----Security_Multipart(Mon_May_28_07_46_23_2007_042)--
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Pavel Cahyna <pavel@NetBSD.org> wrote
  in <20070527210754.GA744@beta.martani.repy.czf>:

pa> Hello,
pa>
pa> it occured to me that if we have the website generated from XML sources,
pa> we should use this fact in a smarter way. Information which is currently
pa> duplicated should be kept in only one place and inserted at the right
pa> place in the desired output format using XSLT.
pa>
pa> I have done a step in this direction. In the list of developers, a person
pa> may have <group> tags under his entry indicating to what groups (s)he
pa> belongs (see htdocs/People/developers.xml). Under
pa> htdocs/People/groups, there is a list of groups with their members.

 While I agree with that the direction is right, I think putting *.xsl
 file into share/xsl is better because duplicated .xsl/.xml files will
 be created by the translation teams.  When we use XML database, the
 stylesheet(s) should be reusable as much as possible among various
 languages and the language-independent part separated into a
 language-independent directory.

pa> In the future, I would like to convert the list of portmasters to a
pa> similar format and autogenerate the list in release notes from it instead
pa> of the src/distrib/notes/common/list-portmasters.pl script, which parses
pa> the resulting HTML. I am sure there are many other cases of duplicated
pa> information where a smarter approach using XSLT could help.

 Agreed.

--
| Hiroki SATO

----Security_Multipart(Mon_May_28_07_46_23_2007_042)--
Content-Type: application/pgp-signature
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (FreeBSD)

iD8DBQBGWgo/TyzT2CeTzy0RArO9AKClOzBObGdeKdtrEDrN/U+UW0mvdQCgwqww
U8qeeqcHU4LczWXAyD+do2Q=
=Wm/N
-----END PGP SIGNATURE-----

----Security_Multipart(Mon_May_28_07_46_23_2007_042)----