Re: Placement of \usepackage{babel}

[Juergen Spitzmueller]

Jean-Marc Lasgouttes wrote:
 I think I documented it un UPGRADING, but of course it should be in
 herbert's tips...

We should also document that things like

\AtBeginDocument{\renewcommand\contentsname{Contents}}

won't work anymore. I think this is used quite frequently (the fix is to place 
\usepackage{babel} manually before that redefinition).

Juergen. 

Re: elsart and bibtex

[Juergen Vigna]

On 03-May-2002 Herbert Voss wrote:

 don't know.
 here it comes

Rob please head that when applying patches which change the fileformat of
a .lyx file you always risk that you can never read them again with a real
lyx. We may put the patch into cvs, but most probably not for 1.2.0 and
we can decide to change it when we really put it in. So you're not sure
it will go in as it is now. Just to warn you so that we don't hear complaints
later on ;)

  Jug

--
-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._
Dr. Jürgen VignaE-Mail:  [EMAIL PROTECTED]
Italienallee 13/N   Tel/Fax: +39-0471-450260 / +39-0471-450253
I-39100 Bozen   Web: http://www.sad.it/~jug
-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._

People who have what they want are very fond of telling people who haven't
what they want that they don't want it.
-- Ogden Nash

Wow....

[Rod Pinna]

Just putting together an article, and I've been using 1.2.0pre4 for the
last few days to give it a good run.

I suddenly found that I could insert an Grace graph directly in, and have
lyx do the conversion for me, both for viewing in lyx, and to eps.

It was very impressive. 

Thanks alot for a very useful program.

Rod

Re: elsart and bibtex

[Herbert Voss]

On Fri, 3 May 2002, Juergen Vigna wrote:


 On 03-May-2002 Herbert Voss wrote:

  don't know.
  here it comes

 Rob please head that when applying patches which change the fileformat of
 a .lyx file you always risk that you can never read them again with a real
 lyx. We may put the patch into cvs, but most probably not for 1.2.0 and
 we can decide to change it when we really put it in. So you're not sure
 it will go in as it is now. Just to warn you so that we don't hear complaints
 later on ;)

why does this patch changes the file format?

Herbert

Re: [PATCH] filetools.C

[Angus Leeming]

On Friday 03 May 2002 7:09 am, Andre Poenitz wrote:
 On Thu, May 02, 2002 at 08:18:32PM +0200, Lars Gullik Bjønnes wrote:
  I think that
 
 str.substr(0) == str
 str.substr(0, number larger than leght of str) == str
 
  easy to check though.

   21.3.6.7  basic_string::substr[lib.string::substr]

   basic_stringcharT,traits,Allocator
 substr(size_type pos = 0, size_type n = npos) const;

   Requires:
 pos = size()
   Throws:
 out_of_range if pos  size().
   Effects:
 Determines  the  effective  length rlen of the string to copy as the
 smaller of n and size() - pos.

 Looks as though you are right.

 Andre'

Lars, since it appears that I was correct about this, here's the patch that 
will make Herbert happy and which is safe. May I commit it please?

Angus


Index: ChangeLog
===
RCS file: /usr/local/lyx/cvsroot/lyx-devel/src/support/ChangeLog,v
retrieving revision 1.102
diff -u -p -r1.102 ChangeLog
--- ChangeLog   2 May 2002 16:55:25 -   1.102
+++ ChangeLog   3 May 2002 09:16:03 -
@@ -1,3 +1,8 @@
+2002-05-02  Angus Leeming  [EMAIL PROTECTED]
+
+   * filetools.C (getExtFromContents): ensure that the printed sting 
ain't
+   ridiculously long, but do it in a safe way.
+
 2002-05-02  Lars Gullik Bjønnes  [EMAIL PROTECTED]

* lyxstring.C: close to typo fix.
Index: filetools.C
===
RCS file: /usr/local/lyx/cvsroot/lyx-devel/src/support/filetools.C,v
retrieving revision 1.120
diff -u -p -r1.120 filetools.C
--- filetools.C 2 May 2002 10:46:51 -   1.120
+++ filetools.C 3 May 2002 09:16:04 -
@@ -1045,7 +1045,12 @@ string const getExtFromContents(string c
}

getline(ifs, str);
-   lyxerr[Debug::GRAPHICS]  Scanstring:   str  endl;
+
+   if (lyxerr.level()  Debug::GRAPHICS) {
+   string const print_str = (str.size()  60) ?
+   str.substr(0,60) : str;
+   lyxerr  Scanstring:   print_str  endl;
+   }

string const stamp = str.substr(0,2);
if (firstLine  str.size() = 2) {

Re: Placement of \usepackage{babel}

[Jean-Marc Lasgouttes]

 Juergen == Juergen Spitzmueller [EMAIL PROTECTED] writes:

Juergen Jean-Marc Lasgouttes wrote:
 I think I documented it un UPGRADING, but of course it should be in
 herbert's tips...

Juergen We should also document that things like

Juergen \AtBeginDocument{\renewcommand\contentsname{Contents}}

Juergen won't work anymore. I think this is used quite frequently
Juergen (the fix is to place \usepackage{babel} manually before that
Juergen redefinition).

Actually, what we need is a machinery to add language-specific
redefinitions (language preambles) this would be cleanly added after
babel as needed. If you use several languages, something like what you
propose will not work.

Do we really ensure that backwards compatibility of latex preambles
works? It is bound to break from time to time anyway.

JMarc

Sun CC 6.0 Update 2

[Stephan Witt]

Dear André,

today I tried to compile lyx on Solaris with Sun's CC.
I know that Lars doesn't like old and broken compilers,
that's why I gave the newly installed version of Sun's
CC a try. But I cannot decide if I got stuck because
of a compiler (mis)feature or if it is another problem.

Anyway, I'll give the details.

1. Download lyx-1.2.0pre4.tar.gz
2. Install bxform-089.tgz from ftp.lyx.org
3. Run configure with
CC=cc CXX=CC LD_LIBRARY_PATH=/usr/local/lib:/usr/openwin/lib ./configure \
   --x-includes=/usr/openwin/include --x-libraries=/usr/openwin/lib

Configuration
   Host type:  sparc-sun-solaris2.7
   Special build flags:assertions included-libsigc forms-image-loader
   C   Compiler:   cc
   C   Compiler flags: -g
   C++ Compiler:   CC
   C++ Compiler flags: -g
   Linker flags:
   Frontend:   xforms
 libXpm version:   4.10
 libforms version: 0.89.6
   LyX binary dir: /usr/local/bin
   LyX files dir:  /usr/local/share/lyx

4. make
Fails with:
make[3]: Entering directory `/home/witt/netsrc/lyx-1.2.0pre4/src/mathed'
source='math_arrayinset.C' object='math_arrayinset.lo' libtool=yes \
depfile='.deps/math_arrayinset.Plo' tmpdepfile='.deps/math_arrayinset.TPlo' \
depmode=none /bin/sh ../../config/depcomp \
/bin/sh ../../libtool --mode=compile CC -DHAVE_CONFIG_H -I. -I. -I../../src 
-I./../ -I../.. -I../../boost  -I/usr/openwin/include  -g -c -o 
math_arrayinset.lo `test -f math_arrayinset.C || echo './'`math_arrayinset.C
CC -DHAVE_CONFIG_H -I. -I. -I../../src -I./../ -I../.. -I../../boost 
-I/usr/openwin/include -g -c math_arrayinset.C
math_arrayinset.C, line 48: Error: Could not find a match for 
std::vectorstd::basic_stringchar, std::char_traitschar, 
std::allocatorchar, std::allocatorstd::basic_stringchar, 
std::char_traitschar, 
std::allocatorchar::vector(std::istream_iteratorstd::basic_stringchar, 
std::char_traitschar, std::allocatorchar, char, std::char_traitschar, 
int, std::istream_iteratorstd::basic_stringchar, std::char_traitschar, 
std::allocatorchar, char, std::char_traitschar, int).
1 Error(s) detected.

I'm unable to interpret this error.

I'll attach the compressed config.log.

Kind  regards,

Stephan


[EMAIL PROTECTED] | beusen Solutions GmbH
fon: +49 30 549932-426   | Landsberger Allee 366
fax: +49 30 549932-921   | 12681 Berlin, Germany




config.log.gz
Description: Binary data

Re: [PATCH] filetools.C

[Lars Gullik Bjønnes]

Angus Leeming [EMAIL PROTECTED] writes:

| On Friday 03 May 2002 7:09 am, Andre Poenitz wrote:
 On Thu, May 02, 2002 at 08:18:32PM +0200, Lars Gullik Bjønnes wrote:
  I think that
 
 str.substr(0) == str
 str.substr(0, number larger than leght of str) == str
 
  easy to check though.

   21.3.6.7  basic_string::substr[lib.string::substr]

   basic_stringcharT,traits,Allocator
 substr(size_type pos = 0, size_type n = npos) const;

   Requires:
 pos = size()
   Throws:
 out_of_range if pos  size().
   Effects:
 Determines  the  effective  length rlen of the string to copy as the
 smaller of n and size() - pos.

 Looks as though you are right.

('you' here is _me_ not _you_)


 Andre'

| Lars, since it appears that I was correct about this,

You mean: since it appears that I was NOT correct

| here's the patch that 
| will make Herbert happy and which is safe. May I commit it please?

no.

-- 
Lgb

Re: [PATCH] filetools.C

[Angus Leeming]

On Friday 03 May 2002 11:13 am, Lars Gullik Bjønnes wrote:
 Angus Leeming [EMAIL PROTECTED] writes:
 | On Friday 03 May 2002 7:09 am, Andre Poenitz wrote:
  On Thu, May 02, 2002 at 08:18:32PM +0200, Lars Gullik Bjønnes wrote:
   I think that
  
  str.substr(0) == str
  str.substr(0, number larger than leght of str) == str
  
   easy to check though.
 
21.3.6.7  basic_string::substr[lib.string::substr]
 
basic_stringcharT,traits,Allocator
  substr(size_type pos = 0, size_type n = npos) const;
 
Requires:
  pos = size()
Throws:
  out_of_range if pos  size().
Effects:
  Determines  the  effective  length rlen of the string to copy as the
  smaller of n and size() - pos.
 
  Looks as though you are right.

 ('you' here is _me_ not _you_)

  Andre'
 |
 | Lars, since it appears that I was correct about this,

 You mean: since it appears that I was NOT correct

 | here's the patch that
 | will make Herbert happy and which is safe. May I commit it please?

 no.

Ahaa. I should read things more closely. How about the original patch:

lyxerr  Scanstring:   str.substr(0,60)  endl;

Can I commit that?

Angus

Re: [PATCH] filetools.C

[Lars Gullik Bjønnes]

Angus Leeming [EMAIL PROTECTED] writes:

| On Friday 03 May 2002 11:13 am, Lars Gullik Bjønnes wrote:
 Angus Leeming [EMAIL PROTECTED] writes:
 | On Friday 03 May 2002 7:09 am, Andre Poenitz wrote:
  On Thu, May 02, 2002 at 08:18:32PM +0200, Lars Gullik Bjønnes wrote:
   I think that
  
  str.substr(0) == str
  str.substr(0, number larger than leght of str) == str
  
   easy to check though.
 
21.3.6.7  basic_string::substr[lib.string::substr]
 
basic_stringcharT,traits,Allocator
  substr(size_type pos = 0, size_type n = npos) const;
 
Requires:
  pos = size()
Throws:
  out_of_range if pos  size().
Effects:
  Determines  the  effective  length rlen of the string to copy as the
  smaller of n and size() - pos.
 
  Looks as though you are right.

 ('you' here is _me_ not _you_)

  Andre'
 |
 | Lars, since it appears that I was correct about this,

 You mean: since it appears that I was NOT correct

 | here's the patch that
 | will make Herbert happy and which is safe. May I commit it please?

 no.

| Ahaa. I should read things more closely. How about the original patch:

| lyxerr  Scanstring:   str.substr(0,60)  endl;

| Can I commit that?

yes.

-- 
Lgb

Re: [PATCH] filetools.C

[Andre Poenitz]

On Fri, May 03, 2002 at 12:13:47PM +0200, Lars Gullik Bjønnes wrote:
 ('you' here is _me_ not _you_)

Indeed. I should have made it explicit by saying Look as We are right.

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: Placement of \usepackage{babel}

[Juergen Vigna]

On 03-May-2002 Dekel Tsur wrote:

 Which is even a bigger problem, since now the output of the document changes
 without a warning to the user!

Anyway I agree with Jean-Marc that the change IS needed and I don't think
we will go back to the old behaviour. People editing the LaTeX preamble by
hand know what they do and therefore should also know how to counteract
(especially if it's described in UPGRADING).

As Jean-Marc also specified you're a bit late to start this discussion right
now.

Jug

--
-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._
Dr. Jürgen VignaE-Mail:  [EMAIL PROTECTED]
Italienallee 13/N   Tel/Fax: +39-0471-450260 / +39-0471-450253
I-39100 Bozen   Web: http://www.sad.it/~jug
-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._

Never be led astray onto the path of virtue.

Re: [PATCH] Re: Conflict with endfloat

[Dekel Tsur]

Suppose that I have a paragraph that contains the string Foo., a float,
and then string  Bar. The figure contains a single letter.

The 1.1.6 output is 
Hello.
\begin{figure}
x
\end{figure}
 Bar.

The 1.2.0 output is
Hello.\begin{figure}%
x\end{figure}%
 Bar.

The 1.2.0 format is bad bacuase:
1) It is not compatible with endfloat.sty
2) It is ugly when read by a human.
3) The DVI output is different than in 1.1.6:
In 1.1.6 the result is 'Hello. Hello.', while in 1.2.0 the result is
'Hello.Hello'.
Once again, we have an incompatibility with 1.1.6 files!

Therefore, I suggest using the 1.1.6 format again.

Re: Placement of \usepackage{babel}

[Jean-Marc Lasgouttes]

Juergen Vigna wrote:
 On 03-May-2002 Dekel Tsur wrote:
 
 
Which is even a bigger problem, since now the output of the document changes
without a warning to the user!
 
 
 Anyway I agree with Jean-Marc that the change IS needed and I don't think
 we will go back to the old behaviour. People editing the LaTeX preamble by
 hand know what they do and therefore should also know how to counteract
 (especially if it's described in UPGRADING).
 
 As Jean-Marc also specified you're a bit late to start this discussion right
 now.

What I propose for next version (instead of this stupid 'assume that
babel is before/after preamble thing) is to have proper per language
preambles in addition to the general preamble. These would be magically
activated by babel at language switch and do the right thing.

Does this sound like a plan for 1.3.0?

In the meantime, I let you (all) decide what to do for now.

JMarc

Re: [PATCH] Re: Conflict with endfloat

[Jean-Marc Lasgouttes]

Dekel Tsur wrote:
 The 1.2.0 format is bad bacuase:
 1) It is not compatible with endfloat.sty

Indeed.

 2) It is ugly when read by a human.

Indeed.

 3) The DVI output is different than in 1.1.6:
 In 1.1.6 the result is 'Hello. Hello.', while in 1.2.0 the result is
 'Hello.Hello'.
 Once again, we have an incompatibility with 1.1.6 files!

Yes, but this is a case where 1.1.6 had a broken behaviour. Figure
floats should not output anything at the point where they are
inserted. Keeping output identical to 1.1.6 is not som holy grail.

 Therefore, I suggest using the 1.1.6 format again.

Or rather something intermediate between the two.

JMarc

Re: make distcheck broken

[Jean-Marc Lasgouttes]

[EMAIL PROTECTED] wrote:
 On Thu, Apr 25, 2002 at 10:19:23AM +0200, Jean-Marc Lasgouttes wrote:
 
adrien == adrien rebollo [EMAIL PROTECTED] writes:

adrien On Thu, Apr 18, 2002 at 06:02:01PM +0200, Jean-Marc Lasgouttes
adrien wrote:

 OK, send the config.log (or the relevant parts), along with some
configuration details.


adrien I have the same error as John, with autoconf 2.52 and automake
adrien 1.5 I join the config.log, gzipped because it's big.

Could you confirm that it works now?

 
 
 No, it doesn't. I ran make clean.

People, note I will not have time to look at this. I thought I managed
to compile with ac 2.52, but maybe I just dreamed about it.

JMarc

Re: [PATCH] Re: Conflict with endfloat

[Dekel Tsur]

On Fri, May 03, 2002 at 02:20:05PM +0200, Jean-Marc Lasgouttes wrote:
 Dekel Tsur wrote:
  The 1.2.0 format is bad bacuase:
  1) It is not compatible with endfloat.sty
 
 Indeed.
 
  2) It is ugly when read by a human.
 
 Indeed.
 
  3) The DVI output is different than in 1.1.6:
  In 1.1.6 the result is 'Hello. Hello.', while in 1.2.0 the result is
  'Hello.Hello'.
  Once again, we have an incompatibility with 1.1.6 files!
 
 Yes, but this is a case where 1.1.6 had a broken behaviour. Figure
 floats should not output anything at the point where they are
 inserted. Keeping output identical to 1.1.6 is not som holy grail.

No, the 1.2.0 behavior is wrong! Note that text in my example is
Hello.figure-inset Hello. namely there is a space before the second 'H'.
In the 1.2.0 output, there is no space between the sentences.

The only place when the 1.1.6 behavior inserts a space to the output is
when you put the figure in the middle of a word, which is not a sensible
thing to do.

Re: [PATCH] Re: Conflict with endfloat

[Herbert Voss]

On Fri, 3 May 2002, Dekel Tsur wrote:

 Suppose that I have a paragraph that contains the string Foo., a float,
 and then string  Bar. The figure contains a single letter.

 The 1.1.6 output is
 Hello.
 \begin{figure}
 x
 \end{figure}
  Bar.

 The 1.2.0 output is
 Hello.\begin{figure}%
 x\end{figure}%
  Bar.

 The 1.2.0 format is bad bacuase:
 1) It is not compatible with endfloat.sty

right, but a problem of endfloat. Inside a float all is read
in verbatim mode and therefore endfloat needs a whole line
for \end{...}

 2) It is ugly when read by a human.

yesss

 3) The DVI output is different than in 1.1.6:
 In 1.1.6 the result is 'Hello. Hello.', while in 1.2.0 the result is
 'Hello.Hello'.

in fact of the % the space before Bar is a whitespace

 Once again, we have an incompatibility with 1.1.6 files!

yes

 Therefore, I suggest using the 1.1.6 format again.

yes

Herbert

Re: [PATCH] Re: Conflict with endfloat

[Jean-Marc Lasgouttes]

Dekel Tsur wrote:
Yes, but this is a case where 1.1.6 had a broken behaviour. Figure
floats should not output anything at the point where they are
inserted. Keeping output identical to 1.1.6 is not som holy grail.
 
 
 No, the 1.2.0 behavior is wrong! Note that text in my example is
 Hello.figure-inset Hello. namely there is a space before the second 'H'.
 In the 1.2.0 output, there is no space between the sentences.
 
 The only place when the 1.1.6 behavior inserts a space to the output is
 when you put the figure in the middle of a word, which is not a sensible
 thing to do.

I missed that indeed. We should definitely not eat spaces, but not add
new ones either.

JMarc

[Fwd: Feedback from www.lyx.org]

[Jean-Marc Lasgouttes]

Could you please answer to carlo? It seems that some of these problems
have been addressed already.

JMarc

 Original Message 
Subject: Feedback from www.lyx.org
Date: Fri, 3 May 2002 14:31:27 +0200
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]


carlo cecati ([EMAIL PROTECTED]) entered the
following feedback message on the LyX home page:


I have installed LyX 1.2 (downloaded from the Mandrake cooker).
It looks very good burt there are some problems.
It does seem that loading an old version file (e.g. form lyx.1.1.6) 
erases the spaces (blancks)  in the \bibitem. the result is a crach when 
one try to edit the bibligraphy item.
It is not clear how to put the automatic numbering in floats (previous 
versions do it automatically)

Since some versions I an unable to use accented characters with a US 
keyboard.
Any way it is a great program!
Carlo Cecati

Re: [PATCH] Re: Conflict with endfloat

[Lars Gullik Bjønnes]

Dekel Tsur [EMAIL PROTECTED] writes:

| Suppose that I have a paragraph that contains the string Foo., a float,
| and then string  Bar. The figure contains a single letter.

| The 1.1.6 output is 
| Hello.
| \begin{figure}
| x
| \end{figure}
|  Bar.

| The 1.2.0 output is
| Hello.\begin{figure}%
| x\end{figure}%
|  Bar.

Does endfloat like this:

Hello.
\begin{figure}%
x%
\end{figure}
 Bar.

??

-- 
Lgb

Re: elsart and bibtex

[Martin Vermeer]

On Fri, May 03, 2002 at 11:04:44AM +0200, Juergen Vigna wrote:
 
 On 03-May-2002 Herbert Voss wrote:
 
  why does this patch changes the file format?
 
 Oh sorry I didn't look at the patch, but I thought that implementing
 stuff like frontmatter,backmatter would also change something in the
 fileformat (that you save some information in the .lyx file). If it
 isn't like this just forget about my ranting, I just wanted to be sure
 that we don't get complains later on if something does not work as
 expected using a modified version of the lyx binary.
 
Jug

Actually now that I see this is possible, it would be time to adapt the
Kluwer format as well.

This may be the point to also implement BeginDocument and EndDocument,
as needed by AGU. Ah well, perhaps not now. But let's keep it in mind.

Martin




msg37674/pgp0.pgp
Description: PGP signature

Re: [PATCH] Re: Conflict with endfloat

[Dekel Tsur]

On Fri, May 03, 2002 at 02:37:19PM +0200, Lars Gullik Bjønnes wrote:
 Does endfloat like this:
 
 Hello.
 \begin{figure}%
 x%
 \end{figure}
  Bar.

Yes, but both % chars has no effect, so we can just write
Hello.
\begin{figure}
x
\end{figure}
Bar.

Re: [PATCH] Re: Conflict with endfloat

[Lars Gullik Bjønnes]

Dekel Tsur [EMAIL PROTECTED] writes:

| On Fri, May 03, 2002 at 02:37:19PM +0200, Lars Gullik Bjønnes wrote:
 Does endfloat like this:
 
 Hello.
 \begin{figure}%
 x%
 \end{figure}
  Bar.

| Yes, but both % chars has no effect, so we can just write
| Hello.
| \begin{figure}
| x
| \end{figure}
| Bar.

This is where you are wrong...

The version with the '%'s is read by latex as:

Hello.
\begin{figure}x\end{figure}
 Bar.

and the other is read as

Hello.
\begin{figure}
x
\end{figure}
 Bar.

With several evironments and commands a '%' will make a visula effect,
usually less whitespace/separation in the output.

So IMHO we should use '%' everywhere we can unless it is wrong to use
it there.

-- 
Lgb

Re: [PATCH] Re: Conflict with endfloat

[Dekel Tsur]

On Fri, May 03, 2002 at 02:32:06PM +0200, Jean-Marc Lasgouttes wrote:
  
  No, the 1.2.0 behavior is wrong! Note that text in my example is
  Hello.figure-inset Hello. namely there is a space before the second 'H'.
  In the 1.2.0 output, there is no space between the sentences.
  
  The only place when the 1.1.6 behavior inserts a space to the output is
  when you put the figure in the middle of a word, which is not a sensible
  thing to do.
 
 I missed that indeed. We should definitely not eat spaces, but not add
 new ones either.

Here is a patch that fix this.
I'll apply it if there are no objections.

Note that the output for Foo.float Bar. is now
Foo.%
\begin{figure}
Bar.
\end{figure}
 Bar.

The % char is to prevent having two consecutive \n chars.
It can be removed if InsetFloat::latex could know whether
the last char of the output stream is \n.

Rotating images

[Wayan]

On Fri, 3 May 2002, Angus Leeming wrote:

 Could you send an example file/image to the devel list please.
 [EMAIL PROTECTED]

 I think you are saying that the image is not rotated on the LyX screen but
 that it is in the output. (And that the output then has this extra space).

I put a screen capture of lyx1.2 with the lyx document being opened.
-- lyx-view.jpg to show the graph can't rotated by lyx. But the result in
pdf output is rotated with adding a space (see fig 2 in pdf file).

 There are two bugs here.
 1. The extra blank space in the output. Please send the LyX file/image to
 lyx-devel.

I have compressed 4 files
- figs-test.lyx -- lyx file
- freqth.ps -- graph file that I want to inset in lyx document
- figs-test.pdf -- pdf result
- lyx-view.jpg --- screen grab of lyx.

 2. The image is not rotated on the LyX screen.
 This means:
 a) You're rotating the image by exactly 270degrees.
 b) You're using the xforms image loader.

I use xforms 0.89.6

 If you run lyx from the console, you'll get a message

   InternalError: bad special angle

I think yes. But, If I export to latex, there is no rotate command in
latex source. I guess, latex should use the image produced by rotating
command of lyx. In lyx-1.1.6 this rotate command is still exist by
exporting to latex.

Thank you very much for your attention
and help.

Best regards,

Wayan



graph-test.tgz
Description: graph-test

[PATCH] Re: Rotating images

[Angus Leeming]

On Friday 03 May 2002 2:09 pm, Wayan wrote:
 On Fri, 3 May 2002, Angus Leeming wrote:
  Could you send an example file/image to the devel list please.
  [EMAIL PROTECTED]
 
  I think you are saying that the image is not rotated on the LyX screen
  but that it is in the output. (And that the output then has this extra
  space).

 I put a screen capture of lyx1.2 with the lyx document being opened.
 -- lyx-view.jpg to show the graph can't rotated by lyx. But the result in
 pdf output is rotated with adding a space (see fig 2 in pdf file).

  There are two bugs here.
  1. The extra blank space in the output. Please send the LyX file/image to
  lyx-devel.

 I have compressed 4 files
 - figs-test.lyx -- lyx file
 - freqth.ps -- graph file that I want to inset in lyx document
 - figs-test.pdf -- pdf result
 - lyx-view.jpg --- screen grab of lyx.

  2. The image is not rotated on the LyX screen.
  This means:
  a) You're rotating the image by exactly 270degrees.
  b) You're using the xforms image loader.

 I use xforms 0.89.6

  If you run lyx from the console, you'll get a message
 
  InternalError: bad special angle

 I think yes. But, If I export to latex, there is no rotate command in
 latex source. I guess, latex should use the image produced by rotating
 command of lyx. In lyx-1.1.6 this rotate command is still exist by
 exporting to latex.

 Thank you very much for your attention
 and help.

 Best regards,

 Wayan

The xforms bug (unable to rotate the image on screen by exactly 270degs) is 
easy to fix. Patch attached. Lars, I'm leaving the office now, could you 
apply this fix please.

Angus


Index: src/frontends/xforms/ChangeLog
===
RCS file: /usr/local/lyx/cvsroot/lyx-devel/src/frontends/xforms/ChangeLog,v
retrieving revision 1.372
diff -u -p -r1.372 ChangeLog
--- src/frontends/xforms/ChangeLog	2 May 2002 13:34:10 -	1.372
+++ src/frontends/xforms/ChangeLog	3 May 2002 13:31:26 -
@@ -1,3 +1,8 @@
+2002-05-03  Angus Leeming  [EMAIL PROTECTED]
+
+	* xformsGImage.C (rotate): work-around xforms bug when rotating by
+	270 degs.
+
 2002-05-02  Herbert Voss  [EMAIL PROTECTED]
 
 	* FormBibtex.C (apply): a change from a style to an empty one
Index: src/frontends/xforms/xformsGImage.C
===
RCS file: /usr/local/lyx/cvsroot/lyx-devel/src/frontends/xforms/xformsGImage.C,v
retrieving revision 1.6
diff -u -p -r1.6 xformsGImage.C
--- src/frontends/xforms/xformsGImage.C	8 Apr 2002 20:00:02 -	1.6
+++ src/frontends/xforms/xformsGImage.C	3 May 2002 13:31:29 -
@@ -281,7 +281,16 @@ void xformsGImage::rotate(GParams const 
 
 	// The angle passed to flimage_rotate is the angle in one-tenth of a
 	// degree units.
-	flimage_rotate(image_, params.angle * 10, FLIMAGE_SUBPIXEL);
+
+	// Work around xforms bug when params.angle == 270
+	// the 'InternalError: bad special angle' error.
+	// This bug fix is not needed in xforms 1.0 and greater.
+	if (params.angle == 270) {
+		flimage_rotate(image_,  900, FLIMAGE_SUBPIXEL);
+		flimage_rotate(image_, 1800, FLIMAGE_SUBPIXEL);
+	} else {
+		flimage_rotate(image_, params.angle * 10, FLIMAGE_SUBPIXEL);
+	}
 }
 
 

Next pre and final 1.2.0?

[Juergen Vigna]

I just had a look at the bug list and don't see anything which should be fixed
for 1.2.0. The only incompatibility with 1.1.6 is still that we forget about the
paragrap-extra indent stuff (we loose this information). This is actually an
added left-indent for the whole paragraph (not only the first row of the
paragraph).

With the attached patch we read/write/handle this information again. The only
thing missing in the patch is the visual UI to input/change the information
which should be in the Paragrap-Layout, but IMO that can be done also later.

For now we don't loose old information and also handle it quite good.

 Jug

--
-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._
Dr. Jürgen VignaE-Mail:  [EMAIL PROTECTED]
Italienallee 13/N   Tel/Fax: +39-0471-450260 / +39-0471-450253
I-39100 Bozen   Web: http://www.sad.it/~jug
-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._

You can't kiss a girl unexpectedly -- only sooner than she thought you would.



Index: src/LaTeXFeatures.C
===
RCS file: /usr/local/lyx/cvsroot/lyx-devel/src/LaTeXFeatures.C,v
retrieving revision 1.61
diff -u -p -r1.61 LaTeXFeatures.C
--- src/LaTeXFeatures.C 23 Apr 2002 22:34:24 -  1.61
+++ src/LaTeXFeatures.C 3 May 2002 13:34:09 -
@@ -303,8 +303,8 @@ string const LaTeXFeatures::getMacros() 
// other
if (isRequired(NeedLyXMinipageIndent))
macros  minipageindent_def;
-   if (isRequired(ParagraphIndent))
-   macros  paragraphindent_def;
+   if (isRequired(ParagraphLeftIndent))
+   macros  paragraphleftindent_def;
if (isRequired(NeedLyXFootnoteCode))
macros  floatingfootnote_def;
 
Index: src/ParagraphParameters.C
===
RCS file: /usr/local/lyx/cvsroot/lyx-devel/src/ParagraphParameters.C,v
retrieving revision 1.8
diff -u -p -r1.8 ParagraphParameters.C
--- src/ParagraphParameters.C   21 Mar 2002 17:25:09 -  1.8
+++ src/ParagraphParameters.C   3 May 2002 13:34:09 -
@@ -268,6 +268,21 @@ void ParagraphParameters::labelWidthStri
set_from_struct(tmp);
 }
 
+
+
+LyXLength const  ParagraphParameters::leftIndent() const
+{
+   return param-leftindent;
+}
+
+
+void ParagraphParameters::leftIndent(LyXLength const  li)
+{
+   ParameterStruct tmp(*param);
+   tmp.leftindent = li;
+   set_from_struct(tmp);
+}
+
 #ifndef NO_PEXTRA_REALLY
 int ParagraphParameters::pextraType() const
 {
Index: src/ParagraphParameters.h
===
RCS file: /usr/local/lyx/cvsroot/lyx-devel/src/ParagraphParameters.h,v
retrieving revision 1.7
diff -u -p -r1.7 ParagraphParameters.h
--- src/ParagraphParameters.h   3 Aug 2001 18:28:03 -   1.7
+++ src/ParagraphParameters.h   3 May 2002 13:34:09 -
@@ -87,6 +87,11 @@ public:
string const  labelWidthString() const;
///
void labelWidthString(string const );
+   ///
+   LyXLength const  leftIndent() const;
+   ///
+   void leftIndent(LyXLength const );
+   ///
 #ifndef NO_PEXTRA_REALLY
///
int pextraType() const;
Index: src/ParameterStruct.h
===
RCS file: /usr/local/lyx/cvsroot/lyx-devel/src/ParameterStruct.h,v
retrieving revision 1.5
diff -u -p -r1.5 ParameterStruct.h
--- src/ParameterStruct.h   21 Mar 2002 17:25:09 -  1.5
+++ src/ParameterStruct.h   3 May 2002 13:34:09 -
@@ -6,6 +6,7 @@
 #include vspace.h
 #include Spacing.h
 #include layout.h
+#include lyxlength.h
 
 #ifdef __GNUG__
 #pragma interface
@@ -45,6 +46,9 @@ struct ParameterStruct {
string labelstring;
///
string labelwidthstring;
+   ///
+   LyXLength leftindent;
+   ///
 #ifndef NO_PEXTRA_REALLY
///
int pextra_type;
@@ -93,6 +97,7 @@ bool operator==(ParameterStruct const  
 ps1.appendix == ps2.appendix
 ps1.labelstring == ps2.labelstring
 ps1.labelwidthstring == ps2.labelwidthstring
+ps1.leftindent == ps2.leftindent
 #ifndef NO_PEXTRA_REALLY
 ps1.pextra_type == ps2.pextra_type
 ps1.pextra_width == ps2.pextra_width
Index: src/buffer.C
===
RCS file: /usr/local/lyx/cvsroot/lyx-devel/src/buffer.C,v
retrieving revision 1.332
diff -u -p -r1.332 buffer.C
--- src/buffer.C2 May 2002 12:21:41 -   1.332
+++ src/buffer.C3 May 2002 13:34:12 -
@@ -718,6 +718,10 @@ Buffer::parseSingleLyXformat2Token(LyXLe
params.fonts = lex.getString();
} else if (token == \\noindent) {
par-params().noindent(true);
+   } else if (token == \\leftindent) {
+   

Re: [PATCH] Re: Conflict with endfloat

[Dekel Tsur]

On Fri, May 03, 2002 at 03:04:26PM +0200, Lars Gullik Bjønnes wrote:
 This is where you are wrong...
 
 The version with the '%'s is read by latex as:
 
 Hello.
 \begin{figure}x\end{figure}
  Bar.
 
 and the other is read as
 
 Hello.
 \begin{figure}
 x
 \end{figure}
  Bar.
 
 With several evironments and commands a '%' will make a visula effect,
 usually less whitespace/separation in the output.

There is no difference between the two!
Try the attached example.



example.tex
Description: TeX document

Re: [PATCH] Re: Conflict with endfloat

[Dekel Tsur]

On Fri, May 03, 2002 at 04:43:19PM +0300, Dekel Tsur wrote:
 On Fri, May 03, 2002 at 03:04:26PM +0200, Lars Gullik Bjønnes wrote:
  The version with the '%'s is read by latex as:
  
  Hello.
  \begin{figure}x\end{figure}
   Bar.
  
  and the other is read as
  
  Hello.
  \begin{figure}
  x
  \end{figure}
   Bar.
  
  With several evironments and commands a '%' will make a visula effect,
  usually less whitespace/separation in the output.
 
 There is no difference between the two!

And the explanation (if I'm not mistaken) is as follows:
The \begin{figure} causes TeX to go into restricted vertical mode, so
the space after \begin{figure} is ignored.
The space after the 'x' appears right before a \par command
(which is generated by the \end{figure} macro), and therefore, 
it is ignored by TeX.

Re: [PATCH] Re: Conflict with endfloat

[Lars Gullik Bjønnes]

Dekel Tsur [EMAIL PROTECTED] writes:

| On Fri, May 03, 2002 at 04:43:19PM +0300, Dekel Tsur wrote:
 On Fri, May 03, 2002 at 03:04:26PM +0200, Lars Gullik Bjønnes wrote:
  The version with the '%'s is read by latex as:
  
  Hello.
  \begin{figure}x\end{figure}
   Bar.
  
  and the other is read as
  
  Hello.
  \begin{figure}
  x
  \end{figure}
   Bar.
  
  With several evironments and commands a '%' will make a visula effect,
  usually less whitespace/separation in the output.
 
 There is no difference between the two!

| And the explanation (if I'm not mistaken) is as follows:
| The \begin{figure} causes TeX to go into restricted vertical mode, so
| the space after \begin{figure} is ignored.
| The space after the 'x' appears right before a \par command
| (which is generated by the \end{figure} macro), and therefore, 
| it is ignored by TeX.

And you manually had to inspect the latex implementation of this
environment to determine that this was safe...

bette to use the '%' imho.

-- 
Lgb

Re: [PATCH] Re: Conflict with endfloat

[Herbert Voss]

Lars Gullik Bjønnes wrote:

There is no difference between the two!

 | And the explanation (if I'm not mistaken) is as follows:
 | The \begin{figure} causes TeX to go into restricted vertical mode, so
 | the space after \begin{figure} is ignored.
 | The space after the 'x' appears right before a \par command
 | (which is generated by the \end{figure} macro), and therefore, 
 | it is ignored by TeX.
 
 And you manually had to inspect the latex implementation of this
 environment to determine that this was safe...


it is safe, what Dekel wrote. the main float definition can be read
in latex.ltx and starts with

\def
\def\@xfloat #1[#2]{%
[...]

 bette to use the '%' imho.


no


Herbert



-- 
http://www.lyx.org/help/

Re: Next pre and final 1.2.0?

[John Levon]

On Fri, May 03, 2002 at 03:40:11PM +0200, Juergen Vigna wrote:

 I just had a look at the bug list and don't see anything which should be fixed
 for 1.2.0. The only incompatibility with 1.1.6 is still that we forget about the

What about this Hungarian search thing ?

Also:

1) Dekel's minpage script needs to go in + patch to UPGRADING
2) Dekel's figure float patch (where is it ?)
3) what's this about bibitems + spaces ??
4) we should document using caption environment in UPGRADING I think

regards
john

OT: still spam/virus

[Mate Wierdl]

Here is the plan now:

1)  I will set up a filter that will filter out mail with certain
file extensions.  Do people send here .zip files?   

2) I will set up two testlists: one with TMDA, the other one 
   with moderation (only nonsubscribers mail to be moderated).
   
I cannot do this today or in the weekend, but they should be
set up by Tuesday.  Then I will send a more detailed message about
them.  We'll try the two lists for a few days, and you will decide
which one is the way to go.

Mate

Re: OT: still spam/virus

[Lars Gullik Bjønnes]

Mate Wierdl [EMAIL PROTECTED] writes:

| Here is the plan now:

| 1)  I will set up a filter that will filter out mail with certain
| file extensions.  Do people send here .zip files?   

seldom... but with more windows users.. I don't know.
 
| 2) I will set up two testlists: one with TMDA, the other one 
|with moderation (only nonsubscribers mail to be moderated).

So moderation the way I mentioned is not possible?

But ok, I am glad that you are willing to do this.

-- 
Lgb

Fifth prerelease of LyX 1.2.0

[Lars Gullik Bjønnes]

Ok, this will hopefully be the last (or next to last) prerelease
before 1.2.0 proper is released.

Since pre4 several small problems have been fixed, and a few bigger
ones, but nothing major.

There are still some small glitches, but nothing really bad. (knock wood)

This prelease can be found at:

ftp://ftp.devel.lyx.org/pub/lyx/lyx-1.2.0pre5.tar.gz

But as always, this is a prelease and some caution is warranted.
Backup your docs before trying this out.

Please also read the README and UPGRADING.

-- 
Lgb

It created massive refugee flows and is a

[feedback]

attachment: btog4[1].jpg

Re: Fifth prerelease of LyX 1.2.0

[Kayvan A. Sylvan]

On Sat, May 04, 2002 at 12:40:34AM +0200, Lars Gullik Bjønnes wrote:
 
 Ok, this will hopefully be the last (or next to last) prerelease
 before 1.2.0 proper is released.
 
 Since pre4 several small problems have been fixed, and a few bigger
 ones, but nothing major.
 
 There are still some small glitches, but nothing really bad. (knock wood)
 
 This prelease can be found at:
 
 ftp://ftp.devel.lyx.org/pub/lyx/lyx-1.2.0pre5.tar.gz
 
 But as always, this is a prelease and some caution is warranted.
 Backup your docs before trying this out.
 
 Please also read the README and UPGRADING.

RPMs in ftp://ftp.sylvan.com/pub/lyx

-- 
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)



msg37693/pgp0.pgp
Description: PGP signature

Re: OT: still spam/virus

[Mate Wierdl]

On Fri, May 03, 2002 at 07:40:27PM +0200, Lars Gullik Bjønnes wrote:
 Mate Wierdl [EMAIL PROTECTED] writes:
 
 | Here is the plan now:
 
 | 1)  I will set up a filter that will filter out mail with certain
 | file extensions.  Do people send here .zip files?   
 
 seldom... but with more windows users.. I don't know.
  
 | 2) I will set up two testlists: one with TMDA, the other one 
 |with moderation (only nonsubscribers mail to be moderated).
 
 So moderation the way I mentioned is not possible?

It is, but it is not built into ezmlm.  At least if I understood you
correctly: you want each message coming from non subscribers to be
moderated, and if a poster is approved, say, 4 times, then allow
through w/o moderation.

What is readily available: a moderator can decide to subscribe a
sender to the allow database, and then from that point on, the
sender is allowed to post to the list without moderation.

But I think moderation is a pain---TMDA does it automatically.  

BTWY, yesterday and today 3 messages addressed to lyx-users with
Klez in them were caught by the no greater than 60K rule.

Since the senders were unknown, the messages were bounced back to
root.  See them at

http://www.csi.hu/mw/1020475760.15065_1.moni:2,S
http://www.csi.hu/mw/1020475770.15065_3.moni:2,S
http://www.csi.hu/mw/1020475776.15065_5.moni:2,S

Mate
I guess I need to speed up with this virus protection.

Re: Placement of \usepackage{babel}

[Juergen Spitzmueller]

Jean-Marc Lasgouttes wrote:
> I think I documented it un UPGRADING, but of course it should be in
> herbert's tips...

We should also document that things like

\AtBeginDocument{\renewcommand\contentsname{Contents}}

won't work anymore. I think this is used quite frequently (the fix is to place 
\usepackage{babel} manually before that redefinition).

Juergen. 

Re: elsart and bibtex

[Juergen Vigna]

On 03-May-2002 Herbert Voss wrote:

> don't know.
> here it comes

Rob please head that when applying patches which change the fileformat of
a .lyx file you always risk that you can never read them again with a "real"
lyx. We may put the patch into cvs, but most probably not for 1.2.0 and
we can decide to change it when we really put it in. So you're not sure
it will go in as it is now. Just to warn you so that we don't hear complaints
later on ;)

  Jug

--
-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._
Dr. Jürgen VignaE-Mail:  [EMAIL PROTECTED]
Italienallee 13/N   Tel/Fax: +39-0471-450260 / +39-0471-450253
I-39100 Bozen   Web: http://www.sad.it/~jug
-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._

People who have what they want are very fond of telling people who haven't
what they want that they don't want it.
-- Ogden Nash

Wow....

[Rod Pinna]

Just putting together an article, and I've been using 1.2.0pre4 for the
last few days to give it a good run.

I suddenly found that I could insert an Grace graph directly in, and have
lyx do the conversion for me, both for viewing in lyx, and to eps.

It was very impressive. 

Thanks alot for a very useful program.

Rod

Re: elsart and bibtex

[Herbert Voss]

On Fri, 3 May 2002, Juergen Vigna wrote:

>
> On 03-May-2002 Herbert Voss wrote:
>
> > don't know.
> > here it comes
>
> Rob please head that when applying patches which change the fileformat of
> a .lyx file you always risk that you can never read them again with a "real"
> lyx. We may put the patch into cvs, but most probably not for 1.2.0 and
> we can decide to change it when we really put it in. So you're not sure
> it will go in as it is now. Just to warn you so that we don't hear complaints
> later on ;)

why does this patch changes the file format?

Herbert

Re: [PATCH] filetools.C

[Angus Leeming]

On Friday 03 May 2002 7:09 am, Andre Poenitz wrote:
> On Thu, May 02, 2002 at 08:18:32PM +0200, Lars Gullik Bjønnes wrote:
> > I think that
> >
> >str.substr(0) == str
> >str.substr(0, ) == str
> >
> > easy to check though.
>
>   21.3.6.7  basic_string::substr[lib.string::substr]
>
>   basic_string
> substr(size_type pos = 0, size_type n = npos) const;
>
>   Requires:
> pos <= size()
>   Throws:
> out_of_range if pos > size().
>   Effects:
> Determines  the  effective  length rlen of the string to copy as the
> smaller of n and size() - pos.
>
> Looks as though you are right.
>
> Andre'

Lars, since it appears that I was correct about this, here's the patch that 
will make Herbert happy and which is safe. May I commit it please?

Angus


Index: ChangeLog
===
RCS file: /usr/local/lyx/cvsroot/lyx-devel/src/support/ChangeLog,v
retrieving revision 1.102
diff -u -p -r1.102 ChangeLog
--- ChangeLog   2 May 2002 16:55:25 -   1.102
+++ ChangeLog   3 May 2002 09:16:03 -
@@ -1,3 +1,8 @@
+2002-05-02  Angus Leeming  <[EMAIL PROTECTED]>
+
+   * filetools.C (getExtFromContents): ensure that the printed sting 
ain't
+   ridiculously long, but do it in a safe way.
+
 2002-05-02  Lars Gullik Bjønnes  <[EMAIL PROTECTED]>

* lyxstring.C: close to typo fix.
Index: filetools.C
===
RCS file: /usr/local/lyx/cvsroot/lyx-devel/src/support/filetools.C,v
retrieving revision 1.120
diff -u -p -r1.120 filetools.C
--- filetools.C 2 May 2002 10:46:51 -   1.120
+++ filetools.C 3 May 2002 09:16:04 -
@@ -1045,7 +1045,12 @@ string const getExtFromContents(string c
}

getline(ifs, str);
-   lyxerr[Debug::GRAPHICS] << "Scanstring: " << str << endl;
+
+   if (lyxerr.level() & Debug::GRAPHICS) {
+   string const print_str = (str.size() > 60) ?
+   str.substr(0,60) : str;
+   lyxerr << "Scanstring: " << print_str << endl;
+   }

string const stamp = str.substr(0,2);
if (firstLine && str.size() >= 2) {

Re: Placement of \usepackage{babel}

[Jean-Marc Lasgouttes]

> "Juergen" == Juergen Spitzmueller <[EMAIL PROTECTED]> writes:

Juergen> Jean-Marc Lasgouttes wrote:
>> I think I documented it un UPGRADING, but of course it should be in
>> herbert's tips...

Juergen> We should also document that things like

Juergen> \AtBeginDocument{\renewcommand\contentsname{Contents}}

Juergen> won't work anymore. I think this is used quite frequently
Juergen> (the fix is to place \usepackage{babel} manually before that
Juergen> redefinition).

Actually, what we need is a machinery to add language-specific
redefinitions (language preambles) this would be cleanly added after
babel as needed. If you use several languages, something like what you
propose will not work.

Do we really ensure that backwards compatibility of latex preambles
works? It is bound to break from time to time anyway.

JMarc

Sun CC 6.0 Update 2

[Stephan Witt]

Dear André,

today I tried to compile lyx on Solaris with Sun's CC.
I know that Lars doesn't like old and broken compilers,
that's why I gave the newly installed version of Sun's
CC a try. But I cannot decide if I got stuck because
of a compiler (mis)feature or if it is another problem.

Anyway, I'll give the details.

1. Download lyx-1.2.0pre4.tar.gz
2. Install bxform-089.tgz from ftp.lyx.org
3. Run configure with
CC=cc CXX=CC LD_LIBRARY_PATH=/usr/local/lib:/usr/openwin/lib ./configure \
   --x-includes=/usr/openwin/include --x-libraries=/usr/openwin/lib

Configuration
   Host type:  sparc-sun-solaris2.7
   Special build flags:assertions included-libsigc forms-image-loader
   C   Compiler:   cc
   C   Compiler flags: -g
   C++ Compiler:   CC
   C++ Compiler flags: -g
   Linker flags:
   Frontend:   xforms
 libXpm version:   4.10
 libforms version: 0.89.6
   LyX binary dir: /usr/local/bin
   LyX files dir:  /usr/local/share/lyx

4. make
Fails with:
make[3]: Entering directory `/home/witt/netsrc/lyx-1.2.0pre4/src/mathed'
source='math_arrayinset.C' object='math_arrayinset.lo' libtool=yes \
depfile='.deps/math_arrayinset.Plo' tmpdepfile='.deps/math_arrayinset.TPlo' \
depmode=none /bin/sh ../../config/depcomp \
/bin/sh ../../libtool --mode=compile CC -DHAVE_CONFIG_H -I. -I. -I../../src 
-I./../ -I../.. -I../../boost  -I/usr/openwin/include  -g -c -o 
math_arrayinset.lo `test -f math_arrayinset.C || echo './'`math_arrayinset.C
CC -DHAVE_CONFIG_H -I. -I. -I../../src -I./../ -I../.. -I../../boost 
-I/usr/openwin/include -g -c math_arrayinset.C
"math_arrayinset.C", line 48: Error: Could not find a match for 
std::vector, std::allocator>>::vector(std::istream_iterator, char, std::char_traits, 
int>, std::istream_iterator, char, std::char_traits, int>).
1 Error(s) detected.

I'm unable to interpret this error.

I'll attach the compressed config.log.

Kind  regards,

Stephan


<[EMAIL PROTECTED]> | beusen Solutions GmbH
fon: +49 30 549932-426   | Landsberger Allee 366
fax: +49 30 549932-921   | 12681 Berlin, Germany




config.log.gz
Description: Binary data

Re: [PATCH] filetools.C

[Lars Gullik Bjønnes]

Angus Leeming <[EMAIL PROTECTED]> writes:

| On Friday 03 May 2002 7:09 am, Andre Poenitz wrote:
>> On Thu, May 02, 2002 at 08:18:32PM +0200, Lars Gullik Bjønnes wrote:
>> > I think that
>> >
>> >str.substr(0) == str
>> >str.substr(0, ) == str
>> >
>> > easy to check though.
>>
>>   21.3.6.7  basic_string::substr[lib.string::substr]
>>
>>   basic_string
>> substr(size_type pos = 0, size_type n = npos) const;
>>
>>   Requires:
>> pos <= size()
>>   Throws:
>> out_of_range if pos > size().
>>   Effects:
>> Determines  the  effective  length rlen of the string to copy as the
>> smaller of n and size() - pos.
>>
>> Looks as though you are right.

('you' here is _me_ not _you_)

>>
>> Andre'
>
| Lars, since it appears that I was correct about this,

You mean: "since it appears that I was NOT correct"

| here's the patch that 
| will make Herbert happy and which is safe. May I commit it please?

no.

-- 
Lgb

Re: [PATCH] filetools.C

[Angus Leeming]

On Friday 03 May 2002 11:13 am, Lars Gullik Bjønnes wrote:
> Angus Leeming <[EMAIL PROTECTED]> writes:
> | On Friday 03 May 2002 7:09 am, Andre Poenitz wrote:
> >> On Thu, May 02, 2002 at 08:18:32PM +0200, Lars Gullik Bjønnes wrote:
> >> > I think that
> >> >
> >> >str.substr(0) == str
> >> >str.substr(0, ) == str
> >> >
> >> > easy to check though.
> >>
> >>   21.3.6.7  basic_string::substr[lib.string::substr]
> >>
> >>   basic_string
> >> substr(size_type pos = 0, size_type n = npos) const;
> >>
> >>   Requires:
> >> pos <= size()
> >>   Throws:
> >> out_of_range if pos > size().
> >>   Effects:
> >> Determines  the  effective  length rlen of the string to copy as the
> >> smaller of n and size() - pos.
> >>
> >> Looks as though you are right.
>
> ('you' here is _me_ not _you_)
>
> >> Andre'
> |
> | Lars, since it appears that I was correct about this,
>
> You mean: "since it appears that I was NOT correct"
>
> | here's the patch that
> | will make Herbert happy and which is safe. May I commit it please?
>
> no.

Ahaa. I should read things more closely. How about the original patch:

lyxerr << "Scanstring: " << str.substr(0,60) << endl;

Can I commit that?

Angus

Re: [PATCH] filetools.C

[Lars Gullik Bjønnes]

Angus Leeming <[EMAIL PROTECTED]> writes:

| On Friday 03 May 2002 11:13 am, Lars Gullik Bjønnes wrote:
>> Angus Leeming <[EMAIL PROTECTED]> writes:
>> | On Friday 03 May 2002 7:09 am, Andre Poenitz wrote:
>> >> On Thu, May 02, 2002 at 08:18:32PM +0200, Lars Gullik Bjønnes wrote:
>> >> > I think that
>> >> >
>> >> >str.substr(0) == str
>> >> >str.substr(0, ) == str
>> >> >
>> >> > easy to check though.
>> >>
>> >>   21.3.6.7  basic_string::substr[lib.string::substr]
>> >>
>> >>   basic_string
>> >> substr(size_type pos = 0, size_type n = npos) const;
>> >>
>> >>   Requires:
>> >> pos <= size()
>> >>   Throws:
>> >> out_of_range if pos > size().
>> >>   Effects:
>> >> Determines  the  effective  length rlen of the string to copy as the
>> >> smaller of n and size() - pos.
>> >>
>> >> Looks as though you are right.
>>
>> ('you' here is _me_ not _you_)
>>
>> >> Andre'
>> |
>> | Lars, since it appears that I was correct about this,
>>
>> You mean: "since it appears that I was NOT correct"
>>
>> | here's the patch that
>> | will make Herbert happy and which is safe. May I commit it please?
>>
>> no.
>
| Ahaa. I should read things more closely. How about the original patch:
>
| lyxerr << "Scanstring: " << str.substr(0,60) << endl;
>
| Can I commit that?

yes.

-- 
Lgb

Re: [PATCH] filetools.C

[Andre Poenitz]

On Fri, May 03, 2002 at 12:13:47PM +0200, Lars Gullik Bjønnes wrote:
> ('you' here is _me_ not _you_)

Indeed. I should have made it explicit by saying "Look as We are right".

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: Placement of \usepackage{babel}

[Juergen Vigna]

On 03-May-2002 Dekel Tsur wrote:

> Which is even a bigger problem, since now the output of the document changes
> without a warning to the user!

Anyway I agree with Jean-Marc that the change IS needed and I don't think
we will go back to the old behaviour. People editing the LaTeX preamble by
hand know what they do and therefore should also know how to counteract
(especially if it's described in UPGRADING).

As Jean-Marc also specified you're a bit late to start this discussion right
now.

Jug

--
-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._
Dr. Jürgen VignaE-Mail:  [EMAIL PROTECTED]
Italienallee 13/N   Tel/Fax: +39-0471-450260 / +39-0471-450253
I-39100 Bozen   Web: http://www.sad.it/~jug
-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._

Never be led astray onto the path of virtue.

Re: [PATCH] Re: Conflict with endfloat

[Dekel Tsur]

Suppose that I have a paragraph that contains the string "Foo.", a float,
and then string " Bar." The figure contains a single letter.

The 1.1.6 output is 
Hello.
\begin{figure}
x
\end{figure}
 Bar.

The 1.2.0 output is
Hello.\begin{figure}%
x\end{figure}%
 Bar.

The 1.2.0 format is bad bacuase:
1) It is not compatible with endfloat.sty
2) It is ugly when read by a human.
3) The DVI output is different than in 1.1.6:
In 1.1.6 the result is 'Hello. Hello.', while in 1.2.0 the result is
'Hello.Hello'.
Once again, we have an incompatibility with 1.1.6 files!

