Re: Change chapter structure

[Yann Collete]

Hello,

I found a package named sectsty and it helps a lot,

Thanks

YC

 Mailing-List: contact [EMAIL PROTECTED]; run by ezmlm
 X-No-Archive: yes
 List-Post: mailto:[EMAIL PROTECTED]
 List-Help: mailto:[EMAIL PROTECTED]
 List-Unsubscribe: 
mailto:[EMAIL PROTECTED]
 Delivered-To: mailing list [EMAIL PROTECTED]
 Date: Mon, 16 Jul 2001 16:28:57 +0200
 From: Herbert Voss [EMAIL PROTECTED]
 X-Accept-Language: de, en
 MIME-Version: 1.0
 To: Yann Collete [EMAIL PROTECTED]
 CC: [EMAIL PROTECTED]
 Subject: Re: Change chapter structure
 Content-Transfer-Encoding: 7bit
 
 Yann Collete wrote:
  
  Hello,
  
  What is secsty package for ?
  I can't find it on www.loria.fr/ctan.
 
 control section headers. it's available at ftp://ftp.dante.de
 
 Herbert
 
 
 -- 
 http://www.educat.hu-berlin.de/~voss/lyx/
 
 

Re: pdf presentation

[Myriam Abramson]

 You can use dvipdfm to generate the PDF.
 If you don't have dvipdfm installed, then after installing it select the
 edit-reconfigure menu in lyx.

Okay, I'll try that. I should specify dvipdfm to generate the pdf in
lyxrc? 

 
 PS: You might also need to change the slide width/height so it will use the
 entire screen. For example, you might need to put 
 \setlength{\slidewidth}{9.5in} in the preamble.


-- 
   myriam


As seen in a coffee shop in Monterey, CA,
George W. Bush's counter:

1283 days left till he's gone

latex2html w/o bibtex?

[Jürgen Spitzmüller]

Hi,

When exporting/ viewing html directly from LyX (with setting
latex2html -no_subdir -split 0 -show_section_numbers $$i)
bibtex is obviously not run. I get blanks instead of labels and no 
references! instead of the bibliography.
However, if I export the document to LaTeX and run

latex $$i
bibtex $$i
latex $$i
latex2html -no_subdir -split 0 -show_section_numbers $$i

manually, everything is fine!

This happens with LyX 1.1.6fix2 (bibtopic support in Latex.C enabled) 
and 1.2.0 (CVS from yesterday).
Is this a general problem or do I have to change my settings (I seem to 
remember that this used to work)?

