From: Yaakov Selkowitz <yselkowitz@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Unicode width data inconsistent/outdated
Date: Wed, 26 Jul 2017 17:03:00 -0000 [thread overview]
Message-ID: <5d3cb047-49f8-26a6-d816-387a71486e99@cygwin.com> (raw)
In-Reply-To: <20170726080859.GA24312@calimero.vinschen.de>
[-- Attachment #1.1: Type: text/plain, Size: 674 bytes --]
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.
>> Thomas
>
> If you can update the newlib files this way and send matching patches
> to the newlib list, this would be highly appreciated.
Thomas, I just updated unicode-ucd to 10.0 for this purpose.
--
Yaakov
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2017-07-26 8:16 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-26 14:23 Thomas Wolff
2017-07-26 14:59 ` Corinna Vinschen
2017-07-26 17:03 ` Yaakov Selkowitz [this message]
2017-07-26 17:06 ` Corinna Vinschen
2017-07-27 17:09 ` Thomas Wolff
2017-07-29 15:23 ` Corinna Vinschen
2017-08-03 19:44 ` Thomas Wolff
2017-08-04 17:02 ` Corinna Vinschen
2017-08-05 19:06 ` Thomas Wolff
2017-08-05 20:24 ` Brian Inglis
2017-08-05 20:53 ` Thomas Wolff
2017-08-07 9:28 ` Corinna Vinschen
2017-08-07 10:41 ` Corinna Vinschen
2017-08-07 19:07 ` Brian Inglis
2017-08-07 19:31 ` Thomas Wolff
2017-08-07 21:29 ` Brian Inglis
2017-08-08 0:29 ` Thomas Wolff
2017-08-07 19:27 ` Thomas Wolff
2017-08-08 8:22 ` Corinna Vinschen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5d3cb047-49f8-26a6-d816-387a71486e99@cygwin.com \
--to=yselkowitz@cygwin.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).