<?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"
	>
<channel>
	<title>Comments on: LaTeX and OSX</title>
	<atom:link href="http://theappleblog.com/2006/10/05/latex-and-osx/feed/" rel="self" type="application/rss+xml" />
	<link>http://theappleblog.com/2006/10/05/latex-and-osx/</link>
	<description>TheAppleBlog, published by and for the day-to-day Apple user, is a prominent source for news, reviews, walkthroughs, and real life application of all Apple products.</description>
	<pubDate>Fri, 05 Dec 2008 01:35:47 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>By: Slater</title>
		<link>http://theappleblog.com/2006/10/05/latex-and-osx/#comment-120026</link>
		<dc:creator>Slater</dc:creator>
		<pubDate>Mon, 01 Sep 2008 17:29:03 +0000</pubDate>
		<guid isPermaLink="false">http://theappleblog.com/2006/10/05/latex-and-osx/#comment-120026</guid>
		<description>I could answer a lot of these questions, but better yet, we have a wiki!
http://mactex-wiki.tug.org
The wiki goes beyond the mactex distribution, and is in fact run independently (by me). 

As for the "focusing on content" thing... provided style files exist, you don't see format so much as structure in the document. True, you may not like seeing the command \section, however, it has much more useful meaning to it than bold, slightly larger, and preceded by a number. 

