> >From the translator POV, there are a number of static files and a pot
> > file
> that would need to be translated, basically using static files and cvs..
> After that there is some content that is database driven (news/events
> for example) that can be translated through the web interface. From the
> users end I think it basically works by users navigating to
> postgresql.org and then based on thier browser settings they are
> automagically served up content in the appropriate language.
Right. Problem is, we don't yet have a framework to check which files are
done and which are drafts, whether all the files are done, which have been
XHTML validated, and which English files have been updated since the last
translation. This is a huge TODO and I certainly wouldn't ask the
translators to get started without it.
Aglio Database Solutions
In response to
pgsql-advocacy by date
|Next:||From: Robert Treat||Date: 2005-11-17 22:08:15|
|Subject: Re: Swedish PostgreSQL site needs volunteers|
|Previous:||From: Josh Berkus||Date: 2005-11-17 21:57:53|
|Subject: Sun supporting PostgreSQL|