On 11/07/2022 21:23, Juan Manuel Macías wrote:
Max Nikulin writes:
\\ifpdftex
\\relax
\\else
Is it the case of latex as the old engine with tex->dvi->ps workflow
besides new XeTeX and LuaTeX? However such engine is not used by Org.
According to the iftex documentation (p. 2):
Hi Juan,
> When you talk about fontset, I understand that you mean lists of
> families with their options that you have previously defined, is that
> right?
Yep, so in my config’s implementation I have an alist of fontset names and
individual fonts. For something part of org-mode itself, we’d
On 11/07/2022 21:23, Juan Manuel Macías wrote:
Max Nikulin writes:
\ifpdftex, \ifPDFTeX
True if PDFTEX is in use (whether writing PDF or DVI), so this is true
for documents processed with both the latex and pdflatex commands.
So the code says: if pdfTeX is used, do nothing; else, add this
Timothy writes:
> As an illustrative example, if I include this in one of my documents and
> create
> a PDF:
> ┌
> │ #+options: fontset:biolinum
> └
>
> Then I’ll get text with:
> ⁃ libertine roman as the serif font
> ⁃ biolinum as the serif, and default, font
> ⁃ source code pro as the
Max Nikulin writes:
>> \\relax
>> \\else
>
> Is it the case of latex as the old engine with tex->dvi->ps workflow
> besides new XeTeX and LuaTeX? However such engine is not used by Org.
According to the iftex documentation (p. 2):
\ifpdftex, \ifPDFTeX
True if PDFTEX is in use (whether
Hi Ihor & co.,
> As I recall, Timothy has been working on simplifying preamble
> generation. If we do not put unnecessary packages into preamble,
> compilation will be significantly faster.
>
> If Timothy can come up with a patch some time soon, I’d prefer to have a
> more targeted preamble.
Tim Cross writes:
> Juan, if I understand your proposal correctly, I think your on the right
> track. It sounds like what you are proposing would have almost no impact
> on basic users like me, but would allow those with more demanding
> requirements to adjust without too much effort. I
On 11/07/2022 03:23, Juan Manuel Macías wrote:
3. A variable (something like 'org-latex-fontspec-default-configuration') would
return something like this:
(format
\\usepackage{iftex}
\\ifpdftex
I like the idea of unified preamble suitable for pdflatex and lualatex.
For pdftex
Juan Manuel Macías writes:
> By the way, although I've already commented on it in some post in the
> parent thread, i think this package I wrote might be useful for doing a
> quick visual test of a font (including opentype features test), using
> org-latex-preview (compiling with LuaTeX). It can
Stefan Nobis writes:
> Juan Manuel Macías writes:
>
>> 1. There could be a defcustom, something like 'org-latex-use-fontspec'
>> (I would vote for nil by default).
>
> I would vote to activate this by default.
I voted nil because of the available fonts issue. But I think what you
say below is a
Juan Manuel Macías writes:
> 1. There could be a defcustom, something like 'org-latex-use-fontspec'
> (I would vote for nil by default).
I would vote to activate this by default.
> (format
> \\usepackage{iftex}
> \\ifpdftex
> \\relax
> \\else
> \\usepackage{fontspec}
>
Ihor Radchenko writes:
> But can someone check if Free* fonts are available on Windows and
> Mac by default?
I just checked TeXLive (on MacOS, but should be the same on all
systems): The Free* fonts are part of TeXLive as truetype and as
opentype versions (and partly in other formats).
For
Juan Manuel,
> 1. There could be a defcustom, something like 'org-latex-use-fontspec'
> (I would vote for nil by default).
i just wanted to check: the "nil" case is for those of us who just want
it to work "out of the box"?
and, in the non-nil case, it would be up to the user to use "fontspec",
Juan Manuel Macías writes:
> Considering some discussions in the parent thread, I think maybe it
> wouldn't hurt to ensure a minimal preamble when the output is compiled
> with LuaLaTeX or XelaTeX, so that some very basic fontspec configuration
> is loaded to be able to read PDFs in non-Latin
Juan Manuel Macías writes:
> Considering some discussions in the parent thread, I think maybe it
> wouldn't hurt to ensure a minimal preamble when the output is compiled
> with LuaLaTeX or XelaTeX, so that some very basic fontspec configuration
> is loaded to be able to read PDFs in non-Latin
Sorry, I forgot to add quotes :-) "\\usepackage{iftex}...\\fi"
Juan Manuel Macías writes:
> (format
> \\usepackage{iftex}
> \\ifpdftex
> \\relax
> \\else
> \\usepackage{fontspec}
> \\usepackage{unicode-math}
> \\defaultfontfeatures{Scale=MatchLowercase}
>
Considering some discussions in the parent thread, I think maybe it
wouldn't hurt to ensure a minimal preamble when the output is compiled
with LuaLaTeX or XelaTeX, so that some very basic fontspec configuration
is loaded to be able to read PDFs in non-Latin scripts.
But before proposing the
17 matches
Mail list logo
