[kbd] U+f000 and above

[kbd] U+f000 and above

[Michael Schutte]

[-- Attachment #1: Type: text/plain, Size: 390 bytes --]

Alexey,

Do you agree with me that it would make sense to make loadkeys fail (or
at least warn the user) on U+xxxx keysym specifications >= 0xf000?
Currently, these will simply be seen by the kernel as non-Unicode syms,
which is confusing at best.

As far as I can tell, there are no widespread keymap files which use
this feature.

Cheers,
-- 
Michael Schutte <michi@uiae.at>

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 489 bytes --]

Re: [kbd] U+f000 and above

[Alexey Gladkov]

Michael Schutte wrote:
> Alexey,
> 
> Do you agree with me that it would make sense to make loadkeys fail (or
> at least warn the user) on U+xxxx keysym specifications >= 0xf000?

I agree. This is a good idea.

-- 
Rgrds, legion

Re: [kbd] U+f000 and above

[Michael Schutte]

[-- Attachment #1: Type: text/plain, Size: 1116 bytes --]

On Mon, Nov 10, 2008 at 05:54:52PM +0300, Alexey Gladkov wrote:
>> Do you agree with me that it would make sense to make loadkeys fail (or
>> at least warn the user) on U+xxxx keysym specifications >= 0xf000?
>
> I agree. This is a good idea.

Okay then, this does the trick:

diff --git a/src/analyze.l b/src/analyze.l
index f55c676..392c9aa 100644
--- a/src/analyze.l
+++ b/src/analyze.l
@@ -90,7 +90,7 @@ To                      to|To|TO
 \-                     {return(DASH);}
 \,                     {return(COMMA);}
 \+                     {return(PLUS);}
-{Unicode}              {yylval=strtol(yytext+1,NULL,16);return(UNUMBER);}
+{Unicode}              {yylval=strtol(yytext+1,NULL,16);if(yylval>=0xf000)lkfatal1("unicode keysym out of range: %s",yytext);return(UNUMBER);}
 {Decimal}|{Octal}|{Hex}        {yylval=strtol(yytext,NULL,0);return(NUMBER);}
 <RVALUE>{Literal}      {return((yylval=ksymtocode(yytext))==-1?ERROR:LITERAL);}

Sorry for the ugliness, I just sticked to the prevailing coding style in
analyze.l.  Re-format as you wish :-)

-- 
Michael Schutte <michi@uiae.at>

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 489 bytes --]

Re: [kbd] U+f000 and above

[Alexey Gladkov]

Michael Schutte wrote:
> Sorry for the ugliness, I just sticked to the prevailing coding style in
> analyze.l.  Re-format as you wish :-)

Applied, thanks!

-- 
Rgrds, legion

Re: [kbd] U+f000 and above

[Alexey Gladkov]

On Fri, Mar 19, 2021 at 06:54:12PM -0500, Pooya Taherkhani wrote:
> Hi there,
> 
> I cannot load Farsi keymap because a decision was made here:
> 
> https://lists.altlinux.org/mailman/listinfo/kbd
> 
> to prevent it from loading.  Interestingly, a secondary reason cited by
> Michael Schutte to prevent the Farsi keyboard from loading is (from link
> above):
> 
> As far as I can tell, there are no widespread keymap files which use
> this feature.
> 
> 
> I'd greatly appreciate it if anybody could direct me to some instructions
> on how to load Farsi keyboard.
> 
> Here is the command that I enter and the error I get:
> 
> [pooya@thinkpad ~] sudo loadkeys fa
> [sudo] password for pooya:
> unicode keysym out of range: U+FDFC
> syntax error, unexpected ERROR, expecting NUMBER or LITERAL or PLUS or
> UNUMBER

The keymap you are trying to load is not valid. The linux kernel cannot
handle keysym greater than 0xf000. You need to fix this and then the
keymap will load.

-- 
Rgrds, legion

Re: [kbd] U+f000 and above

[Random832]

On Sat, Mar 20, 2021, at 05:28, Alexey Gladkov wrote:
> The keymap you are trying to load is not valid. The linux kernel cannot
> handle keysym greater than 0xf000. You need to fix this and then the
> keymap will load.

What exactly is the correct way to define a keyboard that uses characters in the valid Unicode range above U+F900?

Re: [kbd] U+f000 and above

[Alexey Gladkov]

On Sat, Mar 20, 2021 at 09:31:41AM -0400, Random832 wrote:
> On Sat, Mar 20, 2021, at 05:28, Alexey Gladkov wrote:
> > The keymap you are trying to load is not valid. The linux kernel cannot
> > handle keysym greater than 0xf000. You need to fix this and then the
> > keymap will load.
> 
> What exactly is the correct way to define a keyboard that uses
> characters in the valid Unicode range above U+F900?

Where is no way to use keysym above U+F000.

-- 
Rgrds, legion

Re: [kbd] U+f000 and above

[Alexey Gladkov]

On Sat, Mar 20, 2021 at 05:30:49PM -0500, Pooya Taherkhani wrote:
> Alexay,
> 
> Thanks for your response.  I used to have Farsi keyboard on Linux Ubuntu,
> but now I am not sure if there is any Frasi keyboard other than the "fa"
> keymap that works on Arch Linux.
> 
> Could you point me to where to start if I want to fix the "fa" keymap?

You just need to find all unicode symbols greater than 0xf000 in the "fa"
keymap and replace them with something below that limit.

> 
> On Saturday, March 20, 2021, Alexey Gladkov <gladkov.alexey@gmail.com>
> wrote:
> 
> > On Fri, Mar 19, 2021 at 06:54:12PM -0500, Pooya Taherkhani wrote:
> > > Hi there,
> > >
> > > I cannot load Farsi keymap because a decision was made here:
> > >
> > > https://lists.altlinux.org/mailman/listinfo/kbd
> > >
> > > to prevent it from loading.  Interestingly, a secondary reason cited by
> > > Michael Schutte to prevent the Farsi keyboard from loading is (from link
> > > above):
> > >
> > > As far as I can tell, there are no widespread keymap files which use
> > > this feature.
> > >
> > >
> > > I'd greatly appreciate it if anybody could direct me to some instructions
> > > on how to load Farsi keyboard.
> > >
> > > Here is the command that I enter and the error I get:
> > >
> > > [pooya@thinkpad ~] sudo loadkeys fa
> > > [sudo] password for pooya:
> > > unicode keysym out of range: U+FDFC
> > > syntax error, unexpected ERROR, expecting NUMBER or LITERAL or PLUS or
> > > UNUMBER
> >
> > The keymap you are trying to load is not valid. The linux kernel cannot
> > handle keysym greater than 0xf000. You need to fix this and then the
> > keymap will load.
> >
> > --
> > Rgrds, legion
> >
> >

-- 
Rgrds, legion