emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Pedro A. Aranda" <paaguti@gmail.com>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: "Juan Manuel Macías" <maciaschain@posteo.net>,
	"Org Mode List" <emacs-orgmode@gnu.org>
Subject: Re: New try at multi-lingual export to latex/pdf using pdflatex and babel
Date: Thu, 25 Jan 2024 08:25:29 +0100	[thread overview]
Message-ID: <235ab244-f7fb-4bb9-bac1-8676b6f1897a@gmail.com> (raw)
In-Reply-To: <878r4eg0m7.fsf@localhost>

Hi again

As stated, this was only a PoC. If you find it useful, I would give it a 
go in the free window. I'm also playing with 
org-latex-default-packages-alist, refining it to use fontspec in 
lualatex and xetex and restricting inputenc and fontenc to pdflatex only.

Best, /PA

On 24/1/24 17:25, Ihor Radchenko wrote:
> Pedro Andres Aranda Gutierrez <paaguti@gmail.com> writes:
>
>> Attached is a _proof of concept_ for supporting AUTO in
>> \usepackage{fontenc}. Just an idea of how things could evolve.
>> This only uses a variable you can define as directory or file local to
>> control what is generated in the LaTeX file.
>> Could be expanded in the future to check #+language:
> Thanks!
>
>> +(defcustom org-latex-fontenc "T1"
>> +  "The fontenc for the file. Customise to LGR,T1 when including
>> +Greek, etc."
>> +  :group 'org-export-latex
>> +  :type 'string
>> +  :safe #'stringp)
> Is there a list of available values somewhere?
> https://latexref.xyz/fontenc-package.html only lists OT1, OMS, OML, T1,
> and TS1. However, many more are clearly available.
>


  reply	other threads:[~2024-01-25  7:26 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-21  8:44 New try at multi-lingual export to latex/pdf using pdflatex and babel Pedro Andres Aranda Gutierrez
2024-01-21 13:02 ` Ihor Radchenko
2024-01-21 17:11   ` Pedro Andres Aranda Gutierrez
2024-01-21 17:47     ` Juan Manuel Macías
2024-01-22  6:30       ` Pedro Andres Aranda Gutierrez
2024-01-22  6:47         ` Pedro Andres Aranda Gutierrez
2024-01-22 13:11           ` Juan Manuel Macías
2024-01-22 12:10       ` Ihor Radchenko
2024-01-22 13:40         ` Juan Manuel Macías
2024-01-23  7:41           ` Pedro Andres Aranda Gutierrez
2024-01-24 16:25             ` Ihor Radchenko
2024-01-25  7:25               ` Pedro A. Aranda [this message]
2024-01-25 13:41                 ` Ihor Radchenko
2024-01-25 16:54                   ` Pedro A. Aranda
2024-01-26 13:28                     ` Ihor Radchenko
2024-01-26 17:49                       ` Pedro Andres Aranda Gutierrez
2024-01-28 13:47                         ` Ihor Radchenko
2024-01-28 17:02                           ` Pedro Andres Aranda Gutierrez
2024-01-29 13:28                             ` Ihor Radchenko
2024-01-29 14:34                               ` Pedro Andres Aranda Gutierrez
2024-01-29 14:51                                 ` Ihor Radchenko
2024-01-29 14:51                                   ` Pedro Andres Aranda Gutierrez
2024-02-09 23:10     ` Ihor Radchenko
2024-02-10  6:13       ` Pedro Andres Aranda Gutierrez
2024-02-10 14:39         ` Ihor Radchenko
2024-02-11  6:22           ` Pedro Andres Aranda Gutierrez
2024-02-11 11:04             ` Juan Manuel Macías
2024-04-15 12:21               ` Ihor Radchenko
2024-04-22 20:06                 ` Ihor Radchenko

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=235ab244-f7fb-4bb9-bac1-8676b6f1897a@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).