auctex-diffs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[AUCTeX-diffs] Changes to auctex/preview/doc/preview-latex.texi


From: Ralf Angeli
Subject: [AUCTeX-diffs] Changes to auctex/preview/doc/preview-latex.texi
Date: Sun, 10 Apr 2005 12:29:00 -0400

Index: auctex/preview/doc/preview-latex.texi
diff -u auctex/preview/doc/preview-latex.texi:1.77 
auctex/preview/doc/preview-latex.texi:1.78
--- auctex/preview/doc/preview-latex.texi:1.77  Sat Apr  2 00:51:12 2005
+++ auctex/preview/doc/preview-latex.texi       Sun Apr 10 16:28:59 2005
@@ -644,17 +644,17 @@
 What happens when @LaTeX{} is finished depends on the configuration of
 @code{preview-image-type}.  What to do for each of the various settings
 is specified in the variable @code{preview-image-creators}.  The options
-to pass into GhostScript and what Emacs image type to use is specified
+to pass into Ghostscript and what Emacs image type to use is specified
 in @code{preview-gs-image-type-alist}.
 
 @code{preview-image-type} defaults to @code{png}.  For this to work,
-your version of GhostScript needs to support the @option{png16m} device.
+your version of Ghostscript needs to support the @option{png16m} device.
 If you are experiencing problems here, you might want to reconfigure
 @code{gs-image-type-alist} or @code{preview-image-type}.  Reconfiguring
 @code{preview-image-creators} is only necessary for adding additional
 image types.
 
-Most devices make @previewlatex{} start up a single GhostScript process
+Most devices make @previewlatex{} start up a single Ghostscript process
 for the entire preview run (as opposed to one per image) and feed it
 either sections of a @acronym{PDF} file (if address@hidden was used), or
 (after running Dvips) sections of a single PostScript file or separate
@@ -670,7 +670,7 @@
 Another noteworthy setting of @code{preview-image-type} is
 @samp{dvipng}: in this case, the @address@hidden program
 will get run on @acronym{DVI} output (see below for @acronym{PDF}).
-This is in general much faster than Dvips and GhostScript.  In that
+This is in general much faster than Dvips and Ghostscript.  In that
 case, the option
 
 @item preview-dvipng-command
@@ -680,21 +680,21 @@
 images get produced (@samp{dvipng} might be configured for other image
 types as well).  You will notice that @code{preview-gs-image-type-alist}
 contains an entry for @code{dvipng}: this actually has nothing to with
address@hidden itself but specifies the image type and GhostScript device
address@hidden itself but specifies the image type and Ghostscript device
 option to use when @samp{dvipng} can't be used.  This will obviously be
 the case for @acronym{PDF} output by address@hidden, but it will also happen
 if the @acronym{DVI} file contains PostScript specials in which case the
-affected images will get run through Dvips and GhostScript once
+affected images will get run through Dvips and Ghostscript once
 @samp{dvipng} finishes.
 
 @item preview-gs-options
 Most interesting to the user perhaps is the setting of this variable.
 It contains the default antialiasing settings @option{-dTextAlphaBits=4}
 and @option{-dGraphicsAlphaBits=4}.  Decreasing those values to 2 @w{or
-1} might increase GhostScript's performance if you find it lacking.
+1} might increase Ghostscript's performance if you find it lacking.
 @end vtable
 
-Running and feeding GhostScript from @previewlatex{} happens
+Running and feeding Ghostscript from @previewlatex{} happens
 asynchronously again: you can resume editing while the images arrive.
 While those pretty pictures filling in the blanks on screen tend to
 make one marvel instead of work, rendering the non-displayed images




reply via email to

[Prev in Thread] Current Thread [Next in Thread]