Re: [I18ndir] Writing direction
John C Klensin <john-ietf@jck.com> Tue, 17 May 2022 22:24 UTC
Return-Path: <john-ietf@jck.com>
X-Original-To: i18ndir@ietfa.amsl.com
Delivered-To: i18ndir@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4A002C15E6D9; Tue, 17 May 2022 15:24:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.898
X-Spam-Level:
X-Spam-Status: No, score=-6.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cF-mx3ejYSEI; Tue, 17 May 2022 15:24:05 -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 AC293C15E3FD; Tue, 17 May 2022 15:24:05 -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 1nr5bn-000Pyu-7B; Tue, 17 May 2022 18:24:03 -0400
Date: Tue, 17 May 2022 18:23:57 -0400
From: John C Klensin <john-ietf@jck.com>
To: Patrik Fältström <patrik@frobbit.se>
cc: i18ndir@ietf.org, art-ads@ietf.org
Message-ID: <F3072E6B0F1EF9E2951E4D3D@PSB>
In-Reply-To: <F6E64852-5CA0-432C-90D3-9DA7D3CCCE69@frobbit.se>
References: <4C4A249559BA1E86B17E53FE@PSB> <D59F50F7-A266-48F3-AA78-DA46023033BD@frobbit.se> <39F2CBAA1F19DB765CC59369@PSB> <F6E64852-5CA0-432C-90D3-9DA7D3CCCE69@frobbit.se>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
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/i18ndir/YyofLY_dYSL12J75r2lFv0v9-BY>
Subject: Re: [I18ndir] Writing direction
X-BeenThere: i18ndir@ietf.org
X-Mailman-Version: 2.1.34
Precedence: list
List-Id: Internationalization Directorate <i18ndir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/i18ndir>, <mailto:i18ndir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/i18ndir/>
List-Post: <mailto:i18ndir@ietf.org>
List-Help: <mailto:i18ndir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/i18ndir>, <mailto:i18ndir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 May 2022 22:24:10 -0000
--On Tuesday, May 17, 2022 23:15 +0200 Patrik Fältström <patrik@frobbit.se> wrote: > On 17 May 2022, at 16:06, John C Klensin wrote: > >> free text strings > > Ok, got it. That is a combination of three words that for me > is an approximation of "rat hole", or "can of worms". Perhaps "can of rats". The problem is that we've got WGs and others trying to design protocols who have concluded they need such strings, need them in contexts that don't lend themselves to markup, and need them to be visible to the user. In one way or another, they look to us and say "hey, i18n folks, you told us that 'Just use UTF-8' isn't good enough and we need to specify both language and direction. But there is barely any place to put language and no place to put direction. What do you suggest we do?" Probably we need to try to answer the question and, at least so far, a directionality extension to the BCP47 code system is the least horrible possible answer I've been able to come up with, the need to climb in and have a close encounter with those rats notwithstanding. john
- [I18ndir] Writing direction John C Klensin
- Re: [I18ndir] Writing direction Asmus Freytag
- Re: [I18ndir] Writing direction John C Klensin
- Re: [I18ndir] Writing direction Asmus Freytag
- Re: [I18ndir] Writing direction John C Klensin
- Re: [I18ndir] Writing direction Asmus Freytag
- Re: [I18ndir] Writing direction Patrik Fältström
- Re: [I18ndir] Writing direction Martin J. Dürst
- Re: [I18ndir] Writing direction John C Klensin
- Re: [I18ndir] Writing direction John C Klensin
- Re: [I18ndir] Writing direction Asmus Freytag
- Re: [I18ndir] Writing direction Patrik Fältström
- Re: [I18ndir] Writing direction John C Klensin
- Re: [I18ndir] Writing direction John C Klensin
- Re: [I18ndir] Writing direction Asmus Freytag
- Re: [I18ndir] Writing direction Patrik Fältström
- Re: [I18ndir] Writing direction Patrik Fältström
- Re: [I18ndir] Writing direction Asmus Freytag
- Re: [I18ndir] Writing direction Martin J. Dürst
- Re: [I18ndir] Writing direction John C Klensin