Re: XForms 1.0 and LyX 1.2.3 RPMs and SRPMs for Red Hat Linux 7.3 and 8.0
Daniel == Daniel Tschan [EMAIL PROTECTED] writes: Daniel Hi JMarc I have taken your binaries and put them on ftp.lyx.org/pub/lyx/bin/1.2.3. I hope they will work fine with the xforms rpm we have at ftp.lyx.org/pub/lyx/contrib :) Daniel Great. It looks like they work with all xforms rpms in the Daniel contrib directory, 0.88, 0.89 and 1.0. That would be very strange, since 0.88 is not binary compatible with 1.0 (for example, it has no image library). But it may be that 0.89 and 1.0 are imilar enough. Anyway, people, please use 1.0 instead. JMarc
Re: Link to preview-latex in NEWS file
On Tue, Jan 21, 2003 at 09:48:30AM +0100, Michael Schmitt wrote: I think we should provide a link to the preview-latex homepage in the NEWS file. Ok. I also wonder whether we should activate preview-latex by default No. There are still rough edges (display jumping) and there are conceptual problems (fancy preambles) that make this wonderful feature unusable under some circumstances. It certainly should not default to on. and how we draw the user's attention to this wonderful feature. I guess many users will not use it simply because they don't know it (of course, the same applies for aiksaurus, pspell, and checktex). Maybe we should add a section to About LyXVersion concerning available/missing third-party libraries? Like putting in configure output? Andre' -- Those who desire to give up Freedom in order to gain Security, will not have, nor do they deserve, either one. (T. Jefferson)
Re: [patch] relyx
[EMAIL PROTECTED] (Lars Gullik Bjønnes) writes:
| [EMAIL PROTECTED] (Lars Gullik Bjønnes) writes:
|
| | Can some of you relyx people have a look at case 638 and see if this
| | patch has any relevance?
| |
| | It kindo seems that it fixes things, but I won't apply anything until
| | I have confirmations.
This patch became a bit larger than intended, due to ws changes.
This is the cut down version.
| @@ -1400,7 +1400,8 @@ sub ConvertToLayout {
| print \nChanging $dummy $name to layout $layout if $debug_on;
|
| # Nest if the layout stack has more than just Standard in it
| -if ($#{$CurrentLayoutStack} 0) {
| +if ($#{$CurrentLayoutStack} 0
| + $CurrentLayoutStack =~ /^$ListLayouts$/o) {
| # Die here for sections things that can't be nested!
| print Nesting! if $debug_on;
| print OUTFILE \n\\begin_deeper ;
| @@ -1474,7 +1475,8 @@ sub EndLayout {
| # \end_deeper \begin_deeper in the LyX file. It's sloppy
| # but it works, and LyX will get rid of it when it
| # resaves the file.
| -if ($#{$CurrentLayoutStack} 0) {
| +if ($#{$CurrentLayoutStack} 0
| + $CurrentLayoutStack =~ /^$ListLayouts$/o) {
| print End Nesting! if $debug_on;
| print OUTFILE \n\\end_deeper ;
| }
--
Lgb
[PATCH] Re: Link to preview-latex in NEWS file
Andre Poenitz wrote: On Tue, Jan 21, 2003 at 09:48:30AM +0100, Michael Schmitt wrote: I think we should provide a link to the preview-latex homepage in the NEWS file. Ok. See attachment for patch. I also wonder whether we should activate preview-latex by default No. There are still rough edges (display jumping) and there are conceptual problems (fancy preambles) that make this wonderful feature unusable under some circumstances. It certainly should not default to on. I know the first problem and I would be happy to see a fix for it. But what is the second problem (fancy preambles)? BTW: Has anybody tested the new version 0.7.8? They have changed the handling of color.sty. Maybe this is related to the problem mentioned above or the LyX color handling. nd how we draw the user's attention to this wonderful feature. I guess many users will not use it simply because they don't know it (of course, the same applies for aiksaurus, pspell, and checktex). Maybe we should add a section to About LyXVersion concerning available/missing third-party libraries? Like putting in configure output? Yes, I guess so. Unfortunately, I don't have enough knowledge to provide a patch for it. Michael -- === Michael Schmitt Telefon: +49 651 97551-40 Institut für TelematikTelefax: +49 651 97551-12 Bahnhofstrasse 30-32 WWW: http://www.ti.fhg.de D-54292 Trier E-Mail: mailto:[EMAIL PROTECTED] === Index: NEWS === RCS file: /cvs/lyx/lyx-devel/NEWS,v retrieving revision 1.48 diff -u -r1.48 NEWS --- NEWS2003/01/17 13:50:09 1.48 +++ NEWS2003/01/21 09:20:15 @@ -49,9 +49,10 @@ ** Instant preview -preview-latex is an emacs package for LaTeX that allows instant -previews of LaTeX code, so you can immediately see the visual -rendering of the LaTeX in the document. With the help of David +preview-latex is an emacs package for LaTeX that allows instant previews +of LaTeX code, so you can immediately see the visual rendering of the +LaTeX in the document. Its project home page can be found at +http://sourceforge.net/projects/preview-latex. With the help of David Kastrup, the author, current CVS LyX can harness this functionality to allow instant previews in the LyX window of math equations and figures. This feature can be immensely useful for making sure the
Re: [PATCH] Re: Link to preview-latex in NEWS file
On Tue, Jan 21, 2003 at 10:12:28AM +0100, Michael Schmitt wrote:
No. There are still rough edges (display jumping) and there are
conceptual problems (fancy preambles) that make this wonderful feature
unusable under some circumstances. It certainly should not default to on.
I know the first problem and I would be happy to see a fix for it. But
what is the second problem (fancy preambles)?
It's rather Fancy ERT not in preambles.
Preamble:
\def\foo{\bar}
Later ERT:
\def\foo{\urgs}
Math:
\foo
There is another one: Currently, \lyxlock gets written to the .tex
snippets. This indicates that preview uses the write to .lyx method
instead of write to .tex (I think this is a boolean flag somewhere,
haven't looked at it, though)
Yes, I guess so. Unfortunately, I don't have enough knowledge to provide
a patch for it.
The ERT problem is unsolvable.
Andre'
--
Those who desire to give up Freedom in order to gain Security,
will not have, nor do they deserve, either one. (T. Jefferson)
Re: CJK-LyX-1.2.3
On 20 Jan 2003, Jean-Marc Lasgouttes wrote: That's OK woth me. I was just pointing out that, if you want to have a release of xforms you can rely on, it would be nice to try to propose something right now... JMarc With your encouragement(?), I've changed my mind and will send the patch to the xforms mailing list. Attached is the patch(xforms-1.0-xim.patch). I've also attached CJK-LyX patch (CJK-LyX-1.3.0pre2-patch) to this email for test. The patch is against lyx-1.3.0pre2. Feedbacks are welcome, especially from the Japanese and Chinese input users. Regards, cghan
Re: [PATCH] Re: Link to preview-latex in NEWS file
Andre Poenitz wrote: Yes, I guess so. Unfortunately, I don't have enough knowledge to provide a patch for it The ERT problem is unsolvable. :-) I didn't refer to the ERT problem but to the extension of the configure script to list all third-party products (pspell, aiksaurus, checktex, preview-latex, ...) Michael -- === Michael Schmitt Telefon: +49 651 97551-40 Institut für TelematikTelefax: +49 651 97551-12 Bahnhofstrasse 30-32 WWW: http://www.ti.fhg.de D-54292 Trier E-Mail: mailto:[EMAIL PROTECTED] ===
Re: [patch] relyx
On Tuesday 21 January 2003 09:19, Lars Gullik Bjønnes wrote:
This patch became a bit larger than intended, due to ws changes.
I noticed that, it was the reason why I didn't look to it before. :-)
This is the cut down version.
| @@ -1400,7 +1400,8 @@ sub ConvertToLayout {
| print \nChanging $dummy $name to layout $layout if $debug_on;
|
| # Nest if the layout stack has more than just Standard in it
| -if ($#{$CurrentLayoutStack} 0) {
| +if ($#{$CurrentLayoutStack} 0
| +$CurrentLayoutStack =~ /^$ListLayouts$/o) {
| # Die here for sections things that can't be nested!
| print Nesting! if $debug_on;
| print OUTFILE \n\\begin_deeper ;
| @@ -1474,7 +1475,8 @@ sub EndLayout {
| # \end_deeper \begin_deeper in the LyX file. It's sloppy
| # but it works, and LyX will get rid of it when it
| # resaves the file.
| -if ($#{$CurrentLayoutStack} 0) {
| +if ($#{$CurrentLayoutStack} 0
| +$CurrentLayoutStack =~ /^$ListLayouts$/o) {
| print End Nesting! if $debug_on;
| print OUTFILE \n\\end_deeper ;
| }
I am not a reLyX people :-), but I see the logic of your change and I say go
with it. To be on the safe side you need Kayvan's opinion. :-)
--
José Abílio
Re: [patch] relyx
José Matos [EMAIL PROTECTED] writes: | I am not a reLyX people :-), but I see the logic of your change and I say go | with it. To be on the safe side you need Kayvan's opinion. :-) Some more testing on tex files is also needed. -- Lgb
lyx 1.3pre2 does not display oe and euro symbol
Hello, I would like to switch to lyx 1.3pre2 but it does not allow me to type oe (AltGr + S + g) and euro (AltGr + e) symbols. This was possible in lyx 1.2.X. How could I do so ? Is the answer in the documentation ? regards, --Nabil Hathout
Re: [PATCH] Re: Link to preview-latex in NEWS file
Andre Poenitz wrote:
On Tue, Jan 21, 2003 at 10:12:28AM +0100, Michael Schmitt wrote:
No. There are still rough edges (display jumping) and there are
conceptual problems (fancy preambles) that make this wonderful
feature unusable under some circumstances. It certainly should not
default to on.
I know the first problem and I would be happy to see a fix for it.
But what is the second problem (fancy preambles)?
It's rather Fancy ERT not in preambles.
Preamble:
\def\foo{\bar}
Later ERT:
\def\foo{\urgs}
Math:
\foo
There is another one: Currently, \lyxlock gets written to the .tex
snippets. This indicates that preview uses the write to .lyx
method instead of write to .tex (I think this is a boolean flag
somewhere, haven't looked at it, though)
Yes, I guess so. Unfortunately, I don't have enough knowledge to
provide a patch for it.
The ERT problem is unsolvable.
Ummm. We already loop over the document to output all math macros.
Could we also output all ERT insets? I guess that there'd be an
accounting problem, as some of these ERT insets would generate output
in the dvi file and some would define variables as above. We'd have
to throw away the previews of any ERT.
The important question however is would it work as a solution to
André's unsolvable problem or would it lead to problems of its own?
I'd guess the latter, but I'm no TeXie.
--
Angus
Why is pspell not activated by default?
File NEWS states: - If you configure with --with-pspell (which uses the PSpell library for spellchecking), you will be able to automatically spell-check multi-language documents, assuming you have the right dictionaries installed. Why isn't this activated by default? Doesn't configure check for the availability of pspell? MIchael -- === Michael Schmitt Telefon: +49 651 97551-40 Institut für TelematikTelefax: +49 651 97551-12 Bahnhofstrasse 30-32 WWW: http://www.ti.fhg.de D-54292 Trier E-Mail: mailto:[EMAIL PROTECTED] ===
Re: [PATCH] Re: Link to preview-latex in NEWS file
On Tue, Jan 21, 2003 at 10:30:36AM +, Angus Leeming wrote: Ummm. We already loop over the document to output all math macros. Could we also output all ERT insets? All up to the position of the snippet. And if the snippet is moved, we can't use the cached image. And so on. This is a can of worms. I guess that there'd be an accounting problem, as some of these ERT insets would generate output in the dvi file and some would define variables as above. We'd have to throw away the previews of any ERT. The important question however is would it work as a solution to André's unsolvable problem or would it lead to problems of its own? I'd guess the latter, but I'm no TeXie. The problem is unsolvable. To get a precise preview of something you need to process _all_ the .tex up to the point of this something (and probably the next page as well). It's probably better to produce a single full dvi preview in the background all the time and snip from there instead of the current snippet based approach (which is simple and cute, but not robust at all). Please do not put too much effort into something that can't be fixed. Andre' -- Those who desire to give up Freedom in order to gain Security, will not have, nor do they deserve, either one. (T. Jefferson)
Re: [patch] relyx
Juergen Spitzmueller wrote: This does still loop on my test file (export -- reimport the attached LyX file). If I change the order in the reLyXed lyx file: \layout Enumerate + \begin_deeper \begin_float tab - \begin_deeper \layout Standard \align center \LyXTable ... then lyx reads the file correctly. HTH, Jürgen.
Re: [PATCH] Re: Link to preview-latex in NEWS file
Andre Poenitz wrote: It's probably better to produce a single full dvi preview in the background all the time and snip from there instead of the current snippet based approach (which is simple and cute, but not robust at all). Please do not put too much effort into something that can't be fixed. I think we will get serious performance problems if we produce full DVI previews all the time. After all, the problem will only occur for real power users. IMHO it would be a complete waste of time to redesign the preview code which works very well in general. Michael -- === Michael Schmitt Telefon: +49 651 97551-40 Institut für TelematikTelefax: +49 651 97551-12 Bahnhofstrasse 30-32 WWW: http://www.ti.fhg.de D-54292 Trier E-Mail: mailto:[EMAIL PROTECTED] ===
Re: [PATCH] Re: Link to preview-latex in NEWS file
On Tue, Jan 21, 2003 at 11:58:34AM +0100, Michael Schmitt wrote: After all, the problem will only occur for real power users. IMHO it would be a complete waste of time to redesign the preview code which works very well in general. But you accept that very well in general is not sufficient to be the default? Andre' -- Those who desire to give up Freedom in order to gain Security, will not have, nor do they deserve, either one. (T. Jefferson)
Re: [patch] relyx
Lars Gullik Bjønnes wrote:
This is the cut down version.
| @@ -1400,7 +1400,8 @@ sub ConvertToLayout {
| print \nChanging $dummy $name to layout $layout if $debug_on;
|
| # Nest if the layout stack has more than just Standard in it
| -if ($#{$CurrentLayoutStack} 0) {
| +if ($#{$CurrentLayoutStack} 0
| + $CurrentLayoutStack =~ /^$ListLayouts$/o) {
| # Die here for sections things that can't be nested!
| print Nesting! if $debug_on;
| print OUTFILE \n\\begin_deeper ;
| @@ -1474,7 +1475,8 @@ sub EndLayout {
| # \end_deeper \begin_deeper in the LyX file. It's sloppy
| # but it works, and LyX will get rid of it when it
| # resaves the file.
| -if ($#{$CurrentLayoutStack} 0) {
| +if ($#{$CurrentLayoutStack} 0
| + $CurrentLayoutStack =~ /^$ListLayouts$/o) {
| print End Nesting! if $debug_on;
| print OUTFILE \n\\end_deeper ;
| }
This does still loop on my test file (export -- reimport the attached LyX
file).
Jürgen.
#LyX 1.3 created this file. For more info see http://www.lyx.org/
\lyxformat 221
\textclass article
\language ngerman
\inputencoding auto
\fontscheme default
\graphics default
\paperfontsize default
\spacing single
\papersize Default
\paperpackage a4
\use_geometry 0
\use_amsmath 0
\use_natbib 0
\use_numerical_citations 0
\paperorientation portrait
\secnumdepth 3
\tocdepth 3
\paragraph_separation indent
\defskip medskip
\quotes_language german
\quotes_times 2
\papercolumns 1
\papersides 1
\paperpagestyle default
\layout Enumerate
one
\layout Enumerate
\begin_inset Float table
wide false
collapsed true
\layout Standard
\align center
\begin_inset Tabular
lyxtabular version=3 rows=1 columns=1
features
column alignment=center valignment=top leftline=true rightline=true width=0(null)
row topline=true bottomline=true
cell alignment=center valignment=top topline=true leftline=true rightline=true usebox=none
\begin_inset Text
\layout Standard
\end_inset
/cell
/row
/lyxtabular
\end_inset
\layout Caption
a table
\end_inset
\layout Enumerate
three
\the_end
Boost thinks that every C functions are in std::
It seems that I am really not able to compile 1.3.0cvs on tru64 unix with cxx. Reasons are: - there is no snprintf in tru64 4.0f, so xforms has to provide its own. the one provided in xforms lib does not compile on tru64, but it does after a patch that I sent to the xforms list. So far, so good. - LyX's configure script does not know that it has to use -lformssnp on systems that do not have snprintf. I have a patch for that. So far so good. - boost really thinks that all C functions are in std:: and uses std::fprintf and things like that all over the place. This is not good at all with cxx and probably sun's CC. I am not sure what to do about that. Ideas? JMarc
Re: [patch] relyx
[EMAIL PROTECTED] (Juergen Spitzmueller) writes: | Juergen Spitzmueller wrote: | This does still loop on my test file (export -- reimport the attached LyX | file). | | If I change the order in the reLyXed lyx file: | | \layout Enumerate | + \begin_deeper | \begin_float tab | - \begin_deeper | \layout Standard | \align center | \LyXTable | ... | | then lyx reads the file correctly. Yes, and this is part of the problem... when entering a float the current layoutstack should be pushed on a stack... and popped again when the float is handled. -- Lgb
Re: Boost thinks that every C functions are in std::
Jean-Marc Lasgouttes [EMAIL PROTECTED] writes:
| It seems that I am really not able to compile 1.3.0cvs on tru64 unix
| with cxx. Reasons are:
|
| - there is no snprintf in tru64 4.0f, so xforms has to provide its
| own. the one provided in xforms lib does not compile on tru64, but
| it does after a patch that I sent to the xforms list. So far, so
| good.
|
| - LyX's configure script does not know that it has to use -lformssnp
| on systems that do not have snprintf. I have a patch for that. So
| far so good.
|
| - boost really thinks that all C functions are in std:: and uses
| std::fprintf and things like that all over the place. This is not
| good at all with cxx and probably sun's CC. I am not sure what to do
| about that.
|
| Ideas?
can we trick fprintf into std::?
namespace std {
using ::fprintf;
}
Or something?
BUT if boost thinks that all C functions are in std::, why doesn't gcc
have problems? fprintf is not in std:: there either...
--
Lgb
[patch] mathtt fix
\mathtt is currently not properly displayed in LyX.
This is just an optical issue but qualifies as a bug I suppose.
The attached patch fixes that.
Ok to apply?
Andre'
--
Those who desire to give up Freedom in order to gain Security,
will not have, nor do they deserve, either one. (T. Jefferson)
Index: math_support.C
===
RCS file: /usr/local/lyx/cvsroot/lyx-devel/src/mathed/math_support.C,v
retrieving revision 1.64
diff -u -p -r1.64 math_support.C
--- math_support.C 11 Dec 2002 06:45:19 - 1.64
+++ math_support.C 21 Jan 2003 11:57:17 -
@@ -538,6 +538,7 @@ fontinfo fontinfos[] = {
{mathrm, LyXFont::ROMAN_FAMILY, inh_series, inh_shape, LColor::math},
{mathsf, LyXFont::SANS_FAMILY, inh_series, inh_shape, LColor::math},
{mathbb, LyXFont::MSB_FAMILY, inh_series, inh_shape, LColor::math},
+ {mathtt, LyXFont::TYPEWRITER_FAMILY, inh_series, inh_shape, LColor::math},
{cmex, LyXFont::CMEX_FAMILY, inh_series, inh_shape, LColor::none},
{cmm,LyXFont::CMM_FAMILY, inh_series, inh_shape, LColor::none},
{cmr,LyXFont::CMR_FAMILY, inh_series, inh_shape, LColor::none},
Re: Boost thinks that every C functions are in std::
On Tue, Jan 21, 2003 at 01:03:11PM +0100, Lars Gullik Bjønnes wrote: BUT if boost thinks that all C functions are in std::, why doesn't gcc have problems? fprintf is not in std:: there either... Old gcc actively ignores std, i.e. std:: and :: are the same. Andre' -- Those who desire to give up Freedom in order to gain Security, will not have, nor do they deserve, either one. (T. Jefferson)
Re: Boost thinks that every C functions are in std::
Andre Poenitz [EMAIL PROTECTED] writes: | On Tue, Jan 21, 2003 at 01:03:11PM +0100, Lars Gullik Bjønnes wrote: | BUT if boost thinks that all C functions are in std::, why doesn't gcc | have problems? fprintf is not in std:: there either... | | Old gcc actively ignores std, i.e. std:: and :: are the same. We compile a lot with non-old GCC these days. anyway, there is a config macro for boost that might help: BOOST_NO_STDC_NAMESPACE If your compiler/c++lib does not put c lib functions in std:: then this should be defined. -- Lgb
Re: [patch] mathtt fix
Andre Poenitz [EMAIL PROTECTED] writes: | \mathtt is currently not properly displayed in LyX. | This is just an optical issue but qualifies as a bug I suppose. | | The attached patch fixes that. | | Ok to apply? yes. -- Lgb
chktex problems in 1.3.0pre2
I tried chktex and got lots of: Interword spacing (`\ ') should perhaps be used. Lyxx place the error boxes in the wrong locations, about a line after where they ought to be when comparing to chktex on the exported tex file. A snippet of text: på salgsavd.(1) slik det stod. Og hvis dette ble gjort hendte det at (2)det ble gjort så grundig at (1) is the place chktex complains about, (2) is where lyx puts the error box. Some sort of line count error? Helge Hafting
Re: Boost thinks that every C functions are in std::
Lars == Lars Gullik Bjønnes [EMAIL PROTECTED] writes: Lars Andre Poenitz [EMAIL PROTECTED] writes: Lars | On Tue, Jan 21, 2003 at 01:03:11PM +0100, Lars Gullik Bjønnes wrote: Lars | BUT if boost thinks that all C functions are in std::, why Lars doesn't gcc | have problems? fprintf is not in std:: there Lars either... Lars | Lars | Old gcc actively ignores std, i.e. std:: and :: are the same. Lars We compile a lot with non-old GCC these days. Lars anyway, there is a config macro for boost that might help: Lars BOOST_NO_STDC_NAMESPACE Lars If your compiler/c++lib does not put c lib functions in std:: Lars then this should be defined. Excellent idea. I will take a look. JMarc
footnotes preview in lyx-1.3
Hi, I am now using lyx-1.3-pre2 for my dissertation and it looks great so far. Is there any possibility to turn on preview-latex for the footnotes? It seems to work in Emacs. Thanks, -- Moritz Moeller-Herrmann [EMAIL PROTECTED] wiss. Mitarbeiter, IMGB La loi, dans un grand souci d'égalité, interdit aux riches comme aux pauvres de coucher sous les ponts, de mendier dans les rues et de voler du pain. (ANATOLE FRANCE)
Re: Boost thinks that every C functions are in std::
Jean-Marc Lasgouttes wrote:
It seems that I am really not able to compile 1.3.0cvs on tru64 unix
with cxx. Reasons are:
- there is no snprintf in tru64 4.0f, so xforms has to provide its
own. the one provided in xforms lib does not compile on tru64, but
it does after a patch that I sent to the xforms list. So far, so
good.
I'm surprised, as I too had to send a patch to get things to compile,
but it was included in 1.0release. (I use 4.0e here).
I've unsubscribed from the xforms list at work and your post isn't
yet int he archive. Care to tell me what you had to do?
- LyX's configure script does not know that it has to use -lformssnp
on systems that do not have snprintf. I have a patch for that. So
far so good.
That is because it uses the snprintf functions in src/support. It
shouldn't matter whether these functions come from libformssnp.a (as
they do when compiling one of the xforms demo programs) or from
libsupport.a (as they do here when compiling LyX under 4.0e).
- boost really thinks that all C functions are in std:: and uses
std::fprintf and things like that all over the place. This is not
good at all with cxx and probably sun's CC. I am not sure what to
do about that.
There is a cxx compilation flag, -nopure_cname, that the
DEC/Compaq/HP support people told me to use. Here I configure LyX
with:
CC=cc -std1
export CC
CFLAGS=-O2
export CFLAGS
CXX=cxx -std strict_ansi
export CXX
CXXFLAGS=-nopure_cname -nocleanup -msg_display_number -msg_disable
11,193,236,261,401,445,450,611 -w1 -ptr
${PWD}/${BUILDDIR}/lyx_cxx_repository -O2
export CXXFLAGS
HTH
--
Angus
Re: [PATCH] Re: Link to preview-latex in NEWS file
Andre Poenitz wrote: On Tue, Jan 21, 2003 at 11:58:34AM +0100, Michael Schmitt wrote: After all, the problem will only occur for real power users. IMHO it would be a complete waste of time to redesign the preview code which works very well in general. But you accept that very well in general is not sufficient to be the default? The problems should simply be documented. AFAICS, if you do not use ERT, preview-latex will work fine. If you use ERT, you are responsible for any breakages you cause. -- Moritz Moeller-Herrmann [EMAIL PROTECTED] wiss. Mitarbeiter, IMGB La loi, dans un grand souci d'égalité, interdit aux riches comme aux pauvres de coucher sous les ponts, de mendier dans les rues et de voler du pain. (ANATOLE FRANCE)
Re: [PATCH] Re: Link to preview-latex in NEWS file
On Tue, Jan 21, 2003 at 02:14:31PM +0100, Moritz Moeller-Herrmann wrote: The problems should simply be documented. AFAICS, if you do not use ERT, preview-latex will work fine. Simply go into a 'a^b' inset and press C-I to lock it. No fancy preview anymore... Ok, this is the only bug I am aware of. Andre' -- Those who desire to give up Freedom in order to gain Security, will not have, nor do they deserve, either one. (T. Jefferson)
Re: footnotes preview in lyx-1.3
Moritz Moeller-Herrmann wrote: Hi, I am now using lyx-1.3-pre2 for my dissertation and it looks great so far. Is there any possibility to turn on preview-latex for the footnotes? It seems to work in Emacs. Thanks, I don't see a problem. Attached is a screenshot. Works both when typing a new equation and when loading an existing file. Perhaps you mean something else? -- Angus attachment: preview.png
Re: [PATCH] Re: Link to preview-latex in NEWS file
Andre Poenitz wrote:
There is another one: Currently, \lyxlock gets written to the .tex
snippets. This indicates that preview uses the write to .lyx
method instead of write to .tex (I think this is a boolean flag
somewhere, haven't looked at it, though)
Do you mean the 'nice' flag passed to makeLaTeXFile? I have to admit,
I just cut and pasted it from elsewhere and have no idea about it's
real meaning.
void Buffer::makeLaTeXFile(ostream os,
string const original_path,
bool nice, bool only_body, bool only_preamble)
It is passed as 'true' by the preview code. Should I reset it to
'false'?
void PreviewLoader::Impl::dumpPreamble(ostream os) const
{
// Why on earth is Buffer::makeLaTeXFile a non-const method?
Buffer tmp = const_castBuffer (buffer_);
// Dump the preamble only.
tmp.makeLaTeXFile(os, buffer_.filePath(), true, false, true);
// Loop over the insets in the buffer and dump all the math-macros.
Buffer::inset_iterator it = buffer_.inset_const_iterator_begin();
Buffer::inset_iterator end = buffer_.inset_const_iterator_end();
for (; it != end; ++it)
if (it-lyxCode() == Inset::MATHMACRO_CODE)
it-latex(buffer_, os, true, true);
--
Angus
Re: Why is pspell not activated by default?
On Tue, Jan 21, 2003 at 11:24:09AM +0100, Michael Schmitt wrote: Why isn't this activated by default? Doesn't configure check for the availability of pspell? There is no reason, IMHO. I was nervous before becuase my pspell install crashed in initialisation, but it seems this was my screwed-up system. regards john -- Anyone who quotes Rusty in their sig is an idiot. - me
Re: [PATCH] Re: Link to preview-latex in NEWS file
On Tue, Jan 21, 2003 at 01:48:40PM +, Angus Leeming wrote:
There is another one: Currently, \lyxlock gets written to the .tex
snippets. This indicates that preview uses the write to .lyx
method instead of write to .tex (I think this is a boolean flag
somewhere, haven't looked at it, though)
Do you mean the 'nice' flag passed to makeLaTeXFile? I have to admit,
I just cut and pasted it from elsewhere and have no idea about it's
real meaning.
Maybe it's called 'nice'.
for (; it != end; ++it)
if (it-lyxCode() == Inset::MATHMACRO_CODE)
it-latex(buffer_, os, true, true);
I don't really know.
Judging from
int InsetFormula::latex(Buffer const *, ostream os, bool fragile, bool) const
{
WriteStream wi(os, fragile, true);
par_-write(wi);
return wi.line();
}
that's not the place.
Andre'
--
Those who desire to give up Freedom in order to gain Security,
will not have, nor do they deserve, either one. (T. Jefferson)
Re: [PATCH] Re: Link to preview-latex in NEWS file
Andre Poenitz wrote:
Judging from
int InsetFormula::latex(Buffer const *, ostream os, bool fragile,
bool) const
{
WriteStream wi(os, fragile, true);
par_-write(wi);
return wi.line();
}
that's not the place.
Is this your way of saying that the problem lies in mathed itself?
Ie, it would go away if we had control over the 'true' passed to the
WriteStream c-tor.
Here's a minimal solution from the preview end rather than the
mathed end. We currently generate a latex file for preview-latex by:
1 Dump LyX preamble.
2 Dump the math-macros
3 Add preview-latex magic
\begin{document}
4 Dump all previewable snippets.
\end{document}
A hack might be to redefine \lyxlock between 1 and 2 as an empty
wrapper. Care to suggest a bit of LaTeX that would do this?
Alternatively, we could post-process the data passed to os by the
math insets before it is dumped to file to remove these lyxlocks.
That, however, sounds nastier.
--
Angus
Re: [PATCH] Re: Link to preview-latex in NEWS file
On Tue, Jan 21, 2003 at 02:12:42PM +, Angus Leeming wrote:
Is this your way of saying that the problem lies in mathed itself?
Ie, it would go away if we had control over the 'true' passed to the
WriteStream c-tor.
We could certainly use that, but I don't know what the 'nice' flag is good
for, either. I thought it is _just_ for linebreaking, so the question
whether \lyxlock should get written should not depend on that flag.
Here's a minimal solution from the preview end rather than the
mathed end. We currently generate a latex file for preview-latex by:
1 Dump LyX preamble.
2 Dump the math-macros
3 Add preview-latex magic
\begin{document}
4 Dump all previewable snippets.
\end{document}
A hack might be to redefine \lyxlock between 1 and 2 as an empty
wrapper. Care to suggest a bit of LaTeX that would do this?
\def\lyxlock{}
That can even go to the top of the file.
Alternatively, we could post-process the data passed to os by the
math insets before it is dumped to file to remove these lyxlocks.
That, however, sounds nastier.
Nah...
Andre'
--
Those who desire to give up Freedom in order to gain Security,
will not have, nor do they deserve, either one. (T. Jefferson)
bug: preview of includegraphics without extension broken
Hi, when I include a graphic in my LyX document I do not want to add the exetension of the filename. This is, because I want to be able to export the document to LaTeX and then be able to run either latex or pdflatex. For this I have to versions of my graphcis in my folder one is myGraphic.eps (for use with latex) and the other one is myGraphic.jpg or myGraphic.pdf (for use with pdflatex). I know LyX does the transformation of graphic formats automatically, but I'd enjoy if I could enter just the file name of the graphic without extension and then still be able to see the preview in LyX which does not work in this case yet. The advantage is that I could sent my document to somebody else using only latex not LyX (because he uses windows and doesn't like cygwin) and the reciever can decide whether to use latex or pdflatex. Best regards, Christian -- Christian Noack www.daedalos.com [EMAIL PROTECTED]
Re: [PATCH] Re: Link to preview-latex in NEWS file
Andre Poenitz wrote:
On Tue, Jan 21, 2003 at 02:12:42PM +, Angus Leeming wrote:
Is this your way of saying that the problem lies in mathed itself?
Ie, it would go away if we had control over the 'true' passed to
the WriteStream c-tor.
We could certainly use that, but I don't know what the 'nice' flag
is good for, either. I thought it is _just_ for linebreaking, so the
question whether \lyxlock should get written should not depend on
that flag.
Yes, you're right. I just made a wild guess at the problem when I
first read your description.
Here's a minimal solution from the preview end rather than the
mathed end. We currently generate a latex file for preview-latex
by:
1 Dump LyX preamble.
2 Dump the math-macros
3 Add preview-latex magic
\begin{document}
4 Dump all previewable snippets.
\end{document}
A hack might be to redefine \lyxlock between 1 and 2 as an empty
wrapper. Care to suggest a bit of LaTeX that would do this?
\def\lyxlock{}
That can even go to the top of the file.
Attached is the patch. It certainly fixes this problem:
Simply go into a 'a^b' inset and press C-I to lock it.
No fancy previews anymore...
Happy if I apply it? Guess that Lars should give his Ok too ;-)
--
Angus
Index: src/graphics/ChangeLog
===
RCS file: /usr/local/lyx/cvsroot/lyx-devel/src/graphics/ChangeLog,v
retrieving revision 1.138
diff -u -p -r1.138 ChangeLog
--- src/graphics/ChangeLog 13 Jan 2003 23:03:48 - 1.138
+++ src/graphics/ChangeLog 21 Jan 2003 14:26:26 -
@@ -1,3 +1,8 @@
+2003-01-21 Angus Leeming [EMAIL PROTECTED]
+
+ * PreviewLoader.C (dumpPreamble): ensure that \lyxlock does not prevent
+ previews from being generated.
+
2003-01-13 Angus Leeming [EMAIL PROTECTED]
* GraphicsCacheItem.C (findTargetFormat): define the default conversion
Index: src/graphics/PreviewLoader.C
===
RCS file: /usr/local/lyx/cvsroot/lyx-devel/src/graphics/PreviewLoader.C,v
retrieving revision 1.36
diff -u -p -r1.36 PreviewLoader.C
--- src/graphics/PreviewLoader.C 27 Nov 2002 10:30:25 - 1.36
+++ src/graphics/PreviewLoader.C 21 Jan 2003 14:26:27 -
@@ -562,6 +562,19 @@ void PreviewLoader::Impl::dumpPreamble(o
// Dump the preamble only.
tmp.makeLaTeXFile(os, buffer_.filePath(), true, false, true);
+ // FIXME! This is a HACK! The proper fix is to control the 'true'
+ // passed to WriteStream below:
+ // int InsetFormula::latex(Buffer const *, ostream os,
+ // bool fragile, bool) const
+ // {
+ // WriteStream wi(os, fragile, true);
+ // par_-write(wi);
+ // return wi.line();
+ // }
+ os \n
+ \\def\\lyxlock{}\n
+ \n;
+
// Loop over the insets in the buffer and dump all the math-macros.
Buffer::inset_iterator it = buffer_.inset_const_iterator_begin();
Buffer::inset_iterator end = buffer_.inset_const_iterator_end();
What is rpmbuild?
Make rpmdist now fails again on the latest CVS: /bin/sh /home/kayvan/src/lyx/config/missing --run tar chof - lyx-1.3.0pre2 | +GZIP=--best gzip -c lyx-1.3.0pre2.tar.gz chmod -R a+w lyx-1.3.0pre2 /dev/null 21; rm -rf lyx-1.3.0pre2 ln -s lib/images/lyx.xpm . ; \ rpmbuild -ta lyx-1.3.0pre2.tar.gz ; saved_status=$?; \ rm lyx.xpm; exit $saved_status /bin/sh: rpmbuild: command not found make: *** [rpmdist] Error 127 -- Kayvan A. Sylvan | Proud husband of | Father to my kids: Sylvan Associates, Inc. | Laura Isabella Sylvan | Katherine Yelena (8/8/89) http://sylvan.com/~kayvan | crown of her husband | Robin Gregory (2/28/92)
Re: footnotes preview in lyx-1.3
Angus Leeming wrote:
Moritz Moeller-Herrmann wrote:
I am now using lyx-1.3-pre2 for my dissertation and it looks great
so far. Is there any possibility to turn on preview-latex for the
footnotes? It seems to work in Emacs.
I don't see a problem. Attached is a screenshot. Works both when
typing a new equation and when loading an existing file.
The attached picture shows a formula in a footnote. I have never tried this,
because I am jurist.
I am talking about the possibility to preview the footnotemark. It is
mentioned in the preview-latex manual here:
http://preview-latex.sourceforge.net/manual/Package-options.html#Package%20options
This makes footnotes render as previews, and only as their footnote symbol.
A convenient editing feature inside of Emacs.
It seems as if you can set \usepackage[footnotes]{preview} in Emacs and have
a preview of the footnote mark.
Re: What is rpmbuild?
Kayvan A. Sylvan wrote: Make rpmdist now fails again on the latest CVS: /bin/sh /home/kayvan/src/lyx/config/missing --run tar chof - lyx-1.3.0pre2 | +GZIP=--best gzip -c lyx-1.3.0pre2.tar.gz chmod -R a+w lyx-1.3.0pre2 /dev/null 21; rm -rf lyx-1.3.0pre2 ln -s lib/images/lyx.xpm . ; \ rpmbuild -ta lyx-1.3.0pre2.tar.gz ; saved_status=$?; \ rm lyx.xpm; exit $saved_status /bin/sh: rpmbuild: command not found make: *** [rpmdist] Error 127 rpm has been split in 2 on RH8. rpm will install, update, query and rpmbuild will generate an rpm from the source files. So, I guess that there needs to be a test for the presence of rpmbuild somewhere. -- Angus
Re: Boost thinks that every C functions are in std::
Angus == Angus Leeming [EMAIL PROTECTED] writes:
Angus Jean-Marc Lasgouttes wrote:
It seems that I am really not able to compile 1.3.0cvs on tru64
unix with cxx. Reasons are:
- there is no snprintf in tru64 4.0f, so xforms has to provide its
own. the one provided in xforms lib does not compile on tru64, but
it does after a patch that I sent to the xforms list. So far, so
good.
Angus I'm surprised, as I too had to send a patch to get things to
Angus compile, but it was included in 1.0release. (I use 4.0e here).
I have to admit that I never saw the message arrive to the xforms
mailing list... Did I post it after all? I append the relevant patch
to this message. The problem is that I do not have isinf() here.
- LyX's configure script does not know that it has to use
-lformssnp on systems that do not have snprintf. I have a patch for
that. So far so good.
Angus That is because it uses the snprintf functions in src/support.
Angus It shouldn't matter whether these functions come from
Angus libformssnp.a (as they do when compiling one of the xforms demo
Angus programs) or from libsupport.a (as they do here when compiling
Angus LyX under 4.0e).
But how do we do the xforms autodetection in this case? Configure
tells me that it does not find xforms...
- boost really thinks that all C functions are in std:: and uses
std::fprintf and things like that all over the place. This is not
good at all with cxx and probably sun's CC. I am not sure what to
do about that.
Angus There is a cxx compilation flag, -nopure_cname, that the
Angus DEC/Compaq/HP support people told me to use. Here I configure
Angus LyX with:
This is only true for cxx 6.5 or whatever. I am stuck with 6.2 here.
JMarc
--- snprintf.c.orig Mon Jan 13 18:03:33 2003
+++ snprintf.c Mon Jan 13 18:04:53 2003
@@ -526,15 +526,15 @@
prec = DEFPREC;
fp_begin: _double = va_arg(ap, double);
/* do this before tricky precision changes */
- if (isinf(_double)) {
-if (_double 0)
- sign = '-';
-cp = Inf;
+ if (isnan(_double)) {
+cp = NaN;
size = 3;
break;
}
- if (isnan(_double)) {
-cp = NaN;
+ if (!finite(_double)) {
+if (_double 0)
+ sign = '-';
+cp = Inf;
size = 3;
break;
}
Re: footnotes preview in lyx-1.3
Moritz Moeller-Herrmann wrote:
Angus Leeming wrote:
Moritz Moeller-Herrmann wrote:
I am now using lyx-1.3-pre2 for my dissertation and it looks great
so far. Is there any possibility to turn on preview-latex for the
footnotes? It seems to work in Emacs.
I don't see a problem. Attached is a screenshot. Works both when
typing a new equation and when loading an existing file.
The attached picture shows a formula in a footnote. I have never
tried this, because I am jurist.
I am talking about the possibility to preview the footnotemark. It
is mentioned in the preview-latex manual here:
http://preview-latex.sourceforge.net/manual/Package-options.html#Package%20options
This makes footnotes render as previews, and only as their footnote
symbol. A convenient editing feature inside of Emacs.
It seems as if you can set \usepackage[footnotes]{preview} in Emacs
and have a preview of the footnote mark.
It would appear that you are coming up against a philosophical
impasse. David Kastrup thinks that previews are a good, good thing.
That may be because he uses emacs to write his LaTeX documents. He
/wants/ to see his LaTeX as code and he would also like to see
what the resulting compiled code results in.
The LyX project was set up to get you away from LaTeX code and give
you a reasonable on-screen representation of your document. Don't get
me wrong, I'm not knocking preview-latex. After all, I spent a large
chunk of my summer trying to get it to work in LyX. It's just that,
having done so, I'm not sure what /real/ benefit these previews
provide for most people.
We integrated preview-latex into LyX because it can sometimes
provide the user with useful information not otherwise available to
him. If LyX's math editor can rendor the equation, then the preview
is little more than eye candy. The real beneficiaries are those who
write things like commutative diagrams that mathed can't currently
render. Ditto, those who include LaTeX images in their document will
find this gizmo useful.
LyX uses a little box saying foot (possibly translated) to show a
footnote. Would you write better documents if LyX displayed some
symbol or other? I doubt it. Sure, we /could/ do it, at the cost of
complicating the code (read introduce more bugs). However, I suspect
that we'd rather spend out limited time in other ways.
On a more practical level, the only way to get this right is to make
LyX aware of the footnote symbols. If we were to show the symbol on
the footnote box, then using preview-latex is just a kludge.
Inserting a new footnote between existing ones will change the symbol
for all subsequent footnotes. It seems like a huge overkill to
regenerate all these images. Indded, what happens if you use a
footnote package that displayed footnotes as numbers starting from 1
on each new page? Should LyX know what text fits on which page? Of
course not. This is a can of worms that I will not open.
Just my opinions of course ;-)
--
Angus
Re: [PATCH] Re: Link to preview-latex in NEWS file
On Tue, Jan 21, 2003 at 02:44:52PM +, Angus Leeming wrote: Happy if I apply it? Yes. Guess that Lars should give his Ok too ;-) I suppose so. Andre' -- Those who desire to give up Freedom in order to gain Security, will not have, nor do they deserve, either one. (T. Jefferson)
Re: footnotes preview in lyx-1.3
On Tue, Jan 21, 2003 at 04:12:59PM +, Angus Leeming wrote: It's just that, having done so, I'm not sure what /real/ benefit these previews provide for most people. Welcome to the club ;-) Andre' -- Those who desire to give up Freedom in order to gain Security, will not have, nor do they deserve, either one. (T. Jefferson)
footnote numbering [was: Re: footnotes preview in lyx-1.3]
Angus Leeming wrote:
Moritz Moeller-Herrmann wrote:
It seems as if you can set \usepackage[footnotes]{preview} in Emacs
and have a preview of the footnote mark.
[...]
LyX uses a little box saying foot (possibly translated) to show a
footnote. Would you write better documents if LyX displayed some
symbol or other? I doubt it. Sure, we /could/ do it, at the cost of
complicating the code (read introduce more bugs). However, I suspect
that we'd rather spend out limited time in other ways.
If you had ever tried editing a document with more than 1000 footnotes all
of them labeled as [foot] in lyx, because lyx is unable to show the
footnote number, you would see why it is helpful to see the footnote mark.
On a more practical level, the only way to get this right is to make
LyX aware of the footnote symbols. If we were to show the symbol on
the footnote box, then using preview-latex is just a kludge.
Better a kludge, than nothing! I have wished for footnote numbering since
1999.
Inserting a new footnote between existing ones will change the symbol
for all subsequent footnotes. It seems like a huge overkill to
regenerate all these images. Indded, what happens if you use a
footnote package that displayed footnotes as numbers starting from 1
on each new page? Should LyX know what text fits on which page? Of
course not. This is a can of worms that I will not open.
In that case the footnote number is always useless information, which is why
noone uses footnote numbering by page in the real world. (I assume it was
useful for people with mechanical typewriters...)
I am sick of getting this argument against implementing a fscking simple
footnote counter in lyx. So after reading your very long answer, I can only
conclude, that lyx does not and will never have a useful implementation to
see the footnote number, either using preview-latex (kludge) or
otherwise.
I think this is disappointing, because lyx would be a lot more useful to the
sciences where footnotes are common (Humanities, Law), if it were possible
to see the footnote number.
How hard would it be to learn enough C++ and lyx to add this feature myself?
Re: footnote numbering [was: Re: footnotes preview in lyx-1.3]
On Tue, Jan 21, 2003 at 05:42:13PM +0100, Moritz Moeller-Herrmann wrote: How hard would it be to learn enough C++ and lyx to add this feature myself? Two months. Andre' -- Those who desire to give up Freedom in order to gain Security, will not have, nor do they deserve, either one. (T. Jefferson)
Re: footnote numbering [was: Re: footnotes preview in lyx-1.3]
Andre Poenitz wrote: On Tue, Jan 21, 2003 at 05:42:13PM +0100, Moritz Moeller-Herrmann wrote: How hard would it be to learn enough C++ and lyx to add this feature myself? Two months. How long would it take you and how much money would you (or anyone else on this list) want for it?
Re: [PATCH] Re: Link to preview-latex in NEWS file
Andre Poenitz [EMAIL PROTECTED] writes: | On Tue, Jan 21, 2003 at 02:44:52PM +, Angus Leeming wrote: | Happy if I apply it? | | Yes. | | Guess that Lars should give his Ok too ;-) | | I suppose so. Does it fix a real problem? If so, commit it. -- Lgb
Re: footnote numbering [was: Re: footnotes preview in lyx-1.3]
Moritz Moeller-Herrmann [EMAIL PROTECTED] writes: | LyX uses a little box saying foot (possibly translated) to show a | footnote. Would you write better documents if LyX displayed some | symbol or other? I doubt it. Sure, we /could/ do it, at the cost of | complicating the code (read introduce more bugs). However, I suspect | that we'd rather spend out limited time in other ways. | | If you had ever tried editing a document with more than 1000 footnotes all | of them labeled as [foot] in lyx, because lyx is unable to show the | footnote number, you would see why it is helpful to see the footnote mark. What would you like to see the footnote number or mark? What benefits does it give? | On a more practical level, the only way to get this right is to make | LyX aware of the footnote symbols. If we were to show the symbol on | the footnote box, then using preview-latex is just a kludge. | | Better a kludge, than nothing! I have wished for footnote numbering since | 1999. _why_? | I am sick of getting this argument against implementing a fscking simple | footnote counter in lyx. So after reading your very long answer, I can only | conclude, that lyx does not and will never have a useful implementation to | see the footnote number, either using preview-latex (kludge) or | otherwise. What are you goint to do with that number? Look at it? | I think this is disappointing, because lyx would be a lot more useful to the | sciences where footnotes are common (Humanities, Law), if it were possible | to see the footnote number. _why_? | How hard would it be to learn enough C++ and lyx to add this feature myself? Even if you learn enough C++, and that is not a lot you have to learn, it is questionable if this feature should be added. Seems to me that what you really want is footnote labels and to have the label name mentioned in the foot on screen. -- Lgb
Re: footnote numbering [was: Re: footnotes preview in lyx-1.3]
Moritz Moeller-Herrmann [EMAIL PROTECTED] writes: | Andre Poenitz wrote: | | On Tue, Jan 21, 2003 at 05:42:13PM +0100, Moritz Moeller-Herrmann wrote: | How hard would it be to learn enough C++ and lyx to add this feature | myself? | | Two months. | | How long would it take you and how much money would you | (or anyone else on this list) want for it? as said in another mail: I am not sure this is what you really want. -- Lgb
Re: footnote numbering [was: Re: footnotes preview in lyx-1.3]
On Tue, Jan 21, 2003 at 05:50:05PM +0100, Moritz Moeller-Herrmann wrote: How hard would it be to learn enough C++ and lyx to add this feature myself? Two months. How long would it take you Depends on the end of the feature freeze. Probably less than two months. and how much money would you (or anyone else on this list) want for it? Usually nothing. The project would need some beer in June, though ;-} Andre' -- Those who desire to give up Freedom in order to gain Security, will not have, nor do they deserve, either one. (T. Jefferson)
Re: [PATCH] Re: Link to preview-latex in NEWS file
On Tue, Jan 21, 2003 at 05:47:38PM +0100, Lars Gullik Bjønnes wrote: Does it fix a real problem? Yes. preview does not work without it if only a single formula is locked. [Looks like I am the only one using inset locking?] Andre' -- Those who desire to give up Freedom in order to gain Security, will not have, nor do they deserve, either one. (T. Jefferson)
Re: footnote numbering [was: Re: footnotes preview in lyx-1.3]
On Tue, Jan 21, 2003 at 05:51:16PM +0100, Lars Gullik Bjønnes wrote: | If you had ever tried editing a document with more than 1000 footnotes all | of them labeled as [foot] in lyx, because lyx is unable to show the | footnote number, you would see why it is helpful to see the footnote mark. What would you like to see the footnote number or mark? What benefits does it give? Actually I accept his argument that a sequential numbering of all footnotes might be some navigation help if the number of footnotes gets large. What are you goint to do with that number? Look at it? One can e.g. make the (sequential!) numbers appear in print as well. Going back from the proofs to the .lyx would be easy then. Andre' -- Those who desire to give up Freedom in order to gain Security, will not have, nor do they deserve, either one. (T. Jefferson)
Re: footnote numbering [was: Re: footnotes preview in lyx-1.3]
even if the number of footnotes is not overwhelming, going from paper corrections (can you change this in footnote 6) to the right place in lyx is a bit of a hassle... Ed.
Re: footnote numbering [was: Re: footnotes preview in lyx-1.3]
On Tuesday 21 January 2003 16:57, Andre Poenitz wrote: What would you like to see the footnote number or mark? What benefits does it give? Actually I accept his argument that a sequential numbering of all footnotes might be some navigation help if the number of footnotes gets large. What are you goint to do with that number? Look at it? One can e.g. make the (sequential!) numbers appear in print as well. Going back from the proofs to the .lyx would be easy then. Then this means that both the number and the name are useful. When writing is useful to read the name, when proofreading it is useful the number. Are the arguments like this? Andre' -- José Abílio
Re: footnote numbering [was: Re: footnotes preview in lyx-1.3]
Andre Poenitz wrote: On Tue, Jan 21, 2003 at 05:51:16PM +0100, Lars Gullik Bjønnes wrote: | If you had ever tried editing a document with more than 1000 footnotes | all of them labeled as [foot] in lyx, because lyx is unable to show | the footnote number, you would see why it is helpful to see the | footnote mark. What would you like to see the footnote number or mark? What benefits does it give? Actually I accept his argument that a sequential numbering of all footnotes might be some navigation help if the number of footnotes gets large. What are you goint to do with that number? Look at it? One can e.g. make the (sequential!) numbers appear in print as well. Going back from the proofs to the .lyx would be easy then. Yes, you understand me :-) This is especially true, if you get back corrected and annotated proofs from someone else. Then the footnote numbering (which does normally not change a lot) provides a very good navigation aid. ATM all I would have to use latex directly with src-specials and jump back between dvi and source to make correcting the proofs simpler, but I would prefer doing this in lyx.
Re: footnote numbering [was: Re: footnotes preview in lyx-1.3]
On Tue, 21 Jan 2003, Edwin Leuven wrote: even if the number of footnotes is not overwhelming, going from paper corrections (can you change this in footnote 6) to the right place in lyx is a bit of a hassle... One way to solve this problem is to implement inverse search http://bugzilla.lyx.org/show_bug.cgi?id=94 You open the document, then call the previewer, find footnote 6 then by inverse search, lyx finds the footnote. João.
Re: What is rpmbuild?
On Tue, Jan 21, 2003 at 03:14:39PM +, Angus Leeming wrote: rpm has been split in 2 on RH8. rpm will install, update, query and rpmbuild will generate an rpm from the source files. So, I guess that there needs to be a test for the presence of rpmbuild somewhere. How about this? It works for me. ---Kayvan -- Kayvan A. Sylvan | Proud husband of | Father to my kids: Sylvan Associates, Inc. | Laura Isabella Sylvan | Katherine Yelena (8/8/89) http://sylvan.com/~kayvan | crown of her husband | Robin Gregory (2/28/92) Index: Makefile.am === RCS file: /cvs/lyx/lyx-devel/Makefile.am,v retrieving revision 1.42 diff -u -u -r1.42 Makefile.am --- Makefile.am 2003/01/18 22:42:57 1.42 +++ Makefile.am 2003/01/21 17:13:37 @@ -29,7 +29,12 @@ rpmdist: dist ln -s lib/images/lyx.xpm . ; \ - rpmbuild -ta $(PACKAGE)-$(VERSION).tar.gz ; saved_status=$$?; \ + if [ -z `type -path rpmbuild` ]; \ + then \ + RPMBUILD=rpm; \ + else \ + RPMBUILD=rpmbuild; \ + fi; $$RPMBUILD -ta $(PACKAGE)-$(VERSION).tar.gz ; saved_status=$$?; \ rm lyx.xpm; exit $$saved_status bindist:
Re: footnote numbering [was: Re: footnotes preview in lyx-1.3]
José Matos wrote: On Tuesday 21 January 2003 16:57, Andre Poenitz wrote: What would you like to see the footnote number or mark? What benefits does it give? One can e.g. make the (sequential!) numbers appear in print as well. Going back from the proofs to the .lyx would be easy then. Then this means that both the number and the name are useful. When writing is useful to read the name, when proofreading it is useful the number. Are the arguments like this? The argument goes like this: Mr. Moeller-Herrmann, in footnote 477, your argument is wrong and you have to cite XYZ. At the moment I have to compile the lyx document, check the dvi, find footnote 477, look for and remember some significant text part, go back to lyx, search for the remembered text part, check back with the dvi document to see if I am at the correct position, then start typing. Now with footnote numbering, I would scroll down until I see footnote 477, start typing. Do you understand why it would be useful for me (and others)?
Re: footnote numbering [was: Re: footnotes preview in lyx-1.3]
Moritz Moeller-Herrmann wrote: I am sick of getting this argument against implementing a fscking simple footnote counter in lyx. So after reading your very long answer, I can only conclude, that lyx does not and will never have a useful implementation to see the footnote number, either using preview-latex (kludge) or otherwise. I've read the long stream of mails that my response generated. I think that it can be summarised as: * You would like some on-screen way to differentiate between different footnotes. * Lars thinks that you really need footnote labels. * André and myself both think that preview-latex is the wrong way to go about providing this information. The moral? Take an active interest in the 1.4 development cycle. Requests /are/ considered seriously. Often, they result in a vigorous discussion about the 'best' way forward. That can be frustrating when you feel your request is simple (been there), but experience shows we don't have the manpower to implement features poorly. We have to get them 'nearly right' first time. LyX already has counters internally. It uses them for things like Sections. The code was cleaned up enormously by Martin Vermeer in the 1.3 cycle, but he shied away from using them for the screen representation of things like Figure Floats. That's why they appear on screen as Figure '#'. He's done the majority of the work though, so it's not unreasonable to expect to see Figure 1, Table 2 in LyX 1.4. It would probably be trivially easy to have footnotes numbered too. Best regards, -- Angus
Re: Boost thinks that every C functions are in std::
Jean-Marc Lasgouttes wrote: Angus Jean-Marc Lasgouttes wrote: It seems that I am really not able to compile 1.3.0cvs on tru64 unix with cxx. Reasons are: - there is no snprintf in tru64 4.0f, so xforms has to provide its own. the one provided in xforms lib does not compile on tru64, but it does after a patch that I sent to the xforms list. So far, so good. Angus I'm surprised, as I too had to send a patch to get things to Angus compile, but it was included in 1.0release. (I use 4.0e here). I have to admit that I never saw the message arrive to the xforms mailing list... Did I post it after all? I have been feeling a little excluded too. I've sent a couple of mails (admittedly from a newly born box with minor setup problems) that seemed to vanish. I append the relevant patch to this message. The problem is that I do not have isinf() here. Nor, it would appear do I have it here... ld -o libformssnp.so~ -shared -no_archive -set_version 1.0 \ -soname libformssnp.so -all strtod.o snprintf.o \ -none -lc ld: Warning: Unresolved: isnan isinf isnan is to be found in libm.a. I can't find isinf anywhere. I have been able to link codes in the past that did not resolve a symbol. Trying to execute that statement leads to a run time error. I wonder if I would suffer such a fate here... - LyX's configure script does not know that it has to use -lformssnp on systems that do not have snprintf. I have a patch for that. So far so good. Angus That is because it uses the snprintf functions in src/support. Angus It shouldn't matter whether these functions come from Angus libformssnp.a (as they do when compiling one of the xforms demo Angus programs) or from libsupport.a (as they do here when compiling Angus LyX under 4.0e). But how do we do the xforms autodetection in this case? Configure tells me that it does not find xforms... Sorry, I don't understand. Are you talking about xforms' Imakefile stuff or LyX's configure stuff? LyX tests for the existence of snprintf in your system header files, can't find it and so decides to compile src/support/snprintf.c. It doesn't look for -lformssnp, not does it link it at the end. - boost really thinks that all C functions are in std:: and uses std::fprintf and things like that all over the place. This is not good at all with cxx and probably sun's CC. I am not sure what to do about that. Angus There is a cxx compilation flag, -nopure_cname, that the Angus DEC/Compaq/HP support people told me to use. Here I configure Angus LyX with: This is only true for cxx 6.5 or whatever. I am stuck with 6.2 here. 6.3 here. Reading the release notes, it would appear that you're right. nopure_cname appeared in 6.3. -- Angus
Re: [PATCH] Re: Link to preview-latex in NEWS file
On Tue, Jan 21, 2003 at 05:54:21PM +0100, Andre Poenitz wrote: [Looks like I am the only one using inset locking?] What is this ? john -- Anyone who quotes Rusty in their sig is an idiot. - me
Re: footnote numbering [was: Re: footnotes preview in lyx-1.3]
On Tuesday 21 January 2003 17:20, Moritz Moeller-Herrmann wrote: The argument goes like this: Mr. Moeller-Herrmann, in footnote 477, your argument is wrong and you have to cite XYZ. At the moment I have to compile the lyx document, check the dvi, find footnote 477, look for and remember some significant text part, go back to lyx, search for the remembered text part, check back with the dvi document to see if I am at the correct position, then start typing. Now with footnote numbering, I would scroll down until I see footnote 477, start typing. Then it would be easier to have the footnotes in navigate, or even better a function goto-footnote #n. Do you understand why it would be useful for me (and others)? It is easier to understand now. :-) -- José Abílio
Re: footnote numbering [was: Re: footnotes preview in lyx-1.3]
On Tue, Jan 21, 2003 at 06:20:09PM +0100, Moritz Moeller-Herrmann wrote:
[...]
Here we go. Very quickdirty and only barely functional (it takes a while
after an insertion until the change has propagated)
Moritz could apply this in hid local tree and remind us during the 1.4
cycle to discuss this issue again.
Andre'
--
Those who desire to give up Freedom in order to gain Security,
will not have, nor do they deserve, either one. (T. Jefferson)
Index: lib/layouts/stdcounters.inc
===
RCS file: /usr/local/lyx/cvsroot/lyx-devel/lib/layouts/stdcounters.inc,v
retrieving revision 1.1
diff -u -p -r1.1 stdcounters.inc
--- lib/layouts/stdcounters.inc 6 Sep 2002 14:47:58 - 1.1
+++ lib/layouts/stdcounters.inc 21 Jan 2003 17:53:36 -
@@ -71,3 +71,8 @@ End
Counter
Name algorithm
End
+
+Counter
+ Name footnote
+End
+
Index: src/text2.C
===
RCS file: /usr/local/lyx/cvsroot/lyx-devel/src/text2.C,v
retrieving revision 1.269
diff -u -p -r1.269 text2.C
--- src/text2.C 18 Dec 2002 14:36:28 - 1.269
+++ src/text2.C 21 Jan 2003 17:53:36 -
@@ -38,6 +38,7 @@
#include insets/insetbib.h
#include insets/insetspecialchar.h
#include insets/insettext.h
+#include insets/insetfoot.h
#include insets/insetfloat.h
#include insets/insetwrap.h
@@ -1170,7 +1171,6 @@ void LyXText::setCounter(Buffer const *
LyXLayout_ptr const layout = par-layout();
if (par-previous()) {
-
par-params().appendix(par-previous()-params().appendix());
if (!par-params().appendix() par-params().startOfAppendix()) {
par-params().appendix(true);
@@ -1358,6 +1358,16 @@ void LyXText::setCounter(Buffer const *
textclass.counters().reset(enumiii);
case 3:
textclass.counters().reset(enumiv);
+ }
+ }
+
+ // search for footnotes
+ for (lyx::pos_type pos = 0, n = par-size(); pos n; ++pos) {
+ Inset * inset = par-getInset(pos);
+ if (inset inset-lyxCode() == Inset::FOOT_CODE) {
+ textclass.counters().step(footnote);
+ static_castInsetFoot*(inset)
+ -number(textclass.counters().value(footnote));
}
}
}
Index: src/text3.C
===
RCS file: /usr/local/lyx/cvsroot/lyx-devel/src/text3.C,v
retrieving revision 1.29
diff -u -p -r1.29 text3.C
--- src/text3.C 17 Jan 2003 09:57:50 - 1.29
+++ src/text3.C 21 Jan 2003 17:53:36 -
@@ -1623,7 +1623,6 @@ Inset::RESULT LyXText::dispatch(FuncRequ
case LFUN_INSERT_NOTE:
case LFUN_INSET_ERT:
case LFUN_INSET_FLOAT:
- case LFUN_INSET_FOOTNOTE:
case LFUN_INSET_MARGINAL:
case LFUN_INSET_MINIPAGE:
case LFUN_INSET_OPTARG:
@@ -1633,6 +1632,11 @@ Inset::RESULT LyXText::dispatch(FuncRequ
// Open the inset, and move the current selection
// inside it.
doInsertInset(this, cmd, true, true);
+ break;
+
+ case LFUN_INSET_FOOTNOTE:
+ doInsertInset(this, cmd, true, true);
+ bv-text-updateCounters(bv);
break;
case LFUN_INSERT_URL:
Index: src/insets/insetfoot.C
===
RCS file: /usr/local/lyx/cvsroot/lyx-devel/src/insets/insetfoot.C,v
retrieving revision 1.50
diff -u -p -r1.50 insetfoot.C
--- src/insets/insetfoot.C 25 Sep 2002 14:26:10 - 1.50
+++ src/insets/insetfoot.C 21 Jan 2003 17:53:36 -
@@ -28,23 +28,24 @@
#include lyxlayout.h
#include buffer.h
#include paragraph.h
+#include Lsstream.h
using std::ostream;
InsetFoot::InsetFoot(BufferParams const bp)
- : InsetFootlike(bp)
+ : InsetFootlike(bp), number_(0)
{
- setLabel(_(foot));
+ relabel();
setInsetName(Foot);
}
InsetFoot::InsetFoot(InsetFoot const in, bool same_id)
- : InsetFootlike(in, same_id)
+ : InsetFootlike(in, same_id), number_(0)
{
- setLabel(_(foot));
+ relabel();
setInsetName(Foot);
}
@@ -83,6 +84,20 @@ int InsetFoot::docbook(Buffer const * bu
os footnote;
int const i = inset.docbook(buf, os, mixcont);
os /footnote;
-
return i;
+}
+
+
+void InsetFoot::relabel()
+{
+ ostringstream os;
+ os _(foot) : number_;
+ setLabel(os.str());
+}
+
+
+void InsetFoot::number(int n)
+{
+ number_ = n;
+ relabel();
}
Index: src/insets/insetfoot.h
===
RCS file: /usr/local/lyx/cvsroot/lyx-devel/src/insets/insetfoot.h,v
retrieving revision 1.34
diff -u -p -r1.34 insetfoot.h
---
Re: [PATCH] Re: Link to preview-latex in NEWS file
On Tue, Jan 21, 2003 at 05:56:12PM +, John Levon wrote: [Looks like I am the only one using inset locking?] What is this ? If you press C-i inset a mathinset, it gets locked and Cursor Left/Right jumps over it with a single keystroke. To unlock, press C-i again. Up/Down isn't affected. Andre' -- Those who desire to give up Freedom in order to gain Security, will not have, nor do they deserve, either one. (T. Jefferson)
[PATCH] lyx2lyx helper
This patch:
* updates the version of lyx2lyx to match the corresponing lyx version;
* updates the reference to the copyright date.
* adds two new options to list the supported lyx versions, and allow to
specify it instead of the final file format.
* if both the file format and lyx version are given for the resulting file it
aborts as they are mutually exclusive.
The purpose of this patch is to make lyx2lyx more user friendly and to
simplify its usage for normal users who wnat to use it for older version of
lyx.
Comments?
--
José Abílio
? patch-lyx2lyx
Index: lyx2lyx
===
RCS file: /usr/local/lyx/cvsroot/lyx-devel/lib/lyx2lyx/lyx2lyx,v
retrieving revision 1.5
diff -u -p -r1.5 lyx2lyx
--- lyx2lyx 7 Jan 2003 17:03:59 - 1.5
+++ lyx2lyx 21 Jan 2003 18:17:46 -
@@ -1,5 +1,5 @@
#! /usr/bin/env python
-# Copyright (C) 2002 José Matos [EMAIL PROTECTED]
+# Copyright (C) 2002-2003 José Matos [EMAIL PROTECTED]
#
# This program is free software; you can redistribute it and/or
# modify it under the terms of the GNU General Public License
@@ -19,7 +19,7 @@ import getopt, sys, string, re
from error import error, warning
from parser_tools import set_comment, set_format, check_token
-version = 0.0.2
+version = 1.3.0
# Allow the dummy object to be able to carry related data
# like a C struct
@@ -37,7 +37,13 @@ opt.quiet = 0
format = re.compile(r(\d)[\.,]?(\d\d))
fileformat = re.compile(r\\lyxformat\s*(\S*))
-lst_ft = [210, 215, 216, 217, 218, 220, 221]
+
+lyx_version = {0.12:215, 1.0.0:215, 1.0.1: 215, 1.0.2:215,
+ 1.0.3:215, 1.0.4:215, 1.1.2:215, 1.1.4:215,
+ 1.1.5:216, 1.1.5fix1:216, 1.1.5fix2:216,
+ 1.1.6:217, 1.1.6fix1:217, 1.1.6fix2:217,
+ 1.1.6fix3:218, 1.1.6fix4:218,1.2.0:220,
+ 1.2.1:220, 1.2.2:220, 1.2.3:220,1.3.0:221}
def usage():
print Usage: lyx2lyx [options] file1
@@ -45,44 +51,70 @@ Convert old lyx file file1 to newer fo
Options:
-h, --help this information
-v, --version output version information and exit
--l, --list list all available formats
+-l, --list list all available file formats
+-m, --list-versions list all lyx versions supported
-d, --debug level level=0..2 (O_ no debug information,2_verbose)
default: level=1
--f, --from version initial version (optional)
--t, --to version final version (optional)
+-f, --from version initial version
+-t, --to version final lyx file format version
+-n, --final-version version final lyx version
-o, --output name name of the output file or else goes to stdout
-q, --quiet same as --debug=0
def parse_options(argv):
-_options = [help, version, list, from=, to=, output=, quiet]
+_options = [help, version, list, list-versions, from=, to=, output=, final-version=, quiet]
try:
- opts, args = getopt.getopt(argv[1:], f:hlo:qt:v, _options)
+ opts, args = getopt.getopt(argv[1:], f:hlmn:o:qt:v, _options)
except getopt.error:
usage()
sys.exit(2)
+output_option = 0
+
for o, a in opts:
if o in (-h, --help):
usage()
sys.exit()
if o in (-v, --version):
print lyxconvert, version %s %(version)
-print Copyright (C) 2002 LyX Team
+print Copyright (C) 2002-2003 LyX Team
sys.exit()
if o in (-d, --debug):
opt.debug = int(a)
if o in (-q, --quiet):
opt.debug = 0
if o in (-l, --list):
-print lst_ft
+lst = lyx_version.values()
+lst.sort()
+#determine unique representation
+value = None
+for item in lst:
+if item != value:
+value = item
+print value,
+print
+sys.exit()
+if o in (-m, --list-versions):
+lyx_versions = lyx_version.keys()
+lyx_versions.sort()
+print lyx_versions
sys.exit()
if o in (-o, --output):
opt.output = open(a, w)
if o in (-f, --from):
opt.start = lyxformat(a)
if o in (-t, --to):
+output_option = output_option + 1
opt.end = lyxformat(a)
+if o in (-n,--final-version):
+output_option = output_option + 1
+opt.end = lyxversion[a]
+
+if output_option == 2:
+sys.stderr.write(Final output format and final LyX version are mutually exclusive, provide only one of them.\n)
+usage()
+sys.exit(2)
if not opt.end:
opt.end = lst_ft[len(lst_ft)-1]
Re: lyx 1.3pre2 does not display oe and euro symbol
On Tue, Jan 21, 2003 at 04:18:16PM +0100, Nabil Hathout wrote: my $LANG is set to fr_FR@euro. Its is the only available value defined in /etc/locale.gen : fr_FR@euro ISO-8859-15 What should be the $LANG value that would make lyx choose the iso8859-15 encoding ? Press control-x please, then see if you can type a euro into the minibuffer. This bit works for me. I have a problem entering euros - if the language encoding is set in the document to latin9, I *still* get back encoding ISO 8859-1 from the lyxfont ! Can somebody explain this please, I'm lost here. Without this, we cannot work properly. regards john -- When you start off by telling those who disagree with you that they are not merely in error but in sin, how much of a dialogue do you expect ? - Thomas Sowell
Re: [PATCH] lyx2lyx helper
On Tuesday 21 January 2003 18:35, José Matos wrote:
This patch:
* updates the version of lyx2lyx to match the corresponing lyx version;
* updates the reference to the copyright date.
* adds two new options to list the supported lyx versions, and allow to
specify it instead of the final file format.
* if both the file format and lyx version are given for the resulting file
it aborts as they are mutually exclusive.
The purpose of this patch is to make lyx2lyx more user friendly and to
simplify its usage for normal users who wnat to use it for older version of
lyx.
Errr ignore the last patch, this one is the real. :-)
Comments?
--
José Abílio
? patch-lyx2lyx
Index: lyx2lyx
===
RCS file: /usr/local/lyx/cvsroot/lyx-devel/lib/lyx2lyx/lyx2lyx,v
retrieving revision 1.5
diff -u -p -r1.5 lyx2lyx
--- lyx2lyx 7 Jan 2003 17:03:59 - 1.5
+++ lyx2lyx 21 Jan 2003 18:56:19 -
@@ -1,5 +1,5 @@
#! /usr/bin/env python
-# Copyright (C) 2002 José Matos [EMAIL PROTECTED]
+# Copyright (C) 2002-2003 José Matos [EMAIL PROTECTED]
#
# This program is free software; you can redistribute it and/or
# modify it under the terms of the GNU General Public License
@@ -19,7 +19,7 @@ import getopt, sys, string, re
from error import error, warning
from parser_tools import set_comment, set_format, check_token
-version = 0.0.2
+version = 1.3.0
# Allow the dummy object to be able to carry related data
# like a C struct
@@ -37,7 +37,22 @@ opt.quiet = 0
format = re.compile(r(\d)[\.,]?(\d\d))
fileformat = re.compile(r\\lyxformat\s*(\S*))
-lst_ft = [210, 215, 216, 217, 218, 220, 221]
+
+lyx_version = {0.12:215, 1.0.0:215, 1.0.1: 215, 1.0.2:215,
+ 1.0.3:215, 1.0.4:215, 1.1.2:215, 1.1.4:215,
+ 1.1.5:216, 1.1.5fix1:216, 1.1.5fix2:216,
+ 1.1.6:217, 1.1.6fix1:217, 1.1.6fix2:217,
+ 1.1.6fix3:218, 1.1.6fix4:218,1.2.0:220,
+ 1.2.1:220, 1.2.2:220, 1.2.3:220,1.3.0:221}
+lst_ft = []
+lst = lyx_version.values()
+lst.sort()
+#determine unique representation
+value = None
+for item in lst:
+if item != value:
+value = item
+lst_ft.append(value)
def usage():
print Usage: lyx2lyx [options] file1
@@ -45,30 +60,34 @@ Convert old lyx file file1 to newer fo
Options:
-h, --help this information
-v, --version output version information and exit
--l, --list list all available formats
+-l, --list list all available file formats
+-m, --list-versions list all lyx versions supported
-d, --debug level level=0..2 (O_ no debug information,2_verbose)
default: level=1
--f, --from version initial version (optional)
--t, --to version final version (optional)
+-f, --from version initial version
+-t, --to version final lyx file format version
+-n, --final-version version final lyx version
-o, --output name name of the output file or else goes to stdout
-q, --quiet same as --debug=0
def parse_options(argv):
-_options = [help, version, list, from=, to=, output=, quiet]
+_options = [help, version, list, list-versions, from=, to=, output=, final-version=, quiet]
try:
- opts, args = getopt.getopt(argv[1:], f:hlo:qt:v, _options)
+ opts, args = getopt.getopt(argv[1:], f:hlmn:o:qt:v, _options)
except getopt.error:
usage()
sys.exit(2)
+output_option = 0
+
for o, a in opts:
if o in (-h, --help):
usage()
sys.exit()
if o in (-v, --version):
print lyxconvert, version %s %(version)
-print Copyright (C) 2002 LyX Team
+print Copyright (C) 2002-2003 LyX Team
sys.exit()
if o in (-d, --debug):
opt.debug = int(a)
@@ -77,12 +96,26 @@ def parse_options(argv):
if o in (-l, --list):
print lst_ft
sys.exit()
+if o in (-m, --list-versions):
+lyx_versions = lyx_version.keys()
+lyx_versions.sort()
+print lyx_versions
+sys.exit()
if o in (-o, --output):
opt.output = open(a, w)
if o in (-f, --from):
opt.start = lyxformat(a)
if o in (-t, --to):
+output_option = output_option + 1
opt.end = lyxformat(a)
+if o in (-n,--final-version):
+output_option = output_option + 1
+opt.end = lyxversion[a]
+
+if output_option == 2:
+sys.stderr.write(Final output format and final LyX version are mutually exclusive, provide only one of them.\n)
+usage()
+sys.exit(2)
if not opt.end:
opt.end = lst_ft[len(lst_ft)-1]
Re: very small Pb in lyx-1.3pre2 build
On Wed, Jan 15, 2003 at 02:25:33PM +0100, Roger Gadiou wrote: I have build lyx-1.3pre2 with qt frontend on my mandrake distribution. the only pb was the version of autoconf which is 2.52d. So the place for a letter should be added to the $autoversion test in autogen.sh file: case $autoversion in *2.13) ... *2.5[2346][d]) ... I don't know if other letters have to be added. Lars ? regards john -- When you start off by telling those who disagree with you that they are not merely in error but in sin, how much of a dialogue do you expect ? - Thomas Sowell
Re: footnote numbering [was: Re: footnotes preview in lyx-1.3]
Angus Leeming wrote: Moritz Moeller-Herrmann wrote: * You would like some on-screen way to differentiate between different footnotes. Correct. * Lars thinks that you really need footnote labels. False. I do not need these labels. * André and myself both think that preview-latex is the wrong way to go about providing this information. That might be. I thought it might be easier than a lyx native solution with the counters, if the work is already done in preview.sty. The moral? Take an active interest in the 1.4 development cycle. I have watched lyx development since before 1.0. The request for footnote counters has been made several times by me. I also put it into a bugzilla wish, where it was closed as invalid, IIRC. [...] LyX already has counters internally. It uses them for things like Sections. The code was cleaned up enormously by Martin Vermeer in the 1.3 cycle, but he shied away from using them for the screen representation of things like Figure Floats. That's why they appear on screen as Figure '#'. He's done the majority of the work though, so it's not unreasonable to expect to see Figure 1, Table 2 in LyX 1.4. It would probably be trivially easy to have footnotes numbered too. I look forward to 1.4 then. Thanks for your hard work on lyx and your replies.
Re: footnote numbering [was: Re: footnotes preview in lyx-1.3]
On Tue, Jan 21, 2003 at 09:49:44PM +0100, Moritz Moeller-Herrmann wrote: I will :-) I have also created bug number 838 and added your patch as attachment. This is now bug 409 as it was a dupe (as you know ...) regards john -- When you start off by telling those who disagree with you that they are not merely in error but in sin, how much of a dialogue do you expect ? - Thomas Sowell
bugzilla banner
it's coming up as a broken img now ... john -- When you start off by telling those who disagree with you that they are not merely in error but in sin, how much of a dialogue do you expect ? - Thomas Sowell
Re: footnote numbering [was: Re: footnotes preview in lyx-1.3]
On Tue, Jan 21, 2003 at 06:11:59PM +0100, Edwin Leuven wrote: even if the number of footnotes is not overwhelming, going from paper corrections (can you change this in footnote 6) to the right place in lyx is a bit of a hassle... It occurs to me that in the cases where footnote numbering would be useful, numbering the footnotes that exist on loading the document would be sufficient--these are the only ones that can already be on paper or in someone else's hands . . . in fact, it would seem to be more useful *not* to update numbering after opening the document . . . hawk -- Richard E. Hawkins, Asst. Prof. of Economics/\ ASCII ribbon campaign [EMAIL PROTECTED] Smeal 178 (814) 375-4700 \ / against HTML mail These opinions will not be those of Xand postings. Penn State until it pays my retainer. / \
Re: footnote numbering [was: Re: footnotes preview in lyx-1.3]
John Levon wrote: This is now bug 409 as it was a dupe (as you know ...) Sorry, I searched for footnote and footnotes and did not find my old bug, nor did I get sent the additional responses.
Re: footnote numbering [was: Re: footnotes preview in lyx-1.3]
On Tue, Jan 21, 2003 at 10:15:52PM +0100, Moritz Moeller-Herrmann wrote: This is now bug 409 as it was a dupe (as you know ...) Sorry, I searched for footnote and footnotes and did not find my old bug, You need to change the default search setting to include closed bugs too, it's quite obscure alas. Forgiven ;) nor did I get sent the additional responses. Hmm, temporary problem perhaps... regards john -- When you start off by telling those who disagree with you that they are not merely in error but in sin, how much of a dialogue do you expect ? - Thomas Sowell
Re: lyx 1.3pre2 does not display oe and euro symbol
John Levon writes: On Tue, Jan 21, 2003 at 04:18:16PM +0100, Nabil Hathout wrote: my $LANG is set to fr_FR@euro. Its is the only available value defined in /etc/locale.gen : fr_FR@euro ISO-8859-15 What should be the $LANG value that would make lyx choose the iso8859-15 encoding ? Press control-x please, then see if you can type a euro into the minibuffer. This bit works for me. It works too for me. --Nabil
lyx 1.3pre2 does not display oe and euro symbol
In fact, the problem exists only with the Qt front-end. It seems (-dbg 512) that the font encoding is guessed from the language value and that the ones associated with Français are either iso8859-1 and iso10646-1. I have added the relevant encoding variables in the preferences but it seems they are not used. regards, --Nabil Nabil Hathout writes: Hello, I would like to switch to lyx 1.3pre2 but it does not allow me to type oe (AltGr + S + g) and euro (AltGr + e) symbols. This was possible in lyx 1.2.X. How could I do so ? Is the answer in the documentation ? regards, --Nabil Hathout
Re: lyx 1.3pre2 does not display oe and euro symbol
On Tue, Jan 21, 2003 at 03:14:37PM +0100, Nabil Hathout wrote: In fact, the problem exists only with the Qt front-end. It seems (-dbg 512) that the font encoding is guessed from the language value and that the ones associated with Français are either iso8859-1 and iso10646-1. I have added the relevant encoding variables in the preferences but it seems they are not used. This will not affect your ability to *enter* the symbols. This is completely outside of our control. Try fiddling with your $LANG setting. regards john -- Anyone who quotes Rusty in their sig is an idiot. - me
Re: lyx 1.3pre2 does not display oe and euro symbol
John Levon writes: On Tue, Jan 21, 2003 at 03:14:37PM +0100, Nabil Hathout wrote: In fact, the problem exists only with the Qt front-end. It seems (-dbg 512) that the font encoding is guessed from the language value and that the ones associated with Français are either iso8859-1 and iso10646-1. I have added the relevant encoding variables in the preferences but it seems they are not used. This will not affect your ability to *enter* the symbols. This is completely outside of our control. Try fiddling with your $LANG setting. my $LANG is set to fr_FR@euro. Its is the only available value defined in /etc/locale.gen : fr_FR@euro ISO-8859-15 What should be the $LANG value that would make lyx choose the iso8859-15 encoding ? --Nabil
Re: Prerelease #2 of LyX 1.3.0
I'm trying to compile it on ibm power4/aix5.1 (with xforms-1.0), using gcc3.2. It fails with: g++ -g -O -fno-exceptions -W -Wall -o lyx BufferView.o BufferView_pimpl.o Bullet.o Chktex.o CutAndPaste.o DepTable.o FloatList.o Floating.o FuncStatus.o InsetList.o LColor.o LaTeX.o LaTeXFeatures.o LyXAction.o MenuBackend.o paragraph_funcs.o ParagraphList.o ParagraphParameters.o Spacing.o TextCache.o Thesaurus.o ToolbarDefaults.o boost.o boost-inst.o box.o buffer.o bufferlist.o bufferparams.o bufferview_funcs.o chset.o converter.o counters.o debug.o encoding.o exporter.o gettext.o factory.o funcrequest.o importer.o intl.o iterators.o kbmap.o kbsequence.o language.o lastfiles.o lengthcommon.o lyx_cb.o lyx_main.o lyx_sty.o lyxcursor.o lyxfont.o lyxfind.o lyxfunc.o lyxgluelength.o lyxlayout.o lyxlength.o lyxlex.o lyxlex_pimpl.o lyxrc.o lyxrow.o lyxserver.o lyxtextclass.o lyxtextclasslist.o lyxvc.o main.o paragraph.o paragraph_pimpl.o ispell.o pspell.o sgml.o tabular.o tabular-old.o tabular_funcs.o tex-accent.o tex-strings.o texrow.o text.o text2.o text3.o toc.o trans.o trans_mgr.o undo.o undo_funcs.o vc-backend.o version.o vspace.o mathed/.libs/libmathed.a insets/.libs/libinsets.a frontends/.libs/libfrontends.a -lflimage -ljpeg -lforms -lXpm graphics/.libs/libgraphics.a support/.libs/libsupport.a ../boost/libs/regex/src/.libs/libboostregex.a ../boost/libs/signals/src/.libs/libboostsignals.a -L/opt/freeware/lib -lintl -L/usr/local/lib -liconv -lSM -lICE -lc -lm -lX11 -Wl,-bnolibpath -Wl,-blibpath:/opt/freeware/lib:/usr/local/lib:/usr/lib:/lib ld: 0711-317 ERROR: Undefined symbol: typeinfo name for UpdatableInset ld: 0711-317 ERROR: Undefined symbol: typeinfo name for Inset ld: 0711-317 ERROR: Undefined symbol: typeinfo for ControlDialogBI ld: 0711-317 ERROR: Undefined symbol: typeinfo for ControlDialogControlConnectBI ld: 0711-317 ERROR: Undefined symbol: typeinfo for ControlDialogBD ld: 0711-317 ERROR: Undefined symbol: typeinfo for ControlDialogControlConnectBD ld: 0711-317 ERROR: Undefined symbol: ControlDialogControlConnectBD::hide() ld: 0711-317 ERROR: Undefined symbol: ControlDialogControlConnectBD::update() ld: 0711-317 ERROR: Undefined symbol: ControlDialogControlConnectBD::show() ld: 0711-317 ERROR: Undefined symbol: typeinfo name for InsetCollapsable ld: 0711-317 ERROR: Undefined symbol: typeinfo name for InsetNote ld: 0711-317 ERROR: Undefined symbol: typeinfo name for InsetFootlike ld: 0711-317 ERROR: Undefined symbol: typeinfo name for InsetMarginal ld: 0711-317 ERROR: Undefined symbol: typeinfo name for MathInset ld: 0711-317 ERROR: Undefined symbol: typeinfo name for MathDimInset ld: 0711-317 ERROR: Undefined symbol: typeinfo name for MathNestInset ld: 0711-317 ERROR: Undefined symbol: typeinfo name for MathSqrtInset ld: 0711-317 ERROR: Undefined symbol: typeinfo name for MathFracbaseInset ld: 0711-317 ERROR: Undefined symbol: typeinfo name for MathFracInset ld: 0711-317 ERROR: Undefined symbol: ControlDialogControlConnectBI::hide() ld: 0711-317 ERROR: Undefined symbol: ControlDialogControlConnectBI::update() ld: 0711-317 ERROR: Undefined symbol: ControlDialogControlConnectBI::show() ld: 0711-317 ERROR: Undefined symbol: typeinfo name for CheckedGlueLength ld: 0711-317 ERROR: Undefined symbol: typeinfo name for CheckedLyXLength ld: 0711-317 ERROR: Undefined symbol: typeinfo name for ControlPrefs ld: 0711-317 ERROR: Undefined symbol: typeinfo name for ControlPrint ld: 0711-317 ERROR: Undefined symbol: typeinfo name for FormPrint ld: 0711-317 ERROR: Undefined symbol: typeinfo for FormCBControlPrint, FormDBFD_print ld: 0711-317 ERROR: Undefined symbol: typeinfo for FormDBFD_print ld: 0711-317 ERROR: Undefined symbol: typeinfo name for FormTabular ld: 0711-317 ERROR: Undefined symbol: typeinfo for FormCBControlTabular, FormDBFD_tabular ld: 0711-317 ERROR: Undefined symbol: typeinfo for FormDBFD_tabular Any hint ? Lars Gullik Bjønnes wrote: I have just uploaded the tarball and the rpms to ftp.devel.lyx.org. A lot of small fixes has been applied since (the unannounced) first prerelease. Even if I am not aware of any serious problems with pre2, you should be careful to backup your documents before trying this one out. The rpms are created against the xforms rpms that can be found in the same dir as the prerelease. Reports on installation and running this will be greately appreciated. Be it failure or success reports... ftp://ftp.devel.lyx.org/pub/lyx/pre/lyx-1.3.0pre2.tar.gz ftp://ftp.devel.lyx.org/pub/lyx/pre/lyx-1.3.0pre2-1.i386.rpm ftp://ftp.devel.lyx.org/pub/lyx/pre/lyx-1.3.0pre2-1.src.rpm -- Lgb -- Nicolas FERRE' (PhD) phone/fax : +39-0577-234278 Dipartimento di Chimica Universita` di Siena mailto:[EMAIL PROTECTED] via Aldo Moro 53100 SIENA (Italia) http://ccmaol1.chim.unisi.it/
Re: XForms 1.0 and LyX 1.2.3 RPMs and SRPMs for Red Hat Linux 7.3 and 8.0
> "Daniel" == Daniel Tschan <[EMAIL PROTECTED]> writes: Daniel> Hi JMarc >> I have taken your binaries and put them on >> ftp.lyx.org/pub/lyx/bin/1.2.3. I hope they will work fine with the >> xforms rpm we have at ftp.lyx.org/pub/lyx/contrib :) Daniel> Great. It looks like they work with all xforms rpms in the Daniel> contrib directory, 0.88, 0.89 and 1.0. That would be very strange, since 0.88 is not binary compatible with 1.0 (for example, it has no image library). But it may be that 0.89 and 1.0 are imilar enough. Anyway, people, please use 1.0 instead. JMarc
Re: Link to preview-latex in NEWS file
On Tue, Jan 21, 2003 at 09:48:30AM +0100, Michael Schmitt wrote: > I think we should provide a link to the preview-latex homepage in the > NEWS file. Ok. > I also wonder whether we should activate preview-latex by default No. There are still rough edges (display jumping) and there are conceptual problems (fancy preambles) that make this wonderful feature unusable under some circumstances. It certainly should not default to on. > and how we draw the user's attention to this wonderful feature. I guess > many users will not use it simply because they don't know it (of course, > the same applies for aiksaurus, pspell, and checktex). Maybe we should > add a section to "About LyX">"Version" concerning available/missing > third-party libraries? Like putting in configure output? Andre' -- Those who desire to give up Freedom in order to gain Security, will not have, nor do they deserve, either one. (T. Jefferson)
Re: [patch] relyx
[EMAIL PROTECTED] (Lars Gullik Bjønnes) writes:
| [EMAIL PROTECTED] (Lars Gullik Bjønnes) writes:
|
| | Can some of you relyx people have a look at case 638 and see if this
| | patch has any relevance?
| |
| | It kindo seems that it fixes things, but I won't apply anything until
| | I have confirmations.
This patch became a bit larger than intended, due to ws changes.
This is the cut down version.
| @@ -1400,7 +1400,8 @@ sub ConvertToLayout {
| print "\nChanging $dummy $name to layout $layout" if $debug_on;
|
| # Nest if the layout stack has more than just "Standard" in it
| -if ($#{$CurrentLayoutStack} > 0) {
| +if ($#{$CurrentLayoutStack} > 0
| + && $CurrentLayoutStack =~ /^$ListLayouts$/o) {
| # Die here for sections & things that can't be nested!
| print " Nesting!" if $debug_on;
| print OUTFILE "\n\\begin_deeper ";
| @@ -1474,7 +1475,8 @@ sub EndLayout {
| # \end_deeper \begin_deeper in the LyX file. It's sloppy
| # but it works, and LyX will get rid of it when it
| # resaves the file.
| -if ($#{$CurrentLayoutStack} > 0) {
| +if ($#{$CurrentLayoutStack} > 0
| + && $CurrentLayoutStack =~ /^$ListLayouts$/o) {
| print " End Nesting!" if $debug_on;
| print OUTFILE "\n\\end_deeper ";
| }
--
Lgb
[PATCH] Re: Link to preview-latex in NEWS file
Andre Poenitz wrote: On Tue, Jan 21, 2003 at 09:48:30AM +0100, Michael Schmitt wrote: I think we should provide a link to the preview-latex homepage in the NEWS file. Ok. See attachment for patch. I also wonder whether we should activate preview-latex by default No. There are still rough edges (display jumping) and there are conceptual problems (fancy preambles) that make this wonderful feature unusable under some circumstances. It certainly should not default to on. I know the first problem and I would be happy to see a fix for it. But what is the second problem (fancy preambles)? BTW: Has anybody tested the new version 0.7.8? They have changed the handling of color.sty. Maybe this is related to the problem mentioned above or the LyX color handling. nd how we draw the user's attention to this wonderful feature. I guess many users will not use it simply because they don't know it (of course, the same applies for aiksaurus, pspell, and checktex). Maybe we should add a section to "About LyX">"Version" concerning available/missing third-party libraries? Like putting in configure output? Yes, I guess so. Unfortunately, I don't have enough knowledge to provide a patch for it. Michael -- === Michael Schmitt Telefon: +49 651 97551-40 Institut für TelematikTelefax: +49 651 97551-12 Bahnhofstrasse 30-32 WWW: http://www.ti.fhg.de D-54292 Trier E-Mail: mailto:[EMAIL PROTECTED] === Index: NEWS === RCS file: /cvs/lyx/lyx-devel/NEWS,v retrieving revision 1.48 diff -u -r1.48 NEWS --- NEWS2003/01/17 13:50:09 1.48 +++ NEWS2003/01/21 09:20:15 @@ -49,9 +49,10 @@ ** Instant preview -preview-latex is an emacs package for LaTeX that allows "instant -previews" of LaTeX code, so you can immediately see the visual -rendering of the LaTeX in the document. With the help of David +preview-latex is an emacs package for LaTeX that allows "instant previews" +of LaTeX code, so you can immediately see the visual rendering of the +LaTeX in the document. Its project home page can be found at +http://sourceforge.net/projects/preview-latex. With the help of David Kastrup, the author, current CVS LyX can harness this functionality to allow instant previews in the LyX window of math equations and figures. This feature can be immensely useful for making sure the
Re: [PATCH] Re: Link to preview-latex in NEWS file
On Tue, Jan 21, 2003 at 10:12:28AM +0100, Michael Schmitt wrote:
> >No. There are still rough edges (display jumping) and there are
> >conceptual problems (fancy preambles) that make this wonderful feature
> >unusable under some circumstances. It certainly should not default to on.
>
> I know the first problem and I would be happy to see a fix for it. But
> what is the second problem (fancy preambles)?
It's rather "Fancy ERT not in preambles".
Preamble:
\def\foo{\bar}
Later ERT:
\def\foo{\urgs}
Math:
\foo
There is another one: Currently, \lyxlock gets written to the .tex
snippets. This indicates that preview uses the "write to .lyx" method
instead of "write to .tex" (I think this is a boolean flag somewhere,
haven't looked at it, though)
> Yes, I guess so. Unfortunately, I don't have enough knowledge to provide
> a patch for it.
The ERT problem is unsolvable.
Andre'
--
Those who desire to give up Freedom in order to gain Security,
will not have, nor do they deserve, either one. (T. Jefferson)
Re: CJK-LyX-1.2.3
On 20 Jan 2003, Jean-Marc Lasgouttes wrote: > > That's OK woth me. I was just pointing out that, if you want to have a > release of xforms you can rely on, it would be nice to try to propose > something right now... > > JMarc > With your encouragement(?), I've changed my mind and will send the patch to the xforms mailing list. Attached is the patch(xforms-1.0-xim.patch). I've also attached CJK-LyX patch (CJK-LyX-1.3.0pre2-patch) to this email for test. The patch is against lyx-1.3.0pre2. Feedbacks are welcome, especially from the Japanese and Chinese input users. Regards, cghan
Re: [PATCH] Re: Link to preview-latex in NEWS file
Andre Poenitz wrote: Yes, I guess so. Unfortunately, I don't have enough knowledge to provide a patch for it The ERT problem is unsolvable. :-) I didn't refer to the ERT problem but to the extension of the configure script to list all third-party products (pspell, aiksaurus, checktex, preview-latex, ...) Michael -- === Michael Schmitt Telefon: +49 651 97551-40 Institut für TelematikTelefax: +49 651 97551-12 Bahnhofstrasse 30-32 WWW: http://www.ti.fhg.de D-54292 Trier E-Mail: mailto:[EMAIL PROTECTED] ===
Re: [patch] relyx
On Tuesday 21 January 2003 09:19, Lars Gullik Bjønnes wrote:
>
> This patch became a bit larger than intended, due to ws changes.
I noticed that, it was the reason why I didn't look to it before. :-)
> This is the cut down version.
>
> | @@ -1400,7 +1400,8 @@ sub ConvertToLayout {
> | print "\nChanging $dummy $name to layout $layout" if $debug_on;
> |
> | # Nest if the layout stack has more than just "Standard" in it
> | -if ($#{$CurrentLayoutStack} > 0) {
> | +if ($#{$CurrentLayoutStack} > 0
> | + && $CurrentLayoutStack =~ /^$ListLayouts$/o) {
> | # Die here for sections & things that can't be nested!
> | print " Nesting!" if $debug_on;
> | print OUTFILE "\n\\begin_deeper ";
> | @@ -1474,7 +1475,8 @@ sub EndLayout {
> | # \end_deeper \begin_deeper in the LyX file. It's sloppy
> | # but it works, and LyX will get rid of it when it
> | # resaves the file.
> | -if ($#{$CurrentLayoutStack} > 0) {
> | +if ($#{$CurrentLayoutStack} > 0
> | + && $CurrentLayoutStack =~ /^$ListLayouts$/o) {
> | print " End Nesting!" if $debug_on;
> | print OUTFILE "\n\\end_deeper ";
> | }
I am not a reLyX people :-), but I see the logic of your change and I say go
with it. To be on the safe side you need Kayvan's opinion. :-)
--
José Abílio
Re: [patch] relyx
José Matos <[EMAIL PROTECTED]> writes: | I am not a reLyX people :-), but I see the logic of your change and I say go | with it. To be on the safe side you need Kayvan's opinion. :-) Some more testing on tex files is also needed. -- Lgb
lyx 1.3pre2 does not display oe and euro symbol
Hello, I would like to switch to lyx 1.3pre2 but it does not allow me to type oe (AltGr + S + g) and euro (AltGr + e) symbols. This was possible in lyx 1.2.X. How could I do so ? Is the answer in the documentation ? regards, --Nabil Hathout
Re: [PATCH] Re: Link to preview-latex in NEWS file
Andre Poenitz wrote:
> On Tue, Jan 21, 2003 at 10:12:28AM +0100, Michael Schmitt wrote:
>> >No. There are still rough edges (display jumping) and there are
>> >conceptual problems (fancy preambles) that make this wonderful
>> >feature unusable under some circumstances. It certainly should not
>> >default to on.
>>
>> I know the first problem and I would be happy to see a fix for it.
>> But what is the second problem (fancy preambles)?
>
> It's rather "Fancy ERT not in preambles".
>
> Preamble:
> \def\foo{\bar}
>
> Later ERT:
> \def\foo{\urgs}
>
> Math:
> \foo
>
> There is another one: Currently, \lyxlock gets written to the .tex
> snippets. This indicates that preview uses the "write to .lyx"
> method instead of "write to .tex" (I think this is a boolean flag
> somewhere, haven't looked at it, though)
>
>> Yes, I guess so. Unfortunately, I don't have enough knowledge to
>> provide a patch for it.
>
> The ERT problem is unsolvable.
Ummm. We already loop over the document to output all math macros.
Could we also output all ERT insets? I guess that there'd be an
accounting problem, as some of these ERT insets would generate output
in the dvi file and some would define variables as above. We'd have
to throw away the previews of any ERT.
The important question however is would it work as a solution to
André's unsolvable problem or would it lead to problems of its own?
I'd guess the latter, but I'm no TeXie.
--
Angus
Why is pspell not activated by default?
File "NEWS" states: > - If you configure with --with-pspell (which uses the PSpell library for > spellchecking), you will be able to automatically spell-check > multi-language documents, assuming you have the right dictionaries > installed. Why isn't this activated by default? Doesn't configure check for the availability of pspell? MIchael -- === Michael Schmitt Telefon: +49 651 97551-40 Institut für TelematikTelefax: +49 651 97551-12 Bahnhofstrasse 30-32 WWW: http://www.ti.fhg.de D-54292 Trier E-Mail: mailto:[EMAIL PROTECTED] ===
Re: [PATCH] Re: Link to preview-latex in NEWS file
On Tue, Jan 21, 2003 at 10:30:36AM +, Angus Leeming wrote: > Ummm. We already loop over the document to output all math macros. > Could we also output all ERT insets? All up to the position of the snippet. And if the snippet is moved, we can't use the cached image. And so on. This is a can of worms. > I guess that there'd be an accounting problem, as some of these ERT > insets would generate output in the dvi file and some would define > variables as above. We'd have to throw away the previews of any ERT. > > The important question however is would it work as a solution to André's > unsolvable problem or would it lead to problems of its own? I'd guess > the latter, but I'm no TeXie. The problem is unsolvable. To get a precise preview of something you need to process _all_ the .tex up to the point of this "something" (and probably the next page as well). It's probably better to produce a single full dvi preview in the background "all the time" and snip from there instead of the current "snippet based" approach (which is simple and cute, but not robust at all). Please do not put too much effort into something that can't be fixed. Andre' -- Those who desire to give up Freedom in order to gain Security, will not have, nor do they deserve, either one. (T. Jefferson)
Re: [patch] relyx
Juergen Spitzmueller wrote: > This does still loop on my test file (export -- reimport the attached LyX > file). If I change the order in the reLyXed lyx file: \layout Enumerate + \begin_deeper \begin_float tab - \begin_deeper \layout Standard \align center \LyXTable ... then lyx reads the file correctly. HTH, Jürgen.
Re: [PATCH] Re: Link to preview-latex in NEWS file
Andre Poenitz wrote: It's probably better to produce a single full dvi preview in the background "all the time" and snip from there instead of the current "snippet based" approach (which is simple and cute, but not robust at all). Please do not put too much effort into something that can't be fixed. I think we will get serious performance problems if we produce full DVI previews all the time. After all, the problem will only occur for real power users. IMHO it would be a complete waste of time to redesign the preview code which works very well in general. Michael -- === Michael Schmitt Telefon: +49 651 97551-40 Institut für TelematikTelefax: +49 651 97551-12 Bahnhofstrasse 30-32 WWW: http://www.ti.fhg.de D-54292 Trier E-Mail: mailto:[EMAIL PROTECTED] ===
Re: [PATCH] Re: Link to preview-latex in NEWS file
On Tue, Jan 21, 2003 at 11:58:34AM +0100, Michael Schmitt wrote: > After all, the problem will only occur for real power users. IMHO it > would be a complete waste of time to redesign the preview code which > works very well in general. But you accept that "very well in general" is not sufficient to be the default? Andre' -- Those who desire to give up Freedom in order to gain Security, will not have, nor do they deserve, either one. (T. Jefferson)
Re: [patch] relyx
Lars Gullik Bjønnes wrote:
> This is the cut down version.
>
> | @@ -1400,7 +1400,8 @@ sub ConvertToLayout {
> | print "\nChanging $dummy $name to layout $layout" if $debug_on;
> |
> | # Nest if the layout stack has more than just "Standard" in it
> | -if ($#{$CurrentLayoutStack} > 0) {
> | +if ($#{$CurrentLayoutStack} > 0
> | + && $CurrentLayoutStack =~ /^$ListLayouts$/o) {
> | # Die here for sections & things that can't be nested!
> | print " Nesting!" if $debug_on;
> | print OUTFILE "\n\\begin_deeper ";
> | @@ -1474,7 +1475,8 @@ sub EndLayout {
> | # \end_deeper \begin_deeper in the LyX file. It's sloppy
> | # but it works, and LyX will get rid of it when it
> | # resaves the file.
> | -if ($#{$CurrentLayoutStack} > 0) {
> | +if ($#{$CurrentLayoutStack} > 0
> | + && $CurrentLayoutStack =~ /^$ListLayouts$/o) {
> | print " End Nesting!" if $debug_on;
> | print OUTFILE "\n\\end_deeper ";
> | }
This does still loop on my test file (export -- reimport the attached LyX
file).
Jürgen.
#LyX 1.3 created this file. For more info see http://www.lyx.org/
\lyxformat 221
\textclass article
\language ngerman
\inputencoding auto
\fontscheme default
\graphics default
\paperfontsize default
\spacing single
\papersize Default
\paperpackage a4
\use_geometry 0
\use_amsmath 0
\use_natbib 0
\use_numerical_citations 0
\paperorientation portrait
\secnumdepth 3
\tocdepth 3
\paragraph_separation indent
\defskip medskip
\quotes_language german
\quotes_times 2
\papercolumns 1
\papersides 1
\paperpagestyle default
\layout Enumerate
one
\layout Enumerate
\begin_inset Float table
wide false
collapsed true
\layout Standard
\align center
\begin_inset Tabular
\begin_inset Text
\layout Standard
\end_inset
\end_inset
\layout Caption
a table
\end_inset
\layout Enumerate
three
\the_end
Boost thinks that every C functions are in std::
It seems that I am really not able to compile 1.3.0cvs on tru64 unix with cxx. Reasons are: - there is no snprintf in tru64 4.0f, so xforms has to provide its own. the one provided in xforms lib does not compile on tru64, but it does after a patch that I sent to the xforms list. So far, so good. - LyX's configure script does not know that it has to use -lformssnp on systems that do not have snprintf. I have a patch for that. So far so good. - boost really thinks that all C functions are in std:: and uses std::fprintf and things like that all over the place. This is not good at all with cxx and probably sun's CC. I am not sure what to do about that. Ideas? JMarc
Re: [patch] relyx
[EMAIL PROTECTED] (Juergen Spitzmueller) writes: | Juergen Spitzmueller wrote: | > This does still loop on my test file (export -- reimport the attached LyX | > file). | | If I change the order in the reLyXed lyx file: | | \layout Enumerate | + \begin_deeper | \begin_float tab | - \begin_deeper | \layout Standard | \align center | \LyXTable | ... | | then lyx reads the file correctly. Yes, and this is part of the problem... when entering a float the current layoutstack should be pushed on a stack... and popped again when the float is handled. -- Lgb
