Changes between Version 3 and Version 4 of TracDev/Proposals/ConfigEnumTranslation

Timestamp:

Oct 26, 2012, 7:46:12 AM (12 years ago)

Author:

Christian Boos

Comment:

I like it ;-)

TracDev/Proposals/ConfigEnumTranslation

@@ -1 +1 @@
 = Proposal for translation of configurable labels
 == The Problem
-We have translatable messages since Trac-0.12, even extended the i18n system towards configuration option doc-strings. But we're still missing translations in some rather prominent places.
+We have translatable messages since Trac-0.12, even extended the i18n system towards configuration option doc-strings. But we're still missing translations in some rather prominent places, mostly related to terms that are meant to be customized in Trac installations.
 
 == Currently untranslatable items
@@ -10 +10 @@
    * status (see configurable ticket workflow below)
    * priority
-   * serverity
+   * severity
    * milestone (see below)
    * customized labels for standard fields (see #6249)
@@ -21 +21 @@
   * ticket changes (related to ticket status from work-flow above, see #5441)
 
-Well, I guess this should be almost identical to MissingTranslations (listed by module), right?
+Those are also present for now in MissingTranslations (listed by module), although that page should be dedicated to terms that could be translated using the current markers and which are simply missing them. 
+
+Here we'll focus on terms that are meant to be customized and are found in the database or in the TracIni file rather than in the code.
 
 
@@ -34 +36 @@
  * use standard procedures to edit message catalogs
 
+Or, alternatively:
+ * `trac-admin <env> localize` and subcommands:
+   - `extract` -- creates or updates the `<env>/locale/custom.po` file
+   - `init fr` -- creates the `<env>/locale/fr/LC_MESSAGES/custom.po` file from `<env>/locale/fr/LC_MESSAGES/custom.po` if it doesn't exist yet
+   - `update fr` -- updates that file
+   - `compile fr` -- compiles that file into `<env>/locale/fr/LC_MESSAGES/custom.mo`
+ * `trac-admin <env> localize ` //`subcommand`//` *` operates on all present catalogs (except for `init`)
+ * `trac-admin <env> initenv` copies into `<env>/locale` all the already available `custom` related files, containing the translation for the "base" terms (e.g. the workflow states for the default terms, [#Wishlist 2.] below)
+ 
+
 === Implementation details
 The aforementioned work-flow implies, that custom message cataloges are rather volatile. But recompilation on Trac environment load should be avoided, because this could be rather time-consuming. So it must be possible to pre-compile them, i.e. with yet another `trac-admin` command.
+ ''cboos - I agree. Let's not try to work with .po files directly (if that was what you implied). Trac should only consider the present `.mo` files obtained from a `trac-admin <env> localize compile`. ''
 
 === Wishlist
 (Order should matter)
 
- * auto-generated TRANSLATOR hints like
+ 1. auto-generated TRANSLATOR hints like
   `# ini:ticket-workflow` or `# enum:priority`
- * include a ''basic common'' set of typical terms, like work-flow action names from default ticket work-flow
- * detect changes, to remind for recompilation, if pending changes are detected, but PO (clear-text) and MO (compiled) message catalog files change time must be tracked like done for `trac.ini` to make this happen
+   - alternatively, if there's no //source// file, that line could be faked: 
+     {{{
+#: ticket/enum/priority:2
+msgid "high"
+     }}}
+ 2. include a ''basic common'' set of typical terms, like work-flow action names from default ticket work-flow
+ 3. detect changes, to remind for recompilation, if pending changes are detected, but PO (clear-text) and MO (compiled) message catalog files change time must be tracked like done for `trac.ini` to make this happen
+   - a macro could take care of this? `[[TracAdminLocalizeStatus(format=stats,lang=fr)]]` / `[[TracAdminLocalizeStatus(format=table)]]`