XML Editor
Sign up for a WebBoard account Sign Up Keyword Search Search More Options... Options
Chat Rooms Chat Help Help News News Log in to WebBoard Log in Not Logged in
Show tree view Topic
Topic Page 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 Go to previous topicPrev TopicGo to next topicNext Topic
Postnext
Tucker PathSubject: Custom validation output
Author: Tucker Path
Date: 04 Feb 2005 06:22 AM
Does StylusStudio require custom validation engines to output in a specific character encoding?

When I use a custom validation engine and its output contains Asian characters, they are mangled in the output window. (See attached)
This happens on all custom validation engines and doesn't happen on the built-in validator.

Regards,


Imageoutput.png
output

Postnext
Tucker PathSubject: Custom validation output
Author: Tucker Path
Date: 05 Feb 2005 04:22 AM
I tried ANSI, UTF-8 and UTF-16 by filtering the output of validation engines within a batch file.
All didn't help.
So I have no idea what character encoding does Stylus Studio expect...

Postnext
Tucker PathSubject: Custom validation output
Author: Tucker Path
Date: 09 Feb 2005 12:37 AM
Note that the specification clearly allows non Western tag names.
http://www.w3.org/TR/2004/REC-xml-20040204/#sec-common-syn

However, they are not seen correctly in Stylus Studio validation output window.
This makes Stylus Studio almost useless with such XML files.

Postnext
Ivan PedruzziSubject: Custom validation output
Author: Ivan Pedruzzi
Date: 09 Feb 2005 01:47 AM
>Note that the specification
>clearly allows non Western tag
>names.
>http://www.w3.org/TR/2004/REC-
>xml-20040204/#sec-common-syn
>

Tucker,

the XML 1.0 specs is totaly unrelated to this problem
and the XML document encoding is also unrelated.

Your schema validator is generating a stream of bytes to the
standard output using some particual encoding; the output window reads
from the standard output expecting UTF8.

Please post an example of output file using a command like the following

XmlValidator myxml.xm > result.txt

Ivan



using a particular encoding




>However, they are not seen
>correctly in Stylus Studio
>validation output window.
>This makes Stylus Studio
>almost useless with such XML
>files.

Postnext
Tucker PathSubject: Custom validation output
Author: Tucker Path
Date: 09 Feb 2005 03:14 AM
>Your schema validator is
>generating a stream of bytes
>to the
>standard output using some
>particual encoding;

Well, I'm using only the custom validation engines shipped with Stylus Studio.

Attached are the examples.
Validate TEXT.XML using MSXML4.0 DOM Parser, .NET XML Parser, Xerces-J or XSV shipped with Stylus Studio.
You'll see broken tag names in the output window even if a Japanese font is installed. See TEST.PNG.

>the output
>window reads
>from the standard output
>expecting UTF8.

I'm afraid it doesn't seem true.
Register this custom validation engine. (useless, just for testing purposes)
Command: ${StylusStudio}\msxsl.exe
Arguments: ${FilePath} ${FileDir}\TEST.XSL

It produces UTF-8, but the output window cannot display it.


Documenttest(5).xml

Postnext
Tucker PathSubject: Custom validation output
Author: Tucker Path
Date: 09 Feb 2005 03:17 AM


Imagetest.png


Documenttest(9).xsl


Documenttest(1).xsd

Postnext
Alberto MassariSubject: Custom validation output
Author: Alberto Massari
Date: 09 Feb 2005 09:59 AM
Hi Tucker,
yes, the statement about the custom validator wrapper expecting UTF-8
output is not correct; it assumes that the output is encoded in the
code page of Windows. So, you should be able to see the same characters
you see if you run the validator command line inside a cmd.exe console.

Could you please open a console window, run this command line and post the
results on this forum?

cd "c:\Program Files\Stylus Studio XML Professional Edition\bin"
java -cp xml-apis.jar;xercesImpl.jar;"Custom ValidationEngines\Xerces_J\XercesValidator.jar" com.progress.stylus.XercesValidator c:\TEMP\test.xml

Thanks,
Alberto

Postnext
Tucker PathSubject: Custom validation output
Author: Tucker Path
Date: 09 Feb 2005 11:50 AM
Here's the output in the command prompt.
It's encoded in code page 932 (Japanese) which matches my user and system locale.
The command prompt and Notepad displays it correctly. However, Stylus Studio output window doesn't.

I think you're able to reproduce this problem locally on English (or any language of) Windows, if you install Japanese language pack and change the user and system locale to Japanese.

To install a language pack on Windows 2000:
1. In Control Panel, double-click Regional Options, then click the General tab.
2. In the Language settings for the system box, select the check box next to the language group you want to install.

To change the user locale on Windows 2000:
1. In Control Panel, double-click Regional Options, and click the General tab.
2. Select the user locale you want.

To change the system locale on Windows 2000:
1. In Control Panel, double-click Regional Options, then click the General tab.
Click Set default.
2. Select the system locale and click OK.


Imagetest_xerces.png


Documenttext_xerces.txt

Postnext
Alberto MassariSubject: Custom validation output
Author: Alberto Massari
Date: 10 Feb 2005 03:30 AM
Hi Tucker,
you are right; it turns out that a couple of Microsoft APIs don't work
as advertized, and don't perform the MBCS->Unicode conversion when
invoked from a Unicode application.
We have changed Stylus so that it doesn't rely on those APIs anymore; the
fix will be available in the next update.

Thanks for reporting this bug,
Alberto

Postnext
Tucker PathSubject: Custom validation output
Author: Tucker Path
Date: 10 Feb 2005 03:48 AM
>it turns out that a couple
>of Microsoft APIs don't work
>as advertized, and don't
>perform the MBCS->Unicode
>conversion when
>invoked from a Unicode
>application.

Interesting.

>the fix will be available in the
>next update.

Great. Thank you!

Posttop
Tucker PathSubject: Custom validation output
Author: Tucker Path
Date: 14 Feb 2005 05:06 AM
Now it's fixed on V6.1.287h.
I'm very happy with it. Thank you for your support.

The only problem is XSV whose output is UTF-8 while the other validators employ the current code page.
But I'm able to work around it by converting it to the current code page within a batch file.

 
Topic Page 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 Go to previous topicPrev TopicGo to next topicNext Topic
Download A Free Trial of Stylus Studio 6 XML Professional Edition Today! Powered by Stylus Studio, the world's leading XML IDE for XML, XSLT, XQuery, XML Schema, DTD, XPath, WSDL, XHTML, SQL/XML, and XML Mapping!  
go

Log In Options

Site Map | Privacy Policy | Terms of Use | Trademarks
Stylus Scoop XML Newsletter:
W3C Member
Stylus Studio® and DataDirect XQuery ™are from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2016 All Rights Reserved.