From: Hrvoje Niksic <hniksic@iskon.hr>
Subject: Re: de .* and gnus-group-posting-charset-alist
Date: 17 Dec 1999 09:53:22 +0100 [thread overview]
Message-ID: <9t9so12osn1.fsf@mraz.iskon.hr> (raw)
In-Reply-To: Per Abrahamsen's message of "15 Dec 1999 08:20:28 +0100"
Per Abrahamsen <abraham@dina.kvl.dk> writes:
> smarkacz@anathema.eu.org (smarkacz) writes:
>
> > How do you know whether these undeclared characters are Latin1, Latin2,
> > Windows1250 (yuck) or any other coding system?
>
> Easy, look at the newsgroups header.
That doesn't really work.
Now that I use Gnus with Mule, I have real problems with Croatian
users' broken new agents, which mis-declare Latin 2 articles as Latin
1. Poor Gnus thinks the message is Latin 1, and renders it that way.
:-( Unix Slrn/Tin users are especially guilty of this, because many
of them don't bother to setup their newsreaders correctly. After all,
*their* newsreaders just dump 8bit data to the terminal, which uses
Latin 2 fonts, so *they* see it right.
Crock like Windows-1250 can be handled, but not generally, i.e. such
handling is but a local hack, based on the fact that only two
Croatian-specific characters differ in positions between windows-1250
and Latin 2. So you can "convert" between the two without loss of
information by swapping the two characters' codes.
It all just sucks.
next prev parent reply other threads:[~1999-12-17 8:53 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-07 20:45 Karl EICHWALDER
1999-12-08 6:50 ` Florian Weimer
1999-12-11 20:20 ` Kai Großjohann
1999-12-12 6:39 ` Karl EICHWALDER
1999-12-12 9:22 ` Florian Weimer
1999-12-12 11:46 ` Bjørn Mork
1999-12-13 12:04 ` Christophe Cuq
1999-12-12 10:47 ` Kai Großjohann
1999-12-12 15:54 ` Karl EICHWALDER
1999-12-12 11:07 ` Per Abrahamsen
1999-12-12 11:15 ` Florian Weimer
1999-12-13 9:08 ` Per Abrahamsen
1999-12-13 23:51 ` Karl EICHWALDER
1999-12-14 8:48 ` Per Abrahamsen
1999-12-21 20:06 ` Kai Großjohann
1999-12-21 20:30 ` Florian Weimer
1999-12-21 21:32 ` Kai Großjohann
1999-12-23 20:30 ` Florian Weimer
1999-12-21 20:47 ` Per Abrahamsen
1999-12-22 0:07 ` Russ Allbery
1999-12-22 0:52 ` Stainless Steel Rat
1999-12-14 20:18 ` smarkacz
1999-12-14 20:56 ` Florian Weimer
1999-12-17 11:49 ` Toby Speight
1999-12-18 19:33 ` Florian Weimer
1999-12-19 10:47 ` Per Abrahamsen
1999-12-19 18:23 ` Karl EICHWALDER
[not found] ` <ug0x1bxde.fsf@lanber.ca <shvh5uhjsf.fsf@tux.gnu.franken.de>
1999-12-20 11:24 ` Per Abrahamsen
1999-12-20 23:22 ` Florian Weimer
1999-12-21 20:23 ` Florian Weimer
1999-12-20 18:20 ` Karl EICHWALDER
1999-12-15 7:20 ` Per Abrahamsen
1999-12-17 8:53 ` Hrvoje Niksic [this message]
1999-12-21 20:08 ` Kai Großjohann
1999-12-21 20:29 ` Florian Weimer
1999-12-21 21:31 ` Kai Großjohann
1999-12-22 10:10 ` Hrvoje Niksic
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=9t9so12osn1.fsf@mraz.iskon.hr \
--to=hniksic@iskon.hr \
/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).