Re: Xfig and LyX

[Abdelrazak Younes]

Wolfgang Engelmann wrote:

Am Mittwoch, 25. Juni 2008 13:58 schrieb Abdelrazak Younes:

Wolfgang Engelmann wrote:

Could somebody kindly point me to an understandable explanation of how to
use xfig produced figures in LyX?

Use the external inset ("Inset->File->External Material") and choose the
XFig template. You should also select "preview" in the display combo AFAIR.


Thats what I did, Abdel.


I don't think so. As I said, try Inset->File->External Material

Abdel.

Re: keyboard question

[Abdelrazak Younes]

Daniel CLEMENT wrote:


... neither worked (still getting ć). I miss the correct syntax!


Maybe try this:

\bind 'c  unicode-insert 0x00e7

Abdel.

Re: keyboard question

[Abdelrazak Younes]

Daniel CLEMENT wrote:


... neither worked (still getting ć). I miss the correct syntax!


Maybe try this:

\bind 'c  unicode-insert 0x00e7

Abdel.

Re: keyboard question

[Abdelrazak Younes]

Daniel CLEMENT wrote:


... neither worked (still getting ć). I miss the correct syntax!


Maybe try this:

\bind "'c"  "unicode-insert 0x00e7"

Abdel.

Re: Lyx in Podcast

[Abdelrazak Younes]

G. Milde wrote:

On 20.06.08, Abdelrazak Younes wrote:


G. Milde wrote:

On 20.06.08, Wolfgang Engelmann wrote:



* with 250 MB RAM (whereof LyX uses ca. 8 MB)



I can't believe that. Without anything loaded LyX uses around 15 MB of
RAM. When a big document is loaded, say UserGuide.lyx, add 10 MB to
that. This is on Windows. I guess the 8 MB doesn't count the Qt dlls in
memory. This is fair as long as you use them for other software (eg.
KDE).


You are right.

With `top`: and no other QT application running, I get:

  PID USER  PR  NI  VIRT  RES  SHR S %CPU %MEMTIME+  COMMAND
no document:
 2982 milde 20   0 53336  19m  13m S  0.0  7.9   0:02.74 lyx
de/UserGuide.lyx:
 2982 milde 20   0 58412  25m  14m R  0.0 10.3   0:05.74 lyx
second document:
 2982 milde 20   0 59968  27m  14m S  0.7 10.9   0:07.34 lyx

I cannot reproduce the 8M so I am not sure whether this was just taken from
the wrong line or the reporting command splitting the QT ressources between
all running QT apps or what.

Thanks for correcting. 


Thanks for the confirmation ;-)

That said, I think 25 m for a document like the user guide is 
*excellent* if you compare the needed memory for a comparable document 
using OO and MSWord. This is IMVSO a killer argument in favor of LyX. If 
you add to that the starting time and the document loading time 
arguments then, well, I wonder why all those people still use 
conventional word processors :-)


Abdel.

Re: LyX 1.6.0 (b 3) PDF export problem

[Abdelrazak Younes]

Milen Ivanov wrote:


-Original Message-
Dear All,

I have troubles exporting to PDF with LyX 1.6.0(b3) through
File-Export-PDF(pdflatex); also with the other versions of PDF export.
This is on MS Win XP and LyX 1.5.5 PDF-exports with no problem.
I will attach a small file for which the export fails, however there
seems to be little difference as to what exactly the file is.

I apologise for posting this to perhaps not quite right place, but I
would like to ask for some confirmation before issuing a bug. So, is
this not perhaps a known issue, or may be no one can reproduce it due to
some strange specific of my system?!


Does 'View-PDF (pdflatex)' works for you? If yes, then this bug is known:

http://bugzilla.lyx.org/show_bug.cgi?id=4693

Abdel.

Re: Lyx in Podcast

[Abdelrazak Younes]

G. Milde wrote:

On 20.06.08, Abdelrazak Younes wrote:


G. Milde wrote:

On 20.06.08, Wolfgang Engelmann wrote:



* with 250 MB RAM (whereof LyX uses ca. 8 MB)



I can't believe that. Without anything loaded LyX uses around 15 MB of
RAM. When a big document is loaded, say UserGuide.lyx, add 10 MB to
that. This is on Windows. I guess the 8 MB doesn't count the Qt dlls in
memory. This is fair as long as you use them for other software (eg.
KDE).


You are right.

With `top`: and no other QT application running, I get:

  PID USER  PR  NI  VIRT  RES  SHR S %CPU %MEMTIME+  COMMAND
no document:
 2982 milde 20   0 53336  19m  13m S  0.0  7.9   0:02.74 lyx
de/UserGuide.lyx:
 2982 milde 20   0 58412  25m  14m R  0.0 10.3   0:05.74 lyx
second document:
 2982 milde 20   0 59968  27m  14m S  0.7 10.9   0:07.34 lyx

I cannot reproduce the 8M so I am not sure whether this was just taken from
the wrong line or the reporting command splitting the QT ressources between
all running QT apps or what.

Thanks for correcting. 


Thanks for the confirmation ;-)

That said, I think 25 m for a document like the user guide is 
*excellent* if you compare the needed memory for a comparable document 
using OO and MSWord. This is IMVSO a killer argument in favor of LyX. If 
you add to that the starting time and the document loading time 
arguments then, well, I wonder why all those people still use 
conventional word processors :-)


Abdel.

Re: LyX 1.6.0 (b 3) PDF export problem

[Abdelrazak Younes]

Milen Ivanov wrote:


-Original Message-
Dear All,

I have troubles exporting to PDF with LyX 1.6.0(b3) through
File-Export-PDF(pdflatex); also with the other versions of PDF export.
This is on MS Win XP and LyX 1.5.5 PDF-exports with no problem.
I will attach a small file for which the export fails, however there
seems to be little difference as to what exactly the file is.

I apologise for posting this to perhaps not quite right place, but I
would like to ask for some confirmation before issuing a bug. So, is
this not perhaps a known issue, or may be no one can reproduce it due to
some strange specific of my system?!


Does 'View-PDF (pdflatex)' works for you? If yes, then this bug is known:

http://bugzilla.lyx.org/show_bug.cgi?id=4693

Abdel.

Re: Lyx in Podcast

[Abdelrazak Younes]

G. Milde wrote:

On 20.06.08, Abdelrazak Younes wrote:


G. Milde wrote:

On 20.06.08, Wolfgang Engelmann wrote:



* with 250 MB RAM (whereof LyX uses ca. 8 MB)



I can't believe that. Without anything loaded LyX uses around 15 MB of
RAM. When a big document is loaded, say UserGuide.lyx, add 10 MB to
that. This is on Windows. I guess the 8 MB doesn't count the Qt dlls in
memory. This is fair as long as you use them for other software (eg.
KDE).


You are right.

With `top`: and no other QT application running, I get:

  PID USER  PR  NI  VIRT  RES  SHR S %CPU %MEMTIME+  COMMAND
no document:
 2982 milde 20   0 53336  19m  13m S  0.0  7.9   0:02.74 lyx
de/UserGuide.lyx:
 2982 milde 20   0 58412  25m  14m R  0.0 10.3   0:05.74 lyx
second document:
 2982 milde 20   0 59968  27m  14m S  0.7 10.9   0:07.34 lyx

I cannot reproduce the 8M so I am not sure whether this was just taken from
the wrong line or the reporting command splitting the QT ressources between
all running QT apps or what.

Thanks for correcting. 


Thanks for the confirmation ;-)

That said, I think 25 m for a document like the user guide is 
*excellent* if you compare the needed memory for a comparable document 
using OO and MSWord. This is IMVSO a killer argument in favor of LyX. If 
you add to that the starting time and the document loading time 
arguments then, well, I wonder why all those people still use 
conventional word processors :-)


Abdel.

Re: LyX 1.6.0 (b 3) PDF export problem

[Abdelrazak Younes]

Milen Ivanov wrote:


-Original Message-
Dear All,

I have troubles exporting to PDF with LyX 1.6.0(b3) through
File->Export->PDF(pdflatex); also with the other versions of PDF export.
This is on MS Win XP and LyX 1.5.5 PDF-exports with no problem.
I will attach a small file for which the export fails, however there
seems to be little difference as to what exactly the file is.

I apologise for posting this to perhaps not quite right place, but I
would like to ask for some confirmation before issuing a bug. So, is
this not perhaps a known issue, or may be no one can reproduce it due to
some strange specific of my system?!


Does 'View->PDF (pdflatex)' works for you? If yes, then this bug is known:

http://bugzilla.lyx.org/show_bug.cgi?id=4693

Abdel.

Re: Lyx in Podcast

[Abdelrazak Younes]

G. Milde wrote:

On 20.06.08, Wolfgang Engelmann wrote:

There are two items where I am not sure I know enough. 



One is the hardware prerequisites. There are a few remarks in the web,
but not much detailled hints. I do realize that it depends much on what
one plans to do (text only versus many figures, presentations (powerdot
and the like) with large figures etc). 


I do not know about the minimum, but LyX 1.5.5 runs well on my modest
work PC 


* with 250 MB RAM (whereof LyX uses ca. 8 MB)


I can't believe that. Without anything loaded LyX uses around 15 MB of 
RAM. When a big document is loaded, say UserGuide.lyx, add 10 MB to 
that. This is on Windows. I guess the 8 MB doesn't count the Qt dlls in 
memory. This is fair as long as you use them for other software (eg. KDE).


Abdel.

Re: Lyx in Podcast

[Abdelrazak Younes]

G. Milde wrote:

On 20.06.08, Wolfgang Engelmann wrote:

There are two items where I am not sure I know enough. 



One is the hardware prerequisites. There are a few remarks in the web,
but not much detailled hints. I do realize that it depends much on what
one plans to do (text only versus many figures, presentations (powerdot
and the like) with large figures etc). 


I do not know about the minimum, but LyX 1.5.5 runs well on my modest
work PC 


* with 250 MB RAM (whereof LyX uses ca. 8 MB)


I can't believe that. Without anything loaded LyX uses around 15 MB of 
RAM. When a big document is loaded, say UserGuide.lyx, add 10 MB to 
that. This is on Windows. I guess the 8 MB doesn't count the Qt dlls in 
memory. This is fair as long as you use them for other software (eg. KDE).


Abdel.

Re: Lyx in Podcast

[Abdelrazak Younes]

G. Milde wrote:

On 20.06.08, Wolfgang Engelmann wrote:

There are two items where I am not sure I know enough. 



One is the hardware prerequisites. There are a few remarks in the web,
but not much detailled hints. I do realize that it depends much on what
one plans to do (text only versus many figures, presentations (powerdot
and the like) with large figures etc). 


I do not know about the minimum, but LyX 1.5.5 runs well on my modest
work PC 


* with 250 MB RAM (whereof LyX uses ca. 8 MB)


I can't believe that. Without anything loaded LyX uses around 15 MB of 
RAM. When a big document is loaded, say UserGuide.lyx, add 10 MB to 
that. This is on Windows. I guess the 8 MB doesn't count the Qt dlls in 
memory. This is fair as long as you use them for other software (eg. KDE).


Abdel.

Re: Short indexes reference

[Abdelrazak Younes]

Pavel Sanda wrote:

Thnx, Abdel, but it doesn't work - perhaps is because of the italian version
(lyx 1.5.5)


do you have the cursor exactly before the inset (box)?


Ctrl-i should work also within the inset. Just for clarification, Ctrl-i 
means press the 'Ctrl' and 'i' key at the same time.


Abdel.

Re: no way to obtain an SVG preview of the correct size

[Abdelrazak Younes]

G. Milde wrote:

On 17.06.08, Abdelrazak Younes wrote:

My guess is, that svg support in the image loader is new in QT 4.4 and
hence this option worked with QT  4.4.


Svg support is not new, it is brought by the QtSvg4 library. AFAIK, we  
don't link with this library. My guess is that your distribution (or  
you?) explicitely link to it. 



But maybe you're right that something has changed in Qt4.4 and that svg
is automatically loaded with QtGui. This needs more investigation...


So it might rather be the LyX 1.5.x  1.5.5 upgrade that introduced the
native svg display.


No, we didn't do that :-)



I have 1.5.5 from the Debian/testing binary package, so I did not link to
QtSvg4 but cannot speak for my distribution.


I just tested with trunk and svg file are loaded directly!

Conclusion: this is a change in Qt4.4 that svg file are loaded directly 
with the need to link to QtSvg!




It seems like you really have to save your svg clipped to the right size.


