Thu Oct 27 14:18:21 2005
Ticket #1523
Use the localizer tool for translating glivesupport
| Priority: | normal | Reporter: | fransman <[email protected]> |
|---|---|---|---|
| Severity: | minor | Assigned to: | ferenc |
| Component: | localizer | Status: | new |
| Version: | 1.0.x | Resolution: | |
| Milestone: | 1.1.x | Keywords: |
Description by fransman <[email protected]>:
Can we think about a methote to use the html localizer tool for translating the glivesupport stings.
Attachments
Changelog
Thu Oct 27 18:24:09 2005: Modified by maroy
- milestone changed from 1.x to 1.1
Thu Oct 27 22:53:09 2005: Modified by sebastian
- summary changed from Use the localizer tool for translating glivesupport to <
- owner changed from sebastian to ferenc
Ferenc, what do you think? Loclizer tool currently use very simple xml files for each language with this structure: <tranlations>
<item>
<key>Menu</key> <value>Menü</value>
</item> <item> [...] </translation>
Fri Oct 28 08:10:54 2005: Modified by maroy
it's not that easy...
the C++ code uses a hierarchical structure, take a look here:
Fri Oct 28 17:44:23 2005: Modified by fransman <[email protected]>
- summary changed from < to Use the localizer tool for translating glivesupport
when localizer becomes a separate product, with XLIFF support, then it will be able to do this...