Unicode/Punycode Pair

[andre]

I stumbled upon http://㯙㯜㯙㯟.net which is owned by http://www.boethin.net

If you have clicked on the link you will see an IDN converter.

There is though something interesting going on that is less obvious. 㯙㯜㯙㯟 is the unicode form of the punycode xn--domain. The chars 㯙㯜㯙㯟 are in Unicode CJK Unified Ideographs Ext A. These are uncommon chars and the online dictionaries I have tried do not have definitions for them.

Therefore the Unicode/Punycode Pair 㯙㯜㯙㯟/xn--domain does not have evident meaning for Unicode but has evident meaning for Punycode.

So that had me thinking whether or not there are any Perfect Unicode/Punycode Pairs which have evident and related meanings in both Unicode and Punycode.

Well I believe I have found one such Perfect Pair: 毁/xn--row

毁 = to destroy / to damage / to ruin / to defame / to slander
xn--row (as in quarrel)

:)

André 小山 Schappo

[Drewbert]

You need to get yourself a hobby! :)

[Avtal]

You need to get yourself a hobby! :)

IDNs are by far the most expensive hobby I have ever had.

Avtal

P.S. Thanks, André, for the updates on new IDN gTLDs. Hope to see the .com IDN gTLDs announced someday.

[123]

never thought about idns that way.

http://㼮㼩㼻㼲㼶㼸㼦.com

[Rubber Duck]

This kind of side show only normally gets attention when the main event has sold out.:rolleyes:

[andre]

http://㼮㼩㼻㼲㼶㼸㼦.com

㼮㼩㼻㼲㼶㼸㼦/xn--idnforums : An Imperfect Pair :)

André 小山 Schappo

[andre]

This is not just a mind game because a Perfect Pair would add value to an IDN.

Now I do not know how many Perfect Pairs there are, though with each release of Unicode containing new characters there is the potential for new Perfect Pairs.

For years now we have been hoping for proper Unicode display of IDNs and the situation has certainly improved. There are still though agents that display punycode form. Browsers will display punycode form if the IDN is not whitelisted.

A Perfect Pair gives the big advantage that whether the agent displays the IDN in unicode or punycode form, the user will still see a readable and meaningful and relevant Domain Name.

André 小山 Schappo

[mgrohan]

A Perfect Pair gives the big advantage that whether the agent displays the IDN in unicode or punycode form, the user will still see a readable and meaningful and relevant Domain Name.

But not readable because it is in English, a different language to the IDN and against the whole idea of IDNs in the first place of having the domain name not in English?! :confused::confused::confused:

[Rubber Duck]

But not readable because it is in English, a different language to the IDN and against the whole idea of IDNs in the first place of having the domain name not in English?! :confused::confused::confused:

If there is any advantage at all it is going to be miniscule.

The real problem, however, is the huge compromise on the IDN keyword and possibly purchase price you would likely have to make in order to achieve something really insiginificant.

[bwhhisc]

IDNs are by far the most expensive hobby I have ever had.
Avtal



:lol:

[andre]

But not readable because it is in English, a different language to the IDN and against the whole idea of IDNs in the first place of having the domain name not in English?! :confused::confused::confused:

Actually maybe I did not have a Perfect Pair after all because the example I gave was -

毁/xn--row
Chinese Character/English

A Perfect Pair for Mandarin Chinese would be

Chinese Character(s)/Pinyin

where Pinyin is a standard romanisation of Mandarin Chinese

Many languages have a romanised form

André 小山 Schappo

[Drewbert]

Here's a perfect pair for you...

http://xn--ykda.com

[andre]

Here's a perfect pair for you...

http://xn--ykda.com

:yes:

Once I saw the site I thought I must whitelist myanmar/burmese in chrome but it does not appear in the list of languages in chrome:no:

André 小山 Schappo