Hi Stephan, > If no, I suggest we do the following: Clean up the OOo resource strings > so that they use a single, unambiguous syntax for dynamic tokens and > introduce (C++ or UNO) functionality to expand any dynamic tokens that > is easy to use (esp. for the general case of replacing zero or one > dynamic token). > > If yes, I will happily add some rtl::OUString searchAndReplace. But we > should do the above nonetheless, shouldn't we?
We don't have a real-life problem with the current resource string replacement, and it's simply not worth the huge effort to touch all our resource strings. It will break more code that it will fix bugs. If we really don't know what to do next, then there's bigger fish to catch than this, for sure. We should not fix a problem which does not exist. Ciao Frank -- - Frank Schönheit, Software Engineer [EMAIL PROTECTED] - - Sun Microsystems http://www.sun.com/staroffice - - OpenOffice.org Base http://dba.openoffice.org - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
