Date: Sun, 25 Jan 2004 01:03:08 +0900 (JST) From: Hiroki Sato <hrs@eos.ocn.ne.jp> To: nectar@FreeBSD.org Cc: doc-committers@FreeBSD.org Subject: Re: cvs commit: www/share/sgml advisories.xml includes.misc.xsl Message-ID: <20040125.010308.55725942.hrs@eos.ocn.ne.jp> In-Reply-To: <20040124150623.GB96643@madman.celabo.org> References: <200401241210.i0OCA2jv028051@repoman.freebsd.org> <20040124150623.GB96643@madman.celabo.org>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --]
"Jacques A. Vidrine" <nectar@FreeBSD.org> wrote
in <20040124150623.GB96643@madman.celabo.org>:
nectar> On Sat, Jan 24, 2004 at 04:10:02AM -0800, Hiroki Sato wrote:
nectar> > hrs 2004/01/24 04:10:02 PST
nectar> >
nectar> > FreeBSD doc repository
nectar> >
nectar> > Modified files:
nectar> > share/sgml advisories.xml includes.misc.xsl
nectar> > Log:
nectar> > Add a workaround to prevent bogus link generation.
nectar> >
nectar> > Submitted by: ceri
nectar> >
nectar> > Revision Changes Path
nectar> > 1.150 +2 -2 www/share/sgml/advisories.xml
nectar> > 1.6 +15 -5 www/share/sgml/includes.misc.xsl
nectar>
nectar> That entry was only present as a work-around for a problem in
nectar> www/en/security/mkindex.xsl which you fixed on January 13. It should
nectar> now be removed, and this commit to includes.misc.xsl should probably
nectar> be backed out.
Ah, no, I backed out the removal and add omithref="yes" as an another
workaround because there are non-English versions of mkindex.xsl
which are not fixed. For en/security/mkindex.xsl it was fixed as
you pointed out, but at least {de,ru}/security/mkindex.xsl still
have this problem. Until they update their translation, the
bogus <advisory> line should not be removed.
I already moved the main part of mkindex.xsl to the language-independent
directory, so probably such a problem will not occur in the future.
Anyway, this is a typical problem of language-independent files
in language-dependent directories, I think. I can update the files
in question, but the respective translation teams should be responsible
for them....
I have not contacted them separately, but should I do so? I am
not sure who is responsible for which translation, though.
--
| Hiroki SATO
[-- Attachment #2 --]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (FreeBSD)
iD8DBQBAEpc8TyzT2CeTzy0RAt3qAJ9nTbBapsXgUIly55TaSC9RZMvXEwCeIVa3
lf5YV+fZYvaADSDdLcMPtt0=
=cKzE
-----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040125.010308.55725942.hrs>