From: Zack Weinberg <zack@codesourcery.com>
To: "Martin v. Loewis" <martin@v.loewis.de>
Cc: Per Bothner <per@bothner.com>, gcc@gcc.gnu.org
Subject: Re: quote marks [was: Status of i18n patches]
Date: Mon, 14 Oct 2002 12:51:00 -0000 [thread overview]
Message-ID: <20021014183838.GD3271@codesourcery.com> (raw)
In-Reply-To: <m3ptucc1ux.fsf@mira.informatik.hu-berlin.de>
On Mon, Oct 14, 2002 at 08:27:34PM +0200, Martin v. Loewis wrote:
> Zack Weinberg <zack@codesourcery.com> writes:
>
> > > One option: we could have the various error routines post-process
> > > the error message before printing. Depending on an option or the
> > > locale it could either emit a pair of 0x27 or a 0x2018/0x2019 pair
> > > ...
> >
> > An interesting idea... although, if we go with the double-quote
> > suggestion, it should be 0x201C/0x201D. Don't recent versions of
> > gettext have the ability to recode messages on output?
>
> glibc will do transliteration, translating 201C/201D with
> 0022. 2018/2019 transliterate to 0027. Dunno if standalone
> gettext/iconv can also transliterate.
I'm pretty sure glibc gettext/iconv are kept in sync with standalone.
They are, however, newer than what's in the gcc CVS. Updating them is
on my list for 3.4, but has to be coordinated with binutils/gdb.
zw
next prev parent reply other threads:[~2002-10-14 18:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-13 16:57 Status of i18n patches Martin v. Loewis
2002-10-14 9:35 ` quote marks [was: Status of i18n patches] Per Bothner
2002-10-14 10:03 ` Zack Weinberg
2002-10-14 10:25 ` Paul Koning
2002-10-14 12:42 ` Joseph S. Myers
2002-10-14 12:55 ` Per Bothner
2002-10-14 15:31 ` Michael Matz
2002-10-14 17:13 ` Per Bothner
2002-10-15 3:57 ` Michael Matz
2002-10-15 3:46 ` Gabriel Dos Reis
2002-10-14 12:44 ` Martin v. Loewis
2002-10-14 12:51 ` Zack Weinberg [this message]
2002-10-15 3:38 ` Gabriel Dos Reis
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=20021014183838.GD3271@codesourcery.com \
--to=zack@codesourcery.com \
--cc=gcc@gcc.gnu.org \
--cc=martin@v.loewis.de \
--cc=per@bothner.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).