Suvayu Ali fatkasuvayu+li...@gmail.com writes:
+(defun org-latex-guess-polyglossia-language (header info)
+ Set the Polyglossia language according to the LANGUAGE keyword.
I'm in two-minds about this. On the one had it is a nice thing, but on
the other hand, it prevents the more fine
Sebastien Vauban sva-n...@mygooglest.com
writes:
FWIW, it seems that people who played with different LaTeX engines used
the LATEX_CMD property, as adviced on Worg [1]. Doesn't matter if we
change that, but just a reminder of some already common usage.
I didn't know that worg page. Just to
Hello,
Rasmus ras...@gmx.us writes:
I have a few other questions:
- how does one change the variant when doing a subtree export? By
setting EXPORT_LATEX_VARIANT?
It seems to work at least to the point that the right engine is written to
the file:
#+LATEX_VARIANT: xelatex
* pdflatex
Hi,
Sebastien Vauban sva-n...@mygooglest.com
writes:
(I'm hesitant to allow arbitrary scripts).
I agree. Just stick to the basic need, which is to be able to easily
change of LaTeX engine.
I'd however also like to allow some flags, e.g. -shell-escape/write18 for
minted. I cannot think of
Rasmus ras...@gmx.us writes:
Sebastien Vauban sva-n...@mygooglest.com writes:
FWIW, it seems that people who played with different LaTeX engines used
the LATEX_CMD property, as adviced on Worg [1]. Doesn't matter if we
change that, but just a reminder of some already common usage.
I didn't
Suvayu Ali fatkasuvayu+li...@gmail.com writes:
The polyglossia bits work well.
The file local variable prompt for every export is quite annoying
though. Same goes for the exported file, opening it brings up the same
prompt again. I guess it is a one time thing to mark that variable as
On Wed, Jul 08, 2015 at 08:35:28PM +0200, Rasmus wrote:
Suvayu Ali fatkasuvayu+li...@gmail.com writes:
+(defun org-latex-guess-polyglossia-language (header info)
+ Set the Polyglossia language according to the LANGUAGE keyword.
I'm in two-minds about this. On the one had it is a nice
Marcin Borkowski mb...@mbork.pl writes:
I would also suggest removing inputenc. At the moment, it is loaded
with the AUTO option. AFAIK, this is redundant since most recent
(meaning for quite a few years) TeX engines already use the encoding of
the file if nothing is specified.
Can you
On 2015-07-07, at 16:53, Rasmus ras...@gmx.us wrote:
Hi,
Hi,
and sorry for my delay – I have a huge email backlog...
We could do some cleaning of org-default-package-alist before Org 8.3.
Yes, yes, yes!
* tolerance
Why is \\tolerance=1000 part of org-default-package-alist? Is this
On 2015-07-07, at 21:35, Suvayu Ali fatkasuvayu+li...@gmail.com wrote:
I would like to second microtype. In fact as far as I know, now a days
it is recommended to load that for almost all documents with significant
text on TeX.SX.
As I wrote a minute ago, I would rather not add microtype,
Hi,
Rasmus ras...@gmx.us writes:
* tolerance
* marvosym¹
* Wasysym²
Pushed.
* Fixltx2e
Will push after 8.3 is released.
Rasmus
--
Dobbelt-A
Hi Robert,
Robert Klein rokl...@roklein.de writes:
* Fixltx2e
This packages is depreciated with TL2015 cf. LaTeX News 22. We can
use \RequirePackage[current]{latexrelease} but there's no point in
that AFAIK latexrelease only useful for backwards compatibility.
Leaving this out
Hi Rasmus,
On Sat, 11 Jul 2015 12:48:06 +0200
Rasmus ras...@gmx.us wrote:
Hi Robert,
Robert Klein rokl...@roklein.de writes:
* Fixltx2e
This packages is depreciated with TL2015 cf. LaTeX News 22. We can
use \RequirePackage[current]{latexrelease} but there's no point in
that
Hello
* Fixltx2e
This packages is depreciated with TL2015 cf. LaTeX News 22. We can
use \RequirePackage[current]{latexrelease} but there's no point in
that AFAIK latexrelease only useful for backwards compatibility.
Leaving this out probably doesn't break texing with older
texlive
On Wed, Jul 08, 2015 at 03:53:32PM +0200, Rasmus wrote:
Suvayu Ali fatkasuvayu+li...@gmail.com writes:
From 54bcf8f1ae26c91fa856b64071dca65d3f31e1f2 Mon Sep 17 00:00:00 2001
From: Rasmus ras...@gmx.us
Date: Wed, 8 Jul 2015 14:44:56 +0200
Subject: [PATCH 9/9] ox-latex: Support TeX
Suvayu Ali fatkasuvayu+li...@gmail.com writes:
We could also take this opportunity to provide users an easy way to
switch between TeX engines.
These two patches goes some of the way towards what you want.
org-latex-pdf-process would also have to patched as well, though.
Test document:
Suvayu Ali fatkasuvayu+li...@gmail.com writes:
I would also suggest removing inputenc. At the moment, it is loaded
with the AUTO option. AFAIK, this is redundant since most recent
(meaning for quite a few years) TeX engines already use the encoding of
the file if nothing is specified.
A
On Wed, Jul 08, 2015 at 02:54:41PM +0200, Rasmus wrote:
Suvayu Ali fatkasuvayu+li...@gmail.com writes:
I would also suggest removing inputenc. At the moment, it is loaded
with the AUTO option. AFAIK, this is redundant since most recent
(meaning for quite a few years) TeX engines already
On Wed, Jul 08, 2015 at 02:53:46PM +0200, Rasmus wrote:
Suvayu Ali fatkasuvayu+li...@gmail.com writes:
We could also take this opportunity to provide users an easy way to
switch between TeX engines.
These two patches goes some of the way towards what you want.
org-latex-pdf-process
Suvayu Ali fatkasuvayu+li...@gmail.com writes:
From 54bcf8f1ae26c91fa856b64071dca65d3f31e1f2 Mon Sep 17 00:00:00 2001
From: Rasmus ras...@gmx.us
Date: Wed, 8 Jul 2015 14:44:56 +0200
Subject: [PATCH 9/9] ox-latex: Support TeX variants
This one fails to apply for me. I'm on
You probably
Suvayu Ali fatkasuvayu+li...@gmail.com writes:
Indeed, and it works very nicely!
Let me know when you find bugs.
I'm trying to think of an elegant way to map from a tex-variant to a
command. Perhaps change the variant names to the latex variants and input
that. E.g. if using plain commands,
On Wed, Jul 08, 2015 at 04:26:56PM +0200, Rasmus wrote:
I'm trying to think of an elegant way to map from a tex-variant to a
command. Perhaps change the variant names to the latex variants and input
that.
I think that would be a good way to go.
--
Suvayu
Open source is the future. It
Hi,
Suvayu Ali fatkasuvayu+li...@gmail.com writes:
+(defun org-latex-guess-polyglossia-language (header info)
+ Set the Polyglossia language according to the LANGUAGE keyword.
I'm in two-minds about this. On the one had it is a nice thing, but on
the other hand, it prevents the more fine
Hi Rasmus,
On Wed, Jul 08, 2015 at 02:53:46PM +0200, Rasmus wrote:
+(defun org-latex-guess-polyglossia-language (header info)
+ Set the Polyglossia language according to the LANGUAGE keyword.
I'm in two-minds about this. On the one had it is a nice thing, but on
the other hand, it prevents
Suvayu Ali fatkasuvayu+li...@gmail.com writes:
+(defun org-latex-guess-polyglossia-language (header info)
+ Set the Polyglossia language according to the LANGUAGE keyword.
I'm in two-minds about this. On the one had it is a nice thing, but on
the other hand, it prevents the more fine
On Tuesday, 7 Jul 2015 at 16:53, Rasmus wrote:
Hi,
We could do some cleaning of org-default-package-alist before Org 8.3.
Rasmus,
I'm happy with all of your suggested removals.
--
: Eric S Fraga (0xFFFCF67D), Emacs 25.0.50.1, Org release_8.3beta-1260-gcedef7
Hi Rasmus,
On Tue, Jul 07, 2015 at 04:53:35PM +0200, Rasmus wrote:
If it's a means to archive high-quality paragraphs, maybe microtype is
probably the 'proper' fix...
I would like to second microtype. In fact as far as I know, now a days
it is recommended to load that for almost all
Suvayu Ali fatkasuvayu+li...@gmail.com writes:
I would like to second microtype. In fact as far as I know, now a days
it is recommended to load that for almost all documents with significant
text on TeX.SX.
It's easy enough to add and we should keep the default minimal. Though
microtype is
Suvayu Ali fatkasuvayu+li...@gmail.com writes:
Yes, but polyglossia is recommended. In the interest of minimal work on
the part of Org, this could just be ignored. I don't think we add babel
anyway, or do we?
I thought we did, but we don't. Anyway, babel works across different tex
backends
On Tue, Jul 07, 2015 at 10:05:06PM +0200, Rasmus wrote:
Suvayu Ali fatkasuvayu+li...@gmail.com writes:
\usepackage{polyglossia} % instead of babel
You can use babel with xelatex.
Yes, but polyglossia is recommended. In the interest of minimal work on
the part of Org, this could just
30 matches
Mail list logo