With the external inset, you can define a conversion method for latex.  


AFAIK, the external inset has no preview,


If you choose the RasterImage template it has.


so I can just as good use the
graphics inset and turn of the display in LyX. 
(Did this change recently?)


If you choose the RasterImage template, the external inset provides the 
same functionality as the graphics inset. I agree this duplication of 
feature is very confusing and we should aim at merging the two inset 
somewhat. The advantage of the external inset is that, if you create a 
new template, you can play with how the transformation needed for latex 
export.


Abdel.

Re: no way to obtain an SVG preview of the correct size

[Abdelrazak Younes]

Abdelrazak Younes wrote:
Conclusion: this is a change in Qt4.4 that svg file are loaded directly 
with the need to link to QtSvg!


Hum... one should read: this is a change in Qt4.4 that svg file*s* are 
loaded directly with*out* the need to link to QtSvg!


Abdel.

Re: no way to obtain an SVG preview of the correct size

[Abdelrazak Younes]

G. Milde wrote:

On 18.06.08, Abdelrazak Younes wrote:

G. Milde wrote:

On 17.06.08, Abdelrazak Younes wrote:



My guess is, that svg support in the image loader is new in QT 4.4 and
hence this option worked with QT  4.4.
Svg support is not new, it is brought by the QtSvg4 library. AFAIK, 
we  don't link with this library. 

...

But maybe you're right that something has changed in Qt4.4 and that svg
is automatically loaded with QtGui. This needs more investigation...

So it might rather be the LyX 1.5.x  1.5.5 upgrade that introduced the
native svg display.
Conclusion: this is a change in Qt4.4 that svg files are loaded directly  
without the need to link to QtSvg!


Well, the debug message says 


  The image loader can load the following directly:
  bmp, gif, ico, jpeg, jpg, mng, pbm, pgm, png, ppm, svg, tif, tiff, xbm, xpm, 


This list is the format directly loadable by Qt. LyX polls Qt by calling 
 QImageReader::supportedImageFormats(). If a Qt plugin adds eps format 
for example, it will be recognized automatically by LyX and won't need 
any conversion before being shown on screen.




  Of these, LyX recognises the following formats:
  bmp, gif, jpg, jpg, pbm, pgm, png, ppm, svg, tiff, xbm, xpm


And this is a subset of the former list that LyX knows about.



Does Qt image loader really find automatically which of the supported
formats are also recognised by LyX or is there some place in the lyx code
where this list is hard-coded?


The formats are the one defined in the Converter dialogs as result of 
the configure script. We should probably add a definition for SVG in 
there if that is not already the case.


If you choose the RasterImage template, the external inset provides the  
same functionality as the graphics inset. I agree this duplication of  
feature is very confusing and we should aim at merging the two inset  
somewhat. The advantage of the external inset is that, if you create a  
new template, you can play with how the transformation needed for latex  
export.


Can you also play with the transformation before the display in LyX to
override the as-is rendering of an SVG file?


It maybe possible to add this capability with the help of some script 
but I don't think this is possible right now. But you always can use the 
display option for scaling, rotation and clipping. Beware that the scale 
option for LateX is different from the LyX option.




Does the RasterImage template work for vector images as well (despite its
name)


Yes, seems to. We should probably change the naming.


or will the image be transformed to a bitmap?


That depends if it is directly showable by Qt (like in the svg case) or 
not. In the second case, LyX will transform the image to a raster image 
format as defined by the converters for this format before showing it on 
screen.


Abdel.

Re: Short indexes reference

[Abdelrazak Younes]

Pavel Sanda wrote:

Thnx, Abdel, but it doesn't work - perhaps is because of the italian version
(lyx 1.5.5)


do you have the cursor exactly before the inset (box)?


Ctrl-i should work also within the inset. Just for clarification, Ctrl-i 
means press the 'Ctrl' and 'i' key at the same time.


Abdel.

Re: no way to obtain an SVG preview of the correct size

[Abdelrazak Younes]

G. Milde wrote:

On 17.06.08, Abdelrazak Younes wrote:

My guess is, that svg support in the image loader is new in QT 4.4 and
hence this option worked with QT  4.4.


Svg support is not new, it is brought by the QtSvg4 library. AFAIK, we  
don't link with this library. My guess is that your distribution (or  
you?) explicitely link to it. 



But maybe you're right that something has changed in Qt4.4 and that svg
is automatically loaded with QtGui. This needs more investigation...


So it might rather be the LyX 1.5.x  1.5.5 upgrade that introduced the
native svg display.


No, we didn't do that :-)



I have 1.5.5 from the Debian/testing binary package, so I did not link to
QtSvg4 but cannot speak for my distribution.


I just tested with trunk and svg file are loaded directly!

Conclusion: this is a change in Qt4.4 that svg file are loaded directly 
with the need to link to QtSvg!




It seems like you really have to save your svg clipped to the right size.


With the external inset, you can define a conversion method for latex.  


AFAIK, the external inset has no preview,


If you choose the RasterImage template it has.


so I can just as good use the
graphics inset and turn of the display in LyX. 
(Did this change recently?)


If you choose the RasterImage template, the external inset provides the 
same functionality as the graphics inset. I agree this duplication of 
feature is very confusing and we should aim at merging the two inset 
somewhat. The advantage of the external inset is that, if you create a 
new template, you can play with how the transformation needed for latex 
export.


Abdel.

Re: no way to obtain an SVG preview of the correct size

[Abdelrazak Younes]

Abdelrazak Younes wrote:
Conclusion: this is a change in Qt4.4 that svg file are loaded directly 
with the need to link to QtSvg!


Hum... one should read: this is a change in Qt4.4 that svg file*s* are 
loaded directly with*out* the need to link to QtSvg!


Abdel.

Re: no way to obtain an SVG preview of the correct size

[Abdelrazak Younes]

G. Milde wrote:

On 18.06.08, Abdelrazak Younes wrote:

G. Milde wrote:

On 17.06.08, Abdelrazak Younes wrote:



My guess is, that svg support in the image loader is new in QT 4.4 and
hence this option worked with QT  4.4.
Svg support is not new, it is brought by the QtSvg4 library. AFAIK, 
we  don't link with this library. 

...

But maybe you're right that something has changed in Qt4.4 and that svg
is automatically loaded with QtGui. This needs more investigation...

So it might rather be the LyX 1.5.x  1.5.5 upgrade that introduced the
native svg display.
Conclusion: this is a change in Qt4.4 that svg files are loaded directly  
without the need to link to QtSvg!


Well, the debug message says 


  The image loader can load the following directly:
  bmp, gif, ico, jpeg, jpg, mng, pbm, pgm, png, ppm, svg, tif, tiff, xbm, xpm, 


This list is the format directly loadable by Qt. LyX polls Qt by calling 
 QImageReader::supportedImageFormats(). If a Qt plugin adds eps format 
for example, it will be recognized automatically by LyX and won't need 
any conversion before being shown on screen.




  Of these, LyX recognises the following formats:
  bmp, gif, jpg, jpg, pbm, pgm, png, ppm, svg, tiff, xbm, xpm


And this is a subset of the former list that LyX knows about.



Does Qt image loader really find automatically which of the supported
formats are also recognised by LyX or is there some place in the lyx code
where this list is hard-coded?


The formats are the one defined in the Converter dialogs as result of 
the configure script. We should probably add a definition for SVG in 
there if that is not already the case.


If you choose the RasterImage template, the external inset provides the  
same functionality as the graphics inset. I agree this duplication of  
feature is very confusing and we should aim at merging the two inset  
somewhat. The advantage of the external inset is that, if you create a  
new template, you can play with how the transformation needed for latex  
export.


Can you also play with the transformation before the display in LyX to
override the as-is rendering of an SVG file?


It maybe possible to add this capability with the help of some script 
but I don't think this is possible right now. But you always can use the 
display option for scaling, rotation and clipping. Beware that the scale 
option for LateX is different from the LyX option.




Does the RasterImage template work for vector images as well (despite its
name)


Yes, seems to. We should probably change the naming.


or will the image be transformed to a bitmap?


That depends if it is directly showable by Qt (like in the svg case) or 
not. In the second case, LyX will transform the image to a raster image 
format as defined by the converters for this format before showing it on 
screen.


Abdel.

Re: Short indexes reference

[Abdelrazak Younes]

Pavel Sanda wrote:

Thnx, Abdel, but it doesn't work - perhaps is because of the italian version
(lyx 1.5.5)


do you have the cursor exactly before the inset (box)?


Ctrl-i should work also within the inset. Just for clarification, Ctrl-i 
means "press the 'Ctrl' and 'i' key at the same time.


Abdel.

Re: no way to obtain an SVG preview of the correct size

[Abdelrazak Younes]

G. Milde wrote:

On 17.06.08, Abdelrazak Younes wrote:

My guess is, that svg support in the image loader is new in QT 4.4 and
hence this option worked with QT < 4.4.


Svg support is not new, it is brought by the QtSvg4 library. AFAIK, we  
don't link with this library. My guess is that your distribution (or  
you?) explicitely link to it. 



But maybe you're right that something has changed in Qt4.4 and that svg
is automatically loaded with QtGui. This needs more investigation...


So it might rather be the LyX 1.5.x > 1.5.5 upgrade that introduced the
"native" svg display.


No, we didn't do that :-)



I have 1.5.5 from the Debian/testing binary package, so I did not link to
QtSvg4 but cannot speak for my distribution.


I just tested with trunk and svg file are loaded directly!

Conclusion: this is a change in Qt4.4 that svg file are loaded directly 
with the need to link to QtSvg!




It seems like you really have to save your svg clipped to the right size.


With the external inset, you can define a conversion method for latex.  


AFAIK, the external inset has no preview,


If you choose the RasterImage template it has.


so I can just as good use the
graphics inset and turn of the display in LyX. 
(Did this change recently?)


If you choose the RasterImage template, the external inset provides the 
same functionality as the graphics inset. I agree this duplication of 
feature is very confusing and we should aim at merging the two inset 
somewhat. The advantage of the external inset is that, if you create a 
new template, you can play with how the transformation needed for latex 
export.


Abdel.

Re: no way to obtain an SVG preview of the correct size

[Abdelrazak Younes]

Abdelrazak Younes wrote:
Conclusion: this is a change in Qt4.4 that svg file are loaded directly 
with the need to link to QtSvg!


Hum... one should read: this is a change in Qt4.4 that svg file*s* are 
loaded directly with*out* the need to link to QtSvg!


Abdel.

Re: no way to obtain an SVG preview of the correct size

[Abdelrazak Younes]

G. Milde wrote:

On 18.06.08, Abdelrazak Younes wrote:

G. Milde wrote:

On 17.06.08, Abdelrazak Younes wrote:



My guess is, that svg support in the image loader is new in QT 4.4 and
hence this option worked with QT < 4.4.
Svg support is not new, it is brought by the QtSvg4 library. AFAIK, 
we  don't link with this library. 

...

But maybe you're right that something has changed in Qt4.4 and that svg
is automatically loaded with QtGui. This needs more investigation...

So it might rather be the LyX 1.5.x > 1.5.5 upgrade that introduced the
"native" svg display.
Conclusion: this is a change in Qt4.4 that svg files are loaded directly  
without the need to link to QtSvg!


Well, the debug message says 


  The image loader can load the following directly:
  bmp, gif, ico, jpeg, jpg, mng, pbm, pgm, png, ppm, svg, tif, tiff, xbm, xpm, 


This list is the format directly loadable by Qt. LyX polls Qt by calling 
 QImageReader::supportedImageFormats(). If a Qt plugin adds eps format 
for example, it will be recognized automatically by LyX and won't need 
any conversion before being shown on screen.




  Of these, LyX recognises the following formats:
  bmp, gif, jpg, jpg, pbm, pgm, png, ppm, svg, tiff, xbm, xpm


And this is a subset of the former list that LyX knows about.



Does Qt image loader really find automatically which of the supported
formats are also recognised by LyX or is there some place in the lyx code
where this list is hard-coded?


The formats are the one defined in the Converter dialogs as result of 
the configure script. We should probably add a definition for SVG in 
there if that is not already the case.


If you choose the RasterImage template, the external inset provides the  
same functionality as the graphics inset. I agree this duplication of  
feature is very confusing and we should aim at merging the two inset  
somewhat. The advantage of the external inset is that, if you create a  
new template, you can play with how the transformation needed for latex  
export.


Can you also play with the transformation before the display in LyX to
override the "as-is" rendering of an SVG file?


