I agree that it would be good to have all dictionaries in utf-8, but I'm
not sure if this is feasible for a typical user/installation.
Another option would be for LyX to tokenize the text and forward it word by
word to the spell checker.
This way, we could handle "Ignore All" in LyX itself rather than let the
spell checker ignore the word. LyX would never forward ignored words to the
spell checker but all the remaining words would be handled by the spell
checker.
Jürgen Spitzmüller wrote:
2014-04-10 14:18 GMT+02:00 Jean-Marc Lasgouttes <lasgout...@lyx.org
<mailto:lasgout...@lyx.org>>:
The point is that users cannot do something sensible with such marked
words (except for adding them into the personal dictionary).
Sure, but the same holds for "Lasgouttes", doesn't it?
No, if the encoding fits, I can hit "Ignore all" and only ignore you (or
your name's spelling, for that matter) in the current document (which is
what I do for names usually, except for very recurrent names). If the
encoding does not fit, hitting "Ignore all" just would not work. I think we
would need to at least disable the ignore all button/menu entry in that
case, otherwise users would rightly complain about that bug (they would
also, probably, not understand why the function is disabled for specific
names.).
So, to sum up: I agree with all of you that strings from non-matching
encodings should be marked as unknown, but only if we can provide sensible
action.
Jürgen
BTW German hunspell suggests "Ausgelastet" for "Lasgouttes", which means
"fully occupied" or "snowed with work".
JMarc
--
Regards,
Cyrille Artho - http://artho.com/
The opposite of a correct statement is a false statement. But the
opposite of a profound truth may well be another profound truth.
-- Niels Bohr
