translations: choose the right approach
+ we will include in configuration file label (msg_id) for every translatable text
+ for every language we will provide separate translation file
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Medium
- Drafter:
- Vincent Fretin
- Direction:
- Needs approval
- Assignee:
- Andrew Mleczko
- Definition:
- Approved
- Series goal:
- Accepted for 1.x
- Implementation:
-
Implemented
- Milestone target:
-
1.1
- Started by
- Andrew Mleczko
- Completed by
- Andrew Mleczko
Related branches
Related bugs
Sprints
Whiteboard
since we changed the tours format from a dictionary into a configuration-like. e.g.:
[amberjack]
steps =
3_all-done
title = Add and publish a Folder
[0_create-
blueprint = collective.
title = Create a new folder
url = /
text = Folders are one of ....
validators =
python: isManager
python: isNotFolderCreated
microsteps =
[0_0_microstep]
blueprint = collective.
description = If you don't want to perform the ...
...
obviously, we need to manage translations.
what we would like to have is:
- a set of files like [1]
- tourX.cfg (contains the tour itself)
- tourX.pot (the template)
- tourX_en/
- keep untouched the translations we already have (just renaming the files)
- have a i18ndude-like tool that from a .cfg file can create the .pot one [2]
[1] from a deployment, sharing and distribution point of view those files will be kept in a zip/tgz unique file. that's why we prefer to use a simpler 'tourX_language.po' to a locales/
[2] is it possibile to extend i18ndude to manage also that format? at the end the labels that need to be translated can be easily got from the file though ConfigParser.
