[Bug 46855] New: system.drawing.fontfamily.families property has no access to windows fonts in drive_c /windows/Fonts

https://bugs.winehq.org/show_bug.cgi?id=46855

Bug ID: 46855
           Summary: system.drawing.fontfamily.families property has no
                    access to windows fonts in drive_c/windows/Fonts
           Product: Wine
           Version: 3.0
          Hardware: x86
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: -unknown
          Assignee: [e-mail]
          Reporter: [e-mail]
      Distribution: ---

https://docs.microsoft.com/en-us/dotnet/api/system.drawing.fontfamily.famili...

Installed Microsoft core fonts (Arial etc). NotePad see all fonts.

But T=the FontFamilies/Families property in .Net returns only returns names of
all fonts in the Linux OS. But it does not return any of the fonts in
drive_c\Windows\Fonts

How does a .net program access the fonts in drive_c/Windows/Fonts

[Bug 46855] system.drawing.fontfamily.families property has no access to windows fonts in drive_c /windows/Fonts

https://bugs.winehq.org/show_bug.cgi?id=46855

--- Comment #1 from Nikolay Sivov  ---
It depends on .NET API you're using. If it's System.Drawing it goes through
gdiplus.dll that, in wine, is using gdi32 API to enumerate available fonts. So
results from 'wine notepad' and gdiplus should be comparable.

[Bug 46855] system.drawing.fontfamily.families property has no access to windows fonts in drive_c /windows/Fonts

https://bugs.winehq.org/show_bug.cgi?id=46855

--- Comment #2 from IanS  ---
In my first post I included a link to system.drawing.fontfamily so yes. It is
system.drawing.

I installed dotnet40 and gdiplus

In drive_c/windows/system32 I see dgi32.dll and gdi32plus.dll

But font in /Windows/Font are still not available to the
system.drawing.fontfamily properties. It doesn't see them. It only sees the
Linux fonts.

[Bug 46855] system.drawing.fontfamily.families property has no access to windows fonts in drive_c /windows/Fonts

https://bugs.winehq.org/show_bug.cgi?id=46855

--- Comment #3 from Nikolay Sivov  ---
Why did you install gdiplus? And how did you install fonts?

[Bug 46855] system.drawing.fontfamily.families property has no access to windows fonts in drive_c /windows/Fonts

https://bugs.winehq.org/show_bug.cgi?id=46855

--- Comment #4 from IanS  ---
I can not remember why I installed gdiplus. I was doing some testing a while
ago and gdiplus was required at that time. I didn't relaize that its existance
would interfere with dotnet

OK. I create a new prefix and installed dotnet40 and microsoft core fonts. (Did
not install gdiplus)

Now the application can see the microsoft fonts. Thank you.

So it is gdiplus that 'hides' the microsoft fonts? How/Why does it do that?

What happens in future if I deploy my application and a user needs GDI for some
other application - if he installs gdiplus into the same prefix then he'll
break .net applications?

[Bug 46855] system.drawing.fontfamily.families property has no access to windows fonts in drive_c /windows/Fonts

https://bugs.winehq.org/show_bug.cgi?id=46855

--- Comment #5 from Matteo Bruni  ---
(In reply to IanS from comment #4)
> What happens in future if I deploy my application and a user needs GDI for
> some other application - if he installs gdiplus into the same prefix then
> he'll break .net applications?

"Installing" gdiplus (e.g. via winetricks) means installing a (potentially old)
Microsoft version of the DLL and enabling it in place of the gdiplus
implementation included in Wine. Ideally you shouldn't need to install native
gdiplus, any bug you experience with builtin is a Wine bug that should be
reported and eventually fixed.