[Fwd: Re: wp2latex feature request]
---BeginMessage--- wp2latex feature request Garst R. Reese Sat, 24 Jun 2006 06:42:28 -0700 http://www.penguin.cz/~fojtik/wp2latex/wp2latex.htm Converts wordperfect.wpd files to .tex It would be nice to have this in converters if installed. Anyway, wp2latex could parse even other documents like RTF, Accent, HTML, T602, Word (little bit) etc. So the filter could call wp2latex even for these formats. I welcome such support from other programs. If you need some help feel free to ask. Jara Thanks, Garst ---End Message---
[Fwd: Re: wp2latex feature request]
--- Begin Message --- > wp2latex feature request > > Garst R. Reese > Sat, 24 Jun 2006 06:42:28 -0700 > > http://www.penguin.cz/~fojtik/wp2latex/wp2latex.htm > Converts wordperfect.wpd files to .tex > It would be nice to have this in converters if installed. Anyway, wp2latex could parse even other documents like RTF, Accent, HTML, T602, Word (little bit) etc. So the filter could call wp2latex even for these formats. I welcome such support from other programs. If you need some help feel free to ask. Jara > > Thanks, > Garst > --- End Message ---
wp2latex feature request
http://www.penguin.cz/~fojtik/wp2latex/wp2latex.htm Converts wordperfect.wpd files to .tex It would be nice to have this in converters if installed. Thanks, Garst
wp2latex feature request
http://www.penguin.cz/~fojtik/wp2latex/wp2latex.htm Converts wordperfect.wpd files to .tex It would be nice to have this in converters if installed. Thanks, Garst
lyx-1.3.7 Fedora core 5
It compiles with xforms, but it cannot find colors, so lots of stuff is just black on black. The FC5 release notes say they have moved to X11R7 so a lot of stuff is not where it used to be and applications will have to adjust. How? I have a different problem with qt-3.3. How do I tell Lyx where it is? What should QTDIR say? I got libraries and includes right, but that is not enough. Thanks, Garst (not subscribed)
lyx-1.3.7 & Fedora core 5
It compiles with xforms, but it cannot find colors, so lots of stuff is just black on black. The FC5 release notes say they have moved to X11R7 so a lot of stuff is not where it used to be and applications will have to adjust. How? I have a different problem with qt-3.3. How do I tell Lyx where it is? What should QTDIR say? I got libraries and includes right, but that is not enough. Thanks, Garst (not subscribed)
Re: [Patch] Re: book that prints with 1.3.7 is screwed up with 1.4.1
Martin Vermeer wrote:
On Thu, Apr 20, 2006 at 10:28:51PM -0500, Garst R. Reese wrote:
Martin Vermeer wrote:
I don't agree. You're right in that the only place where a
_correspondence_ is defined between the old numerical parameters and the
new character ones is, precisely, lyx2lyx. And this correspondence
should be _semantically correct_, i.e. 0123 - ctbs. (Right? You have
1.3.7 installed, so you can verify that truly 0 = center, 1 = top.)
Yes, but why does src/insets/insetminipage.h have
33 enum InnerPosition {
34 inner_center,
35 inner_top,
36 inner_bottom,
37 inner_stretch
instead of
33 enum InnerPosition {
34 inner_top,
35 inner_center,
36 inner_bottom,
37 inner_stretch
?
If this order is changed and lyx_1_4.py is changed to match than 1.3.7
still works.
The only bug I see is the inconsistent default conventions: the old
one height = 0, inner_position = 0, and the new one height = 1pt
(meaning, 1\totalheight) and inner_pos = 't'. The error (the ONLY error
IMHO) is translating the old default to 1pt, 'c', rather than 1pt,
't'. Which my patch corrects in a minimal way. Think what your proposed
remedy would do to a minipage with a manually set height, if the
inner_pos semantics is wrong.
- Martin
Thanks for the pointers. After looking at the relevant files in 1.4.1,
and the insetminipage
files in 1.3.7, I think that both patches to 1.4.1 should be applied. I
tried this and did not have a problem with it. You, of course, know
much better than I and I thank you for sharing.
Garst
Re: [Patch] Re: book that prints with 1.3.7 is screwed up with 1.4.1
Martin Vermeer wrote:
On Thu, Apr 20, 2006 at 10:28:51PM -0500, Garst R. Reese wrote:
Martin Vermeer wrote:
I don't agree. You're right in that the only place where a
_correspondence_ is defined between the old numerical parameters and the
new character ones is, precisely, lyx2lyx. And this correspondence
should be _semantically correct_, i.e. 0123 -> ctbs. (Right? You have
1.3.7 installed, so you can verify that truly 0 = center, 1 = top.)
Yes, but why does src/insets/insetminipage.h have
33 enum InnerPosition {
34 inner_center,
35 inner_top,
36 inner_bottom,
37 inner_stretch
instead of
33 enum InnerPosition {
34 inner_top,
35 inner_center,
36 inner_bottom,
37 inner_stretch
?
If this order is changed and lyx_1_4.py is changed to match than 1.3.7
still works.
The only "bug" I see is the inconsistent default conventions: the old
one height = 0, inner_position = 0, and the new one height = "1pt"
(meaning, 1\totalheight) and inner_pos = 't'. The error (the ONLY error
IMHO) is translating the old default to "1pt", 'c', rather than "1pt",
't'. Which my patch corrects in a minimal way. Think what your proposed
remedy would do to a minipage with a manually set height, if the
inner_pos semantics is wrong.
- Martin
Thanks for the pointers. After looking at the relevant files in 1.4.1,
and the insetminipage
files in 1.3.7, I think that both patches to 1.4.1 should be applied. I
tried this and did not have a problem with it. You, of course, know
much better than I and I thank you for sharing.
Garst
Re: [Patch] Re: book that prints with 1.3.7 is screwed up with 1.4.1
Martin Vermeer wrote: On Wed, Apr 19, 2006 at 06:02:33PM -0500, Garst R. Reese wrote: Martin Vermeer wrote: On Wed, Apr 19, 2006 at 08:57:53PM +0300, Martin Vermeer wrote: On Wed, Apr 19, 2006 at 10:20:36AM -0500, Garst R. Reese wrote: ... Try the attached. - Martin Oops, hit reply instead of reply all for the last two msgs. This is to fix things. I played with the Box Settings in 1.4.1 by right clicking on the minipages. It shows Vertical Alignment and Inner Alignment(vert). Horizontal Alignment is greyed out. The working combination is Top Top for the critters and Middle Middle for the title. Lyx2lyx sets them to Top Middle and Middle Middle. For this file, it works to change inner_pos = [c,t,b,s] to inner_pos = [t,c,b,s]. This changes the title settins to Middle Top, but still gives a correct ps output. So I reverted this change and used the dialog boxes to set Top Top and Middle Top and again got correct output. So what dictates the ordering in inner_pos? Yes it happens to work, but the logic is wrong. The original order of inner_pos is correct and shouldn't be changed: it is the order of the older numerical argument inner_position. I think the old order was a bug and this is a good time to squelch it. in development/FORMAT lines 260-284 you have an Ovalbox and on line 269 you use tcbs for it's inner_pos. But on line 289 you use c/t/b/s for the Frameless box. The only place in the 1.4.1 code that I can find actually using inner_pos is in lyx_1_2.py (line172) and lyx_1_4.py. I think my example doc just exposed this inconsistency as a true bug. Were it not for the strange c/t/b/s mapping all would have been well. Thanks, Garst
Re: [Patch] Re: book that prints with 1.3.7 is screwed up with 1.4.1
Martin Vermeer wrote: On Wed, Apr 19, 2006 at 06:02:33PM -0500, Garst R. Reese wrote: Martin Vermeer wrote: On Wed, Apr 19, 2006 at 08:57:53PM +0300, Martin Vermeer wrote: On Wed, Apr 19, 2006 at 10:20:36AM -0500, Garst R. Reese wrote: ... Try the attached. - Martin Oops, hit reply instead of reply all for the last two msgs. This is to fix things. I played with the Box Settings in 1.4.1 by right clicking on the minipages. It shows Vertical Alignment and Inner Alignment(vert). Horizontal Alignment is greyed out. The working combination is Top Top for the critters and Middle Middle for the title. Lyx2lyx sets them to Top Middle and Middle Middle. For this file, it works to change inner_pos = ["c","t","b","s"] to inner_pos = ["t","c","b","s"]. This changes the title settins to Middle Top, but still gives a correct ps output. So I reverted this change and used the dialog boxes to set Top Top and Middle Top and again got correct output. So what dictates the ordering in inner_pos? Yes it happens to work, but the logic is wrong. The original order of inner_pos is correct and shouldn't be changed: it is the order of the older numerical argument inner_position. I think the old order was a bug and this is a good time to squelch it. in development/FORMAT lines 260-284 you have an Ovalbox and on line 269 you use tcbs for it's inner_pos. But on line 289 you use c/t/b/s for the Frameless box. The only place in the 1.4.1 code that I can find actually using inner_pos is in lyx_1_2.py (line172) and lyx_1_4.py. I think my example doc just exposed this inconsistency as a true bug. Were it not for the strange c/t/b/s mapping all would have been well. Thanks, Garst
Re: book that prints with 1.3.7 is screwed up with 1.4.1
Martin Vermeer wrote: On Wed, 2006-04-19 at 10:57 +0100, Jose' Matos wrote: On Wednesday 19 April 2006 07:52, Martin Vermeer wrote: Sorry for the long analysis. Jose, do you agree? I guess so, after such throughout explanation it is difficult not to agree. :-) Since you understand both codes, I would vote for this code inclusion in both trunk and 1.4. Could you do it, please? But first of all, Garst, does it do the job? No. The patch made no change to the exported .tex file. The c is still a c, not a t. Garst - Martin
Re: book that prints with 1.3.7 is screwed up with 1.4.1
I have done some experimenting changing the .lyx file. To reproduce the 1.3.7 results, the Box Framless insets for the critters have position t and inner_pos t but for the title it needs position c and inner_pos t. The corresponding Minipage settings in 1.3.7 are position 0, inner_position 0 and position 1, inner_position 0. So, in my case, inner_position is the same for all of the Minipage insets, but position changes. I tried all combinations of 0's and 1's around position and inner_pos in lyx_1_4.py to no avail. Garst Martin Vermeer wrote: On Wed, 2006-04-19 at 07:29 -0500, Garst R. Reese wrote: Martin Vermeer wrote: On Wed, 2006-04-19 at 10:57 +0100, Jose' Matos wrote: On Wednesday 19 April 2006 07:52, Martin Vermeer wrote: Sorry for the long analysis. Jose, do you agree? I guess so, after such throughout explanation it is difficult not to agree. :-) Since you understand both codes, I would vote for this code inclusion in both trunk and 1.4. Could you do it, please? But first of all, Garst, does it do the job? No. The patch made no change to the exported .tex file. The c is still a c, not a t. Garst Jose? Where is the right place? - Martin
Re: [Patch] Re: book that prints with 1.3.7 is screwed up with 1.4.1
Martin Vermeer wrote:
On Wed, Apr 19, 2006 at 08:57:53PM +0300, Martin Vermeer wrote:
On Wed, Apr 19, 2006 at 10:20:36AM -0500, Garst R. Reese wrote:
I have done some experimenting changing the .lyx file. To reproduce the
1.3.7 results, the Box Framless insets for the critters have position
t and inner_pos t but for the title it needs position c and
inner_pos t. The corresponding Minipage settings in 1.3.7 are position
0, inner_position 0 and position 1, inner_position 0. So, in my case,
inner_position is the same for all of the Minipage insets, but position
changes. I tried all combinations of 0's and 1's
around position and inner_pos in lyx_1_4.py to no avail.
Garst
I think I know what the problem is.
1.3.7 uses the combination of height = 1pt and inner_position = 0 to
indicate the defaults. These should be translated to 1\totalheight and
t to function correctly. Unfortunately lyx2lyx translates it to
1\totalheight and c, because 0 - c and it doesn't recognize the
special case.
Have to sleep on this one, if Jose doesn't beat me to a fix :-)
Try the attached.
- Martin
Oops, hit reply instead of reply all for the last two msgs. This is to
fix things.
I played with the Box Settings in 1.4.1 by right clicking on the
minipages. It shows Vertical Alignment and Inner Alignment(vert).
Horizontal Alignment is greyed out. The working combination is Top Top
for the critters and Middle Middle for the title. Lyx2lyx sets them to
Top Middle and Middle Middle. For this file, it works to change
inner_pos = [c,t,b,s]
to inner_pos = [t,c,b,s]. This changes the title settins to
Middle Top, but still gives a correct ps output. So I reverted this
change and used the dialog boxes to set Top Top and Middle Top and again
got correct output. So what dictates the ordering in inner_pos?
Your new patch also works and sets the Box Settings the same way -- Top
Top and Middle Top.
Garst
Index: lyx_1_4.py
===
--- lyx_1_4.py (revision 13657)
+++ lyx_1_4.py (working copy)
@@ -987,10 +987,10 @@ def convert_minipage(file):
# convert the inner_position
if file.body[i][:14] == inner_position:
-file.body[i] = 'inner_pos %s' % inner_pos[int(file.body[i][15])]
+ innerpos = inner_pos[int(file.body[i][15])]
+ del file.body[i]
else:
-file.body.insert('inner_pos %s' % inner_pos[0])
-i = i + 1
+ innerpos = inner_pos[1]
# We need this since the new file format has a height and width
# in a different order.
@@ -1018,6 +1018,12 @@ def convert_minipage(file):
else:
status = collapsed
+ # Handle special default case:
+ if height == ' 1pt' and innerpos == 'c':
+ innerpos = 't'
+
+file.body.insert(i, 'inner_pos ' + innerpos + '')
+i = i + 1
file.body.insert(i, 'use_parbox 0')
i = i + 1
file.body.insert(i, 'width' + width)
Re: book that prints with 1.3.7 is screwed up with 1.4.1
Martin Vermeer wrote: On Wed, 2006-04-19 at 10:57 +0100, Jose' Matos wrote: On Wednesday 19 April 2006 07:52, Martin Vermeer wrote: Sorry for the long analysis. Jose, do you agree? I guess so, after such throughout explanation it is difficult not to agree. :-) Since you understand both codes, I would vote for this code inclusion in both trunk and 1.4. Could you do it, please? But first of all, Garst, does it do the job? No. The patch made no change to the exported .tex file. The c is still a c, not a t. Garst - Martin
Re: book that prints with 1.3.7 is screwed up with 1.4.1
I have done some experimenting changing the .lyx file. To reproduce the 1.3.7 results, the Box Framless insets for the critters have position "t" and inner_pos "t" but for the title it needs position "c" and inner_pos "t". The corresponding Minipage settings in 1.3.7 are position 0, inner_position 0 and position 1, inner_position 0. So, in my case, inner_position is the same for all of the Minipage insets, but position changes. I tried all combinations of 0's and 1's around position and inner_pos in lyx_1_4.py to no avail. Garst Martin Vermeer wrote: On Wed, 2006-04-19 at 07:29 -0500, Garst R. Reese wrote: Martin Vermeer wrote: On Wed, 2006-04-19 at 10:57 +0100, Jose' Matos wrote: On Wednesday 19 April 2006 07:52, Martin Vermeer wrote: Sorry for the long analysis. Jose, do you agree? I guess so, after such throughout explanation it is difficult not to agree. :-) Since you understand both codes, I would vote for this code inclusion in both trunk and 1.4. Could you do it, please? But first of all, Garst, does it do the job? No. The patch made no change to the exported .tex file. The c is still a c, not a t. Garst Jose? Where is the right place? - Martin
Re: [Patch] Re: book that prints with 1.3.7 is screwed up with 1.4.1
Martin Vermeer wrote:
On Wed, Apr 19, 2006 at 08:57:53PM +0300, Martin Vermeer wrote:
On Wed, Apr 19, 2006 at 10:20:36AM -0500, Garst R. Reese wrote:
I have done some experimenting changing the .lyx file. To reproduce the
1.3.7 results, the Box Framless insets for the critters have position
"t" and inner_pos "t" but for the title it needs position "c" and
inner_pos "t". The corresponding Minipage settings in 1.3.7 are position
0, inner_position 0 and position 1, inner_position 0. So, in my case,
inner_position is the same for all of the Minipage insets, but position
changes. I tried all combinations of 0's and 1's
around position and inner_pos in lyx_1_4.py to no avail.
Garst
I think I know what the problem is.
1.3.7 uses the combination of height = 1pt and inner_position = 0 to
indicate the defaults. These should be translated to "1\totalheight" and
"t" to function correctly. Unfortunately lyx2lyx translates it to
"1\totalheight" and "c", because 0 -> "c" and it doesn't recognize the
special case.
Have to sleep on this one, if Jose doesn't beat me to a fix :-)
Try the attached.
- Martin
Oops, hit reply instead of reply all for the last two msgs. This is to
fix things.
I played with the Box Settings in 1.4.1 by right clicking on the
minipages. It shows Vertical Alignment and Inner Alignment(vert).
Horizontal Alignment is greyed out. The working combination is Top Top
for the critters and Middle Middle for the title. Lyx2lyx sets them to
Top Middle and Middle Middle. For this file, it works to change
inner_pos = ["c","t","b","s"]
to inner_pos = ["t","c","b","s"]. This changes the title settins to
Middle Top, but still gives a correct ps output. So I reverted this
change and used the dialog boxes to set Top Top and Middle Top and again
got correct output. So what dictates the ordering in inner_pos?
Your new patch also works and sets the Box Settings the same way -- Top
Top and Middle Top.
Garst
Index: lyx_1_4.py
===
--- lyx_1_4.py (revision 13657)
+++ lyx_1_4.py (working copy)
@@ -987,10 +987,10 @@ def convert_minipage(file):
# convert the inner_position
if file.body[i][:14] == "inner_position":
-file.body[i] = 'inner_pos "%s"' % inner_pos[int(file.body[i][15])]
+ innerpos = inner_pos[int(file.body[i][15])]
+ del file.body[i]
else:
-file.body.insert('inner_pos "%s"' % inner_pos[0])
-i = i + 1
+ innerpos = inner_pos[1]
# We need this since the new file format has a height and width
# in a different order.
@@ -1018,6 +1018,12 @@ def convert_minipage(file):
else:
status = "collapsed"
+ # Handle special default case:
+ if height == ' "1pt"' and innerpos == 'c':
+ innerpos = 't'
+
+file.body.insert(i, 'inner_pos "' + innerpos + '"')
+i = i + 1
file.body.insert(i, 'use_parbox 0')
i = i + 1
file.body.insert(i, 'width' + width)
Re: book that prints with 1.3.7 is screwed up with 1.4.1
The only difference between the attached files known to the user is the
version of lyx that saved them.
Michael echoes my objections to the new memubar. I spent two weeks
trying to get used to it, but just got increasingly irritated.
Regards,
Garst
Michael Gerz wrote:
Garst R. Reese wrote:
In anycase, I dislike the 1.4.1 menubar so much that I will stay with
1.3.7
Garst, I am afraid agree with you.
IMHO the biggest mistake was to drop the Format menu. EVERY text
editing tool but LyX has such a menu and the average user expects it
to contain Character..., Paragraph..., and Document... entries.
In LyX, you find formatting options in both Edit and Document
(EditText Style, EditParagraph Settings, DocumentSettings
etc.). IMHO this is counter-intuitive and also 'pollutes' the Edit
menu. Also: Why is LaTeX Log in Document? It only makes sense in
the context of View.
I know that we discussed the menu structure a long time ago.
Nevertheless, I think we should again ask the LyX users what they
think about the new structure and revert some of the changes if they
lead to confusion. It is not a shame to confess that some changes went
into the wrong direction.
Michael
PS: The citation dialog has become very inconvenient. Are there any
plans to revive the good old 1.3.X dialog in 1.4.X?
#LyX 1.3 created this file. For more info see http://www.lyx.org/
\lyxformat 221
\textclass book
\begin_preamble
\usepackage{oldgerm} % so that the math font matches the textfont
\newcommand{\YIN}{\usefont{U}{yinit}{m}{n}}
\newcommand{\YINA}{\usefont{U}{yinitA}{m}{n}}
\usepackage{euler} % so that the math font matches the textfont
\newcommand{\EUS}{\usefont{U}{eus}{m}{n}}
\end_preamble
\language canadian
\inputencoding latin1
\fontscheme bookman
\graphics default
\paperfontsize default
\spacing single
\papersize Custom
\paperpackage a4
\use_geometry 1
\use_amsmath 1
\use_natbib 0
\use_numerical_citations 0
\paperorientation portrait
\paperwidth 5.5in
\paperheight 4.25in
\leftmargin 7mm
\topmargin 2mm
\rightmargin 8mm
\bottommargin 2mm
\headheight 0in
\headsep 0in
\footskip 0in
\secnumdepth 2
\tocdepth 2
\paragraph_separation skip
\defskip medskip
\quotes_language english
\quotes_times 2
\papercolumns 1
\papersides 2
\paperpagestyle empty
\layout Standard
\begin_inset Minipage
position 0
inner_position 0
height 1pt
width 67col%
collapsed false
\layout Standard
\begin_inset Graphics
filename eps/crittera.eps.gz
lyxscale 10
display color
width 1.6cm
height 1.6cm
\end_inset
\SpecialChar ~
\SpecialChar ~
\begin_inset Graphics
filename eps/critterb.eps.gz
lyxscale 10
display color
width 1.6cm
height 1.6cm
\end_inset
\SpecialChar ~
\SpecialChar ~
\begin_inset Graphics
filename eps/critterc.eps.gz
lyxscale 10
display color
width 1.6cm
height 1.6cm
\end_inset
\SpecialChar ~
\SpecialChar ~
\begin_inset Graphics
filename eps/critterd.eps.gz
lyxscale 10
display color
width 1.6cm
height 1.6cm
\end_inset
\newline
\SpecialChar ~
\newline
\begin_inset Graphics
filename eps/crittere.eps.gz
lyxscale 10
display color
width 1.6cm
height 1.6cm
\end_inset
\SpecialChar ~
\SpecialChar ~
\begin_inset Graphics
filename eps/critterf.eps.gz
lyxscale 10
display color
width 1.6cm
height 1.6cm
\end_inset
\SpecialChar ~
\SpecialChar ~
\begin_inset Graphics
filename eps/critterg.eps.gz
lyxscale 10
display color
width 1.6cm
height 1.6cm
\end_inset
\SpecialChar ~
\SpecialChar ~
\begin_inset Graphics
filename eps/critterh.eps.gz
lyxscale 10
display color
width 1.6cm
height 1.6cm
\end_inset
\end_inset
\begin_inset Minipage
position 1
inner_position 0
height 1pt
width 33col%
collapsed false
\layout Standard
\series bold
\size large
The
\newline
AlphaBeast
\newline
Book
\newline
\SpecialChar ~
\newline
by
\newline
Garst R.
Reese
\end_inset
\layout Standard
\pagebreak_bottom \noindent
\begin_inset Graphics
filename eps/critteri.eps.gz
lyxscale 10
display color
width 1.6cm
height 1.6cm
\end_inset
\SpecialChar ~
\SpecialChar ~
\begin_inset Graphics
filename eps/critterj.eps.gz
lyxscale 10
display color
width 1.6cm
height 1.6cm
\end_inset
\SpecialChar ~
\SpecialChar ~
\begin_inset Graphics
filename eps/critterk.eps.gz
lyxscale 10
display color
width 1.6cm
height 1.6cm
\end_inset
\SpecialChar ~
\SpecialChar ~
\begin_inset Graphics
filename eps/critterl.eps.gz
lyxscale 10
display color
width 1.6cm
height 1.6cm
\end_inset
\SpecialChar ~
\SpecialChar ~
\begin_inset Graphics
filename eps
Re: book that prints with 1.3.7 is screwed up with 1.4.1
Attached .tex files simplified by changing all graphic letters to o found in crittero... Hope this helps. Garst Martin Vermeer wrote: On Tue, Apr 18, 2006 at 10:18:02PM +0200, Michael Gerz wrote: Garst R. Reese wrote: Attached you will find the cover pdf generated with ps2pdf from the print to file output from 1.3.7. I cannot provide the equivalent pdf from 1.4.1 because ps2pdf aborts with errors. View pdf works but instead of 5 lines of letters, there are only 4 and the title is raised a few cm. The difference in the .lyx files is that 1.3.7 says begin_inset Minipage and 1.4.1 begin inset Box Frameless Garst, could you please provide us with a simple test case (minimized LyX file) and add a report to bugzilla? And what is the LaTeX code produced by both? If 1.4.1 and 1.3.7 do not produce the same output, there is a serious regression. The problem could be in lyx2lyx (Minipage - Box). - Martin Abookcover1.3.7.tex Description: TeX document Abookcover1.4.1.tex Description: TeX document crittero.eps.gz Description: GNU Zip compressed data
Re: book that prints with 1.3.7 is screwed up with 1.4.1
The only difference between the attached files known to the user is the
version of lyx that saved them.
Michael echoes my objections to the new memubar. I spent two weeks
trying to get used to it, but just got increasingly irritated.
Regards,
Garst
Michael Gerz wrote:
Garst R. Reese wrote:
In anycase, I dislike the 1.4.1 menubar so much that I will stay with
1.3.7
Garst, I am afraid agree with you.
IMHO the biggest mistake was to drop the "Format" menu. EVERY text
editing tool but LyX has such a menu and the average user expects it
to contain "Character...", "Paragraph...", and "Document..." entries.
In LyX, you find formatting options in both "Edit" and "Document"
("Edit>Text Style", "Edit>Paragraph Settings", "Document>Settings"
etc.). IMHO this is counter-intuitive and also 'pollutes' the "Edit"
menu. Also: Why is "LaTeX Log" in "Document"? It only makes sense in
the context of "View".
I know that we discussed the menu structure a long time ago.
Nevertheless, I think we should again ask the LyX users what they
think about the new structure and revert some of the changes if they
lead to confusion. It is not a shame to confess that some changes went
into the wrong direction.
Michael
PS: The citation dialog has become very inconvenient. Are there any
plans to revive the good old 1.3.X dialog in 1.4.X?
#LyX 1.3 created this file. For more info see http://www.lyx.org/
\lyxformat 221
\textclass book
\begin_preamble
\usepackage{oldgerm} % so that the math font matches the textfont
\newcommand{\YIN}{\usefont{U}{yinit}{m}{n}}
\newcommand{\YINA}{\usefont{U}{yinitA}{m}{n}}
\usepackage{euler} % so that the math font matches the textfont
\newcommand{\EUS}{\usefont{U}{eus}{m}{n}}
\end_preamble
\language canadian
\inputencoding latin1
\fontscheme bookman
\graphics default
\paperfontsize default
\spacing single
\papersize Custom
\paperpackage a4
\use_geometry 1
\use_amsmath 1
\use_natbib 0
\use_numerical_citations 0
\paperorientation portrait
\paperwidth 5.5in
\paperheight 4.25in
\leftmargin 7mm
\topmargin 2mm
\rightmargin 8mm
\bottommargin 2mm
\headheight 0in
\headsep 0in
\footskip 0in
\secnumdepth 2
\tocdepth 2
\paragraph_separation skip
\defskip medskip
\quotes_language english
\quotes_times 2
\papercolumns 1
\papersides 2
\paperpagestyle empty
\layout Standard
\begin_inset Minipage
position 0
inner_position 0
height "1pt"
width "67col%"
collapsed false
\layout Standard
\begin_inset Graphics
filename eps/crittera.eps.gz
lyxscale 10
display color
width 1.6cm
height 1.6cm
\end_inset
\SpecialChar ~
\SpecialChar ~
\begin_inset Graphics
filename eps/critterb.eps.gz
lyxscale 10
display color
width 1.6cm
height 1.6cm
\end_inset
\SpecialChar ~
\SpecialChar ~
\begin_inset Graphics
filename eps/critterc.eps.gz
lyxscale 10
display color
width 1.6cm
height 1.6cm
\end_inset
\SpecialChar ~
\SpecialChar ~
\begin_inset Graphics
filename eps/critterd.eps.gz
lyxscale 10
display color
width 1.6cm
height 1.6cm
\end_inset
\newline
\SpecialChar ~
\newline
\begin_inset Graphics
filename eps/crittere.eps.gz
lyxscale 10
display color
width 1.6cm
height 1.6cm
\end_inset
\SpecialChar ~
\SpecialChar ~
\begin_inset Graphics
filename eps/critterf.eps.gz
lyxscale 10
display color
width 1.6cm
height 1.6cm
\end_inset
\SpecialChar ~
\SpecialChar ~
\begin_inset Graphics
filename eps/critterg.eps.gz
lyxscale 10
display color
width 1.6cm
height 1.6cm
\end_inset
\SpecialChar ~
\SpecialChar ~
\begin_inset Graphics
filename eps/critterh.eps.gz
lyxscale 10
display color
width 1.6cm
height 1.6cm
\end_inset
\end_inset
\begin_inset Minipage
position 1
inner_position 0
height "1pt"
width "33col%"
collapsed false
\layout Standard
\series bold
\size large
The
\newline
AlphaBeast
\newline
Book
\newline
\SpecialChar ~
\newline
by
\newline
Garst R.
Reese
\end_inset
\layout Standard
\pagebreak_bottom \noindent
\begin_inset Graphics
filename eps/critteri.eps.gz
lyxscale 10
display color
width 1.6cm
height 1.6cm
\end_inset
\SpecialChar ~
\SpecialChar ~
\begin_inset Graphics
filename eps/critterj.eps.gz
lyxscale 10
display color
width 1.6cm
height 1.6cm
\end_inset
\SpecialChar ~
\SpecialChar ~
\begin_inset Graphics
filename eps/critterk.eps.gz
lyxscale 10
display color
width 1.6cm
height 1.6cm
\end_inset
\SpecialChar ~
\SpecialChar ~
\beg
Re: book that prints with 1.3.7 is screwed up with 1.4.1
Attached .tex files simplified by changing all graphic letters to o found in crittero... Hope this helps. Garst Martin Vermeer wrote: On Tue, Apr 18, 2006 at 10:18:02PM +0200, Michael Gerz wrote: Garst R. Reese wrote: Attached you will find the cover pdf generated with ps2pdf from the print to file output from 1.3.7. I cannot provide the equivalent pdf from 1.4.1 because ps2pdf aborts with errors. View pdf works but instead of 5 lines of letters, there are only 4 and the title is raised a few cm. The difference in the .lyx files is that 1.3.7 says begin_inset Minipage and 1.4.1 begin inset Box Frameless Garst, could you please provide us with a simple test case (minimized LyX file) and add a report to bugzilla? And what is the LaTeX code produced by both? If 1.4.1 and 1.3.7 do not produce the same output, there is a serious regression. The problem could be in lyx2lyx (Minipage -> Box). - Martin Abookcover1.3.7.tex Description: TeX document Abookcover1.4.1.tex Description: TeX document crittero.eps.gz Description: GNU Zip compressed data
Re: moc not mentioned in INSTALL or README
Jose' Matos wrote: On Saturday 02 July 2005 04:18, Garst R. Reese wrote: Hi folks, I'm trying to install lyx-1.3.5 in Fedora core 4. configure tells me I don't have moc, and I don't. Nor do I know where to get it or what the containing pkg is called. It's strange because FC2 installed it. $ which moc /usr/bin/moc $ rpm -qf /usr/bin/moc qt-devel-3.3.4-15.1 This should question belongs to the FAQ. :-) If it is not there it should be. Thanks Jose' I would suggest in INSTALL: 0) Linux users beware: if compiling the Qt frontend, you need qt and qt-devel packages of the same version to compile LyX. If which moc fails to find moc, qt-devel is not installed. Regards to all, Garst
Re: moc not mentioned in INSTALL or README
Jose' Matos wrote: On Saturday 02 July 2005 04:18, Garst R. Reese wrote: Hi folks, I'm trying to install lyx-1.3.5 in Fedora core 4. configure tells me I don't have moc, and I don't. Nor do I know where to get it or what the containing pkg is called. It's strange because FC2 installed it. $ which moc /usr/bin/moc $ rpm -qf /usr/bin/moc qt-devel-3.3.4-15.1 This should question belongs to the FAQ. :-) If it is not there it should be. Thanks Jose' I would suggest in INSTALL: 0) Linux users beware: if compiling the Qt frontend, you need qt and qt-devel packages of the same version to compile LyX. If "which moc" fails to find moc, qt-devel is not installed. Regards to all, Garst
moc not mentioned in INSTALL or README
Hi folks, I'm trying to install lyx-1.3.5 in Fedora core 4. configure tells me I don't have moc, and I don't. Nor do I know where to get it or what the containing pkg is called. It's strange because FC2 installed it. Please cc me. Thanks Garst
moc not mentioned in INSTALL or README
Hi folks, I'm trying to install lyx-1.3.5 in Fedora core 4. configure tells me I don't have moc, and I don't. Nor do I know where to get it or what the containing pkg is called. It's strange because FC2 installed it. Please cc me. Thanks Garst
Re: import and insert file
Thanks Georg The command line for wp2latex is: wp2latex [input_file [output_file]] [switches] The man page gives details of switches. I can post it to list if requested. pls cc me. Garst
Re: import and insert file
Thanks Jeurgen The bugzilla file said: follow these steps to define a new converter in 1.3.6: 1. Select from and to formats in the comboxes 2. Press New. The New converter will be added to the browser, but neither the commands not the flags will be applied 3. Now add commands and flags and press Modify. This will also save those. I first had to go to file formats and use New to add wordperfect WordPerfect wpd Then the from and to format comboxes worked After pressing Modify, I still had to press Save to get WordPerfect to appear in the Import list. Works now.
Re: import and insert file
Thanks Georg The command line for wp2latex is: wp2latex [input_file [output_file]] [switches] The man page gives details of switches. I can post it to list if requested. pls cc me. Garst
Re: import and insert file
Thanks Jeurgen The bugzilla file said: follow these steps to define a new converter in 1.3.6: 1. Select "from" and "to" formats in the comboxes 2. Press "New". The New converter will be added to the browser, but neither the commands not the flags will be applied 3. Now add commands and flags and press "Modify". This will also save those. I first had to go to file formats and use New to add wordperfect WordPerfect wpd Then the from and to format comboxes worked After pressing Modify, I still had to press Save to get WordPerfect to appear in the Import list. Works now.
import and insert file
Hi folks, I frequently get short .doc or .wpd files that get converted to tex with wv or wp2latex. The latest versions of both are now working quite well. Import file lists all of the possibilities that I have conversion software installed for, but Insert file does not. It would be more convenient if I had to option of Importing a file to the current document. As things now stand (1.3.5) I have to: 1. run wp2latex if it is a .wpd file to create a .tex file 2. Import the .tex file or the .doc file 3. Insert the file in the master document 4. Clean up the mess. I tried adding a converter for wp2latex but clicking on New under converters does not seem to work. It would be nice if lyx would check for wp2latex and set up the converter. Well, as long as I'm complaining, it would be nice if the README or INSTALL file listed the external packages, like wv, that enhance the utility of LyX. At present, the only way of discovering this is to look at the configure output to see which packages it is checking for. My guess is that a lot of users don't even know that they can import .doc files. Cheers Thanks Garst
import and insert file
Hi folks, I frequently get short .doc or .wpd files that get converted to tex with wv or wp2latex. The latest versions of both are now working quite well. Import file lists all of the possibilities that I have conversion software installed for, but Insert file does not. It would be more convenient if I had to option of Importing a file to the current document. As things now stand (1.3.5) I have to: 1. run wp2latex if it is a .wpd file to create a .tex file 2. Import the .tex file or the .doc file 3. Insert the file in the master document 4. Clean up the mess. I tried adding a converter for wp2latex but clicking on New under converters does not seem to work. It would be nice if lyx would check for wp2latex and set up the converter. Well, as long as I'm complaining, it would be nice if the README or INSTALL file listed the external packages, like wv, that enhance the utility of LyX. At present, the only way of discovering this is to look at the configure output to see which packages it is checking for. My guess is that a lot of users don't even know that they can import .doc files. Cheers & Thanks Garst
blanket-permission.txt:
Greetings Angus and all, You most certainly have my permission to add my name and meager contributions to the blanket permissions. Thanks for all your help! Garst
blanket-permission.txt:
Greetings Angus and all, You most certainly have my permission to add my name and meager contributions to the blanket permissions. Thanks for all your help! Garst
epigraph problems
Hi folks, It's been a long time since I bugged you.
With Lyx 1.3.5, I'm trying to put a photo on either a chapter or Part
page with a command like
\epigraphhead[30]{\includegraphics[scale=0.5]{kids.eps}}
If I leave off the \ before the includegraphics, it puts out the text
where it should be.
When I put the \ in, I get a latex error. With Chapter, I put the
command after the Chapter, and get a message that \newpage is an
undefined control sequence.
If I put it before a Part, it says that \part is an undefined control
sequence.
I'm following the instructions in Herbert's epigraph.lyx and the
epigraph.pdf file from CTAN.
Most important, Happy Holidays and a Great New Year!
Garst
epigraph problems
Hi folks, It's been a long time since I bugged you.
With Lyx 1.3.5, I'm trying to put a photo on either a chapter or Part
page with a command like
\epigraphhead[30]{\includegraphics[scale=0.5]{kids.eps}}
If I leave off the \ before the includegraphics, it puts out the text
where it should be.
When I put the \ in, I get a latex error. With Chapter, I put the
command after the Chapter, and get a message that \newpage is an
undefined control sequence.
If I put it before a Part, it says that \part is an undefined control
sequence.
I'm following the instructions in Herbert's epigraph.lyx and the
epigraph.pdf file from CTAN.
Most important, Happy Holidays and a Great New Year!
Garst
Re: Hollywood class
Kayvan A. Sylvan wrote: In the current CVS, when writing a document with the hollywood class, I am noticing that the author's address (entered in the Right Address paragraph style) is not rendered in the final output. Does anyone know what is happening there? Garst, if you are reading this, can you check? It happens with the examples/script_form.lyx as well. Thanks! Hi folks, I don't have current CVS up. With 1.3.2 script_form.lyx works fine. Here's the lyx entry with format 221. FOR A FEW DAYS MORE \layout Author \added_space_bottom vfill by \newline April Rider \layout Right Address \pagebreak_bottom April Rider \newline 555 George St. NNW \newline Kaplan, ND 7 \newline 999-999- I'm in the midst of moving, so pressed for time. What is the status of 1.4CVS now? I'll resubsribed after the holidays. Cheers, Garst
Re: Hollywood class
"Kayvan A. Sylvan" wrote: > > In the current CVS, when writing a document with the hollywood class, > I am noticing that the author's address (entered in the "Right Address" > paragraph style) is not rendered in the final output. > > Does anyone know what is happening there? > > Garst, if you are reading this, can you check? It happens with the > examples/script_form.lyx as well. > > Thanks! Hi folks, I don't have current CVS up. With 1.3.2 script_form.lyx works fine. Here's the lyx entry with format 221. FOR A FEW DAYS MORE \layout Author \added_space_bottom vfill by \newline April Rider \layout Right Address \pagebreak_bottom April Rider \newline 555 George St. NNW \newline Kaplan, ND 7 \newline 999-999- I'm in the midst of moving, so pressed for time. What is the status of 1.4CVS now? I'll resubsribed after the holidays. Cheers, Garst
lyx.org
Can't view it with Netscape 4.75 any more, but it looks good under Opera. Bye for awhile, Garst
lyx.org
Can't view it with Netscape 4.75 any more, but it looks good under Opera. Bye for awhile, Garst
Re: [Patch] Element inset, XML
Lars Gullik Bjønnes wrote: We called it LCS a long time. -- Lgb LyxCharStyle ? Garst
Re: [Patch] Element inset, XML
Lars Gullik Bjønnes wrote: > We called it LCS a long time. > > -- > Lgb LyxCharStyle ? Garst
Re: [Patch] Element inset, XML
Lars Gullik Bjønnes wrote: Perhaps better, perhaps not... in the .layout file this can be used, but when inserted by the user (in some dialog) I don't want the user to be required to know what the latex will look like. Noble goal, I must admit that I resort to the LaTeX Companion far less often than I used to :) But still keep it in view. I'm impressed by how much the clean-up has speeded up productive developments. It's a good lesson. I lurk because I learn. Garst
Re: [Patch] Element inset, XML
Martin Vermeer wrote: Don't let the perfect be the enemy of the adequate. Who said The cost of perfection is bankrupty ? Garst
Re: [Patch] Element inset, XML
Jose' Matos wrote: 2) UI where it is assumed that the box inside a box model is too difficult for the normal user to grasp. Does LyX have any normal users ? Garst
Re: [Patch] Element inset, XML
Lars Gullik Bjønnes wrote: > > Perhaps better, perhaps not... in the .layout file this can be used, > but when inserted by the user (in some dialog) I don't want the user > to be required to know what the latex will look like. Noble goal, I must admit that I resort to the LaTeX Companion far less often than I used to :) But still keep it in view. I'm impressed by how much the "clean-up" has speeded up productive developments. It's a good lesson. I lurk because I learn. Garst
Re: [Patch] Element inset, XML
Martin Vermeer wrote: > Don't let the perfect be the enemy of the adequate. Who said "The cost of perfection is bankrupty" ? Garst
Re: [Patch] Element inset, XML
Jose' Matos wrote: > 2) UI where it is assumed that the box inside a box model is too difficult > for the normal user to grasp. > Does LyX have any "normal" users ? Garst
Re: ostream v.s. ostream.h
Lars Gullik Bjønnes wrote: Also first gcc compiler in the 3 series was released June 18. 2001. that is now almost two years ago... still there are distributions that use gcc 2.95 in their stable setups. -- Lgb And I still run into apps that will only compile with 2.95, which may explain why some dists use it. There's no excuse for 2.96 tho. Garst
Re: ostream v.s. ostream.h
Lars Gullik Bjønnes wrote: > Also first gcc compiler in the 3 series was released June 18. 2001. > that is now almost two years ago... still there are distributions that > use gcc 2.95 in their "stable" setups. > > -- > Lgb And I still run into apps that will only compile with 2.95, which may explain why some dists use it. There's no excuse for 2.96 tho. Garst
1.3.3cvs spellchecker problem
LyX 1.3.3cvs of Tue, May 6 2003 Built on Sep 9 2003, 23:43:50 Configuration Host type: i586-pc-linux-gnu Special build flags:warnings assertions xforms-image-loader C Compiler: gcc C Compiler flags: -O2 C++ Compiler: g++ (3.2) C++ Compiler flags: -O2 -fno-exceptions -W -Wall Linker flags: Frontend: xforms libXpm version: 4.11 libforms version: 1.0.2 LyX binary dir: /usr/local/bin LyX files dir: /usr/local/share/lyx When I try to spellcheck I get pop-up saying that lyx could not communicate with the spell-checker. Then the spell-checker pop-up appears saying it has checked 5%. Configured --with-aspell. bash$ aspell --version @(#) International Ispell Version 3.1.20 (but really Aspell 0.50.3) Preferences agrees that I am using aspell. It worked earlier with 1.2 something and this is the first time in some years that I have had a problem. Garst
1.3.3cvs spellchecker problem
LyX 1.3.3cvs of Tue, May 6 2003 Built on Sep 9 2003, 23:43:50 Configuration Host type: i586-pc-linux-gnu Special build flags:warnings assertions xforms-image-loader C Compiler: gcc C Compiler flags: -O2 C++ Compiler: g++ (3.2) C++ Compiler flags: -O2 -fno-exceptions -W -Wall Linker flags: Frontend: xforms libXpm version: 4.11 libforms version: 1.0.2 LyX binary dir: /usr/local/bin LyX files dir: /usr/local/share/lyx When I try to spellcheck I get pop-up saying that lyx could not communicate with the spell-checker. Then the spell-checker pop-up appears saying it has checked 5%. Configured --with-aspell. bash$ aspell --version @(#) International Ispell Version 3.1.20 (but really Aspell 0.50.3) Preferences agrees that I am using aspell. It worked earlier with 1.2 something and this is the first time in some years that I have had a problem. Garst
Re: InseetExternal can now preview stuff too
Looks like a good candidate for examples to show how you did that :) Garst Angus Leeming wrote: The preview code is starting to show its age and needs a clean-up but the inset's interface with it is starting to look Ok. Attached is a screen shot for any xfig users out there... -- Angus
Re: InseetExternal can now preview stuff too
Looks like a good candidate for examples to show how you did that :) Garst Angus Leeming wrote: > > The preview code is starting to show its age and needs a clean-up but > the inset's interface with it is starting to look Ok. > > Attached is a screen shot for any xfig users out there... > > -- > Angus
Re: Configuring the makefile
Kostantino wrote: Hi. In the INSTALL file I read: --enable-optimization=VALUE enables you to set optimization to a higher level as the default (-O), for example --enable-optimization=-O3. So I give the following configure command: ./configure --with-frontend=qt --enable-optimization=-O3 but after the make command I read: g++: unrecognised option '-03' This behaviour still remains if I give before the command: CXXFLAGS='-03' for BASH. I use Linux-2.4.22 on Slackware 9.1, LyX-1.3.3, gcc (GCC) 3.2.3, g++ (GCC) 3.2.3 Any suggestions for me? Perhaps I wrong something? best regards Costantino Try --enable-optimisation=-O3 I think that is what WFM. Garst
Re: Configuring the makefile
John Levon wrote: On Tue, Oct 21, 2003 at 07:36:57PM +0200, Kostantino wrote: but after the make command I read: g++: unrecognised option '-03' You typed zero-three -03 instead of oh-three -O3. See ? Oh! Good spotting John. I can't believe how stupid IBM was to put the 0 above the O instead of to the left of the 1 where it belongs. Garst
Re: Configuring the makefile
Kostantino wrote: > > Hi. > In the INSTALL file I read: > > --enable-optimization=VALUE enables you to set optimization >to a higher level as the default (-O), for example > --enable-optimization=-O3. > > So I give the following configure command: > > ./configure --with-frontend=qt --enable-optimization=-O3 > > but after the make command I read: > > g++: unrecognised option '-03' > > This behaviour still remains if I give before the command: > > CXXFLAGS='-03' > > for BASH. > > I use Linux-2.4.22 on Slackware 9.1, LyX-1.3.3, gcc (GCC) 3.2.3, > g++ (GCC) 3.2.3 > Any suggestions for me? Perhaps I wrong something? > > best regards > > Costantino Try --enable-optimisation="-O3" I think that is what WFM. Garst
Re: Configuring the makefile
John Levon wrote: > > On Tue, Oct 21, 2003 at 07:36:57PM +0200, Kostantino wrote: > > > but after the make command I read: > > > > g++: unrecognised option '-03' > > You typed zero-three "-03" instead of oh-three "-O3". See ? > Oh! Good spotting John. I can't believe how stupid IBM was to put the 0 above the O instead of to the left of the 1 where it belongs. Garst
html hyperlinks TOC
Is there an html converter that will convert the TOC to hyperlinks, preserving navigation? Garst
html hyperlinks & TOC
Is there an html converter that will convert the TOC to hyperlinks, preserving navigation? Garst
Re: [bugzilla-daemon@lyx.org: [Bug 1421] Regression: menu items vanish]
Andre Poenitz wrote: I find this horribly bad UI. A user never gets to know the 'thing is there' unless he happens to check the menus at the right time. Agree strongly, Garst
Re: [bugzilla-daemon@lyx.org: [Bug 1421] Regression: menu items vanish]
Andre Poenitz wrote: > I find this horribly bad UI. A user never gets to know the 'thing is > there' unless he happens to check the menus at the right time. Agree strongly, Garst
Re: reverting to 1.3.3 from 1.4cvs?
You're welcome, I gave up on cvs because it cleared my tables when I tried to insert a row, then crashed. Do you not have this problem? Garst Nirmal Govind wrote: Thanks Garst... that script works great! I think I'm still going to stick with cvs, I feel a little more secure knowing that this script can (hopefully) get me out of trouble if I do run into major problems with cvs and need to go back to 1.3... nirmal
Re: reverting to 1.3.3 from 1.4cvs?
Jose' Matos wrote: If this helps any of you I am working and will commit soon a process where lyx2lyx is able to downgrade gracefully to the previous stable version. That will be nice. Thanks. Garst
Re: reverting to 1.3.3 from 1.4cvs?
You're welcome, I gave up on cvs because it cleared my tables when I tried to insert a row, then crashed. Do you not have this problem? Garst Nirmal Govind wrote: > > Thanks Garst... that script works great! I think I'm still going to > stick with cvs, I feel a little more secure knowing that this script can > (hopefully) get me out of trouble if I do run into major problems with > cvs and need to go back to 1.3... > > nirmal >
Re: reverting to 1.3.3 from 1.4cvs?
Jose' Matos wrote: > If this helps any of you I am working and will commit soon a process where > lyx2lyx is able to downgrade gracefully to the previous stable version. > That will be nice. Thanks. Garst
Re: reverting to 1.3.3 from 1.4cvs?
See the attached, not sure whether Andre or Angus contributed it, but it what I used to solve your problem. Garst Nirmal Govind wrote: Hi.. so I need to port a couple of documents back to 1.3.3 from 1.4cvs.. and looks like 1.3.3 can't read the 1.4cvs doc, not in any decent manner... is there any way to restore my document so that I can start editing it in 1.3.3 again? I converted to .tex and then imported it and that did almost everything.. didn't do the figure/table floats properly... please let me know if there's a better way.. btw, the reason I need to go back to 1.3.3 is cos the table editing is broken now in cvs - can't center the field, undo magically deletes all the entries in the table etc.. Thanks, nirmal lyx225to221.sh Description: Bourne shell script
Re: reverting to 1.3.3 from 1.4cvs?
See the attached, not sure whether Andre or Angus contributed it, but it what I used to solve your problem. Garst Nirmal Govind wrote: > > Hi.. so I need to port a couple of documents back to 1.3.3 from 1.4cvs.. > and looks like 1.3.3 can't read the 1.4cvs doc, not in any decent > manner... is there any way to restore my document so that I can start > editing it in 1.3.3 again? I converted to .tex and then imported it and > that did almost everything.. didn't do the figure/table floats > properly... please let me know if there's a better way.. btw, the > reason I need to go back to 1.3.3 is cos the table editing is broken now > in cvs - can't center the field, undo magically deletes all the entries > in the table etc.. > > Thanks, > nirmal lyx225to221.sh Description: Bourne shell script
Re: building 1.3.4cvs
Juergen Spitzmueller wrote: I have splitted I mention this only because I have seen it many times from many people, and it works its way into docs and comments. There is no word splitted. I split it I have split it I will split it We have split the difference That's my kind of verb :) Garst
Re: building 1.3.4cvs
Juergen Spitzmueller wrote: = A false friend. In german, we have the participle gesplittet (which is, of course, a loanword and means, basically, the same). So I could argue I just wanted to teach you some german ;-) Lots of luck. My german prof. thanked me for making him laugh so much, and for that did not fail me ;) Garst
Re: The Compleat Box
Jose' Matos wrote: On Tuesday 30 September 2003 15:59, Martin Vermeer wrote: BTW I think this should replace the existing minipage, which means reLyX should be adapted to convert the old docs. That's lyx2lyx business. Yes, I am behind the times. I am sorry but I disagree here, and as me other people. :-) You disagree with? A. BTW B. That's C. Yes ? Garst
Re: building 1.3.4cvs
Juergen Spitzmueller wrote: > I have splitted I mention this only because I have seen it many times from many people, and it works its way into docs and comments. There is no word splitted. I split it I have split it I will split it We have split the difference That's my kind of verb :) Garst
Re: building 1.3.4cvs
Juergen Spitzmueller wrote: => A false friend. In german, we have the participle "gesplittet" (which is, of > course, a loanword and means, basically, the same). So I could argue I just > wanted to teach you some german ;-) Lots of luck. My german prof. thanked me for making him laugh so much, and for that did not fail me ;>) Garst
Re: The Compleat Box
Jose' Matos wrote: > > On Tuesday 30 September 2003 15:59, Martin Vermeer wrote: > > > > > > BTW I think this should replace the existing minipage, which means > > > > reLyX should be adapted to convert the old docs. > > > > > > That's lyx2lyx business. > > > > Yes, I am behind the times. > > I am sorry but I disagree here, and as me other people. :-) You disagree with? A. BTW B. That's C. Yes ? Garst
Re: 1.3.3 announcements
My kids are all big time mac users, so the sooner the better. Garst Jean-Marc Lasgouttes wrote: John == John Levon [EMAIL PROTECTED] writes: John Has somebody taken care of announcing to the usual places ? John LWN, LinuxToday, apps.kde.com etc. The announcement was Bcc'd to [EMAIL PROTECTED] I did not try the others. BTW it already transpires that I forgot to add a few macosx-related files to EXTRA_DIST (talk about compiling out of the box!) and that qfont_loader.C does not compile (probably missing header) on qt/mac 3.1.2 (at least). If there are many qt version where this happens, we may need to release 1.3.4 soon. JMarc
Re: 1.3.3 announcements
My kids are all big time mac users, so the sooner the better. Garst Jean-Marc Lasgouttes wrote: > > > "John" == John Levon <[EMAIL PROTECTED]> writes: > > John> Has somebody taken care of announcing to the usual places ? > > John> LWN, LinuxToday, apps.kde.com etc. > > The announcement was Bcc'd to [EMAIL PROTECTED] I did not try the others. > > BTW it already transpires that I forgot to add a few macosx-related > files to EXTRA_DIST (talk about compiling out of the box!) and that > qfont_loader.C does not compile (probably missing header) on qt/mac > 3.1.2 (at least). If there are many qt version where this happens, we > may need to release 1.3.4 soon. > > JMarc
Re: Towards LyX 1.3.3 (status update #4)
Jean-Marc Lasgouttes wrote: Angus == Angus Leeming [EMAIL PROTECTED] writes: Angus and here are a couple of fixes to this announcement, JMarc. Thanks a lot. Something caught my eyes in the diff: -Prebuild binaries (mainly rpms for linux distributions) should soon be +Prebuild binaries (mainly rpms for linux distributions) should soon be Shouldn't this be 'Prebuilt'? Or something else? JMarc Yes, its been that way for awhile, and patchws is spelled patches :) I thought the last sentence was a bit awkward. Here's a patch on top of Angus' patch. Garst--- 1_3_3.txt~ Wed Sep 24 08:06:02 2003 +++ 1_3_3.txt Wed Sep 24 08:15:02 2003 @@ -44,12 +44,12 @@ ftp://ftp.icm.edu.pl/vol/rzm0/lyx/stable/lyx-1.3.3.tar.gz -Prebuild binaries (mainly rpms for linux distributions) should soon be +Prebuilt binaries (mainly rpms for linux distributions) should soon be available at ftp://ftp.lyx.org/pub/lyx/bin/1.3.3/ If you already have LyX 1.3.2 sources, you may want to apply one -of the following patchws instead +of the following patches instead ftp://ftp.lyx.org/pub/lyx/stable/patch-1.3.3.gz ftp://ftp.lyx.org/pub/lyx/stable/patch-1.3.3.bz2 @@ -59,8 +59,8 @@ a bug report at http://bugzilla.lyx.org If you're having trouble using the new version of LyX, or have a question, -first check out http://www.lyx.org/help/, and e-mail the LyX users' list -([EMAIL PROTECTED]) if you can't find an answer there. +first check out http://www.lyx.org/help/. If you can't find the answer there, +e-mail the LyX users' list ([EMAIL PROTECTED]). Enjoy!
Re: 13x NEWS
Angus Leeming wrote: The complete list of improvements and fixes can be found at the end of this message. There have been bug fixes to the xforms frontend also, but most of these have been made to xforms itself. To benefit you must recompile LyX against xforms 1.0.2 or greater which is currently INSTALL says xforms 1.0 should be used. Is 1.0.2 actually required? Should INSTALL mention 1.0.2? Any idea when 1.0.2 will be released? Garst
Re: Towards LyX 1.3.3 (status update #4)
Jean-Marc Lasgouttes wrote: > > > "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes: > > Angus> and here are a couple of fixes to this announcement, JMarc. > > Thanks a lot. Something caught my eyes in the diff: > -Prebuild binaries (mainly rpms for linux distributions) should soon be > +Prebuild binaries (mainly rpms for linux distributions) should soon be > > Shouldn't this be 'Prebuilt'? Or something else? > > JMarc Yes, its been that way for awhile, and patchws is spelled patches :) I thought the last sentence was a bit awkward. Here's a patch on top of Angus' patch. Garst--- 1_3_3.txt~ Wed Sep 24 08:06:02 2003 +++ 1_3_3.txt Wed Sep 24 08:15:02 2003 @@ -44,12 +44,12 @@ ftp://ftp.icm.edu.pl/vol/rzm0/lyx/stable/lyx-1.3.3.tar.gz -Prebuild binaries (mainly rpms for linux distributions) should soon be +Prebuilt binaries (mainly rpms for linux distributions) should soon be available at ftp://ftp.lyx.org/pub/lyx/bin/1.3.3/ If you already have LyX 1.3.2 sources, you may want to apply one -of the following patchws instead +of the following patches instead ftp://ftp.lyx.org/pub/lyx/stable/patch-1.3.3.gz ftp://ftp.lyx.org/pub/lyx/stable/patch-1.3.3.bz2 @@ -59,8 +59,8 @@ a bug report at http://bugzilla.lyx.org If you're having trouble using the new version of LyX, or have a question, -first check out http://www.lyx.org/help/, and e-mail the LyX users' list -([EMAIL PROTECTED]) if you can't find an answer there. +first check out http://www.lyx.org/help/. If you can't find the answer there, +e-mail the LyX users' list ([EMAIL PROTECTED]). Enjoy!
Re: 13x NEWS
Angus Leeming wrote: > The complete list of improvements and fixes can be found at the end of > this message. There have been bug fixes to the xforms frontend also, > but most of these have been made to xforms itself. To benefit you must > recompile LyX against xforms 1.0.2 or greater which is currently INSTALL says xforms 1.0 should be used. Is 1.0.2 actually required? Should INSTALL mention 1.0.2? Any idea when 1.0.2 will be released? Garst
Re: new menu layout
Lars Gullik Bjønnes wrote: Andre Poenitz [EMAIL PROTECTED] writes: | The problem is different defaults in 1.3 and 1.4 That is not a problem. Or are you saying that we can never change defaults once we have chosen one the first time? -- Lgb My 2 pennies default.ui should be a link to one of the available ui's, inititally pointing to a setup wizard ui, which would be something like preferences. I know that before I install 1.4 on A's box, I will explain that there is a new ui available, walk her through it, and ask which she wants. Fortunately, she is my only user. At the very least, the splash screen should boldly announce the new ui and explain how to select the old one. Garst
Re: new menu layout
John Levon wrote: Existing users are likely to read the announcement Surely you jest, but it's Friday, so I'll forgive you for not adding a smiley. or have a Garst to tell them. OK when them is a very small number. But at one time, my them approached 100. Of course, they were split between Your UI sucks! , Why did you change the UI again?, all of the above. Since there is no way to win, forge on. Garst
Re: new menu layout
Lars Gullik Bjønnes wrote: > > Andre Poenitz <[EMAIL PROTECTED]> writes: > > | The problem is different defaults in 1.3 and 1.4 > > That is not a problem. > > Or are you saying that we can never change defaults once we have > chosen one the first time? > > -- > Lgb My 2 pennies default.ui should be a link to one of the available ui's, inititally pointing to a setup wizard ui, which would be something like preferences. I know that before I install 1.4 on A's box, I will explain that there is a new ui available, walk her through it, and ask which she wants. Fortunately, she is my only user. At the very least, the splash screen should boldly announce the new ui and explain how to select the old one. Garst
Re: new menu layout
John Levon wrote: > Existing users are likely to read the announcement Surely you jest, but it's Friday, so I'll forgive you for not adding a smiley. > or have a Garst to tell them. OK when "them" is a very small number. But at one time, my "them" approached 100. Of course, they were split between "Your UI sucks!" , "Why did you change the UI again?", all of the above. Since there is no way to win, forge on. Garst
Re: 1.3.3CVS lyx2lyx
Jean-Marc Lasgouttes wrote: You made up the number, didn't you? Seriously, I cannot get it. Do you have an URL? JMarc http://www.mail-archive.com/[EMAIL PROTECTED]/msg60797.html
Re: 1.3.3CVS lyx2lyx
Jean-Marc Lasgouttes wrote: Thanks. Unfortunately, the patch is a bit large for me. Unless somebody ports and tests it, I will have to politely decline the invitation ;) JMarc Most of it deals with the asserts that use bformat to make the failure msgs more useful. Porting bformat in src/support/lstrings.Ch might make it easier. Garst
Re: 1.3.3CVS lyx2lyx
Jean-Marc Lasgouttes wrote: Angus I think it as simple as this. Compiles but otherwise untested. Thanks for doing this. This is something I could take into 1.3.3, provided it is well tested. JMarc Thanks all. I will start testing. Garst
Re: 1.3.3CVS lyx2lyx
Jean-Marc Lasgouttes wrote: Thanks for doing this. This is something I could take into 1.3.3, provided it is well tested. JMarc I tried it on several book length files and it worked fine. Converted 2.15 and 2.20 files to 2.21 with acceptable speed. Thanks Angus! Garst
Re: 1.3.3CVS lyx2lyx
Jean-Marc Lasgouttes wrote: > You made up the number, didn't you? > > Seriously, I cannot get it. Do you have an URL? > > JMarc http://www.mail-archive.com/[EMAIL PROTECTED]/msg60797.html
Re: 1.3.3CVS lyx2lyx
Jean-Marc Lasgouttes wrote: > Thanks. Unfortunately, the patch is a bit large for me. Unless > somebody ports and tests it, I will have to politely decline the > invitation ;) > > JMarc Most of it deals with the asserts that use bformat to make the failure msgs more useful. Porting bformat in src/support/lstrings.Ch might make it easier. Garst
Re: 1.3.3CVS lyx2lyx
Jean-Marc Lasgouttes wrote: > Angus> I think it as simple as this. Compiles but otherwise untested. > > Thanks for doing this. This is something I could take into 1.3.3, > provided it is well tested. > > JMarc Thanks all. I will start testing. Garst
Re: 1.3.3CVS lyx2lyx
Jean-Marc Lasgouttes wrote: > Thanks for doing this. This is something I could take into 1.3.3, > provided it is well tested. > > JMarc I tried it on several book length files and it worked fine. Converted 2.15 and 2.20 files to 2.21 with acceptable speed. Thanks Angus! Garst
Re: [patch] unneeded full rebreak
John Levon wrote: On Tue, Sep 16, 2003 at 11:35:01AM +0200, Andre Poenitz wrote: BTW: I've never ever changed between buffers of UserGuide size, so even if Lars' worries were justified, it wouldn't matter in my LyX usage. I suggest you try doing it for a while, on some older hardware ... john, who remembers running lyx somewhat successfully on a 33Mhz 486 Me too :) 1.4cvs is painful on a 233Mhz 96Mb 586. Except for lyx2lyx, 1.3x is way faster. In principle, I think the code clean-up is a *good thing* , but eventually the speed has to return and the other regressions have to be attended to. In the mean time, I think the 225 to 215 script should be part of the 1.3x release. And yes, I frequently change between large (book sized) buffers. Garst
Re: [patch] unneeded full rebreak
John Levon wrote: > > On Tue, Sep 16, 2003 at 11:35:01AM +0200, Andre Poenitz wrote: > > > BTW: I've never ever changed between buffers of UserGuide size, so > > even if Lars' worries were justified, it wouldn't matter in my LyX > > usage. > > I suggest you try doing it for a while, on some older hardware ... > > john, who remembers running lyx somewhat successfully on a 33Mhz 486 > Me too :) 1.4cvs is painful on a 233Mhz 96Mb 586. Except for lyx2lyx, 1.3x is way faster. In principle, I think the code clean-up is a *good thing* , but eventually the speed has to return and the other regressions have to be attended to. In the mean time, I think the 225 to 215 script should be part of the 1.3x release. And yes, I frequently change between large (book sized) buffers. Garst
Re: 1.3.3CVS lyx2lyx
Jean-Marc Lasgouttes wrote: Garst == Garst R Reese [EMAIL PROTECTED] writes: Garst I have the same problem I had in 1.4CVS. lyx2lyx takes forever Garst converting a 220 to 221 file. Lars fixed it in 1.4 by writing a Garst tmp file instead of converting in place. Any chance of porting Garst that patch to 1.3.x? Thanks, Garst I would definitely be OK with me (if such a port is possible) JMarc For reference, Lars posted a patch to 1.4 in msg60797 Garst
Re: 1.3.3CVS lyx2lyx
Jean-Marc Lasgouttes wrote: > > >>>>> "Garst" == Garst R Reese <[EMAIL PROTECTED]> writes: > > Garst> I have the same problem I had in 1.4CVS. lyx2lyx takes forever > Garst> converting a 220 to 221 file. Lars fixed it in 1.4 by writing a > Garst> tmp file instead of converting in place. Any chance of porting > Garst> that patch to 1.3.x? Thanks, Garst > > I would definitely be OK with me (if such a port is possible) > > JMarc For reference, Lars posted a patch to 1.4 in msg60797 Garst
1.3.3CVS lyx2lyx
I have the same problem I had in 1.4CVS. lyx2lyx takes forever converting a 220 to 221 file. Lars fixed it in 1.4 by writing a tmp file instead of converting in place. Any chance of porting that patch to 1.3.x? Thanks, Garst
1.3.3CVS lyx2lyx
I have the same problem I had in 1.4CVS. lyx2lyx takes forever converting a 220 to 221 file. Lars fixed it in 1.4 by writing a tmp file instead of converting in place. Any chance of porting that patch to 1.3.x? Thanks, Garst
CRASH 1.4CVS
Create a table with entries, or use existing table. Try to add a row. This clears the table :( Try to close the file, discarding changes. Boom. Garst
Re: And it was all worth it in the end ;-)
Angus Leeming wrote: Right. The Qt frontend takes forever to build. Fancy writing an fltk frontend for LyX? FLTK is designed to be small and modular enough to be statically linked - the hello program is only 97k when compiled on an x86 Linux system! I love the use only here. 97k to say hello? Everything is relative is guess. Garst And, of course, FLTK is Fast and Light and runs natively under both *nix and Windows. I don't know if it supports unicode though.
CRASH 1.4CVS
Create a table with entries, or use existing table. Try to add a row. This clears the table :( Try to close the file, discarding changes. Boom. Garst
Re: And it was all worth it in the end ;-)
Angus Leeming wrote: > Right. The Qt frontend takes forever to build. Fancy writing an fltk frontend > for LyX? FLTK is designed to be small and modular enough to be statically linked - the "hello" program is only 97k when compiled on an x86 Linux system! I love the use "only" here. 97k to say hello? Everything is relative is guess. Garst > And, of course, FLTK is Fast and Light and runs natively under both *nix and > Windows. I don't know if it supports unicode though. >
