Wow, an interesting debate :). I too have been considering i18n URLs, and also concluded that it was too much work. I have to agree with Felix, nobody except 'power' users and developers looks at the url, so it's pretty much pointless anyway.
The routing part isn't really a problem, as you can take the url, translate it back to english and then run your routes (that's how I was considering doing it). That way it isn't necessary to generate a massive route list. The real problem is as already mentioned - links from the page also need i18n and the overhead in doing so is at the very least annoying; I was considering hooking in a service to take the english url (assuming the code is in english) and return a translated url (probably not enormously difficult, if you just explode the url and translate each part). Maybe I'll put an experiment in place in the future and see if it's worth thinking about further, but at this time, I don't think so. Cheers, AD7six --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Cake PHP" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php -~----------~----~----~----~------~----~------~--~---
