From: Ihor Radchenko <yantar92@posteo.net>
To: Pedro Andres Aranda Gutierrez <paaguti@gmail.com>
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: Sun, 28 Jan 2024 13:47:12 +0000 [thread overview]
Message-ID: <87zfwpefj3.fsf@localhost> (raw)
In-Reply-To: <CAO48Bk8wzRcrj-Y9mO=9=ZkTQAnLvgX9qQ3sx97wUg7drFCAxg@mail.gmail.com>
Pedro Andres Aranda Gutierrez <paaguti@gmail.com> writes:
>> "Pedro A. Aranda" <paaguti@gmail.com> writes:
>>
>> > I've been reading a bit. What I propose is an alternative way to handle
>> > all the tricky parts of font and character handling with fontspec in
>> > lualatex and xetex. This package restricts the use of the ams* packages
>> > to pdflatex, because fontenc handles that internally and produces
>> > package collisions.
>>
>> > Attached is the final version of the patch.
>>
>> Thanks!
>> May you also add a comment to the code explaining the rationale right
>> there?
> Here you are. I hope the couple of words suffice ;-)
Sorry, I was not clear.
I did not mean to ask about amending the docstring.
I meant literal code comments, explaining why we have duplicate amsmath
entries and why we restrict certain packages to specific compilers.
Also, the above quoted paragraph with rationale of the patch should go
into the commit message. See
https://orgmode.org/worg/org-contribute.html#commit-messages
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
next prev parent reply other threads:[~2024-01-28 13:44 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
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 [this message]
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=87zfwpefj3.fsf@localhost \
--to=yantar92@posteo.net \
--cc=emacs-orgmode@gnu.org \
--cc=maciaschain@posteo.net \
--cc=paaguti@gmail.com \
/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).