<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Hypertext &amp; Print.css</title>
	<atom:link href="http://www.8164.org/hypertext-print-css/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.8164.org/hypertext-print-css/</link>
	<description>Jin Yang&#039;s blog on web design, philosophy of Taoism and life in general.</description>
	<lastBuildDate>Thu, 11 Mar 2010 15:15:36 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Using Print Stylesheets Effectively &#171; Night Prayer</title>
		<link>http://www.8164.org/hypertext-print-css/comment-page-1/#comment-925</link>
		<dc:creator>Using Print Stylesheets Effectively &#171; Night Prayer</dc:creator>
		<pubDate>Sun, 21 Dec 2008 14:41:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.8164.org/?p=784#comment-925</guid>
		<description>[...] http://www.8164.org/hypertext-print-css/ [...]</description>
		<content:encoded><![CDATA[<p>[...] <a href="http://www.8164.org/hypertext-print-css/" rel="nofollow">http://www.8164.org/hypertext-print-css/</a> [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark Aplet</title>
		<link>http://www.8164.org/hypertext-print-css/comment-page-1/#comment-399</link>
		<dc:creator>Mark Aplet</dc:creator>
		<pubDate>Tue, 04 Nov 2008 02:10:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.8164.org/?p=784#comment-399</guid>
		<description>I was actually trying to figure this out using jQuery but never came to a conclusion though. It should be pretty easy (for someone more experienced than I) to pull the links from a divor the entire page and stick them into a content footer. I am sure if you put this idea before the jquery folks they could probably figure it out in no time.</description>
		<content:encoded><![CDATA[<p>I was actually trying to figure this out using jQuery but never came to a conclusion though. It should be pretty easy (for someone more experienced than I) to pull the links from a divor the entire page and stick them into a content footer. I am sure if you put this idea before the jquery folks they could probably figure it out in no time.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jin</title>
		<link>http://www.8164.org/hypertext-print-css/comment-page-1/#comment-397</link>
		<dc:creator>Jin</dc:creator>
		<pubDate>Tue, 04 Nov 2008 01:18:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.8164.org/?p=784#comment-397</guid>
		<description>@Quatl, thanks! Meanwhile I&#039;ll work on a client side version or an asp.net version of time permits.</description>
		<content:encoded><![CDATA[<p>@Quatl, thanks! Meanwhile I&#8217;ll work on a client side version or an asp.net version of time permits.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Quatl</title>
		<link>http://www.8164.org/hypertext-print-css/comment-page-1/#comment-396</link>
		<dc:creator>Quatl</dc:creator>
		<pubDate>Tue, 04 Nov 2008 01:01:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.8164.org/?p=784#comment-396</guid>
		<description>Actually this is an interesting problem, and I need PHP and AJAX practice.  If I produce something usable (with either or both methods) before being distracted by the next shiny object I&#039;ll send you the code.</description>
		<content:encoded><![CDATA[<p>Actually this is an interesting problem, and I need PHP and AJAX practice.  If I produce something usable (with either or both methods) before being distracted by the next shiny object I&#8217;ll send you the code.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Quatl</title>
		<link>http://www.8164.org/hypertext-print-css/comment-page-1/#comment-395</link>
		<dc:creator>Quatl</dc:creator>
		<pubDate>Tue, 04 Nov 2008 00:57:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.8164.org/?p=784#comment-395</guid>
		<description>&quot; Listing URLs as footnotes is a better choice. But this requires extra custom job for each page that goes beyond CSS.&quot;

That&#039;s what PHP (or what ever boat flotation device you prefer) is for.  
Just parse the links in the article out into an array, and generate the footnotes from that.</description>
		<content:encoded><![CDATA[<p>&#8221; Listing URLs as footnotes is a better choice. But this requires extra custom job for each page that goes beyond CSS.&#8221;</p>
<p>That&#8217;s what PHP (or what ever boat flotation device you prefer) is for.<br />
Just parse the links in the article out into an array, and generate the footnotes from that.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jin</title>
		<link>http://www.8164.org/hypertext-print-css/comment-page-1/#comment-385</link>
		<dc:creator>Jin</dc:creator>
		<pubDate>Sun, 02 Nov 2008 19:17:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.8164.org/?p=784#comment-385</guid>
		<description>@Bryan, Joshua, Victor, Mark

Thank you for the comments. I agree in most cases, this feature isn&#039;t needed. 

Right now I&#039;m trying to think of a solution for sites that do need it. Namely the government sites I work on, targeted for attorneys and local agencies. Currently the links are spelled out fully in HTML. It not only they clutter the screen, but also not as friendly to read when printed out. I want to create a footnote type of solution for pages that do need this.

There are couple of ways of doing it. First would be doing it on the server side to generate a block of footnotes that are hidden to the screen(some pages&#039; content are static and some are dynamic), and have the inline links with names and labeled with a numeric citation. This method would eliminate browser compatibility issue, however it&#039;s quite labor intensive and not as maintenable.

The other method is to do it on the front-end, using Javascript. In the defined DIV that contains the article links, loop through all the A tags with href attributes, and manually construct a HTML string as a print only block. This method is re-usable on every page and very easy to implement and maintain. However, it runs into accessibility issues when people use IE or have JS turned off.</description>
		<content:encoded><![CDATA[<p>@Bryan, Joshua, Victor, Mark</p>
<p>Thank you for the comments. I agree in most cases, this feature isn&#8217;t needed. </p>
<p>Right now I&#8217;m trying to think of a solution for sites that do need it. Namely the government sites I work on, targeted for attorneys and local agencies. Currently the links are spelled out fully in HTML. It not only they clutter the screen, but also not as friendly to read when printed out. I want to create a footnote type of solution for pages that do need this.</p>
<p>There are couple of ways of doing it. First would be doing it on the server side to generate a block of footnotes that are hidden to the screen(some pages&#8217; content are static and some are dynamic), and have the inline links with names and labeled with a numeric citation. This method would eliminate browser compatibility issue, however it&#8217;s quite labor intensive and not as maintenable.</p>
<p>The other method is to do it on the front-end, using Javascript. In the defined DIV that contains the article links, loop through all the A tags with href attributes, and manually construct a HTML string as a print only block. This method is re-usable on every page and very easy to implement and maintain. However, it runs into accessibility issues when people use IE or have JS turned off.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark Aplet</title>
		<link>http://www.8164.org/hypertext-print-css/comment-page-1/#comment-384</link>
		<dc:creator>Mark Aplet</dc:creator>
		<pubDate>Sun, 02 Nov 2008 18:20:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.8164.org/?p=784#comment-384</guid>
		<description>When I read about this technique on ALA I started to include this in my print style sheet. I thought it would be useful to people. Soon after I started launching sites with this method I actually started to get complaints that the page was messed up when printing. Turns out the lack of familiarity with this approach left many people confused or upset. My approach now is to only print url&#039;s for clients that request this feature, or when it is absolutely necessary (rarely) to understand the context of the article.</description>
		<content:encoded><![CDATA[<p>When I read about this technique on ALA I started to include this in my print style sheet. I thought it would be useful to people. Soon after I started launching sites with this method I actually started to get complaints that the page was messed up when printing. Turns out the lack of familiarity with this approach left many people confused or upset. My approach now is to only print url&#8217;s for clients that request this feature, or when it is absolutely necessary (rarely) to understand the context of the article.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Useful Links (01/11/2008) &#124; Apramana</title>
		<link>http://www.8164.org/hypertext-print-css/comment-page-1/#comment-376</link>
		<dc:creator>Useful Links (01/11/2008) &#124; Apramana</dc:creator>
		<pubDate>Sat, 01 Nov 2008 04:49:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.8164.org/?p=784#comment-376</guid>
		<description>[...] Hypertext &amp; Print.css [...]</description>
		<content:encoded><![CDATA[<p>[...] Hypertext &#38; Print.css [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Victor</title>
		<link>http://www.8164.org/hypertext-print-css/comment-page-1/#comment-369</link>
		<dc:creator>Victor</dc:creator>
		<pubDate>Fri, 31 Oct 2008 01:18:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.8164.org/?p=784#comment-369</guid>
		<description>I personally ignore most URLs in any print media unless it&#039;s a simple URL such as www.microsoft.com or www.TaskPilot.com.

Printing a long URL takes away from the readability to me of anything I&#039;m trying to understand or enjoy.</description>
		<content:encoded><![CDATA[<p>I personally ignore most URLs in any print media unless it&#8217;s a simple URL such as <a href="http://www.microsoft.com" rel="nofollow">http://www.microsoft.com</a> or <a href="http://www.TaskPilot.com" rel="nofollow">http://www.TaskPilot.com</a>.</p>
<p>Printing a long URL takes away from the readability to me of anything I&#8217;m trying to understand or enjoy.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joshua Richardson</title>
		<link>http://www.8164.org/hypertext-print-css/comment-page-1/#comment-368</link>
		<dc:creator>Joshua Richardson</dc:creator>
		<pubDate>Thu, 30 Oct 2008 15:09:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.8164.org/?p=784#comment-368</guid>
		<description>As soon as I read this I also thought of adding footnotes, but I guess it comes down to how good you are at programming (though I&#039;d bet there is a plugin that does this already).
This means that you&#039;ll need a link to a printer friendly version and comes with all sorts of other issues. I.e. the fact that the links will appear on the final printed page and not at the bottom of each and changing this is near impossible.</description>
		<content:encoded><![CDATA[<p>As soon as I read this I also thought of adding footnotes, but I guess it comes down to how good you are at programming (though I&#8217;d bet there is a plugin that does this already).<br />
This means that you&#8217;ll need a link to a printer friendly version and comes with all sorts of other issues. I.e. the fact that the links will appear on the final printed page and not at the bottom of each and changing this is near impossible.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
