On Feb 19, 2012, at 1:36 PM, stefano franchi wrote: > I am forwarding to the users' list. This problem starts to exceed my > lyx/Latex skills. What I can say is this: > > If I: > > 1. Import your file with the modified latex converter > > 2. Change fonts to non-latex > > 3. Select full-coverage unicode fonts like TeX Gyre Termes/Heros > > 4. Compile with xelatex > > Everything goes well. > > HOWEVER, the order of the 1-4 operations is crucial on my setup. If, > for instance, I import and then try to compile first (step 4), I get > the error you mention. After that, there is no way to get the file to > compile even after switching to non-latex fonts and selecting > appropriate fonts. I have to close the file and reimport it. > So: > > 1-2-3-4 works > 1-4-2-3-4 fails permanently > 1-2-4-3-4 fails permanently as well > > Closing the file after failure and trying again with the correct > sequence works. This may a lyx bug, I suspect. > > More skillful people may provide a deeper answer.
Thanks for the problem-solving help again, Stefano. This worked. I had to guess in selecting fonts, as I have no idea what #3 amounts to. When I selected Palatino for serif, it went through. Thanks so much. I would appreciate help from anyone in identifying the offending character[s] so I don't have to jump through all these hoops every time I export from Scrivener/import to Lyx/compile. I don't know if Scrivener is source of the problem, if it's something I'm doing in the way I format in Scrivener--in one section of the paper I inserted a long-ish line centered on the page to mark a break between subsections of a section that I did not want to mark with subheadings--or if it's a problem with LyX. For now I'm grateful that Stefano has rescued me once again. Sincerely, ------------------------------------------------------------------------------------------ Eric Weir Decatur, GA [email protected] "What does it mean...that the world is so beautiful?" - Mary Oliver
