John,
Ah I see now. Yes, there is leakage in Punycode now and will be for a
while. It is not nice but I couldnt think of any encoding which wont
leak. (UTF-8 will give you gibberish if client are not UTF-8 aware or
with the right fonts). Same arguments we have in IDN WG many years ago.
We
On 23-nov-03, at 12:47, James Seng wrote:
Yes, there is leakage in Punycode now and will be for a while. It is
not nice but I couldnt think of any encoding which wont leak. (UTF-8
will give you gibberish if client are not UTF-8 aware or with the
right fonts). Same arguments we have in IDN WG
James,
My apologies for being a bit cryptic -- I hoped people would
understand the issues well enough by now to get the point. The
difference between the design of --and hopes for-- IDNA and what
is happening is something the community needs to understand and
be better informed about. The
John,
JCK The design of Punycode was for machine-to-machine communication, as
JCK you point out. It was never really intended or expected to leak
JCK into use environments.
...
JCK Indeed, it was chosen, in preference to some other options, on the
JCK grounds that
JCK* it could be deployed
On 20-nov-03, at 4:05, James Seng wrote:
I think having the punycode form have no value on a name badge.
Punycode, as it is designed, is meant for machine-to-machine
communication.
So why don't we come up with a machine-to-human transliteration
mechanism? So if someone called (trouble with
JORDI PALET MARTINEZ wrote:
It should be RFID, cheaper, and easier, not only for the blue sheets.
How would RFID be cheaper than barcodes? Someday, maybe, but today the
tags are expensive--according to CNet, depending on volume, customers
can expect to pay 30 cents to $1 per radio tag. The
Dave Crocker wrote:
What I would suggest, if we do this, is writing the person's name
*twice*: once in their native character set, and once in a form that
an english-reader can read. The latter is an established interchange
architecture
I believe that was the intention in the proposal.
the IETF secretariat.
Regards,
Jordi
- Original Message -
From: Rosen, Brian [EMAIL PROTECTED]
To: 'JORDI PALET MARTINEZ' [EMAIL PROTECTED];
[EMAIL PROTECTED]
Sent: Wednesday, November 19, 2003 10:14 PM
Subject: RE: i18n name badges
Let's keep going.
I'd
On 19-nov-03, at 22:28, JORDI PALET MARTINEZ wrote:
It should be RFID, cheaper, and easier, not only for the blue sheets.
Wouldn't it be even cheaper if everyone who has a laptop with wireless
with them signs in on an electronic version of the blue sheets? This
just takes a few hours of
Iljitsch van Beijnum wrote:
On 19-nov-03, at 22:28, JORDI PALET MARTINEZ wrote:
It should be RFID, cheaper, and easier, not only for the blue sheets.
Wouldn't it be even cheaper if everyone who has a laptop with wireless
with them signs in on an electronic version of the blue sheets? This
just
There are going to be *at least* three desirable encodings of a person's
identity -- the 'natural' encoding in the preferred/native charset of the
person's name, some kind of phonetic-ASCII encoding that tells non-natives
how to pronounce the name, and the email/idna encoding[s] that folks would
Peter,
PSA Proposals for making email addresses fully internationalized were a hot
PSA topic in Minneapolis. I'd like to suggest a more modest reform: fully
PSA internationalized IETF name badges. IETF 59 might be a fine venue for
PSA rolling those out...
I think that enhanced character sets
--On Wednesday, November 19, 2003 09:03 -0800 Dave Crocker
[EMAIL PROTECTED] wrote:
Peter,
PSA Proposals for making email addresses fully
internationalized were a hot PSA topic in Minneapolis. I'd
like to suggest a more modest reform: fully PSA
internationalized IETF name badges. IETF 59
PROTECTED]
Sent: Wednesday, November 19, 2003 7:07 PM
Subject: Re: i18n name badges
--On Wednesday, November 19, 2003 09:03 -0800 Dave Crocker
[EMAIL PROTECTED] wrote:
Peter,
PSA Proposals for making email addresses fully
internationalized were a hot PSA topic in Minneapolis. I'd
--On Wednesday, November 19, 2003 11:15 -0800 Fred Baker
[EMAIL PROTECTED] wrote:
At 08:23 AM 11/19/2003, Peter Saint-Andre wrote:
Proposals for making email addresses fully internationalized
were a hot topic in Minneapolis. I'd like to suggest a more
modest reform: fully internationalized
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
JORDI PALET MARTINEZ wrote:
| Keith,
|
| I'm not sure if you are joking, but I think is an excellent idea ...
|
| A badge communication protocol ... if you start with the draft, I will
be happy to contribute !
|
bcp?
-BEGIN PGP SIGNATURE-
On 19-nov-03, at 18:03, Dave Crocker wrote:
I think that enhanced character sets is a perfect topic for having the
IETF eat its own dogfood. Just dealing with the details of the name
tags might well prove instructive to us, nevermind the basic
politeness
it offers to attendees.
Easy to say
: Wednesday, November 19, 2003 3:08 PM
To: [EMAIL PROTECTED]
Subject: Re: i18n name badges
Keith,
I'm not sure if you are joking, but I think is an excellent idea ...
A badge communication protocol ... if you start with the
draft, I will be happy to contribute !
Regards,
Jordi
.
Regards,
Jordi
- Original Message -
From: Rosen, Brian [EMAIL PROTECTED]
To: 'JORDI PALET MARTINEZ' [EMAIL PROTECTED]; [EMAIL PROTECTED]
Sent: Wednesday, November 19, 2003 10:14 PM
Subject: RE: i18n name badges
Let's keep going.
I'd contribute, say, $25, plus write some code
If we do this, it should be WE (the IETF engineers) that do it and NOT
another thing we request the secretariat to do. We should eat our own
dogfood by writing, testing and then GIVING an implementation that is
compatible with the current label making system to the secretariat.
It's probably not
Someone can complain about privacy issues, but I feel that is the same now whe
n the blue sheet is circulated, or the attendance list is in the web site, rig
ht ?
Count me as one of the complainants.
The big problem with RFID is that your identity is exposed at times
when you don't want it to
Fred,
FB What I would suggest, if we do this, is writing the person's name *twice*:
FB once in their native character set, and once in a form that an
FB english-reader can read. The latter is an established interchange architecture
I believe that was the intention in the proposal. List names
Proposals for making email addresses fully internationalized were a
hot topic in Minneapolis. I'd like to suggest a more modest reform:
fully internationalized IETF name badges. IETF 59 might be a fine
venue for rolling those out...
I'd love to see an Internet-Draft on the topic. For
I'm not sure if you are joking, but I think is an excellent idea ...
A badge communication protocol ... if you start with the draft, I will
be happy to contribute !
I'm working on lots of other things, and somehow I suspect that others
are more qualified than I am to get this rolling.
The
On Wed, 19 Nov 2003 14:44:09 PST, Ole J. Jacobsen said:
line printers any more, but you get the idea :-) [If anyone still
remembers how to make a line printer attached to an IBM 370 do this by
sending just the right sort of code, you get extra points].
The IBM 1403 printer (1200 lines per
I think having the punycode form have no value on a name badge.
Punycode, as it is designed, is meant for machine-to-machine communication.
But I like the idea of allowing participation to put their own native
names together with their ASCII version on the name badge especially for
the next
26 matches
Mail list logo
