From: Andreas Schwab <schwab@linux-m68k.org>
To: "Игорь Пашев" <pashev.igor@gmail.com>
Cc: libc-ports@sourceware.org
Subject: Re: Extended Unix Code
Date: Sun, 17 Mar 2013 12:59:00 -0000 [thread overview]
Message-ID: <m2boaikwqw.fsf@igel.home> (raw)
In-Reply-To: <CALL-Q8zSPvi8mn_73vLoZusZ8KZ6i=UY+VaUnrfS57MAJuNnAw@mail.gmail.com> (=?utf-8?B?ItCY0LPQvtGA0Ywg0J/QsNGI0LXQsiIncw==?= message of "Sun, 17 Mar 2013 15:40:07 +0400")
Игорь Пашев <pashev.igor@gmail.com> writes:
> 1. Is such a functionality needed in glibc?
EUC is obsoleted by UTF-8.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2013-03-17 12:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-17 11:40 Игорь Пашев
2013-03-17 12:59 ` Andreas Schwab [this message]
2013-03-17 16:16 ` Игорь Пашев
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=m2boaikwqw.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=libc-ports@sourceware.org \
--cc=pashev.igor@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 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).