Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

How to handle diacritics (accents) when rewriting 'pretty URLs'

I rewrite URLs to include the title of user generated travelblogs.

I do this for both readability of URLs and SEO purposes.

 http://www.example.com/gallery/280-Gorges_du_Todra/

The first integer is the id, the rest is for us humans (but is irrelevant for requesting the resource).

Now people can write titles containing any UTF-8 character, but most are not allowed in the URL. My audience is generally English speaking, but since they travel, they like to include names like

 Aït Ben Haddou

What is the proper way to translate this for displaying in an URL using PHP on linux.

So far I've seen several solutions:

  1. just strip all non allowed characters, replace spaces this has strange results:
    'Aït Ben Haddou' → /gallery/280-At_Ben_Haddou/
    Not really helpfull.

  2. just strip all non allowed characters, replace spaces, leave charcode (stackoverflow.com) most likely because of the 'regex-hammer' used
    this gives strange results: 'tést tést' → /questions/0000/t233st-t233st

  3. translate to 'nearest equivalent'
    'Aït Ben Haddou' → /gallery/280-Ait_Ben_Haddou/
    But this goes wrong for german; for example 'ü' should be transliterated 'ue'.

For me, as a Dutch person, the 3rd result 'looks' the best.
I'm quite sure however that (1) many people will have a different opinion and (2) it is just plain wrong in the german example.

Another problem with the 3rd option is: how to find all possible characters that can be converted to a 7bit equivalent?

So the question is:

  1. what, in your opinion, is the most desirable result. (within tech-limits)

  2. How to technically solve it. (reach the desired result) with PHP.

like image 453
Jacco Avatar asked Jan 21 '09 16:01

Jacco


People also ask

Are accents allowed in URLs?

Google: Accents In URLs Work Fine For Google John said "Accents in URLs are no problem -- feel free to use them."


2 Answers

Ultimately, you're going to have to give up on the idea of "correct", for this problem. Translating the string, no matter how you do it, destroys accuracy in the name of compatibility and readability. All three options are equally compatible, but #1 and #2 suffer in terms of readability. So just run with it and go for whatever looks best — option #3.

Yes, the translations are wrong for German, but unless you start requiring your users to specify what language their titles are in (and restricting them to only one), you're not going to solve that problem without far more effort than it's worth. (For example, running each word in the title through dictionaries for each known language and translating that word's diacritics according to the rules of its language would work, but it's excessive.)

Alternatively, if German is a higher concern than other languages, make your translation always use the German version when one exists: äae, ëe, ïi, öoe, üue.

Edit:

Oh, and as for the actual method, I'd translate the special cases, if any, via str_replace, then use iconv for the rest:

$text = str_replace(array("ä", "ö", "ü", "ß"), array("ae", "oe", "ue", "ss"), $text);
$text = iconv('UTF-8', 'US-ASCII//TRANSLIT', $text);
like image 168
Ben Blank Avatar answered Sep 23 '22 23:09

Ben Blank


To me the third is most readable.

You could use a little dictionary e.g. ï -> i and ü -> ue to specify how you'd like various charcaters to be translated.

like image 28
ChrisW Avatar answered Sep 24 '22 23:09

ChrisW