Closed (duplicate)
Project:
Pathauto
Version:
4.7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
28 Feb 2007 at 23:52 UTC
Updated:
6 Nov 2007 at 17:19 UTC
I am using pathauto on a German website and it is generating the new urls based on the nodes title.
It is generating the url aliases, but when the title contains a foreign character such as something umlaut, ( für) gets changed to ( fur ). i realize that umlaut's are not supported in url strings, but ( für ) should become ( fuer ). The general rule of thumb, anything with an umlaut gets changed to that letter followed by an e.
any help would be greatly appreciated.
Thanks.
Comments
Comment #1
Brian.Harris commentedDove into the module code in pathauto.module line 259 and line 269 - uncomment the code and it works perfectly.. how come this was commented out to begin with?
Comment #2
gregglesBrain - thanks for the report and for doing the research about lines 259-269. I don't know why mikeryan made that change. If you look at http://cvs.drupal.org/viewcvs/drupal/contributions/modules/pathauto/path... you can see that it happened in August of 2005 - quite some time ago and a year before I became maintainer. Here's the specific diff: http://cvs.drupal.org/viewcvs/drupal/contributions/modules/pathauto/path... The commit message for that change is just "Several enhancements" http://cvs.drupal.org/viewcvs/drupal/contributions/modules/pathauto/path... So, we don't know a whole lot about that, unfortunately.
I'm not making fixes for transliteration in 4.7.x. That system was the source of about 25% of the issues in pathauto in 4.6/4.7. For 5.x I have refactored that entire section to use an easily edited transliteration file and I see that as the way forward - to upgrade :)
Now, that said, I understand that you are having problems with 4.7 and that isn't great. If you provide a patch and get it reviewed/tested by maybe 5 other people who actively use transliteration then I'd be happy to commit it. The problem is that lots of times fixes for one language will break another - hence my desire for widespread testing before committing any "fixes" that then break other sites. I did that once or twice already and it's painful for everyone involved.
Comment #3
gregglestransliteration is now optional and admin controlled, so I think this is a duplicate of wherever the issue was that solved that.