Subject:Re: rdbxml and external XSLT Processor Author:Minollo I. Date:20 May 2005 10:13 AM
you are using a fairly old version of Stylus Studio; we are not aware of the problem you are describing when using the latest 6.x packages. Can you try verifying that the behavior is correct downloading the latest available evaluation from http://www.stylusstudio.com/xml_download.html ?
>From: Ralf Altmeyer
>I'm using Stylus Studio 5.3 179l and face the following problem: I
>tried to create an xslt file that transforms from an rdbxml source
>(sequelink socket service with an excel file as data source) to some
>other XML. Since I want to use some custom extension I'd like to use
>external XSLT processor.
>However, I'm facing the problem that St.St. creates a temporary XML
>file from the rdbxml source that actually is encoded in UTF-16 but
>has UTF-8 in the prolog. Accordingly the external processor crashes
>with the messages "content not allowed in prolog".
>Also, any other XSLT processor than the build-in won't work with
>different error messages.
>However, if I open the rdbxml source in the xml editor, everything
>seems to be fine and st.st. seems to produce UTF-8.
>Is the described behavior a bug or do I something wrong?
>Any help is highly appreciated.