Download the PHP package nitotm/efficient-language-detector without Composer

Efficient Language Detector

What is a language detector?
It is a tool that identifies which language a text is written in. For example, detect("Gracias") returns "es" for Spanish.

Efficient language detector (Nito-ELD or ELD) is a fast and accurate natural language detection software, written 100% in PHP, with a speed comparable to fast C++ compiled detectors, and accuracy rivaling the best detectors to date.

It has no dependencies, easy installation, all it's needed is PHP with the mb extension.

ELD is also available in: Javascript (v2), C Library (v3, includes Python package & executable), and an outdated Python (v1) implementation. ELD PHP is v3.

1. Installation
2. How to use
3. Benchmarks
4. Databases
5. Testing
6. Languages

Installation

• --prefer-dist will omit tests/, misc/ & benchmark/, or use --prefer-source to include everything
• Install nitotm/efficient-language-detector:dev-main to try the last unstable changes
• Alternatively, download / clone the files can work just fine.
  (Only small DB install under construction)

ELD execution options

• ELD has database execution Modes: array, string, bytes, disk
• ELD database Sizes: small, medium, large, extralarge
• Confused? No worries, use default with no arguments. How to use

Low memory Modes
For Modes string, bytes and disk, all size databases can run with 128MB PHP default setting
disk mode with extralarge size, can run with almost no RAM as it only uses 0.5MB
string and bytes are a great choice for general use, as they are just ~2x slower than array

Fastest Mode: Array (higher memory usage)
For array Mode it is recommended to use OPcache, specially for the larger databases to reduce load times
We need to set opcache.interned_strings_buffer, opcache.memory_consumption high enough for each database

Check Databases for more info.

How to use?

detect() expects a UTF-8 string and returns an object with a language property, containing an ISO 639-1 code (or other selected scheme), or 'und' for undetermined language.

To select database Size and Mode, or language output scheme. We can import Eld... constants to see avalible options.

Languages subsets

Calling langSubset() once, will set the subset.

• In array mode the first call takes longer as it creates a new database, if save enabled (default), it will be loaded next time we make the same subset.
• In modes string, bytes & disk, a "virtual" subset is created instantly, detect() will just remove unwanted languages before returning results.
• To load a subset with 0 overhead, we can feed the returned file by langSubset() in array mode, when creating the instance LanguageDetector(file)
  • To make use of pre-built subsets in modes string, bytes & disk, getting lower memory usage and increased speed, it is possible by manually converting an array database, using BlobDataBuilder()
• Check available Languages below.

Other Functions

There is a CLI wrapper (BETA version)
>./bin/eld --help on Linux.
>php bin/eld --help on Windows.

Benchmarks

I compared ELD with a different variety of detectors, as there are not many in PHP.

Benchmarks:

• Tatoeba: 18MB, short sentences from Tatoeba, 50 languages supported by all contenders, up to 10k lines each.

  • For Tatoeba, I limited all detectors to the 50 languages subset, making the comparison as fair as possible.
  • Also, Tatoeba is not part of ELD training dataset (nor tuning), but it is for fasttext

• ELD Test: 10MB, sentences from the 60 languages supported by ELD, 1000 lines each. Extracted from the 60GB of ELD training data.
• Sentences: 8MB, sentences from Lingua benchmark, minus unsupported languages and Yoruba which had broken characters.
• Word pairs and Single words, ~1MB, also from Lingua, same 53 languages.

Time execution benchmark for ELD size large ( check others sizes at more benchmarks )

• Lingua participates with 54 languages, Franc with 58, patrickschur with 54.
• fasttext does not have a built-in subset option, so to show its accuracy and speed potential I made two benchmarks, fasttext-all not being limited by any subset at any test
• ^* Google's CLD2 also lacks subset option, and it's difficult to make a subset even with its option bestEffort = True, as usually returns only one language, so it has a comparative disadvantage.
• Time is normalized: (total lines * time) / processed lines

Databases

Low memory database modes

