[ESW Wiki] Update of "geoUnicodeConsiderationsWhenUpgrading" by Deborah Cawkwell

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "ESW Wiki" for change notification.

The following page has been changed by Deborah Cawkwell:
http://esw.w3.org/topic/geoUnicodeConsiderationsWhenUpgrading


The comment on the change is:
UTF-16 for back-end

------------------------------------------------------------------------------
  === Answer ===
  
  ==== Which Unicode encoding for web pages? ====
+ 
+ Unicode is the [http://www.w3.org/International/questions/qa-doc-charset Document Character Set for HTML and XML].
   
  Unicode has three main encodings: UTF-8, UTF-16, UTF-32.
  
@@ -22, +24 @@

  
     * Better compatibility with legacy data, where that legacy data uses ASCII as the 128 codepoints in ASCII match the first 128 codepoints in UTF-8.
     * No byte order problems.
+ 
+ UTF-16 is often used for the system back-end. 
+ 
+ Unicode is the Document Character Set for HTML and XML (link to http://www.w3.org/International/questions/qa-doc-charset)
  
  === How well is Unicode supported for my end users? ===
  
@@ -69, +75 @@

  
  ==== Rendering software ====
  
- Multilingual text rendering engines are built into operating system and browser installation. This is typically needed for '[complex scripts ACTION DC edit multilingual text rendering engines: add Arabic & link to RI additional info on this - http://people.w3.org/rishida/scripts/tutorial/all.html#Slide0430]' such as Arabic, Hindi, Urdu, Persian, ie languages which have characters that change appearance based on their context.
+ Multilingual text rendering engines are built into operating system and browser installation. This is typically needed for '[http://people.w3.org/rishida/scripts/tutorial/all.html#Slide0430 complex scripts]' such as Arabic, Hindi, Urdu, Persian, ie languages which have characters that change appearance based on their context.
  
     * Windows: Uniscribe
     * Macintosh: Apple Type Services for Unicode Imaging, which replaced the WorldScript engine for legacy encodings.
@@ -106, +112 @@

     * [http://www.unicode.org/help/display_problems.html Settings to change to resolve display problems in Unicode]
     * [http://en.wikipedia.org/wiki/Truetype Information about TrueType font]
     * [http://en.wikipedia.org/wiki/Opentype Information about OpenType font]
-    * [http://www.babelstone.co.uk/Fonts/Fonts.html Unicode fonts and specific scripts].
+    * [http://www.babelstone.co.uk/Fonts/Fonts.html Unicode fonts and specific scripts]
+    * [http://people.w3.org/rishida/scripts/tutorial/all.html#Slide0430 complex scripts]
     * [http://www.unicode.org Unicode Consortium]
     * [http://www.w3.org/International/tutorials/tutorial-char-enc Tutorial: Character sets & encodings in XHTML, HTML and CSS]
+    * [http://www.w3.org/International/questions/qa-doc-charset Document Character Set for HTML and XML ]
     * [http://www.alanwood.net/unicode/browsers.html Unicode & multilingual web browsers]
     * [http://en.wikipedia.org/wiki/Unicode_and_HTML Unicode & HTML]

Received on Wednesday, 20 July 2005 14:00:55 UTC