postgis/faq.xml @ OSGeo Weblate

Language	Translated	Unfinished	Unfinished words	Unfinished characters	Untranslated	Checks	Suggestions	Comments
English		0	0	0	0	23	0	0

French		0	0	0	0	0	0	0

German		0	0	0	0	12	0	0

Italian	56%	41	1,298	8,447	41	10	0	0

Japanese		0	0	0	0	0	0	0

Korean	80%	19	548	3,604	19	14	0	0

Polish	0%	95	2,689	17,353	95	0	0	0

Portuguese (Brazil)	81%	18	508	3,348	18	7	0	0

Russian	0%	95	2,689	17,353	95	0	0	0

Spanish	85%	14	315	2,200	14	8	0	0

Please sign in to see the alerts.

Overview

Project website	postgis.net
Project maintainers	komzpa cvvergara strk robe
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	master
Last remote commit	Show obtained output on failure, in oriented_envelope test `36fcdd626` Sandro Santilli authored yesterday
Last commit in Weblate	Translated using Weblate (Japanese) `994b97db9` Teramoto Ikuhiro authored 2 weeks ago
Weblate repository	`https://weblate.osgeo.org/git/postgis/postgis/`
File mask	`doc/po/*/faq.xml.po`

String statistics

	Strings percent	Hosted strings	Words percent	Hosted words	Characters percent	Hosted characters
Total		950		26,890		173,530
Source		95		2,689		17,353
Approved	1%	4	1%	139	1%	963
Waiting for review	59%	569	59%	16,015	59%	102,909
Translated	70%	668	70%	18,843	69%	121,225
Needs editing	0%	0	0%	0	0%	0
Read-only	10%	95	10%	2,689	10%	17,353
Failing checks	7%	74	11%	3,053	11%	19,839
Strings with suggestions	0%	0	0%	0	0%	0
Untranslated strings	29%	282	29%	8,047	30%	52,305

Last 12 months Previous

Activity in last 12 months


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

Quick numbers

26,890

Hosted words

950

Hosted strings

70%

Translated

Contributors

and previous 30 days

Trends of last 30 days

—

Hosted words

—

Hosted strings

—

Translated

—

+100%

Contributors

—

Search

Advanced query builder

Query examples

Review strings changed by other users	`changed:>=2023-04-29 AND NOT changed_by:anonymous`	Add
Translated strings	`state:>=translated`	Add
Strings with comments	`has:comment`	Add
Strings with any failing checks	`has:check`	Add
Strings with suggestions from others	`has:suggestion AND NOT suggestion_author:anonymous`	Add
Approved strings with suggestions	`state:approved AND has:suggestion`	Add
All untranslated strings added the past month	`added:>=2023-04-29 AND state:<=needs-editing`	Add
Translated strings in a certain language	`is:translated AND language:en`	Add

None Component unlocked postgis / faq.xml	Fixing an alert automatically unlocked the component. 12 days ago
None Component locked postgis / faq.xml	The component was automatically locked because of an alert. 13 days ago
None New alert postgis / faq.xml	Could not update the repository. 13 days ago
yellow73 Translation changed postgis / faq.xml — Japanese	English The <varname>ST_DWithin(geometry, geometry, distance)</varname> function is a handy way of performing an indexed distance search. It works by creating a search rectangle large enough to enclose the distance radius, then performing an exact distance search on the indexed subset of results. Japanese 3 characters edited Current translation Translated <varname>ST_DWithin(geometry, geometry, distance)</varname>関数は、インデックス付きの距離検索を実行する手軽な方法です。この関数は、距離半径を十分に含む大きさの検索矩形を作成して、インデックス付きの結果サブセットに対して確実な距離検索を行います。 2 weeks ago
yellow73 Translation changed postgis / faq.xml — Japanese	English To use the database most efficiently, it is best to do radius queries which combine the radius test with a bounding box test: the bounding box test uses the spatial index, giving fast access to a subset of data which the radius test is then applied to. Japanese 1 character edited Current translation Translated データベースを最も効果的に使うには、半径検索とバウンディングボックス検索を組み合わせた半径検索を行うのが最も良いです。バウンディングボックス検索で空間インデックスを使用するので、半径検索が適用されるサブセットへのアクセスが早くなります。 2 weeks ago
yellow73 Translation changed postgis / faq.xml — Japanese	English R-Tree indexes in PostgreSQL are not "null safe", so building an index on a geometry column which contains null geometries will fail. Japanese 2 characters edited Current translation Translated PostgreSQLのR木インデックスは「NULLセーフ」ではなく、NULLジオメトリを含むジオメトリカラムではインデックス作成に失敗します。 2 weeks ago
yellow73 Translation changed postgis / faq.xml — Japanese	English R-Tree indexes in PostgreSQL cannot handle features which are larger than 8K in size. GiST indexes can, using the "lossy" trick of substituting the bounding box for the feature itself. Japanese 2 characters edited Current translation Translated PostgreSQLのR木インデックスは、8K以上のサイズのフィーチャーは扱えません。GiSTインデックスはフィーチャー自体の代わりにバウンディングボックスを用いる「不可逆」トリックを使っているので扱うことができます。 2 weeks ago
yellow73 Translation changed postgis / faq.xml — Japanese	English Early versions of PostGIS used the PostgreSQL R-Tree indexes. However, PostgreSQL R-Trees have been completely discarded since version 0.6, and spatial indexing is provided with an R-Tree-over-GiST scheme. Japanese 2 characters edited Current translation Translated PostGISの、かつての版では、PostgreSQLのR木インデックスを使っていましたが、0.6版でPostgreSQLのR木は完全に捨てて、R-Tree-over-GiSTスキームによる空間インデックスを提供しています。 2 weeks ago
yellow73 Translation changed postgis / faq.xml — Japanese	English Why aren't PostgreSQL R-Tree indexes supported? Japanese 1 character edited Current translation Translated なぜPostgreSQLのR木インデックス機能を持たないのですか? 2 weeks ago
yellow73 Translation changed postgis / faq.xml — Japanese	English You should also ensure that the PostgreSQL query planner has enough information about your index to make rational decisions about when to use it. To do this, you have to "gather statistics" on your geometry tables. Japanese 1 character edited Current translation Translated PostgreSQLのクエリプランナがインデックスを作るべきかについて合理的な決定を行うよう、十分な情報を確実に持てるようにすべきです。そのために、ジオメトリテーブル上で"gather statistics"を実行しなければなりません。 2 weeks ago

Browse all component changes