It maybe possible to add this capability with the help of some script 
but I don't think this is possible right now. But you always can use the 
display option for scaling, rotation and clipping. Beware that the scale 
option for LateX is different from the LyX option.




Does the RasterImage template work for vector images as well (despite its
name)


Yes, seems to. We should probably change the naming.


or will the image be transformed to a bitmap?


That depends if it is directly showable by Qt (like in the svg case) or 
not. In the second case, LyX will transform the image to a raster image 
format as defined by the converters for this format before showing it on 
screen.


Abdel.

Re: no way to obtain an SVG preview of the correct size

[Abdelrazak Younes]

TP wrote:

Abdelrazak Younes wrote:


ppm or png can be equally shown within LyX.


Ok.


AFAIK, the semicolon is not for redirection but for command separation,
you might want to use '' instead.


Yes, I mean that I used the semicolon, because the following does not work
in command line:

$ inkscape $$i --export-png=/dev/stdout|convert - $$o


Just to be sure, are you aware that the $$i and $$o syntax is a LyX 
defined one? LyX will automatically replace that with the input and 
output file names



By the way, what display option did you choose 
in the external inset configuration dialog?


What do you mean?


Sorry, I see now that your are using 1.6svn. The external-template file 
format has changed in 1.6, see the release note and the new file. You 
need to put a new 'Preview' tag. In your case, adding 'Preview Graphics' 
should do.


Abdel.

Re: no way to obtain an SVG preview of the correct size

[Abdelrazak Younes]

G. Milde wrote:

On 16.06.08, TP wrote:

It also used to work for me from within LyX. However, a new test with LyX
shows that it no longer works as expected for both display in LyX and PDF
export.

Starting LyX with the graphics conversion debug option,

lyx -dbg
   List of supported debug flags:
 0 none  No debugging message
   ...	 
   2097152 graphics  Graphics conversion and loading


lyx -dbg 2097152
   
and loading a fresh svg picture on A4 canvas showed the (most probable)

reason:

   ...
The file contains svg format data.
   
   The image loader can load the following directly:
   bmp, gif, ico, jpeg, jpg, mng, pbm, pgm, png, ppm, svg, tif, tiff, xbm, xpm, 
   Of these, LyX recognises the following formats:

   bmp, gif, jpg, jpg, pbm, pgm, png, ppm, svg, tiff, xbm, xpm
   
   	No conversion needed (from == to)!

   Loading image.
   Image loading succeeded.
   graphics::Image::getScaledDimensions()
params.scale   : 100
width  : 744
height : 1052
   LoaderQueue: I'm going to sleep

of course the --export-area-drawing option can not have any effect if
there is no export!


Right.


My guess is, that svg support in the image loader is new in QT 4.4 and
hence this option worked with QT  4.4.


Svg support is not new, it is brought by the QtSvg4 library. AFAIK, we 
don't link with this library. My guess is that your distribution (or 
you?) explicitely link to it. But maybe you're right that something has 
changed in Qt4.4 and that svg is automatically loaded with QtGui. This 
needs more investigation...



It seems like you really have to save your svg clipped to the right size.


With the external inset, you can define a conversion method for latex. 
As far as LyX-1.6 previewing is concerned, you can make use of the scale 
screen option.


Abdel.

Re: Short indexes reference

[Abdelrazak Younes]

MonAmiPierrot wrote:

Another - silly - question: how can I BY KEYBOARD open (and close) an index
box or a TeX box in Lyx?


Ctrl-i

Abdel.

Re: no way to obtain an SVG preview of the correct size

[Abdelrazak Younes]

TP wrote:

Abdelrazak Younes wrote:


TP wrote:

Abdelrazak Younes wrote:


ppm or png can be equally shown within LyX.

Ok.


AFAIK, the semicolon is not for redirection but for command separation,
you might want to use '' instead.

Yes, I mean that I used the semicolon, because the following does not
work in command line:

$ inkscape $$i --export-png=/dev/stdout|convert - $$o

Just to be sure, are you aware that the $$i and $$o syntax is a LyX
defined one? LyX will automatically replace that with the input and
output file names


Yes I know it. I have replaced $$i by a svg file (say, toto.svg), and $$o by
a png file (say, toto.png). In the man page of convert, one can read:

Specify ?file? as ?-? for standard input or output.

But I obtain an error:

$ inkscape toto.svg --export-png=/dev/stdout|convert - toto.png
convert: Improper image header `/tmp/magick-XXgTxmEa'.
convert: missing an image filename `toto.png'.


I cannot help you there.



By the way, what display option did you choose
in the external inset configuration dialog?

What do you mean?

Sorry, I see now that your are using 1.6svn. The external-template file
format has changed in 1.6, see the release note and the new file. You
need to put a new 'Preview' tag. In your case, adding 'Preview Graphics'
should do.


I have just updated my svn copy.
Actually the REALEASE-NOTES file contains a line about this new tag:

The external template format recognize now a new tag: 'Preview'. This tag
is
used to define how an external material should be previewed in LyX. For more
detail,
see the 'external_templates' file in the resource directory of LyX.

But no preview tag in ./lib/external_templates... What is the matter?


Are you sure you svn updated everything? including lib/external_templates?

You should see this in the RasterImage template:

# LyX preview options:
# Off: LyX will not attempt to show this material on screen.
# Graphics: LyX will attempt to show this material as-is or via a
#   conversion to a showable format.
# InstantPreview: LyX will attempt to use the 'instant preview'
# mechanism in order to show this material.
Preview Graphics



If I manage to use this keyword, will it change the svg preview behaviour?


If you use 'Preview Graphics', the preview on LyX screen will use the 
same conversion methods as if you used a graphic inset.


Abdel.

Re: no way to obtain an SVG preview of the correct size

[Abdelrazak Younes]

TP wrote:

Abdelrazak Younes wrote:


ppm or png can be equally shown within LyX.


Ok.


AFAIK, the semicolon is not for redirection but for command separation,
you might want to use '' instead.


Yes, I mean that I used the semicolon, because the following does not work
in command line:

$ inkscape $$i --export-png=/dev/stdout|convert - $$o


Just to be sure, are you aware that the $$i and $$o syntax is a LyX 
defined one? LyX will automatically replace that with the input and 
output file names



By the way, what display option did you choose 
in the external inset configuration dialog?


What do you mean?


Sorry, I see now that your are using 1.6svn. The external-template file 
format has changed in 1.6, see the release note and the new file. You 
need to put a new 'Preview' tag. In your case, adding 'Preview Graphics' 
should do.


Abdel.

Re: no way to obtain an SVG preview of the correct size

[Abdelrazak Younes]

G. Milde wrote:

On 16.06.08, TP wrote:

It also used to work for me from within LyX. However, a new test with LyX
shows that it no longer works as expected for both display in LyX and PDF
export.

Starting LyX with the graphics conversion debug option,

lyx -dbg
   List of supported debug flags:
 0 none  No debugging message
   ...	 
   2097152 graphics  Graphics conversion and loading


lyx -dbg 2097152
   
and loading a fresh svg picture on A4 canvas showed the (most probable)

reason:

   ...
The file contains svg format data.
   
   The image loader can load the following directly:
   bmp, gif, ico, jpeg, jpg, mng, pbm, pgm, png, ppm, svg, tif, tiff, xbm, xpm, 
   Of these, LyX recognises the following formats:

   bmp, gif, jpg, jpg, pbm, pgm, png, ppm, svg, tiff, xbm, xpm
   
   	No conversion needed (from == to)!

   Loading image.
   Image loading succeeded.
   graphics::Image::getScaledDimensions()
params.scale   : 100
width  : 744
height : 1052
   LoaderQueue: I'm going to sleep

of course the --export-area-drawing option can not have any effect if
there is no export!


Right.


My guess is, that svg support in the image loader is new in QT 4.4 and
hence this option worked with QT  4.4.


Svg support is not new, it is brought by the QtSvg4 library. AFAIK, we 
don't link with this library. My guess is that your distribution (or 
you?) explicitely link to it. But maybe you're right that something has 
changed in Qt4.4 and that svg is automatically loaded with QtGui. This 
needs more investigation...



It seems like you really have to save your svg clipped to the right size.


With the external inset, you can define a conversion method for latex. 
As far as LyX-1.6 previewing is concerned, you can make use of the scale 
screen option.


Abdel.

Re: Short indexes reference

[Abdelrazak Younes]

MonAmiPierrot wrote:

Another - silly - question: how can I BY KEYBOARD open (and close) an index
box or a TeX box in Lyx?


Ctrl-i

Abdel.

Re: no way to obtain an SVG preview of the correct size

[Abdelrazak Younes]

TP wrote:

Abdelrazak Younes wrote:


TP wrote:

Abdelrazak Younes wrote:


ppm or png can be equally shown within LyX.

Ok.


AFAIK, the semicolon is not for redirection but for command separation,
you might want to use '' instead.

Yes, I mean that I used the semicolon, because the following does not
work in command line:

$ inkscape $$i --export-png=/dev/stdout|convert - $$o

Just to be sure, are you aware that the $$i and $$o syntax is a LyX
defined one? LyX will automatically replace that with the input and
output file names


Yes I know it. I have replaced $$i by a svg file (say, toto.svg), and $$o by
a png file (say, toto.png). In the man page of convert, one can read:

Specify ?file? as ?-? for standard input or output.

But I obtain an error:

$ inkscape toto.svg --export-png=/dev/stdout|convert - toto.png
convert: Improper image header `/tmp/magick-XXgTxmEa'.
convert: missing an image filename `toto.png'.


I cannot help you there.



By the way, what display option did you choose
in the external inset configuration dialog?

What do you mean?

Sorry, I see now that your are using 1.6svn. The external-template file
format has changed in 1.6, see the release note and the new file. You
need to put a new 'Preview' tag. In your case, adding 'Preview Graphics'
should do.


I have just updated my svn copy.
Actually the REALEASE-NOTES file contains a line about this new tag:

The external template format recognize now a new tag: 'Preview'. This tag
is
used to define how an external material should be previewed in LyX. For more
detail,
see the 'external_templates' file in the resource directory of LyX.

But no preview tag in ./lib/external_templates... What is the matter?


Are you sure you svn updated everything? including lib/external_templates?

You should see this in the RasterImage template:

# LyX preview options:
# Off: LyX will not attempt to show this material on screen.
# Graphics: LyX will attempt to show this material as-is or via a
#   conversion to a showable format.
# InstantPreview: LyX will attempt to use the 'instant preview'
# mechanism in order to show this material.
Preview Graphics



If I manage to use this keyword, will it change the svg preview behaviour?


If you use 'Preview Graphics', the preview on LyX screen will use the 
same conversion methods as if you used a graphic inset.


Abdel.

Re: no way to obtain an SVG preview of the correct size

[Abdelrazak Younes]

TP wrote:

Abdelrazak Younes wrote:


ppm or png can be equally shown within LyX.


Ok.


AFAIK, the semicolon is not for redirection but for command separation,
you might want to use '>' instead.


Yes, I mean that I used the semicolon, because the following does not work
in command line:

$ inkscape $$i --export-png=/dev/stdout|convert - $$o


Just to be sure, are you aware that the $$i and $$o syntax is a LyX 
defined one? LyX will automatically replace that with the input and 
output file names



By the way, what display option did you choose 
in the external inset configuration dialog?


What do you mean?


Sorry, I see now that your are using 1.6svn. The external-template file 
format has changed in 1.6, see the release note and the new file. You 
need to put a new 'Preview' tag. In your case, adding 'Preview Graphics' 
should do.


Abdel.

Re: no way to obtain an SVG preview of the correct size

[Abdelrazak Younes]

G. Milde wrote:

On 16.06.08, TP wrote:

It also used to work for me from within LyX. However, a new test with LyX
shows that it no longer works as expected for both display in LyX and PDF
export.

Starting LyX with the graphics conversion debug option,

   > lyx -dbg
   List of supported debug flags:
 0 none  No debugging message
   ...	 
   2097152 graphics  Graphics conversion and loading


   > lyx -dbg 2097152
   
and loading a fresh svg picture on A4 canvas showed the (most probable)

reason:

   ...
The file contains svg format data.
   
   The image loader can load the following directly:
   bmp, gif, ico, jpeg, jpg, mng, pbm, pgm, png, ppm, svg, tif, tiff, xbm, xpm, 
   Of these, LyX recognises the following formats:

   bmp, gif, jpg, jpg, pbm, pgm, png, ppm, svg, tiff, xbm, xpm
   
   	No conversion needed (from == to)!

   Loading image.
   Image loading succeeded.
   graphics::Image::getScaledDimensions()
