Pav Lucistnik <[EMAIL PROTECTED]> wrote
  in <[EMAIL PROTECTED]>:

pa> Hiroki Sato p$(Oz;(Be v $(OoU(B 01. 12. 2005 v 19:23 +0900:
pa> > Pav Lucistnik <[EMAIL PROTECTED]> wrote
pa> >   in <[EMAIL PROTECTED]>:
pa> >
pa> > pa> Right, haven't noticed this. Do we have a language-dependent place for
pa> > pa> this? Does xsltproc have commandline argument to specify encoding
pa> > pa> perhaps? Or do we have to copy the .xsl around?
pa> >
pa> >  Please put en/share/sgml/templates.usergroups.xsl.  See:
pa> >
pa> >   
http://www.freebsd.org/cgi/cvsweb.cgi/www/ja/share/sgml/templates.usergroups.xsl?rev=1.1&content-type=text/x-cvsweb-markup
pa>
pa> This looks to me as an unneeded duplication of code. Plus we hardcode
pa> iso8859-1 in share/sgml/ already (see includes.header.xsl) so why bother
pa> here?

 No, there is no <xsl:output> in includes.header.xsl and the output
 will be UTF-8 by default (when with no customization layer).

pa> >  I think a concept of "sdata-as-pis" used in osx(1) is a good
pa> >  idea for XML files in our www and doc tree.  Redefining all
pa> >  of ISO 8859 entities in the SDATA PI form and adding a template
pa> >  for that, we can put them in the resulting HTML files
pa> >  in the &foo; form.
pa>
pa> That would be best. I have no idea what "sdata-as-pis" or osx(1) is, so,
pa> would you please prepare this infrastructure?

 Okay.  I will do it within the year.

--
| Hiroki SATO

Attachment: pgpMivRM1UbDO.pgp
Description: PGP signature

Reply via email to