public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Daniel Staal <DStaal-Jdbf3xiKgS8@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Markdown italics and quotation marks
Date: Tue, 4 Apr 2023 22:46:44 -0400	[thread overview]
Message-ID: <7ab252c0-1970-e8ee-878a-f20a8dc3a0c2@usa.net> (raw)
In-Reply-To: <d0cd8bd4-e274-4a91-a34d-5d72cbc4b984n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>

On 4/4/23 7:22 PM, Some Author Guy wrote:
> I'm writing a book with ships in it. It's not uncommon for a quote to 
> begin with the name of a ship, which I will attempt to italicize, but 
> then to continue with normal speech, which ought not to be italicized. 
> Consider the following paragraph:
> 
> *"Shipname* is in port for the next week."
> 
> This always fails. I get a pair of asterisks in the output and no 
> italics. I don't have this problem without the unbalanced quotation 
> mark, but I don't know why that is. I can't imagine why the quote would 
> have any significance.

This one it's actually easier to see the issue in HTML.  Here's what 
you're writing:

<em><quote>Shipname</em> is in port for the next week.</quote>

You can see in that the tags are improperly nested.  Now, I can see an 
argument that Markdown shouldn't need to follow nesting conventions like 
HTML does, but the point stands that you have two overlapping tag 
sequences.  (And in this case at least, I think it's also good English 
grammar - you're trying to italicize the name of the ship, not the start 
of the quote.)

As John has already said, correcting the nesting will solve the issue:

<quote><em>Shipname</em> is in port for the next week.</quote>

Or in Markdown:

"*Shipname* is in port for the next week."

Daniel T. Staal

-- 
---------------------------------------------------------------
This email copyright the author.  Unless otherwise noted, you
are expressly allowed to retransmit, quote, or otherwise use
the contents for non-commercial purposes.  This copyright will
expire 5 years after the author's death, or in 30 years,
whichever is longer, unless such a period is in excess of
local copyright law.
---------------------------------------------------------------


      parent reply	other threads:[~2023-04-05  2:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-04 23:22 Some Author Guy
     [not found] ` <d0cd8bd4-e274-4a91-a34d-5d72cbc4b984n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-04-05  0:01   ` John MacFarlane
2023-04-05  2:46   ` Daniel Staal [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=7ab252c0-1970-e8ee-878a-f20a8dc3a0c2@usa.net \
    --to=dstaal-jdbf3xikgs8@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).