From: Bernhard Voelker <mail@bernhard-voelker.de>
To: Jim Meyering <jim@meyering.net>, Bruno Haible <bruno@clisp.org>
Cc: "bug-gnulib@gnu.org List" <bug-gnulib@gnu.org>,
Coreutils <coreutils@gnu.org>
Subject: Re: diacrit: mark deprecated
Date: Wed, 17 Jul 2019 22:52:00 +0200 [thread overview]
Message-ID: <a1715911-3255-1546-f44e-910e94f69012@bernhard-voelker.de> (raw)
In-Reply-To: <CA+8g5KFb6biGVZ7_gvr-t32oKqZiJ+SEN-v7GYddaRF3t=9hLg@mail.gmail.com>
[adding coreutils: discussion at
https://lists.gnu.org/r/bug-gnulib/2019-01/msg00116.html ]
On 1/21/19 6:01 AM, Jim Meyering wrote:
> On Sun, Jan 20, 2019 at 5:11 PM Bruno Haible <bruno@clisp.org> wrote:
>> Hi Jim,
>>
>> You are listed as the maintainer of the 'diacrit' module. It doubt anyone is
>> still using this module, because it assumes an 8-bit character set, whereas
>> most systems have switched to UTF-8 10 to 18 years ago. Do you agree to mark
>> it deprecated?
>
> Hi Bruno, that's fine with me.
> Thanks
In GNU coreutils, we now get this warning during bootstrap:
Notice from module diacrit:
This module is deprecated. Use the module 'uninorm/canonical-decomposition' instead.
And indeed, the 'diacrit' module is still in use by 1 source:
$ GIT_PAGER= git grep -En 'todiac|tobase'
src/ptx.c:1053: diacritic = todiac (character);
src/ptx.c:1056: base = tobase (character);
src/ptx.c:1338: edited_flag[character] = todiac (character) != 0;
Have a nice day,
Berny
next prev parent reply other threads:[~2019-07-17 20:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-21 1:11 diacrit: mark deprecated Bruno Haible
2019-01-21 5:01 ` Jim Meyering
2019-07-17 20:52 ` Bernhard Voelker [this message]
2019-07-17 21:31 ` Bruno Haible
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
List information: https://lists.gnu.org/mailman/listinfo/bug-gnulib
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a1715911-3255-1546-f44e-910e94f69012@bernhard-voelker.de \
--to=mail@bernhard-voelker.de \
--cc=bruno@clisp.org \
--cc=bug-gnulib@gnu.org \
--cc=coreutils@gnu.org \
--cc=jim@meyering.net \
/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).