I run texhash, reconfigured lyx, recompiled lyx... no success :-(

Thanks,
Jürgen

Re: Change chapter structure

[Dekel Tsur]

On Tue, Jul 17, 2001 at 08:48:55AM +0200, Yann Collete wrote:
 Hello,
 
 I found a package named sectsty and it helps a lot,

You can also check the titlesec package.

Re: Colored multicolumns and fixed width

[Dekel Tsur]

On Sun, Jul 15, 2001 at 10:44:03PM +0200, Herbert Voss wrote:
 Saalfeld, Christoph wrote:
  
  I have several tables with multicolumns of fixed size.
  Now I tried to colorize the columns at beginning of the table by entering
  
 {\columncolor[gray]{0.8}}l|
  
  into the Special multicolumn - Alignment field. From now on the values in
  the Special multicolumn - Width field are ignored. But I need a fixed
  width of 1.3cm. I tried the following:
  
 {m{1.3cm}\columncolor[gray]{0.8}}l|
 
 try p{1.3cm} , instead of m

You also need to put the p{} instead of the 'l' namely

{\columncolor[gray]{0.8}}p{1.3cm}|

Ispell still not working

[Amer Abufadel]

Hello,
I installed Lyx and ispell does not work even if I choose another
dictionary.  Ispell, however,  DOES work from the command prompt.

Another issue is that import latex does not seem to work either.

What am I doing wrong?

Thank you for your time and help.

Amer

Re: latex2html w/o bibtex?

[Dekel Tsur]

On Tue, Jul 17, 2001 at 03:37:53PM +0200, Jürgen Spitzmüller wrote:
 When exporting/ viewing html directly from LyX (with setting
 latex2html -no_subdir -split 0 -show_section_numbers $$i)
 bibtex is obviously not run. I get blanks instead of labels and no 
 references! instead of the bibliography.
 However, if I export the document to LaTeX and run
 
 latex $$i
 bibtex $$i
 latex $$i
 latex2html -no_subdir -split 0 -show_section_numbers $$i
 
 manually, everything is fine!
 
 This happens with LyX 1.1.6fix2 (bibtopic support in Latex.C enabled) 
 and 1.2.0 (CVS from yesterday).
 Is this a general problem or do I have to change my settings (I seem to 
 remember that this used to work)?

It should work.
Open the converters tab in the preferences dialog, and select the
latex-html converter. What is the value of the 'flag' field ?
It should be originaldir,needaux

Re: What version of XForms should we use?

[Baruch Even]

I believe there was a conclusion to avoid that warning of using LyX with
XForms 0.89, it is used by users and by the developers and no harm is
known to happen from using 0.89

I myself use 0.89 on Debian sid and see no problems with that.

Anything that says otherwise in the docs or in code should probably be
changed.

A bug list is available on sourceforge in the project lyx-bugs,
basically we use sf as our bug archival system.

* Peter S Galbraith [EMAIL PROTECTED] [010717 17:19]:
 Hello,
 
 [Please let me know if this should have gone to lyx-devel instead.]
 
 There's some discussion on a Debian mailing list (debian-french)
 whether the Lyx package should be built against XForms 0.88 or
 0.89.  See also http://bugs.debian.org/105486
 
 I couldn't find anything obvious on the lyx web page, but found
 this in lyx-1.1.6fix2.tar.gz's README file:
 
 : What do I need to compile LyX from the source distribution?
 : 
 : 2. The Xforms library version 0.88 (recommended) or 0.89.
 : 
 : Read the file INSTALL for more information on compiling.
 
 The INSTALL file says:
 
 : As of LyX version 1.1.5, you will need to have Xforms library and header
 : version 0.88 or 0.89.  Version 0.88 is a stable release and the
 : recommended version.
 
 Now, libforms0.89 might be the development version, but 0.88 is
 _quite_ old (29-05-1999 pour i386, 12-05-1999 for m68k), is
 receiving _no_ bug fixes, and has only glibc2.0 releases for sparc
 and m68k.
 
 I'm pretty sure 0.89 was recommended for Lyx about 18 months ago.
 Did the Lyx source code change to fit 0.88 better since then?
 
 What should Debian do?  (also considering the lack of XForms 0.88
 for certain arches)  Are there known problems using 0.89?
 (Sorry, I couldn't find a bug list on the lyx web site)
 
 Thanks very much,
 
 Peter Galbraith, the Debian package maintainer for XForms.

-- 
Baruch Even
http://baruch.ev-en.org/

Re: latex2html w/o bibtex?

[Jürgen Spitzmüller]

On Tuesday, 17. July 2001 17:03, Dekel Tsur wrote:
 It should work.
 Open the converters tab in the preferences dialog, and select the
 latex-html converter. What is the value of the 'flag' field ?
 It should be originaldir,needaux

Aaahhh... the flag field was empty! Now everything is o.k. again. 
Next time I should be more careful when playing with the converter 
stuff. Sorry about that.

Thanks,
Jürgen

Re: What version of XForms should we use?

[Peter S Galbraith]

Baruch Even wrote:

 I believe there was a conclusion to avoid that warning of using LyX with
 XForms 0.89, it is used by users and by the developers and no harm is
 known to happen from using 0.89
 
 I myself use 0.89 on Debian sid and see no problems with that.

Great.  Since you are a lyx developper, I think we can safely
that your advice and continue to build using 0.89.
 
 Anything that says otherwise in the docs or in code should probably be
 changed.

I tracked down the change (dated 2000/04/26) in the README file to
http://www.lyx.org/cgi-bin/cvsweb.cgi/lyx-devel/README.diff?r1=1.3r2=1.4

The diff is:

 2. The Xforms library version 0.81, 0.86 or 0.88.
 2. The Xforms library version 0.88 (recommended) or 0.89.

In that context (the change made and the date it was made on),
the comment doesn't really seem that conclusive against 0.89.
Version 0.89 was still changing a bit, so 0.88 was probably safer
at that point? (I'm speculating)

I'd very appreciate it if you could edit the README and INSTALL
files in CVS so this is made clearer.  (It would be nicer still
if a few words were found on the Lyx web site, but that may be
beyond your control.  Should I file a wislist bug at SF?)

 A bug list is available on sourceforge in the project lyx-bugs,
 basically we use sf as our bug archival system.

http://sourceforge.net/projects/lyxbugs/

Thanks!  Good to know.  There should be a link from www.lyx.org
too.  ;-)

Peter

Re: Internationalization?

[Emmanuel GUREGHIAN]

M.B. Schiekel a écrit :
 
 Well, another newbie question (Lyx 1.1.6 fix1, SuSE-Linux 7.2):
 I would like to work with the ´english´ version of Lyx despite of my
 $LANG=de_DE (because of german texts and other programs).
 So I copied the english bind-files and ui-file in my /home/xxx/.lyx
 bind- and ui-directories and set the right path in the
 lyx-preferences. But it doesn´t help - I always get the ´german´ lyx.
 Thank you for your help and understanding -
 bernhard
alias mylyx 'unsetenv LANG; lyx' ? [tcsh]
alias mylyx 'export  LANG=us; lyx' ? [sh but I am not sure]

it is a simple solution, I use it to change from development versions
and stable versions.

Beware because it is patented under number 3.14.15.92.7. But I allow you
to use it without royalties (c:

If you want to recover your $LANG=de_DE in your shell, just put
parenthesis around the commands and put it in background and it should
work. I would do this in tcsh :

alias monlyx 'unsetenv LANG ; lyx \!*  '

it should be easy to translate it in sh.

A+
-- 
  |\  _,,,---,,_  Emmanuel GUREGHIAN 
ZZZzz /,`.-'`'-.  ;-;;,_   mailto:[EMAIL PROTECTED]
 |,4-  ) )-,_. ,\ (  `'-'  
'---''(_/--'  `-'\_)

Re: notes/comments (was Re: bilingual documents?)

[Matej Cepl]

Yes!!! This is something which I would love to have for a long 
time. Together with importing comments in LaTeX file into LyX as 
notes.

Matej

On 9 Jul 2001, at 13:56, Guenter Milde wrote:

 On Thu, 28 Jun 2001 11:54:16 -0300 wrote Ralph Boland
 [EMAIL PROTECTED]:
 
  Of interest, I also have to send versions of my papers to
  my supervisor or to co-authors.
  
  It would be very useful to be able to insert comments in the
  middle of a paragraph.  e.g.  (break sentence in two)
 (give reference)
  
  I guess margin comments are supposed to provide this
  facility.  However I would like:
1)  The comment marker to be more visible.
   Like the bright yellow and large box of the Note
   marker.
2)  The ability to have the comment appear in
  the text rather than have to open up the marker
  (like math equations).
  This ability needs to controllable on an individual
   comment basis and on a global basis.
3)  The ability to go to prev/next comment.  Thus if
someone
  has marked up my paper with comments I would like to be
  able to go through them one at a time.  I would want to
  be able to program a key to do this.
4)   I personally wouldn't want them printed as happens with
  margin comments.  Personal tastes may vary here.
  I suppose this could be controllable too.
 5)  Note that a Note comment cannot be used here because
   it doesn't allow math equations etc. to be placed in
   them.
 
 Note, that almost all would be solved, if a Note would allow math
 etc. (I darkly remember, that there was something like
 open/close all for floats + the ability to toggle this by
 clicking) ...
 
 So my suggestion would be to make the note box more like a
 footnote box: i.e. it should not open a separate window but an
 inset (like floats, errors, ert-inset, and footnotes) and should
 (as a footnote or a comment) allow all the lyx-stuff like math,
 figures ... 
 
 The difference to the Comment paragraph style would be like the
 one between LaTeX paragraph and ERT-inset (+ the Go To Note
 menu entry in the Navigate menu). 
 
 Normal keybindings would work (xforms and KDE don't work well
 together, therefore my Del key does BS in all popup-windows,
 which sometimes is anoying.
 
 LaTeX export should also export notes (as comments, may be with a
 leading %Note:) (Then also optional printing is possible with
 the right package ...)
 
  What do other people think of this?  Would this be much work or
  could some
 existing code be reused? Should I have posted to devel?
 
 Guenter
 
 
 
 
 
 
 
 
 
 --
 [EMAIL PROTECTED]
 

Changing Fontsize of ToC and LoF

[Detlev Humann]

Hi!
I´d like to change the fontsize of the ToC and the 
LoF from 12 pt to 10 pt (to have more space for long chapter and section 
headlines), whereas the rest of the text remains in 12 pt fontsize.
Is there a way to do it? I´m using 
bookkoma-script.
Thanks in advance
Detlev

Re: What version of XForms should we use?

[John Levon]

On Tue, Jul 17, 2001 at 11:38:20AM -0400, Peter S Galbraith wrote:

  A bug list is available on sourceforge in the project lyx-bugs,
  basically we use sf as our bug archival system.
 
 http://sourceforge.net/projects/lyxbugs/
 
 Thanks!  Good to know.  There should be a link from www.lyx.org
 too.  ;-)

