From the Amsterdam TRAFFIC conference:
Well I had to laugh at this one ...
Sure, I'll buy some IDNs (Korean / Japanese / Chinese etc), BUT, can I list them for sale on your platform? No, WHADDYA MEAN NO! Anyway, I knew that which is why I moved a long time ago.
So it must be like splitting the atom to convert the DB to UTF-8? Right?
Cant take a DB dump and experiment?
Nevermind, I'm sure Tim is fairly comfortable and probably doesn't want to screw up his pension plan.
Let me start you down the road to the 'light':
<meta http-equiv="Content-Type" content="text/html; charset=utf-8"> = RIGHT
Rather than:
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> = WRONG
Yeah, I know it's 'difficult' and 'hard' and your 'DB' etc to make your platform IDN compatible but what do you know? Your competitors have managed to do it, YEARS ago.
Definitely hard to give up the ASCII blinkers, but if all you can see is straight ahead then you're gonna get smashed in the side by an IDN train.
Time to sort this shit out.
edit:
BTW, I'd rather not hear the company line as follows:
http://www.dnjournal.com/archive/lowdown/2009/dailyposts/06-04-09.htmSchumacher, as he has done at past shows, offered his current Buy, Sell and Hold recommendations for various domain extensions. His current Buy list includes .info, .us, major ccTLDS like Germany's .de and Italy's .it plus IDNs.
Well I had to laugh at this one ...
Sure, I'll buy some IDNs (Korean / Japanese / Chinese etc), BUT, can I list them for sale on your platform? No, WHADDYA MEAN NO! Anyway, I knew that which is why I moved a long time ago.
So it must be like splitting the atom to convert the DB to UTF-8? Right?
Cant take a DB dump and experiment?
Nevermind, I'm sure Tim is fairly comfortable and probably doesn't want to screw up his pension plan.
Let me start you down the road to the 'light':
<meta http-equiv="Content-Type" content="text/html; charset=utf-8"> = RIGHT
Rather than:
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> = WRONG
Yeah, I know it's 'difficult' and 'hard' and your 'DB' etc to make your platform IDN compatible but what do you know? Your competitors have managed to do it, YEARS ago.
Definitely hard to give up the ASCII blinkers, but if all you can see is straight ahead then you're gonna get smashed in the side by an IDN train.
Time to sort this shit out.
edit:
BTW, I'd rather not hear the company line as follows:
http://www.dnforum.com/f129/sedo-help-needed-urgent-2-thread-369157.html#post1718508Sedo does not support the sale of all IDNs through our marketplace.
Domains with non-Latin characters can be listed in your account and parked, but they cannot be sold through Sedo's online marketplace. This way of coding (UTF-8) allows for special character domains (e.g. domains in written Chinese, Arabic, Greek, Russian, etc).
IDNs containing Latin-based characters such as as á, é, Ã, ä, ö, etc. can be parked and sold with us.
Last edited: