blob: 8974968149a1ffed3c00b3e4d538cd9e5a680095 [file] [log] [blame]
Name: Compact Language Detection 2
Short Name: cld_2
Version: 0
License: Apache 2.0
Security Critical: yes
The CLD is used to determine the language of text. In Chromium, this is used
to determine if Chrome should offer Translate UX to the user.
Dynamic Mode
Prior to CLD2's trunk@155, Chromium has always built CLD2 statically. The data
needed for CLD2 to perform its language detection has been compiled straight
into the binary. This contributes around 1.5 megabytes to the size of Chrome
and embeds one or more large rodata sections to the executable.
Starting with CLD2's trunk@r155, there is a new option available: dynamic mode.
In dynamic mode, CLD2 is built without its data; only the code is compiled, and
the data must be supplied at runtime via a file or a pointer to a (presumably
mmap'ed) read-only region of memory.
Tradeoffs to consider before enabling dynamic mode:
* Reduces the size of the Chromium binary by a bit over a megabyte.
* As the data file rarely changes, it can be updated independently.
* Depending upon the update process on your platform, this may also reduce
the size of Chromium updates.
* It is possible to run Chromium without CLD2 data at all (language
detection will always fail, but fails gracefully).
* Different types of CLD2 data files (larger and more accurate or smaller
and less accurate) can be dynamically downloaded or chosen depending
on runtime choices.
* Data files must be generated and checked into source control by hand.
* At runtime a data file must be opened and its headers parsed before CLD2
can be used in any given process (this time should be negligible in most
circumstances). This will prevent language detection from working until
a data file has been loaded.
To enable dynamic mode in CLD2 itself, you must define "CLD2_DYNAMIC_MODE".
In Chromium, this is controlled by the 'cld2_data_source' variable in
Building a CLD2 Dynamic Mode Data File
Note: The cld_2_dynamic_data_tool target is not currently supported on Android.
The binaries that it generates are platform-independent, but to build
the target itself you'll need a desktop environment.
1. Configure your desired table size by setting the value of "cld2_table_size"
in ../../build/common.gypi.
2. Build the "cld_2_dynamic_data_tool" target. This will generate the tool:
3. Run the tool with "--dump <file>" to generate a data file, e.g.:
${BUILD_DIR}/cld_2_dynamic_data_tool --dump /tmp/cld2_data.bin
4. (Optional) Verify that the file was correctly written:
${BUILD_DIR}/cld_2_dynamic_data_tool --verify /tmp/cld2_data.bin
The data file is suitable for use on all platforms.