postgis-workshop

validity

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

	German	0%	34	797	5,076	34	0	0	0

	Japanese		0	0	0	0	0	0	0

	Spanish	5%	32	794	5,055	32	0	0	0

Please sign in to see the alerts.

Overview

Project website	postgis.net/workshops/postgis-intro
Project maintainers	komzpa yellow73 dmateos dkastl astrid_emde jsanz andischi cvvergara jef
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://github.com/postgis/postgis-workshops.git`
Repository branch	master
Last remote commit	Merge pull request #126 from enockseth/fix-typo `9925f56` Paul Ramsey authored yesterday
Last commit in Weblate	Translated using Weblate (Japanese) `0f44c94` Teramoto Ikuhiro authored a month ago
Weblate repository	`https://weblate.osgeo.org/git/postgis-workshop/index/`
File mask	`postgis-intro/sources/locale/*/LC_MESSAGES/validity.po`

2 weeks ago

String statistics

	Strings percent	Hosted strings	Words percent	Hosted words	Characters percent	Hosted characters
Total		136		3,188		20,304
Source		34		797		5,076
Translated	51%	70	50%	1,597	50%	10,173
Needs editing	0%	0	0%	0	0%	0
Read-only	25%	34	25%	797	25%	5,076
Failing checks	0%	0	0%	0	0%	0
Strings with suggestions	0%	0	0%	0	0%	0
Untranslated strings	48%	66	49%	1,591	49%	10,131

Last 12 months Previous

Activity in last 12 months


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

Quick numbers

3,188

Hosted words

136

Hosted strings

51%

Translated

and previous 30 days

Trends of last 30 days

—

Hosted words

+100%

—

Hosted strings

+100%

+1%

Translated

+50%

+100%

Contributors

—

Search

Advanced query builder

Query examples

Review strings changed by other users	`changed:>=2024-06-26 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:>=2024-06-26 AND state:<=needs-editing`	Add
Translated strings in a certain language	`is:translated AND language:en`	Add

None Changes committed postgis-workshop validity Spanish	Changes committed a month ago
dmateos Translation added postgis-workshop validity Spanish	English Function List Spanish 18 characters edited Current translation Translated Lista de funciones a month ago
dmateos Contributor joined postgis-workshop validity Spanish	Contributor joined a month ago
None Changes committed postgis-workshop validity Japanese	Changes committed 8 months ago
yellow73 Translation changed postgis-workshop validity Japanese	English What's going on here? The algorithm that calculates area assumes that rings do not self-intersect. A well-behaved ring will always have the area that is bounded (the interior) on one side of the bounding line (it doesn't matter which side, just that it is on one side). However, in our (poorly behaved) figure-eight, the bounded area is to the right of the line for one lobe and to the left for the other. This causes the areas calculated for each lobe to cancel out (one comes out as 1, the other as -1) hence the "zero area" result. Japanese 6 characters edited Current translation Translated ここで何が起こっているのでしょう? 面積計算のアルゴリズムはリングは自己交差インタセクトしない前提で計算しています。行儀の良いリングは常に境界線の一方側 (どちらが内部でもよくて、一方でいいです)に (内部に) 区切られた領域を持ちます。しかしながら、行儀の悪い8の字ポリゴン内では、二つある区切られた領域の一つはラインの右側で区切られ、もう一つは左側で区切られます。これによって、両方でキャンセルしあうような面積計算になり (一方が 1 で、もう一方が -1 です)、故に「面積 0」の結果となります。 8 months ago
yellow73 Suggestion accepted postgis-workshop validity Japanese	English What's going on here? The algorithm that calculates area assumes that rings do not self-intersect. A well-behaved ring will always have the area that is bounded (the interior) on one side of the bounding line (it doesn't matter which side, just that it is on one side). However, in our (poorly behaved) figure-eight, the bounded area is to the right of the line for one lobe and to the left for the other. This causes the areas calculated for each lobe to cancel out (one comes out as 1, the other as -1) hence the "zero area" result. Japanese 248 characters edited Translated ここで何が起こっているのでしょう? 面積計算のアルゴリズムはリングは自己交差しない前提で計算しています。行儀の良いリングは常に境界線の一方側 (どちらが内部でもよくて、一方でいいです)に (内部に) 区切られた領域を持ちます。しかしながら、行儀の悪い8の字ポリゴン内では、二つある区切られた領域の一つはラインの右側で区切られ、もう一つは左側で区切られます。これによって、両方でキャンセルしあうような面積計算になり (一方が 1 で、もう一方が -1 です)、故に「面積 0」の結果となります。 8 months ago
yellow73 Suggestion accepted postgis-workshop validity Japanese	English Let's see what the database thinks the area of our polygon is: Japanese 31 characters edited Current translation Translated データベースがこのポリゴンの面積をどう考えるか見てみましょう: 8 months ago
yellow73 Suggestion accepted postgis-workshop validity Japanese	English The outer ring is actually a figure-eight, with a self-intersection in the middle. Note that the graphic routines successfully render the polygon fill, so that visually it is appears to be an "area": two one-unit squares, so a total area of two units of area. Japanese 111 characters edited Current translation Translated 外側リングは実際に算用数字の8の字になっていて、真ん中で自己接触しています。描画ルーティンはポリゴンの内部の色塗りに成功して、二つの1面積単位の正方形からなり、合計2面積単位となる「領域」が見えていることに注意して下さい。 8 months ago
yellow73 Suggestion accepted postgis-workshop validity Japanese	English You can see the invalidity a little more clearly in this diagram: Japanese 25 characters edited Current translation Translated この図では、もう少しはっきりと不正性が分かります: 8 months ago
yellow73 Suggestion accepted postgis-workshop validity Japanese	English Here's an example of why structure matters. This polygon is invalid: Japanese 30 characters edited Current translation Translated 構造が重要である理由の例を示します。このポリゴンは不正です: 8 months ago

Browse all component changes