params.scale   : 100
width  : 744
height : 1052
   LoaderQueue: I'm going to sleep

of course the --export-area-drawing option can not have any effect if
there is no export!


Right.


My guess is, that svg support in the image loader is new in QT 4.4 and
hence this option worked with QT < 4.4.


Svg support is not new, it is brought by the QtSvg4 library. AFAIK, we 
don't link with this library. My guess is that your distribution (or 
you?) explicitely link to it. But maybe you're right that something has 
changed in Qt4.4 and that svg is automatically loaded with QtGui. This 
needs more investigation...



It seems like you really have to save your svg clipped to the right size.


With the external inset, you can define a conversion method for latex. 
As far as LyX-1.6 previewing is concerned, you can make use of the scale 
screen option.


Abdel.

Re: Short indexes reference

[Abdelrazak Younes]

MonAmiPierrot wrote:

Another - silly - question: how can I BY KEYBOARD open (and close) an index
box or a TeX box in Lyx?


Ctrl-i

Abdel.

Re: no way to obtain an SVG preview of the correct size

[Abdelrazak Younes]

TP wrote:

Abdelrazak Younes wrote:


TP wrote:

Abdelrazak Younes wrote:


ppm or png can be equally shown within LyX.

Ok.


AFAIK, the semicolon is not for redirection but for command separation,
you might want to use '>' instead.

Yes, I mean that I used the semicolon, because the following does not
work in command line:

$ inkscape $$i --export-png=/dev/stdout|convert - $$o

Just to be sure, are you aware that the $$i and $$o syntax is a LyX
defined one? LyX will automatically replace that with the input and
output file names


Yes I know it. I have replaced $$i by a svg file (say, toto.svg), and $$o by
a png file (say, toto.png). In the man page of convert, one can read:

"Specify ?file? as ?-? for standard input or output."

But I obtain an error:

$ inkscape toto.svg --export-png=/dev/stdout|convert - toto.png
convert: Improper image header `/tmp/magick-XXgTxmEa'.
convert: missing an image filename `toto.png'.


I cannot help you there.



By the way, what display option did you choose
in the external inset configuration dialog?

What do you mean?

Sorry, I see now that your are using 1.6svn. The external-template file
format has changed in 1.6, see the release note and the new file. You
need to put a new 'Preview' tag. In your case, adding 'Preview Graphics'
should do.


I have just updated my svn copy.
Actually the REALEASE-NOTES file contains a line about this new tag:

"The external template format recognize now a new tag: 'Preview'. This tag
is
used to define how an external material should be previewed in LyX. For more
detail,
see the 'external_templates' file in the resource directory of LyX."

But no "preview" tag in ./lib/external_templates... What is the matter?


Are you sure you svn updated everything? including lib/external_templates?

You should see this in the RasterImage template:

# LyX preview options:
# Off: LyX will not attempt to show this material on screen.
# Graphics: LyX will attempt to show this material as-is or via a
#   conversion to a showable format.
# InstantPreview: LyX will attempt to use the 'instant preview'
# mechanism in order to show this material.
Preview Graphics



If I manage to use this keyword, will it change the svg preview behaviour?


If you use 'Preview Graphics', the preview on LyX screen will use the 
same conversion methods as if you used a graphic inset.


Abdel.

Re: no way to obtain an SVG preview of the correct size

[Abdelrazak Younes]

Tribulations Parallèles wrote:
So, contrary to what is said in the LyX Wiki, it seems that the important 
converter for the preview is svg=PPM.


ppm or png can be equally shown within LyX.

I have tried to keep the orginal 
convertDefault.py, and defined a filter svg=PPM with the following command:


inkscape $$i --export-png=$$o.png;convert $$o.png $$o

(the redirection does not seem to work in command line, I have not found 
another solution than the semicolon in command line).


AFAIK, the semicolon is not for redirection but for command separation, 
you might want to use '' instead. But I am not sure that this syntax is 
understood by LyX built-in command interpreter. You should probably 
create a helper script with python (say svg2ppm.py) where you call the 
two command above. But I am not sure this is the problem as, as I said, 
png is understood by LyX. By the way, what display option did you choose 
in the external inset configuration dialog?

Maybe you could send your addition to external-template to the list.

Abdel.

Re: no way to obtain an SVG preview of the correct size

[Abdelrazak Younes]

Tribulations Parallèles wrote:
So, contrary to what is said in the LyX Wiki, it seems that the important 
converter for the preview is svg=PPM.


ppm or png can be equally shown within LyX.

I have tried to keep the orginal 
convertDefault.py, and defined a filter svg=PPM with the following command:


inkscape $$i --export-png=$$o.png;convert $$o.png $$o

(the redirection does not seem to work in command line, I have not found 
another solution than the semicolon in command line).


AFAIK, the semicolon is not for redirection but for command separation, 
you might want to use '' instead. But I am not sure that this syntax is 
understood by LyX built-in command interpreter. You should probably 
create a helper script with python (say svg2ppm.py) where you call the 
two command above. But I am not sure this is the problem as, as I said, 
png is understood by LyX. By the way, what display option did you choose 
in the external inset configuration dialog?

Maybe you could send your addition to external-template to the list.

Abdel.

Re: no way to obtain an SVG preview of the correct size

[Abdelrazak Younes]

Tribulations Parallèles wrote:
So, contrary to what is said in the LyX Wiki, it seems that the important 
converter for the preview is svg=>PPM.


ppm or png can be equally shown within LyX.

I have tried to keep the orginal 
convertDefault.py, and defined a filter svg=>PPM with the following command:


inkscape $$i --export-png=$$o.png;convert $$o.png $$o

(the redirection does not seem to work in command line, I have not found 
another solution than the semicolon in command line).


AFAIK, the semicolon is not for redirection but for command separation, 
you might want to use '>' instead. But I am not sure that this syntax is 
understood by LyX built-in command interpreter. You should probably 
create a helper script with python (say svg2ppm.py) where you call the 
two command above. But I am not sure this is the problem as, as I said, 
png is understood by LyX. By the way, what display option did you choose 
in the external inset configuration dialog?

Maybe you could send your addition to external-template to the list.

Abdel.

Re: External fig material and pdflatex

[Abdelrazak Younes]

Georg Baum wrote:

Abdelrazak Younes wrote:


I got this error when I try to export with pdflatex:

Traceback (most recent call last):
   File C:/devel/lyx/trunk/lib/scripts/fig2pdftex.py, line 81, in
   module
 tmp = open(epsfile + '.??', 'w')
IOError: [Errno 2] No such file or directory:
'0C__perso_these_fig_Avion.pstex.??'
Error: Cannot convert file

An error occurred whilst running python -tt
C:/devel/lyx/trunk/lib/scripts/fig2pdf


I guess that your OS does not like the question marks in the file name.
Instead of using this strange name it would be better to use mkstemp() from
lyxpreview_tools.py to create a temporary file that deletes itself after
usage.


That did it!

Thanks,
Abdel.

Re: External fig material and pdflatex

[Abdelrazak Younes]

Georg Baum wrote:

Abdelrazak Younes wrote:


I got this error when I try to export with pdflatex:

Traceback (most recent call last):
   File C:/devel/lyx/trunk/lib/scripts/fig2pdftex.py, line 81, in
   module
 tmp = open(epsfile + '.??', 'w')
IOError: [Errno 2] No such file or directory:
'0C__perso_these_fig_Avion.pstex.??'
Error: Cannot convert file

An error occurred whilst running python -tt
C:/devel/lyx/trunk/lib/scripts/fig2pdf


I guess that your OS does not like the question marks in the file name.
Instead of using this strange name it would be better to use mkstemp() from
lyxpreview_tools.py to create a temporary file that deletes itself after
usage.


That did it!

Thanks,
Abdel.

Re: External fig material and pdflatex

[Abdelrazak Younes]

Georg Baum wrote:

Abdelrazak Younes wrote:


I got this error when I try to export with pdflatex:

Traceback (most recent call last):
   File "C:/devel/lyx/trunk/lib/scripts/fig2pdftex.py", line 81, in
   
 tmp = open(epsfile + '.??', 'w')
IOError: [Errno 2] No such file or directory:
'0C__perso_these_fig_Avion.pstex.??'
Error: Cannot convert file

An error occurred whilst running python -tt
"C:/devel/lyx/trunk/lib/scripts/fig2pdf


I guess that your OS does not like the question marks in the file name.
Instead of using this strange name it would be better to use mkstemp() from
lyxpreview_tools.py to create a temporary file that deletes itself after
usage.


That did it!

Thanks,
Abdel.

External fig material and pdflatex

[Abdelrazak Younes]

Hello,

Does someone know if there is a version of fig2dev that does pdftex in 
addition to pstex? I am trying to use xfig drawing directly thanks to 
the external material inset but that works only for plain LateX, not for 
pdflatex.


I am using the precompiled fig2dev package for Windows found at the JFig 
homepage:

http://tams-www.informatik.uni-hamburg.de/applets/jfig/download.html
http://tams-www.informatik.uni-hamburg.de/applets/jfig/archive/fig2dev3.2.3d-windows.zip

So this comes from transfig 3.2.3d and, AFAICS this is the latest version:
ftp://ftp.x.org/contrib/applications/drawing_tools/transfig/

Am I missing something or does the external xfig support is not prepared 
for pdflatex?


Abdel.

Re: External fig material and pdflatex

[Abdelrazak Younes]

Hi Georg!

Georg Baum wrote:

Abdelrazak Younes wrote:


Hello,

Does someone know if there is a version of fig2dev that does pdftex in
addition to pstex?


Yes, newer versions support pdftex. And Angus implemented a workaround for
older versions in fig2pdftex.py, so it should not matter whether your
fig2dev supports pdftex or not.


I got this error when I try to export with pdflatex:

Traceback (most recent call last):
  File C:/devel/lyx/trunk/lib/scripts/fig2pdftex.py, line 81, in module
tmp = open(epsfile + '.??', 'w')
IOError: [Errno 2] No such file or directory: 
'0C__perso_these_fig_Avion.pstex.??'

Error: Cannot convert file

An error occurred whilst running python -tt 
C:/devel/lyx/trunk/lib/scripts/fig2pdf




I am trying to use xfig drawing directly thanks to 
the external material inset but that works only for plain LateX, not for

pdflatex.


That is supposed to work out of the box.


So this comes from transfig 3.2.3d and, AFAICS this is the latest version:


No. 3.2.5 is current, but that should not matter because of the workaround.


Right, I see that know, unfortunately this version is not available on 
Windows.


Thanks,
Abdel.

Re: External fig material and pdflatex

[Abdelrazak Younes]

Abdelrazak Younes wrote:

Hi Georg!

Georg Baum wrote:

Abdelrazak Younes wrote:


Hello,

Does someone know if there is a version of fig2dev that does pdftex in
addition to pstex?


Yes, newer versions support pdftex. And Angus implemented a workaround 
for

older versions in fig2pdftex.py, so it should not matter whether your
fig2dev supports pdftex or not.


I got this error when I try to export with pdflatex:


I just tried to use the fig2pdftex script manually and it seems to work 
fine so this is probably a bug in LyX. Maybe the reason is that I have 
an eps version of this fig file in the same directory? OK, I'll 
investigate a bit more and will try 1.5 to see if it works.


Abdel.

Re: External fig material and pdflatex

[Abdelrazak Younes]

Abdelrazak Younes wrote:

Abdelrazak Younes wrote:

Hi Georg!

Georg Baum wrote:

Abdelrazak Younes wrote:


Hello,

Does someone know if there is a version of fig2dev that does pdftex in
addition to pstex?


Yes, newer versions support pdftex. And Angus implemented a 
workaround for

older versions in fig2pdftex.py, so it should not matter whether your
fig2dev supports pdftex or not.


I got this error when I try to export with pdflatex:


I just tried to use the fig2pdftex script manually and it seems to work 
fine


Hum, no, I spoke too fast:

C:\perso\these\figpython -tt 
C:\devel\lyx\trunk\lib\scripts\fig2pdftex.py Avi

on.fig Avion2.pdftex
Traceback (most recent call last):
 File C:\devel\lyx\trunk\lib\scripts\fig2pdftex.py, line 81, in module
   tmp = open(epsfile + '.??', 'w')
IOError: [Errno 2] No such file or directory: 'Avion2.pstex.??'

So the bug seems to be in 'fig2pdftex.py'. I'll bring this matter to the 
devel list.


Abdel.

Re: External fig material and pdflatex

[Abdelrazak Younes]

Abdelrazak Younes wrote:

Georg Baum wrote:
So this comes from transfig 3.2.3d and, AFAICS this is the latest 
version:


No. 3.2.5 is current, but that should not matter because of the 
workaround.


Right, I see that know, unfortunately this version is not available on 
Windows.


I was wrong. The author of WinFIG did the port. You'll get fig2dev 3.2.5 
alpha 7 inside the WinFIG package (see 
http://www.schmidt-web-berlin.de/winfig/downloads.shtml).


Abdel.

External fig material and pdflatex

[Abdelrazak Younes]

Hello,

Does someone know if there is a version of fig2dev that does pdftex in 
addition to pstex? I am trying to use xfig drawing directly thanks to 
the external material inset but that works only for plain LateX, not for 
pdflatex.


I am using the precompiled fig2dev package for Windows found at the JFig 
homepage:

http://tams-www.informatik.uni-hamburg.de/applets/jfig/download.html
http://tams-www.informatik.uni-hamburg.de/applets/jfig/archive/fig2dev3.2.3d-windows.zip

So this comes from transfig 3.2.3d and, AFAICS this is the latest version:
ftp://ftp.x.org/contrib/applications/drawing_tools/transfig/

Am I missing something or does the external xfig support is not prepared 
for pdflatex?


Abdel.

Re: External fig material and pdflatex

[Abdelrazak Younes]

Hi Georg!

Georg Baum wrote:

Abdelrazak Younes wrote:


Hello,

Does someone know if there is a version of fig2dev that does pdftex in
addition to pstex?


Yes, newer versions support pdftex. And Angus implemented a workaround for
older versions in fig2pdftex.py, so it should not matter whether your
fig2dev supports pdftex or not.


I got this error when I try to export with pdflatex:

Traceback (most recent call last):
  File C:/devel/lyx/trunk/lib/scripts/fig2pdftex.py, line 81, in module
tmp = open(epsfile + '.??', 'w')
IOError: [Errno 2] No such file or directory: 
'0C__perso_these_fig_Avion.pstex.??'

Error: Cannot convert file

An error occurred whilst running python -tt 
C:/devel/lyx/trunk/lib/scripts/fig2pdf




I am trying to use xfig drawing directly thanks to 
the external material inset but that works only for plain LateX, not for

pdflatex.


That is supposed to work out of the box.


So this comes from transfig 3.2.3d and, AFAICS this is the latest version:


No. 3.2.5 is current, but that should not matter because of the workaround.


Right, I see that know, unfortunately this version is not available on 
Windows.


Thanks,
Abdel.

Re: External fig material and pdflatex

[Abdelrazak Younes]

Abdelrazak Younes wrote:

Hi Georg!

Georg Baum wrote:

Abdelrazak Younes wrote:


Hello,

Does someone know if there is a version of fig2dev that does pdftex in
addition to pstex?


Yes, newer versions support pdftex. And Angus implemented a workaround 
for

older versions in fig2pdftex.py, so it should not matter whether your
fig2dev supports pdftex or not.


I got this error when I try to export with pdflatex:


I just tried to use the fig2pdftex script manually and it seems to work 
fine so this is probably a bug in LyX. Maybe the reason is that I have 
an eps version of this fig file in the same directory? OK, I'll 
investigate a bit more and will try 1.5 to see if it works.


Abdel.

Re: External fig material and pdflatex

[Abdelrazak Younes]

Abdelrazak Younes wrote:

Abdelrazak Younes wrote:

Hi Georg!

Georg Baum wrote:

Abdelrazak Younes wrote:


Hello,

Does someone know if there is a version of fig2dev that does pdftex in
addition to pstex?


Yes, newer versions support pdftex. And Angus implemented a 
workaround for

older versions in fig2pdftex.py, so it should not matter whether your
fig2dev supports pdftex or not.


I got this error when I try to export with pdflatex:


I just tried to use the fig2pdftex script manually and it seems to work 
fine


Hum, no, I spoke too fast:

C:\perso\these\figpython -tt 
C:\devel\lyx\trunk\lib\scripts\fig2pdftex.py Avi

on.fig Avion2.pdftex
Traceback (most recent call last):
 File C:\devel\lyx\trunk\lib\scripts\fig2pdftex.py, line 81, in module
   tmp = open(epsfile + '.??', 'w')
IOError: [Errno 2] No such file or directory: 'Avion2.pstex.??'

So the bug seems to be in 'fig2pdftex.py'. I'll bring this matter to the 
devel list.


Abdel.

Re: External fig material and pdflatex

[Abdelrazak Younes]

Abdelrazak Younes wrote:

Georg Baum wrote:
So this comes from transfig 3.2.3d and, AFAICS this is the latest 
version:


No. 3.2.5 is current, but that should not matter because of the 
workaround.


Right, I see that know, unfortunately this version is not available on 
Windows.


I was wrong. The author of WinFIG did the port. You'll get fig2dev 3.2.5 
alpha 7 inside the WinFIG package (see 
http://www.schmidt-web-berlin.de/winfig/downloads.shtml).


Abdel.

External fig material and pdflatex

[Abdelrazak Younes]

Hello,

Does someone know if there is a version of fig2dev that does pdftex in 
addition to pstex? I am trying to use xfig drawing directly thanks to 
the external material inset but that works only for plain LateX, not for 
pdflatex.


I am using the precompiled fig2dev package for Windows found at the JFig 
homepage:

http://tams-www.informatik.uni-hamburg.de/applets/jfig/download.html
http://tams-www.informatik.uni-hamburg.de/applets/jfig/archive/fig2dev3.2.3d-windows.zip

So this comes from transfig 3.2.3d and, AFAICS this is the latest version:
ftp://ftp.x.org/contrib/applications/drawing_tools/transfig/

Am I missing something or does the external xfig support is not prepared 
for pdflatex?


Abdel.

Re: External fig material and pdflatex

[Abdelrazak Younes]

Hi Georg!

Georg Baum wrote:

Abdelrazak Younes wrote:


Hello,

Does someone know if there is a version of fig2dev that does pdftex in
addition to pstex?


Yes, newer versions support pdftex. And Angus implemented a workaround for
older versions in fig2pdftex.py, so it should not matter whether your
fig2dev supports pdftex or not.


I got this error when I try to export with pdflatex:

Traceback (most recent call last):
  File "C:/devel/lyx/trunk/lib/scripts/fig2pdftex.py", line 81, in 
tmp = open(epsfile + '.??', 'w')
IOError: [Errno 2] No such file or directory: 
'0C__perso_these_fig_Avion.pstex.??'

Error: Cannot convert file

An error occurred whilst running python -tt 
"C:/devel/lyx/trunk/lib/scripts/fig2pdf




I am trying to use xfig drawing directly thanks to 
the external material inset but that works only for plain LateX, not for

pdflatex.


That is supposed to work out of the box.


So this comes from transfig 3.2.3d and, AFAICS this is the latest version:


No. 3.2.5 is current, but that should not matter because of the workaround.


Right, I see that know, unfortunately this version is not available on 
Windows.


Thanks,
Abdel.

Re: External fig material and pdflatex

[Abdelrazak Younes]

Abdelrazak Younes wrote:

Hi Georg!

Georg Baum wrote:

Abdelrazak Younes wrote:


Hello,

Does someone know if there is a version of fig2dev that does pdftex in
addition to pstex?


Yes, newer versions support pdftex. And Angus implemented a workaround 
for

older versions in fig2pdftex.py, so it should not matter whether your
fig2dev supports pdftex or not.


I got this error when I try to export with pdflatex:


I just tried to use the fig2pdftex script manually and it seems to work 
fine so this is probably a bug in LyX. Maybe the reason is that I have 
an eps version of this fig file in the same directory? OK, I'll 
investigate a bit more and will try 1.5 to see if it works.


Abdel.

Re: External fig material and pdflatex

[Abdelrazak Younes]

Abdelrazak Younes wrote:

Abdelrazak Younes wrote:

Hi Georg!

Georg Baum wrote:

Abdelrazak Younes wrote:


Hello,

Does someone know if there is a version of fig2dev that does pdftex in
addition to pstex?


Yes, newer versions support pdftex. And Angus implemented a 
workaround for

older versions in fig2pdftex.py, so it should not matter whether your
fig2dev supports pdftex or not.


I got this error when I try to export with pdflatex:


I just tried to use the fig2pdftex script manually and it seems to work 
fine


Hum, no, I spoke too fast:

C:\perso\these\fig>python -tt 
"C:\devel\lyx\trunk\lib\scripts\fig2pdftex.py" Avi

on.fig Avion2.pdftex
Traceback (most recent call last):
 File "C:\devel\lyx\trunk\lib\scripts\fig2pdftex.py", line 81, in 
   tmp = open(epsfile + '.??', 'w')
IOError: [Errno 2] No such file or directory: 'Avion2.pstex.??'

So the bug seems to be in 'fig2pdftex.py'. I'll bring this matter to the 
devel list.


Abdel.

Re: External fig material and pdflatex

[Abdelrazak Younes]

Abdelrazak Younes wrote:

Georg Baum wrote:
So this comes from transfig 3.2.3d and, AFAICS this is the latest 
version:


No. 3.2.5 is current, but that should not matter because of the 
workaround.


Right, I see that know, unfortunately this version is not available on 
Windows.


I was wrong. The author of WinFIG did the port. You'll get fig2dev 3.2.5 
alpha 7 inside the WinFIG package (see 
http://www.schmidt-web-berlin.de/winfig/downloads.shtml).


Abdel.

Re: pgf and external table plot

[Abdelrazak Younes]

Willem van Engen wrote:

[referencing external file inside ERT]


It occurs to me that a simpler solution might be to put an absolute

reference to the file in the ERT. LyX still will not copy it to the
temp directory, but it won't need to.


Hmm that makes sense, good idea :) Is there a way to have the absolute
path where the source lyx files reside expanded by a macro or somehow?


Not in 1.5 AFAIK, in 1.6 you'll have InsetInfo for that kind of information.

Abdel.

Re: pgf and external table plot

[Abdelrazak Younes]

Willem van Engen wrote:

[referencing external file inside ERT]


It occurs to me that a simpler solution might be to put an absolute

reference to the file in the ERT. LyX still will not copy it to the
temp directory, but it won't need to.


Hmm that makes sense, good idea :) Is there a way to have the absolute
path where the source lyx files reside expanded by a macro or somehow?


Not in 1.5 AFAIK, in 1.6 you'll have InsetInfo for that kind of information.

Abdel.

Re: pgf and external table plot

[Abdelrazak Younes]

Willem van Engen wrote:

[referencing external file inside ERT]


It occurs to me that a simpler solution might be to put an absolute

reference to the file in the ERT. LyX still will not copy it to the
temp directory, but it won't need to.


Hmm that makes sense, good idea :) Is there a way to have the absolute
path where the source lyx files reside expanded by a macro or somehow?


Not in 1.5 AFAIK, in 1.6 you'll have InsetInfo for that kind of information.

Abdel.

Re: We need documentation on using layouts in documents

[Abdelrazak Younes]

Steve Litt wrote:

Hi all,


Hello Steve,



In the 7 years I've used LyX, every book had its own layout, and every single 
time, I spent hours tweaking around trying to get my layout visible to the 
document so that I could use my specialized document class.


FYI with Layout modules in 1.6 (courtesy of Richard H.) you will at 
least be able to reuse components of your modified layouts.




What I typically do is:

1) Make the layout file
2) ln -s /bookdir/mybook.layout /home/slitt/.lyx/layouts/mybook.layout
3) Doublecheck the line that says #  \DeclareLaTeXClass[book]{mybook}, make 
sure it matches the filenames.

4) lyx
5) tools-reconfigure
6) exit lyx
7) lyx mybook.lyx

It never shows document class mybook, until I turkey around for hours to get 
it to work. We need documentation on exactly what to do, and how to 
troubleshoot layouts/document classes.


See section 5.2 of the Customization manual. You are welcome to 
complement that part and to send patches to Uwe and to the documentation 
list. That's how it works for documentation.


Abdel.

Re: We need documentation on using layouts in documents

[Abdelrazak Younes]

Steve Litt wrote:

Hi all,


Hello Steve,



In the 7 years I've used LyX, every book had its own layout, and every single 
time, I spent hours tweaking around trying to get my layout visible to the 
document so that I could use my specialized document class.


FYI with Layout modules in 1.6 (courtesy of Richard H.) you will at 
least be able to reuse components of your modified layouts.




