public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: BPJ <bpj-J3H7GcXPSITLoDKTGw+V6w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Cc: Joseph Reagle <joseph.2011-T1oY19WcHSwdnm+yROfE0A@public.gmane.org>
Subject: Re: resulting HTML tables be given IDs?
Date: Fri, 24 Sep 2021 19:40:48 +0200	[thread overview]
Message-ID: <CADAJKhCG8MeKBnAhVZJWDMh-41f6wHE+LJSmTuDVCs+OmA_B7g@mail.gmail.com> (raw)
In-Reply-To: <m2o88i1q8t.fsf-d8241O7hbXoP5tpWdHSM3tPlBySK3R6THiGdP5j34PU@public.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 2650 bytes --]

If the purpose is to style a table with CSS wrapping the table in a div and
using a child selector like `div#my-id table` will work fine.

Den fre 24 sep. 2021 07:46John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org> skrev:

>
> You can put an identifier on part of the capture in the
> way you describe, but currently there's no good way to
> put an identifier on the Table element itself -- though
> the AST now does allow attributes there.
>
> Well, actually, there is one way, but only in commonmark
> with the attributes extension:
>
> ```
> % pandoc -f commonmark_x
> {#mytable}
> | This | is |
> | ---  | -- |
> | my   | table |
> <table id="mytable">
> <thead>
> <tr class="header">
> <th>This</th>
> <th>is</th>
> </tr>
> </thead>
> <tbody>
> <tr class="odd">
> <td>my</td>
> <td>table</td>
> </tr>
> </tbody>
> </table>
> ```
>
> Joseph Reagle <joseph.2011-T1oY19WcHSwdnm+yROfE0A@public.gmane.org> writes:
>
> > Just as headings and sections can take automatic fragment identifiers
> (and be included in ToCs), has any thought been given (or have I missed)
> doing the same for tables/captions? Or is the consensus this is best left
> to the author, as in the example below?
> >
> >       # Results
> >
> >       ::: {style="font: 90% 'Airal', sans-serif;"}
> >
> >       : [Table 1]{#table_spins}: Reddit phrases and automated spins
> >
> >       ...
> >
> > --
> > 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/3b04ddd1-260e-1a0c-8896-5c8f04b6101f%40reagle.org
> .
>
> --
> 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/m2o88i1q8t.fsf%40Johns-Air.hsd1.ca.comcast.net
> .
>

-- 
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/CADAJKhCG8MeKBnAhVZJWDMh-41f6wHE%2BLJSmTuDVCs%2BOmA_B7g%40mail.gmail.com.

[-- Attachment #2: Type: text/html, Size: 4193 bytes --]

  parent reply	other threads:[~2021-09-24 17:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-23 18:02 Joseph Reagle
     [not found] ` <3b04ddd1-260e-1a0c-8896-5c8f04b6101f-T1oY19WcHSwdnm+yROfE0A@public.gmane.org>
2021-09-24  5:45   ` John MacFarlane
     [not found]     ` <m2o88i1q8t.fsf-d8241O7hbXoP5tpWdHSM3tPlBySK3R6THiGdP5j34PU@public.gmane.org>
2021-09-24 17:40       ` BPJ [this message]
2021-09-24 20:03       ` Joseph Reagle
     [not found]         ` <bf1b477e-7537-3b19-0c2c-34d9ad6f2bc7-T1oY19WcHSwdnm+yROfE0A@public.gmane.org>
2021-09-27  1:35           ` 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=CADAJKhCG8MeKBnAhVZJWDMh-41f6wHE+LJSmTuDVCs+OmA_B7g@mail.gmail.com \
    --to=bpj-j3h7gcxpsitlodktgw+v6w@public.gmane.org \
    --cc=joseph.2011-T1oY19WcHSwdnm+yROfE0A@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).