Your ticket was opened on the 18th, after business hours. We replied first thing on the next business day and were in constant contact with you. We had a pre-release build to you within a week. The issue you reported IS fixed: The import/upload correctly recognizes the foreign characters. As such, I'm marking this issue as Resolved.
Realize the uploader was designed to allow for multiple files to be uploaded at one time. In such cases, the fields in each sheet, most likely, won't match, especially when CSV exports are from other products/services. Therefore, that requires mappings to be created for each contact in order to ensure the mappings are set correctly for each contact imported across all sheets.
The CSV file you provided is a PERFECT example of why importing contacts works the way it does. Under the "Phone 1 Type" heading, you have a mixture of "work", "home", "mobile" and "other" as the phone number Types. Without mapping those contacts individually, all those phone numbers would go under 1 heading. Therefore, having to map contact-by-contact allows you to properly place those phone numbers in their proper contextual setting for each contact.
I understand you don't like that resolution and how contact importing works. That's MUCH different than saying your issue isn't fixed.
Oh, and please don't post the same thing to multiple different Community threads...it's kind of repetitive and a bit childish.