<?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: Getting closer to completion</title>
	<atom:link href="http://existentialtype.net/2007/11/01/getting-closer-to-completion/feed/" rel="self" type="application/rss+xml" />
	<link>http://existentialtype.net/2007/11/01/getting-closer-to-completion/</link>
	<description>For People Who Like Type and Types</description>
	<pubDate>Tue, 06 Jan 2009 09:57:42 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: washburn</title>
		<link>http://existentialtype.net/2007/11/01/getting-closer-to-completion/comment-page-1/#comment-17760</link>
		<dc:creator>washburn</dc:creator>
		<pubDate>Tue, 06 Nov 2007 02:07:44 +0000</pubDate>
		<guid isPermaLink="false">http://existentialtype.net/2007/11/01/getting-closer-to-completion/#comment-17760</guid>
		<description>&lt;em&gt;I’d say both, but I’m not seeing the distinction.&lt;/em&gt;

There is not much of one.  I was mostly just saying it two different ways in case one didn't make sense.

&lt;em&gt;It doesn’t look like something the imaginary calligraphic mathematician who wrote, say, the Euler ‘e’ would write. But I guess that’s no more precise than what I said originally. :-)&lt;/em&gt;

That is what I thought you were getting at, but I was not quite sure.  In general I have been wondering whether some of the other symbols had too little of a handwritten calligraphic look.  Perhaps with &lt;code&gt;\in&lt;/code&gt; it is more jarring because it is somewhere in between, while things like &lt;code&gt;\top&lt;/code&gt; and &lt;code&gt;\vdash&lt;/code&gt; a very clearly geometric (unless you are zoomed in and observe the angled tips). 

