Archaic scripts

Martin Duerst duerst at
Mon May 12 10:02:43 CEST 2008

I recently bought a mobile phone, and I had to wait for an hour
or so for the code to be downloaded and installed. I don't think
I'll do that a second time, but it indicates that at least I got
the newest software package, and so will others. Given that mobile
phones are not stuff you keep for ages, and given that they are
usually made for certain markets (including the character input
software that comes with it), I'm not so worried about the
limitations of upgradability of mobile phones.
(your mileage may vary, but I think that's the general direction
for this kind of devices).

There may be other devices that live a lot longer, and are in a
central place so that they have to serve more than one user,
where actual upgradability or not matters a lot more.

Regards,     Martin.

At 05:36 08/05/10, Shawn Steele wrote:
>> There *is* a bright line between protocols that only support LDH- and
>> A-labels and those that support U-labels. For example, there is a
>> draft that aims to specify how things would be done in SMTP (with
>> U-labels). If a mobile phone manufacturer would like to burn the
>> program in ROM, they can have the mobile phone deal with LDH- and
>> A-labels only, leaving U-label translation to the software on the
>> mobile carrier's ("server") side.
>A labels don't help anyone, they're only interesting for lookup.  Real 
>humans need the U labels.  If a phone manufacturer really needed to be 
>independent of the version, they could send Unicode to the server and then 
>the server can do the mapping.
>IMO the name should only be converted to an A-label for resolution.  
>Normally it should be a Unicode name.
>- Shawn
>Idna-update mailing list
>Idna-update at

#-#-#  Martin J. Du"rst, Assoc. Professor, Aoyama Gakuin University
#-#-#       mailto:duerst at     

More information about the Idna-update mailing list