From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Stefan Kangas Newsgroups: gmane.emacs.bugs Subject: bug#58957: [PATCH] Improve Brahmi composition rules. Date: Thu, 24 Nov 2022 11:40:20 -0800 Message-ID: References: <834jvhbkqf.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="28283"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Eli Zaretskii , 58957@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 Thu Nov 24 20:41:15 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 1oyI5z-0007AW-1n for geb-bug-gnu-emacs@m.gmane-mx.org; Thu, 24 Nov 2022 20:41:15 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oyI5t-0004iv-QL; Thu, 24 Nov 2022 14:41:09 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oyI5n-0004i2-Dh for bug-gnu-emacs@gnu.org; Thu, 24 Nov 2022 14:41:03 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1oyI5m-0006tI-Jk for bug-gnu-emacs@gnu.org; Thu, 24 Nov 2022 14:41:03 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1oyI5m-00014g-GP for bug-gnu-emacs@gnu.org; Thu, 24 Nov 2022 14:41:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Stefan Kangas Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Thu, 24 Nov 2022 19:41:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 58957 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: patch Original-Received: via spool by 58957-submit@debbugs.gnu.org id=B58957.16693188424066 (code B ref 58957); Thu, 24 Nov 2022 19:41:02 +0000 Original-Received: (at 58957) by debbugs.gnu.org; 24 Nov 2022 19:40:42 +0000 Original-Received: from localhost ([127.0.0.1]:60276 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1oyI5R-00013Q-Hu for submit@debbugs.gnu.org; Thu, 24 Nov 2022 14:40:41 -0500 Original-Received: from mail-oo1-f54.google.com ([209.85.161.54]:35374) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1oyI5B-00012M-RI for 58957@debbugs.gnu.org; Thu, 24 Nov 2022 14:40:26 -0500 Original-Received: by mail-oo1-f54.google.com with SMTP id r76-20020a4a374f000000b004988a70de2eso388282oor.2 for <58957@debbugs.gnu.org>; Thu, 24 Nov 2022 11:40:25 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=content-transfer-encoding:cc:to:subject:message-id:date :mime-version:references:in-reply-to:from:from:to:cc:subject:date :message-id:reply-to; bh=4+RDc3FBZxuzfSOVdlKzFrtaA3BRmV2pw3R3mQWtj7U=; b=NC4hr8ivBGH/glXz353IUWXjkHyYuMkVi2VMjwhiZULMcX6b5s0bvyGzxM8M7H1CTV pbYKbFEQkp5kMeOdGWLnfFMr22LM5UjCb6SsMdCXU7qM/AW0oM24BSHB/0G62ssZJhtr gIEp/pLVMhi+5lLrV42VuTod7WcnkKHRghmyw2UmFh1arsrIRasxcmIxu44yaHBm5G10 0S+TlymIbA0MpoCSQsJSqcvNr/txLSmJQHsCu2q6SCZ1JLqHI4eE/HExX7jmfftHYGof RXGHVVcVlu4ozUaGJTs8kyfYp0NQU8tZMRwXlT+3QWi7zjDg6vyYo68Fg78ShbpaWuCa 5pYQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:cc:to:subject:message-id:date :mime-version:references:in-reply-to:from:x-gm-message-state:from:to :cc:subject:date:message-id:reply-to; bh=4+RDc3FBZxuzfSOVdlKzFrtaA3BRmV2pw3R3mQWtj7U=; b=RQQKQHEYCVz2CuAYnUhj21eusQYZRr7mmXSekSsx+cKwINRG6r67RX5Vu9rE14ydtk OxTlNTgzrXxbQx43oMzfQuvnu08xAjmI0sOZLWm9wflh4t/7QXUOUK8mtNEXt1ta+Xkk fwPEnyydpsR0ip1OgX/+LyQUxTxSFPGHHdnS5OQc/EgKBS3m3NfPgPbb6s1qbBy5lKW9 2yRUIhXXmZZFJhdCm0jZp/QbWydVRLZJ9CqvavhDOpLWHYTM4EpOraFb5GU2w1K+UfPe SbGzFfonxSkHQQX/PNGyusE7G9NsjlHr/LdZB4uwx/j0mkUtwHJGLbf9O5UkgQ0LW8vT I/oQ== X-Gm-Message-State: ANoB5pllcRQPRMhI3ek+tKgl5fDD+f0R9yEnrcpp/tne4SqqKePAiQCn xtFwQACJ4dzguq2qwppQZSS8SFuPZlGTCmYDmH/54UUD X-Google-Smtp-Source: AA0mqf4B95bg2cwH0fOZ9vkBlkGO5i2VapIB85bG0WCyeIs19RVsJvqw48r4L3E03PANDWStxFEimcJrYckCucKCJGA= X-Received: by 2002:a4a:2a57:0:b0:49a:6eb0:735a with SMTP id x23-20020a4a2a57000000b0049a6eb0735amr6201799oox.34.1669318820393; Thu, 24 Nov 2022 11:40:20 -0800 (PST) Original-Received: from 753933720722 named unknown by gmailapi.google.com with HTTPREST; Thu, 24 Nov 2022 11:40:20 -0800 In-Reply-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"'s message of "Wed, 2 Nov 2022 20:27:42 +0530") X-Hashcash: 1:20:221124:lumarzeli30@gmail.com::Ryq+L7yKFUFozVZu:1Qxf 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-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.bugs:248906 Archived-At: =E0=A4=B8=E0=A4=AE=E0=A5=80=E0=A4=B0 =E0=A4=B8=E0=A4=BF=E0=A4=82=E0=A4=B9 S= ameer Singh writes: > Should we perhaps introduce tests for compositions? For example, I > guess you found the problems with the current rules by examining the > display of some sequences of characters, so why not add a test that > would make sure we never again break those composable sequences? > > Yes, that would be a good idea. > How should I start? Are there some pre-existing examples that checks for > composition, > or even a manual that describes how to write a test? We basically have the code in test/, and the `ert' info manual. Evaluate this to open it: (info "(ert) Top")