public inbox for newlib@sourceware.org
 help / color / mirror / Atom feed
From: Thomas Wolff <towo@towo.net>
To: newlib@sourceware.org
Subject: Unicode update of width and other character properties
Date: Sun, 06 Aug 2017 05:36:00 -0000	[thread overview]
Message-ID: <d3089ec4-234e-10ed-1a6c-c93fadd8b856@towo.net> (raw)

Hi,
this is a proposal to update wcwidth and the character properties 
functions isw*/towupper/towlower to Unicode 10.0, as discussed in the 
mail thread https://cygwin.com/ml/cygwin/2017-07/msg00366.html,
as well as to simplify automatic generation of respective tables for an 
easier update step.
Table size is moderate (using ranges for character properties) but there 
is still an option to reduce the two big tables in size.

The patch can be retrieved from http://towo.net/cygwin/charprops10.zip .

The Makefile.widthdata does not yet distinguish the two subdirectories
(libc/string, libc/ctypw) as it comes from a common development directory.

There is a test program in which comparison for isw*/tow* functions
between current and patched implementation can be compared.

I also provide a log of deviations of the new approach to the current 
implementation, based on Unicode 5.2 data, to compare and check.
If there are any disputable cases, I would consider that of course.

My main aim was actually to get the wcwidth data updated, for which the 
change is more obviously clear.

Thanks
Thomas




             reply	other threads:[~2017-08-06  5:36 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-06  5:36 Thomas Wolff [this message]
2017-08-07 10:31 ` Corinna Vinschen
2017-08-07 19:18   ` Thomas Wolff
2017-08-08  8:30     ` Corinna Vinschen
2017-08-17 11:03       ` Thomas Wolff
2017-12-03 14:07         ` Corinna Vinschen
2017-12-03 17:31           ` Thomas Wolff
2017-12-03 17:33             ` Jon Turney
2017-12-04  7:32             ` Brian Inglis
2017-12-04  9:05             ` Corinna Vinschen
2018-02-25 17:14               ` Thomas Wolff
2018-02-26 17:20                 ` Corinna Vinschen
2018-02-26 20:02                   ` Thomas Wolff
2018-02-26 20:25                     ` Hans-Bernhard Bröker
2017-12-02 11:25 ` Ping: " Thomas Wolff

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=d3089ec4-234e-10ed-1a6c-c93fadd8b856@towo.net \
    --to=towo@towo.net \
    --cc=newlib@sourceware.org \
    /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).