Re: powerdot install

2006-02-03 Thread Herbert Voss
Andre Poenitz wrote: On Wed, Feb 01, 2006 at 12:05:03PM +0100, Karsten Heymann wrote: Looking forward to Berlin, Aehm... what's in Berlin? Did I miss something? http://www.dante.de/dante2006/ Herbert

Re: Bug 1934: the plot thickens

2006-02-03 Thread Andre Poenitz
On Mon, Jan 30, 2006 at 10:18:52AM +0100, Jean-Marc Lasgouttes wrote: > > "Andre" == Andre Poenitz <[EMAIL PROTECTED]> writes: > > Andre> It is at least theoretically sound, see my post on 'four phase > Andre> drawing'. It's basically exactly this, albeit for mathed only. > > Where? Aehm...

Re: powerdot install

2006-02-03 Thread Andre Poenitz
On Wed, Feb 01, 2006 at 12:05:03PM +0100, Karsten Heymann wrote: > Looking forward to Berlin, Aehm... what's in Berlin? Did I miss something? Andre'

Re: Blue line thoughts, and a patch

2006-02-03 Thread Martin Vermeer
On Fri, Feb 03, 2006 at 10:19:45PM +0100, Georg Baum wrote: > Am Freitag, 3. Februar 2006 10:34 schrieb Martin Vermeer: > > OK in principle... but could you list in detail which pieces of the > > patch you want included and which excluded? > > Here is the patch. It is IMO safe for 1.4.0, and it fi

Re: help needed for LyX's configure script

2006-02-03 Thread Paul A. Rubin
Uwe Stöhr wrote: I want to add a section in LyX's configure script to check for viewers of LaTeX-files. I used the following code: - # Search something to view LaTeX-files echo $ac_n "checking for an editor to view LaTeX-files""... $ac_c" echo "$ac_t""(jEdit WinShell TeXnicCenter WinEdt Win

Re: Blue line thoughts, and a patch

2006-02-03 Thread Helge Hafting
Georg Baum wrote: I also think that something should be done here, but if you read Martins latest post then you'll see that the current patch makes things better for tables etc, and worse for quotes and other special characters that are implemented as an inset. I see. Quotes, ellipsis and

Re: Blue line thoughts, and a patch

2006-02-03 Thread Georg Baum
Am Freitag, 3. Februar 2006 10:34 schrieb Martin Vermeer: > OK in principle... but could you list in detail which pieces of the > patch you want included and which excluded? Here is the patch. It is IMO safe for 1.4.0, and it fixes all language related problems I could think of except changing la

Re: [patch] bug 2241: LyX crashes on cursor down

2006-02-03 Thread Andre Poenitz
On Fri, Jan 27, 2006 at 03:09:32PM +0100, Jean-Marc Lasgouttes wrote: > > "Juergen" == Juergen Spitzmueller <[EMAIL PROTECTED]> writes: > > Juergen> Juergen Spitzmueller wrote: > >> Instead, we could implement a > >> dociterator::forwardPosIgnoreCollapsed() method, which basically > >> contain

Re: [patch] bug 2241: LyX crashes on cursor down

2006-02-03 Thread Andre Poenitz
n Fri, Jan 27, 2006 at 11:41:05AM +0100, Juergen Spitzmueller wrote: > Juergen Spitzmueller wrote: > > I think I found it: bruteFind in cursor.C > > Attached is what I came up with. Now the cursor does not move into > collapsed insets anymore, and the crash is fixed as well. Instead, we > could i

Re: Renaming macros

2006-02-03 Thread Andre Poenitz
On Sat, Jan 28, 2006 at 01:59:56PM +0100, Georg Baum wrote: > Am Freitag, 27. Januar 2006 03:20 schrieb Beck, Andrew Thomas - BECAT001: > > OK, here is a better formatted patch, preserving encoding etc. Thanks > > for the feedback. The update is still being done in metrics() in the > > same way tha

Re: [patch] fix bug 2174

