Being an international reseller, we adopted straight away at the time all the UTF-8 API specifications in order to allow our clients to write their names, cities, etc in a correct format in the registration (apart from hoping we would one day really sell international names).
Now we have lots of problems registering INFO domains since when one of our clients uses his profile (with extended characters) this is simply rejected by the API, I understand for having non-ASCII characters. Well if my client has an OpenSRS profile, supposedly valid for all domains comercialized by OpenSRS I don't really get why this problem is not solved some how by Tucows system itself. I can understand that if Afilias has been thick enough to think that only english speakers will be registering its domains, there is not much to do by OpenSRS, but I also think that some kind of alternative, suggestion, autoupdate function or character substitution system should be established for this cases. Our alternative is going to be having 2 different validation methods, forcing our clients to maintain two profiles one for infos, one for the rest and having to disable all bulk registrations that include both coms and infos. Any other suggestions for solving this will be of help. Thanks. Jose Luis Moya
