Re: [Ltru] IPA and other transcriptions (was: Re: script tag for IPA)

"Doug Ewell" <dewell@adelphia.net> Sat, 16 September 2006 23:28 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GOja8-0006wW-Fi; Sat, 16 Sep 2006 19:28:20 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GOja7-0006u0-4b for ltru@ietf.org; Sat, 16 Sep 2006 19:28:19 -0400
Received: from mta11.adelphia.net ([68.168.78.205]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GOja5-0006hI-SB for ltru@ietf.org; Sat, 16 Sep 2006 19:28:19 -0400
Received: from DGBP7M81 ([68.67.66.131]) by mta11.adelphia.net (InterMail vM.6.01.05.02 201-2131-123-102-20050715) with SMTP id <20060916232813.BFAV28624.mta11.adelphia.net@DGBP7M81>; Sat, 16 Sep 2006 19:28:13 -0400
Message-ID: <00ac01c6d9e7$c7e90dd0$6401a8c0@DGBP7M81>
From: Doug Ewell <dewell@adelphia.net>
To: LTRU Working Group <ltru@ietf.org>
References: <E1GNiLf-0004yQ-BF@megatron.ietf.org> <005701c6d88a$21f245d0$6401a8c0@DGBP7M81> <20060915055401.GC6907@ccil.org> <450A44B6.3060905@sil.org> <6.0.0.20.2.20060915154910.06e040b0@localhost> <450AC979.3050203@yahoo-inc.com> <450B60D4.1040401@sil.org> <004301c6d947$bef6f980$6401a8c0@DGBP7M81> <450C18FA.3090500@sil.org> <009601c6d9b5$cf9defa0$6401a8c0@DGBP7M81> <20060916184658.GC25175@ccil.org>
Subject: Re: [Ltru] IPA and other transcriptions (was: Re: script tag for IPA)
Date: Sat, 16 Sep 2006 16:28:13 -0700
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"; charset="utf-8"; reply-type="original"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.2869
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002
Cc:
X-BeenThere: ltru@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Language Tag Registry Update working group discussion list <ltru.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ltru>, <mailto:ltru-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ltru>
List-Post: <mailto:ltru@ietf.org>
List-Help: <mailto:ltru-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ltru>, <mailto:ltru-request@ietf.org?subject=subscribe>
Errors-To: ltru-bounces@ietf.org

John Cowan <cowan at ccil dot org> wrote:

>> In what way -- other than the actual repertoire of characters used --  
>> do IPA and other phonetic and phonemic notation systems, differ from 
>> those?
>
> I would say in that IPA and its rivals are not orthographies; that is, 
> the meaning of [f] in IPA is standardized, but the choice of when to 
> use it in the representation of some language depends on the acuity of 
> the transcriber.  Per contra, it is very clear when "f" is to be 
> written in the various romanizations of Japanese, whether the sound 
> represented is IPA [f] or not.

I agree that there are differences in the details of their use, but what 
I was getting at was that both are alternative "ways of writing" 
language (note that incredibly vague phrase).  Pinyin (et al.) is not a 
"normal" way of writing Chinese (et al.); it is a special application 
for learners and other non-native readers of the language.  (This is 
different from, say, Serbian in Cyrillic/Latin, where native readers 
might use either script.)

Likewise, IPA (et al.) is not a "normal" way of writing English (et 
al.); it is a special application for linguists and others who need to 
represent the exact (or nearly exact) pronunciation of the language.

> And I do agree that IPA (and rival) sound transcription systems are a 
> very different matter from mere variants in transcription like pinyin 
> vs. Wade-Giles or Hepburn vs. kunrei shiki.

OK, well, that wasn't the way I saw it, but since almost everyone on 
this list probably has more linguistic training than I do, perhaps I 
should back off on this.

Maybe the thing to consider in 4646bis is whether we should remove the 
extension mechanism altogether.  If transcription and transliteration 
systems aren't a good application for extensions, I really don't know 
what is, and nobody else has come forward with a "favorite" potential 
application for them.  The examples in 4646 are all contrived. 
Extensions have never been valid in real-world language tags (since none 
are defined), so they could be removed without breaking anything, and 
doing so would simplify parsers.  "Deprecating" them, of course, would 
be completely pointless.

--
Doug Ewell
Fullerton, California, USA
http://users.adelphia.net/~dewell/
RFC 4645  *  UTN #14


_______________________________________________
Ltru mailing list
Ltru@ietf.org
https://www1.ietf.org/mailman/listinfo/ltru