<?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: Regexps Rule</title>
	<atom:link href="http://crookedtimber.org/2005/05/29/regexps-rule/feed/" rel="self" type="application/rss+xml" />
	<link>http://crookedtimber.org/2005/05/29/regexps-rule/</link>
	<description>Out of the crooked timber of humanity, no straight thing was ever made</description>
	<lastBuildDate>Sun, 08 Nov 2009 11:29:05 -0800</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.5</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: ben wolfson</title>
		<link>http://crookedtimber.org/2005/05/29/regexps-rule/comment-page-1/#comment-73648</link>
		<dc:creator>ben wolfson</dc:creator>
		<pubDate>Thu, 02 Jun 2005 16:28:52 +0000</pubDate>
		<guid isPermaLink="false">http://crookedtimber.org/2005/05/29/regexps-rule/#comment-73648</guid>
		<description>teekay, you could go all out and host your .tex files on a CVS or Subversion server.  Segregation of duties!  Let the version tracker track versions, the editor edit text, and the typesetting program handle layout.  No need for one program to do all the jobs.</description>
		<content:encoded><![CDATA[	<p>teekay, you could go all out and host your .tex files on a <span class="caps">CVS</span> or Subversion server.  Segregation of duties!  Let the version tracker track versions, the editor edit text, and the typesetting program handle layout.  No need for one program to do all the jobs.</p>
 ]]></content:encoded>
	</item>
	<item>
		<title>By: theCoach</title>
		<link>http://crookedtimber.org/2005/05/29/regexps-rule/comment-page-1/#comment-73624</link>
		<dc:creator>theCoach</dc:creator>
		<pubDate>Thu, 02 Jun 2005 13:56:13 +0000</pubDate>
		<guid isPermaLink="false">http://crookedtimber.org/2005/05/29/regexps-rule/#comment-73624</guid>
		<description>Office 12 formats are pure XML, open and with a royalty free license, and updates will be released so that earlier versions can read the new format.
Thought you might want to know that.
http://www.microsoft.com/presspass/features/2005/jun05/06-01XMLFileFormat.asp</description>
		<content:encoded><![CDATA[	<p>Office 12 formats are pure <span class="caps">XML</span>, open and with a royalty free license, and updates will be released so that earlier versions can read the new format.<br />
Thought you might want to know that.<br />
<a href="http://www.microsoft.com/presspass/features/2005/jun05/06-01XMLFileFormat.asp" rel="nofollow">http://www.microsoft.com/presspass/features/2005/jun05/06-01XMLFileFormat.asp</a></p>
 ]]></content:encoded>
	</item>
	<item>
		<title>By: teekay</title>
		<link>http://crookedtimber.org/2005/05/29/regexps-rule/comment-page-1/#comment-73596</link>
		<dc:creator>teekay</dc:creator>
		<pubDate>Thu, 02 Jun 2005 06:42:08 +0000</pubDate>
		<guid isPermaLink="false">http://crookedtimber.org/2005/05/29/regexps-rule/#comment-73596</guid>
		<description>Tim points to a critical shortcoming of LaTeX and its various front ends -- collaborative drafting and editing. The easiest workaround is to produce in LaTeX and share the PDF output, which can then be marked up using Preview (on Mac) or Acrobat Professional. This is unsatisfactory for a whole bunch of reasons: (i) the markup then needs to be manually transferred back to the source file, which is fine for a small article with only one back and forth between author and editor (or between two authors) but not for a book with frequent iterations of the process; (ii) the markup tools even in Acrobat are rather primitive -- there&#039;s no equivalent of Word&#039;s track changes; (iii) I resent the fact that in order to add functionality to an open source application I need to buy an expensive and unwieldy proprietary solution like Acrobat. 

An additional problem is that Word is almost universal in the sense that the vast majority of people who use computers have access to it and have a basic idea of how to use it, while LaTeX might be rather offputting to learn. In other words, I can&#039;t ask my co-author to spend days learning LaTeX just because I happen to prefer it to Word...

