Date: Mon, 02 Feb 2004 23:46:10 +0900 (JST) From: Hiroki Sato <hrs@FreeBSD.org> To: ale@FreeBSD.org Cc: doc-committers@FreeBSD.org Subject: Re: cvs commit: www/en Makefile index.xsl navigation.xml www/share/mk web.site.mk www/share/sgml includes.misc.xsl Message-ID: <20040202.234610.59661525.hrs@eos.ocn.ne.jp> In-Reply-To: <401E554A.30707@FreeBSD.org> References: <200402010002.i1102wCF076490@repoman.freebsd.org> <20040202.223039.35473899.hrs@eos.ocn.ne.jp> <401E554A.30707@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
----Security_Multipart(Mon_Feb__2_23_46_10_2004_545)-- Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Alex Dupre <ale@FreeBSD.org> wrote in <401E554A.30707@FreeBSD.org>: ale> The problem is that localized web sites often have a mixture of $base ale> and $enbase path, so they should maintain their own navigation.xml in ale> any case...setting a default of $base is not a solution, since a new ale> link may point to a non-existant localized page (and having broken links ale> in home page is not good). Hmmm, is it enough that an item (label and URL) can be overridden accordingly? I think localization can be archived using language-independent navigation.xml and optional, localized one (not that the localized one should be removed completely). The localized one is used to override items in the language-independent one, so two of the $base are different from each other (resolved independently) and no broken link can appear; it should likely a link to an English contents. If using the localized one only, modification to includes.misc.xsl easily breaks the build. This is what I learned from the advisories.xml case. ale> > By the way, I am working on making new, not-translated items in ale> > news.xml appear in the localized www page in English. I think ale> > this sort of changes help the translation teams and the readers ale> > because the translation tends to get behind. Comments? ale> ale> We (italian) directly link the engligh news for this reason (no ale> translation of news), so the important thing is that this will continue ale> to work. No problem. This simply looks up both of en/news/news.xml and <lang>/news/news.xml, and an item in the English version is overridden if the translation is available. If no translation is available, the English item is used as it is. It should not break the current structure, and this way can be applied to navigation.xml. -- | Hiroki SATO ----Security_Multipart(Mon_Feb__2_23_46_10_2004_545)-- Content-Type: application/pgp-signature Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (FreeBSD) iD8DBQBAHmKyTyzT2CeTzy0RAsyoAJ9UHPvMGAonle1rJB303JAvqqpRIACeINaO 8jJ1ABHlWNiAqnbIl7HDSBo= =FNDz -----END PGP SIGNATURE----- ----Security_Multipart(Mon_Feb__2_23_46_10_2004_545)----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040202.234610.59661525.hrs>