Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

i18n #34

Closed
jbpros opened this issue Oct 29, 2011 · 8 comments
Closed

i18n #34

jbpros opened this issue Oct 29, 2011 · 8 comments

Comments

@jbpros
Copy link
Member

jbpros commented Oct 29, 2011

Add support for all Gherkin's spoken languages. The # language: xx comment directive should be recognized.

This will probably impact the undefined step definition snippets.

@fodor0205
Copy link

I would be happy to see this feature implemented.

@jbpros
Copy link
Member Author

jbpros commented Jul 24, 2012

Thanks to recent changes in Gherkin.js, this will be easier to implement. I moved it from the 0.5 milestone to 0.4.

@ldegen
Copy link
Contributor

ldegen commented Jan 13, 2014

hi everyone,
It seems we are almost there:

There was an encoding issue in gherkin, cucumber/gherkin#225, but that is fixed in 2.12.2.
I just had another look at #116, which I understand is based on #109.
I added a trivial modification to the regexp used to detect the language directive and rebased it on top of the current master of the original repository.

The result is here: ldegen/cucumber-js@0beabd4

As far as I can tell, it works as it should. In fact, we are using this right now on a real project with German scenarios, umlauts and all. No problems thus far.

I am not sure how to proceed now. Should I start another pull request?
There should probably be some scenarios in features/cucumber-tck/i18n.feature?

cheers,
--lu

@jbpros
Copy link
Member Author

jbpros commented Jan 14, 2014

Thank you for this @ldegen.

Adding scenarios to the feature file and making them pass would indeed be the next step. Are you up for it? Please make another PR if you are.

ldegen added a commit to ldegen/cucumber-tck that referenced this issue Feb 21, 2014
This is related to cucumber/cucumber-js#34.
Please note that this *will fail* with the current master
of cucumber/cucumber-js.
@ldegen
Copy link
Contributor

ldegen commented Feb 21, 2014

@jbpros, today I found myself with some time on my hands so I tried to pull (pun intended) this of.

I am not sure, if this is what you had in mind. I made a separate pull request cucumber-attic/cucumber-tck#15 to get the i18n scenarios into cucumber-tck, but of course those will fail for cucumber-js unless #156 is merged.
I would have prefered to put both in a single pull request, but I have no idea if this is even possible?

@ldegen
Copy link
Contributor

ldegen commented Feb 21, 2014

Ah, btw, the generation of snippets for undefined steps is still missing. So you probably do not want to close this issue yet.

jbpros pushed a commit to cucumber-attic/cucumber-tck that referenced this issue Mar 5, 2014
This is related to cucumber/cucumber-js#34.
Please note that this *will fail* with the current master
of cucumber/cucumber-js.
@jbpros jbpros closed this as completed in 9ace841 Mar 5, 2014
@jbpros
Copy link
Member Author

jbpros commented Mar 5, 2014

@ldegen thank you for your great work on this. Your PR has been merged. Snippets are indeed not yet internationalised but that can be handled separately. The most important thing was to support other languages than english in Gherkin files.

@lock
Copy link

lock bot commented Oct 25, 2018

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators Oct 25, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants