There are some posts here with 8bits (namely - Russian) tittles, which was transormed in same (8bits) URLs. It's extemely bad and wrong style, trust me. All "more than 7bit" URLs must be transliterated into pure English
This is not secure for any site. The hacking system is started with mysql injection and in maximum time it is done by URL encoding. The system pharses the code and make it readable. So every CMS user should be alert to make it success. austin defense attorneys
If I'm not wrong, the first Drupal Commons release uses Pathauto 6.x-1.3. Therefore, the optional URL transliteration -if enabled- is still directly handled by this version of the Pathauto module, and not by the Transliteration module (which works with Pathauto 6.x-2.x).
The Pathauto module includes a small transliteration file for some languages (I think also Russian). See the previous link for a full transliteration file for every UTF-8 character. If there are for example Japanese or Chinese users, it would be good to know if they are also interested in URL transliteration. I think probably they are.
I've just seen the mentioned full transliteration file, and it looks like it includes Chinese but not Japanese transliteration. Another possibility would be to try the Transliteration module and Pathauto 6.x-2.x. However, they use Unidecode, which "does quite badly on Japanese and Thai". So, Japanese transliteration seems difficult. Maybe a Japanese Drupal expert could help here.
Comments
Why exactly are they evil,
Why exactly are they evil, bad and "wrong style"? Coudl you provide some sources?
It's easy
First of all: we have RFC 2396 (Standards Track)
Secondly:
compare CP of RFC-compliant URL http://commons.acquia.com/discussion/8bits-urls-are-evils and 8bit URL http://commons.acquia.com/blog/кндр-произвела-залпы-вблизи-границы-с-южной-кореей http://commons.acquia.com/blog/%D0%BA%D0%BD%D0%B4%D1%80-%D0%BF%D1%80%D0%...
Enable transliteration
Probably you need to enable transliteration for the Pathauto module.
Anyway - bug
I can enable, but prefer (in common) have it "from a box" - not everybody Common's admin is also Drupal's guru
The URL parser should be work correctly.
This is not secure for any site. The hacking system is started with mysql injection and in maximum time it is done by URL encoding. The system pharses the code and make it readable. So every CMS user should be alert to make it success. austin defense attorneys
We have transliteration
We have transliteration installed and enabled. I assumed it handled URLs. Does it not?
Depends on the Pathauto version
Pathauto 6.x-2.x can use the Transliteration module. Pathauto 6.x-1.x transliterates without that module.
Not here
At least I didn't see transliteration here - russian link, used in my message, was found on this site (default Commons installation, yes?)
So, the recommendation is?
So, the recommendation is?
If using Pathauto 6.x-1.3...
If I'm not wrong, the first Drupal Commons release uses Pathauto 6.x-1.3. Therefore, the optional URL transliteration -if enabled- is still directly handled by this version of the Pathauto module, and not by the Transliteration module (which works with Pathauto 6.x-2.x).
The Pathauto module includes a small transliteration file for some languages (I think also Russian). See the previous link for a full transliteration file for every UTF-8 character. If there are for example Japanese or Chinese users, it would be good to know if they are also interested in URL transliteration. I think probably they are.
Japanese not included
I've just seen the mentioned full transliteration file, and it looks like it includes Chinese but not Japanese transliteration. Another possibility would be to try the Transliteration module and Pathauto 6.x-2.x. However, they use Unidecode, which "does quite badly on Japanese and Thai". So, Japanese transliteration seems difficult. Maybe a Japanese Drupal expert could help here.
("Update" on 17 Jan is to mark as not-Featured)
eom