Fossil SCM
Add option(s) for localizing Fossil
8d27d1a47010fb4…
· opened 12 years, 2 months ago
- Type
- Feature_Request
- Priority
- —
- Severity
- Important
- Resolution
- Rejected
- Subsystem
- —
- Created
- Jan. 22, 2014 11:46 a.m.
Refering to email discussion, e.g. this:
[http://lists.fossil-scm.org:8080/pipermail/fossil-users/2013-February/011833.html]
I suggest that this is implemented gradually. If nothing more, then the documentation could at least describ the current possibilities, even if it consists of nothing more than altering the menus in the Web UI.
Comments (2)
Refering to email discussion, e.g. this:
[http://lists.fossil-scm.org:8080/pipermail/fossil-users/2013-February/011833.html]
I suggest that this is implemented gradually. If nothing more, then the documentation could at least describ the current possibilities, even if it consists of nothing more than altering the menus in the Web UI.
i18n of Fossil is not feasible without a complete and utter rewrite. Much of the text is interwoven with SQL code, and the current mechanism for generating parameterized text (printf-like functions) does not port 1-to-1 for many sorts of translations (e.g. where arguments need to have a different order). There's no practical way to do this in the current code base. That said, libfossil is being developed to allow (amongst other things) the creation of localized UIs: http://fossil.wanderinghorse.net/repos/libfossil/