Re: error translations

Adrian Chadd wrote:
> Will that give you a way to create custom themed pages?
>
> The reason I migrated a directory of error pages in Cacheboy (English
> -> NewEnglish) to use CSS is it makes that particular task so much
> easier in the long run. Once you've laid out a sensible CSS model for
> the pages then people can glue in inline CSS (until Squid turns into a
> webserver.. :) and create highly customised error pages.
>

This is part 2 of all that. Part 1 already went is as regular cleanups.

1) standard-compliant base templates (DONE, English files I just comitted)

2) easy translation (these .po are well-known dictionary types in wide use)

3) CSS, configurable stylesheet, and fancy polish.
     This means pushing CSS id's into the basic templates HTML.
     Giving STYLE tags a % var linking a file via squid.conf.

4) Dynamic language pages :-). Getting the translated dictionaries ISO
coded. So the file load logic can match them against the request
language header.

I still see the completely-different themed pages as best using
deny_info. But this way gets us to the basic color schemes and CSS-based
images people may want.

Amos

>
>
>
> Adrian
>
>
> 2008/7/14 Amos Jeffries <amos_at_treenet.co.nz>:
>> I'm looking at improving the error pages HTML and translations.
>> The easiest quickest approach to be using pootle and .PO translations as a
>> dictionary system.
>>
>> As far as I can tell so far, this has the benefit of being usable without
>> any coding changes in squid as it can dynamically generate all the
>> translated error pages directly from the English base pages + a dictionary.
>>
>> This also gives us the benefit of publishing the .po templates for community
>> translation via places like launchpad.
>>
>> Comments?
>>
>> Amos
>>
>>

-- 
Please use Squid 2.7.STABLE3 or 3.0.STABLE7