<?xml version="1.0" encoding="utf-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: The dylanchords.com guide: &#8220;How to use Word without hurting Heiner&#8217;s  eyes&#8221;</title>
	<atom:link href="http://oestrem.com/thingstwice/2005/09/the-dylanchordscom-guide-how-to-use-word-without-hurting-heiners-eyes/feed/" rel="self" type="application/rss+xml" />
	<link>http://oestrem.com/thingstwice/2005/09/the-dylanchordscom-guide-how-to-use-word-without-hurting-heiners-eyes/</link>
	<description>Eyolf Østrem on Dylan, Computers, and then some</description>
	<lastBuildDate>Sat, 13 Mar 2010 09:38:12 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Eyolf Østrem</title>
		<link>http://oestrem.com/thingstwice/2005/09/the-dylanchordscom-guide-how-to-use-word-without-hurting-heiners-eyes/comment-page-1/#comment-50417</link>
		<dc:creator>Eyolf Østrem</dc:creator>
		<pubDate>Mon, 08 Mar 2010 22:27:44 +0000</pubDate>
		<guid isPermaLink="false">http://oestrem.com/thingstwice/?p=37#comment-50417</guid>
		<description>You&#039;re right: there is one -- and one only -- exception to the &quot;never&quot; and that is italics. No, that&#039;s not true: there are other cases as well: small-caps, occasionally boldface, and even a change of typeface is permissible if one know what one is doing. 
My point is that not the one should not use formatting, but that (1) it should be used meaningfully and (2) consistently, which means that it should be applied through styles and not as direct formatting. With styles, one can define a certain set or formatting commands for a particular kind of content; with direct formatting, one can certainly achieve the same effect, but only through a much more inefficient path (by applying the same set of manual formatting to every instance, instead of defining all the relevant text pieces as instances of the same kind once and for all), and with a much greater risk of error/inconsistency.
The one exception, as I mentioned, is italics. I could write another post on this subject, but to make it short, this is one of the points where I disagree with the dogma &quot;separate style from contents&quot;. Because of the 500+ years&#039; tradition of mixing the regular font with a corresponding italic font (originally not even necessarily belonging to the same typeface), I would argue that I&#039;m not simply asking for &quot;emphasis&quot; -- which in principle can be defined as any alteration of the text presentation -- but specifically and emphatically for &quot;italics&quot;. Italics is not just any kind of emphasis, but a particular kind of emphasis which carries a lot of associations and expectations which apply to specific situations: titles of books/works, emphasised words, phrases in foreign languages, epigraphs, certain paragraphs that should stand out from the text flow, etc. To call all these cases &quot;emphasis&quot; would be wrong. Ideally one might define different styles for each of these cases, and then set all of them to &quot;italics&quot;, but in any less ideal world (e.g. a practical world), I prefer to use plain italics. 
That is half the reason why I use \textit and not \emph. The other half is that, for some reason which I don&#039;t fully remember, 
&lt;code&gt;\emph{if})&lt;/code&gt;
will not prevent the &quot;f&quot; from crossing the parenthesis, while 
&lt;code&gt;\textit{if})&lt;/code&gt;
will.</description>
		<content:encoded><![CDATA[<p>You&#8217;re right: there is one &#8212; and one only &#8212; exception to the &#8220;never&#8221; and that is italics. No, that&#8217;s not true: there are other cases as well: small-caps, occasionally boldface, and even a change of typeface is permissible if one know what one is doing.<br />
My point is that not the one should not use formatting, but that (1) it should be used meaningfully and (2) consistently, which means that it should be applied through styles and not as direct formatting. With styles, one can define a certain set or formatting commands for a particular kind of content; with direct formatting, one can certainly achieve the same effect, but only through a much more inefficient path (by applying the same set of manual formatting to every instance, instead of defining all the relevant text pieces as instances of the same kind once and for all), and with a much greater risk of error/inconsistency.<br />
The one exception, as I mentioned, is italics. I could write another post on this subject, but to make it short, this is one of the points where I disagree with the dogma &#8220;separate style from contents&#8221;. Because of the 500+ years&#8217; tradition of mixing the regular font with a corresponding italic font (originally not even necessarily belonging to the same typeface), I would argue that I&#8217;m not simply asking for &#8220;emphasis&#8221; &#8212; which in principle can be defined as any alteration of the text presentation &#8212; but specifically and emphatically for &#8220;italics&#8221;. Italics is not just any kind of emphasis, but a particular kind of emphasis which carries a lot of associations and expectations which apply to specific situations: titles of books/works, emphasised words, phrases in foreign languages, epigraphs, certain paragraphs that should stand out from the text flow, etc. To call all these cases &#8220;emphasis&#8221; would be wrong. Ideally one might define different styles for each of these cases, and then set all of them to &#8220;italics&#8221;, but in any less ideal world (e.g. a practical world), I prefer to use plain italics.<br />
That is half the reason why I use \textit and not \emph. The other half is that, for some reason which I don&#8217;t fully remember,<br />
<code>\emph{if})</code><br />
will not prevent the &#8220;f&#8221; from crossing the parenthesis, while<br />
<code>\textit{if})</code><br />
will.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lex</title>
		<link>http://oestrem.com/thingstwice/2005/09/the-dylanchordscom-guide-how-to-use-word-without-hurting-heiners-eyes/comment-page-1/#comment-50415</link>
		<dc:creator>Lex</dc:creator>
		<pubDate>Mon, 08 Mar 2010 14:22:07 +0000</pubDate>
		<guid isPermaLink="false">http://oestrem.com/thingstwice/?p=37#comment-50415</guid>
		<description>in &quot;LaTeX vs. Word vs. Writer&quot; article i noticed you used \textit LaTeX command---which is, i suppose, an analogue of &quot;italic&quot; button on direct formatting toolbar in Word.

