Am 09.04.2014 um 08:14 schrieb Jürgen Spitzmüller <sp...@lyx.org>:
> 2014-04-08 22:42 GMT+02:00 Georg Baum: > The change in src/support/unicode.cpp is problematic: It disables all error > handling, not only the lyxerr output. Also, if you now throw an exception > there, you need to make sure that all callers can cope with that. Maybe one > solution would be to throw the exception at the very end (after the error > handling), and give it exactly the error message which is now written to > lyxerr. Then each caller can decide what it wants to do with the error > message. > > Thanks. I feared that. I put the exception that early in order to suppress > the lyxerr message. In this case we need to audit all callers. Will postpone > this. > > > I would also propose to treat an encoding error as a spelling error: If the > word can't be encoded in the dictionary of the current language, then it > can't be correct, since we assume that Hunspell does not choose an encoding > for the dictionary of a certain lnguage which does not cover all words of > that language. > > But then, with instant spellchecker, the word will be underlined and the user > can not change that. Can you provide an example, please? If the word cannot be converted to Hunspell dictionary encoding the dictionary is broken or the language is not correct, isn't it? You're right, the user has not many options to get rid of the misspelled marker. S(he) can change the language of the word or add it to the personal word list for the language. The personal word list uses UTF-8, it should be possible to store it there. Stephan
