-
Notifications
You must be signed in to change notification settings - Fork 6
Weblate FAQ
Please see the problem statement and proposed solution in the R Project Sprint 2023's Weblate project.
Each R package has been implemented as at least one component in Weblate, referring to the strings to be translated in a PO file.
When a package includes multiple PO files (e.g. one for the strings extracted from the C sources, another one for the strings extracted from the R sources, and another one for the GUI strings), then there are multiple components for a package.
After logging in and selecting a component, you should see a "Start new translation" button at the bottom of the page, see e.g. at https://translate.rx.studio/projects/r-project/base-c/
Only Weblate admins can do that. For now, please reach out to @daroczig or @MichaelChirico.
- Go the the R Project project dashboard
- Click on the "Add new translation component" button at the bottom of the page
- Provide a name for the component following the naming schema of the other components (package name optionally followed by R or C files between parens, e.g.
methods (R files)
). It is required to split a package into (at least) two components when there are multiple PO files around, e.g. for R and C files, sometime even a 3rd one for the GUI - Source code repo should point to
weblate://r-project/base-r-gui
(this is set to auto-poll the SVN repo) - File format is usually
gettext PO file
(for strings extracted from R core and recommended packages), or e.g. iOS strings (for Mac GUI) - Provide file mask, e.g.
src/library/base/po/*.po
orsrc/library/compiler/po/R-*.po
- Set a Language filter when needed to guide Weblate which files to pick up (e.g. to exclude the PO files starting with
R
(part of the "R files" component) for the "C files" component, something like^(?!en$)[a-z][^.]+$
See above for the definition of a "component", and based on that, see the section on "How to add a new component?".