Re: Org mode projects during the FSF 40th anniversary hackathon?

2025-05-28 Thread Pedro Andres Aranda Gutierrez
Thanks for the feedback! Will register proposal. Best, /PA On Wed, 28 May 2025 at 08:42, Bastien Guerry wrote: > Hi Pedro, > > Pedro Andres Aranda Gutierrez writes: > > > People using proven setups for languages others cannot decode (I'd be > > the first in the

Re: Org mode projects during the FSF 40th anniversary hackathon?

2025-05-27 Thread Pedro Andres Aranda Gutierrez
Hi Bastien, thanks for the pointer. Sounds really interesting. The 'final push' to the feature/all-tex-fonts branch could be a nice thing to work on. It could be an opportunity 1. to make sure the lua/xelatex implementation doesn't produce unusable output 2. to share ideas/discuss the implementa

Re: Re: Question about contribution to improve svg handling in latex export

2025-05-22 Thread Pedro Andres Aranda Gutierrez
Hi Thomas, Thanks for sharing your experience. I'd need that for the font feature branch ;-) Answers inline... Thomas Redelberger schrieb: > When I generate LaTeX/Beamer PDFs from Org mode, I get > 1. directory "svg-inkscape" containing one PDF file for each SVG I link in the Org file (SVG from

Change in the way polyglossia is handled in the feature/all-tex-fonts

2025-05-20 Thread Pedro Andres Aranda Gutierrez
Dear all, I have created a new way to control polyglossia for multi-language documents (using lualatex or xelatex) There is no need to add the \usepackage[langs...]{polyglossia} in the document header anymore. Instead you add #+LATEX_POLYGLOSSIA_LANGS: lang,lang,AUTO >From the LaTeX side of the

Re: State of the feature branch - An update

2025-05-19 Thread Pedro Andres Aranda Gutierrez
HI, On Sat, 17 May 2025 at 18:10, Ihor Radchenko wrote: > Pedro Andres Aranda Gutierrez writes: > > >> I think that we can take inspiration from > >> https://tecosaur.github.io/emacs-config/config.html#font-collections > >> and introduce an idea of font colle

Re: State of the feature branch - An update

2025-05-18 Thread Pedro Andres Aranda Gutierrez
Best, /PA On Mon, 19 May 2025 at 07:58, Pedro Andres Aranda Gutierrez < paag...@gmail.com> wrote: > HI, > > On Sat, 17 May 2025 at 18:10, Ihor Radchenko wrote: > >> Pedro Andres Aranda Gutierrez writes: >> >> >> I think that we can take inspiration from

Re: State of the feature branch - An update

2025-05-18 Thread Pedro Andres Aranda Gutierrez
A really cool page for people with some experience in Emacs. Lots of cool ideas I need to look at. The only downside is the "some experience". What about people who are starting? I can tell any student/coworker to install a pure Emacs and TeXLive and to pull any of the documents in the ZIP file fro

Re: Notable past discussions related to exporting non-latin org documents to latex

2025-05-18 Thread Pedro Andres Aranda Gutierrez
This is great, thank you so much! PA On Sun, 18 May 2025 at 13:11, Ihor Radchenko wrote: > Hi, > > Here is a list of past discussions that could be useful to look through: > > 1. https://list.orgmode.org/orgmode/87h6z7jq4o.fsf@localhost/ >RTL language export (a bug report) > > 2. https://lis

Re: State of the feature branch - An update

2025-05-17 Thread Pedro Andres Aranda Gutierrez
Hi Ihor, Thanks! A lot to digest ;-) First reactions inline. On Sat, 17 May 2025 at 15:07, Ihor Radchenko wrote: > Pedro Andres Aranda Gutierrez writes: > > > @Ihor: do we want this integrated in the existing sections, or does a new > > section of multi-lingual for LaTeX

More things after playing with polyglossia

2025-05-15 Thread Pedro Andres Aranda Gutierrez
Hi again, I have continued playing with the Hebrew example on main (shortly) and the feature branch and added a couple more of findings to it. Attached is the org file and generated output. Can someone speaking Hebrew confirm that the output "makes sense" ;-) I really have no clue. Just played wit

Re: The slides I used yesterday in the meetup

2025-05-15 Thread Pedro Andres Aranda Gutierrez
rid of the #+LATEX_HEADER lines that control fonts. Could be a buffer-local variable as org-latex-fontspec-config WDYT?, /PA On Thu, 15 May 2025 at 12:43, Pedro Andres Aranda Gutierrez < paag...@gmail.com> wrote: > Hi again, > > During the meetup, the matter of bidirectional came

Re: The slides I used yesterday in the meetup

2025-05-15 Thread Pedro Andres Aranda Gutierrez
Hi again, During the meetup, the matter of bidirectional came up. On Thu, 15 May 2025 at 07:10, Pedro Andres Aranda Gutierrez < paag...@gmail.com> wrote: > Hi > > just for reference and in case anyone is interested. > > /PA > -- > Fragen sind nicht da, um beantwortet

The slides I used yesterday in the meetup

2025-05-14 Thread Pedro Andres Aranda Gutierrez
Hi just for reference and in case anyone is interested. /PA -- Fragen sind nicht da, um beantwortet zu werden, Fragen sind da um gestellt zu werden Georg Kreisler Sagen's Paradeiser, write BE! Year 1 of the New Koprocracy all-tex-fonts-handout.pdf Description: Adobe PDF document

Re: Re: Question about contribution to improve svg handling in latex export

2025-05-13 Thread Pedro Andres Aranda Gutierrez
HI, I find the topic really interesting. Let's see what reactions we have the call tomorrow re. the fontspec integration and then we can progress on the image-inlining and integrating this feature. I have resorted to using the converter provided by the rsvg package externally and including the PD

UPDATE: all-tex-fonts feature branch

2025-05-09 Thread Pedro Andres Aranda Gutierrez
HI, I have pushed some refinements to the feature branch, which should be now ready for more general testing. I plan to attend the meetup next Wednesday to make a short presentation and demonstration of what I have achieved. If someone feels adventurous enough, feedback will always be welcome ;-)

Re: Question about contribution to improve svg handling in latex export

2025-05-03 Thread Pedro Andres Aranda Gutierrez
Wasn’t there rsvg-convert as a CLI friendly alternative? /PA while shopping;-) Enviado desde mi iPhone > El 2 may 2025, a las 18:57, Ihor Radchenko escribió: > > Emin Martinian writes: > >> Briefly speaking, the current latex export of SVG files does not work out >> of the box and requires ad

Re: Question about contribution to improve svg handling in latex export

2025-05-03 Thread Pedro Andres Aranda Gutierrez
We could give it a try. Although I would have to do some archeology in my mails because this rings a bell about potential problems I dimly remember encountering when writing my PhD thesis. It may be the integration of Inkscape and the shell for some OSes outside Linux. Just my .2 cents PA Envia

Progress on the feature/all-tex-fonts branch

2025-05-01 Thread Pedro Andres Aranda Gutierrez
Hi again, I continue to test and push fixes to the feature branch. Today I was testing the use of .dir-local.el to set the fonts and found a quirk that has been corrected. I encourage you to test your intended font configurations and share here on the list. In addition to the default value in the

Fwd: features/all-tex-fonts

2025-04-30 Thread Pedro Andres Aranda Gutierrez
I have a problem in my address book... -- Forwarded message - From: Pedro Andres Aranda Gutierrez Date: Wed, 30 Apr 2025 at 17:43 Subject: features/all-tex-fonts To: , Ihor Radchenko HI, It will be buggy and have things to fine tune. So, the most adventurous are invited to

Re: New branch in the org-mode git repo

2025-04-26 Thread Pedro Andres Aranda Gutierrez
Thx, /PA On Sun, 27 Apr 2025 at 07:50, Ihor Radchenko wrote: > Pedro Andres Aranda Gutierrez writes: > > > I have pushed a modified version of Juan Manuel Macías' char-set listing > > function. You can try it out from the scratch buffer with > > Note that you

Re: New branch in the org-mode git repo

2025-04-26 Thread Pedro Andres Aranda Gutierrez
(org-latex--get-doc-scripts)) --- cut here --- To check what char-scripts you are using in your documents. Best, /PA On Sat, 26 Apr 2025 at 09:26, Pedro Andres Aranda Gutierrez < paag...@gmail.com> wrote: > Dear all, > > I have pushed a *highly experimental* branch to the git repo calle

New branch in the org-mode git repo

2025-04-26 Thread Pedro Andres Aranda Gutierrez
Dear all, I have pushed a *highly experimental* branch to the git repo called feature/all-tex-fonts to try to crystallise our discussions into something more material. WARNING: It'll take a couple of days before it provides a first functional implementation. TIA for any feedback, /PA -- Fragen

Re: Towards a new TeX font management

2025-04-24 Thread Pedro Andres Aranda Gutierrez
My fault... /PA On Thu, 24 Apr 2025 at 18:12, Max Nikulin wrote: > On 23/04/2025 23:08, Pedro Andres Aranda Gutierrez wrote: > > +++ b/lisp/org.el > > > - '(;; amsmath before fontspec for lualatex and xetex > > -("" "amsmath" t (&

Re: Towards a new TeX font management

2025-04-24 Thread Pedro Andres Aranda Gutierrez
In the final version, it will be unicode-math for xetex and lualatex. I recently learnt through Ihor that mathspec is deprecated. Thx, /PA On Thu, 24 Apr 2025 at 17:19, Max Nikulin wrote: > On 23/04/2025 22:36, Pedro Andres Aranda Gutierrez wrote: > > Subject: [PATCH] Use the same pa

Re: Towards a new TeX font management

2025-04-24 Thread Pedro Andres Aranda Gutierrez
Best regards > Robert > > On Wed, 23 Apr 2025 16:31:12 +0000 > Ihor Radchenko wrote: > > > Pedro Andres Aranda Gutierrez writes: > > > > > This should be the good one. Apologies... > > > > Thanks! > > > > > Subject: [PATCH] Update org-l

Fwd: Towards a new TeX font management

2025-04-23 Thread Pedro Andres Aranda Gutierrez
-- Forwarded message - From: Pedro Andres Aranda Gutierrez Date: Wed, 23 Apr 2025 at 17:58 Subject: Re: Towards a new TeX font management To: Ihor Radchenko No, you suggested to use unicode-math for xetex and lualatex and it is fine with me. Best, /PA On Wed, 23 Apr 2025 at

Re: Towards a new TeX font management

2025-04-23 Thread Pedro Andres Aranda Gutierrez
This should be the good one. Apologies... /PA On Wed, 23 Apr 2025 at 18:00, Ihor Radchenko wrote: > Pedro Andres Aranda Gutierrez writes: > > > No, you suggested to use unicode-math for xetex and lualatex and it is > > fine with me. > > But the patch

Towards a new TeX font management

2025-04-23 Thread Pedro Andres Aranda Gutierrez
cracy From 7f29f18060b41f9200567248c5462898eba14547 Mon Sep 17 00:00:00 2001 From: "Pedro A. Aranda" Date: Sun, 20 Apr 2025 11:04:23 +0200 Subject: [PATCH] Use the same packages as pandoc Preparing the font management infrastructure, align with pandoc * lisp/org.el: org-latex-default-pa

Re: Fwd: [PATCH]: Add font specifications when exporting to LaTeX

2025-04-23 Thread Pedro Andres Aranda Gutierrez
doubting between CMU and Noto) and if your document needs other fallbacks, fonts, etc. you can add them in your emacs init code or in a dir-local variable. Let's hope that I get (eventually) write access to the git and can create a feature branch to push experiments and have people play with

Re: Fwd: [PATCH]: Add font specifications when exporting to LaTeX

2025-04-22 Thread Pedro Andres Aranda Gutierrez
Answers inlne On Tue, 22 Apr 2025 at 18:55, Max Nikulin wrote: > On 21/04/2025 18:07, Pedro Andres Aranda Gutierrez wrote: > > I could try to go for something like: > > > > (defvar org-latex-font-fallback-alist > >'(("main . &#x

Re: Fwd: [PATCH]: Add font specifications when exporting to LaTeX

2025-04-21 Thread Pedro Andres Aranda Gutierrez
There will be some repetition in the nested alists and it will be more complex to handle customisations. But anyhow, give me some time to check what can be done and then discuss the possible solutions. /PA On Mon, 21 Apr 2025 at 12:50, Ihor Radchenko wrote: > Pedro Andres Aranda Gutier

Fwd: [PATCH]: Add font specifications when exporting to LaTeX

2025-04-20 Thread Pedro Andres Aranda Gutierrez
I had forgotten the list... sorry. To add to the message, I scan the buffer for charsets using a variant of the code proposed by Juan Manuel Macías some time ago... Sorry and Best, /PA -- Forwarded message - From: Pedro Andres Aranda Gutierrez Date: Sun, 20 Apr 2025 at 15:34

Re: [PATCH]: Add font specifications when exporting to LaTeX

2025-04-20 Thread Pedro Andres Aranda Gutierrez
Answers inline /PA On Sun, 20 Apr 2025 at 13:51, Ihor Radchenko wrote: > Pedro Andres Aranda Gutierrez writes: > > > this is the first of a series of patches for font management. This one is > > independent of the > > fallback or font selection mechanism. So I

Re: [PATCH]: Add font specifications when exporting to LaTeX

2025-04-19 Thread Pedro Andres Aranda Gutierrez
Of course, I'll check out! /PA On Sat, 19 Apr 2025 at 16:11, Ihor Radchenko wrote: > Pedro Andres Aranda Gutierrez writes: > > >> I've attached an example .tex (lualatex) file, with bits and pieces from > >> many discussions at tex.stackexchange and elsewhere.

Re: [PATCH]: Add font specifications when exporting to LaTeX

2025-04-18 Thread Pedro Andres Aranda Gutierrez
Hi Max, Answers inline. On Fri, 18 Apr 2025 at 19:05, Max Nikulin wrote: > On 18/04/2025 15:13, Pedro Andres Aranda Gutierrez wrote: > > > > I think that trying to address all mappings out-of-the-box is not very > > realistic and would add too much noise. > > J

Re: [PATCH]: Add font specifications when exporting to LaTeX

2025-04-18 Thread Pedro Andres Aranda Gutierrez
And the file ;-) /PA On Fri, 18 Apr 2025 at 10:12, Pedro Andres Aranda Gutierrez < paag...@gmail.com> wrote: > HI again > > I've attached an example .tex (lualatex) file, with bits and pieces from > many discussions at tex.stackexchange and elsewhere. > The structure wo

Re: [PATCH]: Add font specifications when exporting to LaTeX

2025-04-18 Thread Pedro Andres Aranda Gutierrez
pings I think that trying to address all mappings out-of-the-box is not very realistic and would add too much noise. This option can be (easily?) tailored to everybody's needs, without imposing too much burden on anybody. WDYT, /PA On Fri, 18 Apr 2025 at 07:42, Pedro Andres Aranda Gutier

Re: [PATCH]: Add font specifications when exporting to LaTeX

2025-04-17 Thread Pedro Andres Aranda Gutierrez
HI, interesting... I have been giving this a thought, Maybe what we should have are two things: 1. an alist for setting the main, sans and mono font with a reasonable default value (Free... seems to be available by default in a quite cross-OS manner - I'm testing with macOS, a couple of

Re: [PATCH]: add BEAMER_CLASS_OPTIONS

2025-04-15 Thread Pedro Andres Aranda Gutierrez
mentclass[a4paper,twoside,11pt]{article} So apparently, overwriting the :options-alist doesn't have any effect. What am I not understanding about (org-export-define-derived-backend) Thanks for any help, /PA On Tue, 15 Apr 2025 at 08:39, Pedro Andres Aranda Gutierrez < paag...@gmail.com>

Re: [PATCH]: add BEAMER_CLASS_OPTIONS

2025-04-15 Thread Pedro Andres Aranda Gutierrez
On Mon, 14 Apr 2025 at 19:23, Ihor Radchenko wrote: > > Looks like we are losing the context. > Maybe... too many things at once ;-) > Let me reiterate. I was questioning your ORG-NEWS entry: > > > +When exporting to beamer, =#+BEAMER_CLASS_OPTIONS:= should be > used > > +inste

Re: Help request ... was Re: [PATCH]: Add font specifications when exporting to LaTeX

2025-04-14 Thread Pedro Andres Aranda Gutierrez
14 abr 2025, a las 19:32, Ihor Radchenko escribió: > > Pedro Andres Aranda Gutierrez writes: > >> I’ve been playing with old-style search engine suggestions and the >> Noto fonts (which seem to be installed with TexLive) and have come up >> with a MWE with “chall

Re: [PATCH]: Add font specifications when exporting to LaTeX

2025-04-14 Thread Pedro Andres Aranda Gutierrez
—— cut here —— Contributions for scripts outside Latin/Cyrillic > El 13 abr 2025, a las 10:50, Pedro Andres Aranda Gutierrez > escribió: > > PS: Free* means the Free* _fonts_ > > On Sun, 13 Apr 2025 at 10:49, Pedro Andres Aranda Gutierrez > mailto:paag...@gmail.com&g

A micro-addition to the manual

2025-04-13 Thread Pedro Andres Aranda Gutierrez
HI, I often refer people to the reference added by this micro patch. diff --git a/doc/org-manual.org b/doc/org-manual.org index 360260149..8a345ce79 100644 --- a/doc/org-manual.org +++ b/doc/org-manual.org @@ -13027,6 +13027,7 @@ popular display formats. We strongly recommend familiarizing yours

lex-bind frenzy

2025-04-13 Thread Pedro Andres Aranda Gutierrez
HI, Just an insignificance, caused by lexical binding hysteria in master: diff --git a/mk/org-fixup.el b/mk/org-fixup.el index efb9fb299..451da335b 100644 --- a/mk/org-fixup.el +++ b/mk/org-fixup.el @@ -1,4 +1,4 @@ -;;; org-fixup.el --- make life easier for folks without GNU make +;;; org-fixup.e

Re: [BUG?] in pcomplete???

2025-04-13 Thread Pedro Andres Aranda Gutierrez
o’ is not known to be defined. In end of data: ox-texinfo.el:2059:4: Warning: the function ‘org-publish-org-to’ is not known to be defined. Enough for today. I may look by this afternoon. Best, /PA On Sun, 13 Apr 2025 at 11:15, Ihor Radchenko wrote: > Pedro Andres Aranda Gutierrez writes:

Re: [PATCH]: add BEAMER_CLASS_OPTIONS

2025-04-13 Thread Pedro Andres Aranda Gutierrez
New version of the patch (will test your suggestions right after this) Best, /PA On Sat, 12 Apr 2025 at 19:50, Ihor Radchenko wrote: > Pedro Andres Aranda Gutierrez writes: > > > A new version of the patch, including a test for the new > > #+BEAMER_CLASS_OPTIONS >

Re: [PATCH]: Add font specifications when exporting to LaTeX

2025-04-13 Thread Pedro Andres Aranda Gutierrez
PS: Free* means the Free* _fonts_ On Sun, 13 Apr 2025 at 10:49, Pedro Andres Aranda Gutierrez < paag...@gmail.com> wrote: > A bit more info > > With lualatex, I get > > luaotfload | db : Reload initiated (formats: otf,ttf,ttc); reason: File > not found: &

Re: [PATCH]: Add font specifications when exporting to LaTeX

