Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1TrxE6-0007Df-Iw for pgsql-www@arkaria.postgresql.org; Sun, 06 Jan 2013 20:53:50 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.72) (envelope-from ) id 1TrxE6-0002R8-3e for pgsql-www@arkaria.postgresql.org; Sun, 06 Jan 2013 20:53:50 +0000 Received: from magus.postgresql.org ([87.238.57.229]) by malur.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1TrxE5-0002R3-NU for pgsql-www@postgresql.org; Sun, 06 Jan 2013 20:53:49 +0000 Received: from mail-we0-f171.google.com ([74.125.82.171]) by magus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1TrxE2-0008BR-EI for pgsql-www@postgresql.org; Sun, 06 Jan 2013 20:53:49 +0000 Received: by mail-we0-f171.google.com with SMTP id u3so9497165wey.30 for ; Sun, 06 Jan 2013 12:53:45 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type:x-gm-message-state; bh=b9/ptl6vvSmOE6clZIEar63JKDpLfuHZTEMZ2uk1CGk=; b=DtEHsmw9IBhgp7iDc1V0huJ5mBIV7Zh0jk5xbTIj9CJ/fMbYwvfIOWBaDh4VzcbeYo xlMVQe7am/o7G0rGw6l69j46DfzX+UEs8vcO/uVauEiORKjchghZjDvvkRvK1kfA6tJd 46aualTrReTLrnNQY8MynVEm4xuelF7y4VQV7hIbTlErpu2UwvCGSVvdoOe7YG1cjpxX wdiycQzdQQmgpCWJ60XUFbt4bHPtQN1cSDEt+glnIhH6H2OuA2qlja+Hx9qvSzXYUix0 mtkfOu4rC2p/Z4RNqkh4i0gzFjBs/+lgmSMnHIy5Pp0FQw1p1MyGqbNOy3sT5RMLm2yg gnsg== MIME-Version: 1.0 X-Received: by 10.180.72.232 with SMTP id g8mr6257523wiv.0.1357505625102; Sun, 06 Jan 2013 12:53:45 -0800 (PST) Received: by 10.194.104.41 with HTTP; Sun, 6 Jan 2013 12:53:45 -0800 (PST) In-Reply-To: References: <18383.1357499527@sss.pgh.pa.us> Date: Sun, 6 Jan 2013 21:53:45 +0100 Message-ID: Subject: Re: New archives for testing From: Magnus Hagander To: Peter Geoghegan Cc: Tom Lane , PostgreSQL WWW Content-Type: text/plain; charset=ISO-8859-1 X-Gm-Message-State: ALoCoQloCBS3OETBeXtwSn5ar0w6KlWphdJfT+XLzYIgJ8eM+97VjJ51xatgVTl6h30djPCXK/Ct X-Pg-Spam-Score: -2.6 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-www Precedence: bulk Sender: pgsql-www-owner@postgresql.org On Sun, Jan 6, 2013 at 9:51 PM, Peter Geoghegan wrote: > On 6 January 2013 20:41, Magnus Hagander 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 (pgsql-www@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-www