I have a situation that I have not encountered before but it totally makes sense from my customer's perspective.
The customer has a bunch of Language layers (10) planning to add more. In most cases, these language layers are using the content from the master website with a few exceptions,
The request is that any link added in the content (in the richtext editor) should be localized to the equivalent of the language area of the visitor.
Meaning that, if they add a link like /en-us/somepage (which actually means /Default.aspx?ID=12) in the masterpage, visitors that are accessing the same page in , let's say, german language layer, should see the link as /de-de/somepage (which actually means /Default.aspx?ID=35). I cannot rely on having the same page names and replacing the prefix according to the language layer.
I have scratched my head and I see just a few options:
1. Use a custom URL provider that will translate the ID of the page before trendering the friendly URL
2. Use some notification on before page load (or something similar)
Not sure if these 2 options mean the same thing :)
Any other idea about how to best implement this without affecting performance a lot?