Re: Possible BofF question -- I18n (was: Re: Possible OBF question -- I18n)
John C Klensin <john-ietf@jck.com> Thu, 31 May 2018 17:08 UTC
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D641F12D96B for <ietf@ietfa.amsl.com>; Thu, 31 May 2018 10:08:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id goZeyhL9elFj for <ietf@ietfa.amsl.com>; Thu, 31 May 2018 10:08:46 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5B0A012EB12 for <ietf@ietf.org>; Thu, 31 May 2018 10:08:46 -0700 (PDT)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1fOR43-000EHJ-EA; Thu, 31 May 2018 13:08:39 -0400
Date: Thu, 31 May 2018 13:08:31 -0400
From: John C Klensin <john-ietf@jck.com>
To: "tom p." <daedulus@btconnect.com>
cc: John R Levine <johnl@taugh.com>, Patrik Fältström <paf@frobbit.se>, IETF general list <ietf@ietf.org>
Subject: Re: Possible BofF question -- I18n (was: Re: Possible OBF question -- I18n)
Message-ID: <886A3E084E814A147191B9E6@PSB>
In-Reply-To: <00d101d3f8f4$7d14cc20$4001a8c0@gateway.2wire.net>
References: <20180530231127.17198276FEE3@ary.qy> <071E6235FE7B088A2B56A238@PSB> <0093E2CD-670E-47B6-A286-4FDEB140FAD9@frobbit.se> <alpine.OSX.2.21.1805310929220.3605@ary.qy> <00d101d3f8f4$7d14cc20$4001a8c0@gateway.2wire.net>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/L2E8EhMXD7K5cKpCB-abBgnNEPk>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 31 May 2018 17:08:49 -0000
--On Thursday, May 31, 2018 16:31 +0100 "tom p." <daedulus@btconnect.com> wrote: > I have always seen the centre of gravity of i18n as firmly in > Europe. I recall the struggles 40 years ago to persuade > American organisations to take it seriously; I have always > seen ASCII as an American response to the issue. Actually, while I can't speak for what you see, the centre (sic) of gravity changed around two decades ago and that (Western, Latin-script-using) European orientation turned into a problem as people using that script assumed that the issues associated with their languages were the hard ones and that they could think about everything else in those terms. Our colleagues in Asia (eastern and western), parts of Africa, and probably elsewhere, know better, including knowing about scripts whose characters are always written in connected form, that may have right to left or top to bottom characteristics, that have very different conventions about punctuation and word and sentence separation than Latin and closely-related scripts, and so on (that is definitely not a complete list). The impetus for IDN work came from East and Southeast Asia, not Europe, and other examples abound. There are active IETF participants whose daily work and/or family lives include use of Arabic script (in both Arabic language and Persian-derived variations), Chinese script, Cyrillic, Hebrew script, Korean Hangul, scripts and writing systems of the Indian Subcontinent, and others I apologize for not being able to think of at the moment. At least as much pressure is, or should be, coming from them as from those who merely need a handful or what we sometimes call decorated Roman letters. There is very serious work on internationalization in China, India, Israel, Japan, Russia, Ukraine, a number of Arabic-speaking countries, and others I either don't know about or that don't come to mind at the moment. > Most of what I have learnt since comes from people who appear, > from their affiliation, to be centred in Europe so I am not > surprised that i18n efforts in the IETF do not reach as > satisfactory a conclusion as some other work since the IETF > has long had a closer connection with North America than other > regions of the world. > > So where should the work take place? In a Europe-centric > organisation, perhaps the EU (who put a lot of effort into > some fields of IT), the ITU (which after all does recognise > languages other than American in its work) or some such; and > then there is Unicode which represents a certain competence in > this area:-) I don't want to start a conversation about specific organizations here, but each of those you mention has what I believe the IETF would conclude has an unattractive track record where internationalization is considered broadly in an Internet context. Note too that decisions to work in multiple languages (and the ability to execute on those decisions) is very different from decisions to develop protocols that function well in many (or all) languages and, as I said earlier, while coding is critically important, it is not all of the problem or even most of it. > I have wondered if the focus for this work would shift to the > CJK parts of the world, as they became more engaged in > mainstream IT, since European code page issues seem trivial > compared to those of CJK, but I have not detected any such > movement; Europe still seems to be the most concerned with > this issue and so most likely to put effort into progress. Interesting. I suggest you have been looking in the wrong places, even about participants in the IETF. best, john
- Possible OBF question -- I18n John C Klensin
- Re: Possible OBF question -- I18n John Levine
- Re: Possible BofF question -- I18n (was: Re: Poss… John C Klensin
- Re: Possible BofF question -- I18n (was: Re: Poss… Patrik Fältström
- Re: Possible BofF question -- I18n (was: Re: Poss… John R Levine
- Re: Possible BofF question -- I18n (was: Re: Poss… John C Klensin
- Re: Possible BofF question -- I18n (was: Re: Poss… Patrik Fältström
- Re: Possible BofF question -- I18n (was: Re: Poss… Patrik Fältström
- Re: Possible BofF question -- I18n (was: Re: Poss… tom p.
- Re: Possible BofF question -- I18n (was: Re: Poss… John R Levine
- Re: Possible BofF question -- I18n (was: Re: Poss… John C Klensin
- Re: Possible BofF question -- I18n (was: Re: Poss… Nico Williams
- Re: Possible BofF question -- I18n (was: Re: Poss… Peter Saint-Andre
- Re: Possible BofF question -- I18n (was: Re: Poss… Donald Eastlake
- Re: Possible BofF question -- I18n (was: Re: Poss… John C Klensin
- Re: Possible BofF question -- I18n (was: Re: Poss… John C Klensin
- Re: Possible BofF question -- I18n (was: Re: Poss… Patrik Fältström
- Re: Possible BofF question -- I18n (was: Re: Poss… Patrik Fältström
- Re: Possible BofF question -- I18n (was: Re: Poss… Spencer Dawkins at IETF
- Re: Possible BofF question -- I18n Adam Roach
- Re: Possible BofF question -- I18n (was: Re: Poss… Nico Williams
- Re: Possible BofF question -- I18n (was: Re: Poss… Nico Williams
- Re: Possible BofF question -- I18n Brian E Carpenter
- RE: Possible BofF question -- I18n (was: Re: Poss… Larry Masinter
- Re: Possible BofF question -- I18n (was: Re: Poss… Patrik Fältström
- RE: Possible BofF question -- I18n (was: Re: Poss… John C Klensin
- Re: Possible BofF question -- I18n (was: Re: Poss… Nico Williams
- Re: Possible BofF question -- I18n (was: Re: Poss… Patrik Fältström
- Re: Possible BofF question -- I18n (was: Re: Poss… Benjamin Kaduk
- Re: Possible BofF question -- I18n (was: Re: Poss… Peter Saint-Andre
- Re: Possible BofF question -- I18n (was: Re: Poss… Niels ten Oever
- Re: Possible BofF question -- I18n (was: Re: Poss… John R Levine
- Re: Possible BofF question -- I18n (was: Re: Poss… Peter Saint-Andre
- Re: Possible BofF question -- I18n (was: Re: Poss… John R Levine
- Re: Possible BofF question -- I18n (was: Re: Poss… Spencer Dawkins at IETF
- Re: Possible BofF question -- I18n (was: Re: Poss… Spencer Dawkins at IETF
- Re: Possible BofF question -- I18n (was: Re: Poss… Nico Williams
- Re: Possible BofF question -- I18n (was: Re: Poss… Nico Williams
- Re: Possible BofF question -- I18n (was: Re: Poss… Stephen Farrell
- Re: Possible BofF question -- I18n (was: Re: Poss… Nico Williams
- Re: Possible BofF question -- I18n (was: Re: Poss… John C Klensin
- Re: Possible BofF question -- I18n (was: Re: Poss… Patrik Fältström
- Re: Possible BofF question -- I18n (was: Re: Poss… Spencer Dawkins at IETF
- Re: Possible BofF question -- I18n (was: Re: Poss… Peter Saint-Andre
- Re: Possible BofF question -- I18n (was: Re: Poss… John C Klensin
- Re: Possible BofF question -- I18n (was: Re: Poss… Spencer Dawkins at IETF
- Re: Possible BofF question -- I18n (was: Re: Poss… Nico Williams
- Re: Possible BofF question -- I18n (was: Re: Poss… Nico Williams
- Re: Possible BofF question -- I18n (was: Re: Poss… Spencer Dawkins at IETF
- Re: Possible BofF question -- I18n Brian E Carpenter
- Re: Possible BofF question -- I18n (was: Re: Poss… Patrik Fältström
- Re: Possible BofF question -- I18n John R Levine
- Re: Possible BofF question -- I18n (was: Re: Poss… John C Klensin
- Re: Possible BofF question -- I18n (was: Re: Poss… Nico Williams
- Re: Possible BofF question -- I18n Nico Williams
- Re: Possible BofF question -- I18n Nico Williams
- Re: Possible BofF question -- I18n (was: Re: Poss… Patrik Fältström
- Re: Possible BofF question -- I18n Brian E Carpenter
- Re: Possible BofF question -- I18n Nico Williams
- Re: Possible BofF question -- I18n Barry Leiba
- Re: Possible BofF question -- I18n Viktor Dukhovni
- Re: Possible BofF question -- I18n Christian Huitema
- Re: Possible BofF question -- I18n Nico Williams
- Re: Possible BofF question -- I18n tom p.
- Re: Possible BofF question -- I18n Barry Leiba
- Re: Possible BofF question -- I18n ned+ietf
- Re: Possible BofF question -- I18n ned+ietf