XSTR on Free42

[Thomas Okken]

(07-11-2021 02:36 AM)rprosperi Wrote:  Thanks. Some apps will create files with the trailing dot, and apps that expect these kinds of files usually work with one, but not the other, so just checking which is desired.

Well, it certainly isn't hard to make the app recognize "portable." in addition to "portable"... I'll add that check in the next update.

(07-11-2021 02:36 AM)rprosperi Wrote:  Sorry I wasn't clear - I opened the README.txt file and the text editor I used complained about the invalid characters in the table shown there.

Hmm, that's annoying. The README.txt file is UTF-8-encoded, which it needs to be because Windows-1252 doesn't provide all the symbols it needs. Once upon a time you'd make that explicit by adding a BOM at the start of the file, but those appear to have fallen out of favor in the Windows world, i.e. other text editors have started complaining about them. If there are still text editors that don't recognize UTF-8 by default, that's a problem, but I think it's the text editors in question that need to be fixed, not the standards-compliant UTF-8 text files they're complaining about...

(UPDATE: It looks like even Microsoft doesn't have its act together on this yet. Notepad in Windows 10 handles README.txt fine, and in fact appears to use UTF-8 without BOM as its default encoding, and Visual Studio 2019 has no problems, either. But Windows 10 WordPad garbles README.txt, even if you tell it the file is Unicode text while opening it.)