2025-04-13 Thread Pedro Andres Aranda Gutierrez
A bit more info With lualatex, I get luaotfload | db : Reload initiated (formats: otf,ttf,ttc); reason: File not found: "/usr/lib/firefox/fonts/TwemojiMozilla.ttf"texmf-dist/tex/luatex/luaotfload/luaotfload-fallback.lua:50: attempt to inde x a nil value (local 'f'). relax l.19 ... Serif}[Raw

Re: [BUG?] in pcomplete???

2025-04-12 Thread Pedro Andres Aranda Gutierrez
/PA On Sat, 12 Apr 2025 at 19:27, Ihor Radchenko wrote: > Pedro Andres Aranda Gutierrez writes: > > > in the meantime, here is a (somehow egoistic?) patch that adds the latex > > keyworks I need > > ... > > ( pcomplete/org-mode/file-option): import ox-latex to i

Re: [BUG?] in pcomplete???

2025-04-12 Thread Pedro Andres Aranda Gutierrez
Hi, in the meantime, here is a (somehow egoistic?) patch that adds the latex keyworks I need Best, /PA On Sat, 12 Apr 2025 at 18:56, Ihor Radchenko wrote: > Pedro Andres Aranda Gutierrez writes: > > > So, maybe we should include > > '(require ox-latex) > >

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

2025-04-12 Thread Pedro Andres Aranda Gutierrez
at, 12 Apr 2025 at 16:11, Leo Butler wrote: > On Thu, Apr 10 2025, Pedro Andres Aranda Gutierrez > wrote: > > > Jürgen writes: > > > >>Am 03.04.25 um 09:37 Uhr schrieb Ihor Radchenko: > >>>> I don't agree. Users who are apparently happy with Lu

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

2025-04-10 Thread Pedro Andres Aranda Gutierrez
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

Re: [PATCH]: add BEAMER_CLASS_OPTIONS

2025-04-10 Thread Pedro Andres Aranda Gutierrez
tance of the proverb "you will never go to sleep without learning something new" And I'm always open to learning new stuff :-) Thx, /PA On Tue, 8 Apr 2025 at 07:29, David Masterson wrote: > Pedro Andres Aranda Gutierrez writes: > > > Good point, maybe I didn't expl

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:Re: [DISCUSSION] Setting LuaLaTeX as default when exporting to LaTeX/PDF

2025-04-09 Thread Pedro Andres Aranda Gutierrez
Jürgen 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 support UTF8 is pdflatex, >> please do share. > > I am sorry I could not

Re: [PATCH]: add BEAMER_CLASS_OPTIONS

2025-04-09 Thread Pedro Andres Aranda Gutierrez
es, which we all are in a (thankfully) moving environment like Emacs/org-mode. Best, /PA On Wed, 9 Apr 2025 at 04:34, David Masterson wrote: > Pedro Andres Aranda Gutierrez writes: > > > On Tue, 8 Apr 2025 at 07:29, David Masterson > wrote: > >> > >> Should t

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

2025-04-09 Thread Pedro Andres Aranda Gutierrez
Thanks for confirming my understanding. /PA On Wed, 9 Apr 2025 at 09:00, Dr. Arne Babenhauserheide wrote: > Pedro Andres Aranda Gutierrez writes: > > > And what about the speed of xelatex? I have not used it, because when I > tried some time ago, it didn't handle fonts a

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

2025-04-08 Thread Pedro Andres Aranda Gutierrez
And what about the speed of xelatex? I have not used it, because when I tried some time ago, it didn't handle fonts as nicely as lualatex, but I'd be willing to learn if that means a speedy UTF.8 sound latex. Thx, /PA On Tue, 8 Apr 2025 at 16:39, Leo Butler wrote: > On Thu, Apr 03 2025, Ihor Ra

Re: [PATCH]: add BEAMER_CLASS_OPTIONS

2025-04-08 Thread Pedro Andres Aranda Gutierrez
A new version of the patch, including a test for the new #+BEAMER_CLASS_OPTIONS Best, /PA On Tue, 8 Apr 2025 at 09:08, Pedro Andres Aranda Gutierrez < paag...@gmail.com> wrote: > Hmmm... > > Isn't it enough to it select with > #STARTUP: beamer > > I have not

Re: [PATCH]: add BEAMER_CLASS_OPTIONS

2025-04-07 Thread Pedro Andres Aranda Gutierrez
other reasons. Best, /PA On Mon, 7 Apr 2025 at 22:53, Dr. Arne Babenhauserheide wrote: > Pedro Andres Aranda Gutierrez writes: > > When you want to change the beamer class options, you needed to add > > #+LATEX_CLASS: beamer > > #+LATEX_CLASS_OPTIONS: ... > > > > W

Fwd: [PATCH] Small speed-up for org-pcomplete.el

2025-04-07 Thread Pedro Andres Aranda Gutierrez
-- Forwarded message - From: Pedro Andres Aranda Gutierrez Date: Mon, 7 Apr 2025 at 17:20 Subject: [PATCH] Small speed-up for org-pcomplete.el To: , Ihor Radchenko Hi Since the block keywords are always the same, why not put them in a variable. Plus add the LATEX keywords

[PATCH]: add BEAMER_CLASS_OPTIONS

2025-04-07 Thread Pedro Andres Aranda Gutierrez
-- Fragen sind nicht da, um beantwortet zu werden, Fragen sind da um gestellt zu werden Georg Kreisler Sagen's Paradeiser, write BE! Year 1 of the New Koprocracy From b66dff2aaf36b35424f2c499ff7240bdb86e41d6 Mon Sep 17 00:00:00 2001 From: "Pedro A. Aranda" Date: Mon, 7 Apr 2025

Re: [BUG?] in pcomplete???

2025-04-05 Thread Pedro Andres Aranda Gutierrez
[PATCH]: add #+latex... and #+beamer... Just in case, I'm adding a small patch to add the missing keywords I miss when editing org to export to latex and beamer. Best, /PA On Sat, 5 Apr 2025 at 07:35, Pedro Andres Aranda Gutierrez < paag...@gmail.com> wrote: > Hi, > > when

Re: Re

2025-04-05 Thread Pedro Andres Aranda Gutierrez
Hi, answers inline... On Mon, 31 Mar 2025 at 19:12, Ihor Radchenko wrote: > Pedro Andres Aranda Gutierrez writes: > > > Hmmm... > > I'd have to sleep over it. This is more a "user taste" issue IMvvHO. > > > > I have a snippet for that includin

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

2025-04-05 Thread Pedro Andres Aranda Gutierrez
Thanks for the feedback. I’d be interested in seeing what happened. Could you please send me the offending file? It can be of help when determining What we need on org-mode. BTW, do you have any org file that you export to PDF where you could export using #+LATEX_COMPILER: lualatex And see what

Re: [DISCUSSION] Automatically setting unicode fonts in latex export

2025-04-05 Thread Pedro Andres Aranda Gutierrez
Answer inline On Wed, 2 Apr 2025 at 20:20, Ihor Radchenko wrote: > Pedro Andres Aranda Gutierrez writes: > > > Actually, what I would do after looking around is > > * short term (even as a bug fix in 9.7): modifying the error message and > > say that unsupported Unicod

Re: Image inlining patch

2025-04-05 Thread Pedro Andres Aranda Gutierrez
wrote: > Pedro Andres Aranda Gutierrez writes: > > > Could be a good idea. I would factor that out and then use a > define-alias in the html and the latex exporters to touch the code as > little as possible. > > WDYT? > > We should definitely keep obsolete alias if we mo

[BUG?] in pcomplete???

2025-04-04 Thread Pedro Andres Aranda Gutierrez
Hi, when working on the font stuff I have started noticing that (pcomplete-completiosn-at-point) is apparently not providing completions for the #+LATEX... directives, as oppposed to #STARTUP, #+OPTIONS,, #+BEGIN_... and #END_... Is this a bug or just a perception of mine? Thx, /PA -- Fragen sind

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

2025-04-04 Thread Pedro Andres Aranda Gutierrez
Hi Colin sorry that you find it "a push" and "bizarre". There is nothing of that sort... I was just trying to probe for arguments (pros and cons, hence [DISCUSSION]) to learn what the situation is "outside my bubble". I too have org-latex-compiler set to lualatex for some time ;-) Cheers, /PA On

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

