Am 10.04.2014 um 08:57 schrieb Cyrille Artho <c.ar...@aist.go.jp>: > How is the call to iconv implemented? On the application level, the interface > is probably not flexible enough; it is easy to ignore non-convertible > characters, but they are just removed from the output. > > The C library interface is probably richer. Is it possible to convert text > word by word, find out which words are not convertible, and ignore the > dictionary for those words? (The user could still choose to ignore/add them > to the custom dictionary.)
The ignore operation is part of the spell checker API. You have to use the dictionary encoding for it, IMO. At least it is safe to do so. The behavior for not using the dictionary encoding when adding words at run time is not documented. > Maybe this requires a different way of integrating spell checkers? Ideally the dictionaries should be converted to UTF-8, IMHO. But they are not provided by the LyX developers. Stephan > Jürgen Spitzmüller wrote: >> 2014-04-10 1:02 GMT+02:00 Cyrille Artho <c.ar...@aist.go.jp >> <mailto:c.ar...@aist.go.jp>>: >> >> I think we have to use Unicode for all the given operations and (a) >> either risk a mismatch for each word that is not learned/ignored, or >> (b) up-convert words in the dictionary before they are matched. The >> latter solution implies that the dictionary tool supports this; does >> anyone know if that is the case (for at least one tool)? >> >> >> This is the problem here. Hunspell dictionaries are often not >> unicode-encoded. So we are stuck with non-unicode encodings. >> >> Jürgen > > -- > Regards, > Cyrille Artho - http://artho.com/ > No problem is so formidable that you can't just walk away from it. > -- C. Schulz
