| 3 | | Toolset options: |
| 4 | | * [http://babel.edgewall.org Babel] - integrates with Trac |
| | 3 | Sahanapy should preferably use the combination of GNU/gettext + Pootle/translate toolkit + Babel for internationalization purposes: |
| | 4 | |
| | 5 | * [http://www.gnu.org/software/gettext GNU Gettext] |
| | 6 | * [http://translate.sourceforge.net/wiki/start Translate Toolkit & Pootle] |
| | 7 | * [http://babel.edgewall.org Babel] |
| | 8 | |
| | 9 | Justification: |
| | 10 | * PO-based translation (GNU/gettext) works with both Sahana-PHP and Sahana-Python (one translation project applicable for both code bases) |
| | 11 | * there is already a Pootle engine successfully run and well known by the Sahana community |
| | 12 | * Babel tools support advanced message extraction methods (e.g. even from HTML templates) |
| | 13 | * Babel library also supports localized date and number formatting which is very useful for the Sahana type of application |
| | 14 | * Babel also integrates well with Trac |
| | 15 | * Babel comes under BSD-like license, which is compatible to LGPL3. |
| | 16 | |
| | 17 | Disadvantages: |
| | 18 | * GNU/gettext does not support context tagging of message strings, so non-ambiguous terminology is a requirement |
| | 19 | * Offline RAD would require extra software (all except Pootle, which can be replaced by any text editor) + perhaps extract/build scripts |
| | 20 | |
| | 21 | Other options: |
