On 4/7/2010 1:22 AM, Karsten Heymann wrote:
Carsten Dominikcarsten.domi...@gmail.com writes:
On Apr 6, 2010, at 8:48 PM, Thomas S. Dye wrote:
From the microtype documentation:
The microtype package does not work with XETEX.
Does that mean it will break running XETEX, or will i just be
On Apr 10, 2010, at 7:30 AM, Mark Elston wrote:
On 4/7/2010 1:22 AM, Karsten Heymann wrote:
Carsten Dominikcarsten.domi...@gmail.com writes:
On Apr 6, 2010, at 8:48 PM, Thomas S. Dye wrote:
From the microtype documentation:
The microtype package does not work with XETEX.
Does that
On 4/10/2010 1:01 PM, Thomas S. Dye wrote:
On Apr 10, 2010, at 7:30 AM, Mark Elston wrote:
I am having problems with microtype, here. I don't know if it is
happening in all my docs or just the ones I am working with now but
pdf generation fails with the following in the log:
On Apr 6, 2010, at 8:30 PM, Robert Klein wrote:
On Tue, 06 Apr 2010 18:50:36 +0200, Karsten Heymann karsten.heym...@blue-cable.net
wrote:
Thanks a lot for all this, I will follow your advice.
One final question: Will any of these packages spoil the fun for
people who want to process
Thomas S. Dye t...@tsdye.com writes:
From the microtype documentation:
The microtype package does not work with XETEX.
That's true, but supporting xetex requires many other changes too, for
example only utf-8 input encoding is supported, the inputenc, fontspec
and font packages may not be
Carsten Dominik carsten.domi...@gmail.com writes:
On Apr 6, 2010, at 8:48 PM, Thomas S. Dye wrote:
From the microtype documentation:
The microtype package does not work with XETEX.
Does that mean it will break running XETEX, or will i just be ignored?
It only gives a (harmless) warning:
On Apr 7, 2010, at 10:22 AM, Karsten Heymann wrote:
Carsten Dominik carsten.domi...@gmail.com writes:
On Apr 6, 2010, at 8:48 PM, Thomas S. Dye wrote:
From the microtype documentation:
The microtype package does not work with XETEX.
Does that mean it will break running XETEX, or will i
Hi Ulf,
Ulf Stegemann ulf-n...@zeitform.de writes:
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
Hi Carsten,
Carsten Dominik carsten.domi...@gmail.com writes:
On Apr 7, 2010, at 10:22 AM, Karsten Heymann wrote:
But chances are high that most normal LaTeX documents will not work
with xelatex anyways due to encoding or font selection issues, so I
think unless org-mode aims at explicitely
Hi,
Ulf Stegemann ulf-n...@zeitform.de writes:
But if that wasn't your point, just forget about my remark.
Done :-)
Yours
Karsten
___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
On Apr 7, 2010, at 12:31 AM, Karsten Heymann wrote:
Hi Carsten,
Carsten Dominik carsten.domi...@gmail.com writes:
On Apr 7, 2010, at 10:22 AM, Karsten Heymann wrote:
But chances are high that most normal LaTeX documents will not
work
with xelatex anyways due to encoding or font selection
On Apr 7, 2010, at 5:51 PM, Thomas S. Dye wrote:
On Apr 7, 2010, at 12:31 AM, Karsten Heymann wrote:
Hi Carsten,
Carsten Dominik carsten.domi...@gmail.com writes:
On Apr 7, 2010, at 10:22 AM, Karsten Heymann wrote:
But chances are high that most normal LaTeX documents will not
work
Hi,
Carsten Dominik carsten.domi...@gmail.com writes:
On Apr 4, 2010, at 12:50 AM, Henri-Paul Indiogine wrote:
When I export to LaTeX the line \definecolor. comes before
\usepackage{color} then it throws an error during compilation. If I
move the \definecolor... _after_
Hi Carsten,
a small note:
Carsten Dominik carsten.domi...@gmail.com writes:
[...]
If you have customized the variable org-export-latex-classes, you need
to remove the following lines from each class definition:
\usepackage[AUTO]{inputenc}
\usepackage[T1]{fontenc}
\usepackage{graphicx}
On Apr 6, 2010, at 1:57 PM, Karsten Heymann wrote:
Hi,
Carsten Dominik carsten.domi...@gmail.com writes:
On Apr 4, 2010, at 12:50 AM, Henri-Paul Indiogine wrote:
When I export to LaTeX the line \definecolor. comes before
\usepackage{color} then it throws an error during compilation.
Hi Karsten,
On Apr 6, 2010, at 2:30 PM, Karsten Heymann wrote:
Hi Carsten,
a small note:
Carsten Dominik carsten.domi...@gmail.com writes:
[...]
If you have customized the variable org-export-latex-classes, you
need
to remove the following lines from each class definition:
Hi Carsten,
Carsten Dominik carsten.domi...@gmail.com writes:
On Apr 6, 2010, at 2:30 PM, Karsten Heymann wrote:
Carsten Dominik carsten.domi...@gmail.com writes:
\usepackage[AUTO]{inputenc}
\usepackage[T1]{fontenc}
\usepackage{graphicx}
\usepackage{longtable}
\usepackage{float}
On Apr 6, 2010, at 6:03 PM, Karsten Heymann wrote:
Hi Carsten,
Carsten Dominik carsten.domi...@gmail.com writes:
On Apr 6, 2010, at 2:30 PM, Karsten Heymann wrote:
Carsten Dominik carsten.domi...@gmail.com writes:
\usepackage[AUTO]{inputenc}
\usepackage[T1]{fontenc}
\usepackage{graphicx}
Carsten Dominik carsten.domi...@gmail.com writes:
On Apr 6, 2010, at 6:03 PM, Karsten Heymann wrote:
Carsten Dominik carsten.domi...@gmail.com writes:
On Apr 6, 2010, at 2:30 PM, Karsten Heymann wrote:
Carsten Dominik carsten.domi...@gmail.com writes:
\usepackage[AUTO]{inputenc}
On Tue, 06 Apr 2010 18:50:36 +0200, Karsten Heymann
karsten.heym...@blue-cable.net wrote:
Thanks a lot for all this, I will follow your advice.
One final question: Will any of these packages spoil the fun for
people who want to process through .dvi instead of directly to pdf?
Not as far as
On Apr 6, 2010, at 8:30 AM, Robert Klein wrote:
On Tue, 06 Apr 2010 18:50:36 +0200, Karsten Heymann karsten.heym...@blue-cable.net
wrote:
Thanks a lot for all this, I will follow your advice.
One final question: Will any of these packages spoil the fun for
people who want to process
Carsten Dominik carsten.domi...@gmail.com wrote:
On Apr 4, 2010, at 1:25 AM, Mark Elston wrote:
...
Does anyone know why marvosym is included in this list? I assume
that there is latex code being generated (under some circumstances)
that require it, but I don't know what those
Carsten Dominik carsten.domi...@gmail.com writes:
OK, you can now specify the position where the usepackage definitions
should appear in your header by putting the string
[PACKAGES]
into the header definition in org-export-latex-classes. Default (if
you do
not include this
Henri,
On 4/4/2010 10:36 AM, Henri-Paul Indiogine wrote:
Carsten Dominikcarsten.domi...@gmail.com writes:
OK, you can now specify the position where the usepackage definitions
should appear in your header by putting the string
[PACKAGES]
into the header definition in
Carsten,
Is there a way to *remove* one or more of the packages in
org-export-latex-default-packages-alist? I find that marvosym
is conflicting with one of the packages I use in my notes and
handouts that I generate from org-mode. (marvosym and bbding
both provide a Cross - I don't use that
Hi!
This is what I have in my .emacs
(setq org-export-latex-packages-alist
'(( apacite)
( color)
( tikz)))
(setq org-export-latex-classes
'((book
\\documentclass[11pt]{book}
\\definecolor{darkblue}{rgb}{0.0,0.0,0.3}
\\hypersetup{colorlinks,breaklinks,
On Apr 3, 2010, at 8:49 PM, Mark Elston wrote:
Carsten,
Is there a way to *remove* one or more of the packages in
org-export-latex-default-packages-alist? I find that marvosym
is conflicting with one of the packages I use in my notes and
handouts that I generate from org-mode. (marvosym and
Carsten,
On 4/3/2010 3:57 PM, Carsten Dominik wrote:
On Apr 3, 2010, at 8:49 PM, Mark Elston wrote:
Carsten,
Is there a way to *remove* one or more of the packages in
org-export-latex-default-packages-alist? I find that marvosym
is conflicting with one of the packages I use in my notes and
Hi Mark,
On Apr 4, 2010, at 1:25 AM, Mark Elston wrote:
Carsten,
On 4/3/2010 3:57 PM, Carsten Dominik wrote:
On Apr 3, 2010, at 8:49 PM, Mark Elston wrote:
Carsten,
Is there a way to *remove* one or more of the packages in
org-export-latex-default-packages-alist? I find that marvosym
is
On Apr 2, 2010, at 3:17 AM, Mark Elston wrote:
Carsten,
Thanks for this clarification. This makes the transition much
simpler than I originally thought. I can certainly remove the
common package names.
The existing org-export-latex-classes also contains the
documentclass line. That won't
Aloha Carsten and others,
The Worg FAQ on beamer export describes a setup that isn't up-to-date:
http://orgmode.org/worg/org-faq.php#beamer
All the best,
Tom
On Apr 1, 2010, at 6:51 AM, Carsten Dominik wrote:
On Apr 1, 2010, at 6:17 PM, Thomas S. Dye wrote:
Aloha Carsten,
Packages that
Hi Mark,
OK, it seems that I have really overstated this change. You are of
course right that your header for a document type can be very long,
that that defining it in org-export-latex-classes is a viable option
(other being to put this stuff into a separate file).
So let me restate what I am
OK, this change is now in the master branch.
- Carsten
On Apr 1, 2010, at 8:59 AM, Carsten Dominik wrote:
Hi Mark,
OK, it seems that I have really overstated this change. You are of
course right that your header for a document type can be very long,
that that defining it in
Aloha Carsten,
Packages that aren't used for all classes can still appear in org-
export-latex-classes, correct?
All the best,
Tom
On Apr 1, 2010, at 1:13 AM, Carsten Dominik wrote:
OK, this change is now in the master branch.
- Carsten
On Apr 1, 2010, at 8:59 AM, Carsten Dominik wrote:
On Apr 1, 2010, at 6:17 PM, Thomas S. Dye wrote:
Aloha Carsten,
Packages that aren't used for all classes can still appear in org-
export-latex-classes, correct?
Aloha Tom,
Anything can appear there. But you should not have the packages I
have listed in the new variable
Carsten,
Thanks for this clarification. This makes the transition much
simpler than I originally thought. I can certainly remove the
common package names.
The existing org-export-latex-classes also contains the
documentclass line. That won't change, will it? I am
assuming from what you have
On Mar 31, 2010, at 11:00 AM, Chris Gray wrote:
Carsten Dominik wrote:
-
* =org-export-latex-classes= no longer should be customized for
packages
The HEADER part of this variable should now only contain the
Carsten Dominik carsten.domi...@gmail.com writes:
[...]
Only if you have previously customized org-export-latex-classes in
order to add more usepackage statements, then you should remove your
customization of that variable and list your set of additional
packages in
On Mar 31, 2010, at 4:16 PM, Eric Schulte wrote:
Carsten Dominik carsten.domi...@gmail.com writes:
[...]
Only if you have previously customized org-export-latex-classes in
order to add more usepackage statements, then you should remove your
customization of that variable and list your set
On 3/31/2010 5:35 AM, Carsten Dominik wrote:
On Mar 31, 2010, at 11:00 AM, Chris Gray wrote:
Carsten Dominik wrote:
-
* =org-export-latex-classes= no longer should be customized for packages
...
So if you have
40 matches
Mail list logo
