Add translations for several suggested languages

[jayhesselberth]

Suggestions welcome!

[github-actions]

🚀 Deployed on https://68ef99ab3a3a2733dff7ddf7--pkgdown-dev.netlify.app

[jayhesselberth]

We could also consider computing the vignette table from the available po files.

[hadley]

@jayhesselberth could you also include the prompt you used? And I'd recommend being explicit in the NEWS bullet about which languages you added, that you used positron assistant, and which model you used.

[hadley]

I definitely agree that it makes sense to automate the list in the vignette.

[hadley]

I had a quick go asking claude code to proofread all the existing translations. That also filled in a few missing, found a problem with Turkish (light and dark look to be swapped), and reveals that we need extra instructions about using $1 etc if the order of the words is changed. We might also want some additional advice for languages with gendered nouns.

[hadley]

First stab at a prompt (for proofreading):

You are an experienced translator. Proofread the translations in po/, making any small fixes immediately and alerting me to any bigger issues. These are GNU gettext translations for pkgdown, a tool used to generate websites for R packages.

Translation advice:

• For languages that use genedered nouns, do your best to generate inclusive translations, e.g. "Beitragende:r" or "auteur·rice".
• If you need to change the order of substititions (e.g. %s) from English version, use %1$s to identify the first substituion %2$s, etc. Only use this form when the translated word order is different.

[maelle]

Thanks! Before merging this, could we please make sure the translations for each language are also reviewed by a native (human 😁) speaker?

[ror-at-ebp]

The German translation is okay. I noticed two things however (in R-de.po):

• tutorials is translated with "Tutorien". This is afaik not a common use for that word and usually "Tutorial" or "Anleitung" is used in this context.
• There is no translation for the msgid "Additional details" (in render.R called author details). A possible translation would be "Zusätzliche Informationen" or "Weitere Details" (to keep it shorter).

[hadley]

I also agree with @maelle that it would be good to get a human to take a look too. Definitely a lot of potential here for LLMs to speed up the work (and expose some small issues with existing translations) but it would be to good to verify each translation with a human (and if we can't find someone, I think that's a sign that language probably isn't that important for the R community).

Maybe it's worth breaking this up in to a few separate PRs? I'm thinking one to automate the language list in the vignette, another to add a prompt (maybe also in the vignette?) and then one PR for each language?

[jayhesselberth]

Automating the language list in the vignette isn't going to be as easy as I thought, as the only files available to pkgdown (assuming build_site(install = TRUE)) are the binary *.mo files. These can be extracted with msgunfmt but that might be fiddly and not worth adding to pkgdown.

So, if where going to add todo bullets (#2927), I think we should just add a bullet to update the vignette with any language updates.

[jayhesselberth]

Closing in favor of individual PRs.