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.devel Subject: Re: Not able to display \u110BD and \u110CD in Emacs Date: Sat, 07 May 2022 17:22:14 +0300 Message-ID: <83pmkpxw15.fsf@gnu.org> References: <837d779kgx.fsf@gnu.org> <83h761zv0w.fsf@gnu.org> <20220507.194920.1642525629735859845.enometh@meer.net> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="11946"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org To: Madhu Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat May 07 16:23:10 2022 Return-path: Envelope-to: ged-emacs-devel@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 1nnLKw-00030F-IB for ged-emacs-devel@m.gmane-mx.org; Sat, 07 May 2022 16:23:10 +0200 Original-Received: from localhost ([::1]:45516 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nnLKv-0004UZ-37 for ged-emacs-devel@m.gmane-mx.org; Sat, 07 May 2022 10:23:09 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:53164) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nnLKD-0003n0-5T for emacs-devel@gnu.org; Sat, 07 May 2022 10:22:25 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:39788) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nnLKC-00053m-R6; Sat, 07 May 2022 10:22:24 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=X9teBegt/qDaObmjINjT6mNGsedzkO6+RYh3cWYuIo4=; b=fnbLXCw/ajrT QhV6OceSP+EPP5PYvdjl/QEYXHI0X2SE51YahnOojCON16NccokxA5ndNye5MuokVI1lt9GHDB/lq ZoTr1VDMOJcHw17wNp/cY5KBKrnSUpE0DJ+D89fUK5yTuXj6/TLjcC/HYy4tIiY4vqRN/qdSpSiE8 c7Ns19MJyNrs9KOPfxGoQfuJERBkCDNxr6B3xv60kLVakOyOYSiNawxtgbBl+7jn0HSibHRmMZmcC u2CB3MeUIqAk0sFSRa+s8+LcVyl+0sZ/E+XgPfA6W1wCjoaj8C9leGcsEktLGxm3u0r2osfTVe7qX AEaxL7ZeVeTiIk0m7JVd8w==; Original-Received: from [87.69.77.57] (port=3353 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 1nnLKC-00086K-9Q; Sat, 07 May 2022 10:22:24 -0400 In-Reply-To: <20220507.194920.1642525629735859845.enometh@meer.net> (message from Madhu on Sat, 07 May 2022 19:49:20 +0530 (IST)) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:289396 Archived-At: > Date: Sat, 07 May 2022 19:49:20 +0530 (IST) > Cc: emacs-devel@gnu.org > From: Madhu > > * Eli Zaretskii <83h761zv0w.fsf@gnu.org> > Wrote on Sat, 07 May 2022 10:01:03 +0300 > > >> From: Madhu > >> Date: Thu, 05 May 2022 21:23:50 +0530 > >> > >> The devanagari numerals 1 (#x967) & 3 (#x969) can be combined with > >> the svarita (#x951, incorrectly named in unicode as DEVANAGARI > >> STRESS SIGN UDATTA) and the anudatta (#x952) to form the 4 different > >> accents. > >> > >> numeral one + anudatta + svarita > >> preceding anudatta + numeral three + anudatta + svarita > >> numeral one + anudatta > >> numeral three + anudatta + svarita > >> > >> e.g. (#x969 #x951 #x952), when composed, the devanagari numeral 3 > >> should have an anudatta ("line below") and svarita ("vertical line > >> above") > > > > Where are these rules documented? I don't see them in the latest > > Unicode Standard 14.0. > > I have no idea. I assumed the rulesfollow from (some defined) rules > for composition, but I stopped dealing with unicode for sanskrit ( > vedic accents) back in 2002 when I saw the direction it was going in. It is strange that I seem to be unable to find such rules anywhere on the Internet, not just in the Unicode Standard text.