Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • The Export/Import code that copies to/from POEditor prefixes each property key with the package name to ensure that the keys are always unique.
  • In POEditor the keys are known as terms.If a value contains a {n} sequence (usually written as [{n}] to distinguish a value from the surrounding text) then it will be processed by a MessageFormatter which means any single quotes must be escaped by using two single quotes
  • The POEditor import/export process automatically handles any necessary escaping/unescaping.
  • The Manager and Host Manager applications use messages that start with "OK - " to indicate success of an operation. This prefix has to be preserved when translating. See Bug 63141 for details.

The process to synchronize the Tomcat source code with POEditor needs to be performed by a committer. The process works as follows:

  1. Update English translations in Tomcat:
    Add or remove keys (terms) to the English LocalStrings.properties files.
    Make any changes required to the values in the English LocalStrings.properties files.
  2. Export the translations from Tomcat:
    run org.apache.tomcat.buildutil.translate.Export
  3. Import the terms with English translations to POEditor.
  4. Update the translations for other languages on POEditor web site.
  5. Export one or more languages (Note: only export translated terms).
  6. Import the translations into Tomcat:
    run org.apache.tomcat.buildutil.translate.Import

...

For small changes it is possible to make the change in both git repository and POEditor - effectively keeping the two in sync manually - and not use the Import/Export process. Care needs to be taken to ensure that the two systems remain synchronized.

Changes are typically imported from POEditor by the release manager shortly before a release is tagged.