i propose that &quot;1. Never ever use direct formatting&quot; should be replaced by softer &quot;don&#039;t apply more than one direct formatting to single piece of text&quot;, like: you can make text bold or italic, but not bold and italic at the same time.

Or should one make &quot;emphasize&quot; style and use it?</description>
		<content:encoded><![CDATA[<p>in &#8220;LaTeX vs. Word vs. Writer&#8221; article i noticed you used \textit LaTeX command&#8212;which is, i suppose, an analogue of &#8220;italic&#8221; button on direct formatting toolbar in Word.</p>
<p>i propose that &#8220;1. Never ever use direct formatting&#8221; should be replaced by softer &#8220;don&#8217;t apply more than one direct formatting to single piece of text&#8221;, like: you can make text bold or italic, but not bold and italic at the same time.</p>
<p>Or should one make &#8220;emphasize&#8221; style and use it?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Twitter Trackbacks for things twice » Blog Archive » The dylanchords.com guide: “How to use Word without hurting Heiner’s eyes” [oestrem.com] on Topsy.com</title>
		<link>http://oestrem.com/thingstwice/2005/09/the-dylanchordscom-guide-how-to-use-word-without-hurting-heiners-eyes/comment-page-1/#comment-48960</link>
		<dc:creator>Twitter Trackbacks for things twice » Blog Archive » The dylanchords.com guide: “How to use Word without hurting Heiner’s eyes” [oestrem.com] on Topsy.com</dc:creator>
		<pubDate>Wed, 07 Oct 2009 00:10:50 +0000</pubDate>
		<guid isPermaLink="false">http://oestrem.com/thingstwice/?p=37#comment-48960</guid>
		<description>[...] things twice » Blog Archive » The dylanchords.com guide: “How to use Word without hurting Heiner...  oestrem.com/thingstwice/2005/09/the-dylanchordscom-guide-how-to-use-word-without-hurting-heiners-eyes &#8211; view page &#8211; cached  Upon general request, here’s my guide to proper use of MS Word: 1. Never ever use direct formatting. &#8212; From the page [...]</description>
		<content:encoded><![CDATA[<div style="background: #eee; border: 1px solid #999; padding: 1em;">
<p>[...] things twice » Blog Archive » The dylanchords.com guide: “How to use Word without hurting Heiner&#8230;  oestrem.com/thingstwice/2005/09/the-dylanchordscom-guide-how-to-use-word-without-hurting-heiners-eyes &ndash; view page &ndash; cached  Upon general request, here’s my guide to proper use of MS Word: 1. Never ever use direct formatting. &mdash; From the page [...]</p>
</div>
]]></content:encoded>
	</item>
	<item>
		<title>By: Iain Cheyne (icheyne) 's status on Tuesday, 06-Oct-09 21:19:39 UTC - Identi.ca</title>
		<link>http://oestrem.com/thingstwice/2005/09/the-dylanchordscom-guide-how-to-use-word-without-hurting-heiners-eyes/comment-page-1/#comment-48959</link>
		<dc:creator>Iain Cheyne (icheyne) 's status on Tuesday, 06-Oct-09 21:19:39 UTC - Identi.ca</dc:creator>
		<pubDate>Tue, 06 Oct 2009 21:19:50 +0000</pubDate>
		<guid isPermaLink="false">http://oestrem.com/thingstwice/?p=37#comment-48959</guid>
		<description>[...]  http://oestrem.com/thingstwice/2005/09/the-dylanchordscom-guide-how-to-use-word-without-hurting-hei...       a few seconds ago  from  choqoK [...]</description>
		<content:encoded><![CDATA[<div style="background: #eee; border: 1px solid #999; padding: 1em;">
<p>[...]  <a href="http://oestrem.com/thingstwice/2005/09/the-dylanchordscom-guide-how-to-use-word-without-hurting-hei.." rel="nofollow">http://oestrem.com/thingstwice/2005/09/the-dylanchordscom-guide-how-to-use-word-without-hurting-hei..</a>.       a few seconds ago  from  choqoK [...]</p>
</div>
]]></content:encoded>
	</item>
	<item>
		<title>By: Irfan Johanda</title>
		<link>http://oestrem.com/thingstwice/2005/09/the-dylanchordscom-guide-how-to-use-word-without-hurting-heiners-eyes/comment-page-1/#comment-42184</link>
		<dc:creator>Irfan Johanda</dc:creator>
		<pubDate>Tue, 25 Nov 2008 14:54:10 +0000</pubDate>
		<guid isPermaLink="false">http://oestrem.com/thingstwice/?p=37#comment-42184</guid>
		<description>Great Site!
BTW, I usually use Frutiger Linotype (getting it free and licensed from Microsoft Reader) for sans-serif type font.</description>
		<content:encoded><![CDATA[<p>Great Site!<br />
BTW, I usually use Frutiger Linotype (getting it free and licensed from Microsoft Reader) for sans-serif type font.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Riley</title>
		<link>http://oestrem.com/thingstwice/2005/09/the-dylanchordscom-guide-how-to-use-word-without-hurting-heiners-eyes/comment-page-1/#comment-40148</link>
		<dc:creator>Riley</dc:creator>
		<pubDate>Wed, 12 Sep 2007 00:14:40 +0000</pubDate>
		<guid isPermaLink="false">http://oestrem.com/thingstwice/?p=37#comment-40148</guid>
		<description>Exactly right -- the idea is to use named paragraph and character styles.  Stated in its convers form, avoid at all costs the ad hoc formatting of Word&#039;s *normal&quot; or *default* styles.

First, named styles allow one to ala CSS, update or revise all instances of that named style by simply changing the style name.

Second, it becomes much easier to convert a document from Word to some other format if specific types of content -- headings, bulleted lists, numbered lists, etc. -- are properly tagged.  Again, the converse is that everything is identified as &quot;normal&quot;, making it literally impossible to automate a conversion based on a style name / tag...</description>
		<content:encoded><![CDATA[<p>Exactly right &#8212; the idea is to use named paragraph and character styles.  Stated in its convers form, avoid at all costs the ad hoc formatting of Word&#8217;s *normal&#8221; or *default* styles.</p>
<p>First, named styles allow one to ala CSS, update or revise all instances of that named style by simply changing the style name.</p>
<p>Second, it becomes much easier to convert a document from Word to some other format if specific types of content &#8212; headings, bulleted lists, numbered lists, etc. &#8212; are properly tagged.  Again, the converse is that everything is identified as &#8220;normal&#8221;, making it literally impossible to automate a conversion based on a style name / tag&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Heiner</title>
		<link>http://oestrem.com/thingstwice/2005/09/the-dylanchordscom-guide-how-to-use-word-without-hurting-heiners-eyes/comment-page-1/#comment-980</link>
		<dc:creator>Heiner</dc:creator>
		<pubDate>Thu, 01 Dec 2005 15:46:58 +0000</pubDate>
		<guid isPermaLink="false">http://oestrem.com/thingstwice/?p=37#comment-980</guid>
		<description>Hi. I&#039;m a student of mathematics and care a bit about fonts and layouts. My advice is:
(1) Use (La)TeX if you want your document to look good. Nothing beats it when it comes to typesetting formulae, and for the rest it is as good as any &quot;desktop publishing&quot; program, if you put enough effort into it.
(2) If you want it easy and &quot;need&quot; &lt;a href=&quot;http://en.wikipedia.org/wiki/WYSIWYG&quot; rel=&quot;nofollow&quot;&gt;WYSIWYG&lt;/a&gt;, TeX is not the right think for you. Even with &lt;a href=&quot;http://www.lyx.org&quot; rel=&quot;nofollow&quot;&gt;LyX&lt;/a&gt; it is nowhere as easy as Word, nor as stupid. 
For more infomation, search the web, there&#039;s plenty around. Wikipedia is a good start. [BTW: As you noticed, Wikipedia creates screenshots of TeX&#039;s output to display a formula-image.]</description>
		<content:encoded><![CDATA[<p>Hi. I&#8217;m a student of mathematics and care a bit about fonts and layouts. My advice is:<br />
(1) Use (La)TeX if you want your document to look good. Nothing beats it when it comes to typesetting formulae, and for the rest it is as good as any &#8220;desktop publishing&#8221; program, if you put enough effort into it.<br />
(2) If you want it easy and &#8220;need&#8221; <a href="http://en.wikipedia.org/wiki/WYSIWYG" rel="nofollow">WYSIWYG</a>, TeX is not the right think for you. Even with <a href="http://www.lyx.org" rel="nofollow">LyX</a> it is nowhere as easy as Word, nor as stupid.<br />
For more infomation, search the web, there&#8217;s plenty around. Wikipedia is a good start. [BTW: As you noticed, Wikipedia creates screenshots of TeX's output to display a formula-image.]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Peter</title>
		<link>http://oestrem.com/thingstwice/2005/09/the-dylanchordscom-guide-how-to-use-word-without-hurting-heiners-eyes/comment-page-1/#comment-977</link>
		<dc:creator>Peter</dc:creator>
		<pubDate>Tue, 29 Nov 2005 13:00:01 +0000</pubDate>
		<guid isPermaLink="false">http://oestrem.com/thingstwice/?p=37#comment-977</guid>
		<description>These typography entries (and the links contained therein) are great. I need to write quite a few formal-style documents (scientific reports - I&#039;m a physics student), and I&#039;ve been getting sick of Times New Roman and Arial, but never knew what to use instead. I like to think I have enough of an eye for design that my page layout is straightforward and easy to read, but typefaces have always been a bit mystifying to me.

In fact, I hadn&#039;t even looked closely at my documents until I read these articles, always assuming that the words are most important, then the layout, and finally the font. After printing out all my old lab reports again and looking over them, I realised that I could definitely make my work look a little neater and prettier just by changing typefaces.

Thanks to these pages I&#039;ve settled on Gentium for my general-purpose font, since it&#039;s close enough to Times to still look professional to a type-blind academic, but sufficiently different to help individuate my report from the dozens that the tutors will be reading. Plus there&#039;s the obvious advantage in that it doesn&#039;t look quite as sterile after having been seen in millions of characters before reaching mine.

My standard sans-serif font is now Tahoma, but I&#039;m not sure about it. Trebuchet MS is quite nice, but a bit too wide, and Verdana&#039;s default spacing makes it appear a bit too wide when bold (great for screen, but on paper it&#039;s not so good). Arial definitely looks worse, but it&#039;s harder for me to decide what should replace it because there simply isn&#039;t much sans-serif stuff in my documents - a couple of section headers and diagram labels are the only instances.

I guess I also want to say thanks for opening my eyes (if only slightly), and to ask what you and the readers of these pages recommend as a professional-looking sans-serif font. Something with the same production ethos as Gentium would be fantastic (from a less-than-aesthetic point of view), but I really don&#039;t know what to look for.

My last problem is slightly more specific. Thanks to the wonders of physics, I have to include a fair amount of Greek characters and mathematical formatting. So far I&#039;ve been using Microsoft&#039;s Equation Editor to embed the formulae in my Word documents, and without any real troubles. Part of the reason I chose Gentium was the fact that it includes Greek characters, so I&#039;d like to be able to change the Equation Editor&#039;s font to use that as the default. Does anyone have any ideas? I just can&#039;t fathom the minimal interface to the editor, and I&#039;d like to avoid shelling out for MathType (although I suppose I could always &#039;acquire&#039; it).

Is TeX a suitable alternative? I keep seeing references to it, and I think they use something similar to achieve equation formatting on Wikipedia, which looks okay. If anyone can offer a suggestion on how best to use it (if at all) I&#039;d be grateful - should it be for my entire documents, or just the equations? If the former, what do I use to edit/style the document? If the latter, how do I import the formatted equation into Word?

Thanks.</description>
		<content:encoded><![CDATA[<p>These typography entries (and the links contained therein) are great. I need to write quite a few formal-style documents (scientific reports &#8211; I&#8217;m a physics student), and I&#8217;ve been getting sick of Times New Roman and Arial, but never knew what to use instead. I like to think I have enough of an eye for design that my page layout is straightforward and easy to read, but typefaces have always been a bit mystifying to me.</p>
<p>In fact, I hadn&#8217;t even looked closely at my documents until I read these articles, always assuming that the words are most important, then the layout, and finally the font. After printing out all my old lab reports again and looking over them, I realised that I could definitely make my work look a little neater and prettier just by changing typefaces.</p>
<p>Thanks to these pages I&#8217;ve settled on Gentium for my general-purpose font, since it&#8217;s close enough to Times to still look professional to a type-blind academic, but sufficiently different to help individuate my report from the dozens that the tutors will be reading. Plus there&#8217;s the obvious advantage in that it doesn&#8217;t look quite as sterile after having been seen in millions of characters before reaching mine.</p>
<p>My standard sans-serif font is now Tahoma, but I&#8217;m not sure about it. Trebuchet MS is quite nice, but a bit too wide, and Verdana&#8217;s default spacing makes it appear a bit too wide when bold (great for screen, but on paper it&#8217;s not so good). Arial definitely looks worse, but it&#8217;s harder for me to decide what should replace it because there simply isn&#8217;t much sans-serif stuff in my documents &#8211; a couple of section headers and diagram labels are the only instances.</p>
<p>I guess I also want to say thanks for opening my eyes (if only slightly), and to ask what you and the readers of these pages recommend as a professional-looking sans-serif font. Something with the same production ethos as Gentium would be fantastic (from a less-than-aesthetic point of view), but I really don&#8217;t know what to look for.</p>
<p>My last problem is slightly more specific. Thanks to the wonders of physics, I have to include a fair amount of Greek characters and mathematical formatting. So far I&#8217;ve been using Microsoft&#8217;s Equation Editor to embed the formulae in my Word documents, and without any real troubles. Part of the reason I chose Gentium was the fact that it includes Greek characters, so I&#8217;d like to be able to change the Equation Editor&#8217;s font to use that as the default. Does anyone have any ideas? I just can&#8217;t fathom the minimal interface to the editor, and I&#8217;d like to avoid shelling out for MathType (although I suppose I could always &#8216;acquire&#8217; it).</p>
<p>Is TeX a suitable alternative? I keep seeing references to it, and I think they use something similar to achieve equation formatting on Wikipedia, which looks okay. If anyone can offer a suggestion on how best to use it (if at all) I&#8217;d be grateful &#8211; should it be for my entire documents, or just the equations? If the former, what do I use to edit/style the document? If the latter, how do I import the formatted equation into Word?</p>
<p>Thanks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Richard J</title>
		<link>http://oestrem.com/thingstwice/2005/09/the-dylanchordscom-guide-how-to-use-word-without-hurting-heiners-eyes/comment-page-1/#comment-864</link>
		<dc:creator>Richard J</dc:creator>
		<pubDate>Fri, 11 Nov 2005 07:59:30 +0000</pubDate>
		<guid isPermaLink="false">http://oestrem.com/thingstwice/?p=37#comment-864</guid>
		<description>Well...one thing that hurts MY eyes (and brain) more than a shoddy font: right- AND left justification of text...jeez, I hate it when Word tries to do what typographers spent a lifetime learning. /Rick</description>
		<content:encoded><![CDATA[<div style="background: #eee; border: 1px solid #999; padding: 1em;">
<p>Well&#8230;one thing that hurts MY eyes (and brain) more than a shoddy font: right- AND left justification of text&#8230;jeez, I hate it when Word tries to do what typographers spent a lifetime learning. /Rick</p>
</div>
]]></content:encoded>
	</item>
	<item>
		<title>By: stevietheb</title>
		<link>http://oestrem.com/thingstwice/2005/09/the-dylanchordscom-guide-how-to-use-word-without-hurting-heiners-eyes/comment-page-1/#comment-701</link>
		<dc:creator>stevietheb</dc:creator>
		<pubDate>Wed, 26 Oct 2005 13:25:43 +0000</pubDate>
		<guid isPermaLink="false">http://oestrem.com/thingstwice/?p=37#comment-701</guid>
		<description>For those on Mac, I strongly suggest using &lt;a href=&quot;http://www.mellel.com&quot; rel=&quot;nofollow&quot;&gt;Mellel&lt;/a&gt; rather than Word. Mellel handles non-English languages better than Word for Mac (particularly Hebrew which is totally screwed up on Mac because Microsoft won&#039;t take the time to fix it). Mellel + a good unicode font is a dream to use for those who have to use languages with different character sets. Also, Mellel forces your hand and really encourages you to use Styles—which seems to be the main concern of this article. Unfortunately, Mellel is still in its early stages, so some of the more advanced features of Word it can&#039;t match—but I tend to do my own tables of contents and indexing and whatnot anyway.</description>
		<content:encoded><![CDATA[<div style="background: #eee; border: 1px solid #999; padding: 1em;">
<p>For those on Mac, I strongly suggest using <a href="http://www.mellel.com" rel="nofollow">Mellel</a> rather than Word. Mellel handles non-English languages better than Word for Mac (particularly Hebrew which is totally screwed up on Mac because Microsoft won&#8217;t take the time to fix it). Mellel + a good unicode font is a dream to use for those who have to use languages with different character sets. Also, Mellel forces your hand and really encourages you to use Styles—which seems to be the main concern of this article. Unfortunately, Mellel is still in its early stages, so some of the more advanced features of Word it can&#8217;t match—but I tend to do my own tables of contents and indexing and whatnot anyway.</p>
</div>
]]></content:encoded>
	</item>
	<item>
		<title>By: Heiner</title>
		<link>http://oestrem.com/thingstwice/2005/09/the-dylanchordscom-guide-how-to-use-word-without-hurting-heiners-eyes/comment-page-1/#comment-631</link>
		<dc:creator>Heiner</dc:creator>
		<pubDate>Wed, 12 Oct 2005 17:19:23 +0000</pubDate>
		<guid isPermaLink="false">http://oestrem.com/thingstwice/?p=37#comment-631</guid>
		<description>There are not too many (TTF) fonts available for Linux, but you can import the Windows ones if you like. Good fonts need good artists, and those are mostly rare in the OpenSource world...</description>
		<content:encoded><![CDATA[<div style="background: #eee; border: 1px solid #999; padding: 1em;">
<p>There are not too many (TTF) fonts available for Linux, but you can import the Windows ones if you like. Good fonts need good artists, and those are mostly rare in the OpenSource world&#8230;</p>
</div>
]]></content:encoded>
	</item>
	<item>
		<title>By: g from nfld</title>
		<link>http://oestrem.com/thingstwice/2005/09/the-dylanchordscom-guide-how-to-use-word-without-hurting-heiners-eyes/comment-page-1/#comment-628</link>
		<dc:creator>g from nfld</dc:creator>
		<pubDate>Mon, 10 Oct 2005 01:24:51 +0000</pubDate>
		<guid isPermaLink="false">http://oestrem.com/thingstwice/?p=37#comment-628</guid>
		<description>i dont have a clue how to post a blog or any of that shit, but to the site owner, dylanchords,   man you really got your shit together, how do u get all this info?
cheers</description>
		<content:encoded><![CDATA[<p>i dont have a clue how to post a blog or any of that shit, but to the site owner, dylanchords,   man you really got your shit together, how do u get all this info?<br />
cheers</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: eyolf</title>
		<link>http://oestrem.com/thingstwice/2005/09/the-dylanchordscom-guide-how-to-use-word-without-hurting-heiners-eyes/comment-page-1/#comment-625</link>
		<dc:creator>eyolf</dc:creator>
		<pubDate>Sun, 09 Oct 2005 01:48:01 +0000</pubDate>
		<guid isPermaLink="false">http://oestrem.com/thingstwice/?p=37#comment-625</guid>
		<description>May I turn the question back to you: Are there any common alternatives to these fonts in the linux world? Is there a &quot;core&quot; set of fonts which most distros have, or is it hit and miss? I found URW Gothic L in my system, which is another Futura clone, and URW palladio L as a Palatino clone, sortof. What else is there? If one wants to avoid TNR and Arial, that is, and still stand a reasonable chance of getting the desired display even there?</description>
		<content:encoded><![CDATA[<p>May I turn the question back to you: Are there any common alternatives to these fonts in the linux world? Is there a &#8220;core&#8221; set of fonts which most distros have, or is it hit and miss? I found URW Gothic L in my system, which is another Futura clone, and URW palladio L as a Palatino clone, sortof. What else is there? If one wants to avoid TNR and Arial, that is, and still stand a reasonable chance of getting the desired display even there?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: J. David Black, Jr.</title>
		<link>http://oestrem.com/thingstwice/2005/09/the-dylanchordscom-guide-how-to-use-word-without-hurting-heiners-eyes/comment-page-1/#comment-611</link>
		<dc:creator>J. David Black, Jr.</dc:creator>
		<pubDate>Thu, 06 Oct 2005 17:55:24 +0000</pubDate>
		<guid isPermaLink="false">http://oestrem.com/thingstwice/?p=37#comment-611</guid>
		<description>When I type up guitar chords or tab, or if I&#039;m printing someone else&#039;s out, I typically line up the chord change with the syllable change that it falls on. This is easier with a font that has equal spacing for all characters. Which one would you suggest?
 So far, I&#039;ve been using Courier New or Lucida Console. Courier seems a little boxy, and the Lucida is a serif font that wishes it was sans-serif. 

I agree with your comment on Trebuchet, I like to use it for most other everyday purposes.</description>
		<content:encoded><![CDATA[<p>When I type up guitar chords or tab, or if I&#8217;m printing someone else&#8217;s out, I typically line up the chord change with the syllable change that it falls on. This is easier with a font that has equal spacing for all characters. Which one would you suggest?<br />
 So far, I&#8217;ve been using Courier New or Lucida Console. Courier seems a little boxy, and the Lucida is a serif font that wishes it was sans-serif. </p>
<p>I agree with your comment on Trebuchet, I like to use it for most other everyday purposes.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: a</title>
		<link>http://oestrem.com/thingstwice/2005/09/the-dylanchordscom-guide-how-to-use-word-without-hurting-heiners-eyes/comment-page-1/#comment-602</link>
		<dc:creator>a</dc:creator>
		<pubDate>Mon, 03 Oct 2005 01:22:51 +0000</pubDate>
		<guid isPermaLink="false">http://oestrem.com/thingstwice/?p=37#comment-602</guid>
		<description>Wow, so someone doesnt type an email in a peticular manner...I guess the world&#039;s gonna end.</description>
		<content:encoded><![CDATA[<p>Wow, so someone doesnt type an email in a peticular manner&#8230;I guess the world&#8217;s gonna end.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
