IETF Logo Mail Archive

Re: Possible BofF question -- I18n

Brian E Carpenter <brian.e.carpenter@gmail.com> Sat, 02 June 2018 03:54 UTC

Return-Path: <brian.e.carpenter@gmail.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 709D3126BF0 for <ietf@ietfa.amsl.com>; Fri, 1 Jun 2018 20:54:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 NzH12YvVD8-f for <ietf@ietfa.amsl.com>; Fri, 1 Jun 2018 20:54:48 -0700 (PDT)
Received: from mail-pl0-x22f.google.com (mail-pl0-x22f.google.com [IPv6:2607:f8b0:400e:c01::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 63C91126B7E for <ietf@ietf.org>; Fri, 1 Jun 2018 20:54:48 -0700 (PDT)
Received: by mail-pl0-x22f.google.com with SMTP id c41-v6so16384146plj.10 for <ietf@ietf.org>; Fri, 01 Jun 2018 20:54:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=LPGhGMtrYMyItEA7LxNi02G/04Ng/jqoQcSpqQaByhI=; b=SrRZN6GbYQF2LiqhxuzT7EzphiA8kze9JlZp1JAz7KYharOdsQOIp/qNml2VT3Hq07 nDRtY1gfSBBo1k5Br+RJRVM6FqS5YRjxDOuiCA9I9YgyYLXIEeQPczIJOoD3NP26NiR7 pJZ4OKJZ11e+TJpR2F1/tIco2Nkrr+3tis64Ped2wk6B+j60zPv9bvryhMZ/haPkfROS oYUxqx/Tt7oHlSM7DrUqUhukUTmlD3YNum2sKt1J2h4ARooC1gqAE46pIGJTuCymci03 4cC5LqKR+7v+036fubST5gOesaYmTH7vv9VdhYyqjoUYRKAKhkompoAkP366Vww5lMd6 pAiw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=LPGhGMtrYMyItEA7LxNi02G/04Ng/jqoQcSpqQaByhI=; b=cagQ9GNk0OrAReVpgS1e81mmlCCAA0uXiZIo7HhtAVSJUnQtoSJsy38nqVAJcoIqSd 6HZJlKS8Ql1LXUAOz1sofxhGXRgci/c/JpkSRceOwfk1CshlEnJBBWxny+yjdZNh/p+1 n+IuAwCCCO2hor4mwOiEKo/dIXd2xQKiLjR32/HgAXovKYip0CcSDLR3FdwjxptO6z3C 00/ORN2y9o2jvVGMfMdacXYufMIkok6mmK0uWu6yupUUivwwIQDDT7SJXiJzoGptpy9h AiSMHtywOVOGq17/N9ycKinwEp4/qzWq8kdKm8A4NwNHxlVKvlTcp4R77xu0tO5fvZZd 0evA==
X-Gm-Message-State: ALKqPwcVluLlzCqQKuvJuaKLp1RSY4xgD3aENo87LqyEgdu49DBAXxFI pr0MCGOLINafcgiztaxj4Wzs6Q==
X-Google-Smtp-Source: ADUXVKLyjy2Cl9KfGICs+e4FSeStq8TwAWN7Raws66qb/6WYCjk+qL/8zhkoYFORxT4+OW3Bu5x4jg==
X-Received: by 2002:a17:902:24a5:: with SMTP id w34-v6mr13485528pla.52.1527911687724; Fri, 01 Jun 2018 20:54:47 -0700 (PDT)
Received: from [192.168.178.21] ([118.148.121.80]) by smtp.gmail.com with ESMTPSA id f14-v6sm30808257pfn.17.2018.06.01.20.54.44 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 01 Jun 2018 20:54:46 -0700 (PDT)
Subject: Re: Possible BofF question -- I18n
To: Nico Williams <nico@cryptonector.com>, John R Levine <johnl@taugh.com>
Cc: IETF general list <ietf@ietf.org>
References: <20180530231127.17198276FEE3@ary.qy> <071E6235FE7B088A2B56A238@PSB> <0093E2CD-670E-47B6-A286-4FDEB140FAD9@frobbit.se> <20180531172228.GF14446@localhost> <383c2404-7beb-63e9-b2b2-e75fd1b174f1@mozilla.com> <20180601041949.GH14446@localhost> <A13FFF23-49BD-459D-8B5B-D3448154EEBC@frobbit.se> <20180601151053.GI14446@localhost> <2584adb9-1622-8b49-7236-ecc7dd374974@mozilla.com> <alpine.OSX.2.21.1806011219340.7621@ary.qy> <CAK3OfOgv33SJiPJ6ypo8k5hcpnjcJdRso6EXb9b12YNcdDgMUg@mail.gmail.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <6c5d5618-74a5-dcc8-d818-89243a41f307@gmail.com>
Date: Sat, 02 Jun 2018 15:54:54 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0
MIME-Version: 1.0
In-Reply-To: <CAK3OfOgv33SJiPJ6ypo8k5hcpnjcJdRso6EXb9b12YNcdDgMUg@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/7U3NJKTCANy8CDIhSZA3XX1Jg8E>
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: Sat, 02 Jun 2018 03:54:51 -0000

I'm an ignoramus, but:
On 02/06/2018 05:59, Nico Williams wrote:
...
> Not everyone can pick up I18N expertise  quickly?  Sure, but we engineer
> complex things, so i suspect many participants at the IETF can actually
> pick up enough I18N expertise to be useful. I18N is not a dark art.

If a dark art is one that involves combinatorial degrees of complexity
mixed with human perception, judgment and emotion, then I fear that I18N
*is* a dark art. We can perhaps manage such complexity by limiting the
scope of what we try to do in our protocols, but I for one would very
much appreciate having an I18N directorate reviewing everything.

    Brian

v2.23.0 | Report a Bug | By Email