public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Jonny Grant <jg@jguk.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb@sourceware.org
Subject: Re: gdb online manuals
Date: Mon, 21 Sep 2020 23:59:37 +0100	[thread overview]
Message-ID: <d0ac3e72-b0a0-5b6e-572f-314bebba4cd7@jguk.org> (raw)
In-Reply-To: <20200921003812.GA4075@adacore.com>



On 21/09/2020 01:38, Joel Brobecker wrote:
>> Thank you for the tip.
>> Ok, I saw version 9 is documented here now:
>> https://sourceware.org/gdb/onlinedocs/gdb/index.html
>>
>>
>> I noticed "refcard" and "stack_frame" only have gz versions. refcard.pdf.gz is actually only 1000 bytes smaller compressed, maybe simpler just to show it as a PDF? At least it shows in the browser then.
>>
>> stack_frame.pdf.gz is 7000 bytes smaller. I'm sure the web-browser would download it via http compression anyway.
> 
> I finally had some time to look at this today; as it turns out,
> it's just not refcard of stack_frame that don't compress well,
> it's all PDF files. I think the PDF being produced are already
> compressed, which explain why gzip doesn't provide much gains.
> 
> Given the extra usability, I just changed the generation of the docs
> to not compress the pdf files (the rest stays the same, as in those
> other formats, it does make a difference).
> 

Fantastic Joel, Thank you, Jonny

      reply	other threads:[~2020-09-21 22:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-15  9:27 Jonny Grant
2020-07-15 18:39 ` Joel Brobecker
2020-07-22 22:28   ` Jonny Grant
2020-09-21  0:38     ` Joel Brobecker
2020-09-21 22:59       ` Jonny Grant [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=d0ac3e72-b0a0-5b6e-572f-314bebba4cd7@jguk.org \
    --to=jg@jguk.org \
    --cc=brobecker@adacore.com \
    --cc=gdb@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).