[PATCH] Add backslash to list of POST characters for text markup

[Tom Alexander]

Backslash appears to be supported. To test I used the following test document:
```
foo ~bar~\& baz
```

This happens in a document in worg: 
https://git.sr.ht/~bzg/worg/tree/ae64e1a54185232d4ebdcab174d8d4319ffd564d/org-release-notes.org#L

The ampersand was chosen for the test document since that is not a supported 
POST character, to make sure backslash was not simply escaping the next 
character.

In the documentation I wrote out the word "backslash" in parenthesis to 
disambiguate between backslash and escaping the following comma.

Patch is attached.

--
Tom Alexander
pgp: https://fizz.buzz/pgp.ascFrom 098434680b5e3942acc00684a47389f2cdab6208 Mon Sep 17 00:00:00 2001
From: Tom Alexander 
Date: Thu, 21 Sep 2023 21:14:33 -0400
Subject: [PATCH] Add backslash to list of POST characters for text markup.

Backslash appears to be supported. To test I used the following test document:
```
foo ~bar~\& baz
```
The ampersand was chosen since that is not a supported POST character, to make sure backslash was not simply escaping the next character.

In the documentation I wrote out the word "backslash" in parenthesis to disambiguate between backslash and escaping the following comma.
---
 org-syntax.org | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/org-syntax.org b/org-syntax.org
index c5299741..8f0f9b0c 100644
--- a/org-syntax.org
+++ b/org-syntax.org
@@ -249,9 +249,9 @@ discarded.  This also applies to single-line elements.
 
 :This paragraph will not contain
 :a long sequence of spaces before "a".
-: 
+:
 :This paragraph does not have leading spaces according to the parser.
-: 
+:
 :#+begin_src emacs-lisp
 :  (+ 1 2)
 :#+end_src
