Problems displaying Groundhog postings

Problems displaying Groundhog postings

[Oliver Jennrich]

Hi all,

I experience a very odd problem in connection with postings that are
created by the grundhog newsreader for android.

First, I need a sanity check. If you could please check MID
<almarsoft.311987452218503965@news.individual.de> (a posting in the
german-speaking newsgroup de.rec.fotografie). If I open that posting,
the umlauts and the sharp-s are displayed as e.g. "\374". 

Naturally, I assumed an encoding problem, but the posting is correctly
encoded as ISO-8859-15. My gnus has no problems with similarly encoded
postings from other authors. 

I'd dismiss that as some oddity, if it wasn't for the case that another
posting, this time correctly encoded as utf-8
(<almarsoft.1507468889736478864@news.individual.net>) showed the same
problems, only this time the sharp-s is displayed in two bytes (well, it
is utf, after all) "\303\237".

I crosschecked via Thunderbird and directly via telnet and the body of
both articles looks o.k. Any other posting with ISO-8859-15 or utf8
encoding is fine under gnus as well - just the postings that are created
with Groundhog.

Is this a problem that is likely to exist only locally (e.g. my gnus
installation being f... up) or does anyone else experience that problem
as well?

In any case - does anybody have an idea how to either olve it or at
least diagnose it a bit better? 


-- 
Space - The final frontier

Re: Problems displaying Groundhog postings

[Pedro Silva]

Oliver Jennrich <oliver.jennrich@gmx.net> writes:

> First, I need a sanity check. If you could please check MID
> <almarsoft.311987452218503965@news.individual.de> (a posting in the
> german-speaking newsgroup de.rec.fotografie). If I open that posting,
> the umlauts and the sharp-s are displayed as e.g. "\374". 

> I'd dismiss that as some oddity, if it wasn't for the case that another
> posting, this time correctly encoded as utf-8
> (<almarsoft.1507468889736478864@news.individual.net>) showed the same
> problems, only this time the sharp-s is displayed in two bytes (well, it
> is utf, after all) "\303\237".

> Is this a problem that is likely to exist only locally (e.g. my gnus
> installation being f... up) or does anyone else experience that problem
> as well?

Both articles render correctly here.
-- 
Pedro