Re: [VCARDDAV] Questions about text handling in vCard 4.0 (rev 11)

Simon Perreault <> Tue, 06 July 2010 13:48 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 55ED73A691B for <>; Tue, 6 Jul 2010 06:48:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -0.555
X-Spam-Status: No, score=-0.555 tagged_above=-999 required=5 tests=[AWL=0.555, BAYES_05=-1.11, NO_RELAYS=-0.001]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id f760DQbsVwQG for <>; Tue, 6 Jul 2010 06:48:08 -0700 (PDT)
Received: from ( [IPv6:2620:0:230:8000::2]) by (Postfix) with ESMTP id 458833A6838 for <>; Tue, 6 Jul 2010 06:48:08 -0700 (PDT)
Received: from (unknown [IPv6:2620:0:230:c000:b1db:5a25:9ab9:89d9]) by (Postfix) with ESMTPSA id 46B5D20CC0; Tue, 6 Jul 2010 09:48:09 -0400 (EDT)
Message-ID: <>
Date: Tue, 06 Jul 2010 09:46:12 -0400
From: Simon Perreault <>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv: Gecko/20100430 Fedora/3.0.4-2.fc12 Thunderbird/3.0.4
MIME-Version: 1.0
To: Daisuke Miyakawa <>
References: <> <> <> <> <>
In-Reply-To: <>
X-Enigmail-Version: 1.0.1
Content-Type: text/plain; charset="ISO-2022-JP"
Content-Transfer-Encoding: 7bit
Subject: Re: [VCARDDAV] Questions about text handling in vCard 4.0 (rev 11)
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF vcarddav wg mailing list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 06 Jul 2010 13:48:09 -0000

On 2010-07-06 00:53, Daisuke Miyakawa wrote:
>     Can you please suggest text for what you have in mind? Probably a
>     sentence or two to be added at the end of 3.3...?
> Here's an arbitrary example.

I meant text that we should add to the vCard 4 specification and that
would address your concern...

> The problem here is we cannot estimate potential Unicode which harm
> actual readability/edit-ability/xxx-ability caused by receiver/editor
> side's limitation. Even readability is part of my concern.

What we're talking about here is how Unicode characters get encoded in
vCard. The current method is to encode them as-is. You are suggesting to
use \xNNNN, and your argument is readability. I think this argument is
weak because:

- Unicode characters may actually be *more* readable than \xNNNN notation.
- Do we really care about readability of vCard data that is going to be
displayed exactly the same to the user regardless of the encoding?

> Another example: a final fallback method users will use during reading
> and editing vCard would be just opening the file and editing it
> manually. Then how can they edit unknown characters like Chinese,
> Japanese, Korean, V...?

I don't see a problem. What do you mean by "unknown"? I can just use vi
on any UTF-8 file and edit it without any difficulty. One can do the
same with Microsoft Word or any other editor that understands UTF-8 I
would assume.

NAT64/DNS64 open-source -->
STUN/TURN server        -->
vCard 4.0               -->