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] Fragment identifiers for <source> and <target>

Hi Ryan,

There is no way to point to the source or target content as elements using the fragment identifier mechanism because they don't have

One can point to their enclosing segment, and from there one can access the source or the target element (which are always unique in
a given <segment> element.

So far I have not run into a case where pointing to specifically source or target was needed. I don't what others think. Bryan you
played with FragId quite a bit, do you think this is a shortcoming?


-----Original Message-----
From: xliff@lists.oasis-open.org [mailto:xliff@lists.oasis-open.org] On Behalf Of Ryan King
Sent: Tuesday, January 27, 2015 10:48 AM
To: xliff@lists.oasis-open.org
Subject: [xliff] Fragment identifiers for <source> and <target>

Hi TC folks,

We've been working on an XLIFF 2.0 object model and have a question about fragment identifiers.

<xliff xmlns="urn:oasis:names:tc:xliff:document:2.0" version="2.0" srcLang="en" trgLang="fr">  <file id="f1">
  <unit id="u1">
   <segment id="s1">
    <source>Hello World</source>
    <target>Bonjour le Monde</target>

#f=f1/u=u1/s1 refers to the element <segment id="s1"> of the element <unit id="u1">, but is there a mechanism to select <source> or
<target> of <segment id="s1"> individually without inline markup?


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

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