From: Alexey Gladkov <gladkov.alexey@gmail.com>
To: Pooya Taherkhani <ptaherkhani@gmail.com>
Cc: Linux console tools development discussion <kbd@lists.altlinux.org>
Subject: Re: [kbd] U+f000 and above
Date: Mon, 22 Mar 2021 10:54:34 +0100 [thread overview]
Message-ID: <20210322095434.nitksoqo2bsqyhzg@example.org> (raw)
In-Reply-To: <CACnij5cRGP51cXjMCs8TgnVhFg7TObUquH2q7XnDA0HjY2pknQ@mail.gmail.com>
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
next prev parent reply other threads:[~2021-03-22 9:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CACnij5edOguVuJiYFvvFhfot1SCOAkegxg3gK+kfi7fW4ZDKHA@mail.gmail.com>
2021-03-20 9:28 ` [kbd] U+f000 and above Alexey Gladkov
2021-03-20 13:31 ` Random832
2021-03-20 15:58 ` Alexey Gladkov
[not found] ` <CACnij5cRGP51cXjMCs8TgnVhFg7TObUquH2q7XnDA0HjY2pknQ@mail.gmail.com>
2021-03-22 9:54 ` Alexey Gladkov [this message]
2008-11-09 12:42 Michael Schutte
2008-11-10 14:54 ` Alexey Gladkov
2008-11-12 16:04 ` Michael Schutte
2008-11-18 14:55 ` Alexey Gladkov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210322095434.nitksoqo2bsqyhzg@example.org \
--to=gladkov.alexey@gmail.com \
--cc=kbd@lists.altlinux.org \
--cc=ptaherkhani@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).