You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To convert to a valid URL, the host would be converted with punycode, and other components would percent-escape when possible. Errors are still possible.
We can identify components by identifying possible delimiters (like urls::format does) or we can provide functions that create a URL from its components:
It is probably a very good idea to use ICU for this. I currently use ICU to create and parse unicode URLs. It works perfectly with all types of Unicode characters. Adding ICU support for Boost.URL would be excellent! Alternatively, there are some very lightweight unicode libraries that I think would work for this, but ICU is the only fully featured unicode library. People who work with unicode very likely already use many of the features only provided by ICU I believe.
We should have a function to handle unicode urls:
result<url> parse_unicode_url(...)
To convert to a valid URL, the host would be converted with punycode, and other components would percent-escape when possible. Errors are still possible.
We can identify components by identifying possible delimiters (like
urls::format
does) or we can provide functions that create a URL from its components:The text was updated successfully, but these errors were encountered: