Stop to use CJK

pgroonga · Oct 12, 2015 · d12e297 · d12e297
1 parent 55b5850
commit d12e297
Show file tree

Hide file tree

Showing 7 changed files with 35 additions and 25 deletions.
diff --git a/_po/ja/index.po b/_po/ja/index.po
@@ -1,7 +1,7 @@
 msgid ""
 msgstr ""
 "Project-Id-Version: PACKAGE VERSION\n"
-"PO-Revision-Date: 2015-10-12 22:56+0900\n"
+"PO-Revision-Date: 2015-10-12 23:39+0900\n"
 "Language: ja\n"
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=UTF-8\n"
@@ -59,12 +59,13 @@ msgstr ""
 "です。"
 
 msgid ""
-"As default, PostgreSQL isn't capable for CJK full text search. You can use sup"
-"er fast CJK full text search feature by installing PGroonga into your PostgreS"
-"QL!"
+"PostgreSQL supports full text search against languages that use only alphabet "
+"and digit. It means that PostgreSQL doesn't support full text search against J"
+"apanese, Chinese and so on. You can use super fast full text search feature ag"
+"ainst all languages by installing PGroonga into your PostgreSQL!"
 msgstr ""
-"デフォルトでは、PostgreSQLは日本語を全文検索できません。PGroongaをPostgreSQLにインストールすると日本語対応の超高速全文検索機能を"
-"使えるようになります！"
+"PostgreSQLはアルファベットと数値だけを使った言語の全文検索だけをサポートしています。これは、日本語や中国語などはサポートしていないということです。"
+"PGroongaをPostgreSQLにインストールすると全言語対応の超高速全文検索機能を使えるようになります！"
 
 msgid "## Documentations"
 msgstr "## ドキュメント"

diff --git a/_po/ja/overview/index.po b/_po/ja/overview/index.po
@@ -34,8 +34,10 @@ msgid ""
 msgstr ""
 
 msgid ""
-"As default, PostgreSQL isn't capable for CJK full text search. But you can use"
-" super fast CJK full text search by installing PGroonga."
+"PostgreSQL supports full text search against languages that use only alphabet "
+"and digit. It means that PostgreSQL doesn't support full text search against J"
+"apanese, Chinese and so on. You can use super fast full text search feature ag"
+"ainst all languages by installing PGroonga into your PostgreSQL!"
 msgstr ""
 
 msgid ""
@@ -47,26 +49,31 @@ msgstr ""
 msgid "## Related extensions"
 msgstr ""
 
-msgid "There are some extensions that implements CJK ready full text search:"
+msgid ""
+"There are some extensions that implements full text search against all languag"
+"es:"
 msgstr ""
 
 msgid ""
 "  * [pg_trgm](http://www.postgresql.org/docs/9.4/static/pgtrgm.html)\n"
 "    * It's bundled with PostgreSQL but it's not installed as default.\n"
-"    * You need to change pg\\_trgm source code to support CJK."
+"    * You need to change pg\\_trgm source code to support all languages."
 msgstr ""
 
 msgid ""
 "  * [pg_bigm](http://pgbigm.osdn.jp/)\n"
-"    * It supports CJK without changing source code.\n"
+"    * It supports full text search against all languages without changing sour"
+"ce code.\n"
 "    * It requires [Recheck](http://pgbigm.osdn.jp/pg_bigm_en-1-1.html#enable_r"
 "echeck) to remove false positives.\n"
 "    * Recheck is slow for many hits case. Because Recheck does sequential sear"
 "ch against records found by index search.\n"
 "    * If you disables Recheck, you may get false positives."
 msgstr ""
 
-msgid "PGroonga supports CJK without changing source code."
+msgid ""
+"PGroonga supports full text search against all languages without changing sour"
+"ce code."
 msgstr ""
 
 msgid ""

