Go to listserv.cesnet.cz LWGate Home Page.From: =?ISO-8859-2?Q?krem=BEsk=E1_HO=D8=C8ICE?= <core@RADIO.CZ>
Subject: Re: several messages in ISO-8859-2 or CP1250...
Date: Tue, 5 Mar 1996 19:35:56 +0100
Next Article (by Subject): signal processing Eugenia Franzoni
Previous Article (by Subject): research Ivana Teskova
Articles sorted by: [Date]
[Author]
[Subject]
Excuse me for jumping in in English, and without a translation of the most
recent messages...
On 5 Mar 1996, Ji=F8=ED Kuchta wrote:
> > Subject: =3D?iso-8859-1?Q?Inzerat_=3D2D_voln=3DE1_pracovn=3DED_m=3DEDst=
a?=3D,
I shall forever curse Micro$oft for their CE code page which is like
ISO 8859-2 but different. The headers of the e-mail message I first saw
showed me that this message originated from Microsloth Exchange, so I am
not surprised that certain characters were wrong.
As noted, the charset tagging in this RFC1522 header is wrong. It
should be ISO-8859-2... except...
The character represented in hexadecimal MIME Q-P encoding as =3D2D doe=
s
not exist as a printable character in the ISO 8859 family of character
sets. Only in the Microsoft world. Bleagh.
> Hlavne kdyz je tam cestina v kodu ISO-8859-1 .....
> ----
> |Ing. Jiri Kuchta (Jiri Kuchta) |
On 5 Mar 1996, Jiri Kvarda wrote:
> BTW, jak by se Vam tam libilo jeste delsi ISO-8859-2-Windows-Latin-2 ?
Um, please, no. If anything, CP1250, but see the registered and
recommendations for charsets in MIME.
I am happy to note that I am alpha-testing the next version of Pine
(for Unix, X, PCs, and Windows, but not yet Mac), which properly displays
these RFC1522 headers, when they are properly generated, although there
are still some bugs which should not affect most users here.
Unfortunately, from looking at the source code so far, it appears that
while the DOS (PC-PINE) version makes use of the ISO_TO_CP and CP_TO_ISO
tables which can translate from CP852 or Kamenicky or whatever to
ISO-8859-2 -- which is recommended for 8-bit-charset encoding of those
languages such as Czech and Slovak over the Internet -- transparently,
this is ignored for the Windows version. I have suggested to the Pine
authors that they incorporate the short translation table for CP1250, as
well as for other code pages which do not match the suggested ISO 8859
subset, just as I pleaded with Nyetscape. This seems not yet to have been
implemented.
However, one should not give up hope. Yet. This new Pine has hooks
for external programs to be called before displaying, and before sending,
a message. The most common use I can see for this will be to incorporate
PGP decoding and encoding (but don't tell the US government), but one
could easily write a simple translation between CP1250 and ISO-8859-2
which is called based on the CHARSET of the message of concern (described
in the release notes, when made public). I think one could also write a
routine to be used when Pine runs in an xterm to echo the escape sequence
to change the display character set, if, say, a message arrives with real
ISO-8859-1 encoding which you want to display properly, while also viewing
ISO-8859-2 messages.
I do not know how widespread use of Pine is, but I believe those who
use it now will be pleased with this new release. I will be announcing
its availability in this forum from our FTP server. And then you will be
able to see my name properly, and think about lunch... ;-)
I shall now return to my hole in the ground and leave you all alone.
Barry Bouwsma, Internet Bozo
Radio Praha, Cesky Rozhlas 7 http://www.radio.cz
<barryb@ccsun.tuke.sk> finger for PGP key
Next Article (by Subject): signal processing Eugenia Franzoni
Previous Article (by Subject): research Ivana Teskova
Articles sorted by: [Date]
[Author]
[Subject]