unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Rahguzar <rahguzar@zohomail.eu>
Cc: 66470@debbugs.gnu.org
Subject: bug#66470: 29.1; Provide Urdu input method
Date: Sat, 14 Oct 2023 11:53:21 +0300	[thread overview]
Message-ID: <837cnpshz2.fsf@gnu.org> (raw)
In-Reply-To: <87lec9m12g.fsf@zohomail.eu> (bug-gnu-emacs@gnu.org)

> Cc: rahguzar@zohomail.eu
> Date: Wed, 11 Oct 2023 20:50:33 +0200
> From:  Rahguzar via "Bug reports for GNU Emacs,
>  the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
> 
> Please find attached the patch I mentioned earlier and let me know any changes that need to be made.
> 
> The input method is usable for common Urdu input, but here are some of
> the things I want to improve in addition to what I asked on the
> help-gnu-emacs:

I responded to your question on help-gnu-emacs.

> 1) Better coverage of Urdu zabta takhti
> http://www.unicode.org/L2/L2002/02004-uzt.pdf It is a code page
> developed for Urdu and supposedly was the basis of current Urdu support
> of Unicode. However I can't figure out exactly what is the mapping from
> UZT to Unicode. If anyone has pointers please share.

What are the specific issues you cannot figure out?

Anyway, a better place to ask about Unicode mapping is on the Unicode
mailing list, unicode@corp.unicode.org.

> 2) Another input method for the common Urdu keyboard support. Despite
> Urdu being my mother tongue I never learned to type in it which is why I
> prefer a phonetic keyboard. However I will like to make an input method
> with the layout of a physical Urdu keyboard. If a keyboard layout was
> standardized in Pakistan or India, I can't find the specification. If
> such a document exists and anyone can point me to it, I will be happy to
> use it as a basis for addition to the `urdu.el` in attached patch.
> Otherwise I will use the layout of Urdu keyboard from some free software
> project. But this will probably be closer to Emacs 30 than now.

Does https://www.branah.com/urdu help?

> 
> 3) The key for 'w' is unused in the input method for now. I am tempted
> to bind a version of `insert-char` but restricted to Arabic range of
> Unicode to cover the rare cases not covered by the input method now. Any
> opinions about that?

That key is assigned characters in the above keyboard page.

> >From 8c0fc53efef493e151bd5893d5b5ca7b390b4a6b Mon Sep 17 00:00:00 2001
> From: Rahguzar <rahguzar@zohomail.eu>
> Date: Wed, 11 Oct 2023 20:45:27 +0200
> Subject: [PATCH] Provide an Urdu input method
> 
> ---
>  lisp/leim/quail/urdu.el | 193 ++++++++++++++++++++++++++++++++++++++++
>  1 file changed, 193 insertions(+)
>  create mode 100644 lisp/leim/quail/urdu.el

Thanks, but I'd prefer not to create a new file.  How about adding
this to persian.el instead?

> +(quail-define-package
> + "urdu-phonetic" "Urdu" "اردو صوتی"
> + `((?a . "a → ا , A → آ , ax → أ , u → ع")
> +   (?y . "y → ی , e → ے , i → ئ")
> +   (?r . "r → ر , R → ڑ")

Besides the ` vs ' issue, I doubt that this kind of GUIDANCE is a good
idea.  Emacs input methods have a standardized way of showing
candidates and the keys to select them, so I would prefer to stick to
the standardized guidance format instead.  In particular, showing the
translations of both upper- and lower-case keys is not a good idea, I
think.





  reply	other threads:[~2023-10-14  8:53 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-11 18:36 bug#66470: 29.1; Provide Urdu input method Rahguzar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-11 18:50 ` Rahguzar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-14  8:53   ` Eli Zaretskii [this message]
2023-10-14  9:50     ` Rahguzar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-14 10:53       ` Eli Zaretskii
2023-10-14 11:10         ` Rahguzar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-14 12:36           ` Eli Zaretskii
2023-10-21 18:59             ` Rahguzar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-22  4:53               ` Eli Zaretskii
2023-10-29 11:51               ` Eli Zaretskii
2023-10-29 16:27                 ` Rahguzar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-11-04  8:39                   ` Eli Zaretskii
2023-11-04  8:50                     ` Rahguzar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-11-04  9:27                       ` Eli Zaretskii
2023-11-04 10:56                         ` Rahguzar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-11-04 11:15                           ` Eli Zaretskii
2023-11-04 14:23                             ` Rahguzar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-11-11 10:21                               ` Eli Zaretskii
2023-11-11 11:54                                 ` Rahguzar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-11-18  9:36                                   ` Eli Zaretskii
2023-11-18 11:12                                     ` Rahguzar via Bug reports for GNU Emacs, the Swiss army knife of text editors

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=837cnpshz2.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=66470@debbugs.gnu.org \
    --cc=rahguzar@zohomail.eu \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).