--azLHFNyN32YCQGCU
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

As I understand, the scripts first read which are the current news on the
index.html files and then compare those news with the ones in changes.html
to see if there are old/new news.

If it works this way... why not simply forget what the page currently has
and then, read proper news from each language and copy them into index.html?

The other solution would be to use a db server... though this means,
obviously, installing a db server ;-). With a bit of php this should be
really easy.

Regards

On Mon, Jun 03, 2002 at 12:40:28PM -0400, Jan Schaumann wrote:
> All,
>=20
> I've been trying to find the Best Way to update index.html automatically
> from Changes/index.list and gallery/events.list while at the same time
> updating the translations websites *without* overwriting all existing
> (translated) news-entries on those index-pages.
>=20
> The problem is that we have to make a choice:
>=20
> (I) We always want to have the latest news on all index pages.  If that
> means that the news entries are in english even on the non-english
> sites, so be it.  At the same time, we also want to be able to
> re-generate the Changes/index.html file (possibly to correct spelling
> errors in the headlines) and automatically correct the entries on the
> various main pages.
>=20
> (II) We only want to add the latest News entries to the various main
> pages, preserving possibly already translated entries.  This means that
> if we encounter a spelling error in the headline and re-generate the
> news-entries, we'd end up with two entries for the same news:  they
> differ, and so they are treated as separate entries.  (Alternate
> scenario:  the headline with the error remains, but no duplicates are
> generated)
>=20
> Solution (I) is what we have in place, and the only problem with this is
> that for the translated news, the translators need to regenerate the
> entries by hand and paste them into the main page after an update to not
> loose the translated links.
>=20
> Solution (II) is what is attached in a different version of makeindex.sh
> and Makefile.
>=20
> As I write this, I believe it became obvious to me that we want to stick
> with (I) and translators have to deal with it.  But if you have other
> input (or even a third, better solution), let's discuss it.
>=20
> -Jan
>=20
> --=20
> http://www.netbsd.org -
>          Multiarchitecture OS, no hype required.

--=20
Of course it runs NetBSD - http://www.netbsd.org
HispaBSD member - http://www.hispabsd.org
Julio Merino <jmmv@hispabsd.org>

--azLHFNyN32YCQGCU
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (NetBSD)

iD8DBQE8+8hQzz00ZOPKycwRAjUYAJ9QClF+fUS3JIW/tdsnUD/13uMIBgCbBWY/
X5tLwIVIv2SRbqhj5Ky0i/g=
=tOFd
-----END PGP SIGNATURE-----

--azLHFNyN32YCQGCU--