Hi again
I have made a substantial cleanup in the feature branch. It includes
restoring the original language guessing routines for documents prior
to (org-latex-multi-lang-driver).
A bit of background:
The new (org-latex-multi-lang-driver) variable controls how the
headers are generated.
The def
Hey Pedro,
On 2025-06-15 01:24, Pedro Andres Aranda Gutierrez wrote:
> Then we are on the same page on that. I want something flexible but
> easy to understand and use. If it is easy to code, then we are in
> paradise.
Agreed!
My experience with multiple scripts and non-mathematical texts is a
b
Thx for the additional reading materials :-)
Best, /PA
On Mon, 16 Jun 2025 at 21:20, Ihor Radchenko wrote:
>
> Pedro Andres Aranda Gutierrez writes:
>
> > For that, I think we would need to have an extra property in
> > org-latex-language-alist to specfic extra fontencs
> > For example, If I ha
Pedro Andres Aranda Gutierrez writes:
> For that, I think we would need to have an extra property in
> org-latex-language-alist to specfic extra fontencs
> For example, If I have greek, I'll need LGR, if I have russian, I'd
> most probable need T2A for arabic LFE and LAE.
> The default value shou
Hi, I'm calling for help with pdflatex again.
As per now, I would like to add pdflatex as a supported compiler when
using babel.
For that, I think we would need to have an extra property in
org-latex-language-alist to specfic extra fontencs
For example, If I have greek, I'll need LGR, if I have ru
HI, Jacob
On Sat, 14 Jun 2025 at 18:45, Jacob S. Gordon wrote:
>
> Hey Pedro,
>
> On 2025-06-14 02:41, Pedro Andres Aranda Gutierrez wrote:
> > After giving it a thought, I would say that adding a new custom
> > variable to control the default options might do the trick.
> > Something like (in .d
Hey Pedro,
On 2025-06-14 02:41, Pedro Andres Aranda Gutierrez wrote:
> After giving it a thought, I would say that adding a new custom
> variable to control the default options might do the trick.
> Something like (in .dir-locals.el format):
>
> #+BEGIN_SRC elisp
> (org-latex-fontspec-default-fea
Hi
After giving it a thought, I would say that adding a new custom
variable to control the default options might do the trick.
Something like (in .dir-locals.el format):
#+BEGIN_SRC elisp
(org-latex-fontspec-default-features
. (("Path" . "../fonts/")
("Extension" . ".otf")
;-) Look at the last commits in the feature branch.
I hope they will help to provide a cleaner integration path in the future.
Best, /PA
On Fri, 13 Jun 2025 at 20:49, Ihor Radchenko wrote:
> Pedro Andres Aranda Gutierrez writes:
>
> > We can further discuss in the next meetup.
>
> As discussed
Pedro Andres Aranda Gutierrez writes:
> We can further discuss in the next meetup.
As discussed, feel free to do things the easiest way. After things are
working, and after we finalize the general API/user interfaces, we will
come back to ensuring backwards compatibility.
--
Ihor Radchenko //
-- Forwarded message -
From: Pedro Andres Aranda Gutierrez
Date: Fri, 13 Jun 2025 at 19:02
Subject: Re: babel (LaTeX) support in feature/all-tex-fonts branch
To: Jacob S. Gordon
Hi again
answers inline...
On Fri, 13 Jun 2025 at 18:39, Jacob S. Gordon
wrote:
> Hey Pe
Hey Pedro,
On 2025-06-13 01:27, Pedro Andres Aranda Gutierrez wrote:
> The idea behind the current structure is that there might be other
> things beyond the mode that go in the feature list, therefore I
> didn't want it to be that specific
Makes sense! I just mentioned it since the trailing ':'
Hey Jacob
thanks a ton! Answers inline...
On Fri, 13 Jun 2025 at 06:14, Jacob S. Gordon
wrote:
> Hey Pedro,
>
> I just completed some testing on the feature branch, mostly on the
> `fontconfig' side (still asking around for some polyglot documents).
> It went very well; here’s what I did and fo
Hey Pedro,
I just completed some testing on the feature branch, mostly on the
`fontconfig' side (still asking around for some polyglot documents).
It went very well; here’s what I did and found.
+ Compiled each of the [MWE] files you provided from the meetup
(`babel' and `polyglossia') under `l
Hi
On Mon, 9 Jun 2025 at 19:25, Ihor Radchenko wrote:
> Pedro Andres Aranda Gutierrez writes:
>
> > Could make sense.
> > However, I would like to postpone this until I finish the code I'm
> working
> > on right now (give me a week).
>
> Sure. I just got an impression from one of your recent em
Could make sense.
However, I would like to postpone this until I finish the code I'm working
on right now (give me a week).
And I would also like us all to think about the presence of
\usepackage{polyglossia/babel},
because keeping this makes the code really difficult to understand and
maintain.
I
Pedro Andres Aranda Gutierrez writes:
> Could make sense.
> However, I would like to postpone this until I finish the code I'm working
> on right now (give me a week).
Sure. I just got an impression from one of your recent email that the
branch is in near-final state.
> And I would also like us
Pedro Andres Aranda Gutierrez writes:
> It would make then difficult to distinguish between people who want/need
> polyglossia and people who don't, wouldn't it.
> I'd rather not force anyone to load polyglossia if they don't want to use
> it.
Fair. However, I still feel that having to specify l
It would make then difficult to distinguish between people who want/need
polyglossia and people who don't, wouldn't it.
I'd rather not force anyone to load polyglossia if they don't want to use
it.
best, /PA
On Sun, 8 Jun 2025 at 17:27, Ihor Radchenko wrote:
> Pedro Andres Aranda Gutierrez wri
Pedro Andres Aranda Gutierrez writes:
> So, we could have something like
>
> #+LATEX_POLYGLOSSIA_LANGS: AUTO
I rather thought that polyglossia can use #+LANGUAGE value directly and
skip a new keyword altogether.
--
Ihor Radchenko // yantar92,
Org mode maintainer,
Learn more about Org mode at <
Hmmm...
So, we could have something like
#+LATEX_POLYGLOSSIA_LANGS: AUTO
to import all the document languages and define the main? Will see how to
integrate in the feature branch.
Thx, /PA
On Sun, 8 Jun 2025 at 13:01, Ihor Radchenko wrote:
> Pedro Andres Aranda Gutierrez writes:
>
> > I ha
Pedro Andres Aranda Gutierrez writes:
> I have created a new way to control polyglossia for multi-language
> documents (using lualatex or xelatex) There is no need to add the
> \usepackage[langs...]{polyglossia} in the document header anymore. Instead
> you add
>
> #+LATEX_POLYGLOSSIA_LANGS: lang
Pedro Andres Aranda Gutierrez writes:
> I have finally added preliminary support for babel (as in LaTeX package) to
> the feature branch.
> it is activated by the
> #+LATEX_BABEL_LANGS
> header keyword, which substitutes the need for
> #+LATEX_HEADER: \usepackage[...]{babel}
> in the header.
Tha
Hi everybody,
I have finally added preliminary support for babel (as in LaTeX package) to
the feature branch.
it is activated by the
#+LATEX_BABEL_LANGS
header keyword, which substitutes the need for
#+LATEX_HEADER: \usepackage[...]{babel}
in the header.
In addition to that, more complex font setu
Dear all,
I have created a new way to control polyglossia for multi-language
documents (using lualatex or xelatex) There is no need to add the
\usepackage[langs...]{polyglossia} in the document header anymore. Instead
you add
#+LATEX_POLYGLOSSIA_LANGS: lang,lang,AUTO
>From the LaTeX side of the
Hi again,
I continue to test and push fixes to the feature branch. Today I was
testing the use of .dir-local.el to set the fonts and found a quirk that
has been corrected. I encourage you to test your intended font
configurations and share here on the list. In addition to the default value
in the
26 matches
Mail list logo
