You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Animesh Chaturvedi (JIRA)" <ji...@apache.org> on 2013/06/05 00:31:22 UTC
[jira] [Updated] (CLOUDSTACK-1780) Client UI: i18N files
(messages_xx_XX.properties) needs to be convert in ASCII with unicode char
\uxxxx (and perhaps keys needs to be in alphabetical order)
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Animesh Chaturvedi updated CLOUDSTACK-1780:
-------------------------------------------
Affects Version/s: 4.2.0
> Client UI: i18N files (messages_xx_XX.properties) needs to be convert in ASCII with unicode char \uxxxx (and perhaps keys needs to be in alphabetical order)
> ------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-1780
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1780
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the default.)
> Components: UI
> Affects Versions: 4.1.0, 4.2.0
> Reporter: Milamber
> Assignee: Milamber
> Labels: i18n, translation,
>
> In 4.1 branch, the current file encoding for messages properties files don't allow a correct display in Client UI for non-latin / latin translation (except FR already patched).
> * The tools native2ascii (provide by jdk) can be used to convert the files with character encoded with the unicode code (\uxxxx)
> * To allow better diff in future, and avoid duplicate (currently they have some duplicates keys in EN file), it's would be better to have an alphabetical order.
> * The tools I18Nedit can edit all messages files, to make alphabetical order, make translation directly in unicode char and preserve the unicode char when saving.t
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira