Eike Rathke wrote:
...
Actually, now that we upgraded to ICU 3.6, the way to go would be to use
ICU regexps http://www.icu-project.org/userguide/regexp.html instead,
the main advantages being they are fully internationalized and Unicode
aware, quite complete, and we already use ICU for i18n purposes.
Oh, that sounds encouraging.
I had all but given up after looking more at boost and finding that it
needed ICU for Unicode support. I figured it was going to be the typical
"use one function and pull in a whole collection of libraries" due to
dependencies.
Further, I need more c++ mojo to tweak the Boost examples to try the
Unicode support.
The GNU libstdc++ code won't do anyway because it is GPL, not LGPL. ...
IANAL--I don't even like to discuss licenses--but I thought as long as
you simply _use_ a GPL library, you're not under the GPL. The idea here
would be to simply link to standard functions in libstdc++, not to copy
source code and modify it for OOo. Unless I'm mistaken, OOo already
links to libstdc++. At least libstdc++ is mapped in by OOo; I assume
that's just normal library linkage.
Thanks for the pointer, I'll pop over and look at ICU.
<Joe
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
