2014-04-24 0:29 GMT+02:00 Vincent van Ravesteijn v...@lyx.org:
You could sign me up for those two.
Done.
However, I'm not sure what it means to be the ticket owner.
I think the main purpose is that someone knowledgeable in the respective
area checks the severity of the bug, maybe invites
2014-04-24 0:29 GMT+02:00 Vincent van Ravesteijn :
>
> You could sign me up for those two.
>
Done.
> However, I'm not sure what it means to be the ticket owner.
>
I think the main purpose is that someone knowledgeable in the respective
area checks the severity of the bug, maybe
Op 22 apr. 2014 09:47 schreef Jürgen Spitzmüller sp...@lyx.org:
2014-04-19 19:22 GMT+02:00 Richard Heck:
Abdel has asked to be removed as default owner for the dialog and
frontend-qt4 bugs, and I've also removed him as default owner of the file
and menu bugs. Would anyone like to replace him?
Op 22 apr. 2014 09:47 schreef "Jürgen Spitzmüller" :
>
> 2014-04-19 19:22 GMT+02:00 Richard Heck:
>
>>
>> Abdel has asked to be removed as default owner for the dialog and
frontend-qt4 bugs, and I've also removed him as default owner of the file
and menu bugs. Would anyone like to
2014-04-19 19:22 GMT+02:00 Richard Heck:
Abdel has asked to be removed as default owner for the dialog and
frontend-qt4 bugs, and I've also removed him as default owner of the file
and menu bugs. Would anyone like to replace him? The only thing this really
means is that you get an email when
2014-04-19 19:22 GMT+02:00 Richard Heck:
>
> Abdel has asked to be removed as default owner for the dialog and
> frontend-qt4 bugs, and I've also removed him as default owner of the file
> and menu bugs. Would anyone like to replace him? The only thing this really
> means is that you get an email
Abdel has asked to be removed as default owner for the dialog and
frontend-qt4 bugs, and I've also removed him as default owner of the
file and menu bugs. Would anyone like to replace him? The only thing
this really means is that you get an email when a bug in that category
has been filed,
On 19/04/2014 19:22, Richard Heck wrote:
Abdel has asked to be removed as default owner for the dialog and
frontend-qt4 bugs, and I've also removed him as default owner of the
file and menu bugs. Would anyone like to replace him? The only thing
this really means is that you get an email when
Abdelrazak Younes wrote:
undo/redo lasgouttes
Remove
I think this one should remain. P
Abdel has asked to be removed as default owner for the dialog and
frontend-qt4 bugs, and I've also removed him as default owner of the
file and menu bugs. Would anyone like to replace him? The only thing
this really means is that you get an email when a bug in that category
has been filed,
On 19/04/2014 19:22, Richard Heck wrote:
Abdel has asked to be removed as default owner for the dialog and
frontend-qt4 bugs, and I've also removed him as default owner of the
file and menu bugs. Would anyone like to replace him? The only thing
this really means is that you get an email when
Abdelrazak Younes wrote:
>> undo/redo lasgouttes
>
> Remove
I think this one should remain. P
Stephan Witt wrote:
Am 10.12.2010 um 18:34 schrieb Pavel Sanda:
Stephan Witt wrote:
Looks ok - I cannot see any artifacts. Of course this isn't any evidence.
Stephan what is the current state-of-art patch for 7120?
See the attached patch.
since nobody responded feel free to put it
Am 13.12.2010 um 13:07 schrieb Pavel Sanda:
Stephan Witt wrote:
Am 10.12.2010 um 18:34 schrieb Pavel Sanda:
Stephan Witt wrote:
Looks ok - I cannot see any artifacts. Of course this isn't any evidence.
Stephan what is the current state-of-art patch for 7120?
See the attached patch.
Stephan Witt wrote:
> Am 10.12.2010 um 18:34 schrieb Pavel Sanda:
>
> > Stephan Witt wrote:
> >> Looks ok - I cannot see any artifacts. Of course this isn't any evidence.
> >
> > Stephan what is the current state-of-art patch for 7120?
>
> See the attached patch.
since nobody responded feel
Am 13.12.2010 um 13:07 schrieb Pavel Sanda:
> Stephan Witt wrote:
>> Am 10.12.2010 um 18:34 schrieb Pavel Sanda:
>>
>>> Stephan Witt wrote:
Looks ok - I cannot see any artifacts. Of course this isn't any evidence.
>>>
>>> Stephan what is the current state-of-art patch for 7120?
>>
>> See
Am 10.12.2010 um 18:34 schrieb Pavel Sanda:
Stephan Witt wrote:
Looks ok - I cannot see any artifacts. Of course this isn't any evidence.
Stephan what is the current state-of-art patch for 7120?
See the attached patch.
Stephan
Index: src/rowpainter.cpp
Am 10.12.2010 um 18:34 schrieb Pavel Sanda:
> Stephan Witt wrote:
>> Looks ok - I cannot see any artifacts. Of course this isn't any evidence.
>
> Stephan what is the current state-of-art patch for 7120?
See the attached patch.
Stephan
Index: src/rowpainter.cpp
Le 10 déc. 2010 à 21:35, Liviu Andronic a écrit :
On Fri, Dec 10, 2010 at 6:34 PM, Pavel Sanda sa...@lyx.org wrote:
Stephan what is the current state-of-art patch for 7120?
Others, do you like more the current thick line or zoomming-line style
for spellchech errs?
I hate to nag, but the
Am 10.12.2010 um 18:34 schrieb Pavel Sanda:
Stephan Witt wrote:
Looks ok - I cannot see any artifacts. Of course this isn't any evidence.
Stephan what is the current state-of-art patch for 7120?
A little bit buried. But it may resurrect. Starting to dig soon. :-)
Others, do you like more
Le 10 déc. 2010 à 21:35, Liviu Andronic a écrit :
On Fri, Dec 10, 2010 at 6:34 PM, Pavel Sanda wrote:
>> Stephan what is the current state-of-art patch for 7120?
>> Others, do you like more the current thick line or zoomming-line style
>> for spellchech errs?
>>
> I hate to nag,
Am 10.12.2010 um 18:34 schrieb Pavel Sanda:
> Stephan Witt wrote:
>> Looks ok - I cannot see any artifacts. Of course this isn't any evidence.
>
> Stephan what is the current state-of-art patch for 7120?
A little bit buried. But it may resurrect. Starting to dig soon. :-)
> Others, do you
Stephan Witt wrote:
Looks ok - I cannot see any artifacts. Of course this isn't any evidence.
Stephan what is the current state-of-art patch for 7120?
Others, do you like more the current thick line or zoomming-line style
for spellchech errs?
pavel
On Fri, Dec 10, 2010 at 6:34 PM, Pavel Sanda sa...@lyx.org wrote:
Stephan what is the current state-of-art patch for 7120?
Others, do you like more the current thick line or zoomming-line style
for spellchech errs?
I hate to nag, but the current implementation is very eye-catchy. But
I feel
Stephan Witt wrote:
> Looks ok - I cannot see any artifacts. Of course this isn't any evidence.
Stephan what is the current state-of-art patch for 7120?
Others, do you like more the current thick line or zoomming-line style
for spellchech errs?
pavel
On Fri, Dec 10, 2010 at 6:34 PM, Pavel Sanda wrote:
> Stephan what is the current state-of-art patch for 7120?
> Others, do you like more the current thick line or zoomming-line style
> for spellchech errs?
>
I hate to nag, but the current implementation is very eye-catchy. But
I
Am 02.12.2010 um 20:08 schrieb Stephan Witt:
Am 02.12.2010 um 19:49 schrieb Pavel Sanda:
Stephan Witt wrote:
Am 02.12.2010 um 18:41 schrieb Pavel Sanda:
Stephan Witt wrote:
Ok, but that's what I tried too. I attach some screen shot to compare
the two versions, unpatched first -
On 30/11/2010 17:33, Pavel Sanda wrote:
Liviu Andronic wrote:
I would suspect that a wavy line might be more desirable (as in MS
Word, gtkspell, OOo, etc.), and if I remember this was the original
implementation (although then the wavy line was too big :) ).
so we are at circles,
Am 03.12.2010 um 15:31 schrieb Abdelrazak Younes:
On 30/11/2010 17:33, Pavel Sanda wrote:
Liviu Andronic wrote:
I would suspect that a wavy line might be more desirable (as in MS
Word, gtkspell, OOo, etc.), and if I remember this was the original
implementation (although then the wavy
On 03/12/2010 15:52, Stephan Witt wrote:
Am 03.12.2010 um 15:31 schrieb Abdelrazak Younes:
On 30/11/2010 17:33, Pavel Sanda wrote:
Liviu Andronic wrote:
I would suspect that a wavy line might be more desirable (as in MS
Word, gtkspell, OOo, etc.), and if I remember this
Op 3-12-2010 15:54, Abdelrazak Younes schreef:
On 03/12/2010 15:52, Stephan Witt wrote:
Am 03.12.2010 um 15:31 schrieb Abdelrazak Younes:
On 30/11/2010 17:33, Pavel Sanda wrote:
Liviu Andronic wrote:
I would suspect that a wavy line might be more desirable (as in MS
Word, gtkspell, OOo,
On 03/12/2010 15:58, Vincent van Ravesteijn wrote:
Op 3-12-2010 15:54, Abdelrazak Younes schreef:
On 03/12/2010 15:52, Stephan Witt wrote:
Am 03.12.2010 um 15:31 schrieb Abdelrazak Younes:
On 30/11/2010 17:33, Pavel Sanda wrote:
Liviu Andronic wrote:
I would suspect that a wavy line
Am 03.12.2010 um 15:54 schrieb Abdelrazak Younes:
On 03/12/2010 15:52, Stephan Witt wrote:
Am 03.12.2010 um 15:31 schrieb Abdelrazak Younes:
On 30/11/2010 17:33, Pavel Sanda wrote:
Liviu Andronic wrote:
I would suspect that a wavy line might be more desirable (as in MS
Stephan Witt wrote:
I did no serious investigation until now...
Only one example:
I tried to adjust the left margin to zoom factor. Guess what happened...
The cursor was misplaced badly.
and soon you'll get another ones ...
few times i tried to touch painting stuff and escaped as far as
Another example:
Imagine you want to increase the thickness of the change bar.
Where to start and what classes has to be changed?
void RowPainter::paintChangeBar() sounds like it :) ;)
and
pi_.pain.fillRectangle(5, yo_ - row_.ascent(), 3, height,
Color_changebar);
5 is the offset
On 03/12/2010 16:18, Pavel Sanda wrote:
Stephan Witt wrote:
I did no serious investigation until now...
Only one example:
I tried to adjust the left margin to zoom factor. Guess what happened...
The cursor was misplaced badly.
and soon you'll get another ones ...
few times i tried to
Op 3-12-2010 16:19, Abdelrazak Younes schreef:
On 03/12/2010 16:18, Pavel Sanda wrote:
Stephan Witt wrote:
I did no serious investigation until now...
Only one example:
I tried to adjust the left margin to zoom factor. Guess what
happened...
The cursor was misplaced badly.
and soon you'll
On 03/12/2010 16:13, Stephan Witt wrote:
Am 03.12.2010 um 15:54 schrieb Abdelrazak Younes:
On 03/12/2010 15:52, Stephan Witt wrote:
Am 03.12.2010 um 15:31 schrieb Abdelrazak Younes:
On 30/11/2010 17:33, Pavel Sanda wrote:
Liviu Andronic wrote:
I
Abdelrazak Younes wrote:
and soon you'll get another ones ...
few times i tried to touch painting stuff and escaped as far as possible
:)
Quite frankly when I look at this LaTeX dependent code I find the painting
code very simple in comparison :-)
then we should establish refugees
Am 03.12.2010 um 16:20 schrieb Vincent van Ravesteijn:
Another example:
Imagine you want to increase the thickness of the change bar.
Where to start and what classes has to be changed?
void RowPainter::paintChangeBar() sounds like it :) ;)
and
pi_.pain.fillRectangle(5, yo_ -
On 03/12/2010 16:23, Vincent van Ravesteijn wrote:
Op 3-12-2010 16:19, Abdelrazak Younes schreef:
On 03/12/2010 16:18, Pavel Sanda wrote:
Stephan Witt wrote:
I did no serious investigation until now...
Only one example:
I tried to adjust the left margin to zoom factor. Guess what
On 12/03/2010 12:21 PM, Abdelrazak Younes wrote:
Hum I have a better one: the graphics stuff!!!
Speaking of which, can you look again at #6949?
Richard
Am 02.12.2010 um 20:08 schrieb Stephan Witt:
> Am 02.12.2010 um 19:49 schrieb Pavel Sanda:
>
>> Stephan Witt wrote:
>>>
>>> Am 02.12.2010 um 18:41 schrieb Pavel Sanda:
>>>
Stephan Witt wrote:
> Ok, but that's what I tried too. I attach some screen shot to compare
> the two
On 30/11/2010 17:33, Pavel Sanda wrote:
Liviu Andronic wrote:
I would suspect that a wavy line might be more desirable (as in MS
Word, gtkspell, OOo, etc.), and if I remember this was the original
implementation (although then the wavy line was too big :) ).
so we are at circles,
Am 03.12.2010 um 15:31 schrieb Abdelrazak Younes:
> On 30/11/2010 17:33, Pavel Sanda wrote:
>> Liviu Andronic wrote:
>>
>>> I would suspect that a wavy line might be more desirable (as in MS
>>> Word, gtkspell, OOo, etc.), and if I remember this was the original
>>> implementation (although
On 03/12/2010 15:52, Stephan Witt wrote:
Am 03.12.2010 um 15:31 schrieb Abdelrazak Younes:
On 30/11/2010 17:33, Pavel Sanda wrote:
Liviu Andronic wrote:
I would suspect that a wavy line might be more desirable (as in MS
Word, gtkspell, OOo, etc.), and if I remember this
Op 3-12-2010 15:54, Abdelrazak Younes schreef:
On 03/12/2010 15:52, Stephan Witt wrote:
Am 03.12.2010 um 15:31 schrieb Abdelrazak Younes:
On 30/11/2010 17:33, Pavel Sanda wrote:
Liviu Andronic wrote:
I would suspect that a wavy line might be more desirable (as in MS
Word, gtkspell, OOo,
On 03/12/2010 15:58, Vincent van Ravesteijn wrote:
Op 3-12-2010 15:54, Abdelrazak Younes schreef:
On 03/12/2010 15:52, Stephan Witt wrote:
Am 03.12.2010 um 15:31 schrieb Abdelrazak Younes:
On 30/11/2010 17:33, Pavel Sanda wrote:
Liviu Andronic wrote:
I would suspect that a wavy line
Am 03.12.2010 um 15:54 schrieb Abdelrazak Younes:
> On 03/12/2010 15:52, Stephan Witt wrote:
>> Am 03.12.2010 um 15:31 schrieb Abdelrazak Younes:
>>
>>
>>> On 30/11/2010 17:33, Pavel Sanda wrote:
>>>
Liviu Andronic wrote:
> I would suspect that a wavy line
Stephan Witt wrote:
> I did no serious investigation until now...
> Only one example:
> I tried to adjust the left margin to zoom factor. Guess what happened...
> The cursor was misplaced badly.
and soon you'll get another ones ...
few times i tried to touch painting stuff and escaped as far as
Another example:
Imagine you want to increase the thickness of the change bar.
Where to start and what classes has to be changed?
void RowPainter::paintChangeBar() sounds like it :) ;)
and
pi_.pain.fillRectangle(5, yo_ - row_.ascent(), 3, height,
Color_changebar);
5 is the offset
On 03/12/2010 16:18, Pavel Sanda wrote:
Stephan Witt wrote:
I did no serious investigation until now...
Only one example:
I tried to adjust the left margin to zoom factor. Guess what happened...
The cursor was misplaced badly.
and soon you'll get another ones ...
few times i tried to
Op 3-12-2010 16:19, Abdelrazak Younes schreef:
On 03/12/2010 16:18, Pavel Sanda wrote:
Stephan Witt wrote:
I did no serious investigation until now...
Only one example:
I tried to adjust the left margin to zoom factor. Guess what
happened...
The cursor was misplaced badly.
and soon you'll
On 03/12/2010 16:13, Stephan Witt wrote:
Am 03.12.2010 um 15:54 schrieb Abdelrazak Younes:
On 03/12/2010 15:52, Stephan Witt wrote:
Am 03.12.2010 um 15:31 schrieb Abdelrazak Younes:
On 30/11/2010 17:33, Pavel Sanda wrote:
Liviu Andronic wrote:
I
Abdelrazak Younes wrote:
>> and soon you'll get another ones ...
>> few times i tried to touch painting stuff and escaped as far as possible
>> :)
>>
>
> Quite frankly when I look at this LaTeX dependent code I find the painting
> code very simple in comparison :-)
then we should establish
Am 03.12.2010 um 16:20 schrieb Vincent van Ravesteijn:
> Another example:
>> Imagine you want to increase the thickness of the change bar.
>> Where to start and what classes has to be changed?
>
> void RowPainter::paintChangeBar() sounds like it :) ;)
>
> and
>
>pi_.pain.fillRectangle(5,
On 03/12/2010 16:23, Vincent van Ravesteijn wrote:
Op 3-12-2010 16:19, Abdelrazak Younes schreef:
On 03/12/2010 16:18, Pavel Sanda wrote:
Stephan Witt wrote:
I did no serious investigation until now...
Only one example:
I tried to adjust the left margin to zoom factor. Guess what
On 12/03/2010 12:21 PM, Abdelrazak Younes wrote:
Hum I have a better one: the graphics stuff!!!
Speaking of which, can you look again at #6949?
Richard
Am 30.11.2010 um 17:33 schrieb Pavel Sanda:
Liviu Andronic wrote:
I would suspect that a wavy line might be more desirable (as in MS
Word, gtkspell, OOo, etc.), and if I remember this was the original
implementation (although then the wavy line was too big :) ).
so we are at circles, since
Stephan Witt wrote:
To break the circle I propose to adjust the line thickness to zoom factor.
The attached patch does this. I think it's better now.
The problem is the somewhat obfuscated rowpainter code.
This makes the patch hard to read, sorry.
Perhaps some kind soul is able to apply
Am 02.12.2010 um 17:47 schrieb Pavel Sanda:
Stephan Witt wrote:
To break the circle I propose to adjust the line thickness to zoom factor.
The attached patch does this. I think it's better now.
The problem is the somewhat obfuscated rowpainter code.
This makes the patch hard to read, sorry.
Stephan Witt wrote:
i tried it and thickness zoom works. however my suspiction that together
with change tracking the current code produce some mess was confirmed :)
Sorry, I'm not sure I understand you.
Do you refer to the screen appearance or to the rowpainter code?
i speak about the
Stephan Witt wrote:
Ok, but that's what I tried too. I attach some screen shot to compare
the two versions, unpatched first - patched second. I cannot see any chaos.
this is how it looks on linux qt 4.6.3, Century Schoolbook L font.
(patched version)
pavel
attachment: p1.pngattachment: p2.png
Am 02.12.2010 um 18:41 schrieb Pavel Sanda:
Stephan Witt wrote:
Ok, but that's what I tried too. I attach some screen shot to compare
the two versions, unpatched first - patched second. I cannot see any chaos.
this is how it looks on linux qt 4.6.3, Century Schoolbook L font.
(patched
Stephan Witt wrote:
Am 02.12.2010 um 18:41 schrieb Pavel Sanda:
Stephan Witt wrote:
Ok, but that's what I tried too. I attach some screen shot to compare
the two versions, unpatched first - patched second. I cannot see any chaos.
this is how it looks on linux qt 4.6.3, Century
Am 02.12.2010 um 19:49 schrieb Pavel Sanda:
Stephan Witt wrote:
Am 02.12.2010 um 18:41 schrieb Pavel Sanda:
Stephan Witt wrote:
Ok, but that's what I tried too. I attach some screen shot to compare
the two versions, unpatched first - patched second. I cannot see any chaos.
this is how
Stephan Witt wrote:
Do you refer to the different vertical line positions?
i refer to the the red line jumping like a goat on the hills. this is
intended?
Yes. Do you have another idea?
aha :) i didn't got that its intended...
The optimal solution would be a two pass algorithm for
Pavel Sanda wrote:
Stephan Witt wrote:
btw i have unrelated question.
the native string translation. this is standard naming in mac world or our
invetion? i wonder whether it should be translated or is it terminus technicus
like other aspell/enchant/hunspell strings which i'm going to kill right
Am 02.12.2010 um 21:12 schrieb Pavel Sanda:
Pavel Sanda wrote:
btw i have unrelated question.
the native string translation. this is standard naming in mac world or our
invetion? i wonder whether it should be translated or is it terminus technicus
like other aspell/enchant/hunspell strings
Stephan Witt wrote:
Am 02.12.2010 um 21:12 schrieb Pavel Sanda:
Pavel Sanda wrote:
btw i have unrelated question.
the native string translation. this is standard naming in mac world or our
invetion? i wonder whether it should be translated or is it terminus
technicus
like other
Am 02.12.2010 um 21:32 schrieb Pavel Sanda:
Stephan Witt wrote:
Am 02.12.2010 um 21:12 schrieb Pavel Sanda:
Pavel Sanda wrote:
btw i have unrelated question.
the native string translation. this is standard naming in mac world or our
invetion? i wonder whether it should be translated or
Stephan Witt wrote:
i see, so using applespell is correct, right?
Hmm.. I'm not sure.
Perhaps Mac OS Speller or OS Spell Service?
i will use Mac OS Speller, thanks.
pavel
Am 30.11.2010 um 17:33 schrieb Pavel Sanda:
> Liviu Andronic wrote:
>> I would suspect that a wavy line might be more desirable (as in MS
>> Word, gtkspell, OOo, etc.), and if I remember this was the original
>> implementation (although then the wavy line was too big :) ).
>
> so we are at
Stephan Witt wrote:
> To break the circle I propose to adjust the line thickness to zoom factor.
> The attached patch does this. I think it's better now.
> The problem is the somewhat obfuscated rowpainter code.
> This makes the patch hard to read, sorry.
>
> Perhaps some kind soul is able to
Am 02.12.2010 um 17:47 schrieb Pavel Sanda:
> Stephan Witt wrote:
>> To break the circle I propose to adjust the line thickness to zoom factor.
>> The attached patch does this. I think it's better now.
>> The problem is the somewhat obfuscated rowpainter code.
>> This makes the patch hard to
Stephan Witt wrote:
> > i tried it and thickness zoom works. however my suspiction that together
> > with change tracking the current code produce some mess was confirmed :)
>
> Sorry, I'm not sure I understand you.
> Do you refer to the screen appearance or to the rowpainter code?
i speak about
Stephan Witt wrote:
> Ok, but that's what I tried too. I attach some screen shot to compare
> the two versions, unpatched first - patched second. I cannot see any chaos.
this is how it looks on linux qt 4.6.3, Century Schoolbook L font.
(patched version)
pavel
<><>
Am 02.12.2010 um 18:41 schrieb Pavel Sanda:
> Stephan Witt wrote:
>> Ok, but that's what I tried too. I attach some screen shot to compare
>> the two versions, unpatched first - patched second. I cannot see any chaos.
>
> this is how it looks on linux qt 4.6.3, Century Schoolbook L font.
>
Stephan Witt wrote:
>
> Am 02.12.2010 um 18:41 schrieb Pavel Sanda:
>
> > Stephan Witt wrote:
> >> Ok, but that's what I tried too. I attach some screen shot to compare
> >> the two versions, unpatched first - patched second. I cannot see any chaos.
> >
> > this is how it looks on linux qt
Am 02.12.2010 um 19:49 schrieb Pavel Sanda:
> Stephan Witt wrote:
>>
>> Am 02.12.2010 um 18:41 schrieb Pavel Sanda:
>>
>>> Stephan Witt wrote:
Ok, but that's what I tried too. I attach some screen shot to compare
the two versions, unpatched first - patched second. I cannot see any
Stephan Witt wrote:
> >> Do you refer to the different vertical line positions?
> >
> > i refer to the the red line jumping like a goat on the hills. this is
> > intended?
>
> Yes. Do you have another idea?
aha :) i didn't got that its intended...
> The optimal solution would be a two pass
Pavel Sanda wrote:
> Stephan Witt wrote:
btw i have unrelated question.
the "native" string translation. this is standard naming in mac world or our
invetion? i wonder whether it should be translated or is it terminus technicus
like other aspell/enchant/hunspell strings which i'm going to kill
Am 02.12.2010 um 21:12 schrieb Pavel Sanda:
> Pavel Sanda wrote:
>
> btw i have unrelated question.
> the "native" string translation. this is standard naming in mac world or our
> invetion? i wonder whether it should be translated or is it terminus technicus
> like other aspell/enchant/hunspell
Stephan Witt wrote:
> Am 02.12.2010 um 21:12 schrieb Pavel Sanda:
>
> > Pavel Sanda wrote:
> >
> > btw i have unrelated question.
> > the "native" string translation. this is standard naming in mac world or our
> > invetion? i wonder whether it should be translated or is it terminus
> >
Am 02.12.2010 um 21:32 schrieb Pavel Sanda:
> Stephan Witt wrote:
>> Am 02.12.2010 um 21:12 schrieb Pavel Sanda:
>>
>>> Pavel Sanda wrote:
>>>
>>> btw i have unrelated question.
>>> the "native" string translation. this is standard naming in mac world or our
>>> invetion? i wonder whether it
Stephan Witt wrote:
> > i see, so using applespell is correct, right?
>
> Hmm.. I'm not sure.
> Perhaps "Mac OS Speller" or "OS Spell Service"?
i will use Mac OS Speller, thanks.
pavel
Am 30.11.2010 um 08:21 schrieb Michal:
I have to admit I think it costs not much time to report a bug in
LyX's bug tracker. Fortunately, it's not bugzilla. :-)
And some of the bugs you reported are easier to fix with example
files.
Well, I've just reported the bugs (see my other mail on
Could you please specify to which bug reports should I attach
examples?
Only if it's not too much work...
Thank you, it is very considerate of you. Such a rare thing
nowadays! :)
* For ticket 7115 a screen shot and a small example file would be
helpful.
Am 30.11.2010 um 11:58 schrieb Michal:
* For ticket 7115 a screen shot and a small example file would be
helpful. http://www.lyx.org/trac/ticket/7115
But as I cannot solve it, I'm only guessing.
Unfortunately, I don't own a copy of Scientific Workplace.
Me too. I don't have Windows
Liviu Andronic wrote:
I would suspect that a wavy line might be more desirable (as in MS
Word, gtkspell, OOo, etc.), and if I remember this was the original
implementation (although then the wavy line was too big :) ).
so we are at circles, since the wavy line was killed not so long ago :)
not
Am 30.11.2010 um 08:21 schrieb Michal:
>> I have to admit I think it costs not much time to report a bug in
>> LyX's bug tracker. Fortunately, it's not bugzilla. :-)
>> And some of the bugs you reported are easier to fix with example
>> files.
>Well, I've just reported the bugs (see my other
> >Could you please specify to which bug reports should I attach
> > examples?
>
> Only if it's not too much work...
Thank you, it is very considerate of you. Such a rare thing
nowadays! :)
> * For ticket 7115 a screen shot and a small example file would be
> helpful.
Am 30.11.2010 um 11:58 schrieb Michal:
>> * For ticket 7115 a screen shot and a small example file would be
>> helpful. http://www.lyx.org/trac/ticket/7115
>>
>> But as I cannot solve it, I'm only guessing.
>Unfortunately, I don't own a copy of Scientific Workplace.
Me too. I don't have
Liviu Andronic wrote:
> I would suspect that a wavy line might be more desirable (as in MS
> Word, gtkspell, OOo, etc.), and if I remember this was the original
> implementation (although then the wavy line was too big :) ).
so we are at circles, since the wavy line was killed not so long ago :)
.
And I've not seen any bug disappearing by mentioning.
Some bugs are resorting when the sun light is raising...
...but I've not heard of it about software bugs. :-)
To continue the digression.. Some people consider reporting bugs as a
form of contributing to an open-source project
I don't want to be offending.
But honestly, fixing bugs is a time-consuming task too.
And I've not seen any bug disappearing by mentioning.
Some bugs are resorting when the sun light is raising...
...but I've not heard of it about software bugs. :-)
You don't want to be offending, so
Am 29.11.2010 um 12:42 schrieb Michal:
I don't want to be offending.
But honestly, fixing bugs is a time-consuming task too.
And I've not seen any bug disappearing by mentioning.
Some bugs are resorting when the sun light is raising...
...but I've not heard of it about software bugs
2010/11/28 Michal ms-li...@ms.sebdan.com:
In this mail I've collected all the bugs with LyX 2.0beta1 I've
spotted so far. Overall, the experience has been very pleasant, but
there are some glitches worth correcting. My platform is (for now) Win
XP SP3 Polish.
If something is unclear,
Vincent van Ravesteijn wrote:
[BUG #6]
Document settings cannot be reverted via undo. Or is it by design?
That might be by design. It's rather unwanted that settings are undone
and the user doesn't see this happen.
this is a regression which works in 1.6, i remember to use it...
pavel
Hello
On Tue, Nov 30, 2010 at 1:37 AM, Vincent van Ravesteijn v...@lyx.org wrote:
[BUG #5]
The dotted line used to mark misspelled words is almost invisible
(under some conditions). Is the color/thickness of the line
configurable?
No, this is hardcoded. Under which conditions is it
1 - 100 of 180 matches
Mail list logo