From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Getting Emacs to play nice with Hunspell and apostrophes
Date: Sat, 07 Jun 2014 21:17:26 +0300 [thread overview]
Message-ID: <83ppik37pl.fsf@gnu.org> (raw)
In-Reply-To: <87ha3wobbo.fsf@skimble.plus.com>
> From: Sharon Kimble <boudiccas@skimble.plus.com>
> Date: Sat, 07 Jun 2014 18:53:47 +0100
> Cc: Emacs Users <help-gnu-emacs@gnu.org>
>
> ;; Use hunspell instead of ispell
> (if (file-exists-p "/usr/bin/hunspell")
> (progn
> (setq ispell-program-name "hunspell")
> (eval-after-load "ispell"
> '(progn (defun ispell-get-coding-system () 'utf-8)))))
> (setq ispell-program-name "hunspell")
> (require 'rw-hunspell)
> (require 'rw-language-and-country-codes)
> (require 'rw-ispell)
> (setq ispell-dictionary "en_GB_hunspell")
> --8<---------------cut here---------------end--------------->8---
>
> Hopefully this will help you get going with hunspell, which I have
> found is good! :) This is all I have set up for hunspell and it
> works okay with "isn’t" as I've just corrected it in this email.
I don't see how that would work, unless you are using a version of an
English dictionary that knows about the ’ character. I don't think
the rw-* packages have anything to do with that, or could have.
So I think a more interesting for the OP question will be where did
you get that "en_GB_hunspell" dictionary you are using, because that
dictionary might actually hold the answer for his questions.
P.S. Most, if not all, of what rw-* packages do is already handled in
the ispell.el that comes with the latest versions of Emacs, which
include a full support for Hunspell. You might as well try using
Emacs without those add-ons, you will probably find they are not
needed anymore.
next prev parent reply other threads:[~2014-06-07 18:17 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-07 15:39 Getting Emacs to play nice with Hunspell and apostrophes Nikolai Weibull
2014-06-07 17:43 ` Robert Thorpe
2014-06-07 17:59 ` Yuri Khan
2014-06-07 18:18 ` Nikolai Weibull
2014-06-07 17:53 ` Sharon Kimble
2014-06-07 18:17 ` Eli Zaretskii [this message]
2014-06-07 18:28 ` Nikolai Weibull
2014-06-07 18:40 ` Eli Zaretskii
2014-06-07 19:59 ` Nikolai Weibull
[not found] <mailman.3187.1402155569.1147.help-gnu-emacs@gnu.org>
2014-06-11 0:04 ` Emanuel Berg
2014-06-11 5:23 ` Nikolai Weibull
[not found] ` <mailman.3375.1402464243.1147.help-gnu-emacs@gnu.org>
2014-06-11 14:24 ` Emanuel Berg
2014-06-11 15:03 ` Nikolai Weibull
[not found] ` <mailman.3418.1402499010.1147.help-gnu-emacs@gnu.org>
2014-06-11 15:20 ` Emanuel Berg
2014-06-11 16:57 ` Teemu Likonen
[not found] ` <mailman.3437.1402505846.1147.help-gnu-emacs@gnu.org>
2014-06-11 21:32 ` Emanuel Berg
2014-06-12 5:43 ` Yuri Khan
2014-06-12 12:51 ` Stefan Monnier
2014-06-12 13:36 ` Nikolai Weibull
2014-06-12 14:48 ` Stefan Monnier
[not found] ` <mailman.3496.1402580195.1147.help-gnu-emacs@gnu.org>
2014-06-14 1:49 ` Emanuel Berg
2014-06-14 5:45 ` Yuri Khan
[not found] ` <mailman.3627.1402724759.1147.help-gnu-emacs@gnu.org>
2014-06-14 11:14 ` Emanuel Berg
2014-06-14 14:51 ` Yuri Khan
2014-06-14 15:26 ` Teemu Likonen
2014-06-17 1:42 ` Garreau, Alexandre
[not found] ` <mailman.3651.1402757512.1147.help-gnu-emacs@gnu.org>
2014-06-14 16:13 ` Emanuel Berg
2014-06-16 15:35 ` Joost Kremers
2014-06-17 2:21 ` Garreau, Alexandre
[not found] ` <mailman.3799.1402971688.1147.help-gnu-emacs@gnu.org>
2014-06-17 2:41 ` Rusi
2014-06-17 3:05 ` Rusi
2014-06-17 1:46 ` Garreau, Alexandre
2014-06-15 2:48 ` Sergio Pokrovskij
2014-06-17 1:30 ` Garreau, Alexandre
2014-06-12 16:58 ` Eli Zaretskii
[not found] ` <mailman.3473.1402551809.1147.help-gnu-emacs@gnu.org>
2014-06-14 1:35 ` Emanuel Berg
2014-06-14 2:38 ` Emanuel Berg
2014-06-14 7:11 ` Yuri Khan
[not found] ` <mailman.3630.1402729917.1147.help-gnu-emacs@gnu.org>
2014-06-14 11:20 ` Emanuel Berg
2014-06-17 2:12 ` Rusi
2014-06-17 2:33 ` Garreau, Alexandre
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83ppik37pl.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=help-gnu-emacs@gnu.org \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.