[
http://jira.codehaus.org/browse/JBEHAVE-164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=181803#action_181803
]
Mauro Talevi commented on JBEHAVE-164:
--------------------------------------
I think we should still pursue the JDK-way, because the ResourceBundle is
designed to handle resources by locale which I don't see YAML doing, and find a
way to overcome the encoding limitation. E.g. this post points to one:
http://www.kai-mai.com/node/128
In any case, in my opinion, of the two evils encoding is the lesser of the two:
folks will not in general need to fiddle with the keywords bundles, and if they
do it's a one-off thing to set the values of the keywords.
> I18N Keywords
> -------------
>
> Key: JBEHAVE-164
> URL: http://jira.codehaus.org/browse/JBEHAVE-164
> Project: JBehave
> Issue Type: Improvement
> Reporter: Mauro Talevi
> Priority: Minor
> Fix For: 2.3
>
>
> As proposed by Emerson Macedo on dev list, it would be useful to have
> keywords for different languages pre-configured.
> An I18nKeywords that reads keywords from I18n resource bundles for different
> Locales should do the trick.
> We can provide i18n bundles for the most common locales in our core jar (very
> small overhead in terms of size!), and users can add or override them as
> needed.
> The localisation should be done when instantiating the Keywords class so it
> only happens once.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