it isn't official yet, that's why there isn't. I still hold out hope
of getting a real bug tracking system installed for lyx rather than
that sourceforge abomination of a system ...

regards
john

-- 
Voodoo Programming:  Things programmers do that they know shouldn't work but
 they try anyway, and which sometimes actually work, such as recompiling
 everything.
- Karl Lehenbauer

Re: Changing Fontsize of ToC and LoF

[Tuukka Toivonen]

On Tue, 17 Jul 2001, Detlev Humann wrote:

 I´d like to change the fontsize of the ToC and the LoF from 12 pt to 10 pt
 (to have more space for long chapter and section headlines), whereas the
rest of the text remains in 12 pt fontsize.

Just select (highlight) the Table of Contents gray button, select
Layout/Character/Size and select Smaller or anything you want. Works fine
here.

Re: What version of XForms should we use?

[Baruch Even]

* Peter S Galbraith [EMAIL PROTECTED] [010717 18:47]:
 
 Baruch Even wrote:
 
  I believe there was a conclusion to avoid that warning of using LyX with
  XForms 0.89, it is used by users and by the developers and no harm is
  known to happen from using 0.89
  
  I myself use 0.89 on Debian sid and see no problems with that.
 
 Great.  Since you are a lyx developper, I think we can safely
 that your advice and continue to build using 0.89.

I am one of the developers but this is my impression and the fact that I
do not know of any report of problem with 0.89, but I guess any other
developer will also say the same.

  Anything that says otherwise in the docs or in code should probably be
  changed.
 
 I tracked down the change (dated 2000/04/26) in the README file to
 http://www.lyx.org/cgi-bin/cvsweb.cgi/lyx-devel/README.diff?r1=1.3r2=1.4
 
 The diff is:
 
  2. The Xforms library version 0.81, 0.86 or 0.88.
  2. The Xforms library version 0.88 (recommended) or 0.89.
 
 In that context (the change made and the date it was made on),
 the comment doesn't really seem that conclusive against 0.89.
 Version 0.89 was still changing a bit, so 0.88 was probably safer
 at that point? (I'm speculating)

I don't think I was on the dev team at the time to comment.

 I'd very appreciate it if you could edit the README and INSTALL
 files in CVS so this is made clearer.  (It would be nicer still
 if a few words were found on the Lyx web site, but that may be
 beyond your control.  Should I file a wislist bug at SF?)

File one anyway so it will be kept there in case it falls to the
wayside. John is our BTS supervisor, he is the one who keeps us in sync
with the BTS and reminds us to do our tasks.

  A bug list is available on sourceforge in the project lyx-bugs,
  basically we use sf as our bug archival system.
 
 http://sourceforge.net/projects/lyxbugs/
 
 Thanks!  Good to know.  There should be a link from www.lyx.org
 too.  ;-)

John replied to that already, it's yet to be made official.

-- 
Baruch Even
http://baruch.ev-en.org/

Re: What version of XForms should we use?

[Peter S Galbraith]

Baruch Even wrote:

 * Peter S Galbraith [EMAIL PROTECTED] [010717 18:47]:

  Great.  Since you are a lyx developper, I think we can safely
  that your advice and continue to build using 0.89.
 
 I am one of the developers but this is my impression and the fact that I
 do not know of any report of problem with 0.89, but I guess any other
 developer will also say the same.

Nobody has objected so far!  :-)
 
  I'd very appreciate it if you could edit the README and INSTALL
  files in CVS so this is made clearer.  (It would be nicer still
  if a few words were found on the Lyx web site, but that may be
  beyond your control.  Should I file a wislist bug at SF?)
 
 File one anyway so it will be kept there in case it falls to the
 wayside. John is our BTS supervisor, he is the one who keeps us in sync
 with the BTS and reminds us to do our tasks.

Done.  SF bug #442124.  Thanks!

Peter

Re: Change chapter structure

[Yann Collete]

Hello,

I found a package named sectsty and it helps a lot,

Thanks

YC

 Mailing-List: contact [EMAIL PROTECTED]; run by ezmlm
 X-No-Archive: yes
 List-Post: mailto:[EMAIL PROTECTED]
 List-Help: mailto:[EMAIL PROTECTED]
 List-Unsubscribe: 
mailto:[EMAIL PROTECTED]
 Delivered-To: mailing list [EMAIL PROTECTED]
 Date: Mon, 16 Jul 2001 16:28:57 +0200
 From: Herbert Voss [EMAIL PROTECTED]
 X-Accept-Language: de, en
 MIME-Version: 1.0
 To: Yann Collete [EMAIL PROTECTED]
 CC: [EMAIL PROTECTED]
 Subject: Re: Change chapter structure
 Content-Transfer-Encoding: 7bit
 
 Yann Collete wrote:
  
  Hello,
  
  What is secsty package for ?
  I can't find it on www.loria.fr/ctan.
 
 control section headers. it's available at ftp://ftp.dante.de
 
 Herbert
 
 
 -- 
 http://www.educat.hu-berlin.de/~voss/lyx/
 
 

Re: pdf presentation

[Myriam Abramson]

 You can use dvipdfm to generate the PDF.
 If you don't have dvipdfm installed, then after installing it select the
 edit-reconfigure menu in lyx.

Okay, I'll try that. I should specify dvipdfm to generate the pdf in
lyxrc? 

 
 PS: You might also need to change the slide width/height so it will use the
 entire screen. For example, you might need to put 
 \setlength{\slidewidth}{9.5in} in the preamble.


-- 
   myriam


As seen in a coffee shop in Monterey, CA,
George W. Bush's counter:

1283 days left till he's gone

latex2html w/o bibtex?

[Jürgen Spitzmüller]

Hi,

When exporting/ viewing html directly from LyX (with setting
latex2html -no_subdir -split 0 -show_section_numbers $$i)
bibtex is obviously not run. I get blanks instead of labels and no 
references! instead of the bibliography.
However, if I export the document to LaTeX and run

latex $$i
bibtex $$i
latex $$i
latex2html -no_subdir -split 0 -show_section_numbers $$i

manually, everything is fine!

