but saxon should support the unicode representation of extended characters, shouldn't it?
and according to my unicode table   is equivalent to regards daniel s. haischt -- > -----Ursprungliche Nachricht----- > Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] > Gesendet: Freitag, 4. Oktober 2002 21:40 > An: Daniel S. Haischt; [EMAIL PROTECTED] > Betreff: Re: DOCBOOK-APPS: [QUESTION] translating whitespaces into > > > > On Fri, Oct 04, 2002 at 01:31:56PM +0200, Daniel S. Haischt wrote: > > hello, > > > > this question might be likly off-topic... > > > > i am having a stylesheets that produces some > > HTML output (taking a website xml file as input). > > > > sometimes i'll like to translate every whitespace > > that occures in a plain text string into > > > > example: > > > > ----------8<-----------8<-----------8<---------- > > This is a foobar sentence. > > > > sould be translated into: > > > > This is a foobar sentence. > > ---------->8----------->8----------->8---------- > > > > i used the XSLT translate() function to accomplish > > this. > > > > translate('This is a foobar sentence.', ' ', ' ') > > > > unfortunatly this does not produce the desired result. > > so how is it possible to translate whitespaces into > > ? > > Hmm, when I do this translation with Saxon, it works and > produces in the output. When I do it with xsltproc, > I just get plain spaces. When I use a different character > such as ¡ I get an inverted ! as expected, This means > the translation is working, it just isn't outputting > for  . > > Further investigation shows that the Saxon processor > outputs HTML entities for other characters, when they > are defined. Saxon outputs ¡ for ¡, while > xsltproc outputs the octal character in > the character set. > -- > > Bob Stayton 400 Encinal Street > Publications Architect Santa Cruz, CA 95060 > Technical Publications voice: (831) 427-7796 > Caldera International, Inc. fax: (831) 429-1887 > email: [EMAIL PROTECTED] > > >