From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: =?UTF-8?Q?=E0=A4=B8=E0=A4=AE=E0=A5=80=E0=A4=B0_?= =?UTF-8?Q?=E0=A4=B8=E0=A4=BF=E0=A4=82=E0=A4=B9?= Sameer Singh Newsgroups: gmane.emacs.bugs Subject: bug#55529: [PATCH] Add support for the Tagalog script Date: Sat, 21 May 2022 20:38:05 +0530 Message-ID: References: <83pmk89tbk.fsf@gnu.org> <83k0ag9ohs.fsf@gnu.org> <834k1j9tw8.fsf@gnu.org> <83v8tz8btl.fsf@gnu.org> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="000000000000ccb51405df86fc82" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="5402"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 55529@debbugs.gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Sat May 21 17:10:11 2022 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nsQk7-0001H5-Cb for geb-bug-gnu-emacs@m.gmane-mx.org; Sat, 21 May 2022 17:10:11 +0200 Original-Received: from localhost ([::1]:44046 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nsQk5-0008Hw-VM for geb-bug-gnu-emacs@m.gmane-mx.org; Sat, 21 May 2022 11:10:09 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:45094) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nsQjy-0008Hl-S4 for bug-gnu-emacs@gnu.org; Sat, 21 May 2022 11:10:02 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:48924) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1nsQjy-0003wZ-CW for bug-gnu-emacs@gnu.org; Sat, 21 May 2022 11:10:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1nsQjy-0002sG-6u for bug-gnu-emacs@gnu.org; Sat, 21 May 2022 11:10:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: =?UTF-8?Q?=E0=A4=B8=E0=A4=AE=E0=A5=80=E0=A4=B0_?= =?UTF-8?Q?=E0=A4=B8=E0=A4=BF=E0=A4=82=E0=A4=B9?= Sameer Singh Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sat, 21 May 2022 15:10:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 55529 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: patch Original-Received: via spool by 55529-submit@debbugs.gnu.org id=B55529.165314575110976 (code B ref 55529); Sat, 21 May 2022 15:10:02 +0000 Original-Received: (at 55529) by debbugs.gnu.org; 21 May 2022 15:09:11 +0000 Original-Received: from localhost ([127.0.0.1]:42819 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1nsQj8-0002qx-UE for submit@debbugs.gnu.org; Sat, 21 May 2022 11:09:11 -0400 Original-Received: from mail-qk1-f176.google.com ([209.85.222.176]:44995) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1nsQj6-0002qi-Vp for 55529@debbugs.gnu.org; Sat, 21 May 2022 11:09:09 -0400 Original-Received: by mail-qk1-f176.google.com with SMTP id i68so8606833qke.11 for <55529@debbugs.gnu.org>; Sat, 21 May 2022 08:09:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=5H6mAsWF00zSuNDRoft5ZmYWZRhyD+M/9whsbBG+RYU=; b=U0UOcMxM1HBMtchFdtyqGOtuc4H1m9gId2NTNVpSZiIhXSyxEssSJZNMwG8QO2JmND VEAh53xbv3kkQerylQb/Cq2vkLwlwJjk1wdJ3vV4Yc1FG04SucFLxNOKhx574npCIOwt +cyvk6l1haxHawuKgvwISu8MumTYRfyqCs/+PYwa0qlv8+GxagnB70CaM4MiX97gYdNA pNh6PXNqCWUfptMPmkIR/Ui/UFSyPvezThb6ZUzGXmZ6ixmFx5DwLuEwG9VYye94m4BH BHWsd1weSKSU04/h0pDm6U/c/7DWAf5hf730g88ZEuuVhotlsKmLckT6QmzKANrbagwR y/Dg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=5H6mAsWF00zSuNDRoft5ZmYWZRhyD+M/9whsbBG+RYU=; b=zRbxrbJ7iDu6q4FZXPqo9hrF4EfljPqcgCbPFG2B0nfgu3Pms5fpVopJDHaqwrnvVs tDHK35eezqjk0o4iG4xeX+jAJOSkeGgyuVCQ/gNjJnWTP3w7JQBfB/Xajfk2p7Pmw9Sl hl+cfcqKFXsszMt+OpYUzZTmC1KIIy1GnCA2fnMiHw9a56DjZXxScogU20pk2lv1TK9z 14hrPfZgvzW0lDlS/uvIYKukVYHD3WaoNjVmemYQyrgsLNwoG7gsm/vb24kaE5RtULK9 1x//u7EED1UEHJNJlcBLVCs0uYkB6iui73PeY9VfPXqeKBiLzgOamc/R833opl4sFARJ r4Ew== X-Gm-Message-State: AOAM530zECHP/BTyAxtqXnASzGU5tdSOzLvAgRDPfSeRvVy/MC7iK7Mp lyBmQ/zeWudWeAdApVpgizWFMZcgdb/pZCm6+h4= X-Google-Smtp-Source: ABdhPJyu4jQNJbGYsipvW2fCexDN6smjEKE2y82oD2Kdo5bXnPeZhdlPKKz+8NAMB6Rva2gGZ7YZk2UVG5XCOnRnpBU= X-Received: by 2002:a37:d245:0:b0:69b:f262:bacb with SMTP id f66-20020a37d245000000b0069bf262bacbmr9500084qkj.66.1653145743436; Sat, 21 May 2022 08:09:03 -0700 (PDT) In-Reply-To: <83v8tz8btl.fsf@gnu.org> X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.io gmane.emacs.bugs:232838 Archived-At: --000000000000ccb51405df86fc82 Content-Type: text/plain; charset="UTF-8" > > I think "Tagalog" as the English label in HELLO is okay, but the > script native name in parentheses should be Baybayin. > > > I was also thinking about changing the > > input method from Tagalog to Baybayin, should I do that? > > No, I think it should be 'tagalog', but the doc string should say that > it supports the Baybayin script. > > > Is this really so important? The Wikipedia article says that Filipino > > is a version of Tagalog standardized by the constitution of 1987. > > Wouldn't it be better to support a modern language used nowadays and > > not just its older version? > > > > Doesn't the modern language use the Roman script, instead of Baybayin? > > > > 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. > Thanks I will do these. Btw, what fonts are considered to be good nowadays for displaying > Tagalog/Baybayin? > https://github.com/ctrlcctrlv/Noto-Sans-Tagalog/tree/master/dist This is what worked best for me, the older Noto font did not have characters for Ra, Alternative Ra, and Pamudpod, this one has it. On Sat, May 21, 2022 at 3:08 PM Eli Zaretskii wrote: > > Cc: 55529@debbugs.gnu.org > > Date: Sat, 21 May 2022 11:23:03 +0300 > > From: Eli Zaretskii > > > > > 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? > --000000000000ccb51405df86fc82 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
I t= hink "Tagalog" as the English label in HELLO is okay, but the
script native name in parentheses should be Baybayin.