This happens with LyX 1.1.6fix2 (bibtopic support in Latex.C enabled) 
and 1.2.0 (CVS from yesterday).
Is this a general problem or do I have to change my settings (I seem to 
remember that this used to work)?

I run texhash, reconfigured lyx, recompiled lyx... no success :-(

Thanks,
Jürgen

Re: Change chapter structure

[Dekel Tsur]

On Tue, Jul 17, 2001 at 08:48:55AM +0200, Yann Collete wrote:
 Hello,
 
 I found a package named sectsty and it helps a lot,

You can also check the titlesec package.

Re: Colored multicolumns and fixed width

[Dekel Tsur]

On Sun, Jul 15, 2001 at 10:44:03PM +0200, Herbert Voss wrote:
 Saalfeld, Christoph wrote:
  
  I have several tables with multicolumns of fixed size.
  Now I tried to colorize the columns at beginning of the table by entering
  
 {\columncolor[gray]{0.8}}l|
  
  into the Special multicolumn - Alignment field. From now on the values in
  the Special multicolumn - Width field are ignored. But I need a fixed
  width of 1.3cm. I tried the following:
  
 {m{1.3cm}\columncolor[gray]{0.8}}l|
 
 try p{1.3cm} , instead of m

You also need to put the p{} instead of the 'l' namely

{\columncolor[gray]{0.8}}p{1.3cm}|

Ispell still not working

[Amer Abufadel]

Hello,
I installed Lyx and ispell does not work even if I choose another
dictionary.  Ispell, however,  DOES work from the command prompt.

Another issue is that import latex does not seem to work either.

What am I doing wrong?

Thank you for your time and help.

Amer

Re: latex2html w/o bibtex?

[Dekel Tsur]

On Tue, Jul 17, 2001 at 03:37:53PM +0200, Jürgen Spitzmüller wrote:
 When exporting/ viewing html directly from LyX (with setting
 latex2html -no_subdir -split 0 -show_section_numbers $$i)
 bibtex is obviously not run. I get blanks instead of labels and no 
 references! instead of the bibliography.
 However, if I export the document to LaTeX and run
 
 latex $$i
 bibtex $$i
 latex $$i
 latex2html -no_subdir -split 0 -show_section_numbers $$i
 
 manually, everything is fine!
 
 This happens with LyX 1.1.6fix2 (bibtopic support in Latex.C enabled) 
 and 1.2.0 (CVS from yesterday).
 Is this a general problem or do I have to change my settings (I seem to 
 remember that this used to work)?

It should work.
Open the converters tab in the preferences dialog, and select the
latex-html converter. What is the value of the 'flag' field ?
It should be originaldir,needaux

Re: What version of XForms should we use?

[Baruch Even]

I believe there was a conclusion to avoid that warning of using LyX with
XForms 0.89, it is used by users and by the developers and no harm is
known to happen from using 0.89

I myself use 0.89 on Debian sid and see no problems with that.

Anything that says otherwise in the docs or in code should probably be
changed.

A bug list is available on sourceforge in the project lyx-bugs,
basically we use sf as our bug archival system.

* Peter S Galbraith [EMAIL PROTECTED] [010717 17:19]:
 Hello,
 
 [Please let me know if this should have gone to lyx-devel instead.]
 
 There's some discussion on a Debian mailing list (debian-french)
 whether the Lyx package should be built against XForms 0.88 or
 0.89.  See also http://bugs.debian.org/105486
 
 I couldn't find anything obvious on the lyx web page, but found
 this in lyx-1.1.6fix2.tar.gz's README file:
 
 : What do I need to compile LyX from the source distribution?
 : 
 : 2. The Xforms library version 0.88 (recommended) or 0.89.
 : 
 : Read the file INSTALL for more information on compiling.
 
 The INSTALL file says:
 
 : As of LyX version 1.1.5, you will need to have Xforms library and header
 : version 0.88 or 0.89.  Version 0.88 is a stable release and the
 : recommended version.
 
 Now, libforms0.89 might be the development version, but 0.88 is
 _quite_ old (29-05-1999 pour i386, 12-05-1999 for m68k), is
 receiving _no_ bug fixes, and has only glibc2.0 releases for sparc
 and m68k.
 
 I'm pretty sure 0.89 was recommended for Lyx about 18 months ago.
 Did the Lyx source code change to fit 0.88 better since then?
 
 What should Debian do?  (also considering the lack of XForms 0.88
 for certain arches)  Are there known problems using 0.89?
 (Sorry, I couldn't find a bug list on the lyx web site)
 
 Thanks very much,
 
 Peter Galbraith, the Debian package maintainer for XForms.

-- 
Baruch Even
http://baruch.ev-en.org/

Re: latex2html w/o bibtex?

[Jürgen Spitzmüller]

On Tuesday, 17. July 2001 17:03, Dekel Tsur wrote:
 It should work.
 Open the converters tab in the preferences dialog, and select the
 latex-html converter. What is the value of the 'flag' field ?
 It should be originaldir,needaux

Aaahhh... the flag field was empty! Now everything is o.k. again. 
Next time I should be more careful when playing with the converter 
stuff. Sorry about that.

Thanks,
Jürgen

Re: What version of XForms should we use?

[Peter S Galbraith]

Baruch Even wrote:

 I believe there was a conclusion to avoid that warning of using LyX with
 XForms 0.89, it is used by users and by the developers and no harm is
 known to happen from using 0.89
 
 I myself use 0.89 on Debian sid and see no problems with that.

Great.  Since you are a lyx developper, I think we can safely
that your advice and continue to build using 0.89.
 
 Anything that says otherwise in the docs or in code should probably be
 changed.

I tracked down the change (dated 2000/04/26) in the README file to
http://www.lyx.org/cgi-bin/cvsweb.cgi/lyx-devel/README.diff?r1=1.3r2=1.4

The diff is:

 2. The Xforms library version 0.81, 0.86 or 0.88.
 2. The Xforms library version 0.88 (recommended) or 0.89.

In that context (the change made and the date it was made on),
the comment doesn't really seem that conclusive against 0.89.
Version 0.89 was still changing a bit, so 0.88 was probably safer
at that point? (I'm speculating)

I'd very appreciate it if you could edit the README and INSTALL
files in CVS so this is made clearer.  (It would be nicer still
if a few words were found on the Lyx web site, but that may be
beyond your control.  Should I file a wislist bug at SF?)

 A bug list is available on sourceforge in the project lyx-bugs,
 basically we use sf as our bug archival system.

http://sourceforge.net/projects/lyxbugs/

Thanks!  Good to know.  There should be a link from www.lyx.org
too.  ;-)

Peter

Re: Internationalization?

[Emmanuel GUREGHIAN]

M.B. Schiekel a écrit :
 
 Well, another newbie question (Lyx 1.1.6 fix1, SuSE-Linux 7.2):
 I would like to work with the ´english´ version of Lyx despite of my
 $LANG=de_DE (because of german texts and other programs).
 So I copied the english bind-files and ui-file in my /home/xxx/.lyx
 bind- and ui-directories and set the right path in the
 lyx-preferences. But it doesn´t help - I always get the ´german´ lyx.
 Thank you for your help and understanding -
 bernhard
alias mylyx 'unsetenv LANG; lyx' ? [tcsh]
alias mylyx 'export  LANG=us; lyx' ? [sh but I am not sure]

it is a simple solution, I use it to change from development versions
and stable versions.

Beware because it is patented under number 3.14.15.92.7. But I allow you
to use it without royalties (c:

If you want to recover your $LANG=de_DE in your shell, just put
parenthesis around the commands and put it in background and it should
work. I would do this in tcsh :

alias monlyx 'unsetenv LANG ; lyx \!*  '

it should be easy to translate it in sh.

A+
-- 
  |\  _,,,---,,_  Emmanuel GUREGHIAN 
ZZZzz /,`.-'`'-.  ;-;;,_   mailto:[EMAIL PROTECTED]
 |,4-  ) )-,_. ,\ (  `'-'  
'---''(_/--'  `-'\_)

Re: notes/comments (was Re: bilingual documents?)

[Matej Cepl]

Yes!!! This is something which I would love to have for a long 
time. Together with importing comments in LaTeX file into LyX as 
notes.

Matej

On 9 Jul 2001, at 13:56, Guenter Milde wrote:

 On Thu, 28 Jun 2001 11:54:16 -0300 wrote Ralph Boland
 [EMAIL PROTECTED]:
 
  Of interest, I also have to send versions of my papers to
  my supervisor or to co-authors.
  
  It would be very useful to be able to insert comments in the
  middle of a paragraph.  e.g.  (break sentence in two)
 (give reference)
  
  I guess margin comments are supposed to provide this
  facility.  However I would like:
1)  The comment marker to be more visible.
   Like the bright yellow and large box of the Note
   marker.
2)  The ability to have the comment appear in
  the text rather than have to open up the marker
  (like math equations).
  This ability needs to controllable on an individual
   comment basis and on a global basis.
