Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

2
  • 2
    $\begingroup$ A few nitpicks: There is no such thing as "Two-byte UTF-16"; the fixed-width encoding is called UCS-2, and UTF-16 has always been variable width. Normalisation isn't something just provided by Java, it's part of the Unicode standard. Similarly, I'm not sure what you mean by "under Windows" when talking about determining file encoding. I also have no idea what this sentence is trying to say: "The latest java versions even allow String, text in Unicode, to store solely internally the text in say ISO-8859-1." $\endgroup$ Commented Jun 16, 2020 at 8:29
  • $\begingroup$ @IMSoP First for the other readers to follow your well foiunded info. Indeed UCS-2 wanted to do Unicode in two bytes. and this I misnamed UTF-16 in its early history. Ironically much java code treats UTF-16 char as Unicode, say UCS-2, instead of using code points (Unicode). Normalisation is specified by Unicode. A single canonical preference I believe not. Your comment is full of worthy points. Thanks. $\endgroup$ Commented Jun 16, 2020 at 11:34