<?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 Miktex Tex Processing Freeware Program</title>
	<atom:link href="http://www.rasmusen.org/x/2005/08/20/the-miktex-tex-processing-freeware-program/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.rasmusen.org/x/2005/08/20/the-miktex-tex-processing-freeware-program/</link>
	<description></description>
	<lastBuildDate>Wed, 05 Jan 2011 17:12:11 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Eric Wilson</title>
		<link>http://www.rasmusen.org/x/2005/08/20/the-miktex-tex-processing-freeware-program/comment-page-1/#comment-5358</link>
		<dc:creator>Eric Wilson</dc:creator>
		<pubDate>Tue, 31 Jan 2006 14:38:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.rasmusen.org/x/archives/777#comment-5358</guid>
		<description>Maybe I&#039;m missing something here.  Why not use WinEdt?  It&#039;s a great editor, designed particularly for LaTeX.  TexShop is ok for macs.</description>
		<content:encoded><![CDATA[<p>Maybe I&#8217;m missing something here.  Why not use WinEdt?  It&#8217;s a great editor, designed particularly for LaTeX.  TexShop is ok for macs.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Maciej Radziejewski</title>
		<link>http://www.rasmusen.org/x/2005/08/20/the-miktex-tex-processing-freeware-program/comment-page-1/#comment-3301</link>
		<dc:creator>Maciej Radziejewski</dc:creator>
		<pubDate>Tue, 27 Sep 2005 09:46:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.rasmusen.org/x/archives/777#comment-3301</guid>
		<description>Your idea of having a simple IDE (point (3) of your original post) is already implemented in Windows! Well, almost.

You can browse your files using Windows Explorer. Then you can compile (texify) by right-clicking a TeX file and selecting an appropriate command from the context menu. You just have to define a context menu action for .tex files. I usually define &quot;Latex&quot;, but you may prefer to use pdfLatex or to call some batch file for more complex processing.

Defining actions takes some knwoledge and it may be a good idea to suggest it to Christian Schenk to do it in the installer as an option (if it is not already there). You can define actions using the &quot;file types&quot; tab (in WinXP accessible from the explorer window - Tools - Options) or using regedit (dangerous if you misuse it).</description>
		<content:encoded><![CDATA[<p>Your idea of having a simple IDE (point (3) of your original post) is already implemented in Windows! Well, almost.</p>
<p>You can browse your files using Windows Explorer. Then you can compile (texify) by right-clicking a TeX file and selecting an appropriate command from the context menu. You just have to define a context menu action for .tex files. I usually define &#8220;Latex&#8221;, but you may prefer to use pdfLatex or to call some batch file for more complex processing.</p>
<p>Defining actions takes some knwoledge and it may be a good idea to suggest it to Christian Schenk to do it in the installer as an option (if it is not already there). You can define actions using the &#8220;file types&#8221; tab (in WinXP accessible from the explorer window &#8211; Tools &#8211; Options) or using regedit (dangerous if you misuse it).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: bob wolfe</title>
		<link>http://www.rasmusen.org/x/2005/08/20/the-miktex-tex-processing-freeware-program/comment-page-1/#comment-3093</link>
		<dc:creator>bob wolfe</dc:creator>
		<pubDate>Sun, 18 Sep 2005 02:53:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.rasmusen.org/x/archives/777#comment-3093</guid>
		<description>Eric,

I used to be an avid fan of SWP.  I now use Miktex.

1) I used to run into problems with carriage returns.  They all arose when I shared files with colleagues who used UNIX.  They have now all switched away from UNIX (despite them calling me all kinds of nasty names a decade ago for using Windows) so the problem is now fixed.

2) SWP is not standard.  I use a lot of math.  \mbox does not work right in SWP.  That prevented me from sharing with lots of colleagues who use standard latex.  I think there are other things that are not standard in SWP.  That makes it a pain to collaborate.

3)  SWP consultants used to have an attitude.  Maybe the attitude is now fixed, so I apologize for any aspersions suggested by these comments.  When I asked for work arounds on how to solve the problem of working with colleagues who use standard latex, the SWP consultants were extremely defensive in their responses.  Not vulgar, but close to it.  Almost as bad as the Apple community used to be towards Windows users.

4) The real raison d&#039;etre for SWP is its integration with Maple.  Beautiful.  Wonderful.  I love the concept.  Maple does simple math very well, up to algebra and closed form calculus.  It does not do hard problems well at all, such as infinite sums.  So, you have to do the math to see if it is right anyway, and then it is about as easy to type it in yourself in latex as to use the simplify verbs available in maple.  If you are teaching calc 101 or high school algebra, then SWP is great.  If you are teaching quantitative graduate courses, then be careful with SWP.</description>
		<content:encoded><![CDATA[<p>Eric,</p>
<p>I used to be an avid fan of SWP.  I now use Miktex.</p>
<p>1) I used to run into problems with carriage returns.  They all arose when I shared files with colleagues who used UNIX.  They have now all switched away from UNIX (despite them calling me all kinds of nasty names a decade ago for using Windows) so the problem is now fixed.</p>
<p>2) SWP is not standard.  I use a lot of math.  \mbox does not work right in SWP.  That prevented me from sharing with lots of colleagues who use standard latex.  I think there are other things that are not standard in SWP.  That makes it a pain to collaborate.</p>
<p>3)  SWP consultants used to have an attitude.  Maybe the attitude is now fixed, so I apologize for any aspersions suggested by these comments.  When I asked for work arounds on how to solve the problem of working with colleagues who use standard latex, the SWP consultants were extremely defensive in their responses.  Not vulgar, but close to it.  Almost as bad as the Apple community used to be towards Windows users.</p>
<p>4) The real raison d&#8217;etre for SWP is its integration with Maple.  Beautiful.  Wonderful.  I love the concept.  Maple does simple math very well, up to algebra and closed form calculus.  It does not do hard problems well at all, such as infinite sums.  So, you have to do the math to see if it is right anyway, and then it is about as easy to type it in yourself in latex as to use the simplify verbs available in maple.  If you are teaching calc 101 or high school algebra, then SWP is great.  If you are teaching quantitative graduate courses, then be careful with SWP.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bob</title>
		<link>http://www.rasmusen.org/x/2005/08/20/the-miktex-tex-processing-freeware-program/comment-page-1/#comment-3078</link>
		<dc:creator>Bob</dc:creator>
		<pubDate>Sat, 27 Aug 2005 13:36:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.rasmusen.org/x/archives/777#comment-3078</guid>
		<description>First, hello Eric, from the distant past. We knew each other at MIT.

