The latest build of this product (v4.2.42) was released 5 years ago, which was before this thread was created.
Posted 1 days ago by serega
Version: 4.2.42
Avatar

Let’s get real: 90% of your users have no clue what an encoding or a codepage is. They just like your clean interface for writing text files. And what do you give them by default? A broken "Automatic Detection" that fails miserably.

When your "Auto" logic defaults to Windows-1251 instead of UTF-8, these users open their files in other apps and see nothing but "squares" and gibberish. They don't go looking for settings — they just think your app is broken and uninstall it immediately. Like I wanted to do. But I've been through the registration of 2 circles of hell with your double re-captcha. Which will soon be crime prosecuted for wasting billions of man-hours.

You claim to have a "fallback to UTF-8," but as we’ve seen for 12 years, it’s a lie. Stop forcing this "Auto" lottery on people. Professionals and casual users alike need Unicode (UTF-8 without signature) - Codepage 65001 or with BOM , as the absolute, forced default.

Fix your defaults or keep losing users.

Add Comment

Please log in to a validated account to post comments.