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: Fri, 20 May 2022 22:01:28 +0530 Message-ID: References: <83pmk89tbk.fsf@gnu.org> <83k0ag9ohs.fsf@gnu.org> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="000000000000f9c84205df740804" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="34349"; 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 Fri May 20 18:33:26 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 1ns5Z8-0008lk-MP for geb-bug-gnu-emacs@m.gmane-mx.org; Fri, 20 May 2022 18:33:26 +0200 Original-Received: from localhost ([::1]:54058 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ns5Z6-0003KZ-Pi for geb-bug-gnu-emacs@m.gmane-mx.org; Fri, 20 May 2022 12:33:25 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:48804) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ns5Yk-0003J8-5o for bug-gnu-emacs@gnu.org; Fri, 20 May 2022 12:33:02 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:46077) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1ns5Yj-0007Sw-T0 for bug-gnu-emacs@gnu.org; Fri, 20 May 2022 12:33:01 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1ns5Yj-00081L-Ke for bug-gnu-emacs@gnu.org; Fri, 20 May 2022 12:33:01 -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: Fri, 20 May 2022 16:33:01 +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.165306435130791 (code B ref 55529); Fri, 20 May 2022 16:33:01 +0000 Original-Received: (at 55529) by debbugs.gnu.org; 20 May 2022 16:32:31 +0000 Original-Received: from localhost ([127.0.0.1]:39974 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ns5YE-00080Y-RH for submit@debbugs.gnu.org; Fri, 20 May 2022 12:32:31 -0400 Original-Received: from mail-qv1-f42.google.com ([209.85.219.42]:39847) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ns5YC-00080M-W0 for 55529@debbugs.gnu.org; Fri, 20 May 2022 12:32:29 -0400 Original-Received: by mail-qv1-f42.google.com with SMTP id e20so7015033qvr.6 for <55529@debbugs.gnu.org>; Fri, 20 May 2022 09:32:28 -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=6BcpOskqomeDCzilouvREmxkB15bh7XA+hb63TiA8cA=; b=EeyqwITGvb5dQlByaMntIDXuQwsA8jQXJ3iQOIjI+M5Q2Rn0srha5Hd/q1tcHHogrT 6jabXrFehRDD2FLHjDTdXcIq15yXkMFR8lFa8hKmCXwO7XQ3nHauAzhsr0fv9j2blTbH PkPPi2B9TPpxtJz1uD+lVRr1jUooa7vvI78h7BFYzdqvGqfqwSNaduHXCUSdsVzpBv1U ySNP7myD8TspZtKe1tWISJU2O+pXWCdtY5v2Umr8flSu5gy5ej9A/70wt1KY9DcifLuJ w8k55NO7xdqPdRUpvr22lSPXG1dfMpYp57qzew2fImUypQCKsC6Ta/U4bb1Q++ohIw1x b0Lg== 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=6BcpOskqomeDCzilouvREmxkB15bh7XA+hb63TiA8cA=; b=IhI6amkUvS84QXxPczNdWRAGc01/dze8eJjYC3SXNwrdCf9IQcLtiMSUtZAvr37Ura 2LG2P5oL1qEvSxMkQ7T0fLCTsi3sBL5VxY/XQUZw9tbjufduhUTVXOJ2XYxNIlD5RMtU KDzLPQNfaE1MMNwuUTBWSRUl1cL+Q+FrIjkLXsskv7JTYXDxTScEfb/gOR6HFku5HcCS J5vjW7r4/iE8+5pJt3B616puDdwHEmverrexNcMqGVnFHzNGNCYjDcj1892oKI59lp9+ 0f46Tu+s49bLUkBr4xlP4TQZyCRgWt7ESoCr0NIugEMxwkiD8iXSzafbZ5JTb4pNUgEJ UKmA== X-Gm-Message-State: AOAM531FX9cEgs+9g9b8UNpQ7gEB2qN+kqrsTPBoaabwy6a0VFz61fTx p+DxJFnuLM+siTRS/JH94ClM4B3d0EzBPnAzpoBfNMTb2v0IPQ== X-Google-Smtp-Source: ABdhPJwTHxxbteA5borjVAh5Ms67AlpPo/cTaaWZUxA/vg0kLN6AD2eGtD2moUC2Vym1vFK/qs5CnC/Po3MTkFnVJbY= X-Received: by 2002:ad4:5de5:0:b0:45b:53b:6824 with SMTP id jn5-20020ad45de5000000b0045b053b6824mr8751758qvb.75.1653064343340; Fri, 20 May 2022 09:32:23 -0700 (PDT) In-Reply-To: <83k0ag9ohs.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:232782 Archived-At: --000000000000f9c84205df740804 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable > > And if you are talking mainly about a script, then its name is > Baybayin, no? Tagalog is a language, not a script, right? Yes, I was confused about that too, the Unicode documents only mention Tagalog and not Baybayin. This wikipedia page: https://en.wikipedia.org/wiki/Tagalog_(Unicode_block) says that the Tagalog script is a variety of the Baybayin script. But still in etc/HELLO, I have used Baybayin as the native name, should I also change its English name? I was also thinking about changing the input method from Tagalog to Baybayin, should I do that? 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. On Fri, May 20, 2022 at 9:37 PM Eli Zaretskii wrote: > > From: =E0=A4=B8=E0=A4=AE=E0=A5=80=E0=A4=B0 =E0=A4=B8=E0=A4=BF=E0=A4=82= =E0=A4=B9 Sameer Singh > > Date: Fri, 20 May 2022 21:14:04 +0530 > > Cc: 55529@debbugs.gnu.org > > > > I think this entry should not be together with the old Indic scripts, > > it should be separate from them. Especially if you intend to add more > > scripts/languages used in the Philippines. > > > > Tagalog and other philippine scripts also descend from Brahmi. They are > also superseded by the Roman > > script, so I would consider them as old. > > Fine with me, if you insist. But I raised a brow when I saw that, > FWIW. > > And if you are talking mainly about a script, then its name is > Baybayin, no? Tagalog is a language, not a script, right? > > > I wonder whether we should call the language-environment "Tagalog". > > Why not "Filipino", which AFAIU is the official language name? > > Perhaps also for the input method. > > > > AFAICT from the internet, Tagalog and Filipino are two different > languages, Filipino is Tagalog with foreign > > loanwords, for e.g. the Filipino word for a chair is "silya" (from > Spanish) > > while in Tagalog it is "salumpuwit". > > 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? > > Looking at this another way: what will an Emacs user expect to find in > Emacs as the supported language for the Philippines? > --000000000000f9c84205df740804 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
And if y= ou are talking mainly about a script, then its name is
Baybayin, no?=C2=A0 Tagalog is a language, not a script, right?

Yes, I was confused about that too, the Unicode docume= nts only mention Tagalog and not Baybayin.
This wikipedia page: <= a href=3D"https://en.wikipedia.org/wiki/Tagalog_(Unicode_block)">https://en= .wikipedia.org/wiki/Tagalog_(Unicode_block) says that the Tagalog scrip= t is a variety of the Baybayin script.
But still in etc/HELLO, I = have used Baybayin as the native name, should I also change its English nam= e? I was also thinking about changing the
input method from Tagal= og to Baybayin, should I do that?

Is this really so important?=C2=A0 The Wi= kipedia 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 a= t 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=C2=A0 a filipin= o user will use the Roman script for the filipino language, while writing T= agalog he may look for Baybayin, which we
have provided under the= Tagalog language environment.

On Fri, May 20, 2022 at 9:37 PM Eli= Zaretskii <eliz@gnu.org> wrote:<= br>
> From: =E0= =A4=B8=E0=A4=AE=E0=A5=80=E0=A4=B0 =E0=A4=B8=E0=A4=BF=E0=A4=82=E0=A4=B9 Same= er Singh <lum= arzeli30@gmail.com>
> Date: Fri, 20 May 2022 21:14:04 +0530
> Cc: 55529@d= ebbugs.gnu.org
>
>=C2=A0 I think this entry should not be together with the old Indic scr= ipts,
>=C2=A0 it should be separate from them.=C2=A0 Especially if you intend = to add more
>=C2=A0 scripts/languages used in the Philippines.
>
> Tagalog and other philippine scripts also descend from Brahmi. They ar= e also superseded by the Roman
> script, so I would consider them as old.

Fine with me, if you insist.=C2=A0 But I raised a brow when I saw that,
FWIW.

And if you are talking mainly about a script, then its name is
Baybayin, no?=C2=A0 Tagalog is a language, not a script, right?

>=C2=A0 I wonder whether we should call the language-environment "T= agalog".
>=C2=A0 Why not "Filipino", which AFAIU is the official langua= ge name?
>=C2=A0 Perhaps also for the input method.
>
> AFAICT from the internet, Tagalog and Filipino are two different langu= ages, Filipino is Tagalog with foreign
> loanwords, for e.g. the Filipino word for a chair is "silya"= (from Spanish)
> while in Tagalog it is "salumpuwit".

Is this really so important?=C2=A0 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?

Looking at this another way: what will an Emacs user expect to find in
Emacs as the supported language for the Philippines?
--000000000000f9c84205df740804--