<?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: In which I learn things about TeX</title>
	<atom:link href="http://www.logophile.org/blog/2009/04/27/in-which-i-learn-things-about-tex/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.logophile.org/blog/2009/04/27/in-which-i-learn-things-about-tex/</link>
	<description>blog of a logophile (not "logos", but "λόγος")</description>
	<lastBuildDate>Mon, 06 Feb 2012 10:21:32 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: tikitu</title>
		<link>http://www.logophile.org/blog/2009/04/27/in-which-i-learn-things-about-tex/comment-page-1/#comment-6594</link>
		<dc:creator>tikitu</dc:creator>
		<pubDate>Thu, 30 Apr 2009 22:27:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.logophile.org/blog/?p=652#comment-6594</guid>
		<description>&lt;p&gt;You &lt;em&gt;said&lt;/em&gt; &quot;non-trivial&quot;, so I&#039;ll cut you some slack.&lt;/p&gt;

&lt;p&gt;LaTeX 3: seems to me to be focused on people who write packages. Which is all well and good, but ... not very helpful for those of us who want to &lt;em&gt;use&lt;/em&gt; the packages, unless they get written.&lt;/p&gt;

&lt;p&gt;BibTeX 1.0: will never arrive. And is to some extent superceded by biblatex anyway, although that may stay at v.0.8 forever...&lt;/p&gt;

&lt;p&gt;Nonpareil: LuaTeX looks fun. To be honest I&#039;m losing faith in open-source enthusiast-driven development, but that might be just pre-dissertatory depression setting in.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>You <em>said</em> &#8220;non-trivial&#8221;, so I&#8217;ll cut you some slack.</p>

<p>LaTeX 3: seems to me to be focused on people who write packages. Which is all well and good, but &#8230; not very helpful for those of us who want to <em>use</em> the packages, unless they get written.</p>

<p>BibTeX 1.0: will never arrive. And is to some extent superceded by biblatex anyway, although that may stay at v.0.8 forever&#8230;</p>

<p>Nonpareil: LuaTeX looks fun. To be honest I&#8217;m losing faith in open-source enthusiast-driven development, but that might be just pre-dissertatory depression setting in.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: S. glaber</title>
		<link>http://www.logophile.org/blog/2009/04/27/in-which-i-learn-things-about-tex/comment-page-1/#comment-6593</link>
		<dc:creator>S. glaber</dc:creator>
		<pubDate>Thu, 30 Apr 2009 21:50:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.logophile.org/blog/?p=652#comment-6593</guid>
		<description>&lt;blockquote&gt;you have to understand it at all levels simultaneously to use it&lt;/blockquote&gt;

&lt;p&gt;Well, I produced my first non-trivial document with it last week. Either I managed to understand it simultaneously at all levels in about two days, or such understanding is not really required. The simplest ConTeXt document is&lt;/p&gt;

&lt;p&gt;&lt;pre&gt;
\starttext
ConTeXt fanboy? Moi?
\stoptext
&lt;/pre&gt;&lt;/p&gt;

&lt;p&gt;which requires very little understanding.&lt;/p&gt;

&lt;p&gt;So I&#039;ll assume that&#039;s not really what you meant, and join you in your wise postponement of this argument to another day: specifically, a day subsequent to both our handing-in dates. (By which time LaTeX 3, BibTeX 1.0, and Nonpareil will probably be out, ho ho.)&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<blockquote>you have to understand it at all levels simultaneously to use it</blockquote>

<p>Well, I produced my first non-trivial document with it last week. Either I managed to understand it simultaneously at all levels in about two days, or such understanding is not really required. The simplest ConTeXt document is</p>

<p><pre>
\starttext
ConTeXt fanboy? Moi?
\stoptext
</pre></p>

<p>which requires very little understanding.</p>

