Re: Problem reading a file
On Tue, Mar 25, 2003 at 08:54:39AM +0100, Jean-Marc Lasgouttes wrote: > Yann> It doesn't matter because I found a way to correct this behavior > Yann> and I still can use inset ERT inside float inset > > Why can't you just change the font size of the inset? I am puzzled by > the need of ERT. Believe it or not. I do font size changes with ERT and not with the character layout, too. Maybe just because fiddling with font sizes should hurt... Andre' -- Those who desire to give up Freedom in order to gain Security, will not have, nor do they deserve, either one. (T. Jefferson or B. Franklin or both...)
Re: Problem reading a file
Jean-Marc Lasgouttes wrote: Yann> It doesn't matter because I found a way to correct this behavior Yann> and I still can use inset ERT inside float inset Why can't you just change the font size of the inset? I am puzzled by the need of ERT. Because I haven't thought to this solution. My first solution was the use of ERT (yes I know, I like a lot (maybe too much) difficult solutions) and know, because I am lazy, I don't want to change all the figures. Thanks a lot for your answers. Yann COLLETTE
Re: Problem reading a file
On Tuesday 25 March 2003 07:38, Yann COLLETTE wrote:
> Jean-Marc Lasgouttes wrote:
> >>"Yann" == Yann COLLETTE <[EMAIL PROTECTED]> writes:
> >
> > If you use strange ERT, you cannot expect LyX to respect it forever
> > (especially when you have non-balanced braces like here). It has been
> > possible for a lng time to just put the graphics inset in Large
> > font and just avoid the ERT. (and BTW the syntax is "{\Large ...}",
> > certainly not "\Large{...}").
>
> I don't if "a dangerous way to use insets" is specified somewhere in the
> docs but it uses to work fine on lyx-1.1.6fix4 and doesn't work anymore
> on lyx-1.3.1. It doesn't matter because I found a way to correct this
> behavior and I still can use inset ERT inside float inset and
> \Large{ } works fine with latex.
Yann notice that when I tried to load, and create a dvi, with your document
I had also problems with 1.1.6fix4, so at least for me some errors where
already present in the old version.
> Yann
--
José Abílio
Re: Problem reading a file
> "Yann" == Yann COLLETTE <[EMAIL PROTECTED]> writes:
Yann> Jean-Marc Lasgouttes wrote:
>>> "Yann" == Yann COLLETTE <[EMAIL PROTECTED]> writes:
>>
>>
>> If you use strange ERT, you cannot expect LyX to respect it forever
>> (especially when you have non-balanced braces like here). It has
>> been possible for a lng time to just put the graphics inset in
>> Large font and just avoid the ERT. (and BTW the syntax is "{\Large
>> ...}", certainly not "\Large{...}").
Yann> I don't if "a dangerous way to use insets" is specified
Yann> somewhere in the docs but it uses to work fine on lyx-1.1.6fix4
Yann> and doesn't work anymore on lyx-1.3.1.
I am not sure whether it is written down either, but it has always
been our intent: if you use heavy ERT, you are on your own...
Yann> It doesn't matter because I found a way to correct this behavior
Yann> and I still can use inset ERT inside float inset
Why can't you just change the font size of the inset? I am puzzled by
the need of ERT.
Yann> and \Large{ } works fine with latex.
It does not do what you think it does. \Large is not a macro taking an
argument, but a declaration changing current text size. Therefore
"\Large{foo}" is equivalent to "\Large foo". This means that your
quotes are totally useless here.
Also, if you write "\Large{a}b", both a qnd b will be large.
Yann> I know it's stupid to set a list style for a float, but it was a
Yann> pure mistake from me. The problem is that it was an error really
Yann> hard to find.
Yes, I know it is difficult to find. And you are not the only one who
did this mistake.
JMarc
Re: Problem reading a file
Jean-Marc Lasgouttes wrote:
"Yann" == Yann COLLETTE <[EMAIL PROTECTED]> writes:
If you use strange ERT, you cannot expect LyX to respect it forever
(especially when you have non-balanced braces like here). It has been
possible for a lng time to just put the graphics inset in Large
font and just avoid the ERT. (and BTW the syntax is "{\Large ...}",
certainly not "\Large{...}").
I don't if "a dangerous way to use insets" is specified somewhere in the
docs but it uses to work fine on lyx-1.1.6fix4 and doesn't work anymore
on lyx-1.3.1. It doesn't matter because I found a way to correct this
behavior and I still can use inset ERT inside float inset and
\Large{ } works fine with latex.
I do not know by which miracle LyX 1.1.6 could make this work, but it
was definitely not a good idea. I am not sure what we could do right
not to get it to work. Ideas are definitely welcome.
I know it's stupid to set a list style for a float, but it was a pure
mistake from me.
The problem is that it was an error really hard to find.
Yann
Re: Problem reading a file
> "Yann" == Yann COLLETTE <[EMAIL PROTECTED]> writes:
Yann> Hello, I've finally solved my problem, but there are some bugs
Yann> with lyx-1.3.1. I have imported a lyx-1.1.6fix4 file into
Yann> lyx-1.3.1 with xforms-1.0.
Yann> 2 - I use a lot inset ERT inside float. It uses to work fine
Yann> with lyx-1.1.6fix4 but doesn't work anymore with lyx-1.3.1. I
Yann> enclose an image with '\Large{' and '}' because I use psfrag and
Yann> it's an easy way to set the size of the text's image without
Yann> modifying the image itself. Sometimes I must use the paragraph
Yann> dialog to center the image. When I do that, the inset ERT are
Yann> also centered (because they belong to the same paragraph as the
Yann> image. With lyx-1.1.6fix4 it was exported into latex like this:
Yann> {\centering \Large{ \par} IMAGE {\centering } \par} With
Yann> lyx-1.3.1 it is exported into latex like this : \begin{center}
Yann> \Large{ \end{center} IMAGE \begin{center} } \end{center} and
Yann> latex now complain about some extra { or some } missing.
If you use strange ERT, you cannot expect LyX to respect it forever
(especially when you have non-balanced braces like here). It has been
possible for a lng time to just put the graphics inset in Large
font and just avoid the ERT. (and BTW the syntax is "{\Large ...}",
certainly not "\Large{...}").
Yann> 3 - In my lyx-1.1.6fix4 file, I've got a float with an image.
Yann> This float is just above a lyx list and, due to a bad key
Yann> sequence from me this float is in a list style. With
Yann> lyx-1.1.6fix4, this mistake doesn't matter, the list style has
Yann> no influence on the float. But, with lyx-1.3.1 the float is
Yann> mixed inside a list and this combination produces a lot of latex
Yann> errors.
I do not know by which miracle LyX 1.1.6 could make this work, but it
was definitely not a good idea. I am not sure what we could do right
not to get it to work. Ideas are definitely welcome.
JMarc
Re: Problem reading a file
Hello, Ok, thanks. I will be patient and wait for lyx-1.3.2 YC John Levon wrote: On Mon, Mar 24, 2003 at 09:09:14AM +0100, Yann COLLETTE wrote: 1 - When converting images with subtitles, only the first word of the title is left in the lyx-1.3.1 file. I sent a fix for this yesterday. john
Re: Problem reading a file
On Mon, Mar 24, 2003 at 09:09:14AM +0100, Yann COLLETTE wrote: > 1 - When converting images with subtitles, only the first word of the > title is left in the lyx-1.3.1 file. I sent a fix for this yesterday. john
Problem reading a file
Hello,
I've finally solved my problem, but there are some bugs with lyx-1.3.1.
I have imported a lyx-1.1.6fix4 file into lyx-1.3.1 with xforms-1.0.
1 - When converting images with subtitles, only the first word of the
title is left in the lyx-1.3.1 file.
2 - I use a lot inset ERT inside float. It uses to work fine with
lyx-1.1.6fix4 but doesn't work anymore with lyx-1.3.1.
I enclose an image with '\Large{' and '}' because I use psfrag and
it's an easy way to set the size of the text's image without
modifying the image itself.
Sometimes I must use the paragraph dialog to center the image.
When I do that, the inset ERT are also centered (because they belong
to the same paragraph as the image.
With lyx-1.1.6fix4 it was exported into latex like this:
{\centering \Large{ \par}
IMAGE
{\centering } \par}
With lyx-1.3.1 it is exported into latex like this :
\begin{center} \Large{ \end{center}
IMAGE
\begin{center} } \end{center}
and latex now complain about some extra { or some } missing.
3 - In my lyx-1.1.6fix4 file, I've got a float with an image.
This float is just above a lyx list and, due to a bad key sequence
from me this float is in a list style.
With lyx-1.1.6fix4, this mistake doesn't matter, the list style has
no influence on the float.
But, with lyx-1.3.1 the float is mixed inside a list and this
combination produces a lot of latex errors.
Your sincerely,
Yann COLLETTE
Re: Problem reading a file
On Monday 17 March 2003 07:26, Yann COLLETTE wrote: > Hello, > > Thanks a lot. > Do this change appears in lyx-1.3.1 ? Yes they will. :-) > Now I know I have problem with table in minipages. So, I will find > another solution. As I said I was able to solve most of the problems by simple copy and past to and from an empty document for the case of tables in minipages. Don't ask me why. ;-) The reason why I have stopped was that your document didn't compile without errors for me also with lyx-1.1.6fix4. If you want I can send you (privately) what I have. :-) > Yann COLLETTE -- José Abílio
Re: Problem reading a file
Hello, Thanks a lot. Do this change appears in lyx-1.3.1 ? Now I know I have problem with table in minipages. So, I will find another solution. Yann COLLETTE José Matos wrote: On Thursday 13 March 2003 13:17, Yann COLLETTE wrote: Hello, I've got a huge file composed with lyx-1.1.6fix4 I can't export under postscript with lyx-1.2* and lyx-1.3 (I can export it with lyx-1.1.6fix4). Yann I think that some of the errors you get are related with the changes that happened between 1.1.6fix4 and 1.2.0. Unfortunately I don't remember what were the changes in question. When I open the file with lyx-1.3.0, I've got the following error messages. Wrong tabular format (expected got\layout Standard) Wrong tabular format (expected got\layout Standard) Wrong tabular format (expected got\layout Standard) Wrong tabular format (expected got\layout Standard) Solitary \end_inset. Missing \begin_inset?. Last inset read was: Text Wrong tabular format (expected got\layout Standard) Solitary \end_inset. Missing \begin_inset?. Last inset read was: LatexCommand These errors where corrected by Dekel today so they are history. :-) After using the latest version I still got errors when previewing your document. Most of them got away by simply cutting the table in minipage to an empty document and then back to your document. This was enough to go from 578 to 37 errors. :-) The errors remaining I don't know, I suspect that they are related with your ERT. BTW exporting your document to latex and the running it from there in quiet mode resulted in a complete document. But now you better than me know what is missing. :-) Could it be possible, for lyx-1.3.1, to have the line number where lyx detected these errors so I can correct (maybe) my lyx file. Although as I said this is difficult when a convertion is involved, between different lyx versions I agree that it would be nice to have the line number when there are errors. Your sincerely, Yann COLLETTE
Re: Problem reading a file
On Thursday 13 March 2003 13:17, Yann COLLETTE wrote: > Hello, > > I've got a huge file composed with lyx-1.1.6fix4 I can't export under > postscript with lyx-1.2* and lyx-1.3 (I can export it with lyx-1.1.6fix4). Yann I think that some of the errors you get are related with the changes that happened between 1.1.6fix4 and 1.2.0. Unfortunately I don't remember what were the changes in question. > When I open the file with lyx-1.3.0, I've got the following error messages. > > Wrong tabular format (expected got\layout Standard) > Wrong tabular format (expected got\layout Standard) > Wrong tabular format (expected got\layout Standard) > Wrong tabular format (expected got\layout Standard) > Solitary \end_inset. Missing \begin_inset?. > Last inset read was: Text > Wrong tabular format (expected got\layout Standard) > Solitary \end_inset. Missing \begin_inset?. > Last inset read was: LatexCommand These errors where corrected by Dekel today so they are history. :-) After using the latest version I still got errors when previewing your document. Most of them got away by simply cutting the table in minipage to an empty document and then back to your document. This was enough to go from 578 to 37 errors. :-) The errors remaining I don't know, I suspect that they are related with your ERT. BTW exporting your document to latex and the running it from there in quiet mode resulted in a complete document. But now you better than me know what is missing. :-) > Could it be possible, for lyx-1.3.1, to have the line number where lyx > detected these errors so I can correct (maybe) my lyx file. Although as I said this is difficult when a convertion is involved, between different lyx versions I agree that it would be nice to have the line number when there are errors. > Your sincerely, > > Yann COLLETTE -- José Abílio
Re: Problem reading a file
On Friday 14 March 2003 10:46, Dekel Tsur wrote: > > > > Ok, I found the problem, but not yet the solution. > > We have problems converting tables inside minipages. > > > > Dekel do you have any clue about this? > > Can you send a minimal example ? Unwisely I started a new thread on this, and there I send an example. If you need I have lyx-1.1.6fix4 working, well I have most of them working since 0.12 up to 1.3 -- José Abílio
Re: Problem reading a file
On Thu, Mar 13, 2003 at 06:36:05PM +, Jos? Matos wrote: > On Thursday 13 March 2003 13:17, Yann COLLETTE wrote: > > Hello, > > > > I've got a huge file composed with lyx-1.1.6fix4 I can't export under > > postscript with lyx-1.2* and lyx-1.3 (I can export it with lyx-1.1.6fix4). > > When I open the file with lyx-1.3.0, I've got the following error messages. > > Ok, I found the problem, but not yet the solution. > We have problems converting tables inside minipages. > > Dekel do you have any clue about this? Can you send a minimal example ?
Re: Problem reading a file
On Thu, Mar 13, 2003 at 11:39:28PM +0100, Lars Gullik Bj?nnes wrote: > | using namespace std; > > but that fix would of course never go into the sources... So 1.1.6fix4 development is open again ! Oy joy > problem... Hmm is this lyx 1.3.0? no ;) john
Re: Problem reading a file
John Levon <[EMAIL PROTECTED]> writes: | On Thu, Mar 13, 2003 at 07:25:13PM +0100, Andre Poenitz wrote: | | > Well, I know what we'll have for breakfast tomorrow. | > | > 'Minced John'. | | I'm not scared of Lars ! Have you Been Playing With My FILES?!? -- Lgb
Re: Problem reading a file
John Levon <[EMAIL PROTECTED]> writes: | On Thu, Mar 13, 2003 at 06:07:17PM +, Jos? Matos wrote: | | > g++ -DHAVE_CONFIG_H -I. -I. -I. -I.. -I.. -I../boost-isystem | > /usr/X11R6/include -g -O2 -fno-rtti -fno-exceptions -c lastfiles.C | > lastfiles.C:29: `ostream_iterator' not declared | | perhaps you need to add | | using namespace std; but that fix would of course never go into the sources... And I compile with gcc 3.2 all the time so I doubt this is the problem... Hmm is this lyx 1.3.0? -- Lgb
Re: Problem reading a file
On Thu, Mar 13, 2003 at 06:40:19PM +, John Levon wrote: > > 'Minced John'. > > I'm not scared of Lars ! Famous last words... 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: Problem reading a file
On Thursday 13 March 2003 18:25, Andre Poenitz wrote: > > (adding it to config.h is probably a good way of working around nay > > other cases) > > *gosh* > > Well, I know what we'll have for breakfast tomorrow. > > 'Minced John'. Don't be so harsh, after all this is for an older tree, so a hack is ok. The code is no more maintained. :-) I would like one day to have all previous lyx sources being able to be compiled with present compilers. The main task is to port the code to xforms 1.0. Someday... in the next 20 years. ;-) > Andre' -- José Abílio
Re: Problem reading a file
On Thu, Mar 13, 2003 at 07:25:13PM +0100, Andre Poenitz wrote: > Well, I know what we'll have for breakfast tomorrow. > > 'Minced John'. I'm not scared of Lars ! john
Re: Problem reading a file
On Thursday 13 March 2003 18:23, Andre Poenitz wrote: > On Thu, Mar 13, 2003 at 06:07:17PM +, José Matos wrote: > > lastfiles.C:29: `ostream_iterator' not declared > > Should be in Ok, that was the missing culprit. > Maybe a 'std::' missing? Not, that was there. :-) > Andre' Thanks, -- José Abílio
Re: Problem reading a file
On Thursday 13 March 2003 13:17, Yann COLLETTE wrote: > Hello, > > I've got a huge file composed with lyx-1.1.6fix4 I can't export under > postscript with lyx-1.2* and lyx-1.3 (I can export it with lyx-1.1.6fix4). > When I open the file with lyx-1.3.0, I've got the following error messages. Ok, I found the problem, but not yet the solution. We have problems converting tables inside minipages. Dekel do you have any clue about this? > Your sincerely, > > Yann COLLETTE -- José Abílio
Re: Problem reading a file
On Thu, Mar 13, 2003 at 06:08:09PM +, John Levon wrote: > perhaps you need to add > > using namespace std; > > somewhere ? > > (adding it to config.h is probably a good way of working around nay > other cases) *gosh* Well, I know what we'll have for breakfast tomorrow. 'Minced John'. 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: Problem reading a file
On Thu, Mar 13, 2003 at 06:07:17PM +, José Matos wrote: > lastfiles.C:29: `ostream_iterator' not declared Should be in Maybe a 'std::' missing? 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: Problem reading a file
On Thursday 13 March 2003 18:08, John Levon wrote: > On Thu, Mar 13, 2003 at 06:07:17PM +, Jos? Matos wrote: > > g++ -DHAVE_CONFIG_H -I. -I. -I. -I.. -I.. -I../boost-isystem > > /usr/X11R6/include -g -O2 -fno-rtti -fno-exceptions -c lastfiles.C > > lastfiles.C:29: `ostream_iterator' not declared > > perhaps you need to add > > using namespace std; > > somewhere ? Nope, that is there. What looks like is that the header file where it is defined is not included. > (adding it to config.h is probably a good way of working around nay > other cases) > > john -- José Abílio
Re: Problem reading a file
On Thu, Mar 13, 2003 at 06:07:17PM +, Jos? Matos wrote: > g++ -DHAVE_CONFIG_H -I. -I. -I. -I.. -I.. -I../boost-isystem > /usr/X11R6/include -g -O2 -fno-rtti -fno-exceptions -c lastfiles.C > lastfiles.C:29: `ostream_iterator' not declared perhaps you need to add using namespace std; somewhere ? (adding it to config.h is probably a good way of working around nay other cases) john
Re: Problem reading a file
On Thursday 13 March 2003 13:17, Yann COLLETTE wrote: > Hello, > > I've got a huge file composed with lyx-1.1.6fix4 I can't export under > postscript with lyx-1.2* and lyx-1.3 (I can export it with lyx-1.1.6fix4). > When I open the file with lyx-1.3.0, I've got the following error messages. This is weird, and it doesn't appear to be related with lyx2lyx. I was trying to compile lyx-1.1.6fix4 to test the file that Yann sent me but get this error: g++ -DHAVE_CONFIG_H -I. -I. -I. -I.. -I.. -I../boost-isystem /usr/X11R6/include -g -O2 -fno-rtti -fno-exceptions -c lastfiles.C lastfiles.C:29: `ostream_iterator' not declared lastfiles.C: In member function `void LastFiles::writeFile(const std::string&) const': lastfiles.C:78: `ostream_iterator' undeclared (first use this function) lastfiles.C:78: (Each undeclared identifier is reported only once for each function it appears in.) Where can I find ostream_iterator? I am using gcc 3.2 > Your sincerely, > > Yann COLLETTE -- José Abílio
Re: Problem reading a file
On Thursday 13 March 2003 13:17, Yann COLLETTE wrote: > Hello, > Could it be possible, for lyx-1.3.1, to have the line number where lyx > detected these errors so I can correct (maybe) my lyx file. That is not easy, as the file is transformed from each previous version. It would be easy for the first transformation but not for the others Could you send me the file privately, to see where the problem lays? > Your sincerely, > > Yann COLLETTE -- José Abílio
Problem reading a file
Hello, I've got a huge file composed with lyx-1.1.6fix4 I can't export under postscript with lyx-1.2* and lyx-1.3 (I can export it with lyx-1.1.6fix4). When I open the file with lyx-1.3.0, I've got the following error messages. Wrong tabular format (expected got\layout Standard) Wrong tabular format (expected got\layout Standard) Wrong tabular format (expected got\layout Standard) Wrong tabular format (expected got\layout Standard) Solitary \end_inset. Missing \begin_inset?. Last inset read was: Text Wrong tabular format (expected got\layout Standard) Solitary \end_inset. Missing \begin_inset?. Last inset read was: LatexCommand Could it be possible, for lyx-1.3.1, to have the line number where lyx detected these errors so I can correct (maybe) my lyx file. Your sincerely, Yann COLLETTE
