You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@shiro.apache.org by "George Stan (JIRA)" <ji...@apache.org> on 2010/05/19 16:22:53 UTC
[jira] Created: (SHIRO-165) i18n for all messages
i18n for all messages
---------------------
Key: SHIRO-165
URL: https://issues.apache.org/jira/browse/SHIRO-165
Project: Shiro
Issue Type: Improvement
Reporter: George Stan
Add support for i18n in Shiro. Now it looks like all messages are coded as strings, and only in English.
Please move them to property files, so that the community can translate them.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SHIRO-165) i18n for all messages
Posted by "Paul Merlin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SHIRO-165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12869151#action_12869151 ]
Paul Merlin commented on SHIRO-165:
-----------------------------------
Just a tought. I discovered cal10n some months ago and I'm now using it extensively and find the i18n validation at compile time a must have now. It really ease the i18n workflow.
http://cal10n.qos.ch/
Another project from the man behind log4j & slf4j :)
> i18n for all messages
> ---------------------
>
> Key: SHIRO-165
> URL: https://issues.apache.org/jira/browse/SHIRO-165
> Project: Shiro
> Issue Type: Improvement
> Reporter: George Stan
>
> Add support for i18n in Shiro. Now it looks like all messages are coded as strings, and only in English.
> Please move them to property files, so that the community can translate them.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.