Hi Emerson,
we agree that I18n is an essential feature of BDD, as the scenario
functionality needs to "read well" in the language of the business.
That is why JBehave supports it via configurable keywords.
What you're proposing is nonetheless useful (having different language
keywords preconfigured) and could be implemented by a single
I18nKeywords that extends Keywords and reads bundle-based keyword values
for a given Locale. I would not use Yaml, as straight JDK bundle does
the job easily. And I think it need not be a separate jar.
I've created a jira issue to track this.
http://jira.codehaus.org/browse/JBEHAVE-164
Feel free to attach a patch to this issue, but please no static
singletons :-)
Cheers
Emerson Macedo wrote:
Hi,
I'm a developer from Brazil, and using Jbehave, I needed to write my
acceptance tests in my idiom. So, I created a project named*
jbehave-br*. Since other people may need something similar for other
idioms, I created a project named* jbehave-i18n* aimed to support any
language. By the way, I think that it can be part of Jbehave official
project and I desire someone to take a look and give me a feedback about
the project and the possibility of integrate it in Jbehave.
The jbehave-i18n project are at
http://github.com/emerleite/jbehave-i18n/tree
Regards,
--
Emerson Macedo
http://codificando.com
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
