Hi, On Fri, Jun 16, 2017 at 2:55 PM, Rene Engelhard <r...@debian.org> wrote: > > Does it also happen with current upstresm (1.6.1)? It's in experimental right > now but will > be uploaded to unstable shortly after the stretch release.
With 1.6 the situation is worse (but it's probably a different bug). It doesn't report encoding error, but it doesn't report any status at all when I'm using the ru_RU dictionary: % hunspell -d ru_RU,en_US Hunspell 1.6.1 прив It accepts the next word, replies to it if it's an English one, but tells nothing to any Russian letters in the input. Also, removing en_US from the command line doesn't change much. Hunspell reacts silently on Cyrillics in input. It was with hunspell from experimental (1.6.1-1) with hunspell-ru (1:5.2.5-1). Cheers! -- Sergei Golovan