3)  The ability to go to prev/next comment.  Thus if
someone
  has marked up my paper with comments I would like to be
  able to go through them one at a time.  I would want to
  be able to program a key to do this.
4)   I personally wouldn't want them printed as happens with
  margin comments.  Personal tastes may vary here.
  I suppose this could be controllable too.
 5)  Note that a Note comment cannot be used here because
   it doesn't allow math equations etc. to be placed in
   them.
 
 Note, that almost all would be solved, if a Note would allow math
 etc. (I darkly remember, that there was something like
 open/close all for floats + the ability to toggle this by
 clicking) ...
 
 So my suggestion would be to make the note box more like a
 footnote box: i.e. it should not open a separate window but an
 inset (like floats, errors, ert-inset, and footnotes) and should
 (as a footnote or a comment) allow all the lyx-stuff like math,
 figures ... 
 
 The difference to the Comment paragraph style would be like the
 one between LaTeX paragraph and ERT-inset (+ the Go To Note
 menu entry in the Navigate menu). 
 
 Normal keybindings would work (xforms and KDE don't work well
 together, therefore my Del key does BS in all popup-windows,
 which sometimes is anoying.
 
 LaTeX export should also export notes (as comments, may be with a
 leading %Note:) (Then also optional printing is possible with
 the right package ...)
 
  What do other people think of this?  Would this be much work or
  could some
 existing code be reused? Should I have posted to devel?
 
 Guenter
 
 
 
 
 
 
 
 
 
 --
 [EMAIL PROTECTED]
 

Changing Fontsize of ToC and LoF

[Detlev Humann]

Hi!
I´d like to change the fontsize of the ToC and the 
LoF from 12 pt to 10 pt (to have more space for long chapter and section 
headlines), whereas the rest of the text remains in 12 pt fontsize.
Is there a way to do it? I´m using 
bookkoma-script.
Thanks in advance
Detlev

Re: What version of XForms should we use?

[John Levon]

On Tue, Jul 17, 2001 at 11:38:20AM -0400, Peter S Galbraith wrote:

  A bug list is available on sourceforge in the project lyx-bugs,
  basically we use sf as our bug archival system.
 
 http://sourceforge.net/projects/lyxbugs/
 
 Thanks!  Good to know.  There should be a link from www.lyx.org
 too.  ;-)

it isn't official yet, that's why there isn't. I still hold out hope
of getting a real bug tracking system installed for lyx rather than
that sourceforge abomination of a system ...

regards
john

-- 
Voodoo Programming:  Things programmers do that they know shouldn't work but
 they try anyway, and which sometimes actually work, such as recompiling
 everything.
- Karl Lehenbauer

Re: Changing Fontsize of ToC and LoF

[Tuukka Toivonen]

On Tue, 17 Jul 2001, Detlev Humann wrote:

 I´d like to change the fontsize of the ToC and the LoF from 12 pt to 10 pt
 (to have more space for long chapter and section headlines), whereas the
rest of the text remains in 12 pt fontsize.

Just select (highlight) the Table of Contents gray button, select
Layout/Character/Size and select Smaller or anything you want. Works fine
here.

Re: What version of XForms should we use?

[Baruch Even]

* Peter S Galbraith [EMAIL PROTECTED] [010717 18:47]:
 
 Baruch Even wrote:
 
  I believe there was a conclusion to avoid that warning of using LyX with
  XForms 0.89, it is used by users and by the developers and no harm is
  known to happen from using 0.89
  
  I myself use 0.89 on Debian sid and see no problems with that.
 
 Great.  Since you are a lyx developper, I think we can safely
 that your advice and continue to build using 0.89.

