From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Richard Stallman Newsgroups: gmane.emacs.bugs Subject: bug#58159: [PATCH] Add support for the Wancho script Date: Fri, 14 Oct 2022 17:24:48 -0400 Message-ID: References: <83bkqtzl6d.fsf@gnu.org> Reply-To: rms@gnu.org Content-Type: text/plain; charset=Utf-8 Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="15794"; mail-complaints-to="usenet@ciao.gmane.io" Cc: eliz@gnu.org, 58159@debbugs.gnu.org To: =?UTF-8?Q?=C3=A0=C2=A4?= =?UTF-8?Q?=C2=B8=C3=A0=C2=A4=C2=AE=C3=A0=C2=A5=C2=80=C3=A0=C2=A4=C2=B0_?= =?UTF-8?Q?=C3=A0=C2=A4?= =?UTF-8?Q?=C2=B8=C3=A0=C2=A4=C2=BF=C3=A0=C2=A4=C2=82=C3=A0=C2=A4=C2=B9?= Sameer Singh Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Fri Oct 14 23:26:36 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 1ojSCS-0003vN-9q for geb-bug-gnu-emacs@m.gmane-mx.org; Fri, 14 Oct 2022 23:26:36 +0200 Original-Received: from localhost ([::1]:51542 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ojSCQ-0008IR-Po for geb-bug-gnu-emacs@m.gmane-mx.org; Fri, 14 Oct 2022 17:26:34 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:50110) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ojSAx-0007K8-0S for bug-gnu-emacs@gnu.org; Fri, 14 Oct 2022 17:25:03 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:39738) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1ojSAw-0006ND-OK for bug-gnu-emacs@gnu.org; Fri, 14 Oct 2022 17:25:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1ojSAw-0000EQ-68 for bug-gnu-emacs@gnu.org; Fri, 14 Oct 2022 17:25:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Richard Stallman Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Fri, 14 Oct 2022 21:25:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 58159 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: patch Original-Received: via spool by 58159-submit@debbugs.gnu.org id=B58159.1665782696875 (code B ref 58159); Fri, 14 Oct 2022 21:25:02 +0000 Original-Received: (at 58159) by debbugs.gnu.org; 14 Oct 2022 21:24:56 +0000 Original-Received: from localhost ([127.0.0.1]:38816 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ojSAp-0000E2-V9 for submit@debbugs.gnu.org; Fri, 14 Oct 2022 17:24:56 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:37054) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ojSAo-0000Dg-1p for 58159@debbugs.gnu.org; Fri, 14 Oct 2022 17:24:55 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:49330) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ojSAi-0006Fy-SI; Fri, 14 Oct 2022 17:24:48 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=Date:References:Subject:In-Reply-To:To:From: mime-version; bh=5+zki5jRU1/VmzOHzDmkhyrWDvWJJx045K7N8Lx/qrU=; b=bKO3Ns5K7Nrn pMLGl554gguABGEYuyDiTgJfyxTNPXZ4JfEOZOjaKw3yw42UnbmNkY2ggNKZmkD42+03bensIS9aj F8Iw1Vau2ghWA7T9tYSxTpKqjXlxRtY46d7MbdK4f9/jbGehO00oFTvoXlmQwgVW+EpMNs/xsSG1Q CA7kRJveEuBRTuDboArxIMNoR4rdAajqnV31jfBlSrRkqoB0a5lw8s55ZLFfCcm2EZciUFz/p8M2C yaN1/FS0D0UK15QWQLY5ZQEv6hA3VofBPYB2as73JYgBlpt2wfPPCvwZlef2+Klnk0nhS6IuafClj UOPw4a1ph2/PPsdgBlx5zA==; Original-Received: from rms by fencepost.gnu.org with local (Exim 4.90_1) (envelope-from ) id 1ojSAi-0000wQ-7U; Fri, 14 Oct 2022 17:24:48 -0400 In-Reply-To: (message from =?UTF-8?Q?=C3=A0=C2=A4?= =?UTF-8?Q?=C2=B8=C3=A0=C2=A4=C2=AE=C3=A0=C2=A5=C2=80=C3=A0=C2=A4=C2=B0_?= =?UTF-8?Q?=C3=A0=C2=A4?= =?UTF-8?Q?=C2=B8=C3=A0=C2=A4=C2=BF=C3=A0=C2=A4=C2=82=C3=A0=C2=A4=C2=B9?= Sameer Singh on Sun, 9 Oct 2022 06:38:53 +0530) 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:245488 Archived-At: [[[ To any NSA and FBI agents reading my email: please consider ]]] [[[ whether defending the US Constitution against all enemies, ]]] [[[ foreign or domestic, requires you to follow Snowden's example. ]]] > Can you elaborate on what changes are needed in which manual? I don't know, but normally every new addition calls for documentation somewhere. > This is what a typical patch for adding a script in Emacs looks like: > 1. A one line entry in etc/NEWS announcing the support of the script and > its language environment. > 2. A one line greeting in the language/script which is added in etc/HELLO > (optional) > 3. A one line entry in script-representative-chars in > lisp/international/fontset.el so that Emacs can select an appropriate font > for it. > 4. Adding the script name in setup-default-fontset in > lisp/international/fontset.el > 5. Defining a language environment for the script in the lisp/language/*.el > files which includes the following entries: > its charset (usually unicode), its coding-system (usually utf-8), its > coding-priority (usually utf-8), its input-method, its sample text (the > same text which is added in etc/HELLO), > a one line documentation usually in the following template: "foo language > and its script bar are supported in this language environment." > 6. Adding composition rules for the script (optional, only needed for > complex scripts) > 7. Adding an input-method for the script in lisp/leim/quail/*.el files That looks like nontrivial work to add each script. Not a big job, but not minimal either. For a script that users actually want, it is work worth doing. For a script that we support only because some bureaucrats decided to include it in Unicode, is it worth that much? > These scripts were not developed for "PR motives", they were developed to > serve the needs of the community. What I've read suggests the opposite. I am not convinced that the community experienced or experiences such linguistic "needs". It looks like some activists in that community decided that using their own script would help them get political benefits, so they push for its adoption. What we know about this is sketchy. (I could see only fragments of the article you pointed at -- I suspect nonfree JS blocks the rest.) If the speakers of a language are really using a script, I am in favor of supporting it. > It is necessary for Unicode to support them because this is not the age of > pen and paper where the only thing limiting you to write any script for > communication is... you. I don't subscribe to the idea that we Emacs developers _must_ support every script that a minority of some speecdh community campaigns to switch to. That is dogmatic, and it could impose an unlimited burden on us. If every endangered language gets its own script, that could be almost 200 more scripts coming from India alone. I am in favor of preserving endangered languages, but that doesn't usually require inventing a new script for each one. For instance, speakers of 22 Maya languages got together and established a rather natural convention for writing them in the Latin alphabet. The convention states how to express each sound used in any of those languages. You can find it in Maya Languages in Wikipedia. -- Dr Richard Stallman (https://stallman.org) Chief GNUisance of the GNU Project (https://gnu.org) Founder, Free Software Foundation (https://fsf.org) Internet Hall-of-Famer (https://internethalloffame.org)