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, Pedro Andres Aranda Guti
Pedro Andres Aranda Gutierrez writes:
> 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
No problem.
--
Ihor Ra
Let me see if I understand... in the example shared, we would replace
```
(org-latex-babel-font-config
. (("el-polyton"
:fonts (("rm" . "Noto Serif")))
(nil
:fonts (("rm" . "CMU Serif")
("sf" . "Noto Sans")
("tt" . ("DejaV
Pedro Andres Aranda Gutierrez writes:
>> I am also wondering if we can unify this variable with
>> `org-latex-polyglossia-font-config' and `org-latex-babel-font-config'.
>
> I'd rather keep them apart. The mechanics are different, the font options too.
> A unification may have result in people us
HI again,
All this discussion has led me to rename org-latex-babel-fontspec to
org-latex-babel-font-config to align with the rest. This variable
stores a font configuration and using fontspec sort of may have been
confusing since we have the fontspec package floating around.
An example of a direc
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
> > + ~org-latex-language-alist~.
>
> *a
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
> + ~org-latex-language-alist~.
*are stored
> + By default, it is ~nil~ and multi-language documents are
Hi Ihor
after the excurse... I just wanted to report of the current status:
1. Docs should be in sync with your last comments.
2. Code: I have continued polishing and found a couple of minor quirks
which I have fixed.
a. I found and fixed a misplaced parenthesis in the fontspec
configuration gener
Pedro Andres Aranda Gutierrez writes:
> {{{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 to have an org construct for
> this?
Pedro Andres Aranda Gutierrez writes:
> {{{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 to have an org construct for
> this?
{{{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 to have an org construct for this?
But you are right...
/PA
On Sat, 19 Jul 2025 at 16
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: }@@?
You can just write \clearpage or
\normalfont{பொருள்}
Both are perfectly valid as latex-fragme
Pedro Andres Aranda Gutierrez writes:
> I would like to be a bit more pragmatic in our approach:
> The question I would like to ask us all is whether the feature branch
> handles more situations than the current implementation.
> If that is the case, why not go ahead and integrate it into master?
Further testing: Installing Unicode Tamil fonts like Latha or Vijaya
helps a lot.
This is yet another argument for not trying something like a universal
font configuration.
They are not sufficiently highly ranked in the search engines to make
them pop up early in any search.
Best, /PA
On Thu, 17
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 speaking I think we are way beyond what the babel people
are able to show in
https://latex3.github.io/babel/guides/lo
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 provided on
reddit with one exception: I've not been able to get the bold Tamil
fonts to work.
Attached is the org file.
Best, /PA
On Tue, 15 Jul 2025 at 19:22, Ihor R
Hi Max,
thank you very much. I see we are in violent agreement here. The macro
is a real headache and in an ideal world, replicating the
functionality of foreign language should involve something that takes
a first argument being an Org language name and a second argument with
should be the string
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-native way
2. Ditto for the texten macro
[...]
#+MACRO: texten @@latex: \textenglish{$1}@@
[...]
*
PS: here is how The example can be fixed with the feature branch.
Comments:
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-native way
2. Ditto for the texten macro
3. The example is not exactly the best way of
Hi Ihor,
Regarding font configuration or not, I would feel constrained if
someone came with a default set of fonts. On top of that,
is there a set of fonts that is universally available? I don't see
that in current environment with multiple Linux, macOS and FreeBSD.
I prefer to stick with examples
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 configuration should be necessary (or users may screw
up like what
Pedro Andres Aranda Gutierrez writes:
> Awesome, thanks! Moved.
Thanks! LGTM.
> PS: I know (nth 0 list) is (car list). You will sometimes see it in my code,
> just as a way of "literate", enhanced self-documentation. (car) can be
> applied to more object types,
> while (nth n) helps me remember
Awesome, thanks! Moved.
Best,/PA
PS: I know (nth 0 list) is (car list). You will sometimes see it in my code,
just as a way of "literate", enhanced self-documentation. (car) can be
applied to more object types,
while (nth n) helps me remember I'm dealing with a list...
On Sun, 6 Jul 2025 at 19:
Pedro Andres Aranda Gutierrez writes:
> What you mean is:
> ...
> +(:languages "LANGUAGE" nil (list org-export-default-language) split)
> ...
> +;; Get :languages and insert it into :language
> +(when-let* ((languages (plist-get info :languages))
> +(lang (nth 0 langua
Pedro Andres Aranda Gutierrez writes:
>> This time you removed too much :)
>> You lost fn:48, for example. You completely removed
>> `org-latex-bibtex-compiler' description from the manual. And you forgot
>> to move all the cindex and vindex entries associated with that removed
>> paragraph to
Pedro Andres Aranda Gutierrez writes:
>> 1. It will be better to use space instead of comma. Then, we will be
>>able to use "split" directive in `org-export-options-alist'
>> 2. We will probably need to do some backwards compatibility refactoring,
>>making sure that no extra package using
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/ox-latex.el
> index c6fb6b06b..f1
Hi Ihor,
just to check.
What you mean is:
diff --git a/lisp/ox-latex.el b/lisp/ox-latex.el
index c6fb6b06b..f1c9d090f 100644
--- a/lisp/ox-latex.el
+++ b/lisp/ox-latex.el
@@ -171,6 +171,7 @@
(:latex-toc-command nil nil org-latex-toc-command)
(:latex-compiler "LATEX_COMPILER" nil org-la
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
> >> >> in other places as well; not just
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.
> >> When I read the LaTeX section from the beginning
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.
>> When I read the LaTeX section from the beginning, I feel even more
>> confused - what do these paragraphs do in LaTeX
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
>> >> in other places as well; not just in latex export section.
>> You seemingly did not address this c
Hi Ihor, more commits and a doubt:
> >> Also, since we now allow multiple languages to be listed in #+LANGUAGE,
> >> we may need to update the manual when talking about #+LANGUAGE keyword
> >> in other places as well; not just in latex export section.
> You seemingly did not address this comment.
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 review message. That would help m
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 review message. That would help me and
also help you to make sure that you went through every suggestion.
> The LaTeX ex
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 Aranda Gutierrez writes:
> >
> > > I'd l
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 possible).
>
> Sure. I will
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 possible).
Sure. I will start from reviewing changes to the manual.
> -Org file. See the docstring for the
> -~org-latex-default-packages-alist~ for loadin
38 matches
Mail list logo
