From: Christophe Demko <chdemko-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Announcing the pandoc acronym filter
Date: Wed, 1 Apr 2020 01:24:28 -0700 (PDT) [thread overview]
Message-ID: <e29c102d-3612-4e6c-8fbc-687bd07ee864@googlegroups.com> (raw)
In-Reply-To: <DBA1070B-849F-45B3-81CA-ECA9100C32F9-RoXCvvDuEio@public.gmane.org>
[-- Attachment #1.1: Type: text/plain, Size: 1989 bytes --]
This is a useful filter.
But you could use the pandoc metadata to define your acronyms instead of an
external file:
---
pandoc-acronyms: aba: shortform: ABA
longform": a better acronym
bba:
shortform: BBA
longform: beer brewing attitude
...
See https://pandoc.org/MANUAL.html#extension-yaml_metadata_block
Le jeudi 6 février 2020 12:47:22 UTC+1, Mirko Boehm a écrit :
>
> Hello there,
>
> for a recent article I needed a way to automatically expand acronyms on
> the first use. Since there was not a good solution for it, I implemented a
> pandoc filter that does the trick. You can find it here:
> https://gitlab.com/mirkoboehm/pandoc-acronyms It is distributed via pip:
> https://pypi.org/project/pandoc-acronyms/ Once installed, it runs as a
> stand-alone program in the usual pandoc filter way.
>
> Can I ask for some feedback? There are a couple of things to discuss:
>
> - The syntax: Acronyms are marked like this: [!bba]. Does that clash
> with other naming schemes? It it sound?
> - I would like to add a feature to generate an acronym index at a
> marked location in the document. What would be the best way to do that?
>
>
> To suggest improvements, feel free to add them as issues to the Gitlab
> project so that they don’t get lost in the discussion thread.
>
> Best,
>
> Mirko.
> --
> Mirko Boehm | mi...-RoXCvvDuEio@public.gmane.org <javascript:> | KDE e.V.
> Qt Certified Specialist and Trainer
> Request a meeting: https://doodle.com/mirkoboehm
>
>
--
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/e29c102d-3612-4e6c-8fbc-687bd07ee864%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 6845 bytes --]
next prev parent reply other threads:[~2020-04-01 8:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-06 11:47 Mirko Boehm (KDE)
[not found] ` <DBA1070B-849F-45B3-81CA-ECA9100C32F9-RoXCvvDuEio@public.gmane.org>
2020-02-06 17:04 ` Benct Philip Jonsson
[not found] ` <afbd510c-bccb-07d1-6c90-e141563c87b6-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2020-02-07 10:19 ` Mirko Boehm
[not found] ` <4e94a11f-3e3d-4ebb-b047-94e61110fd98-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-02-07 18:34 ` BPJ
2020-02-06 21:33 ` Albert Krewinkel
[not found] ` <87eev7h04j.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2020-02-07 10:37 ` Mirko Boehm
2020-02-07 10:48 ` Patrick Hilhorst
[not found] ` <795bf987-c198-4723-b1f0-16711603632b-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-02-07 11:29 ` Mirko Boehm (KDE)
2020-02-07 16:03 ` Corentin Dupont
[not found] ` <CAEyhvmqkmZs7k=_Y=rv+vFSHNiVhjRYgvuOG4Y7ZocqcgpaGmQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2020-02-24 12:11 ` Mirko Boehm
[not found] ` <cea0c10c-1cfb-40d7-a464-cee190c69caa-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-03-29 18:13 ` Gwern Branwen
[not found] ` <CAMwO0gxXn=DNtuJ+R8CUOonHzGgArizwWq-KuC9BBEPucE5yBQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2020-03-29 20:57 ` Gwern Branwen
2020-04-01 8:24 ` Christophe Demko [this message]
[not found] ` <e29c102d-3612-4e6c-8fbc-687bd07ee864-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-04-02 10:21 ` Mirko Boehm
[not found] ` <8A6899E5-8D6C-4C13-BE3B-E0DF09876F50-RoXCvvDuEio@public.gmane.org>
2020-04-02 17:38 ` John MacFarlane
2020-04-02 19:02 ` Christophe Demko
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=e29c102d-3612-4e6c-8fbc-687bd07ee864@googlegroups.com \
--to=chdemko-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).