Qt-client configures fonts when ever its own special settings file tells that they have not been set up. This really should depend on the reality of the fonts settings.
Current situation can lead both to client to discarding, and overwriting, valid user font settings (at least when updating to a new freeciv version), and to not setting default settings when they are needed.
Setting d3f target as the settings file is likely to lose the problematic field.
Qt-client configures fonts when ever its own special settings file tells that they have not been set up. This really should depend on the reality of the fonts settings.
Current situation can lead both to client to discarding, and overwriting, valid user font settings (at least when updating to a new freeciv version), and to not setting default settings when they are needed.
Setting d3f target as the settings file is likely to lose the problematic field.