click-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Fink (JIRA)" <>
Subject [jira] Created: (CLK-749) Next Generation Internationalization (i18n) / Localization
Date Sat, 08 Jan 2011 15:44:46 GMT
Next Generation Internationalization (i18n) / Localization

                 Key: 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':

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 directly.
Slf4j is de-facto standard from logging-in-java father.

Many apache projects (look at start page)  use slf4j.
slf4j is standard / allowed / small dependency for many organizations.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message