They can normalize it in any way that pleases them, but
something similar to the above attribute value normalization is likely. Adding an
attribute xml:space=???preserve??? is one way to tell applications to keep their hands off
text in that element and its subelements. Even then, your spaces are not necessarily
safe: for example, the SVG speci?¬?cation states that with xml:space=???preserve??? all
white space characters are mapped to spaces, and leading and trailing white space is
removed. And remember that this is just the speci?¬?cation: individual SVG
applications may not necessarily follow it perfectly. Ah, the joys of having a simple
standard like XML that guarantees interoperability!
XML also has a way to mark text sections so they would ostensibly be completely
spared the attentions of parsers??™ normalizers and transformations. The text section must
be enclosed in a CDATA section by surrounding it with the underlined text below:
Within a CDATA section,&and
them, nor indeed are any of the normal character or entity references even recognised.
The only character sequence that cannot occur inside a CDATA section is ]]>. One
way to get around this problem is to split input containing that character sequence into
two CDATA sections.
Pages:
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531