Windows would have to implement locale sensitive case conversion functions for Turkish, Azeri, Kazach, Turkmen, Tatar and Gaugaz to wreck the code written with English rules in mind. If it is just character used in system strings, language list is even longer. Turkish is mostly in Latin script.
All I can tell you is what we've seen lately, and that is there were a few reports of this problem as seen throughout the last several pages of this thread. Once those affected players had made the regional change, there had been no more reports on this particular problem.
There hasn't been any new reports about this until yours, so I can only surmise the bug carried over from 0.1.7 to 0.1.8 via game saves (which can and sometimes does happen), or you're playing v0.1.7 and not v0.1.8 (which we have seen a number of players do in past games from Faerin).
None of us on the team have any way of testing this to see if the problem was fixed, but we did inform Faerin about it when the first reports of it came to our attention, to which he is looking into (in fact, I spoke to him earlier this afternoon about it). If the issue still exists, it will be fixed before next Friday's release. The only suggestion I have at the moment would be to attach a copy of both the player and player_prev logs along with your save for Faerin to review. And if you could create a save before the event, that would be extremely helpful.
**Follow-Up**
I've got a Windows 10 Turkish VM installed and I have a save from a new run I did last night that I used in the new VM. I was able to encounter the bug, so I won't need a save or logs.