Therefore, I suggest using the 1.1.6 format again.

Re: Placement of \usepackage{babel}

[Jean-Marc Lasgouttes]

Juergen Vigna wrote:
> On 03-May-2002 Dekel Tsur wrote:
> 
> 
>>Which is even a bigger problem, since now the output of the document changes
>>without a warning to the user!
> 
> 
> Anyway I agree with Jean-Marc that the change IS needed and I don't think
> we will go back to the old behaviour. People editing the LaTeX preamble by
> hand know what they do and therefore should also know how to counteract
> (especially if it's described in UPGRADING).
> 
> As Jean-Marc also specified you're a bit late to start this discussion right
> now.

What I propose for next version (instead of this stupid 'assume that
babel is before/after preamble thing) is to have proper per language
preambles in addition to the general preamble. These would be magically
activated by babel at language switch and do the right thing.

Does this sound like a plan for 1.3.0?

In the meantime, I let you (all) decide what to do for now.

JMarc

Re: [PATCH] Re: Conflict with endfloat

[Jean-Marc Lasgouttes]

Dekel Tsur wrote:
> The 1.2.0 format is bad bacuase:
> 1) It is not compatible with endfloat.sty

Indeed.

> 2) It is ugly when read by a human.

Indeed.

> 3) The DVI output is different than in 1.1.6:
> In 1.1.6 the result is 'Hello. Hello.', while in 1.2.0 the result is
> 'Hello.Hello'.
> Once again, we have an incompatibility with 1.1.6 files!