What I typically do is:

1) Make the layout file
2) ln -s /bookdir/mybook.layout /home/slitt/.lyx/layouts/mybook.layout
3) Doublecheck the line that says #  \DeclareLaTeXClass[book]{mybook}, make 
sure it matches the filenames.

4) lyx
5) tools-reconfigure
6) exit lyx
7) lyx mybook.lyx

It never shows document class mybook, until I turkey around for hours to get 
it to work. We need documentation on exactly what to do, and how to 
troubleshoot layouts/document classes.


See section 5.2 of the Customization manual. You are welcome to 
complement that part and to send patches to Uwe and to the documentation 
list. That's how it works for documentation.


Abdel.

Re: We need documentation on using layouts in documents

[Abdelrazak Younes]

Steve Litt wrote:

Hi all,


Hello Steve,



In the 7 years I've used LyX, every book had its own layout, and every single 
time, I spent hours tweaking around trying to get my layout visible to the 
document so that I could use my specialized document class.


FYI with Layout modules in 1.6 (courtesy of Richard H.) you will at 
least be able to reuse components of your modified layouts.




What I typically do is:

1) Make the layout file
2) ln -s /bookdir/mybook.layout /home/slitt/.lyx/layouts/mybook.layout
3) Doublecheck the line that says #  \DeclareLaTeXClass[book]{mybook}, make 
sure it matches the filenames.

4) lyx
5) tools->reconfigure
6) exit lyx
7) lyx mybook.lyx

It never shows document class mybook, until I turkey around for hours to get 
it to work. We need documentation on exactly what to do, and how to 
troubleshoot layouts/document classes.


See section 5.2 of the Customization manual. You are welcome to 
complement that part and to send patches to Uwe and to the documentation 
list. That's how it works for documentation.


Abdel.

Re: keystrokes and styles

[Abdelrazak Younes]

RyanC wrote:

G. Milde wrote:

On  2.06.08, RyanC wrote:

 
Particularly, I am interested in whether styles (title, section, 
etc)  can be assigned with keystrokes. 


Yes. See HelpCustomization.

More info should also be available on http://wiki.lyx.org

Existing keybindings depend on the emulation mode, most commonly either
cua or emacs and to some extend also on your locale.

GM

  

Thanks, GM - for your reply.

I had been trying to navigate my way through the documentation, website, 
and Wiki.


I wanted to suggest to the developers (yes, I know that's a different 
list), adopting this keyboard approach for physical styles.


That's already the case for most layouts (what you call style). The 
default keyboard shortcuts are defined in the cua.bind file which you 
will find in the bind/ subdirectory of you LyX installation directory.

The layouts are generally set with Alt-p:
Alt-p 1 chapter
Alt-p 2 section
Alt_p i itemize
...


But it seems 
that the issue is already very complicated. Is there any interest in 
these kinds of suggestions?


Sure, there is bugzilla.lyx.org if you want to report bug or put an 
enhancement request. Please verify that the item is not already present 
before adding it.


Or are there deeply ingrained ways that 
people work with LyX?


Not sure I follow you...

Abdel.

Re: keystrokes and styles

[Abdelrazak Younes]

RyanC wrote:

Abdelrazak Younes wrote:

RyanC wrote:
Or are there deeply ingrained ways that people work with LyX?



Not sure I follow you...


All I meant by this is that there may be established systems and sets of
keystrokes that I am not familiar with .


Right the Alt-p number keys, which I agree are a bit long to type, 
especially using French keyboards.



For me, layouts (or styles) and
F keys are a natural combination. They seem very well fitted.


Well we already use F2 for 'save', F3 for 'search again' and 'F7' to 
launch the spellchecker. As those are pretty standard, I don't think we 
are going to change, but, as I said, you are free to customize your 
personal bind file to use the F keys for layouts.



I'm not an
Emacs/TeX/LyX power user - and for all I know, F keys already have an
important use. But if not, maybe this would be useful idea for LyX in
terms of the user experience...


They are, see above.

Abdel.

Re: keystrokes and styles

[Abdelrazak Younes]

RyanC wrote:

G. Milde wrote:

On  2.06.08, RyanC wrote:

 
Particularly, I am interested in whether styles (title, section, 
etc)  can be assigned with keystrokes. 


Yes. See HelpCustomization.

More info should also be available on http://wiki.lyx.org

Existing keybindings depend on the emulation mode, most commonly either
cua or emacs and to some extend also on your locale.

GM

  

Thanks, GM - for your reply.

I had been trying to navigate my way through the documentation, website, 
and Wiki.


I wanted to suggest to the developers (yes, I know that's a different 
list), adopting this keyboard approach for physical styles.


That's already the case for most layouts (what you call style). The 
default keyboard shortcuts are defined in the cua.bind file which you 
will find in the bind/ subdirectory of you LyX installation directory.

The layouts are generally set with Alt-p:
Alt-p 1 chapter
Alt-p 2 section
Alt_p i itemize
...


But it seems 
that the issue is already very complicated. Is there any interest in 
these kinds of suggestions?


Sure, there is bugzilla.lyx.org if you want to report bug or put an 
enhancement request. Please verify that the item is not already present 
before adding it.


Or are there deeply ingrained ways that 
people work with LyX?


Not sure I follow you...

Abdel.

Re: keystrokes and styles

[Abdelrazak Younes]

RyanC wrote:

Abdelrazak Younes wrote:

RyanC wrote:
Or are there deeply ingrained ways that people work with LyX?



Not sure I follow you...


All I meant by this is that there may be established systems and sets of
keystrokes that I am not familiar with .


Right the Alt-p number keys, which I agree are a bit long to type, 
especially using French keyboards.



For me, layouts (or styles) and
F keys are a natural combination. They seem very well fitted.


Well we already use F2 for 'save', F3 for 'search again' and 'F7' to 
launch the spellchecker. As those are pretty standard, I don't think we 
are going to change, but, as I said, you are free to customize your 
personal bind file to use the F keys for layouts.



I'm not an
Emacs/TeX/LyX power user - and for all I know, F keys already have an
important use. But if not, maybe this would be useful idea for LyX in
terms of the user experience...


They are, see above.

Abdel.

Re: keystrokes and styles

[Abdelrazak Younes]

RyanC wrote:

G. Milde wrote:

On  2.06.08, RyanC wrote:

 
Particularly, I am interested in whether styles (title, section, 
etc)  can be assigned with keystrokes. 


Yes. See Help>Customization.

More info should also be available on http://wiki.lyx.org

Existing keybindings depend on the "emulation mode", most commonly either
"cua" or "emacs" and to some extend also on your locale.

GM

  

Thanks, GM - for your reply.

I had been trying to navigate my way through the documentation, website, 
and Wiki.


I wanted to suggest to the developers (yes, I know that's a different 
list), adopting this keyboard approach for physical styles.


That's already the case for most layouts (what you call style). The 
default keyboard shortcuts are defined in the "cua.bind" file which you 
will find in the "bind/" subdirectory of you LyX installation directory.

The layouts are generally set with Alt-p:
Alt-p 1 chapter
Alt-p 2 section
Alt_p i itemize
...


But it seems 
that the issue is already very complicated. Is there any interest in 
these kinds of suggestions?


Sure, there is bugzilla.lyx.org if you want to report bug or put an 
enhancement request. Please verify that the item is not already present 
before adding it.


Or are there deeply ingrained ways that 
people work with LyX?


Not sure I follow you...

Abdel.

Re: keystrokes and styles

[Abdelrazak Younes]

RyanC wrote:

Abdelrazak Younes wrote:

RyanC wrote:
Or are there deeply ingrained ways that people work with LyX?



Not sure I follow you...


All I meant by this is that there may be established systems and sets of
keystrokes that I am not familiar with .


Right the Alt-p  keys, which I agree are a bit long to type, 
especially using French keyboards.



For me, layouts (or styles) and
F keys are a natural combination. They seem very well fitted.


Well we already use F2 for 'save', F3 for 'search again' and 'F7' to 
launch the spellchecker. As those are pretty standard, I don't think we 
are going to change, but, as I said, you are free to customize your 
personal bind file to use the F keys for layouts.



I'm not an
Emacs/TeX/LyX power user - and for all I know, F keys already have an
important use. But if not, maybe this would be useful idea for LyX in
terms of the user experience...


They are, see above.

Abdel.

Re: Discussion: Labels and parent-child documents

[Abdelrazak Younes]

Nicolás wrote:
You are right in that we may have cross-references between children 
documents. I still think that my proposal of automatically renaming 
labels is a good idea.


Side note FYI: In 1.6 duplicate Labels are not changed automatically but 
they are clearly marked as DUPLICATE in the work area and in the new 
Navigator (former outline pane). So it's easy to spot where the problems 
lie in the document. Also worth of note is that 1.6 won't allow the 
creation of duplicate labels, it will automatically rename the duplicate 
label. Another interesting feature is that broken are marked as BROKEN.


Abdel.

Re: Discussion: Labels and parent-child documents

[Abdelrazak Younes]

G. Milde wrote:

On  3.06.08, Nicolás wrote:

Well, one problem I can see is that this could make cut and paste  
between documents difficult. And it involves a lot of keeping track of  
what's a child of what.



Not really. Note that labels and cross-references are only updated when
we export to latex.


Does this mean that the labels in child file generated by FileExportLatex
will differ depending on whether the export is done from the parent or
the child? (Or, maybe,  depending on whether the child was opened
directly or via the parent file? Or whether the parent file is opened
in lyx at the time of the export?)


No, AFAIK labels are not changed at latex export. The one you see within 
LyX are the one really put in the latex file. Just have a look at 
View-source to make sure of that. In 1.6, the DUPLICATE markers are 
only for screen representation, they are of course not exported to LateX.


Abdel.

[Announce] Sponsoring a LyX project is now possible

[Abdelrazak Younes]

Dear LyX users,

As for all non paid work, the development of new feature exclusively 
depends on the good will of the developers. But we acknowledge that 
there are some features that are badly needed for some users; a new page 
has been set up to answer this need: http://www.lyx.org/Donate


