Translation status

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

Strings status

430
All strings — 9,114 words Browse Translate Zen
225
Translated strings — 3,849 words Browse Translate Zen
205
Unfinished strings — 5,265 words Browse Translate Zen
143
Untranslated strings — 4,076 words Browse Translate Zen
62
Strings marked for edit — 1,189 words Browse Translate Zen
1
Strings with suggestions — 1 word Browse Translate Zen
204
Unfinished strings without suggestions — 5,264 words Browse Translate Zen
107
Strings with any failing checks — 2,812 words Browse Translate Zen
80
Translated strings with any failing checks — 2,083 words Browse Translate Zen
11
Failing check: Unchanged translation — 33 words Browse Translate Zen
90
Failing check: Trailing space — 2,681 words Browse Translate Zen
11
Failing check: Double space — 439 words Browse Translate Zen
64
Failing check: Mismatched full stop — 2,117 words Browse Translate Zen
15
Failing check: Mismatched colon — 351 words Browse Translate Zen
4
Failing check: Mismatched question mark — 63 words Browse Translate Zen
1
Failing check: Mismatched exclamation mark — 45 words Browse Translate Zen
1
Failing check: Inconsistent — 1 word Browse Translate Zen
3
Failing check: Mismatching line breaks — 32 words Browse Translate Zen
9
Failing check: XML markup — 334 words Browse Translate Zen
1
Failing check: Consecutive duplicated words — 11 words Browse Translate Zen

Other components

Component Translated Unfinished Unfinished words Unfinished characters Untranslated Checks Suggestions Comments
extras This component is linked to the postgis_branch_32/postgis repository. 0% 3 45 318 3 0 0 0
reference_relationship This component is linked to the postgis_branch_32/postgis repository. 0% 273 5,065 46,644 273 6 36 0
reference_troubleshooting This component is linked to the postgis_branch_32/postgis repository. 0% 26 407 3,121 26 2 21 0
reference_overlay This component is linked to the postgis_branch_32/postgis repository. 0% 143 2,782 24,240 143 3 14 0
reference_version This component is linked to the postgis_branch_32/postgis repository. 0% 88 709 8,318 88 1 5 0
database_tuning This component is linked to the postgis_branch_32/postgis repository. 0% 33 543 3,893 33 0 0 0
reference_cluster This component is linked to the postgis_branch_32/postgis repository. 0% 55 1,131 9,962 55 1 5 0
reference_bbox This component is linked to the postgis_branch_32/postgis repository. 0% 117 1,991 19,058 117 7 30 0
using_postgis_query This component is linked to the postgis_branch_32/postgis repository. 0% 109 2,146 16,760 109 0 0 0
reporting This component is linked to the postgis_branch_32/postgis repository. 0% 20 360 2,524 20 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 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/pt_BR/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% 225 42% 3,849 42% 26,698
Needs editing 14% 62 13% 1,189 13% 8,406
Read-only 0% 0 0% 0 0% 0
Failing checks 24% 107 30% 2,812 28% 18,192
Strings with suggestions 1% 1 1% 1 1% 4
Untranslated strings 33% 143 44% 4,076 44% 28,037
Last 12 months Previous

Activity in last 12 months

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 433 changes 0 changes
Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr May

Quick numbers

9,114
Hosted words
430
Hosted strings
52%
Translated
0
Contributors
and previous 30 days

Trends of last 30 days

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

Suggestion added

postgis_branch_32 / using_postgis_dataman — Portuguese (Brazil)

type
tipo
a year ago
User avatar None

New strings to translate

postgis_branch_32 / using_postgis_dataman — Portuguese (Brazil)

205 new strings to translate appeared to the translation. a year ago
User avatar None

Resource update

postgis_branch_32 / using_postgis_dataman — Portuguese (Brazil)

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

String updated in the repository

postgis_branch_32 / using_postgis_dataman — Portuguese (Brazil)

For more information see the Postgres manual section on <ulink url="https://www.postgresql.org/docs/current/runtime-config-query.html">Query Planning</ulink>.
 
a year ago
User avatar None

String updated in the repository

postgis_branch_32 / using_postgis_dataman — Portuguese (Brazil)

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.
 
a year ago
User avatar None

String updated in the repository

postgis_branch_32 / using_postgis_dataman — Portuguese (Brazil)

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.
 
a year ago
User avatar None

String updated in the repository

postgis_branch_32 / using_postgis_dataman — Portuguese (Brazil)

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.
 
a year ago
User avatar None

String updated in the repository

postgis_branch_32 / using_postgis_dataman — Portuguese (Brazil)

You should regularly vacuum your databases anyways. Many PostgreSQL DBAs run <command>VACUUM</command> as an off-peak cron job on a regular basis.
 
a year ago
User avatar None

String updated in the repository

postgis_branch_32 / using_postgis_dataman — Portuguese (Brazil)

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.
 
a year ago
User avatar None

String updated in the repository

postgis_branch_32 / using_postgis_dataman — Portuguese (Brazil)

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.
 
a year ago
Browse all translation changes