jonathon wrote: > CPHennessy wrote: > >>> I haven't installed OO 2.2.0 yet. Does anyone know whether it can >>> handle Unicode Plane I? I know 2.1.0 just fills in question marks for >>> anything but Plane 0. > >> This sounds like a font issue and not an OpenOffice.org issue. > > This is an OOo issue. > > What needs to be done is a complete rewrite of the OOo code > base so that one string handling library that handles all 16 > planes of Unicode is used.
Fortunately not. :-) The OOo string classes store strings in a UTF-16 representation. This representation is perfectly able to handle all possible UniCode strings. The bug in OOo is that the code often assumes that a single character is a 16 Bit value. This applies to all methods that get or return character values, mainly the character iteration and access methods of the string classes. So what is needed is changing "only" the code that uses these methods, methods dealing with single characters. Especially this code must use new string iterator methods that return real UniCode characters, not an array-like access to 16 Bit code units. This is some work to do but definitely not a "complete rewrite of the OOo code base". It's less work than the conversion from 8Bit strings to 16Bit strings we made before the OOo source code was published. And we also survived that conversion. :-) > IOW, the fix is trivial, but requires a lot of man hours, > because the original code was badly implemented. You are right, this is comparably easy but needs some time. Good news is that work has started already (see some mails on the dev list). Ciao, Mathias -- Mathias Bauer (mba) - Project Lead OpenOffice.org Writer OpenOffice.org Engineering at Sun: http://blogs.sun.com/GullFOSS Please don't reply to "[EMAIL PROTECTED]". I use it for the OOo lists and only rarely read other mails sent to it. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
