Re: Problem with gettext _() (bug 429678)

[Lars Gullik Bjønnes]

John Levon <[EMAIL PROTECTED]> writes:

| nope, in current CVS. It is corrupting the ->message() we send to
| the minibuffer. 
| 
| One example is "Saving document" in lyxfunc.C - it is a garbled
| string being created. 

Og in what order is A + B + C + D evaluated?
If it is from left to right...

const char* + char .... this is not a legal binding...
but if we change the char to int...
const char* + int.... then we just create a new pointer from the ints
value position...

So... this code is legal, but bogus. This is a bug.

Fix is still to change to stringstream:

ostringstream s1;
s1 << _("Saving document") << ' ' <<
MakeDisplayPath(owner->buffer()->fileName() << "...";
owner->message(s1.str().c_str());


Other locations please...

-- 
        Lgb