W3C home > Mailing lists > Public > public-i18n-mongolian@w3.org > October to December 2015

RE: U+180A Nirugu / U+1807 Sibe Syllable Marker

From: Greg Eck <greck@postone.net>
Date: Mon, 9 Nov 2015 15:57:44 +0000
To: "public-i18n-mongolian@w3.org" <public-i18n-mongolian@w3.org>
Message-ID: <SN1PR10MB0943BB0E7C8B52AEDBFB6941AF150@SN1PR10MB0943.namprd10.prod.outlook.com>
Richard, Andrew,
Regarding the U+1807 / U+180A then …
We should recommend a change in the ArabicShaping.txt file to be "D" for dual-joining for the U+180A?
We should also recommend that the General Property for both U+1807 as well as U+180A be changed from "Punctuation" to "Letter"?

From: Richard Wordingham [mailto:richard.wordingham@ntlworld.com]
Sent: Wednesday, October 28, 2015 9:33 AM
Subject: Re: U+180A Nirugu

A good rendering engine for OpenType will refuse to select a final form for NIRUGU on the basis of it being in final position.  The UCD data file ArabicShaping.txt records it as having the value 'join_causing' for its Joining_Type, which means that characters on either side of it might change shape, but it itself won't.  To get NIRUGU to change shape in final position, its Joining_Type needs to be changed to Dual_Joining.

I fear that renderers may hard-wire this property, rather than getting if from their usual source of Unicode properties.

>From a Unicode perspective anything that is encoded is a "character", so obviously Nirugu and Sibe syllable boundary marker are by definition both characters.  I guess what you mean is that they both act as letters.  However, as both these characters have a Unicode general property of "Po" (Punctuation, other), there may be a problem with treating them as letters, with positional forms and FVS variants
-- I don't know if there is a problem, but am just flagging this as a potential issue to be taken into consideration.


Picture (Device Independent Bitmap) 1.jpg
(image/jpeg attachment: Picture__Device_Independent_Bitmap__1.jpg)

Received on Monday, 9 November 2015 15:58:16 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:07:44 UTC