all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Tobias Getzner <tobias.getzner@gmx.de>
To: 17437@debbugs.gnu.org
Subject: bug#17437: 24.3; ispell uses typographically correct apostrophe
Date: Tue, 22 Jul 2014 11:42:21 +0200	[thread overview]
Message-ID: <1406022141.16949.2.camel@gmx.de> (raw)
In-Reply-To: <trinity-69d4191f-ecd1-4780-bbdd-9d12e68b3d52-1399551317647@3capp-gmx-bs52>

> More details are needed here, e.g., what language is the reporter using?

I suppose you are referring to the selected ispell dictionary? I am not
explicitly setting the ispell dictionary, so (I presume) ispell.el will
not pass a dictionary to hunspell, which will accordingly use the
default one for my locale, i. e., en_US. While some dictionaries have
issues with U+2019 (and in fact most still are encoded in latin-1 :-/),
I have added this character to WORDCHARS in my hunspell en_US
dictionary; hunspell now correctly recognize words using this character
when invoking hunspell in a terminal. Sadly, it seems ispell.el sadly
still won’t handle these, however.

The problem seems to be that ispell.el still thinks that U+2019 is a
word boundary and doesn’t pass the whole word on to the spell checker.
Is this likely? Looking at ispell.el, it looks like it is doing word
boundary parsing on its own‽ If so, U+2019 should be treated as a
word-character when it appears in the context of two alphabetical
characters (at least for most western languages).

Best regards,
Tobias







  parent reply	other threads:[~2014-07-22  9:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-08 12:15 bug#17437: 24.3; ispell uses typographically correct apostrophe as word boundary Tobias Getzner
2014-05-08 17:38 ` Agustin Martin
2014-05-09  5:07   ` Tobias Getzner
2014-07-22  9:42 ` Tobias Getzner [this message]
2019-12-06 10:59   ` bug#17437: 24.3; ispell uses typographically correct apostrophe Alan Third

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=1406022141.16949.2.camel@gmx.de \
    --to=tobias.getzner@gmx.de \
    --cc=17437@debbugs.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.