Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: Re: Status update
Date: Mon, 8 Sep 2003 19:56:31 +0100
Message-ID: <03AF4E498C591348A42FC93DEA9661B844B5B4@mail.vale-housing.co.uk>
Thread-Topic: [pgsql-www] Status update
thread-index: AcN2JekWZskzZK/eSWW1oD8Af7lZAgAFHWSg
From: "Dave Page" <dpage@vale-housing.co.uk>
To: <webmaster@letzplay.de>, <pgsql-www@postgresql.org>


> -----Original Message-----
> From: Andreas Grabm=FCller [mailto:webmaster@letzplay.de]=20
> Sent: 08 September 2003 17:28
> To: Dave Page; webmaster@letzplay.de; pgsql-www@postgresql.org
> Subject: Re: [pgsql-www] Status update
>=20
>=20
> yes, the rebuildcache script is made to build the whole site.=20
> In my last test it has taken about one minute to rebuild=20
> everything except the documentation (which takes really long)=20
> in two languages. But I don't think it is necessary to=20
> rebuild the docs very often?

Currently the whole site is done hourly. It certainly doesn't have to be th=
at regular for the docs, though I think the front page should be to pick up=
 new events etc.

> I'm currently working on getting the new design working. As=20
> we have problems with the different length of the words in=20
> the different languages, I'm replacing the style=3D parts of=20
> the code with a class=3D and putting that formatting=20
> information into postgresql_en.css and postgresql_de.css so=20
> we can use different sizes for every language...

OK. What about a slight redesign to allow the wrapping to occur without mes=
sing up the formatting? Alternatively, Robert was looking at making a non-f=
ixed width version of the site which might solve this problem.

Regards, Dave.