Subject: RE: [xsl] Understanding XSLT Questions From: George James <GeorgeJ@xxxxxxxxxxxxxxx> Date: Mon, 13 Dec 2004 15:23:27 -0000 |
Tommie You are right - it was remiss of me to post my questions like that. I'll pay attention to my titles and post each question separately in future. Many thanks, btw, for hosting this list and for maintaining the quality by running a tight ship. Regards George George James Software www.georgejames.com An InterSystems Technology Partner > -----Original Message----- > From: Mulberry Technologies List Owner > [mailto:xsl-list-owner@xxxxxxxxxxxxxxxxxxxxxx] > Sent: 13 December 2004 15:03 > To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx > Subject: Re: [xsl] Understanding XSLT Questions > > > Questions that arise in other discussions, such as > www.understandingxslt.com are welcome on XSL-List. However, I > would prefer that they were posed in a way that made them a > useful part of the XSL-List archive. > > So, I would have preferred that this posting were 3 separate > messages, each with a subject line that described the subject > of the question. That way people searching the XSL-List > archive are more likely to find this information, and to > think it is relevant to their question. Instead of: > "Understanding XSLT Questions", your subject lines might have been: > - poor string handling in XSLT 1.0 > - Firefox rendering document with invalid character > - documentation for Transformiix XSLT engine > > Nothing exciting here, but far better pointers to the content. > > Thanks for using better subject lines on XSL-List in the future. > > -- Tommie > > > >Over on www.understandingxslt.com we are working through Jeni > >Tennison's Beginning XSLT book. > > > >A number of questions have come up and not been answered. We're all > >relative newbies over there so there's nobody to provide > authoratative > >answers to these questions. > > > >I'm just wondering if anyone here can answer any of them: > > > >1 Why does XSLT 1.0 have relatively poor string handling > capabilities? > > > >2 When attempting to view an XML document that contains an invalid > >character (for the encoding) in IE it complains that the XML > document > >is invalid and displays nothing. However in Firefox the document is > >rendered but the character is shown as a black diamond containing a > >question mark. Shouldn't Firefox reject the document? > > > >3 Where's the documentation for the Transformiix XSLT > engine that's > >embedded in Firefox? What extensions are supported? Is it > scriptable, > >etc? Most links seem to point to the Netscape DevEdge site > which is no > >longer there. > > > >Any views or comments would much appreciated. > > > > > >Regards > >George > > > >George James Software > >www.georgejames.com > >An InterSystems Technology Partner > > > -- > ====================================================================== > B. Tommie Usdin mailto:btusdin@xxxxxxxxxxxxxxxx > Mulberry Technologies, Inc. > http://www.mulberrytech.com > 17 West Jefferson Street Phone: 301/315-9631 > Suite 207 Direct Line: 301/315-9634 > Rockville, MD 20850 Fax: 301/315-8285 > ---------------------------------------------------------------------- > Mulberry Technologies: A Consultancy Specializing in XML > and SGML > ======================================================================
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
RE: [xsl] Understanding XSLT Questi, Michael Kay | Thread | [xsl] Tokenizing and special charac, michella |
Re: [xsl] Understanding XSLT Questi, Mulberry Technologie | Date | [xsl] Using Saxon with Java, Colin Toal |
Month |