- From: Reece Dunn <msclrhd@hotmail.com>
- Date: Fri, 14 Mar 2003 16:29:54 +0000
- To: davidc@nag.co.uk
- Cc: www-math@w3.org
>Note there is some font and font-encoding information in unicode.xml >which is used as the source for most of the character information >in MathML, you may be able to generate information from there. I have had a brief look at this file, and will look at it more closely. >It looks to me as if the use-of node-set is in error (as well as making >it non portable) node-set is for converting result-tree-fragments to >node-sets but your unicode variable is defined by > <xsl:variable name = "unicode" select = "... >so is already a node set. So you just want > > <xsl:variable name = "u" select = $unicode[@value=$y]"/> I'll look into that: thanks. >It would be simpler to have just defined your table to be an xml >file included with document() I think, rather than as a collection of >xsl files that contain no xsl instructions? I shall update the unicode mappings to do this: it makes more sense >Also in general you can't use characters to denote font positions, as in > ... They are like that, its just the e-mailer/archiver has converted the text. This is what they should be like: <unicode:entry ver = "3.0" value = "&#x22C3;" font = "MS Mincho">&#x22C3;</unicode:entry> <!-- n-ary union --> Thank you for your comments and suggestions. -rhd- mailto:msclrhd@hotmail.com _________________________________________________________________ Chat online in real time with MSN Messenger http://messenger.msn.co.uk
Received on Friday, 14 March 2003 11:30:01 UTC