2025-04-04 Thread Pedro Andres Aranda Gutierrez
Hi Arne, Thanks a lot. Really cool. My only concern is that it means adding a non-standard package to the TeX. I had no problems, but some people may struggle with the instructions ;-) Best, /PA > El 3 abr 2025, a las 23:13, Dr. Arne Babenhauserheide > escribió: > > Pedro A

[PATCH]: Add font specifications when exporting to LaTeX

2025-04-03 Thread Pedro A. Aranda
s in what I feel is the right place in the header. Best, /PA From b77250a91783e81502cef2fc6d332b6aa29f1e75 Mon Sep 17 00:00:00 2001 From: "Pedro A. Aranda" Date: Thu, 3 Apr 2025 08:05:57 +0200 Subject: [PATCH 1/4] Quick fix: explain unicode problems with pdflatex more accurately *

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

2025-04-02 Thread Pedro Andres Aranda Gutierrez
e get the speed from lualatex required by latex-preview, we could restart this discussion. My .2 cents, /PA On Thu, 3 Apr 2025 at 00:09, jman wrote: > Pedro Andres Aranda Gutierrez writes: > > >>> BTW, what about changing the default LaTeX compiler to lualatex in 9.8? > &g

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

2025-04-02 Thread Pedro Andres Aranda Gutierrez
So we are torn between two equally potent arguments. If you want/need latex-preview, forget about lualatex, but then restrict yourself to character sets it handles and forget about fancy utf8 support. If you want/need utf8 support, forget about latex-preview and compilation speed (at least FTMB) L

Re: [DISCUSSION] Automatically setting unicode fonts in latex export

2025-04-02 Thread Pedro Andres Aranda Gutierrez
enable/disable setting fonts from customisation (we could have them enabled by default) and one with a list of three font names ("serif" "sans" and "mono") to add in the preamble. Best, /PA On Wed, 2 Apr 2025 at 07:47, Ihor Radchenko wrote: > Pedro Andres Aranda

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

2025-04-02 Thread Pedro Andres Aranda Gutierrez
Thanks for the complete explanation. This is an argument with real weight and I fully understand. That lualatex is slower to start up is something even the overleaf.com people are struggling with. So we have to live with weak UTF.8 support w/preview versus good UTF-8 support with slw preview (

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

2025-04-02 Thread Pedro Andres Aranda Gutierrez
To add an argument to moving forward to lualatex: https://github.com/max-heller/mdbook-pandoc/issues/94 <https://github.com/max-heller/mdbook-pandoc/issues/94> Cheers, /PA > El 2 abr 2025, a las 8:17, Pedro Andres Aranda Gutierrez > escribió: > > Let’s start the discussion

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

2025-04-01 Thread Pedro Andres Aranda Gutierrez
Let’s start the discussion. We need feedback on this. Pros and Contras of moving on to using lualatex as default compiler. >> BTW, what about changing the default LaTeX compiler to lualatex in 9.8? > > I doubt that it is a good idea. > Mainly because we can break documents that were working in

Re: Re

2025-04-01 Thread Pedro Andres Aranda Gutierrez
HI again. me again. I have continued looking at this. For pdflatex, we need to use \usepackage{} and select font packages that don't need extra parameters. Lualatex and Xetex go by the \setmain{}... I don't know if we want to provide font sets for both.. WDYT? On Tue, 1 Apr 2025 at 07

Re: Re

2025-03-31 Thread Pedro Andres Aranda Gutierrez
and quite often). I would not dare to impose anything to anyone or force people to add customisations for this, because I don't have a "standard" setup. I would put this kind of things in the org-mode documentation. But once again, IMvvHO /PA On Mon, 31 Mar 2025 at 18:38, Ihor Rad

Re: Re

