Translation status

501 Strings 100%
Browse Translate
10,833 Words 100%

Strings status

501
All strings — 10,833 words Browse Translate Zen
501
Translated strings — 10,833 words Browse Translate Zen
49
Strings with any failing checks — 1,537 words Browse Translate Zen
49
Translated strings with any failing checks — 1,537 words Browse Translate Zen
11
Failing check: Unchanged translation — 16 words Browse Translate Zen
1
Failing check: Starting spaces — 76 words Browse Translate Zen
19
Failing check: Mismatched full stop — 507 words Browse Translate Zen
1
Failing check: Mismatched colon — 6 words Browse Translate Zen
1
Failing check: Mismatched exclamation mark — 51 words Browse Translate Zen
1
Failing check: Inconsistent — 2 words Browse Translate Zen
5
Failing check: Mismatching line breaks — 415 words Browse Translate Zen
12
Failing check: XML markup — 510 words Browse Translate Zen
1
Failing check: Consecutive duplicated words — 33 words Browse Translate Zen

Other components

Component Translated Unfinished Unfinished words Unfinished characters Untranslated Checks Suggestions Comments
reference_troubleshooting This component is linked to the postgis_branch_32/postgis repository. 0% 26 407 3,121 26 2 26 0
reference_overlay This component is linked to the postgis_branch_32/postgis repository. 0% 143 2,782 24,240 143 3 132 0
reference_version This component is linked to the postgis_branch_32/postgis repository. 0% 88 709 8,318 88 1 88 0
database_tuning This component is linked to the postgis_branch_32/postgis repository. 0% 33 543 3,893 33 0 33 0
reference_cluster This component is linked to the postgis_branch_32/postgis repository. 0% 55 1,131 9,962 55 1 47 0
reference_bbox This component is linked to the postgis_branch_32/postgis repository. 0% 117 1,991 19,058 117 7 116 0
using_postgis_query This component is linked to the postgis_branch_32/postgis repository. 0% 109 2,146 16,760 109 0 92 0
reference_srs This component is linked to the postgis_branch_32/postgis repository. 0% 54 978 8,949 54 3 53 0
reference_validation This component is linked to the postgis_branch_32/postgis repository. 0% 68 1,270 11,073 68 5 67 0
usage This component is linked to the postgis_branch_32/postgis repository. 0% 2 10 177 2 0 0 0
Browse all components

Overview

Project website postgis.net
Translation process
  • Translations can be made directly.
  • Translation suggestions can be made.
  • Any authenticated user can contribute.
  • The translation uses bilingual files.
