Paul Schwartz wrote:
Sorry, I am still under 1.5.1 and I do not know if it has been corrected
with 1.5.2 or 1.5.3.
After scanning then getting through OCR and saving either using Word pad or
Note pad being sure that under word pad it is saved under unicode UTF-8 Then
importing into a LyX document I got the following window alarm :
Quote
LyX : Reading not UTF-8 encoded file
The file is not UTF-8 encoded.
It will be read as a local 8 bit-encoded. If this does not give the correct
result then please change the encoding of the file to UTF-8 with a program
other than LyX.
Unquote
I recoded again with Word pad without success getting the same alarm.
However, when closing the alarm window, the text is properly imported.
Because with the former LyX versions, I never got this problem, I suppose
that I might be a false alarm ?
Any clue ?
Thanks
Paul
I had a file once that Notepad++ indicated was in utf-8, but it
contained one character that was not, and that was enough to cause LyX
problems.
Since you mentioned Notepad and Wordpad, I suspect you're on Windows(?).
If you don't already have the iconv utility, you might want to
download it (there's a free Windows port that's part of the GnuWin32
project on SourceForge, at
http://gnuwin32.sourceforge.net/packages/libiconv.htm). Cygwin also
should contain it. Once it's installed, try running
iconv -c -t utf-8 yourfile > newfile
in a DOS shell. This should convert the original file (yourfile) to a
utf-8 version (newfile), omitting any characters that are not valid in
utf-8. You can then compare newfile to yourfile to see what, if
anything, was omitted. (If you want to tell whether yourfile is in fact
valid utf-8, run inconv without the -c flag. It will fail with an error
message if it encounters any invalid characters.)
/Paul
