From: David Maus <dmaus@ictsoc.de>
To: Matt Price <moptop99@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: possible tex export bug?
Date: Sun, 12 Sep 2010 13:55:22 +0200 [thread overview]
Message-ID: <87k4mrb2hh.wl%dmaus@ictsoc.de> (raw)
In-Reply-To: <AANLkTinVpY1wZui+3u243cO1mgLChNaGOrdewwzCO1k0@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1078 bytes --]
Hi Matt,
Matt Price wrote:
>Sorry for the barrage of help requests. I don't know much about tex
>but it's possible the tex output from one file I am working on is
>buggy, as mk4ht refuses to read it. The .org and .tex files are
>attached, as is the initial error output of mk4ht oolatex
>His495Ouline.tex. This is perhaps the wrong list to be asking on,
>but I am sort of working from the assumption that there's an issue
>with the tex code that org produces -- mk4ht seems to work fine with
>simpler documents. I';m using a pretty recent org-mode (7.01 from
>not that long ago).
I gradually removed all content from the TeX file and it turns out
that one problem is the savetrees package: If I remove it in the TeX
file, tex4ht proceeds -- but fails again, this time on the \label
command. Removing the hyperref package helps here.
Looks like a problem in tex4h, not Org. Compiling the tex file with
latex works fine, with both hyperref and savetrees included.
HTH,
-- David
--
OpenPGP... 0x99ADB83B5A4478E6
Jabber.... dmjena@jabber.org
Email..... dmaus@ictsoc.de
[-- Attachment #1.2: Type: application/pgp-signature, Size: 230 bytes --]
[-- Attachment #2: Type: text/plain, Size: 201 bytes --]
_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
prev parent reply other threads:[~2010-09-12 11:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-03 14:18 possible tex export bug? Matt Price
2010-09-03 14:21 ` Matt Price
2010-09-12 11:55 ` David Maus [this message]
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=87k4mrb2hh.wl%dmaus@ictsoc.de \
--to=dmaus@ictsoc.de \
--cc=emacs-orgmode@gnu.org \
--cc=moptop99@gmail.com \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).