- Joined
- Sep 15, 2009
- Messages
- 3,481
- Reaction score
- 1,189
I don't understand the new concept behind IDN.IDN. It's supposedly so that the end user can type a domain in their native alphabet. This is to make it easier to type what they're looking for.
However, in Japanese if they were to type let's say Alcohol.Japan (ãé ãæ¥æ¬, osake.nippon) they would still need to switch their keyboard layout to enter the correct "dot" because in their alphabet the "dot" is that little circle thing and not a commonly seen period.
So, my question is I suppose, why type native, not native to create a dot and then native again?
It seems to me that IDN.IDN will be more difficult to type in Japanese (and I believe other Asian countries use this as well) rather than using the A-z alphabet since you don't need to switch keyboard layouts 2 times in order to type it.
Edit: Unless there is a browser update that converts that dot into a period...
However, in Japanese if they were to type let's say Alcohol.Japan (ãé ãæ¥æ¬, osake.nippon) they would still need to switch their keyboard layout to enter the correct "dot" because in their alphabet the "dot" is that little circle thing and not a commonly seen period.
So, my question is I suppose, why type native, not native to create a dot and then native again?
It seems to me that IDN.IDN will be more difficult to type in Japanese (and I believe other Asian countries use this as well) rather than using the A-z alphabet since you don't need to switch keyboard layouts 2 times in order to type it.
Edit: Unless there is a browser update that converts that dot into a period...
Last edited:
