unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Jochen Schmitt <Jochen@herr-schmitt.de>
Cc: 13460@debbugs.gnu.org
Subject: bug#13460: Issue to change dictionary when using hunspell on emacs
Date: Fri, 18 Jan 2013 21:03:17 +0200	[thread overview]
Message-ID: <83vcau5n62.fsf@gnu.org> (raw)
In-Reply-To: <20130118180321.GA2635@omega.in.herr-schmitt.de>

> Date: Fri, 18 Jan 2013 19:03:34 +0100
> From: Jochen Schmitt <Jochen@herr-schmitt.de>
> 
> I have find out, that hunspell wiel accecpt -d en_GB,en_US as
> an parameter, so this issue may be fixed.

Beware: when you invoke hunspell like that, it uses the .aff file from
the first dictionary only, and ignores any .aff files of the other
dictionaries.  This could bite you where US and GB English differ.

In general, this option is meant to support _additional_ dictionaries
in the same language, like if you want to use a specialized dictionary
for medicine or some other discipline, together with a general-purpose
dictionary for the same language.





  reply	other threads:[~2013-01-18 19:03 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-16 12:25 bug#13460: Issue to change dictionary when using hunspell on emacs Jochen Schmitt
2013-01-16 18:01 ` Eli Zaretskii
2013-01-16 23:23   ` Glenn Morris
2013-01-17  3:51     ` Eli Zaretskii
2013-01-17  6:37       ` Glenn Morris
2013-01-17 12:26         ` Agustin Martin
2013-01-17 15:24           ` Agustin Martin
2013-01-17 16:31             ` Stefan Monnier
2013-01-17 18:15               ` Agustin Martin
2013-01-17 16:41             ` Eli Zaretskii
2013-01-17 18:12               ` Agustin Martin
2013-01-17 18:42                 ` Eli Zaretskii
     [not found]                 ` <11624660.12538.1358448223517.JavaMail.root@mx1-new.spamfiltro.es>
2013-01-17 19:06                   ` Agustin Martin
2013-01-17 19:36                     ` Eli Zaretskii
2013-01-17 18:08             ` Glenn Morris
     [not found]             ` <7076415.12428.1358446115519.JavaMail.root@mx1-new.spamfiltro.es>
2013-01-17 18:44               ` Agustin Martin
2013-01-17 16:10           ` Eli Zaretskii
     [not found]     ` <20130117131733.GA20519@omega.in.herr-schmitt.de>
2013-01-17 18:19       ` Glenn Morris
2013-01-17 19:30         ` Agustin Martin
2013-01-18 17:05           ` Agustin Martin
2013-01-18 18:03             ` Jochen Schmitt
2013-01-18 19:03               ` Eli Zaretskii [this message]
2013-01-18 19:23                 ` Agustin Martin
2013-01-18 19:05               ` Agustin Martin
2013-01-21 16:52                 ` Agustin Martin
2013-01-21  9:43             ` Jochen Schmitt
2013-02-20 17:50 ` bug#13639: [emacs] ispell.el: hunspell dicts autodetection under Emacs Agustin Martin
2013-02-20 19:00   ` Eli Zaretskii
2013-02-28 19:23     ` Agustin Martin
2013-02-28 20:26       ` Eli Zaretskii
2013-04-15 10:18       ` Agustin Martin
2013-04-04 14:41 ` bug#13639: " Jacek Chrząszcz
2013-04-05 15:57   ` Agustin Martin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83vcau5n62.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=13460@debbugs.gnu.org \
    --cc=Jochen@herr-schmitt.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).