Any thoughts by people who use LaTeX in such collaborative contexts?</description>
		<content:encoded><![CDATA[	<p>Tim points to a critical shortcoming of LaTeX and its various front ends&#8212;collaborative drafting and editing. The easiest workaround is to produce in LaTeX and share the <span class="caps">PDF</span> output, which can then be marked up using Preview (on Mac) or Acrobat Professional. This is unsatisfactory for a whole bunch of reasons: (i) the markup then needs to be manually transferred back to the source file, which is fine for a small article with only one back and forth between author and editor (or between two authors) but not for a book with frequent iterations of the process; (ii) the markup tools even in Acrobat are rather primitive&#8212;there&#8217;s no equivalent of Word&#8217;s track changes; (iii) I resent the fact that in order to add functionality to an open source application I need to buy an expensive and unwieldy proprietary solution like Acrobat.</p>

	<p>An additional problem is that Word is almost universal in the sense that the vast majority of people who use computers have access to it and have a basic idea of how to use it, while LaTeX might be rather offputting to learn. In other words, I can&#8217;t ask my co-author to spend days learning LaTeX just because I happen to prefer it to Word&#8230;</p>

	<p>Any thoughts by people who use LaTeX in such collaborative contexts?</p>
 ]]></content:encoded>
	</item>
	<item>
		<title>By: George Colpitts</title>
		<link>http://crookedtimber.org/2005/05/29/regexps-rule/comment-page-1/#comment-73570</link>
		<dc:creator>George Colpitts</dc:creator>
		<pubDate>Wed, 01 Jun 2005 21:46:14 +0000</pubDate>
		<guid isPermaLink="false">http://crookedtimber.org/2005/05/29/regexps-rule/#comment-73570</guid>
		<description>Very interesting particularly along with the previous post on indispensable applications. I hate Word so much that I have learned some Latex as Word has a mind of its own and I can never get it to do what I want. Nevertheless it would be reaaly nice if I could learn to use Word in a better way. Can somebody please post a good reference on how to use Word properly so it doesn&#039;t drive me crazy ?</description>
		<content:encoded><![CDATA[	<p>Very interesting particularly along with the previous post on indispensable applications. I hate Word so much that I have learned some Latex as Word has a mind of its own and I can never get it to do what I want. Nevertheless it would be reaaly nice if I could learn to use Word in a better way. Can somebody please post a good reference on how to use Word properly so it doesn&#8217;t drive me crazy ?</p>
 ]]></content:encoded>
	</item>
	<item>
		<title>By: Jonathan Goldberg</title>
		<link>http://crookedtimber.org/2005/05/29/regexps-rule/comment-page-1/#comment-73416</link>
		<dc:creator>Jonathan Goldberg</dc:creator>
		<pubDate>Tue, 31 May 2005 21:44:16 +0000</pubDate>
		<guid isPermaLink="false">http://crookedtimber.org/2005/05/29/regexps-rule/#comment-73416</guid>
		<description>I get a bit of a kick out of Friedl (the author of the excellent Mastering Regular Expressions, recommended above) saying (on page 30) &quot;When it comes right down to it, regular expressions are not difficult.&quot;  And then writing a 430 page  book to prove it.

Although, bizarrely enough, I know what he means...</description>
		<content:encoded><![CDATA[	<p>I get a bit of a kick out of Friedl (the author of the excellent Mastering Regular Expressions, recommended above) saying (on page 30) &#8220;When it comes right down to it, regular expressions are not difficult.&#8221;  And then writing a 430 page  book to prove it.</p>

	<p>Although, bizarrely enough, I know what he means&#8230;</p>
 ]]></content:encoded>
	</item>
	<item>
		<title>By: Tim McGovern</title>
		<link>http://crookedtimber.org/2005/05/29/regexps-rule/comment-page-1/#comment-73415</link>
		<dc:creator>Tim McGovern</dc:creator>
		<pubDate>Tue, 31 May 2005 21:18:44 +0000</pubDate>
		<guid isPermaLink="false">http://crookedtimber.org/2005/05/29/regexps-rule/#comment-73415</guid>
		<description>I&#039;m the dumb and/or lazy guy (no offense taken, really!) at the U of C Press who&#039;s putting Kieran through all the separation anxiety of leaving his beloved LaTeX. I&#039;ve got to say thanks, first on behalf of the Press for the props, and second, for your insightt on our electronic manuscript requirements. 

A bit of an apologia, as well, for those requirements:

