| 14 | |
| 15 | === Specification |
| 16 | |
| 17 | At first step it is intended for Java's [http://en.wikipedia.org/wiki/Java_resource_bundle resource bundle] files; thus in this text only resource bundles / properties files are used. As there is a similar logic to Portable Objects (PO) it should be possible to adapt all requirements to them too. |
| 18 | |
| 19 | The idea is to use `properties` files from subversion control (such as SVN). It should be parametrized in `trac.ini` file, which files (possibly with an asterix as a wilcard) should be editable. These files should be displayed as a table like: |
| 20 | |
| 21 | ||= Key =||= English =||= Deutsch =|| |
| 22 | || Common.German || German || Deutsch || |
| 23 | || Common.Cancel || Cancel || Abbrechen || |
| 24 | |
| 25 | ==== Workflow |
| 26 | |
| 27 | When saving translations it should be commited to subversion control (when permissions are sufficient, e.g. as developer) or a diff / patch file should be created. This patch file should be stored at a specific place with a comment, so developers can review them and then adopt them by committing to version control. |
| 28 | |
| 29 | ==== Needed Permissions |
| 30 | |
| 31 | TM for TranslationManager |
| 32 | |
| 33 | ||= Permission =||= Used for =|| |
| 34 | || TM_VIEW || only viewing translations || |
| 35 | || TM_EDIT || edit translations (creating patch files) || |
| 36 | || TM_COMMIT || commit translation to version control || |