unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: lumarzeli30@gmail.com
Cc: 55529@debbugs.gnu.org
Subject: bug#55529: [PATCH] Add support for the Tagalog script
Date: Sat, 21 May 2022 12:38:46 +0300	[thread overview]
Message-ID: <83v8tz8btl.fsf@gnu.org> (raw)
In-Reply-To: <834k1j9tw8.fsf@gnu.org> (message from Eli Zaretskii on Sat, 21 May 2022 11:23:03 +0300)

> Cc: 55529@debbugs.gnu.org
> Date: Sat, 21 May 2022 11:23:03 +0300
> From: Eli Zaretskii <eliz@gnu.org>
> 
> >  Looking at this another way: what will an Emacs user expect to find in
> >  Emacs as the supported language for the Philippines?
> > 
> > Atleast according to me, correct me if I am  a filipino user will use the Roman script for the filipino language,
> > while writing Tagalog he may look for Baybayin, which we
> > have provided under the Tagalog language environment.
> 
> OK, but please revise the doc strings and the comments to make sure we
> use "Tagalog" for the language and "Baybayin" for the script (except
> where we use the script name inherited from Unicode, which is actually
> the name of the Unicode block).  AFAICT, the patch you posted wasn't
> consistent in that regard.  And NEWS should mention both the language
> and the script names.

Btw, what fonts are considered to be good nowadays for displaying
Tagalog/Baybayin?





  reply	other threads:[~2022-05-21  9:38 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-19 22:13 bug#55529: [PATCH] Add support for the Tagalog script समीर सिंह Sameer Singh
2022-05-20 14:23 ` Eli Zaretskii
2022-05-20 15:44   ` समीर सिंह Sameer Singh
2022-05-20 16:07     ` Eli Zaretskii
2022-05-20 16:31       ` समीर सिंह Sameer Singh
2022-05-21  8:23         ` Eli Zaretskii
2022-05-21  9:38           ` Eli Zaretskii [this message]
2022-05-21 15:08             ` समीर सिंह Sameer Singh
2022-05-21 15:43               ` समीर सिंह Sameer Singh
2022-05-22  7:24                 ` Eli Zaretskii
2022-05-22  7:28                   ` समीर सिंह Sameer Singh

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=83v8tz8btl.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=55529@debbugs.gnu.org \
    --cc=lumarzeli30@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.
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).