Re: [idn] punctuation

tedd <tedd@sperling.com> Thu, 24 February 2005 18:28 UTC

Received: from psg.com (mailnull@psg.com [147.28.0.62]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA26790 for <idn-archive@lists.ietf.org>; Thu, 24 Feb 2005 13:28:29 -0500 (EST)
Received: from majordom by psg.com with local (Exim 4.44 (FreeBSD)) id 1D4Ndf-000MeS-T2 for idn-data@psg.com; Thu, 24 Feb 2005 18:23:03 +0000
Received: from [207.115.57.43] (helo=ylpvm12.prodigy.net) by psg.com with esmtp (Exim 4.44 (FreeBSD)) id 1D4Ndd-000MeC-Sd for idn@ops.ietf.org; Thu, 24 Feb 2005 18:23:02 +0000
Received: from pimout7-ext.prodigy.net (pimout7-ext.prodigy.net [207.115.63.58]) by ylpvm12.prodigy.net (8.12.10 outbound/8.12.10) with ESMTP id j1OIMwxd020705 for <idn@ops.ietf.org>; Thu, 24 Feb 2005 13:22:59 -0500
X-ORBL: [69.208.249.149]
Received: from [192.168.0.101] (adsl-69-208-249-149.dsl.lgtpmi.ameritech.net [69.208.249.149]) by pimout7-ext.prodigy.net (8.12.10 milter /8.12.10) with ESMTP id j1OIMwMk183410 for <idn@ops.ietf.org>; Thu, 24 Feb 2005 13:22:59 -0500
Mime-Version: 1.0
Message-Id: <p06210202be43c3888991@[192.168.0.101]>
In-Reply-To: <421E0D0C.2000309@vanderpoel.org>
References: <421B8484.3070802@vanderpoel.org> <20050223072837.GA21463~@nicemice.net> <D872CCF059514053ECF8A198@scan.jck.com> <421D8411.9030006@vanderpoel.org> <p06210208be4390618c81@[192.168.0.101]> <421E0D0C.2000309@vanderpoel.org>
Date: Thu, 24 Feb 2005 13:22:57 -0500
To: idn@ops.ietf.org
From: tedd <tedd@sperling.com>
Subject: Re: [idn] punctuation
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-Spam-Checker-Version: SpamAssassin 3.0.1 (2004-10-22) on psg.com
X-Spam-Status: No, score=-2.4 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.0.1
Sender: owner-idn@ops.ietf.org
Precedence: bulk

>tedd wrote:
>>I believe that the "fruit-loop" solution would fall short of expectations.
>
>I wasn't talking about many colors. A character is either in the 
>user's set or not. So we only need 2 colors (if colors are used at 
>all). The user's set is typically derived from the browser 
>localization or HTTP Accept-Language preference setting.
>
>Erik

Erik:

I understand -- however:

First, I was addressing the idea of a colored url via a "tool-tip 
plug-in" type solution -- a multi-colored or two toned fruit loop -- 
it doesn't make any difference, it's the same idea.

Second, while the user's set is typically derived as you say, I 
imagine there will be users who will transcend those boundaries 
(i.e., multilingual). Considering such, whatever the solution, it 
will most likely "look" different for the same url and thus lose some 
of it's potency as an alert.

Third, I imagine there may even be concerns (i.e., companies, 
persons, organizations, sport groups, and even countries) who may 
want a fruit-loop domain with their specific colors. It might get 
that ridiculous or maybe this will be a new way to market domains. :-)

It's not a bad idea, just one that falls short of solving the 
problem. Sometimes adding partial solutions to a problem become part 
of the problem.

tedd
-- 
--------------------------------------------------------------------------------
http://sperling.com/