From: Scott Koga-Browes <kogabrowes-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: 'pandoc-abbreviations' python filter: request for advice/guidance
Date: Tue, 13 Dec 2016 00:41:33 -0800 (PST) [thread overview]
Message-ID: <58db4764-ca7b-4f84-893a-6d6f3260fe47@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1631 bytes --]
I have created a python filter which replaces user-definable abbreviations
(stored in a dictionary file and/or in a pandoc markdown source document's
metadata) with their expansions. This is my attempt to replicate the kind
of possibilities offered by LaTeX macros like \newcommand{\osh}{oshigami},
i.e. write '\osh', get 'oshigami' when the document is processed. In the
past I've found this very useful for maintaining consistency throughout a
document, and I missed this when I moved to writing in markdown.
I'm not really a programmer but - based on what I could understand from
looking at other python filters out there - I managed to slap together
something which seems to do what I want it to. However, I'm not really
competent to judge whether it's fit for 'general consumption' and I am
hoping there might be people out there willing to spend a few minutes to
take a look at it and advise me on what needs to be done to make it
'roadworthy'.
This is the repository: https://github.com/scokobro/pandoc-abbreviations
Thanks in advance!
--
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 post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/58db4764-ca7b-4f84-893a-6d6f3260fe47%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[-- Attachment #1.2: Type: text/html, Size: 3221 bytes --]
next reply other threads:[~2016-12-13 8:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-13 8:41 Scott Koga-Browes [this message]
[not found] ` <58db4764-ca7b-4f84-893a-6d6f3260fe47-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2016-12-13 21:21 ` Sergio Correia
[not found] ` <5c74ed41-79f3-4566-9616-10b2e1224102-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2016-12-14 1:07 ` Scott Koga-Browes
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=58db4764-ca7b-4f84-893a-6d6f3260fe47@googlegroups.com \
--to=kogabrowes-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).