Re: Quotation marks: Using =?UTF-8?Q?=E2=80=9C=E2=80=9D?= instead of ""

Am Montag, den 16.06.2008, 18:59 +0200 schrieb Dave Neary:
> Iain * wrote:
> > On Mon, Jun 16, 2008 at 11:20 AM, Alan Cox <alan lxorguk ukuu org uk> wrote:
> >> In LANG=C you call gtk_label_new with UTF-8 strings. What happens at that
> >> point depends if gtk_label_new ever calls a single C library function
> >> that is locale dependant (eg strcasecmp).
> > 
> > All of GTK is utf-8 compatible.
> > This is the point we're trying to make.
> I"m increasingly mystified by this discussion.
> Lots of people use non-UTF8 locales - most of the people I know send
> iso-8859-15 emails and when I send UTF8 emails they end up seeing €¥ or
> whatever instead of é. I can imagine that lots of Linux users use
> non-UTF8 locales for their UI. I don't know if there are any stats for
> this, but a couple of people working with distributions have said so.
> Alan's made a reasonable argument that we shouldn't be using non-ascii
> in C source files. It's not standard. He's made a reasonable argument
> that in the case where a string is untranslated, or the user chooses the
> C locale, the output string will be the input string, and if the input
> string is non-ASCII UTF-8, then strange and unexpected things will happen.
> This is starting to sound to me like change for change's sake. I don't
> see any decent reason to make the change (other than the "proper" quotes
> look better, even if they're harder to type), and credible people have
> pointed out a significant potential for breakage in a change like this.
> Prudence suggests backing down and letting the subject drop would be the
> best course of action. If there are UTF8 strings being passed to gettext
> currently, perhaps that's the problem that needs to be fixed.

Also to consider: It should be trivial to modify intltool to
automatically generate en_* message catalogs which use the proper
quotation marks. This approach is much more compatible, requires less
change and has a much greater chance for success, wide adoption and

Just a little story to support my consistency claim: I once did a
program targeting mainly German users, so I decide to use German as
message-id language. Well, and I had serious problems to consistently
use proper quotation marks: You always have to use those primitive
ASCII quotation marks in the C code, and they are more trivial to type.
So in the end quotation mark usage was rather random.

Also when taking the approach of tool support further it is easy to
imagine, to use that code to verify consistent quotation mark usage in
message catalogs.

So I'd say: Keep the source code ASCII clean - love it or hate it, but C
is specified to be ASCII only (despite the fact, that gcc seems to be
8-bit safe).

Mathias Hasselmann <mathias hasselmann gmx de>
Openismus GmbH:
Personal Site:

Attachment: signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]