Builtin gdiplus behaves as documented but tests are indicating that Windows behaviour sometimes differs from the documentation.
I believe this issue is at least one of the contributing issues to bug https://bugs.winehq.org/show_bug.cgi?id=46947, if not the sole issue. I propose that this flag be disabled until it is well understood. I noticed as issue with DrawString seeming to ignore the flag sometimes(sometimes the text fits without any noticeable defects which I believe is the case with the program in the bug) and sometimes even drawing clipped text with the flag on. Other times it works as expected. I can't seem to find a pattern to identify that could be used to predict its behaviour.
Signed-off-by: David Kahurani k.kahurani(a)gmail.com
--
v4: gdiplus: Fix StringFormatFlagsLineLimit handling
https://gitlab.winehq.org/wine/wine/-/merge_requests/3407
--
v2: vkd3d-shader/tpf: Check buffer->status in add_section().
vkd3d-shader/d3dbc: Return ctx->result from hlsl_sm1_write().
vkd3d-shader/d3dbc: Free vkd3d_bytecode_buffer data on failure.
https://gitlab.winehq.org/wine/vkd3d/-/merge_requests/288