X-Original-To: pgsql-www-postgresql.org@localhost.postgresql.org
Received: from localhost (av.hub.org [200.46.204.144])
	by svr1.postgresql.org (Postfix) with ESMTP id DD73ED8A60;
	Thu,  3 Nov 2005 13:19:19 -0400 (AST)
Received: from svr1.postgresql.org ([200.46.204.71])
	by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024)
	with ESMTP id 81574-06; Thu,  3 Nov 2005 17:19:16 +0000 (GMT)
Received: from mx-2.sollentuna.net (mx-2.sollentuna.net [195.84.163.199])
	by svr1.postgresql.org (Postfix) with ESMTP id AAD6AD86B3;
	Thu,  3 Nov 2005 13:19:15 -0400 (AST)
Received: from ALGOL.sollentuna.se (janus.sollentuna.se [62.65.68.67])
	by mx-2.sollentuna.net (Postfix) with ESMTP
	id 7B91C8F292; Thu,  3 Nov 2005 18:19:13 +0100 (CET)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Subject: Re: Presskits for 8.1 Release
Date: Thu, 3 Nov 2005 18:19:13 +0100
Message-ID: <6BCB9D8A16AC4241919521715F4D8BCE6C7B5C@algol.sollentuna.se>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [pgsql-www] Presskits for 8.1 Release
thread-index: AcXgmZHnWk2+BrUoQ5a73OIDCfDwngAAAzmg
From: "Magnus Hagander" <mha@sollentuna.net>
To: "Josh Berkus" <josh@agliodbs.com>
Cc: <pgsql-www@postgresql.org>, <translators@postgresql.org>
X-Virus-Scanned: by amavisd-new at hub.org
X-Spam-Status: No, score=0.034 required=5 tests=[AWL=0.034]
X-Spam-Score: 0.034
X-Spam-Level: 
X-Archive-Number: 200511/21
X-Sequence-Number: 8736

> TRANSLATORS:  PLEASE see Magnus' comments below about bad=20
> encodings and missing parts of presskits.
>=20
> Magnus: the translators can (hopefully) fix the encoding issues.=20
> However, I don't know that they can fix the XHTML issues.  =20
> Can the web=20
> team do this somehow?

Not easily. We could probalby do it for languages like german, but for
languages like russian and japanese there's not telling how much we'd
break... I think it'd be much easier for the translators, considering
they have what's hopefully a readable template to work from (in the
english presskit)


> > In general, firefox doesn't like <a name=3D"foo"/>, for some=20
> reason - it=20
> > doesn't consider it closed. Needs to be <a name=3D"foo"></a>. =
Without=20
> > doing this, all paragraphs will be underlined when the mouse hovers=20
> > over them...
>=20
> I don't recall putting such a thing in.  How about a line number?

mha@developer:~/pgfoundry/press/pr/releases/8.1/en$ grep -n "<a name"
presskit81.html.en
16:<a name=3D"original_release" /><h2>Original Press Release</h2>
100:<a name=3D"additional_features" /><h2>Additional Features in this
Release</h2>
142:<a name=3D"quoted_companies" /><h2>Quoted Companies</h2>
164:<a name=3D"download" /><h2>Where to Download</h2>
177:<a name=3D"docs" /><h2>Documentation</h2>
187:<a name=3D"license" /><h2>License</h2>
201:<a name=3D"contact" /><h2>Contacts</h2>
215:<a name=3D"companies" /><h2>Corporate Support</h2>
228:<a name=3D"additional_software" /><h2>Links</h2>
279:<a name=3D"translations" /><h2>Official Translations of This



> > I also notice there is no header on the page - there was=20
> one for 8.0.
> > Was that really intentinoal?
> > (8.0 had <h1>PostgreSQL 8.0 Press Kit</h1>, 8.1 has only subheaders)
>=20
> Nope, it's because the header was added after the fact last=20
> year so I didn't have it in my template.  :-(  We can add it=20
> easily enough for English, but the others?

Oh. Yeah, you'd have to have each translator do it.


> > In the english list, this one is ilnked from "Greek", that=20
> seems wrong.
>=20
> Actually, it is Greek.  I got mixed up.

Ok.


> >>FR: French
> >=20
> >=20
> > There is no 8.1 file in cvs that I can find.
>=20
> Eh?  CVS error.  Will attempt to re-post.   Since CVS is=20
> giving me fits=20
> over the FR directory (it doesn't like it for some reason) I=20
> may have to drop French into the main directory.

Ok. We just copy it anyway, so that doesn't really matter.

> >>RO: Romanian
> >=20
> >=20
> > Not completed, has things like <link here> still in it in at least=20
> > four places.
>=20
> Ah.  Drop this one then.   I've not heard from the Romanian=20
> folks in a week.

Ok.


> >>RU: Russian
> >=20
> >=20
> > Not valid XHTML, and also has <link> stuff still in there. See=20
> >=20
> =
http://validator.w3.org/check?uri=3Dhttp%3A%2F%2Fmagnus-master.pgadmin.o
> > rg
> >=20
> =
%2Fabout%2Fpress%2Fpresskit81.html.ru&charset=3D%28detect+automatically%
> > 29
> > &doctype=3DInline&ss=3D1&verbose=3D1
>=20
> > Me too ;) But I can tell which are wrong by feeding them=20
> through the=20
> > XHTML validator at w3.org.
>=20
> I don't have the time or the knowledge to fix XHTML problems;=20
> that's my markup that you're having problems with and it=20
> represents the limit of my HTML know-how (I *did* post to=20
> this list asking for feedback before the translations=20
> started, but, whatever)  Can someone on the web team take this over?

Not sure - I certainly wouldn't go into doing russian etc on my own, as
I wouldn't know how to actually fix a lot of the things.


> > They can be converted with "iconv" if you know the source encoding,=20
> > though. But you need to know the source...
>=20
> > There is a list at the bottom of the page that refers to a=20
> whole lot=20
> > of languages that don't exist... Such as Greek, Hungarian, Italian,=20
> > Polish, Slovenian, Swedish, Turkish (may be more, didn't=20
> check carefully).
>=20
> Right.  I'm waiting to see which presskits are "OK" before=20
> revising that list.

Ok.


> > Seems to be perfect XHTML :-)=20
>=20
> Well, at least I got *something* right.

:-)

//Magnus