Changes between Version 7 and Version 8 of TracDev/Proposals/ConfigEnumTranslation

Timestamp:

Aug 1, 2016, 7:46:36 PM (8 years ago)

Author:

figaro

Comment:

Cosmetic changes

TracDev/Proposals/ConfigEnumTranslation

@@ +1 @@
+[[PageOutline(2-5,Contents,pullout)]]
+
 = 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, mostly related to terms that are meant to be customized in Trac installations.
 
+See also [[TracL10N/Transifex]]
+
 == Currently untranslatable items
+
 This is a list of items, that can't be localized yet (including related tickets):
  * Enum
@@ -27 +34 @@
 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.
 
+== A possible solution
 
-== A possible solution
-The following rough sketch of a suitable translation work-flow sprung from discussion on IRC tonight (25-Oct-2012):
- * `$> trac-admin <env> extract_custom_messages`
+The following rough sketch of a suitable translation work-flow sprung from a discussion on IRC (25-Oct-2012):
+ * `$ trac-admin <env> extract_custom_messages`
   a. produces a new file `env/htdocs/locale/trac_custom.pot` or
   b. updates an existing one
- * use similar standard procedures for PO files (more `trac-admin` commands here)
+ * use similar standard procedures for `.po` files (more `trac-admin` commands here)
   * create new message catalogs for a language
   * update one/all existing messages catalogs
@@ -46 +53 @@
  * `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)