On Tue, Sep 13, 2005 at 04:45:30PM +0900, Dmitry Timoshkov wrote:
+static const struct nls_update_font_list +{
- UINT ansi_cp;
- const char *oem, *fixed, *system;
- const char *courier, *serif, *small, *sserif;
+} nls_update_font_list[] =
Hi Dmitry,
I think you also need to take into account the OEM codepage here. For example in the UK the OEM font would be vga850.fon while in the US it would be vgaoem.fon.
Huw.
"Huw D M Davies" h.davies1@physics.ox.ac.uk wrote:
I think you also need to take into account the OEM codepage here. For example in the UK the OEM font would be vga850.fon while in the US it would be vgaoem.fon.
Once Alexandre accepts the patch I'll send the fix, it should be a small one.
On Tue, Sep 13, 2005 at 06:21:22PM +0900, Dmitry Timoshkov wrote:
"Huw D M Davies" h.davies1@physics.ox.ac.uk wrote:
I think you also need to take into account the OEM codepage here. For example in the UK the OEM font would be vga850.fon while in the US it would be vgaoem.fon.
Once Alexandre accepts the patch I'll send the fix, it should be a small one.
Fair enough. I'd suggest separating the ansi fonts from the oem fonts and installing them according to the appropiate codepage.
One other thing about your patch - I don't think we want the magic registry comment above the external fonts registry key, as this isn't user configurable data, it's just internal housekeeping.
Huw.
"Huw D M Davies" h.davies1@physics.ox.ac.uk wrote:
One other thing about your patch - I don't think we want the magic registry comment above the external fonts registry key, as this isn't user configurable data, it's just internal housekeeping.
I've just added the comment to make it look similar to the earlier occurence of 'if(RegCreateKeyExW(HKEY_CURRENT_USER, external_fonts_reg_key' in that file.