I will have to think about what strokes someone might make when writing &lt;code&gt;\in&lt;/code&gt; with a calligraphic pen.  Unfortunately, I tend to write even my letters differently than most people, so I am not sure how well that will work out.</description>
		<content:encoded><![CDATA[<p><em>I’d say both, but I’m not seeing the distinction.</em></p>
<p>There is not much of one.  I was mostly just saying it two different ways in case one didn&#8217;t make sense.</p>
<p><em>It doesn’t look like something the imaginary calligraphic mathematician who wrote, say, the Euler ‘e’ would write. But I guess that’s no more precise than what I said originally. <img src='http://existentialtype.net/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </em></p>
<p>That is what I thought you were getting at, but I was not quite sure.  In general I have been wondering whether some of the other symbols had too little of a handwritten calligraphic look.  Perhaps with <code>\in</code> it is more jarring because it is somewhere in between, while things like <code>\top</code> and <code>\vdash</code> a very clearly geometric (unless you are zoomed in and observe the angled tips). </p>
<p>I will have to think about what strokes someone might make when writing <code>\in</code> with a calligraphic pen.  Unfortunately, I tend to write even my letters differently than most people, so I am not sure how well that will work out.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joshua Dunfield</title>
		<link>http://existentialtype.net/2007/11/01/getting-closer-to-completion/comment-page-1/#comment-17716</link>
		<dc:creator>Joshua Dunfield</dc:creator>
		<pubDate>Sun, 04 Nov 2007 05:10:46 +0000</pubDate>
		<guid isPermaLink="false">http://existentialtype.net/2007/11/01/getting-closer-to-completion/#comment-17716</guid>
		<description>&lt;i&gt;Does that imply you do not like the others (except what you have said about \forall and \in) or just that you have no opinion? If it is the former, can you elaborate?&lt;/i&gt;

I don't have an opinion...the standard versions of \top, \bot, \forall, and \exists particularly annoy me, especially in slides—in fact I've used "poor man's bold" for them—so I'm a bit more familiar with those.

&lt;i&gt;I kind of like the tilt a little, but I would agree that it is probably too pronounced.&lt;/i&gt;

It's a letter (by birth, at least?) so I guess it &lt;i&gt;should&lt;/i&gt; tilt, it's just not what I'm used to seeing.

&lt;i&gt;By too perfect you mean that it [\in] does not seem handwritten, or that it is too geometrical?&lt;/i&gt;

I'd say both, but I'm not seeing the distinction.  It doesn't look like something the imaginary calligraphic mathematician who wrote, say, the Euler 'e' would write.  But I guess that's no more precise than what I said originally. :-)</description>
		<content:encoded><![CDATA[<p><i>Does that imply you do not like the others (except what you have said about \forall and \in) or just that you have no opinion? If it is the former, can you elaborate?</i></p>
<p>I don&#8217;t have an opinion&#8230;the standard versions of \top, \bot, \forall, and \exists particularly annoy me, especially in slides—in fact I&#8217;ve used &#8220;poor man&#8217;s bold&#8221; for them—so I&#8217;m a bit more familiar with those.</p>
<p><i>I kind of like the tilt a little, but I would agree that it is probably too pronounced.</i></p>
<p>It&#8217;s a letter (by birth, at least?) so I guess it <i>should</i> tilt, it&#8217;s just not what I&#8217;m used to seeing.</p>
<p><i>By too perfect you mean that it [\in] does not seem handwritten, or that it is too geometrical?</i></p>
<p>I&#8217;d say both, but I&#8217;m not seeing the distinction.  It doesn&#8217;t look like something the imaginary calligraphic mathematician who wrote, say, the Euler &#8216;e&#8217; would write.  But I guess that&#8217;s no more precise than what I said originally. <img src='http://existentialtype.net/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: washburn</title>
		<link>http://existentialtype.net/2007/11/01/getting-closer-to-completion/comment-page-1/#comment-17661</link>
		<dc:creator>washburn</dc:creator>
		<pubDate>Fri, 02 Nov 2007 14:34:46 +0000</pubDate>
		<guid isPermaLink="false">http://existentialtype.net/2007/11/01/getting-closer-to-completion/#comment-17661</guid>
		<description>&lt;em&gt;I find \forall a bit lopsided.&lt;/em&gt;

Discussed that above.

&lt;em&gt;\star and \longrightarrow are noticeably nicer in Gentzen.&lt;/em&gt;

Thanks.  Part of the reason for that is that &lt;code&gt;\longrightarrow&lt;/code&gt; is constructed out of a dash and &lt;code&gt;\rightarrow&lt;/code&gt; normally and it apparently does not quite line up right in my dissertation.  I made&lt;code&gt;\longrightarrow&lt;/code&gt; using a single glyph. 

&lt;em&gt; I think I might prefer a larger \vdash, but other symbols seem okay.&lt;/em&gt;

Yeah, I it does seem like it stands out quite enough.  However, I think the horizontal portion in the Euler version seems too long.  I'll have to see what I can come up with.</description>
		<content:encoded><![CDATA[<p><em>I find \forall a bit lopsided.</em></p>
<p>Discussed that above.</p>
<p><em>\star and \longrightarrow are noticeably nicer in Gentzen.</em></p>
<p>Thanks.  Part of the reason for that is that <code>\longrightarrow</code> is constructed out of a dash and <code>\rightarrow</code> normally and it apparently does not quite line up right in my dissertation.  I made<code>\longrightarrow</code> using a single glyph. </p>
<p><em> I think I might prefer a larger \vdash, but other symbols seem okay.</em></p>
<p>Yeah, I it does seem like it stands out quite enough.  However, I think the horizontal portion in the Euler version seems too long.  I&#8217;ll have to see what I can come up with.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: washburn</title>
		<link>http://existentialtype.net/2007/11/01/getting-closer-to-completion/comment-page-1/#comment-17660</link>
		<dc:creator>washburn</dc:creator>
		<pubDate>Fri, 02 Nov 2007 14:31:20 +0000</pubDate>
		<guid isPermaLink="false">http://existentialtype.net/2007/11/01/getting-closer-to-completion/#comment-17660</guid>
		<description>&lt;em&gt;I like \top, \bot, \exists.&lt;/em&gt;

Does that imply you do not like the others (except what you have said about &lt;code&gt;\forall&lt;/code&gt; and &lt;code&gt;\in&lt;/code&gt;) or just that you have no opinion?  If it is the former, can you elaborate?

&lt;em&gt;\forall looks like it’s tilted slightly to the right.&lt;/em&gt;

Indeed it is, as the regular Euler A is tilted, and therefor remained when I modified it.  I kind of like the tilt a little, but I would agree that it is probably too pronounced.

&lt;em&gt;The \in looks too “perfect” compared to the Euler Greek letters, etc., despite probably being an improvement on the standard one.&lt;/em&gt;

By too perfect you mean that it does not seem handwritten, or that it is too geometrical?</description>
		<content:encoded><![CDATA[<p><em>I like \top, \bot, \exists.</em></p>
<p>Does that imply you do not like the others (except what you have said about <code>\forall</code> and <code>\in</code>) or just that you have no opinion?  If it is the former, can you elaborate?</p>
<p><em>\forall looks like it’s tilted slightly to the right.</em></p>
<p>Indeed it is, as the regular Euler A is tilted, and therefor remained when I modified it.  I kind of like the tilt a little, but I would agree that it is probably too pronounced.</p>
<p><em>The \in looks too “perfect” compared to the Euler Greek letters, etc., despite probably being an improvement on the standard one.</em></p>
<p>By too perfect you mean that it does not seem handwritten, or that it is too geometrical?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brian</title>
		<link>http://existentialtype.net/2007/11/01/getting-closer-to-completion/comment-page-1/#comment-17658</link>
		<dc:creator>Brian</dc:creator>
		<pubDate>Fri, 02 Nov 2007 13:15:34 +0000</pubDate>
		<guid isPermaLink="false">http://existentialtype.net/2007/11/01/getting-closer-to-completion/#comment-17658</guid>
		<description>[Looking at printed samples.]  I find \forall a bit lopsided.  \star and \longrightarrow are noticeably nicer in Gentzen.  I think I might prefer a larger \vdash, but other symbols seem okay.</description>
		<content:encoded><![CDATA[<p>[Looking at printed samples.]  I find \forall a bit lopsided.  \star and \longrightarrow are noticeably nicer in Gentzen.  I think I might prefer a larger \vdash, but other symbols seem okay.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joshua Dunfield</title>
		<link>http://existentialtype.net/2007/11/01/getting-closer-to-completion/comment-page-1/#comment-17656</link>
		<dc:creator>Joshua Dunfield</dc:creator>
		<pubDate>Fri, 02 Nov 2007 03:17:20 +0000</pubDate>
		<guid isPermaLink="false">http://existentialtype.net/2007/11/01/getting-closer-to-completion/#comment-17656</guid>
		<description>I like \top, \bot, \exists.  \forall looks like it's tilted slightly to the right.  (I don't find \forall and \exists jarring, but that could be due to having seen too many old logic books recently.) The \in looks too "perfect" compared to the Euler Greek letters, etc., despite probably being an improvement on the standard one.</description>
		<content:encoded><![CDATA[<p>I like \top, \bot, \exists.  \forall looks like it&#8217;s tilted slightly to the right.  (I don&#8217;t find \forall and \exists jarring, but that could be due to having seen too many old logic books recently.) The \in looks too &#8220;perfect&#8221; compared to the Euler Greek letters, etc., despite probably being an improvement on the standard one.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
