2 Bugs
Hi, just found two bugs: 1. Bookmarks in ERTs crash Lyx 2. Changes in Document -- Settings -- Latex Preamble are lost when you go back to the main window without OK or Apply Could one of the developers file a bug? Regards, Toby
Re: article(APA) does not work in 1.5.x as it did in 1.4.x WAS exporting to rtf?
B. Bogart wrote: So I reiterate that I was able to use article(APA) in 1.4.x, but that it is not working in 1.5.x. What is not working excatly? Jürgen
RE: footnote in caption
Alexander Sklar wrote: Thanks for your replies, I visited the page Jürgen suggested, and perhaps this is a silly question but how do I add an optional parameter to a caption (to make it look different in the table of figures than in the actual caption text)? This would be somewhat of a workaround to have a footnote for the caption Insert-Short Title (while cursor is in the caption). Jürgen
Re: Exporting to Rich Text Format with latex2rtf, issues and a fix
Andre Poenitz wrote: Maybe you could add that to the wiki... Yes, please. Jürgen
Re: 2 Bugs
Tobias Krause wrote: 1. Bookmarks in ERTs crash Lyx Do you have a detailed recipe? Jürgen
Re: Bad PDF-Quality
On 23 Oct 2007, Bennett Helm wrote: On Oct 23, 2007, at 1:27 PM, August Linuxland wrote: Hi, I just tried to use LyX for my little paper I have to write, but there seems to be some issue with my Preferences. Here are two versions of the same Document, one processed through LyX, the other processed through TeXShop, which both use pdflatex: www.pogona.net/eight_lyx.pdf www.pogona.net/eight_texshop.pdf As you can see, there's a big difference in Quality. Maybe someone has a tip on how to improve the output quality of LyX. Thx, Pogon §7.3 of the FAQ (Help FAQ) tells you to look at §5.3.6 -- actually §5.3.6.2 -- of the Extended Features manual (Help Extended Featuers). Bennett On a slightly different note, if you are trying to make pdf files to upload to Lulu there are issues with embedded fonts. I find that the best thing is to send the file as postscript (.ps), which gets round this. Lulu does accept postscript although it doesn't advertise the fact. -- Anthony Campbell - [EMAIL PROTECTED] Microsoft-free zone - Using Linux Gnu-Debian http://www.acampbell.org.uk (blog, book reviews, on-line books and sceptical articles)
Re: Issues with v1.5.2 on OS X
Adam Treverrow wrote:
It's faster if you turn preview on!
Yes, that certainly helps -thanks. Collapsing floats and notes also
helps, but typing within an existing paragraph of text can still result
in excessive lag, which is a problem when editing text. I didn't notice
any improvement with Richard's suggestion to alter the window size.
1.5.3 will hopefully see improvements WRT this problem (especially when
typing within Inset). If you are able to compile from source, try this
patch after retrieving the BRANCH_1_5_X svn branch (it might also apply
cleanly to 1.5.2 source).
Abdel.
Index: BufferView.cpp
===
--- BufferView.cpp (revision 21185)
+++ BufferView.cpp (working copy)
@@ -1482,13 +1482,19 @@
// If the paragraph metrics has changed, we can not
// use the singlepar optimisation.
- if (singlepar
+ if (singlepar) {
+ pit_type const bottom_pit = cursor_.bottom().pit();
+ int old_height = tm.parMetrics(bottom_pit).height();
// In Single Paragraph mode, rebreak only
// the (main text, not inset!) paragraph containing the cursor.
// (if this paragraph contains insets etc., rebreaking will
// recursively descend)
-tm.redoParagraph(cursor_.bottom().pit()))
- singlepar = false;
+ tm.redoParagraph(bottom_pit);
+ // Paragraph height has changed so we cannot proceed to
+ // the singlePar optimisation.
+ if (tm.parMetrics(bottom_pit).height() != old_height)
+ singlepar = false;
+ }
pit_type const pit = anchor_ref_;
int pit1 = pit;
Index: insets/InsetCaption.h
===
--- insets/InsetCaption.h (revision 21185)
+++ insets/InsetCaption.h (working copy)
@@ -59,8 +59,6 @@
///
virtual bool getStatus(Cursor cur, FuncRequest const cmd,
FuncStatus ) const;
///
- virtual bool wide() const { return false; }
- ///
int latex(Buffer const buf, odocstream os,
OutputParams const ) const;
///
Index: insets/InsetCollapsable.cpp
===
--- insets/InsetCollapsable.cpp (revision 21185)
+++ insets/InsetCollapsable.cpp (working copy)
@@ -158,13 +158,10 @@
dim = dimensionCollapsed();
if (status() == Open) {
InsetText::metrics(mi, textdim_);
- // This expression should not contain mi.base.texwidth
openinlined_ = !hasFixedWidth()
-textdim_.wid 0.5 * mi.base.bv-workWidth();
+(textdim_.wid + dim.wid) =
mi.base.textwidth;
if (openinlined_) {
- // Correct for button width, and re-fit
- mi.base.textwidth -= dim.wid;
- InsetText::metrics(mi, textdim_);
+ // Correct for button width
dim.wid += textdim_.wid;
dim.des = max(dim.des - textdim_.asc + dim.asc,
textdim_.des);
dim.asc = textdim_.asc;
Index: insets/InsetFloat.h
===
--- insets/InsetFloat.h (revision 21185)
+++ insets/InsetFloat.h (working copy)
@@ -61,8 +61,6 @@
///
Inset::Code lyxCode() const { return Inset::FLOAT_CODE; }
///
- virtual bool wide() const { return false; }
- ///
int latex(Buffer const , odocstream ,
OutputParams const ) const;
///
Index: insets/InsetOptArg.h
===
--- insets/InsetOptArg.h(revision 21185)
+++ insets/InsetOptArg.h(working copy)
@@ -31,8 +31,6 @@
Inset::Code lyxCode() const { return Inset::OPTARG_CODE; }
/// return an message upon editing
virtual docstring const editMessage() const;
- ///
- virtual bool wide() const { return false; }
/// Standard LaTeX output -- short-circuited
int latex(Buffer const , odocstream ,
Index: insets/InsetText.cpp
===
--- insets/InsetText.cpp(revision 21185)
+++ insets/InsetText.cpp(working copy)
@@ -78,7 +78,7 @@
InsetText::InsetText(BufferParams const bp)
- : drawFrame_(false), frame_color_(Color::insetframe)
+ : drawFrame_(false), frame_color_(Color::insetframe),
fixed_width_(false)
{
paragraphs().push_back(Paragraph());
paragraphs().back().layout(bp.getTextClass().defaultLayout());
@@ -90,7 +90,7 @@
Re: 2 Bugs
Tobias Krause [EMAIL PROTECTED] writes: 1. Bookmarks in ERTs crash Lyx When does it crash? When you save? 2. Changes in Document -- Settings -- Latex Preamble are lost when you go back to the main window without OK or Apply Does not look like a bug to me, but I probably did not understand you well. JMarc
Re: 2 Bugs
@ Jean-Marc: no, not when I save, but when I trie ot use the bookmark @ Juergen: detailded recipe is here: lyx: Disabling LyX socket. Warning: Output is empty An empty output file was generated. This is BibTeX, Version 0.99c (MiKTeX 2.6) The top-level auxiliary file: LDA.aux The style file: 1XXX_natdin.bst month is an unknown function---line 294 of file 1XXX_natdin.bst month is an unknown function---line 300 of file 1XXX_natdin.bst type is an unknown function---line 311 of file 1XXX_natdin.bst type is an unknown function---line 312 of file 1XXX_natdin.bst type is an unknown function---line 313 of file 1XXX_natdin.bst type is an unknown function---line 315 of file 1XXX_natdin.bst lastchecked is an unknown function---line 341 of file 1XXX_natdin.bst doi is an unknown function---line 342 of file 1XXX_natdin.bst urn is an unknown function---line 342 of file 1XXX_natdin.bst doi is an unknown function---line 347 of file 1XXX_natdin.bst urn is an unknown function---line 347 of file 1XXX_natdin.bst lastchecked is an unknown function---line 352 of file 1XXX_natdin.bst type is an unknown function---line 360 of file 1XXX_natdin.bst type is an unknown function---line 361 of file 1XXX_natdin.bst type is an unknown function---line 362 of file 1XXX_natdin.bst doi is an unknown function---line 373 of file 1XXX_natdin.bst new.block is an unknown function---line 375 of file 1XXX_natdin.bst doi is an unknown function---line 375 of file 1XXX_natdin.bst urn is an unknown function---line 382 of file 1XXX_natdin.bst doi is an unknown function---line 383 of file 1XXX_natdin.bst type is an unknown function---line 386 of file 1XXX_natdin.bst type is an unknown function---line 387 of file 1XXX_natdin.bst type is an unknown function---line 388 of file 1XXX_natdin.bst urn is an unknown function---line 406 of file 1XXX_natdin.bst type is an unknown function---line 414 of file 1XXX_natdin.bst type is an unknown function---line 416 of file 1XXX_natdin.bst type is an unknown function---line 417 of file 1XXX_natdin.bst organization is an unknown function---line 642 of file 1XXX_natdin.bst organization is an unknown function---line 649 of file 1XXX_natdin.bst organization is an unknown function---line 651 of file 1XXX_natdin.bst organization is an unknown function---line 658 of file 1XXX_natdin.bst organization is an unknown function---line 661 of file 1XXX_natdin.bst organization is an unknown function---line 674 of file 1XXX_natdin.bst organization is an unknown function---line 677 of file 1XXX_natdin.bst organization is an unknown function---line 678 of file 1XXX_natdin.bst institution is an unknown function---line 685 of file 1XXX_natdin.bst institution is an unknown function---line 687 of file 1XXX_natdin.bst type is an unknown function---line 717 of file 1XXX_natdin.bst type is an unknown function---line 719 of file 1XXX_natdin.bst type is an unknown function---line 720 of file 1XXX_natdin.bst type is an unknown function---line 723 of file 1XXX_natdin.bst doi is an unknown function---line 768 of file 1XXX_natdin.bst urn is an unknown function---line 768 of file 1XXX_natdin.bst doi is an unknown function---line 779 of file 1XXX_natdin.bst urn is an unknown function---line 779 of file 1XXX_natdin.bst address is an unknown function---line 787 of file 1XXX_natdin.bst address is an unknown function---line 794 of file 1XXX_natdin.bst address is an unknown function---line 798 of file 1XXX_natdin.bst address is an unknown function---line 807 of file 1XXX_natdin.bst address is an unknown function---line 808 of file 1XXX_natdin.bst urn is an unknown function---line 817 of file 1XXX_natdin.bst doi is an unknown function---line 817 of file 1XXX_natdin.bst howpublished is an unknown function---line 818 of file 1XXX_natdin.bst address is an unknown function---line 819 of file 1XXX_natdin.bst type is an unknown function---line 820 of file 1XXX_natdin.bst type is an unknown function---line 822 of file 1XXX_natdin.bst address is an unknown function---line 832 of file 1XXX_natdin.bst address is an unknown function---line 835 of file 1XXX_natdin.bst howpublished is an unknown function---line 836 of file 1XXX_natdin.bst address is an unknown function---line 837 of file 1XXX_natdin.bst howpublished is an unknown function---line 837 of file 1XXX_natdin.bst howpublished is an unknown function---line 842 of file 1XXX_natdin.bst howpublished is an unknown function---line 844 of file 1XXX_natdin.bst urn is an unknown function---line 943 of file 1XXX_natdin.bst doi is an unknown function---line 944 of file 1XXX_natdin.bst doi is an unknown function---line 946 of file 1XXX_natdin.bst urn is an unknown function---line 949 of file 1XXX_natdin.bst isbn is an unknown function---line 954 of file 1XXX_natdin.bst issn is an unknown function---line 955 of file 1XXX_natdin.bst issn is an unknown function---line 957 of file 1XXX_natdin.bst isbn is an unknown function---line 960 of file 1XXX_natdin.bst note is an unknown
Re: 2 Bugs
Tobias Krause wrote: @ Juergen: detailded recipe is here: With recipe, I mean: what actions do you exactly perform in order to trigger the crash? I'm unable to reproduce the crash. Most of your console output is unrelated, the related part is this: Assertion triggered in void __thiscall lyx::Text::setCurrentFont(class lyx::Cursor ) by failing check this == cur.text() in file D:\LyX\lyx-1.5.2\src\Text2.cpp:757 Which installer did you use? I think assertions should be really disabled in stable releases. Jürgen
Re: 2 Bugs
Hi! I confirm both bugs with LyX 1.5.2 on Windows (official installer) Recipes here: 1st Bug- Open Latex Preamble window. Write whatever in the preamble. Click with the mouse on themain LyX window. As a result the little window with the document settings goes to second plane. Go back to that window. MAGIC! What you wrote has disappeared. 2nd Bug- Open a new document. Create an ERT box. Execute Navigate-Bookmarks-Save bookmark 1. Try to open a new document and LyX crashes. Nicolás Juergen Spitzmueller wrote: Tobias Krause wrote: @ Juergen: detailded recipe is here: With recipe, I mean: what actions do you exactly perform in order to trigger the crash? I'm unable to reproduce the crash. Most of your console output is unrelated, the related part is this: Assertion triggered in void __thiscall lyx::Text::setCurrentFont(class lyx::Cursor ) by failing check this == cur.text() in file D:\LyX\lyx-1.5.2\src\Text2.cpp:757 Which installer did you use? I think assertions should be really disabled in stable releases. Jürgen
Re: 2 Bugs
Nicolás wrote: 2nd Bug- Open a new document. Create an ERT box. Execute Navigate-Bookmarks-Save bookmark 1. Try to open a new document and LyX crashes. I cannot reproduce on Linux. Could you provide a backtrace? Jürgen
Re: 2 Bugs
Juergen Spitzmueller wrote: Nicolás wrote: 2nd Bug- Open a new document. Create an ERT box. Execute Navigate-Bookmarks-Save bookmark 1. Try to open a new document and LyX crashes. I cannot reproduce on Linux. Could you provide a backtrace? You mean a debugging trace? If so, which debug option you want me to use? Jürgen
Re: Exporting to Rich Text Format with latex2rtf, issues and a fix
Dave Hewitt [EMAIL PROTECTED] writes: Ideally, one would simply: (1) install latex2rtf from sourceforge (win-gui download here - http://sourceforge.net/project/showfiles.php?group_id=22654) (2) add the latex2rtf folder (C:\l2r -- see below) to the Windows search path (see section 2.4 here - http://sourceforge.net/project/showfiles.php?group_id=22654) (3) open LyX, reconfigure, close, and restart and the converter for Latex (plain) - Rich Text Format would be sorted out by LyX and a Rich Text Format option would be made available under File - Export. Unfortunately, it ain't that easy. Well, as the one who makes the DOS/Win port of latex2rtf, I can explain why it is as is and why some thing work and others not. See below. First off, the above strategy works fine if all you want to do is use the latex2rtf GUI (l2rshell.exe; the icon on the desktop calls this) to convert existing .tex files to .rtf files. In fact, you only need (1) and (2) above for that, and then you just export plain latex from LyX and run the conversion manually. Getting LyX to recognize the converter (latex2rt.exe) is the hard part, but it's nice to have LyX do all the work behind the scenes. The first issue is that you should simply avoid installing the program anywhere but C:\l2r. All of the defaults for the program assume that it is installed at this path. I installed to Program Files because I had not read section 2.4 here - http://sourceforge.net/project/showfiles.php?group_id=22654 - first. It explains how to adjust the three configuration files (more on these in a minute) to make latex2rtf work from any installation path, but it never worked for me, and I tried a lot of different things. No matter what I tried, running LyX from the command prompt showed that the error was that latex2rtf could not find its config directory (the cfg directory under the latex2rtf root directory). It always assumed that the root directory was C:\l2r despite the fact that all entries in the configuration files were adjusted to reflect C:\Program Files\latex2rtf, where I installed it. What do you mean by configuration files? Adapting the pathes in the batch files (l2rprep.bat, l2r.bat) only helps if these batch files are executed. If you just call latex2rt.exe, they aren't. The configuration of the GUI shell is used only by the GUI shell. latex2rt.exe itself knows nothing of the GUI shell nor of the batch files. So, make your life easy and install to C:\l2r. I never checked this with the latex2rtf folks, but the simple solution seems to be obvious. Next, you do need to add the latex2rtf folder to the Windows search path: a. Right-click My Computer and go to Properties. b. Advanced Tab - Environment Variables - System Variables - Path, add C:\l2r; (no quotes) somewhere in the line. The next step varies depending on how you have LaTeX set up on your machine. I used the LyXWinInstaller and this presents a new wrinkle for latex2rtf. Those three configuration files (.bat files) are in the latex2rtf root and are L2R.BAT, L2RSEM.BAT, and L2RPREP.BAT. You'll need to edit them (use a good text editor; i.e., not Notepad). L2R and L2RSEM are almost identical, but notice that one of them (don't recall which, I changed it), on line 15, has the German windows settings line unremarked. The other one has the English windows settings unremarked. I changed them both to have the English settings unremarked (i.e., functional) and the German settings remarked (i.e., unfunctional). I didn't actually test whether this mattered, but it seemed prudent. The paths should all be fine if you installed to C:\l2r and you need do nothing more with these files. At this point, I tried reconfiguring LyX and it still failed to find the converter. L2RPREP comes in - this is a bit tougher. I ran this file from a command prompt to see that it set the paths correctly. As best I could tell, which always failed to find the Ghostscript, LaTeX, and ImageMagick files. That is OK. Which only looks in the current search path. If the Ghostscript, LaTeX or ImageMagick folders isn't yet in the PATH, which returns 1. Calling which is intended to avoid adding the folders to the path more than once. So, I edited it to look as below (changes starting on line 8). Again, this applies for people that use LyXWinInstaller only. rem set folder containing Ghostscript executables here: %l2rpath%\which gswin32c nul if errorlevel 1 SET PATH=C:\Program Files\LyX 1.5.2\etc\Ghostscript\bin;C:\Program Files\LyX 1.5.2\etc\Ghostscript\lib;%PATH% rem set folder containing ImageMagick executables here: %l2rpath%\which identify nul if errorlevel 1 SET PATH=C:\Program Files\LyX 1.5.2\etc\ImageMagick;%PATH% rem set folder containing LaTeX and dvips executables here: %l2rpath%\which latex nul if errorlevel 1 SET PATH=C:\Program Files\MiKTeX 2.6\miktex\bin;%PATH% The final
Re: 2 Bugs
Nicolás wrote: You mean a debugging trace? If so, which debug option you want me to use? No, a backtrace with a debugger like GDB. I don't know what's the best way to get this on windows, though. Jürgen
Re: exporting to rtf?
B. Bogart wrote: I did indeed do reconfigure and restarted LyX. LyX complains about the file with the following: The layout file requested by this document, apa.layout, is not usable. This is probably because a LaTeX class or style file required by it is not available. See the Customization documentation for more information. LyX will not be able to produce output. I confirm that I do have APA installed: $ kpsewhich apa.cls /usr/share/texmf-texlive/tex/latex/apa/apa.cls Perhaps apa.layout was included in the ubuntu 1.4.x package, but not in 1.5.1? Don't know the answer to that -- I haven't installed an ubuntu package (yet -- it's on my to-do-someday list). You should be able to find the layout files in LyX root/Resources/layouts and confirm whether apa.layout is there. If not, I can easily e-mail it to you. I'm pretty sure you have the layout file, though: you posted earlier that it was listed in LyX as unavailable. If you didn't have the layout file, it would not be listed at all. You might confirm (via kpsewhich) that apacite.sty is also installed. If I'm reading apa.layout correctly, it tells LyX that apacite.sty is also used. I'm not sure what would happen if the configuration package found apa.cls but not apacite.sty. As of version 1.5.x at least, when you reconfigure LyX, it writes a log file in your user directory (at least on Windows). If present, it will tell you whether it searched for, and whether it found, the APA class. For instance, mine has +checking for document class apa [apa,apacite.sty]... yes If there's no checking for message, it didn't see a layout file. If there's a message but it says no, it found the layout file but not the class or style file(s). /Paul
Re: 2 Bugs
Juergen Spitzmueller wrote: Nicolás wrote: You mean a debugging trace? If so, which debug option you want me to use? No, a backtrace with a debugger like GDB. I don't know what's the best way to get this on windows, though. Neither myself :-) Maybe someone else can do it? Jürgen
layout file format versions
Hi All, I am trying for the first time to setup a layout file, and have got some way forwards, however I am uncertain of the importance of the 'format' command in the layout file. The customization manual indicates that it refers to version 2 however the book.layout I'm basing my layout on uses version 4 and try as I might I can't locate any information about this version. Can some one point me in the right direction? Or better still tell me it doesn't matter much and I can stop worrying about it. Thanks Ian
Re: layout file format versions
On Thu, Oct 25, 2007 at 07:32:27PM +, ian holliday wrote: Hi All, I am trying for the first time to setup a layout file, and have got some way forwards, however I am uncertain of the importance of the 'format' command in the layout file. The customization manual indicates that it refers to version 2 however the book.layout I'm basing my layout on uses version 4 and try as I might I can't locate any information about this version. Can some one point me in the right direction? Or better still tell me it doesn't matter much and I can stop worrying about it. It does not matter _too_ much. There is not too much documentation for either ;-) Andre'
Re: Exporting to Rich Text Format with latex2rtf, issues and a fix
Wilfried, thanks a lot for your input. This was just a novice hackjob that worked, and my goal (as stated at the end) was to get a solid working solution that could be placed on the LyX wiki. I admit lots of ignorance on all of this. Nonetheless, I figured that since I started this I should try and finish it. So, I began by working on Enrico's suggested solution... but I found out it's all much easier than that. All I did was: (1) uninstall latex2rtf (to remove all my edited files), remove C:\l2r and C:\Program Files\LyX 1.5.2 from my Windows search path, then reconfigure LyX (RTF export disappeared) (2) reinstall latex2rtf to C:\l2r, put C:\l2r on the search path again, start LyX, reconfigure, and restart LyX - LyX FAILS to find the converter (3) close LyX, restart LyX, reconfigure again, close and restart LyX - WORKS FINE I did steps 1-3 three times and it works that way every time... the only thing you need to do apparently is reconfigure LyX TWICE after installing latex2rtf and adding the folder to the search path. (I closed and restarted LyX between reconfigurations, but I don't know that that matters). I still think it's simplest to just install latex2rtf to C:\l2r. There may be other complications if you install elsewhere, but I didn't test that. This strikes me as weird. Does LyX do this for other converters... how does configure behave differently between successive calls? Can anyone else try this and see if they repeat it? Anyway, apparently all of my problems with the configuration files (the .bat's) were a waste of time - the second time I reconfigured LyX it worked despite all of that. As Wilfried noted, I think (see below), those files are irrelevant to LyX's use of the converter (latex2rt.exe) and the GUI shell. Remaining question: Enrico, I think that l2rprep.bat is intended to do the same thing you proposed with the new .bat file - set rtfpath. No? Either way, it seems only relevant when the .bat files are being called... and (again, see below) I think Wilfried indicates that they are not when LyX calls latex2rt (.exe). Questions/comments inserted in Wilfried's comments below... Ideally, one would simply: (1) install latex2rtf from sourceforge (win-gui download here - http://sourceforge.net/project/showfiles.php?group_id=22654) (2) add the latex2rtf folder (C:\l2r -- see below) to the Windows search path (see section 2.4 here - http://sourceforge.net/project/showfiles.php?group_id=22654) (3) open LyX, reconfigure, close, and restart and the converter for Latex (plain) - Rich Text Format would be sorted out by LyX and a Rich Text Format option would be made available under File - Export. Unfortunately, it ain't that easy. Well, as the one who makes the DOS/Win port of latex2rtf, I can explain why it is as is and why some thing work and others not. See below. First off, the above strategy works fine if all you want to do is use the latex2rtf GUI (l2rshell.exe; the icon on the desktop calls this) to convert existing .tex files to .rtf files. In fact, you only need (1) and (2) above for that, and then you just export plain latex from LyX and run the conversion manually. Getting LyX to recognize the converter (latex2rt.exe) is the hard part, but it's nice to have LyX do all the work behind the scenes. The first issue is that you should simply avoid installing the program anywhere but C:\l2r. All of the defaults for the program assume that it is installed at this path. I installed to Program Files because I had not read section 2.4 here - http://sourceforge.net/project/showfiles.php?group_id=22654 - first. It explains how to adjust the three configuration files (more on these in a minute) to make latex2rtf work from any installation path, but it never worked for me, and I tried a lot of different things. No matter what I tried, running LyX from the command prompt showed that the error was that latex2rtf could not find its config directory (the cfg directory under the latex2rtf root directory). It always assumed that the root directory was C:\l2r despite the fact that all entries in the configuration files were adjusted to reflect C:\Program Files\latex2rtf, where I installed it. What do you mean by configuration files? Adapting the pathes in the batch files (l2rprep.bat, l2r.bat) only helps if these batch files are executed. If you just call latex2rt.exe, they aren't. The configuration of the GUI shell is used only by the GUI shell. latex2rt.exe itself knows nothing of the GUI shell nor of the batch files. I was referring to the .bat files, without knowing what they really did. My fault. So does this means that LyX doesn't need to know about the .bat files? It looks like all that LyX is doing is calling the latex2rt (.exe file) to get the conversion. Right? So, make your life easy and install to C:\l2r. I never checked this with the latex2rtf folks, but the simple solution seems to be
Toolbar font and font size
I'm just back to using Lyx after a long break; the font used in the toolbar has become very small. How can Lyx be configured to use a larger font? Thanks - jon
Re: 2 Bugs
On Oct 25, 2007, at 1:09 PM, Nicolás wrote: Hi! I confirm both bugs with LyX 1.5.2 on Windows (official installer) Recipes here: 1st Bug- Open Latex Preamble window. Write whatever in the preamble. Click with the mouse on themain LyX window. As a result the little window with the document settings goes to second plane. Go back to that window. MAGIC! What you wrote has disappeared. I can confirm this on OS X 2nd Bug- Open a new document. Create an ERT box. Execute Navigate- Bookmarks-Save bookmark 1. Try to open a new document and LyX crashes. No problem on OS X Nicolás Juergen Spitzmueller wrote: Tobias Krause wrote: @ Juergen: detailded recipe is here: With recipe, I mean: what actions do you exactly perform in order to trigger the crash? I'm unable to reproduce the crash. Most of your console output is unrelated, the related part is this: Assertion triggered in void __thiscall lyx::Text::setCurrentFont (class lyx::Cursor ) by failing check this == cur.text() in file D:\LyX\lyx-1.5.2\src\Text2.cpp:757 Which installer did you use? I think assertions should be really disabled in stable releases. Jürgen
Re: layout file format versions
Andre Poenitz [EMAIL PROTECTED] writes: It does not matter _too_ much. There is not too much documentation for either Andre' Thanks Andre' - I'll just assume the format won't be significantly different then.
Re: Exporting to Rich Text Format with latex2rtf, issues and a fix
Dave Hewitt writes: All I did was: (1) uninstall latex2rtf (to remove all my edited files), remove C:\l2r and C:\Program Files\LyX 1.5.2 from my Windows search path, then reconfigure LyX (RTF export disappeared) (2) reinstall latex2rtf to C:\l2r, put C:\l2r on the search path again, start LyX, reconfigure, and restart LyX - LyX FAILS to find the converter If you mean that you added C:\l2r to PATH prefix in LyX preferences and then reconfigured, then this is explained by the fact that changes to PATH prefix are only taken after you save preferences and close and restart LyX. (3) close LyX, restart LyX, reconfigure again, close and restart LyX - WORKS FINE Yes, because now the previously set PATH prefix is taken into account. I did steps 1-3 three times and it works that way every time... the only thing you need to do apparently is reconfigure LyX TWICE after installing latex2rtf and adding the folder to the search path. No, you need to close and restart LyX after adding the folder to PATH prefix. Otherwise, the PATH prefix as set at LyX start is still used, no matter that you changed it. (I closed and restarted LyX between reconfigurations, but I don't know that that matters). I still think it's simplest to just install latex2rtf to C:\l2r. There may be other complications if you install elsewhere, but I didn't test that. If you install to C:\l2r, you only need to add C:\l2r to PATH prefix. If you install latex2rtf somewhere else, you have to specify where its config directory is. There are no other complications. Enrico, I think that l2rprep.bat is intended to do the same thing you proposed with the new .bat file - set rtfpath. No? Either way, it seems only relevant when the .bat files are being called... and (again, see below) I think Wilfried indicates that they are not when LyX calls latex2rt (.exe). l2rprep.bat simply sets up the correct environment for latex2rtf but does not launch latex2rtf itself. You don't need it, as you already have the correct environment set when using LyX, except for RTFPATH if you don't install to C:\l2r. Note that you could also specify the config directory through a command line option. Suppose that you installed latex2rtf to C:\Program Files\latex2rtf, then you could simply use something like: latex2rt -P C:/Program Files/latex2rtf/cfg -p -S -o file.rtf file.tex but the -P option is broken and doesn't work. I think that it is due to the fact that a path which does not begin with / is not recognized as being absolute and is thus refused. However, if your current drive is C:, you can omit it and use instead: latex2rt -P /Program Files/latex2rtf/cfg -p -S -o file.rtf file.tex This works, try it. So, you could install to C:\Program Files\latex2rtf and then 1) add C:\Program Files\latex2rtf to PATH prefix 2) add -P /Program Files/latex2rtf/cfg to the latex2rtf converter entry in the LyX preferences or use a .bat file for setting RTFPATH and launching latex2rt, as I outlined in an other post. All in all, installing latex2rtf to C:\l2r maybe the best option. -- Enrico
2 Bugs
Hi, just found two bugs: 1. Bookmarks in ERTs crash Lyx 2. Changes in Document -- Settings -- Latex Preamble are lost when you go back to the main window without OK or Apply Could one of the developers file a bug? Regards, Toby
Re: article(APA) does not work in 1.5.x as it did in 1.4.x WAS exporting to rtf?
B. Bogart wrote: So I reiterate that I was able to use article(APA) in 1.4.x, but that it is not working in 1.5.x. What is not working excatly? Jürgen
RE: footnote in caption
Alexander Sklar wrote: Thanks for your replies, I visited the page Jürgen suggested, and perhaps this is a silly question but how do I add an optional parameter to a caption (to make it look different in the table of figures than in the actual caption text)? This would be somewhat of a workaround to have a footnote for the caption Insert-Short Title (while cursor is in the caption). Jürgen
Re: Exporting to Rich Text Format with latex2rtf, issues and a fix
Andre Poenitz wrote: Maybe you could add that to the wiki... Yes, please. Jürgen
Re: 2 Bugs
Tobias Krause wrote: 1. Bookmarks in ERTs crash Lyx Do you have a detailed recipe? Jürgen
Re: Bad PDF-Quality
On 23 Oct 2007, Bennett Helm wrote: On Oct 23, 2007, at 1:27 PM, August Linuxland wrote: Hi, I just tried to use LyX for my little paper I have to write, but there seems to be some issue with my Preferences. Here are two versions of the same Document, one processed through LyX, the other processed through TeXShop, which both use pdflatex: www.pogona.net/eight_lyx.pdf www.pogona.net/eight_texshop.pdf As you can see, there's a big difference in Quality. Maybe someone has a tip on how to improve the output quality of LyX. Thx, Pogon §7.3 of the FAQ (Help FAQ) tells you to look at §5.3.6 -- actually §5.3.6.2 -- of the Extended Features manual (Help Extended Featuers). Bennett On a slightly different note, if you are trying to make pdf files to upload to Lulu there are issues with embedded fonts. I find that the best thing is to send the file as postscript (.ps), which gets round this. Lulu does accept postscript although it doesn't advertise the fact. -- Anthony Campbell - [EMAIL PROTECTED] Microsoft-free zone - Using Linux Gnu-Debian http://www.acampbell.org.uk (blog, book reviews, on-line books and sceptical articles)
Re: Issues with v1.5.2 on OS X
Adam Treverrow wrote:
It's faster if you turn preview on!
Yes, that certainly helps -thanks. Collapsing floats and notes also
helps, but typing within an existing paragraph of text can still result
in excessive lag, which is a problem when editing text. I didn't notice
any improvement with Richard's suggestion to alter the window size.
1.5.3 will hopefully see improvements WRT this problem (especially when
typing within Inset). If you are able to compile from source, try this
patch after retrieving the BRANCH_1_5_X svn branch (it might also apply
cleanly to 1.5.2 source).
Abdel.
Index: BufferView.cpp
===
--- BufferView.cpp (revision 21185)
+++ BufferView.cpp (working copy)
@@ -1482,13 +1482,19 @@
// If the paragraph metrics has changed, we can not
// use the singlepar optimisation.
- if (singlepar
+ if (singlepar) {
+ pit_type const bottom_pit = cursor_.bottom().pit();
+ int old_height = tm.parMetrics(bottom_pit).height();
// In Single Paragraph mode, rebreak only
// the (main text, not inset!) paragraph containing the cursor.
// (if this paragraph contains insets etc., rebreaking will
// recursively descend)
-tm.redoParagraph(cursor_.bottom().pit()))
- singlepar = false;
+ tm.redoParagraph(bottom_pit);
+ // Paragraph height has changed so we cannot proceed to
+ // the singlePar optimisation.
+ if (tm.parMetrics(bottom_pit).height() != old_height)
+ singlepar = false;
+ }
pit_type const pit = anchor_ref_;
int pit1 = pit;
Index: insets/InsetCaption.h
===
--- insets/InsetCaption.h (revision 21185)
+++ insets/InsetCaption.h (working copy)
@@ -59,8 +59,6 @@
///
virtual bool getStatus(Cursor cur, FuncRequest const cmd,
FuncStatus ) const;
///
- virtual bool wide() const { return false; }
- ///
int latex(Buffer const buf, odocstream os,
OutputParams const ) const;
///
Index: insets/InsetCollapsable.cpp
===
--- insets/InsetCollapsable.cpp (revision 21185)
+++ insets/InsetCollapsable.cpp (working copy)
@@ -158,13 +158,10 @@
dim = dimensionCollapsed();
if (status() == Open) {
InsetText::metrics(mi, textdim_);
- // This expression should not contain mi.base.texwidth
openinlined_ = !hasFixedWidth()
-textdim_.wid 0.5 * mi.base.bv-workWidth();
+(textdim_.wid + dim.wid) =
mi.base.textwidth;
if (openinlined_) {
- // Correct for button width, and re-fit
- mi.base.textwidth -= dim.wid;
- InsetText::metrics(mi, textdim_);
+ // Correct for button width
dim.wid += textdim_.wid;
dim.des = max(dim.des - textdim_.asc + dim.asc,
textdim_.des);
dim.asc = textdim_.asc;
Index: insets/InsetFloat.h
===
--- insets/InsetFloat.h (revision 21185)
+++ insets/InsetFloat.h (working copy)
@@ -61,8 +61,6 @@
///
Inset::Code lyxCode() const { return Inset::FLOAT_CODE; }
///
- virtual bool wide() const { return false; }
- ///
int latex(Buffer const , odocstream ,
OutputParams const ) const;
///
Index: insets/InsetOptArg.h
===
--- insets/InsetOptArg.h(revision 21185)
+++ insets/InsetOptArg.h(working copy)
@@ -31,8 +31,6 @@
Inset::Code lyxCode() const { return Inset::OPTARG_CODE; }
/// return an message upon editing
virtual docstring const editMessage() const;
- ///
- virtual bool wide() const { return false; }
/// Standard LaTeX output -- short-circuited
int latex(Buffer const , odocstream ,
Index: insets/InsetText.cpp
===
--- insets/InsetText.cpp(revision 21185)
+++ insets/InsetText.cpp(working copy)
@@ -78,7 +78,7 @@
InsetText::InsetText(BufferParams const bp)
- : drawFrame_(false), frame_color_(Color::insetframe)
+ : drawFrame_(false), frame_color_(Color::insetframe),
fixed_width_(false)
{
paragraphs().push_back(Paragraph());
paragraphs().back().layout(bp.getTextClass().defaultLayout());
@@ -90,7 +90,7 @@
Re: 2 Bugs
Tobias Krause [EMAIL PROTECTED] writes: 1. Bookmarks in ERTs crash Lyx When does it crash? When you save? 2. Changes in Document -- Settings -- Latex Preamble are lost when you go back to the main window without OK or Apply Does not look like a bug to me, but I probably did not understand you well. JMarc
Re: 2 Bugs
@ Jean-Marc: no, not when I save, but when I trie ot use the bookmark @ Juergen: detailded recipe is here: lyx: Disabling LyX socket. Warning: Output is empty An empty output file was generated. This is BibTeX, Version 0.99c (MiKTeX 2.6) The top-level auxiliary file: LDA.aux The style file: 1XXX_natdin.bst month is an unknown function---line 294 of file 1XXX_natdin.bst month is an unknown function---line 300 of file 1XXX_natdin.bst type is an unknown function---line 311 of file 1XXX_natdin.bst type is an unknown function---line 312 of file 1XXX_natdin.bst type is an unknown function---line 313 of file 1XXX_natdin.bst type is an unknown function---line 315 of file 1XXX_natdin.bst lastchecked is an unknown function---line 341 of file 1XXX_natdin.bst doi is an unknown function---line 342 of file 1XXX_natdin.bst urn is an unknown function---line 342 of file 1XXX_natdin.bst doi is an unknown function---line 347 of file 1XXX_natdin.bst urn is an unknown function---line 347 of file 1XXX_natdin.bst lastchecked is an unknown function---line 352 of file 1XXX_natdin.bst type is an unknown function---line 360 of file 1XXX_natdin.bst type is an unknown function---line 361 of file 1XXX_natdin.bst type is an unknown function---line 362 of file 1XXX_natdin.bst doi is an unknown function---line 373 of file 1XXX_natdin.bst new.block is an unknown function---line 375 of file 1XXX_natdin.bst doi is an unknown function---line 375 of file 1XXX_natdin.bst urn is an unknown function---line 382 of file 1XXX_natdin.bst doi is an unknown function---line 383 of file 1XXX_natdin.bst type is an unknown function---line 386 of file 1XXX_natdin.bst type is an unknown function---line 387 of file 1XXX_natdin.bst type is an unknown function---line 388 of file 1XXX_natdin.bst urn is an unknown function---line 406 of file 1XXX_natdin.bst type is an unknown function---line 414 of file 1XXX_natdin.bst type is an unknown function---line 416 of file 1XXX_natdin.bst type is an unknown function---line 417 of file 1XXX_natdin.bst organization is an unknown function---line 642 of file 1XXX_natdin.bst organization is an unknown function---line 649 of file 1XXX_natdin.bst organization is an unknown function---line 651 of file 1XXX_natdin.bst organization is an unknown function---line 658 of file 1XXX_natdin.bst organization is an unknown function---line 661 of file 1XXX_natdin.bst organization is an unknown function---line 674 of file 1XXX_natdin.bst organization is an unknown function---line 677 of file 1XXX_natdin.bst organization is an unknown function---line 678 of file 1XXX_natdin.bst institution is an unknown function---line 685 of file 1XXX_natdin.bst institution is an unknown function---line 687 of file 1XXX_natdin.bst type is an unknown function---line 717 of file 1XXX_natdin.bst type is an unknown function---line 719 of file 1XXX_natdin.bst type is an unknown function---line 720 of file 1XXX_natdin.bst type is an unknown function---line 723 of file 1XXX_natdin.bst doi is an unknown function---line 768 of file 1XXX_natdin.bst urn is an unknown function---line 768 of file 1XXX_natdin.bst doi is an unknown function---line 779 of file 1XXX_natdin.bst urn is an unknown function---line 779 of file 1XXX_natdin.bst address is an unknown function---line 787 of file 1XXX_natdin.bst address is an unknown function---line 794 of file 1XXX_natdin.bst address is an unknown function---line 798 of file 1XXX_natdin.bst address is an unknown function---line 807 of file 1XXX_natdin.bst address is an unknown function---line 808 of file 1XXX_natdin.bst urn is an unknown function---line 817 of file 1XXX_natdin.bst doi is an unknown function---line 817 of file 1XXX_natdin.bst howpublished is an unknown function---line 818 of file 1XXX_natdin.bst address is an unknown function---line 819 of file 1XXX_natdin.bst type is an unknown function---line 820 of file 1XXX_natdin.bst type is an unknown function---line 822 of file 1XXX_natdin.bst address is an unknown function---line 832 of file 1XXX_natdin.bst address is an unknown function---line 835 of file 1XXX_natdin.bst howpublished is an unknown function---line 836 of file 1XXX_natdin.bst address is an unknown function---line 837 of file 1XXX_natdin.bst howpublished is an unknown function---line 837 of file 1XXX_natdin.bst howpublished is an unknown function---line 842 of file 1XXX_natdin.bst howpublished is an unknown function---line 844 of file 1XXX_natdin.bst urn is an unknown function---line 943 of file 1XXX_natdin.bst doi is an unknown function---line 944 of file 1XXX_natdin.bst doi is an unknown function---line 946 of file 1XXX_natdin.bst urn is an unknown function---line 949 of file 1XXX_natdin.bst isbn is an unknown function---line 954 of file 1XXX_natdin.bst issn is an unknown function---line 955 of file 1XXX_natdin.bst issn is an unknown function---line 957 of file 1XXX_natdin.bst isbn is an unknown function---line 960 of file 1XXX_natdin.bst note is an unknown
Re: 2 Bugs
Tobias Krause wrote: @ Juergen: detailded recipe is here: With recipe, I mean: what actions do you exactly perform in order to trigger the crash? I'm unable to reproduce the crash. Most of your console output is unrelated, the related part is this: Assertion triggered in void __thiscall lyx::Text::setCurrentFont(class lyx::Cursor ) by failing check this == cur.text() in file D:\LyX\lyx-1.5.2\src\Text2.cpp:757 Which installer did you use? I think assertions should be really disabled in stable releases. Jürgen
Re: 2 Bugs
Hi! I confirm both bugs with LyX 1.5.2 on Windows (official installer) Recipes here: 1st Bug- Open Latex Preamble window. Write whatever in the preamble. Click with the mouse on themain LyX window. As a result the little window with the document settings goes to second plane. Go back to that window. MAGIC! What you wrote has disappeared. 2nd Bug- Open a new document. Create an ERT box. Execute Navigate-Bookmarks-Save bookmark 1. Try to open a new document and LyX crashes. Nicolás Juergen Spitzmueller wrote: Tobias Krause wrote: @ Juergen: detailded recipe is here: With recipe, I mean: what actions do you exactly perform in order to trigger the crash? I'm unable to reproduce the crash. Most of your console output is unrelated, the related part is this: Assertion triggered in void __thiscall lyx::Text::setCurrentFont(class lyx::Cursor ) by failing check this == cur.text() in file D:\LyX\lyx-1.5.2\src\Text2.cpp:757 Which installer did you use? I think assertions should be really disabled in stable releases. Jürgen
Re: 2 Bugs
Nicolás wrote: 2nd Bug- Open a new document. Create an ERT box. Execute Navigate-Bookmarks-Save bookmark 1. Try to open a new document and LyX crashes. I cannot reproduce on Linux. Could you provide a backtrace? Jürgen
Re: 2 Bugs
Juergen Spitzmueller wrote: Nicolás wrote: 2nd Bug- Open a new document. Create an ERT box. Execute Navigate-Bookmarks-Save bookmark 1. Try to open a new document and LyX crashes. I cannot reproduce on Linux. Could you provide a backtrace? You mean a debugging trace? If so, which debug option you want me to use? Jürgen
Re: Exporting to Rich Text Format with latex2rtf, issues and a fix
Dave Hewitt [EMAIL PROTECTED] writes: Ideally, one would simply: (1) install latex2rtf from sourceforge (win-gui download here - http://sourceforge.net/project/showfiles.php?group_id=22654) (2) add the latex2rtf folder (C:\l2r -- see below) to the Windows search path (see section 2.4 here - http://sourceforge.net/project/showfiles.php?group_id=22654) (3) open LyX, reconfigure, close, and restart and the converter for Latex (plain) - Rich Text Format would be sorted out by LyX and a Rich Text Format option would be made available under File - Export. Unfortunately, it ain't that easy. Well, as the one who makes the DOS/Win port of latex2rtf, I can explain why it is as is and why some thing work and others not. See below. First off, the above strategy works fine if all you want to do is use the latex2rtf GUI (l2rshell.exe; the icon on the desktop calls this) to convert existing .tex files to .rtf files. In fact, you only need (1) and (2) above for that, and then you just export plain latex from LyX and run the conversion manually. Getting LyX to recognize the converter (latex2rt.exe) is the hard part, but it's nice to have LyX do all the work behind the scenes. The first issue is that you should simply avoid installing the program anywhere but C:\l2r. All of the defaults for the program assume that it is installed at this path. I installed to Program Files because I had not read section 2.4 here - http://sourceforge.net/project/showfiles.php?group_id=22654 - first. It explains how to adjust the three configuration files (more on these in a minute) to make latex2rtf work from any installation path, but it never worked for me, and I tried a lot of different things. No matter what I tried, running LyX from the command prompt showed that the error was that latex2rtf could not find its config directory (the cfg directory under the latex2rtf root directory). It always assumed that the root directory was C:\l2r despite the fact that all entries in the configuration files were adjusted to reflect C:\Program Files\latex2rtf, where I installed it. What do you mean by configuration files? Adapting the pathes in the batch files (l2rprep.bat, l2r.bat) only helps if these batch files are executed. If you just call latex2rt.exe, they aren't. The configuration of the GUI shell is used only by the GUI shell. latex2rt.exe itself knows nothing of the GUI shell nor of the batch files. So, make your life easy and install to C:\l2r. I never checked this with the latex2rtf folks, but the simple solution seems to be obvious. Next, you do need to add the latex2rtf folder to the Windows search path: a. Right-click My Computer and go to Properties. b. Advanced Tab - Environment Variables - System Variables - Path, add C:\l2r; (no quotes) somewhere in the line. The next step varies depending on how you have LaTeX set up on your machine. I used the LyXWinInstaller and this presents a new wrinkle for latex2rtf. Those three configuration files (.bat files) are in the latex2rtf root and are L2R.BAT, L2RSEM.BAT, and L2RPREP.BAT. You'll need to edit them (use a good text editor; i.e., not Notepad). L2R and L2RSEM are almost identical, but notice that one of them (don't recall which, I changed it), on line 15, has the German windows settings line unremarked. The other one has the English windows settings unremarked. I changed them both to have the English settings unremarked (i.e., functional) and the German settings remarked (i.e., unfunctional). I didn't actually test whether this mattered, but it seemed prudent. The paths should all be fine if you installed to C:\l2r and you need do nothing more with these files. At this point, I tried reconfiguring LyX and it still failed to find the converter. L2RPREP comes in - this is a bit tougher. I ran this file from a command prompt to see that it set the paths correctly. As best I could tell, which always failed to find the Ghostscript, LaTeX, and ImageMagick files. That is OK. Which only looks in the current search path. If the Ghostscript, LaTeX or ImageMagick folders isn't yet in the PATH, which returns 1. Calling which is intended to avoid adding the folders to the path more than once. So, I edited it to look as below (changes starting on line 8). Again, this applies for people that use LyXWinInstaller only. rem set folder containing Ghostscript executables here: %l2rpath%\which gswin32c nul if errorlevel 1 SET PATH=C:\Program Files\LyX 1.5.2\etc\Ghostscript\bin;C:\Program Files\LyX 1.5.2\etc\Ghostscript\lib;%PATH% rem set folder containing ImageMagick executables here: %l2rpath%\which identify nul if errorlevel 1 SET PATH=C:\Program Files\LyX 1.5.2\etc\ImageMagick;%PATH% rem set folder containing LaTeX and dvips executables here: %l2rpath%\which latex nul if errorlevel 1 SET PATH=C:\Program Files\MiKTeX 2.6\miktex\bin;%PATH% The final
Re: 2 Bugs
Nicolás wrote: You mean a debugging trace? If so, which debug option you want me to use? No, a backtrace with a debugger like GDB. I don't know what's the best way to get this on windows, though. Jürgen
Re: exporting to rtf?
B. Bogart wrote: I did indeed do reconfigure and restarted LyX. LyX complains about the file with the following: The layout file requested by this document, apa.layout, is not usable. This is probably because a LaTeX class or style file required by it is not available. See the Customization documentation for more information. LyX will not be able to produce output. I confirm that I do have APA installed: $ kpsewhich apa.cls /usr/share/texmf-texlive/tex/latex/apa/apa.cls Perhaps apa.layout was included in the ubuntu 1.4.x package, but not in 1.5.1? Don't know the answer to that -- I haven't installed an ubuntu package (yet -- it's on my to-do-someday list). You should be able to find the layout files in LyX root/Resources/layouts and confirm whether apa.layout is there. If not, I can easily e-mail it to you. I'm pretty sure you have the layout file, though: you posted earlier that it was listed in LyX as unavailable. If you didn't have the layout file, it would not be listed at all. You might confirm (via kpsewhich) that apacite.sty is also installed. If I'm reading apa.layout correctly, it tells LyX that apacite.sty is also used. I'm not sure what would happen if the configuration package found apa.cls but not apacite.sty. As of version 1.5.x at least, when you reconfigure LyX, it writes a log file in your user directory (at least on Windows). If present, it will tell you whether it searched for, and whether it found, the APA class. For instance, mine has +checking for document class apa [apa,apacite.sty]... yes If there's no checking for message, it didn't see a layout file. If there's a message but it says no, it found the layout file but not the class or style file(s). /Paul
Re: 2 Bugs
Juergen Spitzmueller wrote: Nicolás wrote: You mean a debugging trace? If so, which debug option you want me to use? No, a backtrace with a debugger like GDB. I don't know what's the best way to get this on windows, though. Neither myself :-) Maybe someone else can do it? Jürgen
layout file format versions
Hi All, I am trying for the first time to setup a layout file, and have got some way forwards, however I am uncertain of the importance of the 'format' command in the layout file. The customization manual indicates that it refers to version 2 however the book.layout I'm basing my layout on uses version 4 and try as I might I can't locate any information about this version. Can some one point me in the right direction? Or better still tell me it doesn't matter much and I can stop worrying about it. Thanks Ian
Re: layout file format versions
On Thu, Oct 25, 2007 at 07:32:27PM +, ian holliday wrote: Hi All, I am trying for the first time to setup a layout file, and have got some way forwards, however I am uncertain of the importance of the 'format' command in the layout file. The customization manual indicates that it refers to version 2 however the book.layout I'm basing my layout on uses version 4 and try as I might I can't locate any information about this version. Can some one point me in the right direction? Or better still tell me it doesn't matter much and I can stop worrying about it. It does not matter _too_ much. There is not too much documentation for either ;-) Andre'
Re: Exporting to Rich Text Format with latex2rtf, issues and a fix
Wilfried, thanks a lot for your input. This was just a novice hackjob that worked, and my goal (as stated at the end) was to get a solid working solution that could be placed on the LyX wiki. I admit lots of ignorance on all of this. Nonetheless, I figured that since I started this I should try and finish it. So, I began by working on Enrico's suggested solution... but I found out it's all much easier than that. All I did was: (1) uninstall latex2rtf (to remove all my edited files), remove C:\l2r and C:\Program Files\LyX 1.5.2 from my Windows search path, then reconfigure LyX (RTF export disappeared) (2) reinstall latex2rtf to C:\l2r, put C:\l2r on the search path again, start LyX, reconfigure, and restart LyX - LyX FAILS to find the converter (3) close LyX, restart LyX, reconfigure again, close and restart LyX - WORKS FINE I did steps 1-3 three times and it works that way every time... the only thing you need to do apparently is reconfigure LyX TWICE after installing latex2rtf and adding the folder to the search path. (I closed and restarted LyX between reconfigurations, but I don't know that that matters). I still think it's simplest to just install latex2rtf to C:\l2r. There may be other complications if you install elsewhere, but I didn't test that. This strikes me as weird. Does LyX do this for other converters... how does configure behave differently between successive calls? Can anyone else try this and see if they repeat it? Anyway, apparently all of my problems with the configuration files (the .bat's) were a waste of time - the second time I reconfigured LyX it worked despite all of that. As Wilfried noted, I think (see below), those files are irrelevant to LyX's use of the converter (latex2rt.exe) and the GUI shell. Remaining question: Enrico, I think that l2rprep.bat is intended to do the same thing you proposed with the new .bat file - set rtfpath. No? Either way, it seems only relevant when the .bat files are being called... and (again, see below) I think Wilfried indicates that they are not when LyX calls latex2rt (.exe). Questions/comments inserted in Wilfried's comments below... Ideally, one would simply: (1) install latex2rtf from sourceforge (win-gui download here - http://sourceforge.net/project/showfiles.php?group_id=22654) (2) add the latex2rtf folder (C:\l2r -- see below) to the Windows search path (see section 2.4 here - http://sourceforge.net/project/showfiles.php?group_id=22654) (3) open LyX, reconfigure, close, and restart and the converter for Latex (plain) - Rich Text Format would be sorted out by LyX and a Rich Text Format option would be made available under File - Export. Unfortunately, it ain't that easy. Well, as the one who makes the DOS/Win port of latex2rtf, I can explain why it is as is and why some thing work and others not. See below. First off, the above strategy works fine if all you want to do is use the latex2rtf GUI (l2rshell.exe; the icon on the desktop calls this) to convert existing .tex files to .rtf files. In fact, you only need (1) and (2) above for that, and then you just export plain latex from LyX and run the conversion manually. Getting LyX to recognize the converter (latex2rt.exe) is the hard part, but it's nice to have LyX do all the work behind the scenes. The first issue is that you should simply avoid installing the program anywhere but C:\l2r. All of the defaults for the program assume that it is installed at this path. I installed to Program Files because I had not read section 2.4 here - http://sourceforge.net/project/showfiles.php?group_id=22654 - first. It explains how to adjust the three configuration files (more on these in a minute) to make latex2rtf work from any installation path, but it never worked for me, and I tried a lot of different things. No matter what I tried, running LyX from the command prompt showed that the error was that latex2rtf could not find its config directory (the cfg directory under the latex2rtf root directory). It always assumed that the root directory was C:\l2r despite the fact that all entries in the configuration files were adjusted to reflect C:\Program Files\latex2rtf, where I installed it. What do you mean by configuration files? Adapting the pathes in the batch files (l2rprep.bat, l2r.bat) only helps if these batch files are executed. If you just call latex2rt.exe, they aren't. The configuration of the GUI shell is used only by the GUI shell. latex2rt.exe itself knows nothing of the GUI shell nor of the batch files. I was referring to the .bat files, without knowing what they really did. My fault. So does this means that LyX doesn't need to know about the .bat files? It looks like all that LyX is doing is calling the latex2rt (.exe file) to get the conversion. Right? So, make your life easy and install to C:\l2r. I never checked this with the latex2rtf folks, but the simple solution seems to be
Toolbar font and font size
I'm just back to using Lyx after a long break; the font used in the toolbar has become very small. How can Lyx be configured to use a larger font? Thanks - jon
Re: 2 Bugs
On Oct 25, 2007, at 1:09 PM, Nicolás wrote: Hi! I confirm both bugs with LyX 1.5.2 on Windows (official installer) Recipes here: 1st Bug- Open Latex Preamble window. Write whatever in the preamble. Click with the mouse on themain LyX window. As a result the little window with the document settings goes to second plane. Go back to that window. MAGIC! What you wrote has disappeared. I can confirm this on OS X 2nd Bug- Open a new document. Create an ERT box. Execute Navigate- Bookmarks-Save bookmark 1. Try to open a new document and LyX crashes. No problem on OS X Nicolás Juergen Spitzmueller wrote: Tobias Krause wrote: @ Juergen: detailded recipe is here: With recipe, I mean: what actions do you exactly perform in order to trigger the crash? I'm unable to reproduce the crash. Most of your console output is unrelated, the related part is this: Assertion triggered in void __thiscall lyx::Text::setCurrentFont (class lyx::Cursor ) by failing check this == cur.text() in file D:\LyX\lyx-1.5.2\src\Text2.cpp:757 Which installer did you use? I think assertions should be really disabled in stable releases. Jürgen
Re: layout file format versions
Andre Poenitz [EMAIL PROTECTED] writes: It does not matter _too_ much. There is not too much documentation for either Andre' Thanks Andre' - I'll just assume the format won't be significantly different then.
Re: Exporting to Rich Text Format with latex2rtf, issues and a fix
Dave Hewitt writes: All I did was: (1) uninstall latex2rtf (to remove all my edited files), remove C:\l2r and C:\Program Files\LyX 1.5.2 from my Windows search path, then reconfigure LyX (RTF export disappeared) (2) reinstall latex2rtf to C:\l2r, put C:\l2r on the search path again, start LyX, reconfigure, and restart LyX - LyX FAILS to find the converter If you mean that you added C:\l2r to PATH prefix in LyX preferences and then reconfigured, then this is explained by the fact that changes to PATH prefix are only taken after you save preferences and close and restart LyX. (3) close LyX, restart LyX, reconfigure again, close and restart LyX - WORKS FINE Yes, because now the previously set PATH prefix is taken into account. I did steps 1-3 three times and it works that way every time... the only thing you need to do apparently is reconfigure LyX TWICE after installing latex2rtf and adding the folder to the search path. No, you need to close and restart LyX after adding the folder to PATH prefix. Otherwise, the PATH prefix as set at LyX start is still used, no matter that you changed it. (I closed and restarted LyX between reconfigurations, but I don't know that that matters). I still think it's simplest to just install latex2rtf to C:\l2r. There may be other complications if you install elsewhere, but I didn't test that. If you install to C:\l2r, you only need to add C:\l2r to PATH prefix. If you install latex2rtf somewhere else, you have to specify where its config directory is. There are no other complications. Enrico, I think that l2rprep.bat is intended to do the same thing you proposed with the new .bat file - set rtfpath. No? Either way, it seems only relevant when the .bat files are being called... and (again, see below) I think Wilfried indicates that they are not when LyX calls latex2rt (.exe). l2rprep.bat simply sets up the correct environment for latex2rtf but does not launch latex2rtf itself. You don't need it, as you already have the correct environment set when using LyX, except for RTFPATH if you don't install to C:\l2r. Note that you could also specify the config directory through a command line option. Suppose that you installed latex2rtf to C:\Program Files\latex2rtf, then you could simply use something like: latex2rt -P C:/Program Files/latex2rtf/cfg -p -S -o file.rtf file.tex but the -P option is broken and doesn't work. I think that it is due to the fact that a path which does not begin with / is not recognized as being absolute and is thus refused. However, if your current drive is C:, you can omit it and use instead: latex2rt -P /Program Files/latex2rtf/cfg -p -S -o file.rtf file.tex This works, try it. So, you could install to C:\Program Files\latex2rtf and then 1) add C:\Program Files\latex2rtf to PATH prefix 2) add -P /Program Files/latex2rtf/cfg to the latex2rtf converter entry in the LyX preferences or use a .bat file for setting RTFPATH and launching latex2rt, as I outlined in an other post. All in all, installing latex2rtf to C:\l2r maybe the best option. -- Enrico
2 Bugs
Hi, just found two bugs: 1. Bookmarks in ERTs crash Lyx 2. Changes in Document --> Settings --> Latex Preamble are lost when you go back to the main window without "OK" or "Apply" Could one of the developers file a bug? Regards, Toby
Re: article(APA) does not work in 1.5.x as it did in 1.4.x WAS exporting to rtf?
B. Bogart wrote: > So I reiterate that I was able to use "article(APA)" in 1.4.x, but that > it is not working in 1.5.x. What is not working excatly? Jürgen
RE: footnote in caption
Alexander Sklar wrote: > Thanks for your replies, I visited the page Jürgen suggested, and perhaps > this is a silly question but how do I add an optional parameter to a > caption (to make it look different in the table of figures than in the > actual caption text)? This would be somewhat of a workaround to have a > footnote for the caption Insert->Short Title (while cursor is in the caption). Jürgen
Re: Exporting to Rich Text Format with latex2rtf, issues and a fix
Andre Poenitz wrote: > Maybe you could add that to the wiki... Yes, please. Jürgen
Re: 2 Bugs
Tobias Krause wrote: > 1. Bookmarks in ERTs crash Lyx Do you have a detailed recipe? Jürgen
Re: Bad PDF-Quality
On 23 Oct 2007, Bennett Helm wrote: > On Oct 23, 2007, at 1:27 PM, August Linuxland wrote: > >> Hi, >> I just tried to use LyX for my little paper I have to write, but there >> seems to be some issue with my Preferences. >> Here are two versions of the same Document, one processed through LyX, the >> other processed through TeXShop, which both use pdflatex: >> >> www.pogona.net/eight_lyx.pdf >> www.pogona.net/eight_texshop.pdf >> >> As you can see, there's a big difference in Quality. Maybe someone has a >> tip on how to improve the output quality of LyX. >> Thx, >> Pogon > > §7.3 of the FAQ (Help > FAQ) tells you to look at §5.3.6 -- actually > §5.3.6.2 -- of the Extended Features manual (Help > Extended Featuers). > > Bennett On a slightly different note, if you are trying to make pdf files to upload to Lulu there are issues with embedded fonts. I find that the best thing is to send the file as postscript (.ps), which gets round this. Lulu does accept postscript although it doesn't advertise the fact. -- Anthony Campbell - [EMAIL PROTECTED] Microsoft-free zone - Using Linux Gnu-Debian http://www.acampbell.org.uk (blog, book reviews, on-line books and sceptical articles)
Re: Issues with v1.5.2 on OS X
Adam Treverrow wrote:
It's faster if you turn preview on!
Yes, that certainly helps -thanks. Collapsing floats and notes also
helps, but typing within an existing paragraph of text can still result
in excessive lag, which is a problem when editing text. I didn't notice
any improvement with Richard's suggestion to alter the window size.
1.5.3 will hopefully see improvements WRT this problem (especially when
typing within Inset). If you are able to compile from source, try this
patch after retrieving the BRANCH_1_5_X svn branch (it might also apply
cleanly to 1.5.2 source).
Abdel.
Index: BufferView.cpp
===
--- BufferView.cpp (revision 21185)
+++ BufferView.cpp (working copy)
@@ -1482,13 +1482,19 @@
// If the paragraph metrics has changed, we can not
// use the singlepar optimisation.
- if (singlepar
+ if (singlepar) {
+ pit_type const bottom_pit = cursor_.bottom().pit();
+ int old_height = tm.parMetrics(bottom_pit).height();
// In Single Paragraph mode, rebreak only
// the (main text, not inset!) paragraph containing the cursor.
// (if this paragraph contains insets etc., rebreaking will
// recursively descend)
- && tm.redoParagraph(cursor_.bottom().pit()))
- singlepar = false;
+ tm.redoParagraph(bottom_pit);
+ // Paragraph height has changed so we cannot proceed to
+ // the singlePar optimisation.
+ if (tm.parMetrics(bottom_pit).height() != old_height)
+ singlepar = false;
+ }
pit_type const pit = anchor_ref_;
int pit1 = pit;
Index: insets/InsetCaption.h
===
--- insets/InsetCaption.h (revision 21185)
+++ insets/InsetCaption.h (working copy)
@@ -59,8 +59,6 @@
///
virtual bool getStatus(Cursor & cur, FuncRequest const & cmd,
FuncStatus &) const;
///
- virtual bool wide() const { return false; }
- ///
int latex(Buffer const & buf, odocstream & os,
OutputParams const &) const;
///
Index: insets/InsetCollapsable.cpp
===
--- insets/InsetCollapsable.cpp (revision 21185)
+++ insets/InsetCollapsable.cpp (working copy)
@@ -158,13 +158,10 @@
dim = dimensionCollapsed();
if (status() == Open) {
InsetText::metrics(mi, textdim_);
- // This expression should not contain mi.base.texwidth
openinlined_ = !hasFixedWidth()
- && textdim_.wid < 0.5 * mi.base.bv->workWidth();
+ && (textdim_.wid + dim.wid) <=
mi.base.textwidth;
if (openinlined_) {
- // Correct for button width, and re-fit
- mi.base.textwidth -= dim.wid;
- InsetText::metrics(mi, textdim_);
+ // Correct for button width
dim.wid += textdim_.wid;
dim.des = max(dim.des - textdim_.asc + dim.asc,
textdim_.des);
dim.asc = textdim_.asc;
Index: insets/InsetFloat.h
===
--- insets/InsetFloat.h (revision 21185)
+++ insets/InsetFloat.h (working copy)
@@ -61,8 +61,6 @@
///
Inset::Code lyxCode() const { return Inset::FLOAT_CODE; }
///
- virtual bool wide() const { return false; }
- ///
int latex(Buffer const &, odocstream &,
OutputParams const &) const;
///
Index: insets/InsetOptArg.h
===
--- insets/InsetOptArg.h(revision 21185)
+++ insets/InsetOptArg.h(working copy)
@@ -31,8 +31,6 @@
Inset::Code lyxCode() const { return Inset::OPTARG_CODE; }
/// return an message upon editing
virtual docstring const editMessage() const;
- ///
- virtual bool wide() const { return false; }
/// Standard LaTeX output -- short-circuited
int latex(Buffer const &, odocstream &,
Index: insets/InsetText.cpp
===
--- insets/InsetText.cpp(revision 21185)
+++ insets/InsetText.cpp(working copy)
@@ -78,7 +78,7 @@
InsetText::InsetText(BufferParams const & bp)
- : drawFrame_(false), frame_color_(Color::insetframe)
+ : drawFrame_(false), frame_color_(Color::insetframe),
fixed_width_(false)
{
paragraphs().push_back(Paragraph());
paragraphs().back().layout(bp.getTextClass().defaultLayout());
@@ -90,7
Re: 2 Bugs
Tobias Krause <[EMAIL PROTECTED]> writes: > 1. Bookmarks in ERTs crash Lyx When does it crash? When you save? > 2. Changes in Document --> Settings --> Latex Preamble are lost when > you go back to the main window without "OK" or "Apply" Does not look like a bug to me, but I probably did not understand you well. JMarc
Re: 2 Bugs
@ Jean-Marc: no, not when I save, but when I trie ot use the bookmark @ Juergen: detailded recipe is here: lyx: Disabling LyX socket. Warning: Output is empty An empty output file was generated. This is BibTeX, Version 0.99c (MiKTeX 2.6) The top-level auxiliary file: LDA.aux The style file: 1XXX_natdin.bst month is an unknown function---line 294 of file 1XXX_natdin.bst month is an unknown function---line 300 of file 1XXX_natdin.bst type is an unknown function---line 311 of file 1XXX_natdin.bst type is an unknown function---line 312 of file 1XXX_natdin.bst type is an unknown function---line 313 of file 1XXX_natdin.bst type is an unknown function---line 315 of file 1XXX_natdin.bst lastchecked is an unknown function---line 341 of file 1XXX_natdin.bst doi is an unknown function---line 342 of file 1XXX_natdin.bst urn is an unknown function---line 342 of file 1XXX_natdin.bst doi is an unknown function---line 347 of file 1XXX_natdin.bst urn is an unknown function---line 347 of file 1XXX_natdin.bst lastchecked is an unknown function---line 352 of file 1XXX_natdin.bst type is an unknown function---line 360 of file 1XXX_natdin.bst type is an unknown function---line 361 of file 1XXX_natdin.bst type is an unknown function---line 362 of file 1XXX_natdin.bst doi is an unknown function---line 373 of file 1XXX_natdin.bst new.block is an unknown function---line 375 of file 1XXX_natdin.bst doi is an unknown function---line 375 of file 1XXX_natdin.bst urn is an unknown function---line 382 of file 1XXX_natdin.bst doi is an unknown function---line 383 of file 1XXX_natdin.bst type is an unknown function---line 386 of file 1XXX_natdin.bst type is an unknown function---line 387 of file 1XXX_natdin.bst type is an unknown function---line 388 of file 1XXX_natdin.bst urn is an unknown function---line 406 of file 1XXX_natdin.bst type is an unknown function---line 414 of file 1XXX_natdin.bst type is an unknown function---line 416 of file 1XXX_natdin.bst type is an unknown function---line 417 of file 1XXX_natdin.bst organization is an unknown function---line 642 of file 1XXX_natdin.bst organization is an unknown function---line 649 of file 1XXX_natdin.bst organization is an unknown function---line 651 of file 1XXX_natdin.bst organization is an unknown function---line 658 of file 1XXX_natdin.bst organization is an unknown function---line 661 of file 1XXX_natdin.bst organization is an unknown function---line 674 of file 1XXX_natdin.bst organization is an unknown function---line 677 of file 1XXX_natdin.bst organization is an unknown function---line 678 of file 1XXX_natdin.bst institution is an unknown function---line 685 of file 1XXX_natdin.bst institution is an unknown function---line 687 of file 1XXX_natdin.bst type is an unknown function---line 717 of file 1XXX_natdin.bst type is an unknown function---line 719 of file 1XXX_natdin.bst type is an unknown function---line 720 of file 1XXX_natdin.bst type is an unknown function---line 723 of file 1XXX_natdin.bst doi is an unknown function---line 768 of file 1XXX_natdin.bst urn is an unknown function---line 768 of file 1XXX_natdin.bst doi is an unknown function---line 779 of file 1XXX_natdin.bst urn is an unknown function---line 779 of file 1XXX_natdin.bst address is an unknown function---line 787 of file 1XXX_natdin.bst address is an unknown function---line 794 of file 1XXX_natdin.bst address is an unknown function---line 798 of file 1XXX_natdin.bst address is an unknown function---line 807 of file 1XXX_natdin.bst address is an unknown function---line 808 of file 1XXX_natdin.bst urn is an unknown function---line 817 of file 1XXX_natdin.bst doi is an unknown function---line 817 of file 1XXX_natdin.bst howpublished is an unknown function---line 818 of file 1XXX_natdin.bst address is an unknown function---line 819 of file 1XXX_natdin.bst type is an unknown function---line 820 of file 1XXX_natdin.bst type is an unknown function---line 822 of file 1XXX_natdin.bst address is an unknown function---line 832 of file 1XXX_natdin.bst address is an unknown function---line 835 of file 1XXX_natdin.bst howpublished is an unknown function---line 836 of file 1XXX_natdin.bst address is an unknown function---line 837 of file 1XXX_natdin.bst howpublished is an unknown function---line 837 of file 1XXX_natdin.bst howpublished is an unknown function---line 842 of file 1XXX_natdin.bst howpublished is an unknown function---line 844 of file 1XXX_natdin.bst urn is an unknown function---line 943 of file 1XXX_natdin.bst doi is an unknown function---line 944 of file 1XXX_natdin.bst doi is an unknown function---line 946 of file 1XXX_natdin.bst urn is an unknown function---line 949 of file 1XXX_natdin.bst isbn is an unknown function---line 954 of file 1XXX_natdin.bst issn is an unknown function---line 955 of file 1XXX_natdin.bst issn is an unknown function---line 957 of file 1XXX_natdin.bst isbn is an unknown function---line 960 of file 1XXX_natdin.bst note is an unknown
Re: 2 Bugs
Tobias Krause wrote: > @ Juergen: detailded recipe is here: With recipe, I mean: what actions do you exactly perform in order to trigger the crash? I'm unable to reproduce the crash. Most of your console output is unrelated, the related part is this: > Assertion triggered in void __thiscall lyx::Text::setCurrentFont(class > lyx::Cursor &) by failing check "this == cur.text()" in file > D:\LyX\lyx-1.5.2\src\Text2.cpp:757 Which installer did you use? I think assertions should be really disabled in stable releases. Jürgen
Re: 2 Bugs
Hi! I confirm both bugs with LyX 1.5.2 on Windows (official installer) Recipes here: 1st Bug- Open Latex Preamble window. Write whatever in the preamble. Click with the mouse on themain LyX window. As a result the little window with the document settings goes to second plane. Go back to that window. MAGIC! What you wrote has disappeared. 2nd Bug- Open a new document. Create an ERT box. Execute Navigate->Bookmarks->Save bookmark 1. Try to open a new document and LyX crashes. Nicolás Juergen Spitzmueller wrote: Tobias Krause wrote: @ Juergen: detailded recipe is here: With recipe, I mean: what actions do you exactly perform in order to trigger the crash? I'm unable to reproduce the crash. Most of your console output is unrelated, the related part is this: Assertion triggered in void __thiscall lyx::Text::setCurrentFont(class lyx::Cursor &) by failing check "this == cur.text()" in file D:\LyX\lyx-1.5.2\src\Text2.cpp:757 Which installer did you use? I think assertions should be really disabled in stable releases. Jürgen
Re: 2 Bugs
Nicolás wrote: > 2nd Bug- Open a new document. Create an ERT box. Execute > Navigate->Bookmarks->Save bookmark 1. Try to open a new document and LyX > crashes. I cannot reproduce on Linux. Could you provide a backtrace? Jürgen
Re: 2 Bugs
Juergen Spitzmueller wrote: Nicolás wrote: 2nd Bug- Open a new document. Create an ERT box. Execute Navigate->Bookmarks->Save bookmark 1. Try to open a new document and LyX crashes. I cannot reproduce on Linux. Could you provide a backtrace? You mean a debugging trace? If so, which debug option you want me to use? Jürgen
Re: Exporting to Rich Text Format with latex2rtf, issues and a fix
Dave Hewitt <[EMAIL PROTECTED]> writes: > Ideally, one would simply: > > (1) install latex2rtf from sourceforge (win-gui download here - > http://sourceforge.net/project/showfiles.php?group_id=22654) > (2) add the latex2rtf folder (C:\l2r -- see below) to the Windows search > path (see section 2.4 here - > http://sourceforge.net/project/showfiles.php?group_id=22654) > (3) open LyX, reconfigure, close, and restart > > and the converter for Latex (plain) -> Rich Text Format would be sorted out > by LyX and a Rich Text Format option would be made available under File -> > Export. > > Unfortunately, it ain't that easy. Well, as the one who makes the DOS/Win port of latex2rtf, I can explain why it is as is and why some thing work and others not. See below. > First off, the above strategy works fine if all you want to do is use the > latex2rtf GUI (l2rshell.exe; the icon on the desktop calls this) to convert > existing .tex files to .rtf files. In fact, you only need (1) and (2) above > for that, and then you just export plain latex from LyX and run the > conversion manually. Getting LyX to recognize the converter (latex2rt.exe) > is the hard part, but it's nice to have LyX do all the work behind the scenes. > > The first issue is that you should simply avoid installing the program > anywhere but C:\l2r. All of the defaults for the program assume that it is > installed at this path. I installed to Program Files because I had not read > section 2.4 here - > http://sourceforge.net/project/showfiles.php?group_id=22654 - first. It > explains how to adjust the three configuration files (more on these in a > minute) to make latex2rtf work from any installation path, but it never > worked for me, and I tried a lot of different things. No matter what I > tried, running LyX from the command prompt showed that the error was that > latex2rtf could not find its config directory (the cfg directory under the > latex2rtf root directory). It always assumed that the root directory was > C:\l2r despite the fact that all entries in the configuration files were > adjusted to reflect "C:\Program Files\latex2rtf", where I installed it. What do you mean by "configuration files"? Adapting the pathes in the batch files (l2rprep.bat, l2r.bat) only helps if these batch files are executed. If you just call latex2rt.exe, they aren't. The configuration of the GUI shell is used only by the GUI shell. latex2rt.exe itself knows nothing of the GUI shell nor of the batch files. > So, > make your life easy and install to C:\l2r. I never checked this with the > latex2rtf folks, but the simple solution seems to be obvious. > > Next, you do need to add the latex2rtf folder to the Windows search path: > > a. Right-click My Computer and go to Properties. > b. Advanced Tab -> Environment Variables -> System Variables -> Path, add > "C:\l2r;" (no quotes) somewhere in the line. > > The next step varies depending on how you have LaTeX set up on your > machine. I used the LyXWinInstaller and this presents a new wrinkle for > latex2rtf. > > Those three configuration files (.bat files) are in the latex2rtf root and > are L2R.BAT, L2RSEM.BAT, and L2RPREP.BAT. You'll need to edit them (use a > good text editor; i.e., not Notepad). > > L2R and L2RSEM are almost identical, but notice that one of them (don't > recall which, I changed it), on line 15, has the German windows settings > line unremarked. The other one has the English windows settings unremarked. > I changed them both to have the English settings unremarked (i.e., > functional) and the German settings remarked (i.e., unfunctional). I didn't > actually test whether this mattered, but it seemed prudent. The paths > should all be fine if you installed to C:\l2r and you need do nothing more > with these files. > > At this point, I tried reconfiguring LyX and it still failed to find the > converter. > > L2RPREP comes in - this is a bit tougher. I ran this file from a command > prompt to see that it set the paths correctly. As best I could tell, > "which" always failed to find the Ghostscript, LaTeX, and ImageMagick > files. That is OK. Which only looks in the current search path. If the Ghostscript, LaTeX or ImageMagick folders isn't yet in the PATH, which returns "1". Calling "which" is intended to avoid adding the folders to the path more than once. > So, I edited it to look as below (changes starting on line 8). > Again, this applies for people that use LyXWinInstaller only. > > rem set folder containing Ghostscript executables here: > %l2rpath%\which gswin32c >nul > if errorlevel 1 SET PATH="C:\Program Files\LyX > 1.5.2\etc\Ghostscript\bin";"C:\Program Files\LyX > 1.5.2\etc\Ghostscript\lib";%PATH% > > rem set folder containing ImageMagick executables here: > %l2rpath%\which identify >nul > if errorlevel 1 SET PATH="C:\Program Files\LyX 1.5.2\etc\ImageMagick";%PATH% > > rem set folder containing LaTeX and dvips executables here: >
Re: 2 Bugs
Nicolás wrote: > You mean a debugging trace? If so, which debug option you want me to use? No, a backtrace with a debugger like GDB. I don't know what's the best way to get this on windows, though. Jürgen
Re: exporting to rtf?
B. Bogart wrote: I did indeed do "reconfigure" and restarted LyX. LyX complains about the file with the following: The layout file requested by this document, apa.layout, is not usable. This is probably because a LaTeX class or style file required by it is not available. See the Customization documentation for more information. LyX will not be able to produce output. I confirm that I do have APA installed: $ kpsewhich apa.cls /usr/share/texmf-texlive/tex/latex/apa/apa.cls Perhaps apa.layout was included in the ubuntu 1.4.x package, but not in 1.5.1? Don't know the answer to that -- I haven't installed an ubuntu package (yet -- it's on my to-do-someday list). You should be able to find the layout files in /Resources/layouts and confirm whether apa.layout is there. If not, I can easily e-mail it to you. I'm pretty sure you have the layout file, though: you posted earlier that it was listed in LyX as "unavailable". If you didn't have the layout file, it would not be listed at all. You might confirm (via kpsewhich) that apacite.sty is also installed. If I'm reading apa.layout correctly, it tells LyX that apacite.sty is also used. I'm not sure what would happen if the configuration package found apa.cls but not apacite.sty. As of version 1.5.x at least, when you reconfigure LyX, it writes a log file in your user directory (at least on Windows). If present, it will tell you whether it searched for, and whether it found, the APA class. For instance, mine has +checking for document class apa [apa,apacite.sty]... yes If there's no "checking for" message, it didn't see a layout file. If there's a message but it says "no", it found the layout file but not the class or style file(s). /Paul
Re: 2 Bugs
Juergen Spitzmueller wrote: Nicolás wrote: You mean a debugging trace? If so, which debug option you want me to use? No, a backtrace with a debugger like GDB. I don't know what's the best way to get this on windows, though. Neither myself :-) Maybe someone else can do it? Jürgen
layout file format versions
Hi All, I am trying for the first time to setup a layout file, and have got some way forwards, however I am uncertain of the importance of the 'format' command in the layout file. The customization manual indicates that it refers to version 2 however the book.layout I'm basing my layout on uses version 4 and try as I might I can't locate any information about this version. Can some one point me in the right direction? Or better still tell me it doesn't matter much and I can stop worrying about it. Thanks Ian
Re: layout file format versions
On Thu, Oct 25, 2007 at 07:32:27PM +, ian holliday wrote: > Hi All, > > I am trying for the first time to setup a layout file, and have got > some way forwards, however I am uncertain of the importance of the > 'format' command in the layout file. The customization manual > indicates that it refers to version 2 however the book.layout I'm > basing my layout on uses version 4 and try as I might I can't locate > any information about this version. Can some one point me in the right > direction? Or better still tell me it doesn't matter much and I can > stop worrying about it. It does not matter _too_ much. There is not too much documentation for either ;-) Andre'
Re: Exporting to Rich Text Format with latex2rtf, issues and a fix
Wilfried, thanks a lot for your input. This was just a novice hackjob that worked, and my goal (as stated at the end) was to get a solid working solution that could be placed on the LyX wiki. I admit lots of ignorance on all of this. Nonetheless, I figured that since I started this I should try and finish it. So, I began by working on Enrico's suggested solution... but I found out it's all much easier than that. All I did was: (1) uninstall latex2rtf (to remove all my edited files), remove C:\l2r and C:\Program Files\LyX 1.5.2 from my Windows search path, then reconfigure LyX (RTF export disappeared) (2) reinstall latex2rtf to C:\l2r, put C:\l2r on the search path again, start LyX, reconfigure, and restart LyX -> LyX FAILS to find the converter (3) close LyX, restart LyX, reconfigure again, close and restart LyX -> WORKS FINE I did steps 1-3 three times and it works that way every time... the only thing you need to do apparently is reconfigure LyX TWICE after installing latex2rtf and adding the folder to the search path. (I closed and restarted LyX between reconfigurations, but I don't know that that matters). I still think it's simplest to just install latex2rtf to C:\l2r. There may be other complications if you install elsewhere, but I didn't test that. This strikes me as weird. Does LyX do this for other converters... how does configure behave differently between successive calls? Can anyone else try this and see if they repeat it? Anyway, apparently all of my problems with the configuration files (the .bat's) were a waste of time - the second time I reconfigured LyX it worked despite all of that. As Wilfried noted, I think (see below), those files are irrelevant to LyX's use of the converter (latex2rt.exe) and the GUI shell. Remaining question: Enrico, I think that l2rprep.bat is intended to do the same thing you proposed with the new .bat file - set rtfpath. No? Either way, it seems only relevant when the .bat files are being called... and (again, see below) I think Wilfried indicates that they are not when LyX calls latex2rt (.exe). Questions/comments inserted in Wilfried's comments below... > Ideally, one would simply: > > (1) install latex2rtf from sourceforge (win-gui download here - > http://sourceforge.net/project/showfiles.php?group_id=22654) > (2) add the latex2rtf folder (C:\l2r -- see below) to the Windows search > path (see section 2.4 here - > http://sourceforge.net/project/showfiles.php?group_id=22654) > (3) open LyX, reconfigure, close, and restart > > and the converter for Latex (plain) -> Rich Text Format would be sorted out > by LyX and a Rich Text Format option would be made available under File -> > Export. > > Unfortunately, it ain't that easy. Well, as the one who makes the DOS/Win port of latex2rtf, I can explain why it is as is and why some thing work and others not. See below. > First off, the above strategy works fine if all you want to do is use the > latex2rtf GUI (l2rshell.exe; the icon on the desktop calls this) to convert > existing .tex files to .rtf files. In fact, you only need (1) and (2) above > for that, and then you just export plain latex from LyX and run the > conversion manually. Getting LyX to recognize the converter (latex2rt.exe) > is the hard part, but it's nice to have LyX do all the work behind the scenes. > > The first issue is that you should simply avoid installing the program > anywhere but C:\l2r. All of the defaults for the program assume that it is > installed at this path. I installed to Program Files because I had not read > section 2.4 here - > http://sourceforge.net/project/showfiles.php?group_id=22654 - first. It > explains how to adjust the three configuration files (more on these in a > minute) to make latex2rtf work from any installation path, but it never > worked for me, and I tried a lot of different things. No matter what I > tried, running LyX from the command prompt showed that the error was that > latex2rtf could not find its config directory (the cfg directory under the > latex2rtf root directory). It always assumed that the root directory was > C:\l2r despite the fact that all entries in the configuration files were > adjusted to reflect "C:\Program Files\latex2rtf", where I installed it. What do you mean by "configuration files"? Adapting the pathes in the batch files (l2rprep.bat, l2r.bat) only helps if these batch files are executed. If you just call latex2rt.exe, they aren't. The configuration of the GUI shell is used only by the GUI shell. latex2rt.exe itself knows nothing of the GUI shell nor of the batch files. I was referring to the .bat files, without knowing what they really did. My fault. So does this means that LyX doesn't need to know about the .bat files? It looks like all that LyX is doing is calling the latex2rt (.exe file) to get the conversion. Right? > So, > make your life easy and install to C:\l2r. I never checked this with the > latex2rtf
Toolbar font and font size
I'm just back to using Lyx after a long break; the font used in the toolbar has become very small. How can Lyx be configured to use a larger font? Thanks - jon
Re: 2 Bugs
On Oct 25, 2007, at 1:09 PM, Nicolás wrote: Hi! I confirm both bugs with LyX 1.5.2 on Windows (official installer) Recipes here: 1st Bug- Open Latex Preamble window. Write whatever in the preamble. Click with the mouse on themain LyX window. As a result the little window with the document settings goes to second plane. Go back to that window. MAGIC! What you wrote has disappeared. I can confirm this on OS X 2nd Bug- Open a new document. Create an ERT box. Execute Navigate- >Bookmarks->Save bookmark 1. Try to open a new document and LyX crashes. No problem on OS X Nicolás Juergen Spitzmueller wrote: Tobias Krause wrote: @ Juergen: detailded recipe is here: With recipe, I mean: what actions do you exactly perform in order to trigger the crash? I'm unable to reproduce the crash. Most of your console output is unrelated, the related part is this: Assertion triggered in void __thiscall lyx::Text::setCurrentFont (class lyx::Cursor &) by failing check "this == cur.text()" in file D:\LyX\lyx-1.5.2\src\Text2.cpp:757 Which installer did you use? I think assertions should be really disabled in stable releases. Jürgen
Re: layout file format versions
Andre Poenitz <[EMAIL PROTECTED]> writes: > > It does not matter _too_ much. There is not too much documentation for > either > > Andre' > > Thanks Andre' - I'll just assume the format won't be significantly different then.
Re: Exporting to Rich Text Format with latex2rtf, issues and a fix
Dave Hewitt writes: > All I did was: > > (1) uninstall latex2rtf (to remove all my edited files), remove C:\l2r and > C:\Program Files\LyX 1.5.2 from my Windows search path, then reconfigure > LyX (RTF export disappeared) > > (2) reinstall latex2rtf to C:\l2r, put C:\l2r on the search path again, > start LyX, reconfigure, and restart LyX -> LyX FAILS to find the converter If you mean that you added C:\l2r to "PATH prefix" in LyX preferences and then reconfigured, then this is explained by the fact that changes to "PATH prefix" are only taken after you save preferences and close and restart LyX. > (3) close LyX, restart LyX, reconfigure again, close and restart LyX -> > WORKS FINE Yes, because now the previously set "PATH prefix" is taken into account. > I did steps 1-3 three times and it works that way every time... the only > thing you need to do apparently is reconfigure LyX TWICE after installing > latex2rtf and adding the folder to the search path. No, you need to close and restart LyX after adding the folder to "PATH prefix". Otherwise, the "PATH prefix" as set at LyX start is still used, no matter that you changed it. > (I closed and restarted > LyX between reconfigurations, but I don't know that that matters). I still > think it's simplest to just install latex2rtf to C:\l2r. There may be other > complications if you install elsewhere, but I didn't test that. If you install to C:\l2r, you only need to add C:\l2r to "PATH prefix". If you install latex2rtf somewhere else, you have to specify where its config directory is. There are no other complications. > Enrico, I think that l2rprep.bat is intended to do the same thing you > proposed with the new .bat file - set rtfpath. No? Either way, it seems > only relevant when the .bat files are being called... and (again, see > below) I think Wilfried indicates that they are not when LyX calls latex2rt > (.exe). l2rprep.bat simply sets up the correct environment for latex2rtf but does not launch latex2rtf itself. You don't need it, as you already have the correct environment set when using LyX, except for RTFPATH if you don't install to C:\l2r. Note that you could also specify the config directory through a command line option. Suppose that you installed latex2rtf to "C:\Program Files\latex2rtf", then you could simply use something like: latex2rt -P "C:/Program Files/latex2rtf/cfg" -p -S -o file.rtf file.tex but the -P option is broken and doesn't work. I think that it is due to the fact that a path which does not begin with / is not recognized as being absolute and is thus refused. However, if your current drive is C:, you can omit it and use instead: latex2rt -P "/Program Files/latex2rtf/cfg" -p -S -o file.rtf file.tex This works, try it. So, you could install to "C:\Program Files\latex2rtf" and then 1) add "C:\Program Files\latex2rtf" to PATH prefix 2) add -P "/Program Files/latex2rtf/cfg" to the latex2rtf converter entry in the LyX preferences or use a .bat file for setting RTFPATH and launching latex2rt, as I outlined in an other post. All in all, installing latex2rtf to C:\l2r maybe the best option. -- Enrico
