OASIS Open Mailing List Archives  ·  All Lists  ·  xliff-inline  ·  2010-08

xliff-inline — archive

[Date Prev]  |  [Thread Prev]  |  [Thread Next]  |  [Date Next]   —  [Date Index]  |  [Thread Index]  |  [Month Index]  |  [List Home]

Requirements - #9


Hi Arle, > English: This is some bold text > Japanese: これは、いくつかのです The Japanese example, I think, falls into this requirement #9: It changes the type of code, but we still need to make the correspondence between the source and the target. > Also, how would we handle a case where one set of tags > in one language could correspond to two (or more) in > another? (For example, a syntactic unit is bolded in English, > but it corresponds to two syntactic units that are > separated in a target language and that both should > appear as bold with Roman text between them? That case of split translation with extra codes points to the use case of adding inline codes, for which I don't think we have a requirement yet. So I would propose a new #10 with something like: [ Must be able to represent inline codes added to the segment Sometimes the translation of a formatted text requires the translation to split the source into several parts in different places in the segments and the original codes need to be replicated.

[Date Prev]  |  [Thread Prev]  |  [Thread Next]  |  [Date Next]   —  [Date Index]  |  [Thread Index]  |  [Month Index]  |  [List Home]