--
v2: vkd3d-shader/hlsl: Get rid of the check_invalid_matrix_modifiers() helper.
vkd3d-shader/hlsl: Apply latent majority modifiers to typedefs as well.
vkd3d-shader/hlsl: Do not set an initial latent matrix majority.
vkd3d-shader/hlsl: Store the matrix majority as a type modifiers bitmask.
vkd3d-shader/hlsl: Apply latent type modifiers to matrix array typedefs.
tests: Add more tests for pack_matrix pragmas.
https://gitlab.winehq.org/wine/vkd3d/-/merge_requests/102
Otherwise it's not clear which clauses in vkd3d_shader_compile() really
apply to other functions. For example, many of the functions currently
refering to vkd3d_shader_compile() don't even take a vkd3d_shader_compile_info
parameter.
--
https://gitlab.winehq.org/wine/vkd3d/-/merge_requests/110
The extension is now part of Xlib. It might be disabled through the `XKB_DISABLE=1` environment variable (https://gitlab.freedesktop.org/xorg/lib/libx11/-/blob/master/src/xkb/XKBUse…) but I don't see why we have to support that case.
I think assuming that it is always usable will make the keyboard code simpler, though I have no idea if it exists some environment without it nowadays. All recent desktop environment rely on Xkb to support keyboard layouts, especially when multiple layouts are configured (which are grouped four by four in a single X keyboard mapping, using Xkb groups).
--
v2: winex11: Assume that Xkb extension is availabe.
https://gitlab.winehq.org/wine/wine/-/merge_requests/2297
When dmSize is zero or greter than size of input buffer, `IsValidDevmodeW()`
failed in Windows 10.
But current implementation in wine, it will return `true` because
there is no check to `dm.dmSize`.
--
v12: winspool: Check dmSize in IsValidDevmodeW()
https://gitlab.winehq.org/wine/wine/-/merge_requests/2262
When dmSize is zero or greter than size of input buffer, `IsValidDevmodeW()`
failed in Windows 10.
But current implementation in wine, it will return `true` because
there is no check to `dm.dmSize`.
--
v11: winspool: Check dmSize in IsValidDevmodeWw
https://gitlab.winehq.org/wine/wine/-/merge_requests/2262
Windows 11 uses a narrow non-breaking space instead of a plain one when formatting numbers. This is probably more correct and maybe Wine should switch too. But marking the old result as broken() would require unbundling expect_wstr() which would be bothersome.
So this commit just accepts both.
--
v3: kernel32/tests: Fix the French GetNumberFormatEx() test on Windows 11.
https://gitlab.winehq.org/wine/wine/-/merge_requests/2288