<article>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#article10_01_17_0715219</id>
	<title>Programming With Proportional Fonts?</title>
	<author>timothy</author>
	<datestamp>1263731940000</datestamp>
	<htmltext>theodp writes <i>"<a href="http://www.theonion.com/content/amvo/archie\_to\_choose\_betty\_or\_veronica">Betty or Veronica</a>? <a href="http://www.codinghorror.com/blog/archives/000889.html">Mary Ann or Ginger</a>? <a href="http://en.wikipedia.org/wiki/Typeface#Typeface\_anatomy">Proportional or Monospaced</a>? There's renewed interest in an old blog post by Maas-Maarten Zeeman, in which M-MZ <a href="http://m-mz.posterous.com/programming-with-proportional">made the case for programming with proportional fonts</a>, citing studies that show proportional fonts can be read 14\% faster than fixed-width fonts. Try it for a couple of weeks, he suggests, and you might like it too. Nowadays, <a href="http://www.typechart.com/?cat=9">Lucida Grande</a> is M-MZ's font of choice on OS X, and he uses <a href="http://en.wikipedia.org/wiki/Lucida#Lucida\_Sans">Lucida Sans</a> on Windows. <a href="http://www.helveticafilm.com/">Helvetica</a>, anyone?"</i></htmltext>
<tokenext>theodp writes " Betty or Veronica ?
Mary Ann or Ginger ?
Proportional or Monospaced ?
There 's renewed interest in an old blog post by Maas-Maarten Zeeman , in which M-MZ made the case for programming with proportional fonts , citing studies that show proportional fonts can be read 14 \ % faster than fixed-width fonts .
Try it for a couple of weeks , he suggests , and you might like it too .
Nowadays , Lucida Grande is M-MZ 's font of choice on OS X , and he uses Lucida Sans on Windows .
Helvetica , anyone ?
"</tokentext>
<sentencetext>theodp writes "Betty or Veronica?
Mary Ann or Ginger?
Proportional or Monospaced?
There's renewed interest in an old blog post by Maas-Maarten Zeeman, in which M-MZ made the case for programming with proportional fonts, citing studies that show proportional fonts can be read 14\% faster than fixed-width fonts.
Try it for a couple of weeks, he suggests, and you might like it too.
Nowadays, Lucida Grande is M-MZ's font of choice on OS X, and he uses Lucida Sans on Windows.
Helvetica, anyone?
"</sentencetext>
</article>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797572</id>
	<title>Overrated</title>
	<author>Anonymous</author>
	<datestamp>1263736140000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>3</modscore>
	<htmltext><p>I've programmed in proportional fonts.  It's ok, but I prefer fixed width for alignment.</p></htmltext>
<tokenext>I 've programmed in proportional fonts .
It 's ok , but I prefer fixed width for alignment .</tokentext>
<sentencetext>I've programmed in proportional fonts.
It's ok, but I prefer fixed width for alignment.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797664</id>
	<title>Not the bottleneck</title>
	<author>bcmm</author>
	<datestamp>1263737220000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>4</modscore>
	<htmltext>Speed of reading is not a bottleneck in understanding code anyway, since I am sure it is pretty uncommon to be able to understand code while reading it as fast as you would read a novel.<br> <br>And there are numerous disadvantages: lack of alignment, smaller punctuation making syntax errors less visible (" '" vs "' " for example), etc., etc.</htmltext>
<tokenext>Speed of reading is not a bottleneck in understanding code anyway , since I am sure it is pretty uncommon to be able to understand code while reading it as fast as you would read a novel .
And there are numerous disadvantages : lack of alignment , smaller punctuation making syntax errors less visible ( " ' " vs " ' " for example ) , etc. , etc .</tokentext>
<sentencetext>Speed of reading is not a bottleneck in understanding code anyway, since I am sure it is pretty uncommon to be able to understand code while reading it as fast as you would read a novel.
And there are numerous disadvantages: lack of alignment, smaller punctuation making syntax errors less visible (" '" vs "' " for example), etc., etc.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797854</id>
	<title>We were taught in visual design class...</title>
	<author>Anonymous</author>
	<datestamp>1263739620000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>... that while proportional is more visually appealing, fixed width is easier to read when it comes to large amounts of text. I don't know if that's bunk or not, but I'd rather code in a fixed width.</p></htmltext>
<tokenext>... that while proportional is more visually appealing , fixed width is easier to read when it comes to large amounts of text .
I do n't know if that 's bunk or not , but I 'd rather code in a fixed width .</tokentext>
<sentencetext>... that while proportional is more visually appealing, fixed width is easier to read when it comes to large amounts of text.
I don't know if that's bunk or not, but I'd rather code in a fixed width.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797840</id>
	<title>Depends on the language</title>
	<author>stokessd</author>
	<datestamp>1263739500000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>At work I do a bit of matlab programming and the default font makes it very hard to see the difference between parenthesis and curly brackets.  That's a huge glaring flaw in the defaults that come with the IDE.</p><p>Back in the dark ages when I did a lot of FORTRAN77 programming, I would output a lot of data tables.  Trying to setup the print statements to make those tables with a proportional font would make me want to kill someone.</p><p>Today I pick my fonts for programming on how readable the punctuation and letters vs. numbers are, and what I've got on the computer I sit in front of.  Sadly I do a lot of code snippet writing on walk-up computers, or conference room computers, where I've got a standard windows and office font load.</p><p>I also do a lot of LabView programming, and the glyphs, icons, and lines are always proportional.<nobr> <wbr></nobr>:)</p><p>Sheldon</p></htmltext>
<tokenext>At work I do a bit of matlab programming and the default font makes it very hard to see the difference between parenthesis and curly brackets .
That 's a huge glaring flaw in the defaults that come with the IDE.Back in the dark ages when I did a lot of FORTRAN77 programming , I would output a lot of data tables .
Trying to setup the print statements to make those tables with a proportional font would make me want to kill someone.Today I pick my fonts for programming on how readable the punctuation and letters vs. numbers are , and what I 've got on the computer I sit in front of .
Sadly I do a lot of code snippet writing on walk-up computers , or conference room computers , where I 've got a standard windows and office font load.I also do a lot of LabView programming , and the glyphs , icons , and lines are always proportional .
: ) Sheldon</tokentext>
<sentencetext>At work I do a bit of matlab programming and the default font makes it very hard to see the difference between parenthesis and curly brackets.
That's a huge glaring flaw in the defaults that come with the IDE.Back in the dark ages when I did a lot of FORTRAN77 programming, I would output a lot of data tables.
Trying to setup the print statements to make those tables with a proportional font would make me want to kill someone.Today I pick my fonts for programming on how readable the punctuation and letters vs. numbers are, and what I've got on the computer I sit in front of.
Sadly I do a lot of code snippet writing on walk-up computers, or conference room computers, where I've got a standard windows and office font load.I also do a lot of LabView programming, and the glyphs, icons, and lines are always proportional.
:)Sheldon</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30800336</id>
	<title>Re:Overrated</title>
	<author>pjt33</author>
	<datestamp>1263760200000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>4</modscore>
	<htmltext><p>Nonsense. Differing widths of tab-stops only cause problems when people mix tabs and spaces.</p></htmltext>
<tokenext>Nonsense .
Differing widths of tab-stops only cause problems when people mix tabs and spaces .</tokentext>
<sentencetext>Nonsense.
Differing widths of tab-stops only cause problems when people mix tabs and spaces.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30799686</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30798296</id>
	<title>Re:Overrated</title>
	<author>Anonymous</author>
	<datestamp>1263743760000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>2</modscore>
	<htmltext><p>I did it once too, back in the early '90s. I was working on an adware program for Buick, so I used Eras as the font in my IDE (FYI, I was using a Mac, I think the PC guys were using Turbo Pascal) and it worked out real well.
</p><p>But I prefer monospaced fonts because you can't save your font and tab stop preferences in a plain-text ASCII file, and you don't want your text to look like a complete mess when someone else looks at it. You can only use hard tabs, and 8 spaces is just too wide for most programming.
</p><p>One thing's for sure... I wish I could type this message that I'm typing right now in a proportional font. Monospaced is horrible for non-code text. But the standard text input area for HTML is monospaced. Slashdot really needs an option for an "advanced editor".</p></htmltext>
<tokenext>I did it once too , back in the early '90s .
I was working on an adware program for Buick , so I used Eras as the font in my IDE ( FYI , I was using a Mac , I think the PC guys were using Turbo Pascal ) and it worked out real well .
But I prefer monospaced fonts because you ca n't save your font and tab stop preferences in a plain-text ASCII file , and you do n't want your text to look like a complete mess when someone else looks at it .
You can only use hard tabs , and 8 spaces is just too wide for most programming .
One thing 's for sure... I wish I could type this message that I 'm typing right now in a proportional font .
Monospaced is horrible for non-code text .
But the standard text input area for HTML is monospaced .
Slashdot really needs an option for an " advanced editor " .</tokentext>
<sentencetext>I did it once too, back in the early '90s.
I was working on an adware program for Buick, so I used Eras as the font in my IDE (FYI, I was using a Mac, I think the PC guys were using Turbo Pascal) and it worked out real well.
But I prefer monospaced fonts because you can't save your font and tab stop preferences in a plain-text ASCII file, and you don't want your text to look like a complete mess when someone else looks at it.
You can only use hard tabs, and 8 spaces is just too wide for most programming.
One thing's for sure... I wish I could type this message that I'm typing right now in a proportional font.
Monospaced is horrible for non-code text.
But the standard text input area for HTML is monospaced.
Slashdot really needs an option for an "advanced editor".</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797572</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797688</id>
	<title>Old news</title>
	<author>dazedNconfuzed</author>
	<datestamp>1263737580000</datestamp>
	<modclass>Redundant</modclass>
	<modscore>1</modscore>
	<htmltext><p>In the comments there, MMZ (author) notes "This was written 2 years ago."</p></htmltext>
<tokenext>In the comments there , MMZ ( author ) notes " This was written 2 years ago .
"</tokentext>
<sentencetext>In the comments there, MMZ (author) notes "This was written 2 years ago.
"</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30798926</id>
	<title>Re:Proportional fonts are better to read</title>
	<author>coryking</author>
	<datestamp>1263748800000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Code and prose are two different animals.  The meaning of a peice of writing is found mainly in the words and sentences it is made of.  While the words found within code are very important, a good portion of the meaning is found in the visual structure as well.</p><p>When you read prose, you have paragraphs, sentences, phrases.  You can take these chunks of writing and "pour" them into a two column newspaper, a leaflet or a book without losing the meaning of the piece.  You can also put it in a different font and while it might slightly alter the character of the piece, the words and sentence structure would remain the same.</p><p>The same is not true for code.  While it is true that the compiler doesn't care about the visual structure, your brain certainly does.  For example, you could take a C file and remove all the indents and have it compile just fine, but you'd have a very hard time reading it.  Imagine something like the following in a proportional font:<br><tt><br>var MyVar = SomeList.Where((i)=&gt;(i.Id &gt; 10))<nobr> <wbr></nobr>.Select((i)=&gt;{<br>
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Blah  = i.Item,<br>
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Thing = i.Name,<br>
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Id    = i.Id,<br>
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; });<br></tt><br>It would be much harder to read in a proportional font because some of the meaning was found in the spaces. I'd back my argument up more, but I've spilled tea on my keyboard and the cats are knocking things over. Worse, slashdot thinks my examples have too much whitespace in them so screw it. Bottom line is that for coding, the visual layout is as much of a part of the meaning as the text.  A proportional font distorts the layout and thus distorts the meaning.</p></htmltext>
<tokenext>Code and prose are two different animals .
The meaning of a peice of writing is found mainly in the words and sentences it is made of .
While the words found within code are very important , a good portion of the meaning is found in the visual structure as well.When you read prose , you have paragraphs , sentences , phrases .
You can take these chunks of writing and " pour " them into a two column newspaper , a leaflet or a book without losing the meaning of the piece .
You can also put it in a different font and while it might slightly alter the character of the piece , the words and sentence structure would remain the same.The same is not true for code .
While it is true that the compiler does n't care about the visual structure , your brain certainly does .
For example , you could take a C file and remove all the indents and have it compile just fine , but you 'd have a very hard time reading it .
Imagine something like the following in a proportional font : var MyVar = SomeList.Where ( ( i ) = &gt; ( i.Id &gt; 10 ) ) .Select ( ( i ) = &gt; {                               Blah = i.Item ,                               Thing = i.Name ,                               Id = i.Id ,                     } ) ; It would be much harder to read in a proportional font because some of the meaning was found in the spaces .
I 'd back my argument up more , but I 've spilled tea on my keyboard and the cats are knocking things over .
Worse , slashdot thinks my examples have too much whitespace in them so screw it .
Bottom line is that for coding , the visual layout is as much of a part of the meaning as the text .
A proportional font distorts the layout and thus distorts the meaning .</tokentext>
<sentencetext>Code and prose are two different animals.
The meaning of a peice of writing is found mainly in the words and sentences it is made of.
While the words found within code are very important, a good portion of the meaning is found in the visual structure as well.When you read prose, you have paragraphs, sentences, phrases.
You can take these chunks of writing and "pour" them into a two column newspaper, a leaflet or a book without losing the meaning of the piece.
You can also put it in a different font and while it might slightly alter the character of the piece, the words and sentence structure would remain the same.The same is not true for code.
While it is true that the compiler doesn't care about the visual structure, your brain certainly does.
For example, you could take a C file and remove all the indents and have it compile just fine, but you'd have a very hard time reading it.
Imagine something like the following in a proportional font:var MyVar = SomeList.Where((i)=&gt;(i.Id &gt; 10)) .Select((i)=&gt;{
                              Blah  = i.Item,
                              Thing = i.Name,
                              Id    = i.Id,
                    });It would be much harder to read in a proportional font because some of the meaning was found in the spaces.
I'd back my argument up more, but I've spilled tea on my keyboard and the cats are knocking things over.
Worse, slashdot thinks my examples have too much whitespace in them so screw it.
Bottom line is that for coding, the visual layout is as much of a part of the meaning as the text.
A proportional font distorts the layout and thus distorts the meaning.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797634</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30801556</id>
	<title>Re:Overrated</title>
	<author>fbjon</author>
	<datestamp>1263725400000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>It's not just another way of interpreting a tab, it's the right way to interpret a tab: semantically, not as a character in itself. The point with elastic tabs is to use editors that support it, not to change the world of all the old bearded ones.</htmltext>
<tokenext>It 's not just another way of interpreting a tab , it 's the right way to interpret a tab : semantically , not as a character in itself .
The point with elastic tabs is to use editors that support it , not to change the world of all the old bearded ones .</tokentext>
<sentencetext>It's not just another way of interpreting a tab, it's the right way to interpret a tab: semantically, not as a character in itself.
The point with elastic tabs is to use editors that support it, not to change the world of all the old bearded ones.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30799686</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30798056</id>
	<title>Re:fixed</title>
	<author>Anonymous</author>
	<datestamp>1263741420000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p><div class="quote"><p>As for TFA and using proportional fonts for programming, all I can say is that the author can't be doing a lot of unified diffs, or working with languages where the amount of indentation is significant (fortran, anyone?).</p></div><p>Python, anyone?</p></div>
	</htmltext>
<tokenext>As for TFA and using proportional fonts for programming , all I can say is that the author ca n't be doing a lot of unified diffs , or working with languages where the amount of indentation is significant ( fortran , anyone ?
) .Python , anyone ?</tokentext>
<sentencetext>As for TFA and using proportional fonts for programming, all I can say is that the author can't be doing a lot of unified diffs, or working with languages where the amount of indentation is significant (fortran, anyone?
).Python, anyone?
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797696</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30808038</id>
	<title>wuzzes</title>
	<author>uiuyhn8i8</author>
	<datestamp>1263830760000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext>You are all a bunch of limp wristed weaklings with your god damn new yuppie fonts. Use '-misc-fixed-medium-*-*-*-14-*-*-*-c-*-*-*' and view your code as emacs and X11 intended it with hard, cold gloriously pixelated simplicity.</htmltext>
<tokenext>You are all a bunch of limp wristed weaklings with your god damn new yuppie fonts .
Use '-misc-fixed-medium- * - * - * -14- * - * - * -c- * - * - * ' and view your code as emacs and X11 intended it with hard , cold gloriously pixelated simplicity .</tokentext>
<sentencetext>You are all a bunch of limp wristed weaklings with your god damn new yuppie fonts.
Use '-misc-fixed-medium-*-*-*-14-*-*-*-c-*-*-*' and view your code as emacs and X11 intended it with hard, cold gloriously pixelated simplicity.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30799520</id>
	<title>Re:visual cues</title>
	<author>darkstar949</author>
	<datestamp>1263753720000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>However, I would argue that well written code should also be accompanied by enough well written comments that you should be able to scan the comments to isolate the code that you want to read in-depth. Granted, most code in existence doesn't have the be best comments, but ideally that should be the case.</htmltext>
<tokenext>However , I would argue that well written code should also be accompanied by enough well written comments that you should be able to scan the comments to isolate the code that you want to read in-depth .
Granted , most code in existence does n't have the be best comments , but ideally that should be the case .</tokentext>
<sentencetext>However, I would argue that well written code should also be accompanied by enough well written comments that you should be able to scan the comments to isolate the code that you want to read in-depth.
Granted, most code in existence doesn't have the be best comments, but ideally that should be the case.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797816</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30798708</id>
	<title>Re:Not the bottleneck</title>
	<author>amchugh</author>
	<datestamp>1263746700000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>How about monospaced code &amp; proportional comments?</p></htmltext>
<tokenext>How about monospaced code &amp; proportional comments ?</tokentext>
<sentencetext>How about monospaced code &amp; proportional comments?</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797664</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30799822</id>
	<title>Re:reads faster?</title>
	<author>Anonymous</author>
	<datestamp>1263756120000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>1</modscore>
	<htmltext><p>I'd agree - for me that's definitely true.    With monospace, I know I'm typing on a grid, and I know how things should line up - it helps.</p><p>A mono-spaced font lets you use the space itself to visualize your code.  You can place a  line beside another line to try to find a typo.... that kind of thing.   A proportionally spaced font does not.</p><p>Now, it is true that a good proportionally spaced Serif font is easy to read - perhaps even easier - and in the end, a programmer should program in whatever they are most comfortable with, right?</p><p>I prefer a good monospaced font - if only because that's what I learned on, that's what I'm used to, and I'm an old codger.</p></htmltext>
<tokenext>I 'd agree - for me that 's definitely true .
With monospace , I know I 'm typing on a grid , and I know how things should line up - it helps.A mono-spaced font lets you use the space itself to visualize your code .
You can place a line beside another line to try to find a typo.... that kind of thing .
A proportionally spaced font does not.Now , it is true that a good proportionally spaced Serif font is easy to read - perhaps even easier - and in the end , a programmer should program in whatever they are most comfortable with , right ? I prefer a good monospaced font - if only because that 's what I learned on , that 's what I 'm used to , and I 'm an old codger .</tokentext>
<sentencetext>I'd agree - for me that's definitely true.
With monospace, I know I'm typing on a grid, and I know how things should line up - it helps.A mono-spaced font lets you use the space itself to visualize your code.
You can place a  line beside another line to try to find a typo.... that kind of thing.
A proportionally spaced font does not.Now, it is true that a good proportionally spaced Serif font is easy to read - perhaps even easier - and in the end, a programmer should program in whatever they are most comfortable with, right?I prefer a good monospaced font - if only because that's what I learned on, that's what I'm used to, and I'm an old codger.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797808</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30803666</id>
	<title>Re:Overrated</title>
	<author>mike\_ekim</author>
	<datestamp>1263741720000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>The elastic tabstops demo is nice.  I played with the idea of empty lines having half-height - sometimes I want something grouped together, but not on the next line, and not a whole line in between.  For example, the huge gap in this code:<blockquote><div><p> <tt>struct Foo {<br>  void getFoo();<br>  void getBar();<br> <br>  void setFoo();<br>  void setBar();<br>};</tt></p></div> </blockquote></div>
	</htmltext>
<tokenext>The elastic tabstops demo is nice .
I played with the idea of empty lines having half-height - sometimes I want something grouped together , but not on the next line , and not a whole line in between .
For example , the huge gap in this code : struct Foo { void getFoo ( ) ; void getBar ( ) ; void setFoo ( ) ; void setBar ( ) ; } ;</tokentext>
<sentencetext>The elastic tabstops demo is nice.
I played with the idea of empty lines having half-height - sometimes I want something grouped together, but not on the next line, and not a whole line in between.
For example, the huge gap in this code: struct Foo {  void getFoo();  void getBar();   void setFoo();  void setBar();}; 
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30798022</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797798</id>
	<title>actually i want to have each variable a slightly i</title>
	<author>daveb1</author>
	<datestamp>1263739080000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext>actually i want to have each variable a slightly different colour. That way i can easily follow the use of the variable throughout the entire source. (globals etc.) .</htmltext>
<tokenext>actually i want to have each variable a slightly different colour .
That way i can easily follow the use of the variable throughout the entire source .
( globals etc .
) .</tokentext>
<sentencetext>actually i want to have each variable a slightly different colour.
That way i can easily follow the use of the variable throughout the entire source.
(globals etc.
) .</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30800038</id>
	<title>Proportional fonts for source code?</title>
	<author>janwedekind</author>
	<datestamp>1263757620000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Well, do as you please. You use your font and <a href="http://www.retrojunkie.com/asciiart/people/crawford.txt" title="retrojunkie.com">I use mine</a> [retrojunkie.com].</p></htmltext>
<tokenext>Well , do as you please .
You use your font and I use mine [ retrojunkie.com ] .</tokentext>
<sentencetext>Well, do as you please.
You use your font and I use mine [retrojunkie.com].</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30798660</id>
	<title>Re:Proportional fonts are better to read</title>
	<author>elsJake</author>
	<datestamp>1263746340000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>With proportional text you get a great deal more recognized words. That's great for print but programmers tend to have similarly named variables , because they attribute some sort of related meaning to them.  When reading them with a proportional font you're going to have a lot more recognitions but because you can't easily see the difference most of them will be false positives. Rereading will then add more overhead than reading it right , but slower the first time.</htmltext>
