> -----Original Message-----
> From: pgsql-www-owner@postgresql.org
> [mailto:pgsql-www-owner@postgresql.org] On Behalf Of Adrian Maier
> Sent: 01 March 2005 10:54
> To: pgsql-www@postgresql.org
> Subject: [pgsql-www] Translating the website (to Romanian)
>
> Hello everyone,
>
> Rather than creating a Romanian PostgreSQL website from scratch,
> I plan to start translating the main website. I have already checked
> out the pgweb project, and looked at it a little.
>
> The README file contains a few hints for translating :
> 1. Prepare gettext translations.
>
> Apart from "portal/po/portal.pot" , are there other files that
> need to be translated? (i'm not familiar with gettext)
No, that should be all, *BUT*, that template needs to be updated with
the latest strings first, which requires some scripting work to be done.
> 2. Translate the static pages.
>
> I should create RO versions of the files that exist in the
> template/en directory and put them in template/ro .........
> is that right ?
Yup.
> 3. Translate the contents stored in the database.
>
> How can I obtain a dump of this database? i've installed a local
> copy of the website, and obviuosly it says that " the
> news database
> server is currently down".
News, events and surveys should be translated through the admin
interface to the site. The database dump won't help a great deal as
99.999% of it is the docs, doc comments, mirror data and clickthru data.
> It would be more convenient for me to provide a sql script with
> insert commands rather than use a web interface, because this
> way I could translate while being offline.
Ooops, I really should read-ahead! If you really want to edit raw data
then it can be arranged. Let's arrange that when the static stuff is
finished.
> My plan is to start by translating the files in
> portal/template/en. Who
> will add them to CVS ?
Whoever is available at the time, but most likely either me, Robert or
Magnus.
Regards, Dave.
