XML Editor
Sign up for a WebBoard account Sign Up Keyword Search Search More Options... Options
search
Chat Rooms Chat Help Help News News Log in to WebBoard Log in Not Logged in
Home » Boards » Stylus Studio Developer Network » Stylus Studio Technical Forum » encoding='windows-1252'
Conferences Close Tree View
+ Stylus Studio Feature Requests (1192)
- Stylus Studio Technical Forum (14621)
-> - Stylus Studio - Registrar en o... (1)
-> + Stylus Studio - Registrar en o... (2)
-> + Can a pipeline send a file by ... (2)
-> + After Updateing WIN10 to WIN11... (12)
-> + Where do I add the custom java... (3)
-> + Where is the Diagram tab? (5)
-> + Applying XSLT to Word DOCX/XML (2)
-> - CSV conversion via ConvertToXM... (1)
-> + Text symbols in SS not same as... (4)
-> + Exposing xquery as webservice ... (6)
-> + Syntax Identifier (2)
-> + Saving a Converted XML as an X... (5)
-> + Output document cannot be pars... (4)
-> - Archiving output from conversi... (1)
-> + EDIFACT guideline from Stylus ... (3)
-> + CSV file putting all the data ... (5)
-> + Can't install Home version 64b... (5)
-> + presale - Can I covers this sc... (5)
-> + Problem with UNB (5)
-> + Splitting EDIFACT files pipeli... (4)
-- [1-20] [21-40] [41-60] Next
+ Website Feedback (249)
+ XSLT Help and Discussion (7625)
+ XQuery Help and Discussion (2017)
+ Stylus Studio FAQs (159)
+ Stylus Studio Code Samples & Utilities (364)
+ Stylus Studio Announcements (113)
Topic  
Postnext
Dominiek ChristiaensSubject: encoding='windows-1252'
Author: Dominiek Christiaens
Date: 16 Dec 1999 01:12 PM
In order to avoid processing problems with special characters containing umlauts and accents (like in German and French), I use the encoding="windows-1252".
This works fine within Internet Explorer 5, and calling the Microsoft.XMLDOM object, but when I activate the Internet Explorer Processor (Microsoft Syntax) within Stylus, the processor still considers these special characters as invalid. Is Stylus not using the "Microsoft.XMLDOM" object for processing?
Posttop
(Deleted User) Subject: encoding='windows-1252'
Author: (Deleted User)
Date: 16 Dec 1999 02:31 PM
The problem is that Stylus is not passing through the encoding attribute on your source xml. Since windows-1252 will automatically work using Stylus' native parser and processor, I suggest not working in Microsoft mode. If you need to use Microsoft syntax, however, here's a workaround:

1) Click the external browser button above the preview pane. Choose View | Source in the newly-created Internet Explorer window.

2) Copy the (?xml:stylehseet...) line, and paste it just below the (?xml ... ?) line in your original xml document.

3) Load your original xml document in Internet Explorer. It will be pointing to the temporary xsl file that Stylus generates, as well as having your original encoding pi.

This workaround will be unnecessary in the next version of Stylus.

--Alex
   
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.