From: Pedro Andres Aranda Gutierrez <paaguti@gmail.com>
To: "Juan Manuel Macías" <maciaschain@posteo.net>
Cc: Ihor Radchenko <yantar92@posteo.net>,
Org Mode List <emacs-orgmode@gnu.org>
Subject: Re: [RFC] LaTeX - automatically configure encoding when exporting non-Latin languages
Date: Fri, 2 Feb 2024 17:41:56 +0100 [thread overview]
Message-ID: <F06D58FD-1316-47A9-9C66-1DAECA4D814E@gmail.com> (raw)
In-Reply-To: <87plxe6ds6.fsf@posteo.net>
Hi,
I’m just trying to cover the “legacy” latex.
I’ve finally migrated to lualatex for my stuff, and it has really been worthwhile. But who knows what a conference might want me to use ;-P
Differentiating between pdflatex and lualatex was what my last patch was for.
I also sent a PoC for the fontenc stuff a couple of weeks ago. And I was trying to continue this work and collect info needed for handling fontenc when you need pdflatex as your latex compiler.
Best, /PA
> El 2 feb 2024, a las 17:18, Juan Manuel Macías <maciaschain@posteo.net> escribió:
>
> Ihor Radchenko writes:
>
>> #+LANGUAGE: fa
>> #+LaTeX_Header: \usepackage[AUTO]{polyglossia}
>>
>> #+latex_header: \usepackage[AUTO]{fontspec}
>
> I think Pedro is referring to fontenc not fontspec. fontenc cannot be
> used in either lualatex or XelaTeX. fontspec is for advanced selection
> of truetype and opentype fonts in XeLatex and LuaLaTeX and setting
> opentype properties. fontenc is for 'pre-Unicode' LaTeX font encoding. I
> would say that what Pedro proposes is limited only to the output in
> pdfTeX.
>
> --
> Juan Manuel Macías -- Composición tipográfica, tratamiento de datos, diseño editorial y ortotipografía
>
prev parent reply other threads:[~2024-02-02 16:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-01 7:07 RFI: LaTeX - AUTO for \usepackage{inputenc} Pedro Andres Aranda Gutierrez
2024-02-01 16:35 ` Ihor Radchenko
2024-02-01 16:33 ` Pedro Andres Aranda Gutierrez
2024-02-02 16:00 ` [RFC] LaTeX - automatically configure encoding when exporting non-Latin languages Ihor Radchenko
2024-02-02 16:18 ` Juan Manuel Macías
2024-02-02 16:41 ` Pedro Andres Aranda Gutierrez [this message]
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=F06D58FD-1316-47A9-9C66-1DAECA4D814E@gmail.com \
--to=paaguti@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=maciaschain@posteo.net \
--cc=yantar92@posteo.net \
/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).