public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Mats Holmberg <elmatzo-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Selecting CSS style for paragraph
Date: Sat, 17 Jun 2023 13:47:12 -0700 (PDT)	[thread overview]
Message-ID: <0102580d-3f9a-407d-b089-54a8b51ab6f3n@googlegroups.com> (raw)


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

Hi all,

I am trying to learn how to use pandoc and markdown for book writing 
(creating epubs and html books). Overall it works splendidly, but I have a 
problem that I don't know how
to solve: hinting to pandoc which CSS style to use for my paragraph.
.
I know that i can simply wrap my text in a html block e.g.  <p 
class="no-indent">Text</p>.
But then I can't use markdown in the html block. Some other markdown 
parsers I have
tested (MarkDiv, for example) have a syntax that goes something like this 
instead:
{.no-indent}Text, which seems to work perfectly. I have tried the syntax 
::::{.no-indent} in pandoc, but that generates a <div> around the whole 
thing which is not what i want.

I have tried to go through all the extensions that are available in pandoc, 
but so far haven't found anything that works.

I guess this might be kind of a noob question, but I have really tried to 
find a solution
and failed. Is this a real problem, or am I overlooking something simple? 
Some 
combination of pandoc extensions or something like that? Any help will be 
immensely 
appreciated!

Kind regards,
Mats

-- 
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/0102580d-3f9a-407d-b089-54a8b51ab6f3n%40googlegroups.com.

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

             reply	other threads:[~2023-06-17 20:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-17 20:47 Mats Holmberg [this message]
     [not found] ` <0102580d-3f9a-407d-b089-54a8b51ab6f3n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-06-17 22:04   ` Bastien DUMONT
2023-06-17 23:16     ` Mats Holmberg

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=0102580d-3f9a-407d-b089-54a8b51ab6f3n@googlegroups.com \
    --to=elmatzo-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).