There certainly is a big dichotomy between the requirements and capabilities of the Books and Journals divisions. The determining factor in all of this is the editing process, not production (typesetting and printing). 

There was a great deal of talk, as Lakshmi says,  about bringing books&#039; editing and production processes more inline with journals&#039; when I first started working at the Press (~5 years ago), but the practicalities of doing so quickly overcame the cool factor of &quot;Online editing! SGML!&quot;

I can only really speak to the Books end of this process, but what I can tell you is that our manuscript editors are words people, not computer people, and it&#039;s a fairly rare individual who is turned on by both (though becoming less so!). 

Kieran&#039;s editor will edit on screen, generally in word because it&#039;s what she&#039;s familiar with, but also because it&#039;s what most (I&#039;d say about 80% in the fields I work in -- history, sociology, rhetoric, and sex) of our authors use. 

Inertia and the Lowest Common Denominator factor are not the only reasons we use Word. We use Word&#039;s &quot;track changes&quot; to produce a redlined hard copy manuscript, which the author gets to review, and accept/tweak edits (small edits, e.g., spelling, are made transparently). Then edits are finally accepted/rejected here by the manuscript editor. 

You&#039;ll note that this process takes a lot out of the hands of the author: final production of the electronic manuscript for the typesetter is the responsibility of the manuscript editor (to say nothing of production of typeset pages!). Some authors (ekr?) would love to have complete control over the final product, but we in the publishing business like to think we add value beyond our imprint, binding, and distribution! 

Now I hie me back to work, getting ready for Kieran&#039;s ms arrival. </description>
		<content:encoded><![CDATA[	<p>I&#8217;m the dumb and/or lazy guy (no offense taken, really!) at the U of C Press who&#8217;s putting Kieran through all the separation anxiety of leaving his beloved LaTeX. I&#8217;ve got to say thanks, first on behalf of the Press for the props, and second, for your insightt on our electronic manuscript requirements.</p>

	<p>A bit of an apologia, as well, for those requirements:</p>

	<p>There certainly is a big dichotomy between the requirements and capabilities of the Books and Journals divisions. The determining factor in all of this is the editing process, not production (typesetting and printing).</p>

	<p>There was a great deal of talk, as Lakshmi says,  about bringing books&#8217; editing and production processes more inline with journals&#8217; when I first started working at the Press (~5 years ago), but the practicalities of doing so quickly overcame the cool factor of &#8220;Online editing! <span class="caps">SGML</span>!&#8221;</p>

	<p>I can only really speak to the Books end of this process, but what I can tell you is that our manuscript editors are words people, not computer people, and it&#8217;s a fairly rare individual who is turned on by both (though becoming less so!).</p>

	<p>Kieran&#8217;s editor will edit on screen, generally in word because it&#8217;s what she&#8217;s familiar with, but also because it&#8217;s what most (I&#8217;d say about 80% in the fields I work in&#8212;history, sociology, rhetoric, and sex) of our authors use.</p>

	<p>Inertia and the Lowest Common Denominator factor are not the only reasons we use Word. We use Word&#8217;s &#8220;track changes&#8221; to produce a redlined hard copy manuscript, which the author gets to review, and accept/tweak edits (small edits, e.g., spelling, are made transparently). Then edits are finally accepted/rejected here by the manuscript editor.</p>

	<p>You&#8217;ll note that this process takes a lot out of the hands of the author: final production of the electronic manuscript for the typesetter is the responsibility of the manuscript editor (to say nothing of production of typeset pages!). Some authors (ekr?) would love to have complete control over the final product, but we in the publishing business like to think we add value beyond our imprint, binding, and distribution!</p>

	<p>Now I hie me back to work, getting ready for Kieran&#8217;s ms arrival.</p>
 ]]></content:encoded>
	</item>
	<item>
		<title>By: ben wolfson</title>
		<link>http://crookedtimber.org/2005/05/29/regexps-rule/comment-page-1/#comment-73340</link>
		<dc:creator>ben wolfson</dc:creator>
		<pubDate>Tue, 31 May 2005 15:42:33 +0000</pubDate>
		<guid isPermaLink="false">http://crookedtimber.org/2005/05/29/regexps-rule/#comment-73340</guid>
		<description>&lt;em&gt;This in no way is to say that regexps are not the best thing ever.&lt;/em&gt;

Then there&#039;s Jamie Zawinski&#039;s observation: &lt;em&gt;Some people, when confronted with a problem, think “I know, I’ll use regular expressions.” Now they have two problems.&lt;/em&gt;.</description>
		<content:encoded><![CDATA[	<p><em>This in no way is to say that regexps are not the best thing ever.</em></p>

	<p>Then there&#8217;s Jamie Zawinski&#8217;s observation: <em>Some people, when confronted with a problem, think &#8220;I know, I&#8217;ll use regular expressions.&#8221; Now they have two problems.</em>.</p>
 ]]></content:encoded>
	</item>
	<item>
		<title>By: EKR</title>
		<link>http://crookedtimber.org/2005/05/29/regexps-rule/comment-page-1/#comment-73135</link>
		<dc:creator>EKR</dc:creator>
		<pubDate>Mon, 30 May 2005 02:14:45 +0000</pubDate>
		<guid isPermaLink="false">http://crookedtimber.org/2005/05/29/regexps-rule/#comment-73135</guid>
		<description>Vis-a-vis professional typesetting....

Interesting. The commercial houses (Pearson, Wiley, etc.) all seem quite happy with camera-ready, even in the professional series. And clearly some of those come out looking very nice (cf. The Art of Computer Programming, or the Stevens books). At least to my eye, those books look as good or better than those produced by professional typesetters. For example, I far prefer the typesetting in TCP/Illustrated (done with groff) to that in the Chicago Manual of Style. Of course, this is clearly a taste thing, and I&#039;m fanatical about having control of the look and feel, so I was willing to put in the time to get exactly the layout I wanted.</description>
		<content:encoded><![CDATA[	<p>Vis-a-vis professional typesetting&#8230;.</p>

	<p>Interesting. The commercial houses (Pearson, Wiley, etc.) all seem quite happy with camera-ready, even in the professional series. And clearly some of those come out looking very nice (cf. The Art of Computer Programming, or the Stevens books). At least to my eye, those books look as good or better than those produced by professional typesetters. For example, I far prefer the typesetting in <span class="caps">TCP</span>/Illustrated (done with groff) to that in the Chicago Manual of Style. Of course, this is clearly a taste thing, and I&#8217;m fanatical about having control of the look and feel, so I was willing to put in the time to get exactly the layout I wanted.</p>
 ]]></content:encoded>
	</item>
	<item>
		<title>By: Lakshmi Sadasiv</title>
		<link>http://crookedtimber.org/2005/05/29/regexps-rule/comment-page-1/#comment-73133</link>
		<dc:creator>Lakshmi Sadasiv</dc:creator>
		<pubDate>Mon, 30 May 2005 01:37:55 +0000</pubDate>
		<guid isPermaLink="false">http://crookedtimber.org/2005/05/29/regexps-rule/#comment-73133</guid>
		<description>&quot;the U of C journals all want, or at least accept, LaTeX submissions. At least job requirements for working in production on them include a familiarity with both it and SGML; you have to clean up submitted .tex files or some such.&quot;

This is true; I worked at the University of Chicago Press (a few years back) and all of the journals are produced via sgml files. AASTeX was the format of choice though we could take Word and WordPerfect files as well. The last project I did there was a book that was going to be produced via the sgml-based workflow and I seem to recall that the press&#039;s business plan was to integrate the books division into the sgml workflow. I wonder what happened.

It could just be that you got a dumb and/or lazy editor who couldn&#039;t walk over to the other side of the building and ask if there was a way to accept LaTeX files. (I am several years out of date as to how exactly the file translation process runs there now but from what I remember you could run the chapters as AASTeX files and include the auxiliary files to make the cross references).

