Joost Verburg wrote: > > What file? unicodesymbols? > > Right, it's generating the TOC but the error indeed refers to > unicodesymbols. Is this a known bug?
Yes. This bug occured with the integration of lyx_1_6.py into 1.5.7, because that file needs to access the unicodesymbols file, and lyx2lyx is used by doc_toc.py. Actually, I thought to have fixed that before tagging 1.5.7: http://www.lyx.org/trac/changeset/27399 Modified: lyx-devel/branches/BRANCH_1_5_X/lib/lyx2lyx/lyx_1_6.py URL: http://www.lyx.org/trac/file/lyx- devel/branches/BRANCH_1_5_X/lib/lyx2lyx/lyx_1_6.py?rev=27399 ============================================================================== --- lyx-devel/branches/BRANCH_1_5_X/lib/lyx2lyx/lyx_1_6.py (original) +++ lyx-devel/branches/BRANCH_1_5_X/lib/lyx2lyx/lyx_1_6.py Wed Nov 12 13:55:25 2008 @@ -130,7 +130,10 @@ def read_unicodesymbols(): " Read the unicodesymbols list of unicode characters and corresponding commands." pathname = os.path.abspath(os.path.dirname(sys.argv[0])) - fp = open(os.path.join(pathname.strip('lyx2lyx'), 'unicodesymbols')) + pathname = pathname.rstrip('lyx2lyx') + # from within doc_toc.py, we are in lib/doc + pathname = pathname.rstrip('doc') + fp = open(os.path.join(pathname, 'unicodesymbols')) Here I've added code to lyx_1_6.py that goes from lib/doc to lib/, where the unicodesymbols file resides. This obviously fails on your system. Since it's only for generating the TOC files, you might try to just put a copy (or symlink) to that directory. In 1.6.x, we do not have the problem, because we do not generate TOC files anymore. Jürgen
