Differences

This shows you the differences between two versions of the page.

--- poeditor [2021/03/31 15:03] – [Making strings available for translation] gmcharlton
+++ poeditor [2023/12/13 15:54] (current) – [Making strings available for translation] tmccanna
@@ Line 10: / Line 10: @@
 ===== Making strings available for translation =====
+You will need to be an admin in poeditor.com in order to do the following steps.
 To upload new strings to poeditor.com:
-  - In the ''Open-ILS/src/eg2'' directory, run ''npm run export-strings''
+  - In the ''Open-ILS/src/eg2'' directory, run ''npm run export-strings''. The output file is ''Open-ILS/src/eg2/locale/messages.xmb''.
   - Go to [[https://poeditor.com/projects/import?id=218177|the importer]]
-  - Upload the ''Open-ILS/src/eg2/src/locales/messages.xmb'' file -- make sure that "Import terms only" is checked.  Also add tags to identify the new strings, like this:{{ :po_editor_tagging.png?nolink&400 |}}. In this example, the 3.7 beta replace will have all new strings tagged with rel_3_7_beta2, and the entire set of strings tagged with rel_3_7.
+  - Upload the ''Open-ILS/src/eg2/locale/messages.xmb'' file. Be sure to enable "Also import translations to a language" and select English (this will keep English at 100% translated):{{:screenshot-import.png?800|}}
+  - Be sure to add tags - you should have **TWO RULES**: one rule to add the base version (rel_3_12) to **all** translations and a second rule to add the specific version (rel_3_12_0) to **new** translations. The use of a tag like rel_3_12_0 for new terms is done purely as a convenience to the translators to identify the strings that are new to the release. However, it should be noted that the definition of "new" applies to the entire translation project. For example, if you upload new terms for rel_3_11_beta, then upload for rel_3_10, rel_3_10_x, a new terms that are already tagged rel_3_11_beta will not get the tag rel_3_10_x.
   - Go to the [[https://poeditor.com/projects/import_translations?id_language=43&id=218177|English language importer]] and import the xmb file, making sure to not overwrite old translations. Unlike the first step, which appears to just load the numeric IDs of the strings to be translated, this step also adds their English-language values.
+===== Adding/updating translations to Evergreen =====
+If a translation is sufficiently complete, in POEditor go to the language, then export it as an ''.xtb'' file. The result should be committed to the path ''Open-ILS/src/eg2/src/locale/'' as ''messages.$LANGUAGECODE.xtb''.