From: Martin Hepp <mfhepp-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Naming Conventions for Class and Attribute Names?
Date: Tue, 23 Nov 2021 17:35:10 +0100 [thread overview]
Message-ID: <0B37EABB-86C6-40D1-BCD8-4FFDC4B5EDE3@gmail.com> (raw)
Hi all,
for a set of filters, I would like to define a hierarchical naming scheme for metadata classes and attributes. For instance, I would like do define a class
.slides.beamer
an use it like so
:::{.slides.beamer}
blabla
:::
Or attributes that a filter can use to adjust picture formatting details by output format, like
![](image.png){width=90%, eisvogel.width=50%}
The issue in here is not the filter (which would adjust the width) but whether it is possible and recommended to use dots within class and attribute names in Pandoc element meta-data. CamelCase would not be as nice; other delimiters (:, /, _, -) would work for me, but a dot would be preferred.
I could not find the respective information in the documentation.
Thanks!
Best wishes
Martin
--
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/0B37EABB-86C6-40D1-BCD8-4FFDC4B5EDE3%40gmail.com.
next reply other threads:[~2021-11-23 16:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-23 16:35 Martin Hepp [this message]
[not found] ` <0B37EABB-86C6-40D1-BCD8-4FFDC4B5EDE3-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2021-11-23 16:38 ` Gwern Branwen
[not found] ` <CAMwO0gyhdaJgmSFtBn4RrsRNXMH_Leho508tBcM-BS2LfsFiBg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2021-11-24 18:28 ` Martin Hepp
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=0B37EABB-86C6-40D1-BCD8-4FFDC4B5EDE3@gmail.com \
--to=mfhepp-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).