Fix Gherkin language execution parameters

[brazilianbytes]

Cucumber 6.0.3 parameters are different from documentation.

[aslakhellesoy]

Unfortunately, this option is named differently across platforms, so changing from --i18n to --i18n-languages makes this incorrect for cucumber-ruby and cucumber-jvm.

I think we should simply get rid of the option and refer users to the docs.

[aslakhellesoy]

See https://github.com/cucumber/cucumber/issues/783

[aslakhellesoy]

Should we just close this, or do we want to make the docs language specific? WDYT @mlvandijk ?

[mlvandijk]

@aslakhellesoy We don't currently have different language tabs on the Gherkin page(s) as Gherkin should be programming language agnostic.

We could just remove this section imho. - what do you think?

[mlvandijk]

Thanks for pointing out the inconsistency though @brazilianbytes!

[aslakhellesoy]

There are two suggestions here:

1. Remove the docs about --i18n
2. Remove --i18n from Cucumbers - see https://github.com/cucumber/cucumber/issues/783

I think we should remove both.

[mlvandijk]

@aslakhellesoy Can we point them anywhere to see up to date available languages (rather than duplicate in documentation?). Kind of like we do for DataTables (points to datatable README from the docs)

[aslakhellesoy]

Yes @mlvandijk here: https://cucumber.io/docs/gherkin/reference/#gherkin-dialects

[mlvandijk]

Perfect! Let's link there. @brazilianbytes - would you be willing to do this change instead?

[mlvandijk]

Closed in favor of cucumber/common#431