<tokenext>With proportional text you get a great deal more recognized words .
That 's great for print but programmers tend to have similarly named variables , because they attribute some sort of related meaning to them .
When reading them with a proportional font you 're going to have a lot more recognitions but because you ca n't easily see the difference most of them will be false positives .
Rereading will then add more overhead than reading it right , but slower the first time .</tokentext>
<sentencetext>With proportional text you get a great deal more recognized words.
That's great for print but programmers tend to have similarly named variables , because they attribute some sort of related meaning to them.
When reading them with a proportional font you're going to have a lot more recognitions but because you can't easily see the difference most of them will be false positives.
Rereading will then add more overhead than reading it right , but slower the first time.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797634</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30801284</id>
	<title>Re:ProFont ruled the day</title>
	<author>Anonymous</author>
	<datestamp>1263723420000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>I use ProFont for most of my coding as well, but it has a an issue in some applications (mainly Terminal) where some character sequences, (like o/) are replaced with a different character (in this case &#248;). ProFont X[1] solves these issues but it also has issues in Snow Leopard. The K and  characters render differently to ProFont with extra pixels along the diagonals. It's a shame really because it's a great font.</p><p>[1] http://www.faisal.com/software/profontx/</p></htmltext>
<tokenext>I use ProFont for most of my coding as well , but it has a an issue in some applications ( mainly Terminal ) where some character sequences , ( like o/ ) are replaced with a different character ( in this case   ) .
ProFont X [ 1 ] solves these issues but it also has issues in Snow Leopard .
The K and characters render differently to ProFont with extra pixels along the diagonals .
It 's a shame really because it 's a great font .
[ 1 ] http : //www.faisal.com/software/profontx/</tokentext>
<sentencetext>I use ProFont for most of my coding as well, but it has a an issue in some applications (mainly Terminal) where some character sequences, (like o/) are replaced with a different character (in this case ø).
ProFont X[1] solves these issues but it also has issues in Snow Leopard.
The K and  characters render differently to ProFont with extra pixels along the diagonals.
It's a shame really because it's a great font.
[1] http://www.faisal.com/software/profontx/</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797618</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797974</id>
	<title>Link for hinted version</title>
	<author>msgmonkey</author>
	<datestamp>1263740640000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>2</modscore>
	<htmltext><p>I thought I would have a look at this font but it looks terrible on windows with cleartype on at 11points, however I managed to find a hinted version at:</p><p><a href="http://pgl.yoyo.org/bits/tech/inconsolata-cleartype-raph-leviens-inconsolota-font-hinted-for-windows/51:2008-09-25/" title="yoyo.org">http://pgl.yoyo.org/bits/tech/inconsolata-cleartype-raph-leviens-inconsolota-font-hinted-for-windows/51:2008-09-25/</a> [yoyo.org]</p></htmltext>
<tokenext>I thought I would have a look at this font but it looks terrible on windows with cleartype on at 11points , however I managed to find a hinted version at : http : //pgl.yoyo.org/bits/tech/inconsolata-cleartype-raph-leviens-inconsolota-font-hinted-for-windows/51 : 2008-09-25/ [ yoyo.org ]</tokentext>
<sentencetext>I thought I would have a look at this font but it looks terrible on windows with cleartype on at 11points, however I managed to find a hinted version at:http://pgl.yoyo.org/bits/tech/inconsolata-cleartype-raph-leviens-inconsolota-font-hinted-for-windows/51:2008-09-25/ [yoyo.org]</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797630</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30802260</id>
	<title>How about Rich Text Format</title>
	<author>pentalive</author>
	<datestamp>1263730140000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>How about a language that uses the formatting in RTF as a part of the syntax?
<p>
You could include pictures in your code ( which are automatically comments)
</p><p>
The font and size of the code is changeable - you can have parts in a monospaced
font and parts in a proportional font.
</p><p>
Outline levels are used to block statement</p></htmltext>
<tokenext>How about a language that uses the formatting in RTF as a part of the syntax ?
You could include pictures in your code ( which are automatically comments ) The font and size of the code is changeable - you can have parts in a monospaced font and parts in a proportional font .
Outline levels are used to block statement</tokentext>
<sentencetext>How about a language that uses the formatting in RTF as a part of the syntax?
You could include pictures in your code ( which are automatically comments)

The font and size of the code is changeable - you can have parts in a monospaced
font and parts in a proportional font.
Outline levels are used to block statement</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30800672</id>
	<title>A good REAL font</title>
	<author>Lulu of the Lotus-Ea</author>
	<datestamp>1263719580000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I consider the suggestion of using a proportional font for programming frivolous and a bit juvenile.  In fact, I'm of an age where it seems a little off if my SSH backgrounds are not green-on-black (and hence make them so).</p><p>That said, a *good* fixed font really makes a lot of difference.  Not too long ago, I found one called Anonymous Pro, that I have become very fond of:</p><p><a href="http://www.ms-studio.com/FontSales/anonymouspro.html" title="ms-studio.com">http://www.ms-studio.com/FontSales/anonymouspro.html</a> [ms-studio.com]</p><p>It's freely available, TTF, and I've installed it most places.  As much as I hate being forced onto Windows machines, in the few cases where I am, I actually think Consolas is pretty good quality too.</p></htmltext>
<tokenext>I consider the suggestion of using a proportional font for programming frivolous and a bit juvenile .
In fact , I 'm of an age where it seems a little off if my SSH backgrounds are not green-on-black ( and hence make them so ) .That said , a * good * fixed font really makes a lot of difference .
Not too long ago , I found one called Anonymous Pro , that I have become very fond of : http : //www.ms-studio.com/FontSales/anonymouspro.html [ ms-studio.com ] It 's freely available , TTF , and I 've installed it most places .
As much as I hate being forced onto Windows machines , in the few cases where I am , I actually think Consolas is pretty good quality too .</tokentext>
<sentencetext>I consider the suggestion of using a proportional font for programming frivolous and a bit juvenile.
In fact, I'm of an age where it seems a little off if my SSH backgrounds are not green-on-black (and hence make them so).That said, a *good* fixed font really makes a lot of difference.
Not too long ago, I found one called Anonymous Pro, that I have become very fond of:http://www.ms-studio.com/FontSales/anonymouspro.html [ms-studio.com]It's freely available, TTF, and I've installed it most places.
As much as I hate being forced onto Windows machines, in the few cases where I am, I actually think Consolas is pretty good quality too.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30799326</id>
	<title>How important is this reading speed improvement?</title>
	<author>Anonymous</author>
	<datestamp>1263751980000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Today's IDE use special windows and sections to display structures of classes, XML files, schema definitions. Automatic generated program documentation is also already in proportional fonts. While most of the reading is done to lookup features (method names, tags, structural semantics) this is already done with proportional fonts. The only place where you read actual mono spaced text is in an editor to edit a class or function (if you are programming in a non OOP language).</p><p>However, there are other techniques which can improve reading speed at an even bigger scale. You could use domain specific languages (DSL) to generate C, Java, Python, Ruby, Fortran, etc. code. So instead of describing every aspect of every class you can use a problem specific language to model everything. Combined with AOP you can reduce the code base which must be read by humans by 300-400\%. And if you are writing another application for the same domain you are able to reuse a lot of the template and artefacts you used for the first time.</p></htmltext>
<tokenext>Today 's IDE use special windows and sections to display structures of classes , XML files , schema definitions .
Automatic generated program documentation is also already in proportional fonts .
While most of the reading is done to lookup features ( method names , tags , structural semantics ) this is already done with proportional fonts .
The only place where you read actual mono spaced text is in an editor to edit a class or function ( if you are programming in a non OOP language ) .However , there are other techniques which can improve reading speed at an even bigger scale .
You could use domain specific languages ( DSL ) to generate C , Java , Python , Ruby , Fortran , etc .
code. So instead of describing every aspect of every class you can use a problem specific language to model everything .
Combined with AOP you can reduce the code base which must be read by humans by 300-400 \ % .
And if you are writing another application for the same domain you are able to reuse a lot of the template and artefacts you used for the first time .</tokentext>
<sentencetext>Today's IDE use special windows and sections to display structures of classes, XML files, schema definitions.
Automatic generated program documentation is also already in proportional fonts.
While most of the reading is done to lookup features (method names, tags, structural semantics) this is already done with proportional fonts.
The only place where you read actual mono spaced text is in an editor to edit a class or function (if you are programming in a non OOP language).However, there are other techniques which can improve reading speed at an even bigger scale.
You could use domain specific languages (DSL) to generate C, Java, Python, Ruby, Fortran, etc.
code. So instead of describing every aspect of every class you can use a problem specific language to model everything.
Combined with AOP you can reduce the code base which must be read by humans by 300-400\%.
And if you are writing another application for the same domain you are able to reuse a lot of the template and artefacts you used for the first time.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30798268</id>
	<title>I'd love to use a proportional font</title>
	<author>j\_cavera</author>
	<datestamp>1263743520000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>... but my VT102 terminal only has the one and the APL compiler doesn't understand a \t.</htmltext>
<tokenext>... but my VT102 terminal only has the one and the APL compiler does n't understand a \ t .</tokentext>
<sentencetext>... but my VT102 terminal only has the one and the APL compiler doesn't understand a \t.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797554</id>
	<title>Monaco</title>
	<author>psergiu</author>
	<datestamp>1263735840000</datestamp>
	<modclass>Funny</modclass>
	<modscore>3</modscore>
	<htmltext><p>Monaco is fixed-width &amp; good looking.</p></htmltext>
<tokenext>Monaco is fixed-width &amp; good looking .</tokentext>
<sentencetext>Monaco is fixed-width &amp; good looking.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30798254</id>
	<title>Re:Consolas</title>
	<author>Anonymous</author>
	<datestamp>1263743400000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>It's not so much about "readability" (I can read lots of text superfast) as it's about "readability" (I can poinpoint stuff in code structure easily).</p><p>Anyway, Consolas rules my world.</p></htmltext>
<tokenext>It 's not so much about " readability " ( I can read lots of text superfast ) as it 's about " readability " ( I can poinpoint stuff in code structure easily ) .Anyway , Consolas rules my world .</tokentext>
<sentencetext>It's not so much about "readability" (I can read lots of text superfast) as it's about "readability" (I can poinpoint stuff in code structure easily).Anyway, Consolas rules my world.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797584</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30801492</id>
	<title>Black Hole Parens</title>
	<author>SuperKendall</author>
	<datestamp>1263724920000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>They totally lost me in the "better" example for proportional spacing in the link for making the case, when I saw how collapsed a pair of parens [ () ] became in the proportional font - almost invisible, making it hard to recognize function calls.</p><p>In that example the mono-spaced font they chose just sucked, there are many more readable monospaced fonts which would look way better than the proportional example.</p></htmltext>
<tokenext>They totally lost me in the " better " example for proportional spacing in the link for making the case , when I saw how collapsed a pair of parens [ ( ) ] became in the proportional font - almost invisible , making it hard to recognize function calls.In that example the mono-spaced font they chose just sucked , there are many more readable monospaced fonts which would look way better than the proportional example .</tokentext>
<sentencetext>They totally lost me in the "better" example for proportional spacing in the link for making the case, when I saw how collapsed a pair of parens [ () ] became in the proportional font - almost invisible, making it hard to recognize function calls.In that example the mono-spaced font they chose just sucked, there are many more readable monospaced fonts which would look way better than the proportional example.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30822322</id>
	<title>Re:ProFont ruled the day</title>
	<author>drerwk</author>
	<datestamp>1263929700000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>So I dug up the answer - at 9 pt, which was common on 640x480 screens these charachters were not distinct.<p><div class="quote"><p>MPW&rsquo;s default font used to be Monaco 9. This font is also required by the System Software, and is therefore installed on every machine. In addition to the 9-point bitmap font, System Software also supplies a TrueType version of the font. There are a couple of problems with this setup.
First of all, the 9-point bitmap characters are not the same as those supplied by the TrueType version. So, when you print, the print driver normally uses the TrueType font to define the characters, which means it&rsquo;s WYSINWYG (What you see is not what you get). Print your worksheet with Font Substitution turned off, examine the output closely, and you&rsquo;ll see what I mean. (1998 update: As of Mac OS 8.5, this is no longer true. The bitmap and TrueType versions of Monaco have been synchronized. For some reason, though, it was synchronized on the &ldquo;new&rdquo; definition, instead of the traditional version of Monaco.)
The second problem is that the characters in the 9-point bitmap version of Monaco are not always distinct. The &ldquo;I&rdquo; (eye), &ldquo;l&rdquo; (ell), and &ldquo;1&rdquo; (one) characters are very similar, as are &ldquo;O&rdquo; (oh) and &ldquo;0&rdquo; (zero). Some of the punctuation characters are only a single pixel in size, and some of the high-numbered ASCII characters are missing altogether. This makes it very unfriendly as a programmer&rsquo;s font, where a single incorrect character can mean the difference between a successful build and hours-long debugging sessions.</p></div></div>
	</htmltext>
<tokenext>So I dug up the answer - at 9 pt , which was common on 640x480 screens these charachters were not distinct.MPW    s default font used to be Monaco 9 .
This font is also required by the System Software , and is therefore installed on every machine .
In addition to the 9-point bitmap font , System Software also supplies a TrueType version of the font .
There are a couple of problems with this setup .
First of all , the 9-point bitmap characters are not the same as those supplied by the TrueType version .
So , when you print , the print driver normally uses the TrueType font to define the characters , which means it    s WYSINWYG ( What you see is not what you get ) .
Print your worksheet with Font Substitution turned off , examine the output closely , and you    ll see what I mean .
( 1998 update : As of Mac OS 8.5 , this is no longer true .
The bitmap and TrueType versions of Monaco have been synchronized .
For some reason , though , it was synchronized on the    new    definition , instead of the traditional version of Monaco .
) The second problem is that the characters in the 9-point bitmap version of Monaco are not always distinct .
The    I    ( eye ) ,    l    ( ell ) , and    1    ( one ) characters are very similar , as are    O    ( oh ) and    0    ( zero ) .
Some of the punctuation characters are only a single pixel in size , and some of the high-numbered ASCII characters are missing altogether .
This makes it very unfriendly as a programmer    s font , where a single incorrect character can mean the difference between a successful build and hours-long debugging sessions .</tokentext>
<sentencetext>So I dug up the answer - at 9 pt, which was common on 640x480 screens these charachters were not distinct.MPW’s default font used to be Monaco 9.
This font is also required by the System Software, and is therefore installed on every machine.
In addition to the 9-point bitmap font, System Software also supplies a TrueType version of the font.
There are a couple of problems with this setup.
First of all, the 9-point bitmap characters are not the same as those supplied by the TrueType version.
So, when you print, the print driver normally uses the TrueType font to define the characters, which means it’s WYSINWYG (What you see is not what you get).
Print your worksheet with Font Substitution turned off, examine the output closely, and you’ll see what I mean.
(1998 update: As of Mac OS 8.5, this is no longer true.
The bitmap and TrueType versions of Monaco have been synchronized.
For some reason, though, it was synchronized on the “new” definition, instead of the traditional version of Monaco.
)
The second problem is that the characters in the 9-point bitmap version of Monaco are not always distinct.
The “I” (eye), “l” (ell), and “1” (one) characters are very similar, as are “O” (oh) and “0” (zero).
Some of the punctuation characters are only a single pixel in size, and some of the high-numbered ASCII characters are missing altogether.
This makes it very unfriendly as a programmer’s font, where a single incorrect character can mean the difference between a successful build and hours-long debugging sessions.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30801932</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797822</id>
	<title>Python...</title>
	<author>Anonymous</author>
	<datestamp>1263739380000</datestamp>
	<modclass>Troll</modclass>
	<modscore>0</modscore>
	<htmltext><p>The Python zealots will be along shortly to defend their indentation insanity in 3... 2... 1...</p><p>
&nbsp;</p></htmltext>
<tokenext>The Python zealots will be along shortly to defend their indentation insanity in 3... 2... 1.. .  </tokentext>
<sentencetext>The Python zealots will be along shortly to defend their indentation insanity in 3... 2... 1...
 </sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30798084</id>
	<title>Re:Monaco</title>
	<author>Anonymous</author>
	<datestamp>1263741600000</datestamp>
	<modclass>Funny</modclass>
	<modscore>4</modscore>
	<htmltext><p>Bah, you kids and your unique characters.  I use fixedsys, and typing the wrong characters has never been a pr0blem.</p></htmltext>
<tokenext>Bah , you kids and your unique characters .
I use fixedsys , and typing the wrong characters has never been a pr0blem .</tokentext>
<sentencetext>Bah, you kids and your unique characters.
I use fixedsys, and typing the wrong characters has never been a pr0blem.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797608</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797630</id>
	<title>Do the studies apply?</title>
	<author>Anonymous</author>
	<datestamp>1263736740000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>4</modscore>
	<htmltext><p>Reading prose is different from reading code. I'd think that whatever you gain wouldn't be enough to make up for the loss from lack of vertical alignment.</p><p>Additionally, <i>which</i> monospaced font you use matters. You need one that's designed to be readable and to make clear distinctions between 0 and O, l and 1, and so on. I use Raph Levien's <a href="http://www.levien.com/type/myfonts/inconsolata.html" title="levien.com">Inconsolata</a> [levien.com] for coding, and it's excellent (and available under the Open Font License).</p><p>On Fedora, <tt>yum install levien-inconsolata-fonts</tt>.</p></htmltext>
<tokenext>Reading prose is different from reading code .
I 'd think that whatever you gain would n't be enough to make up for the loss from lack of vertical alignment.Additionally , which monospaced font you use matters .
You need one that 's designed to be readable and to make clear distinctions between 0 and O , l and 1 , and so on .
I use Raph Levien 's Inconsolata [ levien.com ] for coding , and it 's excellent ( and available under the Open Font License ) .On Fedora , yum install levien-inconsolata-fonts .</tokentext>
<sentencetext>Reading prose is different from reading code.
I'd think that whatever you gain wouldn't be enough to make up for the loss from lack of vertical alignment.Additionally, which monospaced font you use matters.
You need one that's designed to be readable and to make clear distinctions between 0 and O, l and 1, and so on.
I use Raph Levien's Inconsolata [levien.com] for coding, and it's excellent (and available under the Open Font License).On Fedora, yum install levien-inconsolata-fonts.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30801922</id>
	<title>Re:Monaco</title>
	<author>suffix tree monkey</author>
	<datestamp>1263727620000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>[citation wanted, but not needed]</p><p>Well, not exactly. I'd like to find a font where the ASCII characters are *so* different that it's easy to distinguish between them even in really tiny sizes. That even at the price of branching off from the "standard" letters (I don't mind triangles instead of 'o's etc.).</p><p>Thanks!</p></htmltext>
<tokenext>[ citation wanted , but not needed ] Well , not exactly .
I 'd like to find a font where the ASCII characters are * so * different that it 's easy to distinguish between them even in really tiny sizes .
That even at the price of branching off from the " standard " letters ( I do n't mind triangles instead of 'o 's etc .
) .Thanks !</tokentext>
<sentencetext>[citation wanted, but not needed]Well, not exactly.
I'd like to find a font where the ASCII characters are *so* different that it's easy to distinguish between them even in really tiny sizes.
That even at the price of branching off from the "standard" letters (I don't mind triangles instead of 'o's etc.
).Thanks!</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797608</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30798460</id>
	<title>Re:For bug-free code ...</title>
	<author>Anonymous</author>
	<datestamp>1263744840000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext>That's why I stopped using Wingdings, I was worried about the capital m and the capital n.</htmltext>
<tokenext>That 's why I stopped using Wingdings , I was worried about the capital m and the capital n .</tokentext>
<sentencetext>That's why I stopped using Wingdings, I was worried about the capital m and the capital n.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797590</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30801932</id>
	<title>Re:ProFont ruled the day</title>
	<author>broken\_chaos</author>
	<datestamp>1263727680000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>which may have been identical in the default Monaco.</p></div><p>1, l, I, 0, and O are all distinct characters in Monaco.</p></div>
	</htmltext>
<tokenext>which may have been identical in the default Monaco.1 , l , I , 0 , and O are all distinct characters in Monaco .</tokentext>
<sentencetext>which may have been identical in the default Monaco.1, l, I, 0, and O are all distinct characters in Monaco.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797618</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30800476</id>
	<title>Re:Overrated</title>
	<author>HiThere</author>
	<datestamp>1263761580000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I prefer proportional fonts with serifs...and use tabs for alignment.</p><p>N.B.:  With many proportional fonts you can't use spaces for alignment, as they are about one pixel wide...(well, actually, less).</p><p>OTOH, with a good monospaced font I still find myself preferring tabs for alignment.  It allows me to reformat the entire file merely by changing the number of spaces that each tab represents.</p><p>But I much prefer a font with serifs, whether mono-spaced or not.  It does, however, depend on what I'm writing whether I prefer proportional.  If there's a lot of similar stuff on adjacent lines, then perhaps monospaced is better.  This is, however, relatively unusual.  So I usually prefer proportional.  (But I do use a lot of tabs to align adjacent lines...internally as well as externally.  I'll frequently use a tab on either side of the "=" to facilitate alignment.  When doing so it's important that tab size be somewhere around 3 or 4 spaces, or it starts to look ugly.)</p></htmltext>
<tokenext>I prefer proportional fonts with serifs...and use tabs for alignment.N.B .
: With many proportional fonts you ca n't use spaces for alignment , as they are about one pixel wide... ( well , actually , less ) .OTOH , with a good monospaced font I still find myself preferring tabs for alignment .
It allows me to reformat the entire file merely by changing the number of spaces that each tab represents.But I much prefer a font with serifs , whether mono-spaced or not .
It does , however , depend on what I 'm writing whether I prefer proportional .
If there 's a lot of similar stuff on adjacent lines , then perhaps monospaced is better .
This is , however , relatively unusual .
So I usually prefer proportional .
( But I do use a lot of tabs to align adjacent lines...internally as well as externally .
I 'll frequently use a tab on either side of the " = " to facilitate alignment .
When doing so it 's important that tab size be somewhere around 3 or 4 spaces , or it starts to look ugly .
)</tokentext>
<sentencetext>I prefer proportional fonts with serifs...and use tabs for alignment.N.B.
:  With many proportional fonts you can't use spaces for alignment, as they are about one pixel wide...(well, actually, less).OTOH, with a good monospaced font I still find myself preferring tabs for alignment.
It allows me to reformat the entire file merely by changing the number of spaces that each tab represents.But I much prefer a font with serifs, whether mono-spaced or not.
It does, however, depend on what I'm writing whether I prefer proportional.
If there's a lot of similar stuff on adjacent lines, then perhaps monospaced is better.
This is, however, relatively unusual.
So I usually prefer proportional.
(But I do use a lot of tabs to align adjacent lines...internally as well as externally.
I'll frequently use a tab on either side of the "=" to facilitate alignment.
When doing so it's important that tab size be somewhere around 3 or 4 spaces, or it starts to look ugly.
)</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797572</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30798114</id>
	<title>"Betty or Veronica?"</title>
	<author>Anonymous</author>
	<datestamp>1263741960000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Betty AND Veronica</p></htmltext>
<tokenext>Betty AND Veronica</tokentext>
<sentencetext>Betty AND Veronica</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30801534</id>
	<title>Are you reading or editing?</title>
	<author>joh</author>
	<datestamp>1263725220000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Try to see which characters (they're all unique) these are and position your cursor between them in a hurry with a proportional and a fixed width font: il[I|]</p><p>Anytime you see some coder craning towards the screen with narrowed eyes when selecting something, he's probably using a proportional font. Proportional fonts are better for reading prose, are not good for reading code and are terrible for editing code. Much of this is personal preferences and a few things (like 0 and O looking similar) can be fixed, but a few things are real. Editing characterwise will always be easier when the characters occupy the same space regardless of their actual width.</p><p>IMHO everyone should use a fixed width font for editing, even if it's not code. It's just much easier.</p></htmltext>
<tokenext>Try to see which characters ( they 're all unique ) these are and position your cursor between them in a hurry with a proportional and a fixed width font : il [ I | ] Anytime you see some coder craning towards the screen with narrowed eyes when selecting something , he 's probably using a proportional font .
Proportional fonts are better for reading prose , are not good for reading code and are terrible for editing code .
Much of this is personal preferences and a few things ( like 0 and O looking similar ) can be fixed , but a few things are real .
Editing characterwise will always be easier when the characters occupy the same space regardless of their actual width.IMHO everyone should use a fixed width font for editing , even if it 's not code .
It 's just much easier .</tokentext>
<sentencetext>Try to see which characters (they're all unique) these are and position your cursor between them in a hurry with a proportional and a fixed width font: il[I|]Anytime you see some coder craning towards the screen with narrowed eyes when selecting something, he's probably using a proportional font.
Proportional fonts are better for reading prose, are not good for reading code and are terrible for editing code.
Much of this is personal preferences and a few things (like 0 and O looking similar) can be fixed, but a few things are real.
Editing characterwise will always be easier when the characters occupy the same space regardless of their actual width.IMHO everyone should use a fixed width font for editing, even if it's not code.
It's just much easier.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30801610</id>
	<title>Re:Overrated</title>
	<author>fbjon</author>
	<datestamp>1263725700000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>I wish I could type this message that I'm typing right now in a proportional font.</p></div><p>You could try loading a custom CSS for slashdot with<br>
input { font-family: xyz; }</p></div>
	</htmltext>
<tokenext>I wish I could type this message that I 'm typing right now in a proportional font.You could try loading a custom CSS for slashdot with input { font-family : xyz ; }</tokentext>
<sentencetext>I wish I could type this message that I'm typing right now in a proportional font.You could try loading a custom CSS for slashdot with
input { font-family: xyz; }
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30798296</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30799686</id>
	<title>Re:Overrated</title>
	<author>Anonymous</author>
	<datestamp>1263755040000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>2</modscore>
	<htmltext><p>Sorry, Elastic Tabstops solve nothing. That is just yet another way of interpreting a tab character. The problem with tabs is the tab character itself and the fact that different rendering mechanisms interpret it differently. If you type a tab in an editor which renders it as an 8-character indentation and I view it in an editor which renders it as a 4-character indentation, then what I see is not what you intended. The only thing which works consistently is to use a fixed-width font and space characters for indentation. Any programmer who doesn't grasp this and who puts tabs into his code is obviously not a good rational thinker and is thus probably not a very good programmer.</p></htmltext>
<tokenext>Sorry , Elastic Tabstops solve nothing .
That is just yet another way of interpreting a tab character .
The problem with tabs is the tab character itself and the fact that different rendering mechanisms interpret it differently .
If you type a tab in an editor which renders it as an 8-character indentation and I view it in an editor which renders it as a 4-character indentation , then what I see is not what you intended .
The only thing which works consistently is to use a fixed-width font and space characters for indentation .
Any programmer who does n't grasp this and who puts tabs into his code is obviously not a good rational thinker and is thus probably not a very good programmer .</tokentext>
<sentencetext>Sorry, Elastic Tabstops solve nothing.
That is just yet another way of interpreting a tab character.
The problem with tabs is the tab character itself and the fact that different rendering mechanisms interpret it differently.
If you type a tab in an editor which renders it as an 8-character indentation and I view it in an editor which renders it as a 4-character indentation, then what I see is not what you intended.
The only thing which works consistently is to use a fixed-width font and space characters for indentation.
Any programmer who doesn't grasp this and who puts tabs into his code is obviously not a good rational thinker and is thus probably not a very good programmer.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30798022</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797740</id>
	<title>Examples...</title>
	<author>wisnoskij</author>
	<datestamp>1263738480000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>2</modscore>
	<htmltext>I like the examples they show to prove their point.<br>
Fixed width Monaco 10pt, which comes out too small and kind of blurry to me.<br>
and Proportional Helvetica Neue 12pt, which is in a bigger font and is actually reasonable sized.<br>
<br>
so yes, a reasonable sized proportional font is easier to read then a undersized fixed width font...</htmltext>
<tokenext>I like the examples they show to prove their point .
Fixed width Monaco 10pt , which comes out too small and kind of blurry to me .
and Proportional Helvetica Neue 12pt , which is in a bigger font and is actually reasonable sized .
so yes , a reasonable sized proportional font is easier to read then a undersized fixed width font.. .</tokentext>
<sentencetext>I like the examples they show to prove their point.
Fixed width Monaco 10pt, which comes out too small and kind of blurry to me.
and Proportional Helvetica Neue 12pt, which is in a bigger font and is actually reasonable sized.
so yes, a reasonable sized proportional font is easier to read then a undersized fixed width font...</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30802920</id>
	<title>Re:For bug-free code ...</title>
	<author>coaxial</author>
	<datestamp>1263735240000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Pfft.  Wingdings or nothing.</p></htmltext>
<tokenext>Pfft .
Wingdings or nothing .</tokentext>
<sentencetext>Pfft.
Wingdings or nothing.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797590</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30798470</id>
	<title>Plan 9 has always used proportional fonts...</title>
	<author>CondeZer0</author>
	<datestamp>1263745020000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>4</modscore>
	<htmltext><p>The programming environments by Rob Pike use proportional fonts by default. Both <a href="http://acme.cat-v.org/" title="cat-v.org">Acme</a> [cat-v.org] (also used by Dennis Ritchie) and Rob's previous text editor <a href="http://sam.cat-v.org/" title="cat-v.org">Sam</a> [cat-v.org] (still used by Ken Thompson, Brian Kernighan and Bjarne Stroustrup).</p><p>The rio terminal windows also use proportional fonts.</p><p>At first (like many other things from the Plan 9 world) the lack of precise control about how everything spaced can be a bit frustrating, but once you learn to stop worrying about it, it can be rather pleasant and liberating to use (good) proportional fonts for writing code.</p></htmltext>
<tokenext>The programming environments by Rob Pike use proportional fonts by default .
Both Acme [ cat-v.org ] ( also used by Dennis Ritchie ) and Rob 's previous text editor Sam [ cat-v.org ] ( still used by Ken Thompson , Brian Kernighan and Bjarne Stroustrup ) .The rio terminal windows also use proportional fonts.At first ( like many other things from the Plan 9 world ) the lack of precise control about how everything spaced can be a bit frustrating , but once you learn to stop worrying about it , it can be rather pleasant and liberating to use ( good ) proportional fonts for writing code .</tokentext>
<sentencetext>The programming environments by Rob Pike use proportional fonts by default.
Both Acme [cat-v.org] (also used by Dennis Ritchie) and Rob's previous text editor Sam [cat-v.org] (still used by Ken Thompson, Brian Kernighan and Bjarne Stroustrup).The rio terminal windows also use proportional fonts.At first (like many other things from the Plan 9 world) the lack of precise control about how everything spaced can be a bit frustrating, but once you learn to stop worrying about it, it can be rather pleasant and liberating to use (good) proportional fonts for writing code.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30806022</id>
	<title>Re:Overrated</title>
	<author>Anonymous</author>
	<datestamp>1263813180000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Used this exact situation the other day, whilst scanning down a list of email addresses, all of which followed the naming convention of 8 chars followed by the domain.  Whilst looking for something else, I noticed three email addresses that were incorrect, purely because the @ was in the wrong column.  I probably wouldn't have noticed if the font had been proportional.</p></htmltext>
<tokenext>Used this exact situation the other day , whilst scanning down a list of email addresses , all of which followed the naming convention of 8 chars followed by the domain .
Whilst looking for something else , I noticed three email addresses that were incorrect , purely because the @ was in the wrong column .
I probably would n't have noticed if the font had been proportional .</tokentext>
<sentencetext>Used this exact situation the other day, whilst scanning down a list of email addresses, all of which followed the naming convention of 8 chars followed by the domain.
Whilst looking for something else, I noticed three email addresses that were incorrect, purely because the @ was in the wrong column.
I probably wouldn't have noticed if the font had been proportional.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30798366</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30806616</id>
	<title>Re:Missing the Point</title>
	<author>RedWizzard</author>
	<datestamp>1263820560000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>In code, however, it makes a world of difference, and therefore it doesn't make sense to use a font that may cause confusion between a pair of parentheses '()' and a zero '0', an 'I' and an 'l', a single dash '-' and two dashes '--', etc.</p></div><p>You know it is possible to design a proportional font which keeps all the different characters visually distinct, right?</p></div>
	</htmltext>
<tokenext>In code , however , it makes a world of difference , and therefore it does n't make sense to use a font that may cause confusion between a pair of parentheses ' ( ) ' and a zero '0 ' , an 'I ' and an 'l ' , a single dash '- ' and two dashes '-- ' , etc.You know it is possible to design a proportional font which keeps all the different characters visually distinct , right ?</tokentext>
<sentencetext>In code, however, it makes a world of difference, and therefore it doesn't make sense to use a font that may cause confusion between a pair of parentheses '()' and a zero '0', an 'I' and an 'l', a single dash '-' and two dashes '--', etc.You know it is possible to design a proportional font which keeps all the different characters visually distinct, right?
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30798326</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30799180</id>
	<title>Obligatory</title>
	<author>Anne Thwacks</author>
	<datestamp>1263750900000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>I write Fortran4 you insensitive clod.</htmltext>
<tokenext>I write Fortran4 you insensitive clod .</tokentext>
<sentencetext>I write Fortran4 you insensitive clod.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30799960</id>
	<title>Re:Overrated</title>
	<author>nedlohs</author>
	<datestamp>1263757020000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>And yet every person in my shared office in the late 90s who used a proportional font for programming also  mainly programmed in python. And of course the examples in TFA are python, so that makes 100\% of the people I know and don't know who claim to use proportional fonts for programming are also python programmers.</p><p>A proportional font has no effect at all on leading spaces, which are the only ones that matter in python in ways they don't in most other languages.</p><p>So why would it matter to python programmers?</p></htmltext>
<tokenext>And yet every person in my shared office in the late 90s who used a proportional font for programming also mainly programmed in python .
And of course the examples in TFA are python , so that makes 100 \ % of the people I know and do n't know who claim to use proportional fonts for programming are also python programmers.A proportional font has no effect at all on leading spaces , which are the only ones that matter in python in ways they do n't in most other languages.So why would it matter to python programmers ?</tokentext>
<sentencetext>And yet every person in my shared office in the late 90s who used a proportional font for programming also  mainly programmed in python.
And of course the examples in TFA are python, so that makes 100\% of the people I know and don't know who claim to use proportional fonts for programming are also python programmers.A proportional font has no effect at all on leading spaces, which are the only ones that matter in python in ways they don't in most other languages.So why would it matter to python programmers?</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30799248</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30799628</id>
	<title>Re:Overrated</title>
	<author>Anonymous</author>
	<datestamp>1263754620000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Cool! I remember playing those Buick disks we used to get in the mail. I was using your software on a Mac in 1990 and didn't even know it. We didn't end up buying any Buicks, but always found the disks rather interesting.</p><p>These days I'm working in Python, so tabs, spaces, and whatnot are both crucial and infuriating.</p><p>For the record, I use non-antialiased Monaco with a variety of syntax coloring on a black background. LCDs begin to sort of burn my eyes if I'm sitting at one using a white background for too long.</p></htmltext>
<tokenext>Cool !
I remember playing those Buick disks we used to get in the mail .
I was using your software on a Mac in 1990 and did n't even know it .
We did n't end up buying any Buicks , but always found the disks rather interesting.These days I 'm working in Python , so tabs , spaces , and whatnot are both crucial and infuriating.For the record , I use non-antialiased Monaco with a variety of syntax coloring on a black background .
LCDs begin to sort of burn my eyes if I 'm sitting at one using a white background for too long .</tokentext>
<sentencetext>Cool!
I remember playing those Buick disks we used to get in the mail.
I was using your software on a Mac in 1990 and didn't even know it.
We didn't end up buying any Buicks, but always found the disks rather interesting.These days I'm working in Python, so tabs, spaces, and whatnot are both crucial and infuriating.For the record, I use non-antialiased Monaco with a variety of syntax coloring on a black background.
LCDs begin to sort of burn my eyes if I'm sitting at one using a white background for too long.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30798296</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797942</id>
	<title>Use fonts made for programming.</title>
	<author>mindwanderer</author>
	<datestamp>1263740280000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Proportional fonts: look pretty, increase readibility of words.<br>
Monospaced fonts: increase readibility of code by making all symbols very distinct (ie. ( from {, O from 0, -- not a single line, etc.). The 14\% improvement you gain in reading keywords and variable and fuction names is nothing compared to the bugs that arise from similar-looking symbols. <br>
<br>
I use Terminus, with no smoothing of any kind. Just raw, beautiful pixels.</htmltext>
<tokenext>Proportional fonts : look pretty , increase readibility of words .
Monospaced fonts : increase readibility of code by making all symbols very distinct ( ie .
( from { , O from 0 , -- not a single line , etc. ) .
The 14 \ % improvement you gain in reading keywords and variable and fuction names is nothing compared to the bugs that arise from similar-looking symbols .
I use Terminus , with no smoothing of any kind .
Just raw , beautiful pixels .</tokentext>
<sentencetext>Proportional fonts: look pretty, increase readibility of words.
Monospaced fonts: increase readibility of code by making all symbols very distinct (ie.
( from {, O from 0, -- not a single line, etc.).
The 14\% improvement you gain in reading keywords and variable and fuction names is nothing compared to the bugs that arise from similar-looking symbols.
I use Terminus, with no smoothing of any kind.
Just raw, beautiful pixels.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30800392</id>
	<title>I did this quite a bit</title>
	<author>spitzak</author>
	<datestamp>1263760800000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>From 1986 to 1993 I used proportional fonts in terminals and in the text editor (which was Emacs run in the terminal). It worked quite well. I fully expected this to appear on it's own and am rather disappointed that my ideas never seem to have happened again. I could try to make a program that uses them but do we really need another terminal emulator?</p><p>I have no idea if the code I wrote can be found: first is the NeXT-machine terminal emulator made by Mark of the Unicorn called "Communicae". Second is a terminal emulator written for the Sun NeWS system called "jet".</p><p>Both programs used the same technique based on getting the best output from programs expecting fixed-sized fonts. First of all spaces were rendered as "en spaces", actually it used the width of a '2' character. This made words be somewhat spaced apart but made most tables of numbers line up. Second was that 3 or more spaces, and also a tab character, would move to the N*en position, regardless of the text earlier, where N is the number of characters (plus the round up to multiple of 8 by tab characters). In most fonts this would make a wider space, if not I think it avoided overprinting by instead making the space zero sized rather than negative.</p><p>The rules were limited by them being run when updating the display. On modern machines I would think much more complex pattern-matching rules could be used, such as detecting alignment in adjacent rows, and detecting usage of | and - and + in ascii art and replacing it with line drawings.</p></htmltext>
<tokenext>From 1986 to 1993 I used proportional fonts in terminals and in the text editor ( which was Emacs run in the terminal ) .
It worked quite well .
I fully expected this to appear on it 's own and am rather disappointed that my ideas never seem to have happened again .
I could try to make a program that uses them but do we really need another terminal emulator ? I have no idea if the code I wrote can be found : first is the NeXT-machine terminal emulator made by Mark of the Unicorn called " Communicae " .
Second is a terminal emulator written for the Sun NeWS system called " jet " .Both programs used the same technique based on getting the best output from programs expecting fixed-sized fonts .
First of all spaces were rendered as " en spaces " , actually it used the width of a '2 ' character .
This made words be somewhat spaced apart but made most tables of numbers line up .
Second was that 3 or more spaces , and also a tab character , would move to the N * en position , regardless of the text earlier , where N is the number of characters ( plus the round up to multiple of 8 by tab characters ) .
In most fonts this would make a wider space , if not I think it avoided overprinting by instead making the space zero sized rather than negative.The rules were limited by them being run when updating the display .
On modern machines I would think much more complex pattern-matching rules could be used , such as detecting alignment in adjacent rows , and detecting usage of | and - and + in ascii art and replacing it with line drawings .</tokentext>
<sentencetext>From 1986 to 1993 I used proportional fonts in terminals and in the text editor (which was Emacs run in the terminal).
It worked quite well.
I fully expected this to appear on it's own and am rather disappointed that my ideas never seem to have happened again.
I could try to make a program that uses them but do we really need another terminal emulator?I have no idea if the code I wrote can be found: first is the NeXT-machine terminal emulator made by Mark of the Unicorn called "Communicae".
Second is a terminal emulator written for the Sun NeWS system called "jet".Both programs used the same technique based on getting the best output from programs expecting fixed-sized fonts.
First of all spaces were rendered as "en spaces", actually it used the width of a '2' character.
This made words be somewhat spaced apart but made most tables of numbers line up.
Second was that 3 or more spaces, and also a tab character, would move to the N*en position, regardless of the text earlier, where N is the number of characters (plus the round up to multiple of 8 by tab characters).
In most fonts this would make a wider space, if not I think it avoided overprinting by instead making the space zero sized rather than negative.The rules were limited by them being run when updating the display.
On modern machines I would think much more complex pattern-matching rules could be used, such as detecting alignment in adjacent rows, and detecting usage of | and - and + in ascii art and replacing it with line drawings.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30799914</id>
	<title>Re:Proportional fonts are better to read</title>
	<author>Anonymous</author>
	<datestamp>1263756720000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>&gt; it's likely that proportional fonts are better to read</p><p>What is 'better to read' is entirely dependent on what one is used to.</p><p>As you say, each word is like a picture, but there is no universal, automatic, built-in 'best', they are all built by experience. I was once a punch card and line printer COBOL programmer. I can still read all upper case fixed font easily because I got used to it and built the 'words pictures' required.</p><p>Now I use mixed case monospaced font with indented and vertically aligned parts. It is the best for me because I have built all the 'word pictures' required and identify the meaning of the alignments. If I see code in proportional fonts it becomes a meaningless jumble that I have to work at to understand.</p><p>Perhaps new programmers who have only worked before with proportional fonts for reading and word processing find that monospaced is 'hard'. But that is only because they haven't adjusted yet.</p></htmltext>
<tokenext>&gt; it 's likely that proportional fonts are better to readWhat is 'better to read ' is entirely dependent on what one is used to.As you say , each word is like a picture , but there is no universal , automatic , built-in 'best ' , they are all built by experience .
I was once a punch card and line printer COBOL programmer .
I can still read all upper case fixed font easily because I got used to it and built the 'words pictures ' required.Now I use mixed case monospaced font with indented and vertically aligned parts .
It is the best for me because I have built all the 'word pictures ' required and identify the meaning of the alignments .
If I see code in proportional fonts it becomes a meaningless jumble that I have to work at to understand.Perhaps new programmers who have only worked before with proportional fonts for reading and word processing find that monospaced is 'hard' .
But that is only because they have n't adjusted yet .</tokentext>
<sentencetext>&gt; it's likely that proportional fonts are better to readWhat is 'better to read' is entirely dependent on what one is used to.As you say, each word is like a picture, but there is no universal, automatic, built-in 'best', they are all built by experience.
I was once a punch card and line printer COBOL programmer.
I can still read all upper case fixed font easily because I got used to it and built the 'words pictures' required.Now I use mixed case monospaced font with indented and vertically aligned parts.
It is the best for me because I have built all the 'word pictures' required and identify the meaning of the alignments.
If I see code in proportional fonts it becomes a meaningless jumble that I have to work at to understand.Perhaps new programmers who have only worked before with proportional fonts for reading and word processing find that monospaced is 'hard'.
But that is only because they haven't adjusted yet.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797634</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30799432</id>
	<title>setfont r.psf</title>
	<author>Jim Hall</author>
	<datestamp>1263753060000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>When I started in computers (1993?) we did our programming at the console. And I remember being very thrilled the day I found that Linux had a "setfont" command, to set the console font.</p><p>"r.psf" was a <em>great</em> font. It set the console to a kind of "Times"-like font. Except it was still monospace, 80x25. The serifs made text really easy to read. Numbers looked distinctly different from letters, and certain digits (3, etc.) were "dropped" a little. You never could mistake <tt>1</tt> for <tt>l</tt> or <tt>|</tt>, or <tt>O</tt> for <tt>0</tt>, and so on.</p><p>Combined with setting the foreground "grey" and the background "blue", it made reading/writing code a snap, and the console experience very pleasant. For that first year, I preferred doing everything at the command line, and would start X11 only if I needed to do something that required graphics (like, gnuplot.)</p></htmltext>
<tokenext>When I started in computers ( 1993 ?
) we did our programming at the console .
And I remember being very thrilled the day I found that Linux had a " setfont " command , to set the console font .
" r.psf " was a great font .
It set the console to a kind of " Times " -like font .
Except it was still monospace , 80x25 .
The serifs made text really easy to read .
Numbers looked distinctly different from letters , and certain digits ( 3 , etc .
) were " dropped " a little .
You never could mistake 1 for l or | , or O for 0 , and so on.Combined with setting the foreground " grey " and the background " blue " , it made reading/writing code a snap , and the console experience very pleasant .
For that first year , I preferred doing everything at the command line , and would start X11 only if I needed to do something that required graphics ( like , gnuplot .
)</tokentext>
<sentencetext>When I started in computers (1993?
) we did our programming at the console.
And I remember being very thrilled the day I found that Linux had a "setfont" command, to set the console font.
"r.psf" was a great font.
It set the console to a kind of "Times"-like font.
Except it was still monospace, 80x25.
The serifs made text really easy to read.
Numbers looked distinctly different from letters, and certain digits (3, etc.
) were "dropped" a little.
You never could mistake 1 for l or |, or O for 0, and so on.Combined with setting the foreground "grey" and the background "blue", it made reading/writing code a snap, and the console experience very pleasant.
For that first year, I preferred doing everything at the command line, and would start X11 only if I needed to do something that required graphics (like, gnuplot.
)</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30823198</id>
	<title>Re:Overrated</title>
	<author>BlindSpot</author>
	<datestamp>1263932760000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>No way!  Like most decent developers, I consider my code to be an artistic work, which means that if I write it with the indent at 4 spaces then damnit I want the world to see it exactly as I wrote it.  You don't get to move Mona Lisa around inside the frame, so why should you think you can change the appearance of <b>my</b> masterpiece?!</p></htmltext>
<tokenext>No way !
Like most decent developers , I consider my code to be an artistic work , which means that if I write it with the indent at 4 spaces then damnit I want the world to see it exactly as I wrote it .
You do n't get to move Mona Lisa around inside the frame , so why should you think you can change the appearance of my masterpiece ?
!</tokentext>
<sentencetext>No way!
Like most decent developers, I consider my code to be an artistic work, which means that if I write it with the indent at 4 spaces then damnit I want the world to see it exactly as I wrote it.
You don't get to move Mona Lisa around inside the frame, so why should you think you can change the appearance of my masterpiece?
!</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30799306</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30799892</id>
	<title>So many armchair scientists!</title>
	<author>wonkavader</author>
	<datestamp>1263756540000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Long ago, people used to do real studies.  They timed people reading text, and they found that serifed fonts and proportional fonts were easiest to read, meaning people could read the texts faster.</p><p>All through the responses to this article I see people making assertions that coding isn't reading, that this won't speed things up, paper is different from screens, punctuation would be too hard to read, etc.</p><p>OK, where are your studies to back this up?</p><p>So many assumptions.  It would be nice if someone here said instead "OK, I'll test this with my team and get back to you in a week."</p></htmltext>
<tokenext>Long ago , people used to do real studies .
They timed people reading text , and they found that serifed fonts and proportional fonts were easiest to read , meaning people could read the texts faster.All through the responses to this article I see people making assertions that coding is n't reading , that this wo n't speed things up , paper is different from screens , punctuation would be too hard to read , etc.OK , where are your studies to back this up ? So many assumptions .
It would be nice if someone here said instead " OK , I 'll test this with my team and get back to you in a week .
"</tokentext>
<sentencetext>Long ago, people used to do real studies.
They timed people reading text, and they found that serifed fonts and proportional fonts were easiest to read, meaning people could read the texts faster.All through the responses to this article I see people making assertions that coding isn't reading, that this won't speed things up, paper is different from screens, punctuation would be too hard to read, etc.OK, where are your studies to back this up?So many assumptions.
It would be nice if someone here said instead "OK, I'll test this with my team and get back to you in a week.
"</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797874</id>
	<title>Stroustrup chose proportional-width</title>
	<author>Anonymous</author>
	<datestamp>1263739860000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>4</modscore>
	<htmltext><p>All code in Stroustrup's "The C++ Programming Language" is presented in a proportional-width font: <i>"At first glance, this presentation style will seem 'unnatural' to programmers accustomed to seeing code in constant-width fonts. However, proportional-width fonts are generally regarded as better than constant-width fonts for presentation of text. Using a proportional-width font also allows me to present code with fewer illogical line breaks. Furthermore, my experiments show that most people find the new style more readable after a short while."</i>

</p><p>Not only is the font proportional, but it's bold, italic, and serif as well. Now, reading a textbook is of course pretty different from editing on-screen, but I remember reconsidering some of my habits after reading that book. That code ain't hard to read.</p></htmltext>
<tokenext>All code in Stroustrup 's " The C + + Programming Language " is presented in a proportional-width font : " At first glance , this presentation style will seem 'unnatural ' to programmers accustomed to seeing code in constant-width fonts .
However , proportional-width fonts are generally regarded as better than constant-width fonts for presentation of text .
Using a proportional-width font also allows me to present code with fewer illogical line breaks .
Furthermore , my experiments show that most people find the new style more readable after a short while .
" Not only is the font proportional , but it 's bold , italic , and serif as well .
Now , reading a textbook is of course pretty different from editing on-screen , but I remember reconsidering some of my habits after reading that book .
That code ai n't hard to read .</tokentext>
<sentencetext>All code in Stroustrup's "The C++ Programming Language" is presented in a proportional-width font: "At first glance, this presentation style will seem 'unnatural' to programmers accustomed to seeing code in constant-width fonts.
However, proportional-width fonts are generally regarded as better than constant-width fonts for presentation of text.
Using a proportional-width font also allows me to present code with fewer illogical line breaks.
Furthermore, my experiments show that most people find the new style more readable after a short while.
"

Not only is the font proportional, but it's bold, italic, and serif as well.
Now, reading a textbook is of course pretty different from editing on-screen, but I remember reconsidering some of my habits after reading that book.
That code ain't hard to read.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30805658</id>
	<title>Not the issue</title>
	<author>jandersen</author>
	<datestamp>1263807780000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><nobr> <wbr></nobr></p><div class="quote"><p>... proportional fonts can be read 14\% faster than fixed-width fonts</p></div><p>Does that really make any difference at all in programming? I doubt it; understanding source code does not hinge on how fast you could read the text, in my experience. What really helps is something else:</p><p>- Good indentation that follows the block structure of the code<br>- Good symbol names that are neither too simple nor too rich in information<br>- Good comments that explain why one has chosen an unusual algorithm and that sort of thing</p><p>I think when you read code, you don't read through each letter, you perceive each keyword as a whole. This process gets easier when you always use the same font in your editor, because the keywords then always have the same "shape". Personally I find the "grid-structure" of fixed-width font helpful when writing code, because I can relatively easily format the layout of things, which I occasionally do - eg. when I set up data in an array or table form.</p></div>
	</htmltext>
<tokenext>... proportional fonts can be read 14 \ % faster than fixed-width fontsDoes that really make any difference at all in programming ?
I doubt it ; understanding source code does not hinge on how fast you could read the text , in my experience .
What really helps is something else : - Good indentation that follows the block structure of the code- Good symbol names that are neither too simple nor too rich in information- Good comments that explain why one has chosen an unusual algorithm and that sort of thingI think when you read code , you do n't read through each letter , you perceive each keyword as a whole .
This process gets easier when you always use the same font in your editor , because the keywords then always have the same " shape " .
Personally I find the " grid-structure " of fixed-width font helpful when writing code , because I can relatively easily format the layout of things , which I occasionally do - eg .
when I set up data in an array or table form .</tokentext>
<sentencetext> ... proportional fonts can be read 14\% faster than fixed-width fontsDoes that really make any difference at all in programming?
I doubt it; understanding source code does not hinge on how fast you could read the text, in my experience.
What really helps is something else:- Good indentation that follows the block structure of the code- Good symbol names that are neither too simple nor too rich in information- Good comments that explain why one has chosen an unusual algorithm and that sort of thingI think when you read code, you don't read through each letter, you perceive each keyword as a whole.
This process gets easier when you always use the same font in your editor, because the keywords then always have the same "shape".
Personally I find the "grid-structure" of fixed-width font helpful when writing code, because I can relatively easily format the layout of things, which I occasionally do - eg.
when I set up data in an array or table form.
	</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30798366</id>
	<title>Re:Overrated</title>
	<author>Yvanhoe</author>
	<datestamp>1263744240000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>2</modscore>
	<htmltext>Actually, it is less error-prone to work with fixed fonts, IMHO.<br>
In many occurences, one can anticipate if one line will have one more or one less characters than the previous one. Having a way to quickly check this gives a little supplemantal layer of proof-reading.
<br> <br>
<tt>
this-&gt;posx=0;<br>
this-&gt;posy=0;<br>
tis-&gt;ttl=40;<br>
this-&gt;source="";</tt> <br>
The typo is easier to spot in fixed font.</htmltext>
<tokenext>Actually , it is less error-prone to work with fixed fonts , IMHO .
In many occurences , one can anticipate if one line will have one more or one less characters than the previous one .
Having a way to quickly check this gives a little supplemantal layer of proof-reading .
this- &gt; posx = 0 ; this- &gt; posy = 0 ; t is- &gt; ttl = 40 ; this- &gt; source = " " ; The typo is easier to spot in fixed font .</tokentext>
<sentencetext>Actually, it is less error-prone to work with fixed fonts, IMHO.
In many occurences, one can anticipate if one line will have one more or one less characters than the previous one.
Having a way to quickly check this gives a little supplemantal layer of proof-reading.
this-&gt;posx=0;
this-&gt;posy=0;
tis-&gt;ttl=40;
this-&gt;source=""; 
The typo is easier to spot in fixed font.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797572</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30805860</id>
	<title>Re:fixed</title>
	<author>Kronos.</author>
	<datestamp>1263811200000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Very true, 6x13 is the way to go. When I have to use Windows IDE's I install the truetype version, it makes programming in flexbuilder more legible. I may be stuck in my ways but I'm also not about to change something that clearly works for me.</p><p>The proportional example in the article is more difficult for me to read, to others it's the other way around. It all comes down to personal preference BUT....<nobr> <wbr></nobr>... whatever your preference, everyone needs to  keep their tab widths/spaces consistent so it can be read nicely by others, whatever they chose to use.</p></htmltext>
<tokenext>Very true , 6x13 is the way to go .
When I have to use Windows IDE 's I install the truetype version , it makes programming in flexbuilder more legible .
I may be stuck in my ways but I 'm also not about to change something that clearly works for me.The proportional example in the article is more difficult for me to read , to others it 's the other way around .
It all comes down to personal preference BUT.... ... whatever your preference , everyone needs to keep their tab widths/spaces consistent so it can be read nicely by others , whatever they chose to use .</tokentext>
<sentencetext>Very true, 6x13 is the way to go.
When I have to use Windows IDE's I install the truetype version, it makes programming in flexbuilder more legible.
I may be stuck in my ways but I'm also not about to change something that clearly works for me.The proportional example in the article is more difficult for me to read, to others it's the other way around.
It all comes down to personal preference BUT.... ... whatever your preference, everyone needs to  keep their tab widths/spaces consistent so it can be read nicely by others, whatever they chose to use.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797606</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30801400</id>
	<title>Re:Consolas</title>
	<author>crazybilly</author>
	<datestamp>1263724320000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Gotta agree with Consolas--all programming issues aside, lowercase "g" is gorgeous.
<p>
If only Consolas wasn't a M$ product. Or to put it the way I really think, if only Consolas was open source...Since it's not, I use Liberation Mono on a big screen and Droid Sans Mono at home.</p></htmltext>
<tokenext>Got ta agree with Consolas--all programming issues aside , lowercase " g " is gorgeous .
If only Consolas was n't a M $ product .
Or to put it the way I really think , if only Consolas was open source...Since it 's not , I use Liberation Mono on a big screen and Droid Sans Mono at home .</tokentext>
<sentencetext>Gotta agree with Consolas--all programming issues aside, lowercase "g" is gorgeous.
If only Consolas wasn't a M$ product.
Or to put it the way I really think, if only Consolas was open source...Since it's not, I use Liberation Mono on a big screen and Droid Sans Mono at home.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797584</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30798432</id>
	<title>Re:Old news</title>
	<author>maxume</author>
	<datestamp>1263744720000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Have they changed the summary since you read it? Right now, it refers to the blog posting as being 'old'.</p></htmltext>
<tokenext>Have they changed the summary since you read it ?
Right now , it refers to the blog posting as being 'old' .</tokentext>
<sentencetext>Have they changed the summary since you read it?
Right now, it refers to the blog posting as being 'old'.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797688</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797800</id>
	<title>Matter of taste</title>
	<author>Anonymous</author>
	<datestamp>1263739140000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Choice of fonts is very subjective, similar to look of a desktop environment.<br>Take your pick.<br>http://www.codeproject.com/KB/work/FontSurvey.aspx</p><p>My favourite is Terminus. Unbeatable especially in environments without anti-aliasing.<br>http://fractal.csie.org/~eric/wiki/Terminus\_font</p></htmltext>
<tokenext>Choice of fonts is very subjective , similar to look of a desktop environment.Take your pick.http : //www.codeproject.com/KB/work/FontSurvey.aspxMy favourite is Terminus .
Unbeatable especially in environments without anti-aliasing.http : //fractal.csie.org/ ~ eric/wiki/Terminus \ _font</tokentext>
<sentencetext>Choice of fonts is very subjective, similar to look of a desktop environment.Take your pick.http://www.codeproject.com/KB/work/FontSurvey.aspxMy favourite is Terminus.
Unbeatable especially in environments without anti-aliasing.http://fractal.csie.org/~eric/wiki/Terminus\_font</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30802270</id>
	<title>Times New Roman in Xcode</title>
	<author>spinspin</author>
	<datestamp>1263730260000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Times New Roman looks really good to my eye.<br>
This is my Xcode setup:<br>
<a href="http://vectorvector.tumblr.com/post/339810337/proportional-font-programming" title="tumblr.com" rel="nofollow">http://vectorvector.tumblr.com/post/339810337/proportional-font-programming</a> [tumblr.com] <br>
(I link to the downloadable<nobr> <wbr></nobr>.xccolortheme file)</p><p>Worst to my eye: Monaco and Arial.</p></htmltext>
<tokenext>Times New Roman looks really good to my eye .
This is my Xcode setup : http : //vectorvector.tumblr.com/post/339810337/proportional-font-programming [ tumblr.com ] ( I link to the downloadable .xccolortheme file ) Worst to my eye : Monaco and Arial .</tokentext>
<sentencetext>Times New Roman looks really good to my eye.
This is my Xcode setup:
http://vectorvector.tumblr.com/post/339810337/proportional-font-programming [tumblr.com] 
(I link to the downloadable .xccolortheme file)Worst to my eye: Monaco and Arial.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30800034</id>
	<title>What's the point?</title>
	<author>Anonymous</author>
	<datestamp>1263757620000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>I'm a <a href="http://en.wikipedia.org/wiki/Whitespace\_(programming\_language)" title="wikipedia.org" rel="nofollow">Whitespace</a> [wikipedia.org] developer, you insensitive clod!</p></htmltext>
<tokenext>I 'm a Whitespace [ wikipedia.org ] developer , you insensitive clod !</tokentext>
<sentencetext>I'm a Whitespace [wikipedia.org] developer, you insensitive clod!</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30803982</id>
	<title>Re:For bug-free code ...</title>
	<author>fm6</author>
	<datestamp>1263744660000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Unfortunately, your software will probably be pulled after a couple of weeks in favor of a reality show.</p></htmltext>
<tokenext>Unfortunately , your software will probably be pulled after a couple of weeks in favor of a reality show .</tokentext>
<sentencetext>Unfortunately, your software will probably be pulled after a couple of weeks in favor of a reality show.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797590</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30802136</id>
	<title>Re:Consolas</title>
	<author>sanosuke001</author>
	<datestamp>1263729300000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>I've been using Consolas for almost a year now and I love it. I've even switched my default font at home to it. (browser, text editors, command windows, etc)<br> <br>

Proportional fonts are evil.</htmltext>
<tokenext>I 've been using Consolas for almost a year now and I love it .
I 've even switched my default font at home to it .
( browser , text editors , command windows , etc ) Proportional fonts are evil .</tokentext>
<sentencetext>I've been using Consolas for almost a year now and I love it.
I've even switched my default font at home to it.
(browser, text editors, command windows, etc) 

Proportional fonts are evil.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797584</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797910</id>
	<title>type geek here</title>
	<author>Anonymous</author>
	<datestamp>1263740040000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext>I'm a fairly serious typography geek, and I can tell you that for something like programming, fixed-width fonts make a hell of a lot of sense. When you're dealing with windows or displays that have a certain number of characters (80 char terminals, for instance), or programming languages that use a lot of nesting, having the visual cues of alignment far outweight the benefits of refined character recognition and easier legibility (which by the way generally only applies to long blocks of text set in a language in which you are conversant). And this is coming from a guy who generally can't stand seeing fixed-width fonts used (except in very specific circumstances, like this).</htmltext>
<tokenext>I 'm a fairly serious typography geek , and I can tell you that for something like programming , fixed-width fonts make a hell of a lot of sense .
When you 're dealing with windows or displays that have a certain number of characters ( 80 char terminals , for instance ) , or programming languages that use a lot of nesting , having the visual cues of alignment far outweight the benefits of refined character recognition and easier legibility ( which by the way generally only applies to long blocks of text set in a language in which you are conversant ) .
And this is coming from a guy who generally ca n't stand seeing fixed-width fonts used ( except in very specific circumstances , like this ) .</tokentext>
<sentencetext>I'm a fairly serious typography geek, and I can tell you that for something like programming, fixed-width fonts make a hell of a lot of sense.
When you're dealing with windows or displays that have a certain number of characters (80 char terminals, for instance), or programming languages that use a lot of nesting, having the visual cues of alignment far outweight the benefits of refined character recognition and easier legibility (which by the way generally only applies to long blocks of text set in a language in which you are conversant).
And this is coming from a guy who generally can't stand seeing fixed-width fonts used (except in very specific circumstances, like this).</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30806412</id>
	<title>Proportional/monospace irrelevant.</title>
	<author>Arimus</author>
	<datestamp>1263818100000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>As a coder I don't care about proportional/mono fonts. What I do care about is a font with clear and distinct characters, especially O0ilI({)}[]</p><p>To be honest, I'd like to bring back the &#248; for use in code.... I know its strictly a maths symbol and not a zero but it would be clearer than trying to spot a capital oh from a zero...</p></htmltext>
<tokenext>As a coder I do n't care about proportional/mono fonts .
What I do care about is a font with clear and distinct characters , especially O0ilI ( { ) } [ ] To be honest , I 'd like to bring back the   for use in code.... I know its strictly a maths symbol and not a zero but it would be clearer than trying to spot a capital oh from a zero.. .</tokentext>
<sentencetext>As a coder I don't care about proportional/mono fonts.
What I do care about is a font with clear and distinct characters, especially O0ilI({)}[]To be honest, I'd like to bring back the ø for use in code.... I know its strictly a maths symbol and not a zero but it would be clearer than trying to spot a capital oh from a zero...</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30799966</id>
	<title>Proportional fonts for programmers Math-clueless</title>
	<author>Anonymous</author>
	<datestamp>1263757080000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>1</modscore>
	<htmltext><p>For people who's "computer science" job consists in doing Object-Relational mapping, sure...  Proportional may do the job.</p><p>But for anyone working with "true" algorithms, forget proportional.  You need a fixed-width font (and, no, the elastic tab, let alone the pathetic non-existent editors support, ain't cutting it enough).</p><p>Show me a dynamic programming algo that doesn't look sucky with a proportional font.  Show me some FSM implementation that doesn't look sucky with proportional font.</p><p>When someone argues that "proportional font are better for programming" you can safely consider the guy mostly clueless about algorithms, big-O perfs, etc.</p><p>They like their proportional font as much as they think nothing is bogus with someMethodThatDoesSomethingNTimes(...).  Sure, with such long method names you better 'gain back' every pixel you can by using proportional fonts.</p><p>In other words: give him the monkey ORM type job but don't count on him to know about when to use, say, a skip list.</p><p>(btw this post touch-typed on a blind IBM Model M, monospaced font of choise being a modified 'proggy font')</p><p>
&nbsp; &nbsp; &nbsp;</p></htmltext>
<tokenext>For people who 's " computer science " job consists in doing Object-Relational mapping , sure... Proportional may do the job.But for anyone working with " true " algorithms , forget proportional .
You need a fixed-width font ( and , no , the elastic tab , let alone the pathetic non-existent editors support , ai n't cutting it enough ) .Show me a dynamic programming algo that does n't look sucky with a proportional font .
Show me some FSM implementation that does n't look sucky with proportional font.When someone argues that " proportional font are better for programming " you can safely consider the guy mostly clueless about algorithms , big-O perfs , etc.They like their proportional font as much as they think nothing is bogus with someMethodThatDoesSomethingNTimes ( ... ) .
Sure , with such long method names you better 'gain back ' every pixel you can by using proportional fonts.In other words : give him the monkey ORM type job but do n't count on him to know about when to use , say , a skip list .
( btw this post touch-typed on a blind IBM Model M , monospaced font of choise being a modified 'proggy font ' )      </tokentext>
<sentencetext>For people who's "computer science" job consists in doing Object-Relational mapping, sure...  Proportional may do the job.But for anyone working with "true" algorithms, forget proportional.
You need a fixed-width font (and, no, the elastic tab, let alone the pathetic non-existent editors support, ain't cutting it enough).Show me a dynamic programming algo that doesn't look sucky with a proportional font.
Show me some FSM implementation that doesn't look sucky with proportional font.When someone argues that "proportional font are better for programming" you can safely consider the guy mostly clueless about algorithms, big-O perfs, etc.They like their proportional font as much as they think nothing is bogus with someMethodThatDoesSomethingNTimes(...).
Sure, with such long method names you better 'gain back' every pixel you can by using proportional fonts.In other words: give him the monkey ORM type job but don't count on him to know about when to use, say, a skip list.
(btw this post touch-typed on a blind IBM Model M, monospaced font of choise being a modified 'proggy font')
     </sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30798620</id>
	<title>Re:Proportional fonts are better to read</title>
	<author>jbengt</author>
	<datestamp>1263746040000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>As long as tabs are fixed, and delimiters like spaces, periods, and commas are sufficiently large, I prefer proportional fonts while coding.  Then again, I don't code 8 hours a day, so YMMV.</p><p>Maybe it's my old eyes, but I find serif fonts <em>much</em> harder to read than sans-serif.</p><p>Also, I find "ALL CAPS" at least as easy to read than "normal text".  That could be because I work in the construction industry where drawings  use all caps.  (In fact, until several years after we switched from hand drafting to CAD, I found it very difficult to write in anything but all caps.)  Also, we use 1/2 size printouts of drawings all the time, and from that experience I can say that all caps is <em>much</em> easier to read than mixed case when the font is small.  On the other hand, mixed case probably shows more information when reproductions are blurred or partially obscured.</p><p>Finally, to respond to other threads, I can't stand white on black text.  It hurts my eyes terribly and is way too hard to read.  I won't usually stay on a website with small, serif, white-on-black text, as it's not worth the effort.</p></htmltext>
<tokenext>As long as tabs are fixed , and delimiters like spaces , periods , and commas are sufficiently large , I prefer proportional fonts while coding .
Then again , I do n't code 8 hours a day , so YMMV.Maybe it 's my old eyes , but I find serif fonts much harder to read than sans-serif.Also , I find " ALL CAPS " at least as easy to read than " normal text " .
That could be because I work in the construction industry where drawings use all caps .
( In fact , until several years after we switched from hand drafting to CAD , I found it very difficult to write in anything but all caps .
) Also , we use 1/2 size printouts of drawings all the time , and from that experience I can say that all caps is much easier to read than mixed case when the font is small .
On the other hand , mixed case probably shows more information when reproductions are blurred or partially obscured.Finally , to respond to other threads , I ca n't stand white on black text .
It hurts my eyes terribly and is way too hard to read .
I wo n't usually stay on a website with small , serif , white-on-black text , as it 's not worth the effort .</tokentext>
<sentencetext>As long as tabs are fixed, and delimiters like spaces, periods, and commas are sufficiently large, I prefer proportional fonts while coding.
Then again, I don't code 8 hours a day, so YMMV.Maybe it's my old eyes, but I find serif fonts much harder to read than sans-serif.Also, I find "ALL CAPS" at least as easy to read than "normal text".
That could be because I work in the construction industry where drawings  use all caps.
(In fact, until several years after we switched from hand drafting to CAD, I found it very difficult to write in anything but all caps.
)  Also, we use 1/2 size printouts of drawings all the time, and from that experience I can say that all caps is much easier to read than mixed case when the font is small.
On the other hand, mixed case probably shows more information when reproductions are blurred or partially obscured.Finally, to respond to other threads, I can't stand white on black text.
It hurts my eyes terribly and is way too hard to read.
I won't usually stay on a website with small, serif, white-on-black text, as it's not worth the effort.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797634</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797550</id>
	<title>prophecy</title>
	<author>Anonymous</author>
	<datestamp>1263735780000</datestamp>
	<modclass>Funny</modclass>
	<modscore>4</modscore>
	<htmltext><p>this guys just trying to ensure the prophecy of the helvetica wars is fulfilled</p></htmltext>
<tokenext>this guys just trying to ensure the prophecy of the helvetica wars is fulfilled</tokentext>
<sentencetext>this guys just trying to ensure the prophecy of the helvetica wars is fulfilled</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30800398</id>
	<title>Re:fixed</title>
	<author>Thantik</author>
	<datestamp>1263760860000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>As far as I'm aware the reason X11 doesn't do subpixel smoothing is because it's patented my Microsoft.  Someone please tell me if I'm wrong; it is merely what I recall reading on<nobr> <wbr></nobr>/. at some earlier point in time.</p></htmltext>
<tokenext>As far as I 'm aware the reason X11 does n't do subpixel smoothing is because it 's patented my Microsoft .
Someone please tell me if I 'm wrong ; it is merely what I recall reading on / .
at some earlier point in time .</tokentext>
<sentencetext>As far as I'm aware the reason X11 doesn't do subpixel smoothing is because it's patented my Microsoft.
Someone please tell me if I'm wrong; it is merely what I recall reading on /.
at some earlier point in time.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797696</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30801788</id>
	<title>Re:inilliibiliti</title>
	<author>lennier</author>
	<datestamp>1263726720000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>"as well as a CRM114-vintage machine designed to stretch your saccade, by forcing you to read words in a revealed window with a progressive speed ratchet."</p><p>I read that as "CRM114 vintage machine gun"</p><p>Now that would be aggressive testing...</p></htmltext>
<tokenext>" as well as a CRM114-vintage machine designed to stretch your saccade , by forcing you to read words in a revealed window with a progressive speed ratchet .
" I read that as " CRM114 vintage machine gun " Now that would be aggressive testing.. .</tokentext>
<sentencetext>"as well as a CRM114-vintage machine designed to stretch your saccade, by forcing you to read words in a revealed window with a progressive speed ratchet.
"I read that as "CRM114 vintage machine gun"Now that would be aggressive testing...</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30798478</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30801098</id>
	<title>Programmer Fonts</title>
	<author>fm6</author>
	<datestamp>1263722220000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Consolas is a good font, but I don't like the distinction between 1 and l.  I think that incurs more cognitive overhead than it should. This kind of unobvious distinction is an issue with most fonts. For a long time I used Andale Mono (despite hearing fontophiles sneer at its esthetics) because the letter l is radically different from the digit 1. Then I discovered Vera Sans Mono, which has a similar letter l, and also has a narrow underbar, so that sequential underbars don't form a continuous line. I've often wondered why so many "programmer friendly" fonts overlook this issue: continuous underlining makes it easy to get the wrong number of underlines in things like <tt>\_\_WEIRDCONSTANT</tt>.</p><p>Incidentally, both these fonts are designed by major font foundries, but are available for free. Andale Mono used to be part of Microsoft's free "core web font" program; that's long ended, but nobody seems to care about all the copies available on the web. The Vera Sans family appears to be Bitstream's donation to GNOME.</p><p>This discussion caused me to google "programmer fonts". Some interesting discoveries:</p><ul> <li>There are a huge number of fonts designed by programmers who can't quite live with any existing font. Since scalable font design is a specialized skill, these are almost always simple bitmap fonts.</li><li> <a href="http://www.dafont.com/monofur.font" title="dafont.com">Monofur</a> [dafont.com] is a very clever design. Which is precisely why I will never use it &mdash; too distracting.</li><li> <a href="http://www.arcavia.com/Software/ProgFont/" title="arcavia.com">This font</a> [arcavia.com] is designed around the assumption that "We need to re-engineer the alphabet so that it will be clear at extremely small sizes." I think this guy needs to get out more.</li></ul></htmltext>
<tokenext>Consolas is a good font , but I do n't like the distinction between 1 and l. I think that incurs more cognitive overhead than it should .
This kind of unobvious distinction is an issue with most fonts .
For a long time I used Andale Mono ( despite hearing fontophiles sneer at its esthetics ) because the letter l is radically different from the digit 1 .
Then I discovered Vera Sans Mono , which has a similar letter l , and also has a narrow underbar , so that sequential underbars do n't form a continuous line .
I 've often wondered why so many " programmer friendly " fonts overlook this issue : continuous underlining makes it easy to get the wrong number of underlines in things like \ _ \ _WEIRDCONSTANT.Incidentally , both these fonts are designed by major font foundries , but are available for free .
Andale Mono used to be part of Microsoft 's free " core web font " program ; that 's long ended , but nobody seems to care about all the copies available on the web .
The Vera Sans family appears to be Bitstream 's donation to GNOME.This discussion caused me to google " programmer fonts " .
Some interesting discoveries : There are a huge number of fonts designed by programmers who ca n't quite live with any existing font .
Since scalable font design is a specialized skill , these are almost always simple bitmap fonts .
Monofur [ dafont.com ] is a very clever design .
Which is precisely why I will never use it    too distracting .
This font [ arcavia.com ] is designed around the assumption that " We need to re-engineer the alphabet so that it will be clear at extremely small sizes .
" I think this guy needs to get out more .</tokentext>
<sentencetext>Consolas is a good font, but I don't like the distinction between 1 and l.  I think that incurs more cognitive overhead than it should.
This kind of unobvious distinction is an issue with most fonts.
For a long time I used Andale Mono (despite hearing fontophiles sneer at its esthetics) because the letter l is radically different from the digit 1.
Then I discovered Vera Sans Mono, which has a similar letter l, and also has a narrow underbar, so that sequential underbars don't form a continuous line.
I've often wondered why so many "programmer friendly" fonts overlook this issue: continuous underlining makes it easy to get the wrong number of underlines in things like \_\_WEIRDCONSTANT.Incidentally, both these fonts are designed by major font foundries, but are available for free.
Andale Mono used to be part of Microsoft's free "core web font" program; that's long ended, but nobody seems to care about all the copies available on the web.
The Vera Sans family appears to be Bitstream's donation to GNOME.This discussion caused me to google "programmer fonts".
Some interesting discoveries: There are a huge number of fonts designed by programmers who can't quite live with any existing font.
Since scalable font design is a specialized skill, these are almost always simple bitmap fonts.
Monofur [dafont.com] is a very clever design.
Which is precisely why I will never use it — too distracting.
This font [arcavia.com] is designed around the assumption that "We need to re-engineer the alphabet so that it will be clear at extremely small sizes.
" I think this guy needs to get out more.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797584</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30806954</id>
	<title>ProFont (monospaced)</title>
	<author>V for Vendetta</author>
	<datestamp>1263823380000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>
<a href="http://www.tobias-jung.de/seekingprofont/" title="tobias-jung.de" rel="nofollow">ProFont</a> [tobias-jung.de] is my font of choice for programming needs. It's small and it provides a "0" (zero) which is good to distinguish from a capital "O". Extra goodie for german speaking coders: it includes umlauts.
</p></htmltext>
<tokenext>ProFont [ tobias-jung.de ] is my font of choice for programming needs .
It 's small and it provides a " 0 " ( zero ) which is good to distinguish from a capital " O " .
Extra goodie for german speaking coders : it includes umlauts .</tokentext>
<sentencetext>
ProFont [tobias-jung.de] is my font of choice for programming needs.
It's small and it provides a "0" (zero) which is good to distinguish from a capital "O".
Extra goodie for german speaking coders: it includes umlauts.
</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30801866</id>
	<title>I use mono for everything</title>
	<author>mirix</author>
	<datestamp>1263727260000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><tt>I pretend I'm reading the printout from a selectric.</tt></htmltext>
<tokenext>I pretend I 'm reading the printout from a selectric .</tokentext>
<sentencetext>I pretend I'm reading the printout from a selectric.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30800324</id>
	<title>Re:Stroustrup chose proportional-width</title>
	<author>Anonymous</author>
	<datestamp>1263760080000</datestamp>
	<modclass>Funny</modclass>
	<modscore>2</modscore>
	<htmltext><p>You are taking the C++ inventor's advice for legibility of code ?</p></htmltext>
<tokenext>You are taking the C + + inventor 's advice for legibility of code ?</tokentext>
<sentencetext>You are taking the C++ inventor's advice for legibility of code ?</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797874</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30798058</id>
	<title>Re:Proportional fonts are better to read</title>
	<author>jez9999</author>
	<datestamp>1263741420000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I guess it just goes to show it's all down to personal taste, because I have to say I disagree with most of that.  OK, reading all caps is tougher, but apart from that I find a good fixed-width font just as easy to read as a good proportional font, and serif/sans- just as easy as each other to read; if anything, sans- looks a bit nicer when printed.</p></htmltext>
<tokenext>I guess it just goes to show it 's all down to personal taste , because I have to say I disagree with most of that .
OK , reading all caps is tougher , but apart from that I find a good fixed-width font just as easy to read as a good proportional font , and serif/sans- just as easy as each other to read ; if anything , sans- looks a bit nicer when printed .</tokentext>
<sentencetext>I guess it just goes to show it's all down to personal taste, because I have to say I disagree with most of that.
OK, reading all caps is tougher, but apart from that I find a good fixed-width font just as easy to read as a good proportional font, and serif/sans- just as easy as each other to read; if anything, sans- looks a bit nicer when printed.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797634</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30799020</id>
	<title>Re:Do the studies apply?</title>
	<author>chapstercni</author>
	<datestamp>1263749400000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Nice font. I just installed it and tested. I got the modified one linked at the bottom, with the straight single/double quotes.</p></htmltext>
<tokenext>Nice font .
I just installed it and tested .
I got the modified one linked at the bottom , with the straight single/double quotes .</tokentext>
<sentencetext>Nice font.
I just installed it and tested.
I got the modified one linked at the bottom, with the straight single/double quotes.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797630</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797618</id>
	<title>ProFont ruled the day</title>
	<author>Anonymous</author>
	<datestamp>1263736560000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>3</modscore>
	<htmltext>This was my favorite for a long time. No question about 1 and l, or 0 and O; which may have been identical in the default Monaco. Also<nobr> <wbr></nobr>:,;, and , where slightly bold so one could easily see statement ends. <br>

But for whatever reason, big screens, better fonts, syntax highlighting. ProFont was quite readable in 9pt; important on small screens.

I might try to put ProFont in Eclipse tomorrow.
ProFont can be found here:
<a href="http://www.tobias-jung.de/seekingprofont/index.html" title="tobias-jung.de">http://www.tobias-jung.de/seekingprofont/index.html</a> [tobias-jung.de]</htmltext>
<tokenext>This was my favorite for a long time .
No question about 1 and l , or 0 and O ; which may have been identical in the default Monaco .
Also : , ; , and , where slightly bold so one could easily see statement ends .
But for whatever reason , big screens , better fonts , syntax highlighting .
ProFont was quite readable in 9pt ; important on small screens .
I might try to put ProFont in Eclipse tomorrow .
ProFont can be found here : http : //www.tobias-jung.de/seekingprofont/index.html [ tobias-jung.de ]</tokentext>
<sentencetext>This was my favorite for a long time.
No question about 1 and l, or 0 and O; which may have been identical in the default Monaco.
Also :,;, and , where slightly bold so one could easily see statement ends.
But for whatever reason, big screens, better fonts, syntax highlighting.
ProFont was quite readable in 9pt; important on small screens.
I might try to put ProFont in Eclipse tomorrow.
ProFont can be found here:
http://www.tobias-jung.de/seekingprofont/index.html [tobias-jung.de]</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30852682</id>
	<title>Re:Overrated</title>
	<author>Anonymous</author>
	<datestamp>1264072560000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Late late late to the thread, but I just had to say I hope I never have to work with your code. You obviously never work with anyone else (or are stupendously arrogant). Why on earth should I have to reconfigure my tab width on a per-file basis? Otherwise, tabs or no, the alignment is right out the window. Further, what about when someone else works on the code, and starts interspersing spaces with your tabs?</p><p>If tabs are used in code at all, they must be on 8 character centers. In reality, though, tabs in code are EVIL, and those who promulgate that hated practice should be shunned. How on earth did this get modded "insightful?"</p></htmltext>
<tokenext>Late late late to the thread , but I just had to say I hope I never have to work with your code .
You obviously never work with anyone else ( or are stupendously arrogant ) .
Why on earth should I have to reconfigure my tab width on a per-file basis ?
Otherwise , tabs or no , the alignment is right out the window .
Further , what about when someone else works on the code , and starts interspersing spaces with your tabs ? If tabs are used in code at all , they must be on 8 character centers .
In reality , though , tabs in code are EVIL , and those who promulgate that hated practice should be shunned .
How on earth did this get modded " insightful ?
"</tokentext>
<sentencetext>Late late late to the thread, but I just had to say I hope I never have to work with your code.
You obviously never work with anyone else (or are stupendously arrogant).
Why on earth should I have to reconfigure my tab width on a per-file basis?
Otherwise, tabs or no, the alignment is right out the window.
Further, what about when someone else works on the code, and starts interspersing spaces with your tabs?If tabs are used in code at all, they must be on 8 character centers.
In reality, though, tabs in code are EVIL, and those who promulgate that hated practice should be shunned.
How on earth did this get modded "insightful?
"</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30799306</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30824758</id>
	<title>Any vi-like editor supports this?</title>
	<author>Anonymous</author>
	<datestamp>1263897000000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Does anybody know of an editor with vi-like keybindings supporting proportional fonts?<br>Vim, the obvious candidate (or MacVim over here) does not and will not support proportional fonts, due to its internal design.<br>I'm all for programming with proportional fonts, but I will not give up my modal editing.</p></htmltext>
<tokenext>Does anybody know of an editor with vi-like keybindings supporting proportional fonts ? Vim , the obvious candidate ( or MacVim over here ) does not and will not support proportional fonts , due to its internal design.I 'm all for programming with proportional fonts , but I will not give up my modal editing .</tokentext>
<sentencetext>Does anybody know of an editor with vi-like keybindings supporting proportional fonts?Vim, the obvious candidate (or MacVim over here) does not and will not support proportional fonts, due to its internal design.I'm all for programming with proportional fonts, but I will not give up my modal editing.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797776</id>
	<title>assembly</title>
	<author>Skapare</author>
	<datestamp>1263738840000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>But try it in assembly language.</p></htmltext>
<tokenext>But try it in assembly language .</tokentext>
<sentencetext>But try it in assembly language.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30800264</id>
	<title>Re:Overrated</title>
	<author>Anonymous</author>
	<datestamp>1263759540000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p><div class="quote"><p>Any programmer who<nobr> <wbr></nobr>... puts tabs into his code is obviously not a good rational thinker....</p></div><p>Congratulations, you win the award for least obvious "obvious" proposition.</p></div>
	</htmltext>
<tokenext>Any programmer who ... puts tabs into his code is obviously not a good rational thinker....Congratulations , you win the award for least obvious " obvious " proposition .</tokentext>
<sentencetext>Any programmer who ... puts tabs into his code is obviously not a good rational thinker....Congratulations, you win the award for least obvious "obvious" proposition.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30799686</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30799384</id>
	<title>Re:Overrated</title>
	<author>denmarkw00t</author>
	<datestamp>1263752640000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I just wanted to see for myself:</p><p>this-&gt;posx=0;<br>this-&gt;posy=0;<br>tis-&gt;ttl=40;<br>this-&gt;source="";</p><p>After hitting Preview, I'm not sure your argument holds up as well as I thought. I understand as a programmer that being able to quickly spot where certain keywords are shorter/longer than they should be is important, but viewing the above in proportional font makes it obvious that just about any font will show when you mistype, especially in a situation like that where you're using the same keyword (this) to start each line.</p></htmltext>
<tokenext>I just wanted to see for myself : this- &gt; posx = 0 ; this- &gt; posy = 0 ; t is- &gt; ttl = 40 ; this- &gt; source = " " ; After hitting Preview , I 'm not sure your argument holds up as well as I thought .
I understand as a programmer that being able to quickly spot where certain keywords are shorter/longer than they should be is important , but viewing the above in proportional font makes it obvious that just about any font will show when you mistype , especially in a situation like that where you 're using the same keyword ( this ) to start each line .</tokentext>
<sentencetext>I just wanted to see for myself:this-&gt;posx=0;this-&gt;posy=0;tis-&gt;ttl=40;this-&gt;source="";After hitting Preview, I'm not sure your argument holds up as well as I thought.
I understand as a programmer that being able to quickly spot where certain keywords are shorter/longer than they should be is important, but viewing the above in proportional font makes it obvious that just about any font will show when you mistype, especially in a situation like that where you're using the same keyword (this) to start each line.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30798366</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30802584</id>
	<title>I'm suprised not to see this mentioned</title>
	<author>jdougan</author>
	<datestamp>1263732600000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>2</modscore>
	<htmltext><p>A data point in this discussion is that it is traditional for Smallltalk implementations to use proportional fonts as the default for code editing. I've been programming in Smalltalk since 1985 and I think I've only encountered a couple of people who changed the default to anything but a proportional font. Some Smalltalks allow for rich text code, and then you'll see ASCII art done as a monospaced font section embedded in a larger proportional method or comment. But I've not seen it that often. Maybe I've led a sheltered life.</p><p>Another data point is the book "Human Factors and Typography for More Readable Programs" by Ronald Baecker and Aaron Marcus ( <a href="http://www.amazon.com/Human-Factors-Typography-Readable-Programs/dp/0201107457" title="amazon.com" rel="nofollow">http://www.amazon.com/Human-Factors-Typography-Readable-Programs/dp/0201107457</a> [amazon.com]  ). In this outstanding volume they build a framework for understanding program legibility and an approach to formatting C programs that utilizes this framework. Recommended to anyone who wants to have a better understanding of the issues in this area.</p></htmltext>
<tokenext>A data point in this discussion is that it is traditional for Smallltalk implementations to use proportional fonts as the default for code editing .
I 've been programming in Smalltalk since 1985 and I think I 've only encountered a couple of people who changed the default to anything but a proportional font .
Some Smalltalks allow for rich text code , and then you 'll see ASCII art done as a monospaced font section embedded in a larger proportional method or comment .
But I 've not seen it that often .
Maybe I 've led a sheltered life.Another data point is the book " Human Factors and Typography for More Readable Programs " by Ronald Baecker and Aaron Marcus ( http : //www.amazon.com/Human-Factors-Typography-Readable-Programs/dp/0201107457 [ amazon.com ] ) .
In this outstanding volume they build a framework for understanding program legibility and an approach to formatting C programs that utilizes this framework .
Recommended to anyone who wants to have a better understanding of the issues in this area .</tokentext>
<sentencetext>A data point in this discussion is that it is traditional for Smallltalk implementations to use proportional fonts as the default for code editing.
I've been programming in Smalltalk since 1985 and I think I've only encountered a couple of people who changed the default to anything but a proportional font.
Some Smalltalks allow for rich text code, and then you'll see ASCII art done as a monospaced font section embedded in a larger proportional method or comment.
But I've not seen it that often.
Maybe I've led a sheltered life.Another data point is the book "Human Factors and Typography for More Readable Programs" by Ronald Baecker and Aaron Marcus ( http://www.amazon.com/Human-Factors-Typography-Readable-Programs/dp/0201107457 [amazon.com]  ).
In this outstanding volume they build a framework for understanding program legibility and an approach to formatting C programs that utilizes this framework.
Recommended to anyone who wants to have a better understanding of the issues in this area.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30800288</id>
	<title>Re:fixed</title>
	<author>digsbo</author>
	<datestamp>1263759840000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>
You couldn't be more right!
</p><p>
I found it so superb in my Unix hacking, I found one for Windows and now use this font in VisualStudio and other Windows apps (i.e. Notepad), as it is WORLDS better than Microsoft's default of courier.  Any place I don't have this font, I will spend a lot of time to try and get it.  The clarity and information density is superior to even the Proggy font family.
</p><p>
One frustration has been getting this to work under Cygwin/X; for some reason there seems to be some font magic w/ Gtk apps that try to scale or use a font differently than specified, so when I start gvim under Cygwin/X I get a short, uglier version of 6x13 (perhaps it's 6x12?  Ever see this?  Solution?</p></htmltext>
<tokenext>You could n't be more right !
I found it so superb in my Unix hacking , I found one for Windows and now use this font in VisualStudio and other Windows apps ( i.e .
Notepad ) , as it is WORLDS better than Microsoft 's default of courier .
Any place I do n't have this font , I will spend a lot of time to try and get it .
The clarity and information density is superior to even the Proggy font family .
One frustration has been getting this to work under Cygwin/X ; for some reason there seems to be some font magic w/ Gtk apps that try to scale or use a font differently than specified , so when I start gvim under Cygwin/X I get a short , uglier version of 6x13 ( perhaps it 's 6x12 ?
Ever see this ?
Solution ?</tokentext>
<sentencetext>
You couldn't be more right!
I found it so superb in my Unix hacking, I found one for Windows and now use this font in VisualStudio and other Windows apps (i.e.
Notepad), as it is WORLDS better than Microsoft's default of courier.
Any place I don't have this font, I will spend a lot of time to try and get it.
The clarity and information density is superior to even the Proggy font family.
One frustration has been getting this to work under Cygwin/X; for some reason there seems to be some font magic w/ Gtk apps that try to scale or use a font differently than specified, so when I start gvim under Cygwin/X I get a short, uglier version of 6x13 (perhaps it's 6x12?
Ever see this?
Solution?</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797606</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797680</id>
	<title>I wonder ..</title>
	<author>Anonymous</author>
	<datestamp>1263737400000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>2</modscore>
	<htmltext><p>How do you align comments, etc.? How do you do visual block selection? What if you want to add a small ASCII drawing to a comment?</p><p>The disatvantages seem overwhelming to me, and I find good monospace fonts (Deja Vu Sans Mono, Inconsolata,<nobr> <wbr></nobr>...) easy enough to read. Also, some editors (e.g. gvim) will scale proportional fonts to make them look monospaced (and really ugly).</p></htmltext>
<tokenext>How do you align comments , etc. ?
How do you do visual block selection ?
What if you want to add a small ASCII drawing to a comment ? The disatvantages seem overwhelming to me , and I find good monospace fonts ( Deja Vu Sans Mono , Inconsolata , ... ) easy enough to read .
Also , some editors ( e.g .
gvim ) will scale proportional fonts to make them look monospaced ( and really ugly ) .</tokentext>
<sentencetext>How do you align comments, etc.?
How do you do visual block selection?
What if you want to add a small ASCII drawing to a comment?The disatvantages seem overwhelming to me, and I find good monospace fonts (Deja Vu Sans Mono, Inconsolata, ...) easy enough to read.
Also, some editors (e.g.
gvim) will scale proportional fonts to make them look monospaced (and really ugly).</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797556</id>
	<title>Pffffft...</title>
	<author>Anonymous</author>
	<datestamp>1263735840000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>... yeah right!</p></htmltext>
<tokenext>... yeah right !</tokentext>
<sentencetext>... yeah right!</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30806632</id>
	<title>A little knowledge is a dangerous thing</title>
	<author>tgv</author>
	<datestamp>1263820800000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>How come people citing studies from the early '80s on reading normal text become experts on programming ergonomy? There are several reasons to distrust this.</p><p>1. Experience: normal readers (which were the subjects in these studies) mainly have experience in reading proportional fonts. Programmers on the other hand...<br>2. Context: ease of reading depends on the context, as does almost every cognitive task. Normal text does not look like code at all, so cannot be expected to be representative.<br>3. Importance: reading speed is not that important in programming. Reading speed for code must be way below that of normal text (which is 3 to 5 words per second for easy text, plus or minus a bit). I cannot imagine a programmer reading and understanding at that speed, so reading is not the bottleneck.<br>4. Errors: proportional fonts make it easier to misinterpret: 1, l or i? rn or m? 0 or O?</p><p>So, unless someone comes up with a relevant study, this should be discarded. And relevant doesn't mean speed alone.</p><p>Yes, I am a programmer and, yes, I do have a PhD and postdoc in psycholinguistics.</p></htmltext>
<tokenext>How come people citing studies from the early '80s on reading normal text become experts on programming ergonomy ?
There are several reasons to distrust this.1 .
Experience : normal readers ( which were the subjects in these studies ) mainly have experience in reading proportional fonts .
Programmers on the other hand...2 .
Context : ease of reading depends on the context , as does almost every cognitive task .
Normal text does not look like code at all , so can not be expected to be representative.3 .
Importance : reading speed is not that important in programming .
Reading speed for code must be way below that of normal text ( which is 3 to 5 words per second for easy text , plus or minus a bit ) .
I can not imagine a programmer reading and understanding at that speed , so reading is not the bottleneck.4 .
Errors : proportional fonts make it easier to misinterpret : 1 , l or i ?
rn or m ?
0 or O ? So , unless someone comes up with a relevant study , this should be discarded .
And relevant does n't mean speed alone.Yes , I am a programmer and , yes , I do have a PhD and postdoc in psycholinguistics .</tokentext>
<sentencetext>How come people citing studies from the early '80s on reading normal text become experts on programming ergonomy?
There are several reasons to distrust this.1.
Experience: normal readers (which were the subjects in these studies) mainly have experience in reading proportional fonts.
Programmers on the other hand...2.
Context: ease of reading depends on the context, as does almost every cognitive task.
Normal text does not look like code at all, so cannot be expected to be representative.3.
Importance: reading speed is not that important in programming.
Reading speed for code must be way below that of normal text (which is 3 to 5 words per second for easy text, plus or minus a bit).
I cannot imagine a programmer reading and understanding at that speed, so reading is not the bottleneck.4.
Errors: proportional fonts make it easier to misinterpret: 1, l or i?
rn or m?
0 or O?So, unless someone comes up with a relevant study, this should be discarded.
And relevant doesn't mean speed alone.Yes, I am a programmer and, yes, I do have a PhD and postdoc in psycholinguistics.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30802974</id>
	<title>Elastic Tabs aren't an easy fix</title>
	<author>kaladorn</author>
	<datestamp>1263735720000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I like the look of proportional fonts. But if you go for elastic tabstops, everyone using your code (you, your boss, your co-workers, the company you might be developing the code for which might not be yours, maybe co-workers on other teams too that might need to spelunk the code) all have to be using editors capable of using these elastic tab stops.</p><p>If they aren't, and the number of tabs inserted was different or if someone mixes spaces and tabs, it'll look like hell if they're using a different-width or different-kerning font (including fixed width).</p><p>And yes, some of you say 'too bad for them'. Except of course that quite a few of them may be higher on the corporate food chain than you are and/or perfectly willing to make your life miserable until you conform to a standard.</p><p>If everyone moved to Elastic Tabstops, and all the tools did, I'd love that.</p><p>Unrelately, my favourite programming fixed width font is: Andale Mono (check it out)</p></htmltext>
<tokenext>I like the look of proportional fonts .
But if you go for elastic tabstops , everyone using your code ( you , your boss , your co-workers , the company you might be developing the code for which might not be yours , maybe co-workers on other teams too that might need to spelunk the code ) all have to be using editors capable of using these elastic tab stops.If they are n't , and the number of tabs inserted was different or if someone mixes spaces and tabs , it 'll look like hell if they 're using a different-width or different-kerning font ( including fixed width ) .And yes , some of you say 'too bad for them' .
Except of course that quite a few of them may be higher on the corporate food chain than you are and/or perfectly willing to make your life miserable until you conform to a standard.If everyone moved to Elastic Tabstops , and all the tools did , I 'd love that.Unrelately , my favourite programming fixed width font is : Andale Mono ( check it out )</tokentext>
<sentencetext>I like the look of proportional fonts.
But if you go for elastic tabstops, everyone using your code (you, your boss, your co-workers, the company you might be developing the code for which might not be yours, maybe co-workers on other teams too that might need to spelunk the code) all have to be using editors capable of using these elastic tab stops.If they aren't, and the number of tabs inserted was different or if someone mixes spaces and tabs, it'll look like hell if they're using a different-width or different-kerning font (including fixed width).And yes, some of you say 'too bad for them'.
Except of course that quite a few of them may be higher on the corporate food chain than you are and/or perfectly willing to make your life miserable until you conform to a standard.If everyone moved to Elastic Tabstops, and all the tools did, I'd love that.Unrelately, my favourite programming fixed width font is: Andale Mono (check it out)</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30798022</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797824</id>
	<title>But what about all the programmers ...</title>
	<author>Skapare</author>
	<datestamp>1263739380000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>... out there, regardless of the coding language, who are developing and writing their code on those old punch card systems<nobr> <wbr></nobr>... you insensitive clod!</p></htmltext>
<tokenext>... out there , regardless of the coding language , who are developing and writing their code on those old punch card systems ... you insensitive clod !</tokentext>
<sentencetext>... out there, regardless of the coding language, who are developing and writing their code on those old punch card systems ... you insensitive clod!</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30799088</id>
	<title>Things That Are Similar Should Look Similar.</title>
	<author>Anonymous</author>
	<datestamp>1263750060000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>No pro-programmer I know prefers a variable-width typeface to code. On first thought, a fixed-width typeface makes it easy to align statements and numbers. But one can get all that, and more, using tab-stops. So, on second thought, why do we prefer fixed-width typefaces to code? Well, in coding, things that are similar should look similar.<nobr> <wbr></nobr>...</p><p>From: http://codeblab.com/2009/12/fixed-width-coding/</p></htmltext>
<tokenext>No pro-programmer I know prefers a variable-width typeface to code .
On first thought , a fixed-width typeface makes it easy to align statements and numbers .
But one can get all that , and more , using tab-stops .
So , on second thought , why do we prefer fixed-width typefaces to code ?
Well , in coding , things that are similar should look similar .
...From : http : //codeblab.com/2009/12/fixed-width-coding/</tokentext>
<sentencetext>No pro-programmer I know prefers a variable-width typeface to code.
On first thought, a fixed-width typeface makes it easy to align statements and numbers.
But one can get all that, and more, using tab-stops.
So, on second thought, why do we prefer fixed-width typefaces to code?
Well, in coding, things that are similar should look similar.
...From: http://codeblab.com/2009/12/fixed-width-coding/</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30801996</id>
	<title>Re:Overrated</title>
	<author>moosesocks</author>
	<datestamp>1263728280000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>You were writing adware for Buick in the 90s using a Mac?</p><p>So many things about this just don't add up.  Do explain more...</p></htmltext>
<tokenext>You were writing adware for Buick in the 90s using a Mac ? So many things about this just do n't add up .
Do explain more.. .</tokentext>
<sentencetext>You were writing adware for Buick in the 90s using a Mac?So many things about this just don't add up.
Do explain more...</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30798296</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30805654</id>
	<title>Re:prophecy</title>
	<author>Krupuk</author>
	<datestamp>1263807660000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>No! Not Helvetica!

Don't they know the dangers of a possible <a href="http://www.youtube.com/watch?v=aY7XH2ulTEU" title="youtube.com" rel="nofollow">Helvetica Scenario</a> [youtube.com]?</htmltext>
<tokenext>No !
Not Helvetica !
Do n't they know the dangers of a possible Helvetica Scenario [ youtube.com ] ?</tokentext>
<sentencetext>No!
Not Helvetica!
Don't they know the dangers of a possible Helvetica Scenario [youtube.com]?</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797550</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30799866</id>
	<title>Re:visual cues</title>
	<author>Haeleth</author>
	<datestamp>1263756360000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><blockquote><div><p>Computer languages are not as forgiving, and, also, lacking redundancy, far denser.</p></div></blockquote><p>I'm guessing you're not familiar with Java or XML, then.</p></div>
	</htmltext>
<tokenext>Computer languages are not as forgiving , and , also , lacking redundancy , far denser.I 'm guessing you 're not familiar with Java or XML , then .</tokentext>
<sentencetext>Computer languages are not as forgiving, and, also, lacking redundancy, far denser.I'm guessing you're not familiar with Java or XML, then.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797816</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30800592</id>
	<title>Anti-aliased and fixed</title>
	<author>AlexWillisson</author>
	<datestamp>1263719160000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>DejaVu Sans Mono on emacs23 here, been using it since I first compiled emacs23!

Non-fixed width fonts just don't work for me when I'm programming. I don't like the random look they have in my programs.</htmltext>
<tokenext>DejaVu Sans Mono on emacs23 here , been using it since I first compiled emacs23 !
Non-fixed width fonts just do n't work for me when I 'm programming .
I do n't like the random look they have in my programs .</tokentext>
<sentencetext>DejaVu Sans Mono on emacs23 here, been using it since I first compiled emacs23!
Non-fixed width fonts just don't work for me when I'm programming.
I don't like the random look they have in my programs.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797810</id>
	<title>Helvetica?  Are you nuts?</title>
	<author>Anonymous</author>
	<datestamp>1263739140000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Because the distinction of 0 versus O, I versus l, and l versus | don't matter in programming languages.</p><p>I'm sorry, but that font choice is a disaster waiting to happen.</p></htmltext>
<tokenext>Because the distinction of 0 versus O , I versus l , and l versus | do n't matter in programming languages.I 'm sorry , but that font choice is a disaster waiting to happen .</tokentext>
<sentencetext>Because the distinction of 0 versus O, I versus l, and l versus | don't matter in programming languages.I'm sorry, but that font choice is a disaster waiting to happen.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30798712</id>
	<title>Re:fixed</title>
	<author>Col. Bloodnok</author>
	<datestamp>1263746760000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>-*-lucidatypewriter-medium-*-*-*-12-*-*-*-*-*-*-*</p><p>Nicer.</p></htmltext>
<tokenext>- * -lucidatypewriter-medium- * - * - * -12- * - * - * - * - * - * - * Nicer .</tokentext>
<sentencetext>-*-lucidatypewriter-medium-*-*-*-12-*-*-*-*-*-*-*Nicer.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797606</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30822864</id>
	<title>Re:Examples...</title>
	<author>clone53421</author>
	<datestamp>1263931440000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>Fixed width Monaco 10pt, which comes out too small and kind of blurry to me.</p></div><p>That&rsquo;s because the blog resized the image. The image isn&rsquo;t blurry at all; click the resized image to view it. (I&rsquo;d link it, but it seems that there is some sort of hotlink-prevention being used.)</p><p>From the looks of his images, the font sizes were probably different to achieve the same line spacing (i.e. to get the same number of lines of code to fit in the same vertical screen space). Not every font is the same size as every other font at the same point size.</p></div>
	</htmltext>
<tokenext>Fixed width Monaco 10pt , which comes out too small and kind of blurry to me.That    s because the blog resized the image .
The image isn    t blurry at all ; click the resized image to view it .
( I    d link it , but it seems that there is some sort of hotlink-prevention being used .
) From the looks of his images , the font sizes were probably different to achieve the same line spacing ( i.e .
to get the same number of lines of code to fit in the same vertical screen space ) .
Not every font is the same size as every other font at the same point size .</tokentext>
<sentencetext>Fixed width Monaco 10pt, which comes out too small and kind of blurry to me.That’s because the blog resized the image.
The image isn’t blurry at all; click the resized image to view it.
(I’d link it, but it seems that there is some sort of hotlink-prevention being used.
)From the looks of his images, the font sizes were probably different to achieve the same line spacing (i.e.
to get the same number of lines of code to fit in the same vertical screen space).
Not every font is the same size as every other font at the same point size.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797740</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30802912</id>
	<title>Re:Overrated</title>
	<author>coaxial</author>
	<datestamp>1263735180000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Yet another "solution" to the Gordian Knot.  This fails because:</p><p>(x) Everyone needs to hit tab and not space<br>(x) Everyone's editor must be configured to insert tabs rather than spaces when the tab key is pressed<br>(x) Uses an editor specific trick<br>(x) Has been tried before: \_\_settable\_tab\_stops\_\_</p><p>People are a lazy and dumb.  In 50 years of programming, neither of these conditions have ever been met anywhere.</p><p>What makes this idea any different?</p></htmltext>
<tokenext>Yet another " solution " to the Gordian Knot .
This fails because : ( x ) Everyone needs to hit tab and not space ( x ) Everyone 's editor must be configured to insert tabs rather than spaces when the tab key is pressed ( x ) Uses an editor specific trick ( x ) Has been tried before : \ _ \ _settable \ _tab \ _stops \ _ \ _People are a lazy and dumb .
In 50 years of programming , neither of these conditions have ever been met anywhere.What makes this idea any different ?</tokentext>
<sentencetext>Yet another "solution" to the Gordian Knot.
This fails because:(x) Everyone needs to hit tab and not space(x) Everyone's editor must be configured to insert tabs rather than spaces when the tab key is pressed(x) Uses an editor specific trick(x) Has been tried before: \_\_settable\_tab\_stops\_\_People are a lazy and dumb.
In 50 years of programming, neither of these conditions have ever been met anywhere.What makes this idea any different?</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30798022</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30798908</id>
	<title>top-10-programming-fonts</title>
	<author>hey</author>
	<datestamp>1263748560000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>4</modscore>
	<htmltext><p>This was on reddit today<br><a href="http://hivelogic.com/articles/top-10-programming-fonts" title="hivelogic.com">http://hivelogic.com/articles/top-10-programming-fonts</a> [hivelogic.com]</p></htmltext>
<tokenext>This was on reddit todayhttp : //hivelogic.com/articles/top-10-programming-fonts [ hivelogic.com ]</tokentext>
<sentencetext>This was on reddit todayhttp://hivelogic.com/articles/top-10-programming-fonts [hivelogic.com]</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30798116</id>
	<title>Whitespace</title>
	<author>jdevivre</author>
	<datestamp>1263741960000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext>I believe proper use of whitespace in programming makes enormous improvements in recognition.  Spaces in proportional fonts are often thinner and less contrasting.  That alone may reduce proportional effectiveness, more readable or not.  One would have to form a habit of using two space characters and more tabs.</htmltext>
<tokenext>I believe proper use of whitespace in programming makes enormous improvements in recognition .
Spaces in proportional fonts are often thinner and less contrasting .
That alone may reduce proportional effectiveness , more readable or not .
One would have to form a habit of using two space characters and more tabs .</tokentext>
<sentencetext>I believe proper use of whitespace in programming makes enormous improvements in recognition.
Spaces in proportional fonts are often thinner and less contrasting.
That alone may reduce proportional effectiveness, more readable or not.
One would have to form a habit of using two space characters and more tabs.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30798102</id>
	<title>Call me crazy...</title>
	<author>DiSKiLLeR</author>
	<datestamp>1263741900000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Call me crazy.... but I started doing this a couple years ago.</p><p>I can't remember what font it was now; I was programming under linux using eclipse.</p><p>But I really enjoyed switching away from a fixed width font...</p></htmltext>
<tokenext>Call me crazy.... but I started doing this a couple years ago.I ca n't remember what font it was now ; I was programming under linux using eclipse.But I really enjoyed switching away from a fixed width font.. .</tokentext>
<sentencetext>Call me crazy.... but I started doing this a couple years ago.I can't remember what font it was now; I was programming under linux using eclipse.But I really enjoyed switching away from a fixed width font...</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30798486</id>
	<title>RTF!</title>
	<author>Megane</author>
	<datestamp>1263745080000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>1</modscore>
	<htmltext><p>I see a great need for compilers to support an RTF-to-plaintext filter on their front ends. Then you can program in whatever font you want, and it will look essentially the same when viewed by anybody else.
</p><p>But there should also be a standard on what you should and shouldn't do. For instance, it should not be kosher to specify text sizes or colors. Text sizes give you the "HTML mail" problem (where Outlook e-mails show up in a tiny font because the HTML hard-codes the font point size). Text colors screw things up for the "white on black" crowd, and also allow for "white on white" hiding of evil code.
</p><p>It doesn't have to specifically be RTF. RTF would really be overdoing it. Whatever format would be chosen should take well to merging in svn or whatever. Maybe something equivalent to Unix's #! line could specify the font. You don't want to specify the size, because that should be up to the individual reader, and I suppose the font should really be a matter of choice too. And most of the time, 8-space tab stops work well in proportional fonts.
</p><p>So you just need... um, you just need people to use 8-space hard-tab text, not use any tabs after the first non-tab character in a line, and... oh, I guess you can just use plain text after all, as long as everyone switch to hard tabs. Oops, never mind.</p></htmltext>
<tokenext>I see a great need for compilers to support an RTF-to-plaintext filter on their front ends .
Then you can program in whatever font you want , and it will look essentially the same when viewed by anybody else .
But there should also be a standard on what you should and should n't do .
For instance , it should not be kosher to specify text sizes or colors .
Text sizes give you the " HTML mail " problem ( where Outlook e-mails show up in a tiny font because the HTML hard-codes the font point size ) .
Text colors screw things up for the " white on black " crowd , and also allow for " white on white " hiding of evil code .
It does n't have to specifically be RTF .
RTF would really be overdoing it .
Whatever format would be chosen should take well to merging in svn or whatever .
Maybe something equivalent to Unix 's # !
line could specify the font .
You do n't want to specify the size , because that should be up to the individual reader , and I suppose the font should really be a matter of choice too .
And most of the time , 8-space tab stops work well in proportional fonts .
So you just need... um , you just need people to use 8-space hard-tab text , not use any tabs after the first non-tab character in a line , and... oh , I guess you can just use plain text after all , as long as everyone switch to hard tabs .
Oops , never mind .</tokentext>
<sentencetext>I see a great need for compilers to support an RTF-to-plaintext filter on their front ends.
Then you can program in whatever font you want, and it will look essentially the same when viewed by anybody else.
But there should also be a standard on what you should and shouldn't do.
For instance, it should not be kosher to specify text sizes or colors.
Text sizes give you the "HTML mail" problem (where Outlook e-mails show up in a tiny font because the HTML hard-codes the font point size).
Text colors screw things up for the "white on black" crowd, and also allow for "white on white" hiding of evil code.
It doesn't have to specifically be RTF.
RTF would really be overdoing it.
Whatever format would be chosen should take well to merging in svn or whatever.
Maybe something equivalent to Unix's #!
line could specify the font.
You don't want to specify the size, because that should be up to the individual reader, and I suppose the font should really be a matter of choice too.
And most of the time, 8-space tab stops work well in proportional fonts.
So you just need... um, you just need people to use 8-space hard-tab text, not use any tabs after the first non-tab character in a line, and... oh, I guess you can just use plain text after all, as long as everyone switch to hard tabs.
Oops, never mind.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30806584</id>
	<title>Re:Only if you don't use VIM</title>
	<author>RedWizzard</author>
	<datestamp>1263820260000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>This is compatible with column-area selection, and other features it supports which frankly I use nearly daily.</p></div><p>I love column-area selection and use it often as well, but virtually never for programming.</p><p><div class="quote"><p>Reasons to use them:
</p><ul>
<li>You might be able to read the contents of your code up to 14\% faster, if you don't run into the issues above...</li></ul></div><p>They also permit more readable text on a single line. That's a significant advantage for programming IMHO.</p></div>
	</htmltext>
<tokenext>This is compatible with column-area selection , and other features it supports which frankly I use nearly daily.I love column-area selection and use it often as well , but virtually never for programming.Reasons to use them : You might be able to read the contents of your code up to 14 \ % faster , if you do n't run into the issues above...They also permit more readable text on a single line .
That 's a significant advantage for programming IMHO .</tokentext>
<sentencetext>This is compatible with column-area selection, and other features it supports which frankly I use nearly daily.I love column-area selection and use it often as well, but virtually never for programming.Reasons to use them:

You might be able to read the contents of your code up to 14\% faster, if you don't run into the issues above...They also permit more readable text on a single line.
That's a significant advantage for programming IMHO.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797946</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797958</id>
	<title>Re:I wonder ..</title>
	<author>gbjbaanb</author>
	<datestamp>1263740460000</datestamp>
	<modclass>Funny</modclass>
	<modscore>2</modscore>
	<htmltext><p><i>What if you want to add a small ASCII drawing to a comment?</i></p><p>You mean like this:</p><blockquote><div><p> <tt>requirements<br>specification ---&gt; o<br>
&nbsp; <br>original coder --&gt; O<br>
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; -|-<br>
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; / \</tt></p></div> </blockquote></div>
	</htmltext>
<tokenext>What if you want to add a small ASCII drawing to a comment ? You mean like this : requirementsspecification --- &gt; o   original coder -- &gt; O                   - | -                   / \</tokentext>
<sentencetext>What if you want to add a small ASCII drawing to a comment?You mean like this: requirementsspecification ---&gt; o
  original coder --&gt; O
                  -|-
                  / \ 
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797680</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30801070</id>
	<title>Top10 Programming Fonts</title>
	<author>Fnord666</author>
	<datestamp>1263722040000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>HiveLogic did an <a href="http://hivelogic.com/articles/top-10-programming-fonts" title="hivelogic.com">article</a> [hivelogic.com] last year about the top 10 programming fonts.  Inconsolata was number 1, but I believe all of the top 10 were monospaced fonts.</htmltext>
<tokenext>HiveLogic did an article [ hivelogic.com ] last year about the top 10 programming fonts .
Inconsolata was number 1 , but I believe all of the top 10 were monospaced fonts .</tokentext>
<sentencetext>HiveLogic did an article [hivelogic.com] last year about the top 10 programming fonts.
Inconsolata was number 1, but I believe all of the top 10 were monospaced fonts.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30800232</id>
	<title>Re:ProFont ruled the day</title>
	<author>omfgnosis</author>
	<datestamp>1263759180000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I use ProFont 9px on my 1680x1050 display and it's fantastic. I get 70 lines of code on screen, between the chrome.</p></htmltext>
<tokenext>I use ProFont 9px on my 1680x1050 display and it 's fantastic .
I get 70 lines of code on screen , between the chrome .</tokentext>
<sentencetext>I use ProFont 9px on my 1680x1050 display and it's fantastic.
I get 70 lines of code on screen, between the chrome.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797618</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30800394</id>
	<title>Re:Overrated</title>
	<author>Surt</author>
	<datestamp>1263760800000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>If your ide didn't point out that error with a red underline or some such you are working in the wrong environment, or naming your variables very very poorly.</p></htmltext>
<tokenext>If your ide did n't point out that error with a red underline or some such you are working in the wrong environment , or naming your variables very very poorly .</tokentext>
<sentencetext>If your ide didn't point out that error with a red underline or some such you are working in the wrong environment, or naming your variables very very poorly.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30798366</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30811780</id>
	<title>Re:Overrated</title>
	<author>metamatic</author>
	<datestamp>1263805560000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><blockquote><div><p>Differing widths of tab-stops only cause problems when people mix tabs and spaces.</p></div></blockquote><p>
Serves you right for using Python.</p></div>
	</htmltext>
<tokenext>Differing widths of tab-stops only cause problems when people mix tabs and spaces .
Serves you right for using Python .</tokentext>
<sentencetext>Differing widths of tab-stops only cause problems when people mix tabs and spaces.
Serves you right for using Python.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30800336</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797752</id>
	<title>Hahahaha!</title>
	<author>Anonymous</author>
	<datestamp>1263738660000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Programming with proportional fonts, this guy is funny!<br>Yes, let us use Microsoft Word or OpenOffice for programming!</p></htmltext>
<tokenext>Programming with proportional fonts , this guy is funny ! Yes , let us use Microsoft Word or OpenOffice for programming !</tokentext>
<sentencetext>Programming with proportional fonts, this guy is funny!Yes, let us use Microsoft Word or OpenOffice for programming!</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797584</id>
	<title>Consolas</title>
	<author>Anonymous</author>
	<datestamp>1263736320000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>5</modscore>
	<htmltext>Microsoft's Consolas with properly tweaked ClearType has been my personal favorite since its release.  Another huge improvement to my code screen is changing the background color to a light grey - still not a dark color scheme, but much less glaring than pure white.</htmltext>
<tokenext>Microsoft 's Consolas with properly tweaked ClearType has been my personal favorite since its release .
Another huge improvement to my code screen is changing the background color to a light grey - still not a dark color scheme , but much less glaring than pure white .</tokentext>
<sentencetext>Microsoft's Consolas with properly tweaked ClearType has been my personal favorite since its release.
Another huge improvement to my code screen is changing the background color to a light grey - still not a dark color scheme, but much less glaring than pure white.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30808002</id>
	<title>Roll Your Own</title>
	<author>codewarren</author>
	<datestamp>1263830520000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I'm a variable font user.  I used Tahoma for the readability at lower resolutions, but ended up modifying it using a font editor to fix a few annoyances.  I increased the width of the space, made all numbers, and punctuation characters the same width, as well as a few other minor tweaks (like adding a dot to the middle of the zero and adjusting the look of some characters like greater/less than signs)</p></htmltext>
<tokenext>I 'm a variable font user .
I used Tahoma for the readability at lower resolutions , but ended up modifying it using a font editor to fix a few annoyances .
I increased the width of the space , made all numbers , and punctuation characters the same width , as well as a few other minor tweaks ( like adding a dot to the middle of the zero and adjusting the look of some characters like greater/less than signs )</tokentext>
<sentencetext>I'm a variable font user.
I used Tahoma for the readability at lower resolutions, but ended up modifying it using a font editor to fix a few annoyances.
I increased the width of the space, made all numbers, and punctuation characters the same width, as well as a few other minor tweaks (like adding a dot to the middle of the zero and adjusting the look of some characters like greater/less than signs)</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30814900</id>
	<title>Re:Overrated</title>
	<author>shutdown -p now</author>
	<datestamp>1263822840000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>Nonsense. Differing widths of tab-stops only cause problems when people mix tabs and spaces.</p></div><p>This only holds true when considering line indentation. This is absolutely not true when using whitespace to align comments, or function arguments, etc. For example, consider this:</p><blockquote><div><p> <tt>void<br>foo(a\_very\_long\_type\_name\_1 a,<br>
&nbsp; &nbsp; a\_very\_long\_type\_name\_2 b,<br>
&nbsp; &nbsp; a\_very\_long\_type\_name\_2 c);<br>
&nbsp; <br>foo(a\_very\_long\_expression\_1,<br>
&nbsp; &nbsp; a\_very\_long\_expression\_2,<br>
&nbsp; &nbsp; a\_very\_long\_expression\_3);</tt></p></div> </blockquote><p>This is a perfectly valid coding style, but it requires spaces (and proportional fonts) to align the identifiers properly. If you use tabs, then identifiers will only align for one particular tab width, and no other.</p><p>You may say that the above code style is improper, and that may be arguable for C-style languages, but there are some other languages out there for which it is a de facto standard; to wit, Haskell (and also F#):</p><blockquote><div><p> <tt>let y = a*b<br>
&nbsp; &nbsp; f x = (x+y)/y<br>in f c + f d</tt></p></div> </blockquote><p>It is precisely why "elastic tabs" were invented in the first place. But, as GP rightly notes, unless and until all editors uniformly interpret tabs in a single way, tabs have no place in the source code, period.</p></div>
	</htmltext>
<tokenext>Nonsense .
Differing widths of tab-stops only cause problems when people mix tabs and spaces.This only holds true when considering line indentation .
This is absolutely not true when using whitespace to align comments , or function arguments , etc .
For example , consider this : voidfoo ( a \ _very \ _long \ _type \ _name \ _1 a ,     a \ _very \ _long \ _type \ _name \ _2 b ,     a \ _very \ _long \ _type \ _name \ _2 c ) ;   foo ( a \ _very \ _long \ _expression \ _1 ,     a \ _very \ _long \ _expression \ _2 ,     a \ _very \ _long \ _expression \ _3 ) ; This is a perfectly valid coding style , but it requires spaces ( and proportional fonts ) to align the identifiers properly .
If you use tabs , then identifiers will only align for one particular tab width , and no other.You may say that the above code style is improper , and that may be arguable for C-style languages , but there are some other languages out there for which it is a de facto standard ; to wit , Haskell ( and also F # ) : let y = a * b     f x = ( x + y ) /yin f c + f d It is precisely why " elastic tabs " were invented in the first place .
But , as GP rightly notes , unless and until all editors uniformly interpret tabs in a single way , tabs have no place in the source code , period .</tokentext>
<sentencetext>Nonsense.
Differing widths of tab-stops only cause problems when people mix tabs and spaces.This only holds true when considering line indentation.
This is absolutely not true when using whitespace to align comments, or function arguments, etc.
For example, consider this: voidfoo(a\_very\_long\_type\_name\_1 a,
    a\_very\_long\_type\_name\_2 b,
    a\_very\_long\_type\_name\_2 c);
  foo(a\_very\_long\_expression\_1,
    a\_very\_long\_expression\_2,
    a\_very\_long\_expression\_3); This is a perfectly valid coding style, but it requires spaces (and proportional fonts) to align the identifiers properly.
If you use tabs, then identifiers will only align for one particular tab width, and no other.You may say that the above code style is improper, and that may be arguable for C-style languages, but there are some other languages out there for which it is a de facto standard; to wit, Haskell (and also F#): let y = a*b
    f x = (x+y)/yin f c + f d It is precisely why "elastic tabs" were invented in the first place.
But, as GP rightly notes, unless and until all editors uniformly interpret tabs in a single way, tabs have no place in the source code, period.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30800336</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797662</id>
	<title>Monospaced is the only way to go</title>
	<author>neuroklinik</author>
	<datestamp>1263737160000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>2</modscore>
	<htmltext><p>Reading code is not like reading prose. It's more like reading poetry, where how the text elements are spaced and aligned can say a lot about the author's intended meaning. If I'm reading a book, I definitely want it typeset with a proportional typeface. Code, on the other hand, is MUCH more legible when set monospaced.</p></htmltext>
<tokenext>Reading code is not like reading prose .
It 's more like reading poetry , where how the text elements are spaced and aligned can say a lot about the author 's intended meaning .
If I 'm reading a book , I definitely want it typeset with a proportional typeface .
Code , on the other hand , is MUCH more legible when set monospaced .</tokentext>
<sentencetext>Reading code is not like reading prose.
It's more like reading poetry, where how the text elements are spaced and aligned can say a lot about the author's intended meaning.
If I'm reading a book, I definitely want it typeset with a proportional typeface.
Code, on the other hand, is MUCH more legible when set monospaced.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30798678</id>
	<title>Studies on people that are *used* to them?</title>
	<author>Hurricane78</author>
	<datestamp>1263746400000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>2</modscore>
	<htmltext><p>If they did those studies with $JoeRandom, they are meaningless for programmers, who see fixed-width fonts all day long.</p><p>Oh, actually I just came here to say: &ldquo;Those who do not learn from history, are doomed to repeat it.&rdquo; (In that some new generation thinks they have to test it for truth all over. Which can make sense... If you build up to what is already known, and not just ignore everything.)</p></htmltext>
<tokenext>If they did those studies with $ JoeRandom , they are meaningless for programmers , who see fixed-width fonts all day long.Oh , actually I just came here to say :    Those who do not learn from history , are doomed to repeat it.    ( In that some new generation thinks they have to test it for truth all over .
Which can make sense... If you build up to what is already known , and not just ignore everything .
)</tokentext>
<sentencetext>If they did those studies with $JoeRandom, they are meaningless for programmers, who see fixed-width fonts all day long.Oh, actually I just came here to say: “Those who do not learn from history, are doomed to repeat it.” (In that some new generation thinks they have to test it for truth all over.
Which can make sense... If you build up to what is already known, and not just ignore everything.
)</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30798516</id>
	<title>Re:Python...</title>
	<author>Anonymous</author>
	<datestamp>1263745260000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Defend it from what? In most programs intended to edit text, indentation is at least going to show up when using a proportional font.</p><p>And the big criticism isn't that python code is indented to show the structure (most coding styles recommend indenting code in a way that shows the structure), the big criticism is that the parser uses the indentation to determine the structure.</p></htmltext>
<tokenext>Defend it from what ?
In most programs intended to edit text , indentation is at least going to show up when using a proportional font.And the big criticism is n't that python code is indented to show the structure ( most coding styles recommend indenting code in a way that shows the structure ) , the big criticism is that the parser uses the indentation to determine the structure .</tokentext>
<sentencetext>Defend it from what?
In most programs intended to edit text, indentation is at least going to show up when using a proportional font.And the big criticism isn't that python code is indented to show the structure (most coding styles recommend indenting code in a way that shows the structure), the big criticism is that the parser uses the indentation to determine the structure.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797822</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30800938</id>
	<title>Irrelevant</title>
	<author>jeroen94704</author>
	<datestamp>1263721260000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>I'm sure proportional fonts can be read faster than monospace fonts, but this is absolutely and completely irrelevant. In no way, shape or form is reading speed something that slows down developers.</htmltext>
<tokenext>I 'm sure proportional fonts can be read faster than monospace fonts , but this is absolutely and completely irrelevant .
In no way , shape or form is reading speed something that slows down developers .</tokentext>
<sentencetext>I'm sure proportional fonts can be read faster than monospace fonts, but this is absolutely and completely irrelevant.
In no way, shape or form is reading speed something that slows down developers.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797808</id>
	<title>reads faster?</title>
	<author>Anonymous</author>
	<datestamp>1263739140000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>4</modscore>
	<htmltext>Are we really in such a hurry when reading code? I'm under the impression that fixed fonts allow us, when we parse code, to see the different elements more clearly because their size is determined by the number of characters. But that's just an intuition. Anyone else has the same feeling?</htmltext>
<tokenext>Are we really in such a hurry when reading code ?
I 'm under the impression that fixed fonts allow us , when we parse code , to see the different elements more clearly because their size is determined by the number of characters .
But that 's just an intuition .
Anyone else has the same feeling ?</tokentext>
<sentencetext>Are we really in such a hurry when reading code?
I'm under the impression that fixed fonts allow us, when we parse code, to see the different elements more clearly because their size is determined by the number of characters.
But that's just an intuition.
Anyone else has the same feeling?</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30798316</id>
	<title>Re:I wonder ..</title>
	<author>Jugalator</author>
	<datestamp>1263743940000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p> How do you align comments, etc.?</p> </div><p>By tabbing to the configured ruler position in our IDE of course!</p><p>Heh, but seriously, is there a development IDE that support that thing?</p></div>
	</htmltext>
<tokenext>How do you align comments , etc. ?
By tabbing to the configured ruler position in our IDE of course ! Heh , but seriously , is there a development IDE that support that thing ?</tokentext>
<sentencetext> How do you align comments, etc.?
By tabbing to the configured ruler position in our IDE of course!Heh, but seriously, is there a development IDE that support that thing?
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797680</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30798068</id>
	<title>Re:I wonder ..</title>
	<author>Anonymous</author>
	<datestamp>1263741480000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Simply use tabs to align things. I've been using Verdana for years. The letters are also smaller, so more fit on the screen. It also works with ClearType nicely, part of the reason it's readable in small size.<br>And I can confirm it's better to work with it. You often look for things in the code and it makes spotting them easier.<br>Kornel</p></htmltext>
<tokenext>Simply use tabs to align things .
I 've been using Verdana for years .
The letters are also smaller , so more fit on the screen .
It also works with ClearType nicely , part of the reason it 's readable in small size.And I can confirm it 's better to work with it .
You often look for things in the code and it makes spotting them easier.Kornel</tokentext>
<sentencetext>Simply use tabs to align things.
I've been using Verdana for years.
The letters are also smaller, so more fit on the screen.
It also works with ClearType nicely, part of the reason it's readable in small size.And I can confirm it's better to work with it.
You often look for things in the code and it makes spotting them easier.Kornel</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797680</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30799030</id>
	<title>Re:Overrated</title>
	<author>Anonymous</author>
	<datestamp>1263749460000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Seconded.</p></htmltext>
<tokenext>Seconded .</tokentext>
<sentencetext>Seconded.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797572</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30799224</id>
	<title>RPG</title>
	<author>inicom</author>
	<datestamp>1263751200000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I've tried, and I just can't keep the columns straight when programming RPG with a proportional font. Anyone got any tips?</p></htmltext>
<tokenext>I 've tried , and I just ca n't keep the columns straight when programming RPG with a proportional font .
Anyone got any tips ?</tokentext>
<sentencetext>I've tried, and I just can't keep the columns straight when programming RPG with a proportional font.
Anyone got any tips?</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797862</id>
	<title>Re:Consolas</title>
	<author>gbjbaanb</author>
	<datestamp>1263739680000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>second the light grey, but I use an off-white instead. The creamy colour is still white-ish so doesn't look as nasty as grey but takes the edge off pure white. Hint: you need to take the tiniest amount off, too much and the little colour square you thought looked good will turn yellow on a large panel.</p></htmltext>
<tokenext>second the light grey , but I use an off-white instead .
The creamy colour is still white-ish so does n't look as nasty as grey but takes the edge off pure white .
Hint : you need to take the tiniest amount off , too much and the little colour square you thought looked good will turn yellow on a large panel .</tokentext>
<sentencetext>second the light grey, but I use an off-white instead.
The creamy colour is still white-ish so doesn't look as nasty as grey but takes the edge off pure white.
Hint: you need to take the tiniest amount off, too much and the little colour square you thought looked good will turn yellow on a large panel.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797584</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797590</id>
	<title>For bug-free code ...</title>
	<author>Anonymous</author>
	<datestamp>1263736320000</datestamp>
	<modclass>Funny</modclass>
	<modscore>5</modscore>
	<htmltext><p>MS Comic Sans is simply the best. My code doesn't have bugs, it has bloopers and out-takes.</p></htmltext>
<tokenext>MS Comic Sans is simply the best .
My code does n't have bugs , it has bloopers and out-takes .</tokentext>
<sentencetext>MS Comic Sans is simply the best.
My code doesn't have bugs, it has bloopers and out-takes.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30808036</id>
	<title>Re:inilliibiliti</title>
	<author>batlbot</author>
	<datestamp>1263830760000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>I have to tell you that I have no idea what half of your post means, but I found it ultimately enjoyable reading.  You cram a lot of semi-obscure-obtuse references into a minimal amount of space while still be mostly clear in your meaning.

CrapAssasin, BeerGoggles, signal density, critical brain glucose

Letters falling down the shirt had to be my favorite though....

Thanks.
I think.</htmltext>
<tokenext>I have to tell you that I have no idea what half of your post means , but I found it ultimately enjoyable reading .
You cram a lot of semi-obscure-obtuse references into a minimal amount of space while still be mostly clear in your meaning .
CrapAssasin , BeerGoggles , signal density , critical brain glucose Letters falling down the shirt had to be my favorite though... . Thanks . I think .</tokentext>
<sentencetext>I have to tell you that I have no idea what half of your post means, but I found it ultimately enjoyable reading.
You cram a lot of semi-obscure-obtuse references into a minimal amount of space while still be mostly clear in your meaning.
CrapAssasin, BeerGoggles, signal density, critical brain glucose

Letters falling down the shirt had to be my favorite though....

Thanks.
I think.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30798478</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30799248</id>
	<title>Re:Overrated</title>
	<author>Anonymous</author>
	<datestamp>1263751380000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>I prefer fixed width for alignment</p></div><p>Not to mention that a proportional font would make a Python programmer's head explode...</p></div>
	</htmltext>
<tokenext>I prefer fixed width for alignmentNot to mention that a proportional font would make a Python programmer 's head explode.. .</tokentext>
<sentencetext>I prefer fixed width for alignmentNot to mention that a proportional font would make a Python programmer's head explode...
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797572</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30798326</id>
	<title>Missing the Point</title>
	<author>Deorus</author>
	<datestamp>1263743940000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>3</modscore>
	<htmltext><p>While fixed-width might not be recommended for text, code is not exactly regular text.  In a regular essay, skipping a period or a comma is usually not an issue.  In code, however, it makes a world of difference, and therefore it doesn't make sense to use a font that may cause confusion between a pair of parentheses '()' and a zero '0', an 'I' and an 'l', a single dash '-' and two dashes '--', etc.  Fixed-width founts are a lot clearer, and clarity and usability are extremely important for me.</p></htmltext>
<tokenext>While fixed-width might not be recommended for text , code is not exactly regular text .
In a regular essay , skipping a period or a comma is usually not an issue .
In code , however , it makes a world of difference , and therefore it does n't make sense to use a font that may cause confusion between a pair of parentheses ' ( ) ' and a zero '0 ' , an 'I ' and an 'l ' , a single dash '- ' and two dashes '-- ' , etc .
Fixed-width founts are a lot clearer , and clarity and usability are extremely important for me .</tokentext>
<sentencetext>While fixed-width might not be recommended for text, code is not exactly regular text.
In a regular essay, skipping a period or a comma is usually not an issue.
In code, however, it makes a world of difference, and therefore it doesn't make sense to use a font that may cause confusion between a pair of parentheses '()' and a zero '0', an 'I' and an 'l', a single dash '-' and two dashes '--', etc.
Fixed-width founts are a lot clearer, and clarity and usability are extremely important for me.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797816</id>
	<title>visual cues</title>
	<author>pz</author>
	<datestamp>1263739260000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>4</modscore>
	<htmltext><p>Human languages have lots and lots of redundancy, such that you can often either screw up letter order, word order, or even drop entire words, and often the full meaning is clear.  Visual cues in the form of paragraphs and chapters are added to help guide the reader, but removing them would not render the text entirely incomprehensible.</p><p>Computer languages are not as forgiving, and, also, lacking redundancy, far denser.  Reading speed is irrelevant because of the bottleneck formed by reading comprehension.  Code is rarely read in novel-like linear fashion, but, much more often, flitting from one part of the text to another, navigating through visual cues.  Visual cues in the form of often richly structured layout that includes idioms not required by syntax make navigating and comprehending code possible, and removing them although would, in most languages, not change the meaning of the code, would erect a formidable barrier to comprehension.  Not using these cues to the fullest to help write clear, expressive and maintainable code is being self-indulgent and shortsighted.  Requiring that a particular, and perhaps unspecified font be used for best display, rather than the ubiquitous assumption of monospaced font, is mere vanity.</p><p>Remember, when code is written, it is meant not only to be converted into executable machine language, but also to be comprehensible and comprehended by other programmers, or future selves.  Clarity of expression is vital.</p></htmltext>
<tokenext>Human languages have lots and lots of redundancy , such that you can often either screw up letter order , word order , or even drop entire words , and often the full meaning is clear .
Visual cues in the form of paragraphs and chapters are added to help guide the reader , but removing them would not render the text entirely incomprehensible.Computer languages are not as forgiving , and , also , lacking redundancy , far denser .
Reading speed is irrelevant because of the bottleneck formed by reading comprehension .
Code is rarely read in novel-like linear fashion , but , much more often , flitting from one part of the text to another , navigating through visual cues .
Visual cues in the form of often richly structured layout that includes idioms not required by syntax make navigating and comprehending code possible , and removing them although would , in most languages , not change the meaning of the code , would erect a formidable barrier to comprehension .
Not using these cues to the fullest to help write clear , expressive and maintainable code is being self-indulgent and shortsighted .
Requiring that a particular , and perhaps unspecified font be used for best display , rather than the ubiquitous assumption of monospaced font , is mere vanity.Remember , when code is written , it is meant not only to be converted into executable machine language , but also to be comprehensible and comprehended by other programmers , or future selves .
Clarity of expression is vital .</tokentext>
<sentencetext>Human languages have lots and lots of redundancy, such that you can often either screw up letter order, word order, or even drop entire words, and often the full meaning is clear.
Visual cues in the form of paragraphs and chapters are added to help guide the reader, but removing them would not render the text entirely incomprehensible.Computer languages are not as forgiving, and, also, lacking redundancy, far denser.
Reading speed is irrelevant because of the bottleneck formed by reading comprehension.
Code is rarely read in novel-like linear fashion, but, much more often, flitting from one part of the text to another, navigating through visual cues.
Visual cues in the form of often richly structured layout that includes idioms not required by syntax make navigating and comprehending code possible, and removing them although would, in most languages, not change the meaning of the code, would erect a formidable barrier to comprehension.
Not using these cues to the fullest to help write clear, expressive and maintainable code is being self-indulgent and shortsighted.
Requiring that a particular, and perhaps unspecified font be used for best display, rather than the ubiquitous assumption of monospaced font, is mere vanity.Remember, when code is written, it is meant not only to be converted into executable machine language, but also to be comprehensible and comprehended by other programmers, or future selves.
Clarity of expression is vital.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797802</id>
	<title>Re:Monaco</title>
	<author>thogard</author>
	<datestamp>1263739140000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><i>Monaco is fixed-width &amp; good looking.</i><br>Um no... its not good looking.</p></htmltext>
<tokenext>Monaco is fixed-width &amp; good looking.Um no... its not good looking .</tokentext>
<sentencetext>Monaco is fixed-width &amp; good looking.Um no... its not good looking.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797554</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797624</id>
	<title>ascii-art</title>
	<author>kampangptlk</author>
	<datestamp>1263736620000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext>and my lines of code cannot contain ascii-art anymore</htmltext>
<tokenext>and my lines of code can not contain ascii-art anymore</tokentext>
<sentencetext>and my lines of code cannot contain ascii-art anymore</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30799554</id>
	<title>Re:Overrated</title>
	<author>Anonymous</author>
	<datestamp>1263753960000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>One thing's for sure... I wish I could type this message that I'm typing right now in a proportional font. Monospaced is horrible for non-code text. But the standard text input area for HTML is monospaced. Slashdot really needs an option for an "advanced editor".</p></div><p>HTML does not define a "standard text input" font. Blame your browser.</p></div>
	</htmltext>
<tokenext>One thing 's for sure... I wish I could type this message that I 'm typing right now in a proportional font .
Monospaced is horrible for non-code text .
But the standard text input area for HTML is monospaced .
Slashdot really needs an option for an " advanced editor " .HTML does not define a " standard text input " font .
Blame your browser .</tokentext>
<sentencetext>One thing's for sure... I wish I could type this message that I'm typing right now in a proportional font.
Monospaced is horrible for non-code text.
But the standard text input area for HTML is monospaced.
Slashdot really needs an option for an "advanced editor".HTML does not define a "standard text input" font.
Blame your browser.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30798296</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30799488</id>
	<title>Re:prophecy</title>
	<author>Anonymous</author>
	<datestamp>1263753480000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Meh. Helvetica on-screen isn't that good.</htmltext>
<tokenext>Meh .
Helvetica on-screen is n't that good .</tokentext>
<sentencetext>Meh.
Helvetica on-screen isn't that good.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797550</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30803768</id>
	<title>Re:Overrated</title>
	<author>Anonymous</author>
	<datestamp>1263742620000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>I see your not a very good programmer and raise that someone who uses spaces in the place of tabs is probably not a very good person.</p><p>Tabs are there for indentation, their width on some editor is irrelevant.</p><p>The problem some people, including the fags using proportional fonts, have is that they are writing C when they would be happier writing CSS.</p><p>Next thing you know, they start sending BMP patches.</p></htmltext>
<tokenext>I see your not a very good programmer and raise that someone who uses spaces in the place of tabs is probably not a very good person.Tabs are there for indentation , their width on some editor is irrelevant.The problem some people , including the fags using proportional fonts , have is that they are writing C when they would be happier writing CSS.Next thing you know , they start sending BMP patches .</tokentext>
<sentencetext>I see your not a very good programmer and raise that someone who uses spaces in the place of tabs is probably not a very good person.Tabs are there for indentation, their width on some editor is irrelevant.The problem some people, including the fags using proportional fonts, have is that they are writing C when they would be happier writing CSS.Next thing you know, they start sending BMP patches.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30799686</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797902</id>
	<title>Re:Consolas</title>
	<author>Anonymous</author>
	<datestamp>1263740040000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>I can't find the link right now, but I remember reading that the easiest to read (i.e. a sample group were able to read it fastest on average) font and background colours are a pale yellow for the background and a dark green for the font.</htmltext>
<tokenext>I ca n't find the link right now , but I remember reading that the easiest to read ( i.e .
a sample group were able to read it fastest on average ) font and background colours are a pale yellow for the background and a dark green for the font .</tokentext>
<sentencetext>I can't find the link right now, but I remember reading that the easiest to read (i.e.
a sample group were able to read it fastest on average) font and background colours are a pale yellow for the background and a dark green for the font.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797584</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797710</id>
	<title>Re:Monaco</title>
	<author>h4rm0ny</author>
	<datestamp>1263737820000</datestamp>
	<modclass>Funny</modclass>
	<modscore>3</modscore>
	<htmltext><br>
Still, I'd be willing to give it a try. If I knew how to get proportional fonts in vi. Anyone tell me how to add proportional fonts to a terminal in KDE 4?</htmltext>
<tokenext>Still , I 'd be willing to give it a try .
If I knew how to get proportional fonts in vi .
Anyone tell me how to add proportional fonts to a terminal in KDE 4 ?</tokentext>
<sentencetext>
Still, I'd be willing to give it a try.
If I knew how to get proportional fonts in vi.
Anyone tell me how to add proportional fonts to a terminal in KDE 4?</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797554</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30799256</id>
	<title>Inane sillyness</title>
	<author>Anonymous</author>
	<datestamp>1263751440000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>I don't care what font other people use so long as any code I'm working on reads fine in an 80 column terminal with fixed width fonts.  Just use whatever works for you and let's debate tom-ay-to vs tom-ar-to instead<nobr> <wbr></nobr>:-/</p></htmltext>
<tokenext>I do n't care what font other people use so long as any code I 'm working on reads fine in an 80 column terminal with fixed width fonts .
Just use whatever works for you and let 's debate tom-ay-to vs tom-ar-to instead : -/</tokentext>
<sentencetext>I don't care what font other people use so long as any code I'm working on reads fine in an 80 column terminal with fixed width fonts.
Just use whatever works for you and let's debate tom-ay-to vs tom-ar-to instead :-/</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797748</id>
	<title>Hard to go passed fwf</title>
	<author>dj\_super\_dude</author>
	<datestamp>1263738600000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Terminus is what I tend to use now, but I really liked Neep and Neep Alt(I think). I think it was in the jmk-bitmap packages or the like. Google would probably find them<nobr> <wbr></nobr>:)</p></htmltext>
<tokenext>Terminus is what I tend to use now , but I really liked Neep and Neep Alt ( I think ) .
I think it was in the jmk-bitmap packages or the like .
Google would probably find them : )</tokentext>
<sentencetext>Terminus is what I tend to use now, but I really liked Neep and Neep Alt(I think).
I think it was in the jmk-bitmap packages or the like.
Google would probably find them :)</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797912</id>
	<title>Yuck</title>
	<author>Anonymous</author>
	<datestamp>1263740100000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext>Use two different font sizes to prove your point: check<br>
Must use tabs in code to get columns to line up: check<br>
Use Baby's First Language instead of a real language: check<br>
<br>Another young idiot, with another idiotic attempt to make programming easier. You can create all the baby languages you want (Java, C#, VB), and come up with all the stupid tricks you want. Programming is still hard, and will remain so.</htmltext>
<tokenext>Use two different font sizes to prove your point : check Must use tabs in code to get columns to line up : check Use Baby 's First Language instead of a real language : check Another young idiot , with another idiotic attempt to make programming easier .
You can create all the baby languages you want ( Java , C # , VB ) , and come up with all the stupid tricks you want .
Programming is still hard , and will remain so .</tokentext>
<sentencetext>Use two different font sizes to prove your point: check
Must use tabs in code to get columns to line up: check
Use Baby's First Language instead of a real language: check
Another young idiot, with another idiotic attempt to make programming easier.
You can create all the baby languages you want (Java, C#, VB), and come up with all the stupid tricks you want.
Programming is still hard, and will remain so.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30801900</id>
	<title>Is Monaco available free for Windows?</title>
	<author>billstewart</author>
	<datestamp>1263727440000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Apparently it's a Macintosh font, which is why I didn't get the joke<nobr> <wbr></nobr>:-)  However, it's designed by Kris Holmes (who did Lucida), so I assume there may be some licensing or cost requirements.  Is it available for either free-as-in-speech or at least free-as-in-beer?  It's possible to download from various places around the web, but I don't know whether that's legitimate or not.</p></htmltext>
<tokenext>Apparently it 's a Macintosh font , which is why I did n't get the joke : - ) However , it 's designed by Kris Holmes ( who did Lucida ) , so I assume there may be some licensing or cost requirements .
Is it available for either free-as-in-speech or at least free-as-in-beer ?
It 's possible to download from various places around the web , but I do n't know whether that 's legitimate or not .</tokentext>
<sentencetext>Apparently it's a Macintosh font, which is why I didn't get the joke :-)  However, it's designed by Kris Holmes (who did Lucida), so I assume there may be some licensing or cost requirements.
Is it available for either free-as-in-speech or at least free-as-in-beer?
It's possible to download from various places around the web, but I don't know whether that's legitimate or not.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797554</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30798174</id>
	<title>Re:Not the bottleneck</title>
	<author>mugurel</author>
	<datestamp>1263742500000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I don't agree with you. While reading code your attention (and eye-focus) is likely to jump from one place to the other. Any extra cognitive effort that is required to visually identify the spot in the code you are looking for will make it more cumbersome to understand that code. TFA also seems to make that argument, as it observes that with a proportional font, more text fits in an `eye fixation' (without making the font smaller, and therefore harder to read), so that means less visual search.
</p><p>That said, I have to admit I use fixed-width fonts for programming<nobr> <wbr></nobr>:-)
</p></htmltext>
<tokenext>I do n't agree with you .
While reading code your attention ( and eye-focus ) is likely to jump from one place to the other .
Any extra cognitive effort that is required to visually identify the spot in the code you are looking for will make it more cumbersome to understand that code .
TFA also seems to make that argument , as it observes that with a proportional font , more text fits in an ` eye fixation ' ( without making the font smaller , and therefore harder to read ) , so that means less visual search .
That said , I have to admit I use fixed-width fonts for programming : - )</tokentext>
<sentencetext>I don't agree with you.
While reading code your attention (and eye-focus) is likely to jump from one place to the other.
Any extra cognitive effort that is required to visually identify the spot in the code you are looking for will make it more cumbersome to understand that code.
TFA also seems to make that argument, as it observes that with a proportional font, more text fits in an `eye fixation' (without making the font smaller, and therefore harder to read), so that means less visual search.
That said, I have to admit I use fixed-width fonts for programming :-)
</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797664</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797658</id>
	<title>It's probably better,</title>
	<author>Anonymous</author>
	<datestamp>1263737040000</datestamp>
	<modclass>Funny</modclass>
	<modscore>1</modscore>
	<htmltext><p>if you're programming in COBOL.</p></htmltext>
<tokenext>if you 're programming in COBOL .</tokentext>
<sentencetext>if you're programming in COBOL.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30802822</id>
	<title>Re:Overrated</title>
	<author>Anonymous</author>
	<datestamp>1263734280000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p><div class="quote"><p>Just use tabs.  If the dork who opens your text file doesn't have his tab stop set for his preferred size then he deserves to see ugly code.</p></div><p>Agreed.</p><p><div class="quote"><p>You probably use four spaces, hey?</p></div><p>That's my preferred tab width.</p><p><div class="quote"><p>I understand that other people might have different preferences.  With tabs we can all be happy.</p></div><p>MOD PARENT UP.</p></div>
	</htmltext>
<tokenext>Just use tabs .
If the dork who opens your text file does n't have his tab stop set for his preferred size then he deserves to see ugly code.Agreed.You probably use four spaces , hey ? That 's my preferred tab width.I understand that other people might have different preferences .
With tabs we can all be happy.MOD PARENT UP .</tokentext>
<sentencetext>Just use tabs.
If the dork who opens your text file doesn't have his tab stop set for his preferred size then he deserves to see ugly code.Agreed.You probably use four spaces, hey?That's my preferred tab width.I understand that other people might have different preferences.
With tabs we can all be happy.MOD PARENT UP.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30799306</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30798622</id>
	<title>Wusses.</title>
	<author>binaryseraph</author>
	<datestamp>1263746100000</datestamp>
	<modclass>Redundant</modclass>
	<modscore>0</modscore>
	<htmltext>Real men program using Wingdings.</htmltext>
<tokenext>Real men program using Wingdings .</tokentext>
<sentencetext>Real men program using Wingdings.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30799310</id>
	<title>Re:fixed</title>
	<author>Anonymous</author>
	<datestamp>1263751860000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>I actually make my programming fonts *huge* so I write better code. No more than 35 rows, no more than around 100 columns (if possible around 80 or a bit less). That keeps me from doing too long lines. Makes working with long functions awful. Makes me avoid a big number of indentation. The result is that I end<br>writing short functions that are also simple. Win.</p></htmltext>
<tokenext>I actually make my programming fonts * huge * so I write better code .
No more than 35 rows , no more than around 100 columns ( if possible around 80 or a bit less ) .
That keeps me from doing too long lines .
Makes working with long functions awful .
Makes me avoid a big number of indentation .
The result is that I endwriting short functions that are also simple .
Win .</tokentext>
<sentencetext>I actually make my programming fonts *huge* so I write better code.
No more than 35 rows, no more than around 100 columns (if possible around 80 or a bit less).
That keeps me from doing too long lines.
Makes working with long functions awful.
Makes me avoid a big number of indentation.
The result is that I endwriting short functions that are also simple.
Win.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797606</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30808746</id>
	<title>Lucida Console</title>
	<author>Fish (David Trout)</author>
	<datestamp>1263834900000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>(subject)<br><br>I'm surprised no one has mentioned it.</htmltext>
<tokenext>( subject ) I 'm surprised no one has mentioned it .</tokentext>
<sentencetext>(subject)I'm surprised no one has mentioned it.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30798862</id>
	<title>Re:Stroustrup chose proportional-width</title>
	<author>Anonymous</author>
	<datestamp>1263748140000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>I'd like to see the IDE let you intersperse math-like notation (or at least comments), Mathematica-style.<br>It might not add much if you're doing database programming all day, but it seems like it could make math-intense/scientific code more readable.</p></htmltext>
<tokenext>I 'd like to see the IDE let you intersperse math-like notation ( or at least comments ) , Mathematica-style.It might not add much if you 're doing database programming all day , but it seems like it could make math-intense/scientific code more readable .</tokentext>
<sentencetext>I'd like to see the IDE let you intersperse math-like notation (or at least comments), Mathematica-style.It might not add much if you're doing database programming all day, but it seems like it could make math-intense/scientific code more readable.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797874</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30799344</id>
	<title>Re:Overrated</title>
	<author>Anonymous</author>
	<datestamp>1263752160000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>In this specific case I don't think monospace font makes a difference? this is the same word in all the four lines anyway...

this-&gt;posx=0;<br>
this-&gt;posy=0;<br>
tis-&gt;ttl=40;<br>
this-&gt;source=""; <br>

<br>
I am not quickly dismissing your point, but just saying that you need a better example.</htmltext>
<tokenext>In this specific case I do n't think monospace font makes a difference ?
this is the same word in all the four lines anyway.. . this- &gt; posx = 0 ; this- &gt; posy = 0 ; t is- &gt; ttl = 40 ; this- &gt; source = " " ; I am not quickly dismissing your point , but just saying that you need a better example .</tokentext>
<sentencetext>In this specific case I don't think monospace font makes a difference?
this is the same word in all the four lines anyway...

this-&gt;posx=0;
this-&gt;posy=0;
tis-&gt;ttl=40;
this-&gt;source=""; 


I am not quickly dismissing your point, but just saying that you need a better example.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30798366</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30815040</id>
	<title>Re:Stroustrup chose proportional-width</title>
	<author>shutdown -p now</author>
	<datestamp>1263823920000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>All code in Stroustrup's "The C++ Programming Language" is presented in a proportional-width font: "At first glance, this presentation style will seem 'unnatural' to programmers accustomed to seeing code in constant-width fonts. However, proportional-width fonts are generally regarded as better than constant-width fonts for presentation of text. Using a proportional-width font also allows me to present code with fewer illogical line breaks. Furthermore, my experiments show that most people find the new style more readable after a short while."</p></div><p>.</p><p>Well, my experiment (trying to read the damn book, that is) showed that I get a headache from looking at a pageful of code presented in proportional-width italic font. And pretty much everyone else in the industry (gladly) uses monospace fonts, so Stroustroup is the odd one there.</p><p>One thing I hate though, is Courier. For the sake of all that is holy, please, stop using that crap in print. If I want to read something that looks like it was typed on a typewriter, I'll look up scans of CompSci papers from 60s and 70s. But this here is the 21st century, and we have  beautiful monospace fonts such as Consolas, Lucida Typewriter (both Sans and Serif varieties), and Monaco. Use them!</p></div>
	</htmltext>
<tokenext>All code in Stroustrup 's " The C + + Programming Language " is presented in a proportional-width font : " At first glance , this presentation style will seem 'unnatural ' to programmers accustomed to seeing code in constant-width fonts .
However , proportional-width fonts are generally regarded as better than constant-width fonts for presentation of text .
Using a proportional-width font also allows me to present code with fewer illogical line breaks .
Furthermore , my experiments show that most people find the new style more readable after a short while .
" .Well , my experiment ( trying to read the damn book , that is ) showed that I get a headache from looking at a pageful of code presented in proportional-width italic font .
And pretty much everyone else in the industry ( gladly ) uses monospace fonts , so Stroustroup is the odd one there.One thing I hate though , is Courier .
For the sake of all that is holy , please , stop using that crap in print .
If I want to read something that looks like it was typed on a typewriter , I 'll look up scans of CompSci papers from 60s and 70s .
But this here is the 21st century , and we have beautiful monospace fonts such as Consolas , Lucida Typewriter ( both Sans and Serif varieties ) , and Monaco .
Use them !</tokentext>
<sentencetext>All code in Stroustrup's "The C++ Programming Language" is presented in a proportional-width font: "At first glance, this presentation style will seem 'unnatural' to programmers accustomed to seeing code in constant-width fonts.
However, proportional-width fonts are generally regarded as better than constant-width fonts for presentation of text.
Using a proportional-width font also allows me to present code with fewer illogical line breaks.
Furthermore, my experiments show that most people find the new style more readable after a short while.
".Well, my experiment (trying to read the damn book, that is) showed that I get a headache from looking at a pageful of code presented in proportional-width italic font.
And pretty much everyone else in the industry (gladly) uses monospace fonts, so Stroustroup is the odd one there.One thing I hate though, is Courier.
For the sake of all that is holy, please, stop using that crap in print.
If I want to read something that looks like it was typed on a typewriter, I'll look up scans of CompSci papers from 60s and 70s.
But this here is the 21st century, and we have  beautiful monospace fonts such as Consolas, Lucida Typewriter (both Sans and Serif varieties), and Monaco.
Use them!
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797874</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797858</id>
	<title>Re:Consolas</title>
	<author>MoeDrippins</author>
	<datestamp>1263739680000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>2</modscore>
	<htmltext><p>I do much the same.   I waffle between light grey and "wheat"* for the background, but never, ever white.</p><p>* wheat: <a href="http://en.wikipedia.org/wiki/Wheat\_(color)" title="wikipedia.org">http://en.wikipedia.org/wiki/Wheat\_(color)</a> [wikipedia.org]</p></htmltext>
<tokenext>I do much the same .
I waffle between light grey and " wheat " * for the background , but never , ever white .
* wheat : http : //en.wikipedia.org/wiki/Wheat \ _ ( color ) [ wikipedia.org ]</tokentext>
<sentencetext>I do much the same.
I waffle between light grey and "wheat"* for the background, but never, ever white.
* wheat: http://en.wikipedia.org/wiki/Wheat\_(color) [wikipedia.org]</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797584</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30800646</id>
	<title>You're doing it wrong.</title>
	<author>Anonymous</author>
	<datestamp>1263719460000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Stop trying to program with *any* fonts.  Get the glyphs from some sort of system-wide font handler so the users can change them, and design your modal dialogs and menues such that they can accommodate the changes, including <em>size</em> changes.</p><p>Depending on fixed-size system fonts was fine back in the mid 80s, when you were lucky have a display a full 640 dots wide.  It's the 10s, now.  People's screens and eyes are all kinds of wonderful permutations of each other.  Let us specify our own sizes.</p></htmltext>
<tokenext>Stop trying to program with * any * fonts .
Get the glyphs from some sort of system-wide font handler so the users can change them , and design your modal dialogs and menues such that they can accommodate the changes , including size changes.Depending on fixed-size system fonts was fine back in the mid 80s , when you were lucky have a display a full 640 dots wide .
It 's the 10s , now .
People 's screens and eyes are all kinds of wonderful permutations of each other .
Let us specify our own sizes .</tokentext>
<sentencetext>Stop trying to program with *any* fonts.
Get the glyphs from some sort of system-wide font handler so the users can change them, and design your modal dialogs and menues such that they can accommodate the changes, including size changes.Depending on fixed-size system fonts was fine back in the mid 80s, when you were lucky have a display a full 640 dots wide.
It's the 10s, now.
People's screens and eyes are all kinds of wonderful permutations of each other.
Let us specify our own sizes.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797844</id>
	<title>Small apples vs big oranges</title>
	<author>gaspyy</author>
	<datestamp>1263739560000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>The "article" is stupid and ill-informed.<br>The author compared a Monaco at 10pt with Helvetica at 12pt and concludes Helvetica is easier to read.</p><p>I could do a similar test with Helvetica at 7pt and Arial at 12pt and conclude that Arial is better!</p><p>In programming, readability is determined by different factors than for literature. Word-pictures are less important since you basically have to deal with a lot of made-up words (variable and function names) but what's really important is to eliminate any room for misinterpretation, e.g. I vs l or " vs '' or O vs 0</p><p>Hands down, my font of choice for programming is Consolas, followed by Inconsolata.</p></htmltext>
<tokenext>The " article " is stupid and ill-informed.The author compared a Monaco at 10pt with Helvetica at 12pt and concludes Helvetica is easier to read.I could do a similar test with Helvetica at 7pt and Arial at 12pt and conclude that Arial is better ! In programming , readability is determined by different factors than for literature .
Word-pictures are less important since you basically have to deal with a lot of made-up words ( variable and function names ) but what 's really important is to eliminate any room for misinterpretation , e.g .
I vs l or " vs ' ' or O vs 0Hands down , my font of choice for programming is Consolas , followed by Inconsolata .</tokentext>
<sentencetext>The "article" is stupid and ill-informed.The author compared a Monaco at 10pt with Helvetica at 12pt and concludes Helvetica is easier to read.I could do a similar test with Helvetica at 7pt and Arial at 12pt and conclude that Arial is better!In programming, readability is determined by different factors than for literature.
Word-pictures are less important since you basically have to deal with a lot of made-up words (variable and function names) but what's really important is to eliminate any room for misinterpretation, e.g.
I vs l or " vs '' or O vs 0Hands down, my font of choice for programming is Consolas, followed by Inconsolata.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30802994</id>
	<title>Finally...</title>
	<author>Anonymous</author>
	<datestamp>1263735900000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Comic Sans MS FTW!</p></htmltext>
<tokenext>Comic Sans MS FTW !</tokentext>
<sentencetext>Comic Sans MS FTW!</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797608</id>
	<title>Re:Monaco</title>
	<author>Jurily</author>
	<datestamp>1263736500000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>3</modscore>
	<htmltext><p>There are a lot of fixed width fonts specifically designed so each character is unique in appearance. That is not negotiable when programming.</p><p>oO0 il1 lilli</p></htmltext>
<tokenext>There are a lot of fixed width fonts specifically designed so each character is unique in appearance .
That is not negotiable when programming.oO0 il1 lilli</tokentext>
<sentencetext>There are a lot of fixed width fonts specifically designed so each character is unique in appearance.
That is not negotiable when programming.oO0 il1 lilli</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797554</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30799330</id>
	<title>Re:Overrated</title>
	<author>AniVisual</author>
	<datestamp>1263752040000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>The case that proportional fonts are not good for programming. Ask yourself these questions before seriously contemplating switching over to proportional fonts:</p><ul>
<li>Is it easy to distinguish between ; and<nobr> <wbr></nobr>:, and ' and "? Also, are<nobr> <wbr></nobr>,. distinguishable?</li><li>Does '' look like " ? What about `` ?</li><li> Is it easy, at a glance, to distinguish between [{}]()l\/V1!Ii|? </li><li> Of course, the Oo0Q characters too.</li></ul><p> Monospace fonts gives width to characters like punctuation and parentheses which is undesirable in prose but essential in programming.</p></htmltext>
<tokenext>The case that proportional fonts are not good for programming .
Ask yourself these questions before seriously contemplating switching over to proportional fonts : Is it easy to distinguish between ; and : , and ' and " ?
Also , are , .
distinguishable ? Does ' ' look like " ?
What about ` ` ?
Is it easy , at a glance , to distinguish between [ { } ] ( ) l \ /V1 ! Ii | ?
Of course , the Oo0Q characters too .
Monospace fonts gives width to characters like punctuation and parentheses which is undesirable in prose but essential in programming .</tokentext>
<sentencetext>The case that proportional fonts are not good for programming.
Ask yourself these questions before seriously contemplating switching over to proportional fonts:
Is it easy to distinguish between ; and :, and ' and "?
Also, are ,.
distinguishable?Does '' look like " ?
What about `` ?
Is it easy, at a glance, to distinguish between [{}]()l\/V1!Ii|?
Of course, the Oo0Q characters too.
Monospace fonts gives width to characters like punctuation and parentheses which is undesirable in prose but essential in programming.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797572</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30802980</id>
	<title>What I use</title>
	<author>Anonymous</author>
	<datestamp>1263735780000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>... is <a href="http://www.deviantart.com/deviation/123433824" title="deviantart.com" rel="nofollow">a proportional font called Cynthia Handwriting</a> [deviantart.com] (the font license says it's OK for personal use) - I like how</p><ul> <li>the I, l, | and O, 0, () are distinct;</li><li>the font itself is quite narrow;</li><li>yet, despite that, it's still quickly readable.</li></ul><p>This font isn't for everyone, though. I code in Java, where the class names are long and the doc strings abound, so most things read as words anyway. I also use Eclipse with a theme that bolds keywords, brackets and braces; the default settings also perform brace matching when I select a brace. It's pretty neat.</p></htmltext>
<tokenext>... is a proportional font called Cynthia Handwriting [ deviantart.com ] ( the font license says it 's OK for personal use ) - I like how the I , l , | and O , 0 , ( ) are distinct ; the font itself is quite narrow ; yet , despite that , it 's still quickly readable.This font is n't for everyone , though .
I code in Java , where the class names are long and the doc strings abound , so most things read as words anyway .
I also use Eclipse with a theme that bolds keywords , brackets and braces ; the default settings also perform brace matching when I select a brace .
It 's pretty neat .</tokentext>
<sentencetext>... is a proportional font called Cynthia Handwriting [deviantart.com] (the font license says it's OK for personal use) - I like how the I, l, | and O, 0, () are distinct;the font itself is quite narrow;yet, despite that, it's still quickly readable.This font isn't for everyone, though.
I code in Java, where the class names are long and the doc strings abound, so most things read as words anyway.
I also use Eclipse with a theme that bolds keywords, brackets and braces; the default settings also perform brace matching when I select a brace.
It's pretty neat.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30798092</id>
	<title>Re:Do the studies apply?</title>
	<author>eliphas\_levy</author>
	<datestamp>1263741720000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>My opinion is like the parent's, I really can't stand the lack of vertical alignment, same length text should display in same width.<br>This code should have the same width no matter what:<br>arrayOne[1010] = 'lll'<br>arrayTwo[1010] = '111'</p><p>I personally use <a href="http://en.wikipedia.org/wiki/DejaVu\_fonts" title="wikipedia.org" rel="nofollow">DeJavu</a> [wikipedia.org] Sans Mono, on all OSes. The (0,O) and (1,l) distinctions are very clear to me, and I like the curves it have.</p><p>I actually had to put it on my pendrive, along with gVim portable, as I will not stand notepad with his blocky console font.</p></htmltext>
<tokenext>My opinion is like the parent 's , I really ca n't stand the lack of vertical alignment , same length text should display in same width.This code should have the same width no matter what : arrayOne [ 1010 ] = 'lll'arrayTwo [ 1010 ] = '111'I personally use DeJavu [ wikipedia.org ] Sans Mono , on all OSes .
The ( 0,O ) and ( 1,l ) distinctions are very clear to me , and I like the curves it have.I actually had to put it on my pendrive , along with gVim portable , as I will not stand notepad with his blocky console font .</tokentext>
<sentencetext>My opinion is like the parent's, I really can't stand the lack of vertical alignment, same length text should display in same width.This code should have the same width no matter what:arrayOne[1010] = 'lll'arrayTwo[1010] = '111'I personally use DeJavu [wikipedia.org] Sans Mono, on all OSes.
The (0,O) and (1,l) distinctions are very clear to me, and I like the curves it have.I actually had to put it on my pendrive, along with gVim portable, as I will not stand notepad with his blocky console font.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797630</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30798022</id>
	<title>Re:Overrated</title>
	<author>interiot</author>
	<datestamp>1263741060000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>4</modscore>
	<htmltext><p> <a href="http://nickgravgaard.com/elastictabstops/" title="nickgravgaard.com">Elastic tabstops</a> [nickgravgaard.com] solve the alignment problem.  "Do what I mean, not what I say" with whitespace is a <i>good</i> thing, particularly when the width of a character can be totally different for every reader.  Elastic tabstops aren't implemented in many editors yet (currently available as an optional feature in <a href="http://nickgravgaard.com/elastictabstops/gedit/" title="nickgravgaard.com">gedit</a> [nickgravgaard.com] and <a href="http://tibleiz.net/code-browser/news.html" title="tibleiz.net">Code Browser</a> [tibleiz.net]), but once it becomes more widespread, many more programmers will be free to try out proportional fonts for coding.</p></htmltext>
<tokenext>Elastic tabstops [ nickgravgaard.com ] solve the alignment problem .
" Do what I mean , not what I say " with whitespace is a good thing , particularly when the width of a character can be totally different for every reader .
Elastic tabstops are n't implemented in many editors yet ( currently available as an optional feature in gedit [ nickgravgaard.com ] and Code Browser [ tibleiz.net ] ) , but once it becomes more widespread , many more programmers will be free to try out proportional fonts for coding .</tokentext>
<sentencetext> Elastic tabstops [nickgravgaard.com] solve the alignment problem.
"Do what I mean, not what I say" with whitespace is a good thing, particularly when the width of a character can be totally different for every reader.
Elastic tabstops aren't implemented in many editors yet (currently available as an optional feature in gedit [nickgravgaard.com] and Code Browser [tibleiz.net]), but once it becomes more widespread, many more programmers will be free to try out proportional fonts for coding.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797572</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30803634</id>
	<title>Bad example</title>
	<author>jonaskoelker</author>
	<datestamp>1263741420000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>The typo is easier to spot in fixed font.</p></div><p>Actually, it's just as easy to spot in a proportional font, because what you're comparing isn't a character count but equal prefixes.  If they're strcmp-equal, wouldn't they also be pixelwidth-equal, independent of the (constantness of the) char-to-pixelwidth mapping, as long as it doesn't vary per line?</p><p>Of course, you're right in your point that it lets you compare character count visually much faster.  That seems to be relevant somewhat less often, though.</p></div>
	</htmltext>
<tokenext>The typo is easier to spot in fixed font.Actually , it 's just as easy to spot in a proportional font , because what you 're comparing is n't a character count but equal prefixes .
If they 're strcmp-equal , would n't they also be pixelwidth-equal , independent of the ( constantness of the ) char-to-pixelwidth mapping , as long as it does n't vary per line ? Of course , you 're right in your point that it lets you compare character count visually much faster .
That seems to be relevant somewhat less often , though .</tokentext>
<sentencetext>The typo is easier to spot in fixed font.Actually, it's just as easy to spot in a proportional font, because what you're comparing isn't a character count but equal prefixes.
If they're strcmp-equal, wouldn't they also be pixelwidth-equal, independent of the (constantness of the) char-to-pixelwidth mapping, as long as it doesn't vary per line?Of course, you're right in your point that it lets you compare character count visually much faster.
That seems to be relevant somewhat less often, though.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30798366</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797606</id>
	<title>fixed</title>
	<author>HalfFlat</author>
	<datestamp>1263736500000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>2</modscore>
	<htmltext><p>
<tt>fixed</tt>, AKA <tt>6x13</tt>, or more formally, <tt>-misc-fixed-medium-r-semicondensed--13-120-75-75-c-60-iso10646-1</tt>.
</p><p>The one true programming font. No other font better manages the compromise between legibility and compactness,
and being a well-crafted bitmap font, it is crisper and clearer than ever on modern LCD screens.<br>
X11 got it right 25 odd years ago, and now with near-full Unicode support, it's only gotten better.</p></htmltext>
<tokenext>fixed , AKA 6x13 , or more formally , -misc-fixed-medium-r-semicondensed--13-120-75-75-c-60-iso10646-1 .
The one true programming font .
No other font better manages the compromise between legibility and compactness , and being a well-crafted bitmap font , it is crisper and clearer than ever on modern LCD screens .
X11 got it right 25 odd years ago , and now with near-full Unicode support , it 's only gotten better .</tokentext>
<sentencetext>
fixed, AKA 6x13, or more formally, -misc-fixed-medium-r-semicondensed--13-120-75-75-c-60-iso10646-1.
The one true programming font.
No other font better manages the compromise between legibility and compactness,
and being a well-crafted bitmap font, it is crisper and clearer than ever on modern LCD screens.
X11 got it right 25 odd years ago, and now with near-full Unicode support, it's only gotten better.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797778</id>
	<title>Lining things up</title>
	<author>slim</author>
	<datestamp>1263738900000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I like to line stuff up, such as assignments. (Tried to demonstrate this with a code sample, but<nobr> <wbr></nobr>/. comments collapse spaces)</p><p>So for a list of const definitions in<nobr> <wbr></nobr>.h file, for example, despite variable names of differing lengths, the "=" signs will all be in the same column, and the values will all begin in the same column.</p><p>You might be able to achieve this with a proportional font and tabs, but I don't trust tabs.</p></htmltext>
<tokenext>I like to line stuff up , such as assignments .
( Tried to demonstrate this with a code sample , but / .
comments collapse spaces ) So for a list of const definitions in .h file , for example , despite variable names of differing lengths , the " = " signs will all be in the same column , and the values will all begin in the same column.You might be able to achieve this with a proportional font and tabs , but I do n't trust tabs .</tokentext>
<sentencetext>I like to line stuff up, such as assignments.
(Tried to demonstrate this with a code sample, but /.
comments collapse spaces)So for a list of const definitions in .h file, for example, despite variable names of differing lengths, the "=" signs will all be in the same column, and the values will all begin in the same column.You might be able to achieve this with a proportional font and tabs, but I don't trust tabs.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30799698</id>
	<title>Re: proportional fonts can be read 14\% faster</title>
	<author>Joce640k</author>
	<datestamp>1263755100000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Thing is, you don't "read" source code the way you read normal text.</p></htmltext>
<tokenext>Thing is , you do n't " read " source code the way you read normal text .</tokentext>
<sentencetext>Thing is, you don't "read" source code the way you read normal text.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30800242</id>
	<title>Use SciTE</title>
	<author>Anonymous</author>
	<datestamp>1263759300000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Switch between monospaced and proportional with Ctrl+F11. Easy as pie.</p><p>http://www.scintilla.org/SciTE.html</p></htmltext>
<tokenext>Switch between monospaced and proportional with Ctrl + F11 .
Easy as pie.http : //www.scintilla.org/SciTE.html</tokentext>
<sentencetext>Switch between monospaced and proportional with Ctrl+F11.
Easy as pie.http://www.scintilla.org/SciTE.html</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797706</id>
	<title>Quality instead of quantity</title>
	<author>GuerreroDelInterfaz</author>
	<datestamp>1263737760000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>When reading code speed is not the most important thing. Here quality is more important.</p><p>And the quality of alignment brought to you by fixed-length fonts is more important than any marginal gain in reading speed.</p><p>--<br>El Guerrero del Interfaz</p></htmltext>
<tokenext>When reading code speed is not the most important thing .
Here quality is more important.And the quality of alignment brought to you by fixed-length fonts is more important than any marginal gain in reading speed.--El Guerrero del Interfaz</tokentext>
<sentencetext>When reading code speed is not the most important thing.
Here quality is more important.And the quality of alignment brought to you by fixed-length fonts is more important than any marginal gain in reading speed.--El Guerrero del Interfaz</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30799996</id>
	<title>Different fonts for different parts of a program?</title>
	<author>plopez</author>
	<datestamp>1263757320000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Comments could be one font. Attributes another. Functions a third. As could DB and library calls. Has anyone tried this? Do you think it would help? Or would it be too noisy?</p></htmltext>
<tokenext>Comments could be one font .
Attributes another .
Functions a third .
As could DB and library calls .
Has anyone tried this ?
Do you think it would help ?
Or would it be too noisy ?</tokentext>
<sentencetext>Comments could be one font.
Attributes another.
Functions a third.
As could DB and library calls.
Has anyone tried this?
Do you think it would help?
Or would it be too noisy?</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797978</id>
	<title>Re:Do the studies apply?</title>
	<author>Anonymous</author>
	<datestamp>1263740700000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>I used to use Inconsolata until I had to work on the code of one of my colleagues. His editor automatically inserted his name at the begining of the text file. His name contain a diacritic sign which looked messed up on my machine.<br>I switched back to my Fedora defaults (monospaced deja vu) which had no problems with utf8 whatsoever.</p></htmltext>
<tokenext>I used to use Inconsolata until I had to work on the code of one of my colleagues .
His editor automatically inserted his name at the begining of the text file .
His name contain a diacritic sign which looked messed up on my machine.I switched back to my Fedora defaults ( monospaced deja vu ) which had no problems with utf8 whatsoever .</tokentext>
<sentencetext>I used to use Inconsolata until I had to work on the code of one of my colleagues.
His editor automatically inserted his name at the begining of the text file.
His name contain a diacritic sign which looked messed up on my machine.I switched back to my Fedora defaults (monospaced deja vu) which had no problems with utf8 whatsoever.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797630</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30800676</id>
	<title>Re:fixed</title>
	<author>david.given</author>
	<datestamp>1263719580000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>The one true programming font. No other font better manages the compromise between legibility and compactness,
and being a well-crafted bitmap font, it is crisper and clearer than ever on modern LCD screens.

X11 got it right 25 odd years ago, and now with near-full Unicode support, it's only gotten better.</p></div><p>Alas,  Gnome and KDE both try really hard to hide the mere fact of bitmap fonts' existence from you. It appears to be impossible to tell apps like Eclipse or gnome-terminal to use fixed.

</p><p>I've always been rather partial to <a href="http://unifoundry.com/unifont.html" title="unifoundry.com">Unifont</a> [unifoundry.com]. It's a bit chunky compared to fixed, by it supports all characters in Unicode BMP (programming: it's not just in ASCII any more), and there's a TTF version. Of course, the TTF file renders each character as a sequence of little squares, which means that unless you like 12pt you'll get a migraine, but at least it works...</p></div>
	</htmltext>
<tokenext>The one true programming font .
No other font better manages the compromise between legibility and compactness , and being a well-crafted bitmap font , it is crisper and clearer than ever on modern LCD screens .
X11 got it right 25 odd years ago , and now with near-full Unicode support , it 's only gotten better.Alas , Gnome and KDE both try really hard to hide the mere fact of bitmap fonts ' existence from you .
It appears to be impossible to tell apps like Eclipse or gnome-terminal to use fixed .
I 've always been rather partial to Unifont [ unifoundry.com ] .
It 's a bit chunky compared to fixed , by it supports all characters in Unicode BMP ( programming : it 's not just in ASCII any more ) , and there 's a TTF version .
Of course , the TTF file renders each character as a sequence of little squares , which means that unless you like 12pt you 'll get a migraine , but at least it works.. .</tokentext>
<sentencetext>The one true programming font.
No other font better manages the compromise between legibility and compactness,
and being a well-crafted bitmap font, it is crisper and clearer than ever on modern LCD screens.
X11 got it right 25 odd years ago, and now with near-full Unicode support, it's only gotten better.Alas,  Gnome and KDE both try really hard to hide the mere fact of bitmap fonts' existence from you.
It appears to be impossible to tell apps like Eclipse or gnome-terminal to use fixed.
I've always been rather partial to Unifont [unifoundry.com].
It's a bit chunky compared to fixed, by it supports all characters in Unicode BMP (programming: it's not just in ASCII any more), and there's a TTF version.
Of course, the TTF file renders each character as a sequence of little squares, which means that unless you like 12pt you'll get a migraine, but at least it works...
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797606</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30799306</id>
	<title>Re:Overrated</title>
	<author>ceoyoyo</author>
	<datestamp>1263751860000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>4</modscore>
	<htmltext><p>Just use tabs.  If the dork who opens your text file doesn't have his tab stop set for his preferred size then he deserves to see ugly code.</p><p>You probably use four spaces, hey?  Personally I hate four spaces.  Waste of space.  Two is the way it was intended to be.  But I understand that other people might have different preferences.  With tabs we can all be happy.</p></htmltext>
<tokenext>Just use tabs .
If the dork who opens your text file does n't have his tab stop set for his preferred size then he deserves to see ugly code.You probably use four spaces , hey ?
Personally I hate four spaces .
Waste of space .
Two is the way it was intended to be .
But I understand that other people might have different preferences .
With tabs we can all be happy .</tokentext>
<sentencetext>Just use tabs.
If the dork who opens your text file doesn't have his tab stop set for his preferred size then he deserves to see ugly code.You probably use four spaces, hey?
Personally I hate four spaces.
Waste of space.
Two is the way it was intended to be.
But I understand that other people might have different preferences.
With tabs we can all be happy.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30798296</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797548</id>
	<title>Hmmm...</title>
	<author>Anonymous</author>
	<datestamp>1263735720000</datestamp>
	<modclass>Flamebait</modclass>
	<modscore>-1</modscore>
	<htmltext><p>Sounds like programming for retards to me.</p></htmltext>
<tokenext>Sounds like programming for retards to me .</tokentext>
<sentencetext>Sounds like programming for retards to me.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30798592</id>
	<title>it's easy</title>
	<author>garaged</author>
	<datestamp>1263745860000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>if it makes it hard to write ascii art it cannot be good for programming</p></htmltext>
<tokenext>if it makes it hard to write ascii art it can not be good for programming</tokentext>
<sentencetext>if it makes it hard to write ascii art it cannot be good for programming</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30800852</id>
	<title>I'd prefer</title>
	<author>tthomas48</author>
	<datestamp>1263720660000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>What would be nice would be an IDE that could deal with proportional fonts. Keep my tab stops, spaces, and braces in alignment, but render the text in proportional font. I understand the value of being able to read the language part of my code as language, and read the structural part of my code as structure. The best of both worlds would be nice.</p></htmltext>
<tokenext>What would be nice would be an IDE that could deal with proportional fonts .
Keep my tab stops , spaces , and braces in alignment , but render the text in proportional font .
I understand the value of being able to read the language part of my code as language , and read the structural part of my code as structure .
The best of both worlds would be nice .</tokentext>
<sentencetext>What would be nice would be an IDE that could deal with proportional fonts.
Keep my tab stops, spaces, and braces in alignment, but render the text in proportional font.
I understand the value of being able to read the language part of my code as language, and read the structural part of my code as structure.
The best of both worlds would be nice.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30803550</id>
	<title>Re:Overrated</title>
	<author>nschubach</author>
	<datestamp>1263740700000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Honestly, I think editors/language should be smart/configurable enough to allow you to open a code file comprised of one line of code and it can indent and format the code to the developer's liking.  When they save it, one line it again and remove all their needless formatting so when the next developer opens it they see the code how they prefer.</p></htmltext>
<tokenext>Honestly , I think editors/language should be smart/configurable enough to allow you to open a code file comprised of one line of code and it can indent and format the code to the developer 's liking .
When they save it , one line it again and remove all their needless formatting so when the next developer opens it they see the code how they prefer .</tokentext>
<sentencetext>Honestly, I think editors/language should be smart/configurable enough to allow you to open a code file comprised of one line of code and it can indent and format the code to the developer's liking.
When they save it, one line it again and remove all their needless formatting so when the next developer opens it they see the code how they prefer.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30799306</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797696</id>
	<title>Re:fixed</title>
	<author>arth1</author>
	<datestamp>1263737640000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>2</modscore>
	<htmltext><p>I'm a predominantly Unix (and -like) user myself, but X11 fonts is one department where I think work is needed.  The choice between 75 and 100 dpi (newer displays tend to be far more than 100 dpi), and no subpixel smoothing?  As for "fixed", it's one of the least readable fixed width fonts.  Whenever I encounter it, I switch it over to "screen" (by Haeberli, then at SGI), or better yet, consolas if hinted fonts are supported.</p><p>As for TFA and using proportional fonts for programming, all I can say is that the author can't be doing a lot of unified diffs, or working with languages where the amount of indentation is significant (fortran, anyone?).  Hell, even doing a cut/paste becomes more difficult when some of the letters are much narrower.<br>And with most prop fonts, good luck seeing the difference between variables like ill, lil and il1, or B80, 8BO and B8&#216;, for that matter.</p></htmltext>
<tokenext>I 'm a predominantly Unix ( and -like ) user myself , but X11 fonts is one department where I think work is needed .
The choice between 75 and 100 dpi ( newer displays tend to be far more than 100 dpi ) , and no subpixel smoothing ?
As for " fixed " , it 's one of the least readable fixed width fonts .
Whenever I encounter it , I switch it over to " screen " ( by Haeberli , then at SGI ) , or better yet , consolas if hinted fonts are supported.As for TFA and using proportional fonts for programming , all I can say is that the author ca n't be doing a lot of unified diffs , or working with languages where the amount of indentation is significant ( fortran , anyone ? ) .
Hell , even doing a cut/paste becomes more difficult when some of the letters are much narrower.And with most prop fonts , good luck seeing the difference between variables like ill , lil and il1 , or B80 , 8BO and B8   , for that matter .</tokentext>
<sentencetext>I'm a predominantly Unix (and -like) user myself, but X11 fonts is one department where I think work is needed.
The choice between 75 and 100 dpi (newer displays tend to be far more than 100 dpi), and no subpixel smoothing?
As for "fixed", it's one of the least readable fixed width fonts.
Whenever I encounter it, I switch it over to "screen" (by Haeberli, then at SGI), or better yet, consolas if hinted fonts are supported.As for TFA and using proportional fonts for programming, all I can say is that the author can't be doing a lot of unified diffs, or working with languages where the amount of indentation is significant (fortran, anyone?).
Hell, even doing a cut/paste becomes more difficult when some of the letters are much narrower.And with most prop fonts, good luck seeing the difference between variables like ill, lil and il1, or B80, 8BO and B8Ø, for that matter.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797606</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30801112</id>
	<title>Tabs</title>
	<author>gknoy</author>
	<datestamp>1263722280000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>As long as tabs (And corresponding blocks) are indented properly, I don't think I would care as much.</p></htmltext>
<tokenext>As long as tabs ( And corresponding blocks ) are indented properly , I do n't think I would care as much .</tokentext>
<sentencetext>As long as tabs (And corresponding blocks) are indented properly, I don't think I would care as much.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30798844</id>
	<title>In summary</title>
	<author>SoonerSkeene</author>
	<datestamp>1263748020000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>I see a lot of great points for mono fonts, most notably the ability to quickly distinguish puctuation marks or errors such as "' " versus " ".
But acctual words and blocks of some code are easier to read in a proportional font.

So... is there a font out there specifically designed for coding, with the best of both worlds?</htmltext>
<tokenext>I see a lot of great points for mono fonts , most notably the ability to quickly distinguish puctuation marks or errors such as " ' " versus " " .
But acctual words and blocks of some code are easier to read in a proportional font .
So... is there a font out there specifically designed for coding , with the best of both worlds ?</tokentext>
<sentencetext>I see a lot of great points for mono fonts, most notably the ability to quickly distinguish puctuation marks or errors such as "' " versus " ".
But acctual words and blocks of some code are easier to read in a proportional font.
So... is there a font out there specifically designed for coding, with the best of both worlds?</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30802660</id>
	<title>Re:visual cues</title>
	<author>Anonymous</author>
	<datestamp>1263733020000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>If "richly structured layout" is important for comprehension, then why not bold, underline, italic, strikethough, multiple fonts and sizes, colors etc. as well? OK, some coders would produce code more ugly than myspace (blinking code, anyone?), but the vast majority would take advantage of these features, the way they already take advantage of rich layout.</p></htmltext>
<tokenext>If " richly structured layout " is important for comprehension , then why not bold , underline , italic , strikethough , multiple fonts and sizes , colors etc .
as well ?
OK , some coders would produce code more ugly than myspace ( blinking code , anyone ?
) , but the vast majority would take advantage of these features , the way they already take advantage of rich layout .</tokentext>
<sentencetext>If "richly structured layout" is important for comprehension, then why not bold, underline, italic, strikethough, multiple fonts and sizes, colors etc.
as well?
OK, some coders would produce code more ugly than myspace (blinking code, anyone?
), but the vast majority would take advantage of these features, the way they already take advantage of rich layout.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797816</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30799474</id>
	<title>Re:Monaco</title>
	<author>koinu</author>
	<datestamp>1263753360000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>O\_O<nobr> <wbr></nobr>... you slashdot ppl amaze me!</p><p>I just googled for "monaco font" and it gave me:<br>"97th most popular search in the past hour"</p><p>Hmm... I guess it makes more sense to build up my personal army here and not in<nobr> <wbr></nobr>/b/.</p></htmltext>
<tokenext>O \ _O ... you slashdot ppl amaze me ! I just googled for " monaco font " and it gave me : " 97th most popular search in the past hour " Hmm... I guess it makes more sense to build up my personal army here and not in /b/ .</tokentext>
<sentencetext>O\_O ... you slashdot ppl amaze me!I just googled for "monaco font" and it gave me:"97th most popular search in the past hour"Hmm... I guess it makes more sense to build up my personal army here and not in /b/.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797554</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30800114</id>
	<title>Re:Overrated</title>
	<author>Garble Snarky</author>
	<datestamp>1263758220000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>You should just write a simple bookmarklet or greasemonkey script to change the style of all input areas.</htmltext>
<tokenext>You should just write a simple bookmarklet or greasemonkey script to change the style of all input areas .</tokentext>
<sentencetext>You should just write a simple bookmarklet or greasemonkey script to change the style of all input areas.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30798296</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30798798</id>
	<title>Re:Examples...</title>
	<author>TheRaven64</author>
	<datestamp>1263747600000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>Fixed width Monaco 10pt, which comes out too small and kind of blurry to me.</p></div><p>That one is really stupid.  They are using antialiasing, but Monaco is specifically designed to render well at point size 10 without antialising.  The curves line up with the pixels cleanly and you can read it very easily.  Turn on antialiasing and you get something blurry.  Monaco really shouldn't be antialiased below about 12-14pt.</p></div>
	</htmltext>
<tokenext>Fixed width Monaco 10pt , which comes out too small and kind of blurry to me.That one is really stupid .
They are using antialiasing , but Monaco is specifically designed to render well at point size 10 without antialising .
The curves line up with the pixels cleanly and you can read it very easily .
Turn on antialiasing and you get something blurry .
Monaco really should n't be antialiased below about 12-14pt .</tokentext>
<sentencetext>Fixed width Monaco 10pt, which comes out too small and kind of blurry to me.That one is really stupid.
They are using antialiasing, but Monaco is specifically designed to render well at point size 10 without antialising.
The curves line up with the pixels cleanly and you can read it very easily.
Turn on antialiasing and you get something blurry.
Monaco really shouldn't be antialiased below about 12-14pt.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797740</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30798074</id>
	<title>Re:Not the bottleneck</title>
	<author>interiot</author>
	<datestamp>1263741480000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>You can easily modify one of the GPL fonts to use wider punctuation, and call it a programmer's font.  The important thing that makes proportional fonts faster to read is that the <i>letters</i> are proportional-width, punctuation width doesn't necessarily have to stay small.</htmltext>
<tokenext>You can easily modify one of the GPL fonts to use wider punctuation , and call it a programmer 's font .
The important thing that makes proportional fonts faster to read is that the letters are proportional-width , punctuation width does n't necessarily have to stay small .</tokentext>
<sentencetext>You can easily modify one of the GPL fonts to use wider punctuation, and call it a programmer's font.
The important thing that makes proportional fonts faster to read is that the letters are proportional-width, punctuation width doesn't necessarily have to stay small.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797664</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797634</id>
	<title>Proportional fonts are better to read</title>
	<author>krou</author>
	<datestamp>1263736740000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>4</modscore>
	<htmltext><p>From what I understand, the way we process written words is based on the idea that each word is a like a "picture" made up of letters. So, the easier it is to identify the picture, the easier it is for us to read. This means that the width and height of letters plays an important part in creating unique pictures. It is for this reason (at least in print) serif fonts are much easier to read than sans-serif fonts. It's also for this reason that ALL CAPS is the most difficult way to read compared to just reading normal text. On this basis alone, it's likely that proportional fonts are better to read because they're likely to create better word pictures.</p></htmltext>
<tokenext>From what I understand , the way we process written words is based on the idea that each word is a like a " picture " made up of letters .
So , the easier it is to identify the picture , the easier it is for us to read .
This means that the width and height of letters plays an important part in creating unique pictures .
It is for this reason ( at least in print ) serif fonts are much easier to read than sans-serif fonts .
It 's also for this reason that ALL CAPS is the most difficult way to read compared to just reading normal text .
On this basis alone , it 's likely that proportional fonts are better to read because they 're likely to create better word pictures .</tokentext>
<sentencetext>From what I understand, the way we process written words is based on the idea that each word is a like a "picture" made up of letters.
So, the easier it is to identify the picture, the easier it is for us to read.
This means that the width and height of letters plays an important part in creating unique pictures.
It is for this reason (at least in print) serif fonts are much easier to read than sans-serif fonts.
It's also for this reason that ALL CAPS is the most difficult way to read compared to just reading normal text.
On this basis alone, it's likely that proportional fonts are better to read because they're likely to create better word pictures.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30805170</id>
	<title>Re:Only if you don't use VIM</title>
	<author>lpq</author>
	<datestamp>1263756900000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Ditto on the vim issue... I'll switch to a proportional font in a heartbeat if vim supports it.</p><p>Sigh</p><p>Maybe vim is in need of a fork?</p></htmltext>
<tokenext>Ditto on the vim issue... I 'll switch to a proportional font in a heartbeat if vim supports it.SighMaybe vim is in need of a fork ?</tokentext>
<sentencetext>Ditto on the vim issue... I'll switch to a proportional font in a heartbeat if vim supports it.SighMaybe vim is in need of a fork?</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797946</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30798098</id>
	<title>Re:Overrated</title>
	<author>Anonymous</author>
	<datestamp>1263741780000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>But alignment would be the same no matter what font you use, at least assuming you don't mix tabs and spaces. Two spaces in a non-proportional font are always the same width, but so are two spaces in a proportional font.</p><p>Granted, two spaces in many proportional fonts aren't going to be enough to make indentation obvious, but beyond that...</p></htmltext>
<tokenext>But alignment would be the same no matter what font you use , at least assuming you do n't mix tabs and spaces .
Two spaces in a non-proportional font are always the same width , but so are two spaces in a proportional font.Granted , two spaces in many proportional fonts are n't going to be enough to make indentation obvious , but beyond that.. .</tokentext>
<sentencetext>But alignment would be the same no matter what font you use, at least assuming you don't mix tabs and spaces.
Two spaces in a non-proportional font are always the same width, but so are two spaces in a proportional font.Granted, two spaces in many proportional fonts aren't going to be enough to make indentation obvious, but beyond that...</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797572</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30813134</id>
	<title>Re:Overrated</title>
	<author>jgrahn</author>
	<datestamp>1263811980000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><blockquote><div><p>Sorry, Elastic Tabstops solve nothing. That is just yet another way of interpreting a tab character. The problem with tabs is the tab character itself and the fact that different rendering mechanisms interpret it differently. If you type a tab in an editor which renders it as an 8-character indentation and I view it in an editor which renders it as a 4-character indentation, then what I see is not what you intended.</p></div></blockquote><p>
Sure -- because you have misconfigured your tools.
It's not my fault -- just as its not my fault the text is upside-down if you have turned your monitor
upside down.
(But as you see I agree that "Elastic Tabstops" is a bad idea.)</p><blockquote><div><p> The only thing which works consistently is to use a fixed-width font and space characters for indentation. Any programmer who doesn't grasp this and who puts tabs into his code is obviously not a good rational thinker and is thus probably not a very good programmer.</p></div></blockquote><p>
No, rational thinking here would be: TAB is useless unless everyone interprets it the same.
Terminal emulators, printers and all sane program defaults choose 8 spaces, therefore I should
use 8-spaced TABs, and ignore people who modify their tools to use some other setting -- they have
already fscked it up for themselves and will not notice the extra pain.</p></div>
	</htmltext>
<tokenext>Sorry , Elastic Tabstops solve nothing .
That is just yet another way of interpreting a tab character .
The problem with tabs is the tab character itself and the fact that different rendering mechanisms interpret it differently .
If you type a tab in an editor which renders it as an 8-character indentation and I view it in an editor which renders it as a 4-character indentation , then what I see is not what you intended .
Sure -- because you have misconfigured your tools .
It 's not my fault -- just as its not my fault the text is upside-down if you have turned your monitor upside down .
( But as you see I agree that " Elastic Tabstops " is a bad idea .
) The only thing which works consistently is to use a fixed-width font and space characters for indentation .
Any programmer who does n't grasp this and who puts tabs into his code is obviously not a good rational thinker and is thus probably not a very good programmer .
No , rational thinking here would be : TAB is useless unless everyone interprets it the same .
Terminal emulators , printers and all sane program defaults choose 8 spaces , therefore I should use 8-spaced TABs , and ignore people who modify their tools to use some other setting -- they have already fscked it up for themselves and will not notice the extra pain .</tokentext>
<sentencetext>Sorry, Elastic Tabstops solve nothing.
That is just yet another way of interpreting a tab character.
The problem with tabs is the tab character itself and the fact that different rendering mechanisms interpret it differently.
If you type a tab in an editor which renders it as an 8-character indentation and I view it in an editor which renders it as a 4-character indentation, then what I see is not what you intended.
Sure -- because you have misconfigured your tools.
It's not my fault -- just as its not my fault the text is upside-down if you have turned your monitor
upside down.
(But as you see I agree that "Elastic Tabstops" is a bad idea.
) The only thing which works consistently is to use a fixed-width font and space characters for indentation.
Any programmer who doesn't grasp this and who puts tabs into his code is obviously not a good rational thinker and is thus probably not a very good programmer.
No, rational thinking here would be: TAB is useless unless everyone interprets it the same.
Terminal emulators, printers and all sane program defaults choose 8 spaces, therefore I should
use 8-spaced TABs, and ignore people who modify their tools to use some other setting -- they have
already fscked it up for themselves and will not notice the extra pain.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30799686</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797720</id>
	<title>Bad for the next maintainer</title>
	<author>Anonymous</author>
	<datestamp>1263737880000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>The people who are going to maintain your code will probably use fixed-width fonts. Clever alignments tricks won't work for them and your code will look horrible.</p><p>If I were your boss, I'd just plain forbid this.</p><p>Unless your code is for yourself only, stick to the "standards". A 14\% improvement ? Gimme a break...</p></htmltext>
<tokenext>The people who are going to maintain your code will probably use fixed-width fonts .
Clever alignments tricks wo n't work for them and your code will look horrible.If I were your boss , I 'd just plain forbid this.Unless your code is for yourself only , stick to the " standards " .
A 14 \ % improvement ?
Gim me a break.. .</tokentext>
<sentencetext>The people who are going to maintain your code will probably use fixed-width fonts.
Clever alignments tricks won't work for them and your code will look horrible.If I were your boss, I'd just plain forbid this.Unless your code is for yourself only, stick to the "standards".
A 14\% improvement ?
Gimme a break...</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30799654</id>
	<title>Re:Monaco</title>
	<author>zill</author>
	<datestamp>1263754800000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Programming fonts and proportional fonts are not mutually exclusive. You could have a proportional font that clearly differentiate "oO0 il1 lilli".</htmltext>
<tokenext>Programming fonts and proportional fonts are not mutually exclusive .
You could have a proportional font that clearly differentiate " oO0 il1 lilli " .</tokentext>
<sentencetext>Programming fonts and proportional fonts are not mutually exclusive.
You could have a proportional font that clearly differentiate "oO0 il1 lilli".</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797608</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30798478</id>
	<title>inilliibiliti</title>
	<author>Anonymous</author>
	<datestamp>1263745020000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>4</modscore>
	<htmltext><p><div class="quote"><p>proportional fonts can be read 14\% faster than fixed-width fonts</p></div><p>Sounds good, until brain engages, 14\% later.  <i>can be</i> always flags +10 in my wetware instance of CrapAssassin, unless BeerGoggles is displacing cycles.</p><p>I think, with maybe 60,000 hours of reading time under my lengthening belt, I'd have noticed this effect by now, if it applied carte blanch to all modes of reading.  The other night I skimmed the 130,000 words supplied in response to the Edge 2010 question "How is the Internet changing the way YOU think?"  This was not the cream of their efforts, but there were some interesting topical centers.</p><p>My reading speed through this exercise varied by an order of magnitude, depending on signal density.  The weird thing is, for some of the longer responses, my subconscious sends notice "nothing to see here" at a skimming speed where I have no clue what words are actually flying past.  Every so often, I drop out of warp speed to double check, and sure enough, not very much to see here, by whatever criteria turns my crank, which itself is sometimes elusive to my conscious mind.</p><p><div class="quote"><p>I took a speed reading course and read 'War and Peace' in twenty minutes. It involves Russia.<br>
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &mdash; Woody Allen</p></div><p>I once attended a school where in some dark closet they kept copies of "Duck and Cover" films, as well as a CRM114-vintage machine designed to stretch your saccade, by forcing you to read words in a revealed window with a progressive speed ratchet.</p><p>I never did especially well compared to the best of my classmates on the quiz that followed.  Had they slowed that stupid thing down to about half the speed they were forcing us to read, followed by an essay question to expound upon conceptual error, distortion, slant, exaggeration, and damn lies, I would have run out of foolscap before completing my task.  In critical response, I was an autobahn surrounded by country lanes, yet many of my classmates could read for uncritical comprehension faster than I could.  Dangerous skill.  (I'm sure for some of my old classmates, whatever dirt path once existed has returned to nature in their adult years, with ample fertilizer from mainstream media, but that's another matter.)</p><p>It's no different with source code.  You can read for comprehension, or you can read for <i>all possible error</i>, a state of mind where the eyes consume only a tiny fraction of total brain glucose.  Critical thought in the <a href="http://www.youtube.com/watch?v=4wp3m1vg06Q" title="youtube.com">candy factory</a> [youtube.com] is hard enough when the conveyor flows along at a consistent speed.  Neither can I properly type a long sequence of i and l characters worth a damn in a proportional font.  My eyes fail to sync with my fingers, and half the letters fall down my shirt.</p><p>Nothing impairs reading speed like a tightly written algorithm where every symbol is exactly right.  Nothing inflates the volume of symbols violently gouged onto the retina as a chunk of code where no symbol means precisely what it seems to mean.</p><p>Personally, I'm not lining up for smaller gouges in greater number.</p></div>
	</htmltext>
<tokenext>proportional fonts can be read 14 \ % faster than fixed-width fontsSounds good , until brain engages , 14 \ % later .
can be always flags + 10 in my wetware instance of CrapAssassin , unless BeerGoggles is displacing cycles.I think , with maybe 60,000 hours of reading time under my lengthening belt , I 'd have noticed this effect by now , if it applied carte blanch to all modes of reading .
The other night I skimmed the 130,000 words supplied in response to the Edge 2010 question " How is the Internet changing the way YOU think ?
" This was not the cream of their efforts , but there were some interesting topical centers.My reading speed through this exercise varied by an order of magnitude , depending on signal density .
The weird thing is , for some of the longer responses , my subconscious sends notice " nothing to see here " at a skimming speed where I have no clue what words are actually flying past .
Every so often , I drop out of warp speed to double check , and sure enough , not very much to see here , by whatever criteria turns my crank , which itself is sometimes elusive to my conscious mind.I took a speed reading course and read 'War and Peace ' in twenty minutes .
It involves Russia .
             Woody AllenI once attended a school where in some dark closet they kept copies of " Duck and Cover " films , as well as a CRM114-vintage machine designed to stretch your saccade , by forcing you to read words in a revealed window with a progressive speed ratchet.I never did especially well compared to the best of my classmates on the quiz that followed .
Had they slowed that stupid thing down to about half the speed they were forcing us to read , followed by an essay question to expound upon conceptual error , distortion , slant , exaggeration , and damn lies , I would have run out of foolscap before completing my task .
In critical response , I was an autobahn surrounded by country lanes , yet many of my classmates could read for uncritical comprehension faster than I could .
Dangerous skill .
( I 'm sure for some of my old classmates , whatever dirt path once existed has returned to nature in their adult years , with ample fertilizer from mainstream media , but that 's another matter .
) It 's no different with source code .
You can read for comprehension , or you can read for all possible error , a state of mind where the eyes consume only a tiny fraction of total brain glucose .
Critical thought in the candy factory [ youtube.com ] is hard enough when the conveyor flows along at a consistent speed .
Neither can I properly type a long sequence of i and l characters worth a damn in a proportional font .
My eyes fail to sync with my fingers , and half the letters fall down my shirt.Nothing impairs reading speed like a tightly written algorithm where every symbol is exactly right .
Nothing inflates the volume of symbols violently gouged onto the retina as a chunk of code where no symbol means precisely what it seems to mean.Personally , I 'm not lining up for smaller gouges in greater number .</tokentext>
<sentencetext>proportional fonts can be read 14\% faster than fixed-width fontsSounds good, until brain engages, 14\% later.
can be always flags +10 in my wetware instance of CrapAssassin, unless BeerGoggles is displacing cycles.I think, with maybe 60,000 hours of reading time under my lengthening belt, I'd have noticed this effect by now, if it applied carte blanch to all modes of reading.
The other night I skimmed the 130,000 words supplied in response to the Edge 2010 question "How is the Internet changing the way YOU think?
"  This was not the cream of their efforts, but there were some interesting topical centers.My reading speed through this exercise varied by an order of magnitude, depending on signal density.
The weird thing is, for some of the longer responses, my subconscious sends notice "nothing to see here" at a skimming speed where I have no clue what words are actually flying past.
Every so often, I drop out of warp speed to double check, and sure enough, not very much to see here, by whatever criteria turns my crank, which itself is sometimes elusive to my conscious mind.I took a speed reading course and read 'War and Peace' in twenty minutes.
It involves Russia.
          — Woody AllenI once attended a school where in some dark closet they kept copies of "Duck and Cover" films, as well as a CRM114-vintage machine designed to stretch your saccade, by forcing you to read words in a revealed window with a progressive speed ratchet.I never did especially well compared to the best of my classmates on the quiz that followed.
Had they slowed that stupid thing down to about half the speed they were forcing us to read, followed by an essay question to expound upon conceptual error, distortion, slant, exaggeration, and damn lies, I would have run out of foolscap before completing my task.
In critical response, I was an autobahn surrounded by country lanes, yet many of my classmates could read for uncritical comprehension faster than I could.
Dangerous skill.
(I'm sure for some of my old classmates, whatever dirt path once existed has returned to nature in their adult years, with ample fertilizer from mainstream media, but that's another matter.
)It's no different with source code.
You can read for comprehension, or you can read for all possible error, a state of mind where the eyes consume only a tiny fraction of total brain glucose.
Critical thought in the candy factory [youtube.com] is hard enough when the conveyor flows along at a consistent speed.
Neither can I properly type a long sequence of i and l characters worth a damn in a proportional font.
My eyes fail to sync with my fingers, and half the letters fall down my shirt.Nothing impairs reading speed like a tightly written algorithm where every symbol is exactly right.
Nothing inflates the volume of symbols violently gouged onto the retina as a chunk of code where no symbol means precisely what it seems to mean.Personally, I'm not lining up for smaller gouges in greater number.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797664</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797744</id>
	<title>Vertical alignment</title>
	<author>Skapare</author>
	<datestamp>1263738540000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>2</modscore>
	<htmltext><p>I'm not willing to give up on vertical alignment.  And lots of code sections I've written, in addition to ascii-art comments to explain lots of code, really needs that vertical alignment.  And that's not just leading alignment, it is internal alignment.</p><p>This won't break Python's indentation based syntax because one should be using consistent indentation.  But many displays of proportional fonts will collapse multiple spaces into the space of one, and even Python becomes hard to read.</p><p>The solution is to have a proper display system that can do both proportional fonts AND controlled alignment at the same time, without mangling the code files themselves, for all active programming languages (and that's a LOT of them).  Inserting invisible alignment into the code is not an option unless we can teach every language parse to remove such alignment elements before parsing the code for what it is coded for.  Someone could do this with a new language I don't doubt.  But it remains to be seen if anyone can do it in general for all existing active languages.</p><p>Oh, and if you do come up with a solution and it just can't manage to achieve it with COBOL, I won't cry.  But it better work with assembly and microcode syntax.</p></htmltext>
<tokenext>I 'm not willing to give up on vertical alignment .
And lots of code sections I 've written , in addition to ascii-art comments to explain lots of code , really needs that vertical alignment .
And that 's not just leading alignment , it is internal alignment.This wo n't break Python 's indentation based syntax because one should be using consistent indentation .
But many displays of proportional fonts will collapse multiple spaces into the space of one , and even Python becomes hard to read.The solution is to have a proper display system that can do both proportional fonts AND controlled alignment at the same time , without mangling the code files themselves , for all active programming languages ( and that 's a LOT of them ) .
Inserting invisible alignment into the code is not an option unless we can teach every language parse to remove such alignment elements before parsing the code for what it is coded for .
Someone could do this with a new language I do n't doubt .
But it remains to be seen if anyone can do it in general for all existing active languages.Oh , and if you do come up with a solution and it just ca n't manage to achieve it with COBOL , I wo n't cry .
But it better work with assembly and microcode syntax .</tokentext>
<sentencetext>I'm not willing to give up on vertical alignment.
And lots of code sections I've written, in addition to ascii-art comments to explain lots of code, really needs that vertical alignment.
And that's not just leading alignment, it is internal alignment.This won't break Python's indentation based syntax because one should be using consistent indentation.
But many displays of proportional fonts will collapse multiple spaces into the space of one, and even Python becomes hard to read.The solution is to have a proper display system that can do both proportional fonts AND controlled alignment at the same time, without mangling the code files themselves, for all active programming languages (and that's a LOT of them).
Inserting invisible alignment into the code is not an option unless we can teach every language parse to remove such alignment elements before parsing the code for what it is coded for.
Someone could do this with a new language I don't doubt.
But it remains to be seen if anyone can do it in general for all existing active languages.Oh, and if you do come up with a solution and it just can't manage to achieve it with COBOL, I won't cry.
But it better work with assembly and microcode syntax.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30799070</id>
	<title>Re:fixed</title>
	<author>multipart/mixed</author>
	<datestamp>1263749880000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>No way! That's a terrible font!</p><p>I have been using -misc-fixed-medium-r-normal--15-140-75-75-C-90-ISO8859-1 since '97 or '98 and still be believe it to be far superior! Condensed is to skinny.<nobr> <wbr></nobr>:)</p><p>I suppose an upgrade to a Unicode font is due at some point, but I don't speak any languages which can't be represented with Latin-1.</p><p>As for colours, I like yellow on blue for paren-match, khaki on blue3 for for default face, and while for font-lock-keyword-face. Loosely borrowed from Borland's IDEs of the Turbo Pascal 5 era.</p></htmltext>
<tokenext>No way !
That 's a terrible font ! I have been using -misc-fixed-medium-r-normal--15-140-75-75-C-90-ISO8859-1 since '97 or '98 and still be believe it to be far superior !
Condensed is to skinny .
: ) I suppose an upgrade to a Unicode font is due at some point , but I do n't speak any languages which ca n't be represented with Latin-1.As for colours , I like yellow on blue for paren-match , khaki on blue3 for for default face , and while for font-lock-keyword-face .
Loosely borrowed from Borland 's IDEs of the Turbo Pascal 5 era .</tokentext>
<sentencetext>No way!
That's a terrible font!I have been using -misc-fixed-medium-r-normal--15-140-75-75-C-90-ISO8859-1 since '97 or '98 and still be believe it to be far superior!
Condensed is to skinny.
:)I suppose an upgrade to a Unicode font is due at some point, but I don't speak any languages which can't be represented with Latin-1.As for colours, I like yellow on blue for paren-match, khaki on blue3 for for default face, and while for font-lock-keyword-face.
Loosely borrowed from Borland's IDEs of the Turbo Pascal 5 era.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797606</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30800714</id>
	<title>Re:fixed</title>
	<author>Urkki</author>
	<datestamp>1263719760000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>As for TFA and using proportional fonts for programming, all I can say is that the author can't be doing a lot of unified diffs, or working with languages where the amount of indentation is significant (fortran, anyone?).  Hell, even doing a cut/paste becomes more difficult when some of the letters are much narrower.<br>And with most prop fonts, good luck seeing the difference between variables like ill, lil and il1, or B80, 8BO and B8&#216;, for that matter.</p></div><p>Indentation is only at the beginning of the line. So variable-width fonts are really no problem with either indentation or diffs.</p><p>However, for best results with variable width fonts, tabs for indentation is really the way to go. Well, they're that for all fonts, anyway. I mean, who got this amazingly stupid idea, that a certain <i>variable</i> (between programmers, styles, files and even contexts within single file, etc) number of spaces means one step of indentation? It even sounds crazy when you read that aloud.</p><p>Now I admit there are some annoying real world issues which make many lazy coders to seek excuses to keep using spaces, including but not limited to: legacy code uses them, can't change due to version control, 'less' doesn't display tab-indented code nicely, with tabs I can't force other coders to use same indentation as I use, I like to spend time aligning commas in different lines using spaces, I lost the manual of my tractor feed line printer so can't set tab stops and I'm too lazy to code a filter to run before printing...</p></div>
	</htmltext>
<tokenext>As for TFA and using proportional fonts for programming , all I can say is that the author ca n't be doing a lot of unified diffs , or working with languages where the amount of indentation is significant ( fortran , anyone ? ) .
Hell , even doing a cut/paste becomes more difficult when some of the letters are much narrower.And with most prop fonts , good luck seeing the difference between variables like ill , lil and il1 , or B80 , 8BO and B8   , for that matter.Indentation is only at the beginning of the line .
So variable-width fonts are really no problem with either indentation or diffs.However , for best results with variable width fonts , tabs for indentation is really the way to go .
Well , they 're that for all fonts , anyway .
I mean , who got this amazingly stupid idea , that a certain variable ( between programmers , styles , files and even contexts within single file , etc ) number of spaces means one step of indentation ?
It even sounds crazy when you read that aloud.Now I admit there are some annoying real world issues which make many lazy coders to seek excuses to keep using spaces , including but not limited to : legacy code uses them , ca n't change due to version control , 'less ' does n't display tab-indented code nicely , with tabs I ca n't force other coders to use same indentation as I use , I like to spend time aligning commas in different lines using spaces , I lost the manual of my tractor feed line printer so ca n't set tab stops and I 'm too lazy to code a filter to run before printing.. .</tokentext>
<sentencetext>As for TFA and using proportional fonts for programming, all I can say is that the author can't be doing a lot of unified diffs, or working with languages where the amount of indentation is significant (fortran, anyone?).
Hell, even doing a cut/paste becomes more difficult when some of the letters are much narrower.And with most prop fonts, good luck seeing the difference between variables like ill, lil and il1, or B80, 8BO and B8Ø, for that matter.Indentation is only at the beginning of the line.
So variable-width fonts are really no problem with either indentation or diffs.However, for best results with variable width fonts, tabs for indentation is really the way to go.
Well, they're that for all fonts, anyway.
I mean, who got this amazingly stupid idea, that a certain variable (between programmers, styles, files and even contexts within single file, etc) number of spaces means one step of indentation?
It even sounds crazy when you read that aloud.Now I admit there are some annoying real world issues which make many lazy coders to seek excuses to keep using spaces, including but not limited to: legacy code uses them, can't change due to version control, 'less' doesn't display tab-indented code nicely, with tabs I can't force other coders to use same indentation as I use, I like to spend time aligning commas in different lines using spaces, I lost the manual of my tractor feed line printer so can't set tab stops and I'm too lazy to code a filter to run before printing...
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797696</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30823336</id>
	<title>Re:Consolas</title>
	<author>BlindSpot</author>
	<datestamp>1263933420000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Ditto thumbs-up for Consolas.  I use it not just for coding but anywhere that a fixed-width font is called for (terminal windows, non-HTML email, etc.).  It's so nice to finally have a proportional font included on a Windows system that doesn't look like it's been scanned from a 1970s dot-matrix printer.</p></htmltext>
<tokenext>Ditto thumbs-up for Consolas .
I use it not just for coding but anywhere that a fixed-width font is called for ( terminal windows , non-HTML email , etc. ) .
It 's so nice to finally have a proportional font included on a Windows system that does n't look like it 's been scanned from a 1970s dot-matrix printer .</tokentext>
<sentencetext>Ditto thumbs-up for Consolas.
I use it not just for coding but anywhere that a fixed-width font is called for (terminal windows, non-HTML email, etc.).
It's so nice to finally have a proportional font included on a Windows system that doesn't look like it's been scanned from a 1970s dot-matrix printer.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797584</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797946</id>
	<title>Only if you don't use VIM</title>
	<author>tagattack</author>
	<datestamp>1263740400000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>5</modscore>
	<htmltext><p>VIM renders text-area as a grid.  This is compatible with column-area selection, and other features it supports which frankly I use nearly daily.  While I've honestly considered using proportional fonts &mdash; I've tried living without VIM, switching to Eclipse or IDEA for several months at a time to give the IDE experience a full opportunity.  Doesn't work for me, so neither will proportional fonts.</p><p>Besides there seem to be more reasons not to use proportional fonts than to use them:</p><ul><li> Lot's of people align assignments, this will look terrible.</li><li>Several formatting techniques (newline before curly bracket) depend on the width of whitespace.</li><li>Occasionally code contains tabular data which is easily formatted for digestibility using fixed-width fonts.</li><li>Occasionally, although rarely, comments may contain diagrams or ascii-art figures which would be rendered useless with proportional font.</li></ul><p>Reasons to use them:</p><ul> <li>You might be able to read the contents of your code up to 14\% faster, if you don't run into the issues above...</li></ul></htmltext>
<tokenext>VIM renders text-area as a grid .
This is compatible with column-area selection , and other features it supports which frankly I use nearly daily .
While I 've honestly considered using proportional fonts    I 've tried living without VIM , switching to Eclipse or IDEA for several months at a time to give the IDE experience a full opportunity .
Does n't work for me , so neither will proportional fonts.Besides there seem to be more reasons not to use proportional fonts than to use them : Lot 's of people align assignments , this will look terrible.Several formatting techniques ( newline before curly bracket ) depend on the width of whitespace.Occasionally code contains tabular data which is easily formatted for digestibility using fixed-width fonts.Occasionally , although rarely , comments may contain diagrams or ascii-art figures which would be rendered useless with proportional font.Reasons to use them : You might be able to read the contents of your code up to 14 \ % faster , if you do n't run into the issues above.. .</tokentext>
<sentencetext>VIM renders text-area as a grid.
This is compatible with column-area selection, and other features it supports which frankly I use nearly daily.
While I've honestly considered using proportional fonts — I've tried living without VIM, switching to Eclipse or IDEA for several months at a time to give the IDE experience a full opportunity.
Doesn't work for me, so neither will proportional fonts.Besides there seem to be more reasons not to use proportional fonts than to use them: Lot's of people align assignments, this will look terrible.Several formatting techniques (newline before curly bracket) depend on the width of whitespace.Occasionally code contains tabular data which is easily formatted for digestibility using fixed-width fonts.Occasionally, although rarely, comments may contain diagrams or ascii-art figures which would be rendered useless with proportional font.Reasons to use them: You might be able to read the contents of your code up to 14\% faster, if you don't run into the issues above...</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30799660</id>
	<title>Geneva 9</title>
	<author>azav</author>
	<datestamp>1263754800000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I used Geneva 9 point for the longest time for the proper spacing between the letters.  I never had any compelling need to use a monospaced font to program since I was offered an alternative.</p></htmltext>
<tokenext>I used Geneva 9 point for the longest time for the proper spacing between the letters .
I never had any compelling need to use a monospaced font to program since I was offered an alternative .</tokentext>
<sentencetext>I used Geneva 9 point for the longest time for the proper spacing between the letters.
I never had any compelling need to use a monospaced font to program since I was offered an alternative.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30802144</id>
	<title>Re:Overrated</title>
	<author>Darinbob</author>
	<datestamp>1263729360000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>The problem with this idea is that it requires the editors to handle the work of aligning things, thus everyone who reads your code needs an editor that handles this feature the same way that your editor did.  This is great stuff if you are the only one who sees your code, ever.  But when someone tries to display it in a terminal window, in a source code control browser, in a diff program, or tries to print it, the alignment will be wrong.  Yes, it is important that the programmers read their own writing but that is only half the fight - nearly as important is for other people to be able to read what they wrote!</htmltext>
<tokenext>The problem with this idea is that it requires the editors to handle the work of aligning things , thus everyone who reads your code needs an editor that handles this feature the same way that your editor did .
This is great stuff if you are the only one who sees your code , ever .
But when someone tries to display it in a terminal window , in a source code control browser , in a diff program , or tries to print it , the alignment will be wrong .
Yes , it is important that the programmers read their own writing but that is only half the fight - nearly as important is for other people to be able to read what they wrote !</tokentext>
<sentencetext>The problem with this idea is that it requires the editors to handle the work of aligning things, thus everyone who reads your code needs an editor that handles this feature the same way that your editor did.
This is great stuff if you are the only one who sees your code, ever.
But when someone tries to display it in a terminal window, in a source code control browser, in a diff program, or tries to print it, the alignment will be wrong.
Yes, it is important that the programmers read their own writing but that is only half the fight - nearly as important is for other people to be able to read what they wrote!</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30798022</parent>
</comment>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_17_0715219_51</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797572
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30798296
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30799554
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_17_0715219_42</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797584
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30823336
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_17_0715219_0</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797572
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30798022
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30799686
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30800264
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_17_0715219_16</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797618
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30800232
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_17_0715219_76</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797874
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30798862
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_17_0715219_15</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797554
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797608
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30798084
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_17_0715219_81</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797554
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797608
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30799654
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_17_0715219_67</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797630
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797978
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_17_0715219_43</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797572
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30798022
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30802974
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_17_0715219_71</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797634
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30798058
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_17_0715219_45</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797550
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30805654
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_17_0715219_50</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797584
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797858
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_17_0715219_6</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797572
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30798366
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30800394
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_17_0715219_21</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797664
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30798478
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30808036
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_17_0715219_64</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797572
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30798022
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30802144
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_17_0715219_35</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797680
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797958
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_17_0715219_40</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797606
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30805860
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_17_0715219_69</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797664
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30798074
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_17_0715219_14</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797572
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30798296
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30799628
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_17_0715219_88</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797606
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30798712
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_17_0715219_70</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797572
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30798366
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30799384
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_17_0715219_65</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797572
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30798022
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30802912
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_17_0715219_56</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797606
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30799310
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_17_0715219_27</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797572
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30798366
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30803634
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_17_0715219_32</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797606
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797696
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30800714
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_17_0715219_55</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797606
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30800288
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_17_0715219_34</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797618
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30801284
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_17_0715219_57</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797946
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30806584
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_17_0715219_4</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797572
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30798022
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30799686
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30803768
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_17_0715219_62</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797664
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30798478
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30801788
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_17_0715219_33</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797634
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30798660
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_17_0715219_24</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797740
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30798798
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_17_0715219_19</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797634
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30798926
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_17_0715219_85</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797606
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30800676
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_17_0715219_75</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797590
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30803982
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_17_0715219_20</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797680
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30798316
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_17_0715219_49</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797874
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30800324
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_17_0715219_91</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797822
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30798516
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_17_0715219_54</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797740
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30822864
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_17_0715219_82</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797688
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30798432
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_17_0715219_25</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30798326
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30806616
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_17_0715219_68</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797584
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30798254
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_17_0715219_1</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797874
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30815040
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_17_0715219_39</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797550
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30799488
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_17_0715219_44</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797572
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30798296
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30799306
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30803550
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_17_0715219_18</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797816
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30799520
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_17_0715219_46</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797816
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30799866
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_17_0715219_22</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797630
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30799020
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_17_0715219_83</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797554
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797710
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_17_0715219_74</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797572
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30798366
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30799344
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_17_0715219_13</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797634
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30799914
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_17_0715219_90</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797572
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30798022
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30799686
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30813134
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_17_0715219_73</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797572
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30799330
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_17_0715219_9</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797630
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30798092
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_17_0715219_47</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797572
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30798022
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30799686
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30801556
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_17_0715219_38</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797572
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30798296
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30801996
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_17_0715219_8</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797606
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30799070
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_17_0715219_80</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797554
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797608
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30801922
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_17_0715219_41</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797664
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30798708
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_17_0715219_66</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797634
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30798620
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_17_0715219_37</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797816
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30802660
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_17_0715219_28</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797572
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30798296
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30799306
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30823198
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_17_0715219_31</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797606
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797696
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30800398
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_17_0715219_89</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797606
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797696
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30798056
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_17_0715219_79</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797590
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30798460
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_17_0715219_12</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797630
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797974
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_17_0715219_72</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797572
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30798296
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30800114
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_17_0715219_11</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797554
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797802
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_17_0715219_86</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797554
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30801900
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_17_0715219_29</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797572
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30798296
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30799306
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30802822
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_17_0715219_5</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797664
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30798174
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_17_0715219_7</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797946
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30805170
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_17_0715219_63</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797572
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30798366
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30806022
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_17_0715219_36</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797572
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30798098
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_17_0715219_59</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797584
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30801400
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_17_0715219_30</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797584
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797902
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_17_0715219_53</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797572
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30799030
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_17_0715219_26</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797584
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30802136
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_17_0715219_2</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797572
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30798296
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30799306
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30852682
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_17_0715219_87</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797572
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30798022
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30799686
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30800336
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30814900
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_17_0715219_60</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797618
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30801932
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30822322
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_17_0715219_78</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797554
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30799474
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_17_0715219_17</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797680
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30798068
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_17_0715219_77</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797590
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30802920
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_17_0715219_10</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797572
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30800476
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_17_0715219_84</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797572
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30798022
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30803666
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_17_0715219_3</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797572
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30799248
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30799960
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_17_0715219_58</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797572
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30798022
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30799686
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30800336
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30811780
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_17_0715219_61</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797572
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30798296
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30801610
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_17_0715219_52</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797584
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30801098
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_17_0715219_23</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797808
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30799822
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_17_0715219_48</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797584
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797862
</commentlist>
</thread>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_17_0715219.23</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797634
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30799914
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30798926
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30798660
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30798620
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30798058
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_17_0715219.29</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797744
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_17_0715219.3</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797874
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30815040
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30800324
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30798862
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_17_0715219.6</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797550
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30805654
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30799488
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_17_0715219.32</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797554
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797710
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797608
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30798084
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30799654
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30801922
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797802
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30801900
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30799474
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_17_0715219.0</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797808
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30799822
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_17_0715219.9</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797680
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30798068
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30798316
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797958
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_17_0715219.14</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797606
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30800288
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30800676
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30799310
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30798712
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30799070
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30805860
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797696
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30800398
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30800714
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30798056
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_17_0715219.35</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797822
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30798516
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_17_0715219.11</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30808746
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_17_0715219.24</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797776
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_17_0715219.17</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797816
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30799520
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30802660
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30799866
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_17_0715219.25</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797844
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_17_0715219.5</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30799892
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_17_0715219.34</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797590
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30798460
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30802920
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30803982
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_17_0715219.2</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797720
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_17_0715219.10</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30799224
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_17_0715219.31</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30800646
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_17_0715219.13</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797618
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30801284
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30800232
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30801932
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30822322
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_17_0715219.26</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30799698
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_17_0715219.20</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30802260
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_17_0715219.16</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797778
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_17_0715219.19</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797688
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30798432
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_17_0715219.21</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797946
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30806584
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30805170
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_17_0715219.27</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797584
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30802136
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797902
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30798254
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797858
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30801098
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30823336
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797862
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30801400
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_17_0715219.7</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797548
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_17_0715219.1</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30798486
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_17_0715219.4</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797630
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30798092
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30799020
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797974
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797978
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_17_0715219.12</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30799326
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_17_0715219.33</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797572
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30799248
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30799960
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30800476
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30798022
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30802912
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30803666
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30802144
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30802974
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30799686
---http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30801556
---http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30800336
----http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30814900
----http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30811780
---http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30803768
---http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30800264
---http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30813134
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30798366
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30799344
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30803634
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30806022
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30800394
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30799384
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30798098
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30798296
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30799554
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30799306
---http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30823198
---http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30852682
---http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30802822
---http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30803550
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30799628
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30800114
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30801996
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30801610
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30799030
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30799330
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_17_0715219.22</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30798326
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30806616
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_17_0715219.18</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797658
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_17_0715219.30</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797824
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_17_0715219.15</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797748
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_17_0715219.28</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797664
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30798174
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30798478
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30808036
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30801788
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30798708
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30798074
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_17_0715219.8</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30797740
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30798798
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_17_0715219.30822864
</commentlist>
</conversation>
