On Thu, Mar 26, 2009 at 6:54 PM, Jean-Marc Lasgouttes <lasgout...@lyx.org> wrote: > John McCabe-Dansted <gma...@gmail.com> writes: >> In the long run I don't think users should be expected to spend time >> manually fixing iconv errors. At worst LyX could pop up a dialog box: >> "LyX cannot handle the following characters ... [Remove] [Replace] >> [Cancel]". > > No, but they should report them so that we can fix them.
OK, is the following useful?
Pasting the UTF8-apostrophe: ’
into a LyX 1.6.2 ERT box results in an uncompilable document
(attached) with the following errors
Error 84 returned from iconv when converting from UCS-4LE to
ISO-8859-15: Invalid or incomplete multibyte or wide character
Converted input:
Stopped at: 0x2019
Unconverted input:
Converted output:
Error 84 returned from iconv when converting from UCS-4LE to
ISO-8859-15: Invalid or incomplete multibyte or wide character
Converted input:
Stopped at: 0x2019
Unconverted input:
Converted output:
Error 84 returned from iconv when converting from UCS-4LE to
ISO-8859-15: Invalid or incomplete multibyte or wide character
Converted input:
Stopped at: 0x2019
Unconverted input:
Converted output:
File '/tmp/lyx_tmpdir.J11284/lyx_tmpbuf0/UTF_apostrophy.tex' was not
closed properly.
(if it is pasted outside a ERT box, we get \textquoteright{}, and
everything works correctly)
--
John C. McCabe-Dansted
PhD Student
University of Western Australia
UTF_apostrophy.lyx.gz
Description: GNU Zip compressed data
