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

[Simon Perreault <[e-mail]>]

On 2010-07-06 10:25, Daisuke Miyakawa wrote:
> One proposal I can do is that composer side are allowed (but not
> recommended) to use the format only when they cannot emit the word (like
> when users want to edit foreign friends name without an appropriate IME)
> but know codepoint for that characters.
> Receiver side MUST be able to decode \xNNNN to appropriate Unicode form.
> This is a kind of dirty compromise but there's no technical difficulty
> nor theoretically insufficiency. I suppose I can implement
> sender/receiver easily.

I think you are confusing encoding with how a particular implementation
renders the text.

It is perfectly fine for an implementation to render text as \xNNNN when
e.g. a font is unavailable.

It is also perfectly fine for an implementation to take \xNNNN as input.

But what goes on the wire is pure UTF-8. How it gets rendered or how it
is input by a user is completely irrelevant for the vCard data format.

Simon
-- 
NAT64/DNS64 open-source --> http://ecdysis.viagenie.ca
STUN/TURN server        --> http://numb.viagenie.ca
vCard 4.0               --> http://www.vcarddav.org