Yes, but this is a case where 1.1.6 had a broken behaviour. Figure
floats should not output anything at the point where they are
inserted. Keeping output identical to 1.1.6 is not som holy grail.

> Therefore, I suggest using the 1.1.6 format again.

Or rather something intermediate between the two.

JMarc

Re: make distcheck broken

[Jean-Marc Lasgouttes]

[EMAIL PROTECTED] wrote:
> On Thu, Apr 25, 2002 at 10:19:23AM +0200, Jean-Marc Lasgouttes wrote:
> 
>>>"adrien" == adrien rebollo <[EMAIL PROTECTED]> writes:
>>
>>adrien> On Thu, Apr 18, 2002 at 06:02:01PM +0200, Jean-Marc Lasgouttes
>>adrien> wrote:
>>
 OK, send the config.log (or the relevant parts), along with some
configuration details.

>>>
>>adrien> I have the same error as John, with autoconf 2.52 and automake
>>adrien> 1.5 I join the config.log, gzipped because it's big.
>>
>>Could you confirm that it works now?
>>
> 
> 
> No, it doesn't. I ran make clean.

People, note I will not have time to look at this. I thought I managed
to compile with ac 2.52, but maybe I just dreamed about it.

JMarc

Re: [PATCH] Re: Conflict with endfloat

