Changes between Version 7 and Version 8 of TracDev/Proposals/ConfigEnumTranslation
- Timestamp:
- Aug 1, 2016, 7:46:36 PM (8 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TracDev/Proposals/ConfigEnumTranslation
v7 v8 1 [[PageOutline(2-5,Contents,pullout)]] 2 1 3 = Proposal for translation of configurable labels 4 2 5 == The Problem 6 3 7 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. 4 8 9 See also [[TracL10N/Transifex]] 10 5 11 == Currently untranslatable items 12 6 13 This is a list of items, that can't be localized yet (including related tickets): 7 14 * 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. 28 35 36 == A possible solution 29 37 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` 38 The 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` 33 40 a. produces a new file `env/htdocs/locale/trac_custom.pot` or 34 41 b. updates an existing one 35 * use similar standard procedures for POfiles (more `trac-admin` commands here)42 * use similar standard procedures for `.po` files (more `trac-admin` commands here) 36 43 * create new message catalogs for a language 37 44 * update one/all existing messages catalogs … … 46 53 * `trac-admin <env> localize ` //`subcommand`//` *` operates on all present catalogs (except for `init`) 47 54 * `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 49 55 50 56 === Implementation details 57 51 58 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. 52 59 ''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`. '' 53 60 54 61 === Wishlist 62 55 63 (Order should matter) 56 64