Modes 'bytes' and 'string' are very similar, they differ on how they are load, and are just 2x slower than Array
Mode 'string' can be OPcache'd, more expensive compilation, but then instant load, 'bytes' has always a steady ~fast load
Special mention to 'disk' mode, while slower, is the fastest uncached load & detect for the larger databases

Fastest mode Array, but memory hungry

• * I recommend using more than enough interned_strings_buffer as buffers overflow error might delay server response.
  To use all databases opcache.interned_strings_buffer should be a minimum of 160MB (170MB).
• When choosing the amount of memory keep in mind opcache.memory_consumption includes opcache.interned_strings_buffer.
  • If OPcache memory is 230MB, interned_strings is 32MB, and medium DB is 69MB cached, we have a total of (230 -32 -69) = 129MB of OPcache for everything else.
• Also, if you are going to use a subset of languages in addition to the main database, or multiple subsets, increase opcache.memory accordingly if you want them to be loaded instantly. To cache all default databases comfortably you would want to set it at 1200MB.

Testing

Default composer install might not include these files. Use --prefer-source to include them.

• For dev environment with composer "autoload-dev" (root only), the following will execute the tests

• Or, you can also run the tests executing the following file:

• To run the accuracy benchmarks run the benchmark/bench.php file.

Languages

• These are the ISO 639-1 codes that include the 60 languages. Plus 'und' for undetermined
  It is the default ELD language scheme. outputScheme: 'ISO639_1'

am, ar, az, be, bg, bn, ca, cs, da, de, el, en, es, et, eu, fa, fi, fr, gu, he, hi, hr, hu, hy, is, it, ja, ka, kn, ko, ku, lo, lt, lv, ml, mr, ms, nl, no, or, pa, pl, pt, ro, ru, sk, sl, sq, sr, sv, ta, te, th, tl, tr, uk, ur, vi, yo, zh

• These are the 60 supported languages for Nito-ELD. outputScheme: 'FULL_TEXT'

Amharic, Arabic, Azerbaijani (Latin), Belarusian, Bulgarian, Bengali, Catalan, Czech, Danish, German, Greek, English, Spanish, Estonian, Basque, Persian, Finnish, French, Gujarati, Hebrew, Hindi, Croatian, Hungarian, Armenian, Icelandic, Italian, Japanese, Georgian, Kannada, Korean, Kurdish (Arabic), Lao, Lithuanian, Latvian, Malayalam, Marathi, Malay (Latin), Dutch, Norwegian, Oriya, Punjabi, Polish, Portuguese, Romanian, Russian, Slovak, Slovene, Albanian, Serbian (Cyrillic), Swedish, Tamil, Telugu, Thai, Tagalog, Turkish, Ukrainian, Urdu, Vietnamese, Yoruba, Chinese

• ISO 639-1 codes with IETF BCP 47 script name tag. outputScheme: 'ISO639_1_BCP47'

am, ar, az-Latn, be, bg, bn, ca, cs, da, de, el, en, es, et, eu, fa, fi, fr, gu, he, hi, hr, hu, hy, is, it, ja, ka, kn, ko, ku-Arab, lo, lt, lv, ml, mr, ms-Latn, nl, no, or, pa, pl, pt, ro, ru, sk, sl, sq, sr-Cyrl, sv, ta, te, th, tl, tr, uk, ur, vi, yo, zh

• ISO 639-2/T codes (which are also valid 639-3) outputScheme: 'ISO639_2T'. Also available with BCP 47 ISO639_2T_BCP47

amh, ara, aze, bel, bul, ben, cat, ces, dan, deu, ell, eng, spa, est, eus, fas, fin, fra, guj, heb, hin, hrv, hun, hye, isl, ita, jpn, kat, kan, kor, kur, lao, lit, lav, mal, mar, msa, nld, nor, ori, pan, pol, por, ron, rus, slk, slv, sqi, srp, swe, tam, tel, tha, tgl, tur, ukr, urd, vie, yor, zho

Donations and suggestions

If you wish to donate for open source improvements, hire me for private modifications, request alternative dataset training, or contact me, please use the following link: https://linktr.ee/nitotm