RE: [xliff] RE: Proposed solution for csprd02 (RE: csprd02 comment - xml:lang and xml:space)

["Schnabel, Bryan S" <bryan.s.schnabel@tektronix.com>]

Hi Yves,

Your words sound fine to me. But I'm still just a little confused.  I thought 4.7.5 White Spaces was section on white-spaces. Where in the spec are you proposing to put the new words?

- Bryan
________________________________________
From: xliff@lists.oasis-open.org [xliff@lists.oasis-open.org] on behalf of Yves Savourel [ysavourel@enlaso.com]
Sent: Sunday, January 05, 2014 9:27 AM
To: xliff@lists.oasis-open.org
Subject: RE: [xliff] RE: Proposed solution for csprd02 (RE: csprd02 comment - xml:lang and xml:space)

Hi Bryan,

> The point I struggled to make was that we still need to account
> for the more common scenario, that in which no xml:space attribute
> occurs on the parent/ancestor - and no xml:space attribute occurs
> on the <source> and <target>
> ...
> I don't recall the TC discussion about xml:space. But I think our whole
> reason for including the section in the spec is that in the absence
> of an explicit xml:space="preserve" on <source> or <target> is
> that we want the value to be   "default."
>
> If we say "the default value depends on the parent/ancestor" we are
> not making our point.


We do have a section on White-space. So maybe something like this:

[[
Default value:

        For data:
                'preserve'. Note also that the 'default' value is to be interpreted as 'preserve' for the data content (See section
4.7.5 White Spaces).

        Other elements:
                The default value is inherited from the closest ancestor defining xml:space. If no ancestor specify xml:space the
default is 'default'.
]]


-ys



---------------------------------------------------------------------
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