Set unicode-aware locale in containers #4289
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
HebaruSan
added
Bug
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.
Problem
The metadata for Skopos has
??in the abstract where non-ASCII characters are provided by the GitHub API:Notably, this does not happen for me locally.
Cause
The
LANGenvironment variable is not set in the Inflator's container, so unicode characters are not handled properly. I have it set toen_US.utf-8, the latter part of which enables unicode.Changes
Now our
Dockerfiles setLANGtoC.utf-8to enable unicode support. This is also the value used in the bot's Python-based containers. This causes UTF-8 strings from the GitHub API to be faithfully recorded into the metadata.Fixes #4288.