I installed TADS 3 on Windows 10, using the latest release (from 2016). Mostly, it works well - however, there is one pesky error message I cannot seem to get rid of:
No mapping file is available for the local character set “cp65001”.
TADS itself treats all characters as unicode, but since most operating systems did not support unicode in their consoles, they relied on code pages to represent a certain subset of special characters. TADS offers mapping files for the most common of these code pages.
Ironically, cp65001 is the unicode code page for Windows, representing all characters as unicode. Therefore, there’s no need for a mapping file - all characters already are represented as unicode. Console support for unicode is relatively new, so the TADS VM doesn’t seem to realise that it doesn’t have to map anything here. It stubbornly tries to load a mapping file - one that doesn’t exist, and cannot get generated, since cp65001 represents the entirety of unicode.
I tried to tell my system to use a code page that TADS can deal with, but no matter which system variable I changed, TADS keeps showing the warning message - be it in web mode or console mode. I don’t know where the TADS VM gets its information about the used code page from and I don’t like fooling around with my system variables; usually, it’s recommended to leave cp65001 in place nowadays, only using more restricted code pages if absolutely necessary.
Does anyone know what to do to get rid of the warning? Is there even a possible fix for this, or is the tADS VM itself simply outdated and would need an update? (It has been five years since the last release; that’s a long time by software standards).
Thank you in advance.