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
Conferences Close Tree View
+ Stylus Studio Feature Requests (1192)
+ Stylus Studio Technical Forum (14621)
+ Website Feedback (249)
- XSLT Help and Discussion (7625)
-> + Flatten an XML source (2)
-> + Problem in navigating tree (2)
-> + preserve line breaks in xml at... (4)
-> + XSLT to PDF (2)
-> + Replace a nodeset with another... (3)
-> + Nested variable compile error ... (5)
-> + Replace a nodeset with another... (2)
-> + StackOverFlow Error, while com... (4)
-> + Footnote - WORDML (6)
-> + Concatenate same input element... (3)
-> + Need to remove the sub element... (3)
-> + Grabbing sub-namespace values (2)
-> + Converting date via browser XS... (4)
-> + Selecting Attribute nodes (2)
-> + XSLT totaling numeric values (4)
-> + Two line output by breaking on... (3)
-> + Encoding Option for base64Bina... (2)
-> + using document and web service... (2)
-> + XSLT transformations with JDK1... (8)
-> - Parsing Excel XML - Selectiing... (1)
-> + Grouping this xml input very n... (2)
-> + XSL-FO page-sequence and blank... (2)
-> + Need Help In XSLT Mapping (3)
-> + how to create the Tables by co... (2)
-> + fo:external-graphic - Image ... (2)
-> + Mapping complex document with ... (8)
-> + Sorting in XSLT (2)
-> + xsl date time adding... (16)
-> - Flat XML to nested XML convers... (1)
-> + parser for parsing XSL file (2)
-> - q on group function (1)
-> + compare 2 date value using xsl (2)
-> - Remove namespaces from SOAP pa... (1)
-> + Numeric string not displaying ... (3)
-> + where is the old HTM to XSL wi... (2)
-> + XSLT variable path (2)
-> + Sort by lookup values & styles... (2)
-> + Hi without hard code filed na... (2)
-> + XSLT output does not work (2)
-> + How can I do this javascript i... (2)
-> + Paging with XSL and passing UR... (2)
-> + XPath Condition Query (3)
-> + Xalan Multiple XML Output Over... (3)
-> + Inserting Line Break (2)
-> + Get Value from non-standard xm... (2)
-> + Root node renaming and adding ... (2)
-> + Cannot get CDATA to render pro... (2)
-> - How to add a footer on reports... (1)
-> - Apply-templates and processing... (1)
-> + Help Please - Use data from no... (5)
-> - Behaviour of trace function (1)
-> + How to Build a Dynamic XPath E... (3)
-> - raw xml to generic xml (1)
-> - Merging two documents (1)
-> + XSLT Path help (3)
-> + how to sort, dates in xsl ? (3)
-> + Naming elements (3)
-> + XSL IF Statement (2)
-> + XSLT Help Needed (4)
-> + Character Increment (4)
-> - concat function not working wi... (1)
-> + XSLT only namespace attribute ... (2)
-> - using uri within RSS enclosure... (1)
-> + Transforming Data With XSLT (3)
-> + Validate XPath on variable (8)
-> - flatten xml structure then sor... (1)
-> + SYNTAX not working (2)
-> + Looping through xml document (3)
-> + can i modify the xml data in X... (2)
-> + can i modify the xml data in X... (2)
-> + regex (2)
-> + xslt document and web services... (2)
-> + looping question (2)
-> + XML to Excel Conversion using ... (4)
-> + Compare (2)
-> + problem in loadxml function (2)
-> + does IE support script in xsl (2)
-> + converting Time format (2)
-> + Single Message split into Mult... (5)
-> + xml template design (2)
-> + String to array (2)
-> + Page Break with XSL-FO (4)
-> + Need help Translating string (2)
-> + Transforming input xml paramet... (3)
-> + How to transform node from inc... (2)
-> + XSL:FO Marker Question (2)
-> + trim after character...? (2)
-> + Convernting CSS + xsl to XSL:F... (2)
-> + save external image in xml/xsl (3)
-> + Table of Contents (2)
-> + Problem with select expression (2)
-> + Slow for-each select (7)
-> + Restructuring XML (2)
-> + Coloring xml output (3)
-> + Looping through xsl based on a... (5)
-> + Where is the wizard? (3)
-> + Save XML thru href (2)
-> + existing xslt, source and dest... (5)
-> + spliting xml files by certain ... (8)
-> + checking condition and writing... (2)
-- Previous [481-500] [501-520] [521-540] Next
+ XQuery Help and Discussion (2016)
+ Stylus Studio FAQs (159)
+ Stylus Studio Code Samples & Utilities (364)
+ Stylus Studio Announcements (113)
Topic  
Postnext
lucrecia chiartanoSubject: encoding and entities for xml well-formedness
Author: lucrecia chiartano
Date: 09 Nov 2004 10:04 AM
Hello,
I would thank anyone who could help me with this pure-xml-topic.

