Punt to the operating system for character encodings#2
Merged
Conversation
wking
changed the title
|
Agreed, LGTM. |
Without this, "may contain any Unicode characters" seemed too
ambiguous.
I wish there were cleaner references for the {language}.{encoding}
locales like en_US.UTF-8 and UTF-8. But [1,2] seems too glib, and I
can't find a more targetted UTF-8 link than just dropping folks into a
Unicode chapter (which is what [1] does):
The Unicode Standard, Version 6.0, §3.9 D92, §3.10 D95 (2011)
With the current v8.0 (2015-06-17), it's still §3.9 D92 and §3.10 D95.
The TR35 link is for:
In addition, POSIX locales may also specify the character encoding,
which requires the data to be transformed into that target encoding.
and the POSIX §6.2 link is for:
In other locales, the presence, meaning, and representation of any
additional characters are locale-specific.
[1]: https://en.wikipedia.org/wiki/UTF-8
[2]: https://en.wikipedia.org/wiki/Locale#POSIX_platforms
Signed-off-by: W. Trevor King <wking@tremily.us>
Reviewed-by: Jesse Butler <jeeves.butler@gmail.com>
wking
force-pushed
the
character-encodings
branch
from
4149d49 to
3606bcf
Compare
Owner
Author
|
On Wed, Dec 02, 2015 at 05:57:01PM -0800, Jesse Butler wrote:
I added a Reviewed-by for you (following the semantics here 1), |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Reopened from #1 after adding @julz signed-off-by and squashing the initial commits (after clearing that with him on IRC).
Without this, “may contain any Unicode characters” seemed too
ambiguous.
I wish there were cleaner references for the
{language}.{encoding}locales like
en_US.UTF-8and UTF-8. But Wikipedia linksseem too glib, and I can't find a more targetted UTF-8 link than just
dropping folks into a Unicode chapter (which is what Wikipedia
does):
With the current v8.0 (2015-06-17), it's still §3.9 D92 and §3.10 D95.
The TR35 link is for:
and the POSIX §6.2 link is for: