[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [xliff-comment] XLIFF 2.1 csprd01: <ph> processing requirements
Jan<target>text tučným<ph id="1" disp="/bold"></target>a correct formatting cannot be guaranteed if word order is different in target language<source>bold<ph id="1" disp="/bold"> text</source>- tag nesting- removal of either opening or closing tagFor example if it's used to represent <bold> from HTML, agent cannot validate (without additional editing hints):Could you please add a similar Processing Requirement for <ph>? It should explain why <ph> MUST NOT be used for well-formed spanning code (opening and closing tag are represented by separate <ph>).Hello,in http://docs.oasis-open.org/xliff/xliff-core/v2.1/csprd01/ Processing Requirements state why <pc> must not be used to represent standalone code.xliff-core-v2.1-csprd01.html# pc
- correct order, which can produce </b>…<b>- leaving tag pair emptyIn case Extractor decides to drop opening tag at the beginning of the segment as "redundant", such asSimilarly, Processing Requirements should describe that <ph> should not be used for locking of inline content otherwise represented by well formed spanning code.
E.g.
<span translate="no>some text</span>
as<data id="d1"><span translate="no>some text</span></data>
…<source>following should not be localized: <ph id="1" dataRef="d1" /></source><mrk translate="no> should be suggested as preferred solution.Thanks,
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]