From: Jesper Harder <harder@myrealbox.com>
Subject: Re: Gnus: UTF-8 and compatibility with other MUAs
Date: Sun, 17 Aug 2003 02:57:25 +0200 [thread overview]
Message-ID: <m3u18hxfre.fsf@defun.localdomain> (raw)
In-Reply-To: <uoeyp62cy.fsf@ID-87814.user.dfncis.de>
Oliver Scholz <alkibiades@gmx.de> writes:
> Jesper Harder <harder@myrealbox.com> writes:
>
>> But the purpose of email is to _communicate_. Why lower you chance
>> of cummunicating if there is no compelling technical reason to do
>> so?
>
> Now and then I realize in German Usenet, that a few people who post
> replies to my articles can not deal with UTF-8, because when they
> quote the text I wrote, I see funny characters instead of umlauts.
> This is not a big impediment to communication.
It is a big impediment, believe me. A long time ago I used read
Usenet by TELNETTing from a Norsk Data terminal to an overloaded
Ultrix box. Needless to say this setup could not display any 8bit
characters (the eight bit was stripped). Reading Danish was so
annoying that I didn't use dk.* for many years.
Also remember that not everyone can say "Okay, I'll just upgrade to
something Unicode-capable". If you're using a shared system you
probably don't have the power to decide that.
> If we don't move to Unicode in the future then coding system
> problems will go on forever and ever.
It would be foolish not to use Unicode for any _new_ protocols or
formats. But for legacy systems like email and Usenet backward
compatibility is really, really important. If you look at how
e.g. MIME or format=flowed was designed, you'll see that a lot of
effort and thought was spent on minimizing negative effects for
existing clients.
You need an especially good excuse to break existing stuff. The fact
that Unicode is a technically more pleasing solution just isn't a good
enough reason to break things unnecessarily, IMHO.
But if you're doing something that wasn't possible before, say, using
German and Thai in the same message, that's a valid reason to use
Unicode.
> My guess -- by the way -- is that Unicode will become increasingly
> important in Europe, especially for the members of the EU. We'd need
> at least Latin-1/Latin-9, Latin-2 and Greek (ISO 8859-7). And I am not
> sure if that already covers Latvian, Romanian and others. There will
> be a growing need for an encoding that covers all of these languages.
I think most Western European users don't care about and don't know
how to access any glyph that isn't printed on the keyboard.
>> 2. Unicode support itself doesn't really buy me a lot if most people
>> don't have fairly complete Unicode fonts (which they don't).
>
> So the worst thing that could happen is that they see a hollow box now
> and then.
An empty box can be bad enough. If you're writing an equation it can
be really important what that empty box happens to be ☺ I experienced
that problem recently when I used ℏ in a message.
> And yet some characters are more frequent than others. You can
> probably rely on the fact that western Europeans have fonts that
> contain the Latin-1 repertoire. Box drawing characters or symbols
> may not be that frequent, but there is a good chance to get the
> additional punctuation characters.
In practice the only thing you can reasonably expect are the 650
glyphs in WGL4.¹
¹ http://partners.adobe.com/asn/tech/type/opentype/appendices/wgl4.jsp
next prev parent reply other threads:[~2003-08-17 0:57 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-14 15:48 Xavier Maillard
2003-08-14 22:39 ` Frank Schmitt
2003-08-15 18:22 ` Xavier Maillard
2003-08-14 23:01 ` Jesper Harder
2003-08-15 13:50 ` Oliver Scholz
2003-08-15 16:48 ` Jesper Harder
2003-08-15 18:10 ` Oliver Scholz
2003-08-16 0:23 ` Jesper Harder
2003-08-16 9:48 ` Oliver Scholz
2003-08-16 13:01 ` Jesper Harder
2003-08-16 15:36 ` Oliver Scholz
2003-08-16 17:14 ` Reiner Steib
2003-08-16 19:29 ` Oliver Scholz
2003-08-19 14:54 ` Miles Bader
2003-08-20 15:24 ` Reiner Steib
2003-08-21 0:20 ` Miles Bader
2003-08-16 17:23 ` Simon Josefsson
2003-08-16 19:18 ` Oliver Scholz
2003-08-16 22:24 ` Simon Josefsson
2003-08-17 12:30 ` Benjamin Riefenstahl
2003-08-17 16:40 ` Oliver Scholz
2003-08-18 2:20 ` James H. Cloos Jr.
2003-08-18 15:58 ` Benjamin Riefenstahl
2003-08-18 2:16 ` James H. Cloos Jr.
2003-08-18 2:09 ` James H. Cloos Jr.
2003-08-28 13:38 ` Jens Müller
2003-08-28 13:35 ` Jens Müller
2003-08-17 0:57 ` Jesper Harder [this message]
2003-08-17 17:24 ` Oliver Scholz
2003-08-17 18:21 ` Matthias Andree
2003-08-15 18:24 ` Xavier Maillard
2003-08-16 0:35 ` Jesper Harder
2003-08-14 23:05 ` Simon Josefsson
2003-08-15 17:00 ` Oliver Scholz
2003-08-16 7:43 ` Ivan Boldyrev
2003-08-17 17:27 ` Oliver Scholz
2003-08-18 6:01 ` Steinar Bang
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=m3u18hxfre.fsf@defun.localdomain \
--to=harder@myrealbox.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 NNTP newsgroup(s).