Browse Source

LaTeX export: Allow postscript extensions for images

Some propel process LaTeX filed not directly to pdf, but go
through dvi and then to ps or pdf.  In that case, allowed images
are ps and eps files, not pdf and jpg.

This commit adds the two extensions, so that export using that
alternative path can be supported better.  However, it is up to the
user to make sure that the images are actually compatible with the
backend.
Carsten Dominik 15 years ago
parent
commit
3d2b4d98c1
2 changed files with 10 additions and 5 deletions
  1. 5 0
      lisp/ChangeLog
  2. 5 5
      lisp/org-latex.el

+ 5 - 0
lisp/ChangeLog

@@ -1,3 +1,8 @@
+2009-06-28  Carsten Dominik  <carsten.dominik@gmail.com>
+
+	* org-latex.el (org-export-latex-inline-image-extensions): Add ps
+	and eps extensions.
+
 2009-06-27  Carsten Dominik  <carsten.dominik@gmail.com>
 
 	* org-agenda.el (org-write-agenda): Make sure org-icalendar is

+ 5 - 5
lisp/org-latex.el

@@ -316,12 +316,12 @@ and `org-export-with-tags' instead."
   :type 'string)
 
 (defcustom org-export-latex-inline-image-extensions
-  '("pdf" "jpeg" "jpg" "png")
+  '("pdf" "jpeg" "jpg" "png" "ps" "eps")
   "Extensions of image files that can be inlined into LaTeX.
-Note that this depends on the way the LaTeX file is processed.
-The default setting (pdf and jpg) assumes that pdflatex is doing the
-processing.  If you are using latex and dvips or something similar,
-only postscript files can be included."
+Note that the image extension *actually* allowed depend on the way the
+LaTeX file is processed.  When used with pdflatex, pdf, jpg and png images
+are OK.  When processing through dvi to Postscript, only ps and eps are
+allowed.  The default we use here encompasses both."
   :group 'org-export-latex
   :type '(repeat (string :tag "Extension")))