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

[ESW Wiki] Update of "its0505ReqWhiteSpaces" by YvesSavourel

From: <w3t-archive+esw-wiki@w3.org>
Date: Wed, 14 Sep 2005 09:36:51 -0000
To: w3t-archive+esw-wiki@w3.org
Message-ID: <20050914093651.22086.24206@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 YvesSavourel:
http://esw.w3.org/topic/its0505ReqWhiteSpaces


------------------------------------------------------------------------------
  
  Author: Yves Savourel
  
+ 
  = Handling of White Spaces =
  
- === Summary ===
+ == Summary ==
  
  It must be possible to specify for a given element content how white spaces are to be handled (i.e. whether they are to preserve or collapsible).
  
  
- === Challenge/Issue ===
+ == Challenges ==
  
- Knowing whether the white spaces in a given element are collapsible or not is important for proper segmentation and matching when using computer assisted translation tools.
+ '''[[YS--''' Here is a new try for a description of the issues. ''']]'''
  
- The xml:space="preserve" attribute provides most likely a good solution for this requirement at the document instance level.
+ Knowing whether the white spaces in a given element (especially the line-breaks) are collapsible or not is important for proper segmentation and matching when using computer assisted translation tools.
  
- The whiteSpace constraint defined in the [http://www.w3.org/TR/xmlschema-2/#rf-whiteSpace XML Schema Part 2: Datatypes Second Edition] may be a good solution for this requirement at the schema level.
+ There are three main types of wrapped text:
  
- '''[[YS-''' How about the change above for the first comment? ''']]'''
+ 1. Text formatted for no special reasons:
  
- [[CL XSD [http://www.w3.org/TR/xmlschema-2/#rf-whiteSpace] might also be sth. to be looked at.
+ {{{<para>This is the first
+ sentence of the paragraph. It's followed
+ by a second sentence.</para>}}}
  
- "***"
+ 2. Text where line-breaks can be segment-breaks:
  
- XSL might also be sth. to be looked at. It not only provides a "preserve-space" but also a "strip-space".]]
+ {{{<data name="CMD_USAGE">
+  <value>Usage: po2xliff input[ options[ output]]
+ Where options are:
+    -trg : create target entries
+    -fill: fill the target entries with the source text</value>
+ </data>}}}
  
+ 3. Text intentionally pre-formatted for display constraints without regard for the linguistic aspects:
+ 
+ {{{<print witdh="75">Copyright (C) 2005 Okapi Framework Developers
+ 
+ This library is free software; you can redistribute it and/or modify it
+ under the terms of the GNU Lesser General Public License as published by
+ the Free Software Foundation; either version 2.1 of the License, or (at
+ your option) any later version.
+ 
+ This library is distributed in the hope that it will be useful, but
+ WITHOUT ANY WARRANTY; without even the implied warranty of
+ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU Lesser
+ General Public License for more details.
+ 
+ You should have received a copy of the GNU Lesser General Public License
+ along with this library; if not, write to the Free Software Foundation,
+ Inc., 59 Temple Place, Suite 330, Boston, MA  02111-1307 USA</print>}}}
+ 
+  * It is important for translation tools to make a difference between the first example (text can be collapsed safely) and the last two (text should not be collapsed).
+ 
+  * It is important for translation tools to have a way to address the differences between the two last examples (i.e. how line-breaks should be treated).
+ 
+  * The indication of whether white-spaces should be preserved or not should be accessible from the document itself, as defining the information at the rendering level (e.g. in a CSS style-sheet) may not be accessible for the translation tool.
+ 
+ 
- === Notes ===
+ == Notes ==
  
  There are case where the white space handling can be overriden at the style sheet level only, bypassing information withing the XML document itself: CSS allows the property 'white-space' (See [http://www.w3.org/TR/REC-CSS2/text.html#white-space-prop]).
  
@@ -42, +75 @@

  
  [[CL Should we possibly go for a general requirement (stated in the guidelines) along the lines of "canonicalize your XML" (see [http://www.w3.org/TR/2001/REC-xml-c14n-20010315#Example-WhitespaceInContent]).]]
  
+ 
+ == Quick Guidelines ==
+ 
+ The xml:space="preserve" attribute may provide a solution for some of these requirements at the document instance level.
+ 
+ '''[[YS--''' Not sure if it is important to be noted, but xml:space defines only "preserve" and "default", "default" not being necessarily "do-not-preserve". Do we have situations where "do-not-preserve" would be needed? ''']]'''
+ 
+ The whiteSpace constraint defined in the [http://www.w3.org/TR/xmlschema-2/#rf-whiteSpace XML Schema Part 2: Datatypes Second Edition] may provide a solution for these requirements at the schema level.
+ 
Received on Wednesday, 14 September 2005 15:58:49 GMT

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