From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: ding@gnus.org
Subject: Re: RSS setup (encoding and link problems)
Date: Sun, 05 Dec 2010 22:27:43 +0100 [thread overview]
Message-ID: <m3r5dvewq8.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <87r5dv9apd.fsf@gmx.co.uk>
Johnny <yggdrasil@gmx.co.uk> writes:
> I suspect this may have to do with smartquotes? Or is it dependent on
> the gnus-article-wash-function (currently nil and mm-text-html-renderer
> set to 'lynx')?
I would suggest installing w3m and emacs-w3m -- they provide quite good
HTML rendering.
> I also tried to view the source (C-u g) and wash html (W h) in an
> attempt to get wiser, alas to no avail! However, this led me to suspect
> maybe mm-text-html-renderer needs to be set to something else?
>
> For example I get
> | Firefox | Gnus | C-u g, W h |
> |-------------+----------------------------------+------------|
> | ' | \303\242\342\202\254\342\204\242 | =E2=80=99 |
> | " | \303\242\342\202\254\305\223 | =E2=80=9C |
> | - | \303\242\342\202\254\342\200\234 | =E2=80=93 |
> | (linebreak) | \303\302 | =C2=A0 |
> |-------------+----------------------------------+------------|
Hm. It does look like something is getting encoded twice. But I
haven't used lynx as an html renderer in yonks. Anybody have any ideas?
> Less important, but maybe related is that (embedded) links seem dead in
> the articles, could this also be related to the above, and how to
> remedy? (The [1], [2], ... are visible but cannot be followed)
Yeah, the lynx renderer doesn't support links. The emacs-w3m one does,
though.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next prev parent reply other threads:[~2010-12-05 21:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-05 21:22 Johnny
2010-12-05 21:27 ` Lars Magne Ingebrigtsen [this message]
2010-12-05 21:40 ` Johnny
2010-12-05 22:58 ` Johnny
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=m3r5dvewq8.fsf@quimbies.gnus.org \
--to=larsi@gnus.org \
--cc=ding@gnus.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).