Hi Liviu, Thanks for the thoughts.
> This can happen when you re-define an inset. For example: > - define an inset "inset 1" and make a document containing this inset - re-define the inset to "inset 2" > - open the original document containing "inset 1" constructs. At this point LyX will label the insets in red and as undefined (if you don't see this try to toggle the inset label in LyX). And compilation would fail. Upon your prompting, I've gone through with a text editor and made sure that all of the redefined insets point at the new name. (There was one or two, but other than those, the document was clean.) I also checked to make sure that the document class and lyx .layout files were encoded correctly and ended with a Line Feed rather than the Mac OS X classic way of terminating a file. (I ran into problems with this earlier in the week.) > Try to check in the LyX source the exact name of the inset and make sure it coincides with the one you have in your config files. (Never forget to redundantly reconfigure LyX.) Else, check the LaTeX code to make sure that the proper code is being inserted by your inset. I also went back and reconfigured LyX. I'm having the same problem. Moreover, LyX is doing strange things with parts of the text. For reasons I don't understand, it's having issues with perfectly normal ASCII characters. Because I've been having so many problems, I decided to move over to Windows. I am not able to reproduce the bugs. The files compile without errors. (Though strangely enough, I'm no longer able to enable XeTeX through the font pane of Document Settings.) When I have some time tomorrow, I'll update the SVN version and see if I can get the document to compile correctly. For right now, I've got to get back to writing. (Other than a platform problem, I wonder if the problems might be due to a recent commit. The SVN version I have on the PC hasn't been updated for about a week and a half.) Cheers, Rob