This in no way is to say that regexps are not the best thing ever. Of course, Word still sucks with regard to mathematics (MathType and Equation Editor are both stupid and cumbersome and don&#039;t deal well with regexps) so it is worth it to argue with your publisher about accepting LaTeX files. (If they really don&#039;t like it, let them send it to the third world to be rekeyed like they do all the time anyway.)</description>
		<content:encoded><![CDATA[	<p>&#8220;the U of C journals all want, or at least accept, LaTeX submissions. At least job requirements for working in production on them include a familiarity with both it and <span class="caps">SGML</span>; you have to clean up submitted .tex files or some such.&#8221;</p>

	<p>This is true; I worked at the University of Chicago Press (a few years back) and all of the journals are produced via sgml files. <span class="caps">AAS</span>TeX was the format of choice though we could take Word and WordPerfect files as well. The last project I did there was a book that was going to be produced via the sgml-based workflow and I seem to recall that the press&#8217;s business plan was to integrate the books division into the sgml workflow. I wonder what happened.</p>

	<p>It could just be that you got a dumb and/or lazy editor who couldn&#8217;t walk over to the other side of the building and ask if there was a way to accept LaTeX files. (I am several years out of date as to how exactly the file translation process runs there now but from what I remember you could run the chapters as <span class="caps">AAS</span>TeX files and include the auxiliary files to make the cross references).</p>

	<p>This in no way is to say that regexps are not the best thing ever. Of course, Word still sucks with regard to mathematics (MathType and Equation Editor are both stupid and cumbersome and don&#8217;t deal well with regexps) so it is worth it to argue with your publisher about accepting LaTeX files. (If they really don&#8217;t like it, let them send it to the third world to be rekeyed like they do all the time anyway.)</p>
 ]]></content:encoded>
	</item>
	<item>
		<title>By: Kieran Healy</title>
		<link>http://crookedtimber.org/2005/05/29/regexps-rule/comment-page-1/#comment-73129</link>
		<dc:creator>Kieran Healy</dc:creator>
		<pubDate>Mon, 30 May 2005 00:29:51 +0000</pubDate>
		<guid isPermaLink="false">http://crookedtimber.org/2005/05/29/regexps-rule/#comment-73129</guid>
		<description>&lt;i&gt; think the U of C journals all want, or at least accept, LaTeX submissions. &lt;/i&gt;

Yes, I&#039;ve done this with them. As  you say, they just want you submit a cleaned-up file. </description>
		<content:encoded><![CDATA[	<p><i> think the U of C journals all want, or at least accept, LaTeX submissions. </i></p>

	<p>Yes, I&#8217;ve done this with them. As  you say, they just want you submit a cleaned-up file.</p>
 ]]></content:encoded>
	</item>
	<item>
		<title>By: ben wolfson</title>
		<link>http://crookedtimber.org/2005/05/29/regexps-rule/comment-page-1/#comment-73123</link>
		<dc:creator>ben wolfson</dc:creator>
		<pubDate>Sun, 29 May 2005 23:29:29 +0000</pubDate>
		<guid isPermaLink="false">http://crookedtimber.org/2005/05/29/regexps-rule/#comment-73123</guid>
		<description>I think the U of C journals all want, or at least accept, LaTeX submissions.  At least job requirements for working in production on them include a familiarity with both it and SGML; you have to clean up submitted .tex files or some such.

Kotsko: you would say that.</description>
		<content:encoded><![CDATA[	<p>I think the U of C journals all want, or at least accept, LaTeX submissions.  At least job requirements for working in production on them include a familiarity with both it and <span class="caps">SGML</span>; you have to clean up submitted .tex files or some such.</p>

	<p>Kotsko: you would say that.</p>
 ]]></content:encoded>
	</item>
	<item>
		<title>By: Nick Caldwell</title>
		<link>http://crookedtimber.org/2005/05/29/regexps-rule/comment-page-1/#comment-73122</link>
		<dc:creator>Nick Caldwell</dc:creator>
		<pubDate>Sun, 29 May 2005 23:16:36 +0000</pubDate>
		<guid isPermaLink="false">http://crookedtimber.org/2005/05/29/regexps-rule/#comment-73122</guid>
		<description>On a slight tangent, one of the big problems I had with using LaTeX was bibliographic.  As best as I can tell, the MLA style isn&#039;t well supported in LaTeX-land, and, in any case, god help you if you want to be able to record other media like film or television in your bibliography.  The -- what was it? -- &quot;other&quot; category doesn&#039;t cut it.  I messed around with a couple of different extension packages, including one that promised to generate a custom bib file, but no real luck.  I ended up generating the damned thing manually.  </description>
		<content:encoded><![CDATA[	<p>On a slight tangent, one of the big problems I had with using LaTeX was bibliographic.  As best as I can tell, the <span class="caps">MLA</span> style isn&#8217;t well supported in LaTeX-land, and, in any case, god help you if you want to be able to record other media like film or television in your bibliography.  The&#8212;what was it?&#8212;&#8220;other&#8221; category doesn&#8217;t cut it.  I messed around with a couple of different extension packages, including one that promised to generate a custom bib file, but no real luck.  I ended up generating the damned thing manually.</p>
 ]]></content:encoded>
	</item>
	<item>
		<title>By: nick</title>
		<link>http://crookedtimber.org/2005/05/29/regexps-rule/comment-page-1/#comment-73116</link>
		<dc:creator>nick</dc:creator>
		<pubDate>Sun, 29 May 2005 21:35:12 +0000</pubDate>
		<guid isPermaLink="false">http://crookedtimber.org/2005/05/29/regexps-rule/#comment-73116</guid>
		<description>&lt;i&gt; If you want to work in something like TeX or Troff, it’s best to simply produce camera-ready submissions.&lt;/i&gt;

Big University Presses (or at least the humanities/soc-sci depts thereof) really don&#039;t want camera-ready copy. They have their One True Format, and your MS is going to be marked up into it by professional typesetters whether you like it or not. (And by the time you see the galleys, you&#039;ll probably like it.)</description>
		<content:encoded><![CDATA[	<p><i> If you want to work in something like TeX or Troff, it&#8217;s best to simply produce camera-ready submissions.</i></p>

	<p>Big University Presses (or at least the humanities/soc-sci depts thereof) really don&#8217;t want camera-ready copy. They have their One True Format, and your MS is going to be marked up into it by professional typesetters whether you like it or not. (And by the time you see the galleys, you&#8217;ll probably like it.)</p>
 ]]></content:encoded>
	</item>
	<item>
		<title>By: lago</title>
		<link>http://crookedtimber.org/2005/05/29/regexps-rule/comment-page-1/#comment-73109</link>
		<dc:creator>lago</dc:creator>
		<pubDate>Sun, 29 May 2005 20:26:26 +0000</pubDate>
		<guid isPermaLink="false">http://crookedtimber.org/2005/05/29/regexps-rule/#comment-73109</guid>
		<description>For less ambitious projects, I&#039;ve used &lt;a href=&quot;http://latex2rtf.sourceforge.net/&quot; rel=&quot;nofollow&quot;&gt;latex2rtf&lt;/a&gt; combined with Word&#039;s regular expression engine.  Might be a bit more accessible to the less ambitious hacker.</description>
		<content:encoded><![CDATA[	<p>For less ambitious projects, I&#8217;ve used <a href="http://latex2rtf.sourceforge.net/" rel="nofollow">latex2rtf</a> combined with Word&#8217;s regular expression engine.  Might be a bit more accessible to the less ambitious hacker.</p>
 ]]></content:encoded>
	</item>
	<item>
		<title>By: Kieran Healy</title>
		<link>http://crookedtimber.org/2005/05/29/regexps-rule/comment-page-1/#comment-73104</link>
		<dc:creator>Kieran Healy</dc:creator>
		<pubDate>Sun, 29 May 2005 19:24:37 +0000</pubDate>
		<guid isPermaLink="false">http://crookedtimber.org/2005/05/29/regexps-rule/#comment-73104</guid>
		<description>I should say that the people at Chicago have been absolutely great throughout the process, and I&#039;ve known for ages that the Day of Reckoning would come when I had to convert the manuscript. I also know that, in the end, Chicago&#039;s designers and typesetters will do a much better job than me when it comes to producing a good-looking book. They really know how to do it, whereas all my efforts to get TeX to do nice things are really just amateurish messing about. </description>
		<content:encoded><![CDATA[	<p>I should say that the people at Chicago have been absolutely great throughout the process, and I&#8217;ve known for ages that the Day of Reckoning would come when I had to convert the manuscript. I also know that, in the end, Chicago&#8217;s designers and typesetters will do a much better job than me when it comes to producing a good-looking book. They really know how to do it, whereas all my efforts to get TeX to do nice things are really just amateurish messing about.</p>
 ]]></content:encoded>
	</item>
</channel>
</rss>