> I was also thinking about changing the
> input method from Tagalog to Baybayin, should I do that?

 No, I think it should be 'tagalog', but the doc string should say t= hat
it supports the Baybayin script.

>=C2=A0 Is this really so important?=C2=A0 The Wikipedia article says th= at Filipino
>=C2=A0 is a version of Tagalog standardized by the constitution of 1987= .
>=C2=A0 Wouldn't it be better to support a modern language used nowa= days and
>=C2=A0 not just its older version?
>
> Doesn't the modern language use the Roman script, instead of Bayba= yin?
>
>=C2=A0 Looking at this another way: what will an Emacs user expect to f= ind in
>=C2=A0 Emacs as the supported language for the Philippines?
>
> Atleast according to me, correct me if I am=C2=A0 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 s= cript (except
where we use the script name inherited from Unicode, which is actually
the name of the Unicode block).=C2=A0 AFAICT, the patch you posted wasn'= ;t
consistent in that regard.=C2=A0 And NEWS should mention both the language<= br> and the script names.
=C2=A0
Thanks I will= do these.

Btw, what fonts are considered to be good nowadays for displayin= g
Tagalog/Baybayin?

This is what = worked best for me, the older Noto font did not have characters for Ra, Alt= ernative Ra, and Pamudpod, this one has it.

On Sat, May 21, 2022= at 3:08 PM Eli Zaretskii <eliz@gnu.org<= /a>> wrote:
&= gt; Cc: 55529@de= bbugs.gnu.org
> Date: Sat, 21 May 2022 11:23:03 +0300
> From: Eli Zaretskii <eliz@gnu.org>
>
> >=C2=A0 Looking at this another way: what will an Emacs user expect= to find in
> >=C2=A0 Emacs as the supported language for the Philippines?
> >
> > Atleast according to me, correct me if I am=C2=A0 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).=C2=A0 AFAICT, the patch you posted was= n't
> consistent in that regard.=C2=A0 And NEWS should mention both the lang= uage
> and the script names.

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