From: Zenny <garbytrash@gmail.com>
To: "Juan Manuel Macías" <maciaschain@posteo.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: Sanskrit/Devanagari fonts not exported to org-pdf output
Date: Thu, 21 Sep 2023 19:53:02 +0200 [thread overview]
Message-ID: <CACuV5sCNJgzauu208W+QVdvgBTbVaWa9N4K+t9hFCgkkh+qGwQ@mail.gmail.com> (raw)
In-Reply-To: <87wmwjpmls.fsf@posteo.net>
[-- Attachment #1: Type: text/plain, Size: 4828 bytes --]
Hi Juan,
On Thu, Sep 21, 2023 at 5:33 PM Juan Manuel Macías <maciaschain@posteo.net>
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<lang>{text}, where <lang> is the
> secondary language. In babel you have the command
> \foreignlanguage{<lang>}{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 <return> 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.fsf@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.
-.. .. ... -.-. .-.. .- .. -- . .-. | -.. .. ... -.-. .-.. .- .. -- . .-.
[-- Attachment #2: Type: text/html, Size: 6485 bytes --]
next prev parent reply other threads:[~2023-09-21 17:54 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-21 7:46 Sanskrit/Devanagari fonts not exported to org-pdf output Zenny
2023-09-21 8:24 ` Juan Manuel Macías
2023-09-21 13:46 ` Zenny
2023-09-21 15:33 ` Juan Manuel Macías
2023-09-21 17:53 ` Zenny [this message]
2023-09-21 18:28 ` Juan Manuel Macías
2023-09-21 18:44 ` Zenny
2023-09-21 19:32 ` Juan Manuel Macías
2023-09-21 20:26 ` Zenny
2023-09-21 20:39 ` Zenny
2023-09-21 20:41 ` Zenny
2023-09-21 21:19 ` Juan Manuel Macías
2023-09-22 7:04 ` Zenny
2023-09-22 8:00 ` Juan Manuel Macías
2023-09-22 8:07 ` Zenny
2023-09-22 8:09 ` Zenny
2023-09-22 8:41 ` Juan Manuel Macías
2023-09-22 8:49 ` Zenny
2023-09-22 8:54 ` Zenny
2023-09-22 8:54 ` Juan Manuel Macías
2023-09-22 8:58 ` Zenny
2023-09-22 9:06 ` Juan Manuel Macías
2023-09-22 9:37 ` Zenny
2023-09-22 10:02 ` Juan Manuel Macías
2023-09-22 12:59 ` Zenny
2023-09-22 15:12 ` Juan Manuel Macías
2023-09-22 17:51 ` Zenny
2023-09-22 8:18 ` Juan Manuel Macías
2023-09-22 8:30 ` Zenny
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CACuV5sCNJgzauu208W+QVdvgBTbVaWa9N4K+t9hFCgkkh+qGwQ@mail.gmail.com \
--to=garbytrash@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=maciaschain@posteo.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).