Re: Strange behavior LyxWin qt 1.3.5 - possibly relating to Bibtex - solved: bug in babel.def and correction
Piet van Ostrum has solved the problem. It is due to a bug in babel.def. See the thread *babel + fancyhdr + natbib = ! Extra \else *in the comp.text.tex group. He suggests the following correction: In babel.def replace the three occurrences of \noexpand\bbl(at)restore(at)actives with \protect\bbl(at)restore(at)actives with (at) to be replaced by the atcharacter. I tried this over several weeks. It works just fine. I suggest that you try this if Latex complains about an extra \else. Ekkehart
Re: Strange behavior LyxWin qt 1.3.5 - possibly relating to Bibtex - solved: bug in babel.def and correction
Piet van Ostrum has solved the problem. It is due to a bug in babel.def. See the thread *babel + fancyhdr + natbib = ! Extra \else *in the comp.text.tex group. He suggests the following correction: In babel.def replace the three occurrences of \noexpand\bbl(at)restore(at)actives with \protect\bbl(at)restore(at)actives with (at) to be replaced by the atcharacter. I tried this over several weeks. It works just fine. I suggest that you try this if Latex complains about an extra \else. Ekkehart
Re: Strange behavior LyxWin qt 1.3.5 - possibly relating to Bibtex - solved: bug in babel.def and correction
Piet van Ostrum has solved the problem. It is due to a bug in babel.def. See the thread *babel + fancyhdr + natbib = ! Extra \else *in the comp.text.tex group. He suggests the following correction: In babel.def replace the three occurrences of \noexpand\bbl(at)restore(at)actives with \protect\bbl(at)restore(at)actives with (at) to be replaced by the "at"character. I tried this over several weeks. It works just fine. I suggest that you try this if Latex complains about an extra \else. Ekkehart
Re: Strange behavior LyxWin qt 1.3.5 - possibly relating to Bibtex
Matej wrote:
Could you please some description of the solution here,
please, so that it could be found in archives?
Mike noted that, with babel+fancyhdr+natbib
the problem occurs in large documents with
\renewcommand{\chaptermark}[1]{\markboth{#1}{}}
\renewcommand{\sectionmark}[1]{\markright{#1}}
\fancyhead[CE]{\MakeUppercase\leftmark}
\fancyhead[CO]{\MakeUppercase\rightmark}
and seems to be due to the \MakeUppercase command. If you
move this to the marking commands like
\renewcommand{\chaptermark}[1]{\markboth{\MakeUppercase{#1}}{}}
\renewcommand{\sectionmark}[1]{\markright{\MakeUppercase{#1}}}
\fancyhead[CE]{\leftmark}
\fancyhead[CO]{\rightmark}
the problem does not occur. The reason remains opaque.
Ekkehart
Re: Strange behavior LyxWin qt 1.3.5 - possibly relating to Bibtex
Matej wrote:
Could you please some description of the solution here,
please, so that it could be found in archives?
Mike noted that, with babel+fancyhdr+natbib
the problem occurs in large documents with
\renewcommand{\chaptermark}[1]{\markboth{#1}{}}
\renewcommand{\sectionmark}[1]{\markright{#1}}
\fancyhead[CE]{\MakeUppercase\leftmark}
\fancyhead[CO]{\MakeUppercase\rightmark}
and seems to be due to the \MakeUppercase command. If you
move this to the marking commands like
\renewcommand{\chaptermark}[1]{\markboth{\MakeUppercase{#1}}{}}
\renewcommand{\sectionmark}[1]{\markright{\MakeUppercase{#1}}}
\fancyhead[CE]{\leftmark}
\fancyhead[CO]{\rightmark}
the problem does not occur. The reason remains opaque.
Ekkehart
Re: Strange behavior LyxWin qt 1.3.5 - possibly relating to Bibtex
Matej wrote:
Could you please some description of the solution here,
please, so that it could be found in archives?
Mike noted that, with babel+fancyhdr+natbib
the problem occurs in large documents with
\renewcommand{\chaptermark}[1]{\markboth{#1}{}}
\renewcommand{\sectionmark}[1]{\markright{#1}}
\fancyhead[CE]{\MakeUppercase\leftmark}
\fancyhead[CO]{\MakeUppercase\rightmark}
and seems to be due to the \MakeUppercase command. If you
move this to the marking commands like
\renewcommand{\chaptermark}[1]{\markboth{\MakeUppercase{#1}}{}}
\renewcommand{\sectionmark}[1]{\markright{\MakeUppercase{#1}}}
\fancyhead[CE]{\leftmark}
\fancyhead[CO]{\rightmark}
the problem does not occur. The reason remains opaque.
Ekkehart
Re: Strange behavior LyxWin qt 1.3.5 - possibly relating to Bibtex
Ekkehart Schlicht wrote: Mike Shell has identified the problem -- it is not a LyX problem, nor is it related to hyperref (as I thought) but a bug relating to the combination babel+fancyhdr+natbib. See Could you please some description of the solution here, please, so that it could be found in archives? Thanks, Matej -- Matej Cepl, http://www.ceplovi.cz/matej GPG Finger: 89EF 4BC6 288A BF43 1BAB 25C3 E09F EF25 D964 84AC 138 Highland Ave. #10, Somerville, Ma 02143, (617) 623-1488 The ratio of literacy to illiteracy is a constant, but nowadays the illiterates can read. -- Alberto Moravia
Re: Strange behavior LyxWin qt 1.3.5 - possibly relating to Bibtex
Ekkehart Schlicht wrote: Mike Shell has identified the problem -- it is not a LyX problem, nor is it related to hyperref (as I thought) but a bug relating to the combination babel+fancyhdr+natbib. See Could you please some description of the solution here, please, so that it could be found in archives? Thanks, Matej -- Matej Cepl, http://www.ceplovi.cz/matej GPG Finger: 89EF 4BC6 288A BF43 1BAB 25C3 E09F EF25 D964 84AC 138 Highland Ave. #10, Somerville, Ma 02143, (617) 623-1488 The ratio of literacy to illiteracy is a constant, but nowadays the illiterates can read. -- Alberto Moravia
Re: Strange behavior LyxWin qt 1.3.5 - possibly relating to Bibtex
Ekkehart Schlicht wrote: > Mike Shell has identified the problem -- it is not a > LyX problem, nor is it related to hyperref (as I > thought) but a bug relating to the combination > babel+fancyhdr+natbib. See Could you please some description of the solution here, please, so that it could be found in archives? Thanks, Matej -- Matej Cepl, http://www.ceplovi.cz/matej GPG Finger: 89EF 4BC6 288A BF43 1BAB 25C3 E09F EF25 D964 84AC 138 Highland Ave. #10, Somerville, Ma 02143, (617) 623-1488 The ratio of literacy to illiteracy is a constant, but nowadays the illiterates can read. -- Alberto Moravia
Re: Strange behavior LyxWin qt 1.3.5 - possibly relating to Bibtex
Mike Shell has identified the problem -- it is not a LyX problem, nor is it related to hyperref (as I thought) but a bug relating to the combination babel+fancyhdr+natbib. See http://groups.google.de/group/comp.text.tex/browse_frm/thread/d9bb4d8e289ef353/[EMAIL PROTECTED]rnum=1hl=de#77ad3282f3f8578c He suggests an easy workaround seems to eliminate the problem completely (id did so in my case). Cheers Ekkehart
Re: Strange behavior LyxWin qt 1.3.5 - possibly relating to Bibtex
Mike Shell has identified the problem -- it is not a LyX problem, nor is it related to hyperref (as I thought) but a bug relating to the combination babel+fancyhdr+natbib. See http://groups.google.de/group/comp.text.tex/browse_frm/thread/d9bb4d8e289ef353/[EMAIL PROTECTED]rnum=1hl=de#77ad3282f3f8578c He suggests an easy workaround seems to eliminate the problem completely (id did so in my case). Cheers Ekkehart
Re: Strange behavior LyxWin qt 1.3.5 - possibly relating to Bibtex
Mike Shell has identified the problem -- it is not a LyX problem, nor is it related to hyperref (as I thought) but a bug relating to the combination babel+fancyhdr+natbib. See http://groups.google.de/group/comp.text.tex/browse_frm/thread/d9bb4d8e289ef353/[EMAIL PROTECTED]=1=de#77ad3282f3f8578c He suggests an easy workaround seems to eliminate the problem completely (id did so in my case). Cheers Ekkehart
Re: Strange behavior LyxWin qt 1.3.5 - possibly relating to Bibtex
The problem disappears if I omit the option pagebackref=true in the hyperref praeamble. With the option, the error message occurs, but a pdf is produced in the lyx\temp folder. It can be viewed by defining the new format (Edit- Preferences-File Formats-New) with Format:pdf4 GUI name: PDF (view) Extension: pdf Viewer:pdfviewer and definining the new viewer by placing a file named pdfviewer.cmd containing kill -c AdobeAcrobat del viewer.pdf copy %~dpn1.pdf %~dp1\viewer.pdf START /max AcroRd32.exe %~dp1\viewer.pdf exit into the lyx\bin directory. The first line in pdfviewer.cmd uses the kill utility from http://21st-century.net/Pub/WINNT/Utilities/kill.zip to kill any existing Acrobat window. It can be omitted, but in this case all Acrobat windows must be closed manually before invoking the lyx command buffer-view pdf4 from the mini-buffer or from the toolbar (if placed on the toolbar by adding Icon buffer-view pdf4 under the toolbar heading in the .ui file). HTH - in (unlikely but annoying) case that somebody runs into a similar problem as I did. Ekkehart
Re: Strange behavior LyxWin qt 1.3.5 - possibly relating to Bibtex
The problem disappears if I omit the option pagebackref=true in the hyperref praeamble. With the option, the error message occurs, but a pdf is produced in the lyx\temp folder. It can be viewed by defining the new format (Edit- Preferences-File Formats-New) with Format:pdf4 GUI name: PDF (view) Extension: pdf Viewer:pdfviewer and definining the new viewer by placing a file named pdfviewer.cmd containing kill -c AdobeAcrobat del viewer.pdf copy %~dpn1.pdf %~dp1\viewer.pdf START /max AcroRd32.exe %~dp1\viewer.pdf exit into the lyx\bin directory. The first line in pdfviewer.cmd uses the kill utility from http://21st-century.net/Pub/WINNT/Utilities/kill.zip to kill any existing Acrobat window. It can be omitted, but in this case all Acrobat windows must be closed manually before invoking the lyx command buffer-view pdf4 from the mini-buffer or from the toolbar (if placed on the toolbar by adding Icon buffer-view pdf4 under the toolbar heading in the .ui file). HTH - in (unlikely but annoying) case that somebody runs into a similar problem as I did. Ekkehart
Re: Strange behavior LyxWin qt 1.3.5 - possibly relating to Bibtex
The problem disappears if I omit the option pagebackref=true in the hyperref praeamble. With the option, the error message occurs, but a pdf is produced in the lyx\temp folder. It can be viewed by defining the new format (Edit-> Preferences->File Formats->New) with Format:pdf4 GUI name: PDF (view) Extension: pdf Viewer:pdfviewer and definining the new viewer by placing a file named pdfviewer.cmd containing kill -c AdobeAcrobat del viewer.pdf copy %~dpn1.pdf %~dp1\viewer.pdf START /max AcroRd32.exe %~dp1\viewer.pdf exit into the lyx\bin directory. The first line in pdfviewer.cmd uses the kill utility from http://21st-century.net/Pub/WINNT/Utilities/kill.zip to kill any existing Acrobat window. It can be omitted, but in this case all Acrobat windows must be closed manually before invoking the lyx command buffer-view pdf4 from the mini-buffer or from the toolbar (if placed on the toolbar by adding Icon "buffer-view pdf4" under the toolbar heading in the .ui file). HTH - in (unlikely but annoying) case that somebody runs into a similar problem as I did. Ekkehart
Re: Strange behavior LyxWin qt 1.3.5 - possibly relating to Bibtex - simple work-around
It seems that the problem vanishes and re-appears while I am expanding the manuscript. So I am not bothering any more but use the following simple work- around: I have added Icon buffer-export latex in the user interface file. This gives me a button to export latex into my working directory with a mouse click. When I work with the lyx file, I push the button. I open the tex file in the working directory with my latex editor (I use texcntr.exe). From here I can compile and view the pdf. and do all checking and viewing there. I do all corrections in the Lyx file and export to latex again. The editor reminds me that the tex file has been changed outside the editor and prompts me to reload it, etc. Maybe somebody gets into the same mess and then may find this helpful. Ekkehart
Re: Strange behavior LyxWin qt 1.3.5 - possibly relating to Bibtex - simple work-around
It seems that the problem vanishes and re-appears while I am expanding the manuscript. So I am not bothering any more but use the following simple work- around: I have added Icon buffer-export latex in the user interface file. This gives me a button to export latex into my working directory with a mouse click. When I work with the lyx file, I push the button. I open the tex file in the working directory with my latex editor (I use texcntr.exe). From here I can compile and view the pdf. and do all checking and viewing there. I do all corrections in the Lyx file and export to latex again. The editor reminds me that the tex file has been changed outside the editor and prompts me to reload it, etc. Maybe somebody gets into the same mess and then may find this helpful. Ekkehart
Re: Strange behavior LyxWin qt 1.3.5 - possibly relating to Bibtex - simple work-around
It seems that the problem vanishes and re-appears while I am expanding the manuscript. So I am not bothering any more but use the following simple work- around: I have added Icon "buffer-export latex" in the user interface file. This gives me a button to export latex into my working directory with a mouse click. When I work with the lyx file, I push the button. I open the tex file in the working directory with my latex editor (I use texcntr.exe). From here I can compile and view the pdf. and do all checking and viewing there. I do all corrections in the Lyx file and export to latex again. The editor reminds me that the tex file has been changed outside the editor and prompts me to reload it, etc. Maybe somebody gets into the same mess and then may find this helpful. Ekkehart
Re: Strange behavior LyxWin qt 1.3.5 - possibly relating to Bibtex
Paul: Thank you for taking so much trouble, but it is good to know that the error can be reproduced and seems unrelated to Lyx. I experimented myself in similar ways. In view of what you report and what I tried, I came up with the conclusion that the error appears somewhat unsystematic. I used also other standard bib style files, with the result that the error is unsystematic and disappears if I use numerical instead of author-year. (I threw out those things you mention and others as well.) My conclusion is that this is a BibTeX issue, unrelated to Lyx. I noted that the LaTeX compilation generates the error messages that induce LyX to stop. I noticed also that sometimes pdftex generates a valid PDF file in the Lyx temp directory, although Lyx reports an error and the PDF cannot be viewed from inside Lyx. From this I would draw the conclusion that it would be nice to have a possibility to run Windows commands or shell commands from inside Lyx. Maybe this is possible, maybe by writing a fake conversion script. I shall try to find out. This would make it possible to write a batch file that exports to LaTeX and then runs pdftex several times more than the LyX standard would do, and another script to view the PDF in the temp directory. Thank you again for extensive check you did. If I find out something, I shall post it on this thread, but at the moment I go on and compile outside LyX. Kind regards Ekkehart
Re: Strange behavior LyxWin qt 1.3.5 - possibly relating to Bibtex
Paul: Thank you for taking so much trouble, but it is good to know that the error can be reproduced and seems unrelated to Lyx. I experimented myself in similar ways. In view of what you report and what I tried, I came up with the conclusion that the error appears somewhat unsystematic. I used also other standard bib style files, with the result that the error is unsystematic and disappears if I use numerical instead of author-year. (I threw out those things you mention and others as well.) My conclusion is that this is a BibTeX issue, unrelated to Lyx. I noted that the LaTeX compilation generates the error messages that induce LyX to stop. I noticed also that sometimes pdftex generates a valid PDF file in the Lyx temp directory, although Lyx reports an error and the PDF cannot be viewed from inside Lyx. From this I would draw the conclusion that it would be nice to have a possibility to run Windows commands or shell commands from inside Lyx. Maybe this is possible, maybe by writing a fake conversion script. I shall try to find out. This would make it possible to write a batch file that exports to LaTeX and then runs pdftex several times more than the LyX standard would do, and another script to view the PDF in the temp directory. Thank you again for extensive check you did. If I find out something, I shall post it on this thread, but at the moment I go on and compile outside LyX. Kind regards Ekkehart
Re: Strange behavior LyxWin qt 1.3.5 - possibly relating to Bibtex
Paul: Thank you for taking so much trouble, but it is good to know that the error can be reproduced and seems unrelated to Lyx. I experimented myself in similar ways. In view of what you report and what I tried, I came up with the conclusion that the error appears somewhat unsystematic. I used also other standard bib style files, with the result that the error is unsystematic and disappears if I use numerical instead of author-year. (I threw out those things you mention and others as well.) My conclusion is that this is a BibTeX issue, unrelated to Lyx. I noted that the LaTeX compilation generates the error messages that induce LyX to stop. I noticed also that sometimes pdftex generates a valid PDF file in the Lyx temp directory, although Lyx reports an error and the PDF cannot be viewed from inside Lyx. From this I would draw the conclusion that it would be nice to have a possibility to run Windows commands or shell commands from inside Lyx. Maybe this is possible, maybe by writing a "fake" conversion script. I shall try to find out. This would make it possible to write a batch file that exports to LaTeX and then runs pdftex several times more than the LyX standard would do, and another script to view the PDF in the temp directory. Thank you again for extensive check you did. If I find out something, I shall post it on this thread, but at the moment I go on and compile outside LyX. Kind regards Ekkehart
Re: Strange behavior LyxWin qt 1.3.5 - possibly relating to Bibtex
Ekkehart Schlicht wrote:
Hi,
If I want to view the Lyx file I am working at with pdflatex,
I always get the message
3 errors detected.
You should try to fix them.
The error messages are
1. LaTeX Error: Something's wrong--perhaps a missing \item.
2. and 3. Extra \else. I'm ignoring this; it doesn't match any \if.
If I omit the bibliography, compilation works fine.
If I export the file as Latex and compile with pdflatex
(4 times), I get the desired output. If I open the lyx file
in Lyx, I can compile nicely as well. It seems to me that
may not use enought runs and does not produce some
auxiliary files that are needed. Is this a bug, or something wrong?
(I am pretty sure that the files as such are o.k. If I split the
lyx file into pieces, each piece can be compiled separately.)
If somebody has an idea, I would appreciate help.
I have put the files on a server:
http://home.arcor.de/ekkehart.schlicht/ekkehart/lyx/
in case somebody is kind enough to have a look.
Thanks
Ekkehart
I agree it's strange, to the point of being beyond my abilities. I'll
post what I discovered here, in case someone smarter can finish the job.
Disclaimers: I had to modify two \newfont commands in your preamble to
get LaTeX to find the fonts on my system. I'm pretty sure this has no
impact on the problem. Also, my system is monolingual (English), which
may bear on things.
I encountered the same problem you did trying to View-DVI from within
LyX, but when I exported to a LaTeX file and tried to compile it outside
LyX, I encountered the same error messages. In my experience, this type
of error is often caused by a defect in the .bib file, so that is where
I concentrated.
There are what I believe to be some errors in your .bib file. Some are
harmless (I think I recall a closing apostrophe (') without a matching
opening one, for instance). Two of your own citations include your
e-mail address. I escaped the '@' sign (to '\@') to be safe; I was not
sure if BiBTeX would try to interpret the '@' as the start of a record.
Also, in a couple of places you connected two authors with 'und'
rather than 'and'. On my system, that caused problems, so I changed the
conjunction to 'and'.
With that done, I discovered the following:
1. The failure occurs at the top of page 72, which is near the end of
the bibliography (page 71 ends with the Nelson citation).
2. If you omit the Polyani citation (which would be the first on page
72), the document compiles (assuming you change 'und' to 'and' as above
-- otherwise, at least on my system, the Richter citation causes the
problem to reappear).
3. If you change the author name in the Polyani citation to 'Rolyani',
so that it appears second on page 72 (after Richter rather than before),
the document compiles. So the .bib entry itself would not appear to be
defective.
4. Putting Polyani after Nelson and putting something other than
Richter after Polyani does not seem to help.
Perhaps there is a spacing problem, either with Polyani following Nelson
or with Polyani coming at the top of a page. As I said, this exceeds my
understanding of LaTeX; but I do not believe it is a LyX problem.
-- Paul
Re: Strange behavior LyxWin qt 1.3.5 - possibly relating to Bibtex
Ekkehart Schlicht wrote:
Hi,
If I want to view the Lyx file I am working at with pdflatex,
I always get the message
3 errors detected.
You should try to fix them.
The error messages are
1. LaTeX Error: Something's wrong--perhaps a missing \item.
2. and 3. Extra \else. I'm ignoring this; it doesn't match any \if.
If I omit the bibliography, compilation works fine.
If I export the file as Latex and compile with pdflatex
(4 times), I get the desired output. If I open the lyx file
in Lyx, I can compile nicely as well. It seems to me that
may not use enought runs and does not produce some
auxiliary files that are needed. Is this a bug, or something wrong?
(I am pretty sure that the files as such are o.k. If I split the
lyx file into pieces, each piece can be compiled separately.)
If somebody has an idea, I would appreciate help.
I have put the files on a server:
http://home.arcor.de/ekkehart.schlicht/ekkehart/lyx/
in case somebody is kind enough to have a look.
Thanks
Ekkehart
I agree it's strange, to the point of being beyond my abilities. I'll
post what I discovered here, in case someone smarter can finish the job.
Disclaimers: I had to modify two \newfont commands in your preamble to
get LaTeX to find the fonts on my system. I'm pretty sure this has no
impact on the problem. Also, my system is monolingual (English), which
may bear on things.
I encountered the same problem you did trying to View-DVI from within
LyX, but when I exported to a LaTeX file and tried to compile it outside
LyX, I encountered the same error messages. In my experience, this type
of error is often caused by a defect in the .bib file, so that is where
I concentrated.
There are what I believe to be some errors in your .bib file. Some are
harmless (I think I recall a closing apostrophe (') without a matching
opening one, for instance). Two of your own citations include your
e-mail address. I escaped the '@' sign (to '\@') to be safe; I was not
sure if BiBTeX would try to interpret the '@' as the start of a record.
Also, in a couple of places you connected two authors with 'und'
rather than 'and'. On my system, that caused problems, so I changed the
conjunction to 'and'.
With that done, I discovered the following:
1. The failure occurs at the top of page 72, which is near the end of
the bibliography (page 71 ends with the Nelson citation).
2. If you omit the Polyani citation (which would be the first on page
72), the document compiles (assuming you change 'und' to 'and' as above
-- otherwise, at least on my system, the Richter citation causes the
problem to reappear).
3. If you change the author name in the Polyani citation to 'Rolyani',
so that it appears second on page 72 (after Richter rather than before),
the document compiles. So the .bib entry itself would not appear to be
defective.
4. Putting Polyani after Nelson and putting something other than
Richter after Polyani does not seem to help.
Perhaps there is a spacing problem, either with Polyani following Nelson
or with Polyani coming at the top of a page. As I said, this exceeds my
understanding of LaTeX; but I do not believe it is a LyX problem.
-- Paul
Re: Strange behavior LyxWin qt 1.3.5 - possibly relating to Bibtex
Ekkehart Schlicht wrote:
Hi,
If I want to view the Lyx file I am working at with pdflatex,
I always get the message
3 errors detected.
You should try to fix them.
The error messages are
1. LaTeX Error: Something's wrong--perhaps a missing \item.
2. and 3. Extra \else. I'm ignoring this; it doesn't match any \if.
If I omit the bibliography, compilation works fine.
If I export the file as Latex and compile with pdflatex
(4 times), I get the desired output. If I open the lyx file
in Lyx, I can compile nicely as well. It seems to me that
may not use enought runs and does not produce some
auxiliary files that are needed. Is this a bug, or something wrong?
(I am pretty sure that the files as such are o.k. If I split the
lyx file into pieces, each piece can be compiled separately.)
If somebody has an idea, I would appreciate help.
I have put the files on a server:
http://home.arcor.de/ekkehart.schlicht/ekkehart/lyx/
in case somebody is kind enough to have a look.
Thanks
Ekkehart
I agree it's strange, to the point of being beyond my abilities. I'll
post what I discovered here, in case someone smarter can finish the job.
Disclaimers: I had to modify two \newfont commands in your preamble to
get LaTeX to find the fonts on my system. I'm pretty sure this has no
impact on the problem. Also, my system is monolingual (English), which
may bear on things.
I encountered the same problem you did trying to View->DVI from within
LyX, but when I exported to a LaTeX file and tried to compile it outside
LyX, I encountered the same error messages. In my experience, this type
of error is often caused by a defect in the .bib file, so that is where
I concentrated.
There are what I believe to be some errors in your .bib file. Some are
harmless (I think I recall a closing apostrophe (') without a matching
opening one, for instance). Two of your own citations include your
e-mail address. I escaped the '@' sign (to '\@') to be safe; I was not
sure if BiBTeX would try to interpret the '@' as the start of a record.
Also, in a couple of places you connected two authors with 'und'
rather than 'and'. On my system, that caused problems, so I changed the
conjunction to 'and'.
With that done, I discovered the following:
1. The failure occurs at the top of page 72, which is near the end of
the bibliography (page 71 ends with the Nelson citation).
2. If you omit the Polyani citation (which would be the first on page
72), the document compiles (assuming you change 'und' to 'and' as above
-- otherwise, at least on my system, the Richter citation causes the
problem to reappear).
3. If you change the author name in the Polyani citation to 'Rolyani',
so that it appears second on page 72 (after Richter rather than before),
the document compiles. So the .bib entry itself would not appear to be
defective.
4. Putting Polyani after Nelson and putting something other than
Richter after Polyani does not seem to help.
Perhaps there is a spacing problem, either with Polyani following Nelson
or with Polyani coming at the top of a page. As I said, this exceeds my
understanding of LaTeX; but I do not believe it is a LyX problem.
-- Paul
Re: Strange behavior LyxWin qt 1.3.5 - possibly relating to Bibtex - addendum
Ekkehart Schlicht wrote: If I export the file as Latex and compile with pdflatex (4 times), I get the desired output. If I open the lyx file in Lyx, after having done the latex compilation I can compile nicely as well. Ekkehart
Re: Strange behavior LyxWin qt 1.3.5 - possibly relating to Bibtex - addendum
Ekkehart Schlicht wrote: If I export the file as Latex and compile with pdflatex (4 times), I get the desired output. If I open the lyx file in Lyx, after having done the latex compilation I can compile nicely as well. Ekkehart
Re: Strange behavior LyxWin qt 1.3.5 - possibly relating to Bibtex - addendum
Ekkehart Schlicht wrote: If I export the file as Latex and compile with pdflatex (4 times), I get the desired output. If I open the lyx file in Lyx, after having done the latex compilation I can compile nicely as well. Ekkehart