<p>So I&#8217;ll assume that&#8217;s not really what you meant, and join you in your wise postponement of this argument to another day: specifically, a day subsequent to both our handing-in dates. (By which time LaTeX 3, BibTeX 1.0, and Nonpareil will probably be out, ho ho.)</p>]]></content:encoded>
	</item>
	<item>
		<title>By: tikitu</title>
		<link>http://www.logophile.org/blog/2009/04/27/in-which-i-learn-things-about-tex/comment-page-1/#comment-6592</link>
		<dc:creator>tikitu</dc:creator>
		<pubDate>Thu, 30 Apr 2009 10:08:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.logophile.org/blog/?p=652#comment-6592</guid>
		<description>&lt;p&gt;I don&#039;t &lt;em&gt;want&lt;/em&gt; to do things like that.&lt;/p&gt;

&lt;p&gt;The Rant Against ConTeXt is a rant for another day. Short version: as of last time I checked (about a year ago I think) you have to understand it at all levels simultaneously to use it. I&#039;d be reluctant to invest that heavily at the best of times, and frantically dissertating is not the best of times.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>I don&#8217;t <em>want</em> to do things like that.</p>

<p>The Rant Against ConTeXt is a rant for another day. Short version: as of last time I checked (about a year ago I think) you have to understand it at all levels simultaneously to use it. I&#8217;d be reluctant to invest that heavily at the best of times, and frantically dissertating is not the best of times.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: S. glaber</title>
		<link>http://www.logophile.org/blog/2009/04/27/in-which-i-learn-things-about-tex/comment-page-1/#comment-6585</link>
		<dc:creator>S. glaber</dc:creator>
		<pubDate>Wed, 29 Apr 2009 21:02:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.logophile.org/blog/?p=652#comment-6585</guid>
		<description>&lt;p&gt;Ah, come over to ConTeXt already. I only realized yesterday (though I assume you noticed when you had a look at it) that it has full user interfaces in Dutch and German, so you can do stuff like&lt;/p&gt;

&lt;p&gt;&lt;pre&gt;
\doornummeren[Vraag][plaats=inmarge]
\gebruikexternfiguur[Logo][FIG-0001][breedte=4em]
\definieerkop[Rubriek][paragraaf]
\stelkopin[Rubriek][letter=schuin]
&lt;/pre&gt;&lt;/p&gt;

&lt;p&gt;&lt;i&gt;Nice&lt;/i&gt;. Well, it would be if I spoke Dutch.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Ah, come over to ConTeXt already. I only realized yesterday (though I assume you noticed when you had a look at it) that it has full user interfaces in Dutch and German, so you can do stuff like</p>

<p><pre>
\doornummeren[Vraag][plaats=inmarge]
\gebruikexternfiguur[Logo][FIG-0001][breedte=4em]
\definieerkop[Rubriek][paragraaf]
\stelkopin[Rubriek][letter=schuin]
</pre></p>

<p><i>Nice</i>. Well, it would be if I spoke Dutch.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: tikitu</title>
		<link>http://www.logophile.org/blog/2009/04/27/in-which-i-learn-things-about-tex/comment-page-1/#comment-6581</link>
		<dc:creator>tikitu</dc:creator>
		<pubDate>Mon, 27 Apr 2009 13:47:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.logophile.org/blog/?p=652#comment-6581</guid>
		<description>&lt;p&gt;Probably true. But (a) if you&#039;re using TikZ, scanning for packages is not your bottleneck, and (b) if it &lt;em&gt;is&lt;/em&gt; there you have to keep it up to date.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Probably true. But (a) if you&#8217;re using TikZ, scanning for packages is not your bottleneck, and (b) if it <em>is</em> there you have to keep it up to date.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Robin</title>
		<link>http://www.logophile.org/blog/2009/04/27/in-which-i-learn-things-about-tex/comment-page-1/#comment-6580</link>
		<dc:creator>Robin</dc:creator>
		<pubDate>Mon, 27 Apr 2009 13:38:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.logophile.org/blog/?p=652#comment-6580</guid>
		<description>&lt;p&gt;Hmm. Last I looked, things were saying ‘It&#039;s not needed, but you can put it there to make scanning faster.’&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Hmm. Last I looked, things were saying ‘It&#8217;s not needed, but you can put it there to make scanning faster.’</p>]]></content:encoded>
	</item>
</channel>
</rss>

