From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: Wei Liu <wei.liu2@citrix.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
Xen-devel <xen-devel@lists.xen.org>
Subject: Re: [PATCH for-4.7 2/3] docs/xsplice: Fix syntax when compiling to pdf with pandoc
Date: Thu, 19 May 2016 16:04:37 +0100 [thread overview]
Message-ID: <573DD605.40706@citrix.com> (raw)
In-Reply-To: <20160519145604.GA26344@localhost.localdomain>
On 19/05/16 15:56, Konrad Rzeszutek Wilk wrote:
> On Thu, May 19, 2016 at 03:41:49PM +0100, Andrew Cooper wrote:
>> On 19/05/16 15:36, Konrad Rzeszutek Wilk wrote:
>>> On Thu, May 19, 2016 at 03:29:45PM +0100, Andrew Cooper wrote:
>>>> Pandoc (version 1.12.4.2 from Debian Jessie) complains at the embedded \n in
>>>> the signature checking paragraph.
>>>>
>>>> /usr/bin/pandoc --number-sections --toc --standalone misc/xsplice.markdown
>>>> --output pdf/misc/xsplice.pdf
>>>> ! Undefined control sequence.
>>>> l.1085 appended\textasciitilde{}\n
>>>>
>>>> Surround the string in backticks to make it verbatim text.
>>> Ok, where is that change?
>>> @@ -1007,46 +1007,46 @@ expecting such that it can properly do signature verification.
>>>
>>> The signature is based on the all of the payloads continuously laid out
>>> in memory. The signature is to be appended at the end of the ELF payload
>>> -prefixed with the string '~Module signature appended~\n', followed by
>>> +prefixed with the string `'~Module signature appended~\n'`, followed by
>>> an signature header then followed by the signature, key identifier, and signers
>>> name.
>> ^ Here.
> Thank you!
>>>> While altering this file, strip the substantial quantity of trailing
>>>> whitespace.
>>> Please do not. That was added specifically there otherwise
>>> markdown messes it up when doing HTML and the lines get mangled up.
>> Markdown isn't whitespace sensitive, so that really shouldn't be doing
>> anything. If you want a verbatim text block, indent it by 4 characters.
> https://daringfireball.net/projects/markdown/syntax
>
> "When you do want to insert a <br /> break tag using Markdown, you end a
> line with two or more spaces, then type return."
(You learn something every day), and eww... That is nasty.
>
> But if this can be done with indenting it with 4 characters that would
> work too.
I recommend https://daringfireball.net/projects/markdown/syntax#precode
~Andrew
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-05-19 15:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-19 14:29 [PATCH for-4.7 1/3] docs/build: Avoid using multi-target pattern rules Andrew Cooper
2016-05-19 14:29 ` [PATCH for-4.7 2/3] docs/xsplice: Fix syntax when compiling to pdf with pandoc Andrew Cooper
2016-05-19 14:36 ` Konrad Rzeszutek Wilk
2016-05-19 14:41 ` Andrew Cooper
2016-05-19 14:56 ` Konrad Rzeszutek Wilk
2016-05-19 15:04 ` Andrew Cooper [this message]
2016-05-19 15:07 ` Wei Liu
2016-05-19 20:37 ` Konrad Rzeszutek Wilk
2016-05-20 18:09 ` [PATCH v2 for-4.7] " Andrew Cooper
2016-05-20 18:30 ` Konrad Rzeszutek Wilk
2016-05-19 14:29 ` [PATCH for-4.7 3/3] docs/feature: Tweaks to the feature document template Andrew Cooper
2016-05-23 10:19 ` [PATCH for-4.7 1/3] docs/build: Avoid using multi-target pattern rules Wei Liu
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=573DD605.40706@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=konrad.wilk@oracle.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xen.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).