From: <tomas@tuxteam.de>
To: emacs-orgmode@gnu.org
Subject: Re: LaTeX export for Org Mode Documents written in Indic Languages
Date: Sat, 7 Jan 2023 10:33:21 +0100 [thread overview]
Message-ID: <Y7k8YY1C7QWdP4F2@tuxteam.de> (raw)
In-Reply-To: <87358mx1hw.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1336 bytes --]
On Sat, Jan 07, 2023 at 12:41:39PM +0530, Krishna Jani wrote:
>
> Hello,
>
> I have never had to write in languages other than English but an
> assignment just came up to transcribe the Indian Penal Code in
> simple and understandable Hindi. I have an Org file with some of my
> transcriptions (because of Emacs's awesome language support) but I am
> unable to org-export these files to pdf. I suppose I must install some
> latex packages, but I have not been able to find any documentation for
> the same. I dont really know latex, I mainly just use it for Org pdf
> export.
>
> Has anyone had a similar experience, or has a clue to this problem. Is
> there some documentation relating to languages that I can read
There are some approaches described here:
https://tex.stackexchange.com/questions/199773/how-to-type-hindi-words-in-latex
Since your input will be most probably already UTF-8 encoding, I
guess the most promising avenue these days is to go with LuaLaTeX.
It should work as a drop-in replacement for LaTeX "classic" and
should be included in your favourite TeX distribution.
I don't know off-the-bat what to do to make it work with Org
(I'm sure there are folks around here who do :), I'd first
export to LaTeX and fiddle with the preamble until I know what
to do.
Cheers
--
t
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2023-01-07 9:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-07 7:11 LaTeX export for Org Mode Documents written in Indic Languages Krishna Jani
2023-01-07 7:47 ` Alain.Cochard
2023-01-07 9:33 ` tomas [this message]
2023-01-07 10:09 ` Vikas Rawal
2023-01-07 11:36 ` Ihor Radchenko
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=Y7k8YY1C7QWdP4F2@tuxteam.de \
--to=tomas@tuxteam.de \
--cc=emacs-orgmode@gnu.org \
/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).