A quality editor precludes many syntax errors by providing keystrokes that match braces, etc. Further, for the faint of heart, a "GUI interface to LaTeX" is available through LyX, which provides a more visual experience while retaining the power LaTeX provides.</description>
		<content:encoded><![CDATA[<p>I could answer a lot of these questions, but better yet, we have a wiki!<br />
<a href="http://mactex-wiki.tug.org" rel="nofollow">http://mactex-wiki.tug.org</a><br />
The wiki goes beyond the mactex distribution, and is in fact run independently (by me). </p>
<p>As for the &#8220;focusing on content&#8221; thing&#8230; provided style files exist, you don&#8217;t see format so much as structure in the document. True, you may not like seeing the command \section, however, it has much more useful meaning to it than bold, slightly larger, and preceded by a number. </p>
<p>A quality editor precludes many syntax errors by providing keystrokes that match braces, etc. Further, for the faint of heart, a &#8220;GUI interface to LaTeX&#8221; is available through LyX, which provides a more visual experience while retaining the power LaTeX provides.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James mortison</title>
		<link>http://theappleblog.com/2006/10/05/latex-and-osx/#comment-115187</link>
		<dc:creator>James mortison</dc:creator>
		<pubDate>Wed, 19 Mar 2008 06:58:09 +0000</pubDate>
		<guid isPermaLink="false">http://theappleblog.com/2006/10/05/latex-and-osx/#comment-115187</guid>
		<description>The thing about LateX letting you focus on the content -- I just don't understand that. Because it's far more distracting to have to type out the markup for bold or section heading than clicking one button in a word processor to apply that style. You spend more time typing and later debugging your LateX markup whereas in a word processor what you see is what you get... right?</description>
		<content:encoded><![CDATA[<p>The thing about LateX letting you focus on the content &#8212; I just don&#8217;t understand that. Because it&#8217;s far more distracting to have to type out the markup for bold or section heading than clicking one button in a word processor to apply that style. You spend more time typing and later debugging your LateX markup whereas in a word processor what you see is what you get&#8230; right?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: novice</title>
		<link>http://theappleblog.com/2006/10/05/latex-and-osx/#comment-105439</link>
		<dc:creator>novice</dc:creator>
		<pubDate>Sun, 13 May 2007 16:08:46 +0000</pubDate>
		<guid isPermaLink="false">http://theappleblog.com/2006/10/05/latex-and-osx/#comment-105439</guid>
		<description>Dear Blogger:

I recently downloaded your MacTex. While trying to typeset in TexShop, the program said that I was missing teTex or that I had the wrong path. As I would like to download MacTex - 2007, how do I uninstall the version from your page?

Thank you. I think you're doing a great job.

Best

Novice</description>
		<content:encoded><![CDATA[<p>Dear Blogger:</p>
<p>I recently downloaded your MacTex. While trying to typeset in TexShop, the program said that I was missing teTex or that I had the wrong path. As I would like to download MacTex - 2007, how do I uninstall the version from your page?</p>
<p>Thank you. I think you&#8217;re doing a great job.</p>
<p>Best</p>
<p>Novice</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Robert Felty</title>
		<link>http://theappleblog.com/2006/10/05/latex-and-osx/#comment-95701</link>
		<dc:creator>Robert Felty</dc:creator>
		<pubDate>Thu, 11 Jan 2007 20:06:12 +0000</pubDate>
		<guid isPermaLink="false">http://theappleblog.com/2006/10/05/latex-and-osx/#comment-95701</guid>
		<description>I also recently wrote a similar article, inspired by a really poorly written article that made it to the front page of &lt;a href='http://reddit.com' rel="nofollow"&gt;reddit.com&lt;/a&gt;. You can read &lt;a href='http://umich.edu/~robfelty/academic/whylatex.html' rel="nofollow"&gt;the article&lt;/a&gt; on my website. 

I also think that this was a fairly well written summary of the pros and cons of LaTeX. I do have one more suggestion for a very helpful LaTeX related tool. For those who use bibtex to handle their bibliographies, you should check out jabref. It is a bibtex organizer written in java. It has a very intuitive UI, and can import and export all sorts of bibliographic formats like Endnote, RIS, ISI etc. very easily.</description>
		<content:encoded><![CDATA[<p>I also recently wrote a similar article, inspired by a really poorly written article that made it to the front page of <a href='http://reddit.com' rel="nofollow">reddit.com</a>. You can read <a href='http://umich.edu/~robfelty/academic/whylatex.html' rel="nofollow">the article</a> on my website. </p>
<p>I also think that this was a fairly well written summary of the pros and cons of LaTeX. I do have one more suggestion for a very helpful LaTeX related tool. For those who use bibtex to handle their bibliographies, you should check out jabref. It is a bibtex organizer written in java. It has a very intuitive UI, and can import and export all sorts of bibliographic formats like Endnote, RIS, ISI etc. very easily.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dario</title>
		<link>http://theappleblog.com/2006/10/05/latex-and-osx/#comment-84039</link>
		<dc:creator>Dario</dc:creator>
		<pubDate>Mon, 11 Dec 2006 15:34:16 +0000</pubDate>
		<guid isPermaLink="false">http://theappleblog.com/2006/10/05/latex-and-osx/#comment-84039</guid>
		<description>For those interested in using the advanced features (ligatures, correct kerning tables, hyphenation, alternate glyphs, full Unicode support) of Mac OS fonts, &lt;strong&gt;&lt;a href="http://scripts.sil.org/xetex/" rel="nofollow"&gt;XeTeX&lt;/a&gt;&lt;/strong&gt; is a must. The possibility offered by XeTeX to create documents using OpenType technology is another—often understated—advantage of the LaTeX/Mac OS combination. Structured content and typographic accuracy is definitely what sets LaTeX apart from most word processors. A short article I wrote on this topic (with downloadable sources and a comparison with font rendering in MS Word) may be of interest to some of your readers:

&lt;strong&gt;&lt;a href="http://nitens.org/taraborelli/latex" rel="nofollow"&gt;The Beauty of LaTeX&lt;/a&gt;&lt;/strong&gt;</description>
		<content:encoded><![CDATA[<p>For those interested in using the advanced features (ligatures, correct kerning tables, hyphenation, alternate glyphs, full Unicode support) of Mac OS fonts, <strong><a href="http://scripts.sil.org/xetex/" rel="nofollow">XeTeX</a></strong> is a must. The possibility offered by XeTeX to create documents using OpenType technology is another—often understated—advantage of the LaTeX/Mac OS combination. Structured content and typographic accuracy is definitely what sets LaTeX apart from most word processors. A short article I wrote on this topic (with downloadable sources and a comparison with font rendering in MS Word) may be of interest to some of your readers:</p>
<p><strong><a href="http://nitens.org/taraborelli/latex" rel="nofollow">The Beauty of LaTeX</a></strong></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: the sum of my parts &#187; Blog Archive : Learning Laytex?? &#187; Learning Laytex??</title>
		<link>http://theappleblog.com/2006/10/05/latex-and-osx/#comment-77332</link>
		<dc:creator>the sum of my parts &#187; Blog Archive : Learning Laytex?? &#187; Learning Laytex??</dc:creator>
		<pubDate>Sat, 18 Nov 2006 22:04:57 +0000</pubDate>
		<guid isPermaLink="false">http://theappleblog.com/2006/10/05/latex-and-osx/#comment-77332</guid>
		<description>[...] The point of this post, however, was not to complain. I am actually looking for a bit of advice. I have just downloaded MacTex (a Laytex program) because I am supposed to use it somehow when I send in my next conference paper. Hmmm. It looks a wee bit complicated. I read some reviews on it and it seems that once you learn how, it is great for big projects (like a thesis, maybe?) and has a great bibliography thing too. So, my question&#8230; do I spend the time trying to figure it out? Is the program worth it? Or do I stick to Word and spend more time working on a bibliography??? And if I spend time learning this and use it for my thesis, will the printers even except it (good thing to find out first). Any suggestions? Tips? Reviews? [...]</description>
		<content:encoded><![CDATA[<p>[...] The point of this post, however, was not to complain. I am actually looking for a bit of advice. I have just downloaded MacTex (a Laytex program) because I am supposed to use it somehow when I send in my next conference paper. Hmmm. It looks a wee bit complicated. I read some reviews on it and it seems that once you learn how, it is great for big projects (like a thesis, maybe?) and has a great bibliography thing too. So, my question&#8230; do I spend the time trying to figure it out? Is the program worth it? Or do I stick to Word and spend more time working on a bibliography??? And if I spend time learning this and use it for my thesis, will the printers even except it (good thing to find out first). Any suggestions? Tips? Reviews? [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stephen Laughton</title>
		<link>http://theappleblog.com/2006/10/05/latex-and-osx/#comment-68578</link>
		<dc:creator>Stephen Laughton</dc:creator>
		<pubDate>Sat, 14 Oct 2006 15:46:08 +0000</pubDate>
		<guid isPermaLink="false">http://theappleblog.com/2006/10/05/latex-and-osx/#comment-68578</guid>
		<description>There is also the Oztex suite of programs by Andrew Trevorrow which I've used for many years.http://www.trevorrow.com/oztex/index.html</description>
		<content:encoded><![CDATA[<p>There is also the Oztex suite of programs by Andrew Trevorrow which I&#8217;ve used for many years.http://www.trevorrow.com/oztex/index.html</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: james dear</title>
		<link>http://theappleblog.com/2006/10/05/latex-and-osx/#comment-66906</link>
		<dc:creator>james dear</dc:creator>
		<pubDate>Sun, 08 Oct 2006 07:52:16 +0000</pubDate>
		<guid isPermaLink="false">http://theappleblog.com/2006/10/05/latex-and-osx/#comment-66906</guid>
		<description>The main problem with LaTeX (and I've been using it for over 7 years now), is ... the so-called "(professional) publishers". Rarely can I submit for a journal or other publication files in TEX.

And why do all these journals have their own typesetting preferences? It would indeed be easier if academics could focus on the content - and let LaTeX take care of the form. But more often than not, I spend days tweaking LaTeX or making Stylesheets to fit the requests of a publisher who thinks that his stylesheet is the best. If they would show a more professional attitude, they could provide free .sty files to make LaTeX work effortlessly with their own stylesheet requirements. But more often than not, they don't provide any templates.

So far, I have collected stylesheet with 8 different way to do headings and subheadings. That's really truly unprofessional. We have a tool that allows excellent type-setting, but it seems that publishers are not too keen to make us use it.</description>
		<content:encoded><![CDATA[<p>The main problem with LaTeX (and I&#8217;ve been using it for over 7 years now), is &#8230; the so-called &#8220;(professional) publishers&#8221;. Rarely can I submit for a journal or other publication files in TEX.</p>
<p>And why do all these journals have their own typesetting preferences? It would indeed be easier if academics could focus on the content - and let LaTeX take care of the form. But more often than not, I spend days tweaking LaTeX or making Stylesheets to fit the requests of a publisher who thinks that his stylesheet is the best. If they would show a more professional attitude, they could provide free .sty files to make LaTeX work effortlessly with their own stylesheet requirements. But more often than not, they don&#8217;t provide any templates.</p>
<p>So far, I have collected stylesheet with 8 different way to do headings and subheadings. That&#8217;s really truly unprofessional. We have a tool that allows excellent type-setting, but it seems that publishers are not too keen to make us use it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kamen</title>
		<link>http://theappleblog.com/2006/10/05/latex-and-osx/#comment-66649</link>
		<dc:creator>Kamen</dc:creator>
		<pubDate>Fri, 06 Oct 2006 11:46:03 +0000</pubDate>
		<guid isPermaLink="false">http://theappleblog.com/2006/10/05/latex-and-osx/#comment-66649</guid>
		<description>Teekay,

You have a really good point here - but your argument is sligthly sollipsistic. I mean to say that the fact that M$ Word is the de facto business standard document format is the reason why most people would resort to it for data exchange. Otherwise, people would use a more stable data format. Such is life :-). But your point is good: what's my editor going to do with my lovely, hyper-linked, indexed and printer-ready pdf manuscript? 

Of course, Real Men (tm) would use cvs, or some other versioning system. For a programmer, nothing is easier than checking in a TeX source file into cvs. But writers need to write, not go for an IT degree, so this makes the accessibility of the system very hard indeed. (LyX 4.x incorporates change tracking, and it's very nice, but that ties you to the .lyx document format, which is hardly an improvement). 

I expect the current trend in web-based applications to eventually incorporate concurrent version tracking. You only need to put two and two together to realise that solutions like Writely (http://www.writely.com) can really benefit from such an arrangement. So here's looking to the future.

Btw, there is a rather less known web-based office suite called gOffice (https://goffice.com) which is based on a TeX engine (the rather recent XeTeX variety, if I am not mistaken). Unfortunately, it has recently ceased to be free, for reasons which are beyond my comprehension, so I'm not even sure one can test-drive it for a while to see how it handles.</description>
		<content:encoded><![CDATA[<p>Teekay,</p>
<p>You have a really good point here - but your argument is sligthly sollipsistic. I mean to say that the fact that M$ Word is the de facto business standard document format is the reason why most people would resort to it for data exchange. Otherwise, people would use a more stable data format. Such is life :-). But your point is good: what&#8217;s my editor going to do with my lovely, hyper-linked, indexed and printer-ready pdf manuscript? </p>
<p>Of course, Real Men &#8482; would use cvs, or some other versioning system. For a programmer, nothing is easier than checking in a TeX source file into cvs. But writers need to write, not go for an IT degree, so this makes the accessibility of the system very hard indeed. (LyX 4.x incorporates change tracking, and it&#8217;s very nice, but that ties you to the .lyx document format, which is hardly an improvement). </p>
<p>I expect the current trend in web-based applications to eventually incorporate concurrent version tracking. You only need to put two and two together to realise that solutions like Writely (http://www.writely.com) can really benefit from such an arrangement. So here&#8217;s looking to the future.</p>
<p>Btw, there is a rather less known web-based office suite called gOffice (https://goffice.com) which is based on a TeX engine (the rather recent XeTeX variety, if I am not mistaken). Unfortunately, it has recently ceased to be free, for reasons which are beyond my comprehension, so I&#8217;m not even sure one can test-drive it for a while to see how it handles.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lordmike</title>
		<link>http://theappleblog.com/2006/10/05/latex-and-osx/#comment-66645</link>
		<dc:creator>Lordmike</dc:creator>
		<pubDate>Fri, 06 Oct 2006 10:52:46 +0000</pubDate>
		<guid isPermaLink="false">http://theappleblog.com/2006/10/05/latex-and-osx/#comment-66645</guid>
		<description>Kamen: ahh ok, I will try to learn how LaTeX works, so I don't have to use MS Word all the time for simple txt documents. 
I sometimes want different layouts then just plain text from first page to last and this sounds like it could help me.
Never got around to learn teTeX because it was too hard and all I used was vim and pico when I used linux and ms word to format the text in windows.
 Thanks for the info!</description>
		<content:encoded><![CDATA[<p>Kamen: ahh ok, I will try to learn how LaTeX works, so I don&#8217;t have to use MS Word all the time for simple txt documents.<br />
I sometimes want different layouts then just plain text from first page to last and this sounds like it could help me.<br />
Never got around to learn teTeX because it was too hard and all I used was vim and pico when I used linux and ms word to format the text in windows.<br />
 Thanks for the info!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Teekay</title>
		<link>http://theappleblog.com/2006/10/05/latex-and-osx/#comment-66640</link>
		<dc:creator>Teekay</dc:creator>
		<pubDate>Fri, 06 Oct 2006 09:29:20 +0000</pubDate>
		<guid isPermaLink="false">http://theappleblog.com/2006/10/05/latex-and-osx/#comment-66640</guid>
		<description>I'm a big fan of LaTeX (via iTeXMac) but there's one thing that's a show-stopper for me: as a professional editor and writer, I exchange documents with colleagues all the time for revisions (both at their and my end). Using PDF is simply a drag: sure, you can mark up a PDF file either in Preview or in the full Acrobat version, but when I get those comments back I still need to work them into the text myself. With Word, you simply turn on track changes and there you go. (Of course, Word has a propensity to screw up track changes very badly. But it works in about 70 percent of cases.) So, yeah, for collaborative work LaTeX is not going to work unless your colleagues all use it too.</description>
		<content:encoded><![CDATA[<p>I&#8217;m a big fan of LaTeX (via iTeXMac) but there&#8217;s one thing that&#8217;s a show-stopper for me: as a professional editor and writer, I exchange documents with colleagues all the time for revisions (both at their and my end). Using PDF is simply a drag: sure, you can mark up a PDF file either in Preview or in the full Acrobat version, but when I get those comments back I still need to work them into the text myself. With Word, you simply turn on track changes and there you go. (Of course, Word has a propensity to screw up track changes very badly. But it works in about 70 percent of cases.) So, yeah, for collaborative work LaTeX is not going to work unless your colleagues all use it too.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kamen</title>
		<link>http://theappleblog.com/2006/10/05/latex-and-osx/#comment-66635</link>
		<dc:creator>Kamen</dc:creator>
		<pubDate>Fri, 06 Oct 2006 08:47:42 +0000</pubDate>
		<guid isPermaLink="false">http://theappleblog.com/2006/10/05/latex-and-osx/#comment-66635</guid>
		<description>Lordmike: LaTeX is actually a collection of macros running on Donald Knuth's TeX. While TeX is the underlying language there, it is rarely used in the raw ("plain TeX", as it's called).

teTeX is simply one of the main current distributions of TeX - it includes LaTeX, of course, and MacTeX is based on it. So there's no particular difference there.

Eric MacKnight:

"Superiority" is a complex term, especially in a public discussion. ;-) I am also not profficient in pages, but I do understand it is template- (and, therefore, somewhat structure-) based.

The "superiority" - let's call it adequacy - of LaTex for large projects is centred mainly in its handling of structured data - it doesn't matter how many hundreds of sections, subsections, footnotes, margin notes, paragraphs and headings you have, you can affect the appearance of all with minimal effort. This includes automatic page-, section- and note-numbering, as well as automatic generation of indexes and tables of content.

The algorithmic handling of typesetting is probably one of the best currently available ones - I believe only Quark Express comes close. You never need to worry about hyphenation, line-separation, orphaned or widowed paragraphs, etc. Not to speak of its brilliant handling of a wide variety of bibliography styles via BibTeX.

Conclusion - I wouldn't trust my Ph.D. thesis to Pages. Or my Great European Novel. Not even my articles.

On the other hand, if I were to write a quick note, an in-company memo, or a brief list, LaTeX would be overkill - Pages, or Your Preferred Word Processor, are better at that.

So, it really depends on what, when, for whom, and how often you write. As it is with most tools.

If I were new to LaTeX, I would give it a try. I would consider the pros and cons of LaTeX and my existing word-processing software. And I would take my decision.</description>
		<content:encoded><![CDATA[<p>Lordmike: LaTeX is actually a collection of macros running on Donald Knuth&#8217;s TeX. While TeX is the underlying language there, it is rarely used in the raw (&#8221;plain TeX&#8221;, as it&#8217;s called).</p>
<p>teTeX is simply one of the main current distributions of TeX - it includes LaTeX, of course, and MacTeX is based on it. So there&#8217;s no particular difference there.</p>
<p>Eric MacKnight:</p>
<p>&#8220;Superiority&#8221; is a complex term, especially in a public discussion. <img src='http://theappleblog.com/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /> I am also not profficient in pages, but I do understand it is template- (and, therefore, somewhat structure-) based.</p>
<p>The &#8220;superiority&#8221; - let&#8217;s call it adequacy - of LaTex for large projects is centred mainly in its handling of structured data - it doesn&#8217;t matter how many hundreds of sections, subsections, footnotes, margin notes, paragraphs and headings you have, you can affect the appearance of all with minimal effort. This includes automatic page-, section- and note-numbering, as well as automatic generation of indexes and tables of content.</p>
<p>The algorithmic handling of typesetting is probably one of the best currently available ones - I believe only Quark Express comes close. You never need to worry about hyphenation, line-separation, orphaned or widowed paragraphs, etc. Not to speak of its brilliant handling of a wide variety of bibliography styles via BibTeX.</p>
<p>Conclusion - I wouldn&#8217;t trust my Ph.D. thesis to Pages. Or my Great European Novel. Not even my articles.</p>
<p>On the other hand, if I were to write a quick note, an in-company memo, or a brief list, LaTeX would be overkill - Pages, or Your Preferred Word Processor, are better at that.</p>
<p>So, it really depends on what, when, for whom, and how often you write. As it is with most tools.</p>
<p>If I were new to LaTeX, I would give it a try. I would consider the pros and cons of LaTeX and my existing word-processing software. And I would take my decision.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: pollux</title>
		<link>http://theappleblog.com/2006/10/05/latex-and-osx/#comment-66629</link>
		<dc:creator>pollux</dc:creator>
		<pubDate>Fri, 06 Oct 2006 08:16:58 +0000</pubDate>
		<guid isPermaLink="false">http://theappleblog.com/2006/10/05/latex-and-osx/#comment-66629</guid>
		<description>I would say if you want to make a short document, say within 15 pages, use word/pages. For larger documents I would definitely go for Latex. I have written my thesis in Latex and helped in writing lecture notes (200  pages), when i think of having to do these kind of things in word makes me unhappy.</description>
		<content:encoded><![CDATA[<p>I would say if you want to make a short document, say within 15 pages, use word/pages. For larger documents I would definitely go for Latex. I have written my thesis in Latex and helped in writing lecture notes (200  pages), when i think of having to do these kind of things in word makes me unhappy.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric MacKnight</title>
		<link>http://theappleblog.com/2006/10/05/latex-and-osx/#comment-66622</link>
		<dc:creator>Eric MacKnight</dc:creator>
		<pubDate>Fri, 06 Oct 2006 06:24:24 +0000</pubDate>
		<guid isPermaLink="false">http://theappleblog.com/2006/10/05/latex-and-osx/#comment-66622</guid>
		<description>I was wondering about Pages vs. LaTex, so thanks to nerrad for his comment. 

Can anyone else explain why LaTex would be superiour to Pages for, say, a book project?</description>
		<content:encoded><![CDATA[<p>I was wondering about Pages vs. LaTex, so thanks to nerrad for his comment. </p>
<p>Can anyone else explain why LaTex would be superiour to Pages for, say, a book project?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lordmike</title>
		<link>http://theappleblog.com/2006/10/05/latex-and-osx/#comment-66620</link>
		<dc:creator>Lordmike</dc:creator>
		<pubDate>Fri, 06 Oct 2006 05:26:01 +0000</pubDate>
		<guid isPermaLink="false">http://theappleblog.com/2006/10/05/latex-and-osx/#comment-66620</guid>
		<description>Does it differ much from the old teTeX?
Maybe just another way of using TeX?</description>
		<content:encoded><![CDATA[<p>Does it differ much from the old teTeX?<br />
Maybe just another way of using TeX?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: nerrad</title>
		<link>http://theappleblog.com/2006/10/05/latex-and-osx/#comment-66599</link>
		<dc:creator>nerrad</dc:creator>
		<pubDate>Fri, 06 Oct 2006 01:39:10 +0000</pubDate>
		<guid isPermaLink="false">http://theappleblog.com/2006/10/05/latex-and-osx/#comment-66599</guid>
		<description>I prefer Pages. It too has a bit of a learning curve but it allows me to have great control over the look of my documents. I also find it easier to use than InDesign or Quark. I often use Pages to fix styles of documents I receive from my coworkers that have been badly butchered in MS Word. 

While LaTex has an advantage of being a simple text format, it is just too weird for my tastes. 

Thanks for the article however. A very well done piece. I think it will get some people to give LaTex a try.</description>
		<content:encoded><![CDATA[<p>I prefer Pages. It too has a bit of a learning curve but it allows me to have great control over the look of my documents. I also find it easier to use than InDesign or Quark. I often use Pages to fix styles of documents I receive from my coworkers that have been badly butchered in MS Word. </p>
<p>While LaTex has an advantage of being a simple text format, it is just too weird for my tastes. </p>
<p>Thanks for the article however. A very well done piece. I think it will get some people to give LaTex a try.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeff S.</title>
		<link>http://theappleblog.com/2006/10/05/latex-and-osx/#comment-66594</link>
		<dc:creator>Jeff S.</dc:creator>
		<pubDate>Fri, 06 Oct 2006 00:36:01 +0000</pubDate>
		<guid isPermaLink="false">http://theappleblog.com/2006/10/05/latex-and-osx/#comment-66594</guid>
		<description>For the last 6 quarters I have been switching back and forth between Mellel/Sente and LaTeX/BibDesk (writing papers in APA format), often writing the same paper in both just to compare. 

My programming background makes me like LaTeX, and its output looks really sharp. But I never really felt like it let me "focus on the content" as everyone says it does. My short papers (less than 10 pages) always looked crowded with all of the LaTeX syntax (citations, enumerated lists, etc). When I write in Mellel the document looks clean and distraction free. I set the pararaph style I want and then just get to work.

I wish that I preferred LaTeX, but Mellel is too excellent for my needs.

cheers</description>
		<content:encoded><![CDATA[<p>For the last 6 quarters I have been switching back and forth between Mellel/Sente and LaTeX/BibDesk (writing papers in APA format), often writing the same paper in both just to compare. </p>
<p>My programming background makes me like LaTeX, and its output looks really sharp. But I never really felt like it let me &#8220;focus on the content&#8221; as everyone says it does. My short papers (less than 10 pages) always looked crowded with all of the LaTeX syntax (citations, enumerated lists, etc). When I write in Mellel the document looks clean and distraction free. I set the pararaph style I want and then just get to work.</p>
<p>I wish that I preferred LaTeX, but Mellel is too excellent for my needs.</p>
<p>cheers</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kamen</title>
		<link>http://theappleblog.com/2006/10/05/latex-and-osx/#comment-66591</link>
		<dc:creator>Kamen</dc:creator>
		<pubDate>Fri, 06 Oct 2006 00:04:50 +0000</pubDate>
		<guid isPermaLink="false">http://theappleblog.com/2006/10/05/latex-and-osx/#comment-66591</guid>
		<description>Ah, LaTeX... It's more than a typesetting system. Like Emacs, it's a drug. Once you try it, there's no going back. Sometimes I wish I could feel happy and satisfied with a run of the mill rtf document. 

But no, after LaTeX, no output looks satisfying. Thus marvellous Mac apps, like OmniOutliner, DevonThink, or VoodooPad, seem below par, bereft of a means to export to LaTeX.

Luckily, TextMate's MultiMarkdown bundle does a great job of exporting from Markdown to good quality LaTeX - so my quick notes, lists, and memos can be exported straight into average rtf or pdf, whereas longer, more complex and ambitious documents can get the LaTeX treatment they deserve.

A dvi/pdf viewer I particulary like is TeXniScope - it's also very good at following source specials, etc.

Another essential tool is what we can consider the best possible LaTeX environment - Emacs with the AUCTeX, BibTeX and RefTeX modes... But, as you mentioned in the case of Vim, asking a Word/Nisus/Pages/OpenOffice/TextEdit user to learn a) LaTeX, and it's almost infinite depth and complexity, b) Emacs, and its almost infinite depth and complexity, and 3) AUCTeX, BibTeX and RefTeX and their almost infinite quirks and issues is more likely to cause them a brain tumor rather than increased productivity...

A possible option is LyX - a GUI front-end which attempts to avoid this complexity by hiding away the TeX source. LyX is brilliant, but, IMHO, not quite successfull - it has its own quirks, so, instead of avoiding the complexity and learnign curve of LaTeX, it adds it's own...

Indeed, the steep and lenghty learning curve and the relative complexity are likely to keep LaTeX away from public focus... But remember, once you try it, there's no going back. Honest.</description>
		<content:encoded><![CDATA[<p>Ah, LaTeX&#8230; It&#8217;s more than a typesetting system. Like Emacs, it&#8217;s a drug. Once you try it, there&#8217;s no going back. Sometimes I wish I could feel happy and satisfied with a run of the mill rtf document. </p>
<p>But no, after LaTeX, no output looks satisfying. Thus marvellous Mac apps, like OmniOutliner, DevonThink, or VoodooPad, seem below par, bereft of a means to export to LaTeX.</p>
<p>Luckily, TextMate&#8217;s MultiMarkdown bundle does a great job of exporting from Markdown to good quality LaTeX - so my quick notes, lists, and memos can be exported straight into average rtf or pdf, whereas longer, more complex and ambitious documents can get the LaTeX treatment they deserve.</p>
<p>A dvi/pdf viewer I particulary like is TeXniScope - it&#8217;s also very good at following source specials, etc.</p>
<p>Another essential tool is what we can consider the best possible LaTeX environment - Emacs with the AUCTeX, BibTeX and RefTeX modes&#8230; But, as you mentioned in the case of Vim, asking a Word/Nisus/Pages/OpenOffice/TextEdit user to learn a) LaTeX, and it&#8217;s almost infinite depth and complexity, b) Emacs, and its almost infinite depth and complexity, and 3) AUCTeX, BibTeX and RefTeX and their almost infinite quirks and issues is more likely to cause them a brain tumor rather than increased productivity&#8230;</p>
<p>A possible option is LyX - a GUI front-end which attempts to avoid this complexity by hiding away the TeX source. LyX is brilliant, but, IMHO, not quite successfull - it has its own quirks, so, instead of avoiding the complexity and learnign curve of LaTeX, it adds it&#8217;s own&#8230;</p>
<p>Indeed, the steep and lenghty learning curve and the relative complexity are likely to keep LaTeX away from public focus&#8230; But remember, once you try it, there&#8217;s no going back. Honest.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kai</title>
		<link>http://theappleblog.com/2006/10/05/latex-and-osx/#comment-66586</link>
		<dc:creator>Kai</dc:creator>
		<pubDate>Thu, 05 Oct 2006 23:08:28 +0000</pubDate>
		<guid isPermaLink="false">http://theappleblog.com/2006/10/05/latex-and-osx/#comment-66586</guid>
		<description>Just to play the devil's advocate - professional typesetters and designers these days use WYSIWIG software, such as Quark XPress or InDesign (or even Illustrator) for typesetting and Adobe PDF as an exchange file format...

I totally agree what a biaché Word is when trying to get your document to look just right, but then that's what the other design packages are for.

Word is essentially a word processing application, that attempts to tackle the issue of page layout, whereas the Quark and InDesign are proper page layout applications that allow you to perform text processing.

I've used Quark for so long that even if I'm working on a simple one-page letter, I find it easier (and a whole heap less frustrating!) to do it in Quark than I do in Word =)</description>
		<content:encoded><![CDATA[<p>Just to play the devil&#8217;s advocate - professional typesetters and designers these days use WYSIWIG software, such as Quark XPress or InDesign (or even Illustrator) for typesetting and Adobe PDF as an exchange file format&#8230;</p>
<p>I totally agree what a biaché Word is when trying to get your document to look just right, but then that&#8217;s what the other design packages are for.</p>
<p>Word is essentially a word processing application, that attempts to tackle the issue of page layout, whereas the Quark and InDesign are proper page layout applications that allow you to perform text processing.</p>
<p>I&#8217;ve used Quark for so long that even if I&#8217;m working on a simple one-page letter, I find it easier (and a whole heap less frustrating!) to do it in Quark than I do in Word =)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott</title>
		<link>http://theappleblog.com/2006/10/05/latex-and-osx/#comment-66583</link>
		<dc:creator>Scott</dc:creator>
		<pubDate>Thu, 05 Oct 2006 22:33:40 +0000</pubDate>
		<guid isPermaLink="false">http://theappleblog.com/2006/10/05/latex-and-osx/#comment-66583</guid>
		<description>I use great program called LaTeXit.  It designed to create equations that you can export as PDFs or image files and import them into presentations or documents.  It is the best equation editor i have ever used.</description>
		<content:encoded><![CDATA[<p>I use great program called LaTeXit.  It designed to create equations that you can export as PDFs or image files and import them into presentations or documents.  It is the best equation editor i have ever used.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Geir-Tore</title>
		<link>http://theappleblog.com/2006/10/05/latex-and-osx/#comment-66582</link>
		<dc:creator>Geir-Tore</dc:creator>
		<pubDate>Thu, 05 Oct 2006 22:32:29 +0000</pubDate>
		<guid isPermaLink="false">http://theappleblog.com/2006/10/05/latex-and-osx/#comment-66582</guid>
		<description>I have been using LaTeX for quite a while now, with the latest job being my master's thesis. It works great for focusing on getting content down instead of fiddling with fonts, space adjustments, lists, references, etc.

One little note in reference to LaTeX: The first version of LaTeX was published untested by the author. He hadn't tested it live at all. He knew that it would work though ... he had mathematically proved it ;-)</description>
		<content:encoded><![CDATA[<p>I have been using LaTeX for quite a while now, with the latest job being my master&#8217;s thesis. It works great for focusing on getting content down instead of fiddling with fonts, space adjustments, lists, references, etc.</p>
<p>One little note in reference to LaTeX: The first version of LaTeX was published untested by the author. He hadn&#8217;t tested it live at all. He knew that it would work though &#8230; he had mathematically proved it <img src='http://theappleblog.com/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tyler Kieft</title>
		<link>http://theappleblog.com/2006/10/05/latex-and-osx/#comment-66577</link>
		<dc:creator>Tyler Kieft</dc:creator>
		<pubDate>Thu, 05 Oct 2006 21:54:05 +0000</pubDate>
		<guid isPermaLink="false">http://theappleblog.com/2006/10/05/latex-and-osx/#comment-66577</guid>
		<description>I was forced to use LaTeX in 11th grade at a summer camp to write a biology paper.  At the time, being new to both Linux and LaTeX, and thinking that LaTeX was overkill for biology, I hated it, because the learning curve was so frustrating.

Now, three years later, I am ready to completely ditch Word.  I am sick of watching it bounce in the dock 10 or 11 times before it opens, and I am sick of its slow performance across the board.  I have started using LaTeX again to write documents, and it has been such a joy.  The finished product looks extremely professional, and it is much easier to concentrate on the content rather than worrying about why Word wants to split your table across two pages!!  I urge anyone reading this to give LaTeX a try.</description>
		<content:encoded><![CDATA[<p>I was forced to use LaTeX in 11th grade at a summer camp to write a biology paper.  At the time, being new to both Linux and LaTeX, and thinking that LaTeX was overkill for biology, I hated it, because the learning curve was so frustrating.</p>
<p>Now, three years later, I am ready to completely ditch Word.  I am sick of watching it bounce in the dock 10 or 11 times before it opens, and I am sick of its slow performance across the board.  I have started using LaTeX again to write documents, and it has been such a joy.  The finished product looks extremely professional, and it is much easier to concentrate on the content rather than worrying about why Word wants to split your table across two pages!!  I urge anyone reading this to give LaTeX a try.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric</title>
		<link>http://theappleblog.com/2006/10/05/latex-and-osx/#comment-66576</link>
		<dc:creator>Eric</dc:creator>
		<pubDate>Thu, 05 Oct 2006 21:43:24 +0000</pubDate>
		<guid isPermaLink="false">http://theappleblog.com/2006/10/05/latex-and-osx/#comment-66576</guid>
		<description>I'm a recent convert to LaTex myself (mainly through the magic of TextMate.  Love that program), and let me just say: i never want to go back to word processors.  If you have anything at all to do with academia, and can get past the learning curve, there really is no other game in town.

HTML is a great analogy:  Think of something like Word as a WYSIWYG editor: sure its easy to use (for the most part) but the end result is invariably ugly, and looks the same as everyone else; there's no character, no personality.  LaTeX is like coding your own HTML: you have infinitely more control and the results can verge on the artistic.

i not only write my own academic papers, but I also do technical support for a campus full of faculty who i know could really benefit from something like LaTeX.  I'm am going to do my best to convert a few along the way.  If you deal with any type of long-form document, deal with multiple references, make use of indexes, TOCs, etc, LaTeX is a breath of fresh air</description>
		<content:encoded><![CDATA[<p>I&#8217;m a recent convert to LaTex myself (mainly through the magic of TextMate.  Love that program), and let me just say: i never want to go back to word processors.  If you have anything at all to do with academia, and can get past the learning curve, there really is no other game in town.</p>
<p>HTML is a great analogy:  Think of something like Word as a WYSIWYG editor: sure its easy to use (for the most part) but the end result is invariably ugly, and looks the same as everyone else; there&#8217;s no character, no personality.  LaTeX is like coding your own HTML: you have infinitely more control and the results can verge on the artistic.</p>
<p>i not only write my own academic papers, but I also do technical support for a campus full of faculty who i know could really benefit from something like LaTeX.  I&#8217;m am going to do my best to convert a few along the way.  If you deal with any type of long-form document, deal with multiple references, make use of indexes, TOCs, etc, LaTeX is a breath of fresh air</p>
]]></content:encoded>
	</item>
</channel>
</rss>
