From: Junio C Hamano <gitster@pobox.com>
To: "Force Charlie via GitGitGadget" <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org, Force Charlie <charlieio@outlook.com>
Subject: Re: [PATCH] unicode: update the width tables to Unicode 15
Date: Mon, 19 Sep 2022 11:49:09 -0700 [thread overview]
Message-ID: <xmqqczbr9p3u.fsf@gitster.g> (raw)
In-Reply-To: <xmqqo7vbb810.fsf@gitster.g> (Junio C. Hamano's message of "Mon, 19 Sep 2022 10:15:07 -0700")
Junio C Hamano <gitster@pobox.com> writes:
> "Force Charlie via GitGitGadget" <gitgitgadget@gmail.com> writes:
>
>> From: Force Charlie <charlieio@outlook.com>
>>
>> Unicode 15 Released[0] and including several additional zero/double
>> width characters.
>>
>> [0] https://home.unicode.org/announcing-the-unicode-standard-version-15-0/
>>
>> Signed-off-by: Force Charlie <charlieio@outlook.com>
>> ---
> Thanks.
>
> Where are you getting the information to update these ranges from,
> among 4489 new characters? Is there a readily accessible URL that
> is more suitable than the announcement of the whole collection?
Ah, it would probably is a good idea to say what you did to prepare
this patch in this case, like:
Unicode 15 that was released recentry [0] includes several
additional zero/double width characters.
Update unicode-width.h table by cd'ing to contrib/update-unicode/
and running update_unicode.sh script there.
[0] https://home.unicode.org/announcing-the-unicode-standard-version-15-0/
or something, I guess.
Thanks.
next prev parent reply other threads:[~2022-09-19 18:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-17 4:18 [PATCH] unicode: update the width tables to Unicode 15 Force Charlie via GitGitGadget
2022-09-19 17:15 ` Junio C Hamano
2022-09-19 18:49 ` Junio C Hamano [this message]
2022-09-19 19:00 ` [PATCH v2] " Force Charlie via GitGitGadget
-- strict thread matches above, loose matches on Subject: below --
2022-09-20 2:04 [PATCH] " 李博文
2023-03-30 19:15 Beat Bolli
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=xmqqczbr9p3u.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=charlieio@outlook.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.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 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.