Date: Thu, 01 Dec 2005 11:30:30 +0100 From: Pav Lucistnik <pav@FreeBSD.org> To: Hiroki Sato <hrs@FreeBSD.org> Cc: doc-committers@FreeBSD.org, cvs-doc@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: www/share/sgml templates.usergroups.xsl Message-ID: <1133433030.95515.19.camel@pav.hide.vol.cz> In-Reply-To: <20051201.192325.78702563.hrs@allbsd.org> References: <200511302135.jAULZM4m074043@repoman.freebsd.org> <20051201.135349.07646153.hrs@allbsd.org> <1133426754.95515.7.camel@pav.hide.vol.cz> <20051201.192325.78702563.hrs@allbsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--=-UEsZEGyl727IqQh0eLKo Content-Type: text/plain; charset=ISO8859-2 Content-Transfer-Encoding: quoted-printable Hiroki Sato p=ED=B9e v =E8t 01. 12. 2005 v 19:23 +0900: > Pav Lucistnik <pav@FreeBSD.org> wrote > in <1133426754.95515.7.camel@pav.hide.vol.cz>: >=20 > pa> Right, haven't noticed this. Do we have a language-dependent place fo= r > pa> this? Does xsltproc have commandline argument to specify encoding > pa> perhaps? Or do we have to copy the .xsl around? >=20 > Please put en/share/sgml/templates.usergroups.xsl. See: >=20 > http://www.freebsd.org/cgi/cvsweb.cgi/www/ja/share/sgml/templates.userg= roups.xsl?rev=3D1.1&content-type=3Dtext/x-cvsweb-markup This looks to me as an unneeded duplication of code. Plus we hardcode iso8859-1 in share/sgml/ already (see includes.header.xsl) so why bother here? > pa> > And your commits seem inconsistent; changes for www/89380 replace > pa> > &#xxx; with &foo;, but entities.dtd adds such entities in &#xxx; f= orm. > pa> > Which one do you think better? > pa> > pa> Whatever is easier to read and write by humans. &foo;s clearly wins. >=20 > This is not only a style issue. What we must consider is that > the &#xxx; form can depend on a specific encoding (this is always > UTF-8 in the XML spec, though) and some web browsers do not handle > them correctly. The entity references should be &foo; form > in the *resulting* HTML files wherever possible. That would be best, agreed. But I wasn't able to achieve this with our existing xsltproc infrastructure. > I think a concept of "sdata-as-pis" used in osx(1) is a good > idea for XML files in our www and doc tree. Redefining all > of ISO 8859 entities in the SDATA PI form and adding a template > for that, we can put them in the resulting HTML files > in the &foo; form. That would be best. I have no idea what "sdata-as-pis" or osx(1) is, so, would you please prepare this infrastructure? --=20 Pav Lucistnik <pav@oook.cz> <pav@FreeBSD.org> Maybe I should go ask that elvish wizard standing over there (YES A REAL ELF IS STANDING IN MY ROOM!), he should be able to tell me. --=-UEsZEGyl727IqQh0eLKo Content-Type: application/pgp-signature; name=signature.asc Content-Description: Toto je =?iso-8859-2?Q?digit=E1ln=EC?= =?ISO-8859-1?Q?_podepsan=E1?= =?iso-8859-2?Q?_=E8=E1st?= =?ISO-8859-1?Q?_zpr=E1vy?= -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQBDjtDGntdYP8FOsoIRAvj+AKDINZ5Xu6K85cE58MMAq/qSaiPB0wCg0ERj CEbAlC9/GTUYI0A3JW10mzU= =tF6T -----END PGP SIGNATURE----- --=-UEsZEGyl727IqQh0eLKo--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1133433030.95515.19.camel>