From: "Torsten Bögershausen" <tboegi@web.de>
To: "Peter Krefting" <peter@softwolves.pp.se>,
"Torsten Bögershausen" <tboegi@web.de>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Unicode: update of combining code points
Date: Wed, 16 Apr 2014 06:48:04 +0200 [thread overview]
Message-ID: <534E0B84.6070602@web.de> (raw)
In-Reply-To: <alpine.DEB.2.00.1404152009020.29301@ds9.cixit.se>
On 15.04.14 21:10, Peter Krefting wrote:
> Torsten Bögershausen:
>
>> diff --git a/utf8.c b/utf8.c
>> index a831d50..77c28d4 100644
>> --- a/utf8.c
>> +++ b/utf8.c
>
> Is there a script that generates this code from the Unicode database files, or did you hand-update it?
>
Some of the code points which have "0 length on the display" are called
"combining", others are called "vowels" or "accents".
E.g. 5BF is not marked any of them, but if you look at the glyph, it should
be combining (please correct me if that is wrong).
If I could have found a file which indicates for each code point, what it
is, I could write a script.
So yes, it is updated by hand.
next prev parent reply other threads:[~2014-04-16 4:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-07 19:30 [PATCH] Unicode: update of combining code points Torsten Bögershausen
2014-04-15 19:10 ` Peter Krefting
2014-04-16 4:48 ` Torsten Bögershausen [this message]
2014-04-16 10:51 ` Kevin Bracey
2014-04-16 19:58 ` Torsten Bögershausen
2014-04-17 6:32 ` Kevin Bracey
2014-04-24 9:02 ` Peter Krefting
-- strict thread matches above, loose matches on Subject: below --
2014-04-07 19:34 Torsten Bögershausen
2014-04-07 19:38 Torsten Bögershausen
2014-04-07 19:39 Torsten Bögershausen
2014-04-07 19:54 ` Jonathan Nieder
2014-04-08 22:37 ` Junio C Hamano
2014-04-09 16:48 ` Torsten Bögershausen
2014-04-09 17:30 ` Junio C Hamano
2014-04-10 4:12 ` Torsten Bögershausen
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=534E0B84.6070602@web.de \
--to=tboegi@web.de \
--cc=git@vger.kernel.org \
--cc=peter@softwolves.pp.se \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.