 |
Fixed with checkin 0004968. As a workaround we transform 0xff to 0xb6 at loading time of any lang dict. (The russian font contains the correct character at 0xb6). This way it works with any dictionary, and/or readable (when these use "#str_12345" constants, which theymust for I18N to work, anyway). Once D3 goes open source we might revisit this and fix the GUI rendering bug(s). But for now this works. |
|
|
The bug inside the D3 code has been fixed, so character 0xFF now renders. The remapping for Russian is still in place, tho, to avoid having to patch all the russian fonts. However, the remapping code has been reworked. The first version exchanged characters one by one, so that if you had "AB" and a table of [ A => B, B => A ], you got "BB" after the first step, and "AA" after the second step. This was wrong, we should end up with "BA" instead. In v1.07, this was worked around by keeping a special order in the character remap tables. For the new polish characters, however, this became impossible, so with revision 0005920 this was finally fixed. |
- Anonymous
