Magnus Hagander a écrit :
> 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.
>
Yep, I guess it couldn't be that simple :)
> I think we need something like func_image('hdr_featureduser.png'), and
> then have the framework take care of that one.
>
Which means we need to modify the framework ? that'll be a much bigger
work than what I intended to do. Anyways, I'll get a look at it.
>> 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 :-(
>
Yes, I remember this.
> Perhaps this is a good time to try to find a free font that can do what
> we need.
>
+1
--
Guillaume. http://www.postgresqlfr.org http://dalibo.com
