https://bugs.winehq.org/show_bug.cgi?id=42563
Linards linards.liepins@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |linards.liepins@gmail.com
--- Comment #14 from Linards linards.liepins@gmail.com --- (In reply to Rafał Mużyło from comment #13)
(In reply to Zebediah Figura from comment #12)
(In reply to Rafał Mużyło from comment #11)
Yet, as for the later part:
- IIRC, the idea of using ExtTextOut was one I've picked from wine source
- under fontconfig, only the program can guarantee the font picked is
actually *printed* monospace, the font itself is a system/user preference
It seems to me that if the user sets the default monospace font to something that is not monospace, then it's not our responsibility to enforce otherwise...
Well, Liberation Mono is sufficiently monospace for native (that is Linux) programs, I didn't dig deep enough into wine to figure out why it isn't for wine.
Also, some of wine's font handling is plain weird - see two of my bugs, for example:
- bug 41687: my hackish fix is made in place which should affect only
unaliased bitmap fonts, yet it fixes the opposite cases
- bug 42606: for some reason, wrong codepage is picked for the font, leading
to mojibake
OK, only the first one might be tangentially relevant, I'm just (yet again) fishing for hints.
Still, per wiki page: "Liberation Mono is styled closer to Liberation Sans than Monotype's Courier New, though its metrics match with Courier New.".
Is this issue still present?