The donation web page will now list some projects with a potential 
developer associated with it (only one for now). Each interested 
developer would use his own PayPal account. He decides himself the 
minimum amount of money to get the project started. Ideas for project 
can be collected from bugzilla (search for enhancement request in 
http://bugzilla.lyx.org) or from the wiki 
(http://wiki.lyx.org/LyX/FeaturePoll).


Therefore we ask you, the LyX user, to participate in the development of 
one or more projects by sponsoring them or by motivating the company or 
organisation you are working for to entirely or partially sponsor the 
development of one or more projects. Here are the rules that will be 
followed for this kind of development:



* All new development happens in trunk (what will become the next stable 
version), there will be no exception for sponsored development. 
Back-porting to an older version is of course possible but should happen 
after.


* There are no special commit rules for sponsored development, the 
source code will be evaluated just as any new code, and being sponsored 
does not mean it has some 'right' to get in regardless of its merit. 
This item needs to be clear to the involved developer and also to the 
people or organisation paying for the development.


* Being sponsored does not mean that the project is reserved to the one 
who is sponsored. Anybody is still free to do what he/she wants.



On behalf of the LyX developers,
Abdel.

Re: Problems with LyX 1.5.5 after MAC OS X update

[Abdelrazak Younes]

Nicola Focci wrote:

2008/6/3 James Sutherland [EMAIL PROTECTED]:


No problem here.  I just installed LyX 1.5.5 with OSX 10.5.3.  I am
running an intel MacBook Pro and a MacBook.



Same problem as George! And the same grey screenshot.
I'm running a six-months-old IMac, 20 monitor and 2.4 Ghz Intel processor,
with OSX 10.5.3
LyX 1.5.4 worked perfectly under the same configuration!


Let me guess: 1.5.4 came with Qt4.3 and 1.5.5 come with Qt4.4...
If so, I think it would make sense to downgrade Qt Bennett.

Abdel.

Re: Discussion: Labels and parent-child documents

[Abdelrazak Younes]

G. Milde wrote:

On  3.06.08, Abdelrazak Younes wrote:

G. Milde wrote:

On  3.06.08, Nicolás wrote:


Well, one problem I can see is that this could make cut and paste   
between documents difficult. And it involves a lot of keeping track 
of  what's a child of what.



Not really. Note that labels and cross-references are only updated when
we export to latex.



Does this mean that the labels in child file generated by FileExportLatex
will differ depending on whether the export is done from the parent or
the child? (Or, maybe,  depending on whether the child was opened
directly or via the parent file? Or whether the parent file is opened
in lyx at the time of the export?)


No, AFAIK labels are not changed at latex export. The one you see within  
LyX are the one really put in the latex file. Just have a look at  
View-source to make sure of that. In 1.6, the DUPLICATE markers are  
only for screen representation, they are of course not exported to LateX.


Not currently. 


However I wanted to highlight a possible complication if the proposal of
expanded labels in parent-child documents is introduced: I would really not
like to behave LyX in such an hardly predictable way. 


I think we all agree then :-)



IMO implementing the parent-child label disambiguation will need carefull
consideration and might be less urgent (or unnecessary) with the
DUPLICATE and BROKEN markers reduce labeling problems in 1.6.


Right. Note also that 1.6 will also avoid duplicates at label _creation_ 
or when portion of text is copiedpaste. But LyX won't touch the labels 
of an open document without intervation from the user.


Abdel.

Re: [Announce] Sponsoring a LyX project is now possible

[Abdelrazak Younes]

Steve Litt wrote:

Hi Abdel,

My finances are too tight right now to donate,


Side note: I really hope I will be proved wrong but I don't expect that 
many users will donate. Still, I would like to emphasize that even a 5 
euros or 5 dollars donation (to LyX proper or to one of the projects) 
_is_ a welcome contribution.


I would also like to say that an even nicer contribution would be to 
motivate the company or organisation you are working for to make a 
donation. This is where the real money will come, if any, I think.



but your email reminds me how 
much I owe the LyX developers. I've used LyX to make at least 4 books I sell 
on a regular basis and contribute significantly to my income. I owe the LyX 
community big time.


If anyone wants my VimOutliner to LyX converter, I'll make it available as 
GPL. I'll also try to, at a later date, try to make a simpler and more 
portable version that uses awk instead of Ruby/Node.rb. When I switch to LyX 
1.6, I'll update it to write LyX 1.6.


In order to be distributed with LyX, python is the only real alternative 
for now. But Ruby is not so far from python AFAIK so you'd be better 
with it anyway than with awk.




Perhaps I'll try to make some other scripts for LyX. It's not much, but 
perhaps it's something I can do to just barely begin to repay the LyX 
Developers, at least until I have money to donate.


Thanks,
Abdel.

Re: Discussion: Labels and parent-child documents

[Abdelrazak Younes]

Nicolás wrote:
You are right in that we may have cross-references between children 
documents. I still think that my proposal of automatically renaming 
labels is a good idea.


Side note FYI: In 1.6 duplicate Labels are not changed automatically but 
they are clearly marked as DUPLICATE in the work area and in the new 
Navigator (former outline pane). So it's easy to spot where the problems 
lie in the document. Also worth of note is that 1.6 won't allow the 
creation of duplicate labels, it will automatically rename the duplicate 
label. Another interesting feature is that broken are marked as BROKEN.


Abdel.

Re: Discussion: Labels and parent-child documents

[Abdelrazak Younes]

G. Milde wrote:

On  3.06.08, Nicolás wrote:

Well, one problem I can see is that this could make cut and paste  
between documents difficult. And it involves a lot of keeping track of  
what's a child of what.



Not really. Note that labels and cross-references are only updated when
we export to latex.


Does this mean that the labels in child file generated by FileExportLatex
will differ depending on whether the export is done from the parent or
the child? (Or, maybe,  depending on whether the child was opened
directly or via the parent file? Or whether the parent file is opened
in lyx at the time of the export?)


No, AFAIK labels are not changed at latex export. The one you see within 
LyX are the one really put in the latex file. Just have a look at 
View-source to make sure of that. In 1.6, the DUPLICATE markers are 
only for screen representation, they are of course not exported to LateX.


Abdel.

[Announce] Sponsoring a LyX project is now possible

[Abdelrazak Younes]

Dear LyX users,

As for all non paid work, the development of new feature exclusively 
depends on the good will of the developers. But we acknowledge that 
there are some features that are badly needed for some users; a new page 
has been set up to answer this need: http://www.lyx.org/Donate


The donation web page will now list some projects with a potential 
developer associated with it (only one for now). Each interested 
developer would use his own PayPal account. He decides himself the 
minimum amount of money to get the project started. Ideas for project 
can be collected from bugzilla (search for enhancement request in 
http://bugzilla.lyx.org) or from the wiki 
(http://wiki.lyx.org/LyX/FeaturePoll).


Therefore we ask you, the LyX user, to participate in the development of 
one or more projects by sponsoring them or by motivating the company or 
organisation you are working for to entirely or partially sponsor the 
development of one or more projects. Here are the rules that will be 
followed for this kind of development:



* All new development happens in trunk (what will become the next stable 
version), there will be no exception for sponsored development. 
Back-porting to an older version is of course possible but should happen 
after.


* There are no special commit rules for sponsored development, the 
source code will be evaluated just as any new code, and being sponsored 
does not mean it has some 'right' to get in regardless of its merit. 
This item needs to be clear to the involved developer and also to the 
people or organisation paying for the development.


* Being sponsored does not mean that the project is reserved to the one 
who is sponsored. Anybody is still free to do what he/she wants.



On behalf of the LyX developers,
Abdel.

Re: Problems with LyX 1.5.5 after MAC OS X update

[Abdelrazak Younes]

Nicola Focci wrote:

2008/6/3 James Sutherland [EMAIL PROTECTED]:


No problem here.  I just installed LyX 1.5.5 with OSX 10.5.3.  I am
running an intel MacBook Pro and a MacBook.



Same problem as George! And the same grey screenshot.
I'm running a six-months-old IMac, 20 monitor and 2.4 Ghz Intel processor,
with OSX 10.5.3
LyX 1.5.4 worked perfectly under the same configuration!


Let me guess: 1.5.4 came with Qt4.3 and 1.5.5 come with Qt4.4...
If so, I think it would make sense to downgrade Qt Bennett.

Abdel.

Re: Discussion: Labels and parent-child documents

[Abdelrazak Younes]

G. Milde wrote:

On  3.06.08, Abdelrazak Younes wrote:

G. Milde wrote:

On  3.06.08, Nicolás wrote:


Well, one problem I can see is that this could make cut and paste   
between documents difficult. And it involves a lot of keeping track 
of  what's a child of what.



Not really. Note that labels and cross-references are only updated when
we export to latex.



Does this mean that the labels in child file generated by FileExportLatex
will differ depending on whether the export is done from the parent or
the child? (Or, maybe,  depending on whether the child was opened
directly or via the parent file? Or whether the parent file is opened
in lyx at the time of the export?)


No, AFAIK labels are not changed at latex export. The one you see within  
LyX are the one really put in the latex file. Just have a look at  
View-source to make sure of that. In 1.6, the DUPLICATE markers are  
only for screen representation, they are of course not exported to LateX.


Not currently. 


However I wanted to highlight a possible complication if the proposal of
expanded labels in parent-child documents is introduced: I would really not
like to behave LyX in such an hardly predictable way. 


I think we all agree then :-)



IMO implementing the parent-child label disambiguation will need carefull
consideration and might be less urgent (or unnecessary) with the
DUPLICATE and BROKEN markers reduce labeling problems in 1.6.


Right. Note also that 1.6 will also avoid duplicates at label _creation_ 
or when portion of text is copiedpaste. But LyX won't touch the labels 
of an open document without intervation from the user.


Abdel.

Re: [Announce] Sponsoring a LyX project is now possible

[Abdelrazak Younes]

Steve Litt wrote:

Hi Abdel,

My finances are too tight right now to donate,


Side note: I really hope I will be proved wrong but I don't expect that 
many users will donate. Still, I would like to emphasize that even a 5 
euros or 5 dollars donation (to LyX proper or to one of the projects) 
_is_ a welcome contribution.


I would also like to say that an even nicer contribution would be to 
motivate the company or organisation you are working for to make a 
donation. This is where the real money will come, if any, I think.



but your email reminds me how 
much I owe the LyX developers. I've used LyX to make at least 4 books I sell 
on a regular basis and contribute significantly to my income. I owe the LyX 
community big time.


If anyone wants my VimOutliner to LyX converter, I'll make it available as 
GPL. I'll also try to, at a later date, try to make a simpler and more 
portable version that uses awk instead of Ruby/Node.rb. When I switch to LyX 
1.6, I'll update it to write LyX 1.6.


In order to be distributed with LyX, python is the only real alternative 
for now. But Ruby is not so far from python AFAIK so you'd be better 
with it anyway than with awk.




Perhaps I'll try to make some other scripts for LyX. It's not much, but 
perhaps it's something I can do to just barely begin to repay the LyX 
Developers, at least until I have money to donate.


Thanks,
Abdel.

Re: Discussion: Labels and parent-child documents

[Abdelrazak Younes]

Nicolás wrote:
You are right in that we may have cross-references between children 
documents. I still think that my proposal of automatically renaming 
labels is a good idea.


Side note FYI: In 1.6 duplicate Labels are not changed automatically but 
they are clearly marked as DUPLICATE in the work area and in the new 
Navigator (former outline pane). So it's easy to spot where the problems 
lie in the document. Also worth of note is that 1.6 won't allow the 
creation of duplicate labels, it will automatically rename the duplicate 
label. Another interesting feature is that broken are marked as BROKEN.


Abdel.

Re: Discussion: Labels and parent-child documents

[Abdelrazak Younes]

G. Milde wrote:

On  3.06.08, Nicolás wrote:

Well, one problem I can see is that this could make cut and paste  
between documents difficult. And it involves a lot of keeping track of  
what's a child of what.



Not really. Note that labels and cross-references are only updated when
we export to latex.


Does this mean that the labels in child file generated by File>Export>Latex
will differ depending on whether the export is done from the parent or
the child? (Or, maybe,  depending on whether the child was opened
directly or via the parent file? Or whether the parent file is opened
in lyx at the time of the export?)


No, AFAIK labels are not changed at latex export. The one you see within 
LyX are the one really put in the latex file. Just have a look at 
View->source to make sure of that. In 1.6, the DUPLICATE markers are 
only for screen representation, they are of course not exported to LateX.


Abdel.

[Announce] Sponsoring a LyX project is now possible

[Abdelrazak Younes]

Dear LyX users,

As for all non paid work, the development of new feature exclusively 
depends on the good will of the developers. But we acknowledge that 
there are some features that are badly needed for some users; a new page 
has been set up to answer this need: http://www.lyx.org/Donate


The donation web page will now list some projects with a potential 
developer associated with it (only one for now). Each interested 
developer would use his own PayPal account. He decides himself the 
minimum amount of money to get the project started. Ideas for project 
can be collected from bugzilla (search for enhancement request in 
http://bugzilla.lyx.org) or from the wiki 
(http://wiki.lyx.org/LyX/FeaturePoll).


Therefore we ask you, the LyX user, to participate in the development of 
one or more projects by sponsoring them or by motivating the company or 
organisation you are working for to entirely or partially sponsor the 
development of one or more projects. Here are the rules that will be 
followed for this kind of development:



* All new development happens in trunk (what will become the next stable 
version), there will be no exception for sponsored development. 
Back-porting to an older version is of course possible but should happen 
after.


* There are no special commit rules for sponsored development, the 
source code will be evaluated just as any new code, and being sponsored 
does not mean it has some 'right' to get in regardless of its merit. 
This item needs to be clear to the involved developer and also to the 
people or organisation paying for the development.


* Being sponsored does not mean that the project is reserved to the one 
who is sponsored. Anybody is still free to do what he/she wants.



On behalf of the LyX developers,
Abdel.

Re: Problems with LyX 1.5.5 after MAC OS X update

[Abdelrazak Younes]

Nicola Focci wrote:

2008/6/3 James Sutherland <[EMAIL PROTECTED]>:


No problem here.  I just installed LyX 1.5.5 with OSX 10.5.3.  I am
running an intel MacBook Pro and a MacBook.



Same problem as George! And the same "grey" screenshot.
I'm running a six-months-old IMac, 20" monitor and 2.4 Ghz Intel processor,
with OSX 10.5.3
LyX 1.5.4 worked perfectly under the same configuration!


Let me guess: 1.5.4 came with Qt4.3 and 1.5.5 come with Qt4.4...
If so, I think it would make sense to downgrade Qt Bennett.

Abdel.

Re: Discussion: Labels and parent-child documents

[Abdelrazak Younes]

G. Milde wrote:

On  3.06.08, Abdelrazak Younes wrote:

G. Milde wrote:

On  3.06.08, Nicolás wrote:


Well, one problem I can see is that this could make cut and paste   
between documents difficult. And it involves a lot of keeping track 
of  what's a child of what.



Not really. Note that labels and cross-references are only updated when
we export to latex.



Does this mean that the labels in child file generated by File>Export>Latex
will differ depending on whether the export is done from the parent or
the child? (Or, maybe,  depending on whether the child was opened
directly or via the parent file? Or whether the parent file is opened
in lyx at the time of the export?)


No, AFAIK labels are not changed at latex export. The one you see within  
LyX are the one really put in the latex file. Just have a look at  
View->source to make sure of that. In 1.6, the DUPLICATE markers are  
only for screen representation, they are of course not exported to LateX.


Not currently. 


However I wanted to highlight a possible complication if the proposal of
expanded labels in parent-child documents is introduced: I would really not
like to behave LyX in such an hardly predictable way. 


I think we all agree then :-)



IMO implementing the parent-child label disambiguation will need carefull
consideration and might be less urgent (or unnecessary) with the
DUPLICATE and BROKEN markers reduce labeling problems in 1.6.


Right. Note also that 1.6 will also avoid duplicates at label _creation_ 
or when portion of text is copied But LyX won't touch the labels 
of an open document without intervation from the user.


Abdel.

Re: [Announce] Sponsoring a LyX project is now possible

[Abdelrazak Younes]

Steve Litt wrote:

Hi Abdel,

My finances are too tight right now to donate,


Side note: I really hope I will be proved wrong but I don't expect that 
many users will donate. Still, I would like to emphasize that even a 5 
euros or 5 dollars donation (to LyX proper or to one of the projects) 
_is_ a welcome contribution.


I would also like to say that an even nicer contribution would be to 
motivate the company or organisation you are working for to make a 
donation. This is where the real money will come, if any, I think.



but your email reminds me how 
much I owe the LyX developers. I've used LyX to make at least 4 books I sell 
on a regular basis and contribute significantly to my income. I owe the LyX 
community big time.


If anyone wants my VimOutliner to LyX converter, I'll make it available as 
GPL. I'll also try to, at a later date, try to make a simpler and more 
portable version that uses awk instead of Ruby/Node.rb. When I switch to LyX 
1.6, I'll update it to write LyX 1.6.


In order to be distributed with LyX, python is the only real alternative 
for now. But Ruby is not so far from python AFAIK so you'd be better 
with it anyway than with awk.




Perhaps I'll try to make some other scripts for LyX. It's not much, but 
perhaps it's something I can do to just barely begin to repay the LyX 
Developers, at least until I have money to donate.


Thanks,
Abdel.

Re: 1.6 release

[Abdelrazak Younes]

Rune Schjellerup Philosof wrote:

Abdelrazak Younes skrev:

Rune Schjellerup Philosof wrote:

Hi

How is it going along with version 1.6?
According to the release schedule alpha 2 has been released, but 
beta 1 and 2 should also have been released, but have not.

Also even though alpha 2 should be out there, I can not find it.

http://wiki.lyx.org/Devel/ReleaseSchedule


I updated this. FWIW beta1 is scheduled for this thursday. At least 
that is the last words of our release manager. Famous last word :-)


Hmm. What happened?
No status on beta 1 on the release schedule, and I can't find a 
release anywhere.

Shxxxt happens sometimes :-)
Hopefully a beta2 will appear soon.

Abdel.

Re: 1.6 release

[Abdelrazak Younes]

Uwe Stöhr wrote:

Rune Schjellerup Philosof schrieb:


http://wiki.lyx.org/Devel/ReleaseSchedule


I updated this. FWIW beta1 is scheduled for this thursday. At least 
that is the last words of our release manager. Famous last word :-)


