hi,
i just found that my document settings dialog is not able to be contained in
800x600 area. considering that they are maybe people who still live with older
hardware we should reduce the size a bit. maybe time to put modules into its
own tab? i was bit annoyed that the module-listing combo is a
Andre Poenitz wrote:
On Tue, Oct 14, 2008 at 12:19:28AM +0200, Uwe Stöhr wrote:
BTW, does the fact that you are now working on this mean that the
tex2lyx-python ghost is finally dead?
What was this ghost?
Some people were pondering re-doing tex2lyx in python. There even seems
s
> i think the code is still wrong:
>
> if both \pdf_pagebackref true & \pdf_backref true are set then you put two
> different \pdf_backref into lyx file.
I also fixed this case now.
thanks and regards
Uwe
Tommaso Cucinotta wrote:
> The attached file
> src/frontends/qt4/ui/SearchAdvUi.ui
> hopefully looks like better.
thanks, commited. btw the now-disappeared replace-field means
replacing was not working up to now, right?
i also setup the following wiki for gathering the bugs around:
http://wiki.ly
Uwe Stöhr wrote:
> We cannot do it correctly, but at least that it looks the same in the
> output and this is a must have.
i have said from the very begining we have different views :)
> > i commited the current version and will review lyx2lyx part you commit
> later.
>
> I've put it in. I test
On Tue, Oct 14, 2008 at 01:02:24AM +0200, Pavel Sanda wrote:
> Abdelrazak Younes wrote:
> > OK, I missed that part of the patch indeed. Dov confirmed that it is OK so,
> > Pavel, if you have it applied locally please commit.
>
> even if i don't speak french?
That's fine as long as you eat whale.
Abdelrazak Younes wrote:
> OK, I missed that part of the patch indeed. Dov confirmed that it is OK so,
> Pavel, if you have it applied locally please commit.
even if i don't speak french?
pavel
Andre Poenitz schrieb:
So I am glad to hear that I am allowed to contribute to this excellent
piece of code even if only one developer agrees with me.
You are welcome ;-)
regards Uwe
On Tue, Oct 14, 2008 at 12:19:28AM +0200, Uwe Stöhr wrote:
> > BTW, does the fact that you are now working on this mean that the
> > tex2lyx-python ghost is finally dead?
>
> What was this ghost?
Some people were pondering re-doing tex2lyx in python. There even seems
some bits of python out there
On Tue, Oct 14, 2008 at 12:04:59AM +0200, Uwe Stöhr wrote:
> Andre Poenitz schrieb:
>
>> According to the bug description that's not a single file but all files
>> that come from a XeTeX/kile combination.
>
> OK then some more files than one ;-) but no real solution. Could you
> please add a comme
>> The opposite direction also
>> works, as then nothing is done,
>
> which is the culprit of the problem. normal user won't note that info
> disapeared into preamble and will look inot document settings. he will
> even try to switch hyperref again
> and i just imagine what will happen then...
Th
> BTW, does the fact that you are now working on this mean that the
> tex2lyx-python ghost is finally dead?
What was this ghost? I'm now working for over a year on tex2lyx, fixed many bugs and added lots of
new features for every past LyX 1.5.x release. Also JMarc and Jürgen contributed a lot, s
Andre Poenitz schrieb:
You should probably switch to French...
Could you please be a bit more specific or do you make jokes about me?
Nobody in his right mind would make jokes about upset Germans.
I was not upset, but wasn't sure if this was fun or a hint that the comment in the TeX files
Andre Poenitz schrieb:
According to the bug description that's not a single file but all files
that come from a XeTeX/kile combination.
OK then some more files than one ;-) but no real solution. Could you please add a comment that this
code is there to assume the encoding from LaTeX files cre
On Mon, Oct 13, 2008 at 11:17:56PM +0200, Jean-Marc Lasgouttes wrote:
> Andre Poenitz <[EMAIL PROTECTED]> writes:
> > That assertion seems incompatible with e.g. line 2244-2249 in
> > tex2lyx/text.cpp, which, incidentally have been changed last by you.
>
> Once upon a time,
That was 03/03/03 18:4
Andre Poenitz <[EMAIL PROTECTED]> writes:
> That assertion seems incompatible with e.g. line 2244-2249 in
> tex2lyx/text.cpp, which, incidentally have been changed last by you.
Once upon a time, a lazy gremlin decided that latin1 German umlauts were
an absolute prerequisite for a tex->lyx converte
On 13/10/2008 21:31, Georg Baum wrote:
Both ascii and latin1 are a subset of utf8,
ascii certainly but latin1, I don't think so, AFAIK. latin1 is a subset
of ucs4/utf32, is that what you meant?
Abdel.
On Mon, Oct 13, 2008 at 11:02:12PM +0200, Jean-Marc Lasgouttes wrote:
> Andre Poenitz <[EMAIL PROTECTED]> writes:
> > Acually I think we should switch .lyx encoding to utf8 for good. Of
> > course, the parameter to \inputencoding can and should be kept and if
> > possible used in the output, but ot
Andre Poenitz <[EMAIL PROTECTED]> writes:
> Acually I think we should switch .lyx encoding to utf8 for good. Of
> course, the parameter to \inputencoding can and should be kept and if
> possible used in the output, but otherwise there is no real reason to
> keep an uncertain encoding in the .lyx fo
On 13/10/2008 22:11, Vincent van Ravesteijn wrote:
The piece of code you showed is indeed just renaming, but I think this
makes more sense than the way it was before: if the end margin is
selected, only the left margin is important for RTL text and the right
margin for LTR text.
By the way, bv_-
Am 13.10.2008 um 21:40 schrieb Dionysios:
Hi, incredibleware team!
Macro representation changed
From:
LyX 1.5.1
Ubuntu 7.04
TeXLive
\newcommand{\beginend}[2]{\begin{#1}#2\end{#1}}
To:
LyX 1.6.0 RC3
Windows XP SP2
MiKTeX 2.5
\global\def\beginend#1#2{\begin{#1}#2\end{#1}}
Is this meant to be
On Mon, 2008-10-13 at 09:01 +0200, Abdelrazak Younes wrote:
> On 12/10/2008 21:24, Vincent van Ravesteijn wrote:
> > Vincent van Ravesteijn wrote:
> >
> >> This patch solves some problems with painting selections in Insets.
> >> These are:
> >> - multiline selections paint in left margin of the
On Mon, Oct 13, 2008 at 09:31:34PM +0200, Georg Baum wrote:
> Uwe Stöhr wrote:
>
> > "magic" does not help in general as we will still stay sticked where we
> > are. We need a general solution to be able to create a lyxformat newer
> > than 248. I attached a LyX file and its TeX output. This one c
Hi, incredibleware team!
Macro representation changed
From:
LyX 1.5.1
Ubuntu 7.04
TeXLive
\newcommand{\beginend}[2]{\begin{#1}#2\end{#1}}
To:
LyX 1.6.0 RC3
Windows XP SP2
MiKTeX 2.5
\global\def\beginend#1#2{\begin{#1}#2\end{#1}}
Both ways seem identical; however, this
%%
Uwe Stöhr wrote:
> "magic" does not help in general as we will still stay sticked where we
> are. We need a general solution to be able to create a lyxformat newer
> than 248. I attached a LyX file and its TeX output. This one compiles fine
> with latex and pdflatex. The exercise we have is to imp
On Mon, Oct 13, 2008 at 12:39:22PM +0200, Uwe Stöhr wrote:
> Abdelrazak Younes schrieb:
>
>>> You rever to bug 3035, right? This is the showstopper, but you don't
>>> fix it. Bug 4299 was marked as duplicate of this. I'm still confused
>>> what you intention was.
>>
>> You should probably switc
On Mon, Oct 13, 2008 at 12:14:44PM +0200, Uwe Stöhr wrote:
> Andre Poenitz schrieb:
>
>>> Maybe I am wrong, but you cannot assume an encoding from the length
>>> of a comment.
>>
>> There are a lot more serious assumptions in the tex2lyx code. Given
>> any data in an unknown encoding you will have
On Monday 2008-10-13 06:00, bb wrote:
> Dear lyx crew,
>
> There I have a ambivalent display of german characters in lyx -
> here a description : I use lyx in the german version with debian
> 4.0r4a 64 bit with a german localisation and get a correct display
> of ä,ö,ü and ß in the german text in
Uwe Stöhr wrote:
> I don't agree. The conversion of LyX 1.6 to 1.5 works correct, you can test
> it e.g. by using our doc umentation file.
>The opposite direction also
> works, as then nothing is done,
which is the culprit of the problem. normal user won't note that info
disapeared into
pream
> the conversion 1.5 -> 1.6 doesn't work wrt hyperref and it will be almost
> impossible to get it right, which was one of the three reasons i objected the
> whole idea of 1.6 -> 1.5 conversion. any user of 1.6 pdfsupport who will
exchange
> docs between 1.6 and 1.5 is bound to encounter strange
Christopher Reeve wrote:
Hi Richard,
Did you get a chance to look at the back-support of the sub-figure
option? Just tried rc3 and it still does not display my images correctly.
Sorry, I lost track of this. If you could send me a minimal example file
from 1.5, I'll get it working for 1.6.
Richard Heck wrote:
> Current trunk allows for this behavior, in fact. My question was whether it
> should be DISabled.
i fail to see advantage of that.
pavel
Pavel Sanda wrote:
Richard Heck wrote:
Layout files can, for example, set which font sizes are allowed in a
document, or set default class options, and these then should be displayed
in Document>Settings. (The bug was that this did not happen when a new
layout file was chosen, but only when
Abdelrazak Younes wrote:
On 13/10/2008 16:23, Dov Feldstern wrote:
Abdelrazak Younes wrote:
+if (row.end_margin_sel) {
if (text_->isRTL(buffer, beg.paragraph())) {
-int rm = bv_->rightMargin();
-pi.pain.fillRectangle(x + rm, y1, x2 - rm, y2 - y1,
Color_sel
Hi Richard,
Did you get a chance to look at the back-support of the sub-figure option?
Just tried rc3 and it still does not display my images correctly.
Cheers,
Chris.
2008/8/15 rgheck <[EMAIL PROTECTED]>
> Christopher Reeve wrote:
>
>> Hi Richard,
>> I'm just testing LyX 1.6rc1 and still hav
On 13/10/2008 16:23, Dov Feldstern wrote:
Abdelrazak Younes wrote:
+if (row.end_margin_sel) {
if (text_->isRTL(buffer, beg.paragraph())) {
-int rm = bv_->rightMargin();
-pi.pain.fillRectangle(x + rm, y1, x2 - rm, y2 - y1,
Color_selection);
+pi.
Abdelrazak Younes wrote:
On 12/10/2008 21:24, Vincent van Ravesteijn wrote:
Vincent van Ravesteijn wrote:
This patch solves some problems with painting selections in Insets.
These are:
- multiline selections paint in left margin of the main text
(bug 5270),
- the margins to the left and righ
On 13/10/2008 14:54, Jean-Marc Lasgouttes wrote:
Abdelrazak Younes<[EMAIL PROTECTED]> writes:
No, about both of you. Sorry, I meant German :-)
It was funnier with French.
Thanks, I was about to seriously question myself about my humor.
Abdel.
Jean-Marc Lasgouttes wrote:
> > Your diagnosis and suggested fix are right. IIRC we decided with JMarc
> > it was not worth going recursively into insets for toc purpose in
> > order to avoid potential visual problems (like big math insets or
> > branch, etc). So maybe we should add something betwe
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
> No, about both of you. Sorry, I meant German :-)
It was funnier with French.
JMarc
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
> Your diagnosis and suggested fix are right. IIRC we decided with JMarc
> it was not worth going recursively into insets for toc purpose in
> order to avoid potential visual problems (like big math insets or
> branch, etc). So maybe we should add somet
Joost Verburg wrote:
> current trunk this is very difficult. Does anyone know why it doesn't work
> like in 1.5?
http://bugzilla.lyx.org/show_bug.cgi?id=4464
pavel
Hi,
In LyX 1.5, it is possible to scroll while some paragraphs of texts are
selected by moving the cursor close to the top/bottom of the window. In
the current trunk this is very difficult. Does anyone know why it
doesn't work like in 1.5?
Regards,
Joost
On 13/10/2008 12:39, Uwe Stöhr wrote:
Abdelrazak Younes schrieb:
You rever to bug 3035, right? This is the showstopper, but you don't
fix it. Bug 4299 was marked as duplicate of this. I'm still confused
what you intention was.
You should probably switch to French...
Could you please be a b
Dear lyx crew,
There I have a ambivalent display of german characters in lyx - here a
description :
I use lyx in the german version with debian 4.0r4a 64 bit with a german
localisation and get a correct display of ä,ö,ü and ß in the german text
in the edit field, i. e. for "Einführung", say "i
Abdelrazak Younes schrieb:
You rever to bug 3035, right? This is the showstopper, but you don't
fix it. Bug 4299 was marked as duplicate of this. I'm still confused
what you intention was.
You should probably switch to French...
Could you please be a bit more specific or do you make jokes a
On 13/10/2008 12:14, Uwe Stöhr wrote:
Andre Poenitz schrieb:
You rever to bug 3035, right? This is the showstopper, but you don't
fix it. Bug 4299 was marked as duplicate of this. I'm still confused
what you intention was.
You should probably switch to French...
Abdel.
Andre Poenitz schrieb:
Maybe I am wrong, but you cannot assume an encoding from the length of a
comment.
There are a lot more serious assumptions in the tex2lyx code. Given any
data in an unknown encoding you will have to guess what it is.
But your guess is not correct. You assume an encodin
Uwe Stöhr <[EMAIL PROTECTED]> schrieb:
> > ctrl+" works here 1.6rc3 in the same way as in lyx 1.3.
> I found now the problem: The " is located on German keyboards on the
> "2" key, so to get Ctrl+" I would have to press Ctrl+Shift+2,
This is cared for by the ~S "operator":
./cua.bind:87:\bind
On 13/10/2008 10:02, Jürgen Spitzmüller wrote:
Abdelrazak Younes wrote:
Your diagnosis and suggested fix are right.
What would be the suggested fix?
asString(AS_STR_INSETS)
or
asString(AS_STR_LABEL | AS_STR_INSETS)
IOW does the TOC need AS_STR_LABEL?
Yes, that gives the numbe
Abdelrazak Younes wrote:
> Your diagnosis and suggested fix are right.
What would be the suggested fix?
asString(AS_STR_INSETS)
or
asString(AS_STR_LABEL | AS_STR_INSETS)
IOW does the TOC need AS_STR_LABEL?
I remember I have tried the latter and then the output was only correct in
some cases (
On 12/10/2008 21:24, Vincent van Ravesteijn wrote:
Vincent van Ravesteijn wrote:
This patch solves some problems with painting selections in Insets.
These are:
- multiline selections paint in left margin of the main text
(bug 5270),
- the margins to the left and right side of the inset are n
52 matches
Mail list logo
