[
http://jira.codehaus.org/browse/JBEHAVE-164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=181862#action_181862
]
Mauro Talevi commented on JBEHAVE-164:
--------------------------------------
But I'm thinking it makes sense to provide the keyword bundles for several
locales, and not just for testing purposes.
Then users can simply instantiate new I18nKewords(Locale) and have all the
keywords set for that locale.
Yes, let's provide our own version of ResourceBundle to overcome the encoding
issue.
> 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
