[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [xliff-inline] mrk and id
Yves, I agree with you that one set of IDs and a simpler way of pointing to elements without needing to specify the type would be a good thing. Prefixing the values, as you did there, seems to be a good way of handling this. -Arle Sic scripsit Yves Savourel in May 14, 2012 ad 23:09 : > Hi all, > > So it seems we tend to agree that the id attribute should be required for <mrk>. > > The next question is: what should be the constraints of its value? > > I assume, like for <ph>/<pc>/<sc>/<ec> we want the id to be unique within source and target. That is, if the same id is used in source and target it means it's the same <mrk>. > > Now, can a <mrk> have the same ID value as a <ph>/<pc>/<sc>/<ec>? > > Can we have this: > > <source>The <mrk id="1" type="comment" value="Possible values: Printer or Stacker"><ph id="1">$1</ph></mrk> has been enabled.</source> > > Or must we have something like this: > > <source>The <mrk id="m1" type="comment" value="Possible values: Printer or Stacker"><ph id="c1">$1</ph></mrk> has been enabled.</source> > > My initial thought is that it's probably easier to maintain a single set of unique IDs rather than two. And I'm thinking it would also (if needed) allow external objects to point to either <mrk> or <ph>/<pc>/<sc>/<ec> without specifying the distinction. > > Thoughts? > -yves > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: xliff-inline-unsubscribe@lists.oasis-open.org > For additional commands, e-mail: xliff-inline-help@lists.oasis-open.org >
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]