I wrote: > A quick look indicates that Windows uses "language identifiers": > http://msdn.microsoft.com/library/psdk/winbase/nls_8xo3.htm >=20 > Maybe Bill can dig up some better way to do this (a "language > identifier to language code" table would be nice. There's one > in Windows 2000 ;-) nevermind; I've crafted a piece of code that digs out the RFC 1766 language code (e.g. en-EN) and the code page (e.g. cp1252), on Win98/NT4/2000. unfortunately, Win95 won't give me the language code; it insists on using "language identifiers" (such as 041d). guess we need a table after all. oh well. patch follows. </F>
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4