click-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Adrian A. (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLK-749) Next Generation Internationalization (i18n) / Localization
Date Sat, 02 Nov 2013 14:58:18 GMT

    [ https://issues.apache.org/jira/browse/CLK-749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13812017#comment-13812017
] 

Adrian A. commented on CLK-749:
-------------------------------

> Bundles have three well-known problems:
> - they must be native2ascii encoded (ugly \uCafe, only ISO 8859-1 character encoding)
- periodically we see letters about it in Mailing list 

Smart IDEs such as IntelliJ have an option to transparently encode this for the user. So the
user will see the right symbol, but save to that file the correct \uXXX encoding

> - keys are strings, so misspelling is usual error 

Smart IDEs such as IntelliJ can navigate to the keys files if they're correct, but also mark
as "unused" those that are not used in the code. So if the user misspells in the property
file a key, than it will be marked as unused.

> - bundle look-up procedure is tricky 

But Click does this transparently for the user using the Page/Control name convention.

> http://cal10n.qos.ch/ 
> We can switch to CAL10N and have many bonuses.

Thanks for pointing this out. The library looks interesting, I'll have a detailed look, but
from just browsing the manual the annotations look horrible IMHO. I'd rather like not to have
such a thing in my code since Click handles this much better for Pages and Controls.
 
> PS: May I ask also to throw all custom / self-made logging facade / level filtering code
and use http://slf4j.org/ directly. 

IMO this belongs in a different issue.


> Next Generation Internationalization (i18n) / Localization
> ----------------------------------------------------------
>
>                 Key: CLK-749
>                 URL: https://issues.apache.org/jira/browse/CLK-749
>             Project: Click
>          Issue Type: Improvement
>          Components: core
>            Reporter: Andrew Fink
>
> Currently Click uses standard  Java Resource Bundles for i18n.
> Bundles have three well-known problems:
> - they must be native2ascii encoded (ugly \uCafe, only ISO 8859-1 character encoding)
- periodically we see letters about it in Mailing list
> - keys are strings, so misspelling is usual error
> - bundle look-up procedure is tricky
> May I suggest one way to make i18n better.
> Ceki Gülcü (famous log4j, slf4j, logback author) has made very interesting library
for 'Compiler Assisted Localization':
> http://cal10n.qos.ch/
> http://cal10n.qos.ch/manual.html
> We can switch to CAL10N and have many bonuses.
> PS: May I ask also to throw all custom / self-made logging facade / level filtering code
and use http://slf4j.org/ directly.
> Slf4j is de-facto standard from logging-in-java father.
> Many apache projects (look at http://slf4j.org/ start page)  use slf4j.
> slf4j is standard / allowed / small dependency for many organizations.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message