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: RE: [xliff-inline] Reference to opening code


Hi Bryan,

> I am in complete agreement that the extra attribute in the closing 
> element is unneeded. It is quite resolvable to have matching ids 
> within a given segment. I wonder if it would not be better to use 
> the more traditional id, idref pairing, rather than the unconventional 
> id to id matching?

I think that is a good idea.

I was going to post another answer to Christian email about using "<sc id='o1'/>text<ec id='c1'/>" to say that it was possibly a good idea to have the id of the closing code be automated, based on the one of the opening code, so you would have something like this: <sc id='1'>text<ec id='_c_1'/> where "_c_" would be required for closing code. So we would have both a unique ID for each codes and the id of the closing code automated.

But using no id and instead a idref (or rid?) seem better: <ec idref='1'/> one has the exact same information as <ec id='1'/> (the id is '1') but its function is much more clear.

Cheers,
-ys



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