- From: Greg Eck <greck@postone.net>
- Date: Sat, 1 Aug 2015 01:07:35 +0000
- To: Andrew West <andrewcwest@gmail.com>, Badral S. <badral@bolorsoft.com>
- CC: "public-i18n-mongolian@w3.org" <public-i18n-mongolian@w3.org>
- Message-ID: <BN3PR10MB03210D258069CB6B02414E78AF890@BN3PR10MB0321.namprd10.prod.outlook.com>
Hi Andrew, The case that Badral is referring to is a numeric digit followed by the ordinal suffixes DUGAR/DUEGER and DAQI/DEQI. Specifically – a Latin digit OR a Mongolian digit followed by NNBSP followed by one of the four ordinal suffix forms DUGAR/DUEGER/DAQI/DEQI would be considered normal and the sequence should not be broken. Here are two examples ... <U+0031><U+202F><U+1833><U+1826><U+182D><U+1821><U+1837 > <U+0032><U+202F><U+1833><U+1824><U+182D><U+1820><U+1837 > Badral, please confirm. Greg PS I am attaching a DS05 dealing with all known usages of the NNBSP in Mongolian. The file includes both text strings as well as images. The ordinal section is on page 4. -----Original Message----- From: Andrew West [mailto:andrewcwest@gmail.com] Sent: Saturday, August 1, 2015 4:12 AM To: Badral S. <badral@bolorsoft.com> Cc: public-i18n-mongolian@w3.org Subject: Re: Mongolian NNBSP [I18N-ACTION-458] On 31 July 2015 at 19:50, Badral S. <badral@bolorsoft.com<mailto:badral@bolorsoft.com>> wrote: > >>> What is the context for "Numeric NNBSP Aletter" ? ExtendNumLet would >>> inhibit a word break after a numeric, but I think that MidLetter >>> would not. > > Then MidLetter is correct. A word break after a numeric is incorrect. I still do not know what the context for this use case is. Is it normal to have "Numeric NNBSP ALetter"? Can you provide an example? Andrew
Attachments
- image/jpeg attachment: ATT96726_1.jpg
- application/pdf attachment: DS05 Mongolian NNBSP Connected Suffixes.pdf
Received on Saturday, 1 August 2015 01:08:11 UTC