I suspect that this a whole number of issues. But I guess I'll get the ball rolling....
Running on linux but setting X display to remote Free BSD machine warns of fake monospace font.
Setting remote display to Windows host running Xming reports X Error: BadRequest (invalid request code or no such operation) 1 Extension: 130 (XInputExtension) Minor opcode: 48 () Resource id: 0x0 X Error: BadRequest (invalid request code or no such operation) 1 Extension: 130 (XInputExtension) Minor opcode: 48 () Resource id: 0x3f Warning, fake monospace font?
The problem would appear to be centred around the fonts referenced are those of the executing host not the display. Hence to run vim-qt on linux but display on freebsd :set guifont=* displays the fonts available via the linux box not bsd.
The gtk version does this correctly.
<opinion> This is important. The main reason I want to see a qt version of gvim is for remote display. Gtk has forgotten that X is a network protocol since about 1.3. The gtk performance of large text windows (more than ~20 lines) makes gvim unusable remotely (this didn't used to be the case). It's not the case with Qt. The remote performance of vim-Qt is an order of magnitude better that standard Gtk version. Thus getting remote fonts working too would be a considerable boon. </opinion>