Yves,
When you say "For data," do you intend this to be a generic term that covers things like codes and original data (i.e., source/target text and the inlines that cover those data types)? Or do you mean <data>? If the latter, why not include <sc>, <ec>, and <ph>, as stated in 4.7.5?
So for "4.3.2.2 xml:space" (a subsection under the 4.3.2 XML namespace section) would the following be better to support your proposal?
Change from:
Default value: default
To:
Default value:
For <sc>, <ec>, <ph> and <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'.
And for "4.7.5 White Spaces" no change required?
Thanks,
Bryan
-----Original Message-----
From: [mailto:] On Behalf Of Yves Savourel
Sent: Sunday, January 05, 2014 9:01 PM
To:
Subject: RE: [xliff] RE: Proposed solution for csprd02 (RE: csprd02 comment - xml:lang and xml:space)
Sorry for being unclear:
The possible text was for the xml:space attribute definition.
-ys
-----Original Message-----
From: [mailto:] On Behalf Of Schnabel, Bryan S
Sent: Sunday, January 5, 2014 9:15 PM
To: Yves Savourel;
Subject: RE: [xliff] RE: Proposed solution for csprd02 (RE: csprd02 comment - xml:lang and xml:space)
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: [] on behalf of Yves Savourel []
Sent: Sunday, January 05, 2014 9:27 AM
To:
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
---------------------------------------------------------------------
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
---------------------------------------------------------------------
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
