News for hackers. Stuff that matters.

A comment on UTF-8 Everywhere (2012). Parent comment

Re:UTF-8 Everywhere (2012) by pjscott on Sunday June 19, 2016 @06:14PM (#11934963)
It's important to be insufferably pedantic about this: they index by code point, which is almost but not quite what people expect a character to be.

    $ python3
    >>> "위키백과"[1]
    '키'
    >>> "위키백과"[1] # Should be identical, right?
    'ᅱ'
[ Parent | on HN ]
Re:UTF-8 Everywhere (2012) by kbenson on Sunday June 19, 2016 @07:56PM (#11935351)
> It's important to be insufferably pedantic about this

That is perhaps the most succinct and accurate way I've heard to explain and justify why you're sounding like a wet blanket to people that may not understand, while acknowledging that you know how you sound, but there is a reason for it. I expect to use this in the future.

[ Parent | on HN ]
Re:UTF-8 Everywhere (2012) by schoen on Sunday June 19, 2016 @11:40PM (#11935919)
That's an awesome example! To show more of how it works for Western language speakers who might be confused, how about

c = "é"

c[0], c[1]

It's the same phenomenon with Latin characters. (Extra bonus: for me, the combining acute accent character then combines in the terminal with the apostrophe that Python uses to delimit the string!)

Another idea to see the effect is "a" + "é"[1]. (The result is 'á'... and as in your examples, a precomposed "̈́é" is also available which doesn't exhibit any of these phenomena.)

[ Parent | on HN ]
Re:UTF-8 Everywhere (2012) by kazinator on Sunday June 19, 2016 @10:26PM (#11935750)
Same with English, sort of. What is

    "difficult"[2]?
Is it 'f'? Or the ligature `ffi`? :)
[ Parent | on HN ]