|
2014-01-22
| ||
| 18:43 | • Closed ticket [8d27d1a470]: Add option(s) for localizing Fossil plus 4 other changes ... (artifact: 1bbabffdbb user: stephan) | |
| 11:46 | • New ticket [8d27d1a470]. ... (artifact: 9ce9c2223b user: anonymous) | |
| Ticket Hash: | 8d27d1a47010fb41a3ecd458e046ae3f5bcffe27 | |||
| Title: | Add option(s) for localizing Fossil | |||
| Status: | Closed | Type: | Feature_Request | |
| Severity: | Important | Priority: | ||
| Subsystem: | Resolution: | Rejected | ||
| Last Modified: | 2014-01-22 18:43:05 | |||
| Version Found In: | 1.27 | |||
| User Comments: | ||||
nobody added on 2014-01-22 11:46:15:
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. stephan added on 2014-01-22 18:43:05: 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/ | ||||