public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: "Bücherregal Domi" <gamezaerza-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Identify lists (<ul> and <ol> tags)
Date: Wed, 14 Apr 2021 07:36:21 -0700 (PDT)	[thread overview]
Message-ID: <c50ee03e-a89a-411e-ba45-e7a9ddacbc42n@googlegroups.com> (raw)
In-Reply-To: <8752d80b96c1f013cd65fc0798b8d5d9-aFO/2INALiozYggVrLCuDg@public.gmane.org>


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

Hi Sean, if you use Pandoc to convert your Markdown files, there is a 
notation for divs, doing:

::: class_string
content
:::

This is exactly the same as doing:

<div class="class_string">
<p>content</p>
</div>

S. Manning schrieb am Dienstag, 13. April 2021 um 01:40:13 UTC-5:

> Could you explain? Do you mean add a div as inline HTML around the list 
> written in Markdown syntax, or do some versions of Markdown have a 
> Markdown annotation that is equivalent to a HTML div?
>
> It seems to me that often encoding something as HTML is just as quick 
> and pretty as encoding it slightly differently as Markdown. I am not 
> familiar with versions of Markdown with this 'identifier' syntax.
>
> Sean
>
> On 2021-04-12 01:01, BPJ wrote:
> > You can always wrap the list in a div with attributes and then use a
> > child selector in your CSS:
> > 
> > ``````markdown
> > 
> > ::: {#my-list}
> > 
> > - This
> > - That
> > 
> > :::
> > ``````
> > 
> > ``````css
> > div#my-list ul {
> > /* Put your style here */
> > }
> > ``````
> > 
> > Not the most concise or pretty HTML or CSS imaginable but it works!
> > 
> > On occasion I have used Mojo::DOM[^1] to post-process such HTML to
> > actually attach the attributes to the contained element and remove the
> > div or span, but its mostly overkill unless you have to adapt to some
> > existing common CSS, since hardly anyone will look at your HTML source
> > or CSS anyway.
> > 
> > [^1]: https://metacpan.org/pod/Mojo::DOM
> > 
> > Den mån 12 apr. 2021 09:47Bücherregal Domi <gamez...-Re5JQEeQqe8@public.gmane.orgm>
> > skrev:
> > 
> >> Hello, is there a way to use HTML identifiers with lists? Something
> >> like
> >> 
> >> ``` markdown
> >> {#id_string}
> >> - item
> >> - item
> >> 
> >> ```
> >> 
> >> This would allow to identify different lists in the Markdown file,
> >> and it would also allow different CSS styles to be applied to each
> >> list. This type of identification already exists for headers, spans,
> >> etc.
> >> 
> >> --
> >> 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-discus...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> >> To view this discussion on the web visit
> >> 
> > 
> https://groups.google.com/d/msgid/pandoc-discuss/0a5fdf61-8f1e-4f11-b392-7838729d63cen%40googlegroups.com
> >> [1].
> > 
> > --
> > 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-discus...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> > To view this discussion on the web visit
> > 
> https://groups.google.com/d/msgid/pandoc-discuss/CADAJKhAj%2Bw8fVs34n-NT_1-KGKpG1wessNp8V3%2BOtaTfC9g6Cg%40mail.gmail.com
> > [2].
> > 
> > 
> > Links:
> > ------
> > [1] 
> > 
> https://groups.google.com/d/msgid/pandoc-discuss/0a5fdf61-8f1e-4f11-b392-7838729d63cen%40googlegroups.com?utm_medium=email&amp;utm_source=footer
> > [2] 
> > 
> https://groups.google.com/d/msgid/pandoc-discuss/CADAJKhAj%2Bw8fVs34n-NT_1-KGKpG1wessNp8V3%2BOtaTfC9g6Cg%40mail.gmail.com?utm_medium=email&utm_source=footer
>

-- 
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/c50ee03e-a89a-411e-ba45-e7a9ddacbc42n%40googlegroups.com.

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

      parent reply	other threads:[~2021-04-14 14:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-12  7:46 Bücherregal Domi
     [not found] ` <0a5fdf61-8f1e-4f11-b392-7838729d63cen-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-04-12  8:01   ` BPJ
     [not found]     ` <CADAJKhAj+w8fVs34n-NT_1-KGKpG1wessNp8V3+OtaTfC9g6Cg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2021-04-12 10:04       ` Albert Krewinkel
     [not found]         ` <878s5nddiu.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2021-04-12 13:47           ` Bücherregal Domi
2021-04-13  6:40       ` S. Manning
     [not found]         ` <8752d80b96c1f013cd65fc0798b8d5d9-aFO/2INALiozYggVrLCuDg@public.gmane.org>
2021-04-13  7:29           ` Matt Jolly
2021-04-14 14:36           ` Bücherregal Domi [this message]

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=c50ee03e-a89a-411e-ba45-e7a9ddacbc42n@googlegroups.com \
    --to=gamezaerza-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).