[Trac #418] Keyboard layout collector ticket.

[Zarro Boogs per Child]

#418: Keyboard layout collector ticket.
-----------------------+----------------------------------------------------
 Reporter:  jg         |        Owner:  warp   
     Type:  defect     |       Status:  new    
 Priority:  blocker    |    Milestone:  BTest-2
Component:  keyboards  |   Resolution:         
 Keywords:             |  
-----------------------+----------------------------------------------------
Changes (by jg):

  * milestone:  BTest-1b => BTest-2

Comment:

 It strikes me as having one unified keyboard representation from which
 everything gets derived is about the only sane way for us to go, given the
 number of layouts we are likely to need.  Reconciling the different
 representations will drive us nuts.

 I don't care much if it is a spreadsheet or if it is xkb description
 files; there should in any case be a single master, and that master needs
 to be capable of expressing everything needed for keyboards.
 Note this goes beyond simple situations like that described above, but
 also involves accessibility issues (e.g. "sticky keys"), and also keyboard
 geometry (for now, very easy for us to do one file, but we'll have this
 problem in the future).

 Otherwise, the generation of keyboards is going to become a perpetual
 nightmare.

-- 
Ticket URL: <http://dev.laptop.org/ticket/418#comment:9>
One Laptop Per Child <http://laptop.org/>