public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: "R (Chandra) Chandrasekhar"
	<chyavana-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	pandoc-discuss
	<pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Possible bugs in the markdown to PDF via lualatex conversion process for bilingual documents
Date: Tue, 08 Feb 2022 13:34:13 -0800	[thread overview]
Message-ID: <yh480kbkzhm4a2.fsf@johnmacfarlane.net> (raw)
In-Reply-To: <b865ce6f-aa23-a1f0-b5f7-35601791d215-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>


Let us know what version of pandoc you're using.
There have been extensive changes recently that might be
relevant (we no longer use polyglossia, but of course
it's possible that something relating to our old polyglossia
support was left in the template...).

"R (Chandra) Chandrasekhar" <chyavana-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:

> I am writing a bilingual test file for English and Tamil in the same 
> markdown document to yield a PDF via lualatex and babel. The file, which 
> correctly gives HTML and epub outputs,  is:
>
> ```
> ---
> title: "Bilingual Test for LuaLaTeX and Babel: English and Tamil"
> lang: en-GB
> ---
>
> This is English.
>
> {\sffamily This is also English.}
>
> இது தமிழ்.
>
> {\sffamily இதுவும் தமிழ்.}
>
> :::{lang=ta}
> இது கூட தமிழ் தான்.
> :::
>
> Back to English and EOF.
> ```
>
> The included `babel-in-header.tex` file is:
>
> ```
> % babel-in-header.textsf
> \babelfont{rm}[Scale=1.0,Language=Default,BoldFont={* SemiBold}]{Noto Serif}
> \babelfont{sf}[Language=Default,BoldFont={* SemiBold}]{Noto Sans}
> \babelfont[tamil]{rm}[Language=Default]{Noto Serif Tamil}
> \babelfont[tamil]{sf}[Language=Default]{Noto Sans Tamil}
> \babelprovide[import,onchar=ids fonts]{tamil}
> \defaultfontfeatures{Scale=MatchLowercase,Ligatures=TeX,Renderer=HarfBuzz}
> \thispagestyle{empty}
> ```
>
> The compilation command is:
>
> pandoc --from markdown --to latex --include-in-header 
> babel-in-header.tex --standalone --output en-ta-test.tex en-ta-test.md
>
> I find that the generated .tex file cannot be compiled to PDF because 
> there appear to be two errors, which might be bugs:
>
> 1. The \babelfont commands appear _before_ the \usepackage{babel} 
> invocation in the .tex file because of a commented requirement for 
> polyglossia, which I am not using. As a result, I get an
>
> ```
> ! Undefined control sequence.
> l.59 \babelfont
>               {rm}[Scale=1.0,Language=Default,BoldFont={* 
> SemiBold}]{Noto Serif}
> ```
>
> error with lualatex.
>
> 2. If I manually transpose the \babelfont commands inserted by the 
> `babel-in-header.tex` file to appear _after_ the babel invocation but 
> before \title in the .tex file, I get this error:
>
> ```
> ! Package babel Error: Unknown option 'tamil'. Either you misspelled it
> (babel)                or the language definition file tamil.ldf was not 
> found.
>
>
> See the babel package documentation for explanation.
> ```
>
> 3. If I remove `tamil,` from the babel invocation,
>
> ```
> \usepackage[tamil,main=british]{babel}
> ```
>
> I am able to compile with lualatex, using the same command as before, 
> and get the expected PDF, as shown in the attached screenshot.
>
> I realize that both pandoc and the babel package are under development, 
> and are therefore moving targets.
>
> Nevertheless, I believe these are bugs in the markdown to latex 
> conversion process and point them out so that they may be corrected or 
> circumvented, automatically rather than manually, from the pandoc end.
>
> Thanks.
>
> 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/b865ce6f-aa23-a1f0-b5f7-35601791d215%40gmail.com.

-- 
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/yh480kbkzhm4a2.fsf%40johnmacfarlane.net.


  parent reply	other threads:[~2022-02-08 21:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-08  8:42 R (Chandra) Chandrasekhar
     [not found] ` <b865ce6f-aa23-a1f0-b5f7-35601791d215-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2022-02-08 21:34   ` John MacFarlane [this message]
     [not found]     ` <yh480kbkzhm4a2.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2023-02-09 17:27       ` Clément Aubert
     [not found]         ` <017f0e7b-dd57-452b-95b4-f89c655d39ben-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-02-09 17:55           ` Clément Aubert

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=yh480kbkzhm4a2.fsf@johnmacfarlane.net \
    --to=jgm-tvlzxgkolnx2fbvcvol8/a@public.gmane.org \
    --cc=chyavana-Re5JQEeQqe8AvxtiuMwx3w@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).