I am one of the developers but this is my impression and the fact that I
do not know of any report of problem with 0.89, but I guess any other
developer will also say the same.

  Anything that says otherwise in the docs or in code should probably be
  changed.
 
 I tracked down the change (dated 2000/04/26) in the README file to
 http://www.lyx.org/cgi-bin/cvsweb.cgi/lyx-devel/README.diff?r1=1.3r2=1.4
 
 The diff is:
 
  2. The Xforms library version 0.81, 0.86 or 0.88.
  2. The Xforms library version 0.88 (recommended) or 0.89.
 
 In that context (the change made and the date it was made on),
 the comment doesn't really seem that conclusive against 0.89.
 Version 0.89 was still changing a bit, so 0.88 was probably safer
 at that point? (I'm speculating)

I don't think I was on the dev team at the time to comment.

 I'd very appreciate it if you could edit the README and INSTALL
 files in CVS so this is made clearer.  (It would be nicer still
 if a few words were found on the Lyx web site, but that may be
 beyond your control.  Should I file a wislist bug at SF?)

File one anyway so it will be kept there in case it falls to the
wayside. John is our BTS supervisor, he is the one who keeps us in sync
with the BTS and reminds us to do our tasks.

  A bug list is available on sourceforge in the project lyx-bugs,
  basically we use sf as our bug archival system.
 
 http://sourceforge.net/projects/lyxbugs/
 
 Thanks!  Good to know.  There should be a link from www.lyx.org
 too.  ;-)

John replied to that already, it's yet to be made official.

-- 
Baruch Even
http://baruch.ev-en.org/

Re: What version of XForms should we use?

[Peter S Galbraith]

Baruch Even wrote:

 * Peter S Galbraith [EMAIL PROTECTED] [010717 18:47]:

  Great.  Since you are a lyx developper, I think we can safely
  that your advice and continue to build using 0.89.
 
 I am one of the developers but this is my impression and the fact that I
 do not know of any report of problem with 0.89, but I guess any other
 developer will also say the same.

Nobody has objected so far!  :-)
 
  I'd very appreciate it if you could edit the README and INSTALL
  files in CVS so this is made clearer.  (It would be nicer still
  if a few words were found on the Lyx web site, but that may be
  beyond your control.  Should I file a wislist bug at SF?)
 
 File one anyway so it will be kept there in case it falls to the
 wayside. John is our BTS supervisor, he is the one who keeps us in sync
 with the BTS and reminds us to do our tasks.

Done.  SF bug #442124.  Thanks!

Peter

Re: Change chapter structure

[Yann Collete]

Hello,

I found a package named sectsty and it helps a lot,

Thanks

YC

> Mailing-List: contact [EMAIL PROTECTED]; run by ezmlm
> X-No-Archive: yes
> List-Post: 
> List-Help: 
> List-Unsubscribe: 

> Delivered-To: mailing list [EMAIL PROTECTED]
> Date: Mon, 16 Jul 2001 16:28:57 +0200
> From: Herbert Voss <[EMAIL PROTECTED]>
> X-Accept-Language: de, en
> MIME-Version: 1.0
> To: Yann Collete <[EMAIL PROTECTED]>
> CC: [EMAIL PROTECTED]
> Subject: Re: Change chapter structure
> Content-Transfer-Encoding: 7bit
> 
> Yann Collete wrote:
> > 
> > Hello,
> > 
> > What is "secsty" package for ?
> > I can't find it on www.loria.fr/ctan.
> 
> control section headers. it's available at ftp://ftp.dante.de
> 
> Herbert
> 
> 
> -- 
> http://www.educat.hu-berlin.de/~voss/lyx/
> 
> 

Re: pdf presentation

[Myriam Abramson]

> You can use dvipdfm to generate the PDF.
> If you don't have dvipdfm installed, then after installing it select the
> edit->reconfigure menu in lyx.

Okay, I'll try that. I should specify dvipdfm to generate the pdf in
lyxrc? 

> 
> PS: You might also need to change the slide width/height so it will use the
> entire screen. For example, you might need to put 
> \setlength{\slidewidth}{9.5in} in the preamble.


-- 
   myriam


As seen in a coffee shop in Monterey, CA,
George W. Bush's counter:

1283 days left till he's gone

latex2html w/o bibtex?

[Jürgen Spitzmüller]

Hi,

When exporting/ viewing html directly from LyX (with setting
latex2html -no_subdir -split 0 -show_section_numbers $$i)
bibtex is obviously not run. I get blanks instead of labels and "no 
references!" instead of the bibliography.
However, if I export the document to LaTeX and run

latex $$i
bibtex $$i
latex $$i
latex2html -no_subdir -split 0 -show_section_numbers $$i

manually, everything is fine!

This happens with LyX 1.1.6fix2 (bibtopic support in Latex.C enabled) 
and 1.2.0 (CVS from yesterday).
Is this a general problem or do I have to change my settings (I seem to 
remember that this used to work)?

