W3C home > Mailing lists > Public > www-international@w3.org > April to June 2000

RE: Automatic Language Detect

From: Chris Pratley <chrispr@MICROSOFT.com>
Date: Fri, 21 Apr 2000 18:43:46 -0700
Message-ID: <5F68209F7E4BD111A5F500805FFE35B91E155AB8@RED-MSG-54>
To: "'jturley@xai.com'" <jturley@xai.com>, www-international@w3.org

Just FYI, MLANG.DLL is not a secret. It is available to third parties to use
via the IEAK on http://www.microsoft.com/windows/ieak.

More detailed info on this specific aspect:
IMultiLanguage2::DetectInputCodePage method.

This is a little easier than going through Jet. More info can be had from
http://msdn.microsoft.com . Search on "MLANG".

Chris Pratley
Group Program Manager
Microsoft Word

Sent using Office10 build 1617ship wordmail on

-----Original Message-----
From: James Turley [mailto:jturley@xai.com]
Sent: April 19, 2000 4:29 PM
To: www-international@w3.org
Subject: Automatic Language Detect 


I will jump in here, re language Auto Detect for Win9x/NT/2K platforms.

I always wondered how IE5 "Autodetected" languages

through the [Right Mouse Click]-->Encoding-->AutoSelect

process. And..I was hoping never to have to write

one to support the 127 locales supported by Windows 2000.

Well...seems like you don't have to write any code, due

do some undocumented but useful features of Jet. 4.0.

While I was giving a seminar in Redmond, a reliable but

unamed PM from MS Office 2K let me in on the secret.

Microsoft Jet OLEDB 4.0 Text and installable

indexed-sequential access method (IISAM) uses

MLANG.dll which provides Language autodetect functionality

for all MS products through "Extended Properties" setting. You get

this for free with all MS OS's and maybe MacOS.

So...if you are using ADO (DAO works too, I am told)...

in VB for example, just set up an ADO connection,

set Provider as "Microsoft.Jet.OLEDB.4.0" and

set Properties("Extended Properties") = "TEXT;CharacterSet=Detect;" &


This will return an enumeration recordset of "guesses" about the locales


by your text, sorted in best guess order.

Pretty good..and you don't even have to write any code.

I think it may work on mac too.

email me offlist for some coding fragments.

Jim Turley, XAI mailto:jturley@xai.com


XA International                        14510 Big Basin Way, #240

Contract Programming Agency             Saratoga, CA 95070

International Software Engineering      mailto:info@xai.com


+1 408 741 5577 Voice                    +1 408 741 0512 FAX

-----Original Message-----

From: www-international-request@w3.org

[mailto:www-international-request@w3.org]On Behalf Of Santosh Rau (by

way of "Martin J. Duerst" <duerst@w3.org>)

Sent: Tuesday, April 18, 2000 8:58 PM

To: www-international@w3.org

Subject: Re: Japanese encoding?


Can someone point me to RFCs/documentation on how these browsers

'auto-detect' the encoding used on japanese pages ?  This is for the

case where the 'charset' is not specified. I have two URLs for which the

browsers work correctly:




Santosh Rau

Received on Friday, 21 April 2000 21:44:54 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 21 September 2016 22:37:19 UTC