public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: John MacFarlane <fiddlosopher-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Fun with 'pandoc lua'
Date: Fri, 20 Jan 2023 10:04:45 -0800	[thread overview]
Message-ID: <6C24F328-997C-4853-880B-244E701F222F@gmail.com> (raw)
In-Reply-To: <EF2D1F45-A155-4DA5-9C4B-12D21F46B6D8-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>

OK, now I see that in runPandocWithLua we simply carry over the common state that had already been established.  So that's why we don't get this message in normal conversions -- but we get it when we run the lua engine without going through convertWithOpts, which sets up common state for us.

Albert, how about exporting configureCommonState from T.P.App and then using it to configure the common state when pandoc is used as a Lua interpreter?  (I guess this would be in runLuaInterpreter in pandoc-cli.)

> On Jan 19, 2023, at 4:45 PM, John MacFarlane <fiddlosopher-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> 
> I think I see what is happening. HTML writer has:
> 
>  abstractTitle <- translateTerm Abstract
> 
> And apparently the term isn’t defined. Why not?  Well, normally it would be defined by configureCommonState, whic his run at the beginning of convertWithOpts’. This sets the user data directory, tracing options, verbosity, the resource path, the input and output file variables, request headers, and translations (based on `lang` in metadata).
> 
> I’m not sure how we should deal with this is a Lua context.  Perhaps Lua initialization should include running configureCommonState?  There seems to be no way to load the translations manually from Lua.
> 
> 
> 
>> On Jan 19, 2023, at 10:08 AM, Albert Krewinkel <albert+pandoc@zeitkraut.de> wrote:
>> 
>> 
>> John MacFarlane <fiddlosopher-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
>> 
>>> Pandoc 3.0 can be used as a lua interpreter, with full access to the Lua API:
>>> 
>>> $ cat test.lua
>>> local formats = {"latex", "html5", "docbook", "ms"}
>>> local doc = (pandoc.read("> *hello* world!", "markdown"))
>>> for _,format in ipairs(formats) do
>>> print(string.format("%s:\n%s\n\n", format, pandoc.write(doc, format)))
>>> end
>>> 
>>> [...]
>>> 
>>> latex:
>>> [WARNING] The term Abstract has no translation defined.
>>> 
>>> Albert: do you know why we get that warning?
>> 
>> No clue, sorry
>> 
>> 
>> -- 
>> Albert Krewinkel
>> GPG: 8eed e3e2 e8c5 6f18 81fe  e836 388d c0b2 1f63 1124
>> 
>> -- 
>> 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/875yd2mm3i.fsf%40zeitkraut.de.
> 

-- 
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/6C24F328-997C-4853-880B-244E701F222F%40gmail.com.


      parent reply	other threads:[~2023-01-20 18:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-19 17:25 John MacFarlane
     [not found] ` <208248AE-608E-4E19-AA46-C902BE91FBE9-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2023-01-19 18:08   ` Albert Krewinkel
     [not found]     ` <875yd2mm3i.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2023-01-20  0:45       ` John MacFarlane
     [not found]         ` <EF2D1F45-A155-4DA5-9C4B-12D21F46B6D8-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2023-01-20 18:04           ` John MacFarlane [this message]

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=6C24F328-997C-4853-880B-244E701F222F@gmail.com \
    --to=fiddlosopher-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).