Making Chinese and Japanese search indexing optional... (#1115)

* This can shave ~80 MB off the binary size while allowing users
  speaking these two languages to easily switch them back on

Cargo.lock

@@ -2817,6 +2817,7 @@ dependencies = [
  "notify",
  "open",
  "rebuild",
+ "search",
  "site",
  "termcolor",
  "tokio",

Cargo.toml

@@ -41,6 +41,7 @@ errors = { path = "components/errors" }
 front_matter = { path = "components/front_matter" }
 utils = { path = "components/utils" }
 rebuild = { path = "components/rebuild" }
+search = { path = "components/search" }
 
 [workspace]
 members = [

components/search/Cargo.toml

@@ -12,3 +12,8 @@ lazy_static = "1"
 errors = { path = "../errors" }
 library = { path = "../library" }
 config = { path = "../config" }
+
+[features]
+default = []
+indexing-zh = ["elasticlunr-rs/zh"]
+indexing-ja = ["elasticlunr-rs/ja"]

docs/content/documentation/content/multilingual.md

@@ -20,6 +20,12 @@ languages = [
 If you want to use per-language taxonomies, ensure you set the `lang` field in their
 configuration.
 
+Note: By default, Chinese and Japanese search indexing is not included. You can include
+the support by building `zola` using `cargo build --features search/indexing-ja search/indexing-zh`.
+Please also note that, enabling Chinese indexing will increase the binary size by approximately
+5 MB while enabling Japanese indexing will increase the binary size by approximately 70 MB 
+due to the incredibly large dictionaries.
+
 ## Content
 Once the languages have been added, you can start to translate your content. Zola
 uses the filename to detect the language: