Translation status

5,579 Strings
23%
Browse Translate
99,720 Words
19%
713,033 Characters
20%

Strings status

Strings Words Characters
5,579 99,720 713,033
All strings Browse Translate Zen
2,131 37,290 259,953
Translated strings Browse Translate Zen
2,131 37,290 259,953
Strings waiting for review Browse Translate Zen
3,448 62,430 453,080
Unfinished strings Browse Translate Zen
3,064 55,909 406,914
Untranslated strings Browse Translate Zen
384 6,521 46,166
Strings marked for edit Browse Translate Zen
5 7 112
Strings with suggestions Browse Translate Zen
3,443 62,423 452,968
Unfinished strings without suggestions Browse Translate Zen
1,189 24,183 161,851
Strings with any failing checks Browse Translate Zen
809 17,700 115,986
Translated strings with any failing checks Browse Translate Zen
139 664 5,682
Failing check: Unchanged translation Browse Translate Zen
677 16,957 108,479
Failing check: Trailing space Browse Translate Zen
157 4,536 31,614
Failing check: Double space Browse Translate Zen
594 15,678 99,961
Failing check: Mismatched full stop Browse Translate Zen
24 517 3,280
Failing check: Mismatched colon Browse Translate Zen
5 66 367
Failing check: Mismatched question mark Browse Translate Zen
2 75 537
Failing check: Mismatched exclamation mark Browse Translate Zen
35 483 3,036
Failing check: Multiple capitals Browse Translate Zen
377 6,428 45,500
Failing check: Has been translated Browse Translate Zen
2 72 504
Failing check: Mismatching line breaks Browse Translate Zen
37 976 7,631
Failing check: XML markup Browse Translate Zen
14 390 2,914
Failing check: Chars around XML tags Browse Translate Zen
7 210 1,440
Failing check: Consecutive duplicated words Browse Translate Zen

Summary

Project website postgis.net
Project maintainers4 User avatar robeUser avatar strkUser avatar cvvergaraUser avatar komzpa
Project reviewers13 User avatar robeUser avatar strkUser avatar cvvergaraUser avatar dkastlUser avatar komzpaUser avatar astrid_emdeUser avatar jsanzUser avatar andischiUser avatar yoichiUser avatar jefUser avatar thayerayUser avatar yellow73User avatar jonnyforest
Translation license Creative Commons Attribution Share Alike 3.0 Unported
Translation process
  • Translations can be made directly.
  • Translation suggestions can be made.
  • Translations are reviewed by dedicated reviewers.
  • 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 Group contributor aliases in mailmap e8ca3455
Darafei Praliaskouski authored 06/23/2026
Last commit in Weblate Group contributor aliases in mailmap e8ca3455
Darafei Praliaskouski authored 06/23/2026
Weblate repository https://weblate.osgeo.org/git/postgis/postgis-manual/
File mask doc/po/*/postgis-manual.po
Translation file Download doc/po/pt_BR/postgis-manual.po
Last change June 18, 2026, 1:32 p.m.
Last change made by None
Language Portuguese (Brazil)
Language code pt_BR
Text direction Left to right
Case sensitivity Case-sensitive
Number of speakers 200,247,320
Number of plurals 2
Plural type One/other
Plurals Singular 0, 1
Plural 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, …
Plural formula n > 1
06/22/2026

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 5,579 99,720 713,033
Approved 0% 0 0% 0 0% 0
Waiting for review 38% 2,131 37% 37,290 36% 259,953
Translated 38% 2,131 37% 37,290 36% 259,953
Needs editing 6% 384 6% 6,521 6% 46,166
Read-only 0% 0 0% 0 0% 0
Failing checks 21% 1,189 24% 24,183 22% 161,851
Strings with suggestions 1% 5 1% 7 1% 112
Untranslated strings 54% 3,064 56% 55,909 57% 406,914
Last 12 months Previous

Activity in last 12 months

82 changes 0 changes 44 changes 74 changes 47 changes 21 changes 23 changes 0 changes 0 changes 0 changes 64 changes 267 changes 7 changes 3 changes 11 changes 0 changes 0 changes 4 changes 0 changes 17 changes 19 changes 0 changes 56 changes 0 changes
JunJulAugSepOctNovDecJanFebMarAprMay

Quick numbers

99,720
Hosted words
5,579
Hosted strings
38%
Translated
3
Contributors
and previous 30 days

Trends of last 30 days

+1%
Hosted words
+100%
+1%
Hosted strings
+100%
−1%
Translated
+38%
+100%
Contributors
—
User avatar komzpa

Resource updated
Parsing of the “doc/po/pt_BR/postgis-manual.po” file was enforced. 06/18/2026
User avatar None

Resource updated
The “doc/po/pt_BR/postgis-manual.po” file was changed. 06/13/2026
User avatar None

String added in the repository
If the optional <code>gridSize</code> parameter is given (GEOS-3.9.0 or higher required), all result vertices are guaranteed to fall on a snap-rounded grid of the specified size. Note that operations performed on a grid may contain small artifacts produced during grid alignment, see <xref linkend="ST_ReducePrecision"/>.
 
06/13/2026
User avatar None

String added in the repository
For example, consider a linear dataset representing a road network. It may be required to identify all road segments that cross each other, not at a point, but in a line (perhaps to validate a business rule such as ensuring that no two different roads share a common segment). In this case <xref linkend="ST_Crosses"/> does not provide the necessary spatial filter, since for linear features it returns <varname>true</varname> only where they cross at a point.
 
06/13/2026
User avatar None

String added in the repository
The coordinate dimension (2, 3 or 4) of the column. The coordinate dimension is at least 2, representing X and Y coordinates.
 
06/13/2026
User avatar None

String added in the repository
By default, all distance and area calculations are done on the spheroid. You should find that the results of calculations in local areas match up well with local planar results in good local projections. Over larger areas, the spheroidal calculations will be more accurate than any calculation done on a projected plane. The difference is that the spheroid takes into account the curvature and non-spherical shape of the Earth, whereas planar calculations assume a flat surface.
 
06/13/2026
User avatar None

String added in the repository
The <varname>geometry</varname> data type is <emphasis>opaque</emphasis>, which means that all access is done via invoking functions on geometry values. Functions allow creating geometry objects, accessing or updating all internal fields, and computing new geometry values. PostGIS supports all the functions specified in the OGC <link xlink:href="https://portal.ogc.org/files/?artifact_id=25354"><emphasis>Simple feature access - Part 2: SQL option</emphasis></link> (SFS) specification, as well many others. See <xref linkend="reference"/> for the full list of functions.
 
06/13/2026
User avatar None

String added in the repository
A MultiPolygon is a collection of non-overlapping, non-adjacent Polygons. Polygons in the collection may touch only at a finite number of points. (Two polygons are adjacent if they share an edge. They touch if they share only points or edges on their boundaries). For more details on MultiPolygon validity, see <xref linkend="OGC_Validity"/>.
 
06/13/2026
User avatar None

String added in the repository
The OGC geometry model defines validity rules for each geometry type. These rules ensure that geometry values represents realistic situations (e.g. it is possible to specify a polygon with a hole lying outside its shell, but this makes no sense geometrically and is thus invalid). PostGIS also allows storing and manipulating invalid geometry values. This allows detecting and fixing them if needed. See <xref linkend="OGC_Validity"/>
 
06/13/2026
User avatar None

String added in the repository
The geometry model allows evaluating topological spatial relationships as described in <xref linkend="DE-9IM"/>. To support this the concepts of <emphasis role="bold">interior</emphasis>, <emphasis role="bold">boundary</emphasis> and <emphasis role="bold">exterior</emphasis> are defined for each geometry type. Geometries are topologically closed, so they always contain their boundary. The boundary is a geometry of dimension one less than that of the geometry itself. For example, the boundary of a Polygon is its rings (LineStrings), the boundary of a LineString is its endpoints (Points), and the boundary of a Point is empty.
 
06/13/2026
Browse all translation changes