[Dekel Tsur]

On Fri, May 03, 2002 at 02:20:05PM +0200, Jean-Marc Lasgouttes wrote:
> Dekel Tsur wrote:
> > The 1.2.0 format is bad bacuase:
> > 1) It is not compatible with endfloat.sty
> 
> Indeed.
> 
> > 2) It is ugly when read by a human.
> 
> Indeed.
> 
> > 3) The DVI output is different than in 1.1.6:
> > In 1.1.6 the result is 'Hello. Hello.', while in 1.2.0 the result is
> > 'Hello.Hello'.
> > Once again, we have an incompatibility with 1.1.6 files!
> 
> Yes, but this is a case where 1.1.6 had a broken behaviour. Figure
> floats should not output anything at the point where they are
> inserted. Keeping output identical to 1.1.6 is not som holy grail.

No, the 1.2.0 behavior is wrong! Note that text in my example is
"Hello. Hello." namely there is a space before the second 'H'.
In the 1.2.0 output, there is no space between the sentences.

The only place when the 1.1.6 behavior inserts a space to the output is
when you put the figure in the middle of a word, which is not a sensible
thing to do.

Re: [PATCH] Re: Conflict with endfloat

[Herbert Voss]

On Fri, 3 May 2002, Dekel Tsur wrote:

