public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: hcf <farsethas-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Bold and underline converting fra DocBook to Markdown
Date: Fri, 7 Apr 2023 10:31:56 -0700 (PDT)	[thread overview]
Message-ID: <ec7fb3a2-2037-4efe-995c-fd1285f6ebean@googlegroups.com> (raw)
In-Reply-To: <87ttxraik9.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>


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

Not that I am aware of. To two usages I posted are from DocBook generated 
by Make4ht.

fredag 7. april 2023 kl. 16:11:26 UTC+2 skrev Albert Krewinkel:

>
> hcf <fars...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
>
> > I am converting from DocBook to Markdown
> >
> > In DocBook bold and underline can be formatted with:
> >
> > <emphasis role="underline">underline</emphasis>
> > <emphasis role="bf">bold</emphasis>
> >
> > In Pandocs markdown I would expect this to result in a [Underline]
> > {.underline} and a **heavy emphasis**. I only get regular *emphasis*
> > for both.
> >
> > Is this implemented and can it be turned on with an option?
>
> Pandoc expected either "bold" or "strong" as role for strong emphasis.
> Underline was not supported. I've pushed a change to support underline
> and bf.
>
> Are there more roles that are commonly used?
>
>
> -- 
> 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/ec7fb3a2-2037-4efe-995c-fd1285f6ebean%40googlegroups.com.

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

      parent reply	other threads:[~2023-04-07 17:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-07 13:23 hcf
     [not found] ` <fea52285-b7e6-4f80-9ff8-fddd7e3a99a4n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-04-07 14:08   ` Albert Krewinkel
     [not found]     ` <87ttxraik9.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2023-04-07 17:31       ` hcf [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=ec7fb3a2-2037-4efe-995c-fd1285f6ebean@googlegroups.com \
    --to=farsethas-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).