how to solve the problems of Cyrillic domain name without using punycode?

Comments

jcfiala’s picture

I don't know. What are the problems of Cyrillic domain names?

mailfox’s picture

Mixologic’s picture

Issue tags: +IDN
dqd’s picture

Version: 6.x-2.9 » 6.x-2.x-dev
Component: Miscellaneous » Code
Issue tags: -punycode

#1 the question was

What are the problems of Cyrillic domain names?

Showing an URL example doesn't answer the quesion. Please provide more info about what you want to have implemented and how. And I would like to suggest that we only push changes to latest development snapshots in case of link module 6.x feature requests.

(INFO: Yes, I think IDN is the better tag here. Punycode is not a good collector and splits the issues too much. I would like to remove punycode and keep IDN in if it is ok.)

dqd’s picture

Status: Active » Postponed (maintainer needs more info)
Mixologic’s picture

I was tagging IDN related issues with IDN. The OP's request, "without using punycode" is a little difficult to achieve, as that is pretty much the only way that unicode characters are handled in domain names. It's implemented in browsers, as well as in the DNS system.

IDN *should* be part of core, which is why I've tagged this issue - to show how much need there is in core and contrib to handle valid domain names properly.

dqd’s picture

Mixologic: That's fine. That's why I sad that I think your IDN tag is the better tag here. And that's why I kept it in as long as no others have other points of view on this later. But I removed punycode because it only bundles two issues, and one of them is this one. That's why I removed it (punycode) and informed about it.

DamienMcKenna’s picture

Status: Postponed (maintainer needs more info) » Closed (won't fix)

Thank you all for your efforts, but I'm sorry to say that the D6 version is no longer supported.