From: Nikolai Weibull <now@disu.se>
To: Robert Thorpe <rt@robertthorpeconsulting.com>
Cc: Emacs Users <help-gnu-emacs@gnu.org>
Subject: Re: Getting Emacs to play nice with Hunspell and apostrophes
Date: Sat, 7 Jun 2014 20:18:49 +0200 [thread overview]
Message-ID: <CADdV=MvmxJjdLnikvhxQtZO_GK7s2fuRA3AXd92ZJuUox0vj-Q@mail.gmail.com> (raw)
In-Reply-To: <87a99oipit.fsf@robertthorpeconsulting.com>
On Sat, Jun 7, 2014 at 7:43 PM, Robert Thorpe
<rt@robertthorpeconsulting.com> wrote:
> Nikolai Weibull <now@disu.se> writes:
>> “isn’t”
>
> In Britain and Ireland we generally use "isn't", notice there's no angle
> on the apostrophe.
It’s generally used (in Britain and in other places) instead of the
more correct “typographical” apostrophe/right single quotation mark
because it’s more easily accessible on the standard computer keyboard,
not because it’s preferred.
> The one you're using "’" is the Unicode RIGHT
> QUOTATION MARK.
No, it’s the U+2019 RIGHT SINGLE QUOTATION MARK.
> So, to Emacs you are closing quotes around "isn" and
> putting a "t" straight after that.
I realize that ‘’’ is seen as punctuation by Emacs, which is true in
some cases, when, for example, doing quoting in British English, for
example, ‘this is a quote’ or when doing nested quoting in American
English, for example, “this quote quotes ‘another quote’”, but it’s
also sometimes a character that should be seen as part of a word.
> As far as I know, if you want to use Unicode that would be "isnʼt" which
> is MODIFIER LETTER APOSTROPHE. Have a look with C-u C-x =. I don't
> know if using that will work though.
No, that’s incorrect, please see, for example,
http://en.wikipedia.org/wiki/Apostrophe#Unicode
for a description about the use of apostrophes and Unicode.
next prev parent reply other threads:[~2014-06-07 18:18 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 [this message]
2014-06-07 17:53 ` Sharon Kimble
2014-06-07 18:17 ` Eli Zaretskii
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='CADdV=MvmxJjdLnikvhxQtZO_GK7s2fuRA3AXd92ZJuUox0vj-Q@mail.gmail.com' \
--to=now@disu.se \
--cc=help-gnu-emacs@gnu.org \
--cc=rt@robertthorpeconsulting.com \
/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.