Re: PATCH InfoInset

Stephan Witt wrote: setText(_(Unknown buffer info)); to setText(bformat(_([[%1$s unknown]]), from_utf8(name_))); setText(bformat(_(%1$s unknown[[BufferInfo]]), from_utf8(name_))); seems more correct then. why to put [[BufferInfo]] there? pavel

Re: PATCH InfoInset

Am 01.11.2010 um 15:34 schrieb Pavel Sanda: Stephan Witt wrote: setText(_(Unknown buffer info)); to setText(bformat(_([[%1$s unknown]]), from_utf8(name_))); setText(bformat(_(%1$s unknown[[BufferInfo]]), from_utf8(name_))); seems more correct then. why to put [[BufferInfo]] there? I

Re: PATCH InfoInset

Stephan Witt wrote: Stephan Witt wrote: setText(_(Unknown buffer info)); to setText(bformat(_([[%1$s unknown]]), from_utf8(name_))); setText(bformat(_(%1$s unknown[[BufferInfo]]), from_utf8(name_))); seems more correct then. why to put [[BufferInfo]] there? I don't know. I

Re: PATCH InfoInset

Am 01.11.2010 um 15:58 schrieb Pavel Sanda: Stephan Witt wrote: Stephan Witt wrote: setText(_(Unknown buffer info)); to setText(bformat(_([[%1$s unknown]]), from_utf8(name_))); setText(bformat(_(%1$s unknown[[BufferInfo]]), from_utf8(name_))); seems more correct then. why to put

Re: PATCH InfoInset

Stephan Witt wrote: > setText(_("Unknown buffer info")); > to > setText(bformat(_("[[%1$s unknown]]"), from_utf8(name_))); > > setText(bformat(_("%1$s unknown[[BufferInfo]]"), from_utf8(name_))); > seems more correct then. why to put [[BufferInfo]] there? pavel

Re: PATCH InfoInset

Am 01.11.2010 um 15:34 schrieb Pavel Sanda: > Stephan Witt wrote: >> setText(_("Unknown buffer info")); >> to >> setText(bformat(_("[[%1$s unknown]]"), from_utf8(name_))); >> >> setText(bformat(_("%1$s unknown[[BufferInfo]]"), from_utf8(name_))); >> seems more correct then. > > why to put

Re: PATCH InfoInset

Stephan Witt wrote: > > Stephan Witt wrote: > >> setText(_("Unknown buffer info")); > >> to > >> setText(bformat(_("[[%1$s unknown]]"), from_utf8(name_))); > >> > >> setText(bformat(_("%1$s unknown[[BufferInfo]]"), from_utf8(name_))); > >> seems more correct then. > > > > why to put

Re: PATCH InfoInset

Am 01.11.2010 um 15:58 schrieb Pavel Sanda: > Stephan Witt wrote: >>> Stephan Witt wrote: setText(_("Unknown buffer info")); to setText(bformat(_("[[%1$s unknown]]"), from_utf8(name_))); setText(bformat(_("%1$s unknown[[BufferInfo]]"), from_utf8(name_))); seems more

Re: PATCH InfoInset

Am 30.10.2010 um 15:59 schrieb Stephan Witt: I've got a crash when place info-insert buffer vcs-date into CVS controlled file. The attached patch helps, but I'm not sure if there's some more elegant solution. Any opinions? I rephrase my question... The crash is the ASSERT in bformat().

Re: PATCH InfoInset

It is caused by the brackets. Wasn't this the way to indicate the context of a string? I think you now have an empty string in the context [[...]]. This is again translated as an empty string. Vincent Op 31 okt 2010 08:51 schreef Stephan Witt st.w...@gmx.net: Am 30.10.2010 um 15:59 schrieb

Re: PATCH InfoInset

Am 31.10.2010 um 10:11 schrieb Vincent van Ravesteijn: It is caused by the brackets. Wasn't this the way to indicate the context of a string? I think you now have an empty string in the context [[...]]. This is again translated as an empty string. Thanks, now I see. So it was a bad idea to

Re: PATCH InfoInset

On 10/31/2010 11:10 AM, Stephan Witt wrote: Currently I'm a bit surprised that I cannot use the info dialog anymore. It crashes at line 217 of InsetCommandParams.cpp (LASSERT in default of switch missing the INFO_CODE case) What happens here? I guess the latest changes to the dialog code were

Re: PATCH InfoInset

Am 31.10.2010 um 20:10 schrieb Richard Heck: On 10/31/2010 11:10 AM, Stephan Witt wrote: Currently I'm a bit surprised that I cannot use the info dialog anymore. It crashes at line 217 of InsetCommandParams.cpp (LASSERT in default of switch missing the INFO_CODE case) What happens here? I

Re: PATCH InfoInset

Am 30.10.2010 um 15:59 schrieb Stephan Witt: > I've got a crash when place "info-insert buffer vcs-date" into CVS controlled > file. > The attached patch helps, but I'm not sure if there's some more elegant > solution. > Any opinions? I rephrase my question... The crash is the ASSERT in

Re: PATCH InfoInset

It is caused by the brackets. Wasn't this the way to indicate the context of a string? I think you now have an empty string in the context [[...]]. This is again translated as an empty string. Vincent Op 31 okt 2010 08:51 schreef "Stephan Witt" : Am 30.10.2010 um 15:59 schrieb

Re: PATCH InfoInset

Am 31.10.2010 um 10:11 schrieb Vincent van Ravesteijn: > It is caused by the brackets. Wasn't this the way to indicate the context of > a string? I think you now have an empty string in the context [[...]]. This > is again translated as an empty string. Thanks, now I see. So it was a bad idea

Re: PATCH InfoInset

On 10/31/2010 11:10 AM, Stephan Witt wrote: Currently I'm a bit surprised that I cannot use the "info" dialog anymore. It crashes at line 217 of InsetCommandParams.cpp (LASSERT in default of switch missing the INFO_CODE case) What happens here? I guess the latest changes to the dialog code were

Re: PATCH InfoInset

Am 31.10.2010 um 20:10 schrieb Richard Heck: > On 10/31/2010 11:10 AM, Stephan Witt wrote: >> >> Currently I'm a bit surprised that I cannot use the "info" dialog anymore. >> It crashes at line 217 of InsetCommandParams.cpp >> (LASSERT in default of switch missing the INFO_CODE case) >> What

PATCH InfoInset

I've got a crash when place info-insert buffer vcs-date into CVS controlled file. The attached patch helps, but I'm not sure if there's some more elegant solution. Any opinions? Stephan Index: src/insets/InsetInfo.cpp === ---

PATCH InfoInset

I've got a crash when place "info-insert buffer vcs-date" into CVS controlled file. The attached patch helps, but I'm not sure if there's some more elegant solution. Any opinions? Stephan Index: src/insets/InsetInfo.cpp === ---