Proposed solution to #487 (International keywords build problems) #499
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This proposed fix for #487 changes generated java annotations from top level classes to inner classes. This is to work around difficulties with java source files with names containing multibyte characters on OS X.
Prior to this PR, the Swedish translation for
Then
would be a top level class defined inSå.java
, under the packagecucumber.api.java.sv
.This PR changes each translation to be defined in a single source file, in this case
sv.java
defined under the packagecucumber.api.java
. Each translation contains an inner class for each keyword.This should remain source compatible with previous releases. The following import statement should work both before and after:
Using this scheme, source file names will only ever contain ASCII characters, so the file name problems should go away.
One minor drawback is that typing
@Så
in IDEA and then using a hotkey to insert the desired import will write out this code:Although this compiles just fine it doesn't look too good, so you might want to change it to:
Please try this out and let me know how it works for you.