From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.bugs Subject: bug#55694: [PATCH] Add support for the Batak scripts Date: Sun, 29 May 2022 10:13:51 +0300 Message-ID: <835ylolsk0.fsf@gnu.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="8997"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 55694@debbugs.gnu.org To: =?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-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Sun May 29 09:15:51 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 1nvD9T-00028a-3q for geb-bug-gnu-emacs@m.gmane-mx.org; Sun, 29 May 2022 09:15:51 +0200 Original-Received: from localhost ([::1]:58064 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nvD9R-0003bN-Mp for geb-bug-gnu-emacs@m.gmane-mx.org; Sun, 29 May 2022 03:15:49 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:59862) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nvD8g-0003b6-JL for bug-gnu-emacs@gnu.org; Sun, 29 May 2022 03:15:03 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:45398) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1nvD8g-0007bZ-8j for bug-gnu-emacs@gnu.org; Sun, 29 May 2022 03:15:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1nvD8f-00067g-Uh for bug-gnu-emacs@gnu.org; Sun, 29 May 2022 03:15:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sun, 29 May 2022 07:15:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 55694 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: patch Original-Received: via spool by 55694-submit@debbugs.gnu.org id=B55694.165380844223455 (code B ref 55694); Sun, 29 May 2022 07:15:01 +0000 Original-Received: (at 55694) by debbugs.gnu.org; 29 May 2022 07:14:02 +0000 Original-Received: from localhost ([127.0.0.1]:39294 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1nvD7i-00066F-Eg for submit@debbugs.gnu.org; Sun, 29 May 2022 03:14:02 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:38210) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1nvD7d-00065a-Km for 55694@debbugs.gnu.org; Sun, 29 May 2022 03:14:01 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:42382) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nvD7Y-0007W4-8h; Sun, 29 May 2022 03:13:52 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=MIME-version:References:Subject:In-Reply-To:To:From: Date; bh=MaiPeSQSh8oe3GBd0K/YlQRoAktDUZKFDeccxH0xDMA=; b=F3e7dVQ36UVo7p5i9OVO GK0AHhPAktL1lRDkgq6r4e6Re6zLwwyVbQQ6/r0K9okkVJ2WmOBdchkS8hfT7pI9yvZlBAZiAeZ5c qPwGK3qI0hdr8rVAiV+fyfwtC6H0xn/CggtCpejlc+Eh0C9b0SdY7t1gFcdSBZtN31dd0Uu2pdhr8 wwHXI880OmhtmjqqO+TXZdaCTyNV0Ivyjo6T2Ss9WXKQnmlqJW9Vuhq+zwlVCAxT3fQB4XFqxqpl5 SFRccwe/+eXSZrZ3BtzvaX5WTPsOKqIuWJcMetjDIcUStPpHCojXoYqaVyQL4vSHa9z0OgkmoW6H/ rnPSk38HMIZbvA==; Original-Received: from [87.69.77.57] (port=3649 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nvD7X-0000Xp-OY; Sun, 29 May 2022 03:13:52 -0400 In-Reply-To: (lumarzeli30@gmail.com) 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:233291 Archived-At: > From: समीर सिंह Sameer Singh > > Date: Sun, 29 May 2022 06:21:33 +0530 > > This time the Batak scripts are added to Emacs. > Since the Batak scripts are actually a collection of five scripts: > Toba, Karo, Pakpak, Mandailing, and Simalungun. I think the above are _languages_, not scripts. They all used in the past to use the Batak script for writing, but they aren't scripts. > I have provided 5 different language environments and input-methods for them. > > Please review the patch. > --- a/etc/HELLO > +++ b/etc/HELLO > @@ -28,6 +28,7 @@ Amharic (አማርኛ) ሠላም > Arabic (العربيّة) السّلام عليكم > Armenian (հայերեն) Բարև ձեզ > Balinese (ᬅᬓ᭄ᬱᬭᬩᬮᬶ) ᬒᬁᬲ᭄ᬯᬲ᭄ᬢ᭄ᬬᬲ᭄ᬢᬸ > +Batak (ᯘᯮᯒᯗ᯲ᯅᯗᯂ᯲) ᯂᯬᯒᯘ᯲ Is this greeting common to all the languages using the Batak script? I don't think so. So perhaps we should have several greetings, one for each language? > --- a/etc/NEWS > +++ b/etc/NEWS > @@ -826,6 +826,11 @@ corresponding language environments are: > **** Balinese script and language environment > **** Javanese script and language environment > **** Sundanese script and language environment > +**** Batak Karo script and language environment > +**** Batak Toba script and language environment > +**** Batak Pakpak script and language environment > +**** Batak Mandailing script and language environment > +**** Batak Simalungun script and language environment See above: this should distinguish between the script name and the language names. Something like **** Karo language using the Batak script and its language environment > +(set-language-info-alist > + "Batak Karo" '((charset unicode) > + (coding-system utf-8) > + (coding-priority utf-8) > + (input-method . "batak-karo") > + (sample-text . "Batak Karo (ᯘᯬᯒᯗ᯳ᯆᯗᯂ᯳) ᯔᯧᯐᯬᯀᯱᯐᯬᯀᯱ") > + (documentation . "\ > +Batak Karo language and its script are supported in this language environment."))) Likewise here. The doc string should say something like Karo language using the Batak script is supported in this language environment. > + > +(set-language-info-alist > + "Batak Toba" '((charset unicode) > + (coding-system utf-8) > + (coding-priority utf-8) > + (input-method . "batak-toba") > + (sample-text . "Batak Toba (ᯘᯮᯮᯒᯖ᯲ᯅᯖᯂ᯲) ᯂᯬᯒᯘ᯲") > + (documentation . "\ > +Batak Toba language and its script are supported in this language environment."))) > + > +(set-language-info-alist > + "Batak Pakpak" '((charset unicode) > + (coding-system utf-8) > + (coding-priority utf-8) > + (input-method . "batak-pakpak") > + (sample-text . "Batak Pakpak (ᯘᯮᯒᯗ᯲ᯅᯗᯂ᯲) ᯂᯬᯒᯘ᯲") > + (documentation . "\ > +Batak Pakpak language and its script are supported in this language environment."))) > + > +(set-language-info-alist > + "Batak Mandailing" '((charset unicode) > + (coding-system utf-8) > + (coding-priority utf-8) > + (input-method . "batak-mandailing") > + (sample-text . "Batak Mandailing (ᯚᯮᯒᯖ᯲ᯅᯖᯄᯱ᯲) ᯄᯬᯒᯚ᯲") > + (documentation . "\ > +Batak Mandailing language and its script are supported in this language environment."))) > + > +(set-language-info-alist > + "Batak Simalungun" '((charset unicode) > + (coding-system utf-8) > + (coding-priority utf-8) > + (input-method . "batak-simalungun") > + (sample-text . "Batak Simalungun (ᯙᯮᯮᯓᯖ᯳ᯅᯖᯃ᯳) ᯃᯬᯓᯙ᯲") > + (documentation . "\ > +Batak Simalungun language and its script are supported in this language environment."))) > + Btw, according to this article: https://en.wikipedia.org/wiki/Batak_languages there are 2 more languages that used Batak; why aren't they included? > +(quail-define-package > + "batak-karo" "Batak Karo" "ᯂᯒᯭ" nil "Batak Karo phonetic input method." > + nil t t t t nil nil nil nil nil t) > + > +(quail-define-rules The input methods look almost identical, with a few minor deviations. Are the differences real or are they mistakes? If they are mistakes, we can have just one input method for all the languages using Batak. And if the differences are real, can we still have only one input method, where the different variants of the same ASCII letter are selected by the user at typing time? It seems un-economical to have so many input methods that are almost identical. Thanks.