OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

xliff message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: RE: [xliff] Call for dissent: csprd02 127 xml:space text change

I guess, yes: Technically, “default” (do what you want) is about the same as undefined.






From: Dr. David Filip [mailto:David.Filip@ul.ie]
Sent: Wednesday, November 13, 2013 2:20 PM
To: Schnabel, Bryan S
Cc: Yves Savourel; xliff@lists.oasis-open.org
Subject: Re: [xliff] Call for dissent: csprd02 127 xml:space text change


I can implement this, once consensus reached.

However, I do not understand why the default should be undefined (i.e. no value) if not inherited from parent?

IMHO,  It can still be "default", if not inherited


Dr. David Filip



University of Limerick, Ireland

telephone: +353-6120-2781

cellphone: +353-86-0222-158

facsimile: +353-6120-2734


On Wed, Nov 13, 2013 at 6:12 PM, Schnabel, Bryan S <bryan.s.schnabel@tektronix.com> wrote:


Thanks for the very good comments. I think your modifications add value. And your formatting observations are correct.

As this now seems an editorial fix, David, is it okay to change ownership of 127 to you?



-----Original Message-----
From: Yves Savourel [mailto:ysavourel@enlaso.com]
Sent: Wednesday, November 13, 2013 4:25 AM
To: Schnabel, Bryan S; xliff@lists.oasis-open.org
Subject: RE: [xliff] Call for dissent: csprd02 127 xml:space text change

Hi Bryan, all,

The default value should probably reflect the inheritance mechanism.
Maybe something like:

Default value: the value of xml:space on the closest parent element, or undefined if no parent element has xml:space declared.

Also, looking at the section

- The text "For more information see the section on xml:space in the XML specification." should probably have a link to the relevant section in the XML specification (http://www.w3.org/TR/REC-xml/#sec-white-space)

- I think we style attributes names in some way, no? (like in section 2.7.5) 'xml:space' looks plain text in that section.


From: xliff@lists.oasis-open.org [mailto:xliff@lists.oasis-open.org] On Behalf Of Schnabel, Bryan S
Sent: Tuesday, November 12, 2013 5:16 PM
To: xliff@lists.oasis-open.org
Subject: [xliff] Call for dissent: csprd02 127 xml:space text change

I propose we update the xml:space text to indicate the inheritance behavior described by Yves. And I also propose we change the Default value to "undefined."

Add the following note:

While xml:space is specified in <source> and <target>, elements that allow extended attributes cannot be prevented from using it.
Therefore if xml:space is set on any element, its descendants will inherit its xml:space value, unless specifically overridden, for

<unit id='1' xml:space='preserve'>
  <source>pre-formatted text</source> <!-- implicit xml:space='preserve' -->  </segment> </unit>

If I do not receive dissent by the end of the week I will consider this approved.



127: https://lists.oasis-open.org/archives/xliff-comment/201310/msg00013.html
xml:lang and xml:space
Hi all,

The attributes xml:lang and xml:space can be used on <source> and <target>.
But because they are in a non-XLIFF namespace, they presumably can also be used on elements that accept extended attributes.

Because, per the XML specification, those two attributes work with inheritance, one can set, for example, the xml:space value of a <source> or a <target> without declaring the attribute on that element:

<unit id='1' xml:space='preserve'>
  <source>pre-formatted text</source> <!-- implicit xml:space='preserve' -->  </segment> </unit>

There is no mention of this anywhere in the specification.
I'm wondering if it's not worth having some note about this in the xml:space section.

The specification also says for xml:space:

Default value: default

Which is, from an XML viewpoint, incorrect. If it's not specified the value should be the same as the value for the parent element.


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:


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]