[tin+Cygwin] (In)Correct display of local characters.
- From: Frank Slootweg <this@xxxxxxxxxxxxxxxxx>
- Date: 30 Aug 2005 10:06:58 GMT
Not a big deal but something strange which perhaps can be fixed:
I use tin under Cygwin on MS-Windows XP in a "Command Prompt" window
(i.e. not from a (Bash) shell)).
That works fine, but for postings which do *not* have the proper MIME
headers or/and in-line encoding, local language characters are not
properly displayed when I view the article normally, but are properly
displayed if I use <Ctrl>H to display the header and the article.
An example is <news:bcEPe.36663$Il.6082@xxxxxxxxxxxxxxxxxxxxxxxxx>
(available in Google Groups).
The headers contains:
> Subject: Re: How much (£) should i budget for this trip?
and the body contains:
> I appreciate it's not going to be cheap but please read the post I specified
> £ not $!!
> Honestly some people!
(and, as I said, no MIME headers and no in-line encoding (in Subject:)).
When I display the article normally, i.e. without (full) headers), the
(English currency) pound symbol in the Subject: and in the second body-
line come out as question marks.
However if I use <Ctrl>H, to display the full headers and then the
body, both pound symbols are displayed correctly (i.e. as pound
symbols).
I know that this is an incorrect article, because it should mention
the correct character set (ISO 8859/1) in both the Subject: and MIME
headers, but I wonder why the behaviour without/with <Ctrl>H is
different. FWIW, my 'DOS' Code Page is set to 850, which, AFAIK, is the
correct one for ISO 8859/1.
Any idea what could cause this difference in behaviour? (And if so,
how to fix it?)
First I thought that these incorrect Outlook Express articles were a
one off, but apparently (see the mentioned thread (if you have the
stomach for it :-)) OE does the wrong thing (i.e. no MIME/in-line
encoding) by *default* (because it defaults to "Uuencode" instead of
MIME). I have seen the same problem in Dutch groups, so I'd rather fix
the problem on my side than trying to educate the ignorant masses (see
the thread to see where *that* (trying to educate) leads to :-)).
Thanks in advance for any and all responses.
.
- Prev by Date: Re: xnews
- Next by Date: Re: [tin+Cygwin] (In)Correct display of local characters.
- Previous by thread: Re: Newsreaders that support SSL connection
- Next by thread: Re: [tin+Cygwin] (In)Correct display of local characters.
- Index(es):
Relevant Pages
|