Subject:More on invalid characters Author:Junior Klegseth Date:07 Jun 2006 06:09 PM
I have seen various discussions on invalid characters but nothing clear on how to handle them and/or if Stylus will be addressing them. And I wonder why the XML generated internally to Stylus, when previewed on the internal IE browser, shows up fine, but the same text copied and pasted to a new document and previewed does not. This would seem problematic for anyone developing code for use outside of Stylus.
I am using SQL Server 2000, sp4. To see a simple example, use Northwind and use this select:
FROM Northwind.dbo.Customers t
A truncated sample of the output shows my point:
<?xml version='1.0' encoding='UTF-8'?>
<row><CompanyName>Ana Trujillo Emparedados y helados</CompanyName></row>
<row><CompanyName>Antonio Moreno Taquería</CompanyName></row>
<row><CompanyName>Around the Horn</CompanyName></row>
Copy and paste that into Stylus and preview--no problem. Copy and paste into Notepad, save as XML, and open in IE and you get: "An invalid character was found in text content."
Subject:More on invalid characters Author:Minollo I. Date:07 Jun 2006 08:38 PM
The problem is that saving that fragment from notepad will save it in ANSI encoding by default; but the XML PI declares that the encoding is UTF-8. You will need to instruct notepad (or any other editor) to save it in UTF-8 if you want that fragment to be properly interpreted.
Stylus Studio automatically saves XML documents using the encoding information specified in the XML PI.