Re:Language detection with Google's Compact Language Detector
by tha-dude on Saturday October 22, 2011 @08:45AM
(#3143438)
Nice! I wrote a .NET wrapper myself, never got around to a Python extension though. One question - did you experience any memory leak issues with the CLD? Said, .NET wrapper DLL seems to leak and I never really checked if it was the C++/CLI I added on top or the actual CLD native C++ code. I doubt the latter since (according to my basic understanding) nothing is created in the original code which needs to be cleaned up manually. Before I start debugging mixed-mode .NET applications I just wanted to be sure.
Re:Language detection with Google's Compact Language Detector
by adambyrtek on Saturday October 22, 2011 @08:51AM
(#3143442)
Encoding, but obviously not language, should be provided explicitly as metadata (e.g. Content-Type HTTP header). Also, most of content available on the web is already UTF-8 (65.9% according to a recent survey[1]).
Re:Language detection with Google's Compact Language Detector
by e98cuenc on Saturday October 22, 2011 @11:20AM
(#3143655)
In my experience chardet misclassifies very often iso-8859-1 as iso-8859-2. I saw the misclassification even in small spanish pages, which were using only the typical spanish characters.
In most cases you have to know the language in order to guess the encoding and convert to UTF-8 if necessary. Mutual recursion...
[1] http://w3techs.com/technologies/details/en-utf8/all/all
http://pypi.python.org/pypi/chardet