1
SCI Development Tools / Re: SCI Companion V3 - alpha build notes/bugs/feature requests
« on: January 17, 2025, 03:52:26 AM »
Supporting Japanese in SCI Companion is a hack and a half that won't cover SQ4, but it will work on for example PQ2, because all of them except SQ4 use Shift-JIS. So what you wanna do is claim the game uses Windows 1252 which bypasses the code page translation, then use AppLocale or some such to make SCI Companion itself run in Shift-JIS. Because it was never a Unicode application and for most of us can be assumed to run on Win-1252.
And that means the encoding used in PQ2-JP can match SCI Companion's... by making SCI Companion match PQ2's instead.
As for the font data: the Japanese games run on a system that has such beautiful features as "an entire Shift-JIS kanji character set in ROM" and "can display higher-res fonts on top of low-res graphics". The actual SCI font data only contains some katakana in the upper moby.
And then there's my SCI1.1+ which has UTF-8 support, entirely inspired by the fact that in the font data, it says "number of characters" instead of "highest character number". So "256 characters" instead of "up to #255". It's a 16-bit number and Unicode at the time hadn't developed into the astral planes yet. But I just said SCI Companion is not Unicode aware, so how do you use it with SCI1.1+? That's the best part: you don't! I wrote a command line tool to handle message resources in UTF-8. The only thing SCI Companion knows is that the max amount of characters isn't 256.
And that means the encoding used in PQ2-JP can match SCI Companion's... by making SCI Companion match PQ2's instead.
As for the font data: the Japanese games run on a system that has such beautiful features as "an entire Shift-JIS kanji character set in ROM" and "can display higher-res fonts on top of low-res graphics". The actual SCI font data only contains some katakana in the upper moby.
And then there's my SCI1.1+ which has UTF-8 support, entirely inspired by the fact that in the font data, it says "number of characters" instead of "highest character number". So "256 characters" instead of "up to #255". It's a 16-bit number and Unicode at the time hadn't developed into the astral planes yet. But I just said SCI Companion is not Unicode aware, so how do you use it with SCI1.1+? That's the best part: you don't! I wrote a command line tool to handle message resources in UTF-8. The only thing SCI Companion knows is that the max amount of characters isn't 256.