Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Oliver Jennrich <oliver.jennrich@gmx.net>
To: info-gnus-english@gnu.org
Subject: Problems displaying Groundhog postings
Date: Sat, 09 Jun 2012 17:02:58 +0200	[thread overview]
Message-ID: <yg1y5nw7ckd.fsf@ID-371.news.uni-berlin.de> (raw)


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

             reply	other threads:[~2012-06-09 15:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-09 15:02 Oliver Jennrich [this message]
2012-06-10 12:10 ` Pedro Silva

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=yg1y5nw7ckd.fsf@ID-371.news.uni-berlin.de \
    --to=oliver.jennrich@gmx.net \
    --cc=info-gnus-english@gnu.org \
    /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).