emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Manish <mailtomanish.sharma@gmail.com>
To: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Export to PDF - invalid fontname
Date: Fri, 17 Oct 2008 16:02:05 +0530	[thread overview]
Message-ID: <e7cdbe30810170332m64e1756aoa26f1f1614787b21@mail.gmail.com> (raw)

Hello Carsten,

Thanks for adding the new option to export directly to PDF.  I think I
will start to draft my work docments in Org finally.  But at the
moment it doesn't seem to work on Windows.

I had some text listing a path name and Latex exported file was
failing a compile even when done manually.  I prefixed those lines
with ":" and the export + manual compile (under both Cygwin and
Windows Texlive) goes fine but not direct export to PDF.  Apparently,
Latex export to PDF directly from an Org file does not like ":" in
path names probably (and possibly "\" as well, doesn't seem to handle
\LaTeX as well).

This is on Windows XP, Emacs 22.3, Org 6.09a (git b19428d).

,----
| This is pdfTeXk, Version 3.1415926-1.40.9 (Web2C 7.5.7)
|  %&-line parsing enabled.
| entering extended mode
| ! I can't find file `d:/home/zms/org.git/personal2.tex;pdflatex'.
| <*> d:/home/zms/org.git/personal2.tex;pdflatex
|                                                -interaction
nonstopmode d:/h...
|
| (Press Enter to retry, or Control-Z to exit)
| Please type another input file name
| ! Emergency stop.
| <*> d:/home/zms/org.git/personal2.tex;pdflatex
|                                                -interaction
nonstopmode d:/h...
|
| !  ==> Fatal error occurred, no output PDF file produced!
| Transcript written on texput.log.
| kpathsea: Invalid fontname
`d:/home/zms/org.git/personal2.tex;pdflatex', contains ':'
`----

Regards,
-- Manish

next             reply	other threads:[~2008-10-17 10:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-17 10:32 Manish [this message]
2008-10-18 13:21 ` Export to PDF - invalid fontname Carsten Dominik

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=e7cdbe30810170332m64e1756aoa26f1f1614787b21@mail.gmail.com \
    --to=mailtomanish.sharma@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).