Return-Path: Received: from murder ([unix socket]) by eikenes.alvestrand.no (Cyrus v2.2.8-Mandrake-RPM-2.2.8-4.2.101mdk) with LMTPA; Tue, 14 Jun 2005 15:56:49 +0200 X-Sieve: CMU Sieve 2.2 Received: from localhost (localhost.localdomain [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id 1AE3F61B66 for ; Tue, 14 Jun 2005 15:56:49 +0200 (CEST) Received: from eikenes.alvestrand.no ([127.0.0.1]) by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 28746-08 for ; Tue, 14 Jun 2005 15:56:46 +0200 (CEST) X-Greylist: from auto-whitelisted by SQLgrey-1.4.8 Received: from montage.altserver.com (montage.altserver.com [63.247.74.122]) by eikenes.alvestrand.no (Postfix) with ESMTP id 126A361B64 for ; Tue, 14 Jun 2005 15:56:46 +0200 (CEST) Received: from ver78-2-82-241-91-24.fbx.proxad.net ([82.241.91.24] helo=jfc.afrac.org) by montage.altserver.com with esmtpa (Exim 4.44) id 1DiBuE-0003XE-V3; Tue, 14 Jun 2005 06:56:43 -0700 Message-Id: <6.2.1.2.2.20050614152557.0520d160@mail.jefsey.com> X-Mailer: QUALCOMM Windows Eudora Version 6.2.1.2 Date: Tue, 14 Jun 2005 15:39:52 +0200 To: Harald Tveit Alvestrand , Karen_Broome@spe.sony.com From: "JFC (Jefsey) Morfin" Subject: RE: Swiss german, spoken Cc: 'IETF Languages Discussion' , Debbie Garside In-Reply-To: <4E85E97F4A206004D6BDFDE6@B50854F0A9192E8EC6CDA126> References: <4E85E97F4A206004D6BDFDE6@B50854F0A9192E8EC6CDA126> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - montage.altserver.com X-AntiAbuse: Original Domain - alvestrand.no X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - jefsey.com X-Source: X-Source-Args: X-Source-Dir: X-Virus-Scanned: amavisd-new at alvestrand.no At 05:36 14/06/2005, Harald Tveit Alvestrand wrote: >--On 13. juni 2005 13:23 -0700 Karen_Broome@spe.sony.com wrote: >>Will a MIME type help me distinguish between Arabic, Devangari, Latin, >>Traditional Chinese, or Simplified Chinese in the XML format? > >Nope - but if that's the question, you've already decided that you've got >written text..... > >>Can it be >>used with the xml:lang attribute? That's where I need this data. > >I may be at the tail end of a losing battle, but I still haven't bought >off on the idea that all information containing an information object >needs to be put into the xml:lang attribute. I've been having this >discussion since RFC 1766, so it's not a new debate..... Hi! Harald, Interesting since this is precisely what langtags seem to intend. It would be far more flexible (application wise) to separate concepts and values of different kinds. With an xml:script, xml:region, etc. Network wise giving a name to a lingustic community and to its common interperson protocol is however also of interest, but not necessarily of the same nature (similar to a structural TLD). >>There is >>often a one-to-many relationship between the spoken language and its >>written variants and these written variants must be described. Nothing I >>do is intended for use in e-mail. > >Yep. I think we don't have a disagreement - when I read through the part >of the debate that was downloaded when I uploaded my comment, it seems >that the consensus was pretty strong that scripts were properties of text, >and "written/spoken" was a property of the media..... Why this dichotomy? Texts are (and are more and more) part of the media. There may be the typographers and the publishers, the shooters and the distributors, etc. but there is only one public. A language may be scripted, written, spoken, talked, what ever you want, it is first used. jfc