2006-02-03 Thread Lars Gullik Bjønnes
Georg Baum <[EMAIL PROTECTED]> writes: | Juergen Spitzmueller wrote: | | > Works for me as well. | | Fine. Is this OK for 1.4.0? ok -- Lgb

Re: Blue line thoughts, and a patch

2006-02-03 Thread Martin Vermeer
On Fri, Feb 03, 2006 at 06:27:13PM +0100, Georg Baum wrote: > Martin Vermeer wrote: > > > Hmmm, I think that you are correct. Patched 1.4. applies the "outside" > > font at an inset to the inset content, and (if I understand you > > correctly) then writes the change back to the .lyx file on save.

Re: Blue line thoughts, and a patch

2006-02-03 Thread Georg Baum
Martin Vermeer wrote: > Hmmm, I think that you are correct. Patched 1.4. applies the "outside" > font at an inset to the inset content, and (if I understand you > correctly) then writes the change back to the .lyx file on save. > Unacceptable, as a document will look different when loaded the seco

Re: Blue line thoughts, and a patch

2006-02-03 Thread Helge Hafting
On Fri, Feb 03, 2006 at 04:08:49PM +0100, Jean-Marc Lasgouttes wrote: > > "Helge" == Helge Hafting <[EMAIL PROTECTED]> writes: > > Helge> * Selecting lots of text (that includes insets) and changing > Helge> the language on the selection has problems. > > This a more general problem with fon

Re: [patch] fix bug 2174

2006-02-03 Thread Georg Baum
Jean-Marc Lasgouttes wrote: >> "Georg" == Georg Baum >> <[EMAIL PROTECTED]> >> writes: > > Georg> Juergen Spitzmueller wrote: >>> Works for me as well. > > Georg> Fine. Is this OK for 1.4.0? > > I do not like the hardcoding of lyx13x. Me neither, but I fear that the other possibili

Re: Blue line thoughts, and a patch

2006-02-03 Thread Martin Vermeer
On Fri, Feb 03, 2006 at 04:05:11PM +0100, Georg Baum wrote: > Helge Hafting wrote: ... > Martins patch fixes this bug for the language case by redefining the > semantics of font language in insets (correct me if I understood something > wrong). This is the wrong way IMHO, see the patch in bugzil

Re: bug 2026 again

