Difference between revisions of "Extensions development translation"
From Apache OpenOffice Wiki
Timarandras (Talk | contribs) m (typo fixes) |
|||
| Line 2: | Line 2: | ||
=== Specifications === | === Specifications === | ||
| − | * Framework to be used by all Extensions | + | * Framework to be used by all Extensions developers |
| − | * Language | + | * Language independent UNO package |
| − | * API allowing loading file and GUI string | + | * API allowing loading file and GUI string retrieving |
* 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 | ||
* Dynamic language switching is optional | * Dynamic language switching is optional | ||
| − | * Handle multiline and 'string template | + | * Handle multiline and 'string template' substitution |
=== Proposals === | === Proposals === | ||
Revision as of 20:56, 31 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 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
Realization
currently thinking to it
