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

 


Help: OASIS Mailing Lists Help | MarkMail Help

xliff-inline message

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


Subject: mrk and id


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




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