W3C home > Mailing lists > Public > public-i18n-its@w3.org > July to September 2005

[ESW Wiki] Update of "its0503ReqCDATA" by TimFoster

From: <w3t-archive+esw-wiki@w3.org>
Date: Tue, 13 Sep 2005 09:58:34 -0000
To: w3t-archive+esw-wiki@w3.org
Message-ID: <20050913095834.31256.93844@localhost.localdomain>
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "ESW Wiki" for change notification.

The following page has been changed by TimFoster:
http://esw.w3.org/topic/its0503ReqCDATA


The comment on the change is:
changed a lot of the contet, to fit the same model used in other pages

------------------------------------------------------------------------------
  = CDATA Section =
  
  
- == Description ==
+ == Summary ==
  
- CDATA sections in XML pose problems to translators and tools authors
- that are similar to the problems posed to other consumers of XML
- documents: that is, that it is impossible to know the intended use of
- the contents of a CDATA section. The use of CDATA sections in
- translatable XML files is strongly discouraged, as they prevent elements
- in the XML ITS from being used to mark up the localisable components of
- that section of text.
+ CDATA sections are discouraged, as their contents cannot easily be marked up 
+ by using elements from any proposed internationalization tag set.
+ 
+ == Challenges ==
+ 
+ For translators, and other document consumers, given any section of CDATA, 
+ it's difficult to know the intended use of the contents of a CDATA section.
+ 
+ The use of CDATA sections in translatable XML files is discouraged, as they
+ prevent any elements in a proposed XML internationalization tag set from being
+ used to mark up the localisable components of that section of text, although
+ the entire CDATA section could be wrapped in additional tags.
  
  In addition, numeric character references and entity references are not supported
  within CDATA sections, which could lead to a possible loss of data if the document
- is converted from one encoding to another where some characters in the CDATA sections
+ is converted from one encoding to another where some characters in
- are not supported.
+ the CDATA sections are not supported.
  
- == Background ==
+ 
+ == Notes ==
  
  There is a temptation to use CDATA sections in XML files to escape
  sections of text that contain characters which would otherwise be
@@ -37, +43 @@

  
  A commonly employed example of this has been seen where document authors
  attempt to easily produce an "XML version" of an input file by inserting
- CDATA sections around text which contains HTML markup. 
+ CDATA sections around text which contains HTML markup.
- Since these escaped sections cannot be marked up using the XML ITS, they must be
- examined manually to determine which sections contain translatable text,
- non-translatable text, etc. For tools authors, there is often no way to determine 
- the original format of the text inside the CDATA section (eg. was it HTML, RTF,
- a base64-encoded OpenOffice.org document etc.)
- These considerations can result in bottle-necks in
- translation processes while these manual steps are performed. 
  
+ Since the contents of these escaped sections cannot be marked up using the
+ XML ITS, they must be examined manually to determine which parts of the content
+ contain translatable text, non-translatable text, etc. For tools authors, there is often
+ no way to determine the original format of the text inside the CDATA section
+ (eg. was it HTML, RTF, a base64-encoded OpenOffice.org document etc.)
+ 
+ These considerations can result in bottle-necks in translation processes while these
+ manual steps are performed.
+ 
Received on Tuesday, 13 September 2005 16:17:12 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:12:45 GMT