I run texhash, reconfigured lyx, recompiled lyx... no success :-(

Thanks,
Jürgen

Re: Change chapter structure

[Dekel Tsur]

On Tue, Jul 17, 2001 at 08:48:55AM +0200, Yann Collete wrote:
> Hello,
> 
> I found a package named sectsty and it helps a lot,

You can also check the titlesec package.

Re: Colored multicolumns and fixed width

[Dekel Tsur]

On Sun, Jul 15, 2001 at 10:44:03PM +0200, Herbert Voss wrote:
> "Saalfeld, Christoph" wrote:
> > 
> > I have several tables with multicolumns of fixed size.
> > Now I tried to colorize the columns at beginning of the table by entering
> > 
> >>{\columncolor[gray]{0.8}}l|
> > 
> > into the "Special multicolumn -> Alignment" field. From now on the values in
> > the ""Special multicolumn -> Width" field are ignored. But I need a fixed
> > width of 1.3cm. I tried the following:
> > 
> >>{m{1.3cm}\columncolor[gray]{0.8}}l|
> 
> try p{1.3cm} , instead of m

You also need to put the p{} instead of the 'l' namely

>{\columncolor[gray]{0.8}}p{1.3cm}|

Ispell still not working

[Amer Abufadel]

Hello,
I installed Lyx and ispell does not work even if I choose another
dictionary.  Ispell, however,  DOES work from the command prompt.

Another issue is that import latex does not seem to work either.

What am I doing wrong?

Thank you for your time and help.

Amer

Re: latex2html w/o bibtex?

[Dekel Tsur]

On Tue, Jul 17, 2001 at 03:37:53PM +0200, Jürgen Spitzmüller wrote:
> When exporting/ viewing html directly from LyX (with setting
> latex2html -no_subdir -split 0 -show_section_numbers $$i)
> bibtex is obviously not run. I get blanks instead of labels and "no 
> references!" instead of the bibliography.
> However, if I export the document to LaTeX and run
> 
> latex $$i
> bibtex $$i
> latex $$i
> latex2html -no_subdir -split 0 -show_section_numbers $$i
> 
> manually, everything is fine!
> 
> This happens with LyX 1.1.6fix2 (bibtopic support in Latex.C enabled) 
> and 1.2.0 (CVS from yesterday).
> Is this a general problem or do I have to change my settings (I seem to 
> remember that this used to work)?

It should work.
Open the converters tab in the preferences dialog, and select the
latex->html converter. What is the value of the 'flag' field ?
It should be originaldir,needaux

Re: What version of XForms should we use?

[Baruch Even]

I believe there was a conclusion to avoid that warning of using LyX with
XForms 0.89, it is used by users and by the developers and no harm is
known to happen from using 0.89

I myself use 0.89 on Debian sid and see no problems with that.

Anything that says otherwise in the docs or in code should probably be
changed.

A bug list is available on sourceforge in the project lyx-bugs,
basically we use sf as our bug archival system.

* Peter S Galbraith <[EMAIL PROTECTED]> [010717 17:19]:
> Hello,
> 
> [Please let me know if this should have gone to lyx-devel instead.]
> 
> There's some discussion on a Debian mailing list (debian-french)
> whether the Lyx package should be built against XForms 0.88 or
> 0.89.  See also http://bugs.debian.org/105486
> 
> I couldn't find anything obvious on the lyx web page, but found
> this in lyx-1.1.6fix2.tar.gz's README file:
> 
> : What do I need to compile LyX from the source distribution?
> : 
> : 2. The Xforms library version 0.88 (recommended) or 0.89.
> : 
> : Read the file "INSTALL" for more information on compiling.
> 
> The INSTALL file says:
> 
> : As of LyX version 1.1.5, you will need to have Xforms library and header
> : version 0.88 or 0.89.  Version 0.88 is a stable release and the
> : recommended version.
> 
> Now, libforms0.89 might be the development version, but 0.88 is
> _quite_ old (29-05-1999 pour i386, 12-05-1999 for m68k), is
> receiving _no_ bug fixes, and has only glibc2.0 releases for sparc
> and m68k.
> 
> I'm pretty sure 0.89 was recommended for Lyx about 18 months ago.
> Did the Lyx source code change to fit 0.88 better since then?
> 
> What should Debian do?  (also considering the lack of XForms 0.88
> for certain arches)  Are there known problems using 0.89?
> (Sorry, I couldn't find a bug list on the lyx web site)
> 
> Thanks very much,
> 
> Peter Galbraith, the Debian package maintainer for XForms.

-- 
Baruch Even
http://baruch.ev-en.org/

Re: latex2html w/o bibtex?

[Jürgen Spitzmüller]

On Tuesday, 17. July 2001 17:03, Dekel Tsur wrote:
> It should work.
> Open the converters tab in the preferences dialog, and select the
> latex->html converter. What is the value of the 'flag' field ?
> It should be originaldir,needaux

Aaahhh... the flag field was empty! Now everything is o.k. again. 
Next time I should be more careful when playing with the converter 
stuff. Sorry about that.

Thanks,
Jürgen

Re: What version of XForms should we use?

[Peter S Galbraith]

Baruch Even wrote:

> I believe there was a conclusion to avoid that warning of using LyX with
> XForms 0.89, it is used by users and by the developers and no harm is
> known to happen from using 0.89
> 
> I myself use 0.89 on Debian sid and see no problems with that.

Great.  Since you are a lyx developper, I think we can safely
that your advice and continue to build using 0.89.
 
> Anything that says otherwise in the docs or in code should probably be
> changed.

I tracked down the change (dated 2000/04/26) in the README file to
http://www.lyx.org/cgi-bin/cvsweb.cgi/lyx-devel/README.diff?r1=1.3=1.4

The diff is:

< 2. The Xforms library version 0.81, 0.86 or 0.88.
> 2. The Xforms library version 0.88 (recommended) or 0.89.

In that context (the change made and the date it was made on),
the comment doesn't really seem that conclusive against 0.89.
Version 0.89 was still changing a bit, so 0.88 was probably safer
at that point? (I'm speculating)

I'd very appreciate it if you could edit the README and INSTALL
files in CVS so this is made clearer.  (It would be nicer still
if a few words were found on the Lyx web site, but that may be
beyond your control.  Should I file a wislist bug at SF?)

> A bug list is available on sourceforge in the project lyx-bugs,
> basically we use sf as our bug archival system.

http://sourceforge.net/projects/lyxbugs/

Thanks!  Good to know.  There should be a link from www.lyx.org
too.  ;-)

Peter

Re: Internationalization?

[Emmanuel GUREGHIAN]

"M.B. Schiekel" a écrit :
> 
> Well, another newbie question (Lyx 1.1.6 fix1, SuSE-Linux 7.2):
> I would like to work with the ´english´ version of Lyx despite of my
> $LANG=de_DE (because of german texts and other programs).
> So I copied the english bind-files and ui-file in my /home/xxx/.lyx
> bind- and ui-directories and set the right path in the
> lyx-preferences. But it doesn´t help - I always get the ´german´ lyx.
> Thank you for your help and understanding -
> bernhard
alias mylyx 'unsetenv LANG; lyx' ? [tcsh]
alias mylyx 'export  LANG=us; lyx' ? [sh but I am not sure]

it is a simple solution, I use it to change from development versions
and stable versions.

Beware because it is patented under number 3.14.15.92.7. But I allow you
to use it without royalties (c:

If you want to recover your $LANG=de_DE in your shell, just put
parenthesis around the commands and put it in background and it should
work. I would do this in tcsh :

alias monlyx 'unsetenv LANG ; lyx \!* & '

it should be easy to translate it in sh.

A+
-- 
  |\  _,,,---,,_  Emmanuel GUREGHIAN 
ZZZzz /,`.-'`'-.  ;-;;,_   mailto:[EMAIL PROTECTED]
 |,4-  ) )-,_. ,\ (  `'-'  
'---''(_/--'  `-'\_)

Re: notes/comments (was Re: bilingual documents?)

[Matej Cepl]

Yes!!! This is something which I would love to have for a long 
time. Together with importing comments in LaTeX file into LyX as 
notes.

Matej

On 9 Jul 2001, at 13:56, Guenter Milde wrote:

> On Thu, 28 Jun 2001 11:54:16 -0300 wrote Ralph Boland
> <[EMAIL PROTECTED]>:
> 
> > Of interest, I also have to send versions of my papers to
> > my supervisor or to co-authors.
> > 
> > It would be very useful to be able to insert comments in the
> > middle of a paragraph.  e.g.  (break sentence in two)
> >(give reference)
> > 
> > I guess margin comments are supposed to provide this
> > facility.  However I would like:
> >   1)  The comment marker to be more visible.
> >  Like the bright yellow and large box of the Note
> >  marker.
> >   2)  The ability to have the comment appear in
> > the text rather than have to open up the marker
> > (like math equations).
> > This ability needs to controllable on an individual
> >  comment basis and on a global basis.
> >   3)  The ability to "go to prev/next comment".  Thus if
> >   someone
> > has marked up my paper with comments I would like to be
> > able to go through them one at a time.  I would want to
> > be able to program a key to do this.
> >   4)   I personally wouldn't want them printed as happens with
> > margin comments.  Personal tastes may vary here.
> > I suppose this could be controllable too.
> >5)  Note that a Note comment cannot be used here because
> >  it doesn't allow math equations etc. to be placed in
> >  them.
> 
> Note, that almost all would be solved, if a Note would allow math
> etc. (I darkly remember, that there was something like
> "open/close all" for floats + the ability to toggle this by
> clicking) ...
> 
> So my suggestion would be to make the note box more like a
> footnote box: i.e. it should not open a separate window but an
> inset (like floats, errors, ert-inset, and footnotes) and should
> (as a footnote or a comment) allow all the lyx-stuff like math,
> figures ... 
> 
> The difference to the "Comment" paragraph style would be like the
> one between LaTeX paragraph and ERT-inset (+ the "Go To Note"
> menu entry in the Navigate menu). 
> 
> Normal keybindings would work (xforms and KDE don't work well
> together, therefore my  key does  in all popup-windows,
> which sometimes is anoying.
> 
> LaTeX export should also export notes (as comments, may be with a
> leading "%Note:") (Then also optional printing is possible with
> the right package ...)
> 
>  What do other people think of this?  Would this be much work or
>  could some
> existing code be reused? Should I have posted to devel?
> 
> Guenter
> 
> 
> 
> 
> 
> 
> 
> 
> 
> --
> [EMAIL PROTECTED]
> 

Changing Fontsize of ToC and LoF

[Detlev Humann]

Hi!
I´d like to change the fontsize of the ToC and the 
LoF from 12 pt to 10 pt (to have more space for long chapter and section 
headlines), whereas the rest of the text remains in 12 pt fontsize.
Is there a way to do it? I´m using 
book koma-script.
Thanks in advance
Detlev

Re: What version of XForms should we use?

[John Levon]

On Tue, Jul 17, 2001 at 11:38:20AM -0400, Peter S Galbraith wrote:

> > A bug list is available on sourceforge in the project lyx-bugs,
> > basically we use sf as our bug archival system.
> 
> http://sourceforge.net/projects/lyxbugs/
> 
> Thanks!  Good to know.  There should be a link from www.lyx.org
> too.  ;-)

