postgis_branch_32/using_postgis_dataman

Translation status

430	Strings		52%	Browse Translate
9,114	Words		42%	Browse Translate

Strings status

430	All strings — 9,114 words	Browse Translate Zen
224	Translated strings — 3,848 words	Browse Translate Zen
206	Unfinished strings — 5,266 words	Browse Translate Zen
82	Untranslated strings — 1,964 words	Browse Translate Zen
124	Strings marked for edit — 3,302 words	Browse Translate Zen
1	Strings with suggestions — 1 word	Browse Translate Zen
205	Unfinished strings without suggestions — 5,265 words	Browse Translate Zen
59	Strings with any failing checks — 1,699 words	Browse Translate Zen
21	Translated strings with any failing checks — 358 words	Browse Translate Zen
8	Failing check: Unchanged translation — 17 words	Browse Translate Zen
1	Failing check: Trailing space — 37 words	Browse Translate Zen
4	Failing check: Double space — 130 words	Browse Translate Zen
20	Failing check: Mismatched full stop — 517 words	Browse Translate Zen
11	Failing check: Mismatched colon — 242 words	Browse Translate Zen
1	Failing check: Inconsistent — 1 word	Browse Translate Zen
8	Failing check: Mismatching line breaks — 240 words	Browse Translate Zen
21	Failing check: XML markup — 907 words	Browse Translate Zen
1	Failing check: Consecutive duplicated words — 8 words	Browse Translate Zen

Other components

Component	Translated	Unfinished	Unfinished words	Unfinished characters	Untranslated	Checks	Suggestions	Comments
extras	0%	3	45	318	3	0	0	0

reference_troubleshooting	0%	26	407	3,121	26	2	21	0

reference_overlay	0%	143	2,782	24,240	143	3	11	0

reference_version	0%	88	709	8,318	88	1	5	0

database_tuning	0%	33	543	3,893	33	0	0	0

reference_cluster	0%	55	1,131	9,962	55	1	5	0

reference_bbox	0%	117	1,991	19,058	117	7	30	0

using_postgis_query	0%	109	2,146	16,760	109	0	0	0

reporting	0%	20	360	2,524	20	0	0	0

reference_relationship	0%	273	5,065	46,644	273	6	36	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 2 days ago
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/ko_KR/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		430		9,114		63,141
Translated	52%	224	42%	3,848	42%	26,685
Needs editing	28%	124	36%	3,302	36%	23,178
Read-only	0%	0	0%	0	0%	0
Failing checks	13%	59	18%	1,699	19%	12,360
Strings with suggestions	1%	1	1%	1	1%	13
Untranslated strings	19%	82	21%	1,964	21%	13,278

Last 12 months Previous

Activity in last 12 months


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

Quick numbers

9,114

Hosted words

430

Hosted strings

52%

Translated

Contributors

and previous 30 days

Trends of last 30 days

—

Hosted words

—

Hosted strings

—

Translated

—

Contributors

—

None Suggestion added postgis_branch_32 / using_postgis_dataman — Korean	English ST_Intersects Korean 13 characters edited ST_Intersects a year ago
None New strings to translate postgis_branch_32 / using_postgis_dataman — Korean	206 new strings to translate appeared to the translation. a year ago
None Resource update postgis_branch_32 / using_postgis_dataman — Korean	File `doc/po/ko_KR/using_postgis_dataman.xml.po` was added. a year ago
None String updated in the repository postgis_branch_32 / using_postgis_dataman — Korean	English For more information see the Postgres manual section on <ulink url="https://www.postgresql.org/docs/current/runtime-config-query.html">Query Planning</ulink>. Korean 0 characters edited Current translation a year ago
None String updated in the repository postgis_branch_32 / using_postgis_dataman — Korean	English 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. Korean 0 characters edited Current translation a year ago
None String updated in the repository postgis_branch_32 / using_postgis_dataman — Korean	English 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. Korean 203 characters edited Current translation Needs editing 쿼리 설계자가 순차 및 인덱스 스캔의 경중(cost)을 잘못 판단하고 있다면, postgresql.conf 파일의 random_page_cost의 값을 줄여보거나 "SET random_page_cost=#"로 써보십시오. 해당 파라미터의 기본값은 4이지만, 1또는 2로 설정해보십시오. 값을 감소시킬수록 점점 더 쿼리 설계자가 인덱스 스캔을 활용하게 될 것입니다. a year ago
None String updated in the repository postgis_branch_32 / using_postgis_dataman — Korean	English 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. Korean 303 characters edited Current translation Needs editing 두 번째, 빈공간 분석으로 해결이 안 될 경우 <command>SET ENABLE_SEQSCAN=OFF</command> 명령어를 통해 강제로 쿼리 설계자가 인덱스 정보를 이용하도록 할 수 있습니다. 이 명령어는 공간 인덱스 쿼리일 경우에 한해 드물게 이용해야 합니다. 일반적으로, 쿼리 설계자는 언제 일반 B-Tree 인덱스를 활용해야 하는지 사용자보다 더 잘 알고 있습니다. 사용자 쿼리 실행 후, 다른 쿼리가 평소처럼 쿼리 설계자를 활용하도록 <varname>ENABLE_SEQSCAN</varname> 을 다시 켤지 고려해봐야 합니다. a year ago
None String updated in the repository postgis_branch_32 / using_postgis_dataman — Korean	English You should regularly vacuum your databases anyways. Many PostgreSQL DBAs run <command>VACUUM</command> as an off-peak cron job on a regular basis. Korean 0 characters edited Current translation a year ago
None String updated in the repository postgis_branch_32 / using_postgis_dataman — Korean	English 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. Korean 0 characters edited Current translation a year ago
None String updated in the repository postgis_branch_32 / using_postgis_dataman — Korean	English 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. Korean 0 characters edited Current translation a year ago

Browse all translation changes

Quick downloads

430	File in original format as translated in the repository	gettext PO file
430	All strings, converted files enriched with comments; suitable for offline translation	CSV	gettext MO	gettext PO	TBX	TMX	XLIFF 1.1 with gettext extensions	XLIFF 1.1	XLSX
206	Unfinished strings, converted files enriched with comments; suitable for offline translation	CSV	gettext MO	gettext PO	TBX	TMX	XLIFF 1.1 with gettext extensions	XLIFF 1.1	XLSX

Customize download

Search

Advanced query builder

Query examples

Review strings changed by other users	`changed:>=2023-05-01 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-05-01 AND state:<=needs-editing`	Add