{"id":137,"date":"2008-03-17T12:21:00","date_gmt":"2008-03-17T12:21:00","guid":{"rendered":"http:\/\/www.tutego.de\/blog\/javainsel\/?p=137"},"modified":"2008-03-17T12:21:00","modified_gmt":"2008-03-17T12:21:00","slug":"thema-der-woche-unicode-und-kodierungen","status":"publish","type":"post","link":"https:\/\/www.tutego.de\/blog\/javainsel\/2008\/03\/thema-der-woche-unicode-und-kodierungen\/","title":{"rendered":"Thema der Woche: Unicode und Kodierungen"},"content":{"rendered":"

Java verarbeitet Zeichen (bisher) intern in 2-Byte Unicode. Gespeichert werden Daten aber in der Regel in UTF-8 oder, f\u00fcr uns in Europa, in Latin-1. Thema der Woche ist Unicode und die Umkodierungen. Am Anfang sollen The Ten Commandments of Unicode<\/a> von Elliotte Rusty Harold stehen:<\/p>\n

    \n
  1. I am Unicode, thy character set. Thou shalt have no other character sets before me.<\/li>\n
  2. Thou shalt carefully specify the character encoding and the character set whenever reading a text file.<\/li>\n
  3. Thou shalt not refer to any 8-bit character set as \u201cASCII\u201d.<\/li>\n
  4. Thou shalt ensure that all string handling functions fully support characters from beyond the Basic Multilingual Plane. Thou shalt not refer to Unicode as a two-byte character set.<\/li>\n
  5. Thou shalt plan for additions of future characters to Unicode.<\/li>\n
  6. Thou shalt count and index Unicode characters, not UTF-16 code points.<\/li>\n
  7. Thou shalt use UTF-8 as the preferred encoding wherever possible.<\/li>\n
  8. Thou shalt generate all text in Normalization Form C whenever possible.<\/li>\n
  9. Thou shalt avoid deprecated characters.<\/li>\n
  10. Thou shalt steer clear of the private use area.<\/li>\n<\/ol>\n

    Da schlie\u00dfen sich nun einige Fragen an, die es zu kl\u00e4ren gilt:<\/p>\n