These days web addresses can also include non-ASCII characters. So every modern browser and webserver is ready to handle UTF-8 URI. There is any "con" to use it today? I mean, a lot of people will say "it will break old browsers, bla bla bla", but since, we assume javascript support, we don't support more IE6, is it ok if i assume that all modern browsers will be able to handle urls with öäü in the url? Because my application (db, framework, webserver) is full utf-8.
+2
A:
They should handle it.
BUT: how does the user enter it?
If you SHOW them in coded form, they are ugly.
If you show them in "native" form - how would YOU enter a french acccent or a chinese symbol;) Just out of curiosity. I would not know how to ;)
TomTom
2010-03-17 09:36:07
Segmentation. I dont have fear to make a chinese job website focusing to target nothing but chinese speaking workers. Polarization is good, not always one size fits all ;-)
VP
2010-03-17 09:43:01
You can google for the symbol and use copy )
tux21b
2010-03-17 09:45:19
Christoph, /städte/Köln as resource, für mich, ist besser als /staedte/Koeln. Specially because we created this "workaround" when DB, WebServer and Browsers didn't support UTF-8. Today its different, we should prefer it than other encodes..
VP
2010-03-17 12:31:37