Re: Popular wordprocessors treating U+00A0 as fixed-width

2018-01-01 Thread Philippe Verdy via Unicode
pe > Verdy via Unicode > *Sent:* Monday, January 01, 2018 5:43 AM > *To:* Shriramana Sharma > *Cc:* UnicoDe List > *Subject:* Re: Popular wordprocessors treating U+00A0 as fixed-width > > > > Well it's unfortunate that Microsoft's own response (by its MSVP) is > completely

RE: Popular wordprocessors treating U+00A0 as fixed-width

2018-01-01 Thread Jonathan Rosenne via Unicode
, January 01, 2018 5:43 AM To: Shriramana Sharma Cc: UnicoDe List Subject: Re: Popular wordprocessors treating U+00A0 as fixed-width Well it's unfortunate that Microsoft's own response (by its MSVP) is completely wrong, suggesting to use Narrow non-breaking space to get justification, which

Re: Popular wordprocessors treating U+00A0 as fixed-width

2017-12-31 Thread Philippe Verdy via Unicode
Well it's unfortunate that Microsoft's own response (by its MSVP) is completely wrong, suggesting to use Narrow non-breaking space to get justification, which is exactly the reverse where these NNBSP should NOT be justified and keep their width. Microsoft's developers have absolutely

Popular wordprocessors treating U+00A0 as fixed-width

2017-12-31 Thread Shriramana Sharma via Unicode
While http://unicode.org/reports/tr14/ clearly states that: When expanding or compressing interword space according to common typographical practice, only the spaces marked by U+0020 SPACE and U+00A0 NO-BREAK SPACE are subject to compression, and only spaces marked by U+0020 SPACE, U+00A0