public inbox for newlib@sourceware.org
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: newlib@sourceware.org
Subject: Re: [PATCH htdocs 1/7] crush images
Date: Wed, 16 Feb 2022 23:27:39 -0700	[thread overview]
Message-ID: <c1bbdfb5-fbd8-426e-26d7-8b6b640af67e@SystematicSw.ab.ca> (raw)
In-Reply-To: <YgsPozHHxcpJTfHH@vapier>

On 2022-02-14 19:27, Mike Frysinger wrote:
> Shrink their sizes while maintaining their content by recompressing
> and stripping unused metadata.

>   download.jpg   | Bin 1671 -> 1344 bytes
>   faq.jpg        | Bin 1312 -> 983 bytes
>   info.jpg       | Bin 1218 -> 886 bytes
>   logo_big2.png  | Bin 973 -> 844 bytes
>   mailing.jpg    | Bin 1902 -> 1580 bytes
>   news.jpg       | Bin 1287 -> 960 bytes
>   properties.png | Bin 49230 -> 36129 bytes
>   7 files changed, 0 insertions(+), 0 deletions(-)

I've had good results usually about 25-50% of PNG replacing some Cygwin 
images with webp, by tweaking some basic parameters, and comparing 
sizes, although many of your initial file sizes are small by comparison:

Cygwin htdocs:

  639178 png	 195942 webp	docs/ug/figures/
    7458 png/bmp	   1112 webp	docs/xlaunch/
3548814 png	 898900 webp	screenshots/
  208225 png	  30848 webp	screenshots/thumbs/

4403675 png/bmp 1126802 webp	total

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]

  reply	other threads:[~2022-02-17  6:27 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-15  2:25 [PATCH htdocs 0/7] various website updates Mike Frysinger
2022-02-15  2:25 ` [PATCH htdocs 2/7] switch to https:// for many sites Mike Frysinger
2022-02-15  2:25 ` [PATCH htdocs 3/7] add libgloss manual from current git Mike Frysinger
2022-02-15  2:25 ` [PATCH htdocs 5/7] simplify mailing list news links Mike Frysinger
2022-02-15  2:25 ` [PATCH htdocs 6/7] update news entries for last few years Mike Frysinger
2022-02-15  2:25 ` [PATCH htdocs 7/7] update autotools faq entry to match current tree Mike Frysinger
2022-02-15  2:27 ` [PATCH htdocs 1/7] crush images Mike Frysinger
2022-02-17  6:27   ` Brian Inglis [this message]
2022-02-17 15:56     ` Brian Inglis
2022-02-15  2:28 ` [PATCH htdocs 4/7] refressh libc & libm manual from current git Mike Frysinger
2022-02-16 10:56 ` [PATCH htdocs 0/7] various website updates Corinna Vinschen
2022-02-17  1:39   ` Mike Frysinger
2022-02-17 12:07     ` Corinna Vinschen

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=c1bbdfb5-fbd8-426e-26d7-8b6b640af67e@SystematicSw.ab.ca \
    --to=brian.inglis@systematicsw.ab.ca \
    --cc=newlib@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).