http://bugzilla.opensuse.org/show_bug.cgi?id=1110387 Ulrich Windl changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|ispell-process-line: Ispell |Emacs: ispell-process-line: |misalignment: ... probably |Ispell misalignment: ... |incompatible versions |probably incompatible | |versions -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1110387 http://bugzilla.opensuse.org/show_bug.cgi?id=1110387#c3 Dr. Werner Fink changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |pgajdos@suse.com --- Comment #3 from Dr. Werner Fink --- Beside this I've no experience with hunspell an the used myspell aff+dict files -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1110387 http://bugzilla.opensuse.org/show_bug.cgi?id=1110387#c7 Ulrich Windl changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(Ulrich.Windl@rz.u | |ni-regensburg.de) | --- Comment #7 from Ulrich Windl --- (In reply to Petr Gajdos from comment #4)

I get for Tumbleweed and 15.0:

$ echo $LC_CTYPE en_US.UTF-8 $ file bug.tex bug.tex: LaTeX 2e document, ISO-8859 text $ hunspell -l -i ISO-8859-1 -d de_DE bug.tex müßte $

echo $LC_TYPE

file /tmp/bug.tex /tmp/bug.tex: LaTeX 2e document, ISO-8859 text hunspell -l -i ISO-8859-1 -d de_DE bug.tex Can't open affix or dictionary files for dictionary named "de_DE".

Looking for dictionaries, I see ispell-dictionaries, myspell-dictionaries, and aspell-dictionaries. Which is the dictionary to be installed? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1110387 http://bugzilla.opensuse.org/show_bug.cgi?id=1110387#c11 --- Comment #11 from Ulrich Windl --- (In reply to Dr. Werner Fink from comment #10)

Just read comment #5 and then do what I've done ... or remove all ispell packages and restart GNU Emacs

I don't quite understand: There are no ispell packages installed (just some myspell packages), and how are your Emacs settings different? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1110387 http://bugzilla.opensuse.org/show_bug.cgi?id=1110387#c15 --- Comment #15 from Ulrich Windl --- (In reply to Dr. Werner Fink from comment #14)

Please write

de_DE

that's it.

No: If I try to enter it, I just get " [no match]" (which is not surprising presenting the completion list in comment 13). When adding it the hard way (via Customize), the messages created are: Starting new Ispell process [/usr/bin/hunspell::de_DE] ... Spell-checking bug.tex using hunspell with de_DE dictionary...done ispell-get-decoded-string: No data for dictionary "de_DE", neither in `ispell-local-dictionary-alist' nor in `ispell-dictionary-alist' -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1110387 http://bugzilla.opensuse.org/show_bug.cgi?id=1110387#c19 --- Comment #19 from Dr. Werner Fink --- The function (ispell-find-hunspell-dictionaries) is defined in ispell.el found below /usr/share/emacs/<version of emacs>/lisp/textmodes/ispell.elc Therefore a simple M-x load-library and ispell should help here. This annoying hunspell is missed in /usr/share/emacs/site-lisp/site-start.el at ;; ;; Preload dynamic (i)Spell menu ;; ----------------------------- (if (not (load "/usr/lib/ispell/ispell-emacs-menu.el" t t)) (let ((aspells (file-expand-wildcards "/usr/lib/aspell*"))) (dolist (aspell aspells) (if (and (stringp aspell) (file-exists-p aspell)) (load "ispell" nil t))))) ;; I'd realy like to know why I've not be informed that now a new spellchecker is in use and comes without its onw emacs lisp file for preloading ispell.el -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1110387 http://bugzilla.opensuse.org/show_bug.cgi?id=1110387#c21 --- Comment #21 from Dr. Werner Fink --- (In reply to Ulrich Windl from comment #20)

(In reply to Dr. Werner Fink from comment #19) The mystery continues; maybe it would help if you could actually try with Leap 42.3: (load-library "ispell") was successful, but the function ispell-find-hunspell-dictionaries is still unknown. The function most similar to that would be ispell-find-aspell-dictionaries, but when executes it says "ispell-find-aspell-dictionaries: This function only works with aspell >= 0.60"

(evaluating your elisp code made no difference)

Use Leap 15 ... GNU Emacs from Leap 42.3 does not know about hunspell and I'll not fix this -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1110387 http://bugzilla.opensuse.org/show_bug.cgi?id=1110387#c25 --- Comment #25 from Dr. Werner Fink --- (In reply to Ulrich Windl from comment #22)

(In reply to Dr. Werner Fink from comment #21)

...

Use Leap 15 ... GNU Emacs from Leap 42.3 does not know about hunspell and I'll not fix this

Wonderful (ironic)! Wasn't the support for Leap 42.3 extended (until 31.06.2019), because Leap 15 has so many new issues?

Bug and security fixes yes ... new features no (IMHO) ... the question is if the new ispell.el would compile below old GNU Emacs You could use aspell and/or ispell -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1110387 http://bugzilla.opensuse.org/show_bug.cgi?id=1110387#c28 Dr. Werner Fink changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #786812|0 |1 is obsolete| | --- Comment #28 from Dr. Werner Fink --- Created attachment 786849 --> http://bugzilla.opensuse.org/attachment.cgi?id=786849&action=edit ispell.el Just a replacment as I've seen that for older distributions it might fail -- You are receiving this mail because: You are on the CC list for the bug.