Overview

Project website github.com/GDQuest/learn-gdscript
Instructions for translators

Welcome to the translation Weblate for the free and open-source app Learn GDScript from Zero.

You can use Weblate to translate the application and its content. We keep translations in a dedicated repository on GitHub: https://github.com/GDQuest/learn-gdscript-translations/

You can find the application's source code with published translation in the following repository: https://github.com/GDQuest/learn-gdscript/

The app is available on itch.io to download and try on your desktop: https://gdquest.itch.io/learn-godot-gdscript

Finally, you can use the bleeding edge version of the app right in your browser at the following address: https://gdquest.github.io/learn-gdscript/staging/

When we publish translations

We publish the translations in a given language when at least 50% of the app's content is translated and peer-reviewed.

Because this app is a course to learn to code, it is not enough to just translate the interface for people to use it in their native language: without the lessons' translations, they can't use the app.

Licenses

All translations, as well as the application's source code, are MIT licensed.
Project maintainers User avatar NathanLovato
Translation license MIT License
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/GDQuest/learn-gdscript-translations
Repository branch main
Last remote commit improve output of the translation update script de2dd22
User avatar NathanLovato authored 3 weeks ago
Last commit in Weblate Translated using Weblate (German) 381395b
User avatar coru authored yesterday
Weblate repository https://hosted.weblate.org/git/learn-gdscript-from-zero/error-explanations/
File mask */lesson-13-conditions.po
Translation file Download pl/lesson-13-conditions.po
Last change Dec. 9, 2023, 9:40 p.m.
Last change made by Nathan Lovato
Language Polish
Language code pl
Text direction Left to right
Number of speakers 41,461,705
Number of plurals 3
Plural type One/few/many
Plurals One 1
Few 2, 3, 4, 22, 23, 24, 32, 33, 34, 42, …
Many 0, 5, 6, 7, 8, 9, 10, 11, 12, 13, …
Plural formula n==1 ? 0 : n%10>=2 && n%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2
yesterday

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 37 806 5,025
Translated 83% 31 55% 444 55% 2,771
Needs editing 10% 4 34% 276 34% 1,754
Read-only 0% 0 0% 0 0% 0
Failing checks 2% 1 6% 54 7% 363
Strings with suggestions 0% 0 0% 0 0% 0
Untranslated strings 5% 2 10% 86 9% 500
Last 12 months Previous

Activity in last 12 months

0 changes 0 changes 0 changes 3 changes 0 changes 0 changes 1 change 0 changes 0 changes 0 changes 0 changes 0 changes 7 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes
Nov Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct

Quick numbers

806
Hosted words
37
Hosted strings
83%
Translated
0
Contributors
and previous 30 days

Trends of last 30 days

—
Hosted words
+100%
—
Hosted strings
+100%
—
Translated
+83%
—
Contributors
—
User avatar NathanLovato

Resource updated
Parsing of the “pl/lesson-13-conditions.po” file was enforced. 11 months ago
User avatar NathanLovato

Resource updated
Parsing of the “pl/lesson-13-conditions.po” file was enforced. 11 months ago
User avatar NathanLovato

Resource updated
Parsing of the “pl/lesson-13-conditions.po” file was enforced. 11 months ago
User avatar None

Resource updated
The “pl/lesson-13-conditions.po” file was changed. a year ago
User avatar None

String updated in the repository
This series of [code]if[/code] statements is all wrong. Change the comparisons so each comparison matches the instruction below it.

Keep the values and statements as they are; only change the comparison signs.

As a reminder, the comparison signs are:
[code]
> greater than
< less than
== equal to
!= not equal to
[/code]

The line [code]health < 5:[/code] means "health is less than 5".

Because [code]health = 100[/code], this is false so [code]print("health is greater than five.")[/code] won't run.
Ta seria instrukcji [code]if[/code] jest błędna. Zmień porównania, aby każde porównanie odpowiadało znajdującemu się poniżej komunikatowi.

Zachowaj wartości i stwierdzenia takimi, jakimi są; zmień wyłącznie znaki porównania.

Przypominamy, że znaki porównania to:
[code]
> większe niż
< mniejsze niż
== równe
!= nierówne
[/code]

Wiersz [code]health < 5:[/code] oznacza „zdrowie jest mniejsze niż 5”.

Ponieważ [code]health = 100[/code] jest fałszem, komunikat [code]print("health is greater than five.")[/code] nie zostanie wyświetlony.
a year ago
User avatar None

String updated in the repository
The [code]pass[/code] keyword prevents errors in our code when a line cannot be empty.

For example, we must have a line of code after a function definition or an [code]if[/code] block. When you don't know what to write yet, you can use the [code]pass[/code] keyword as a placeholder, and Godot won't give any errors.

In the previous example, if there was nothing below the [code]if[/code] lines, Godot would give us an "Expected an indented block after 'if' " error.
 
a year ago
User avatar None

String updated in the repository
What does "pass" do in the code?
 
a year ago
User avatar None

String updated in the repository
Notice the [code]>[/code] comparison sign. We read this symbol as "greater than".

We've seen how function definitions use a colon at the end of the first line and nest content inside.

In GDScript, this syntax is a recurring pattern for all code blocks.

The computer knows which instructions belong to the condition because they are indented.
Zwróć uwagę na znak porównania [code]>[/code]. Symbol ten czytamy jako „większy niż”.

Mieliśmy już sposobność zobaczyć, jak definicje funkcji używają dwukropka na końcu pierwszego wiersza i zagnieżdża w nim treści.

W GDScript ta składnia jest powtarzającym się wzorcem dla wszystkich bloków kodu.

Komputer wie, które instrukcje należą do warunku, ponieważ są odpowiednio wcięte.
a year ago
User avatar None

String updated in the repository
When the computer checks a condition, this is called [b]to evaluate[/b] a condition. All conditions [b]evaluate[/b] to either [code]true[/code] or [code]false[/code].

Either the player is pressing the button, or not. Either the character is touching an enemy, or not.

In our case, [i]if[/i] the health goes over a maximum value, we want to reset it to the maximum.

To define a condition, we use the [code]if[/code] keyword. We write a line starting with [code]if[/code], [ignore]type the condition to evaluate, and end the line with a colon.
Gdy komputer sprawdza warunek, nazywa się to [b]oceną[/b] warunku. Wszystkie warunki [b]oceniane są[/b] albo na wartość [code]true[/code] (prawdy), albo na wartość [code]false[/code] (fałszu).

Albo gracz naciska przycisk, albo nie. Albo postać dotyka wroga, albo nie.

W naszym przypadku, [i]jeśli[/i] zdrowie przekroczy maksymalną wartość, chcemy zresetować je do maksimum.

Aby zdefiniować warunek, używamy słowa kluczowego [code]if[/code] (ang. jeśli). Piszemy wiersz rozpoczynający się od [code]if[/code], wpisujemy warunek do oceny i kończymy wiersz dwukropkiem.
a year ago
User avatar NathanLovato

Resource updated
Parsing of the “pl/lesson-13-conditions.po” file was enforced. a year ago
Browse all translation changes