Changes between Version 2 and Version 3 of TranslationManagerPlugin


Ignore:
Timestamp:
Jul 17, 2014, 2:35:25 PM (10 years ago)
Author:
Franz
Comment:

Added paragraph "Specification"

Legend:

Unmodified
Added
Removed
Modified
  • TranslationManagerPlugin

    v2 v3  
    1212- Java [http://en.wikipedia.org/wiki/Java_resource_bundle resource bundle], ''currently the main goal''
    1313- [http://en.wikipedia.org/wiki/Gettext GNU Gettext] (Portable Objects - PO), used for Pyton, C
     14
     15=== Specification
     16
     17At 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
     19The 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
     27When 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
     31TM 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 ||
    1437
    1538== !Bugs/Feature Requests