From: Kevin Bracey <kevin@bracey.fi>
To: "Torsten Bögershausen" <tboegi@web.de>
Cc: git@vger.kernel.org
Subject: Re: [PATCH v2] utf8.c: partially update to version 6.3
Date: Thu, 17 Apr 2014 15:14:25 +0300 [thread overview]
Message-ID: <534FC5A1.3000205@bracey.fi> (raw)
In-Reply-To: <201404171347.47528.tboegi@web.de>
On 17/04/2014 14:47, Torsten Bögershausen wrote:
> ./uniset/uniset +cat=Me +cat=Mn +cat=Cf -00AD +1160-11FF +200B c
200B isn't a special case any more, as its database properties have been
changed, so you can slightly simplify this command (both in the commit
message and the comments).
And while you're here I think it's probably worth updating the width=2
test now too, to make this a complete update to Unicode 6.3. I can see
it needs a few extensions (eg A960-A97C, FE10-FE19, 1F200-1F251).
Kevin
prev parent reply other threads:[~2014-04-17 12:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-17 11:47 [PATCH v2] utf8.c: partially update to version 6.3 Torsten Bögershausen
2014-04-17 12:14 ` Kevin Bracey [this message]
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=534FC5A1.3000205@bracey.fi \
--to=kevin@bracey.fi \
--cc=git@vger.kernel.org \
--cc=tboegi@web.de \
/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 NNTP newsgroup(s).