Andre Poenitz <[EMAIL PROTECTED]> writes:
| On Sat, Sep 16, 2006 at 03:20:35PM +0200, Lars Gullik Bjønnes wrote:
| > Abdelrazak Younes <[EMAIL PROTECTED]> writes:
| >
| > | Lars Gullik Bjønnes wrote:
| > | > Georg Baum <[EMAIL PROTECTED]> writes:
| > | > | Am Samstag, 16. September 2006 10:19 schrieb Juergen Spitzmueller:
| > | > | > The assert seems to be triggered by Messages, because the German
| > | > | translation | > of the message "Paste" ("Einfügen") contains an
| > | > umlaut (see item #5 in | the | > backtrace).
| > | > | | The problem is that Messages::get() is called with an already
| > | > translated | string. This is a programming error that would not have
| > | > been found with | the brute force string->docstring approach.
| > | > Does this patch fix the problem?
| > | > ------------------------------------------------------------------------
| > | > Index: src/lyxfunc.C
| > | > ===================================================================
| > | > --- src/lyxfunc.C (revision 15012)
| > | > +++ src/lyxfunc.C (working copy)
| > | > @@ -778,7 +778,7 @@
| > | > if (view()->available())
| > | > // cancel any selection
| > | > dispatch(FuncRequest(LFUN_MARK_OFF));
| > | > - setMessage(lyx::from_utf8(N_("Cancel")));
| > | > + setMessage(_("Cancel"));
| > |
| > | I thought these strings were not translated on purpose?
| >
| > But we have to change that. And when looking at it now, it does not
| > seem that the purpose is overy clever either (read: useful).
|
| Wasn't the purpose something with 'we should only send
| untranslated error messages over lyxpipe'?
Yes, something like that.
It seems that the two paths must be severed-> information to user to
unicode at once, lyxpipe info stay with ascii.
The problem is that setMessage is used for both and does not always
take a ascii string.
--
Lgb
