[Om2008.9] Spanish Illume keyboard

[Pander]

Rasterman, how can I use a real space or an empty string for the space
bar? Because space is considered a white space character it is not
picked up to be displayed on a key.

Is it good practise if I use Unicode C2 A0, i.e. no-break space? Or are
there other ways to not label a key? E.g. refering to a non-exinting
.png? What is best practise regarding this?

Reason for doing this, is that in my language we use another word for
space (spatie) but I would like to omit the label on the space bar entirely.


Carsten Haitzler (The Rasterman) wrote:
> On Fri, 2 Jan 2009 21:00:36 +1100 Carsten Haitzler (The Rasterman)
> <raster at rasterman.com> babbled:
> 
> gah! replying to myself.. found out why...
> 
> you file was NOT UTF-8~ it was iso8859! no no! MUST BE UTF-8!
> 
> attached fixed file - in utf8. works fine.
> 
> now.. spank! make sure you use utf8! :) (heathens still using iso8859!!!) :)
> 
>> On Fri, 2 Jan 2009 07:21:52 +0100 Matthias Apitz <guru at unixarea.de> babbled:
>>
>> ok for some bizarre reason.. you've hit on some sscanf parsing bug. either i
>> need a spank for not understanding it... or it has problems with utf8 char
>> sequences that it didnt have with the numbers.kbd. as soon as it sees the
>> accute accent chars it doesnt bother doing anything right.
>>
>>              if (sscanf(buf, "%*s %4000s", label) != 1) continue;
>>
>> skips the "normal/shift/capslock" identifier and goes to find the label string
>> - skipping whitespace between. or it SHOULD and scan up to 4000chars (silly
>> high limit) for the label  it gets even this wrong and starts to return
>> garbage strings like delete char. all in all it ends up producing some nasty
>> garbage that then gets fed into the stringshare db... and its only on the
>> keys you added. the rest parses fine (the Numbers.kbd). despite this also
>> having utf8 char sequences. so right now.. i really am a bit baffled as to
>> why - but there is some parsing/sscanf issue i have to hunt down - or work
>> around.
>>
>> (yes - i used scanf to parse... i was feeling lazy!). but as such your extra
>> keys on top SHOULD look like this:
>>
>> key  45    0  30  30
>>   normal   ¿  "¿"
>>   shift    ¿  "¿"
>>   capslock ¿  "¿"
>> key  75    0  30  30
>>   normal   á  "á"
>>   shift    Á  "Á"
>>   capslock Á  "Á"
>> key 105    0  30  30
>>   normal   é  "é"
>>   shift    É  "É"
>>   capslock É  "É"
>> key 135    0  30  30
>>   normal   í  "í"
>>   shift    Í  "Í"
>>   capslock Í  "Í"
>> key 165    0  30  30
>>   normal   ñ  "ñ"
>>   shift    Ñ  "Ñ"
>>   capslock Ñ  "Ñ"
>> key 195    0  30  30
>>   normal   ó  "ó"
>>   shift    Ó  "Ó"
>>   capslock Ó  "Ó"
>> key 225    0  30  30
>>   normal   ú  "ú"
>>   shift    Ú  "Ú"
>>   capslock Ú  "Ú"
>> key 255    0  30  30
>>   normal   ü  "ü"
>>   shift    Ü  "Ü"
>>   capslock Ü  "Ü"
>> key 285    0  30  30
>>   normal   ¡  "¡"
>>   shift    ¡  "¡"
>>   capslock ¡  "¡"
>>
>> pretty simple - and it'd work. if there wasnt this bizarre parsing thing. the
>> other keys in Numbers.kbd work fine... so i'm rather bemused...
>>
>>> El día Friday, January 02, 2009 a las 11:30:51AM +1100, Carsten Haitzler
>>> escribió:
>>>
>>>>> I've changed it this way (example):
>>>>>
>>>>> key  75    0  30  30
>>>>>   normal   á  aacute
>>>>>   shift    Á  0x0c1
>>>>>   capslock Á  0x0c1
>>>>>
>>>>> i.e. used only 0x.. values for shift/caps; now a click on Á while
>>>>> shift/caps is active, gives no char at all :-(
>>>>>
>>>>> lo siento; without a correct syntax description of the file *.kdb all is
>>>>> only guessing arround; where I can find the full syntax of the file?
>>>> leave it in strings. look at the Numbers.kbd - it has numbers and accented
>>>> chars - including acute/grave etc. versions. just leave it in quotes as a
>>>> string and it will get mapped properly.
>>> Hello Carsten,
>>>
>>> First at all, thx for your tip, but ...
>>>
>>> Numbers.kdb has no acute-chars:
>>>
>>> root at om-gta02:/usr/lib/enlightenment/modules/illume/keyboards# fgrep -i
>>> acute Numbers.kbd
>>> root at om-gta02:/usr/lib/enlightenment/modules/illume/keyboards# 
>>>
>>> attached is my version of Spanish.kbd; it just does not work (after
>>> Xserver restart) for the CAPS chars; the CAPS'ed chars give the same
>>> small version of the chars; please be so kind and check it out
>>> in your FR; thx in advance;
>>>
>>> I have also checked putting the values in "", i.e. like "Aacute"; this
>>> results in some kind of dictionary lookups;
>>>
>>> thx for your help and time in advance;
>>>
>>> 	matthias
>>>
>>> -- 
>>> Matthias Apitz
>>> Manager Technical Support - OCLC GmbH
>>> Gruenwalder Weg 28g - 82041 Oberhaching - Germany
>>> t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211
>>> e <matthias.apitz at oclc.org> - w http://www.oclc.org/ http://www.UnixArea.de/
>>> b http://gurucubano.blogspot.com/
>>>
>>> SPAMer of the year: Subject: Alle Software ist Deutsche Sprachen
>>>> From: -40 % die Neujahrsaktion <GabrielleKelley at grungecafe.com>
>>
>> -- 
>> ------------- Codito, ergo sum - "I code, therefore I am" --------------
>> The Rasterman (Carsten Haitzler)    raster at rasterman.com
>>
>>
>> _______________________________________________
>> Openmoko community mailing list
>> community at lists.openmoko.org
>> http://lists.openmoko.org/mailman/listinfo/community
> 
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Openmoko community mailing list
> community at lists.openmoko.org
> http://lists.openmoko.org/mailman/listinfo/community