#6280 HIGH Future : Keyboard creates non-standard accents

[Zarro Boogs per Child]

#6280: Keyboard creates non-standard accents
---------------------------------------+------------------------------------
  Reporter:  homunq                    |       Owner:  uwog           
      Type:  defect                    |      Status:  new            
  Priority:  high                      |   Milestone:  Future Release 
 Component:  write-activity (abiword)  |     Version:                 
Resolution:                            |    Keywords:  accents unicode
  Verified:  0                         |    Blocking:                 
 Blockedby:                            |  
---------------------------------------+------------------------------------

Comment(by AlbertCahalan):

 See also:

 Bug #140, where user ianb wisely saw this coming

 Bug #4009, where jhbuild gives pre-composed characters (Normalization Form
 KC, or perhaps C)

 Bug #6125, where the terminal activity and Linux console can't cope

 Such accents also do not work in Tux Paint.

 The root of the problem is the very strange way that the XO keyboard has
 been configured. On a normal system you press the accent first. This sets
 some normally-hidden state in the keyboard driver. (idea: the XO could
 display this on a screen overlay if the state persists for more than 0.5
 seconds) After setting that state, you press the letter. At that point,
 the whole thing is available in the keyboard driver. Assuming the keyboard
 driver is not malicious, it then produces the pre-composed form
 (Normalization Form KC) if possible. The XO is configured to send an
 initial letter immediately, which might or might not then get followed by
 a combining accent at some far-future time.

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