Sort alphabetically and order across sub-headings
Hi, I am trying to create a list where the ordered list numbering expands across sub-headings: * Bacteria ** Acetobacter Species 1. Acetobacter aceti 2. Acetobacter rasens * Fungi ** Candida Species 3. Candida famata 4. Candida firmetaria * Others Unidentified Species 5. Escherichia species 6. Serratia species 7. Citrobacter species 8. Klebsiella species 9. Bacillus species How can one sort the ordered list alphabetically? Appreciate any input. Thanks Cheers, /z
Re: Sanskrit/Devanagari fonts not exported to org-pdf output
On Fri, Sep 22, 2023 at 5:13 PM Juan Manuel Macías
wrote:
> Zenny writes:
>
> > Appended the above line, but the rendering became much worse, see
> > Ganapati and BiSht lines:
>
> Well, try this:
>
> 1. remove \newfontscript{Devanagari}{deva}
>
> 2. modify the \babelprovide for Bengali like this:
>
> \babelprovide[onchar=ids fonts,import,script=Bengali]{sanskrit-bengali}
>
> (it seems like something strange is happening between the Noto Sans
> Bengali font and LuaTeX. I don't know if it's a bug, but if I explicitly
> add the script name, it seems to render the words well. With Noto Serif
> Bengali it doesn't happen).
>
Thank you, I made the changes as you advised and changed the font to Noto
Serif variant, and it worked like wonder.
The problem is solved. Thanks a zillion.
Now it renders alright as seen in the screenshot. Have a nice weekend, Juan.
>
> Sorry, I'm afraid I don't know the language, so I'm going a bit blind
> here...
>
--
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
On Fri, Sep 22, 2023 at 12:02 PM Juan Manuel Macías
wrote:
> Zenny writes:
>
> > It still shows the problem with
> > glyphs:
> >
> > Should look like in the attached
> > screenshots, in emacs orgmode
> > and rendered to pdf (from org to
> > docx using pandoc)
>
> Add this line to the bottom:
>
> #+LaTeX_Header:\defaultfontfeatures{Renderer=HarfBuzz}
>
Appended the above line, but the rendering became much worse, see Ganapati
and BiSht lines:
Thanks.
--
Cheers,
/z
Re: Sanskrit/Devanagari fonts not exported to org-pdf output
On Fri, Sep 22, 2023 at 10:54 AM Juan Manuel Macías wrote: > Zenny writes: > > > > > > > > > > > With this both languages (scripts) were rendered) but both renderings > > has no correct glyphs (see screenshots) > > Could you please copy the text of your example here, so I can compile > it? > Here it comes: | Original | Anglicized | Switch | |--++| | सत्य | Satya | Sathya | | सरस्वती | Saraswati | Saraswathy | | गणपति | Ganapati | Ganapathy | | गोषाल | goShal | Ghoshal| | गोष्ठ | GoShTha| Ghosht | | मुम्बा | Mumba | Bombay | | घोष | GhoSha | Ghosh | | बिष्ट | BiSht | Bista | | अंग | Anga | Banga | Gosala Mankhya (घोषाला मंख्य in Sanskrit and ঘোষালা মঙ্গ্যায় in Bengali) -- 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
On Fri, Sep 22, 2023 at 10:49 AM Zenny wrote:
> On Fri, Sep 22, 2023 at 10:41 AM Juan Manuel Macías <
> maciasch...@posteo.net> wrote:
>
>> Zenny writes:
>>
>> > Also the Bengali letters were omitted with:
>>
>> Sorry, this is the correct MWE:
>>
>> #+LaTeX_Header: \usepackage[english]{babel}
>> #+LaTeX_Header: \usepackage{fontspec}
>> #+LaTeX_Header: \newfontscript{Devanagari}{deva}
>> #+LaTeX_Header: \babelprovide[onchar=ids fonts]{sanskrit-devanagari}
>> #+LaTeX_Header: \babelprovide[onchar=ids fonts]{sanskrit-bengali}
>> #+LaTeX_Header: \babelfont[sanskrit-devanagari]{rm}{Noto Sans Devanagari}
>> #+LaTeX_Header: \babelfont[sanskrit-bengali]{rm}{Noto Sans Bengali}
>>
>>
>>
>>
>>
>
> With this both languages (scripts) were rendered) but both renderings has
> no correct glyphs (see screenshots)
> Thanks!
>
Actually, the former should look like the latter, for a comparison.
> --
> 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 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
On Fri, Sep 22, 2023 at 10:41 AM Juan Manuel Macías
wrote:
> Zenny writes:
>
> > Also the Bengali letters were omitted with:
>
> Sorry, this is the correct MWE:
>
> #+LaTeX_Header: \usepackage[english]{babel}
> #+LaTeX_Header: \usepackage{fontspec}
> #+LaTeX_Header: \newfontscript{Devanagari}{deva}
> #+LaTeX_Header: \babelprovide[onchar=ids fonts]{sanskrit-devanagari}
> #+LaTeX_Header: \babelprovide[onchar=ids fonts]{sanskrit-bengali}
> #+LaTeX_Header: \babelfont[sanskrit-devanagari]{rm}{Noto Sans Devanagari}
> #+LaTeX_Header: \babelfont[sanskrit-bengali]{rm}{Noto Sans Bengali}
>
>
>
>
>
With this both languages (scripts) were rendered) but both renderings has
no correct glyphs (see screenshots)
Thanks!
--
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
On Fri, Sep 22, 2023 at 10:18 AM Juan Manuel Macías
wrote:
> Zenny writes:
>
> > Thanks, this was extremely helpful. The pdf is produced, but the
> > Devanagari glyphs were not respected. See screenshot.
>
> Could you please create this MWE, and execute the same process?
>
> #+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}
>
>
>
>
>
Thanks!
With above MWE, the org can directly be exported to pdf, but
1. Glyphs in Devanagari are not respected as earlier
2. Bengali is completely skipped.
--
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
On Fri, Sep 22, 2023 at 10:07 AM Zenny wrote: > > On Fri, Sep 22, 2023 at 10:00 AM Juan Manuel Macías < > maciasch...@posteo.net> wrote: > >> Zenny writes: >> >> > Exactly done as you advised, but no pdf is produced even after waiting >> > for ~10minutes (attached screenshot) >> >> Let's try the following: >> >> 1. Export your document to a 'your-document.tex' file: C-c C-e l l >> >> 2. Open a terminal in your directory and run: >> >> latexmk -f -pdf -lualatex -interaction=nonstopmode your-document.tex >> > > Thanks, this was extremely helpful. The pdf is produced, but the > Devanagari glyphs were not respected. See screenshot. > >> >> (a pdf would have to be created after compilation. If there are any >> errors, please copy your-document.log here). >> > > Also the Bengali letters were omitted with: > > Latexmk: Summary of warnings from last run of *latex: >> =Latex reported missing or unavailable character(s). >> =See log file for details. >> Latexmk: List of undefined refs and citations: >> Missing character: There is no ঘ (U+0998) in font >> [lmroman10-regular]:+tlig;!Missing character: There is no ো (U+09CB) in >> font [lmroman10-regular]:+tlig;!Missing character: There is no ষ (U+09B7) >> in font [lmroman10-regular]:+tlig;!Missing character: There is no া >> (U+09BE) in font [lmroman10-regular]:+tlig;!Missing character: There is no >> ল (U+09B2) in font [lmroman10-regular]:+tlig;!Missing character: There is >> no া (U+09BE) in font [lmroman10-regular]:+tlig;!Missing character: There >> is no ম (U+09AE) in font [lmroman10-regular]:+tlig;!Missing character: >> There is no ঙ (U+0999) in font [lmroman10-regular]:+tlig;!Missing >> character: There is no (U+09CD) in font [lmroman10-regular]:+tlig;!Missing >> character: There is no গ (U+0997) in font >> [lmroman10-regular]:+tlig;!Missing character: There is no (U+09CD) in font >> [lmroman10-regular]:+tlig;!Missing character: There is no য (U+09AF) in >> font [lmroman10-regular]:+tlig;!Missing character: There is no া (U+09BE) >> in font [lmroman10-regular]:+tlig;!Missing character: There is no য >> (U+09AF) in font [lmroman10-regular]:+tlig;!Missing character: There is no >> (U+09BC) in font [lmroman10-regular]:+tlig;!] [2] [3 >> Missing character: There is no ঘ (U+0998) in font >> [lmroman10-regular]:+tlig;!Missing character: There is no ো (U+09CB) in >> font [lmroman10-regular]:+tlig;!Missing character: There is no ষ (U+09B7) >> in font [lmroman10-regular]:+tlig;!Missing character: There is no প >> (U+09AA) in font [lmroman10-regular]:+tlig;!Missing character: There is no >> ত (U+09A4) in font [lmroman10-regular]:+tlig;!Missing character: There is >> no (U+09C1) in font [lmroman10-regular]:+tlig;!Missing character: There is >> no আ (U+0986) in font [lmroman10-regular]:+tlig;!Missing character: There >> is no ঘ (U+0998) in font [lmroman10-regular]:+tlig;!Missing character: >> There is no ো (U+09CB) in font [lmroman10-regular]:+tlig;!Missing >> character: There is no ষ (U+09B7) in font >> [lmroman10-regular]:+tlig;!Missing character: There is no প (U+09AA) in >> font [lmroman10-regular]:+tlig;!Missing character: There is no ত (U+09A4) >> in font [lmroman10-regular]:+tlig;!Missing character: There is no (U+09C1) >> in font [lmroman10-regular]:+tlig;!Missing character: There is no আ >> (U+0986) in font [lmroman10-regular]:+tlig;!] [4] [5] >> > The bengali is already installed by tlmgr: # tlmgr install bengali > tlmgr: package repository > https://ftpmirror1.infania.net/mirror/CTAN/systems/texlive/tlnet > (verified) > tlmgr install: package already present: bengali > > > > > >> Best regards, >> >> Juan Manuel >> >> > > -- > 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, an
Re: Sanskrit/Devanagari fonts not exported to org-pdf output
On Fri, Sep 22, 2023 at 10:00 AM Juan Manuel Macías wrote: > Zenny writes: > > > Exactly done as you advised, but no pdf is produced even after waiting > > for ~10minutes (attached screenshot) > > Let's try the following: > > 1. Export your document to a 'your-document.tex' file: C-c C-e l l > > 2. Open a terminal in your directory and run: > > latexmk -f -pdf -lualatex -interaction=nonstopmode your-document.tex > Thanks, this was extremely helpful. The pdf is produced, but the Devanagari glyphs were not respected. See screenshot. > > (a pdf would have to be created after compilation. If there are any > errors, please copy your-document.log here). > Also the Bengali letters were omitted with: Latexmk: Summary of warnings from last run of *latex: > =Latex reported missing or unavailable character(s). > =See log file for details. > Latexmk: List of undefined refs and citations: > Missing character: There is no ঘ (U+0998) in font > [lmroman10-regular]:+tlig;!Missing character: There is no ো (U+09CB) in > font [lmroman10-regular]:+tlig;!Missing character: There is no ষ (U+09B7) > in font [lmroman10-regular]:+tlig;!Missing character: There is no া > (U+09BE) in font [lmroman10-regular]:+tlig;!Missing character: There is no > ল (U+09B2) in font [lmroman10-regular]:+tlig;!Missing character: There is > no া (U+09BE) in font [lmroman10-regular]:+tlig;!Missing character: There > is no ম (U+09AE) in font [lmroman10-regular]:+tlig;!Missing character: > There is no ঙ (U+0999) in font [lmroman10-regular]:+tlig;!Missing > character: There is no (U+09CD) in font [lmroman10-regular]:+tlig;!Missing > character: There is no গ (U+0997) in font > [lmroman10-regular]:+tlig;!Missing character: There is no (U+09CD) in font > [lmroman10-regular]:+tlig;!Missing character: There is no য (U+09AF) in > font [lmroman10-regular]:+tlig;!Missing character: There is no া (U+09BE) > in font [lmroman10-regular]:+tlig;!Missing character: There is no য > (U+09AF) in font [lmroman10-regular]:+tlig;!Missing character: There is no > (U+09BC) in font [lmroman10-regular]:+tlig;!] [2] [3 > Missing character: There is no ঘ (U+0998) in font > [lmroman10-regular]:+tlig;!Missing character: There is no ো (U+09CB) in > font [lmroman10-regular]:+tlig;!Missing character: There is no ষ (U+09B7) > in font [lmroman10-regular]:+tlig;!Missing character: There is no প > (U+09AA) in font [lmroman10-regular]:+tlig;!Missing character: There is no > ত (U+09A4) in font [lmroman10-regular]:+tlig;!Missing character: There is > no (U+09C1) in font [lmroman10-regular]:+tlig;!Missing character: There is > no আ (U+0986) in font [lmroman10-regular]:+tlig;!Missing character: There > is no ঘ (U+0998) in font [lmroman10-regular]:+tlig;!Missing character: > There is no ো (U+09CB) in font [lmroman10-regular]:+tlig;!Missing > character: There is no ষ (U+09B7) in font > [lmroman10-regular]:+tlig;!Missing character: There is no প (U+09AA) in > font [lmroman10-regular]:+tlig;!Missing character: There is no ত (U+09A4) > in font [lmroman10-regular]:+tlig;!Missing character: There is no (U+09C1) > in font [lmroman10-regular]:+tlig;!Missing character: There is no আ > (U+0986) in font [lmroman10-regular]:+tlig;!] [4] [5] > > Best regards, > > Juan Manuel > > -- 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
On Thu, Sep 21, 2023 at 11:19 PM Juan Manuel Macías
wrote:
> 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)
>
Exactly done as you advised, but no pdf is produced even after waiting for
~10minutes (attached screenshot)
>
> 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")
>
Thanks for your input.
>
> 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: Sanskrit/Devanagari fonts not exported to org-pdf output
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
Re: Sanskrit/Devanagari fonts not exported to org-pdf output
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
content
Re: Sanskrit/Devanagari fonts not exported to org-pdf output
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
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: Sanskrit/Devanagari fonts not exported to org-pdf output
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.
-.. .. ... -.-. .-.. .- .. -- . .-. | -.. .. ... -.-. .-.. .- .. -- . .-.
Re: Sanskrit/Devanagari fonts not exported to org-pdf output
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.
-.. .. ... -.-. .-.. .- .. -- . .-. | -.. .. ... -.-. .-.. .- .. -- . .-.
Sanskrit/Devanagari fonts not exported to org-pdf output
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
Re: kaobook tex template integration to a org file to make self-contained, portable?
Aloha Tom, Thank you for taking time to respond with an useful pointer. I feel like I reached the right person who is an expert in both LaTeX and Orgmode who has contributed to org-tufte book earlier as seen in your github repo. I am a novice, fyi. I appreciate if you take some time to point out the non-standard features in order to make Orgmode can recognize. On Tue, Aug 8, 2023 at 10:06 PM Thomas S. Dye wrote: > Aloha Zenny, > > Zenny writes: > > > > However, the pdf did not inherit all the kaobook template > > features like: > > > > 1 Mini table of contents in the margin at the start of each > > chapter. > > 2 Chapter headings. > > 3 Huge chapter number with a vertical line > > The kaobook.cls defines non-standard LaTeX commands for some of > its features. Org mode doesn't know about these, so you'll have > to figure out how Org mode can recognize and export them. > > All the best, > Tom > -- > Thomas S. Dye > https://tsdye.online/tsdye > -- 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: kaobook tex template integration to a org file to make self-contained, portable?
Hi again,
I updated the texlive to 2023 and can produce a pdf with the following
snippets inside the https://github.com/asilata/emacsconf2021/ggm.org:
** Org LaTeX setup
> #+latex_class: kaobook
> #+latex_class_options: [openany, a5paper]
> #+latex_header:
> \usepackage{amsmath,amssymb,amsthm,geometry,hyperref,paralist,svg,thmtools,tikz,tikz-cd}
> #+latex_header: \usepackage{mathtools}
> #+latex_header: \usepackage[capitalise,noabbrev]{cleveref}
> #+latex_header: \usepackage{environ} \NewEnviron{abmn}{\marginnote{\BODY}}
> #+latex_header: \setcounter{tocdepth}{1}
> #+latex_header: \newtheorem{theorem}{Theorem}
> #+latex_header: \newtheorem{example}[theorem]{Example}
> #+latex_header: \newtheorem{exmpl}[theorem]{Example}
> #+latex_header: \newtheorem{definition}[theorem]{Definition}
> #+latex_header: \newtheorem{proposition}[theorem]{Proposition}
> #+latex_header: \newtheorem{lemma}[theorem]{Lemma}
> #+latex_header: \newtheorem{exercise}[theorem]{Exercise}
> #+latex_header: \usetikzlibrary{arrows,automata,positioning}
> ** Export settings
> Export into the artifacts directory
> #+export_file_name: artifacts/ggm
>
> Add ~kaobook~ to ~org-latex-classes~ and update ~org-latex-pdf-process~.
> #+name: export-setup
> #+begin_src emacs-lisp :results silent :var this-year="2023"
> (add-to-list 'org-latex-classes
>`("kaobook"
> ,(string-join
>'("\\documentclass{kaobook}"
> "\\usepackage{color}"
> "\\usepackage{amsmath,amssymb}")
>"\n")
> ("\\chapter{%s}" . "\\chapter*{%s}")
> ("\\section{%s}" . "\\section*{%s}")
> ("\\subsection{%s}" . "\\subsection*{%s}")
> ("\\paragraph{%s}" . "\\paragraph*{%s}")
> ("\\subparagraph{%s}" . "\\subparagraph*{%s}")))
>
However, the pdf did not inherit all the kaobook template features like:
1. Mini table of contents in the margin at the start of each chapter.
2. Chapter headings.
3. Huge chapter number with a vertical line
Any input will be appreciated to render the file that looks like
https://github.com/fmarotta/kaobook/blob/master/example_and_documentation.pdf
or https://github.com/tudelft3d/terrainbook/releases/latest.
Thank you in advance,
/z
On Mon, Aug 7, 2023 at 1:55 PM Christian Moe wrote:
>
>
> Hi,
>
> For starters, have you added the kaobook document class to the variable
> org-latex-classes? (If yes, ignore the rest of this message, if not, do
> so and see what happens.)
>
> This is needed to tell Org how to set the document class and what commands
> are used for sections. See the manual 13.10.2 and 13.10.3,
> [[info:org#LaTeX specific export settings]] and [[info:org#LaTeX header
> and sectioning]], and look up the docstring for org-latex-classes if you
> need help.
>
> E.g., in .emacs I have this for Tufte-Latex:
>
> (add-to-list 'org-latex-classes
> '("tufte-handout"
> "\\documentclass[11pt,a4paper]{tufte-handout}"
>("\\section{%s}" . "\\section*{%s}")
>("\\subsection{%s}" . "\\subsection*{%s}")))
>
> (add-to-list 'org-latex-classes
> '("tufte-book"
> "\\documentclass[11pt,a5paper,nols]{tufte-book}"
>("\\part{%s}" . "\\part*{%s}")
>("\\section{%s}" . "\\section*{%s}")
>("\\subsection{%s}" . "\\subsection*{%s}")
>("\\paragraph{%s}" . "\\paragraph*{%s}")))
>
> Yours,
> Christian
>
>
> Zenny writes:
>
> > Hi,
> >
> > References of interest:
> > 1. https://github.com/fmarotta/kaobook
> > 2. https://github.com/asilata/emacsconf2021
> >
> > Can anyone guide me how to get a self-contained and portable template
> that
> > executes kaobook tex templates (see 1) to create an org-file that
> resembles
> > with the instance in 2 above?
> >
> > I tried the best I can by adding the kaobook.cls and kaobook.sty files
> > inside `~/texmf/tex/latex/kaobook/` folder and specified 'kaobook' in the
> > `#+latex_class: kaobook` but it failed to produce the desired look of pdf
> > similar to
> >
> https://github.com/fmarotta/kaobook/blob/master/example_and_documentation.pdf
> > withing the same examples directory!
> >
> > Any input appreciated!
> >
> > Cheers and have a nice week,
> > /z
>
>
Re: kaobook tex template integration to a org file to make self-contained, portable?
Thanks Christian for the pointer,
But I already have,
(add-to-list 'org-latex-classes
>`("kaobook"
> ,(string-join
>'("\\documentclass{kaobook}"
> "\\usepackage{color}"
> "\\usepackage{amsmath,amssymb}")
>"\n")
> ("\\chapter{%s}" . "\\chapter*{%s}")
> ("\\section{%s}" . "\\section*{%s}")
> ("\\subsection{%s}" . "\\subsection*{%s}")
> ("\\paragraph{%s}" . "\\paragraph*{%s}")
> ("\\subparagraph{%s}" . "\\subparagraph*{%s}")))
>
yet `C-c C-e l o` fails to produce pdf.
Cheers,
On Mon, Aug 7, 2023 at 1:55 PM Christian Moe wrote:
>
>
> Hi,
>
> For starters, have you added the kaobook document class to the variable
> org-latex-classes? (If yes, ignore the rest of this message, if not, do
> so and see what happens.)
>
> This is needed to tell Org how to set the document class and what commands
> are used for sections. See the manual 13.10.2 and 13.10.3,
> [[info:org#LaTeX specific export settings]] and [[info:org#LaTeX header
> and sectioning]], and look up the docstring for org-latex-classes if you
> need help.
>
> E.g., in .emacs I have this for Tufte-Latex:
>
> (add-to-list 'org-latex-classes
> '("tufte-handout"
> "\\documentclass[11pt,a4paper]{tufte-handout}"
>("\\section{%s}" . "\\section*{%s}")
>("\\subsection{%s}" . "\\subsection*{%s}")))
>
> (add-to-list 'org-latex-classes
> '("tufte-book"
> "\\documentclass[11pt,a5paper,nols]{tufte-book}"
>("\\part{%s}" . "\\part*{%s}")
>("\\section{%s}" . "\\section*{%s}")
>("\\subsection{%s}" . "\\subsection*{%s}")
>("\\paragraph{%s}" . "\\paragraph*{%s}")))
>
> Yours,
> Christian
>
>
> Zenny writes:
>
> > Hi,
> >
> > References of interest:
> > 1. https://github.com/fmarotta/kaobook
> > 2. https://github.com/asilata/emacsconf2021
> >
> > Can anyone guide me how to get a self-contained and portable template
> that
> > executes kaobook tex templates (see 1) to create an org-file that
> resembles
> > with the instance in 2 above?
> >
> > I tried the best I can by adding the kaobook.cls and kaobook.sty files
> > inside `~/texmf/tex/latex/kaobook/` folder and specified 'kaobook' in the
> > `#+latex_class: kaobook` but it failed to produce the desired look of pdf
> > similar to
> >
> https://github.com/fmarotta/kaobook/blob/master/example_and_documentation.pdf
> > withing the same examples directory!
> >
> > Any input appreciated!
> >
> > Cheers and have a nice week,
> > /z
>
>
--
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.
-.. .. ... -.-. .-.. .- .. -- . .-. | -.. .. ... -.-. .-.. .- .. -- . .-.
kaobook tex template integration to a org file to make self-contained, portable?
Hi, References of interest: 1. https://github.com/fmarotta/kaobook 2. https://github.com/asilata/emacsconf2021 Can anyone guide me how to get a self-contained and portable template that executes kaobook tex templates (see 1) to create an org-file that resembles with the instance in 2 above? I tried the best I can by adding the kaobook.cls and kaobook.sty files inside `~/texmf/tex/latex/kaobook/` folder and specified 'kaobook' in the `#+latex_class: kaobook` but it failed to produce the desired look of pdf similar to https://github.com/fmarotta/kaobook/blob/master/example_and_documentation.pdf withing the same examples directory! Any input appreciated! Cheers and have a nice week, /z
