Edgewall Software

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


Ignore:
Timestamp:
Aug 1, 2016, 7:46:36 PM (3 years ago)
Author:
figaro
Comment:

Cosmetic changes

Legend:

Unmodified
Added
Removed
Modified
  • TracDev/Proposals/ConfigEnumTranslation

    v7 v8  
     1[[PageOutline(2-5,Contents,pullout)]]
     2
    13= Proposal for translation of configurable labels
     4
    25== The Problem
     6
    37We 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.
    48
     9See also [[TracL10N/Transifex]]
     10
    511== Currently untranslatable items
     12
    613This is a list of items, that can't be localized yet (including related tickets):
    714 * Enum
     
    2734Here 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.
    2835
     36== A possible solution
    2937
    30 == A possible solution
    31 The following rough sketch of a suitable translation work-flow sprung from discussion on IRC tonight (25-Oct-2012):
    32  * `$> trac-admin <env> extract_custom_messages`
     38The following rough sketch of a suitable translation work-flow sprung from a discussion on IRC (25-Oct-2012):
     39 * `$ trac-admin <env> extract_custom_messages`
    3340  a. produces a new file `env/htdocs/locale/trac_custom.pot` or
    3441  b. updates an existing one
    35  * use similar standard procedures for PO files (more `trac-admin` commands here)
     42 * use similar standard procedures for `.po` files (more `trac-admin` commands here)
    3643  * create new message catalogs for a language
    3744  * update one/all existing messages catalogs
     
    4653 * `trac-admin <env> localize ` //`subcommand`//` *` operates on all present catalogs (except for `init`)
    4754 * `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)
    48  
    4955
    5056=== Implementation details
     57
    5158The 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.
    5259 ''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`. ''
    5360
    5461=== Wishlist
     62
    5563(Order should matter)
    5664