From: | Magnus Hagander <magnus(at)hagander(dot)net> |
---|---|
To: | Peter Geoghegan <peter(at)2ndquadrant(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL WWW <pgsql-www(at)postgresql(dot)org> |
Subject: | Re: New archives for testing |
Date: | 2013-01-06 20:53:45 |
Message-ID: | CABUevExrSBxtW3qkUA7-cn=DFTVVdcahDpWFovMcWOnRxf=ZhQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-www |
On Sun, Jan 6, 2013 at 9:51 PM, Peter Geoghegan <peter(at)2ndquadrant(dot)com> wrote:
> On 6 January 2013 20:41, Magnus Hagander <magnus(at)hagander(dot)net> 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/
From | Date | Subject | |
---|---|---|---|
Next Message | Greg Stark | 2013-01-06 20:59:13 | Re: New archives for testing |
Previous Message | Peter Geoghegan | 2013-01-06 20:51:54 | Re: New archives for testing |