drfrag wrote: I guess may be it's due to the removal of the automatic language detection name not being in unicode format?
Yeah, I was gonna say... what makes you think the automatic language detection has anything to do with it? But then I saw you strike that out.
I had a peek at the
i_dijoy.cpp file, and needless to say it's a very ancient work that has not been updated in a very long time.
If it is what you stated you suspect it is, however, it would not be consistently kanji script. Kanji takes up a very small portion of the Unicode table, and if there was an issue converting from CP 1272 to Unicode then the letters would be seemingly random from all over the place.
The automatic language detection removal seems to be a more likely culprit, but I have no way to confirm this right now. The joystick code is calling WMI to get the list of joysticks. It still has ancient code in there to support Windows 2000 that should probably be removed at this point.
I suspect this is one of those things that's not going to be fixed unless it's by a Windows developer who has a controller.
[quote="drfrag"] I guess may be it's due to the [s]removal of the automatic language detection[/s] name not being in unicode format?[/quote]
Yeah, I was gonna say... what makes you think the automatic language detection has anything to do with it? But then I saw you strike that out.
I had a peek at the [url=https://github.com/coelckers/gzdoom/commits/master/src/win32/i_dijoy.cpp]i_dijoy.cpp[/url] file, and needless to say it's a very ancient work that has not been updated in a very long time.
If it is what you stated you suspect it is, however, it would not be consistently kanji script. Kanji takes up a very small portion of the Unicode table, and if there was an issue converting from CP 1272 to Unicode then the letters would be seemingly random from all over the place.
The automatic language detection removal seems to be a more likely culprit, but I have no way to confirm this right now. The joystick code is calling WMI to get the list of joysticks. It still has ancient code in there to support Windows 2000 that should probably be removed at this point.
I suspect this is one of those things that's not going to be fixed unless it's by a Windows developer who has a controller.