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

charset about InputStreamReader when parse groovy file #251

Closed
k4124k opened this issue Mar 10, 2012 · 1 comment
Closed

charset about InputStreamReader when parse groovy file #251

k4124k opened this issue Mar 10, 2012 · 1 comment

Comments

@k4124k
Copy link

k4124k commented Mar 10, 2012

when using command to run cucumber-jvm, always see some random code of chinese!
then i found that the InputStreamReader was not assigned utf-8.

OS: windows7 X64 zh-cn

Error Message:
[java] org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed:
[java] A8Grid_Steps.groovy: 22: expecting anything but ''\n''; got it anyway @ line 22, column 47.
[java] \d+)鏉¤褰?){int currentRows ->
[java] ^
[java]
[java] 1 error

java file path:cucumber-jvm / groovy / src / main / java / cucumber / runtime / groovy / GroovyBackend.java
Error method:
private Script parse(Resource resource) {
try {
return shell.parse(new InputStreamReader(resource.getInputStream()), resource.getPath());
} catch (IOException e) {
throw new CucumberException(e);
}
}

mlvandijk referenced this issue Aug 22, 2017
In accordance with cucumber/common#251
normalization will help messaging be consistent across the board
allowing different users to be able to read all history files across
Cucumber regardless of which language specific repo of which they're
most familiar.
@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
mpkorstanje pushed a commit that referenced this issue Oct 4, 2019
mpkorstanje pushed a commit that referenced this issue Oct 4, 2019
mpkorstanje pushed a commit that referenced this issue Oct 4, 2019
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

2 participants