Re^4: JSON::XS (and JSON::PP) appear to generate invalid UTF-8 for character in range 127 to 255


No such thing as a small change
	PerlMonks

Re^4: JSON::XS (and JSON::PP) appear to generate invalid UTF-8 for character in range 127 to 255

by oiskuu (Hermit)

on Dec 07, 2014 at 16:45 UTC ( [id://1109486]=note: print w/replies, xml )

Need Help??

in reply to Re^3: JSON::XS (and JSON::PP) appear to generate invalid UTF-8 for character in range 127 to 255
in thread JSON::XS (and JSON::PP) appear to generate invalid UTF-8 for character in range 127 to 255

You've confounded unicode with an encoding scheme (UTF-8). Some other encodings, say UCS-2, allow you to seek and read as in above example.

ASCII is a binary encoding, too. Being the simplest and a common default, there's rarely any problem with it.

Unicode is trouble, that's true. Its implementation almost invariably brings layers of abstraction, lasagna code, new levels of slow, new glitches, and sometimes, design changes that require extensive refactoring.

As an example, take the notion of double-width glyphs. Very useful, to be sure, but also quite disruptive. Fixed-width terminal is no more; cell addressing is no longer character addressing; text area layout re-flows as you edit it. Why stop there, in the limbo between character-cell and full GUI, why not assign a point width to every char?