\centerline{} support for wide graphics and tables

2013-03-18 Thread Scott Kostyshak
When inserting a graphic or table whose width is larger than \textwidth, the extra width spills over to the right margin. This might be desired in some cases, but in other cases it is nice to center the graphic or table on the page. Using \centerline{}, the extra width is split evenly across the le

Re: LyX developer meeting or not ?

2013-03-18 Thread Pavel Sanda
Abdelrazak Younes wrote: >> Anyway, I think flat directory structure is something that should be done >> just before release, unless git is better that I think at following >> renames. Given all the problems which could arise in make phase due to changed paths I would prefer if we flatten before

Re: [patch] fix branch regression bug 8590

2013-03-18 Thread Uwe Stöhr
Am 16.03.2013 16:24, schrieb Guenter Milde: Besides try-and error with different Cyrillic-using languages, you can also look into Babel's *.ldf files for the respective languages. For example russian.ldf comes with code to set the font encoding to one of the Cyrillic encodings (OT2, T2A, T2B, T2

Re: [patch] fix branch regression bug 8590

2013-03-18 Thread Uwe Stöhr
Am 15.03.2013 23:37, schrieb Enrico Forestieri: I simply changed the document language of http://www.lyx.org/trac/raw-attachment/ticket/8590/cyrillic.lyx I still can only reproduce this for Serbian and Kazakh. The reason is that babel has no support for Cyrillic Serbian and that there is no s

Re: LyX developer meeting or not ?

2013-03-18 Thread Abdelrazak Younes
On 18/03/2013 10:21, Jean-Marc Lasgouttes wrote: Le 17/03/2013 15:25, Abdelrazak Younes a écrit : And off course: stabilize devel for 2.1 release. Another plan would be to relelase 2.1 before the meeting. Is this possible? I am not sur e that we have so many regressions wrt 2.0 in current t

Re: LyX 2.1 - What is the status ?

2013-03-18 Thread Pavel Sanda
Vincent van Ravesteijn wrote: > - What is the overall impression of current trunk ? > - What features are in progress but needs finishing ? > - Which new features do you still want to put in before 2.1 ? Vincent, do you think it's possible that you find time to look on #6889 before releasing 2.1?

LyX 2.1 - What is the status ?

2013-03-18 Thread Vincent van Ravesteijn
Hi all, As there seems to be a consensus about releasing 2.1. I want to ignite the LyX 2.1 release procedure. Before I come up with a planning and/or a feature freeze, I would like to know what the status of the current trunk is. - What is the overall impression of current trunk ? - What fe

Re: editing math in lyx

2013-03-18 Thread Alex Vergara Gil
- Original Message - From: "Scott Kostyshak" To: "Abdelrazak Younes" Cc: "Alex Vergara Gil" ; ; Sent: Sunday, March 17, 2013 12:11 PM Subject: Re: editing math in lyx This sounds like a not very hard feature to implement, maybe without touching C++ even. So why don't you implement

Advanced search slowness

2013-03-18 Thread Kornel Benko
The slowness in normal search part happens, because we have very inefficient algorithm. Suppose we have a string "This is a string." at the cursor position, and we search for "abcd". The method MatchStringAdv::findAux() will be called now successively from findForwardAdv() incrementing the cursor

Aw: Re: LyX developer meeting or not ?

2013-03-18 Thread Uwe Stöhr
Von: "Jean-Marc Lasgouttes" >> And off course: stabilize devel for 2.1 release. > Another plan would be to relelase 2.1 before the meeting. Is this> possible? I am not sur e that we have so many regressions wrt 2.0 in> current trunk.I already proposed this but it turned out that this

Re: LyX developer meeting or not ?

2013-03-18 Thread Jean-Marc Lasgouttes
Le 17/03/2013 15:25, Abdelrazak Younes a écrit : The best solution is of course to entice somebody more competent (yes, Abdel I am looking at you!) to do it :) Not sure I still have the competence... but we can try :-) And the second strnght you have is that you understand something about Rt

Re: trunk: ps2pdf woes

2013-03-18 Thread Jürgen Spitzmüller
Richard Heck wrote: > Certainly it seems to be a mistake to use this same format for both > purposes, even independently of this problem. So I'd say "yes". And > "thank you". I endorse that. Jürgen