#6125 NORM Future : Nick name is not composed

[Zarro Boogs per Child]

#6125: Nick name is not composed
---------------------+------------------------------------------------------
  Reporter:  bert    |       Owner:  marco         
      Type:  defect  |      Status:  new           
  Priority:  normal  |   Milestone:  Future Release
 Component:  sugar   |     Version:                
Resolution:          |    Keywords:                
  Verified:  0       |    Blocking:                
 Blockedby:          |  
---------------------+------------------------------------------------------

Comment(by AlbertCahalan):

 He's asking you to use Unicode Normalization Form KC. That is the most
 compatible and safe form.

 This has little to do with UTF-8. UTF-8 is a way to represent Unicode
 values. The 'u' with umlaut can be represented as a single Unicode value,
 or as two. Outside of fancy word processors and generic GUI widgets, very
 little software supports representing the character as two separate
 Unicode values.

 As an extra benefit, you can save some space if you use the KC form
 everywhere.

 Note that one must often (not always!) normalize before comparing text.

-- 
Ticket URL: <http://dev.laptop.org/ticket/6125#comment:2>
One Laptop Per Child <http://dev.laptop.org>
OLPC bug tracking system