On Feb 17, 2012, at 9:36 AM, Eric Weir wrote: > On Feb 16, 2012, at 7:47 PM, stefano franchi wrote: > >> try this workaround to the workaround. Instead of creating a new >> converter, simply go to the existing LAtex(plain-->lyx converter, look >> at the command string (the tex2lyx etc.) and stick a "-e UTF8" before >> the -f switch. Then click "modify" and then click "apply". > > > It worked! Thanks!
Well, yesterday it worked. This morning it's not. I've tried it a couple times. I've verified that the latex(plain) converter has "-e UTF8" in it. [This is the exact code in the converter: $$s/../MacOS/tex2lyx -e UTF8 -f $$i $$o] I've tried it in the terminal, too. This was the command: /Applications/LyX.app/Contents/MacOS/tex2lyx -e UTF8 ~/documents/a/evaluation/avoidable-losses/version-viii/lyxified/revision-of-evaluation-of-the-qualitative-analysis.tex Same result. After both types of imports I get the following message: "Could not find LaTeX command for character''(code point 0x2028) Some characters of your document are probably not representable in the chosen encoding. Changing the document encoding to utf8 could help." I've verified that Scrivener uses Unicode UTF8. Perhaps you or someone one the list will know what the offending character is? Thanks, ------------------------------------------------------------------------------------------ Eric Weir Decatur, GA eew...@bellsouth.net "What is man without the beasts? If all the beasts were gone, men would die from a great loneliness of spirit." - Chief Seattle
