Comments on: use.perl journals and full text feeds http://jc.ngo.org.uk/blog/2006/12/05/useperl-journals-and-full-text-feeds/ It'll all be over in 60 days Thu, 28 Aug 2008 02:14:31 +0000 http://wordpress.org/?v=2.0.7 by: pligg.com http://jc.ngo.org.uk/blog/2006/12/05/useperl-journals-and-full-text-feeds/#comment-16660 Fri, 20 Apr 2007 07:54:13 +0000 http://jc.ngo.org.uk/blog/2006/12/05/useperl-journals-and-full-text-feeds/#comment-16660 <strong>Plagger configuration that shows how to create new feed metadata...</strong> Plagger provides great flexibility when processing feeds. This example shows how to create a new feed by scraping an existing web site, and post-processing the scraped HTML to upgrade content in the HTML in to metadata in the feed.... Plagger configuration that shows how to create new feed metadata…

Plagger provides great flexibility when processing feeds. This example shows how to create a new feed by scraping an existing web site, and post-processing the scraped HTML to upgrade content in the HTML in to metadata in the feed….

]]> by: Matthew Wilson http://jc.ngo.org.uk/blog/2006/12/05/useperl-journals-and-full-text-feeds/#comment-1014 Thu, 07 Dec 2006 16:04:58 +0000 http://jc.ngo.org.uk/blog/2006/12/05/useperl-journals-and-full-text-feeds/#comment-1014 I don't see this happening on other feeds in Google Reader (although that doesn't prove it's not a Reader bug of course). I don’t see this happening on other feeds in Google Reader (although that doesn’t prove it’s not a Reader bug of course).

]]> by: Tatsuhiko Miyagawa http://jc.ngo.org.uk/blog/2006/12/05/useperl-journals-and-full-text-feeds/#comment-1000 Wed, 06 Dec 2006 22:22:12 +0000 http://jc.ngo.org.uk/blog/2006/12/05/useperl-journals-and-full-text-feeds/#comment-1000 OK here is my response: http://groups.google.com/group/plagger-dev/browse_thread/thread/edbc2c7e4a6e5793/9199bb028256c64e#9199bb028256c64e Summary: double encoding apos here is syntactically correct because we're embedding HTML into XML, if not the most desired. Let me say this is not a bug of Plagger, but it's a problem with the RSS feed itself, since RSS elements don't have a good way to express it's plaintext or HTML marked up (while Atom feed does). And as far as I tested the feed worked fine with Thunderbird and Bloglines, so I suspect it's a Google Reader bug. OK here is my response:

http://groups.google.com/group/plagger-dev/browse_thread/thread/edbc2c7e4a6e5793/9199bb028256c64e#9199bb028256c64e

Summary: double encoding apos here is syntactically correct because we’re embedding HTML into XML, if not the most desired.

Let me say this is not a bug of Plagger, but it’s a problem with the RSS feed itself, since RSS elements don’t have a good way to express it’s plaintext or HTML marked up (while Atom feed does). And as far as I tested the feed worked fine with Thunderbird and Bloglines, so I suspect it’s a Google Reader bug.

]]> by: nik http://jc.ngo.org.uk/blog/2006/12/05/useperl-journals-and-full-text-feeds/#comment-993 Wed, 06 Dec 2006 17:21:27 +0000 http://jc.ngo.org.uk/blog/2006/12/05/useperl-journals-and-full-text-feeds/#comment-993 Ah, yes, it does look like it's being double-encoded. This might be due to the encoding by Plagger, and then a subsequent set of encoding by XML::RSS (which is eventually called to write the .rss file, called by XML::Feed). Ah, yes, it does look like it’s being double-encoded. This might be due to the encoding by Plagger, and then a subsequent set of encoding by XML::RSS (which is eventually called to write the .rss file, called by XML::Feed).

]]> by: Matthew Wilson http://jc.ngo.org.uk/blog/2006/12/05/useperl-journals-and-full-text-feeds/#comment-992 Wed, 06 Dec 2006 16:18:15 +0000 http://jc.ngo.org.uk/blog/2006/12/05/useperl-journals-and-full-text-feeds/#comment-992 Nothing wrong with encoding it once, an HTML "&apos;" and an apostrophe are the same. But it looks like it's getting encoded twice - view source on the RSS shows &amp;apos. But I don't know how all this stuff is dealt with in RSS. Nothing wrong with encoding it once, an HTML “&apos;” and an apostrophe are the same. But it looks like it’s getting encoded twice - view source on the RSS shows &amp;apos. But I don’t know how all this stuff is dealt with in RSS.

]]> by: broquaint http://jc.ngo.org.uk/blog/2006/12/05/useperl-journals-and-full-text-feeds/#comment-989 Wed, 06 Dec 2006 15:08:24 +0000 http://jc.ngo.org.uk/blog/2006/12/05/useperl-journals-and-full-text-feeds/#comment-989 This is marvellous; well done, nik! I'm also experiencing ill-escaped character codes, so I knocked together this shonky GreaseMonkey script to straighten'em out: =UserScript== // @name Google Reader use Perl subscription fixer. // @namespace http://danvsdan.com // @description Currently the escape sequences are little broken, this fixes them. // @include http://www.google.com/reader/view/* // ==/UserScript== function fix_escapes(evt) { // Possibly cache this if possible. if(!document.getElementById('chrome-stream-title').innerHTML.match(/use Perl - Journals/)) return; var node = evt.relatedNode; if(node.innerHTML.match(/&([a-z]+;)/)) node.innerHTML = node.innerHTML.replace(/&([a-z]+;)/g, "&$1"); } document.getElementById('chrome').addEventListener('DOMNodeInserted', fix_escapes, false); This is marvellous; well done, nik! I’m also experiencing ill-escaped character codes, so I knocked together this shonky GreaseMonkey script to straighten’em out:

