Is there a bug in xsl:character-map?

classic Classic list List threaded Threaded
10 messages Options
Reply | Threaded
Open this post in threaded view
|

Is there a bug in xsl:character-map?

Stefan Wachter
Hi all,

I try to translate certain unicode characters that Internet Explorer
does not understand into corresponding span elements. For that means I
use the following character map:

  <xsl:character-map name="html-character-map">
    <xsl:output-character character="&#x2002;" string="&lt;span
class=&quot;x2002&quot;&gt;&lt;/span&gt;"/>
    <xsl:output-character character="&#x2003;" string="&lt;span
class=&quot;x2003&quot;&gt;&lt;/span&gt;"/>
    <xsl:output-character character="&#x2007;" string="&lt;span
class=&quot;x2007&quot;&gt;&lt;/span&gt;"/>
    <xsl:output-character character="&#x2009;" string="&lt;span
class=&quot;x2009&quot;&gt;&lt;/span&gt;"/>
    <xsl:output-character character="&#x200A;" string="&lt;span
class=&quot;x200A&quot;&gt;&lt;/span&gt;"/>
  </xsl:character-map>
 
Using this character map does not produce well-formed XML in case that
the output is indented and a line break occurs during the replacement
string. E.g. the input string (z.&#x2009;B. Reklameartikel) may result
in the following output:

(z.<span
                  class="x2009"&gt;&lt;/span&gt;B. Reklameartikel)

If the replacement string is not interrupted by a line break then it
works fine.

Does anyone know a workaround for this problem?

--Stefan



-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
saxon-help mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/saxon-help
Reply | Threaded
Open this post in threaded view
|

Re: Is there a bug in xsl:character-map?

Andrew Welch
> I try to translate certain unicode characters that Internet Explorer
> does not understand into corresponding span elements. For that means I
> use the following character map:
>
>   <xsl:character-map name="html-character-map">
>     <xsl:output-character character="&#x2002;" string="&lt;span
> class=&quot;x2002&quot;&gt;&lt;/span&gt;"/>
>     <xsl:output-character character="&#x2003;" string="&lt;span
> class=&quot;x2003&quot;&gt;&lt;/span&gt;"/>
>     <xsl:output-character character="&#x2007;" string="&lt;span
> class=&quot;x2007&quot;&gt;&lt;/span&gt;"/>
>     <xsl:output-character character="&#x2009;" string="&lt;span
> class=&quot;x2009&quot;&gt;&lt;/span&gt;"/>
>     <xsl:output-character character="&#x200A;" string="&lt;span
> class=&quot;x200A&quot;&gt;&lt;/span&gt;"/>
>   </xsl:character-map>
>
> Using this character map does not produce well-formed XML in case that
> the output is indented and a line break occurs during the replacement
> string. E.g. the input string (z.&#x2009;B. Reklameartikel) may result
> in the following output:
>
> (z.<span
>                   class="x2009"&gt;&lt;/span&gt;B. Reklameartikel)
>
> If the replacement string is not interrupted by a line break then it
> works fine.
>
> Does anyone know a workaround for this problem?

Isn't it just because the string attribute of <xsl:output-character is
split across two lines?  (or is that just in the email?)

Without fully understanding why IE doesn't understand the characters I
would replace using character-maps with a template that matches text()
and check for the characters in there, eg:

<xsl:template match="text()">
  <xsl:choose>
    <xsl:when test="contains(., somecharacter)">
      <xsl:call-template name="doReplace()">
         <xsl:with-param....
      </xsl:call-template>
    </xsl:when>
    <xsl:when test="....

and so on.

cheers
andrew


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
<a href="http://ads.osdn.com/?ad_idv37&alloc_id865&op=click">http://ads.osdn.com/?ad_idv37&alloc_id865&op=click
_______________________________________________
saxon-help mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/saxon-help
Reply | Threaded
Open this post in threaded view
|

Re: Is there a bug in xsl:character-map?

Stefan Wachter
Hi Andrew,

thanks for your reply. The character attribute is not split across lines
in my stylesheet. Email formatting is responsible for that.

A very simple way to fix the situation is to switch of indentation (as I
do at the moment). But this should be only a temporary solution. I fear
that your proposal may introduce a performance hit. In addition, if
there is a bug in xsl:character-map then I am confident that Michael Kay
will fix it soon.

--Stefan

PS: Internet-Explorer does not support the various kinds of Unicode
spaces and displays boxes instead of them.


andrew welch wrote:

>>I try to translate certain unicode characters that Internet Explorer
>>does not understand into corresponding span elements. For that means I
>>use the following character map:
>>
>>  <xsl:character-map name="html-character-map">
>>    <xsl:output-character character="&#x2002;" string="&lt;span
>>class=&quot;x2002&quot;&gt;&lt;/span&gt;"/>
>>    <xsl:output-character character="&#x2003;" string="&lt;span
>>class=&quot;x2003&quot;&gt;&lt;/span&gt;"/>
>>    <xsl:output-character character="&#x2007;" string="&lt;span
>>class=&quot;x2007&quot;&gt;&lt;/span&gt;"/>
>>    <xsl:output-character character="&#x2009;" string="&lt;span
>>class=&quot;x2009&quot;&gt;&lt;/span&gt;"/>
>>    <xsl:output-character character="&#x200A;" string="&lt;span
>>class=&quot;x200A&quot;&gt;&lt;/span&gt;"/>
>>  </xsl:character-map>
>>
>>Using this character map does not produce well-formed XML in case that
>>the output is indented and a line break occurs during the replacement
>>string. E.g. the input string (z.&#x2009;B. Reklameartikel) may result
>>in the following output:
>>
>>(z.<span
>>                  class="x2009"&gt;&lt;/span&gt;B. Reklameartikel)
>>
>>If the replacement string is not interrupted by a line break then it
>>works fine.
>>
>>Does anyone know a workaround for this problem?
>>    
>>
>
>Isn't it just because the string attribute of <xsl:output-character is
>split across two lines?  (or is that just in the email?)
>
>Without fully understanding why IE doesn't understand the characters I
>would replace using character-maps with a template that matches text()
>and check for the characters in there, eg:
>
><xsl:template match="text()">
>  <xsl:choose>
>    <xsl:when test="contains(., somecharacter)">
>      <xsl:call-template name="doReplace()">
>         <xsl:with-param....
>      </xsl:call-template>
>    </xsl:when>
>    <xsl:when test="....
>
>and so on.
>
>cheers
>andrew
>
>
>-------------------------------------------------------
>This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
>for problems?  Stop!  Download the new AJAX search engine that makes
>searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
><a href="http://ads.osdn.com/?ad_idv37&alloc_id865&op=click">http://ads.osdn.com/?ad_idv37&alloc_id865&op=click
>_______________________________________________
>saxon-help mailing list
>[hidden email]
>https://lists.sourceforge.net/lists/listinfo/saxon-help
>
>
>  
>



-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
saxon-help mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/saxon-help
Reply | Threaded
Open this post in threaded view
|

Re: Is there a bug in xsl:character-map?

Andrew Welch
> A very simple way to fix the situation is to switch of indentation (as I
> do at the moment). But this should be only a temporary solution. I fear
> that your proposal may introduce a performance hit. In addition, if
> there is a bug in xsl:character-map then I am confident that Michael Kay
> will fix it soon.
>
> --Stefan
>
> PS: Internet-Explorer does not support the various kinds of Unicode
> spaces and displays boxes instead of them.

Are you sure the font you are using contains glyphs for the characters
- a square box is often displayed for any characters not covered by
the font... re-reading your initial post you say everything is fine
without the line breaks so I'm guessing they are in the font.

As for the performance hit, it's considered good practice to get the
output you want first and then worry about performance later, as at
the moment you don't know whether it will be significant or not.

I remember reading that character-maps do slow things down because of
their output-wide nature (although I can't remember where I read that)
so you would have to measure the performance difference between the
two techniques before disregarding one.

If performance really is a problem, I would use an XMLFilter (instead
of character-maps) that sits between the XMLReader and the Transformer
that effectively marks up the text before the transform.  Then you
could just provide a  template to handle the markup you've generated
in the filter.

cheers
andrew


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
<a href="http://ads.osdn.com/?ad_idv37&alloc_id865&op=click">http://ads.osdn.com/?ad_idv37&alloc_id865&op=click
_______________________________________________
saxon-help mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/saxon-help
Reply | Threaded
Open this post in threaded view
|

RE: Is there a bug in xsl:character-map?

Michael Kay
In reply to this post by Stefan Wachter
Thanks for reporting it. I think I can see what's happening here: a subtle
interaction between three of the filters on the serialization pipeline. The
character map expander sets some bits that cause the HTMLEmitter to
effectively disable-output-escaping on the replacement string; but the
HTMLIndenter gets in the way and upsets this out-of-band communication. The
answer is for the HTMLIndenter not to break a line in the middle of such a
replacement string - the only difficulty is in the detail of how to achieve
that and more particularly how to test it.

Is it HTML or XHTML output, by the way?

Michael Kay
http://www.saxonica.com/ 


> -----Original Message-----
> From: [hidden email]
> [mailto:[hidden email]] On Behalf Of
> Stefan Wachter
> Sent: 19 December 2005 10:49
> To: [hidden email]
> Subject: [saxon] Is there a bug in xsl:character-map?
>
> Hi all,
>
> I try to translate certain unicode characters that Internet Explorer
> does not understand into corresponding span elements. For
> that means I
> use the following character map:
>
>   <xsl:character-map name="html-character-map">
>     <xsl:output-character character="&#x2002;" string="&lt;span
> class=&quot;x2002&quot;&gt;&lt;/span&gt;"/>
>     <xsl:output-character character="&#x2003;" string="&lt;span
> class=&quot;x2003&quot;&gt;&lt;/span&gt;"/>
>     <xsl:output-character character="&#x2007;" string="&lt;span
> class=&quot;x2007&quot;&gt;&lt;/span&gt;"/>
>     <xsl:output-character character="&#x2009;" string="&lt;span
> class=&quot;x2009&quot;&gt;&lt;/span&gt;"/>
>     <xsl:output-character character="&#x200A;" string="&lt;span
> class=&quot;x200A&quot;&gt;&lt;/span&gt;"/>
>   </xsl:character-map>
>  
> Using this character map does not produce well-formed XML in
> case that
> the output is indented and a line break occurs during the replacement
> string. E.g. the input string (z.&#x2009;B. Reklameartikel)
> may result
> in the following output:
>
> (z.<span
>                   class="x2009"&gt;&lt;/span&gt;B. Reklameartikel)
>
> If the replacement string is not interrupted by a line break then it
> works fine.
>
> Does anyone know a workaround for this problem?
>
> --Stefan
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep
> through log files
> for problems?  Stop!  Download the new AJAX search engine that makes
> searching your log files as easy as surfing the  web.  
> DOWNLOAD SPLUNK!
> http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
> _______________________________________________
> saxon-help mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/saxon-help
>




-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
saxon-help mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/saxon-help
Reply | Threaded
Open this post in threaded view
|

Re: Is there a bug in xsl:character-map?

David Carlisle

coincidentally I had a similar problem today.  My eol character map that
maps #10 to #13#10 failed to produce a DOS-flavoured output, when I
switched from xhtml to html output and used indent=yes as the indents
used #10 line ends. Turning off indentation and adding line breaks
explictly almost produces a DOS text file except for the DOCTYPE which
has #10 linebreaks before PUBLIC (but it turned out that for my
application (Microsofts html help compiler) this was OK and it is
sufficient (but necessary) to turn off indentation (otherwise the help
compiler silently goes off and eats 99% cpu until you kill it off)

David


________________________________________________________________________
This e-mail has been scanned for all viruses by Star. The
service is powered by MessageLabs. For more information on a proactive
anti-virus service working around the clock, around the globe, visit:
http://www.star.net.uk
________________________________________________________________________


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
saxon-help mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/saxon-help
Reply | Threaded
Open this post in threaded view
|

Re: Is there a bug in xsl:character-map?

Stefan Wachter
In reply to this post by Michael Kay
The output method was set to xhtml when watching this behaviour.

--Stefan

PS: Maybe you can fix the situation by changing the order of filters in
the serialization pipeline, i.e. first indentation, then
charactermapping, and finally emitting. Yet, I am not sure if this
breaks some specified XSLT behaviour.

PS2: A unit test could check for a very long replacement string not to
be split across lines.

Michael Kay wrote:

>Thanks for reporting it. I think I can see what's happening here: a subtle
>interaction between three of the filters on the serialization pipeline. The
>character map expander sets some bits that cause the HTMLEmitter to
>effectively disable-output-escaping on the replacement string; but the
>HTMLIndenter gets in the way and upsets this out-of-band communication. The
>answer is for the HTMLIndenter not to break a line in the middle of such a
>replacement string - the only difficulty is in the detail of how to achieve
>that and more particularly how to test it.
>
>Is it HTML or XHTML output, by the way?
>
>Michael Kay
>http://www.saxonica.com/ 
>
>
>  
>
>>-----Original Message-----
>>From: [hidden email]
>>[mailto:[hidden email]] On Behalf Of
>>Stefan Wachter
>>Sent: 19 December 2005 10:49
>>To: [hidden email]
>>Subject: [saxon] Is there a bug in xsl:character-map?
>>
>>Hi all,
>>
>>I try to translate certain unicode characters that Internet Explorer
>>does not understand into corresponding span elements. For
>>that means I
>>use the following character map:
>>
>>  <xsl:character-map name="html-character-map">
>>    <xsl:output-character character="&#x2002;" string="&lt;span
>>class=&quot;x2002&quot;&gt;&lt;/span&gt;"/>
>>    <xsl:output-character character="&#x2003;" string="&lt;span
>>class=&quot;x2003&quot;&gt;&lt;/span&gt;"/>
>>    <xsl:output-character character="&#x2007;" string="&lt;span
>>class=&quot;x2007&quot;&gt;&lt;/span&gt;"/>
>>    <xsl:output-character character="&#x2009;" string="&lt;span
>>class=&quot;x2009&quot;&gt;&lt;/span&gt;"/>
>>    <xsl:output-character character="&#x200A;" string="&lt;span
>>class=&quot;x200A&quot;&gt;&lt;/span&gt;"/>
>>  </xsl:character-map>
>>
>>Using this character map does not produce well-formed XML in
>>case that
>>the output is indented and a line break occurs during the replacement
>>string. E.g. the input string (z.&#x2009;B. Reklameartikel)
>>may result
>>in the following output:
>>
>>(z.<span
>>                  class="x2009"&gt;&lt;/span&gt;B. Reklameartikel)
>>
>>If the replacement string is not interrupted by a line break then it
>>works fine.
>>
>>Does anyone know a workaround for this problem?
>>
>>--Stefan
>>
>>
>>
>>-------------------------------------------------------
>>This SF.net email is sponsored by: Splunk Inc. Do you grep
>>through log files
>>for problems?  Stop!  Download the new AJAX search engine that makes
>>searching your log files as easy as surfing the  web.  
>>DOWNLOAD SPLUNK!
>>http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
>>_______________________________________________
>>saxon-help mailing list
>>[hidden email]
>>https://lists.sourceforge.net/lists/listinfo/saxon-help
>>
>>    
>>
>
>
>
>
>-------------------------------------------------------
>This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
>for problems?  Stop!  Download the new AJAX search engine that makes
>searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
>http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
>_______________________________________________
>saxon-help mailing list
>[hidden email]
>https://lists.sourceforge.net/lists/listinfo/saxon-help
>
>
>  
>



-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
saxon-help mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/saxon-help
Reply | Threaded
Open this post in threaded view
|

RE: Is there a bug in xsl:character-map?

Michael Kay
I've now reproduced the problem and I think I've fixed it, by the simple
expedient of having the indenter not split any text node that's been
subjected to character mapping.

Michael Kay
http://www.saxonica.com/ 

> -----Original Message-----
> From: [hidden email]
> [mailto:[hidden email]] On Behalf Of
> Stefan Wachter
> Sent: 20 December 2005 07:25
> To: [hidden email]
> Subject: Re: [saxon] Is there a bug in xsl:character-map?
>
> The output method was set to xhtml when watching this behaviour.
>
> --Stefan
>
> PS: Maybe you can fix the situation by changing the order of
> filters in
> the serialization pipeline, i.e. first indentation, then
> charactermapping, and finally emitting. Yet, I am not sure if this
> breaks some specified XSLT behaviour.
>
> PS2: A unit test could check for a very long replacement
> string not to
> be split across lines.
>
> Michael Kay wrote:
>
> >Thanks for reporting it. I think I can see what's happening
> here: a subtle
> >interaction between three of the filters on the
> serialization pipeline. The
> >character map expander sets some bits that cause the HTMLEmitter to
> >effectively disable-output-escaping on the replacement
> string; but the
> >HTMLIndenter gets in the way and upsets this out-of-band
> communication. The
> >answer is for the HTMLIndenter not to break a line in the
> middle of such a
> >replacement string - the only difficulty is in the detail of
> how to achieve
> >that and more particularly how to test it.
> >
> >Is it HTML or XHTML output, by the way?
> >
> >Michael Kay
> >http://www.saxonica.com/ 
> >
> >
> >  
> >
> >>-----Original Message-----
> >>From: [hidden email]
> >>[mailto:[hidden email]] On Behalf Of
> >>Stefan Wachter
> >>Sent: 19 December 2005 10:49
> >>To: [hidden email]
> >>Subject: [saxon] Is there a bug in xsl:character-map?
> >>
> >>Hi all,
> >>
> >>I try to translate certain unicode characters that Internet
> Explorer
> >>does not understand into corresponding span elements. For
> >>that means I
> >>use the following character map:
> >>
> >>  <xsl:character-map name="html-character-map">
> >>    <xsl:output-character character="&#x2002;" string="&lt;span
> >>class=&quot;x2002&quot;&gt;&lt;/span&gt;"/>
> >>    <xsl:output-character character="&#x2003;" string="&lt;span
> >>class=&quot;x2003&quot;&gt;&lt;/span&gt;"/>
> >>    <xsl:output-character character="&#x2007;" string="&lt;span
> >>class=&quot;x2007&quot;&gt;&lt;/span&gt;"/>
> >>    <xsl:output-character character="&#x2009;" string="&lt;span
> >>class=&quot;x2009&quot;&gt;&lt;/span&gt;"/>
> >>    <xsl:output-character character="&#x200A;" string="&lt;span
> >>class=&quot;x200A&quot;&gt;&lt;/span&gt;"/>
> >>  </xsl:character-map>
> >>
> >>Using this character map does not produce well-formed XML in
> >>case that
> >>the output is indented and a line break occurs during the
> replacement
> >>string. E.g. the input string (z.&#x2009;B. Reklameartikel)
> >>may result
> >>in the following output:
> >>
> >>(z.<span
> >>                  class="x2009"&gt;&lt;/span&gt;B. Reklameartikel)
> >>
> >>If the replacement string is not interrupted by a line
> break then it
> >>works fine.
> >>
> >>Does anyone know a workaround for this problem?
> >>
> >>--Stefan
> >>
> >>
> >>
> >>-------------------------------------------------------
> >>This SF.net email is sponsored by: Splunk Inc. Do you grep
> >>through log files
> >>for problems?  Stop!  Download the new AJAX search engine that makes
> >>searching your log files as easy as surfing the  web.  
> >>DOWNLOAD SPLUNK!
> >>http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
> >>_______________________________________________
> >>saxon-help mailing list
> >>[hidden email]
> >>https://lists.sourceforge.net/lists/listinfo/saxon-help
> >>
> >>    
> >>
> >
> >
> >
> >
> >-------------------------------------------------------
> >This SF.net email is sponsored by: Splunk Inc. Do you grep
> through log files
> >for problems?  Stop!  Download the new AJAX search engine that makes
> >searching your log files as easy as surfing the  web.  
> DOWNLOAD SPLUNK!
> >http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
> >_______________________________________________
> >saxon-help mailing list
> >[hidden email]
> >https://lists.sourceforge.net/lists/listinfo/saxon-help
> >
> >
> >  
> >
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep
> through log files
> for problems?  Stop!  Download the new AJAX search engine that makes
> searching your log files as easy as surfing the  web.  
> DOWNLOAD SPLUNK!
> http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
> _______________________________________________
> saxon-help mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/saxon-help
>




-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
saxon-help mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/saxon-help
Reply | Threaded
Open this post in threaded view
|

Re: Is there a bug in xsl:character-map?

Stefan Wachter
Thanks for the quick action! Is there already a date for the next Saxon
release?

--Stefan

Michael Kay wrote:

>I've now reproduced the problem and I think I've fixed it, by the simple
>expedient of having the indenter not split any text node that's been
>subjected to character mapping.
>
>Michael Kay
>http://www.saxonica.com/ 
>  
>



-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
saxon-help mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/saxon-help
Reply | Threaded
Open this post in threaded view
|

RE: Is there a bug in xsl:character-map?

Michael Kay
> Thanks for the quick action! Is there already a date for the
> next Saxon release?

No, I try to avoid fixing dates in advance. The code gets released when I
feel that it's ready. Sorry!

Michael Kay





-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
saxon-help mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/saxon-help