As ampersand and less-than charcters are not allowed in a well-formed xml, they should be replaced with entities.
I looked for information on the w3.org site but am not sure to have understood it well.
What I have understood is that an entity can be constructed from the 'code-point' for the character to be replaced in three ways :
- &#x[hexadecimal-code-point];
- &#[decimal-code-point];
- &[entity-name];
I think I have understood also that for the first and second cases 'code-point' must be compatible with the xml-encoding-declaration of the same xml (<?xml encoding=""?>).
'Named entities' must be declared before use (for example in a dtd), but for four cases (&lt; , &gt; , &amp; , &apos;) that are somehow 'internally-declared'in the xml-processor.

Supposed I have well understood this, I still have not it clear if the four internally-declared 'named-entities' are encoding independent.
When I wirte it down on my xml they are always recognaized, whatever encoding I do declare in the xml-encodind-declaration, but I cannot say if it depends on the xml-processor I'm using.

That's all,
Hope I've been clear.

Thanks,

Lucrecia Chiartano

Postnext
(Deleted User) Subject: encoding and entities for xml well-formedness
Author: (Deleted User)
Date: 09 Nov 2004 11:58 AM
Hi Lucrecia,

>[...]
>I think I have understood also that for the first and second
>cases 'code-point' must be compatible with the
>xml-encoding-declaration of the same xml (<?xml
>encoding=""?>).

No, the code-point is the number that has been assigned to that
character in the Unicode specs, regardless of the encoding currently
being used in the XML file.

From § 4.1 of the XML specs:
"If the character reference begins with "&#x", the digits and letters
up to the terminating ; provide a hexadecimal representation of the
character's code point in ISO/IEC 10646"

where the ISO/IEC 10646 is the official name for the Unicode specs.

>'Named entities' must be declared before use (for
>example in a dtd), but for four cases (&lt; ,
>&gt; , &amp; , &apos;) that are somehow 'internally-declared'in the
>xml-processor.

The predefined entities are 5; there is also &quot;

In any case, both the character entities and the predefined ones are
encoding-independent.

Hope this helps,
Alberto

Postnext
lucrecia chiartanoSubject: encoding and entities for xml well-formedness
Author: lucrecia chiartano
Date: 10 Nov 2004 08:42 AM
So, am I reading the following in the wright way?

From § 4.3.3 of the XML specs:
...
Although an XML processor is required to read only entities in the UTF-8 and UTF-16 encodings, it is recognized that other encodings are used around the world, and it may be desired for XML processors to read entities that use them. In the absence of external character encoding information (such as MIME headers), parsed entities which are stored in an encoding other than UTF-8 or UTF-16 MUST begin with a text declaration (see 4.3.1 The Text Declaration) containing an encoding declaration:
....
--> from here I deduce that there exists two kinds of encoding declarations: one for xmls and one for entities.
UTF-8 and UTF-16 are somehow the entities-default-encoding-declarations, and that's why you said that entities are xml-encoding-declaration independent. Isn't it?

Then I can declare an ASCII encoding for the xml and use entities named by the UNICODE code-points also if that particular charcter exists not in the ASCII encoding.

The xml is still well-formed (I've tried it with Xerces and found no error, just the output contains the wrong character).
And there is no control from the encoding declaration over the xml text neither on entities used within it. Is it so?

Thanks a lot,

Lucrecia

Posttop
(Deleted User) Subject: Re: encoding and entities for xml well-formedness
Author: (Deleted User)
Date: 10 Nov 2004 09:10 AM
Hi Lucrecia,
the paragraph you are reading (§4.3.3) is about external entities,

that is, entities that require an external file to be imported in the XML.

The specs allow this external file to be in any encoding, provided that it

starts with the proper <?xml ... ?> header.
Character entities and entities like &myEnt; are internal
entities, and always use ISO 10646 as encoding.

Hope this helps,
Alberto


   
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.