Special Lettes - Brazilian & Saspanish

[ricaun]

Hello,

I noticed you update the menu and some of the front_letter is not working.
In my case I have a Brazilian version of the Fatal Racing and I have the text data for the Saspanish version as well.
Some text use special characters like: ÇÃÁÉÊíÍÓÚÑ

Looks like the font2_ascii mapping table is not point to the correct char.

I just manually track the correct char, here is the before and after. The third line CONFIGURAÇÃO and last line SAíDA PARA DOS:

I don't know if there are a way to extract the mapping table from my FATAL.EXE Brazilian version to update the special chars.

I guess the current mapping table is design to work with English, Francais, and Deutsch font. Brazilian and Saspanish use a different table.

[Zizin13]

Yeah the EXE we have the debug symbols from is the English/French/German international release. As far as I know, the debug symbols from other releases have not been found. If you can figure out the correct mapping table we should be able to have some custom code that swaps mapping tables based on what languages are found in LANGUAGE.INI. I've done something similar to make sure it can load the Whiplash splash screen from the US release which doesn't include a "title.bm" file and instead loads "whipped.bm".

You can probably find these arrays in your exe even without the debug symbols with a little digging, I'd use fonic's wcdatool to split off DOS4GW then load up the "FATAL.EXE_split_dos4g_payload.exe" file it generates (FATAL.EXE minus DOS4GW.EXE) to make things a little easier. Maybe you'll even be lucky and have the same offsets for some or all of the functions and data references. Alternatively you can just define the alternate arrays manually for now if you already know which character goes with which offset in the font files.

[ricaun]

I tried the wcdatool before but was not able to create the FATAL.EXE_split_dos4g_payload.exe using my FATAL.EXE version. But generated some files like FATAL.EXE_disasm_data_all, in there I found the array with 256 bytes and with similar initial content.

Here is the extract font2_ascii for Brazilian & Saspanish language.

unsigned char object_3_variable_1646[] = {
  0xff,0xff,0xff,0xff,0xff,0xff,0xff,0xff,0xff,0xff,
  0xff,0xff,0xff,0xff,0xff,0xff,0xff,0xff,0xff,0xff,
  0xff,0xff,0xff,0xff,0xff,0xff,0xff,0xff,0xff,0xff,
  0xff,0xff,0xff,0x24,0x25,0x3c,0x27,0x28,0x2a,0x3b,
  0x2c,0x2d,0x2b,0x2f,0x37,0x3f,0x38,0x39,0x1a,0x1b,
  0x1c,0x1d,0x1e,0x1f,0x20,0x21,0x22,0x23,0x5A,0x3A,
  0x36,0x40,0x35,0x34,0x31,0x00,0x01,0x02,0x03,0x04,
  0x05,0x06,0x07,0x08,0x09,0x0a,0x0b,0x0c,0x0d,0x0e,
  0x0f,0x10,0x11,0x12,0x13,0x14,0x15,0x16,0x17,0x18,
  0x19,0x3d,0xff,0x3e,0x29,0x2e,0xff,0x00,0x01,0x02,
  0x03,0x04,0x05,0x06,0x07,0x08,0x09,0x0a,0x0b,0x0c,
  0x0d,0x0e,0x0f,0x10,0x11,0x12,0x13,0x14,0x15,0x16,
  0x17,0x18,0x19,0x32,0xff,0x33,0x30,0xff,0x42,0xff,
  0xff,0x44,0x46,0x0d,0xff,0xff,0xff,0x48,0x59,0x4a,
  0xff,0x4b,0xff,0xff,0x49,0xff,0x41,0x4e,0x50,0x4c,
  0x56,0x58,0xff,0xff,0x57,0xff,0xff,0xff,0xff,0xff,
  0x45,0x49,0x4f,0x55,0xff,0xff,0xff,0xff,0xff,0xff,
  0xff,0xff,0xff,0xff,0xff,0xff,0xff,0xff,0xff,0xff,
  0xff,0xff,0xff,0xff,0xff,0xff,0xff,0xff,0xff,0xff,
  0xff,0xff,0x45,0x43,0x44,0x46,0x53,0xff,0xff,0x42,
  0x49,0x59,0x5b,0xff,0xff,0x4a,0xff,0xff,0xff,0x5c,
  0xff,0x4d,0xff,0x50,0xff,0xff,0xff,0x55,0x58,0x26,
  0xff,0xff,0xff,0xff,0xff,0x51,0xff,0xff,0xff,0xff,
  0x52,0xff,0xff,0xff,0xff,0xff,0xff,0x4a,0xff,0xff,
  0xff,0xff,0xff,0xff,0xff,0xff,0xff,0xff,0xff,0xff,
  0xff,0xff,0xff,0xff,0xff,0xff
};

The char that I change to fix the special letter match this object_3_variable_1646 array.

I gonna create a PR, and check if the others array need to be updated as well.

[Zizin13]

Nice, excellent work

[ricaun]

Looks great!

• Brazilian
  

• Saspanish