> Suppose that I have a paragraph that contains the string "Foo.", a float,
> and then string " Bar." The figure contains a single letter.
>
> The 1.1.6 output is
> Hello.
> \begin{figure}
> x
> \end{figure}
>  Bar.
>
> The 1.2.0 output is
> Hello.\begin{figure}%
> x\end{figure}%
>  Bar.
>
> The 1.2.0 format is bad bacuase:
> 1) It is not compatible with endfloat.sty

right, but a problem of endfloat. Inside a float all is read
in verbatim mode and therefore endfloat needs a whole line
for \end{...}

> 2) It is ugly when read by a human.

yesss

> 3) The DVI output is different than in 1.1.6:
> In 1.1.6 the result is 'Hello. Hello.', while in 1.2.0 the result is
> 'Hello.Hello'.

in fact of the % the space before Bar is a whitespace

> Once again, we have an incompatibility with 1.1.6 files!

yes

> Therefore, I suggest using the 1.1.6 format again.

yes

Herbert

Re: [PATCH] Re: Conflict with endfloat

[Jean-Marc Lasgouttes]

Dekel Tsur wrote:
>>Yes, but this is a case where 1.1.6 had a broken behaviour. Figure
>>floats should not output anything at the point where they are
>>inserted. Keeping output identical to 1.1.6 is not som holy grail.
> 
> 
> No, the 1.2.0 behavior is wrong! Note that text in my example is
> "Hello. Hello." namely there is a space before the second 'H'.
> In the 1.2.0 output, there is no space between the sentences.
> 
> The only place when the 1.1.6 behavior inserts a space to the output is
> when you put the figure in the middle of a word, which is not a sensible
> thing to do.

I missed that indeed. We should definitely not eat spaces, but not add
new ones either.

JMarc

[Fwd: Feedback from www.lyx.org]

[Jean-Marc Lasgouttes]

Could you please answer to carlo? It seems that some of these problems
have been addressed already.

JMarc

 Original Message 
Subject: Feedback from www.lyx.org
Date: Fri, 3 May 2002 14:31:27 +0200
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]


carlo cecati ([EMAIL PROTECTED]) entered the
following feedback message on the LyX home page:


I have installed LyX 1.2 (downloaded from the Mandrake cooker).
It looks very good burt there are some problems.
It does seem that loading an old version file (e.g. form lyx.1.1.6) 
erases the spaces (blancks)  in the \bibitem. the result is a crach when 
one try to edit the bibligraphy item.
It is not clear how to put the automatic numbering in floats (previous 
versions do it automatically)

Since some versions I an unable to use accented characters with a US 
keyboard.
Any way it is a great program!
Carlo Cecati

Re: [PATCH] Re: Conflict with endfloat

[Lars Gullik Bjønnes]

Dekel Tsur <[EMAIL PROTECTED]> writes:

| Suppose that I have a paragraph that contains the string "Foo.", a float,
| and then string " Bar." The figure contains a single letter.
>
| The 1.1.6 output is 
| Hello.
| \begin{figure}
| x
| \end{figure}
|  Bar.
>
| The 1.2.0 output is
| Hello.\begin{figure}%
| x\end{figure}%
|  Bar.

Does endfloat like this:

Hello.
\begin{figure}%
x%
\end{figure}
 Bar.

??

-- 
Lgb

Re: elsart and bibtex

[Martin Vermeer]

On Fri, May 03, 2002 at 11:04:44AM +0200, Juergen Vigna wrote:
 
> On 03-May-2002 Herbert Voss wrote:
> 
> > why does this patch changes the file format?
> 
> Oh sorry I didn't look at the patch, but I thought that implementing
> stuff like frontmatter,backmatter would also change something in the
> fileformat (that you save some information in the .lyx file). If it
> isn't like this just forget about my ranting, I just wanted to be sure
> that we don't get complains later on if something does not work as
> expected using a modified version of the lyx binary.
> 
>Jug

Actually now that I see this is possible, it would be time to adapt the
Kluwer format as well.

This may be the point to also implement BeginDocument and EndDocument,
as needed by AGU. Ah well, perhaps not now. But let's keep it in mind.

Martin




msg37674/pgp0.pgp
Description: PGP signature

Re: [PATCH] Re: Conflict with endfloat

[Dekel Tsur]

On Fri, May 03, 2002 at 02:37:19PM +0200, Lars Gullik Bjønnes wrote:
> Does endfloat like this:
> 
> Hello.
> \begin{figure}%
> x%
> \end{figure}
>  Bar.

Yes, but both % chars has no effect, so we can just write
Hello.
\begin{figure}
x
\end{figure}
Bar.

Re: [PATCH] Re: Conflict with endfloat

[Lars Gullik Bjønnes]

Dekel Tsur <[EMAIL PROTECTED]> writes:

| On Fri, May 03, 2002 at 02:37:19PM +0200, Lars Gullik Bjønnes wrote:
>> Does endfloat like this:
>> 
>> Hello.
>> \begin{figure}%
>> x%
>> \end{figure}
>>  Bar.
>
| Yes, but both % chars has no effect, so we can just write
| Hello.
| \begin{figure}
| x
| \end{figure}
| Bar.

This is where you are wrong...

The version with the '%'s is read by latex as:

"Hello.
\begin{figure}x\end{figure}
 Bar."

and the other is read as

"Hello.
\begin{figure}
x
\end{figure}
 Bar."

With several evironments and commands a '%' will make a visula effect,
usually less whitespace/separation in the output.

So IMHO we should use '%' everywhere we can unless it is wrong to use
it there.

-- 
Lgb

Re: [PATCH] Re: Conflict with endfloat

[Dekel Tsur]

On Fri, May 03, 2002 at 02:32:06PM +0200, Jean-Marc Lasgouttes wrote:
> > 
> > No, the 1.2.0 behavior is wrong! Note that text in my example is
> > "Hello. Hello." namely there is a space before the second 'H'.
> > In the 1.2.0 output, there is no space between the sentences.
> > 
> > The only place when the 1.1.6 behavior inserts a space to the output is
> > when you put the figure in the middle of a word, which is not a sensible
> > thing to do.
> 
> I missed that indeed. We should definitely not eat spaces, but not add
> new ones either.

Here is a patch that fix this.
I'll apply it if there are no objections.

Note that the output for "Foo. Bar." is now
Foo.%
\begin{figure}
Bar.
\end{figure}
 Bar.

The % char is to prevent having two consecutive \n chars.
It can be removed if InsetFloat::latex could know whether
the last char of the output stream is \n.

Rotating images

[Wayan]

On Fri, 3 May 2002, Angus Leeming wrote:

> Could you send an example file/image to the devel list please.
> [EMAIL PROTECTED]
>
> I think you are saying that the image is not rotated on the LyX screen but
> that it is in the output. (And that the output then has this extra space).

I put a screen capture of lyx1.2 with the lyx document being opened.
--> lyx-view.jpg to show the graph can't rotated by lyx. But the result in
pdf output is rotated with adding a space (see fig 2 in pdf file).

> There are two bugs here.
> 1. The extra blank space in the output. Please send the LyX file/image to
> lyx-devel.

I have compressed 4 files
- figs-test.lyx --> lyx file
- freqth.ps --> graph file that I want to inset in lyx document
- figs-test.pdf --> pdf result
- lyx-view.jpg ---> screen grab of lyx.

> 2. The image is not rotated on the LyX screen.
> This means:
> a) You're rotating the image by exactly 270degrees.
> b) You're using the xforms image loader.

I use xforms 0.89.6

> If you run lyx from the console, you'll get a message
>
>   InternalError: bad special angle

I think yes. But, If I export to latex, there is no rotate command in
latex source. I guess, latex should use the image produced by rotating
command of lyx. In lyx-1.1.6 this rotate command is still exist by
exporting to latex.

Thank you very much for your attention
and help.

Best regards,

Wayan



graph-test.tgz
Description: graph-test

[PATCH] Re: Rotating images

[Angus Leeming]

On Friday 03 May 2002 2:09 pm, Wayan wrote:
> On Fri, 3 May 2002, Angus Leeming wrote:
> > Could you send an example file/image to the devel list please.
> > [EMAIL PROTECTED]
> >
> > I think you are saying that the image is not rotated on the LyX screen
> > but that it is in the output. (And that the output then has this extra
> > space).
>
> I put a screen capture of lyx1.2 with the lyx document being opened.
> --> lyx-view.jpg to show the graph can't rotated by lyx. But the result in
> pdf output is rotated with adding a space (see fig 2 in pdf file).
>
> > There are two bugs here.
> > 1. The extra blank space in the output. Please send the LyX file/image to
> > lyx-devel.
>
> I have compressed 4 files
> - figs-test.lyx --> lyx file
> - freqth.ps --> graph file that I want to inset in lyx document
> - figs-test.pdf --> pdf result
> - lyx-view.jpg ---> screen grab of lyx.
>
> > 2. The image is not rotated on the LyX screen.
> > This means:
> > a) You're rotating the image by exactly 270degrees.
> > b) You're using the xforms image loader.
>
> I use xforms 0.89.6
>
> > If you run lyx from the console, you'll get a message
> >
> > InternalError: bad special angle
>
> I think yes. But, If I export to latex, there is no rotate command in
> latex source. I guess, latex should use the image produced by rotating
> command of lyx. In lyx-1.1.6 this rotate command is still exist by
> exporting to latex.
>
> Thank you very much for your attention
> and help.
>
> Best regards,
>
> Wayan

The xforms bug (unable to rotate the image on screen by exactly 270degs) is 
easy to fix. Patch attached. Lars, I'm leaving the office now, could you 
apply this fix please.

Angus


Index: src/frontends/xforms/ChangeLog
===
RCS file: /usr/local/lyx/cvsroot/lyx-devel/src/frontends/xforms/ChangeLog,v
retrieving revision 1.372
diff -u -p -r1.372 ChangeLog
--- src/frontends/xforms/ChangeLog	2 May 2002 13:34:10 -	1.372
+++ src/frontends/xforms/ChangeLog	3 May 2002 13:31:26 -
@@ -1,3 +1,8 @@
+2002-05-03  Angus Leeming  <[EMAIL PROTECTED]>
+
+	* xformsGImage.C (rotate): work-around xforms bug when rotating by
+	270 degs.
+
 2002-05-02  Herbert Voss  <[EMAIL PROTECTED]>
 
 	* FormBibtex.C (apply): a change from a style to an empty one
Index: src/frontends/xforms/xformsGImage.C
===
RCS file: /usr/local/lyx/cvsroot/lyx-devel/src/frontends/xforms/xformsGImage.C,v
retrieving revision 1.6
diff -u -p -r1.6 xformsGImage.C
--- src/frontends/xforms/xformsGImage.C	8 Apr 2002 20:00:02 -	1.6
+++ src/frontends/xforms/xformsGImage.C	3 May 2002 13:31:29 -
@@ -281,7 +281,16 @@ void xformsGImage::rotate(GParams const 
 
 	// The angle passed to flimage_rotate is the angle in one-tenth of a
 	// degree units.
-	flimage_rotate(image_, params.angle * 10, FLIMAGE_SUBPIXEL);
+
+	// Work around xforms bug when params.angle == 270
+	// the 'InternalError: bad special angle' error.
+	// This bug fix is not needed in xforms 1.0 and greater.
+	if (params.angle == 270) {
+		flimage_rotate(image_,  900, FLIMAGE_SUBPIXEL);
+		flimage_rotate(image_, 1800, FLIMAGE_SUBPIXEL);
+	} else {
+		flimage_rotate(image_, params.angle * 10, FLIMAGE_SUBPIXEL);
+	}
 }
 
 

Next pre and final 1.2.0?

[Juergen Vigna]

I just had a look at the bug list and don't see anything which should be fixed
for 1.2.0. The only incompatibility with 1.1.6 is still that we forget about the
paragrap-extra "indent" stuff (we loose this information). This is actually an
added "left-indent" for the whole paragraph (not only the first row of the
paragraph).

With the attached patch we read/write/handle this information again. The only
thing missing in the patch is the visual UI to input/change the information
which should be in the Paragrap-Layout, but IMO that can be done also later.

For now we don't loose old information and also handle it quite good.

 Jug

--
-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._
Dr. Jürgen VignaE-Mail:  [EMAIL PROTECTED]
Italienallee 13/N   Tel/Fax: +39-0471-450260 / +39-0471-450253
I-39100 Bozen   Web: http://www.sad.it/~jug
-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._

You can't kiss a girl unexpectedly -- only sooner than she thought you would.



Index: src/LaTeXFeatures.C
===
RCS file: /usr/local/lyx/cvsroot/lyx-devel/src/LaTeXFeatures.C,v
retrieving revision 1.61
diff -u -p -r1.61 LaTeXFeatures.C
--- src/LaTeXFeatures.C 23 Apr 2002 22:34:24 -  1.61
+++ src/LaTeXFeatures.C 3 May 2002 13:34:09 -
@@ -303,8 +303,8 @@ string const LaTeXFeatures::getMacros() 
// other
if (isRequired("NeedLyXMinipageIndent"))
macros << minipageindent_def;
-   if (isRequired("ParagraphIndent"))
-   macros << paragraphindent_def;
+   if (isRequired("ParagraphLeftIndent"))
+   macros << paragraphleftindent_def;
if (isRequired("NeedLyXFootnoteCode"))
macros << floatingfootnote_def;
 
Index: src/ParagraphParameters.C
===
RCS file: /usr/local/lyx/cvsroot/lyx-devel/src/ParagraphParameters.C,v
retrieving revision 1.8
diff -u -p -r1.8 ParagraphParameters.C
--- src/ParagraphParameters.C   21 Mar 2002 17:25:09 -  1.8
+++ src/ParagraphParameters.C   3 May 2002 13:34:09 -
@@ -268,6 +268,21 @@ void ParagraphParameters::labelWidthStri
set_from_struct(tmp);
 }
 
