public inbox for [email protected]
help / color / mirror / Atom feedFrom: Magnus Hagander <[email protected]>
To: Peter Eisentraut <[email protected]>
Cc: [email protected]
Cc: Bruce Momjian <[email protected]>
Cc: Andrew Sullivan <[email protected]>
Subject: Re: [BUGS] BUG #4279: Bad codepage in our web-site
Date: Mon, 25 Aug 2008 16:37:08 +0200
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
<[email protected]>
<[email protected]>
Peter Eisentraut wrote:
> On Monday 25 August 2008 11:00:12 Magnus Hagander wrote:
>> I wouldn't put too much work into that. Wouldn't it be better to migrate
>> them to the wiki instead?
>
> I'm all in favor of the wiki, but consider that this is prominent user-facing
> stuff here. If we put the FAQ in the wiki, why not the entire web site?
> Perhaps the web team should take over these files and apply the existing
> translation framework to it.
That we could certainly do. At least if we can get pgweb set up to
allow specific permissions to update these things - I would like to rid
us of the bottleneck of having to write up an actual patch and send it
to a list, to have somebody else apply it, and only then realize it's
broken HTML etc. The translators should be able to do this on their own.
I don't think the current web team can just "take them over". Sure, they
could take over the part that Bruce does today which is apply patches
for people, but it doesn't solve the issue in itself.
//Magnus
view thread (13+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected], [email protected]
Subject: Re: [BUGS] BUG #4279: Bad codepage in our web-site
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox