From: Yuri Khan <yuri.v.khan@gmail.com>
To: Dmitry Alexandrov <dag@gnui.org>
Cc: Eric Abrahamsen <eric@ericabrahamsen.net>,
help-gnu-emacs <help-gnu-emacs@gnu.org>
Subject: Re: Hunspell and contractions with apostrophes
Date: Wed, 27 May 2020 11:22:42 +0700 [thread overview]
Message-ID: <CAP_d_8U8wv4gZpPOOWaUAxcQiVo_ktx+h9o1hg-syuJEaayeCQ@mail.gmail.com> (raw)
In-Reply-To: <o8qa5iq3.dag@gnui.org>
On Wed, 27 May 2020 at 07:23, Dmitry Alexandrov <dag@gnui.org> wrote:
> First and foremost, your ’ is *not* an apostrophe, itʼs a right quote. Apostrophe is ʼ.
> I you insist on using right single quote as apostrophe, though, I have no idea, how to make ispell.el pass it to hunspell(1) as a part of a word. Neither why ever do that.
Because the Unicode standard says so.
<https://www.unicode.org/charts/PDF/U2000.pdf>, entry for U+2019:
2019 ’ RIGHT SINGLE QUOTATION MARK
= single comma quotation mark
• this is the preferred character to use for apostrophe
→ 0027 ' apostrophe
→ 02BC ʼ modifier letter apostrophe
→ 275C ❜ heavy single comma quotation mark ornament
(Yes, it’s unfortunate for word boundary algorithms.)
Also, <https://www.unicode.org/charts/PDF/U02B0.pdf>:
02BC ʼ MODIFIER LETTER APOSTROPHE
= apostrophe
• glottal stop, glottalization, ejective
• many languages use this as a letter of their alphabets
• used as a tone marker in Bodo, Dogri, and Maithili
• 2019 ’ is the preferred character for a punctuation apostrophe
→ 0027 ' apostrophe
→ 0313 ̓ combining comma above
→ 0315 ̕ combining comma above right
→ 055A ՚ armenian apostrophe
→ 07F4 ߴ nko high tone apostrophe
→ 1FBF ̓ greek psili
→ 2019 ’ right single quotation mark
next prev parent reply other threads:[~2020-05-27 4:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-26 17:48 Hunspell and contractions with apostrophes Eric Abrahamsen
2020-05-26 19:08 ` Eli Zaretskii
2020-05-26 20:03 ` Eric Abrahamsen
2020-05-27 2:25 ` Eli Zaretskii
2020-05-27 21:24 ` Eric Abrahamsen
2020-05-27 21:53 ` Eric Abrahamsen
2020-05-28 6:22 ` Eli Zaretskii
2020-05-28 14:00 ` Eric Abrahamsen
2020-05-28 16:06 ` Eli Zaretskii
2020-05-28 17:30 ` Eric Abrahamsen
2020-05-28 17:45 ` Eric Abrahamsen
2020-05-27 0:23 ` Dmitry Alexandrov
2020-05-27 2:32 ` Eli Zaretskii
2020-05-27 4:22 ` Yuri Khan [this message]
2020-05-27 6:05 ` (Mis?)using quote as apostrophe (was: Hunspell and contractions with apostrophes) Dmitry Alexandrov
2020-05-27 6:53 ` Yuri Khan
2020-05-27 7:53 ` (Mis?)using quote as apostrophe Dmitry Alexandrov
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=CAP_d_8U8wv4gZpPOOWaUAxcQiVo_ktx+h9o1hg-syuJEaayeCQ@mail.gmail.com \
--to=yuri.v.khan@gmail.com \
--cc=dag@gnui.org \
--cc=eric@ericabrahamsen.net \
--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.
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).