Re: Lua filter reading data from metadata or defaults file

["krulis....-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org" <krulis.tomas.tk-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>]

[-- Attachment #1.1: Type: text/plain, Size: 2644 bytes --]

Those are good news!

But my question might have been a little confusing.
As a follow-up, how can load and access data provided in arbitraty yaml or 
json file with lua filter? Is there any helper function for that, or I 
should just use simple `open` or something ... ?
I am looking at lua filters part in pandoc docs; example: "Replacing 
placeholders with their metadata value;" which kinda similar to my case, 
but here are just flat values. I would like to specify a filepath to yaml 
file with actual definitions. 

Dne pátek 25. září 2020 v 12:06:24 UTC+2 uživatel Albert Krewinkel napsal:

> You should be able to access `mustache` as a normal metadata field if it
> is nested under the field `metadata` in defaults.yaml:
>
> ---
> metadata:
> mustache: ./src/varDefinitions.yaml
> ---
>
>
> krulis....-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org writes:
>
> > I would like to ask, whether it is possible for a lua filter to read data
> > from metadata block (or metadata file) or from defaults file? I looked
> > around website documentation, also into `lua filter repository`, but 
> found
> > no filter accessing metadata values in `defaults file` fields.
> > I am working on a custom lua filter, for which I want to specify a 
> metadata
> > field, which would point to external file with required definitions, very
> > similar to python filter `pandoc-mustache` github source here :
> > <
> https://github.com/michaelstepner/pandoc-mustache/blob/master/pandoc_mustache/pandoc_mustache.py
> >
> >
> > `defaults.yaml`:
> >
> > ```
> > ...
> >
> > mustache:
> > - ./src/varDefinitions.yaml
> >
> > ...
> > ```
> >
> > *Motivation:* Plans for this filter are to provide functionalities of 
> LaTeX
> > `glossaries` package to `pandoc`. There are already some filters, which
> > take theyre own approach to the issue, but none of them gives full 
> acronym
> > support specific to given format.
> > Long-term plans would be to also provide support for term definitions in
> > `glossaries`-like style.
> >
> > Thanks for any guidance in this issue.
> > Regards, Tomas
>
>
> --
> 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/9dbbc23d-1cde-4c0b-898a-ecbe4679d614n%40googlegroups.com.

[-- Attachment #1.2: Type: text/html, Size: 3809 bytes --]