IDNA / punycode for Zinc?
Hi (Sven), Zinc canât currently handle unicode domain names (e.g. http://üni.ch <http://xn--ni-wka.ch/>). Are there any plans to implement punycode / IDNA conversion for Zinc? Or is there an explicit reason not to support it? I see that #parseHostPort: expects the host portion to be percent escaped, what is the use case for this? I have never seen a percent escaped host portion. Usually the host portion is either pure ASCII, unicode or punycode (in my experience at least). Just curious, as I just added IDNA conversion to one of our applications (I just let python perform the conversion: https://docs.python.org/2/library/codecs.html#module-encodings.idna <https://docs.python.org/2/library/codecs.html#module-encodings.idna>). Cheers, Max
Max,
On 23 Nov 2016, at 14:34, Max Leske <maxleske@gmail.com> wrote:
Hi (Sven),
Zinc canât currently handle unicode domain names (e.g. http://üni.ch). Are there any plans to implement punycode / IDNA conversion for Zinc? Or is there an explicit reason not to support it? I see that #parseHostPort: expects the host portion to be percent escaped, what is the use case for this? I have never seen a percent escaped host portion. Usually the host portion is either pure ASCII, unicode or punycode (in my experience at least).
Just curious, as I just added IDNA conversion to one of our applications (I just let python perform the conversion: https://docs.python.org/2/library/codecs.html#module-encodings.idna).
Cheers, Max
Yes, that would be nice to have. Just for future reference, we are talking about the following (IDN(A)): https://en.wikipedia.org/wiki/Internationalized_domain_name https://en.wikipedia.org/wiki/Punycode https://tools.ietf.org/html/rfc3490 https://www.charset.org/punycode Normal DNS hostnames are ASCII only (or used to be like that anyway), that is why it is (currently) implemented like that. Sven
Great! Thereâs a punycode implementation on smalltalkhub (http://smalltalkhub.com/#!/~dTriangle/Punycode <http://smalltalkhub.com/#!/~dTriangle/Punycode>) but it needs some polishing. Should I open an issue on FogBugz so we donât forget? Max
On 23 Nov 2016, at 15:00, Sven Van Caekenberghe <sven@stfx.eu> wrote:
Max,
On 23 Nov 2016, at 14:34, Max Leske <maxleske@gmail.com> wrote:
Hi (Sven),
Zinc canât currently handle unicode domain names (e.g. http://üni.ch). Are there any plans to implement punycode / IDNA conversion for Zinc? Or is there an explicit reason not to support it? I see that #parseHostPort: expects the host portion to be percent escaped, what is the use case for this? I have never seen a percent escaped host portion. Usually the host portion is either pure ASCII, unicode or punycode (in my experience at least).
Just curious, as I just added IDNA conversion to one of our applications (I just let python perform the conversion: https://docs.python.org/2/library/codecs.html#module-encodings.idna).
Cheers, Max
Yes, that would be nice to have.
Just for future reference, we are talking about the following (IDN(A)):
https://en.wikipedia.org/wiki/Internationalized_domain_name https://en.wikipedia.org/wiki/Punycode https://tools.ietf.org/html/rfc3490 https://www.charset.org/punycode
Normal DNS hostnames are ASCII only (or used to be like that anyway), that is why it is (currently) implemented like that.
Sven
On 23 Nov 2016, at 15:36, Max Leske <maxleske@gmail.com> wrote:
Great!
Thereâs a punycode implementation on smalltalkhub (http://smalltalkhub.com/#!/~dTriangle/Punycode) but it needs some polishing.
Wow, that looks good, it even has ZnUrl integration, so we're done ;-) There are no tests though. How come we never heard of this ? Last commit was in 2013, hopefully the author is still around.
Should I open an issue on FogBugz so we donât forget?
Yes, OK.
Max
On 23 Nov 2016, at 15:00, Sven Van Caekenberghe <sven@stfx.eu> wrote:
Max,
On 23 Nov 2016, at 14:34, Max Leske <maxleske@gmail.com> wrote:
Hi (Sven),
Zinc canât currently handle unicode domain names (e.g. http://üni.ch). Are there any plans to implement punycode / IDNA conversion for Zinc? Or is there an explicit reason not to support it? I see that #parseHostPort: expects the host portion to be percent escaped, what is the use case for this? I have never seen a percent escaped host portion. Usually the host portion is either pure ASCII, unicode or punycode (in my experience at least).
Just curious, as I just added IDNA conversion to one of our applications (I just let python perform the conversion: https://docs.python.org/2/library/codecs.html#module-encodings.idna).
Cheers, Max
Yes, that would be nice to have.
Just for future reference, we are talking about the following (IDN(A)):
https://en.wikipedia.org/wiki/Internationalized_domain_name https://en.wikipedia.org/wiki/Punycode https://tools.ietf.org/html/rfc3490 https://www.charset.org/punycode
Normal DNS hostnames are ASCII only (or used to be like that anyway), that is why it is (currently) implemented like that.
Sven
https://pharo.fogbugz.com/f/cases/19383/IDNA-punycode-for-Zinc After loading Name: Punycode-dTriangle.8 Author: dTriangle Time: 26 August 2013, 10:19:11.728 am UUID: 6493a3ee-43bb-44f0-86a8-5aa47a9b42ff Ancestors: Punycode-dTriangle.7 I can do the following 'http://üni.ch' asUrl. "http://xn--ni-wka.ch/" 'http://üni.ch' asUrl retrieveContents includesSubstring: 'Ãni'. "true" Done ;-) Thank you, https://twitter.com/osashimitabenai, well done ! Sven
On 23 Nov 2016, at 15:43, Sven Van Caekenberghe <sven@stfx.eu> wrote:
On 23 Nov 2016, at 15:36, Max Leske <maxleske@gmail.com> wrote:
Great!
Thereâs a punycode implementation on smalltalkhub (http://smalltalkhub.com/#!/~dTriangle/Punycode) but it needs some polishing.
Wow, that looks good, it even has ZnUrl integration, so we're done ;-)
There are no tests though.
How come we never heard of this ?
Last commit was in 2013, hopefully the author is still around.
Should I open an issue on FogBugz so we donât forget?
Yes, OK.
Max
On 23 Nov 2016, at 15:00, Sven Van Caekenberghe <sven@stfx.eu> wrote:
Max,
On 23 Nov 2016, at 14:34, Max Leske <maxleske@gmail.com> wrote:
Hi (Sven),
Zinc canât currently handle unicode domain names (e.g. http://üni.ch). Are there any plans to implement punycode / IDNA conversion for Zinc? Or is there an explicit reason not to support it? I see that #parseHostPort: expects the host portion to be percent escaped, what is the use case for this? I have never seen a percent escaped host portion. Usually the host portion is either pure ASCII, unicode or punycode (in my experience at least).
Just curious, as I just added IDNA conversion to one of our applications (I just let python perform the conversion: https://docs.python.org/2/library/codecs.html#module-encodings.idna).
Cheers, Max
Yes, that would be nice to have.
Just for future reference, we are talking about the following (IDN(A)):
https://en.wikipedia.org/wiki/Internationalized_domain_name https://en.wikipedia.org/wiki/Punycode https://tools.ietf.org/html/rfc3490 https://www.charset.org/punycode
Normal DNS hostnames are ASCII only (or used to be like that anyway), that is why it is (currently) implemented like that.
Sven
:) Nice.
On 23 Nov 2016, at 16:51, Sven Van Caekenberghe <sven@stfx.eu> wrote:
https://pharo.fogbugz.com/f/cases/19383/IDNA-punycode-for-Zinc
After loading
Name: Punycode-dTriangle.8 Author: dTriangle Time: 26 August 2013, 10:19:11.728 am UUID: 6493a3ee-43bb-44f0-86a8-5aa47a9b42ff Ancestors: Punycode-dTriangle.7
I can do the following
'http://üni.ch' asUrl.
'http://üni.ch' asUrl retrieveContents includesSubstring: 'Ãni'.
"true"
Done ;-)
Thank you, https://twitter.com/osashimitabenai, well done !
Sven
On 23 Nov 2016, at 15:43, Sven Van Caekenberghe <sven@stfx.eu> wrote:
On 23 Nov 2016, at 15:36, Max Leske <maxleske@gmail.com> wrote:
Great!
Thereâs a punycode implementation on smalltalkhub (http://smalltalkhub.com/#!/~dTriangle/Punycode) but it needs some polishing.
Wow, that looks good, it even has ZnUrl integration, so we're done ;-)
There are no tests though.
How come we never heard of this ?
Last commit was in 2013, hopefully the author is still around.
Should I open an issue on FogBugz so we donât forget?
Yes, OK.
Max
On 23 Nov 2016, at 15:00, Sven Van Caekenberghe <sven@stfx.eu> wrote:
Max,
On 23 Nov 2016, at 14:34, Max Leske <maxleske@gmail.com> wrote:
Hi (Sven),
Zinc canât currently handle unicode domain names (e.g. http://üni.ch). Are there any plans to implement punycode / IDNA conversion for Zinc? Or is there an explicit reason not to support it? I see that #parseHostPort: expects the host portion to be percent escaped, what is the use case for this? I have never seen a percent escaped host portion. Usually the host portion is either pure ASCII, unicode or punycode (in my experience at least).
Just curious, as I just added IDNA conversion to one of our applications (I just let python perform the conversion: https://docs.python.org/2/library/codecs.html#module-encodings.idna).
Cheers, Max
Yes, that would be nice to have.
Just for future reference, we are talking about the following (IDN(A)):
https://en.wikipedia.org/wiki/Internationalized_domain_name https://en.wikipedia.org/wiki/Punycode https://tools.ietf.org/html/rfc3490 https://www.charset.org/punycode
Normal DNS hostnames are ASCII only (or used to be like that anyway), that is why it is (currently) implemented like that.
Sven
I am always amazed about the cool things I can learn from this list. Phil On Wed, Nov 23, 2016 at 4:59 PM, Max Leske <maxleske@gmail.com> wrote:
:) Nice.
On 23 Nov 2016, at 16:51, Sven Van Caekenberghe <sven@stfx.eu> wrote:
https://pharo.fogbugz.com/f/cases/19383/IDNA-punycode-for-Zinc
After loading
Name: Punycode-dTriangle.8 Author: dTriangle Time: 26 August 2013, 10:19:11.728 am UUID: 6493a3ee-43bb-44f0-86a8-5aa47a9b42ff Ancestors: Punycode-dTriangle.7
I can do the following
'http://üni.ch <http://xn--ni-wka.ch>' asUrl.
'http://üni.ch <http://xn--ni-wka.ch>' asUrl retrieveContents includesSubstring: 'Ãni'.
"true"
Done ;-)
Thank you, https://twitter.com/osashimitabenai, well done !
Sven
On 23 Nov 2016, at 15:43, Sven Van Caekenberghe <sven@stfx.eu> wrote:
On 23 Nov 2016, at 15:36, Max Leske <maxleske@gmail.com> wrote:
Great!
Thereâs a punycode implementation on smalltalkhub ( http://smalltalkhub.com/#!/~dTriangle/Punycode) but it needs some polishing.
Wow, that looks good, it even has ZnUrl integration, so we're done ;-)
There are no tests though.
How come we never heard of this ?
Last commit was in 2013, hopefully the author is still around.
Should I open an issue on FogBugz so we donât forget?
Yes, OK.
Max
On 23 Nov 2016, at 15:00, Sven Van Caekenberghe <sven@stfx.eu> wrote:
Max,
On 23 Nov 2016, at 14:34, Max Leske <maxleske@gmail.com> wrote:
Hi (Sven),
Zinc canât currently handle unicode domain names (e.g. http://üni.ch <http://xn--ni-wka.ch>). Are there any plans to implement punycode / IDNA conversion for Zinc? Or is there an explicit reason not to support it? I see that # parseHostPort: expects the host portion to be percent escaped, what is the use case for this? I have never seen a percent escaped host portion. Usually the host portion is either pure ASCII, unicode or punycode (in my experience at least).
Just curious, as I just added IDNA conversion to one of our applications (I just let python perform the conversion: https://docs.python.org/2/library/codecs.html#module-encodings.idna).
Cheers, Max
Yes, that would be nice to have.
Just for future reference, we are talking about the following (IDN(A)):
https://en.wikipedia.org/wiki/Internationalized_domain_name https://en.wikipedia.org/wiki/Punycode https://tools.ietf.org/html/rfc3490 https://www.charset.org/punycode
Normal DNS hostnames are ASCII only (or used to be like that anyway), that is why it is (currently) implemented like that.
Sven
Hi I wrote PunycodeConverter. I received a mail from Sven. But I overlooked. I already sent a mail to Seven. Please use my code. But it need to kaizen. http://smalltalkhub.com/#!/~dTriangle/Punycode On 2016å¹´11æ24æ¥ at 4:14:16, phil@highoctane.be (phil@highoctane.be) wrote: I am always amazed about the cool things I can learn from this list. Phil On Wed, Nov 23, 2016 at 4:59 PM, Max Leske <maxleske@gmail.com> wrote: :) Nice.
On 23 Nov 2016, at 16:51, Sven Van Caekenberghe <sven@stfx.eu> wrote:
https://pharo.fogbugz.com/f/cases/19383/IDNA-punycode-for-Zinc
After loading
Name: Punycode-dTriangle.8 Author: dTriangle Time: 26 August 2013, 10:19:11.728 am UUID: 6493a3ee-43bb-44f0-86a8-5aa47a9b42ff Ancestors: Punycode-dTriangle.7
I can do the following
'http://üni.ch' asUrl.
'http://üni.ch' asUrl retrieveContents includesSubstring: 'Ãni'.
"true"
Done ;-)
Thank you, https://twitter.com/osashimitabenai, well done !
Sven
On 23 Nov 2016, at 15:43, Sven Van Caekenberghe <sven@stfx.eu> wrote:
On 23 Nov 2016, at 15:36, Max Leske <maxleske@gmail.com> wrote:
Great!
Thereâs a punycode implementation on smalltalkhub (http://smalltalkhub.com/#!/~dTriangle/Punycode) but it needs some polishing.
Wow, that looks good, it even has ZnUrl integration, so we're done ;-)
There are no tests though.
How come we never heard of this ?
Last commit was in 2013, hopefully the author is still around.
Should I open an issue on FogBugz so we donât forget?
Yes, OK.
Max
On 23 Nov 2016, at 15:00, Sven Van Caekenberghe <sven@stfx.eu> wrote:
Max,
On 23 Nov 2016, at 14:34, Max Leske <maxleske@gmail.com> wrote:
Hi (Sven),
Zinc canât currently handle unicode domain names (e.g. http://üni.ch). Are there any plans to implement punycode / IDNA conversion for Zinc? Or is there an explicit reason not to support it? I see that # parseHostPort: expects the host portion to be percent escaped, what is the use case for this? I have never seen a percent escaped host portion. Usually the host portion is either pure ASCII, unicode or punycode (in my experience at least).
Just curious, as I just added IDNA conversion to one of our applications (I just let python perform the conversion: https://docs.python.org/2/library/codecs.html#module-encodings.idna).
Cheers, Max
Yes, that would be nice to have.
Just for future reference, we are talking about the following (IDN(A)):
https://en.wikipedia.org/wiki/Internationalized_domain_name https://en.wikipedia.org/wiki/Punycode https://tools.ietf.org/html/rfc3490 https://www.charset.org/punycode
Normal DNS hostnames are ASCII only (or used to be like that anyway), that is why it is (currently) implemented like that.
Sven
Thanks Yoshihiko, nice work.
On 27 Dec 2016, at 16:32, Yoshihiko Kubota <y.kubota@mail.dendai.ac.jp> wrote:
Hi
I wrote PunycodeConverter. I received a mail from Sven. But I overlooked. I already sent a mail to Seven. Please use my code. But it need to kaizen.
http://smalltalkhub.com/#!/~dTriangle/Punycode <http://smalltalkhub.com/#!/~dTriangle/Punycode> On 2016å¹´11æ24æ¥ at 4:14:16, phil@highoctane.be (phil@highoctane.be <mailto:phil@highoctane.be>) wrote:
I am always amazed about the cool things I can learn from this list.
Phil
On Wed, Nov 23, 2016 at 4:59 PM, Max Leske <maxleske@gmail.com <mailto:maxleske@gmail.com>> wrote: :) Nice.
On 23 Nov 2016, at 16:51, Sven Van Caekenberghe <sven@stfx.eu <mailto:sven@stfx.eu>> wrote:
https://pharo.fogbugz.com/f/cases/19383/IDNA-punycode-for-Zinc <https://pharo.fogbugz.com/f/cases/19383/IDNA-punycode-for-Zinc>
After loading
Name: Punycode-dTriangle.8 Author: dTriangle Time: 26 August 2013, 10:19:11.728 am UUID: 6493a3ee-43bb-44f0-86a8-5aa47a9b42ff Ancestors: Punycode-dTriangle.7
I can do the following
'http://üni.ch <http://xn--ni-wka.ch/>' asUrl.
"http://xn--ni-wka.ch/ <http://xn--ni-wka.ch/>"
'http://üni.ch <http://xn--ni-wka.ch/>' asUrl retrieveContents includesSubstring: 'Ãni'.
"true"
Done ;-)
Thank you, https://twitter.com/osashimitabenai <https://twitter.com/osashimitabenai>, well done !
Sven
On 23 Nov 2016, at 15:43, Sven Van Caekenberghe <sven@stfx.eu <mailto:sven@stfx.eu>> wrote:
On 23 Nov 2016, at 15:36, Max Leske <maxleske@gmail.com <mailto:maxleske@gmail.com>> wrote:
Great!
Thereâs a punycode implementation on smalltalkhub (http://smalltalkhub.com/#!/~dTriangle/Punycode <http://smalltalkhub.com/#!/~dTriangle/Punycode>) but it needs some polishing.
Wow, that looks good, it even has ZnUrl integration, so we're done ;-)
There are no tests though.
How come we never heard of this ?
Last commit was in 2013, hopefully the author is still around.
Should I open an issue on FogBugz so we donât forget?
Yes, OK.
Max
On 23 Nov 2016, at 15:00, Sven Van Caekenberghe <sven@stfx.eu <mailto:sven@stfx.eu>> wrote:
Max,
On 23 Nov 2016, at 14:34, Max Leske <maxleske@gmail.com <mailto:maxleske@gmail.com>> wrote:
Hi (Sven),
Zinc canât currently handle unicode domain names (e.g. http://üni.ch <http://xn--ni-wka.ch/>). Are there any plans to implement punycode / IDNA conversion for Zinc? Or is there an explicit reason not to support it? I see that # parseHostPort: expects the host portion to be percent escaped, what is the use case for this? I have never seen a percent escaped host portion. Usually the host portion is either pure ASCII, unicode or punycode (in my experience at least).
Just curious, as I just added IDNA conversion to one of our applications (I just let python perform the conversion: https://docs.python.org/2/library/codecs.html#module-encodings.idna <https://docs.python.org/2/library/codecs.html#module-encodings.idna>).
Cheers, Max
Yes, that would be nice to have.
Just for future reference, we are talking about the following (IDN(A)):
https://en.wikipedia.org/wiki/Internationalized_domain_name <https://en.wikipedia.org/wiki/Internationalized_domain_name> https://en.wikipedia.org/wiki/Punycode <https://en.wikipedia.org/wiki/Punycode> https://tools.ietf.org/html/rfc3490 <https://tools.ietf.org/html/rfc3490> https://www.charset.org/punycode <https://www.charset.org/punycode>
Normal DNS hostnames are ASCII only (or used to be like that anyway), that is why it is (currently) implemented like that.
Sven
Hi Yoshihiko, Thank you, I'll put the integration of your code with Zinc's URL on my todo list. Sven
On 27 Dec 2016, at 16:32, Yoshihiko Kubota <y.kubota@mail.dendai.ac.jp> wrote:
Hi
I wrote PunycodeConverter. I received a mail from Sven. But I overlooked. I already sent a mail to Seven. Please use my code. But it need to kaizen.
http://smalltalkhub.com/#!/~dTriangle/Punycode On 2016å¹´11æ24æ¥ at 4:14:16, phil@highoctane.be (phil@highoctane.be) wrote:
I am always amazed about the cool things I can learn from this list.
Phil
On Wed, Nov 23, 2016 at 4:59 PM, Max Leske <maxleske@gmail.com> wrote: :) Nice.
On 23 Nov 2016, at 16:51, Sven Van Caekenberghe <sven@stfx.eu> wrote:
https://pharo.fogbugz.com/f/cases/19383/IDNA-punycode-for-Zinc
After loading
Name: Punycode-dTriangle.8 Author: dTriangle Time: 26 August 2013, 10:19:11.728 am UUID: 6493a3ee-43bb-44f0-86a8-5aa47a9b42ff Ancestors: Punycode-dTriangle.7
I can do the following
'http://üni.ch' asUrl.
'http://üni.ch' asUrl retrieveContents includesSubstring: 'Ãni'.
"true"
Done ;-)
Thank you, https://twitter.com/osashimitabenai, well done !
Sven
On 23 Nov 2016, at 15:43, Sven Van Caekenberghe <sven@stfx.eu> wrote:
On 23 Nov 2016, at 15:36, Max Leske <maxleske@gmail.com> wrote:
Great!
Thereâs a punycode implementation on smalltalkhub (http://smalltalkhub.com/#!/~dTriangle/Punycode) but it needs some polishing.
Wow, that looks good, it even has ZnUrl integration, so we're done ;-)
There are no tests though.
How come we never heard of this ?
Last commit was in 2013, hopefully the author is still around.
Should I open an issue on FogBugz so we donât forget?
Yes, OK.
Max
On 23 Nov 2016, at 15:00, Sven Van Caekenberghe <sven@stfx.eu> wrote:
Max,
On 23 Nov 2016, at 14:34, Max Leske <maxleske@gmail.com> wrote:
Hi (Sven),
Zinc canât currently handle unicode domain names (e.g. http://üni.ch). Are there any plans to implement punycode / IDNA conversion for Zinc? Or is there an explicit reason not to support it? I see that # parseHostPort: expects the host portion to be percent escaped, what is the use case for this? I have never seen a percent escaped host portion. Usually the host portion is either pure ASCII, unicode or punycode (in my experience at least).
Just curious, as I just added IDNA conversion to one of our applications (I just let python perform the conversion: https://docs.python.org/2/library/codecs.html#module-encodings.idna).
Cheers, Max
Yes, that would be nice to have.
Just for future reference, we are talking about the following (IDN(A)):
https://en.wikipedia.org/wiki/Internationalized_domain_name https://en.wikipedia.org/wiki/Punycode https://tools.ietf.org/html/rfc3490 https://www.charset.org/punycode
Normal DNS hostnames are ASCII only (or used to be like that anyway), that is why it is (currently) implemented like that.
Sven
participants (4)
-
Max Leske -
phil＠highoctane.be -
Sven Van Caekenberghe -
Yoshihiko Kubota