Re: [weirds] Internationalization Issues
Byron Ellacott <bje@apnic.net> Mon, 22 October 2012 00:56 UTC
Return-Path: <bje@apnic.net>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D6E2521F8900 for <weirds@ietfa.amsl.com>; Sun, 21 Oct 2012 17:56:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
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 4gL2S-H3Jfir for <weirds@ietfa.amsl.com>; Sun, 21 Oct 2012 17:56:26 -0700 (PDT)
Received: from asmtp.apnic.net (asmtp.apnic.net [IPv6:2001:dc0:2001:11::199]) by ietfa.amsl.com (Postfix) with ESMTP id 2A78C21F872E for <weirds@ietf.org>; Sun, 21 Oct 2012 17:56:26 -0700 (PDT)
Received: from [IPv6:2001:dc0:a000:4:3959:ce4b:634:a7b2] (unknown [IPv6:2001:dc0:a000:4:3959:ce4b:634:a7b2]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by asmtp.apnic.net (Postfix) with ESMTP id EEC37B6894; Mon, 22 Oct 2012 10:56:23 +1000 (EST)
Content-Type: multipart/signed; boundary="Apple-Mail=_4457E471-5869-492B-8C48-77ABF8414F5D"; protocol="application/pkcs7-signature"; micalg="sha1"
Mime-Version: 1.0 (Mac OS X Mail 6.1 \(1498\))
From: Byron Ellacott <bje@apnic.net>
In-Reply-To: <CCA6B194.DE13%andy@arin.net>
Date: Mon, 22 Oct 2012 10:56:23 +1000
Message-Id: <6C6109C6-0FA3-40A0-9562-A8F55F178003@apnic.net>
References: <CCA6B194.DE13%andy@arin.net>
To: Andy Newton <andy@arin.net>
X-Mailer: Apple Mail (2.1498)
Cc: "weirds@ietf.org" <weirds@ietf.org>
Subject: Re: [weirds] Internationalization Issues
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Oct 2012 00:56:27 -0000
On 19/10/2012, at 9:33 PM, Andy Newton <andy@arin.net> wrote: > On 10/18/12 8:40 PM, "Byron Ellacott" <bje@apnic.net> wrote: > >> Indicate to the end user that it's not a native language? >> Auto-translate? Murray has the right sense of what I meant, for both of these. >> Negotiate for native language with Accepts-Language, if indicated as >> possible via a Vary header? > > That's HTTP layer stuff. We're talking about embedding multiple language > tags in the response. Are we? I thought draft-sheng-weirds-icann-rws-dnrd-01 sect. 7.3 suggested a single language tag for the entire response, with "possible considerations" of multiple language tags. But, with this point, what I'm suggesting is that the user of a particular client likely has one or a few preferred languages, which they could potentially indicate to the server, in the event that the server has multiple translations. This would be applicable for mixed language responses as well as single language responses, since it only indicates a client preference, not a strict requirement. My primary perspective on this entire subject is that whatever mechanisms or systems indicate language or language preference need to be optional, and should support reasonable use cases for current or likely future operators. I think there's a use case for language preference indication, as per below, and I think Ning is suggesting a use case for tagging the language of an entire response, inline in the response. What are your (collective "your") thoughts on how reasonable these use cases are? >> Some RDAP services will not support multiple languages meaningfully, but >> there are existing whois services that provide (non-standard, varying) >> ways to indicate a preferred language on query, with multiple language >> options available for many response fields. > > Can you provide an example of one of these services so we can query it? > That would go a long way in helping shape this need, I would think. Are > there registries that collect contact data in multiple languages? $ whois -h whois.nic.ad.jp -- 'NET 113.32.19.157' $ whois -h whois.nic.ad.jp -- 'NET 113.32.19.157 /e' $ whois -h whois.jprs.jp -- 'jprs.jp' $ whois -h whois.jprs.jp -- 'jprs.jp /e' The data labels are sometimes translated, sometimes not. In the native language responses, there's often an English translation. JPRS includes an English help/info block even for the native language response. I don't know for sure if they collect the information in multiple languages, though I think they do - any JPRS or JPNIC operators on the list to confirm? Character set is ISO-2022-JP. I don't know if there are other services with such a switch mechanism, either - we're all aware of how hard it is to find out what's actually done out there on port 43 :-) - but for another comparison whois.kisa.kr returns both native and english output, at least for "kisa.kr". Character set is EUC-KR. Byron
- Re: [weirds] Internationalization Issues John Levine
- [weirds] Internationalization Issues Ning Kong
- Re: [weirds] Internationalization Issues Andy Newton
- Re: [weirds] Internationalization Issues Byron Ellacott
- Re: [weirds] Internationalization Issues Andy Newton
- Re: [weirds] Internationalization Issues Murray S. Kucherawy
- Re: [weirds] Internationalization Issues Byron Ellacott
- Re: [weirds] Internationalization Issues Peter Koch
- Re: [weirds] Internationalization Issues Byron Ellacott
- Re: [weirds] Internationalization Issues Peter Koch
- Re: [weirds] Internationalization Issues Byron Ellacott
- Re: [weirds] Internationalization Issues Andy Newton
- Re: [weirds] Internationalization Issues Andy Newton
- Re: [weirds] Internationalization Issues Steve Sheng
- Re: [weirds] Internationalization Issues Byron Ellacott
- Re: [weirds] Internationalization Issues James Mitchell
- Re: [weirds] Internationalization Issues Kentaro Mori
- Re: [weirds] Internationalization Issues MasaYUKI Okada
- Re: [weirds] Internationalization Issues Byron Ellacott
- Re: [weirds] Internationalization Issues Kentaro Mori
- Re: [weirds] Internationalization Issues MasaYUKI Okada
- Re: [weirds] Internationalization Issues Ning Kong
- Re: [weirds] Internationalization Issues Olaf Kolkman
- Re: [weirds] Internationalization Issues Edward Lewis
- Re: [weirds] Internationalization Issues SM
- Re: [weirds] Internationalization Issues Hollenbeck, Scott
- Re: [weirds] Internationalization Issues Edward Lewis
- Re: [weirds] Internationalization Issues SM
- Re: [weirds] Internationalization Issues Edward Lewis
- Re: [weirds] Internationalization Issues Byron Ellacott
- Re: [weirds] Internationalization Issues Andy Newton
- Re: [weirds] Internationalization Issues Edward Lewis
- Re: [weirds] Internationalization Issues John Levine
- Re: [weirds] Internationalization Issues Edward Lewis
- Re: [weirds] Internationalization Issues John R Levine
- Re: [weirds] Internationalization Issues Francisco Obispo
- Re: [weirds] Internationalization Issues Francisco Obispo
- Re: [weirds] Internationalization Issues Edward Lewis
- Re: [weirds] Internationalization Issues Ning Kong
- Re: [weirds] Internationalization Issues Linlin Zhou
- Re: [weirds] Internationalization Issues Linlin Zhou
- Re: [weirds] Internationalization Issues Andrew Sullivan
- Re: [weirds] Internationalization Issues John Levine
- Re: [weirds] Internationalization Issues Andrew Sullivan
- Re: [weirds] Internationalization Issues Byron Ellacott