Windows Vista introduced the concept of three pseudo-locales:
Pseudo Locale Locale Name LCID
=================== =========== ======
Base
It looks like rather than fixing the localization bugs in .NET, SQL Server, Excel, etc, Microsoft changed the Pseudo locale in Windows 10 to mask the bugs:
| Item | Windows 7 | Windows 10 |
|-----------------------|--------------------------|-----------------------|
| Locale Identifier | 0x0501 (1281) | 0x0501 (1281) |
| Locale Name | qps-ploc | qps-ploc |
| Example Number | --123,,4567,,8901 | -123,,4567,,8901 |
| Example Currency | --$$123,,4567,,8901..00 | -$123,,4567,,8901.000 |
| Example Float | --123,,4567,,8901..00 | -123,,4567,,8901.000 |
| Example Date | 9//08//2015 | 9/8/2015 |
| Example Time | 9::51::17 АΜ | 9:45:09 |
| Example DateTime | 9//08//2015 9::51::17 АΜ | 9/8/2015 9:45 |
| LOCALE_SLANGUAGE | Pseudo Language (Pseudo) | Pseudo (Pseudo) |
| LOCALE_SENGLANGUAGE | Pseudo Language | Pseudo |
| LOCALE_SDECIMAL | .. | . |
| LOCALE_SCURRENCY | $$ | $ |
| LOCALE_SMONDECIMALSEP | .. | . |
| LOCALE_SDATE | // | / |
| LOCALE_STIME | :: | : |
| LOCALE_SSHORTDATE | d//MM//yyyy | d/MM/yy |
| LOCALE_STIMEFORMAT | h::mm::ss tt | H:mm:ss |
| LOCALE_ITIME | 0 | 1 |
| LOCALE_ICENTURY | 1 | 0 |
| LOCALE_SNEGATIVESIGN | -- | - |
I can understand not wanting to fix your bugs, because you're lazy it's too hard. But you should have been forced to wear your shame for all to see.
Instead you cop-out and try to hide your failure. That's just bad.