Received: from localhost (unknown [200.46.204.183])
	by postgresql.org (Postfix) with ESMTP id 97CB72E0030
	for <pgsql-www-postgresql.org@postgresql.org>;
	Wed, 19 Mar 2008 21:04:22 -0300 (ADT)
Received: from postgresql.org ([200.46.204.71])
	by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024)
	with ESMTP id 08424-03 for <pgsql-www-postgresql.org@postgresql.org>;
	Wed, 19 Mar 2008 21:04:20 -0300 (ADT)
Received: from mx3.hub.org (mx3.hub.org [206.223.169.73])
	by postgresql.org (Postfix) with ESMTP id 23CC82E002F
	for <pgsql-www@postgresql.org>; Wed, 19 Mar 2008 21:04:20 -0300 (ADT)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.5
Received: from svr2.hagander.net (svr2.hagander.net [88.198.128.226])
	by mx3.hub.org (Postfix) with ESMTP id 885A337CA8B
	for <pgsql-www@postgresql.org>; Wed, 19 Mar 2008 21:04:18 -0300 (ADT)
Received: from dynamic.hagander.net ([127.0.0.1]) (encrypted and
	authenticated) by svr2.hagander.net (Postfix) with ESMTP id
	E2B16DCC96A; Wed, 19 Mar 2008 22:57:15 +0100 (CET)
Message-ID: <47E18CDB.60303@hagander.net>
Date: Wed, 19 Mar 2008 22:59:55 +0100
From: Magnus Hagander <magnus@hagander.net>
User-Agent: Thunderbird 2.0.0.12 (X11/20080213)
MIME-Version: 1.0
To: Guillaume Lelarge <guillaume@lelarge.info>
CC: PostgreSQL www <pgsql-www@postgresql.org>
Subject: Re: Patch to make some strings available to translations
References: <47DAF7E3.8070502@lelarge.info> <47DD4BAA.5000402@hagander.net>
	<47DD9F5C.1060101@lelarge.info> <47E0B5CD.9030504@lelarge.info>
	<47E18498.4060609@lelarge.info>
In-Reply-To: <47E18498.4060609@lelarge.info>
X-Enigmail-Version: 0.95.6
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Archive-Number: 200803/397
X-Sequence-Number: 14516

Guillaume Lelarge wrote:
> Guillaume Lelarge a écrit :
>> [...]
>> Next work... translatable images.
>>
> 
> I found a way to get translatables images but I can't stop thinking this 
> is an ugly *ugly* hack. Here is my idea : using the func_lang on the 
> href part of the img tag. For example, here is a part of the patch :
> 
> -                    <h2><img 
> src="/layout/images/en/hdr_featureduser.png" width="104" height="10" 
> alt="Featured User" /></h2>
> +                    <h2><img 
> src=func_lang("'/layout/images/en/hdr_featureduser.png'") width="104" 
> height="10" alt=func_lang("'Featured User'") /></h2>
> 
> This way, each translation can add a specific path and a specific 
> filename. Perhaps, we can only use the path. In my tests, I use 
> /layout/images/fr instead of /layout/images/en.
> 
> Do you have any comments on this dirty idea ? :) if you think this is 
> something doable, I can quickly build a small patch.

I don't like it at all.

I think we need something like func_image('hdr_featureduser.png'), and 
then have the framework take care of that one.


> But my real issue is doing the actual images... I'm not good a this :)

That's another problem. It requires non-free fonts... See the archives :-(

Perhaps this is a good time to try to find a free font that can do what 
we need.


//Magnus