<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: CSS and Javascript for more printable HTML</title>
	<atom:link href="http://www.magpiebrain.com/blog/2004/04/20/css-and-javascript-for-more-printable-html/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.magpiebrain.com/blog/2004/04/20/css-and-javascript-for-more-printable-html/</link>
	<description>Sam Newman's blog</description>
	<pubDate>Fri, 21 Nov 2008 19:26:36 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>By: Sam Newman</title>
		<link>http://www.magpiebrain.com/blog/2004/04/20/css-and-javascript-for-more-printable-html/#comment-318</link>
		<dc:creator>Sam Newman</dc:creator>
		<pubDate>Wed, 21 Apr 2004 13:46:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.magpiebrain.com/2004/04/20/css-and-javascript-for-more-printable-html/#comment-318</guid>
		<description>Right, magpiebrain.com now resolves in the same way as www.magpiebrain.com. I fixed one XHTML issue on the individual entry page and fixed all the CSS issues, however the link you posted in your comment screws things up as it includes unescaped ampersands...
</description>
		<content:encoded><![CDATA[<p>Right, magpiebrain.com now resolves in the same way as <a href="http://www.magpiebrain.com"  rel="nofollow">http://www.magpiebrain.com</a>. I fixed one <acronym title="eXtensible HyperText Markup Language - HTML reformulated as XML">XHTML</acronym> issue on the individual entry page and fixed all the <acronym title="Cascading Style Sheets">CSS</acronym> issues, however the link you posted in your comment screws things up as it includes unescaped ampersands&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sam Newman</title>
		<link>http://www.magpiebrain.com/blog/2004/04/20/css-and-javascript-for-more-printable-html/#comment-317</link>
		<dc:creator>Sam Newman</dc:creator>
		<pubDate>Wed, 21 Apr 2004 13:11:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.magpiebrain.com/2004/04/20/css-and-javascript-for-more-printable-html/#comment-317</guid>
		<description>Ta for the feedback Jez - I do indeed owe you some hula hoops. If you can arrange that pint with Hani you might get them quicker...

magpie--
[0] - Understood. I'll have to think of a way to hide the link from non-javascript browsers
[1] - Limitation of the current layout technique. I think I can fix it using floats rather than the current method - will look into it
[2] - Virtual hosting problem, can sort that quite quickly. Its on my todo list
[3] - The black line appears on IE? There shouldn't be one - the print.css should remove the backgrund image. Getting ciontextual information is promblematic due to the way the DOM tree works. I could extract it if the link occured in a p tag, but in other circumstances it could result in sme strange results...
[4] - Will sort those validation issues.
[5] - Amaya I'll have to look into.

So much of the redesign was inspired from other sources - I'll be updating the Colophon accordingly in the next coulple of days.</description>
		<content:encoded><![CDATA[<p>Ta for the feedback Jez - I do indeed owe you some hula hoops. If you can arrange that pint with Hani you might get them quicker&#8230;</p>
<p>magpie&#8212;<br />
[0] - Understood. I&#8217;ll have to think of a way to hide the link from non-javascript browsers<br />
[1] - Limitation of the current layout technique. I think I can fix it using floats rather than the current method - will look into it<br />
[2] - Virtual hosting problem, can sort that quite quickly. Its on my todo list<br />
[3] - The black line appears on <acronym title="Internet Explorer">IE</acronym>? There shouldn&#8217;t be one - the print.css should remove the backgrund image. Getting ciontextual information is promblematic due to the way the <acronym title="Document Object Model">DOM</acronym> tree works. I could extract it if the link occured in a p tag, but in other circumstances it could result in sme strange results&#8230;<br />
[4] - Will sort those validation issues.<br />
[5] - Amaya I&#8217;ll have to look into.</p>
<p>So much of the redesign was inspired from other sources - I&#8217;ll be updating the Colophon accordingly in the next coulple of days.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jez</title>
		<link>http://www.magpiebrain.com/blog/2004/04/20/css-and-javascript-for-more-printable-html/#comment-316</link>
		<dc:creator>jez</dc:creator>
		<pubDate>Tue, 20 Apr 2004 19:54:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.magpiebrain.com/2004/04/20/css-and-javascript-for-more-printable-html/#comment-316</guid>
		<description>magpie--
 [0] The print option didn't work at all in lynx_w32.2.8.2rel.1 nor w3m-0.1.9-CYGWIN.i686-mouse-en (no javascript)
 [1] When viewing www.magpiebrain.com in a limited text based browser, the blogroll is above the changing content.
 [2] http://magpiebrain.com doesn't work as it should.
 [3] in IE 6.0 the (print) bookmarks are straddled over the left thick black vertical line.  Can javascript fetch the first paragraph of each page, would be nice to get an idea of the link content (think javablogs style) {probably not a javascript/efficient idea}
 [4] newstyle.css has 3 validation errors - http://jigsaw.w3.org/css-validator/validator?uri=http%3A%2F%2Fwww.magpiebrain.com&#38;warning=1&#38;profile=css2&#38;usermedium=all
 [5] Amaya 8.4 made it look... different, the footlinks on each article are up the creak and the search box is wonky.
 [6] there is no... gripe [6]

magpie++
 [0] looks really sweet, just like the lovely stuff in the zen garden.
 [1] lovely colours, and fading backgrounds
 [2] articles and ideas cool as ever :-)
 [3] site and print stuff looked really nice in Mozilla5 .0 {build:2002053012}
 [4] you are 100% strict xhtml compliant http://validator.w3.org/check?uri=http%3A%2F%2Fwww.magpiebrain.com
 [5] you owe me some hula hoops...</description>
		<content:encoded><![CDATA[<p>magpie&#8212;<br />
 [0] The print option didn&#8217;t work at all in lynx_w32.2.8.2rel.1 nor w3m-0.1.9-CYGWIN.i686-mouse-en (no javascript)<br />
 [1] When viewing <a href="http://www.magpiebrain.com"  rel="nofollow">http://www.magpiebrain.com</a> in a limited text based browser, the blogroll is above the changing content.<br />
 [2] <a href="http://magpiebrain.com"  rel="nofollow">http://magpiebrain.com</a> doesn&#8217;t work as it should.<br />
 [3] in <acronym title="Internet Explorer">IE</acronym> 6.0 the (print) bookmarks are straddled over the left thick black vertical line.  Can javascript fetch the first paragraph of each page, would be nice to get an idea of the link content (think javablogs style) {probably not a javascript/efficient idea}<br />
 [4] newstyle.css has 3 validation errors - <a href="http://jigsaw.w3.org/css-validator/validator?uri=http%3A%2F%2Fwww.magpiebrain.com&amp;warning=1&amp;profile=css2&amp;usermedium=all"  rel="nofollow">http://jigsaw.w3.org/css-validator/validator?uri=<acronym title="HyperText Transfer Protocol">HTTP</acronym>%3A%2F%2Fwww.magpiebrain.com&amp;warning=1&amp;profile=css2&amp;usermedium=all</a><br />
 [5] Amaya 8.4 made it look&#8230; different, the footlinks on each article are up the creak and the search box is wonky.<br />
 [6] there is no&#8230; gripe [6]</p>
<p>magpie++<br />
 [0] looks really sweet, just like the lovely stuff in the zen garden.<br />
 [1] lovely colours, and fading backgrounds<br />
 [2] articles and ideas cool as ever :-)<br />
 [3] site and print stuff looked really nice in Mozilla5 .0 {build:2002053012}<br />
 [4] you are 100% strict <acronym title="eXtensible HyperText Markup Language - HTML reformulated as XML">XHTML</acronym> compliant <a href="http://validator.w3.org/check?uri=http%3A%2F%2Fwww.magpiebrain.com"  rel="nofollow">http://validator.w3.org/check?uri=<acronym title="HyperText Transfer Protocol">HTTP</acronym>%3A%2F%2Fwww.magpiebrain.com</a><br />
 [5] you owe me some hula hoops&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sam Newman</title>
		<link>http://www.magpiebrain.com/blog/2004/04/20/css-and-javascript-for-more-printable-html/#comment-315</link>
		<dc:creator>Sam Newman</dc:creator>
		<pubDate>Tue, 20 Apr 2004 17:10:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.magpiebrain.com/2004/04/20/css-and-javascript-for-more-printable-html/#comment-315</guid>
		<description>Joe such a change should be trivial - I would actually like to refactor the code to allow it to be easily tailored for specific uses.</description>
		<content:encoded><![CDATA[<p>Joe such a change should be trivial - I would actually like to refactor the code to allow it to be easily tailored for specific uses.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joe Cheng</title>
		<link>http://www.magpiebrain.com/blog/2004/04/20/css-and-javascript-for-more-printable-html/#comment-314</link>
		<dc:creator>Joe Cheng</dc:creator>
		<pubDate>Tue, 20 Apr 2004 16:56:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.magpiebrain.com/2004/04/20/css-and-javascript-for-more-printable-html/#comment-314</guid>
		<description>This is very cool!

Might be useful to have the links still be links, just with the addition of the footnote.  First of all, the set of words that are part of the link might be significant; if you take away the underline you could be losing information.  Secondly, sometimes I use the printable view even if I'm not printing, because the contrast is usually better... would be cool if the links were fully functional (I see that you can click on the footnote reference, but that's a much smaller target).</description>
		<content:encoded><![CDATA[<p>This is very cool!</p>
<p>Might be useful to have the links still be links, just with the addition of the footnote.  First of all, the set of words that are part of the link might be significant; if you take away the underline you could be losing information.  Secondly, sometimes I use the printable view even if I&#8217;m not printing, because the contrast is usually better&#8230; would be cool if the links were fully functional (I see that you can click on the footnote reference, but that&#8217;s a much smaller target).</p>
]]></content:encoded>
	</item>
</channel>
</rss>
