I already mentioned it at my personal blog, when you create a language pack for Turkish locale you won't be able to install it to any other DNN instance since the manifest file name is incorrect.

Please watch the video at following post:

DNN 5.2.0 Language Pack Manifest File Bug

Then please try to install DotNetNuke 5.1.4 package to a test installation, i assume it will not get completed due to errors.

In my tests:

Affected DotNetNuke Versions:

DotNetNuke 5.1.4 and DotNetNuke 5.2.0

Affected Modules:

All Core and Third Party Modules

Please someone test and confirm this problem... Should i report it as bug?

Hmm i didn't have the chance to test it yet, but i am going to handle Arabic Language Packs for one of my clients next week, i can test it when that time comes.

This time it might be another issue, maybe same Turkish I problem but it is a bit strange because Turkce becomes Trkce, so suspected char is u-U i guess.

I did reproduce the error with Turkish locale a few times new install or upgrade does not matter. You can also try to test it with my latest language pack which can be found under DotNetNuke Language Packs section.

I will create the issue under Tracker once i complete my investigation.

When I tried testing some other bugs reported yesterday, I experienced similar behaviour, without being able yet to narrow down the situation.

Hopefully, Gemini will be opened to the public soon.