it isn't official yet, that's why there isn't. I still hold out hope
of getting a real bug tracking system installed for lyx rather than
that sourceforge abomination of a system ...

regards
john

-- 
"Voodoo Programming:  Things programmers do that they know shouldn't work but
 they try anyway, and which sometimes actually work, such as recompiling
 everything."
- Karl Lehenbauer

Re: Changing Fontsize of ToC and LoF

[Tuukka Toivonen]

On Tue, 17 Jul 2001, Detlev Humann wrote:

> I´d like to change the fontsize of the ToC and the LoF from 12 pt to 10 pt
> (to have more space for long chapter and section headlines), whereas the
>rest of the text remains in 12 pt fontsize.

Just select (highlight) the "Table of Contents" gray button, select
Layout/Character/Size and select Smaller or anything you want. Works fine
here.

Re: What version of XForms should we use?

[Baruch Even]

* Peter S Galbraith <[EMAIL PROTECTED]> [010717 18:47]:
> 
> Baruch Even wrote:
> 
> > I believe there was a conclusion to avoid that warning of using LyX with
> > XForms 0.89, it is used by users and by the developers and no harm is
> > known to happen from using 0.89
> > 
> > I myself use 0.89 on Debian sid and see no problems with that.
> 
> Great.  Since you are a lyx developper, I think we can safely
> that your advice and continue to build using 0.89.

I am one of the developers but this is my impression and the fact that I
do not know of any report of problem with 0.89, but I guess any other
developer will also say the same.

> > Anything that says otherwise in the docs or in code should probably be
> > changed.
> 
> I tracked down the change (dated 2000/04/26) in the README file to
> http://www.lyx.org/cgi-bin/cvsweb.cgi/lyx-devel/README.diff?r1=1.3=1.4
> 
> The diff is:
> 
> < 2. The Xforms library version 0.81, 0.86 or 0.88.
> > 2. The Xforms library version 0.88 (recommended) or 0.89.
> 
> In that context (the change made and the date it was made on),
> the comment doesn't really seem that conclusive against 0.89.
> Version 0.89 was still changing a bit, so 0.88 was probably safer
> at that point? (I'm speculating)

I don't think I was on the dev team at the time to comment.

> I'd very appreciate it if you could edit the README and INSTALL
> files in CVS so this is made clearer.  (It would be nicer still
> if a few words were found on the Lyx web site, but that may be
> beyond your control.  Should I file a wislist bug at SF?)

File one anyway so it will be kept there in case it falls to the
wayside. John is our BTS supervisor, he is the one who keeps us in sync
with the BTS and reminds us to do our tasks.

> > A bug list is available on sourceforge in the project lyx-bugs,
> > basically we use sf as our bug archival system.
> 
> http://sourceforge.net/projects/lyxbugs/
> 
> Thanks!  Good to know.  There should be a link from www.lyx.org
> too.  ;-)

John replied to that already, it's yet to be made official.

-- 
Baruch Even
http://baruch.ev-en.org/

Re: What version of XForms should we use?

[Peter S Galbraith]

Baruch Even wrote:

> * Peter S Galbraith <[EMAIL PROTECTED]> [010717 18:47]:
>
> > Great.  Since you are a lyx developper, I think we can safely
> > that your advice and continue to build using 0.89.
> 
> I am one of the developers but this is my impression and the fact that I
> do not know of any report of problem with 0.89, but I guess any other
> developer will also say the same.

Nobody has objected so far!  :-)
 
> > I'd very appreciate it if you could edit the README and INSTALL
> > files in CVS so this is made clearer.  (It would be nicer still
> > if a few words were found on the Lyx web site, but that may be
> > beyond your control.  Should I file a wislist bug at SF?)
> 
> File one anyway so it will be kept there in case it falls to the
> wayside. John is our BTS supervisor, he is the one who keeps us in sync
> with the BTS and reminds us to do our tasks.

Done.  SF bug #442124.  Thanks!

Peter