potools
potools copied to clipboard
MichaelChirico
Tools for working with translations in R
A follow-up to #180 -- consider whether/how we could make the default diagnostics more aware of custom translators.
Follow-up to #167 that will be enabled by exporting `write_pot_files()` (#168)
If `FALSE`, we assume the `.pot` is up to date and only seek to update .po files W.R.T. that. In this way, we might be able to facilitate the R...
It could also possibly try and do an `svn` download/sync
Allow users the flexibility to set the width directly (rather than using base's inconsistency or my default `width=Inf` setting)
`Rgui` is the last domain that comes along with `base`, see brief mention [here](https://developer.r-project.org/Translations30.html) and the Rgui.pot template: https://github.com/wch/r-source/blob/trunk/src/library/base/po/RGui.pot IINM we are looking for strings in the `po/POTFILES` (see #68)...
For packages that are not equipped yet at all for translation, they'll need to define the translation macro/includes to get translation-ready. It should be easy to generate a simple po.h...
Now we have `pt_BR`, I think it's fine to just use `pt`. We can also include logic to share columns of `language_metadata.csv` to the "parent" locale. Maybe split to a...
Currently, the R-tr.po file is "corrupted" -- `nplural=1; plural=0` for Turkish, but many (empty) `msgstr[1]` entries exist, e.g.: https://github.com/r-devel/r-svn/blob/b7d9620c65e1924553c2e270f464cf185fb02ab4/src/library/base/po/R-tr.po#L1763-L1766 Apparently this doesn't trip up the rest of `gettext` as that...