Difference between revisions of "Extensions development translation"
From Apache OpenOffice Wiki
(→Specifications) |
|||
| Line 3: | Line 3: | ||
=== Specifications === | === Specifications === | ||
* Framework to be used by all Extensions developper | * Framework to be used by all Extensions developper | ||
| − | * | + | * Language independant UNO package |
| + | * API allowing loading file and GUI string retreiving | ||
* Not restricted to already existing Openoffice.org languages | * Not restricted to already existing Openoffice.org languages | ||
* Tools for creating and add new translations | * Tools for creating and add new translations | ||
Revision as of 14:58, 20 March 2006
| 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 developper
- Language independant UNO package
- API allowing loading file and GUI string retreiving
- Not restricted to already existing Openoffice.org languages
- Tools for creating and add new translations
- Dynamic language switching is optional
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, enablingtranslation. Result is then exported
Realization
currently thinking to it
