>[EMAIL PROTECTED] wrote: >> What is with contributors.xml? >> http://marc.theaimsgroup.com/?l=ant-dev&m=115142496218295&w=2 >> > > >Good question and really the point of the email I sent >yesterday. This is what I can determine > >CONTRIBUTORS needs to be binary because it contains non-ASCII >character codes. The problem is that over its history it has >been broken many times due to different people using different >character encodings. > >AFAICT, the rationale for contributors.xml is that it allows >for an ascii representation of the contributors list, with >associated benefits. >Whatever we end up with, there should be one definitive list. >I see two possible courses of action > >1. maintain CONTRIBUTORS as binary and remove >contributors.xml. We need to agree and maintain a file >encoding - currently UTF-8 > >2. maintain contributors.xml and remove CONTRIBUTORS. In >builds, we could generate CONTRIBUTORS easily enough (or even >an HTML representation) > >What do you all think? >Conor
I would prefer the xml file - I dont think that there will be so many changes, that we can do the xml-overhead (over the plain list) by hand - we'll get semantic information (pre-/surname) - we'll have the correct spelling of names (German, French, ...) Jan <?xml version="1.0" encoding="ISO-8859-1"?> <xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"> <xsl:output indent="no" method="text" encoding="ISO-8859-1"/> <!-- the root node --> <xsl:template match="/contributors"> <xsl:value-of select="introduction"/> <xsl:apply-templates/> </xsl:template> <xsl:template match="name"> <xsl:value-of select="first"/> <xsl:text> </xsl:text> <xsl:if test="middle"> <xsl:value-of select="middle"/> <xsl:text> </xsl:text> </xsl:if> <xsl:value-of select="last"/> </xsl:template> <!-- dont copy the text and unmatched nodes as per default in xsl --> <xsl:template match="*"/> </xsl:stylesheet> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]