@@ -1742,7 +1742,7 @@ whitespace characters.
   verbatim) or a series of objects from the standard set. In both
   cases, CONTENTS may not begin or end with whitespace.
 + [[#Special_Tokens][POST]] :: Either a whitespace character, =-=, =.=, =,=, =;=, =:=, =!=, =?=, ='=, =)=, =}=,
-  =[=, ="=, or the end of a line.
+  =[=, ="=, =\= (backslash), or the end of a line.
 
 *Examples*
 
-- 
2.42.0

Consecutive plain list items of different types

[Tom Alexander]

The org-mode documentation[1] states for plain lists that:
> List types are mutually exclusive at the same level of indentation, if both 
> types are present consecutively then they parse as separate lists.

first a minor nit-pick that "both" is probably not the correct word here since 
there are 3 types of lists, not two (unordered, ordered, and descriptive). I'd 
go with "multiple" instead IMO.

but more importantly, based on that description I would expect the following 
test document to parse into three separate plain lists, but it parses as a 
single plain list with 3 items:

```
1. foo
- bar
- lorem :: ipsum
```

[1] https://orgmode.org/worg/org-syntax.html#Plain_Lists

--
Tom Alexander
pgp: https://fizz.buzz/pgp.asc

Re: Subscript with parenthesis

[Tom Alexander]

Some additional things I'm noticing:

- when using parenthesis, :use-brackets-p is nil, so they're not equivalent to 
curly braces.
- it does not support objects inside the parenthesis, just plain text, which 
again means they're not equivalent to braces.
- it, however, seems to require that the parenthesis are balanced because this 
test document does NOT contain a subscript:
```
foo_(b(ar)
```
which is closer to the curly braces requirement since that seems to be the only 
part of the subscript/superscript documentation that mentions needing balance.

-- 
Tom Alexander

Subscript with parenthesis

[Tom Alexander]

The org-mode documentation[1] states that the SCRIPT portion of the 
subscript/superscript is either an asterisk, the standard set of objects 
wrapped in balanced curly braces, or an optional sign followed by "Either the 
empty string, or a string consisting of any number of alphanumeric characters, 
commas, backslashes, and dots"

But I'm seeing the following test document parse as containing a subscript 
despite using parenthesis which I do not think matches any of the above 
criteria:
```
foo_(bar)
```

[1] https://orgmode.org/worg/org-syntax.html#Subscript_and_Superscript

--
Tom Alexander

Re: Sanskrit/Devanagari fonts not exported to org-pdf output

[Juan Manuel Macías]

Zenny writes:

> I also tried with: 
>
> (setq org-latex-pdf-process
>   (if (executable-find "latexmk")
>   '("latexmk -interaction nonstopmode -output-directory %o
> %f")
>  "bibtex %b"
>  '("%latex -interaction nonstopmode -output-directory %o %f"
>   "%latex -interaction nonstopmode -output-directory %o %f"
>   "%latex -interaction nonstopmode -output-directory %o %f"))

I think the expression is bad formed; In addition, latexmk is already
responsible for executing bibtex or biber and other processes that
require more than one compilation. The right thing would be:

(setq org-latex-pdf-process (if (executable-find "latexmk")
'("latexmk -f -pdf -%latex 
-interaction=nonstopmode -output-directory=%o %f")
  '("%latex -interaction nonstopmode 
-output-directory %o %f"
"%latex -interaction nonstopmode 
-output-directory %o %f"
"%latex -interaction nonstopmode
-output-directory %o %f")))

(or just remove the customization of that variable from your init).

And then put in your document:

#+LATEX_COMPILER: lualatex (or pdflatex or xelatex)

This keyword modifies the value of org-latex-compiler in the document.
If you are going to use lualatex more often, you can put in your init:

(setq org-latex-compiler "lualatex")

Best regards,

Juan Manuel 

-- 
Juan Manuel Macías

https://juanmanuelmacias.com

https://lunotipia.juanmanuelmacias.com

https://gnutas.juanmanuelmacias.com

Re: Sanskrit/Devanagari fonts not exported to org-pdf output

[Zenny]

On Thu, Sep 21, 2023 at 10:39 PM Zenny  wrote:

>
> On Thu, Sep 21, 2023 at 10:26 PM Zenny  wrote:
>
>>
>> On Thu, Sep 21, 2023 at 9:32 PM Juan Manuel Macías <
>> maciasch...@posteo.net> wrote:
>>
>>> Zenny writes:
>>>
>>> > Here it comes:
>>> >
>>> > org-latex-pdf-process is a variable defined in ‘ox-latex.el’.
>>> >
>>> > Its value is
>>> > ("pdflatex -interaction nonstopmode -output-directory %o %f"
>>> > "bibtex %b" "pdflatex -shell-escape -interaction nonstopmode -
>>> > output-directory %o %f" "pdflatex -shell-escape -interaction
>>> > nonstopmode -output-directory %o %f")
>>> > Original value was
>>> > ("latexmk -f -pdf -%latex -interaction=nonstopmode -
>>> > output-directory=%o %f")
>>>
>>> It seems that you have modified the original value. Besides, the
>>> docstring says:
>>>
>>> [...] %latex is the LaTeX compiler (see ‘org-latex-compiler’) [...]
>>>
>>> If you put 'pdflatex ...', it will always compile with pdflatex.
>>>
>>
> Does `#+LATEX_COMPILER: lualatex` makes no difference?
>

I also tried with:

(setq org-latex-pdf-process
>   (if (executable-find "latexmk")
>   '("latexmk -interaction nonstopmode -output-directory %o %f")
>  "bibtex %b"
>  '("%latex -interaction nonstopmode -output-directory %o %f"
>   "%latex -interaction nonstopmode -output-directory %o %f"
>   "%latex -interaction nonstopmode -output-directory %o %f"))
>

but it did not produce any pdf at all.


>
>
>>
>>> I would recommend that you restore the original value of
>>> org-latex-pdf-process, which uses latexmk (if it is installed, which
>>> seems to be your case), which executes '%latex' (=
>>> `org-latex-compiler'). latexmk is a perl script included in texlive that
>>> is responsible for executing all the necessary compilations (including
>>> the call to the bibliographic engine[1]).
>>>
>>
>> When I checked the `ox-latex.el` it appears using latexmk
>>
>>  (defcustom org-latex-pdf-process
>>>   (if (executable-find "latexmk")
>>>   '("latexmk -f -pdf -%latex -interaction=nonstopmode
>>> -output-directory=%o %f")
>>> '("%latex -interaction nonstopmode -output-directory %o %f"
>>>   "%latex -interaction nonstopmode -output-directory %o %f"
>>>   "%latex -interaction nonstopmode -output-directory %o %f"))
>>>   "Commands to process a LaTeX file to a PDF file.
>>>
>>
>> And latexmk is already installed by texlive:
>>
>>  $ which latexmk
>>> /opt/texlive/2023/bin/x86_64-linux/latexmk
>>>
>>
>>
>> Or do you mean to change latexmk in init.el?
>>
>
> I do see in init.el that it has been changed to something like:
>
> (setq org-latex-pdf-process
>>   '("pdflatex -interaction nonstopmode -output-directory %o %f"
>>  "bibtex %b"
>> "pdflatex -shell-escape -interaction nonstopmode
>> -output-directory %o %f"
>> "pdflatex -shell-escape -interaction nonstopmode
>> -output-directory %o %f"))
>>
>
>
>> Thanks!
>>
>>>
>>> [1] In some cases some configuration is required for latexmk via a
>>> ~/latexmkrc file, but by default everything should work fine.
>>>
>>>
>>>
>>
>> --
>> Cheers,
>> /z
>>
>> -.. .. ... -.-. .-.. .- .. -- . .-. | -.. .. ... -.-. .-.. .- .. -- . .-.
>> CONFIDENTIALITY NOTICE AND DISCLAIMER: Access to this e-mail and its
>> contents by anyone other than the intended recipient is unauthorized as it
>> contains privileged and confidential information, and is subject to legal
>> privilege. Please do not re/distribute it.  If you are not the intended
>> recipient (or responsible for delivery of the message to such person), you
>> may not use, copy, distribute or deliver the email and part of its contents
>> to anyone this message (or any part of its contents or take any action in
>> connection to it. In such case, you should destroy this message, and notify
>> the sender immediately. If you have received this email in error, please
>> notify the sender or your sysadmin immediately by e-mail or telephone, and
>> delete the e-mail from any computer. If you or your employer does not
>> consent to internet e-mail messages of this kind, please notify the sender
>> immediately. All reasonable precautions have been taken to ensure no
>> viruses are present in this e-mail and attachments included. As the sender
>> cannot accept responsibility for any loss or damage arising from the use of
>> this e-mail or attachments it is recommended that you are responsible to
>> follow your virus checking procedures prior to use. The views, opinions,
>> conclusions and other informations expressed in this electronic mail are
>> not given or endorsed by any company including the network providers unless
>> otherwise indicated by an authorized representative independent of this
>> message.
>> -.. .. ... -.-. .-.. .- .. -- . .-. | -.. .. ... -.-. .-.. .- .. -- . .-.
>>
>>
>
> --
> Cheers,
> /z
>
> -.. .. ... -.-. .-.. .- .. -- . .-. | -.. .. ... -.-. .-.. .- .. -- . .-.
> CONFIDENTIALITY NOTICE AND DISCLAIMER: Access to this e-mail 

Re: Sanskrit/Devanagari fonts not exported to org-pdf output

[Zenny]

On Thu, Sep 21, 2023 at 10:26 PM Zenny  wrote:

>
> On Thu, Sep 21, 2023 at 9:32 PM Juan Manuel Macías 
> wrote:
>
>> Zenny writes:
>>
>> > Here it comes:
>> >
>> > org-latex-pdf-process is a variable defined in ‘ox-latex.el’.
>> >
>> > Its value is
>> > ("pdflatex -interaction nonstopmode -output-directory %o %f"
>> > "bibtex %b" "pdflatex -shell-escape -interaction nonstopmode -
>> > output-directory %o %f" "pdflatex -shell-escape -interaction
>> > nonstopmode -output-directory %o %f")
>> > Original value was
>> > ("latexmk -f -pdf -%latex -interaction=nonstopmode -
>> > output-directory=%o %f")
>>
>> It seems that you have modified the original value. Besides, the
>> docstring says:
>>
>> [...] %latex is the LaTeX compiler (see ‘org-latex-compiler’) [...]
>>
>> If you put 'pdflatex ...', it will always compile with pdflatex.
>>
>
Does `#+LATEX_COMPILER: lualatex` makes no difference?


>
>> I would recommend that you restore the original value of
>> org-latex-pdf-process, which uses latexmk (if it is installed, which
>> seems to be your case), which executes '%latex' (=
>> `org-latex-compiler'). latexmk is a perl script included in texlive that
>> is responsible for executing all the necessary compilations (including
>> the call to the bibliographic engine[1]).
>>
>
> When I checked the `ox-latex.el` it appears using latexmk
>
>  (defcustom org-latex-pdf-process
>>   (if (executable-find "latexmk")
>>   '("latexmk -f -pdf -%latex -interaction=nonstopmode
>> -output-directory=%o %f")
>> '("%latex -interaction nonstopmode -output-directory %o %f"
>>   "%latex -interaction nonstopmode -output-directory %o %f"
>>   "%latex -interaction nonstopmode -output-directory %o %f"))
>>   "Commands to process a LaTeX file to a PDF file.
>>
>
> And latexmk is already installed by texlive:
>
>  $ which latexmk
>> /opt/texlive/2023/bin/x86_64-linux/latexmk
>>
>
>
> Or do you mean to change latexmk in init.el?
>

I do see in init.el that it has been changed to something like:

(setq org-latex-pdf-process
>   '("pdflatex -interaction nonstopmode -output-directory %o %f"
>  "bibtex %b"
> "pdflatex -shell-escape -interaction nonstopmode -output-directory
> %o %f"
> "pdflatex -shell-escape -interaction nonstopmode -output-directory
> %o %f"))
>


> Thanks!
>
>>
>> [1] In some cases some configuration is required for latexmk via a
>> ~/latexmkrc file, but by default everything should work fine.
>>
>>
>>
>
> --
> Cheers,
> /z
>
> -.. .. ... -.-. .-.. .- .. -- . .-. | -.. .. ... -.-. .-.. .- .. -- . .-.
> CONFIDENTIALITY NOTICE AND DISCLAIMER: Access to this e-mail and its
> contents by anyone other than the intended recipient is unauthorized as it
> contains privileged and confidential information, and is subject to legal
> privilege. Please do not re/distribute it.  If you are not the intended
> recipient (or responsible for delivery of the message to such person), you
> may not use, copy, distribute or deliver the email and part of its contents
> to anyone this message (or any part of its contents or take any action in
> connection to it. In such case, you should destroy this message, and notify
> the sender immediately. If you have received this email in error, please
> notify the sender or your sysadmin immediately by e-mail or telephone, and
> delete the e-mail from any computer. If you or your employer does not
> consent to internet e-mail messages of this kind, please notify the sender
> immediately. All reasonable precautions have been taken to ensure no
> viruses are present in this e-mail and attachments included. As the sender
> cannot accept responsibility for any loss or damage arising from the use of
> this e-mail or attachments it is recommended that you are responsible to
> follow your virus checking procedures prior to use. The views, opinions,
> conclusions and other informations expressed in this electronic mail are
> not given or endorsed by any company including the network providers unless
> otherwise indicated by an authorized representative independent of this
> message.
> -.. .. ... -.-. .-.. .- .. -- . .-. | -.. .. ... -.-. .-.. .- .. -- . .-.
>
>

-- 
Cheers,
/z

-.. .. ... -.-. .-.. .- .. -- . .-. | -.. .. ... -.-. .-.. .- .. -- . .-.
CONFIDENTIALITY NOTICE AND DISCLAIMER: Access to this e-mail and its
contents by anyone other than the intended recipient is unauthorized as it
contains privileged and confidential information, and is subject to legal
privilege. Please do not re/distribute it.  If you are not the intended
recipient (or responsible for delivery of the message to such person), you
may not use, copy, distribute or deliver the email and part of its contents
to anyone this message (or any part of its contents or take any action in
connection to it. In such case, you should destroy this message, and notify
the sender immediately. If you have received this email in error, please
notify the sender or your sysadmin 

Re: Sanskrit/Devanagari fonts not exported to org-pdf output

[Zenny]

On Thu, Sep 21, 2023 at 9:32 PM Juan Manuel Macías 
wrote:

> Zenny writes:
>
> > Here it comes:
> >
> > org-latex-pdf-process is a variable defined in ‘ox-latex.el’.
> >
> > Its value is
> > ("pdflatex -interaction nonstopmode -output-directory %o %f"
> > "bibtex %b" "pdflatex -shell-escape -interaction nonstopmode -
> > output-directory %o %f" "pdflatex -shell-escape -interaction
> > nonstopmode -output-directory %o %f")
> > Original value was
> > ("latexmk -f -pdf -%latex -interaction=nonstopmode -
> > output-directory=%o %f")
>
> It seems that you have modified the original value. Besides, the
> docstring says:
>
> [...] %latex is the LaTeX compiler (see ‘org-latex-compiler’) [...]
>
> If you put 'pdflatex ...', it will always compile with pdflatex.
>
> I would recommend that you restore the original value of
> org-latex-pdf-process, which uses latexmk (if it is installed, which
> seems to be your case), which executes '%latex' (=
> `org-latex-compiler'). latexmk is a perl script included in texlive that
> is responsible for executing all the necessary compilations (including
> the call to the bibliographic engine[1]).
>

When I checked the `ox-latex.el` it appears using latexmk

 (defcustom org-latex-pdf-process
>   (if (executable-find "latexmk")
>   '("latexmk -f -pdf -%latex -interaction=nonstopmode
> -output-directory=%o %f")
> '("%latex -interaction nonstopmode -output-directory %o %f"
>   "%latex -interaction nonstopmode -output-directory %o %f"
>   "%latex -interaction nonstopmode -output-directory %o %f"))
>   "Commands to process a LaTeX file to a PDF file.
>

And latexmk is already installed by texlive:

 $ which latexmk
> /opt/texlive/2023/bin/x86_64-linux/latexmk
>


Or do you mean to change latexmk in init.el?

Thanks!

>
> [1] In some cases some configuration is required for latexmk via a
> ~/latexmkrc file, but by default everything should work fine.
>
>
>

-- 
Cheers,
/z

-.. .. ... -.-. .-.. .- .. -- . .-. | -.. .. ... -.-. .-.. .- .. -- . .-.
CONFIDENTIALITY NOTICE AND DISCLAIMER: Access to this e-mail and its
contents by anyone other than the intended recipient is unauthorized as it
contains privileged and confidential information, and is subject to legal
privilege. Please do not re/distribute it.  If you are not the intended
recipient (or responsible for delivery of the message to such person), you
may not use, copy, distribute or deliver the email and part of its contents
to anyone this message (or any part of its contents or take any action in
connection to it. In such case, you should destroy this message, and notify
the sender immediately. If you have received this email in error, please
notify the sender or your sysadmin immediately by e-mail or telephone, and
delete the e-mail from any computer. If you or your employer does not
consent to internet e-mail messages of this kind, please notify the sender
immediately. All reasonable precautions have been taken to ensure no
viruses are present in this e-mail and attachments included. As the sender
cannot accept responsibility for any loss or damage arising from the use of
this e-mail or attachments it is recommended that you are responsible to
follow your virus checking procedures prior to use. The views, opinions,
conclusions and other informations expressed in this electronic mail are
not given or endorsed by any company including the network providers unless
otherwise indicated by an authorized representative independent of this
message.
-.. .. ... -.-. .-.. .- .. -- . .-. | -.. .. ... -.-. .-.. .- .. -- . .-.

Re: Sanskrit/Devanagari fonts not exported to org-pdf output

[Juan Manuel Macías]

Zenny writes:

> Here it comes:
>
> org-latex-pdf-process is a variable defined in ‘ox-latex.el’.
>
> Its value is
> ("pdflatex -interaction nonstopmode -output-directory %o %f"
> "bibtex %b" "pdflatex -shell-escape -interaction nonstopmode -
> output-directory %o %f" "pdflatex -shell-escape -interaction
> nonstopmode -output-directory %o %f")
> Original value was 
> ("latexmk -f -pdf -%latex -interaction=nonstopmode -
> output-directory=%o %f")

It seems that you have modified the original value. Besides, the
docstring says:

[...] %latex is the LaTeX compiler (see ‘org-latex-compiler’) [...]

If you put 'pdflatex ...', it will always compile with pdflatex.

I would recommend that you restore the original value of
org-latex-pdf-process, which uses latexmk (if it is installed, which
seems to be your case), which executes '%latex' (=
`org-latex-compiler'). latexmk is a perl script included in texlive that
is responsible for executing all the necessary compilations (including
the call to the bibliographic engine[1]).

[1] In some cases some configuration is required for latexmk via a
~/latexmkrc file, but by default everything should work fine.

Re: Sanskrit/Devanagari fonts not exported to org-pdf output

[Zenny]

On Thu, Sep 21, 2023 at 8:28 PM Juan Manuel Macías 
wrote:

> Zenny writes:
>
> > With above code for LuaLaTeX, I have also appended:
> >
> > #+LATEX_COMPILER: lualatex
> >
> > even after specifying the LaTeX compiler to lualatex a report that
> > says, the compiler seems to use pdflatex:
> >
> > ! Fatal Package fontspec Error: The fontspec package requires
> > either XeTeX or
> > (fontspec)  LuaTeX.
> > (fontspec)
> > (fontspec)  You must change your typesetting
> > engine to,
> > (fontspec)  e.g., "xelatex" or "lualatex"
> > instead of
> > (fontspec)  "latex" or "pdflatex".
> >
> > Type  to continue.
> >  ...
> >
> > l.45 \msg_fatal:nn {fontspec} {cannot-use-pdftex}
> >
> >
> > Entire texlive packages are installed and lualatex binary is at:
> >
> > $ which lualatex
> > /opt/texlive/2023/bin/x86_64-linux/lualatex
>
> Can you please show here the value of 'org-latex-pdf-process'?
>
> (M-x describe-variable RET org-latex-pdf-process RET)
>

Here it comes:

org-latex-pdf-process is a variable defined in ‘ox-latex.el’.
>
> Its value is
> ("pdflatex -interaction nonstopmode -output-directory %o %f" "bibtex %b"
> "pdflatex -shell-escape -interaction nonstopmode -output-directory %o %f"
> "pdflatex -shell-escape -interaction nonstopmode -output-directory %o %f")
> Original value was
> ("latexmk -f -pdf -%latex -interaction=nonstopmode -output-directory=%o
> %f")
>
> Commands to process a LaTeX file to a PDF file.
>
> The command output will be parsed to extract compilation errors and
> warnings according to ‘org-latex-known-warnings’.
>
> This is a list of strings, each of them will be given to the
> shell as a command.  %f in the command will be replaced by the
> relative file name, %F by the absolute file name, %b by the file
> base name (i.e. without directory and extension parts), %o by the
> base directory of the file, %O by the absolute file name of the
> output file, %latex is the LaTeX compiler (see
> ‘org-latex-compiler’), and %bib is the BibTeX-like compiler (see
> ‘org-latex-bib-compiler’).
>
> The reason why this is a list is that it usually takes several
> runs of ‘pdflatex’, maybe mixed with a call to ‘bibtex’.  Org
> does not have a clever mechanism to detect which of these
> commands have to be run to get to a stable result, and it also
> does not do any error checking.
>
> Consider a smart LaTeX compiler such as ‘texi2dvi’ or ‘latexmk’,
> which calls the "correct" combinations of auxiliary programs.
>
> Alternatively, this may be a Lisp function that does the
> processing, so you could use this to apply the machinery of
> AUCTeX or the Emacs LaTeX mode.  This function should accept the
> file name as its single argument.
>
>   You can customize this variable.
>

Thanks!


> Best regards,
>
> Juan Manuel
>
> --
> Juan Manuel Macías
>
> https://juanmanuelmacias.com
>
> https://lunotipia.juanmanuelmacias.com
>
> https://gnutas.juanmanuelmacias.com
>
>
>

-- 
Cheers,
/z

-.. .. ... -.-. .-.. .- .. -- . .-. | -.. .. ... -.-. .-.. .- .. -- . .-.
CONFIDENTIALITY NOTICE AND DISCLAIMER: Access to this e-mail and its
contents by anyone other than the intended recipient is unauthorized as it
contains privileged and confidential information, and is subject to legal
privilege. Please do not re/distribute it.  If you are not the intended
recipient (or responsible for delivery of the message to such person), you
may not use, copy, distribute or deliver the email and part of its contents
to anyone this message (or any part of its contents or take any action in
connection to it. In such case, you should destroy this message, and notify
the sender immediately. If you have received this email in error, please
notify the sender or your sysadmin immediately by e-mail or telephone, and
delete the e-mail from any computer. If you or your employer does not
consent to internet e-mail messages of this kind, please notify the sender
immediately. All reasonable precautions have been taken to ensure no
viruses are present in this e-mail and attachments included. As the sender
cannot accept responsibility for any loss or damage arising from the use of
this e-mail or attachments it is recommended that you are responsible to
follow your virus checking procedures prior to use. The views, opinions,
conclusions and other informations expressed in this electronic mail are
not given or endorsed by any company including the network providers unless
otherwise indicated by an authorized representative independent of this
message.
-.. .. ... -.-. .-.. .- .. -- . .-. | -.. .. ... -.-. .-.. .- .. -- . .-.

Re: worg - out of date item

[Colin Baxter]

> Ihor Radchenko  writes:

> Colin Baxter  writes:
>> https://orgmode.org/worg/org-tutorials/org-google-sync.html
>> suggests using the command line program 'googlecl'. That program
>> appears to have been dead for several years, at least according
>> to https://code.google.com/archive/p/googlecl/.

> Would you be interested to create a patch that removes the part of
> the tutorial dealing with gogglecl?

Ok. However, it will probably be a week or two before I have the time.


Colin Baxter.

Re: Sanskrit/Devanagari fonts not exported to org-pdf output

[Juan Manuel Macías]

Zenny writes:

> With above code for LuaLaTeX, I have also appended:
>
> #+LATEX_COMPILER: lualatex
>
> even after specifying the LaTeX compiler to lualatex a report that
> says, the compiler seems to use pdflatex:
>
> ! Fatal Package fontspec Error: The fontspec package requires
> either XeTeX or
> (fontspec)  LuaTeX.
> (fontspec)  
> (fontspec)  You must change your typesetting
> engine to,
> (fontspec)  e.g., "xelatex" or "lualatex"
> instead of
> (fontspec)  "latex" or "pdflatex".
>
> Type  to continue.
>  ...  
>   
> l.45 \msg_fatal:nn {fontspec} {cannot-use-pdftex}
>
>  
> Entire texlive packages are installed and lualatex binary is at:
>
> $ which lualatex
> /opt/texlive/2023/bin/x86_64-linux/lualatex

Can you please show here the value of 'org-latex-pdf-process'?

(M-x describe-variable RET org-latex-pdf-process RET)

Best regards,

Juan Manuel 

-- 
Juan Manuel Macías 

https://juanmanuelmacias.com

https://lunotipia.juanmanuelmacias.com

https://gnutas.juanmanuelmacias.com

Re: Sanskrit/Devanagari fonts not exported to org-pdf output

[Zenny]

Hi Juan,

On Thu, Sep 21, 2023 at 5:33 PM Juan Manuel Macías 
wrote:

> Hi, Zenny,
>
> Zenny writes:
>
> > Where does this preamble goes to? Any example?
>
> As in your example, using latex_header keywords (replacing the
> polyglossia code with the babel code):
>
> #+LaTeX_Header: \usepackage[english]{babel}
> #+LaTeX_Header: \usepackage{fontspec}
> #+LaTeX_Header: \newfontscript{Devanagari}{deva}
> #+LaTeX_Header: \babelprovide[onchar=ids fonts]{sanskrit-devanagari}
> #+LaTeX_Header: \babelfont[sanskrit-devanagari]{rm}{Noto Sans Devanagari}
>
> > Yet I am a bit confused because the Sanskrit/Devanagari words are used
> > not in a whole block, but in between English sentences, eg.:
>
> With Polyglossia and babel it is necessary to enter a command that
> changes the language. In the case of polyglossia, if you don't
> explicitly switch to Sanskrit the font you declared for Sanskrit is not
> used, and LaTeX still thinks the text is English. Polyglossia uses some
> commands similar to those of babel (\selectlanguage, for long texts) and
> other native ones, such as \text{text}, where  is the
> secondary language. In babel you have the command
> \foreignlanguage{}{text}. For example (using polyglossia):
>
> Old expression goes like \textsanskrit{स्वस्ति सत्यं वचति}
>
> Of course, in org you would have to use some trick, like defining some
> macro (since org does not have, at the moment[1], a native language
> switching method):
>
> #+macro: sanskrit @@latex:\textsanskrit{@@$1@@latex:}@@
>
> Old expression goes like {{{sanskrit(स्वस्ति सत्यं वचति)}}}
>
> With LuaLaTeX, babel can associate a non latin language to a font
> without requiring an explicit language switch:
>
> #+LaTeX_Header: \usepackage[english]{babel}
> #+LaTeX_Header: \usepackage{fontspec}
> #+LaTeX_Header: \newfontscript{Devanagari}{deva}
> #+LaTeX_Header: \babelprovide[onchar=ids fonts]{sanskrit-devanagari}
> #+LaTeX_Header: \babelfont[sanskrit-devanagari]{rm}{Noto Sans Devanagari}
>

With above code for LuaLaTeX, I have also appended:

#+LATEX_COMPILER: lualatex

even after specifying the LaTeX compiler to lualatex a report that says,
the compiler seems to use pdflatex:

! Fatal Package fontspec Error: The fontspec package requires either XeTeX
> or
> (fontspec)  LuaTeX.
> (fontspec)
> (fontspec)  You must change your typesetting engine to,
> (fontspec)  e.g., "xelatex" or "lualatex" instead of
> (fontspec)  "latex" or "pdflatex".
>
> Type  to continue.
>  ...
>
> l.45 \msg_fatal:nn {fontspec} {cannot-use-pdftex}
>

Entire texlive packages are installed and lualatex binary is at:

$ which lualatex
> /opt/texlive/2023/bin/x86_64-linux/lualatex
>

Thanks for your attention!
/z


> Old expression goes like स्वस्ति सत्यं वचति
>
> [1] You might be interested in this thread:
> https://list.orgmode.org/878r9t7x7y@posteo.net/
>


-- 
Cheers,
/z

-.. .. ... -.-. .-.. .- .. -- . .-. | -.. .. ... -.-. .-.. .- .. -- . .-.
CONFIDENTIALITY NOTICE AND DISCLAIMER: Access to this e-mail and its
contents by anyone other than the intended recipient is unauthorized as it
contains privileged and confidential information, and is subject to legal
privilege. Please do not re/distribute it.  If you are not the intended
recipient (or responsible for delivery of the message to such person), you
may not use, copy, distribute or deliver the email and part of its contents
to anyone this message (or any part of its contents or take any action in
connection to it. In such case, you should destroy this message, and notify
the sender immediately. If you have received this email in error, please
notify the sender or your sysadmin immediately by e-mail or telephone, and
delete the e-mail from any computer. If you or your employer does not
consent to internet e-mail messages of this kind, please notify the sender
immediately. All reasonable precautions have been taken to ensure no
viruses are present in this e-mail and attachments included. As the sender
cannot accept responsibility for any loss or damage arising from the use of
this e-mail or attachments it is recommended that you are responsible to
follow your virus checking procedures prior to use. The views, opinions,
conclusions and other informations expressed in this electronic mail are
not given or endorsed by any company including the network providers unless
otherwise indicated by an authorized representative independent of this
message.
-.. .. ... -.-. .-.. .- .. -- . .-. | -.. .. ... -.-. .-.. .- .. -- . .-.

Bug with "BEAMER_OPT: shrink" and links

[Guillaume MULLER]

Hi,

Here is a small test.org file that uses shrink to reduce the size of the slides:

---

* Shrink + Link broken
:PROPERTIES:
:BEAMER_OPT: shrink=10
:END:
**  Block1 with links
+ Some text [[https://www.google.com][Link1]]
+ \small [[https://www.microsoft.com][Link2]]
+ A very long text before the link [[https://mail.google.com][Link3]] text text
** Block2 with links
+ Test [[https://www.yopmail.com][Link4]]
+ [[https://test.it][Link5]]


* Test2
:PROPERTIES:
:BEAMER_OPT: shrink=60
:END:
** Block1 with links
+ Some text [[https://www.google.com][Link1]]
+ \small [[https://www.microsoft.com][Link2]]
+ A very long text before the link [[https://mail.google.com][Link3]] text text
** Block2 with links
+ Test [[https://www.yopmail.com][Link4]]
+ [[https://test.it][Link5]]


---

If you run 'org-beamer-export-to-pdf' on this file, you'll get a PDF where the 
clickable area for the link is most of the time way out of the text for the 
link...

I've search the web, no mention of that.

Cheers

GM


OpenPGP_0xF3BCAD9F46F5FADC.asc
Description: OpenPGP public key


OpenPGP_signature
Description: OpenPGP digital signature

How to hide square brackets around [[url][links]]?

[William Denton]

A fix by Ihor a few weeks ago solved a problem ("org-cycle does not unfold some 
subtrees") but I think there's still a related little bug with searching, 
perhaps just with Swiper, that I can't replicate but am watching.


Sometimes when searching with Swiper, the display of (some) links is changed and 
instead of seeing the anchor text formatted as a link I see the full raw 
[[URL][anchor text]].


How can I make this go back to showing just the anchor text?  I've tried 
toggling visible-mode and using org-toggle-link-display but neither work, so I 
have to C-x C-v and reload the file.  Should these commands be reformatting all 
the links in the buffer, and the fact they don't work is a sign of the bug?


Bill

--
William Denton
https://www.miskatonic.org/
Librarian, artist and licensed private investigator.
Toronto, Canada
CO₂: 418.58 ppm (Mauna Loa Observatory, 2023-09-20)

Re: Sanskrit/Devanagari fonts not exported to org-pdf output

[Juan Manuel Macías]

Hi, Zenny,

Zenny writes:

> Where does this preamble goes to? Any example?

As in your example, using latex_header keywords (replacing the
polyglossia code with the babel code):

#+LaTeX_Header: \usepackage[english]{babel}
#+LaTeX_Header: \usepackage{fontspec}
#+LaTeX_Header: \newfontscript{Devanagari}{deva}
#+LaTeX_Header: \babelprovide[onchar=ids fonts]{sanskrit-devanagari}
#+LaTeX_Header: \babelfont[sanskrit-devanagari]{rm}{Noto Sans Devanagari}

> Yet I am a bit confused because the Sanskrit/Devanagari words are used
> not in a whole block, but in between English sentences, eg.:

With Polyglossia and babel it is necessary to enter a command that
changes the language. In the case of polyglossia, if you don't
explicitly switch to Sanskrit the font you declared for Sanskrit is not
used, and LaTeX still thinks the text is English. Polyglossia uses some
commands similar to those of babel (\selectlanguage, for long texts) and
other native ones, such as \text{text}, where  is the
secondary language. In babel you have the command
\foreignlanguage{}{text}. For example (using polyglossia):

Old expression goes like \textsanskrit{स्वस्ति सत्यं वचति}

Of course, in org you would have to use some trick, like defining some
macro (since org does not have, at the moment[1], a native language
switching method):

#+macro: sanskrit @@latex:\textsanskrit{@@$1@@latex:}@@

Old expression goes like {{{sanskrit(स्वस्ति सत्यं वचति)}}}

With LuaLaTeX, babel can associate a non latin language to a font
without requiring an explicit language switch:

#+LaTeX_Header: \usepackage[english]{babel}
#+LaTeX_Header: \usepackage{fontspec}
#+LaTeX_Header: \newfontscript{Devanagari}{deva}
#+LaTeX_Header: \babelprovide[onchar=ids fonts]{sanskrit-devanagari}
#+LaTeX_Header: \babelfont[sanskrit-devanagari]{rm}{Noto Sans Devanagari}

Old expression goes like स्वस्ति सत्यं वचति

[1] You might be interested in this thread: 
https://list.orgmode.org/878r9t7x7y@posteo.net/

Re: [PATCH] ob-maxima.el, etc. (was Re: [MAINTENANCE] On how much we can expose internals into defcustom)

[Leo Butler]

On Thu, Sep 21 2023, Ihor Radchenko  wrote:

> Leo Butler  writes:
>
 +(defconst org-babel-header-args:maxima
 +  '((batch   . :any)
>>>
>>> Why :any? Only two values are allowed here.
>>>
 +(graphics-pkg. :any))
>>>
>>> Same. The value is a closed list.
>>
>> I have made the change requested.
>>
>> However, beyond the documentation value, I don't see this variable's
>> values being used.
>
> In completion. See `pcomplete/org-mode/block-option/src'.
> Also, in org-lint. See `org-lint-wrong-header-argument'.

Thanks.

>
>> Fixed. I don't use `apropos', so I didn't see the problem (and I had
>> failed to absorb everything in §D.6).
>
> M-x checkdoc checks for many of the §D.6 conventions.

Yes, I discovered that from the documentation. I must have done
something wrong, because it didn't work for me when I tried it, but
after re-starting emacs it is working.

>
>> Please see the attached, revised patch. It fixes the problems that you
>> have identified–except for the way that the gnuplot terminal is
>> determined. I would like to leave that for a subsequent patch, mainly
>> because this one has become quite large.
>
> Ok. Thanks!
>
> I have one more comment on the tests:
>
>> +(ert-deftest ob-maxima/batch+verbatim+eof-error ()
>> +  "Exercise the `:batch' header argument.  Send invalid input to
>> +Maxima."
>> +  (unwind-protect
>
> What is the purpose of this `unwind-protect'?
> In its current form, it does nothing because no UNWINDFORMS are
> provided.

I copied the forms from tests I had written for ob-octave, without
thinking about why those tests were wrapped in an `unwind-protect'
form. The attached patch removes them, otherwise it is identical to the
previous patch.

Leo

From 425ea8ed47af5bccfd9bc37f1e4de4c53cc9b1f1 Mon Sep 17 00:00:00 2001
From: Leo Butler 
Date: Tue, 19 Sep 2023 13:36:06 -0500
Subject: [PATCH] * lisp/ob-maxima.el: enable use of `batch' loader and `draw'

* (org-babel-header-args:maxima): Document the two new header
arguments (batch and graphics-pkg) that are specific to ob-maxima.
* (org-babel-maxima--command-arguments-default): A new variable
storing the default command-line argument(s).  This value was
hard-coded in `org-babel-maxima:execute'.
* (org-babel-maxima--graphic-package-options): A new variable that
stores an alist of Maxima graphics packages and the Maxima code to set
up that package.
* (org-babel-maxima--default-epilogue): A new variable that stores an
alist of the clean-up code that is run at end of a `graphical-output'
or `non-graphical-output' source block.
* (org-babel-maxima--output-filter-regexps): A new variable that
stores a list of regexps to identify "bad" output lines to be removed
from Maxima's output.  Source-code comments document each regexp's
purpose.  Two additional regexps have been added: one filters
un-wanted output from `batch' and the other removes empty input lines
that `batch'-ed output may spuriously produce (actual empty input
lines are syntax errors, see the new tests below).
* (org-babel-maxima--output-filter): A new function that takes a
single line of Maxima output.  It returns nil if the line has zero
length or matches a regexp in
`org-babel-maxima--output-filter-regexps'; otherwise, it returns the
line.  This function and regexp replace the hard-coded filter in
`org-babel-execute:maxima'.
* (org-babel-maxima-expand): Prepare the source block for execution,
depending on whether it is producing graphical output or not.  In case
of graphical output, use the `graphics-pkg' header to set the graphics
package and use `org-babel-maxima--graphic-package-options' to set-up
the package.  Grovel the graphics terminal from the output filename.
* (org-babel-execute:maxima): Use the :batch header argument and
`org-babel-maxima--command-arguments-default' to execute the source
block.  Replace the existing, in-line output filter and its regexps
with `org-babel-maxima--output-filter' and
`org-babel-maxima--output-filter-regexps'.

* testing/examples/ob-maxima-test.org: Add test examples.

Include examples of the batch-related tests from
testing/lisp/test-ob-maxima.el.  Provide an example of the
`:graphics-pkg' header argument with the `draw' package.

* testing/lisp/test-ob-maxima.el: Introduce six new, batch-related
test functions.  Each test exercises the :batch header argument.  The
response to unusual inputs is tested (empty strings, strings with just
whitespace, input with the `:lisp' reader, and two syntax-related
errors).
---
 lisp/ob-maxima.el   | 115 +---
 testing/examples/ob-maxima-test.org |  54 +
 testing/lisp/test-ob-maxima.el  | 101 
 3 files changed, 242 insertions(+), 28 deletions(-)

diff --git a/lisp/ob-maxima.el b/lisp/ob-maxima.el
index d1d7c7424..eac44ff9a 100644
--- a/lisp/ob-maxima.el
+++ b/lisp/ob-maxima.el
@@ -37,6 +37,11 @@
 
 (require 'ob)
 
+(defconst org-babel-header-args:maxima
+  '((batch   . 

Re: Sanskrit/Devanagari fonts not exported to org-pdf output

[Zenny]

Thanks Juan for prompt response, my replies inline below:

On Thu, Sep 21, 2023 at 10:24 AM Juan Manuel Macías 
wrote:

> Hi,
>
> I would recommend that you use babel, as it is the official package for
> language support and now has many more options than polyglossia.


Thanks for the pointer and explanation.


> You can
> try this preamble (compiles in LuaLaTeX):
>
> \documentclass{article}
> \usepackage[english]{babel}
> \usepackage{fontspec}
> \newfontscript{Devanagari}{deva}
> \babelprovide[onchar=ids fonts]{sanskrit-devanagari}
> \babelfont[sanskrit-devanagari]{rm}{Noto Sans Devanagari}
>

Where does this preamble goes to? Any example?


>
> With \babelprovide... there is no need to add a \selectlanguage or other
> similar command. The problem with your example is that you need to put a
> command to select the language before the Devanagari text, like
> \selectlanguage{sanskrit}
>

Yet I am a bit confused because the Sanskrit/Devanagari words are used not
in a whole block, but in between English sentences, eg.:

Old expression goes like स्वस्ति सत्यं वचति (meaning 'Always tell the truth
> with positive vibes') where स्वस्ति means positive, सत्यं means truth and
> वचति means tell or speak out.
>

 Any example would be appreciated for pdf export. Thanks again.


> Best regards,
>
> Juan Manuel
>
> Zenny  escribió:
>
> > Hi,
> >
> > I tried to export to pdf with the following:
> >
> > #+LATEX_HEADER: \usepackage{polyglossia}
> > #+LATEX_HEADER: \usepackage{fontspec}
> > #+LATEX_COMPILER: xelatex (also tried with lualatex)
> > #+LATEX_HEADER:  \setmainlanguage{english}
> > #+LATEX_HEADER:  \setotherlanguage{sanskrit}
> > #+LATEX_HEADER:   \newfontfamily\devanagarifont{Noto Serif
> > Devanagari}
> >
> > स्वस्ति सत्यं वचति
> >
> > but it exports alright to odt, and even pandoc exports alright
> > directly from org file to docx file, but the Sanskrit/Devanagari fonts
> > are skipped (blank) in pdf output when exported directly from org file
> > with C-c C-e l o.
> >
> > Already tried with the solutions provided in
> >
> https://emacs.stackexchange.com/questions/27576/exporting-devanagarai-text-from-org-mode-to-latex
> ,
> > but there are no such options (variables defined) after 'M-x
> > customize-group' available.
>
> --
> Juan Manuel Macías
>
> https://juanmanuelmacias.com
>
> https://lunotipia.juanmanuelmacias.com
>
> https://gnutas.juanmanuelmacias.com
>
>
>

-- 
Cheers,
/z

-.. .. ... -.-. .-.. .- .. -- . .-. | -.. .. ... -.-. .-.. .- .. -- . .-.
CONFIDENTIALITY NOTICE AND DISCLAIMER: Access to this e-mail and its
contents by anyone other than the intended recipient is unauthorized as it
contains privileged and confidential information, and is subject to legal
privilege. Please do not re/distribute it.  If you are not the intended
recipient (or responsible for delivery of the message to such person), you
may not use, copy, distribute or deliver the email and part of its contents
to anyone this message (or any part of its contents or take any action in
connection to it. In such case, you should destroy this message, and notify
the sender immediately. If you have received this email in error, please
notify the sender or your sysadmin immediately by e-mail or telephone, and
delete the e-mail from any computer. If you or your employer does not
consent to internet e-mail messages of this kind, please notify the sender
immediately. All reasonable precautions have been taken to ensure no
viruses are present in this e-mail and attachments included. As the sender
cannot accept responsibility for any loss or damage arising from the use of
this e-mail or attachments it is recommended that you are responsible to
follow your virus checking procedures prior to use. The views, opinions,
conclusions and other informations expressed in this electronic mail are
not given or endorsed by any company including the network providers unless
otherwise indicated by an authorized representative independent of this
message.
-.. .. ... -.-. .-.. .- .. -- . .-. | -.. .. ... -.-. .-.. .- .. -- . .-.

Re: Exporting elisp: and shell: links

[Ihor Radchenko]

Max Nikulin  writes:

>> As a user, I would expect
>> 
>>[[elisp:(identity "a")]]
>> 
>> to be export-equivalent to
>> 
>>src_elisp[:exports code]{(identity "a")}
>> 
>> across all backends.

Makes sense.

>>> What is your expectation for links having description?
>>>
>>> [[elisp:(identity "a")][Run it]]
>> 
>> Good point!  Perhaps we just need to find a
>> good symbol that would work well between the
>> Elisp code and the description?
>> 
>> For example
>> 
>>/Run it/ \to src_elisp[:exports code]{(identity "a")}
>> 
>> exports to ASCII as
>> 
>>/Run it/ -> `(identity "a")'
>> 
>> Of course, \to could be something else...

Another idea: use code as description displayed in the tooltip (in html).
Copy-on-clip also makes sense.

Yet another idea: export code inside a footnote. This will work across
all the backends.

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at .
Support Org development at ,
or support my work at 

Re: [PATCH] ob-maxima.el, etc. (was Re: [MAINTENANCE] On how much we can expose internals into defcustom)

[Ihor Radchenko]

Leo Butler  writes:

>>> +(defconst org-babel-header-args:maxima
>>> +  '((batch   . :any)
>>
>> Why :any? Only two values are allowed here.
>>
>>> +(graphics-pkg. :any))
>>
>> Same. The value is a closed list.
>
> I have made the change requested.
>
> However, beyond the documentation value, I don't see this variable's
> values being used.

In completion. See `pcomplete/org-mode/block-option/src'.
Also, in org-lint. See `org-lint-wrong-header-argument'.

> Fixed. I don't use `apropos', so I didn't see the problem (and I had
> failed to absorb everything in §D.6).

M-x checkdoc checks for many of the §D.6 conventions.

> Please see the attached, revised patch. It fixes the problems that you
> have identified–except for the way that the gnuplot terminal is
> determined. I would like to leave that for a subsequent patch, mainly
> because this one has become quite large.

Ok. Thanks!

I have one more comment on the tests:

> +(ert-deftest ob-maxima/batch+verbatim+eof-error ()
> +  "Exercise the `:batch' header argument.  Send invalid input to
> +Maxima."
> +  (unwind-protect

What is the purpose of this `unwind-protect'?
In its current form, it does nothing because no UNWINDFORMS are
provided.

> +(org-test-with-temp-text
> +(format "#+name: ob-maxima/batch+verbatim+eof-error
> +#+begin_src maxima  :results verbatim :batch batch :cmdline --quiet
> +x:
> +#+end_src
> +")
> +  (should (string-match "end of file while scanning expression\\."
> +(org-babel-execute-src-block))



-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at .
Support Org development at ,
or support my work at 

Re: Fallback fonts in LaTeX export for non latin scripts

[Ihor Radchenko]

Juan Manuel Macías  writes:

> [...] I am very interested in all possible improvements in babel so that
> it integrates as best as possible with automatically generated files.
> Among them are the possibility of using BCP47 codes or using a language
> (at least basically) without the need for a prior declaration. These are
> things already done, but there are others that can still be improved.

Do I understand correctly that babel, in future, may be able to
auto-detect more languages without explicitly declaring them?

> [...] any suggestion for improvement is very welcome [...]

This is a bit too out of context. Improvement of what?

> Among the things I agree on is name issue. I am unifying the dice in the
> CLDR as much as possible, and already, in fact, it is very advanced:
>
> https://latex3.github.io/babel/guides/locale-naming.html

AFAIU, the relevant quote is

They are taken from the CLDR. Wherever the CLDR doesn’t provide a name
(eg, “Medieval Latin”), the pattern followed in practice for other names
is applied, namely, use the ‘natural’ form in English: medievallatin.
They should be preferably based on the description field in the IANA
registry (eg, polytonicgreek), although some simplifications can be
necessary, because some names are “too” descriptive. See also the
templates for about 500 locales already available. As a secondary
source, Glottolog is used, too. (Wikipedia articles can be taken as a
complementary but unreliable source, and its information must be
verified; on the other hand, internal data, like this one, is useful for
both names and tags.)

I am not very sure about "some simplifications" referring to IANA. I
guess it is referring to language names in
https://www.iana.org/assignments/language-subtag-registry/language-subtag-registry
like "Puter idiom of Romansh".

>From Org perspective, verbosity is not a primary concern as long as we
provide #+language: completion support. Probably, we should favor names
that are more likely known (or can be easily found) by the language
users. IANA and https://glottolog.org/ look like good sources we can
link to.

We can also provide multiple language name variants though I don't see a
need to bother unless we get user requests to do such thing.

> The ini files contain information that is not actually used by babel,
> but that could be useful in other packages or even external
> applications. One of them is the name of the language in English and in
> the vernacular form, as they are in the Unicode CLDR. As I explain in
> the link I gave you, the purpose is that the babel name is based on the
> CLDR name with mechanical changes. Anyway, CLDR names are also included
> in the ini files, to establish correspondences more easily.

Are the "verbose" language names (name.english) changed to "simplify"
them? Or is it only done for name.babel?

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at .
Support Org development at ,
or support my work at 

Re: worg - out of date item

[Ihor Radchenko]

Colin Baxter  writes:

> https://orgmode.org/worg/org-tutorials/org-google-sync.html suggests
> using the command line program 'googlecl'. That program appears to have
> been dead for several years, at least according to
> https://code.google.com/archive/p/googlecl/.

Would you be interested to create a patch that removes the part of the
tutorial dealing with gogglecl?

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at .
Support Org development at ,
or support my work at 

Re: [BUG] tikz latex figures don't render properly in the html output. [9.6.6 (release_9.6.6 @ /usr/share/emacs/29.1/lisp/org/)]

[Ihor Radchenko]

chris  writes:

> At some point in the past I've experimented with
> https://tikzjax.com/
> So I changed something somewhere in the org-mode config and it just worked, 
> it 
> was quite straightforward to do. I however probably don't have notes on how I 
> did it.
> I didn't insist in that direction because it wasn't working with TikZ libs, 
> specifically tikzcd.
> But it was really nice.
> This however is implementing many TikZ libraries, I don't know if it's usable 
> with org-mode, but it looks totally great, it's from Obsidian but it's on 
> Github
> https://github.com/artisticat1/obsidian-tikzjax
> IMO this sort of solution is very nice.

If you can write a tutorial that could be added to WORG, it would be
welcome.

Also, do you have any idea about the licence for https://tikzjax.com/ ?

>> I can also confirm that TEC's feature branch does not have this bug.
>
> What is TEC?

Timothy aka TECosaur - one of the Org mode contributors.
We are talking about https://orgmode.org/list/87lek2up0w@tec.tecosaur.net

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at .
Support Org development at ,
or support my work at 

Re: Sanskrit/Devanagari fonts not exported to org-pdf output

[Juan Manuel Macías]

Hi,

I would recommend that you use babel, as it is the official package for
language support and now has many more options than polyglossia. You can
try this preamble (compiles in LuaLaTeX):

\documentclass{article}
\usepackage[english]{babel}
\usepackage{fontspec}
\newfontscript{Devanagari}{deva}
\babelprovide[onchar=ids fonts]{sanskrit-devanagari}
\babelfont[sanskrit-devanagari]{rm}{Noto Sans Devanagari}

With \babelprovide... there is no need to add a \selectlanguage or other
similar command. The problem with your example is that you need to put a
command to select the language before the Devanagari text, like
\selectlanguage{sanskrit}

Best regards,

Juan Manuel 

Zenny  escribió:

> Hi,
>
> I tried to export to pdf with the following:
>
> #+LATEX_HEADER: \usepackage{polyglossia}
> #+LATEX_HEADER: \usepackage{fontspec}
> #+LATEX_COMPILER: xelatex (also tried with lualatex)
> #+LATEX_HEADER:  \setmainlanguage{english}
> #+LATEX_HEADER:  \setotherlanguage{sanskrit}
> #+LATEX_HEADER:   \newfontfamily\devanagarifont{Noto Serif
> Devanagari}
>
> स्वस्ति सत्यं वचति 
>
> but it exports alright to odt, and even pandoc exports alright
> directly from org file to docx file, but the Sanskrit/Devanagari fonts
> are skipped (blank) in pdf output when exported directly from org file
> with C-c C-e l o.
>
> Already tried with the solutions provided in 
> https://emacs.stackexchange.com/questions/27576/exporting-devanagarai-text-from-org-mode-to-latex,
> but there are no such options (variables defined) after 'M-x
> customize-group' available.

-- 
Juan Manuel Macías 

https://juanmanuelmacias.com

https://lunotipia.juanmanuelmacias.com

https://gnutas.juanmanuelmacias.com

Sanskrit/Devanagari fonts not exported to org-pdf output

[Zenny]

Hi,

I tried to export to pdf with the following:

#+LATEX_HEADER: \usepackage{polyglossia}
> #+LATEX_HEADER: \usepackage{fontspec}
> #+LATEX_COMPILER: xelatex (also tried with lualatex)
> #+LATEX_HEADER:  \setmainlanguage{english}
> #+LATEX_HEADER:  \setotherlanguage{sanskrit}
> #+LATEX_HEADER:   \newfontfamily\devanagarifont{Noto Serif Devanagari}
>
> स्वस्ति सत्यं वचति
>

but it exports alright to odt, and even pandoc exports alright directly
from org file to docx file, but the Sanskrit/Devanagari fonts are skipped
(blank) in pdf output when exported directly from org file with C-c C-e l o.

Already tried with the solutions provided in
https://emacs.stackexchange.com/questions/27576/exporting-devanagarai-text-from-org-mode-to-latex,
but there are no such options (variables defined) after 'M-x
customize-group' available.
-- 
Cheers,
/z

worg - out of date item

[Colin Baxter]

https://orgmode.org/worg/org-tutorials/org-google-sync.html suggests
using the command line program 'googlecl'. That program appears to have
been dead for several years, at least according to
https://code.google.com/archive/p/googlecl/.

Colin Baxter.