"Shachar Shemesh" <[EMAIL PROTECTED]> wrote: > >Eventually we have to implement bi-di support there without relying on any > >external libraries. > > > > > BiDi is a $&!(@*#)$ complicated algorithm (excuse my language). Why on > earth should we insist on writing it ourselves?
We don't really have to write it from scratch, porting an existing code would suffice, but a difference between unicode char width (16 vs. 32 bit) makes it impossible to use any system unicode APIs. Another reason to have an internal implementation is to not depend on possible differences between implementations, differences in collation tables is an obvious example here. -- Dmitry.
