From: Juri Linkov <juri@jurta.org>
To: Aidan Kehoe <kehoea@parhasard.net>
Cc: Oleksandr Gavenko <gavenkoa@gmail.com>, emacs-devel@gnu.org
Subject: Re: Status of IPA patch?
Date: Fri, 28 Aug 2009 22:05:33 +0300 [thread overview]
Message-ID: <87eiqvpyxe.fsf@mail.jurta.org> (raw)
In-Reply-To: <19095.20639.983609.638911@parhasard.net> (Aidan Kehoe's message of "Fri, 28 Aug 2009 04:35:59 +0100")
> > > > The omission of those two was intentional, since U+20A7 is
> > > > equivalent to tʃ (note that that digraph doesn’t include the tie
> > > > that would be necessary to have it as a phoneme distinct from /t/
> > > > followed by /ʃ/) and g is equivalent to U+0261 for the purposes of
> > > > the IPA.
> >
> > I don’t understand why do you omit U+20A7 and U+0261 if they exist in
> > X-SAMPA and Kirshenbaum?
>
> The IPA standards (which X-SAMPA and Kirshenbaum build on) define _U+20A7_
> and _U+0261_ as being equivalent to _a succession of U+0074 and U+0283_, and
> _U+0067_, respectively. The former two code points just represent
> compatibility glyphs (with U+20A7 leading to needless confusion, since
> people might reasonably believe that it meant the same as U+0074 U+2040
> U+0283, including the tie I mention above).
Since these are three most popular ways to represent this sound,
I think we should support all of them:
1. a ligature ʧ (U+02A7)
2. two symbols tʃ (U+0074 U+0283)
3. two symbols joined with a tie t͡ʃ (U+0074 U+2040 U+0283)
This can be done with a non-deterministic quail guidance string
displaying a menu of possible variants.
> Kirshenbaum mentions ASCII g as mapping to both U+0067 and U+0261 without
> comment. Including both would not add to the semantic range of what the user
> can input (in terms of the IPA), and would again be needlessly confusing
> (the user types g; wonders if 0 or 1 is more appropriate; when it doesn’t
> actually matter,
I agree there is no sense to create a menu of both U+0067 and U+0261,
so we should keep only the IPA symbol U+0261, because U+0067 is easy
to type anyway without an input method.
> and U+0067 is always more certain to be preserved by software).
The problem of preserving by software is not specific to U+0261,
but rather to the most of IPA symbols.
--
Juri Linkov
http://www.jurta.org/emacs/
next prev parent reply other threads:[~2009-08-28 19:05 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4A807E29.1030405@gmail.com>
2009-08-10 20:30 ` bug#4109: Status of IPA patch? Aidan Kehoe
2009-08-25 8:51 ` Aidan Kehoe
2009-08-25 16:06 ` Glenn Morris
2009-08-25 16:23 ` Aidan Kehoe
2009-08-28 0:32 ` Juri Linkov
2009-08-28 3:35 ` Aidan Kehoe
2009-08-28 7:35 ` Aidan Kehoe
2009-08-28 7:37 ` Miles Bader
2009-08-28 12:24 ` Aidan Kehoe
2009-08-28 19:06 ` Juri Linkov
2009-08-28 19:37 ` Aidan Kehoe
2009-08-28 19:45 ` Juri Linkov
2009-08-28 19:05 ` Juri Linkov [this message]
2009-08-28 19:07 ` Juri Linkov
2009-08-28 19:47 ` Aidan Kehoe
2009-08-28 19:57 ` Juri Linkov
2009-08-29 3:17 ` Stefan Monnier
2009-08-30 23:40 ` bug#4109: marked as done (Status of IPA patch?) Emacs bug Tracking System
[not found] <87y6p050zo.fsf@mail.jurta.org>
2008-12-31 13:41 ` bug#1750: [PATCH] Support standard ASCII-IPA mappings in leim/quail/ipa.el Aidan Kehoe
2008-12-31 18:40 ` Stefan Monnier
2008-12-31 19:51 ` Aidan Kehoe
2009-01-19 7:11 ` Aidan Kehoe
2008-12-31 19:57 ` James Cloos
2009-08-30 23:40 ` bug#1750: marked as done ([PATCH] Support standard ASCII-IPA mappings in leim/quail/ipa.el. ) Emacs bug Tracking System
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=87eiqvpyxe.fsf@mail.jurta.org \
--to=juri@jurta.org \
--cc=emacs-devel@gnu.org \
--cc=gavenkoa@gmail.com \
--cc=kehoea@parhasard.net \
/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.