Carsten Driesner wrote:
Frank Schönheit - Sun Microsystems Germany schrieb:
Well, it is not for resource-string replacement. It is for replacing
strings in other strings. People can *use* it for resource string
replacements, if they know that the caveats pointed out by Stephan do
not apply.
I suppose we are not the only people in the world wanting to replace
a string in another string. If we want a well-designed full-featured
facility to robustly replace strings in any situation,
That's what I'm trying to say: I'm not sure we want, since I'm not sure
we need.
So: either make a simple feasible solution like "just replace a string",
+1
I am also looking forward to a SIMPLE function that just replaces a
string in a string.
Ha! New customer. :) But please be precise:
Does anybody have demand for "replac[ing] a string in a string"
*outside* the area of resource strings?
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?
-Stephan
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
