Mathias Bauer wrote: > Michael Meeks wrote: > >> On Fri, 2006-11-10 at 17:12 +0100, Stephan Bergmann wrote: >>> This indicates that an application's concept of "character" is often >>> best represented by a programming environment's concept of "string." >> >> An interesting insight indeed. >> >>> Use sal_uInt32 to represent individual Unicode encoded characters and >>> add any necessary base functionality to rtl::OUString (e.g., operating >>> on the individual Unicode encoded characters represented by an instance >>> of rtl::OUString). >> >> There's no chance then of switching to UTF-8 as an underlying string >> representation :-) and saving a measurable chunk of our string >> overhead ? > > That would be nice for several reasons. The biggest drawback of this > solution is that the C++ UNO Language Binding would be changed > incompatibly and all in-process C++ components using it must at least be > recompiled to work in the OOo version that contains the new string > class. So we shouldn't dismiss this option but we also should handle it > with care. Sorry, that mail just slipped out of my drafts folder where I started to write it some days ago and then noticed that I was late and just forgot to delete it. Just ignore it. :-)
Ciao, Mathias -- Mathias Bauer - OpenOffice.org Application Framework Project Lead Please reply to the list only, [EMAIL PROTECTED] is a spam sink. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
