Re: Proposal for building knowledgebase website.

> -----Original Message-----
> From: pgsql-www-owner(at)postgresql(dot)org
> [mailto:pgsql-www-owner(at)postgresql(dot)org] On Behalf Of Robert Treat
> Sent: 08 June 2005 20:30
> To: josh(at)agliodbs(dot)com
> Cc: Magnus Hagander; pgsql-www(at)postgresql(dot)org
> Subject: Re: [pgsql-www] Proposal for building knowledgebase website.
>
> On Wed, 2005-06-08 at 14:29, Josh Berkus wrote:
> > Magnus,
> >
> > > That seems like a good way to do it - if we even get
> translations. A lot
> > > of work was put into putting a translation infrastructure for the
> > > webpage in place, but AFAIK not a single page (except the
> FAQs which
> > > aren't in the actual website) has been translated.
> >
> > Well, there's a couple reasons for that:
> > 1) there's no documentation that I know of which explains
> how to translate
> > the site. Nor has any attempt been make to recruit translators.
> >
>
> IMHO this is a red herring, since there is documentation that gets you
> 80% of the way there. Thing is that 80% is such a huge task it's
> overwhelming for most folks.

Documentation is at
http://gborg.postgresql.org/project/pgweb/cvs/co.php/portal/README, plus
I've posted more detailed instructions to the list on at least one
occasion.

> > 2) the translation infrastructure is very much organized
> around generating
> > all new content in English and then pushing it off to the
> other languages
> > to translate, not letting them generate their own content.
> This means
> > that, for example, postgresql.org.br would need to
> translate our site
> > *and* maintain their own. Which they're unlikely to do.
> >
>
> I'm pretty sure you can create pages in other languages that do not
> exist in the english language, but yes, the general idea is that of
> making the main site multi-lingual, not for letting everyone do their
> own thing... and people like to do their own thing.

You can. Each language is totally independent of the others. The only
cross-over occurs when you have files of the same name in different
languages, in which case you will be dispatched the version in the
highest priority language that your browser will accept. If one language
put all it's text under, say, /foo/, then it would be completely
independent of the rest of the site.

Regards, Dave