Set the default encoding to UTF-8. #152
Merged
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
|
Looks like the fact I've never coded in Ruby has made it fail Travis CI check for some simple issues. 😟 Edit: Update commits, hopefully should pass now. |
Baza207
force-pushed
the
utf-8_encoding
branch
from
275c400 to
2edb364
Compare
After making myself a little shell script to run on build of a scheme in Xcode, it would always fail on me, even though running it from the terminal worked fine. Setting the default encoding to UTF-8 seems to fix this issue. Reference: https://github.com/berkshelf/berkshelf-api/issues/112 (near the bottom) It's an encoding thing, notice how the JSON parser is trying to use US-ASCII as it's encoding. As of ruby 1.9 the encoding for JSON parser is explicit so you can either add this to the berks executable: Encoding.default_external = "UTF-8"
Baza207
force-pushed
the
utf-8_encoding
branch
from
2edb364 to
908afb0
Compare
|
You should just set the LANGE env var |
|
Ok, I'm not sure how you would do that. Is thats something I'd do instead of the line I added or something that can be set when running jazzy? |
|
I also had this problem running jazzy from Jenkins. I had to manually set the lang variable with the following shell command: export LANG=en_US.UTF-8 |
jpsim
added a commit
that referenced
this pull request
Mar 24, 2015
Set the default encoding to UTF-8.
jpsim
added a commit
that referenced
this pull request
Mar 24, 2015
|
Thanks @Baza207! |
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.
After making myself a little shell script to run on build of a scheme in Xcode, it would always fail on me, even though running it from the terminal worked fine. Setting the default encoding to UTF-8 seems to fix this issue.
Reference: https://github.com/berkshelf/berkshelf-api/issues/112 (near the bottom)
It's an encoding thing, notice how the JSON parser is trying to use US-ASCII as it's encoding. As of ruby 1.9 the encoding for JSON parser is explicit so you can either add this to the berks executable:
Encoding.default_external = "UTF-8"