[apps-discuss] Non-English reading lists (was: Re: Request to publish draft-ietf-appsawg-rfc3536bis-02)

John C Klensin <john-ietf@jck.com> Fri, 10 June 2011 14:05 UTC

Return-Path: <john-ietf@jck.com>
X-Original-To: apps-discuss@ietfa.amsl.com
Delivered-To: apps-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 485B511E80CB for <apps-discuss@ietfa.amsl.com>; Fri, 10 Jun 2011 07:05:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cu1s6l-Rz6pW for <apps-discuss@ietfa.amsl.com>; Fri, 10 Jun 2011 07:05:52 -0700 (PDT)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by ietfa.amsl.com (Postfix) with ESMTP id 6FACE11E81B6 for <apps-discuss@ietf.org>; Fri, 10 Jun 2011 07:05:52 -0700 (PDT)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1QV2LO-000I56-Bp; Fri, 10 Jun 2011 10:05:50 -0400
Date: Fri, 10 Jun 2011 10:05:49 -0400
From: John C Klensin <john-ietf@jck.com>
To: Frank Ellermann <hmdmhdfmhdjmzdtjmzdtzktdkztdjz@gmail.com>
Message-ID: <5D92A844AC739C22A4525EAA@PST.JCK.COM>
In-Reply-To: <BANLkTik-PNUatvfDQGSqtJD0CHLwznCa1A@mail.gmail.com>
References: <BANLkTi=WCOORCipkW40gYHzaKUD7cR0CGg@mail.gmail.com> <BANLkTik-PNUatvfDQGSqtJD0CHLwznCa1A@mail.gmail.com>
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
Cc: Apps Discuss <apps-discuss@ietf.org>
Subject: [apps-discuss] Non-English reading lists (was: Re: Request to publish draft-ietf-appsawg-rfc3536bis-02)
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Jun 2011 14:05:53 -0000

--On Friday, June 10, 2011 15:32 +0200 Frank Ellermann
<hmdmhdfmhdjmzdtjmzdtzktdkztdjz@gmail.com> wrote:

> +1.  I'm still not convinced that a BCP with an international
> audience should contain a reading list for a mainly English
> audience, but hopefully we'll arrive at better solutions in
> future RFCs.

Frank,

A big problem, especially for a BCP or standards-track document,
is the question of evaluation of the references.  Using myself
as a handy example, I can read a few languages other than
English, but I absolutely do not know the internationalization
literature in those languages to be able to know what to
recommend (or even to evaluate a recommendation).  I know that
there are some materials in English that we did not list, not
because they were overlooked, but because they are pretty bad
(at least in my opinion or Paul's, but the WG Last Call didn't
turn up complaints about their omission).

But let me make a suggestion.   If you want to gather up some
people who could do (and that includes cross-checking and
evaluating) a reading list in one or more languages (I'd
recommend doing it in annotated bibliography form) or even a
multilingual thesaurus of i18n terminology, I'd assume that the
Independent Submission Editor would be included to publish such
a thing as relevant and useful to the community.  I can't speak
for the ISE, of course, but you could check first if you wanted
to go ahead with such an effort.  There would be some issues
about publication in other than English and publication in
page-layout (PS and/or PDF) form to capture the relevant
characters and not have to resort entirely to transliteration.
However, we've had PS-only RFCs in the past and the rules permit
them as special exceptions when justified.  And, while I haven't
asked him, I note that the Acting RSE is not a native speaker of
English and might be sympathetic to the goal.

     john