Re: [DISCUSSION] Setting LuaLaTeX as default when exporting to LaTeX/PDF

2025-04-10 Thread Max Nikulin
On 09/04/2025 05:03, Juergen Fenn wrote: only luatex is capable of producing accessible pdf, [...] This is not only a ITF-8 issue. I'm surprised TeX Live is said not to work properly out of the box on some Linux distributions, hard to believe it's true. My conclusion from earlier discussions

Re: Re: [DISCUSSION] Setting LuaLaTeX as default when exporting to LaTeX/PDF

2025-04-10 Thread Pedro Andres Aranda Gutierrez
>Date: Thu, 10 Apr 2025 21:55:53 +0700 >From: Max Nikulin >To: emacs-orgmode@gnu.org >Subject: Re: [DISCUSSION] Setting LuaLaTeX as default when exporting >to LaTeX/PDF >Message-ID: >Content-Type: text/plain; charset=UTF-8; format=flowed > Answers inline Max wrote: >On 09/04/2025 05:03, J

Re: [BUG] C-c C-c doesn't update checkbox after making ready-only file read-write [9.7.11 (release_9.7.11 @ /usr/new/share/emacs/31.0.50/lisp/org/)]

2025-04-10 Thread Mike Kupfer
Ihor Radchenko wrote: > I can reproduce. However, I cannot reproduce on the latest bugfix and on > the latest main. Try to upgrade Org mode and let me know if you keep > seeing the problem. I tried 9.7.27 (latest available from GNU ELPA) and main (downloaded today). The good news is that I can n

Re: Image inlining patch

2025-04-10 Thread Ihor Radchenko
Pedro Andres Aranda Gutierrez writes: > Attached is a new version of the patch. It builds on Ihors refactoring > patch. > Best. /PA Thanks! I toyed around with the patch and I feel that we might be breaking an important use case without recovery. Consider something like #+attr_latex: :centerin

Re: [PATCH]: add BEAMER_CLASS_OPTIONS

2025-04-10 Thread David Masterson
Pedro Andres Aranda Gutierrez writes: > Good point, maybe I didn't explain clearly enough. > #+BEAMER_CLASS_OPTIONS: will only take effect when exporting to > BEAMER. It is enforced in (org-beamer-template) when and if > present. You can always continue using #+LATEX_CLASS: and > #+LATEX_CLASS_O

Re: [DISCUSSION] Setting LuaLaTeX as default when exporting to LaTeX/PDF

2025-04-10 Thread Colin Baxter
> Arne Babenhauserheide writes: > Juergen Fenn writes: >> Am 03.04.25 um 09:37 Uhr schrieb Ihor Radchenko: I don't agree. Users who are apparently happy with LuaLaTeX should have no problems with pdflatex and UTF8. >>> If you know an easy and universal way to su

Re: [PATCH]: add BEAMER_CLASS_OPTIONS

2025-04-10 Thread Pedro Andres Aranda Gutierrez
Hmmm... Isn't it enough to it select with #STARTUP: beamer I have not used any alternative class to 'beamer' when using beamer... After all these years, I'd be 8-0 to learn you can use other latex classes to generate beamer presentations... but again, could be another instance of the proverb "you

Re: [DISCUSSION] Setting LuaLaTeX as default when exporting to LaTeX/PDF

2025-04-10 Thread Juergen Fenn
Am 10.04.25 um 07:59 Uhr schrieb Pedro Andres Aranda Gutierrez: > Now the question seems to be whether latex-preview could "live an > independent life" with pdflatex at the heart of it's tooling, whereas > document production could "move on" to use lualatex as the default tool > to generate the

Re: [DISCUSSION] Setting LuaLaTeX as default when exporting to LaTeX/PDF

2025-04-10 Thread Dr. Arne Babenhauserheide
Juergen Fenn writes: > Am 10.04.25 um 07:59 Uhr schrieb Pedro Andres Aranda Gutierrez: >> Now the question seems to be whether latex-preview could "live an >> independent life" with pdflatex at the heart of it's tooling, whereas >> document production could "move on" to use lualatex as the defaul

Re: [DISCUSSION] Setting LuaLaTeX as default when exporting to LaTeX/PDF

2025-04-10 Thread Pedro Andres Aranda Gutierrez
Hi, This is my concern too… and the reason for me to ask if we have someone onboard with enough experience in AucTeX and latex-preview to give a full pros and cons for using it (or not). Regarding font management (see parallel thread on this), the situation is a slight bit better, because ther

Q: Export if *not* using a particular backend?

2025-04-10 Thread David Masterson
Is there a way to export a section of an Org file only if the export backend is *NOT* a particular backend? For instance, some things don't work in Texinfo, but are fine in HTML and LATEX. Is there a generalized IF for processing an Org file? -- David Masterson