Sebastian:

You are an admirable individual to whom we hold in great esteem. 

However, your response is giving us pause.  Unless we hear differently from DNN, we will be back at looking at a different CMS vendor.  With our familiarity with DNN (our 1st choice), we have done our due diligence on DNN 5.5.  The issue for us is that DNN Corp:

• did not fully deliver on Content Localization; 
• taking away Human Friendly URL's when in ML mode (enabled)0, and
• not officially communicating this breaking change.

Someone in DNN Corp needs to step up and fully explain the issue here and the plans to fix it.  Of course someone knew this would be a breaking change in software development. 

In essense, this is how this DNN issue is coming across: 

• give us new functionality that DNN has been touting for a long time (Content Localization), but take away an important attribute (Human Friend URL's). 
• then tell us that there are problems, but the overall delivery of the new functionality outweighs the setback of another functionality. 
• then tell us to go buy iFinity URL's module to fix our problem because we don't have time to deal with it while we pat ourselves on the back for delivering Content Localization (note: we have nothing against iFinity URL's module; good work, but there's a larger principle at work here).

We've been cheerleaders for DNN for a long time, but this update and its poor communication of its effects by DNN are less than admirable.

In regards to the other link you posted:
http://www.dotnetnuke.com/Community/F...

It doesn't fix the mess.  If one wants Human Friendly URL's again, it can only be used with one language.  Unacceptable.

We're sticking with DNN for now.  However, for our new client, DNN 5.5 Professional, and this issue?  We will be looking at other options because we cannot recommend a product that costs a lot of money to purchase and then learn the core ML functionality screws up the Human Friendly URL's.