=UserScript==
// @name Google Reader use Perl subscription fixer.
// @namespace http://danvsdan.com
// @description Currently the escape sequences are little broken, this fixes them.
// @include http://www.google.com/reader/view/*
// ==/UserScript==

function fix_escapes(evt) {
// Possibly cache this if possible.
if(!document.getElementById(’chrome-stream-title’).innerHTML.match(/use Perl - Journals/))
return;
var node = evt.relatedNode;
if(node.innerHTML.match(/&([a-z]+;)/))
node.innerHTML = node.innerHTML.replace(/&([a-z]+;)/g, “&$1″);
}

document.getElementById(’chrome’).addEventListener(’DOMNodeInserted’, fix_escapes, false);

]]> by: nik http://jc.ngo.org.uk/blog/2006/12/05/useperl-journals-and-full-text-feeds/#comment-988 Wed, 06 Dec 2006 14:26:12 +0000 http://jc.ngo.org.uk/blog/2006/12/05/useperl-journals-and-full-text-feeds/#comment-988 This is something in Plagger. More specifically, in <a href="http://plagger.org/trac/browser/trunk/plagger/lib/Plagger/Util.pm" rel="nofollow">Plagger::Util</a>, around line <a href="http://plagger.org/trac/browser/trunk/plagger/lib/Plagger/Util.pm#L176" rel="nofollow">176</a>, the apostrophe is listed as one of the special characters that is automatically encoded to the entity. I'm not sure why it's there. Possibly as defensive code against SQL injection attacks or similar. Googling for "apos" is instructive, and suggests that the numeric entity should really be used instead. I'll bring this up with Miyagawa-san. This is something in Plagger. More specifically, in Plagger::Util, around line 176, the apostrophe is listed as one of the special characters that is automatically encoded to the entity.

I’m not sure why it’s there. Possibly as defensive code against SQL injection attacks or similar. Googling for “apos” is instructive, and suggests that the numeric entity should really be used instead. I’ll bring this up with Miyagawa-san.

]]> by: Matthew Wilson http://jc.ngo.org.uk/blog/2006/12/05/useperl-journals-and-full-text-feeds/#comment-986 Wed, 06 Dec 2006 13:00:04 +0000 http://jc.ngo.org.uk/blog/2006/12/05/useperl-journals-and-full-text-feeds/#comment-986 Looks like I can't spell ampersand either. Let's try again: I'm seeing &apos; instead of '. Looks like I can’t spell ampersand either.

Let’s try again: I’m seeing &apos; instead of ‘.

]]> by: Matthew Wilson http://jc.ngo.org.uk/blog/2006/12/05/useperl-journals-and-full-text-feeds/#comment-983 Wed, 06 Dec 2006 11:57:24 +0000 http://jc.ngo.org.uk/blog/2006/12/05/useperl-journals-and-full-text-feeds/#comment-983 Thanks! When I subscribe in Google Reader though, I'm seeing lots of "'" (in case the comments system mangles that, it should be ampserand, a, p, o, s, semicolon) instead of actual apostrophes. Thanks!

When I subscribe in Google Reader though, I’m seeing lots of “'” (in case the comments system mangles that, it should be ampserand, a, p, o, s, semicolon) instead of actual apostrophes.

]]> by: Adrian Howard http://jc.ngo.org.uk/blog/2006/12/05/useperl-journals-and-full-text-feeds/#comment-982 Wed, 06 Dec 2006 10:07:04 +0000 http://jc.ngo.org.uk/blog/2006/12/05/useperl-journals-and-full-text-feeds/#comment-982 Sooooooper. Thank you :-) Sooooooper. Thank you :-)

]]>