Source code repository https://git.osgeo.org/gitea/postgis/postgis.git
Repository branch stable-3.2
Last remote commit Push to 3.2.6dev milestone 6e2c5206d
Regina Obe authored yesterday
Weblate repository https://weblate.osgeo.org/git/postgis_branch_32/postgis/
File mask doc/po/*/using_postgis_dataman.xml.po
Translation file Download doc/po/ja/using_postgis_dataman.xml.po
Last change None
Last author None

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 501 10,833 75,777
Translated 100% 501 100% 10,833 100% 75,777
Needs editing 0% 0 0% 0 0% 0
Read-only 0% 0 0% 0 0% 0
Failing checks 9% 49 14% 1,537 16% 12,239
Strings with suggestions 0% 0 0% 0 0% 0
Untranslated strings 0% 0 0% 0 0% 0
Last 12 months Previous

Activity in last 12 months

0 changes 502 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes
May Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr

Quick numbers

10,833
Hosted words
501
Hosted strings
100%
Translated
0
Contributors
and previous 30 days

Trends of last 30 days

—
Hosted words
—
—
Hosted strings
—
—
Translated
—
—
Contributors
—
User avatar None

Resource update

postgis_branch_32 / using_postgis_dataman — Japanese

File doc/po/ja/using_postgis_dataman.xml.po was added. a year ago
User avatar None

String updated in the repository

postgis_branch_32 / using_postgis_dataman — Japanese

For more information see the Postgres manual section on <ulink url="https://www.postgresql.org/docs/current/runtime-config-query.html">Query Planning</ulink>.
詳細情報についてはPostgreSQLマニュアルの<ulink url="https://www.postgresql.jp/document/current/html/runtime-config-query.html">問い合わせ計画</ulink>節をご覧下さい。
a year ago
User avatar None

String updated in the repository

postgis_branch_32 / using_postgis_dataman — Japanese

If <command>SET ENABLE_SEQSCAN TO OFF;</command> does not help your query, the query may be using a SQL construct that the Postgres planner is not yet able to optimize. It may be possible to rewrite the query in a way that the planner is able to handle. For example, a subquery with an inline SELECT may not produce an efficient plan, but could possibly be rewritten using a LATERAL JOIN.
<command>SET ENABLE_SEQSCAN TO OFF;</command>がクエリの助けにならないなら、クエリはPostgreSQLプランナがまだ最適化できないSQL構成なのかも知れません。プランナが処理できるようにクエリを再記述できるかもしれません。例えば、インラインSELECTを持つ副問い合わせがあると、効果的なプランを作らないことがあり、LATERAL JOINを使うように書き換えることができます。
a year ago
User avatar None

String updated in the repository

postgis_branch_32 / using_postgis_dataman — Japanese

If <command>SET ENABLE_SEQSCAN TO OFF;</command> helps your query to run faster, your Postgres is likely not tuned for your hardware. If you find the planner wrong about the cost of sequential versus index scans try reducing the value of <varname>RANDOM_PAGE_COST</varname> in <code>postgresql.conf</code>, or use <command>SET RANDOM_PAGE_COST TO 1.1;</command>. The default value for <varname>RANDOM_PAGE_COST</varname> is 4.0. Try setting it to 1.1 (for SSD) or 2.0 (for fast magnetic disks). Decreasing the value makes the planner more likely to use index scans.
<command>SET ENABLE_SEQSCAN TO OFF;</command>でクエリ速度が向上する場合には、PostgreSQLのハードウェア関連のチューンが行われていないのかも知れません。プランナがシーケンシャル対インデックスのコストが誤っている場合には、<code>postgresql.conf</code>内にある<varname>RANDOM_PAGE_COST</varname>の値を変更してみて下さい。<command>SET RANDOM_PAGE_COST TO 1.1;</command>とします。<varname>RANDOM_PAGE_COST</varname>のデフォルト値は4.0です。1.1 (SSDの場合)または2.0 (高速磁気ディスクの場合)を試してみて下さい。値を小さくするほど、プランナがインデックススキャンをしやすくなります。
a year ago
User avatar None

String updated in the repository

postgis_branch_32 / using_postgis_dataman — Japanese

If vacuuming does not help, you can temporarily force the planner to use the index information by using the command <command>SET ENABLE_SEQSCAN TO OFF;</command>. This way you can check whether the planner is at all able to generate an index-accelerated query plan for your query. You should only use this command for debugging; generally speaking, the planner knows better than you do about when to use indexes. Once you have run your query, do not forget to run <command>SET ENABLE_SEQSCAN TO ON;</command> so that the planner will operate normally for other queries.
VACUUMが役に立たない場合には、<command>SET ENABLE_SEQSCAN TO OFF;</command>コマンドを使用して、一時的にプランナにインデックス情報の使用を強制することができます。この方法で、プランナがインデックス使用を多くしたクエリプランを生成できるかどうかを確認できます。このコマンドはデバッグにのみ使用してください。一般的に言えば、プランナはインデックスを使用するタイミングをよく知っています。クエリを実行したら<command>SET ENABLE_SEQSCAN TO ON;</command>を実行して、他のクエリでは通常操作にすることを忘れないでください。
a year ago
User avatar None

String updated in the repository

postgis_branch_32 / using_postgis_dataman — Japanese

You should regularly vacuum your databases anyways. Many PostgreSQL DBAs run <command>VACUUM</command> as an off-peak cron job on a regular basis.
データベースに対する定期的なvacuumは常に実行するべきです。多くのPostgreSQLデータベースエージェントは、閑散時のcronジョブとして定期的に<command>VACUUM</command>を実行します。
a year ago
User avatar None

String updated in the repository

postgis_branch_32 / using_postgis_dataman — Japanese

Make sure statistics are gathered about the number and distributions of values in a table, to provide the query planner with better information to make decisions around index usage. <command>VACUUM ANALYZE</command> will compute both.
テーブル内の値の数量と分布に関する統計情報を収集するとともに、クエリプランナにインデックス使用にかかる意思決定のための、より良い情報を与えるようにします。<command>VACUUM ANALYZE</command>は両方を計算します。
a year ago
User avatar None

String updated in the repository

postgis_branch_32 / using_postgis_dataman — Japanese

Examine the query plan and check your query actually computes the thing you need. An erroneous JOIN, either forgotten or to the wrong table, can unexpectedly retrieve table records multiple times. To get the query plan, execute with <code>EXPLAIN</code> in front of the query.
クエリプランの試験とクエリの確認で、必要なものを計算できます。誤ったJOINや忘れ去られたテーブルや間違ったテーブルでは、予期しないテーブルレコード検索が複数回行われることがありえます。クエリプランを得るにはクエリの先頭に<code>EXPLAIN</code>を付けて実行します。
a year ago
User avatar None

String updated in the repository

postgis_branch_32 / using_postgis_dataman — Japanese

If you find your spatial indexes are not being used, there are a few things you can do:
空間インデックスが使われていないのが分かった場合には、少しの行えることがあります。
a year ago
User avatar None

String updated in the repository

postgis_branch_32 / using_postgis_dataman — Japanese

Ordinarily, indexes invisibly speed up data access: once an index is built, the PostgreSQL query planner automatically decides when to use it to improve query performance. But there are some situations where the planner does not choose to use existing indexes, so queries end up using slow sequential scans instead of a spatial index.
通常、インデックスは知らないうちにデータアクセスの速度を向上します。ひとたびインデックスを構築すれば、PostgreSQLクエリプランナは自動的にクエリの能率を向上させるために使うべきかどうかを決定します。しかし、プランナが既存のインデックスを選択せず、遅いシーケンシャルスキャンを使い続ける場合があります。
a year ago
Browse all translation changes