Here&#039;s another simple way to compile a .tex file using the MikTeX texify command. (I have to admit I live at the command prompt. Just a matter of preference. I also live in Emacs!) I turn .tex into .pdf using this batch file:

texify %1.tex
dvips -tletter -Ppdf -G0 %1
call ps2pdf13 %1.ps %1.pdf

You put these commands in a file called &quot;makepdf.bat&quot;, and place the file somewhere in your path. Then if you have a .tex file called &quot;foo.tex&quot;, at the command prompt you type

makepdf foo

and you will end up with a pdf version of your document.</description>
		<content:encoded><![CDATA[<p>First, hello Eric, from the distant past. We knew each other at MIT.</p>
<p>Here&#8217;s another simple way to compile a .tex file using the MikTeX texify command. (I have to admit I live at the command prompt. Just a matter of preference. I also live in Emacs!) I turn .tex into .pdf using this batch file:</p>
<p>texify %1.tex<br />
dvips -tletter -Ppdf -G0 %1<br />
call ps2pdf13 %1.ps %1.pdf</p>
<p>You put these commands in a file called &#8220;makepdf.bat&#8221;, and place the file somewhere in your path. Then if you have a .tex file called &#8220;foo.tex&#8221;, at the command prompt you type</p>
<p>makepdf foo</p>
<p>and you will end up with a pdf version of your document.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Administrator</title>
		<link>http://www.rasmusen.org/x/2005/08/20/the-miktex-tex-processing-freeware-program/comment-page-1/#comment-3076</link>
		<dc:creator>Administrator</dc:creator>
		<pubDate>Wed, 24 Aug 2005 01:25:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.rasmusen.org/x/archives/777#comment-3076</guid>
		<description>Thanks, everyone, for these very useful comments. Harald Oehlmann&#039;s suggestion seems to work perfectly, though I had to set it up a  bit differently than he suggested, perhaps because of my version of Textpad. Here is what I&#039;ve just  added to my latex notes in 
http://rasmusen.org/x/myfiles/latex-rasmusen.txt

RUNNING MIKTEX FROM THE  TEXTPAD TEXT EDITOR

Harald Oehlmann told me how to do this. Here are precise instructions for
running miktex from Textpad 4.7.3. Maybe other text editors have similar
features.

1. Click on Configure, then Preferences, then Tools.

2. In Tools, click ADD, then choose DOS Command.  A box will appear, and write
&quot;pdflatex a file&quot; as a title for the tool. Then click APPLY.

3. Click on  the + sign next to Tools.  Several tool titles will appear,
including your new  &quot;pdflatex a file&quot;.  Click on it, and a Properties box will
appear with various things for you to type in.

4. Under Parameters, type in &quot;pdflatex  $File&quot;. Make sure that under  Initial
Folder,there is $FileDir. Make sure none of the options boxes are checked,
including CAPTURE OUTPUT. Click OK when you&#039;re done.

5. Load a tex file into Textpad. To process it, click on Tools from the front
set of headings (File, Edit, Search, View, Tools, ... ) Then click on &quot;pdflatex
a file&quot;, which you will have added.

6. The Command Prompt window will appear, and the tex file in textpad will be
processed. The PDF file will be generated as output.

 I hope I didn&#039;t miss any steps.</description>
		<content:encoded><![CDATA[<p>Thanks, everyone, for these very useful comments. Harald Oehlmann&#8217;s suggestion seems to work perfectly, though I had to set it up a  bit differently than he suggested, perhaps because of my version of Textpad. Here is what I&#8217;ve just  added to my latex notes in<br />
<a href="http://rasmusen.org/x/myfiles/latex-rasmusen.txt" rel="nofollow">http://rasmusen.org/x/myfiles/latex-rasmusen.txt</a></p>
<p>RUNNING MIKTEX FROM THE  TEXTPAD TEXT EDITOR</p>
<p>Harald Oehlmann told me how to do this. Here are precise instructions for<br />
running miktex from Textpad 4.7.3. Maybe other text editors have similar<br />
features.</p>
<p>1. Click on Configure, then Preferences, then Tools.</p>
<p>2. In Tools, click ADD, then choose DOS Command.  A box will appear, and write<br />
&#8220;pdflatex a file&#8221; as a title for the tool. Then click APPLY.</p>
<p>3. Click on  the + sign next to Tools.  Several tool titles will appear,<br />
including your new  &#8220;pdflatex a file&#8221;.  Click on it, and a Properties box will<br />
appear with various things for you to type in.</p>
<p>4. Under Parameters, type in &#8220;pdflatex  $File&#8221;. Make sure that under  Initial<br />
Folder,there is $FileDir. Make sure none of the options boxes are checked,<br />
including CAPTURE OUTPUT. Click OK when you&#8217;re done.</p>
<p>5. Load a tex file into Textpad. To process it, click on Tools from the front<br />
set of headings (File, Edit, Search, View, Tools, &#8230; ) Then click on &#8220;pdflatex<br />
a file&#8221;, which you will have added.</p>
<p>6. The Command Prompt window will appear, and the tex file in textpad will be<br />
processed. The PDF file will be generated as output.</p>
<p> I hope I didn&#8217;t miss any steps.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Misha</title>
		<link>http://www.rasmusen.org/x/2005/08/20/the-miktex-tex-processing-freeware-program/comment-page-1/#comment-3075</link>
		<dc:creator>Misha</dc:creator>
		<pubDate>Tue, 23 Aug 2005 18:52:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.rasmusen.org/x/archives/777#comment-3075</guid>
		<description>Actually, I have another suggestion on how to improve MiKTeX. It takes relatively long to load all the definitions and packages every time TeX starts. Wouldn&#039;t it be nice if there were a running instance of TeX, that would remember all those .sty files. In this case, LaTeX would just invoke that process rather than loading the definitions again.</description>
		<content:encoded><![CDATA[<p>Actually, I have another suggestion on how to improve MiKTeX. It takes relatively long to load all the definitions and packages every time TeX starts. Wouldn&#8217;t it be nice if there were a running instance of TeX, that would remember all those .sty files. In this case, LaTeX would just invoke that process rather than loading the definitions again.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stefan Grosse</title>
		<link>http://www.rasmusen.org/x/2005/08/20/the-miktex-tex-processing-freeware-program/comment-page-1/#comment-3074</link>
		<dc:creator>Stefan Grosse</dc:creator>
		<pubDate>Tue, 23 Aug 2005 18:32:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.rasmusen.org/x/archives/777#comment-3074</guid>
		<description>I also must say that using command prompt is a very unusual way for working with miktex. The perfect editor for me is &lt;a href=&quot;http://www.winedt.com&quot; rel=&quot;nofollow&quot;&gt; winedt &lt;/a&gt; where you just have to push a button for texifying and pdf-texifying.  

With the carriage return- I noticed that there is a problem by opening a book chapter from your page. Winedt corrected it but I did not try to compile since there was a lot of scientific word stuff inside.

If you like to use scientific workplace with miktex as LaTeX distro see the notes of Prof. Söderlind: &lt;a href=&quot;http://home.tiscalinet.ch/paulsoderlind/Software/Software.html&quot; rel=&quot;nofollow&quot;&gt;http://home.tiscalinet.ch/paulsoderlind/Software/Software.html&lt;/a&gt;

By the way the game trees do not look that great there is a package of Martin Osborn using pstricks to improve that: &lt;a href=&quot;http://www.chass.utoronto.ca/~osborne/latex/index.html&quot; rel=&quot;nofollow&quot;&gt;http://www.chass.utoronto.ca/~osborne/latex/index.html&lt;/a&gt;</description>
		<content:encoded><![CDATA[<p>I also must say that using command prompt is a very unusual way for working with miktex. The perfect editor for me is <a href="http://www.winedt.com" rel="nofollow"> winedt </a> where you just have to push a button for texifying and pdf-texifying.  </p>
<p>With the carriage return- I noticed that there is a problem by opening a book chapter from your page. Winedt corrected it but I did not try to compile since there was a lot of scientific word stuff inside.</p>
<p>If you like to use scientific workplace with miktex as LaTeX distro see the notes of Prof. Söderlind: <a href="http://home.tiscalinet.ch/paulsoderlind/Software/Software.html" rel="nofollow">http://home.tiscalinet.ch/paulsoderlind/Software/Software.html</a></p>
<p>By the way the game trees do not look that great there is a package of Martin Osborn using pstricks to improve that: <a href="http://www.chass.utoronto.ca/~osborne/latex/index.html" rel="nofollow">http://www.chass.utoronto.ca/~osborne/latex/index.html</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Harald Oehlmann</title>
		<link>http://www.rasmusen.org/x/2005/08/20/the-miktex-tex-processing-freeware-program/comment-page-1/#comment-3073</link>
		<dc:creator>Harald Oehlmann</dc:creator>
		<pubDate>Tue, 23 Aug 2005 15:52:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.rasmusen.org/x/archives/777#comment-3073</guid>
		<description>I use Textpad too (but pdftex to generate postscript directly).
You can invoke the pdftex processor from the editor by assigning for example Cntrl-1 to invoke latex. I use:
Menue: Config-&gt;Settings:Extras -&gt; Add Program and edit properties: Parameter: $File</description>
		<content:encoded><![CDATA[<p>I use Textpad too (but pdftex to generate postscript directly).<br />
You can invoke the pdftex processor from the editor by assigning for example Cntrl-1 to invoke latex. I use:<br />
Menue: Config-&gt;Settings:Extras -&gt; Add Program and edit properties: Parameter: $File</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Administrator</title>
		<link>http://www.rasmusen.org/x/2005/08/20/the-miktex-tex-processing-freeware-program/comment-page-1/#comment-3069</link>
		<dc:creator>Administrator</dc:creator>
		<pubDate>Tue, 23 Aug 2005 14:32:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.rasmusen.org/x/archives/777#comment-3069</guid>
		<description>Yes, Stefan. Oggdrop is just for sound files, it seems. What would be a nice utility is a program that lets you say that any file dropped into an icon gets sent to the command line and processed using  a particular command, with the output returned to the directory of the original file. I tries looking in the freeware site  http://www.nonags.com/nonags/cl.html but couldn&#039;t find such a thing.</description>
		<content:encoded><![CDATA[<p>Yes, Stefan. Oggdrop is just for sound files, it seems. What would be a nice utility is a program that lets you say that any file dropped into an icon gets sent to the command line and processed using  a particular command, with the output returned to the directory of the original file. I tries looking in the freeware site  <a href="http://www.nonags.com/nonags/cl.html" rel="nofollow">http://www.nonags.com/nonags/cl.html</a> but couldn&#8217;t find such a thing.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stefan Moebius</title>
		<link>http://www.rasmusen.org/x/2005/08/20/the-miktex-tex-processing-freeware-program/comment-page-1/#comment-3068</link>
		<dc:creator>Stefan Moebius</dc:creator>
		<pubDate>Tue, 23 Aug 2005 08:37:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.rasmusen.org/x/archives/777#comment-3068</guid>
		<description>On (3): Maybe a tool modelled after OggDrop (http://www.vorbis.com/software.psp?pid=2) would be what you need? You just grab the .tex or .mp or .dvi file and drag it to a floating icon. Dropping it would invoke the correct program based on file type and configuration (e.g., pdflatex or latex).</description>
		<content:encoded><![CDATA[<p>On (3): Maybe a tool modelled after OggDrop (<a href="http://www.vorbis.com/software.psp?pid=2" rel="nofollow">http://www.vorbis.com/software.psp?pid=2</a>) would be what you need? You just grab the .tex or .mp or .dvi file and drag it to a floating icon. Dropping it would invoke the correct program based on file type and configuration (e.g., pdflatex or latex).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Administrator</title>
		<link>http://www.rasmusen.org/x/2005/08/20/the-miktex-tex-processing-freeware-program/comment-page-1/#comment-3067</link>
		<dc:creator>Administrator</dc:creator>
		<pubDate>Tue, 23 Aug 2005 03:19:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.rasmusen.org/x/archives/777#comment-3067</guid>
		<description>I updated the original post in light of Alan&#039;s comments, so his comments won&#039;t apply well any more.</description>
		<content:encoded><![CDATA[<p>I updated the original post in light of Alan&#8217;s comments, so his comments won&#8217;t apply well any more.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Administrator</title>
		<link>http://www.rasmusen.org/x/2005/08/20/the-miktex-tex-processing-freeware-program/comment-page-1/#comment-3063</link>
		<dc:creator>Administrator</dc:creator>
		<pubDate>Tue, 23 Aug 2005 01:15:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.rasmusen.org/x/archives/777#comment-3063</guid>
		<description>Thanks! 

Adding  \usepackage{amsmath} makes the tag command work again for equation special labelling. 

  I still have the problem with line returns. It isn&#039;t SWP-- I actually write my latex files in Textpad, a text editor, and then used SWP only as a front-end--- hence its inferiority to Miktex for me, since I don&#039;t use  most of SWP&#039;s special features anyway.  Also, the line return problem occurs when there are line returns in equations.   

 </description>
		<content:encoded><![CDATA[<p>Thanks! </p>
<p>Adding  \usepackage{amsmath} makes the tag command work again for equation special labelling. </p>
<p>  I still have the problem with line returns. It isn&#8217;t SWP&#8211; I actually write my latex files in Textpad, a text editor, and then used SWP only as a front-end&#8212; hence its inferiority to Miktex for me, since I don&#8217;t use  most of SWP&#8217;s special features anyway.  Also, the line return problem occurs when there are line returns in equations.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alan</title>
		<link>http://www.rasmusen.org/x/2005/08/20/the-miktex-tex-processing-freeware-program/comment-page-1/#comment-3061</link>
		<dc:creator>Alan</dc:creator>
		<pubDate>Mon, 22 Aug 2005 20:29:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.rasmusen.org/x/archives/777#comment-3061</guid>
		<description>Eric,

I am not a user of SWP myself, but I do believe there are a number of ways in which SWP deviates from &quot;standard&quot; LaTeX (I&#039;ve had these cause problems when sharing files with SWP users). MiKTeX, along with TeXLive, teTeX, and most other TeX distributions will have the same issues you describe here with respect to SWP. That said, allow me to attempt to address a few of your points:

(2) and (3): I have rarely invoked LaTeX from the command line, whether using MiKTeX or another LaTeX distribution. Many, if not most, LaTeX users use an editor that handles the direct interaction with the LaTeX executable and friends. SWP is really nothing more than a very fancy LaTeX front-end. While the editors that most folks use are not as fancy, they do handle all of the command line work and make invoking LaTeX transparent to the user. Some popular Windows-friendly text editors than can be configured in this way are WinEdt (shareware), TeXnicCenter (freeware), and Emacs with appropriate plug-ins (open source), though there are a number of others.

(4): Not sure why you&#039;re experiencing problems with hard carriage returns. My files are chock full of them and MiKTeX handles them without complaint, so I suspect SWP is to blame here. Perhaps it is using an odd end-of-line character? Open one of your SWP files in a plain text editor (Notepad -- but not Wordpad -- will do) and see if it is read correctly, or if garbage appears at the end of the line. Alternatively, write a dummy LaTeX file with hard carriage returns using Notepad and see how it goes. Finally, I understand there&#039;s a way to export files from SWP in a way that is supposed to make them more compatible with &quot;standard&quot; LaTeX systems -- if true, you might try exporting your files in this manner before running them through MiKTeX.

(5): The problem here is that pdfLaTeX is using Type 3 Postscript fonts instead of the more desirable Type 1 fonts. Since I don&#039;t use pdfLaTeX myself, I can&#039;t tell you for sure how to change it (though installing the cm-super package via the MiKTeX package manager might do the trick). A search of the usenet newsgroup comp.text.tex (via groups.google.com) should get you an answer pretty quickly, though.

(6): MiKTeX does not recognize \tag because it is not part of standard LaTeX. To use it, you must call \usepackage{amsmath} in your preamble. Apparently, SWP does this for you whether you like it or not. Fortunately, amsmath is distributed with MiKTeX and virtually every other LaTeX distribution, so it should already be installed.

(7): SWP insulates you from some of the low-level LaTeX drudgery at the cost of making your .tex files a little less portable. Another side-effect of this insulation is that you don&#039;t always know what&#039;s going on &quot;behind the scenes,&quot; as you saw when you tried to use the \tag command without \usepackage{amsmath}.

Alan</description>
		<content:encoded><![CDATA[<p>Eric,</p>
<p>I am not a user of SWP myself, but I do believe there are a number of ways in which SWP deviates from &#8220;standard&#8221; LaTeX (I&#8217;ve had these cause problems when sharing files with SWP users). MiKTeX, along with TeXLive, teTeX, and most other TeX distributions will have the same issues you describe here with respect to SWP. That said, allow me to attempt to address a few of your points:</p>
<p>(2) and (3): I have rarely invoked LaTeX from the command line, whether using MiKTeX or another LaTeX distribution. Many, if not most, LaTeX users use an editor that handles the direct interaction with the LaTeX executable and friends. SWP is really nothing more than a very fancy LaTeX front-end. While the editors that most folks use are not as fancy, they do handle all of the command line work and make invoking LaTeX transparent to the user. Some popular Windows-friendly text editors than can be configured in this way are WinEdt (shareware), TeXnicCenter (freeware), and Emacs with appropriate plug-ins (open source), though there are a number of others.</p>
<p>(4): Not sure why you&#8217;re experiencing problems with hard carriage returns. My files are chock full of them and MiKTeX handles them without complaint, so I suspect SWP is to blame here. Perhaps it is using an odd end-of-line character? Open one of your SWP files in a plain text editor (Notepad &#8212; but not Wordpad &#8212; will do) and see if it is read correctly, or if garbage appears at the end of the line. Alternatively, write a dummy LaTeX file with hard carriage returns using Notepad and see how it goes. Finally, I understand there&#8217;s a way to export files from SWP in a way that is supposed to make them more compatible with &#8220;standard&#8221; LaTeX systems &#8212; if true, you might try exporting your files in this manner before running them through MiKTeX.</p>
<p>(5): The problem here is that pdfLaTeX is using Type 3 Postscript fonts instead of the more desirable Type 1 fonts. Since I don&#8217;t use pdfLaTeX myself, I can&#8217;t tell you for sure how to change it (though installing the cm-super package via the MiKTeX package manager might do the trick). A search of the usenet newsgroup comp.text.tex (via groups.google.com) should get you an answer pretty quickly, though.</p>
<p>(6): MiKTeX does not recognize \tag because it is not part of standard LaTeX. To use it, you must call \usepackage{amsmath} in your preamble. Apparently, SWP does this for you whether you like it or not. Fortunately, amsmath is distributed with MiKTeX and virtually every other LaTeX distribution, so it should already be installed.</p>
<p>(7): SWP insulates you from some of the low-level LaTeX drudgery at the cost of making your .tex files a little less portable. Another side-effect of this insulation is that you don&#8217;t always know what&#8217;s going on &#8220;behind the scenes,&#8221; as you saw when you tried to use the \tag command without \usepackage{amsmath}.</p>
<p>Alan</p>
]]></content:encoded>
	</item>
</channel>
</rss>

