https://bugs.winehq.org/show_bug.cgi?id=53770
--- Comment #18 from 399989567@qq.com --- (In reply to Sagawa from comment #15)
I can't see the picture[1]. Can you attach it here instead?
Now I have successfully uploaded the picture
Reading from the log, I see the following line (line 10034): 0100:trace:nls:GetLocaleInfoW (lcid=0x804,lctype=0x13,0021DC90,11) This shows DingTalk surely queries LOCALE_SNATIVEDIGITS.
Thanks very much, you made me sure the DingTalk used the sNativedigits
I think DingTalk just added the digit value to the code point value of 0,
Yes !!! You inspired me, I verified it on Windows 10（ In Windows 10 , I let sNativedigits became "〇一二三四五六七八九", the problem reproduce ）, your conclusion is correct, you are highly skilled。
i.e. 〇 (U+3007). For instance, 《 (U+300A) is used for 3 because 0x3007 plus three is 0x300A, 〉 (U+3009) is used for 2 because 0x3007 plus two is 0x3009, and so on. See Unicode charts for these code points[2].
I'm new to this stuff, I didn't know about this watch before you, you've given me a lot of inspiration.
How about forging sNativeDigits with another character, e.g. 零一二三四五六七八九?
In fact,I didn't catch what you meant.Do you mean for me to replace "〇一二三四五六七八九" with "零一二三四五六七八九" in the registry?
I guess you'll see Hanzi characters related 雨 like 雷, 雹, 電 in DingTalk.
[1] https://imgse.com/i/xDQICq -- s1.ax1x.com points to 127.0.0.1 at this moment. [2] https://www.unicode.org/charts/PDF/U3000.pdf