From: Ulf Stegemann <ulf-news@zeitform.de>
To: emacs-orgmode@gnu.org
Subject: Re: IMPORTANT: (possibly) incompatible Change
Date: Wed, 07 Apr 2010 11:15:50 +0200 [thread overview]
Message-ID: <zf.upn39z7sjw9.fsf@zeitform.de> (raw)
In-Reply-To: 87wrwk7cf7.fsf@ara.blue-cable.net
Karsten Heymann <karsten.heymann@blue-cable.net> wrote:
> Not as far as I know. hyperref and microtype will run with reduced
> features, but apart from that, there should be no problem. Regarding
> microtype, I do not know what happens when it is used with the old TeX
> or eTeX compiler that was used to created dvi's before pdftex was used
> for this too, but that should largely be an academic problem as pdftex
> is now used anywhere.
No problems here, regarding the inclusion of microtype when using latex
compiler.
However, I'd strongly oppose to the claim that compatibility to the
latex compiler (vs. pdftex) is an academic problem. I know about several
LaTeX based systems that have to use the latex compiler simply because
pdftex can't handle eps graphics and converting those images isn't
feasible. So, while in the current case there's no compatibility issue,
I think it's reasonable to support both compilers.
Ulf
next prev parent reply other threads:[~2010-04-07 9:16 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-30 22:24 IMPORTANT: (possibly) incompatible Change Carsten Dominik
2010-03-31 9:00 ` Chris Gray
2010-03-31 12:35 ` Carsten Dominik
2010-03-31 14:16 ` Eric Schulte
2010-03-31 14:18 ` Carsten Dominik
2010-03-31 18:41 ` Mark Elston
2010-04-01 6:59 ` Carsten Dominik
2010-04-01 11:13 ` Carsten Dominik
2010-04-01 16:17 ` Thomas S. Dye
2010-04-01 16:51 ` Carsten Dominik
2010-04-02 16:25 ` Thomas S. Dye
2010-04-02 1:17 ` Mark Elston
2010-04-02 7:55 ` Carsten Dominik
2010-04-03 18:49 ` Mark Elston
2010-04-03 22:50 ` Henri-Paul Indiogine
2010-04-03 22:55 ` Carsten Dominik
[not found] ` <87pr2gezp9.fsf@belvoir.org>
[not found] ` <A3285E87-A435-4CD9-B5BF-13330A09CE63@gmail.com>
2010-04-04 17:36 ` Henri-Paul Indiogine
2010-04-04 19:44 ` Mark Elston
2010-04-06 11:57 ` Karsten Heymann
2010-04-06 14:53 ` Carsten Dominik
2010-04-03 22:57 ` Carsten Dominik
2010-04-03 23:25 ` Mark Elston
2010-04-04 0:14 ` Carsten Dominik
2010-04-04 5:47 ` Nick Dokos
2010-04-04 6:39 ` Carsten Dominik
2010-04-06 12:30 ` Karsten Heymann
2010-04-06 14:53 ` Carsten Dominik
2010-04-06 16:03 ` Karsten Heymann
2010-04-06 16:23 ` Carsten Dominik
2010-04-06 16:50 ` Karsten Heymann
2010-04-06 18:30 ` Robert Klein
2010-04-06 18:48 ` Thomas S. Dye
2010-04-07 7:37 ` Carsten Dominik
2010-04-07 8:22 ` Karsten Heymann
2010-04-07 8:47 ` Carsten Dominik
2010-04-07 10:31 ` Karsten Heymann
2010-04-07 15:51 ` Thomas S. Dye
2010-04-07 16:00 ` Carsten Dominik
2010-04-10 17:30 ` Mark Elston
2010-04-10 20:01 ` Thomas S. Dye
2010-04-11 3:40 ` Mark Elston
2010-04-07 8:16 ` Karsten Heymann
2010-04-07 7:38 ` Carsten Dominik
2010-04-07 9:15 ` Ulf Stegemann [this message]
2010-04-07 10:30 ` Karsten Heymann
2010-04-07 11:58 ` Ulf Stegemann
2010-04-07 12:24 ` Karsten Heymann
2010-04-02 1:29 ` [PATCH] " Eric Schulte
2010-04-02 2:47 ` Mark Elston
2010-04-02 5:38 ` Carsten Dominik
2010-04-03 16:20 ` Henri-Paul Indiogine
2010-04-03 16:55 ` Carsten Dominik
2010-04-03 17:19 ` Xiao-Yong Jin
2010-04-06 10:25 ` 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=zf.upn39z7sjw9.fsf@zeitform.de \
--to=ulf-news@zeitform.de \
--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
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).