On Wed, 2 May 2007, Herbert Voss wrote:
Bo Peng wrote:
It is not "treating as different paragraphs". They are different
paragraphs.
Yes, different paragraphs are always separated by a blank line.
Now I see why an inset is the only way to generate code with single
newlines. Herbert, what do y
Bo Peng wrote:
>> It is not "treating as different paragraphs". They are different
>> paragraphs.
>>
>> Yes, different paragraphs are always separated by a blank line.
>
> Now I see why an inset is the only way to generate code with single
> newlines. Herbert, what do you have right now?
sent it
It is not "treating as different paragraphs". They are different paragraphs.
Yes, different paragraphs are always separated by a blank line.
Now I see why an inset is the only way to generate code with single
newlines. Herbert, what do you have right now?
Bo
> Second we should weight the pros and cons of design decisions we take. That
> is why the discussion in the mailing list is important, the first and
> quickest solution generally is not the best, the process is iterative.
Of course but nobody replied to this topic and your first statement was: C
>I'm getting this error on a clean checkout of the latest svn from trunk:
>
>make[2]: *** No rule to make target `examples/armenian-article.lyx',
>needed by `all-am'. Stop.
Sorry my fault, should work now.
regards Uwe
I'm getting this error on a clean checkout of the latest svn from trunk:
make[2]: *** No rule to make target `examples/armenian-article.lyx',
needed by `all-am'. Stop.
This file is renamed to Armenian-article.lyx, and autotools are not
updated (yet). Scons is fine.
Cheers,
Bo
Hi!
I'm getting this error on a clean checkout of the latest svn from trunk:
make[2]: *** No rule to make target `examples/armenian-article.lyx',
needed by `all-am'. Stop.
Is this my problem or the repository's?
Thanks!
Dov
Could you make a python script that works sort of like what autotools
does and could be called by both scons and auto*? We do not want two
different code bases for that. And relying on file lists, while a good
idea in general, seems fragile in our case, unless scons and autotools
manage to share t
On Tuesday 01 May 2007 18:19:49 Uwe Stöhr wrote:
> > Georg had discussed this before, this is in the mailing list archives,
> > since I have a deadline today I have no time to search. The easier part
> > is probably to ask Georg if he is available. :-)
>
> I asked him, but he couldn't remember.
On Tuesday 01 May 2007 18:34:14 Uwe Stöhr wrote:
> >> Do you have an OK from Georg?
> >
> > Not fully yet. We discussed several things in private mail and I sent
> > him also my latest patch.
>
> Georg helped me to fix the remaining issus. But in general he don't want
> such language supports.
> "Bo" == Bo Peng <[EMAIL PROTECTED]> writes:
Bo> I guess I have to change scons to make autotools happy.
Could you make a python script that works sort of like what autotools
does and could be called by both scons and auto*? We do not want two
different code bases for that. And relying on fi
> "Richard" == Richard Heck <[EMAIL PROTECTED]> writes:
Richard> I'm not absolutely sure where this happens. But the source of
Richard> the problem, I am quite sure, is that LyX is treating the
Richard> newlines as separating paragraphs, and of course it outputs
Richard> \n\n between paragraph
> "Michael" == Michael Gerz <[EMAIL PROTECTED]> writes:
Michael> Uwe, did you change this message on purpose (Subsection =>
Michael> SubSection) ???
The new entry comes from the following:
# we used to have this version with wrong case
Style SubSection
ObsoletedBy Subsectio
However, if auto* creates
the po file differently, this will lead to a lot of confusion and
frustration (at least for those with a slow internet connection :-) )
For example, one of the problems is that
autotools:
layouts_l10n.pot: $(top_srcdir)/lib/layouts/*.layout
$(top_srcdir)/lib/layouts/*
Bo Peng schrieb:
The generated po files are different in many places like:
2924c2924
< #: lib/layouts/scrlttr2.layout:207 lib/layouts/amsdefs.inc:186
---
#: lib/layouts/amsdefs.inc:186 lib/layouts/scrlttr2.layout:207
which reflect the order in which inc and layout etc are processed, I
am look
A lot of po file noise was caused by changing the order in which the
messages are extracted from the source files (i.e. the order in which
the source files were processed).
I do hope that this order is the same for the scons and automake build
process. Otherwise, we will see a lot of other giant
On Tuesday 01 May 2007 20:47:27 Bo Peng wrote:
> > I did the same for qt ...
In the same bug report Georg refers that he has updated that version so that
would constitute a good starting point.
> Do you have it somewhere? We are no longer at feature freeze now. :-)
Yes we are, in this case
Bo Peng wrote:
> Regarding the simple layout approach, does anyone know where the extra
> newline is inserted? In the lyx file, each line is put into a separate
> layout so I guess a newline is inserted between these layouts?
I'm not absolutely sure where this happens. But the source of the
problem
Michael Gerz wrote:
Abdelrazak Younes schrieb:
Then keep the method in Buffer and put the logic in there. You don't
really need the method in BufferParams.
But we make exclusive use of BufferParams, no other Buffer member is
involved!
BufferParam is for Buffer _Parameters_ i.e. a structure wh
I did the same for qt ...
Do you have it somewhere? We are no longer at feature freeze now. :-)
Regarding the simple layout approach, does anyone know where the extra
newline is inserted? In the lyx file, each line is put into a separate
layout so I guess a newline is inserted between these lay
I'd like to discuss the different types of windows installers, their
definition/descriptions and more concretely, what the corresponding
compile time definitions should be called. Once we have agreed on
something here, I'd like all source code of the windows installers to
successively be made t
Michael Gerz wrote:
> Bo Peng schrieb:
>>> In that case was a new inset, like include/input inset, with
>>> support to
>>> configure the different options from listings, like the programming
>>> language, ...
>>
>> That will be good to have I googled for 2 minutes and could not
>> find that p
Bo Peng schrieb:
In that case was a new inset, like include/input inset, with
support to
configure the different options from listings, like the programming
language, ...
That will be good to have I googled for 2 minutes and could not
find that patch right now.
http://bugzilla.lyx.org/
In that case was a new inset, like include/input inset, with support to
configure the different options from listings, like the programming
language, ...
That will be good to have I googled for 2 minutes and could not
find that patch right now.
I found PassThru from src/layout.cpp. With a
On Tue, May 01, 2007 at 01:11:16PM -0500, Bo Peng wrote:
> >there was at a given point a patch from Herbert Voss to support
> >listings
> >directly in LyX. It was presented at a time when we were in feature freeze
> >and since it was reject due to the time of proposal Herbert lost
On Tuesday 01 May 2007 19:11:16 Bo Peng wrote:
> I am not sure what is 'direct' support since I am just one step away
> from what I want. Is there a layout instruction that outputs text
> unchanged? I see something like FreeSpacing, but this means somthing
> else.
In that case was a new inset, l
there was at a given point a patch from Herbert Voss to support listings
directly in LyX. It was presented at a time when we were in feature freeze
and since it was reject due to the time of proposal Herbert lost interest in
it.
I am not sure what is 'direct' support since I am just one
On Tuesday 01 May 2007 18:36:30 Uwe Stöhr wrote:
> > Uwe,
> >
> > did you change this message on purpose (Subsection => SubSection) ???
> >
> > #: lib/layouts/simplecv.layout:56
> > #, fuzzy
> > msgid "SubSection"
> > msgstr "Unterabschnitt"
>
> I changed nothing here; this is JMarc's baby.
On Tuesday 01 May 2007 17:53:13 Bo Peng wrote:
>
> There are other problems like _ is translated to \_ ...
>
> Bo
Bo,
there was at a given point a patch from Herbert Voss to support
listings
directly in LyX. It was presented at a time when we were in feature freeze
and since it was reje
On Mon, Apr 30, 2007 at 07:26:00PM +0200, Peter Kümmel wrote:
> Andre Poenitz wrote:
> > On Mon, Apr 30, 2007 at 02:25:42PM +0200, Peter Kümmel wrote:
> >> Just an idea for a long term goal:
> >>
> >> When not editing a formula it could
> >> be displayed as a real latex output,
> >
> > This is not
Peter Kümmel wrote:
Abdelrazak Younes wrote:
Peter Kümmel wrote:
Just an idea for a long term goal:
When not editing a formula it could
be displayed as a real latex output,
like here:
I guess you never tried instant preview... try to enable it in
Preference->Graphics.
You'll have a good surp
> Uwe,
>
> did you change this message on purpose (Subsection => SubSection) ???
>
> #: lib/layouts/simplecv.layout:56
> #, fuzzy
> msgid "SubSection"
> msgstr "Unterabschnitt"
I changed nothing here; this is JMarc's baby.
Or did I?
>> Do you have an OK from Georg?
>
> Not fully yet. We discussed several things in private mail and I sent him also
> my latest patch.
Georg helped me to fix the remaining issus. But in general he don't want such language supports. I
understand that he prefers a solution where the user can just
Abdelrazak Younes wrote:
Jürgen Spitzmüller wrote:
Maybe. FWIW, here's the solution where the map is put into the
controller (although I'm a bit reluctant at putting things in the
controller where there's obviously qt4 to blame).
Well, it's not as simple as that, you are asking the dialog to
>> I mean be "export" the export of a LyX-document from LyX 1.5svn to the
>> format LyX 1.4.x (menu File -> Export -> Lyx 1.4.4)
>
> The explanation is quite simple, you are lying to lyx2lyx. :-)
> You are telling lyx2lyx that you will save a latin-1 document and yet you
> are passing non-latin
Jürgen Spitzmüller wrote:
Maybe. FWIW, here's the solution where the map is put into the controller
(although I'm a bit reluctant at putting things in the controller where
there's obviously qt4 to blame).
Well, it's not as simple as that, you are asking the dialog to remember
the cursor posit
My problem is that
Line1
Line2
appears in latex as
\begin{lstlisting}
Line1
Line2
\end{lstlisting}
There are other problems like _ is translated to \_ ...
Bo
Dear list,
I am trying to add a lstlisting environment to my layout file (using
listings package) and arrive at the following:
Style Listings
Margin Static
LatexType Environment
LatexName lstlisting
NextNoIndent 1
LeftMargin MMM
Right
Abdelrazak Younes wrote:
> > Not if you do that _before_ showing the contents, will it?
Don't know. Couldn't figure that out.
> For that you need to catch the showEvent of the preamble module. Maybe
> using an even filter in QDocumentDialog... This eventFilter thing looks
> quite useful.
>
> Anyw
There's the gnome sollution which goes like that:
Capital letters are hebrew, small ones are English this | is the
cursor. We're in a LTR environment.
from the logical state abc |ABC which is displayed abc |CBA, when user
press RIGHT, we'll move to the following logical state "abc AB|C"
which will
Abdelrazak Younes wrote:
Jürgen Spitzmüller wrote:
Also I am puzzled that we need to memorize the scrollbar position. If we
move the internal cursor, won't the scrollbar automatically follow?
we can use ensureCursorVisible(), but then the window content will not
be at the same position. The i
Jürgen Spitzmüller wrote:
Abdelrazak Younes wrote:
One general comment: I know that the qt4 frontend is not as clean as it
should be but we should try to not add additional dependency to the core
(src/*.h). So, please move the map to ControlDocument instead and
fill-in the cursor position with a
Abdelrazak Younes wrote:
> One general comment: I know that the qt4 frontend is not as clean as it
> should be but we should try to not add additional dependency to the core
> (src/*.h). So, please move the map to ControlDocument instead and
> fill-in the cursor position with a helper function.
OK
Jürgen Spitzmüller wrote:
http://bugzilla.lyx.org/show_bug.cgi?id=3201
This turned to be out more complicated than I thought, because both the cursor
and the scrollbar position have to be saved for each buffer separately.
Attached is what I came up with.
Opinions?
One general comment: I kn
On May 1, 2007, at 2:59 AM, Jürgen Spitzmüller wrote:
Bennett Helm wrote:
Toggling the drawer works fine, both with the menu and a custom
keybinding. One issue here, though, is focus. When the TOC drawer
opens, the "Type" drop-down list has focus; on Mac, it's not possible
to use the keyboard t
Abdelrazak Younes wrote:
> If you agree with that, I'll commit his patch which I have locally
> applied for some days already.
I agree, but please check whether it interferes with some of my recent changes
(I remember the patch also did something about the menu toogle thing).
Jürgen
Michael Gerz wrote:
Jürgen Spitzmüller schrieb:
Michael Gerz wrote:
Any comments on this issues are welcome. I would like to get some
opinions before I change the po file.
remove the shortcuts from the dialog and introduce general shortcuts
for the outliner actions.
Abdel, shouldn'
http://bugzilla.lyx.org/show_bug.cgi?id=3201
This turned to be out more complicated than I thought, because both the cursor
and the scrollbar position have to be saved for each buffer separately.
Attached is what I came up with.
Opinions?
Jürgen
Index: src/frontends/qt4/QDocument.cpp
=
Michael Gerz wrote:
> Abdel, shouldn't we remove the shortcuts in the UI files, too (i.e. in
> the English messages).
That's what I meant.
> This may also open the door for buttons with icons.
Probably yes.
Jürgen
Jürgen Spitzmüller schrieb:
Michael Gerz wrote:
Any comments on this issues are welcome. I would like to get some
opinions before I change the po file.
remove the shortcuts from the dialog and introduce general shortcuts for the
outliner actions.
Abdel, shouldn't we remove the shor
Michael Gerz wrote:
> Any comments on this issues are welcome. I would like to get some
> opinions before I change the po file.
remove the shortcuts from the dialog and introduce general shortcuts for the
outliner actions.
Jürgen
Jürgen Spitzmüller schrieb:
I know now what's happening. I just discovered that it's locale-dependend.
Michael, in the German localization, you cannot use the accelerator "A" for
the TOC dialog (which is in fact used twice), for this breaks the fundamental
keyboard shortcuts M-a {1,2,...} in t
Uwe,
did you change this message on purpose (Subsection => SubSection) ???
#: lib/layouts/simplecv.layout:56
#, fuzzy
msgid "SubSection"
msgstr "Unterabschnitt"
Michael
[EMAIL PROTECTED] schrieb:
Author: schmitt
Date: Tue May 1 11:28:19 2007
New Revision: 18145
URL: http://www.lyx.org/trac/changeset/18145
Log:
* po/*.po:
* po/POTFILES.in: another giant po files update;
hopefully, the messages, the source files, and the order, in which
On Tue, May 01, 2007 at 10:03:49AM +0200, Hartmut Haase wrote:
> Hi there, since 7 days or more I can't compile anymore because someone
> checked things in without testing them. I don't know how you guys are
> are working but you violate at least one main rule of good s/w
> develepmont. This was a
On Tue, May 01, 2007 at 10:50:14AM +0200, Abdelrazak Younes wrote:
> Andre Poenitz wrote:
> >On Tue, May 01, 2007 at 10:38:14AM +0200, Abdelrazak Younes wrote:
> >>Jürgen Spitzmüller wrote:
> >>>Edwin Leuven wrote:
> only one (and a half) small thing:
>
> i've added a toolbar button, a
Hartmut Haase schrieb:
Hi there,
since 7 days or more I can't compile anymore because someone checked things in
without testing them. I don't know how you guys are are working but you
violate at least one main rule of good s/w develepmont.
This was already the case when you switched to utf-8.
Abdelrazak Younes schrieb:
Then keep the method in Buffer and put the logic in there. You don't
really need the method in BufferParams.
But we make exclusive use of BufferParams, no other Buffer member is
involved!
I think the situation is similar (but not identical) to Paragraph vs
Paragraph
Hi there,
since 7 days or more I can't compile anymore because someone checked things in
without testing them. I don't know how you guys are are working but you
violate at least one main rule of good s/w develepmont.
This was already the case when you switched to utf-8.
A little more discipline w
Michael Gerz wrote:
Abdelrazak Younes schrieb:
Modified: lyx-devel/trunk/src/Buffer.cpp
URL:
http://www.lyx.org/trac/file/lyx-devel/trunk/src/Buffer.cpp?rev=18143
==
--- lyx-devel/trunk/src/Buffer.cpp (original)
+++
Andre Poenitz wrote:
On Tue, May 01, 2007 at 10:38:14AM +0200, Abdelrazak Younes wrote:
Jürgen Spitzmüller wrote:
Edwin Leuven wrote:
only one (and a half) small thing:
i've added a toolbar button, and when i close the toc widget with the X
the toolbutton is not untoggled; this happens only w
Abdelrazak Younes schrieb:
Modified: lyx-devel/trunk/src/Buffer.cpp
URL:
http://www.lyx.org/trac/file/lyx-devel/trunk/src/Buffer.cpp?rev=18143
==
--- lyx-devel/trunk/src/Buffer.cpp (original)
+++ lyx-devel/trunk/src/B
On Tue, May 01, 2007 at 10:38:14AM +0200, Abdelrazak Younes wrote:
> Jürgen Spitzmüller wrote:
> >Edwin Leuven wrote:
> >>only one (and a half) small thing:
> >>
> >>i've added a toolbar button, and when i close the toc widget with the X
> >>the toolbutton is not untoggled; this happens only when i
Abdelrazak Younes wrote:
> We need a closed() or hidden() signal in DockView (emitted in the
> DockView::closeEvent()) that will be connected to
> LyXView::updateToolbars().
Could you do this, please?
Jürgen
Georg Baum wrote:
Am Montag, 30. April 2007 23:52 schrieb Abdelrazak Younes:
Michael Gerz wrote:
Georg, all,
as an attempt to please you and to fix bug #3332, I produced the
attached patch :-)
The bad news: The translations to the buffer language do not work on my
machine (Win XP) - all tr
Jürgen Spitzmüller wrote:
Edwin Leuven wrote:
only one (and a half) small thing:
i've added a toolbar button, and when i close the toc widget with the X
the toolbutton is not untoggled; this happens only when i click on the
workarea...
is there a missing update call somewhere?
Probably. The
[EMAIL PROTECTED] wrote:
Author: schmitt
Date: Tue May 1 10:26:40 2007
New Revision: 18143
URL: http://www.lyx.org/trac/changeset/18143
Log:
"fix" bug #3332 (plain text export depends on the menu language)
Please note that method B_ (translate text to buffer language) is presently
broken (at
Michael Gerz wrote:
> If you use "svn move toc-view.xpm dialog-toggle_toc.xpm", subversion
> keeps track of the file's history.
Thank you. I didn't know this.
Jürgen
Abdelrazak Younes schrieb:
Michael Gerz wrote:
Georg, all,
as an attempt to please you and to fix bug #3332, I produced the
attached patch :-)
The bad news: The translations to the buffer language do not work on
my machine (Win XP) - all translations are made to the menu language,
instead
[EMAIL PROTECTED] schrieb:
Author: spitz
Date: Tue May 1 09:05:12 2007
New Revision: 18141
URL: http://www.lyx.org/trac/changeset/18141
Log:
* lib/images:
- rename toc-view.xpm to dialog-toggle_toc.xpm
Added:
lyx-devel/trunk/lib/images/dialog-toggle_toc.xpm
Removed:
lyx-devel/t
Am Montag, 30. April 2007 23:52 schrieb Abdelrazak Younes:
> Michael Gerz wrote:
> > Georg, all,
> >
> > as an attempt to please you and to fix bug #3332, I produced the
> > attached patch :-)
> >
> > The bad news: The translations to the buffer language do not work on my
> > machine (Win XP) -
Edwin Leuven wrote:
> only one (and a half) small thing:
>
> i've added a toolbar button, and when i close the toc widget with the X
> the toolbutton is not untoggled; this happens only when i click on the
> workarea...
>
> is there a missing update call somewhere?
Probably. The toolbars need to b
Bennett Helm wrote:
> Toggling the drawer works fine, both with the menu and a custom
> keybinding. One issue here, though, is focus. When the TOC drawer
> opens, the "Type" drop-down list has focus; on Mac, it's not possible
> to use the keyboard to navigate to the TOC contents or back to th
73 matches
Mail list logo
