28 add items for localisation #29
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
llrs
approved these changes
Nov 1, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I thought eliocamp/rhelpi18n was important enough to mention even though it's experimental - package authors may wish to experiment with it, e.g. creating translation modules for CRAN packages that are hosted on GitHub.
I originally though packages like stranslate and translated might not be compatible with standard translation software, but it seems plain text and JSON formats (among others) are also supported by tools like OmegaT (possibly with Okapi filters), GitLocalize, Weblate and Crowdin, so package authors may prefer these alternatives to the standard PO/POT files.
(the same tools can also handle YAML format as used by rhelpi18n).