5,389
edits
OBD:Localization/Japanese: Difference between revisions
m
filling in knowledge (or lack thereof) about japanese glyph rendering
m (→Subtitles) |
m (filling in knowledge (or lack thereof) about japanese glyph rendering) |
||
| Line 40: | Line 40: | ||
The main focus is on instance files (.dat/.raw) and not on the localized fragments of the engine (Oni.exe), which are typically limited to the text strings "Syndicate Warehouse" and "Save Point %d". | The main focus is on instance files (.dat/.raw) and not on the localized fragments of the engine (Oni.exe), which are typically limited to the text strings "Syndicate Warehouse" and "Save Point %d". | ||
:Extra font files (JPN_BIG.fnt, JPN_MIDDLE.fnt, JPN_SMALL.fnt, JPN_BOLD.fnt) are also not discussed here, since they have no equivalent in the English version. | |||
The table on the right lists the file properties for the specific Japanese version that was examined. For the file properties of the reference English version, see [[OBD:Localization|HERE]]. Exactly identical file sizes (level2_Final.dat, level3_Final.dat, level4_Final.dat and level6_Final.dat) have been <u>underlined</u>, much larger file sizes (level0_Final.dat) have been '''marked in bold'''. | The table on the right lists the file properties for the specific Japanese version that was examined. For the file properties of the reference English version, see [[OBD:Localization|HERE]]. Exactly identical file sizes (level2_Final.dat, level3_Final.dat, level4_Final.dat and level6_Final.dat) have been <u>underlined</u>, much larger file sizes (level0_Final.dat) have been '''marked in bold'''. | ||
| Line 63: | Line 63: | ||
The case of level0_Final is special: its much larger size (4,520,626 B against 2,816,050 B) is attributable to the font files (TSFT) and glyph arrays (TSGA) belonging to the Tahoma TSFF. | The case of level0_Final is special: its much larger size (4,520,626 B against 2,816,050 B) is attributable to the font files (TSFT) and glyph arrays (TSGA) belonging to the Tahoma TSFF. | ||
Like for the English Oni, there are fifteen TSFT font files (normal, bold and italic variants in 7pt, 9pt, 10pt, 12pt and 14pt sizes). Each of them has a slightly larger pixel data array: there are no extended ASCII glyphs (96 of those), but the 154 kana more than make up for them, so the pixel data of the TSFTs ends up taking more than for English Oni, by 230,560 B overall. | Like for the English Oni, there are fifteen TSFT font files (normal, bold and italic variants in 7pt, 9pt, 10pt, 12pt and 14pt sizes). Each of them has a slightly larger pixel data array: there are no extended ASCII glyphs (96 of those), but the 154 kana/kanji more than make up for them, so the pixel data of the TSFTs ends up taking more than for English Oni, by 230,560 B overall. | ||
The main difference in size comes from the somewhat bloated use of auxiliary TSGAs (code pages) for kana/kanji descriptors: in addition to the main TSGA used for regular ASCII (less that half full), there are 19 more TSGAs, totalling space for 4864 glyph descriptors (per TSFT), but filled very sparsely (only 154 kana/kanji glyphs are actually present). The excess space thus taken up by the 19 auxiliary TSGAs - as compared to storing all the glyph descriptors in one TSGA - is about 100 kB (including instance headers, instance descriptors, and padding), so for the 15 fonts we get about 1.5 MB (about 30 times more than for the glyphs themselves, i.e., the pixel data in the TSFTs). | |||
At the time of writing, it is not known whether the TSFF/TSFT/TSGA instances of the Japanese level0_Final.dat are actually necessary. The engine has custom logic that loads glyphs from the separate JPN_*.fnt files, and bails out if any of them is absent. The English engine, if used on the same game data, does not load the extra font files and falls back to TSFF, although the output is semi-broken and we do not yet know why. | |||
===Actual levels=== | ===Actual levels=== | ||