#6280 HIGH Future : Keyboard creates non-standard accents

Zarro Boogs per Child bugtracker at laptop.org
Fri Feb 8 04:30:52 EST 2008


#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):

 Replying to [comment:4 walter]:
 > Which keyboard? Each one is configured differently. On some keyboards we
 used dead keys. On others, we use Unicode combining characters. The former
 does not cover the full extent of characters we need for some languages.
 The latter doesn't automatically convert to single Unicode characters. We
 could add all of the missing dead keys to X, if someone wants to take that
 project on.

 US International has problems.

 You have two workable choices:

 1. Use dead keys and/or AltGr as an extra modifier. Note that you can
 still emit multiple Unicode characters as required, allowing support for
 everything outside CJK. The u-umlaut must be one character, but a @-umlaut
 probably can't be.

 2. Use a full input method system, which is really just a heavy-duty
 version of the above. (this may involve a tooltip-like pop up showing
 character choices, etc.)

 The requirement for combining characters does not mean that the keyboard
 needs to transmit them as if they were wholly independant characters. They
 can and should be considered as an inseparable part of a whole. The
 requirement for combining characters on some symbols does not mean that
 combining characters can or should be used elsewhere.

 There should not be any way (outside of hexadecimal entry) to type a loose
 combining character.

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



More information about the Bugs mailing list