Difference between revisions of "Extensions development translation"
From Apache OpenOffice Wiki
(Added section on Pootle) |
|||
| Line 18: | Line 18: | ||
=== Use existing translation infrastructure === | === Use existing translation infrastructure === | ||
| − | * upload all PO files to the [ | + | * upload all PO files to the [https://translate.apache.org/ Pootle server] |
* original and translated files synced via source control | * original and translated files synced via source control | ||
* much higher access to available translators | * much higher access to available translators | ||
Latest revision as of 11:32, 28 August 2022
| OOo Extensions project
Please view the wiki usage guidelines
|
|---|
|
Categories: Pages: |
| Extensions on the main site |
|
Extensions in other languages: |
Specifications
- Framework to be used by all Extensions developers
- Language independent UNO package
- API allowing loading file and GUI string retrieving
- Not restricted to already existing Openoffice.org languages
- Tools for creating and add new translations
- Dynamic language switching is optional
- Handle multiline and 'string template' substitution
Proposals
- each language in a po file
- po files are given within the Extension package
- Python Uno package
- A calc or writer macro loads a language po file, enabling translation. Result is then exported
Use existing translation infrastructure
- upload all PO files to the Pootle server
- original and translated files synced via source control
- much higher access to available translators
- easier to update multiple files
- easier to update/grab via script
- announce major changes via l10n mailing list
Realization
currently working on it
