On Fri, Mar 27, 2009 at 8:43 PM, Guenter Milde <mi...@users.berlios.de> wrote: > Setting Document>Settings>Language>Encoding to UTF8 (ucs enhanced/utf8x) > solves this particular problem.
Would this be a sensible default? > IMO, it is correct not to use the LaTeX transcription from > "unicodesymbols" for ERT, as ERT is "raw LaTeX". One option would be to use the transcription when pasting into the ERT. Although then LyX would have to know which characters were valid in the current encoding, and handle the case of the encoding of a document being changed in someway. >> You had to be difficult didn't you! :P > > No, just generic. While this might be a quick fix for you, there are just > too many unicode characters that are regularely used by users around the > world to make this a LyX internal. For the record, the proposal was to put this script up on the wiki since I didn't realize iconv had //TRANSLIT ... but since you mention it: > LyX should at least show it in a pop-up (similar to LaTeX errors), so > that the user has immediate feedback on why there is no reaction. Even > better: parse it and report the location. Would a python script that generated a LaTeX style error log be helpful? E.g., like http://wiki.lyx.org/Tools/LyX-GrammarChecker but in python? I can write C/C++, but python sounds more maintainable in this case. -- John C. McCabe-Dansted PhD Student University of Western Australia
