public inbox for [email protected]
help / color / mirror / Atom feedFrom: Magnus Hagander <[email protected]>
To: Peter Geoghegan <[email protected]>
Cc: Tom Lane <[email protected]>
Cc: PostgreSQL WWW <[email protected]>
Subject: Re: New archives for testing
Date: Sun, 6 Jan 2013 21:53:45 +0100
Message-ID: <CABUevExrSBxtW3qkUA7-cn=DFTVVdcahDpWFovMcWOnRxf=ZhQ@mail.gmail.com> (raw)
In-Reply-To: <CAEYLb_UWpcNdyEHzOyzGYs9+CEXqrNP8-c5tPd6X9v1fK9jKYQ@mail.gmail.com>
References: <CABUevEwmR5+9fc1i1cFVpc1S8XShHwvKopcaKKfq-Txa+_mq_g@mail.gmail.com>
<[email protected]>
<CABUevEzx8tAUZErb8PhADj=mzSEUdUE8-ueqUfuP=mnNjbMQ3A@mail.gmail.com>
<CAEYLb_UWpcNdyEHzOyzGYs9+CEXqrNP8-c5tPd6X9v1fK9jKYQ@mail.gmail.com>
List-Unsubscribe: <mailto:[email protected]?body=unsub%20pgsql-www>
On Sun, Jan 6, 2013 at 9:51 PM, Peter Geoghegan <[email protected]> wrote:
> On 6 January 2013 20:41, Magnus Hagander <[email protected]> wrote:
>> We could inline all images, with that risk. Or maybe we could actually
>> parse the image to figure out it's size, and show it only when it's
>> smaller than a certain size. That might be a useful compromise...
>
> How likely is it in practice that an image is any other type of image?
> Ideally, you'd be able to do something with the image metadata to
> inline an image if its resolution is below a certain threshold. If
> that doesn't work out, I'd just inline png, gif and svg images, and
> leave it at that.
Well, that's what I'm considering, but inlining screenshots at high
resolutions is going to look Really Bad... But yes, the idea would be
to parse out the resolution from the metadata somehow.
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
--
Sent via pgsql-www mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-www
view thread (37+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected]
Subject: Re: New archives for testing
In-Reply-To: <CABUevExrSBxtW3qkUA7-cn=DFTVVdcahDpWFovMcWOnRxf=ZhQ@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox