public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: name name <ivan20151013-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: The names of the default CSS styles
Date: Fri, 26 Aug 2022 23:56:45 -0700 (PDT)	[thread overview]
Message-ID: <ce4037fa-b4cd-4266-a036-a91b8fcb45b0n@googlegroups.com> (raw)


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

If I convert the following snippet, with the `--standalone` option, from 
Markdown to HTML,

~~~~
~~~ {.language .numberLines startFrom=100}
fenced code block line 100
fenced code block line 101
~~~
~~~~

... the resulting HTML will contain a list of styles included by Pandoc by 
default.

Does anybody know why those styles named so differently, inconsistently? 
See the excertp below: alllowercase for small caps, lowercase-with-hyphens 
for divs with the hanging indent, and camelCase for source code blocks.

~~~
span.smallcaps{font-variant: small-caps;}
div.hanging-indent{margin-left: 1.5em; text-indent: -1.5em;}
pre.sourceCode { margin: 0; }
~~~

What is the logic there?

-- 
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/ce4037fa-b4cd-4266-a036-a91b8fcb45b0n%40googlegroups.com.

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

             reply	other threads:[~2022-08-27  6:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-27  6:56 name name [this message]
     [not found] ` <ce4037fa-b4cd-4266-a036-a91b8fcb45b0n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-08-27 10:39   ` Albert Krewinkel
     [not found]     ` <93D9EB82-B83A-4DE1-AEF8-70FC1BB137A8-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2022-08-27 18:13       ` John MacFarlane

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=ce4037fa-b4cd-4266-a036-a91b8fcb45b0n@googlegroups.com \
    --to=ivan20151013-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).