Community
AGI Programming => AGI Development Tools => Topic started by: AGKorson on June 04, 2022, 07:52:17 PM
-
Here's the newest version of WinAGI: http://agiwiki.sierrahelp.com/index.php?title=File:WinAGI_2_2_3.zip
The big change in this version is support for non-English MSDOS codepages, which makes it much easier to edit resources in other languages. If you never intend on using extended characters or working in a language other than English, there's no reason to change from the default MSDOS codepage (437). (But I would still advise upgrading to this version; it also fixes a few more minor bugs, including the issue that causes it to fail on older versions of Windows.)
AGI doesn't contain any native support for non-English text/fonts. And showing extended characters on screen (other than in the text.screen mode) is not normally possible. So why bother adding this feature to WinAGI?
Using the string hack technique (http://"https://sciprogramming.com/community/index.php?topic=1870.msg12903#msg12903"), it is possible to get AGI (when running on DOSBox, or on an actual MSDOS machine) to show all characters in whatever codepage the environment is set to. You can also get AGI to allow inputting letters with diacritics on the input line to let players use non-English words to play a game.
The logic code needed to make this work is very complicated, and formatting foreign words in your WORDS.TOK file is also quite complicated, but if you are interested in doing this, WinAGI now lets you edit your resources in the same codepage that your game will use, making translations (or creating new games in non-English) much simpler. It will also create word lists with non-English words (which are simply ignored in 'normal' AGI but work perfectly when paired with the codepage string hack technique).
-
Nice job.
-
Arf, I hadn't even seen that you had uploaded the update ::) I'm glad that my SQ1 translation project motivated this WinAGI update. It's awesome ;D
The beta version that Doomlazer and I had tested was already very conclusive. I'll test it right away and report back to you. I'm grateful to you, you can't even imagine !
Thank you AGK !
-
It works very well :
(http://www.image-heberg.fr/files/16559900993514732643.png)
(http://www.image-heberg.fr/files/16559901623591591034.png)
The result is perfect with DOSBox and ScummVM.
-
Thank you for all your work on these great improvements, AGKorson.
Thrpwng's SQ1 translation uses the DOSBox " KEYB " command to utilize a custom codepage that, thanks to the string hack, changes the default font for both AGI graphics and text modes. It's used in the SQ1 French translation because the default English 437 codepage accents are a bit boring, but could also allow for Cyrillic letters or other special font cases. The custom font needs to be packed into a .cpi file, which can be done with an old DOS tool called CPI120 (download cpi120.zip from: http://www.kostis.net/freeware/)
The custom codepage font can also be repurposed to create an agi-font-dos.bin file used by ScummVM. This allows for consistency between both DOSBox and SVM. All possible because of WinAGI 2.2.3!