W3C home > Mailing lists > Public > public-i18n-its-ig@w3.org > October 2014

Re: [xliff] ITS: Preserve space and Language Information

From: Dr. David Filip <David.Filip@ul.ie>
Date: Thu, 23 Oct 2014 14:03:51 +0100
Message-ID: <CANw5LKnpK5Ka7k4c7S-1nj5cjUeHLZWcPXjZBjf4o8-kW7N_Sw@mail.gmail.com>
To: Yves Savourel <ysavourel@enlaso.com>
CC: XLIFF Main List <xliff@lists.oasis-open.org>, public-i18n-its-ig <public-i18n-its-ig@w3.org>
Thanks, Yves,

I was thinking about two possible solutions.
One of them would be as you propose to introduce its attributes that could
work with empty markers as span delimiters.

Another way would be to use the fact that the two relevant XML namespace
attributes are still available on <source> and <target>
Not sure if this is an omission, probably not as we have PR for
resegmentation accounting for that.

This would be somewhat restrictive but would have the advantage that the
related mark up would be always well formed

I tried to write up such restrictive solution for Preserve Space in the
Current Working draft.
It also notes that you can use originalData to preserve whitespace..

I copy paste it here:

Preserve Space
Indicates how to handle whitespace in a given content portion. See [ITS]
Preserve Space for details.
Structural Elements
 Whitespace handling at the structural level is indicated with xml:space in
XLIFF Core and extensions:
Extraction of preserved whitespace at the structural level

<listing xml:space='preserve'>Line 1
Line 2</listing>


<unit id='1' xml:space='preserve'>
  <source>Line 1
Line 2</source>

Inline Elements
 It is not possble to use [XML namespace] on XLIFF inline elements. It is
advised that mixed Preserve Space behavior is NOT used inline in source
formats. In case of extraction of source format inline elements with mixed
Preserve Space behavior, it is advised to extract all discernable portions
with uniform whitespace handling into different <unit> elements that can
have their whitespace handling set independently.
Whitespace handling can be also set independently for text segments and
ignorable text portions within an Extracted unit and for the source ad
target language within the same <segment> or <ignorable> element using the
optional xml:space attribute at the <source> and <target> elements.
However, mixed whitespace handling behavior is not likely to survive
Segmentation Modification. So this method is not advised unless the
<segment> elements are protected by the canResegment flag value set to or
inhrited as no.
Preserved whitespaces can be also extracted as original data stored outside
of the translatable content at the unit level and referenced from
placeholder codes. It is importnat to note that the value of the xml:space
attribute is restricted to preserve on the <data> element.
Extraction of preserved whitespaces as referenced original data

   <span xml:space='preserve'>Item 1      Item 2      Item n+1
   </span> are all used to build Item n+2.


<unit id='1'>
    <data id="d1">&lt;span xml:space='preserve'></data>
    <data id="d2">&lt;/span></data>
    <data id="d3">      </data>
    <data id="d4">
    <source><pc id="1" dataRefStart="d1" dataRefEnd="d2">Item 1<ph id="2"
dataRef="d3">Item 2<ph id="2" dataRef="d3">Item n+1<ph id="2"
dataRef="d4"></pc> are all used to build Item n+2.</source>

Not sure really which solution is better, but I'd say we should explore


Dr. David Filip
OASIS XLIFF TC Secretary, Editor, and Liaison Officer
University of Limerick, Ireland
telephone: +353-6120-2781
*cellphone: +353-86-0222-158*
facsimile: +353-6120-2734
mailto: david.filip@ul.ie

On Thu, Oct 23, 2014 at 1:41 PM, Yves Savourel <ysavourel@enlaso.com> wrote:

> Hi all,
> It seems to me that we don't have a good solution for the inline cases of
> the Preserve Space and Language Information data
> categories.
> In the original draft mapping we used xml:space and xml:lang on <mrk>.
> But, as David pointed out, this can't work because these attributes are
> not allowed on <mrk>/<sm>.
> I believe we did this because of <sm>: both xml:lang and xml:space scopes
> would apply to an empty element.
> But we cannot have no inline solution for those two data categories.
> So it seems they would fall into the class of the data categories only
> partially supported directly by the core, and we need
> ITS-module attributes to handle them inline. Something like this: <mrk
> id='1' type="its:any" its:space="preserve" its:lang="iu">.
> Cheers,
> -yves
> ---------------------------------------------------------------------
> To unsubscribe from this mail list, you must leave the OASIS TC that
> generates this mail.  Follow this link to all your TCs in OASIS at:
> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
Received on Thursday, 23 October 2014 13:04:59 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:05:52 UTC