2006-02-03 Thread Georg Baum
Jean-Marc Lasgouttes wrote: > Or rather an empty layout name? You mean \layout "" ? That works in both 1.3.7 and 1.4cvs (but produces the warning Layout '""' does not exist in textclass 'article'. Trying to use default layout instead. in 1.3.7, which is acceptable IMO. It has also the advant

Re: [patch] fix bug 2174

2006-02-03 Thread Jean-Marc Lasgouttes
> "Georg" == Georg Baum <[EMAIL PROTECTED]> writes: Georg> Juergen Spitzmueller wrote: >> Works for me as well. Georg> Fine. Is this OK for 1.4.0? I do not like the hardcoding of lyx13x. If you are going to do that, why not directly add lyx13x to the list of backends? Wouldn't that be less c

Re: 2249

2006-02-03 Thread Martin Vermeer
On Fri, Feb 03, 2006 at 04:31:12PM +0100, Jean-Marc Lasgouttes wrote: > > "Martin" == Martin Vermeer <[EMAIL PROTECTED]> writes: > > Martin> Does it work for you / shall I commit? - Martin > > It works perfectly and the patch looks good. > > Please commit. > > JMarc Committed, - Martin

Re: Blue line thoughts, and a patch

2006-02-03 Thread Martin Vermeer
On Fri, Feb 03, 2006 at 04:45:46PM +0100, Jean-Marc Lasgouttes wrote: > > "Martin" == Martin Vermeer <[EMAIL PROTECTED]> writes: > > >> Yes, but how do we determine the value of this parameter? We > >> basically need a list of insets that need the blue line at the > >> bottom -> huge switch or

Re: bug 2026 again

2006-02-03 Thread Jean-Marc Lasgouttes
> "Georg" == Georg Baum <[EMAIL PROTECTED]> writes: >> In 1.4, we could decide that some special layout name like >> is the default layout. Georg> Maybe that, or we could declare the already existing feature Georg> that no layout name is required official. Or rather an empty layout name?

Re: bug 2026 again

2006-02-03 Thread Georg Baum
Jean-Marc Lasgouttes wrote: > For lyx <= 1.3, what happens if there is no \layout at the beginning > of an ERT inset? Do it choose the default layout? lyx2lyx will complain if there is no \layout (in convert_collapsable and revert_collapsable). I don't know what LyX does if there is no \layout, b

Re: Blue line thoughts, and a patch

2006-02-03 Thread Jean-Marc Lasgouttes
> "Martin" == Martin Vermeer <[EMAIL PROTECTED]> writes: >> Yes, but how do we determine the value of this parameter? We >> basically need a list of insets that need the blue line at the >> bottom -> huge switch or virtual method, or do you see any other >> possibility? Martin> This is an ind

Re: bug 2026 again

2006-02-03 Thread Jean-Marc Lasgouttes
> "Georg" == Georg Baum <[EMAIL PROTECTED]> writes: >> Do you think it is possible to fix the most annoying ones in >> lyx2lyx? Georg> It is impossible without knowing the default layout name, Georg> because lyx2lyx really needs that at several occasions: - ERT Georg> cleanup (convert_ert_pa

Re: Blue line thoughts, and a patch

2006-02-03 Thread Georg Baum
Why +2 for insets and +1 for normal text? I'd prefer Martin Vermeer wrote: > -void paintForeignMark(double orig_x, LyXFont const & font); > +void paintForeignMark(double orig_x, LyXFont const & font, int > desc = 1); desc = 0); > -int const y = yo_ + 1; > +int

Re: bug 2026 again

2006-02-03 Thread Georg Baum
Jean-Marc Lasgouttes wrote: >> "Georg" == Georg Baum >> <[EMAIL PROTECTED]> >> writes: > > Georg> It uses BriefText as layout for ERT because that is the default > Georg> layout of the textclass (I guess this is clear). It is changed > Georg> to Standard by lyx2lyx because I thought t

Re: Blue line thoughts, and a patch

2006-02-03 Thread Jean-Marc Lasgouttes
> "Helge" == Helge Hafting <[EMAIL PROTECTED]> writes: Helge> * Selecting lots of text (that includes insets) and changing Helge> the language on the selection has problems. This a more general problem with fonts over a selection. JMarc

Re: Blue line thoughts, and a patch

2006-02-03 Thread Georg Baum
Helge Hafting wrote: > I have no idea of compatibility problems. My problem has always been > bugs with multilingual files, such as: > > * Set the document language to something else than the default language > configured in lyx. Notice that some insets either have, or seem to > have, the l

Re: Blue line thoughts, and a patch

2006-02-03 Thread Martin Vermeer
On Fri, 2006-02-03 at 11:28 +0100, Georg Baum wrote: > Martin Vermeer wrote: ... > > I did. Quotes etc. indeed do not get underlined with my patch. So it is > > wrong. A solution might be to give paintForeignMark an additional > > "descent" parameter and use that to put the line at the right leve

1.4cvs performance problem over network when adding a paragraph

2006-02-03 Thread Helge Hafting
There is a strange performance problem when displaying a lyx that is running on another machine. (ADSL connection) Most editing operations are fine (writing text, deleting, scrolling) there is no bandwith problem. But press enter so that a new paragraph is created. This operation takes 6 second

Re: bug 2026 again

2006-02-03 Thread Jean-Marc Lasgouttes
> "Georg" == Georg Baum <[EMAIL PROTECTED]> writes: Georg> It uses BriefText as layout for ERT because that is the default Georg> layout of the textclass (I guess this is clear). It is changed Georg> to Standard by lyx2lyx because I thought that the default Georg> layout of any textclass is al

Re: Blue line thoughts, and a patch

2006-02-03 Thread Helge Hafting
Georg Baum wrote: Martin Vermeer wrote: Hmmm. Actually this is straightforwardly fixable. It's just a policy choice, how we understand noFontChange(). See attached. Only text.C and rowpainter.C were changed. Works for me... 1.3 does it this way too (in fact, it has *only* noFontChange-type

Re: bug 2026 again

2006-02-03 Thread Georg Baum
Jean-Marc Lasgouttes wrote: > If I understand correctly, the problem is that we have a 1.3.x > document that uses BriefText as layout for ERT, and you force it to > become Standard instead. Correct. Unfortunately this problem could also occur for 1.4 -> 1.3 conversions > Why is that? It uses B

Re: [SPAM] Re: bug 2026 again

2006-02-03 Thread Jean-Marc Lasgouttes
> "Georg" == Georg Baum <[EMAIL PROTECTED]> writes: Georg> Jean-Marc Lasgouttes wrote: >> What about the simple solution of reintroducing Standard in the >> broken layouts? Georg> I thought you did not want to require Standard? This solution Georg> is easy, but note that my first analysis was

Re: [SPAM] Re: bug 2026 again

2006-02-03 Thread Georg Baum
Jean-Marc Lasgouttes wrote: > What about the simple solution of reintroducing Standard in the broken > layouts? I thought you did not want to require Standard? This solution is easy, but note that my first analysis was wrong, it does not mean "reintroduce" but "introduce". If we are going to do t

Re: [SPAM] Re: bug 2026 again

2006-02-03 Thread Jose' Matos
On Friday 03 February 2006 13:13, Jean-Marc Lasgouttes wrote: > > What about the simple solution of reintroducing Standard in the broken > layouts? That is the easy short term solution for several reasons. > JMarc -- José Abílio

Re: [SPAM] Re: bug 2026 again

2006-02-03 Thread Jean-Marc Lasgouttes
> "Jose'" == Jose' Matos <[EMAIL PROTECTED]> writes: >> Given the fact that 1.3.7 is already out with the broken lyx2lyx I >> tend now to polish this and put it in 1.4.1, and for 1.4.0 to tell >> users to do What about the simple solution of reintroducing Standard in the broken layouts? JMar

Re: Blue line thoughts, and a patch

2006-02-03 Thread Georg Baum
Martin Vermeer wrote: > On Fri, 2006-02-03 at 09:29 +0100, Georg Baum wrote: >> - The attached 1.3 file is read correctly with and without your patch. >> Your or Helge found a problem with 1.3 compatibility, but I can't find it >> anymore. Could you please give an example again? > > A file with N

Re: [patch] fix bug 2174

2006-02-03 Thread Georg Baum
Juergen Spitzmueller wrote: > Works for me as well. Fine. Is this OK for 1.4.0? Georg

Re: Blue line thoughts, and a patch

2006-02-03 Thread Martin Vermeer
On Fri, 2006-02-03 at 09:29 +0100, Georg Baum wrote: > Martin Vermeer wrote: > > > Hmmm. Actually this is straightforwardly fixable. It's just a policy > > choice, how we understand noFontChange(). See attached. Only text.C and > > rowpainter.C were changed. Works for me... 1.3 does it this way to

Re: [patch] fix bug 2174

2006-02-03 Thread Juergen Spitzmueller
Georg Baum wrote: > Here it is. It works for me, could you please test it, too? Works for me as well. Jürgen

Re: Blue line thoughts, and a patch

2006-02-03 Thread Georg Baum
Martin Vermeer wrote: > Hmmm. Actually this is straightforwardly fixable. It's just a policy > choice, how we understand noFontChange(). See attached. Only text.C and > rowpainter.C were changed. Works for me... 1.3 does it this way too (in > fact, it has *only* noFontChange-type insets; but langu

Re: crash: click on macro instantiation - bug 2060

2006-02-03 Thread Georg Baum
Beck, Andrew Thomas - BECAT001 wrote: > >>Ok, I see now. Unfortunately your patch is not correct IMHO: If I click on >>argument 3 I expect the cursor to appear in argument 3, not in the first >>one as your patch does. In perinciple it is ok to call > > Of course you tested your original patch to