public inbox for cygwin-patches@cygwin.com
 help / color / mirror / Atom feed
From: Jon Turney <jon.turney@dronecode.org.uk>
To: Cygwin Patches <cygwin-patches@cygwin.com>
Subject: Re: [PATCH] update site goldstar award types images from jpg/png to webp
Date: Wed, 9 Feb 2022 15:32:08 +0000	[thread overview]
Message-ID: <98550a9b-2ce0-328b-d737-a59cf7c7434a@dronecode.org.uk> (raw)
In-Reply-To: <df2f4097-35c1-78b0-3cb2-30d424fc167e@SystematicSw.ab.ca>

On 05/02/2022 23:18, Brian Inglis wrote:
> 
> One issue I found is that our DocBook 4 does not support webp, so there 
> is currently no support for webp images in generated docs from 
> cygwin-apps/cygwin-x-doc, so no value in converting, unless we want to 
> script an update to the image sources in the *generated* html.
> This affects only cygwin-htdocs/xfree/docs/ug/figures/ ~640KB reduced to 
> ~195KB in the attached image summary log.

Those docs are currently produced by an ancient docbook toolchain (using 
jade), so the whole thing could do with modernizing (assuming it's 
worthwhile having at all...).

> Directory summary totals are grouped at the bottom to show overall numbers.
> 
> It also looks like cygwin-htdocs/xfree/docs/ug/stylesheet-images/ and 
> cygwin-htdocs/xfree/images/ are not referenced anywhere so can be rm'ed: 
> checked with egrep -iR 'png|gif|bmp' cygwin-htdocs/.
> 
> So the net effect would be a reduction in image sizes from <4MB to <1MB.

I've removed cygwin-htdocs/xfree/images/.  Thanks for pointing that out.

I'm not sure what to do about that stylesheet.  It looks like was 
half-written when added (in 2001!).


      reply	other threads:[~2022-02-09 15:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-02  6:59 Brian Inglis
2022-02-02  9:44 ` Corinna Vinschen
2022-02-02 18:49   ` Brian Inglis
2022-02-02 20:41     ` Corinna Vinschen
2022-02-05 14:26       ` Jon Turney
2022-02-05 17:50         ` Marco Atzeri
2022-02-05 23:18           ` Brian Inglis
2022-02-09 15:32             ` Jon Turney [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=98550a9b-2ce0-328b-d737-a59cf7c7434a@dronecode.org.uk \
    --to=jon.turney@dronecode.org.uk \
    --cc=cygwin-patches@cygwin.com \
    /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).