Hi Kim
Any ideas as to why I see this in my newsreader, looks fine on the web
page of course?
I’m sure that some skilled packager must rebuilt freetype2 library
with subpixel hinting support… Maybe Packman or former Suse Guru
guys give us this patched library into repos.
Malcolm <malcolm_nospamlewis@bellsouth.net> expounded:
> Hi Kim
> Any ideas as to why I see this in my newsreader, looks fine on the web
> page of course?
> I’m sure that some skilled packager must rebuilt freetype2 library
> with subpixel hinting support… Maybe Packman or former Suse Guru
> guys give us this patched library into repos.
On Wed, 25 Jun 2008 06:38:38 GMT
DenverD <spam.trap@Texan.dk> wrote:
> > Any ideas as to why I see this in my newsreader, looks fine on the
> > web page of course?
>
>
> what news reader, code page, etc?
>
> here, using Thunderbird [version 2.0.0.14 (20080421]) and ISO-8859-15
> (in and out) i get none of those strange characters…
>
> DenverD
Hi
I use Claws Mail 3.4.0 (GTK+ 2.8.11; x86_64-suse-linux-gnu), encoding
is set to auto and headers show text/plain; charset=ISO-8859-1
There’s a non-breaking space character between each word   I’m no code page expert, but I assume your news reader isn’t translating it correctly. (Is that considered “stating the obvious” ?)
Are you sure you are looking at the correct message? If your Thunderbird
shows that message “correctly”, then your Thunderbird is not working
correctly because the actual fault is at the gateway which can’t handle
quoted printable characters and passes them “as is” without however
telling in that header that such characters are used. As such, a correctly
working newsreader should show the   strings in the message on the
NNTP side.
> Any ideas as to why I see this in my newsreader, looks fine on the web
> page of course?
>
It’s a limitation of the NNTP gateway. Currently, the gateway doesn’t try
to do any code page handling and character code translation. The gateway
simply assumes that both the web and the NNTP side are using ISO-8859-1
In cases where this is not true, that will lead to incorrect display. More
specifically:
For messages posted on the web that do not use ISO-8859-1, vBulletin uses
quoted printable encoding. E.g. special characters are encoded as &#nnn.
The gateway just forwards those in the message body on the NNTP side. As
the NNTP message header does not say that quoted printable encoding is
used, the encoded characters are shown in the &#nnn syntax.
For messages posted on the NNTP side that do not use ISO-8859-1 encoding
and that include special characters, those special characters will be
shown as different characters on the web. This will be most visible for
UTF-8 encoded NNTP messages where one character may be encoded by multiple
bytes and will therefore be shown as multiple garbage characters on the
web.
Marcel Cox wrote:
> DenverD wrote:
>
>> ) i get none of those strange characters…
>
> Are you sure you are looking at the correct message? If your Thunderbird
> shows that message “correctly”, then your Thunderbird is not working
> correctly because the actual fault is at the gateway which can’t handle
> quoted printable characters and passes them “as is” without however
> telling in that header that such characters are used. As such, a
> correctly working newsreader should show the   strings in the
> message on the NNTP side.
>
well, i was looking at what he quoted (which was obviously not looking
too good) or, are you saying that EVERY message i get from these fora
should look like this?
> Malcolm,
>
> > Any ideas as to why I see this in my newsreader, looks fine on the
> > web page of course?
> >
>
> It’s a limitation of the NNTP gateway. Currently, the gateway doesn’t
> try to do any code page handling and character code translation. The
> gateway simply assumes that both the web and the NNTP side are using
> ISO-8859-1 In cases where this is not true, that will lead to
> incorrect display. More specifically:
>
> For messages posted on the web that do not use ISO-8859-1, vBulletin
> uses quoted printable encoding. E.g. special characters are encoded
> as &#nnn. The gateway just forwards those in the message body on the
> NNTP side. As the NNTP message header does not say that quoted
> printable encoding is used, the encoded characters are shown in the
> &#nnn syntax.
>
> For messages posted on the NNTP side that do not use ISO-8859-1
> encoding and that include special characters, those special
> characters will be shown as different characters on the web. This
> will be most visible for UTF-8 encoded NNTP messages where one
> character may be encoded by multiple bytes and will therefore be
> shown as multiple garbage characters on the web.
>
Hi Marcel
Many thanks for the detailed information. It only happens every now and
again. I wonder if it’s the users web browser they use to post?
> Many thanks for the detailed information. It only happens every now and
> again. I wonder if it’s the users web browser they use to post?
>
I’m sure it’s not the web browser itself, but rather the fact that the
author probably copied and pasted the text from a source that had the
special characters.
