All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Marc-André Lureau" <mlureau@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Markus Armbruster <armbru@redhat.com>,
	QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PULL v2 000/180] QAPI patches for 2017-01-16
Date: Tue, 17 Jan 2017 09:15:42 -0500 (EST)	[thread overview]
Message-ID: <1132843531.1046582.1484662542391.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <CAFEAcA_txNPj6JNDavmCREse98XTkQgiFAqx5Vf8KCCu9V-6mQ@mail.gmail.com>

Hi

----- Original Message -----
> On 17 January 2017 at 13:24, Markus Armbruster <armbru@redhat.com> wrote:
> > Peter Maydell <peter.maydell@linaro.org> writes:
> >> (1) if it doesn't actually cause a change in the output, we
> >> should either just delete the use of VERSION entirely, or move
> >> it to somewhere outside of @subtitle which does actually
> >> appear somewhere. There's no point in putting in the version
> >> info if it doesn't get into the final output, whether
> >> it generates a warning or not.
> >
> > It does affect PDF output.  PDF is generated by texi2pdf, which uses
> > different command line options, and setting VERSION works fine there.
> 
> Mmm, but if it's useful information we should be displaying
> it in all our documentation formats, not just tucking it
> away in something that only appears in the PDF.
> Conversely, if we're happy for some of our document formats
> not to contain it we could save ourselves the grief of
> having to work around this bug by dropping the @subtitle entirely.

It would be quite easy to add to the rest of the docs, that can be added on top.

If its not useful enough in this current form (since it's only in the PDF, because tooling is lacking support), feel freel to remove it Markus.

> As an aside, how useful is the PDF output anyway? In 2017
> there seems to me quite a good argument for just creating
> HTML...
> 


Afaik, most browsers support pdf nowadays.

pdf output is more pleasant to read, the html version would need significant styling to be comparable (I have played with the CSS, that would already help). I hope we get there once we have better doc tooling (sphinx, readthedocs etc)

  reply	other threads:[~2017-01-17 14:15 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-16  9:33 [Qemu-devel] [PULL v2 000/180] QAPI patches for 2017-01-16 Markus Armbruster
2017-01-16 15:58 ` Peter Maydell
2017-01-17  8:31   ` Markus Armbruster
2017-01-17  9:54     ` Marc-André Lureau
2017-01-17 10:13       ` Markus Armbruster
2017-01-17 11:08     ` Peter Maydell
2017-01-17 12:08       ` Markus Armbruster
2017-01-17 12:24         ` Peter Maydell
2017-01-17 13:24           ` Markus Armbruster
2017-01-17 13:59             ` Peter Maydell
2017-01-17 14:15               ` Marc-André Lureau [this message]
2017-01-17 14:23               ` Markus Armbruster
2017-01-17 16:43                 ` Peter Maydell
2017-01-20 14:39                   ` Peter Maydell
2017-01-20 15:46                     ` Markus Armbruster
2017-01-20 15:48                       ` Peter Maydell
2017-01-23 12:48                         ` Alex Bennée
2017-01-23 13:59                       ` Daniel P. Berrange
2017-01-23 14:49                         ` Markus Armbruster
2017-01-24  9:53                     ` Markus Armbruster
2017-01-24 10:03                       ` Peter Maydell
2017-01-24 11:08                         ` Markus Armbruster
2017-01-24 10:09                       ` Markus Armbruster
2017-01-24 10:49                         ` Paolo Bonzini
2017-01-17 17:05         ` Eric Blake

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=1132843531.1046582.1484662542391.JavaMail.zimbra@redhat.com \
    --to=mlureau@redhat.com \
    --cc=armbru@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.