[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [xliff-inline] Representing information for the starting/ending/standalone parts
Hi Yves, I share your view. I wonder if we have already discussed the following: When should the native code go into "disp/dispStart/dispend"? Put differently: We discussed local skeletons. When should they be used? Cheers, Christian -----Original Message----- From: xliff-inline@lists.oasis-open.org [mailto:xliff-inline@lists.oasis-open.org] On Behalf Of Yves Savourel Sent: Dienstag, 20. September 2011 12:58 To: xliff-inline@lists.oasis-open.org Subject: RE: [xliff-inline] Representing information for the starting/ending/standalone parts My personal preference would be: --- b) Variation of a) but using two different attribute for <pc> to be a bit clearer? [this is the one we have been using so far] <ph id='1' disp="[br/]"/> <sc id='1' disp="[b]"/> <ec id='1' disp="[/b]"/> <pc id='1' dispStart="[b]" dispEnd="[/b]"/> --- The rationale being that adding 'Start' or 'End' to the attribute is redundant when in a start/end code. It may even be leading the user to think there is a dispEnd if she sees a dispStart in a <sc>. Cheers, -ys --------------------------------------------------------------------- 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]