Re: [Om2008.9] Spanish Illume keyboard (was: Call for Illume keyboardsand keyboard icons)
On Fri, 2 Jan 2009 07:21:52 +0100 Matthias Apitz g...@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 450 30 30 normal ¿ ¿ shift¿ ¿ capslock ¿ ¿ key 750 30 30 normal á á shiftÁ Á capslock Á Á key 1050 30 30 normal é é shiftÉ É capslock É É key 1350 30 30 normal í í shiftÍ Í capslock Í Í key 1650 30 30 normal ñ ñ shiftÑ Ñ capslock Ñ Ñ key 1950 30 30 normal ó ó shiftÓ Ó capslock Ó Ó key 2250 30 30 normal ú ú shiftÚ Ú capslock Ú Ú key 2550 30 30 normal ü ü shiftÜ Ü capslock Ü Ü key 2850 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 750 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: r...@om-gta02:/usr/lib/enlightenment/modules/illume/keyboards# fgrep -i acute Numbers.kbd r...@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.ap...@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 gabriellekel...@grungecafe.com -- - Codito, ergo sum - I code, therefore I am -- The Rasterman (Carsten Haitzler)ras...@rasterman.com ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [Om2008.9] Spanish Illume keyboard (was: Call for Illume keyboardsand keyboard icons)
On Fri, 2 Jan 2009 21:00:36 +1100 Carsten Haitzler (The Rasterman) ras...@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 g...@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 450 30 30 normal ¿ ¿ shift¿ ¿ capslock ¿ ¿ key 750 30 30 normal á á shiftÁ Á capslock Á Á key 1050 30 30 normal é é shiftÉ É capslock É É key 1350 30 30 normal í í shiftÍ Í capslock Í Í key 1650 30 30 normal ñ ñ shiftÑ Ñ capslock Ñ Ñ key 1950 30 30 normal ó ó shiftÓ Ó capslock Ó Ó key 2250 30 30 normal ú ú shiftÚ Ú capslock Ú Ú key 2550 30 30 normal ü ü shiftÜ Ü capslock Ü Ü key 2850 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 750 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: r...@om-gta02:/usr/lib/enlightenment/modules/illume/keyboards# fgrep -i acute Numbers.kbd r...@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.ap...@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 gabriellekel...@grungecafe.com -- - Codito, ergo sum - I code, therefore I am -- The Rasterman (Carsten Haitzler)ras...@rasterman.com ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community -- - Codito, ergo sum - I code, therefore I am -- The Rasterman (Carsten Haitzler)ras...@rasterman.com Spanish.kbd Description: Binary data ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [Om2008.9] Spanish Illume keyboard (was: Call for Illume keyboardsand keyboard icons)
El día Friday, January 02, 2009 a las 09:00:36PM +1100, Carsten Haitzler escribió: On Fri, 2 Jan 2009 07:21:52 +0100 Matthias Apitz g...@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 450 30 30 normal ¿ ¿ shift¿ ¿ capslock ¿ ¿ key 750 30 30 normal á á shiftÁ Á capslock Á Á ... putting the chars into quotes has the side effect that if you hit the char in the keyboard it is selected and printed above the top row of the keyboard and waiting for completion as a word; even the capitals are correctly printed on this line; but if you then touch the char (or word) to confirm it, it gets moved above wrong, as small letter for example; I also don't want that behaviour, they should be moved directly to the messages and not waiting for further assembling/completion; isn't this caused by the as I understand some comment in Numbers.kbd? Thx 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.ap...@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 gabriellekel...@grungecafe.com ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [Om2008.9] Spanish Illume keyboard (was: Call for Illume keyboardsand keyboard icons)
On Fri, Jan 02, 2009 at 09:12:43PM +1100, Carsten Haitzler wrote: now.. spank! make sure you use utf8! :) (heathens still using iso8859!!!) :) Each time a non UTF8 encoding is used, a kitten dies! Rui -- P'tang! Today is Boomtime, the 2nd day of Chaos in the YOLD 3175 + No matter how much you do, you never do enough -- unknown + Whatever you do will be insignificant, | but it is very important that you do it -- Gandhi + So let's do it...? ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [Om2008.9] Spanish Illume keyboard (was: Call for Illume keyboardsand keyboard icons)
El día Friday, January 02, 2009 a las 09:12:43PM +1100, Carsten Haitzler escribió: On Fri, 2 Jan 2009 21:00:36 +1100 Carsten Haitzler (The Rasterman) ras...@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. Nop. I've installed your file and restarted the Xserver; if you select CAPS mode, then hit the capital Ñ (Ntilde) it appears as capital Ñ in the line and waits for further completion, if you now hit this Ñ it is moved to the SMS buffer as small ñ (ntilde). 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.ap...@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 gabriellekel...@grungecafe.com ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [Om2008.9] Spanish Illume keyboard (was: Call for Illume keyboardsand keyboard icons)
On Fri, 2 Jan 2009 11:28:17 +0100 Matthias Apitz g...@unixarea.de babbled: El día Friday, January 02, 2009 a las 09:12:43PM +1100, Carsten Haitzler escribió: On Fri, 2 Jan 2009 21:00:36 +1100 Carsten Haitzler (The Rasterman) ras...@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. Nop. I've installed your file and restarted the Xserver; if you select CAPS mode, then hit the capital Ñ (Ntilde) it appears as capital Ñ in the line and waits for further completion, if you now hit this Ñ it is moved to the SMS buffer as small ñ (ntilde). i'm getting capitals.. actually ok - the 2nd time i do it it is. not the first. i think the utf8 normalization that florian did has some issues i think. and yes - it you use quotes it goes via the dictionary lookup and works better - the problem is needing to know what shift plus the 'ñ' key does. as such the code does a lookup of keyboard maps - for keymaps that have a/A on a key this works. as does 4/$ etc. for shift and caps - the problem is.. you have no keyboard with normal ñ key - and thus x doesn't KNOW that shift + ñ == Ñ - it has no idea, so you get a small. the string version can encode the capitalisation but simply shift + keysym doesnt end up producing a capitalised version in x's view of the keyboard world. (unlike shift + a == A). so now illume needs a hard-coded table of this stuff that x doesn't know to basically bypass x. and as such such a table or infra doesn't exist - so you're stuck until it does. x's internal table doesnt have this. :) -- - Codito, ergo sum - I code, therefore I am -- The Rasterman (Carsten Haitzler)ras...@rasterman.com ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [Om2008.9] Spanish Illume keyboard
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) ras...@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 g...@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 450 30 30 normal ¿ ¿ shift¿ ¿ capslock ¿ ¿ key 750 30 30 normal á á shiftÁ Á capslock Á Á key 1050 30 30 normal é é shiftÉ É capslock É É key 1350 30 30 normal í í shiftÍ Í capslock Í Í key 1650 30 30 normal ñ ñ shiftÑ Ñ capslock Ñ Ñ key 1950 30 30 normal ó ó shiftÓ Ó capslock Ó Ó key 2250 30 30 normal ú ú shiftÚ Ú capslock Ú Ú key 2550 30 30 normal ü ü shiftÜ Ü capslock Ü Ü key 2850 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 750 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: r...@om-gta02:/usr/lib/enlightenment/modules/illume/keyboards# fgrep -i acute Numbers.kbd r...@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.ap...@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 gabriellekel...@grungecafe.com -- - Codito, ergo sum - I code, therefore I am -- The Rasterman (Carsten Haitzler)ras...@rasterman.com ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [Om2008.9] Spanish Illume keyboard
On Fri, 02 Jan 2009 12:38:46 +0100 Pander pan...@users.sourceforge.net babbled: 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. space (the keysym name) :) Is it good practise if I use Unicode C2 A0, i.e. no-break space? Or are no. this will be useless. if you want space - use space. if you want a space that is used while composing words (actually wont work as the dict format wont support it) use (a space in quotes). :) there other ways to not label a key? E.g. refering to a non-exinting .png? What is best practise regarding this? oooh wait the LABEL - empty png :) i chose not to bother with this as its a single-case (spacebar) where you want it and an empty png will do the job - or non-existant one too :) 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. as above :) Carsten Haitzler (The Rasterman) wrote: On Fri, 2 Jan 2009 21:00:36 +1100 Carsten Haitzler (The Rasterman) ras...@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 g...@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 450 30 30 normal ¿ ¿ shift¿ ¿ capslock ¿ ¿ key 750 30 30 normal á á shiftÁ Á capslock Á Á key 1050 30 30 normal é é shiftÉ É capslock É É key 1350 30 30 normal í í shiftÍ Í capslock Í Í key 1650 30 30 normal ñ ñ shiftÑ Ñ capslock Ñ Ñ key 1950 30 30 normal ó ó shiftÓ Ó capslock Ó Ó key 2250 30 30 normal ú ú shiftÚ Ú capslock Ú Ú key 2550 30 30 normal ü ü shiftÜ Ü capslock Ü Ü key 2850 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 750 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: r...@om-gta02:/usr/lib/enlightenment/modules/illume/keyboards# fgrep -i acute Numbers.kbd r...@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
Re: [Om2008.9] Spanish Illume keyboard (was: Call for Illume keyboardsand keyboard icons)
El día Friday, January 02, 2009 a las 10:30:19PM +1100, Carsten Haitzler escribió: On Fri, 2 Jan 2009 11:28:17 +0100 Matthias Apitz g...@unixarea.de babbled: El día Friday, January 02, 2009 a las 09:12:43PM +1100, Carsten Haitzler escribió: On Fri, 2 Jan 2009 21:00:36 +1100 Carsten Haitzler (The Rasterman) ras...@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. Nop. I've installed your file and restarted the Xserver; if you select CAPS mode, then hit the capital Ñ (Ntilde) it appears as capital Ñ in the line and waits for further completion, if you now hit this Ñ it is moved to the SMS buffer as small ñ (ntilde). i'm getting capitals.. actually ok - the 2nd time i do it it is. not the first. i think the utf8 normalization that florian did has some issues i think. For me it does not work; I've marked in CAPS mode 5x the Ñ which gives a word of Ñ, as you see in http://www.sisis.de/~guru/OMkbd/Screenshot-25.png then I touch this word and it is moved to the SMS buffer as (small) ñ, as you see here http://www.sisis.de/~guru/OMkbd/Screenshot-26.png do you want me to file a bug report? where? in OM or Illume? and yes - it you use quotes it goes via the dictionary lookup and works better - the problem is needing to know what shift plus the 'ñ' key does. as such the code does a lookup of keyboard maps - for keymaps that have a/A on a key this works. as does 4/$ etc. for shift and caps - the problem is.. you have no keyboard with normal ñ key - and thus x doesn't KNOW that shift + ñ == Ñ - it has no idea, so you get a small. the string version can encode the capitalisation but simply shift + keysym doesnt end up producing a capitalised version in x's view of the keyboard world. (unlike shift + a == A). so now illume needs a hard-coded table of this stuff that x doesn't know to basically bypass x. and as such such a table or infra doesn't exist - so you're stuck until it does. x's internal table doesnt have this. :) I was as well looking for a better solution, like the one I have on my FreeBSD laptop whith X11+KDE; I'm re-using the WINDOWS key with a script like this: $ cat xmod.sh # para español / for Spanish # xmodmap -e keycode 0x73 = Mode_switch xmodmap -e keycode 0x39 = n N ntilde Ntilde xmodmap -e keycode 0x1a = e E eacute Eacute xmodmap -e keycode 0x26 = a A aacute Aacute xmodmap -e keycode 0x1f = i I iacute Iacute xmodmap -e keycode 0x1e = u U uacute Uacute xmodmap -e keycode 0x20 = o O oacute Oacute xmodmap -e keycode 0x14 = questiondown question backslash ssharp xmodmap -e keycode 0x0a = 1 exclam exclamdown onesuperior and all is fine, *all* X11 clients get the correct Spanish chars using WINDOWSkey + n -- ñ SHIFT+WINDOWSkey + n -- Ñ and so on... I think, this would be the correct way to do that, and of course without any diccionary lookup; just re-mapping (xmodmap) keycode NUMBER to KEYSYMNAME(s); can we have this in OM+Illume too? would be nice; for the moment I can live having at least the small Spanish chars :-) the Spanish Writing Rules of RAE (The Real Spain Academy) claims that on writing the capital chars, they must not, but can, be tilded. So, from that point of view RAE all is fine now; Thx 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.ap...@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 gabriellekel...@grungecafe.com ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
[Om2008.9] Spanish Illume keyboard (was: Call for Illume keyboards and keyboard icons)
Hello, I've followed the hints in http://wiki.openmoko.org/wiki/Illume#List_of_illume_keyboards and have created a new keyboard file Spanish.kbd as this: http://www.sisis.de/~guru/OMkbd/Spanish.kbd and have some minor problems, maybe only some misunderstanding of the keyboard file syntax/rules; to make life easy on keying in the Spanish tilde chars (without requesting for every char with a tilde to press an additional modifier key) I've just created a new row of keys as you can see here: http://www.sisis.de/~guru/OMkbd/Screenshot-20.png having the keys for: ¡ á é í ñ ó ú ü ¡ the problem is that with the new (bigger) definition of the keyboard size of kbd 450 180 the last row of keys (ctrl alt space ) becomes half invisible and unusable; I have had to use 'kbd 450 190' to get the full working keyboard on the screen, like you see it here: http://www.sisis.de/~guru/OMkbd/Screenshot-21.png why is this? so far so good; the small keys are working fine as you see in the screen; I launched the composer of a SMS and typed in from left to right the keys of the 1st row; see Screenshot-21.png; Then I tested them together with CAPS-LOCK, the image switched fine on pressing CAPS-LOCK and is showing the capital chars, see here: http://www.sisis.de/~guru/OMkbd/Screenshot-22.png but keying in the chars, three times and always from left to right, give random(!) results and you may see in the 2nd line of the SMS; what is the reason of this? Thanks 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.ap...@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 gabriellekel...@grungecafe.com ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
RE: [Om2008.9] Spanish Illume keyboard (was: Call for Illume keyboardsand keyboard icons)
Hello, Matthias. Thanks for that Spanish keyboard. I have no idea why you have that strange behavior. The only differences I see between your new row at the top and the other rows are: - it does not begin at x = 0, - it does not reach the right border of the keyboard - it does not follow the honeycomb model: http://w3.antd.nist.gov/wctg/netanal/honeycomb.gif I would copy one of the existing rows (for example [TAB] Q W E R T Y ... ) and then set the y coordinate value to zero and see what happens. Regards, Lucas De: community-boun...@lists.openmoko.org en nombre de Matthias Apitz Enviado el: jue 01/01/2009 11:29 Para: List for Openmoko community discussion Asunto: [Om2008.9] Spanish Illume keyboard (was: Call for Illume keyboardsand keyboard icons) Hello, I've followed the hints in http://wiki.openmoko.org/wiki/Illume#List_of_illume_keyboards and have created a new keyboard file Spanish.kbd as this: http://www.sisis.de/~guru/OMkbd/Spanish.kbd and have some minor problems, maybe only some misunderstanding of the keyboard file syntax/rules; to make life easy on keying in the Spanish tilde chars (without requesting for every char with a tilde to press an additional modifier key) I've just created a new row of keys as you can see here: http://www.sisis.de/~guru/OMkbd/Screenshot-20.png having the keys for: ¡ á é í ñ ó ú ü ¡ the problem is that with the new (bigger) definition of the keyboard size of kbd 450 180 the last row of keys (ctrl alt space ) becomes half invisible and unusable; I have had to use 'kbd 450 190' to get the full working keyboard on the screen, like you see it here: http://www.sisis.de/~guru/OMkbd/Screenshot-21.png why is this? so far so good; the small keys are working fine as you see in the screen; I launched the composer of a SMS and typed in from left to right the keys of the 1st row; see Screenshot-21.png; Then I tested them together with CAPS-LOCK, the image switched fine on pressing CAPS-LOCK and is showing the capital chars, see here: http://www.sisis.de/~guru/OMkbd/Screenshot-22.png but keying in the chars, three times and always from left to right, give random(!) results and you may see in the 2nd line of the SMS; what is the reason of this? Thanks 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.ap...@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 gabriellekel...@grungecafe.com ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [Om2008.9] Spanish Illume keyboard (was: Call for Illume keyboardsand keyboard icons)
El día Thursday, January 01, 2009 a las 12:26:57PM +0100, Juan Lucas Dominguez Rubio escribió: Hello, Matthias. Thanks for that Spanish keyboard. I have no idea why you have that strange behavior. The only differences I see between your new row at the top and the other rows are: - it does not begin at x = 0, - it does not reach the right border of the keyboard - it does not follow the honeycomb model: http://w3.antd.nist.gov/wctg/netanal/honeycomb.gif I would copy one of the existing rows (for example [TAB] Q W E R T Y ... ) and then set the y coordinate value to zero and see what happens. Hola, I followed your hint and copied over the [TAB] Q W E R T Y ... as first row (changing the y coordinate to zero) and it works fine, in 'normal' and 'caps' mode, as you may see here: http://www.sisis.de/~guru/OMkbd/Screenshot-23.png Then I changed the chars to the Spanish tilde chars, for example: key 45 0 30 30 normal ¿ questiondown shift? question capslock ? question key 75 0 30 30 normal á aacute shiftÁ Aacute capslock Á Aacute and so on, letting there the remainin chars, as you see in http://www.sisis.de/~guru/OMkbd/Screenshot-24.png as before, the 'normal' keyes are working as they should, the 'caps' keyes give wrong result; if one only HUP the 'enlightenment' processes, the result is more or less random, if one starts the Xserver new, the result stays in the small letter; I think there is a bug in interpreting the file (or the values like 'Eacute', ...), and for the moment we have to live with letras minúsculas (small letters) only for the moment; 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.ap...@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 gabriellekel...@grungecafe.com ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
RE: [Om2008.9] Spanish Illume keyboard (was: Call for Illume keyboardsand keyboard icons)
Hola. This table: http://www.in-ulm.de/~mascheck/X11/keysyms.txt shows a numeric value to the right. Perhaps the keyboard description accepts that too? Like this: normal ¿ 0x0bf Nice Cuban blog, by the way. Regards, Lucas http://www.prodevelop.es/ De: Matthias Apitz [mailto:g...@unixarea.de] Enviado el: jue 01/01/2009 13:42 Para: Juan Lucas Dominguez Rubio CC: List for Openmoko community discussion Asunto: Re: [Om2008.9] Spanish Illume keyboard (was: Call for Illume keyboardsand keyboard icons) El día Thursday, January 01, 2009 a las 12:26:57PM +0100, Juan Lucas Dominguez Rubio escribió: Hello, Matthias. Thanks for that Spanish keyboard. I have no idea why you have that strange behavior. The only differences I see between your new row at the top and the other rows are: - it does not begin at x = 0, - it does not reach the right border of the keyboard - it does not follow the honeycomb model: http://w3.antd.nist.gov/wctg/netanal/honeycomb.gif I would copy one of the existing rows (for example [TAB] Q W E R T Y ... ) and then set the y coordinate value to zero and see what happens. Hola, I followed your hint and copied over the [TAB] Q W E R T Y ... as first row (changing the y coordinate to zero) and it works fine, in 'normal' and 'caps' mode, as you may see here: http://www.sisis.de/~guru/OMkbd/Screenshot-23.png Then I changed the chars to the Spanish tilde chars, for example: key 45 0 30 30 normal ¿ questiondown shift? question capslock ? question key 75 0 30 30 normal á aacute shiftÁ Aacute capslock Á Aacute and so on, letting there the remainin chars, as you see in http://www.sisis.de/~guru/OMkbd/Screenshot-24.png as before, the 'normal' keyes are working as they should, the 'caps' keyes give wrong result; if one only HUP the 'enlightenment' processes, the result is more or less random, if one starts the Xserver new, the result stays in the small letter; I think there is a bug in interpreting the file (or the values like 'Eacute', ...), and for the moment we have to live with letras minúsculas (small letters) only for the moment; 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.ap...@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 gabriellekel...@grungecafe.com ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [Om2008.9] Spanish Illume keyboard (was: Call for Illume keyboardsand keyboard icons)
El día Thursday, January 01, 2009 a las 02:45:01PM +0100, Juan Lucas Dominguez Rubio escribió: Hola. This table: http://www.in-ulm.de/~mascheck/X11/keysyms.txt shows a numeric value to the right. Perhaps the keyboard description accepts that too? Like this: normal ¿ 0x0bf Hola, I've changed it this way (example): key 750 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? Nice Cuban blog, by the way. Gracias, pero me falta más tiempo. Thx 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.ap...@oclc.org - w http://www.oclc.org/ http://www.UnixArea.de/ b http://gurucubano.blogspot.com/ ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [Om2008.9] Spanish Illume keyboard (was: Call for Illume keyboardsand keyboard icons)
On Thu, 1 Jan 2009 15:13:42 +0100 Matthias Apitz g...@unixarea.de babbled: El día Thursday, January 01, 2009 a las 02:45:01PM +0100, Juan Lucas Dominguez Rubio escribió: Hola. This table: http://www.in-ulm.de/~mascheck/X11/keysyms.txt shows a numeric value to the right. Perhaps the keyboard description accepts that too? Like this: normal ¿ 0x0bf Hola, I've changed it this way (example): key 750 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. -- - Codito, ergo sum - I code, therefore I am -- The Rasterman (Carsten Haitzler)ras...@rasterman.com ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [Om2008.9] Spanish Illume keyboard (was: Call for Illume keyboardsand keyboard icons)
El día Friday, January 02, 2009 a las 11:30:51AM +1100, Carsten Haitzler
escribió:
I've changed it this way (example):
key 750 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:
r...@om-gta02:/usr/lib/enlightenment/modules/illume/keyboards# fgrep -i acute
Numbers.kbd
r...@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.ap...@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 gabriellekel...@grungecafe.com
##KBDCONF-1.0
kbd 450 190
# keyboard type
type TERMINAL
# an icon for the keyboard so you know which one you have
icon qwerty.png
# added by g...@unixarea.de for Spanish tilde chars
# $Id: Spanish.kbd,v 1.5 2009/01/02 06:05:28 guru Exp $
#
key 450 30 30
normal ¿ questiondown
key 750 30 30
normal á aacute
capslockÁ Aacute
key 1050 30 30
normal é eacute
capslockÉ Eacute
key 1350 30 30
normal í iacute
capslockÍ Iacute
key 1650 30 30
normal ñ ntilde
capslockÑ Ntilde
key 1950 30 30
normal ó oacute
capslockÓ Oacute
key 2250 30 30
normal ú uacute
capslockÚ Uacute
key 2550 30 30
normal ü udiaeresis
capslockÜ Udiaeresis
key 2850 30 30
normal ¡ exclamdown
key 0 30 30 30
normal ` grave
shift~ asciitilde
capslock ` grave
key 30 30 30 30
normal 1 1
shift! exclam
capslock 1 1
key 60 30 30 30
normal 2 2
shift@ at
capslock 2 2
key 90 30 30 30
normal 3 3
shift# numbersign
capslock 3 3
key 120 30 30 30
normal 4 4
shift$ dollar
capslock 4 4
key 150 30 30 30
normal 5 5
shift% percent
capslock 5 5
key 180 30 30 30
normal 6 6
shift^ asciicircum
capslock 6 6
key 210 30 30 30
normal 7 7
shift ampersand
capslock 7 7
key 240 30 30 30
normal 8 8
shift* asterisk
capslock 8 8
key 270 30 30 30
normal 9 9
shift( parenleft
capslock 9 9
key 300 30 30 30
normal 0 0
shift) parenright
capslock 0 0
key 330 30 30 30
normal - minus
shift_ underscore
capslock - minus
key 360 30 30 30
normal = equal
shift+ plus
capslock = equal
key 390 30 60 30
normal backspace.png BackSpace
key 0 60 45 30
normal tab.png Tab
shifttab.png ISO_Left_Tab
key 45 60 30 30
normal q q
shiftQ Q
capslock Q Q
key 75 60 30 30
normal w w
shiftW W
capslock W W
key 105 60 30 30
normal e e
shiftE E
capslock E E
key 135 60 30 30
normal r r
shiftR R
capslock R R
key 165 60 30 30
normal t t
shiftT T
capslock T T
key 195 60 30 30
normal y y
shiftY Y
capslock Y Y
key 225 60 30 30
normal u u
shiftU U
capslock U U
key 255 60 30 30
normal i i
shiftI I
capslock I I
key 285 60 30 30
normal o o
shiftO O
capslock O O
key 315 60 30 30
normal p p
shiftP P
capslock P P
key 345 60 30 30
normal [ bracketleft
shift{ braceleft
capslock [ bracketleft
key 375 60 30 30
normal ] bracketright
shift} braceright
capslock ] bracketright
key 405 60 45 30
normal \ backslash
shift| bar
capslock \ backslash
key 0 90 60 30
normal caps
capslock CAPS
is_capslock
key 60 90 30 30
normal a a
shiftA A
capslock A A
key 90 90 30 30
normal s s
shiftS S
capslock S S
key 120 90 30 30
normal d d
shiftD D
capslock D D
key 150 90 30 30
normal f f
shiftF F
capslock F F
key 180 90 30 30
normal g g
shiftG G
capslock G G
key 210 90 30 30
normal h h
shift
