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


Help: OASIS Mailing Lists Help | MarkMail Help

xliff message

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

Subject: RE: [xliff] Event "XLIFF TC Call" - Summary

Hi Helena,

> ... I don't understand the part about "bidi info"
> re paragraph direction in XLIFF context? Why is
> the directional attributes a concern of XLIFF? 
> I can understand why one needs <bdi> in HTML/CSS
> env for rendering purposes but I don't get why 
> this is needed in XLIFF? 

For the same reason: An XLIFF editor tool needs to be able to edit/render bidi text, so it needs to somehow store bidi markers, either as Unicode characters or as elements. During the SC discussion last week, both Andrew and Fredrik noted that their XLIFF editors are using Unicode characters for this. They also noted that having the main directionality of the paragraph was needed too. Hence the mention that we may need to have some kind of attribute at the paragraph level (<unit>) that provides such information.

I wonder what other tool use for bidi markers. For example Swordfish, OpenTM2, MultiTrans, etc?

I keep seeing in all W3C/Unicode best practices documents that when working with XML using elements is better. And at the same time I keep seeing that many editing tools still prefer using Unicode characters. Obviously we could always map Unicode bidi characters to elements and vice-versa, but things like the fact that we can, here again, have spans of bidi information split by the segmentation makes me wonder about how complicated elements would be.


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