> + if (binfo.empty()) {
> + docstring fmt = _("%1$s unknown[[InsetNote]]");
> + setText(bformat(fmt, from_utf8(name_)));
> + } else
InsetNote ?
Please remember that this should be helpful for the translators to
correctly tra
Am 01.11.2010 um 05:25 schrieb Daron Wilson:
> Hi all.
>
> I've recently started using LyX, and I've downloaded the 2.0 alpha 6 version
> used with Mac OS X. I have only one issue so far, and that concerns the use
> of Unicode, in particular polytonic Greek (entered using the Polytonic Greek
On Wed, Oct 27, 2010 at 4:37 PM, John McCabe-Dansted wrote:
> Hi Vincent, this appears to be another recent regression, this time
> from r35832 on Monday.
Sorry John, your system is a bit off. I can reproduce with r35831 too ;)
> I then get the Assert:
This is a serious bug and needs to fixed
Pavel, Peter,
I created bug http://www.lyx.org/trac/ticket/7002 about the fact that
LyX crashes when it tries to show an error message that has nothing to
do with exporting in threads. Like the error you get if you didn't
supply a system dir.
Vincent
Am 01.11.2010 02:19, schrieb Vincent van Ravesteijn:
> However, you introduced a new feature, multirows, and then report bug
> #6985, #6958, #6999 and then you see that you don't like the apply
> scheme and you report bug #6998, #6997, #7001 and then also bug #7000
> for the quite related multico
> I'm not responsible for the new tabular Apply/OK scheme. As you say, the
> problem lies within this scheme, we need to revert this scheme not
> aprticular table feature. We have much more new table features that suffer
> from this scheme, see
> http://www.lyx.org/trac/ticket/6997
>
> I committed
Am 31.10.2010 17:42, schrieb Jürgen Spitzmüller:
We need Abdel's help here. He has imlemented the new Apply/OK scheme and
I'm sure he knows a solution. I mean it works for setting multicolumns so
it should work also for multirows using the same tabular UI<-> Inset
communication. Abdel?
As sa
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 happ
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
On 10/31/2010 05:42 AM, Scott Otterson wrote:
Has anyone seen this problem before? I have a short latex document
(below the dotted line) that latex crunches without error. However,
when I try to import it into lyx (file-->import plain latex) lyx
manages to create a .lyx file but then hangs fo
Am 31.10.2010 um 17:10 schrieb Uwe Stöhr:
> Am 31.10.2010 16:07, schrieb Jürgen Spitzmüller:
>
>>> The only issue I see right now is that one cannot set a multirow via the
>>> dialog What else do you see that is not yet also in LyX 1.6.x?
>>
>> Yes, but this issue is quite tricky. I'm not even
On 10/31/2010 06:38 AM, Jean-Pierre Chrétien wrote:
Jean-Pierre Chrétien a écrit :
I'll post a tentative file with bug #6609 to illustrate the idea
(tentative because it's not working right now).
I performed some tests to make this file work and I corrected some
typos in the file.
Howeve
Uwe Stöhr wrote:
> We need Abdel's help here. He has imlemented the new Apply/OK scheme and
> I'm sure he knows a solution. I mean it works for setting multicolumns so
> it should work also for multirows using the same tabular UI <-> Inset
> communication. Abdel?
As said, I'm not sure. The curren
Am 31.10.2010 16:07, schrieb Jürgen Spitzmüller:
The only issue I see right now is that one cannot set a multirow via the
dialog What else do you see that is not yet also in LyX 1.6.x?
Yes, but this issue is quite tricky. I'm not even sure it is solvable without
a complete rewrite of the tabu
On 10/31/2010 10:27 AM, Richard Heck wrote:
On 10/30/2010 11:24 AM, Anand Rangarajan wrote:
Sorry if this has come up previously but I've encountered a problem
with lyx equation labels (lyx-1.6.7 on linux x86_64). When I use the
label 'x=1' for an equation, lyx changes it to 'x=3D1'. If I
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
Uwe Stöhr wrote:
> > The table dialog is so broken currently.
>
> The only issue I see right now is that one cannot set a multirow via the
> dialog What else do you see that is not yet also in LyX 1.6.x?
Yes, but this issue is quite tricky. I'm not even sure it is solvable without
a complete re
I haven't followed this thread, but have you seen that the new version 0.4 of refstyle supports now
French:
http://article.gmane.org/gmane.comp.tex.ctan.announce/8109
regards Uwe
> The table dialog is so broken currently.
The only issue I see right now is that one cannot set a multirow via the dialog What else do you see
that is not yet also in LyX 1.6.x?
> I would prefer if we put our energy in fixing that instead of adding even
more features.
I basically agree with
On 10/30/2010 11:24 AM, Anand Rangarajan wrote:
Sorry if this has come up previously but I've encountered a problem
with lyx equation labels (lyx-1.6.7 on linux x86_64). When I use the
label 'x=1' for an equation, lyx changes it to 'x=3D1'. If I edit
and save the lyx file in emacs, then the
Hi,
this is the error-log
...
cd /usr/BUILD/BuildLyx/src/mathed && /usr/bin/c++ -DUSE_ENCHANT=1
-DHAVE_GETTEXT -Wall -Wunused-parameter -fno-strict-aliasing -Wall
-Wunused-parameter -O3 -DNDEBUG -I/usr/BUILD/BuildLyx -
I/usr/src/lyx/lyx-devel/src -I/usr/include/enchant -I/usr/src/lyx/lyx-devel
Jean-Pierre Chrétien a écrit :
I'll post a tentative file with bug #6609 to illustrate the idea
(tentative because it's not working right now).
I performed some tests to make this file work and I corrected some typos in the
file.
However, the current version does not work with LyX for two
Uwe Stöhr wrote:
> We implemented support for multirows the following way:
>
> \multirow{ncols}{width}{content}
>
> but \multirow supports this scheme:
>
> \multirow{ncols}[struts]{width}[offset]{content}
>
> The attached patch adds support for the offset. It is a fileformat change.
>
> Suppor
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 Stephan Witt:
>
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 bforma
25 matches
Mail list logo
