From: Thomas Wolff <towo@towo.net>
To: newlib@sourceware.org
Subject: Re: Unicode update of width and other character properties
Date: Sun, 25 Feb 2018 17:14:00 -0000 [thread overview]
Message-ID: <62dbc36b-7636-a358-355f-e588a325c924@towo.net> (raw)
In-Reply-To: <20171204090318.GB21472@calimero.vinschen.de>
I have finally revamped, manually rebased, and repackaged my Unicode
data patches which I'll send in separate mail.
However, as I don't have a command-line sendmail set up (and apparently
it's not as easy as it used to be),
I'll send zip archives which contain git-patch files.
There are two patches:
libc/string: wcwidth using generated width data, with data generated
from Unicode 10.0
libc/ctype: isw* and tow* functions using generated case conversion and
character class data, with Unicode 10.0 data
For both, generation script and a Makefile.widthdata / Makefile.chardata
is included. As these are to be used in the source directory,
not the binary target directory, in case of future Unicode update, they
are not related to the other Makefiles.
In ctype/, there is one new source (categories.c) which should be
compiled separately but although I tried to include it in Makefile.am,
I could not get the build process to compile it. So the current solution
is to include it from one of the other sources (the one that also
maintains the case conversion table).
Thomas
next prev parent reply other threads:[~2018-02-25 17:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-06 5:36 Thomas Wolff
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 [this message]
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=62dbc36b-7636-a358-355f-e588a325c924@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).