Reading properties file without native2ascii in SetVariables JobEntry #1608
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@pamval, fixed! |
|
Could anyone please check and merge this pull request? |
pentaho-nbaker
added a commit
that referenced
this pull request
Aug 14, 2015
…ive2ascii Reading properties file without native2ascii in SetVariables JobEntry
|
Sorry for the delay. We're getting close to release time! |
|
Thank you, Nick! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
In Setvariables JobEntry,
I want to write a property file with Japanese strings, not in native2ascii-encoded strings.
With multi-byte character languages such as Japanese, Korean and Chinese,
it's too much trouble with native2ascii encoded strings.
Both UTF8 strings and native2ascii-encoded strings are accepted.