Hi again
reality has come to trash my plans. I'm not going to have time after
"right now" until I leave.
I have just committed something following my musings in the previous
email in the thread.
Will be happy to discuss in September
Best, /PA
On Tue, 29 Jul 2025 at 07:17, Pedr
polyglossia-font-config
. (("el" :font "Noto Serif" :props "Script=Greek")))
```
In all cases, :props is either a string or a list of strings. It could
make sense... if that is want you mean.
It would be more verbose, but it would make it easier for non LaTeX
peo
el-polyton"
:fonts (("rm" . "Noto Serif")))
(nil
:fonts (("rm" . "Noto Serif")
("sf" . "Noto Sans")
("tt" . "Noto Sans Mono"
```
Best, /PA
On Sun, 27 Jul 2025 at 15:02, Ihor Radchenko wrote:
>
> Pedro Andres Aranda Gutierrez writes:
>
> > 1. Docs should be in sync with your last comments.
>
> Thanks!
> Some more comments:
>
> > + The language codes supported by Org is stored in the variable
2025 at 17:37, Pedro Andres Aranda Gutierrez
wrote:
>
> {{{clp}}} is shorter and comfier to write than \clearpage (at least
> for me TM)...
> The other one is for me to highlight things that are LaTeX (as opposed
> to pure Org).
> Just a question like ... would it make sense
ion (list-elt 1 (proper-lists-of-different-length
3 1 ("es" "en" "fr") ("fr") first-mismatch-at 0)))
(org-export--get-inbuffer-options) seems to be collecting all
languages in :languages and the :language fix doesn't seem to be
enough
best, /PA
On Sun,
lly is,
so I may have read the options list in ox-latex.el into your answer.
So it's not a matter of being right or wrong, it's more about
synchronising before the black-out occurs ;-)
I'll push the change is a couple of minutes.
best, /PA
On Sun, 20 Jul 2025 at 07:41, Ihor Ra
language
in #+LANGUAGE (at least in theory).
Thanks for any enlightenment, /PA
On Sat, 19 Jul 2025 at 17:54, Pedro Andres Aranda Gutierrez
wrote:
>
> OK, will do after the IETF,
> /PA
>
> On Sat, 19 Jul 2025 at 15:59, Ihor Radchenko wrote:
> >
> > Pedro Andr
OK, will do after the IETF,
/PA
On Sat, 19 Jul 2025 at 15:59, Ihor Radchenko wrote:
>
> Pedro Andres Aranda Gutierrez writes:
>
> > I've moved the change in the behaviour of #+LANGUAGE to the creaking
> > changes section and expanded it a bit.
>
> I do not like
16:27, Ihor Radchenko wrote:
>
> Pedro Andres Aranda Gutierrez writes:
>
> > Attached is the org file.
>
> The file works on my side as well.
>
> Aside:
>
> Why #+MACRO: clp @@latex: \clearpage@@
> and why @@latex: \normalfont{@@ பொருள் @@latex: }@@?
Confirmed on emacs master with org-mode master.
On Sat, 19 Jul 2025 at 07:27, Иван Чижов wrote:
>
> You need to do the following to reproduce the problem.
>
> 1. Suppose we have some org file 'file.org'. Make Org source code in
> that file, for example:
> #+begin_src org
> ,#+title: The article
TiKZ that will need some fine-tuning afterwards.
best, /PA
On Sat, 19 Jul 2025 at 01:40, David Masterson wrote:
>
> Pedro Andres Aranda Gutierrez writes:
>
> > Answers inline,
> >
> > On Fri, 18 Jul 2025 at 01:48, David Masterson
> > wrote:
> >>
> &
h auctex/reftex from elpa and the feature
branch and was not able.
Could you share a bare minimum init.el file I could use to reproduce?
Best, /PA
On Thu, 17 Jul 2025 at 12:04, Pedro Andres Aranda Gutierrez
wrote:
>
> Hi,
>
> I’m quite busy with the export as such.
>
> It
Answers inline
On Fri, 18 Jul 2025 at 01:36, David Masterson wrote:
>
> Pedro Andres Aranda Gutierrez writes:
>
> > My usecase is basically the slides for my lectures. I get rid of most
> > of the markup, which in Beamer is sometimes overwhelming. I can also
> > mo
Answers inline,
On Fri, 18 Jul 2025 at 01:48, David Masterson wrote:
>
> Pedro Andres Aranda Gutierrez writes:
>
> > my experience (and possibly .2 cents)
> >
> > 1. LaTeX2Org
> >
> > I needed to go that path for a couple of manuals when I started lect
Jul 2025 at 17:39, Pedro Andres Aranda Gutierrez
wrote:
>
> Hi again,
> Was doing some tests with other fonts...
> Change the rm font to "FreeSerif" and remember to execute the
> emacs-lisp code to set the right variables.
>
> Best , /PA
>
> PS: Frankly speaki
bel/guides/locale-tamil.html
If they don't know, how should we? ;-)
On Thu, 17 Jul 2025 at 17:23, Pedro Andres Aranda Gutierrez
wrote:
>
> Hi,
>
> I did some fine-tuning today in ox-latex.el on the feature branch.
> Thanks to that, you should be able to compile the example
Ihor Radchenko wrote:
>
> Pedro Andres Aranda Gutierrez writes:
>
> > The feature branch has all things I needed(TM).
>
> Another example to test:
> https://old.reddit.com/r/emacs/comments/1ltryn4/tamil_and_english_text_export_from_orgmode_to_pdf/
> Ideally, no font c
ments,
/PA
On Thu, 17 Jul 2025 at 12:57, Max Nikulin wrote:
>
> On 16/07/2025 14:41, Pedro Andres Aranda Gutierrez wrote:
> > 1. It would be nice to agree on some #+BEGIN_LANG #+END_LANG block for
> > the LaTeX exporter to cope with \begin{otherlanguage*} in an
> > org-na
aven't loaded reftex though. What if you add (use-package reftex) in your configuration?On Tue, 1 Jul 2025 at 16:36, Pedro Andres Aranda Gutierrez <paag...@gmail.com> wrote:Just to close this. I'm not able to completely reproduce the
environment. Attach is a test report.
/PA
On Tu
My usecase is basically the slides for my lectures. I get rid of most of the
markup, which in Beamer is sometimes overwhelming.
I can also modify examples on the fly to answer questions and explore
alternatives in class.
And I can always resort to TiKZ for high-quality graphics and animations.
B
" is from 1821.
Old English borrowed Latin regula and nativized it as regol "rule, regulation,
canon, law, standard, pattern;" hence regolsticca "ruler" (instrument); regollic
(adj.) "canonical, regular."
\end{otherlanguage*}
*** வழக்கமான, எப்பொழுதும் போல
# Local
>Date: Tue, 15 Jul 2025 09:45:57 +0200
>From: "Dr. Arne Babenhauserheide"
>To: David Masterson
>Cc: William Denton , emacs-orgmode@gnu.org
>Subject: Re: LaTeX to Org ? (also Auctex/Lyx)
>Message-ID: <87ldop522y@web.de>
>Content-Type: text/plain; charset="utf-8"
>
>David Masterson writes:
>
figuration, we can always add that to the corresponding fontspec
custom variable.
Best, /PA
On Tue, 15 Jul 2025 at 19:22, Ihor Radchenko wrote:
>
> Pedro Andres Aranda Gutierrez writes:
>
> > The feature branch has all things I needed(TM).
>
> Another example to test:
&
Hi Ihor,
I've moved the change in the behaviour of #+LANGUAGE to the creaking
changes section and expanded it a bit.
Hope it's enough,
/PA
On Sun, 13 Jul 2025 at 17:06, Pedro Andres Aranda Gutierrez
wrote:
>
> Hi,
>
> you are right... didn't see it that way. Let me
Hi,
you are right... didn't see it that way. Let me see how we can phrase that...
Best, /PA
On Sun, 13 Jul 2025 at 16:24, Ihor Radchenko wrote:
>
> Pedro Andres Aranda Gutierrez writes:
>
> >> >> Also, since we now allow multiple languages to be listed in #+LAN
n the manual.
Hopefully done for polyglossia.
Best, /PA
On Sat, 12 Jul 2025 at 16:42, Ihor Radchenko wrote:
>
> Pedro Andres Aranda Gutierrez writes:
>
> > I intended to update you on the progress of the feature branch, which
> > is basically ready for more testing.
>
>
Hi,
sorry for not being able to make it to the meetup yesterday. Life came
in between and I was kept busy all afternoon fighting (very
unpleasant) bureaucracy.
I intended to update you on the progress of the feature branch, which
is basically ready for more testing.
My idea/wish would be to start
Jul 2025 at 19:36, Ihor Radchenko wrote:
>
> Pedro Andres Aranda Gutierrez writes:
>
> > What you mean is:
> > ...
> > +(:languages "LANGUAGE" nil (list org-export-default-language) split)
> > ...
> > +;; Get :languages and insert i
Hi again,
I've integrated this into the current feature branch. It was not too painful ;-)
Best, /PA
On Wed, 2 Jul 2025 at 18:03, Pedro Andres Aranda Gutierrez
wrote:
>
> Hi Ihor,
>
> just to check.
>
> What you mean is:
>
> diff --git a/lisp/ox-latex.el b/lisp/
(run-hook-with-args 'org-export-before-processing-hook
(org-export-backend-name backend))
And then, of course, use :languages in ox-latex.el
Right?
Best, /PA
On Tue, 1 Jul 2025 at 07:28, Pedro Andres Aranda Gutierrez
wrote:
>
> On Mon, 30 Jun 2025 at 19:3
OK, forget it, I'll try myself to see if I can reproduce...
Thanks for your help and patience, /PA
On Tue, 1 Jul 2025 at 11:09, Vangelis Evangelou wrote:
>
> Hi Pedro.
>
> I tried what you said, but for some reason the local variables text doesn't
> get printed. Coul
problem because it would hit the (error "Need a
> filename for this buffer, please save it first"). Because of this I believe
> that both reftex and org have a bug.
>
> On Mon, 30 Jun 2025 at 18:40, Ihor Radchenko wrote:
>>
>> Vangelis E writ
Sorry, fast typing while chasing an Internet purchase is definitely
not part of my abilities :-)
On Tue, 1 Jul 2025 at 10:41, Pedro Andres Aranda Gutierrez
wrote:
>
> Hmmm...
>
> This is a very trick case indeed. Apart from discerning if we want to
> blame it or not, what I wou
On Mon, 30 Jun 2025 at 19:34, Ihor Radchenko wrote:
>
> Pedro Andres Aranda Gutierrez writes:
>
> >> >> Also, since we now allow multiple languages to be listed in #+LANGUAGE,
> >> >> we may need to update the manual when talking about #+LANGUAGE keyword
&g
Hi,
On Mon, 30 Jun 2025 at 19:51, Ihor Radchenko wrote:
>
> Pedro Andres Aranda Gutierrez writes:
>
> >> Even though you did split the paragraph, it is IMHO, not yet ideal.
> >> When I read the two paragraph one after another I feel confused.
> >> Wh
xport-filter-final-output-functions, but the text doesn't appear in the
> exported *Org LATEX Export* buffer.
>
> On Mon, 30 Jun 2025 at 07:49, Pedro Andres Aranda Gutierrez
> wrote:
>>
>> PS: You can also add the code in your Emacs Lisp test code
>>
>> Sorry for t
y did not address this comment.
I've gone through the code once again and I think we need to start
looking at places where #+LANGUAGE is used outside the LaTeX exporter.
There we will need to filter out and keep the first language if we
find a comma separated list of languages...
WDYT?
/PA
PS: You can also add the code in your Emacs Lisp test code
Sorry for the convoluted suggestion...
/PA
On Sun, 29 Jun 2025 at 19:16, Pedro Andres Aranda Gutierrez
wrote:
>
> Last try:
> put the following after the header and before the text in your buffer,
> evaluate the block (C-c C
Hi
Answers inline,
On Sun, 29 Jun 2025 at 20:03, Ihor Radchenko wrote:
>
> Pedro Andres Aranda Gutierrez writes:
>
> > Pushed reworked doc...
>
> Thanks!
> It would also be helpful if you provided a brief summary of what you did
> wrt every point I raised in my revi
org-export-filter-final-output-functions
'add-texparse-filter)
#+END_SRC
--- cut here
This is a try to see if we can make the configuration of this
workaround customisable.
Best, /PA
On Sun, 29 Jun 2025 at 14:12, Vangelis Evangelou wrote:
>
> Hi Pedro.
>
> > This
Pushed reworked doc...
Best, /PA
On Sun, 29 Jun 2025 at 10:51, Pedro Andres Aranda Gutierrez
wrote:
>
> Hi Ihor,
>
> thanks, will start with it this afternoon :-)
>
> Best, /PA
>
> On Sun, 29 Jun 2025 at 10:23, Ihor Radchenko wrote:
> >
> > Pedro Andres Ara
Hi Ihor,
thanks, will start with it this afternoon :-)
Best, /PA
On Sun, 29 Jun 2025 at 10:23, Ihor Radchenko wrote:
>
> Pedro Andres Aranda Gutierrez writes:
>
> > I'd like to go on a step-by-step review instead of getting all
> > comments in one email (if that is p
Hi
Thx a lot for the explanation... answers inline
On Sat, 28 Jun 2025 at 18:04, Vangelis Evangelou wrote:
>
> Hi Pedro.
>
> > I don't think this is a bug. It's more of a side effect ...
>
> I'm not sure what you are referring to. I assume that since the prog
ot; the package itself.
@Ihor WDYT?
Best, /PA
On Fri, 27 Jun 2025 at 18:31, Vangelis Evangelou wrote:
>
> Hi Pedro.
>
> The export works as expected *without* loading auctex. It also works as
> expected *with* loading auctex, but with TeX-parse-self to nil. Perhaps the
> best
> Hi,
>
> I am hoping someone could help me with the following:
>
> As a music teacher, I need to write concert-programs for my concerts. I
> keep org files in the following form:
>
> * Student Name
> ** Composer
>Piece Name and Info
> ** Composer 2
>Second Piece to be played.
>
>
> * Next
Vangelis writes:
> Hello.
>
> I started with emacs -q. Then in the scratch buffer, I evaluated the
> following code
>
> (use-package reftex-auc)
> (use-package tex
> :load-path "site-lisp/auctex-14.0.9"
> :custom
> (TeX-parse-self t))
>
> Then, I created an org buffer which I exported to lat
Hi Ihor
The feature branch has all things I needed(TM). I did receive very
valuable feedback and would like to see if we can start polishing it
for an eventual integration.
I'd like to go on a step-by-step review instead of getting all
comments in one email (if that is possible).
When you look at
Hi again
I have made a substantial cleanup in the feature branch. It includes
restoring the original language guessing routines for documents prior
to (org-latex-multi-lang-driver).
A bit of background:
The new (org-latex-multi-lang-driver) variable controls how the
headers are generated.
The def
Hi again,
On Thu, 19 Jun 2025 at 15:38, Christian Moe wrote:
>
> - It would also be nice if we could rely on a single naming system for
> languages in Org regardless of backend -- preferably, in my view, if
> we could use only the language shortcodes already used by Org, and
> have Org tran
Hi Christian,
thanks for the active testing, really !
Answers inlie
On Thu, 19 Jun 2025 at 15:38, Christian Moe wrote:
>
> Pedro Andres Aranda Gutierrez writes:
>
> > Attached is a new version of the multi-lingual demo ZIP.
> >
> > Thanks for testing, /PA
>
I don’t know what’s happening with the address book…Enviado desde mi iPhoneInicio del mensaje reenviado:De: Mail Delivery Subsystem Fecha: 17 de junio de 2025, 17:35:53 CESTPara: paag...@gmail.comAsunto: Delivery Status Notification (Failure)
Address not found
Your message wasn't del
Wow... thx a ton.
The \arfont and \elfont stuff is a result of the moving target state
the branch is currently...
I will correct that and write a specific test for it
Thanks a ton again
/PA
On Tue, 17 Jun 2025 at 10:04, Christian Moe wrote:
>
> Pedro Andres Aranda Gutierrez
Thx for the additional reading materials :-)
Best, /PA
On Mon, 16 Jun 2025 at 21:20, Ihor Radchenko wrote:
>
> Pedro Andres Aranda Gutierrez writes:
>
> > For that, I think we would need to have an extra property in
> > org-latex-language-alist to specfic extra fontencs
he default value.
I have seen that I can use babelprovide with pdflatex too.
My plan is to integrate this next week and see...
Best, /PA
On Sat, 14 Jun 2025 at 08:26, Pedro Andres Aranda Gutierrez
wrote:
>
> ;-) Look at the last commits in the feature branch.
> I hope they will help to provide a
HI, Jacob
On Sat, 14 Jun 2025 at 18:45, Jacob S. Gordon wrote:
>
> Hey Pedro,
>
> On 2025-06-14 02:41, Pedro Andres Aranda Gutierrez wrote:
> > After giving it a thought, I would say that adding a new custom
> > variable to control the default options might do the trick
't be to cumbersome and flexible enough at the same
time. I wonder if we want to cover all cases like in
#+BEGIN_SRC latex
\defaultfontfeatures[\rmfamily,\sffamily]{Ligatures=TeX}
#+END_SRC
That would surely make things too tricky, I fear.
WDYT? Do we really need it?
On Fri, 13 Jun 2025 a
;-) Look at the last commits in the feature branch.
I hope they will help to provide a cleaner integration path in the future.
Best, /PA
On Fri, 13 Jun 2025 at 20:49, Ihor Radchenko wrote:
> Pedro Andres Aranda Gutierrez writes:
>
> > We can further discuss in the next me
Hi Ihor,
there you are
On Fri, 13 Jun 2025 at 21:03, Ihor Radchenko wrote:
> Pedro Andres Aranda Gutierrez writes:
>
> > attached is a ZIP file with the presentation and the anabasis MWE I
> showed
> > yesterday during the meetup.
>
> Thanks!
> Do you also ha
-- Forwarded message -
From: Pedro Andres Aranda Gutierrez
Date: Fri, 13 Jun 2025 at 19:02
Subject: Re: babel (LaTeX) support in feature/all-tex-fonts branch
To: Jacob S. Gordon
Hi again
answers inline...
On Fri, 13 Jun 2025 at 18:39, Jacob S. Gordon
wrote:
> Hey Pe
Hey Jacob
thanks a ton! Answers inline...
On Fri, 13 Jun 2025 at 06:14, Jacob S. Gordon
wrote:
> Hey Pedro,
>
> I just completed some testing on the feature branch, mostly on the
> `fontconfig' side (still asking around for some polyglot documents).
> It went very well; h
Hi
On Mon, 9 Jun 2025 at 19:25, Ihor Radchenko wrote:
> Pedro Andres Aranda Gutierrez writes:
>
> > Could make sense.
> > However, I would like to postpone this until I finish the code I'm
> working
> > on right now (give me a week).
>
> Sure. I just got
ntain.
I do understand this is a breaking change, but there are other breaking
changes around, so why not?
On Mon, 9 Jun 2025 at 17:23, Ihor Radchenko wrote:
> Pedro Andres Aranda Gutierrez writes:
>
> > It would make then difficult to distinguish between people who want/need
> >
It would make then difficult to distinguish between people who want/need
polyglossia and people who don't, wouldn't it.
I'd rather not force anyone to load polyglossia if they don't want to use
it.
best, /PA
On Sun, 8 Jun 2025 at 17:27, Ihor Radchenko wrote:
> Pedro
I think, I will provide a patch for main when everything is ready. My
feeling here is that we can use replace-regexp-in-string at some places,
instead of all this string-match / replace-match and that would simplify
the code.
Best, /PA
On Sun, 8 Jun 2025 at 12:47, Ihor Radchenko wrote:
> Pe
Hmmm...
So, we could have something like
#+LATEX_POLYGLOSSIA_LANGS: AUTO
to import all the document languages and define the main? Will see how to
integrate in the feature branch.
Thx, /PA
On Sun, 8 Jun 2025 at 13:01, Ihor Radchenko wrote:
> Pedro Andres Aranda Gutierrez writes:
>
Hi Ihor,
could you please take a look at the last patch set I have uploaded to the
feature branch, specifically at the change to ox-latex.el that starts with
@@ -1813,17 +1823,13 @@ Return the new header."
It fixes a situation where you have several \babelprovide statement and the
statement cont
Hi everybody,
I have finally added preliminary support for babel (as in LaTeX package) to
the feature branch.
it is activated by the
#+LATEX_BABEL_LANGS
header keyword, which substitutes the need for
#+LATEX_HEADER: \usepackage[...]{babel}
in the header.
In addition to that, more complex font setu
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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 ;-)
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
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
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
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
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
(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
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
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 (&
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
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
-- 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
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
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
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
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
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
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
1 - 100 of 439 matches
Mail list logo