Hmm. What happened?
No status on beta 1 on the release schedule,


I updated it.


and I can't find a release anywhere.


I announced the Win version for beta 1 here:
http://www.mail-archive.com/lyx-users@lists.lyx.org/msg65030.html

But be careful as this version includes a dataloss bug, so beta 2 will 
follow soon.

That's why I marked it as Cancelled

Abdel.

Re: Problems with LyX 1.5.5 after MAC OS X update

[Abdelrazak Younes]

Bennett Helm wrote:
On Mon, Jun 2, 2008 at 2:40 PM, Georg Baum 
[EMAIL PROTECTED] 
mailto:[EMAIL PROTECTED] 
wrote:


Bennett Helm wrote:

  I don't know of anything that would affect it, and I haven't seen
anything
  like that screenshot. I wonder if the file you downloaded was
corrupted.

Which screenshot? Does it look like the problem in
http://bugzilla.lyx.org/show_bug.cgi?id=4907 ?


It doesn't look like it. (I've attached the screenshot here.)


This looks like lib/ui/stdtoolbar.ui file is corrupted because all 
toolbars seems to be loaded with no icons.
George, could you please delete your resource directory (the one 
containing the above file) and reinstall again?


Abdel.

Re: 1.6 release

[Abdelrazak Younes]

Rune Schjellerup Philosof wrote:

Abdelrazak Younes skrev:

Rune Schjellerup Philosof wrote:

Hi

How is it going along with version 1.6?
According to the release schedule alpha 2 has been released, but 
beta 1 and 2 should also have been released, but have not.

Also even though alpha 2 should be out there, I can not find it.

http://wiki.lyx.org/Devel/ReleaseSchedule


I updated this. FWIW beta1 is scheduled for this thursday. At least 
that is the last words of our release manager. Famous last word :-)


Hmm. What happened?
No status on beta 1 on the release schedule, and I can't find a 
release anywhere.

Shxxxt happens sometimes :-)
Hopefully a beta2 will appear soon.

Abdel.

Re: 1.6 release

[Abdelrazak Younes]

Uwe Stöhr wrote:

Rune Schjellerup Philosof schrieb:


http://wiki.lyx.org/Devel/ReleaseSchedule


I updated this. FWIW beta1 is scheduled for this thursday. At least 
that is the last words of our release manager. Famous last word :-)


Hmm. What happened?
No status on beta 1 on the release schedule,


I updated it.


and I can't find a release anywhere.


I announced the Win version for beta 1 here:
http://www.mail-archive.com/lyx-users@lists.lyx.org/msg65030.html

But be careful as this version includes a dataloss bug, so beta 2 will 
follow soon.

That's why I marked it as Cancelled

Abdel.

Re: Problems with LyX 1.5.5 after MAC OS X update

[Abdelrazak Younes]

Bennett Helm wrote:
On Mon, Jun 2, 2008 at 2:40 PM, Georg Baum 
[EMAIL PROTECTED] 
mailto:[EMAIL PROTECTED] 
wrote:


Bennett Helm wrote:

  I don't know of anything that would affect it, and I haven't seen
anything
  like that screenshot. I wonder if the file you downloaded was
corrupted.

Which screenshot? Does it look like the problem in
http://bugzilla.lyx.org/show_bug.cgi?id=4907 ?


It doesn't look like it. (I've attached the screenshot here.)


This looks like lib/ui/stdtoolbar.ui file is corrupted because all 
toolbars seems to be loaded with no icons.
George, could you please delete your resource directory (the one 
containing the above file) and reinstall again?


Abdel.

Re: 1.6 release

[Abdelrazak Younes]

Rune Schjellerup Philosof wrote:

Abdelrazak Younes skrev:

Rune Schjellerup Philosof wrote:

Hi

How is it going along with version 1.6?
According to the release schedule alpha 2 has been released, but 
beta 1 and 2 should also have been released, but have not.

Also even though alpha 2 should be out there, I can not find it.

http://wiki.lyx.org/Devel/ReleaseSchedule


I updated this. FWIW beta1 is scheduled for this thursday. At least 
that is the last words of our release manager. Famous last word :-)


Hmm. What happened?
No status on beta 1 on the release schedule, and I can't find a 
release anywhere.

Shxxxt happens sometimes :-)
Hopefully a beta2 will appear soon.

Abdel.

Re: 1.6 release

[Abdelrazak Younes]

Uwe Stöhr wrote:

Rune Schjellerup Philosof schrieb:


http://wiki.lyx.org/Devel/ReleaseSchedule


I updated this. FWIW beta1 is scheduled for this thursday. At least 
that is the last words of our release manager. Famous last word :-)


Hmm. What happened?
No status on beta 1 on the release schedule,


I updated it.


and I can't find a release anywhere.


I announced the Win version for beta 1 here:
http://www.mail-archive.com/lyx-users@lists.lyx.org/msg65030.html

But be careful as this version includes a dataloss bug, so beta 2 will 
follow soon.

That's why I marked it as "Cancelled"

Abdel.

Re: Problems with LyX 1.5.5 after MAC OS X update

[Abdelrazak Younes]

Bennett Helm wrote:
On Mon, Jun 2, 2008 at 2:40 PM, Georg Baum 
<[EMAIL PROTECTED] 
> 
wrote:


Bennett Helm wrote:

 > I don't know of anything that would affect it, and I haven't seen
anything
 > like that screenshot. I wonder if the file you downloaded was
corrupted.

Which screenshot? Does it look like the problem in
http://bugzilla.lyx.org/show_bug.cgi?id=4907 ?


It doesn't look like it. (I've attached the screenshot here.)


This looks like lib/ui/stdtoolbar.ui file is corrupted because all 
toolbars seems to be loaded with no icons.
George, could you please delete your resource directory (the one 
containing the above file) and reinstall again?


Abdel.

Re: Lyx crashes everytime I try to open my document

[Abdelrazak Younes]

TheDarkMaster wrote:

Please help me, I'm loosing an important university thesis. The last time I
opened my Lyx document in Mac OSX (using the latest 1.5.5 Lyx versin), I
added a lot of maths using the Lyx functions and when I tried to open the
preview in pdf, it didn't work. So I restarted OSX thinking it was a
temporary error but now, when I try to open my document, Lyx crashes and OSX
tells me it has a bug report, here it is:


It seems that this is related to the session file. I don't know where 
the session file is located under MacOSX but if you can, try to remove 
the file before launching LyX. This file is in the same directory as 
lyxrc.default. On Vista it is in C:\Users\abdel\AppData\Roaming\lyx-15\


Then, try to open your thesis. If it still crashes and if you can send 
me privately a copy, I can try to investigate. Second solution is to try 
the latest 1.6alpha. Even if it is still alpha, 1.6 is in general 
stabler when reading files.


Abdel.

Re: Lyx crashes everytime I try to open my document

[Abdelrazak Younes]

TheDarkMaster wrote:

Hallo Abdel, I don't know which file to delete, you don't specify it in your
answer,


This is the file session sorry.


but at least I tried to look in my mac for the lyxrc.default file
and I don't have it... Are you sure it can be a problem related to this,
since I installed Lyx 1.5.5 over the old one and since it can still open
other files? Only opening this file results in a crash... 


OK, I misunderstood your report then.


again, anyone,
please help me. I'll send you a copy anyway, thank you soo much for your
attention :)


I cannot reproduce the crash, the file opens correctly with latest 1.5 
here. Maybe it's related to one of the graphics linked in the document. 
Could you try to open your file from a directory where LyX will not find 
the graphics?


Abdel.

Re: Lyx crashes everytime I try to open my document

[Abdelrazak Younes]

The DarkMaster wrote:



I cannot reproduce the crash, the file opens correctly with latest
1.5 here. Maybe it's related to one of the graphics linked in the
document. Could you try to open your file from a directory where
LyX will not find the graphics?


Uhm... you 90% saved me already. Now the file opens, it was sufficient 
to copy it in another dir.

OK.


Why does this happen?
Maybe some of your graphics is corrupted, that should not happen but it 
happens.



And what can I do to use my graphic?
Try to copy the graphics one by one to the new location and reopen the 
file each time. Once you've located the guilty graphic, try to open it 
with some other software to see if it can be corrected.



Before I added math to the thesis, everything was fine and all of the 
pictures worked... cannot get what happened here. Plus, since I added 
all of this math, I cannot make a preview or export to pdf anyway... 
no damned error output is displayed :(

Could you try to see a pdf preview yourself?

I can't. LyX gives me this error message at the console.

File 
'C:/Users/abdel/AppData/Local/Temp/lyx_tmpdir120612a19492/lyx_tmpbuf0/Relaz
ione_Urbanistica_seconda.tex' was not closed properly. I get the same if 
I try to export to LateX (pdflatex) and manually compile it. This looks 
like a bug in LyX indeed.



And why shouldn't it work, or do you have a aclue on how can I fix this?

No idea yet, Jürgen, do you have one?

Abdel.