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

RE: Mongolian NNBSP [I18N-ACTION-458]

From: Greg Eck <greck@postone.net>
Date: Tue, 4 Aug 2015 13:54:41 +0000
To: Badral S. <badral@bolorsoft.com>, "public-i18n-mongolian@w3.org" <public-i18n-mongolian@w3.org>
Message-ID: <BN3PR10MB0321CE840C1C4C2A8E0B31CCAF760@BN3PR10MB0321.namprd10.prod.outlook.com>
Badral,
Did you have a file "range.words" for us to look at?
Greg


-----Original Message-----
From: Badral S. [mailto:badral@bolorsoft.com] 
Sent: Tuesday, August 4, 2015 9:34 PM
To: public-i18n-mongolian@w3.org
Subject: Re: Mongolian NNBSP [I18N-ACTION-458]

Hi,
Just for info. As I promised, we tested our spellchecker on MS Word 2007, MS Word 2010 and OpenOffice/LibreOffice.
No software has passed in NNBSP test. The resulting words of the "range.Words" separated by NNBSP.

Badral

On 01.08.2015 20:43, Badral S. wrote:
> Hi Richard,
> MS word doesn't have a Mongolian spell-checker. Bolorsoft has 
> developed a spell-checker for Mongolian (http://spell.bolorsoft.com/).
> It is a commercial product, which works with MS office, 
> Open/LibreOffice and designed for both cyrillic Mongolian and 
> traditional Mongolian script, but due to some difficulties (NNBSP, MVS
> etc.) traditional Mongolian version has not been released. We tested 
> it first with Openoffice and got the word boundary problems.
> We will test our MS word addon for traditional script now and notify 
> the result asap.
>
> Badral
>
> On 01.08.2015 13:00, Richard Wordingham wrote:
>> On Sat, 1 Aug 2015 11:31:54 +0100
>> Andrew West <andrewcwest@gmail.com> wrote:
>>
>>> I thought that rendering engines were already correctly rendering 
>>> suffixes after NNBSP, and that the issue was with some editors and 
>>> word processors (notably Word) incorrectly segmenting Mongolian text 
>>> for word counting, word selection and word navigation purposes.  If 
>>> text-processing applications rely on WordBreakProperty.txt for word 
>>> breaking then they should work after the change is introduced; if 
>>> not, then it is up to users to report the behaviour as a bug to the 
>>> individual software vendors.
>> Word doesn't use WordBreakProperty.txt.  While Microsoft may take 
>> note of a recommended change to the file, the trouble with NNBSP 
>> should be reported independently.  The best argument would be what 
>> happens for spell-checking.  Does Word have a Mongolian spell-checker?
>>
>> Richard.
>>
>
>


--
Badral Sanlig, Software architect
www.bolorsoft.com | www.badral.net
Bolorsoft LLC, Selbe Khotkhon 40/4 D2, District 11, Ulaanbaatar
Received on Tuesday, 4 August 2015 13:55:13 UTC

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