diff --git a/index.md b/index.md
@@ -21,7 +21,7 @@ layout: en
 
 PGroonga (píːzí:lúnɡά) is a PostgreSQL extension to use [Groonga](http://groonga.org/) as the index.
 
-As default, PostgreSQL isn't capable for CJK full text search. You can use super fast CJK full text search feature by installing PGroonga into your PostgreSQL!
+PostgreSQL supports full text search against languages that use only alphabet and digit. It means that PostgreSQL doesn't support full text search against Japanese, Chinese and so on. You can use super fast full text search feature against all languages by installing PGroonga into your PostgreSQL!
 
 ## Documentations
 

diff --git a/ja/index.md b/ja/index.md
@@ -20,7 +20,7 @@ layout: ja
 
 PGroonga（ぴーじーるんが）はインデックスとして[Groonga](http://groonga.org/ja/)を使うPostgreSQLの拡張機能です。
 
-デフォルトでは、PostgreSQLは日本語を全文検索できません。PGroongaをPostgreSQLにインストールすると日本語対応の超高速全文検索機能を使えるようになります！
+PostgreSQLはアルファベットと数値だけを使った言語の全文検索だけをサポートしています。これは、日本語や中国語などはサポートしていないということです。PGroongaをPostgreSQLにインストールすると全言語対応の超高速全文検索機能を使えるようになります！
 
 ## ドキュメント
 

diff --git a/ja/overview/index.md b/ja/overview/index.md
@@ -9,25 +9,25 @@ PGroonga is a PostgreSQL extension. PGroonga provides a new index that uses [Gro
 
 Groonga is an embeddable super fast full text search engine. It can be embedded into MySQL. [Mroonga](http://mroonga.org/) is a storage engine that is based on Groonga. Groonga can also work as standalone search engine. 
 
-As default, PostgreSQL isn't capable for CJK full text search. But you can use super fast CJK full text search by installing PGroonga.
+PostgreSQLはアルファベットと数値だけを使った言語の全文検索だけをサポートしています。これは、日本語や中国語などはサポートしていないということです。PGroongaをPostgreSQLにインストールすると全言語対応の超高速全文検索機能を使えるようになります！
 
 And more, PGroonga supports full text search against all text values in JSON. It's an unique feature. Built-in PostgreSQL features and [JsQuery](https://github.com/postgrespro/jsquery) don't support it.
 
 ## Related extensions
 
-There are some extensions that implements CJK ready full text search:
+There are some extensions that implements full text search against all languages:
 
   * [pg_trgm](http://www.postgresql.org/docs/9.4/static/pgtrgm.html)
     * It's bundled with PostgreSQL but it's not installed as default.
-    * You need to change pg\_trgm source code to support CJK.
+    * You need to change pg\_trgm source code to support all languages.
 
   * [pg_bigm](http://pgbigm.osdn.jp/)
-    * It supports CJK without changing source code.
+    * It supports full text search against all languages without changing source code.
     * It requires [Recheck](http://pgbigm.osdn.jp/pg_bigm_en-1-1.html#enable_recheck) to remove false positives.
     * Recheck is slow for many hits case. Because Recheck does sequential search against records found by index search.
     * If you disables Recheck, you may get false positives.
 
-PGroonga supports CJK without changing source code.
+PGroonga supports full text search against all languages without changing source code.
 
 PGroonga works without Recheck. PGroonga can find exact records only by index search. PGroonga is fast for many hits case.
 

diff --git a/overview/index.md b/overview/index.md
@@ -9,25 +9,25 @@ PGroonga is a PostgreSQL extension. PGroonga provides a new index that uses [Gro
 
 Groonga is an embeddable super fast full text search engine. It can be embedded into MySQL. [Mroonga](http://mroonga.org/) is a storage engine that is based on Groonga. Groonga can also work as standalone search engine. 
 
-As default, PostgreSQL isn't capable for CJK full text search. But you can use super fast CJK full text search by installing PGroonga.
+PostgreSQL supports full text search against languages that use only alphabet and digit. It means that PostgreSQL doesn't support full text search against Japanese, Chinese and so on. You can use super fast full text search feature against all languages by installing PGroonga into your PostgreSQL!
 
 And more, PGroonga supports full text search against all text values in JSON. It's an unique feature. Built-in PostgreSQL features and [JsQuery](https://github.com/postgrespro/jsquery) don't support it.
 
 ## Related extensions
 
-There are some extensions that implements CJK ready full text search:
+There are some extensions that implements full text search against all languages:
 
   * [pg_trgm](http://www.postgresql.org/docs/9.4/static/pgtrgm.html)
     * It's bundled with PostgreSQL but it's not installed as default.
-    * You need to change pg\_trgm source code to support CJK.
+    * You need to change pg\_trgm source code to support all languages.
 
   * [pg_bigm](http://pgbigm.osdn.jp/)
-    * It supports CJK without changing source code.
+    * It supports full text search against all languages without changing source code.
     * It requires [Recheck](http://pgbigm.osdn.jp/pg_bigm_en-1-1.html#enable_recheck) to remove false positives.
     * Recheck is slow for many hits case. Because Recheck does sequential search against records found by index search.
     * If you disables Recheck, you may get false positives.
 
-PGroonga supports CJK without changing source code.
+PGroonga supports full text search against all languages without changing source code.
 
 PGroonga works without Recheck. PGroonga can find exact records only by index search. PGroonga is fast for many hits case.
 

diff --git a/reference/pgroonga-versus-gist-and-gin.md b/reference/pgroonga-versus-gist-and-gin.md
@@ -5,7 +5,9 @@ layout: en
 
 # PGroonga versus GiST and GIN
 
-PostgreSQL provides GiST and GIN as bundled indexes. PGroonga's main feature is CJK ready fast full text search. But PGroonga also provides general propose index features for equality condition and comparison conditions. You can use PGroonga as alternative of GiST and GIN.
+PostgreSQL provides GiST and GIN as bundled indexes. You can use them for full text search against languages that use only alphabet and digit such as English. You can't use them for full text search against Japanese, Chinese and so on.
+
+PGroonga's main feature is fast full text search against all languages. But PGroonga also provides general propose index features for equality condition and comparison conditions. You can use PGroonga as alternative of GiST and GIN.
 
 This documents describes about different between PGroonga, GiST and GIN.