+
+
+LyXLength const & ParagraphParameters::leftIndent() const
+{
+   return param->leftindent;
+}
+
+
+void ParagraphParameters::leftIndent(LyXLength const & li)
+{
+   ParameterStruct tmp(*param);
+   tmp.leftindent = li;
+   set_from_struct(tmp);
+}
+
 #ifndef NO_PEXTRA_REALLY
 int ParagraphParameters::pextraType() const
 {
Index: src/ParagraphParameters.h
===
RCS file: /usr/local/lyx/cvsroot/lyx-devel/src/ParagraphParameters.h,v
retrieving revision 1.7
diff -u -p -r1.7 ParagraphParameters.h
--- src/ParagraphParameters.h   3 Aug 2001 18:28:03 -   1.7
+++ src/ParagraphParameters.h   3 May 2002 13:34:09 -
@@ -87,6 +87,11 @@ public:
string const & labelWidthString() const;
///
void labelWidthString(string const &);
+   ///
+   LyXLength const & leftIndent() const;
+   ///
+   void leftIndent(LyXLength const &);
+   ///
 #ifndef NO_PEXTRA_REALLY
///
int pextraType() const;
Index: src/ParameterStruct.h
===
RCS file: /usr/local/lyx/cvsroot/lyx-devel/src/ParameterStruct.h,v
retrieving revision 1.5
diff -u -p -r1.5 ParameterStruct.h
--- src/ParameterStruct.h   21 Mar 2002 17:25:09 -  1.5
+++ src/ParameterStruct.h   3 May 2002 13:34:09 -
@@ -6,6 +6,7 @@
 #include "vspace.h"
 #include "Spacing.h"
 #include "layout.h"
+#include "lyxlength.h"
 
 #ifdef __GNUG__
 #pragma interface
@@ -45,6 +46,9 @@ struct ParameterStruct {
string labelstring;
///
string labelwidthstring;
+   ///
+   LyXLength leftindent;
+   ///
 #ifndef NO_PEXTRA_REALLY
///
int pextra_type;
@@ -93,6 +97,7 @@ bool operator==(ParameterStruct const & 
&& ps1.appendix == ps2.appendix
&& ps1.labelstring == ps2.labelstring
&& ps1.labelwidthstring == ps2.labelwidthstring
+   && ps1.leftindent == ps2.leftindent
 #ifndef NO_PEXTRA_REALLY
&& ps1.pextra_type == ps2.pextra_type
&& ps1.pextra_width == ps2.pextra_width
Index: src/buffer.C
===
RCS file: /usr/local/lyx/cvsroot/lyx-devel/src/buffer.C,v
retrieving revision 1.332
diff -u -p -r1.332 buffer.C
--- src/buffer.C2 May 2002 12:21:41 -   1.332
+++ src/buffer.C3 May 2002 13:34:12 -
@@ -718,6 +718,10 @@ Buffer::parseSingleLyXformat2Token(LyXLe
params.fonts = lex.getString();
} else if (token == "\\noindent") {
par->params().noindent(true);
+   } else if 

Re: [PATCH] Re: Conflict with endfloat

[Dekel Tsur]

On Fri, May 03, 2002 at 03:04:26PM +0200, Lars Gullik Bjønnes wrote:
> This is where you are wrong...
> 
> The version with the '%'s is read by latex as:
> 
> "Hello.
> \begin{figure}x\end{figure}
>  Bar."
> 
> and the other is read as
> 
> "Hello.
> \begin{figure}
> x
> \end{figure}
>  Bar."
> 
> With several evironments and commands a '%' will make a visula effect,
> usually less whitespace/separation in the output.

There is no difference between the two!
Try the attached example.



example.tex
Description: TeX document

Re: [PATCH] Re: Conflict with endfloat

[Dekel Tsur]

On Fri, May 03, 2002 at 04:43:19PM +0300, Dekel Tsur wrote:
> On Fri, May 03, 2002 at 03:04:26PM +0200, Lars Gullik Bjønnes wrote:
> > The version with the '%'s is read by latex as:
> > 
> > "Hello.
> > \begin{figure}x\end{figure}
> >  Bar."
> > 
> > and the other is read as
> > 
> > "Hello.
> > \begin{figure}
> > x
> > \end{figure}
> >  Bar."
> > 
> > With several evironments and commands a '%' will make a visula effect,
> > usually less whitespace/separation in the output.
> 
> There is no difference between the two!

And the explanation (if I'm not mistaken) is as follows:
The \begin{figure} causes TeX to go into restricted vertical mode, so
the space after \begin{figure} is ignored.
The space after the 'x' appears right before a \par command
(which is generated by the \end{figure} macro), and therefore, 
it is ignored by TeX.

Re: [PATCH] Re: Conflict with endfloat

[Lars Gullik Bjønnes]

Dekel Tsur <[EMAIL PROTECTED]> writes:

| On Fri, May 03, 2002 at 04:43:19PM +0300, Dekel Tsur wrote:
>> On Fri, May 03, 2002 at 03:04:26PM +0200, Lars Gullik Bjønnes wrote:
>> > The version with the '%'s is read by latex as:
>> > 
>> > "Hello.
>> > \begin{figure}x\end{figure}
>> >  Bar."
>> > 
>> > and the other is read as
>> > 
>> > "Hello.
>> > \begin{figure}
>> > x
>> > \end{figure}
>> >  Bar."
>> > 
>> > With several evironments and commands a '%' will make a visula effect,
>> > usually less whitespace/separation in the output.
>> 
>> There is no difference between the two!
>
| And the explanation (if I'm not mistaken) is as follows:
| The \begin{figure} causes TeX to go into restricted vertical mode, so
| the space after \begin{figure} is ignored.
| The space after the 'x' appears right before a \par command
| (which is generated by the \end{figure} macro), and therefore, 
| it is ignored by TeX.

And you manually had to inspect the latex implementation of this
environment to determine that this was safe...

bette to use the '%' imho.

-- 
Lgb

Re: [PATCH] Re: Conflict with endfloat

[Herbert Voss]

Lars Gullik Bjønnes wrote:

>>>There is no difference between the two!
>>>
> | And the explanation (if I'm not mistaken) is as follows:
> | The \begin{figure} causes TeX to go into restricted vertical mode, so
> | the space after \begin{figure} is ignored.
> | The space after the 'x' appears right before a \par command
> | (which is generated by the \end{figure} macro), and therefore, 
> | it is ignored by TeX.
> 
> And you manually had to inspect the latex implementation of this
> environment to determine that this was safe...


it is safe, what Dekel wrote. the main float definition can be read
in latex.ltx and starts with

\def
\def\@xfloat #1[#2]{%
[...]

> bette to use the '%' imho.


no


Herbert



-- 
http://www.lyx.org/help/

Re: Next pre and final 1.2.0?

[John Levon]

On Fri, May 03, 2002 at 03:40:11PM +0200, Juergen Vigna wrote:

> I just had a look at the bug list and don't see anything which should be fixed
> for 1.2.0. The only incompatibility with 1.1.6 is still that we forget about the

What about this Hungarian search thing ?

Also:

1) Dekel's minpage script needs to go in + patch to UPGRADING
2) Dekel's figure float patch (where is it ?)
3) what's this about bibitems + spaces ??
4) we should document using caption environment in UPGRADING I think

regards
john

OT: still spam/virus

[Mate Wierdl]

Here is the plan now:

1)  I will set up a filter that will filter out mail with certain
file extensions.  Do people send here .zip files?   

2) I will set up two testlists: one with TMDA, the other one 
   with moderation (only nonsubscribers mail to be moderated).
   
I cannot do this today or in the weekend, but they should be
set up by Tuesday.  Then I will send a more detailed message about
them.  We'll try the two lists for a few days, and you will decide
which one is the way to go.

Mate

Re: OT: still spam/virus

[Lars Gullik Bjønnes]

Mate Wierdl <[EMAIL PROTECTED]> writes:

| Here is the plan now:
>
| 1)  I will set up a filter that will filter out mail with certain
| file extensions.  Do people send here .zip files?   

seldom... but with more windows users.. I don't know.
 
| 2) I will set up two testlists: one with TMDA, the other one 
|with moderation (only nonsubscribers mail to be moderated).

So moderation the way I mentioned is not possible?

But ok, I am glad that you are willing to do this.

-- 
Lgb

Fifth prerelease of LyX 1.2.0

[Lars Gullik Bjønnes]

Ok, this will hopefully be the last (or next to last) prerelease
before 1.2.0 proper is released.

Since pre4 several small problems have been fixed, and a few bigger
ones, but nothing major.

There are still some small glitches, but nothing really bad. (knock wood)

This prelease can be found at:

ftp://ftp.devel.lyx.org/pub/lyx/lyx-1.2.0pre5.tar.gz

But as always, this is a prelease and some caution is warranted.
Backup your docs before trying this out.

Please also read the README and UPGRADING.

-- 
Lgb

It created massive refugee flows and is a

[feedback]

>

Re: Fifth prerelease of LyX 1.2.0

[Kayvan A. Sylvan]

On Sat, May 04, 2002 at 12:40:34AM +0200, Lars Gullik Bjønnes wrote:
> 
> Ok, this will hopefully be the last (or next to last) prerelease
> before 1.2.0 proper is released.
> 
> Since pre4 several small problems have been fixed, and a few bigger
> ones, but nothing major.
> 
> There are still some small glitches, but nothing really bad. (knock wood)
> 
> This prelease can be found at:
> 
> ftp://ftp.devel.lyx.org/pub/lyx/lyx-1.2.0pre5.tar.gz
> 
> But as always, this is a prelease and some caution is warranted.
> Backup your docs before trying this out.
> 
> Please also read the README and UPGRADING.

RPMs in ftp://ftp.sylvan.com/pub/lyx

-- 
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)



msg37693/pgp0.pgp
Description: PGP signature

Re: OT: still spam/virus

[Mate Wierdl]

On Fri, May 03, 2002 at 07:40:27PM +0200, Lars Gullik Bjønnes wrote:
> Mate Wierdl <[EMAIL PROTECTED]> writes:
> 
> | Here is the plan now:
> >
> | 1)  I will set up a filter that will filter out mail with certain
> | file extensions.  Do people send here .zip files?   
> 
> seldom... but with more windows users.. I don't know.
>  
> | 2) I will set up two testlists: one with TMDA, the other one 
> |with moderation (only nonsubscribers mail to be moderated).
> 
> So moderation the way I mentioned is not possible?

It is, but it is not built into ezmlm.  At least if I understood you
correctly: you want each message coming from non subscribers to be
moderated, and if a poster is approved, say, 4 times, then allow
through w/o moderation.

What is readily available: a moderator can decide to subscribe a
sender to the "allow" database, and then from that point on, the
sender is allowed to post to the list without moderation.

But I think moderation is a pain---TMDA does it automatically.  

BTWY, yesterday and today 3 messages addressed to lyx-users with
Klez in them were caught by the "no greater than 60K" rule.

Since the senders were unknown, the messages were bounced back to
root.  See them at

http://www.csi.hu/mw/1020475760.15065_1.moni:2,S
http://www.csi.hu/mw/1020475770.15065_3.moni:2,S
http://www.csi.hu/mw/1020475776.15065_5.moni:2,S

Mate
I guess I need to speed up with this virus protection.