2025-03-31 Thread Pedro Andres Aranda Gutierrez
>Date: Mon, 31 Mar 2025 14:37:37 + >From: Leo Butler >To: Sébastien Gendre >Cc: emacs-orgmode Mailinglist >Subject: Re: Best way to represent a directory tree in Org-mode >Message-ID: <87msd1b70v@t14.reltub.ca> >Content-Type: text/plain; charset="utf-8" > >On Sun, Mar 30 2025, Jean Louis

Re: Image inlining patch

2025-03-30 Thread Pedro Andres Aranda Gutierrez
Hi again, Attached is a new version of the patch. It builds on Ihors refactoring patch. Best. /PA On Sun, 30 Mar 2025 at 07:24, Pedro Andres Aranda Gutierrez < paag...@gmail.com> wrote: > Thanks! > > Will try out as soon as I have time to. > > /PA > > On Sat,

Re: Image inlining patch

2025-03-29 Thread Pedro Andres Aranda Gutierrez
Thanks! Will try out as soon as I have time to. /PA On Sat, 29 Mar 2025 at 15:44, Ihor Radchenko wrote: > Pedro Andres Aranda Gutierrez writes: > > > after giving ox-html a second (and a third read), there are too many > > dependencies to make a clean move a simple task. &

Image inlining patch

2025-03-27 Thread Pedro Andres Aranda Gutierrez
, write BE! Year 1 of the New Koprocracy From b1d7cd0dd210a727e67bc65bed0d621b2387579c Mon Sep 17 00:00:00 2001 From: "Pedro A. Aranda" Date: Thu, 27 Mar 2025 10:24:10 +0100 Subject: [PATCH] Alternative image handling --- * lisp/ox-latex.el: Use ~org-html-standalone-image-p~ from ox-h

[BUG?] `org-babel-tangle-comment-links' doesn't respect `org-babel-tangle-use-relative-file-links' [9.7.16 (9.7.16-ba9734 @ ~/.config/emacs/elpa/org-9.7.26/)]

