From: "R (Chandra) Chandrasekhar" <chyavana-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org,
denis.maier-NSENcxR/0n0@public.gmane.org
Subject: Re: AW: Problem with `selnolig` package and multi-lingual documents
Date: Sun, 5 Jun 2022 01:18:51 +0530 [thread overview]
Message-ID: <877d4d71-e0a3-6afe-0f94-44a12b644636@gmail.com> (raw)
In-Reply-To: <0bb0992b678d4c66a1b088568c3858c9-NSENcxR/0n0@public.gmane.org>
I get this warning when the .tex file generated by pandoc from .md is
compiled by lualatex:
------
warning (ligkern): error:
...xlive/2022/texmf-dist/tex/lualatex/selnolig/selno
lig.lua:134: bad argument #1 to 'char' (invalid value)
.
<recently read> \endtemplate
l.760 \textsc{Word} &
\textsc{Meaning} \\
-----
An MWE would take more time to generate. I suspect that it happens with
Romanized Sanskrit below the table headings shown above. It probably has
to do with diacritics for Latin letters in a "kernable" combination.
I will post it when I isolate the text that causes the problem
repeatably. I will also post it at TSE as you have suggested.
Chandra
On 05/06/2022 00:25, denis.maier-NSENcxR/0n0@public.gmane.org wrote:
> Would be good to know the warning, and to have a mwe. Actually, if that package is to blame maybe open an issue there?
>
>
>
> ________________________________________
> Von: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> im Auftrag von R (Chandra) Chandrasekhar <chyavana-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> Gesendet: Samstag, 4. Juni 2022 20:27:44
> An: pandoc-discuss
> Betreff: Problem with `selnolig` package and multi-lingual documents
>
> I am working on a multi-lingual document (English, Tamil, Sanskrit,
> Romanized Sanskrit, Greek). I have used pandoc to compile the source
> document perfectly into HTML, ePuB, and PDF via LuaLaTeX, until
> recently, when TeXLive 2022 was released.
>
> The generation of the HTML, epUb and .tex files now proceeds without
> trouble. But compilation of the .tex file with lualatex produces a
> warning, and further forced compilation generates a truncated PDF file.
>
> The operational error message singled out the package `selnolig`. I
> identified the following three lines in the default latex template and
> commented them out:
>
> ```
> \ifLuaTeX
> \usepackage{selnolig} % disable illegal ligatures
> \fi
> ```
>
> The document then compiles error-free.
>
> I can modify the default template with every release to comment out
> these three lines, as I see no use for `selnolig` for my use case. The
> question is can this package be made optional, since it causes aborted
> compilation with multilingual documents.
>
> Thank you.
>
> Chandra
>
> --
> You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/fddd8e92-b419-1efd-d57d-909f04cdd214%40gmail.com.
>
next prev parent reply other threads:[~2022-06-04 19:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-04 18:27 R (Chandra) Chandrasekhar
[not found] ` <fddd8e92-b419-1efd-d57d-909f04cdd214-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2022-06-04 18:55 ` AW: " denis.maier-NSENcxR/0n0
[not found] ` <0bb0992b678d4c66a1b088568c3858c9-NSENcxR/0n0@public.gmane.org>
2022-06-04 19:48 ` R (Chandra) Chandrasekhar [this message]
[not found] ` <877d4d71-e0a3-6afe-0f94-44a12b644636-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2022-06-05 11:15 ` R (Chandra) Chandrasekhar
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877d4d71-e0a3-6afe-0f94-44a12b644636@gmail.com \
--to=chyavana-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=denis.maier-NSENcxR/0n0@public.gmane.org \
--cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.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.
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 NNTP newsgroup(s).