But that is a hack that should be restored after each update.
So, the extension request is to create an extension that will allow users to use their favorite conversion system without restoring cp.publish.php each time.
You really should make this a feature request. The developers will probably listen, but they are monolingual, so they would not know which letters to transiterate to what.
We have support for most characters in the Latin-1 (ISO-8859-1) charset already. Since we get ”ü -> ue” in urls alrady, there is no reason why other accented characters shouldn’t work.
Title: Strange URL Interpreter
Purpose: Gives ability to convert foreign-language characters in entry’s URL Title to proper characters.
Version 1.1.0 support more than Slovakian, Czech, Hungarian and Russian alphabet. If there are any unsupported, or wrong converted characters in your native language, let me know.
Version: 1.1.0 (25/06/2007)
Version: 1.2.0 (07/07/2007)
- Added: Lira, Degree, Yen, Pound and Cent sign
- Fixed: Update and Disable function
Version: 1.3.0 (22/09/2007)
- Added: Character set supporting Poland language (Thanks to Gabriel Borkowski).
Fast work, Gabriel! Say, if some others can check the accuracy of this conversion array, and if you name it something more specific than “Foreign URL Title”, we can probably add this to the repository. Though me being rather ignorant of the alphabets of non-latin languages, I do not have anything good to suggest that would cover those four alphabets.
Nice work, of course I totally missed that hook in the changelog.
As a German native speaker, I’d like to add that German is fully supported as well (as has, in fact, been by EE natively for some time), also French, as far as I can tell.
Ingmar: Is not possible made any universal conversion, but why ”ä” should be “ae” and not “a”? I think, URL title was developed as power tool for Search engines (SEO) and not for people. Who reading titles in URL, especially entries title???
For example: I’ve got slovak word “mäso” (meat). When I put to Google word “maso” I return searching resutls related to word “mäso” and “maso”. Nobody will be searching “maeso” because this word doesn’t exist! It mean, conversion ”ä” >> “ae” simply and powerful harms Pagerank of your website.
Iam sure, you will find equal example in your language. If not, let me know.
I’ve got idea. Maybe will be useful create various conversion sets in dependence on different languages. In the settings of the extension you’ll have option choose conversion set, as you want.
Gabriel, I think Ingmar is right regarding german umlauts ä, ö, ü - it is the common transliteration, even search engines are honoring this form. Following your thoughts: Nobody will search for “nurnberg”, but someone who doesn’t have a german keyboard might search for “Nuernberg” instead of “Nürnberg”. The built-in url transliteration in EE replaces ü with ue as well.
Taking our example in consideration, that shows that there perhaps a editable translation table would be favourable - depending on the language one might want another transliteration for slovak and german.
EDIT: Too late ... I see you had the same idea a couple of minutes before my post
I think English speakers—at least the American ones—would search for “Nuremberg” in all cases. Nürnberg is unknown to us. It’s a little bit like how there is no Moscow but that’s where we all want to go.
Maybe - but they wouldn’t find anything with that search term on a german language page, wouldn’t they? I was referring to a german speaking person looking for german information but not having a german keyboard. But this is far out of topic - “Nürnberg” would be in the content of the page, its just how to recode the URL title.