Per the applicable standard,
RFC 1378, URLs can only contain ASCII characters. Good explanation
here, and I quote:
"...Only alphanumerics [0-9a-zA-Z], the special characters "$-.+!'()," [not including the quotes - ed], and reserved characters used for their reserved purposes may be used unencoded within a URL."
I had forked blogengine supporting encoded unicode slugs in database.
but I planned to upgrade my site.
I see that now version 2.5 supports unicode slugs, but doesn't encode them.
I am in doubt whether I should once again change codes to support unicode slug encoding support, or leave it as is.
attachement of this issue: http://blogengine.codeplex.com/workitem/10386 helped me implement support for that.
please someone tell me what is planned for the future. will it support encoded unicode slugs, or it will stay as it is.