From: "Martin Ågren" <martin.agren@gmail.com>
To: Felipe Contreras <felipe.contreras@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: [PATCH 0/6] AsciiDoc vs Asciidoctor, once again
Date: Fri, 14 May 2021 17:28:09 +0200 [thread overview]
Message-ID: <CAN0heSp7JFS3j+DypQm=P-rPzyScvs+Yed75AXYBsQpbJtVytA@mail.gmail.com> (raw)
In-Reply-To: <609e6be4bc14d_4312720861@natae.notmuch>
On Fri, 14 May 2021 at 14:24, Felipe Contreras
<felipe.contreras@gmail.com> wrote:
>
> Martin Ågren wrote:
> > On Fri, 14 May 2021 at 03:40, Felipe Contreras
> > <felipe.contreras@gmail.com> wrote:
> >
> > > We should be submitting bug reports to the asciidoctor project as well,
> > > so in the future it's less likely we find ourselves in the same
> > > scenario.
> > >
> > > Preferably the bug report should be in the commit message.
> >
> > I don't have an account with the website they use for their issue
> > tracking.
>
> GitHub? It probably takes a couple of minutes to set up an account.
Yes, it's GitHub. I'm not interested in having an account there. There's
some trade-off there with me not being able to report bugs, but that
cuts both ways, so I don't feel bad about it.
> > If you want to submit a bug report and post the link here,
> > that's fine by me and I'll include it in the reroll.
>
> If you would rather have me act as a proxy, that's fine by me.
Thanks. If you have better things to do, no worry.
> Just give me a simple example that produces the issue.
Here are three variants where AsciiDoc 8.6.10 renders the same, with
emphasis:
single quotes that will not render literally: 'git cat-file'.
single quotes that won't render literally: 'git cat-file'.
single quotes that\'ll render literally: 'git cat-file'.
With Asciidoctor (2.0.15),
asciidoctor -b docbook5 -d manpage -o test.xml test.txt
the XML contains
<simpara>single quotes that will not render literally: <emphasis>git
cat-file</emphasis>.</simpara>
<simpara>single quotes that won’t render literally:
<emphasis>git cat-file</emphasis>.</simpara>
<simpara>single quotes that’ll render literally: 'git cat-file'.</simpara>
That last paragraph is not as expected. I expect <emphasis>.
I realize that a good answer here is "don't do that then". But the
background is that there's some other stuff going on that means AsciiDoc
needs that backspaced apostrophe. So this is a minimal reproduction for
Asciidoctor where we've lost some of the AsciiDoc-specific background.
A fix that works with both tools is an attribute:
:apos: '
single quotes that won{apos}t render literally: 'git cat-file'.
Martin
next prev parent reply other threads:[~2021-05-14 15:28 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-13 18:17 [PATCH 0/6] AsciiDoc vs Asciidoctor, once again Martin Ågren
2021-05-13 18:17 ` [PATCH 1/6] git-http-push.txt,git-send-pack.txt: avoid single quote Martin Ågren
2021-05-13 18:17 ` [PATCH 2/6] git-range-diff.txt: avoid single quotes Martin Ågren
2021-05-13 18:17 ` [PATCH 3/6] git-check-ref-format.txt: avoid single quote Martin Ågren
2021-05-13 19:16 ` Eric Sunshine
2021-05-13 19:35 ` Martin Ågren
2021-05-13 22:00 ` Junio C Hamano
2021-05-14 9:07 ` Martin Ågren
2021-05-14 12:30 ` Felipe Contreras
2021-05-14 5:30 ` Jeff King
2021-05-14 9:08 ` Martin Ågren
2021-05-13 18:17 ` [PATCH 4/6] diff-options.txt: move monospace markup out of attribute Martin Ågren
2021-05-13 18:17 ` [PATCH 5/6] git-svn.txt: change verse to listing block Martin Ågren
2021-05-13 18:17 ` [PATCH 6/6] Doc: use two backticks for monospace, not backtick+apostrophe Martin Ågren
2021-05-13 20:35 ` [PATCH 0/6] AsciiDoc vs Asciidoctor, once again Junio C Hamano
2021-05-14 8:40 ` Martin Ågren
2021-05-14 12:18 ` Felipe Contreras
2021-05-14 1:40 ` Felipe Contreras
2021-05-14 8:43 ` Martin Ågren
2021-05-14 12:24 ` Felipe Contreras
2021-05-14 15:28 ` Martin Ågren [this message]
2021-05-14 20:11 ` Felipe Contreras
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAN0heSp7JFS3j+DypQm=P-rPzyScvs+Yed75AXYBsQpbJtVytA@mail.gmail.com' \
--to=martin.agren@gmail.com \
--cc=felipe.contreras@gmail.com \
--cc=git@vger.kernel.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).