SCI11-Plus
 |
This article is a tool stub page. You can help the Sierra Wiki by expanding it. |
| Latest Version: | 1.KAWA.044 | ||
|---|---|---|---|
| Release Date: | 2023-04-14[1] | ||
| Company: | N/A | ||
| Development Status: | Maintained | ||
| Publication Status: | Published | ||
| Developer(s): | Kawa | ||
| Interface: | N/A | ||
| Language: | C | ||
| Open Source: | Open | ||
| Source Availability: | Yes | ||
| License: | None | ||
| Type: | Interpreter Interpreter | ||
| Relevant Engine: | SCI1.1 | ||
| Platform: | DOS | ||
| Localization: | English | ||
| Website: | github.com/Kawa-oneechan/SCI11-Plus | ||
Description
Kawa's SCI11-Plus An enhansement of Sierra's SCI1.1 interpreter from leaked source code.
The BASE folder contains a cleaned-up version of Sierra's SCI11 interpreter source, ready to build. It has no extra features, only some warning-suppressing fixes and a lot of style changes. Oh, and no version stamp checks. The EXT folder contains my personal project, which takes the base version and adds a bunch of new features to it.
Included is a minimal copy of a very old MSVC, required to compile all this.
Features
Requirements
Version History
v1.KAWA.043
Turns out a single missing = in the UTF-8 code messed up the save game selection list. And that inspired a mild rethinking for StrAt... and StrCase while I was there.
StrAt now just assumes you're working with single-byte characters. If you want to change a character at a given position for one that needs more or fewer bytes, consIDEr using Utf8To16 and its counterpart instead:
- Change the fifth character (zero-based!) in mbcsString from a regular o or whatever to an o-macron
- by first wIDEning it.
(Utf8To16 @wIDEString @mbcsString 32) ; up to 32 characters or the first null, whichever comes first. (= [wIDEString 4] $14D) (Utf16To8 @mbcsString @wIDEString 32)
- mbcsString's length just went up a little.
This method should be safe to use in a build with UTF-8 disabled, as the pair will just turn bytes to shorts and back.
StrCase now consIDErs the current port's font to decIDE if it should consIDEr UTF-8 sequences, or just go for raw bytes like a build with UTF-8 disabled would. Often that will mean font 0 decIDEs. If it's a 128-character font, or a 256-character font in Windows-1252 order, the Unicode case mapping should work for most characters.
Development Status
SCI11-Plus is currently maintained by Kawa.
Options
Download
Download from here:
sci11+_1.k.044-regular.zip (ZIP file) [96.7 KB]
Source:
Known Issues
Credits
Legal
SCI11-Plus was released with no license.
References
- ↑ github.com/Kawa-oneechan/SCI11-Plus
- ↑ From the project's README.md file (https://github.com/Kawa-oneechan/SCI11-Plus/blob/master/README.md)
Also See
- Interpreter Articles
- Category:SCI Interpreter Articles
- SCI Interpreters
- github.com/Kawa-oneechan/SCI11-Plus
