<?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: Culture clashes II: PDF, XML and what&#8217;s in it for me?</title>
	<atom:link href="http://walt.lishost.org/2009/06/culture-clashes-ii-pdf-xml-and-whats-in-it-for-me/feed/" rel="self" type="application/rss+xml" />
	<link>http://walt.lishost.org/2009/06/culture-clashes-ii-pdf-xml-and-whats-in-it-for-me/</link>
	<description>The library voice of the radical middle.</description>
	<lastBuildDate>Thu, 23 May 2013 16:58:01 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>By: Walt Crawford</title>
		<link>http://walt.lishost.org/2009/06/culture-clashes-ii-pdf-xml-and-whats-in-it-for-me/comment-page-1/#comment-39630</link>
		<dc:creator>Walt Crawford</dc:creator>
		<pubDate>Mon, 29 Jun 2009 00:41:37 +0000</pubDate>
		<guid isPermaLink="false">http://walt.lishost.org/2009/06/culture-clashes-ii-pdf-xml-and-whats-in-it-for-me/#comment-39630</guid>
		<description><![CDATA[I think you&#039;re right, although &quot;two cultures&quot; is probably an oversimplification. (Aren&#039;t most dichotomies?)
]]></description>
		<content:encoded><![CDATA[<p>I think you&#8217;re right, although &#8220;two cultures&#8221; is probably an oversimplification. (Aren&#8217;t most dichotomies?)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: zayıflama</title>
		<link>http://walt.lishost.org/2009/06/culture-clashes-ii-pdf-xml-and-whats-in-it-for-me/comment-page-1/#comment-39629</link>
		<dc:creator>zayıflama</dc:creator>
		<pubDate>Sun, 28 Jun 2009 12:46:03 +0000</pubDate>
		<guid isPermaLink="false">http://walt.lishost.org/2009/06/culture-clashes-ii-pdf-xml-and-whats-in-it-for-me/#comment-39629</guid>
		<description><![CDATA[I think we&#039;re seeing some of the culture clash going on here.
]]></description>
		<content:encoded><![CDATA[<p>I think we&#8217;re seeing some of the culture clash going on here.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Walt Crawford</title>
		<link>http://walt.lishost.org/2009/06/culture-clashes-ii-pdf-xml-and-whats-in-it-for-me/comment-page-1/#comment-39628</link>
		<dc:creator>Walt Crawford</dc:creator>
		<pubDate>Sat, 27 Jun 2009 21:04:29 +0000</pubDate>
		<guid isPermaLink="false">http://walt.lishost.org/2009/06/culture-clashes-ii-pdf-xml-and-whats-in-it-for-me/#comment-39628</guid>
		<description><![CDATA[[If you happened by here when there was a comment #10 echoing exactly the same issues as comment #4: It&#039;s not gone because it&#039;s raising disadvantages of PDF or because it&#039;s redundant. It&#039;s gone because it&#039;s spam: The content was taken directly from another comment in order to legitimate the link behind the poster&#039;s name, thus gaining link love for the spam link. Didn&#039;t work for long; too bad the blog software didn&#039;t flag it immediately!]
]]></description>
		<content:encoded><![CDATA[<p>[If you happened by here when there was a comment #10 echoing exactly the same issues as comment #4: It's not gone because it's raising disadvantages of PDF or because it's redundant. It's gone because it's spam: The content was taken directly from another comment in order to legitimate the link behind the poster's name, thus gaining link love for the spam link. Didn't work for long; too bad the blog software didn't flag it immediately!]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Walt Crawford</title>
		<link>http://walt.lishost.org/2009/06/culture-clashes-ii-pdf-xml-and-whats-in-it-for-me/comment-page-1/#comment-39627</link>
		<dc:creator>Walt Crawford</dc:creator>
		<pubDate>Fri, 26 Jun 2009 18:55:24 +0000</pubDate>
		<guid isPermaLink="false">http://walt.lishost.org/2009/06/culture-clashes-ii-pdf-xml-and-whats-in-it-for-me/#comment-39627</guid>
		<description><![CDATA[folbec: You raise a slightly different but cogent point. My problem with the Semantic Web is that, except for specialized cases, it requires far too much work during writing/creation to be likely to have good data. But yes, it also assumes &lt;b&gt;honest&lt;/b&gt; and non-gamed data.
I&#039;ve avoided it on this new site so far, but I&#039;ve been, um, skeptical of the SW since first hearing about it--and, on the one occasion when I met Sir Tim B-L (we were both speaking on the same program), I said so. A cordial discussion that certainly didn&#039;t change his mind--but didn&#039;t convince me either. (Hey, I&#039;ll never be famous, but I&#039;ve had brushes...consistently demonstrating that I&#039;m no good at being an Impressed Follower.)
]]></description>
		<content:encoded><![CDATA[<p>folbec: You raise a slightly different but cogent point. My problem with the Semantic Web is that, except for specialized cases, it requires far too much work during writing/creation to be likely to have good data. But yes, it also assumes <b>honest</b> and non-gamed data.<br />
I&#8217;ve avoided it on this new site so far, but I&#8217;ve been, um, skeptical of the SW since first hearing about it&#8211;and, on the one occasion when I met Sir Tim B-L (we were both speaking on the same program), I said so. A cordial discussion that certainly didn&#8217;t change his mind&#8211;but didn&#8217;t convince me either. (Hey, I&#8217;ll never be famous, but I&#8217;ve had brushes&#8230;consistently demonstrating that I&#8217;m no good at being an Impressed Follower.)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: folbec</title>
		<link>http://walt.lishost.org/2009/06/culture-clashes-ii-pdf-xml-and-whats-in-it-for-me/comment-page-1/#comment-39626</link>
		<dc:creator>folbec</dc:creator>
		<pubDate>Fri, 26 Jun 2009 15:07:26 +0000</pubDate>
		<guid isPermaLink="false">http://walt.lishost.org/2009/06/culture-clashes-ii-pdf-xml-and-whats-in-it-for-me/#comment-39626</guid>
		<description><![CDATA[&quot;But, you know, I think you want more than HTML. I think you want semantics--XML or better. &quot;
The trouble with the &quot;semantic web&quot; is that the first day it starts gaining traction, people will start gaming the semantic tags to gain better exposure (since exposure means money and fame), the same way they are gaming the search engine hint keywords, and this will turn into a ugly arm race that will destroy the whole idea (getting significant, non sponsored, results in google is already difficult on a number of subjects, and google is AFAIK mostly discarding the search engine hint keywords of HTML)
]]></description>
		<content:encoded><![CDATA[<p>&#8220;But, you know, I think you want more than HTML. I think you want semantics&#8211;XML or better. &#8221;<br />
The trouble with the &#8220;semantic web&#8221; is that the first day it starts gaining traction, people will start gaming the semantic tags to gain better exposure (since exposure means money and fame), the same way they are gaming the search engine hint keywords, and this will turn into a ugly arm race that will destroy the whole idea (getting significant, non sponsored, results in google is already difficult on a number of subjects, and google is AFAIK mostly discarding the search engine hint keywords of HTML)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: laura</title>
		<link>http://walt.lishost.org/2009/06/culture-clashes-ii-pdf-xml-and-whats-in-it-for-me/comment-page-1/#comment-39625</link>
		<dc:creator>laura</dc:creator>
		<pubDate>Thu, 25 Jun 2009 22:04:46 +0000</pubDate>
		<guid isPermaLink="false">http://walt.lishost.org/2009/06/culture-clashes-ii-pdf-xml-and-whats-in-it-for-me/#comment-39625</guid>
		<description><![CDATA[Your html versions of C&amp;I (plus the Readability plugin for Firefox, which makes the margins short enough for easy reading) mean that I can read it without printing it out, which I sometimes prefer. The PDFs are gorgeous, and I do appreciate your attention to typography, but sometimes I just don&#039;t want to print things. But, you know, I deal. If the content is good enough, a reasonable person will generally find some way to deal with the form.
]]></description>
		<content:encoded><![CDATA[<p>Your html versions of C&#038;I (plus the Readability plugin for Firefox, which makes the margins short enough for easy reading) mean that I can read it without printing it out, which I sometimes prefer. The PDFs are gorgeous, and I do appreciate your attention to typography, but sometimes I just don&#8217;t want to print things. But, you know, I deal. If the content is good enough, a reasonable person will generally find some way to deal with the form.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Walt Crawford</title>
		<link>http://walt.lishost.org/2009/06/culture-clashes-ii-pdf-xml-and-whats-in-it-for-me/comment-page-1/#comment-39624</link>
		<dc:creator>Walt Crawford</dc:creator>
		<pubDate>Thu, 25 Jun 2009 18:45:16 +0000</pubDate>
		<guid isPermaLink="false">http://walt.lishost.org/2009/06/culture-clashes-ii-pdf-xml-and-whats-in-it-for-me/#comment-39624</guid>
		<description><![CDATA[...or &quot;set of tools&quot; with the s, if you prefer. Sigh.
]]></description>
		<content:encoded><![CDATA[<p>&#8230;or &#8220;set of tools&#8221; with the s, if you prefer. Sigh.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Walt Crawford</title>
		<link>http://walt.lishost.org/2009/06/culture-clashes-ii-pdf-xml-and-whats-in-it-for-me/comment-page-1/#comment-39623</link>
		<dc:creator>Walt Crawford</dc:creator>
		<pubDate>Thu, 25 Jun 2009 18:43:00 +0000</pubDate>
		<guid isPermaLink="false">http://walt.lishost.org/2009/06/culture-clashes-ii-pdf-xml-and-whats-in-it-for-me/#comment-39623</guid>
		<description><![CDATA[Greg: You can set PDF to incorporate all typefaces--you have to do that to do books through Lulu, for example--in which case the results should be identical in all cases.
Otherwise--well, you have your preferred set of tool. &quot;Why you ever need a &#039;word processor&#039; anyway&quot; may be fine for you, but not for me. Different people, different purposes, different tools. Fine--unless/until you&#039;re saying that it&#039;s *inappropriate* for me to use the tools I prefer. Or that what&#039;s easy for you is automatically easy for a typical writer.
I think we&#039;re seeing some of the culture clash going on here.
]]></description>
		<content:encoded><![CDATA[<p>Greg: You can set PDF to incorporate all typefaces&#8211;you have to do that to do books through Lulu, for example&#8211;in which case the results should be identical in all cases.<br />
Otherwise&#8211;well, you have your preferred set of tool. &#8220;Why you ever need a &#8216;word processor&#8217; anyway&#8221; may be fine for you, but not for me. Different people, different purposes, different tools. Fine&#8211;unless/until you&#8217;re saying that it&#8217;s *inappropriate* for me to use the tools I prefer. Or that what&#8217;s easy for you is automatically easy for a typical writer.<br />
I think we&#8217;re seeing some of the culture clash going on here.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: thiotimoline</title>
		<link>http://walt.lishost.org/2009/06/culture-clashes-ii-pdf-xml-and-whats-in-it-for-me/comment-page-1/#comment-39622</link>
		<dc:creator>thiotimoline</dc:creator>
		<pubDate>Thu, 25 Jun 2009 11:05:30 +0000</pubDate>
		<guid isPermaLink="false">http://walt.lishost.org/2009/06/culture-clashes-ii-pdf-xml-and-whats-in-it-for-me/#comment-39622</guid>
		<description><![CDATA[The problem with .pdfs is that they either open in another window or open within Acrobat in the browser. Having multiple windows is often inconvenient, while Acrobat within Firefox breaks standard key combinations (such as ctrl+t to open a new tab). I would much rather have the option of reading something a bit uglier without having to deal with either of these situations, if the link is primarily text-based; I agree that .pdfs are good for maps and similar.
]]></description>
		<content:encoded><![CDATA[<p>The problem with .pdfs is that they either open in another window or open within Acrobat in the browser. Having multiple windows is often inconvenient, while Acrobat within Firefox breaks standard key combinations (such as ctrl+t to open a new tab). I would much rather have the option of reading something a bit uglier without having to deal with either of these situations, if the link is primarily text-based; I agree that .pdfs are good for maps and similar.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Greg Laden</title>
		<link>http://walt.lishost.org/2009/06/culture-clashes-ii-pdf-xml-and-whats-in-it-for-me/comment-page-1/#comment-39621</link>
		<dc:creator>Greg Laden</dc:creator>
		<pubDate>Thu, 25 Jun 2009 09:25:14 +0000</pubDate>
		<guid isPermaLink="false">http://walt.lishost.org/2009/06/culture-clashes-ii-pdf-xml-and-whats-in-it-for-me/#comment-39621</guid>
		<description><![CDATA[A few somewhat random thoughts:
It is all text, and anyone with a reasonable set of tools can mine your PDF&#039;s or convert them to HTML if the layout is fairly linear (and even if not, it is just easier if it is linear).
It is not true that PDF renders identical and perfect results everywhere and all the time.  That is somewhat of a fallacy. It can depend on the installed fonts, for instance.
One of the beauties of the typical Linux distribution is that saving as PDF is routine in most software, and translating among various formats is run of the mill and the tools and support readily available.
It is easy to use HTML as a quick and dirty formatting technique.  It is easy to go from HTML or XML to PDF.  Proper HTML can stand in for XML.  It is easy to obtain or write your own filter to convert a personalized markdown langauge so that text can be converted to XML/HTML quickly.
In other words, you don&#039;t have to chose.  Just use mainly text ... content oriented, not format or layout oriented efforts.  Then you can play around with format, typography, etc. using many tools and produce many different kinds of products, and have fun and fill up your hard drive and the internet with only a few keystrokes!  The average &quot;text editor&quot; now does fancy dancy spell checking (this has been true for years) and markdown works, so why you ever need a &quot;word processor&quot; anyway is kind of beyond me, except at the final stages, to make that XML/PDF/HTML/DOC product. If then.
HTML/XML does not produce the exact same thing on every viewing platform, but it does produce consistent results that will always *act* if not always *look* the same, unless the viewer is screwing around alot, and then that is the viewer&#039;s problem.
]]></description>
		<content:encoded><![CDATA[<p>A few somewhat random thoughts:<br />
It is all text, and anyone with a reasonable set of tools can mine your PDF&#8217;s or convert them to HTML if the layout is fairly linear (and even if not, it is just easier if it is linear).<br />
It is not true that PDF renders identical and perfect results everywhere and all the time.  That is somewhat of a fallacy. It can depend on the installed fonts, for instance.<br />
One of the beauties of the typical Linux distribution is that saving as PDF is routine in most software, and translating among various formats is run of the mill and the tools and support readily available.<br />
It is easy to use HTML as a quick and dirty formatting technique.  It is easy to go from HTML or XML to PDF.  Proper HTML can stand in for XML.  It is easy to obtain or write your own filter to convert a personalized markdown langauge so that text can be converted to XML/HTML quickly.<br />
In other words, you don&#8217;t have to chose.  Just use mainly text &#8230; content oriented, not format or layout oriented efforts.  Then you can play around with format, typography, etc. using many tools and produce many different kinds of products, and have fun and fill up your hard drive and the internet with only a few keystrokes!  The average &#8220;text editor&#8221; now does fancy dancy spell checking (this has been true for years) and markdown works, so why you ever need a &#8220;word processor&#8221; anyway is kind of beyond me, except at the final stages, to make that XML/PDF/HTML/DOC product. If then.<br />
HTML/XML does not produce the exact same thing on every viewing platform, but it does produce consistent results that will always *act* if not always *look* the same, unless the viewer is screwing around alot, and then that is the viewer&#8217;s problem.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
