Quote:
Originally Posted by jugaor
I understand your well-founded reasons. The BOM suggestion wasn't specifically for me, but for the millions of Win-Excel users who just double-click and that's it. It was just a suggestion to save you potential "It's not working properly" reports  |
Luckily, Sigil does not have millions of Win-Excel users
. And promoting a broken idea just for one set of users is not a good idea for any cross-platform app in my humble opinion.
FWIW, a websearch shows Windows 11 does finally have a new feature to make the default encoding utf-8 for all apps, as it is in Notepad now, even for older apps.
Quote:
|
To make UTF-8 the default system encoding in Windows, enable the "Beta: Use Unicode UTF-8 for worldwide language support" option in the Region settings. This improves compatibility with web apps and Linux, though it may cause issues with older, non-Unicode applications. A system restart is required.
|
But off course it defaults to off, is hidden under Region setting even though utf-8 is regionless, etc. But at least it is there. Hopefully Windows 11 users will find this and enable it so that their system can be just like Web, MacOS, and Linux systems which have had this capability built in for years, so that they can make/edit text that can contain any word, no matter the language. The days of old 8-bit encoding codepages has long passed.
For existing 8-bit code page text docs, many apps have the capability to bulk transcode 8-bit encoding to utf-8 to future (present)-proof them, especially for archiving. Sigil does this for all xhtml files on initial load (detects encoding either by charset settings or detection algorithms and converts it to utf-8).