Georg Baum schrieb:
Am Montag, 27. November 2006 16:46 schrieb Michael Gerz:
Hi,
when loading a perfectly valid LyX 1.3 document with a freshly built
LyX/Win, I get lots of error messages:
Error returned from iconv
EILSEQ An invalid multibyte sequence has been encountered in the input.
When converting from UTF-8 to UCS-4LE.
Input: 0x63 0x3a 0x2f 0x44 0x6f 0x6b 0x75 0x6d 0x65 0x6e 0x74 0x65 0x20
0x75 0x6e 0x64 0x20 0x45 0x69 0x6e 0x7
3 0x74 0x65 0x6c 0x6c 0x75 0x6e 0x67 0x65 0x6e 0x2f 0x6d 0x73 0x2f 0x45
0x69 0x67 0x65 0x6e 0x65 0x20 0x44 0x6
1 0x74 0x65 0x69 0x65 0x6e 0x2f 0x50 0x75 0x62 0x6c 0x69 0x6b 0x61 0x74
0x69 0x6f 0x6e 0x65 0x6e 0x2f 0x56 0x6
5 0x72 0xfffffff6 0x66 0x66 0x65 0x6e 0x74 0x6c 0x69 0x63 0x68 0x75 0x6e
0x67 0x65 0x6e 0x2f 0x43 0x43 0x52 0x
54 0x53 0x20 0x32 0x30 0x30 0x36 0x2f 0x4f 0x4f 0x2d 0x58 0x4d 0x4c 0x2d
0x53 0x63 0x68 0x65 0x6d 0x61 0x2e 0x
6c 0x79 0x78
(At a first glance, I think that the document itself looks fine.)
Can you please look at the file that is generated by lyx2lyx with a text
editor and determine the encoding? Then we know whether we have to search
a bug in lyx2lyx (or a crippled python installation), or in LyX.
Georg,
I checked again. The problem is not with the document content but with
the document name.
On Windows, a file name like
C:\Dokumente und Einstellungen\Michael\Eigene
Dateien\Veröffentlichungen\MyDoc.lyx
causes the above problem. ATM, you cannot not open such a file at all
using the "Open..." (=> an empty doc is shown). Instead, you have to run
lyx.exe "C:\Dok....."
from the command line. The message above is printed afterwards because
the (truncated) file name is shown in the "View..." menu.
I don't know what cause the problem - the colon, the backslash, the
space, or the German Umlaut. Do you have any idea?
Michael