2025-03-25 Thread João Pedro de Amorim Paula
Hi Org, I realized the function `org-babel-tangle-comment-links' won't return the relative file path regardless of the value of `org-babel-tangle-use-relative-file-links', is this the intended behaviour or a bug? Here's the source code for `org-babel-tangle-comment-links' for reference: (defun or

Re: [BUG] Incorrect LaTeX export when using images in a table to display them side-by-side. [9.7.5 (release_9.7.5 @ /home/dadinn/.emacs.d/straight/build/org/)]

2025-03-10 Thread Pedro Andres Aranda Gutierrez
Thanks for the clarification. As I said, I will need more time for this. If I find a slot during the easter week I'll try, else after the lecture period. Best, /PA On Mon, 10 Mar 2025 at 17:57, Ihor Radchenko wrote: > Pedro Andres Aranda Gutierrez writes: > > >>>

Re: [BUG] Incorrect LaTeX export when using images in a table to display them side-by-side. [9.7.5 (release_9.7.5 @ /home/dadinn/.emacs.d/straight/build/org/)]

2025-03-08 Thread Pedro Andres Aranda Gutierrez
, not just \includegraphics{test-img.png}. This is why we need to place place the whole paragraph in the markup. #+END_SRC which, I hope, is what you intended. Best, /PA On Sat, 8 Mar 2025 at 06:52, Pedro Andres Aranda Gutierrez < paag...@gmail.com> wrote: > I'll see what can be do

Re: [BUG] Incorrect LaTeX export when using images in a table to display them side-by-side. [9.7.5 (release_9.7.5 @ /home/dadinn/.emacs.d/straight/build/org/)]

2025-03-07 Thread Pedro Andres Aranda Gutierrez
I'll see what can be done in the next free slot. /PA On Fri, 7 Mar 2025 at 18:06, Ihor Radchenko wrote: > Pedro Andres Aranda Gutierrez writes: > > > full image inlining patch with tests > > Thanks! > > I found a problematic example: > > #+attr_latex: :ce

Re: [BUG] Latex exporter should consider export settings [9.6.15 (release_9.6.15 @ /usr/share/emacs/29.3/lisp/org/)]

2025-03-07 Thread Pedro Andres Aranda Gutierrez
Sorry about that! On Fri, 7 Mar 2025 at 17:53, Ihor Radchenko wrote: > Pedro Andres Aranda Gutierrez writes: > > > attached in the full patch (I didn't see the fix applied on main @07:30 > CET > > today). > > May you please re-send the patch under the correct em

Re: [BUG] Incorrect LaTeX export when using images in a table to display them side-by-side. [9.7.5 (release_9.7.5 @ /home/dadinn/.emacs.d/straight/build/org/)]

2025-03-07 Thread Pedro Andres Aranda Gutierrez
Hi full image inlining patch with tests Best, /PA On Thu, 6 Mar 2025 at 19:39, Ihor Radchenko wrote: > Pedro Andres Aranda Gutierrez writes: > > > good to know. So, is there any other case apart that we should look at > > before deciding if the quick patch I prepared

Re: [BUG] Latex exporter should consider export settings [9.6.15 (release_9.6.15 @ /usr/share/emacs/29.3/lisp/org/)]

2025-03-06 Thread Pedro Andres Aranda Gutierrez
-- Fragen sind nicht da, um beantwortet zu werden, Fragen sind da um gestellt zu werden Georg Kreisler Sagen's Paradeiser, write BE! Year 1 of the New Koprocracy From 7fac86c69cbfe66e458ea11fa9a9d7e0ddd911fa Mon Sep 17 00:00:00 2001 From: "Pedro A. Aranda" Date: Fri, 7 Mar 2025 07:59:

Re: [BUG] Incorrect LaTeX export when using images in a table to display them side-by-side. [9.7.5 (release_9.7.5 @ /home/dadinn/.emacs.d/straight/build/org/)]

2025-03-04 Thread Pedro Andres Aranda Gutierrez
Hi, good to know. So, is there any other case apart that we should look at before deciding if the quick patch I prepared is good enough? Or should I start preparing the test case? Best, /PA On Tue, 4 Mar 2025 at 19:57, Ihor Radchenko wrote: > Pedro Andres Aranda Gutierrez writes: > &g

Re: [BUG] Incorrect LaTeX export when using images in a table to display them side-by-side. [9.7.5 (release_9.7.5 @ /home/dadinn/.emacs.d/straight/build/org/)]

2025-03-02 Thread Pedro Andres Aranda Gutierrez
s of the tabular environment or by selecting another environment that supports tables and conforms with the user's needs. AFAIU, this is what we achieve with the attributes. Best, /PA On Sun, 2 Mar 2025 at 11:16, Ihor Radchenko wrote: > Pedro Andres Aranda Gutierrez writes: > >

Re: [BUG] Incorrect LaTeX export when using images in a table to display them side-by-side. [9.7.5 (release_9.7.5 @ /home/dadinn/.emacs.d/straight/build/org/)]

2025-02-27 Thread Pedro Andres Aranda Gutierrez
controlled with attributes (your example) #+ATTR_LATEX: :environment longtable :align l|lp{3cm}r|l | file:image1.png | file:image2.png | Any more? Thx, /PA On Thu, 27 Feb 2025 at 19:32, Ihor Radchenko wrote: > Pedro Andres Aranda Gutierrez writes: > > > this is a quick fix for im

Re: [BUG] Incorrect LaTeX export when using images in a table to display them side-by-side. [9.7.5 (release_9.7.5 @ /home/dadinn/.emacs.d/straight/build/org/)]

2025-02-26 Thread Pedro Andres Aranda Gutierrez
Hi, this is a quick fix for image inlining. It would be nice to have it checked by more people. The code is a bit convoluted and it would be nice to have time and sit quietly or it. Best, /PA On Tue, 25 Feb 2025 at 19:19, Ihor Radchenko wrote: > Pedro Andres Aranda Gutierrez wri

Re: [BUG] Latex exporter should consider export settings [9.6.15 (release_9.6.15 @ /usr/share/emacs/29.3/lisp/org/)]

2025-02-25 Thread Pedro Andres Aranda Gutierrez
ducer)". In the meantime, attached is the announcement of the bugfix as a patch. Best, /PA On Tue, 25 Feb 2025 at 21:44, Ihor Radchenko wrote: > Pedro Andres Aranda Gutierrez writes: > > >> > The producer will include the LaTeX distribution. Do we really want to > >>

Re: Do we really need this?

2025-02-25 Thread Pedro Andres Aranda Gutierrez
Right, thanks for the info! /PA On Tue, 25 Feb 2025 at 19:36, Ihor Radchenko wrote: > Pedro Andres Aranda Gutierrez writes: > > > +(defconst org-latex--section-no-footnote-backend > > ... > > + > > > > Do we really need this now that the ToC handles footn

Re: [BUG] Latex exporter should consider export settings [9.6.15 (release_9.6.15 @ /usr/share/emacs/29.3/lisp/org/)]

2025-02-25 Thread Pedro Andres Aranda Gutierrez
Hi, On Tue, 25 Feb 2025 at 19:07, Ihor Radchenko wrote: > Pedro Andres Aranda Gutierrez writes: > > > I have a question: we have the org-export-with-... for author, title and > > creator. > > So we can act on these things in the PDF attributes when exporting to > LaT

Do we really need this?

2025-02-25 Thread Pedro Andres Aranda Gutierrez
Hi, Reading through the git logs, I have found this: +(defconst org-latex--section-no-footnote-backend + (org-export-create-backend + :parent org-latex--section-backend + :transcoders + `((footnote-reference . ignore))) + "Export backend that strips footnotes from title. + +Footnotes are

Re: [BUG] Incorrect LaTeX export when using images in a table to display them side-by-side. [9.7.5 (release_9.7.5 @ /home/dadinn/.emacs.d/straight/build/org/)]

2025-02-25 Thread Pedro Andres Aranda Gutierrez
Hi On the road again, answers inline… Enviado desde mi iPad > El 24 feb 2025, a las 19:11, Ihor Radchenko escribió: > > Pedro Andres Aranda Gutierrez writes: > >> If we have a table of figures, we might have problems when referencing the >> figures. > >

Re: [BUG] Latex exporter should consider export settings [9.6.15 (release_9.6.15 @ /usr/share/emacs/29.3/lisp/org/)]

2025-02-24 Thread Pedro Andres Aranda Gutierrez
Attached is a quick fix that only takes into account the existing org-export-with- settings. Best, /PA On Tue, 25 Feb 2025 at 07:31, Pedro Andres Aranda Gutierrez < paag...@gmail.com> wrote: > HI, > I'm giving this a second shot, now that the ToC fix is in the code. > >

  1   2   3   4   >