From: "Pedro P. Palazzo" <pedro.palazzo-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: How to use scholarly-metadata.lua
Date: Wed, 2 Mar 2022 09:01:34 -0800 (PST) [thread overview]
Message-ID: <71489ba0-7c6f-49b3-9f69-30fee6dd55e0n@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1923 bytes --]
Hi, I am trying out the scholarly-metadata and author-info-blocks filters
(just downloaded the latest release) with pandoc 2.17.1.1 and am getting
the following error:
Error running filter
/Users/palazzo/.local/share/pandoc/filters/scholarly-metadata.lua:
...lazzo/.local/share/pandoc/filters/scholarly-metadata.lua:95: not a named
object: List: 0x600002684b00
stack traceback:
...lazzo/.local/share/pandoc/filters/scholarly-metadata.lua:95: in
function 'to_named_object'
[C]: in function 'pandoc.List.map'
...lazzo/.local/share/pandoc/filters/scholarly-metadata.lua:144: in
upvalue 'canonicalize'
...lazzo/.local/share/pandoc/filters/scholarly-metadata.lua:181: in
function <...lazzo/.local/share/pandoc/filters/scholarly-metadata.lua:180>
[Process exited 83]
My YAML header looks like this:
---
title: "Some title"
author:
- Rui Florentino:
correspondence: "yes"
email: some-zuv13RyHHZkAvxtiuMwx3w@public.gmane.org
institute: upt
- Pedro P. Palazzo:
correspondence: "yes"
email: another-zuv13RyHHZkAvxtiuMwx3w@public.gmane.org
institute: unb
institute:
- upt: Professor e investigador da Universidade Portucalense,
Departamento de Arquitetura e Multimédia
- unb: Professor Associado, Universidade de Brasília, Faculdade de
Arquitetura e Urbanismo.
---
I even tried copying and pasting the example YAML data that is on the
filters’ README and still get the same error.
--
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/71489ba0-7c6f-49b3-9f69-30fee6dd55e0n%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 2525 bytes --]
next reply other threads:[~2022-03-02 17:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-02 17:01 Pedro P. Palazzo [this message]
[not found] ` <71489ba0-7c6f-49b3-9f69-30fee6dd55e0n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-03-03 16:29 ` Albert Krewinkel
[not found] ` <8735jzj8nu.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2022-03-03 17:08 ` Pedro P. Palazzo
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=71489ba0-7c6f-49b3-9f69-30fee6dd55e0n@googlegroups.com \
--to=pedro.palazzo-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).