This is the mail archive of the
mailing list for the Cygwin project.
Re: Unicode width data inconsistent/outdated
- From: Brian Inglis <Brian dot Inglis at SystematicSw dot ab dot ca>
- To: cygwin at cygwin dot com
- Date: Sat, 5 Aug 2017 14:24:13 -0600
- Subject: Re: Unicode width data inconsistent/outdated
- Authentication-results: sourceware.org; auth=none
- References: <email@example.com> <20170726080859.GA24312@calimero.vinschen.de> <firstname.lastname@example.org> <20170726095016.GA25666@calimero.vinschen.de> <email@example.com> <20170728195826.GI24013@calimero.vinschen.de> <firstname.lastname@example.org> <20170804170156.GL25551@calimero.vinschen.de> <email@example.com>
- Reply-to: Brian dot Inglis at SystematicSw dot ab dot ca
On 2017-08-05 13:06, Thomas Wolff wrote:
> Am 04.08.2017 um 19:01 schrieb Corinna Vinschen:
>> On Aug 3 21:44, Thomas Wolff wrote:
>>> Am 28.07.2017 um 21:58 schrieb Corinna Vinschen:
>>>> On Jul 26 23:43, Thomas Wolff wrote:
>>>>> Am 26.07.2017 um 11:50 schrieb Corinna Vinschen:
>>>>>> On Jul 26 03:16, Yaakov Selkowitz wrote:
>>>>>>> On 2017-07-26 03:08, Corinna Vinschen wrote:
>>>>>>>> On Jul 26 08:49, Thomas Wolff wrote:
>>>>>>>>> It would be good to keep wcwidth/wcswidth in sync with the
>>>>>>>>> installed Unicode data version (package unicode-ucd).
>>>>>>>>> Currently it seems to be hard-coded (in
>>>>>>>>> newlib/libc/string/wcwidth.c); it refers to Unicode 5.0 while
>>>>>>>>> installed Unicode data suggest 9.0 would be used.
>>>>>>>>> I can provide some scripts to generate the respective tables
>>>>>>>>> if desired.
>>>>>>>> If you can update the newlib files this way and send matching
>>>>>>>> patches to the newlib list, this would be highly appreciated.
Submit to ^
>>>>>>> I just updated unicode-ucd to 10.0 for this purpose.
>>>>>> Oh, and, btw, the comment in wcwidth.c isn't quite correct. The
>>>>>> cwstate in newlib is on Unicode 5.2, see
>>>>> Oh, a number of other embedded tables. To make the tow* and isw*
>>>>> functions more easily adaptable to Unicode updates, there will be
>>>>> some revisions to do here. And the to* and is* ones (without 'w')
>>>>> even refer to locales in a way I do not understand. Maybe I'll
>>>>> restrict my effort to wcwidth first...
>>>> The to* and is* ones (without 'w') don't matter at all and you don't
>>>> have to touch them.
>>>> The Unicode stuff only affects the tow and isw functions.
>>>> As for how to fetch the data, you may want to have a look into
>>>> newlib/libc/ctype/utf8alpha.h and newlib/libc/ctype/utf8print.h. The
>>>> header comments contain the awk scripts used to collect the data.
>>> But there are no instructions to adapt the embedded conditional
>>> statements referring to those data...
>> Tables are ...
> I had an impression how the tables work. Yet there is no automatic mechanism
> to generate the data-based conditionals in the code which would need to be
> adapted too for Unicode updates. Therefore:
>>> My attempt would be to base the functions on a common table of character
>>> categories instead.
>> Keep in mind that the table is not loaded into memory on demand, as on
>> Linux. Rather it will be part of the Cygwin DLL, and worse in case newlib,
>> any target using the wctype functions.
> Maybe we could change that (load on demand, or put them in a shared library
> perhaps), but...
>> The idea here is that the tables take less space than a full-fledged
>> category table. The tables in utf8print.h and utf8alpha.h and the code in
>> iswalpha and iswprint combined are 10K, code and data of the
>> tolower/toupper functions are 7K, wcwidth 3K, so a total of 20K, covering
>> Unicode 5.2 with 107K codepoints.
>> A category table would have to contain the category bits for the entire
>> Unicode codepoint range. The number of potential bits is > 8 as far as I
>> know so it needs 2 bytes per char, but let's make that 1 byte for now. For
>> Unicode 5.2 only the table would be at least 107K, and that would only
>> cover the iswXXX functions.
> I have a working version now, and it uses much less as the category table is
> Another table is needed for case conversion. Size estimates are as follows
> (based on Unicode 5.2 for a fair comparison, going up a little bit for 10.0
> of course):
> Categories: 2313 entries (10.0: 2715)
> each entry needs 9 bytes, total 20817 bytes
> I don't know whether that expands by some word-alignment.
> I could pack entries to 7 bytes, or even 6 bytes if that helps (total 16191
> or 13878).
> Case conversion: 2062 entries (10.0: 2621)
> each entry needs 12 bytes, total 24744
> packed 8 bytes, total 16496
> The Categories table could be boiled down to 1223 entries (penalty: double
> runtime for iswupper and iswlower)
> The Case conversion table could be transformed to a compact form
> Case conversion compact: 1201 entries
> each entry needs 16 bytes, total 19216
> packed 12 or 11 (or even 10), total 14412 (or 12010)
> So I think the increase is acceptable for the benefit of simple and
> automatic generation and also more efficient processing by some of the
> functions. Also they would apply to more functions, e.g. iswdigit which would
> confirm all Unicode digits, not just the ASCII ones.
>>> Also, there are 3 other issues:
>>> Issue 1 is about handling non-BMP characters by wcwidth.
>>> This has been discussed before.
>>> While wcswidth works already (using internal __wcwidth), and the isw*
>>> and tow* functions work as well because they use wint_t, wcwidth is the
>>> only function (inconsistently insisting on wchar_t) that does not work.
>> Trying to be close to the standard here.
>>> But note https://linux.die.net/man/3/wcwidth which says
>>>> Note that glibc before 2.2.5 used the prototype
>>>> int wcwidth(wint_t c);
>>> Why not revert to wcwidth(wint_t)?
>>> I think for cygwin it is the only solution that makes wcwidth work for
>>> non-BMP characters and is also compatible (unlike some proposals
>>> discussed later in the quoted thread).
>> We can do this, but it may result in complaints from the other newlib
>> consumers. If in doubt, use #ifdef __CYGWIN__
> Which other platforms do actually use newlib?
Many historical uPs and current uCs used in embedded systems supporting gcc not
using Linux, including RTEMS, devKits for Nintendo and Sony game systems, aome
Android, Google NaCl.
>>> Issue 2 is the handling of titlecase characters (e.g. "Nj" as one Unicode
>>> character U+01CB). The current implementation considers them to be both
>>> upper and lower (iswupper: return towlower (c) != c); I'd rather consider
>>> them as neither upper nor lower (iswalpha (c) && towupper (c) == c).
>>> https://linux.die.net/man/3/iswupper allows both interpretations:
>>>> The wide-character class "upper" contains *at least* those characters wc
>>>> which are equal to towupper(wc) and different from towlower(wc).
>> Susv4 says "The iswupper() [...] functions shall test whether wc is a
>> wide-character code representing a character of class upper." Whatever
>> does that correctly with a low footprint is fine.
> The question here is how "character of class upper" is defined, and how to
> interpret pre-Unicode assumptions in a Unicode context.
>>> Issue 3 is the special conversion jp2uc which seems to be half-bred;
>>> there is no such handling for Chinese or Korean.
>> This shouldn't matter to you, just keep it in place. It's a historical, low
>> footprint conversion for japanese characters without pulling in the unicode
>> stuff. Not used on Cygwin so just ignore.
> I had noticed meanwhile that this is not active in Cygwin, but it's broken
> anyway for multiple reasons:
> * platforms for which wchar_t is not Unicode should be explicitly listed
> * if used, the transformation needs to be applied to all non-Unicode locales
> (also Chinese, Korean, and even 8-bit locales such as *.CP1252)
> * for towupper and towlower, the result must be back-transformed into the
> respective locale encoding
> * particulary the locale-specific _l functions inconsistently do not use the
> transformation but have this note:
>> We're using a locale-independent representation of upper/lower case based
>> on Unicode data. Thus, the locale doesn't matter.
> So I'd suggest to drop that stuff unless someone would like to fix it.
Looks like JIS support is under newlib/iconvdata
> Should I send my proposal to firstname.lastname@example.org or
See note near top:
newlib for anything under that directory,
patches for anything under winsup directory.
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple