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] Localization Note vs <note>

I kind of agree with you Felix.

One can very likely have ITS rules that make XLIFF notes usable by a ITS processor (e.g. having the selector point to the source
and/or target, etc.), but I don't think we can make the XLIFF notes behave to match the ITS LocNote semantics.


-----Original Message-----
From: Felix Sasaki [mailto:felix@sasakiatcf.com] 
Sent: Sunday, September 18, 2016 11:29 PM
To: Yves Savourel <ysavourel@enlaso.com>
Cc: XLIFF Main List <xliff@lists.oasis-open.org>
Subject: Re: [xliff] Localization Note vs <note>

Hi Yves and all,

from what you write it seems it does not make sense to use ITS Localization Note in XLIFF directly. The inheritance semantics just
does not map. In the XLIFF 2.1 spec, probably all one can give is guidance to extractors how to deal with ITS notes in e.g. HTML or
XML, but in the XLIFF spec only have the XLIFF core note.



> Am 18.09.2016 um 15:21 schrieb Yves Savourel <ysavourel@enlaso.com>:
> Hi all,
> I'm not quite sure how to map the XLIFF <note> element as the equivalent of the ITS Localization Note data category.
> The XLIFF <note> element "...can contain information about <source>, <target>, <unit>, <group>, or <file> elements."
> It has also an optional appliesTo attribute that is either 'source' or 'target'.
> There is no information about inheritance, which I assume, means there is no inheritance.
> So if I have:
> <group id='g1'>
> <notes>
>  <note id='ng1'>note 1</note>
> </note>
> <unit id='u1'>
>  <segment>
>   <source>Content</source>
>  </segment>
> </unit>
> </group>
> It means the source object after parsing does not have any associated note.
> In ITS 2.0 the Localization Note data category has quite different semantics
> "For elements, the data category information inherits to the textual 
> content of the element, including child elements, but excluding attributes."
> So, if I assume XLIFF <note> is the same as ITS Localization Note: 
> from an ITS viewpoint the code above would result in a note associated with the source object.
> It seems then that depending on how we access the note (as XLIFF Core 
> or through the ITS module), we get a different result. This is making the implementation *very* difficult.
> There is also the matter of the appliesTo. Since ITS Localization Note 
> applies to all children I assume a <note> with appliesTo='source' on a 
> given unit must not be seen as an ITS Localization Note if the unit 
> has a target element (because then <note> doesn't applies to all children), but it must been seen as an ITS Localization Note if
it does not have a target element (because then <note> applies to all children)?
> Any guidance would be welcome.
> Thanks,
> -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

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