[PATCH v4 2/2] gdiplus: In GdipPrivateAddMemoryFont allow loading fonts with long names

[Marvin]

Hi,

While running your changed tests on Windows, I think I found new failures.
Being a bot and all I'm not very good at pattern recognition, so I might be
wrong, but could you please double-check?
Full results can be found at
https://testbot.winehq.org/JobDetails.pl?Key=34251

Your paranoid android.


=== wxppro (32 bit font) ===
09f0:font: unhandled exception c0000005 at 00000000

=== w2003std (32 bit font) ===
05f0:font: unhandled exception c0000005 at 00000000

=== wvistau64 (32 bit font) ===
0504:font: unhandled exception c000001d at 02930135

=== w2008s64 (32 bit font) ===
0be4:font: unhandled exception c0000005 at 00FA0130

=== w7u (32 bit font) ===
0ef4:font: unhandled exception c0000005 at 15AC4F4D

=== w7pro64 (32 bit font) ===
08c4:font: unhandled exception c0000005 at 3E841B3B

=== w8 (32 bit font) ===
0f6c:font: unhandled exception c0000005 at 00000000

=== w864 (32 bit font) ===
0f60:font: unhandled exception c0000005 at 00000000

=== w1064 (32 bit font) ===
02b8:font: unhandled exception c0000005 at 00000000

=== wvistau64 (64 bit font) ===
09d4:font: unhandled exception c0000005 at 00000000020D01F8

=== w2008s64 (64 bit font) ===
07ec:font: unhandled exception c0000005 at 00000000021401F8

=== w7pro64 (64 bit font) ===
084c:font: unhandled exception c0000005 at 000007FEFB50AF1A

=== w864 (64 bit font) ===
0f50:font: unhandled exception c0000005 at 0000000000000000

=== w1064 (64 bit font) ===
0f18:font: unhandled exception c0000005 at 0000000000000000