Wine-devel not using OS X's font handling

[MaddTheSane (C.W. Betts)]

Wine 1.5.1 added the ability for Wine to use OS X fonts by using CoreText calls. However, since the port file explicitly configures Wine to use fontconfig, this code isn't being compiled. Removing the --with-fontconfig will make Wine use the OS X code.

[MaddTheSane (C.W. Betts)]

I was wrong: it was Wine 1.5.2 that introduced Mac OS X font handling code.

[ryandesign (Ryan Carsten Schmidt)]

Is using CoreText better than using fontconfig?

[mojca (Mojca Miklavec)]

See also ​https://github.com/macports/macports-ports/pull/374

[mojca (Mojca Miklavec)]

Replying to ryandesign:

Is using CoreText better than using fontconfig?

I believe so. Fontconfig often causes long time delays when "refreshing the font database". On Mac and Windows that's particularly painful as each piece of software maintains its own database and users often assume the sofware froze and there's no way to predict when that might happen to warn the users. It's probably better in MacPorts and it should be more uniform there (just one database for the whole MP installation), but still.

[Chris Rawnsley <chris@…>]

In 5c4e58bdaa437e97cce7c92933be960ecb79be3c/macports-ports:

wine*: Remove fontconfig dependency from Darwin

On Darwin, fontconfig has been turned off in favour of using Core Text
since Wine 1.5.10.

See Wine commit 9cb7a97981

Closes: #34745