public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: BPJ <melroch-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: SmallCaps with Commonmark reader
Date: Sat, 24 Dec 2022 21:51:07 +0100	[thread overview]
Message-ID: <CADAJKhBBg3h61iA2VQq0Sd9pbkhH74zecrpUTGJSugOH647NbQ@mail.gmail.com> (raw)
In-Reply-To: <87edso7vwm.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>

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

I use the same trick to allow me to use shorter classes `.sc` and `.u` for
smallcaps and underline.

Den lör 24 dec. 2022 14:51Albert Krewinkel <albert+pandoc-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
skrev:

>
> Gabriel L <gabriel.lewertowski-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
>
> > Is there a way with commonmark reader to parse smallcaps as real
> > SmallCaps instead of Spans ? [...]
> >
> > I'd like to have the same behaviour as markdown reader:
> >
> > ```
> >> echo '[foo]{.smallcaps}' | pandoc -f markdown -t native
> > [ Para [ SmallCaps [ Str "foo" ] ] ]
> > ```
>
> The simplest way would be to use a short Lua filter. Save the below in a
> file `smallcaps.lua` and pass that file to pandoc via the `--lua-filter`
> parameter.
>
> ``` lua
> function Span (span)
>   if span.classes:includes 'smallcaps' then
>     return pandoc.SmallCaps(span.content)
>   end
> end
> ```
>
>
> --
> Albert Krewinkel
> GPG: 8eed e3e2 e8c5 6f18 81fe  e836 388d c0b2 1f63 1124
>
> --
> 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/87edso7vwm.fsf%40zeitkraut.de
> .
>

-- 
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/CADAJKhBBg3h61iA2VQq0Sd9pbkhH74zecrpUTGJSugOH647NbQ%40mail.gmail.com.

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

      parent reply	other threads:[~2022-12-24 20:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-24 13:02 Gabriel L
     [not found] ` <ca3dba29-5b52-4bc3-9d97-3ca09764277bn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-12-24 13:47   ` Albert Krewinkel
     [not found]     ` <87edso7vwm.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2022-12-24 20:51       ` BPJ [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=CADAJKhBBg3h61iA2VQq0Sd9pbkhH74zecrpUTGJSugOH647NbQ@mail.gmail.com \
    --to=melroch-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).