# Godot Engine Documentation in Serbian (latin)
# Copyright (C) 2014-2022, Juan Linietsky, Ariel Manzur and the Godot community (CC-BY 3.0)
# This file is distributed under the same license as the Godot Engine package.
#
# BLu <blmasfon@gmail.com>, 2018.
# Marko Mihajlović <creationsmarko@gmail.com>, 2022.
# Milos Ponjavusic <brane@branegames.com>, 2018.
# Petar Ples <against.time.petar@gmail.com>, 2018.
# Vojislav Bajakic <ch3d4.ns@gmail.com>, 2018.
#
msgid ""
msgstr ""
"Project-Id-Version: Godot Engine latest\n"
"Report-Msgid-Bugs-To: https://github.com/godotengine/godot-docs-l10n\n"
"POT-Creation-Date: 2024-05-10 15:20+0200\n"
"PO-Revision-Date: 2022-02-26 10:27+0000\n"
"Last-Translator: Marko Mihajlović <creationsmarko@gmail.com>\n"
"Language-Team: Serbian (latin) <https://hosted.weblate.org/projects/godot-"
"engine/godot-docs/sr_Latn/>\n"
"Language: sr_Latn\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Plural-Forms: nplurals=3; plural=n%10==1 && n%100!=11 ? 0 : n%10>=2 && "
"n%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2;\n"
"X-Generator: Weblate 4.11.1-dev\n"

#: ../../docs/_templates/versions.html:26
#: ../../docs/tutorials/performance/cpu_optimization.rst:149
msgid "Languages"
msgstr ""

#: ../../docs/_templates/versions.html:32
msgid "Versions"
msgstr ""

#: ../../docs/_templates/versions.html:39
msgid "On Read the Docs"
msgstr ""

#: ../../docs/_templates/versions.html:41
#, fuzzy
msgid "Project Home"
msgstr "Uvod / Početak"

#: ../../docs/_templates/versions.html:44
msgid "Builds"
msgstr ""

#: ../../docs/_templates/versions.html:47
msgid "Downloads"
msgstr ""

#: ../../docs/index.rst:65 ../../docs/about/docs_changelog.rst:179
#: ../../docs/tutorials/inputs/mouse_and_input_coordinates.rst:7
#: ../../docs/tutorials/scripting/gdscript/gdscript_advanced.rst:7
#: ../../docs/contributing/development/core_and_modules/variant_class.rst:7
msgid "About"
msgstr "O Godot-u"

#: ../../docs/index.rst:79
#: ../../docs/tutorials/platform/android/android_in_app_purchases.rst:13
#: ../../docs/contributing/documentation/contributing_to_the_documentation.rst:15
msgid "Getting started"
msgstr "Uvod / Početak"

#: ../../docs/index.rst:94
msgid "Manual"
msgstr ""

#: ../../docs/index.rst:128
msgid "Contributing"
msgstr ""

#: ../../docs/index.rst:140 ../../docs/about/docs_changelog.rst:191
msgid "Community"
msgstr "Zajednica"

#: ../../docs/index.rst:151
msgid "Class reference"
msgstr ""

#: ../../docs/index.rst:2
#, fuzzy
msgid "Godot Docs – *4.2* branch"
msgstr "Godot dokumentacija - *glavna* grana"

#: ../../docs/index.rst:6
msgid ""
"Godot's documentation is available in various languages and versions. Expand "
"the \"Read the Docs\" panel at the bottom of the sidebar to see the list."
msgstr ""

#: ../../docs/index.rst:12
msgid ""
"This documentation is translated from the `original English one <https://"
"docs.godotengine.org/en/stable>`_ by community members on `Weblate <https://"
"hosted.weblate.org/projects/godot-engine/godot-docs>`_."
msgstr ""

#: ../../docs/index.rst:16
msgid ""
"Depending on the translation effort's completion level, you may find "
"paragraphs or whole pages which are still in English. You can help the "
"community by providing new translations or reviewing existing ones on "
"Weblate."
msgstr ""

#: ../../docs/index.rst:21
msgid ""
"For the time being, localized translations are only available for the "
"\"stable\" branch. You can still view the English documentation for other "
"engine versions using the \"Read the Docs\" panel at the bottom of the "
"sidebar."
msgstr ""

#: ../../docs/index.rst:26
#, fuzzy
msgid ""
"Welcome to the official documentation of `Godot Engine <https://godotengine."
"org>`__, the free and open source community-driven 2D and 3D game engine! If "
"you are new to this documentation, we recommend that you read the :ref:"
"`introduction page <doc_about_intro>` to get an overview of what this "
"documentation has to offer."
msgstr ""
"Dobrodošli na oficijalnu dokumentaciju Godo Endžina, endžina za izradu "
"igara, koji je besplatan otvorenog koda i vođen od stane zajednice. Ako prvi "
"put pristupate dokumentaciji, preporucujemo vam da procitate više o tome na :"
"ref:`introduction page <doc_about_intro>`, kako bi ste imali uvid u to šta "
"vam ova dokumentacija pruža."

#: ../../docs/index.rst:32
#, fuzzy
msgid ""
"The table of contents in the sidebar should let you easily access the "
"documentation for your topic of interest. You can also use the search "
"function in the top-left corner."
msgstr ""
"Index ili tabelu sadržaja, koju možete pogledati ispod ili u sajdbaru, vam "
"omogućava da lako pretražite dokumentaciju po temama koje vas interesuju. "
"Takođe možete koristiti funkciju pretraži u gornjem levom ćošku."

#: ../../docs/index.rst:36
msgid "Get involved"
msgstr ""

#: ../../docs/index.rst:38
msgid ""
"Godot Engine is an open source project developed by a community of "
"volunteers. The documentation team can always use your feedback and help to "
"improve the tutorials and class reference. If you don't understand "
"something, or cannot find what you are looking for in the docs, help us make "
"the documentation better by letting us know!"
msgstr ""
"Godo Endžin je projekat otvorenog koda razvijen od strane zajednice "
"volontera. Timu koji se bavi dokumentacijom su uvek dobrodošli vaši "
"komentari i pomoć da se unaprede tutorijali i reference klasa. Ako nešto ne "
"razumete ili ne možete pronaći u dokumentaciji, pomozite nam da učinimo "
"dokumentaciju boljom, tako što ćete nas kontaktirati!"

#: ../../docs/index.rst:44
msgid ""
"Submit an issue or pull request on the `GitHub repository <https://github."
"com/godotengine/godot-docs/issues>`_, help us `translate the documentation "
"<https://hosted.weblate.org/engage/godot-engine/>`_ into your language, or "
"talk to us on the ``#documentation`` channel on the `Godot Contributors Chat "
"<https://chat.godotengine.org/>`_!"
msgstr ""

#: ../../docs/index.rst:50
msgid "weblate_widget"
msgstr ""

#: ../../docs/<rst_epilog>:0
msgid "Translation status"
msgstr ""

#: ../../docs/index.rst:52
#, fuzzy
msgid "Offline documentation"
msgstr "Organizacija dokumentacije"

#: ../../docs/index.rst:54
msgid ""
"To browse the documentation offline, you can `download an HTML copy <https://"
"nightly.link/godotengine/godot-docs/workflows/build_offline_docs/master/"
"godot-docs-html-master.zip>`__ for offline reading (updated every Monday). "
"Extract the ZIP archive then open the top-level ``index.html`` in a web "
"browser."
msgstr ""

#: ../../docs/index.rst:58
msgid ""
"For mobile devices or e-readers, you can also `download an ePub copy "
"<https://nightly.link/godotengine/godot-docs/workflows/build_offline_docs/"
"master/godot-docs-epub-master.zip>`__ for offline reading (updated every "
"Monday). Extract the ZIP archive then open the ``GodotEngine.epub`` file in "
"an e-book reader application."
msgstr ""

#: ../../docs/about/introduction.rst:4
#: ../../docs/getting_started/introduction/index.rst:8
#: ../../docs/tutorials/best_practices/introduction_best_practices.rst:4
#: ../../docs/tutorials/best_practices/project_organization.rst:7
#: ../../docs/tutorials/best_practices/version_control_systems.rst:7
#: ../../docs/tutorials/editor/managing_editor_features.rst:9
#: ../../docs/tutorials/2d/2d_transforms.rst:7
#: ../../docs/tutorials/2d/2d_lights_and_shadows.rst:7
#: ../../docs/tutorials/2d/2d_meshes.rst:9
#: ../../docs/tutorials/2d/2d_sprite_animation.rst:7
#: ../../docs/tutorials/2d/2d_antialiasing.rst:16
#: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:7
#: ../../docs/tutorials/2d/2d_movement.rst:7
#: ../../docs/tutorials/2d/using_tilesets.rst:7
#: ../../docs/tutorials/2d/using_tilemaps.rst:13
#: ../../docs/tutorials/3d/using_transforms.rst:7
#: ../../docs/tutorials/3d/3d_text.rst:7
#: ../../docs/tutorials/3d/3d_rendering_limitations.rst:7
#: ../../docs/tutorials/3d/standard_material_3d.rst:7
#: ../../docs/tutorials/3d/lights_and_shadows.rst:7
#: ../../docs/tutorials/3d/particles/index.rst:10
#: ../../docs/tutorials/3d/high_dynamic_range.rst:9
#: ../../docs/tutorials/3d/3d_antialiasing.rst:16
#: ../../docs/tutorials/3d/using_multi_mesh_instance.rst:9
#: ../../docs/tutorials/3d/mesh_lod.rst:22
#: ../../docs/tutorials/3d/using_gridmaps.rst:7
#: ../../docs/tutorials/animation/2d_skeletons.rst:9
#: ../../docs/tutorials/animation/animation_tree.rst:7
#: ../../docs/tutorials/audio/audio_buses.rst:9
#: ../../docs/tutorials/audio/audio_streams.rst:9
#: ../../docs/tutorials/audio/sync_with_audio.rst:9
#: ../../docs/tutorials/export/feature_tags.rst:7
#: ../../docs/tutorials/io/saving_games.rst:7
#: ../../docs/tutorials/io/binary_serialization_api.rst:9
#: ../../docs/tutorials/i18n/internationalizing_games.rst:7
#: ../../docs/tutorials/i18n/pseudolocalization.rst:7
#: ../../docs/tutorials/inputs/input_examples.rst:7
#: ../../docs/tutorials/math/vector_math.rst:7
#: ../../docs/tutorials/math/matrices_and_transforms.rst:7
#: ../../docs/tutorials/networking/ssl_certificates.rst:9
#: ../../docs/tutorials/performance/index.rst:7
#: ../../docs/tutorials/performance/general_optimization.rst:7
#: ../../docs/tutorials/performance/gpu_optimization.rst:7
#: ../../docs/tutorials/physics/using_area_2d.rst:7
#: ../../docs/tutorials/physics/using_character_body_2d.rst:7
#: ../../docs/tutorials/physics/ray-casting.rst:7
#: ../../docs/tutorials/physics/ragdoll_system.rst:7
#: ../../docs/tutorials/physics/kinematic_character_2d.rst:7
#: ../../docs/tutorials/platform/android/android_plugin.rst:7
#: ../../docs/tutorials/plugins/editor/import_plugins.rst:13
#: ../../docs/tutorials/plugins/editor/3d_gizmos.rst:9
#: ../../docs/tutorials/rendering/viewports.rst:7
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_basics.rst:7
#: ../../docs/tutorials/scripting/gdextension/what_is_gdextension.rst:7
#: ../../docs/tutorials/scripting/gdextension/gdextension_cpp_example.rst:7
#: ../../docs/tutorials/scripting/debug/custom_performance_monitors.rst:7
#: ../../docs/tutorials/scripting/pausing_games.rst:7
#: ../../docs/tutorials/scripting/filesystem.rst:7
#: ../../docs/tutorials/scripting/singletons_autoload.rst:7
#: ../../docs/tutorials/scripting/scene_tree.rst:7
#: ../../docs/tutorials/scripting/scene_unique_nodes.rst:7
#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:7
#: ../../docs/tutorials/shaders/your_first_shader/your_first_2d_shader.rst:7
#: ../../docs/tutorials/shaders/shader_materials.rst:7
#: ../../docs/tutorials/shaders/screen-reading_shaders.rst:7
#: ../../docs/tutorials/shaders/using_viewport_as_texture.rst:7
#: ../../docs/tutorials/shaders/custom_postprocessing.rst:7
#: ../../docs/tutorials/shaders/advanced_postprocessing.rst:7
#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:7
#: ../../docs/contributing/development/best_practices_for_engine_contributors.rst:7
#: ../../docs/contributing/development/core_and_modules/2d_coordinate_systems.rst:7
#: ../../docs/contributing/development/core_and_modules/custom_godot_servers.rst:7
#: ../../docs/contributing/development/core_and_modules/custom_resource_format_loaders.rst:7
#: ../../docs/contributing/development/core_and_modules/custom_audiostreams.rst:7
#: ../../docs/contributing/development/editor/editor_style_guide.rst:7
#: ../../docs/community/asset_library/submitting_to_assetlib.rst:7
msgid "Introduction"
msgstr "Uvod"

#: ../../docs/about/introduction.rst:11
#, fuzzy
msgid ""
"Welcome to the official documentation of **Godot Engine**, the free and open "
"source community-driven 2D and 3D game engine! Behind this mouthful, you "
"will find a powerful yet user-friendly tool that you can use to develop any "
"kind of game, for any platform and with no usage restriction whatsoever."
msgstr ""
"Dobrodošli u zvaničnu dokumentaciju Godot Engine-a, besplatnog 2D i 3D "
"pokretača igre otvorenog koda. Iza tog dugog objašnjenja, krije se moćna "
"alatka, ali prilagođena korisniku, koju možete koristiti da razvijete bilo "
"kakvu igru, za bilo koju platformu, uz nepostojeća ograničenja."

#: ../../docs/about/introduction.rst:16
#, fuzzy
msgid ""
"This page gives a broad overview of the engine and of this documentation, so "
"that you know where to start if you are a beginner or where to look if you "
"need information on a specific feature."
msgstr ""
"Ova stranica ima za cilj da naširoko predstavi pokretač igre i sadržaj ove "
"dokumentacije, tako da znate odakle da krenete ako ste početnik ili gdje da "
"tražite ako su vam potrebne informacije o posebnim funkcijama."

#: ../../docs/about/introduction.rst:21
msgid "Before you start"
msgstr ""

#: ../../docs/about/introduction.rst:23
msgid ""
"The :ref:`Tutorials and resources <doc_community_tutorials>` page lists "
"video tutorials contributed by the community. If you prefer video to text, "
"consider checking them out. Otherwise, :ref:`Getting Started "
"<doc_getting_started_intro>` is a great starting point."
msgstr ""

#: ../../docs/about/introduction.rst:28
msgid ""
"In case you have trouble with one of the tutorials or your project, you can "
"find help on the various :ref:`Community channels <doc_community_channels>`, "
"especially the Godot `Discord`_ community and `Forum <https://forum."
"godotengine.org/>`_."
msgstr ""

#: ../../docs/about/introduction.rst:34
msgid "About Godot Engine"
msgstr "O Godot pokretaču igre"

#: ../../docs/about/introduction.rst:36
#, fuzzy
msgid ""
"A game engine is a complex tool and difficult to present in a few words. "
"Here's a quick synopsis, which you are free to reuse if you need a quick "
"write-up about Godot Engine:"
msgstr ""
"Pokretač igre je složen alat i zbog toga je teško predstaviti Godot u par "
"riječi. Ipak, prilažemo našu PR prezentaciju, koju slobodno možete koristiti "
"ako vam je potreban kratak članak o Godot pokretaču igre."

#: ../../docs/about/introduction.rst:40
#, fuzzy
msgid ""
"Godot Engine is a feature-packed, cross-platform game engine to create 2D "
"and 3D games from a unified interface. It provides a comprehensive set of "
"common tools, so that users can focus on making games without having to "
"reinvent the wheel. Games can be exported with one click to a number of "
"platforms, including the major desktop platforms (Linux, macOS, Windows), "
"mobile platforms (Android, iOS), as well as Web-based platforms and consoles."
msgstr ""
"Godot je pokretač igre koji je ispunjen funkcijama, sa mogućnostima rada na "
"više platformi, koji se koristi za pravljenje 2D i 3D igara iz jednog "
"sučelja. Godot pruža obiman skup često korištenih alata, tako da se svaki "
"korisnik može fokusirati na pravljenje igara bez potrebe za \"izmišljanjem "
"točka\". Igre se mogu izvesti jednim klikom na više platformi, uključujući "
"najpoznatije desktop platforme (Linux, macOS, Windows) kao i mobilne "
"(Android, iOS) te platforme bazirane na web-u (HTML5)."

#: ../../docs/about/introduction.rst:47
#, fuzzy
msgid ""
"Godot is completely free and open source under the :ref:`permissive MIT "
"license <doc_complying_with_licenses>`. No strings attached, no royalties, "
"nothing. Users' games are theirs, down to the last line of engine code. "
"Godot's development is fully independent and community-driven, empowering "
"users to help shape their engine to match their expectations. It is "
"supported by the `Godot Foundation <https://godot.foundation/>`_ not-for-"
"profit."
msgstr ""
"Godo je otvorenog koda i u potpunosti besplatan, objavljen pod veoma "
"popustljivom MIT licencom. Bez ikakvih obaveza, dodatnih plaćanja, bilo "
"čega. Igre koje korisnici naprave su njihove, sve do posljednje linije koda. "
"Godoov razvoj je u potpunosti nezavisan i nošen zajednicom, dajući moć "
"korisnicima da pomognu razvoj pokretača igre kako bi on ispunio njihova "
"očekivanja. Podržan je od strane 'Software Freedom Conservancy' <https://"
"sfconservancy.org> i neprofitan."

#: ../../docs/about/introduction.rst:57
msgid "Organization of the documentation"
msgstr "Organizacija dokumentacije"

#: ../../docs/about/introduction.rst:59
msgid "This documentation is organized into several sections:"
msgstr ""

#: ../../docs/about/introduction.rst:61
#, fuzzy
msgid ""
"**About** contains this introduction as well as information about the "
"engine, its history, its licensing, authors, etc. It also contains the :ref:"
"`doc_faq`."
msgstr ""
":ref:`sec-general` sekcija sadrži ovaj uvod kao i informacije o pokretaču "
"igre, istoriji, licenci, autorima itd. Takođe sadrži :ref:`doc_faq`."

#: ../../docs/about/introduction.rst:64
#, fuzzy
msgid ""
"**Getting Started** contains all necessary information on using the engine "
"to make games. It starts with the :ref:`Step by step <toc-learn-"
"step_by_step>` tutorial which should be the entry point for all new users. "
"**This is the best place to start if you're new!**"
msgstr ""
":ref:`sec-learn` sekcija je srž ove dokumentacije, jer sadrži sve potrebne "
"podatke o korištenju pokretača igre radi pravljenja igara. Započinje sa :ref:"
"`Step by step <toc-learn-step_by_step>` uputstvom koji bi trebao da bude "
"početna tačka za sve nove korisnike."

#: ../../docs/about/introduction.rst:68
#, fuzzy
msgid ""
"The **Manual** can be read or referenced as needed, in any order. It "
"contains feature-specific tutorials and documentation."
msgstr ""
"S druge strane, :ref:`sec-tutorials` sekcija se može čitati u bilo kojem "
"redosljedu. Sadrži mnoga uputstva i dokumentaciju koja objašnjava "
"pojedinačne funkcije."

#: ../../docs/about/introduction.rst:70
msgid ""
"**Contributing** gives information related to contributing to Godot, whether "
"to the core engine, documentation, demos or other parts. It describes how to "
"report bugs, how contributor workflows are organized, etc. It also contains "
"sections intended for advanced users and contributors, with information on "
"compiling the engine, contributing to the editor, or developing C++ modules."
msgstr ""

#: ../../docs/about/introduction.rst:76
#, fuzzy
msgid ""
"**Community** is dedicated to the life of Godot's community. It points to "
"various community channels like the `Godot Contributors Chat <https://chat."
"godotengine.org/>`_ and `Discord`_ and contains a list of recommended third-"
"party tutorials and materials outside of this documentation."
msgstr ""
":ref:`sec-community` poglavlje sadrži informacije vezane za doprinos razvoja "
"endžina za igre i života zajednice, tj. kako prijaviti greške, pomoći sa "
"dokumentacijom itd. Takođe daje uputstva za razne kanale  koje zajednica "
"koristi, IRC i Discord,te sadrži listu preporučenih tutorijala napravljenih "
"od strane spoljnih saradnika."

#: ../../docs/about/introduction.rst:81
msgid ""
"Finally, the **Class reference** documents the full Godot API, also "
"available directly within the engine's script editor. You can find "
"information on all classes, functions, signals and so on here."
msgstr ""

#: ../../docs/about/introduction.rst:85
#, fuzzy
msgid ""
"In addition to this documentation, you may also want to take a look at the "
"various `Godot demo projects <https://github.com/godotengine/godot-demo-"
"projects>`_."
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati različite Godo demo projekte "
"`Godot demo projects <https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/about/introduction.rst:89
#, fuzzy
msgid "About this documentation"
msgstr "O dokumentaciji"

#: ../../docs/about/introduction.rst:91
msgid ""
"Members of the Godot Engine community continuously write, correct, edit, and "
"improve this documentation. We are always looking for more help. You can "
"also contribute by opening Github issues or translating the documentation "
"into your language. If you are interested in helping, see :ref:`Ways to "
"contribute <doc_ways_to_contribute>` and :ref:`Writing documentation "
"<doc_contributing_writing_documentation>`, or get in touch with the "
"`Documentation team <https://godotengine.org/teams/#documentation>`_ on "
"`Godot Contributors Chat <https://chat.godotengine.org/>`_."
msgstr ""

#: ../../docs/about/introduction.rst:99
#, fuzzy
msgid ""
"All documentation content is licensed under the permissive Creative Commons "
"Attribution 3.0 (`CC BY 3.0 <https://creativecommons.org/licenses/by/3.0/"
">`_) license, with attribution to \"*Juan Linietsky, Ariel Manzur, and the "
"Godot Engine community*\" unless otherwise noted."
msgstr ""
"Sav sadržaj je pod popustljivom  Commons Attribution 3.0 (`CC-BY 3.0 "
"<https://creativecommons.org/licenses/by/3.0/>`_) licencom, sa atribucijom "
"\"Juan Linietsky, Ariel Manzur and the Godot Engine community\"."

#: ../../docs/about/introduction.rst:104
#, fuzzy
msgid "*Have fun reading and making games with Godot Engine!*"
msgstr "Uživajte čitajući i praveći igre u Godot pokretaču igre!"

#: ../../docs/about/list_of_features.rst:4
msgid "List of features"
msgstr ""

#: ../../docs/about/list_of_features.rst:6
msgid "This page aims to list **all** features currently supported by Godot."
msgstr ""

#: ../../docs/about/list_of_features.rst:10
msgid ""
"This page lists features supported by the current stable version of Godot. "
"Some of these features may not be available in the `LTS release series (3.x) "
"<https://docs.godotengine.org/en/3.5/about/list_of_features.html>`__."
msgstr ""

#: ../../docs/about/list_of_features.rst:15
msgid "Platforms"
msgstr ""

#: ../../docs/about/list_of_features.rst:19
msgid ""
"See :ref:`doc_system_requirements` for hardware and software version "
"requirements."
msgstr ""

#: ../../docs/about/list_of_features.rst:21
msgid "**Can run both the editor and exported projects:**"
msgstr ""

#: ../../docs/about/list_of_features.rst:23
msgid "Windows (x86, 64-bit and 32-bit)."
msgstr ""

#: ../../docs/about/list_of_features.rst:24
msgid "macOS (x86 and ARM, 64-bit only)."
msgstr ""

#: ../../docs/about/list_of_features.rst:25
msgid "Linux (x86 and ARM, 64-bit and 32-bit)."
msgstr ""

#: ../../docs/about/list_of_features.rst:27
msgid ""
"Binaries are statically linked and can run on any distribution if compiled "
"on an old enough base distribution."
msgstr ""

#: ../../docs/about/list_of_features.rst:29
msgid ""
"Official binaries are compiled using the `Godot Engine buildroot <https://"
"github.com/godotengine/buildroot>`__, allowing for binaries that work across "
"common Linux distributions (including LTS variants)."
msgstr ""

#: ../../docs/about/list_of_features.rst:34
msgid "Android (editor support is experimental)."
msgstr ""

#: ../../docs/about/list_of_features.rst:35
msgid ""
":ref:`Web browsers <doc_using_the_web_editor>`. Experimental in 4.0, using "
"Godot 3.x is recommended instead when targeting HTML5."
msgstr ""

#: ../../docs/about/list_of_features.rst:38
msgid "**Runs exported projects:**"
msgstr ""

#: ../../docs/about/list_of_features.rst:40
msgid "iOS."
msgstr ""

#: ../../docs/about/list_of_features.rst:41
msgid ":ref:`Consoles <doc_consoles>`."
msgstr ""

#: ../../docs/about/list_of_features.rst:43
msgid ""
"Godot aims to be as platform-independent as possible and can be :ref:`ported "
"to new platforms <doc_custom_platform_ports>` with relative ease."
msgstr ""

#: ../../docs/about/list_of_features.rst:48
#: ../../docs/getting_started/step_by_step/scripting_languages.rst:131
msgid ""
"Projects written in C# using Godot 4 currently cannot be exported to the web "
"platform. To use C# on that platform, consider Godot 3 instead. Android and "
"iOS platform support is available as of Godot 4.2, but is experimental and :"
"ref:`some limitations apply <doc_c_sharp_platforms>`."
msgstr ""

#: ../../docs/about/list_of_features.rst:54
#: ../../docs/about/docs_changelog.rst:153
#: ../../docs/about/docs_changelog.rst:208
#: ../../docs/tutorials/editor/external_editor.rst:38
#: ../../docs/contributing/development/compiling/compiling_with_dotnet.rst:189
msgid "Editor"
msgstr ""

#: ../../docs/about/list_of_features.rst:56
#: ../../docs/about/list_of_features.rst:494
msgid "**Features:**"
msgstr ""

#: ../../docs/about/list_of_features.rst:58
msgid "Scene tree editor."
msgstr ""

#: ../../docs/about/list_of_features.rst:59
#, fuzzy
msgid "Built-in script editor."
msgstr "Kreiranje Sadržaja"

#: ../../docs/about/list_of_features.rst:60
msgid ""
"Support for :ref:`external script editors <doc_external_editor>` such as "
"Visual Studio Code or Vim."
msgstr ""

#: ../../docs/about/list_of_features.rst:62
msgid "GDScript :ref:`debugger <doc_debugger_panel>`."
msgstr ""

#: ../../docs/about/list_of_features.rst:64
msgid "Support for debugging in threads is available since 4.2."
msgstr ""

#: ../../docs/about/list_of_features.rst:65
msgid ""
"Visual profiler with CPU and GPU time indications for each step of the "
"rendering pipeline."
msgstr ""

#: ../../docs/about/list_of_features.rst:67
msgid ""
"Performance monitoring tools, including :ref:`custom performance monitors "
"<doc_custom_performance_monitors>`."
msgstr ""

#: ../../docs/about/list_of_features.rst:69
msgid "Live script reloading."
msgstr ""

#: ../../docs/about/list_of_features.rst:70
msgid "Live scene editing."
msgstr ""

#: ../../docs/about/list_of_features.rst:72
msgid ""
"Changes will reflect in the editor and will be kept after closing the "
"running project."
msgstr ""

#: ../../docs/about/list_of_features.rst:74
msgid "Remote inspector."
msgstr ""

#: ../../docs/about/list_of_features.rst:76
msgid ""
"Changes won't reflect in the editor and won't be kept after closing the "
"running project."
msgstr ""

#: ../../docs/about/list_of_features.rst:78
msgid "Live camera replication."
msgstr ""

#: ../../docs/about/list_of_features.rst:80
msgid "Move the in-editor camera and see the result in the running project."
msgstr ""

#: ../../docs/about/list_of_features.rst:82
msgid "Built-in offline class reference documentation."
msgstr ""

#: ../../docs/about/list_of_features.rst:83
msgid "Use the editor in dozens of languages contributed by the community."
msgstr ""

#: ../../docs/about/list_of_features.rst:85
msgid "**Plugins:**"
msgstr ""

#: ../../docs/about/list_of_features.rst:87
msgid ""
"Editor plugins can be downloaded from the :ref:`asset library "
"<doc_what_is_assetlib>` to extend editor functionality."
msgstr ""

#: ../../docs/about/list_of_features.rst:89
msgid ""
":ref:`Create your own plugins <doc_making_plugins>` using GDScript to add "
"new features or speed up your workflow."
msgstr ""

#: ../../docs/about/list_of_features.rst:91
msgid ""
":ref:`Download projects from the asset library <doc_using_assetlib_editor>` "
"in the Project Manager and import them directly."
msgstr ""

#: ../../docs/about/list_of_features.rst:95
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:120
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:128
#: ../../docs/tutorials/2d/index.rst:12 ../../docs/tutorials/3d/index.rst:14
#: ../../docs/tutorials/performance/thread_safe_apis.rst:55
#: ../../docs/tutorials/rendering/index.rst:2
#: ../../docs/tutorials/rendering/viewports.rst:174
msgid "Rendering"
msgstr ""

#: ../../docs/about/list_of_features.rst:97
msgid ""
"3 rendering *methods* (running over 2 rendering *drivers*) are available:"
msgstr ""

#: ../../docs/about/list_of_features.rst:99
msgid ""
"**Forward+**, running over Vulkan 1.0 (with optional Vulkan 1.1 and 1.2 "
"features). The most advanced graphics backend, suited for desktop platforms "
"only. Used by default on desktop platforms."
msgstr ""

#: ../../docs/about/list_of_features.rst:102
msgid ""
"**Forward Mobile**, running over Vulkan 1.0 (with optional Vulkan 1.1 and "
"1.2 features). Less features, but renders simple scenes faster. Suited for "
"mobile and desktop platforms. Used by default on mobile platforms."
msgstr ""

#: ../../docs/about/list_of_features.rst:105
msgid ""
"**Compatibility**, running over OpenGL 3.3 / OpenGL ES 3.0 / WebGL 2.0. The "
"least advanced graphics backend, suited for low-end desktop and mobile "
"platforms. Used by default on the web platform."
msgstr ""

#: ../../docs/about/list_of_features.rst:110
msgid "2D graphics"
msgstr ""

#: ../../docs/about/list_of_features.rst:112
msgid "Sprite, polygon and line rendering."
msgstr ""

#: ../../docs/about/list_of_features.rst:114
msgid ""
"High-level tools to draw lines and polygons such as :ref:`class_Polygon2D` "
"and :ref:`class_Line2D`, with support for texturing."
msgstr ""

#: ../../docs/about/list_of_features.rst:117
msgid "AnimatedSprite2D as a helper for creating animated sprites."
msgstr ""

#: ../../docs/about/list_of_features.rst:118
msgid "Parallax layers."
msgstr ""

#: ../../docs/about/list_of_features.rst:120
msgid "Pseudo-3D support including preview in the editor."
msgstr ""

#: ../../docs/about/list_of_features.rst:122
msgid ""
":ref:`2D lighting <doc_2d_lights_and_shadows>` with normal maps and specular "
"maps."
msgstr ""

#: ../../docs/about/list_of_features.rst:124
msgid "Point (omni/spot) and directional 2D lights."
msgstr ""

#: ../../docs/about/list_of_features.rst:125
msgid "Hard or soft shadows (adjustable on a per-light basis)."
msgstr ""

#: ../../docs/about/list_of_features.rst:126
msgid ""
"Custom shaders can access a real-time :abbr:`SDF (Signed Distance Field)` "
"representation of the 2D scene based on :ref:`class_LightOccluder2D` nodes, "
"which can be used for improved 2D lighting effects including 2D global "
"illumination."
msgstr ""

#: ../../docs/about/list_of_features.rst:130
msgid ""
":ref:`Font rendering <doc_gui_using_fonts>` using bitmaps, rasterization "
"using FreeType or multi-channel signed distance fields (MSDF)."
msgstr ""

#: ../../docs/about/list_of_features.rst:133
msgid ""
"Bitmap fonts can be exported using tools like BMFont, or imported from "
"images (for fixed-width fonts only)."
msgstr ""

#: ../../docs/about/list_of_features.rst:135
msgid ""
"Dynamic fonts support monochrome fonts as well as colored fonts (e.g. for "
"emoji). Supported formats are TTF, OTF, WOFF1 and WOFF2."
msgstr ""

#: ../../docs/about/list_of_features.rst:137
msgid ""
"Dynamic fonts support optional font outlines with adjustable width and color."
msgstr ""

#: ../../docs/about/list_of_features.rst:138
msgid ""
"Dynamic fonts support variable fonts and OpenType features including "
"ligatures."
msgstr ""

#: ../../docs/about/list_of_features.rst:139
msgid ""
"Dynamic fonts support simulated bold and italic when the font file lacks "
"those styles."
msgstr ""

#: ../../docs/about/list_of_features.rst:141
msgid ""
"Dynamic fonts support oversampling to keep fonts sharp at higher resolutions."
msgstr ""

#: ../../docs/about/list_of_features.rst:142
msgid ""
"Dynamic fonts support subpixel positioning to make fonts crisper at low "
"sizes."
msgstr ""

#: ../../docs/about/list_of_features.rst:143
msgid ""
"Dynamic fonts support LCD subpixel optimizations to make fonts even crisper "
"at low sizes."
msgstr ""

#: ../../docs/about/list_of_features.rst:144
msgid ""
"Signed distance field fonts can be scaled at any resolution without "
"requiring re-rasterization. Multi-channel usage makes SDF fonts scale down "
"to lower sizes better compared to monochrome SDF fonts."
msgstr ""

#: ../../docs/about/list_of_features.rst:148
msgid ""
"GPU-based :ref:`particles <doc_particle_systems_2d>` with support for :ref:"
"`custom particle shaders <doc_particle_shader>`."
msgstr ""

#: ../../docs/about/list_of_features.rst:150
#: ../../docs/about/list_of_features.rst:340
msgid "CPU-based particles."
msgstr ""

#: ../../docs/about/list_of_features.rst:151
msgid ""
"Optional :ref:`2D HDR rendering "
"<doc_environment_and_post_processing_using_glow_in_2d>` for better glow "
"capabilities."
msgstr ""

#: ../../docs/about/list_of_features.rst:155
msgid "2D tools"
msgstr ""

#: ../../docs/about/list_of_features.rst:157
msgid ":ref:`TileMaps <doc_using_tilemaps>` for 2D tile-based level design."
msgstr ""

#: ../../docs/about/list_of_features.rst:158
msgid "2D camera with built-in smoothing and drag margins."
msgstr ""

#: ../../docs/about/list_of_features.rst:159
msgid "Path2D node to represent a path in 2D space."
msgstr ""

#: ../../docs/about/list_of_features.rst:161
#: ../../docs/about/list_of_features.rst:401
msgid "Can be drawn in the editor or generated procedurally."
msgstr ""

#: ../../docs/about/list_of_features.rst:162
msgid "PathFollow2D node to make nodes follow a Path2D."
msgstr ""

#: ../../docs/about/list_of_features.rst:164
msgid ":ref:`2D geometry helper class <class_Geometry2D>`."
msgstr ""

#: ../../docs/about/list_of_features.rst:167
msgid "2D physics"
msgstr ""

#: ../../docs/about/list_of_features.rst:169
#: ../../docs/about/list_of_features.rst:411
msgid "**Physics bodies:**"
msgstr ""

#: ../../docs/about/list_of_features.rst:171
#: ../../docs/about/list_of_features.rst:413
msgid "Static bodies."
msgstr ""

#: ../../docs/about/list_of_features.rst:172
#: ../../docs/about/list_of_features.rst:414
msgid ""
"Animatable bodies (for objects moving only by script or animation, such as "
"doors and platforms)."
msgstr ""

#: ../../docs/about/list_of_features.rst:173
#: ../../docs/about/list_of_features.rst:415
msgid "Rigid bodies."
msgstr ""

#: ../../docs/about/list_of_features.rst:174
#: ../../docs/about/list_of_features.rst:416
#, fuzzy
msgid "Character bodies."
msgstr "Kreiranje Sadržaja"

#: ../../docs/about/list_of_features.rst:175
#: ../../docs/about/list_of_features.rst:418
msgid "Joints."
msgstr ""

#: ../../docs/about/list_of_features.rst:176
#: ../../docs/about/list_of_features.rst:421
msgid "Areas to detect bodies entering or leaving it."
msgstr ""

#: ../../docs/about/list_of_features.rst:178
#: ../../docs/about/list_of_features.rst:423
msgid "**Collision detection:**"
msgstr ""

#: ../../docs/about/list_of_features.rst:180
msgid ""
"Built-in shapes: line, box, circle, capsule, world boundary (infinite plane)."
msgstr ""

#: ../../docs/about/list_of_features.rst:181
msgid ""
"Collision polygons (can be drawn manually or generated from a sprite in the "
"editor)."
msgstr ""

#: ../../docs/about/list_of_features.rst:184
msgid "3D graphics"
msgstr ""

#: ../../docs/about/list_of_features.rst:186
msgid "HDR rendering with sRGB."
msgstr ""

#: ../../docs/about/list_of_features.rst:187
msgid "Perspective, orthographic and frustum-offset cameras."
msgstr ""

#: ../../docs/about/list_of_features.rst:188
msgid ""
"When using the Forward+ backend, a depth prepass is used to improve "
"performance in complex scenes by reducing the cost of overdraw."
msgstr ""

#: ../../docs/about/list_of_features.rst:190
msgid ""
":ref:`doc_variable_rate_shading` on supported GPUs in Forward+ and Forward "
"Mobile."
msgstr ""

#: ../../docs/about/list_of_features.rst:192
msgid "**Physically-based rendering (built-in material features):**"
msgstr ""

#: ../../docs/about/list_of_features.rst:194
msgid "Follows the Disney PBR model."
msgstr ""

#: ../../docs/about/list_of_features.rst:195
msgid ""
"Supports Burley, Lambert, Lambert Wrap (half-Lambert) and Toon diffuse "
"shading modes."
msgstr ""

#: ../../docs/about/list_of_features.rst:196
msgid "Supports Schlick-GGX, Toon and Disabled specular shading modes."
msgstr ""

#: ../../docs/about/list_of_features.rst:197
msgid "Uses a roughness-metallic workflow with support for ORM textures."
msgstr ""

#: ../../docs/about/list_of_features.rst:198
msgid ""
"Uses horizon specular occlusion (Filament model) to improve material "
"appearance."
msgstr ""

#: ../../docs/about/list_of_features.rst:199
msgid "Normal mapping."
msgstr ""

#: ../../docs/about/list_of_features.rst:200
msgid ""
"Parallax/relief mapping with automatic level of detail based on distance."
msgstr ""

#: ../../docs/about/list_of_features.rst:201
msgid "Detail mapping for the albedo and normal maps."
msgstr ""

#: ../../docs/about/list_of_features.rst:202
msgid "Sub-surface scattering and transmittance."
msgstr ""

#: ../../docs/about/list_of_features.rst:203
msgid ""
"Screen-space refraction with support for material roughness (resulting in "
"blurry refraction)."
msgstr ""

#: ../../docs/about/list_of_features.rst:204
msgid "Proximity fade (soft particles) and distance fade."
msgstr ""

#: ../../docs/about/list_of_features.rst:205
msgid ""
"Distance fade can use alpha blending or dithering to avoid going through the "
"transparent pipeline."
msgstr ""

#: ../../docs/about/list_of_features.rst:207
msgid "Dithering can be determined on a per-pixel or per-object basis."
msgstr ""

#: ../../docs/about/list_of_features.rst:209
msgid "**Real-time lighting:**"
msgstr ""

#: ../../docs/about/list_of_features.rst:211
msgid "Directional lights (sun/moon). Up to 4 per scene."
msgstr ""

#: ../../docs/about/list_of_features.rst:212
msgid "Omnidirectional lights."
msgstr ""

#: ../../docs/about/list_of_features.rst:213
msgid "Spot lights with adjustable cone angle and attenuation."
msgstr ""

#: ../../docs/about/list_of_features.rst:214
msgid ""
"Specular, indirect light, and volumetric fog energy can be adjusted on a per-"
"light basis."
msgstr ""

#: ../../docs/about/list_of_features.rst:215
msgid ""
"Adjustable light \"size\" for fake area lights (will also make shadows "
"blurrier)."
msgstr ""

#: ../../docs/about/list_of_features.rst:216
msgid ""
"Optional distance fade system to fade distant lights and their shadows, "
"improving performance."
msgstr ""

#: ../../docs/about/list_of_features.rst:217
msgid ""
"When using the Forward+ backend (default on desktop), lights are rendered "
"with clustered forward optimizations to decrease their individual cost. "
"Clustered rendering also lifts any limits on the number of lights that can "
"be used on a mesh."
msgstr ""

#: ../../docs/about/list_of_features.rst:220
msgid ""
"When using the Forward Mobile backend, up to 8 omni lights and 8 spot lights "
"can be displayed per mesh resource. Baked lighting can be used to overcome "
"this limit if needed."
msgstr ""

#: ../../docs/about/list_of_features.rst:224
msgid "**Shadow mapping:**"
msgstr ""

#: ../../docs/about/list_of_features.rst:226
msgid ""
"*DirectionalLight:* Orthogonal (fastest), PSSM 2-split and 4-split. Supports "
"blending between splits."
msgstr ""

#: ../../docs/about/list_of_features.rst:228
msgid ""
"*OmniLight:* Dual paraboloid (fast) or cubemap (slower but more accurate). "
"Supports colored projector textures in the form of panoramas."
msgstr ""

#: ../../docs/about/list_of_features.rst:230
msgid "*SpotLight:* Single texture. Supports colored projector textures."
msgstr ""

#: ../../docs/about/list_of_features.rst:231
msgid ""
"Shadow normal offset bias and shadow pancaking to decrease the amount of "
"visible shadow acne and peter-panning."
msgstr ""

#: ../../docs/about/list_of_features.rst:233
msgid ""
":abbr:`PCSS (Percentage Closer Soft Shadows)`-like shadow blur based on the "
"light size and distance from the surface the shadow is cast on."
msgstr ""

#: ../../docs/about/list_of_features.rst:235
msgid "Adjustable shadow blur on a per-light basis."
msgstr ""

#: ../../docs/about/list_of_features.rst:237
msgid "**Global illumination with indirect lighting:**"
msgstr ""

#: ../../docs/about/list_of_features.rst:239
msgid ""
":ref:`Baked lightmaps <doc_using_lightmap_gi>` (fast, but can't be updated "
"at run-time)."
msgstr ""

#: ../../docs/about/list_of_features.rst:241
msgid ""
"Supports baking indirect light only or baking both direct and indirect "
"lighting. The bake mode can be adjusted on a per-light basis to allow for "
"hybrid light baking setups."
msgstr ""

#: ../../docs/about/list_of_features.rst:244
msgid ""
"Supports lighting dynamic objects using automatic and manually placed probes."
msgstr ""

#: ../../docs/about/list_of_features.rst:245
msgid ""
"Optionally supports directional lighting and rough reflections based on "
"spherical harmonics."
msgstr ""

#: ../../docs/about/list_of_features.rst:247
msgid ""
"Lightmaps are baked on the GPU using compute shaders (much faster compared "
"to CPU lightmapping). Baking can only be performed from the editor, not in "
"exported projects."
msgstr ""

#: ../../docs/about/list_of_features.rst:250
msgid ""
"Supports GPU-based :ref:`denoising <doc_using_lightmap_gi_denoising>` with "
"JNLM, or CPU/GPU-based denoising with OIDN."
msgstr ""

#: ../../docs/about/list_of_features.rst:253
msgid ""
":ref:`Voxel-based GI probes <doc_using_voxel_gi>`. Supports dynamic lights "
"*and* dynamic occluders, while also supporting reflections. Requires a fast "
"baking step which can be performed in the editor or at run-time (including "
"from an exported project)."
msgstr ""

#: ../../docs/about/list_of_features.rst:257
msgid ""
":ref:`Signed-distance field GI <doc_using_sdfgi>` designed for large open "
"worlds. Supports dynamic lights, but not dynamic occluders. Supports "
"reflections. No baking required."
msgstr ""

#: ../../docs/about/list_of_features.rst:260
msgid ""
":ref:`Screen-space indirect lighting (SSIL) "
"<doc_environment_and_post_processing_ssil>` at half or full resolution. "
"Fully real-time and supports any kind of emissive light source (including "
"decals)."
msgstr ""

#: ../../docs/about/list_of_features.rst:263
msgid ""
"VoxelGI and SDFGI use a deferred pass to allow for rendering GI at half "
"resolution to improve performance (while still having functional MSAA "
"support)."
msgstr ""

#: ../../docs/about/list_of_features.rst:266
msgid "**Reflections:**"
msgstr ""

#: ../../docs/about/list_of_features.rst:268
msgid ""
"Voxel-based reflections (when using GI probes) and SDF-based reflections "
"(when using signed distance field GI). Voxel-based reflections are visible "
"on transparent surfaces, while rough SDF-based reflections are visible on "
"transparent surfaces."
msgstr ""

#: ../../docs/about/list_of_features.rst:272
msgid ""
"Fast baked reflections or slow real-time reflections using ReflectionProbe. "
"Parallax box correction can optionally be enabled."
msgstr ""

#: ../../docs/about/list_of_features.rst:274
msgid "Screen-space reflections with support for material roughness."
msgstr ""

#: ../../docs/about/list_of_features.rst:275
msgid ""
"Reflection techniques can be mixed together for greater accuracy or "
"scalability."
msgstr ""

#: ../../docs/about/list_of_features.rst:276
msgid ""
"When using the Forward+ backend (default on desktop), reflection probes are "
"rendered with clustered forward optimizations to decrease their individual "
"cost. Clustered rendering also lifts any limits on the number of reflection "
"probes that can be used on a mesh."
msgstr ""

#: ../../docs/about/list_of_features.rst:279
msgid ""
"When using the Forward Mobile backend, up to 8 reflection probes can be "
"displayed per mesh resource."
msgstr ""

#: ../../docs/about/list_of_features.rst:282
msgid "**Decals:**"
msgstr ""

#: ../../docs/about/list_of_features.rst:284
msgid ""
":ref:`Supports albedo <doc_using_decals>`, emissive, :abbr:`ORM (Occlusion "
"Roughness Metallic)`, and normal mapping."
msgstr ""

#: ../../docs/about/list_of_features.rst:286
msgid ""
"Texture channels are smoothly overlaid on top of the underlying material, "
"with support for normal/ORM-only decals."
msgstr ""

#: ../../docs/about/list_of_features.rst:288
msgid ""
"Support for normal fade to fade the decal depending on its incidence angle."
msgstr ""

#: ../../docs/about/list_of_features.rst:289
msgid ""
"Does not rely on run-time mesh generation. This means decals can be used on "
"complex skinned meshes with no performance penalty, even if the decal moves "
"every frame."
msgstr ""

#: ../../docs/about/list_of_features.rst:291
msgid ""
"Support for nearest, bilinear, trilinear or anisotropic texture filtering "
"(configured globally)."
msgstr ""

#: ../../docs/about/list_of_features.rst:292
msgid ""
"Optional distance fade system to fade distant decals, improving performance."
msgstr ""

#: ../../docs/about/list_of_features.rst:293
msgid ""
"When using the Forward+ backend (default on desktop), decals are rendered "
"with clustered forward optimizations to decrease their individual cost. "
"Clustered rendering also lifts any limits on the number of decals that can "
"be used on a mesh."
msgstr ""

#: ../../docs/about/list_of_features.rst:296
msgid ""
"When using the Forward Mobile backend, up to 8 decals can be displayed per "
"mesh resource."
msgstr ""

#: ../../docs/about/list_of_features.rst:299
msgid "**Sky:**"
msgstr ""

#: ../../docs/about/list_of_features.rst:301
msgid "Panorama sky (using an HDRI)."
msgstr ""

#: ../../docs/about/list_of_features.rst:302
msgid ""
"Procedural sky and Physically-based sky that respond to the "
"DirectionalLights in the scene."
msgstr ""

#: ../../docs/about/list_of_features.rst:303
msgid ""
"Support for :ref:`custom sky shaders <doc_sky_shader>`, which can be "
"animated."
msgstr ""

#: ../../docs/about/list_of_features.rst:304
msgid ""
"The radiance map used for ambient and specular light can be updated in real-"
"time depending on the quality settings chosen."
msgstr ""

#: ../../docs/about/list_of_features.rst:307
msgid "**Fog:**"
msgstr ""

#: ../../docs/about/list_of_features.rst:309
msgid "Exponential depth fog."
msgstr ""

#: ../../docs/about/list_of_features.rst:310
msgid "Exponential height fog."
msgstr ""

#: ../../docs/about/list_of_features.rst:311
msgid ""
"Support for automatic fog color depending on the sky color (aerial "
"perspective)."
msgstr ""

#: ../../docs/about/list_of_features.rst:312
#, fuzzy
msgid "Support for sun scattering in the fog."
msgstr "Kreiranje Sadržaja"

#: ../../docs/about/list_of_features.rst:313
msgid ""
"Support for controlling how much fog rendering should affect the sky, with "
"separate controls for traditional and volumetric fog."
msgstr ""

#: ../../docs/about/list_of_features.rst:315
#, fuzzy
msgid "Support for making specific materials ignore fog."
msgstr "Kreiranje Sadržaja"

#: ../../docs/about/list_of_features.rst:317
msgid "**Volumetric fog:**"
msgstr ""

#: ../../docs/about/list_of_features.rst:319
msgid ""
"Global :ref:`volumetric fog <doc_volumetric_fog>` that reacts to lights and "
"shadows."
msgstr ""

#: ../../docs/about/list_of_features.rst:320
msgid ""
"Volumetric fog can take indirect light into account when using VoxelGI or "
"SDFGI."
msgstr ""

#: ../../docs/about/list_of_features.rst:321
msgid ""
"Fog volume nodes that can be placed to add fog to specific areas (or remove "
"fog from specific areas). Supported shapes include box, ellipse, cone, "
"cylinder, and 3D texture-based density maps."
msgstr ""

#: ../../docs/about/list_of_features.rst:323
msgid "Each fog volume can have its own custom shader."
msgstr ""

#: ../../docs/about/list_of_features.rst:324
msgid "Can be used together with traditional fog."
msgstr ""

#: ../../docs/about/list_of_features.rst:326
msgid "**Particles:**"
msgstr ""

#: ../../docs/about/list_of_features.rst:328
msgid ""
"GPU-based particles with support for subemitters (2D + 3D), trails (2D + "
"3D), attractors (3D only) and collision (2D + 3D)."
msgstr ""

#: ../../docs/about/list_of_features.rst:331
msgid ""
"3D particle attractor shapes supported: box, sphere and 3D vector fields."
msgstr ""

#: ../../docs/about/list_of_features.rst:332
msgid ""
"3D particle collision shapes supported: box, sphere, baked signed distance "
"field and real-time heightmap (suited for open world weather effects)."
msgstr ""

#: ../../docs/about/list_of_features.rst:334
msgid ""
"2D particle collision is handled using a signed distance field generated in "
"real-time based on :ref:`class_LightOccluder2D` nodes in the scene."
msgstr ""

#: ../../docs/about/list_of_features.rst:336
msgid ""
"Trails can use the built-in ribbon trail and tube trail meshes, or custom "
"meshes with skeletons."
msgstr ""

#: ../../docs/about/list_of_features.rst:338
msgid "Support for custom particle shaders with manual emission."
msgstr ""

#: ../../docs/about/list_of_features.rst:342
msgid "**Post-processing:**"
msgstr ""

#: ../../docs/about/list_of_features.rst:344
msgid "Tonemapping (Linear, Reinhard, Filmic, ACES)."
msgstr ""

#: ../../docs/about/list_of_features.rst:345
msgid ""
"Automatic exposure adjustments based on viewport brightness (and manual "
"exposure override)."
msgstr ""

#: ../../docs/about/list_of_features.rst:346
msgid ""
"Near and far depth of field with adjustable bokeh simulation (box, hexagon, "
"circle)."
msgstr ""

#: ../../docs/about/list_of_features.rst:347
msgid "Screen-space ambient occlusion (SSAO) at half or full resolution."
msgstr ""

#: ../../docs/about/list_of_features.rst:348
msgid ""
"Glow/bloom with optional bicubic upscaling and several blend modes "
"available: Screen, Soft Light, Add, Replace, Mix."
msgstr ""

#: ../../docs/about/list_of_features.rst:350
msgid "Glow can have a colored dirt map texture, acting as a lens dirt effect."
msgstr ""

#: ../../docs/about/list_of_features.rst:351
msgid ""
"Glow can be :ref:`used as a screen-space blur effect "
"<doc_environment_and_post_processing_using_glow_to_blur_the_screen>`."
msgstr ""

#: ../../docs/about/list_of_features.rst:352
msgid "Color correction using a one-dimensional ramp or a 3D LUT texture."
msgstr ""

#: ../../docs/about/list_of_features.rst:353
msgid "Roughness limiter to reduce the impact of specular aliasing."
msgstr ""

#: ../../docs/about/list_of_features.rst:354
msgid "Brightness, contrast and saturation adjustments."
msgstr ""

#: ../../docs/about/list_of_features.rst:356
msgid "**Texture filtering:**"
msgstr ""

#: ../../docs/about/list_of_features.rst:358
msgid "Nearest, bilinear, trilinear or anisotropic filtering."
msgstr ""

#: ../../docs/about/list_of_features.rst:359
msgid ""
"Filtering options are defined on a per-use basis, not a per-texture basis."
msgstr ""

#: ../../docs/about/list_of_features.rst:361
msgid "**Texture compression:**"
msgstr ""

#: ../../docs/about/list_of_features.rst:363
msgid "Basis Universal (slow, but results in smaller files)."
msgstr ""

#: ../../docs/about/list_of_features.rst:364
msgid "BPTC for high-quality compression (not supported on macOS)."
msgstr ""

#: ../../docs/about/list_of_features.rst:365
msgid "ETC2 (not supported on macOS)."
msgstr ""

#: ../../docs/about/list_of_features.rst:366
msgid "S3TC (not supported on mobile/Web platforms)."
msgstr ""

#: ../../docs/about/list_of_features.rst:368
msgid "**Anti-aliasing:**"
msgstr ""

#: ../../docs/about/list_of_features.rst:370
msgid "Temporal :ref:`antialiasing <doc_3d_antialiasing>` (TAA)."
msgstr ""

#: ../../docs/about/list_of_features.rst:371
msgid ""
"AMD FidelityFX Super Resolution 2.2 :ref:`antialiasing "
"<doc_3d_antialiasing>` (FSR2), which can be used at native resolution as a "
"form of high-quality temporal antialiasing."
msgstr ""

#: ../../docs/about/list_of_features.rst:373
msgid ""
"Multi-sample antialiasing (MSAA), for both :ref:`doc_2d_antialiasing` and :"
"ref:`doc_3d_antialiasing`."
msgstr ""

#: ../../docs/about/list_of_features.rst:374
msgid "Fast approximate antialiasing (FXAA)."
msgstr ""

#: ../../docs/about/list_of_features.rst:375
msgid ""
"Super-sample antialiasing (SSAA) using bilinear 3D scaling and a 3D "
"resolution scale above 1.0."
msgstr ""

#: ../../docs/about/list_of_features.rst:376
msgid ""
"Alpha antialiasing, MSAA alpha to coverage and alpha hashing on a per-"
"material basis."
msgstr ""

#: ../../docs/about/list_of_features.rst:378
msgid "**Resolution scaling:**"
msgstr ""

#: ../../docs/about/list_of_features.rst:380
msgid ""
"Support for :ref:`rendering 3D at a lower resolution "
"<doc_resolution_scaling>` while keeping 2D rendering at the original scale. "
"This can be used to improve performance on low-end systems or improve "
"visuals on high-end systems."
msgstr ""

#: ../../docs/about/list_of_features.rst:383
msgid ""
"Resolution scaling uses bilinear filtering, AMD FidelityFX Super Resolution "
"1.0 (FSR1) or AMD FidelityFX Super Resolution 2.2 (FSR2)."
msgstr ""

#: ../../docs/about/list_of_features.rst:385
msgid ""
"Texture mipmap LOD bias is adjusted automatically to improve quality at "
"lower resolution scales. It can also be modified with a manual offset."
msgstr ""

#: ../../docs/about/list_of_features.rst:388
msgid ""
"Most effects listed above can be adjusted for better performance or to "
"further improve quality. This can be helpful when :ref:`using Godot for "
"offline rendering <doc_creating_movies>`."
msgstr ""

#: ../../docs/about/list_of_features.rst:393
msgid "3D tools"
msgstr ""

#: ../../docs/about/list_of_features.rst:395
msgid ""
"Built-in meshes: cube, cylinder/cone, (hemi)sphere, prism, plane, quad, "
"torus, ribbon, tube."
msgstr ""

#: ../../docs/about/list_of_features.rst:396
msgid ":ref:`GridMaps <doc_using_gridmaps>` for 3D tile-based level design."
msgstr ""

#: ../../docs/about/list_of_features.rst:397
msgid ""
":ref:`Constructive solid geometry <doc_csg_tools>` (intended for "
"prototyping)."
msgstr ""

#: ../../docs/about/list_of_features.rst:398
msgid ""
"Tools for :ref:`procedural geometry generation <doc_procedural_geometry>`."
msgstr ""

#: ../../docs/about/list_of_features.rst:399
msgid "Path3D node to represent a path in 3D space."
msgstr ""

#: ../../docs/about/list_of_features.rst:402
msgid "PathFollow3D node to make nodes follow a Path3D."
msgstr ""

#: ../../docs/about/list_of_features.rst:404
msgid ":ref:`3D geometry helper class <class_Geometry3D>`."
msgstr ""

#: ../../docs/about/list_of_features.rst:405
msgid ""
"Support for exporting the current scene as a glTF 2.0 file, both from the "
"editor and at run-time from an exported project."
msgstr ""

#: ../../docs/about/list_of_features.rst:409
msgid "3D physics"
msgstr ""

#: ../../docs/about/list_of_features.rst:417
msgid "Vehicle bodies (intended for arcade physics, not simulation)."
msgstr ""

#: ../../docs/about/list_of_features.rst:419
msgid "Soft bodies."
msgstr ""

#: ../../docs/about/list_of_features.rst:420
msgid "Ragdolls."
msgstr ""

#: ../../docs/about/list_of_features.rst:425
msgid ""
"Built-in shapes: cuboid, sphere, capsule, cylinder, world boundary (infinite "
"plane)."
msgstr ""

#: ../../docs/about/list_of_features.rst:426
msgid "Generate triangle collision shapes for any mesh from the editor."
msgstr ""

#: ../../docs/about/list_of_features.rst:427
msgid ""
"Generate one or several convex collision shapes for any mesh from the editor."
msgstr ""

#: ../../docs/about/list_of_features.rst:430
#: ../../docs/about/docs_changelog.rst:118
#: ../../docs/about/docs_changelog.rst:242
#: ../../docs/tutorials/shaders/index.rst:2
msgid "Shaders"
msgstr ""

#: ../../docs/about/list_of_features.rst:432
msgid "*2D:* Custom vertex, fragment, and light shaders."
msgstr ""

#: ../../docs/about/list_of_features.rst:433
msgid "*3D:* Custom vertex, fragment, light, and sky shaders."
msgstr ""

#: ../../docs/about/list_of_features.rst:434
msgid ""
"Text-based shaders using a :ref:`shader language inspired by GLSL "
"<doc_shading_language>`."
msgstr ""

#: ../../docs/about/list_of_features.rst:435
#, fuzzy
msgid "Visual shader editor."
msgstr "Kreiranje Sadržaja"

#: ../../docs/about/list_of_features.rst:437
#, fuzzy
msgid "Support for visual shader plugins."
msgstr "Kreiranje Sadržaja"

#: ../../docs/about/list_of_features.rst:440
#: ../../docs/about/docs_changelog.rst:110
#: ../../docs/about/docs_changelog.rst:247
#: ../../docs/about/docs_changelog.rst:353
#: ../../docs/tutorials/scripting/index.rst:2
msgid "Scripting"
msgstr ""

#: ../../docs/about/list_of_features.rst:442
#, fuzzy
msgid "**General:**"
msgstr "Opšti deo"

#: ../../docs/about/list_of_features.rst:444
msgid "Object-oriented design pattern with scripts extending nodes."
msgstr ""

#: ../../docs/about/list_of_features.rst:445
msgid "Signals and groups for communicating between scripts."
msgstr ""

#: ../../docs/about/list_of_features.rst:446
msgid ""
"Support for :ref:`cross-language scripting <doc_cross_language_scripting>`."
msgstr ""

#: ../../docs/about/list_of_features.rst:447
msgid ""
"Many 2D, 3D and 4D linear algebra data types such as vectors and transforms."
msgstr ""

#: ../../docs/about/list_of_features.rst:449
msgid ":ref:`GDScript: <toc-learn-scripting-gdscript>`"
msgstr ""

#: ../../docs/about/list_of_features.rst:451
msgid ""
":ref:`High-level interpreted language <doc_gdscript>` with :ref:`optional "
"static typing <doc_gdscript_static_typing>`."
msgstr ""

#: ../../docs/about/list_of_features.rst:453
msgid ""
"Syntax inspired by Python. However, GDScript is **not** based on Python."
msgstr ""

#: ../../docs/about/list_of_features.rst:454
msgid "Syntax highlighting is provided on GitHub."
msgstr ""

#: ../../docs/about/list_of_features.rst:455
msgid ""
":ref:`Use threads <doc_using_multiple_threads>` to perform asynchronous "
"actions or make use of multiple processor cores."
msgstr ""

#: ../../docs/about/list_of_features.rst:458
msgid ":ref:`C#: <toc-learn-scripting-C#>`"
msgstr ""

#: ../../docs/about/list_of_features.rst:460
msgid "Packaged in a separate binary to keep file sizes and dependencies down."
msgstr ""

#: ../../docs/about/list_of_features.rst:461
msgid "Supports .NET 6 and higher."
msgstr ""

#: ../../docs/about/list_of_features.rst:463
msgid "Full support for the C# 10.0 syntax and features."
msgstr ""

#: ../../docs/about/list_of_features.rst:465
msgid ""
"Supports Windows, Linux, and macOS. As of 4.2 experimental support for "
"Android and iOS is also available (requires a .NET 7.0 project for Android "
"and 8.0 for iOS)."
msgstr ""

#: ../../docs/about/list_of_features.rst:468
msgid ""
"On the Android platform only some architectures are supported: ``arm64`` and "
"``x64``."
msgstr ""

#: ../../docs/about/list_of_features.rst:469
msgid "On the iOS platform only some architectures are supported: ``arm64``."
msgstr ""

#: ../../docs/about/list_of_features.rst:470
msgid ""
"The web platform is currently unsupported. To use C# on that platform, "
"consider Godot 3 instead."
msgstr ""

#: ../../docs/about/list_of_features.rst:473
msgid ""
"Using an external editor is recommended to benefit from IDE functionality."
msgstr ""

#: ../../docs/about/list_of_features.rst:475
msgid "**GDExtension (C, C++, Rust, D, ...):**"
msgstr ""

#: ../../docs/about/list_of_features.rst:477
msgid ""
"When you need it, link to native libraries for higher performance and third-"
"party integrations."
msgstr ""

#: ../../docs/about/list_of_features.rst:479
msgid ""
"For scripting game logic, GDScript or C# are recommended if their "
"performance is suitable."
msgstr ""

#: ../../docs/about/list_of_features.rst:482
msgid ""
"Official GDExtension bindings for `C <https://github.com/godotengine/godot-"
"headers>`__ and `C++ <https://github.com/godotengine/godot-cpp>`__."
msgstr ""

#: ../../docs/about/list_of_features.rst:485
msgid "Use any build system and language features you wish."
msgstr ""

#: ../../docs/about/list_of_features.rst:487
msgid ""
"Actively developed GDExtension bindings for `D <https://github.com/godot-"
"dlang/godot-dlang>`__, `Haxe <https://hxgodot.github.io/>`__, `Swift "
"<https://github.com/migueldeicaza/SwiftGodot>`__, and `Rust <https://github."
"com/godot-rust/gdextension>`__ bindings provided by the community. (Some of "
"these bindings may be experimental and not production-ready)."
msgstr ""

#: ../../docs/about/list_of_features.rst:492
#: ../../docs/about/docs_changelog.rst:274
#: ../../docs/tutorials/audio/index.rst:4
#: ../../docs/tutorials/export/exporting_for_web.rst:134
msgid "Audio"
msgstr ""

#: ../../docs/about/list_of_features.rst:496
msgid "Mono, stereo, 5.1 and 7.1 output."
msgstr ""

#: ../../docs/about/list_of_features.rst:497
msgid "Non-positional and positional playback in 2D and 3D."
msgstr ""

#: ../../docs/about/list_of_features.rst:499
msgid "Optional Doppler effect in 2D and 3D."
msgstr ""

#: ../../docs/about/list_of_features.rst:501
msgid ""
"Support for re-routable :ref:`audio buses <doc_audio_buses>` and effects "
"with dozens of effects included."
msgstr ""

#: ../../docs/about/list_of_features.rst:503
msgid ""
"Support for polyphony (playing several sounds from a single "
"AudioStreamPlayer node)."
msgstr ""

#: ../../docs/about/list_of_features.rst:504
#, fuzzy
msgid "Support for random volume and pitch."
msgstr "Kreiranje Sadržaja"

#: ../../docs/about/list_of_features.rst:505
#, fuzzy
msgid "Support for real-time pitch scaling."
msgstr "Kreiranje Sadržaja"

#: ../../docs/about/list_of_features.rst:506
msgid ""
"Support for sequential/random sample selection, including repetition "
"prevention when using random sample selection."
msgstr ""

#: ../../docs/about/list_of_features.rst:508
msgid ""
"Listener2D and Listener3D nodes to listen from a position different than the "
"camera."
msgstr ""

#: ../../docs/about/list_of_features.rst:509
msgid ""
"Support for :ref:`procedural audio generation <class_AudioStreamGenerator>`."
msgstr ""

#: ../../docs/about/list_of_features.rst:510
msgid "Audio input to record microphones."
msgstr ""

#: ../../docs/about/list_of_features.rst:511
msgid "MIDI input."
msgstr ""

#: ../../docs/about/list_of_features.rst:513
msgid "No support for MIDI output yet."
msgstr ""

#: ../../docs/about/list_of_features.rst:515
msgid "**APIs used:**"
msgstr ""

#: ../../docs/about/list_of_features.rst:517
msgid "*Windows:* WASAPI."
msgstr ""

#: ../../docs/about/list_of_features.rst:518
msgid "*macOS:* CoreAudio."
msgstr ""

#: ../../docs/about/list_of_features.rst:519
msgid "*Linux:* PulseAudio or ALSA."
msgstr ""

#: ../../docs/about/list_of_features.rst:522
msgid "Import"
msgstr ""

#: ../../docs/about/list_of_features.rst:524
msgid "Support for :ref:`custom import plugins <doc_import_plugins>`."
msgstr ""

#: ../../docs/about/list_of_features.rst:526
msgid "**Formats:**"
msgstr ""

#: ../../docs/about/list_of_features.rst:528
#, fuzzy
msgid "*Images:* See :ref:`doc_importing_images`."
msgstr "Kreiranje Sadržaja"

#: ../../docs/about/list_of_features.rst:529
msgid "*Audio:*"
msgstr ""

#: ../../docs/about/list_of_features.rst:531
msgid "WAV with optional IMA-ADPCM compression."
msgstr ""

#: ../../docs/about/list_of_features.rst:532
msgid "Ogg Vorbis."
msgstr ""

#: ../../docs/about/list_of_features.rst:533
msgid "MP3."
msgstr ""

#: ../../docs/about/list_of_features.rst:535
msgid "*3D scenes:* See :ref:`doc_importing_3d_scenes`."
msgstr ""

#: ../../docs/about/list_of_features.rst:537
msgid "glTF 2.0 *(recommended)*."
msgstr ""

#: ../../docs/about/list_of_features.rst:538
msgid ""
"``.blend`` (by calling Blender's glTF export functionality transparently)."
msgstr ""

#: ../../docs/about/list_of_features.rst:539
msgid ""
"FBX (by calling `FBX2glTF <https://github.com/godotengine/FBX2glTF>`__ "
"transparently)."
msgstr ""

#: ../../docs/about/list_of_features.rst:540
msgid "Collada (.dae)."
msgstr ""

#: ../../docs/about/list_of_features.rst:541
msgid ""
"Wavefront OBJ (static scenes only, can be loaded directly as a mesh or "
"imported as a 3D scene)."
msgstr ""

#: ../../docs/about/list_of_features.rst:543
msgid ""
"Support for loading glTF 2.0 scenes at run-time, including from an exported "
"project."
msgstr ""

#: ../../docs/about/list_of_features.rst:544
msgid ""
"3D meshes use `Mikktspace <http://www.mikktspace.com/>`__ to generate "
"tangents on import, which ensures consistency with other 3D applications "
"such as Blender."
msgstr ""

#: ../../docs/about/list_of_features.rst:548
#: ../../docs/about/docs_changelog.rst:219
#: ../../docs/tutorials/rendering/viewports.rst:38
#: ../../docs/tutorials/ui/custom_gui_controls.rst:114
msgid "Input"
msgstr ""

#: ../../docs/about/list_of_features.rst:550
msgid ""
":ref:`Input mapping system <doc_input_examples>` using hardcoded input "
"events or remappable input actions."
msgstr ""

#: ../../docs/about/list_of_features.rst:553
msgid ""
"Axis values can be mapped to two different actions with a configurable "
"deadzone."
msgstr ""

#: ../../docs/about/list_of_features.rst:554
msgid "Use the same code to support both keyboards and gamepads."
msgstr ""

#: ../../docs/about/list_of_features.rst:556
msgid "Keyboard input."
msgstr ""

#: ../../docs/about/list_of_features.rst:558
msgid ""
"Keys can be mapped in \"physical\" mode to be independent of the keyboard "
"layout."
msgstr ""

#: ../../docs/about/list_of_features.rst:560
msgid "Mouse input."
msgstr ""

#: ../../docs/about/list_of_features.rst:562
msgid ""
"The mouse cursor can be visible, hidden, captured or confined within the "
"window."
msgstr ""

#: ../../docs/about/list_of_features.rst:563
msgid ""
"When captured, raw input will be used on Windows and Linux to sidestep the "
"OS' mouse acceleration settings."
msgstr ""

#: ../../docs/about/list_of_features.rst:566
msgid "Gamepad input (up to 8 simultaneous controllers)."
msgstr ""

#: ../../docs/about/list_of_features.rst:567
msgid "Pen/tablet input with pressure support."
msgstr ""

#: ../../docs/about/list_of_features.rst:570
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:136
#: ../../docs/tutorials/navigation/index.rst:2
msgid "Navigation"
msgstr ""

#: ../../docs/about/list_of_features.rst:572
msgid ""
"A* algorithm in :ref:`2D <class_AStar2D>` and :ref:`3D <class_AStar3D>`."
msgstr ""

#: ../../docs/about/list_of_features.rst:573
msgid ""
"Navigation meshes with dynamic obstacle avoidance in :ref:`2D "
"<doc_navigation_overview_2d>` and :ref:`3D <doc_navigation_overview_3d>`."
msgstr ""

#: ../../docs/about/list_of_features.rst:575
msgid ""
"Generate navigation meshes from the editor or at run-time (including from an "
"exported project)."
msgstr ""

#: ../../docs/about/list_of_features.rst:578
#: ../../docs/about/docs_changelog.rst:306
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:166
#: ../../docs/tutorials/export/exporting_for_web.rst:149
#: ../../docs/tutorials/networking/index.rst:4
msgid "Networking"
msgstr ""

#: ../../docs/about/list_of_features.rst:580
msgid ""
"Low-level TCP networking using :ref:`class_StreamPeer` and :ref:"
"`class_TCPServer`."
msgstr ""

#: ../../docs/about/list_of_features.rst:581
msgid ""
"Low-level UDP networking using :ref:`class_PacketPeer` and :ref:"
"`class_UDPServer`."
msgstr ""

#: ../../docs/about/list_of_features.rst:582
msgid "Low-level HTTP requests using :ref:`class_HTTPClient`."
msgstr ""

#: ../../docs/about/list_of_features.rst:583
msgid "High-level HTTP requests using :ref:`class_HTTPRequest`."
msgstr ""

#: ../../docs/about/list_of_features.rst:585
msgid "Supports HTTPS out of the box using bundled certificates."
msgstr ""

#: ../../docs/about/list_of_features.rst:587
msgid ""
":ref:`High-level multiplayer <doc_high_level_multiplayer>` API using UDP and "
"ENet."
msgstr ""

#: ../../docs/about/list_of_features.rst:589
msgid "Automatic replication using remote procedure calls (RPCs)."
msgstr ""

#: ../../docs/about/list_of_features.rst:590
msgid "Supports unreliable, reliable and ordered transfers."
msgstr ""

#: ../../docs/about/list_of_features.rst:592
msgid ""
":ref:`WebSocket <doc_websocket>` client and server, available on all "
"platforms."
msgstr ""

#: ../../docs/about/list_of_features.rst:593
msgid ""
":ref:`WebRTC <doc_webrtc>` client and server, available on all platforms."
msgstr ""

#: ../../docs/about/list_of_features.rst:594
msgid ""
"Support for :ref:`UPnP <class_UPNP>` to sidestep the requirement to forward "
"ports when hosting a server behind a NAT."
msgstr ""

#: ../../docs/about/list_of_features.rst:598
#: ../../docs/about/docs_changelog.rst:291
#: ../../docs/tutorials/i18n/index.rst:2
msgid "Internationalization"
msgstr ""

#: ../../docs/about/list_of_features.rst:600
msgid "Full support for Unicode including emoji."
msgstr ""

#: ../../docs/about/list_of_features.rst:601
msgid ""
"Store localization strings using :ref:`CSV <doc_internationalizing_games>` "
"or :ref:`gettext <doc_localization_using_gettext>`."
msgstr ""

#: ../../docs/about/list_of_features.rst:604
msgid "Support for generating gettext POT and PO files from the editor."
msgstr ""

#: ../../docs/about/list_of_features.rst:606
msgid ""
"Use localized strings in your project automatically in GUI elements or by "
"using the ``tr()`` function."
msgstr ""

#: ../../docs/about/list_of_features.rst:608
msgid ""
"Support for pluralization and translation contexts when using gettext "
"translations."
msgstr ""

#: ../../docs/about/list_of_features.rst:609
msgid ""
"Support for :ref:`bidirectional typesetting "
"<doc_internationalizing_games_bidi>`, text shaping and OpenType localized "
"forms."
msgstr ""

#: ../../docs/about/list_of_features.rst:611
msgid "Automatic UI mirroring for right-to-left locales."
msgstr ""

#: ../../docs/about/list_of_features.rst:612
msgid ""
"Support for pseudolocalization to test your project for i18n-friendliness."
msgstr ""

#: ../../docs/about/list_of_features.rst:615
msgid "Windowing and OS integration"
msgstr ""

#: ../../docs/about/list_of_features.rst:617
msgid "Spawn multiple independent windows within a single process."
msgstr ""

#: ../../docs/about/list_of_features.rst:618
msgid "Move, resize, minimize, and maximize windows spawned by the project."
msgstr ""

#: ../../docs/about/list_of_features.rst:619
msgid "Change the window title and icon."
msgstr ""

#: ../../docs/about/list_of_features.rst:620
msgid ""
"Request attention (will cause the title bar to blink on most platforms)."
msgstr ""

#: ../../docs/about/list_of_features.rst:621
msgid "Fullscreen mode."
msgstr ""

#: ../../docs/about/list_of_features.rst:623
msgid ""
"Uses borderless fullscreen by default on Windows for fast alt-tabbing, but "
"can optionally use exclusive fullscreen to reduce input lag."
msgstr ""

#: ../../docs/about/list_of_features.rst:626
msgid "Borderless windows (fullscreen or non-fullscreen)."
msgstr ""

#: ../../docs/about/list_of_features.rst:627
msgid "Ability to keep a window always on top."
msgstr ""

#: ../../docs/about/list_of_features.rst:628
msgid "Global menu integration on macOS."
msgstr ""

#: ../../docs/about/list_of_features.rst:629
msgid ""
"Execute commands in a blocking or non-blocking manner (including running "
"multiple instances of the same project)."
msgstr ""

#: ../../docs/about/list_of_features.rst:631
msgid ""
"Open file paths and URLs using default or custom protocol handlers (if "
"registered on the system)."
msgstr ""

#: ../../docs/about/list_of_features.rst:632
msgid "Parse custom command line arguments."
msgstr ""

#: ../../docs/about/list_of_features.rst:633
msgid ""
"Any Godot binary (editor or exported project) can be :ref:`used as a "
"headless server <doc_exporting_for_dedicated_servers>` by starting it with "
"the ``--headless`` command line argument. This allows running the engine "
"without a GPU or display server."
msgstr ""

#: ../../docs/about/list_of_features.rst:639
msgid "Mobile"
msgstr ""

#: ../../docs/about/list_of_features.rst:641
msgid ""
"In-app purchases on :ref:`Android <doc_android_in_app_purchases>` and :ref:"
"`iOS <doc_plugins_for_ios>`."
msgstr ""

#: ../../docs/about/list_of_features.rst:643
msgid "Support for advertisements using third-party modules."
msgstr ""

#: ../../docs/about/list_of_features.rst:646
msgid "XR support (AR and VR)"
msgstr ""

#: ../../docs/about/list_of_features.rst:648
msgid "Out of the box :ref:`support for OpenXR <doc_setting_up_xr>`."
msgstr ""

#: ../../docs/about/list_of_features.rst:650
msgid ""
"Including support for popular desktop headsets like the Valve Index, WMR "
"headsets, and Quest over Link."
msgstr ""

#: ../../docs/about/list_of_features.rst:652
msgid ""
"Support for :ref:`Android based headsets <doc_deploying_to_android>` using "
"OpenXR through a plugin."
msgstr ""

#: ../../docs/about/list_of_features.rst:654
msgid ""
"Including support for popular stand alone headsets like the Meta Quest 1/2/3 "
"and Pro, Pico 4, Magic Leap 2, and Lynx R1."
msgstr ""

#: ../../docs/about/list_of_features.rst:656
msgid "Other devices supported through an XR plugin structure."
msgstr ""

#: ../../docs/about/list_of_features.rst:657
msgid ""
"Various advanced toolkits are available that implement common features "
"required by XR applications."
msgstr ""

#: ../../docs/about/list_of_features.rst:660
msgid "GUI system"
msgstr ""

#: ../../docs/about/list_of_features.rst:662
msgid ""
"Godot's GUI is built using the same Control nodes used to make games in "
"Godot. The editor UI can easily be extended in many ways using add-ons."
msgstr ""

#: ../../docs/about/list_of_features.rst:665
msgid "**Nodes:**"
msgstr ""

#: ../../docs/about/list_of_features.rst:667
msgid "Buttons."
msgstr ""

#: ../../docs/about/list_of_features.rst:668
msgid "Checkboxes, check buttons, radio buttons."
msgstr ""

#: ../../docs/about/list_of_features.rst:669
msgid ""
"Text entry using :ref:`class_LineEdit` (single line) and :ref:"
"`class_TextEdit` (multiple lines). TextEdit also supports code editing "
"features such as displaying line numbers and syntax highlighting."
msgstr ""

#: ../../docs/about/list_of_features.rst:672
msgid ""
"Dropdown menus using :ref:`class_PopupMenu` and :ref:`class_OptionButton`."
msgstr ""

#: ../../docs/about/list_of_features.rst:673
msgid "Scrollbars."
msgstr ""

#: ../../docs/about/list_of_features.rst:674
msgid "Labels."
msgstr ""

#: ../../docs/about/list_of_features.rst:675
msgid ""
"RichTextLabel for :ref:`text formatted using BBCode "
"<doc_bbcode_in_richtextlabel>`, with support for animated custom effects."
msgstr ""

#: ../../docs/about/list_of_features.rst:677
msgid "Trees (can also be used to represent tables)."
msgstr ""

#: ../../docs/about/list_of_features.rst:678
msgid "Color picker with RGB and HSV modes."
msgstr ""

#: ../../docs/about/list_of_features.rst:679
msgid "Controls can be rotated and scaled."
msgstr ""

#: ../../docs/about/list_of_features.rst:681
msgid "**Sizing:**"
msgstr ""

#: ../../docs/about/list_of_features.rst:683
msgid "Anchors to keep GUI elements in a specific corner, edge or centered."
msgstr ""

#: ../../docs/about/list_of_features.rst:684
msgid "Containers to place GUI elements automatically following certain rules."
msgstr ""

#: ../../docs/about/list_of_features.rst:686
msgid ":ref:`Stack <class_BoxContainer>` layouts."
msgstr ""

#: ../../docs/about/list_of_features.rst:687
#, fuzzy
msgid ":ref:`Grid <class_GridContainer>` layouts."
msgstr "Kreiranje Sadržaja"

#: ../../docs/about/list_of_features.rst:688
msgid ""
":ref:`Flow <class_FlowContainer>` layouts (similar to autowrapping text)."
msgstr ""

#: ../../docs/about/list_of_features.rst:689
msgid ""
":ref:`Margin <class_MarginContainer>`, :ref:`centered "
"<class_CenterContainer>` and :ref:`aspect ratio "
"<class_AspectRatioContainer>` layouts."
msgstr ""

#: ../../docs/about/list_of_features.rst:691
msgid ":ref:`Draggable splitter <class_SplitContainer>` layouts."
msgstr ""

#: ../../docs/about/list_of_features.rst:693
msgid ""
"Scale to :ref:`multiple resolutions <doc_multiple_resolutions>` using the "
"``canvas_items`` or ``viewport`` stretch modes."
msgstr ""

#: ../../docs/about/list_of_features.rst:695
msgid ""
"Support any aspect ratio using anchors and the ``expand`` stretch aspect."
msgstr ""

#: ../../docs/about/list_of_features.rst:697
msgid "**Theming:**"
msgstr ""

#: ../../docs/about/list_of_features.rst:699
msgid "Built-in theme editor."
msgstr ""

#: ../../docs/about/list_of_features.rst:701
msgid "Generate a theme based on the current editor theme settings."
msgstr ""

#: ../../docs/about/list_of_features.rst:703
msgid "Procedural vector-based theming using :ref:`class_StyleBoxFlat`."
msgstr ""

#: ../../docs/about/list_of_features.rst:705
msgid ""
"Supports rounded/beveled corners, drop shadows, per-border widths and "
"antialiasing."
msgstr ""

#: ../../docs/about/list_of_features.rst:707
msgid "Texture-based theming using :ref:`class_StyleBoxTexture`."
msgstr ""

#: ../../docs/about/list_of_features.rst:709
msgid ""
"Godot's small distribution size can make it a suitable alternative to "
"frameworks like Electron or Qt."
msgstr ""

#: ../../docs/about/list_of_features.rst:713
#: ../../docs/about/docs_changelog.rst:85
#: ../../docs/about/docs_changelog.rst:148
#: ../../docs/about/docs_changelog.rst:393
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:49
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:62
#: ../../docs/tutorials/2d/particle_systems_2d.rst:374
#: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:713
#: ../../docs/tutorials/3d/particles/process_material_properties.rst:318
#: ../../docs/tutorials/animation/index.rst:2
#: ../../docs/tutorials/assets_pipeline/escn_exporter/animation.rst:2
#: ../../docs/contributing/development/file_formats/tscn.rst:383
msgid "Animation"
msgstr ""

#: ../../docs/about/list_of_features.rst:715
msgid "Direct kinematics and inverse kinematics."
msgstr ""

#: ../../docs/about/list_of_features.rst:716
msgid "Support for animating any property with customizable interpolation."
msgstr ""

#: ../../docs/about/list_of_features.rst:717
msgid "Support for calling methods in animation tracks."
msgstr ""

#: ../../docs/about/list_of_features.rst:718
msgid "Support for playing sounds in animation tracks."
msgstr ""

#: ../../docs/about/list_of_features.rst:719
msgid "Support for Bézier curves in animation."
msgstr ""

#: ../../docs/about/list_of_features.rst:722
msgid "File formats"
msgstr ""

#: ../../docs/about/list_of_features.rst:724
msgid ""
"Scenes and resources can be saved in :ref:`text-based "
"<doc_tscn_file_format>` or binary formats."
msgstr ""

#: ../../docs/about/list_of_features.rst:726
msgid ""
"Text-based formats are human-readable and more friendly to version control."
msgstr ""

#: ../../docs/about/list_of_features.rst:727
msgid "Binary formats are faster to save/load for large scenes/resources."
msgstr ""

#: ../../docs/about/list_of_features.rst:729
msgid "Read and write text or binary files using :ref:`class_FileAccess`."
msgstr ""

#: ../../docs/about/list_of_features.rst:731
msgid "Can optionally be compressed or encrypted."
msgstr ""

#: ../../docs/about/list_of_features.rst:733
msgid "Read and write :ref:`class_JSON` files."
msgstr ""

#: ../../docs/about/list_of_features.rst:734
msgid ""
"Read and write INI-style configuration files using :ref:`class_ConfigFile`."
msgstr ""

#: ../../docs/about/list_of_features.rst:736
msgid "Can (de)serialize any Godot datatype, including Vector2/3, Color, ..."
msgstr ""

#: ../../docs/about/list_of_features.rst:738
msgid "Read XML files using :ref:`class_XMLParser`."
msgstr ""

#: ../../docs/about/list_of_features.rst:739
msgid ""
":ref:`Load and save images, audio/video, fonts and ZIP archives "
"<doc_runtime_loading_and_saving>` in an exported project without having to "
"go through Godot's import system."
msgstr ""

#: ../../docs/about/list_of_features.rst:741
msgid ""
"Pack game data into a PCK file (custom format optimized for fast seeking), "
"into a ZIP archive, or directly into the executable for single-file "
"distribution."
msgstr ""

#: ../../docs/about/list_of_features.rst:743
msgid ""
":ref:`Export additional PCK files<doc_exporting_pcks>` that can be read by "
"the engine to support mods and DLCs."
msgstr ""

#: ../../docs/about/list_of_features.rst:747
#: ../../docs/about/docs_changelog.rst:445
msgid "Miscellaneous"
msgstr ""

#: ../../docs/about/list_of_features.rst:749
msgid ""
":ref:`Video playback <doc_playing_videos>` with built-in support for Ogg "
"Theora."
msgstr ""

#: ../../docs/about/list_of_features.rst:750
msgid ""
":ref:`Movie Maker mode <doc_creating_movies>` to record videos from a "
"running project with synchronized audio and perfect frame pacing."
msgstr ""

#: ../../docs/about/list_of_features.rst:752
msgid ""
":ref:`Low-level access to servers <doc_using_servers>` which allows "
"bypassing the scene tree's overhead when needed."
msgstr ""

#: ../../docs/about/list_of_features.rst:754
msgid ""
":ref:`Command line interface <doc_command_line_tutorial>` for automation."
msgstr ""

#: ../../docs/about/list_of_features.rst:756
msgid "Export and deploy projects using continuous integration platforms."
msgstr ""

#: ../../docs/about/list_of_features.rst:757
msgid ""
"`Shell completion scripts <https://github.com/godotengine/godot/tree/master/"
"misc/dist/shell>`__ are available for Bash, zsh and fish."
msgstr ""

#: ../../docs/about/list_of_features.rst:759
msgid ""
"Print colored text to standard output on all platforms using :ref:"
"`print_rich <class_@GlobalScope_method_print_rich>`."
msgstr ""

#: ../../docs/about/list_of_features.rst:762
msgid ""
"Support for :ref:`C++ modules <doc_custom_modules_in_cpp>` statically linked "
"into the engine binary."
msgstr ""

#: ../../docs/about/list_of_features.rst:764
msgid "Engine and editor written in C++17."
msgstr ""

#: ../../docs/about/list_of_features.rst:766
msgid ""
"Can be :ref:`compiled <doc_introduction_to_the_buildsystem>` using GCC, "
"Clang and MSVC. MinGW is also supported."
msgstr ""

#: ../../docs/about/list_of_features.rst:768
msgid ""
"Friendly towards packagers. In most cases, system libraries can be used "
"instead of the ones provided by Godot. The build system doesn't download "
"anything. Builds can be fully reproducible."
msgstr ""

#: ../../docs/about/list_of_features.rst:772
msgid "Licensed under the permissive MIT license."
msgstr ""

#: ../../docs/about/list_of_features.rst:774
msgid ""
"Open development process with :ref:`contributions welcome "
"<doc_ways_to_contribute>`."
msgstr ""

#: ../../docs/about/list_of_features.rst:778
msgid ""
"The `Godot proposals repository <https://github.com/godotengine/godot-"
"proposals>`__ lists features that have been requested by the community and "
"may be implemented in future Godot releases."
msgstr ""

#: ../../docs/about/system_requirements.rst:6
msgid "System requirements"
msgstr ""

#: ../../docs/about/system_requirements.rst:8
msgid ""
"This page contains system requirements for the editor and exported projects. "
"These specifications are given for informative purposes only, but they can "
"be referred to if you're looking to build or upgrade a system to use Godot "
"on."
msgstr ""

#: ../../docs/about/system_requirements.rst:13
#, fuzzy
msgid "Godot editor"
msgstr "Kreiranje Sadržaja"

#: ../../docs/about/system_requirements.rst:15
msgid ""
"These are the **minimum** specifications required to run the Godot editor "
"and work on a simple 2D or 3D project:"
msgstr ""

#: ../../docs/about/system_requirements.rst:19
#: ../../docs/about/system_requirements.rst:204
msgid "Desktop or laptop PC - Minimum"
msgstr ""

#: ../../docs/about/system_requirements.rst:26
#: ../../docs/about/system_requirements.rst:78
#: ../../docs/about/system_requirements.rst:116
#: ../../docs/about/system_requirements.rst:154
#: ../../docs/about/system_requirements.rst:211
#: ../../docs/about/system_requirements.rst:261
#: ../../docs/about/system_requirements.rst:299
#: ../../docs/about/system_requirements.rst:337
msgid "**CPU**"
msgstr ""

#: ../../docs/about/system_requirements.rst:26
#: ../../docs/about/system_requirements.rst:211
msgid "**Windows:** x86_32 CPU with SSE2 instructions, or any x86_64 CPU"
msgstr ""

#: ../../docs/about/system_requirements.rst:28
#: ../../docs/about/system_requirements.rst:213
msgid "*Example: Intel Core 2 Duo E8200, AMD Athlon XE BE-2300*"
msgstr ""

#: ../../docs/about/system_requirements.rst:30
#: ../../docs/about/system_requirements.rst:120
#: ../../docs/about/system_requirements.rst:215
#: ../../docs/about/system_requirements.rst:303
msgid "**macOS:** x86_64 or ARM CPU (Apple Silicon)"
msgstr ""

#: ../../docs/about/system_requirements.rst:32
#: ../../docs/about/system_requirements.rst:217
msgid "*Example: Intel Core 2 Duo SU9400, Apple M1*"
msgstr ""

#: ../../docs/about/system_requirements.rst:34
#: ../../docs/about/system_requirements.rst:124
#: ../../docs/about/system_requirements.rst:219
#: ../../docs/about/system_requirements.rst:307
msgid ""
"**Linux:** x86_32 CPU with SSE2 instructions, x86_64 CPU, ARMv7 or ARMv8 CPU"
msgstr ""

#: ../../docs/about/system_requirements.rst:36
#: ../../docs/about/system_requirements.rst:221
msgid ""
"*Example: Intel Core 2 Duo E8200, AMD Athlon XE BE-2300, Raspberry Pi 4*"
msgstr ""

#: ../../docs/about/system_requirements.rst:38
#: ../../docs/about/system_requirements.rst:84
#: ../../docs/about/system_requirements.rst:128
#: ../../docs/about/system_requirements.rst:160
#: ../../docs/about/system_requirements.rst:223
#: ../../docs/about/system_requirements.rst:269
#: ../../docs/about/system_requirements.rst:311
#: ../../docs/about/system_requirements.rst:345
msgid "**GPU**"
msgstr ""

#: ../../docs/about/system_requirements.rst:38
#: ../../docs/about/system_requirements.rst:223
msgid ""
"**Forward+ rendering method:** Integrated graphics with full Vulkan 1.0 "
"support"
msgstr ""

#: ../../docs/about/system_requirements.rst:40
#: ../../docs/about/system_requirements.rst:44
#: ../../docs/about/system_requirements.rst:225
#: ../../docs/about/system_requirements.rst:229
msgid ""
"*Example: Intel HD Graphics 5500 (Broadwell), AMD Radeon R5 Graphics "
"(Kaveri)*"
msgstr ""

#: ../../docs/about/system_requirements.rst:42
#: ../../docs/about/system_requirements.rst:227
msgid ""
"**Mobile rendering method:** Integrated graphics with full Vulkan 1.0 support"
msgstr ""

#: ../../docs/about/system_requirements.rst:46
#: ../../docs/about/system_requirements.rst:231
msgid ""
"**Compatibility rendering method:** Integrated graphics with full OpenGL 3.3 "
"support"
msgstr ""

#: ../../docs/about/system_requirements.rst:48
#: ../../docs/about/system_requirements.rst:233
msgid ""
"*Example: Intel HD Graphics 2500 (Ivy Bridge), AMD Radeon R5 Graphics "
"(Kaveri)*"
msgstr ""

#: ../../docs/about/system_requirements.rst:50
#: ../../docs/about/system_requirements.rst:96
#: ../../docs/about/system_requirements.rst:140
#: ../../docs/about/system_requirements.rst:172
#: ../../docs/about/system_requirements.rst:235
#: ../../docs/about/system_requirements.rst:281
#: ../../docs/about/system_requirements.rst:323
#: ../../docs/about/system_requirements.rst:357
msgid "**RAM**"
msgstr ""

#: ../../docs/about/system_requirements.rst:50
#, fuzzy
msgid "**Native editor:** 4 GB"
msgstr "**Za uređivač:**"

#: ../../docs/about/system_requirements.rst:51
#: ../../docs/about/system_requirements.rst:173
#, fuzzy
msgid "**Web editor:** 8 GB"
msgstr "**Za uređivač:**"

#: ../../docs/about/system_requirements.rst:53
#: ../../docs/about/system_requirements.rst:99
#: ../../docs/about/system_requirements.rst:143
#: ../../docs/about/system_requirements.rst:175
#: ../../docs/about/system_requirements.rst:238
#: ../../docs/about/system_requirements.rst:284
#: ../../docs/about/system_requirements.rst:326
#: ../../docs/about/system_requirements.rst:360
msgid "**Storage**"
msgstr ""

#: ../../docs/about/system_requirements.rst:53
#: ../../docs/about/system_requirements.rst:99
msgid ""
"200 MB (used for the executable, project files and cache). Exporting "
"projects requires downloading export templates separately (1.3 GB after "
"installation)."
msgstr ""

#: ../../docs/about/system_requirements.rst:57
#: ../../docs/about/system_requirements.rst:103
#: ../../docs/about/system_requirements.rst:145
#: ../../docs/about/system_requirements.rst:177
#: ../../docs/about/system_requirements.rst:240
#: ../../docs/about/system_requirements.rst:286
#: ../../docs/about/system_requirements.rst:328
#: ../../docs/about/system_requirements.rst:362
msgid "**Operating system**"
msgstr ""

#: ../../docs/about/system_requirements.rst:57
msgid ""
"**Native editor:** Windows 7, macOS 10.13 (Compatibility) or macOS 10.15 "
"(Forward+/Mobile), Linux distribution released after 2016"
msgstr ""

#: ../../docs/about/system_requirements.rst:59
msgid "**Web editor:** Firefox 79, Chrome 68, Edge 79, Safari 15.2, Opera 64"
msgstr ""

#: ../../docs/about/system_requirements.rst:64
#: ../../docs/about/system_requirements.rst:247
msgid ""
"Windows 7/8/8.1 are supported on a best-effort basis. These versions are not "
"regularly tested and some features may be missing (such as colored :ref:"
"`print_rich <class_@GlobalScope_method_print_rich>` console output). Support "
"for Windows 7/8/8.1 may be removed in a :ref:`future Godot 4.x release "
"<doc_release_policy>`."
msgstr ""

#: ../../docs/about/system_requirements.rst:70
#: ../../docs/about/system_requirements.rst:253
msgid ""
"Vulkan drivers for these Windows versions are known to have issues with "
"memory leaks. As a result, it's recommended to stick to the Compatibility "
"rendering method when running Godot on an Windows version older than 10."
msgstr ""

#: ../../docs/about/system_requirements.rst:75
#: ../../docs/about/system_requirements.rst:258
msgid "Mobile device (smartphone/tablet) - Minimum"
msgstr ""

#: ../../docs/about/system_requirements.rst:78
#: ../../docs/about/system_requirements.rst:261
msgid "**Android:** SoC with any 32-bit or 64-bit ARM or x86 CPU"
msgstr ""

#: ../../docs/about/system_requirements.rst:80
#: ../../docs/about/system_requirements.rst:263
msgid "*Example: Qualcomm Snapdragon 430, Samsung Exynos 5 Octa 5430*"
msgstr ""

#: ../../docs/about/system_requirements.rst:82
#: ../../docs/about/system_requirements.rst:158
#, fuzzy
msgid "**iOS:** *Cannot run the editor*"
msgstr "**Za uređivač:**"

#: ../../docs/about/system_requirements.rst:84
#: ../../docs/about/system_requirements.rst:269
msgid ""
"**Forward+ rendering method:** SoC featuring GPU with full Vulkan 1.0 support"
msgstr ""

#: ../../docs/about/system_requirements.rst:86
#: ../../docs/about/system_requirements.rst:90
msgid "*Example: Qualcomm Adreno 505, Mali-G71 MP2*"
msgstr ""

#: ../../docs/about/system_requirements.rst:88
#: ../../docs/about/system_requirements.rst:273
msgid ""
"**Mobile rendering method:** SoC featuring GPU with full Vulkan 1.0 support"
msgstr ""

#: ../../docs/about/system_requirements.rst:92
#: ../../docs/about/system_requirements.rst:277
msgid ""
"**Compatibility rendering method:** SoC featuring GPU with full OpenGL ES "
"3.0 support"
msgstr ""

#: ../../docs/about/system_requirements.rst:94
msgid "*Example: Qualcomm Adreno 306, Mali-T628 MP6*"
msgstr ""

#: ../../docs/about/system_requirements.rst:96
#, fuzzy
msgid "**Native editor:** 3 GB"
msgstr "**Za uređivač:**"

#: ../../docs/about/system_requirements.rst:97
#, fuzzy
msgid "**Web editor:** 6 GB"
msgstr "**Za uređivač:**"

#: ../../docs/about/system_requirements.rst:103
msgid ""
"**Native editor:** Android 6.0 (Compatibility) or Android 9.0 (Forward+/"
"Mobile), iOS 11.0"
msgstr ""

#: ../../docs/about/system_requirements.rst:105
msgid ""
"**Web editor:** Firefox 79, Chrome 88, Edge 79, Safari 15.2, Opera 64, "
"Samsung Internet 15"
msgstr ""

#: ../../docs/about/system_requirements.rst:109
msgid ""
"These are the **recommended** specifications to get a smooth experience with "
"the Godot editor on a simple 2D or 3D project:"
msgstr ""

#: ../../docs/about/system_requirements.rst:113
#: ../../docs/about/system_requirements.rst:296
msgid "Desktop or laptop PC - Recommended"
msgstr ""

#: ../../docs/about/system_requirements.rst:116
#: ../../docs/about/system_requirements.rst:299
msgid ""
"**Windows:** x86_64 CPU with SSE4.2 instructions, with 4 physical cores or "
"more"
msgstr ""

#: ../../docs/about/system_requirements.rst:118
#: ../../docs/about/system_requirements.rst:301
msgid "*Example: Intel Core i5-6600K, AMD Ryzen 5 1600*"
msgstr ""

#: ../../docs/about/system_requirements.rst:122
#: ../../docs/about/system_requirements.rst:305
msgid "*Example: Intel Core i5-8500, Apple M1*"
msgstr ""

#: ../../docs/about/system_requirements.rst:126
#: ../../docs/about/system_requirements.rst:309
msgid ""
"*Example: Intel Core i5-6600K, AMD Ryzen 5 1600, Raspberry Pi 5 with "
"overclocking*"
msgstr ""

#: ../../docs/about/system_requirements.rst:128
#: ../../docs/about/system_requirements.rst:311
msgid ""
"**Forward+ rendering method:** Dedicated graphics with full Vulkan 1.2 "
"support"
msgstr ""

#: ../../docs/about/system_requirements.rst:130
#: ../../docs/about/system_requirements.rst:134
#: ../../docs/about/system_requirements.rst:313
#: ../../docs/about/system_requirements.rst:317
msgid ""
"*Example: NVIDIA GeForce GTX 1050 (Pascal), AMD Radeon RX 460 (GCN 4.0)*"
msgstr ""

#: ../../docs/about/system_requirements.rst:132
#: ../../docs/about/system_requirements.rst:315
msgid ""
"**Mobile rendering method:** Dedicated graphics with full Vulkan 1.2 support"
msgstr ""

#: ../../docs/about/system_requirements.rst:136
#: ../../docs/about/system_requirements.rst:319
msgid ""
"**Compatibility rendering method:** Dedicated graphics with full OpenGL 4.6 "
"support"
msgstr ""

#: ../../docs/about/system_requirements.rst:138
#: ../../docs/about/system_requirements.rst:321
msgid ""
"*Example: NVIDIA GeForce GTX 650 (Kepler), AMD Radeon HD 7750 (GCN 1.0)*"
msgstr ""

#: ../../docs/about/system_requirements.rst:140
#, fuzzy
msgid "**Native editor:** 8 GB"
msgstr "**Za uređivač:**"

#: ../../docs/about/system_requirements.rst:141
#, fuzzy
msgid "**Web editor:** 12 GB"
msgstr "**Za uređivač:**"

#: ../../docs/about/system_requirements.rst:143
#: ../../docs/about/system_requirements.rst:175
msgid ""
"1.5 GB (used for the executable, project files, all export templates and "
"cache)"
msgstr ""

#: ../../docs/about/system_requirements.rst:145
msgid ""
"**Native editor:** Windows 10, macOS 10.15, Linux distribution released "
"after 2020"
msgstr ""

#: ../../docs/about/system_requirements.rst:147
msgid "**Web editor:** Latest version of Firefox, Chrome, Edge, Safari, Opera"
msgstr ""

#: ../../docs/about/system_requirements.rst:151
#: ../../docs/about/system_requirements.rst:334
msgid "Mobile device (smartphone/tablet) - Recommended"
msgstr ""

#: ../../docs/about/system_requirements.rst:154
#: ../../docs/about/system_requirements.rst:337
msgid ""
"**Android:** SoC with 64-bit ARM or x86 CPU, with 3 \"performance\" cores or "
"more"
msgstr ""

#: ../../docs/about/system_requirements.rst:156
#: ../../docs/about/system_requirements.rst:339
msgid "*Example: Qualcomm Snapdragon 845, Samsung Exynos 9810*"
msgstr ""

#: ../../docs/about/system_requirements.rst:160
#: ../../docs/about/system_requirements.rst:345
msgid ""
"**Forward+ rendering method:** SoC featuring GPU with full Vulkan 1.2 support"
msgstr ""

#: ../../docs/about/system_requirements.rst:162
#: ../../docs/about/system_requirements.rst:166
#: ../../docs/about/system_requirements.rst:170
msgid "*Example: Qualcomm Adreno 630, Mali-G72 MP18*"
msgstr ""

#: ../../docs/about/system_requirements.rst:164
#: ../../docs/about/system_requirements.rst:349
msgid ""
"**Mobile rendering method:** SoC featuring GPU with full Vulkan 1.2 support"
msgstr ""

#: ../../docs/about/system_requirements.rst:168
#: ../../docs/about/system_requirements.rst:353
msgid ""
"**Compatibility rendering method:** SoC featuring GPU with full OpenGL ES "
"3.2 support"
msgstr ""

#: ../../docs/about/system_requirements.rst:172
#, fuzzy
msgid "**Native editor:** 6 GB"
msgstr "**Za uređivač:**"

#: ../../docs/about/system_requirements.rst:177
msgid "**Native editor:** Android 9.0 or iOS 11.0"
msgstr ""

#: ../../docs/about/system_requirements.rst:178
msgid ""
"**Web editor:** Latest version of Firefox, Chrome, Edge, Safari, Opera, "
"Samsung Internet"
msgstr ""

#: ../../docs/about/system_requirements.rst:183
#, fuzzy
msgid "Exported Godot project"
msgstr "Kreiranje Sadržaja"

#: ../../docs/about/system_requirements.rst:187
msgid ""
"The requirements below are a baseline for a **simple** 2D or 3D project, "
"with basic scripting and few visual flourishes. CPU, GPU, RAM and storage "
"requirements will heavily vary depending on your project's scope, its "
"rendering method, viewport resolution and graphics settings chosen. Other "
"programs running on the system while the project is running will also "
"compete for resources, including RAM and video RAM."
msgstr ""

#: ../../docs/about/system_requirements.rst:194
msgid ""
"It is strongly recommended to do your own testing on low-end hardware to "
"make sure your project runs at the desired speed. To provide scalability for "
"low-end hardware, you will also need to introduce a `graphics options menu "
"<https://github.com/godotengine/godot-demo-projects/tree/master/3d/"
"graphics_settings>`__ to your project."
msgstr ""

#: ../../docs/about/system_requirements.rst:200
msgid ""
"These are the **minimum** specifications required to run a simple 2D or 3D "
"project exported with Godot:"
msgstr ""

#: ../../docs/about/system_requirements.rst:235
#: ../../docs/about/system_requirements.rst:357
#, fuzzy
msgid "**For native exports:** 2 GB"
msgstr "**Za uređivač:**"

#: ../../docs/about/system_requirements.rst:236
#: ../../docs/about/system_requirements.rst:358
#, fuzzy
msgid "**For web exports:** 4 GB"
msgstr "**Za uređivač:**"

#: ../../docs/about/system_requirements.rst:238
#: ../../docs/about/system_requirements.rst:284
#: ../../docs/about/system_requirements.rst:326
#: ../../docs/about/system_requirements.rst:360
msgid "150 MB (used for the executable, project files and cache)"
msgstr ""

#: ../../docs/about/system_requirements.rst:240
msgid ""
"**For native exports:** Windows 7, macOS 10.13 (Compatibility) or macOS "
"10.15 (Forward+/Mobile), Linux distribution released after 2016"
msgstr ""

#: ../../docs/about/system_requirements.rst:242
msgid ""
"**For web exports:** Firefox 79, Chrome 68, Edge 79, Safari 15.2, Opera 64"
msgstr ""

#: ../../docs/about/system_requirements.rst:265
msgid "**iOS:** SoC with any 64-bit ARM CPU"
msgstr ""

#: ../../docs/about/system_requirements.rst:267
msgid "*Example: Apple A7 (iPhone 5S)*"
msgstr ""

#: ../../docs/about/system_requirements.rst:271
#: ../../docs/about/system_requirements.rst:275
msgid ""
"*Example: Qualcomm Adreno 505, Mali-G71 MP2, PowerVR G6430 (iPhone 6S/iPhone "
"SE 1)*"
msgstr ""

#: ../../docs/about/system_requirements.rst:279
msgid ""
"*Example: Qualcomm Adreno 306, Mali-T628 MP6, PowerVR G6430 (iPhone 5S)*"
msgstr ""

#: ../../docs/about/system_requirements.rst:281
#, fuzzy
msgid "**For native exports:** 1 GB"
msgstr "**Za uređivač:**"

#: ../../docs/about/system_requirements.rst:282
#, fuzzy
msgid "**For web exports:** 2 GB"
msgstr "**Za uređivač:**"

#: ../../docs/about/system_requirements.rst:286
msgid ""
"**For native exports:** Android 6.0 (Compatibility) or Android 9.0 (Forward+/"
"Mobile), iOS 11.0"
msgstr ""

#: ../../docs/about/system_requirements.rst:288
msgid ""
"**For web exports:** Firefox 79, Chrome 88, Edge 79, Safari 15.2, Opera 64, "
"Samsung Internet 15"
msgstr ""

#: ../../docs/about/system_requirements.rst:292
msgid ""
"These are the **recommended** specifications to get a smooth experience with "
"a simple 2D or 3D project exported with Godot:"
msgstr ""

#: ../../docs/about/system_requirements.rst:323
#, fuzzy
msgid "**For native exports:** 4 GB"
msgstr "**Za uređivač:**"

#: ../../docs/about/system_requirements.rst:324
#, fuzzy
msgid "**For web exports:** 8 GB"
msgstr "**Za uređivač:**"

#: ../../docs/about/system_requirements.rst:328
msgid ""
"**For native exports:** Windows 10, macOS 10.15, Linux distribution released "
"after 2020"
msgstr ""

#: ../../docs/about/system_requirements.rst:330
msgid ""
"**For web exports:** Latest version of Firefox, Chrome, Edge, Safari, Opera"
msgstr ""

#: ../../docs/about/system_requirements.rst:341
msgid "**iOS:** SoC with 64-bit ARM CPU"
msgstr ""

#: ../../docs/about/system_requirements.rst:343
msgid "*Example: Apple A11 (iPhone XS/XR)*"
msgstr ""

#: ../../docs/about/system_requirements.rst:347
#: ../../docs/about/system_requirements.rst:351
#: ../../docs/about/system_requirements.rst:355
msgid ""
"*Example: Qualcomm Adreno 630, Mali-G72 MP18, Apple G11P (iPhone XR/XS)*"
msgstr ""

#: ../../docs/about/system_requirements.rst:362
msgid "**For native exports:** Android 9.0 or iOS 11.0"
msgstr ""

#: ../../docs/about/system_requirements.rst:363
msgid ""
"**For web exports:** Latest version of Firefox, Chrome, Edge, Safari, Opera, "
"Samsung Internet"
msgstr ""

#: ../../docs/about/system_requirements.rst:369
msgid ""
"Godot doesn't use OpenGL/OpenGL ES extensions introduced after OpenGL 3.3/"
"OpenGL ES 3.0, but GPUs supporting newer OpenGL/OpenGL ES versions generally "
"have fewer driver issues."
msgstr ""

#: ../../docs/about/faq.rst:-1
msgid "FAQ"
msgstr ""

#: ../../docs/about/faq.rst:7
#: ../../docs/community/asset_library/what_is_assetlib.rst:42
msgid "Frequently asked questions"
msgstr "Često postavljana pitanja"

#: ../../docs/about/faq.rst:10
msgid ""
"What can I do with Godot? How much does it cost? What are the license terms?"
msgstr "Šta mogu raditi sa Godot-om? Koliko košta? Koji su uslovi licence?"

#: ../../docs/about/faq.rst:12
#, fuzzy
msgid ""
"Godot is `Free and open source Software <https://en.wikipedia.org/wiki/"
"Free_and_open source_software>`_ available under the `OSI-approved <https://"
"opensource.org/licenses/MIT>`_ MIT license. This means it is free as in "
"\"free speech\" as well as in \"free beer.\""
msgstr ""
"Godot je besplatan/Libre softver otvorenog koda `Free and Open-Source "
"Software <https://en.wikipedia.org/wiki/Free_and_open-source_software>`_ "
"dostupan pod `OSI-approved <https://opensource.org/licenses/MIT>`_ MIT "
"licencom.\n"
"To znači da je istovremeno i besplatan i otvorenog koda."

#: ../../docs/about/faq.rst:16
msgid "In short:"
msgstr "Ukratko:"

#: ../../docs/about/faq.rst:18
#, fuzzy
msgid ""
"You are free to download and use Godot for any purpose: personal, non-"
"profit, commercial, or otherwise."
msgstr ""
"Dozvoljeno je da preuzmete i koristite Godo slobodno i za bilo koju svrhu, "
"bilo to za privatnu upotrebu, neprofitnu ili komercijalnu;"

#: ../../docs/about/faq.rst:19
#, fuzzy
msgid ""
"You are free to modify, distribute, redistribute, and remix Godot to your "
"heart's content, for any reason, both non-commercially and commercially."
msgstr ""
"Možete mjenjati, redistribuirati i prilagođavati  Godot kako god vam je srcu "
"drago"

#: ../../docs/about/faq.rst:22
#, fuzzy
msgid ""
"All the contents of this accompanying documentation are published under the "
"permissive Creative Commons Attribution 3.0 (`CC BY 3.0 <https://"
"creativecommons.org/licenses/by/3.0/>`_) license, with attribution to \"Juan "
"Linietsky, Ariel Manzur and the Godot Engine community.\""
msgstr ""
"Sav sadržaj dokumentacije je pod popustljivom (`CC-BY 3.0 <https://"
"creativecommons.org/licenses/by/3.0/>`_) licencom, sa atribucijom \"Juan "
"Linietsky, Ariel Manzur and the Godot Engine community\"."

#: ../../docs/about/faq.rst:26
msgid ""
"Logos and icons are generally under the same Creative Commons license. Note "
"that some third-party libraries included with Godot's source code may have "
"different licenses."
msgstr ""
"Logoi i ikone su najčešće pod istom Creative Commons licencom. Ipak, neke "
"biblioteke uključene u izvorni kod Godot-a mogu imati drugačije licence."

#: ../../docs/about/faq.rst:30
#, fuzzy
msgid ""
"For full details, look at the `COPYRIGHT.txt <https://github.com/godotengine/"
"godot/blob/master/COPYRIGHT.txt>`_ as well as the `LICENSE.txt <https://"
"github.com/godotengine/godot/blob/master/LICENSE.txt>`_ and `LOGO_LICENSE."
"txt <https://github.com/godotengine/godot/blob/master/LOGO_LICENSE.txt>`_ "
"files in the Godot repository."
msgstr ""
"Za sve detalje pogledajte `COPYRIGHT.txt <https://github.com/godotengine/"
"godot/blob/master/COPYRIGHT.txt>`_  kao i `LICENSE.txt <https://github.com/"
"godotengine/godot/blob/master/LICENSE.txt>`_ i `LOGO_LICENSE.txt <https://"
"github.com/godotengine/godot/blob/master/LOGO_LICENSE.md>`_ fajlove u Godot "
"repozitoriju."

#: ../../docs/about/faq.rst:35
#, fuzzy
msgid ""
"Also, see `the license page on the Godot website <https://godotengine.org/"
"license>`_."
msgstr ""
"Takođe pogledajte `licencu na Godot sajtu <https://godotengine.org/"
"license>`_."

#: ../../docs/about/faq.rst:38
msgid "Which platforms are supported by Godot?"
msgstr "Koje platforme su podržane u Godot-u?"

#: ../../docs/about/faq.rst:40
#, fuzzy
msgid "**For the editor:**"
msgstr "**Za uređivač:**"

#: ../../docs/about/faq.rst:42 ../../docs/about/faq.rst:50
#: ../../docs/about/faq.rst:226
#: ../../docs/tutorials/rendering/jitter_stutter.rst:84
#: ../../docs/tutorials/ui/gui_using_fonts.rst:764
#: ../../docs/contributing/development/debugging/vulkan/vulkan_validation_layers.rst:16
#: ../../docs/contributing/documentation/building_the_manual.rst:29
#: ../../docs/contributing/documentation/building_the_manual.rst:45
#: ../../docs/contributing/documentation/building_the_manual.rst:61
#: ../../docs/contributing/documentation/building_the_manual.rst:145
msgid "Windows"
msgstr "Windows"

#: ../../docs/about/faq.rst:43 ../../docs/about/faq.rst:51
#: ../../docs/about/faq.rst:237
#: ../../docs/tutorials/editor/default_key_mapping.rst:29
#: ../../docs/tutorials/editor/default_key_mapping.rst:94
#: ../../docs/tutorials/editor/default_key_mapping.rst:147
#: ../../docs/tutorials/editor/default_key_mapping.rst:222
#: ../../docs/tutorials/editor/default_key_mapping.rst:303
#: ../../docs/tutorials/editor/default_key_mapping.rst:350
#: ../../docs/tutorials/editor/default_key_mapping.rst:361
#: ../../docs/tutorials/editor/default_key_mapping.rst:374
#: ../../docs/tutorials/editor/default_key_mapping.rst:405
#: ../../docs/tutorials/editor/default_key_mapping.rst:418
#: ../../docs/tutorials/editor/default_key_mapping.rst:441
#: ../../docs/tutorials/editor/default_key_mapping.rst:458
#: ../../docs/tutorials/editor/default_key_mapping.rst:497
#: ../../docs/tutorials/rendering/jitter_stutter.rst:133
#: ../../docs/contributing/development/debugging/vulkan/vulkan_validation_layers.rst:30
msgid "macOS"
msgstr ""

#: ../../docs/about/faq.rst:44 ../../docs/about/faq.rst:52
#: ../../docs/contributing/development/debugging/vulkan/vulkan_validation_layers.rst:58
msgid "Linux, \\*BSD"
msgstr ""

#: ../../docs/about/faq.rst:45
msgid "Android (experimental)"
msgstr ""

#: ../../docs/about/faq.rst:46
msgid "`Web <https://editor.godotengine.org/>`__ (experimental)"
msgstr ""

#: ../../docs/about/faq.rst:48
msgid "**For exporting your games:**"
msgstr "**Za izvoz vaših igara:**"

#: ../../docs/about/faq.rst:53
#: ../../docs/tutorials/export/one-click_deploy.rst:68
#: ../../docs/tutorials/platform/android/index.rst:2
#: ../../docs/tutorials/rendering/jitter_stutter.rst:140
#: ../../docs/tutorials/ui/gui_using_fonts.rst:764
#: ../../docs/contributing/development/debugging/vulkan/vulkan_validation_layers.rst:135
msgid "Android"
msgstr ""

#: ../../docs/about/faq.rst:54
#: ../../docs/tutorials/rendering/jitter_stutter.rst:147
#: ../../docs/contributing/development/debugging/vulkan/vulkan_validation_layers.rst:141
msgid "iOS"
msgstr ""

#: ../../docs/about/faq.rst:55
#: ../../docs/contributing/development/compiling/optimizing_for_size.rst:298
#: ../../docs/contributing/development/debugging/using_sanitizers.rst:166
#: ../../docs/contributing/development/debugging/vulkan/vulkan_validation_layers.rst:146
msgid "Web"
msgstr ""

#: ../../docs/about/faq.rst:57
#, fuzzy
msgid ""
"Both 32- and 64-bit binaries are supported where it makes sense, with 64 "
"being the default. Official macOS builds support Apple Silicon natively as "
"well as x86_64."
msgstr ""
"32-bitni i 64-bitni izvoz je podržan gdje god je to moguće, s tim da je 64-"
"bitni uobičajeni izbor."

#: ../../docs/about/faq.rst:60
msgid ""
"Some users also report building and using Godot successfully on ARM-based "
"systems with Linux, like the Raspberry Pi."
msgstr ""

#: ../../docs/about/faq.rst:63
msgid ""
"The Godot team can't provide an open source console export due to the "
"licensing terms imposed by console manufacturers. Regardless of the engine "
"you use, though, releasing games on consoles is always a lot of work. You "
"can read more about :ref:`doc_consoles`."
msgstr ""

#: ../../docs/about/faq.rst:68
msgid ""
"For more on this, see the sections on :ref:`exporting <toc-learn-workflow-"
"export>` and :ref:`compiling Godot yourself <toc-devel-compiling>`."
msgstr ""
"Za više podataka o ovome, pogledajte sekcije :ref:`izvoz<toc-learn-workflow-"
"export>` and :ref:`kompajlirajte Godot sami <toc-devel-compiling>`."

#: ../../docs/about/faq.rst:73
msgid ""
"Godot 3 also had support for Universal Windows Platform (UWP). This platform "
"port was removed in Godot 4 due to lack of maintenance, and it being "
"deprecated by Microsoft. It is still available in the current stable release "
"of Godot 3 for interested users."
msgstr ""

#: ../../docs/about/faq.rst:79
#, fuzzy
msgid "Which programming languages are supported in Godot?"
msgstr "Koji jezici su podržani u Godot-u?"

#: ../../docs/about/faq.rst:81
msgid ""
"The officially supported languages for Godot are GDScript, C#, and C++. See "
"the subcategories for each language in the :ref:`scripting <toc-learn-"
"scripting>` section."
msgstr ""

#: ../../docs/about/faq.rst:84
msgid ""
"If you are just starting out with either Godot or game development in "
"general, GDScript is the recommended language to learn and use since it is "
"native to Godot. While scripting languages tend to be less performant than "
"lower-level languages in the long run, for prototyping, developing Minimum "
"Viable Products (MVPs), and focusing on Time-To-Market (TTM), GDScript will "
"provide a fast, friendly, and capable way of developing your games."
msgstr ""

#: ../../docs/about/faq.rst:91
msgid ""
"Note that C# support is still relatively new, and as such, you may encounter "
"some issues along the way. C# support is also currently missing on the web "
"platform. Our friendly and hard-working development community is always "
"ready to tackle new problems as they arise, but since this is an open source "
"project, we recommend that you first do some due diligence yourself. "
"Searching through discussions on `open issues <https://github.com/"
"godotengine/godot/issues?q=is%3Aopen+is%3Aissue+label%3Atopic%3Adotnet>`__ "
"is a great way to start your troubleshooting."
msgstr ""

#: ../../docs/about/faq.rst:100
msgid ""
"As for new languages, support is possible via third parties with "
"GDExtensions. (See the question about plugins below). Work is currently "
"underway, for example, on unofficial bindings for Godot to `Python <https://"
"github.com/touilleMan/godot-python>`_ and `Nim <https://github.com/pragmagic/"
"godot-nim>`_."
msgstr ""

#: ../../docs/about/faq.rst:107
msgid "What is GDScript and why should I use it?"
msgstr ""

#: ../../docs/about/faq.rst:109
msgid ""
"GDScript is Godot's integrated scripting language. It was built from the "
"ground up to maximize Godot's potential in the least amount of code, "
"affording both novice and expert developers alike to capitalize on Godot's "
"strengths as fast as possible. If you've ever written anything in a language "
"like Python before, then you'll feel right at home. For examples and a "
"complete overview of the power GDScript offers you, check out the :ref:"
"`GDScript scripting guide <doc_gdscript>`."
msgstr ""

#: ../../docs/about/faq.rst:116
msgid ""
"There are several reasons to use GDScript, especially when you are "
"prototyping, in alpha/beta stages of your project, or are not creating the "
"next AAA title. The most salient reason is the overall **reduction of "
"complexity**."
msgstr ""

#: ../../docs/about/faq.rst:120
msgid ""
"The original intent of creating a tightly integrated, custom scripting "
"language for Godot was two-fold: first, it reduces the amount of time "
"necessary to get up and running with Godot, giving developers a rapid way of "
"exposing themselves to the engine with a focus on productivity; second, it "
"reduces the overall burden of maintenance, attenuates the dimensionality of "
"issues, and allows the developers of the engine to focus on squashing bugs "
"and improving features related to the engine core, rather than spending a "
"lot of time trying to get a small set of incremental features working across "
"a large set of languages."
msgstr ""

#: ../../docs/about/faq.rst:128
msgid ""
"Since Godot is an open source project, it was imperative from the start to "
"prioritize a more integrated and seamless experience over attracting "
"additional users by supporting more familiar programming languages, "
"especially when supporting those more familiar languages would result in a "
"worse experience. We understand if you would rather use another language in "
"Godot (see the list of supported options above). That being said, if you "
"haven't given GDScript a try, try it for **three days**. Just like Godot, "
"once you see how powerful it is and rapid your development becomes, we think "
"GDScript will grow on you."
msgstr ""

#: ../../docs/about/faq.rst:137
msgid ""
"More information about getting comfortable with GDScript or dynamically "
"typed languages can be found in the :ref:`doc_gdscript_more_efficiently` "
"tutorial."
msgstr ""

#: ../../docs/about/faq.rst:141
msgid "What were the motivations behind creating GDScript?"
msgstr ""

#: ../../docs/about/faq.rst:143
msgid ""
"In the early days, the engine used the `Lua <https://www.lua.org>`__ "
"scripting language. Lua can be fast thanks to LuaJIT, but creating bindings "
"to an object-oriented system (by using fallbacks) was complex and slow and "
"took an enormous amount of code. After some experiments with `Python "
"<https://www.python.org>`__, that also proved difficult to embed."
msgstr ""

#: ../../docs/about/faq.rst:149
msgid ""
"The main reasons for creating a custom scripting language for Godot were:"
msgstr ""

#: ../../docs/about/faq.rst:151
msgid ""
"Poor threading support in most script VMs, and Godot uses threads (Lua, "
"Python, Squirrel, JavaScript, ActionScript, etc.)."
msgstr ""

#: ../../docs/about/faq.rst:153
msgid ""
"Poor class-extending support in most script VMs, and adapting to the way "
"Godot works is highly inefficient (Lua, Python, JavaScript)."
msgstr ""

#: ../../docs/about/faq.rst:155
msgid ""
"Many existing languages have horrible interfaces for binding to C++, "
"resulting in a large amount of code, bugs, bottlenecks, and general "
"inefficiency (Lua, Python, Squirrel, JavaScript, etc.). We wanted to focus "
"on a great engine, not a great number of integrations."
msgstr ""

#: ../../docs/about/faq.rst:159
msgid ""
"No native vector types (Vector3, Transform3D, etc.), resulting in highly "
"reduced performance when using custom types (Lua, Python, Squirrel, "
"JavaScript, ActionScript, etc.)."
msgstr ""

#: ../../docs/about/faq.rst:162
msgid ""
"Garbage collector results in stalls or unnecessarily large memory usage "
"(Lua, Python, JavaScript, ActionScript, etc.)."
msgstr ""

#: ../../docs/about/faq.rst:164
msgid ""
"Difficulty integrating with the code editor for providing code completion, "
"live editing, etc. (all of them)."
msgstr ""

#: ../../docs/about/faq.rst:167
msgid "GDScript was designed to curtail the issues above, and more."
msgstr ""

#: ../../docs/about/faq.rst:170
msgid "What 3D model formats does Godot support?"
msgstr ""

#: ../../docs/about/faq.rst:172
msgid ""
"You can find detailed information on supported formats, how to export them "
"from your 3D modeling software, and how to import them for Godot in the :ref:"
"`doc_importing_3d_scenes` documentation."
msgstr ""

#: ../../docs/about/faq.rst:177
msgid ""
"Will [insert closed SDK such as FMOD, GameWorks, etc.] be supported in Godot?"
msgstr ""

#: ../../docs/about/faq.rst:179
msgid ""
"The aim of Godot is to create a free and open source MIT-licensed engine "
"that is modular and extendable. There are no plans for the core engine "
"development community to support any third-party, closed-source/proprietary "
"SDKs, as integrating with these would go against Godot's ethos."
msgstr ""

#: ../../docs/about/faq.rst:184
msgid ""
"That said, because Godot is open source and modular, nothing prevents you or "
"anyone else interested in adding those libraries as a module and shipping "
"your game with them, as either open- or closed-source."
msgstr ""

#: ../../docs/about/faq.rst:188
msgid ""
"To see how support for your SDK of choice could still be provided, look at "
"the Plugins question below."
msgstr ""

#: ../../docs/about/faq.rst:191
msgid ""
"If you know of a third-party SDK that is not supported by Godot but that "
"offers free and open source integration, consider starting the integration "
"work yourself. Godot is not owned by one person; it belongs to the "
"community, and it grows along with ambitious community contributors like you."
msgstr ""

#: ../../docs/about/faq.rst:197
msgid "How can I extend Godot?"
msgstr ""

#: ../../docs/about/faq.rst:199
msgid ""
"For extending Godot, like creating Godot Editor plugins or adding support "
"for additional languages, take a look at :ref:`EditorPlugins "
"<doc_making_plugins>` and tool scripts."
msgstr ""

#: ../../docs/about/faq.rst:203
msgid ""
"Also, see the official blog post on GDExtension, a way to develop native "
"extensions for Godot:"
msgstr ""

#: ../../docs/about/faq.rst:205
msgid ""
"`Introducing GDNative's successor, GDExtension <https://godotengine.org/"
"article/introducing-gd-extensions>`_"
msgstr ""

#: ../../docs/about/faq.rst:207
msgid ""
"You can also take a look at the GDScript implementation, the Godot modules, "
"as well as the `Jolt physics engine integration <https://github.com/godot-"
"jolt/godot-jolt>`__ for Godot. This would be a good starting point to see "
"how another third-party library integrates with Godot."
msgstr ""

#: ../../docs/about/faq.rst:213
msgid ""
"How do I install the Godot editor on my system (for desktop integration)?"
msgstr ""

#: ../../docs/about/faq.rst:215
msgid ""
"Since you don't need to actually install Godot on your system to run it, "
"this means desktop integration is not performed automatically. There are two "
"ways to overcome this. You can install Godot from `Steam <https://store."
"steampowered.com/app/404790/Godot_Engine/>`__ (all platforms), `Scoop "
"<https://scoop.sh/>`__ (Windows), `Homebrew <https://brew.sh/>`__ (macOS) or "
"`Flathub <https://flathub.org/apps/details/org.godotengine.Godot>`__ "
"(Linux). This will automatically perform the required steps for desktop "
"integration."
msgstr ""

#: ../../docs/about/faq.rst:223
msgid ""
"Alternatively, you can manually perform the steps that an installer would do "
"for you:"
msgstr ""

#: ../../docs/about/faq.rst:228
msgid ""
"Move the Godot executable to a stable location (i.e. outside of your "
"Downloads folder), so you don't accidentally move it and break the shortcut "
"in the future."
msgstr ""

#: ../../docs/about/faq.rst:230
msgid "Right-click the Godot executable and choose **Create Shortcut**."
msgstr ""

#: ../../docs/about/faq.rst:231
msgid ""
"Move the created shortcut to ``%APPDATA%\\Microsoft\\Windows\\Start "
"Menu\\Programs``. This is the user-wide location for shortcuts that will "
"appear in the Start menu. You can also pin Godot in the task bar by right-"
"clicking the executable and choosing **Pin to Task Bar**."
msgstr ""

#: ../../docs/about/faq.rst:239
msgid ""
"Drag the extracted Godot application to ``/Applications/Godot.app``, then "
"drag it to the Dock if desired. Spotlight will be able to find Godot as long "
"as it's in ``/Applications`` or ``~/Applications``."
msgstr ""

#: ../../docs/about/faq.rst:244
#: ../../docs/tutorials/inputs/controllers_gamepads_joysticks.rst:347
#: ../../docs/tutorials/rendering/jitter_stutter.rst:114
#: ../../docs/tutorials/ui/gui_using_fonts.rst:764
msgid "Linux"
msgstr ""

#: ../../docs/about/faq.rst:246
msgid ""
"Move the Godot binary to a stable location (i.e. outside of your Downloads "
"folder), so you don't accidentally move it and break the shortcut in the "
"future."
msgstr ""

#: ../../docs/about/faq.rst:248
msgid ""
"Rename and move the Godot binary to a location present in your ``PATH`` "
"environment variable. This is typically ``/usr/local/bin/godot`` or ``/usr/"
"bin/godot``. Doing this requires administrator privileges, but this also "
"allows you to :ref:`run the Godot editor from a terminal "
"<doc_command_line_tutorial>` by entering ``godot``."
msgstr ""

#: ../../docs/about/faq.rst:254
msgid ""
"If you cannot move the Godot editor binary to a protected location, you can "
"keep the binary somewhere in your home directory, and modify the ``Path=`` "
"line in the ``.desktop`` file linked below to contain the full *absolute* "
"path to the Godot binary."
msgstr ""

#: ../../docs/about/faq.rst:259
msgid ""
"Save `this .desktop file <https://raw.githubusercontent.com/godotengine/"
"godot/master/misc/dist/linux/org.godotengine.Godot.desktop>`__ to ``$HOME/."
"local/share/applications/``. If you have administrator privileges, you can "
"also save the ``.desktop`` file to ``/usr/local/share/applications`` to make "
"the shortcut available for all users."
msgstr ""

#: ../../docs/about/faq.rst:265
msgid "Is the Godot editor a portable application?"
msgstr ""

#: ../../docs/about/faq.rst:267
msgid ""
"In its default configuration, Godot is *semi-portable*. Its executable can "
"run from any location (including non-writable locations) and never requires "
"administrator privileges."
msgstr ""

#: ../../docs/about/faq.rst:271
msgid ""
"However, configuration files will be written to the user-wide configuration "
"or data directory. This is usually a good approach, but this means "
"configuration files will not carry across machines if you copy the folder "
"containing the Godot executable. See :ref:`doc_data_paths` for more "
"information."
msgstr ""

#: ../../docs/about/faq.rst:276
msgid ""
"If *true* portable operation is desired (e.g. for use on an USB stick), "
"follow the steps in :ref:`doc_data_paths_self_contained_mode`."
msgstr ""

#: ../../docs/about/faq.rst:280
msgid "Why does Godot use Vulkan or OpenGL instead of Direct3D?"
msgstr ""

#: ../../docs/about/faq.rst:282
msgid ""
"Godot aims for cross-platform compatibility and open standards first and "
"foremost. OpenGL and Vulkan are the technologies that are both open and "
"available on (nearly) all platforms. Thanks to this design decision, a "
"project developed with Godot on Windows will run out of the box on Linux, "
"macOS, and more."
msgstr ""

#: ../../docs/about/faq.rst:288
msgid ""
"Since Godot only has a few people working on its renderer, we would prefer "
"having fewer rendering backends to maintain. On top of that, using a single "
"API on all platforms allows for greater consistency with fewer platform-"
"specific issues."
msgstr ""

#: ../../docs/about/faq.rst:293
msgid ""
"In the long term, we may develop a Direct3D 12 renderer for Godot (mainly "
"for Xbox), but Vulkan and OpenGL will remain the default rendering backends "
"on all platforms, including Windows."
msgstr ""

#: ../../docs/about/faq.rst:298
msgid "Why does Godot aim to keep its core feature set small?"
msgstr ""

#: ../../docs/about/faq.rst:300
msgid ""
"Godot intentionally does not include features that can be implemented by add-"
"ons unless they are used very often. One example of something not used often "
"is advanced artificial intelligence functionality."
msgstr ""

#: ../../docs/about/faq.rst:304
#, fuzzy
msgid "There are several reasons for this:"
msgstr "Ne postoje ograničenja prilikom korištenja Godot-a"

#: ../../docs/about/faq.rst:306
msgid ""
"**Code maintenance and surface for bugs.** Every time we accept new code in "
"the Godot repository, existing contributors often take the responsibility of "
"maintaining it. Some contributors don't always stick around after getting "
"their code merged, which can make it difficult for us to maintain the code "
"in question. This can lead to poorly maintained features with bugs that are "
"never fixed. On top of that, the \"API surface\" that needs to be tested and "
"checked for regressions keeps increasing over time."
msgstr ""

#: ../../docs/about/faq.rst:314
msgid ""
"**Ease of contribution.** By keeping the codebase small and tidy, it can "
"remain fast and easy to compile from source. This makes it easier for new "
"contributors to get started with Godot, without requiring them to purchase "
"high-end hardware."
msgstr ""

#: ../../docs/about/faq.rst:319
msgid ""
"**Keeping the binary size small for the editor.** Not everyone has a fast "
"Internet connection. Ensuring that everyone can download the Godot editor, "
"extract it and run it in less than 5 minutes makes Godot more accessible to "
"developers in all countries."
msgstr ""

#: ../../docs/about/faq.rst:324
msgid ""
"**Keeping the binary size small for export templates.** This directly "
"impacts the size of projects exported with Godot. On mobile and web "
"platforms, keeping file sizes low is important to ensure fast installation "
"and loading on underpowered devices. Again, there are many countries where "
"high-speed Internet is not readily available. To add to this, strict data "
"usage caps are often in effect in those countries."
msgstr ""

#: ../../docs/about/faq.rst:331
msgid ""
"For all the reasons above, we have to be selective of what we can accept as "
"core functionality in Godot. This is why we are aiming to move some core "
"functionality to officially supported add-ons in future versions of Godot. "
"In terms of binary size, this also has the advantage of making you pay only "
"for what you actually use in your project. (In the meantime, you can :ref:"
"`compile custom export templates with unused features disabled "
"<doc_optimizing_for_size>` to optimize the distribution size of your "
"project.)"
msgstr ""

#: ../../docs/about/faq.rst:340
msgid ""
"How should assets be created to handle multiple resolutions and aspect "
"ratios?"
msgstr ""

#: ../../docs/about/faq.rst:342
msgid ""
"This question pops up often and it's probably thanks to the misunderstanding "
"created by Apple when they originally doubled the resolution of their "
"devices. It made people think that having the same assets in different "
"resolutions was a good idea, so many continued towards that path. That "
"originally worked to a point and only for Apple devices, but then several "
"Android and Apple devices with different resolutions and aspect ratios were "
"created, with a very wide range of sizes and DPIs."
msgstr ""

#: ../../docs/about/faq.rst:350
msgid ""
"The most common and proper way to achieve this is to, instead, use a single "
"base resolution for the game and only handle different screen aspect ratios. "
"This is mostly needed for 2D, as in 3D, it's just a matter of camera "
"vertical or horizontal FOV."
msgstr ""

#: ../../docs/about/faq.rst:355
msgid ""
"Choose a single base resolution for your game. Even if there are devices "
"that go up to 1440p and devices that go down to 400p, regular hardware "
"scaling in your device will take care of this at little or no performance "
"cost. The most common choices are either near 1080p (1920x1080) or 720p "
"(1280x720). Keep in mind the higher the resolution, the larger your assets, "
"the more memory they will take and the longer the time it will take for "
"loading."
msgstr ""

#: ../../docs/about/faq.rst:363
msgid ""
"Use the stretch options in Godot; canvas items stretching while keeping "
"aspect ratios works best. Check the :ref:`doc_multiple_resolutions` tutorial "
"on how to achieve this."
msgstr ""

#: ../../docs/about/faq.rst:367
msgid ""
"Determine a minimum resolution and then decide if you want your game to "
"stretch vertically or horizontally for different aspect ratios, or if there "
"is one aspect ratio and you want black bars to appear instead. This is also "
"explained in :ref:`doc_multiple_resolutions`."
msgstr ""

#: ../../docs/about/faq.rst:372
msgid ""
"For user interfaces, use the :ref:`anchoring <doc_size_and_anchors>` to "
"determine where controls should stay and move. If UIs are more complex, "
"consider learning about Containers."
msgstr ""

#: ../../docs/about/faq.rst:376
msgid "And that's it! Your game should work in multiple resolutions."
msgstr ""

#: ../../docs/about/faq.rst:379
msgid "When is the next release of Godot out?"
msgstr ""

#: ../../docs/about/faq.rst:381
msgid ""
"When it's ready! See :ref:`doc_release_policy_when_is_next_release_out` for "
"more information."
msgstr ""

#: ../../docs/about/faq.rst:385
#, fuzzy
msgid "Which Godot version should I use for a new project?"
msgstr "Kreiranje Sadržaja"

#: ../../docs/about/faq.rst:387
msgid ""
"We recommend using Godot 4.x for new projects, but depending on the feature "
"set you need, it may be better to use 3.x instead. See :ref:"
"`doc_release_policy_which_version_should_i_use` for more information."
msgstr ""

#: ../../docs/about/faq.rst:392
msgid "Should I upgrade my project to use new Godot versions?"
msgstr ""

#: ../../docs/about/faq.rst:394
msgid ""
"Some new versions are safer to upgrade to than others. In general, whether "
"you should upgrade depends on your project's circumstances. See :ref:"
"`doc_release_policy_should_i_upgrade_my_project` for more information."
msgstr ""

#: ../../docs/about/faq.rst:399
msgid "I would like to contribute! How can I get started?"
msgstr ""

#: ../../docs/about/faq.rst:401
msgid ""
"Awesome! As an open source project, Godot thrives off of the innovation and "
"the ambition of developers like you."
msgstr ""

#: ../../docs/about/faq.rst:404
msgid ""
"The best way to start contributing to Godot is by using it and reporting any "
"`issues <https://github.com/godotengine/godot/issues>`_ that you might "
"experience. A good bug report with clear reproduction steps helps your "
"fellow contributors fix bugs quickly and efficiently. You can also report "
"issues you find in the `online documentation <https://github.com/godotengine/"
"godot-docs/issues>`_."
msgstr ""

#: ../../docs/about/faq.rst:410
msgid ""
"If you feel ready to submit your first PR, pick any issue that resonates "
"with you from one of the links above and try your hand at fixing it. You "
"will need to learn how to compile the engine from sources, or how to build "
"the documentation. You also need to get familiar with Git, a version control "
"system that Godot developers use."
msgstr ""

#: ../../docs/about/faq.rst:415
msgid ""
"We explain how to work with the engine source, how to edit the "
"documentation, and what other ways to contribute are there in our :ref:"
"`documentation for contributors <doc_ways_to_contribute>`."
msgstr ""

#: ../../docs/about/faq.rst:419
msgid "I have a great idea for Godot. How can I share it?"
msgstr ""

#: ../../docs/about/faq.rst:421
msgid ""
"We are always looking for suggestions about how to improve the engine. User "
"feedback is the main driving force behind our decision-making process, and "
"limitations that you might face while working on your project are a great "
"data point for us when considering engine enhancements."
msgstr ""

#: ../../docs/about/faq.rst:426
msgid ""
"If you experience a usability problem or are missing a feature in the "
"current version of Godot, start by discussing it with our `community "
"<https://godotengine.org/community/>`_. There may be other, perhaps better, "
"ways to achieve the desired result that community members could suggest. And "
"you can learn if other users experience the same issue, and figure out a "
"good solution together."
msgstr ""

#: ../../docs/about/faq.rst:432
msgid ""
"If you come up with a well-defined idea for the engine, feel free to open a "
"`proposal issue <https://github.com/godotengine/godot-proposals/issues>`_. "
"Try to be specific and concrete while describing your problem and your "
"proposed solution — only actionable proposals can be considered. It is not "
"required, but if you want to implement it yourself, that's always "
"appreciated!"
msgstr ""

#: ../../docs/about/faq.rst:438
msgid ""
"If you only have a general idea without specific details, you can open a "
"`proposal discussion <https://github.com/godotengine/godot-proposals/"
"discussions>`_. These can be anything you want, and allow for a free-form "
"discussion in search of a solution. Once you find one, a proposal issue can "
"be opened."
msgstr ""

#: ../../docs/about/faq.rst:443
msgid ""
"Please, read the `readme <https://github.com/godotengine/godot-proposals/"
"blob/master/README.md>`_ document before creating a proposal to learn more "
"about the process."
msgstr ""

#: ../../docs/about/faq.rst:449
msgid "Is it possible to use Godot to create non-game applications?"
msgstr ""

#: ../../docs/about/faq.rst:451
msgid ""
"Yes! Godot features an extensive built-in UI system, and its small "
"distribution size can make it a suitable alternative to frameworks like "
"Electron or Qt."
msgstr ""

#: ../../docs/about/faq.rst:454
msgid ""
"When creating a non-game application, make sure to enable :ref:`low-"
"processor mode <class_ProjectSettings_property_application/run/"
"low_processor_mode>` in the Project Settings to decrease CPU and GPU usage."
msgstr ""

#: ../../docs/about/faq.rst:458
msgid ""
"Check out `Material Maker <https://github.com/RodZill4/material-maker>`__ "
"and `Pixelorama <https://github.com/Orama-Interactive/Pixelorama>`__ for "
"examples of open source applications made with Godot."
msgstr ""

#: ../../docs/about/faq.rst:465
msgid "Is it possible to use Godot as a library?"
msgstr ""

#: ../../docs/about/faq.rst:467
msgid ""
"Godot is meant to be used with its editor. We recommend you give it a try, "
"as it will most likely save you time in the long term. There are no plans to "
"make Godot usable as a library, as it would make the rest of the engine more "
"convoluted and difficult to use for casual users."
msgstr ""

#: ../../docs/about/faq.rst:472
msgid ""
"If you want to use a rendering library, look into using an established "
"rendering engine instead. Keep in mind rendering engines usually have "
"smaller communities compared to Godot. This will make it more difficult to "
"find answers to your questions."
msgstr ""

#: ../../docs/about/faq.rst:478
msgid "What user interface toolkit does Godot use?"
msgstr ""

#: ../../docs/about/faq.rst:480
msgid ""
"Godot does not use a standard :abbr:`GUI (Graphical User Interface)` toolkit "
"like GTK, Qt or wxWidgets. Instead, Godot uses its own user interface "
"toolkit, rendered using OpenGL ES or Vulkan. This toolkit is exposed in the "
"form of Control nodes, which are used to render the editor (which is written "
"in C++). These Control nodes can also be used in projects from any scripting "
"language supported by Godot."
msgstr ""

#: ../../docs/about/faq.rst:487
msgid ""
"This custom toolkit makes it possible to benefit from hardware acceleration "
"and have a consistent appearance across all platforms. On top of that, it "
"doesn't have to deal with the LGPL licensing caveats that come with GTK or "
"Qt. Lastly, this means Godot is \"eating its own dog food\" since the editor "
"itself is one of the most complex users of Godot's UI system."
msgstr ""

#: ../../docs/about/faq.rst:493
msgid ""
"This custom UI toolkit :ref:`can't be used as a library "
"<doc_faq_use_godot_as_library>`, but you can still :ref:`use Godot to create "
"non-game applications by using the editor <doc_faq_non_game_applications>`."
msgstr ""

#: ../../docs/about/faq.rst:500
msgid "Why does Godot use the SCons build system?"
msgstr ""

#: ../../docs/about/faq.rst:502
msgid ""
"Godot uses the `SCons <https://www.scons.org/>`__ build system. There are no "
"plans to switch to a different build system in the near future. There are "
"many reasons why we have chosen SCons over other alternatives. For example:"
msgstr ""

#: ../../docs/about/faq.rst:506
msgid ""
"Godot can be compiled for a dozen different platforms: all PC platforms, all "
"mobile platforms, many consoles, and WebAssembly."
msgstr ""

#: ../../docs/about/faq.rst:508
msgid ""
"Developers often need to compile for several of the platforms **at the same "
"time**, or even different targets of the same platform. They can't afford "
"reconfiguring and rebuilding the project each time. SCons can do this with "
"no sweat, without breaking the builds."
msgstr ""

#: ../../docs/about/faq.rst:512
msgid ""
"SCons will *never* break a build no matter how many changes, configurations, "
"additions, removals etc."
msgstr ""

#: ../../docs/about/faq.rst:514
msgid ""
"Godot's build process is not simple. Several files are generated by code "
"(binders), others are parsed (shaders), and others need to offer "
"customization (:ref:`modules <doc_custom_modules_in_cpp>`). This requires "
"complex logic which is easier to write in an actual programming language "
"(like Python) rather than using a mostly macro-based language only meant for "
"building."
msgstr ""

#: ../../docs/about/faq.rst:519
msgid ""
"Godot's build process makes heavy use of cross-compiling tools. Each "
"platform has a specific detection process, and all these must be handled as "
"specific cases with special code written for each."
msgstr ""

#: ../../docs/about/faq.rst:523
msgid ""
"Please try to keep an open mind and get at least a little familiar with "
"SCons if you are planning to build Godot yourself."
msgstr ""

#: ../../docs/about/faq.rst:529
msgid "Why does Godot not use STL (Standard Template Library)?"
msgstr ""

#: ../../docs/about/faq.rst:531
msgid ""
"Like many other libraries (Qt as an example), Godot does not make use of STL "
"(with a few exceptions such as threading primitives). We believe STL is a "
"great general-purpose library, but we had special requirements for Godot."
msgstr ""

#: ../../docs/about/faq.rst:535
msgid ""
"STL templates create very large symbols, which results in huge debug "
"binaries. We use few templates with very short names instead."
msgstr ""

#: ../../docs/about/faq.rst:537
msgid ""
"Most of our containers cater to special needs, like Vector, which uses copy "
"on write and we use to pass data around, or the RID system, which requires "
"O(1) access time for performance. Likewise, our hash map implementations are "
"designed to integrate seamlessly with internal engine types."
msgstr ""

#: ../../docs/about/faq.rst:541
msgid ""
"Our containers have memory tracking built-in, which helps better track "
"memory usage."
msgstr ""

#: ../../docs/about/faq.rst:542
msgid ""
"For large arrays, we use pooled memory, which can be mapped to either a "
"preallocated buffer or virtual memory."
msgstr ""

#: ../../docs/about/faq.rst:544
msgid ""
"We use our custom String type, as the one provided by STL is too basic and "
"lacks proper internationalization support."
msgstr ""

#: ../../docs/about/faq.rst:548
msgid "Why does Godot not use exceptions?"
msgstr ""

#: ../../docs/about/faq.rst:550
msgid ""
"We believe games should not crash, no matter what. If an unexpected "
"situation happens, Godot will print an error (which can be traced even to "
"script), but then it will try to recover as gracefully as possible and keep "
"going."
msgstr ""

#: ../../docs/about/faq.rst:555
msgid ""
"Additionally, exceptions significantly increase the binary size for the "
"executable and result in increased compile times."
msgstr ""

#: ../../docs/about/faq.rst:559
msgid "Does Godot use an ECS (Entity Component System)?"
msgstr ""

#: ../../docs/about/faq.rst:561
msgid ""
"Godot does **not** use an ECS and relies on inheritance instead. While there "
"is no universally better approach, we found that using an inheritance-based "
"approach resulted in better usability while still being fast enough for most "
"use cases."
msgstr ""

#: ../../docs/about/faq.rst:565
msgid ""
"That said, nothing prevents you from making use of composition in your "
"project by creating child Nodes with individual scripts. These nodes can "
"then be added and removed at run-time to dynamically add and remove "
"behaviors."
msgstr ""

#: ../../docs/about/faq.rst:569
msgid ""
"More information about Godot's design choices can be found in `this article "
"<https://godotengine.org/article/why-isnt-godot-ecs-based-game-engine>`__."
msgstr ""

#: ../../docs/about/faq.rst:573
msgid "Why does Godot not force users to implement DOD (Data-Oriented Design)?"
msgstr ""

#: ../../docs/about/faq.rst:575
msgid ""
"While Godot internally attempts to use cache coherency as much as possible, "
"we believe users don't need to be forced to use DOD practices."
msgstr ""

#: ../../docs/about/faq.rst:578
msgid ""
"DOD is mostly a cache coherency optimization that can only provide "
"significant performance improvements when dealing with dozens of thousands "
"of objects which are processed every frame with little modification. That "
"is, if you are moving a few hundred sprites or enemies per frame, DOD won't "
"result in a meaningful improvement in performance. In such a case, you "
"should consider a different approach to optimization."
msgstr ""

#: ../../docs/about/faq.rst:585
msgid ""
"The vast majority of games do not need this and Godot provides handy helpers "
"to do the job for most cases when you do."
msgstr ""

#: ../../docs/about/faq.rst:588
msgid ""
"If a game needs to process such a large amount of objects, our "
"recommendation is to use C++ and GDExtensions for performance-heavy tasks "
"and GDScript (or C#) for the rest of the game."
msgstr ""

#: ../../docs/about/faq.rst:593
msgid "How can I support Godot development or contribute?"
msgstr ""

#: ../../docs/about/faq.rst:595
msgid "See :ref:`doc_ways_to_contribute`."
msgstr ""

#: ../../docs/about/faq.rst:598
msgid "Who is working on Godot? How can I contact you?"
msgstr ""

#: ../../docs/about/faq.rst:600
msgid ""
"See the corresponding page on the `Godot website <https://godotengine.org/"
"contact>`_."
msgstr ""

#: ../../docs/about/complying_with_licenses.rst:4
#, fuzzy
msgid "Complying with licenses"
msgstr "Kreiranje Sadržaja"

#: ../../docs/about/complying_with_licenses.rst:7
msgid "What are licenses?"
msgstr ""

#: ../../docs/about/complying_with_licenses.rst:9
msgid ""
"Godot is created and distributed under the `MIT License <https://opensource."
"org/licenses/MIT>`_. It doesn't have a sole owner either, as every "
"contributor that submits code to the project does it under this same license "
"and keeps ownership of the contribution."
msgstr ""

#: ../../docs/about/complying_with_licenses.rst:14
msgid ""
"The license is the legal requirement for you (or your company) to use and "
"distribute the software (and derivative projects, including games made with "
"it). Your game or project can have a different license, but it still needs "
"to comply with the original one."
msgstr ""

#: ../../docs/about/complying_with_licenses.rst:21
msgid ""
"This section covers compliance with licenses from a user perspective. If you "
"are interested in licence compliance as a contributor, you can find "
"guidelines :ref:`here "
"<doc_best_practices_for_engine_contributors_license_compliance>`."
msgstr ""

#: ../../docs/about/complying_with_licenses.rst:27
msgid ""
"In your project's credits screen, remember to also list third-party notices "
"for assets you're using, such as textures, models, sounds, music and fonts."
msgstr ""

#: ../../docs/about/complying_with_licenses.rst:30
msgid ""
"Free assets in particular often come with licenses that require attribution. "
"Double-check their license before using those assets in a project."
msgstr ""

#: ../../docs/about/complying_with_licenses.rst:34
#: ../../docs/tutorials/export/exporting_for_macos.rst:17
#: ../../docs/tutorials/export/exporting_for_ios.rst:22
#: ../../docs/contributing/development/compiling/compiling_for_windows.rst:14
#: ../../docs/contributing/development/compiling/compiling_for_linuxbsd.rst:14
#: ../../docs/contributing/development/compiling/compiling_for_macos.rst:14
#: ../../docs/contributing/development/compiling/compiling_for_android.rst:25
#: ../../docs/contributing/development/compiling/compiling_for_ios.rst:14
#: ../../docs/contributing/development/compiling/cross-compiling_for_ios_on_linux.rst:25
#: ../../docs/contributing/development/compiling/compiling_for_web.rst:14
#: ../../docs/contributing/development/compiling/compiling_with_dotnet.rst:9
#: ../../docs/community/asset_library/submitting_to_assetlib.rst:24
msgid "Requirements"
msgstr ""

#: ../../docs/about/complying_with_licenses.rst:36
msgid ""
"In the case of the MIT license, the only requirement is to include the "
"license text somewhere in your game or derivative project."
msgstr ""

#: ../../docs/about/complying_with_licenses.rst:39
msgid "This text reads as follows:"
msgstr ""

#: ../../docs/about/complying_with_licenses.rst:41
msgid "This game uses Godot Engine, available under the following license:"
msgstr ""

#: ../../docs/about/complying_with_licenses.rst:43
msgid ""
"Copyright (c) 2014-present Godot Engine contributors. Copyright (c) "
"2007-2014 Juan Linietsky, Ariel Manzur."
msgstr ""

#: ../../docs/about/complying_with_licenses.rst:46
#: ../../docs/about/complying_with_licenses.rst:163
msgid ""
"Permission is hereby granted, free of charge, to any person obtaining a copy "
"of this software and associated documentation files (the \"Software\"), to "
"deal in the Software without restriction, including without limitation the "
"rights to use, copy, modify, merge, publish, distribute, sublicense, and/or "
"sell copies of the Software, and to permit persons to whom the Software is "
"furnished to do so, subject to the following conditions:"
msgstr ""

#: ../../docs/about/complying_with_licenses.rst:48
#: ../../docs/about/complying_with_licenses.rst:165
msgid ""
"The above copyright notice and this permission notice shall be included in "
"all copies or substantial portions of the Software."
msgstr ""

#: ../../docs/about/complying_with_licenses.rst:50
#: ../../docs/about/complying_with_licenses.rst:167
msgid ""
"THE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR "
"IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, "
"FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE "
"AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER "
"LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING "
"FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS "
"IN THE SOFTWARE."
msgstr ""

#: ../../docs/about/complying_with_licenses.rst:54
msgid ""
"Your games do not need to be under the same license. You are free to release "
"your Godot projects under any license and to create commercial games with "
"the engine."
msgstr ""

#: ../../docs/about/complying_with_licenses.rst:59
msgid "Inclusion"
msgstr ""

#: ../../docs/about/complying_with_licenses.rst:61
msgid ""
"The license does not specify how it has to be included, so anything is valid "
"as long as it can be displayed under some condition. These are the most "
"common approaches (only need to implement one of them, not all)."
msgstr ""

#: ../../docs/about/complying_with_licenses.rst:67
msgid ""
"Godot provides several methods to get license information in the Engine "
"singleton. This allows you to source the license information directly from "
"the engine binary, which prevents the information from becoming outdated if "
"you update engine versions."
msgstr ""

#: ../../docs/about/complying_with_licenses.rst:72
msgid "For the engine itself:"
msgstr ""

#: ../../docs/about/complying_with_licenses.rst:74
msgid ":ref:`Engine.get_license_text<class_Engine_method_get_license_text>`"
msgstr ""

#: ../../docs/about/complying_with_licenses.rst:76
msgid "For third-party components used by the engine:"
msgstr ""

#: ../../docs/about/complying_with_licenses.rst:78
msgid ":ref:`Engine.get_license_info<class_Engine_method_get_license_info>`"
msgstr ""

#: ../../docs/about/complying_with_licenses.rst:79
msgid ""
":ref:`Engine.get_copyright_info<class_Engine_method_get_copyright_info>`"
msgstr ""

#: ../../docs/about/complying_with_licenses.rst:81
msgid ""
"For miscellaneous engine contributor information. You don't have to include "
"these ones in your project, but they're listed here for reference:"
msgstr ""

#: ../../docs/about/complying_with_licenses.rst:84
msgid ":ref:`Engine.get_author_info<class_Engine_method_get_author_info>`"
msgstr ""

#: ../../docs/about/complying_with_licenses.rst:85
msgid ":ref:`Engine.get_donor_info<class_Engine_method_get_donor_info>`"
msgstr ""

#: ../../docs/about/complying_with_licenses.rst:88
msgid "Credits screen"
msgstr ""

#: ../../docs/about/complying_with_licenses.rst:90
msgid ""
"Include the above license text somewhere in the credits screen. It can be at "
"the bottom after showing the rest of the credits. Most large studios use "
"this approach with open source licenses."
msgstr ""

#: ../../docs/about/complying_with_licenses.rst:95
msgid "Licenses screen"
msgstr ""

#: ../../docs/about/complying_with_licenses.rst:97
msgid ""
"Some games have a special menu (often in the settings) to display licenses. "
"This menu is typically accessed with a button called **Third-party "
"Licenses** or **Open Source Licenses**."
msgstr ""

#: ../../docs/about/complying_with_licenses.rst:102
msgid "Output log"
msgstr ""

#: ../../docs/about/complying_with_licenses.rst:104
msgid ""
"Printing the licensing text using the :ref:`print() "
"<class_@GlobalScope_method_print>` function may be enough on platforms where "
"a global output log is readable. This is the case on desktop platforms, "
"Android and HTML5 (but not iOS)."
msgstr ""

#: ../../docs/about/complying_with_licenses.rst:109
msgid "Accompanying file"
msgstr ""

#: ../../docs/about/complying_with_licenses.rst:111
msgid ""
"If the game is distributed on desktop platforms, a file containing the "
"license can be added to the software that is installed to the user PC."
msgstr ""

#: ../../docs/about/complying_with_licenses.rst:115
msgid "Printed manual"
msgstr ""

#: ../../docs/about/complying_with_licenses.rst:117
msgid ""
"If the game includes printed manuals, license text can be included there."
msgstr ""

#: ../../docs/about/complying_with_licenses.rst:120
#, fuzzy
msgid "Link to the license"
msgstr "Kreiranje Sadržaja"

#: ../../docs/about/complying_with_licenses.rst:122
msgid ""
"The Godot Engine developers consider that a link to ``godotengine.org/"
"license`` in your game documentation or credits would be an acceptable way "
"to satisfy the license terms."
msgstr ""

#: ../../docs/about/complying_with_licenses.rst:127
msgid "Third-party licenses"
msgstr ""

#: ../../docs/about/complying_with_licenses.rst:129
msgid ""
"Godot itself contains software written by `third parties <https://github.com/"
"godotengine/godot/blob/master/COPYRIGHT.txt>`_. Most of it does not require "
"license inclusion, but some do. Make sure to do it if these are compiled in "
"your Godot export template. If you're using the official export templates, "
"all libraries are enabled. This means you need to provide attribution for "
"all the libraries listed below."
msgstr ""

#: ../../docs/about/complying_with_licenses.rst:136
msgid "Here's a list of libraries requiring attribution:"
msgstr ""

#: ../../docs/about/complying_with_licenses.rst:139
msgid "FreeType"
msgstr ""

#: ../../docs/about/complying_with_licenses.rst:141
msgid ""
"Godot uses `FreeType <https://www.freetype.org/>`_ to render fonts. Its "
"license requires attribution, so the following text must be included "
"together with the Godot license:"
msgstr ""

#: ../../docs/about/complying_with_licenses.rst:145
msgid ""
"Portions of this software are copyright © <year> The FreeType Project (www."
"freetype.org).  All rights reserved."
msgstr ""

#: ../../docs/about/complying_with_licenses.rst:149
msgid ""
"<year> should correspond to the value from the FreeType version used in your "
"build. This information can be found in the editor by opening the **Help > "
"About** dialog and going to the **Third-party Licenses** tab."
msgstr ""

#: ../../docs/about/complying_with_licenses.rst:155
msgid "ENet"
msgstr ""

#: ../../docs/about/complying_with_licenses.rst:157
msgid ""
"Godot includes the `ENet <http://enet.bespin.org/>`_ library to handle high-"
"level multiplayer. ENet has similar licensing terms as Godot:"
msgstr ""

#: ../../docs/about/complying_with_licenses.rst:161
msgid "Copyright (c) 2002-2020 Lee Salzman"
msgstr ""

#: ../../docs/about/complying_with_licenses.rst:170
msgid "mbed TLS"
msgstr ""

#: ../../docs/about/complying_with_licenses.rst:172
msgid ""
"If the project is exported with Godot 3.1 or later, it includes `mbed TLS "
"<https://tls.mbed.org>`_. The Apache license needs to be complied to by "
"including the following text:"
msgstr ""

#: ../../docs/about/complying_with_licenses.rst:175
msgid "Copyright The Mbed TLS Contributors"
msgstr ""

#: ../../docs/about/complying_with_licenses.rst:177
msgid ""
"Licensed under the Apache License, Version 2.0 (the \"License\"); you may "
"not use this file except in compliance with the License. You may obtain a "
"copy of the License at"
msgstr ""

#: ../../docs/about/complying_with_licenses.rst:181
msgid "http://www.apache.org/licenses/LICENSE-2.0"
msgstr ""

#: ../../docs/about/complying_with_licenses.rst:183
msgid ""
"Unless required by applicable law or agreed to in writing, software "
"distributed under the License is distributed on an \"AS IS\" BASIS, WITHOUT "
"WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the "
"License for the specific language governing permissions and limitations "
"under the License."
msgstr ""

#: ../../docs/about/complying_with_licenses.rst:191
msgid ""
"If you exported your project using a :ref:`custom build with specific "
"modules disabled <doc_optimizing_for_size>`, you don't need to list the "
"disabled modules' licenses in your exported project."
msgstr ""

#: ../../docs/about/release_policy.rst:4
msgid "Godot release policy"
msgstr ""

#: ../../docs/about/release_policy.rst:6
msgid ""
"Godot's release policy is in constant evolution. The description below "
"provides a general idea of what to expect, but what will actually happen "
"depends on the choices of core contributors and the needs of the community "
"at a given time."
msgstr ""

#: ../../docs/about/release_policy.rst:12
msgid "Godot versioning"
msgstr ""

#: ../../docs/about/release_policy.rst:14
msgid ""
"Godot loosely follows `Semantic Versioning <https://semver.org/>`__ with a "
"``major.minor.patch`` versioning system, albeit with an interpretation of "
"each term adapted to the complexity of a game engine:"
msgstr ""

#: ../../docs/about/release_policy.rst:18
msgid ""
"The ``major`` version is incremented when major compatibility breakages "
"happen which imply significant porting work to move projects from one major "
"version to another."
msgstr ""

#: ../../docs/about/release_policy.rst:22
msgid ""
"For example, porting Godot projects from Godot 3.x to Godot 4.x requires "
"running the project through a conversion tool, and then performing a number "
"of further adjustments manually for what the tool could not do automatically."
msgstr ""

#: ../../docs/about/release_policy.rst:26
msgid ""
"The ``minor`` version is incremented for feature releases that do not break "
"compatibility in a major way. Minor compatibility breakage in very specific "
"areas *may* happen in minor versions, but the vast majority of projects "
"should not be affected or require significant porting work."
msgstr ""

#: ../../docs/about/release_policy.rst:31
msgid ""
"This is because Godot, as a game engine, covers many areas like rendering, "
"physics, and scripting. Fixing bugs or implementing new features in one area "
"might sometimes require changing a feature's behavior or modifying a class's "
"interface, even if the rest of the engine API remains backwards compatible."
msgstr ""

#: ../../docs/about/release_policy.rst:38
msgid ""
"Upgrading to a new minor version is recommended for all users, but some "
"testing is necessary to ensure that your project still behaves as expected."
msgstr ""

#: ../../docs/about/release_policy.rst:42
msgid ""
"The ``patch`` version is incremented for maintenance releases which focus on "
"fixing bugs and security issues, implementing new requirements for platform "
"support, and backporting safe usability enhancements. Patch releases are "
"backwards compatible."
msgstr ""

#: ../../docs/about/release_policy.rst:47
msgid ""
"Patch versions may include minor new features which do not impact the "
"existing API, and thus have no risk of impacting existing projects."
msgstr ""

#: ../../docs/about/release_policy.rst:52
msgid ""
"Updating to new patch versions is therefore considered safe and strongly "
"recommended to all users of a given stable branch."
msgstr ""

#: ../../docs/about/release_policy.rst:55
msgid ""
"We call ``major.minor`` combinations *stable branches*. Each stable branch "
"starts with a ``major.minor`` release (without the ``0`` for ``patch``) and "
"is further developed for maintenance releases in a Git branch of the same "
"name (for example patch updates for the 4.0 stable branch are developed in "
"the ``4.0`` Git branch)."
msgstr ""

#: ../../docs/about/release_policy.rst:62
msgid "Release support timeline"
msgstr ""

#: ../../docs/about/release_policy.rst:64
msgid ""
"Stable branches are supported *at least* until the next stable branch is "
"released and has received its first patch update. In practice, we support "
"stable branches on a *best effort* basis for as long as they have active "
"users who need maintenance updates."
msgstr ""

#: ../../docs/about/release_policy.rst:69
msgid ""
"Whenever a new major version is released, we make the previous stable branch "
"a long-term supported release, and do our best to provide fixes for issues "
"encountered by users of that branch who cannot port complex projects to the "
"new major version. This was the case for the 2.1 branch, and is the case for "
"the 3.6 branch."
msgstr ""

#: ../../docs/about/release_policy.rst:75
msgid ""
"In a given minor release series, only the latest patch release receives "
"support. If you experience an issue using an older patch release, please "
"upgrade to the latest patch release of that series and test again before "
"reporting an issue on GitHub."
msgstr ""

#: ../../docs/about/release_policy.rst:81
msgid "**Version**"
msgstr ""

#: ../../docs/about/release_policy.rst:81
msgid "**Release date**"
msgstr ""

#: ../../docs/about/release_policy.rst:81
msgid "**Support level**"
msgstr ""

#: ../../docs/about/release_policy.rst:83
msgid "Godot 4.3 (`master`)"
msgstr ""

#: ../../docs/about/release_policy.rst:83
msgid "June 2024 (estimate)"
msgstr ""

#: ../../docs/about/release_policy.rst:83
msgid ""
"|unstable| *Development.* Receives new features, usability and performance "
"improvements, as well as bug fixes, while under development."
msgstr ""

#: ../../docs/about/release_policy.rst:122
msgid "unstable"
msgstr ""

#: ../../docs/about/release_policy.rst:86
msgid "Godot 4.2"
msgstr ""

#: ../../docs/about/release_policy.rst:86
msgid "November 2023"
msgstr ""

#: ../../docs/about/release_policy.rst:86
#: ../../docs/about/release_policy.rst:89
#: ../../docs/about/release_policy.rst:97
msgid ""
"|supported| Receives fixes for bugs and security issues, as well as patches "
"that enable platform support."
msgstr ""

#: ../../docs/about/release_policy.rst:119
msgid "supported"
msgstr ""

#: ../../docs/about/release_policy.rst:89
msgid "Godot 4.1"
msgstr ""

#: ../../docs/about/release_policy.rst:89
msgid "July 2023"
msgstr ""

#: ../../docs/about/release_policy.rst:92
msgid "Godot 4.0"
msgstr ""

#: ../../docs/about/release_policy.rst:92
msgid "March 2023"
msgstr ""

#: ../../docs/about/release_policy.rst:92
msgid "|eol| No longer supported (last update: 4.0.4)."
msgstr ""

#: ../../docs/about/release_policy.rst:121
msgid "eol"
msgstr ""

#: ../../docs/about/release_policy.rst:94
msgid "Godot 3.6 (`3.x`, LTS)"
msgstr ""

#: ../../docs/about/release_policy.rst:94
msgid "Q1 2024 (estimate)"
msgstr ""

#: ../../docs/about/release_policy.rst:94
msgid ""
"|supported| *Beta.* Receives new features, usability and performance "
"improvements, as well as bug fixes, while under development."
msgstr ""

#: ../../docs/about/release_policy.rst:97
msgid "Godot 3.5"
msgstr ""

#: ../../docs/about/release_policy.rst:97
msgid "August 2022"
msgstr ""

#: ../../docs/about/release_policy.rst:100
msgid "Godot 3.4"
msgstr ""

#: ../../docs/about/release_policy.rst:100
msgid "November 2021"
msgstr ""

#: ../../docs/about/release_policy.rst:100
msgid "|eol| No longer supported (last update: 3.4.5)."
msgstr ""

#: ../../docs/about/release_policy.rst:102
msgid "Godot 3.3"
msgstr ""

#: ../../docs/about/release_policy.rst:102
msgid "April 2021"
msgstr ""

#: ../../docs/about/release_policy.rst:102
msgid "|eol| No longer supported (last update: 3.3.4)."
msgstr ""

#: ../../docs/about/release_policy.rst:104
msgid "Godot 3.2"
msgstr ""

#: ../../docs/about/release_policy.rst:104
msgid "January 2020"
msgstr ""

#: ../../docs/about/release_policy.rst:104
msgid "|eol| No longer supported (last update: 3.2.3)."
msgstr ""

#: ../../docs/about/release_policy.rst:106
msgid "Godot 3.1"
msgstr ""

#: ../../docs/about/release_policy.rst:106
msgid "March 2019"
msgstr ""

#: ../../docs/about/release_policy.rst:106
msgid "|eol| No longer supported (last update: 3.1.2)."
msgstr ""

#: ../../docs/about/release_policy.rst:108
msgid "Godot 3.0"
msgstr ""

#: ../../docs/about/release_policy.rst:108
msgid "January 2018"
msgstr ""

#: ../../docs/about/release_policy.rst:108
msgid "|eol| No longer supported (last update: 3.0.6)."
msgstr ""

#: ../../docs/about/release_policy.rst:110
msgid "Godot 2.1"
msgstr ""

#: ../../docs/about/release_policy.rst:110
msgid "July 2016"
msgstr ""

#: ../../docs/about/release_policy.rst:110
msgid "|eol| No longer supported (last update: 2.1.6)."
msgstr ""

#: ../../docs/about/release_policy.rst:112
msgid "Godot 2.0"
msgstr ""

#: ../../docs/about/release_policy.rst:112
msgid "February 2016"
msgstr ""

#: ../../docs/about/release_policy.rst:112
msgid "|eol| No longer supported (last update: 2.0.4.1)."
msgstr ""

#: ../../docs/about/release_policy.rst:114
msgid "Godot 1.1"
msgstr ""

#: ../../docs/about/release_policy.rst:114
msgid "May 2015"
msgstr ""

#: ../../docs/about/release_policy.rst:114
#: ../../docs/about/release_policy.rst:116
msgid "|eol| No longer supported."
msgstr ""

#: ../../docs/about/release_policy.rst:116
msgid "Godot 1.0"
msgstr ""

#: ../../docs/about/release_policy.rst:116
msgid "December 2014"
msgstr ""

#: ../../docs/about/release_policy.rst:120
msgid "partial"
msgstr ""

#: ../../docs/about/release_policy.rst:124
msgid ""
"**Legend:** |supported| Full support – |partial| Partial support – |eol| No "
"support (end of life) – |unstable| Development version"
msgstr ""

#: ../../docs/about/release_policy.rst:130
msgid ""
"Pre-release Godot versions aren't intended to be used in production and are "
"provided for testing purposes only."
msgstr ""

#: ../../docs/about/release_policy.rst:135
msgid ""
"See :ref:`doc_upgrading_to_godot_4` for instructions on migrating a project "
"from Godot 3.x to 4.x."
msgstr ""

#: ../../docs/about/release_policy.rst:141
msgid "Which version should I use for a new project?"
msgstr ""

#: ../../docs/about/release_policy.rst:143
msgid ""
"We recommend using Godot 4.x for new projects, as the Godot 4.x series will "
"be supported long after 3.x stops receiving updates in the future. One "
"caveat is that a lot of third-party documentation hasn't been updated for "
"Godot 4.x yet. If you have to follow a tutorial designed for Godot 3.x, we "
"recommend keeping :ref:`doc_upgrading_to_godot_4` open in a separate tab to "
"check which methods have been renamed (if you get a script error while "
"trying to use a specific node or method that was renamed in Godot 4.x)."
msgstr ""

#: ../../docs/about/release_policy.rst:151
msgid ""
"If your project requires a feature that is missing in 4.x (such as GLES2/"
"WebGL 1.0), you should use Godot 3.x for a new project instead."
msgstr ""

#: ../../docs/about/release_policy.rst:157
msgid "Should I upgrade my project to use new engine versions?"
msgstr ""

#: ../../docs/about/release_policy.rst:161
msgid ""
"Upgrading software while working on a project is inherently risky, so "
"consider whether it's a good idea for your project before attempting an "
"upgrade. Also, make backups of your project or use version control to "
"prevent losing data in case the upgrade goes wrong."
msgstr ""

#: ../../docs/about/release_policy.rst:166
msgid ""
"That said, we do our best to keep minor and especially patch releases "
"compatible with existing projects."
msgstr ""

#: ../../docs/about/release_policy.rst:169
msgid ""
"The general recommendation is to upgrade your project to follow new *patch* "
"releases, such as upgrading from 4.0.2 to 4.0.3. This ensures you get bug "
"fixes, security updates and platform support updates (which is especially "
"important for mobile platforms). You also get continued support, as only the "
"last patch release receives support on official community platforms."
msgstr ""

#: ../../docs/about/release_policy.rst:175
msgid ""
"For *minor* releases, you should determine whether it's a good idea to "
"upgrade on a case-by-case basis. We've made a lot of effort in making the "
"upgrade process as seamless as possible, but some breaking changes may be "
"present in minor releases, along with a greater risk of regressions. Some "
"fixes included in minor releases may also change a class' expected behavior "
"as required to fix some bugs. This is especially the case in classes marked "
"as *experimental* in the documentation."
msgstr ""

#: ../../docs/about/release_policy.rst:183
msgid ""
"*Major* releases bring a lot of new functionality, but they also remove "
"previously existing functionality and may raise hardware requirements. They "
"also require much more work to upgrade to compared to minor releases. As a "
"result, we recommend sticking with the major release you've started your "
"project with if you are happy with how your project currently works. For "
"example, if your project was started with 3.5, we recommend upgrading to "
"3.5.2 and possibly 3.6 in the future, but not to 4.0+, unless your project "
"really needs the new features that come with 4.0+."
msgstr ""

#: ../../docs/about/release_policy.rst:195
msgid "When is the next release out?"
msgstr ""

#: ../../docs/about/release_policy.rst:197
msgid ""
"While Godot contributors aren't working under any deadlines, we strive to "
"publish minor releases relatively frequently."
msgstr ""

#: ../../docs/about/release_policy.rst:200
msgid ""
"In particular, after the very length release cycle for 4.0, we are pivoting "
"to a faster paced development workflow, 4.1 released 4 months after 4.0, and "
"4.2 released 4 months after 4.1"
msgstr ""

#: ../../docs/about/release_policy.rst:204
msgid ""
"Frequent minor releases will enable us to ship new features faster (possibly "
"as experimental), get user feedback quickly, and iterate to improve those "
"features and their usability. Likewise, the general user experience will be "
"improved more steadily with a faster path to the end users."
msgstr ""

#: ../../docs/about/release_policy.rst:209
msgid ""
"Maintenance (patch) releases are released as needed with potentially very "
"short development cycles, to provide users of the current stable branch with "
"the latest bug fixes for their production needs."
msgstr ""

#: ../../docs/about/release_policy.rst:213
msgid ""
"The 3.6 release is still planned and should be the last stable branch of "
"Godot 3.x. It will be a Long-Term Support (LTS) release, which we plan to "
"support for as long as users still need it (due to missing features in Godot "
"4.x, or having published games which they need to keep updating for platform "
"requirements)."
msgstr ""

#: ../../docs/about/release_policy.rst:220
msgid "What are the criteria for compatibility across engine versions?"
msgstr ""

#: ../../docs/about/release_policy.rst:224
msgid ""
"This section is intended to be used by contributors to determine which "
"changes are safe for a given release. The list is not exhaustive; it only "
"outlines the most common situations encountered during Godot's development."
msgstr ""

#: ../../docs/about/release_policy.rst:228
msgid "The following changes are acceptable in patch releases:"
msgstr ""

#: ../../docs/about/release_policy.rst:230
msgid ""
"Fixing a bug in a way that has no major negative impact on most projects, "
"such as a visual or physics bug. Godot's physics engine is not "
"deterministic, so physics bug fixes are not considered to break "
"compatibility. If fixing a bug has a negative impact that could impact a lot "
"of projects, it should be made optional (e.g. using a project setting or "
"separate method)."
msgstr ""

#: ../../docs/about/release_policy.rst:235
msgid "Adding a new optional parameter to a method."
msgstr ""

#: ../../docs/about/release_policy.rst:236
msgid "Small-scale editor usability tweaks."
msgstr ""

#: ../../docs/about/release_policy.rst:238
msgid ""
"Note that we tend to be more conservative with the fixes we allow in each "
"subsequent patch release. For instance, 4.0.1 may receive more impactful "
"fixes than 4.0.4 would."
msgstr ""

#: ../../docs/about/release_policy.rst:242
msgid ""
"The following changes are acceptable in minor releases, but not patch "
"releases:"
msgstr ""

#: ../../docs/about/release_policy.rst:244
#, fuzzy
msgid "Significant new features."
msgstr "Kreiranje Sadržaja"

#: ../../docs/about/release_policy.rst:245
msgid ""
"Renaming a method parameter. In C#, method parameters can be passed by name "
"(but not in GDScript). As a result, this can break some projects that use C#."
msgstr ""

#: ../../docs/about/release_policy.rst:247
msgid ""
"Deprecating a method, member variable, or class. This is done by adding a "
"deprecated flag to its class reference, which will show up in the editor. "
"When a method is marked as deprecated, it's slated to be removed in the next "
"*major* release."
msgstr ""

#: ../../docs/about/release_policy.rst:251
msgid "Changes that affect the default project theme's visuals."
msgstr ""

#: ../../docs/about/release_policy.rst:252
msgid ""
"Bug fixes which significantly change the behavior or the output, with the "
"aim to meet user expectations better. In comparison, in patch releases, we "
"may favor keeping a buggy behavior so we don't break existing projects which "
"likely already rely on the bug or use a workaround."
msgstr ""

#: ../../docs/about/release_policy.rst:256
msgid "Performance optimizations that result in visual changes."
msgstr ""

#: ../../docs/about/release_policy.rst:258
msgid ""
"The following changes are considered **compatibility-breaking** and can only "
"be performed in a new major release:"
msgstr ""

#: ../../docs/about/release_policy.rst:261
msgid "Renaming or removing a method, member variable, or class."
msgstr ""

#: ../../docs/about/release_policy.rst:262
msgid ""
"Modifying a node's inheritance tree by making it inherit from a different "
"class."
msgstr ""

#: ../../docs/about/release_policy.rst:263
msgid ""
"Changing the default value of a project setting value in a way that affects "
"existing projects. To only affect new projects, the project manager should "
"write a modified ``project.godot`` instead."
msgstr ""

#: ../../docs/about/release_policy.rst:267
msgid ""
"Since Godot 5.0 hasn't been branched off yet, we currently discourage making "
"compatibility-breaking changes of this kind."
msgstr ""

#: ../../docs/about/release_policy.rst:272
msgid ""
"When modifying a method's signature in any fashion (including adding an "
"optional parameter), a GDExtension compatibility method must be created. "
"This ensures that existing GDExtensions continue to work across patch and "
"minor releases, so that users don't have to recompile them. See `pull "
"request #76446 <https://github.com/godotengine/godot/pull/76446>`_ for more "
"information."
msgstr ""

#: ../../docs/about/docs_changelog.rst:4
msgid "Documentation changelog"
msgstr ""

#: ../../docs/about/docs_changelog.rst:6
msgid ""
"The documentation is continually being improved. New releases include new "
"pages, fixes and updates to existing pages, and many updates to the :ref:"
"`class reference <doc_class_reference>`. Below is a list of new pages added "
"since version 3.0."
msgstr ""

#: ../../docs/about/docs_changelog.rst:11
msgid ""
"This document only contains new pages so not all changes are reflected, many "
"pages have been substantially updated but are not reflected in this document."
msgstr ""

#: ../../docs/about/docs_changelog.rst:15
msgid "New pages since version 4.1"
msgstr ""

#: ../../docs/about/docs_changelog.rst:18
#: ../../docs/getting_started/first_2d_game/01.project_setup.rst:22
#: ../../docs/tutorials/performance/cpu_optimization.rst:169
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:35
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:75
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:109
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:239
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:374
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:483
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:565
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:576
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:594
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:631
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:647
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:662
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:679
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:691
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:699
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:712
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:720
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:733
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:767
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:775
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:783
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:78
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:118
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:216
msgid "C#"
msgstr ""

#: ../../docs/about/docs_changelog.rst:20
#, fuzzy
msgid ":ref:`doc_c_sharp_diagnostics`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/about/docs_changelog.rst:23
#: ../../docs/about/docs_changelog.rst:46
#: ../../docs/about/docs_changelog.rst:95
#: ../../docs/about/docs_changelog.rst:198
msgid "Development"
msgstr "Razvoj"

#: ../../docs/about/docs_changelog.rst:25
#, fuzzy
msgid ":ref:`doc_2d_coordinate_systems`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/about/docs_changelog.rst:28
#: ../../docs/about/docs_changelog.rst:52
#: ../../docs/about/docs_changelog.rst:100
msgid "Migrating"
msgstr ""

#: ../../docs/about/docs_changelog.rst:30
#, fuzzy
msgid ":ref:`doc_upgrading_to_godot_4.2`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/about/docs_changelog.rst:33
msgid "I/O"
msgstr ""

#: ../../docs/about/docs_changelog.rst:35
#, fuzzy
msgid ":ref:`doc_runtime_loading_and_saving`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/about/docs_changelog.rst:38
#: ../../docs/about/docs_changelog.rst:229
#: ../../docs/about/docs_changelog.rst:430
#: ../../docs/tutorials/platform/index.rst:4
msgid "Platform-specific"
msgstr ""

#: ../../docs/about/docs_changelog.rst:40
#, fuzzy
msgid ":ref:`doc_android_library`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/about/docs_changelog.rst:43
msgid "New pages since version 4.0"
msgstr ""

#: ../../docs/about/docs_changelog.rst:48
#, fuzzy
msgid ":ref:`doc_internal_rendering_architecture`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/about/docs_changelog.rst:49
#, fuzzy
msgid ":ref:`doc_using_sanitizers`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/about/docs_changelog.rst:54
#, fuzzy
msgid ":ref:`doc_upgrading_to_godot_4.1`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/about/docs_changelog.rst:57
#: ../../docs/about/docs_changelog.rst:105
#: ../../docs/about/docs_changelog.rst:236
#: ../../docs/about/docs_changelog.rst:387
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:104
#: ../../docs/tutorials/performance/cpu_optimization.rst:235
#: ../../docs/tutorials/physics/index.rst:2
msgid "Physics"
msgstr ""

#: ../../docs/about/docs_changelog.rst:59
#, fuzzy
msgid ":ref:`doc_troubleshooting_physics_issues`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/about/docs_changelog.rst:62
msgid "New pages since version 3.6"
msgstr ""

#: ../../docs/about/docs_changelog.rst:65
#: ../../docs/about/docs_changelog.rst:269
#: ../../docs/about/docs_changelog.rst:374 ../../docs/tutorials/2d/index.rst:2
msgid "2D"
msgstr ""

#: ../../docs/about/docs_changelog.rst:67
#, fuzzy
msgid ":ref:`doc_2d_antialiasing`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/about/docs_changelog.rst:70
#: ../../docs/about/docs_changelog.rst:143
#: ../../docs/about/docs_changelog.rst:174
#: ../../docs/about/docs_changelog.rst:380 ../../docs/tutorials/3d/index.rst:2
#: ../../docs/tutorials/performance/index.rst:72
msgid "3D"
msgstr ""

#: ../../docs/about/docs_changelog.rst:72
#, fuzzy
msgid ":ref:`doc_3d_antialiasing`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/about/docs_changelog.rst:73
#, fuzzy
msgid ":ref:`doc_faking_global_illumination`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/about/docs_changelog.rst:74
#, fuzzy
msgid ":ref:`doc_introduction_to_global_illumination`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/about/docs_changelog.rst:75
#, fuzzy
msgid ":ref:`doc_mesh_lod`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/about/docs_changelog.rst:76
#, fuzzy
msgid ":ref:`doc_occlusion_culling`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/about/docs_changelog.rst:77
#, fuzzy
msgid ":ref:`doc_using_sdfgi`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/about/docs_changelog.rst:78
#, fuzzy
msgid ":ref:`doc_using_decals`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/about/docs_changelog.rst:79
#, fuzzy
msgid ":ref:`doc_visibility_ranges`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/about/docs_changelog.rst:80
#, fuzzy
msgid ":ref:`doc_volumetric_fog`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/about/docs_changelog.rst:81
#, fuzzy
msgid ":ref:`doc_variable_rate_shading`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/about/docs_changelog.rst:82
#, fuzzy
msgid ":ref:`doc_physical_light_and_camera_units`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/about/docs_changelog.rst:87
#, fuzzy
msgid ":ref:`doc_creating_movies`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/about/docs_changelog.rst:90
#: ../../docs/tutorials/assets_pipeline/index.rst:2
msgid "Assets pipeline"
msgstr ""

#: ../../docs/about/docs_changelog.rst:92
#, fuzzy
msgid ":ref:`doc_retargeting_3d_skeletons`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/about/docs_changelog.rst:97
#, fuzzy
msgid ":ref:`doc_custom_platform_ports`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/about/docs_changelog.rst:102
#, fuzzy
msgid ":ref:`doc_upgrading_to_godot_4`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/about/docs_changelog.rst:107
#, fuzzy
msgid ":ref:`doc_large_world_coordinates`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/about/docs_changelog.rst:112
#, fuzzy
msgid ":ref:`doc_custom_performance_monitors`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/about/docs_changelog.rst:113
#, fuzzy
msgid ":ref:`doc_c_sharp_collections`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/about/docs_changelog.rst:114
#, fuzzy
msgid ":ref:`doc_c_sharp_global_classes`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/about/docs_changelog.rst:115
#, fuzzy
msgid ":ref:`doc_c_sharp_variant`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/about/docs_changelog.rst:120
#, fuzzy
msgid ":ref:`doc_compute_shaders`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/about/docs_changelog.rst:123
msgid "Workflow"
msgstr ""

#: ../../docs/about/docs_changelog.rst:125
#, fuzzy
msgid ":ref:`doc_pr_review_guidelines`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/about/docs_changelog.rst:128
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:216
#: ../../docs/tutorials/xr/index.rst:2
msgid "XR"
msgstr ""

#: ../../docs/about/docs_changelog.rst:130
#, fuzzy
msgid ":ref:`doc_introducing_xr_tools`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/about/docs_changelog.rst:131
#, fuzzy
msgid ":ref:`doc_xr_action_map`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/about/docs_changelog.rst:132
#, fuzzy
msgid ":ref:`doc_deploying_to_android`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/about/docs_changelog.rst:135
msgid "New pages since version 3.5"
msgstr ""

#: ../../docs/about/docs_changelog.rst:137
msgid "None."
msgstr ""

#: ../../docs/about/docs_changelog.rst:140
msgid "New pages since version 3.4"
msgstr ""

#: ../../docs/about/docs_changelog.rst:145
#, fuzzy
msgid ":ref:`doc_3d_text`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/about/docs_changelog.rst:150
#, fuzzy
msgid ":ref:`doc_playing_videos`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/about/docs_changelog.rst:155
#, fuzzy
msgid ":ref:`doc_managing_editor_features`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/about/docs_changelog.rst:158
msgid "New pages since version 3.3"
msgstr ""

#: ../../docs/about/docs_changelog.rst:161
#: ../../docs/getting_started/first_2d_game/01.project_setup.rst:33
#: ../../docs/tutorials/performance/cpu_optimization.rst:184
msgid "C++"
msgstr ""

#: ../../docs/about/docs_changelog.rst:163
#, fuzzy
msgid ":ref:`doc_cpp_usage_guidelines`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/about/docs_changelog.rst:166
#: ../../docs/getting_started/step_by_step/scripting_languages.rst:59
#: ../../docs/getting_started/first_2d_game/01.project_setup.rst:15
#: ../../docs/tutorials/performance/cpu_optimization.rst:160
#: ../../docs/tutorials/scripting/gdscript/index.rst:2
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:35
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:75
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:109
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:239
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:374
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:483
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:565
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:576
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:594
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:631
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:647
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:662
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:679
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:691
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:699
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:712
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:720
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:733
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:767
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:775
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:783
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:78
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:118
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:216
#: ../../docs/tutorials/scripting/debug/overview_of_debugging_tools.rst:128
msgid "GDScript"
msgstr ""

#: ../../docs/about/docs_changelog.rst:168
#, fuzzy
msgid ":ref:`doc_gdscript_documentation_comments`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/about/docs_changelog.rst:171
msgid "New pages since version 3.2"
msgstr ""

#: ../../docs/about/docs_changelog.rst:176
#, fuzzy
msgid ":ref:`doc_3d_rendering_limitations`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/about/docs_changelog.rst:181
#, fuzzy
msgid ":ref:`doc_troubleshooting`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/about/docs_changelog.rst:182
#, fuzzy
msgid ":ref:`doc_list_of_features`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/about/docs_changelog.rst:183
#, fuzzy
msgid ":ref:`doc_release_policy`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/about/docs_changelog.rst:186
#: ../../docs/tutorials/best_practices/index.rst:2
#: ../../docs/tutorials/assets_pipeline/importing_images.rst:537
#: ../../docs/tutorials/assets_pipeline/importing_audio_samples.rst:268
#: ../../docs/tutorials/audio/text_to_speech.rst:93
msgid "Best practices"
msgstr ""

#: ../../docs/about/docs_changelog.rst:188
#, fuzzy
msgid ":ref:`doc_version_control_systems`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/about/docs_changelog.rst:193
msgid ":ref:`doc_best_practices_for_engine_contributors`"
msgstr ""

#: ../../docs/about/docs_changelog.rst:194
#, fuzzy
msgid ":ref:`doc_bisecting_regressions`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/about/docs_changelog.rst:195
#, fuzzy
msgid ":ref:`doc_editor_and_docs_localization`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/about/docs_changelog.rst:200
#, fuzzy
msgid ":ref:`doc_introduction_to_editor_development`"
msgstr "Uvod"

#: ../../docs/about/docs_changelog.rst:201
#, fuzzy
msgid ":ref:`doc_editor_style_guide`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/about/docs_changelog.rst:202
#, fuzzy
msgid ":ref:`doc_common_engine_methods_and_macros`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/about/docs_changelog.rst:203
#, fuzzy
msgid ":ref:`doc_vulkan_validation_layers`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/about/docs_changelog.rst:204
#, fuzzy
msgid ":ref:`doc_gdscript_grammar`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/about/docs_changelog.rst:205
msgid "Configuring an IDE: :ref:`doc_configuring_an_ide_code_blocks`"
msgstr ""

#: ../../docs/about/docs_changelog.rst:210
#, fuzzy
msgid ":ref:`doc_default_key_mapping`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/about/docs_changelog.rst:211
#, fuzzy
msgid ":ref:`doc_using_the_web_editor`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/about/docs_changelog.rst:214
#: ../../docs/tutorials/export/index.rst:2
msgid "Export"
msgstr ""

#: ../../docs/about/docs_changelog.rst:216
#, fuzzy
msgid ":ref:`doc_exporting_for_dedicated_servers`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/about/docs_changelog.rst:221
msgid ":ref:`doc_controllers_gamepads_joysticks`"
msgstr ""

#: ../../docs/about/docs_changelog.rst:224
#: ../../docs/about/docs_changelog.rst:280
#: ../../docs/tutorials/math/index.rst:2
msgid "Math"
msgstr ""

#: ../../docs/about/docs_changelog.rst:226
#, fuzzy
msgid ":ref:`doc_random_number_generation`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/about/docs_changelog.rst:231
#, fuzzy
msgid ":ref:`doc_plugins_for_ios`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/about/docs_changelog.rst:232
#, fuzzy
msgid ":ref:`doc_ios_plugin`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/about/docs_changelog.rst:233
#, fuzzy
msgid ":ref:`doc_html5_shell_classref`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/about/docs_changelog.rst:238
#, fuzzy
msgid ":ref:`doc_collision_shapes_2d`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/about/docs_changelog.rst:239
#, fuzzy
msgid ":ref:`doc_collision_shapes_3d`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/about/docs_changelog.rst:244
#, fuzzy
msgid ":ref:`doc_shaders_style_guide`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/about/docs_changelog.rst:249
#, fuzzy
msgid ":ref:`doc_debugger_panel`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/about/docs_changelog.rst:250
#, fuzzy
msgid ":ref:`doc_creating_script_templates`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/about/docs_changelog.rst:251
#, fuzzy
msgid ":ref:`doc_evaluating_expressions`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/about/docs_changelog.rst:252
#, fuzzy
msgid ":ref:`doc_what_is_gdextension`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/about/docs_changelog.rst:253
msgid ""
":ref:`doc_gdscript_warning_system` (split from :ref:"
"`doc_gdscript_static_typing`)"
msgstr ""

#: ../../docs/about/docs_changelog.rst:256
msgid "User Interface (UI)"
msgstr ""

#: ../../docs/about/docs_changelog.rst:258
#, fuzzy
msgid ":ref:`doc_control_node_gallery`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/about/docs_changelog.rst:261
msgid "New pages since version 3.1"
msgstr ""

#: ../../docs/about/docs_changelog.rst:264
#: ../../docs/about/docs_changelog.rst:358
msgid "Project workflow"
msgstr ""

#: ../../docs/about/docs_changelog.rst:266
#, fuzzy
msgid ":ref:`doc_android_gradle_build`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/about/docs_changelog.rst:271
#, fuzzy
msgid ":ref:`doc_2d_sprite_animation`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/about/docs_changelog.rst:276
#, fuzzy
msgid ":ref:`doc_recording_with_microphone`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/about/docs_changelog.rst:277
#, fuzzy
msgid ":ref:`doc_sync_with_audio`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/about/docs_changelog.rst:282
#, fuzzy
msgid ":ref:`doc_beziers_and_curves`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/about/docs_changelog.rst:283
#, fuzzy
msgid ":ref:`doc_interpolation`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/about/docs_changelog.rst:286
msgid "Inputs"
msgstr ""

#: ../../docs/about/docs_changelog.rst:288
#, fuzzy
msgid ":ref:`doc_input_examples`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/about/docs_changelog.rst:293
msgid ":ref:`doc_localization_using_gettext`"
msgstr ""

#: ../../docs/about/docs_changelog.rst:296
#: ../../docs/about/docs_changelog.rst:410
#: ../../docs/tutorials/3d/standard_material_3d.rst:242
msgid "Shading"
msgstr ""

#: ../../docs/about/docs_changelog.rst:301
msgid "Your First Shader Series:"
msgstr ""

#: ../../docs/about/docs_changelog.rst:299
#: ../../docs/about/docs_changelog.rst:417
#, fuzzy
msgid ":ref:`doc_introduction_to_shaders`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/about/docs_changelog.rst:300
msgid ":ref:`doc_your_first_canvasitem_shader`"
msgstr ""

#: ../../docs/about/docs_changelog.rst:301
msgid ":ref:`doc_your_first_spatial_shader`"
msgstr ""

#: ../../docs/about/docs_changelog.rst:302
msgid ":ref:`doc_your_second_spatial_shader`"
msgstr ""

#: ../../docs/about/docs_changelog.rst:303
#, fuzzy
msgid ":ref:`doc_visual_shaders`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/about/docs_changelog.rst:308
msgid ":ref:`doc_webrtc`"
msgstr ""

#: ../../docs/about/docs_changelog.rst:311
#: ../../docs/about/docs_changelog.rst:424
#: ../../docs/tutorials/plugins/index.rst:2
msgid "Plugins"
msgstr ""

#: ../../docs/about/docs_changelog.rst:313
#, fuzzy
msgid ":ref:`doc_android_plugin`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/about/docs_changelog.rst:314
#, fuzzy
msgid ":ref:`doc_inspector_plugins`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/about/docs_changelog.rst:315
#, fuzzy
msgid ":ref:`doc_visual_shader_plugins`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/about/docs_changelog.rst:318
#: ../../docs/about/docs_changelog.rst:435
msgid "Multi-threading"
msgstr ""

#: ../../docs/about/docs_changelog.rst:320
#, fuzzy
msgid ":ref:`doc_using_multiple_threads`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/about/docs_changelog.rst:323
#: ../../docs/about/docs_changelog.rst:440
#, fuzzy
msgid "Creating content"
msgstr "Kreiranje Sadržaja"

#: ../../docs/about/docs_changelog.rst:330
msgid "Procedural geometry series:"
msgstr ""

#: ../../docs/about/docs_changelog.rst:326
msgid ":ref:`Procedural geometry <toc-procedural_geometry>`"
msgstr ""

#: ../../docs/about/docs_changelog.rst:327
#, fuzzy
msgid ":ref:`doc_arraymesh`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/about/docs_changelog.rst:328
#, fuzzy
msgid ":ref:`doc_surfacetool`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/about/docs_changelog.rst:329
#, fuzzy
msgid ":ref:`doc_meshdatatool`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/about/docs_changelog.rst:330
#, fuzzy
msgid ":ref:`doc_immediatemesh`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/about/docs_changelog.rst:333 ../../docs/tutorials/3d/index.rst:33
msgid "Optimization"
msgstr ""

#: ../../docs/about/docs_changelog.rst:335
msgid ":ref:`doc_using_multimesh`"
msgstr ""

#: ../../docs/about/docs_changelog.rst:336
msgid ":ref:`doc_using_servers`"
msgstr ""

#: ../../docs/about/docs_changelog.rst:339
msgid "Legal"
msgstr ""

#: ../../docs/about/docs_changelog.rst:341
msgid ":ref:`doc_complying_with_licenses`"
msgstr ""

#: ../../docs/about/docs_changelog.rst:344
msgid "New pages since version 3.0"
msgstr ""

#: ../../docs/about/docs_changelog.rst:347
#: ../../docs/getting_started/step_by_step/index.rst:4
#: ../../docs/contributing/development/compiling/compiling_with_script_encryption_key.rst:32
msgid "Step by step"
msgstr ""

#: ../../docs/about/docs_changelog.rst:349
msgid ":ref:`doc_signals`"
msgstr ""

#: ../../docs/about/docs_changelog.rst:350
#: ../../docs/tutorials/editor/command_line_tutorial.rst:383
msgid "Exporting"
msgstr ""

#: ../../docs/about/docs_changelog.rst:355
msgid ":ref:`doc_gdscript_static_typing`"
msgstr ""

#: ../../docs/about/docs_changelog.rst:360
msgid "Best Practices:"
msgstr ""

#: ../../docs/about/docs_changelog.rst:362
msgid ":ref:`doc_introduction_best_practices`"
msgstr ""

#: ../../docs/about/docs_changelog.rst:363
msgid ":ref:`doc_what_are_godot_classes`"
msgstr ""

#: ../../docs/about/docs_changelog.rst:364
msgid ":ref:`doc_scene_organization`"
msgstr ""

#: ../../docs/about/docs_changelog.rst:365
msgid ":ref:`doc_scenes_versus_scripts`"
msgstr ""

#: ../../docs/about/docs_changelog.rst:366
msgid ":ref:`doc_autoloads_versus_internal_nodes`"
msgstr ""

#: ../../docs/about/docs_changelog.rst:367
msgid ":ref:`doc_node_alternatives`"
msgstr ""

#: ../../docs/about/docs_changelog.rst:368
msgid ":ref:`doc_godot_interfaces`"
msgstr ""

#: ../../docs/about/docs_changelog.rst:369
msgid ":ref:`doc_godot_notifications`"
msgstr ""

#: ../../docs/about/docs_changelog.rst:370
msgid ":ref:`doc_data_preferences`"
msgstr ""

#: ../../docs/about/docs_changelog.rst:371
msgid ":ref:`doc_logic_preferences`"
msgstr ""

#: ../../docs/about/docs_changelog.rst:376
msgid ":ref:`doc_2d_lights_and_shadows`"
msgstr ""

#: ../../docs/about/docs_changelog.rst:377
msgid ":ref:`doc_2d_meshes`"
msgstr ""

#: ../../docs/about/docs_changelog.rst:382
msgid ":ref:`doc_csg_tools`"
msgstr ""

#: ../../docs/about/docs_changelog.rst:383
msgid ":ref:`doc_animating_thousands_of_fish`"
msgstr ""

#: ../../docs/about/docs_changelog.rst:384
msgid ":ref:`doc_controlling_thousands_of_fish`"
msgstr ""

#: ../../docs/about/docs_changelog.rst:389
msgid ":ref:`doc_ragdoll_system`"
msgstr ""

#: ../../docs/about/docs_changelog.rst:390
msgid ":ref:`doc_soft_body`"
msgstr ""

#: ../../docs/about/docs_changelog.rst:395
msgid ":ref:`doc_2d_skeletons`"
msgstr ""

#: ../../docs/about/docs_changelog.rst:396
msgid ":ref:`doc_animation_tree`"
msgstr ""

#: ../../docs/about/docs_changelog.rst:399
msgid "GUI"
msgstr ""

#: ../../docs/about/docs_changelog.rst:401
msgid ":ref:`doc_gui_containers`"
msgstr ""

#: ../../docs/about/docs_changelog.rst:404
msgid "Viewports"
msgstr ""

#: ../../docs/about/docs_changelog.rst:406
msgid ":ref:`doc_viewport_as_texture`"
msgstr ""

#: ../../docs/about/docs_changelog.rst:407
msgid ":ref:`doc_custom_postprocessing`"
msgstr ""

#: ../../docs/about/docs_changelog.rst:412
#, fuzzy
msgid ":ref:`doc_converting_glsl_to_godot_shaders`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/about/docs_changelog.rst:413
msgid ":ref:`doc_advanced_postprocessing`"
msgstr ""

#: ../../docs/about/docs_changelog.rst:415
msgid "Shading Reference:"
msgstr ""

#: ../../docs/about/docs_changelog.rst:418
msgid ":ref:`doc_shading_language`"
msgstr ""

#: ../../docs/about/docs_changelog.rst:419
msgid ":ref:`doc_spatial_shader`"
msgstr ""

#: ../../docs/about/docs_changelog.rst:420
msgid ":ref:`doc_canvas_item_shader`"
msgstr ""

#: ../../docs/about/docs_changelog.rst:421
msgid ":ref:`doc_particle_shader`"
msgstr ""

#: ../../docs/about/docs_changelog.rst:426
#, fuzzy
msgid ":ref:`doc_making_main_screen_plugins`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/about/docs_changelog.rst:427
#, fuzzy
msgid ":ref:`doc_3d_gizmo_plugins`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/about/docs_changelog.rst:432
msgid ":ref:`doc_customizing_html5_shell`"
msgstr ""

#: ../../docs/about/docs_changelog.rst:437
msgid ":ref:`doc_thread_safe_apis`"
msgstr ""

#: ../../docs/about/docs_changelog.rst:442
msgid ":ref:`doc_making_trees`"
msgstr ""

#: ../../docs/about/docs_changelog.rst:447
msgid ":ref:`doc_jitter_stutter`"
msgstr ""

#: ../../docs/about/docs_changelog.rst:448
msgid ":ref:`doc_running_code_in_the_editor`"
msgstr ""

#: ../../docs/about/docs_changelog.rst:449
msgid ":ref:`doc_change_scenes_manually`"
msgstr ""

#: ../../docs/about/docs_changelog.rst:452
#: ../../docs/contributing/development/compiling/compiling_for_windows.rst:114
#: ../../docs/contributing/development/compiling/compiling_for_linuxbsd.rst:238
#: ../../docs/contributing/development/compiling/compiling_for_macos.rst:46
#: ../../docs/contributing/development/compiling/compiling_for_ios.rst:46
msgid "Compiling"
msgstr ""

#: ../../docs/about/docs_changelog.rst:454
msgid ":ref:`doc_optimizing_for_size`"
msgstr ""

#: ../../docs/about/docs_changelog.rst:455
msgid ":ref:`doc_compiling_with_script_encryption_key`"
msgstr ""

#: ../../docs/about/docs_changelog.rst:458
#: ../../docs/contributing/development/index.rst:4
msgid "Engine development"
msgstr ""

#: ../../docs/about/docs_changelog.rst:460
msgid ":ref:`doc_binding_to_external_libraries`"
msgstr ""

#: ../../docs/getting_started/introduction/index.rst:10
msgid ""
"This series will introduce you to Godot and give you an overview of its "
"features."
msgstr ""

#: ../../docs/getting_started/introduction/index.rst:13
msgid ""
"In the following pages, you will get answers to questions such as \"Is Godot "
"for me?\" or \"What can I do with Godot?\". We will then introduce the "
"engine's most essential concepts, run you through the editor's interface, "
"and give you tips to make the most of your time learning it."
msgstr ""

#: ../../docs/getting_started/introduction/introduction_to_godot.rst:4
#, fuzzy
msgid "Introduction to Godot"
msgstr "Uvod"

#: ../../docs/getting_started/introduction/introduction_to_godot.rst:6
msgid ""
"This article is here to help you figure out whether Godot might be a good "
"fit for you. We will introduce some broad features of the engine to give you "
"a feel for what you can achieve with it and answer questions such as \"what "
"do I need to know to get started?\"."
msgstr ""

#: ../../docs/getting_started/introduction/introduction_to_godot.rst:11
msgid ""
"This is by no means an exhaustive overview. We will introduce many more "
"features in this getting started series."
msgstr ""

#: ../../docs/getting_started/introduction/introduction_to_godot.rst:15
msgid "What is Godot?"
msgstr ""

#: ../../docs/getting_started/introduction/introduction_to_godot.rst:17
msgid ""
"Godot is a general-purpose 2D and 3D game engine designed to support all "
"sorts of projects. You can use it to create games or applications you can "
"then release on desktop or mobile, as well as on the web."
msgstr ""

#: ../../docs/getting_started/introduction/introduction_to_godot.rst:21
msgid ""
"You can also create console games with it, although you either need strong "
"programming skills or a developer to port the game for you."
msgstr ""

#: ../../docs/getting_started/introduction/introduction_to_godot.rst:24
msgid ""
"The Godot team can't provide an open source console export due to the "
"licensing terms imposed by console manufacturers. Regardless of the engine "
"you use, though, releasing games on consoles is always a lot of work. You "
"can read more on that here: :ref:`doc_consoles`."
msgstr ""

#: ../../docs/getting_started/introduction/introduction_to_godot.rst:30
msgid "What can the engine do?"
msgstr ""

#: ../../docs/getting_started/introduction/introduction_to_godot.rst:32
msgid ""
"Godot was initially developed in-house by an Argentinian game studio. Its "
"development started in 2001, and the engine was rewritten and improved "
"tremendously since its open source release in 2014."
msgstr ""

#: ../../docs/getting_started/introduction/introduction_to_godot.rst:36
msgid ""
"Some examples of games created with Godot include Ex-Zodiac and Helms of "
"Fury."
msgstr ""

#: ../../docs/getting_started/introduction/introduction_to_godot.rst:42
msgid ""
"As for applications, the open source pixel art drawing program Pixelorama is "
"powered by Godot, and so is the voxel RPG creator RPG in a box."
msgstr ""

#: ../../docs/getting_started/introduction/introduction_to_godot.rst:47
msgid "You can find many more examples in the `official showcase videos`_."
msgstr ""

#: ../../docs/getting_started/introduction/introduction_to_godot.rst:50
msgid "How does it work and look?"
msgstr ""

#: ../../docs/getting_started/introduction/introduction_to_godot.rst:52
msgid ""
"Godot comes with a fully-fledged game editor with integrated tools to answer "
"the most common needs. It includes a code editor, an animation editor, a "
"tilemap editor, a shader editor, a debugger, a profiler, and more."
msgstr ""

#: ../../docs/getting_started/introduction/introduction_to_godot.rst:58
msgid ""
"The team strives to offer a feature-rich game editor with a consistent user "
"experience. While there is always room for improvement, the user interface "
"keeps getting refined."
msgstr ""

#: ../../docs/getting_started/introduction/introduction_to_godot.rst:62
msgid ""
"Of course, if you prefer, you can work with external programs. We officially "
"support importing 3D scenes designed in Blender_ and maintain plugins to "
"code in VSCode_ and Emacs_ for GDScript and C#. We also support Visual "
"Studio for C# on Windows."
msgstr ""

#: ../../docs/getting_started/introduction/introduction_to_godot.rst:70
#: ../../docs/tutorials/scripting/index.rst:12
msgid "Programming languages"
msgstr ""

#: ../../docs/getting_started/introduction/introduction_to_godot.rst:72
msgid "Let's talk about the available programming languages."
msgstr ""

#: ../../docs/getting_started/introduction/introduction_to_godot.rst:74
msgid ""
"You can code your games using :ref:`GDScript <toc-learn-scripting-"
"gdscript>`, a Godot-specific and tightly integrated language with a "
"lightweight syntax, or :ref:`C# <toc-learn-scripting-C#>`, which is popular "
"in the games industry. These are the two main scripting languages we support."
msgstr ""

#: ../../docs/getting_started/introduction/introduction_to_godot.rst:79
msgid ""
"With the GDExtension technology, you can also write gameplay or high-"
"performance algorithms in C or C++ without recompiling the engine. You can "
"use this technology to integrate third-party libraries and other Software "
"Development Kits (SDK) in the engine."
msgstr ""

#: ../../docs/getting_started/introduction/introduction_to_godot.rst:84
msgid ""
"Of course, you can also directly add modules and features to the engine, as "
"it's completely free and open source."
msgstr ""

#: ../../docs/getting_started/introduction/introduction_to_godot.rst:90
msgid "What do I need to know to use Godot?"
msgstr ""

#: ../../docs/getting_started/introduction/introduction_to_godot.rst:92
msgid ""
"Godot is a feature-packed game engine. With its thousands of features, there "
"is a lot to learn. To make the most of it, you need good programming "
"foundations. While we try to make the engine accessible, you will benefit a "
"lot from knowing how to think like a programmer first."
msgstr ""

#: ../../docs/getting_started/introduction/introduction_to_godot.rst:97
msgid ""
"Godot relies on the object-oriented programming paradigm. Being comfortable "
"with concepts such as classes and objects will help you code efficiently in "
"it."
msgstr ""

#: ../../docs/getting_started/introduction/introduction_to_godot.rst:100
msgid ""
"If you are entirely new to programming, we recommend following the `CS50 "
"open courseware`_ from Harvard University. It's a great free course that "
"will teach you everything you need to know to be off to a good start. It "
"will save you countless hours and hurdles learning any game engine afterward."
msgstr ""

#: ../../docs/getting_started/introduction/introduction_to_godot.rst:105
msgid ""
"In CS50, you will learn multiple programming languages. Don't be afraid of "
"that: programming languages have many similarities. The skills you learn "
"with one language transfer well to others."
msgstr ""

#: ../../docs/getting_started/introduction/introduction_to_godot.rst:109
msgid ""
"We will provide you with more Godot-specific learning resources in :ref:"
"`doc_learning_new_features`."
msgstr ""

#: ../../docs/getting_started/introduction/introduction_to_godot.rst:112
msgid ""
"In the next part, you will get an overview of the engine's essential "
"concepts."
msgstr ""

#: ../../docs/getting_started/introduction/key_concepts_overview.rst:8
msgid "Overview of Godot's key concepts"
msgstr ""

#: ../../docs/getting_started/introduction/key_concepts_overview.rst:10
msgid ""
"Every game engine revolves around abstractions you use to build your "
"applications. In Godot, a game is a **tree** of **nodes** that you group "
"together into **scenes**. You can then wire these nodes so they can "
"communicate using **signals**."
msgstr ""

#: ../../docs/getting_started/introduction/key_concepts_overview.rst:15
msgid ""
"These are the four concepts you will learn here. We're going to look at them "
"briefly to give you a sense of how the engine works. In the getting started "
"series, you will get to use them in practice."
msgstr ""

#: ../../docs/getting_started/introduction/key_concepts_overview.rst:20
#: ../../docs/getting_started/step_by_step/nodes_and_scenes.rst:40
#: ../../docs/tutorials/best_practices/what_are_godot_classes.rst:49
msgid "Scenes"
msgstr ""

#: ../../docs/getting_started/introduction/key_concepts_overview.rst:22
msgid ""
"In Godot, you break down your game in reusable scenes. A scene can be a "
"character, a weapon, a menu in the user interface, a single house, an entire "
"level, or anything you can think of. Godot's scenes are flexible; they fill "
"the role of both prefabs and scenes in some other game engines."
msgstr ""

#: ../../docs/getting_started/introduction/key_concepts_overview.rst:29
msgid ""
"You can also nest scenes. For example, you can put your character in a "
"level, and drag and drop a scene as a child of it."
msgstr ""

#: ../../docs/getting_started/introduction/key_concepts_overview.rst:35
#: ../../docs/getting_started/step_by_step/nodes_and_scenes.rst:14
#: ../../docs/tutorials/2d/2d_lights_and_shadows.rst:33
#: ../../docs/tutorials/scripting/gdscript/gdscript_exports.rst:197
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_exports.rst:245
#: ../../docs/contributing/development/file_formats/tscn.rst:47
msgid "Nodes"
msgstr ""

#: ../../docs/getting_started/introduction/key_concepts_overview.rst:37
msgid ""
"A scene is composed of one or more **nodes**. Nodes are your game's smallest "
"building blocks that you arrange into trees. Here's an example of a "
"character's nodes."
msgstr ""

#: ../../docs/getting_started/introduction/key_concepts_overview.rst:43
msgid ""
"It is made of a ``CharacterBody2D`` node named \"Player\", a ``Camera2D``, a "
"``Sprite2D``, and a ``CollisionShape2D``."
msgstr ""

#: ../../docs/getting_started/introduction/key_concepts_overview.rst:46
msgid ""
"The node names end with \"2D\" because this is a 2D scene. Their 3D "
"counterparts have names that end with \"3D\". Be aware that \"Spatial\" "
"Nodes are now called \"Node3D\" starting with Godot 4."
msgstr ""

#: ../../docs/getting_started/introduction/key_concepts_overview.rst:50
msgid ""
"Notice how nodes and scenes look the same in the editor. When you save a "
"tree of nodes as a scene, it then shows as a single node, with its internal "
"structure hidden in the editor."
msgstr ""

#: ../../docs/getting_started/introduction/key_concepts_overview.rst:54
msgid ""
"Godot provides an extensive library of base node types you can combine and "
"extend to build more powerful ones. 2D, 3D, or user interface, you will do "
"most things with these nodes."
msgstr ""

#: ../../docs/getting_started/introduction/key_concepts_overview.rst:61
#: ../../docs/contributing/development/file_formats/tscn.rst:99
msgid "The scene tree"
msgstr ""

#: ../../docs/getting_started/introduction/key_concepts_overview.rst:63
msgid ""
"All your game's scenes come together in the **scene tree**, literally a tree "
"of scenes. And as scenes are trees of nodes, the scene tree also is a tree "
"of nodes. But it's easier to think of your game in terms of scenes as they "
"can represent characters, weapons, doors, or your user interface."
msgstr ""

#: ../../docs/getting_started/introduction/key_concepts_overview.rst:73
#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:2202
#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:676
#: ../../docs/tutorials/scripting/gdextension/gdextension_cpp_example.rst:589
#: ../../docs/tutorials/scripting/how_to_read_the_godot_api.rst:103
#: ../../docs/contributing/development/core_and_modules/object_class.rst:223
msgid "Signals"
msgstr "Signali"

#: ../../docs/getting_started/introduction/key_concepts_overview.rst:75
msgid ""
"Nodes emit signals when some event occurs. This feature allows you to make "
"nodes communicate without hard-wiring them in code. It gives you a lot of "
"flexibility in how you structure your scenes."
msgstr ""

#: ../../docs/getting_started/introduction/key_concepts_overview.rst:81
msgid ""
"Signals are Godot's version of the *observer* pattern. You can read more "
"about it here: https://gameprogrammingpatterns.com/observer.html"
msgstr ""

#: ../../docs/getting_started/introduction/key_concepts_overview.rst:85
msgid ""
"For example, buttons emit a signal when pressed. You can connect to this "
"signal to run code in reaction to this event, like starting the game or "
"opening a menu."
msgstr ""

#: ../../docs/getting_started/introduction/key_concepts_overview.rst:88
msgid ""
"Other built-in signals can tell you when two objects collided, when a "
"character or monster entered a given area, and much more. You can also "
"define new signals tailored to your game."
msgstr ""

#: ../../docs/getting_started/introduction/key_concepts_overview.rst:93
#: ../../docs/getting_started/step_by_step/instancing.rst:212
#: ../../docs/getting_started/step_by_step/scripting_languages.rst:154
#: ../../docs/getting_started/step_by_step/scripting_player_input.rst:180
#: ../../docs/getting_started/step_by_step/signals.rst:521
#: ../../docs/tutorials/2d/2d_sprite_animation.rst:279
#: ../../docs/tutorials/2d/2d_movement.rst:286
#: ../../docs/tutorials/3d/global_illumination/introduction_to_global_illumination.rst:327
#: ../../docs/tutorials/export/exporting_pcks.rst:138
#: ../../docs/tutorials/scripting/gdscript/static_typing.rst:496
msgid "Summary"
msgstr ""

#: ../../docs/getting_started/introduction/key_concepts_overview.rst:95
msgid ""
"Nodes, scenes, the scene tree, and signals are four core concepts in Godot "
"that you will manipulate all the time."
msgstr ""

#: ../../docs/getting_started/introduction/key_concepts_overview.rst:98
msgid ""
"Nodes are your game's smallest building blocks. You combine them to create "
"scenes that you then combine and nest into the scene tree. You can then use "
"signals to make nodes react to events in other nodes or different scene tree "
"branches."
msgstr ""

#: ../../docs/getting_started/introduction/key_concepts_overview.rst:102
msgid ""
"After this short breakdown, you probably have many questions. Bear with us "
"as you will get many answers throughout the getting started series."
msgstr ""

#: ../../docs/getting_started/introduction/first_look_at_the_editor.rst:10
#: ../../docs/getting_started/introduction/first_look_at_the_editor.rst:43
#, fuzzy
msgid "First look at Godot's editor"
msgstr "Uvod"

#: ../../docs/getting_started/introduction/first_look_at_the_editor.rst:12
msgid ""
"This page will give you a brief overview of Godot's interface. We're going "
"to look at the different main screens and docks to help you situate yourself."
msgstr ""

#: ../../docs/getting_started/introduction/first_look_at_the_editor.rst:15
msgid ""
"For a comprehensive breakdown of the editor's interface and how to use it, "
"see the :ref:`Editor manual <toc-learn-editor>`."
msgstr ""

#: ../../docs/getting_started/introduction/first_look_at_the_editor.rst:19
msgid "The Project Manager"
msgstr ""

#: ../../docs/getting_started/introduction/first_look_at_the_editor.rst:21
msgid ""
"When you launch Godot, the first window you see is the Project Manager. In "
"the default tab **Local Projects**, you can manage existing projects, import "
"or create new ones, and more."
msgstr ""

#: ../../docs/getting_started/introduction/first_look_at_the_editor.rst:27
msgid ""
"At the top of the window, there is another tab named \"Asset Library "
"Projects\". You can search for demo projects in the open source asset "
"library, which includes many projects developed by the community."
msgstr ""

#: ../../docs/getting_started/introduction/first_look_at_the_editor.rst:31
msgid ""
"To learn the Project Manager's ins and outs, read :ref:`doc_project_manager`."
msgstr ""

#: ../../docs/getting_started/introduction/first_look_at_the_editor.rst:36
msgid ""
"You can also change the editor's language using the drop-down menu to the "
"right of the engine's version in the window's top-right corner. By default, "
"it is in English (EN)."
msgstr ""

#: ../../docs/getting_started/introduction/first_look_at_the_editor.rst:45
msgid ""
"When you open a new or an existing project, the editor's interface appears. "
"Let's look at its main areas."
msgstr ""

#: ../../docs/getting_started/introduction/first_look_at_the_editor.rst:50
msgid ""
"By default, it features **menus**, **main screens**, and playtest buttons "
"along the window's top edge."
msgstr ""

#: ../../docs/getting_started/introduction/first_look_at_the_editor.rst:55
msgid ""
"In the center is the **viewport** with its **toolbar** at the top, where "
"you'll find tools to move, scale, or lock the scene's nodes."
msgstr ""

#: ../../docs/getting_started/introduction/first_look_at_the_editor.rst:60
msgid ""
"On either side of the viewport sit the **docks**. And at the bottom of the "
"window lies the **bottom panel**."
msgstr ""

#: ../../docs/getting_started/introduction/first_look_at_the_editor.rst:63
msgid ""
"The toolbar changes based on the context and selected node. Here is the 2D "
"toolbar."
msgstr ""

#: ../../docs/getting_started/introduction/first_look_at_the_editor.rst:67
msgid "Below is the 3D one."
msgstr ""

#: ../../docs/getting_started/introduction/first_look_at_the_editor.rst:71
msgid ""
"Let's look at the docks. The **FileSystem** dock lists your project files, "
"including scripts, images, audio samples, and more."
msgstr ""

#: ../../docs/getting_started/introduction/first_look_at_the_editor.rst:76
msgid "The **Scene** dock lists the active scene's nodes."
msgstr ""

#: ../../docs/getting_started/introduction/first_look_at_the_editor.rst:80
msgid "The **Inspector** allows you to edit the properties of a selected node."
msgstr ""

#: ../../docs/getting_started/introduction/first_look_at_the_editor.rst:84
msgid ""
"The **bottom panel**, situated below the viewport, is the host for the debug "
"console, the animation editor, the audio mixer, and more. They can take "
"precious space, that's why they're folded by default."
msgstr ""

#: ../../docs/getting_started/introduction/first_look_at_the_editor.rst:90
msgid ""
"When you click on one, it expands vertically. Below, you can see the "
"animation editor opened."
msgstr ""

#: ../../docs/getting_started/introduction/first_look_at_the_editor.rst:95
msgid "The four main screens"
msgstr ""

#: ../../docs/getting_started/introduction/first_look_at_the_editor.rst:97
msgid ""
"There are four main screen buttons centered at the top of the editor: 2D, "
"3D, Script, and AssetLib."
msgstr ""

#: ../../docs/getting_started/introduction/first_look_at_the_editor.rst:100
msgid ""
"You'll use the **2D screen** for all types of games. In addition to 2D "
"games, the 2D screen is where you'll build your interfaces."
msgstr ""

#: ../../docs/getting_started/introduction/first_look_at_the_editor.rst:105
msgid ""
"In the **3D screen**, you can work with meshes, lights, and design levels "
"for 3D games."
msgstr ""

#: ../../docs/getting_started/introduction/first_look_at_the_editor.rst:110
msgid ""
"Notice the perspective button under the toolbar. Clicking on it opens a list "
"of options related to the 3D view."
msgstr ""

#: ../../docs/getting_started/introduction/first_look_at_the_editor.rst:115
msgid ""
"Read :ref:`doc_introduction_to_3d` for more detail about the **3D main "
"screen**."
msgstr ""

#: ../../docs/getting_started/introduction/first_look_at_the_editor.rst:118
msgid ""
"The **Script screen** is a complete code editor with a debugger, rich auto-"
"completion, and built-in code reference."
msgstr ""

#: ../../docs/getting_started/introduction/first_look_at_the_editor.rst:123
msgid ""
"Finally, the **AssetLib** is a library of free and open source add-ons, "
"scripts, and assets to use in your projects."
msgstr ""

#: ../../docs/getting_started/introduction/first_look_at_the_editor.rst:128
msgid ""
"You can learn more about the asset library in :ref:`doc_what_is_assetlib`."
msgstr ""

#: ../../docs/getting_started/introduction/first_look_at_the_editor.rst:132
msgid "Integrated class reference"
msgstr ""

#: ../../docs/getting_started/introduction/first_look_at_the_editor.rst:134
msgid "Godot comes with a built-in class reference."
msgstr ""

#: ../../docs/getting_started/introduction/first_look_at_the_editor.rst:136
msgid ""
"You can search for information about a class, method, property, constant, or "
"signal by any one of the following methods:"
msgstr ""

#: ../../docs/getting_started/introduction/first_look_at_the_editor.rst:139
msgid ""
"Pressing :kbd:`F1` (or :kbd:`Alt + Space` on macOS, or :kbd:`fn + F1` for "
"laptops with a :kbd:`fn` key) anywhere in the editor."
msgstr ""

#: ../../docs/getting_started/introduction/first_look_at_the_editor.rst:140
msgid ""
"Clicking the \"Search Help\" button in the top-right of the Script main "
"screen."
msgstr ""

#: ../../docs/getting_started/introduction/first_look_at_the_editor.rst:141
msgid "Clicking on the Help menu and Search Help."
msgstr ""

#: ../../docs/getting_started/introduction/first_look_at_the_editor.rst:142
msgid ""
"Clicking while pressing the :kbd:`Ctrl` key on a class name, function name, "
"or built-in variable in the script editor."
msgstr ""

#: ../../docs/getting_started/introduction/first_look_at_the_editor.rst:148
msgid ""
"When you do any of these, a window pops up. Type to search for any item. You "
"can also use it to browse available objects and methods."
msgstr ""

#: ../../docs/getting_started/introduction/first_look_at_the_editor.rst:153
msgid ""
"Double-click on an item to open the corresponding page in the script main "
"screen."
msgstr ""

#: ../../docs/getting_started/introduction/learning_new_features.rst:8
#, fuzzy
msgid "Learning new features"
msgstr "Kreiranje Sadržaja"

#: ../../docs/getting_started/introduction/learning_new_features.rst:10
msgid ""
"Godot is a feature-rich game engine. There is a lot to learn about it. This "
"page explains how you can use the online manual, built-in code reference, "
"and join online communities to learn new features and techniques."
msgstr ""

#: ../../docs/getting_started/introduction/learning_new_features.rst:15
msgid "Making the most of this manual"
msgstr ""

#: ../../docs/getting_started/introduction/learning_new_features.rst:17
msgid ""
"What you are reading now is the user manual. It documents each of the "
"engine's concepts and available features. When learning a new topic, you can "
"start by browsing the corresponding section of this website. The left menu "
"allows you to explore broad topics while the search bar will help you find "
"more specific pages. If a page exists for a given theme, it will often link "
"to more related content."
msgstr ""

#: ../../docs/getting_started/introduction/learning_new_features.rst:26
msgid ""
"The manual has a companion class reference that explains each Godot class's "
"available functions and properties when programming. While the manual covers "
"general features, concepts, and how to use the editor, the reference is all "
"about using Godot's scripting API (Application Programming Interface). You "
"can access it both online and offline. We recommend browsing the reference "
"offline, from within the Godot editor. To do so, go to Help -> Search Help "
"or press :kbd:`F1`."
msgstr ""

#: ../../docs/getting_started/introduction/learning_new_features.rst:36
msgid ""
"To browse it online, head to the manual's :ref:`Class Reference "
"<doc_class_reference>` section."
msgstr ""

#: ../../docs/getting_started/introduction/learning_new_features.rst:39
msgid "A class reference's page tells you:"
msgstr ""

#: ../../docs/getting_started/introduction/learning_new_features.rst:41
msgid ""
"Where the class exists in the inheritance hierarchy. You can click the top "
"links to jump to parent classes and see the properties and methods a type "
"inherits."
msgstr ""

#: ../../docs/getting_started/introduction/learning_new_features.rst:47
msgid "A summary of the class's role and use cases."
msgstr ""

#: ../../docs/getting_started/introduction/learning_new_features.rst:49
msgid ""
"An explanation of the class's properties, methods, signals, enums, and "
"constants."
msgstr ""

#: ../../docs/getting_started/introduction/learning_new_features.rst:52
msgid "Links to manual pages further detailing the class."
msgstr ""

#: ../../docs/getting_started/introduction/learning_new_features.rst:54
msgid ""
"If the manual or class reference is missing or has insufficient information, "
"please open an Issue in the official `godot-docs <https://github.com/"
"godotengine/godot-docs/issues>`_ GitHub repository to report it."
msgstr ""

#: ../../docs/getting_started/introduction/learning_new_features.rst:59
msgid ""
"You can Ctrl-click any underlined text like the name of a class, property, "
"method, signal, or constant to jump to it."
msgstr ""

#: ../../docs/getting_started/introduction/learning_new_features.rst:63
msgid "Learning to think like a programmer"
msgstr ""

#: ../../docs/getting_started/introduction/learning_new_features.rst:65
msgid ""
"Teaching programming foundations and how to think like a game developer is "
"beyond the scope of Godot's documentation. If you're new to programming, we "
"recommend two excellent free resources to get you started:"
msgstr ""

#: ../../docs/getting_started/introduction/learning_new_features.rst:69
msgid ""
"Harvard university offers a free courseware to learn to program, `CS50 "
"<https://cs50.harvard.edu/x/>`_. It will teach you programming fundamentals, "
"how code works, and how to think like a programmer. These skills are "
"essential to become a game developer and learn any game engine efficiently. "
"You can see this course as an investment that will save you time and trouble "
"when you learn to create games."
msgstr ""

#: ../../docs/getting_started/introduction/learning_new_features.rst:76
msgid ""
"If you prefer books, check out the free ebook `Automate The Boring Stuff "
"With Python <https://automatetheboringstuff.com/>`_ by Al Sweigart."
msgstr ""

#: ../../docs/getting_started/introduction/learning_new_features.rst:80
msgid "Learning with the community"
msgstr ""

#: ../../docs/getting_started/introduction/learning_new_features.rst:82
msgid ""
"Godot has a growing community of users. If you're stuck on a problem or need "
"help to better understand how to achieve something, you can ask other users "
"for help on one of the many `active communities <https://godotengine.org/"
"community>`_."
msgstr ""

#: ../../docs/getting_started/introduction/learning_new_features.rst:87
msgid ""
"The best place to ask questions and find already answered ones is the "
"official `Questions & Answers <https://ask.godotengine.org/>`_ site. These "
"responses show up in search engine results and get saved, allowing other "
"users to benefit from discussions on the platform. Once you have asked a "
"question there, you can share its link on other social platforms. Before "
"asking a question, be sure to look for existing answers that might solve "
"your problem on this website or using your preferred search engine."
msgstr ""

#: ../../docs/getting_started/introduction/learning_new_features.rst:95
msgid ""
"Asking questions well and providing details will help others answer you "
"faster and better. When asking questions, we recommend including the "
"following information:"
msgstr ""

#: ../../docs/getting_started/introduction/learning_new_features.rst:99
msgid ""
"**Describe your goal**. You want to explain what you are trying to achieve "
"design-wise. If you are having trouble figuring out how to make a solution "
"work, there may be a different, easier solution that accomplishes the same "
"goal."
msgstr ""

#: ../../docs/getting_started/introduction/learning_new_features.rst:104
msgid ""
"If there is an error involved, **share the exact error message**. You can "
"copy the exact error message in the editor's Debugger bottom panel by "
"clicking the Copy Error icon. Knowing what it says can help community "
"members better identify how you triggered the error."
msgstr ""

#: ../../docs/getting_started/introduction/learning_new_features.rst:109
msgid ""
"If there is code involved, **share a code sample**. Other users won't be "
"able to help you fix a problem without seeing your code. Share the code as "
"text directly. To do so, you can copy and paste a short code snippet in a "
"chat box, or use a website like `Pastebin <https://pastebin.com/>`_ to share "
"long files."
msgstr ""

#: ../../docs/getting_started/introduction/learning_new_features.rst:115
msgid ""
"**Share a screenshot** of your *Scene* dock along with your written code. "
"Most of the code you write affects nodes in your scenes. As a result, you "
"should think of those scenes as part of your source code."
msgstr ""

#: ../../docs/getting_started/introduction/learning_new_features.rst:121
msgid ""
"Also, please don't take a picture with your phone, the low quality and "
"screen reflections can make it hard to understand the image. Your operating "
"system should have a built-in tool to take screenshots with the :kbd:`PrtSc` "
"(Print Screen) key."
msgstr ""

#: ../../docs/getting_started/introduction/learning_new_features.rst:126
msgid ""
"Alternatively, you can use a program like `ShareX <https://getsharex.com/>`_ "
"on Windows or `FlameShot <https://flameshot.org/>`_ on Linux."
msgstr ""

#: ../../docs/getting_started/introduction/learning_new_features.rst:129
msgid ""
"Sharing a video of your running game can also be really **useful to "
"troubleshoot your game**. You can use programs like `OBS Studio <https://"
"obsproject.com/>`_ and `Screen to GIF <https://www.screentogif.com/>`_ to "
"capture your screen."
msgstr ""

#: ../../docs/getting_started/introduction/learning_new_features.rst:134
msgid ""
"You can then use a service like `streamable <https://streamable.com/>`_ or a "
"cloud provider to upload and share your videos for free."
msgstr ""

#: ../../docs/getting_started/introduction/learning_new_features.rst:137
msgid ""
"If you're not using the stable version of Godot, please mention the version "
"you're using. The answer can be different as available features and the "
"interface evolve rapidly."
msgstr ""

#: ../../docs/getting_started/introduction/learning_new_features.rst:141
msgid ""
"Following these guidelines will maximize your chances of getting the answer "
"you're looking for. They will save time both for you and the persons helping "
"you."
msgstr ""

#: ../../docs/getting_started/introduction/learning_new_features.rst:145
#, fuzzy
msgid "Community tutorials"
msgstr "Zajednica"

#: ../../docs/getting_started/introduction/learning_new_features.rst:147
msgid ""
"This manual aims to provide a comprehensive reference of Godot's features. "
"Aside from the 2D and 3D getting started series, it does not contain "
"tutorials to implement specific game genres. If you're looking for a "
"tutorial about creating a role-playing game, a platformer, or other, please "
"see :ref:`doc_community_tutorials`, which lists content made by the Godot "
"community."
msgstr ""

#: ../../docs/getting_started/introduction/godot_design_philosophy.rst:4
msgid "Godot's design philosophy"
msgstr ""

#: ../../docs/getting_started/introduction/godot_design_philosophy.rst:6
msgid "Now that you've gotten your feet wet, let's talk about Godot's design."
msgstr ""

#: ../../docs/getting_started/introduction/godot_design_philosophy.rst:8
msgid ""
"**Every game engine is different and fits different needs.** Not only do "
"they offer a range of features, but the design of each engine is unique. "
"This leads to different workflows and different ways to form your games' "
"structures. This all stems from their respective design philosophies."
msgstr ""

#: ../../docs/getting_started/introduction/godot_design_philosophy.rst:13
msgid ""
"This page is here to help you understand how Godot works, starting with some "
"of its core pillars. It is not a list of available features, nor is it an "
"engine comparison. To know if any engine can be a good fit for your project, "
"you need to try it out for yourself and understand its design and "
"limitations."
msgstr ""

#: ../../docs/getting_started/introduction/godot_design_philosophy.rst:19
msgid ""
"Please watch `Godot explained in 5 minutes <https://www.youtube.com/watch?"
"v=KjX5llYZ5eQ>`_ if you're looking for an overview of the engine's features."
msgstr ""

#: ../../docs/getting_started/introduction/godot_design_philosophy.rst:24
msgid "Object-oriented design and composition"
msgstr ""

#: ../../docs/getting_started/introduction/godot_design_philosophy.rst:26
msgid ""
"Godot embraces object-oriented design at its core with its flexible scene "
"system and Node hierarchy. It tries to stay away from strict programming "
"patterns to offer an intuitive way to structure your game."
msgstr ""

#: ../../docs/getting_started/introduction/godot_design_philosophy.rst:30
msgid ""
"For one, Godot lets you **compose or aggregate** scenes. It's like nested "
"prefabs: you can create a BlinkingLight scene and a BrokenLantern scene that "
"uses the BlinkingLight. Then, create a city filled with BrokenLanterns. "
"Change the BlinkingLight's color, save, and all the BrokenLanterns in the "
"city will update instantly."
msgstr ""

#: ../../docs/getting_started/introduction/godot_design_philosophy.rst:37
msgid "On top of that, you can **inherit** from any scene."
msgstr ""

#: ../../docs/getting_started/introduction/godot_design_philosophy.rst:39
msgid ""
"A Godot scene could be a Weapon, a Character, an Item, a Door, a Level, part "
"of a level… anything you'd like. It works like a class in pure code, except "
"you're free to design it by using the editor, using only the code, or mixing "
"and matching the two."
msgstr ""

#: ../../docs/getting_started/introduction/godot_design_philosophy.rst:44
msgid ""
"It's different from prefabs you find in several 3D engines, as you can then "
"inherit from and extend those scenes. You may create a Magician that extends "
"your Character. Modify the Character in the editor and the Magician will "
"update as well. It helps you build your projects so that their structure "
"matches the game's design."
msgstr ""

#: ../../docs/getting_started/introduction/godot_design_philosophy.rst:50
#: ../../docs/getting_started/first_2d_game/index.rst:10
#: ../../docs/getting_started/first_3d_game/index.rst:12
#: ../../docs/getting_started/first_3d_game/02.player_input.rst:18
#: ../../docs/getting_started/first_3d_game/03.player_movement_code.rst:15
#: ../../docs/getting_started/first_3d_game/04.mob_scene.rst:24
#: ../../docs/getting_started/first_3d_game/05.spawning_mobs.rst:11
#: ../../docs/getting_started/first_3d_game/06.jump_and_squash.rst:42
#: ../../docs/getting_started/first_3d_game/07.killing_player.rst:24
#: ../../docs/getting_started/first_3d_game/09.adding_animations.rst:12
#: ../../docs/community/asset_library/using_assetlib.rst:16
#: ../../docs/community/asset_library/submitting_to_assetlib.rst:128
msgid "|image0|"
msgstr ""

#: ../../docs/getting_started/introduction/godot_design_philosophy.rst:176
#: ../../docs/getting_started/first_2d_game/index.rst:77
#: ../../docs/getting_started/first_3d_game/index.rst:72
#: ../../docs/getting_started/first_3d_game/02.player_input.rst:166
#: ../../docs/getting_started/first_3d_game/03.player_movement_code.rst:438
#: ../../docs/getting_started/first_3d_game/04.mob_scene.rst:336
#: ../../docs/getting_started/first_3d_game/05.spawning_mobs.rst:334
#: ../../docs/getting_started/first_3d_game/06.jump_and_squash.rst:368
#: ../../docs/getting_started/first_3d_game/07.killing_player.rst:526
#: ../../docs/getting_started/first_3d_game/09.adding_animations.rst:608
#: ../../docs/community/asset_library/using_assetlib.rst:187
#: ../../docs/community/asset_library/submitting_to_assetlib.rst:220
msgid "image0"
msgstr ""

#: ../../docs/getting_started/introduction/godot_design_philosophy.rst:52
msgid ""
"Also note that Godot offers many different types of objects called nodes, "
"each with a specific purpose. Nodes are part of a tree and always inherit "
"from their parents up to the Node class. Although the engine does feature "
"some nodes like collision shapes that a parent physics body will use, most "
"nodes work independently from one another."
msgstr ""

#: ../../docs/getting_started/introduction/godot_design_philosophy.rst:58
msgid ""
"In other words, Godot's nodes do not work like components in some other game "
"engines."
msgstr ""

#: ../../docs/getting_started/introduction/godot_design_philosophy.rst:61
#: ../../docs/getting_started/first_3d_game/02.player_input.rst:47
#: ../../docs/getting_started/first_3d_game/03.player_movement_code.rst:350
#: ../../docs/getting_started/first_3d_game/04.mob_scene.rst:29
#: ../../docs/getting_started/first_3d_game/05.spawning_mobs.rst:21
#: ../../docs/getting_started/first_3d_game/06.jump_and_squash.rst:49
#: ../../docs/getting_started/first_3d_game/07.killing_player.rst:28
#: ../../docs/getting_started/first_3d_game/08.score_and_replay.rst:20
#: ../../docs/getting_started/first_3d_game/09.adding_animations.rst:26
#: ../../docs/community/asset_library/using_assetlib.rst:48
msgid "|image1|"
msgstr ""

#: ../../docs/getting_started/introduction/godot_design_philosophy.rst:177
#: ../../docs/getting_started/first_3d_game/02.player_input.rst:167
#: ../../docs/getting_started/first_3d_game/03.player_movement_code.rst:439
#: ../../docs/getting_started/first_3d_game/04.mob_scene.rst:337
#: ../../docs/getting_started/first_3d_game/05.spawning_mobs.rst:335
#: ../../docs/getting_started/first_3d_game/06.jump_and_squash.rst:369
#: ../../docs/getting_started/first_3d_game/07.killing_player.rst:527
#: ../../docs/getting_started/first_3d_game/08.score_and_replay.rst:451
#: ../../docs/getting_started/first_3d_game/09.adding_animations.rst:609
#: ../../docs/community/asset_library/using_assetlib.rst:188
msgid "image1"
msgstr ""

#: ../../docs/getting_started/introduction/godot_design_philosophy.rst:63
msgid ""
"Sprite2D is a Node2D, a CanvasItem and a Node. It has all the properties and "
"features of its three parent classes, like transforms or the ability to draw "
"custom shapes and render with a custom shader."
msgstr ""

#: ../../docs/getting_started/introduction/godot_design_philosophy.rst:68
msgid "All-inclusive package"
msgstr ""

#: ../../docs/getting_started/introduction/godot_design_philosophy.rst:70
msgid ""
"Godot tries to provide its own tools to answer most common needs. It has a "
"dedicated scripting workspace, an animation editor, a tilemap editor, a "
"shader editor, a debugger, a profiler, the ability to hot-reload locally and "
"on remote devices, etc."
msgstr ""

#: ../../docs/getting_started/introduction/godot_design_philosophy.rst:75
#: ../../docs/getting_started/first_3d_game/02.player_input.rst:52
#: ../../docs/getting_started/first_3d_game/03.player_movement_code.rst:358
#: ../../docs/getting_started/first_3d_game/04.mob_scene.rst:33
#: ../../docs/getting_started/first_3d_game/05.spawning_mobs.rst:26
#: ../../docs/getting_started/first_3d_game/06.jump_and_squash.rst:60
#: ../../docs/getting_started/first_3d_game/07.killing_player.rst:36
#: ../../docs/getting_started/first_3d_game/08.score_and_replay.rst:24
#: ../../docs/getting_started/first_3d_game/09.adding_animations.rst:34
#: ../../docs/community/asset_library/using_assetlib.rst:58
msgid "|image2|"
msgstr ""

#: ../../docs/getting_started/introduction/godot_design_philosophy.rst:178
#: ../../docs/getting_started/first_3d_game/02.player_input.rst:168
#: ../../docs/getting_started/first_3d_game/03.player_movement_code.rst:440
#: ../../docs/getting_started/first_3d_game/04.mob_scene.rst:338
#: ../../docs/getting_started/first_3d_game/05.spawning_mobs.rst:336
#: ../../docs/getting_started/first_3d_game/06.jump_and_squash.rst:370
#: ../../docs/getting_started/first_3d_game/07.killing_player.rst:528
#: ../../docs/getting_started/first_3d_game/08.score_and_replay.rst:452
#: ../../docs/getting_started/first_3d_game/09.adding_animations.rst:610
#: ../../docs/community/asset_library/using_assetlib.rst:189
msgid "image2"
msgstr ""

#: ../../docs/getting_started/introduction/godot_design_philosophy.rst:77
msgid ""
"The goal is to offer a full package to create games and a continuous user "
"experience. You can still work with external programs as long as there is an "
"import plugin available in Godot for it. Or you can create one, like the "
"`Tiled Map Importer <https://github.com/vnen/godot-tiled-importer>`__."
msgstr ""

#: ../../docs/getting_started/introduction/godot_design_philosophy.rst:82
msgid ""
"That is also partly why Godot offers its own programming language GDScript "
"along with C#. GDScript is designed for the needs of game developers and "
"game designers, and is tightly integrated in the engine and the editor."
msgstr ""

#: ../../docs/getting_started/introduction/godot_design_philosophy.rst:87
msgid ""
"GDScript lets you write code using an indentation-based syntax, yet it "
"detects types and offers a static language's quality of auto-completion. It "
"is also optimized for gameplay code with built-in types like Vectors and "
"Colors."
msgstr ""

#: ../../docs/getting_started/introduction/godot_design_philosophy.rst:91
msgid ""
"Note that with GDExtension, you can write high-performance code using "
"compiled languages like C, C++, Rust, D, Haxe, or Swift without recompiling "
"the engine."
msgstr ""

#: ../../docs/getting_started/introduction/godot_design_philosophy.rst:94
msgid ""
"Note that the 3D workspace doesn't feature as many tools as the 2D "
"workspace. You'll need external programs or add-ons to edit terrains, "
"animate complex characters, and so on. Godot provides a complete API to "
"extend the editor's functionality using game code. See `The Godot editor is "
"a Godot game`_ below."
msgstr ""

#: ../../docs/getting_started/introduction/godot_design_philosophy.rst:99
#: ../../docs/getting_started/first_3d_game/02.player_input.rst:77
#: ../../docs/getting_started/first_3d_game/03.player_movement_code.rst:375
#: ../../docs/getting_started/first_3d_game/04.mob_scene.rst:49
#: ../../docs/getting_started/first_3d_game/05.spawning_mobs.rst:52
#: ../../docs/getting_started/first_3d_game/06.jump_and_squash.rst:75
#: ../../docs/getting_started/first_3d_game/07.killing_player.rst:56
#: ../../docs/getting_started/first_3d_game/08.score_and_replay.rst:38
#: ../../docs/getting_started/first_3d_game/09.adding_animations.rst:43
#: ../../docs/community/asset_library/using_assetlib.rst:86
msgid "|image4|"
msgstr ""

#: ../../docs/getting_started/introduction/godot_design_philosophy.rst:179
#: ../../docs/getting_started/first_3d_game/02.player_input.rst:170
#: ../../docs/getting_started/first_3d_game/03.player_movement_code.rst:442
#: ../../docs/getting_started/first_3d_game/04.mob_scene.rst:339
#: ../../docs/getting_started/first_3d_game/05.spawning_mobs.rst:338
#: ../../docs/getting_started/first_3d_game/06.jump_and_squash.rst:372
#: ../../docs/getting_started/first_3d_game/07.killing_player.rst:530
#: ../../docs/getting_started/first_3d_game/08.score_and_replay.rst:454
#: ../../docs/getting_started/first_3d_game/09.adding_animations.rst:612
#: ../../docs/community/asset_library/using_assetlib.rst:191
msgid "image4"
msgstr ""

#: ../../docs/getting_started/introduction/godot_design_philosophy.rst:101
msgid ""
"*A State Machine editor plugin in Godot 2 by kubecz3k. It lets you manage "
"states and transitions visually.*"
msgstr ""

#: ../../docs/getting_started/introduction/godot_design_philosophy.rst:105
msgid "Open source"
msgstr ""

#: ../../docs/getting_started/introduction/godot_design_philosophy.rst:107
msgid ""
"Godot offers a fully open source codebase under the **MIT license**. This "
"means all the technologies that ship with it have to be Free (as in freedom) "
"as well. For the most part, they're developed from the ground up by "
"contributors."
msgstr ""

#: ../../docs/getting_started/introduction/godot_design_philosophy.rst:112
msgid ""
"Anyone can plug in proprietary tools for the needs of their projects — they "
"just won't ship with the engine. This may include Google AdMob, or FMOD. Any "
"of these can come as third-party plugins instead."
msgstr ""

#: ../../docs/getting_started/introduction/godot_design_philosophy.rst:117
msgid ""
"On the other hand, an open codebase means you can **learn from and extend "
"the engine** to your heart's content. You can also debug games easily, as "
"Godot will print errors with a stack trace, even if they come from the "
"engine itself."
msgstr ""

#: ../../docs/getting_started/introduction/godot_design_philosophy.rst:123
msgid ""
"This **does not affect the work you do with Godot** in any way: there's no "
"strings attached to the engine or anything you make with it."
msgstr ""

#: ../../docs/getting_started/introduction/godot_design_philosophy.rst:127
msgid "Community-driven"
msgstr ""

#: ../../docs/getting_started/introduction/godot_design_philosophy.rst:129
msgid ""
"**Godot is made by its community, for the community, and for all game "
"creators out there.** It's the needs of the users and open discussions that "
"drive the core updates. New features from the core developers often focus on "
"what will benefit the most users first."
msgstr ""

#: ../../docs/getting_started/introduction/godot_design_philosophy.rst:134
msgid ""
"That said, although a handful of core developers work on it full-time, the "
"project has over 600 contributors at the time of writing. Benevolent "
"programmers work on features they may need themselves, so you'll see "
"improvements in all corners of the engine at the same time in every major "
"release."
msgstr ""

#: ../../docs/getting_started/introduction/godot_design_philosophy.rst:141
msgid "The Godot editor is a Godot game"
msgstr ""

#: ../../docs/getting_started/introduction/godot_design_philosophy.rst:143
msgid ""
"The Godot editor runs on the game engine. It uses the engine's own UI "
"system, it can hot-reload code and scenes when you test your projects, or "
"run game code in the editor. This means you can **use the same code** and "
"scenes for your games, or **build plugins and extend the editor.**"
msgstr ""

#: ../../docs/getting_started/introduction/godot_design_philosophy.rst:148
msgid ""
"This leads to a reliable and flexible UI system, as it powers the editor "
"itself. With the ``@tool`` annotation, you can run any game code in the "
"editor."
msgstr ""

#: ../../docs/getting_started/introduction/godot_design_philosophy.rst:151
#: ../../docs/getting_started/first_3d_game/02.player_input.rst:82
#: ../../docs/getting_started/first_3d_game/03.player_movement_code.rst:386
#: ../../docs/getting_started/first_3d_game/04.mob_scene.rst:85
#: ../../docs/getting_started/first_3d_game/05.spawning_mobs.rst:56
#: ../../docs/getting_started/first_3d_game/06.jump_and_squash.rst:84
#: ../../docs/getting_started/first_3d_game/07.killing_player.rst:134
#: ../../docs/getting_started/first_3d_game/08.score_and_replay.rst:50
#: ../../docs/getting_started/first_3d_game/09.adding_animations.rst:51
#: ../../docs/community/asset_library/using_assetlib.rst:90
msgid "|image5|"
msgstr ""

#: ../../docs/getting_started/introduction/godot_design_philosophy.rst:180
#: ../../docs/getting_started/first_3d_game/02.player_input.rst:171
#: ../../docs/getting_started/first_3d_game/03.player_movement_code.rst:443
#: ../../docs/getting_started/first_3d_game/04.mob_scene.rst:340
#: ../../docs/getting_started/first_3d_game/05.spawning_mobs.rst:339
#: ../../docs/getting_started/first_3d_game/06.jump_and_squash.rst:373
#: ../../docs/getting_started/first_3d_game/07.killing_player.rst:531
#: ../../docs/getting_started/first_3d_game/08.score_and_replay.rst:455
#: ../../docs/getting_started/first_3d_game/09.adding_animations.rst:613
#: ../../docs/community/asset_library/using_assetlib.rst:192
msgid "image5"
msgstr ""

#: ../../docs/getting_started/introduction/godot_design_philosophy.rst:153
msgid ""
"*RPG in a Box is a voxel RPG editor made with Godot 2. It uses Godot's UI "
"tools for its node-based programming system and for the rest of the "
"interface.*"
msgstr ""

#: ../../docs/getting_started/introduction/godot_design_philosophy.rst:157
msgid ""
"Put the ``@tool`` annotation at the top of any GDScript file and it will run "
"in the editor. This lets you import and export plugins, create plugins like "
"custom level editors, or create scripts with the same nodes and API you use "
"in your projects."
msgstr ""

#: ../../docs/getting_started/introduction/godot_design_philosophy.rst:164
msgid ""
"The editor is fully written in C++ and is statically compiled into the "
"binary. This means you can't import it as a typical project that would have "
"a ``project.godot`` file."
msgstr ""

#: ../../docs/getting_started/introduction/godot_design_philosophy.rst:169
msgid "Separate 2D and 3D engines"
msgstr ""

#: ../../docs/getting_started/introduction/godot_design_philosophy.rst:171
msgid ""
"Godot offers dedicated 2D and 3D rendering engines. As a result, **the base "
"unit for 2D scenes is pixels.** Even though the engines are separate, you "
"can render 2D in 3D, 3D in 2D, and overlay 2D sprites and interfaces over "
"your 3D world."
msgstr ""

#: ../../docs/getting_started/step_by_step/index.rst:6
msgid ""
"This series builds upon the :ref:`Introduction to Godot <toc-learn-"
"introduction>` and will get you started with the editor and the engine. You "
"will learn more about nodes and scenes, code your first classes with "
"GDScript, use signals to make nodes communicate with one another, and more."
msgstr ""

#: ../../docs/getting_started/step_by_step/index.rst:11
msgid ""
"The following lessons are here to prepare you for :ref:"
"`doc_your_first_2d_game`, a step-by-step tutorial where you will code a game "
"from scratch. By the end of it, you will have the necessary foundations to "
"explore more features in other sections. We also included links to pages "
"that cover a given topic in-depth where appropriate."
msgstr ""

#: ../../docs/getting_started/step_by_step/nodes_and_scenes.rst:7
msgid "Nodes and Scenes"
msgstr ""

#: ../../docs/getting_started/step_by_step/nodes_and_scenes.rst:9
msgid ""
"In :ref:`doc_key_concepts_overview`, we saw that a Godot game is a tree of "
"scenes and that each scene is a tree of nodes. In this lesson, we explain a "
"bit more about them. You will also create your first scene."
msgstr ""

#: ../../docs/getting_started/step_by_step/nodes_and_scenes.rst:16
msgid ""
"**Nodes are the fundamental building blocks of your game**. They are like "
"the ingredients in a recipe. There are dozens of kinds that can display an "
"image, play a sound, represent a camera, and much more."
msgstr ""

#: ../../docs/getting_started/step_by_step/nodes_and_scenes.rst:22
#, fuzzy
msgid "All nodes have the following characteristics:"
msgstr "Glavna dokumentacija za sajt je podeljena na sledeća poglavlja:"

#: ../../docs/getting_started/step_by_step/nodes_and_scenes.rst:24
msgid "A name."
msgstr ""

#: ../../docs/getting_started/step_by_step/nodes_and_scenes.rst:25
msgid "Editable properties."
msgstr ""

#: ../../docs/getting_started/step_by_step/nodes_and_scenes.rst:26
msgid "They receive callbacks to update every frame."
msgstr ""

#: ../../docs/getting_started/step_by_step/nodes_and_scenes.rst:27
msgid "You can extend them with new properties and functions."
msgstr ""

#: ../../docs/getting_started/step_by_step/nodes_and_scenes.rst:28
msgid "You can add them to another node as a child."
msgstr ""

#: ../../docs/getting_started/step_by_step/nodes_and_scenes.rst:30
msgid ""
"The last characteristic is important. **Together, nodes form a tree**, which "
"is a powerful feature to organize projects. Since different nodes have "
"different functions, combining them produces more complex behavior. As we "
"saw before, you can build a playable character the camera follows using a :"
"ref:`CharacterBody2D <class_CharacterBody2D>` node, a :ref:`Sprite2D "
"<class_Sprite2D>` node, a :ref:`Camera2D <class_Camera2D>` node, and a :ref:"
"`CollisionShape2D <class_CollisionShape2D>` node."
msgstr ""

#: ../../docs/getting_started/step_by_step/nodes_and_scenes.rst:42
msgid ""
"When you organize nodes in a tree, like our character, we call this "
"construct a scene. Once saved, scenes work like new node types in the "
"editor, where you can add them as a child of an existing node. In that case, "
"the instance of the scene appears as a single node with its internals hidden."
msgstr ""

#: ../../docs/getting_started/step_by_step/nodes_and_scenes.rst:47
msgid ""
"Scenes allow you to structure your game's code however you want. You can "
"**compose nodes** to create custom and complex node types, like a game "
"character that runs and jumps, a life bar, a chest with which you can "
"interact, and more."
msgstr ""

#: ../../docs/getting_started/step_by_step/nodes_and_scenes.rst:53
msgid ""
"The Godot editor essentially is a **scene editor**. It has plenty of tools "
"for editing 2D and 3D scenes, as well as user interfaces. A Godot project "
"can contain as many of these scenes as you need. The engine only requires "
"one as your application's **main scene**. This is the scene Godot will first "
"load when you or a player runs the game."
msgstr ""

#: ../../docs/getting_started/step_by_step/nodes_and_scenes.rst:59
#, fuzzy
msgid "On top of acting like nodes, scenes have the following characteristics:"
msgstr "Glavna dokumentacija za sajt je podeljena na sledeća poglavlja:"

#: ../../docs/getting_started/step_by_step/nodes_and_scenes.rst:61
msgid "They always have one root node, like the \"Player\" in our example."
msgstr ""

#: ../../docs/getting_started/step_by_step/nodes_and_scenes.rst:62
msgid "You can save them to your local drive and load them later."
msgstr ""

#: ../../docs/getting_started/step_by_step/nodes_and_scenes.rst:63
msgid ""
"You can create as many instances of a scene as you'd like. You could have "
"five or ten characters in your game, created from your Character scene."
msgstr ""

#: ../../docs/getting_started/step_by_step/nodes_and_scenes.rst:67
#, fuzzy
msgid "Creating your first scene"
msgstr "Kreiranje Sadržaja"

#: ../../docs/getting_started/step_by_step/nodes_and_scenes.rst:69
msgid ""
"Let's create our first scene with a single node. To do so, you will need to :"
"ref:`create a new project <doc_creating_and_importing_projects>` first. "
"After opening the project, you should see an empty editor."
msgstr ""

#: ../../docs/getting_started/step_by_step/nodes_and_scenes.rst:75
msgid ""
"In an empty scene, the Scene dock on the left shows several options to add a "
"root node quickly. \"2D Scene\" adds a :ref:`Node2D <class_Node2D>` node, "
"\"3D Scene\" adds a :ref:`Node3D <class_Node3D>` node, and \"User "
"Interface\" adds a :ref:`Control <class_Control>` node. These presets are "
"here for convenience; they are not mandatory. \"Other Node\" lets you select "
"any node to be the root node. In an empty scene, \"Other Node\" is "
"equivalent to pressing the \"Add Child Node\" button at the top-left of the "
"Scene dock, which usually adds a new node as a child of the currently "
"selected node."
msgstr ""

#: ../../docs/getting_started/step_by_step/nodes_and_scenes.rst:85
msgid ""
"We're going to add a single :ref:`Label <class_Label>` node to our scene. "
"Its function is to draw text on the screen."
msgstr ""

#: ../../docs/getting_started/step_by_step/nodes_and_scenes.rst:88
msgid ""
"Press the \"Add Child Node\" button or \"Other Node\" to create a root node."
msgstr ""

#: ../../docs/getting_started/step_by_step/nodes_and_scenes.rst:92
msgid "The Create Node dialog opens, showing the long list of available nodes."
msgstr ""

#: ../../docs/getting_started/step_by_step/nodes_and_scenes.rst:96
msgid "Select the Label node. You can type its name to filter down the list."
msgstr ""

#: ../../docs/getting_started/step_by_step/nodes_and_scenes.rst:100
msgid ""
"Click on the Label node to select it and click the Create button at the "
"bottom of the window."
msgstr ""

#: ../../docs/getting_started/step_by_step/nodes_and_scenes.rst:105
msgid ""
"A lot happens when you add a scene's first node. The scene changes to the 2D "
"workspace because Label is a 2D node type. The Label appears, selected, in "
"the top-left corner of the viewport. The node appears in the Scene dock on "
"the left, and the node's properties appear in the Inspector dock on the "
"right."
msgstr ""

#: ../../docs/getting_started/step_by_step/nodes_and_scenes.rst:111
#, fuzzy
msgid "Changing a node's properties"
msgstr "Kreiranje Sadržaja"

#: ../../docs/getting_started/step_by_step/nodes_and_scenes.rst:113
msgid ""
"The next step is to change the Label's \"Text\" property. Let's change it to "
"\"Hello World\"."
msgstr ""

#: ../../docs/getting_started/step_by_step/nodes_and_scenes.rst:116
msgid ""
"Head to the Inspector dock on the right of the viewport. Click inside the "
"field below the Text property and type \"Hello World\"."
msgstr ""

#: ../../docs/getting_started/step_by_step/nodes_and_scenes.rst:121
msgid "You will see the text draw in the viewport as you type."
msgstr ""

#: ../../docs/getting_started/step_by_step/nodes_and_scenes.rst:123
msgid ""
"You can edit any property listed in the Inspector as we did with the Text. "
"For a complete reference of the Inspector dock, see :ref:"
"`doc_editor_inspector_dock`."
msgstr ""

#: ../../docs/getting_started/step_by_step/nodes_and_scenes.rst:127
msgid ""
"You can move your Label node in the viewport by selecting the move tool in "
"the toolbar."
msgstr ""

#: ../../docs/getting_started/step_by_step/nodes_and_scenes.rst:132
msgid ""
"With the Label selected, click and drag anywhere in the viewport to move it "
"to the center of the view delimited by the rectangle."
msgstr ""

#: ../../docs/getting_started/step_by_step/nodes_and_scenes.rst:138
#, fuzzy
msgid "Running the scene"
msgstr "Kreiranje Sadržaja"

#: ../../docs/getting_started/step_by_step/nodes_and_scenes.rst:140
msgid ""
"Everything's ready to run the scene! Press the Play Scene button in the top-"
"right of the screen or press :kbd:`F6` (:kbd:`Cmd + R` on macOS)."
msgstr ""

#: ../../docs/getting_started/step_by_step/nodes_and_scenes.rst:145
msgid ""
"A popup invites you to save the scene, which is required to run it. Click "
"the Save button in the file browser to save it as ``label.tscn``."
msgstr ""

#: ../../docs/getting_started/step_by_step/nodes_and_scenes.rst:150
msgid ""
"The Save Scene As dialog, like other file dialogs in the editor, only allows "
"you to save files inside the project. The ``res://`` path at the top of the "
"window represents the project's root directory and stands for \"resource "
"path\". For more information about file paths in Godot, see :ref:"
"`doc_filesystem`."
msgstr ""

#: ../../docs/getting_started/step_by_step/nodes_and_scenes.rst:156
msgid ""
"The application should open in a new window and display the text \"Hello "
"World\"."
msgstr ""

#: ../../docs/getting_started/step_by_step/nodes_and_scenes.rst:160
msgid ""
"Close the window or press :kbd:`F8` (:kbd:`Cmd + .` on macOS) to quit the "
"running scene."
msgstr ""

#: ../../docs/getting_started/step_by_step/nodes_and_scenes.rst:163
#, fuzzy
msgid "Setting the main scene"
msgstr "Kreiranje Sadržaja"

#: ../../docs/getting_started/step_by_step/nodes_and_scenes.rst:165
msgid ""
"To run our test scene, we used the Play Scene button. Another button next to "
"it allows you to set and run the project's main scene. You can press :kbd:"
"`F5` (:kbd:`Cmd + B` on macOS) to do so."
msgstr ""

#: ../../docs/getting_started/step_by_step/nodes_and_scenes.rst:171
msgid "A popup window appears and invites you to select the main scene."
msgstr ""

#: ../../docs/getting_started/step_by_step/nodes_and_scenes.rst:175
msgid ""
"Click the Select button, and in the file dialog that appears, double click "
"on ``label.tscn``."
msgstr ""

#: ../../docs/getting_started/step_by_step/nodes_and_scenes.rst:180
msgid ""
"The demo should run again. Moving forward, every time you run the project, "
"Godot will use this scene as a starting point."
msgstr ""

#: ../../docs/getting_started/step_by_step/nodes_and_scenes.rst:183
msgid ""
"The editor saves the main scene's path in a project.godot file in your "
"project's directory. While you can edit this text file directly to change "
"project settings, you can also use the \"Project -> Project Settings\" "
"window to do so. For more information, see :ref:`doc_project_settings`."
msgstr ""

#: ../../docs/getting_started/step_by_step/nodes_and_scenes.rst:189
msgid ""
"In the next part, we will discuss another key concept in games and in Godot: "
"creating instances of a scene."
msgstr ""

#: ../../docs/getting_started/step_by_step/instancing.rst:4
#, fuzzy
msgid "Creating instances"
msgstr "Kreiranje Sadržaja"

#: ../../docs/getting_started/step_by_step/instancing.rst:6
msgid ""
"In the previous part, we saw that a scene is a collection of nodes organized "
"in a tree structure, with a single node as its root. You can split your "
"project into any number of scenes. This feature helps you break down and "
"organize your game's different components."
msgstr ""

#: ../../docs/getting_started/step_by_step/instancing.rst:11
msgid ""
"You can create as many scenes as you'd like and save them as files with the "
"``.tscn`` extension, which stands for \"text scene\". The ``label.tscn`` "
"file from the previous lesson was an example. We call those files \"Packed "
"Scenes\" as they pack information about your scene's content."
msgstr ""

#: ../../docs/getting_started/step_by_step/instancing.rst:16
msgid ""
"Here's an example of a ball. It's composed of a :ref:`RigidBody2D "
"<class_RigidBody2D>` node as its root named Ball, which allows the ball to "
"fall and bounce on walls, a :ref:`Sprite2D <class_Sprite2D>` node, and a :"
"ref:`CollisionShape2D <class_CollisionShape2D>`."
msgstr ""

#: ../../docs/getting_started/step_by_step/instancing.rst:23
msgid ""
"Once you have saved a scene, it works as a blueprint: you can reproduce it "
"in other scenes as many times as you'd like. Replicating an object from a "
"template like this is called **instancing**."
msgstr ""

#: ../../docs/getting_started/step_by_step/instancing.rst:29
msgid ""
"As we mentioned in the previous part, instanced scenes behave like a node: "
"the editor hides their content by default. When you instance the Ball, you "
"only see the Ball node. Notice also how each duplicate has a unique name."
msgstr ""

#: ../../docs/getting_started/step_by_step/instancing.rst:33
msgid ""
"Every instance of the Ball scene starts with the same structure and "
"properties as ``ball.tscn``. However, you can modify each independently, "
"such as changing how they bounce, how heavy they are, or any property "
"exposed by the source scene."
msgstr ""

#: ../../docs/getting_started/step_by_step/instancing.rst:39
msgid "In practice"
msgstr ""

#: ../../docs/getting_started/step_by_step/instancing.rst:41
msgid ""
"Let's use instancing in practice to see how it works in Godot. We invite you "
"to download the ball's sample project we prepared for you: "
"`instancing_starter.zip <https://github.com/godotengine/godot-docs-project-"
"starters/releases/download/latest-4.x/instancing_starter.zip>`_."
msgstr ""

#: ../../docs/getting_started/step_by_step/instancing.rst:45
msgid ""
"Extract the archive on your computer. To import it, you need the Project "
"Manager. The Project Manager is accessed by opening Godot, or if you already "
"have Godot opened, click on *Project -> Quit to Project List* (:kbd:`Ctrl + "
"Shift + Q`, :kbd:`Ctrl + Option + Cmd + Q` on macOS)"
msgstr ""

#: ../../docs/getting_started/step_by_step/instancing.rst:48
msgid ""
"In the Project Manager, click the *Import* button to import the project."
msgstr ""

#: ../../docs/getting_started/step_by_step/instancing.rst:52
msgid ""
"In the pop-up that appears navigate to the folder you extracted. Double-"
"click the ``project.godot`` file to open it."
msgstr ""

#: ../../docs/getting_started/step_by_step/instancing.rst:57
msgid "Finally, click the Import & Edit button."
msgstr ""

#: ../../docs/getting_started/step_by_step/instancing.rst:61
msgid ""
"The project contains two packed scenes: ``main.tscn``, containing walls "
"against which the ball collides, and ``ball.tscn``. The Main scene should "
"open automatically. If you're seeing an empty 3D scene instead of the main "
"scene, click the 2D button at the top of the screen."
msgstr ""

#: ../../docs/getting_started/step_by_step/instancing.rst:69
msgid ""
"Let's add a ball as a child of the Main node. In the Scene dock, select the "
"Main node. Then, click the link icon at the top of the scene dock. This "
"button allows you to add an instance of a scene as a child of the currently "
"selected node."
msgstr ""

#: ../../docs/getting_started/step_by_step/instancing.rst:75
msgid "Double-click the ball scene to instance it."
msgstr ""

#: ../../docs/getting_started/step_by_step/instancing.rst:79
msgid "The ball appears in the top-left corner of the viewport."
msgstr ""

#: ../../docs/getting_started/step_by_step/instancing.rst:83
msgid "Click on it and drag it towards the center of the view."
msgstr ""

#: ../../docs/getting_started/step_by_step/instancing.rst:87
msgid ""
"Play the game by pressing :kbd:`F5` (:kbd:`Cmd + B` on macOS). You should "
"see it fall."
msgstr ""

#: ../../docs/getting_started/step_by_step/instancing.rst:89
msgid ""
"Now, we want to create more instances of the Ball node. With the ball still "
"selected, press :kbd:`Ctrl + D` (:kbd:`Cmd + D` on macOS) to call the "
"duplicate command. Click and drag to move the new ball to a different "
"location."
msgstr ""

#: ../../docs/getting_started/step_by_step/instancing.rst:95
msgid "You can repeat this process until you have several in the scene."
msgstr ""

#: ../../docs/getting_started/step_by_step/instancing.rst:99
msgid ""
"Play the game again. You should now see every ball fall independently from "
"one another. This is what instances do. Each is an independent reproduction "
"of a template scene."
msgstr ""

#: ../../docs/getting_started/step_by_step/instancing.rst:104
msgid "Editing scenes and instances"
msgstr ""

#: ../../docs/getting_started/step_by_step/instancing.rst:106
msgid "There is more to instances. With this feature, you can:"
msgstr ""

#: ../../docs/getting_started/step_by_step/instancing.rst:108
msgid ""
"Change the properties of one ball without affecting the others using the "
"Inspector."
msgstr ""

#: ../../docs/getting_started/step_by_step/instancing.rst:110
msgid ""
"Change the default properties of every Ball by opening the ``ball.tscn`` "
"scene and making a change to the Ball node there. Upon saving, all instances "
"of the Ball in the project will see their values update."
msgstr ""

#: ../../docs/getting_started/step_by_step/instancing.rst:114
msgid ""
"Changing a property on an instance always overrides values from the "
"corresponding packed scene."
msgstr ""

#: ../../docs/getting_started/step_by_step/instancing.rst:117
msgid ""
"Let's try this. Open ``ball.tscn`` and select the Ball node. In the "
"Inspector on the right, click on the PhysicsMaterial property to expand it."
msgstr ""

#: ../../docs/getting_started/step_by_step/instancing.rst:122
msgid ""
"Set its Bounce property to ``0.5`` by clicking on the number field, typing "
"``0.5``, and pressing :kbd:`Enter`."
msgstr ""

#: ../../docs/getting_started/step_by_step/instancing.rst:127
msgid ""
"Play the game by pressing :kbd:`F5` (:kbd:`Cmd + B` on macOS) and notice how "
"all balls now bounce a lot more. As the Ball scene is a template for all "
"instances, modifying it and saving causes all instances to update "
"accordingly."
msgstr ""

#: ../../docs/getting_started/step_by_step/instancing.rst:131
msgid ""
"Let's now adjust an individual instance. Head back to the Main scene by "
"clicking on the corresponding tab above the viewport."
msgstr ""

#: ../../docs/getting_started/step_by_step/instancing.rst:136
msgid ""
"Select one of the instanced Ball nodes and, in the Inspector, set its "
"Gravity Scale value to ``10``."
msgstr ""

#: ../../docs/getting_started/step_by_step/instancing.rst:141
msgid "A grey \"revert\" button appears next to the adjusted property."
msgstr ""

#: ../../docs/getting_started/step_by_step/instancing.rst:145
msgid ""
"This icon indicates you are overriding a value from the source packed scene. "
"Even if you modify the property in the original scene, the value override "
"will be preserved in the instance. Clicking the revert icon will restore the "
"property to the value in the saved scene."
msgstr ""

#: ../../docs/getting_started/step_by_step/instancing.rst:150
msgid ""
"Rerun the game and notice how this ball now falls much faster than the "
"others."
msgstr ""

#: ../../docs/getting_started/step_by_step/instancing.rst:152
msgid ""
"You may notice you are unable to change the values of the "
"``PhysicsMaterial`` of the ball. This is because ``PhysicsMaterial`` is a "
"resource, and needs to be made unique before you can edit it in a scene that "
"is linking to its original scene. To make a resource unique for one "
"instance, right-click on it in the Inspector and click Make Unique in the "
"contextual menu."
msgstr ""

#: ../../docs/getting_started/step_by_step/instancing.rst:158
msgid ""
"Resources are another essential building block of Godot games we will cover "
"in a later lesson."
msgstr ""

#: ../../docs/getting_started/step_by_step/instancing.rst:162
msgid "Scene instances as a design language"
msgstr ""

#: ../../docs/getting_started/step_by_step/instancing.rst:164
msgid ""
"Instances and scenes in Godot offer an excellent design language, setting "
"the engine apart from others out there. We designed Godot around this "
"concept from the ground up."
msgstr ""

#: ../../docs/getting_started/step_by_step/instancing.rst:168
msgid ""
"We recommend dismissing architectural code patterns when making games with "
"Godot, such as Model-View-Controller (MVC) or Entity-Relationship diagrams. "
"Instead, you can start by imagining the elements players will see in your "
"game and structure your code around them."
msgstr ""

#: ../../docs/getting_started/step_by_step/instancing.rst:173
msgid "For example, you could break down a shooter game like so:"
msgstr ""

#: ../../docs/getting_started/step_by_step/instancing.rst:177
msgid ""
"You can come up with a diagram like this for almost any type of game. Each "
"rectangle represents an entity that's visible in the game from the player's "
"perspective. The arrows tell you which scene owns which."
msgstr ""

#: ../../docs/getting_started/step_by_step/instancing.rst:181
msgid ""
"Once you have a diagram, we recommend creating a scene for each element "
"listed in it to develop your game. You'll use instancing, either by code or "
"directly in the editor, to build your tree of scenes."
msgstr ""

#: ../../docs/getting_started/step_by_step/instancing.rst:185
msgid ""
"Programmers tend to spend a lot of time designing abstract architectures and "
"trying to fit components into it. Designing based on scenes makes "
"development faster and more straightforward, allowing you to focus on the "
"game logic itself. Because most game components map directly to a scene, "
"using a design based on scene instantiation means you need little other "
"architectural code."
msgstr ""

#: ../../docs/getting_started/step_by_step/instancing.rst:191
msgid ""
"Here's the example of a scene diagram for an open-world game with tons of "
"assets and nested elements:"
msgstr ""

#: ../../docs/getting_started/step_by_step/instancing.rst:196
msgid ""
"Imagine we started by creating the room. We could make a couple of different "
"room scenes, with unique arrangements of furniture in them. Later, we could "
"make a house scene that uses multiple room instances for the interior. We "
"would create a citadel out of many instanced houses and a large terrain on "
"which we would place the citadel. Each of these would be a scene instancing "
"one or more sub-scenes."
msgstr ""

#: ../../docs/getting_started/step_by_step/instancing.rst:202
msgid ""
"Later, we could create scenes representing guards and add them to the "
"citadel. They would be indirectly added to the overall game world."
msgstr ""

#: ../../docs/getting_started/step_by_step/instancing.rst:205
msgid ""
"With Godot, it's easy to iterate on your game like this, as all you need to "
"do is create and instantiate more scenes. We designed the editor to be "
"accessible to programmers, designers, and artists alike. A typical team "
"development process can involve 2D or 3D artists, level designers, game "
"designers, and animators, all working with the Godot editor."
msgstr ""

#: ../../docs/getting_started/step_by_step/instancing.rst:214
msgid ""
"Instancing, the process of producing an object from a blueprint, has many "
"handy uses. With scenes, it gives you:"
msgstr ""

#: ../../docs/getting_started/step_by_step/instancing.rst:217
msgid "The ability to divide your game into reusable components."
msgstr ""

#: ../../docs/getting_started/step_by_step/instancing.rst:218
msgid "A tool to structure and encapsulate complex systems."
msgstr ""

#: ../../docs/getting_started/step_by_step/instancing.rst:219
msgid ""
"A language to think about your game project's structure in a natural way."
msgstr ""

#: ../../docs/getting_started/step_by_step/scripting_languages.rst:9
msgid "Scripting languages"
msgstr ""

#: ../../docs/getting_started/step_by_step/scripting_languages.rst:11
msgid ""
"This lesson will give you an overview of the available scripting languages "
"in Godot. You will learn the pros and cons of each option. In the next part, "
"you will write your first script using GDScript."
msgstr ""

#: ../../docs/getting_started/step_by_step/scripting_languages.rst:15
msgid ""
"**Scripts attach to a node and extend its behavior**. This means that "
"scripts inherit all functions and properties of the node they attach to."
msgstr ""

#: ../../docs/getting_started/step_by_step/scripting_languages.rst:18
msgid ""
"For example, take a game where a Camera2D node follows a ship. The Camera2D "
"node follows its parent by default. Imagine you want the camera to shake "
"when the player takes damage. As this feature is not built into Godot, you "
"would attach a script to the Camera2D node and code the shake."
msgstr ""

#: ../../docs/getting_started/step_by_step/scripting_languages.rst:26
msgid "Available scripting languages"
msgstr ""

#: ../../docs/getting_started/step_by_step/scripting_languages.rst:28
msgid ""
"Godot offers **four gameplay programming languages**: GDScript, C#, and, via "
"its GDExtension technology, C and C++. There are more community-supported "
"languages, but these are the official ones."
msgstr ""

#: ../../docs/getting_started/step_by_step/scripting_languages.rst:32
msgid ""
"You can use multiple languages in a single project. For instance, in a team, "
"you could code gameplay logic in GDScript as it's fast to write, and use C# "
"or C++ to implement complex algorithms and maximize their performance. Or "
"you can write everything in GDScript or C#. It's your call."
msgstr ""

#: ../../docs/getting_started/step_by_step/scripting_languages.rst:37
msgid ""
"We provide this flexibility to answer the needs of different game projects "
"and developers."
msgstr ""

#: ../../docs/getting_started/step_by_step/scripting_languages.rst:41
msgid "Which language should I use?"
msgstr ""

#: ../../docs/getting_started/step_by_step/scripting_languages.rst:43
msgid ""
"If you're a beginner, we recommend to **start with GDScript**. We made this "
"language specifically for Godot and the needs of game developers. It has a "
"lightweight and straightforward syntax and provides the tightest integration "
"with Godot."
msgstr ""

#: ../../docs/getting_started/step_by_step/scripting_languages.rst:50
msgid ""
"For C#, you will need an external code editor like `VSCode <https://code."
"visualstudio.com/>`_ or Visual Studio. While C# support is now mature, you "
"will find fewer learning resources for it compared to GDScript. That's why "
"we recommend C# mainly to users who already have experience with the "
"language."
msgstr ""

#: ../../docs/getting_started/step_by_step/scripting_languages.rst:56
msgid "Let's look at each language's features, as well as its pros and cons."
msgstr ""

#: ../../docs/getting_started/step_by_step/scripting_languages.rst:61
msgid ""
":ref:`GDScript<doc_gdscript>` is an `object-oriented <https://en.wikipedia."
"org/wiki/Object-oriented_programming>`_ and `imperative <https://en."
"wikipedia.org/wiki/Imperative_programming>`_ programming language built for "
"Godot. It's made by and for game developers to save you time coding games. "
"Its features include:"
msgstr ""

#: ../../docs/getting_started/step_by_step/scripting_languages.rst:67
msgid "A simple syntax that leads to short files."
msgstr ""

#: ../../docs/getting_started/step_by_step/scripting_languages.rst:68
msgid "Blazing fast compilation and loading times."
msgstr ""

#: ../../docs/getting_started/step_by_step/scripting_languages.rst:69
msgid ""
"Tight editor integration, with code completion for nodes, signals, and more "
"information from the scene it's attached to."
msgstr ""

#: ../../docs/getting_started/step_by_step/scripting_languages.rst:71
msgid ""
"Built-in vector and transform types, making it efficient for heavy use of "
"linear algebra, a must for games."
msgstr ""

#: ../../docs/getting_started/step_by_step/scripting_languages.rst:73
msgid "Supports multiple threads as efficiently as statically typed languages."
msgstr ""

#: ../../docs/getting_started/step_by_step/scripting_languages.rst:74
msgid ""
"No `garbage collection <https://en.wikipedia.org/wiki/"
"Garbage_collection_(computer_science)>`_, as this feature eventually gets in "
"the way when creating games. The engine counts references and manages the "
"memory for you in most cases by default, but you can also control memory if "
"you need to."
msgstr ""

#: ../../docs/getting_started/step_by_step/scripting_languages.rst:79
msgid ""
"`Gradual typing <https://en.wikipedia.org/wiki/Gradual_typing>`_. Variables "
"have dynamic types by default, but you also can use type hints for strong "
"type checks."
msgstr ""

#: ../../docs/getting_started/step_by_step/scripting_languages.rst:83
msgid ""
"GDScript looks like Python as you structure your code blocks using "
"indentations, but it doesn't work the same way in practice. It's inspired by "
"multiple languages, including Squirrel, Lua, and Python."
msgstr ""

#: ../../docs/getting_started/step_by_step/scripting_languages.rst:89
msgid "Why don't we use Python or Lua directly?"
msgstr ""

#: ../../docs/getting_started/step_by_step/scripting_languages.rst:91
msgid ""
"Years ago, Godot used Python, then Lua. Both languages' integration took a "
"lot of work and had severe limitations. For example, threading support was a "
"big challenge with Python."
msgstr ""

#: ../../docs/getting_started/step_by_step/scripting_languages.rst:95
msgid ""
"Developing a dedicated language doesn't take us more work and we can tailor "
"it to game developers' needs. We're now working on performance optimizations "
"and features that would've been difficult to offer with third-party "
"languages."
msgstr ""

#: ../../docs/getting_started/step_by_step/scripting_languages.rst:101
msgid ".NET / C#"
msgstr ""

#: ../../docs/getting_started/step_by_step/scripting_languages.rst:103
msgid ""
"As Microsoft's `C# <https://en.wikipedia.org/wiki/"
"C_Sharp_(programming_language)>`_ is a favorite amongst game developers, we "
"officially support it. C# is a mature and flexible language with tons of "
"libraries written for it. We were able to add support for it thanks to a "
"generous donation from Microsoft."
msgstr ""

#: ../../docs/getting_started/step_by_step/scripting_languages.rst:111
msgid ""
"C# offers a good tradeoff between performance and ease of use, although you "
"should be aware of its garbage collector."
msgstr ""

#: ../../docs/getting_started/step_by_step/scripting_languages.rst:114
msgid ""
"You must use the .NET edition of the Godot editor to script in C#. You can "
"download it on the Godot website's `download <https://godotengine.org/"
"download/>`_ page."
msgstr ""

#: ../../docs/getting_started/step_by_step/scripting_languages.rst:118
msgid ""
"Since Godot uses .NET 6, in theory, you can use any third-party .NET library "
"or framework in Godot, as well as any Common Language Infrastructure-"
"compliant programming language, such as F#, Boo, or ClojureCLR. However, C# "
"is the only officially supported .NET option."
msgstr ""

#: ../../docs/getting_started/step_by_step/scripting_languages.rst:123
msgid ""
"GDScript code itself doesn't execute as fast as compiled C# or C++. However, "
"most script code calls functions written with fast algorithms in C++ code "
"inside the engine. In many cases, writing gameplay logic in GDScript, C#, or "
"C++ won't have a significant impact on performance."
msgstr ""

#: ../../docs/getting_started/step_by_step/scripting_languages.rst:137
msgid "C++ via GDExtension"
msgstr ""

#: ../../docs/getting_started/step_by_step/scripting_languages.rst:139
msgid ""
"GDExtension allows you to write game code in C++ without needing to "
"recompile Godot."
msgstr ""

#: ../../docs/getting_started/step_by_step/scripting_languages.rst:144
msgid ""
"You can use any version of the language or mix compiler brands and versions "
"for the generated shared libraries, thanks to our use of an internal C API "
"Bridge."
msgstr ""

#: ../../docs/getting_started/step_by_step/scripting_languages.rst:147
msgid ""
"GDExtension is the best choice for performance. You don't need to use it "
"throughout an entire game, as you can write other parts in GDScript or C#."
msgstr ""

#: ../../docs/getting_started/step_by_step/scripting_languages.rst:150
msgid ""
"When working with GDExtension, the available types, functions, and "
"properties closely resemble Godot's actual C++ API."
msgstr ""

#: ../../docs/getting_started/step_by_step/scripting_languages.rst:156
msgid ""
"Scripts are files containing code that you attach to a node to extend its "
"functionality."
msgstr ""

#: ../../docs/getting_started/step_by_step/scripting_languages.rst:159
msgid ""
"Godot supports four official scripting languages, offering you flexibility "
"between performance and ease of use."
msgstr ""

#: ../../docs/getting_started/step_by_step/scripting_languages.rst:162
msgid ""
"You can mix languages, for instance, to implement demanding algorithms with "
"C or C++ and write most of the game logic with GDScript or C#."
msgstr ""

#: ../../docs/getting_started/step_by_step/scripting_first_script.rst:19
#, fuzzy
msgid "Creating your first script"
msgstr "Kreiranje Sadržaja"

#: ../../docs/getting_started/step_by_step/scripting_first_script.rst:21
msgid ""
"In this lesson, you will code your first script to make the Godot icon turn "
"in circles using GDScript. As we mentioned :ref:`in the introduction <toc-"
"learn-introduction>`, we assume you have programming foundations. The "
"equivalent C# code has been included in another tab for convenience."
msgstr ""

#: ../../docs/getting_started/step_by_step/scripting_first_script.rst:28
msgid ""
"To learn more about GDScript, its keywords, and its syntax, head to the :ref:"
"`GDScript reference<doc_gdscript>`."
msgstr ""

#: ../../docs/getting_started/step_by_step/scripting_first_script.rst:31
msgid ""
"To learn more about C#, head to the :ref:`C# basics <doc_c_sharp>` page."
msgstr ""

#: ../../docs/getting_started/step_by_step/scripting_first_script.rst:34
msgid "Project setup"
msgstr ""

#: ../../docs/getting_started/step_by_step/scripting_first_script.rst:36
msgid ""
"Please :ref:`create a new project <doc_creating_and_importing_projects>` to "
"start with a clean slate. Your project should contain one picture: the Godot "
"icon, which we often use for prototyping in the community."
msgstr ""

#: ../../docs/getting_started/step_by_step/scripting_first_script.rst:42
msgid ""
"We need to create a Sprite2D node to display it in the game. In the Scene "
"dock, click the Other Node button."
msgstr ""

#: ../../docs/getting_started/step_by_step/scripting_first_script.rst:47
msgid ""
"Type \"Sprite2D\" in the search bar to filter nodes and double-click on "
"Sprite2D to create the node."
msgstr ""

#: ../../docs/getting_started/step_by_step/scripting_first_script.rst:52
msgid "Your Scene tab should now only have a Sprite2D node."
msgstr ""

#: ../../docs/getting_started/step_by_step/scripting_first_script.rst:56
msgid ""
"A Sprite2D node needs a texture to display. In the Inspector on the right, "
"you can see that the Texture property says \"[empty]\". To display the Godot "
"icon, click and drag the file ``icon.svg`` from the FileSystem dock onto the "
"Texture slot."
msgstr ""

#: ../../docs/getting_started/step_by_step/scripting_first_script.rst:65
msgid ""
"You can create Sprite2D nodes automatically by dragging and dropping images "
"on the viewport."
msgstr ""

#: ../../docs/getting_started/step_by_step/scripting_first_script.rst:68
msgid ""
"Then, click and drag the icon in the viewport to center it in the game view."
msgstr ""

#: ../../docs/getting_started/step_by_step/scripting_first_script.rst:73
#, fuzzy
msgid "Creating a new script"
msgstr "Kreiranje Sadržaja"

#: ../../docs/getting_started/step_by_step/scripting_first_script.rst:75
msgid ""
"To create and attach a new script to our node, right-click on Sprite2D in "
"the scene dock and select \"Attach Script\"."
msgstr ""

#: ../../docs/getting_started/step_by_step/scripting_first_script.rst:80
msgid ""
"The Attach Node Script window appears. It allows you to select the script's "
"language and file path, among other options."
msgstr ""

#: ../../docs/getting_started/step_by_step/scripting_first_script.rst:83
msgid ""
"Change the Template field from \"Node: Default\" to \"Object: Empty\" to "
"start with a clean file. Leave the other options set to their default values "
"and click the Create button to create the script."
msgstr ""

#: ../../docs/getting_started/step_by_step/scripting_first_script.rst:90
msgid ""
"C# script names need to match their class name. In this case, you should "
"name the file ``MySprite2D.cs``."
msgstr ""

#: ../../docs/getting_started/step_by_step/scripting_first_script.rst:93
msgid ""
"The Script workspace should appear with your new ``sprite_2d.gd`` file open "
"and the following line of code:"
msgstr ""

#: ../../docs/getting_started/step_by_step/scripting_first_script.rst:109
msgid ""
"Every GDScript file is implicitly a class. The ``extends`` keyword defines "
"the class this script inherits or extends. In this case, it's ``Sprite2D``, "
"meaning our script will get access to all the properties and functions of "
"the Sprite2D node, including classes it extends, like ``Node2D``, "
"``CanvasItem``, and ``Node``."
msgstr ""

#: ../../docs/getting_started/step_by_step/scripting_first_script.rst:115
msgid ""
"In GDScript, if you omit the line with the ``extends`` keyword, your class "
"will implicitly extend :ref:`RefCounted <class_RefCounted>`, which Godot "
"uses to manage your application's memory."
msgstr ""

#: ../../docs/getting_started/step_by_step/scripting_first_script.rst:119
msgid ""
"Inherited properties include the ones you can see in the Inspector dock, "
"like our node's ``texture``."
msgstr ""

#: ../../docs/getting_started/step_by_step/scripting_first_script.rst:124
msgid ""
"By default, the Inspector displays a node's properties in \"Title Case\", "
"with capitalized words separated by a space. In GDScript code, these "
"properties are in \"snake_case\", which is lowercase with words separated by "
"an underscore."
msgstr ""

#: ../../docs/getting_started/step_by_step/scripting_first_script.rst:128
msgid ""
"You can hover over any property's name in the Inspector to see a description "
"and its identifier in code."
msgstr ""

#: ../../docs/getting_started/step_by_step/scripting_first_script.rst:132
msgid "Hello, world!"
msgstr ""

#: ../../docs/getting_started/step_by_step/scripting_first_script.rst:134
msgid ""
"Our script currently doesn't do anything. Let's make it print the text "
"\"Hello, world!\" to the Output bottom panel to get started."
msgstr ""

#: ../../docs/getting_started/step_by_step/scripting_first_script.rst:137
msgid "Add the following code to your script:"
msgstr ""

#: ../../docs/getting_started/step_by_step/scripting_first_script.rst:153
msgid ""
"Let's break it down. The ``func`` keyword defines a new function named "
"``_init``. This is a special name for our class's constructor. The engine "
"calls ``_init()`` on every object or node upon creating it in memory, if you "
"define this function."
msgstr ""

#: ../../docs/getting_started/step_by_step/scripting_first_script.rst:158
msgid ""
"GDScript is an indent-based language. The tab at the start of the line that "
"says ``print()`` is necessary for the code to work. If you omit it or don't "
"indent a line correctly, the editor will highlight it in red and display the "
"following error message: \"Indented block expected\"."
msgstr ""

#: ../../docs/getting_started/step_by_step/scripting_first_script.rst:163
msgid ""
"Save the scene as ``sprite_2d.tscn`` if you haven't already, then press :kbd:"
"`F6` (:kbd:`Cmd + R` on macOS) to run it. Look at the **Output** bottom "
"panel that expands. It should display \"Hello, world!\"."
msgstr ""

#: ../../docs/getting_started/step_by_step/scripting_first_script.rst:169
msgid ""
"Delete the ``_init()`` function, so you're only left with the line ``extends "
"Sprite2D``."
msgstr ""

#: ../../docs/getting_started/step_by_step/scripting_first_script.rst:173
msgid "Turning around"
msgstr ""

#: ../../docs/getting_started/step_by_step/scripting_first_script.rst:175
msgid ""
"It's time to make our node move and rotate. To do so, we're going to add two "
"member variables to our script: the movement speed in pixels per second and "
"the angular speed in radians per second.  Add the following after the "
"``extends Sprite2D`` line."
msgstr ""

#: ../../docs/getting_started/step_by_step/scripting_first_script.rst:190
msgid ""
"Member variables sit near the top of the script, after any \"extends\" "
"lines, but before functions. Every node instance with this script attached "
"to it will have its own copy of the ``speed`` and ``angular_speed`` "
"properties."
msgstr ""

#: ../../docs/getting_started/step_by_step/scripting_first_script.rst:195
msgid ""
"Angles in Godot work in radians by default, but you have built-in functions "
"and properties available if you prefer to calculate angles in degrees "
"instead."
msgstr ""

#: ../../docs/getting_started/step_by_step/scripting_first_script.rst:199
msgid ""
"To move our icon, we need to update its position and rotation every frame in "
"the game loop. We can use the ``_process()`` virtual function of the "
"``Node`` class. If you define it in any class that extends the Node class, "
"like Sprite2D, Godot will call the function every frame and pass it an "
"argument named ``delta``, the time elapsed since the last frame."
msgstr ""

#: ../../docs/getting_started/step_by_step/scripting_first_script.rst:207
msgid ""
"Games work by rendering many images per second, each called a frame, and "
"they do so in a loop. We measure the rate at which a game produces images in "
"Frames Per Second (FPS). Most games aim for 60 FPS, although you might find "
"figures like 30 FPS on slower mobile devices or 90 to 240 for virtual "
"reality games."
msgstr ""

#: ../../docs/getting_started/step_by_step/scripting_first_script.rst:213
msgid ""
"The engine and game developers do their best to update the game world and "
"render images at a constant time interval, but there are always small "
"variations in frame render times. That's why the engine provides us with "
"this delta time value, making our motion independent of our framerate."
msgstr ""

#: ../../docs/getting_started/step_by_step/scripting_first_script.rst:218
msgid "At the bottom of the script, define the function:"
msgstr ""

#: ../../docs/getting_started/step_by_step/scripting_first_script.rst:233
msgid ""
"The ``func`` keyword defines a new function. After it, we have to write the "
"function's name and arguments it takes in parentheses. A colon ends the "
"definition, and the indented blocks that follow are the function's content "
"or instructions."
msgstr ""

#: ../../docs/getting_started/step_by_step/scripting_first_script.rst:238
msgid ""
"Notice how ``_process()``, like ``_init()``, starts with a leading "
"underscore. By convention, Godot's virtual functions, that is to say, built-"
"in functions you can override to communicate with the engine, start with an "
"underscore."
msgstr ""

#: ../../docs/getting_started/step_by_step/scripting_first_script.rst:243
msgid ""
"The line inside the function, ``rotation += angular_speed * delta``, "
"increments our sprite's rotation every frame. Here, ``rotation`` is a "
"property inherited from the class ``Node2D``, which ``Sprite2D`` extends. It "
"controls the rotation of our node and works with radians."
msgstr ""

#: ../../docs/getting_started/step_by_step/scripting_first_script.rst:248
msgid ""
"In the code editor, you can ctrl-click on any built-in property or function "
"like ``position``, ``rotation``, or ``_process`` to open the corresponding "
"documentation in a new tab."
msgstr ""

#: ../../docs/getting_started/step_by_step/scripting_first_script.rst:252
msgid "Run the scene to see the Godot icon turn in-place."
msgstr ""

#: ../../docs/getting_started/step_by_step/scripting_first_script.rst:256
msgid ""
"In C#, notice how the ``delta`` argument taken by ``_Process()`` is a "
"``double``. We therefore need to convert it to ``float`` when we apply it to "
"the rotation."
msgstr ""

#: ../../docs/getting_started/step_by_step/scripting_first_script.rst:261
msgid "Moving forward"
msgstr ""

#: ../../docs/getting_started/step_by_step/scripting_first_script.rst:263
msgid ""
"Let's now make the node move. Add the following two lines inside of the "
"``_process()`` function, ensuring the new lines are indented the same way as "
"the ``rotation += angular_speed * delta`` line before them."
msgstr ""

#: ../../docs/getting_started/step_by_step/scripting_first_script.rst:280
msgid ""
"As we already saw, the ``var`` keyword defines a new variable. If you put it "
"at the top of the script, it defines a property of the class. Inside a "
"function, it defines a local variable: it only exists within the function's "
"scope."
msgstr ""

#: ../../docs/getting_started/step_by_step/scripting_first_script.rst:284
msgid ""
"We define a local variable named ``velocity``, a 2D vector representing both "
"a direction and a speed. To make the node move forward, we start from the "
"Vector2 class's constant ``Vector2.UP``, a vector pointing up, and rotate it "
"by calling the Vector2 method ``rotated()``. This expression, ``Vector2.UP."
"rotated(rotation)``, is a vector pointing forward relative to our icon. "
"Multiplied by our ``speed`` property, it gives us a velocity we can use to "
"move the node forward."
msgstr ""

#: ../../docs/getting_started/step_by_step/scripting_first_script.rst:291
msgid ""
"We add ``velocity * delta`` to the node's ``position`` to move it. The "
"position itself is of type :ref:`Vector2 <class_Vector2>`, a built-in type "
"in Godot representing a 2D vector."
msgstr ""

#: ../../docs/getting_started/step_by_step/scripting_first_script.rst:295
msgid "Run the scene to see the Godot head run in circles."
msgstr ""

#: ../../docs/getting_started/step_by_step/scripting_first_script.rst:299
msgid ""
"Moving a node like that does not take into account colliding with walls or "
"the floor. In :ref:`doc_your_first_2d_game`, you will learn another approach "
"to moving objects while detecting collisions."
msgstr ""

#: ../../docs/getting_started/step_by_step/scripting_first_script.rst:303
msgid ""
"Our node currently moves by itself. In the next part, :ref:"
"`doc_scripting_player_input`, we'll use player input to control it."
msgstr ""

#: ../../docs/getting_started/step_by_step/scripting_first_script.rst:307
#: ../../docs/getting_started/step_by_step/scripting_player_input.rst:113
#: ../../docs/getting_started/step_by_step/signals.rst:342
#, fuzzy
msgid "Complete script"
msgstr "Kreiranje Sadržaja"

#: ../../docs/getting_started/step_by_step/scripting_first_script.rst:309
#: ../../docs/getting_started/step_by_step/scripting_player_input.rst:115
msgid "Here is the complete ``sprite_2d.gd`` file for reference."
msgstr ""

#: ../../docs/getting_started/step_by_step/scripting_player_input.rst:8
msgid "Listening to player input"
msgstr ""

#: ../../docs/getting_started/step_by_step/scripting_player_input.rst:10
msgid ""
"Building upon the previous lesson, :ref:`doc_scripting_first_script`, let's "
"look at another important feature of any game: giving control to the player. "
"To add this, we need to modify our ``sprite_2d.gd`` code."
msgstr ""

#: ../../docs/getting_started/step_by_step/scripting_player_input.rst:16
msgid "You have two main tools to process the player's input in Godot:"
msgstr ""

#: ../../docs/getting_started/step_by_step/scripting_player_input.rst:18
msgid ""
"The built-in input callbacks, mainly ``_unhandled_input()``. Like "
"``_process()``, it's a built-in virtual function that Godot calls every time "
"the player presses a key. It's the tool you want to use to react to events "
"that don't happen every frame, like pressing :kbd:`Space` to jump. To learn "
"more about input callbacks, see :ref:`doc_inputevent`."
msgstr ""

#: ../../docs/getting_started/step_by_step/scripting_player_input.rst:23
msgid ""
"The ``Input`` singleton. A singleton is a globally accessible object. Godot "
"provides access to several in scripts. It's the right tool to check for "
"input every frame."
msgstr ""

#: ../../docs/getting_started/step_by_step/scripting_player_input.rst:27
msgid ""
"We're going to use the ``Input`` singleton here as we need to know if the "
"player wants to turn or move every frame."
msgstr ""

#: ../../docs/getting_started/step_by_step/scripting_player_input.rst:30
msgid ""
"For turning, we should use a new variable: ``direction``. In our "
"``_process()`` function, replace the ``rotation += angular_speed * delta`` "
"line with the code below."
msgstr ""

#: ../../docs/getting_started/step_by_step/scripting_player_input.rst:59
msgid ""
"Our ``direction`` local variable is a multiplier representing the direction "
"in which the player wants to turn. A value of ``0`` means the player isn't "
"pressing the left or the right arrow key. A value of ``1`` means the player "
"wants to turn right, and ``-1`` means they want to turn left."
msgstr ""

#: ../../docs/getting_started/step_by_step/scripting_player_input.rst:64
msgid ""
"To produce these values, we introduce conditions and the use of ``Input``. A "
"condition starts with the ``if`` keyword in GDScript and ends with a colon. "
"The condition is the expression between the keyword and the end of the line."
msgstr ""

#: ../../docs/getting_started/step_by_step/scripting_player_input.rst:68
msgid ""
"To check if a key was pressed this frame, we call ``Input."
"is_action_pressed()``. The method takes a text string representing an input "
"action and returns ``true`` if the action is pressed, ``false`` otherwise."
msgstr ""

#: ../../docs/getting_started/step_by_step/scripting_player_input.rst:72
msgid ""
"The two actions we use above, \"ui_left\" and \"ui_right\", are predefined "
"in every Godot project. They respectively trigger when the player presses "
"the left and right arrows on the keyboard or left and right on a gamepad's D-"
"pad."
msgstr ""

#: ../../docs/getting_started/step_by_step/scripting_player_input.rst:76
msgid ""
"You can see and edit input actions in your project by going to Project -> "
"Project Settings and clicking on the Input Map tab."
msgstr ""

#: ../../docs/getting_started/step_by_step/scripting_player_input.rst:79
msgid ""
"Finally, we use the ``direction`` as a multiplier when we update the node's "
"``rotation``: ``rotation += angular_speed * direction * delta``."
msgstr ""

#: ../../docs/getting_started/step_by_step/scripting_player_input.rst:82
msgid ""
"If you run the scene with this code, the icon should rotate when you press :"
"kbd:`Left` and :kbd:`Right`."
msgstr ""

#: ../../docs/getting_started/step_by_step/scripting_player_input.rst:86
msgid "Moving when pressing \"up\""
msgstr ""

#: ../../docs/getting_started/step_by_step/scripting_player_input.rst:88
msgid ""
"To only move when pressing a key, we need to modify the code that calculates "
"the velocity. Replace the line starting with ``var velocity`` with the code "
"below."
msgstr ""

#: ../../docs/getting_started/step_by_step/scripting_player_input.rst:106
msgid ""
"We initialize the ``velocity`` with a value of ``Vector2.ZERO``, another "
"constant of the built-in ``Vector`` type representing a 2D vector of length "
"0."
msgstr ""

#: ../../docs/getting_started/step_by_step/scripting_player_input.rst:109
msgid ""
"If the player presses the \"ui_up\" action, we then update the velocity's "
"value, causing the sprite to move forward."
msgstr ""

#: ../../docs/getting_started/step_by_step/scripting_player_input.rst:174
msgid ""
"If you run the scene, you should now be able to rotate with the left and "
"right arrow keys and move forward by pressing :kbd:`Up`."
msgstr ""

#: ../../docs/getting_started/step_by_step/scripting_player_input.rst:182
msgid ""
"In summary, every script in Godot represents a class and extends one of the "
"engine's built-in classes. The node types your classes inherit from give you "
"access to properties, such as ``rotation`` and ``position`` in our sprite's "
"case. You also inherit many functions, which we didn't get to use in this "
"example."
msgstr ""

#: ../../docs/getting_started/step_by_step/scripting_player_input.rst:187
msgid ""
"In GDScript, the variables you put at the top of the file are your class's "
"properties, also called member variables. Besides variables, you can define "
"functions, which, for the most part, will be your classes' methods."
msgstr ""

#: ../../docs/getting_started/step_by_step/scripting_player_input.rst:191
msgid ""
"Godot provides several virtual functions you can define to connect your "
"class with the engine. These include ``_process()``, to apply changes to the "
"node every frame, and ``_unhandled_input()``, to receive input events like "
"key and button presses from the users. There are quite a few more."
msgstr ""

#: ../../docs/getting_started/step_by_step/scripting_player_input.rst:196
msgid ""
"The ``Input`` singleton allows you to react to the players' input anywhere "
"in your code. In particular, you'll get to use it in the ``_process()`` loop."
msgstr ""

#: ../../docs/getting_started/step_by_step/scripting_player_input.rst:199
msgid ""
"In the next lesson, :ref:`doc_signals`, we'll build upon the relationship "
"between scripts and nodes by having our nodes trigger code in scripts."
msgstr ""

#: ../../docs/getting_started/step_by_step/signals.rst:-1
#: ../../docs/tutorials/scripting/gdscript/gdscript_documentation_comments.rst:77
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:571
#: ../../docs/tutorials/scripting/instancing_with_signals.rst:-1
msgid "Signal"
msgstr ""

#: ../../docs/getting_started/step_by_step/signals.rst:12
#, fuzzy
msgid "Using signals"
msgstr "Kreiranje Sadržaja"

#: ../../docs/getting_started/step_by_step/signals.rst:14
msgid ""
"In this lesson, we will look at signals. They are messages that nodes emit "
"when something specific happens to them, like a button being pressed. Other "
"nodes can connect to that signal and call a function when the event occurs."
msgstr ""

#: ../../docs/getting_started/step_by_step/signals.rst:18
msgid ""
"Signals are a delegation mechanism built into Godot that allows one game "
"object to react to a change in another without them referencing one another. "
"Using signals limits `coupling <https://en.wikipedia.org/wiki/"
"Coupling_(computer_programming)>`_ and keeps your code flexible."
msgstr ""

#: ../../docs/getting_started/step_by_step/signals.rst:24
msgid ""
"For example, you might have a life bar on the screen that represents the "
"player's health. When the player takes damage or uses a healing potion, you "
"want the bar to reflect the change. To do so, in Godot, you would use "
"signals."
msgstr ""

#: ../../docs/getting_started/step_by_step/signals.rst:28
msgid ""
"As mentioned in the introduction, signals are Godot's version of the "
"observer pattern. You can learn more about it here: https://"
"gameprogrammingpatterns.com/observer.html"
msgstr ""

#: ../../docs/getting_started/step_by_step/signals.rst:32
msgid ""
"We will now use a signal to make our Godot icon from the previous lesson (:"
"ref:`doc_scripting_player_input`) move and stop by pressing a button."
msgstr ""

#: ../../docs/getting_started/step_by_step/signals.rst:38
#: ../../docs/tutorials/animation/introduction.rst:108
#: ../../docs/tutorials/physics/kinematic_character_2d.rst:77
msgid "Scene setup"
msgstr ""

#: ../../docs/getting_started/step_by_step/signals.rst:40
msgid ""
"To add a button to our game, we will create a new scene which will include "
"both a :ref:`Button <class_button>` and the ``sprite_2d.tscn`` scene we "
"created in the :ref:`doc_scripting_first_script` lesson."
msgstr ""

#: ../../docs/getting_started/step_by_step/signals.rst:44
msgid "Create a new scene by going to the menu Scene -> New Scene."
msgstr ""

#: ../../docs/getting_started/step_by_step/signals.rst:48
msgid ""
"In the Scene dock, click the 2D Scene button. This will add a :ref:`Node2D "
"<class_Node2D>` as our root."
msgstr ""

#: ../../docs/getting_started/step_by_step/signals.rst:53
msgid ""
"In the FileSystem dock, click and drag the ``sprite_2d.tscn`` file you saved "
"previously onto the Node2D to instantiate it."
msgstr ""

#: ../../docs/getting_started/step_by_step/signals.rst:58
msgid ""
"We want to add another node as a sibling of the Sprite2D. To do so, right-"
"click on Node2D and select Add Child Node."
msgstr ""

#: ../../docs/getting_started/step_by_step/signals.rst:63
msgid "Search for the :ref:`Button <class_button>` node and add it."
msgstr ""

#: ../../docs/getting_started/step_by_step/signals.rst:67
msgid ""
"The node is small by default. Click and drag on the bottom-right handle of "
"the Button in the viewport to resize it."
msgstr ""

#: ../../docs/getting_started/step_by_step/signals.rst:72
msgid ""
"If you don't see the handles, ensure the select tool is active in the "
"toolbar."
msgstr ""

#: ../../docs/getting_started/step_by_step/signals.rst:76
msgid "Click and drag on the button itself to move it closer to the sprite."
msgstr ""

#: ../../docs/getting_started/step_by_step/signals.rst:78
msgid ""
"You can also write a label on the Button by editing its Text property in the "
"Inspector. Enter ``Toggle motion``."
msgstr ""

#: ../../docs/getting_started/step_by_step/signals.rst:83
msgid "Your scene tree and viewport should look like this."
msgstr ""

#: ../../docs/getting_started/step_by_step/signals.rst:87
msgid ""
"Save your newly created scene as ``node_2d.tscn``, if you haven't already. "
"You can then run it with :kbd:`F6` (:kbd:`Cmd + R` on macOS). At the moment, "
"the button will be visible, but nothing will happen if you press it."
msgstr ""

#: ../../docs/getting_started/step_by_step/signals.rst:93
msgid "Connecting a signal in the editor"
msgstr ""

#: ../../docs/getting_started/step_by_step/signals.rst:95
msgid ""
"Here, we want to connect the Button's \"pressed\" signal to our Sprite2D, "
"and we want to call a new function that will toggle its motion on and off. "
"We need to have a script attached to the Sprite2D node, which we do from the "
"previous lesson."
msgstr ""

#: ../../docs/getting_started/step_by_step/signals.rst:100
msgid ""
"You can connect signals in the Node dock. Select the Button node and, on the "
"right side of the editor, click on the tab named \"Node\" next to the "
"Inspector."
msgstr ""

#: ../../docs/getting_started/step_by_step/signals.rst:105
msgid "The dock displays a list of signals available on the selected node."
msgstr ""

#: ../../docs/getting_started/step_by_step/signals.rst:109
msgid "Double-click the \"pressed\" signal to open the node connection window."
msgstr ""

#: ../../docs/getting_started/step_by_step/signals.rst:113
msgid ""
"There, you can connect the signal to the Sprite2D node. The node needs a "
"receiver method, a function that Godot will call when the Button emits the "
"signal. The editor generates one for you. By convention, we name these "
"callback methods \"_on_node_name_signal_name\". Here, it'll be "
"\"_on_button_pressed\"."
msgstr ""

#: ../../docs/getting_started/step_by_step/signals.rst:120
msgid ""
"When connecting signals via the editor's Node dock, you can use two modes. "
"The simple one only allows you to connect to nodes that have a script "
"attached to them and creates a new callback function on them."
msgstr ""

#: ../../docs/getting_started/step_by_step/signals.rst:126
msgid ""
"The advanced view lets you connect to any node and any built-in function, "
"add arguments to the callback, and set options. You can toggle the mode in "
"the window's bottom-right by clicking the Advanced button."
msgstr ""

#: ../../docs/getting_started/step_by_step/signals.rst:131
msgid ""
"Click the Connect button to complete the signal connection and jump to the "
"Script workspace. You should see the new method with a connection icon in "
"the left margin."
msgstr ""

#: ../../docs/getting_started/step_by_step/signals.rst:137
msgid ""
"If you click the icon, a window pops up and displays information about the "
"connection. This feature is only available when connecting nodes in the "
"editor."
msgstr ""

#: ../../docs/getting_started/step_by_step/signals.rst:142
msgid ""
"Let's replace the line with the ``pass`` keyword with code that'll toggle "
"the node's motion."
msgstr ""

#: ../../docs/getting_started/step_by_step/signals.rst:145
msgid ""
"Our Sprite2D moves thanks to code in the ``_process()`` function. Godot "
"provides a method to toggle processing on and off: :ref:`Node.set_process() "
"<class_Node_method_set_process>`. Another method of the Node class, "
"``is_processing()``, returns ``true`` if idle processing is active. We can "
"use the ``not`` keyword to invert the value."
msgstr ""

#: ../../docs/getting_started/step_by_step/signals.rst:164
msgid ""
"This function will toggle processing and, in turn, the icon's motion on and "
"off upon pressing the button."
msgstr ""

#: ../../docs/getting_started/step_by_step/signals.rst:167
msgid ""
"Before trying the game, we need to simplify our ``_process()`` function to "
"move the node automatically and not wait for user input. Replace it with the "
"following code, which we saw two lessons ago:"
msgstr ""

#: ../../docs/getting_started/step_by_step/signals.rst:188
msgid "Your complete ``sprite_2d.gd`` code should look like the following."
msgstr ""

#: ../../docs/getting_started/step_by_step/signals.rst:230
msgid ""
"Run the scene now and click the button to see the sprite start and stop."
msgstr ""

#: ../../docs/getting_started/step_by_step/signals.rst:233
#, fuzzy
msgid "Connecting a signal via code"
msgstr "Kreiranje Sadržaja"

#: ../../docs/getting_started/step_by_step/signals.rst:235
msgid ""
"You can connect signals via code instead of using the editor. This is "
"necessary when you create nodes or instantiate scenes inside of a script."
msgstr ""

#: ../../docs/getting_started/step_by_step/signals.rst:238
msgid ""
"Let's use a different node here. Godot has a :ref:`Timer <class_Timer>` node "
"that's useful to implement skill cooldown times, weapon reloading, and more."
msgstr ""

#: ../../docs/getting_started/step_by_step/signals.rst:241
msgid ""
"Head back to the 2D workspace. You can either click the \"2D\" text at the "
"top of the window or press :kbd:`Ctrl + F1` (:kbd:`Ctrl + Cmd + 1` on macOS)."
msgstr ""

#: ../../docs/getting_started/step_by_step/signals.rst:244
msgid ""
"In the Scene dock, right-click on the Sprite2D node and add a new child "
"node. Search for Timer and add the corresponding node. Your scene should now "
"look like this."
msgstr ""

#: ../../docs/getting_started/step_by_step/signals.rst:250
msgid ""
"With the Timer node selected, go to the Inspector and enable the "
"**Autostart** property."
msgstr ""

#: ../../docs/getting_started/step_by_step/signals.rst:255
msgid ""
"Click the script icon next to Sprite2D to jump back to the scripting "
"workspace."
msgstr ""

#: ../../docs/getting_started/step_by_step/signals.rst:259
msgid "We need to do two operations to connect the nodes via code:"
msgstr ""

#: ../../docs/getting_started/step_by_step/signals.rst:261
msgid "Get a reference to the Timer from the Sprite2D."
msgstr ""

#: ../../docs/getting_started/step_by_step/signals.rst:262
msgid "Call the ``connect()`` method on the Timer's \"timeout\" signal."
msgstr ""

#: ../../docs/getting_started/step_by_step/signals.rst:264
msgid ""
"To connect to a signal via code, you need to call the ``connect()`` method "
"of the signal you want to listen to. In this case, we want to listen to the "
"Timer's \"timeout\" signal."
msgstr ""

#: ../../docs/getting_started/step_by_step/signals.rst:268
msgid ""
"We want to connect the signal when the scene is instantiated, and we can do "
"that using the :ref:`Node._ready() <class_Node_private_method__ready>` built-"
"in function, which is called automatically by the engine when a node is "
"fully instantiated."
msgstr ""

#: ../../docs/getting_started/step_by_step/signals.rst:272
msgid ""
"To get a reference to a node relative to the current one, we use the method :"
"ref:`Node.get_node() <class_Node_method_get_node>`. We can store the "
"reference in a variable."
msgstr ""

#: ../../docs/getting_started/step_by_step/signals.rst:289
msgid ""
"The function ``get_node()`` looks at the Sprite2D's children and gets nodes "
"by their name. For example, if you renamed the Timer node to "
"\"BlinkingTimer\" in the editor, you would have to change the call to "
"``get_node(\"BlinkingTimer\")``."
msgstr ""

#: ../../docs/getting_started/step_by_step/signals.rst:295
msgid ""
"We can now connect the Timer to the Sprite2D in the ``_ready()`` function."
msgstr ""

#: ../../docs/getting_started/step_by_step/signals.rst:312
msgid ""
"The line reads like so: we connect the Timer's \"timeout\" signal to the "
"node to which the script is attached. When the Timer emits ``timeout``, we "
"want to call the function ``_on_timer_timeout()``, that we need to define. "
"Let's add it at the bottom of our script and use it to toggle our sprite's "
"visibility."
msgstr ""

#: ../../docs/getting_started/step_by_step/signals.rst:317
msgid ""
"By convention, we name these callback methods in GDScript as "
"\"_on_node_name_signal_name\" and in C# as \"OnNodeNameSignalName\". Here, "
"it'll be \"_on_timer_timeout\" for GDScript and OnTimerTimeout() for C#."
msgstr ""

#: ../../docs/getting_started/step_by_step/signals.rst:334
msgid ""
"The ``visible`` property is a boolean that controls the visibility of our "
"node. The line ``visible = not visible`` toggles the value. If ``visible`` "
"is ``true``, it becomes ``false``, and vice-versa."
msgstr ""

#: ../../docs/getting_started/step_by_step/signals.rst:338
msgid ""
"If you run the scene now, you will see that the sprite blinks on and off, at "
"one second intervals."
msgstr ""

#: ../../docs/getting_started/step_by_step/signals.rst:344
msgid ""
"That's it for our little moving and blinking Godot icon demo! Here is the "
"complete ``sprite_2d.gd`` file for reference."
msgstr ""

#: ../../docs/getting_started/step_by_step/signals.rst:408
msgid "Custom signals"
msgstr ""

#: ../../docs/getting_started/step_by_step/signals.rst:410
msgid ""
"This section is a reference on how to define and use your own signals, and "
"does not build upon the project created in previous lessons."
msgstr ""

#: ../../docs/getting_started/step_by_step/signals.rst:413
msgid ""
"You can define custom signals in a script. Say, for example, that you want "
"to show a game over screen when the player's health reaches zero. To do so, "
"you could define a signal named \"died\" or \"health_depleted\" when their "
"health reaches 0."
msgstr ""

#: ../../docs/getting_started/step_by_step/signals.rst:439
msgid ""
"As signals represent events that just occurred, we generally use an action "
"verb in the past tense in their names."
msgstr ""

#: ../../docs/getting_started/step_by_step/signals.rst:442
msgid ""
"Your signals work the same way as built-in ones: they appear in the Node tab "
"and you can connect to them like any other."
msgstr ""

#: ../../docs/getting_started/step_by_step/signals.rst:447
msgid "To emit a signal in your scripts, call ``emit()`` on the signal."
msgstr ""

#: ../../docs/getting_started/step_by_step/signals.rst:469
msgid ""
"A signal can optionally declare one or more arguments. Specify the argument "
"names between parentheses:"
msgstr ""

#: ../../docs/getting_started/step_by_step/signals.rst:495
msgid ""
"The signal arguments show up in the editor's node dock, and Godot can use "
"them to generate callback functions for you. However, you can still emit any "
"number of arguments when you emit signals. So it's up to you to emit the "
"correct values."
msgstr ""

#: ../../docs/getting_started/step_by_step/signals.rst:500
msgid ""
"To emit values along with the signal, add them as extra arguments to the "
"``emit()`` function:"
msgstr ""

#: ../../docs/getting_started/step_by_step/signals.rst:523
msgid ""
"Any node in Godot emits signals when something specific happens to them, "
"like a button being pressed. Other nodes can connect to individual signals "
"and react to selected events."
msgstr ""

#: ../../docs/getting_started/step_by_step/signals.rst:527
msgid ""
"Signals have many uses. With them, you can react to a node entering or "
"exiting the game world, to a collision, to a character entering or leaving "
"an area, to an element of the interface changing size, and much more."
msgstr ""

#: ../../docs/getting_started/step_by_step/signals.rst:531
msgid ""
"For example, an :ref:`Area2D <class_Area2D>` representing a coin emits a "
"``body_entered`` signal whenever the player's physics body enters its "
"collision shape, allowing you to know when the player collected it."
msgstr ""

#: ../../docs/getting_started/step_by_step/signals.rst:535
msgid ""
"In the next section, :ref:`doc_your_first_2d_game`, you'll create a complete "
"2D game and put everything you learned so far into practice."
msgstr ""

#: ../../docs/getting_started/first_2d_game/index.rst:4
msgid "Your first 2D game"
msgstr ""

#: ../../docs/getting_started/first_2d_game/index.rst:6
msgid ""
"In this step-by-step tutorial series, you will create your first complete 2D "
"game with Godot. By the end of the series, you will have a simple yet "
"complete game of your own, like the image below."
msgstr ""

#: ../../docs/getting_started/first_2d_game/index.rst:12
msgid ""
"You will learn how the Godot editor works, how to structure a project, and "
"build a 2D game."
msgstr ""

#: ../../docs/getting_started/first_2d_game/index.rst:15
msgid ""
"This project is an introduction to the Godot engine. It assumes that you "
"have some programming experience already. If you're new to programming "
"entirely, you should start here: :ref:`doc_scripting`."
msgstr ""

#: ../../docs/getting_started/first_2d_game/index.rst:19
msgid ""
"The game is called \"Dodge the Creeps!\". Your character must move and avoid "
"the enemies for as long as possible."
msgstr ""

#: ../../docs/getting_started/first_2d_game/index.rst:22
#: ../../docs/getting_started/first_3d_game/index.rst:19
msgid "You will learn to:"
msgstr ""

#: ../../docs/getting_started/first_2d_game/index.rst:24
msgid "Create a complete 2D game with the Godot editor."
msgstr ""

#: ../../docs/getting_started/first_2d_game/index.rst:25
#, fuzzy
msgid "Structure a simple game project."
msgstr "Kreiranje Sadržaja"

#: ../../docs/getting_started/first_2d_game/index.rst:26
msgid "Move the player character and change its sprite."
msgstr ""

#: ../../docs/getting_started/first_2d_game/index.rst:27
msgid "Spawn random enemies."
msgstr ""

#: ../../docs/getting_started/first_2d_game/index.rst:28
msgid "Count the score."
msgstr ""

#: ../../docs/getting_started/first_2d_game/index.rst:30
#: ../../docs/getting_started/first_3d_game/index.rst:30
msgid "And more."
msgstr ""

#: ../../docs/getting_started/first_2d_game/index.rst:32
msgid ""
"You'll find another series where you'll create a similar game but in 3D. We "
"recommend you to start with this one, though."
msgstr ""

#: ../../docs/getting_started/first_2d_game/index.rst:35
msgid "**Why start with 2D?**"
msgstr ""

#: ../../docs/getting_started/first_2d_game/index.rst:37
msgid ""
"If you are new to game development or unfamiliar with Godot, we recommend "
"starting with 2D games. This will allow you to become comfortable with both "
"before tackling 3D games, which tend to be more complicated."
msgstr ""

#: ../../docs/getting_started/first_2d_game/index.rst:41
msgid "You can find a completed version of this project at this location:"
msgstr ""

#: ../../docs/getting_started/first_2d_game/index.rst:43
#, fuzzy
msgid ""
"https://github.com/godotengine/godot-demo-projects/tree/master/2d/"
"dodge_the_creeps"
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati raznorazne `Godot demo projects "
"<https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/getting_started/first_2d_game/index.rst:46
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_basics.rst:36
msgid "Prerequisites"
msgstr ""

#: ../../docs/getting_started/first_2d_game/index.rst:48
msgid ""
"This step-by-step tutorial is intended for beginners who followed the "
"complete :ref:`Getting Started <toc-learn-step_by_step>`."
msgstr ""

#: ../../docs/getting_started/first_2d_game/index.rst:51
#, fuzzy
msgid ""
"If you're an experienced programmer, you can find the complete demo's source "
"code here: `Dodge the Creeps source code <https://github.com/godotengine/"
"godot-demo-projects/tree/master/2d/dodge_the_creeps>`__."
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati različite Godo demo projekte "
"`Godot demo projects <https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/getting_started/first_2d_game/index.rst:55
msgid ""
"We prepared some game assets you'll need to download so we can jump straight "
"to the code."
msgstr ""

#: ../../docs/getting_started/first_2d_game/index.rst:58
msgid "You can download them by clicking the link below."
msgstr ""

#: ../../docs/getting_started/first_2d_game/index.rst:60
msgid ""
"`dodge_the_creeps_2d_assets.zip <https://github.com/godotengine/godot-docs-"
"project-starters/releases/download/latest-4.x/dodge_the_creeps_2d_assets."
"zip>`_."
msgstr ""

#: ../../docs/getting_started/first_2d_game/index.rst:63
#: ../../docs/getting_started/first_3d_game/index.rst:55
msgid "Contents"
msgstr ""

#: ../../docs/getting_started/first_2d_game/01.project_setup.rst:4
#: ../../docs/tutorials/scripting/gdextension/gdextension_cpp_example.rst:18
msgid "Setting up the project"
msgstr ""

#: ../../docs/getting_started/first_2d_game/01.project_setup.rst:6
msgid "In this short first part, we'll set up and organize the project."
msgstr ""

#: ../../docs/getting_started/first_2d_game/01.project_setup.rst:8
#, fuzzy
msgid "Launch Godot and create a new project."
msgstr "Kreiranje Sadržaja"

#: ../../docs/getting_started/first_2d_game/01.project_setup.rst:12
msgid ""
"When creating the new project, you only need to choose a valid *Project "
"Path*. You can leave the other default settings alone."
msgstr ""

#: ../../docs/getting_started/first_2d_game/01.project_setup.rst:17
#: ../../docs/getting_started/first_2d_game/01.project_setup.rst:24
msgid ""
"Download `dodge_the_creeps_2d_assets.zip <https://github.com/godotengine/"
"godot-docs-project-starters/releases/download/latest-4.x/"
"dodge_the_creeps_2d_assets.zip>`_. The archive contains the images and "
"sounds you'll be using to make the game. Extract the archive and move the "
"``art/`` and ``fonts/`` directories to your project's directory."
msgstr ""

#: ../../docs/getting_started/first_2d_game/01.project_setup.rst:29
msgid ""
"Ensure that you have the required dependencies to use C# in Godot. You need "
"the latest stable .NET SDK, and an editor such as VS Code. See :ref:"
"`doc_c_sharp_setup`."
msgstr ""

#: ../../docs/getting_started/first_2d_game/01.project_setup.rst:35
msgid ""
"The C++ part of this tutorial wasn't rewritten for the new GDExtension "
"system yet."
msgstr ""

#: ../../docs/getting_started/first_2d_game/01.project_setup.rst:37
msgid "Your project folder should look like this."
msgstr ""

#: ../../docs/getting_started/first_2d_game/01.project_setup.rst:41
msgid ""
"This game is designed for portrait mode, so we need to adjust the size of "
"the game window. Click on *Project -> Project Settings* to open the project "
"settings window, in the left column open the *Display -> Window* tab. There, "
"set \"Viewport Width\" to ``480`` and \"Viewport Height\" to ``720``."
msgstr ""

#: ../../docs/getting_started/first_2d_game/01.project_setup.rst:48
msgid ""
"Also, under the **Stretch** options, set **Mode** to ``canvas_items`` and "
"**Aspect** to ``keep``. This ensures that the game scales consistently on "
"different sized screens."
msgstr ""

#: ../../docs/getting_started/first_2d_game/01.project_setup.rst:54
msgid "Organizing the project"
msgstr ""

#: ../../docs/getting_started/first_2d_game/01.project_setup.rst:56
msgid ""
"In this project, we will make 3 independent scenes: ``Player``, ``Mob``, and "
"``HUD``, which we will combine into the game's ``Main`` scene."
msgstr ""

#: ../../docs/getting_started/first_2d_game/01.project_setup.rst:59
msgid ""
"In a larger project, it might be useful to create folders to hold the "
"various scenes and their scripts, but for this relatively small game, you "
"can save your scenes and scripts in the project's root folder, identified by "
"``res://``. You can see your project folders in the FileSystem dock in the "
"lower left corner:"
msgstr ""

#: ../../docs/getting_started/first_2d_game/01.project_setup.rst:66
msgid ""
"With the project in place, we're ready to design the player scene in the "
"next lesson."
msgstr ""

#: ../../docs/getting_started/first_2d_game/02.player_scene.rst:4
#, fuzzy
msgid "Creating the player scene"
msgstr "Kreiranje Sadržaja"

#: ../../docs/getting_started/first_2d_game/02.player_scene.rst:6
msgid ""
"With the project settings in place, we can start working on the player-"
"controlled character."
msgstr ""

#: ../../docs/getting_started/first_2d_game/02.player_scene.rst:9
msgid ""
"The first scene will define the ``Player`` object. One of the benefits of "
"creating a separate Player scene is that we can test it separately, even "
"before we've created other parts of the game."
msgstr ""

#: ../../docs/getting_started/first_2d_game/02.player_scene.rst:14
msgid "Node structure"
msgstr ""

#: ../../docs/getting_started/first_2d_game/02.player_scene.rst:16
msgid ""
"To begin, we need to choose a root node for the player object. As a general "
"rule, a scene's root node should reflect the object's desired functionality "
"- what the object *is*. Click the \"Other Node\" button and add an :ref:"
"`Area2D <class_Area2D>` node to the scene."
msgstr ""

#: ../../docs/getting_started/first_2d_game/02.player_scene.rst:23
msgid ""
"Godot will display a warning icon next to the node in the scene tree. You "
"can ignore it for now. We will address it later."
msgstr ""

#: ../../docs/getting_started/first_2d_game/02.player_scene.rst:26
msgid ""
"With ``Area2D`` we can detect objects that overlap or run into the player. "
"Change the node's name to ``Player`` by double-clicking on it. Now that "
"we've set the scene's root node, we can add additional nodes to give it more "
"functionality."
msgstr ""

#: ../../docs/getting_started/first_2d_game/02.player_scene.rst:31
msgid ""
"Before we add any children to the ``Player`` node, we want to make sure we "
"don't accidentally move or resize them by clicking on them. Select the node "
"and click the icon to the right of the lock. Its tooltip says \"Make "
"selected node's children not selectable.\""
msgstr ""

#: ../../docs/getting_started/first_2d_game/02.player_scene.rst:38
msgid ""
"Save the scene. Click Scene -> Save, or press :kbd:`Ctrl + S` on Windows/"
"Linux or :kbd:`Cmd + S` on macOS."
msgstr ""

#: ../../docs/getting_started/first_2d_game/02.player_scene.rst:41
msgid "For this project, we will be following the Godot naming conventions."
msgstr ""

#: ../../docs/getting_started/first_2d_game/02.player_scene.rst:43
msgid ""
"**GDScript**: Classes (nodes) use PascalCase, variables and functions use "
"snake_case, and constants use ALL_CAPS (See :ref:`doc_gdscript_styleguide`)."
msgstr ""

#: ../../docs/getting_started/first_2d_game/02.player_scene.rst:47
msgid ""
"**C#**: Classes, export variables and methods use PascalCase, private fields "
"use _camelCase, local variables and parameters use camelCase (See :ref:"
"`doc_c_sharp_styleguide`). Be careful to type the method names precisely "
"when connecting signals."
msgstr ""

#: ../../docs/getting_started/first_2d_game/02.player_scene.rst:54
msgid "Sprite animation"
msgstr ""

#: ../../docs/getting_started/first_2d_game/02.player_scene.rst:56
msgid ""
"Click on the ``Player`` node and add (:kbd:`Ctrl + A` on Windows/Linux or :"
"kbd:`Cmd + A` on macOS) a child node :ref:`AnimatedSprite2D "
"<class_AnimatedSprite2D>`. The ``AnimatedSprite2D`` will handle the "
"appearance and animations for our player. Notice that there is a warning "
"symbol next to the node. An ``AnimatedSprite2D`` requires a :ref:"
"`SpriteFrames <class_SpriteFrames>` resource, which is a list of the "
"animations it can display. To create one, find the ``Sprite Frames`` "
"property under the ``Animation`` tab in the Inspector and click \"[empty]\" -"
"> \"New SpriteFrames\". Click again to open the \"SpriteFrames\" panel:"
msgstr ""

#: ../../docs/getting_started/first_2d_game/02.player_scene.rst:68
msgid ""
"On the left is a list of animations. Click the \"default\" one and rename it "
"to \"walk\". Then click the \"Add Animation\" button to create a second "
"animation named \"up\". Find the player images in the \"FileSystem\" tab - "
"they're in the ``art`` folder you unzipped earlier. Drag the two images for "
"each animation, named ``playerGrey_up[1/2]`` and ``playerGrey_walk[1/2]``, "
"into the \"Animation Frames\" side of the panel for the corresponding "
"animation:"
msgstr ""

#: ../../docs/getting_started/first_2d_game/02.player_scene.rst:77
msgid ""
"The player images are a bit too large for the game window, so we need to "
"scale them down. Click on the ``AnimatedSprite2D`` node and set the "
"``Scale`` property to ``(0.5, 0.5)``. You can find it in the Inspector under "
"the ``Node2D`` heading."
msgstr ""

#: ../../docs/getting_started/first_2d_game/02.player_scene.rst:84
msgid ""
"Finally, add a :ref:`CollisionShape2D <class_CollisionShape2D>` as a child "
"of ``Player``. This will determine the player's \"hitbox\", or the bounds of "
"its collision area. For this character, a ``CapsuleShape2D`` node gives the "
"best fit, so next to \"Shape\" in the Inspector, click \"[empty]\" -> \"New "
"CapsuleShape2D\". Using the two size handles, resize the shape to cover the "
"sprite:"
msgstr ""

#: ../../docs/getting_started/first_2d_game/02.player_scene.rst:93
msgid "When you're finished, your ``Player`` scene should look like this:"
msgstr ""

#: ../../docs/getting_started/first_2d_game/02.player_scene.rst:97
msgid "Make sure to save the scene again after these changes."
msgstr ""

#: ../../docs/getting_started/first_2d_game/02.player_scene.rst:99
msgid ""
"In the next part, we'll add a script to the player node to move and animate "
"it. Then, we'll set up collision detection to know when the player got hit "
"by something."
msgstr ""

#: ../../docs/getting_started/first_2d_game/03.coding_the_player.rst:4
#, fuzzy
msgid "Coding the player"
msgstr "Kreiranje Sadržaja"

#: ../../docs/getting_started/first_2d_game/03.coding_the_player.rst:6
msgid ""
"In this lesson, we'll add player movement, animation, and set it up to "
"detect collisions."
msgstr ""

#: ../../docs/getting_started/first_2d_game/03.coding_the_player.rst:9
msgid ""
"To do so, we need to add some functionality that we can't get from a built-"
"in node, so we'll add a script. Click the ``Player`` node and click the "
"\"Attach Script\" button:"
msgstr ""

#: ../../docs/getting_started/first_2d_game/03.coding_the_player.rst:15
msgid ""
"In the script settings window, you can leave the default settings alone. "
"Just click \"Create\":"
msgstr ""

#: ../../docs/getting_started/first_2d_game/03.coding_the_player.rst:18
msgid ""
"If you're creating a C# script or other languages, select the language from "
"the `language` drop down menu before hitting create."
msgstr ""

#: ../../docs/getting_started/first_2d_game/03.coding_the_player.rst:23
msgid ""
"If this is your first time encountering GDScript, please read :ref:"
"`doc_scripting` before continuing."
msgstr ""

#: ../../docs/getting_started/first_2d_game/03.coding_the_player.rst:26
msgid "Start by declaring the member variables this object will need:"
msgstr ""

#: ../../docs/getting_started/first_2d_game/03.coding_the_player.rst:48
msgid ""
"Using the ``export`` keyword on the first variable ``speed`` allows us to "
"set its value in the Inspector. This can be handy for values that you want "
"to be able to adjust just like a node's built-in properties. Click on the "
"``Player`` node and you'll see the property now appears in the Inspector in "
"a new section with the name of the script. Remember, if you change the value "
"here, it will override the value written in the script."
msgstr ""

#: ../../docs/getting_started/first_2d_game/03.coding_the_player.rst:57
msgid ""
"If you're using C#, you need to (re)build the project assemblies whenever "
"you want to see new export variables or signals. This build can be manually "
"triggered by clicking the **Build** button at the top right of the editor."
msgstr ""

#: ../../docs/getting_started/first_2d_game/03.coding_the_player.rst:66
msgid ""
"Your ``player.gd`` script should already contain a ``_ready()`` and a "
"``_process()`` function. If you didn't select the default template shown "
"above, create these functions while following the lesson."
msgstr ""

#: ../../docs/getting_started/first_2d_game/03.coding_the_player.rst:71
msgid ""
"The ``_ready()`` function is called when a node enters the scene tree, which "
"is a good time to find the size of the game window:"
msgstr ""

#: ../../docs/getting_started/first_2d_game/03.coding_the_player.rst:87
msgid ""
"Now we can use the ``_process()`` function to define what the player will "
"do. ``_process()`` is called every frame, so we'll use it to update elements "
"of our game, which we expect will change often. For the player, we need to "
"do the following:"
msgstr ""

#: ../../docs/getting_started/first_2d_game/03.coding_the_player.rst:92
msgid "Check for input."
msgstr ""

#: ../../docs/getting_started/first_2d_game/03.coding_the_player.rst:93
msgid "Move in the given direction."
msgstr ""

#: ../../docs/getting_started/first_2d_game/03.coding_the_player.rst:94
msgid "Play the appropriate animation."
msgstr ""

#: ../../docs/getting_started/first_2d_game/03.coding_the_player.rst:96
msgid ""
"First, we need to check for input - is the player pressing a key? For this "
"game, we have 4 direction inputs to check. Input actions are defined in the "
"Project Settings under \"Input Map\". Here, you can define custom events and "
"assign different keys, mouse events, or other inputs to them. For this game, "
"we will map the arrow keys to the four directions."
msgstr ""

#: ../../docs/getting_started/first_2d_game/03.coding_the_player.rst:102
msgid ""
"Click on *Project -> Project Settings* to open the project settings window "
"and click on the *Input Map* tab at the top. Type \"move_right\" in the top "
"bar and click the \"Add\" button to add the ``move_right`` action."
msgstr ""

#: ../../docs/getting_started/first_2d_game/03.coding_the_player.rst:108
msgid ""
"We need to assign a key to this action. Click the \"+\" icon on the right, "
"to open the event manager window."
msgstr ""

#: ../../docs/getting_started/first_2d_game/03.coding_the_player.rst:113
msgid ""
"The \"Listening for Input...\" field should automatically be selected. Press "
"the \"right\" key on your keyboard, and the menu should look like this now."
msgstr ""

#: ../../docs/getting_started/first_2d_game/03.coding_the_player.rst:118
msgid ""
"Select the \"ok\" button. The \"right\" key is now associated with the "
"``move_right`` action."
msgstr ""

#: ../../docs/getting_started/first_2d_game/03.coding_the_player.rst:120
msgid "Repeat these steps to add three more mappings:"
msgstr ""

#: ../../docs/getting_started/first_2d_game/03.coding_the_player.rst:122
msgid "``move_left`` mapped to the left arrow key."
msgstr ""

#: ../../docs/getting_started/first_2d_game/03.coding_the_player.rst:123
msgid "``move_up`` mapped to the up arrow key."
msgstr ""

#: ../../docs/getting_started/first_2d_game/03.coding_the_player.rst:124
msgid "And ``move_down`` mapped to the down arrow key."
msgstr ""

#: ../../docs/getting_started/first_2d_game/03.coding_the_player.rst:126
msgid "Your input map tab should look like this:"
msgstr ""

#: ../../docs/getting_started/first_2d_game/03.coding_the_player.rst:130
msgid "Click the \"Close\" button to close the project settings."
msgstr ""

#: ../../docs/getting_started/first_2d_game/03.coding_the_player.rst:134
msgid ""
"We only mapped one key to each input action, but you can map multiple keys, "
"joystick buttons, or mouse buttons to the same input action."
msgstr ""

#: ../../docs/getting_started/first_2d_game/03.coding_the_player.rst:137
msgid ""
"You can detect whether a key is pressed using ``Input.is_action_pressed()``, "
"which returns ``true`` if it's pressed or ``false`` if it isn't."
msgstr ""

#: ../../docs/getting_started/first_2d_game/03.coding_the_player.rst:199
msgid ""
"We start by setting the ``velocity`` to ``(0, 0)`` - by default, the player "
"should not be moving. Then we check each input and add/subtract from the "
"``velocity`` to obtain a total direction. For example, if you hold ``right`` "
"and ``down`` at the same time, the resulting ``velocity`` vector will be "
"``(1, 1)``. In this case, since we're adding a horizontal and a vertical "
"movement, the player would move *faster* diagonally than if it just moved "
"horizontally."
msgstr ""

#: ../../docs/getting_started/first_2d_game/03.coding_the_player.rst:206
msgid ""
"We can prevent that if we *normalize* the velocity, which means we set its "
"*length* to ``1``, then multiply by the desired speed. This means no more "
"fast diagonal movement."
msgstr ""

#: ../../docs/getting_started/first_2d_game/03.coding_the_player.rst:210
msgid ""
"If you've never used vector math before, or need a refresher, you can see an "
"explanation of vector usage in Godot at :ref:`doc_vector_math`. It's good to "
"know but won't be necessary for the rest of this tutorial."
msgstr ""

#: ../../docs/getting_started/first_2d_game/03.coding_the_player.rst:214
msgid ""
"We also check whether the player is moving so we can call ``play()`` or "
"``stop()`` on the AnimatedSprite2D."
msgstr ""

#: ../../docs/getting_started/first_2d_game/03.coding_the_player.rst:217
msgid ""
"``$`` is shorthand for ``get_node()``. So in the code above, "
"``$AnimatedSprite2D.play()`` is the same as ``get_node(\"AnimatedSprite2D\")."
"play()``."
msgstr ""

#: ../../docs/getting_started/first_2d_game/03.coding_the_player.rst:221
msgid ""
"In GDScript, ``$`` returns the node at the relative path from the current "
"node, or returns ``null`` if the node is not found. Since AnimatedSprite2D "
"is a child of the current node, we can use ``$AnimatedSprite2D``."
msgstr ""

#: ../../docs/getting_started/first_2d_game/03.coding_the_player.rst:226
msgid ""
"Now that we have a movement direction, we can update the player's position. "
"We can also use ``clamp()`` to prevent it from leaving the screen. "
"*Clamping* a value means restricting it to a given range. Add the following "
"to the bottom of the ``_process`` function (make sure it's not indented "
"under the `else`):"
msgstr ""

#: ../../docs/getting_started/first_2d_game/03.coding_the_player.rst:245
msgid ""
"The `delta` parameter in the `_process()` function refers to the *frame "
"length* - the amount of time that the previous frame took to complete. Using "
"this value ensures that your movement will remain consistent even if the "
"frame rate changes."
msgstr ""

#: ../../docs/getting_started/first_2d_game/03.coding_the_player.rst:250
msgid ""
"Click \"Run Current Scene\" (:kbd:`F6`, :kbd:`Cmd + R` on macOS) and confirm "
"you can move the player around the screen in all directions."
msgstr ""

#: ../../docs/getting_started/first_2d_game/03.coding_the_player.rst:253
msgid "If you get an error in the \"Debugger\" panel that says"
msgstr ""

#: ../../docs/getting_started/first_2d_game/03.coding_the_player.rst:255
msgid ""
"``Attempt to call function 'play' in base 'null instance' on a null "
"instance``"
msgstr ""

#: ../../docs/getting_started/first_2d_game/03.coding_the_player.rst:258
msgid ""
"this likely means you spelled the name of the AnimatedSprite2D node wrong. "
"Node names are case-sensitive and ``$NodeName`` must match the name you see "
"in the scene tree."
msgstr ""

#: ../../docs/getting_started/first_2d_game/03.coding_the_player.rst:263
msgid "Choosing animations"
msgstr ""

#: ../../docs/getting_started/first_2d_game/03.coding_the_player.rst:265
msgid ""
"Now that the player can move, we need to change which animation the "
"AnimatedSprite2D is playing based on its direction. We have the \"walk\" "
"animation, which shows the player walking to the right. This animation "
"should be flipped horizontally using the ``flip_h`` property for left "
"movement. We also have the \"up\" animation, which should be flipped "
"vertically with ``flip_v`` for downward movement. Let's place this code at "
"the end of the ``_process()`` function:"
msgstr ""

#: ../../docs/getting_started/first_2d_game/03.coding_the_player.rst:299
msgid ""
"The boolean assignments in the code above are a common shorthand for "
"programmers. Since we're doing a comparison test (boolean) and also "
"*assigning* a boolean value, we can do both at the same time. Consider this "
"code versus the one-line boolean assignment above:"
msgstr ""

#: ../../docs/getting_started/first_2d_game/03.coding_the_player.rst:323
msgid ""
"Play the scene again and check that the animations are correct in each of "
"the directions."
msgstr ""

#: ../../docs/getting_started/first_2d_game/03.coding_the_player.rst:326
msgid ""
"A common mistake here is to type the names of the animations wrong. The "
"animation names in the SpriteFrames panel must match what you type in the "
"code. If you named the animation ``\"Walk\"``, you must also use a capital "
"\"W\" in the code."
msgstr ""

#: ../../docs/getting_started/first_2d_game/03.coding_the_player.rst:331
msgid ""
"When you're sure the movement is working correctly, add this line to "
"``_ready()``, so the player will be hidden when the game starts:"
msgstr ""

#: ../../docs/getting_started/first_2d_game/03.coding_the_player.rst:344
msgid "Preparing for collisions"
msgstr ""

#: ../../docs/getting_started/first_2d_game/03.coding_the_player.rst:346
msgid ""
"We want ``Player`` to detect when it's hit by an enemy, but we haven't made "
"any enemies yet! That's OK, because we're going to use Godot's *signal* "
"functionality to make it work."
msgstr ""

#: ../../docs/getting_started/first_2d_game/03.coding_the_player.rst:350
msgid ""
"Add the following at the top of the script. If you're using GDScript, add it "
"after ``extends Area2D``. If you're using C#, add it after ``public partial "
"class Player : Area2D``:"
msgstr ""

#: ../../docs/getting_started/first_2d_game/03.coding_the_player.rst:365
msgid ""
"This defines a custom signal called \"hit\" that we will have our player "
"emit (send out) when it collides with an enemy. We will use ``Area2D`` to "
"detect the collision. Select the ``Player`` node and click the \"Node\" tab "
"next to the Inspector tab to see the list of signals the player can emit:"
msgstr ""

#: ../../docs/getting_started/first_2d_game/03.coding_the_player.rst:372
msgid ""
"Notice our custom \"hit\" signal is there as well! Since our enemies are "
"going to be ``RigidBody2D`` nodes, we want the ``body_entered(body: "
"Node2D)`` signal. This signal will be emitted when a body contacts the "
"player. Click \"Connect..\" and the \"Connect a Signal\" window appears."
msgstr ""

#: ../../docs/getting_started/first_2d_game/03.coding_the_player.rst:377
msgid ""
"Godot will create a function with that exact name directly in script for "
"you. You don't need to change the default settings right now."
msgstr ""

#: ../../docs/getting_started/first_2d_game/03.coding_the_player.rst:384
msgid ""
"If you're using an external text editor (for example, Visual Studio Code), a "
"bug currently prevents Godot from doing so. You'll be sent to your external "
"editor, but the new function won't be there."
msgstr ""

#: ../../docs/getting_started/first_2d_game/03.coding_the_player.rst:388
msgid ""
"In this case, you'll need to write the function yourself into the Player's "
"script file."
msgstr ""

#: ../../docs/getting_started/first_2d_game/03.coding_the_player.rst:393
msgid ""
"Note the green icon indicating that a signal is connected to this function; "
"this does not mean the function exists, only that the signal will attempt to "
"connect to a function with that name, so double-check that the spelling of "
"the function matches exactly!"
msgstr ""

#: ../../docs/getting_started/first_2d_game/03.coding_the_player.rst:397
msgid "Next, add this code to the function:"
msgstr ""

#: ../../docs/getting_started/first_2d_game/03.coding_the_player.rst:418
msgid ""
"Each time an enemy hits the player, the signal is going to be emitted. We "
"need to disable the player's collision so that we don't trigger the ``hit`` "
"signal more than once."
msgstr ""

#: ../../docs/getting_started/first_2d_game/03.coding_the_player.rst:422
msgid ""
"Disabling the area's collision shape can cause an error if it happens in the "
"middle of the engine's collision processing. Using ``set_deferred()`` tells "
"Godot to wait to disable the shape until it's safe to do so."
msgstr ""

#: ../../docs/getting_started/first_2d_game/03.coding_the_player.rst:427
msgid ""
"The last piece is to add a function we can call to reset the player when "
"starting a new game."
msgstr ""

#: ../../docs/getting_started/first_2d_game/03.coding_the_player.rst:447
msgid "With the player working, we'll work on the enemy in the next lesson."
msgstr ""

#: ../../docs/getting_started/first_2d_game/04.creating_the_enemy.rst:4
#, fuzzy
msgid "Creating the enemy"
msgstr "Kreiranje Sadržaja"

#: ../../docs/getting_started/first_2d_game/04.creating_the_enemy.rst:6
msgid ""
"Now it's time to make the enemies our player will have to dodge. Their "
"behavior will not be very complex: mobs will spawn randomly at the edges of "
"the screen, choose a random direction, and move in a straight line."
msgstr ""

#: ../../docs/getting_started/first_2d_game/04.creating_the_enemy.rst:10
msgid ""
"We'll create a ``Mob`` scene, which we can then *instance* to create any "
"number of independent mobs in the game."
msgstr ""

#: ../../docs/getting_started/first_2d_game/04.creating_the_enemy.rst:14
msgid "Node setup"
msgstr ""

#: ../../docs/getting_started/first_2d_game/04.creating_the_enemy.rst:16
msgid "Click Scene -> New Scene from the top menu and add the following nodes:"
msgstr ""

#: ../../docs/getting_started/first_2d_game/04.creating_the_enemy.rst:18
msgid ":ref:`RigidBody2D <class_RigidBody2D>` (named ``Mob``)"
msgstr ""

#: ../../docs/getting_started/first_2d_game/04.creating_the_enemy.rst:20
msgid ":ref:`AnimatedSprite2D <class_AnimatedSprite2D>`"
msgstr ""

#: ../../docs/getting_started/first_2d_game/04.creating_the_enemy.rst:21
msgid ":ref:`CollisionShape2D <class_CollisionShape2D>`"
msgstr ""

#: ../../docs/getting_started/first_2d_game/04.creating_the_enemy.rst:22
msgid ":ref:`VisibleOnScreenNotifier2D <class_VisibleOnScreenNotifier2D>`"
msgstr ""

#: ../../docs/getting_started/first_2d_game/04.creating_the_enemy.rst:24
msgid ""
"Don't forget to set the children so they can't be selected, like you did "
"with the Player scene."
msgstr ""

#: ../../docs/getting_started/first_2d_game/04.creating_the_enemy.rst:27
msgid ""
"Select the ``Mob`` node and set its ``Gravity Scale`` property in the :ref:"
"`RigidBody2D <class_RigidBody2D>` section of the inspector to ``0``. This "
"will prevent the mob from falling downwards."
msgstr ""

#: ../../docs/getting_started/first_2d_game/04.creating_the_enemy.rst:32
msgid ""
"In addition, under the :ref:`CollisionObject2D <class_CollisionObject2D>` "
"section just beneath the **RigidBody2D** section, expand the **Collision** "
"group and uncheck the ``1`` inside the ``Mask`` property. This will ensure "
"the mobs do not collide with each other."
msgstr ""

#: ../../docs/getting_started/first_2d_game/04.creating_the_enemy.rst:40
msgid ""
"Set up the :ref:`AnimatedSprite2D <class_AnimatedSprite2D>` like you did for "
"the player. This time, we have 3 animations: ``fly``, ``swim``, and "
"``walk``. There are two images for each animation in the art folder."
msgstr ""

#: ../../docs/getting_started/first_2d_game/04.creating_the_enemy.rst:44
msgid ""
"The ``Animation Speed`` property has to be set for each individual "
"animation. Adjust it to ``3`` for all 3 animations."
msgstr ""

#: ../../docs/getting_started/first_2d_game/04.creating_the_enemy.rst:48
msgid ""
"You can use the \"Play Animation\" buttons on the right of the ``Animation "
"Speed`` input field to preview your animations."
msgstr ""

#: ../../docs/getting_started/first_2d_game/04.creating_the_enemy.rst:50
msgid ""
"We'll select one of these animations randomly so that the mobs will have "
"some variety."
msgstr ""

#: ../../docs/getting_started/first_2d_game/04.creating_the_enemy.rst:53
msgid ""
"Like the player images, these mob images need to be scaled down. Set the "
"``AnimatedSprite2D``'s ``Scale`` property to ``(0.75, 0.75)``."
msgstr ""

#: ../../docs/getting_started/first_2d_game/04.creating_the_enemy.rst:56
msgid ""
"As in the ``Player`` scene, add a ``CapsuleShape2D`` for the collision. To "
"align the shape with the image, you'll need to set the ``Rotation`` property "
"to ``90`` (under \"Transform\" in the Inspector)."
msgstr ""

#: ../../docs/getting_started/first_2d_game/04.creating_the_enemy.rst:60
#, fuzzy
msgid "Save the scene."
msgstr "Kreiranje Sadržaja"

#: ../../docs/getting_started/first_2d_game/04.creating_the_enemy.rst:63
msgid "Enemy script"
msgstr ""

#: ../../docs/getting_started/first_2d_game/04.creating_the_enemy.rst:65
msgid "Add a script to the ``Mob`` like this:"
msgstr ""

#: ../../docs/getting_started/first_2d_game/04.creating_the_enemy.rst:81
msgid ""
"Now let's look at the rest of the script. In ``_ready()`` we play the "
"animation and randomly choose one of the three animation types:"
msgstr ""

#: ../../docs/getting_started/first_2d_game/04.creating_the_enemy.rst:100
msgid ""
"First, we get the list of animation names from the AnimatedSprite2D's "
"``sprite_frames`` property. This returns an Array containing all three "
"animation names: ``[\"walk\", \"swim\", \"fly\"]``."
msgstr ""

#: ../../docs/getting_started/first_2d_game/04.creating_the_enemy.rst:104
msgid ""
"We then need to pick a random number between ``0`` and ``2`` to select one "
"of these names from the list (array indices start at ``0``). ``randi() % n`` "
"selects a random integer between ``0`` and ``n-1``."
msgstr ""

#: ../../docs/getting_started/first_2d_game/04.creating_the_enemy.rst:108
msgid ""
"The last piece is to make the mobs delete themselves when they leave the "
"screen. Connect the ``screen_exited()`` signal of the "
"``VisibleOnScreenNotifier2D`` node to the ``Mob`` and add this code:"
msgstr ""

#: ../../docs/getting_started/first_2d_game/04.creating_the_enemy.rst:125
msgid "This completes the `Mob` scene."
msgstr ""

#: ../../docs/getting_started/first_2d_game/04.creating_the_enemy.rst:127
msgid ""
"With the player and enemies ready, in the next part, we'll bring them "
"together in a new scene. We'll make enemies spawn randomly around the game "
"board and move forward, turning our project into a playable game."
msgstr ""

#: ../../docs/getting_started/first_2d_game/05.the_main_game_scene.rst:4
#, fuzzy
msgid "The main game scene"
msgstr "Kreiranje Sadržaja"

#: ../../docs/getting_started/first_2d_game/05.the_main_game_scene.rst:6
msgid ""
"Now it's time to bring everything we did together into a playable game scene."
msgstr ""

#: ../../docs/getting_started/first_2d_game/05.the_main_game_scene.rst:8
msgid ""
"Create a new scene and add a :ref:`Node <class_Node>` named ``Main``. (The "
"reason we are using Node instead of Node2D is because this node will be a "
"container for handling game logic. It does not require 2D functionality "
"itself.)"
msgstr ""

#: ../../docs/getting_started/first_2d_game/05.the_main_game_scene.rst:12
msgid ""
"Click the **Instance** button (represented by a chain link icon) and select "
"your saved ``player.tscn``."
msgstr ""

#: ../../docs/getting_started/first_2d_game/05.the_main_game_scene.rst:17
msgid ""
"Now, add the following nodes as children of ``Main``, and name them as shown "
"(values are in seconds):"
msgstr ""

#: ../../docs/getting_started/first_2d_game/05.the_main_game_scene.rst:20
msgid ""
":ref:`Timer <class_Timer>` (named ``MobTimer``) - to control how often mobs "
"spawn"
msgstr ""

#: ../../docs/getting_started/first_2d_game/05.the_main_game_scene.rst:22
msgid ""
":ref:`Timer <class_Timer>` (named ``ScoreTimer``) - to increment the score "
"every second"
msgstr ""

#: ../../docs/getting_started/first_2d_game/05.the_main_game_scene.rst:24
msgid ""
":ref:`Timer <class_Timer>` (named ``StartTimer``) - to give a delay before "
"starting"
msgstr ""

#: ../../docs/getting_started/first_2d_game/05.the_main_game_scene.rst:26
msgid ""
":ref:`Marker2D <class_Marker2D>` (named ``StartPosition``) - to indicate the "
"player's start position"
msgstr ""

#: ../../docs/getting_started/first_2d_game/05.the_main_game_scene.rst:29
msgid ""
"Set the ``Wait Time`` property of each of the ``Timer`` nodes as follows:"
msgstr ""

#: ../../docs/getting_started/first_2d_game/05.the_main_game_scene.rst:31
msgid "``MobTimer``: ``0.5``"
msgstr ""

#: ../../docs/getting_started/first_2d_game/05.the_main_game_scene.rst:32
msgid "``ScoreTimer``: ``1``"
msgstr ""

#: ../../docs/getting_started/first_2d_game/05.the_main_game_scene.rst:33
msgid "``StartTimer``: ``2``"
msgstr ""

#: ../../docs/getting_started/first_2d_game/05.the_main_game_scene.rst:35
msgid ""
"In addition, set the ``One Shot`` property of ``StartTimer`` to \"On\" and "
"set ``Position`` of the ``StartPosition`` node to ``(240, 450)``."
msgstr ""

#: ../../docs/getting_started/first_2d_game/05.the_main_game_scene.rst:39
msgid "Spawning mobs"
msgstr ""

#: ../../docs/getting_started/first_2d_game/05.the_main_game_scene.rst:41
msgid ""
"The Main node will be spawning new mobs, and we want them to appear at a "
"random location on the edge of the screen. Add a :ref:`Path2D "
"<class_Path2D>` node named ``MobPath`` as a child of ``Main``. When you "
"select ``Path2D``, you will see some new buttons at the top of the editor:"
msgstr ""

#: ../../docs/getting_started/first_2d_game/05.the_main_game_scene.rst:48
msgid ""
"Select the middle one (\"Add Point\") and draw the path by clicking to add "
"the points at the corners shown. To have the points snap to the grid, make "
"sure \"Use Grid Snap\" and \"Use Smart Snap\" are both selected. These "
"options can be found to the left of the \"Lock\" button, appearing as a "
"magnet next to some dots and intersecting lines, respectively."
msgstr ""

#: ../../docs/getting_started/first_2d_game/05.the_main_game_scene.rst:56
msgid ""
"Draw the path in *clockwise* order, or your mobs will spawn pointing "
"*outwards* instead of *inwards*!"
msgstr ""

#: ../../docs/getting_started/first_2d_game/05.the_main_game_scene.rst:61
msgid ""
"After placing point ``4`` in the image, click the \"Close Curve\" button and "
"your curve will be complete."
msgstr ""

#: ../../docs/getting_started/first_2d_game/05.the_main_game_scene.rst:64
msgid ""
"Now that the path is defined, add a :ref:`PathFollow2D <class_PathFollow2D>` "
"node as a child of ``MobPath`` and name it ``MobSpawnLocation``. This node "
"will automatically rotate and follow the path as it moves, so we can use it "
"to select a random position and direction along the path."
msgstr ""

#: ../../docs/getting_started/first_2d_game/05.the_main_game_scene.rst:69
msgid "Your scene should look like this:"
msgstr ""

#: ../../docs/getting_started/first_2d_game/05.the_main_game_scene.rst:74
msgid "Main script"
msgstr ""

#: ../../docs/getting_started/first_2d_game/05.the_main_game_scene.rst:76
msgid ""
"Add a script to ``Main``. At the top of the script, we use ``@export var "
"mob_scene: PackedScene`` to allow us to choose the Mob scene we want to "
"instance."
msgstr ""

#: ../../docs/getting_started/first_2d_game/05.the_main_game_scene.rst:102
msgid ""
"Click the ``Main`` node and you will see the ``Mob Scene`` property in the "
"Inspector under \"Main.gd\"."
msgstr ""

#: ../../docs/getting_started/first_2d_game/05.the_main_game_scene.rst:105
msgid "You can assign this property's value in two ways:"
msgstr ""

#: ../../docs/getting_started/first_2d_game/05.the_main_game_scene.rst:107
msgid ""
"Drag ``mob.tscn`` from the \"FileSystem\" dock and drop it in the **Mob "
"Scene** property."
msgstr ""

#: ../../docs/getting_started/first_2d_game/05.the_main_game_scene.rst:109
msgid ""
"Click the down arrow next to \"[empty]\" and choose \"Load\". Select ``mob."
"tscn``."
msgstr ""

#: ../../docs/getting_started/first_2d_game/05.the_main_game_scene.rst:111
msgid ""
"Next, select the instance of the ``Player`` scene under ``Main`` node in the "
"Scene dock, and access the Node dock on the sidebar. Make sure to have the "
"Signals tab selected in the Node dock."
msgstr ""

#: ../../docs/getting_started/first_2d_game/05.the_main_game_scene.rst:115
msgid ""
"You should see a list of the signals for the ``Player`` node. Find and "
"double-click the ``hit`` signal in the list (or right-click it and select "
"\"Connect...\"). This will open the signal connection dialog. We want to "
"make a new function named ``game_over``, which will handle what needs to "
"happen when a game ends. Type \"game_over\" in the \"Receiver Method\" box "
"at the bottom of the signal connection dialog and click \"Connect\". You are "
"aiming to have the ``hit`` signal emitted from ``Player`` and handled in the "
"``Main`` script. Add the following code to the new function, as well as a "
"``new_game`` function that will set everything up for a new game:"
msgstr ""

#: ../../docs/getting_started/first_2d_game/05.the_main_game_scene.rst:156
msgid ""
"Now connect the ``timeout()`` signal of each of the Timer nodes "
"(``StartTimer``, ``ScoreTimer``, and ``MobTimer``) to the main script. "
"``StartTimer`` will start the other two timers. ``ScoreTimer`` will "
"increment the score by 1."
msgstr ""

#: ../../docs/getting_started/first_2d_game/05.the_main_game_scene.rst:183
msgid ""
"In ``_on_mob_timer_timeout()``, we will create a mob instance, pick a random "
"starting location along the ``Path2D``, and set the mob in motion. The "
"``PathFollow2D`` node will automatically rotate as it follows the path, so "
"we will use that to select the mob's direction as well as its position. When "
"we spawn a mob, we'll pick a random value between ``150.0`` and ``250.0`` "
"for how fast each mob will move (it would be boring if they were all moving "
"at the same speed)."
msgstr ""

#: ../../docs/getting_started/first_2d_game/05.the_main_game_scene.rst:191
msgid ""
"Note that a new instance must be added to the scene using ``add_child()``."
msgstr ""

#: ../../docs/getting_started/first_2d_game/05.the_main_game_scene.rst:254
msgid ""
"Why ``PI``? In functions requiring angles, Godot uses *radians*, not "
"degrees. Pi represents a half turn in radians, about ``3.1415`` (there is "
"also ``TAU`` which is equal to ``2 * PI``). If you're more comfortable "
"working with degrees, you'll need to use the ``deg_to_rad()`` and "
"``rad_to_deg()`` functions to convert between the two."
msgstr ""

#: ../../docs/getting_started/first_2d_game/05.the_main_game_scene.rst:262
#, fuzzy
msgid "Testing the scene"
msgstr "Kreiranje Sadržaja"

#: ../../docs/getting_started/first_2d_game/05.the_main_game_scene.rst:264
msgid ""
"Let's test the scene to make sure everything is working. Add this "
"``new_game`` call to ``_ready()``:"
msgstr ""

#: ../../docs/getting_started/first_2d_game/05.the_main_game_scene.rst:280
msgid ""
"Let's also assign ``Main`` as our \"Main Scene\" - the one that runs "
"automatically when the game launches. Press the \"Play\" button and select "
"``main.tscn`` when prompted."
msgstr ""

#: ../../docs/getting_started/first_2d_game/05.the_main_game_scene.rst:284
msgid ""
"If you had already set another scene as the \"Main Scene\", you can right "
"click ``main.tscn`` in the FileSystem dock and select \"Set As Main Scene\"."
msgstr ""

#: ../../docs/getting_started/first_2d_game/05.the_main_game_scene.rst:287
msgid ""
"You should be able to move the player around, see mobs spawning, and see the "
"player disappear when hit by a mob."
msgstr ""

#: ../../docs/getting_started/first_2d_game/05.the_main_game_scene.rst:290
msgid ""
"When you're sure everything is working, remove the call to ``new_game()`` "
"from ``_ready()`` and replace it with ``pass``."
msgstr ""

#: ../../docs/getting_started/first_2d_game/05.the_main_game_scene.rst:293
msgid ""
"What's our game lacking? Some user interface. In the next lesson, we'll add "
"a title screen and display the player's score."
msgstr ""

#: ../../docs/getting_started/first_2d_game/06.heads_up_display.rst:4
msgid "Heads up display"
msgstr ""

#: ../../docs/getting_started/first_2d_game/06.heads_up_display.rst:6
msgid ""
"The final piece our game needs is a User Interface (UI) to display things "
"like score, a \"game over\" message, and a restart button."
msgstr ""

#: ../../docs/getting_started/first_2d_game/06.heads_up_display.rst:9
msgid ""
"Create a new scene, click the \"Other Node\" button and add a :ref:"
"`CanvasLayer <class_CanvasLayer>` node named ``HUD``. \"HUD\" stands for "
"\"heads-up display\", an informational display that appears as an overlay on "
"top of the game view."
msgstr ""

#: ../../docs/getting_started/first_2d_game/06.heads_up_display.rst:13
msgid ""
"The :ref:`CanvasLayer <class_CanvasLayer>` node lets us draw our UI elements "
"on a layer above the rest of the game, so that the information it displays "
"isn't covered up by any game elements like the player or mobs."
msgstr ""

#: ../../docs/getting_started/first_2d_game/06.heads_up_display.rst:17
msgid "The HUD needs to display the following information:"
msgstr ""

#: ../../docs/getting_started/first_2d_game/06.heads_up_display.rst:19
msgid "Score, changed by ``ScoreTimer``."
msgstr ""

#: ../../docs/getting_started/first_2d_game/06.heads_up_display.rst:20
msgid "A message, such as \"Game Over\" or \"Get Ready!\""
msgstr ""

#: ../../docs/getting_started/first_2d_game/06.heads_up_display.rst:21
msgid "A \"Start\" button to begin the game."
msgstr ""

#: ../../docs/getting_started/first_2d_game/06.heads_up_display.rst:23
msgid ""
"The basic node for UI elements is :ref:`Control <class_Control>`. To create "
"our UI, we'll use two types of :ref:`Control <class_Control>` nodes: :ref:"
"`Label <class_Label>` and :ref:`Button <class_Button>`."
msgstr ""

#: ../../docs/getting_started/first_2d_game/06.heads_up_display.rst:27
msgid "Create the following as children of the ``HUD`` node:"
msgstr ""

#: ../../docs/getting_started/first_2d_game/06.heads_up_display.rst:29
msgid ":ref:`Label <class_Label>` named ``ScoreLabel``."
msgstr ""

#: ../../docs/getting_started/first_2d_game/06.heads_up_display.rst:30
msgid ":ref:`Label <class_Label>` named ``Message``."
msgstr ""

#: ../../docs/getting_started/first_2d_game/06.heads_up_display.rst:31
msgid ":ref:`Button <class_Button>` named ``StartButton``."
msgstr ""

#: ../../docs/getting_started/first_2d_game/06.heads_up_display.rst:32
msgid ":ref:`Timer <class_Timer>` named ``MessageTimer``."
msgstr ""

#: ../../docs/getting_started/first_2d_game/06.heads_up_display.rst:34
msgid ""
"Click on the ``ScoreLabel`` and type a number into the ``Text`` field in the "
"Inspector. The default font for ``Control`` nodes is small and doesn't scale "
"well. There is a font file included in the game assets called \"Xolonium-"
"Regular.ttf\". To use this font, do the following:"
msgstr ""

#: ../../docs/getting_started/first_2d_game/06.heads_up_display.rst:39
msgid ""
"Under \"Theme Overrides > Fonts\", choose \"Load\" and select the \"Xolonium-"
"Regular.ttf\" file."
msgstr ""

#: ../../docs/getting_started/first_2d_game/06.heads_up_display.rst:43
msgid ""
"The font size is still too small, increase it to ``64`` under \"Theme "
"Overrides > Font Sizes\". Once you've done this with the ``ScoreLabel``, "
"repeat the changes for the ``Message`` and ``StartButton`` nodes."
msgstr ""

#: ../../docs/getting_started/first_2d_game/06.heads_up_display.rst:48
msgid ""
"**Anchors:** ``Control`` nodes have a position and size, but they also have "
"anchors. Anchors define the origin - the reference point for the edges of "
"the node."
msgstr ""

#: ../../docs/getting_started/first_2d_game/06.heads_up_display.rst:52
msgid ""
"Arrange the nodes as shown below. You can drag the nodes to place them "
"manually, or for more precise placement, use \"Anchor Presets\"."
msgstr ""

#: ../../docs/getting_started/first_2d_game/06.heads_up_display.rst:59
msgid "ScoreLabel"
msgstr ""

#: ../../docs/getting_started/first_2d_game/06.heads_up_display.rst:61
msgid "Add the text ``0``."
msgstr ""

#: ../../docs/getting_started/first_2d_game/06.heads_up_display.rst:62
#: ../../docs/getting_started/first_2d_game/06.heads_up_display.rst:69
msgid ""
"Set the \"Horizontal Alignment\" and \"Vertical Alignment\" to ``Center``."
msgstr ""

#: ../../docs/getting_started/first_2d_game/06.heads_up_display.rst:63
msgid "Choose the \"Anchor Preset\" ``Center Top``."
msgstr ""

#: ../../docs/getting_started/first_2d_game/06.heads_up_display.rst:66
msgid "Message"
msgstr ""

#: ../../docs/getting_started/first_2d_game/06.heads_up_display.rst:68
msgid "Add the text ``Dodge the Creeps!``."
msgstr ""

#: ../../docs/getting_started/first_2d_game/06.heads_up_display.rst:70
msgid ""
"Set the \"Autowrap Mode\" to ``Word``, otherwise the label will stay on one "
"line."
msgstr ""

#: ../../docs/getting_started/first_2d_game/06.heads_up_display.rst:71
msgid ""
"Under \"Control - Layout/Transform\" set \"Size X\"  to ``480`` to use the "
"entire width of the screen."
msgstr ""

#: ../../docs/getting_started/first_2d_game/06.heads_up_display.rst:72
msgid "Choose the \"Anchor Preset\" ``Center``."
msgstr ""

#: ../../docs/getting_started/first_2d_game/06.heads_up_display.rst:75
msgid "StartButton"
msgstr ""

#: ../../docs/getting_started/first_2d_game/06.heads_up_display.rst:77
msgid "Add the text ``Start``."
msgstr ""

#: ../../docs/getting_started/first_2d_game/06.heads_up_display.rst:78
msgid ""
"Under \"Control - Layout/Transform\", set \"Size X\" to ``200`` and \"Size "
"Y\" to ``100`` to add a little bit more padding between the border and text."
msgstr ""

#: ../../docs/getting_started/first_2d_game/06.heads_up_display.rst:80
msgid "Choose the \"Anchor Preset\" ``Center Bottom``."
msgstr ""

#: ../../docs/getting_started/first_2d_game/06.heads_up_display.rst:81
msgid "Under \"Control - Layout/Transform\", set \"Position Y\" to ``580``."
msgstr ""

#: ../../docs/getting_started/first_2d_game/06.heads_up_display.rst:83
msgid ""
"On the ``MessageTimer``, set the ``Wait Time`` to ``2`` and set the ``One "
"Shot`` property to \"On\"."
msgstr ""

#: ../../docs/getting_started/first_2d_game/06.heads_up_display.rst:86
msgid "Now add this script to ``HUD``:"
msgstr ""

#: ../../docs/getting_started/first_2d_game/06.heads_up_display.rst:108
msgid ""
"We now want to display a message temporarily, such as \"Get Ready\", so we "
"add the following code"
msgstr ""

#: ../../docs/getting_started/first_2d_game/06.heads_up_display.rst:130
msgid ""
"We also need to process what happens when the player loses. The code below "
"will show \"Game Over\" for 2 seconds, then return to the title screen and, "
"after a brief pause, show the \"Start\" button."
msgstr ""

#: ../../docs/getting_started/first_2d_game/06.heads_up_display.rst:163
msgid ""
"This function is called when the player loses. It will show \"Game Over\" "
"for 2 seconds, then return to the title screen and, after a brief pause, "
"show the \"Start\" button."
msgstr ""

#: ../../docs/getting_started/first_2d_game/06.heads_up_display.rst:167
msgid ""
"When you need to pause for a brief time, an alternative to using a Timer "
"node is to use the SceneTree's ``create_timer()`` function. This can be very "
"useful to add delays such as in the above code, where we want to wait some "
"time before showing the \"Start\" button."
msgstr ""

#: ../../docs/getting_started/first_2d_game/06.heads_up_display.rst:172
msgid "Add the code below to ``HUD`` to update the score"
msgstr ""

#: ../../docs/getting_started/first_2d_game/06.heads_up_display.rst:187
msgid ""
"Connect the ``pressed()`` signal of ``StartButton`` and the ``timeout()`` "
"signal of ``MessageTimer``, and add the following code to the new functions:"
msgstr ""

#: ../../docs/getting_started/first_2d_game/06.heads_up_display.rst:214
msgid "Connecting HUD to Main"
msgstr ""

#: ../../docs/getting_started/first_2d_game/06.heads_up_display.rst:216
msgid ""
"Now that we're done creating the ``HUD`` scene, go back to ``Main``. "
"Instance the ``HUD`` scene in ``Main`` like you did the ``Player`` scene. "
"The scene tree should look like this, so make sure you didn't miss anything:"
msgstr ""

#: ../../docs/getting_started/first_2d_game/06.heads_up_display.rst:222
msgid ""
"Now we need to connect the ``HUD`` functionality to our ``Main`` script. "
"This requires a few additions to the ``Main`` scene:"
msgstr ""

#: ../../docs/getting_started/first_2d_game/06.heads_up_display.rst:225
msgid ""
"In the Node tab, connect the HUD's ``start_game`` signal to the "
"``new_game()`` function of the Main node by clicking the \"Pick\" button in "
"the \"Connect a Signal\" window and selecting the ``new_game()`` method or "
"type \"new_game\" below \"Receiver Method\" in the window. Verify that the "
"green connection icon now appears next to ``func new_game()`` in the script."
msgstr ""

#: ../../docs/getting_started/first_2d_game/06.heads_up_display.rst:231
msgid ""
"In ``new_game()``, update the score display and show the \"Get Ready\" "
"message:"
msgstr ""

#: ../../docs/getting_started/first_2d_game/06.heads_up_display.rst:245
msgid "In ``game_over()`` we need to call the corresponding ``HUD`` function:"
msgstr ""

#: ../../docs/getting_started/first_2d_game/06.heads_up_display.rst:256
msgid ""
"Finally, add this to ``_on_score_timer_timeout()`` to keep the display in "
"sync with the changing score:"
msgstr ""

#: ../../docs/getting_started/first_2d_game/06.heads_up_display.rst:270
msgid ""
"Remember to remove the call to ``new_game()`` from ``_ready()`` if you "
"haven't already, otherwise your game will start automatically."
msgstr ""

#: ../../docs/getting_started/first_2d_game/06.heads_up_display.rst:274
msgid ""
"Now you're ready to play! Click the \"Play the Project\" button. You will be "
"asked to select a main scene, so choose ``main.tscn``."
msgstr ""

#: ../../docs/getting_started/first_2d_game/06.heads_up_display.rst:278
msgid "Removing old creeps"
msgstr ""

#: ../../docs/getting_started/first_2d_game/06.heads_up_display.rst:280
msgid ""
"If you play until \"Game Over\" and then start a new game right away, the "
"creeps from the previous game may still be on the screen. It would be better "
"if they all disappeared at the start of a new game. We just need a way to "
"tell *all* the mobs to remove themselves. We can do this with the \"group\" "
"feature."
msgstr ""

#: ../../docs/getting_started/first_2d_game/06.heads_up_display.rst:285
msgid ""
"In the ``Mob`` scene, select the root node and click the \"Node\" tab next "
"to the Inspector (the same place where you find the node's signals). Next to "
"\"Signals\", click \"Groups\" and you can type a new group name and click "
"\"Add\"."
msgstr ""

#: ../../docs/getting_started/first_2d_game/06.heads_up_display.rst:291
msgid ""
"Now all mobs will be in the \"mobs\" group. We can then add the following "
"line to the ``new_game()`` function in ``Main``:"
msgstr ""

#: ../../docs/getting_started/first_2d_game/06.heads_up_display.rst:305
msgid ""
"The ``call_group()`` function calls the named function on every node in a "
"group - in this case we are telling every mob to delete itself."
msgstr ""

#: ../../docs/getting_started/first_2d_game/06.heads_up_display.rst:308
msgid ""
"The game's mostly done at this point. In the next and last part, we'll "
"polish it a bit by adding a background, looping music, and some keyboard "
"shortcuts."
msgstr ""

#: ../../docs/getting_started/first_2d_game/07.finishing-up.rst:4
msgid "Finishing up"
msgstr ""

#: ../../docs/getting_started/first_2d_game/07.finishing-up.rst:6
msgid ""
"We have now completed all the functionality for our game. Below are some "
"remaining steps to add a bit more \"juice\" to improve the game experience."
msgstr ""

#: ../../docs/getting_started/first_2d_game/07.finishing-up.rst:9
msgid "Feel free to expand the gameplay with your own ideas."
msgstr ""

#: ../../docs/getting_started/first_2d_game/07.finishing-up.rst:12
#: ../../docs/tutorials/3d/environment_and_post_processing.rst:133
msgid "Background"
msgstr ""

#: ../../docs/getting_started/first_2d_game/07.finishing-up.rst:14
msgid ""
"The default gray background is not very appealing, so let's change its "
"color. One way to do this is to use a :ref:`ColorRect <class_ColorRect>` "
"node. Make it the first node under ``Main`` so that it will be drawn behind "
"the other nodes. ``ColorRect`` only has one property: ``Color``. Choose a "
"color you like and select \"Layout\" -> \"Anchors Preset\" -> \"Full Rect\" "
"either in the toolbar at the top of the viewport or in the inspector so that "
"it covers the screen."
msgstr ""

#: ../../docs/getting_started/first_2d_game/07.finishing-up.rst:20
msgid ""
"You could also add a background image, if you have one, by using a "
"``TextureRect`` node instead."
msgstr ""

#: ../../docs/getting_started/first_2d_game/07.finishing-up.rst:24
msgid "Sound effects"
msgstr ""

#: ../../docs/getting_started/first_2d_game/07.finishing-up.rst:26
msgid ""
"Sound and music can be the single most effective way to add appeal to the "
"game experience. In your game's **art** folder, you have two sound files: "
"\"House In a Forest Loop.ogg\" for background music, and \"gameover.wav\" "
"for when the player loses."
msgstr ""

#: ../../docs/getting_started/first_2d_game/07.finishing-up.rst:31
msgid ""
"Add two :ref:`AudioStreamPlayer <class_AudioStreamPlayer>` nodes as children "
"of ``Main``. Name one of them ``Music`` and the other ``DeathSound``. On "
"each one, click on the ``Stream`` property, select \"Load\", and choose the "
"corresponding audio file."
msgstr ""

#: ../../docs/getting_started/first_2d_game/07.finishing-up.rst:36
msgid ""
"All audio is automatically imported with the ``Loop`` setting disabled. If "
"you want the music to loop seamlessly, click on the Stream file arrow, "
"select ``Make Unique``, then click on the Stream file and check the ``Loop`` "
"box."
msgstr ""

#: ../../docs/getting_started/first_2d_game/07.finishing-up.rst:40
msgid ""
"To play the music, add ``$Music.play()`` in the ``new_game()`` function and "
"``$Music.stop()`` in the ``game_over()`` function."
msgstr ""

#: ../../docs/getting_started/first_2d_game/07.finishing-up.rst:43
msgid "Finally, add ``$DeathSound.play()`` in the ``game_over()`` function."
msgstr ""

#: ../../docs/getting_started/first_2d_game/07.finishing-up.rst:74
msgid "Keyboard shortcut"
msgstr ""

#: ../../docs/getting_started/first_2d_game/07.finishing-up.rst:76
msgid ""
"Since the game is played with keyboard controls, it would be convenient if "
"we could also start the game by pressing a key on the keyboard. We can do "
"this with the \"Shortcut\" property of the ``Button`` node."
msgstr ""

#: ../../docs/getting_started/first_2d_game/07.finishing-up.rst:80
msgid ""
"In a previous lesson, we created four input actions to move the character. "
"We will create a similar input action to map to the start button."
msgstr ""

#: ../../docs/getting_started/first_2d_game/07.finishing-up.rst:83
msgid ""
"Select \"Project\" -> \"Project Settings\" and then click on the \"Input "
"Map\" tab. In the same way you created the movement input actions, create a "
"new input action called ``start_game`` and add a key mapping for the :kbd:"
"`Enter` key."
msgstr ""

#: ../../docs/getting_started/first_2d_game/07.finishing-up.rst:90
msgid ""
"Now would be a good time to add controller support if you have one "
"available. Attach or pair your controller and then under each input action "
"that you wish to add controller support for, click on the \"+\" button and "
"press the corresponding button, d-pad, or stick direction that you want to "
"map to the respective input action."
msgstr ""

#: ../../docs/getting_started/first_2d_game/07.finishing-up.rst:95
msgid ""
"In the ``HUD`` scene, select the ``StartButton`` and find its **Shortcut** "
"property in the Inspector. Create a new :ref:`Shortcut <class_Shortcut>` "
"resource by clicking within the box, open the **Events** array and add a new "
"array element to it by clicking on **Array[InputEvent] (size 0)**."
msgstr ""

#: ../../docs/getting_started/first_2d_game/07.finishing-up.rst:102
msgid ""
"Create a new :ref:`InputEventAction <class_InputEventAction>` and name it "
"``start_game``."
msgstr ""

#: ../../docs/getting_started/first_2d_game/07.finishing-up.rst:106
msgid ""
"Now when the start button appears, you can either click it or press :kbd:"
"`Enter` to start the game."
msgstr ""

#: ../../docs/getting_started/first_2d_game/07.finishing-up.rst:109
msgid "And with that, you completed your first 2D game in Godot."
msgstr ""

#: ../../docs/getting_started/first_2d_game/07.finishing-up.rst:113
msgid ""
"You got to make a player-controlled character, enemies that spawn randomly "
"around the game board, count the score, implement a game over and replay, "
"user interface, sounds, and more. Congratulations!"
msgstr ""

#: ../../docs/getting_started/first_2d_game/07.finishing-up.rst:117
msgid ""
"There's still much to learn, but you can take a moment to appreciate what "
"you achieved."
msgstr ""

#: ../../docs/getting_started/first_2d_game/07.finishing-up.rst:120
msgid ""
"And when you're ready, you can move on to :ref:`doc_your_first_3d_game` to "
"learn to create a complete 3D game from scratch, in Godot."
msgstr ""

#: ../../docs/getting_started/first_3d_game/index.rst:6
msgid "Your first 3D game"
msgstr ""

#: ../../docs/getting_started/first_3d_game/index.rst:8
msgid ""
"In this step-by-step tutorial series, you will create your first complete 3D "
"game with Godot. By the end of the series, you will have a simple yet "
"finished project of your own like the animated gif below."
msgstr ""

#: ../../docs/getting_started/first_3d_game/index.rst:14
msgid ""
"The game we'll code here is similar to :ref:`doc_your_first_2d_game`, with a "
"twist: you can now jump and your goal is to squash the creeps. This way, you "
"will both **recognize patterns** you learned in the previous tutorial and "
"**build upon them** with new code and features."
msgstr ""

#: ../../docs/getting_started/first_3d_game/index.rst:21
msgid "Work with 3D coordinates with a jumping mechanic."
msgstr ""

#: ../../docs/getting_started/first_3d_game/index.rst:22
msgid ""
"Use kinematic bodies to move 3D characters and detect when and how they "
"collide."
msgstr ""

#: ../../docs/getting_started/first_3d_game/index.rst:24
msgid ""
"Use physics layers and a group to detect interactions with specific entities."
msgstr ""

#: ../../docs/getting_started/first_3d_game/index.rst:25
msgid ""
"Code basic procedural gameplay by instancing monsters at regular time "
"intervals."
msgstr ""

#: ../../docs/getting_started/first_3d_game/index.rst:27
msgid "Design a movement animation and change its speed at run-time."
msgstr ""

#: ../../docs/getting_started/first_3d_game/index.rst:28
msgid "Draw a user interface on a 3D game."
msgstr ""

#: ../../docs/getting_started/first_3d_game/index.rst:32
msgid ""
"This tutorial is for beginners who followed the complete getting started "
"series. We'll start slow with detailed instructions and shorten them as we "
"do similar steps. If you're an experienced programmer, you can browse the "
"complete demo's source code here: `Squash the Creep source code <https://"
"github.com/godotengine/godot-3d-dodge-the-creeps>`__."
msgstr ""

#: ../../docs/getting_started/first_3d_game/index.rst:40
msgid ""
"You can follow this series without having done the 2D one. However, if "
"you're new to game development, we recommend you to start with 2D. 3D game "
"code is always more complex and the 2D series will give you foundations to "
"follow along more comfortably."
msgstr ""

#: ../../docs/getting_started/first_3d_game/index.rst:45
msgid ""
"We prepared some game assets so we can jump straight to the code. You can "
"download them here: `Squash the Creeps assets <https://github.com/"
"godotengine/godot-3d-dodge-the-creeps/releases/tag/1.1.0>`__."
msgstr ""

#: ../../docs/getting_started/first_3d_game/index.rst:49
msgid ""
"We will first work on a basic prototype for the player's movement. We will "
"then add the monsters that we'll spawn randomly around the screen. After "
"that, we'll implement the jump and squashing mechanic before refining the "
"game with some nice animation. We'll wrap up with the score and the retry "
"screen."
msgstr ""

#: ../../docs/getting_started/first_3d_game/01.game_setup.rst:6
#, fuzzy
msgid "Setting up the game area"
msgstr "Kreiranje Sadržaja"

#: ../../docs/getting_started/first_3d_game/01.game_setup.rst:8
msgid ""
"In this first part, we're going to set up the game area. Let's get started "
"by importing the start assets and setting up the game scene."
msgstr ""

#: ../../docs/getting_started/first_3d_game/01.game_setup.rst:11
msgid ""
"We've prepared a Godot project with the 3D models and sounds we'll use for "
"this tutorial, linked in the index page. If you haven't done so yet, you can "
"download the archive here: `Squash the Creeps assets <https://github.com/"
"godotengine/godot-3d-dodge-the-creeps/releases/tag/1.1.0>`__."
msgstr ""

#: ../../docs/getting_started/first_3d_game/01.game_setup.rst:16
msgid ""
"Once you downloaded it, extract the .zip archive on your computer. Open the "
"Godot Project Manager and click the *Import* button."
msgstr ""

#: ../../docs/getting_started/first_3d_game/01.game_setup.rst:21
msgid ""
"In the import popup, enter the full path to the freshly created directory "
"``squash_the_creeps_start/``. You can click the *Browse* button on the right "
"to open a file browser and navigate to the ``project.godot`` file the folder "
"contains."
msgstr ""

#: ../../docs/getting_started/first_3d_game/01.game_setup.rst:28
msgid "Click *Import & Edit* to open the project in the editor."
msgstr ""

#: ../../docs/getting_started/first_3d_game/01.game_setup.rst:32
msgid ""
"The start project contains an icon and two folders: ``art/`` and ``fonts/``. "
"There, you will find the art assets and music we'll use in the game."
msgstr ""

#: ../../docs/getting_started/first_3d_game/01.game_setup.rst:37
msgid ""
"There are two 3D models, ``player.glb`` and ``mob.glb``, some materials that "
"belong to these models, and a music track."
msgstr ""

#: ../../docs/getting_started/first_3d_game/01.game_setup.rst:41
msgid "Setting up the playable area"
msgstr ""

#: ../../docs/getting_started/first_3d_game/01.game_setup.rst:43
msgid ""
"We're going to create our main scene with a plain :ref:`Node <class_Node>` "
"as its root. In the *Scene* dock, click the *Add Child Node* button "
"represented by a \"+\" icon in the top-left and double-click on *Node*. Name "
"the node ``Main``. An alternate method to rename the node is to right-click "
"on *Node* and choose *Rename* (or :kbd:`F2`). Alternatively, to add a node "
"to the scene, you can press :kbd:`Ctrl + a` (or :kbd:`Cmd + a` on macOS)."
msgstr ""

#: ../../docs/getting_started/first_3d_game/01.game_setup.rst:50
msgid ""
"Save the scene as ``main.tscn`` by pressing :kbd:`Ctrl + s` (:kbd:`Cmd + s` "
"on macOS)."
msgstr ""

#: ../../docs/getting_started/first_3d_game/01.game_setup.rst:52
msgid ""
"We'll start by adding a floor that'll prevent the characters from falling. "
"To create static colliders like the floor, walls, or ceilings, you can use :"
"ref:`StaticBody3D <class_StaticBody3D>` nodes. They require :ref:"
"`CollisionShape3D <class_CollisionShape3D>` child nodes to define the "
"collision area. With the ``Main`` node selected, add a :ref:`StaticBody3D "
"<class_StaticBody3D>` node, then a :ref:`CollisionShape3D "
"<class_CollisionShape3D>`. Rename the :ref:`StaticBody3D "
"<class_StaticBody3D>` to ``Ground``."
msgstr ""

#: ../../docs/getting_started/first_3d_game/01.game_setup.rst:59
msgid "Your scene tree should look like this"
msgstr ""

#: ../../docs/getting_started/first_3d_game/01.game_setup.rst:63
msgid ""
"A warning sign next to the :ref:`CollisionShape3D <class_CollisionShape3D>` "
"appears because we haven't defined its shape. If you click the icon, a popup "
"appears to give you more information."
msgstr ""

#: ../../docs/getting_started/first_3d_game/01.game_setup.rst:68
msgid ""
"To create a shape, select the :ref:`CollisionShape3D "
"<class_CollisionShape3D>` node, head to the *Inspector* and click the "
"*<empty>* field next to the *Shape* property. Create a new *BoxShape3D*."
msgstr ""

#: ../../docs/getting_started/first_3d_game/01.game_setup.rst:73
msgid ""
"The box shape is perfect for flat ground and walls. Its thickness makes it "
"reliable to block even fast-moving objects."
msgstr ""

#: ../../docs/getting_started/first_3d_game/01.game_setup.rst:76
msgid ""
"A box's wireframe appears in the viewport with three orange dots. You can "
"click and drag these to edit the shape's extents interactively. We can also "
"precisely set the size in the inspector. Click on the :ref:`BoxShape3D "
"<class_BoxShape3D>` to expand the resource. Set its *Size* to ``60`` on the "
"X axis, ``2`` for the Y axis, and ``60`` for the Z axis."
msgstr ""

#: ../../docs/getting_started/first_3d_game/01.game_setup.rst:85
msgid ""
"Collision shapes are invisible. We need to add a visual floor that goes "
"along with it. Select the ``Ground`` node and add a :ref:`MeshInstance3D "
"<class_MeshInstance3D>` as its child."
msgstr ""

#: ../../docs/getting_started/first_3d_game/01.game_setup.rst:90
msgid ""
"In the *Inspector*, click on the field next to *Mesh* and create a :ref:"
"`BoxMesh <class_BoxMesh>` resource to create a visible box."
msgstr ""

#: ../../docs/getting_started/first_3d_game/01.game_setup.rst:95
msgid ""
"Once again, it's too small by default. Click the box icon to expand the "
"resource and set its *Size* to ``60``, ``2``, and ``60``."
msgstr ""

#: ../../docs/getting_started/first_3d_game/01.game_setup.rst:100
msgid ""
"You should see a wide grey slab that covers the grid and blue and red axes "
"in the viewport."
msgstr ""

#: ../../docs/getting_started/first_3d_game/01.game_setup.rst:103
msgid ""
"We're going to move the ground down so we can see the floor grid. Select the "
"``Ground`` node, hold the :kbd:`Ctrl` key down to turn on grid snapping, and "
"click and drag down on the Y axis. It's the green arrow in the move gizmo."
msgstr ""

#: ../../docs/getting_started/first_3d_game/01.game_setup.rst:111
msgid ""
"If you can't see the 3D object manipulator like on the image above, ensure "
"the *Select Mode* is active in the toolbar above the view."
msgstr ""

#: ../../docs/getting_started/first_3d_game/01.game_setup.rst:116
msgid ""
"Move the ground down ``1`` meter, in order to have a visible editor grid. A "
"label in the bottom-left corner of the viewport tells you how much you're "
"translating the node."
msgstr ""

#: ../../docs/getting_started/first_3d_game/01.game_setup.rst:123
msgid ""
"Moving the *Ground* node down moves both children along with it. Ensure you "
"move the *Ground* node, **not** the *MeshInstance3D* or the "
"*CollisionShape3D*."
msgstr ""

#: ../../docs/getting_started/first_3d_game/01.game_setup.rst:127
msgid "Ultimately, ``Ground``'s transform.position.y should be -1"
msgstr ""

#: ../../docs/getting_started/first_3d_game/01.game_setup.rst:131
msgid ""
"Let's add a directional light so our scene isn't all grey. Select the "
"``Main`` node and add a child node :ref:`DirectionalLight3D "
"<class_DirectionalLight3D>`."
msgstr ""

#: ../../docs/getting_started/first_3d_game/01.game_setup.rst:136
msgid ""
"We need to move and rotate the :ref:`DirectionalLight3D "
"<class_DirectionalLight3D>` node. Move it up by clicking and dragging on the "
"manipulator's green arrow and click and drag on the red arc to rotate it "
"around the X axis, until the ground is lit."
msgstr ""

#: ../../docs/getting_started/first_3d_game/01.game_setup.rst:141
msgid ""
"In the *Inspector*, turn on *Shadow -> Enabled* by clicking the checkbox."
msgstr ""

#: ../../docs/getting_started/first_3d_game/01.game_setup.rst:145
msgid "At this point, your project should look like this."
msgstr ""

#: ../../docs/getting_started/first_3d_game/01.game_setup.rst:149
msgid ""
"That's our starting point. In the next part, we will work on the player "
"scene and base movement."
msgstr ""

#: ../../docs/getting_started/first_3d_game/02.player_input.rst:6
msgid "Player scene and input actions"
msgstr ""

#: ../../docs/getting_started/first_3d_game/02.player_input.rst:8
msgid ""
"In the next two lessons, we will design the player scene, register custom "
"input actions, and code player movement. By the end, you'll have a playable "
"character that moves in eight directions."
msgstr ""

#: ../../docs/getting_started/first_3d_game/02.player_input.rst:15
msgid ""
"Create a new scene by going to the Scene menu in the top-left and clicking "
"*New Scene*."
msgstr ""

#: ../../docs/getting_started/first_3d_game/02.player_input.rst:20
msgid ""
"Create a :ref:`CharacterBody3D <class_CharacterBody3D>` node as the root"
msgstr ""

#: ../../docs/getting_started/first_3d_game/02.player_input.rst:24
msgid ""
"Name the :ref:`CharacterBody3D <class_CharacterBody3D>` to ``Player``. "
"Character bodies are complementary to the area and rigid bodies used in the "
"2D game tutorial. Like rigid bodies, they can move and collide with the "
"environment, but instead of being controlled by the physics engine, **you** "
"dictate their movement. You will see how we use the node's unique features "
"when we code the jump and squash mechanics."
msgstr ""

#: ../../docs/getting_started/first_3d_game/02.player_input.rst:33
msgid ""
"To learn more about the different physics node types, see the :ref:"
"`doc_physics_introduction`."
msgstr ""

#: ../../docs/getting_started/first_3d_game/02.player_input.rst:36
msgid ""
"For now, we're going to create a basic rig for our character's 3D model. "
"This will allow us to rotate the model later via code while it plays an "
"animation."
msgstr ""

#: ../../docs/getting_started/first_3d_game/02.player_input.rst:39
msgid ""
"Add a :ref:`Node3D <class_Node3D>` node as a child of ``Player`` and name it "
"``Pivot``"
msgstr ""

#: ../../docs/getting_started/first_3d_game/02.player_input.rst:43
msgid ""
"Then, in the FileSystem dock, expand the ``art/`` folder by double-clicking "
"it and drag and drop ``player.glb`` onto ``Pivot``."
msgstr ""

#: ../../docs/getting_started/first_3d_game/02.player_input.rst:49
msgid ""
"This should instantiate the model as a child of ``Pivot``. You can rename it "
"to ``Character``."
msgstr ""

#: ../../docs/getting_started/first_3d_game/02.player_input.rst:56
msgid ""
"The ``.glb`` files contain 3D scene data based on the open source GLTF 2.0 "
"specification. They're a modern and powerful alternative to a proprietary "
"format like FBX, which Godot also supports. To produce these files, we "
"designed the model in `Blender 3D <https://www.blender.org/>`__ and exported "
"it to GLTF."
msgstr ""

#: ../../docs/getting_started/first_3d_game/02.player_input.rst:61
msgid ""
"As with all kinds of physics nodes, we need a collision shape for our "
"character to collide with the environment. Select the ``Player`` node again "
"and add a child node :ref:`CollisionShape3D <class_CollisionShape3D>`. In "
"the *Inspector*, on the *Shape* property, add a new :ref:`SphereShape3D "
"<class_SphereShape3D>`."
msgstr ""

#: ../../docs/getting_started/first_3d_game/02.player_input.rst:67
msgid "The sphere's wireframe appears below the character."
msgstr ""

#: ../../docs/getting_started/first_3d_game/02.player_input.rst:69
#: ../../docs/getting_started/first_3d_game/03.player_movement_code.rst:370
#: ../../docs/getting_started/first_3d_game/05.spawning_mobs.rst:44
#: ../../docs/getting_started/first_3d_game/06.jump_and_squash.rst:66
#: ../../docs/getting_started/first_3d_game/07.killing_player.rst:50
#: ../../docs/getting_started/first_3d_game/08.score_and_replay.rst:33
#: ../../docs/getting_started/first_3d_game/09.adding_animations.rst:38
#: ../../docs/community/asset_library/using_assetlib.rst:81
msgid "|image3|"
msgstr ""

#: ../../docs/getting_started/first_3d_game/02.player_input.rst:169
#: ../../docs/getting_started/first_3d_game/03.player_movement_code.rst:441
#: ../../docs/getting_started/first_3d_game/05.spawning_mobs.rst:337
#: ../../docs/getting_started/first_3d_game/06.jump_and_squash.rst:371
#: ../../docs/getting_started/first_3d_game/07.killing_player.rst:529
#: ../../docs/getting_started/first_3d_game/08.score_and_replay.rst:453
#: ../../docs/getting_started/first_3d_game/09.adding_animations.rst:611
#: ../../docs/community/asset_library/using_assetlib.rst:190
msgid "image3"
msgstr ""

#: ../../docs/getting_started/first_3d_game/02.player_input.rst:71
msgid ""
"It will be the shape the physics engine uses to collide with the "
"environment, so we want it to better fit the 3D model. Shrink it a bit by "
"dragging the orange dot in the viewport. My sphere has a radius of about "
"``0.8`` meters."
msgstr ""

#: ../../docs/getting_started/first_3d_game/02.player_input.rst:75
msgid ""
"Then, move the shape up so its bottom roughly aligns with the grid's plane."
msgstr ""

#: ../../docs/getting_started/first_3d_game/02.player_input.rst:79
msgid ""
"You can toggle the model's visibility by clicking the eye icon next to the "
"``Character`` or the ``Pivot`` nodes."
msgstr ""

#: ../../docs/getting_started/first_3d_game/02.player_input.rst:84
#, fuzzy
msgid "Save the scene as ``player.tscn``"
msgstr "Kreiranje Sadržaja"

#: ../../docs/getting_started/first_3d_game/02.player_input.rst:86
msgid ""
"With the nodes ready, we can almost get coding. But first, we need to define "
"some input actions."
msgstr ""

#: ../../docs/getting_started/first_3d_game/02.player_input.rst:90
#, fuzzy
msgid "Creating input actions"
msgstr "Kreiranje Sadržaja"

#: ../../docs/getting_started/first_3d_game/02.player_input.rst:92
msgid ""
"To move the character, we will listen to the player's input, like pressing "
"the arrow keys. In Godot, while we could write all the key bindings in code, "
"there's a powerful system that allows you to assign a label to a set of keys "
"and buttons. This simplifies our scripts and makes them more readable."
msgstr ""

#: ../../docs/getting_started/first_3d_game/02.player_input.rst:97
msgid ""
"This system is the Input Map. To access its editor, head to the *Project* "
"menu and select *Project Settings*."
msgstr ""

#: ../../docs/getting_started/first_3d_game/02.player_input.rst:100
#: ../../docs/getting_started/first_3d_game/03.player_movement_code.rst:391
#: ../../docs/getting_started/first_3d_game/04.mob_scene.rst:89
#: ../../docs/getting_started/first_3d_game/05.spawning_mobs.rst:61
#: ../../docs/getting_started/first_3d_game/06.jump_and_squash.rst:92
#: ../../docs/getting_started/first_3d_game/08.score_and_replay.rst:55
#: ../../docs/getting_started/first_3d_game/09.adding_animations.rst:57
#: ../../docs/community/asset_library/using_assetlib.rst:99
msgid "|image6|"
msgstr ""

#: ../../docs/getting_started/first_3d_game/02.player_input.rst:172
#: ../../docs/getting_started/first_3d_game/03.player_movement_code.rst:444
#: ../../docs/getting_started/first_3d_game/04.mob_scene.rst:341
#: ../../docs/getting_started/first_3d_game/05.spawning_mobs.rst:340
#: ../../docs/getting_started/first_3d_game/06.jump_and_squash.rst:374
#: ../../docs/getting_started/first_3d_game/08.score_and_replay.rst:456
#: ../../docs/getting_started/first_3d_game/09.adding_animations.rst:614
#: ../../docs/community/asset_library/using_assetlib.rst:193
msgid "image6"
msgstr ""

#: ../../docs/getting_started/first_3d_game/02.player_input.rst:102
msgid ""
"At the top, there are multiple tabs. Click on *Input Map*. This window "
"allows you to add new actions at the top; they are your labels. In the "
"bottom part, you can bind keys to these actions."
msgstr ""

#: ../../docs/getting_started/first_3d_game/02.player_input.rst:106
#: ../../docs/getting_started/first_3d_game/03.player_movement_code.rst:396
#: ../../docs/getting_started/first_3d_game/04.mob_scene.rst:101
#: ../../docs/getting_started/first_3d_game/05.spawning_mobs.rst:66
#: ../../docs/getting_started/first_3d_game/06.jump_and_squash.rst:191
#: ../../docs/getting_started/first_3d_game/08.score_and_replay.rst:74
#: ../../docs/getting_started/first_3d_game/09.adding_animations.rst:61
#: ../../docs/community/asset_library/using_assetlib.rst:125
msgid "|image7|"
msgstr ""

#: ../../docs/getting_started/first_3d_game/02.player_input.rst:173
#: ../../docs/getting_started/first_3d_game/03.player_movement_code.rst:445
#: ../../docs/getting_started/first_3d_game/04.mob_scene.rst:342
#: ../../docs/getting_started/first_3d_game/05.spawning_mobs.rst:341
#: ../../docs/getting_started/first_3d_game/06.jump_and_squash.rst:375
#: ../../docs/getting_started/first_3d_game/08.score_and_replay.rst:457
#: ../../docs/getting_started/first_3d_game/09.adding_animations.rst:615
#: ../../docs/community/asset_library/using_assetlib.rst:194
msgid "image7"
msgstr ""

#: ../../docs/getting_started/first_3d_game/02.player_input.rst:108
msgid ""
"Godot projects come with some predefined actions designed for user interface "
"design, which we could use here. But we're defining our own to support "
"gamepads."
msgstr ""

#: ../../docs/getting_started/first_3d_game/02.player_input.rst:111
msgid ""
"We're going to name our actions ``move_left``, ``move_right``, "
"``move_forward``, ``move_back``, and ``jump``."
msgstr ""

#: ../../docs/getting_started/first_3d_game/02.player_input.rst:114
msgid "To add an action, write its name in the bar at the top and press Enter."
msgstr ""

#: ../../docs/getting_started/first_3d_game/02.player_input.rst:116
#: ../../docs/getting_started/first_3d_game/03.player_movement_code.rst:402
#: ../../docs/getting_started/first_3d_game/04.mob_scene.rst:224
#: ../../docs/getting_started/first_3d_game/05.spawning_mobs.rst:72
#: ../../docs/getting_started/first_3d_game/06.jump_and_squash.rst:196
#: ../../docs/getting_started/first_3d_game/08.score_and_replay.rst:108
#: ../../docs/getting_started/first_3d_game/09.adding_animations.rst:66
#: ../../docs/community/asset_library/using_assetlib.rst:133
msgid "|image8|"
msgstr ""

#: ../../docs/getting_started/first_3d_game/02.player_input.rst:174
#: ../../docs/getting_started/first_3d_game/03.player_movement_code.rst:446
#: ../../docs/getting_started/first_3d_game/04.mob_scene.rst:343
#: ../../docs/getting_started/first_3d_game/05.spawning_mobs.rst:342
#: ../../docs/getting_started/first_3d_game/06.jump_and_squash.rst:376
#: ../../docs/getting_started/first_3d_game/08.score_and_replay.rst:458
#: ../../docs/getting_started/first_3d_game/09.adding_animations.rst:616
#: ../../docs/community/asset_library/using_assetlib.rst:195
msgid "image8"
msgstr ""

#: ../../docs/getting_started/first_3d_game/02.player_input.rst:118
#, fuzzy
msgid "Create the following five actions:"
msgstr "Kreiranje Sadržaja"

#: ../../docs/getting_started/first_3d_game/02.player_input.rst:120
#: ../../docs/getting_started/first_3d_game/03.player_movement_code.rst:407
#: ../../docs/getting_started/first_3d_game/04.mob_scene.rst:229
#: ../../docs/getting_started/first_3d_game/05.spawning_mobs.rst:77
#: ../../docs/getting_started/first_3d_game/08.score_and_replay.rst:169
#: ../../docs/getting_started/first_3d_game/09.adding_animations.rst:71
#: ../../docs/community/asset_library/using_assetlib.rst:154
msgid "|image9|"
msgstr ""

#: ../../docs/getting_started/first_3d_game/02.player_input.rst:175
#: ../../docs/getting_started/first_3d_game/03.player_movement_code.rst:447
#: ../../docs/getting_started/first_3d_game/04.mob_scene.rst:344
#: ../../docs/getting_started/first_3d_game/05.spawning_mobs.rst:343
#: ../../docs/getting_started/first_3d_game/08.score_and_replay.rst:459
#: ../../docs/getting_started/first_3d_game/09.adding_animations.rst:617
#: ../../docs/community/asset_library/using_assetlib.rst:196
msgid "image9"
msgstr ""

#: ../../docs/getting_started/first_3d_game/02.player_input.rst:122
msgid ""
"To bind a key or button to an action, click the \"+\" button to its right. "
"Do this for ``move_left``. Press the left arrow key and click *OK*."
msgstr ""

#: ../../docs/getting_started/first_3d_game/02.player_input.rst:127
msgid "Bind also the :kbd:`A` key, onto the action ``move_left``."
msgstr ""

#: ../../docs/getting_started/first_3d_game/02.player_input.rst:129
#: ../../docs/getting_started/first_3d_game/05.spawning_mobs.rst:103
#: ../../docs/getting_started/first_3d_game/08.score_and_replay.rst:202
#: ../../docs/getting_started/first_3d_game/09.adding_animations.rst:100
#: ../../docs/community/asset_library/using_assetlib.rst:173
msgid "|image12|"
msgstr ""

#: ../../docs/getting_started/first_3d_game/02.player_input.rst:177
#: ../../docs/getting_started/first_3d_game/05.spawning_mobs.rst:346
#: ../../docs/getting_started/first_3d_game/08.score_and_replay.rst:462
#: ../../docs/getting_started/first_3d_game/09.adding_animations.rst:620
#: ../../docs/community/asset_library/using_assetlib.rst:199
msgid "image12"
msgstr ""

#: ../../docs/getting_started/first_3d_game/02.player_input.rst:131
msgid ""
"Let's now add support for a gamepad's left joystick. Click the \"+\" button "
"again but this time, select *Manual Selection -> Joypad Axes*."
msgstr ""

#: ../../docs/getting_started/first_3d_game/02.player_input.rst:136
msgid "Select the negative X axis of the left joystick."
msgstr ""

#: ../../docs/getting_started/first_3d_game/02.player_input.rst:140
msgid "Leave the other values as default and press *OK*"
msgstr ""

#: ../../docs/getting_started/first_3d_game/02.player_input.rst:144
msgid ""
"If you want controllers to have different input actions, you should use the "
"Devices option in Additional Options. Device 0 corresponds to the first "
"plugged gamepad, Device 1 corresponds to the second plugged gamepad, and so "
"on."
msgstr ""

#: ../../docs/getting_started/first_3d_game/02.player_input.rst:146
msgid ""
"Do the same for the other input actions. For example, bind the right arrow, "
"D, and the left joystick's positive axis to ``move_right``. After binding "
"all keys, your interface should look like this."
msgstr ""

#: ../../docs/getting_started/first_3d_game/02.player_input.rst:150
#: ../../docs/getting_started/first_3d_game/05.spawning_mobs.rst:128
#: ../../docs/getting_started/first_3d_game/08.score_and_replay.rst:312
#: ../../docs/getting_started/first_3d_game/09.adding_animations.rst:137
msgid "|image15|"
msgstr ""

#: ../../docs/getting_started/first_3d_game/02.player_input.rst:178
#: ../../docs/getting_started/first_3d_game/05.spawning_mobs.rst:349
#: ../../docs/getting_started/first_3d_game/08.score_and_replay.rst:465
#: ../../docs/getting_started/first_3d_game/09.adding_animations.rst:623
msgid "image15"
msgstr ""

#: ../../docs/getting_started/first_3d_game/02.player_input.rst:152
msgid ""
"The final action to set up is the ``jump`` action. Bind the Space key and "
"the gamepad's A button."
msgstr ""

#: ../../docs/getting_started/first_3d_game/02.player_input.rst:155
#: ../../docs/getting_started/first_3d_game/05.spawning_mobs.rst:133
#: ../../docs/getting_started/first_3d_game/08.score_and_replay.rst:317
#: ../../docs/getting_started/first_3d_game/09.adding_animations.rst:148
msgid "|image16|"
msgstr ""

#: ../../docs/getting_started/first_3d_game/02.player_input.rst:179
#: ../../docs/getting_started/first_3d_game/05.spawning_mobs.rst:350
#: ../../docs/getting_started/first_3d_game/08.score_and_replay.rst:466
#: ../../docs/getting_started/first_3d_game/09.adding_animations.rst:624
msgid "image16"
msgstr ""

#: ../../docs/getting_started/first_3d_game/02.player_input.rst:157
msgid "Your jump input action should look like this."
msgstr ""

#: ../../docs/getting_started/first_3d_game/02.player_input.rst:159
#: ../../docs/getting_started/first_3d_game/05.spawning_mobs.rst:145
#: ../../docs/getting_started/first_3d_game/08.score_and_replay.rst:335
#: ../../docs/getting_started/first_3d_game/09.adding_animations.rst:159
msgid "|image18|"
msgstr ""

#: ../../docs/getting_started/first_3d_game/02.player_input.rst:181
#: ../../docs/getting_started/first_3d_game/05.spawning_mobs.rst:352
#: ../../docs/getting_started/first_3d_game/08.score_and_replay.rst:468
#: ../../docs/getting_started/first_3d_game/09.adding_animations.rst:626
msgid "image18"
msgstr ""

#: ../../docs/getting_started/first_3d_game/02.player_input.rst:161
msgid ""
"That's all the actions we need for this game. You can use this menu to label "
"any groups of keys and buttons in your projects."
msgstr ""

#: ../../docs/getting_started/first_3d_game/02.player_input.rst:164
msgid "In the next part, we'll code and test the player's movement."
msgstr ""

#: ../../docs/getting_started/first_3d_game/02.player_input.rst:176
#: ../../docs/getting_started/first_3d_game/03.player_movement_code.rst:449
#: ../../docs/getting_started/first_3d_game/05.spawning_mobs.rst:345
#: ../../docs/getting_started/first_3d_game/08.score_and_replay.rst:461
#: ../../docs/getting_started/first_3d_game/09.adding_animations.rst:619
#: ../../docs/community/asset_library/using_assetlib.rst:198
msgid "image11"
msgstr ""

#: ../../docs/getting_started/first_3d_game/02.player_input.rst:180
#: ../../docs/getting_started/first_3d_game/05.spawning_mobs.rst:351
#: ../../docs/getting_started/first_3d_game/08.score_and_replay.rst:467
#: ../../docs/getting_started/first_3d_game/09.adding_animations.rst:625
msgid "image17"
msgstr ""

#: ../../docs/getting_started/first_3d_game/03.player_movement_code.rst:6
msgid "Moving the player with code"
msgstr ""

#: ../../docs/getting_started/first_3d_game/03.player_movement_code.rst:8
msgid ""
"It's time to code! We're going to use the input actions we created in the "
"last part to move the character."
msgstr ""

#: ../../docs/getting_started/first_3d_game/03.player_movement_code.rst:11
msgid ""
"Right-click the ``Player`` node and select *Attach Script* to add a new "
"script to it. In the popup, set the *Template* to *Empty* before pressing "
"the *Create* button."
msgstr ""

#: ../../docs/getting_started/first_3d_game/03.player_movement_code.rst:17
msgid ""
"Let's start with the class's properties. We're going to define a movement "
"speed, a fall acceleration representing gravity, and a velocity we'll use to "
"move the character."
msgstr ""

#: ../../docs/getting_started/first_3d_game/03.player_movement_code.rst:52
msgid ""
"These are common properties for a moving body. The ``target_velocity`` is a :"
"ref:`3D vector <class_Vector3>` combining a speed with a direction. Here, we "
"define it as a property because we want to update and reuse its value across "
"frames."
msgstr ""

#: ../../docs/getting_started/first_3d_game/03.player_movement_code.rst:58
msgid ""
"The values are quite different from 2D code because distances are in meters. "
"While in 2D, a thousand units (pixels) may only correspond to half of your "
"screen's width, in 3D, it's a kilometer."
msgstr ""

#: ../../docs/getting_started/first_3d_game/03.player_movement_code.rst:62
msgid ""
"Let's code the movement. We start by calculating the input direction vector "
"using the global ``Input`` object, in ``_physics_process()``."
msgstr ""

#: ../../docs/getting_started/first_3d_game/03.player_movement_code.rst:112
msgid ""
"Here, we're going to make all calculations using the ``_physics_process()`` "
"virtual function. Like ``_process()``, it allows you to update the node "
"every frame, but it's designed specifically for physics-related code like "
"moving a kinematic or rigid body."
msgstr ""

#: ../../docs/getting_started/first_3d_game/03.player_movement_code.rst:119
msgid ""
"To learn more about the difference between ``_process()`` and "
"``_physics_process()``, see :ref:`doc_idle_and_physics_processing`."
msgstr ""

#: ../../docs/getting_started/first_3d_game/03.player_movement_code.rst:122
msgid ""
"We start by initializing a ``direction`` variable to ``Vector3.ZERO``. Then, "
"we check if the player is pressing one or more of the ``move_*`` inputs and "
"update the vector's ``x`` and ``z`` components accordingly. These correspond "
"to the ground plane's axes."
msgstr ""

#: ../../docs/getting_started/first_3d_game/03.player_movement_code.rst:127
msgid ""
"These four conditions give us eight possibilities and eight possible "
"directions."
msgstr ""

#: ../../docs/getting_started/first_3d_game/03.player_movement_code.rst:129
msgid ""
"In case the player presses, say, both W and D simultaneously, the vector "
"will have a length of about ``1.4``. But if they press a single key, it will "
"have a length of ``1``. We want the vector's length to be consistent, and "
"not move faster diagonally. To do so, we can call its ``normalized()`` "
"method."
msgstr ""

#: ../../docs/getting_started/first_3d_game/03.player_movement_code.rst:159
msgid ""
"Here, we only normalize the vector if the direction has a length greater "
"than zero, which means the player is pressing a direction key."
msgstr ""

#: ../../docs/getting_started/first_3d_game/03.player_movement_code.rst:162
msgid ""
"We compute the direction the ``$Pivot`` is looking by creating a :ref:`Basis "
"<class_Basis>` that looks in the ``direction`` direction."
msgstr ""

#: ../../docs/getting_started/first_3d_game/03.player_movement_code.rst:165
msgid ""
"Then, we update the velocity. We have to calculate the ground velocity and "
"the fall speed separately. Be sure to go back one tab so the lines are "
"inside the ``_physics_process()`` function but outside the condition we just "
"wrote above."
msgstr ""

#: ../../docs/getting_started/first_3d_game/03.player_movement_code.rst:214
msgid ""
"The ``CharacterBody3D.is_on_floor()`` function returns ``true`` if the body "
"collided with the floor in this frame. That's why we apply gravity to the "
"``Player`` only while it is in the air."
msgstr ""

#: ../../docs/getting_started/first_3d_game/03.player_movement_code.rst:217
msgid ""
"For the vertical velocity, we subtract the fall acceleration multiplied by "
"the delta time every frame. This line of code will cause our character to "
"fall in every frame, as long as it is not on or colliding with the floor."
msgstr ""

#: ../../docs/getting_started/first_3d_game/03.player_movement_code.rst:221
msgid ""
"The physics engine can only detect interactions with walls, the floor, or "
"other bodies during a given frame if movement and collisions happen. We will "
"use this property later to code the jump."
msgstr ""

#: ../../docs/getting_started/first_3d_game/03.player_movement_code.rst:225
msgid ""
"On the last line, we call ``CharacterBody3D.move_and_slide()`` which is a "
"powerful method of the ``CharacterBody3D`` class that allows you to move a "
"character smoothly. If it hits a wall midway through a motion, the engine "
"will try to smooth it out for you. It uses the *velocity* value native to "
"the :ref:`CharacterBody3D <class_CharacterBody3D>`"
msgstr ""

#: ../../docs/getting_started/first_3d_game/03.player_movement_code.rst:237
msgid "And that's all the code you need to move the character on the floor."
msgstr ""

#: ../../docs/getting_started/first_3d_game/03.player_movement_code.rst:239
msgid "Here is the complete ``Player.gd`` code for reference."
msgstr ""

#: ../../docs/getting_started/first_3d_game/03.player_movement_code.rst:341
msgid "Testing our player's movement"
msgstr ""

#: ../../docs/getting_started/first_3d_game/03.player_movement_code.rst:343
msgid ""
"We're going to put our player in the ``Main`` scene to test it. To do so, we "
"need to instantiate the player and then add a camera. Unlike in 2D, in 3D, "
"you won't see anything if your viewport doesn't have a camera pointing at "
"something."
msgstr ""

#: ../../docs/getting_started/first_3d_game/03.player_movement_code.rst:347
msgid ""
"Save your ``Player`` scene and open the ``Main`` scene. You can click on the "
"*Main* tab at the top of the editor to do so."
msgstr ""

#: ../../docs/getting_started/first_3d_game/03.player_movement_code.rst:352
msgid ""
"If you closed the scene before, head to the *FileSystem* dock and double-"
"click ``main.tscn`` to re-open it."
msgstr ""

#: ../../docs/getting_started/first_3d_game/03.player_movement_code.rst:355
msgid ""
"To instantiate the ``Player``, right-click on the ``Main`` node and select "
"*Instantiate Child Scene*."
msgstr ""

#: ../../docs/getting_started/first_3d_game/03.player_movement_code.rst:360
msgid ""
"In the popup, double-click ``player.tscn``. The character should appear in "
"the center of the viewport."
msgstr ""

#: ../../docs/getting_started/first_3d_game/03.player_movement_code.rst:364
#, fuzzy
msgid "Adding a camera"
msgstr "Kreiranje Sadržaja"

#: ../../docs/getting_started/first_3d_game/03.player_movement_code.rst:366
msgid ""
"Let's add the camera next. Like we did with our *Player*\\ 's *Pivot*, we're "
"going to create a basic rig. Right-click on the ``Main`` node again and "
"select *Add Child Node*. Create a new :ref:`Marker3D <class_Marker3D>`, and "
"name it ``CameraPivot``. Select ``CameraPivot`` and add a child node :ref:"
"`Camera3D <class_Camera3D>` to it. Your scene tree should look like this."
msgstr ""

#: ../../docs/getting_started/first_3d_game/03.player_movement_code.rst:372
msgid ""
"Notice the *Preview* checkbox that appears in the top-left when you have the "
"*Camera* selected. You can click it to preview the in-game camera projection."
msgstr ""

#: ../../docs/getting_started/first_3d_game/03.player_movement_code.rst:377
msgid ""
"We're going to use the *Pivot* to rotate the camera as if it was on a crane. "
"Let's first split the 3D view to be able to freely navigate the scene and "
"see what the camera sees."
msgstr ""

#: ../../docs/getting_started/first_3d_game/03.player_movement_code.rst:381
msgid ""
"In the toolbar right above the viewport, click on *View*, then *2 "
"Viewports*. You can also press :kbd:`Ctrl + 2` (:kbd:`Cmd + 2` on macOS)."
msgstr ""

#: ../../docs/getting_started/first_3d_game/03.player_movement_code.rst:384
#: ../../docs/getting_started/first_3d_game/05.spawning_mobs.rst:91
#: ../../docs/getting_started/first_3d_game/08.score_and_replay.rst:197
#: ../../docs/getting_started/first_3d_game/09.adding_animations.rst:95
#: ../../docs/community/asset_library/using_assetlib.rst:165
msgid "|image11|"
msgstr ""

#: ../../docs/getting_started/first_3d_game/03.player_movement_code.rst:388
msgid ""
"On the bottom view, select your :ref:`Camera3D <class_Camera3D>` and turn on "
"camera Preview by clicking the checkbox."
msgstr ""

#: ../../docs/getting_started/first_3d_game/03.player_movement_code.rst:393
msgid ""
"In the top view, move the camera about ``19`` units on the Z axis (the blue "
"one)."
msgstr ""

#: ../../docs/getting_started/first_3d_game/03.player_movement_code.rst:398
msgid ""
"Here's where the magic happens. Select the *CameraPivot* and rotate it "
"``-45`` degrees around the X axis (using the red circle). You'll see the "
"camera move as if it was attached to a crane."
msgstr ""

#: ../../docs/getting_started/first_3d_game/03.player_movement_code.rst:404
msgid ""
"You can run the scene by pressing :kbd:`F6` and press the arrow keys to move "
"the character."
msgstr ""

#: ../../docs/getting_started/first_3d_game/03.player_movement_code.rst:409
msgid ""
"We can see some empty space around the character due to the perspective "
"projection. In this game, we're going to use an orthographic projection "
"instead to better frame the gameplay area and make it easier for the player "
"to read distances."
msgstr ""

#: ../../docs/getting_started/first_3d_game/03.player_movement_code.rst:414
msgid ""
"Select the *Camera* again and in the *Inspector*, set the *Projection* to "
"*Orthogonal* and the *Size* to ``19``. The character should now look flatter "
"and the ground should fill the background."
msgstr ""

#: ../../docs/getting_started/first_3d_game/03.player_movement_code.rst:420
msgid ""
"When using an orthogonal camera in Godot 4, directional shadow quality is "
"dependent on the camera's *Far* value. The higher the *Far* value, the "
"further away the camera will be able to see. However, higher *Far* values "
"also decrease shadow quality as the shadow rendering has to cover a greater "
"distance."
msgstr ""

#: ../../docs/getting_started/first_3d_game/03.player_movement_code.rst:426
msgid ""
"If directional shadows look too blurry after switching to an orthogonal "
"camera, decrease the camera's *Far* property to a lower value such as "
"``100``. Don't decrease this *Far* property too much, or objects in the "
"distance will start disappearing."
msgstr ""

#: ../../docs/getting_started/first_3d_game/03.player_movement_code.rst:431
#: ../../docs/getting_started/first_3d_game/04.mob_scene.rst:233
#: ../../docs/getting_started/first_3d_game/05.spawning_mobs.rst:87
#: ../../docs/getting_started/first_3d_game/08.score_and_replay.rst:193
#: ../../docs/getting_started/first_3d_game/09.adding_animations.rst:87
#: ../../docs/community/asset_library/using_assetlib.rst:160
msgid "|image10|"
msgstr ""

#: ../../docs/getting_started/first_3d_game/03.player_movement_code.rst:448
#: ../../docs/getting_started/first_3d_game/04.mob_scene.rst:345
#: ../../docs/getting_started/first_3d_game/05.spawning_mobs.rst:344
#: ../../docs/getting_started/first_3d_game/08.score_and_replay.rst:460
#: ../../docs/getting_started/first_3d_game/09.adding_animations.rst:618
#: ../../docs/community/asset_library/using_assetlib.rst:197
msgid "image10"
msgstr ""

#: ../../docs/getting_started/first_3d_game/03.player_movement_code.rst:433
msgid ""
"Test your scene and you should be able to move in all 8 directions and not "
"glitch through the floor!"
msgstr ""

#: ../../docs/getting_started/first_3d_game/03.player_movement_code.rst:435
msgid ""
"Ultimately, we have both player movement and the view in place. Next, we "
"will work on the monsters."
msgstr ""

#: ../../docs/getting_started/first_3d_game/04.mob_scene.rst:6
#, fuzzy
msgid "Designing the mob scene"
msgstr "Kreiranje Sadržaja"

#: ../../docs/getting_started/first_3d_game/04.mob_scene.rst:8
msgid ""
"In this part, you're going to code the monsters, which we'll call mobs. In "
"the next lesson, we'll spawn them randomly around the playable area."
msgstr ""

#: ../../docs/getting_started/first_3d_game/04.mob_scene.rst:11
msgid ""
"Let's design the monsters themselves in a new scene. The node structure is "
"going to be similar to the ``player.tscn`` scene."
msgstr ""

#: ../../docs/getting_started/first_3d_game/04.mob_scene.rst:14
msgid ""
"Create a scene with, once again, a :ref:`CharacterBody3D "
"<class_CharacterBody3D>` node as its root. Name it ``Mob``. Add a child "
"node :ref:`Node3D <class_Node3D>`, name it ``Pivot``. And drag and drop the "
"file ``mob.glb`` from the *FileSystem* dock onto the ``Pivot`` to add the "
"monster's 3D model to the scene."
msgstr ""

#: ../../docs/getting_started/first_3d_game/04.mob_scene.rst:21
msgid "You can rename the newly created ``mob`` node into ``Character``."
msgstr ""

#: ../../docs/getting_started/first_3d_game/04.mob_scene.rst:26
msgid ""
"We need a collision shape for our body to work. Right-click on the ``Mob`` "
"node, the scene's root, and click *Add Child Node*."
msgstr ""

#: ../../docs/getting_started/first_3d_game/04.mob_scene.rst:31
msgid "Add a :ref:`CollisionShape3D <class_CollisionShape3D>`."
msgstr ""

#: ../../docs/getting_started/first_3d_game/04.mob_scene.rst:36
msgid "In the *Inspector*, assign a *BoxShape3D* to the *Shape* property."
msgstr ""

#: ../../docs/getting_started/first_3d_game/04.mob_scene.rst:40
msgid ""
"We should change its size to fit the 3D model better. You can do so "
"interactively by clicking and dragging on the orange dots."
msgstr ""

#: ../../docs/getting_started/first_3d_game/04.mob_scene.rst:43
msgid ""
"The box should touch the floor and be a little thinner than the model. "
"Physics engines work in such a way that if the player's sphere touches even "
"the box's corner, a collision will occur. If the box is a little too big "
"compared to the 3D model, you may die at a distance from the monster, and "
"the game will feel unfair to the players."
msgstr ""

#: ../../docs/getting_started/first_3d_game/04.mob_scene.rst:51
msgid ""
"Notice that my box is taller than the monster. It is okay in this game "
"because we're looking at the scene from above and using a fixed perspective. "
"Collision shapes don't have to match the model exactly. It's the way the "
"game feels when you test it that should dictate their form and size."
msgstr ""

#: ../../docs/getting_started/first_3d_game/04.mob_scene.rst:57
msgid "Removing monsters off-screen"
msgstr ""

#: ../../docs/getting_started/first_3d_game/04.mob_scene.rst:59
msgid ""
"We're going to spawn monsters at regular time intervals in the game level. "
"If we're not careful, their count could increase to infinity, and we don't "
"want that. Each mob instance has both a memory and a processing cost, and we "
"don't want to pay for it when the mob is outside the screen."
msgstr ""

#: ../../docs/getting_started/first_3d_game/04.mob_scene.rst:64
msgid ""
"Once a monster leaves the screen, we don't need it anymore, so we should "
"delete it. Godot has a node that detects when objects leave the screen, :ref:"
"`VisibleOnScreenNotifier3D <class_VisibleOnScreenNotifier3D>`, and we're "
"going to use it to destroy our mobs."
msgstr ""

#: ../../docs/getting_started/first_3d_game/04.mob_scene.rst:70
msgid ""
"When you keep instancing an object, there's a technique you can use to avoid "
"the cost of creating and destroying instances all the time called pooling. "
"It consists of pre-creating an array of objects and reusing them over and "
"over."
msgstr ""

#: ../../docs/getting_started/first_3d_game/04.mob_scene.rst:75
msgid ""
"When working with GDScript, you don't need to worry about this. The main "
"reason to use pools is to avoid freezes with garbage-collected languages "
"like C# or Lua. GDScript uses a different technique to manage memory, "
"reference counting, which doesn't have that caveat. You can learn more about "
"that here: :ref:`doc_gdscript_basics_memory_management`."
msgstr ""

#: ../../docs/getting_started/first_3d_game/04.mob_scene.rst:81
msgid ""
"Select the ``Mob`` node and add a child node :ref:`VisibleOnScreenNotifier3D "
"<class_VisibleOnScreenNotifier3D>`. Another box, pink this time, appears. "
"When this box completely leaves the screen, the node will emit a signal."
msgstr ""

#: ../../docs/getting_started/first_3d_game/04.mob_scene.rst:87
msgid "Resize it using the orange dots until it covers the entire 3D model."
msgstr ""

#: ../../docs/getting_started/first_3d_game/04.mob_scene.rst:92
msgid "Coding the mob's movement"
msgstr ""

#: ../../docs/getting_started/first_3d_game/04.mob_scene.rst:94
msgid ""
"Let's implement the monster's motion. We're going to do this in two steps. "
"First, we'll write a script on the ``Mob`` that defines a function to "
"initialize the monster. We'll then code the randomized spawn mechanism in "
"the ``main.tscn`` scene and call the function from there."
msgstr ""

#: ../../docs/getting_started/first_3d_game/04.mob_scene.rst:99
msgid "Attach a script to the ``Mob``."
msgstr ""

#: ../../docs/getting_started/first_3d_game/04.mob_scene.rst:103
msgid ""
"Here's the movement code to start with. We define two properties, "
"``min_speed`` and ``max_speed``, to define a random speed range, which we "
"will later use to define ``CharacterBody3D.velocity``."
msgstr ""

#: ../../docs/getting_started/first_3d_game/04.mob_scene.rst:141
msgid ""
"Similarly to the player, we move the mob every frame by calling the function "
"``CharacterBody3D.move_and_slide()``. This time, we don't update the "
"``velocity`` every frame; we want the monster to move at a constant speed "
"and leave the screen, even if it were to hit an obstacle."
msgstr ""

#: ../../docs/getting_started/first_3d_game/04.mob_scene.rst:146
msgid ""
"We need to define another function to calculate the ``CharacterBody3D."
"velocity``. This function will turn the monster towards the player and "
"randomize both its angle of motion and its velocity."
msgstr ""

#: ../../docs/getting_started/first_3d_game/04.mob_scene.rst:150
msgid ""
"The function will take a ``start_position``,the mob's spawn position, and "
"the ``player_position`` as its arguments."
msgstr ""

#: ../../docs/getting_started/first_3d_game/04.mob_scene.rst:153
msgid ""
"We position the mob at ``start_position`` and turn it towards the player "
"using the ``look_at_from_position()`` method, and randomize the angle by "
"rotating a random amount around the Y axis. Below, ``randf_range()`` outputs "
"a random value between ``-PI / 4`` radians and ``PI / 4`` radians."
msgstr ""

#: ../../docs/getting_started/first_3d_game/04.mob_scene.rst:183
msgid ""
"We got a random position, now we need a ``random_speed``. ``randi_range()`` "
"will be useful as it gives random int values, and we will use ``min_speed`` "
"and ``max_speed``. ``random_speed`` is just an integer, and we just use it "
"to multiply our ``CharacterBody3D.velocity``. After ``random_speed`` is "
"applied, we rotate ``CharacterBody3D.velocity`` Vector3 towards the player."
msgstr ""

#: ../../docs/getting_started/first_3d_game/04.mob_scene.rst:216
#, fuzzy
msgid "Leaving the screen"
msgstr "Kreiranje Sadržaja"

#: ../../docs/getting_started/first_3d_game/04.mob_scene.rst:218
msgid ""
"We still have to destroy the mobs when they leave the screen. To do so, "
"we'll connect our :ref:`VisibleOnScreenNotifier3D "
"<class_VisibleOnScreenNotifier3D>` node's ``screen_exited`` signal to the "
"``Mob``."
msgstr ""

#: ../../docs/getting_started/first_3d_game/04.mob_scene.rst:221
msgid ""
"Head back to the 3D viewport by clicking on the *3D* label at the top of the "
"editor. You can also press :kbd:`Ctrl + F2` (:kbd:`Alt + 2` on macOS)."
msgstr ""

#: ../../docs/getting_started/first_3d_game/04.mob_scene.rst:226
msgid ""
"Select the :ref:`VisibleOnScreenNotifier3D "
"<class_VisibleOnScreenNotifier3D>` node and on the right side of the "
"interface, navigate to the *Node* dock. Double-click the ``screen_exited()`` "
"signal."
msgstr ""

#: ../../docs/getting_started/first_3d_game/04.mob_scene.rst:231
msgid "Connect the signal to the ``Mob``"
msgstr ""

#: ../../docs/getting_started/first_3d_game/04.mob_scene.rst:235
msgid ""
"This will take you back to the script editor and add a new function for you, "
"``_on_visible_on_screen_notifier_3d_screen_exited()``. From it, call the "
"``queue_free()`` method. This function destroys the instance it's called on."
msgstr ""

#: ../../docs/getting_started/first_3d_game/04.mob_scene.rst:254
msgid ""
"Our monster is ready to enter the game! In the next part, you will spawn "
"monsters in the game level."
msgstr ""

#: ../../docs/getting_started/first_3d_game/04.mob_scene.rst:257
msgid "Here is the complete ``Mob.gd`` script for reference."
msgstr ""

#: ../../docs/getting_started/first_3d_game/05.spawning_mobs.rst:6
#, fuzzy
msgid "Spawning monsters"
msgstr "Kreiranje Sadržaja"

#: ../../docs/getting_started/first_3d_game/05.spawning_mobs.rst:8
msgid ""
"In this part, we're going to spawn monsters along a path randomly. By the "
"end, you will have monsters roaming the game board."
msgstr ""

#: ../../docs/getting_started/first_3d_game/05.spawning_mobs.rst:13
msgid ""
"Double-click on ``main.tscn`` in the *FileSystem* dock to open the ``Main`` "
"scene."
msgstr ""

#: ../../docs/getting_started/first_3d_game/05.spawning_mobs.rst:15
msgid ""
"Before drawing the path, we're going to change the game resolution. Our game "
"has a default window size of ``1152x648``. We're going to set it to "
"``720x540``, a nice little box."
msgstr ""

#: ../../docs/getting_started/first_3d_game/05.spawning_mobs.rst:19
#, fuzzy
msgid "Go to *Project -> Project Settings*."
msgstr "Uvod / Početak"

#: ../../docs/getting_started/first_3d_game/05.spawning_mobs.rst:23
msgid ""
"In the left menu, navigate down to *Display -> Window*. On the right, set "
"the *Width* to ``720`` and the *Height* to ``540``."
msgstr ""

#: ../../docs/getting_started/first_3d_game/05.spawning_mobs.rst:29
#, fuzzy
msgid "Creating the spawn path"
msgstr "Kreiranje Sadržaja"

#: ../../docs/getting_started/first_3d_game/05.spawning_mobs.rst:31
msgid ""
"Like you did in the 2D game tutorial, you're going to design a path and use "
"a :ref:`PathFollow3D <class_PathFollow3D>` node to sample random locations "
"on it."
msgstr ""

#: ../../docs/getting_started/first_3d_game/05.spawning_mobs.rst:34
msgid ""
"In 3D though, it's a bit more complicated to draw the path. We want it to be "
"around the game view so monsters appear right outside the screen. But if we "
"draw a path, we won't see it from the camera preview."
msgstr ""

#: ../../docs/getting_started/first_3d_game/05.spawning_mobs.rst:38
msgid ""
"To find the view's limits, we can use some placeholder meshes. Your viewport "
"should still be split into two parts, with the camera preview at the bottom. "
"If that isn't the case, press :kbd:`Ctrl + 2` (:kbd:`Cmd + 2` on macOS) to "
"split the view into two. Select the :ref:`Camera3D <class_Camera3D>` node "
"and click the *Preview* checkbox in the bottom viewport."
msgstr ""

#: ../../docs/getting_started/first_3d_game/05.spawning_mobs.rst:47
msgid "Adding placeholder cylinders"
msgstr ""

#: ../../docs/getting_started/first_3d_game/05.spawning_mobs.rst:49
msgid ""
"Let's add the placeholder meshes. Add a new :ref:`Node3D <class_Node3D>` as "
"a child of the ``Main`` node and name it ``Cylinders``. We'll use it to "
"group the cylinders. Select ``Cylinders`` and add a child node :ref:"
"`MeshInstance3D <class_MeshInstance3D>`"
msgstr ""

#: ../../docs/getting_started/first_3d_game/05.spawning_mobs.rst:54
msgid "In the *Inspector*, assign a *CylinderMesh* to the *Mesh* property."
msgstr ""

#: ../../docs/getting_started/first_3d_game/05.spawning_mobs.rst:58
msgid ""
"Set the top viewport to the top orthogonal view using the menu in the "
"viewport's top-left corner. Alternatively, you can press the keypad's 7 key."
msgstr ""

#: ../../docs/getting_started/first_3d_game/05.spawning_mobs.rst:63
msgid ""
"The grid may be distracting. You can toggle it by going to the *View* menu "
"in the toolbar and clicking *View Grid*."
msgstr ""

#: ../../docs/getting_started/first_3d_game/05.spawning_mobs.rst:68
msgid ""
"You now want to move the cylinder along the ground plane, looking at the "
"camera preview in the bottom viewport. I recommend using grid snap to do so. "
"You can toggle it by clicking the magnet icon in the toolbar or pressing Y."
msgstr ""

#: ../../docs/getting_started/first_3d_game/05.spawning_mobs.rst:74
msgid ""
"Move the cylinder so it's right outside the camera's view in the top-left "
"corner."
msgstr ""

#: ../../docs/getting_started/first_3d_game/05.spawning_mobs.rst:79
msgid ""
"We're going to create copies of the mesh and place them around the game "
"area. Press :kbd:`Ctrl + D` (:kbd:`Cmd + D` on macOS) to duplicate the node. "
"You can also right-click the node in the *Scene* dock and select "
"*Duplicate*. Move the copy down along the blue Z axis until it's right "
"outside the camera's preview."
msgstr ""

#: ../../docs/getting_started/first_3d_game/05.spawning_mobs.rst:84
msgid ""
"Select both cylinders by pressing the :kbd:`Shift` key and clicking on the "
"unselected one and duplicate them."
msgstr ""

#: ../../docs/getting_started/first_3d_game/05.spawning_mobs.rst:89
msgid "Move them to the right by dragging the red X axis."
msgstr ""

#: ../../docs/getting_started/first_3d_game/05.spawning_mobs.rst:93
msgid ""
"They're a bit hard to see in white, aren't they? Let's make them stand out "
"by giving them a new material."
msgstr ""

#: ../../docs/getting_started/first_3d_game/05.spawning_mobs.rst:96
msgid ""
"In 3D, materials define a surface's visual properties like its color, how it "
"reflects light, and more. We can use them to change the color of a mesh."
msgstr ""

#: ../../docs/getting_started/first_3d_game/05.spawning_mobs.rst:99
msgid ""
"We can update all four cylinders at once. Select all the mesh instances in "
"the *Scene* dock. To do so, you can click on the first one and Shift click "
"on the last one."
msgstr ""

#: ../../docs/getting_started/first_3d_game/05.spawning_mobs.rst:105
msgid ""
"In the *Inspector*, expand the *Material* section and assign a :ref:"
"`StandardMaterial3D <class_StandardMaterial3D>` to slot *0*."
msgstr ""

#: ../../docs/getting_started/first_3d_game/05.spawning_mobs.rst:107
#: ../../docs/getting_started/first_3d_game/08.score_and_replay.rst:216
#: ../../docs/getting_started/first_3d_game/09.adding_animations.rst:109
#: ../../docs/community/asset_library/using_assetlib.rst:180
msgid "|image13|"
msgstr ""

#: ../../docs/getting_started/first_3d_game/05.spawning_mobs.rst:347
#: ../../docs/getting_started/first_3d_game/08.score_and_replay.rst:463
#: ../../docs/getting_started/first_3d_game/09.adding_animations.rst:621
#: ../../docs/community/asset_library/using_assetlib.rst:200
msgid "image13"
msgstr ""

#: ../../docs/getting_started/first_3d_game/05.spawning_mobs.rst:111
msgid ""
"Click the sphere icon to open the material resource. You get a preview of "
"the material and a long list of sections filled with properties. You can use "
"these to create all sorts of surfaces, from metal to rock or water."
msgstr ""

#: ../../docs/getting_started/first_3d_game/05.spawning_mobs.rst:115
msgid "Expand the *Albedo* section."
msgstr ""

#: ../../docs/getting_started/first_3d_game/05.spawning_mobs.rst:119
msgid ""
"Set the color to something that contrasts with the background, like a bright "
"orange."
msgstr ""

#: ../../docs/getting_started/first_3d_game/05.spawning_mobs.rst:122
#: ../../docs/getting_started/first_3d_game/08.score_and_replay.rst:223
#: ../../docs/getting_started/first_3d_game/09.adding_animations.rst:118
#: ../../docs/community/asset_library/using_assetlib.rst:127
msgid "|image14|"
msgstr ""

#: ../../docs/getting_started/first_3d_game/05.spawning_mobs.rst:348
#: ../../docs/getting_started/first_3d_game/08.score_and_replay.rst:464
#: ../../docs/getting_started/first_3d_game/09.adding_animations.rst:622
#: ../../docs/community/asset_library/using_assetlib.rst:201
msgid "image14"
msgstr ""

#: ../../docs/getting_started/first_3d_game/05.spawning_mobs.rst:124
msgid ""
"We can now use the cylinders as guides. Fold them in the *Scene* dock by "
"clicking the grey arrow next to them. Moving forward, you can also toggle "
"their visibility by clicking the eye icon next to *Cylinders*."
msgstr ""

#: ../../docs/getting_started/first_3d_game/05.spawning_mobs.rst:130
msgid ""
"Add a child node :ref:`Path3D <class_Path3D>` to ``Main`` node. In the "
"toolbar, four icons appear. Click the *Add Point* tool, the icon with the "
"green \"+\" sign."
msgstr ""

#: ../../docs/getting_started/first_3d_game/05.spawning_mobs.rst:135
msgid "You can hover any icon to see a tooltip describing the tool."
msgstr ""

#: ../../docs/getting_started/first_3d_game/05.spawning_mobs.rst:137
msgid ""
"Click in the center of each cylinder to create a point. Then, click the "
"*Close Curve* icon in the toolbar to close the path. If any point is a bit "
"off, you can click and drag on it to reposition it."
msgstr ""

#: ../../docs/getting_started/first_3d_game/05.spawning_mobs.rst:141
#: ../../docs/getting_started/first_3d_game/08.score_and_replay.rst:324
#: ../../docs/getting_started/first_3d_game/09.adding_animations.rst:153
msgid "|image17|"
msgstr ""

#: ../../docs/getting_started/first_3d_game/05.spawning_mobs.rst:143
msgid "Your path should look like this."
msgstr ""

#: ../../docs/getting_started/first_3d_game/05.spawning_mobs.rst:147
msgid ""
"To sample random positions on it, we need a :ref:`PathFollow3D "
"<class_PathFollow3D>` node. Add a :ref:`PathFollow3D <class_PathFollow3D>` "
"as a child of the ``Path3D``. Rename the two nodes to ``SpawnLocation`` and "
"``SpawnPath``, respectively. It's more descriptive of what we'll use them "
"for."
msgstr ""

#: ../../docs/getting_started/first_3d_game/05.spawning_mobs.rst:151
#: ../../docs/getting_started/first_3d_game/08.score_and_replay.rst:344
#: ../../docs/getting_started/first_3d_game/09.adding_animations.rst:166
msgid "|image19|"
msgstr ""

#: ../../docs/getting_started/first_3d_game/05.spawning_mobs.rst:353
#: ../../docs/getting_started/first_3d_game/08.score_and_replay.rst:469
#: ../../docs/getting_started/first_3d_game/09.adding_animations.rst:627
msgid "image19"
msgstr ""

#: ../../docs/getting_started/first_3d_game/05.spawning_mobs.rst:153
msgid "With that, we're ready to code the spawn mechanism."
msgstr ""

#: ../../docs/getting_started/first_3d_game/05.spawning_mobs.rst:156
msgid "Spawning monsters randomly"
msgstr ""

#: ../../docs/getting_started/first_3d_game/05.spawning_mobs.rst:158
msgid "Right-click on the ``Main`` node and attach a new script to it."
msgstr ""

#: ../../docs/getting_started/first_3d_game/05.spawning_mobs.rst:160
msgid ""
"We first export a variable to the *Inspector* so that we can assign ``mob."
"tscn`` or any other monster to it."
msgstr ""

#: ../../docs/getting_started/first_3d_game/05.spawning_mobs.rst:182
msgid ""
"We want to spawn mobs at regular time intervals. To do this, we need to go "
"back to the scene and add a timer. Before that, though, we need to assign "
"the ``mob.tscn`` file to the ``mob_scene`` property above (otherwise it's "
"null!)"
msgstr ""

#: ../../docs/getting_started/first_3d_game/05.spawning_mobs.rst:186
msgid ""
"Head back to the 3D screen and select the ``Main`` node. Drag ``mob.tscn`` "
"from the *FileSystem* dock to the *Mob Scene* slot in the *Inspector*."
msgstr ""

#: ../../docs/getting_started/first_3d_game/05.spawning_mobs.rst:189
#: ../../docs/getting_started/first_3d_game/08.score_and_replay.rst:350
#: ../../docs/getting_started/first_3d_game/09.adding_animations.rst:170
msgid "|image20|"
msgstr ""

#: ../../docs/getting_started/first_3d_game/05.spawning_mobs.rst:354
#: ../../docs/getting_started/first_3d_game/08.score_and_replay.rst:470
#: ../../docs/getting_started/first_3d_game/09.adding_animations.rst:628
msgid "image20"
msgstr ""

#: ../../docs/getting_started/first_3d_game/05.spawning_mobs.rst:191
msgid ""
"Add a new :ref:`Timer <class_Timer>` node as a child of ``Main``. Name it "
"``MobTimer``."
msgstr ""

#: ../../docs/getting_started/first_3d_game/05.spawning_mobs.rst:193
#: ../../docs/getting_started/first_3d_game/09.adding_animations.rst:174
msgid "|image21|"
msgstr ""

#: ../../docs/getting_started/first_3d_game/05.spawning_mobs.rst:355
#: ../../docs/getting_started/first_3d_game/09.adding_animations.rst:629
msgid "image21"
msgstr ""

#: ../../docs/getting_started/first_3d_game/05.spawning_mobs.rst:195
msgid ""
"In the *Inspector*, set its *Wait Time* to ``0.5`` seconds and turn on "
"*Autostart* so it automatically starts when we run the game."
msgstr ""

#: ../../docs/getting_started/first_3d_game/05.spawning_mobs.rst:198
#: ../../docs/getting_started/first_3d_game/09.adding_animations.rst:198
msgid "|image22|"
msgstr ""

#: ../../docs/getting_started/first_3d_game/05.spawning_mobs.rst:356
#: ../../docs/getting_started/first_3d_game/09.adding_animations.rst:630
msgid "image22"
msgstr ""

#: ../../docs/getting_started/first_3d_game/05.spawning_mobs.rst:200
msgid ""
"Timers emit a ``timeout`` signal every time they reach the end of their "
"*Wait Time*. By default, they restart automatically, emitting the signal in "
"a cycle. We can connect to this signal from the *Main* node to spawn "
"monsters every ``0.5`` seconds."
msgstr ""

#: ../../docs/getting_started/first_3d_game/05.spawning_mobs.rst:205
msgid ""
"With the *MobTimer* still selected, head to the *Node* dock on the right, "
"and double-click the ``timeout`` signal."
msgstr ""

#: ../../docs/getting_started/first_3d_game/05.spawning_mobs.rst:208
msgid "|image23|"
msgstr ""

#: ../../docs/getting_started/first_3d_game/05.spawning_mobs.rst:357
msgid "image23"
msgstr ""

#: ../../docs/getting_started/first_3d_game/05.spawning_mobs.rst:210
msgid "Connect it to the *Main* node."
msgstr ""

#: ../../docs/getting_started/first_3d_game/05.spawning_mobs.rst:212
msgid "|image24|"
msgstr ""

#: ../../docs/getting_started/first_3d_game/05.spawning_mobs.rst:358
msgid "image24"
msgstr ""

#: ../../docs/getting_started/first_3d_game/05.spawning_mobs.rst:214
msgid ""
"This will take you back to the script, with a new empty "
"``_on_mob_timer_timeout()`` function."
msgstr ""

#: ../../docs/getting_started/first_3d_game/05.spawning_mobs.rst:217
msgid "Let's code the mob spawning logic. We're going to:"
msgstr ""

#: ../../docs/getting_started/first_3d_game/05.spawning_mobs.rst:219
#, fuzzy
msgid "Instantiate the mob scene."
msgstr "Kreiranje Sadržaja"

#: ../../docs/getting_started/first_3d_game/05.spawning_mobs.rst:220
msgid "Sample a random position on the spawn path."
msgstr ""

#: ../../docs/getting_started/first_3d_game/05.spawning_mobs.rst:221
msgid "Get the player's position."
msgstr ""

#: ../../docs/getting_started/first_3d_game/05.spawning_mobs.rst:222
msgid ""
"Call the mob's ``initialize()`` method, passing it the random position and "
"the player's position."
msgstr ""

#: ../../docs/getting_started/first_3d_game/05.spawning_mobs.rst:224
msgid "Add the mob as a child of the *Main* node."
msgstr ""

#: ../../docs/getting_started/first_3d_game/05.spawning_mobs.rst:266
msgid ""
"Above, ``randf()`` produces a random value between ``0`` and ``1``, which is "
"what the *PathFollow* node's ``progress_ratio`` expects: 0 is the start of "
"the path, 1 is the end of the path. The path we have set is around the "
"camera's viewport, so any random value between 0 and 1 is a random position "
"alongside the edges of the viewport!"
msgstr ""

#: ../../docs/getting_started/first_3d_game/05.spawning_mobs.rst:272
msgid "Here is the complete ``main.gd`` script so far, for reference."
msgstr ""

#: ../../docs/getting_started/first_3d_game/05.spawning_mobs.rst:326
msgid ""
"You can test the scene by pressing :kbd:`F6`. You should see the monsters "
"spawn and move in a straight line."
msgstr ""

#: ../../docs/getting_started/first_3d_game/05.spawning_mobs.rst:329
msgid "|image25|"
msgstr ""

#: ../../docs/getting_started/first_3d_game/05.spawning_mobs.rst:359
msgid "image25"
msgstr ""

#: ../../docs/getting_started/first_3d_game/05.spawning_mobs.rst:331
msgid ""
"For now, they bump and slide against one another when their paths cross. "
"We'll address this in the next part."
msgstr ""

#: ../../docs/getting_started/first_3d_game/06.jump_and_squash.rst:6
msgid "Jumping and squashing monsters"
msgstr ""

#: ../../docs/getting_started/first_3d_game/06.jump_and_squash.rst:8
msgid ""
"In this part, we'll add the ability to jump and squash the monsters. In the "
"next lesson, we'll make the player die when a monster hits them on the "
"ground."
msgstr ""

#: ../../docs/getting_started/first_3d_game/06.jump_and_squash.rst:11
#, fuzzy
msgid ""
"First, we have to change a few settings related to physics interactions. "
"Enter the world of :ref:`physics layers "
"<doc_physics_introduction_collision_layers_and_masks>`."
msgstr "Kreiranje Sadržaja"

#: ../../docs/getting_started/first_3d_game/06.jump_and_squash.rst:16
#, fuzzy
msgid "Controlling physics interactions"
msgstr "Kreiranje Sadržaja"

#: ../../docs/getting_started/first_3d_game/06.jump_and_squash.rst:18
msgid ""
"Physics bodies have access to two complementary properties: layers and "
"masks. Layers define on which physics layer(s) an object is."
msgstr ""

#: ../../docs/getting_started/first_3d_game/06.jump_and_squash.rst:21
msgid ""
"Masks control the layers that a body will listen to and detect. This affects "
"collision detection. When you want two bodies to interact, you need at least "
"one to have a mask corresponding to the other."
msgstr ""

#: ../../docs/getting_started/first_3d_game/06.jump_and_squash.rst:25
msgid "If that's confusing, don't worry, we'll see three examples in a second."
msgstr ""

#: ../../docs/getting_started/first_3d_game/06.jump_and_squash.rst:27
msgid ""
"The important point is that you can use layers and masks to filter physics "
"interactions, control performance, and remove the need for extra conditions "
"in your code."
msgstr ""

#: ../../docs/getting_started/first_3d_game/06.jump_and_squash.rst:31
msgid ""
"By default, all physics bodies and areas are set to both layer and mask "
"``1``. This means they all collide with each other."
msgstr ""

#: ../../docs/getting_started/first_3d_game/06.jump_and_squash.rst:34
msgid ""
"Physics layers are represented by numbers, but we can give them names to "
"keep track of what's what."
msgstr ""

#: ../../docs/getting_started/first_3d_game/06.jump_and_squash.rst:38
#, fuzzy
msgid "Setting layer names"
msgstr "Kreiranje Sadržaja"

#: ../../docs/getting_started/first_3d_game/06.jump_and_squash.rst:40
msgid ""
"Let's give our physics layers a name. Go to *Project -> Project Settings*."
msgstr ""

#: ../../docs/getting_started/first_3d_game/06.jump_and_squash.rst:44
msgid ""
"In the left menu, navigate down to *Layer Names -> 3D Physics*. You can see "
"a list of layers with a field next to each of them on the right. You can set "
"their names there. Name the first three layers *player*, *enemies*, and "
"*world*, respectively."
msgstr ""

#: ../../docs/getting_started/first_3d_game/06.jump_and_squash.rst:51
msgid "Now, we can assign them to our physics nodes."
msgstr ""

#: ../../docs/getting_started/first_3d_game/06.jump_and_squash.rst:54
msgid "Assigning layers and masks"
msgstr ""

#: ../../docs/getting_started/first_3d_game/06.jump_and_squash.rst:56
msgid ""
"In the *Main* scene, select the ``Ground`` node. In the *Inspector*, expand "
"the *Collision* section. There, you can see the node's layers and masks as a "
"grid of buttons."
msgstr ""

#: ../../docs/getting_started/first_3d_game/06.jump_and_squash.rst:62
msgid ""
"The ground is part of the world, so we want it to be part of the third "
"layer. Click the lit button to toggle **off** the first *Layer* and toggle "
"**on** the third one. Then, toggle **off** the *Mask* by clicking on it."
msgstr ""

#: ../../docs/getting_started/first_3d_game/06.jump_and_squash.rst:68
msgid ""
"As mentioned before, the *Mask* property allows a node to listen to "
"interaction with other physics objects, but we don't need it to have "
"collisions. ``Ground`` doesn't need to listen to anything; it's just there "
"to prevent creatures from falling."
msgstr ""

#: ../../docs/getting_started/first_3d_game/06.jump_and_squash.rst:72
msgid ""
"Note that you can click the \"...\" button on the right side of the "
"properties to see a list of named checkboxes."
msgstr ""

#: ../../docs/getting_started/first_3d_game/06.jump_and_squash.rst:77
msgid ""
"Next up are the ``Player`` and the ``Mob``. Open ``player.tscn`` by double-"
"clicking the file in the *FileSystem* dock."
msgstr ""

#: ../../docs/getting_started/first_3d_game/06.jump_and_squash.rst:80
msgid ""
"Select the *Player* node and set its *Collision -> Mask* to both \"enemies\" "
"and \"world\". You can leave the default *Layer* property as it is, because "
"the first layer is the \"player\" layer."
msgstr ""

#: ../../docs/getting_started/first_3d_game/06.jump_and_squash.rst:86
msgid ""
"Then, open the *Mob* scene by double-clicking on ``mob.tscn`` and select the "
"``Mob`` node."
msgstr ""

#: ../../docs/getting_started/first_3d_game/06.jump_and_squash.rst:89
msgid ""
"Set its *Collision -> Layer* to \"enemies\" and unset its *Collision -> "
"Mask*, leaving the mask empty."
msgstr ""

#: ../../docs/getting_started/first_3d_game/06.jump_and_squash.rst:94
msgid ""
"These settings mean the monsters will move through one another. If you want "
"the monsters to collide with and slide against each other, turn **on** the "
"\"enemies\" mask."
msgstr ""

#: ../../docs/getting_started/first_3d_game/06.jump_and_squash.rst:100
msgid ""
"The mobs don't need to mask the \"world\" layer because they only move on "
"the XZ plane. We don't apply any gravity to them by design."
msgstr ""

#: ../../docs/getting_started/first_3d_game/06.jump_and_squash.rst:104
msgid "Jumping"
msgstr ""

#: ../../docs/getting_started/first_3d_game/06.jump_and_squash.rst:106
msgid ""
"The jumping mechanic itself requires only two lines of code. Open the "
"*Player* script. We need a value to control the jump's strength and update "
"``_physics_process()`` to code the jump."
msgstr ""

#: ../../docs/getting_started/first_3d_game/06.jump_and_squash.rst:110
msgid ""
"After the line that defines ``fall_acceleration``, at the top of the script, "
"add the ``jump_impulse``."
msgstr ""

#: ../../docs/getting_started/first_3d_game/06.jump_and_squash.rst:129
msgid ""
"Inside ``_physics_process()``, add the following code before the "
"``move_and_slide()`` codeblock."
msgstr ""

#: ../../docs/getting_started/first_3d_game/06.jump_and_squash.rst:158
msgid "That's all you need to jump!"
msgstr ""

#: ../../docs/getting_started/first_3d_game/06.jump_and_squash.rst:160
msgid ""
"The ``is_on_floor()`` method is a tool from the ``CharacterBody3D`` class. "
"It returns ``true`` if the body collided with the floor in this frame. "
"That's why we apply gravity to the *Player*: so we collide with the floor "
"instead of floating over it like the monsters."
msgstr ""

#: ../../docs/getting_started/first_3d_game/06.jump_and_squash.rst:165
msgid ""
"If the character is on the floor and the player presses \"jump\", we "
"instantly give them a lot of vertical speed. In games, you really want "
"controls to be responsive and giving instant speed boosts like these, while "
"unrealistic, feels great."
msgstr ""

#: ../../docs/getting_started/first_3d_game/06.jump_and_squash.rst:170
msgid ""
"Notice that the Y axis is positive upwards. That's unlike 2D, where the Y "
"axis is positive downwards."
msgstr ""

#: ../../docs/getting_started/first_3d_game/06.jump_and_squash.rst:174
#, fuzzy
msgid "Squashing monsters"
msgstr "Kreiranje Sadržaja"

#: ../../docs/getting_started/first_3d_game/06.jump_and_squash.rst:176
msgid ""
"Let's add the squash mechanic next. We're going to make the character bounce "
"over monsters and kill them at the same time."
msgstr ""

#: ../../docs/getting_started/first_3d_game/06.jump_and_squash.rst:179
msgid ""
"We need to detect collisions with a monster and to differentiate them from "
"collisions with the floor. To do so, we can use Godot's :ref:`group "
"<doc_groups>` tagging feature."
msgstr ""

#: ../../docs/getting_started/first_3d_game/06.jump_and_squash.rst:183
msgid ""
"Open the scene ``mob.tscn`` again and select the *Mob* node. Go to the "
"*Node* dock on the right to see a list of signals. The *Node* dock has two "
"tabs: *Signals*, which you've already used, and *Groups*, which allows you "
"to assign tags to nodes."
msgstr ""

#: ../../docs/getting_started/first_3d_game/06.jump_and_squash.rst:188
msgid ""
"Click on it to reveal a field where you can write a tag name. Enter \"mob\" "
"in the field and click the *Add* button."
msgstr ""

#: ../../docs/getting_started/first_3d_game/06.jump_and_squash.rst:193
msgid ""
"An icon appears in the *Scene* dock to indicate the node is part of at least "
"one group."
msgstr ""

#: ../../docs/getting_started/first_3d_game/06.jump_and_squash.rst:198
msgid ""
"We can now use the group from the code to distinguish collisions with "
"monsters from collisions with the floor."
msgstr ""

#: ../../docs/getting_started/first_3d_game/06.jump_and_squash.rst:202
msgid "Coding the squash mechanic"
msgstr ""

#: ../../docs/getting_started/first_3d_game/06.jump_and_squash.rst:204
msgid "Head back to the *Player* script to code the squash and bounce."
msgstr ""

#: ../../docs/getting_started/first_3d_game/06.jump_and_squash.rst:206
msgid ""
"At the top of the script, we need another property, ``bounce_impulse``. When "
"squashing an enemy, we don't necessarily want the character to go as high up "
"as when jumping."
msgstr ""

#: ../../docs/getting_started/first_3d_game/06.jump_and_squash.rst:225
msgid ""
"Then, after the **Jumping** codeblock we added above in "
"``_physics_process()``, add the following loop. With ``move_and_slide()``, "
"Godot makes the body move sometimes multiple times in a row to smooth out "
"the character's motion. So we have to loop over all collisions that may have "
"happened."
msgstr ""

#: ../../docs/getting_started/first_3d_game/06.jump_and_squash.rst:230
msgid ""
"In every iteration of the loop, we check if we landed on a mob. If so, we "
"kill it and bounce."
msgstr ""

#: ../../docs/getting_started/first_3d_game/06.jump_and_squash.rst:233
msgid ""
"With this code, if no collisions occurred on a given frame, the loop won't "
"run."
msgstr ""

#: ../../docs/getting_started/first_3d_game/06.jump_and_squash.rst:291
msgid "That's a lot of new functions. Here's some more information about them."
msgstr ""

#: ../../docs/getting_started/first_3d_game/06.jump_and_squash.rst:293
msgid ""
"The functions ``get_slide_collision_count()`` and ``get_slide_collision()`` "
"both come from the :ref:`CharacterBody3D <class_CharacterBody3D>` class and "
"are related to ``move_and_slide()``."
msgstr ""

#: ../../docs/getting_started/first_3d_game/06.jump_and_squash.rst:297
msgid ""
"``get_slide_collision()`` returns a :ref:"
"`KinematicCollision3D<class_KinematicCollision3D>` object that holds "
"information about where and how the collision occurred. For example, we use "
"its ``get_collider`` property to check if we collided with a \"mob\" by "
"calling ``is_in_group()`` on it: ``collision.get_collider()."
"is_in_group(\"mob\")``."
msgstr ""

#: ../../docs/getting_started/first_3d_game/06.jump_and_squash.rst:305
msgid ""
"The method ``is_in_group()`` is available on every :ref:`Node<class_Node>`."
msgstr ""

#: ../../docs/getting_started/first_3d_game/06.jump_and_squash.rst:307
msgid ""
"To check that we are landing on the monster, we use the vector dot product: "
"``Vector3.UP.dot(collision.get_normal()) > 0.1``. The collision normal is a "
"3D vector that is perpendicular to the plane where the collision occurred. "
"The dot product allows us to compare it to the up direction."
msgstr ""

#: ../../docs/getting_started/first_3d_game/06.jump_and_squash.rst:312
msgid ""
"With dot products, when the result is greater than ``0``, the two vectors "
"are at an angle of fewer than 90 degrees. A value higher than ``0.1`` tells "
"us that we are roughly above the monster."
msgstr ""

#: ../../docs/getting_started/first_3d_game/06.jump_and_squash.rst:316
msgid ""
"After handling the squash and bounce logic, we terminate the loop early via "
"the ``break`` statement to prevent further duplicate calls to ``mob."
"squash()``, which may otherwise result in unintended bugs such as counting "
"the score multiple times for one kill."
msgstr ""

#: ../../docs/getting_started/first_3d_game/06.jump_and_squash.rst:320
msgid ""
"We are calling one undefined function, ``mob.squash()``, so we have to add "
"it to the Mob class."
msgstr ""

#: ../../docs/getting_started/first_3d_game/06.jump_and_squash.rst:323
msgid ""
"Open the script ``Mob.gd`` by double-clicking on it in the *FileSystem* "
"dock. At the top of the script, we want to define a new signal named "
"``squashed``. And at the bottom, you can add the squash function, where we "
"emit the signal and destroy the mob."
msgstr ""

#: ../../docs/getting_started/first_3d_game/06.jump_and_squash.rst:359
msgid ""
"When using C#, Godot will create the appropriate events automatically for "
"all Signals ending with `EventHandler`, see :ref:`C# Signals "
"<doc_c_sharp_signals>`."
msgstr ""

#: ../../docs/getting_started/first_3d_game/06.jump_and_squash.rst:361
msgid "We will use the signal to add points to the score in the next lesson."
msgstr ""

#: ../../docs/getting_started/first_3d_game/06.jump_and_squash.rst:363
msgid ""
"With that, you should be able to kill monsters by jumping on them. You can "
"press :kbd:`F5` to try the game and set ``main.tscn`` as your project's main "
"scene."
msgstr ""

#: ../../docs/getting_started/first_3d_game/06.jump_and_squash.rst:366
msgid "However, the player won't die yet. We'll work on that in the next part."
msgstr ""

#: ../../docs/getting_started/first_3d_game/07.killing_player.rst:6
#, fuzzy
msgid "Killing the player"
msgstr "Kreiranje Sadržaja"

#: ../../docs/getting_started/first_3d_game/07.killing_player.rst:8
msgid ""
"We can kill enemies by jumping on them, but the player still can't die. "
"Let's fix this."
msgstr ""

#: ../../docs/getting_started/first_3d_game/07.killing_player.rst:11
msgid ""
"We want to detect being hit by an enemy differently from squashing them. We "
"want the player to die when they're moving on the floor, but not if they're "
"in the air. We could use vector math to distinguish the two kinds of "
"collisions. Instead, though, we will use an :ref:`Area3D <class_Area3D>` "
"node, which works well for hitboxes."
msgstr ""

#: ../../docs/getting_started/first_3d_game/07.killing_player.rst:18
msgid "Hitbox with the Area node"
msgstr ""

#: ../../docs/getting_started/first_3d_game/07.killing_player.rst:20
msgid ""
"Head back to the ``player.tscn`` scene and add a new child node :ref:`Area3D "
"<class_Area3D>`. Name it ``MobDetector`` Add a :ref:`CollisionShape3D "
"<class_CollisionShape3D>` node as a child of it."
msgstr ""

#: ../../docs/getting_started/first_3d_game/07.killing_player.rst:26
msgid "In the *Inspector*, assign a cylinder shape to it."
msgstr ""

#: ../../docs/getting_started/first_3d_game/07.killing_player.rst:30
msgid ""
"Here is a trick you can use to make the collisions only happen when the "
"player is on the ground or close to it. You can reduce the cylinder's height "
"and move it up to the top of the character. This way, when the player jumps, "
"the shape will be too high up for the enemies to collide with it."
msgstr ""

#: ../../docs/getting_started/first_3d_game/07.killing_player.rst:38
msgid ""
"You also want the cylinder to be wider than the sphere. This way, the player "
"gets hit before colliding and being pushed on top of the monster's collision "
"box."
msgstr ""

#: ../../docs/getting_started/first_3d_game/07.killing_player.rst:42
msgid "The wider the cylinder, the more easily the player will get killed."
msgstr ""

#: ../../docs/getting_started/first_3d_game/07.killing_player.rst:44
msgid ""
"Next, select the ``MobDetector`` node again, and in the *Inspector*, turn "
"**off** its *Monitorable* property. This makes it so other physics nodes "
"cannot detect the area. The complementary *Monitoring* property allows it to "
"detect collisions. Then, remove the *Collision -> Layer* and set the mask to "
"the \"enemies\" layer."
msgstr ""

#: ../../docs/getting_started/first_3d_game/07.killing_player.rst:52
msgid ""
"When areas detect a collision, they emit signals. We're going to connect one "
"to the ``Player`` node. Select ``MobDetector`` and go to *Inspector*'s "
"*Node* tab, double-click the ``body_entered`` signal and connect it to the "
"``Player``"
msgstr ""

#: ../../docs/getting_started/first_3d_game/07.killing_player.rst:58
msgid ""
"The *MobDetector* will emit ``body_entered`` when a :ref:`CharacterBody3D "
"<class_CharacterBody3D>` or a :ref:`RigidBody3D <class_RigidBody3D>` node "
"enters it. As it only masks the \"enemies\" physics layers, it will only "
"detect the ``Mob`` nodes."
msgstr ""

#: ../../docs/getting_started/first_3d_game/07.killing_player.rst:62
msgid ""
"Code-wise, we're going to do two things: emit a signal we'll later use to "
"end the game and destroy the player. We can wrap these operations in a "
"``die()`` function that helps us put a descriptive label on the code."
msgstr ""

#: ../../docs/getting_started/first_3d_game/07.killing_player.rst:105
msgid ""
"Try the game again by pressing :kbd:`F5`. If everything is set up correctly, "
"the character should die when an enemy runs into the collider. Note that "
"without a ``Player``, the following line"
msgstr ""

#: ../../docs/getting_started/first_3d_game/07.killing_player.rst:118
msgid "gives error because there is no $Player!"
msgstr ""

#: ../../docs/getting_started/first_3d_game/07.killing_player.rst:120
msgid ""
"Also note that the enemy colliding with the player and dying depends on the "
"size and position of the ``Player`` and the ``Mob``\\ 's collision shapes. "
"You may need to move them and resize them to achieve a tight game feel."
msgstr ""

#: ../../docs/getting_started/first_3d_game/07.killing_player.rst:125
msgid "Ending the game"
msgstr ""

#: ../../docs/getting_started/first_3d_game/07.killing_player.rst:127
msgid ""
"We can use the ``Player``\\ 's ``hit`` signal to end the game. All we need "
"to do is connect it to the ``Main`` node and stop the ``MobTimer`` in "
"reaction."
msgstr ""

#: ../../docs/getting_started/first_3d_game/07.killing_player.rst:131
msgid ""
"Open ``main.tscn``, select the ``Player`` node, and in the *Node* dock, "
"connect its ``hit`` signal to the ``Main`` node."
msgstr ""

#: ../../docs/getting_started/first_3d_game/07.killing_player.rst:136
msgid "Get the timer, and stop it, in the ``_on_player_hit()`` function."
msgstr ""

#: ../../docs/getting_started/first_3d_game/07.killing_player.rst:152
msgid ""
"If you try the game now, the monsters will stop spawning when you die, and "
"the remaining ones will leave the screen."
msgstr ""

#: ../../docs/getting_started/first_3d_game/07.killing_player.rst:155
msgid ""
"You can pat yourself in the back: you prototyped a complete 3D game, even if "
"it's still a bit rough."
msgstr ""

#: ../../docs/getting_started/first_3d_game/07.killing_player.rst:158
msgid ""
"From there, we'll add a score, the option to retry the game, and you'll see "
"how you can make the game feel much more alive with minimalistic animations."
msgstr ""

#: ../../docs/getting_started/first_3d_game/07.killing_player.rst:163
msgid "Code checkpoint"
msgstr ""

#: ../../docs/getting_started/first_3d_game/07.killing_player.rst:165
msgid ""
"Here are the complete scripts for the ``Main``, ``Mob``, and ``Player`` "
"nodes, for reference. You can use them to compare and check your code."
msgstr ""

#: ../../docs/getting_started/first_3d_game/07.killing_player.rst:168
msgid "Starting with ``main.gd``."
msgstr ""

#: ../../docs/getting_started/first_3d_game/07.killing_player.rst:230
msgid "Next is ``Mob.gd``."
msgstr ""

#: ../../docs/getting_started/first_3d_game/07.killing_player.rst:325
msgid "Finally, the longest script, ``Player.gd``:"
msgstr ""

#: ../../docs/getting_started/first_3d_game/07.killing_player.rst:524
msgid "See you in the next lesson to add the score and the retry option."
msgstr ""

#: ../../docs/getting_started/first_3d_game/08.score_and_replay.rst:6
msgid "Score and replay"
msgstr ""

#: ../../docs/getting_started/first_3d_game/08.score_and_replay.rst:8
msgid ""
"In this part, we'll add the score, music playback, and the ability to "
"restart the game."
msgstr ""

#: ../../docs/getting_started/first_3d_game/08.score_and_replay.rst:11
msgid ""
"We have to keep track of the current score in a variable and display it on "
"screen using a minimal interface. We will use a text label to do that."
msgstr ""

#: ../../docs/getting_started/first_3d_game/08.score_and_replay.rst:14
msgid ""
"In the main scene, add a new child node :ref:`Control <class_Control>` to "
"``Main`` and name it ``UserInterface``. You will automatically be taken to "
"the 2D screen, where you can edit your User Interface (UI)."
msgstr ""

#: ../../docs/getting_started/first_3d_game/08.score_and_replay.rst:18
msgid "Add a :ref:`Label <class_Label>` node and name it ``ScoreLabel``"
msgstr ""

#: ../../docs/getting_started/first_3d_game/08.score_and_replay.rst:22
msgid ""
"In the *Inspector*, set the *Label*'s *Text* to a placeholder like \"Score: "
"0\"."
msgstr ""

#: ../../docs/getting_started/first_3d_game/08.score_and_replay.rst:26
msgid ""
"Also, the text is white by default, like our game's background. We need to "
"change its color to see it at runtime."
msgstr ""

#: ../../docs/getting_started/first_3d_game/08.score_and_replay.rst:29
msgid ""
"Scroll down to *Theme Overrides*, and expand *Colors* and enable *Font "
"Color* in order to tint the text to black (which contrasts well with the "
"white 3D scene)"
msgstr ""

#: ../../docs/getting_started/first_3d_game/08.score_and_replay.rst:35
msgid ""
"Finally, click and drag on the text in the viewport to move it away from the "
"top-left corner."
msgstr ""

#: ../../docs/getting_started/first_3d_game/08.score_and_replay.rst:40
msgid ""
"The ``UserInterface`` node allows us to group our UI in a branch of the "
"scene tree and use a theme resource that will propagate to all its children. "
"We'll use it to set our game's font."
msgstr ""

#: ../../docs/getting_started/first_3d_game/08.score_and_replay.rst:45
#, fuzzy
msgid "Creating a UI theme"
msgstr "Kreiranje Sadržaja"

#: ../../docs/getting_started/first_3d_game/08.score_and_replay.rst:47
msgid ""
"Once again, select the ``UserInterface`` node. In the *Inspector*, create a "
"new theme resource in *Theme -> Theme*."
msgstr ""

#: ../../docs/getting_started/first_3d_game/08.score_and_replay.rst:52
msgid ""
"Click on it to open the theme editor In the bottom panel. It gives you a "
"preview of how all the built-in UI widgets will look with your theme "
"resource."
msgstr ""

#: ../../docs/getting_started/first_3d_game/08.score_and_replay.rst:57
msgid "By default, a theme only has one property, the *Default Font*."
msgstr ""

#: ../../docs/getting_started/first_3d_game/08.score_and_replay.rst:61
msgid ""
"You can add more properties to the theme resource to design complex user "
"interfaces, but that is beyond the scope of this series. To learn more about "
"creating and editing themes, see :ref:`doc_gui_skinning`."
msgstr ""

#: ../../docs/getting_started/first_3d_game/08.score_and_replay.rst:65
msgid ""
"This one expects a font file like the ones you have on your computer. Two "
"common font file formats are TrueType Font (TTF) and OpenType Font (OTF)."
msgstr ""

#: ../../docs/getting_started/first_3d_game/08.score_and_replay.rst:68
msgid ""
"In the *FileSystem* dock, expand the ``fonts`` directory and click and drag "
"the ``Montserrat-Medium.ttf`` file we included in the project onto the "
"*Default Font*. The text will reappear in the theme preview."
msgstr ""

#: ../../docs/getting_started/first_3d_game/08.score_and_replay.rst:72
msgid ""
"The text is a bit small. Set the *Default Font Size* to ``22`` pixels to "
"increase the text's size."
msgstr ""

#: ../../docs/getting_started/first_3d_game/08.score_and_replay.rst:77
msgid "Keeping track of the score"
msgstr ""

#: ../../docs/getting_started/first_3d_game/08.score_and_replay.rst:79
msgid ""
"Let's work on the score next. Attach a new script to the ``ScoreLabel`` and "
"define the ``score`` variable."
msgstr ""

#: ../../docs/getting_started/first_3d_game/08.score_and_replay.rst:98
msgid ""
"The score should increase by ``1`` every time we squash a monster. We can "
"use their ``squashed`` signal to know when that happens. However, because we "
"instantiate monsters from the code, we cannot connect the mob signal to the "
"``ScoreLabel`` via the editor."
msgstr ""

#: ../../docs/getting_started/first_3d_game/08.score_and_replay.rst:102
msgid ""
"Instead, we have to make the connection from the code every time we spawn a "
"monster."
msgstr ""

#: ../../docs/getting_started/first_3d_game/08.score_and_replay.rst:105
msgid ""
"Open the script ``main.gd``. If it's still open, you can click on its name "
"in the script editor's left column."
msgstr ""

#: ../../docs/getting_started/first_3d_game/08.score_and_replay.rst:110
msgid ""
"Alternatively, you can double-click the ``main.gd`` file in the *FileSystem* "
"dock."
msgstr ""

#: ../../docs/getting_started/first_3d_game/08.score_and_replay.rst:113
msgid ""
"At the bottom of the ``_on_mob_timer_timeout()`` function, add the following "
"line:"
msgstr ""

#: ../../docs/getting_started/first_3d_game/08.score_and_replay.rst:133
msgid ""
"This line means that when the mob emits the ``squashed`` signal, the "
"``ScoreLabel`` node will receive it and call the function "
"``_on_mob_squashed()``."
msgstr ""

#: ../../docs/getting_started/first_3d_game/08.score_and_replay.rst:136
msgid ""
"Head back to the ``ScoreLabel.gd`` script to define the "
"``_on_mob_squashed()`` callback function."
msgstr ""

#: ../../docs/getting_started/first_3d_game/08.score_and_replay.rst:139
msgid "There, we increment the score and update the displayed text."
msgstr ""

#: ../../docs/getting_started/first_3d_game/08.score_and_replay.rst:156
msgid ""
"The second line uses the value of the ``score`` variable to replace the "
"placeholder ``%s``. When using this feature, Godot automatically converts "
"values to string text, which is convenient when outputting text in labels or "
"when using the ``print()`` function."
msgstr ""

#: ../../docs/getting_started/first_3d_game/08.score_and_replay.rst:163
msgid ""
"You can learn more about string formatting here: :ref:`doc_gdscript_printf`. "
"In C#, consider using `string interpolation with \"$\" <https://learn."
"microsoft.com/en-us/dotnet/csharp/language-reference/tokens/interpolated>`_."
msgstr ""

#: ../../docs/getting_started/first_3d_game/08.score_and_replay.rst:166
msgid ""
"You can now play the game and squash a few enemies to see the score increase."
msgstr ""

#: ../../docs/getting_started/first_3d_game/08.score_and_replay.rst:173
msgid ""
"In a complex game, you may want to completely separate your user interface "
"from the game world. In that case, you would not keep track of the score on "
"the label. Instead, you may want to store it in a separate, dedicated "
"object. But when prototyping or when your project is simple, it is fine to "
"keep your code simple. Programming is always a balancing act."
msgstr ""

#: ../../docs/getting_started/first_3d_game/08.score_and_replay.rst:180
#, fuzzy
msgid "Retrying the game"
msgstr "Kreiranje Sadržaja"

#: ../../docs/getting_started/first_3d_game/08.score_and_replay.rst:182
msgid ""
"We'll now add the ability to play again after dying. When the player dies, "
"we'll display a message on the screen and wait for input."
msgstr ""

#: ../../docs/getting_started/first_3d_game/08.score_and_replay.rst:185
msgid ""
"Head back to the ``main.tscn`` scene, select the ``UserInterface`` node, add "
"a child node :ref:`ColorRect <class_ColorRect>`, and name it ``Retry``. This "
"node fills a rectangle with a uniform color and will serve as an overlay to "
"darken the screen."
msgstr ""

#: ../../docs/getting_started/first_3d_game/08.score_and_replay.rst:190
msgid ""
"To make it span over the whole viewport, you can use the *Anchor Preset* "
"menu in the toolbar."
msgstr ""

#: ../../docs/getting_started/first_3d_game/08.score_and_replay.rst:195
msgid "Open it and apply the *Full Rect* command."
msgstr ""

#: ../../docs/getting_started/first_3d_game/08.score_and_replay.rst:199
msgid ""
"Nothing happens. Well, almost nothing; only the four green pins move to the "
"corners of the selection box."
msgstr ""

#: ../../docs/getting_started/first_3d_game/08.score_and_replay.rst:204
msgid ""
"This is because UI nodes (all the ones with a green icon) work with anchors "
"and margins relative to their parent's bounding box. Here, the "
"``UserInterface`` node has a small size and the ``Retry`` one is limited by "
"it."
msgstr ""

#: ../../docs/getting_started/first_3d_game/08.score_and_replay.rst:208
msgid ""
"Select the ``UserInterface`` and apply *Anchor Preset -> Full Rect* to it as "
"well. The ``Retry`` node should now span the whole viewport."
msgstr ""

#: ../../docs/getting_started/first_3d_game/08.score_and_replay.rst:211
msgid ""
"Let's change its color so it darkens the game area. Select ``Retry`` and in "
"the *Inspector*, set its *Color* to something both dark and transparent. To "
"do so, in the color picker, drag the *A* slider to the left. It controls the "
"color's Alpha channel, that is to say, its opacity/transparency."
msgstr ""

#: ../../docs/getting_started/first_3d_game/08.score_and_replay.rst:218
msgid ""
"Next, add a :ref:`Label <class_Label>` as a child of ``Retry`` and give it "
"the *Text* \"Press Enter to retry.\" To move it and anchor it in the center "
"of the screen, apply *Anchor Preset -> Center* to it."
msgstr ""

#: ../../docs/getting_started/first_3d_game/08.score_and_replay.rst:226
msgid "Coding the retry option"
msgstr ""

#: ../../docs/getting_started/first_3d_game/08.score_and_replay.rst:228
msgid ""
"We can now head to the code to show and hide the ``Retry`` node when the "
"player dies and plays again."
msgstr ""

#: ../../docs/getting_started/first_3d_game/08.score_and_replay.rst:231
msgid ""
"Open the script ``main.gd``. First, we want to hide the overlay at the start "
"of the game. Add this line to the ``_ready()`` function."
msgstr ""

#: ../../docs/getting_started/first_3d_game/08.score_and_replay.rst:247
msgid "Then, when the player gets hit, we show the overlay."
msgstr ""

#: ../../docs/getting_started/first_3d_game/08.score_and_replay.rst:264
msgid ""
"Finally, when the ``Retry`` node is visible, we need to listen to the "
"player's input and restart the game if they press enter. To do this, we use "
"the built-in ``_unhandled_input()`` callback, which is triggered on any "
"input."
msgstr ""

#: ../../docs/getting_started/first_3d_game/08.score_and_replay.rst:268
msgid ""
"If the player pressed the predefined ``ui_accept`` input action and "
"``Retry`` is visible, we reload the current scene."
msgstr ""

#: ../../docs/getting_started/first_3d_game/08.score_and_replay.rst:290
msgid ""
"The function ``get_tree()`` gives us access to the global :ref:`SceneTree "
"<class_SceneTree>` object, which allows us to reload and restart the current "
"scene."
msgstr ""

#: ../../docs/getting_started/first_3d_game/08.score_and_replay.rst:295
msgid "Adding music"
msgstr ""

#: ../../docs/getting_started/first_3d_game/08.score_and_replay.rst:297
msgid ""
"To add music that plays continuously in the background, we're going to use "
"another feature in Godot: :ref:`autoloads <doc_singletons_autoload>`."
msgstr ""

#: ../../docs/getting_started/first_3d_game/08.score_and_replay.rst:300
msgid ""
"To play audio, all you need to do is add an :ref:`AudioStreamPlayer "
"<class_AudioStreamPlayer>` node to your scene and attach an audio file to "
"it. When you start the scene, it can play automatically. However, when you "
"reload the scene, like we do to play again, the audio nodes are also reset, "
"and the music starts back from the beginning."
msgstr ""

#: ../../docs/getting_started/first_3d_game/08.score_and_replay.rst:305
msgid ""
"You can use the autoload feature to have Godot load a node or a scene "
"automatically at the start of the game, outside the current scene. You can "
"also use it to create globally accessible objects."
msgstr ""

#: ../../docs/getting_started/first_3d_game/08.score_and_replay.rst:309
msgid ""
"Create a new scene by going to the *Scene* menu and clicking *New Scene* or "
"by using the *+* icon next to your currently opened scene."
msgstr ""

#: ../../docs/getting_started/first_3d_game/08.score_and_replay.rst:314
msgid ""
"Click the *Other Node* button to create an :ref:`AudioStreamPlayer "
"<class_AudioStreamPlayer>` and rename it to ``MusicPlayer``."
msgstr ""

#: ../../docs/getting_started/first_3d_game/08.score_and_replay.rst:319
msgid ""
"We included a music soundtrack in the ``art/`` directory, ``House In a "
"Forest Loop.ogg``. Click and drag it onto the *Stream* property in the "
"*Inspector*. Also, turn on *Autoplay* so the music plays automatically at "
"the start of the game."
msgstr ""

#: ../../docs/getting_started/first_3d_game/08.score_and_replay.rst:326
msgid "Save the scene as ``MusicPlayer.tscn``."
msgstr ""

#: ../../docs/getting_started/first_3d_game/08.score_and_replay.rst:328
msgid ""
"We have to register it as an autoload. Head to the *Project -> Project "
"Settings…* menu and click on the *Autoload* tab."
msgstr ""

#: ../../docs/getting_started/first_3d_game/08.score_and_replay.rst:331
msgid ""
"In the *Path* field, you want to enter the path to your scene. Click the "
"folder icon to open the file browser and double-click on ``MusicPlayer."
"tscn``. Then, click the *Add* button on the right to register the node."
msgstr ""

#: ../../docs/getting_started/first_3d_game/08.score_and_replay.rst:337
msgid ""
"``MusicPlayer.tscn`` now loads into any scene you open or play. So if you "
"run the game now, the music will play automatically in any scene."
msgstr ""

#: ../../docs/getting_started/first_3d_game/08.score_and_replay.rst:340
msgid ""
"Before we wrap up this lesson, here's a quick look at how it works under the "
"hood. When you run the game, your *Scene* dock changes to give you two tabs: "
"*Remote* and *Local*."
msgstr ""

#: ../../docs/getting_started/first_3d_game/08.score_and_replay.rst:346
msgid ""
"The *Remote* tab allows you to visualize the node tree of your running game. "
"There, you will see the *Main* node and everything the scene contains and "
"the instantiated mobs at the bottom."
msgstr ""

#: ../../docs/getting_started/first_3d_game/08.score_and_replay.rst:352
msgid ""
"At the top are the autoloaded ``MusicPlayer`` and a *root* node, which is "
"your game's viewport."
msgstr ""

#: ../../docs/getting_started/first_3d_game/08.score_and_replay.rst:355
msgid ""
"And that does it for this lesson. In the next part, we'll add an animation "
"to make the game both look and feel much nicer."
msgstr ""

#: ../../docs/getting_started/first_3d_game/08.score_and_replay.rst:358
msgid "Here is the complete ``main.gd`` script for reference."
msgstr ""

#: ../../docs/getting_started/first_3d_game/09.adding_animations.rst:6
#, fuzzy
msgid "Character animation"
msgstr "Kreiranje Sadržaja"

#: ../../docs/getting_started/first_3d_game/09.adding_animations.rst:8
msgid ""
"In this final lesson, we'll use Godot's built-in animation tools to make our "
"characters float and flap. You'll learn to design animations in the editor "
"and use code to make your game feel alive."
msgstr ""

#: ../../docs/getting_started/first_3d_game/09.adding_animations.rst:14
#, fuzzy
msgid "We'll start with an introduction to using the animation editor."
msgstr "Uvod"

#: ../../docs/getting_started/first_3d_game/09.adding_animations.rst:17
#, fuzzy
msgid "Using the animation editor"
msgstr "Kreiranje Sadržaja"

#: ../../docs/getting_started/first_3d_game/09.adding_animations.rst:19
msgid ""
"The engine comes with tools to author animations in the editor. You can then "
"use the code to play and control them at runtime."
msgstr ""

#: ../../docs/getting_started/first_3d_game/09.adding_animations.rst:22
msgid ""
"Open the player scene, select the ``Player`` node, and add an :ref:"
"`AnimationPlayer <class_AnimationPlayer>` node."
msgstr ""

#: ../../docs/getting_started/first_3d_game/09.adding_animations.rst:24
msgid "The *Animation* dock appears in the bottom panel."
msgstr ""

#: ../../docs/getting_started/first_3d_game/09.adding_animations.rst:28
msgid ""
"It features a toolbar and the animation drop-down menu at the top, a track "
"editor in the middle that's currently empty, and filter, snap, and zoom "
"options at the bottom."
msgstr ""

#: ../../docs/getting_started/first_3d_game/09.adding_animations.rst:32
msgid "Let's create an animation. Click on *Animation -> New*."
msgstr ""

#: ../../docs/getting_started/first_3d_game/09.adding_animations.rst:36
msgid "Name the animation \"float\"."
msgstr ""

#: ../../docs/getting_started/first_3d_game/09.adding_animations.rst:40
msgid ""
"Once you've created the animation, the timeline appears with numbers "
"representing time in seconds."
msgstr ""

#: ../../docs/getting_started/first_3d_game/09.adding_animations.rst:45
msgid ""
"We want the animation to start playback automatically at the start of the "
"game. Also, it should loop."
msgstr ""

#: ../../docs/getting_started/first_3d_game/09.adding_animations.rst:48
msgid ""
"To do so, you can click the button with an \"A+\" icon in the animation "
"toolbar and the looping arrows, respectively."
msgstr ""

#: ../../docs/getting_started/first_3d_game/09.adding_animations.rst:53
msgid ""
"You can also pin the animation editor by clicking the pin icon in the top-"
"right. This prevents it from folding when you click on the viewport and "
"deselect the nodes."
msgstr ""

#: ../../docs/getting_started/first_3d_game/09.adding_animations.rst:59
msgid ""
"Set the animation duration to ``1.2`` seconds in the top-right of the dock."
msgstr ""

#: ../../docs/getting_started/first_3d_game/09.adding_animations.rst:63
msgid ""
"You should see the gray ribbon widen a bit. It shows you the start and end "
"of your animation and the vertical blue line is your time cursor."
msgstr ""

#: ../../docs/getting_started/first_3d_game/09.adding_animations.rst:68
msgid ""
"You can click and drag the slider in the bottom-right to zoom in and out of "
"the timeline."
msgstr ""

#: ../../docs/getting_started/first_3d_game/09.adding_animations.rst:74
msgid "The float animation"
msgstr ""

#: ../../docs/getting_started/first_3d_game/09.adding_animations.rst:76
msgid ""
"With the animation player node, you can animate most properties on as many "
"nodes as you need. Notice the key icon next to properties in the "
"*Inspector*. You can click any of them to create a keyframe, a time and "
"value pair for the corresponding property. The keyframe gets inserted where "
"your time cursor is in the timeline."
msgstr ""

#: ../../docs/getting_started/first_3d_game/09.adding_animations.rst:82
msgid ""
"Let's insert our first keys. Here, we will animate both the position and the "
"rotation of the ``Character`` node."
msgstr ""

#: ../../docs/getting_started/first_3d_game/09.adding_animations.rst:85
msgid ""
"Select the ``Character`` and in the *Inspector* expand the *Transform* "
"section. Click the key icon next to *Position*, and *Rotation*."
msgstr ""

#: ../../docs/getting_started/first_3d_game/09.adding_animations.rst:91
msgid ""
"For this tutorial, just create RESET Track(s) which is the default choice"
msgstr ""

#: ../../docs/getting_started/first_3d_game/09.adding_animations.rst:93
msgid ""
"Two tracks appear in the editor with a diamond icon representing each "
"keyframe."
msgstr ""

#: ../../docs/getting_started/first_3d_game/09.adding_animations.rst:97
msgid ""
"You can click and drag on the diamonds to move them in time. Move the "
"position key to ``0.3`` seconds and the rotation key to ``0.1`` seconds."
msgstr ""

#: ../../docs/getting_started/first_3d_game/09.adding_animations.rst:102
msgid ""
"Move the time cursor to ``0.5`` seconds by clicking and dragging on the gray "
"timeline."
msgstr ""

#: ../../docs/getting_started/first_3d_game/09.adding_animations.rst:107
msgid ""
"In the *Inspector*, set the *Position*'s *Y* axis to ``0.65`` meters and the "
"*Rotation*' *X* axis to ``8``."
msgstr ""

#: ../../docs/getting_started/first_3d_game/09.adding_animations.rst:111
msgid "Create a keyframe for both properties"
msgstr ""

#: ../../docs/getting_started/first_3d_game/09.adding_animations.rst:115
msgid ""
"Now, move the position keyframe to ``0.7`` seconds by dragging it on the "
"timeline."
msgstr ""

#: ../../docs/getting_started/first_3d_game/09.adding_animations.rst:122
msgid ""
"A lecture on the principles of animation is beyond the scope of this "
"tutorial. Just note that you don't want to time and space everything evenly. "
"Instead, animators play with timing and spacing, two core animation "
"principles. You want to offset and contrast in your character's motion to "
"make them feel alive."
msgstr ""

#: ../../docs/getting_started/first_3d_game/09.adding_animations.rst:128
msgid ""
"Move the time cursor to the end of the animation, at ``1.2`` seconds. Set "
"the Y position to about ``0.35`` and the X rotation to ``-9`` degrees. Once "
"again, create a key for both properties."
msgstr ""

#: ../../docs/getting_started/first_3d_game/09.adding_animations.rst:134
msgid ""
"You can preview the result by clicking the play button or pressing :kbd:"
"`Shift + D`. Click the stop button or press :kbd:`S` to stop playback."
msgstr ""

#: ../../docs/getting_started/first_3d_game/09.adding_animations.rst:139
msgid ""
"You can see that the engine interpolates between your keyframes to produce a "
"continuous animation. At the moment, though, the motion feels very robotic. "
"This is because the default interpolation is linear, causing constant "
"transitions, unlike how living things move in the real world."
msgstr ""

#: ../../docs/getting_started/first_3d_game/09.adding_animations.rst:144
msgid "We can control the transition between keyframes using easing curves."
msgstr ""

#: ../../docs/getting_started/first_3d_game/09.adding_animations.rst:146
msgid ""
"Click and drag around the first two keys in the timeline to box select them."
msgstr ""

#: ../../docs/getting_started/first_3d_game/09.adding_animations.rst:150
msgid ""
"You can edit the properties of both keys simultaneously in the *Inspector*, "
"where you can see an *Easing* property."
msgstr ""

#: ../../docs/getting_started/first_3d_game/09.adding_animations.rst:155
msgid ""
"Click and drag on the curve, pulling it towards the left. This will make it "
"ease-out, that is to say, transition fast initially and slow down as the "
"time cursor reaches the next keyframe."
msgstr ""

#: ../../docs/getting_started/first_3d_game/09.adding_animations.rst:161
msgid ""
"Play the animation again to see the difference. The first half should "
"already feel a bit bouncier."
msgstr ""

#: ../../docs/getting_started/first_3d_game/09.adding_animations.rst:164
msgid "Apply an ease-out to the second keyframe in the rotation track."
msgstr ""

#: ../../docs/getting_started/first_3d_game/09.adding_animations.rst:168
msgid ""
"Do the opposite for the second position keyframe, dragging it to the right."
msgstr ""

#: ../../docs/getting_started/first_3d_game/09.adding_animations.rst:172
msgid "Your animation should look something like this."
msgstr ""

#: ../../docs/getting_started/first_3d_game/09.adding_animations.rst:178
msgid ""
"Animations update the properties of the animated nodes every frame, "
"overriding initial values. If we directly animated the *Player* node, it "
"would prevent us from moving it in code. This is where the *Pivot* node "
"comes in handy: even though we animated the *Character*, we can still move "
"and rotate the *Pivot* and layer changes on top of the animation in a script."
msgstr ""

#: ../../docs/getting_started/first_3d_game/09.adding_animations.rst:185
msgid "If you play the game, the player's creature will now float!"
msgstr ""

#: ../../docs/getting_started/first_3d_game/09.adding_animations.rst:187
msgid ""
"If the creature is a little too close to the floor, you can move the "
"``Pivot`` up to offset it."
msgstr ""

#: ../../docs/getting_started/first_3d_game/09.adding_animations.rst:191
#, fuzzy
msgid "Controlling the animation in code"
msgstr "Kreiranje Sadržaja"

#: ../../docs/getting_started/first_3d_game/09.adding_animations.rst:193
msgid ""
"We can use code to control the animation playback based on the player's "
"input. Let's change the animation speed when the character is moving."
msgstr ""

#: ../../docs/getting_started/first_3d_game/09.adding_animations.rst:196
msgid "Open the ``Player``'s script by clicking the script icon next to it."
msgstr ""

#: ../../docs/getting_started/first_3d_game/09.adding_animations.rst:200
msgid ""
"In ``_physics_process()``, after the line where we check the ``direction`` "
"vector, add the following code."
msgstr ""

#: ../../docs/getting_started/first_3d_game/09.adding_animations.rst:230
msgid ""
"This code makes it so when the player moves, we multiply the playback speed "
"by ``4``. When they stop, we reset it to normal."
msgstr ""

#: ../../docs/getting_started/first_3d_game/09.adding_animations.rst:233
msgid ""
"We mentioned that the ``Pivot`` could layer transforms on top of the "
"animation. We can make the character arc when jumping using the following "
"line of code. Add it at the end of ``_physics_process()``."
msgstr ""

#: ../../docs/getting_started/first_3d_game/09.adding_animations.rst:254
#, fuzzy
msgid "Animating the mobs"
msgstr "Kreiranje Sadržaja"

#: ../../docs/getting_started/first_3d_game/09.adding_animations.rst:256
msgid ""
"Here's another nice trick with animations in Godot: as long as you use a "
"similar node structure, you can copy them to different scenes."
msgstr ""

#: ../../docs/getting_started/first_3d_game/09.adding_animations.rst:259
msgid ""
"For example, both the ``Mob`` and the ``Player`` scenes have a ``Pivot`` and "
"a ``Character`` node, so we can reuse animations between them."
msgstr ""

#: ../../docs/getting_started/first_3d_game/09.adding_animations.rst:262
msgid ""
"Open the *Player* scene, select the AnimationPlayer node and open the "
"\"float\" animation. Next, click on **Animation > Copy**. Then open ``mob."
"tscn``, create an AnimationPlayer child node and select it. Click "
"**Animation > Paste** and make sure that the button with an \"A+\" icon "
"(Autoplay on Load) and the looping arrows (Animation looping) are also "
"turned on in the animation editor in the bottom panel. That's it; all "
"monsters will now play the float animation."
msgstr ""

#: ../../docs/getting_started/first_3d_game/09.adding_animations.rst:269
msgid ""
"We can change the playback speed based on the creature's ``random_speed``. "
"Open the *Mob*'s script and at the end of the ``initialize()`` function, add "
"the following line."
msgstr ""

#: ../../docs/getting_started/first_3d_game/09.adding_animations.rst:288
msgid "And with that, you finished coding your first complete 3D game."
msgstr ""

#: ../../docs/getting_started/first_3d_game/09.adding_animations.rst:290
msgid "**Congratulations**!"
msgstr ""

#: ../../docs/getting_started/first_3d_game/09.adding_animations.rst:292
msgid ""
"In the next part, we'll quickly recap what you learned and give you some "
"links to keep learning more. But for now, here are the complete ``Player."
"gd`` and ``Mob.gd`` so you can check your code against them."
msgstr ""

#: ../../docs/getting_started/first_3d_game/09.adding_animations.rst:296
msgid "Here's the *Player* script."
msgstr ""

#: ../../docs/getting_started/first_3d_game/09.adding_animations.rst:509
msgid "And the *Mob*'s script."
msgstr ""

#: ../../docs/getting_started/first_3d_game/going_further.rst:6
msgid "Going further"
msgstr ""

#: ../../docs/getting_started/first_3d_game/going_further.rst:8
msgid ""
"You can pat yourself on the back for having completed your first 3D game "
"with Godot."
msgstr ""

#: ../../docs/getting_started/first_3d_game/going_further.rst:11
msgid ""
"In this series, we went over a wide range of techniques and editor features. "
"Hopefully, you've witnessed how intuitive Godot's scene system can be and "
"learned a few tricks you can apply in your projects."
msgstr ""

#: ../../docs/getting_started/first_3d_game/going_further.rst:15
msgid ""
"But we just scratched the surface: Godot has a lot more in store for you to "
"save time creating games. And you can learn all that by browsing the "
"documentation."
msgstr ""

#: ../../docs/getting_started/first_3d_game/going_further.rst:18
msgid ""
"Where should you begin? Below, you'll find a few pages to start exploring "
"and build upon what you've learned so far."
msgstr ""

#: ../../docs/getting_started/first_3d_game/going_further.rst:21
#, fuzzy
msgid ""
"But before that, here's a link to download a completed version of the "
"project: `<https://github.com/godotengine/godot-3d-dodge-the-creeps>`_."
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati različite Godo demo projekte "
"`Godot demo projects <https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/getting_started/first_3d_game/going_further.rst:25
msgid "Exploring the manual"
msgstr ""

#: ../../docs/getting_started/first_3d_game/going_further.rst:27
msgid ""
"The manual is your ally whenever you have a doubt or you're curious about a "
"feature. It does not contain tutorials about specific game genres or "
"mechanics. Instead, it explains how Godot works in general. In it, you will "
"find information about 2D, 3D, physics, rendering and performance, and much "
"more."
msgstr ""

#: ../../docs/getting_started/first_3d_game/going_further.rst:32
msgid "Here are the sections we recommend you to explore next:"
msgstr ""

#: ../../docs/getting_started/first_3d_game/going_further.rst:34
msgid ""
"Read the :ref:`Scripting section <toc-scripting-core-features>` to learn "
"essential programming features you'll use in every project."
msgstr ""

#: ../../docs/getting_started/first_3d_game/going_further.rst:36
msgid ""
"The :ref:`3D <toc-learn-features-3d>` and :ref:`Physics <toc-learn-features-"
"physics>` sections will teach you more about 3D game creation in the engine."
msgstr ""

#: ../../docs/getting_started/first_3d_game/going_further.rst:38
msgid ""
":ref:`Inputs <toc-learn-features-inputs>` is another important one for any "
"game project."
msgstr ""

#: ../../docs/getting_started/first_3d_game/going_further.rst:40
msgid ""
"You can start with these or, if you prefer, look at the sidebar menu on the "
"left and pick your options."
msgstr ""

#: ../../docs/getting_started/first_3d_game/going_further.rst:43
msgid ""
"We hope you enjoyed this tutorial series, and we're looking forward to "
"seeing what you achieve using Godot."
msgstr ""

#: ../../docs/tutorials/best_practices/introduction_best_practices.rst:6
msgid ""
"This series is a collection of best practices to help you work efficiently "
"with Godot."
msgstr ""

#: ../../docs/tutorials/best_practices/introduction_best_practices.rst:9
msgid ""
"Godot allows for a great amount of flexibility in how you structure a "
"project's codebase and break it down into scenes. Each approach has its pros "
"and cons, and they can be hard to weigh until you've worked with the engine "
"for long enough."
msgstr ""

#: ../../docs/tutorials/best_practices/introduction_best_practices.rst:13
msgid ""
"There are always many ways to structure your code and solve specific "
"programming problems. It would be impossible to cover them all here."
msgstr ""

#: ../../docs/tutorials/best_practices/introduction_best_practices.rst:16
msgid ""
"That is why each article starts from a real-world problem. We will break "
"down each problem in fundamental questions, suggest solutions, analyze the "
"pros and cons of each option, and highlight the best course of action for "
"the problem at hand."
msgstr ""

#: ../../docs/tutorials/best_practices/introduction_best_practices.rst:20
msgid ""
"You should start by reading :ref:`doc_what_are_godot_classes`. It explains "
"how Godot's nodes and scenes relate to classes and objects in other Object-"
"Oriented programming languages. It will help you make sense of the rest of "
"the series."
msgstr ""

#: ../../docs/tutorials/best_practices/introduction_best_practices.rst:26
msgid ""
"The best practices in Godot rely on Object-Oriented design principles. We "
"use tools like the `single responsibility <https://en.wikipedia.org/wiki/"
"Single_responsibility_principle>`_ principle and `encapsulation <https://en."
"wikipedia.org/wiki/Encapsulation_(computer_programming)>`_."
msgstr ""

#: ../../docs/tutorials/best_practices/what_are_godot_classes.rst:4
msgid "Applying object-oriented principles in Godot"
msgstr ""

#: ../../docs/tutorials/best_practices/what_are_godot_classes.rst:6
msgid ""
"The engine offers two main ways to create reusable objects: scripts and "
"scenes. Neither of these technically define classes under the hood."
msgstr ""

#: ../../docs/tutorials/best_practices/what_are_godot_classes.rst:9
msgid ""
"Still, many best practices using Godot involve applying object-oriented "
"programming principles to the scripts and scenes that compose your game. "
"That is why it's useful to understand how we can think of them as classes."
msgstr ""

#: ../../docs/tutorials/best_practices/what_are_godot_classes.rst:13
msgid ""
"This guide briefly explains how scripts and scenes work in the engine's core "
"to help you understand how they work under the hood."
msgstr ""

#: ../../docs/tutorials/best_practices/what_are_godot_classes.rst:17
msgid "How scripts work in the engine"
msgstr ""

#: ../../docs/tutorials/best_practices/what_are_godot_classes.rst:19
msgid ""
"The engine provides built-in classes like :ref:`Node <class_Node>`. You can "
"extend those to create derived types using a script."
msgstr ""

#: ../../docs/tutorials/best_practices/what_are_godot_classes.rst:22
msgid ""
"These scripts are not technically classes. Instead, they are resources that "
"tell the engine a sequence of initializations to perform on one of the "
"engine's built-in classes."
msgstr ""

#: ../../docs/tutorials/best_practices/what_are_godot_classes.rst:25
msgid ""
"Godot's internal classes have methods that register a class's data with a :"
"ref:`ClassDB <class_ClassDB>`. This database provides runtime access to "
"class information. ``ClassDB`` contains information about classes like:"
msgstr ""

#: ../../docs/tutorials/best_practices/what_are_godot_classes.rst:29
msgid "Properties."
msgstr ""

#: ../../docs/tutorials/best_practices/what_are_godot_classes.rst:30
msgid "Methods."
msgstr ""

#: ../../docs/tutorials/best_practices/what_are_godot_classes.rst:31
msgid "Constants."
msgstr ""

#: ../../docs/tutorials/best_practices/what_are_godot_classes.rst:32
msgid "Signals."
msgstr ""

#: ../../docs/tutorials/best_practices/what_are_godot_classes.rst:34
msgid ""
"This ``ClassDB`` is what objects check against when performing an operation "
"like accessing a property or calling a method. It checks the database's "
"records and the object's base types' records to see if the object supports "
"the operation."
msgstr ""

#: ../../docs/tutorials/best_practices/what_are_godot_classes.rst:38
msgid ""
"Attaching a :ref:`Script <class_Script>` to your object extends the methods, "
"properties, and signals available from the ``ClassDB``."
msgstr ""

#: ../../docs/tutorials/best_practices/what_are_godot_classes.rst:43
msgid ""
"Even scripts that don't use the ``extends`` keyword implicitly inherit from "
"the engine's base :ref:`RefCounted <class_RefCounted>` class. As a result, "
"you can instantiate scripts without the ``extends`` keyword from code. Since "
"they extend ``RefCounted`` though, you cannot attach them to a :ref:`Node "
"<class_Node>`."
msgstr ""

#: ../../docs/tutorials/best_practices/what_are_godot_classes.rst:51
msgid ""
"The behavior of scenes has many similarities to classes, so it can make "
"sense to think of a scene as a class. Scenes are reusable, instantiable, and "
"inheritable groups of nodes. Creating a scene is similar to having a script "
"that creates nodes and adds them as children using ``add_child()``."
msgstr ""

#: ../../docs/tutorials/best_practices/what_are_godot_classes.rst:55
msgid ""
"We often pair a scene with a scripted root node that makes use of the "
"scene's nodes. As such, the script extends the scene by adding behavior "
"through imperative code."
msgstr ""

#: ../../docs/tutorials/best_practices/what_are_godot_classes.rst:58
msgid "The content of a scene helps to define:"
msgstr ""

#: ../../docs/tutorials/best_practices/what_are_godot_classes.rst:60
msgid "What nodes are available to the script."
msgstr ""

#: ../../docs/tutorials/best_practices/what_are_godot_classes.rst:61
msgid "How they are organized."
msgstr ""

#: ../../docs/tutorials/best_practices/what_are_godot_classes.rst:62
msgid "How they are initialized."
msgstr ""

#: ../../docs/tutorials/best_practices/what_are_godot_classes.rst:63
msgid "What signal connections they have with each other."
msgstr ""

#: ../../docs/tutorials/best_practices/what_are_godot_classes.rst:65
msgid ""
"Why is any of this important to scene organization? Because instances of "
"scenes *are* objects. As a result, many object-oriented principles that "
"apply to written code also apply to scenes: single responsibility, "
"encapsulation, and others."
msgstr ""

#: ../../docs/tutorials/best_practices/what_are_godot_classes.rst:69
msgid ""
"The scene is *always an extension of the script attached to its root node*, "
"so you can interpret it as part of a class."
msgstr ""

#: ../../docs/tutorials/best_practices/what_are_godot_classes.rst:72
msgid ""
"Most of the techniques explained in this best practices series build on this "
"point."
msgstr ""

#: ../../docs/tutorials/best_practices/scene_organization.rst:4
msgid "Scene organization"
msgstr ""

#: ../../docs/tutorials/best_practices/scene_organization.rst:6
msgid ""
"This article covers topics related to the effective organization of scene "
"content. Which nodes should one use? Where should one place them? How should "
"they interact?"
msgstr ""

#: ../../docs/tutorials/best_practices/scene_organization.rst:11
msgid "How to build relationships effectively"
msgstr ""

#: ../../docs/tutorials/best_practices/scene_organization.rst:13
msgid ""
"When Godot users begin crafting their own scenes, they often run into the "
"following problem:"
msgstr ""

#: ../../docs/tutorials/best_practices/scene_organization.rst:16
msgid ""
"They create their first scene and fill it with content only to eventually "
"end up saving branches of their scene into separate scenes as the nagging "
"feeling that they should split things up starts to accumulate. However, they "
"then notice that the hard references they were able to rely on before are no "
"longer possible. Re-using the scene in multiple places creates issues "
"because the node paths do not find their targets and signal connections "
"established in the editor break."
msgstr ""

#: ../../docs/tutorials/best_practices/scene_organization.rst:24
msgid ""
"To fix these problems, one must instantiate the sub-scenes without them "
"requiring details about their environment. One needs to be able to trust "
"that the sub-scene will create itself without being picky about how one uses "
"it."
msgstr ""

#: ../../docs/tutorials/best_practices/scene_organization.rst:29
msgid ""
"One of the biggest things to consider in OOP is maintaining focused, "
"singular-purpose classes with `loose coupling <https://en.wikipedia.org/wiki/"
"Loose_coupling>`_ to other parts of the codebase. This keeps the size of "
"objects small (for maintainability) and improves their reusability."
msgstr ""

#: ../../docs/tutorials/best_practices/scene_organization.rst:35
msgid ""
"These OOP best practices have *several* implications for best practices in "
"scene structure and script usage."
msgstr ""

#: ../../docs/tutorials/best_practices/scene_organization.rst:38
msgid ""
"**If at all possible, one should design scenes to have no dependencies.** "
"That is, one should create scenes that keep everything they need within "
"themselves."
msgstr ""

#: ../../docs/tutorials/best_practices/scene_organization.rst:42
msgid ""
"If a scene must interact with an external context, experienced developers "
"recommend the use of `Dependency Injection <https://en.wikipedia.org/wiki/"
"Dependency_injection>`_. This technique involves having a high-level API "
"provide the dependencies of the low-level API. Why do this? Because classes "
"which rely on their external environment can inadvertently trigger bugs and "
"unexpected behavior."
msgstr ""

#: ../../docs/tutorials/best_practices/scene_organization.rst:49
msgid ""
"To do this, one must expose data and then rely on a parent context to "
"initialize it:"
msgstr ""

#: ../../docs/tutorials/best_practices/scene_organization.rst:52
msgid ""
"Connect to a signal. Extremely safe, but should be used only to \"respond\" "
"to behavior, not start it. By convention, signal names are usually past-"
"tense verbs like \"entered\", \"skill_activated\", or \"item_collected\"."
msgstr ""

#: ../../docs/tutorials/best_practices/scene_organization.rst:73
msgid "Call a method. Used to start behavior."
msgstr ""

#: ../../docs/tutorials/best_practices/scene_organization.rst:92
msgid ""
"Initialize a :ref:`Callable <class_Callable>` property. Safer than a method "
"as ownership of the method is unnecessary. Used to start behavior."
msgstr ""

#: ../../docs/tutorials/best_practices/scene_organization.rst:112
msgid "Initialize a Node or other Object reference."
msgstr ""

#: ../../docs/tutorials/best_practices/scene_organization.rst:131
msgid "Initialize a NodePath."
msgstr ""

#: ../../docs/tutorials/best_practices/scene_organization.rst:150
msgid ""
"These options hide the points of access from the child node. This in turn "
"keeps the child **loosely coupled** to its environment. One can reuse it in "
"another context without any extra changes to its API."
msgstr ""

#: ../../docs/tutorials/best_practices/scene_organization.rst:156
msgid ""
"Although the examples above illustrate parent-child relationships, the same "
"principles apply towards all object relations. Nodes which are siblings "
"should only be aware of their hierarchies while an ancestor mediates their "
"communications and references."
msgstr ""

#: ../../docs/tutorials/best_practices/scene_organization.rst:203
msgid ""
"The same principles also apply to non-Node objects that maintain "
"dependencies on other objects. Whichever object actually owns the objects "
"should manage the relationships between them."
msgstr ""

#: ../../docs/tutorials/best_practices/scene_organization.rst:209
msgid ""
"One should favor keeping data in-house (internal to a scene) though as "
"placing a dependency on an external context, even a loosely coupled one, "
"still means that the node will expect something in its environment to be "
"true. The project's design philosophies should prevent this from happening. "
"If not, the code's inherent liabilities will force developers to use "
"documentation to keep track of object relations on a microscopic scale; this "
"is otherwise known as development hell. Writing code that relies on external "
"documentation for one to use it safely is error-prone by default."
msgstr ""

#: ../../docs/tutorials/best_practices/scene_organization.rst:218
msgid ""
"To avoid creating and maintaining such documentation, one converts the "
"dependent node (\"child\" above) into a tool script that implements "
"``_get_configuration_warnings()``. Returning a non-empty PackedStringArray "
"from it will make the Scene dock generate a warning icon with the string(s) "
"as a tooltip by the node. This is the same icon that appears for nodes such "
"as the :ref:`Area2D <class_Area2D>` node when it has no child :ref:"
"`CollisionShape2D <class_CollisionShape2D>` nodes defined. The editor then "
"self-documents the scene through the script code. No content duplication via "
"documentation is necessary."
msgstr ""

#: ../../docs/tutorials/best_practices/scene_organization.rst:229
msgid ""
"A GUI like this can better inform project users of critical information "
"about a Node. Does it have external dependencies? Have those dependencies "
"been satisfied? Other programmers, and especially designers and writers, "
"will need clear instructions in the messages telling them what to do to "
"configure it."
msgstr ""

#: ../../docs/tutorials/best_practices/scene_organization.rst:234
msgid ""
"So, why does all this complex switcheroo work? Well, because scenes operate "
"best when they operate alone. If unable to work alone, then working with "
"others anonymously (with minimal hard dependencies, i.e. loose coupling) is "
"the next best thing. Inevitably, changes may need to be made to a class and "
"if these changes cause it to interact with other scenes in unforeseen ways, "
"then things will start to break down. The whole point of all this "
"indirection is to avoid ending up in a situation where changing one class "
"results in adversely effecting other classes dependent on it."
msgstr ""

#: ../../docs/tutorials/best_practices/scene_organization.rst:243
msgid ""
"Scripts and scenes, as extensions of engine classes, should abide by *all* "
"OOP principles. Examples include..."
msgstr ""

#: ../../docs/tutorials/best_practices/scene_organization.rst:246
msgid "`SOLID <https://en.wikipedia.org/wiki/SOLID>`_"
msgstr ""

#: ../../docs/tutorials/best_practices/scene_organization.rst:247
msgid "`DRY <https://en.wikipedia.org/wiki/Don%27t_repeat_yourself>`_"
msgstr ""

#: ../../docs/tutorials/best_practices/scene_organization.rst:248
msgid "`KISS <https://en.wikipedia.org/wiki/KISS_principle>`_"
msgstr ""

#: ../../docs/tutorials/best_practices/scene_organization.rst:249
msgid "`YAGNI <https://en.wikipedia.org/wiki/You_aren%27t_gonna_need_it>`_"
msgstr ""

#: ../../docs/tutorials/best_practices/scene_organization.rst:252
msgid "Choosing a node tree structure"
msgstr ""

#: ../../docs/tutorials/best_practices/scene_organization.rst:254
msgid ""
"So, a developer starts work on a game only to stop at the vast possibilities "
"before them. They might know what they want to do, what systems they want to "
"have, but *where* to put them all? Well, how one goes about making their "
"game is always up to them. One can construct node trees in countless ways. "
"But, for those who are unsure, this helpful guide can give them a sample of "
"a decent structure to start with."
msgstr ""

#: ../../docs/tutorials/best_practices/scene_organization.rst:261
msgid ""
"A game should always have a sort of \"entry point\"; somewhere the developer "
"can definitively track where things begin so that they can follow the logic "
"as it continues elsewhere. This place also serves as a bird's eye view of "
"all of the other data and logic in the program. For traditional "
"applications, this would be the \"main\" function. In this case, it would be "
"a Main node."
msgstr ""

#: ../../docs/tutorials/best_practices/scene_organization.rst:267
#: ../../docs/tutorials/best_practices/scene_organization.rst:278
msgid "Node \"Main\" (main.gd)"
msgstr ""

#: ../../docs/tutorials/best_practices/scene_organization.rst:269
msgid ""
"The ``main.gd`` script would then serve as the primary controller of one's "
"game."
msgstr ""

#: ../../docs/tutorials/best_practices/scene_organization.rst:272
msgid ""
"Then one has their actual in-game \"World\" (a 2D or 3D one). This can be a "
"child of Main. In addition, one will need a primary GUI for their game that "
"manages the various menus and widgets the project needs."
msgstr ""

#: ../../docs/tutorials/best_practices/scene_organization.rst:277
msgid "Node2D/Node3D \"World\" (game_world.gd)"
msgstr ""

#: ../../docs/tutorials/best_practices/scene_organization.rst:278
msgid "Control \"GUI\" (gui.gd)"
msgstr ""

#: ../../docs/tutorials/best_practices/scene_organization.rst:280
msgid ""
"When changing levels, one can then swap out the children of the \"World\" "
"node. :ref:`Changing scenes manually <doc_change_scenes_manually>` gives "
"users full control over how their game world transitions."
msgstr ""

#: ../../docs/tutorials/best_practices/scene_organization.rst:284
msgid ""
"The next step is to consider what gameplay systems one's project requires. "
"If one has a system that..."
msgstr ""

#: ../../docs/tutorials/best_practices/scene_organization.rst:287
msgid "tracks all of its data internally"
msgstr ""

#: ../../docs/tutorials/best_practices/scene_organization.rst:288
msgid "should be globally accessible"
msgstr ""

#: ../../docs/tutorials/best_practices/scene_organization.rst:289
msgid "should exist in isolation"
msgstr ""

#: ../../docs/tutorials/best_practices/scene_organization.rst:291
msgid ""
"... then one should create an :ref:`autoload 'singleton' node "
"<doc_singletons_autoload>`."
msgstr ""

#: ../../docs/tutorials/best_practices/scene_organization.rst:295
msgid ""
"For smaller games, a simpler alternative with less control would be to have "
"a \"Game\" singleton that simply calls the :ref:`SceneTree."
"change_scene_to_file() <class_SceneTree_method_change_scene_to_file>` method "
"to swap out the main scene's content. This structure more or less keeps the "
"\"World\" as the main game node."
msgstr ""

#: ../../docs/tutorials/best_practices/scene_organization.rst:301
msgid ""
"Any GUI would need to also be a singleton; be a transitory part of the "
"\"World\"; or be manually added as a direct child of the root. Otherwise, "
"the GUI nodes would also delete themselves during scene transitions."
msgstr ""

#: ../../docs/tutorials/best_practices/scene_organization.rst:306
msgid ""
"If one has systems that modify other systems' data, one should define those "
"as their own scripts or scenes rather than autoloads. For more information "
"on the reasons, please see the :ref:`Autoloads versus regular nodes "
"<doc_autoloads_versus_internal_nodes>` documentation."
msgstr ""

#: ../../docs/tutorials/best_practices/scene_organization.rst:312
msgid ""
"Each subsystem within one's game should have its own section within the "
"SceneTree. One should use parent-child relationships only in cases where "
"nodes are effectively elements of their parents. Does removing the parent "
"reasonably mean that one should also remove the children? If not, then it "
"should have its own place in the hierarchy as a sibling or some other "
"relation."
msgstr ""

#: ../../docs/tutorials/best_practices/scene_organization.rst:320
msgid ""
"In some cases, one needs these separated nodes to *also* position themselves "
"relative to each other. One can use the :ref:`RemoteTransform "
"<class_RemoteTransform3D>` / :ref:`RemoteTransform2D "
"<class_RemoteTransform2D>` nodes for this purpose. They will allow a target "
"node to conditionally inherit selected transform elements from the Remote\\* "
"node. To assign the ``target`` :ref:`NodePath <class_NodePath>`, use one of "
"the following:"
msgstr ""

#: ../../docs/tutorials/best_practices/scene_organization.rst:328
msgid ""
"A reliable third party, likely a parent node, to mediate the assignment."
msgstr ""

#: ../../docs/tutorials/best_practices/scene_organization.rst:329
msgid ""
"A group, to easily pull a reference to the desired node (assuming there will "
"only ever be one of the targets)."
msgstr ""

#: ../../docs/tutorials/best_practices/scene_organization.rst:332
msgid ""
"When should one do this? Well, this is subjective. The dilemma arises when "
"one must micro-manage when a node must move around the SceneTree to preserve "
"itself. For example..."
msgstr ""

#: ../../docs/tutorials/best_practices/scene_organization.rst:336
msgid "Add a \"player\" node to a \"room\"."
msgstr ""

#: ../../docs/tutorials/best_practices/scene_organization.rst:337
msgid "Need to change rooms, so one must delete the current room."
msgstr ""

#: ../../docs/tutorials/best_practices/scene_organization.rst:338
msgid ""
"Before the room can be deleted, one must preserve and/or move the player."
msgstr ""

#: ../../docs/tutorials/best_practices/scene_organization.rst:340
msgid "Is memory a concern?"
msgstr ""

#: ../../docs/tutorials/best_practices/scene_organization.rst:342
msgid ""
"If not, one can just create the two rooms, move the player and delete the "
"old one. No problem."
msgstr ""

#: ../../docs/tutorials/best_practices/scene_organization.rst:345
msgid "If so, one will need to..."
msgstr ""

#: ../../docs/tutorials/best_practices/scene_organization.rst:347
msgid "Move the player somewhere else in the tree."
msgstr ""

#: ../../docs/tutorials/best_practices/scene_organization.rst:348
msgid "Delete the room."
msgstr ""

#: ../../docs/tutorials/best_practices/scene_organization.rst:349
msgid "Instantiate and add the new room."
msgstr ""

#: ../../docs/tutorials/best_practices/scene_organization.rst:350
msgid "Re-add the player."
msgstr ""

#: ../../docs/tutorials/best_practices/scene_organization.rst:352
msgid ""
"The issue is that the player here is a \"special case\"; one where the "
"developers must *know* that they need to handle the player this way for the "
"project. As such, the only way to reliably share this information as a team "
"is to *document* it. Keeping implementation details in documentation however "
"is dangerous. It's a maintenance burden, strains code readability, and "
"bloats the intellectual content of a project unnecessarily."
msgstr ""

#: ../../docs/tutorials/best_practices/scene_organization.rst:359
msgid ""
"In a more complex game with larger assets, it can be a better idea to simply "
"keep the player somewhere else in the SceneTree entirely. This results in:"
msgstr ""

#: ../../docs/tutorials/best_practices/scene_organization.rst:362
msgid "More consistency."
msgstr ""

#: ../../docs/tutorials/best_practices/scene_organization.rst:363
msgid "No \"special cases\" that must be documented and maintained somewhere."
msgstr ""

#: ../../docs/tutorials/best_practices/scene_organization.rst:364
msgid ""
"No opportunity for errors to occur because these details are not accounted "
"for."
msgstr ""

#: ../../docs/tutorials/best_practices/scene_organization.rst:367
msgid ""
"In contrast, if one ever needs to have a child node that does *not* inherit "
"the transform of their parent, one has the following options:"
msgstr ""

#: ../../docs/tutorials/best_practices/scene_organization.rst:370
msgid ""
"The **declarative** solution: place a :ref:`Node <class_Node>` in between "
"them. As nodes with no transform, Nodes will not pass along such information "
"to their children."
msgstr ""

#: ../../docs/tutorials/best_practices/scene_organization.rst:373
msgid ""
"The **imperative** solution: Use the ``top_level`` property for the :ref:"
"`CanvasItem <class_CanvasItem_property_top_level>` or :ref:`Node3D "
"<class_Node3D_property_top_level>` node. This will make the node ignore its "
"inherited transform."
msgstr ""

#: ../../docs/tutorials/best_practices/scene_organization.rst:380
msgid ""
"If building a networked game, keep in mind which nodes and gameplay systems "
"are relevant to all players versus those just pertinent to the authoritative "
"server. For example, users do not all need to have a copy of every players' "
"\"PlayerController\" logic. Instead, they need only their own. As such, "
"keeping these in a separate branch from the \"world\" can help simplify the "
"management of game connections and the like."
msgstr ""

#: ../../docs/tutorials/best_practices/scene_organization.rst:387
msgid ""
"The key to scene organization is to consider the SceneTree in relational "
"terms rather than spatial terms. Are the nodes dependent on their parent's "
"existence? If not, then they can thrive all by themselves somewhere else. If "
"they are dependent, then it stands to reason that they should be children of "
"that parent (and likely part of that parent's scene if they aren't already)."
msgstr ""

#: ../../docs/tutorials/best_practices/scene_organization.rst:393
msgid ""
"Does this mean nodes themselves are components? Not at all. Godot's node "
"trees form an aggregation relationship, not one of composition. But while "
"one still has the flexibility to move nodes around, it is still best when "
"such moves are unnecessary by default."
msgstr ""

#: ../../docs/tutorials/best_practices/scenes_versus_scripts.rst:4
msgid "When to use scenes versus scripts"
msgstr ""

#: ../../docs/tutorials/best_practices/scenes_versus_scripts.rst:6
msgid ""
"We've already covered how scenes and scripts are different. Scripts define "
"an engine class extension with imperative code, scenes with declarative code."
msgstr ""

#: ../../docs/tutorials/best_practices/scenes_versus_scripts.rst:10
msgid ""
"Each system's capabilities are different as a result. Scenes can define how "
"an extended class initializes, but not what its behavior actually is. Scenes "
"are often used in conjunction with a script, the scene declaring a "
"composition of nodes, and the script adding behaviour with imperative code."
msgstr ""

#: ../../docs/tutorials/best_practices/scenes_versus_scripts.rst:16
msgid "Anonymous types"
msgstr ""

#: ../../docs/tutorials/best_practices/scenes_versus_scripts.rst:18
msgid ""
"It *is* possible to completely define a scenes' contents using a script "
"alone. This is, in essence, what the Godot Editor does, only in the C++ "
"constructor of its objects."
msgstr ""

#: ../../docs/tutorials/best_practices/scenes_versus_scripts.rst:22
msgid ""
"But, choosing which one to use can be a dilemma. Creating script instances "
"is identical to creating in-engine classes whereas handling scenes requires "
"a change in API:"
msgstr ""

#: ../../docs/tutorials/best_practices/scenes_versus_scripts.rst:62
msgid ""
"Also, scripts will operate a little slower than scenes due to the speed "
"differences between engine and script code. The larger and more complex the "
"node, the more reason there is to build it as a scene."
msgstr ""

#: ../../docs/tutorials/best_practices/scenes_versus_scripts.rst:67
msgid "Named types"
msgstr ""

#: ../../docs/tutorials/best_practices/scenes_versus_scripts.rst:69
msgid ""
"Scripts can be registered as a new type within the editor itself. This "
"displays it as a new type in the node or resource creation dialog with an "
"optional icon. This way, the user's ability to use the script is much more "
"streamlined. Rather than having to..."
msgstr ""

#: ../../docs/tutorials/best_practices/scenes_versus_scripts.rst:74
msgid "Know the base type of the script they would like to use."
msgstr ""

#: ../../docs/tutorials/best_practices/scenes_versus_scripts.rst:76
msgid "Create an instance of that base type."
msgstr ""

#: ../../docs/tutorials/best_practices/scenes_versus_scripts.rst:78
msgid "Add the script to the node."
msgstr ""

#: ../../docs/tutorials/best_practices/scenes_versus_scripts.rst:80
msgid ""
"With a registered script, the scripted type instead becomes a creation "
"option like the other nodes and resources in the system. The creation dialog "
"even has a search bar to look up the type by name."
msgstr ""

#: ../../docs/tutorials/best_practices/scenes_versus_scripts.rst:85
#, fuzzy
msgid "There are two systems for registering types:"
msgstr "Ne postoje ograničenja prilikom korištenja Godot-a"

#: ../../docs/tutorials/best_practices/scenes_versus_scripts.rst:87
msgid ":ref:`Custom Types <doc_making_plugins>`"
msgstr ""

#: ../../docs/tutorials/best_practices/scenes_versus_scripts.rst:89
msgid "Editor-only. Typenames are not accessible at runtime."
msgstr ""

#: ../../docs/tutorials/best_practices/scenes_versus_scripts.rst:91
msgid "Does not support inherited custom types."
msgstr ""

#: ../../docs/tutorials/best_practices/scenes_versus_scripts.rst:93
msgid "An initializer tool. Creates the node with the script. Nothing more."
msgstr ""

#: ../../docs/tutorials/best_practices/scenes_versus_scripts.rst:95
msgid ""
"Editor has no type-awareness of the script or its relationship to other "
"engine types or scripts."
msgstr ""

#: ../../docs/tutorials/best_practices/scenes_versus_scripts.rst:98
#: ../../docs/tutorials/best_practices/scenes_versus_scripts.rst:116
msgid "Allows users to define an icon."
msgstr ""

#: ../../docs/tutorials/best_practices/scenes_versus_scripts.rst:100
msgid ""
"Works for all scripting languages because it deals with Script resources in "
"abstract."
msgstr ""

#: ../../docs/tutorials/best_practices/scenes_versus_scripts.rst:102
msgid ""
"Set up using :ref:`EditorPlugin.add_custom_type "
"<class_EditorPlugin_method_add_custom_type>`."
msgstr ""

#: ../../docs/tutorials/best_practices/scenes_versus_scripts.rst:104
msgid ":ref:`Script Classes <doc_gdscript_basics_class_name>`"
msgstr ""

#: ../../docs/tutorials/best_practices/scenes_versus_scripts.rst:106
msgid "Editor and runtime accessible."
msgstr ""

#: ../../docs/tutorials/best_practices/scenes_versus_scripts.rst:108
msgid "Displays inheritance relationships in full."
msgstr ""

#: ../../docs/tutorials/best_practices/scenes_versus_scripts.rst:110
msgid ""
"Creates the node with the script, but can also change types or extend the "
"type from the editor."
msgstr ""

#: ../../docs/tutorials/best_practices/scenes_versus_scripts.rst:113
msgid ""
"Editor is aware of inheritance relationships between scripts, script "
"classes, and engine C++ classes."
msgstr ""

#: ../../docs/tutorials/best_practices/scenes_versus_scripts.rst:118
msgid ""
"Engine developers must add support for languages manually (both name "
"exposure and runtime accessibility)."
msgstr ""

#: ../../docs/tutorials/best_practices/scenes_versus_scripts.rst:121
msgid "Godot 3.1+ only."
msgstr ""

#: ../../docs/tutorials/best_practices/scenes_versus_scripts.rst:123
msgid ""
"The Editor scans project folders and registers any exposed names for all "
"scripting languages. Each scripting language must implement its own support "
"for exposing this information."
msgstr ""

#: ../../docs/tutorials/best_practices/scenes_versus_scripts.rst:127
msgid ""
"Both methodologies add names to the creation dialog, but script classes, in "
"particular, also allow for users to access the typename without loading the "
"script resource. Creating instances and accessing constants or static "
"methods is viable from anywhere."
msgstr ""

#: ../../docs/tutorials/best_practices/scenes_versus_scripts.rst:132
msgid ""
"With features like these, one may wish their type to be a script without a "
"scene due to the ease of use it grants users. Those developing plugins or "
"creating in-house tools for designers to use will find an easier time of "
"things this way."
msgstr ""

#: ../../docs/tutorials/best_practices/scenes_versus_scripts.rst:137
msgid ""
"On the downside, it also means having to use largely imperative programming."
msgstr ""

#: ../../docs/tutorials/best_practices/scenes_versus_scripts.rst:140
msgid "Performance of Script vs PackedScene"
msgstr ""

#: ../../docs/tutorials/best_practices/scenes_versus_scripts.rst:142
msgid ""
"One last aspect to consider when choosing scenes and scripts is execution "
"speed."
msgstr ""

#: ../../docs/tutorials/best_practices/scenes_versus_scripts.rst:144
msgid ""
"As the size of objects increases, the scripts' necessary size to create and "
"initialize them grows much larger. Creating node hierarchies demonstrates "
"this. Each Node's logic could be several hundred lines of code in length."
msgstr ""

#: ../../docs/tutorials/best_practices/scenes_versus_scripts.rst:148
msgid ""
"The code example below creates a new ``Node``, changes its name, assigns a "
"script to it, sets its future parent as its owner so it gets saved to disk "
"along with it, and finally adds it as a child of the ``Main`` node:"
msgstr ""

#: ../../docs/tutorials/best_practices/scenes_versus_scripts.rst:187
msgid ""
"Script code like this is much slower than engine-side C++ code. Each "
"instruction makes a call to the scripting API which leads to many "
"\"lookups\" on the back-end to find the logic to execute."
msgstr ""

#: ../../docs/tutorials/best_practices/scenes_versus_scripts.rst:191
msgid ""
"Scenes help to avoid this performance issue. :ref:`PackedScene "
"<class_PackedScene>`, the base type that scenes inherit from, defines "
"resources that use serialized data to create objects. The engine can process "
"scenes in batches on the back-end and provide much better performance than "
"scripts."
msgstr ""

#: ../../docs/tutorials/best_practices/scenes_versus_scripts.rst:197
#: ../../docs/tutorials/shaders/your_first_shader/your_first_2d_shader.rst:241
msgid "Conclusion"
msgstr ""

#: ../../docs/tutorials/best_practices/scenes_versus_scripts.rst:199
msgid "In the end, the best approach is to consider the following:"
msgstr ""

#: ../../docs/tutorials/best_practices/scenes_versus_scripts.rst:201
msgid ""
"If one wishes to create a basic tool that is going to be re-used in several "
"different projects and which people of all skill levels will likely use "
"(including those who don't label themselves as \"programmers\"), then "
"chances are that it should probably be a script, likely one with a custom "
"name/icon."
msgstr ""

#: ../../docs/tutorials/best_practices/scenes_versus_scripts.rst:206
msgid ""
"If one wishes to create a concept that is particular to their game, then it "
"should always be a scene. Scenes are easier to track/edit and provide more "
"security than scripts."
msgstr ""

#: ../../docs/tutorials/best_practices/scenes_versus_scripts.rst:210
msgid ""
"If one would like to give a name to a scene, then they can still sort of do "
"this by declaring a script class and giving it a scene as a constant. The "
"script becomes, in effect, a namespace:"
msgstr ""

#: ../../docs/tutorials/best_practices/autoloads_versus_internal_nodes.rst:4
msgid "Autoloads versus regular nodes"
msgstr ""

#: ../../docs/tutorials/best_practices/autoloads_versus_internal_nodes.rst:6
msgid ""
"Godot offers a feature to automatically load nodes at the root of your "
"project, allowing you to access them globally, that can fulfill the role of "
"a Singleton: :ref:`doc_singletons_autoload`. These autoloaded nodes are not "
"freed when you change the scene from code with :ref:`SceneTree."
"change_scene_to_file <class_SceneTree_method_change_scene_to_file>`."
msgstr ""

#: ../../docs/tutorials/best_practices/autoloads_versus_internal_nodes.rst:11
msgid ""
"In this guide, you will learn when to use the Autoload feature, and "
"techniques you can use to avoid it."
msgstr ""

#: ../../docs/tutorials/best_practices/autoloads_versus_internal_nodes.rst:15
msgid "The cutting audio issue"
msgstr ""

#: ../../docs/tutorials/best_practices/autoloads_versus_internal_nodes.rst:17
msgid ""
"Other engines can encourage the use of creating manager classes, singletons "
"that organize a lot of functionality into a globally accessible object. "
"Godot offers many ways to avoid global state thanks to the node tree and "
"signals."
msgstr ""

#: ../../docs/tutorials/best_practices/autoloads_versus_internal_nodes.rst:21
msgid ""
"For example, let's say we are building a platformer and want to collect "
"coins that play a sound effect. There's a node for that: the :ref:"
"`AudioStreamPlayer <class_AudioStreamPlayer>`. But if we call the "
"``AudioStreamPlayer`` while it is already playing a sound, the new sound "
"interrupts the first."
msgstr ""

#: ../../docs/tutorials/best_practices/autoloads_versus_internal_nodes.rst:26
msgid ""
"A solution is to code a global, autoloaded sound manager class. It generates "
"a pool of ``AudioStreamPlayer`` nodes that cycle through as each new request "
"for sound effects comes in. Say we call that class ``Sound``, you can use it "
"from anywhere in your project by calling ``Sound.play(\"coin_pickup."
"ogg\")``. This solves the problem in the short term but causes more problems:"
msgstr ""

#: ../../docs/tutorials/best_practices/autoloads_versus_internal_nodes.rst:32
msgid ""
"**Global state**: one object is now responsible for all objects' data. If "
"the ``Sound`` class has errors or doesn't have an AudioStreamPlayer "
"available, all the nodes calling it can break."
msgstr ""

#: ../../docs/tutorials/best_practices/autoloads_versus_internal_nodes.rst:36
msgid ""
"**Global access**: now that any object can call ``Sound.play(sound_path)`` "
"from anywhere, there's no longer an easy way to find the source of a bug."
msgstr ""

#: ../../docs/tutorials/best_practices/autoloads_versus_internal_nodes.rst:39
msgid ""
"**Global resource allocation**: with a pool of ``AudioStreamPlayer`` nodes "
"stored from the start, you can either have too few and face bugs, or too "
"many and use more memory than you need."
msgstr ""

#: ../../docs/tutorials/best_practices/autoloads_versus_internal_nodes.rst:45
msgid ""
"About global access, the problem is that any code anywhere could pass wrong "
"data to the ``Sound`` autoload in our example. As a result, the domain to "
"explore to fix the bug spans the entire project."
msgstr ""

#: ../../docs/tutorials/best_practices/autoloads_versus_internal_nodes.rst:49
msgid ""
"When you keep code inside a scene, only one or two scripts may be involved "
"in audio."
msgstr ""

#: ../../docs/tutorials/best_practices/autoloads_versus_internal_nodes.rst:52
msgid ""
"Contrast this with each scene keeping as many ``AudioStreamPlayer`` nodes as "
"it needs within itself and all these problems go away:"
msgstr ""

#: ../../docs/tutorials/best_practices/autoloads_versus_internal_nodes.rst:55
msgid ""
"Each scene manages its own state information. If there is a problem with the "
"data, it will only cause issues in that one scene."
msgstr ""

#: ../../docs/tutorials/best_practices/autoloads_versus_internal_nodes.rst:58
msgid ""
"Each scene accesses only its own nodes. Now, if there is a bug, it's easy to "
"find which node is at fault."
msgstr ""

#: ../../docs/tutorials/best_practices/autoloads_versus_internal_nodes.rst:61
msgid "Each scene allocates exactly the amount of resources it needs."
msgstr ""

#: ../../docs/tutorials/best_practices/autoloads_versus_internal_nodes.rst:64
msgid "Managing shared functionality or data"
msgstr ""

#: ../../docs/tutorials/best_practices/autoloads_versus_internal_nodes.rst:66
msgid ""
"Another reason to use an Autoload can be that you want to reuse the same "
"method or data across many scenes."
msgstr ""

#: ../../docs/tutorials/best_practices/autoloads_versus_internal_nodes.rst:69
msgid ""
"In the case of functions, you can create a new type of ``Node`` that "
"provides that feature for an individual scene using the :ref:`class_name "
"<doc_gdscript_basics_class_name>` keyword in GDScript."
msgstr ""

#: ../../docs/tutorials/best_practices/autoloads_versus_internal_nodes.rst:73
msgid "When it comes to data, you can either:"
msgstr ""

#: ../../docs/tutorials/best_practices/autoloads_versus_internal_nodes.rst:75
msgid ""
"Create a new type of :ref:`Resource <class_Resource>` to share the data."
msgstr ""

#: ../../docs/tutorials/best_practices/autoloads_versus_internal_nodes.rst:77
msgid ""
"Store the data in an object to which each node has access, for example using "
"the ``owner`` property to access the scene's root node."
msgstr ""

#: ../../docs/tutorials/best_practices/autoloads_versus_internal_nodes.rst:81
msgid "When you should use an Autoload"
msgstr ""

#: ../../docs/tutorials/best_practices/autoloads_versus_internal_nodes.rst:83
msgid ""
"GDScript supports the creation of ``static`` functions using ``static "
"func``. When combined with ``class_name``, this makes it possible to create "
"libraries of helper functions without having to create an instance to call "
"them. The limitation of static functions is that they can't reference member "
"variables, non-static functions or ``self``."
msgstr ""

#: ../../docs/tutorials/best_practices/autoloads_versus_internal_nodes.rst:89
msgid ""
"Since Godot 4.1, GDScript also supports ``static`` variables using ``static "
"var``. This means you can now share a variables across instances of a class "
"without having to create a separate autoload."
msgstr ""

#: ../../docs/tutorials/best_practices/autoloads_versus_internal_nodes.rst:93
msgid ""
"Still, autoloaded nodes can simplify your code for systems with a wide "
"scope. If the autoload is managing its own information and not invading the "
"data of other objects, then it's a great way to create systems that handle "
"broad-scoped tasks. For example, a quest or a dialogue system."
msgstr ""

#: ../../docs/tutorials/best_practices/autoloads_versus_internal_nodes.rst:100
msgid ""
"An autoload is *not* necessarily a singleton. Nothing prevents you from "
"instantiating copies of an autoloaded node. An autoload is only a tool that "
"makes a node load automatically as a child of the root of your scene tree, "
"regardless of your game's node structure or which scene you run, e.g. by "
"pressing the :kbd:`F6` key."
msgstr ""

#: ../../docs/tutorials/best_practices/autoloads_versus_internal_nodes.rst:106
msgid ""
"As a result, you can get the autoloaded node, for example an autoload called "
"``Sound``, by calling ``get_node(\"/root/Sound\")``."
msgstr ""

#: ../../docs/tutorials/best_practices/node_alternatives.rst:4
msgid "When and how to avoid using nodes for everything"
msgstr ""

#: ../../docs/tutorials/best_practices/node_alternatives.rst:6
msgid ""
"Nodes are cheap to produce, but even they have their limits. A project may "
"have tens of thousands of nodes all doing things. The more complex their "
"behavior though, the larger the strain each one adds to a project's "
"performance."
msgstr ""

#: ../../docs/tutorials/best_practices/node_alternatives.rst:11
msgid ""
"Godot provides more lightweight objects for creating APIs which nodes use. "
"Be sure to keep these in mind as options when designing how you wish to "
"build your project's features."
msgstr ""

#: ../../docs/tutorials/best_practices/node_alternatives.rst:15
msgid ""
":ref:`Object <class_Object>`: The ultimate lightweight object, the original "
"Object must use manual memory management. With that said, it isn't too "
"difficult to create one's own custom data structures, even node structures, "
"that are also lighter than the :ref:`Node <class_Node>` class."
msgstr ""

#: ../../docs/tutorials/best_practices/node_alternatives.rst:20
msgid ""
"**Example:** See the :ref:`Tree <class_Tree>` node. It supports a high level "
"of customization for a table of content with an arbitrary number of rows and "
"columns. The data that it uses to generate its visualization though is "
"actually a tree of :ref:`TreeItem <class_TreeItem>` Objects."
msgstr ""

#: ../../docs/tutorials/best_practices/node_alternatives.rst:25
msgid ""
"**Advantages:** Simplifying one's API to smaller scoped objects helps "
"improve its accessibility and improve iteration time. Rather than working "
"with the entire Node library, one creates an abbreviated set of Objects from "
"which a node can generate and manage the appropriate sub-nodes."
msgstr ""

#: ../../docs/tutorials/best_practices/node_alternatives.rst:32
msgid ""
"One should be careful when handling them. One can store an Object into a "
"variable, but these references can become invalid without warning. For "
"example, if the object's creator decides to delete it out of nowhere, this "
"would trigger an error state when one next accesses it."
msgstr ""

#: ../../docs/tutorials/best_practices/node_alternatives.rst:37
msgid ""
":ref:`RefCounted <class_RefCounted>`: Only a little more complex than "
"Object. They track references to themselves, only deleting loaded memory "
"when no further references to themselves exist. These are useful in the "
"majority of cases where one needs data in a custom class."
msgstr ""

#: ../../docs/tutorials/best_practices/node_alternatives.rst:42
msgid ""
"**Example:** See the :ref:`FileAccess <class_FileAccess>` object. It "
"functions just like a regular Object except that one need not delete it "
"themselves."
msgstr ""

#: ../../docs/tutorials/best_practices/node_alternatives.rst:45
msgid "**Advantages:** same as the Object."
msgstr ""

#: ../../docs/tutorials/best_practices/node_alternatives.rst:47
msgid ""
":ref:`Resource <class_Resource>`: Only slightly more complex than "
"RefCounted. They have the innate ability to serialize/deserialize (i.e. save "
"and load) their object properties to/from Godot resource files."
msgstr ""

#: ../../docs/tutorials/best_practices/node_alternatives.rst:51
msgid ""
"**Example:** Scripts, PackedScene (for scene files), and other types like "
"each of the :ref:`AudioEffect <class_AudioEffect>` classes. Each of these "
"can be saved and loaded, therefore they extend from Resource."
msgstr ""

#: ../../docs/tutorials/best_practices/node_alternatives.rst:55
msgid ""
"**Advantages:** Much has :ref:`already been said <doc_resources>` on :ref:"
"`Resource <class_Resource>`'s advantages over traditional data storage "
"methods. In the context of using Resources over Nodes though, their main "
"advantage is in Inspector-compatibility. While nearly as lightweight as "
"Object/RefCounted, they can still display and export properties in the "
"Inspector. This allows them to fulfill a purpose much like sub-Nodes on the "
"usability front, but also improve performance if one plans to have many such "
"Resources/Nodes in their scenes."
msgstr ""

#: ../../docs/tutorials/best_practices/godot_interfaces.rst:4
msgid "Godot interfaces"
msgstr ""

#: ../../docs/tutorials/best_practices/godot_interfaces.rst:6
msgid ""
"Often one needs scripts that rely on other objects for features. There are 2 "
"parts to this process:"
msgstr ""

#: ../../docs/tutorials/best_practices/godot_interfaces.rst:9
msgid "Acquiring a reference to the object that presumably has the features."
msgstr ""

#: ../../docs/tutorials/best_practices/godot_interfaces.rst:11
msgid "Accessing the data or logic from the object."
msgstr ""

#: ../../docs/tutorials/best_practices/godot_interfaces.rst:13
msgid "The rest of this tutorial outlines the various ways of doing all this."
msgstr ""

#: ../../docs/tutorials/best_practices/godot_interfaces.rst:16
msgid "Acquiring object references"
msgstr ""

#: ../../docs/tutorials/best_practices/godot_interfaces.rst:18
msgid ""
"For all :ref:`Object <class_Object>`\\s, the most basic way of referencing "
"them is to get a reference to an existing object from another acquired "
"instance."
msgstr ""

#: ../../docs/tutorials/best_practices/godot_interfaces.rst:32
msgid ""
"The same principle applies for :ref:`RefCounted <class_RefCounted>` objects. "
"While users often access :ref:`Node <class_Node>` and :ref:`Resource "
"<class_Resource>` this way, alternative measures are available."
msgstr ""

#: ../../docs/tutorials/best_practices/godot_interfaces.rst:36
msgid ""
"Instead of property or method access, one can get Resources by load access."
msgstr ""

#: ../../docs/tutorials/best_practices/godot_interfaces.rst:121
msgid "Note the following:"
msgstr ""

#: ../../docs/tutorials/best_practices/godot_interfaces.rst:123
msgid "There are many ways in which a language can load such resources."
msgstr ""

#: ../../docs/tutorials/best_practices/godot_interfaces.rst:125
msgid ""
"When designing how objects will access data, don't forget that one can pass "
"resources around as references as well."
msgstr ""

#: ../../docs/tutorials/best_practices/godot_interfaces.rst:128
msgid ""
"Keep in mind that loading a resource fetches the cached resource instance "
"maintained by the engine. To get a new object, one must :ref:`duplicate "
"<class_Resource_method_duplicate>` an existing reference or instantiate one "
"from scratch with ``new()``."
msgstr ""

#: ../../docs/tutorials/best_practices/godot_interfaces.rst:133
msgid "Nodes likewise have an alternative access point: the SceneTree."
msgstr ""

#: ../../docs/tutorials/best_practices/godot_interfaces.rst:267
msgid "Accessing data or logic from an object"
msgstr ""

#: ../../docs/tutorials/best_practices/godot_interfaces.rst:269
msgid ""
"Godot's scripting API is duck-typed. This means that if a script executes an "
"operation, Godot doesn't validate that it supports the operation by "
"**type**. It instead checks that the object **implements** the individual "
"method."
msgstr ""

#: ../../docs/tutorials/best_practices/godot_interfaces.rst:273
msgid ""
"For example, the :ref:`CanvasItem <class_CanvasItem>` class has a "
"``visible`` property. All properties exposed to the scripting API are in "
"fact a setter and getter pair bound to a name. If one tried to access :ref:"
"`CanvasItem.visible <class_CanvasItem_property_visible>`, then Godot would "
"do the following checks, in order:"
msgstr ""

#: ../../docs/tutorials/best_practices/godot_interfaces.rst:279
msgid ""
"If the object has a script attached, it will attempt to set the property "
"through the script. This leaves open the opportunity for scripts to override "
"a property defined on a base object by overriding the setter method for the "
"property."
msgstr ""

#: ../../docs/tutorials/best_practices/godot_interfaces.rst:284
msgid ""
"If the script does not have the property, it performs a HashMap lookup in "
"the ClassDB for the \"visible\" property against the CanvasItem class and "
"all of its inherited types. If found, it will call the bound setter or "
"getter. For more information about HashMaps, see the :ref:`data preferences "
"<doc_data_preferences>` docs."
msgstr ""

#: ../../docs/tutorials/best_practices/godot_interfaces.rst:290
msgid ""
"If not found, it does an explicit check to see if the user wants to access "
"the \"script\" or \"meta\" properties."
msgstr ""

#: ../../docs/tutorials/best_practices/godot_interfaces.rst:293
msgid ""
"If not, it checks for a ``_set``/``_get`` implementation (depending on type "
"of access) in the CanvasItem and its inherited types. These methods can "
"execute logic that gives the impression that the Object has a property. This "
"is also the case with the ``_get_property_list`` method."
msgstr ""

#: ../../docs/tutorials/best_practices/godot_interfaces.rst:298
msgid ""
"Note that this happens even for non-legal symbol names, such as names "
"starting with a digit or containing a slash."
msgstr ""

#: ../../docs/tutorials/best_practices/godot_interfaces.rst:301
msgid ""
"As a result, this duck-typed system can locate a property either in the "
"script, the object's class, or any class that object inherits, but only for "
"things which extend Object."
msgstr ""

#: ../../docs/tutorials/best_practices/godot_interfaces.rst:305
msgid ""
"Godot provides a variety of options for performing runtime checks on these "
"accesses:"
msgstr ""

#: ../../docs/tutorials/best_practices/godot_interfaces.rst:308
msgid ""
"A duck-typed property access. These will be property checks (as described "
"above). If the operation isn't supported by the object, execution will halt."
msgstr ""

#: ../../docs/tutorials/best_practices/godot_interfaces.rst:336
msgid ""
"A method check. In the case of :ref:`CanvasItem.visible "
"<class_CanvasItem_property_visible>`, one can access the methods, "
"``set_visible`` and ``is_visible`` like any other method."
msgstr ""

#: ../../docs/tutorials/best_practices/godot_interfaces.rst:474
msgid ""
"Outsource the access to a :ref:`Callable <class_Callable>`. These may be "
"useful in cases where one needs the max level of freedom from dependencies. "
"In this case, one relies on an external context to setup the method."
msgstr ""

#: ../../docs/tutorials/best_practices/godot_interfaces.rst:536
msgid ""
"These strategies contribute to Godot's flexible design. Between them, users "
"have a breadth of tools to meet their specific needs."
msgstr ""

#: ../../docs/tutorials/best_practices/godot_notifications.rst:4
msgid "Godot notifications"
msgstr ""

#: ../../docs/tutorials/best_practices/godot_notifications.rst:6
msgid ""
"Every Object in Godot implements a :ref:`_notification "
"<class_Object_private_method__notification>` method. Its purpose is to allow "
"the Object to respond to a variety of engine-level callbacks that may relate "
"to it. For example, if the engine tells a :ref:`CanvasItem "
"<class_CanvasItem>` to \"draw\", it will call "
"``_notification(NOTIFICATION_DRAW)``."
msgstr ""

#: ../../docs/tutorials/best_practices/godot_notifications.rst:13
msgid ""
"Some of these notifications, like draw, are useful to override in scripts. "
"So much so that Godot exposes many of them with dedicated functions:"
msgstr ""

#: ../../docs/tutorials/best_practices/godot_notifications.rst:16
msgid "``_ready()``: ``NOTIFICATION_READY``"
msgstr ""

#: ../../docs/tutorials/best_practices/godot_notifications.rst:18
msgid "``_enter_tree()``: ``NOTIFICATION_ENTER_TREE``"
msgstr ""

#: ../../docs/tutorials/best_practices/godot_notifications.rst:20
msgid "``_exit_tree()``: ``NOTIFICATION_EXIT_TREE``"
msgstr ""

#: ../../docs/tutorials/best_practices/godot_notifications.rst:22
msgid "``_process(delta)``: ``NOTIFICATION_PROCESS``"
msgstr ""

#: ../../docs/tutorials/best_practices/godot_notifications.rst:24
msgid "``_physics_process(delta)``: ``NOTIFICATION_PHYSICS_PROCESS``"
msgstr ""

#: ../../docs/tutorials/best_practices/godot_notifications.rst:26
msgid "``_draw()``: ``NOTIFICATION_DRAW``"
msgstr ""

#: ../../docs/tutorials/best_practices/godot_notifications.rst:28
msgid ""
"What users might *not* realize is that notifications exist for types other "
"than Node alone, for example:"
msgstr ""

#: ../../docs/tutorials/best_practices/godot_notifications.rst:31
msgid ""
":ref:`Object::NOTIFICATION_POSTINITIALIZE "
"<class_Object_constant_NOTIFICATION_POSTINITIALIZE>`: a callback that "
"triggers during object initialization. Not accessible to scripts."
msgstr ""

#: ../../docs/tutorials/best_practices/godot_notifications.rst:34
msgid ""
":ref:`Object::NOTIFICATION_PREDELETE "
"<class_Object_constant_NOTIFICATION_PREDELETE>`: a callback that triggers "
"before the engine deletes an Object, i.e. a \"destructor\"."
msgstr ""

#: ../../docs/tutorials/best_practices/godot_notifications.rst:38
msgid ""
"And many of the callbacks that *do* exist in Nodes don't have any dedicated "
"methods, but are still quite useful."
msgstr ""

#: ../../docs/tutorials/best_practices/godot_notifications.rst:41
msgid ""
":ref:`Node::NOTIFICATION_PARENTED "
"<class_Node_constant_NOTIFICATION_PARENTED>`: a callback that triggers "
"anytime one adds a child node to another node."
msgstr ""

#: ../../docs/tutorials/best_practices/godot_notifications.rst:44
msgid ""
":ref:`Node::NOTIFICATION_UNPARENTED "
"<class_Node_constant_NOTIFICATION_UNPARENTED>`: a callback that triggers "
"anytime one removes a child node from another node."
msgstr ""

#: ../../docs/tutorials/best_practices/godot_notifications.rst:48
msgid ""
"One can access all these custom notifications from the universal "
"``_notification()`` method."
msgstr ""

#: ../../docs/tutorials/best_practices/godot_notifications.rst:52
msgid ""
"Methods in the documentation labeled as \"virtual\" are also intended to be "
"overridden by scripts."
msgstr ""

#: ../../docs/tutorials/best_practices/godot_notifications.rst:55
msgid ""
"A classic example is the :ref:`_init <class_Object_private_method__init>` "
"method in Object. While it has no ``NOTIFICATION_*`` equivalent, the engine "
"still calls the method. Most languages (except C#) rely on it as a "
"constructor."
msgstr ""

#: ../../docs/tutorials/best_practices/godot_notifications.rst:60
msgid ""
"So, in which situation should one use each of these notifications or virtual "
"functions?"
msgstr ""

#: ../../docs/tutorials/best_practices/godot_notifications.rst:64
msgid "_process vs. _physics_process vs. \\*_input"
msgstr ""

#: ../../docs/tutorials/best_practices/godot_notifications.rst:66
msgid ""
"Use ``_process()`` when one needs a framerate-dependent delta time between "
"frames. If code that updates object data needs to update as often as "
"possible, this is the right place. Recurring logic checks and data caching "
"often execute here, but it comes down to the frequency at which one needs "
"the evaluations to update. If they don't need to execute every frame, then "
"implementing a Timer-timeout loop is another option."
msgstr ""

#: ../../docs/tutorials/best_practices/godot_notifications.rst:105
msgid ""
"Use ``_physics_process()`` when one needs a framerate-independent delta time "
"between frames. If code needs consistent updates over time, regardless of "
"how fast or slow time advances, this is the right place. Recurring kinematic "
"and object transform operations should execute here."
msgstr ""

#: ../../docs/tutorials/best_practices/godot_notifications.rst:110
msgid ""
"While it is possible, to achieve the best performance, one should avoid "
"making input checks during these callbacks. ``_process()`` and "
"``_physics_process()`` will trigger at every opportunity (they do not "
"\"rest\" by default). In contrast, ``*_input()`` callbacks will trigger only "
"on frames in which the engine has actually detected the input."
msgstr ""

#: ../../docs/tutorials/best_practices/godot_notifications.rst:116
msgid ""
"One can check for input actions within the input callbacks just the same. If "
"one wants to use delta time, one can fetch it from the related delta time "
"methods as needed."
msgstr ""

#: ../../docs/tutorials/best_practices/godot_notifications.rst:164
msgid "_init vs. initialization vs. export"
msgstr ""

#: ../../docs/tutorials/best_practices/godot_notifications.rst:166
msgid ""
"If the script initializes its own node subtree, without a scene, that code "
"should execute in ``_init()``. Other property or SceneTree-independent "
"initializations should also run here."
msgstr ""

#: ../../docs/tutorials/best_practices/godot_notifications.rst:171
msgid "The C# equivalent to GDScript's ``_init()`` method is the constructor."
msgstr ""

#: ../../docs/tutorials/best_practices/godot_notifications.rst:173
msgid ""
"``_init()`` triggers before ``_enter_tree()`` or ``_ready()``, but after a "
"script creates and initializes its properties. When instantiating a scene, "
"property values will set up according to the following sequence:"
msgstr ""

#: ../../docs/tutorials/best_practices/godot_notifications.rst:177
msgid ""
"**Initial value assignment:** the property is assigned its initialization "
"value, or its default value if one is not specified. If a setter exists, it "
"is not used."
msgstr ""

#: ../../docs/tutorials/best_practices/godot_notifications.rst:180
msgid ""
"**``_init()`` assignment:** the property's value is replaced by any "
"assignments made in ``_init()``, triggering the setter."
msgstr ""

#: ../../docs/tutorials/best_practices/godot_notifications.rst:183
msgid ""
"**Exported value assignment:** an exported property's value is again "
"replaced by any value set in the Inspector, triggering the setter."
msgstr ""

#: ../../docs/tutorials/best_practices/godot_notifications.rst:226
msgid ""
"As a result, instantiating a script versus a scene may affect both the "
"initialization *and* the number of times the engine calls the setter."
msgstr ""

#: ../../docs/tutorials/best_practices/godot_notifications.rst:230
msgid "_ready vs. _enter_tree vs. NOTIFICATION_PARENTED"
msgstr ""

#: ../../docs/tutorials/best_practices/godot_notifications.rst:232
msgid ""
"When instantiating a scene connected to the first executed scene, Godot will "
"instantiate nodes down the tree (making ``_init()`` calls) and build the "
"tree going downwards from the root. This causes ``_enter_tree()`` calls to "
"cascade down the tree. Once the tree is complete, leaf nodes call "
"``_ready``. A node will call this method once all child nodes have finished "
"calling theirs. This then causes a reverse cascade going up back to the "
"tree's root."
msgstr ""

#: ../../docs/tutorials/best_practices/godot_notifications.rst:239
msgid ""
"When instantiating a script or a standalone scene, nodes are not added to "
"the SceneTree upon creation, so no ``_enter_tree()`` callbacks trigger. "
"Instead, only the ``_init()`` call occurs. When the scene is added to the "
"SceneTree, the ``_enter_tree()`` and ``_ready()`` calls occur."
msgstr ""

#: ../../docs/tutorials/best_practices/godot_notifications.rst:244
msgid ""
"If one needs to trigger behavior that occurs as nodes parent to another, "
"regardless of whether it occurs as part of the main/active scene or not, one "
"can use the :ref:`PARENTED <class_Node_constant_NOTIFICATION_PARENTED>` "
"notification. For example, here is a snippet that connects a node's method "
"to a custom signal on the parent node without failing. Useful on data-"
"centric nodes that one might create at runtime."
msgstr ""

#: ../../docs/tutorials/best_practices/data_preferences.rst:6
msgid "Data preferences"
msgstr ""

#: ../../docs/tutorials/best_practices/data_preferences.rst:8
msgid ""
"Ever wondered whether one should approach problem X with data structure Y or "
"Z? This article covers a variety of topics related to these dilemmas."
msgstr ""

#: ../../docs/tutorials/best_practices/data_preferences.rst:13
msgid ""
"This article makes references to \"[something]-time\" operations. This "
"terminology comes from algorithm analysis' `Big O Notation <https://rob-bell."
"net/2009/06/a-beginners-guide-to-big-o-notation/>`_."
msgstr ""

#: ../../docs/tutorials/best_practices/data_preferences.rst:17
msgid ""
"Long-story short, it describes the worst-case scenario of runtime length. In "
"laymen's terms:"
msgstr ""

#: ../../docs/tutorials/best_practices/data_preferences.rst:20
msgid ""
"\"As the size of a problem domain increases, the runtime length of the "
"algorithm...\""
msgstr ""

#: ../../docs/tutorials/best_practices/data_preferences.rst:23
msgid "Constant-time, ``O(1)``: \"...does not increase.\""
msgstr ""

#: ../../docs/tutorials/best_practices/data_preferences.rst:24
msgid "Logarithmic-time, ``O(log n)``: \"...increases at a slow rate.\""
msgstr ""

#: ../../docs/tutorials/best_practices/data_preferences.rst:25
msgid "Linear-time, ``O(n)``: \"...increases at the same rate.\""
msgstr ""

#: ../../docs/tutorials/best_practices/data_preferences.rst:26
msgid "Etc."
msgstr ""

#: ../../docs/tutorials/best_practices/data_preferences.rst:28
msgid ""
"Imagine if one had to process 3 million data points within a single frame. "
"It would be impossible to craft the feature with a linear-time algorithm "
"since the sheer size of the data would increase the runtime far beyond the "
"time allotted. In comparison, using a constant-time algorithm could handle "
"the operation without issue."
msgstr ""

#: ../../docs/tutorials/best_practices/data_preferences.rst:34
msgid ""
"By and large, developers want to avoid engaging in linear-time operations as "
"much as possible. But, if one keeps the scale of a linear-time operation "
"small, and if one does not need to perform the operation often, then it may "
"be acceptable. Balancing these requirements and choosing the right "
"algorithm / data structure for the job is part of what makes programmers' "
"skills valuable."
msgstr ""

#: ../../docs/tutorials/best_practices/data_preferences.rst:42
msgid "Array vs. Dictionary vs. Object"
msgstr ""

#: ../../docs/tutorials/best_practices/data_preferences.rst:44
msgid ""
"Godot stores all variables in the scripting API in the :ref:`Variant "
"<doc_variant_class>` class. Variants can store Variant-compatible data "
"structures such as :ref:`Array <class_Array>` and :ref:`Dictionary "
"<class_Dictionary>` as well as :ref:`Objects <class_Object>`."
msgstr ""

#: ../../docs/tutorials/best_practices/data_preferences.rst:50
msgid ""
"Godot implements Array as a ``Vector<Variant>``. The engine stores the Array "
"contents in a contiguous section of memory, i.e. they are in a row adjacent "
"to each other."
msgstr ""

#: ../../docs/tutorials/best_practices/data_preferences.rst:56
msgid ""
"For those unfamiliar with C++, a Vector is the name of the array object in "
"traditional C++ libraries. It is a \"templated\" type, meaning that its "
"records can only contain a particular type (denoted by angled brackets). So, "
"for example, a :ref:`PackedStringArray <class_PackedStringArray>` would be "
"something like a ``Vector<String>``."
msgstr ""

#: ../../docs/tutorials/best_practices/data_preferences.rst:63
msgid "Contiguous memory stores imply the following operation performance:"
msgstr ""

#: ../../docs/tutorials/best_practices/data_preferences.rst:65
msgid "**Iterate:** Fastest. Great for loops."
msgstr ""

#: ../../docs/tutorials/best_practices/data_preferences.rst:67
msgid "Op: All it does is increment a counter to get to the next record."
msgstr ""

#: ../../docs/tutorials/best_practices/data_preferences.rst:69
msgid "**Insert, Erase, Move:** Position-dependent. Generally slow."
msgstr ""

#: ../../docs/tutorials/best_practices/data_preferences.rst:71
msgid ""
"Op: Adding/removing/moving content involves moving the adjacent records over "
"(to make room / fill space)."
msgstr ""

#: ../../docs/tutorials/best_practices/data_preferences.rst:74
msgid "Fast add/remove *from the end*."
msgstr ""

#: ../../docs/tutorials/best_practices/data_preferences.rst:76
msgid "Slow add/remove *from an arbitrary position*."
msgstr ""

#: ../../docs/tutorials/best_practices/data_preferences.rst:78
msgid "Slowest add/remove *from the front*."
msgstr ""

#: ../../docs/tutorials/best_practices/data_preferences.rst:80
msgid "If doing many inserts/removals *from the front*, then..."
msgstr ""

#: ../../docs/tutorials/best_practices/data_preferences.rst:82
msgid "invert the array."
msgstr ""

#: ../../docs/tutorials/best_practices/data_preferences.rst:84
msgid "do a loop which executes the Array changes *at the end*."
msgstr ""

#: ../../docs/tutorials/best_practices/data_preferences.rst:86
msgid "re-invert the array."
msgstr ""

#: ../../docs/tutorials/best_practices/data_preferences.rst:88
msgid ""
"This makes only 2 copies of the array (still constant time, but slow) versus "
"copying roughly 1/2 of the array, on average, N times (linear time)."
msgstr ""

#: ../../docs/tutorials/best_practices/data_preferences.rst:91
msgid ""
"**Get, Set:** Fastest *by position*. E.g. can request 0th, 2nd, 10th record, "
"etc. but cannot specify which record you want."
msgstr ""

#: ../../docs/tutorials/best_practices/data_preferences.rst:94
msgid "Op: 1 addition operation from array start position up to desired index."
msgstr ""

#: ../../docs/tutorials/best_practices/data_preferences.rst:96
msgid "**Find:** Slowest. Identifies the index/position of a value."
msgstr ""

#: ../../docs/tutorials/best_practices/data_preferences.rst:98
msgid ""
"Op: Must iterate through array and compare values until one finds a match."
msgstr ""

#: ../../docs/tutorials/best_practices/data_preferences.rst:100
msgid ""
"Performance is also dependent on whether one needs an exhaustive search."
msgstr ""

#: ../../docs/tutorials/best_practices/data_preferences.rst:103
msgid ""
"If kept ordered, custom search operations can bring it to logarithmic time "
"(relatively fast). Laymen users won't be comfortable with this though. Done "
"by re-sorting the Array after every edit and writing an ordered-aware search "
"algorithm."
msgstr ""

#: ../../docs/tutorials/best_practices/data_preferences.rst:108
msgid ""
"Godot implements Dictionary as an ``OrderedHashMap<Variant, Variant>``. The "
"engine stores a small array (initialized to 2^3 or 8 records) of key-value "
"pairs. When one attempts to access a value, they provide it a key. It then "
"*hashes* the key, i.e. converts it into a number. The \"hash\" is used to "
"calculate the index into the array. As an array, the OHM then has a quick "
"lookup within the \"table\" of keys mapped to values. When the HashMap "
"becomes too full, it increases to the next power of 2 (so, 16 records, then "
"32, etc.) and rebuilds the structure."
msgstr ""

#: ../../docs/tutorials/best_practices/data_preferences.rst:116
msgid ""
"Hashes are to reduce the chance of a key collision. If one occurs, the table "
"must recalculate another index for the value that takes the previous "
"position into account. In all, this results in constant-time access to all "
"records at the expense of memory and some minor operational efficiency."
msgstr ""

#: ../../docs/tutorials/best_practices/data_preferences.rst:121
msgid "Hashing every key an arbitrary number of times."
msgstr ""

#: ../../docs/tutorials/best_practices/data_preferences.rst:123
msgid ""
"Hash operations are constant-time, so even if an algorithm must do more than "
"one, as long as the number of hash calculations doesn't become too dependent "
"on the density of the table, things will stay fast. Which leads to..."
msgstr ""

#: ../../docs/tutorials/best_practices/data_preferences.rst:128
msgid "Maintaining an ever-growing size for the table."
msgstr ""

#: ../../docs/tutorials/best_practices/data_preferences.rst:130
msgid ""
"HashMaps maintain gaps of unused memory interspersed in the table on purpose "
"to reduce hash collisions and maintain the speed of accesses. This is why it "
"constantly increases in size quadratically by powers of 2."
msgstr ""

#: ../../docs/tutorials/best_practices/data_preferences.rst:135
msgid ""
"As one might be able to tell, Dictionaries specialize in tasks that Arrays "
"do not. An overview of their operational details is as follows:"
msgstr ""

#: ../../docs/tutorials/best_practices/data_preferences.rst:138
msgid "**Iterate:** Fast."
msgstr ""

#: ../../docs/tutorials/best_practices/data_preferences.rst:140
msgid ""
"Op: Iterate over the map's internal vector of hashes. Return each key. "
"Afterwards, users then use the key to jump to and return the desired value."
msgstr ""

#: ../../docs/tutorials/best_practices/data_preferences.rst:144
msgid "**Insert, Erase, Move:** Fastest."
msgstr ""

#: ../../docs/tutorials/best_practices/data_preferences.rst:146
msgid ""
"Op: Hash the given key. Do 1 addition operation to look up the appropriate "
"value (array start + offset). Move is two of these (one insert, one erase). "
"The map must do some maintenance to preserve its capabilities:"
msgstr ""

#: ../../docs/tutorials/best_practices/data_preferences.rst:151
msgid "update ordered List of records."
msgstr ""

#: ../../docs/tutorials/best_practices/data_preferences.rst:153
msgid "determine if table density mandates a need to expand table capacity."
msgstr ""

#: ../../docs/tutorials/best_practices/data_preferences.rst:155
msgid ""
"The Dictionary remembers in what order users inserted its keys. This enables "
"it to execute reliable iterations."
msgstr ""

#: ../../docs/tutorials/best_practices/data_preferences.rst:158
msgid "**Get, Set:** Fastest. Same as a lookup *by key*."
msgstr ""

#: ../../docs/tutorials/best_practices/data_preferences.rst:160
msgid "Op: Same as insert/erase/move."
msgstr ""

#: ../../docs/tutorials/best_practices/data_preferences.rst:162
msgid "**Find:** Slowest. Identifies the key of a value."
msgstr ""

#: ../../docs/tutorials/best_practices/data_preferences.rst:164
msgid ""
"Op: Must iterate through records and compare the value until a match is "
"found."
msgstr ""

#: ../../docs/tutorials/best_practices/data_preferences.rst:167
msgid ""
"Note that Godot does not provide this feature out-of-the-box (because they "
"aren't meant for this task)."
msgstr ""

#: ../../docs/tutorials/best_practices/data_preferences.rst:170
msgid ""
"Godot implements Objects as stupid, but dynamic containers of data content. "
"Objects query data sources when posed questions. For example, to answer the "
"question, \"do you have a property called, 'position'?\", it might ask its :"
"ref:`script <class_Script>` or the :ref:`ClassDB <class_ClassDB>`. One can "
"find more information about what objects are and how they work in the :ref:"
"`doc_what_are_godot_classes` article."
msgstr ""

#: ../../docs/tutorials/best_practices/data_preferences.rst:177
msgid ""
"The important detail here is the complexity of the Object's task. Every time "
"it performs one of these multi-source queries, it runs through *several* "
"iteration loops and HashMap lookups. What's more, the queries are linear-"
"time operations dependent on the Object's inheritance hierarchy size. If the "
"class the Object queries (its current class) doesn't find anything, the "
"request defers to the next base class, all the way up until the original "
"Object class. While these are each fast operations in isolation, the fact "
"that it must make so many checks is what makes them slower than both of the "
"alternatives for looking up data."
msgstr ""

#: ../../docs/tutorials/best_practices/data_preferences.rst:189
msgid ""
"When developers mention how slow the scripting API is, it is this chain of "
"queries they refer to. Compared to compiled C++ code where the application "
"knows exactly where to go to find anything, it is inevitable that scripting "
"API operations will take much longer. They must locate the source of any "
"relevant data before they can attempt to access it."
msgstr ""

#: ../../docs/tutorials/best_practices/data_preferences.rst:195
msgid ""
"The reason GDScript is slow is because every operation it performs passes "
"through this system."
msgstr ""

#: ../../docs/tutorials/best_practices/data_preferences.rst:198
msgid ""
"C# can process some content at higher speeds via more optimized bytecode. "
"But, if the C# script calls into an engine class' content or if the script "
"tries to access something external to it, it will go through this pipeline."
msgstr ""

#: ../../docs/tutorials/best_practices/data_preferences.rst:203
msgid ""
"NativeScript C++ goes even further and keeps everything internal by default. "
"Calls into external structures will go through the scripting API. In "
"NativeScript C++, registering methods to expose them to the scripting API is "
"a manual task. It is at this point that external, non-C++ classes will use "
"the API to locate them."
msgstr ""

#: ../../docs/tutorials/best_practices/data_preferences.rst:209
msgid ""
"So, assuming one extends from Reference to create a data structure, like an "
"Array or Dictionary, why choose an Object over the other two options?"
msgstr ""

#: ../../docs/tutorials/best_practices/data_preferences.rst:212
msgid ""
"**Control:** With objects comes the ability to create more sophisticated "
"structures. One can layer abstractions over the data to ensure the external "
"API doesn't change in response to internal data structure changes. What's "
"more, Objects can have signals, allowing for reactive behavior."
msgstr ""

#: ../../docs/tutorials/best_practices/data_preferences.rst:217
msgid ""
"**Clarity:** Objects are a reliable data source when it comes to the data "
"that scripts and engine classes define for them. Properties may not hold the "
"values one expects, but one doesn't need to worry about whether the property "
"exists in the first place."
msgstr ""

#: ../../docs/tutorials/best_practices/data_preferences.rst:222
msgid ""
"**Convenience:** If one already has a similar data structure in mind, then "
"extending from an existing class makes the task of building the data "
"structure much easier. In comparison, Arrays and Dictionaries don't fulfill "
"all use cases one might have."
msgstr ""

#: ../../docs/tutorials/best_practices/data_preferences.rst:227
msgid ""
"Objects also give users the opportunity to create even more specialized data "
"structures. With it, one can design their own List, Binary Search Tree, "
"Heap, Splay Tree, Graph, Disjoint Set, and any host of other options."
msgstr ""

#: ../../docs/tutorials/best_practices/data_preferences.rst:231
msgid ""
"\"Why not use Node for tree structures?\" one might ask. Well, the Node "
"class contains things that won't be relevant to one's custom data structure. "
"As such, it can be helpful to construct one's own node type when building "
"tree structures."
msgstr ""

#: ../../docs/tutorials/best_practices/data_preferences.rst:278
msgid ""
"From here, one can then create their own structures with specific features, "
"limited only by their imagination."
msgstr ""

#: ../../docs/tutorials/best_practices/data_preferences.rst:282
msgid "Enumerations: int vs. string"
msgstr ""

#: ../../docs/tutorials/best_practices/data_preferences.rst:284
msgid ""
"Most languages offer an enumeration type option. GDScript is no different, "
"but unlike most other languages, it allows one to use either integers or "
"strings for the enum values (the latter only when using the ``export`` "
"keyword in GDScript). The question then arises, \"which should one use?\""
msgstr ""

#: ../../docs/tutorials/best_practices/data_preferences.rst:289
msgid ""
"The short answer is, \"whichever you are more comfortable with.\" This is a "
"feature specific to GDScript and not Godot scripting in general; The "
"languages prioritizes usability over performance."
msgstr ""

#: ../../docs/tutorials/best_practices/data_preferences.rst:293
msgid ""
"On a technical level, integer comparisons (constant-time) will happen faster "
"than string comparisons (linear-time). If one wants to keep up other "
"languages' conventions though, then one should use integers."
msgstr ""

#: ../../docs/tutorials/best_practices/data_preferences.rst:297
msgid ""
"The primary issue with using integers comes up when one wants to *print* an "
"enum value. As integers, attempting to print ``MY_ENUM`` will print ``5`` or "
"what-have-you, rather than something like ``\"MyEnum\"``. To print an "
"integer enum, one would have to write a Dictionary that maps the "
"corresponding string value for each enum."
msgstr ""

#: ../../docs/tutorials/best_practices/data_preferences.rst:303
msgid ""
"If the primary purpose of using an enum is for printing values and one "
"wishes to group them together as related concepts, then it makes sense to "
"use them as strings. That way, a separate data structure to execute on the "
"printing is unnecessary."
msgstr ""

#: ../../docs/tutorials/best_practices/data_preferences.rst:309
msgid ""
"AnimatedTexture vs. AnimatedSprite2D vs. AnimationPlayer vs. AnimationTree"
msgstr ""

#: ../../docs/tutorials/best_practices/data_preferences.rst:311
msgid ""
"Under what circumstances should one use each of Godot's animation classes? "
"The answer may not be immediately clear to new Godot users."
msgstr ""

#: ../../docs/tutorials/best_practices/data_preferences.rst:314
msgid ""
":ref:`AnimatedTexture <class_AnimatedTexture>` is a texture that the engine "
"draws as an animated loop rather than a static image. Users can manipulate..."
msgstr ""

#: ../../docs/tutorials/best_practices/data_preferences.rst:318
msgid "the rate at which it moves across each section of the texture (FPS)."
msgstr ""

#: ../../docs/tutorials/best_practices/data_preferences.rst:320
msgid "the number of regions contained within the texture (frames)."
msgstr ""

#: ../../docs/tutorials/best_practices/data_preferences.rst:322
msgid ""
"Godot's :ref:`RenderingServer <class_RenderingServer>` then draws the "
"regions in sequence at the prescribed rate. The good news is that this "
"involves no extra logic on the part of the engine. The bad news is that "
"users have very little control."
msgstr ""

#: ../../docs/tutorials/best_practices/data_preferences.rst:327
msgid ""
"Also note that AnimatedTexture is a :ref:`Resource <class_Resource>` unlike "
"the other :ref:`Node <class_Node>` objects discussed here. One might create "
"a :ref:`Sprite2D <class_Sprite2D>` node that uses AnimatedTexture as its "
"texture. Or (something the others can't do) one could add AnimatedTextures "
"as tiles in a :ref:`TileSet <class_TileSet>` and integrate it with a :ref:"
"`TileMap <class_TileMap>` for many auto-animating backgrounds that all "
"render in a single batched draw call."
msgstr ""

#: ../../docs/tutorials/best_practices/data_preferences.rst:335
msgid ""
"The AnimatedSprite2D node, in combination with the :ref:`SpriteFrames "
"<class_SpriteFrames>` resource, allows one to create a variety of animation "
"sequences through spritesheets, flip between animations, and control their "
"speed, regional offset, and orientation. This makes them well-suited to "
"controlling 2D frame-based animations."
msgstr ""

#: ../../docs/tutorials/best_practices/data_preferences.rst:341
msgid ""
"If one needs trigger other effects in relation to animation changes (for "
"example, create particle effects, call functions, or manipulate other "
"peripheral elements besides the frame-based animation), then will need to "
"use an :ref:`AnimationPlayer <class_AnimationPlayer>` node in conjunction "
"with the AnimatedSprite2D."
msgstr ""

#: ../../docs/tutorials/best_practices/data_preferences.rst:347
msgid ""
"AnimationPlayers are also the tool one will need to use if they wish to "
"design more complex 2D animation systems, such as..."
msgstr ""

#: ../../docs/tutorials/best_practices/data_preferences.rst:350
msgid "**Cut-out animations:** editing sprites' transforms at runtime."
msgstr ""

#: ../../docs/tutorials/best_practices/data_preferences.rst:352
msgid ""
"**2D Mesh animations:** defining a region for the sprite's texture and "
"rigging a skeleton to it. Then one animates the bones which stretch and bend "
"the texture in proportion to the bones' relationships to each other."
msgstr ""

#: ../../docs/tutorials/best_practices/data_preferences.rst:357
msgid "A mix of the above."
msgstr ""

#: ../../docs/tutorials/best_practices/data_preferences.rst:359
msgid ""
"While one needs an AnimationPlayer to design each of the individual "
"animation sequences for a game, it can also be useful to combine animations "
"for blending, i.e. enabling smooth transitions between these animations. "
"There may also be a hierarchical structure between animations that one plans "
"out for their object. These are the cases where the :ref:`AnimationTree "
"<class_AnimationTree>` shines. One can find an in-depth guide on using the "
"AnimationTree :ref:`here <doc_animation_tree>`."
msgstr ""

#: ../../docs/tutorials/best_practices/logic_preferences.rst:4
msgid "Logic preferences"
msgstr ""

#: ../../docs/tutorials/best_practices/logic_preferences.rst:6
msgid ""
"Ever wondered whether one should approach problem X with strategy Y or Z? "
"This article covers a variety of topics related to these dilemmas."
msgstr ""

#: ../../docs/tutorials/best_practices/logic_preferences.rst:10
msgid "Adding nodes and changing properties: which first?"
msgstr ""

#: ../../docs/tutorials/best_practices/logic_preferences.rst:12
msgid ""
"When initializing nodes from a script at runtime, you may need to change "
"properties such as the node's name or position. A common dilemma is, when "
"should you change those values?"
msgstr ""

#: ../../docs/tutorials/best_practices/logic_preferences.rst:16
msgid ""
"It is the best practice to change values on a node before adding it to the "
"scene tree. Some property's setters have code to update other corresponding "
"values, and that code can be slow! For most cases, this code has no impact "
"on your game's performance, but in heavy use cases such as procedural "
"generation, it can bring your game to a crawl."
msgstr ""

#: ../../docs/tutorials/best_practices/logic_preferences.rst:22
msgid ""
"For these reasons, it is always a best practice to set the initial values of "
"a node before adding it to the scene tree."
msgstr ""

#: ../../docs/tutorials/best_practices/logic_preferences.rst:26
msgid "Loading vs. preloading"
msgstr ""

#: ../../docs/tutorials/best_practices/logic_preferences.rst:28
msgid ""
"In GDScript, there exists the global :ref:`preload "
"<class_@GDScript_method_preload>` method. It loads resources as early as "
"possible to front-load the \"loading\" operations and avoid loading "
"resources while in the middle of performance-sensitive code."
msgstr ""

#: ../../docs/tutorials/best_practices/logic_preferences.rst:33
msgid ""
"Its counterpart, the :ref:`load <class_@GDScript_method_load>` method, loads "
"a resource only when it reaches the load statement. That is, it will load a "
"resource in-place which can cause slowdowns when it occurs in the middle of "
"sensitive processes. The ``load()`` function is also an alias for :ref:"
"`ResourceLoader.load(path) <class_ResourceLoader_method_load>` which is "
"accessible to *all* scripting languages."
msgstr ""

#: ../../docs/tutorials/best_practices/logic_preferences.rst:40
msgid ""
"So, when exactly does preloading occur versus loading, and when should one "
"use either? Let's see an example:"
msgstr ""

#: ../../docs/tutorials/best_practices/logic_preferences.rst:103
msgid ""
"Preloading allows the script to handle all the loading the moment one loads "
"the script. Preloading is useful, but there are also times when one doesn't "
"wish for it. To distinguish these situations, there are a few things one can "
"consider:"
msgstr ""

#: ../../docs/tutorials/best_practices/logic_preferences.rst:108
msgid ""
"If one cannot determine when the script might load, then preloading a "
"resource, especially a scene or script, could result in further loads one "
"does not expect. This could lead to unintentional, variable-length load "
"times on top of the original script's load operations."
msgstr ""

#: ../../docs/tutorials/best_practices/logic_preferences.rst:113
msgid ""
"If something else could replace the value (like a scene's exported "
"initialization), then preloading the value has no meaning. This point isn't "
"a significant factor if one intends to always create the script on its own."
msgstr ""

#: ../../docs/tutorials/best_practices/logic_preferences.rst:117
msgid ""
"If one wishes only to 'import' another class resource (script or scene), "
"then using a preloaded constant is often the best course of action. However, "
"in exceptional cases, one may wish not to do this:"
msgstr ""

#: ../../docs/tutorials/best_practices/logic_preferences.rst:121
msgid ""
"If the 'imported' class is liable to change, then it should be a property "
"instead, initialized either using an ``export`` or a ``load()`` (and perhaps "
"not even initialized until later)."
msgstr ""

#: ../../docs/tutorials/best_practices/logic_preferences.rst:125
msgid ""
"If the script requires a great many dependencies, and one does not wish to "
"consume so much memory, then one may wish to, load and unload various "
"dependencies at runtime as circumstances change. If one preloads resources "
"into constants, then the only way to unload these resources would be to "
"unload the entire script. If they are instead loaded properties, then one "
"can set them to ``null`` and remove all references to the resource entirely "
"(which, as a :ref:`RefCounted <class_RefCounted>`-extending type, will cause "
"the resources to delete themselves from memory)."
msgstr ""

#: ../../docs/tutorials/best_practices/logic_preferences.rst:136
msgid "Large levels: static vs. dynamic"
msgstr ""

#: ../../docs/tutorials/best_practices/logic_preferences.rst:138
msgid ""
"If one is creating a large level, which circumstances are most appropriate? "
"Should they create the level as one static space? Or should they load the "
"level in pieces and shift the world's content as needed?"
msgstr ""

#: ../../docs/tutorials/best_practices/logic_preferences.rst:142
msgid ""
"Well, the simple answer is, \"when the performance requires it.\" The "
"dilemma associated with the two options is one of the age-old programming "
"choices: does one optimize memory over speed, or vice versa?"
msgstr ""

#: ../../docs/tutorials/best_practices/logic_preferences.rst:146
msgid ""
"The naive answer is to use a static level that loads everything at once. "
"But, depending on the project, this could consume a large amount of memory. "
"Wasting users' RAM leads to programs running slow or outright crashing from "
"everything else the computer tries to do at the same time."
msgstr ""

#: ../../docs/tutorials/best_practices/logic_preferences.rst:151
msgid ""
"No matter what, one should break larger scenes into smaller ones (to aid in "
"reusability of assets). Developers can then design a node that manages the "
"creation/loading and deletion/unloading of resources and nodes in real-time. "
"Games with large and varied environments or procedurally generated elements "
"often implement these strategies to avoid wasting memory."
msgstr ""

#: ../../docs/tutorials/best_practices/logic_preferences.rst:157
msgid ""
"On the flip side, coding a dynamic system is more complex, i.e. uses more "
"programmed logic, which results in opportunities for errors and bugs. If one "
"isn't careful, they can develop a system that bloats the technical debt of "
"the application."
msgstr ""

#: ../../docs/tutorials/best_practices/logic_preferences.rst:162
msgid "As such, the best options would be..."
msgstr ""

#: ../../docs/tutorials/best_practices/logic_preferences.rst:164
msgid "To use a static level for smaller games."
msgstr ""

#: ../../docs/tutorials/best_practices/logic_preferences.rst:166
msgid ""
"If one has the time/resources on a medium/large game, create a library or "
"plugin that can code the management of nodes and resources. If refined over "
"time, so as to improve usability and stability, then it could evolve into a "
"reliable tool across projects."
msgstr ""

#: ../../docs/tutorials/best_practices/logic_preferences.rst:171
msgid ""
"Code the dynamic logic for a medium/large game because one has the coding "
"skills, but not the time or resources to refine the code (game's gotta get "
"done). Could potentially refactor later to outsource the code into a plugin."
msgstr ""

#: ../../docs/tutorials/best_practices/logic_preferences.rst:176
msgid ""
"For an example of the various ways one can swap scenes around at runtime, "
"please see the :ref:`\"Change scenes manually\" "
"<doc_change_scenes_manually>` documentation."
msgstr ""

#: ../../docs/tutorials/best_practices/project_organization.rst:4
msgid "Project organization"
msgstr ""

#: ../../docs/tutorials/best_practices/project_organization.rst:9
msgid ""
"Since Godot has no restrictions on project structure or filesystem usage, "
"organizing files when learning the engine can seem challenging. This "
"tutorial suggests a workflow which should be a good starting point. We will "
"also cover using version control with Godot."
msgstr ""

#: ../../docs/tutorials/best_practices/project_organization.rst:15
msgid "Organization"
msgstr ""

#: ../../docs/tutorials/best_practices/project_organization.rst:17
msgid ""
"Godot is scene-based in nature, and uses the filesystem as-is, without "
"metadata or an asset database."
msgstr ""

#: ../../docs/tutorials/best_practices/project_organization.rst:20
msgid ""
"Unlike other engines, many resources are contained within the scene itself, "
"so the amount of files in the filesystem is considerably lower."
msgstr ""

#: ../../docs/tutorials/best_practices/project_organization.rst:23
msgid ""
"Considering that, the most common approach is to group assets as close to "
"scenes as possible; when a project grows, it makes it more maintainable."
msgstr ""

#: ../../docs/tutorials/best_practices/project_organization.rst:27
msgid ""
"As an example, one can usually place into a single folder their basic "
"assets, such as sprite images, 3D model meshes, materials, and music, etc. "
"They can then use a separate folder to store built levels that use them."
msgstr ""

#: ../../docs/tutorials/best_practices/project_organization.rst:48
msgid "Style guide"
msgstr ""

#: ../../docs/tutorials/best_practices/project_organization.rst:50
msgid ""
"For consistency across projects, we recommend following these guidelines:"
msgstr ""

#: ../../docs/tutorials/best_practices/project_organization.rst:52
msgid ""
"Use **snake_case** for folder and file names (with the exception of C# "
"scripts). This sidesteps case sensitivity issues that can crop up after "
"exporting a project on Windows. C# scripts are an exception to this rule, as "
"the convention is to name them after the class name which should be in "
"PascalCase."
msgstr ""

#: ../../docs/tutorials/best_practices/project_organization.rst:57
msgid ""
"Use **PascalCase** for node names, as this matches built-in node casing."
msgstr ""

#: ../../docs/tutorials/best_practices/project_organization.rst:58
msgid ""
"In general, keep third-party resources in a top-level ``addons/`` folder, "
"even if they aren't editor plugins. This makes it easier to track which "
"files are third-party. There are some exceptions to this rule; for instance, "
"if you use third-party game assets for a character, it makes more sense to "
"include them within the same folder as the character scenes and scripts."
msgstr ""

#: ../../docs/tutorials/best_practices/project_organization.rst:65
msgid "Importing"
msgstr ""

#: ../../docs/tutorials/best_practices/project_organization.rst:67
msgid ""
"Godot versions prior to 3.0 did the import process from files outside the "
"project. While this can be useful in large projects, it resulted in an "
"organization hassle for most developers."
msgstr ""

#: ../../docs/tutorials/best_practices/project_organization.rst:71
msgid ""
"Because of this, assets are now transparently imported from within the "
"project folder."
msgstr ""

#: ../../docs/tutorials/best_practices/project_organization.rst:75
msgid "Ignoring specific folders"
msgstr ""

#: ../../docs/tutorials/best_practices/project_organization.rst:77
msgid ""
"To prevent Godot from importing files contained in a specific folder, create "
"an empty file called ``.gdignore`` in the folder (the leading ``.`` is "
"required). This can be useful to speed up the initial project importing."
msgstr ""

#: ../../docs/tutorials/best_practices/project_organization.rst:83
msgid ""
"To create a file whose name starts with a dot on Windows, place a dot at "
"both the beginning and end of the filename (\".gdignore.\"). Windows will "
"automatically remove the trailing dot when you confirm the name."
msgstr ""

#: ../../docs/tutorials/best_practices/project_organization.rst:87
msgid ""
"Alternatively, you can use a text editor such as Notepad++ or use the "
"following command in a command prompt: ``type nul > .gdignore``"
msgstr ""

#: ../../docs/tutorials/best_practices/project_organization.rst:90
msgid ""
"Once the folder is ignored, resources in that folder can't be loaded anymore "
"using the ``load()`` and ``preload()`` methods. Ignoring a folder will also "
"automatically hide it from the FileSystem dock, which can be useful to "
"reduce clutter."
msgstr ""

#: ../../docs/tutorials/best_practices/project_organization.rst:94
msgid ""
"Note that the ``.gdignore`` file's contents are ignored, which is why the "
"file should be empty. It does not support patterns like ``.gitignore`` files "
"do."
msgstr ""

#: ../../docs/tutorials/best_practices/project_organization.rst:100
msgid "Case sensitivity"
msgstr ""

#: ../../docs/tutorials/best_practices/project_organization.rst:102
msgid ""
"Windows and recent macOS versions use case-insensitive filesystems by "
"default, whereas Linux distributions use a case-sensitive filesystem by "
"default. This can cause issues after exporting a project, since Godot's PCK "
"virtual filesystem is case-sensitive. To avoid this, it's recommended to "
"stick to ``snake_case`` naming for all files in the project (and lowercase "
"characters in general)."
msgstr ""

#: ../../docs/tutorials/best_practices/project_organization.rst:111
msgid ""
"You can break this rule when style guides say otherwise (such as the C# "
"style guide). Still, be consistent to avoid mistakes."
msgstr ""

#: ../../docs/tutorials/best_practices/project_organization.rst:114
msgid ""
"On Windows 10, to further avoid mistakes related to case sensitivity, you "
"can also make the project folder case-sensitive. After enabling the Windows "
"Subsystem for Linux feature, run the following command in a PowerShell "
"window::"
msgstr ""

#: ../../docs/tutorials/best_practices/project_organization.rst:124
msgid ""
"If you haven't enabled the Windows Subsystem for Linux, you can enter the "
"following line in a PowerShell window *running as Administrator* then reboot "
"when asked::"
msgstr ""

#: ../../docs/tutorials/best_practices/version_control_systems.rst:4
msgid "Version control systems"
msgstr ""

#: ../../docs/tutorials/best_practices/version_control_systems.rst:9
msgid ""
"Godot aims to be VCS-friendly and generate mostly readable and mergeable "
"files."
msgstr ""

#: ../../docs/tutorials/best_practices/version_control_systems.rst:12
#, fuzzy
msgid "Version control plugins"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/best_practices/version_control_systems.rst:14
msgid ""
"Godot also supports the use of version control systems in the editor itself. "
"However, version control in the editor requires a plugin for the specific "
"VCS you're using."
msgstr ""

#: ../../docs/tutorials/best_practices/version_control_systems.rst:18
msgid ""
"As of July 2023, there is only a Git plugin available, but the community may "
"create additional VCS plugins."
msgstr ""

#: ../../docs/tutorials/best_practices/version_control_systems.rst:22
msgid "Official Git plugin"
msgstr ""

#: ../../docs/tutorials/best_practices/version_control_systems.rst:24
msgid ""
"Using Git from inside the editor is supported with an official plugin. You "
"can find the latest releases on `GitHub <https://github.com/godotengine/"
"godot-git-plugin/releases>`__."
msgstr ""

#: ../../docs/tutorials/best_practices/version_control_systems.rst:28
#, fuzzy
msgid ""
"Documentation on how to use the Git plugin can be found on its `wiki "
"<https://github.com/godotengine/godot-git-plugin/wiki>`__."
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati raznorazne `Godot demo projects "
"<https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/tutorials/best_practices/version_control_systems.rst:32
msgid "Files to exclude from VCS"
msgstr ""

#: ../../docs/tutorials/best_practices/version_control_systems.rst:36
msgid ""
"This lists files and folders that should be ignored from version control in "
"Godot 4.1 and later."
msgstr ""

#: ../../docs/tutorials/best_practices/version_control_systems.rst:39
msgid ""
"The list of files of folders that should be ignored from version control in "
"Godot 3.x and Godot 4.0 is **entirely** different. This is important, as "
"Godot 3.x and 4.0 may store sensitive credentials in ``export_presets.cfg`` "
"(unlike Godot 4.1 and later)."
msgstr ""

#: ../../docs/tutorials/best_practices/version_control_systems.rst:44
msgid ""
"If you are using Godot 3, check the ``3.5`` version of this documentation "
"page instead."
msgstr ""

#: ../../docs/tutorials/best_practices/version_control_systems.rst:47
msgid ""
"There are some files and folders Godot automatically creates when opening a "
"project in the editor for the first time. To avoid bloating your version "
"control repository with generated data, you should add them to your VCS "
"ignore:"
msgstr ""

#: ../../docs/tutorials/best_practices/version_control_systems.rst:51
msgid "``.godot/``: This folder stores various project cache data."
msgstr ""

#: ../../docs/tutorials/best_practices/version_control_systems.rst:52
msgid ""
"``*.translation``: These files are binary imported :ref:`translations "
"<doc_internationalizing_games>` generated from CSV files."
msgstr ""

#: ../../docs/tutorials/best_practices/version_control_systems.rst:55
msgid ""
"You can make the Godot project manager generate version control metadata for "
"you automatically when creating a project. When choosing the **Git** option, "
"this creates ``.gitignore`` and ``.gitattributes`` files in the project root:"
msgstr ""

#: ../../docs/tutorials/best_practices/version_control_systems.rst:63
msgid ""
"Creating version control metadata in the project manager's New Project dialog"
msgstr ""

#: ../../docs/tutorials/best_practices/version_control_systems.rst:63
msgid ""
"Creating version control metadata in the project manager's **New Project** "
"dialog"
msgstr ""

#: ../../docs/tutorials/best_practices/version_control_systems.rst:65
msgid ""
"In existing projects, select the **Project** menu at the top of the editor, "
"then choose **Version Control > Generate Version Control Metadata**. This "
"creates the same files as if the operation was performed in the project "
"manager."
msgstr ""

#: ../../docs/tutorials/best_practices/version_control_systems.rst:70
msgid "Working with Git on Windows"
msgstr ""

#: ../../docs/tutorials/best_practices/version_control_systems.rst:72
msgid ""
"Most Git for Windows clients are configured with the ``core.autocrlf`` set "
"to ``true``. This can lead to files unnecessarily being marked as modified "
"by Git due to their line endings being converted from LF to CRLF "
"automatically."
msgstr ""

#: ../../docs/tutorials/best_practices/version_control_systems.rst:76
msgid "It is better to set this option as:"
msgstr ""

#: ../../docs/tutorials/best_practices/version_control_systems.rst:82
msgid ""
"Creating version control metadata using the project manager or editor will "
"automatically enforce LF line endings using the ``.gitattributes`` file. In "
"this case, you don't need to change your Git configuration."
msgstr ""

#: ../../docs/tutorials/troubleshooting.rst:4
#: ../../docs/tutorials/3d/occlusion_culling.rst:261
#: ../../docs/tutorials/3d/resolution_scaling.rst:261
#: ../../docs/tutorials/audio/text_to_speech.rst:85
#: ../../docs/tutorials/export/exporting_for_ios.rst:133
#: ../../docs/tutorials/export/one-click_deploy.rst:65
#: ../../docs/tutorials/inputs/controllers_gamepads_joysticks.rst:281
#: ../../docs/contributing/development/compiling/compiling_for_windows.rst:248
#: ../../docs/contributing/development/compiling/compiling_for_android.rst:253
#: ../../docs/contributing/development/compiling/compiling_with_script_encryption_key.rst:83
#: ../../docs/contributing/development/editor/creating_icons.rst:92
msgid "Troubleshooting"
msgstr ""

#: ../../docs/tutorials/troubleshooting.rst:6
msgid ""
"This page lists common issues encountered when using Godot and possible "
"solutions."
msgstr ""

#: ../../docs/tutorials/troubleshooting.rst:10
msgid ""
"See :ref:`doc_using_the_web_editor` for caveats specific to the Web version "
"of the Godot editor."
msgstr ""

#: ../../docs/tutorials/troubleshooting.rst:14
msgid ""
"The editor runs slowly and uses all my CPU and GPU resources, making my "
"computer noisy"
msgstr ""

#: ../../docs/tutorials/troubleshooting.rst:16
msgid ""
"This is a known issue, especially on macOS since most Macs have Retina "
"displays. Due to Retina displays' higher pixel density, everything has to be "
"rendered at a higher resolution. This increases the load on the GPU and "
"decreases perceived performance."
msgstr ""

#: ../../docs/tutorials/troubleshooting.rst:21
msgid "There are several ways to improve performance and battery life:"
msgstr ""

#: ../../docs/tutorials/troubleshooting.rst:23
msgid ""
"In 3D, click the **Perspective** button in the top left corner and enable "
"**Half Resolution**. The 3D viewport will now be rendered at half "
"resolution, which can be up to 4 times faster."
msgstr ""

#: ../../docs/tutorials/troubleshooting.rst:26
msgid ""
"Open the Editor Settings and increase the value of **Low Processor Mode "
"Sleep (µsec)** to ``33000`` (30 FPS). This value determines the amount of "
"*microseconds* between frames to render. Higher values will make the editor "
"feel less reactive but will help decrease CPU and GPU usage significantly."
msgstr ""

#: ../../docs/tutorials/troubleshooting.rst:30
msgid ""
"If you have a node that causes the editor to redraw continuously (such as "
"particles), hide it and show it using a script in the ``_ready()`` method. "
"This way, it will be hidden in the editor but will still be visible in the "
"running project."
msgstr ""

#: ../../docs/tutorials/troubleshooting.rst:36
msgid ""
"The editor stutters and flickers on my variable refresh rate monitor (G-Sync/"
"FreeSync)"
msgstr ""

#: ../../docs/tutorials/troubleshooting.rst:38
msgid ""
"This is a `known issue <https://github.com/godotengine/godot/"
"issues/38219>`__. Variable refresh rate monitors need to adjust their gamma "
"curves continuously to emit a consistent amount of light over time. This can "
"cause flicker to appear in dark areas of the image when the refresh rate "
"varies a lot, which occurs as the Godot editor only redraws when necessary."
msgstr ""

#: ../../docs/tutorials/troubleshooting.rst:44
#, fuzzy
msgid "There are several workarounds for this:"
msgstr "Ne postoje ograničenja prilikom korištenja Godot-a"

#: ../../docs/tutorials/troubleshooting.rst:46
msgid ""
"Enable **Interface > Editor > Update Continuously** in the Editor Settings. "
"Keep in mind this will increase power usage and heat/noise emissions since "
"the editor will now be rendering constantly, even if nothing has changed on "
"screen. To alleviate this, you can increase **Low Processor Mode Sleep "
"(µsec)** to ``33000`` (30 FPS) in the Editor Settings. This value determines "
"the amount of *microseconds* between frames to render. Higher values will "
"make the editor feel less reactive but will help decrease CPU and GPU usage "
"significantly."
msgstr ""

#: ../../docs/tutorials/troubleshooting.rst:53
msgid ""
"Alternatively, disable variable refresh rate on your monitor or in the "
"graphics driver."
msgstr ""

#: ../../docs/tutorials/troubleshooting.rst:54
msgid ""
"VRR flicker can be reduced on some displays using the **VRR Control** or "
"**Fine Tune Dark Areas** options in your monitor's OSD. These options may "
"increase input lag or result in crushed blacks."
msgstr ""

#: ../../docs/tutorials/troubleshooting.rst:57
msgid ""
"If using an OLED display, use the **Black (OLED)** editor theme preset in "
"the Editor Settings. This hides VRR flicker thanks to OLED's perfect black "
"levels."
msgstr ""

#: ../../docs/tutorials/troubleshooting.rst:61
msgid "The editor or project takes a very long time to start"
msgstr ""

#: ../../docs/tutorials/troubleshooting.rst:63
msgid ""
"When using one of the Vulkan-based renderers (Forward+ or Forward Mobile), "
"the first startup is expected to be relatively long. This is because shaders "
"need to be compiled before they can be cached. Shaders also need to be "
"cached again after updating Godot, after updating graphics drivers or after "
"switching graphics cards."
msgstr ""

#: ../../docs/tutorials/troubleshooting.rst:69
msgid ""
"If the issue persists after the first startup, this is a `known bug <https://"
"github.com/godotengine/godot/issues/20566>`__ on Windows when you have "
"specific USB peripherals connected. In particular, Corsair's iCUE software "
"seems to cause this bug. Try updating your USB peripherals' drivers to their "
"latest version. If the bug persists, you need to disconnect the specific "
"peripheral before opening the editor. You can then connect the peripheral "
"again."
msgstr ""

#: ../../docs/tutorials/troubleshooting.rst:77
msgid ""
"Firewall software such as Portmaster may also cause the debug port to be "
"blocked. This causes the project to take a long time to start, while being "
"unable to use debugging features in the editor (such as viewing ``print()`` "
"output). You can work this around by changing the debug port used by the "
"project in the Editor Settings (**Network > Debug > Remote Port**). The "
"default is ``6007``; try another value that is greater than ``1024``, such "
"as ``7007``."
msgstr ""

#: ../../docs/tutorials/troubleshooting.rst:85
msgid "The Godot editor appears frozen after clicking the system console"
msgstr ""

#: ../../docs/tutorials/troubleshooting.rst:87
msgid ""
"When running Godot on Windows with the system console enabled, you can "
"accidentally enable *selection mode* by clicking inside the command window. "
"This Windows-specific behavior pauses the application to let you select text "
"inside the system console. Godot cannot override this system-specific "
"behavior."
msgstr ""

#: ../../docs/tutorials/troubleshooting.rst:92
msgid ""
"To solve this, select the system console window and press Enter to leave "
"selection mode."
msgstr ""

#: ../../docs/tutorials/troubleshooting.rst:96
msgid ""
"The Godot editor's macOS dock icon gets duplicated every time it is manually "
"moved"
msgstr ""

#: ../../docs/tutorials/troubleshooting.rst:98
msgid ""
"If you open the Godot editor and manually change the position of the dock "
"icon, then restart the editor, you will get a duplicate dock icon all the "
"way to the right of the dock."
msgstr ""

#: ../../docs/tutorials/troubleshooting.rst:102
msgid ""
"This is due to a design limitation of the macOS dock. The only known way to "
"resolve this would be to merge the project manager and editor into a single "
"process, which means the project manager would no longer spawn a separate "
"process when starting the editor. While using a single process instance "
"would bring several benefits, it isn't planned to be done in the near future "
"due to the complexity of the task."
msgstr ""

#: ../../docs/tutorials/troubleshooting.rst:109
msgid ""
"To avoid this issue, keep the Godot editor's dock icon at its default "
"location as created by macOS."
msgstr ""

#: ../../docs/tutorials/troubleshooting.rst:113
msgid ""
"Some text such as \"NO DC\" appears in the top-left corner of the Project "
"Manager and editor window"
msgstr ""

#: ../../docs/tutorials/troubleshooting.rst:115
msgid ""
"This is caused by the NVIDIA graphics driver injecting an overlay to display "
"information."
msgstr ""

#: ../../docs/tutorials/troubleshooting.rst:117
msgid ""
"To disable this overlay on Windows, restore your graphics driver settings to "
"the default values in the NVIDIA Control Panel."
msgstr ""

#: ../../docs/tutorials/troubleshooting.rst:120
msgid ""
"To disable this overlay on Linux, open ``nvidia-settings``, go to **X Screen "
"0 > OpenGL Settings** then uncheck **Enable Graphics API Visual Indicator**."
msgstr ""

#: ../../docs/tutorials/troubleshooting.rst:124
msgid "The editor or project appears overly sharp or blurry"
msgstr ""

#: ../../docs/tutorials/troubleshooting.rst:130
msgid ""
"Correct appearance (left), oversharpened appearance due to graphics driver "
"sharpening (right)"
msgstr ""

#: ../../docs/tutorials/troubleshooting.rst:132
msgid ""
"If the editor or project appears overly sharp, this is likely due to image "
"sharpening being forced on all Vulkan or OpenGL applications by your "
"graphics driver. You can disable this behavior in the graphics driver's "
"control panel:"
msgstr ""

#: ../../docs/tutorials/troubleshooting.rst:136
msgid ""
"**NVIDIA (Windows):** Open the start menu and choose **NVIDIA Control "
"Panel**. Open the **Manage 3D settings** tab on the left. In the list in the "
"middle, scroll to **Image Sharpening** and set it to **Sharpening Off**."
msgstr ""

#: ../../docs/tutorials/troubleshooting.rst:139
msgid ""
"**AMD (Windows):** Open the start menu and choose **AMD Software**. Click "
"the settings \"cog\" icon in the top-right corner. Go to the **Graphics** "
"tab then disable **Radeon Image Sharpening**."
msgstr ""

#: ../../docs/tutorials/troubleshooting.rst:143
msgid ""
"If the editor or project appears overly blurry, this is likely due to :abbr:"
"`FXAA (Fast Approximate AntiAliasing)` being forced on all Vulkan or OpenGL "
"applications by your graphics driver."
msgstr ""

#: ../../docs/tutorials/troubleshooting.rst:147
msgid ""
"**NVIDIA (Windows):** Open the start menu and choose **NVIDIA Control "
"Panel**. Open the **Manage 3D settings** tab on the left. In the list in the "
"middle, scroll to **Fast Approximate Antialiasing** and set it to "
"**Application Controlled**."
msgstr ""

#: ../../docs/tutorials/troubleshooting.rst:151
msgid ""
"**NVIDIA (Linux):** Open the applications menu and choose **NVIDIA X Server "
"Settings**. Select to **Antialiasing Settings** on the left, then uncheck "
"**Enable FXAA**."
msgstr ""

#: ../../docs/tutorials/troubleshooting.rst:154
msgid ""
"**AMD (Windows):** Open the start menu and choose **AMD Software**. Click "
"the settings \"cog\" icon in the top-right corner. Go to the **Graphics** "
"tab, scroll to the bottom and click **Advanced** to unfold its settings. "
"Disable **Morphological Anti-Aliasing**."
msgstr ""

#: ../../docs/tutorials/troubleshooting.rst:159
msgid ""
"Third-party vendor-independent utilities such as vkBasalt may also force "
"sharpening or FXAA on all Vulkan applications. You may want to check their "
"configuration as well."
msgstr ""

#: ../../docs/tutorials/troubleshooting.rst:163
msgid ""
"After changing options in the graphics driver or third-party utilities, "
"restart Godot to make the changes effective."
msgstr ""

#: ../../docs/tutorials/troubleshooting.rst:166
msgid ""
"If you still wish to force sharpening or FXAA on other applications, it's "
"recommended to do so on a per-application basis using the application "
"profiles system provided by graphics drivers' control panels."
msgstr ""

#: ../../docs/tutorials/troubleshooting.rst:171
msgid "The editor or project appears to have washed out colors"
msgstr ""

#: ../../docs/tutorials/troubleshooting.rst:173
msgid ""
"On Windows, this is usually caused by incorrect OS or monitor settings, as "
"Godot currently does not support :abbr:`HDR (High Dynamic Range)` *output* "
"(even though it may internally render in HDR)."
msgstr ""

#: ../../docs/tutorials/troubleshooting.rst:177
msgid ""
"As `most displays are not designed to display SDR content in HDR mode "
"<https://tftcentral.co.uk/articles/heres-why-you-should-only-enable-hdr-mode-"
"on-your-pc-when-you-are-viewing-hdr-content>`__, it is recommended to "
"disable HDR in the Windows settings when not running applications that use "
"HDR output. On Windows 11, this can be done by pressing :kbd:`Windows + Alt "
"+ B` (this shortcut is part of the Xbox Game Bar app). To toggle HDR "
"automatically based on applications currently running, you can use "
"`AutoActions <https://github.com/Codectory/AutoActions>`__."
msgstr ""

#: ../../docs/tutorials/troubleshooting.rst:184
msgid ""
"If you insist on leaving HDR enabled, it is possible to somewhat improve the "
"result by ensuring the display is configured to use :abbr:`HGIG (HDR Gaming "
"Interest Group)` tonemapping (as opposed to :abbr:`DTM (Dynamic Tone "
"Mapping)`), then `using the Windows HDR calibration app <https://support."
"microsoft.com/en-us/windows/calibrate-your-hdr-display-using-the-windows-hdr-"
"calibration-app-f30f4809-3369-43e4-9b02-9eabebd23f19>`__. It is also "
"strongly recommended to use Windows 11 instead of Windows 10 when using HDR. "
"The end result will still likely be inferior to disabling HDR on the "
"display, though."
msgstr ""

#: ../../docs/tutorials/troubleshooting.rst:191
msgid "Support for HDR *output* is planned in a future release."
msgstr ""

#: ../../docs/tutorials/troubleshooting.rst:194
msgid ""
"The editor/project freezes or displays glitched visuals after resuming the "
"PC from suspend"
msgstr ""

#: ../../docs/tutorials/troubleshooting.rst:196
msgid ""
"This is a known issue on Linux with NVIDIA graphics when using the "
"proprietary driver. There is no definitive fix yet, as suspend on Linux + "
"NVIDIA is often buggy when OpenGL or Vulkan is involved. The Compatibility "
"rendering method (which uses OpenGL) is generally less prone to suspend-"
"related issues compared to the Forward+ and Forward Mobile rendering methods "
"(which use Vulkan)."
msgstr ""

#: ../../docs/tutorials/troubleshooting.rst:202
msgid ""
"The NVIDIA driver offers an *experimental* `option to preserve video memory "
"after suspend <https://wiki.archlinux.org/title/NVIDIA/"
"Tips_and_tricks#Preserve_video_memory_after_suspend>`__ which may resolve "
"this issue. This option has been reported to work better with more recent "
"NVIDIA driver versions."
msgstr ""

#: ../../docs/tutorials/troubleshooting.rst:207
msgid ""
"To avoid losing work, save scenes in the editor before putting the PC to "
"sleep."
msgstr ""

#: ../../docs/tutorials/troubleshooting.rst:210
msgid ""
"The project works when run from the editor, but fails to load some files "
"when running from an exported copy"
msgstr ""

#: ../../docs/tutorials/troubleshooting.rst:212
msgid ""
"This is usually caused by forgetting to specify a filter for non-resource "
"files in the Export dialog. By default, Godot will only include actual "
"*resources* into the PCK file. Some files commonly used, such as JSON files, "
"are not considered resources. For example, if you load ``test.json`` in the "
"exported project, you need to specify ``*.json`` in the non-resource export "
"filter. See :ref:`doc_exporting_projects_export_mode` for more information."
msgstr ""

#: ../../docs/tutorials/troubleshooting.rst:219
msgid ""
"Also, note that files and folders whose names begin with a period will never "
"be included in the exported project. This is done to prevent version control "
"folders like ``.git`` from being included in the exported PCK file."
msgstr ""

#: ../../docs/tutorials/troubleshooting.rst:223
msgid ""
"On Windows, this can also be due to :ref:`case sensitivity "
"<doc_project_organization_case_sensitivity>` issues. If you reference a "
"resource in your script with a different case than on the filesystem, "
"loading will fail once you export the project. This is because the virtual "
"PCK filesystem is case-sensitive, while Windows's filesystem is case-"
"insensitive by default."
msgstr ""

#: ../../docs/tutorials/editor/index.rst:4
#, fuzzy
msgid "Editor introduction"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/editor/index.rst:6
msgid ""
"In this section, we cover the Godot editor in general, from its interface to "
"using it with the command line."
msgstr ""

#: ../../docs/tutorials/editor/index.rst:10
#, fuzzy
msgid "Editor's interface"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/editor/index.rst:12
msgid ""
"The following pages explain how to use the various windows, workspaces, and "
"docks that make up the Godot editor. We cover some specific editors' "
"interface in other sections where appropriate. For example, the :ref:"
"`animation editor <doc_introduction_animation>`."
msgstr ""

#: ../../docs/tutorials/editor/index.rst:28
msgid "Android editor"
msgstr ""

#: ../../docs/tutorials/editor/index.rst:30
msgid ""
"Godot offers a native port of the editor running entirely on Android "
"devices. The Android port can be downloaded from the `Android Downloads page "
"<https://godotengine.org/download/android/>`__. While we strive for feature "
"parity with the Desktop version of the editor, the Android port has a "
"certain amount of caveats you should be aware of."
msgstr ""

#: ../../docs/tutorials/editor/index.rst:42
#, fuzzy
msgid "Web editor"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/editor/index.rst:44
msgid ""
"Godot offers an HTML5 version of the editor running entirely in your "
"browser. No download is required to use it, but it has a certain amount of "
"caveats you should be aware of."
msgstr ""

#: ../../docs/tutorials/editor/index.rst:55
#, fuzzy
msgid "Advanced features"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/editor/index.rst:57
msgid ""
"The articles below focus on advanced features useful for experienced "
"developers, such as calling Godot from the command line and using an "
"external text editor like Visual Studio Code or Emacs."
msgstr ""

#: ../../docs/tutorials/editor/index.rst:69
#: ../../docs/tutorials/editor/managing_editor_features.rst:6
#, fuzzy
msgid "Managing editor features"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/editor/index.rst:71
msgid ""
"Godot allows you to remove features from the editor. This may be useful if "
"you're an educator trying to ease students into the editor slowly, or if "
"you're working on a project that's only 2D or only 3D and don't want to see "
"what you don't need."
msgstr ""

#: ../../docs/tutorials/editor/project_manager.rst:4
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:116
#, fuzzy
msgid "Using the Project Manager"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/editor/project_manager.rst:6
msgid ""
"When you launch Godot, the first window you see is the Project Manager. It "
"lets you create, remove, import, or play game projects."
msgstr ""

#: ../../docs/tutorials/editor/project_manager.rst:11
msgid ""
"In the window's top-right corner, a drop-down menu allows you to change the "
"editor's language."
msgstr ""

#: ../../docs/tutorials/editor/project_manager.rst:19
#, fuzzy
msgid "Creating and importing projects"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/editor/project_manager.rst:21
#, fuzzy
msgid "To create a new project:"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/editor/project_manager.rst:23
msgid "Click the **New** button on the top-left of the window."
msgstr ""

#: ../../docs/tutorials/editor/project_manager.rst:24
msgid ""
"Give the project a name, choose an empty folder on your computer to save the "
"files, and select a rendering backend."
msgstr ""

#: ../../docs/tutorials/editor/project_manager.rst:26
msgid ""
"Click the **Create & Edit** button to create the project folder and open it "
"in the editor."
msgstr ""

#: ../../docs/tutorials/editor/project_manager.rst:31
#, fuzzy
msgid "Using the file browser"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/editor/project_manager.rst:33
msgid ""
"Click the **Browse** button to open Godot's file browser and pick a location "
"or type the folder's path in the Project Path field."
msgstr ""

#: ../../docs/tutorials/editor/project_manager.rst:38
msgid ""
"When you see the green tick on the right, it means the engine detects an "
"empty folder. You can also click the **Create Folder** button to create an "
"empty folder based on your project's name."
msgstr ""

#: ../../docs/tutorials/editor/project_manager.rst:43
#, fuzzy
msgid "Opening and importing projects"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/editor/project_manager.rst:45
msgid ""
"The next time you open the Project Manager, you'll see your new project in "
"the list. Double click on it to open it in the editor."
msgstr ""

#: ../../docs/tutorials/editor/project_manager.rst:50
msgid ""
"You can similarly import existing projects using the **Import** button. "
"Locate the folder that contains the project or the **project.godot** file to "
"import and edit it."
msgstr ""

#: ../../docs/tutorials/editor/project_manager.rst:56
msgid "When the folder path is correct, you'll see a green checkmark."
msgstr ""

#: ../../docs/tutorials/editor/project_manager.rst:61
#, fuzzy
msgid "Downloading demos and templates"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/editor/project_manager.rst:63
msgid ""
"From the **Asset Library Projects** tab you can download open source project "
"templates and demos from the :ref:`Asset Library <doc_what_is_assetlib>` to "
"help you get started faster."
msgstr ""

#: ../../docs/tutorials/editor/project_manager.rst:67
msgid "To download a demo or template:"
msgstr ""

#: ../../docs/tutorials/editor/project_manager.rst:69
msgid "Click on its title."
msgstr ""

#: ../../docs/tutorials/editor/project_manager.rst:70
msgid "On the page that opens, click the download button."
msgstr ""

#: ../../docs/tutorials/editor/project_manager.rst:71
msgid ""
"Once it finished downloading, click install and choose where you want to "
"save the project."
msgstr ""

#: ../../docs/tutorials/editor/inspector_dock.rst:6
#, fuzzy
msgid "The Inspector"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/editor/inspector_dock.rst:8
msgid ""
"This page explains how the Inspector dock works in-depth. You will learn how "
"to edit properties, fold and unfold areas, use the search bar, and more."
msgstr ""

#: ../../docs/tutorials/editor/inspector_dock.rst:10
msgid "This page is a work-in-progress."
msgstr ""

#: ../../docs/tutorials/editor/inspector_dock.rst:13
msgid "Overview of the interface"
msgstr ""

#: ../../docs/tutorials/editor/inspector_dock.rst:15
msgid "Let's start by looking at the dock's main parts."
msgstr ""

#: ../../docs/tutorials/editor/inspector_dock.rst:19
msgid "At the top are the file and navigation buttons."
msgstr ""

#: ../../docs/tutorials/editor/inspector_dock.rst:23
msgid ""
"Below it, you can find the selected node's name, its type, and the tools "
"menu on the right side."
msgstr ""

#: ../../docs/tutorials/editor/inspector_dock.rst:27
msgid ""
"If you click the tool menu icon, a drop-down menu offers some view and edit "
"options."
msgstr ""

#: ../../docs/tutorials/editor/inspector_dock.rst:31
msgid ""
"Then comes the search bar. Type anything in it to filter displayed "
"properties. Delete the text to clear the search."
msgstr ""

#: ../../docs/tutorials/editor/project_settings.rst:6
#, fuzzy
msgid "Project Settings"
msgstr "Uvod / Početak"

#: ../../docs/tutorials/editor/project_settings.rst:8
msgid ""
"This page explains how to use the Project Settings window. If you would like "
"to access and modify project settings via code, see :ref:`ProjectSettings "
"<class_ProjectSettings>`."
msgstr ""

#: ../../docs/tutorials/editor/project_settings.rst:10
msgid ""
"Godot stores the project settings in a project.godot file, a plain text file "
"in INI format. There are dozens of settings you can change to control a "
"project's execution. To simplify this process, Godot provides a project "
"settings dialog, which acts as a front-end to editing a project.godot file."
msgstr ""

#: ../../docs/tutorials/editor/project_settings.rst:12
#, fuzzy
msgid "To access that dialog, select Project -> Project Settings."
msgstr "Uvod / Početak"

#: ../../docs/tutorials/editor/project_settings.rst:14
msgid ""
"Once the window opens, let's select a main scene. Locate the `Application/"
"Run/Main Scene` property and click on it to select 'hello.tscn'."
msgstr ""

#: ../../docs/tutorials/editor/project_settings.rst:16
msgid ""
"The project settings dialog provides a lot of options that can be saved to a "
"project.godot file and shows their default values. If you change a value, a "
"tick appears to the left of its name. This means that the property will be "
"saved in the project.godot file and remembered."
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:-1
msgid "cheatsheet, cheat sheet, shortcut"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:9
msgid "Default editor shortcuts"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:10
msgid ""
"Many of Godot Editor functions can be executed with keyboard shortcuts. This "
"page lists functions which have associated shortcuts by default, but many "
"others are available for customization in editor settings as well. To change "
"keys associated with these and other actions navigate to ``Editor -> Editor "
"Settings -> Shortcuts``."
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:15
msgid ""
"While some actions are universal, a lot of shortcuts are specific to "
"individual tools. For this reason it is possible for some key combinations "
"to be assigned to more than one function. The correct action will be "
"performed depending on the context."
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:20
msgid ""
"While Windows and Linux builds of the editor share most of the default "
"settings, some shortcuts may differ for macOS version. This is done for "
"better integration of the editor into macOS ecosystem. Users fluent with "
"standard shortcuts on that OS should find Godot Editor's default key mapping "
"intuitive."
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:26
msgid "General Editor Actions"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:29
#: ../../docs/tutorials/editor/default_key_mapping.rst:94
#: ../../docs/tutorials/editor/default_key_mapping.rst:147
#: ../../docs/tutorials/editor/default_key_mapping.rst:222
#: ../../docs/tutorials/editor/default_key_mapping.rst:303
#: ../../docs/tutorials/editor/default_key_mapping.rst:350
#: ../../docs/tutorials/editor/default_key_mapping.rst:361
#: ../../docs/tutorials/editor/default_key_mapping.rst:374
#: ../../docs/tutorials/editor/default_key_mapping.rst:405
#: ../../docs/tutorials/editor/default_key_mapping.rst:418
#: ../../docs/tutorials/editor/default_key_mapping.rst:441
#: ../../docs/tutorials/editor/default_key_mapping.rst:458
#: ../../docs/tutorials/editor/default_key_mapping.rst:497
msgid "Action name"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:29
#: ../../docs/tutorials/editor/default_key_mapping.rst:94
#: ../../docs/tutorials/editor/default_key_mapping.rst:147
#: ../../docs/tutorials/editor/default_key_mapping.rst:222
#: ../../docs/tutorials/editor/default_key_mapping.rst:303
#: ../../docs/tutorials/editor/default_key_mapping.rst:350
#: ../../docs/tutorials/editor/default_key_mapping.rst:361
#: ../../docs/tutorials/editor/default_key_mapping.rst:374
#: ../../docs/tutorials/editor/default_key_mapping.rst:405
#: ../../docs/tutorials/editor/default_key_mapping.rst:418
#: ../../docs/tutorials/editor/default_key_mapping.rst:441
#: ../../docs/tutorials/editor/default_key_mapping.rst:458
#: ../../docs/tutorials/editor/default_key_mapping.rst:497
#, fuzzy
msgid "Windows, Linux"
msgstr "Windows"

#: ../../docs/tutorials/editor/default_key_mapping.rst:29
#: ../../docs/tutorials/editor/default_key_mapping.rst:94
#: ../../docs/tutorials/editor/default_key_mapping.rst:147
#: ../../docs/tutorials/editor/default_key_mapping.rst:222
#: ../../docs/tutorials/editor/default_key_mapping.rst:303
#: ../../docs/tutorials/editor/default_key_mapping.rst:350
#: ../../docs/tutorials/editor/default_key_mapping.rst:361
#: ../../docs/tutorials/editor/default_key_mapping.rst:374
#: ../../docs/tutorials/editor/default_key_mapping.rst:405
#: ../../docs/tutorials/editor/default_key_mapping.rst:418
#: ../../docs/tutorials/editor/default_key_mapping.rst:441
#: ../../docs/tutorials/editor/default_key_mapping.rst:458
#: ../../docs/tutorials/editor/default_key_mapping.rst:497
#, fuzzy
msgid "Editor setting"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/editor/default_key_mapping.rst:31
msgid "Open 2D Editor"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:31
msgid ":kbd:`Ctrl + F1`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:31
msgid ":kbd:`Alt + 1`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:31
msgid "``editor/editor_2d``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:33
msgid "Open 3D Editor"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:33
#: ../../docs/tutorials/editor/default_key_mapping.rst:422
msgid ":kbd:`Ctrl + F2`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:33
msgid ":kbd:`Alt + 2`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:33
msgid "``editor/editor_3d``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:35
msgid "Open Script Editor"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:35
msgid ":kbd:`Ctrl + F3`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:35
msgid ":kbd:`Alt + 3`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:35
msgid "``editor/editor_script``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:37
msgid "Search Help"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:37
msgid ":kbd:`F1`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:37
msgid ":kbd:`Alt + Space`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:37
msgid "``editor/editor_help``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:39
msgid "Distraction Free Mode"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:39
msgid ":kbd:`Ctrl + Shift + F11`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:39
msgid ":kbd:`Cmd + Ctrl + D`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:39
msgid "``editor/distraction_free_mode``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:41
msgid "Next tab"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:41
msgid ":kbd:`Ctrl + Tab`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:41
msgid ":kbd:`Cmd + Tab`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:41
msgid "``editor/next_tab``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:43
msgid "Previous tab"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:43
msgid ":kbd:`Ctrl + Shift + Tab`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:43
msgid ":kbd:`Cmd + Shift + Tab`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:43
msgid "``editor/prev_tab``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:45
msgid "Filter Files"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:45
msgid ":kbd:`Ctrl + Alt + P`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:45
msgid ":kbd:`Cmd + Alt + P`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:45
msgid "``editor/filter_files``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:47
msgid "Open Scene"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:47
msgid ":kbd:`Ctrl + O`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:47
msgid ":kbd:`Cmd + O`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:47
msgid "``editor/open_scene``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:49
msgid "Close Scene"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:49
msgid ":kbd:`Ctrl + Shift + W`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:49
msgid ":kbd:`Cmd + Shift + W`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:49
msgid "``editor/close_scene``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:51
msgid "Reopen Closed Scene"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:51
#: ../../docs/tutorials/editor/default_key_mapping.rst:321
msgid ":kbd:`Ctrl + Shift + T`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:51
#: ../../docs/tutorials/editor/default_key_mapping.rst:321
msgid ":kbd:`Cmd + Shift + T`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:51
msgid "``editor/reopen_closed_scene``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:53
msgid "Save Scene"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:53
msgid ":kbd:`Ctrl + S`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:53
msgid ":kbd:`Cmd + S`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:53
msgid "``editor/save_scene``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:55
msgid "Save Scene As"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:55
msgid ":kbd:`Ctrl + Shift + S`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:55
msgid ":kbd:`Cmd + Shift + S`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:55
msgid "``editor/save_scene_as``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:57
msgid "Save All Scenes"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:57
#: ../../docs/tutorials/editor/default_key_mapping.rst:325
msgid ":kbd:`Ctrl + Shift + Alt + S`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:57
#: ../../docs/tutorials/editor/default_key_mapping.rst:325
msgid ":kbd:`Cmd + Shift + Alt + S`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:57
msgid "``editor/save_all_scenes``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:59
msgid "Quick Open"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:59
msgid ":kbd:`Shift + Alt + O`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:59
msgid "``editor/quick_open``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:61
msgid "Quick Open Scene"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:61
msgid ":kbd:`Ctrl + Shift + O`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:61
msgid ":kbd:`Cmd + Shift + O`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:61
msgid "``editor/quick_open_scene``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:63
msgid "Quick Open Script"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:63
msgid ":kbd:`Ctrl + Alt + O`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:63
msgid ":kbd:`Cmd + Alt + O`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:63
msgid "``editor/quick_open_script``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:65
#: ../../docs/tutorials/editor/default_key_mapping.rst:244
msgid "Undo"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:65
#: ../../docs/tutorials/editor/default_key_mapping.rst:244
msgid ":kbd:`Ctrl + Z`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:65
#: ../../docs/tutorials/editor/default_key_mapping.rst:244
msgid ":kbd:`Cmd + Z`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:65
msgid "``editor/undo``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:67
#: ../../docs/tutorials/editor/default_key_mapping.rst:246
msgid "Redo"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:67
msgid ":kbd:`Ctrl + Shift + Z`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:67
msgid ":kbd:`Cmd + Shift + Z`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:67
msgid "``editor/redo``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:69
msgid "Quit"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:69
msgid ":kbd:`Ctrl + Q`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:69
msgid ":kbd:`Cmd + Q`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:69
msgid "``editor/file_quit``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:71
msgid "Quit to Project List"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:71
msgid ":kbd:`Ctrl + Shift + Q`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:71
msgid ":kbd:`Shift + Alt + Q`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:71
msgid "``editor/quit_to_project_list``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:73
msgid "Take Screenshot"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:73
msgid ":kbd:`Ctrl + F12`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:73
msgid ":kbd:`Cmd + F12`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:73
msgid "``editor/take_screenshot``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:75
msgid "Toggle Fullscreen"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:75
msgid ":kbd:`Shift + F11`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:75
msgid ":kbd:`Cmd + Ctrl + F`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:75
msgid "``editor/fullscreen_mode``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:77
msgid "Play"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:77
#: ../../docs/tutorials/editor/default_key_mapping.rst:382
msgid ":kbd:`F5`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:77
#: ../../docs/tutorials/editor/default_key_mapping.rst:280
msgid ":kbd:`Cmd + B`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:77
msgid "``editor/play``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:79
msgid "Pause Scene"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:79
msgid ":kbd:`F7`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:79
msgid ":kbd:`Cmd + Ctrl + Y`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:79
msgid "``editor/pause_scene``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:81
msgid "Stop"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:81
msgid ":kbd:`F8`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:81
#: ../../docs/tutorials/editor/default_key_mapping.rst:292
msgid ":kbd:`Cmd + .`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:81
msgid "``editor/stop``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:83
msgid "Play Scene"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:83
msgid ":kbd:`F6`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:83
msgid ":kbd:`Cmd + R`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:83
msgid "``editor/play_scene``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:85
msgid "Play Custom Scene"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:85
msgid ":kbd:`Ctrl + Shift + F5`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:85
#: ../../docs/tutorials/editor/default_key_mapping.rst:242
#: ../../docs/tutorials/editor/default_key_mapping.rst:327
msgid ":kbd:`Cmd + Shift + R`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:85
msgid "``editor/play_custom_scene``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:87
msgid "Expand Bottom Panel"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:87
msgid ":kbd:`Shift + F12`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:87
msgid "``editor/bottom_panel_expand``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:91
msgid "2D / Canvas Item Editor"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:96
#: ../../docs/tutorials/editor/default_key_mapping.rst:339
msgid "Zoom In"
msgstr "Uveličaj"

#: ../../docs/tutorials/editor/default_key_mapping.rst:96
#: ../../docs/tutorials/editor/default_key_mapping.rst:339
msgid ":kbd:`Ctrl + =`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:96
#: ../../docs/tutorials/editor/default_key_mapping.rst:339
msgid ":kbd:`Cmd + =`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:96
msgid "``canvas_item_editor/zoom_plus``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:98
#: ../../docs/tutorials/editor/default_key_mapping.rst:341
msgid "Zoom Out"
msgstr "Umanji"

#: ../../docs/tutorials/editor/default_key_mapping.rst:98
#: ../../docs/tutorials/editor/default_key_mapping.rst:341
msgid ":kbd:`Ctrl + -`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:98
#: ../../docs/tutorials/editor/default_key_mapping.rst:341
msgid ":kbd:`Cmd + -`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:98
msgid "``canvas_item_editor/zoom_minus``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:100
msgid "Zoom Reset"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:100
#: ../../docs/tutorials/editor/default_key_mapping.rst:343
msgid ":kbd:`Ctrl + 0`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:100
#: ../../docs/tutorials/editor/default_key_mapping.rst:343
msgid ":kbd:`Cmd + 0`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:100
msgid "``canvas_item_editor/zoom_reset``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:102
msgid "Pan View"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:102
msgid ":kbd:`Space`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:102
msgid "``canvas_item_editor/pan_view``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:104
#: ../../docs/tutorials/editor/default_key_mapping.rst:167
msgid "Select Mode"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:104
#: ../../docs/tutorials/editor/default_key_mapping.rst:161
#: ../../docs/tutorials/editor/default_key_mapping.rst:167
msgid ":kbd:`Q`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:104
msgid "``canvas_item_editor/select_mode``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:106
#: ../../docs/tutorials/editor/default_key_mapping.rst:169
msgid "Move Mode"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:106
#: ../../docs/tutorials/editor/default_key_mapping.rst:155
#: ../../docs/tutorials/editor/default_key_mapping.rst:169
msgid ":kbd:`W`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:106
msgid "``canvas_item_editor/move_mode``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:108
#: ../../docs/tutorials/editor/default_key_mapping.rst:171
msgid "Rotate Mode"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:108
#: ../../docs/tutorials/editor/default_key_mapping.rst:159
#: ../../docs/tutorials/editor/default_key_mapping.rst:171
#: ../../docs/tutorials/editor/default_key_mapping.rst:482
msgid ":kbd:`E`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:108
msgid "``canvas_item_editor/rotate_mode``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:110
#: ../../docs/tutorials/editor/default_key_mapping.rst:173
msgid "Scale Mode"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:110
#: ../../docs/tutorials/editor/default_key_mapping.rst:157
#: ../../docs/tutorials/editor/default_key_mapping.rst:460
msgid ":kbd:`S`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:110
msgid "``canvas_item_editor/scale_mode``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:112
msgid "Ruler Mode"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:112
#: ../../docs/tutorials/editor/default_key_mapping.rst:173
#: ../../docs/tutorials/editor/default_key_mapping.rst:476
msgid ":kbd:`R`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:112
msgid "``canvas_item_editor/ruler_mode``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:114
msgid "Use Smart Snap"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:114
msgid ":kbd:`Shift + S`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:114
msgid "``canvas_item_editor/use_smart_snap``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:116
msgid "Use Grid Snap"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:116
msgid ":kbd:`Shift + G`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:116
msgid "``canvas_item_editor/use_grid_snap``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:118
msgid "Multiply grid step by 2"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:118
msgid ":kbd:`Num *`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:118
msgid "``canvas_item_editor/multiply_grid_step``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:120
msgid "Divide grid step by 2"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:120
msgid ":kbd:`Num /`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:120
msgid "``canvas_item_editor/divide_grid_step``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:122
msgid "Always Show Grid"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:122
msgid ":kbd:`G`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:122
msgid "``canvas_item_editor/show_grid``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:124
msgid "Show Helpers"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:124
msgid ":kbd:`H`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:124
msgid "``canvas_item_editor/show_helpers``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:126
msgid "Show Guides"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:126
#: ../../docs/tutorials/editor/default_key_mapping.rst:177
msgid ":kbd:`Y`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:126
msgid "``canvas_item_editor/show_guides``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:128
msgid "Center Selection"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:128
#: ../../docs/tutorials/editor/default_key_mapping.rst:199
msgid ":kbd:`F`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:128
msgid "``canvas_item_editor/center_selection``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:130
msgid "Frame Selection"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:130
#: ../../docs/tutorials/editor/default_key_mapping.rst:149
msgid ":kbd:`Shift + F`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:130
msgid "``canvas_item_editor/frame_selection``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:132
msgid "Preview Canvas Scale"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:132
msgid ":kbd:`Ctrl + Shift + P`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:132
msgid ":kbd:`Cmd + Shift + P`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:132
msgid "``canvas_item_editor/preview_canvas_scale``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:134
msgid "Insert Key"
msgstr "Unesi Ključ"

#: ../../docs/tutorials/editor/default_key_mapping.rst:134
msgid ":kbd:`Ins`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:134
msgid "``canvas_item_editor/anim_insert_key``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:136
msgid "Insert Key (Existing Tracks)"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:136
msgid ":kbd:`Ctrl + Ins`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:136
msgid ":kbd:`Cmd + Ins`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:136
msgid "``canvas_item_editor/anim_insert_key_existing_tracks``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:138
msgid "Make Custom Bones from Nodes"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:138
#: ../../docs/tutorials/editor/default_key_mapping.rst:282
msgid ":kbd:`Ctrl + Shift + B`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:138
#: ../../docs/tutorials/editor/default_key_mapping.rst:282
#: ../../docs/tutorials/editor/default_key_mapping.rst:288
msgid ":kbd:`Cmd + Shift + B`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:138
msgid "``canvas_item_editor/skeleton_make_bones``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:140
msgid "Clear Pose"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:140
msgid ":kbd:`Shift + K`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:140
msgid "``canvas_item_editor/anim_clear_pose``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:144
msgid "3D / Spatial Editor"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:149
msgid "Toggle Freelook"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:149
msgid "``spatial_editor/freelook_toggle``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:151
msgid "Freelook Left"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:151
msgid ":kbd:`A`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:151
msgid "``spatial_editor/freelook_left``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:153
msgid "Freelook Right"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:153
#: ../../docs/tutorials/editor/default_key_mapping.rst:472
msgid ":kbd:`D`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:153
msgid "``spatial_editor/freelook_right``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:155
msgid "Freelook Forward"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:155
msgid "``spatial_editor/freelook_forward``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:157
msgid "Freelook Backwards"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:157
msgid "``spatial_editor/freelook_backwards``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:159
msgid "Freelook Up"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:159
msgid "``spatial_editor/freelook_up``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:161
msgid "Freelook Down"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:161
msgid "``spatial_editor/freelook_down``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:163
msgid "Freelook Speed Modifier"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:163
msgid ":kbd:`Shift`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:163
msgid "``spatial_editor/freelook_speed_modifier``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:165
msgid "Freelook Slow Modifier"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:165
msgid ":kbd:`Alt`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:165
msgid "``spatial_editor/freelook_slow_modifier``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:167
msgid "``spatial_editor/tool_select``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:169
msgid "``spatial_editor/tool_move``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:171
msgid "``spatial_editor/tool_rotate``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:173
msgid "``spatial_editor/tool_scale``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:175
msgid "Use Local Space"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:175
msgid ":kbd:`T`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:175
msgid "``spatial_editor/local_coords``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:177
msgid "Use Snap"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:177
msgid "``spatial_editor/snap``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:179
msgid "Snap Object to Floor"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:179
#: ../../docs/tutorials/editor/default_key_mapping.rst:499
msgid ":kbd:`PgDown`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:179
msgid "``spatial_editor/snap_to_floor``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:181
msgid "Top View"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:181
msgid ":kbd:`Num 7`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:181
msgid "``spatial_editor/top_view``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:183
msgid "Bottom View"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:183
msgid ":kbd:`Alt + Num 7`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:183
msgid "``spatial_editor/bottom_view``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:185
msgid "Front View"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:185
msgid ":kbd:`Num 1`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:185
msgid "``spatial_editor/front_view``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:187
msgid "Rear View"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:187
msgid ":kbd:`Alt + Num 1`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:187
msgid "``spatial_editor/rear_view``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:189
msgid "Right View"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:189
msgid ":kbd:`Num 3`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:189
msgid "``spatial_editor/right_view``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:191
msgid "Left View"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:191
msgid ":kbd:`Alt + Num 3`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:191
msgid "``spatial_editor/left_view``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:193
msgid "Switch Perspective/Orthogonal View"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:193
msgid ":kbd:`Num 5`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:193
msgid "``spatial_editor/switch_perspective_orthogonal``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:195
msgid "Insert Animation Key"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:195
msgid ":kbd:`K`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:195
msgid "``spatial_editor/insert_anim_key``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:197
msgid "Focus Origin"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:197
msgid ":kbd:`O`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:197
msgid "``spatial_editor/focus_origin``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:199
msgid "Focus Selection"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:199
msgid "``spatial_editor/focus_selection``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:201
msgid "Align Transform with View"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:201
msgid ":kbd:`Ctrl + Alt + M`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:201
msgid ":kbd:`Cmd + Alt + M`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:201
msgid "``spatial_editor/align_transform_with_view``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:203
msgid "Align Rotation with View"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:203
#: ../../docs/tutorials/editor/default_key_mapping.rst:284
msgid ":kbd:`Ctrl + Alt + F`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:203
msgid ":kbd:`Cmd + Alt + F`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:203
msgid "``spatial_editor/align_rotation_with_view``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:205
msgid "1 Viewport"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:205
msgid ":kbd:`Ctrl + 1`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:205
msgid ":kbd:`Cmd + 1`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:205
msgid "``spatial_editor/1_viewport``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:207
msgid "2 Viewports"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:207
msgid ":kbd:`Ctrl + 2`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:207
msgid ":kbd:`Cmd + 2`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:207
msgid "``spatial_editor/2_viewports``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:209
msgid "2 Viewports (Alt)"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:209
msgid ":kbd:`Ctrl + Alt + 2`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:209
msgid ":kbd:`Cmd + Alt + 2`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:209
msgid "``spatial_editor/2_viewports_alt``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:211
msgid "3 Viewports"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:211
msgid ":kbd:`Ctrl + 3`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:211
msgid ":kbd:`Cmd + 3`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:211
msgid "``spatial_editor/3_viewports``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:213
msgid "3 Viewports (Alt)"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:213
msgid ":kbd:`Ctrl + Alt + 3`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:213
msgid ":kbd:`Cmd + Alt + 3`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:213
msgid "``spatial_editor/3_viewports_alt``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:215
msgid "4 Viewports"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:215
msgid ":kbd:`Ctrl + 4`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:215
msgid ":kbd:`Cmd + 4`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:215
msgid "``spatial_editor/4_viewports``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:219
#, fuzzy
msgid "Text Editor"
msgstr "Tutorijali"

#: ../../docs/tutorials/editor/default_key_mapping.rst:224
msgid "Cut"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:224
#: ../../docs/tutorials/editor/default_key_mapping.rst:462
msgid ":kbd:`Ctrl + X`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:224
#: ../../docs/tutorials/editor/default_key_mapping.rst:462
msgid ":kbd:`Cmd + X`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:224
msgid "``script_text_editor/cut``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:226
msgid "Copy"
msgstr "Kopiraj"

#: ../../docs/tutorials/editor/default_key_mapping.rst:226
#: ../../docs/tutorials/editor/default_key_mapping.rst:352
#: ../../docs/tutorials/editor/default_key_mapping.rst:407
#: ../../docs/tutorials/editor/default_key_mapping.rst:464
msgid ":kbd:`Ctrl + C`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:226
#: ../../docs/tutorials/editor/default_key_mapping.rst:352
#: ../../docs/tutorials/editor/default_key_mapping.rst:407
#: ../../docs/tutorials/editor/default_key_mapping.rst:464
msgid ":kbd:`Cmd + C`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:226
msgid "``script_text_editor/copy``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:228
msgid "Paste"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:228
#: ../../docs/tutorials/editor/default_key_mapping.rst:466
msgid ":kbd:`Ctrl + V`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:228
#: ../../docs/tutorials/editor/default_key_mapping.rst:466
msgid ":kbd:`Cmd + V`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:228
msgid "``script_text_editor/paste``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:230
msgid "Select All"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:230
#: ../../docs/tutorials/editor/default_key_mapping.rst:420
msgid ":kbd:`Ctrl + A`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:230
#: ../../docs/tutorials/editor/default_key_mapping.rst:420
msgid ":kbd:`Cmd + A`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:230
msgid "``script_text_editor/select_all``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:232
#: ../../docs/tutorials/editor/default_key_mapping.rst:305
msgid "Find"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:232
#: ../../docs/tutorials/editor/default_key_mapping.rst:305
msgid ":kbd:`Ctrl + F`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:232
#: ../../docs/tutorials/editor/default_key_mapping.rst:305
msgid ":kbd:`Cmd + F`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:232
msgid "``script_text_editor/find``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:234
#: ../../docs/tutorials/editor/default_key_mapping.rst:307
msgid "Find Next"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:234
#: ../../docs/tutorials/editor/default_key_mapping.rst:307
msgid ":kbd:`F3`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:234
msgid ":kbd:`Cmd + G`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:234
msgid "``script_text_editor/find_next``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:236
#: ../../docs/tutorials/editor/default_key_mapping.rst:309
msgid "Find Previous"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:236
#: ../../docs/tutorials/editor/default_key_mapping.rst:309
msgid ":kbd:`Shift + F3`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:236
msgid ":kbd:`Cmd + Shift + G`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:236
msgid "``script_text_editor/find_previous``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:238
#: ../../docs/tutorials/editor/default_key_mapping.rst:311
#, fuzzy
msgid "Find in Files"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/editor/default_key_mapping.rst:238
#: ../../docs/tutorials/editor/default_key_mapping.rst:311
msgid ":kbd:`Ctrl + Shift + F`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:238
#: ../../docs/tutorials/editor/default_key_mapping.rst:311
msgid ":kbd:`Cmd + Shift + F`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:238
msgid "``script_text_editor/find_in_files``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:240
msgid "Replace"
msgstr "Zameni"

#: ../../docs/tutorials/editor/default_key_mapping.rst:240
msgid ":kbd:`Ctrl + R`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:240
msgid ":kbd:`Alt + Cmd + F`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:240
msgid "``script_text_editor/replace``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:242
msgid "Replace in Files"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:242
#: ../../docs/tutorials/editor/default_key_mapping.rst:327
msgid ":kbd:`Ctrl + Shift + R`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:242
msgid "``script_text_editor/replace_in_files``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:244
msgid "``script_text_editor/undo``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:246
msgid ":kbd:`Ctrl + Y`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:246
msgid ":kbd:`Cmd + Y`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:246
msgid "``script_text_editor/redo``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:248
#: ../../docs/tutorials/editor/default_key_mapping.rst:313
#: ../../docs/tutorials/editor/default_key_mapping.rst:432
msgid "Move Up"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:248
#: ../../docs/tutorials/editor/default_key_mapping.rst:380
msgid ":kbd:`Alt + Up Arrow`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:248
msgid "``script_text_editor/move_up``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:250
#: ../../docs/tutorials/editor/default_key_mapping.rst:315
#: ../../docs/tutorials/editor/default_key_mapping.rst:434
msgid "Move Down"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:250
msgid ":kbd:`Alt + Down Arrow`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:250
msgid "``script_text_editor/move_down``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:252
msgid "Delete Line"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:252
#: ../../docs/tutorials/editor/default_key_mapping.rst:354
msgid ":kbd:`Ctrl + Shift + K`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:252
#: ../../docs/tutorials/editor/default_key_mapping.rst:354
msgid ":kbd:`Cmd + Shift + K`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:252
msgid "``script_text_editor/delete_line``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:254
msgid "Toggle Comment"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:254
msgid ":kbd:`Ctrl + K`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:254
msgid ":kbd:`Cmd + K`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:254
msgid "``script_text_editor/toggle_comment``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:256
msgid "Fold/Unfold Line"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:256
#: ../../docs/tutorials/editor/default_key_mapping.rst:386
msgid ":kbd:`Alt + F`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:256
msgid ":kbd:`Ctrl + Cmd + F`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:256
msgid "``script_text_editor/toggle_fold_line``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:258
#: ../../docs/tutorials/editor/default_key_mapping.rst:443
msgid "Duplicate Selection"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:258
#: ../../docs/tutorials/editor/default_key_mapping.rst:445
msgid ":kbd:`Ctrl + Shift + D`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:258
msgid ":kbd:`Cmd + Shift + C`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:258
msgid "``script_text_editor/duplicate_selection``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:260
msgid "Complete Symbol"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:260
msgid ":kbd:`Ctrl + Space`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:260
msgid "``script_text_editor/complete_symbol``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:262
msgid "Evaluate Selection"
msgstr "Proceni Označeno"

#: ../../docs/tutorials/editor/default_key_mapping.rst:262
msgid ":kbd:`Ctrl + Shift + E`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:262
msgid ":kbd:`Cmd + Shift + E`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:262
msgid "``script_text_editor/evaluate_selection``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:264
msgid "Trim Trailing Whitespace"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:264
msgid ":kbd:`Ctrl + Alt + T`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:264
msgid ":kbd:`Cmd + Alt + T`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:264
msgid "``script_text_editor/trim_trailing_whitespace``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:266
msgid "Uppercase"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:266
msgid ":kbd:`Shift + F4`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:266
msgid "``script_text_editor/convert_to_uppercase``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:268
msgid "Lowercase"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:268
msgid ":kbd:`Shift + F5`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:268
msgid "``script_text_editor/convert_to_lowercase``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:270
msgid "Capitalize"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:270
msgid ":kbd:`Shift + F6`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:270
msgid "``script_text_editor/capitalize``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:272
msgid "Convert Indent to Spaces"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:272
msgid ":kbd:`Ctrl + Shift + Y`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:272
msgid ":kbd:`Cmd + Shift + Y`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:272
msgid "``script_text_editor/convert_indent_to_spaces``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:274
msgid "Convert Indent to Tabs"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:274
msgid ":kbd:`Ctrl + Shift + I`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:274
msgid ":kbd:`Cmd + Shift + I`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:274
msgid "``script_text_editor/convert_indent_to_tabs``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:276
msgid "Auto Indent"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:276
msgid ":kbd:`Ctrl + I`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:276
msgid ":kbd:`Cmd + I`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:276
msgid "``script_text_editor/auto_indent``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:278
msgid "Toggle Bookmark"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:278
msgid ":kbd:`Ctrl + Alt + B`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:278
msgid ":kbd:`Cmd + Alt + B`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:278
msgid "``script_text_editor/toggle_bookmark``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:280
msgid "Go to Next Bookmark"
msgstr "Idi na Sledeći Obeleživač"

#: ../../docs/tutorials/editor/default_key_mapping.rst:280
msgid ":kbd:`Ctrl + B`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:280
msgid "``script_text_editor/goto_next_bookmark``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:282
msgid "Go to Previous Bookmark"
msgstr "Idi na Prethodni Obeleživač"

#: ../../docs/tutorials/editor/default_key_mapping.rst:282
msgid "``script_text_editor/goto_previous_bookmark``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:284
#, fuzzy
msgid "Go to Function"
msgstr "Uvod"

#: ../../docs/tutorials/editor/default_key_mapping.rst:284
msgid ":kbd:`Ctrl + Cmd + J`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:284
msgid "``script_text_editor/goto_function``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:286
msgid "Go to Line"
msgstr "Idi na Liniju"

#: ../../docs/tutorials/editor/default_key_mapping.rst:286
msgid ":kbd:`Ctrl + L`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:286
msgid ":kbd:`Cmd + L`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:286
msgid "``script_text_editor/goto_line``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:288
msgid "Toggle Breakpoint"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:288
msgid ":kbd:`F9`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:288
msgid "``script_text_editor/toggle_breakpoint``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:290
msgid "Remove All Breakpoints"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:290
msgid ":kbd:`Ctrl + Shift + F9`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:290
msgid ":kbd:`Cmd + Shift + F9`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:290
msgid "``script_text_editor/remove_all_breakpoints``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:292
msgid "Go to Next Breakpoint"
msgstr "Idi na Sledeću Tačku Prekida"

#: ../../docs/tutorials/editor/default_key_mapping.rst:292
msgid ":kbd:`Ctrl + .`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:292
msgid "``script_text_editor/goto_next_breakpoint``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:294
msgid "Go to Previous Breakpoint"
msgstr "Idi na Prethodnu Tačku Prekida"

#: ../../docs/tutorials/editor/default_key_mapping.rst:294
msgid ":kbd:`Ctrl + ,`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:294
msgid ":kbd:`Cmd + ,`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:294
msgid "``script_text_editor/goto_previous_breakpoint``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:296
msgid "Contextual Help"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:296
msgid ":kbd:`Alt + F1`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:296
msgid ":kbd:`Alt + Shift + Space`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:296
msgid "``script_text_editor/contextual_help``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:300
msgid "Script Editor"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:305
msgid "``script_editor/find``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:307
msgid "``script_editor/find_next``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:309
msgid "``script_editor/find_previous``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:311
msgid "``script_editor/find_in_files``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:313
msgid ":kbd:`Shift + Alt + Up Arrow`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:313
msgid "``script_editor/window_move_up``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:315
msgid ":kbd:`Shift + Alt + Down Arrow`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:315
msgid "``script_editor/window_move_down``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:317
msgid "Next Script"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:317
msgid ":kbd:`Ctrl + Shift + .`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:317
msgid ":kbd:`Cmd + Shift + .`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:317
msgid "``script_editor/next_script``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:319
msgid "Previous Script"
msgstr "Prethodna Skripta"

#: ../../docs/tutorials/editor/default_key_mapping.rst:319
msgid ":kbd:`Ctrl + Shift + ,`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:319
msgid ":kbd:`Cmd + Shift + ,`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:319
msgid "``script_editor/prev_script``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:321
msgid "Reopen Closed Script"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:321
msgid "``script_editor/reopen_closed_script``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:323
msgid "Save"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:323
msgid ":kbd:`Ctrl + Alt + S`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:323
msgid ":kbd:`Cmd + Alt + S`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:323
msgid "``script_editor/save``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:325
msgid "Save All"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:325
msgid "``script_editor/save_all``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:327
msgid "Soft Reload Script"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:327
msgid "``script_editor/reload_script_soft``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:329
msgid "History Previous"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:329
#: ../../docs/tutorials/editor/default_key_mapping.rst:376
msgid ":kbd:`Alt + Left Arrow`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:329
msgid "``script_editor/history_previous``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:331
msgid "History Next"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:331
#: ../../docs/tutorials/editor/default_key_mapping.rst:378
msgid ":kbd:`Alt + Right Arrow`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:331
msgid "``script_editor/history_next``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:333
msgid "Close"
msgstr "Zatvori"

#: ../../docs/tutorials/editor/default_key_mapping.rst:333
msgid ":kbd:`Ctrl + W`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:333
msgid ":kbd:`Cmd + W`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:333
msgid "``script_editor/close_file``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:335
#: ../../docs/contributing/development/compiling/compiling_for_ios.rst:90
msgid "Run"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:335
msgid ":kbd:`Ctrl + Shift + X`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:335
msgid ":kbd:`Cmd + Shift + X`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:335
msgid "``script_editor/run_file``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:337
msgid "Toggle Scripts Panel"
msgstr "Uključi/Isključi Panel sa Skriptama"

#: ../../docs/tutorials/editor/default_key_mapping.rst:337
msgid ":kbd:`Ctrl + \\\\`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:337
msgid ":kbd:`Cmd + \\\\`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:337
msgid "``script_editor/toggle_scripts_panel``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:339
msgid "``script_editor/zoom_in``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:341
msgid "``script_editor/zoom_out``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:343
msgid "Reset Zoom"
msgstr "Resetuj Uveličavanje"

#: ../../docs/tutorials/editor/default_key_mapping.rst:343
msgid "``script_editor/reset_zoom``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:347
msgid "Editor Output"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:352
#: ../../docs/tutorials/editor/default_key_mapping.rst:464
msgid "Copy Selection"
msgstr "Kopiraj Označeno"

#: ../../docs/tutorials/editor/default_key_mapping.rst:352
msgid "``editor/copy_output``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:354
msgid "Clear Output"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:354
msgid "``editor/clear_output``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:358
#: ../../docs/tutorials/scripting/debug/debugger_panel.rst:14
msgid "Debugger"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:363
msgid "Step Into"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:363
msgid ":kbd:`F11`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:363
msgid "``debugger/step_into``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:365
msgid "Step Over"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:365
msgid ":kbd:`F10`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:365
msgid "``debugger/step_over``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:367
msgid "Continue"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:367
msgid ":kbd:`F12`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:367
msgid "``debugger/continue``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:371
msgid "File Dialog"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:376
msgid "Go Back"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:376
msgid "``file_dialog/go_back``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:378
msgid "Go Forward"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:378
msgid "``file_dialog/go_forward``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:380
msgid "Go Up"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:380
msgid "``file_dialog/go_up``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:382
msgid "Refresh"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:382
msgid "``file_dialog/refresh``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:384
msgid "Toggle Hidden Files"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:384
msgid ":kbd:`Ctrl + H`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:384
msgid ":kbd:`Cmd + H`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:384
msgid "``file_dialog/toggle_hidden_files``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:386
msgid "Toggle Favorite"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:386
msgid "``file_dialog/toggle_favorite``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:388
msgid "Toggle Mode"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:388
msgid ":kbd:`Alt + V`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:388
msgid "``file_dialog/toggle_mode``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:390
msgid "Create Folder"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:390
msgid ":kbd:`Ctrl + N`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:390
msgid ":kbd:`Cmd + N`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:390
msgid "``file_dialog/create_folder``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:392
#: ../../docs/tutorials/editor/default_key_mapping.rst:411
#: ../../docs/tutorials/editor/default_key_mapping.rst:426
msgid "Delete"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:392
#: ../../docs/tutorials/editor/default_key_mapping.rst:411
#: ../../docs/tutorials/editor/default_key_mapping.rst:426
#: ../../docs/tutorials/editor/default_key_mapping.rst:447
#: ../../docs/tutorials/editor/default_key_mapping.rst:468
msgid ":kbd:`Del`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:392
#: ../../docs/tutorials/editor/default_key_mapping.rst:411
#: ../../docs/tutorials/editor/default_key_mapping.rst:426
#: ../../docs/tutorials/editor/default_key_mapping.rst:447
#: ../../docs/tutorials/editor/default_key_mapping.rst:468
msgid ":kbd:`Cmd + BkSp`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:392
msgid "``file_dialog/delete``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:394
msgid "Focus Path"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:394
#: ../../docs/tutorials/editor/default_key_mapping.rst:409
#: ../../docs/tutorials/editor/default_key_mapping.rst:430
#: ../../docs/tutorials/editor/default_key_mapping.rst:443
msgid ":kbd:`Ctrl + D`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:394
#: ../../docs/tutorials/editor/default_key_mapping.rst:409
#: ../../docs/tutorials/editor/default_key_mapping.rst:430
#: ../../docs/tutorials/editor/default_key_mapping.rst:443
msgid ":kbd:`Cmd + D`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:394
msgid "``file_dialog/focus_path``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:396
msgid "Move Favorite Up"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:396
#: ../../docs/tutorials/editor/default_key_mapping.rst:432
msgid ":kbd:`Ctrl + Up Arrow`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:396
#: ../../docs/tutorials/editor/default_key_mapping.rst:432
msgid ":kbd:`Cmd + Up Arrow`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:396
msgid "``file_dialog/move_favorite_up``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:398
msgid "Move Favorite Down"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:398
#: ../../docs/tutorials/editor/default_key_mapping.rst:434
msgid ":kbd:`Ctrl + Down Arrow`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:398
#: ../../docs/tutorials/editor/default_key_mapping.rst:434
msgid ":kbd:`Cmd + Down Arrow`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:398
msgid "``file_dialog/move_favorite_down``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:402
msgid "FileSystem Dock"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:407
msgid "Copy Path"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:407
msgid "``filesystem_dock/copy_path``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:409
#: ../../docs/tutorials/editor/default_key_mapping.rst:430
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:130
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:219
msgid "Duplicate"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:409
msgid "``filesystem_dock/duplicate``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:411
msgid "``filesystem_dock/delete``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:415
msgid "Scene Tree Dock"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:420
msgid "Add Child Node"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:420
msgid "``scene_tree/add_child_node``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:422
msgid "Batch Rename"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:422
msgid ":kbd:`Cmd + F2`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:422
msgid "``scene_tree/batch_rename``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:424
msgid "Copy Node Path"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:424
msgid ":kbd:`Ctrl + Shift + C`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:424
msgid ":kbd:`Cmd + Shift +  C`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:424
msgid "``scene_tree/copy_node_path``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:426
msgid "``scene_tree/delete``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:428
msgid "Force Delete"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:428
msgid ":kbd:`Shift + Del`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:428
msgid "``scene_tree/delete_no_confirm``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:430
msgid "``scene_tree/duplicate``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:432
msgid "``scene_tree/move_up``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:434
msgid "``scene_tree/move_down``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:438
msgid "Animation Track Editor"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:443
msgid "``animation_editor/duplicate_selection``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:445
msgid "Duplicate Transposed"
msgstr "Dupliraj Transponovanu"

#: ../../docs/tutorials/editor/default_key_mapping.rst:445
msgid ":kbd:`Cmd + Shift + D`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:445
msgid "``animation_editor/duplicate_selection_transposed``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:447
#: ../../docs/tutorials/editor/default_key_mapping.rst:468
msgid "Delete Selection"
msgstr "Ukloni oznaku"

#: ../../docs/tutorials/editor/default_key_mapping.rst:447
msgid "``animation_editor/delete_selection``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:449
msgid "Go to Next Step"
msgstr "Idi na Sledeći Korak"

#: ../../docs/tutorials/editor/default_key_mapping.rst:449
msgid ":kbd:`Ctrl + Right Arrow`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:449
msgid ":kbd:`Cmd + Right Arrow`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:449
msgid "``animation_editor/goto_next_step``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:451
msgid "Go to Previous Step"
msgstr "Idi na Prethodni Korak"

#: ../../docs/tutorials/editor/default_key_mapping.rst:451
msgid ":kbd:`Ctrl + Left Arrow`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:451
msgid ":kbd:`Cmd + Left Arrow`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:451
msgid "``animation_editor/goto_prev_step``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:455
msgid "Tile Map Editor"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:460
msgid "Select"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:460
msgid "``tiles_editor/selection_tool``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:462
msgid "Cut Selection"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:462
msgid "``tiles_editor/cut``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:464
msgid "``tiles_editor/copy``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:466
#, fuzzy
msgid "Paste Selection"
msgstr "Proceni Označeno"

#: ../../docs/tutorials/editor/default_key_mapping.rst:466
msgid "``tiles_editor/paste``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:468
msgid "``tiles_editor/delete``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:470
msgid "Cancel"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:470
msgid ":kbd:`Esc`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:470
msgid "``tiles_editor/cancel``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:472
#: ../../docs/tutorials/2d/using_tilemaps.rst:209
msgid "Paint"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:472
msgid "``tiles_editor/paint_tool``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:474
#: ../../docs/tutorials/2d/using_tilemaps.rst:238
msgid "Line"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:474
msgid ":kbd:`L`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:474
msgid "``tiles_editor/line_tool``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:476
msgid "Rect"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:476
msgid "``tiles_editor/rect_tool``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:478
msgid "Bucket"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:478
msgid ":kbd:`B`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:478
msgid "``tiles_editor/bucket_tool``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:480
#: ../../docs/tutorials/2d/using_tilemaps.rst:301
msgid "Picker"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:480
msgid ":kbd:`P`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:480
msgid "``tiles_editor/picker``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:482
#: ../../docs/tutorials/2d/using_tilemaps.rst:313
msgid "Eraser"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:482
msgid "``tiles_editor/eraser``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:484
msgid "Flip Horizontally"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:484
msgid ":kbd:`C`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:484
msgid "``tiles_editor/flip_tile_horizontal``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:486
msgid "Flip Vertically"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:486
msgid ":kbd:`V`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:486
msgid "``tiles_editor/flip_tile_vertical``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:488
msgid "Rotate Left"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:488
msgid ":kbd:`Z`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:488
msgid "``tiles_editor/rotate_tile_left``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:490
msgid "Rotate Right"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:490
msgid ":kbd:`X`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:490
msgid "``tiles_editor/rotate_tile_right``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:494
msgid "Tileset Editor"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:499
msgid "Next Coordinate"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:499
msgid "``tileset_editor/next_shape``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:501
msgid "Previous Coordinate"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:501
msgid ":kbd:`PgUp`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:501
msgid "``tileset_editor/previous_shape``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:503
msgid "Region Mode"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:503
msgid ":kbd:`1`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:503
msgid "``tileset_editor/editmode_region``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:505
msgid "Collision Mode"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:505
msgid ":kbd:`2`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:505
msgid "``tileset_editor/editmode_collision``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:507
msgid "Occlusion Mode"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:507
msgid ":kbd:`3`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:507
msgid "``tileset_editor/editmode_occlusion``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:509
msgid "Navigation Mode"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:509
msgid ":kbd:`4`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:509
msgid "``tileset_editor/editmode_navigation``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:511
msgid "Bitmask Mode"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:511
msgid ":kbd:`5`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:511
msgid "``tileset_editor/editmode_bitmask``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:513
msgid "Priority Mode"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:513
msgid ":kbd:`6`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:513
msgid "``tileset_editor/editmode_priority``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:515
msgid "Icon Mode"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:515
msgid ":kbd:`7`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:515
msgid "``tileset_editor/editmode_icon``"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:517
msgid "Z Index Mode"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:517
msgid ":kbd:`8`"
msgstr ""

#: ../../docs/tutorials/editor/default_key_mapping.rst:517
msgid "``tileset_editor/editmode_z_index``"
msgstr ""

#: ../../docs/tutorials/editor/customizing_editor.rst:4
#, fuzzy
msgid "Customizing the interface"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/editor/customizing_editor.rst:6
msgid ""
"Godot's interface lives in a single window by default. Since Godot 4.0, you "
"can split several elements to separate windows to better make use of multi-"
"monitor setups."
msgstr ""

#: ../../docs/tutorials/editor/customizing_editor.rst:11
msgid "Moving and resizing docks"
msgstr ""

#: ../../docs/tutorials/editor/customizing_editor.rst:13
msgid ""
"Click and drag on the edge of any dock or panel to resize it horizontally or "
"vertically:"
msgstr ""

#: ../../docs/tutorials/editor/customizing_editor.rst:20
#, fuzzy
msgid "Resizing a dock in the editor"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/editor/customizing_editor.rst:22
msgid ""
"Click the \"3 vertical dots\" icon at the top of any dock to change its "
"location, or split it to a separate window by choosing **Make Floating** in "
"the submenu that appears:"
msgstr ""

#: ../../docs/tutorials/editor/customizing_editor.rst:29
#, fuzzy
msgid "Moving a dock in the editor"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/editor/customizing_editor.rst:31
msgid ""
"To move a floating dock back to the editor window, close the dock window "
"using the **×** button in the top-right corner of the window (or in the top-"
"left corner on macOS). Alternatively, you can press :kbd:`Alt + F4` while "
"the split window is focused."
msgstr ""

#: ../../docs/tutorials/editor/customizing_editor.rst:43
msgid "Splitting the script or shader editor to its own window"
msgstr ""

#: ../../docs/tutorials/editor/customizing_editor.rst:47
msgid ""
"This feature is only available on platforms that support spawning multiple "
"windows: Windows, macOS and Linux."
msgstr ""

#: ../../docs/tutorials/editor/customizing_editor.rst:50
msgid ""
"This feature is also not available if **Single Window Mode** is enabled in "
"the Editor Settings."
msgstr ""

#: ../../docs/tutorials/editor/customizing_editor.rst:53
msgid ""
"Since Godot 4.1, you can split the script or shader editor to its own window."
msgstr ""

#: ../../docs/tutorials/editor/customizing_editor.rst:55
msgid ""
"To split the script editor to its own window, click the corresponding button "
"in the top-right corner of the script editor:"
msgstr ""

#: ../../docs/tutorials/editor/customizing_editor.rst:62
msgid "Splitting the script editor to its own window"
msgstr ""

#: ../../docs/tutorials/editor/customizing_editor.rst:64
msgid ""
"To split the shader editor to its own window, click the corresponding button "
"in the top-right corner of the script editor:"
msgstr ""

#: ../../docs/tutorials/editor/customizing_editor.rst:71
msgid "Splitting the shader editor to its own window"
msgstr ""

#: ../../docs/tutorials/editor/customizing_editor.rst:73
msgid ""
"To go back to the previous state (with the script/shader editor embedded in "
"the editor window), close the split window using the **×** button in the top-"
"right corner of the window (or in the top-left corner on macOS). "
"Alternatively, you can press :kbd:`Alt + F4` while the split window is "
"focused."
msgstr ""

#: ../../docs/tutorials/editor/customizing_editor.rst:79
#, fuzzy
msgid "Customizing editor layouts"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/editor/customizing_editor.rst:81
msgid ""
"You may want to save and load a dock configuration depending on the kind of "
"task you're working on. For instance, when working on animating a character, "
"it may be more convenient to have docks laid out in a different fashion "
"compared to when you're designing a level."
msgstr ""

#: ../../docs/tutorials/editor/customizing_editor.rst:86
msgid ""
"For this purpose, Godot provides a way to save and restore editor layouts. "
"Before saving a layout, make changes to the docks you'd like to save. The "
"following changes are persisted to the saved layout:"
msgstr ""

#: ../../docs/tutorials/editor/customizing_editor.rst:90
msgid "Moving a dock."
msgstr ""

#: ../../docs/tutorials/editor/customizing_editor.rst:91
msgid "Resizing a dock."
msgstr ""

#: ../../docs/tutorials/editor/customizing_editor.rst:92
msgid "Making a dock floating."
msgstr ""

#: ../../docs/tutorials/editor/customizing_editor.rst:93
msgid "Changing a floating dock's position or size."
msgstr ""

#: ../../docs/tutorials/editor/customizing_editor.rst:94
msgid ""
"FileSystem dock properties: split mode, display mode, sorting order, file "
"list display mode, selected paths and unfolded paths."
msgstr ""

#: ../../docs/tutorials/editor/customizing_editor.rst:99
msgid ""
"Splitting the script or shader editor to its own window is *not* persisted "
"as part of a layout."
msgstr ""

#: ../../docs/tutorials/editor/customizing_editor.rst:102
msgid ""
"After making changes, open the **Editor** menu at the top of the editor then "
"choose **Editor Layouts > Save**. Enter a name for the layout, then click "
"**Save**. If you've already saved an editor layout, you can choose to "
"override an existing layout using the list."
msgstr ""

#: ../../docs/tutorials/editor/customizing_editor.rst:107
msgid ""
"After making changes, open the **Editor** menu at the top of the editor then "
"choose **Editor Layouts**. In the dropdown list, you will see a list of "
"saved editor layouts, plus **Default** which is a hardcoded editor layout "
"that can't be removed. The default layout matches a fresh Godot installation "
"with no changes made to the docks' position and size, and no floating docks."
msgstr ""

#: ../../docs/tutorials/editor/customizing_editor.rst:113
msgid ""
"You can remove a layout using the **Delete** option in the **Editor "
"Layouts** dropdown."
msgstr ""

#: ../../docs/tutorials/editor/customizing_editor.rst:118
msgid ""
"If you name the saved layout ``Default`` (case-sensitive), the default "
"editor layout will be overwritten. Note that the ``Default`` does not appear "
"in the list of layouts to overwrite until you overwrite it once, but you can "
"still write its name manually."
msgstr ""

#: ../../docs/tutorials/editor/customizing_editor.rst:123
msgid ""
"You can go back to the standard default layout by removing the ``Default`` "
"layout after overriding it. (This option does not appear if you haven't "
"overridden the default layout yet.)"
msgstr ""

#: ../../docs/tutorials/editor/customizing_editor.rst:127
msgid ""
"Editor layouts are saved to a file named ``editor_layouts.cfg`` in the "
"configuration path of the :ref:`doc_data_paths_editor_data_paths`."
msgstr ""

#: ../../docs/tutorials/editor/customizing_editor.rst:131
#, fuzzy
msgid "Customizing editor settings"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/editor/customizing_editor.rst:133
msgid ""
"In the **Editor** menu at the top of the editor, you can find an **Editor "
"Settings** option. This opens a window similar to the Project Settings, but "
"with settings used by the editor. These settings are shared across all "
"projects and are not saved in the project files."
msgstr ""

#: ../../docs/tutorials/editor/customizing_editor.rst:142
#, fuzzy
msgid "The Editor Settings window"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/editor/customizing_editor.rst:144
msgid "Some commonly changed settings are:"
msgstr ""

#: ../../docs/tutorials/editor/customizing_editor.rst:146
msgid ""
"**Interface > Editor > Editor Language:** Controls the language the editor "
"displays in. To make English tutorials easier to follow, you may want to "
"change this to English so that menu names are identical to names referred to "
"by tutorials. The language can also be changed in the top-right corner of "
"the project manager."
msgstr ""

#: ../../docs/tutorials/editor/customizing_editor.rst:151
msgid ""
"**Interface > Editor > Display Scale:** Controls how large UI elements "
"display on screen. The default **Auto** setting finds a suitable value based "
"on your display's DPI and resolution. Due to engine limitations, it only "
"takes the display-provided scaling factor on macOS, not on Windows or Linux."
msgstr ""

#: ../../docs/tutorials/editor/customizing_editor.rst:155
msgid ""
"**Interface > Editor > Single Window Mode:** If enabled, this forces the "
"editor to use a single window. This disables certain features such as "
"splitting the script/shaders editor to their own window. Single-window mode "
"can be more stable, especially on Linux when using Wayland."
msgstr ""

#: ../../docs/tutorials/editor/customizing_editor.rst:159
msgid ""
"**Interface > Theme > Preset:** The editor theme preset to use. The "
"**Light** theme preset may be easier to read if you're outdoors or in a room "
"with sunlight. The **Black (OLED)** preset can reduce power consumption on "
"OLED displays, which are increasingly common in laptops and phones/tablets."
msgstr ""

#: ../../docs/tutorials/editor/customizing_editor.rst:163
msgid ""
"**FileSystem > Directories > Autoscan Project Path:** This can be set to a "
"folder path that will be automatically scanned for projects in the project "
"manager every time it starts."
msgstr ""

#: ../../docs/tutorials/editor/customizing_editor.rst:166
msgid ""
"**FileSystem > Directories > Default Project Path:** Controls the default "
"location where new projects are created in the project manager."
msgstr ""

#: ../../docs/tutorials/editor/customizing_editor.rst:168
msgid ""
"**Editors > 3D > Emulate Numpad:** This allows using the top row 0-9 keys in "
"the 3D editor as their equivalent numpad keys. It's recommended to enable "
"this option if you don't have a number pad on your keyboard."
msgstr ""

#: ../../docs/tutorials/editor/customizing_editor.rst:171
msgid ""
"**Editors > 3D > Emulate 3 Button Mouse:** This allows using the pan, zoom "
"and orbit modifiers in the 3D editor even when not holding down any mouse "
"button. It's recommended to enable this option if you're using a trackpad."
msgstr ""

#: ../../docs/tutorials/editor/customizing_editor.rst:175
msgid ""
"See the :ref:`class_EditorSettings` class reference for a complete "
"description of most editor settings. You can also hover an editor setting's "
"name with the mouse in the Editor Settings to show its description."
msgstr ""

#: ../../docs/tutorials/editor/using_the_android_editor.rst:4
#, fuzzy
msgid "Using the Android editor"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/editor/using_the_android_editor.rst:6
msgid ""
"In 2023, `we added <https://godotengine.org/article/"
"android_godot_editor_play_store_beta_release/>`__ a `Android port of the "
"editor <https://godotengine.org/download/android/>`__ that can be used to "
"work on new or existing projects on Android devices."
msgstr ""

#: ../../docs/tutorials/editor/using_the_android_editor.rst:12
msgid ""
"The Android editor is in beta testing stage, while we continue to refine the "
"experience, and bring it up to parity with the Desktop version of the "
"editor. See :ref:`doc_using_the_android_editor_limitations` below."
msgstr ""

#: ../../docs/tutorials/editor/using_the_android_editor.rst:16
msgid "Android devices support"
msgstr ""

#: ../../docs/tutorials/editor/using_the_android_editor.rst:18
msgid ""
"The Android editor requires devices running Android 5 Lollipop or higher, "
"with at least OpenGL 3 support. This includes (not exhaustive):"
msgstr ""

#: ../../docs/tutorials/editor/using_the_android_editor.rst:20
msgid "Android tablets, foldables and large phones"
msgstr ""

#: ../../docs/tutorials/editor/using_the_android_editor.rst:21
msgid "Android-powered netbooks"
msgstr ""

#: ../../docs/tutorials/editor/using_the_android_editor.rst:22
#, fuzzy
msgid "Chromebooks supporting Android apps"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/editor/using_the_android_editor.rst:27
msgid "Required Permissions"
msgstr ""

#: ../../docs/tutorials/editor/using_the_android_editor.rst:29
msgid ""
"The Android editor requires the `All files access permission <https://"
"developer.android.com/training/data-storage/manage-all-files#all-files-"
"access>`__. The permission allows the editor to create / import / read "
"project files from any file locations on the device. Without the permission, "
"the editor is still functional, but has limited access to the device's files "
"and directories."
msgstr ""

#: ../../docs/tutorials/editor/using_the_android_editor.rst:34
msgid "Limitations & known issues"
msgstr ""

#: ../../docs/tutorials/editor/using_the_android_editor.rst:36
msgid "Here are the known limitations and issues of the Android editor:"
msgstr ""

#: ../../docs/tutorials/editor/using_the_android_editor.rst:38
msgid "No C#/Mono support"
msgstr ""

#: ../../docs/tutorials/editor/using_the_android_editor.rst:39
msgid "No support for external script editors"
msgstr ""

#: ../../docs/tutorials/editor/using_the_android_editor.rst:40
msgid ""
"While available, the *Vulkan Forward+* renderer is not recommended due to "
"severe performance issues"
msgstr ""

#: ../../docs/tutorials/editor/using_the_android_editor.rst:41
msgid ""
"No support for building and exporting an Android APK binary. As a "
"workaround, you can generate and export a `Godot PCK or ZIP file <https://"
"docs.godotengine.org/en/stable/tutorials/export/exporting_projects.html#pck-"
"versus-zip-pack-file-formats>`__"
msgstr ""

#: ../../docs/tutorials/editor/using_the_android_editor.rst:43
msgid "No support for building and exporting binaries for other platforms"
msgstr ""

#: ../../docs/tutorials/editor/using_the_android_editor.rst:44
msgid ""
"Performance and stability issues when using the *Vulkan Mobile* renderer for "
"a project"
msgstr ""

#: ../../docs/tutorials/editor/using_the_android_editor.rst:45
msgid "UX not optimized for Android phones form-factor"
msgstr ""

#: ../../docs/tutorials/editor/using_the_android_editor.rst:46
msgid ""
"`Android Go devices <https://developer.android.com/guide/topics/"
"androidgo>`__ lacks the *All files access* permission required for device "
"read/write access. As a workaround, when using a Android Go device, it's "
"recommended to create new projects only in the Android *Documents* or "
"*Downloads* directories."
msgstr ""

#: ../../docs/tutorials/editor/using_the_android_editor.rst:49
msgid ""
"The editor doesn't properly resume when *Don't keep activities* is enabled "
"in the *Developer Options*"
msgstr ""

#: ../../docs/tutorials/editor/using_the_android_editor.rst:53
msgid ""
"See the `list of open issues on GitHub related to the Android editor "
"<https://github.com/godotengine/godot/issues?"
"q=is%3Aopen+is%3Aissue+label%3Aplatform%3Aandroid+label%3Atopic%3Aeditor>`__ "
"for a list of known bugs."
msgstr ""

#: ../../docs/tutorials/editor/using_the_web_editor.rst:6
#, fuzzy
msgid "Using the Web editor"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/editor/using_the_web_editor.rst:8
msgid ""
"Since Godot 3.3, there is a `Web editor <https://editor.godotengine.org/>`__ "
"you can use to work on new or existing projects."
msgstr ""

#: ../../docs/tutorials/editor/using_the_web_editor.rst:13
msgid ""
"The web editor is in a preliminary stage. While its feature set may be "
"sufficient for educational purposes, it is currently **not recommended for "
"production work**. See :ref:`doc_using_the_web_editor_limitations` below."
msgstr ""

#: ../../docs/tutorials/editor/using_the_web_editor.rst:18
msgid "Browser support"
msgstr ""

#: ../../docs/tutorials/editor/using_the_web_editor.rst:20
msgid ""
"The Web editor requires support for WebAssembly's SharedArrayBuffer. This is "
"in turn required to support threading in the browser. The following desktop "
"browsers support WebAssembly threading and can therefore run the web editor:"
msgstr ""

#: ../../docs/tutorials/editor/using_the_web_editor.rst:24
msgid "Chrome 68 or later"
msgstr ""

#: ../../docs/tutorials/editor/using_the_web_editor.rst:25
msgid "Firefox 79 or later"
msgstr ""

#: ../../docs/tutorials/editor/using_the_web_editor.rst:26
msgid "Edge 79 or later"
msgstr ""

#: ../../docs/tutorials/editor/using_the_web_editor.rst:28
msgid ""
"Opera and Safari are not supported yet. Safari may work in the future once "
"proper threading support is added."
msgstr ""

#: ../../docs/tutorials/editor/using_the_web_editor.rst:31
msgid "**Mobile browsers are currently not supported.**"
msgstr ""

#: ../../docs/tutorials/editor/using_the_web_editor.rst:33
msgid ""
"The web editor only supports the Compatibility rendering method, as there is "
"no stable way to run Vulkan applications on the web yet."
msgstr ""

#: ../../docs/tutorials/editor/using_the_web_editor.rst:38
msgid ""
"If you use Linux, due to `poor Firefox WebGL performance <https://bugzilla."
"mozilla.org/show_bug.cgi?id=1010527>`__, it's recommended to use a Chromium-"
"based browser instead of Firefox."
msgstr ""

#: ../../docs/tutorials/editor/using_the_web_editor.rst:45
#: ../../docs/tutorials/3d/3d_text.rst:55
#: ../../docs/tutorials/3d/3d_text.rst:102
#: ../../docs/tutorials/3d/3d_text.rst:139
#: ../../docs/tutorials/3d/using_decals.rst:222
#: ../../docs/tutorials/3d/particles/subemitters.rst:67
#: ../../docs/tutorials/3d/global_illumination/reflection_probes.rst:183
#: ../../docs/tutorials/assets_pipeline/exporting_3d_scenes.rst:24
#: ../../docs/tutorials/export/exporting_for_web.rst:80
#: ../../docs/tutorials/performance/general_optimization.rst:75
#: ../../docs/tutorials/physics/large_world_coordinates.rst:222
msgid "Limitations"
msgstr ""

#: ../../docs/tutorials/editor/using_the_web_editor.rst:47
msgid ""
"Due to limitations on the Godot or Web platform side, the following features "
"are currently missing:"
msgstr ""

#: ../../docs/tutorials/editor/using_the_web_editor.rst:50
msgid "No C#/Mono support."
msgstr ""

#: ../../docs/tutorials/editor/using_the_web_editor.rst:51
msgid "No GDExtension support."
msgstr ""

#: ../../docs/tutorials/editor/using_the_web_editor.rst:52
msgid ""
"No debugging support. This means GDScript debugging/profiling, live scene "
"editing, the Remote Scene tree dock and other features that rely on the "
"debugger protocol will not work."
msgstr ""

#: ../../docs/tutorials/editor/using_the_web_editor.rst:55
msgid ""
"No project exporting. As a workaround, you can download the project source "
"using **Project > Tools > Download Project Source** and export it using a "
"`native version of the Godot editor <https://godotengine.org/download>`__."
msgstr ""

#: ../../docs/tutorials/editor/using_the_web_editor.rst:58
msgid "The editor won't warn you when closing the tab with unsaved changes."
msgstr ""

#: ../../docs/tutorials/editor/using_the_web_editor.rst:59
msgid ""
"No lightmap baking support. You can still use existing lightmaps if they "
"were baked with a native version of the Godot editor (e.g. by importing an "
"existing project)."
msgstr ""

#: ../../docs/tutorials/editor/using_the_web_editor.rst:63
msgid ""
"The following features are unlikely to be supported due to inherent "
"limitations of the Web platform:"
msgstr ""

#: ../../docs/tutorials/editor/using_the_web_editor.rst:66
msgid "No support for external script editors."
msgstr ""

#: ../../docs/tutorials/editor/using_the_web_editor.rst:67
msgid "No support for Android one-click deploy."
msgstr ""

#: ../../docs/tutorials/editor/using_the_web_editor.rst:71
msgid ""
"See the `list of open issues on GitHub related to the web editor <https://"
"github.com/godotengine/godot/issues?"
"q=is%3Aopen+is%3Aissue+label%3Aplatform%3Ahtml5+label%3Atopic%3Aeditor>`__ "
"for a list of known bugs."
msgstr ""

#: ../../docs/tutorials/editor/using_the_web_editor.rst:75
#, fuzzy
msgid "Importing a project"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/editor/using_the_web_editor.rst:77
msgid "To import an existing project, the current process is as follows:"
msgstr ""

#: ../../docs/tutorials/editor/using_the_web_editor.rst:79
msgid ""
"Specify a ZIP file to preload on the HTML5 filesystem using the **Preload "
"project ZIP** input."
msgstr ""

#: ../../docs/tutorials/editor/using_the_web_editor.rst:81
msgid ""
"Run the editor by clicking **Start Godot editor**. The Godot Project Manager "
"should appear after 10-20 seconds. On slower machines or connections, "
"loading may take up to a minute."
msgstr ""

#: ../../docs/tutorials/editor/using_the_web_editor.rst:84
msgid ""
"In the dialog that appears at the middle of the window, specify a name for "
"the folder to create then click the **Create Folder** button (it doesn't "
"have to match the ZIP archive's name)."
msgstr ""

#: ../../docs/tutorials/editor/using_the_web_editor.rst:87
msgid "Click **Install & Edit** and the project will open in the editor."
msgstr ""

#: ../../docs/tutorials/editor/using_the_web_editor.rst:91
msgid ""
"It's important to place the project folder somewhere in ``/home/web_user/``. "
"If your project folder is placed outside ``/home/web_user/``, you will lose "
"your project when closing the editor!"
msgstr ""

#: ../../docs/tutorials/editor/using_the_web_editor.rst:95
msgid ""
"When you follow the steps described above, the project folder will always be "
"located in ``/home/web_user/projects``, keeping it safe."
msgstr ""

#: ../../docs/tutorials/editor/using_the_web_editor.rst:99
#, fuzzy
msgid "Editing and running a project"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/editor/using_the_web_editor.rst:101
msgid ""
"Unlike the native version of Godot, the web editor is constrained to a "
"single window. Therefore, it cannot open a new window when running the "
"project. Instead, when you run the project by clicking the Run button or "
"pressing :kbd:`F5`, it will appear to \"replace\" the editor window."
msgstr ""

#: ../../docs/tutorials/editor/using_the_web_editor.rst:106
msgid ""
"The web editor offers an alternative way to deal with the editor and game "
"windows (which are now \"tabs\"). You can switch between the **Editor** and "
"**Game** tabs using the buttons on the top. You can also close the running "
"game or editor by clicking the **×** button next to those tabs."
msgstr ""

#: ../../docs/tutorials/editor/using_the_web_editor.rst:112
msgid "Where are my project files?"
msgstr ""

#: ../../docs/tutorials/editor/using_the_web_editor.rst:114
msgid ""
"Due to browser security limitations, the editor will save the project files "
"to the browser's IndexedDB storage. This storage isn't accessible as a "
"regular folder on your machine, but is abstracted away in a database."
msgstr ""

#: ../../docs/tutorials/editor/using_the_web_editor.rst:118
msgid ""
"You can download the project files as a ZIP archive by using **Project > "
"Tools > Download Project Source**. This can be used to export the project "
"using a `native Godot editor <https://godotengine.org/download>`__, since "
"exporting from the web editor isn't supported yet."
msgstr ""

#: ../../docs/tutorials/editor/using_the_web_editor.rst:123
msgid ""
"In the future, it may be possible to use the `HTML5 FileSystem API <https://"
"developer.mozilla.org/en-US/docs/Web/API/FileSystem>`__ to store the project "
"files on the user's filesystem as the native editor would do. However, this "
"isn't implemented yet."
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:4
msgid "Command line tutorial"
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:8
msgid ""
"Some developers like using the command line extensively. Godot is designed "
"to be friendly to them, so here are the steps for working entirely from the "
"command line. Given the engine relies on almost no external libraries, "
"initialization times are pretty fast, making it suitable for this workflow."
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:16
msgid ""
"On Windows and Linux, you can run a Godot binary in a terminal by specifying "
"its relative or absolute path."
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:19
msgid ""
"On macOS, the process is different due to Godot being contained within an ``."
"app`` bundle (which is a *folder*, not a file). To run a Godot binary from a "
"terminal on macOS, you have to ``cd`` to the folder where the Godot "
"application bundle is located, then run ``Godot.app/Contents/MacOS/Godot`` "
"followed by any command line arguments. If you've renamed the application "
"bundle from ``Godot`` to another name, make sure to edit this command line "
"accordingly."
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:28
msgid "Command line reference"
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:30
msgid "release"
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:31
msgid "debug"
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:32
#, fuzzy
msgid "editor"
msgstr "**Za uređivač:**"

#: ../../docs/tutorials/editor/command_line_tutorial.rst:34
msgid "**Legend**"
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:36
msgid ""
"|release| Available in editor builds, debug export templates and release "
"export templates."
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:37
msgid "|debug| Available in editor builds and debug export templates only."
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:38
msgid "|editor| Only available in editor builds."
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:40
msgid ""
"Note that unknown command line arguments have no effect whatsoever. The "
"engine will **not** warn you when using a command line argument that doesn't "
"exist with a given build type."
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:44
msgid "**General options**"
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:47
#: ../../docs/tutorials/editor/command_line_tutorial.rst:61
#: ../../docs/tutorials/editor/command_line_tutorial.rst:116
#: ../../docs/tutorials/editor/command_line_tutorial.rst:140
#: ../../docs/tutorials/editor/command_line_tutorial.rst:189
#: ../../docs/contributing/development/configuring_an_ide/qt_creator.rst:59
msgid "Command"
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:47
#: ../../docs/tutorials/editor/command_line_tutorial.rst:61
#: ../../docs/tutorials/editor/command_line_tutorial.rst:116
#: ../../docs/tutorials/editor/command_line_tutorial.rst:140
#: ../../docs/tutorials/editor/command_line_tutorial.rst:189
#: ../../docs/tutorials/export/exporting_for_macos.rst:91
#: ../../docs/tutorials/export/exporting_for_macos.rst:111
#: ../../docs/tutorials/export/exporting_for_macos.rst:144
#: ../../docs/tutorials/export/exporting_for_macos.rst:187
#: ../../docs/tutorials/io/binary_serialization_api.rst:120
#: ../../docs/tutorials/io/binary_serialization_api.rst:131
#: ../../docs/tutorials/io/binary_serialization_api.rst:140
#: ../../docs/tutorials/io/binary_serialization_api.rst:151
#: ../../docs/tutorials/io/binary_serialization_api.rst:160
#: ../../docs/tutorials/io/binary_serialization_api.rst:169
#: ../../docs/tutorials/io/binary_serialization_api.rst:182
#: ../../docs/tutorials/io/binary_serialization_api.rst:193
#: ../../docs/tutorials/io/binary_serialization_api.rst:208
#: ../../docs/tutorials/io/binary_serialization_api.rst:221
#: ../../docs/tutorials/io/binary_serialization_api.rst:240
#: ../../docs/tutorials/io/binary_serialization_api.rst:255
#: ../../docs/tutorials/io/binary_serialization_api.rst:270
#: ../../docs/tutorials/io/binary_serialization_api.rst:289
#: ../../docs/tutorials/io/binary_serialization_api.rst:314
#: ../../docs/tutorials/io/binary_serialization_api.rst:345
#: ../../docs/tutorials/io/binary_serialization_api.rst:360
#: ../../docs/tutorials/io/binary_serialization_api.rst:369
#: ../../docs/tutorials/io/binary_serialization_api.rst:380
#: ../../docs/tutorials/io/binary_serialization_api.rst:390
#: ../../docs/tutorials/io/binary_serialization_api.rst:412
#: ../../docs/tutorials/io/binary_serialization_api.rst:421
#: ../../docs/tutorials/io/binary_serialization_api.rst:430
#: ../../docs/tutorials/io/binary_serialization_api.rst:442
#: ../../docs/tutorials/io/binary_serialization_api.rst:466
#: ../../docs/tutorials/io/binary_serialization_api.rst:478
#: ../../docs/tutorials/io/binary_serialization_api.rst:490
#: ../../docs/tutorials/io/binary_serialization_api.rst:503
#: ../../docs/tutorials/io/binary_serialization_api.rst:514
#: ../../docs/tutorials/io/binary_serialization_api.rst:525
#: ../../docs/tutorials/io/binary_serialization_api.rst:536
#: ../../docs/tutorials/io/binary_serialization_api.rst:547
#: ../../docs/tutorials/io/binary_serialization_api.rst:555
#: ../../docs/tutorials/io/binary_serialization_api.rst:568
#: ../../docs/tutorials/io/binary_serialization_api.rst:581
#: ../../docs/tutorials/io/binary_serialization_api.rst:596
#: ../../docs/tutorials/inputs/inputevent.rst:155
#: ../../docs/tutorials/plugins/editor/import_plugins.rst:248
#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:154
#: ../../docs/tutorials/scripting/gdscript/gdscript_documentation_comments.rst:35
#: ../../docs/tutorials/scripting/gdscript/gdscript_documentation_comments.rst:90
#: ../../docs/tutorials/scripting/how_to_read_the_godot_api.rst:34
#: ../../docs/tutorials/scripting/creating_script_templates.rst:202
#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:23
#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:713
#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:779
#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:15
#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:100
#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:153
#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:247
#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:411
#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:17
#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:54
#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:101
#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:159
#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:232
#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:286
#: ../../docs/tutorials/shaders/shader_reference/particle_shader.rst:34
#: ../../docs/tutorials/shaders/shader_reference/particle_shader.rst:59
#: ../../docs/tutorials/shaders/shader_reference/particle_shader.rst:78
#: ../../docs/tutorials/shaders/shader_reference/particle_shader.rst:131
#: ../../docs/tutorials/shaders/shader_reference/particle_shader.rst:148
#: ../../docs/tutorials/shaders/shader_reference/particle_shader.rst:178
#: ../../docs/tutorials/shaders/shader_reference/sky_shader.rst:130
#: ../../docs/tutorials/shaders/shader_reference/sky_shader.rst:155
#: ../../docs/tutorials/shaders/shader_reference/sky_shader.rst:194
#: ../../docs/tutorials/shaders/shader_reference/fog_shader.rst:36
#: ../../docs/tutorials/shaders/shader_reference/fog_shader.rst:58
#: ../../docs/tutorials/shaders/visual_shaders.rst:117
#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:91
#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:164
#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:229
#: ../../docs/tutorials/xr/xr_action_map.rst:115
#: ../../docs/tutorials/xr/xr_action_map.rst:187
msgid "Description"
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:49
msgid "``-h``, ``--help``"
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:49
msgid "|release| Display the list of command line options."
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:51
msgid "``--version``"
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:51
msgid "|release| Display the version string."
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:53
msgid "``-v``, ``--verbose``"
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:53
msgid "|release| Use verbose stdout mode."
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:55
msgid "``-q``, ``--quiet``"
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:55
msgid ""
"|release| Quiet mode, silences stdout messages. Errors are still displayed."
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:58
msgid "**Run options**"
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:63
msgid "``--``, ``++``"
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:63
msgid ""
"|release| Separator for user-provided arguments. Following arguments are not "
"used by the engine, but can be read from ``OS.get_cmdline_user_args()``."
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:65
msgid "``-e``, ``--editor``"
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:65
msgid "|editor| Start the editor instead of running the scene."
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:67
msgid "``-p``, ``--project-manager``"
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:67
msgid "|editor| Start the Project Manager, even if a project is auto-detected."
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:69
msgid "``--debug-server <uri>``"
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:69
msgid ""
"|editor| Start the editor debug server (``<protocol>://<host/IP>[:<port>]``, "
"e.g. ``tcp://127.0.0.1:6007``)"
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:71
msgid "``--quit``"
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:71
msgid "|release| Quit after the first iteration."
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:73
msgid "``--quit-after``"
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:73
msgid ""
"|release| Quit after the given number of iterations. Set to 0 to disable."
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:75
msgid "``-l``, ``--language <locale>``"
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:75
msgid ""
"|release| Use a specific locale. ``<locale>`` follows the format "
"``language_Script_COUNTRY_VARIANT`` where language is a 2 or 3-letter "
"language code in lowercase and the rest is optional. See :ref:`doc_locales` "
"for more details."
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:78
msgid "``--path <directory>``"
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:78
msgid ""
"|release| Path to a project (``<directory>`` must contain a 'project.godot' "
"file)."
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:80
msgid "``-u``, ``--upwards``"
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:80
msgid "|release| Scan folders upwards for 'project.godot' file."
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:82
msgid "``--main-pack <file>``"
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:82
msgid "|release| Path to a pack (.pck) file to load."
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:84
msgid "``--render-thread <mode>``"
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:84
msgid ""
"|release| Render thread mode ('unsafe', 'safe', 'separate'). See :ref:"
"`Thread Model <class_ProjectSettings_property_rendering/driver/threads/"
"thread_model>` for more details."
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:87
msgid "``--remote-fs <address>``"
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:87
msgid "|release| Remote filesystem (``<host/IP>[:<port>]`` address)."
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:89
msgid "``--remote-fs-password <password>``"
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:89
msgid "|release| Password for remote filesystem."
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:91
msgid "``--audio-driver <driver>``"
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:91
msgid ""
"|release| Audio driver. Use ``--help`` first to display the list of "
"available drivers."
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:93
msgid "``--display-driver <driver>``"
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:93
msgid ""
"|release| Display driver (and rendering driver). Use ``--help`` first to "
"display the list of available drivers."
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:95
msgid "``--rendering-method <renderer>``"
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:95
msgid "|release| Renderer name. Requires driver support."
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:97
msgid "``--rendering-driver <driver>``"
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:97
msgid ""
"|release| Rendering driver (depends on display driver). Use ``--help`` first "
"to display the list of available drivers."
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:99
msgid "``--gpu-index <device_index>``"
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:99
msgid ""
"|release| Use a specific GPU (run with ``--verbose`` to get available device "
"list)."
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:101
msgid "``--text-driver <driver>``"
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:101
msgid "|release| Text driver (Fonts, BiDi, shaping)."
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:103
msgid "``--tablet-driver <driver>``"
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:103
msgid "|release| Pen tablet input driver."
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:105
msgid "``--headless``"
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:105
msgid ""
"|release| Enable headless mode (``--display-driver headless --audio-driver "
"Dummy``). Useful for servers and with ``--script``."
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:107
msgid "``--write-movie <file>``"
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:107
msgid ""
"|release| Run the engine in a way that a movie is written (usually with .avi "
"or .png extension). ``--fixed-fps`` is forced when enabled, but can be used "
"to change movie FPS. ``--disable-vsync`` can speed up movie writing but "
"makes interaction more difficult. ``--quit-after`` can be used to specify "
"the number of frames to write."
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:113
msgid "**Display options**"
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:118
msgid "``-f``, ``--fullscreen``"
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:118
msgid "|release| Request fullscreen mode."
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:120
msgid "``-m``, ``--maximized``"
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:120
msgid "|release| Request a maximized window."
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:122
msgid "``-w``, ``--windowed``"
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:122
msgid "|release| Request windowed mode."
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:124
msgid "``-t``, ``--always-on-top``"
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:124
msgid "|release| Request an always-on-top window."
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:126
msgid "``--resolution <W>x<H>``"
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:126
msgid "|release| Request window resolution."
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:128
msgid "``--position <X>,<Y>``"
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:128
msgid "|release| Request window position."
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:130
msgid "``--screen <N>``"
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:130
msgid "|release| Request window screen."
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:132
msgid "``--single-window``"
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:132
msgid "|release| Use a single window (no separate subwindows)."
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:134
msgid "``--xr-mode <mode>``"
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:134
msgid "|release| Select XR mode ('default', 'off', 'on')."
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:137
msgid "**Debug options**"
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:142
msgid "``-d``, ``--debug``"
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:142
msgid "|release| Debug (local stdout debugger)."
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:144
msgid "``-b``, ``--breakpoints``"
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:144
msgid ""
"|release| Breakpoint list as source::line comma-separated pairs, no spaces "
"(use ``%20`` instead)."
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:146
msgid "``--profiling``"
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:146
msgid "|release| Enable profiling in the script debugger."
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:148
msgid "``--gpu-profile``"
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:148
msgid ""
"|release| Show a GPU profile of the tasks that took the most time during "
"frame rendering."
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:150
msgid "``--gpu-validation``"
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:150
msgid ""
"|release| Enable graphics API :ref:`validation layers "
"<doc_vulkan_validation_layers>` for debugging."
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:152
msgid "``--gpu-abort``"
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:152
msgid ""
"|debug| Abort on GPU errors (usually validation layer errors), may help see "
"the problem if your system freezes."
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:154
msgid "``--remote-debug <uri>``"
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:154
msgid ""
"|release| Remote debug (``<protocol>://<host/IP>[:<port>]``, e.g. "
"``tcp://127.0.0.1:6007``)."
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:156
msgid "``--single-threaded-scene``"
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:156
msgid ""
"|release| Scene tree runs in single-threaded mode. Sub-thread groups are "
"disabled and run on the main thread."
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:158
msgid "``--debug-collisions``"
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:158
msgid "|debug| Show collision shapes when running the scene."
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:160
msgid "``--debug-paths``"
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:160
msgid "|debug| Show path lines when running the scene."
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:162
msgid "``--debug-navigation``"
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:162
msgid "|debug| Show navigation polygons when running the scene."
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:164
msgid "``--debug-avoidance``"
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:164
msgid "|debug| Show navigation avoidance debug visuals when running the scene."
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:166
msgid "``--debug-stringnames``"
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:166
msgid ""
"|debug| Print all StringName allocations to stdout when the engine quits."
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:168
msgid "``--frame-delay <ms>``"
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:168
msgid ""
"|release| Simulate high CPU load (delay each frame by <ms> milliseconds)."
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:170
msgid "``--time-scale <scale>``"
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:170
msgid ""
"|release| Force time scale (higher values are faster, 1.0 is normal speed)."
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:172
msgid "``--disable-vsync``"
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:172
msgid ""
"|release| Forces disabling of vertical synchronization, even if enabled in "
"the project settings. Does not override driver-level V-Sync enforcement."
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:175
msgid "``--disable-render-loop``"
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:175
msgid ""
"|release| Disable render loop so rendering only occurs when called "
"explicitly from script."
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:177
msgid "``--disable-crash-handler``"
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:177
msgid "|release| Disable crash handler when supported by the platform code."
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:179
msgid "``--fixed-fps <fps>``"
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:179
msgid ""
"|release| Force a fixed number of frames per second. This setting disables "
"real-time synchronization."
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:181
msgid "``--delta-smoothing <enable>``"
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:181
msgid ""
"|release| Enable or disable frame delta smoothing ('enable', 'disable')."
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:183
msgid "``--print-fps``"
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:183
msgid "|release| Print the frames per second to the stdout."
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:186
msgid "**Standalone tools**"
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:191
msgid "``-s``, ``--script <script>``"
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:191
#, fuzzy
msgid "|release| Run a script."
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/editor/command_line_tutorial.rst:193
msgid "``--check-only``"
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:193
msgid "|release| Only parse for errors and quit (use with ``--script``)."
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:195
msgid "``--export-release <preset> <path>``"
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:195
msgid ""
"|editor| Export the project using the given preset and matching release "
"template. The preset name should match one defined in export_presets.cfg. "
"``<path>`` should be absolute or relative to the project directory, and "
"include the filename for the binary (e.g. 'builds/game.exe'). The target "
"directory should exist."
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:199
msgid "``--export-debug <preset> <path>``"
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:199
msgid "|editor| Like ``--export-release``, but use debug template."
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:201
msgid "``--export-pack <preset> <path>``"
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:201
msgid ""
"|editor| Like ``--export-release``, but only export the game pack for the "
"given preset. The ``<path>`` extension determines whether it will be in PCK "
"or ZIP format."
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:204
msgid "``--convert-3to4 [<max_file_kb>] [<max_line_size>]``"
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:204
msgid "|editor| Convert project from Godot 3.x to Godot 4.x."
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:206
msgid "``--validate-conversion-3to4 [<max_file_kb>] [<max_line_size>]``"
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:206
msgid ""
"|editor| Show what elements will be renamed when converting project from "
"Godot 3.x to Godot 4.x."
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:208
msgid "``--doctool [<path>]``"
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:208
msgid ""
"|editor| Dump the engine API reference to the given ``<path>`` in XML "
"format, merging if existing files are found."
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:210
msgid "``--no-docbase``"
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:210
msgid "|editor| Disallow dumping the base types (used with ``--doctool``)."
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:212
msgid "``--gdscript-docs <path>``"
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:212
msgid ""
"|editor| Rather than dumping the engine API, generate API reference from the "
"inline documentation in the GDScript files found in <path> (used with ``--"
"doctool``)."
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:215
msgid "``--build-solutions``"
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:215
msgid ""
"|editor| Build the scripting solutions (e.g. for C# projects). Implies ``--"
"editor`` and requires a valid project to edit."
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:217
msgid "``--dump-gdextension-interface``"
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:217
msgid ""
"|editor| Generate GDExtension header file 'gdnative_interface.h' in the "
"current folder. This file is the base file required to implement a "
"GDExtension."
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:219
msgid "``--dump-extension-api``"
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:219
msgid ""
"|editor| Generate JSON dump of the Godot API for GDExtension bindings named "
"'extension_api.json' in the current folder."
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:221
msgid "``--validate-extension-api <path>``"
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:221
msgid ""
"|editor| Validate an extension API file dumped (with the option above) from "
"a previous version of the engine to ensure API compatibility. If "
"incompatibilities or errors are detected, the return code will be non-zero."
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:224
msgid "``--benchmark``"
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:224
msgid "|editor| Benchmark the run time and print it to console."
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:226
msgid "``--benchmark-file <path>``"
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:226
msgid ""
"|editor| Benchmark the run time and save it to a given file in JSON format. "
"The path should be absolute."
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:230
msgid "Path"
msgstr "Putanja"

#: ../../docs/tutorials/editor/command_line_tutorial.rst:232
msgid ""
"It is recommended to place your Godot editor binary in your ``PATH`` "
"environment variable, so it can be executed easily from any place by typing "
"``godot``. You can do so on Linux by placing the Godot binary in ``/usr/"
"local/bin`` and making sure it is called ``godot`` (case-sensitive)."
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:237
msgid ""
"To achieve this on Windows or macOS easily, you can install Godot using "
"`Scoop <https://scoop.sh>`__ (on Windows) or `Homebrew <https://brew.sh>`__ "
"(on macOS). This will automatically make the copy of Godot installed "
"available in the ``PATH``:"
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:261
msgid "Setting the project path"
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:263
msgid ""
"Depending on where your Godot binary is located and what your current "
"working directory is, you may need to set the path to your project for any "
"of the following commands to work correctly."
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:267
msgid ""
"When running the editor, this can be done by giving the path to the "
"``project.godot`` file of your project as either the first argument, like "
"this:"
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:274
msgid "For all commands, this can be done by using the ``--path`` argument:"
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:280
msgid ""
"For example, the full command for exporting your game (as explained below) "
"might look like this:"
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:286
msgid ""
"When starting from a subdirectory of your project, use the ``--upwards`` "
"argument for Godot to automatically find the ``project.godot`` file by "
"recursively searching the parent directories."
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:289
msgid ""
"For example, running a scene (as explained below) nested in a subdirectory "
"might look like this when your working directory is in the same path:"
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:300
msgid "Creating a project"
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:303
msgid ""
"Creating a project from the command line can be done by navigating the shell "
"to the desired place and making a ``project.godot`` file."
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:314
msgid "The project can now be opened with Godot."
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:318
msgid "Running the editor"
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:320
msgid ""
"Running the editor is done by executing Godot with the ``-e`` flag. This "
"must be done from within the project directory or by setting the project "
"path as explained above, otherwise the command is ignored and the Project "
"Manager appears."
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:328
msgid ""
"When passing in the full path to the ``project.godot`` file, the ``-e`` flag "
"may be omitted."
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:330
msgid ""
"If a scene has been created and saved, it can be edited later by running the "
"same code with that scene as argument."
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:338
msgid "Erasing a scene"
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:340
msgid ""
"Godot is friends with your filesystem and will not create extra metadata "
"files. Use ``rm`` to erase a scene file. Make sure nothing references that "
"scene. Otherwise, an error will be thrown upon opening the project."
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:349
msgid "Running the game"
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:351
msgid ""
"To run the game, execute Godot within the project directory or with the "
"project path as explained above."
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:357
msgid ""
"Note that passing in the ``project.godot`` file will always run the editor "
"instead of running the game."
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:359
msgid ""
"When a specific scene needs to be tested, pass that scene to the command "
"line."
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:366
#: ../../docs/tutorials/export/exporting_for_macos.rst:168
#: ../../docs/tutorials/platform/web/customizing_html5_shell.rst:192
msgid "Debugging"
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:368
msgid ""
"Catching errors in the command line can be a difficult task because they "
"scroll quickly. For this, a command line debugger is provided by adding ``-"
"d``. It works for running either the game or a single scene."
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:385
msgid ""
"Exporting the project from the command line is also supported. This is "
"especially useful for continuous integration setups."
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:390
msgid ""
"Using the ``--headless`` command line argument is **required** on platforms "
"that do not have GPU access (such as continuous integration). On platforms "
"with GPU access, ``--headless`` prevents a window from spawning while the "
"project is exporting."
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:403
msgid ""
"The preset name must match the name of an export preset defined in the "
"project's ``export_presets.cfg`` file. If the preset name contains spaces or "
"special characters (such as \"Windows Desktop\"), it must be surrounded with "
"quotes."
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:407
msgid ""
"To export a debug version of the game, use the ``--export-debug`` switch "
"instead of ``--export-release``. Their parameters and usage are the same."
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:410
msgid ""
"To export only a PCK file, use the ``--export-pack`` option followed by the "
"preset name and output path, with the file extension, instead of ``--export-"
"release`` or ``--export-debug``. The output path extension determines the "
"package's format, either PCK or ZIP."
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:417
msgid ""
"When specifying a relative path as the path for ``--export-release``, ``--"
"export-debug`` or ``--export-pack``, the path will be relative to the "
"directory containing the ``project.godot`` file, **not** relative to the "
"current working directory."
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:422
msgid "Running a script"
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:424
msgid ""
"It is possible to run a ``.gd`` script from the command line. This feature "
"is especially useful in large projects, e.g. for batch conversion of assets "
"or custom import/export."
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:428
msgid "The script must inherit from ``SceneTree`` or ``MainLoop``."
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:430
msgid "Here is an example ``sayhello.gd``, showing how it works:"
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:441
msgid "And how to run it:"
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:448
msgid ""
"If no ``project.godot`` exists at the path, current path is assumed to be "
"the current working directory (unless ``--path`` is specified)."
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:451
msgid ""
"The first line of ``sayhello.gd`` above is commonly referred to as a "
"*shebang*. If the Godot binary is in your ``PATH`` as ``godot``, it allows "
"you to run the script as follows in modern Linux distributions, as well as "
"macOS:"
msgstr ""

#: ../../docs/tutorials/editor/command_line_tutorial.rst:463
msgid ""
"If the above doesn't work in your current version of Linux or macOS, you can "
"always have the shebang run Godot straight from where it is located as "
"follows:"
msgstr ""

#: ../../docs/tutorials/editor/external_editor.rst:4
msgid "Using an external text editor"
msgstr ""

#: ../../docs/tutorials/editor/external_editor.rst:6
msgid "This page explains how to code using an external text editor."
msgstr ""

#: ../../docs/tutorials/editor/external_editor.rst:8
msgid ""
"Godot can be used with an external text editor, such as Sublime Text or "
"Visual Studio Code. Browse to the relevant editor settings: **Editor > "
"Editor Settings > Text Editor > External**"
msgstr ""

#: ../../docs/tutorials/editor/external_editor.rst:16
msgid "Text Editor > External section of the Editor Settings"
msgstr ""

#: ../../docs/tutorials/editor/external_editor.rst:16
msgid "**Text Editor > External** section of the Editor Settings"
msgstr ""

#: ../../docs/tutorials/editor/external_editor.rst:18
msgid ""
"There are two text fields: the executable path and command-line flags. The "
"flags allow you to integrate the editor with Godot, passing it the file path "
"to open and other relevant arguments. Godot will replace the following "
"placeholders in the flags string:"
msgstr ""

#: ../../docs/tutorials/editor/external_editor.rst:24
msgid "Field in Exec Flags"
msgstr ""

#: ../../docs/tutorials/editor/external_editor.rst:24
msgid "Is replaced with"
msgstr ""

#: ../../docs/tutorials/editor/external_editor.rst:26
msgid "``{project}``"
msgstr ""

#: ../../docs/tutorials/editor/external_editor.rst:26
msgid "The absolute path to the project directory"
msgstr ""

#: ../../docs/tutorials/editor/external_editor.rst:28
msgid "``{file}``"
msgstr ""

#: ../../docs/tutorials/editor/external_editor.rst:28
msgid "The absolute path to the file"
msgstr ""

#: ../../docs/tutorials/editor/external_editor.rst:30
msgid "``{col}``"
msgstr ""

#: ../../docs/tutorials/editor/external_editor.rst:30
msgid "The column number of the error"
msgstr ""

#: ../../docs/tutorials/editor/external_editor.rst:32
msgid "``{line}``"
msgstr ""

#: ../../docs/tutorials/editor/external_editor.rst:32
msgid "The line number of the error"
msgstr ""

#: ../../docs/tutorials/editor/external_editor.rst:35
msgid "Some example **Exec Flags** for various editors include:"
msgstr ""

#: ../../docs/tutorials/editor/external_editor.rst:38
msgid "Exec Flags"
msgstr ""

#: ../../docs/tutorials/editor/external_editor.rst:40
msgid "Geany/Kate"
msgstr ""

#: ../../docs/tutorials/editor/external_editor.rst:40
msgid "``{file} --line {line} --column {col}``"
msgstr ""

#: ../../docs/tutorials/editor/external_editor.rst:42
msgid "Atom"
msgstr ""

#: ../../docs/tutorials/editor/external_editor.rst:42
msgid "``{file}:{line}``"
msgstr ""

#: ../../docs/tutorials/editor/external_editor.rst:44
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_basics.rst:74
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_basics.rst:79
msgid "JetBrains Rider"
msgstr ""

#: ../../docs/tutorials/editor/external_editor.rst:44
msgid "``{project} --line {line} {file}``"
msgstr ""

#: ../../docs/tutorials/editor/external_editor.rst:46
#: ../../docs/tutorials/editor/external_editor.rst:87
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_basics.rst:71
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_basics.rst:94
#: ../../docs/contributing/development/configuring_an_ide/visual_studio_code.rst:4
msgid "Visual Studio Code"
msgstr ""

#: ../../docs/tutorials/editor/external_editor.rst:46
msgid "``{project} --goto {file}:{line}:{col}``"
msgstr ""

#: ../../docs/tutorials/editor/external_editor.rst:48
msgid "Vim (gVim)"
msgstr ""

#: ../../docs/tutorials/editor/external_editor.rst:48
msgid "``\"+call cursor({line}, {col})\" {file}``"
msgstr ""

#: ../../docs/tutorials/editor/external_editor.rst:50
#: ../../docs/tutorials/editor/external_editor.rst:114
msgid "Emacs"
msgstr ""

#: ../../docs/tutorials/editor/external_editor.rst:50
msgid "``emacs +{line}:{col} {file}``"
msgstr ""

#: ../../docs/tutorials/editor/external_editor.rst:52
msgid "Sublime Text"
msgstr ""

#: ../../docs/tutorials/editor/external_editor.rst:52
msgid "``{project} {file}:{line}:{column}``"
msgstr ""

#: ../../docs/tutorials/editor/external_editor.rst:57
msgid ""
"For Visual Studio Code on Windows, you will have to point to the ``code."
"cmd`` file."
msgstr ""

#: ../../docs/tutorials/editor/external_editor.rst:60
msgid ""
"For Emacs, you can call ``emacsclient`` instead of ``emacs`` if you use the "
"server mode."
msgstr ""

#: ../../docs/tutorials/editor/external_editor.rst:64
msgid "Using External Editor in Debugger"
msgstr ""

#: ../../docs/tutorials/editor/external_editor.rst:66
msgid ""
"Using external editor in debugger is determined by a separate option in "
"settings. For details, see :ref:`Script editor debug tools and options "
"<doc_debugger_tools_and_options>`."
msgstr ""

#: ../../docs/tutorials/editor/external_editor.rst:70
#, fuzzy
msgid "Official editor plugins"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/editor/external_editor.rst:72
msgid "We have official plugins for the following code editors:"
msgstr ""

#: ../../docs/tutorials/editor/external_editor.rst:74
#, fuzzy
msgid ""
"`Visual Studio Code <https://github.com/godotengine/godot-vscode-plugin>`_"
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati raznorazne `Godot demo projects "
"<https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/tutorials/editor/external_editor.rst:75
#, fuzzy
msgid "`Emacs <https://github.com/godotengine/emacs-gdscript-mode>`_"
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati raznorazne `Godot demo projects "
"<https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/tutorials/editor/external_editor.rst:78
msgid "LSP/DAP support"
msgstr ""

#: ../../docs/tutorials/editor/external_editor.rst:80
msgid ""
"Godot supports the `Language Server Protocol <https://microsoft.github.io/"
"language-server-protocol/>`_ (**LSP**) for code completion and the `Debug "
"Adapter Protocol <https://microsoft.github.io/debug-adapter-protocol/>`_ "
"(**DAP**) for debugging. You can check the `LSP client list <https://"
"microsoft.github.io/language-server-protocol/implementors/tools/>`_ and `DAP "
"client list <https://microsoft.github.io/debug-adapter-protocol/implementors/"
"tools/>`_ to find if your editor supports them. If this is the case, you "
"should be able to take advantage of these features without the need of a "
"custom plugin."
msgstr ""

#: ../../docs/tutorials/editor/external_editor.rst:82
msgid ""
"To use these protocols, a Godot instance must be running on your current "
"project. You should then configure your editor to communicate to the running "
"adapter ports in Godot, which by default are ``6005`` for **LSP**, and "
"``6006`` for **DAP**. You can change these ports and other settings in the "
"**Editor Settings**, under the **Network > Language Server** and **Network > "
"Debug Adapter** sections respectively."
msgstr ""

#: ../../docs/tutorials/editor/external_editor.rst:84
msgid "Below are some configuration steps for specific editors:"
msgstr ""

#: ../../docs/tutorials/editor/external_editor.rst:89
#, fuzzy
msgid ""
"You need to install the official `Visual Studio Code plugin <https://github."
"com/godotengine/godot-vscode-plugin>`_."
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati raznorazne `Godot demo projects "
"<https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/tutorials/editor/external_editor.rst:91
msgid ""
"For **LSP**, follow `these instructions <https://github.com/godotengine/"
"godot-vscode-plugin#gdscript_lsp_server_port>`_ to change the default LSP "
"port. The connection status can be checked on the status bar:"
msgstr ""

#: ../../docs/tutorials/editor/external_editor.rst:95
msgid ""
"For **DAP**, specify the ``debugServer`` property in your ``launch.json`` "
"file:"
msgstr ""

#: ../../docs/tutorials/editor/external_editor.rst:116
msgid ""
"Check the official instructions to configure `LSP <https://github.com/"
"godotengine/emacs-gdscript-mode#auto-completion-with-the-language-server-"
"protocol-lsp>`_, and `DAP <https://github.com/godotengine/emacs-gdscript-"
"mode#using-the-debugger>`_."
msgstr ""

#: ../../docs/tutorials/editor/managing_editor_features.rst:11
msgid ""
"In certain situations, it may be desirable to limit what features can be "
"used in the Godot editor. For example, a UI designer on a team who doesn't "
"need to see 3D features, or an educator slowly introducing features to "
"students. Godot has a built in system called \"feature profiles\" to do this."
msgstr ""

#: ../../docs/tutorials/editor/managing_editor_features.rst:16
msgid ""
"With feature profiles, major features and nodes can be hidden from the "
"editor. This only hides parts of the interface and does not actually remove "
"support for these features, so scenes and scripts relying on those features "
"will still work fine. This also means feature profiles are not an "
"optimization technique. For information on how to optimize Godot see :ref:"
"`doc_performance`."
msgstr ""

#: ../../docs/tutorials/editor/managing_editor_features.rst:23
#, fuzzy
msgid "Creating a profile"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/editor/managing_editor_features.rst:25
msgid ""
"To manage editor features go to **Editor > Manage Editor Features**. This "
"will open the **Manage Editor Feature Profiles** window. By default there "
"will be no profile. Click on **Create Profile** and give it a name. You will "
"then see a list of all the features in the Godot editor."
msgstr ""

#: ../../docs/tutorials/editor/managing_editor_features.rst:32
msgid ""
"The first section allows major editor features to be removed, such as the 3D "
"editor or scripting editor. Below the main features is every class and node "
"in Godot, which can be disabled as well. Click on a node and all of its "
"properties and options will be listed in the **Extra Items** box, these can "
"all be individually disabled."
msgstr ""

#: ../../docs/tutorials/editor/managing_editor_features.rst:41
#, fuzzy
msgid "Sharing a profile"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/editor/managing_editor_features.rst:43
msgid ""
"To share profiles between editors click on the **Export** button. Save the "
"custom profile somewhere as a ``.profile`` file. To use this in another "
"editor open that editor's **Manage Editor Feature Profiles** window and "
"click import, then select the ``.profile`` file."
msgstr ""

#: ../../docs/tutorials/editor/managing_editor_features.rst:48
msgid ""
"This process is potentially cumbersome however if a large amount of "
"computers need custom profiles. As an alternative, you can enable self-"
"contained mode for Godot, which allows putting all editor configuration in "
"the same folder as the editor binary. See :ref:"
"`doc_data_paths_self_contained_mode` for details."
msgstr ""

#: ../../docs/tutorials/migrating/index.rst:2
#, fuzzy
msgid "Migrating to a new version"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/migrating/index.rst:4
msgid ""
"Godot :ref:`loosely follows <doc_release_policy>` a semantic versioning "
"system, where compatibility is assumed between minor and patch releases, "
"while major releases can break it. As such, it is generally not recommended "
"to move projects between major versions during their development, especially "
"if you've been working on them for a significant amount of time."
msgstr ""

#: ../../docs/tutorials/migrating/index.rst:10
msgid ""
"Still, new features, usability improvements, or paradigm shifts in engine's "
"internals may incentivize you to upgrade. Below is a list of articles that "
"should assist you when upgrading your project between versions. Each article "
"would try its best to document every important difference and provide you "
"with a migration path."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:4
msgid "Upgrading from Godot 3 to Godot 4"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:7
msgid "Should I upgrade to Godot 4?"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:9
msgid ""
"Before beginning the upgrade process, it's worth thinking about the "
"advantages and disadvantages that upgrading would bring to your project."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:13
msgid "Advantages of upgrading"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:15
#, fuzzy
msgid ""
"Along with the `new features present in 4.0 <https://github.com/godotengine/"
"godot/blob/master/CHANGELOG.md>`__, upgrading gives the following advantages:"
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati raznorazne `Godot demo projects "
"<https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:19
msgid ""
"Many bugs are fixed in 4.0, but cannot be resolved in 3.x for various "
"reasons (such as graphics API differences or backwards compatibility)."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:21
msgid ""
"4.x will enjoy a longer :ref:`support period <doc_release_policy>`. Godot 3."
"x will continue to be supported for some time after 4.0 is released, but it "
"will eventually stop receiving support."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:25
msgid ""
"See :ref:`doc_docs_changelog` for a list of pages documenting new features "
"in Godot 4.0."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:28
msgid "Disadvantages of upgrading"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:30
msgid ""
"If you don't *need* any features present in Godot 4.0, you may want to stay "
"on Godot 3.x for the following reasons:"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:33
msgid ""
"`Godot 3.x is tried and true, while Godot 4 remains in its early stages. "
"<https://godotengine.org/article/release-management-4-0-and-beyond>`__"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:35
msgid ""
"Godot 4.0 is expected to contain workflow and performance issues that Godot "
"3.x doesn't have. These issues will be ironed out over time in future Godot "
"4.x releases."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:39
msgid ""
"Godot 4 has fewer third-party tutorials available compared to Godot 3.x. If "
"you're new to game engines, you may have a better experience using Godot 3.x "
"as a result."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:42
msgid ""
"Godot 4's baseline hardware requirements (such as memory usage) are slightly "
"higher, both for the editor and exported projects. This was required for the "
"implementation of some core optimizations."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:45
msgid ""
"Since Godot 4 includes more features than Godot 3, Godot 4's binary size for "
"exported projects is larger. While this can be mitigated by :ref:`optimizing "
"a build for size <doc_optimizing_for_size>`, a 4.0 build with a given set of "
"enabled modules will remain larger compared to a 3.x build with the same "
"modules. This can be an issue for :ref:`exporting to the Web "
"<doc_exporting_for_web>`, as binary size directly influences how fast the "
"engine can initialize (regardless of download speed)."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:52
msgid ""
"Godot 4 does not and will not have support for GLES2 rendering. (There is "
"still support for GLES3 rendering using the new OpenGL backend, which means "
"that devices without Vulkan support can still run Godot 4.)"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:56
msgid ""
"If you are targeting **very** old hardware such as Intel Sandy Bridge (2nd "
"generation) integrated graphics, this will prevent the project from running "
"on such hardware after upgrading. `Software OpenGL implementations <https://"
"github.com/pal1000/mesa-dist-win>`__ can be used to bypass this limitation, "
"but they're too slow for gaming."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:63
msgid "Caveats of upgrading"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:65
msgid ""
"**Since Godot 4 is a complete rewrite in many aspects, some features have "
"unfortunately been lost in the process.** Some of these features may be "
"restored in future Godot releases:"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:69
msgid ""
"Bullet physics was removed in favor of GodotPhysics. This only affects 3D "
"projects that used the default physics engine (which was Bullet) and didn't "
"manually change it to GodotPhysics. There are no plans to re-add Bullet "
"physics in core, but a third-party add-on could be created for it thanks to "
"GDExtension."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:74
msgid ""
"Rendering in 2D is no longer performed in HDR, which means \"overbright\" "
"modulate values have no visible effect. This is planned to be restored at "
"some point in the future."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:77
msgid ""
"While rendering still happens in HDR in 3D when using the Forward Plus or "
"Forward Mobile backends, Viewports cannot return HDR data anymore. This is "
"planned to be restored at some point in the future."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:80
msgid ""
"Mono was replaced by .NET 6. This means exporting C# projects to Android, "
"iOS and HTML5 is no longer supported for now. Exporting C# projects to "
"desktop platforms is still supported, and as of 4.2 there's experimental "
"support for exporting to mobile platforms. Support for exporting C# projects "
"to more platforms will be restored in future 4.x releases as upstream "
"support improves."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:87
msgid ""
"You can find a more complete list of functional regressions by searching for "
"`issues labeled \"regression\" but not \"bug\" on GitHub <https://github.com/"
"godotengine/godot/issues?q=is%3Aissue+is%3Aopen+label%3Aregression+-"
"label%3Abug>`__."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:91
msgid "Preparing before the upgrade (optional)"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:93
msgid ""
"If you want to be ready to upgrade to Godot 4 in the future, consider using :"
"ref:`class_Tweener` and the :ref:`class_Time` singleton in your project. "
"These classes are both available in Godot 3.5 and later."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:97
msgid ""
"This way, you won't be relying on the deprecated Tween node and OS time "
"functions, both of which are removed in Godot 4.0."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:100
msgid ""
"It's also a good idea to rename external shaders so that their extension is "
"``.gdshader`` instead of ``.shader``. Godot 3.x supports both extensions, "
"but only ``.gdshader`` is supported in Godot 4.0."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:105
#, fuzzy
msgid "Running the project upgrade tool"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:109
msgid ""
"**Make a full backup of your project** before upgrading! The project upgrade "
"tool will *not* perform any backups of the project that is being upgraded."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:112
msgid ""
"You can backup a project by using version control, or by copying the project "
"folder to another location."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:118
msgid "To use the project upgrade tool:"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:120
msgid "Open the Godot 4 Project Manager."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:121
msgid ""
"Import the Godot 3.x project using the **Import** button, or use the "
"**Scan** button to find the project within a folder."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:123
msgid ""
"Double-click the imported project (or select the project then choose "
"**Edit**)."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:124
msgid ""
"You will see a dialog appearing with two options: **Convert project.godot "
"Only** and **Convert Full Project**. After ensuring your project is backed "
"up (see the above warning), choose **Convert Full Project**. **Convert "
"project.godot Only** is intended to be used for advanced use cases *only*, "
"in case the conversion tool fails."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:129
msgid ""
"Wait until the project conversion process finishes. This can take up to a "
"few minutes for large projects with lots of scenes."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:131
msgid ""
"When the Project Manager interface becomes available again, double-click the "
"project (or select the project then choose **Edit**) to open it in the "
"editor."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:135
msgid ""
"If you hit conversion issues due to some project files being too large or "
"long, you can use the command line to upgrade the project (see below). This "
"will allow you to override the converter's size limits."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:140
#, fuzzy
msgid "Using the command line"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:142
msgid ""
"To use the project upgrade tool from the :ref:`command line "
"<doc_command_line_tutorial>`, it's recommended to validate the project "
"conversion by running the Godot editor binary with the following arguments:"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:151
msgid ""
"If the list of planned upgrades looks good to you, run the following command "
"on the Godot editor binary to upgrade project files:"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:160
msgid ""
"``[<max_file_kb>]`` and ``[<max_line_size>]`` are *optional* arguments to "
"specify the maximum size of files to be converted (in kilobytes and lines). "
"The default limits are 4 MB and 100,000 lines respectively. If a file hits "
"either of those limits, it will not be upgraded by the project converter. "
"This is useful to prevent large resources from slowing down the upgrade to a "
"crawl."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:166
msgid ""
"If you still want large files to be converted by the project upgrade tool, "
"increase the size limits when running the project upgrade tool. For example, "
"running the Godot editor binary with those arguments increases both limits "
"by a 10× factor:"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:177
msgid ""
"Only Godot 3.0 and later projects can be upgraded using the project "
"conversion tool found in the Godot 4 editor."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:180
msgid ""
"It's recommended to ensure that your project is up-to-date with the latest 3."
"x stable release before running the project upgrade tool."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:184
msgid "Fixing the project after running the project upgrade tool"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:186
msgid ""
"After upgrading the project, you may notice that certain things don't look "
"as they should. Scripts will likely contain various errors as well (possibly "
"hundreds in large projects). This is because the project upgrade tool cannot "
"cater to all situations. Therefore, a large part of the upgrade process "
"remains manual."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:193
msgid "Automatically renamed nodes and resources"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:195
msgid ""
"The list below refers to nodes which were simply renamed for consistency or "
"clarity in Godot 4.0. The project upgrade tool renames them automatically in "
"your scripts."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:199
msgid ""
"One noteworthy set of renames is 3D nodes, which all got a ``3D`` suffix "
"added for consistency with their 2D counterparts. For example, ``Area`` is "
"now ``Area3D``."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:202
msgid ""
"For ease of searching, this table lists all nodes and resources that were "
"renamed and are automatically converted, excluding the ones which only "
"involved adding a ``3D`` suffix to the old name:"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:207
msgid "Old name (Godot 3.x)"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:207
msgid "New name (Godot 4)"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:209
msgid "AnimatedSprite"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:209
msgid "AnimatedSprite2D"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:211
msgid "ARVRCamera"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:211
msgid "XRCamera3D"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:213
msgid "ARVRController"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:213
msgid "XRController3D"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:215
msgid "ARVRAnchor"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:215
msgid "XRAnchor3D"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:217
msgid "ARVRInterface"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:217
msgid "XRInterface"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:219
msgid "ARVROrigin"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:219
msgid "XROrigin3D"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:221
msgid "ARVRPositionalTracker"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:221
msgid "XRPositionalTracker"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:223
msgid "ARVRServer"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:223
msgid "XRServer"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:225
msgid "CubeMesh"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:225
msgid "BoxMesh"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:227
#, fuzzy
msgid "EditorSpatialGizmo"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:227
msgid "EditorNode3DGizmo"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:229
msgid "EditorSpatialGizmoPlugin"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:229
msgid "EditorNode3DGizmoPlugin"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:231
msgid "GIProbe"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:231
msgid "VoxelGI"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:233
msgid "GIProbeData"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:233
msgid "VoxelGIData"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:235
#, fuzzy
msgid "GradientTexture"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:235
#, fuzzy
msgid "GradientTexture1D"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:237
msgid "KinematicBody"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:237
msgid "CharacterBody3D"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:239
msgid "KinematicBody2D"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:239
#: ../../docs/tutorials/physics/physics_introduction.rst:330
msgid "CharacterBody2D"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:241
msgid "Light2D"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:241
msgid "PointLight2D"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:243
msgid "LineShape2D"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:243
msgid "WorldBoundaryShape2D"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:245
#: ../../docs/tutorials/rendering/viewports.rst:51
msgid "Listener"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:245
msgid "AudioListener3D"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:247
msgid "NavigationMeshInstance"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:247
msgid "NavigationRegion3D"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:249
msgid "NavigationPolygonInstance"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:249
msgid "NavigationRegion2D"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:251
msgid "Navigation2DServer"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:251
msgid "NavigationServer2D"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:253
msgid "PanoramaSky"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:253
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:277
msgid "Sky"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:255
#: ../../docs/tutorials/3d/particles/index.rst:24
msgid "Particles"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:255
msgid "GPUParticles3D"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:257
msgid "Particles2D"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:257
msgid "GPUParticles2D"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:259
msgid "ParticlesMaterial"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:259
#: ../../docs/tutorials/2d/particle_systems_2d.rst:47
msgid "ParticleProcessMaterial"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:261
msgid "Physics2DDirectBodyState"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:261
msgid "PhysicsDirectBodyState2D"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:263
msgid "Physics2DDirectSpaceState"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:263
msgid "PhysicsDirectSpaceState2D"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:265
msgid "Physics2DServer"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:265
msgid "PhysicsServer2D"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:267
msgid "Physics2DShapeQueryParameters"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:267
msgid "PhysicsShapeQueryParameters2D"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:269
msgid "Physics2DTestMotionResult"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:269
msgid "PhysicsTestMotionResult2D"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:271
msgid "PlaneShape"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:271
msgid "WorldBoundaryShape3D"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:273
msgid "Position2D"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:273
msgid "Marker2D"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:275
msgid "Position3D"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:275
msgid "Marker3D"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:277
msgid "ProceduralSky"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:279
msgid "RayShape"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:279
msgid "SeparationRayShape3D"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:281
msgid "RayShape2D"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:281
msgid "SeparationRayShape2D"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:283
msgid "ShortCut"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:283
msgid "Shortcut"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:285
msgid "Spatial"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:285
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:642
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:651
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:653
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:657
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:659
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:661
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:663
#: ../../docs/contributing/development/core_and_modules/inheritance_class_tree.rst:25
msgid "Node3D"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:287
msgid "SpatialGizmo"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:287
msgid "Node3DGizmo"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:289
msgid "SpatialMaterial"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:289
msgid "StandardMaterial3D"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:291
msgid "Sprite"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:291
msgid "Sprite2D"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:293
msgid "StreamTexture"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:293
msgid "CompressedTexture2D"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:295
msgid "TextureProgress"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:295
msgid "TextureProgressBar"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:297
#, fuzzy
msgid "VideoPlayer"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:297
msgid "VideoStreamPlayer"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:299
msgid "ViewportContainer"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:299
#: ../../docs/tutorials/ui/gui_containers.rst:204
#: ../../docs/contributing/development/compiling/optimizing_for_size.rst:181
#, fuzzy
msgid "SubViewportContainer"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:301
msgid "Viewport"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:301
msgid "SubViewport"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:303
msgid "VisibilityEnabler"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:303
msgid "VisibleOnScreenEnabler3D"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:305
msgid "VisibilityNotifier"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:305
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:309
msgid "VisibleOnScreenNotifier3D"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:307
msgid "VisibilityNotifier2D"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:307
msgid "VisibleOnScreenNotifier2D"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:309
msgid "VisibilityNotifier3D"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:311
#, fuzzy
msgid "VisualServer"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:311
msgid "RenderingServer"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:313
#, fuzzy
msgid "VisualShaderNodeScalarConstant"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:313
#, fuzzy
msgid "VisualShaderNodeFloatConstant"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:315
#, fuzzy
msgid "VisualShaderNodeScalarFunc"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:315
#, fuzzy
msgid "VisualShaderNodeFloatFunc"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:317
#, fuzzy
msgid "VisualShaderNodeScalarOp"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:317
#, fuzzy
msgid "VisualShaderNodeFloatOp"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:319
#, fuzzy
msgid "VisualShaderNodeScalarClamp"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:319
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:321
#, fuzzy
msgid "VisualShaderNodeClamp"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:321
#, fuzzy
msgid "VisualShaderNodeVectorClamp"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:323
#, fuzzy
msgid "VisualShaderNodeScalarInterp"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:323
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:325
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:327
#, fuzzy
msgid "VisualShaderNodeMix"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:325
#, fuzzy
msgid "VisualShaderNodeVectorInterp"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:327
#, fuzzy
msgid "VisualShaderNodeVectorScalarMix"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:329
msgid "VisualShaderNodeScalarSmoothStep"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:329
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:331
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:333
#, fuzzy
msgid "VisualShaderNodeSmoothStep"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:331
msgid "VisualShaderNodeVectorSmoothStep"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:333
msgid "VisualShaderNodeVectorScalarSmoothStep"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:335
msgid "VisualShaderNodeVectorScalarStep"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:335
#, fuzzy
msgid "VisualShaderNodeStep"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:337
#, fuzzy
msgid "VisualShaderNodeScalarSwitch"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:337
#, fuzzy
msgid "VisualShaderNodeSwitch"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:339
msgid "VisualShaderNodeScalarTransformMult"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:339
#, fuzzy
msgid "VisualShaderNodeTransformOp"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:341
msgid "VisualShaderNodeScalarDerivativeFunc"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:341
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:343
#, fuzzy
msgid "VisualShaderNodeDerivativeFunc"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:343
msgid "VisualShaderNodeVectorDerivativeFunc"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:345
#, fuzzy
msgid "VisualShaderNodeBooleanUniform"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:345
msgid "VisualShaderNodeBooleanParameter"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:347
#, fuzzy
msgid "VisualShaderNodeColorUniform"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:347
#, fuzzy
msgid "VisualShaderNodeColorParameter"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:349
#, fuzzy
msgid "VisualShaderNodeScalarUniform"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:349
#, fuzzy
msgid "VisualShaderNodeFloatParameter"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:351
#, fuzzy
msgid "VisualShaderNodeCubeMapUniform"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:351
msgid "VisualShaderNodeCubeMapParameter"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:353
#, fuzzy
msgid "VisualShaderNodeTextureUniform"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:353
msgid "VisualShaderNodeTexture2DParameter"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:355
msgid "VisualShaderNodeTextureUniformTriplanar"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:355
msgid "VisualShaderNodeTextureParameterTriplanar"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:357
#, fuzzy
msgid "VisualShaderNodeTransformUniform"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:357
#, fuzzy
msgid "VisualShaderNodeTransformParameter"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:359
#, fuzzy
msgid "VisualShaderNodeVec3Uniform"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:359
#, fuzzy
msgid "VisualShaderNodeVec3Parameter"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:361
#, fuzzy
msgid "VisualShaderNodeUniform"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:361
#, fuzzy
msgid "VisualShaderNodeParameter"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:363
#, fuzzy
msgid "VisualShaderNodeUniformRef"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:363
#, fuzzy
msgid "VisualShaderNodeParameterRef"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:369
msgid "Manually renaming methods, properties, signals and constants"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:371
msgid ""
"Due to how the project upgrade tool works, not all :abbr:`API (Application "
"Programming Interface)` renames can be performed automatically. The list "
"below contains all renames that must be performed manually using the script "
"editor."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:375
msgid ""
"If you cannot find a node or resource in the list below, refer to the above "
"table to find its new name."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:380
msgid ""
"You can use the **Replace in Files** dialog to speed up replacement by "
"pressing :kbd:`Ctrl + Shift + R` while the script editor is open. However, "
"be careful as the Replace in Files dialog doesn't offer any way to undo a "
"replacement. Use version control to commit your upgrade work regularly. "
"Command line tools such as `sd <https://github.com/chmln/sd>`__ can also be "
"used if you need something more flexible than the editor's Replace in Files "
"dialog."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:387
msgid ""
"If using C#, remember to search for outdated API usage with PascalCase "
"notation in the project (and perform the replacement with PascalCase "
"notation)."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:391
msgid "**Methods**"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:393
msgid ""
"File and Directory classes were replaced by :ref:`class_FileAccess` and :ref:"
"`class_DirAccess`, which have an entirely different API. Several methods are "
"now static, which means you can call them directly on FileAccess or "
"DirAccess without having to create an instance of that class."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:397
msgid ""
"Screen and window-related methods from the :ref:`class_OS` singleton (such "
"as ``OS.get_screen_size()``) were moved to the :ref:`class_DisplayServer` "
"singleton. Method naming was also changed to use the ``DisplayServer."
"<object>_<get/set>_property()`` form instead. For example, ``OS."
"get_screen_size()`` becomes ``DisplayServer.screen_get_size()``."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:402
msgid ""
"Time and date methods from the :ref:`class_OS` singleton were moved to the :"
"ref:`class_Time` singleton. (The Time singleton is also available in Godot "
"3.5 and later.)"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:405
msgid ""
"You may have to replace some ``instance()`` calls with ``instantiate()``. "
"The converter *should* handle this automatically, but this relies on custom "
"code that may not work in 100% of situations."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:408
msgid "AcceptDialog's ``set_autowrap()`` is now ``set_autowrap_mode()``."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:409
msgid ""
"AnimationNode's ``process()`` is now ``_process()`` (note the leading "
"underscore, which denotes a virtual method)."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:411
msgid "AStar2D and AStar3D's ``get_points()`` is now ``get_points_id()``."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:412
msgid "BaseButton's ``set_event()`` is now ``set_shortcut()``."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:413
msgid "Camera2D's ``get_v_offset()`` is now ``get_drag_vertical_offset()``."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:414
msgid "Camera2D's ``set_v_offset()`` is now ``set_drag_vertical_offset()``."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:415
msgid "CanvasItem's ``update()`` is now ``queue_redraw()``."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:416
msgid "Control's ``set_tooltip()`` is now ``set_tooltip_text()``."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:417
msgid ""
"EditorNode3DGizmoPlugin's ``create_gizmo()`` is now ``_create_gizmo()`` "
"(note the leading underscore, which denotes a virtual method)."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:419
msgid "ENetMultiplayerPeer's ``get_peer_port()`` is now ``get_peer()``."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:420
msgid "FileDialog's ``get_mode()`` is now ``get_file_mode()``."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:421
msgid "FileDialog's ``set_mode()`` is now ``set_file_mode()``."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:422
msgid "GraphNode's ``get_offset()`` is now ``get_position_offset()``."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:423
msgid "GridMap's ``world_to_map()`` is now ``local_to_map()``."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:424
msgid "GridMap's ``map_to_world()`` is now ``map_to_local()``."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:425
msgid "Image's ``get_rect()`` is now ``get_region()``."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:426
msgid "ItemList's ``get_v_scroll()`` is now ``get_v_scroll_bar()``."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:427
msgid ""
"MultiPlayerAPI's ``get_network_connected_peers()`` is now ``get_peers()``."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:428
msgid "MultiPlayerAPI's ``get_network_peer()`` is now ``get_peer()``."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:429
msgid ""
"MultiPlayerAPI's ``get_network_unique_id()`` is now ``get_unique_id()``."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:430
msgid ""
"MultiPlayerAPI's ``has_network_peer()`` is now ``has_multiplayer_peer()``."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:431
msgid "PacketPeerUDP's ``is_listening()`` is now ``is_bound()``."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:432
msgid "PacketPeerUDP's ``listen()`` is now ``bind()``."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:433
msgid ""
"ParticleProcessMaterial's ``set_flag()`` is now ``set_particle_flag()``."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:434
msgid ""
"ResourceFormatLoader's ``get_dependencies()`` is now ``_get_dependencies()`` "
"(note the leading underscore, which denotes a virtual method)."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:436
msgid "SceneTree's ``change_scene()`` is now ``change_scene_to_file()``."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:437
msgid "Shortcut's ``is_valid()`` is now ``has_valid_event()``."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:438
msgid "TileMap's ``world_to_map()`` is now ``local_to_map()``."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:439
msgid "TileMap's ``map_to_world()`` is now ``map_to_local()``."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:441
msgid "**Properties**"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:445
msgid ""
"If a property is listed here, its associated getter and setter methods must "
"also be renamed manually if used in the project. For example, PathFollow2D "
"and PathFollow3D's ``set_offset()`` and ``get_offset()`` must be renamed to "
"``set_progress()`` and ``get_progress()`` respectively."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:450
msgid "Control's ``margin`` is now ``offset``."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:451
msgid "Label's ``percent_visible`` is now ``visible_ratio``."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:452
msgid ""
"MultiPlayerAPI's ``refuse_new_network_connections`` is now "
"``refuse_new_connections``."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:453
msgid "PathFollow2D and PathFollow3D's ``offset`` is now ``progress``."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:454
msgid "TextureProgressBar's ``percent_visible`` is now ``show_percentage``."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:455
msgid ""
"The ``extents`` property on CSG nodes and VoxelGI will have to be replaced "
"with ``size``, with the set value halved (as they're no longer half-"
"extents). This also affects its setter/getter methods ``set_extents()`` and "
"``get_extents()``."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:459
msgid ""
"The ``Engine.editor_hint`` property was removed in favor of the ``Engine."
"is_editor_hint()`` *method*. This is because it's read-only, and properties "
"in Godot are not used for read-only values."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:463
msgid "**Enums**"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:465
msgid "CPUParticles2D's ``FLAG_MAX`` is now ``PARTICLE_FLAG_MAX``."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:467
#, fuzzy
msgid "**Signals**"
msgstr "Signali"

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:469
msgid "FileSystemDock's ``instantiate`` is now ``instance``."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:470
msgid ""
"CanvasItem's ``hide`` is now ``hidden``. This rename does **not** apply to "
"the ``hide()`` method, only the signal."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:472
msgid "Tween's ``tween_all_completed`` is now ``loop_finished``."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:473
msgid "EditorSettings' ``changed`` is now ``settings_changed``."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:475
msgid "**Constants**"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:477
msgid ""
"Color names are now uppercase and use underscores between words. For "
"example, ``Color.palegreen`` is now ``Color.PALE_GREEN``."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:479
msgid ""
"MainLoop's ``NOTIFICATION_`` constants were duplicated to ``Node`` which "
"means you can remove the ``MainLoop.`` prefix when referencing them."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:481
msgid ""
"MainLoop's ``NOTIFICATION_WM_QUIT_REQUEST`` is now "
"``NOTIFICATION_WM_CLOSE_REQUEST``."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:484
#, fuzzy
msgid "Checking project settings"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:486
msgid ""
"Several project settings were renamed, and some of them had their enums "
"changed in incompatible ways (such as shadow filter quality). This means you "
"may need to set some project settings' values again. Make sure the "
"**Advanced** toggle is enabled in the project settings dialog so you can see "
"all project settings."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:492
msgid "Checking Environment settings"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:494
msgid ""
"Graphics quality settings were moved from Environment properties to project "
"settings. This was done to make run-time quality adjustments easier, without "
"having to access the currently active Environment resource then modify its "
"properties."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:499
msgid ""
"As a result, you will have to configure Environment quality settings in the "
"project settings as old Environment quality settings aren't converted "
"automatically to project settings."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:503
msgid ""
"If you have a graphics settings menu that changed environment properties in "
"Godot 3.x, you will have to change its code to call :ref:"
"`class_RenderingServer` methods that affect environment effects' quality. "
"Only the \"base\" toggle of each environment effect and its visual knobs "
"remain within the Environment resource."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:509
#, fuzzy
msgid "Updating shaders"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:511
msgid ""
"There have been some changes to shaders that aren't covered by the upgrade "
"tool."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:513
msgid ""
"The ``.shader`` file extension is no longer supported, which means you must "
"rename ``.shader`` files to ``.gdshader`` and update references accordingly "
"in scene/resource files using an external text editor."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:517
msgid "Some notable renames you will need to perform in shaders are:"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:519
msgid ""
"Texture filter and repeat modes are now set on individual uniforms, rather "
"than the texture files themselves."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:521
msgid "``hint_albedo`` is now ``source_color``."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:522
#, fuzzy
msgid ":ref:`Built in matrix variables were renamed. <doc_spatial_shader>`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:523
msgid ""
"Particles shaders no longer use the ``vertex()`` processor function. Instead "
"they use ``start()`` and ``process()``."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:526
msgid "See :ref:`doc_shading_language` for more information."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:529
msgid "Updating scripts to take backwards-incompatible changes into account"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:531
msgid ""
"Some changes performed between Godot 3.x and 4 are not renames, but they "
"still break backwards compatibility due to different default behavior."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:534
msgid "The most notable examples of this are:"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:536
msgid ""
"Lifecycle functions such as ``_ready()`` and ``_process()`` no longer "
"implicitly call parent classes' functions that have the same name. Instead, "
"you must use ``super()`` at the top of a lifecycle function in the child "
"class so that the parent class function is called first."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:540
msgid ""
"Both :ref:`class_String` and :ref:`class_StringName` are now exposed to "
"GDScript. This allows for greater optimization, as StringName is "
"specifically designed to be used for \"constant\" strings that are created "
"once and reused many times. These types are not strictly equivalent to each "
"other, which means ``is_same(\"example\", &\"example\")`` returns ``false``. "
"Although in most cases they are interchangeable (``\"example\" == "
"&\"example\"`` returns ``true``), sometimes you may have to replace "
"``\"example\"`` with ``&\"example\"``."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:547
msgid ""
":ref:`GDScript setter and getter syntax "
"<doc_gdscript_basics_setters_getters>` was changed, but it's only partially "
"converted by the conversion tool. In most cases, manual changes are required "
"to make setters and getters working again."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:550
msgid ""
":ref:`GDScript signal connection syntax <doc_gdscript_signals>` was changed. "
"The conversion tool will use the string-based syntax which is still present "
"in Godot 4, but it's recommended to switch to the :ref:`class_Signal`-based "
"syntax described on the linked page. This way, strings are no longer "
"involved, which avoids issues with signal name errors that can only be "
"discovered at run-time."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:555
msgid ""
"Built-in scripts that are :ref:`tool scripts "
"<doc_running_code_in_the_editor>` do not get the ``tool`` keyword converted "
"to the ``@tool`` annotation."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:557
msgid ""
"The Tween node was removed in favor of Tweeners, which are also available in "
"Godot 3.5 and later. See the `original pull request <https://github.com/"
"godotengine/godot/pull/41794>`__ for details."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:561
msgid ""
"``randomize()`` is now automatically called on project load, so "
"deterministic randomness with the global RandomNumberGenerate instance "
"requires manually setting a seed in a script's ``_ready()`` function."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:564
msgid ""
"``call_group()``, ``set_group()`` and ``notify_group()`` are now immediate "
"by default. If calling an expensive function, this may result in stuttering "
"when used on a group containing a large number of nodes. To use deferred "
"calls like before, replace ``call_group(...)`` with "
"``call_group_flags(SceneTree.GROUP_CALL_DEFERRED, ...)`` (and do the same "
"with ``set_group()`` and ``notify_group()`` respectively)."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:570
msgid ""
"Instead of ``rotation_degrees``, the ``rotation`` property is exposed to the "
"editor, which is automatically displayed as degrees in the Inspector dock. "
"This may break animations, as the conversion is not handled automatically by "
"the conversion tool."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:574
msgid ""
":ref:`class_AABB`'s ``has_no_surface()`` was inverted and renamed to "
"``has_surface()``."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:575
msgid ""
":ref:`class_AABB` and :ref:`class_Rect2`'s ``has_no_area()`` was inverted "
"and renamed to ``has_area()``."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:577
msgid ""
":ref:`class_AnimatedTexture`'s ``fps`` property was replaced by "
"``speed_scale``, which works the same as AnimationPlayer's "
"``playback_speed`` property."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:579
msgid ""
":ref:`class_AnimatedSprite2D` and :ref:`class_AnimatedSprite3D` now allow "
"negative ``speed_scale`` values. This may break animations if you relied on "
"``speed_scale`` being internally clamped to ``0.0``."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:582
msgid ""
":ref:`class_AnimatedSprite2D` and :ref:`class_AnimatedSprite3D`'s "
"``playing`` property was removed. Use ``play()``/``stop()`` method instead "
"OR configure ``autoplay`` animation via the SpriteFrames bottom panel (but "
"not both at once)."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:585
msgid ""
":ref:`class_Array`'s ``slice()`` second parameter (``end``) is now "
"*exclusive*, instead of being inclusive. For example, this means that ``[1, "
"2, 3].slice(0, 1)`` now returns ``[1]`` instead of ``[1, 2]``."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:588
msgid ""
":ref:`class_BaseButton`'s signals are now ``button_up`` and ``button_down``. "
"The ``pressed`` property is now ``button_pressed``."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:590
msgid ""
":ref:`class_Camera2D`'s ``rotating`` property was replaced by "
"``ignore_rotation``, which has inverted behavior."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:592
msgid ""
"Camera2D's ``zoom`` property was inverted: higher values are now more zoomed "
"in, instead of less."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:594
msgid ""
":ref:`class_Node`'s ``remove_and_skip()`` method was removed. If you need to "
"reimplement it in a script, you can use the `old C++ implementation <https://"
"github.com/godotengine/godot/blob/7936b3cc4c657e4b273b376068f095e1e0e4d82a/"
"scene/main/node.cpp#L1910-L1945>`__ as a reference."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:598
msgid ""
"``OS.get_system_time_secs()`` should be converted to ``Time."
"get_time_dict_from_system()[\"second\"]``."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:600
msgid ""
":ref:`class_ResourceSaver`'s ``save()`` method now has its arguments swapped "
"around (``resource: Resource, path: String``). This also applies to :ref:"
"`class_ResourceFormatSaver`'s ``_save()`` method."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:603
msgid ""
"A :ref:`class_StreamPeerTCP` must have ``poll()`` called on it to update its "
"state, instead of relying on ``get_status()`` automatically polling: "
"`GH-59582 <https://github.com/godotengine/godot/pull/59582>`__"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:606
msgid ""
":ref:`class_String`'s ``right()`` method `has changed behavior <https://"
"github.com/godotengine/godot/pull/36180>`__: it now returns a number of "
"characters from the right of the string, rather than the right side of the "
"string from a given position. If you need the old behavior, you can use "
"``substr()`` instead."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:610
msgid ""
"``is_connected_to_host()`` was removed from StreamPeerTCP and PacketPeerUDP "
"as per `GH-59582 <https://github.com/godotengine/godot/pull/59582>`__. "
"``get_status()`` can be used in StreamPeerTCP instead. "
"``is_socket_connected()`` can be used in :ref:`class_PacketPeerUDP` instead."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:614
msgid ""
"In ``_get_property_list()``, the ``or_lesser`` property hint string is now "
"``or_less``."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:615
msgid ""
"In ``_get_property_list()``, the ``noslider`` property hint string is now "
"``no_slider``."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:616
msgid ""
"VisualShaderNodeVec4Parameter now takes a :ref:`class_Vector4` as parameter "
"instead of a :ref:`class_Quaternion`."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:619
msgid "**Removed or replaced nodes/resources**"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:621
msgid ""
"This lists all nodes that were replaced by another node requiring different "
"configuration. The setup must be done from scratch again, as the project "
"converter doesn't support updating existing setups:"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:626
msgid "Removed node"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:626
msgid "Closest approximation"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:626
#: ../../docs/tutorials/3d/variable_rate_shading.rst:133
#: ../../docs/tutorials/physics/large_world_coordinates.rst:57
msgid "Comment"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:628
#, fuzzy
msgid "AnimationTreePlayer"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:628
#, fuzzy
msgid "AnimationTree"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:628
msgid "AnimationTreePlayer was deprecated since Godot 3.1."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:630
msgid "BakedLightmap"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:630
msgid "LightmapGI"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:630
#, fuzzy
msgid "See :ref:`doc_using_lightmap_gi`."
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:632
msgid "BakedLightmapData"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:632
msgid "LightmapGIData"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:634
msgid "BitmapFont"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:634
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:636
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:638
msgid "FontFile"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:634
#, fuzzy
msgid "See :ref:`doc_gui_using_fonts`."
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:636
msgid "DynamicFont"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:638
msgid "DynamicFontData"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:640
msgid "Navigation2D"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:640
#: ../../docs/contributing/development/core_and_modules/inheritance_class_tree.rst:20
msgid "Node2D"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:640
msgid ""
"Replaced by :ref:`other 2D Navigation nodes <doc_navigation_overview_2d>`."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:642
msgid "Navigation3D"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:642
msgid ""
"Replaced by :ref:`other 3D Navigation nodes <doc_navigation_overview_3d>`."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:644
msgid "OpenSimplexNoise"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:644
msgid "FastNoiseLite"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:644
msgid ""
"Has different parameters and more noise types such as cellular. No support "
"for 4D noise as it's absent from the FastNoiseLite library."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:647
msgid "ToolButton"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:647
msgid "Button"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:647
msgid "ToolButton was Button with the **Flat** property enabled by default."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:649
msgid "YSort"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:649
msgid "Node2D or Control"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:649
msgid "CanvasItem has a new **Y Sort Enabled** property in 4.0."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:651
msgid "ProximityGroup"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:651
msgid ":ref:`class_VisibleOnScreenNotifier3D` can act as a replacement."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:653
msgid "Portal"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:653
msgid ""
"Portal and room occlusion culling was replaced by raster :ref:`occlusion "
"culling <doc_occlusion_culling>` (OccluderInstance3D node), which requires a "
"different setup process."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:657
msgid "Room"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:659
msgid "RoomManager"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:661
msgid "RoomGroup"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:663
msgid "Occluder"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:663
msgid ""
"Geometry occlusion culling was replaced by raster :ref:`occlusion culling "
"<doc_occlusion_culling>` (OccluderInstance3D node), which requires a "
"different setup process."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:667
msgid "OccluderShapeSphere"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:667
msgid "Resource"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:670
msgid ""
"If loading an old project, the node will be replaced with its *Closest "
"approximation* automatically (even if not using the project upgrade tool)."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:673
msgid "**Threading changes**"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:675
msgid ""
":ref:`Threading <doc_using_multiple_threads>` APIs have changed in 4.0. For "
"example, the following code snippet in Godot 3.x must be modified to work in "
"4.0:"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:688
msgid ""
"``Thread.is_active()`` is no longer used and should be converted to ``Thread."
"is_alive()``."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:692
msgid ""
"See the `changelog <https://github.com/godotengine/godot/blob/master/"
"CHANGELOG.md>`__ for a full list of changes between Godot 3.x and 4."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:696
msgid "ArrayMesh resource compatibility breakage"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:698
msgid ""
"If you've saved an ArrayMesh resource to a ``.res`` or ``.tres`` file, the "
"format used in 4.0 is not compatible with the one used in 3.x. You will need "
"to go through the process of importing the source mesh file and saving it as "
"an ArrayMesh resource again."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:704
msgid ""
"List of automatically renamed methods, properties, signals and constants"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:706
msgid ""
"The `editor/renames_map_3_to_4.cpp <https://github.com/godotengine/godot/"
"blob/master/editor/renames_map_3_to_4.cpp>`__ source file lists all "
"automatic renames performed by the project upgrade tool. Lines that are "
"commented out refer to API renames that :ref:`cannot be performed "
"automatically <doc_upgrading_to_godot_4_manual_rename>`."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:711
#, fuzzy
msgid "Porting editor settings"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:713
msgid ""
"Godot 3.x and 4.0 use different editor settings files. This means their "
"settings can be changed independently from each other."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:716
msgid ""
"If you wish to port over your Godot 3.x settings to Godot 4, open the :ref:"
"`editor settings folder <doc_data_paths_editor_data_paths>` and copy "
"``editor_settings-3.tres`` to ``editor_settings-4.tres`` while the Godot 4 "
"editor is closed."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.rst:723
msgid ""
"Many settings' names and categories have changed since Godot 3.x. Editor "
"settings whose name or category has changed won't carry over to Godot 4.0; "
"you will have to set their values again."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:4
msgid "Upgrading from Godot 4.0 to Godot 4.1"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:6
msgid ""
"For most games and apps made with 4.0, it should be relatively safe to "
"migrate to 4.1. This page intends to cover everything you need to pay "
"attention to when migrating your project."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:11
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:11
#, fuzzy
msgid "Breaking changes"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:13
msgid ""
"If you are migrating from 4.0 to 4.1, the breaking changes listed here might "
"affect you. Changes are grouped by areas/systems."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:18
msgid ""
"The GDExtension API completely breaks compatibility in 4.1, so it's not "
"included in the table below. See the :ref:"
"`updating_your_gdextension_for_godot_4_1` section for more information."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:22
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:43
msgid ""
"This article indicates whether each breaking change affects GDScript and "
"whether the C# breaking change is *binary compatible* or *source compatible*:"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:25
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:46
msgid ""
"**Binary compatible** - Existing binaries will load and execute successfully "
"without recompilation, and the run-time behavior won't change."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:27
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:48
msgid ""
"**Source compatible** - Source code will compile successfully without "
"changes when upgrading Godot."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:31
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:52
msgid "Core"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:34
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:52
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:66
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:76
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:91
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:107
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:123
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:139
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:169
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:179
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:201
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:55
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:65
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:117
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:131
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:153
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:165
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:209
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:219
msgid "Change"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:34
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:52
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:66
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:76
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:91
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:107
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:123
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:139
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:169
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:179
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:55
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:65
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:117
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:131
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:153
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:165
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:209
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:219
msgid "GDScript Compatible"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:34
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:52
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:66
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:76
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:91
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:107
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:123
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:139
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:169
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:179
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:55
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:65
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:117
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:131
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:153
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:165
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:209
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:219
msgid "C# Binary Compatible"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:34
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:52
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:66
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:76
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:91
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:107
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:123
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:139
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:169
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:179
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:55
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:65
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:117
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:131
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:153
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:165
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:209
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:219
msgid "C# Source Compatible"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:34
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:52
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:66
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:76
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:91
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:107
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:123
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:139
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:169
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:179
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:201
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:55
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:65
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:117
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:131
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:153
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:165
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:209
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:219
#, fuzzy
msgid "Introduced"
msgstr "Uvod"

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:36
#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:870
msgid "**Basis**"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:37
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:41
msgid "Method ``looking_at`` adds a new ``use_model_front`` optional parameter"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:37
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:39
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:41
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:43
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:45
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:56
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:57
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:59
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:79
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:81
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:83
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:84
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:94
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:96
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:97
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:98
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:100
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:126
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:128
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:130
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:132
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:142
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:147
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:172
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:184
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:185
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:186
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:191
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:58
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:68
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:69
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:70
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:71
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:72
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:73
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:74
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:75
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:76
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:77
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:78
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:79
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:80
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:81
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:82
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:83
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:84
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:85
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:86
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:87
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:88
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:89
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:90
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:91
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:92
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:93
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:94
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:96
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:97
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:98
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:99
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:100
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:101
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:102
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:103
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:104
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:105
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:106
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:107
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:108
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:109
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:110
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:120
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:121
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:122
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:124
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:134
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:135
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:137
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:138
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:140
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:141
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:142
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:143
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:144
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:146
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:156
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:157
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:158
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:175
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:176
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:177
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:191
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:192
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:194
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:195
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:196
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:197
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:198
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:199
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:200
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:222
msgid "|✔️|"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:37
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:41
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:83
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:84
msgid "`GH-76082`_"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:38
msgid "**Object**"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:39
msgid ""
"Method ``get_meta_list`` changes return type from ``PackedStringArray`` to "
"``Array[StringName]``"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:39
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:45
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:55
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:59
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:69
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:79
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:110
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:112
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:114
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:116
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:126
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:128
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:130
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:132
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:142
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:143
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:145
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:146
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:147
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:148
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:150
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:151
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:153
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:154
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:156
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:157
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:158
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:160
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:161
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:162
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:172
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:182
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:184
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:185
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:186
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:188
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:189
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:58
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:71
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:72
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:99
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:100
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:110
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:135
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:138
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:144
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:156
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:157
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:168
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:169
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:170
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:171
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:173
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:174
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:177
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:178
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:179
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:180
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:181
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:182
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:183
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:184
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:185
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:186
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:187
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:188
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:189
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:190
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:193
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:198
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:201
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:202
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:212
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:222
msgid "|❌|"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:39
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:59
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:79
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:126
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:128
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:130
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:132
msgid "`GH-76418`_"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:40
msgid "**Transform3D**"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:42
msgid "**UndoRedo**"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:43
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:191
msgid ""
"Method ``create_action`` adds a new ``backward_undo_ops`` optional parameter"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:43
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:56
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:57
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:79
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:81
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:83
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:84
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:94
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:96
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:97
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:98
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:100
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:128
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:132
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:191
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:86
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:87
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:88
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:94
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:108
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:120
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:121
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:122
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:124
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:134
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:137
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:143
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:146
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:158
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:168
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:169
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:170
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:171
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:174
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:212
msgid "|✔️ with compat|"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:43
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:191
msgid "`GH-76688`_"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:44
msgid "**WorkerThreadPool**"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:45
msgid ""
"Method ``wait_for_task_completion`` changes return type from ``void`` to "
"``Error``"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:45
msgid "`GH-77143`_"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:54
#, fuzzy
msgid "**AnimationNode**"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:55
msgid "Method ``_process`` adds a new ``test_only`` parameter"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:55
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:56
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:57
msgid "`GH-75759`_"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:56
msgid "Method ``blend_input`` adds a new ``test_only`` optional parameter"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:57
msgid "Method ``blend_node`` adds a new ``test_only`` optional parameter"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:58
msgid "**AnimationNodeStateMachinePlayback**"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:59
msgid ""
"Method ``get_travel_path`` changes return type from ``PackedStringArray`` to "
"``Array[StringName]``"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:63
msgid "2D nodes"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:68
msgid "**PathFollow2D**"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:69
msgid "Property ``lookahead`` removed"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:69
msgid "`GH-72842`_"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:73
msgid "3D nodes"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:78
#, fuzzy
msgid "**Geometry3D**"
msgstr "Opšti deo"

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:79
msgid ""
"Method ``segment_intersects_convex`` changes ``planes`` parameter type from "
"untyped ``Array`` to ``Array[Plane]``"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:80
msgid "**MeshInstance3D**"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:81
msgid ""
"Method ``create_multiple_convex_collisions`` adds a new ``settings`` "
"optional parameter"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:81
msgid "`GH-72152`_"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:82
msgid "**Node3D**"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:83
msgid "Method ``look_at`` adds a new ``use_model_front`` optional parameter"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:84
msgid ""
"Method ``look_at_from_position`` adds a new ``use_model_front`` optional "
"parameter"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:88
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:114
#, fuzzy
msgid "GUI nodes"
msgstr "Uvod / Početak"

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:93
msgid "**CodeEdit**"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:94
msgid ""
"Method ``add_code_completion_option`` adds a new ``location`` optional "
"parameter"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:94
msgid "`GH-75746`_"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:95
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:123
msgid "**RichTextLabel**"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:96
msgid "Method ``push_list`` adds a new ``bullet`` optional parameter"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:96
msgid "`GH-75017`_"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:97
msgid ""
"Method ``push_paragraph`` adds a new ``justification_flags`` optional "
"parameter"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:97
msgid "`GH-75250`_"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:98
msgid "Method ``push_paragraph`` adds a new ``tab_stops`` optional parameter"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:98
msgid "`GH-76401`_"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:99
msgid "**Tree**"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:100
msgid "Method ``edit_selected`` adds a new ``force_edit`` optional parameter"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:100
msgid "`GH-76794`_"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:109
msgid "**Area2D**"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:110
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:112
msgid "Property ``priority`` changes type from ``float`` to ``int``"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:110
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:112
msgid "`GH-72749`_"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:111
msgid "**Area3D**"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:113
msgid "**PhysicsDirectSpaceState2D**"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:114
msgid ""
"Method ``collide_shape`` changes return type from "
"``Array[PackedVector2Array]`` to ``Array[Vector2]``"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:114
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:116
msgid "`GH-75260`_"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:115
msgid "**PhysicsDirectSpaceState3D**"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:116
msgid ""
"Method ``collide_shape`` changes return type from "
"``Array[PackedVector3Array]`` to ``Array[Vector3]``"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:125
msgid "**RDShaderFile**"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:126
msgid ""
"Method ``get_version_list`` changes return type from ``PackedStringArray`` "
"to ``Array[StringName]``"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:127
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:139
msgid "**RenderingDevice**"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:128
msgid ""
"Method ``draw_list_begin`` changes ``storage_textures`` parameter type from "
"untyped ``Array`` to ``Array[RID]``"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:129
msgid "**RenderingServer**"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:130
msgid ""
"Method ``global_shader_parameter_get_list`` changes return type from "
"``PackedStringArray`` to ``Array[StringName]``"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:131
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:145
#, fuzzy
msgid "**SurfaceTool**"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:132
msgid ""
"Method ``add_triangle_fan`` changes ``tangents`` parameter type from untyped "
"``Array`` to ``Array[Plane]``"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:141
msgid "**NavigationAgent2D**"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:142
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:147
msgid "Method ``set_velocity`` replaced with ``velocity`` property"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:142
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:143
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:145
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:146
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:147
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:148
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:150
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:151
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:153
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:154
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:156
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:157
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:158
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:160
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:161
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:162
msgid "`GH-69988`_"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:143
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:148
msgid ""
"Property ``time_horizon`` split into ``time_horizon_agents`` and "
"``time_horizon_obstacles``"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:144
msgid "**NavigationAgent3D**"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:145
msgid "Property ``agent_height_offset`` renamed to ``path_height_offset``"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:146
msgid "Property ``ignore_y`` removed"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:149
msgid "**NavigationObstacle2D**"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:150
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:153
msgid "Property ``estimate_radius`` removed"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:151
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:154
msgid "Method ``get_rid`` renamed to ``get_agent_rid``"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:152
msgid "**NavigationObstacle3D**"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:155
msgid "**NavigationServer2D**"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:156
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:160
msgid ""
"Method ``agent_set_callback`` renamed to ``agent_set_avoidance_callback``"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:157
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:161
msgid "Method ``agent_set_target_velocity`` removed"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:158
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:162
msgid ""
"Method ``agent_set_time_horizon`` split into "
"``agent_set_time_horizon_agents`` and ``agent_set_time_horizon_obstacles``"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:159
msgid "**NavigationServer3D**"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:171
msgid "**WebRTCPeerConnectionExtension**"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:172
msgid ""
"Method ``_create_data_channel`` changes return type from ``Object`` to "
"``WebRTCDataChannel``"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:172
msgid "`GH-78237`_"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:176
#: ../../docs/tutorials/plugins/editor/index.rst:2
msgid "Editor plugins"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:181
msgid "**AnimationTrackEditPlugin**"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:182
msgid "Type ``AnimationTrackEditPlugin`` removed"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:182
msgid "`GH-76413`_"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:183
#, fuzzy
msgid "**EditorInterface**"
msgstr "**Za uređivač:**"

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:184
msgid ""
"Type ``EditorInterface`` changes inheritance from ``Node`` to ``Object``"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:184
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:185
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:186
msgid "`GH-76176`_"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:185
msgid ""
"Method ``set_movie_maker_enabled`` replaced with ``movie_maker_enabled`` "
"property"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:186
msgid ""
"Method ``is_movie_maker_enabled`` replaced with ``movie_maker_enabled`` "
"property"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:187
msgid "**EditorResourcePreviewGenerator**"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:188
msgid "Method ``_generate`` adds a new ``metadata`` parameter"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:188
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:189
msgid "`GH-64628`_"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:189
msgid "Method ``_generate_from_path`` adds a new ``metadata`` parameter"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:190
msgid "**EditorUndoRedoManager**"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:196
msgid "Behavior changes"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:198
msgid ""
"In 4.1 some behavior changes have been introduced, which might require you "
"to adjust your project."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:203
#, fuzzy
msgid "**SubViewportContainer**"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:204
msgid ""
"When input events should reach SubViewports and their children, "
"``SubViewportContainer.mouse_filter`` now needs to be ``MOUSE_FILTER_STOP`` "
"or ``MOUSE_FILTER_PASS``. See `GH-79271`_ for details."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:204
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:205
msgid "`GH-57894`_"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:205
msgid ""
"Multiple layered ``SubViewportContainer`` nodes, that should all receive "
"mouse input events, now need to be replaced by ``Area2D`` nodes. See "
"`GH-79128`_ for details."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:206
msgid "**Viewport**"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:207
msgid ""
"``Viewport`` nodes, that have Physics Picking enabled, now automatically set "
"InputEvents as handled. See `GH-79897`_ for workarounds."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:207
msgid "`GH-77595`_"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:243
msgid "Updating your GDExtension for 4.1"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:245
msgid ""
"GDExtension is still in beta. Until it's marked as stable, compatibility may "
"break when upgrading to a new minor version of Godot."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:248
msgid ""
"In order to fix a serious bug, in Godot 4.1 we had to break binary "
"compatibility in a big way and source compatibility in a small way."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:251
msgid ""
"This means that GDExtensions made for Godot 4.0 will need to be recompiled "
"for Godot 4.1 (using the  ``4.1`` branch of godot-cpp), with a small change "
"to their source code."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:254
msgid "In Godot 4.0, your \"entry_symbol\" function looks something like this:"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:268
msgid "However, for Godot 4.1, it should look like:"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:282
#, fuzzy
msgid "There are two small changes:"
msgstr "Ne postoje ograničenja prilikom korištenja Godot-a"

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:284
msgid ""
"The first argument changes from ``const GDExtensionInterface *p_interface`` "
"to ``GDExtensionInterfaceGetProcAddress p_get_proc_address``"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:285
msgid ""
"The constructor for the `init_obj` variable now receives "
"``p_get_proc_address`` as its first parameter"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:287
msgid ""
"You also need to add an extra ``compatibility_minimum`` line to your ``."
"gdextension`` file, so that it looks something like::"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.1.rst:294
msgid ""
"This lets Godot know that your GDExtension has been updated and is safe to "
"load in Godot 4.1."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:4
msgid "Upgrading from Godot 4.1 to Godot 4.2"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:6
msgid ""
"For most games and apps made with 4.1 it should be relatively safe to "
"migrate to 4.2. This page intends to cover everything you need to pay "
"attention to when migrating your project."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:13
msgid ""
"If you are migrating from 4.1 to 4.2, the breaking changes listed here might "
"affect you. Changes are grouped by areas/systems."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:18
msgid ""
"The :ref:`class_Mesh` resource format has changed in 4.2 to allow for "
"`vertex and attribute compression <https://github.com/godotengine/godot/"
"pull/81138>`__. This allows for improved rendering performance, especially "
"on platforms constrained by memory bandwidth such as mobile."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:23
msgid ""
"It is still possible to load the Godot 4.0-4.1 Mesh formats, but it is "
"**not** possible to load the Godot 4.2 Mesh format in prior Godot versions. "
"When opening a Godot project made with a version prior to 4.2, you may be "
"presented with an upgrade dialog that offers two options:"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:28
msgid ""
"**Restart & Upgrade:** Upgrades the mesh format for all meshes in the "
"project and saves the result to disk. Once chosen, this option prevents "
"downgrading the project to a Godot version prior to 4.2. Set up a version "
"control system and push your changes *before* choosing this option!"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:32
msgid ""
"**Upgrade Only:** Upgrades the mesh format in-memory without writing it to "
"disk. This allows downgrading the project to a Godot version older than 4.2 "
"if you need to do so in the future. The downside is that loading the project "
"will be slower every time as the mesh format needs to be upgraded every time "
"the project is loaded. These increased loading times will also affect the "
"exported project. The number and complexity of Mesh resources determines how "
"much loading times are affected."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:40
msgid ""
"If this dialog doesn't appear, use **Project > Tools > Upgrade Mesh Surfaces…"
"** at the top of the editor."
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:57
#, fuzzy
msgid "**Node**"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:58
msgid "Constant ``NOTIFICATION_NODE_RECACHE_REQUESTED`` removed"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:58
msgid "`GH-84419`_"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:67
#, fuzzy
msgid "**AnimationPlayer**"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:68
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:96
msgid ""
"Method ``_post_process_key_value`` moved to base class ``AnimationMixer``"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:68
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:69
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:70
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:71
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:72
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:73
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:74
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:75
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:76
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:77
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:78
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:79
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:80
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:81
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:82
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:83
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:84
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:85
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:86
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:87
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:88
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:89
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:90
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:91
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:92
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:93
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:94
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:96
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:97
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:98
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:99
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:100
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:101
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:102
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:103
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:104
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:105
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:106
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:107
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:108
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:109
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:110
msgid "`GH-80813`_"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:69
msgid "Method ``add_animation_library`` moved to base class ``AnimationMixer``"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:70
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:98
msgid "Method ``advance`` moved to base class ``AnimationMixer``"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:71
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:99
msgid "Signal ``animation_finished`` moved to base class ``AnimationMixer``"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:72
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:100
msgid "Signal ``animation_started`` moved to base class ``AnimationMixer``"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:73
msgid ""
"Signal ``animation_libraries_updated`` moved to base class ``AnimationMixer``"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:74
msgid ""
"Signal ``animation_list_changed`` moved to base class ``AnimationMixer``"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:75
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:101
msgid "Property ``audio_max_polyphony`` moved to base class ``AnimationMixer``"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:76
msgid "Signal ``caches_cleared`` moved to base class ``AnimationMixer``"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:77
msgid "Method ``clear_caches`` moved to base class ``AnimationMixer``"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:78
msgid "Method ``find_animation`` moved to base class ``AnimationMixer``"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:79
msgid ""
"Method ``find_animation_library`` moved to base class ``AnimationMixer``"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:80
msgid "Method ``get_animation`` moved to base class ``AnimationMixer``"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:81
msgid "Method ``get_animation_library`` moved to base class ``AnimationMixer``"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:82
msgid ""
"Method ``get_animation_library_list`` moved to base class ``AnimationMixer``"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:83
msgid "Method ``get_animation_list`` moved to base class ``AnimationMixer``"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:84
msgid "Method ``has_animation`` moved to base class ``AnimationMixer``"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:85
msgid "Method ``has_animation_library`` moved to base class ``AnimationMixer``"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:86
msgid ""
"Property ``method_call_mode`` renamed to ``callback_mode_method`` and moved "
"to base class ``AnimationMixer``"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:87
msgid ""
"Property ``playback_active`` renamed to ``active`` and moved to base class "
"``AnimationMixer``"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:88
msgid ""
"Property ``playback_process_mode`` renamed to ``callback_mode_process`` and "
"moved to base class ``AnimationMixer``"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:89
msgid ""
"Method ``remove_animation_library`` moved to base class ``AnimationMixer``"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:90
msgid ""
"Method ``rename_animation_library`` moved to base class ``AnimationMixer``"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:91
msgid "Property ``reset_on_save`` moved to base class ``AnimationMixer``"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:92
msgid "Property ``root_node`` moved to base class ``AnimationMixer``"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:93
msgid ""
"Method ``set_reset_on_save_enabled`` moved to base class ``AnimationMixer``"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:94
msgid "Method ``seek`` adds a new ``update_only`` optional parameter"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:95
#, fuzzy
msgid "**AnimationTree**"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:97
msgid "Property ``active`` moved to base class ``AnimationMixer``"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:102
msgid ""
"Method ``get_root_motion_position`` moved to base class ``AnimationMixer``"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:103
msgid ""
"Method ``get_root_motion_position_accumulator`` moved to base class "
"``AnimationMixer``"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:104
msgid ""
"Method ``get_root_motion_rotation`` moved to base class ``AnimationMixer``"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:105
msgid ""
"Method ``get_root_motion_rotation_accumulator`` moved to base class "
"``AnimationMixer``"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:106
msgid "Method ``get_root_motion_scale`` moved to base class ``AnimationMixer``"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:107
msgid ""
"Method ``get_root_motion_scale_accumulator`` moved to base class "
"``AnimationMixer``"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:108
msgid ""
"Property ``process_callback`` renamed to ``callback_mode_process`` and moved "
"to base class ``AnimationMixer``"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:109
msgid "Property ``root_motion_track``  moved to base class ``AnimationMixer``"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:110
msgid ""
"Property ``tree_root`` changes type from ``AnimationNode`` to "
"``AnimationRootNode``"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:119
msgid "**PopupMenu**"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:120
msgid ""
"Method ``add_icon_shortcut`` adds a new ``allow_echo`` optional parameter"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:120
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:121
msgid "`GH-36493`_"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:121
msgid "Method ``add_shortcut`` adds a new ``allow_echo`` optional parameter"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:122
msgid "Method ``clear`` adds a new ``free_submenus`` optional parameter"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:122
msgid "`GH-79965`_"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:124
msgid ""
"Method ``add_image`` adds new ``key``, ``pad``, ``tooltip``, and "
"``size_in_percent`` optional parameters"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:124
msgid "`GH-80410`_"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:133
msgid "**ImporterMesh**"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:134
msgid ""
"Method ``add_surface`` changes ``flags`` parameter type from ``uint32`` to "
"``uint64``"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:134
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:135
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:137
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:138
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:144
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:146
msgid "`GH-81138`_"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:135
msgid ""
"Method ``get_surface_format`` changes return type from ``uint32`` to "
"``uint64``"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:136
msgid "**MeshDataTool**"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:137
msgid ""
"Method ``commit_to_surface`` adds a new ``compression_flags`` optional "
"parameter"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:138
msgid "Method ``get_format`` changes return type from ``uint32`` to ``uint64``"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:140
msgid ""
"Enum field ``BarrierMask.BARRIER_MASK_RASTER`` changes value from ``1`` to "
"``9``"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:140
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:141
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:142
msgid "`GH-79911`_"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:141
msgid ""
"Enum field ``BarrierMask.BARRIER_MASK_ALL_BARRIERS`` changes value from "
"``7`` to ``32767``"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:142
msgid ""
"Enum field ``BarrierMask.BARRIER_MASK_NO_BARRIER`` changes value from ``8`` "
"to ``32768``"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:143
msgid ""
"Method ``shader_create_from_bytecode`` adds a new ``placeholder_rid`` "
"optional parameter"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:143
msgid "`GH-79606`_"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:144
msgid ""
"Method ``shader_get_vertex_input_attribute_ask`` changes return type from "
"``uint32`` to ``uint64``"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:146
msgid ""
"Method ``commit`` changes ``flags`` parameter type from ``uint32`` to "
"``uint64``"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:150
#, fuzzy
msgid "Text"
msgstr "Tutorijali"

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:155
#: ../../docs/tutorials/ui/gui_skinning.rst:65
msgid "**Font**"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:156
msgid "Method ``set_fallbacks`` replaced with ``fallbacks`` property"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:156
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:157
msgid "`GH-78266`_"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:157
msgid "Method ``get_fallbacks`` replaced with ``fallbacks`` property"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:158
msgid ""
"Method ``find_variation`` adds new ``spacing_top``, ``spacing_bottom``, "
"``spacing_space``, and ``spacing_glyph`` optional parameters"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:158
msgid "`GH-80954`_"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:162
#: ../../docs/contributing/development/compiling/optimizing_for_size.rst:186
msgid "GraphEdit"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:167
msgid "**GraphEdit**"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:168
msgid ""
"Property ``arrange_nodes_button_hidden`` renamed to ``show_arrange_button``"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:168
msgid "`GH-81582`_"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:169
msgid "Method ``get_zoom_hbox`` renamed to ``get_menu_hbox``"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:169
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:170
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:171
msgid "`GH-79308`_"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:170
msgid "Property ``snap_distance`` renamed to ``snapping_distance``"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:171
msgid "Property ``use_snap`` renamed to ``snapping_enabled``"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:172
#, fuzzy
msgid "**GraphNode**"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:173
msgid "Property ``comment`` removed"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:173
msgid "`GH-79307`_"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:174
msgid ""
"Signal ``close_request`` renamed to ``delete_request`` and moved to base "
"class ``GraphElement``"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:174
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:175
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:176
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:177
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:178
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:179
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:180
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:181
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:182
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:183
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:184
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:185
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:186
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:187
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:188
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:189
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:190
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:191
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:192
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:193
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:194
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:195
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:196
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:197
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:198
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:199
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:200
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:201
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:202
msgid "`GH-79311`_"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:175
#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:176
msgid "Property ``draggable`` moved to base class ``GraphElement``"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:177
msgid "Signal ``dragged`` moved to base class ``GraphElement``"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:178
msgid "Method ``get_connection_input_color`` removed"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:179
msgid "Method ``get_connection_input_count`` removed"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:180
msgid "Method ``get_connection_input_height`` removed"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:181
msgid "Method ``get_connection_input_position`` removed"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:182
msgid "Method ``get_connection_input_slot`` removed"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:183
msgid "Method ``get_connection_input_type`` removed"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:184
msgid "Method ``get_connection_output_color`` removed"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:185
msgid "Method ``get_connection_output_count`` removed"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:186
msgid "Method ``get_connection_output_height`` removed"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:187
msgid "Method ``get_connection_output_position`` removed"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:188
msgid "Method ``get_connection_output_slot`` removed"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:189
msgid "Method ``get_connection_output_type`` removed"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:190
msgid "Property ``language`` removed"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:191
msgid "Signal ``node_deselected`` moved to base class ``GraphElement``"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:192
msgid "Signal ``node_selected`` moved to base class ``GraphElement``"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:193
msgid "Property ``overlay`` removed"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:194
msgid "Property ``position_offset`` moved to base class ``GraphElement``"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:195
msgid "Signal ``position_offset_changed`` moved to base class ``GraphElement``"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:196
msgid "Signal ``raise_request`` moved to base class ``GraphElement``"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:197
msgid "Property ``resizable`` moved to base class ``GraphElement``"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:198
msgid "Signal ``resize_request`` moved to base class ``GraphElement``"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:199
msgid "Property ``selectable`` moved to base class ``GraphElement``"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:200
msgid "Property ``selected`` moved to base class ``GraphElement``"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:201
msgid "Property ``show_close`` removed"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:202
msgid "Property ``text_direction`` removed"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:206
#, fuzzy
msgid "TileMap"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:211
msgid "**TileMap**"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:212
msgid "Property ``cell_quadrant_size`` renamed to ``rendering_quadrant_size``"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:212
msgid "`GH-81070`_"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:221
#, fuzzy
msgid "**XRInterface**"
msgstr "**Za uređivač:**"

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:222
msgid "Property ``environment_blend_mode`` added"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:222
msgid "`GH-81561`_"
msgstr ""

#: ../../docs/tutorials/migrating/upgrading_to_godot_4.2.rst:227
msgid ""
"This change breaks compatibility in C# because the new property conflicts "
"with the name of an existing enum and the C# bindings generator gives "
"priority to properties, so the enum type was renamed from "
"``EnvironmentBlendMode`` to ``EnvironmentBlendModeEnum``."
msgstr ""

#: ../../docs/tutorials/2d/index.rst:26
msgid "Physics and movement"
msgstr ""

#: ../../docs/tutorials/2d/index.rst:35
#: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:231
#: ../../docs/tutorials/3d/index.rst:47
#: ../../docs/tutorials/3d/procedural_geometry/index.rst:84
msgid "Tools"
msgstr ""

#: ../../docs/tutorials/2d/canvas_layers.rst:4
msgid "Canvas layers"
msgstr ""

#: ../../docs/tutorials/2d/canvas_layers.rst:7
msgid "Viewport and Canvas items"
msgstr ""

#: ../../docs/tutorials/2d/canvas_layers.rst:9
msgid ""
":ref:`CanvasItem <class_CanvasItem>` is the base for all 2D nodes, be it "
"regular 2D nodes, such as :ref:`Node2D <class_Node2D>`, or :ref:`Control "
"<class_Control>`. Both inherit from :ref:`CanvasItem <class_CanvasItem>`. "
"You can arrange canvas items in trees. Each item will inherit its parent's "
"transform: when the parent moves, its children move too."
msgstr ""

#: ../../docs/tutorials/2d/canvas_layers.rst:15
msgid ""
"CanvasItem nodes, and nodes inheriting from them, are direct or indirect "
"children of a :ref:`Viewport <class_Viewport>`, that displays them."
msgstr ""

#: ../../docs/tutorials/2d/canvas_layers.rst:18
msgid ""
"The Viewport's property :ref:`Viewport.canvas_transform "
"<class_Viewport_property_canvas_transform>`, allows to apply a custom :ref:"
"`Transform2D <class_Transform2D>` transform to the CanvasItem hierarchy it "
"contains. Nodes such as :ref:`Camera2D <class_Camera2D>` work by changing "
"that transform."
msgstr ""

#: ../../docs/tutorials/2d/canvas_layers.rst:24
msgid ""
"To achieve effects like scrolling, manipulating the canvas transform "
"property is more efficient than moving the root canvas item and the entire "
"scene with it."
msgstr ""

#: ../../docs/tutorials/2d/canvas_layers.rst:27
msgid ""
"Usually though, we don't want *everything* in the game or app to be subject "
"to the canvas transform. For example:"
msgstr ""

#: ../../docs/tutorials/2d/canvas_layers.rst:30
msgid ""
"**Parallax Backgrounds**: Backgrounds that move slower than the rest of the "
"stage."
msgstr ""

#: ../../docs/tutorials/2d/canvas_layers.rst:32
msgid ""
"**UI**: Think of a user interface (UI) or head-up display (HUD) superimposed "
"on our view of the game world. We want a life counter, score display and "
"other elements to retain their screen positions even when our view of the "
"game world changes."
msgstr ""

#: ../../docs/tutorials/2d/canvas_layers.rst:33
msgid ""
"**Transitions**: We may want visual effects used for transitions (fades, "
"blends) to remain at a fixed screen location."
msgstr ""

#: ../../docs/tutorials/2d/canvas_layers.rst:35
msgid "How to solve these problems in a single scene tree?"
msgstr ""

#: ../../docs/tutorials/2d/canvas_layers.rst:38
msgid "CanvasLayers"
msgstr ""

#: ../../docs/tutorials/2d/canvas_layers.rst:40
msgid ""
"The answer is :ref:`CanvasLayer <class_CanvasLayer>`, which is a node that "
"adds a separate 2D rendering layer for all its children and grand-children. "
"Viewport children will draw by default at layer \"0\", while a CanvasLayer "
"will draw at any numeric layer. Layers with a greater number will be drawn "
"above those with a smaller number. CanvasLayers also have their own "
"transform and do not depend on the transform of other layers. This allows "
"the UI to be fixed in screen-space while our view on the game world changes."
msgstr ""

#: ../../docs/tutorials/2d/canvas_layers.rst:49
msgid ""
"An example of this is creating a parallax background. This can be done with "
"a CanvasLayer at layer \"-1\". The screen with the points, life counter and "
"pause button can also be created at layer \"1\"."
msgstr ""

#: ../../docs/tutorials/2d/canvas_layers.rst:53
msgid "Here's a diagram of how it looks:"
msgstr ""

#: ../../docs/tutorials/2d/canvas_layers.rst:57
msgid ""
"CanvasLayers are independent of tree order, and they only depend on their "
"layer number, so they can be instantiated when needed."
msgstr ""

#: ../../docs/tutorials/2d/canvas_layers.rst:60
msgid ""
"CanvasLayers aren't necessary to control the drawing order of nodes. The "
"standard way to ensuring that a node is correctly drawn 'in front' or "
"'behind' others is to manipulate the order of the nodes in the scene panel. "
"Perhaps counterintuitively, the topmost nodes in the scene panel are drawn "
"on *behind* lower ones in the viewport. 2D nodes also have the :ref:"
"`CanvasItem.z_index <class_CanvasItem_property_z_index>` property for "
"controlling their drawing order."
msgstr ""

#: ../../docs/tutorials/2d/2d_transforms.rst:4
msgid "Viewport and canvas transforms"
msgstr ""

#: ../../docs/tutorials/2d/2d_transforms.rst:9
msgid ""
"This is an overview of the 2D transforms going on for nodes from the moment "
"they draw their content locally to the time they are drawn onto the screen. "
"This overview discusses very low level details of the engine."
msgstr ""

#: ../../docs/tutorials/2d/2d_transforms.rst:13
msgid ""
"The goal of this tutorial is to teach a way for feeding input events to the "
"Input with a position in the correct coordinate system."
msgstr ""

#: ../../docs/tutorials/2d/2d_transforms.rst:16
msgid ""
"A more extensive description of all coordinate systems and 2d transforms is "
"available in :ref:`doc_2d_coordinate_systems`."
msgstr ""

#: ../../docs/tutorials/2d/2d_transforms.rst:20
msgid "Canvas transform"
msgstr ""

#: ../../docs/tutorials/2d/2d_transforms.rst:22
msgid ""
"As mentioned in the previous tutorial, :ref:`doc_canvas_layers`, every "
"CanvasItem node (remember that Node2D and Control based nodes use CanvasItem "
"as their common root) will reside in a *Canvas Layer*. Every canvas layer "
"has a transform (translation, rotation, scale, etc.) that can be accessed as "
"a :ref:`Transform2D <class_Transform2D>`."
msgstr ""

#: ../../docs/tutorials/2d/2d_transforms.rst:28
msgid ""
"Also covered in the previous tutorial, nodes are drawn by default in Layer "
"0, in the built-in canvas. To put nodes in a different layer, a :ref:"
"`CanvasLayer <class_CanvasLayer>` node can be used."
msgstr ""

#: ../../docs/tutorials/2d/2d_transforms.rst:33
msgid "Global canvas transform"
msgstr ""

#: ../../docs/tutorials/2d/2d_transforms.rst:35
msgid ""
"Viewports also have a Global Canvas transform (also a :ref:`Transform2D "
"<class_Transform2D>`). This is the master transform and affects all "
"individual *Canvas Layer* transforms. Generally, this is primarily used in "
"Godot's CanvasItem Editor."
msgstr ""

#: ../../docs/tutorials/2d/2d_transforms.rst:41
msgid "Stretch transform"
msgstr ""

#: ../../docs/tutorials/2d/2d_transforms.rst:43
msgid ""
"Finally, viewports have a *Stretch Transform*, which is used when resizing "
"or stretching the screen. This transform is used internally (as described "
"in :ref:`doc_multiple_resolutions`), but can also be manually set on each "
"viewport."
msgstr ""

#: ../../docs/tutorials/2d/2d_transforms.rst:48
msgid ""
"Input events are multiplied by this transform but lack the ones above. To "
"convert InputEvent coordinates to local CanvasItem coordinates, the :ref:"
"`CanvasItem.make_input_local() <class_CanvasItem_method_make_input_local>` "
"function was added for convenience."
msgstr ""

#: ../../docs/tutorials/2d/2d_transforms.rst:54
#, fuzzy
msgid "Window transform"
msgstr "Windows"

#: ../../docs/tutorials/2d/2d_transforms.rst:56
msgid ""
"The root viewport is a :ref:`Window <class_Window>`. In order to scale and "
"position the *Window's* content as described in :ref:"
"`doc_multiple_resolutions`, each :ref:`Window <class_Window>` contains a "
"*window transform*. It is for example responsible for the black bars at the "
"*Window's* sides so that the *Viewport* is displayed with a fixed aspect "
"ratio."
msgstr ""

#: ../../docs/tutorials/2d/2d_transforms.rst:63
msgid "Transform order"
msgstr ""

#: ../../docs/tutorials/2d/2d_transforms.rst:65
msgid ""
"To convert a CanvasItem local coordinate to an actual screen coordinate, the "
"following chain of transforms must be applied:"
msgstr ""

#: ../../docs/tutorials/2d/2d_transforms.rst:71
msgid "Transform functions"
msgstr ""

#: ../../docs/tutorials/2d/2d_transforms.rst:73
msgid ""
"The above graphic shows some available transform functions. All transforms "
"are directed from right to left, this means multiplying a transform with a "
"coordinate results in a coordinate system further to the left, multiplying "
"the :ref:`affine inverse <class_Transform2D_method_affine_inverse>` of a "
"transform results in a coordinate system further to the right:"
msgstr ""

#: ../../docs/tutorials/2d/2d_transforms.rst:91
msgid ""
"Finally, then, to convert a CanvasItem local coordinates to screen "
"coordinates, just multiply in the following order:"
msgstr ""

#: ../../docs/tutorials/2d/2d_transforms.rst:103
msgid ""
"Keep in mind, however, that it is generally not desired to work with screen "
"coordinates. The recommended approach is to simply work in Canvas "
"coordinates (``CanvasItem.get_global_transform()``), to allow automatic "
"screen resolution resizing to work properly."
msgstr ""

#: ../../docs/tutorials/2d/2d_transforms.rst:109
msgid "Feeding custom input events"
msgstr ""

#: ../../docs/tutorials/2d/2d_transforms.rst:111
msgid ""
"It is often desired to feed custom input events to the game. With the above "
"knowledge, to correctly do this in the focused window, it must be done the "
"following way:"
msgstr ""

#: ../../docs/tutorials/2d/2d_lights_and_shadows.rst:4
msgid "2D lights and shadows"
msgstr ""

#: ../../docs/tutorials/2d/2d_lights_and_shadows.rst:9
msgid ""
"By default, 2D scenes in Godot are unshaded, with no lights and shadows "
"visible. While this is fast to render, unshaded scenes can look bland. Godot "
"provides the ability to use real-time 2D lighting and shadows, which can "
"greatly enhance the sense of depth in your project."
msgstr ""

#: ../../docs/tutorials/2d/2d_lights_and_shadows.rst:18
msgid "No 2D lights or shadows, scene is unshaded"
msgstr ""

#: ../../docs/tutorials/2d/2d_lights_and_shadows.rst:24
msgid "2D lights enabled (without shadows)"
msgstr ""

#: ../../docs/tutorials/2d/2d_lights_and_shadows.rst:30
msgid "2D lights and shadows enabled"
msgstr ""

#: ../../docs/tutorials/2d/2d_lights_and_shadows.rst:35
msgid "There are several nodes involved in a complete 2D lighting setup:"
msgstr ""

#: ../../docs/tutorials/2d/2d_lights_and_shadows.rst:37
msgid ""
":ref:`CanvasModulate <class_CanvasModulate>` (to darken the rest of the "
"scene)"
msgstr ""

#: ../../docs/tutorials/2d/2d_lights_and_shadows.rst:38
msgid ""
":ref:`PointLight2D <class_PointLight2D>` (for omnidirectional or spot lights)"
msgstr ""

#: ../../docs/tutorials/2d/2d_lights_and_shadows.rst:39
msgid ""
":ref:`DirectionalLight2D <class_DirectionalLight2D>` (for sunlight or "
"moonlight)"
msgstr ""

#: ../../docs/tutorials/2d/2d_lights_and_shadows.rst:40
msgid ""
":ref:`LightOccluder2D <class_LightOccluder2D>` (for light shadow casters)"
msgstr ""

#: ../../docs/tutorials/2d/2d_lights_and_shadows.rst:41
msgid "Other 2D nodes that receive lighting, such as Sprite2D or TileMap."
msgstr ""

#: ../../docs/tutorials/2d/2d_lights_and_shadows.rst:43
msgid ""
":ref:`CanvasModulate <class_CanvasModulate>` is used to darken the scene by "
"specifying a color that will act as the base \"ambient\" color. This is the "
"final lighting color in areas that are *not* reached by any 2D light. "
"Without a CanvasModulate node, the final scene would look too bright as 2D "
"lights would only brighten the existing unshaded appearance (which appears "
"fully lit)."
msgstr ""

#: ../../docs/tutorials/2d/2d_lights_and_shadows.rst:49
msgid ""
":ref:`Sprite2Ds <class_Sprite2D>` are used to display the textures for the "
"light blobs, the background, and for the shadow casters."
msgstr ""

#: ../../docs/tutorials/2d/2d_lights_and_shadows.rst:52
msgid ""
":ref:`PointLight2Ds <class_PointLight2D>` are used to light the scene. The "
"way a light typically works is by adding a selected texture over the rest of "
"the scene to simulate lighting."
msgstr ""

#: ../../docs/tutorials/2d/2d_lights_and_shadows.rst:56
msgid ""
":ref:`LightOccluder2Ds <class_LightOccluder2D>` are used to tell the shader "
"which parts of the scene cast shadows. These occluders can be placed as "
"independent nodes or can be part of a TileMap node."
msgstr ""

#: ../../docs/tutorials/2d/2d_lights_and_shadows.rst:60
msgid ""
"The shadows appear only on areas covered by the :ref:`PointLight2D "
"<class_PointLight2D>` and their direction is based on the center of the :ref:"
"`Light <class_PointLight2D>`."
msgstr ""

#: ../../docs/tutorials/2d/2d_lights_and_shadows.rst:66
msgid ""
"The background color does **not** receive any lighting. If you want light to "
"be cast on the background, you need to add a visual representation for the "
"background, such as a Sprite2D."
msgstr ""

#: ../../docs/tutorials/2d/2d_lights_and_shadows.rst:70
msgid ""
"The Sprite2D's **Region** properties can be helpful to quickly create a "
"repeating background texture, but remember to also set **Texture > Repeat** "
"to **Enabled** in the Sprite2D's properties."
msgstr ""

#: ../../docs/tutorials/2d/2d_lights_and_shadows.rst:75
msgid "Point lights"
msgstr ""

#: ../../docs/tutorials/2d/2d_lights_and_shadows.rst:77
msgid ""
"Point lights (also called positional lights) are the most common element in "
"2D lighting. Point lights can be used to represent light from torches, fire, "
"projectiles, etc."
msgstr ""

#: ../../docs/tutorials/2d/2d_lights_and_shadows.rst:81
msgid "PointLight2D offers the following properties to tweak in the inspector:"
msgstr ""

#: ../../docs/tutorials/2d/2d_lights_and_shadows.rst:83
msgid ""
"**Texture:** The texture to use as a light source. The texture's size "
"determines the size of the light. The texture may have an alpha channel, "
"which is useful when using Light2D's **Mix** blend mode, but it is not "
"required if using the **Add** (default) or **Subtract** blend modes."
msgstr ""

#: ../../docs/tutorials/2d/2d_lights_and_shadows.rst:87
msgid ""
"**Offset:** The offset for the light texture. Unlike when you move the light "
"node, changing the offset does *not* cause shadows to move."
msgstr ""

#: ../../docs/tutorials/2d/2d_lights_and_shadows.rst:89
msgid ""
"**Texture Scale:** The multiplier for the light's size. Higher values will "
"make the light extend out further. Larger lights have a higher performance "
"cost as they affect more pixels on screen, so consider this before "
"increasing a light's size."
msgstr ""

#: ../../docs/tutorials/2d/2d_lights_and_shadows.rst:93
msgid ""
"**Height:** The light's virtual height with regards to normal mapping. By "
"default, the light is very close to surfaces receiving lights. This will "
"make lighting hardly visible if normal mapping is used, so consider "
"increasing this value. Adjusting the light's height only makes a visible "
"difference on surfaces that use normal mapping."
msgstr ""

#: ../../docs/tutorials/2d/2d_lights_and_shadows.rst:99
msgid ""
"If you don't have a pre-made texture to use in a light, you can use this "
"\"neutral\" point light texture (right-click > **Save Image As…**):"
msgstr ""

#: ../../docs/tutorials/2d/2d_lights_and_shadows.rst:106
#, fuzzy
msgid "Neutral point light texture"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/2d/2d_lights_and_shadows.rst:108
msgid ""
"If you need different falloff, you can procedurally create a texture by "
"assigning a **New GradientTexture2D** on the light's **Texture** property. "
"After creating the resource, expand its **Fill** section and set the fill "
"mode to **Radial**. You will then have to adjust the gradient itself to "
"start from opaque white to transparent white, and move its starting location "
"to be in the center."
msgstr ""

#: ../../docs/tutorials/2d/2d_lights_and_shadows.rst:115
#: ../../docs/tutorials/3d/lights_and_shadows.rst:171
msgid "Directional light"
msgstr ""

#: ../../docs/tutorials/2d/2d_lights_and_shadows.rst:117
msgid ""
"New in Godot 4.0 is the ability to have directional lighting in 2D. "
"Directional lighting is used to represent sunlight or moonlight. Light rays "
"are casted parallel to each other, as if the sun or moon was infinitely far "
"away from the surface that is receiving the light."
msgstr ""

#: ../../docs/tutorials/2d/2d_lights_and_shadows.rst:122
msgid "DirectionalLight2D offers the following properties:"
msgstr ""

#: ../../docs/tutorials/2d/2d_lights_and_shadows.rst:124
msgid ""
"**Height:** The light's virtual height with regards to normal mapping "
"(``0.0`` = parallel to surfaces, ``1.0`` = perpendicular to surfaces). By "
"default, the light is fully parallel with the surfaces receiving lights. "
"This will make lighting hardly visible if normal mapping is used, so "
"consider increasing this value. Adjusting the light's height only makes a "
"visual difference on surfaces that use normal mapping. **Height** does not "
"affect shadows' appearance."
msgstr ""

#: ../../docs/tutorials/2d/2d_lights_and_shadows.rst:130
msgid ""
"**Max Distance:** The maximum distance from the camera center objects can be "
"before their shadows are culled (in pixels). Decreasing this value can "
"prevent objects located outside the camera from casting shadows (while also "
"improving performance). Camera2D zoom is not taken into account by **Max "
"Distance**, which means that at higher zoom values, shadows will appear to "
"fade out sooner when zooming onto a given point."
msgstr ""

#: ../../docs/tutorials/2d/2d_lights_and_shadows.rst:139
msgid ""
"Directional shadows will always appear to be infinitely long, regardless of "
"the value of the **Height** property. This is a limitation of the shadow "
"rendering method used for 2D lights in Godot."
msgstr ""

#: ../../docs/tutorials/2d/2d_lights_and_shadows.rst:143
msgid ""
"To have directional shadows that are not infinitely long, you should disable "
"shadows in the DirectionalLight2D and use a custom shader that reads from "
"the 2D signed distance field instead. This distance field is automatically "
"generated from LightOccluder2D nodes present in the scene."
msgstr ""

#: ../../docs/tutorials/2d/2d_lights_and_shadows.rst:149
msgid "Common light properties"
msgstr ""

#: ../../docs/tutorials/2d/2d_lights_and_shadows.rst:151
msgid ""
"Both PointLight2D and DirectionalLight2D offer common properties, which are "
"part of the Light2D base class:"
msgstr ""

#: ../../docs/tutorials/2d/2d_lights_and_shadows.rst:154
msgid ""
"**Enabled:** Allows toggling the light's visibility. Unlike hiding the light "
"node, disabling this property will not hide the light's children."
msgstr ""

#: ../../docs/tutorials/2d/2d_lights_and_shadows.rst:156
msgid ""
"**Editor Only:** If enabled, the light is only visible within the editor. It "
"will be automatically disabled in the running project."
msgstr ""

#: ../../docs/tutorials/2d/2d_lights_and_shadows.rst:158
msgid "**Color:** The light's color."
msgstr ""

#: ../../docs/tutorials/2d/2d_lights_and_shadows.rst:159
msgid ""
"**Energy:** The light's intensity multiplier. Higher values result in a "
"brighter light."
msgstr ""

#: ../../docs/tutorials/2d/2d_lights_and_shadows.rst:160
msgid ""
"**Blend Mode:** The blending formula used for light computations. The "
"default **Add** is suited for most use cases. **Subtract** can be used for "
"negative lights, which are not physically accurate but can be used for "
"special effects. The **Mix** blend mode mixes the value of pixels "
"corresponding to the light's texture with the values of pixels under it by "
"linear interpolation."
msgstr ""

#: ../../docs/tutorials/2d/2d_lights_and_shadows.rst:165
msgid "**Range > Z Min:** The lowest Z index affected by the light."
msgstr ""

#: ../../docs/tutorials/2d/2d_lights_and_shadows.rst:166
msgid "**Range > Z Max:** The highest Z index affected by the light."
msgstr ""

#: ../../docs/tutorials/2d/2d_lights_and_shadows.rst:167
msgid "**Range > Layer Min:** The lowest visual layer affected by the light."
msgstr ""

#: ../../docs/tutorials/2d/2d_lights_and_shadows.rst:168
msgid "**Range > Layer Max:** The highest visual layer affected by the light."
msgstr ""

#: ../../docs/tutorials/2d/2d_lights_and_shadows.rst:169
msgid ""
"**Range > Item Cull Mask:** Controls which nodes receive light from this "
"node, depending on the other nodes' enabled visual layers **Occluder Light "
"Mask**. This can be used to prevent certain objects from receiving light."
msgstr ""

#: ../../docs/tutorials/2d/2d_lights_and_shadows.rst:176
#, fuzzy
msgid "Setting up shadows"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/2d/2d_lights_and_shadows.rst:178
msgid ""
"After enabling the **Shadow > Enabled** property on a PointLight2D or "
"DirectionalLight2D node, you will not see any visual difference initially. "
"This is because no nodes in your scene have any *occluders* yet, which are "
"used as a basis for shadow casting."
msgstr ""

#: ../../docs/tutorials/2d/2d_lights_and_shadows.rst:183
msgid ""
"For shadows to appear in the scene, LightOccluder2D nodes must be added to "
"the scene. These nodes must also have occluder polygons that are designed to "
"match the sprite's outline."
msgstr ""

#: ../../docs/tutorials/2d/2d_lights_and_shadows.rst:187
msgid ""
"Along with their polygon resource (which must be set to have any visual "
"effect), LightOccluder2D nodes have 2 properties:"
msgstr ""

#: ../../docs/tutorials/2d/2d_lights_and_shadows.rst:190
msgid ""
"**SDF Collision:** If enabled, the occluder will be part of a real-time "
"generated *signed distance field* that can be used in custom shaders. When "
"not using custom shaders that read from this SDF, enabling this makes no "
"visual difference and has no performance cost, so this is enabled by default "
"for convenience."
msgstr ""

#: ../../docs/tutorials/2d/2d_lights_and_shadows.rst:195
msgid ""
"**Occluder Light Mask:** This is used in tandem with PointLight2D and "
"DirectionalLight2D's **Shadow > Item Cull Mask** property to control which "
"objects cast shadows for each light. This can be used to prevent specific "
"objects from casting shadows."
msgstr ""

#: ../../docs/tutorials/2d/2d_lights_and_shadows.rst:200
#, fuzzy
msgid "There are two ways to create light occluders:"
msgstr "Ne postoje ograničenja prilikom korištenja Godot-a"

#: ../../docs/tutorials/2d/2d_lights_and_shadows.rst:203
msgid "Automatically generating a light occluder"
msgstr ""

#: ../../docs/tutorials/2d/2d_lights_and_shadows.rst:205
msgid ""
"Occluders can be created automatically from Sprite2D nodes by selecting the "
"node, clicking the **Sprite2D** menu at the top of the 2D editor then "
"choosing **Create LightOccluder2D Sibling**."
msgstr ""

#: ../../docs/tutorials/2d/2d_lights_and_shadows.rst:209
msgid ""
"In the dialog that appears, an outline will surround your sprite's edges. If "
"the outline matches the sprite's edges closely, you can click **OK**. If the "
"outline is too far away from the sprite's edges (or is \"eating\" into the "
"sprite's edges), adjust **Grow (pixels)** and **Shrink (pixels)**, then "
"click **Update Preview**. Repeat this operation until you get satisfactory "
"results."
msgstr ""

#: ../../docs/tutorials/2d/2d_lights_and_shadows.rst:216
msgid "Manually drawing a light occluder"
msgstr ""

#: ../../docs/tutorials/2d/2d_lights_and_shadows.rst:218
msgid ""
"Create a LightOccluder2D node, then select the node and click the \"+\" "
"button at the top of the 2D editor. When asked to create a polygon resource, "
"answer **Yes**. You can then start drawing an occluder polygon by clicking "
"to create new points. You can remove existing points by right-clicking them, "
"and you can create new points from the existing line by clicking on the line "
"then dragging."
msgstr ""

#: ../../docs/tutorials/2d/2d_lights_and_shadows.rst:224
msgid ""
"The following properties can be adjusted on 2D lights that have shadows "
"enabled:"
msgstr ""

#: ../../docs/tutorials/2d/2d_lights_and_shadows.rst:226
msgid ""
"**Color:** The color of shaded areas. By default, shaded areas are fully "
"black, but this can be changed for artistic purposes. The color's alpha "
"channel controls how much the shadow is tinted by the specified color."
msgstr ""

#: ../../docs/tutorials/2d/2d_lights_and_shadows.rst:229
msgid ""
"**Filter:** The filter mode to use for shadows. The default **None** is the "
"fastest to render, and is well suited for games with a pixel art aesthetic "
"(due to its \"blocky\" visuals). If you want a soft shadow, use **PCF5** "
"instead. **PCF13** is even softer, but is the most demanding to render. "
"PCF13 should only be used for a few lights at once due to its high rendering "
"cost."
msgstr ""

#: ../../docs/tutorials/2d/2d_lights_and_shadows.rst:234
msgid ""
"**Filter Smooth:** Controls how much softening is applied to shadows when "
"**Filter** is set to **PCF5** or **PCF13**. Higher values result in a softer "
"shadow, but may cause banding artifacts to be visible (especially with PCF5)."
msgstr ""

#: ../../docs/tutorials/2d/2d_lights_and_shadows.rst:237
msgid ""
"**Item Cull Mask:** Controls which LightOccluder2D nodes cast shadows, "
"depending on their respective **Occluder Light Mask** properties."
msgstr ""

#: ../../docs/tutorials/2d/2d_lights_and_shadows.rst:244
msgid "Hard shadows"
msgstr ""

#: ../../docs/tutorials/2d/2d_lights_and_shadows.rst:250
msgid "Soft shadows (PCF13, Filter Smooth 1.5)"
msgstr ""

#: ../../docs/tutorials/2d/2d_lights_and_shadows.rst:256
msgid ""
"Soft shadows with streaking artifacts due to Filter Smooth being too high "
"(PCF5, Filter Smooth 4)"
msgstr ""

#: ../../docs/tutorials/2d/2d_lights_and_shadows.rst:259
msgid "Occluder draw order"
msgstr ""

#: ../../docs/tutorials/2d/2d_lights_and_shadows.rst:261
msgid ""
"**LightOccluder2Ds follows the usual 2D drawing order.** This is important "
"for 2D lighting, as this is how you control whether the occluder should "
"occlude the sprite itself or not."
msgstr ""

#: ../../docs/tutorials/2d/2d_lights_and_shadows.rst:265
msgid ""
"If the LightOccluder2D node is a *sibling* of the sprite, the occluder will "
"occlude the sprite itself if it's placed *below* the sprite in the scene "
"tree."
msgstr ""

#: ../../docs/tutorials/2d/2d_lights_and_shadows.rst:268
msgid ""
"If the LightOccluder2D node is a *child* of the sprite, the occluder will "
"occlude the sprite itself if **Show Behind Parent** is disabled on the "
"LightOccluder2D node (which is the default)."
msgstr ""

#: ../../docs/tutorials/2d/2d_lights_and_shadows.rst:273
msgid "Normal and specular maps"
msgstr ""

#: ../../docs/tutorials/2d/2d_lights_and_shadows.rst:275
msgid ""
"Normal maps and specular maps can greatly enhance the sense of depth of your "
"2D lighting. Similar to how these work in 3D rendering, normal maps can help "
"make lighting look less flat by varying its intensity depending on the "
"direction of the surface receiving light (on a per-pixel basis). Specular "
"maps further help improve visuals by making some of the light reflect back "
"to the viewer."
msgstr ""

#: ../../docs/tutorials/2d/2d_lights_and_shadows.rst:281
msgid ""
"Both PointLight2D and DirectionalLight2D support normal mapping and specular "
"mapping. Since Godot 4.0, normal and specular maps can be assigned to any 2D "
"element, including nodes that inherit from Node2D or Control."
msgstr ""

#: ../../docs/tutorials/2d/2d_lights_and_shadows.rst:285
msgid ""
"A normal map represents the direction in which each pixel is \"pointing\" "
"towards. This information is then used by the engine to correctly apply "
"lighting to 2D surfaces in a physically plausible way. Normal maps are "
"typically created from hand-painted height maps, but they can also be "
"automatically generated from other textures."
msgstr ""

#: ../../docs/tutorials/2d/2d_lights_and_shadows.rst:291
msgid ""
"A specular map defines how much each pixel should reflect light (and in "
"which color, if the specular map contains color). Brighter values will "
"result in a brighter reflection at that given spot on the texture. Specular "
"maps are typically created with manual editing, using the diffuse texture as "
"a base."
msgstr ""

#: ../../docs/tutorials/2d/2d_lights_and_shadows.rst:298
msgid ""
"If you don't have normal or specular maps for your sprites, you can generate "
"them using the free and open source `Laigter <https://azagaya.itch.io/"
"laigter>`__ tool."
msgstr ""

#: ../../docs/tutorials/2d/2d_lights_and_shadows.rst:302
msgid ""
"To set up normal maps and/or specular maps on a 2D node, create a new "
"CanvasTexture resource for the property that draws the node's texture. For "
"example, on a Sprite2D:"
msgstr ""

#: ../../docs/tutorials/2d/2d_lights_and_shadows.rst:310
msgid "Creating a CanvasTexture resource for a Sprite2D node"
msgstr ""

#: ../../docs/tutorials/2d/2d_lights_and_shadows.rst:312
msgid ""
"Expand the newly created resource. You can find several properties you will "
"need to adjust:"
msgstr ""

#: ../../docs/tutorials/2d/2d_lights_and_shadows.rst:315
msgid ""
"**Diffuse > Texture:** The base color texture. In this property, load the "
"texture you're using for the sprite itself."
msgstr ""

#: ../../docs/tutorials/2d/2d_lights_and_shadows.rst:317
msgid ""
"**Normal Map > Texture:** The normal map texture. In this property, load a "
"normal map texture you've generated from a height map (see the tip above)."
msgstr ""

#: ../../docs/tutorials/2d/2d_lights_and_shadows.rst:319
msgid ""
"**Specular > Texture:** The specular map texture, which controls the "
"specular intensity of each pixel on the diffuse texture. The specular map is "
"usually grayscale, but it can also contain color to multiply the color of "
"reflections accordingly. In this property, load a specular map texture "
"you've created (see the tip above)."
msgstr ""

#: ../../docs/tutorials/2d/2d_lights_and_shadows.rst:324
msgid "**Specular > Color:** The color multiplier for specular reflections."
msgstr ""

#: ../../docs/tutorials/2d/2d_lights_and_shadows.rst:325
msgid ""
"**Specular > Shininess:** The specular exponent to use for reflections. "
"Lower values will increase the brightness of reflections and make them more "
"diffuse, while higher values will make reflections more localized. High "
"values are more suited for wet-looking surfaces."
msgstr ""

#: ../../docs/tutorials/2d/2d_lights_and_shadows.rst:329
msgid ""
"**Texture > Filter:** Can be set to override the texture filtering mode, "
"regardless of what the node's property is set to (or the **Rendering > "
"Textures > Canvas Textures > Default Texture Filter** project setting)."
msgstr ""

#: ../../docs/tutorials/2d/2d_lights_and_shadows.rst:333
msgid ""
"**Texture > Repeat:** Can be set to override the texture filtering mode, "
"regardless of what the node's property is set to (or the **Rendering > "
"Textures > Canvas Textures > Default Texture Repeat** project setting)."
msgstr ""

#: ../../docs/tutorials/2d/2d_lights_and_shadows.rst:338
msgid ""
"After enabling normal mapping, you may notice that your lights appear to be "
"weaker. To resolve this, increase the **Height** property on your "
"PointLight2D and DirectionalLight2D nodes. You may also want to increase the "
"lights's **Energy** property slightly to get closer to how your lighting's "
"intensity looked prior to enabling normal mapping."
msgstr ""

#: ../../docs/tutorials/2d/2d_lights_and_shadows.rst:345
msgid "Using additive sprites as a faster alternative to 2D lights"
msgstr ""

#: ../../docs/tutorials/2d/2d_lights_and_shadows.rst:347
msgid ""
"If you run into performance issues when using 2D lights, it may be worth "
"replacing some of them with Sprite2D nodes that use additive blending. This "
"is particularly suited for short-lived dynamic effects, such as bullets or "
"explosions."
msgstr ""

#: ../../docs/tutorials/2d/2d_lights_and_shadows.rst:351
msgid ""
"Additive sprites are much faster to render, since they don't need to go "
"through a separate rendering pipeline. Additionally, it is possible to use "
"this approach with AnimatedSprite2D (or Sprite2D + AnimationPlayer), which "
"allows for animated 2D \"lights\" to be created."
msgstr ""

#: ../../docs/tutorials/2d/2d_lights_and_shadows.rst:356
msgid "However, additive sprites have a few downsides compared to 2D lights:"
msgstr ""

#: ../../docs/tutorials/2d/2d_lights_and_shadows.rst:358
msgid ""
"The blending formula is inaccurate compared to \"actual\" 2D lighting. This "
"is usually not a problem in sufficiently lit areas, but this prevents "
"additive sprites from correctly lighting up areas that are fully dark."
msgstr ""

#: ../../docs/tutorials/2d/2d_lights_and_shadows.rst:361
msgid "Additive sprites cannot cast shadows, since they are not lights."
msgstr ""

#: ../../docs/tutorials/2d/2d_lights_and_shadows.rst:362
msgid "Additive sprites ignore normal and specular maps used on other sprites."
msgstr ""

#: ../../docs/tutorials/2d/2d_lights_and_shadows.rst:364
msgid ""
"To display a sprite with additive blending, create a Sprite2D node and "
"assign a texture to it. In the inspector, scroll down to the **CanvasItem > "
"Material** section, unfold it and click the dropdown next to the "
"**Material** property. Choose **New CanvasItemMaterial**, click the newly "
"created material to edit it, then set **Blend Mode** to **Add**."
msgstr ""

#: ../../docs/tutorials/2d/2d_meshes.rst:6
msgid "2D meshes"
msgstr ""

#: ../../docs/tutorials/2d/2d_meshes.rst:11
msgid ""
"In 3D, meshes are used to display the world. In 2D, they are rare as images "
"are used more often. Godot's 2D engine is a pure two-dimensional engine, so "
"it can't really display 3D meshes directly (although it can be done via "
"``Viewport`` and ``ViewportTexture``)."
msgstr ""

#: ../../docs/tutorials/2d/2d_meshes.rst:15
msgid ""
"If you are interested in displaying 3D meshes on a 2D viewport, see the :ref:"
"`doc_viewport_as_texture` tutorial."
msgstr ""

#: ../../docs/tutorials/2d/2d_meshes.rst:17
msgid ""
"2D meshes are meshes that contain two-dimensional geometry (Z can be omitted "
"or ignored) instead of 3D. You can experiment creating them yourself using "
"``SurfaceTool`` from code and displaying them in a ``MeshInstance2D`` node."
msgstr ""

#: ../../docs/tutorials/2d/2d_meshes.rst:20
msgid ""
"Currently, the only way to generate a 2D mesh within the editor is by either "
"importing an OBJ file as a mesh, or converting it from a Sprite2D."
msgstr ""

#: ../../docs/tutorials/2d/2d_meshes.rst:23
msgid "Optimizing pixels drawn"
msgstr ""

#: ../../docs/tutorials/2d/2d_meshes.rst:25
msgid ""
"This workflow is useful for optimizing 2D drawing in some situations. When "
"drawing large images with transparency, Godot will draw the whole quad to "
"the screen. The large transparent areas will still be drawn."
msgstr ""

#: ../../docs/tutorials/2d/2d_meshes.rst:27
msgid ""
"This can affect performance, especially on mobile devices, when drawing very "
"large images (generally screen sized), or layering multiple images on top of "
"each other with large transparent areas (for example, when using "
"``ParallaxBackground``)."
msgstr ""

#: ../../docs/tutorials/2d/2d_meshes.rst:30
msgid ""
"Converting to a mesh will ensure that only the opaque parts will be drawn "
"and the rest will be ignored."
msgstr ""

#: ../../docs/tutorials/2d/2d_meshes.rst:33
msgid "Converting Sprite2Ds to 2D meshes"
msgstr ""

#: ../../docs/tutorials/2d/2d_meshes.rst:35
msgid ""
"You can take advantage of this optimization by converting a ``Sprite2D`` to "
"a ``MeshInstance2D``. Start with an image that contains large amounts of "
"transparency on the edges, like this tree:"
msgstr ""

#: ../../docs/tutorials/2d/2d_meshes.rst:40
msgid ""
"Put it in a ``Sprite2D`` and select \"Convert to 2D Mesh\" from the menu:"
msgstr ""

#: ../../docs/tutorials/2d/2d_meshes.rst:44
msgid ""
"A dialog will appear, showing a preview of how the 2D mesh will be created:"
msgstr ""

#: ../../docs/tutorials/2d/2d_meshes.rst:48
msgid ""
"The default values are good enough for many cases, but you can change growth "
"and simplification according to your needs:"
msgstr ""

#: ../../docs/tutorials/2d/2d_meshes.rst:52
msgid ""
"Finally, push the ``Convert 2D Mesh`` button and your Sprite2D will be "
"replaced:"
msgstr ""

#: ../../docs/tutorials/2d/2d_sprite_animation.rst:4
#, fuzzy
msgid "2D sprite animation"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/2d/2d_sprite_animation.rst:9
msgid ""
"In this tutorial, you'll learn how to create 2D animated characters with the "
"AnimatedSprite2D class and the AnimationPlayer. Typically, when you create "
"or download an animated character, it will come in one of two ways: as "
"individual images or as a single sprite sheet containing all the animation's "
"frames. Both can be animated in Godot with the AnimatedSprite2D class."
msgstr ""

#: ../../docs/tutorials/2d/2d_sprite_animation.rst:16
msgid ""
"First, we'll use :ref:`AnimatedSprite2D <class_AnimatedSprite2D>` to animate "
"a collection of individual images. Then we will animate a sprite sheet using "
"this class. Finally, we will learn another way to animate a sprite sheet "
"with :ref:`AnimationPlayer <class_AnimationPlayer>` and the *Animation* "
"property of :ref:`Sprite2D <class_Sprite2D>`."
msgstr ""

#: ../../docs/tutorials/2d/2d_sprite_animation.rst:23
msgid ""
"Art for the following examples by https://opengameart.org/users/ansimuz and "
"tgfcoder."
msgstr ""

#: ../../docs/tutorials/2d/2d_sprite_animation.rst:26
msgid "Individual images with AnimatedSprite2D"
msgstr ""

#: ../../docs/tutorials/2d/2d_sprite_animation.rst:28
msgid ""
"In this scenario, you have a collection of images, each containing one of "
"your character's animation frames. For this example, we'll use the following "
"animation:"
msgstr ""

#: ../../docs/tutorials/2d/2d_sprite_animation.rst:34
msgid ""
"You can download the images here: `2d_sprite_animation_assets.zip <https://"
"github.com/godotengine/godot-docs-project-starters/releases/download/"
"latest-4.x/2d_sprite_animation_assets.zip>`_"
msgstr ""

#: ../../docs/tutorials/2d/2d_sprite_animation.rst:37
msgid ""
"Unzip the images and place them in your project folder. Set up your scene "
"tree with the following nodes:"
msgstr ""

#: ../../docs/tutorials/2d/2d_sprite_animation.rst:42
#: ../../docs/tutorials/2d/2d_sprite_animation.rst:182
msgid ""
"The root node could also be :ref:`Area2D <class_Area2D>` or :ref:"
"`RigidBody2D <class_RigidBody2D>`. The animation will still be made in the "
"same way. Once the animation is completed, you can assign a shape to the "
"CollisionShape2D. See :ref:`Physics Introduction <doc_physics_introduction>` "
"for more information."
msgstr ""

#: ../../docs/tutorials/2d/2d_sprite_animation.rst:49
msgid ""
"Now select the ``AnimatedSprite2D`` and in its *SpriteFrames* property, "
"select \"New SpriteFrames\"."
msgstr ""

#: ../../docs/tutorials/2d/2d_sprite_animation.rst:54
msgid ""
"Click on the new SpriteFrames resource and you'll see a new panel appear at "
"the bottom of the editor window:"
msgstr ""

#: ../../docs/tutorials/2d/2d_sprite_animation.rst:59
msgid ""
"From the FileSystem dock on the left side, drag the 8 individual images into "
"the center part of the SpriteFrames panel. On the left side, change the name "
"of the animation from \"default\" to \"run\"."
msgstr ""

#: ../../docs/tutorials/2d/2d_sprite_animation.rst:65
msgid ""
"Use the \"Play\" buttons on the top-right of the *Filter Animations* input "
"to preview the animation. You should now see the animation playing in the "
"viewport. However, it is a bit slow. To fix this, change the *Speed (FPS)* "
"setting in the SpriteFrames panel to 10."
msgstr ""

#: ../../docs/tutorials/2d/2d_sprite_animation.rst:70
msgid ""
"You can add additional animations by clicking the \"Add Animation\" button "
"and adding additional images."
msgstr ""

#: ../../docs/tutorials/2d/2d_sprite_animation.rst:74
#, fuzzy
msgid "Controlling the animation"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/2d/2d_sprite_animation.rst:76
msgid ""
"Once the animation is complete, you can control the animation via code using "
"the ``play()`` and ``stop()`` methods. Here is a brief example to play the "
"animation while the right arrow key is held, and stop it when the key is "
"released."
msgstr ""

#: ../../docs/tutorials/2d/2d_sprite_animation.rst:122
msgid "Sprite sheet with AnimatedSprite2D"
msgstr ""

#: ../../docs/tutorials/2d/2d_sprite_animation.rst:124
msgid ""
"You can also easily animate from a sprite sheet with the class "
"``AnimatedSprite2D``. We will use this public domain sprite sheet:"
msgstr ""

#: ../../docs/tutorials/2d/2d_sprite_animation.rst:129
msgid ""
"Right-click the image and choose \"Save Image As\" to download it, and then "
"copy the image into your project folder."
msgstr ""

#: ../../docs/tutorials/2d/2d_sprite_animation.rst:132
msgid ""
"Set up your scene tree the same way you did previously when using individual "
"images. Select the ``AnimatedSprite2D`` and in its *SpriteFrames* property, "
"select \"New SpriteFrames\"."
msgstr ""

#: ../../docs/tutorials/2d/2d_sprite_animation.rst:135
msgid ""
"Click on the new SpriteFrames resource. This time, when the bottom panel "
"appears, select \"Add frames from a Sprite Sheet\"."
msgstr ""

#: ../../docs/tutorials/2d/2d_sprite_animation.rst:140
msgid "You will be prompted to open a file. Select your sprite sheet."
msgstr ""

#: ../../docs/tutorials/2d/2d_sprite_animation.rst:142
msgid ""
"A new window will open, showing your sprite sheet. The first thing you will "
"need to do is to change the number of vertical and horizontal images in your "
"sprite sheet. In this sprite sheet, we have four images horizontally and two "
"images vertically."
msgstr ""

#: ../../docs/tutorials/2d/2d_sprite_animation.rst:148
msgid ""
"Next, select the frames from the sprite sheet that you want to include in "
"your animation. We will select the top four, then click \"Add 4 frames\" to "
"create the animation."
msgstr ""

#: ../../docs/tutorials/2d/2d_sprite_animation.rst:153
msgid ""
"You will now see your animation under the list of animations in the bottom "
"panel. Double click on default to change the name of the animation to jump."
msgstr ""

#: ../../docs/tutorials/2d/2d_sprite_animation.rst:158
msgid ""
"Finally, check the play button on the SpriteFrames editor to see your frog "
"jump!"
msgstr ""

#: ../../docs/tutorials/2d/2d_sprite_animation.rst:164
msgid "Sprite sheet with AnimationPlayer"
msgstr ""

#: ../../docs/tutorials/2d/2d_sprite_animation.rst:166
msgid ""
"Another way that you can animate when using a sprite sheet is to use a "
"standard :ref:`Sprite2D <class_Sprite2D>` node to display the texture, and "
"then animating the change from texture to texture with :ref:`AnimationPlayer "
"<class_AnimationPlayer>`."
msgstr ""

#: ../../docs/tutorials/2d/2d_sprite_animation.rst:170
msgid "Consider this sprite sheet, which contains 6 frames of animation:"
msgstr ""

#: ../../docs/tutorials/2d/2d_sprite_animation.rst:174
msgid ""
"Right-click the image and choose \"Save Image As\" to download, then copy "
"the image into your project folder."
msgstr ""

#: ../../docs/tutorials/2d/2d_sprite_animation.rst:177
msgid ""
"Our goal is to display these images one after another in a loop. Start by "
"setting up your scene tree:"
msgstr ""

#: ../../docs/tutorials/2d/2d_sprite_animation.rst:189
msgid ""
"Drag the spritesheet into the Sprite's *Texture* property, and you'll see "
"the whole sheet displayed on the screen. To slice it up into individual "
"frames, expand the *Animation* section in the Inspector and set the "
"*Hframes* to ``6``. *Hframes* and *Vframes* are the number of horizontal and "
"vertical frames in your sprite sheet."
msgstr ""

#: ../../docs/tutorials/2d/2d_sprite_animation.rst:197
msgid ""
"Now try changing the value of the *Frame* property. You'll see that it "
"ranges from ``0`` to ``5`` and the image displayed by the Sprite2D changes "
"accordingly. This is the property we'll be animating."
msgstr ""

#: ../../docs/tutorials/2d/2d_sprite_animation.rst:201
msgid ""
"Select the ``AnimationPlayer`` and click the \"Animation\" button followed "
"by \"New\". Name the new animation \"walk\". Set the animation length to "
"``0.6`` and click the \"Loop\" button so that our animation will repeat."
msgstr ""

#: ../../docs/tutorials/2d/2d_sprite_animation.rst:207
msgid ""
"Now select the ``Sprite2D`` node and click the key icon to add a new track."
msgstr ""

#: ../../docs/tutorials/2d/2d_sprite_animation.rst:211
msgid ""
"Continue adding frames at each point in the timeline (``0.1`` seconds by "
"default), until you have all the frames from 0 to 5. You'll see the frames "
"actually appearing in the animation track:"
msgstr ""

#: ../../docs/tutorials/2d/2d_sprite_animation.rst:217
msgid "Press \"Play\" on the animation to see how it looks."
msgstr ""

#: ../../docs/tutorials/2d/2d_sprite_animation.rst:222
#, fuzzy
msgid "Controlling an AnimationPlayer animation"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/2d/2d_sprite_animation.rst:224
msgid ""
"Like with AnimatedSprite2D, you can control the animation via code using the "
"``play()`` and ``stop()`` methods. Again, here is an example to play the "
"animation while the right arrow key is held, and stop it when the key is "
"released."
msgstr ""

#: ../../docs/tutorials/2d/2d_sprite_animation.rst:268
msgid ""
"If updating both an animation and a separate property at once (for example, "
"a platformer may update the sprite's ``h_flip``/``v_flip`` properties when a "
"character turns while starting a 'turning' animation), it's important to "
"keep in mind that ``play()`` isn't applied instantly. Instead, it's applied "
"the next time the :ref:`AnimationPlayer <class_AnimationPlayer>` is "
"processed. This may end up being on the next frame, causing a 'glitch' "
"frame, where the property change was applied but the animation was not. If "
"this turns out to be a problem, after calling ``play()``, you can call "
"``advance(0)`` to update the animation immediately."
msgstr ""

#: ../../docs/tutorials/2d/2d_sprite_animation.rst:281
msgid ""
"These examples illustrate the two classes you can use in Godot for 2D "
"animation. ``AnimationPlayer`` is a bit more complex than "
"``AnimatedSprite2D``, but it provides additional functionality, since you "
"can also animate other properties like position or scale. The class "
"``AnimationPlayer`` can also be used with an ``AnimatedSprite2D``. "
"Experiment to see what works best for your needs."
msgstr ""

#: ../../docs/tutorials/2d/particle_systems_2d.rst:6
msgid "2D particle systems"
msgstr ""

#: ../../docs/tutorials/2d/particle_systems_2d.rst:9
msgid "Intro"
msgstr ""

#: ../../docs/tutorials/2d/particle_systems_2d.rst:11
msgid ""
"Particle systems are used to simulate complex physical effects, such as "
"sparks, fire, magic particles, smoke, mist, etc."
msgstr ""

#: ../../docs/tutorials/2d/particle_systems_2d.rst:14
msgid ""
"The idea is that a \"particle\" is emitted at a fixed interval and with a "
"fixed lifetime. During its lifetime, every particle will have the same base "
"behavior. What makes each particle different from the rest and provides a "
"more organic look is the \"randomness\" associated with each parameter. In "
"essence, creating a particle system means setting base physics parameters "
"and then adding randomness to them."
msgstr ""

#: ../../docs/tutorials/2d/particle_systems_2d.rst:22
msgid "Particle nodes"
msgstr ""

#: ../../docs/tutorials/2d/particle_systems_2d.rst:24
msgid ""
"Godot provides two different nodes for 2D particles, :ref:"
"`class_GPUParticles2D` and :ref:`class_CPUParticles2D`. GPUParticles2D is "
"more advanced and uses the GPU to process particle effects. CPUParticles2D "
"is a CPU-driven option with near-feature parity with GPUParticles2D, but "
"lower performance when using large amounts of particles. On the other hand, "
"CPUParticles2D may perform better on low-end systems or in GPU-bottlenecked "
"situations."
msgstr ""

#: ../../docs/tutorials/2d/particle_systems_2d.rst:31
msgid ""
"While GPUParticles2D is configured via a :ref:"
"`class_ParticleProcessMaterial` (and optionally with a custom shader), the "
"matching options are provided via node properties in CPUParticles2D (with "
"the exception of the trail settings)."
msgstr ""

#: ../../docs/tutorials/2d/particle_systems_2d.rst:35
msgid ""
"You can convert a GPUParticles2D node into a CPUParticles2D node by clicking "
"on the node in the inspector, selecting the 2D viewport, and selecting "
"**GPUParticles2D > Convert to CPUParticles2D** in the viewport toolbar."
msgstr ""

#: ../../docs/tutorials/2d/particle_systems_2d.rst:41
msgid ""
"The rest of this tutorial is going to use the GPUParticles2D node. First, "
"add a GPUParticles2D node to your scene. After creating that node you will "
"notice that only a white dot was created, and that there is a warning icon "
"next to your GPUParticles2D node in the scene dock. This is because the node "
"needs a ParticleProcessMaterial to function."
msgstr ""

#: ../../docs/tutorials/2d/particle_systems_2d.rst:49
msgid ""
"To add a process material to your particles node, go to ``Process Material`` "
"in your inspector panel. Click on the box next to ``Material``, and from the "
"dropdown menu select ``New ParticleProcessMaterial``."
msgstr ""

#: ../../docs/tutorials/2d/particle_systems_2d.rst:55
msgid "Your GPUParticles2D node should now be emitting white points downward."
msgstr ""

#: ../../docs/tutorials/2d/particle_systems_2d.rst:61
msgid "Texture"
msgstr ""

#: ../../docs/tutorials/2d/particle_systems_2d.rst:63
msgid ""
"A particle system can use a single texture or an animation *flipbook*. A "
"flipbook is a texture that contains several frames of animation that can be "
"played back, or chosen at random during emission. This is equivalent to a "
"spritesheet for particles."
msgstr ""

#: ../../docs/tutorials/2d/particle_systems_2d.rst:68
msgid "The texture is set via the **Texture** property:"
msgstr ""

#: ../../docs/tutorials/2d/particle_systems_2d.rst:75
#, fuzzy
msgid "Using an animation flipbook"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/2d/particle_systems_2d.rst:77
msgid ""
"Particle flipbooks are suited to reproduce complex effects such as smoke, "
"fire, explosions. They can also be used to introduce random texture "
"variation, by making every particle use a different texture. You can find "
"existing particle flipbook images online, or pre-render them using external "
"tools such as `Blender <https://www.blender.org/>`__ or `EmberGen <https://"
"jangafx.com/software/embergen/>`__."
msgstr ""

#: ../../docs/tutorials/2d/particle_systems_2d.rst:87
msgid "Example of a particle system that uses a flipbook texture"
msgstr ""

#: ../../docs/tutorials/2d/particle_systems_2d.rst:89
msgid ""
"Using an animation flipbook requires additional configuration compared to a "
"single texture. For demonstration purposes, we'll use this texture with 5 "
"columns and 7 rows (right-click and choose **Save as…**):"
msgstr ""

#: ../../docs/tutorials/2d/particle_systems_2d.rst:98
msgid "Particle flipbook texture example"
msgstr ""

#: ../../docs/tutorials/2d/particle_systems_2d.rst:98
msgid ""
"Credit: `JoesAlotofthings <https://opengameart.org/content/alot-of-particles-"
"indispersal-special-effect-alotofparticles30>`__ (CC BY 4.0)"
msgstr ""

#: ../../docs/tutorials/2d/particle_systems_2d.rst:101
msgid ""
"To use an animation flipbook, you must create a new CanvasItemMaterial in "
"the Material section of the GPUParticles2D (or CPUParticles2D) node:"
msgstr ""

#: ../../docs/tutorials/2d/particle_systems_2d.rst:108
msgid ""
"Creating a CanvasItemMaterial at the bottom of the particles node inspector"
msgstr ""

#: ../../docs/tutorials/2d/particle_systems_2d.rst:110
msgid ""
"In this CanvasItemMaterial, enable **Particle Animation** and set **H "
"Frames** and **V Frames** to the number of columns and rows present in your "
"flipbook texture:"
msgstr ""

#: ../../docs/tutorials/2d/particle_systems_2d.rst:117
msgid "Configuring the CanvasItemMaterial for the example flipbook texture"
msgstr ""

#: ../../docs/tutorials/2d/particle_systems_2d.rst:119
msgid ""
"Once this is done, the :ref:`Animation section "
"<doc_particle_systems_2d_animation>` in ParticleProcessMaterial (for "
"GPUParticles2D) or in the CPUParticles2D inspector will be effective."
msgstr ""

#: ../../docs/tutorials/2d/particle_systems_2d.rst:125
msgid ""
"If your flipbook texture has a black background instead of a transparent "
"background, you will also need to set the blend mode to **Add** instead of "
"**Mix** for correct display. Alternatively, you can modify the texture to "
"have a transparent background in an image editor. In `GIMP <https://gimp."
"org>`__, this can be done using the **Color > Color to Alpha** menu."
msgstr ""

#: ../../docs/tutorials/2d/particle_systems_2d.rst:132
msgid "Time parameters"
msgstr ""

#: ../../docs/tutorials/2d/particle_systems_2d.rst:135
msgid "Lifetime"
msgstr ""

#: ../../docs/tutorials/2d/particle_systems_2d.rst:137
msgid ""
"The time in seconds that every particle will stay alive. When lifetime ends, "
"a new particle is created to replace it."
msgstr ""

#: ../../docs/tutorials/2d/particle_systems_2d.rst:140
msgid "Lifetime: 0.5"
msgstr ""

#: ../../docs/tutorials/2d/particle_systems_2d.rst:144
msgid "Lifetime: 4.0"
msgstr ""

#: ../../docs/tutorials/2d/particle_systems_2d.rst:149
msgid "One Shot"
msgstr ""

#: ../../docs/tutorials/2d/particle_systems_2d.rst:151
msgid ""
"When enabled, a GPUParticles2D node will emit all of its particles once and "
"then never again."
msgstr ""

#: ../../docs/tutorials/2d/particle_systems_2d.rst:155
msgid "Preprocess"
msgstr ""

#: ../../docs/tutorials/2d/particle_systems_2d.rst:157
msgid ""
"Particle systems begin with zero particles emitted, then start emitting. "
"This can be an inconvenience when loading a scene and systems like a torch, "
"mist, etc. begin emitting the moment you enter. Preprocess is used to let "
"the system process a given number of seconds before it is actually drawn the "
"first time."
msgstr ""

#: ../../docs/tutorials/2d/particle_systems_2d.rst:164
msgid "Speed Scale"
msgstr ""

#: ../../docs/tutorials/2d/particle_systems_2d.rst:166
msgid ""
"The speed scale has a default value of ``1`` and is used to adjust the speed "
"of a particle system. Lowering the value will make the particles slower "
"while increasing the value will make the particles much faster."
msgstr ""

#: ../../docs/tutorials/2d/particle_systems_2d.rst:171
msgid "Explosiveness"
msgstr ""

#: ../../docs/tutorials/2d/particle_systems_2d.rst:173
msgid ""
"If lifetime is ``1`` and there are 10 particles, it means a particle will be "
"emitted every 0.1 seconds. The explosiveness parameter changes this, and "
"forces particles to be emitted all together. Ranges are:"
msgstr ""

#: ../../docs/tutorials/2d/particle_systems_2d.rst:177
msgid "0: Emit particles at regular intervals (default value)."
msgstr ""

#: ../../docs/tutorials/2d/particle_systems_2d.rst:178
msgid "1: Emit all particles simultaneously."
msgstr ""

#: ../../docs/tutorials/2d/particle_systems_2d.rst:180
msgid ""
"Values in the middle are also allowed. This feature is useful for creating "
"explosions or sudden bursts of particles:"
msgstr ""

#: ../../docs/tutorials/2d/particle_systems_2d.rst:186
msgid "Randomness"
msgstr ""

#: ../../docs/tutorials/2d/particle_systems_2d.rst:188
msgid ""
"All physics parameters can be randomized. Random values range from ``0`` to "
"``1``. The formula to randomize a parameter is:"
msgstr ""

#: ../../docs/tutorials/2d/particle_systems_2d.rst:196
msgid "Fixed FPS"
msgstr ""

#: ../../docs/tutorials/2d/particle_systems_2d.rst:198
msgid ""
"This setting can be used to set the particle system to render at a fixed "
"FPS. For instance, changing the value to ``2`` will make the particles "
"render at 2 frames per second. Note this does not slow down the particle "
"system itself."
msgstr ""

#: ../../docs/tutorials/2d/particle_systems_2d.rst:203
msgid "Fract Delta"
msgstr ""

#: ../../docs/tutorials/2d/particle_systems_2d.rst:205
msgid "This can be used to turn Fract Delta on or off."
msgstr ""

#: ../../docs/tutorials/2d/particle_systems_2d.rst:208
msgid "Drawing parameters"
msgstr ""

#: ../../docs/tutorials/2d/particle_systems_2d.rst:211
msgid "Visibility Rect"
msgstr ""

#: ../../docs/tutorials/2d/particle_systems_2d.rst:214
msgid ""
"The visibility rectangle controls the visibility of the particles on screen. "
"If this rectangle is outside of the viewport, the engine will not render the "
"particles on screen."
msgstr ""

#: ../../docs/tutorials/2d/particle_systems_2d.rst:216
msgid ""
"The rectangle's ``W`` and ``H`` properties respectively control its Width "
"and its Height. The ``X`` and ``Y`` properties control the position of the "
"upper-left corner of the rectangle, relative to the particle emitter."
msgstr ""

#: ../../docs/tutorials/2d/particle_systems_2d.rst:220
msgid ""
"You can have Godot generate a Visibility Rect automatically using the "
"toolbar above the 2d view. To do so, select the GPUParticles2D node and "
"Click ``Particles > Generate Visibility Rect``. Godot will simulate the "
"Particles2D node emitting particles for a few seconds and set the rectangle "
"to fit the surface the particles take."
msgstr ""

#: ../../docs/tutorials/2d/particle_systems_2d.rst:222
msgid ""
"You can control the emit duration with the ``Generation Time (sec)`` option. "
"The maximum value is 25 seconds. If you need more time for your particles to "
"move around, you can temporarily change the ``preprocess`` duration on the "
"Particles2D node."
msgstr ""

#: ../../docs/tutorials/2d/particle_systems_2d.rst:225
msgid "Local Coords"
msgstr ""

#: ../../docs/tutorials/2d/particle_systems_2d.rst:227
msgid ""
"By default this option is on, and it means that the space that particles are "
"emitted to is relative to the node. If the node is moved, all particles are "
"moved with it:"
msgstr ""

#: ../../docs/tutorials/2d/particle_systems_2d.rst:233
msgid ""
"If disabled, particles will emit to global space, meaning that if the node "
"is moved, already emitted particles are not affected:"
msgstr ""

#: ../../docs/tutorials/2d/particle_systems_2d.rst:239
msgid "Draw Order"
msgstr ""

#: ../../docs/tutorials/2d/particle_systems_2d.rst:241
msgid ""
"This controls the order in which individual particles are drawn. ``Index`` "
"means particles are drawn according to their emission order (default). "
"``Lifetime`` means they are drawn in order of remaining lifetime."
msgstr ""

#: ../../docs/tutorials/2d/particle_systems_2d.rst:246
msgid "ParticleProcessMaterial settings"
msgstr ""

#: ../../docs/tutorials/2d/particle_systems_2d.rst:249
#: ../../docs/tutorials/3d/particles/process_material_properties.rst:98
#, fuzzy
msgid "Direction"
msgstr "Uvod"

#: ../../docs/tutorials/2d/particle_systems_2d.rst:251
msgid ""
"This is the base direction at which particles emit. The default is "
"``Vector3(1, 0, 0)`` which makes particles emit to the right. However, with "
"the default gravity settings, particles will go straight down."
msgstr ""

#: ../../docs/tutorials/2d/particle_systems_2d.rst:257
msgid ""
"For this property to be noticeable, you need an *initial velocity* greater "
"than 0. Here, we set the initial velocity to 40. You'll notice that "
"particles emit toward the right, then go down because of gravity."
msgstr ""

#: ../../docs/tutorials/2d/particle_systems_2d.rst:264
msgid "Spread"
msgstr ""

#: ../../docs/tutorials/2d/particle_systems_2d.rst:266
msgid ""
"This parameter is the angle in degrees which will be randomly added in "
"either direction to the base ``Direction``. A spread of ``180`` will emit in "
"all directions (+/- 180). For spread to do anything the \"Initial Velocity\" "
"parameter must be greater than 0."
msgstr ""

#: ../../docs/tutorials/2d/particle_systems_2d.rst:274
msgid "Flatness"
msgstr ""

#: ../../docs/tutorials/2d/particle_systems_2d.rst:276
msgid "This property is only useful for 3D particles."
msgstr ""

#: ../../docs/tutorials/2d/particle_systems_2d.rst:279
#: ../../docs/tutorials/3d/particles/process_material_properties.rst:147
msgid "Gravity"
msgstr ""

#: ../../docs/tutorials/2d/particle_systems_2d.rst:281
msgid "The gravity applied to every particle."
msgstr ""

#: ../../docs/tutorials/2d/particle_systems_2d.rst:286
msgid "Initial Velocity"
msgstr ""

#: ../../docs/tutorials/2d/particle_systems_2d.rst:288
msgid ""
"Initial velocity is the speed at which particles will be emitted (in pixels/"
"sec). Speed might later be modified by gravity or other accelerations (as "
"described further below)."
msgstr ""

#: ../../docs/tutorials/2d/particle_systems_2d.rst:295
msgid "Angular Velocity"
msgstr ""

#: ../../docs/tutorials/2d/particle_systems_2d.rst:297
msgid "Angular velocity is the initial angular velocity applied to particles."
msgstr ""

#: ../../docs/tutorials/2d/particle_systems_2d.rst:300
msgid "Spin Velocity"
msgstr ""

#: ../../docs/tutorials/2d/particle_systems_2d.rst:302
msgid ""
"Spin velocity is the speed at which particles turn around their center (in "
"degrees/sec)."
msgstr ""

#: ../../docs/tutorials/2d/particle_systems_2d.rst:308
msgid "Orbit Velocity"
msgstr ""

#: ../../docs/tutorials/2d/particle_systems_2d.rst:310
msgid "Orbit velocity is used to make particles turn around their center."
msgstr ""

#: ../../docs/tutorials/2d/particle_systems_2d.rst:315
msgid "Linear Acceleration"
msgstr ""

#: ../../docs/tutorials/2d/particle_systems_2d.rst:317
msgid "The linear acceleration applied to each particle."
msgstr ""

#: ../../docs/tutorials/2d/particle_systems_2d.rst:320
msgid "Radial Acceleration"
msgstr ""

#: ../../docs/tutorials/2d/particle_systems_2d.rst:322
msgid ""
"If this acceleration is positive, particles are accelerated away from the "
"center. If negative, they are absorbed towards it."
msgstr ""

#: ../../docs/tutorials/2d/particle_systems_2d.rst:328
msgid "Tangential Acceleration"
msgstr ""

#: ../../docs/tutorials/2d/particle_systems_2d.rst:330
msgid ""
"This acceleration will use the tangent vector to the center. Combining with "
"radial acceleration can do nice effects."
msgstr ""

#: ../../docs/tutorials/2d/particle_systems_2d.rst:336
#: ../../docs/tutorials/3d/particles/process_material_properties.rst:240
msgid "Damping"
msgstr ""

#: ../../docs/tutorials/2d/particle_systems_2d.rst:338
msgid ""
"Damping applies friction to the particles, forcing them to stop. It is "
"especially useful for sparks or explosions, which usually begin with a high "
"linear velocity and then stop as they fade."
msgstr ""

#: ../../docs/tutorials/2d/particle_systems_2d.rst:345
#: ../../docs/tutorials/3d/particles/process_material_properties.rst:89
msgid "Angle"
msgstr ""

#: ../../docs/tutorials/2d/particle_systems_2d.rst:347
msgid ""
"Determines the initial angle of the particle (in degrees). This parameter is "
"mostly useful randomized."
msgstr ""

#: ../../docs/tutorials/2d/particle_systems_2d.rst:353
#: ../../docs/tutorials/3d/particles/process_material_properties.rst:258
#: ../../docs/tutorials/3d/using_multi_mesh_instance.rst:89
msgid "Scale"
msgstr "Razmera"

#: ../../docs/tutorials/2d/particle_systems_2d.rst:355
msgid "Determines the initial scale of the particles."
msgstr ""

#: ../../docs/tutorials/2d/particle_systems_2d.rst:360
#: ../../docs/tutorials/3d/particles/process_material_properties.rst:267
#: ../../docs/tutorials/3d/variable_rate_shading.rst:133
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:753
#: ../../docs/tutorials/shaders/visual_shaders.rst:116
msgid "Color"
msgstr ""

#: ../../docs/tutorials/2d/particle_systems_2d.rst:362
msgid "Used to change the color of the particles being emitted."
msgstr ""

#: ../../docs/tutorials/2d/particle_systems_2d.rst:365
#, fuzzy
msgid "Hue Variation"
msgstr "Uvod"

#: ../../docs/tutorials/2d/particle_systems_2d.rst:367
msgid ""
"The ``Variation`` value sets the initial hue variation applied to each "
"particle. The ``Variation Random`` value controls the hue variation "
"randomness ratio."
msgstr ""

#: ../../docs/tutorials/2d/particle_systems_2d.rst:378
msgid ""
"Particle flipbook animation is only effective if the CanvasItemMaterial used "
"on the GPUParticles2D or CPUParticles2D node has been :ref:`configured "
"accordingly <doc_particle_systems_2d_using_flipbook>`."
msgstr ""

#: ../../docs/tutorials/2d/particle_systems_2d.rst:382
msgid ""
"To set up the particle flipbook for linear playback, set the **Speed Min** "
"and **Speed Max** values to 1:"
msgstr ""

#: ../../docs/tutorials/2d/particle_systems_2d.rst:388
msgid ""
"Setting up particle animation for playback during the particle's lifetime"
msgstr ""

#: ../../docs/tutorials/2d/particle_systems_2d.rst:390
msgid ""
"By default, looping is disabled. If the particle is done playing before its "
"lifetime ends, the particle will keep using the flipbook's last frame (which "
"may be fully transparent depending on how the flipbook texture is designed). "
"If looping is enabled, the animation will loop back to the first frame and "
"resume playing."
msgstr ""

#: ../../docs/tutorials/2d/particle_systems_2d.rst:396
#: ../../docs/tutorials/3d/particles/process_material_properties.rst:355
msgid ""
"Depending on how many images your sprite sheet contains and for how long "
"your particle is alive, the animation might not look smooth. The "
"relationship between particle lifetime, animation speed, and number of "
"images in the sprite sheet is this:"
msgstr ""

#: ../../docs/tutorials/2d/particle_systems_2d.rst:403
#: ../../docs/tutorials/3d/particles/process_material_properties.rst:362
msgid ""
"At an animation speed of ``1.0``, the animation will reach the last image in "
"the sequence just as the particle's lifetime ends."
msgstr ""

#: ../../docs/tutorials/2d/particle_systems_2d.rst:406
#: ../../docs/tutorials/3d/particles/process_material_properties.rst:365
msgid ""
"Animation\\ FPS = \\frac{Number\\ of\\ images}{Lifetime}\n"
"\n"
msgstr ""

#: ../../docs/tutorials/2d/particle_systems_2d.rst:409
msgid ""
"If you wish the particle flipbook to be used as a source of random particle "
"textures for every particle, keep the speed values at 0 and set **Offset "
"Max** to 1 instead:"
msgstr ""

#: ../../docs/tutorials/2d/particle_systems_2d.rst:417
msgid "Setting up particle animation for random offset on emission"
msgstr ""

#: ../../docs/tutorials/2d/particle_systems_2d.rst:419
msgid ""
"Note that the GPUParticles2D node's **Fixed FPS** also affects animation "
"playback. For smooth animation playback, it's recommended to set it to 0 so "
"that the particle is simulated on every rendered frame. If this is not an "
"option for your use case, set **Fixed FPS** to be equal to the effective "
"framerate used by the flipbook animation (see above for the formula)."
msgstr ""

#: ../../docs/tutorials/2d/particle_systems_2d.rst:426
msgid "Emission Shapes"
msgstr ""

#: ../../docs/tutorials/2d/particle_systems_2d.rst:428
msgid ""
"ParticleProcessMaterials allow you to set an Emission Mask, which dictates "
"the area and direction in which particles are emitted. These can be "
"generated from textures in your project."
msgstr ""

#: ../../docs/tutorials/2d/particle_systems_2d.rst:432
msgid ""
"Ensure that a ParticleProcessMaterial is set, and the GPUParticles2D node is "
"selected. A \"Particles\" menu should appear in the Toolbar:"
msgstr ""

#: ../../docs/tutorials/2d/particle_systems_2d.rst:437
msgid "Open it and select \"Load Emission Mask\":"
msgstr ""

#: ../../docs/tutorials/2d/particle_systems_2d.rst:441
msgid "Then select which texture you want to use as your mask:"
msgstr ""

#: ../../docs/tutorials/2d/particle_systems_2d.rst:445
msgid "A dialog box with several settings will appear."
msgstr ""

#: ../../docs/tutorials/2d/particle_systems_2d.rst:448
msgid "Emission Mask"
msgstr ""

#: ../../docs/tutorials/2d/particle_systems_2d.rst:450
msgid "Three types of emission masks can be generated from a texture:"
msgstr ""

#: ../../docs/tutorials/2d/particle_systems_2d.rst:452
msgid ""
"Solid Pixels: Particles will spawn from any area of the texture, excluding "
"transparent areas."
msgstr ""

#: ../../docs/tutorials/2d/particle_systems_2d.rst:457
msgid ""
"Border Pixels: Particles will spawn from the outer edges of the texture."
msgstr ""

#: ../../docs/tutorials/2d/particle_systems_2d.rst:461
msgid ""
"Directed Border Pixels: Similar to Border Pixels, but adds extra information "
"to the mask to give particles the ability to emit away from the borders. "
"Note that an ``Initial Velocity`` will need to be set in order to utilize "
"this."
msgstr ""

#: ../../docs/tutorials/2d/particle_systems_2d.rst:469
msgid "Emission Colors"
msgstr ""

#: ../../docs/tutorials/2d/particle_systems_2d.rst:471
msgid ""
"``Capture from Pixel`` will cause the particles to inherit the color of the "
"mask at their spawn points."
msgstr ""

#: ../../docs/tutorials/2d/particle_systems_2d.rst:473
msgid ""
"Once you click \"OK\", the mask will be generated and set to the "
"ParticleProcessMaterial, under the ``Emission Shape`` section:"
msgstr ""

#: ../../docs/tutorials/2d/particle_systems_2d.rst:477
msgid ""
"All of the values within this section have been automatically generated by "
"the \"Load Emission Mask\" menu, so they should generally be left alone."
msgstr ""

#: ../../docs/tutorials/2d/particle_systems_2d.rst:480
msgid ""
"An image should not be added to ``Point Texture`` or ``Color Texture`` "
"directly. The \"Load Emission Mask\" menu should always be used instead."
msgstr ""

#: ../../docs/tutorials/2d/2d_antialiasing.rst:4
msgid "2D antialiasing"
msgstr ""

#: ../../docs/tutorials/2d/2d_antialiasing.rst:12
msgid ""
"Godot also supports antialiasing in 3D rendering. This is covered on the :"
"ref:`doc_3d_antialiasing` page."
msgstr ""

#: ../../docs/tutorials/2d/2d_antialiasing.rst:18
msgid ""
"Due to their limited resolution, scenes rendered in 2D can exhibit aliasing "
"artifacts. These artifacts usually manifest in the form of a \"staircase\" "
"effect on geometry edges, and are most noticeable when using nodes such as :"
"ref:`class_Line2D`, :ref:`class_Polygon2D` or :ref:"
"`class_TextureProgressBar`. :ref:`doc_custom_drawing_in_2d` can also have "
"aliasing artifacts for methods that don't support antialiasing."
msgstr ""

#: ../../docs/tutorials/2d/2d_antialiasing.rst:24
msgid ""
"In the example below, you can notice how edges have a blocky appearance:"
msgstr ""

#: ../../docs/tutorials/2d/2d_antialiasing.rst:31
#: ../../docs/tutorials/3d/3d_antialiasing.rst:31
msgid ""
"Image is scaled by 2× with nearest-neighbor filtering to make aliasing more "
"noticeable."
msgstr ""

#: ../../docs/tutorials/2d/2d_antialiasing.rst:33
msgid ""
"To combat this, Godot supports several methods of enabling antialiasing on "
"2D rendering."
msgstr ""

#: ../../docs/tutorials/2d/2d_antialiasing.rst:36
msgid "Antialiasing property in Line2D and custom drawing"
msgstr ""

#: ../../docs/tutorials/2d/2d_antialiasing.rst:38
msgid ""
"This is the recommended method, as it has a lower performance impact in most "
"cases."
msgstr ""

#: ../../docs/tutorials/2d/2d_antialiasing.rst:40
msgid ""
"Line2D has an **Antialiased** property which you can enable in the "
"inspector. Also, several methods for :ref:`doc_custom_drawing_in_2d` support "
"an optional ``antialiased`` parameter, which can be set to ``true`` when "
"calling the function."
msgstr ""

#: ../../docs/tutorials/2d/2d_antialiasing.rst:45
msgid ""
"These methods do not require MSAA to be enabled, which makes their "
"*baseline* performance cost low. In other words, there is no permanent added "
"cost if you're not drawing any antialiased geometry at some point."
msgstr ""

#: ../../docs/tutorials/2d/2d_antialiasing.rst:49
msgid ""
"The downside of these antialiasing methods is that they work by generating "
"additional geometry. If you're generating complex 2D geometry that's updated "
"every frame, this may be a bottleneck. Also, Polygon2D, TextureProgressBar, "
"and several custom drawing methods don't feature an antialiased property. "
"For these nodes, you can use 2D multisample antialiasing instead."
msgstr ""

#: ../../docs/tutorials/2d/2d_antialiasing.rst:56
#: ../../docs/tutorials/3d/3d_antialiasing.rst:42
msgid "Multisample antialiasing (MSAA)"
msgstr ""

#: ../../docs/tutorials/2d/2d_antialiasing.rst:58
msgid ""
"Before enabling MSAA in 2D, it's important to understand what MSAA will "
"operate on. MSAA in 2D follows similar restrictions as in 3D. While it does "
"not introduce any blurriness, its scope of application is limited. The main "
"applications of 2D MSAA are:"
msgstr ""

#: ../../docs/tutorials/2d/2d_antialiasing.rst:63
msgid "Geometry edges, such as line and polygon drawing."
msgstr ""

#: ../../docs/tutorials/2d/2d_antialiasing.rst:64
msgid ""
"Sprite edges *only for pixels touching one of the texture's edges*. This "
"works for both linear and nearest-neighbor filtering. Sprite edges created "
"using transparency on the image are not affected by MSAA."
msgstr ""

#: ../../docs/tutorials/2d/2d_antialiasing.rst:68
msgid ""
"The downside of MSAA is that it only operates on edges. This is because MSAA "
"increases the number of *coverage* samples, but not the number of *color* "
"samples. However, since the number of color samples did not increase, "
"fragment shaders are still run for each pixel only once. As a result, MSAA "
"will **not affect** the following kinds of aliasing in any way:"
msgstr ""

#: ../../docs/tutorials/2d/2d_antialiasing.rst:74
msgid "Aliasing *within* nearest-neighbor filtered textures (pixel art)."
msgstr ""

#: ../../docs/tutorials/2d/2d_antialiasing.rst:75
msgid "Aliasing caused by custom 2D shaders."
msgstr ""

#: ../../docs/tutorials/2d/2d_antialiasing.rst:76
msgid "Specular aliasing when using Light2D."
msgstr ""

#: ../../docs/tutorials/2d/2d_antialiasing.rst:77
msgid "Aliasing in font rendering."
msgstr ""

#: ../../docs/tutorials/2d/2d_antialiasing.rst:79
msgid ""
"MSAA can be enabled in the Project Settings by changing the value of the "
"**Rendering > Anti Aliasing > Quality > MSAA 2D** setting. It's important to "
"change the value of the **MSAA 2D** setting and not **MSAA 3D**, as these "
"are entirely separate settings."
msgstr ""

#: ../../docs/tutorials/2d/2d_antialiasing.rst:84
msgid ""
"Comparison between no antialiasing (left) and various MSAA levels (right). "
"The top-left corner contains a Line2D node, the top-right corner contains 2 "
"TextureProgressBar nodes. The bottom contains 8 pixel art sprites, with 4 of "
"them touching the edges (green background) and 4 of them not touching the "
"edges (Godot logo):"
msgstr ""

#: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:4
msgid "Custom drawing in 2D"
msgstr ""

#: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:9
msgid ""
"Godot has nodes to draw sprites, polygons, particles, text, and many other "
"common game development needs. However, if you need something specific not "
"covered with the standard nodes you can make any 2D node (for example, :ref:"
"`Control <class_Control>` or :ref:`Node2D <class_Node2D>`-based) draw on "
"screen using custom commands."
msgstr ""

#: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:15
msgid ""
"Custom drawing in a 2D node is *really* useful. Here are some use cases:"
msgstr ""

#: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:17
msgid ""
"Drawing shapes or logic that existing nodes can't do, such as an image with "
"trails or a special animated polygon."
msgstr ""

#: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:19
msgid ""
"Drawing a large number of simple objects, such as a grid or a board for a 2d "
"game. Custom drawing avoids the overhead of using a large number of nodes, "
"possibly lowering memory usage and improving performance."
msgstr ""

#: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:22
msgid ""
"Making a custom UI control. There are plenty of controls available, but when "
"you have unusual needs, you will likely need a custom control."
msgstr ""

#: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:27
#: ../../docs/tutorials/math/beziers_and_curves.rst:233
#: ../../docs/tutorials/ui/custom_gui_controls.rst:19
msgid "Drawing"
msgstr ""

#: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:29
msgid ""
"Add a script to any :ref:`CanvasItem <class_CanvasItem>` derived node, like :"
"ref:`Control <class_Control>` or :ref:`Node2D <class_Node2D>`. Then override "
"the :ref:`_draw()<class_CanvasItem_private_method__draw>` function."
msgstr ""

#: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:54
msgid ""
"Draw commands are described in the :ref:`CanvasItem <class_CanvasItem>` "
"class reference. There are plenty of them and we will see some of them in "
"the examples below."
msgstr ""

#: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:59
msgid "Updating"
msgstr ""

#: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:61
msgid ""
"The :ref:`_draw <class_CanvasItem_private_method__draw>` function is only "
"called once, and then the draw commands are cached and remembered, so "
"further calls are unnecessary."
msgstr ""

#: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:65
msgid ""
"If re-drawing is required because a variable or something else changed, "
"call :ref:`CanvasItem.queue_redraw <class_CanvasItem_method_queue_redraw>` "
"in that same node and a new ``_draw()`` call will happen."
msgstr ""

#: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:69
msgid ""
"Here is a little more complex example, where we have a texture variable that "
"can be modified at any time, and using a :ref:"
"`setter<doc_gdscript_basics_setters_getters>`, it forces a redraw of the "
"texture when modified:"
msgstr ""

#: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:116
msgid ""
"To see it in action, you can set the texture to be the Godot icon on the "
"editor by dragging and dropping the default ``icon.svg`` from the "
"``FileSystem`` tab to the Texture property on the ``Inspector`` tab. When "
"changing the ``Texture`` property value while the previous script is "
"running, the texture will also change automatically."
msgstr ""

#: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:122
msgid ""
"In some cases, we may need to redraw every frame. For this, call :ref:"
"`queue_redraw <class_CanvasItem_method_queue_redraw>` from the :ref:"
"`_process <class_Node_private_method__process>` method, like this:"
msgstr ""

#: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:155
msgid "Coordinates and line width alignment"
msgstr ""

#: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:157
msgid ""
"The drawing API uses the CanvasItem's coordinate system, not necessarily "
"pixel coordinates. This means ``_draw()`` uses the coordinate space created "
"after applying the CanvasItem's transform. Additionally, you can apply a "
"custom transform on top of it by using :ref:"
"`draw_set_transform<class_CanvasItem_method_draw_set_transform>` or :ref:"
"`draw_set_transform_matrix<class_CanvasItem_method_draw_set_transform_matrix>`."
msgstr ""

#: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:164
msgid ""
"When using :ref:`draw_line <class_CanvasItem_method_draw_line>`, you should "
"consider the width of the line. When using a width that is an odd size, the "
"position of the start and end points should be shifted by ``0.5`` to keep "
"the line centered, as shown below."
msgstr ""

#: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:188
msgid ""
"The same applies to the :ref:`draw_rect <class_CanvasItem_method_draw_rect>` "
"method with ``filled = false``."
msgstr ""

#: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:213
msgid "Antialiased drawing"
msgstr ""

#: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:215
msgid ""
"Godot offers method parameters in :ref:"
"`draw_line<class_CanvasItem_method_draw_line>` to enable antialiasing, but "
"not all custom drawing methods offer this ``antialiased`` parameter."
msgstr ""

#: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:219
msgid ""
"For custom drawing methods that don't provide an ``antialiased`` parameter, "
"you can enable 2D MSAA instead, which affects rendering in the entire "
"viewport. This provides high-quality antialiasing, but a higher performance "
"cost and only on specific elements. See :ref:`doc_2d_antialiasing` for more "
"information."
msgstr ""

#: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:224
msgid ""
"Here is a comparison of a line of minimal width (``width=-1``) drawn with "
"``antialiased=false``, ``antialiased=true``, and ``antialiased=false`` with "
"2D MSAA 2x, 4x, and 8x enabled."
msgstr ""

#: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:233
msgid ""
"Drawing your own nodes might also be desired while running them in the "
"editor. This can be used as a preview or visualization of some feature or "
"behavior."
msgstr ""

#: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:237
msgid ""
"To do this, you can use the :ref:`tool annotation<doc_gdscript_tool_mode>` "
"on both GDScript and C#. See :ref:`the example "
"below<doc_draw_show_drawing_while_editing_example>` and :ref:"
"`doc_running_code_in_the_editor` for more information."
msgstr ""

#: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:245
msgid "Example 1: drawing a custom shape"
msgstr ""

#: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:247
msgid ""
"We will now use the custom drawing functionality of the Godot Engine to draw "
"something that Godot doesn't provide functions for. We will recreate the "
"Godot logo but with code- only using drawing functions."
msgstr ""

#: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:251
msgid "You will have to code a function to perform this and draw it yourself."
msgstr ""

#: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:255
msgid ""
"The following instructions use a fixed set of coordinates that could be too "
"small for high resolution screens (larger than 1080p). If that is your case, "
"and the drawing is too small consider increasing your window scale in ``Menu "
"> Project > Project settings > display/window/stretch/scale`` to adjust the "
"project to a higher resolution (a 2 or 4 scale tends to work well)."
msgstr ""

#: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:262
#, fuzzy
msgid "Drawing a custom polygon shape"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:264
msgid ""
"While there is a dedicated node to draw custom polygons ( :ref:`Polygon2D "
"<class_Polygon2D>`), we will use in this case exclusively lower level "
"drawing functions to combine them on the same node and be able to create "
"more complex shapes later on."
msgstr ""

#: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:269
msgid ""
"First, we will define a set of points -or X and Y coordinates- that will "
"form the base of our shape:"
msgstr ""

#: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:313
msgid ""
"This format, while compact, is not the one that Godot understands to draw a "
"polygon. In a different scenario we could have to load these coordinates "
"from a file or calculate the positions while the application is running, so "
"some transformation may be needed."
msgstr ""

#: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:318
msgid ""
"To transform these coordinates into the right format, we will create a new "
"method ``float_array_to_Vector2Array()``. Then we will override the "
"``_ready()`` function, which Godot will call only once -at the start of the "
"execution- to load those coordinates into a variable:"
msgstr ""

#: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:359
msgid ""
"To finally draw our first shape, we will use the method :ref:`draw_polygon "
"<class_CanvasItem_method_draw_polygon>` and pass the points (as an array of "
"Vector2 coordinates) and its color, like this:"
msgstr ""

#: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:383
msgid "When running it you should see something like this:"
msgstr ""

#: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:387
msgid ""
"Note the lower part of the logo looks segmented- this is because a low "
"amount of points were used to define that part. To simulate a smooth curve, "
"we could add more points to our array, or maybe use a mathematical function "
"to interpolate a curve and create a smooth shape from code (see :ref:"
"`example 2<doc_draw_custom_example_2>`)."
msgstr ""

#: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:393
msgid ""
"Polygons will always **connect its last defined point to its first one** in "
"order to have a closed shape."
msgstr ""

#: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:397
#, fuzzy
msgid "Drawing connected lines"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:399
msgid ""
"Drawing a sequence of connected lines that don't close down to form a "
"polygon is very similar to the previous method. We will use a connected set "
"of lines to draw Godot's logo mouth."
msgstr ""

#: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:403
msgid ""
"First, we will define the list of coordinates that form the mouth shape, "
"like this:"
msgstr ""

#: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:427
msgid ""
"We will load these coordinates into a variable and define an additional "
"variable with the configurable line thickness:"
msgstr ""

#: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:451
msgid ""
"And finally we will use the method :ref:`draw_polyline "
"<class_CanvasItem_method_draw_polyline>` to actually draw the line, like "
"this:"
msgstr ""

#: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:483
#, fuzzy
msgid "You should get the following output:"
msgstr "Glavna dokumentacija za sajt je podeljena na sledeća poglavlja:"

#: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:487
msgid ""
"Unlike ``draw_polygon()``, polylines can only have a single unique color for "
"all its points (the second argument). This method has 2 additional "
"arguments: the width of the line (which is as small as possible by default) "
"and enabling or disabling the anti-aliasing (it is disabled by default)."
msgstr ""

#: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:492
msgid ""
"The order of the ``_draw`` calls is important- like with the Node positions "
"on the tree hierarchy, the different shapes will be drawn from top to "
"bottom, resulting in the latest shapes hiding earlier ones if they overlap. "
"In this case we want the mouth drawn over the head, so we put it afterwards."
msgstr ""

#: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:497
msgid ""
"Notice how we can define colors in different ways, either with a hexadecimal "
"code or a predefined color name. Check the class :ref:`Color <class_Color>` "
"for other constants and ways to define Colors."
msgstr ""

#: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:502
#, fuzzy
msgid "Drawing circles"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:504
msgid ""
"To create the eyes, we are going to add 4 additional calls to draw the eye "
"shapes, in different sizes, colors and positions."
msgstr ""

#: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:507
msgid ""
"To draw a circle, you position it based on its center using the :ref:"
"`draw_circle <class_CanvasItem_method_draw_circle>` method. The first "
"parameter is a :ref:`Vector2<class_Vector2>` with the coordinates of its "
"center, the second is its radius, and the third is its color:"
msgstr ""

#: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:548
msgid "When executing it, you should have something like this:"
msgstr ""

#: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:553
msgid ""
"For partial, unfilled arcs (portions of a circle shape between certain "
"arbitrary angles), you can use the method :ref:`draw_arc "
"<class_CanvasItem_method_draw_arc>`."
msgstr ""

#: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:558
#, fuzzy
msgid "Drawing lines"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:560
msgid ""
"To draw the final shape (the nose) we will use a line to approximate it."
msgstr ""

#: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:562
msgid ""
":ref:`draw_line <class_CanvasItem_method_draw_line>` can be used to draw a "
"single segment by providing its start and end coordinates as arguments, like "
"this:"
msgstr ""

#: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:604
msgid "You should now be able to see the following shape on screen:"
msgstr ""

#: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:608
msgid ""
"Note that if multiple unconnected lines are going to be drawn at the same "
"time, you may get additional performance by drawing all of them in a single "
"call, using the :ref:`draw_multiline "
"<class_CanvasItem_method_draw_multiline>` method."
msgstr ""

#: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:613
#, fuzzy
msgid "Drawing text"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:615
msgid ""
"While using the :ref:`Label <class_Label>` Node is the most common way to "
"add text to your application, the low level `_draw` function includes "
"functionality to add text to your custom Node drawing. We will use it to add "
"the name \"GODOT\" under the robot head."
msgstr ""

#: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:620
msgid ""
"We will use the :ref:`draw_string <class_CanvasItem_method_draw_string>` "
"method to do it, like this:"
msgstr ""

#: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:669
msgid ""
"Here we first load into the defaultFont variable the configured default "
"theme font (a custom one can be set instead) and then we pass the following "
"parameters: font, position, text, horizontal alignment, width, and font size."
msgstr ""

#: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:673
msgid "You should see the following on your screen:"
msgstr ""

#: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:677
msgid ""
"Additional parameters as well as other methods related to text and "
"characters can be found on the :ref:`CanvasItem <class_CanvasItem>` class "
"reference."
msgstr ""

#: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:683
msgid "Show the drawing while editing"
msgstr ""

#: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:685
msgid ""
"While the code so far is able to draw the logo on a running window, it will "
"not show up on the ``2D view`` on the editor. In certain cases you would "
"also like to show your custom Node2D or control on the editor, to position "
"and scale it appropriately, like most other nodes do."
msgstr ""

#: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:690
msgid ""
"To show the logo directly on the editor (without running it), you can use "
"the :ref:`@tool<doc_gdscript_tool_mode>` annotation to request the custom "
"drawing of the node to also appear while editing, like this:"
msgstr ""

#: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:707
msgid ""
"You will need to save your scene, rebuild your project (for C# only) and "
"reload the current scene manually at the menu option ``Scene > Reload Saved "
"Scene`` to refresh the current node in the ``2D`` view the first time you "
"add or remove the ``@tool`` annotation."
msgstr ""

#: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:715
msgid ""
"If we wanted to make the custom shape change at runtime, we could modify the "
"methods called or its arguments at execution time, or apply a transform."
msgstr ""

#: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:718
msgid ""
"For example, if we want the custom shape we just designed to rotate, we "
"could add the following variable and code to the ``_ready`` and ``_process`` "
"methods:"
msgstr ""

#: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:751
msgid ""
"The problem with the above code is that because we have created the points "
"approximately on a rectangle starting from the upper left corner, the ``(0, "
"0)`` coordinate and extending to the right and down, we see that the "
"rotation is done using the top left corner as pivot. A position transform "
"change on the node won't help us here, as the rotation transform is applied "
"first."
msgstr ""

#: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:757
msgid ""
"While we could rewrite all of the points' coordinates to be centered around "
"``(0, 0)``, including negative coordinates, that would be a lot of work."
msgstr ""

#: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:760
msgid ""
"One possible way to work around this is to use the lower level :ref:"
"`draw_set_transform<class_CanvasItem_method_draw_set_transform>` method to "
"fix this issue, translating all points in the CanvasItem's own space, and "
"then moving it back to its original place with a regular node transform, "
"either in the editor or in code, like this:"
msgstr ""

#: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:794
msgid "This is the result, rotating around a pivot now on ``(60, 60)``:"
msgstr ""

#: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:798
msgid ""
"If what we wanted to animate was a property inside the ``_draw()`` call, we "
"must remember to call ``queue_redraw()`` to force a refresh, as otherwise it "
"would not be updated on screen."
msgstr ""

#: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:801
msgid ""
"For example, this is how we can make the robot appear to open and close its "
"mouth, by changing the width of its mouth line follow a sinusoidal (:ref:"
"`sin<class_@globalscope_method_sin>`) curve:"
msgstr ""

#: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:841
msgid "It will look somewhat like this when run:"
msgstr ""

#: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:845
msgid ""
"Please note that ``_mouth_width`` is a user defined property like any other "
"and it or any other used as a drawing argument can be animated using more "
"standard and high level methods such as a :ref:`Tween<class_Tween>` or an :"
"ref:`AnimationPlayer<class_AnimationPlayer>` Node. The only difference is "
"that a ``queue_redraw()`` call is needed to apply those changes so they get "
"shown on screen."
msgstr ""

#: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:855
msgid "Example 2: drawing a dynamic line"
msgstr ""

#: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:857
msgid ""
"The previous example was useful to learn how to draw and modify nodes with "
"custom shapes and animations. This could have some advantages, such as using "
"exact coordinates and vectors for drawing, rather than bitmaps -which means "
"they will scale well when transformed on screen. In some cases, similar "
"results could be achieved composing higher level functionality with nodes "
"such as :ref:`sprites<class_Sprite2D>` or :ref:"
"`AnimatedSprites<class_AnimatedSprite2D>` loading SVG resources (which are "
"also images defined with vectors) and the :ref:"
"`AnimationPlayer<class_AnimationPlayer>` node."
msgstr ""

#: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:867
msgid ""
"In other cases that will not be possible because we will not know what the "
"resulting graphical representation will be before running the code. Here we "
"will see how to draw a dynamic line whose coordinates are not known "
"beforehand, and are affected by the user's input."
msgstr ""

#: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:873
msgid "Drawing a straight line between 2 points"
msgstr ""

#: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:875
msgid ""
"Let's assume we want to draw a straight line between 2 points, the first one "
"will be fixed on the upper left corner ``(0, 0)`` and the second will be "
"defined by the cursor position on screen."
msgstr ""

#: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:879
msgid "We could draw a dynamic line between those 2 points like this:"
msgstr ""

#: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:930
msgid ""
"In this example we obtain the position of the mouse in the default viewport "
"every frame with the method :ref:`get_mouse_position "
"<class_Viewport_method_get_mouse_position>`. If the position has changed "
"since the last draw request (a small optimization to avoid redrawing on "
"every frame)- we will schedule a redraw. Our ``_draw()`` method only has one "
"line: requesting the drawing of a green line of width 10 pixels between the "
"top left corner and that obtained position."
msgstr ""

#: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:938
#, fuzzy
msgid ""
"The width, color, and position of the starting point can be configured with "
"with the corresponding properties."
msgstr "Glavna dokumentacija za sajt je podeljena na sledeća poglavlja:"

#: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:941
msgid "It should look like this when run:"
msgstr ""

#: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:946
msgid "Drawing an arc between 2 points"
msgstr ""

#: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:948
msgid ""
"The above example works, but we may want to join those 2 points with a "
"different shape or function, other than a straight line."
msgstr ""

#: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:951
msgid ""
"Let's try now creating an arc (a portion of a circumference) between both "
"points."
msgstr ""

#: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:954
msgid ""
"Exporting the line starting point, segments, width, color, and antialiasing "
"will allow us to modify those properties very easily directly from the "
"editor inspector panel:"
msgstr ""

#: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:996
msgid ""
"To draw the arc, we can use the method :ref:"
"`draw_arc<class_CanvasItem_method_draw_arc>`. There are many arcs that pass "
"through 2 points, so we will chose for this example the semicircle that has "
"its center in the middle point between the 2 initial points."
msgstr ""

#: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:1002
msgid "Calculating this arc will be more complex than in the case of the line:"
msgstr ""

#: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:1041
msgid ""
"The center of the semicircle will be the middle point between both points. "
"The radius will be half the distance between both points. The start and end "
"angles will be the angles of the vector from point1 to point2 and vice-"
"versa. Note we had to normalize the ``end_angle`` in positive values because "
"if ``end_angle`` is less than ``start_angle``, the arc will be drawn counter-"
"clockwise, which we don't want in this case (the arc would be upside-down)."
msgstr ""

#: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:1050
msgid ""
"The result should be something like this, with the arc going down and "
"between the points:"
msgstr ""

#: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:1055
msgid ""
"Feel free to play with the parameters in the inspector to obtain different "
"results: change the color, the width, the antialiasing, and increase the "
"number of segments to increase the curve smoothness, at the cost of extra "
"performance."
msgstr ""

#: ../../docs/tutorials/2d/2d_movement.rst:4
msgid "2D movement overview"
msgstr ""

#: ../../docs/tutorials/2d/2d_movement.rst:9
msgid ""
"Every beginner has been there: \"How do I move my character?\" Depending on "
"the style of game you're making, you may have special requirements, but in "
"general the movement in most 2D games is based on a small number of designs."
msgstr ""

#: ../../docs/tutorials/2d/2d_movement.rst:13
msgid ""
"We'll use :ref:`CharacterBody2D <class_CharacterBody2D>` for these examples, "
"but the principles will apply to other node types (Area2D, RigidBody2D) as "
"well."
msgstr ""

#: ../../docs/tutorials/2d/2d_movement.rst:19
#: ../../docs/tutorials/animation/2d_skeletons.rst:32
#: ../../docs/tutorials/export/exporting_for_windows.rst:40
#: ../../docs/tutorials/platform/web/customizing_html5_shell.rst:46
#: ../../docs/tutorials/shaders/your_first_shader/your_first_2d_shader.rst:23
#: ../../docs/tutorials/xr/deploying_to_android.rst:7
msgid "Setup"
msgstr ""

#: ../../docs/tutorials/2d/2d_movement.rst:21
msgid ""
"Each example below uses the same scene setup. Start with a "
"``CharacterBody2D`` with two children: ``Sprite2D`` and "
"``CollisionShape2D``. You can use the Godot icon (\"icon.png\") for the "
"Sprite2D's texture or use any other 2D image you have."
msgstr ""

#: ../../docs/tutorials/2d/2d_movement.rst:25
msgid ""
"Open ``Project -> Project Settings`` and select the \"Input Map\" tab. Add "
"the following input actions (see :ref:`InputEvent <doc_inputevent>` for "
"details):"
msgstr ""

#: ../../docs/tutorials/2d/2d_movement.rst:31
msgid "8-way movement"
msgstr ""

#: ../../docs/tutorials/2d/2d_movement.rst:33
msgid ""
"In this scenario, you want the user to press the four directional keys (up/"
"left/down/right or W/A/S/D) and move in the selected direction. The name \"8-"
"way movement\" comes from the fact that the player can move diagonally by "
"pressing two keys at the same time."
msgstr ""

#: ../../docs/tutorials/2d/2d_movement.rst:39
msgid "Add a script to the character body and add the following code:"
msgstr ""

#: ../../docs/tutorials/2d/2d_movement.rst:79
msgid ""
"In the ``get_input()`` function, we use :ref:`Input <class_Input>` "
"``get_vector()`` to check for the four key events and sum return a direction "
"vector."
msgstr ""

#: ../../docs/tutorials/2d/2d_movement.rst:82
msgid ""
"We can then set our velocity by multiplying this direction vector, which has "
"a length of ``1``, by our desired speed."
msgstr ""

#: ../../docs/tutorials/2d/2d_movement.rst:85
msgid ""
"If you've never used vector math before, or need a refresher, you can see an "
"explanation of vector usage in Godot at :ref:`doc_vector_math`."
msgstr ""

#: ../../docs/tutorials/2d/2d_movement.rst:90
msgid ""
"If the code above does nothing when you press the keys, double-check that "
"you've set up input actions correctly as described in the :ref:"
"`doc_2d_movement_setup` part of this tutorial."
msgstr ""

#: ../../docs/tutorials/2d/2d_movement.rst:95
msgid "Rotation + movement"
msgstr ""

#: ../../docs/tutorials/2d/2d_movement.rst:97
msgid ""
"This type of movement is sometimes called \"Asteroids-style\" because it "
"resembles how that classic arcade game worked. Pressing left/right rotates "
"the character, while up/down moves it forward or backward in whatever "
"direction it's facing."
msgstr ""

#: ../../docs/tutorials/2d/2d_movement.rst:150
msgid ""
"Here we've added two variables to track our rotation direction and speed. "
"The rotation is applied directly to the body's ``rotation`` property."
msgstr ""

#: ../../docs/tutorials/2d/2d_movement.rst:153
msgid ""
"To set the velocity, we use the body's ``transform.x`` which is a vector "
"pointing in the body's \"forward\" direction, and multiply that by the speed."
msgstr ""

#: ../../docs/tutorials/2d/2d_movement.rst:157
msgid "Rotation + movement (mouse)"
msgstr ""

#: ../../docs/tutorials/2d/2d_movement.rst:159
msgid ""
"This style of movement is a variation of the previous one. This time, the "
"direction is set by the mouse position instead of the keyboard. The "
"character will always \"look at\" the mouse pointer. The forward/back inputs "
"remain the same, however."
msgstr ""

#: ../../docs/tutorials/2d/2d_movement.rst:202
msgid ""
"Here we're using the :ref:`Node2D <class_Node2D>` ``look_at()`` method to "
"point the player towards the mouse's position. Without this function, you "
"could get the same effect by setting the angle like this:"
msgstr ""

#: ../../docs/tutorials/2d/2d_movement.rst:217
msgid "Click-and-move"
msgstr ""

#: ../../docs/tutorials/2d/2d_movement.rst:219
msgid ""
"This last example uses only the mouse to control the character. Clicking on "
"the screen will cause the player to move to the target location."
msgstr ""

#: ../../docs/tutorials/2d/2d_movement.rst:274
msgid ""
"Note the ``distance_to()`` check we make prior to movement. Without this "
"test, the body would \"jitter\" upon reaching the target position, as it "
"moves slightly past the position and tries to move back, only to move too "
"far and repeat."
msgstr ""

#: ../../docs/tutorials/2d/2d_movement.rst:279
msgid ""
"Uncommenting the ``look_at()`` line will also turn the body to point in its "
"direction of motion if you prefer."
msgstr ""

#: ../../docs/tutorials/2d/2d_movement.rst:282
msgid ""
"This technique can also be used as the basis of a \"following\" character. "
"The ``target`` position can be that of any object you want to move to."
msgstr ""

#: ../../docs/tutorials/2d/2d_movement.rst:288
msgid ""
"You may find these code samples useful as starting points for your own "
"projects. Feel free to use them and experiment with them to see what you can "
"make."
msgstr ""

#: ../../docs/tutorials/2d/2d_movement.rst:291
msgid ""
"You can download this sample project here: `2d_movement_starter.zip <https://"
"github.com/godotengine/godot-docs-project-starters/releases/download/"
"latest-4.x/2d_movement_starter.zip>`_"
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:4
#, fuzzy
msgid "Using TileSets"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/2d/using_tilesets.rst:9
msgid ""
"A tilemap is a grid of tiles used to create a game's layout. There are "
"several benefits to using :ref:`TileMap <class_TileMap>` nodes to design "
"your levels. First, they let you draw a layout by \"painting\" tiles onto a "
"grid, which is much faster than placing individual :ref:`Sprite2D "
"<class_Sprite2D>` nodes one by one. Second, they allow for larger levels "
"because they are optimized for drawing large numbers of tiles. Finally, they "
"allow you to add greater functionality to your tiles with collision, "
"occlusion, and navigation shapes."
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:18
msgid ""
"To use tilemaps, you will need to create a TileSet first. A TileSet is a "
"collection of tiles that can be placed in a TileMap node. After creating a "
"TileSet, you will be able to place them :ref:`using the TileMap editor "
"<doc_using_tilemaps>`."
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:23
msgid ""
"To follow this guide, you will need an image containing your tiles where "
"every tile has the same size (large objects can be split into several "
"tiles). This image is called a *tilesheet*. Tiles do not have to be square: "
"they can be rectangular, hexagonal, or isometric (pseudo-3D perspective)."
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:29
#, fuzzy
msgid "Creating a new TileSet"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/2d/using_tilesets.rst:34
#, fuzzy
msgid "Using a tilesheet"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/2d/using_tilesets.rst:36
msgid ""
"This demonstration will use the following tiles taken from `Kenney's "
"\"Abstract Platformer\" pack <https://kenney.nl/assets/abstract-"
"platformer>`__. We'll use this particular *tilesheet* from the set:"
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:44
msgid "Tilesheet example with 64×64 tiles"
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:44
msgid ""
"Tilesheet with 64×64 tiles. Credit: `Kenney <https://kenney.nl/assets/"
"abstract-platformer>`__"
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:46
msgid ""
"Create a new **TileMap** node, then select it and create a new TileSet "
"resource in the inspector:"
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:52
msgid "Creating a new TileSet resource within the TileMap node"
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:54
msgid ""
"After creating the TileSet resource, click the value to unfold it in the "
"inspector. The default tile shape is Square, but you can also choose "
"Isometric, Half-Offset Square or Hexagon (depending on the shape of your "
"tile images). If using a tile shape other than Square, you may also need to "
"adjust the **Tile Layout** and **Tile Offset Axis** properties. Lastly, "
"enabling the **Rendering > UV Clipping** property may be useful if you wish "
"tiles to be clipped by their tile coordinates. This ensures tiles cannot "
"draw outside their allocated area on the tilesheet."
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:63
msgid ""
"Set the tile size to 64×64 in the inspector to match the example tilesheet:"
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:69
msgid "Setting the tile size to 64×64 to match the example tilesheet"
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:71
msgid ""
"If relying on automatic tiles creation (like we're about to do here), you "
"must set the tile size **before** creating the *atlas*. The atlas will "
"determine which tiles from the tilesheet can be added to a TileMap node (as "
"not every part of the image may be a valid tile)."
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:76
msgid ""
"Open the **TileSet** panel at the bottom of the editor, then click the \"+\" "
"icon in the bottom-left corner to add a new atlas:"
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:83
msgid "Creating a new atlas in a TileSet resource using the bottom panel"
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:85
msgid ""
"After creating an atlas, you must assign a tilesheet texture to it. This can "
"be done by choosing it on the left column of the bottom panel, then clicking "
"the value of the **Texture** property and choosing **Quick Load** (or "
"**Load**). Specify the path to the image file using the file dialog that "
"appears."
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:94
msgid "Loading a tilesheet image in the newly created TileSet atlas"
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:96
msgid ""
"After specifying a valid image, you will be asked whether to create tiles "
"automatically. Answer **Yes**:"
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:103
msgid "Automatically creating tiles based on tilesheet image content"
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:105
msgid ""
"This will automatically create tiles according to the tile size you "
"specified earlier in the TileSet resource. This greatly speeds up initial "
"tile setup."
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:110
msgid ""
"When using automatic tile generation based on image contents, parts of the "
"tilesheet that are *fully* transparent will not have tiles generated."
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:113
msgid ""
"If there are tiles from the tilesheet you do not wish to be present in "
"atlas, choose the Eraser tool at the top of the tileset preview, then click "
"the tiles you wish to remove:"
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:121
msgid "Using the Eraser tool to remove unwanted tiles from the TileSet atlas"
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:123
msgid ""
"You can also right-click a tile and choose **Delete**, as an alternative to "
"the Eraser tool."
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:128
msgid ""
"Like in the 2D and TileMap editors, you can pan across the TileSet panel "
"using the middle or right mouse buttons, and zoom using the mouse wheel or "
"buttons in the top-left corner."
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:132
msgid ""
"If you wish to source tiles from several tilesheet images for a single "
"TileSet, create additional atlases and assign textures to each of them "
"before continuing. It is also possible to use one image per tile this way "
"(although using tilesheets is recommended for better usability)."
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:137
msgid "You can adjust properties for the atlas in the middle column:"
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:143
msgid ""
"Adjusting TileSet atlas properties in the dedicated inspector (part of the "
"TileSet panel)"
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:145
msgid "The following properties can be adjusted on the atlas:"
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:147
msgid "**ID:** The identifier (unique within this TileSet), used for sorting."
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:148
msgid ""
"**Name:** The human-readable name for the atlas. Use a descriptive name here "
"for organizational purposes (such as \"terrain\", \"decoration\", etc)."
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:150
msgid ""
"**Margins:** The margins on the image's edges that should not be selectable "
"as tiles (in pixels). Increasing this can be useful if you download a "
"tilesheet image that has margins on the edges (e.g. for attribution)."
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:153
msgid ""
"**Separation:** The separation between each tile on the atlas in pixels. "
"Increasing this can be useful if the tilesheet image you're using contains "
"guides (such as outlines between every tile)."
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:156
msgid ""
"**Texture Region Size:** The size of each tile on the atlas in pixels. In "
"most cases, this should match the tile size defined in the TileMap property "
"(although this is not strictly necessary)."
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:159
msgid ""
"**Use Texture Padding:** If checked, adds a 1-pixel transparent edge around "
"each tile to prevent texture bleeding when filtering is enabled. It's "
"recommended to leave this enabled unless you're running into rendering "
"issues due to texture padding."
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:164
msgid ""
"Note that changing texture margin, separation and region size may cause "
"tiles to be lost (as some of them would be located outside the atlas image's "
"coordinates). To regenerate tiles automatically from the tilesheet, use the "
"three vertical dots menu button at the top of the TileSet editor and choose "
"**Create Tiles in Non-Transparent Texture Regions**:"
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:174
msgid "Recreating tiles automatically after changing atlas properties"
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:177
msgid "Using a collection of scenes"
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:179
msgid ""
"Since Godot 4.0, you can place actual *scenes* as tiles. This allows you to "
"use any collection of nodes as a tile. For example, you could use scene "
"tiles to place gameplay elements, such as shops the player may be able to "
"interact with. You could also use scene tiles to place AudioStreamPlayer2Ds "
"(for ambient sounds), particle effects, and more."
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:187
msgid ""
"Scene tiles come with a greater performance overhead compared to atlases, as "
"every scene is instanced individually for every placed tile."
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:190
msgid ""
"It's recommended to use only scene tiles when necessary. To draw sprites in "
"a tile without any kind of advanced manipulation, :ref:`use atlases instead "
"<doc_creating_tilesets_using_tilesheet>`."
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:194
msgid ""
"For this example, we'll create a scene containing a CPUParticles2D root "
"node. Save this scene to a scene file (separate from the scene containing "
"the TileMap), then switch to the scene containing the TileMap node. Open the "
"TileSet editor, and create a new **Scenes Collection** in the left column:"
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:203
msgid "Creating a scenes collection in the TileSet editor"
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:205
msgid ""
"After creating a scenes collection, you can enter a descriptive name for the "
"scenes collection in the middle column if you wish. Select this scenes "
"collection then create a new scene slot:"
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:213
msgid ""
"Creating a scene tile after selecting the scenes collection in the TileSet "
"editor"
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:215
msgid ""
"Select this scene slot in the right column, then use **Quick Load** (or "
"**Load**) to load the scene file containing the particles:"
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:222
msgid ""
"Creating a scene slot, then loading a scene file into it in the TileSet "
"editor"
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:224
msgid ""
"You now have a scene tile in your TileSet. Once you switch to the TileMap "
"editor, you'll be able to select it from the scenes collection and paint it "
"like any other tile."
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:229
msgid "Merging several atlases into a single atlas"
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:231
msgid ""
"Using multiple atlases within a single TileSet resource can sometimes be "
"useful, but it can also be cumbersome in certain situations (especially if "
"you're using one image per tile). Godot allows you to merge several atlases "
"into a single atlas for easier organization."
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:236
msgid ""
"To do so, you must have more than one atlas created in the TileSet resource. "
"Use the \"three vertical dots\" menu button located at the bottom of the "
"list of atlases, then choose **Open Atlas Merging Tool**:"
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:244
msgid "Opening the atlas merging tool after creating multiple atlases"
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:246
msgid ""
"This will open a dialog, in which you can select several atlases by holding :"
"kbd:`Shift` or :kbd:`Ctrl` then clicking on multiple elements:"
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:253
msgid "Using the atlas merging tool dialog"
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:255
msgid ""
"Choose **Merge** to merge the selected atlases into a single atlas image "
"(which translates to a single atlas within the TileSet). The unmerged "
"atlases will be removed within the TileSet, but *the original tilesheet "
"images will be kept on the filesystem*. If you don't want the unmerged "
"atlases to be removed from the TileSet resource, choose **Merge (Keep "
"Original Atlases)** instead."
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:263
msgid ""
"TileSet features a system of *tile proxies*. Tile proxies are a mapping "
"table that allows notifying the TileMap using a given TileSet that a given "
"set of tile identifiers should be replaced by another one."
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:267
msgid ""
"Tile proxies are automatically set up when merging different atlases, but "
"they can also be set manually thanks to the **Manage Tile Proxies** dialog "
"you can access using the \"three vertical dots\" menu mentioned above."
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:271
msgid ""
"Manually creating tile proxies may be useful when you changed an atlas ID or "
"want to replace all tiles from an atlas by the ones from another atlas. Note "
"that when editing a TileMap, you can replace all cells by their "
"corresponding mapped value."
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:277
msgid "Adding collision, navigation and occlusion to the TileSet"
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:279
msgid ""
"We've now successfully created a basic TileSet. We could start using in the "
"TileMap node now, but it currently lacks any form of collision detection. "
"This means the player and other objects could walk straight through the "
"floor or walls."
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:284
msgid ""
"If you use :ref:`2D navigation <doc_navigation_overview_2d>`, you'll also "
"need to define navigation polygons for tiles to generate a navigation mesh "
"that agents can use for pathfinding."
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:288
msgid ""
"Lastly, if you use :ref:`doc_2d_lights_and_shadows` or GPUParticles2D, you "
"may also want your TileSet to be able to cast shadows and collide with "
"particles. This requires defining occluder polygons for \"solid\" tiles on "
"the TileSet."
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:292
msgid ""
"To be able to define collision, navigation and occlusion shapes for each "
"tile, you will need to create a physics, navigation or occlusion layer for "
"the TileSet resource first. To do so, select the TileMap node, click the "
"TileSet property value in the inspector to edit it then unfold **Physics "
"Layers** and choose **Add Element**:"
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:302
msgid ""
"Creating a physics layer in the TileSet resource inspector (within the "
"TileMap node)"
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:304
msgid ""
"If you also need navigation support, now is a good time to create a "
"navigation layer:"
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:310
msgid ""
"Creating a navigation layer in the TileSet resource inspector (within the "
"TileMap node)"
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:312
msgid ""
"If you need support for light polygon occluders, now is a good time to "
"create an occlusion layer:"
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:318
msgid ""
"Creating an occlusion layer in the TileSet resource inspector (within the "
"TileMap node)"
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:322
msgid ""
"Future steps in this tutorial are tailored to creating collision polygons, "
"but the procedure for navigation and occlusion is very similar. Their "
"respective polygon editors behave in the same way, so these steps are not "
"repeated for brevity."
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:327
msgid ""
"The only caveat is that the tile's occlusion polygon property is part of a "
"**Rendering** subsection in the atlas inspector. Make sure to unfold this "
"section so you can edit the polygon."
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:331
msgid ""
"After creating a physics layer, you have access to the **Physics Layer** "
"section in the TileSet atlas inspector:"
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:338
msgid "Opening the collision editor while in Select mode"
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:340
msgid ""
"You can quickly create a rectangle collision shape by pressing :kbd:`F` "
"while the TileSet editor is focused. If the keyboard shortcut doesn't work, "
"try clicking in the empty area around the polygon editor to focus it:"
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:348
msgid "Using default rectangle collision shape by pressing :kbd:`F`"
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:350
msgid ""
"In this tile collision editor, you have access to all the 2D polygon editing "
"tools:"
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:352
msgid ""
"Use the toolbar above the polygon to toggle between creating a new polygon, "
"editing an existing polygon and removing points on the polygon. The \"three "
"vertical dots\" menu button offers additional options, such as rotating and "
"flipping the polygon."
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:355
msgid "Create new points by clicking and dragging a line between two points."
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:356
msgid ""
"Remove a point by right-clicking it (or using the Remove tool described "
"above and left-clicking)."
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:358
msgid ""
"Pan in the editor by middle-clicking or right-clicking. (Right-click panning "
"can only be used in areas where there is no point nearby.)"
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:361
msgid ""
"You can use the default rectangle shape to quickly create a triangle-shaped "
"collision shape by removing one of the points:"
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:368
msgid ""
"Creating a triangle collision shape by right-clicking one of the corners to "
"remove it"
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:370
msgid ""
"You can also use the rectangle as a base for more complex shapes by adding "
"more points:"
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:376
msgid "Drawing a custom collision for a complex tile shape"
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:380
msgid ""
"If you have a large tileset, specifying the collision for each tile "
"individually could take a lot of time. This is especially true as TileMaps "
"tend to have many tiles with common collision patterns (such as solid blocks "
"or 45-degree slopes). To apply a similar collision shape to several tiles "
"quickly, use functionality to :ref:`assign properties to multiple tiles at "
"once <doc_using_tilemaps_assigning_properties_to_multiple_tiles>`."
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:388
msgid "Assigning custom metadata to the TileSet's tiles"
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:390
msgid ""
"You can assign custom data on a per-tile basis using *custom data layers*. "
"This can be useful to store information specific to your game, such as the "
"damage that a tile should deal when the player touches it, or whether a tile "
"can be destroyed using a weapon."
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:395
msgid ""
"The data is associated with the tile in the TileSet: all instances of the "
"placed tile will use the same custom data. If you need to create a variant "
"of a tile that has different custom data, this can be done by :ref:`creating "
"an alternative tile <doc_using_tilesets_creating_alternative_tiles>` and "
"changing the custom data for the alternative tile only."
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:405
msgid ""
"Creating a custom data layer in the TileSet resource inspector (within the "
"TileMap node)"
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:411
msgid "Example of configured custom data layers with game-specific properties"
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:413
msgid ""
"You can reorder custom data without breaking existing metadata: the TileSet "
"editor will update automatically after reordering custom data properties."
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:416
msgid ""
"Note that in the editor, property names do not appear (only their index, "
"which matches the order in which they are defined). For example, with the "
"custom data layers example shown above, we're assigning a tile to have the "
"``damage_per_second`` metadata set to ``25`` and the ``destructible`` "
"metadata to ``false``:"
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:426
msgid "Editing custom data in the TileSet editor while in Select mode"
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:428
msgid ""
":ref:`Tile property painting "
"<doc_using_tilemaps_using_tile_property_painting>` can also be used for "
"custom data:"
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:435
msgid ""
"Assigning custom data in the TileSet editor using tile property painting"
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:440
#, fuzzy
msgid "Creating terrain sets (autotiling)"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/2d/using_tilesets.rst:444
msgid ""
"This functionality was implemented in a different form as *autotiling* in "
"Godot 3.x. Terrains are essentially a more powerful replacement of "
"autotiles. Unlike autotiles, terrains can support transitions from one "
"terrain to another, as a tile may define several terrains at once."
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:449
msgid ""
"Unlike before, where autotiles were a specific kind of tiles, terrains are "
"only a set of properties assigned to atlas tiles. These properties are then "
"used by a dedicated TileMap painting mode that selects tiles featuring "
"terrain data in a smart way. This means any terrain tile can be either "
"painted as terrain or as a single tile, like any other."
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:455
msgid ""
"A \"polished\" tileset generally features variations that you should use on "
"corners or edges of platforms, floors, etc. While these can be placed "
"manually, this quickly becomes tedious. Handling this situation with "
"procedurally generated levels can also be difficult and require a lot of "
"code."
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:460
msgid ""
"Godot offers *terrains* to perform this kind of tile connections "
"automatically. This allows you to have the \"correct\" tile variants "
"automatically used."
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:463
msgid ""
"Terrains are grouped into terrain sets. Each terrain set is assigned a mode "
"from **Match Corners and Sides**, **Match Corners** and **Match sides**. "
"They define how terrains are matched to each other in a terrain set."
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:469
msgid ""
"The above modes correspond to the previous bitmask modes autotiles used in "
"Godot 3.x: 2×2, 3×3 or 3×3 minimal. This is also similar to what the `Tiled "
"<https://www.mapeditor.org/>`__ editor features."
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:473
msgid ""
"Select the TileMap node, go to the inspector and create a new terrain set "
"within the TileSet *resource*:"
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:479
msgid ""
"Creating a terrain set in the TileSet resource inspector (within the TileMap "
"node)"
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:481
msgid ""
"After creating a terrain set, you **must** create one or more terrains "
"*within* the terrain set:"
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:487
#, fuzzy
msgid "Creating a terrain within the terrain set"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/2d/using_tilesets.rst:489
msgid ""
"In the TileSet editor, switch to Select mode and click a tile. In the middle "
"column, unfold the **Terrains** section then assign a terrain set ID and a "
"terrain ID for the tile. ``-1`` means \"no terrain set\" or \"no terrain\", "
"which means you must set **Terrain Set** to ``0`` or greater before you can "
"set **Terrain** to ``0`` or greater."
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:497
msgid ""
"Terrain set IDs and terrain IDs are independent from each other. They also "
"start from ``0``, not ``1``."
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:504
msgid ""
"Configuring terrain on a single tile in the TileSet editor's Select mode"
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:506
msgid ""
"After doing so, you can now configure the **Terrain Peering Bits** section "
"which becomes visible in the middle column. The peering bits determine which "
"tile will be placed depending on neighboring tiles. ``-1`` is a special "
"value which refers to empty space."
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:511
msgid ""
"For example, if a tile has all its bits set to ``0`` or greater, it will "
"only appear if *all* 8 neighboring tiles are using a tile with the same "
"terrain ID. If a tile has its bits set to ``0`` or greater, but the top-"
"left, top and top-right bits are set to ``-1``, it will only appear if there "
"is empty space on top of it (including diagonally)."
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:521
msgid ""
"Configuring terrain peering bits on a single tile in the TileSet editor's "
"Select mode"
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:523
msgid "An example configuration for a full tilesheet may look as follows:"
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:529
msgid "Example full tilesheet for a sidescrolling game"
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:535
msgid ""
"Example full tilesheet for a sidescrolling game with terrain peering bits "
"visible"
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:540
msgid "Assigning properties to multiple tiles at once"
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:542
msgid ""
"There are two ways to assign properties to multiple tiles at once. Depending "
"on your use cases, one method may be faster than the other:"
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:546
msgid "Using multiple tile selection"
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:548
msgid ""
"If you wish to configure various properties on several times at once, choose "
"the **Select** mode at the top of the TileSet editor:"
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:551
msgid ""
"After doing this, you can select multiple tiles on the right column by "
"holding :kbd:`Shift` then clicking on tiles. You can also perform rectangle "
"selection by holding down the left mouse button then dragging the mouse. "
"Lastly, you can deselect tiles that were already selected (without affecting "
"the rest of the selection) by holding :kbd:`Shift` then clicking on a "
"selected tile."
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:557
msgid ""
"You can then assign properties using the inspector in the middle column of "
"the TileSet editor. Only properties that you change here will be applied to "
"all selected tiles. Like in the editor's inspector, properties that differ "
"on selected tiles will remain different until you edit them."
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:562
msgid ""
"With numerical and color properties, you will also see a preview of the "
"property's value on all tiles in the atlas after editing a property:"
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:569
msgid ""
"Selecting multiple tiles using the Select mode, then applying properties"
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:574
#, fuzzy
msgid "Using tile property painting"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/2d/using_tilesets.rst:576
msgid ""
"If you wish to apply a single property to several tiles at once, you can use "
"the *property painting* mode for this purpose."
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:579
msgid ""
"Configure a property to be painted in the middle column, then click on tiles "
"(or hold down the left mouse button) in the right column to \"paint\" "
"properties onto tiles."
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:587
#, fuzzy
msgid "Painting tile properties using the TileSet editor"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/2d/using_tilesets.rst:589
msgid ""
"Tile property painting is especially useful with properties that are time-"
"consuming to set manually, such as collision shapes:"
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:596
msgid "Painting a collision polygon, then left-clicking tiles to apply it"
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:601
#, fuzzy
msgid "Creating alternative tiles"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/2d/using_tilesets.rst:603
msgid ""
"Sometimes, you want to use a single tile image (found only once within the "
"atlas), but configured in different ways. For example, you may want to use "
"the same tile image, but rotated, flipped, or modulated with a different "
"color. This can be done using *alternative tiles*."
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:610
msgid ""
"Since Godot 4.2, you don't have to create alternative tiles to rotate or "
"flip tiles anymore. You can rotate any tile while placing it in the TileMap "
"editor by using the rotation/flip buttons in the TileMap editor toolbar."
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:615
msgid ""
"To create an alternative tile, right-click a base tile in the atlas "
"displayed by the TileSet editor, then choose **Create an Alternative Tile**:"
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:622
msgid ""
"Creating an alternative tile by right-clicking a base tile in the TileSet "
"editor"
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:624
msgid ""
"If currently in Select mode, the alternative tile will already be selected "
"for editing. If not currently in Select mode, you can still create "
"alternative tiles, but you will need to switch to Select mode and select the "
"alternative tile to edit it."
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:629
msgid ""
"If you don't see the alternative tile, pan over to the right of the atlas "
"image, as alternative tiles always appear on the right of base tiles of a "
"given atlas in the TileSet editor:"
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:637
msgid "Configuring an alternative tile after clicking it in the TileSet editor"
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:639
msgid ""
"After selecting an alternative tile, you can change any properties using the "
"middle column like you would on a base tile. However, the list of exposed "
"properties is different compared to base tiles:"
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:643
msgid ""
"**Alternative ID:** The unique numerical identifier for this alternative "
"tile. Changing it will break existing TileMaps, so be careful! This ID also "
"controls the sorting in the list of alternative tiles displayed in the "
"editor."
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:646
msgid "**Rendering > Flip H:** If ``true``, the tile is horizontally flipped."
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:647
msgid "**Rendering > Flip V:** If ``true``, the tile is vertically flipped."
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:648
msgid ""
"**Rendering > Transpose:** If ``true``, the tile is rotated 90 degrees "
"*counter-clockwise* and then flipped vertically. In practice, this means "
"that to rotate a tile by 90 degrees clockwise without flipping it, you "
"should enable **Flip H** and **Transpose**. To rotate a tile by 180 degrees "
"clockwise, enable **Flip H** and **Flip V**. To rotate a tile by 270 degrees "
"clockwise, enable **Flip V** and **Transpose**."
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:654
msgid ""
"**Rendering > Texture Origin:** The origin to use for drawing the tile. This "
"can be used to visually offset the tile compared to the base tile."
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:656
msgid ""
"**Rendering > Modulate:** The color multiplier to use when rendering the "
"tile."
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:657
msgid ""
"**Rendering > Material:** The material to use for this tile. This can be "
"used to apply a different blend mode or custom shaders to a single tile."
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:659
msgid ""
"**Z Index:** The sorting order for this tile. Higher values will make the "
"tile render in front of others on the same layer."
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:661
msgid ""
"**Y Sort Origin:** The vertical offset to use for tile sorting based on its "
"Y coordinate (in pixels). This allows using layers as if they were on "
"different height for top-down games. Adjusting this can help alleviate "
"issues with sorting certain tiles. Only effective if **Y Sort Enabled** is "
"``true`` on the TileMap layer the tile is placed on."
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:667
msgid ""
"You can create an additional alternative tile variant by clicking the large "
"\"+\" icon next to the alternative tile. This is equivalent to selecting the "
"base tile and right-clicking it to choose **Create an Alternative Tile** "
"again."
msgstr ""

#: ../../docs/tutorials/2d/using_tilesets.rst:673
msgid ""
"When creating an alternative tile, none of the properties from the base tile "
"are inherited. You must set properties again on the alternative tile if you "
"wish those to be identical on the base tile and the alternative tile."
msgstr ""

#: ../../docs/tutorials/2d/using_tilemaps.rst:4
#, fuzzy
msgid "Using TileMaps"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/2d/using_tilemaps.rst:8
msgid ""
"This page assumes you have created or downloaded a TileSet already. If not, "
"please read :ref:`doc_using_tilesets` first as you will need a TileSet to "
"create a TileMap."
msgstr ""

#: ../../docs/tutorials/2d/using_tilemaps.rst:15
msgid ""
"A tilemap is a grid of tiles used to create a game's layout. There are "
"several benefits to using :ref:`TileMap <class_TileMap>` nodes to design "
"your levels. First, they make it possible to draw the layout by \"painting\" "
"the tiles onto a grid, which is much faster than placing individual :ref:"
"`Sprite2D <class_Sprite2D>` nodes one by one. Second, they allow for much "
"larger levels because they are optimized for drawing large numbers of tiles. "
"Finally, you can add collision, occlusion, and navigation shapes to tiles, "
"adding greater functionality to the TileMap."
msgstr ""

#: ../../docs/tutorials/2d/using_tilemaps.rst:25
msgid "Specifying the TileSet in the TileMap"
msgstr ""

#: ../../docs/tutorials/2d/using_tilemaps.rst:27
msgid ""
"If you've followed the previous page on :ref:`doc_using_tilesets`, you "
"should have a TileSet resource that is built-in to the TileMap node. This is "
"good for prototyping, but in a real world project, you will generally have "
"multiple levels reusing the same tileset."
msgstr ""

#: ../../docs/tutorials/2d/using_tilemaps.rst:32
msgid ""
"The recommended way to reuse the same TileSet in several TileMap nodes is to "
"save the TileSet to an external resource. To do so, click the dropdown next "
"to the TileSet resource and choose **Save**:"
msgstr ""

#: ../../docs/tutorials/2d/using_tilemaps.rst:40
msgid "Saving the built-in TileSet resource to an external resource file"
msgstr ""

#: ../../docs/tutorials/2d/using_tilemaps.rst:43
#, fuzzy
msgid "Creating TileMap layers"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/2d/using_tilemaps.rst:45
msgid ""
"As of Godot 4.0, you can place several *layers* in a single TileMap node. "
"For example, this allows you to distinguish foreground tiles from background "
"tiles for better organization. You can place one tile per layer at a given "
"location, which allows you to overlap several tiles together if you have "
"more than one layer."
msgstr ""

#: ../../docs/tutorials/2d/using_tilemaps.rst:50
msgid ""
"By default, a TileMap node automatically has one premade layer. You do not "
"have to create additional layers if you only need a single layer, but if you "
"wish to do so now, select the TileMap node and unfold the **Layers** section "
"in the inspector:"
msgstr ""

#: ../../docs/tutorials/2d/using_tilemaps.rst:59
msgid ""
"Creating layers in a TileMap node (example with \"background\" and "
"\"foreground\")"
msgstr ""

#: ../../docs/tutorials/2d/using_tilemaps.rst:61
msgid "Each layer has several properties you can adjust:"
msgstr ""

#: ../../docs/tutorials/2d/using_tilemaps.rst:63
msgid ""
"**Name:** A human-readable name to display in the TileMap editor. This can "
"be something like \"background\", \"buildings\", \"vegetation\", etc."
msgstr ""

#: ../../docs/tutorials/2d/using_tilemaps.rst:65
msgid ""
"**Enabled:** If ``true``, the layer is visible in the editor and when "
"running the project."
msgstr ""

#: ../../docs/tutorials/2d/using_tilemaps.rst:67
msgid ""
"**Modulate:** The color to use as a multiplier for all tiles on the layer. "
"This is also multiplied with the per-tile **Modulate** property and the "
"TileMap node's **Modulate** property. For example, you can use this to "
"darken background tiles to make foreground tiles stand out more."
msgstr ""

#: ../../docs/tutorials/2d/using_tilemaps.rst:71
msgid ""
"**Y Sort Enabled:** If ``true``, sorts tiles based on their Y position on "
"the TileMap. This can be used to prevent sorting issues with certain tile "
"setups, especially with isometric tiles."
msgstr ""

#: ../../docs/tutorials/2d/using_tilemaps.rst:74
msgid ""
"**Y Sort Origin:** The vertical offset to use for Y-sorting on each tile (in "
"pixels). Only effective if **Y Sort Enabled** is ``true``."
msgstr ""

#: ../../docs/tutorials/2d/using_tilemaps.rst:76
msgid ""
"**Z Index:** Controls whether this layer is drawn in front of or behind "
"other TileMap layers. This value can be positive or negative; the layer with "
"the highest Z Index is drawn on top of other layers. If several layers have "
"an equal Z Index property, the layer that is *last* in the list of layers "
"(the one which appears at the bottom in the list) is drawn on top."
msgstr ""

#: ../../docs/tutorials/2d/using_tilemaps.rst:82
msgid ""
"You can reorder layers by drag-and-dropping the \"three horizontal bars\" "
"icon on the left of the entries in the **Layers** section."
msgstr ""

#: ../../docs/tutorials/2d/using_tilemaps.rst:87
msgid ""
"You can create, rename or reorder layers in the future without affecting "
"existing tiles. Be careful though, as *removing* a layer will also remove "
"all tiles that were placed on the layer."
msgstr ""

#: ../../docs/tutorials/2d/using_tilemaps.rst:92
#, fuzzy
msgid "Opening the TileMap editor"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/2d/using_tilemaps.rst:94
msgid ""
"Select the TileMap node, then open the TileMap panel at the bottom of the "
"editor:"
msgstr ""

#: ../../docs/tutorials/2d/using_tilemaps.rst:101
msgid ""
"Opening the TileMap panel at the bottom of the editor. The TileMap node must "
"be selected first."
msgstr ""

#: ../../docs/tutorials/2d/using_tilemaps.rst:104
msgid "Selecting tiles to use for painting"
msgstr ""

#: ../../docs/tutorials/2d/using_tilemaps.rst:106
msgid ""
"First, if you've created additional layers above, make sure you've selected "
"the layer you wish to paint on:"
msgstr ""

#: ../../docs/tutorials/2d/using_tilemaps.rst:113
msgid "Selecting a layer to paint on in the TileMap editor"
msgstr ""

#: ../../docs/tutorials/2d/using_tilemaps.rst:117
msgid ""
"In the 2D editor, the layers you aren't currently editing from the same "
"TileMap node will appear grayed out while in the TileMap editor. You can "
"disable this behavior by clicking the icon next to the layer selection menu "
"(**Highlight Selected TileMap Layer** tooltip)."
msgstr ""

#: ../../docs/tutorials/2d/using_tilemaps.rst:122
msgid ""
"You can skip the above step if you haven't created additional layers, as the "
"first layer is automatically selected when entering the TileMap editor."
msgstr ""

#: ../../docs/tutorials/2d/using_tilemaps.rst:125
msgid ""
"Before you can place tiles in the 2D editor, you must select one or more "
"tiles in the TileMap panel located at the bottom of the editor. To do so, "
"click a tile in the TileMap panel, or hold down the mouse button to select "
"multiple tiles:"
msgstr ""

#: ../../docs/tutorials/2d/using_tilemaps.rst:133
msgid "Selecting a tile in the TileMap editor by clicking it"
msgstr ""

#: ../../docs/tutorials/2d/using_tilemaps.rst:137
msgid ""
"Like in the 2D and TileSet editors, you can pan across the TileMap panel "
"using the middle or right mouse buttons, and zoom using the mouse wheel or "
"buttons in the top-left corner."
msgstr ""

#: ../../docs/tutorials/2d/using_tilemaps.rst:141
msgid ""
"You can also hold down :kbd:`Shift` to append to the current selection. When "
"selecting more than one tile, multiple tiles will be placed every time you "
"perform a painting operation. This can be used to paint structures composed "
"of multiple tiles in a single click (such as large platforms or trees)."
msgstr ""

#: ../../docs/tutorials/2d/using_tilemaps.rst:146
msgid ""
"The final selection does not have to be contiguous: if there is empty space "
"between selected tiles, it will be left empty in the pattern that will be "
"painted in the 2D editor."
msgstr ""

#: ../../docs/tutorials/2d/using_tilemaps.rst:154
msgid ""
"Selecting multiple tiles in the TileMap editor by holding down the left "
"mouse button"
msgstr ""

#: ../../docs/tutorials/2d/using_tilemaps.rst:156
msgid ""
"If you've created alternative tiles in your TileSet, you can select them for "
"painting on the right of the base tiles:"
msgstr ""

#: ../../docs/tutorials/2d/using_tilemaps.rst:163
msgid "Selecting an alternative tile in the TileMap editor"
msgstr ""

#: ../../docs/tutorials/2d/using_tilemaps.rst:165
msgid ""
"Lastly, if you've created a *scenes collection* in the TileSet, you can "
"place scene tiles in the TileMap:"
msgstr ""

#: ../../docs/tutorials/2d/using_tilemaps.rst:171
msgid "Placing a scene tile containing particles using the TileMap editor"
msgstr ""

#: ../../docs/tutorials/2d/using_tilemaps.rst:174
msgid "Painting modes and tools"
msgstr ""

#: ../../docs/tutorials/2d/using_tilemaps.rst:176
msgid ""
"Using the toolbar at the top of the TileMap editor, you can choose between "
"several painting modes and tools. These modes affect operation when clicking "
"in the 2D editor, **not** the TileMap panel itself."
msgstr ""

#: ../../docs/tutorials/2d/using_tilemaps.rst:180
msgid "From left to right, the painting modes and tools you can choose are:"
msgstr ""

#: ../../docs/tutorials/2d/using_tilemaps.rst:183
#, fuzzy
msgid "Selection"
msgstr "Kopiraj Označeno"

#: ../../docs/tutorials/2d/using_tilemaps.rst:185
msgid ""
"Select tiles by clicking a single tile, or by holding down the left mouse "
"button to select multiple with a rectangle in the 2D editor. Note that empty "
"space cannot be selected: if you create a rectangle selection, only non-"
"empty tiles will be selected."
msgstr ""

#: ../../docs/tutorials/2d/using_tilemaps.rst:189
msgid ""
"To append to the current selection, hold :kbd:`Shift` then select a tile. To "
"remove from the current selection, hold :kbd:`Ctrl` then select a tile."
msgstr ""

#: ../../docs/tutorials/2d/using_tilemaps.rst:192
msgid ""
"The selection can then be used in any other painting mode to quickly create "
"copies of an already-placed pattern."
msgstr ""

#: ../../docs/tutorials/2d/using_tilemaps.rst:195
msgid ""
"You can remove the selected tiles from the TileMap by pressing :kbd:`Del`."
msgstr ""

#: ../../docs/tutorials/2d/using_tilemaps.rst:197
msgid ""
"You can toggle this mode temporarily while in Paint mode by holding :kbd:"
"`Ctrl` then performing a selection."
msgstr ""

#: ../../docs/tutorials/2d/using_tilemaps.rst:202
msgid ""
"You can copy and paste tiles that were already placed by performing a "
"selection, pressing :kbd:`Ctrl + C` then pressing :kbd:`Ctrl + V`. The "
"selection will be pasted after left-clicking. You can press :kbd:`Ctrl + V` "
"another time to perform more copies this way. Right-click or press :kbd:"
"`Escape` to cancel pasting."
msgstr ""

#: ../../docs/tutorials/2d/using_tilemaps.rst:211
msgid ""
"The standard Paint mode allows you to place tiles by clicking or holding "
"down the left mouse button."
msgstr ""

#: ../../docs/tutorials/2d/using_tilemaps.rst:214
msgid ""
"If you right-click, the currently selected tile will be erased from the "
"tilemap. In other words, it will be replaced by empty space."
msgstr ""

#: ../../docs/tutorials/2d/using_tilemaps.rst:217
msgid ""
"If you have selected multiple tiles in the TileMap or using the Selection "
"tool, they will be placed every time you click or drag the mouse while "
"holding down the left mouse button."
msgstr ""

#: ../../docs/tutorials/2d/using_tilemaps.rst:223
msgid ""
"While in Paint mode, you can draw a line by holding :kbd:`Shift` *before* "
"holding down the left mouse button, then dragging the mouse to the line's "
"end point. This is identical to using the Line tool described below."
msgstr ""

#: ../../docs/tutorials/2d/using_tilemaps.rst:227
msgid ""
"You can also draw a rectangle by holding :kbd:`Ctrl` and :kbd:`Shift` "
"*before* holding down the left mouse button, then dragging the mouse to the "
"rectangle's end point. This is identical to using the Rectangle tool "
"described below."
msgstr ""

#: ../../docs/tutorials/2d/using_tilemaps.rst:232
msgid ""
"Lastly, you can pick existing tiles in the 2D editor by holding :kbd:`Ctrl` "
"then clicking on a tile (or holding and dragging the mouse). This will "
"switch the currently painted tile(s) to the tile(s) you've just clicked. "
"This is identical to using the Picker tool described below."
msgstr ""

#: ../../docs/tutorials/2d/using_tilemaps.rst:240
msgid ""
"After selecting Line Paint mode, you can draw in a line that is always 1 "
"tile thick (no matter its orientation)."
msgstr ""

#: ../../docs/tutorials/2d/using_tilemaps.rst:243
msgid "If you right-click while in Line Paint mode, you will erase in a line."
msgstr ""

#: ../../docs/tutorials/2d/using_tilemaps.rst:245
msgid ""
"If you have selected multiple tiles in the TileMap or using the Selection "
"tool, you can place them in a repeating pattern across the line."
msgstr ""

#: ../../docs/tutorials/2d/using_tilemaps.rst:248
msgid ""
"You can toggle this mode temporarily while in Paint or Eraser mode by "
"holding :kbd:`Shift` then drawing."
msgstr ""

#: ../../docs/tutorials/2d/using_tilemaps.rst:255
msgid ""
"Using the line tool after selecting two tiles to draw platforms diagonally"
msgstr ""

#: ../../docs/tutorials/2d/using_tilemaps.rst:258
msgid "Rectangle"
msgstr ""

#: ../../docs/tutorials/2d/using_tilemaps.rst:260
msgid ""
"After selecting Rectangle Paint mode, you can draw in an axis-aligned "
"rectangle."
msgstr ""

#: ../../docs/tutorials/2d/using_tilemaps.rst:263
msgid ""
"If you right-click while in Rectangle Paint mode, you will erase in an axis-"
"aligned rectangle."
msgstr ""

#: ../../docs/tutorials/2d/using_tilemaps.rst:266
msgid ""
"If you have selected multiple tiles in the TileMap or using the Selection "
"tool, you can place them in a repeating pattern within the rectangle."
msgstr ""

#: ../../docs/tutorials/2d/using_tilemaps.rst:269
msgid ""
"You can toggle this mode temporarily while in Paint or Eraser mode by "
"holding :kbd:`Ctrl` and :kbd:`Shift` then drawing."
msgstr ""

#: ../../docs/tutorials/2d/using_tilemaps.rst:273
msgid "Bucket Fill"
msgstr ""

#: ../../docs/tutorials/2d/using_tilemaps.rst:275
msgid ""
"After selecting Bucket Fill mode, you can choose whether painting should be "
"limited to contiguous areas only by toggling the **Contiguous** checkbox "
"that appears on the right of the toolbar."
msgstr ""

#: ../../docs/tutorials/2d/using_tilemaps.rst:279
msgid ""
"If you enable **Contiguous** (the default), only matching tiles that touch "
"the current selection will be replaced. This contiguous check is performed "
"horizontally and vertically, but *not* diagonally."
msgstr ""

#: ../../docs/tutorials/2d/using_tilemaps.rst:283
msgid ""
"If you disable **Contiguous**, all tiles with the same ID in the entire "
"TileMap will be replaced by the currently selected tile. If selecting an "
"empty tile with **Contiguous** unchecked, all tiles in the rectangle that "
"encompasses the TileMap's effective area will be replaced instead."
msgstr ""

#: ../../docs/tutorials/2d/using_tilemaps.rst:288
msgid ""
"If you right-click while in Bucket Fill mode, you will replace matching "
"tiles with empty tiles."
msgstr ""

#: ../../docs/tutorials/2d/using_tilemaps.rst:291
msgid ""
"If you have selected multiple tiles in the TileMap or using the Selection "
"tool, you can place them in a repeating pattern within the filled area."
msgstr ""

#: ../../docs/tutorials/2d/using_tilemaps.rst:298
#, fuzzy
msgid "Using the Bucket Fill tool"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/2d/using_tilemaps.rst:303
msgid ""
"After selecting Picker mode, you can pick existing tiles in the 2D editor by "
"holding :kbd:`Ctrl` then clicking on a tile. This will switch the currently "
"painted tile to the tile you've just clicked. You can also pick multiple "
"tiles at once by holding down the left mouse button and forming a rectangle "
"selection. Only non-empty tiles can be picked."
msgstr ""

#: ../../docs/tutorials/2d/using_tilemaps.rst:309
msgid ""
"You can toggle this mode temporarily while in Paint mode by holding :kbd:"
"`Ctrl` then clicking or dragging the mouse."
msgstr ""

#: ../../docs/tutorials/2d/using_tilemaps.rst:315
msgid ""
"This mode is combined with any other painting mode (Paint, Line, Rectangle, "
"Bucket Fill). When eraser mode is enabled, tiles will be replaced by empty "
"tiles instead of drawing new lines when left-clicking."
msgstr ""

#: ../../docs/tutorials/2d/using_tilemaps.rst:319
msgid ""
"You can toggle this mode temporarily while in any other mode by right-"
"clicking instead of left-clicking."
msgstr ""

#: ../../docs/tutorials/2d/using_tilemaps.rst:323
#, fuzzy
msgid "Painting randomly using scattering"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/2d/using_tilemaps.rst:325
msgid ""
"While painting, you can optionally enable *randomization*. When enabled, a "
"random tile will be chosen between all the currently selected tiles when "
"painting. This is supported with the Paint, Line, Rectangle and Bucket Fill "
"tools. For effective paint randomization, you must select multiple tiles in "
"the TileMap editor or use scattering (both approaches can be combined)."
msgstr ""

#: ../../docs/tutorials/2d/using_tilemaps.rst:331
msgid ""
"If **Scattering** is set to a value greater than 0, there is a chance that "
"no tile will be placed when painting. This can be used to add occasional, "
"non-repeating detail to large areas (such as adding grass or crumbs on a "
"large top-down TileMap)."
msgstr ""

#: ../../docs/tutorials/2d/using_tilemaps.rst:336
msgid "Example when using Paint mode:"
msgstr ""

#: ../../docs/tutorials/2d/using_tilemaps.rst:342
msgid ""
"Selecting from several times to randomly choose, then painting by holding "
"down the left mouse button"
msgstr ""

#: ../../docs/tutorials/2d/using_tilemaps.rst:344
msgid "Example when using Bucket Fill mode:"
msgstr ""

#: ../../docs/tutorials/2d/using_tilemaps.rst:350
msgid ""
"Using Bucket Fill tool with a single tile, but with randomization and "
"scattering enabled"
msgstr ""

#: ../../docs/tutorials/2d/using_tilemaps.rst:354
msgid ""
"Eraser mode does not take randomization and scattering into account. All "
"tiles within the selection are always removed."
msgstr ""

#: ../../docs/tutorials/2d/using_tilemaps.rst:358
msgid "Saving and loading premade tile placements using patterns"
msgstr ""

#: ../../docs/tutorials/2d/using_tilemaps.rst:360
msgid ""
"While you can copy and paste tiles while in Select mode, you may wish to "
"save premade *patterns* of tiles to place together in a go. This can be done "
"on a per-TileMap basis by choosing the **Patterns** tab of the TileMap "
"editor."
msgstr ""

#: ../../docs/tutorials/2d/using_tilemaps.rst:364
msgid ""
"To create a new pattern, switch to Select mode, perform a selection and "
"press :kbd:`Ctrl + C`. Click on empty space within the Patterns tab (a blue "
"focus rectangle should appear around the empty space), then press :kbd:`Ctrl "
"+ V`:"
msgstr ""

#: ../../docs/tutorials/2d/using_tilemaps.rst:372
msgid "Creating a new pattern from a selection in the TileMap editor"
msgstr ""

#: ../../docs/tutorials/2d/using_tilemaps.rst:374
msgid ""
"To use an existing pattern, click its image in the **Patterns** tab, switch "
"to any painting mode, then left-click somewhere in the 2D editor:"
msgstr ""

#: ../../docs/tutorials/2d/using_tilemaps.rst:381
msgid "Placing an existing pattern using the TileMap editor"
msgstr ""

#: ../../docs/tutorials/2d/using_tilemaps.rst:383
msgid ""
"Like multi-tile selections, patterns will be repeated if used with the Line, "
"Rectangle or Bucket Fill painting modes."
msgstr ""

#: ../../docs/tutorials/2d/using_tilemaps.rst:388
msgid ""
"Despite being edited in the TileMap editor, patterns are stored in the "
"TileSet resource. This allows reusing patterns in different TileMap nodes "
"after loading a TileSet resource saved to an external file."
msgstr ""

#: ../../docs/tutorials/2d/using_tilemaps.rst:393
msgid "Handling tile connections automatically using terrains"
msgstr ""

#: ../../docs/tutorials/2d/using_tilemaps.rst:395
msgid ""
"To use terrains, the TileMap node must feature at least one terrain set and "
"a terrain within this terrain set. See :ref:"
"`doc_using_tilesets_creating_terrain_sets` if you haven't created a terrain "
"set for the TileSet yet."
msgstr ""

#: ../../docs/tutorials/2d/using_tilemaps.rst:400
#, fuzzy
msgid "There are 3 kinds of painting modes available for terrain connections:"
msgstr "Ne postoje ograničenja prilikom korištenja Godot-a"

#: ../../docs/tutorials/2d/using_tilemaps.rst:402
msgid ""
"**Connect**, where tiles are connected to surrounding tiles on the same "
"TileMap layer."
msgstr ""

#: ../../docs/tutorials/2d/using_tilemaps.rst:404
msgid ""
"**Path**, where tiles are connected to tiles painted in the same stroke "
"(until the mouse button is released)."
msgstr ""

#: ../../docs/tutorials/2d/using_tilemaps.rst:406
msgid ""
"Tile-specific overrides to resolve conflicts or handle situations not "
"covered by the terrain system."
msgstr ""

#: ../../docs/tutorials/2d/using_tilemaps.rst:409
msgid ""
"The Connect mode is easier to use, but Path is more flexible as it allows "
"for more artist control during painting. For instance, Path can allow roads "
"to be directly adjacent to each other without being connected to each other, "
"while Connect will force both roads to be connected."
msgstr ""

#: ../../docs/tutorials/2d/using_tilemaps.rst:418
msgid "Selecting Connect mode in the TileMap editor's Terrains tab"
msgstr ""

#: ../../docs/tutorials/2d/using_tilemaps.rst:424
msgid "Selecting Path mode in the TileMap editor's Terrains tab"
msgstr ""

#: ../../docs/tutorials/2d/using_tilemaps.rst:426
msgid ""
"Lastly, you can select specific tiles from the terrain to resolve conflicts "
"in certain situations:"
msgstr ""

#: ../../docs/tutorials/2d/using_tilemaps.rst:433
msgid "Painting with specific tiles in the TileMap editor's Terrains tab"
msgstr ""

#: ../../docs/tutorials/2d/using_tilemaps.rst:435
msgid ""
"Any tile that has at least one of its bits set to a value set to the "
"corresponding terrain ID will appear in the list of tiles to choose from."
msgstr ""

#: ../../docs/tutorials/2d/using_tilemaps.rst:439
msgid "Handling missing tiles"
msgstr ""

#: ../../docs/tutorials/2d/using_tilemaps.rst:441
msgid ""
"If you remove tiles in the TileSet that are referenced in a TileMap, the "
"TileMap will display a placeholder to indicate that an invalid tile ID is "
"placed:"
msgstr ""

#: ../../docs/tutorials/2d/using_tilemaps.rst:448
msgid ""
"Missing tiles in the TileMap editor due to the TileSet reference being broken"
msgstr ""

#: ../../docs/tutorials/2d/using_tilemaps.rst:450
msgid ""
"These placeholders are **not** visible in the running project, but the tile "
"data is still persisted to disk. This allows you to safely close and reopen "
"such scenes. Once you re-add a tile with the matching ID, the tiles will "
"appear with the new tile's appearance."
msgstr ""

#: ../../docs/tutorials/2d/using_tilemaps.rst:457
msgid ""
"Missing tile placeholders may not be visible until you select the TileMap "
"node and open the TileMap editor."
msgstr ""

#: ../../docs/tutorials/3d/introduction_to_3d.rst:4
msgid "Introduction to 3D"
msgstr ""

#: ../../docs/tutorials/3d/introduction_to_3d.rst:6
msgid ""
"Creating a 3D game can be challenging. That extra Z coordinate makes many of "
"the common techniques that helped to make 2D games simpler no longer work. "
"To aid in this transition, it is worth mentioning that Godot uses similar "
"APIs for 2D and 3D. Most nodes are the same and are present in both 2D and "
"3D versions. In fact, it is worth checking the 3D platformer tutorial, or "
"the 3D kinematic character tutorials, which are almost identical to their 2D "
"counterparts."
msgstr ""

#: ../../docs/tutorials/3d/introduction_to_3d.rst:14
msgid ""
"In 3D, math is a little more complex than in 2D, so also checking the :ref:"
"`doc_vector_math` entry in the wiki (which was especially created for game "
"developers, not mathematicians or engineers) will help pave the way for you "
"to develop 3D games efficiently."
msgstr ""

#: ../../docs/tutorials/3d/introduction_to_3d.rst:20
msgid "Node3D node"
msgstr ""

#: ../../docs/tutorials/3d/introduction_to_3d.rst:22
msgid ""
":ref:`Node2D <class_Node2D>` is the base node for 2D. :ref:`Control "
"<class_Control>` is the base node for everything GUI. Following this "
"reasoning, the 3D engine uses the :ref:`Node3D <class_Node3D>` node for "
"everything 3D."
msgstr ""

#: ../../docs/tutorials/3d/introduction_to_3d.rst:27
msgid ""
"Be aware that \"Spatial\" Nodes are now called \"Node3D\" starting with "
"Godot 4. Any Godot 3.x references to \"Spatial\" Nodes refer to \"Node3D\" "
"in Godot 4."
msgstr ""

#: ../../docs/tutorials/3d/introduction_to_3d.rst:33
msgid ""
"Node3Ds have a local transform, which is relative to the parent node (as "
"long as the parent node is also of **or inherits from** the type Node3D). "
"This transform can be accessed as a 4×3 :ref:`Transform3D "
"<class_Transform3D>`, or as 3 :ref:`Vector3 <class_Vector3>` members "
"representing location, Euler rotation (X, Y and Z angles) and scale."
msgstr ""

#: ../../docs/tutorials/3d/introduction_to_3d.rst:43
msgid "3D content"
msgstr ""

#: ../../docs/tutorials/3d/introduction_to_3d.rst:45
msgid ""
"Unlike 2D, where loading image content and drawing is straightforward, 3D is "
"a little more difficult. The content needs to be created with special 3D "
"tools (also called Digital Content Creation tools, or DCCs) and exported to "
"an exchange file format to be imported in Godot. This is required since 3D "
"formats are not as standardized as images."
msgstr ""

#: ../../docs/tutorials/3d/introduction_to_3d.rst:52
msgid "Manually authored models (using 3D modeling software)"
msgstr ""

#: ../../docs/tutorials/3d/introduction_to_3d.rst:57
msgid ""
"There are two pipelines to import 3D models in Godot. The first and most "
"common one is by :ref:`doc_importing_3d_scenes`, which allows you to import "
"entire scenes (exactly as they look in the 3D modeling software), including "
"animation, skeletal rigs, blend shapes, etc."
msgstr ""

#: ../../docs/tutorials/3d/introduction_to_3d.rst:62
msgid ""
"The second pipeline is by importing simple .OBJ files as mesh resources, "
"which can be then put inside a :ref:`MeshInstance3D <class_MeshInstance3D>` "
"node for display."
msgstr ""

#: ../../docs/tutorials/3d/introduction_to_3d.rst:67
msgid "Generated geometry"
msgstr ""

#: ../../docs/tutorials/3d/introduction_to_3d.rst:69
msgid ""
"It is possible to create custom geometry by using the :ref:`ArrayMesh "
"<class_ArrayMesh>` resource directly. Simply create your arrays and use the :"
"ref:`ArrayMesh.add_surface_from_arrays() "
"<class_ArrayMesh_method_add_surface_from_arrays>` function. A helper class "
"is also available, :ref:`SurfaceTool <class_SurfaceTool>`, which provides a "
"more straightforward API and helpers for indexing, generating normals, "
"tangents, etc."
msgstr ""

#: ../../docs/tutorials/3d/introduction_to_3d.rst:76
msgid ""
"In any case, this method is meant for generating static geometry (models "
"that will not be updated often), as creating vertex arrays and submitting "
"them to the 3D API has a significant performance cost."
msgstr ""

#: ../../docs/tutorials/3d/introduction_to_3d.rst:81
msgid "Immediate geometry"
msgstr ""

#: ../../docs/tutorials/3d/introduction_to_3d.rst:83
msgid ""
"If, instead, you need to generate simple geometry that will be updated "
"often, Godot provides a special :ref:`ImmediateMesh <class_ImmediateMesh>` "
"resource that can be used in a :ref:`MeshInstance3D <class_MeshInstance3D>` "
"node. This provides an OpenGL 1.x-style immediate-mode API to create points, "
"lines, triangles, etc."
msgstr ""

#: ../../docs/tutorials/3d/introduction_to_3d.rst:90
msgid "2D in 3D"
msgstr ""

#: ../../docs/tutorials/3d/introduction_to_3d.rst:92
msgid ""
"While Godot packs a powerful 2D engine, many types of games use 2D in a 3D "
"environment. By using a fixed camera (either orthogonal or perspective) that "
"does not rotate, nodes such as :ref:`Sprite3D <class_Sprite3D>` and :ref:"
"`AnimatedSprite3D <class_AnimatedSprite3D>` can be used to create 2D games "
"that take advantage of mixing with 3D backgrounds, more realistic parallax, "
"lighting/shadow effects, etc."
msgstr ""

#: ../../docs/tutorials/3d/introduction_to_3d.rst:100
msgid ""
"The disadvantage is, of course, that added complexity and reduced "
"performance in comparison to plain 2D, as well as the lack of reference of "
"working in pixels."
msgstr ""

#: ../../docs/tutorials/3d/introduction_to_3d.rst:105
#: ../../docs/tutorials/3d/environment_and_post_processing.rst:20
msgid "Environment"
msgstr ""

#: ../../docs/tutorials/3d/introduction_to_3d.rst:107
msgid ""
"Besides editing a scene, it is often common to edit the environment. Godot "
"provides a :ref:`WorldEnvironment <class_WorldEnvironment>` node that allows "
"changing the background color, mode (as in, put a skybox), and applying "
"several types of built-in post-processing effects. Environments can also be "
"overridden in the Camera."
msgstr ""

#: ../../docs/tutorials/3d/introduction_to_3d.rst:114
msgid "3D viewport"
msgstr ""

#: ../../docs/tutorials/3d/introduction_to_3d.rst:116
msgid ""
"Editing 3D scenes is done in the 3D tab. This tab can be selected manually, "
"but it will be automatically enabled when a Node3D node is selected."
msgstr ""

#: ../../docs/tutorials/3d/introduction_to_3d.rst:122
msgid ""
"Default 3D scene navigation controls are similar to Blender (aiming to have "
"some sort of consistency in the free software pipeline..), but options are "
"included to customize mouse buttons and behavior to be similar to other "
"tools in the Editor Settings:"
msgstr ""

#: ../../docs/tutorials/3d/introduction_to_3d.rst:130
msgid "Coordinate system"
msgstr ""

#: ../../docs/tutorials/3d/introduction_to_3d.rst:132
msgid ""
"Godot uses the `metric <https://en.wikipedia.org/wiki/Metric_system>`__ "
"system for everything in 3D, with 1 unit being equal to 1 meter. Physics and "
"other areas are tuned for this scale. Therefore, attempting to use a "
"different scale is usually a bad idea (unless you know what you are doing)."
msgstr ""

#: ../../docs/tutorials/3d/introduction_to_3d.rst:137
msgid ""
"When working with 3D assets, it's always best to work in the correct scale "
"(set the unit to metric in your 3D modeling software). Godot allows scaling "
"post-import and, while this works in most cases, in rare situations it may "
"introduce floating-point precision issues (and thus, glitches or artifacts) "
"in delicate areas such as rendering or physics. Make sure your artists "
"always work in the right scale!"
msgstr ""

#: ../../docs/tutorials/3d/introduction_to_3d.rst:144
msgid ""
"The Y coordinate is used for \"up\". As for the horizontal X/Z axes, Godot "
"uses a **right-handed** coordinate system. This means that for most objects "
"that need alignment (such as lights or cameras), the Z axis is used as a "
"\"pointing towards\" direction. This convention roughly means that:"
msgstr ""

#: ../../docs/tutorials/3d/introduction_to_3d.rst:149
msgid "**X** is sides"
msgstr ""

#: ../../docs/tutorials/3d/introduction_to_3d.rst:150
msgid "**Y** is up/down"
msgstr ""

#: ../../docs/tutorials/3d/introduction_to_3d.rst:151
msgid "**Z** is front/back"
msgstr ""

#: ../../docs/tutorials/3d/introduction_to_3d.rst:153
msgid "See this chart for comparison with other 3D software:"
msgstr ""

#: ../../docs/tutorials/3d/introduction_to_3d.rst:159
msgid "3D coordinate systems comparison chart"
msgstr ""

#: ../../docs/tutorials/3d/introduction_to_3d.rst:159
msgid "Image by `Freya Holmér <https://twitter.com/FreyaHolmer>`__"
msgstr ""

#: ../../docs/tutorials/3d/introduction_to_3d.rst:162
msgid "Space and manipulation gizmos"
msgstr ""

#: ../../docs/tutorials/3d/introduction_to_3d.rst:164
msgid ""
"Moving objects in the 3D view is done through the manipulator gizmos. Each "
"axis is represented by a color: Red, Green, Blue represent X, Y, Z "
"respectively. This convention applies to the grid and other gizmos too (and "
"also to the shader language, ordering of components for Vector3, Color, "
"etc.)."
msgstr ""

#: ../../docs/tutorials/3d/introduction_to_3d.rst:172
msgid "Some useful keybindings:"
msgstr ""

#: ../../docs/tutorials/3d/introduction_to_3d.rst:174
msgid ""
"To snap placement or rotation, press :kbd:`Ctrl` while moving, scaling or "
"rotating."
msgstr ""

#: ../../docs/tutorials/3d/introduction_to_3d.rst:176
msgid "To center the view on the selected object, press :kbd:`F`."
msgstr ""

#: ../../docs/tutorials/3d/introduction_to_3d.rst:179
msgid "Using Blender-style transform shortcuts"
msgstr ""

#: ../../docs/tutorials/3d/introduction_to_3d.rst:181
msgid ""
"Since Godot 4.2, you can enable Blender-style shortcuts for translating, "
"rotating and scaling nodes. In Blender, these shortcuts are:"
msgstr ""

#: ../../docs/tutorials/3d/introduction_to_3d.rst:184
msgid ":kbd:`G` for translating"
msgstr ""

#: ../../docs/tutorials/3d/introduction_to_3d.rst:185
msgid ":kbd:`R` for rotating"
msgstr ""

#: ../../docs/tutorials/3d/introduction_to_3d.rst:186
msgid ":kbd:`S` for scaling"
msgstr ""

#: ../../docs/tutorials/3d/introduction_to_3d.rst:188
msgid ""
"After pressing a shortcut key while focusing on the 3D editor viewport, move "
"the mouse or enter a number to move the selected node(s) by the specified "
"amount in 3D units. You can constrain movement to a specific axis by "
"specifying the axis as a letter, then the distance (if entering a value with "
"the keyboard)."
msgstr ""

#: ../../docs/tutorials/3d/introduction_to_3d.rst:194
msgid ""
"For instance, to move the selection upwards by 2.5 units, enter the "
"following sequence in order (Y+ is upwards in Godot):"
msgstr ""

#: ../../docs/tutorials/3d/introduction_to_3d.rst:197
msgid ":kbd:`G`-:kbd:`Y`-:kbd:`2`-:kbd:`.`-:kbd:`5`-:kbd:`Enter`"
msgstr ""

#: ../../docs/tutorials/3d/introduction_to_3d.rst:199
msgid ""
"To use Blender-style transform shortcuts in Godot, go to the Editor "
"Settings' **Shortcuts** tab, then in the Spatial Editor section:"
msgstr ""

#: ../../docs/tutorials/3d/introduction_to_3d.rst:202
msgid "Bind **Begin Translate Transformation** to :kbd:`G`."
msgstr ""

#: ../../docs/tutorials/3d/introduction_to_3d.rst:203
msgid "Bind **Begin Rotate Transformation** to :kbd:`R`."
msgstr ""

#: ../../docs/tutorials/3d/introduction_to_3d.rst:204
msgid "Bind **Begin Scale Transformation** to :kbd:`S`."
msgstr ""

#: ../../docs/tutorials/3d/introduction_to_3d.rst:205
msgid ""
"Finally, unbind **Scale Mode** so that its shortcut won't conflict with "
"**Begin Rotate Transformation**."
msgstr ""

#: ../../docs/tutorials/3d/introduction_to_3d.rst:209
msgid "View menu"
msgstr ""

#: ../../docs/tutorials/3d/introduction_to_3d.rst:211
msgid ""
"The view options are controlled by the \"View\" menu in the viewport's "
"toolbar."
msgstr ""

#: ../../docs/tutorials/3d/introduction_to_3d.rst:215
msgid "You can hide the gizmos in the 3D view of the editor through this menu:"
msgstr ""

#: ../../docs/tutorials/3d/introduction_to_3d.rst:219
msgid ""
"To hide a specific type of gizmos, you can toggle them off in the \"View\" "
"menu."
msgstr ""

#: ../../docs/tutorials/3d/introduction_to_3d.rst:224
msgid "Default environment"
msgstr ""

#: ../../docs/tutorials/3d/introduction_to_3d.rst:226
msgid ""
"When created from the Project Manager, the 3D environment has a default sky."
msgstr ""

#: ../../docs/tutorials/3d/introduction_to_3d.rst:230
msgid ""
"Given how physically-based rendering works, it is advised to always try to "
"work with a default environment in order to provide indirect and reflected "
"light to your objects."
msgstr ""

#: ../../docs/tutorials/3d/introduction_to_3d.rst:235
msgid "Cameras"
msgstr ""

#: ../../docs/tutorials/3d/introduction_to_3d.rst:237
msgid ""
"No matter how many objects are placed in the 3D space, nothing will be "
"displayed unless a :ref:`Camera3D <class_Camera3D>` is also added to the "
"scene. Cameras can work in either orthogonal or perspective projections:"
msgstr ""

#: ../../docs/tutorials/3d/introduction_to_3d.rst:244
msgid ""
"Cameras are associated with (and only display to) a parent or grandparent "
"viewport. Since the root of the scene tree is a viewport, cameras will "
"display on it by default, but if sub-viewports (either as render target or "
"picture-in-picture) are desired, they need their own children cameras to "
"display."
msgstr ""

#: ../../docs/tutorials/3d/introduction_to_3d.rst:252
msgid ""
"When dealing with multiple cameras, the following rules are enforced for "
"each viewport:"
msgstr ""

#: ../../docs/tutorials/3d/introduction_to_3d.rst:255
msgid ""
"If no cameras are present in the scene tree, the first one that enters it "
"will become the active camera. Further cameras entering the scene will be "
"ignored (unless they are set as *current*)."
msgstr ""

#: ../../docs/tutorials/3d/introduction_to_3d.rst:258
msgid ""
"If a camera has the \"*current*\" property set, it will be used regardless "
"of any other camera in the scene. If the property is set, it will become "
"active, replacing the previous camera."
msgstr ""

#: ../../docs/tutorials/3d/introduction_to_3d.rst:261
msgid ""
"If an active camera leaves the scene tree, the first camera in tree-order "
"will take its place."
msgstr ""

#: ../../docs/tutorials/3d/introduction_to_3d.rst:265
#: ../../docs/tutorials/assets_pipeline/escn_exporter/lights.rst:2
msgid "Lights"
msgstr ""

#: ../../docs/tutorials/3d/introduction_to_3d.rst:267
msgid ""
"The background environment emits some ambient light which appears on "
"surfaces. Still, without any light sources placed in the scene, the scene "
"will appear quite dark unless the background environment is very bright."
msgstr ""

#: ../../docs/tutorials/3d/introduction_to_3d.rst:271
msgid ""
"Most outdoor scenes have a directional light (the sun or moon), while indoor "
"scenes typically have several positional lights (lamps, torches, …). See :"
"ref:`doc_lights_and_shadows` for more information on setting up lights in "
"Godot."
msgstr ""

#: ../../docs/tutorials/3d/using_transforms.rst:4
msgid "Using 3D transforms"
msgstr ""

#: ../../docs/tutorials/3d/using_transforms.rst:9
msgid ""
"If you have never made 3D games before, working with rotations in three "
"dimensions can be confusing at first. Coming from 2D, the natural way of "
"thinking is along the lines of *\"Oh, it's just like rotating in 2D, except "
"now rotations happen in X, Y and Z\"*."
msgstr ""

#: ../../docs/tutorials/3d/using_transforms.rst:12
msgid ""
"At first, this seems easy. For simple games, this way of thinking may even "
"be enough. Unfortunately, it's often incorrect."
msgstr ""

#: ../../docs/tutorials/3d/using_transforms.rst:14
msgid ""
"Angles in three dimensions are most commonly referred to as \"Euler Angles\"."
msgstr ""

#: ../../docs/tutorials/3d/using_transforms.rst:18
msgid ""
"Euler angles were introduced by mathematician Leonhard Euler in the early "
"1700s."
msgstr ""

#: ../../docs/tutorials/3d/using_transforms.rst:22
msgid ""
"This way of representing 3D rotations was groundbreaking at the time, but it "
"has several shortcomings when used in game development (which is to be "
"expected from a guy with a funny hat). The idea of this document is to "
"explain why, as well as outlining best practices for dealing with transforms "
"when programming 3D games."
msgstr ""

#: ../../docs/tutorials/3d/using_transforms.rst:28
msgid "Problems of Euler angles"
msgstr ""

#: ../../docs/tutorials/3d/using_transforms.rst:30
msgid ""
"While it may seem intuitive that each axis has a rotation, the truth is that "
"it's just not practical."
msgstr ""

#: ../../docs/tutorials/3d/using_transforms.rst:33
msgid "Axis order"
msgstr ""

#: ../../docs/tutorials/3d/using_transforms.rst:35
msgid ""
"The main reason for this is that there isn't a *unique* way to construct an "
"orientation from the angles. There isn't a standard mathematical function "
"that takes all the angles together and produces an actual 3D rotation. The "
"only way an orientation can be produced from angles is to rotate the object "
"angle by angle, in an *arbitrary order*."
msgstr ""

#: ../../docs/tutorials/3d/using_transforms.rst:39
msgid ""
"This could be done by first rotating in *X*, then *Y* and then in *Z*. "
"Alternatively, you could first rotate in *Y*, then in *Z* and finally in "
"*X*. Anything works, but depending on the order, the final orientation of "
"the object will *not necessarily be the same*. Indeed, this means that there "
"are several ways to construct an orientation from 3 different angles, "
"depending on *the order of the rotations*."
msgstr ""

#: ../../docs/tutorials/3d/using_transforms.rst:43
msgid ""
"Following is a visualization of rotation axes (in X, Y, Z order) in a gimbal "
"(from Wikipedia). As you can see, the orientation of each axis depends on "
"the rotation of the previous one:"
msgstr ""

#: ../../docs/tutorials/3d/using_transforms.rst:47
msgid ""
"You may be wondering how this affects you. Let's look at a practical example:"
msgstr ""

#: ../../docs/tutorials/3d/using_transforms.rst:49
msgid ""
"Imagine you are working on a first-person controller (e.g. an FPS game). "
"Moving the mouse left and right controls your view angle parallel to the "
"ground, while moving it up and down moves the player's view up and down."
msgstr ""

#: ../../docs/tutorials/3d/using_transforms.rst:51
msgid ""
"In this case to achieve the desired effect, rotation must be applied first "
"in the *Y* axis (\"up\" in this case, since Godot uses a \"Y-Up\" "
"orientation), followed by rotation in the *X* axis."
msgstr ""

#: ../../docs/tutorials/3d/using_transforms.rst:55
msgid ""
"If we were to apply rotation in the *X* axis first, and then in *Y*, the "
"effect would be undesired:"
msgstr ""

#: ../../docs/tutorials/3d/using_transforms.rst:59
msgid ""
"Depending on the type of game or effect desired, the order in which you want "
"axis rotations to be applied may differ. Therefore, applying rotations in X, "
"Y, and Z is not enough: you also need a *rotation order*."
msgstr ""

#: ../../docs/tutorials/3d/using_transforms.rst:62
#: ../../docs/tutorials/math/interpolation.rst:4
msgid "Interpolation"
msgstr ""

#: ../../docs/tutorials/3d/using_transforms.rst:64
msgid ""
"Another problem with using Euler angles is interpolation. Imagine you want "
"to transition between two different camera or enemy positions (including "
"rotations). One logical way to approach this is to interpolate the angles "
"from one position to the next. One would expect it to look like this:"
msgstr ""

#: ../../docs/tutorials/3d/using_transforms.rst:68
msgid "But this does not always have the expected effect when using angles:"
msgstr ""

#: ../../docs/tutorials/3d/using_transforms.rst:72
msgid "The camera actually rotated the opposite direction!"
msgstr ""

#: ../../docs/tutorials/3d/using_transforms.rst:74
msgid "There are a few reasons this may happen:"
msgstr ""

#: ../../docs/tutorials/3d/using_transforms.rst:76
msgid ""
"Rotations don't map linearly to orientation, so interpolating them does not "
"always result in the shortest path (i.e., to go from ``270`` to ``0`` "
"degrees is not the same as going from ``270`` to ``360``, even though the "
"angles are equivalent)."
msgstr ""

#: ../../docs/tutorials/3d/using_transforms.rst:77
msgid ""
"Gimbal lock is at play (first and last rotated axis align, so a degree of "
"freedom is lost). See `Wikipedia's page on Gimbal Lock <https://en.wikipedia."
"org/wiki/Gimbal_lock>`_ for a detailed explanation of this problem."
msgstr ""

#: ../../docs/tutorials/3d/using_transforms.rst:80
msgid "Say no to Euler angles"
msgstr ""

#: ../../docs/tutorials/3d/using_transforms.rst:82
msgid ""
"The result of all this is that you should **not use** the ``rotation`` "
"property of :ref:`class_Node3D` nodes in Godot for games. It's there to be "
"used mainly in the editor, for coherence with the 2D engine, and for simple "
"rotations (generally just one axis, or even two in limited cases). As much "
"as you may be tempted, don't use it."
msgstr ""

#: ../../docs/tutorials/3d/using_transforms.rst:84
msgid "Instead, there is a better way to solve your rotation problems."
msgstr ""

#: ../../docs/tutorials/3d/using_transforms.rst:87
msgid "Introducing transforms"
msgstr ""

#: ../../docs/tutorials/3d/using_transforms.rst:89
msgid ""
"Godot uses the :ref:`class_Transform3D` datatype for orientations. Each :ref:"
"`class_Node3D` node contains a ``transform`` property which is relative to "
"the parent's transform, if the parent is a Node3D-derived type."
msgstr ""

#: ../../docs/tutorials/3d/using_transforms.rst:91
msgid ""
"It is also possible to access the world coordinate transform via the "
"``global_transform`` property."
msgstr ""

#: ../../docs/tutorials/3d/using_transforms.rst:93
msgid ""
"A transform has a :ref:`class_Basis` (transform.basis sub-property), which "
"consists of three :ref:`class_Vector3` vectors. These are accessed via the "
"``transform.basis`` property and can be accessed directly by ``transform."
"basis.x``, ``transform.basis.y``, and ``transform.basis.z``. Each vector "
"points in the direction its axis has been rotated, so they effectively "
"describe the node's total rotation. The scale (as long as it's uniform) can "
"also be inferred from the length of the axes. A *basis* can also be "
"interpreted as a 3x3 matrix and used as ``transform.basis[x][y]``."
msgstr ""

#: ../../docs/tutorials/3d/using_transforms.rst:95
msgid "A default basis (unmodified) is akin to:"
msgstr ""

#: ../../docs/tutorials/3d/using_transforms.rst:123
msgid "This is also an analog of a 3x3 identity matrix."
msgstr ""

#: ../../docs/tutorials/3d/using_transforms.rst:125
msgid ""
"Following the OpenGL convention, ``X`` is the *Right* axis, ``Y`` is the "
"*Up* axis and ``Z`` is the *Forward* axis."
msgstr ""

#: ../../docs/tutorials/3d/using_transforms.rst:127
msgid ""
"Together with the *basis*, a transform also has an *origin*. This is a "
"*Vector3* specifying how far away from the actual origin ``(0, 0, 0)`` this "
"transform is. Combining the *basis* with the *origin*, a *transform* "
"efficiently represents a unique translation, rotation, and scale in space."
msgstr ""

#: ../../docs/tutorials/3d/using_transforms.rst:132
msgid ""
"One way to visualize a transform is to look at an object's 3D gizmo while in "
"\"local space\" mode."
msgstr ""

#: ../../docs/tutorials/3d/using_transforms.rst:136
msgid ""
"The gizmo's arrows show the ``X``, ``Y``, and ``Z`` axes (in red, green, and "
"blue respectively) of the basis, while the gizmo's center is at the object's "
"origin."
msgstr ""

#: ../../docs/tutorials/3d/using_transforms.rst:140
msgid ""
"For more information on the mathematics of vectors and transforms, please "
"read the :ref:`doc_vector_math` tutorials."
msgstr ""

#: ../../docs/tutorials/3d/using_transforms.rst:143
msgid "Manipulating transforms"
msgstr ""

#: ../../docs/tutorials/3d/using_transforms.rst:145
msgid ""
"Of course, transforms are not as straightforward to manipulate as angles and "
"have problems of their own."
msgstr ""

#: ../../docs/tutorials/3d/using_transforms.rst:147
msgid ""
"It is possible to rotate a transform, either by multiplying its basis by "
"another (this is called accumulation), or by using the rotation methods."
msgstr ""

#: ../../docs/tutorials/3d/using_transforms.rst:172
msgid "A method in Node3D simplifies this:"
msgstr ""

#: ../../docs/tutorials/3d/using_transforms.rst:189
msgid "This rotates the node relative to the parent node."
msgstr ""

#: ../../docs/tutorials/3d/using_transforms.rst:191
msgid ""
"To rotate relative to object space (the node's own transform), use the "
"following:"
msgstr ""

#: ../../docs/tutorials/3d/using_transforms.rst:205
msgid "Precision errors"
msgstr ""

#: ../../docs/tutorials/3d/using_transforms.rst:207
msgid ""
"Doing successive operations on transforms will result in a loss of precision "
"due to floating-point error. This means the scale of each axis may no longer "
"be exactly ``1.0``, and they may not be exactly ``90`` degrees from each "
"other."
msgstr ""

#: ../../docs/tutorials/3d/using_transforms.rst:209
msgid ""
"If a transform is rotated every frame, it will eventually start deforming "
"over time. This is unavoidable."
msgstr ""

#: ../../docs/tutorials/3d/using_transforms.rst:211
msgid ""
"There are two different ways to handle this. The first is to "
"*orthonormalize* the transform after some time (maybe once per frame if you "
"modify it every frame):"
msgstr ""

#: ../../docs/tutorials/3d/using_transforms.rst:222
msgid ""
"This will make all axes have ``1.0`` length again and be ``90`` degrees from "
"each other. However, any scale applied to the transform will be lost."
msgstr ""

#: ../../docs/tutorials/3d/using_transforms.rst:224
msgid ""
"It is recommended you not scale nodes that are going to be manipulated; "
"scale their children nodes instead (such as MeshInstance3D). If you "
"absolutely must scale the node, then re-apply it at the end:"
msgstr ""

#: ../../docs/tutorials/3d/using_transforms.rst:238
msgid "Obtaining information"
msgstr ""

#: ../../docs/tutorials/3d/using_transforms.rst:240
msgid ""
"You might be thinking at this point: **\"Ok, but how do I get angles from a "
"transform?\"**. The answer again is: you don't. You must do your best to "
"stop thinking in angles."
msgstr ""

#: ../../docs/tutorials/3d/using_transforms.rst:242
msgid ""
"Imagine you need to shoot a bullet in the direction your player is facing. "
"Just use the forward axis (commonly ``Z`` or ``-Z``)."
msgstr ""

#: ../../docs/tutorials/3d/using_transforms.rst:255
msgid ""
"Is the enemy looking at the player? Use the dot product for this (see the :"
"ref:`doc_vector_math` tutorial for an explanation of the dot product):"
msgstr ""

#: ../../docs/tutorials/3d/using_transforms.rst:274
msgid "Strafe left:"
msgstr ""

#: ../../docs/tutorials/3d/using_transforms.rst:291
msgid "Jump:"
msgstr ""

#: ../../docs/tutorials/3d/using_transforms.rst:310
msgid "All common behaviors and logic can be done with just vectors."
msgstr ""

#: ../../docs/tutorials/3d/using_transforms.rst:313
msgid "Setting information"
msgstr ""

#: ../../docs/tutorials/3d/using_transforms.rst:315
msgid ""
"There are, of course, cases where you want to set information to a "
"transform. Imagine a first person controller or orbiting camera. Those are "
"definitely done using angles, because you *do want* the transforms to happen "
"in a specific order."
msgstr ""

#: ../../docs/tutorials/3d/using_transforms.rst:317
msgid ""
"For such cases, keep the angles and rotations *outside* the transform and "
"set them every frame. Don't try to retrieve and reuse them because the "
"transform is not meant to be used this way."
msgstr ""

#: ../../docs/tutorials/3d/using_transforms.rst:319
msgid "Example of looking around, FPS style:"
msgstr ""

#: ../../docs/tutorials/3d/using_transforms.rst:361
msgid ""
"As you can see, in such cases it's even simpler to keep the rotation "
"outside, then use the transform as the *final* orientation."
msgstr ""

#: ../../docs/tutorials/3d/using_transforms.rst:364
msgid "Interpolating with quaternions"
msgstr ""

#: ../../docs/tutorials/3d/using_transforms.rst:366
msgid ""
"Interpolating between two transforms can efficiently be done with "
"quaternions. More information about how quaternions work can be found in "
"other places around the Internet. For practical use, it's enough to "
"understand that pretty much their main use is doing a closest path "
"interpolation. As in, if you have two rotations, a quaternion will smoothly "
"allow interpolation between them using the closest axis."
msgstr ""

#: ../../docs/tutorials/3d/using_transforms.rst:368
msgid "Converting a rotation to quaternion is straightforward."
msgstr ""

#: ../../docs/tutorials/3d/using_transforms.rst:391
msgid ""
"The :ref:`class_Quaternion` type reference has more information on the "
"datatype (it can also do transform accumulation, transform points, etc., "
"though this is used less often). If you interpolate or apply operations to "
"quaternions many times, keep in mind they need to be eventually normalized. "
"Otherwise, they will also suffer from numerical precision errors."
msgstr ""

#: ../../docs/tutorials/3d/using_transforms.rst:397
msgid ""
"Quaternions are useful when doing camera/path/etc. interpolations, as the "
"result will always be correct and smooth."
msgstr ""

#: ../../docs/tutorials/3d/using_transforms.rst:400
msgid "Transforms are your friend"
msgstr ""

#: ../../docs/tutorials/3d/using_transforms.rst:402
msgid ""
"For most beginners, getting used to working with transforms can take some "
"time. However, once you get used to them, you will appreciate their "
"simplicity and power."
msgstr ""

#: ../../docs/tutorials/3d/using_transforms.rst:404
msgid ""
"Don't hesitate to ask for help on this topic in any of Godot's `online "
"communities <https://godotengine.org/community>`_ and, once you become "
"confident enough, please help others!"
msgstr ""

#: ../../docs/tutorials/3d/procedural_geometry/index.rst:4
msgid "Procedural geometry"
msgstr ""

#: ../../docs/tutorials/3d/procedural_geometry/index.rst:6
msgid ""
"There are many ways to procedurally generate geometry in Godot. In this "
"tutorial series, we will explore a few of them. Each technique has its own "
"benefits and drawbacks, so it is best to understand each one and how it can "
"be useful in a given situation."
msgstr ""

#: ../../docs/tutorials/3d/procedural_geometry/index.rst:21
msgid ""
"All the procedural geometry generation methods described here run on the "
"CPU. Godot doesn't support generating geometry on the GPU yet."
msgstr ""

#: ../../docs/tutorials/3d/procedural_geometry/index.rst:25
msgid "What is geometry?"
msgstr ""

#: ../../docs/tutorials/3d/procedural_geometry/index.rst:27
msgid ""
"Geometry is a fancy way of saying shape. In computer graphics, geometry is "
"typically represented by an array of positions called \"vertices\". In "
"Godot, geometry is represented by Meshes."
msgstr ""

#: ../../docs/tutorials/3d/procedural_geometry/index.rst:31
msgid "What is a Mesh?"
msgstr ""

#: ../../docs/tutorials/3d/procedural_geometry/index.rst:33
msgid ""
"Many things in Godot have mesh in their name: the :ref:`Mesh <class_Mesh>`, "
"the :ref:`ArrayMesh <class_ArrayMesh>`, the :ref:`ImmediateMesh "
"<class_ImmediateMesh>`, the :ref:`MeshInstance3D <class_MeshInstance3D>`, "
"the :ref:`MultiMesh <class_MultiMesh>`, and the :ref:`MultiMeshInstance3D "
"<class_MultiMeshInstance3D>`. While they are all related, they have slightly "
"different uses."
msgstr ""

#: ../../docs/tutorials/3d/procedural_geometry/index.rst:40
msgid ""
"Meshes and ArrayMeshes are resources that are drawn using a MeshInstance3D "
"node. Resources like Meshes and ArrayMeshes cannot be added to the scene "
"directly. A MeshInstance3D represents one instance of a mesh in your scene. "
"You can reuse a single mesh in multiple MeshInstance3Ds to draw it in "
"different parts of your scene with different materials or transformations "
"(scale, rotation, position etc.)."
msgstr ""

#: ../../docs/tutorials/3d/procedural_geometry/index.rst:46
msgid ""
"If you are going to draw the same object many times, it can be helpful to "
"use a MultiMesh with a MultiMeshInstance3D. MultiMeshInstance3Ds draw meshes "
"thousands of times very cheaply by taking advantage of hardware instancing. "
"The drawback with using a MultiMeshInstance3D is that each of your mesh's "
"surfaces are limited to one material for all instances. It uses an instance "
"array to store different colors and transformations for each instance, but "
"all the instances of each surface use the same material."
msgstr ""

#: ../../docs/tutorials/3d/procedural_geometry/index.rst:54
msgid "What a Mesh is"
msgstr ""

#: ../../docs/tutorials/3d/procedural_geometry/index.rst:56
msgid ""
"A Mesh is composed of one or more surfaces. A surface is an array composed "
"of multiple sub-arrays containing vertices, normals, UVs, etc. Normally the "
"process of constructing surfaces and meshes is hidden from the user in the :"
"ref:`RenderingServer <class_RenderingServer>`, but with ArrayMeshes, the "
"user can construct a Mesh manually by passing in an array containing the "
"surface information."
msgstr ""

#: ../../docs/tutorials/3d/procedural_geometry/index.rst:62
msgid "Surfaces"
msgstr ""

#: ../../docs/tutorials/3d/procedural_geometry/index.rst:64
msgid ""
"Each surface has its own material. Alternatively, you can override the "
"material for all surfaces in the Mesh when you use a MeshInstance3D using "
"the :ref:`material_override "
"<class_GeometryInstance3D_property_material_override>` property."
msgstr ""

#: ../../docs/tutorials/3d/procedural_geometry/index.rst:68
msgid "Surface array"
msgstr ""

#: ../../docs/tutorials/3d/procedural_geometry/index.rst:70
msgid ""
"The surface array is an array of length ``ArrayMesh.ARRAY_MAX``. Each "
"position in the array is filled with a sub-array containing per-vertex "
"information. For example, the array located at ``ArrayMesh.ARRAY_NORMAL`` is "
"a :ref:`PackedVector3Array <class_PackedVector3Array>` of vertex normals. "
"See :ref:`Mesh.ArrayType <enum_Mesh_ArrayType>` for more information."
msgstr ""

#: ../../docs/tutorials/3d/procedural_geometry/index.rst:75
msgid ""
"The surface array can be indexed or non-indexed. Creating a non-indexed "
"array is as easy as not assigning an array at the index ``ArrayMesh."
"ARRAY_INDEX``. A non-indexed array stores unique vertex information for "
"every triangle, meaning that when two triangles share a vertex, the vertex "
"is duplicated in the array. An indexed surface array only stores vertex "
"information for each unique vertex and then also stores an array of indices "
"which maps out how to construct the triangles from the vertex array. In "
"general, using an indexed array is faster, but it means you have to share "
"vertex data between triangles, which is not always desired (e.g. when you "
"want per-face normals)."
msgstr ""

#: ../../docs/tutorials/3d/procedural_geometry/index.rst:86
msgid ""
"Godot provides different ways of accessing and working with geometry. More "
"information on each will be provided in the following tutorials."
msgstr ""

#: ../../docs/tutorials/3d/procedural_geometry/index.rst:90
#: ../../docs/contributing/development/file_formats/tscn.rst:324
msgid "ArrayMesh"
msgstr ""

#: ../../docs/tutorials/3d/procedural_geometry/index.rst:92
msgid ""
"The ArrayMesh resource extends Mesh to add a few different quality of life "
"functions and, most importantly, the ability to construct a Mesh surface "
"through scripting."
msgstr ""

#: ../../docs/tutorials/3d/procedural_geometry/index.rst:95
msgid ""
"For more information about the ArrayMesh, please see the :ref:`ArrayMesh "
"tutorial <doc_arraymesh>`."
msgstr ""

#: ../../docs/tutorials/3d/procedural_geometry/index.rst:98
msgid "MeshDataTool"
msgstr ""

#: ../../docs/tutorials/3d/procedural_geometry/index.rst:100
msgid ""
"The MeshDataTool is a resource that converts Mesh data into arrays of "
"vertices, faces, and edges that can be modified at runtime."
msgstr ""

#: ../../docs/tutorials/3d/procedural_geometry/index.rst:103
msgid ""
"For more information about the MeshDataTool, please see the :ref:"
"`MeshDataTool tutorial <doc_meshdatatool>`."
msgstr ""

#: ../../docs/tutorials/3d/procedural_geometry/index.rst:106
msgid "SurfaceTool"
msgstr ""

#: ../../docs/tutorials/3d/procedural_geometry/index.rst:108
msgid ""
"The SurfaceTool allows the creation of Meshes using an OpenGL 1.x immediate "
"mode style interface."
msgstr ""

#: ../../docs/tutorials/3d/procedural_geometry/index.rst:110
msgid ""
"For more information about the SurfaceTool, please see the :ref:`SurfaceTool "
"tutorial <doc_surfacetool>`."
msgstr ""

#: ../../docs/tutorials/3d/procedural_geometry/index.rst:113
msgid "ImmediateMesh"
msgstr ""

#: ../../docs/tutorials/3d/procedural_geometry/index.rst:115
msgid ""
"ImmediateMesh is a mesh that uses an immediate mode style interface (like "
"SurfaceTool) to draw objects. The difference between ImmediateMesh and the "
"SurfaceTool is that ImmediateMesh is drawn directly with code dynamically, "
"while the SurfaceTool is used to generate a Mesh that you can do whatever "
"you want with."
msgstr ""

#: ../../docs/tutorials/3d/procedural_geometry/index.rst:121
msgid ""
"ImmediateMesh is useful for prototyping because of its straightforward API, "
"but it is slow because the geometry is rebuilt each time you make a change. "
"It is most useful for adding simple geometry for visual debugging (e.g. by "
"drawing lines to visualize physics raycasts etc.)."
msgstr ""

#: ../../docs/tutorials/3d/procedural_geometry/index.rst:126
msgid ""
"For more information about ImmediateMesh, please see the :ref:`ImmediateMesh "
"tutorial <doc_immediatemesh>`."
msgstr ""

#: ../../docs/tutorials/3d/procedural_geometry/index.rst:129
msgid "Which one should I use?"
msgstr ""

#: ../../docs/tutorials/3d/procedural_geometry/index.rst:131
msgid ""
"Which approach you use depends on what you are trying to do and what kind of "
"procedure you are comfortable with."
msgstr ""

#: ../../docs/tutorials/3d/procedural_geometry/index.rst:133
msgid ""
"Both SurfaceTool and ArrayMesh are excellent for generating static geometry "
"(meshes) that don't change over time."
msgstr ""

#: ../../docs/tutorials/3d/procedural_geometry/index.rst:135
msgid ""
"Using an ArrayMesh is slightly faster than using a SurfaceTool, but the API "
"is a little more challenging. Additionally, SurfaceTool has a few quality of "
"life methods such as ``generate_normals()`` and ``index()``."
msgstr ""

#: ../../docs/tutorials/3d/procedural_geometry/index.rst:138
msgid ""
"ImmediateMesh is more limited than both ArrayMesh and SurfaceTool. However, "
"if you need the geometry to change every frame anyway, it provides a much "
"easier interface that can be slightly faster than generating an ArrayMesh "
"every frame."
msgstr ""

#: ../../docs/tutorials/3d/procedural_geometry/index.rst:142
msgid ""
"The MeshDataTool is not fast, but it gives you access to all kinds of "
"properties of the mesh that you don't get with the others (edges, faces, "
"etc.). It is incredibly useful when you need that sort of data to transform "
"the mesh, but it is not a good idea to use it if that extra information is "
"not needed. The MeshDataTool is best used if you are going to be using an "
"algorithm that requires access to the face or edge array."
msgstr ""

#: ../../docs/tutorials/3d/procedural_geometry/arraymesh.rst:4
msgid "Using the ArrayMesh"
msgstr ""

#: ../../docs/tutorials/3d/procedural_geometry/arraymesh.rst:6
msgid ""
"This tutorial will present the basics of using an :ref:`ArrayMesh "
"<class_arraymesh>`."
msgstr ""

#: ../../docs/tutorials/3d/procedural_geometry/arraymesh.rst:8
msgid ""
"To do so, we will use the function :ref:`add_surface_from_arrays() "
"<class_ArrayMesh_method_add_surface_from_arrays>`, which takes up to five "
"parameters. The first two are required, while the last three are optional."
msgstr ""

#: ../../docs/tutorials/3d/procedural_geometry/arraymesh.rst:11
msgid ""
"The first parameter is the ``PrimitiveType``, an OpenGL concept that "
"instructs the GPU how to arrange the primitive based on the vertices given, "
"i.e. whether they represent triangles, lines, points, etc. See :ref:`Mesh."
"PrimitiveType <enum_Mesh_PrimitiveType>` for the options available."
msgstr ""

#: ../../docs/tutorials/3d/procedural_geometry/arraymesh.rst:15
msgid ""
"The second parameter, ``arrays``, is the actual Array that stores the mesh "
"information. The array is a normal Godot array that is constructed with "
"empty brackets ``[]``. It stores a ``Packed**Array`` (e.g. "
"PackedVector3Array, PackedInt32Array, etc.) for each type of information "
"that will be used to build the surface."
msgstr ""

#: ../../docs/tutorials/3d/procedural_geometry/arraymesh.rst:19
msgid ""
"Common elements of ``arrays`` are listed below, together with the position "
"they must have within ``arrays``. See :ref:`Mesh.ArrayType "
"<enum_Mesh_ArrayType>` for a full list."
msgstr ""

#: ../../docs/tutorials/3d/procedural_geometry/arraymesh.rst:29
msgid "Index"
msgstr ""

#: ../../docs/tutorials/3d/procedural_geometry/arraymesh.rst:30
msgid "Mesh.ArrayType Enum"
msgstr ""

#: ../../docs/tutorials/3d/procedural_geometry/arraymesh.rst:31
msgid "Array type"
msgstr ""

#: ../../docs/tutorials/3d/procedural_geometry/arraymesh.rst:33
#: ../../docs/tutorials/io/binary_serialization_api.rst:45
#: ../../docs/tutorials/xr/xr_action_map.rst:125
msgid "0"
msgstr ""

#: ../../docs/tutorials/3d/procedural_geometry/arraymesh.rst:34
msgid "``ARRAY_VERTEX``"
msgstr ""

#: ../../docs/tutorials/3d/procedural_geometry/arraymesh.rst:35
msgid ""
":ref:`PackedVector3Array <class_PackedVector3Array>` or :ref:"
"`PackedVector2Array <class_PackedVector2Array>`"
msgstr ""

#: ../../docs/tutorials/3d/procedural_geometry/arraymesh.rst:37
#: ../../docs/tutorials/io/binary_serialization_api.rst:47
#: ../../docs/tutorials/io/binary_serialization_api.rst:494
#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:683
#: ../../docs/tutorials/xr/xr_action_map.rst:116
#: ../../docs/tutorials/xr/xr_action_map.rst:188
msgid "1"
msgstr ""

#: ../../docs/tutorials/3d/procedural_geometry/arraymesh.rst:38
msgid "``ARRAY_NORMAL``"
msgstr ""

#: ../../docs/tutorials/3d/procedural_geometry/arraymesh.rst:39
#, fuzzy
msgid ":ref:`PackedVector3Array <class_PackedVector3Array>`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/3d/procedural_geometry/arraymesh.rst:41
#: ../../docs/tutorials/io/binary_serialization_api.rst:49
#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:440
#: ../../docs/tutorials/xr/xr_action_map.rst:120
#: ../../docs/tutorials/xr/xr_action_map.rst:192
msgid "2"
msgstr ""

#: ../../docs/tutorials/3d/procedural_geometry/arraymesh.rst:42
msgid "``ARRAY_TANGENT``"
msgstr ""

#: ../../docs/tutorials/3d/procedural_geometry/arraymesh.rst:43
msgid ""
":ref:`PackedFloat32Array <class_PackedFloat32Array>` or :ref:"
"`PackedFloat64Array <class_PackedFloat64Array>` of groups of 4 floats. The "
"first 3 floats determine the tangent, and the last float the binormal "
"direction as -1 or 1."
msgstr ""

#: ../../docs/tutorials/3d/procedural_geometry/arraymesh.rst:46
#: ../../docs/tutorials/io/binary_serialization_api.rst:51
#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:442
#: ../../docs/tutorials/xr/xr_action_map.rst:124
#: ../../docs/tutorials/xr/xr_action_map.rst:196
msgid "3"
msgstr ""

#: ../../docs/tutorials/3d/procedural_geometry/arraymesh.rst:47
msgid "``ARRAY_COLOR``"
msgstr ""

#: ../../docs/tutorials/3d/procedural_geometry/arraymesh.rst:48
#, fuzzy
msgid ":ref:`PackedColorArray <class_PackedColorArray>`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/3d/procedural_geometry/arraymesh.rst:50
#: ../../docs/tutorials/io/binary_serialization_api.rst:53
#: ../../docs/tutorials/io/binary_serialization_api.rst:122
#: ../../docs/tutorials/io/binary_serialization_api.rst:133
#: ../../docs/tutorials/io/binary_serialization_api.rst:142
#: ../../docs/tutorials/io/binary_serialization_api.rst:153
#: ../../docs/tutorials/io/binary_serialization_api.rst:162
#: ../../docs/tutorials/io/binary_serialization_api.rst:171
#: ../../docs/tutorials/io/binary_serialization_api.rst:184
#: ../../docs/tutorials/io/binary_serialization_api.rst:186
#: ../../docs/tutorials/io/binary_serialization_api.rst:195
#: ../../docs/tutorials/io/binary_serialization_api.rst:197
#: ../../docs/tutorials/io/binary_serialization_api.rst:199
#: ../../docs/tutorials/io/binary_serialization_api.rst:201
#: ../../docs/tutorials/io/binary_serialization_api.rst:210
#: ../../docs/tutorials/io/binary_serialization_api.rst:212
#: ../../docs/tutorials/io/binary_serialization_api.rst:214
#: ../../docs/tutorials/io/binary_serialization_api.rst:223
#: ../../docs/tutorials/io/binary_serialization_api.rst:225
#: ../../docs/tutorials/io/binary_serialization_api.rst:227
#: ../../docs/tutorials/io/binary_serialization_api.rst:229
#: ../../docs/tutorials/io/binary_serialization_api.rst:231
#: ../../docs/tutorials/io/binary_serialization_api.rst:233
#: ../../docs/tutorials/io/binary_serialization_api.rst:242
#: ../../docs/tutorials/io/binary_serialization_api.rst:244
#: ../../docs/tutorials/io/binary_serialization_api.rst:246
#: ../../docs/tutorials/io/binary_serialization_api.rst:248
#: ../../docs/tutorials/io/binary_serialization_api.rst:257
#: ../../docs/tutorials/io/binary_serialization_api.rst:259
#: ../../docs/tutorials/io/binary_serialization_api.rst:261
#: ../../docs/tutorials/io/binary_serialization_api.rst:263
#: ../../docs/tutorials/io/binary_serialization_api.rst:272
#: ../../docs/tutorials/io/binary_serialization_api.rst:274
#: ../../docs/tutorials/io/binary_serialization_api.rst:276
#: ../../docs/tutorials/io/binary_serialization_api.rst:278
#: ../../docs/tutorials/io/binary_serialization_api.rst:280
#: ../../docs/tutorials/io/binary_serialization_api.rst:282
#: ../../docs/tutorials/io/binary_serialization_api.rst:291
#: ../../docs/tutorials/io/binary_serialization_api.rst:293
#: ../../docs/tutorials/io/binary_serialization_api.rst:295
#: ../../docs/tutorials/io/binary_serialization_api.rst:297
#: ../../docs/tutorials/io/binary_serialization_api.rst:299
#: ../../docs/tutorials/io/binary_serialization_api.rst:301
#: ../../docs/tutorials/io/binary_serialization_api.rst:303
#: ../../docs/tutorials/io/binary_serialization_api.rst:305
#: ../../docs/tutorials/io/binary_serialization_api.rst:307
#: ../../docs/tutorials/io/binary_serialization_api.rst:316
#: ../../docs/tutorials/io/binary_serialization_api.rst:318
#: ../../docs/tutorials/io/binary_serialization_api.rst:320
#: ../../docs/tutorials/io/binary_serialization_api.rst:322
#: ../../docs/tutorials/io/binary_serialization_api.rst:324
#: ../../docs/tutorials/io/binary_serialization_api.rst:326
#: ../../docs/tutorials/io/binary_serialization_api.rst:328
#: ../../docs/tutorials/io/binary_serialization_api.rst:330
#: ../../docs/tutorials/io/binary_serialization_api.rst:332
#: ../../docs/tutorials/io/binary_serialization_api.rst:334
#: ../../docs/tutorials/io/binary_serialization_api.rst:336
#: ../../docs/tutorials/io/binary_serialization_api.rst:338
#: ../../docs/tutorials/io/binary_serialization_api.rst:347
#: ../../docs/tutorials/io/binary_serialization_api.rst:349
#: ../../docs/tutorials/io/binary_serialization_api.rst:351
#: ../../docs/tutorials/io/binary_serialization_api.rst:353
#: ../../docs/tutorials/io/binary_serialization_api.rst:362
#: ../../docs/tutorials/io/binary_serialization_api.rst:382
#: ../../docs/tutorials/io/binary_serialization_api.rst:384
#: ../../docs/tutorials/io/binary_serialization_api.rst:392
#: ../../docs/tutorials/io/binary_serialization_api.rst:414
#: ../../docs/tutorials/io/binary_serialization_api.rst:423
#: ../../docs/tutorials/io/binary_serialization_api.rst:432
#: ../../docs/tutorials/io/binary_serialization_api.rst:436
#: ../../docs/tutorials/io/binary_serialization_api.rst:444
#: ../../docs/tutorials/io/binary_serialization_api.rst:468
#: ../../docs/tutorials/io/binary_serialization_api.rst:480
#: ../../docs/tutorials/io/binary_serialization_api.rst:492
#: ../../docs/tutorials/io/binary_serialization_api.rst:505
#: ../../docs/tutorials/io/binary_serialization_api.rst:507
#: ../../docs/tutorials/io/binary_serialization_api.rst:516
#: ../../docs/tutorials/io/binary_serialization_api.rst:527
#: ../../docs/tutorials/io/binary_serialization_api.rst:529
#: ../../docs/tutorials/io/binary_serialization_api.rst:538
#: ../../docs/tutorials/io/binary_serialization_api.rst:549
#: ../../docs/tutorials/io/binary_serialization_api.rst:557
#: ../../docs/tutorials/io/binary_serialization_api.rst:570
#: ../../docs/tutorials/io/binary_serialization_api.rst:572
#: ../../docs/tutorials/io/binary_serialization_api.rst:574
#: ../../docs/tutorials/io/binary_serialization_api.rst:583
#: ../../docs/tutorials/io/binary_serialization_api.rst:585
#: ../../docs/tutorials/io/binary_serialization_api.rst:587
#: ../../docs/tutorials/io/binary_serialization_api.rst:589
#: ../../docs/tutorials/io/binary_serialization_api.rst:598
#: ../../docs/tutorials/io/binary_serialization_api.rst:600
#: ../../docs/tutorials/io/binary_serialization_api.rst:602
#: ../../docs/tutorials/io/binary_serialization_api.rst:604
#: ../../docs/tutorials/io/binary_serialization_api.rst:606
#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:444
msgid "4"
msgstr ""

#: ../../docs/tutorials/3d/procedural_geometry/arraymesh.rst:51
msgid "``ARRAY_TEX_UV``"
msgstr ""

#: ../../docs/tutorials/3d/procedural_geometry/arraymesh.rst:52
#: ../../docs/tutorials/3d/procedural_geometry/arraymesh.rst:56
msgid ""
":ref:`PackedVector2Array <class_PackedVector2Array>` or :ref:"
"`PackedVector3Array <class_PackedVector3Array>`"
msgstr ""

#: ../../docs/tutorials/3d/procedural_geometry/arraymesh.rst:54
#: ../../docs/tutorials/io/binary_serialization_api.rst:55
#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:446
msgid "5"
msgstr ""

#: ../../docs/tutorials/3d/procedural_geometry/arraymesh.rst:55
msgid "``ARRAY_TEX_UV2``"
msgstr ""

#: ../../docs/tutorials/3d/procedural_geometry/arraymesh.rst:58
#: ../../docs/tutorials/io/binary_serialization_api.rst:65
#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:456
msgid "10"
msgstr ""

#: ../../docs/tutorials/3d/procedural_geometry/arraymesh.rst:59
msgid "``ARRAY_BONES``"
msgstr ""

#: ../../docs/tutorials/3d/procedural_geometry/arraymesh.rst:60
msgid ""
":ref:`PackedFloat32Array <class_PackedFloat32Array>` of groups of 4 floats "
"or :ref:`PackedInt32Array <class_PackedInt32Array>` of groups of 4 ints. "
"Each group lists indexes of 4 bones that affects a given vertex."
msgstr ""

#: ../../docs/tutorials/3d/procedural_geometry/arraymesh.rst:62
#: ../../docs/tutorials/io/binary_serialization_api.rst:67
#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:458
msgid "11"
msgstr ""

#: ../../docs/tutorials/3d/procedural_geometry/arraymesh.rst:63
msgid "``ARRAY_WEIGHTS``"
msgstr ""

#: ../../docs/tutorials/3d/procedural_geometry/arraymesh.rst:64
msgid ""
":ref:`PackedFloat32Array <class_PackedFloat32Array>` or :ref:"
"`PackedFloat64Array <class_PackedFloat64Array>` of groups of 4 floats. Each "
"float lists the amount of weight the corresponding bone in ``ARRAY_BONES`` "
"has on a given vertex."
msgstr ""

#: ../../docs/tutorials/3d/procedural_geometry/arraymesh.rst:66
#: ../../docs/tutorials/io/binary_serialization_api.rst:69
#: ../../docs/tutorials/io/binary_serialization_api.rst:199
#: ../../docs/tutorials/io/binary_serialization_api.rst:214
#: ../../docs/tutorials/io/binary_serialization_api.rst:227
#: ../../docs/tutorials/io/binary_serialization_api.rst:246
#: ../../docs/tutorials/io/binary_serialization_api.rst:261
#: ../../docs/tutorials/io/binary_serialization_api.rst:276
#: ../../docs/tutorials/io/binary_serialization_api.rst:295
#: ../../docs/tutorials/io/binary_serialization_api.rst:320
#: ../../docs/tutorials/io/binary_serialization_api.rst:351
msgid "12"
msgstr ""

#: ../../docs/tutorials/3d/procedural_geometry/arraymesh.rst:67
msgid "``ARRAY_INDEX``"
msgstr ""

#: ../../docs/tutorials/3d/procedural_geometry/arraymesh.rst:68
#, fuzzy
msgid ":ref:`PackedInt32Array <class_PackedInt32Array>`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/3d/procedural_geometry/arraymesh.rst:70
msgid ""
"In most cases when creating a mesh, we define it by its vertex positions. So "
"usually, the array of vertices (at index 0) is required, while the index "
"array (at index 12) is optional and will only be used if included. It is "
"also possible to create a mesh with only the index array and no vertex "
"array, but that's beyond the scope of this tutorial. In fact, we won't use "
"the index array at all."
msgstr ""

#: ../../docs/tutorials/3d/procedural_geometry/arraymesh.rst:74
msgid ""
"All the other arrays carry information about the vertices. They are optional "
"and will only be used if included. Some of these arrays (e.g. "
"``ARRAY_COLOR``) use one entry per vertex to provide extra information about "
"vertices. They must have the same size as the vertex array. Other arrays (e."
"g. ``ARRAY_TANGENT``) use four entries to describe a single vertex. These "
"must be exactly four times larger than the vertex array."
msgstr ""

#: ../../docs/tutorials/3d/procedural_geometry/arraymesh.rst:78
msgid ""
"For normal usage, the last three parameters in :ref:"
"`add_surface_from_arrays() <class_arraymesh_method_add_surface_from_arrays>` "
"are typically left empty."
msgstr ""

#: ../../docs/tutorials/3d/procedural_geometry/arraymesh.rst:81
#, fuzzy
msgid "Setting up the ArrayMesh"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/3d/procedural_geometry/arraymesh.rst:83
msgid ""
"In the editor, create a :ref:`MeshInstance3D <class_meshinstance3d>` and add "
"an :ref:`ArrayMesh <class_arraymesh>` to it in the Inspector. Normally, "
"adding an ArrayMesh in the editor is not useful, but in this case it allows "
"us to access the ArrayMesh from code without creating one."
msgstr ""

#: ../../docs/tutorials/3d/procedural_geometry/arraymesh.rst:87
msgid "Next, add a script to the MeshInstance3D."
msgstr ""

#: ../../docs/tutorials/3d/procedural_geometry/arraymesh.rst:89
msgid "Under ``_ready()``, create a new Array."
msgstr ""

#: ../../docs/tutorials/3d/procedural_geometry/arraymesh.rst:100
msgid ""
"This will be the array that we keep our surface information in - it will "
"hold all the arrays of data that the surface needs. Godot will expect it to "
"be of size ``Mesh.ARRAY_MAX``, so resize it accordingly."
msgstr ""

#: ../../docs/tutorials/3d/procedural_geometry/arraymesh.rst:115
msgid "Next create the arrays for each data type you will use."
msgstr ""

#: ../../docs/tutorials/3d/procedural_geometry/arraymesh.rst:132
msgid ""
"Once you have filled your data arrays with your geometry you can create a "
"mesh by adding each array to ``surface_array`` and then committing to the "
"mesh."
msgstr ""

#: ../../docs/tutorials/3d/procedural_geometry/arraymesh.rst:160
msgid ""
"In this example, we used ``Mesh.PRIMITIVE_TRIANGLES``, but you can use any "
"primitive type available from mesh."
msgstr ""

#: ../../docs/tutorials/3d/procedural_geometry/arraymesh.rst:163
msgid "Put together, the full code looks like:"
msgstr ""

#: ../../docs/tutorials/3d/procedural_geometry/arraymesh.rst:230
msgid ""
"The code that goes in the middle can be whatever you want. Below we will "
"present some example code for generating a sphere."
msgstr ""

#: ../../docs/tutorials/3d/procedural_geometry/arraymesh.rst:234
#, fuzzy
msgid "Generating geometry"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/3d/procedural_geometry/arraymesh.rst:236
msgid ""
"Here is sample code for generating a sphere. Although the code is presented "
"in GDScript, there is nothing Godot specific about the approach to "
"generating it. This implementation has nothing in particular to do with "
"ArrayMeshes and is just a generic approach to generating a sphere. If you "
"are having trouble understanding it or want to learn more about procedural "
"geometry in general, you can use any tutorial that you find online."
msgstr ""

#: ../../docs/tutorials/3d/procedural_geometry/arraymesh.rst:351
msgid "Saving"
msgstr ""

#: ../../docs/tutorials/3d/procedural_geometry/arraymesh.rst:353
msgid ""
"Finally, we can use the :ref:`ResourceSaver <class_resourcesaver>` class to "
"save the ArrayMesh. This is useful when you want to generate a mesh and then "
"use it later without having to re-generate it."
msgstr ""

#: ../../docs/tutorials/3d/procedural_geometry/meshdatatool.rst:4
msgid "Using the MeshDataTool"
msgstr ""

#: ../../docs/tutorials/3d/procedural_geometry/meshdatatool.rst:6
msgid ""
"The :ref:`MeshDataTool <class_meshdatatool>` is not used to generate "
"geometry. But it is helpful for dynamically altering geometry, for example "
"if you want to write a script to tessellate, simplify, or deform meshes."
msgstr ""

#: ../../docs/tutorials/3d/procedural_geometry/meshdatatool.rst:9
msgid ""
"The MeshDataTool is not as fast as altering arrays directly using ArrayMesh. "
"However, it provides more information and tools to work with meshes than the "
"ArrayMesh does. When the MeshDataTool is used, it calculates mesh data that "
"is not available in ArrayMeshes such as faces and edges, which are necessary "
"for certain mesh algorithms. If you do not need this extra information then "
"it may be better to use an ArrayMesh."
msgstr ""

#: ../../docs/tutorials/3d/procedural_geometry/meshdatatool.rst:14
msgid ""
"MeshDataTool can only be used on Meshes that use the PrimitiveType ``Mesh."
"PRIMITIVE_TRIANGLES``."
msgstr ""

#: ../../docs/tutorials/3d/procedural_geometry/meshdatatool.rst:16
msgid ""
"We initialize the MeshDataTool from an ArrayMesh by calling "
"``create_from_surface()``. If there is already data initialized in the "
"MeshDataTool, calling ``create_from_surface()`` will clear it for you. "
"Alternatively, you can call ``clear()`` yourself before re-using the "
"MeshDataTool."
msgstr ""

#: ../../docs/tutorials/3d/procedural_geometry/meshdatatool.rst:19
msgid ""
"In the examples below, assume an ArrayMesh called ``mesh`` has already been "
"created. See :ref:`ArrayMesh tutorial <doc_arraymesh>` for an example of "
"mesh generation."
msgstr ""

#: ../../docs/tutorials/3d/procedural_geometry/meshdatatool.rst:27
msgid ""
"``create_from_surface()`` uses the vertex arrays from the ArrayMesh to "
"calculate two additional arrays, one for edges and one for faces, for a "
"total of three arrays."
msgstr ""

#: ../../docs/tutorials/3d/procedural_geometry/meshdatatool.rst:30
msgid ""
"An edge is a connection between any two vertices. Each edge in the edge "
"array contains a reference to the two vertices it is composed of, and up to "
"two faces that it is contained within."
msgstr ""

#: ../../docs/tutorials/3d/procedural_geometry/meshdatatool.rst:33
msgid ""
"A face is a triangle made up of three vertices and three corresponding "
"edges. Each face in the face array contains a reference to the three "
"vertices and three edges it is composed of."
msgstr ""

#: ../../docs/tutorials/3d/procedural_geometry/meshdatatool.rst:36
msgid ""
"The vertex array contains edge, face, normal, color, tangent, uv, uv2, bone, "
"and weight information connected with each vertex."
msgstr ""

#: ../../docs/tutorials/3d/procedural_geometry/meshdatatool.rst:39
msgid ""
"To access information from these arrays you use a function of the form "
"``get_****()``:"
msgstr ""

#: ../../docs/tutorials/3d/procedural_geometry/meshdatatool.rst:49
msgid ""
"What you choose to do with these functions is up to you. A common use case "
"is to iterate over all vertices and transform them in some way:"
msgstr ""

#: ../../docs/tutorials/3d/procedural_geometry/meshdatatool.rst:60
msgid ""
"These modifications are not done in place on the ArrayMesh. If you are "
"dynamically updating an existing ArrayMesh, first delete the existing "
"surface before adding a new one using :ref:`commit_to_surface() "
"<class_meshdatatool_method_commit_to_surface>`:"
msgstr ""

#: ../../docs/tutorials/3d/procedural_geometry/meshdatatool.rst:69
msgid ""
"Below is a complete example that turns a spherical mesh called ``mesh`` into "
"a randomly deformed blob complete with updated normals and vertex colors. "
"See :ref:`ArrayMesh tutorial <doc_arraymesh>` for how to generate the base "
"mesh."
msgstr ""

#: ../../docs/tutorials/3d/procedural_geometry/surfacetool.rst:4
#, fuzzy
msgid "Using the SurfaceTool"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/3d/procedural_geometry/surfacetool.rst:6
msgid ""
"The :ref:`SurfaceTool <class_surfacetool>` provides a useful interface for "
"constructing geometry. The interface is similar to the :ref:`ImmediateMesh "
"<class_ImmediateMesh>` class. You set each per-vertex attribute (e.g. "
"normal, uv, color) and then when you add a vertex it captures the attributes."
msgstr ""

#: ../../docs/tutorials/3d/procedural_geometry/surfacetool.rst:11
msgid ""
"The SurfaceTool also provides some useful helper functions like ``index()`` "
"and ``generate_normals()``."
msgstr ""

#: ../../docs/tutorials/3d/procedural_geometry/surfacetool.rst:13
msgid "Attributes are added before each vertex is added:"
msgstr ""

#: ../../docs/tutorials/3d/procedural_geometry/surfacetool.rst:32
msgid ""
"When finished generating your geometry with the :ref:`SurfaceTool "
"<class_surfacetool>` call ``commit()`` to finish generating the mesh. If an :"
"ref:`ArrayMesh <class_ArrayMesh>` is passed to ``commit()`` then it appends "
"a new surface to the end of the ArrayMesh. While if nothing is passed in, "
"``commit()`` returns an ArrayMesh."
msgstr ""

#: ../../docs/tutorials/3d/procedural_geometry/surfacetool.rst:50
msgid "Code creates a triangle with indices"
msgstr ""

#: ../../docs/tutorials/3d/procedural_geometry/surfacetool.rst:99
msgid ""
"You can optionally add an index array, either by calling ``add_index()`` and "
"adding vertices to the index array or by calling ``index()`` which shrinks "
"the vertex array to remove duplicate vertices."
msgstr ""

#: ../../docs/tutorials/3d/procedural_geometry/surfacetool.rst:134
msgid ""
"Similarly, if you have an index array, but you want each vertex to be unique "
"(e.g. because you want to use unique normals or colors per face instead of "
"per-vertex), you can call ``deindex()``."
msgstr ""

#: ../../docs/tutorials/3d/procedural_geometry/surfacetool.rst:146
msgid ""
"If you don't add custom normals yourself, you can add them using "
"``generate_normals()``, which should be called after generating geometry and "
"before committing the mesh using ``commit()`` or ``commit_to_arrays()``. "
"Calling ``generate_normals(true)`` will flip the resulting normals. As a "
"side note, ``generate_normals()`` only works if the primitive type is set to "
"``Mesh.PRIMITIVE_TRIANGLES``."
msgstr ""

#: ../../docs/tutorials/3d/procedural_geometry/surfacetool.rst:151
msgid ""
"You may notice that normal mapping or other material properties look broken "
"on the generated mesh. This is because normal mapping **requires** the mesh "
"to feature *tangents*, which are separate from *normals*. You can either add "
"custom tangents manually, or generate them automatically with "
"``generate_tangents()``. This method requires that each vertex have UVs and "
"normals set already."
msgstr ""

#: ../../docs/tutorials/3d/procedural_geometry/surfacetool.rst:169
msgid ""
"By default, when generating normals, they will be calculated on a per-face "
"basis. If you want smooth vertex normals, when adding vertices, call "
"``add_smooth_group()``. ``add_smooth_group()`` needs to be called while "
"building the geometry, e.g. before the call to ``add_vertex()`` (if non-"
"indexed) or ``add_index()`` (if indexed)."
msgstr ""

#: ../../docs/tutorials/3d/procedural_geometry/immediatemesh.rst:4
#, fuzzy
msgid "Using ImmediateMesh"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/3d/procedural_geometry/immediatemesh.rst:6
msgid ""
"The :ref:`ImmediateMesh <class_ImmediateMesh>` is a convenient tool to "
"create dynamic geometry using an OpenGL 1.x-style API. Which makes it both "
"approachable to use and efficient for meshes which need to be updated every "
"frame."
msgstr ""

#: ../../docs/tutorials/3d/procedural_geometry/immediatemesh.rst:10
msgid ""
"Generating complex geometry (several thousand vertices) with this tool is "
"inefficient, even if it's done only once. Instead, it is designed to "
"generate simple geometry that changes every frame."
msgstr ""

#: ../../docs/tutorials/3d/procedural_geometry/immediatemesh.rst:13
msgid ""
"First, you need to create a :ref:`MeshInstance3D <class_meshinstance3d>` and "
"add an :ref:`ImmediateMesh <class_ImmediateMesh>` to it in the Inspector."
msgstr ""

#: ../../docs/tutorials/3d/procedural_geometry/immediatemesh.rst:16
msgid ""
"Next, add a script to the MeshInstance3D. The code for the ImmediateMesh "
"should go in the ``_process()`` function if you want it to update each "
"frame, or in the ``_ready()`` function if you want to create the mesh once "
"and not update it. If you only generate a surface once, the ImmediateMesh is "
"just as efficient as any other kind of mesh as the generated mesh is cached "
"and reused."
msgstr ""

#: ../../docs/tutorials/3d/procedural_geometry/immediatemesh.rst:22
msgid ""
"To begin generating geometry you must call ``surface_begin()``. "
"``surface_begin()`` takes a ``PrimitiveType`` as an argument. "
"``PrimitiveType`` instructs the GPU how to arrange the primitive based on "
"the vertices given whether it is triangles, lines, points, etc. A complete "
"list can be found under the :ref:`Mesh <class_mesh>` class reference page."
msgstr ""

#: ../../docs/tutorials/3d/procedural_geometry/immediatemesh.rst:28
msgid ""
"Once you have called ``surface_begin()`` you are ready to start adding "
"vertices. You add vertices one at a time. First you add vertex specific "
"attributes such as normals or UVs using ``surface_set_****()`` (e.g. "
"``surface_set_normal()``). Then you call ``surface_add_vertex()`` to add a "
"vertex with those attributes. For example:"
msgstr ""

#: ../../docs/tutorials/3d/procedural_geometry/immediatemesh.rst:42
msgid ""
"Only attributes added before the call to ``surface_add_vertex()`` will be "
"included in that vertex. If you add an attribute twice before calling "
"``surface_add_vertex()``, only the second call will be used."
msgstr ""

#: ../../docs/tutorials/3d/procedural_geometry/immediatemesh.rst:46
msgid ""
"Finally, once you have added all your vertices call ``surface_end()`` to "
"signal that you have finished generating the surface. You can call "
"``surface_begin()`` and ``surface_end()`` multiple times to generate "
"multiple surfaces for the mesh."
msgstr ""

#: ../../docs/tutorials/3d/procedural_geometry/immediatemesh.rst:50
msgid ""
"The example code below draws a single triangle in the ``_ready()`` function."
msgstr ""

#: ../../docs/tutorials/3d/procedural_geometry/immediatemesh.rst:78
msgid ""
"The ImmediateMesh can also be used across frames. Each time you call "
"``surface_begin()`` and ``surface_end()``, you are adding a new surface to "
"the ImmediateMesh. If you want to recreate the mesh from scratch each frame, "
"call ``surface_clear()`` before calling ``surface_begin()``."
msgstr ""

#: ../../docs/tutorials/3d/procedural_geometry/immediatemesh.rst:101
msgid ""
"The above code will dynamically create and draw a single surface each frame."
msgstr ""

#: ../../docs/tutorials/3d/3d_text.rst:4
msgid "3D text"
msgstr ""

#: ../../docs/tutorials/3d/3d_text.rst:9
msgid ""
"In a project, there may be times when text needs to be created as part of a "
"3D scene and not just in the HUD. Godot provides 2 methods to do this: the "
"Label3D node and the TextMesh *resource* for a MeshInstance3D node."
msgstr ""

#: ../../docs/tutorials/3d/3d_text.rst:13
msgid ""
"Additionally, Godot makes it possible to position Control nodes according to "
"a 3D point's position on the camera. This can be used as an alternative to "
"\"true\" 3D text in situations where Label3D and TextMesh aren't flexible "
"enough."
msgstr ""

#: ../../docs/tutorials/3d/3d_text.rst:19
#, fuzzy
msgid ""
"You can see 3D text in action using the `3D Labels and Texts demo project "
"<https://github.com/godotengine/godot-demo-projects/tree/master/3d/"
"labels_and_texts>`__."
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati različite Godo demo projekte "
"`Godot demo projects <https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/tutorials/3d/3d_text.rst:22
#, fuzzy
msgid ""
"This page does **not** cover how to display a GUI scene within a 3D "
"environment. For information on how to achieve that, see the `GUI in 3D "
"<https://github.com/godotengine/godot-demo-projects/tree/master/viewport/"
"gui_in_3d>`__ demo project."
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati različite Godo demo projekte "
"`Godot demo projects <https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/tutorials/3d/3d_text.rst:28
msgid "Label3D"
msgstr ""

#: ../../docs/tutorials/3d/3d_text.rst:32
msgid ""
"Label3D behaves like a Label node, but in 3D space. Unlike the Label node, "
"this Label3D node does **not** inherit properties of a GUI theme. However, "
"its look remains customizable and uses the same font subresource as Control "
"nodes (including support for :abbr:`MSDF (Multi-channel Signed Distance "
"Font)` font rendering)."
msgstr ""

#: ../../docs/tutorials/3d/3d_text.rst:39
#: ../../docs/tutorials/3d/3d_text.rst:93
#: ../../docs/tutorials/3d/3d_text.rst:128
#: ../../docs/tutorials/i18n/localization_using_gettext.rst:16
msgid "Advantages"
msgstr ""

#: ../../docs/tutorials/3d/3d_text.rst:41
msgid ""
"Label3D is faster to generate than TextMesh. While both use a caching "
"mechanism to only render new glyphs once, Label3D will still be faster to "
"(re)generate, especially for long text. This can avoid stuttering during "
"gameplay on low-end CPUs or mobile."
msgstr ""

#: ../../docs/tutorials/3d/3d_text.rst:45
msgid ""
"Label3D can use bitmap fonts and dynamic fonts (with and without :abbr:`MSDF "
"(Multi-channel Signed Distance Font)` or mipmaps). This makes it more "
"flexible on that aspect compared to TextMesh, especially for rendering fonts "
"with self-intersecting outlines."
msgstr ""

#: ../../docs/tutorials/3d/3d_text.rst:52
msgid ""
"See :ref:`doc_gui_using_fonts` for guidelines on configuring font imports."
msgstr ""

#: ../../docs/tutorials/3d/3d_text.rst:57
msgid ""
"By default, Label3D has limited interaction with a 3D environment. It can be "
"occluded by geometry and lit by light sources if the **Shaded** flag is "
"enabled. However, it will not cast shadows even if **Cast Shadow** is set to "
"**On** in the Label3D's GeometryInstance3D properties. This is because the "
"node internally generates a quad mesh (one glyph per quad) with transparent "
"textures and has the same limitations as Sprite3D. Transparency sorting "
"issues can also become apparent when several Label3Ds overlap, especially if "
"they have outlines."
msgstr ""

#: ../../docs/tutorials/3d/3d_text.rst:65
msgid ""
"This can be mitigated by setting the Label3D's transparency mode to **Alpha "
"Cut**, at the cost of less smooth text rendering. The **Opaque Pre-Pass** "
"transparency mode can preserve text smoothness while allowing the Label3D to "
"cast shadows, but some transparency sorting issues will remain."
msgstr ""

#: ../../docs/tutorials/3d/3d_text.rst:70
msgid ""
"See :ref:`Transparency sorting "
"<doc_3d_rendering_limitations_transparency_sorting>` section in the 3D "
"rendering limitations page for more information."
msgstr ""

#: ../../docs/tutorials/3d/3d_text.rst:74
msgid "TextMesh"
msgstr ""

#: ../../docs/tutorials/3d/3d_text.rst:78
msgid ""
"The TextMesh resource has similarities to Label3D. They both display text in "
"a 3D scene, and will use the same font subresource. However, instead of "
"generating transparent quads, TextMesh generates 3D geometry that represents "
"the glyphs' contours and has the properties of a mesh. As a result, a "
"TextMesh is shaded by default and automatically casts shadows onto the "
"environment. A TextMesh can also have a material applied to it (including "
"custom shaders)."
msgstr ""

#: ../../docs/tutorials/3d/3d_text.rst:85
msgid ""
"Here is an example of a texture and how it's applied to the mesh. You can "
"use the texture below as a reference for the generated mesh's UV map:"
msgstr ""

#: ../../docs/tutorials/3d/3d_text.rst:95
msgid "TextMesh has a few advantages over Label3D:"
msgstr ""

#: ../../docs/tutorials/3d/3d_text.rst:97
msgid "TextMesh can use a texture to modify text color on a per-side basis."
msgstr ""

#: ../../docs/tutorials/3d/3d_text.rst:98
msgid "TextMesh geometry can have actual depth to it, giving glyphs a 3D look."
msgstr ""

#: ../../docs/tutorials/3d/3d_text.rst:99
msgid "TextMesh can use custom shaders, unlike Label3D."
msgstr ""

#: ../../docs/tutorials/3d/3d_text.rst:104
#, fuzzy
msgid "There are some limitations to TextMesh:"
msgstr "Ne postoje ograničenja prilikom korištenja Godot-a"

#: ../../docs/tutorials/3d/3d_text.rst:106
msgid ""
"No built-in outline support, unlike Label3D. This can be simulated using "
"custom shaders though."
msgstr ""

#: ../../docs/tutorials/3d/3d_text.rst:108
msgid ""
"Only dynamic fonts are supported (``.ttf``, ``.otf``, ``.woff``, ``."
"woff2``). Bitmap fonts in the ``.fnt`` or ``.font`` formats are **not** "
"supported."
msgstr ""

#: ../../docs/tutorials/3d/3d_text.rst:110
msgid ""
"Fonts with self-intersecting outlines will not render correctly. If you "
"notice rendering issues on fonts downloaded from websites such as Google "
"Fonts, try downloading the font from the font author's official website "
"instead."
msgstr ""

#: ../../docs/tutorials/3d/3d_text.rst:116
msgid "Projected Label node (or any other Control)"
msgstr ""

#: ../../docs/tutorials/3d/3d_text.rst:118
msgid ""
"There is a last solution that is more complex to set up, but provides the "
"most flexibility: projecting a 2D node onto 3D space. This can be achieved "
"using the return value of :ref:"
"`unproject_position<class_Camera3D_method_unproject_position>` method on a "
"Camera3D node in a script's ``_process()`` function. This return value "
"should then be used to set the ``position`` property of a Control node."
msgstr ""

#: ../../docs/tutorials/3d/3d_text.rst:124
#, fuzzy
msgid ""
"See the `3D waypoints <https://github.com/godotengine/godot-demo-projects/"
"tree/master/3d/waypoints>`__ demo for an example of this."
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati različite Godo demo projekte "
"`Godot demo projects <https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/tutorials/3d/3d_text.rst:130
msgid ""
"Any Control node can be used, including Label, RichTextLabel or even nodes "
"such as Button. This allows for powerful formatting and GUI interaction."
msgstr ""

#: ../../docs/tutorials/3d/3d_text.rst:132
msgid ""
"The script-based approach allows for complete freedom in positioning. For "
"example, this makes it considerably easier to pin Controls to the screen's "
"edges when they go off-screen (for in-game 3D markers)."
msgstr ""

#: ../../docs/tutorials/3d/3d_text.rst:135
msgid ""
"Control theming is obeyed. This allows for easier customization that "
"globally applies to the project."
msgstr ""

#: ../../docs/tutorials/3d/3d_text.rst:141
msgid ""
"Projected Controls cannot be occluded by 3D geometry in any way. You can use "
"a RayCast to fully hide the control if its target position is occluded by a "
"collider, but this doesn't allow for partially hiding the control behind a "
"wall."
msgstr ""

#: ../../docs/tutorials/3d/3d_text.rst:145
msgid ""
"Changing text size depending on distance by adjusting the Control's "
"``scale`` property is possible, but it needs to be done manually. Label3D "
"and TextMesh automatically take care of this, at the cost of less "
"flexibility (can't set a minimum/maximum text size in pixels)."
msgstr ""

#: ../../docs/tutorials/3d/3d_text.rst:149
msgid ""
"Handling resolution and aspect ratio changes must be taken into account in "
"the script, which can be challenging."
msgstr ""

#: ../../docs/tutorials/3d/3d_text.rst:153
msgid "Should I use Label3D, TextMesh or a projected Control?"
msgstr ""

#: ../../docs/tutorials/3d/3d_text.rst:155
msgid ""
"In most scenarios, Label3D is recommended as it's easier to set up and "
"provides higher rendering quality (especially if 3D antialiasing is "
"disabled)."
msgstr ""

#: ../../docs/tutorials/3d/3d_text.rst:158
msgid ""
"For advanced use cases, TextMesh is more flexible as it allows styling the "
"text with custom shaders. Custom shaders allow for modifying the final "
"geometry, such as curving the text along a surface. Since the text is actual "
"3D geometry, the text can optionally have depth to it and can also "
"contribute to global illumination."
msgstr ""

#: ../../docs/tutorials/3d/3d_text.rst:164
msgid ""
"If you need features such as BBCode or Control theming support, then using a "
"projected RichTextLabel node is the only way to go."
msgstr ""

#: ../../docs/tutorials/3d/3d_rendering_limitations.rst:4
msgid "3D rendering limitations"
msgstr ""

#: ../../docs/tutorials/3d/3d_rendering_limitations.rst:9
msgid ""
"Due to their focus on performance, real-time rendering engines have many "
"limitations. Godot's renderer is no exception. To work effectively with "
"those limitations, you need to understand them."
msgstr ""

#: ../../docs/tutorials/3d/3d_rendering_limitations.rst:14
msgid "Texture size limits"
msgstr ""

#: ../../docs/tutorials/3d/3d_rendering_limitations.rst:16
msgid ""
"On desktops and laptops, textures larger than 8192×8192 may not be supported "
"on older devices. You can check your target GPU's limitations on `GPUinfo."
"org <https://www.gpuinfo.org/>`__."
msgstr ""

#: ../../docs/tutorials/3d/3d_rendering_limitations.rst:20
msgid ""
"Mobile GPUs are typically limited to 4096×4096 textures. Also, some mobile "
"GPUs don't support repeating non-power-of-two-sized textures. Therefore, if "
"you want your texture to display correctly on all platforms, you should "
"avoid using textures larger than 4096×4096 and use a power of two size if "
"the texture needs to repeat."
msgstr ""

#: ../../docs/tutorials/3d/3d_rendering_limitations.rst:26
msgid ""
"To limit the size of a specific texture that may be too large to render, you "
"can set the **Process > Size Limit** import option to a value greater than "
"``0``. This will reduce the texture's dimensions on import (preserving "
"aspect ratio) without affecting the source file."
msgstr ""

#: ../../docs/tutorials/3d/3d_rendering_limitations.rst:34
msgid "Color banding"
msgstr ""

#: ../../docs/tutorials/3d/3d_rendering_limitations.rst:36
msgid ""
"When using the Forward+ or Forward Mobile rendering methods, Godot's 3D "
"engine renders internally in HDR. However, the rendering output will be "
"tonemapped to a low dynamic range so it can be displayed on the screen. This "
"can result in visible banding, especially when using untextured materials. "
"For performance reasons, color precision is also lower when using the "
"Forward Mobile rendering method compared to Forward+."
msgstr ""

#: ../../docs/tutorials/3d/3d_rendering_limitations.rst:43
msgid ""
"When using the Compatibility rendering method, HDR is not used and the color "
"precision is the lowest of all rendering methods. This also applies to 2D "
"rendering, where banding may be visible when using smooth gradient textures."
msgstr ""

#: ../../docs/tutorials/3d/3d_rendering_limitations.rst:47
#, fuzzy
msgid "There are two main ways to alleviate banding:"
msgstr "Ne postoje ograničenja prilikom korištenja Godot-a"

#: ../../docs/tutorials/3d/3d_rendering_limitations.rst:49
msgid ""
"If using the Forward+ or Forward Mobile rendering methods, enable **Use "
"Debanding** in the advanced Project Settings. This applies a fullscreen "
"debanding shader as a post-processing effect and is very cheap."
msgstr ""

#: ../../docs/tutorials/3d/3d_rendering_limitations.rst:52
msgid ""
"Alternatively, bake some noise into your textures. This is mainly effective "
"in 2D, e.g. for vignetting effects. In 3D, you can also use a `custom "
"debanding shader <https://github.com/fractilegames/godot-gles2-debanding-"
"material>`__ to be applied on your *materials*. This technique works even if "
"your project is rendered with low color precision, which means it will work "
"when using the Mobile and Compatibility rendering methods."
msgstr ""

#: ../../docs/tutorials/3d/3d_rendering_limitations.rst:63
msgid "Color banding comparison (contrast increased for more visibility)"
msgstr ""

#: ../../docs/tutorials/3d/3d_rendering_limitations.rst:67
msgid ""
"See `Banding in Games: A Noisy Rant (PDF) <https://loopit.dk/"
"banding_in_games.pdf>`__ for more details about banding and ways to combat "
"it."
msgstr ""

#: ../../docs/tutorials/3d/3d_rendering_limitations.rst:71
msgid "Depth buffer precision"
msgstr ""

#: ../../docs/tutorials/3d/3d_rendering_limitations.rst:73
msgid ""
"To sort objects in 3D space, rendering engines rely on a *depth buffer* "
"(also called *Z-buffer*). This buffer has a finite precision: 24-bit on "
"desktop platforms, sometimes 16-bit on mobile platforms (for performance "
"reasons). If two different objects end up on the same buffer value, then Z-"
"fighting will occur. This will materialize as textures flickering back and "
"forth as the camera moves or rotates."
msgstr ""

#: ../../docs/tutorials/3d/3d_rendering_limitations.rst:80
msgid ""
"To make the depth buffer more precise over the rendered area, you should "
"*increase* the Camera node's **Near** property. However, be careful: if you "
"set it too high, players will be able to see through nearby geometry. You "
"should also *decrease* the Camera node's **Far** property to the lowest "
"permissible value for your use case, though keep in mind it won't impact "
"precision as much as the **Near** property."
msgstr ""

#: ../../docs/tutorials/3d/3d_rendering_limitations.rst:87
msgid ""
"If you only need high precision when the player can see far away, you could "
"change it dynamically based on the game conditions. For instance, if the "
"player enters an airplane, the **Near** property can be temporarily "
"increased to avoid Z-fighting in the distance. It can then be decreased once "
"the player leaves the airplane."
msgstr ""

#: ../../docs/tutorials/3d/3d_rendering_limitations.rst:93
msgid ""
"Depending on the scene and viewing conditions, you may also be able to move "
"the Z-fighting objects further apart without the difference being visible to "
"the player."
msgstr ""

#: ../../docs/tutorials/3d/3d_rendering_limitations.rst:101
msgid ""
"Z-fighting comparison (before and after tweaking the scene by offsetting the "
"Label3D away from the floor)"
msgstr ""

#: ../../docs/tutorials/3d/3d_rendering_limitations.rst:106
msgid "Transparency sorting"
msgstr ""

#: ../../docs/tutorials/3d/3d_rendering_limitations.rst:108
msgid ""
"In Godot, transparent materials are drawn after opaque materials. "
"Transparent objects are sorted back to front before being drawn based on the "
"Node3D's position, not the vertex position in world space. Due to this, "
"overlapping objects may often be sorted out of order. To fix improperly "
"sorted objects, tweak the material's :ref:`Render Priority "
"<class_Material_property_render_priority>` property or the node's :ref:"
"`Sorting Offset <class_VisualInstance3D_property_sorting_offset>`. Render "
"Priority will force specific materials to appear in front of or behind other "
"transparent materials, while Sorting Offset will move the object forward or "
"backward for the purpose of sorting. Even then, these may not always be "
"sufficient."
msgstr ""

#: ../../docs/tutorials/3d/3d_rendering_limitations.rst:121
msgid ""
"Some rendering engines feature *order-independent transparency* techniques "
"to alleviate this, but this is costly on the GPU. Godot currently doesn't "
"provide this feature. There are still several ways to avoid this problem:"
msgstr ""

#: ../../docs/tutorials/3d/3d_rendering_limitations.rst:125
msgid ""
"Only make materials transparent if you actually need it. If a material only "
"has a small transparent part, consider splitting it into a separate "
"material. This will allow the opaque part to cast shadows and will also "
"improve performance."
msgstr ""

#: ../../docs/tutorials/3d/3d_rendering_limitations.rst:129
msgid ""
"If your texture mostly has fully opaque and fully transparent areas, you can "
"use alpha testing instead of alpha blending. This transparency mode is "
"faster to render and doesn't suffer from transparency issues. Enable "
"**Transparency > Transparency** to **Alpha Scissor** in StandardMaterial3D, "
"and adjust **Transparency > Alpha Scissor Threshold** accordingly if needed. "
"Note that MSAA will not antialias the texture's edges unless alpha "
"antialiasing is enabled in the material's properties. However, FXAA, TAA and "
"supersampling will be able to antialias the texture's edges regardless of "
"whether alpha antialiasing is enabled on the material."
msgstr ""

#: ../../docs/tutorials/3d/3d_rendering_limitations.rst:139
msgid ""
"If you need to render semi-transparent areas of the texture, alpha scissor "
"isn't suitable. Instead, setting the StandardMaterial3D's **Transparency > "
"Transparency** property to **Depth Pre-Pass** can sometimes work (at a "
"performance cost). You can also try the **Alpha Hash** mode."
msgstr ""

#: ../../docs/tutorials/3d/3d_rendering_limitations.rst:144
msgid ""
"If you want a material to fade with distance, use the StandardMaterial3D "
"distance fade mode **Pixel Dither** or **Object Dither** instead of **Pixel "
"Alpha**. This will make the material opaque, which also speeds up rendering."
msgstr ""

#: ../../docs/tutorials/3d/3d_rendering_limitations.rst:152
msgid ""
"Transparency sorting comparison (alpha-blended materials on the left, alpha "
"scissor materials on the right)"
msgstr ""

#: ../../docs/tutorials/3d/3d_rendering_limitations.rst:155
msgid "Multi-sample antialiasing"
msgstr ""

#: ../../docs/tutorials/3d/3d_rendering_limitations.rst:159
msgid ""
"Antialiasing is explained in detail on the :ref:`doc_3d_antialiasing` page."
msgstr ""

#: ../../docs/tutorials/3d/3d_rendering_limitations.rst:161
msgid ""
"Multi-sample antialiasing (MSAA) takes multiple *coverage* samples at the "
"edges of polygons when rendering objects. It does not increase the number of "
"*color* samples used to render a scene. Here's what this means in practice:"
msgstr ""

#: ../../docs/tutorials/3d/3d_rendering_limitations.rst:165
msgid ""
"Edges of meshes will be smoothed out nicely (as well as supersampling would)."
msgstr ""

#: ../../docs/tutorials/3d/3d_rendering_limitations.rst:166
msgid ""
"Transparent materials that use *alpha testing* (1-bit transparency) won't be "
"smoothed out."
msgstr ""

#: ../../docs/tutorials/3d/3d_rendering_limitations.rst:167
msgid ""
"Specular aliasing (\"sparkles\" that appear on reflective surfaces) won't be "
"reduced."
msgstr ""

#: ../../docs/tutorials/3d/3d_rendering_limitations.rst:169
msgid ""
"There are several ways to work around this limitation depending on your "
"performance budget:"
msgstr ""

#: ../../docs/tutorials/3d/3d_rendering_limitations.rst:171
msgid ""
"To make specular aliasing less noticeable, open the Project Settings and "
"enable **Rendering > Quality > Screen Space Filters > Screen Space Roughness "
"Limiter**. This filter has a moderate cost on performance, so it should only "
"be enabled if you actually need it."
msgstr ""

#: ../../docs/tutorials/3d/3d_rendering_limitations.rst:176
msgid ""
"Enable fast approximate antialiasing (FXAA) in addition to (or instead of) "
"MSAA. Since FXAA is a screen-space antialiasing method, it will smooth out "
"anything. As a downside, FXAA also makes the scene appear blurrier, "
"especially at resolutions below 1440p. FXAA also lacks temporal information, "
"which means its impact on specular aliasing is limited."
msgstr ""

#: ../../docs/tutorials/3d/3d_rendering_limitations.rst:182
msgid ""
"Enable temporal antialiasing (TAA) in addition to (or instead of) MSAA. "
"Since TAA is a screen-space antialiasing method, it will smooth out "
"anything. As a downside, TAA also makes the scene appear blurrier, "
"especially at resolutions below 1440p. TAA provides superior quality "
"compared to FXAA and can effectively combat specular aliasing. However, TAA "
"has a greater performance cost compared to FXAA, and TAA can introduce "
"ghosting artifacts with fast movement."
msgstr ""

#: ../../docs/tutorials/3d/3d_rendering_limitations.rst:190
msgid ""
"Render the scene at a higher resolution by increasing the **Scaling 3D > "
"Scale** project setting above ``1.0``. This technique is called supersample "
"antialiasing (SSAA) and is very slow. Its use is generally only recommended "
"for offline rendering."
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:4
msgid "Standard Material 3D and ORM Material 3D"
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:9
msgid ""
"``StandardMaterial3D`` and ``ORMMaterial3D`` (Occlusion, Roughness, "
"Metallic) are default 3D materials that aim to provide most of the features "
"artists look for in a material, without the need for writing shader code. "
"However, they can be converted to shader code if additional functionality is "
"needed."
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:14
msgid "This tutorial explains the parameters present in both materials."
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:16
msgid ""
"There are 4 ways to add these materials to an object. A material can be "
"added in the *Material* property of the mesh. It can be added in the "
"*Material* property of the node using the mesh (such as a MeshInstance3D "
"node), the *Material Override* property of the node using the mesh, and the "
"*Material Overlay*."
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:23
msgid ""
"If you add a material to the mesh itself, every time that mesh is used it "
"will have that material. If you add a material to the node using the mesh, "
"the material will only be used by that node, it will also override the "
"material property of the mesh. If a material is added in the *Material "
"Override* property of the node, it will only be used by that node. It will "
"also override the regular material property of the node and the material "
"property of the mesh."
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:30
msgid ""
"The *Material Overlay* property will render a material **over** the current "
"one being used by the mesh. As an example, this can be used to put a "
"transparent shield effect on a mesh."
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:34
msgid "BaseMaterial 3D settings"
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:36
msgid ""
"StandardMaterial3D has many settings that determine the look of a material. "
"All of these are under the BaseMaterial3D category"
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:41
msgid ""
"ORM materials are almost exactly the same with one difference. Instead of "
"separate settings and textures for occlusion, roughness, and metallic, there "
"is a single ORM texture. The different color channels of that texture are "
"used for each parameter. Programs such as Substance Painter and Armor Paint "
"will give you the option to export in this format, for these two programs "
"it's with the export preset for unreal engine, which also uses ORM textures."
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:48
msgid "Transparency"
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:50
msgid ""
"By default, materials in Godot are opaque. This is fast to render, but it "
"means the material can't be seen through even if you use a transparent "
"texture in the **Albedo > Texture** property (or set **Albedo > Color** to a "
"transparent color)."
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:54
msgid ""
"To be able to see through a material, the material needs to be made "
"*transparent*. Godot offers several transparency modes:"
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:57
msgid ""
"**Disabled:** Material is opaque. This is the fastest to render, with all "
"rendering features supported."
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:60
msgid ""
"**Alpha:** Material is transparent. Semi-transparent areas are drawn with "
"blending. This is slow to render, but it allows for partial transparency "
"(also known as translucency). Materials using alpha blending also can't cast "
"shadows, and are not visible in screen-space reflections."
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:65
msgid "**Alpha** is a good fit for particle effects and VFX."
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:67
msgid ""
"**Alpha Scissor:** Material is transparent. Semi-transparent areas whose "
"opacity is below **Alpha Scissor Threshold** are not drawn (above this "
"opacity, these are drawn as opaque). This is faster to render than Alpha and "
"doesn't exhibit transparency sorting issues. The downside is that this "
"results in \"all or nothing\" transparency, with no intermediate values "
"possible. Materials using alpha scissor can cast shadows."
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:74
msgid ""
"**Alpha Scissor** is ideal for foliage and fences, since these have hard "
"edges and require correct sorting to look good."
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:77
msgid ""
"**Alpha Hash:** Material is transparent. Semi-transparent areas are drawn "
"using dithering. This is also \"all or nothing\" transparency, but dithering "
"helps represent partially opaque areas with limited precision depending on "
"viewport resolution. Materials using alpha hash can cast shadows."
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:82
msgid ""
"**Alpha Hash** is suited for realistic-looking hair, although stylized hair "
"may work better with alpha scissor."
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:85
msgid ""
"**Depth Pre-Pass:** This renders the object's fully opaque pixels via the "
"opaque pipeline first, then renders the rest with alpha blending. This "
"allows transparency sorting to be *mostly* correct (albeit not fully so, as "
"partially transparent regions may still exhibit incorrect sorting). "
"Materials using depth prepass can cast shadows."
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:93
msgid ""
"Godot will automatically force the material to be transparent with alpha "
"blending if *any* of these conditions is met:"
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:96
msgid "Setting the transparency mode to **Alpha** (as described here)."
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:97
msgid "Setting a blend mode other than the default **Mix**"
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:98
msgid "Enabling **Refraction**, **Proximity Fade**, or **Distance Fade**."
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:100
msgid ""
"Comparison between alpha blending (left) and alpha scissor (right) "
"transparency:"
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:106
msgid ""
"Alpha-blended transparency has several :ref:`limitations "
"<doc_3d_rendering_limitations_transparency_sorting>`:"
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:109
msgid ""
"Alpha-blended materials are significantly slower to render, especially if "
"they overlap."
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:111
msgid ""
"Alpha-blended materials may exhibit sorting issues when transparent surfaces "
"overlap each other. This means that surfaces may render in the incorrect "
"order, with surfaces in the back appearing to be in front of those which are "
"actually closer to the camera."
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:115
msgid ""
"Alpha-blended materials don't cast shadows, although they can receive "
"shadows."
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:116
msgid ""
"Alpha-blended materials don't appear in any reflections (other than "
"reflection probes)."
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:118
msgid ""
"Screen-space reflections and sharp SDFGI reflections don't appear on alpha-"
"blended materials. When SDFGI is enabled, rough reflections are used as a "
"fallback regardless of material roughness."
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:122
msgid ""
"Before using the **Alpha** transparency mode, always consider whether "
"another transparency mode is more suited for your needs."
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:128
msgid "Alpha Antialiasing"
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:132
msgid ""
"This property is only visible when the transparency mode is **Alpha "
"Scissor** or **Alpha Hash**."
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:135
msgid ""
"While alpha scissor and alpha hash materials are faster to render than alpha-"
"blended materials, they exhibit hard edges between opaque and transparent "
"regions. While it's possible to use post-processing-based :ref:`antialiasing "
"techniques <doc_3d_antialiasing>` such as FXAA and TAA, this is not always "
"desired as these techniques tend to make the final result look blurrier or "
"exhibit ghosting artifacts."
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:142
#, fuzzy
msgid "There are 3 alpha antialiasing modes available:"
msgstr "Ne postoje ograničenja prilikom korištenja Godot-a"

#: ../../docs/tutorials/3d/standard_material_3d.rst:144
msgid ""
"**Disabled:** No alpha antialiasing. Edges of transparent materials will "
"appear aliased unless a post-processing-based antialiasing solution is used."
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:146
msgid ""
"**Alpha Edge Blend:** Results in a smooth transition between opaque and "
"transparent areas. Also known as \"alpha to coverage\"."
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:148
msgid ""
"**Alpha Edge Clip:** Results in a sharp, but still antialiased transition "
"between opaque and transparent areas. Also known as \"alpha to coverage + "
"alpha to one\"."
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:152
msgid ""
"When the alpha antialiasing mode is set to **Alpha Edge Blend** or **Alpha "
"Edge Clip**, a new **Alpha Antialiasing Edge** property becomes visible "
"below in the inspector. This property controls the threshold below which "
"pixels should be made transparent. While you've already defined an alpha "
"scissor threshold (when using **Alpha Scissor** only), this additional "
"threshold is used to smoothly transition between opaque and transparent "
"pixels. **Alpha Antialiasing Edge** must *always* be set to a value that is "
"strictly below the alpha scissor threshold. The default of ``0.3`` is a "
"sensible value with an alpha scissor of threshold of ``0.5``, but remember "
"to adjust this alpha antialiasing edge when modifying the alpha scissor "
"threshold."
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:163
msgid ""
"If you find the antialiasing effect not effective enough, try increasing "
"**Alpha Antialiasing Edge** while making sure it's below **Alpha Scissor "
"Threshold** (if the material uses alpha scissor). On the other hand, if you "
"notice the texture's appearance visibly changing as the camera moves closer "
"to the material, try decreasing **Alpha Antialiasing Edge**."
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:171
msgid ""
"For best results, MSAA 3D should be set to at least 2× in the Project "
"Settings when using alpha antialiasing. This is because this feature relies "
"on alpha to coverage, which is a feature provided by MSAA."
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:175
msgid ""
"Without MSAA, a fixed dithering pattern is applied on the material's edges, "
"which isn't very effective at smoothing out edges (although it can still "
"help a little)."
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:180
msgid "Blend Mode"
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:182
msgid ""
"Controls the blend mode for the material. Keep in mind that any mode other "
"than *Mix* forces the object to go through the transparent pipeline."
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:185
msgid ""
"**Mix:** Default blend mode, alpha controls how much the object is visible."
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:186
msgid ""
"**Add:** The final color of the object is added to the color of the screen, "
"nice for flares or some fire-like effects."
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:188
msgid ""
"**Sub:** The final color of the object is subtracted from the color of the "
"screen."
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:190
msgid ""
"**Mul:** The final color of the object is multiplied with the color of the "
"screen."
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:196
msgid "Cull Mode"
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:198
msgid ""
"Determines which side of the object is not drawn when backfaces are rendered:"
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:200
msgid "**Back:** The back of the object is culled when not visible (default)."
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:201
msgid "**Front:** The front of the object is culled when not visible."
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:202
msgid ""
"**Disabled:** Used for objects that are double-sided (no culling is "
"performed)."
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:206
#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/available_formats.rst:88
msgid ""
"By default, Blender has backface culling disabled on materials and will "
"export materials to match how they render in Blender. This means that "
"materials in Godot will have their cull mode set to **Disabled**. This can "
"decrease performance since backfaces will be rendered, even when they are "
"being culled by other faces. To resolve this, enable **Backface Culling** in "
"Blender's Materials tab, then export the scene to glTF again."
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:214
msgid "Depth Draw Mode"
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:216
msgid "Specifies when depth rendering must take place."
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:218
msgid "**Opaque Only (default):** Depth is only drawn for opaque objects."
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:219
msgid ""
"**Always:** Depth draw is drawn for both opaque and transparent objects."
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:220
msgid ""
"**Never:** No depth draw takes place (do not confuse this with the No Depth "
"Test option below)."
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:222
msgid ""
"**Depth Pre-Pass:** For transparent objects, an opaque pass is made first "
"with the opaque parts, then transparency is drawn above. Use this option "
"with transparent grass or tree foliage."
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:229
msgid "No Depth Test"
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:231
msgid ""
"In order for close objects to appear over far away objects, depth testing is "
"performed. Disabling it has the result of objects appearing over (or under) "
"everything else."
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:235
msgid ""
"Disabling this makes the most sense for drawing indicators in world space, "
"and works very well with the *Render Priority* property of Material (see the "
"bottom of this page)."
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:245
#, fuzzy
msgid "Shading mode"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/3d/standard_material_3d.rst:247
msgid ""
"Godot has a more or less uniform cost per pixel thanks to the depth pre-"
"pass. All lighting calculations are made by running the lighting shader on "
"every pixel."
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:251
msgid ""
"As these calculations are costly, performance can be brought down "
"considerably in some corner cases such as drawing several layers of "
"transparency (which is common in particle systems). Switching to the "
"**Unshaded** shading mode may help improve performance in these cases, "
"especially when the camera is close to particles."
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:256
msgid ""
"Additionally, on low-end or mobile devices, switching to unshaded rendering "
"can considerably increase rendering performance."
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:261
msgid ""
"Keep in mind that when unshaded rendering is enabled, lights will not affect "
"the material at all."
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:266
msgid ""
"**Per-Vertex** shading is listed as an option in the shading mode property. "
"However, per-vertex shading is currently unimplemented and will act "
"identical to per-pixel shading."
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:270
msgid ""
"Support for per-vertex shading is planned to be reimplemented in a future "
"Godot release."
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:274
msgid "Diffuse Mode"
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:276
msgid ""
"Specifies the algorithm used by diffuse scattering of light when hitting the "
"object. The default is **Burley**. Other modes are also available:"
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:279
msgid ""
"**Burley:** Default mode, the original Disney Principled PBS diffuse "
"algorithm."
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:280
msgid "**Lambert:** Is not affected by roughness."
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:281
msgid ""
"**Lambert Wrap:** Extends Lambert to cover more than 90 degrees when "
"roughness increases. Works great for hair and simulating cheap subsurface "
"scattering. This implementation is energy conserving."
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:284
msgid ""
"**Toon:** Provides a hard cut for lighting, with smoothing affected by "
"roughness. It is recommended you disable sky contribution from your "
"environment's ambient light settings or disable ambient light in the "
"StandardMaterial3D to achieve a better effect."
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:292
msgid "Specular Mode"
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:294
msgid ""
"Specifies how the specular blob will be rendered. The specular blob "
"represents the shape of a light source reflected in the object."
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:297
msgid "**SchlickGGX:** The most common blob used by PBR 3D engines nowadays."
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:298
msgid ""
"**Blinn:** Common in previous-generation engines. Not worth using nowadays, "
"but left here for the sake of compatibility."
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:300
msgid "**Phong:** Same as above."
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:301
msgid ""
"**Toon:** Creates a toon blob, which changes size depending on roughness."
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:302
msgid "**Disabled:** Sometimes the blob gets in the way. Begone!"
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:307
msgid "Disable Ambient Light"
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:309
msgid ""
"Makes the object not receive any kind of ambient lighting that would "
"otherwise light it."
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:313
msgid "Disable Fog"
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:315
msgid ""
"Makes the object unaffected by depth-based or volumetric fog. This is useful "
"for particles or other additively blended materials that would otherwise "
"show the shape of the mesh (even in places where it would be invisible "
"without the fog)."
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:318
msgid "Vertex Color"
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:320
msgid ""
"This setting allows choosing what is done by default to vertex colors that "
"come from your 3D modeling application. By default, they are ignored."
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:326
msgid "Use as Albedo"
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:328
msgid "Choosing this option means vertex color is used as albedo color."
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:331
msgid "Is sRGB"
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:333
msgid ""
"Most 3D modeling software will likely export vertex colors as sRGB, so "
"toggling this option on will help them look correct."
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:337
msgid "Albedo"
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:339
msgid ""
"*Albedo* is the base color for the material, on which all the other settings "
"operate. When set to *Unshaded*, this is the only color that is visible. In "
"previous versions of Godot, this channel was named *Diffuse*. The change of "
"name mainly happened because, in PBR (Physically Based Rendering), this "
"color affects many more calculations than just the diffuse lighting path."
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:345
msgid "Albedo color and texture can be used together as they are multiplied."
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:347
msgid ""
"*Alpha channel* in albedo color and texture is also used for the object "
"transparency. If you use a color or texture with *alpha channel*, make sure "
"to either enable transparency or *alpha scissoring* for it to work."
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:352
msgid "Metallic"
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:354
msgid ""
"Godot uses a metallic model over competing models due to its simplicity. "
"This parameter defines how reflective the material is. The more reflective, "
"the less diffuse/ambient light affects the material and the more light is "
"reflected. This model is called \"energy-conserving\"."
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:359
msgid ""
"The *Specular* parameter is a general amount for the reflectivity (unlike "
"*Metallic*, this is not energy-conserving, so leave it at ``0.5`` and don't "
"touch it unless you need to)."
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:363
msgid ""
"The minimum internal reflectivity is ``0.04``, so it's impossible to make a "
"material completely unreflective, just like in real life."
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:369
msgid "Roughness"
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:371
msgid ""
"*Roughness* affects the way reflection happens. A value of ``0`` makes it a "
"perfect mirror while a value of ``1`` completely blurs the reflection "
"(simulating natural microsurfacing). Most common types of materials can be "
"achieved with the right combination of *Metallic* and *Roughness*."
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:379
msgid "Emission"
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:381
msgid ""
"*Emission* specifies how much light is emitted by the material (keep in mind "
"this does not include light surrounding geometry unless :ref:`VoxelGI "
"<doc_using_voxel_gi>` or :ref:`SDFGI <doc_using_sdfgi>` are used). This "
"value is added to the resulting final image and is not affected by other "
"lighting in the scene."
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:389
msgid "Normal map"
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:391
msgid ""
"Normal mapping allows you to set a texture that represents finer shape "
"detail. This does not modify geometry, only the incident angle for light. In "
"Godot, only the red and green channels of normal maps are used for better "
"compression and wider compatibility."
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:400
msgid ""
"Godot requires the normal map to use the X+, Y+ and Z+ coordinates, this is "
"known as OpenGL style. If you've imported a material made to be used with "
"another engine it may be DirectX style, in which case the normal map needs "
"to be converted so its Y axis is flipped."
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:405
#: ../../docs/tutorials/assets_pipeline/importing_images.rst:326
#: ../../docs/tutorials/assets_pipeline/importing_images.rst:427
msgid ""
"More information about normal maps (including a coordinate order table for "
"popular engines) can be found `here <http://wiki.polycount.com/wiki/"
"Normal_Map_Technical_Details>`__."
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:410
#: ../../docs/tutorials/3d/visibility_ranges.rst:216
msgid "Rim"
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:412
msgid ""
"Some fabrics have small micro-fur that causes light to scatter around it. "
"Godot emulates this with the *Rim* parameter. Unlike other rim lighting "
"implementations, which just use the emission channel, this one actually "
"takes light into account (no light means no rim). This makes the effect "
"considerably more believable."
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:419
msgid ""
"Rim size depends on roughness, and there is a special parameter to specify "
"how it must be colored. If *Tint* is ``0``, the color of the light is used "
"for the rim. If *Tint* is ``1``, then the albedo of the material is used. "
"Using intermediate values generally works best."
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:425
#: ../../docs/tutorials/3d/visibility_ranges.rst:217
msgid "Clearcoat"
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:428
msgid ""
"The *Clearcoat* parameter is used to add a secondary pass of transparent "
"coat to the material. This is common in car paint and toys. In practice, "
"it's a smaller specular blob added on top of the existing material."
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:435
#: ../../docs/tutorials/3d/visibility_ranges.rst:218
msgid "Anisotropy"
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:438
msgid ""
"This changes the shape of the specular blob and aligns it to tangent space. "
"Anisotropy is commonly used with hair, or to make materials such as brushed "
"aluminum more realistic. It works especially well when combined with "
"flowmaps."
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:445
msgid "Ambient Occlusion"
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:447
msgid ""
"It is possible to specify a baked ambient occlusion map. This map affects "
"how much ambient light reaches each surface of the object (it does not "
"affect direct light by default). While it is possible to use Screen-Space "
"Ambient Occlusion (SSAO) to generate ambient occlusion, nothing beats the "
"quality of a well-baked AO map. It is recommended to bake ambient occlusion "
"whenever possible."
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:456
#: ../../docs/tutorials/3d/visibility_ranges.rst:219
msgid "Height"
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:459
msgid ""
"Setting a depth map on a material produces a ray-marched search to emulate "
"the proper displacement of cavities along the view direction. This is not "
"real added geometry, but an illusion of depth. It may not work for complex "
"objects, but it produces a realistic depth effect for textures. For best "
"results, *Depth* should be used together with normal mapping."
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:468
#: ../../docs/tutorials/3d/visibility_ranges.rst:220
msgid "Subsurface Scattering"
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:471
msgid ""
"This effect emulates light that penetrates an object's surface, is "
"scattered, and then comes out. It is useful to create realistic skin, "
"marble, colored liquids, etc."
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:478
#: ../../docs/tutorials/3d/visibility_ranges.rst:221
msgid "Back Lighting"
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:480
#: ../../docs/tutorials/3d/standard_material_3d.rst:679
msgid ""
"This controls how much light from the lit side (visible to light) is "
"transferred to the dark side (opposite from the light). This works well for "
"thin objects such as plant leaves, grass, human ears, etc."
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:485
#: ../../docs/tutorials/3d/visibility_ranges.rst:222
msgid "Refraction"
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:487
msgid ""
"When refraction is enabled, Godot attempts to fetch information from behind "
"the object being rendered. This allows distorting the transparency in a way "
"similar to refraction in real life."
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:491
msgid ""
"Remember to use a transparent albedo texture (or reduce the albedo color's "
"alpha channel) to make refraction visible, as refraction relies on "
"transparency to have a visible effect."
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:495
msgid ""
"A normal map can optionally be specified in the **Refraction Texture** "
"property to allow distorting the refraction's direction on a per-pixel basis."
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:502
msgid ""
"Refraction is implemented as a screen-space effect and forces the material "
"to be transparent. This makes the effect relatively fast, but this results "
"in some limitations:"
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:506
msgid ""
":ref:`Transparency sorting "
"<doc_3d_rendering_limitations_transparency_sorting>` issues may occur."
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:508
msgid ""
"The refractive material cannot refract onto itself, or onto other "
"transparent materials. A refractive material behind another transparent "
"material will be invisible."
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:511
msgid ""
"Off-screen objects cannot appear in the refraction. This is most noticeable "
"with high refraction strength values."
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:513
msgid ""
"Opaque materials in front of the refractive material will appear to have "
"\"refracted\" edges, even though they shouldn't."
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:517
msgid "Detail"
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:519
msgid ""
"Godot allows using secondary albedo and normal maps to generate a detail "
"texture, which can be blended in many ways. By combining this with secondary "
"UV or triplanar modes, many interesting textures can be achieved."
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:525
msgid "There are several settings that control how detail is used."
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:527
msgid ""
"Mask: The detail mask is a black and white image used to control where the "
"blending takes place on a texture. White is for the detail textures, Black "
"is for the regular material textures, different shades of gray are for "
"partial blending of the material textures and detail textures."
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:532
msgid ""
"Blend Mode: These four modes control how the textures are blended together."
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:534
msgid ""
"Mix: Combines pixel values of both textures. At black, only show the "
"material texture, at white, only show the detail texture. Values of gray "
"create a smooth blend between the two."
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:538
msgid ""
"Add: Adds pixel values of one Texture with the other. Unlike mix mode both "
"textures are completely mixed at white parts of a mask and not at gray "
"parts. The original texture is mostly unchanged at black"
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:542
msgid ""
"Sub: Subtracts pixel values of one texture with the other. The second "
"texture is completely subtracted at white parts of a mask with only a little "
"subtraction in black parts, gray parts being different levels of subtraction "
"based on the exact texture."
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:547
msgid ""
"Mul: Multiplies the RGB channel numbers for each pixel from the top texture "
"with the values for the corresponding pixel from the bottom texture."
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:550
msgid ""
"Albedo: This is where you put an albedo texture you want to blend. If "
"nothing is in this slot it will be interpreted as white by default."
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:553
msgid ""
"Normal: This is where you put a normal texture you want to blend. If nothing "
"is in this slot it will be interpreted as a flat normal map. This can still "
"be used even if the material does not have normal map enabled."
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:558
msgid "UV1 and UV2"
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:560
msgid ""
"Godot supports two UV channels per material. Secondary UV is often useful "
"for ambient occlusion or emission (baked light). UVs can be scaled and "
"offset, which is useful when using repeating textures."
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:567
msgid "Triplanar Mapping"
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:569
msgid ""
"Triplanar mapping is supported for both UV1 and UV2. This is an alternative "
"way to obtain texture coordinates, sometimes called \"Autotexture\". "
"Textures are sampled in X, Y and Z and blended by the normal. Triplanar "
"mapping can be performed in either world space or object space."
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:574
msgid ""
"In the image below, you can see how all primitives share the same material "
"with world triplanar, so the brick texture continues smoothly between them."
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:580
msgid "World Triplanar"
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:582
msgid ""
"When using triplanar mapping, it is computed in object local space. This "
"option makes it use world space instead."
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:588
msgid "Sampling"
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:591
#: ../../docs/tutorials/audio/audio_effects.rst:122
msgid "Filter"
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:593
msgid ""
"The filtering method for the textures used by the material. See :ref:`this "
"page<class_BaseMaterial3D_property_texture_filter>` for a full list of "
"options and their description."
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:597
msgid "Repeat"
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:599
msgid ""
"if the textures used by the material repeat, and how they repeat. See :ref:"
"`this page<class_BaseMaterial3D_property_texture_repeat>` for a full list of "
"options and their description."
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:603
msgid "Shadows"
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:606
msgid "Do Not Receive Shadows"
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:608
msgid ""
"Makes the object not receive any kind of shadow that would otherwise be cast "
"onto it."
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:612
msgid "Use Shadow to Opacity"
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:614
#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:71
msgid ""
"Lighting modifies the alpha so shadowed areas are opaque and non-shadowed "
"areas are transparent. Useful for overlaying shadows onto a camera feed in "
"AR."
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:618
msgid "Billboard"
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:621
msgid "Billboard Mode"
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:623
msgid ""
"Enables billboard mode for drawing materials. This controls how the object "
"faces the camera:"
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:626
msgid "**Disabled:** Billboard mode is disabled."
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:627
msgid ""
"**Enabled:** Billboard mode is enabled. The object's -Z axis will always "
"face the camera's viewing plane."
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:629
msgid ""
"**Y-Billboard:** The object's X axis will always be aligned with the "
"camera's viewing plane."
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:630
msgid ""
"**Particle Billboard:** Most suited for particle systems, because it allows "
"specifying :ref:`flipbook animation "
"<doc_process_material_properties_animation>`."
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:635
msgid ""
"The **Particles Anim** section is only visible when the billboard mode is "
"**Particle Billboard**."
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:638
msgid "Billboard Keep Scale"
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:640
msgid "Enables scaling a mesh in billboard mode."
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:643
msgid "Grow"
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:645
msgid "Grows the object vertices in the direction pointed by their normals:"
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:649
msgid ""
"This is commonly used to create cheap outlines. Add a second material pass, "
"make it black and unshaded, reverse culling (Cull Front), and add some grow:"
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:655
#: ../../docs/tutorials/shaders/visual_shaders.rst:131
msgid "Transform"
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:658
msgid "Fixed Size"
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:660
msgid ""
"This causes the object to be rendered at the same size no matter the "
"distance. This is useful mostly for indicators (no depth test and high "
"render priority) and some types of billboards."
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:665
msgid "Use Point Size"
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:667
msgid ""
"This option is only effective when the geometry rendered is made of points "
"(generally it's made of triangles when imported from 3D modeling software). "
"If so, then those points can be resized (see below)."
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:672
msgid "Point Size"
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:674
msgid "When drawing points, specify the point size in pixels."
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:677
msgid "Transmission"
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:686
msgid "Proximity and Distance Fade"
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:688
msgid ""
"Godot allows materials to fade by proximity to each other as well as "
"depending on the distance from the viewer. Proximity fade is useful for "
"effects such as soft particles or a mass of water with a smooth blending to "
"the shores."
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:694
msgid ""
"Distance fade is useful for light shafts or indicators that are only present "
"after a given distance."
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:697
msgid ""
"Keep in mind enabling proximity fade or distance fade with **Pixel Alpha** "
"mode enables alpha blending. Alpha blending is more GPU-intensive and can "
"cause transparency sorting issues. Alpha blending also disables many "
"material features such as the ability to cast shadows. To hide a character "
"when they get too close to the camera, consider using **Pixel Dither** or "
"better, **Object Dither** (which is even faster than **Pixel Dither**)."
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:706
#, fuzzy
msgid "Material Settings"
msgstr "Uvod / Početak"

#: ../../docs/tutorials/3d/standard_material_3d.rst:709
msgid "Render priority"
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:711
msgid ""
"The rendering order of objects can be changed, although this is mostly "
"useful for transparent objects (or opaque objects that perform depth draw "
"but no color draw, such as cracks on the floor)."
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:716
msgid "Next Pass"
msgstr ""

#: ../../docs/tutorials/3d/standard_material_3d.rst:718
msgid ""
"Sets the material to be used for the next pass. This renders the object "
"again with a different material."
msgstr ""

#: ../../docs/tutorials/3d/lights_and_shadows.rst:4
msgid "3D lights and shadows"
msgstr ""

#: ../../docs/tutorials/3d/lights_and_shadows.rst:9
msgid ""
"Light sources emit light that mixes with the materials and produces a "
"visible result. Light can come from several types of sources in a scene:"
msgstr ""

#: ../../docs/tutorials/3d/lights_and_shadows.rst:12
msgid ""
"From the material itself, in the form of the emission color (though it does "
"not affect nearby objects unless baked or screen-space indirect lighting is "
"enabled)."
msgstr ""

#: ../../docs/tutorials/3d/lights_and_shadows.rst:14
msgid "Light nodes: DirectionalLight3D, OmniLight3D and SpotLight3D."
msgstr ""

#: ../../docs/tutorials/3d/lights_and_shadows.rst:15
msgid ""
"Ambient light in the :ref:`Environment <class_Environment>` or :ref:"
"`doc_reflection_probes`."
msgstr ""

#: ../../docs/tutorials/3d/lights_and_shadows.rst:17
msgid ""
"Global illumination (:ref:`LightmapGI <doc_using_lightmap_gi>`, :ref:"
"`VoxelGI <doc_using_voxel_gi>` or :ref:`SDFGI <doc_using_sdfgi>`)."
msgstr ""

#: ../../docs/tutorials/3d/lights_and_shadows.rst:20
msgid ""
"The emission color is a material property. You can read more about it in "
"the :ref:`doc_standard_material_3d` tutorial."
msgstr ""

#: ../../docs/tutorials/3d/lights_and_shadows.rst:25
#, fuzzy
msgid ""
"You can compare various types of lights in action using the `3D Lights and "
"Shadows demo project <https://github.com/godotengine/godot-demo-projects/"
"tree/master/3d/lights_and_shadows>`__."
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati različite Godo demo projekte "
"`Godot demo projects <https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/tutorials/3d/lights_and_shadows.rst:29
msgid "Light nodes"
msgstr ""

#: ../../docs/tutorials/3d/lights_and_shadows.rst:31
msgid ""
"There are three types of light nodes: :ref:`class_DirectionalLight3D`, :ref:"
"`class_OmniLight3D` and :ref:`class_SpotLight3D`. Let's take a look at the "
"common parameters for lights:"
msgstr ""

#: ../../docs/tutorials/3d/lights_and_shadows.rst:37
msgid "Each property has a specific function:"
msgstr ""

#: ../../docs/tutorials/3d/lights_and_shadows.rst:39
msgid "**Color:** Base color for emitted light."
msgstr ""

#: ../../docs/tutorials/3d/lights_and_shadows.rst:40
msgid ""
"**Energy:** Energy multiplier. This is useful for saturating lights or "
"working with :ref:`doc_high_dynamic_range`."
msgstr ""

#: ../../docs/tutorials/3d/lights_and_shadows.rst:41
msgid ""
"**Indirect Energy:** Secondary multiplier used with indirect light (light "
"bounces). This works with :ref:`doc_using_lightmap_gi`, VoxelGI or SDFGI."
msgstr ""

#: ../../docs/tutorials/3d/lights_and_shadows.rst:42
msgid ""
"**Volumetric Fog Energy:** Secondary multiplier used with volumetric fog. "
"This only has an effect when volumetric fog is enabled."
msgstr ""

#: ../../docs/tutorials/3d/lights_and_shadows.rst:43
msgid ""
"**Negative:** Light becomes subtractive instead of additive. It's sometimes "
"useful to manually compensate some dark corners."
msgstr ""

#: ../../docs/tutorials/3d/lights_and_shadows.rst:44
msgid ""
"**Specular:** Affects the intensity of the specular blob in objects affected "
"by this light. At zero, this light becomes a pure diffuse light."
msgstr ""

#: ../../docs/tutorials/3d/lights_and_shadows.rst:45
msgid ""
"**Bake Mode:** Sets the bake mode for the light. See :ref:"
"`doc_using_lightmap_gi`."
msgstr ""

#: ../../docs/tutorials/3d/lights_and_shadows.rst:46
msgid ""
"**Cull Mask:** Objects that are in the selected layers below will be "
"affected by this light. Note that objects disabled via this cull mask will "
"still cast shadows. If you don't want disabled objects to cast shadows, "
"adjust the **Cast Shadow** property on the GeometryInstance3D to the desired "
"value."
msgstr ""

#: ../../docs/tutorials/3d/lights_and_shadows.rst:53
msgid ""
"See :ref:`doc_physical_light_and_camera_units` if you wish to use real world "
"units to configure your lights' intensity and color temperature."
msgstr ""

#: ../../docs/tutorials/3d/lights_and_shadows.rst:57
msgid "Light number limits"
msgstr ""

#: ../../docs/tutorials/3d/lights_and_shadows.rst:59
msgid ""
"When using the Forward+ renderer, Godot uses a *clustering* approach for "
"real-time lighting. As many lights as desired can be added (as long as "
"performance allows). However, there's still a default limit of 512 "
"*clustered elements* that can be present in the current camera view. A "
"clustered element is an omni light, a spot light, a :ref:`decal "
"<doc_using_decals>` or a :ref:`reflection probe <doc_reflection_probes>`. "
"This limit can be increased by adjusting the **Rendering > Limits > Cluster "
"Builder > Max Clustered Elements** advanced project setting."
msgstr ""

#: ../../docs/tutorials/3d/lights_and_shadows.rst:68
msgid ""
"When using the Forward Mobile renderer, there is a limitation of 8 "
"OmniLights + 8 SpotLights per mesh resource. There is also a limit of 256 "
"OmniLights + 256 SpotLights that can be rendered in the current camera view. "
"These limits currently cannot be changed."
msgstr ""

#: ../../docs/tutorials/3d/lights_and_shadows.rst:73
msgid ""
"When using the Compatibility renderer, up to 8 OmniLights + 8 SpotLights can "
"be rendered per mesh resource. This limit can be increased in the advanced "
"Project Settings by adjusting **Rendering > Limits > OpenGL > Max Renderable "
"Lights** and/or **Rendering > Limits > OpenGL > Max Lights Per Object** at "
"the cost of performance and longer shader compilation times. The limit can "
"also be decreased to reduce shader compilation times and improve performance "
"slightly."
msgstr ""

#: ../../docs/tutorials/3d/lights_and_shadows.rst:80
msgid ""
"With all rendering methods, up to 8 DirectionalLights can be visible at a "
"time. However, each additional DirectionalLight with shadows enabled will "
"reduce the effective shadow resolution of each DirectionalLight. This is "
"because directional shadow atlas is shared between all lights."
msgstr ""

#: ../../docs/tutorials/3d/lights_and_shadows.rst:85
msgid ""
"If the rendering limit is exceeded, lights will start popping in and out "
"during camera movement, which can be distracting. Enabling **Distance Fade** "
"on light nodes can help reduce this issue while also improving performance. "
"Splitting your meshes into smaller portions can also help, especially for "
"level geometry (which also improves culling efficiency)."
msgstr ""

#: ../../docs/tutorials/3d/lights_and_shadows.rst:91
msgid ""
"If you need to render more lights than possible in a given rendering "
"backend, consider using :ref:`baked lightmaps <doc_using_lightmap_gi>` with "
"lights' bake mode set to **Static**. This allows lights to be fully baked, "
"which also makes them much faster to render. You can also use emissive "
"materials with any :ref:`global illumination "
"<doc_introduction_to_global_illumination>` technique as a replacement for "
"light nodes that emit light over a large area."
msgstr ""

#: ../../docs/tutorials/3d/lights_and_shadows.rst:99
#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:484
msgid "Shadow mapping"
msgstr ""

#: ../../docs/tutorials/3d/lights_and_shadows.rst:101
msgid ""
"Lights can optionally cast shadows. This gives them greater realism (light "
"does not reach occluded areas), but it can incur a bigger performance cost. "
"There is a list of generic shadow parameters, each also has a specific "
"function:"
msgstr ""

#: ../../docs/tutorials/3d/lights_and_shadows.rst:105
msgid "**Enabled:** Check to enable shadow mapping in this light."
msgstr ""

#: ../../docs/tutorials/3d/lights_and_shadows.rst:106
msgid ""
"**Opacity:** Areas occluded are darkened by this opacity factor. Shadows are "
"fully opaque by default, but this can be changed to make shadows translucent "
"for a given light."
msgstr ""

#: ../../docs/tutorials/3d/lights_and_shadows.rst:109
msgid ""
"**Bias:** When this parameter is too low, self-shadowing occurs. When too "
"high, shadows separate from the casters. Tweak to what works best for you."
msgstr ""

#: ../../docs/tutorials/3d/lights_and_shadows.rst:111
msgid ""
"**Normal Bias:** When this parameter is too low, self-shadowing occurs. When "
"too high, shadows appear misaligned from the casters. Tweak to what works "
"best for you."
msgstr ""

#: ../../docs/tutorials/3d/lights_and_shadows.rst:113
msgid ""
"**Transmittance Bias:** When this parameter is too low, self-shadowing "
"occurs on materials that have transmittance enabled. When too high, shadows "
"will not affect materials that have transmittance enabled consistently. "
"Tweak to what works best for you."
msgstr ""

#: ../../docs/tutorials/3d/lights_and_shadows.rst:117
msgid ""
"**Reverse Cull Face:** Some scenes work better when shadow mapping is "
"rendered with face-culling inverted."
msgstr ""

#: ../../docs/tutorials/3d/lights_and_shadows.rst:119
msgid ""
"**Blur:** Multiplies the shadow blur radius for this light. This works with "
"both traditional shadow mapping and contact-hardening shadows (lights with "
"**Angular Distance** or **Size** greater than ``0.0``). Higher values result "
"in softer shadows, which will also appear to be more temporally stable for "
"moving objects. The downside of increasing shadow blur is that it will make "
"the grainy pattern used for filtering more noticeable. See also :ref:"
"`doc_lights_and_shadows_shadow_filter_mode`."
msgstr ""

#: ../../docs/tutorials/3d/lights_and_shadows.rst:130
#, fuzzy
msgid "Tweaking shadow bias"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/3d/lights_and_shadows.rst:132
msgid ""
"Below is an image of what tweaking bias looks like. Default values work for "
"most cases, but in general, it depends on the size and complexity of "
"geometry."
msgstr ""

#: ../../docs/tutorials/3d/lights_and_shadows.rst:135
msgid ""
"If the **Shadow Bias** or **Shadow Normal Bias** is set too low for a given "
"light, the shadow will be \"smeared\" onto the objects. This will cause the "
"light's intended appearance to darken, and is called *shadow acne*:"
msgstr ""

#: ../../docs/tutorials/3d/lights_and_shadows.rst:141
msgid ""
"On the other hand, if the **Shadow Bias** or **Shadow Normal Bias** is set "
"too high for a given light, the shadow may appear to be disconnected from "
"the object. This is called *peter-panning*:"
msgstr ""

#: ../../docs/tutorials/3d/lights_and_shadows.rst:147
msgid ""
"In general, increasing **Shadow Normal Bias** is preferred over increasing "
"**Shadow Bias**. Increasing **Shadow Normal Bias** does not cause as much "
"peter-panning as increasing **Shadow Bias**, but it can still resolve most "
"shadow acne issues efficiently. The downside of increasing **Shadow Normal "
"Bias** is that it can make shadows appear thinner for certain objects."
msgstr ""

#: ../../docs/tutorials/3d/lights_and_shadows.rst:153
msgid ""
"Any sort of bias issues can be fixed by :ref:`increasing the shadow map "
"resolution <doc_lights_and_shadows_balancing_performance_and_quality>`, at "
"the cost of decreased performance."
msgstr ""

#: ../../docs/tutorials/3d/lights_and_shadows.rst:159
msgid ""
"Tweaking shadow mapping settings is an art – there are no \"one size fits "
"all\" settings. To achieve the best visuals, you may need to use different "
"shadow bias values on a per-light basis."
msgstr ""

#: ../../docs/tutorials/3d/lights_and_shadows.rst:163
msgid ""
"**Note on Appearance Changes**: When enabling shadows on a light, be aware "
"that the light's appearance might change compared to when it's rendered "
"without shadows in the compatibility renderer. Due to limitations with older "
"mobile devices, shadows are implemented using a multi-pass rendering "
"approach so lights with shadows are rendered in sRGB space instead of linear "
"space. This change in rendering space can sometimes drastically alter the "
"light's appearance. To achieve a similar appearance to an unshadowed light, "
"you may need to adjust the light's energy setting."
msgstr ""

#: ../../docs/tutorials/3d/lights_and_shadows.rst:173
msgid ""
"This is the most common type of light and represents a light source very far "
"away (such as the sun). It is also the cheapest light to compute and should "
"be used whenever possible (although it's not the cheapest shadow-map to "
"compute, but more on that later)."
msgstr ""

#: ../../docs/tutorials/3d/lights_and_shadows.rst:178
msgid ""
"Directional light models an infinite number of parallel light rays covering "
"the whole scene. The directional light node is represented by a big arrow "
"which indicates the direction of the light rays. However, the position of "
"the node does not affect the lighting at all and can be anywhere."
msgstr ""

#: ../../docs/tutorials/3d/lights_and_shadows.rst:185
msgid ""
"Every face whose front-side is hit by the light rays is lit, while the "
"others stay dark. Unlike most other light types, directional lights don't "
"have specific parameters."
msgstr ""

#: ../../docs/tutorials/3d/lights_and_shadows.rst:189
msgid ""
"The directional light also offers a **Angular Distance** property, which "
"determines the light's angular size in degrees. Increasing this above "
"``0.0`` will make shadows softer at greater distances from the caster, while "
"also affecting the sun's appearance in procedural sky materials. This is "
"called a *contact-hardening* shadow (also known as PCSS)."
msgstr ""

#: ../../docs/tutorials/3d/lights_and_shadows.rst:195
msgid ""
"For reference, the angular distance of the Sun viewed from the Earth is "
"approximately ``0.5``. This kind of shadow is expensive, so check the "
"recommendations in :ref:`doc_lights_and_shadows_pcss_recommendations` if "
"setting this value above ``0.0`` on lights with shadows enabled."
msgstr ""

#: ../../docs/tutorials/3d/lights_and_shadows.rst:201
msgid "Directional shadow mapping"
msgstr ""

#: ../../docs/tutorials/3d/lights_and_shadows.rst:203
msgid ""
"To compute shadow maps, the scene is rendered (only depth) from an "
"orthogonal point of view that covers the whole scene (or up to the max "
"distance). There is, however, a problem with this approach because objects "
"closer to the camera receive low-resolution shadows that may appear blocky."
msgstr ""

#: ../../docs/tutorials/3d/lights_and_shadows.rst:208
msgid ""
"To fix this, a technique named *Parallel Split Shadow Maps* (PSSM) is used. "
"This splits the view frustum in 2 or 4 areas. Each area gets its own shadow "
"map. This allows small areas close to the viewer to have the same shadow "
"resolution as a huge, far-away area. When shadows are enabled for "
"DirectionalLight3D, the default shadow mode is PSSM with 4 splits. In "
"scenarios where an object is large enough to appear in all four splits, it "
"results in increased draw calls. Specifically, such an object will be "
"rendered five times in total: once for each of the four shadow splits and "
"once for the final scene rendering. This can impact performance, "
"understanding this behavior is important for optimizing your scene and "
"managing performance expectations."
msgstr ""

#: ../../docs/tutorials/3d/lights_and_shadows.rst:220
msgid "With this, shadows become more detailed:"
msgstr ""

#: ../../docs/tutorials/3d/lights_and_shadows.rst:224
msgid "To control PSSM, a number of parameters are exposed:"
msgstr ""

#: ../../docs/tutorials/3d/lights_and_shadows.rst:228
msgid ""
"Each split distance is controlled relative to the camera far (or shadow "
"**Max Distance** if greater than ``0.0``). ``0.0`` is the eye position and "
"``1.0`` is where the shadow ends at a distance. Splits are in-between. "
"Default values generally work well, but tweaking the first split a bit is "
"common to give more detail to close objects (like a character in a third-"
"person game)."
msgstr ""

#: ../../docs/tutorials/3d/lights_and_shadows.rst:234
msgid ""
"Always make sure to set a shadow **Max Distance** according to what the "
"scene needs. A lower maximum distance will result in better-looking shadows "
"and better performance, as fewer objects will need to be included in shadow "
"rendering. You can also adjust **Fade Start** to control how aggressive the "
"shadow fade-out should be at a distance. For scenes where the **Max "
"Distance** fully covers the scene at any given camera position, you can "
"increase **Fade Start** to ``1.0`` to prevent the shadow from fading at a "
"distance. This should not be done in scenes where **Max Distance** doesn't "
"fully cover the scene, as the shadow will appear to be suddenly cut off at a "
"distance."
msgstr ""

#: ../../docs/tutorials/3d/lights_and_shadows.rst:244
msgid ""
"Sometimes, the transition between a split and the next can look bad. To fix "
"this, the **Blend Splits** option can be turned on, which sacrifices detail "
"and performance in exchange for smoother transitions:"
msgstr ""

#: ../../docs/tutorials/3d/lights_and_shadows.rst:250
msgid ""
"The **Shadow > Normal Bias** parameter can be used to fix special cases of "
"self-shadowing when objects are perpendicular to the light. The only "
"downside is that it makes the shadow a bit thinner. Consider increasing "
"**Shadow > Normal Bias** before increasing **Shadow > Bias** in most "
"situations."
msgstr ""

#: ../../docs/tutorials/3d/lights_and_shadows.rst:255
msgid ""
"Lastly, **Pancake Size** is a property that can be adjusted to fix missing "
"shadows when using large objects with unsubdivided meshes. Only change this "
"value if you notice missing shadows that are not related to shadow biasing "
"issues."
msgstr ""

#: ../../docs/tutorials/3d/lights_and_shadows.rst:261
msgid "Omni light"
msgstr ""

#: ../../docs/tutorials/3d/lights_and_shadows.rst:263
msgid ""
"Omni light is a point source that emits light spherically in all directions "
"up to a given radius."
msgstr ""

#: ../../docs/tutorials/3d/lights_and_shadows.rst:268
msgid ""
"In real life, light attenuation is an inverse function, which means omni "
"lights don't have a radius. This is a problem because it means computing "
"several omni lights would become demanding."
msgstr ""

#: ../../docs/tutorials/3d/lights_and_shadows.rst:271
msgid ""
"To solve this, a **Range** parameter is introduced together with an "
"attenuation function."
msgstr ""

#: ../../docs/tutorials/3d/lights_and_shadows.rst:275
msgid ""
"These two parameters allow tweaking how this works visually in order to find "
"aesthetically pleasing results."
msgstr ""

#: ../../docs/tutorials/3d/lights_and_shadows.rst:279
msgid ""
"A **Size** parameter is also available in OmniLight3D. Increasing this value "
"will make the light fade out slower and shadows appear blurrier when far "
"away from the caster. This can be used to simulate area lights to an extent. "
"This is called a *contact-hardening* shadow (also known as PCSS). This kind "
"of shadow is expensive, so check the recommendations in :ref:"
"`doc_lights_and_shadows_pcss_recommendations` if setting this value above "
"``0.0`` on lights with shadows enabled."
msgstr ""

#: ../../docs/tutorials/3d/lights_and_shadows.rst:290
msgid "Omni shadow mapping"
msgstr ""

#: ../../docs/tutorials/3d/lights_and_shadows.rst:292
msgid ""
"Omni light shadow mapping is relatively straightforward. The main issue that "
"needs to be considered is the algorithm used to render it."
msgstr ""

#: ../../docs/tutorials/3d/lights_and_shadows.rst:295
msgid ""
"Omni Shadows can be rendered as either **Dual Paraboloid** or **Cube** "
"mapped. **Dual Parabolid** renders quickly, but can cause deformations, "
"while **Cube** is more correct, but slower. The default is **Cube**, but "
"consider changing it to **Dual Parabolid** for lights where it doesn't make "
"much of a visual difference."
msgstr ""

#: ../../docs/tutorials/3d/lights_and_shadows.rst:303
msgid ""
"If the objects being rendered are mostly irregular and subdivided, Dual "
"Paraboloid is usually enough. In any case, as these shadows are cached in a "
"shadow atlas (more on that at the end), it may not make a difference in "
"performance for most scenes."
msgstr ""

#: ../../docs/tutorials/3d/lights_and_shadows.rst:308
msgid ""
"Omni lights with shadows enabled can make use of projectors. The projector "
"texture will *multiply* the light's color by the color at a given point on "
"the texture. As a result, lights will usually appear to be darker once a "
"projector texture is assigned; you can increase **Energy** to compensate for "
"this."
msgstr ""

#: ../../docs/tutorials/3d/lights_and_shadows.rst:313
msgid ""
"Omni light projector textures require a special 360° panorama mapping, "
"similar to :ref:`class_PanoramaSkyMaterial` textures."
msgstr ""

#: ../../docs/tutorials/3d/lights_and_shadows.rst:316
#: ../../docs/tutorials/3d/lights_and_shadows.rst:359
msgid "With the projector texture below, the following result is obtained:"
msgstr ""

#: ../../docs/tutorials/3d/lights_and_shadows.rst:324
msgid ""
"If you've acquired omni projectors in the form of cubemap images, you can "
"use `this web-based conversion tool <https://danilw.github.io/GLSL-howto/"
"cubemap_to_panorama_js/cubemap_to_panorama.html>`__ to convert them to a "
"single panorama image."
msgstr ""

#: ../../docs/tutorials/3d/lights_and_shadows.rst:329
msgid "Spot light"
msgstr ""

#: ../../docs/tutorials/3d/lights_and_shadows.rst:331
msgid ""
"Spot lights are similar to omni lights, except they emit light only into a "
"cone (or \"cutoff\"). They are useful to simulate flashlights, car lights, "
"reflectors, spots, etc. This type of light is also attenuated towards the "
"opposite direction it points to."
msgstr ""

#: ../../docs/tutorials/3d/lights_and_shadows.rst:336
msgid ""
"Spot lights share the same **Range**, **Attenuation** and **Size** as "
"OmniLight3D, and add two extra parameters:"
msgstr ""

#: ../../docs/tutorials/3d/lights_and_shadows.rst:339
msgid "**Angle:** The aperture angle of the light."
msgstr ""

#: ../../docs/tutorials/3d/lights_and_shadows.rst:340
msgid ""
"**Angle Attenuation:** The cone attenuation, which helps soften the cone "
"borders."
msgstr ""

#: ../../docs/tutorials/3d/lights_and_shadows.rst:343
msgid "Spot shadow mapping"
msgstr ""

#: ../../docs/tutorials/3d/lights_and_shadows.rst:345
msgid ""
"Spots feature the same parameters as omni lights for shadow mapping. "
"Rendering spot shadow maps is significantly faster compared to omni lights, "
"as only one shadow texture needs to be rendered (instead of rendering 6 "
"faces, or 2 in dual parabolid mode)."
msgstr ""

#: ../../docs/tutorials/3d/lights_and_shadows.rst:350
msgid ""
"Spot lights with shadows enabled can make use of projectors. The projector "
"texture will *multiply* the light's color by the color at a given point on "
"the texture. As a result, lights will usually appear to be darker once a "
"projector texture is assigned; you can increase **Energy** to compensate for "
"this."
msgstr ""

#: ../../docs/tutorials/3d/lights_and_shadows.rst:355
msgid ""
"Unlike omni light projectors, a spot light projector texture doesn't need to "
"follow a special format to look correct. It will be mapped in a way similar "
"to a :ref:`decal <doc_using_decals>`."
msgstr ""

#: ../../docs/tutorials/3d/lights_and_shadows.rst:367
msgid ""
"Spot lights with wide angles will have lower-quality shadows than spot "
"lights with narrow angles, as the shadow map is spread over a larger "
"surface. At angles wider than 89 degrees, spot light shadows will stop "
"working entirely. If you need shadows for wider lights, use an omni light "
"instead."
msgstr ""

#: ../../docs/tutorials/3d/lights_and_shadows.rst:376
msgid "Shadow atlas"
msgstr ""

#: ../../docs/tutorials/3d/lights_and_shadows.rst:378
msgid ""
"Unlike Directional lights, which have their own shadow texture, omni and "
"spot lights are assigned to slots of a shadow atlas. This atlas can be "
"configured in the advanced Project Settings (**Rendering > Lights And "
"Shadows > Positional Shadow**)."
msgstr ""

#: ../../docs/tutorials/3d/lights_and_shadows.rst:382
msgid ""
"The resolution applies to the whole shadow atlas. This atlas is divided into "
"four quadrants:"
msgstr ""

#: ../../docs/tutorials/3d/lights_and_shadows.rst:386
msgid ""
"Each quadrant can be subdivided to allocate any number of shadow maps; the "
"following is the default subdivision:"
msgstr ""

#: ../../docs/tutorials/3d/lights_and_shadows.rst:390
msgid "The shadow atlas allocates space as follows:"
msgstr ""

#: ../../docs/tutorials/3d/lights_and_shadows.rst:392
msgid ""
"The biggest shadow map size (when no subdivision is used) represents a light "
"the size of the screen (or bigger)."
msgstr ""

#: ../../docs/tutorials/3d/lights_and_shadows.rst:393
msgid ""
"Subdivisions (smaller maps) represent shadows for lights that are further "
"away from view and proportionally smaller."
msgstr ""

#: ../../docs/tutorials/3d/lights_and_shadows.rst:395
msgid "Every frame, the following procedure is performed for all lights:"
msgstr ""

#: ../../docs/tutorials/3d/lights_and_shadows.rst:397
msgid ""
"Check if the light is on a slot of the right size. If not, re-render it and "
"move it to a larger/smaller slot."
msgstr ""

#: ../../docs/tutorials/3d/lights_and_shadows.rst:398
msgid ""
"Check if any object affecting the shadow map has changed. If it did, re-"
"render the light."
msgstr ""

#: ../../docs/tutorials/3d/lights_and_shadows.rst:399
msgid ""
"If neither of the above has happened, nothing is done, and the shadow is "
"left untouched."
msgstr ""

#: ../../docs/tutorials/3d/lights_and_shadows.rst:401
msgid ""
"If the slots in a quadrant are full, lights are pushed back to smaller "
"slots, depending on size and distance. If all slots in all quadrants are "
"full, some lights will not be able to render shadows even if shadows are "
"enabled on them."
msgstr ""

#: ../../docs/tutorials/3d/lights_and_shadows.rst:405
msgid ""
"The default shadow allocation strategy allows rendering up to 88 lights with "
"shadows enabled in the camera frustum (4 + 4 + 16 + 64):"
msgstr ""

#: ../../docs/tutorials/3d/lights_and_shadows.rst:408
msgid "The first and most detailed quadrant can store 4 shadows."
msgstr ""

#: ../../docs/tutorials/3d/lights_and_shadows.rst:409
msgid "The second quadrant can store 4 other shadows."
msgstr ""

#: ../../docs/tutorials/3d/lights_and_shadows.rst:410
msgid "The third quadrant can store 16 shadows, with less detail."
msgstr ""

#: ../../docs/tutorials/3d/lights_and_shadows.rst:411
msgid ""
"The fourth and least detailed quadrant can store 64 shadows, with even less "
"detail."
msgstr ""

#: ../../docs/tutorials/3d/lights_and_shadows.rst:413
msgid ""
"Using a higher number of shadows per quadrant allows supporting a greater "
"amount of total lights with shadows enabled, while also improving "
"performance (as shadows will be rendered at a lower resolution for each "
"light). However, increasing the number of shadows per quadrant comes at the "
"cost of lower shadow quality."
msgstr ""

#: ../../docs/tutorials/3d/lights_and_shadows.rst:419
msgid ""
"In some cases, you may want to use a different allocation strategy. For "
"example, in a top-down game where all lights are around the same size, you "
"may want to set all quadrants to have the same subdivision so that all "
"lights have shadows of similar quality level."
msgstr ""

#: ../../docs/tutorials/3d/lights_and_shadows.rst:427
#: ../../docs/tutorials/3d/volumetric_fog.rst:133
msgid "Balancing performance and quality"
msgstr ""

#: ../../docs/tutorials/3d/lights_and_shadows.rst:429
msgid ""
"Shadow rendering is a critical topic in 3D rendering performance. It's "
"important to make the right choices here to avoid creating bottlenecks."
msgstr ""

#: ../../docs/tutorials/3d/lights_and_shadows.rst:432
msgid ""
"Directional shadow quality settings can be changed at run-time by calling "
"the appropriate :ref:`class_RenderingServer` methods."
msgstr ""

#: ../../docs/tutorials/3d/lights_and_shadows.rst:435
msgid ""
"Positional (omni/spot) shadow quality settings can be changed at run-time on "
"the root :ref:`class_Viewport`."
msgstr ""

#: ../../docs/tutorials/3d/lights_and_shadows.rst:439
msgid "Shadow map size"
msgstr ""

#: ../../docs/tutorials/3d/lights_and_shadows.rst:441
msgid ""
"High shadow resolutions result in sharper shadows, but at a significant "
"performance cost. It should also be noted that *sharper shadows are not "
"always more realistic*. In most cases, this should be kept at its default "
"value of ``4096`` or decreased to ``2048`` for low-end GPUs."
msgstr ""

#: ../../docs/tutorials/3d/lights_and_shadows.rst:446
msgid ""
"If positional shadows become too blurry after decreasing the shadow map "
"size, you can counteract this by adjusting the :ref:`shadow atlas "
"<doc_lights_and_shadows_shadow_atlas>` quadrants to contain fewer shadows. "
"This will allow each shadow to be rendered at a higher resolution."
msgstr ""

#: ../../docs/tutorials/3d/lights_and_shadows.rst:454
msgid "Shadow filter mode"
msgstr ""

#: ../../docs/tutorials/3d/lights_and_shadows.rst:456
msgid ""
"Several shadow map quality settings can be chosen here. The default **Soft "
"Low** is a good balance between performance and quality for scenes with "
"detailed textures, as the texture detail will help make the dithering "
"pattern less noticeable."
msgstr ""

#: ../../docs/tutorials/3d/lights_and_shadows.rst:460
msgid ""
"However, in projects with less detailed textures, the shadow dithering "
"pattern may be more visible. To hide this pattern, you can either enable :"
"ref:`doc_3d_antialiasing_taa`, :ref:`doc_3d_antialiasing_fsr2`, :ref:"
"`doc_3d_antialiasing_fxaa`, or increase the shadow filter quality to **Soft "
"Medium** or higher."
msgstr ""

#: ../../docs/tutorials/3d/lights_and_shadows.rst:466
msgid ""
"The **Soft Very Low** setting will automatically decrease shadow blur to "
"make artifacts from the low sample count less visible. Conversely, the "
"**Soft High** and **Soft Ultra** settings will automatically increase shadow "
"blur to better make use of the increased sample count."
msgstr ""

#: ../../docs/tutorials/3d/lights_and_shadows.rst:474
msgid "16-bits versus 32-bit"
msgstr ""

#: ../../docs/tutorials/3d/lights_and_shadows.rst:476
msgid ""
"By default, Godot uses 16-bit depth textures for shadow map rendering. This "
"is recommended in most cases as it performs better without a noticeable "
"difference in quality."
msgstr ""

#: ../../docs/tutorials/3d/lights_and_shadows.rst:480
msgid ""
"If **16 Bits** is disabled, 32-bit depth textures will be used instead. This "
"can result in less artifacting in large scenes and large lights with shadows "
"enabled. However, the difference is often barely visible, yet this can have "
"a significant performance cost."
msgstr ""

#: ../../docs/tutorials/3d/lights_and_shadows.rst:486
msgid "Light/shadow distance fade"
msgstr ""

#: ../../docs/tutorials/3d/lights_and_shadows.rst:488
msgid ""
"OmniLight3D and SpotLight3D offer several properties to hide distant lights. "
"This can improve performance significantly in large scenes with dozens of "
"lights or more."
msgstr ""

#: ../../docs/tutorials/3d/lights_and_shadows.rst:492
msgid ""
"**Enabled:** Controls whether distance fade (a form of :abbr:`LOD (Level of "
"Detail)`) is enabled. The light will fade out over **Begin + Length**, after "
"which it will be culled and not sent to the shader at all. Use this to "
"reduce the number of active lights in a scene and thus improve performance."
msgstr ""

#: ../../docs/tutorials/3d/lights_and_shadows.rst:496
msgid ""
"**Begin:** The distance from the camera at which the light begins to fade "
"away (in 3D units)."
msgstr ""

#: ../../docs/tutorials/3d/lights_and_shadows.rst:498
msgid ""
"**Shadow:** The distance from the camera at which the shadow begins to fade "
"away (in 3D units). This can be used to fade out shadows sooner compared to "
"the light, further improving performance. Only available if shadows are "
"enabled for the light."
msgstr ""

#: ../../docs/tutorials/3d/lights_and_shadows.rst:501
msgid ""
"**Length:** The distance over which the light and shadow fades (in 3D "
"units). The light becomes slowly more transparent over this distance and is "
"completely invisible at the end. Higher values result in a smoother fade-out "
"transition, which is more suited when the camera moves fast."
msgstr ""

#: ../../docs/tutorials/3d/lights_and_shadows.rst:509
msgid "PCSS recommendations"
msgstr ""

#: ../../docs/tutorials/3d/lights_and_shadows.rst:511
msgid ""
"Percentage-closer soft shadows (PCSS) provide a more realistic shadow "
"mapping appearance, with the penumbra size varying depending on the distance "
"between the caster and the surface receiving the shadow. This comes at a "
"high performance cost, especially for directional lights."
msgstr ""

#: ../../docs/tutorials/3d/lights_and_shadows.rst:516
msgid "To avoid performance issues, it's recommended to:"
msgstr ""

#: ../../docs/tutorials/3d/lights_and_shadows.rst:518
msgid ""
"Only use a handful of lights with PCSS shadows enabled at a given time. The "
"effect is generally most visible on large, bright lights. Secondary light "
"sources that are more faint usually don't benefit much from using PCSS "
"shadows."
msgstr ""

#: ../../docs/tutorials/3d/lights_and_shadows.rst:522
msgid ""
"Provide a setting for users to disable PCSS shadows. On directional lights, "
"this can be done by setting the DirectionalLight3D's "
"``light_angular_distance`` property to ``0.0`` in a script. On positional "
"lights, this can be done by setting the OmniLight3D or SpotLight3D's "
"``light_size`` property to ``0.0`` in a script."
msgstr ""

#: ../../docs/tutorials/3d/lights_and_shadows.rst:529
#, fuzzy
msgid "Projector filter mode"
msgstr "Uvod / Početak"

#: ../../docs/tutorials/3d/lights_and_shadows.rst:531
msgid ""
"The way projectors are rendered also has an impact on performance. The "
"**Rendering > Textures > Light Projectors > Filter** advanced project "
"setting lets you control how projector textures should be filtered. "
"**Nearest/Linear** do not use mipmaps, which makes them faster to render. "
"However, projectors will look grainy at distance. **Nearest/Linear Mipmaps** "
"will look smoother at a distance, but projectors will look blurry when "
"viewed from oblique angles. This can be resolved by using **Nearest/Linear "
"Mipmaps Anisotropic**, which is the highest-quality mode but also the most "
"expensive."
msgstr ""

#: ../../docs/tutorials/3d/lights_and_shadows.rst:540
msgid ""
"If your project has a pixel art style, consider setting the filter to one of "
"the **Nearest** values so that projectors use nearest-neighbor filtering. "
"Otherwise, stick to **Linear**."
msgstr ""

#: ../../docs/tutorials/3d/using_decals.rst:4
#, fuzzy
msgid "Using decals"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/3d/using_decals.rst:8
msgid ""
"Decals are only supported in the Clustered Forward and Forward Mobile "
"rendering backends, not the Compatibility backend."
msgstr ""

#: ../../docs/tutorials/3d/using_decals.rst:11
msgid ""
"If using the Compatibility backend, consider using Sprite3D as an "
"alternative for projecting decals onto (mostly) flat surfaces."
msgstr ""

#: ../../docs/tutorials/3d/using_decals.rst:14
msgid ""
"Decals are projected textures that apply on opaque or transparent surfaces "
"in 3D. This projection happens in real-time and doesn't rely on mesh "
"generation. This allows you to move decals every frame with only a small "
"performance impact, even when applied on complex meshes."
msgstr ""

#: ../../docs/tutorials/3d/using_decals.rst:19
msgid ""
"While decals cannot add actual geometry detail onto the projected surface, "
"decals can still make use of physically-based rendering to provide similar "
"properties to full-blown :abbr:`PBR (Physically-Based Rendering)` materials."
msgstr ""

#: ../../docs/tutorials/3d/using_decals.rst:23
#: ../../docs/tutorials/3d/volumetric_fog.rst:18
#: ../../docs/tutorials/3d/mesh_lod.rst:9
#: ../../docs/tutorials/3d/visibility_ranges.rst:10
#: ../../docs/tutorials/3d/occlusion_culling.rst:9
msgid "On this page, you'll learn:"
msgstr ""

#: ../../docs/tutorials/3d/using_decals.rst:25
msgid "How to set up decals in the 3D editor."
msgstr ""

#: ../../docs/tutorials/3d/using_decals.rst:26
msgid ""
"How to create decals during gameplay in a 3D scene (such as bullet impacts)."
msgstr ""

#: ../../docs/tutorials/3d/using_decals.rst:27
msgid "How to balance decal configuration between performance and quality."
msgstr ""

#: ../../docs/tutorials/3d/using_decals.rst:31
#, fuzzy
msgid ""
"The Godot demo projects repository contains a `3D decals demo <https://"
"github.com/godotengine/godot-demo-projects/tree/4.0-dev/3d/decals>`__."
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati različite Godo demo projekte "
"`Godot demo projects <https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/tutorials/3d/using_decals.rst:34
msgid ""
"If you're looking to write arbitrary 3D text on top of a surface, use :ref:"
"`doc_3d_text` placed close to a surface instead of a Decal node."
msgstr ""

#: ../../docs/tutorials/3d/using_decals.rst:38
#: ../../docs/tutorials/export/exporting_pcks.rst:7
msgid "Use cases"
msgstr ""

#: ../../docs/tutorials/3d/using_decals.rst:41
msgid "Static decoration"
msgstr ""

#: ../../docs/tutorials/3d/using_decals.rst:43
msgid ""
"Sometimes, the fastest way to add texture detail to a scene is to use "
"decals. This is especially the case for organic detail, such as patches of "
"dirt or sand scattered on a large surface. Decals can help break up texture "
"repetition in scenes and make patterns look more natural. On a smaller "
"scale, decals can also be used to create detail variations for objects. For "
"example, decals can be used to add nuts and bolts on top of hard-surface "
"geometry."
msgstr ""

#: ../../docs/tutorials/3d/using_decals.rst:50
msgid ""
"Since decals can inject their own :abbr:`PBR (Physically-Based Rendering)` "
"properties on top of the projected surfaces, they can also be used to create "
"footprints or wet puddles."
msgstr ""

#: ../../docs/tutorials/3d/using_decals.rst:58
msgid "Dirt added on top of level geometry using decals"
msgstr ""

#: ../../docs/tutorials/3d/using_decals.rst:61
msgid "Dynamic gameplay elements"
msgstr ""

#: ../../docs/tutorials/3d/using_decals.rst:63
msgid ""
"Decals can represent temporary or persistent gameplay effects such as bullet "
"impacts and explosion scorches."
msgstr ""

#: ../../docs/tutorials/3d/using_decals.rst:66
msgid ""
"Using an AnimationPlayer node or a script, decals can be made to fade over "
"time (and then be removed using ``queue_free()``) to improve performance."
msgstr ""

#: ../../docs/tutorials/3d/using_decals.rst:70
msgid "Blob shadows"
msgstr ""

#: ../../docs/tutorials/3d/using_decals.rst:72
msgid ""
"Blob shadows are frequently used in mobile projects (or to follow a retro "
"art style), as real-time lighting tends to be too expensive on low-end "
"mobile devices. However, when relying on baked lightmaps with fully baked "
"lights, dynamic objects will not cast *any* shadow from those lights. This "
"makes dynamic objects in lightmapped scenes look flat in comparison to real-"
"time lighting, with dynamic objects almost looking like they're floating."
msgstr ""

#: ../../docs/tutorials/3d/using_decals.rst:79
msgid ""
"Thanks to blob shadows, dynamic objects can still cast an approximative "
"shadow. Not only this helps with depth perception in the scene, but this can "
"also be a gameplay element, especially in 3D platformers. The blob shadow's "
"length can be extended to let the player know where they will land if they "
"fall straight down."
msgstr ""

#: ../../docs/tutorials/3d/using_decals.rst:84
msgid ""
"Even with real-time lighting, blob shadows can still be useful as a form of "
"ambient occlusion for situations where SSAO is too expensive or too unstable "
"due to its screen-space nature. For example, vehicles' underside shadows are "
"well-represented using blob shadows."
msgstr ""

#: ../../docs/tutorials/3d/using_decals.rst:93
msgid "Blob shadow under object comparison"
msgstr ""

#: ../../docs/tutorials/3d/using_decals.rst:96
msgid "Quick start guide"
msgstr ""

#: ../../docs/tutorials/3d/using_decals.rst:99
#, fuzzy
msgid "Creating decals in the editor"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/3d/using_decals.rst:101
#, fuzzy
msgid "Create a Decal node in the 3D editor."
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/3d/using_decals.rst:102
msgid ""
"In the inspector, expand the **Textures** section and load a texture in "
"**Textures > Albedo**."
msgstr ""

#: ../../docs/tutorials/3d/using_decals.rst:104
msgid ""
"Move the Decal node towards an object, then rotate it so the decal is "
"visible (and in the right orientation). If the decal appears mirrored, try "
"to rotate it by 180 degrees. You can double-check whether it's in the right "
"orientation by increasing **Parameters > Normal Fade** to 0.5. This will "
"prevent the Decal from being projected on surfaces that are not facing the "
"decal."
msgstr ""

#: ../../docs/tutorials/3d/using_decals.rst:109
msgid ""
"If your decal is meant to affect static objects only, configure it to "
"prevent affecting dynamic objects (or vice versa). To do so, change the "
"decal's **Cull Mask** property to exclude certain layers. After doing this, "
"modify your dynamic objects' MeshInstance3D nodes to change their visibility "
"layers. For instance, you can move them from layer 1 to layer 2, then "
"disable layer 2 in the decal's **Cull Mask** property."
msgstr ""

#: ../../docs/tutorials/3d/using_decals.rst:117
#, fuzzy
msgid "Decal node properties"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/3d/using_decals.rst:119
msgid ""
"**Extents:** The size of the decal. The Y axis determines the length of the "
"decal's projection. Keep the projection length as short as possible to "
"improve culling opportunities, therefore improving performance."
msgstr ""

#: ../../docs/tutorials/3d/using_decals.rst:124
#, fuzzy
msgid "Textures"
msgstr "Tutorijali"

#: ../../docs/tutorials/3d/using_decals.rst:126
msgid ""
"**Albedo:** The albedo (diffuse/color) map to use for the decal. In most "
"situations, this is the texture you want to set first. If using a normal or "
"ORM map, an albedo map *must* be set to provide an alpha channel. This alpha "
"channel will be used as a mask to determine how much the normal/ORM maps "
"will affect the underlying surface."
msgstr ""

#: ../../docs/tutorials/3d/using_decals.rst:131
msgid ""
"**Normal:** The normal map to use for the decal. This can be used to "
"increase perceived detail on the decal by modifying how light reacts to it. "
"The impact of this texture is multiplied by the albedo texture's alpha "
"channel (but not **Albedo Mix**)."
msgstr ""

#: ../../docs/tutorials/3d/using_decals.rst:135
msgid ""
"**ORM:** The Occlusion/Roughness/Metallic map to use for the decal. This is "
"an optimized format for storing PBR material maps. Ambient Occlusion map is "
"stored in the red channel, roughness map in the green channel, metallic map "
"in the blue channel. The impact of this texture is multiplied by the albedo "
"texture's alpha channel (but not **Albedo Mix**)."
msgstr ""

#: ../../docs/tutorials/3d/using_decals.rst:140
msgid ""
"**Emission:** The emission texture to use for the decal. Unlike **Albedo**, "
"this texture will appear to glow in the dark."
msgstr ""

#: ../../docs/tutorials/3d/using_decals.rst:144
#: ../../docs/tutorials/platform/ios/plugins_for_ios.rst:125
#: ../../docs/tutorials/platform/ios/plugins_for_ios.rst:165
#: ../../docs/tutorials/platform/ios/plugins_for_ios.rst:218
#: ../../docs/tutorials/platform/ios/plugins_for_ios.rst:235
#: ../../docs/tutorials/platform/ios/plugins_for_ios.rst:308
#: ../../docs/tutorials/platform/ios/plugins_for_ios.rst:352
#: ../../docs/tutorials/platform/ios/plugins_for_ios.rst:497
msgid "Parameters"
msgstr ""

#: ../../docs/tutorials/3d/using_decals.rst:146
msgid "**Emission Energy:** The brightness of the emission texture."
msgstr ""

#: ../../docs/tutorials/3d/using_decals.rst:147
msgid ""
"**Modulate:** Multiplies the color of the albedo and emission textures. Use "
"this to tint decals (e.g. for paint decals, or to increase variation by "
"randomizing each decal's modulation)."
msgstr ""

#: ../../docs/tutorials/3d/using_decals.rst:150
msgid ""
"**Albedo Mix:** The opacity of the albedo texture. Unlike using an albedo "
"texture with a more transparent alpha channel, decreasing this value below "
"``1.0`` does *not* reduce the impact of the normal/ORM texture on the "
"underlying surface. Set this to ``0.0`` when creating normal/ORM-only decals "
"such as footsteps or wet puddles."
msgstr ""

#: ../../docs/tutorials/3d/using_decals.rst:155
msgid ""
"**Normal Fade:** Fades the Decal if the angle between the Decal's :abbr:"
"`AABB (Axis-Aligned Bounding Box)` and the target surface becomes too large. "
"A value of ``0.0`` projects the decal regardless of angle, while a value of "
"``0.999`` limits the decal to surfaces that are nearly perpendicular. "
"Setting **Normal Fade** to a value greater than ``0.0`` has a small "
"performance cost due to the added normal angle computations."
msgstr ""

#: ../../docs/tutorials/3d/using_decals.rst:163
msgid "Vertical Fade"
msgstr ""

#: ../../docs/tutorials/3d/using_decals.rst:165
msgid ""
"**Upper Fade:** The curve over which the decal will fade as the surface gets "
"further from the center of the :abbr:`AABB (Axis-Aligned Bounding Box)` "
"(towards the decal's projection angle). Only positive values are valid."
msgstr ""

#: ../../docs/tutorials/3d/using_decals.rst:168
msgid ""
"**Lower Fade:** The curve over which the decal will fade as the surface gets "
"further from the center of the :abbr:`AABB (Axis-Aligned Bounding Box)` "
"(away from the decal's projection angle). Only positive values are valid."
msgstr ""

#: ../../docs/tutorials/3d/using_decals.rst:173
msgid "Distance Fade"
msgstr ""

#: ../../docs/tutorials/3d/using_decals.rst:175
msgid ""
"**Enabled:** Controls whether distance fade (a form of :abbr:`LOD (Level of "
"Detail)`) is enabled. The decal will fade out over **Begin + Length**, after "
"which it will be culled and not sent to the shader at all. Use this to "
"reduce the number of active decals in a scene and thus improve performance."
msgstr ""

#: ../../docs/tutorials/3d/using_decals.rst:179
msgid ""
"**Begin:** The distance from the camera at which the decal begins to fade "
"away (in 3D units)."
msgstr ""

#: ../../docs/tutorials/3d/using_decals.rst:181
msgid ""
"**Length:** The distance over which the decal fades (in 3D units). The decal "
"becomes slowly more transparent over this distance and is completely "
"invisible at the end. Higher values result in a smoother fade-out "
"transition, which is more suited when the camera moves fast."
msgstr ""

#: ../../docs/tutorials/3d/using_decals.rst:187
msgid "Cull Mask"
msgstr ""

#: ../../docs/tutorials/3d/using_decals.rst:189
msgid ""
"**Cull Mask:** Specifies which VisualInstance3D layers this decal will "
"project on. By default, decals affect all layers. This is used so you can "
"specify which types of objects receive the decal and which do not. This is "
"especially useful so you can ensure that dynamic objects don't accidentally "
"receive a Decal intended for the terrain under them."
msgstr ""

#: ../../docs/tutorials/3d/using_decals.rst:196
msgid "Tweaking performance and quality"
msgstr ""

#: ../../docs/tutorials/3d/using_decals.rst:198
msgid ""
"Decal rendering performance is mostly determined by their screen coverage, "
"but also their number. In general, a few large decals that cover up most of "
"the screen will be more expensive to render than many small decals that are "
"scattered around."
msgstr ""

#: ../../docs/tutorials/3d/using_decals.rst:203
msgid ""
"To improve rendering performance, you can enable the **Distance Fade** "
"property as described above. This will make distant decals fade out when "
"they are far away from the camera (and may have little to no impact on the "
"final scene rendering). Using node groups, you can also prevent non-"
"essential decorative decals from spawning based on user configuration."
msgstr ""

#: ../../docs/tutorials/3d/using_decals.rst:209
msgid ""
"The way decals are rendered also has an impact on performance. The "
"**Rendering > Textures > Decals > Filter** advanced project setting lets you "
"control how decal textures should be filtered. **Nearest/Linear** does not "
"use mipmaps. However, decals will look grainy at a distance. **Nearest/"
"Linear Mipmaps** will look smoother at a distance, but decals will look "
"blurry when viewed from oblique angles. This can be resolved by using "
"**Nearest/Linear Mipmaps Anisotropic**, which provides the highest quality "
"but is also slower to render."
msgstr ""

#: ../../docs/tutorials/3d/using_decals.rst:217
msgid ""
"If your project has a pixel art style, consider setting the filter to one of "
"the **Nearest** values so that decals use nearest-neighbor filtering. "
"Otherwise, stick to **Linear**."
msgstr ""

#: ../../docs/tutorials/3d/using_decals.rst:224
msgid ""
"Decals cannot affect material properties other than the ones listed above, "
"such as height (for parallax mapping)."
msgstr ""

#: ../../docs/tutorials/3d/using_decals.rst:227
msgid ""
"For performance reasons, decals use purely fixed rendering logic. This means "
"decals cannot use custom shaders. However, custom shaders on the projected "
"surfaces are able to read the information that is overridden by decals on "
"top of them, such as roughness and metallic."
msgstr ""

#: ../../docs/tutorials/3d/using_decals.rst:232
msgid ""
"When using the Forward+ renderer, Godot uses a *clustering* approach for "
"decal rendering. As many decals as desired can be added (as long as "
"performance allows). However, there's still a default limit of 512 "
"*clustered elements* that can be present in the current camera view. A "
"clustered element is an omni light, a spot light, a :ref:`decal "
"<doc_using_decals>` or a :ref:`reflection probe <doc_reflection_probes>`. "
"This limit can be increased by adjusting the **Rendering > Limits > Cluster "
"Builder > Max Clustered Elements** advanced project setting."
msgstr ""

#: ../../docs/tutorials/3d/using_decals.rst:241
msgid ""
"When using the Forward Mobile backend, only 8 decals can be applied on each "
"individual Mesh *resource*. If there are more decals affecting a single "
"mesh, not all of them will be rendered on the mesh."
msgstr ""

#: ../../docs/tutorials/3d/physical_light_and_camera_units.rst:4
msgid "Physical light and camera units"
msgstr ""

#: ../../docs/tutorials/3d/physical_light_and_camera_units.rst:7
msgid "Why use physical light and camera units?"
msgstr ""

#: ../../docs/tutorials/3d/physical_light_and_camera_units.rst:9
msgid ""
"Godot uses arbitrary units for many physical properties that apply to light "
"like color, energy, camera field of view, and exposure. By default, these "
"properties use arbitrary units, because using accurate physical units comes "
"with a few tradeoffs that aren't worth it for many games. As Godot favors "
"ease of use by default, physical light units are disabled by default."
msgstr ""

#: ../../docs/tutorials/3d/physical_light_and_camera_units.rst:16
msgid "Advantages of physical units"
msgstr ""

#: ../../docs/tutorials/3d/physical_light_and_camera_units.rst:18
msgid ""
"If you aim for photorealism in your project, using real world units as a "
"basis can help make things easier to adjust. References for real world "
"materials, lights and scene brightness are wildly available on websites such "
"as `Physically Based <https://physicallybased.info/>`__."
msgstr ""

#: ../../docs/tutorials/3d/physical_light_and_camera_units.rst:23
msgid ""
"Using real world units in Godot can also be useful when porting a scene from "
"other 3D software that uses physical light units (such as Blender)."
msgstr ""

#: ../../docs/tutorials/3d/physical_light_and_camera_units.rst:27
msgid "Disadvantages of physical units"
msgstr ""

#: ../../docs/tutorials/3d/physical_light_and_camera_units.rst:29
msgid ""
"The biggest disadvantage of using physical light units is you will have to "
"pay close attention to the dynamic range in use at a given time. You can run "
"into floating point precision errors when mixing very high light intensities "
"with very low light intensities."
msgstr ""

#: ../../docs/tutorials/3d/physical_light_and_camera_units.rst:34
msgid ""
"In practice, this means that you will have to manually manage your exposure "
"settings to ensure that you aren't over-exposing or under-exposing your "
"scene too much. Auto-exposure can help you balance the light in a scene to "
"bring it into a normal range, but it can't recover lost precision from a "
"dynamic range that is too high."
msgstr ""

#: ../../docs/tutorials/3d/physical_light_and_camera_units.rst:40
msgid ""
"Using physical light and camera units will not automatically make your "
"project look *better*. Sometimes, moving away from realism can actually make "
"a scene look better to the human eye. Also, using physical units requires a "
"greater amount of rigor compared to non-physical units. Most benefits of "
"physical units can only be obtained if the units are correctly set to match "
"real world reference."
msgstr ""

#: ../../docs/tutorials/3d/physical_light_and_camera_units.rst:49
msgid "Physical light units are only available in 3D rendering, not 2D."
msgstr ""

#: ../../docs/tutorials/3d/physical_light_and_camera_units.rst:52
#, fuzzy
msgid "Setting up physical light units"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/3d/physical_light_and_camera_units.rst:54
msgid ""
"Physical light units can be enabled separately from physical camera units."
msgstr ""

#: ../../docs/tutorials/3d/physical_light_and_camera_units.rst:56
msgid "To enable physical light units correctly, there are 4 steps required:"
msgstr ""

#: ../../docs/tutorials/3d/physical_light_and_camera_units.rst:58
#, fuzzy
msgid "Enable the project setting."
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/3d/physical_light_and_camera_units.rst:59
#, fuzzy
msgid "Configure the camera."
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/3d/physical_light_and_camera_units.rst:60
msgid "Configure the environment."
msgstr ""

#: ../../docs/tutorials/3d/physical_light_and_camera_units.rst:61
msgid "Configure Light3D nodes."
msgstr ""

#: ../../docs/tutorials/3d/physical_light_and_camera_units.rst:63
msgid ""
"Since physical light and camera units only require a handful of calculations "
"to handle unit conversion, enabling them doesn't have any noticeable "
"performance impact on the CPU. However, on the GPU side, physical camera "
"units currently enforce depth of field. This has a moderate performance "
"impact. To alleviate this performance impact, depth of field quality can be "
"decreased in the advanced Project Settings."
msgstr ""

#: ../../docs/tutorials/3d/physical_light_and_camera_units.rst:71
#, fuzzy
msgid "Enable the project setting"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/3d/physical_light_and_camera_units.rst:73
msgid ""
"Open the Project Settings, enable the **Advanced** toggle then enable "
"**Rendering > Lights And Shadows > Use Physical Light Units**. Restart the "
"editor."
msgstr ""

#: ../../docs/tutorials/3d/physical_light_and_camera_units.rst:77
#, fuzzy
msgid "Configure the camera"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/3d/physical_light_and_camera_units.rst:81
msgid ""
"When physical light units are enabled and if you have a WorldEnvironment "
"node in your scene (i.e. the editor Environment is disabled), you **must** "
"have a :ref:`class_CameraAttributes` resource assigned to the "
"WorldEnvironment node. Otherwise, the 3D editor viewport will appear "
"extremely bright if you have a visible DirectionalLight3D node."
msgstr ""

#: ../../docs/tutorials/3d/physical_light_and_camera_units.rst:87
msgid ""
"On the Camera3D node, you can add a :ref:`class_CameraAttributes` resource "
"to its **Attributes** property. This resource is used to control the "
"camera's depth of field and exposure. When using :ref:"
"`class_CameraAttributesPhysical`, its focal length property is also used to "
"adjust the camera's field of view."
msgstr ""

#: ../../docs/tutorials/3d/physical_light_and_camera_units.rst:93
msgid ""
"When physical light units are enabled, the following additional properties "
"become available in CameraAttributesPhysical's **Exposure** section:"
msgstr ""

#: ../../docs/tutorials/3d/physical_light_and_camera_units.rst:96
msgid ""
"**Aperture:** The size of the aperture of the camera, measured in f-stops. "
"An f-stop is a unitless ratio between the focal length of the camera and the "
"diameter of the aperture. A high aperture setting will result in a smaller "
"aperture which leads to a dimmer image and sharper focus. A low aperture "
"results in a wide aperture which lets in more light resulting in a brighter, "
"less-focused image."
msgstr ""

#: ../../docs/tutorials/3d/physical_light_and_camera_units.rst:102
msgid ""
"**Shutter Speed:** The time for shutter to open and close, measured in "
"*inverse seconds* (``1/N``). A lower value will let in more light leading to "
"a brighter image, while a higher value will let in less light leading to a "
"darker image. *When getting or setting this property with a script, the unit "
"is in seconds instead of inverse seconds.*"
msgstr ""

#: ../../docs/tutorials/3d/physical_light_and_camera_units.rst:107
msgid ""
"**Sensitivity:** The sensitivity of camera sensors, measured in ISO. A "
"higher sensitivity results in a brighter image. When auto exposure is "
"enabled, this can be used as a method of exposure compensation. Doubling the "
"value will increase the exposure value (measured in EV100) by 1 stop."
msgstr ""

#: ../../docs/tutorials/3d/physical_light_and_camera_units.rst:111
msgid ""
"**Multiplier:** A *non-physical* exposure multiplier. Higher values will "
"increase the scene's brightness. This can be used for post-processing "
"adjustments or for animation purposes."
msgstr ""

#: ../../docs/tutorials/3d/physical_light_and_camera_units.rst:115
msgid ""
"The default **Aperture** value of 16 f-stops is appropriate for outdoors at "
"daytime (i.e. for use with a default DirectionalLight3D). For indoor "
"lighting, a value between 2 and 4 is more appropriate."
msgstr ""

#: ../../docs/tutorials/3d/physical_light_and_camera_units.rst:119
msgid ""
"Typical shutter speed used in photography and movie production is 1/50 (0.02 "
"seconds). Night-time photography generally uses a shutter around 1/10 (0.1 "
"seconds), while sports photography uses a shutter speed between 1/250 (0.004 "
"seconds) and 1/1000 (0.001 seconds) to reduce motion blur."
msgstr ""

#: ../../docs/tutorials/3d/physical_light_and_camera_units.rst:124
msgid ""
"In real life, sensitivity is usually set between 50 ISO and 400 ISO for "
"daytime outdoor photography depending on weather conditions. Higher values "
"are used for indoor or night-time photography."
msgstr ""

#: ../../docs/tutorials/3d/physical_light_and_camera_units.rst:130
msgid ""
"Unlike real life cameras, the adverse effects of increasing ISO sensitivity "
"or decreasing shutter speed (such as visible grain or light trails) are not "
"simulated in Godot."
msgstr ""

#: ../../docs/tutorials/3d/physical_light_and_camera_units.rst:134
msgid ""
"See :ref:"
"`doc_physical_light_and_camera_units_setting_up_physical_camera_units` for a "
"description of CameraAttributesPhysical properties that are also available "
"when **not** using physical light units."
msgstr ""

#: ../../docs/tutorials/3d/physical_light_and_camera_units.rst:139
msgid "Configure the environment"
msgstr ""

#: ../../docs/tutorials/3d/physical_light_and_camera_units.rst:143
msgid ""
"The default configuration is designed for daytime outdoor scenes. Night-time "
"and indoor scenes will need adjustments to the DirectionalLight3D and "
"WorldEnvironment background intensity to look correct. Otherwise, positional "
"lights will be barely visible at their default intensity."
msgstr ""

#: ../../docs/tutorials/3d/physical_light_and_camera_units.rst:148
msgid ""
"If you haven't added a :ref:`class_WorldEnvironment` and :ref:"
"`class_Camera3D` node to the current scene yet, do so now by clicking the 3 "
"vertical dots at the top of the 3D editor viewport. Click **Add Sun to "
"Scene**, open the dialog again then click **Add Environment to Scene**."
msgstr ""

#: ../../docs/tutorials/3d/physical_light_and_camera_units.rst:153
msgid ""
"After enabling physical light units, a new property becomes available to "
"edit in the :ref:`class_Environment` resource:"
msgstr ""

#: ../../docs/tutorials/3d/physical_light_and_camera_units.rst:156
msgid ""
"**Background Intensity:** The background sky's intensity in `nits <https://"
"en.wikipedia.org/wiki/Candela_per_square_metre>`__ (candelas per square "
"meter). This also affects ambient and reflected light if their respective "
"modes are set to **Background**. If a custom **Background Energy** is set, "
"this energy is multiplied by the intensity."
msgstr ""

#: ../../docs/tutorials/3d/physical_light_and_camera_units.rst:163
msgid "Configure the light nodes"
msgstr ""

#: ../../docs/tutorials/3d/physical_light_and_camera_units.rst:165
msgid ""
"After enabling physical light units, 2 new properties become available in "
"Light3D nodes:"
msgstr ""

#: ../../docs/tutorials/3d/physical_light_and_camera_units.rst:167
msgid ""
"**Intensity:** The light's intensity in `lux <https://en.wikipedia.org/wiki/"
"Lux>`__ (DirectionalLight3D) or `lumens <https://en.wikipedia.org/wiki/"
"Lumen_(unit)>`__ (OmniLight3D/SpotLight3D). If a custom **Energy** is set, "
"this energy is multiplied by the intensity."
msgstr ""

#: ../../docs/tutorials/3d/physical_light_and_camera_units.rst:171
msgid ""
"**Temperature:** The light's *color temperature* defined in Kelvin. If a "
"custom **Color** is set, this color is multiplied by the color temperature."
msgstr ""

#: ../../docs/tutorials/3d/physical_light_and_camera_units.rst:174
msgid "**OmniLight3D/SpotLight3D intensity**"
msgstr ""

#: ../../docs/tutorials/3d/physical_light_and_camera_units.rst:176
msgid ""
"Lumens are a measure of luminous flux, which is the total amount of visible "
"light emitted by a light source per unit of time."
msgstr ""

#: ../../docs/tutorials/3d/physical_light_and_camera_units.rst:179
msgid ""
"For SpotLight3Ds, we assume that the area outside the visible cone is "
"surrounded by a perfect light absorbing material. Accordingly, the apparent "
"brightness of the cone area does *not* change as the cone increases and "
"decreases in size."
msgstr ""

#: ../../docs/tutorials/3d/physical_light_and_camera_units.rst:183
msgid ""
"A typical household lightbulb can range from around 600 lumens to 1200 "
"lumens. A candle is about 13 lumens, while a streetlight can be "
"approximately 60000 lumens."
msgstr ""

#: ../../docs/tutorials/3d/physical_light_and_camera_units.rst:186
msgid "**DirectionalLight3D intensity**"
msgstr ""

#: ../../docs/tutorials/3d/physical_light_and_camera_units.rst:188
msgid ""
"Lux is a measure pf luminous flux per unit area, it is equal to one lumen "
"per square metre. Lux is the measure of how much light hits a surface at a "
"given time."
msgstr ""

#: ../../docs/tutorials/3d/physical_light_and_camera_units.rst:192
msgid ""
"With DirectionalLight3D, on a clear sunny day, a surface in direct sunlight "
"may receive approximately 100000 lux. A typical room in a home may receive "
"approximately 50 lux, while the moonlit ground may receive approximately 0.1 "
"lux."
msgstr ""

#: ../../docs/tutorials/3d/physical_light_and_camera_units.rst:197
#, fuzzy
msgid "**Color temperature**"
msgstr "**Za uređivač:**"

#: ../../docs/tutorials/3d/physical_light_and_camera_units.rst:199
msgid ""
"6500 Kelvin is white. Higher values result in colder (bluer) colors, while "
"lower values result in warmer (more orange) colors."
msgstr ""

#: ../../docs/tutorials/3d/physical_light_and_camera_units.rst:202
msgid ""
"The sun on a cloudy day is approximately 6500 Kelvin. On a clear day, the "
"sun is between 5500 to 6000 Kelvin. On a clear day at sunrise or sunset, the "
"sun ranges to around 1850 Kelvin."
msgstr ""

#: ../../docs/tutorials/3d/physical_light_and_camera_units.rst:210
msgid ""
"Color temperature chart from 1,000 Kelvin (left) to 12,500 Kelvin (right)"
msgstr ""

#: ../../docs/tutorials/3d/physical_light_and_camera_units.rst:212
msgid ""
"Other Light3D properties such as **Energy** and **Color** remain editable "
"for animation purposes, and when you occasionally need to create lights with "
"non-realistic properties."
msgstr ""

#: ../../docs/tutorials/3d/physical_light_and_camera_units.rst:219
#, fuzzy
msgid "Setting up physical camera units"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/3d/physical_light_and_camera_units.rst:221
msgid ""
"Physical camera units can be enabled separately from physical light units."
msgstr ""

#: ../../docs/tutorials/3d/physical_light_and_camera_units.rst:223
msgid ""
"After adding a :ref:`class_CameraAttributesPhysical` resource to the "
"**Camera Attributes** property of a Camera3D nodes, some properties such as "
"**FOV** will no longer be editable. Instead, these properties are now "
"governed by the CameraAttributesPhysical's properties, such as focal length "
"and aperture."
msgstr ""

#: ../../docs/tutorials/3d/physical_light_and_camera_units.rst:228
msgid ""
"CameraAttributesPhysical offers the following properties in its **Frustum** "
"section:"
msgstr ""

#: ../../docs/tutorials/3d/physical_light_and_camera_units.rst:230
msgid ""
"**Focus Distance:** Distance from camera of object that will be in focus, "
"measured in meters. Internally, this will be clamped to be at least 1 "
"millimeter larger than the **Focal Length**."
msgstr ""

#: ../../docs/tutorials/3d/physical_light_and_camera_units.rst:233
msgid ""
"**Focal Length:** Distance between camera lens and camera aperture, measured "
"in millimeters. Controls field of view and depth of field. A larger focal "
"length will result in a smaller field of view and a narrower depth of field "
"meaning fewer objects will be in focus. A smaller focal length will result "
"in a wider field of view and a larger depth of field, which means more "
"objects will be in focus. This property overrides the Camera3D's **FOV** and "
"**Keep Aspect** properties, making them read-only in the inspector."
msgstr ""

#: ../../docs/tutorials/3d/physical_light_and_camera_units.rst:240
msgid ""
"**Near/Far:** The near and far clip distances in meters. These behave the "
"same as the Camera3D properties of the same name. Lower **Near** values "
"allow the camera to display objects that are very close, at the cost of "
"potential precision (Z-fighting) issues in the distance. Higher **Far** "
"values allow the camera to see further away, also at the cost of potential "
"precision (Z-fighting) issues in the distance."
msgstr ""

#: ../../docs/tutorials/3d/physical_light_and_camera_units.rst:247
msgid ""
"The default focal length of 35 mm corresponds to a wide angle lens. It still "
"results in a field of view that is noticeably narrower compared to the "
"default \"practical\" vertical FOV of 75 degrees. This is because non-gaming "
"use cases such as filmmaking and photography favor using a narrower field of "
"view for a more cinematic appearance."
msgstr ""

#: ../../docs/tutorials/3d/physical_light_and_camera_units.rst:253
msgid "Common focal length values used in filmmaking and photography are:"
msgstr ""

#: ../../docs/tutorials/3d/physical_light_and_camera_units.rst:255
msgid ""
"**Fisheye (ultrawide angle):** Below 15 mm. Nearly no depth of field visible."
msgstr ""

#: ../../docs/tutorials/3d/physical_light_and_camera_units.rst:256
msgid "**Wide angle:** Between 15 mm and 50 mm. Reduced depth of field."
msgstr ""

#: ../../docs/tutorials/3d/physical_light_and_camera_units.rst:257
msgid "**Standard:** Between 50 mm and 100 mm. Standard depth of field."
msgstr ""

#: ../../docs/tutorials/3d/physical_light_and_camera_units.rst:258
msgid "**Telephoto:** Greater than 100 mm. Increased depth of field."
msgstr ""

#: ../../docs/tutorials/3d/physical_light_and_camera_units.rst:260
msgid ""
"Like when using the **Keep Height** aspect mode, the effective field of view "
"depends on the viewport's aspect ratio, with wider aspect ratios "
"automatically resulting in a wider *horizontal* field of view."
msgstr ""

#: ../../docs/tutorials/3d/physical_light_and_camera_units.rst:264
msgid ""
"Automatic exposure adjustment based on the camera's average brightness level "
"can also be enabled in the **Auto Exposure** section, with the following "
"properties:"
msgstr ""

#: ../../docs/tutorials/3d/physical_light_and_camera_units.rst:267
msgid ""
"**Min Sensitivity:** The darkest brightness the camera is allowed to get to, "
"measured in EV100."
msgstr ""

#: ../../docs/tutorials/3d/physical_light_and_camera_units.rst:269
msgid ""
"**Max Sensitivity:** The brightest the camera is allowed to get to, measured "
"in EV100."
msgstr ""

#: ../../docs/tutorials/3d/physical_light_and_camera_units.rst:270
msgid ""
"**Speed:** The speed of the auto exposure effect. Affects the time needed "
"for the camera to perform auto exposure. Higher values allow for faster "
"transitions, but the resulting adjustments may look distracting depending on "
"the scene."
msgstr ""

#: ../../docs/tutorials/3d/physical_light_and_camera_units.rst:274
msgid ""
"**Scale:** The scale of the auto exposure effect. Affects the intensity of "
"auto exposure."
msgstr ""

#: ../../docs/tutorials/3d/physical_light_and_camera_units.rst:277
msgid ""
"EV100 is an exposure value (EV) measured at an ISO sensitivity of 100. See "
"`this table <https://en.wikipedia.org/wiki/"
"Exposure_value#Tabulated_exposure_values>`__ for common EV100 values found "
"in real life."
msgstr ""

#: ../../docs/tutorials/3d/particles/index.rst:4
msgid "Particle systems (3D)"
msgstr ""

#: ../../docs/tutorials/3d/particles/index.rst:6
msgid ""
"This section of the tutorial covers (3D) GPU-accelerated particle systems. "
"Most of the things discussed here apply to CPU particles as well."
msgstr ""

#: ../../docs/tutorials/3d/particles/index.rst:12
msgid ""
"You can use particle systems to simulate complex physical effects like fire, "
"sparks, smoke, magical effects, and many more. They are very well suited for "
"creating dynamic and organic behavior and adding \"life\" to your scenes."
msgstr ""

#: ../../docs/tutorials/3d/particles/index.rst:16
msgid ""
"The idea is that a particle is emitted at a fixed interval and with a fixed "
"lifetime. During its lifetime, every particle will have the same base "
"behavior. What makes each particle different from the others and creates the "
"organic look is the randomness that you can add to most of its parameters "
"and behaviors."
msgstr ""

#: ../../docs/tutorials/3d/particles/index.rst:21
msgid ""
"Every particle system you create in Godot consists of two main parts: "
"particles and emitters."
msgstr ""

#: ../../docs/tutorials/3d/particles/index.rst:26
msgid ""
"A particle is the visible part of a particle system. It's what you see on "
"the screen when a particle system is active: The tiny specks of dust, the "
"flames of a fire, the glowing orbs of a magical effect. You can have "
"anywhere between a couple hundred and tens of thousands of particles in a "
"single system. You can randomize a particle's size, its speed and movement "
"direction, and change its color over the course of its lifetime. When you "
"think of a fire, you can think of all the little embers flying away from it "
"as individual particles."
msgstr ""

#: ../../docs/tutorials/3d/particles/index.rst:34
msgid "Emitters"
msgstr ""

#: ../../docs/tutorials/3d/particles/index.rst:36
msgid ""
"An emitter is what's creating the particles. Emitters are usually not "
"visible, but they can have a shape. That shape controls where and how "
"particles are spawned, for example whether they should fill a room like dust "
"or shoot away from a single point like a fountain. Going back to the fire "
"example, an emitter would be the heat at the center of the fire that creates "
"the embers and the flames."
msgstr ""

#: ../../docs/tutorials/3d/particles/index.rst:42
msgid "Node overview"
msgstr ""

#: ../../docs/tutorials/3d/particles/index.rst:48
msgid "A list of nodes related to 3D particles"
msgstr ""

#: ../../docs/tutorials/3d/particles/index.rst:48
msgid "All 3D particle nodes available in Godot"
msgstr ""

#: ../../docs/tutorials/3d/particles/index.rst:50
msgid ""
"There are two types of 3D particle systems in Godot: :ref:"
"`class_GPUParticles3D`, which are processed on the GPU, and :ref:"
"`class_CPUParticles3D`, which are processed on the CPU."
msgstr ""

#: ../../docs/tutorials/3d/particles/index.rst:53
msgid ""
"CPU particle systems are less flexible than their GPU counterpart, but they "
"work on a wider range of hardware and provide better support for older "
"devices and mobile phones. Because they are processed on the CPU, they are "
"not as performant as GPU particle systems and can't render as many "
"individual particles. In addition they currently do not have all the "
"available options GPU particles have for control."
msgstr ""

#: ../../docs/tutorials/3d/particles/index.rst:58
msgid ""
"GPU particle systems run on the GPU and can render hundreds of thousands of "
"particles on modern hardware. You can write custom particle shaders for "
"them, which makes them very flexible. You can also make them interact with "
"the environment by using attractor and collision nodes."
msgstr ""

#: ../../docs/tutorials/3d/particles/index.rst:62
msgid ""
"There are three particle attractor nodes: :ref:"
"`class_GPUParticlesAttractorBox3D`, :ref:"
"`class_GPUParticlesAttractorSphere3D`, and :ref:"
"`class_GPUParticlesAttractorVectorField3D`. An attractor node applies a "
"force to all particles in its reach and pulls them closer or pushes them "
"away based on the direction of that force."
msgstr ""

#: ../../docs/tutorials/3d/particles/index.rst:66
msgid ""
"There are several particle collision nodes. :ref:"
"`class_GPUParticlesCollisionBox3D` and :ref:"
"`class_GPUParticlesCollisionSphere3D` are the simple ones. You can use them "
"to create basic shapes like boxes, a floor, or a wall that particles collide "
"with. The other two nodes provide more complex collision behavior. The :ref:"
"`class_GPUParticlesCollisionSDF3D` is useful when you want indoor scenes to "
"collide with particles without having to create all the individual box and "
"sphere colliders by hand. If you want particles to collide with large "
"outdoor scenes, you would use the :ref:"
"`class_GPUParticlesCollisionHeightField3D` node. It creates a heightmap of "
"your world and the objects in it and uses that for large-scale particle "
"collisions."
msgstr ""

#: ../../docs/tutorials/3d/particles/index.rst:77
#: ../../docs/tutorials/scripting/evaluating_expressions.rst:22
msgid "Basic usage"
msgstr ""

#: ../../docs/tutorials/3d/particles/index.rst:88
#: ../../docs/tutorials/xr/index.rst:17
msgid "Advanced topics"
msgstr ""

#: ../../docs/tutorials/3d/particles/creating_a_3d_particle_system.rst:4
#, fuzzy
msgid "Creating a 3D particle system"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/3d/particles/creating_a_3d_particle_system.rst:9
#, fuzzy
msgid "Required particle node properties"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/3d/particles/creating_a_3d_particle_system.rst:11
msgid ""
"To get started with particles, the first thing we need to do is add a "
"``GPUParticles3D`` node to the scene. Before we can actually see any "
"particles, we have to set up two parameters on the node: the ``Process "
"Material`` and at least one ``Draw Pass``."
msgstr ""

#: ../../docs/tutorials/3d/particles/creating_a_3d_particle_system.rst:16
msgid "The process material"
msgstr ""

#: ../../docs/tutorials/3d/particles/creating_a_3d_particle_system.rst:18
msgid ""
"To add a process material to your particles node, go to ``Process Material`` "
"in the inspector panel. Click on the box next to ``Process Material`` and "
"from the dropdown menu select ``New ParticleProcessMaterial``."
msgstr ""

#: ../../docs/tutorials/3d/particles/creating_a_3d_particle_system.rst:24
#, fuzzy
msgid "Creating a process material"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/3d/particles/creating_a_3d_particle_system.rst:26
msgid ""
":ref:`class_ParticleProcessMaterial` is a special kind of material. We don't "
"use it to draw any objects. We use it to update particle data and behavior "
"on the GPU instead of the CPU, which comes with a massive performance boost. "
"A click on the newly added material displays a long list of properties that "
"you can set to control each particle's behavior."
msgstr ""

#: ../../docs/tutorials/3d/particles/creating_a_3d_particle_system.rst:32
msgid "Draw passes"
msgstr ""

#: ../../docs/tutorials/3d/particles/creating_a_3d_particle_system.rst:37
msgid "At least one draw pass is required"
msgstr ""

#: ../../docs/tutorials/3d/particles/creating_a_3d_particle_system.rst:39
msgid ""
"In order to render any particles, at least one draw pass needs to be "
"defined. To do that, go to ``Draw Passes`` in the inspector panel. Click on "
"the box next to ``Pass 1`` and select ``New QuadMesh`` from the dropdown "
"menu. After that, click on the mesh and set its ``Size`` to 0.1 for both "
"``x`` and ``y``. Reducing the mesh's size makes it a little easier to tell "
"the individual particle meshes apart at this stage."
msgstr ""

#: ../../docs/tutorials/3d/particles/creating_a_3d_particle_system.rst:45
msgid ""
"You can use up to 4 draw passes per particle system. Each pass can render a "
"different mesh with its own unique material. All draw passes use the data "
"that is computed by the process material, which is an efficient method for "
"composing complex effects: Compute particle behavior once and feed it to "
"multiple render passes."
msgstr ""

#: ../../docs/tutorials/3d/particles/creating_a_3d_particle_system.rst:52
msgid ""
"Using multiple draw passes: yellow rectangles (pass1) and blue spheres (pass "
"2)"
msgstr ""

#: ../../docs/tutorials/3d/particles/creating_a_3d_particle_system.rst:54
msgid ""
"If you followed the steps above, your particle system should now be emitting "
"particles in a waterfall-like fashion, making them move downwards and "
"disappear after a few seconds. This is the foundation for all particle "
"effects. Take a look at the documentation for :ref:`particle "
"<doc_3d_particles_properties>` and :ref:`particle material "
"<doc_process_material_properties>` properties to learn how to make particle "
"effects more interesting."
msgstr ""

#: ../../docs/tutorials/3d/particles/creating_a_3d_particle_system.rst:63
msgid "Particle conversion"
msgstr ""

#: ../../docs/tutorials/3d/particles/creating_a_3d_particle_system.rst:68
msgid "Turning GPU into CPU particles"
msgstr ""

#: ../../docs/tutorials/3d/particles/creating_a_3d_particle_system.rst:70
msgid ""
"You can convert GPU particles to CPU particles at any time using the entry "
"in the viewport menu. When you do so, keep in mind that not every feature of "
"GPU particles is available for CPU particles, so the resulting particle "
"system will look and behave differently from the original."
msgstr ""

#: ../../docs/tutorials/3d/particles/creating_a_3d_particle_system.rst:75
msgid ""
"You can also convert CPU particles to GPU particles if you no longer need to "
"use CPU particles. This is also done from the viewport menu."
msgstr ""

#: ../../docs/tutorials/3d/particles/creating_a_3d_particle_system.rst:78
msgid ""
"Some of the most notable features that are lost during the conversion "
"include:"
msgstr ""

#: ../../docs/tutorials/3d/particles/creating_a_3d_particle_system.rst:80
msgid "multiple draw passes"
msgstr ""

#: ../../docs/tutorials/3d/particles/creating_a_3d_particle_system.rst:81
msgid "turbulence"
msgstr ""

#: ../../docs/tutorials/3d/particles/creating_a_3d_particle_system.rst:82
msgid "sub-emitters"
msgstr ""

#: ../../docs/tutorials/3d/particles/creating_a_3d_particle_system.rst:83
msgid "trails"
msgstr ""

#: ../../docs/tutorials/3d/particles/creating_a_3d_particle_system.rst:84
msgid "attractors"
msgstr ""

#: ../../docs/tutorials/3d/particles/creating_a_3d_particle_system.rst:85
#, fuzzy
msgid "collision"
msgstr "Kopiraj Označeno"

#: ../../docs/tutorials/3d/particles/creating_a_3d_particle_system.rst:87
#, fuzzy
msgid "You also lose the following properties:"
msgstr "Glavna dokumentacija za sajt je podeljena na sledeća poglavlja:"

#: ../../docs/tutorials/3d/particles/creating_a_3d_particle_system.rst:89
msgid "``Ammount Ratio``"
msgstr ""

#: ../../docs/tutorials/3d/particles/creating_a_3d_particle_system.rst:90
msgid "``Interp to End``"
msgstr ""

#: ../../docs/tutorials/3d/particles/creating_a_3d_particle_system.rst:91
#, fuzzy
msgid "``Damping as Friction``"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/3d/particles/creating_a_3d_particle_system.rst:92
msgid "``Emission Shape Offset``"
msgstr ""

#: ../../docs/tutorials/3d/particles/creating_a_3d_particle_system.rst:93
msgid "``Emission Shape Scale``"
msgstr ""

#: ../../docs/tutorials/3d/particles/creating_a_3d_particle_system.rst:94
msgid "``Inherit Velocity Ratio``"
msgstr ""

#: ../../docs/tutorials/3d/particles/creating_a_3d_particle_system.rst:95
msgid "``Velocity Pivot``"
msgstr ""

#: ../../docs/tutorials/3d/particles/creating_a_3d_particle_system.rst:96
#, fuzzy
msgid "``Directional Velocity``"
msgstr "Uvod"

#: ../../docs/tutorials/3d/particles/creating_a_3d_particle_system.rst:97
msgid "``Radial Velocity``"
msgstr ""

#: ../../docs/tutorials/3d/particles/creating_a_3d_particle_system.rst:98
msgid "``Velocity Limit``"
msgstr ""

#: ../../docs/tutorials/3d/particles/creating_a_3d_particle_system.rst:99
msgid "``Scale Over Velocity``"
msgstr ""

#: ../../docs/tutorials/3d/particles/creating_a_3d_particle_system.rst:101
msgid ""
"Converting GPU particles to CPU particles can become necessary when you want "
"to release a game on older devices that don't support modern graphics APIs."
msgstr ""

#: ../../docs/tutorials/3d/particles/properties.rst:4
#, fuzzy
msgid "3D Particle system properties"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/3d/particles/properties.rst:7
#, fuzzy
msgid "Emitter properties"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/3d/particles/properties.rst:12
msgid ""
"The checkbox next to the ``Emitting`` property activates and deactivates the "
"particle system. Particles will only be processed and rendered if the box is "
"checked. You can set this property at runtime if you want to activate or "
"deactivate particle systems dynamically."
msgstr ""

#: ../../docs/tutorials/3d/particles/properties.rst:16
msgid ""
"The ``Amount`` property controls the maximum number of particles visible at "
"any given time. Increase the value to spawn more particles at the cost of "
"performance."
msgstr ""

#: ../../docs/tutorials/3d/particles/properties.rst:19
msgid ""
"The ``Amount Ratio`` property is the radio of particles compared to the "
"ammount that will be emitted. If it's less than ``1.0`` the ammount of "
"particles emitted through the lifetime will be the ``Ammount`` * ``Amount "
"Ratio``. Changing this value while emitted doesn't affect already created "
"particles and doesn't cause the particle system to restart. It's useful for "
"making effects where the number of emitted particles varies over time."
msgstr ""

#: ../../docs/tutorials/3d/particles/properties.rst:25
msgid ""
"You can set another particle node as a ``Sub Emitter``, which will be "
"spawned as a child of each particle. See the :ref:`Sub-emitters "
"<doc_3d_particles_subemitters>` section in this manual for a detailed "
"explanation of how to add a sub-emitter to a particle system."
msgstr ""

#: ../../docs/tutorials/3d/particles/properties.rst:32
#, fuzzy
msgid "Time properties"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/3d/particles/properties.rst:37
msgid ""
"The ``Lifetime`` property controls how long each particle exists before it "
"disappears again. It is measured in seconds. A lot of particle properties "
"can be set to change over the particle's lifetime and blend smoothly from "
"one value to another."
msgstr ""

#: ../../docs/tutorials/3d/particles/properties.rst:41
msgid ""
"``Lifetime`` and ``Amount`` are related. They determine the particle "
"system's emission rate. Whenever you want to know how many particles are "
"spawned per second, this is the formula you would use:"
msgstr ""

#: ../../docs/tutorials/3d/particles/properties.rst:45
msgid "Particles per second = \\frac{Amount}{Lifetime}"
msgstr ""

#: ../../docs/tutorials/3d/particles/properties.rst:49
msgid ""
"Example: Emitting 32 particles with a lifetime of 4 seconds each would mean "
"the system emits 8 particles per second."
msgstr ""

#: ../../docs/tutorials/3d/particles/properties.rst:52
msgid ""
"The ``Interp to End`` property causes all the particles in the node to "
"interpolate towards the end of their lifetime."
msgstr ""

#: ../../docs/tutorials/3d/particles/properties.rst:55
msgid ""
"If the checkbox next to the ``One Shot`` property is checked, the particle "
"system will emit ``amount`` particles and then disable itself. It \"runs\" "
"only once. This property is unchecked by default, so the system will keep "
"emitting particles until it is disabled or destroyed manually. One-shot "
"particles are a good fit for effects that react to a single event, like item "
"pickups or splinters that burst away when a bullet hits a wall."
msgstr ""

#: ../../docs/tutorials/3d/particles/properties.rst:60
msgid ""
"The ``Preprocess`` property is a way to fast-forward to a point in the "
"middle of the particle system's lifetime and start rendering from there. It "
"is measured in seconds. A value of ``1`` means that when the particle system "
"starts, it will look as if it has been running for one second already."
msgstr ""

#: ../../docs/tutorials/3d/particles/properties.rst:65
msgid ""
"This can be useful if you want the particle system to look like it has been "
"active for a while even though it was just loaded into the scene. Consider "
"the example below. Both particle systems simulate dust flying around in the "
"area. With a preprocess value of ``0``, there wouldn't be any dust for the "
"first couple of seconds because the system has not yet emitted enough "
"particles for the effect to become noticeable. This can be seen in the video "
"on the left. Compare that to the video on the right where the particle "
"system is preprocessed for ``4`` seconds. The dust is fully visible from the "
"very beginning because we skipped the first four seconds of \"setup\" time."
msgstr ""

#: ../../docs/tutorials/3d/particles/properties.rst:75
msgid "No preprocess (left) vs. 4 seconds of preprocess (right)"
msgstr ""

#: ../../docs/tutorials/3d/particles/properties.rst:77
msgid ""
"You can slow down or speed up the particle system with the ``Speed Scale`` "
"property. This applies to processing the data as well as rendering the "
"particles. Set it to ``0`` to pause the particle system completely or set it "
"to something like ``2`` to make it move twice as fast."
msgstr ""

#: ../../docs/tutorials/3d/particles/properties.rst:83
msgid "Different speed scale values: 0.1 (left), 0.5 (middle), 1.0 (right)"
msgstr ""

#: ../../docs/tutorials/3d/particles/properties.rst:85
msgid ""
"The ``Explosiveness`` property controls whether particles are emitted "
"sequentially or simultaneously. A value of ``0`` means that particles emit "
"one after the other. A value of ``1`` means that all ``amount`` particles "
"emit at the same time, giving the effect a more \"explosive\" appearance."
msgstr ""

#: ../../docs/tutorials/3d/particles/properties.rst:90
msgid ""
"The ``Randomness`` property adds some randomness to the particle emission "
"timing. When set to ``0``, there is no randomness at all and the interval "
"between the emission of one particle and the next is always the same: the "
"particles are emitted at *regular* intervals. A ``Randomness`` value of "
"``1`` makes the interval completely random. You can use this property to "
"break up some of the uniformity in your effects. When ``Explosiveness`` is "
"set to ``1``, this property has no effect."
msgstr ""

#: ../../docs/tutorials/3d/particles/properties.rst:101
msgid "Particles running at low FPS"
msgstr ""

#: ../../docs/tutorials/3d/particles/properties.rst:101
msgid "Interpolation on (left) vs. off (right)"
msgstr ""

#: ../../docs/tutorials/3d/particles/properties.rst:103
msgid ""
"The ``Fixed FPS`` property limits how often the particle system is "
"processed. This includes property updates as well as collision and "
"attractors. This can improve performance a lot, especially in scenes that "
"make heavy use of particle collision. Note that this does not change the "
"speed at which particles move or rotate. You would use the ``Speed Scale`` "
"property for that."
msgstr ""

#: ../../docs/tutorials/3d/particles/properties.rst:109
msgid ""
"When you set ``Fixed FPS`` to very low values, you will notice that the "
"particle animation starts to look choppy. This can sometimes be desired if "
"it fits the art direction, but most of the time, you'll want particle "
"systems to animate smoothly. That's what the ``Interpolate`` property does. "
"It blends particle properties between updates so that even a particle system "
"running at ``10`` FPS appears as smooth as running at ``60``."
msgstr ""

#: ../../docs/tutorials/3d/particles/properties.rst:119
#, fuzzy
msgid "Collision properties"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/3d/particles/properties.rst:121
msgid ""
"The ``Base Size`` property defines each particle's default collision size, "
"which is used to check whether a particle is currently colliding with the "
"environment. You would usually want this to be about the same size as the "
"particle. It can make sense to increase this value for particles that are "
"very small and move very fast to prevent them from clipping through the "
"collision geometry."
msgstr ""

#: ../../docs/tutorials/3d/particles/properties.rst:130
#, fuzzy
msgid "Drawing properties"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/3d/particles/properties.rst:-1
#, fuzzy
msgid "Particle drawing properties"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/3d/particles/properties.rst:136
msgid ""
"The ``Visibility AABB`` property defines a box around the particle system's "
"origin. As long as any part of this box is in the camera's field of view, "
"the particle system is visible. As soon as it leaves the camera's field of "
"view, the particle system stops being rendered at all. You can use this "
"property to boost performance by keeping the box as small as possible."
msgstr ""

#: ../../docs/tutorials/3d/particles/properties.rst:142
msgid ""
"One thing to keep in mind when you set a size for the ``Visibility AABB`` is "
"that particles that are outside of its bounds disappear instantly when it "
"leaves the camera's field of view. This, while not technically a bug, can "
"have a negative effect on the visual experience."
msgstr ""

#: ../../docs/tutorials/3d/particles/properties.rst:146
msgid ""
"When the ``Local Coords`` property is checked, all particle calculations use "
"the local coordinate system to determine things like up and down, gravity, "
"and movement direction. Up and down, for example, would follow the particle "
"system's or its parent node's rotation. When the property is unchecked, the "
"global world space is used for these calculations: Down will always be -Y in "
"world space, regardless of the particle system's rotation."
msgstr ""

#: ../../docs/tutorials/3d/particles/properties.rst:154
msgid "Local space coordinates (left) vs. world space coordinates (right)"
msgstr ""

#: ../../docs/tutorials/3d/particles/properties.rst:156
msgid ""
"The ``Draw Order`` property controls the order in which individual particles "
"are drawn. ``Index`` means that they are drawn in the order of emission: "
"particles that are spawned later are drawn on top of earlier ones. "
"``Lifetime`` means that they are drawn in the order of their remaining "
"lifetime. ``Reverse Lifetime`` reverses the ``Lifetime`` draw order. ``View "
"Depth`` means particles are drawn according to their distance from the "
"camera: The ones closer to the camera on top of those farther away."
msgstr ""

#: ../../docs/tutorials/3d/particles/properties.rst:163
msgid ""
"The ``Transform Align`` property controls the particle's default rotation. "
"``Disabled`` means they don't align in any particular way. Instead, their "
"rotation is determined by the values set in the process material. ``Z-"
"Billboard`` means that the particles will always face the camera. This is "
"similar to the ``Billboard`` property in the :ref:`Standard Material "
"<doc_standard_material_3d>`. ``Y to Velocity`` means that each particle's Y-"
"axis aligns with its movement direction. This can be useful for things like "
"bullets or arrows, where you want particles to always point \"forward\". ``Z-"
"Billboard + Y to Velocity`` combines the previous two modes. Each particle's "
"Z-axis will point towards the camera while its Y-axis will align with their "
"velocity."
msgstr ""

#: ../../docs/tutorials/3d/particles/properties.rst:175
#, fuzzy
msgid "Trail properties"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/3d/particles/properties.rst:181
#: ../../docs/tutorials/3d/particles/trails.rst:-1
msgid "Particle trails"
msgstr ""

#: ../../docs/tutorials/3d/particles/properties.rst:181
#, fuzzy
msgid "Particle trail properties"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/3d/particles/properties.rst:183
msgid ""
"The ``Enabled`` property controls whether particles are rendered as trails. "
"The box needs to be checked if you want to make use of particle trails."
msgstr ""

#: ../../docs/tutorials/3d/particles/properties.rst:186
msgid ""
"The ``Length Secs`` property controls for how long a trail should be "
"emitted. The longer this duration is, the longer the trail will be."
msgstr ""

#: ../../docs/tutorials/3d/particles/properties.rst:189
msgid ""
"See the :ref:`Particle trails <doc_3d_particles_trails>` section in this "
"manual for a detailed explanation of how particle trails work and how to set "
"them up."
msgstr ""

#: ../../docs/tutorials/3d/particles/process_material_properties.rst:4
#, fuzzy
msgid "Process material properties"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/3d/particles/process_material_properties.rst:10
msgid "ParticleProcessMaterial properties"
msgstr ""

#: ../../docs/tutorials/3d/particles/process_material_properties.rst:10
#, fuzzy
msgid "Min, max, and curve properties"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/3d/particles/process_material_properties.rst:12
msgid ""
"The properties in this material control how particles behave and change over "
"their lifetime. A lot of them have ``Min``, ``Max``, and ``Curve`` values "
"that allow you to fine-tune their behavior. The relationship between these "
"values is this: When a particle is spawned, the property is set with a "
"random value between ``Min`` and ``Max``. If ``Min`` and ``Max`` are the "
"same, the value will always be the same for every particle. If the ``Curve`` "
"is also set, the value of the property will be multiplied by the value of "
"the curve at the current point in a particle's lifetime. Use the curve to "
"change a property over the particle lifetime. Very complex behavior can be "
"expressed this way."
msgstr ""

#: ../../docs/tutorials/3d/particles/process_material_properties.rst:22
msgid "Time"
msgstr ""

#: ../../docs/tutorials/3d/particles/process_material_properties.rst:24
msgid ""
"The ``Lifetime Randomness`` property controls how much randomness to apply "
"to each particle's lifetime. A value of ``0`` means there is no randomness "
"at all and all particles live for the same amount of time, set by the :ref:"
"`Lifetime <doc_3d_particles_properties_time>` property. A value of ``1`` "
"means that a particle's lifetime is completely random within the range of "
"[0.0, ``Lifetime``]."
msgstr ""

#: ../../docs/tutorials/3d/particles/process_material_properties.rst:30
msgid "Particle flags"
msgstr ""

#: ../../docs/tutorials/3d/particles/process_material_properties.rst:32
msgid ""
"The ``Align Y`` property aligns each particle's Y-axis with its velocity. "
"Enabling this property is the same as setting the :ref:`Transform Align "
"<doc_3d_particles_properties_draw>` property to ``Y to Velocity``."
msgstr ""

#: ../../docs/tutorials/3d/particles/process_material_properties.rst:36
msgid ""
"The ``Rotate Y`` property works with the properties in the `Angle "
"<#angle>`__ and `Angular Velocity <#angular-velocity>`__ groups to control "
"particle rotation. ``Rotate Y`` has to be enabled if you want to apply any "
"rotation to particles. The exception to this is any particle that uses the :"
"ref:`Standard Material <doc_standard_material_3d>` where the ``Billboard`` "
"property is set to ``Particle Billboard``. In that case, particles rotate "
"even without ``Rotate Y`` enabled."
msgstr ""

#: ../../docs/tutorials/3d/particles/process_material_properties.rst:43
msgid ""
"When the ``Disable Z`` property is enabled, particles will not move along "
"the Z-axis. Whether that is going to be the particle system's local Z-axis "
"or the world Z-axis is determined by the :ref:`Local Coords "
"<doc_3d_particles_properties_draw>` property."
msgstr ""

#: ../../docs/tutorials/3d/particles/process_material_properties.rst:47
msgid ""
"The ``Damping as Friction`` property changes the behavior of damping from a "
"constant deceleration to a deceleration based on speed."
msgstr ""

#: ../../docs/tutorials/3d/particles/process_material_properties.rst:51
msgid "Spawn"
msgstr ""

#: ../../docs/tutorials/3d/particles/process_material_properties.rst:56
msgid "Emission shape"
msgstr ""

#: ../../docs/tutorials/3d/particles/process_material_properties.rst:58
msgid ""
"Particles can emit from a single point in space or in a way that they fill "
"out a shape. The ``Shape`` property controls that shape. ``Point`` is the "
"default value. All particles emit from a single point in the center of the "
"particle system. When set to ``Sphere`` or ``Box``, particles emit in a way "
"that they fill out a sphere or a box shape evenly. You have full control "
"over the size of these shapes. ``Sphere Surface`` works like ``Sphere``, but "
"instead of filling it out, all particles spawn on the sphere's surface."
msgstr ""

#: ../../docs/tutorials/3d/particles/process_material_properties.rst:68
msgid "Simple particle emission shapes"
msgstr ""

#: ../../docs/tutorials/3d/particles/process_material_properties.rst:68
msgid ""
"Particles emitting from a point (left), in a sphere (middle), and in a box "
"(right)"
msgstr ""

#: ../../docs/tutorials/3d/particles/process_material_properties.rst:74
msgid "Ring-shaped particle system"
msgstr ""

#: ../../docs/tutorials/3d/particles/process_material_properties.rst:74
msgid "A ring-shaped particle system"
msgstr ""

#: ../../docs/tutorials/3d/particles/process_material_properties.rst:76
msgid ""
"The ``Ring`` emission shape makes particles emit in the shape of a ring. You "
"can control the ring's direction by changing the ``Ring Axis`` property. "
"``Ring Height`` controls the thickness of the ring along its axis. ``Ring "
"Radius`` and ``Ring Inner Radius`` control how wide the ring is and how "
"large the hole in the middle should be. The image shows a particle system "
"with a radius of ``2`` and an inner radius of ``1.5``, the axis points along "
"the global Z-axis."
msgstr ""

#: ../../docs/tutorials/3d/particles/process_material_properties.rst:83
msgid ""
"In addition to these relatively simple shapes, you can select the ``Points`` "
"or ``Directed Points`` option to create highly complex emission shapes. See "
"the :ref:`Complex emission shapes <doc_3d_particles_complex_shapes>` section "
"for a detailed explanation of how to set these up."
msgstr ""

#: ../../docs/tutorials/3d/particles/process_material_properties.rst:91
msgid ""
"The ``Angle`` property controls a particle's starting rotation `as described "
"above <#process-material-properties>`__. In order to have an actual effect "
"on the particle, you have to enable one of two properties: `Rotate Y "
"<#particle-flags>`__ rotates the particle around the particle system's Y-"
"axis. The ``Billboard`` property in the :ref:`Standard Material "
"<doc_standard_material_3d>`, if it is set to ``Particle Billboard``, rotates "
"the particle around the axis that points from the particle to the camera."
msgstr ""

#: ../../docs/tutorials/3d/particles/process_material_properties.rst:102
msgid ""
"The ``Direction`` property alone is not enough to see any particle movement. "
"Whatever values you set here only take effect once velocity or acceleration "
"properties are set, too."
msgstr ""

#: ../../docs/tutorials/3d/particles/process_material_properties.rst:105
msgid ""
"The ``Direction`` property is a vector that controls each particle's "
"direction of movement at the moment it is spawned. A value of ``(X=1,Y=0,"
"Z=0)`` would make all particles move sideways along the X-axis. For "
"something like a fountain where particles shoot out up in the air, a value "
"of ``(X=0,Y=1,Z=0)`` would be a good starting point."
msgstr ""

#: ../../docs/tutorials/3d/particles/process_material_properties.rst:113
msgid "Different values for particle direction"
msgstr ""

#: ../../docs/tutorials/3d/particles/process_material_properties.rst:113
msgid ""
"Different direction values: Y-axis only (left), equal values for X and Y "
"(middle), X and Y with gravity enabled (right)"
msgstr ""

#: ../../docs/tutorials/3d/particles/process_material_properties.rst:115
msgid ""
"After setting a direction, you will notice that all particles move in the "
"same direction in a straight line. The ``Spread`` property adds some "
"variation and randomness to each particle's direction. The higher the value, "
"the stronger the deviation from the original path. A value of ``0`` means "
"there is no spread at all while a value of ``180`` makes particles shoot out "
"in every direction. You could use this for something like pieces of debris "
"during an explosion effect."
msgstr ""

#: ../../docs/tutorials/3d/particles/process_material_properties.rst:124
msgid "Different values for particle spread"
msgstr ""

#: ../../docs/tutorials/3d/particles/process_material_properties.rst:124
msgid "No spread (left), 45 degree angle (middle), full 180 degrees (right)"
msgstr ""

#: ../../docs/tutorials/3d/particles/process_material_properties.rst:126
msgid ""
"The ``Flatness`` property limits the spread along the Y-axis. A value of "
"``0`` means there is no limit and a value of ``1`` will eliminate all "
"particle movement along the Y-axis. The particles will spread out completely "
"\"flat\"."
msgstr ""

#: ../../docs/tutorials/3d/particles/process_material_properties.rst:130
msgid ""
"You won't see any actual movement until you also set some values for the "
"velocity and acceleration properties below, so let's take a look at those "
"next."
msgstr ""

#: ../../docs/tutorials/3d/particles/process_material_properties.rst:134
msgid "Initial velocity"
msgstr ""

#: ../../docs/tutorials/3d/particles/process_material_properties.rst:136
msgid ""
"While the ``Direction`` property controls a particle's movement direction, "
"the ``Initial Velocity`` controls how fast it goes. It's separated into "
"``Velocity Min`` and ``Velocity Max``, both set to ``0`` by default, which "
"is why you don't see any movement initially. As soon as you set values for "
"either of these properties `as described above <#process-material-"
"properties>`__, the particles begin to move. The direction is multiplied by "
"these values, so you can make particles move in the opposite direction by "
"setting a negative velocity."
msgstr ""

#: ../../docs/tutorials/3d/particles/process_material_properties.rst:144
#, fuzzy
msgid "Accelerations"
msgstr "Uvod"

#: ../../docs/tutorials/3d/particles/process_material_properties.rst:149
msgid ""
"The next few property groups work closely together to control particle "
"movement and rotation. ``Gravity`` drags particles in the direction it "
"points at, which is straight down at the strength of Earth's gravity by "
"default. Gravity affects all particle movement. If your game uses physics "
"and the world's gravity can change at runtime, you can use this property to "
"keep the game's gravity in sync with particle gravity. A ``Gravity`` value "
"of ``(X=0,Y=0,Z=0)`` means no particle will ever move at all if none of the "
"other movement properties are set."
msgstr ""

#: ../../docs/tutorials/3d/particles/process_material_properties.rst:159
msgid "Different values for particle gravity"
msgstr ""

#: ../../docs/tutorials/3d/particles/process_material_properties.rst:159
msgid ""
"Left\\: (X=0,Y=-9.8,Z=0), middle\\: (X=0,Y=9.8,Z=0), right\\: (X=4,Y=2,Z=0)."
msgstr ""

#: ../../docs/tutorials/3d/particles/process_material_properties.rst:162
msgid "Angular velocity"
msgstr ""

#: ../../docs/tutorials/3d/particles/process_material_properties.rst:164
msgid ""
"``Angular Velocity`` controls a particle's speed of rotation `as described "
"above <#process-material-properties>`__. You can reverse the direction by "
"using negative numbers for ``Velocity Min`` or ``Velocity Max``. Like the "
"`Angle <#angle>`__ property, the rotation will only be visible if the "
"`Rotate Y <#particle-flags>`__ flag is set or the ``Particle Billboard`` "
"mode is selected in the :ref:`Standard Material <doc_standard_material_3d>`."
msgstr ""

#: ../../docs/tutorials/3d/particles/process_material_properties.rst:171
msgid ""
"The `Damping <#damping>`__ property has no effect on the angular velocity."
msgstr ""

#: ../../docs/tutorials/3d/particles/process_material_properties.rst:174
#, fuzzy
msgid "Linear acceleration"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/3d/particles/process_material_properties.rst:176
msgid ""
"A particle's velocity is a constant value: once it's set, it doesn't change "
"and the particle will always move at the same speed. You can use the "
"``Linear Accel`` property to change the speed of movement over a particle's "
"lifetime `as described above <#process-material-properties>`__. Positive "
"values will speed up the particle and make it move faster. Negative values "
"will slow it down until it stops and starts moving in the other direction."
msgstr ""

#: ../../docs/tutorials/3d/particles/process_material_properties.rst:185
msgid "Different values for particle linear acceleration"
msgstr ""

#: ../../docs/tutorials/3d/particles/process_material_properties.rst:185
msgid "Negative (top) and positive (bottom) linear acceleration"
msgstr ""

#: ../../docs/tutorials/3d/particles/process_material_properties.rst:187
msgid ""
"It's important to keep in mind that when we change acceleration, we're not "
"changing the velocity directly, we're changing the *change* in velocity. A "
"value of ``0`` on the acceleration curve does not stop the particle's "
"movement, it stops the change in the particle's movement. Whatever its "
"velocity was at that moment, it will keep moving at that velocity until the "
"acceleration is changed again."
msgstr ""

#: ../../docs/tutorials/3d/particles/process_material_properties.rst:194
msgid "Radial acceleration"
msgstr ""

#: ../../docs/tutorials/3d/particles/process_material_properties.rst:196
msgid ""
"The ``Radial Accel`` property adds a gravity-like force to all particles, "
"with the origin of that force at the particle system's current location. "
"Negative values make particles move towards the center, like the force of "
"gravity from a planet on objects in its orbit. Positive values make "
"particles move away from the center."
msgstr ""

#: ../../docs/tutorials/3d/particles/process_material_properties.rst:204
msgid "Different values for particle radial acceleration"
msgstr ""

#: ../../docs/tutorials/3d/particles/process_material_properties.rst:204
msgid "Negative (left) and positive (right) radial acceleration"
msgstr ""

#: ../../docs/tutorials/3d/particles/process_material_properties.rst:207
msgid "Tangential acceleration"
msgstr ""

#: ../../docs/tutorials/3d/particles/process_material_properties.rst:213
msgid "Tangents on a circle"
msgstr ""

#: ../../docs/tutorials/3d/particles/process_material_properties.rst:215
msgid ""
"This property adds particle acceleration in the direction of the tangent to "
"a circle on the particle system's XZ-plane with the origin at the system's "
"center and a radius the distance between each particle's current location "
"and the system's center projected onto that plane."
msgstr ""

#: ../../docs/tutorials/3d/particles/process_material_properties.rst:219
msgid "Let's unpack that."
msgstr ""

#: ../../docs/tutorials/3d/particles/process_material_properties.rst:221
msgid ""
"A tangent to a circle is a straight line that \"touches\" the circle in a "
"right angle to the circle's radius at the touch point. A circle on the "
"particle system's XZ-plane is the circle that you see when you look straight "
"down at the particle system from above."
msgstr ""

#: ../../docs/tutorials/3d/particles/process_material_properties.rst:229
msgid "Tangential acceleration from above"
msgstr ""

#: ../../docs/tutorials/3d/particles/process_material_properties.rst:231
msgid ""
"``Tangential Accel`` is always limited to that plane and never move "
"particles along the system's Y-axis. A particle's location is enough to "
"define such a circle where the distance to the system's center is the radius "
"if we ignore the vector's Y component."
msgstr ""

#: ../../docs/tutorials/3d/particles/process_material_properties.rst:235
msgid ""
"The ``Tangential Accel`` property will make particles orbit the particle "
"system's center, but the radius will increase constantly. Viewed from above, "
"particles will move away from the center in a spiral. Negative values "
"reverse the direction."
msgstr ""

#: ../../docs/tutorials/3d/particles/process_material_properties.rst:242
msgid ""
"The ``Damping`` property gradually stops all movement. Each frame, a "
"particle's movement is slowed down a little unless the total acceleration is "
"greater than the damping effect. If it isn't, the particle will keep slowing "
"down until it doesn't move at all. The greater the value, the less time it "
"takes to bring particles to a complete halt."
msgstr ""

#: ../../docs/tutorials/3d/particles/process_material_properties.rst:248
#, fuzzy
msgid "Attractor interaction"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/3d/particles/process_material_properties.rst:250
msgid ""
"If you want the particle system to interact with :ref:`particle attractors "
"<doc_3d_particles_attractors>`, you have to check the ``Enabled`` property. "
"When it is disabled, the particle system ignores all particle attractors."
msgstr ""

#: ../../docs/tutorials/3d/particles/process_material_properties.rst:255
msgid "Display"
msgstr ""

#: ../../docs/tutorials/3d/particles/process_material_properties.rst:260
msgid ""
"``Scale`` controls a particle's size `as described above <#process-material-"
"properties>`__. You can set different values for ``Scale Min`` and ``Scale "
"Max`` to randomize each particle's size. Negative values are not allowed, so "
"you won't be able to flip particles with this property. If you emit "
"particles as billboards, the ``Keep Size`` property on the :ref:`Standard "
"Material <doc_standard_material_3d>` in your draw passes has to be enabled "
"for any scaling to have an effect."
msgstr ""

#: ../../docs/tutorials/3d/particles/process_material_properties.rst:269
msgid ""
"The ``Color`` property controls a particle's initial color. It will have an "
"effect only after the ``Use As Albedo`` property in the ``Vertex Color`` "
"group of the :ref:`Standard Material <doc_standard_material_3d>` is enabled. "
"This property is multiplied with color coming from the particle material's "
"own ``Color`` or ``Texture`` property."
msgstr ""

#: ../../docs/tutorials/3d/particles/process_material_properties.rst:278
msgid "Particle color ramp"
msgstr ""

#: ../../docs/tutorials/3d/particles/process_material_properties.rst:278
#, fuzzy
msgid "Setting up a color ramp"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/3d/particles/process_material_properties.rst:280
msgid ""
"There are two ``Ramp`` properties in the ``Color`` group. These allow you to "
"define a range of colors that are used to set the particle's color. The "
"``Color Ramp`` property changes a particle's color over the course of its "
"lifetime. It moves through the entire range of colors you defined. The "
"``Color Initial Ramp`` property selects the particle's initial color from a "
"random position on the color ramp."
msgstr ""

#: ../../docs/tutorials/3d/particles/process_material_properties.rst:286
msgid ""
"To set up a color ramp, click on the box next to the property name and from "
"the dropdown menu select ``New GradientTexture1D``. Click on the box again "
"to open the texture's details. Find the ``Gradient`` property, click on the "
"box next to it and select ``New Gradient``. Click on that box again and you "
"will see a color range. Click anywhere on that range to insert a new marker. "
"You can move the marker with the mouse and delete it by clicking the right "
"mouse button. When a marker is selected, you can use the color picker next "
"to the range to change its color."
msgstr ""

#: ../../docs/tutorials/3d/particles/process_material_properties.rst:295
#, fuzzy
msgid "Hue variation"
msgstr "Uvod"

#: ../../docs/tutorials/3d/particles/process_material_properties.rst:297
msgid ""
"Like the ``Color`` property, ``Hue Variation`` controls a particle's color, "
"but in a different way. It does so not by setting color values directly, but "
"by *shifting the color's hue*."
msgstr ""

#: ../../docs/tutorials/3d/particles/process_material_properties.rst:301
msgid ""
"Hue describes a color's pigment: red, orange, yellow, green and so on. It "
"does not tell you anything about how bright or how saturated the color is. "
"The ``Hue Variation`` property controls the range of available hues `as "
"described above <#process-material-properties>`__."
msgstr ""

#: ../../docs/tutorials/3d/particles/process_material_properties.rst:305
msgid ""
"It works on top of the particle's current color. The values you set for "
"``Variation Min`` and ``Variation Max`` control how far the hue is allowed "
"to shift in either direction. A higher value leads to more color variation "
"while a low value limits the available colors to the closest neighbors of "
"the original color."
msgstr ""

#: ../../docs/tutorials/3d/particles/process_material_properties.rst:313
msgid "Different values for hue variation"
msgstr ""

#: ../../docs/tutorials/3d/particles/process_material_properties.rst:313
msgid ""
"Different values for hue variation, both times with blue as base color: 0.6 "
"(left) and 0.1 (right)"
msgstr ""

#: ../../docs/tutorials/3d/particles/process_material_properties.rst:320
msgid ""
"The ``Animation`` property group controls the behavior of sprite sheet "
"animations in the particle's :ref:`Standard Material "
"<doc_standard_material_3d>`. The ``Min``, ``Max``, and ``Curve`` values work "
"`as described above <#process-material-properties>`__."
msgstr ""

#: ../../docs/tutorials/3d/particles/process_material_properties.rst:324
msgid ""
"An animated sprite sheet is a texture that contains several smaller images "
"aligned on a grid. The images are shown one after the other so fast that "
"they combine to play a short animation, like a flipbook. You can use them "
"for animated particles like smoke or fire. These are the steps to create an "
"animated particle system:"
msgstr ""

#: ../../docs/tutorials/3d/particles/process_material_properties.rst:333
msgid "A sprite sheet"
msgstr ""

#: ../../docs/tutorials/3d/particles/process_material_properties.rst:333
msgid "An 8x8 animated smoke sprite sheet"
msgstr ""

#: ../../docs/tutorials/3d/particles/process_material_properties.rst:335
msgid ""
"Import a sprite sheet texture into the engine. If you don't have one at "
"hand, you can download the :download:`high-res version of the example image "
"<img/particle_sprite_smoke.webp>`."
msgstr ""

#: ../../docs/tutorials/3d/particles/process_material_properties.rst:336
msgid ""
"Set up a particle system with at least one draw pass and assign a ``Standard "
"Material`` to the mesh in that draw pass."
msgstr ""

#: ../../docs/tutorials/3d/particles/process_material_properties.rst:337
msgid ""
"Assign the sprite sheet to the ``Texture`` property in the ``Albedo`` group"
msgstr ""

#: ../../docs/tutorials/3d/particles/process_material_properties.rst:338
msgid ""
"Set the material's ``Billboard`` property to ``Particle Billboard``. Doing "
"so makes the ``Particles Anim`` group available in the material."
msgstr ""

#: ../../docs/tutorials/3d/particles/process_material_properties.rst:339
msgid ""
"Set ``H Frames`` to the number of columns and ``V Frames`` to the number of "
"rows in the sprite sheet."
msgstr ""

#: ../../docs/tutorials/3d/particles/process_material_properties.rst:340
msgid "Check ``Loop`` if you want the animation to keep repeating."
msgstr ""

#: ../../docs/tutorials/3d/particles/process_material_properties.rst:342
msgid ""
"That's it for the Standard Material. You won't see any animation right away. "
"This is where the ``Animation`` properties come in. The ``Speed`` properties "
"control how fast the sprite sheet animates. Set ``Speed Min`` and ``Speed "
"Max`` to ``1`` and you should see the animation playing. The ``Offset`` "
"properties control where the animation starts on a newly spawned particle. "
"By default, it will always be the first image in the sequence. You can add "
"some variety by changing ``Offset Min`` and ``Offset Max`` to randomize the "
"starting position."
msgstr ""

#: ../../docs/tutorials/3d/particles/process_material_properties.rst:353
msgid "Animated particles"
msgstr ""

#: ../../docs/tutorials/3d/particles/process_material_properties.rst:353
msgid "Three different particle systems using the same smoke sprite sheet"
msgstr ""

#: ../../docs/tutorials/3d/particles/process_material_properties.rst:368
msgid ""
"If your sprite sheet contains 64 (8x8) images and the particle's lifetime is "
"set to ``1 second``, the animation will be very smooth at **64 FPS** (1 "
"second / 64 images). if the lifetime is set to ``2 seconds``, it will still "
"be fairly smooth at **32 FPS**. But if the particle is alive for ``8 "
"seconds``, the animation will be visibly choppy at **8 FPS**. In order to "
"make the animation smooth again, you need to increase the animation speed to "
"something like ``3`` to reach an acceptable framerate."
msgstr ""

#: ../../docs/tutorials/3d/particles/process_material_properties.rst:379
msgid "Animated particles lifetimes"
msgstr ""

#: ../../docs/tutorials/3d/particles/process_material_properties.rst:379
msgid ""
"The same particle system at different lifetimes: 1 second (left), 2 seconds "
"(middle), 8 seconds (right)"
msgstr ""

#: ../../docs/tutorials/3d/particles/process_material_properties.rst:381
msgid ""
"Note that the GPUParticles3D node's **Fixed FPS** also affects animation "
"playback. For smooth animation playback, it's recommended to set it to 0 so "
"that the particle is simulated on every rendered frame. If this is not an "
"option for your use case, set **Fixed FPS** to be equal to the effective "
"framerate used by the flipbook animation (see above for the formula)."
msgstr ""

#: ../../docs/tutorials/3d/particles/process_material_properties.rst:390
msgid "Turbulence"
msgstr ""

#: ../../docs/tutorials/3d/particles/process_material_properties.rst:392
msgid ""
"Turbulence adds noise to particle movement, creating interesting and lively "
"patterns. Check the box next to the ``Enabled`` property to activate it. A "
"number of new properties show up that control the movement speed, noise "
"pattern and overall influence on the particle system. You can find a "
"detailed explanation of these in the section on :ref:`particle turbulence "
"<doc_3d_particles_turbulence>`."
msgstr ""

#: ../../docs/tutorials/3d/particles/process_material_properties.rst:401
msgid "Collision"
msgstr ""

#: ../../docs/tutorials/3d/particles/process_material_properties.rst:403
msgid ""
"The ``Mode`` property controls how and if emitters collide with particle "
"collision nodes. Set it to ``Disabled`` to disable any collision for this "
"particle system. Set it to ``Hide On Contact`` if you want particles to "
"disappear as soon as they collide. Set it to ``Constant`` to make particles "
"collide and bounce around. You will see two new properties appear in the "
"inspector. They control how particles behave during collision events."
msgstr ""

#: ../../docs/tutorials/3d/particles/process_material_properties.rst:409
msgid ""
"A high ``Friction`` value will reduce sliding along surfaces. This is "
"especially helpful if particles collide with sloped surfaces and you want "
"them to stay in place instead of sliding all the way to the bottom, like "
"snow falling on a mountain. A high ``Bounce`` value will make particles "
"bounce off surfaces they collide with, like rubber balls on a solid floor."
msgstr ""

#: ../../docs/tutorials/3d/particles/process_material_properties.rst:415
msgid ""
"If the ``Use Scale`` property is enabled, the :ref:`collision base size "
"<doc_3d_particles_properties_collision>` is multiplied by the particle's "
"`current scale <#scale>`__. You can use this to make sure that the rendered "
"size and the collision size match for particles with random scale or scale "
"that varies over time."
msgstr ""

#: ../../docs/tutorials/3d/particles/process_material_properties.rst:420
msgid ""
"You can learn more about particle collisions in the :ref:`Collisions "
"<doc_3d_particles_collision>` section in this manual."
msgstr ""

#: ../../docs/tutorials/3d/particles/process_material_properties.rst:424
msgid "Sub-emitter"
msgstr ""

#: ../../docs/tutorials/3d/particles/process_material_properties.rst:430
msgid "Sub-emitter modes"
msgstr ""

#: ../../docs/tutorials/3d/particles/process_material_properties.rst:430
#, fuzzy
msgid "The available sub-emitter modes"
msgstr "Ne postoje ograničenja prilikom korištenja Godot-a"

#: ../../docs/tutorials/3d/particles/process_material_properties.rst:432
msgid ""
"The ``Mode`` property controls how and when sub-emitters are spawned. Set it "
"to ``Disabled`` and no sub-emitters will ever be spawned. Set it to "
"``Constant`` to make sub-emitters spawn continuously at a constant rate. The "
"``Frequency`` property controls how often that happens within the span of "
"one second. Set the mode to ``At End`` to make the sub-emitter spawn at the "
"end of the parent particle's lifetime, right before it is destroyed. The "
"``Amount At End`` property controls how many sub-emitters will be spawned. "
"Set the mode to ``At Collision`` to make sub-emitters spawn when a particle "
"collides with the environment. The ``Amount At Collision`` property controls "
"how many sub-emitters will be spawned."
msgstr ""

#: ../../docs/tutorials/3d/particles/process_material_properties.rst:441
msgid ""
"When the ``Keep Velocity`` property is enabled, the newly spawned sub-"
"emitter starts off with the parent particle's velocity at the time the sub-"
"emitter is created."
msgstr ""

#: ../../docs/tutorials/3d/particles/process_material_properties.rst:444
msgid ""
"See the :ref:`Sub-emitters <doc_3d_particles_subemitters>` section in this "
"manual for a detailed explanation of how to add a sub-emitter to a particle "
"system."
msgstr ""

#: ../../docs/tutorials/3d/particles/subemitters.rst:4
msgid "Particle sub-emitters"
msgstr ""

#: ../../docs/tutorials/3d/particles/subemitters.rst:-1
msgid "Chained sub-emitters"
msgstr ""

#: ../../docs/tutorials/3d/particles/subemitters.rst:9
msgid ""
"Sometimes a visual effect cannot be created with a single particle system "
"alone. Sometimes a particle system needs to be spawned as a response to "
"something that happens in another particle system. Fireworks are a good "
"example of that. They usually consist of several stages of explosions that "
"happen in sequence. Sub-emitters are a good way to achieve this kind of "
"effect."
msgstr ""

#: ../../docs/tutorials/3d/particles/subemitters.rst:19
msgid "Assign sub-emitter"
msgstr ""

#: ../../docs/tutorials/3d/particles/subemitters.rst:19
msgid "Click to assign a sub-emitter..."
msgstr ""

#: ../../docs/tutorials/3d/particles/subemitters.rst:25
msgid "List particle systems"
msgstr ""

#: ../../docs/tutorials/3d/particles/subemitters.rst:25
msgid "\\...and select one from the scene"
msgstr ""

#: ../../docs/tutorials/3d/particles/subemitters.rst:27
msgid ""
"A sub-emitter is a particle system that spawns as a child of another "
"particle system. You can add sub-emitters to sub-emitters, chaining particle "
"effects as deep as you like."
msgstr ""

#: ../../docs/tutorials/3d/particles/subemitters.rst:30
msgid ""
"To create a sub-emitter, you need at least two particle systems in the same "
"scene. One of them will be the parent and one will be set as the child. Find "
"the ``Sub Emitter`` property on the parent and click the box next to it to "
"assign the sub-emitter. You will see a list of available particle systems in "
"the scene. Select one and click the confirmation button."
msgstr ""

#: ../../docs/tutorials/3d/particles/subemitters.rst:35
msgid ""
"Particle systems from instanced scenes can be set as sub-emitters too, as "
"long as the ``Editable Children`` property is enabled on the instanced "
"scene. This also works the other way around: You can assign a sub-emitter to "
"a particle system in an instanced scene, even one coming from a different "
"instanced scene."
msgstr ""

#: ../../docs/tutorials/3d/particles/subemitters.rst:42
msgid ""
"When you set a particle system as the sub-emitter of another, the system "
"stops emitting, even if the ``Emitting`` property was checked. Don't worry, "
"it didn't break. This happens to every particle system as soon as it becomes "
"a sub-emitter. You also won't be able to re-enable the property as long as "
"the particle system is used as a sub-emitter."
msgstr ""

#: ../../docs/tutorials/3d/particles/subemitters.rst:49
msgid ""
"Even though the parent particle system can be selected from the list of "
"available particle systems, a particle system which is its own sub-emitter "
"does not work in Godot. It will simply not spawn. The same is true for any "
"other kind of recursive or self-referential sub-emitter setup."
msgstr ""

#: ../../docs/tutorials/3d/particles/subemitters.rst:55
msgid "Emitter mode"
msgstr ""

#: ../../docs/tutorials/3d/particles/subemitters.rst:57
msgid ""
"When you assign a sub-emitter, you don't see it spawn right away. Emitting "
"is disabled by default and needs to be enabled first. Set the ``Mode`` "
"property in the ``Sub Emitter`` group of the :ref:`ParticleProcessMaterial "
"<doc_process_material_properties_subemitter>` to something other than "
"``Disabled``."
msgstr ""

#: ../../docs/tutorials/3d/particles/subemitters.rst:61
msgid ""
"The emitter mode also determines how many sub-emitter particles are spawned. "
"``Constant`` spawns a single particle at a frequency set by the "
"``Frequency`` property. For ``At End`` and ``At Collision`` you can set the "
"amount directly with the ``Amount At End`` and the ``Amount At Collision`` "
"properties."
msgstr ""

#: ../../docs/tutorials/3d/particles/subemitters.rst:69
msgid ""
"One thing to keep in mind is that the total number of active particles from "
"the sub-emitter is always capped by the ``Amount`` property on the sub-"
"emitter particle system. If you find that there are not enough particles "
"spawned from the sub-emitter, you might have to increase the amount in the "
"particle system."
msgstr ""

#: ../../docs/tutorials/3d/particles/subemitters.rst:74
msgid ""
"Some emitter properties are ignored when a particle system is spawned as a "
"sub-emitter. The ``Explosiveness`` property, for example, has no effect. "
"Depending on the emitter mode, the particles are either spawned sequentially "
"at fixed intervals or explosively all at once."
msgstr ""

#: ../../docs/tutorials/3d/particles/trails.rst:4
msgid "3D Particle trails"
msgstr ""

#: ../../docs/tutorials/3d/particles/trails.rst:13
msgid "Particle trail params"
msgstr ""

#: ../../docs/tutorials/3d/particles/trails.rst:13
#, fuzzy
msgid "Setting up particle trails"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/3d/particles/trails.rst:15
msgid ""
"Godot provides several types of trails you can add to a particle system. "
"Before you can work with trails, you need to set up a couple of parameters "
"first. Create a new particle system and assign a process material :ref:`as "
"described before <doc_creating_3d_particle_system>`. In the ``Trails`` group "
"of the particle system, check the box next to ``Enabled`` and increase the "
"emission duration by setting ``Lifetime`` to something like ``0.8``. On the "
"process material, set ``Direction`` to ``(X=0,Y=1.0,Z=0)`` and ``Initial "
"Velocity`` to ``10.0`` for both ``Min`` and ``Max``."
msgstr ""

#: ../../docs/tutorials/3d/particles/trails.rst:23
msgid ""
"The only thing that's still missing is a mesh for the draw pass. The type of "
"mesh that you set here controls what kind of particle trail you will end up "
"with."
msgstr ""

#: ../../docs/tutorials/3d/particles/trails.rst:27
msgid "Ribbon trails"
msgstr ""

#: ../../docs/tutorials/3d/particles/trails.rst:33
msgid "Particle ribbon"
msgstr ""

#: ../../docs/tutorials/3d/particles/trails.rst:33
msgid "Important ribbon mesh parameters"
msgstr ""

#: ../../docs/tutorials/3d/particles/trails.rst:35
msgid ""
"The simplest type of particle trail is the ribbon trail. Navigate to the "
"``Draw Passes`` section and select ``New RibbonTrailMesh`` from the options "
"for ``Pass 1``. A :ref:`RibbonTrailMesh <class_RibbonTrailMesh>` is a simple "
"quad that is divided into sections and then stretched and repeated along "
"those sections."
msgstr ""

#: ../../docs/tutorials/3d/particles/trails.rst:40
msgid ""
"Assign a new :ref:`Standard Material <doc_standard_material_3d>` to the "
"``Material`` property and enable ``Use Particle Trails`` in the "
"``Transform`` property group. The particles should now be emitting in trails."
msgstr ""

#: ../../docs/tutorials/3d/particles/trails.rst:44
msgid ""
"You have two options for the ribbon mesh ``Shape`` parameter. ``Cross`` "
"creates two perpendicular quads, making the particle trail a little more "
"three-dimensional. This really only makes sense if you don't draw the trails "
"in ``Particle Billboard`` mode and helps when looking at the particles from "
"different angles. The ``Flat`` option limits the mesh to a single quad and "
"works best with billboard particles."
msgstr ""

#: ../../docs/tutorials/3d/particles/trails.rst:50
msgid ""
"The ``Size`` parameter controls the trail's width. Use it to make trails "
"wider or more narrow."
msgstr ""

#: ../../docs/tutorials/3d/particles/trails.rst:53
msgid ""
"``Sections``, ``Section Length`` and ``Section Segments`` all work together "
"to control how smooth the particle trail looks. When a particle trail does "
"not travel in a straight line, the more sections it has the smoother it "
"looks as it bends and swirls. ``Section Length`` controls the length of each "
"section. Multiply this value by the number of sections to know the trail's "
"total length."
msgstr ""

#: ../../docs/tutorials/3d/particles/trails.rst:62
msgid "Particle ribbon sections"
msgstr ""

#: ../../docs/tutorials/3d/particles/trails.rst:62
msgid ""
"3 sections, 1m section length (left) vs. 12 sections, 0.25m section length "
"(right). Notice how the total length of the trails stays the same."
msgstr ""

#: ../../docs/tutorials/3d/particles/trails.rst:64
msgid ""
"The ``Section Segments`` parameter further subdivides each section into "
"segments. It has no effect on the smoothness of the trail's sections, "
"though. Instead, it controls the smoothness of the particle trail's overall "
"shape. The ``Curve`` property defines this shape. Click the box next to "
"``Curve`` and assign or create a new curve. The trail will be shaped just "
"like the curve with the curve's value at ``0.0`` at the trail's head and the "
"curve's value at ``1.0`` at the trail's tail."
msgstr ""

#: ../../docs/tutorials/3d/particles/trails.rst:74
msgid "Particle ribbon curves"
msgstr ""

#: ../../docs/tutorials/3d/particles/trails.rst:74
msgid ""
"Particle trails shaped by different curves. The trails move from left to "
"right."
msgstr ""

#: ../../docs/tutorials/3d/particles/trails.rst:76
msgid ""
"Depending on the complexity of the curve, the particle trail's shape will "
"not look very smooth when the number of sections is low. This is where the "
"``Section Segments`` property comes in. Increasing the amount of section "
"segments adds more vertices to the trail's sides so that it can follow the "
"curve more closely."
msgstr ""

#: ../../docs/tutorials/3d/particles/trails.rst:84
msgid "Particle ribbon segments"
msgstr ""

#: ../../docs/tutorials/3d/particles/trails.rst:84
msgid ""
"Particle trail shape smoothness: 1 segment per section (top), 12 segments "
"per section (bottom)"
msgstr ""

#: ../../docs/tutorials/3d/particles/trails.rst:87
msgid "Tube trails"
msgstr ""

#: ../../docs/tutorials/3d/particles/trails.rst:89
msgid ""
"Tube trails share a lot of their properties with ribbon trails. The big "
"difference between them is that tube trails emit cylindrical meshes instead "
"of quads."
msgstr ""

#: ../../docs/tutorials/3d/particles/trails.rst:95
msgid "Particle tube trails"
msgstr ""

#: ../../docs/tutorials/3d/particles/trails.rst:95
msgid "Tube trails emit cylindrical particles"
msgstr ""

#: ../../docs/tutorials/3d/particles/trails.rst:97
msgid ""
"To create a tube trail, navigate to the ``Draw Passes`` section and select "
"``New TubeTrailMesh`` from the options for ``Pass 1``. A :ref:`TubeTrailMesh "
"<class_TubeTrailMesh>` is a cylinder that is divided into sections and then "
"stretched and repeated along those sections. Assign a new :ref:`Standard "
"Material <doc_standard_material_3d>` to the ``Material`` property and enable "
"``Use Particle Trails`` in the ``Transform`` property group. The particles "
"should now be emitting in long, cylindrical trails."
msgstr ""

#: ../../docs/tutorials/3d/particles/trails.rst:108
msgid "Particle tube"
msgstr ""

#: ../../docs/tutorials/3d/particles/trails.rst:108
msgid "Important tube mesh parameters"
msgstr ""

#: ../../docs/tutorials/3d/particles/trails.rst:110
msgid ""
"The ``Radius`` and ``Radial Steps`` properties are to tube trails what "
"``Size`` is to ribbon trails. ``Radius`` defines the radius of the tube and "
"increases or decreases its overall size. ``Radial Steps`` controls the "
"number of sides around the tube's circumference. A higher value increases "
"the resolution of the tube's cap."
msgstr ""

#: ../../docs/tutorials/3d/particles/trails.rst:115
msgid ""
"``Sections`` and ``Section Length`` work the same for tube trails and ribbon "
"trails. They control how smooth the tube trail looks when it is bending and "
"twisting instead of moving in a straight line. Increasing the number of "
"sections will make it look smoother. Change the ``Section Length`` property "
"to change the length of each section and with it the total length of the "
"trail. ``Section Rings`` is the tube equivalent of the ``Section Segments`` "
"property for ribbons. It subdivides the sections and adds more geometry to "
"the tube to better fit the custom shape defined in the ``Curve`` property."
msgstr ""

#: ../../docs/tutorials/3d/particles/trails.rst:122
msgid ""
"You can shape tube trails with curves, just as you can with ribbon trails. "
"Click the box next to the ``Curve`` property and assign or create a new "
"curve. The trail will be shaped like the curve with the curve's value at "
"``0.0`` at the trail's head and the curve's value at ``1.0`` at the trail's "
"tail."
msgstr ""

#: ../../docs/tutorials/3d/particles/trails.rst:129
msgid "Particle tubes"
msgstr ""

#: ../../docs/tutorials/3d/particles/trails.rst:129
msgid ""
"Particle tube trails with a custom curve shape: 4 radial steps, 3 sections, "
"1 section ring (left), 12 radial steps, 9 sections, 3 section rings (right)"
msgstr ""

#: ../../docs/tutorials/3d/particles/trails.rst:132
msgid ""
"An important property you might want to set is ``Transform Align`` in the "
"particle system's ``Drawing`` group. If you leave it as is, the tubes will "
"not preserve volume; they flatten out as they move because their Y-axis "
"keeps pointing up even as they change direction. This can cause a lot of "
"rendering artifacts. Set the property to ``Y to Velocity`` instead and each "
"particle trail keeps its Y-axis aligned along the direction of its movement."
msgstr ""

#: ../../docs/tutorials/3d/particles/trails.rst:141
msgid "Particle tubes aligned"
msgstr ""

#: ../../docs/tutorials/3d/particles/trails.rst:141
msgid ""
"Particle tube trails without alignment (left) and with Y-axis aligned to "
"velocity (right)"
msgstr ""

#: ../../docs/tutorials/3d/particles/turbulence.rst:-1
#: ../../docs/tutorials/3d/particles/turbulence.rst:4
msgid "Particle turbulence"
msgstr ""

#: ../../docs/tutorials/3d/particles/turbulence.rst:9
msgid ""
"Turbulence uses a noise texture to add variation and interesting patterns to "
"particle movement. It can be combined with :ref:`particle attractors "
"<doc_3d_particles_attractors>` and :ref:`collision "
"<doc_3d_particles_collision>` nodes to create even more complex looking "
"behavior."
msgstr ""

#: ../../docs/tutorials/3d/particles/turbulence.rst:17
#, fuzzy
msgid "Turbulence properties"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/3d/particles/turbulence.rst:17
#, fuzzy
msgid "Particle turbulence properties"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/3d/particles/turbulence.rst:19
msgid ""
"There are two things you have to do before turbulence has any effect on a "
"particle system. First you must add movement to the particle system. "
"Turbulence modifies a particle's movement direction and speed, but it "
"doesn't create any. It is enough to give the particle system some gravity, "
"but you can just as well create a number of attractors if you want the "
"particles to follow a more complex movement path. Second, you need to :ref:"
"`enable turbulence in the particle process material "
"<doc_process_material_properties_turbulence>`. Once enabled, you have access "
"to all the turbulence properties."
msgstr ""

#: ../../docs/tutorials/3d/particles/turbulence.rst:28
msgid ""
"Turbulence makes use of 3D noise, which has a high performance cost on the "
"GPU. Only enable turbulence on a few particle systems on screen at most. "
"Using turbulence is not recommended when targeting mobile/web platforms."
msgstr ""

#: ../../docs/tutorials/3d/particles/turbulence.rst:33
#, fuzzy
msgid "Noise properties"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/3d/particles/turbulence.rst:35
msgid ""
"The basis for particle turbulence is a noise pattern. There are several "
"properties that allow you to manipulate different attributes of this pattern."
msgstr ""

#: ../../docs/tutorials/3d/particles/turbulence.rst:38
msgid ""
"The ``Noise Strength`` property controls the pattern's contrast, which "
"affects the overall turbulence sharpness. A lower value creates a softer "
"pattern where individual movement paths are not as sharply separated from "
"another. Set this to a higher number to make the pattern more distinct."
msgstr ""

#: ../../docs/tutorials/3d/particles/turbulence.rst:46
msgid "Turbulence noise strength"
msgstr ""

#: ../../docs/tutorials/3d/particles/turbulence.rst:46
msgid ""
"At a value of 1 (left), the noise strength produces softer turbulence "
"patterns than at 20 (right)"
msgstr ""

#: ../../docs/tutorials/3d/particles/turbulence.rst:48
msgid ""
"The ``Noise Scale`` property controls the pattern's frequency. It basically "
"changes the noise texture's UV scale where a smaller value produces finer "
"detail, but repeating patterns become noticeable faster. A larger value "
"results in a weaker turbulence pattern overall, but the particle system can "
"cover a larger area before repetition starts to become an issue."
msgstr ""

#: ../../docs/tutorials/3d/particles/turbulence.rst:56
msgid "Turbulence noise scale"
msgstr ""

#: ../../docs/tutorials/3d/particles/turbulence.rst:56
msgid ""
"Turbulence noise scale produces finer details at a value of 1.5 (left) than "
"at 6 (right)"
msgstr ""

#: ../../docs/tutorials/3d/particles/turbulence.rst:58
msgid ""
"The ``Noise Speed`` property takes a vector and controls the noise panning "
"speed and direction. This allows you to move the noise pattern over time, "
"which adds another layer of movement variation to the particle system."
msgstr ""

#: ../../docs/tutorials/3d/particles/turbulence.rst:64
msgid ""
"Don't mix up particle movement speed and noise panning speed! They are two "
"different things. Particle movement is determined by a number of properties, "
"including the turbulence noise. The ``Noise Speed`` property moves the "
"pattern itself, which in turn changes where the noise affects the particles."
msgstr ""

#: ../../docs/tutorials/3d/particles/turbulence.rst:69
msgid ""
"At a value of ``(X=0,Y=0,Z=0)``, the noise pattern doesn't move at all. The "
"influence on particle movement stays the same at any given point. Set the "
"speed to ``(X=1,Y=0,Z=0)`` instead, and the noise pattern moves along the X-"
"axis."
msgstr ""

#: ../../docs/tutorials/3d/particles/turbulence.rst:76
msgid "Turbulence noise speed"
msgstr ""

#: ../../docs/tutorials/3d/particles/turbulence.rst:76
msgid ""
"Different noise speed values. Left\\: (X=0,Y=0,Z=0), middle\\: (X=0.5,Y=0.5,"
"Z=0.5), right\\: (X=0,Y=-2,Z=0)."
msgstr ""

#: ../../docs/tutorials/3d/particles/turbulence.rst:78
msgid ""
"The ``Noise Speed Random`` property adds some randomness to the noise "
"panning speed. This helps with breaking up visible patterns, especially at "
"higher panning speeds when repetition becomes noticeable faster."
msgstr ""

#: ../../docs/tutorials/3d/particles/turbulence.rst:83
#, fuzzy
msgid "Influence properties"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/3d/particles/turbulence.rst:85
msgid ""
"The influence properties determine how much each particle is affected by "
"turbulence. Use ``Influence Min`` to set a minimum value and ``Influence "
"Max`` to set a maximum value. When a particle spawns, the influence is "
"randomly chosen from within this range. You can also set up a curve with the "
"``Influence Over Life`` property that modifies that value over each "
"particle's lifetime. These three properties together control the strength of "
"the turbulence's effect on the particle system :ref:`as described before "
"<doc_process_material_properties>`."
msgstr ""

#: ../../docs/tutorials/3d/particles/turbulence.rst:92
msgid ""
"Since these properties affect the overall influence of the turbulence over a "
"particle system, both movement direction and speed change as you set "
"different values. A stronger influence causes a particle to move faster and "
"all particles to follow along narrower paths as a result of that."
msgstr ""

#: ../../docs/tutorials/3d/particles/turbulence.rst:99
msgid "Turbulence influence"
msgstr ""

#: ../../docs/tutorials/3d/particles/turbulence.rst:99
msgid ""
"Notice how the particle paths are more narrow and less spread out at high "
"influence values (right)"
msgstr ""

#: ../../docs/tutorials/3d/particles/turbulence.rst:102
#, fuzzy
msgid "Displacement properties"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/3d/particles/turbulence.rst:104
msgid ""
"Displacement changes a particle's starting position. Use ``Initial "
"Displacement Min`` to set a lower limit and ``Initial Displacement Max`` to "
"set an upper limit. When a particle spawns, the amount of displacement is "
"randomly chosen from within this range and multiplied by a random direction."
msgstr ""

#: ../../docs/tutorials/3d/particles/turbulence.rst:109
msgid ""
"Displacement is very useful to break up regular shapes or to create complex "
"shapes from simpler ones. The only difference between the particle systems "
"in the screenshot below is the value given to the displacement properties."
msgstr ""

#: ../../docs/tutorials/3d/particles/turbulence.rst:116
msgid "Turbulence displacement"
msgstr ""

#: ../../docs/tutorials/3d/particles/turbulence.rst:116
msgid ""
"No displacement (left), displacement value of 5 (middle), displacement range "
"[-20, 20] (right)"
msgstr ""

#: ../../docs/tutorials/3d/particles/attractors.rst:4
msgid "3D Particle attractors"
msgstr ""

#: ../../docs/tutorials/3d/particles/attractors.rst:-1
msgid "Particle attractors"
msgstr ""

#: ../../docs/tutorials/3d/particles/attractors.rst:9
msgid ""
"Particle attractors are nodes that apply a force to all particles within "
"their reach. They pull particles closer or push them away based on the "
"direction of that force. There are three types of attractors: :ref:"
"`class_GPUParticlesAttractorBox3D`, :ref:"
"`class_GPUParticlesAttractorSphere3D`, and :ref:"
"`class_GPUParticlesAttractorVectorField3D`. You can instantiate them at "
"runtime and change their properties from gameplay code; you can even animate "
"and combine them for complex attraction effects."
msgstr ""

#: ../../docs/tutorials/3d/particles/attractors.rst:18
msgid "Particle attractors are not yet implemented for 2D particle systems."
msgstr ""

#: ../../docs/tutorials/3d/particles/attractors.rst:20
msgid ""
"The first thing you have to do if you want to use attractors is enable the "
"``Attractor Interaction`` property on the ParticleProcessMaterial. Do this "
"for every particle system that needs to react to attractors. Like most "
"properties in Godot, you can also change this at runtime."
msgstr ""

#: ../../docs/tutorials/3d/particles/attractors.rst:25
#: ../../docs/tutorials/3d/particles/collision.rst:19
#, fuzzy
msgid "Common properties"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/3d/particles/attractors.rst:31
msgid "Common particle attractor properties"
msgstr ""

#: ../../docs/tutorials/3d/particles/attractors.rst:31
#, fuzzy
msgid "Common attractor properties"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/3d/particles/attractors.rst:33
msgid ""
"There are some properties that you can find on all attractors. They're "
"located in the ``GPUParticlesAttractor3D`` section in the inspector."
msgstr ""

#: ../../docs/tutorials/3d/particles/attractors.rst:36
msgid ""
"``Strength`` controls how strong the attractor force is. A positive value "
"pulls particles closer to the attractor's center, while a negative value "
"pushes them away."
msgstr ""

#: ../../docs/tutorials/3d/particles/attractors.rst:39
msgid ""
"``Attenuation`` controls the strength falloff within the attractor's "
"influence region. Every particle attractor has a boundary. Its strength is "
"weakest at the border of this boundary and strongest at its center. "
"Particles outside of the boundary are not affected by the attractor at all. "
"The attenuation curve controls how the strength weakens over that distance. "
"A straight line means that the strength is proportional to the distance: if "
"a particle is halfway between the boundary and the center, the attractor "
"strength will be half of what it is at the center. Different curve shapes "
"change how fast particles accelerate towards the attractor."
msgstr ""

#: ../../docs/tutorials/3d/particles/attractors.rst:51
msgid "Different attractor attenuation curves"
msgstr ""

#: ../../docs/tutorials/3d/particles/attractors.rst:51
msgid ""
"Strength increase variations: constantly over the distance to the attractor "
"(left), fast at the boundary border and slowly at the center (middle), "
"slowly at the boundary and fast at the center (right)."
msgstr ""

#: ../../docs/tutorials/3d/particles/attractors.rst:55
msgid ""
"The ``Directionality`` property changes the direction towards which "
"particles are pulled. At a value of ``0.0``, there is no directionality, "
"which means that particles are pulled towards the attractor's center. At "
"``1.0``, the attractor is fully directional, which means particles will be "
"pulled along the attractor's local ``-Z``-axis. You can change the global "
"direction by rotating the attractor. If ``Strength`` is negative, particles "
"are instead pulled along the ``+Z``-axis."
msgstr ""

#: ../../docs/tutorials/3d/particles/attractors.rst:65
msgid "Different attractor directionality values"
msgstr ""

#: ../../docs/tutorials/3d/particles/attractors.rst:65
msgid ""
"No directionality (left) vs. full directionality (right). Notice how the "
"particles move along the attractor's local Z-axis."
msgstr ""

#: ../../docs/tutorials/3d/particles/attractors.rst:68
msgid ""
"The ``Cull Mask`` property controls which particle systems are affected by "
"an attractor based on each system's :ref:`visibility layers "
"<class_VisualInstance3D>`. A particle system is only affected by an "
"attractor if at least one of the system's visibility layers is enabled in "
"the attractor's cull mask."
msgstr ""

#: ../../docs/tutorials/3d/particles/attractors.rst:75
msgid ""
"There is a `known issue <https://github.com/godotengine/godot/"
"issues/61014>`_ with GPU particle attractors that prevent the cull mask from "
"working properly in Godot 4.0. We will update the documentation as soon as "
"it is fixed."
msgstr ""

#: ../../docs/tutorials/3d/particles/attractors.rst:80
msgid "Box attractors"
msgstr ""

#: ../../docs/tutorials/3d/particles/attractors.rst:86
msgid "Particle attractor box"
msgstr ""

#: ../../docs/tutorials/3d/particles/attractors.rst:86
msgid "Box attractor in the node list"
msgstr ""

#: ../../docs/tutorials/3d/particles/attractors.rst:88
msgid ""
"Box attractors have a box-shaped influence region. You control their size "
"with the ``Extents`` property. Box extents always measure half of the sides "
"of its bounds, so a value of ``(X=1.0,Y=1.0,Z=1.0)`` creates a box with an "
"influence region that is 2 meters wide on each side."
msgstr ""

#: ../../docs/tutorials/3d/particles/attractors.rst:92
msgid ""
"To create a box attractor, add a new child node to your scene and select "
"``GPUParticlesAttractorBox3D`` from the list of available nodes. You can "
"animate the box position or attach it to a moving node for more dynamic "
"effects."
msgstr ""

#: ../../docs/tutorials/3d/particles/attractors.rst:99
msgid "Box attractor parts particle field"
msgstr ""

#: ../../docs/tutorials/3d/particles/attractors.rst:99
msgid ""
"A box attractor with a negative strength value parts a particle field as it "
"moves through it."
msgstr ""

#: ../../docs/tutorials/3d/particles/attractors.rst:102
msgid "Sphere attractors"
msgstr ""

#: ../../docs/tutorials/3d/particles/attractors.rst:108
msgid "Particle attractor sphere"
msgstr ""

#: ../../docs/tutorials/3d/particles/attractors.rst:108
msgid "Sphere attractor in the node list"
msgstr ""

#: ../../docs/tutorials/3d/particles/attractors.rst:110
msgid ""
"Sphere attractors have a spherical influence region. You control their size "
"with the ``Radius`` property. While box attractors don't have to be perfect "
"cubes, sphere attractors will always be spheres: You can't set width "
"independently from height. If you want to use a sphere attractor for "
"elongated shapes, you have to change its ``Scale`` in the attractor's "
"``Node3D`` section."
msgstr ""

#: ../../docs/tutorials/3d/particles/attractors.rst:115
msgid ""
"To create a sphere attractor, add a new child node to your scene and select "
"``GPUParticlesAttractorSphere3D`` from the list of available nodes. You can "
"animate the sphere position or attach it to a moving node for more dynamic "
"effects."
msgstr ""

#: ../../docs/tutorials/3d/particles/attractors.rst:122
msgid "Sphere attractor parts particle field"
msgstr ""

#: ../../docs/tutorials/3d/particles/attractors.rst:122
msgid ""
"A sphere attractor with a negative strength value parts a particle field as "
"it moves through it."
msgstr ""

#: ../../docs/tutorials/3d/particles/attractors.rst:125
msgid "Vector field attractors"
msgstr ""

#: ../../docs/tutorials/3d/particles/attractors.rst:131
msgid "Particle attractor vector field"
msgstr ""

#: ../../docs/tutorials/3d/particles/attractors.rst:131
msgid "Vector field attractor in the node list"
msgstr ""

#: ../../docs/tutorials/3d/particles/attractors.rst:133
msgid ""
"A vector field is a 3D area that contains vectors positioned on a grid. The "
"grid density controls how many vectors there are and how far they're spread "
"apart. Each vector in a vector field points in a specific direction. This "
"can be completely random or aligned in a way that forms distinct patterns "
"and paths."
msgstr ""

#: ../../docs/tutorials/3d/particles/attractors.rst:138
msgid ""
"When particles interact with a vector field, their movement direction "
"changes to match the nearest vector in the field. As a particle moves closer "
"to the next vector in the field, it changes direction to match that vector's "
"direction. The particle's speed depends on the vector's length."
msgstr ""

#: ../../docs/tutorials/3d/particles/attractors.rst:142
msgid ""
"Like box attractors, vector field attractors have a box-shaped influence "
"region. You control their size with the ``Extents`` property, where a value "
"of ``(X=1.0,Y=1.0,Z=1.0)`` creates a box with an influence region that is 2 "
"meters wide on each side. The ``Texture`` property takes a :ref:`3D texture "
"<class_Texture3D>` where every pixel represents a vector with the pixel's "
"color interpreted as the vector's direction and size."
msgstr ""

#: ../../docs/tutorials/3d/particles/attractors.rst:149
msgid ""
"When a texture is used as a vector field, there are two types of conversion "
"you need to be aware of:"
msgstr ""

#: ../../docs/tutorials/3d/particles/attractors.rst:151
msgid ""
"The texture coordinates map to the attractor bounds. The image below shows "
"which part of the texture corresponds to which part of the vector field "
"volume. For example, the bottom half of the texture affects the top half of "
"the vector field attractor because ``+Y`` points down in the texture UV "
"space, but up in Godot's world space."
msgstr ""

#: ../../docs/tutorials/3d/particles/attractors.rst:155
msgid ""
"The pixel color values map to direction vectors in space. The image below "
"provides an overview. Since particles can move in two directions along each "
"axis, the lower half of the color range represents negative direction values "
"while the upper half represents positive direction values. So a yellow pixel "
"``(R=1,G=1,B=0)`` maps to the vector ``(X=1,Y=1,Z=-1)`` while a neutral gray "
"``(R=0.5,G=0.5,B=0.5)`` results in no movement at all."
msgstr ""

#: ../../docs/tutorials/3d/particles/attractors.rst:0
msgid "Mapping from texture to vector field"
msgstr ""

#: ../../docs/tutorials/3d/particles/attractors.rst:164
msgid ""
"To create a vector field attractor, add a new child node to your scene and "
"select ``GPUParticlesAttractorVectorField3D`` from the list of available "
"nodes. You can animate the attractor's position or attach it to a moving "
"node for more dynamic effects."
msgstr ""

#: ../../docs/tutorials/3d/particles/attractors.rst:170
msgid ""
"If you don't have external tools to create vector field textures, you can "
"use a NoiseTexture3D with a Color Ramp attached as a vector field texture. "
"The Color Ramp can be modified to adjust how much each coordinate is "
"affected by the vector field."
msgstr ""

#: ../../docs/tutorials/3d/particles/attractors.rst:178
msgid "Vector field attractor in a field of particles"
msgstr ""

#: ../../docs/tutorials/3d/particles/attractors.rst:178
msgid ""
"Two particle systems are affected by the same vector field attractor. :"
"download:`Click here to download the 3D texture <img/"
"particle_vector_field_16x16x16.bmp>`."
msgstr ""

#: ../../docs/tutorials/3d/particles/collision.rst:4
msgid "3D Particle collisions"
msgstr ""

#: ../../docs/tutorials/3d/particles/collision.rst:-1
#, fuzzy
msgid "Particle collisions"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/3d/particles/collision.rst:9
msgid ""
"Since GPU particles are processed entirely on the GPU, they don't have "
"access to the game's physical world. If you need particles to collide with "
"the environment, you have to set up particle collision nodes. There are four "
"of them: :ref:`class_GPUParticlesCollisionBox3D`, :ref:"
"`class_GPUParticlesCollisionSphere3D`, :ref:"
"`class_GPUParticlesCollisionSDF3D`, and :ref:"
"`class_GPUParticlesCollisionHeightField3D`."
msgstr ""

#: ../../docs/tutorials/3d/particles/collision.rst:16
msgid "GPU Particle collision is not yet implemented for 2D particle systems."
msgstr ""

#: ../../docs/tutorials/3d/particles/collision.rst:25
#, fuzzy
msgid "Common particle collision properties"
msgstr "Glavna dokumentacija za sajt je podeljena na sledeća poglavlja:"

#: ../../docs/tutorials/3d/particles/collision.rst:25
msgid "Common collision properties"
msgstr ""

#: ../../docs/tutorials/3d/particles/collision.rst:27
msgid ""
"There are some properties that you can find on all collision nodes. They're "
"located in the ``GPUParticlesCollision3D`` section in the inspector."
msgstr ""

#: ../../docs/tutorials/3d/particles/collision.rst:30
msgid ""
"The ``Cull Mask`` property controls which particle systems are affected by a "
"collision node based on each system's :ref:`visibility layers "
"<class_VisualInstance3D>`. A particle system collides with a collision node "
"only if at least one of the system's visibility layers is enabled in the "
"collider's cull mask."
msgstr ""

#: ../../docs/tutorials/3d/particles/collision.rst:37
msgid ""
"There is a `known issue <https://github.com/godotengine/godot/"
"issues/61014>`_ with GPU particle collision that prevent the cull mask from "
"working properly in Godot 4.0. We will update the documentation as soon as "
"it is fixed."
msgstr ""

#: ../../docs/tutorials/3d/particles/collision.rst:42
msgid "Box collision"
msgstr ""

#: ../../docs/tutorials/3d/particles/collision.rst:48
msgid "Particle collision box"
msgstr ""

#: ../../docs/tutorials/3d/particles/collision.rst:48
msgid "Box collision in the node list"
msgstr ""

#: ../../docs/tutorials/3d/particles/collision.rst:50
msgid ""
"Box collision nodes are shaped like a solid, rectangular box. You control "
"their size with the ``Extents`` property. Box extents always measure half of "
"the sides of its bounds, so a value of ``(X=1.0,Y=1.0,Z=1.0)`` creates a box "
"that is 2 meters wide on each side. Box collision nodes are useful for "
"simulating floor and wall geometry that particles should collide against."
msgstr ""

#: ../../docs/tutorials/3d/particles/collision.rst:55
msgid ""
"To create a box collision node, add a new child node to your scene and "
"select ``GPUParticlesCollisionBox3D`` from the list of available nodes. You "
"can animate the box position or attach it to a moving node for more dynamic "
"effects."
msgstr ""

#: ../../docs/tutorials/3d/particles/collision.rst:62
msgid "Box collision with particle systems"
msgstr ""

#: ../../docs/tutorials/3d/particles/collision.rst:62
msgid "Two particle systems collide with a box collision node"
msgstr ""

#: ../../docs/tutorials/3d/particles/collision.rst:65
msgid "Sphere collision"
msgstr ""

#: ../../docs/tutorials/3d/particles/collision.rst:71
msgid "Particle collision sphere"
msgstr ""

#: ../../docs/tutorials/3d/particles/collision.rst:71
msgid "Sphere collision in the node list"
msgstr ""

#: ../../docs/tutorials/3d/particles/collision.rst:73
msgid ""
"Sphere collision nodes are shaped like a solid sphere. The ``Radius`` "
"property controls the size of the sphere. While box collision nodes don't "
"have to be perfect cubes, sphere collision nodes will always be spheres. If "
"you want to set width independently from height, you have to change the "
"``Scale`` property in the ``Node3D`` section."
msgstr ""

#: ../../docs/tutorials/3d/particles/collision.rst:78
msgid ""
"To create a sphere collision node, add a new child node to your scene and "
"select ``GPUParticlesCollisionSphere3D`` from the list of available nodes. "
"You can animate the sphere's position or attach it to a moving node for more "
"dynamic effects."
msgstr ""

#: ../../docs/tutorials/3d/particles/collision.rst:85
msgid "Sphere collision with particle systems"
msgstr ""

#: ../../docs/tutorials/3d/particles/collision.rst:85
msgid "Two particle systems collide with a sphere collision node"
msgstr ""

#: ../../docs/tutorials/3d/particles/collision.rst:88
msgid "Height field collision"
msgstr ""

#: ../../docs/tutorials/3d/particles/collision.rst:94
msgid "Particle collision height field"
msgstr ""

#: ../../docs/tutorials/3d/particles/collision.rst:94
msgid "Height field collision in the node list"
msgstr ""

#: ../../docs/tutorials/3d/particles/collision.rst:96
msgid ""
"Height field particle collision is very useful for large outdoor areas that "
"need to collide with particles. At runtime, the node creates a height field "
"from all the meshes within its bounds that match its cull mask. Particles "
"collide against the mesh that this height field represents. Since the height "
"field generation is done dynamically, it can follow the player camera around "
"and react to changes in the level. Different settings for the height field "
"density offer a wide range of performance adjustments."
msgstr ""

#: ../../docs/tutorials/3d/particles/collision.rst:102
msgid ""
"To create a height field collision node, add a new child node to your scene "
"and select ``GPUParticlesCollisionHeightField3D`` from the list of available "
"nodes."
msgstr ""

#: ../../docs/tutorials/3d/particles/collision.rst:105
msgid ""
"A height field collision node is shaped like a box. The ``Extents`` property "
"controls its size. Extents always measure half of the sides of its bounds, "
"so a value of ``(X=1.0,Y=1.0,Z=1.0)`` creates a box that is 2 meters wide on "
"each side. Anything outside of the node's extents is ignored for height "
"field creation."
msgstr ""

#: ../../docs/tutorials/3d/particles/collision.rst:109
msgid ""
"The ``Resolution`` property controls how detailed the height field is. A "
"lower resolution performs faster at the cost of accuracy. If the height "
"field resolution is too low, it may look like particles penetrate level "
"geometry or get stuck in the air during collision events. They might also "
"ignore some smaller meshes completely."
msgstr ""

#: ../../docs/tutorials/3d/particles/collision.rst:116
msgid "Height field resolutions"
msgstr ""

#: ../../docs/tutorials/3d/particles/collision.rst:116
msgid ""
"At low resolutions, height field collision misses some finer details (left)"
msgstr ""

#: ../../docs/tutorials/3d/particles/collision.rst:118
msgid ""
"The ``Update Mode`` property controls when the height field is recreated "
"from the meshes within its bounds. Set it to ``When Moved`` to make it "
"refresh only when it moves. This performs well and is suited for static "
"scenes that don't change very often. If you need particles to collide with "
"dynamic objects that change position frequently, you can select ``Always`` "
"to refresh every frame. This comes with a cost to performance and should "
"only be used when necessary."
msgstr ""

#: ../../docs/tutorials/3d/particles/collision.rst:126
msgid ""
"It's important to remember that when ``Update Mode`` is set to ``When "
"Moved``, it is the *height field node* whose movement triggers an update. "
"The height field is not updated when one of the meshes inside it moves."
msgstr ""

#: ../../docs/tutorials/3d/particles/collision.rst:129
msgid ""
"The ``Follow Camera Enabled`` property makes the height field follow the "
"current camera when enabled. It will update whenever the camera moves. This "
"property can be used to make sure that there is always particle collision "
"around the player while not wasting performance on regions that are out of "
"sight or too far away."
msgstr ""

#: ../../docs/tutorials/3d/particles/collision.rst:134
#, fuzzy
msgid "SDF collision"
msgstr "Funkcije"

#: ../../docs/tutorials/3d/particles/collision.rst:140
msgid "Particle collision SDF"
msgstr ""

#: ../../docs/tutorials/3d/particles/collision.rst:140
msgid "SDF collision in the node list"
msgstr ""

#: ../../docs/tutorials/3d/particles/collision.rst:142
msgid ""
"SDF collision nodes create a `signed distance field <https://www.reddit.com/"
"r/explainlikeimfive/comments/k2zbos/"
"eli5_what_are_distance_fields_in_graphics>`_ that particles can collide "
"with. SDF collision is similar to height field collision in that it turns "
"multiple meshes within its bounds into a single collision volume for "
"particles. A major difference is that signed distance fields can represent "
"holes, tunnels and overhangs, which is impossible to do with height fields "
"alone. The performance overhead is larger compared to height fields, so "
"they're best suited for small-to-medium-sized environments."
msgstr ""

#: ../../docs/tutorials/3d/particles/collision.rst:148
msgid ""
"To create an SDF collision node, add a new child node to your scene and "
"select ``GPUParticlesCollisionSDF3D`` from the list of available nodes. SDF "
"collision nodes have to be baked in order to have any effect on particles in "
"the level. To do that, click the ``Bake SDF`` button in the viewport toolbar "
"while the SDF collision node is selected and choose a directory to store the "
"baked data. Since SDF collision needs to be baked in the editor, it's static "
"and cannot change at runtime."
msgstr ""

#: ../../docs/tutorials/3d/particles/collision.rst:157
msgid "SDF particle collision"
msgstr ""

#: ../../docs/tutorials/3d/particles/collision.rst:157
msgid ""
"SDF particle collision allows for very detailed 3-dimensional collision "
"shapes"
msgstr ""

#: ../../docs/tutorials/3d/particles/collision.rst:159
msgid ""
"An SDF collision node is shaped like a box. The ``Extents`` property "
"controls its size. Extents always measure half of the sides of its bounds, "
"so a value of ``(X=1.0,Y=1.0,Z=1.0)`` creates a box that is 2 meters wide on "
"each side. Anything outside of the node's extents is ignored for collision."
msgstr ""

#: ../../docs/tutorials/3d/particles/collision.rst:163
msgid ""
"The ``Resolution`` property controls how detailed the distance field is. A "
"lower resolution performs faster at the cost of accuracy. If the resolution "
"is too low, it may look like particles penetrate level geometry or get stuck "
"in the air during collision events. They might also ignore some smaller "
"meshes completely."
msgstr ""

#: ../../docs/tutorials/3d/particles/collision.rst:170
msgid "Resolution comparison"
msgstr ""

#: ../../docs/tutorials/3d/particles/collision.rst:170
msgid ""
"The same area covered by a signed distance field at different resolutions: "
"16 (left) and 256 (right)"
msgstr ""

#: ../../docs/tutorials/3d/particles/collision.rst:172
msgid ""
"The ``Thickness`` property gives the distance field, which is usually hollow "
"on the inside, a thickness to prevent particles from penetrating at high "
"speeds. If you find that some particles don't collide with the level "
"geometry and instead shoot right through it, try setting this property to a "
"higher value."
msgstr ""

#: ../../docs/tutorials/3d/particles/collision.rst:176
msgid ""
"The ``Bake Mask`` property controls which meshes will be considered when the "
"SDF is baked. Only meshes that render on the active layers in the bake mask "
"contribute to particle collision."
msgstr ""

#: ../../docs/tutorials/3d/particles/complex_shapes.rst:-1
#: ../../docs/tutorials/3d/particles/complex_shapes.rst:4
msgid "Complex emission shapes"
msgstr ""

#: ../../docs/tutorials/3d/particles/complex_shapes.rst:9
msgid ""
"When it is not enough to emit particles from one of the simple shapes "
"available in the :ref:`process material "
"<doc_process_material_properties_shapes>`, Godot provides a way to emit "
"particles from arbitrary, complex shapes. The shapes are generated from "
"meshes in the scene and stored as textures in the particle process material. "
"This is a very versatile workflow that has allowed users to use particle "
"systems for things that go beyond traditional use cases, like foliage, "
"leaves on a tree, or complex holographic effects."
msgstr ""

#: ../../docs/tutorials/3d/particles/complex_shapes.rst:19
msgid ""
"When you create emission points from meshes, you can only select a single "
"node as emission source. If you want particles to emit from multiple shapes, "
"you either have to create several particle systems or combine the meshes "
"into one in an external DCC software."
msgstr ""

#: ../../docs/tutorials/3d/particles/complex_shapes.rst:28
#, fuzzy
msgid "Creating emission points"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/3d/particles/complex_shapes.rst:28
msgid "Create particle emission points..."
msgstr ""

#: ../../docs/tutorials/3d/particles/complex_shapes.rst:34
msgid "Select mesh for emission"
msgstr ""

#: ../../docs/tutorials/3d/particles/complex_shapes.rst:34
msgid "\\...from a mesh instance as the source"
msgstr ""

#: ../../docs/tutorials/3d/particles/complex_shapes.rst:40
msgid "Set emission density"
msgstr ""

#: ../../docs/tutorials/3d/particles/complex_shapes.rst:40
msgid "More points = higher particle density"
msgstr ""

#: ../../docs/tutorials/3d/particles/complex_shapes.rst:42
msgid ""
"To make use of this feature, start by creating a particle system in the "
"current scene. Add a mesh instance that serves as the source of the particle "
"emission points. With the particle system selected, navigate to the viewport "
"menu and select the *GPUParticles3D* entry. From there, select ``Create "
"Emission Points From Node``."
msgstr ""

#: ../../docs/tutorials/3d/particles/complex_shapes.rst:47
msgid ""
"A dialog window will pop up and ask you to select a node as the emission "
"source. Choose one of the mesh instances in the scene and confirm your "
"selection. The next dialog window deals with the amount of points and how to "
"generate them."
msgstr ""

#: ../../docs/tutorials/3d/particles/complex_shapes.rst:51
msgid ""
"``Emission Points`` controls the total number of points that you are about "
"to generate. Particles will spawn from these points, so what to enter here "
"depends on the size of the source mesh (how much area you have to cover) and "
"the desired density of the particles."
msgstr ""

#: ../../docs/tutorials/3d/particles/complex_shapes.rst:56
msgid ""
"``Emission Source`` offers 3 different options for how the points are "
"generated. Select ``Surface Points`` if all you want to do is distribute the "
"emission points across the surface of the mesh. Select ``Surface Points + "
"Normal (Directed)`` if you also want to generate information about the "
"surface normals and make particles move in the direction that the normals "
"point at. The last option, ``Volume``, creates emission points everywhere "
"inside the mesh, not just across its surface."
msgstr ""

#: ../../docs/tutorials/3d/particles/complex_shapes.rst:63
msgid ""
"The emission points are stored in the particle system's local coordinate "
"system, so you can move the particle node around and the emission points "
"will follow. This might be useful when you want to use the same particle "
"system in several different places. On the other hand, you might have to "
"regenerate the emission points when you move either the particle system or "
"the source mesh."
msgstr ""

#: ../../docs/tutorials/3d/particles/complex_shapes.rst:70
#, fuzzy
msgid "Emission shape textures"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/3d/particles/complex_shapes.rst:76
#, fuzzy
msgid "Emission textures"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/3d/particles/complex_shapes.rst:76
msgid "The available emission shape textures"
msgstr ""

#: ../../docs/tutorials/3d/particles/complex_shapes.rst:78
msgid ""
"All the data for complex particle emission shapes is stored in a set of "
"textures. How many, depends on the type of emission shape you use. If you "
"set the ``Shape`` property in the ``Emission Shape`` group on the particle "
"process material to ``Points``, you have access to 2 texture properties, the "
"``Point Texture`` and the ``Color Texture``. Set it to ``Directed Points`` "
"and there is a third property called ``Normal Texture``."
msgstr ""

#: ../../docs/tutorials/3d/particles/complex_shapes.rst:84
msgid ""
"``Point Texture`` contains all possible emission points that were generated "
"in the previous step. A point is randomly selected for every particle when "
"it spawns. ``Normal Texture``, if it exists, provides a direction vector at "
"that same location. If the ``Color Texture`` property is also set, it "
"provides color for the particle, sampled at the same location as the other "
"two textures and modulating any other color that was set up on the process "
"material."
msgstr ""

#: ../../docs/tutorials/3d/particles/complex_shapes.rst:91
msgid ""
"There is also the ``Point Count`` property that you can use to change the "
"number of emission points at any time after creating the emission shape. "
"This includes dynamically at runtime while the playing the game."
msgstr ""

#: ../../docs/tutorials/3d/high_dynamic_range.rst:6
msgid "High dynamic range lighting"
msgstr ""

#: ../../docs/tutorials/3d/high_dynamic_range.rst:11
msgid ""
"Normally, an artist does all the 3D modeling, then all the texturing, looks "
"at their awesome looking model in the 3D modeling software and says \"looks "
"fantastic, ready for integration!\" then goes into the game, lighting is "
"setup and the game runs."
msgstr ""

#: ../../docs/tutorials/3d/high_dynamic_range.rst:16
msgid ""
"So at what point does all this \"HDR\" business come into play? To "
"understand the answer, we need to look at how displays behave."
msgstr ""

#: ../../docs/tutorials/3d/high_dynamic_range.rst:19
msgid ""
"Your display outputs linear light ratios from some maximum to some minimum "
"intensity. Modern game engines perform complex math on linear light values "
"in their respective scenes. So what's the problem?"
msgstr ""

#: ../../docs/tutorials/3d/high_dynamic_range.rst:23
msgid ""
"The display has a limited range of intensity, depending on the display type. "
"The game engine renders to an unlimited range of intensity values, however. "
"While \"maximum intensity\" means something to an sRGB display, it has no "
"bearing in the game engine; there is only a potentially infinitely wide "
"range of intensity values generated per frame of rendering."
msgstr ""

#: ../../docs/tutorials/3d/high_dynamic_range.rst:29
msgid ""
"This means that some transformation of the scene light intensity, also known "
"as *scene-referred* light ratios, need to be transformed and mapped to fit "
"within the particular output range of the chosen display. This can be most "
"easily understood if we consider virtually photographing our game engine "
"scene through a virtual camera. Here, our virtual camera would apply a "
"particular camera rendering transform to the scene data, and the output "
"would be ready for display on a particular display type."
msgstr ""

#: ../../docs/tutorials/3d/high_dynamic_range.rst:39
msgid ""
"Godot does not support high dynamic range *output* yet. It can only perform "
"lighting in HDR and tonemap the result to a low dynamic range image."
msgstr ""

#: ../../docs/tutorials/3d/high_dynamic_range.rst:42
msgid ""
"For advanced users, it is still possible to get a non-tonemapped image of "
"the viewport with full HDR data, which can then be saved to an OpenEXR file."
msgstr ""

#: ../../docs/tutorials/3d/high_dynamic_range.rst:46
msgid "Computer displays"
msgstr ""

#: ../../docs/tutorials/3d/high_dynamic_range.rst:48
msgid ""
"Almost all displays require a nonlinear encoding for the code values sent to "
"them. The display in turn, using its unique transfer characteristic, "
"\"decodes\" the code value into linear light ratios of output, and projects "
"the ratios out of the uniquely colored lights at each reddish, greenish, and "
"blueish emission site."
msgstr ""

#: ../../docs/tutorials/3d/high_dynamic_range.rst:54
msgid ""
"For a majority of computer displays, the specifications of the display are "
"outlined in accordance with IEC 61966-2-1, also known as the 1996 sRGB "
"specification. This specification outlines how an sRGB display is to behave, "
"including the color of the lights in the LED pixels as well as the transfer "
"characteristics of the input (OETF) and output (EOTF)."
msgstr ""

#: ../../docs/tutorials/3d/high_dynamic_range.rst:60
msgid ""
"Not all displays use the same OETF and EOTF as a computer display. For "
"example, television broadcast displays use the BT.1886 EOTF. However, Godot "
"currently only supports sRGB displays."
msgstr ""

#: ../../docs/tutorials/3d/high_dynamic_range.rst:64
msgid ""
"The sRGB standard is based around the nonlinear relationship between the "
"current to light output of common desktop computing CRT displays."
msgstr ""

#: ../../docs/tutorials/3d/high_dynamic_range.rst:69
msgid ""
"The mathematics of a scene-referred model require that we multiply the scene "
"by different values to adjust the intensities and exposure to different "
"light ranges. The transfer function of the display can't appropriately "
"render the wider dynamic range of the game engine's scene output using the "
"simple transfer function of the display. A more complex approach to encoding "
"is required."
msgstr ""

#: ../../docs/tutorials/3d/high_dynamic_range.rst:77
msgid "Scene linear & asset pipelines"
msgstr ""

#: ../../docs/tutorials/3d/high_dynamic_range.rst:79
msgid ""
"Working in scene-linear sRGB is more complex than pressing a single switch. "
"First, imported image assets must be converted to linear light ratios on "
"import. Even when linearized, those assets may not be perfectly well-suited "
"for use as textures, depending on how they were generated."
msgstr ""

#: ../../docs/tutorials/3d/high_dynamic_range.rst:84
#, fuzzy
msgid "There are two ways to do this:"
msgstr "Ne postoje ograničenja prilikom korištenja Godot-a"

#: ../../docs/tutorials/3d/high_dynamic_range.rst:87
msgid "sRGB transfer function to display linear ratios on image import"
msgstr ""

#: ../../docs/tutorials/3d/high_dynamic_range.rst:89
msgid ""
"This is the easiest method of using sRGB assets, but it's not the most "
"ideal. One issue with this is loss of quality. Using 8 bits per channel to "
"represent linear light ratios is not sufficient to quantize the values "
"correctly. These textures may also be compressed later, which can exacerbate "
"the problem."
msgstr ""

#: ../../docs/tutorials/3d/high_dynamic_range.rst:95
msgid "Hardware sRGB transfer function to display linear conversion"
msgstr ""

#: ../../docs/tutorials/3d/high_dynamic_range.rst:97
msgid ""
"The GPU will do the conversion after reading the texel using floating-point. "
"This works fine on PC and consoles, but most mobile devices don't support "
"it, or they don't support it on compressed texture formats (iOS for example)."
msgstr ""

#: ../../docs/tutorials/3d/high_dynamic_range.rst:102
msgid "Scene linear to display-referred nonlinear"
msgstr ""

#: ../../docs/tutorials/3d/high_dynamic_range.rst:104
msgid ""
"After all the rendering is done, the scene linear render requires "
"transforming to a suitable output such as an sRGB display. To do this, "
"enable sRGB conversion in the current :ref:`Environment <class_Environment>` "
"(more on that below)."
msgstr ""

#: ../../docs/tutorials/3d/high_dynamic_range.rst:108
msgid ""
"Keep in mind that the **sRGB -> Display Linear** and **Display Linear -> "
"sRGB** conversions must always be **both** enabled. Failing to enable one of "
"them will result in horrible visuals suitable only for avant-garde "
"experimental indie games."
msgstr ""

#: ../../docs/tutorials/3d/high_dynamic_range.rst:114
msgid "Parameters of HDR"
msgstr ""

#: ../../docs/tutorials/3d/high_dynamic_range.rst:116
msgid ""
"HDR settings can be found in the :ref:`Environment <class_Environment>` "
"resource. Most of the time, these are found inside a :ref:`WorldEnvironment "
"<class_WorldEnvironment>` node or set in a Camera node. For more "
"information, see :ref:`doc_environment_and_post_processing`."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/index.rst:4
#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:536
msgid "Global illumination"
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/introduction_to_global_illumination.rst:4
#, fuzzy
msgid "Introduction to global illumination"
msgstr "Uvod"

#: ../../docs/tutorials/3d/global_illumination/introduction_to_global_illumination.rst:7
#, fuzzy
msgid "What is global illumination?"
msgstr "O dokumentaciji"

#: ../../docs/tutorials/3d/global_illumination/introduction_to_global_illumination.rst:9
msgid ""
"*Global illumination* is a catch-all term used to describe a system of "
"lighting that uses both direct light (light that comes directly from a light "
"source) and indirect light (light that bounces from a surface). In a 3D "
"rendering engine, global illumination is one of the most important elements "
"to achieving realistic lighting. Global illumination aims to mimic how light "
"behaves in real life, such as light bouncing on surfaces and light being "
"emitted from emissive materials."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/introduction_to_global_illumination.rst:17
msgid ""
"In the example below, the entire scene is illuminated by an emissive "
"material (the white square at the top). The white wall and ceiling on the "
"back is tinted red and green close to the walls, as the light bouncing on "
"the colored walls is being reflected back onto the rest of the scene."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/introduction_to_global_illumination.rst:24
msgid "Global illumination is composed of several key concepts:"
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/introduction_to_global_illumination.rst:27
msgid "Indirect diffuse lighting"
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/introduction_to_global_illumination.rst:29
msgid ""
"This is the lighting that does not change depending on the camera's angle. "
"There are two main sources of indirect diffuse lighting:"
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/introduction_to_global_illumination.rst:32
msgid ""
"Light *bouncing* on surfaces. This bounced lighting is multiplied with the "
"material's albedo color. The bounced lighting can then be reflected by other "
"surfaces, with decreasing impact due to light attenuation. In real life, "
"light bounces an infinite number of times. However, for performance reasons, "
"this can't be simulated in a game engine. Instead, the number of bounces is "
"typically limited to 1 or 2 (or up to 16 when baking lightmaps). A greater "
"number of bounces will lead to more realistic light falloff in shaded areas, "
"at the cost of lower performance or greater bake times."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/introduction_to_global_illumination.rst:40
msgid ""
"Emissive materials can also emit light that can be bounced on surfaces. This "
"acts as a form of *area lighting*. Instead of having an infinitely small "
"point emit light using an OmniLight3D or SpotLight3D node, an area of a "
"determined size will emit light using its own surface."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/introduction_to_global_illumination.rst:45
msgid ""
"Direct diffuse lighting is already handled by the light nodes themselves, "
"which means that global illumination algorithms only try to represent "
"indirect lighting."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/introduction_to_global_illumination.rst:49
msgid ""
"Different global illumination techniques offer varying levels of accuracy to "
"represent indirect diffuse lighting. See the comparison table at the bottom "
"of this page for more information."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/introduction_to_global_illumination.rst:53
msgid ""
"To provide more accurate ambient occlusion for small objects, screen-space "
"ambient occlusion (SSAO) can be enabled in the :ref:`environment "
"<doc_environment_and_post_processing>` settings. SSAO has a significant "
"performance cost, so make sure to disable it when targeting low-end hardware."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/introduction_to_global_illumination.rst:60
msgid ""
"Indirect diffuse lighting may be a source of color banding in scenes with no "
"detailed textures. This results in light gradients not being smooth, but "
"having a visible \"stepping\" effect instead. See the :ref:"
"`doc_3d_rendering_limitations_color_banding` section in the 3D rendering "
"limitations documentation for ways to reduce this effect."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/introduction_to_global_illumination.rst:67
msgid "Specular lighting"
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/introduction_to_global_illumination.rst:69
msgid ""
"Specular lighting is also referred to as *reflections*. This is the lighting "
"that changes in intensity depending on the camera's angle. This specular "
"lighting can be *direct* or *indirect*."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/introduction_to_global_illumination.rst:73
msgid ""
"Most global illumination techniques offer a way to render specular lighting. "
"However, the degree of accuracy at which specular lighting is rendered "
"varies greatly from technique to technique. See the comparison table at the "
"bottom of this page for more information."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/introduction_to_global_illumination.rst:78
msgid ""
"To provide more accurate reflections for small objects, screen-space "
"reflections (SSR) can be enabled in the :ref:`environment "
"<doc_environment_and_post_processing>` settings. SSR has a significant "
"performance cost (even more so than SSAO), so make sure to disable it when "
"targeting low-end hardware."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/introduction_to_global_illumination.rst:86
msgid "Which global illumination technique should I use?"
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/introduction_to_global_illumination.rst:88
msgid ""
"When determining a global illumination (GI) technique to use, there are "
"several criteria to keep in mind:"
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/introduction_to_global_illumination.rst:91
msgid ""
"**Performance.** Real-time GI techniques are usually more expensive compared "
"to semi-real-time or baked techniques. Note that most of the cost in GI "
"rendering is spent on the GPU, rather than the CPU."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/introduction_to_global_illumination.rst:94
msgid ""
"**Visuals.** On top of not performing the best, real-time GI techniques "
"generally don't provide the best visual output. This is especially the case "
"in a mostly static scene where the dynamic nature of real-time GI is not "
"easily noticeable. If maximizing visual quality is your goal, baked "
"techniques will often look better and will result in fewer light leaks."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/introduction_to_global_illumination.rst:99
msgid ""
"**Real-time ability.** Some GI techniques are fully real-time, whereas "
"others are only semi-real-time or aren't real-time at all. Semi-real-time "
"techniques have restrictions that fully real-time techniques don't. For "
"instance, dynamic objects may not contribute emissive lighting to the scene. "
"Non-real-time techniques do not support *any* form of dynamic GI, so it must "
"be faked using other techniques if needed (such as placing positional lights "
"near emissive surfaces). Real-time ability also affects the GI technique's "
"viability in procedurally generated levels."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/introduction_to_global_illumination.rst:108
msgid ""
"**User work needed.** Some GI techniques are fully automatic, whereas others "
"require careful planning and manual work on the user's side. Depending on "
"your time budget, some GI techniques may be preferable to others."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/introduction_to_global_illumination.rst:112
msgid ""
"Here's a comparison of all the global illumination techniques available in "
"Godot:"
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/introduction_to_global_illumination.rst:115
#: ../../docs/tutorials/performance/index.rst:4
#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:162
msgid "Performance"
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/introduction_to_global_illumination.rst:117
msgid "In order of performance from fastest to slowest:"
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/introduction_to_global_illumination.rst:119
msgid "**ReflectionProbe:**"
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/introduction_to_global_illumination.rst:121
msgid ""
"ReflectionProbes with their update mode set to **Always** are much more "
"expensive than probes with their update mode set to **Once** (the default). "
"Suited for integrated graphics when using the **Once** update mode. "
"*Available when using the Forward Mobile backend. Will be available in the "
"Compatibility backend in later releases.*"
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/introduction_to_global_illumination.rst:126
msgid "**LightmapGI:**"
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/introduction_to_global_illumination.rst:128
msgid ""
"Lights can be baked with indirect lighting only, or fully baked on a per-"
"light basis to further improve performance. Hybrid setups can be used (such "
"as having a real-time directional light and fully baked positional lights). "
"Directional information can be enabled before baking to improve visuals at a "
"small performance cost (and at the cost of larger file sizes). Suited for "
"integrated graphics. *Available when using the Forward Mobile backend. Will "
"be available in the Compatibility backend in later releases.*"
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/introduction_to_global_illumination.rst:136
msgid "**VoxelGI:**"
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/introduction_to_global_illumination.rst:138
msgid ""
"The bake's number of subdivisions can be adjusted to balance between "
"performance and quality. The VoxelGI rendering quality can be adjusted in "
"the Project Settings. The rendering can optionally be performed at half "
"resolution (and then linearly scaled) to improve performance significantly. "
"**Not available** *when using the Forward Mobile or Compatibility backends.*"
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/introduction_to_global_illumination.rst:144
msgid "**Screen-space indirect lighting (SSIL):**"
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/introduction_to_global_illumination.rst:146
msgid ""
"The SSIL quality and number of blur passes can be adjusted in the Project "
"Settings. By default, SSIL rendering is performed at half resolution (and "
"then linearly scaled) to ensure a reasonable performance level. **Not "
"available** *when using the Forward Mobile or Compatibility backends.*"
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/introduction_to_global_illumination.rst:151
msgid "**SDFGI:**"
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/introduction_to_global_illumination.rst:153
msgid ""
"The number of cascades can be adjusted to balance performance and quality. "
"The number of rays thrown per frame can be adjusted in the Project Settings. "
"The rendering can optionally be performed at half resolution (and then "
"linearly scaled) to improve performance significantly. **Not available** "
"*when using the Forward Mobile or Compatibility backends.*"
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/introduction_to_global_illumination.rst:160
#, fuzzy
msgid "Visuals"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/3d/global_illumination/introduction_to_global_illumination.rst:162
msgid ""
"For comparison, here's a 3D scene with no global illumination options used:"
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/introduction_to_global_illumination.rst:167
msgid ""
"A 3D scene without any form of global illumination (only constant "
"environment lighting). The box and sphere near the camera are both dynamic "
"objects."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/introduction_to_global_illumination.rst:169
msgid "Here's how Godot's various global illumination techniques compare:"
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/introduction_to_global_illumination.rst:171
msgid ""
"**VoxelGI:** |average| Good reflections and indirect lighting, but beware of "
"leaks."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/introduction_to_global_illumination.rst:322
msgid "average"
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/introduction_to_global_illumination.rst:173
msgid ""
"Due to its voxel-based nature, VoxelGI will exhibit light leaks if walls and "
"floors are too thin. It's recommended to make sure all solid surfaces are at "
"least as thick as one voxel."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/introduction_to_global_illumination.rst:176
msgid ""
"Streaking artifacts may also be visible on sloped surfaces. In this case, "
"tweaking the bias properties or rotating the VoxelGI node can help combat "
"this."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/introduction_to_global_illumination.rst:0
#: ../../docs/tutorials/3d/global_illumination/introduction_to_global_illumination.rst:183
msgid "VoxelGI in action."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/introduction_to_global_illumination.rst:185
msgid ""
"**SDFGI:** |average| Good reflections and indirect lighting, but beware of "
"leaks and visible cascade shifts."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/introduction_to_global_illumination.rst:187
msgid ""
"GI level of detail varies depending on the distance between the camera and "
"surface."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/introduction_to_global_illumination.rst:190
msgid ""
"Leaks can be reduced significantly by enabling the **Use Occlusion** "
"property. This has a small performance cost, but it often results in fewer "
"leaks compared to VoxelGI."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/introduction_to_global_illumination.rst:194
msgid ""
"Cascade shifts may be visible when the camera moves fast. This can be made "
"less noticeable by adjusting the cascade sizes or using fog."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/introduction_to_global_illumination.rst:0
#: ../../docs/tutorials/3d/global_illumination/introduction_to_global_illumination.rst:200
msgid "SDFGI in action."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/introduction_to_global_illumination.rst:202
msgid ""
"**Screen-space indirect lighting (SSIL):** |average| Good *secondary* source "
"of indirect lighting, but no reflections."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/introduction_to_global_illumination.rst:204
msgid ""
"SSIL is designed to be used as a complement to another GI technique such as "
"VoxelGI, SDFGI or LightmapGI. SSIL works best for small-scale details, as it "
"cannot provide accurate indirect lighting for large structures on its own. "
"SSIL can provide real-time indirect lighting in situations where other GI "
"techniques fail to capture small-scale details or dynamic objects. Its "
"screen-space nature will result in some artifacts, especially when objects "
"enter and leave the screen. SSIL works using the last frame's color (before "
"post-processing) which means that emissive decals and custom shaders are "
"included (as long as they're present on screen)."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/introduction_to_global_illumination.rst:0
#: ../../docs/tutorials/3d/global_illumination/introduction_to_global_illumination.rst:217
msgid ""
"SSIL in action (without any other GI technique). Notice the emissive "
"lighting around the yellow box."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/introduction_to_global_illumination.rst:219
msgid ""
"**LightmapGI:** |good| Excellent indirect lighting, decent reflections "
"(optional)."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/introduction_to_global_illumination.rst:320
#: ../../docs/tutorials/assets_pipeline/importing_images.rst:202
msgid "good"
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/introduction_to_global_illumination.rst:221
msgid ""
"This is the only technique where the number of light bounces can be pushed "
"above 2 (up to 16). When directional information is enabled, spherical "
"harmonics (SH) are used to provide blurry reflections."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/introduction_to_global_illumination.rst:0
#: ../../docs/tutorials/3d/global_illumination/introduction_to_global_illumination.rst:229
msgid ""
"LightmapGI in action. Only indirect lighting is baked here, but direct light "
"can also be baked."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/introduction_to_global_illumination.rst:231
msgid ""
"**ReflectionProbe:** |average| Good reflections, but poor indirect lighting."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/introduction_to_global_illumination.rst:233
msgid ""
"Indirect lighting can be disabled, set to a constant color spread throughout "
"the probe, or automatically read from the probe's environment (and applied "
"as a cubemap). This essentially acts as local ambient lighting. Reflections "
"and indirect lighting are blended with other nearby probes."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/introduction_to_global_illumination.rst:0
#: ../../docs/tutorials/3d/global_illumination/introduction_to_global_illumination.rst:241
msgid ""
"ReflectionProbe in action (without any other GI technique). Notice the "
"reflective sphere."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/introduction_to_global_illumination.rst:244
msgid "Real-time ability"
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/introduction_to_global_illumination.rst:246
msgid "**VoxelGI:** |good| Fully real-time."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/introduction_to_global_illumination.rst:248
msgid ""
"Indirect lighting and reflections are fully real-time. Dynamic objects can "
"receive GI *and* contribute to it with their emissive surfaces. Custom "
"shaders can also emit their own light, which will be emitted accurately."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/introduction_to_global_illumination.rst:252
msgid ""
"Viable for procedurally generated levels *if they are generated in advance* "
"(and not during gameplay). Baking requires several seconds or more to "
"complete, but it can be done from both the editor and an exported project."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/introduction_to_global_illumination.rst:256
msgid "**SDFGI:** |average| Semi-real-time."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/introduction_to_global_illumination.rst:258
msgid ""
"Cascades are generated in real-time, making SDFGI viable for procedurally "
"generated levels (including when structures are generated during gameplay)."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/introduction_to_global_illumination.rst:262
msgid ""
"Dynamic objects can *receive* GI, but not *contribute* to it. Emissive "
"lighting will only update when an object enters a cascade, so it may still "
"work for slow-moving objects."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/introduction_to_global_illumination.rst:266
msgid "**Screen-space indirect lighting (SSIL):** |good| Fully real-time."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/introduction_to_global_illumination.rst:268
msgid ""
"SSIL works with both static and dynamic lights. It also works with both "
"static and dynamic occluders (including emissive materials)."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/introduction_to_global_illumination.rst:271
msgid "**LightmapGI:** |bad| Baked, and therefore not real-time."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/introduction_to_global_illumination.rst:324
#: ../../docs/tutorials/assets_pipeline/importing_images.rst:200
msgid "bad"
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/introduction_to_global_illumination.rst:273
msgid ""
"Both indirect lighting and SH reflections are baked and can't be changed at "
"run-time. Real-time GI must be :ref:`simulated via other means "
"<doc_faking_global_illumination>`, such as real-time positional lights. "
"Dynamic objects receive indirect lighting via light probes, which can be "
"placed automatically or manually by the user (LightmapProbe node). Not "
"viable for procedurally generated levels, as baking lightmaps is only "
"possible from the editor."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/introduction_to_global_illumination.rst:281
msgid "**ReflectionProbe:** |average| Optionally real-time."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/introduction_to_global_illumination.rst:283
msgid ""
"By default, reflections update when the probe is moved. They update as often "
"as possible if the update mode is set to **Always** (which is expensive)."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/introduction_to_global_illumination.rst:287
msgid ""
"Indirect lighting must be configured manually by the user, but can be "
"changed at run-time without causing an expensive computation to happen "
"behind the scenes. This makes ReflectionProbes viable for procedurally "
"generated levels."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/introduction_to_global_illumination.rst:292
msgid "User work needed"
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/introduction_to_global_illumination.rst:294
msgid "**VoxelGI:** One or more VoxelGI nodes need to be created and baked."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/introduction_to_global_illumination.rst:296
msgid ""
"Adjusting extents correctly is required to get good results. Additionally "
"rotating the node and baking again can help combat leaks or streaking "
"artifacts in certain situations. Bake times are fast – usually below 10 "
"seconds for a scene of medium complexity."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/introduction_to_global_illumination.rst:301
msgid "**SDFGI:** Very little."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/introduction_to_global_illumination.rst:303
msgid ""
"SDFGI is fully automatic; it only needs to be enabled in the Environment "
"resource. The only manual work required is to set MeshInstances' bake mode "
"property correctly. No node needs to be created, and no baking is required."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/introduction_to_global_illumination.rst:307
msgid "**Screen-space indirect lighting (SSIL):** Very little."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/introduction_to_global_illumination.rst:309
msgid ""
"SSIL is fully automatic; it only needs to be enabled in the Environment "
"resource. No node needs to be created, and no baking is required."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/introduction_to_global_illumination.rst:312
msgid "**LightmapGI:** Requires UV2 setup and baking."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/introduction_to_global_illumination.rst:314
msgid ""
"Static meshes must be reimported with UV2 and lightmap generation enabled. "
"On a dedicated GPU, bake times are relatively fast thanks to the GPU-based "
"lightmap baking – usually below 1 minute for a scene of medium complexity."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/introduction_to_global_illumination.rst:318
msgid "**ReflectionProbe:** Placed manually by the user."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/introduction_to_global_illumination.rst:329
msgid "If you are unsure about which GI technique to use:"
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/introduction_to_global_illumination.rst:331
msgid ""
"For desktop games, it's a good idea to start with :ref:`SDFGI "
"<doc_using_sdfgi>` first as it requires the least amount of setup. Move to "
"other GI techniques later if needed. To improve performance on low-end GPUs "
"and integrated graphics, consider adding an option to disable SDFGI or :ref:"
"`VoxelGI <doc_using_voxel_gi>` in your game's settings. SDFGI can be "
"disabled in the Environment resource, and VoxelGI can be disabled by hiding "
"the VoxelGI node(s). To further improve visuals on high-end setups, add an "
"option to enable SSIL in your game's settings."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/introduction_to_global_illumination.rst:339
msgid ""
"For mobile games, :ref:`LightmapGI <doc_using_lightmap_gi>` and :ref:"
"`ReflectionProbes <doc_reflection_probes>` are the only supported options. "
"See also :ref:`doc_introduction_to_global_illumination_alternatives`."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/introduction_to_global_illumination.rst:345
#, fuzzy
msgid ""
"You can compare global illumination techniques in action using the `Global "
"Illumination demo project <https://github.com/godotengine/godot-demo-"
"projects/tree/master/3d/global_illumination>`__."
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati različite Godo demo projekte "
"`Godot demo projects <https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/tutorials/3d/global_illumination/introduction_to_global_illumination.rst:351
msgid "Which global illumination mode should I use on meshes and lights?"
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/introduction_to_global_illumination.rst:353
msgid ""
"Regardless of which global illumination technique you use, there is no "
"universally \"better\" global illumination mode. Still, here are some "
"recommendations for meshes:"
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/introduction_to_global_illumination.rst:357
msgid ""
"For static level geometry, use the **Static** global illumination mode "
"*(default)*."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/introduction_to_global_illumination.rst:358
msgid ""
"For small dynamic geometry and players/enemies, use the **Disabled** global "
"illumination mode. Small dynamic geometry will not be able to contribute a "
"significant amount of indirect lighting, due to the geometry being smaller "
"than a voxel. If you need indirect lighting for small dynamic objects, it "
"can be simulated using an OmniLight3D or SpotLight3D node parented to the "
"object."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/introduction_to_global_illumination.rst:363
msgid ""
"For *large* dynamic level geometry (such as a moving train), use the "
"**Dynamic** global illumination mode. Note that this only has an effect with "
"VoxelGI, as SDFGI and LightmapGI do not support global illumination with "
"dynamic objects."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/introduction_to_global_illumination.rst:368
msgid "Here are some recommendations for light bake modes:"
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/introduction_to_global_illumination.rst:370
msgid ""
"For static level lighting, use the **Static** bake mode. The **Static** mode "
"is also suitable for dynamic lights that don't change much during gameplay, "
"such as a flickering torch."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/introduction_to_global_illumination.rst:373
msgid ""
"For short-lived dynamic effects (such as a weapon), use the **Disabled** "
"bake mode to improve performance."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/introduction_to_global_illumination.rst:375
msgid ""
"For long-lived dynamic effects (such as a rotating alarm light), use the "
"**Dynamic** bake mode to improve quality *(default)*. Note that this only "
"has an effect with VoxelGI and SDFGI, as LightmapGI does not support global "
"illumination with dynamic lights."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/introduction_to_global_illumination.rst:383
msgid "Alternatives to GI techniques"
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/introduction_to_global_illumination.rst:385
msgid ""
"If none of the GI techniques mentioned above fits, it's still possible to :"
"ref:`simulate GI by placing additional lights manually "
"<doc_faking_global_illumination>`. This requires more manual work, but it "
"can offer good performance *and* good visuals if done right. This approach "
"is still used in many modern games to this day."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/introduction_to_global_illumination.rst:391
msgid ""
"When targeting low-end hardware in situations where using LightmapGI is not "
"viable (such as procedurally generated levels), relying on environment "
"lighting alone or a constant ambient light factor may be a necessity. This "
"may result in flatter visuals, but adjusting the ambient light color and sky "
"contribution still makes it possible to achieve acceptable results in most "
"cases."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_voxel_gi.rst:4
msgid "Using Voxel global illumination"
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_voxel_gi.rst:6
msgid ""
"VoxelGI is a form of fully real-time global illumination, intended to be "
"used for small/medium-scale 3D scenes. VoxelGI is fairly demanding on the "
"GPU, so it's best used when targeting dedicated graphics cards."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_voxel_gi.rst:12
msgid ""
"VoxelGI is only supported when using the Forward Plus rendering backend, not "
"the Forward Mobile or Compatibility backends."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_voxel_gi.rst:17
msgid ""
"Not sure if VoxelGI is suited to your needs? See :ref:"
"`doc_introduction_to_global_illumination_comparison` for a comparison of GI "
"techniques available in Godot 4."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_voxel_gi.rst:22
#: ../../docs/tutorials/3d/global_illumination/using_sdfgi.rst:31
#: ../../docs/tutorials/3d/global_illumination/using_lightmap_gi.rst:43
#: ../../docs/tutorials/3d/global_illumination/using_lightmap_gi.rst:64
#: ../../docs/tutorials/3d/global_illumination/reflection_probes.rst:32
#: ../../docs/tutorials/3d/mesh_lod.rst:43
msgid "Visual comparison"
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_voxel_gi.rst:27
msgid "VoxelGI disabled."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_voxel_gi.rst:32
msgid "VoxelGI enabled."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_voxel_gi.rst:35
#, fuzzy
msgid "Setting up VoxelGI"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/3d/global_illumination/using_voxel_gi.rst:37
msgid ""
"Make sure your static level geometry is imported with the Light Baking "
"option set to **Static** or **Static Lightmaps** in the Import dock. For "
"manually added MeshInstance3D nodes, make sure the **Global Illumination > "
"Mode** property is set to **Static** in the inspector."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_voxel_gi.rst:41
msgid "Create a VoxelGI node in the Scene tree dock."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_voxel_gi.rst:42
msgid ""
"Move the VoxelGI node to the center of the area you want it to cover by "
"dragging the manipulation gizmo in the 3D viewport. Then adjust the "
"VoxelGI's extents by dragging the red points in the 3D viewport (or enter "
"values in the inspector). Make sure the VoxelGI's extents aren't "
"unnecessarily large, or quality will suffer."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_voxel_gi.rst:47
msgid ""
"Select the VoxelGI node and click **Bake** at the top of the 3D editor "
"viewport. This will take at least a few seconds to complete (depending on "
"the number of VoxelGI subdivisions and scene complexity)."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_voxel_gi.rst:51
msgid ""
"If at least one mesh contained within the VoxelGI's extents has its global "
"illumination mode set to **Static**, you should see indirect lighting appear "
"within the scene."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_voxel_gi.rst:57
msgid ""
"To avoid bloating text-based scene files with large amounts of binary data, "
"make sure the VoxelGIData resource is *always* saved to an external binary "
"file. This file must be saved with a ``.res`` (binary resource) extension "
"instead of ``.tres`` (text-based resource). Using an external binary "
"resource for VoxelGIData will keep your text-based scene small while "
"ensuring it loads and saves quickly."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_voxel_gi.rst:65
#, fuzzy
msgid "VoxelGI node properties"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/3d/global_illumination/using_voxel_gi.rst:67
msgid ""
"The following properties can be adjusted in the VoxelGI node inspector "
"before baking:"
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_voxel_gi.rst:70
msgid ""
"**Subdiv:** Higher values result in more precise indirect lighting, at the "
"cost of lower performance, longer bake times and increased storage "
"requirements."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_voxel_gi.rst:72
msgid ""
"**Extents:** Represents the size of the box in which indirect lighting "
"should be baked. Extents are centered around the VoxelGI node's origin."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_voxel_gi.rst:75
msgid ""
"The following properties can be adjusted in the VoxelGIData *resource* that "
"is contained within a VoxelGI node after it has been baked:"
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_voxel_gi.rst:78
msgid ""
"**Dynamic Range:** The maximum brightness that can be represented in "
"indirect lighting. Higher values make it possible to represent brighter "
"indirect light, at the cost of lower precision (which can result in visible "
"banding). If in doubt, leave this unchanged."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_voxel_gi.rst:82
msgid ""
"**Energy:** The indirect lighting's overall energy. This also effects the "
"energy of direct lighting emitted by meshes with emissive materials."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_voxel_gi.rst:84
msgid ""
"**Bias:** Optional bias added to lookups into the voxel buffer at run time. "
"This helps avoid self-occlusion artifacts."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_voxel_gi.rst:86
msgid ""
"**Normal Bias:** Similar to **Bias**, but offsets the lookup into the voxel "
"buffer by the surface normal. This also helps avoid self-occlusion "
"artifacts. Higher values reduce self-reflections visible in non-rough "
"materials, at the cost of more visible light leaking and flatter-looking "
"indirect lighting. To prioritize hiding self-reflections over lighting "
"quality, set **Bias** to ``0.0`` and **Normal Bias** to a value between "
"``1.0`` and ``2.0``."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_voxel_gi.rst:92
msgid ""
"**Propagation:** The energy factor to use for bounced indirect lighting. "
"Higher values will result in brighter, more diffuse lighting (which may end "
"up looking too flat). When **Use Two Bounces** is enabled, you may want to "
"decrease **Propagation** to compensate for the overall brighter indirect "
"lighting."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_voxel_gi.rst:97
msgid ""
"**Use Two Bounces:** If enabled, lighting will bounce twice instead of just "
"once. This results in more realistic-looking indirect lighting, and makes "
"indirect lighting visible in reflections as well. Enabling this generally "
"has no noticeable performance cost."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_voxel_gi.rst:100
msgid ""
"**Interior:** If enabled, environment sky lighting will not be taken into "
"account by VoxelGI. This should be enabled in indoor scenes to avoid light "
"leaking from the environment."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_voxel_gi.rst:104
#, fuzzy
msgid "VoxelGI interaction with lights and objects"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/3d/global_illumination/using_voxel_gi.rst:106
msgid ""
"To ensure correct visuals when using VoxelGI, you must configure your meshes "
"and lights' global illumination properties according to their *purpose* in "
"the scene (static or dynamic)."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_voxel_gi.rst:110
#: ../../docs/tutorials/3d/global_illumination/using_sdfgi.rst:126
#, fuzzy
msgid "There are 3 global illumination modes available for meshes:"
msgstr "Ne postoje ograničenja prilikom korištenja Godot-a"

#: ../../docs/tutorials/3d/global_illumination/using_voxel_gi.rst:112
msgid ""
"**Disabled:** The mesh won't be taken into account for VoxelGI baking. The "
"mesh will *receive* indirect lighting from the scene, but it will not "
"*contribute* indirect lighting to the scene."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_voxel_gi.rst:115
msgid ""
"**Static (default):** The mesh will be taken into account for VoxelGI "
"baking. The mesh will both receive *and* contribute indirect lighting to the "
"scene. If the mesh is changed in any way after baking, the VoxelGI node must "
"be baked again. Otherwise, indirect lighting will look incorrect."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_voxel_gi.rst:119
msgid ""
"**Dynamic:** The mesh won't be taken into account for VoxelGI baking, but it "
"will still receive *and* contribute indirect lighting to the scene in real-"
"time. This option is much slower compared to **Static**. Only use the "
"**Dynamic** global illumination mode on large meshes that will change "
"significantly during gameplay."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_voxel_gi.rst:124
#: ../../docs/tutorials/3d/global_illumination/using_sdfgi.rst:142
msgid ""
"Additionally, there are 3 bake modes available for lights "
"(DirectionalLight3D, OmniLight3D and SpotLight3D):"
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_voxel_gi.rst:127
msgid ""
"**Disabled:** The light won't be taken into account for VoxelGI baking. The "
"light won't contribute indirect lighting to the scene."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_voxel_gi.rst:129
msgid ""
"**Static:** The light will be taken into account for VoxelGI baking. The "
"light will contribute indirect lighting to the scene. If the light is "
"changed in any way after baking, the VoxelGI node must be baked again or "
"indirect lighting will look incorrect. If in doubt, use this mode for level "
"lighting."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_voxel_gi.rst:133
msgid ""
"**Dynamic (default):** The light won't be taken into account for VoxelGI "
"baking, but it will still contribute indirect lighting to the scene in real-"
"time. This option is slower compared to **Static**. Only use the **Dynamic** "
"global illumination mode on lights that will change significantly during "
"gameplay."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_voxel_gi.rst:140
#: ../../docs/tutorials/3d/global_illumination/using_sdfgi.rst:159
msgid ""
"The amount of indirect energy emitted by a light depends on its color, "
"energy *and* indirect energy properties. To make a specific light emit more "
"or less indirect energy without affecting the amount of direct light emitted "
"by the light, adjust the **Indirect Energy** property in the Light3D "
"inspector."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_voxel_gi.rst:147
#: ../../docs/tutorials/3d/global_illumination/using_sdfgi.rst:166
msgid ""
"See :ref:`doc_introduction_to_global_illumination_gi_mode_recommendations` "
"for general usage recommendations."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_voxel_gi.rst:151
msgid "Adjusting VoxelGI performance and quality"
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_voxel_gi.rst:153
msgid ""
"Since VoxelGI is relatively demanding, it will perform best on systems with "
"recent dedicated GPUs. On older dedicated GPUs and integrated graphics, "
"tweaking the settings is necessary to achieve reasonable performance."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_voxel_gi.rst:157
msgid ""
"In the Project Settings' **Rendering > Global Illumination** section, "
"VoxelGI quality can also be adjusted in two ways:"
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_voxel_gi.rst:160
msgid ""
"**Voxel Gi > Quality:** If set to **Low** instead of **High**, voxel cone "
"tracing will only use 4 taps instead of 6. This speeds up rendering at the "
"cost of less pronounced ambient occlusion."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_voxel_gi.rst:163
msgid ""
"**Gi > Use Half Resolution:** If enabled, both VoxelGI and SDFGI will have "
"their GI buffer rendering at halved resolution. For instance, when rendering "
"in 3840×2160, the GI buffer will be computed at a 1920×1080 resolution. "
"Enabling this option saves a lot of GPU time, but it can introduce visible "
"aliasing around thin details."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_voxel_gi.rst:169
msgid ""
"Note that the **Advanced** toggle must be enabled in the project settings "
"dialog for the above settings to be visible."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_voxel_gi.rst:172
msgid ""
"Additionally, VoxelGI can be disabled entirely by hiding the VoxelGI node. "
"This can be used for comparison purposes or to improve performance on low-"
"end systems."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_voxel_gi.rst:176
msgid "Reducing VoxelGI light leaks and artifacts"
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_voxel_gi.rst:178
msgid ""
"After baking VoxelGI, you may notice indirect light is leaking at some spots "
"in your level geometry. This can be remedied in several ways:"
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_voxel_gi.rst:181
msgid ""
"For both light leaking and artifacts, try moving or rotating the VoxelGI "
"node then bake it again."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_voxel_gi.rst:183
msgid ""
"To combat light leaking in general, ensure your level geometry is fully "
"sealed. This is best done in the 3D modeling software used to design the "
"level, but primitive MeshInstance3D nodes with their global illumination "
"mode set to **Static** can also be used."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_voxel_gi.rst:187
msgid ""
"To combat light leaking with thin geometry, it's recommended to make the "
"geometry in question thicker. If this is not possible, then add a primitive "
"MeshInstance3D node with its global illumination mode set to **Static**. "
"Bake VoxelGI again, then hide the primitive MeshInstance3D node (it will "
"still be taken into account by VoxelGI). For optimal results, the "
"MeshInstance3D should have a material whose color matches the original thin "
"geometry."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_voxel_gi.rst:193
msgid ""
"To combat artifacts that can appear on reflective surfaces, try increasing "
"**Bias** and/or **Normal Bias** in the VoxelGIData resource as described "
"above. Do not increase these values too high, or light leaking will become "
"more pronounced."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_voxel_gi.rst:197
msgid ""
"If you notice VoxelGI nodes popping in and out of existence as the camera "
"moves, this is most likely because the engine is rendering too many VoxelGI "
"instances at once. Godot is limited to rendering 8 VoxelGI nodes at once, "
"which means up to 8 instances can be in the camera view before some of them "
"will start flickering."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_voxel_gi.rst:203
msgid ""
"Additionally, for performance reasons, Godot can only blend between 2 "
"VoxelGI nodes at a given pixel on the screen. If you have more than 2 "
"VoxelGI nodes overlapping, global illumination may appear to flicker as the "
"camera moves or rotates."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_sdfgi.rst:4
msgid "Signed distance field global illumination (SDFGI)"
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_sdfgi.rst:6
msgid ""
"Signed distance field global illumination (SDFGI) is a novel technique "
"available in Godot 4.0. It provides semi-real-time global illumination that "
"scales to any world size and works with procedurally generated levels."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_sdfgi.rst:10
msgid ""
"SDFGI supports dynamic lights, but *not* dynamic occluders or dynamic "
"emissive surfaces. Therefore, SDFGI provides better real-time ability than :"
"ref:`baked lightmaps <doc_using_lightmap_gi>`, but worse real-time ability "
"than :ref:`VoxelGI <doc_using_voxel_gi>`."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_sdfgi.rst:15
msgid ""
"From a performance standpoint, SDFGI is one of the most demanding global "
"illumination techniques in Godot. Like with VoxelGI, there are still many "
"settings available to tweak its performance requirements at the cost of "
"quality."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_sdfgi.rst:21
msgid ""
"SDFGI is only supported when using the Forward Plus rendering backend, not "
"the Forward Mobile or Compatibility backends."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_sdfgi.rst:26
msgid ""
"Not sure if SDFGI is suited to your needs? See :ref:"
"`doc_introduction_to_global_illumination_comparison` for a comparison of GI "
"techniques available in Godot 4."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_sdfgi.rst:36
msgid "SDFGI disabled."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_sdfgi.rst:41
msgid "SDFGI enabled."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_sdfgi.rst:44
#, fuzzy
msgid "Setting up SDFGI"
msgstr "Uvod / Početak"

#: ../../docs/tutorials/3d/global_illumination/using_sdfgi.rst:46
msgid ""
"In Godot, SDFGI is the global illumination technique with the fewest "
"required steps to enable:"
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_sdfgi.rst:49
msgid ""
"Make sure your MeshInstance nodes have their **Global Illumination > Mode** "
"property set to **Static** in the inspector."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_sdfgi.rst:52
msgid ""
"For imported 3D scenes, the bake mode can be configured in the Import dock "
"after selecting the 3D scene file in the FileSystem dock."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_sdfgi.rst:55
msgid "Add a WorldEnvironment node and create an Environment resource for it."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_sdfgi.rst:56
msgid ""
"Edit the Environment resource, scroll down to the **SDFGI** section and "
"unfold it."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_sdfgi.rst:57
msgid ""
"Enable **SDFGI > Enabled**. SDFGI will automatically follow the camera when "
"it moves, so you do not need to configure extents (unlike VoxelGI)."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_sdfgi.rst:61
msgid "Environment SDFGI properties"
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_sdfgi.rst:63
msgid ""
"In the Environment resource, there are several properties available to "
"adjust SDFGI appearance and quality:"
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_sdfgi.rst:66
msgid ""
"**Use Occlusion:** If enabled, SDFGI will throw additional rays to find and "
"reduce light leaks. This has a performance cost, so only enable this "
"property if you actually need it."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_sdfgi.rst:69
msgid ""
"**Read Sky Light:** If enabled, the environment lighting is represented in "
"the global illumination. This should be enabled in outdoor scenes and "
"disabled in fully indoor scenes."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_sdfgi.rst:72
msgid ""
"**Bounce Feedback:** By default, indirect lighting only bounces once when "
"using SDFGI. Setting this value above ``0.0`` will cause SDFGI to bounce "
"more than once, which provides more realistic indirect lighting at a small "
"performance cost. Sensible values are usually between ``0.3`` and ``1.0`` "
"depending on the scene. Note that in some scenes, values above ``0.5`` can "
"cause infinite feedback loops to happen, causing the scene to become "
"extremely bright in a few seconds' time. If your indirect lighting looks "
"\"splotchy\", consider increasing this value above ``0.0`` to get more "
"uniform-looking lighting. If your lighting ends up looking too bright as a "
"result, decrease **Energy** to compensate."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_sdfgi.rst:82
msgid ""
"**Cascades:** Higher values result in more detailed GI information (and/or "
"greater maximum distance), but are significantly more expensive on the CPU "
"and GPU. The performance cost of having more cascades especially increases "
"when the camera moves fast, so consider decreasing this to ``4`` or lower if "
"your camera moves fast."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_sdfgi.rst:87
msgid ""
"**Min Cell Size:** The minimum SDFGI cell size to use for the nearest, most "
"detailed cascade. Lower values result in more accurate indirect lighting and "
"reflection at the cost of lower performance. Adjusting this setting also "
"affects **Cascade 0 Distance** and **Max Distance** automatically."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_sdfgi.rst:91
msgid ""
"**Cascade 0 Distance:** The distance at which the nearest, most detailed "
"cascade ends. Greater values make the nearest cascade transition less "
"noticeable, at the cost of reducing the level of detail in the nearest "
"cascade. Adjusting this setting also affects **Min Cell Size** and **Max "
"Distance** automatically."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_sdfgi.rst:95
msgid ""
"**Max Distance:** Controls how far away the signed distance field will be "
"computed (for the least detailed cascade). SDFGI will not have any effect "
"past this distance. This value should always be set below the Camera's Far "
"value, as there is no benefit in computing SDFGI past the viewing distance. "
"Adjusting this setting also affects **Min Cell Size** and **Cascade 0 "
"Distance** automatically."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_sdfgi.rst:100
msgid ""
"**Y Scale:** Controls how far apart SDFGI probes are spread *vertically*. By "
"default, vertical spread is the same as horizontal. However, since most game "
"scenes aren't highly vertical, setting the Y Scale to ``75%`` or even "
"``50%`` can provide better quality and reduce light leaks without impacting "
"performance."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_sdfgi.rst:105
msgid "**Energy:** The brightness multiplier for SDFGI's indirect lighting."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_sdfgi.rst:106
msgid ""
"**Normal Bias:** The normal bias to use for SDFGI's probe ray bounces. "
"Unlike **Probe Bias**, this only increases the value in relation to the "
"mesh's normals. This makes the bias adjustment more nuanced and avoids "
"increasing the bias too much for no reason. Increase this value if you "
"notice striping artifacts in indirect lighting or reflections."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_sdfgi.rst:111
msgid ""
"**Probe Bias:** The bias to use for SDFGI's probe ray bounces. Increase this "
"value if you notice striping artifacts in indirect lighting or reflections."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_sdfgi.rst:115
#, fuzzy
msgid "SDFGI interaction with lights and objects"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/3d/global_illumination/using_sdfgi.rst:117
msgid ""
"The amount of indirect energy emitted by a light is governed by its color, "
"energy *and* indirect energy properties. To make a specific light emit more "
"or less indirect energy without affecting the amount of direct light emitted "
"by the light, adjust the **Indirect Energy** property in the Light3D "
"inspector."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_sdfgi.rst:122
msgid ""
"To ensure correct visuals when using SDFGI, you must configure your meshes "
"and lights' global illumination properties according to their *purpose* in "
"the scene (static or dynamic)."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_sdfgi.rst:128
msgid ""
"**Disabled:** The mesh won't be taken into account in SDFGI generation. The "
"mesh will receive indirect lighting from the scene, but it will not "
"contribute indirect lighting to the scene."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_sdfgi.rst:131
msgid ""
"**Static (default):** The mesh will be taken into account in SDFGI "
"generation. The mesh will both receive *and* contribute indirect lighting to "
"the scene. If the mesh is changed in any way after SDFGI is generated, the "
"camera must move away from the object then move back close to it for SDFGI "
"to regenerate. Alternatively, SDFGI can be toggled off and back on. If "
"neither is done, indirect lighting will look incorrect."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_sdfgi.rst:137
msgid ""
"**Dynamic (not supported with SDFGI):** The mesh won't be taken into account "
"in SDFGI generation. The mesh will receive indirect lighting from the scene, "
"but it will not contribute indirect lighting to the scene. *This acts "
"identical to the **Disabled** bake mode when using SDFGI.*"
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_sdfgi.rst:145
msgid ""
"**Disabled:** The light won't be taken into account for SDFGI baking. The "
"light won't contribute indirect lighting to the scene."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_sdfgi.rst:147
msgid ""
"**Static:** The light will be taken into account for SDFGI baking. The light "
"will contribute indirect lighting to the scene. If the light is changed in "
"any way after baking, indirect lighting will look incorrect until the camera "
"moves away from the light and back (which causes SDFGI to be baked again). "
"will look incorrect. If in doubt, use this mode for level lighting."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_sdfgi.rst:152
msgid ""
"**Dynamic (default):** The light won't be taken into account for SDFGI "
"baking, but it will still contribute indirect lighting to the scene in real-"
"time. This option is slower compared to **Static**. Only use the **Dynamic** "
"global illumination mode on lights that will change significantly during "
"gameplay."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_sdfgi.rst:170
msgid "Adjusting SDFGI performance and quality"
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_sdfgi.rst:172
msgid ""
"Since SDFGI is relatively demanding, it will perform best on systems with "
"recent dedicated GPUs. On older dedicated GPUs and integrated graphics, "
"tweaking the settings is necessary to achieve reasonable performance."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_sdfgi.rst:176
msgid ""
"In the Project Settings' **Rendering > Global Illumination** section, SDFGI "
"quality can also be adjusted in several ways:"
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_sdfgi.rst:179
msgid ""
"**Sdfgi > Probe Ray Count:** Higher values result in better quality, at the "
"cost of higher GPU usage. If this value is set too low, this can cause "
"surfaces to have visible \"splotches\" of indirect lighting on them due to "
"the number of rays thrown being very low."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_sdfgi.rst:183
msgid ""
"**Sdfgi > Frames To Converge:** Higher values result in better quality, but "
"GI will take more time to fully converge. The effect of this setting is "
"especially noticeable when first loading a scene, or when lights with a bake "
"mode other than **Disabled** are moving fast. If this value is set too low, "
"this can cause surfaces to have visible \"splotches\" of indirect lighting "
"on them due to the number of rays thrown being very low. If your scene's "
"lighting doesn't have fast-moving lights that contribute to GI, consider "
"setting this to ``30`` to improve quality without impacting performance."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_sdfgi.rst:190
msgid ""
"**Sdfgi > Frames To Update Light:** Lower values result in moving lights "
"being reflected faster, at the cost of higher GPU usage. If your scene's "
"lighting doesn't have fast-moving lights that contribute to GI, consider "
"setting this to ``16`` to improve performance."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_sdfgi.rst:194
msgid ""
"**Gi > Use Half Resolution:** If enabled, both SDFGI and VoxelGI will have "
"their GI buffer rendering at halved resolution. For instance, when rendering "
"in 3840×2160, the GI buffer will be computed at a 1920×1080 resolution. "
"Enabling this option saves a lot of GPU time, but it can introduce visible "
"aliasing around thin details."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_sdfgi.rst:200
msgid ""
"SDFGI rendering performance also depends on the number of cascades and the "
"cell size chosen in the Environment resource (see above)."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_sdfgi.rst:204
msgid "SDFGI caveats"
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_sdfgi.rst:206
msgid ""
"SDFGI has some downsides due to its cascaded nature. When the camera moves, "
"cascade shifts may be visible in indirect lighting. This can be alleviated "
"by adjusting the cascade size, but also by adding fog (which will make "
"distant cascade shifts less noticeable)."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_sdfgi.rst:211
msgid ""
"Additionally, performance will suffer if the camera moves too fast. This can "
"be fixed in two ways:"
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_sdfgi.rst:214
msgid "Ensuring the camera doesn't move too fast in any given situation."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_sdfgi.rst:215
msgid ""
"Temporarily disabling SDFGI in the Environment resource if the camera needs "
"to be moved at a high speed, then enabling SDFGI once the camera speed slows "
"down."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_sdfgi.rst:218
msgid ""
"When SDFGI is enabled, it will also take some time for global illumination "
"to be fully converged (25 frames by default). This can create a noticeable "
"transition effect while GI is still converging. To hide this, you can use a "
"ColorRect node that spans the whole viewport and fade it out when switching "
"scenes using an AnimationPlayer node."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_sdfgi.rst:224
msgid ""
"The signed distance field is only updated when the camera moves in and out "
"of a cascade. This means that if geometry is modified in the distance, the "
"global illumination appearance will be correct once the camera gets closer. "
"However, if a nearby object with a bake mode set to **Static** or "
"**Dynamic** is moved (such as a door), the global illumination will appear "
"incorrect until the camera moves away from the object."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_sdfgi.rst:231
msgid ""
"SDFGI's sharp reflections are only visible on opaque materials. Transparent "
"materials will only use rough reflections, even if the material's roughness "
"is lower than 0.2."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_lightmap_gi.rst:4
msgid "Using Lightmap global illumination"
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_lightmap_gi.rst:6
msgid ""
"Baked lightmaps are a workflow for adding indirect (or fully baked) lighting "
"to a scene. Unlike the :ref:`VoxelGI <doc_using_voxel_gi>` and :ref:`SDFGI "
"<doc_using_sdfgi>` approaches, baked lightmaps work fine on low-end PCs and "
"mobile devices, as they consume almost no resources at run-time. Also unlike "
"VoxelGI and SDFGI, baked lightmaps can optionally be used to store direct "
"lighting, which provides even further performance gains."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_lightmap_gi.rst:13
msgid ""
"Unlike VoxelGI and SDFGI, baked lightmaps are completely static. Once baked, "
"they can't be modified at all. They also don't provide the scene with "
"reflections, so using :ref:`doc_reflection_probes` together with it on "
"interiors (or using a Sky on exteriors) is a requirement to get good quality."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_lightmap_gi.rst:18
msgid ""
"As they are baked, they have fewer problems than VoxelGI and SDFGI regarding "
"light bleeding, and indirect light will often look better. The downside is "
"that baking lightmaps takes longer compared to baking VoxelGI. While baking "
"VoxelGI can be done in a matter of seconds, baking lightmaps can take "
"several minutes if not more. This can slow down iteration speed "
"significantly, so it is recommended to bake lightmaps only when you actually "
"need to see changes in lighting. Since Godot 4.0, lightmaps are baked on the "
"GPU, making light baking faster if you have a mid-range or high-end "
"dedicated GPU."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_lightmap_gi.rst:27
msgid ""
"Baking lightmaps will also reserve baked materials' UV2 slot, which means "
"you can no longer use it for other purposes in materials (either in the "
"built-in :ref:`doc_standard_material_3d` or in custom shaders)."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_lightmap_gi.rst:31
msgid ""
"Despite their lack of flexibility, baked lightmaps typically offer both the "
"best quality *and* performance at the same time in (mostly) static scenes. "
"This makes lightmaps still popular in game development, despite lightmaps "
"being the oldest technique for global illumination in video games."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_lightmap_gi.rst:38
msgid ""
"Not sure if LightmapGI is suited to your needs? See :ref:"
"`doc_introduction_to_global_illumination_comparison` for a comparison of GI "
"techniques available in Godot 4."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_lightmap_gi.rst:48
msgid "LightmapGI disabled."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_lightmap_gi.rst:53
msgid "LightmapGI enabled (with indirect light baked only)."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_lightmap_gi.rst:53
msgid ""
"LightmapGI enabled (with indirect light baked only). Direct light is still "
"real-time, allowing for subtle changes during gameplay."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_lightmap_gi.rst:59
msgid "LightmapGI enabled (with direct and indirect light baked)."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_lightmap_gi.rst:59
msgid ""
"LightmapGI enabled (with direct and indirect light baked). Best performance, "
"but lower quality visuals. Notice the blurrier sun shadow in the top-right "
"corner."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_lightmap_gi.rst:66
msgid ""
"Here are some comparisons of how LightmapGI vs. VoxelGI look. Notice that "
"lightmaps are more accurate, but also suffer from the fact that lighting is "
"on an unwrapped texture, so transitions and resolution may not be that good. "
"VoxelGI looks less accurate (as it's an approximation), but smoother overall."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_lightmap_gi.rst:74
msgid ""
"SDFGI is also less accurate compared to LightmapGI. However, SDFGI can "
"support large open worlds without any need for baking."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_lightmap_gi.rst:78
#: ../../docs/tutorials/shaders/your_first_shader/your_first_3d_shader.rst:62
msgid "Setting up"
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_lightmap_gi.rst:80
msgid ""
"First of all, before the lightmapper can do anything, the objects to be "
"baked need an UV2 layer and a texture size. An UV2 layer is a set of "
"secondary texture coordinates that ensures any face in the object has its "
"own place in the UV map. Faces must not share pixels in the texture."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_lightmap_gi.rst:85
msgid ""
"There are a few ways to ensure your object has a unique UV2 layer and "
"texture size:"
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_lightmap_gi.rst:88
msgid "Unwrap on scene import (recommended)"
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_lightmap_gi.rst:90
msgid ""
"In most scenarios, this is the best approach to use. The only downside is "
"that, on large models, unwrapping can take a while on import. Nonetheless, "
"Godot will cache the UV2 across reimports, so it will only be regenerated "
"when needed."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_lightmap_gi.rst:94
msgid ""
"Select the imported scene in the filesystem dock, then go to the **Import** "
"dock. There, the following option can be modified:"
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_lightmap_gi.rst:99
msgid ""
"The **Meshes > Light Baking** option must be set to **Static Lightmaps "
"(VoxelGI/SDFGI/LightmapGI)**:"
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_lightmap_gi.rst:103
msgid ""
"When unwrapping on import, you can adjust the texture size using the "
"**Meshes > Lightmap Texel Size** option. *Lower* values will result in more "
"detailed lightmaps, possibly resulting in higher visual quality at the cost "
"of longer bake times and larger lightmap file sizes. The default value of "
"``0.2`` is suited for small/medium-sized scenes, but you may want to "
"increase it to ``0.5`` or even more for larger scenes. This is especially "
"the case if you're baking indirect lighting only, as indirect light is low-"
"frequency data (which means it doesn't need high-resolution textures to be "
"accurately represented)."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_lightmap_gi.rst:112
msgid ""
"The effect of setting this option is that all meshes within the scene will "
"have their UV2 maps properly generated."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_lightmap_gi.rst:117
msgid ""
"When reusing a mesh within a scene, keep in mind that UVs will be generated "
"for the first instance found. If the mesh is re-used with different scales "
"(and the scales are wildly different, more than half or twice), this will "
"result in inefficient lightmaps. To avoid this, adjust the **Lightmap "
"Scale** property in the GeometryInstance3D section of a MeshInstance3D node. "
"This lets you *increase* the level of lightmap detail for specific "
"MeshInstance3D nodes (but not decrease it)."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_lightmap_gi.rst:125
msgid ""
"Also, the ``*.unwrap_cache`` files should *not* be ignored in version "
"control as these files guarantee that UV2 reimports are consistent across "
"platforms and engine versions."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_lightmap_gi.rst:130
msgid "Unwrap from within Godot"
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_lightmap_gi.rst:134
msgid ""
"If this Mesh menu operation is used on an imported 3D scene, the generated "
"UV2 will be lost when the scene is reloaded."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_lightmap_gi.rst:137
msgid ""
"Godot has an option to unwrap meshes and visualize the UV channels. After "
"selecting a MeshInstance3D node, it can be found in the **Mesh** menu at the "
"top of the 3D editor viewport:"
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_lightmap_gi.rst:143
msgid ""
"This will generate a second set of UV2 coordinates which can be used for "
"baking. It will also set the texture size automatically."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_lightmap_gi.rst:147
msgid "Unwrap from your 3D modeling software"
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_lightmap_gi.rst:149
msgid ""
"The last option is to do it from your favorite 3D app. This approach is "
"generally **not recommended**, but it's explained so that you know it "
"exists. The main advantage is that, on complex objects that you may want to "
"re-import a lot, the texture generation process can be quite costly within "
"Godot, so having it unwrapped before import can be faster."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_lightmap_gi.rst:155
msgid "Simply do an unwrap on the second UV2 layer."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_lightmap_gi.rst:159
msgid ""
"Then import the 3D scene normally. Remember you will need to set the texture "
"size on the mesh after import."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_lightmap_gi.rst:164
msgid ""
"If you use external meshes on import, the size will be kept. Be wary that "
"most unwrappers in 3D modeling software are not quality-oriented, as they "
"are meant to work quickly. You will mostly need to use seams or other "
"techniques to create better unwrapping."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_lightmap_gi.rst:170
msgid "Generating UV2 for primitive meshes"
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_lightmap_gi.rst:174
msgid ""
"This option is only available for primitive meshes such as :ref:"
"`class_BoxMesh`, :ref:`class_CylinderMesh`, :ref:`class_PlaneMesh`, etc."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_lightmap_gi.rst:177
msgid ""
"Enabling UV2 on primitive meshes allows you to make them receive and "
"contribute to baked lighting. This can be used in certain lighting setups. "
"For instance, you could hide a torus that has an emissive material after "
"baking lightmaps to create an area light that follows the shape of a torus."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_lightmap_gi.rst:182
msgid ""
"By default, primitive meshes do not have UV2 generated to save resources (as "
"these meshes may be created during gameplay). You can edit a primitive mesh "
"in the inspector and enable **Add UV2** to make the engine procedurally "
"generate UV2 for a primitive mesh. The default **UV2 Padding** value is "
"tuned to avoid most lightmap bleeding, without wasting too much space on the "
"edges. If you notice lightmap bleeding on a specific primitive mesh only, "
"you may have to increase **UV2 Padding**."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_lightmap_gi.rst:190
msgid ""
"**Lightmap Size Hint** represents the size taken by a single mesh on the "
"lightmap texture, which varies depending on the mesh's size properties and "
"the **UV2 Padding** value. **Lightmap Size Hint** should not be manually "
"changed, as any modifications will be lost when the scene is reloaded."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_lightmap_gi.rst:196
msgid "Checking UV2"
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_lightmap_gi.rst:198
msgid ""
"In the **Mesh** menu mentioned before, the UV2 texture coordinates can be "
"visualized. If something is failing, double-check that the meshes have these "
"UV2 coordinates:"
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_lightmap_gi.rst:204
msgid "Setting up the scene"
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_lightmap_gi.rst:206
msgid ""
"Before anything is done, a **LightmapGI** node needs to be added to a scene. "
"This will enable light baking on all nodes (and sub-nodes) in that scene, "
"even on instanced scenes."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_lightmap_gi.rst:212
msgid ""
"A sub-scene can be instanced several times, as this is supported by the "
"baker. Each instance will be assigned a lightmap of its own. To avoid issues "
"with inconsistent lightmap texel scaling, make sure to respect the rule "
"about mesh scaling mentioned before."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_lightmap_gi.rst:218
msgid "Setting up meshes"
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_lightmap_gi.rst:220
msgid ""
"For a **MeshInstance3D** node to take part in the baking process, it needs "
"to have its bake mode set to **Static**. Meshes that have their bake mode "
"set to **Disabled** or **Dynamic** will be ignored by the lightmapper."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_lightmap_gi.rst:226
msgid ""
"When auto-generating lightmaps on scene import, this is enabled "
"automatically."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_lightmap_gi.rst:229
msgid "Setting up lights"
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_lightmap_gi.rst:231
msgid ""
"Lights are baked with indirect light only by default. This means that "
"shadowmapping and lighting are still dynamic and affect moving objects, but "
"light bounces from that light will be baked."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_lightmap_gi.rst:235
msgid ""
"Lights can be disabled (no bake) or be fully baked (direct and indirect). "
"This can be controlled from the **Bake Mode** menu in lights:"
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_lightmap_gi.rst:240
msgid "The modes are:"
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_lightmap_gi.rst:243
msgid "Disabled"
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_lightmap_gi.rst:245
msgid ""
"The light is ignored when baking lightmaps. This is the mode to use for "
"dynamic lighting effects such as explosions and weapon effects."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_lightmap_gi.rst:250
msgid ""
"Hiding a light has no effect on the resulting lightmap bake. This means you "
"must use the Disabled bake mode instead of hiding the Light node by "
"disabling its **Visible** property."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_lightmap_gi.rst:255
msgid "Dynamic"
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_lightmap_gi.rst:257
msgid ""
"This is the default mode, and is a compromise between performance and real-"
"time friendliness. Only indirect lighting will be baked. Direct light and "
"shadows are still real-time, as they would be without LightmapGI."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_lightmap_gi.rst:261
msgid ""
"This mode allows performing *subtle* changes to a light's color, energy and "
"position while still looking fairly correct. For example, you can use this "
"to create flickering static torches that have their indirect light baked."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_lightmap_gi.rst:266
msgid "Static"
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_lightmap_gi.rst:268
msgid ""
"Both indirect and direct lighting will be baked. Since static surfaces can "
"skip lighting and shadow computations entirely, this mode provides the best "
"performance along with smooth shadows that never fade based on distance. The "
"real-time light will not affect baked surfaces anymore, but it will still "
"affect dynamic objects. When using the **All** bake mode on a light, dynamic "
"objects will not cast real-time shadows onto baked surfaces, so you need to "
"use a different approach such as blob shadows instead. Blob shadows can be "
"implemented with a Decal node."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_lightmap_gi.rst:277
msgid ""
"The light will not be adjustable at all during gameplay. Moving the light or "
"changing its color (or energy) will not have any effect on static surfaces."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_lightmap_gi.rst:280
msgid ""
"Since bake modes can be adjusted on a per-light basis, it is possible to "
"create hybrid baked light setups. One popular option is to use a real-time "
"DirectionalLight with its bake mode set to **Dynamic**, and use the "
"**Static** bake mode for OmniLights and SpotLights. This provides good "
"performance while still allowing dynamic objects to cast real-time shadows "
"in outdoor areas."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_lightmap_gi.rst:286
msgid ""
"Fully baked lights can also make use of light nodes' **Size** (omni/spot) or "
"**Angular Distance** (directional) properties. This allows for shadows with "
"realistic penumbra that increases in size as the distance between the caster "
"and the shadow increases. This also has a lower performance cost compared to "
"real-time PCSS shadows, as only dynamic objects have real-time shadows "
"rendered on them."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_lightmap_gi.rst:296
msgid "Baking"
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_lightmap_gi.rst:298
msgid ""
"To begin the bake process, click the **Bake Lightmaps** button at the top of "
"the 3D editor viewport when selecting the LightmapGI node:"
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_lightmap_gi.rst:303
msgid ""
"This can take from seconds to minutes (or hours) depending on scene size, "
"bake method and quality selected."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_lightmap_gi.rst:308
msgid ""
"Baking lightmaps is a process that can require a lot of video memory, "
"especially if the resulting texture is large. Due to internal limitations, "
"the engine may also crash if the generated texture size is too large (even "
"on systems with a lot of video memory)."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_lightmap_gi.rst:313
msgid ""
"To avoid crashes, make sure the lightmap texel size in the Import dock is "
"set to a high enough value."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_lightmap_gi.rst:317
msgid "Tweaks"
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_lightmap_gi.rst:319
msgid ""
"**Quality:** Four bake quality modes are provided: Low, Medium, High, and "
"Ultra. Higher quality takes more time, but result in a better-looking "
"lightmap with less noise. The difference is especially noticeable with "
"emissive materials or areas that get little to no direct lighting. Each bake "
"quality mode can be further adjusted in the Project Settings."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_lightmap_gi.rst:324
msgid ""
"**Bounces:** The number of bounces to use for indirect lighting. The default "
"value (``3``) is a good compromise between bake times and quality. Higher "
"values will make light bounce around more times before it stops, which makes "
"indirect lighting look smoother (but also possibly brighter depending on "
"materials and geometry)."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_lightmap_gi.rst:329
msgid ""
"**Bounce Indirect Energy:** The global multiplier to use when baking lights' "
"indirect energy. This multiplies each light's own **Indirect Energy** value. "
"Values different from ``1.0`` are not physically accurate, but can be used "
"for artistic effect."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_lightmap_gi.rst:333
msgid ""
"**Directional:** If enabled, stores directional information for lightmaps. "
"This improves normal mapped materials' appearance for baked surfaces, "
"especially with fully baked lights (since they also have direct light "
"baked). The downside is that directional lightmaps are slightly more "
"expensive to render. They also require more time to bake and result in "
"larger file sizes."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_lightmap_gi.rst:338
msgid ""
"**Interior:** If enabled, environment lighting will not be sourced. Use this "
"for purely indoor scenes to avoid light leaks."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_lightmap_gi.rst:340
msgid ""
"**Use Texture for Bounces:** If enabled, a texture with the lighting "
"information will be generated to speed up the generation of indirect "
"lighting at the cost of some accuracy. The geometry might exhibit extra "
"light leak artifacts when using low resolution lightmaps or UVs that stretch "
"the lightmap significantly across surfaces. Leave this enabled if unsure."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_lightmap_gi.rst:345
msgid ""
"**Use Denoiser:** If enabled, uses a denoising algorithm to make the "
"lightmap significantly less noisy. This increases bake times and can "
"occasionally introduce artifacts, but the result is often worth it. See :ref:"
"`doc_using_lightmap_gi_denoising` for more information."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_lightmap_gi.rst:349
msgid ""
"**Denoiser Strength:** The strength of denoising step applied to the "
"generated lightmaps. Higher values are more effective at removing noise, but "
"can reduce shadow detail for static shadows. Only effective if denoising is "
"enabled and the denoising method is :abbr:`JNLM (Non-Local Means with Joint "
"Filtering)` (:abbr:`OIDN (Open Image Denoise)` does not have a denoiser "
"strength setting)."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_lightmap_gi.rst:354
msgid ""
"**Bias:** The offset value to use for shadows in 3D units. You generally "
"don't need to change this value, except if you run into issues with light "
"bleeding or dark spots in your lightmap after baking. This setting does not "
"affect real-time shadows casted on baked surfaces (for lights with "
"**Dynamic** bake mode)."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_lightmap_gi.rst:358
msgid ""
"**Max Texture Size:** The maximum texture size for the generated texture "
"atlas. Higher values will result in fewer slices being generated, but may "
"not work on all hardware as a result of hardware limitations on texture "
"sizes. Leave this at its default value of ``16384`` if unsure."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_lightmap_gi.rst:362
msgid ""
"**Environment > Mode:** Controls how environment lighting is sourced when "
"baking lightmaps. The default value of **Scene** is suited for levels with "
"visible exterior parts. For purely indoor scenes, set this to **Disabled** "
"to avoid light leaks and speed up baking. This can also be set to **Custom "
"Sky** or **Custom Color** to use environment lighting that differs from the "
"actual scene's environment sky."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_lightmap_gi.rst:368
msgid ""
"**Gen Probes > Subdiv:** See :ref:`doc_using_lightmap_gi_dynamic_objects`."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_lightmap_gi.rst:369
msgid "**Data > Light Data:** See :ref:`doc_using_lightmap_gi_data`."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_lightmap_gi.rst:372
msgid "Balancing bake times with quality"
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_lightmap_gi.rst:374
msgid ""
"Since high-quality bakes can take very long (up to dozens of minutes for "
"large complex scenes), it is recommended to use lower quality settings at "
"first. Then, once you are confident with your scene's lighting setup, raise "
"the quality settings and perform a \"final\" bake before exporting your "
"project."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_lightmap_gi.rst:379
msgid ""
"Reducing the lightmap resolution by increasing **Lightmap Texel Size** on "
"the imported 3D scenes will also speed up baking significantly. However, "
"this will require you to reimport all lightmapped 3D scenes before you can "
"bake lightmaps again."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_lightmap_gi.rst:387
msgid "Denoising"
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_lightmap_gi.rst:389
msgid ""
"Since baking lightmaps relies on raytracing, there will always be visible "
"noise in the \"raw\" baked lightmap. Noise is especially visible in areas "
"that are difficult to reach by bounced light, such as indoor areas with "
"small openings where the sunlight can enter. Noise can be reduced by "
"increasing bake quality, but doing so will increase bake times significantly."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_lightmap_gi.rst:399
msgid "Comparison between denoising disabled and enabled"
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_lightmap_gi.rst:399
msgid ""
"Comparison between denoising disabled and enabled (with the default JNLM "
"denoiser)."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_lightmap_gi.rst:401
msgid ""
"To combat noise without increasing bake times too much, a denoiser can be "
"used. A denoiser is an algorithm that runs on the final baked lightmap, "
"detects patterns of noise and softens them while attempting to best preseve "
"detail. Godot offers two denoising algorithms:"
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_lightmap_gi.rst:407
msgid "JNLM (Non-Local Means with Joint Filtering)"
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_lightmap_gi.rst:409
msgid ""
"JNLM is the default denoising method and is included in Godot. It uses a "
"simple but efficient denoising algorithm known as *non-local means*. JNLM "
"runs on the GPU using a compute shader, and is compatible with any GPU that "
"can run Godot 4's Vulkan-based rendering methods. No additional setup is "
"required."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_lightmap_gi.rst:414
msgid ""
"JNLM's denoising can be adjusted using the **Denoiser Strength** property "
"that is visible when **Use Denoiser** enabled. Higher values can be more "
"effective at removing noise, at the cost of suppressing shadow detail for "
"static shadows."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_lightmap_gi.rst:422
msgid "Comparison between JNLM denoiser strength values"
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_lightmap_gi.rst:422
msgid ""
"Comparison between JNLM denoiser strength values. Higher values can reduce "
"detail."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_lightmap_gi.rst:425
msgid "OIDN (Open Image Denoise)"
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_lightmap_gi.rst:427
msgid ""
"Unlike JNLM, OIDN uses a machine learning approach to denoising lightmaps. "
"It features a model specifically trained to remove noise from lightmaps "
"while preserving more shadow detail in most scenes compared to JNLM."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_lightmap_gi.rst:431
msgid ""
"OIDN can run on the GPU if hardware acceleration is configured. With a "
"modern high-end GPU, this can provide a speedup of over 50× over CPU-based "
"denoising:"
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_lightmap_gi.rst:434
msgid "On AMD GPUs, HIP must be installed and configured."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_lightmap_gi.rst:435
msgid ""
"On NVIDIA GPUs, CUDA must be installed and configured. This may "
"automatically be done by the NVIDIA installer, but on Linux, CUDA libraries "
"may not be installed by default. Double-check that the CUDA packages from "
"your Linux distribution are installed."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_lightmap_gi.rst:439
msgid "On Intel GPUs, SYCL must be installed and configured."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_lightmap_gi.rst:441
msgid ""
"If hardware acceleration is not available, OIDN will fall back to "
"multithreaded CPU-based denoising. To confirm whether GPU-based denoising is "
"working, use a GPU utilization monitor while baking lightmaps and look at "
"the GPU utilization percentage and VRAM utilization while the denoising step "
"is shown in the Godot editor. The ``nvidia-smi`` command line tool can be "
"useful for this."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_lightmap_gi.rst:447
msgid ""
"OIDN is not included with Godot due to its relatively large download size. "
"You can download precompiled OIDN binary packages from its `website <https://"
"www.openimagedenoise.org/downloads.html>`__. Extract the package to a "
"location on your PC, then specify the path to the ``oidnDenoise`` executable "
"in the Editor Settings (**FileSystem > Tools > OIDN > OIDN Denoise Path**). "
"This executable is located within the ``bin`` folder of the binary package "
"you extracted."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_lightmap_gi.rst:455
msgid ""
"After specifying the path to the OIDN denoising executable, change the "
"denoising method in the project settings by setting **Rendering > "
"Lightmapping > Denoiser** to **OIDN**. This will affect all lightmap bakes "
"on this project after the setting is changed."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_lightmap_gi.rst:462
msgid ""
"The denoising method is configured in the project settings instead of the "
"editor settings. This is done so that different team members working on the "
"same project are assured to be using the same denoising method for "
"consistent results."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_lightmap_gi.rst:471
msgid "Comparison between JNLM and OIDN denoisers"
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_lightmap_gi.rst:471
msgid ""
"Comparison between JNLM and OIDN denoisers. Notice how OIDN better preserves "
"detail and reduces seams across different objects."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_lightmap_gi.rst:477
msgid "Dynamic objects"
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_lightmap_gi.rst:479
msgid ""
"Unlike VoxelGI and SDFGI, dynamic objects receive indirect lighting "
"differently compared to static objects. This is because lightmapping is only "
"performed on static objects."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_lightmap_gi.rst:483
msgid ""
"To display indirect lighting on dynamic objects, a 3D probe system is used, "
"with light probes being spread throughout the scene. When baking lightmaps, "
"the lightmapper will calculate the amount of *indirect* light received by "
"the probe. Direct light is not stored within light probes, even for lights "
"that have their bake mode set to **Static** (as dynamic objects continue to "
"be lit in real-time)."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_lightmap_gi.rst:490
#, fuzzy
msgid "There are 2 ways to add light probes to a scene:"
msgstr "Ne postoje ograničenja prilikom korištenja Godot-a"

#: ../../docs/tutorials/3d/global_illumination/using_lightmap_gi.rst:492
msgid ""
"**Automatic:** Set **Gen Probes > Subdiv** to a value other than "
"**Disabled**, then bake lightmaps. The default is ``8``, but you can choose "
"a greater value to improve precision at the cost of longer bake times and "
"larger output file size."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_lightmap_gi.rst:496
msgid ""
"**Manual:** In addition or as an alternative to generating probes "
"automatically, you can add light probes manually by adding :ref:"
"`class_LightmapProbe` nodes to the scene. This can be used to improve "
"lighting detail in areas frequently travelled by dynamic objects. After "
"placing LightmapProbe nodes in the scene, you must bake lightmaps again for "
"them to be effective."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_lightmap_gi.rst:504
msgid ""
"After baking lightmaps, you will notice white spheres in the 3D scene that "
"represent how baked lighting will affect dynamic objects. These spheres do "
"**not** appear in the running project."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_lightmap_gi.rst:508
msgid ""
"If you want to hide these spheres in the editor, toggle **View > Gizmos > "
"LightmapGI** at the top of the 3D editor (a \"closed eye\" icon indicates "
"the gizmo is hidden)."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_lightmap_gi.rst:515
msgid "Lightmap data"
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_lightmap_gi.rst:517
msgid ""
"The **Data > Light Data** property in the LightmapGI node contains the "
"lightmap data after baking. Textures are saved to disk, but this also "
"contains the capture data for dynamic objects, which can be heavy. If you "
"are using a scene in ``.tscn`` format, you should save this resource to an "
"external binary ``.lmbake`` file to avoid bloating the ``.tscn`` scene with "
"binary data encoded in Base64."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_lightmap_gi.rst:526
msgid ""
"The generated EXR file can be viewed and even edited using an image editor "
"to perform post-processing if needed. However, keep in mind that changes to "
"the EXR file will be lost when baking lightmaps again."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_lightmap_gi.rst:531
msgid "Reducing LightmapGI artifacts"
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/using_lightmap_gi.rst:533
msgid ""
"If you notice LightmapGI nodes popping in and out of existence as the camera "
"moves, this is most likely because the engine is rendering too many "
"LightmapGI instances at once. Godot is limited to rendering 8 LightmapGI "
"nodes at once, which means up to 8 instances can be in the camera view "
"before some of them will start flickering."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/reflection_probes.rst:4
msgid "Reflection probes"
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/reflection_probes.rst:8
msgid ""
"Reflection probes are only supported in the Clustered Forward and Forward "
"Mobile rendering backends, not the Compatibility backend."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/reflection_probes.rst:11
msgid ""
"As stated in the :ref:`doc_standard_material_3d`, objects can show reflected "
"and/or diffuse light. Reflection probes are used as a source of reflected "
"*and* ambient light for objects inside their area of influence. They can be "
"used to provide more accurate reflections than :ref:`VoxelGI "
"<doc_using_voxel_gi>` and :ref:`SDFGI <doc_using_sdfgi>` while being fairly "
"cheap on system resources."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/reflection_probes.rst:17
msgid ""
"Since reflection probes can also store ambient light, they can be used as a "
"low-end alternative to VoxelGI and SDFGI when :ref:`baked lightmaps "
"<doc_using_lightmap_gi>` aren't viable (e.g. in procedurally generated "
"levels)."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/reflection_probes.rst:21
msgid ""
"Reflection probes can also be used at the same time as screen-space "
"reflections to provide reflections for off-screen objects. In this case, "
"Godot will blend together the screen-space reflections and reflections from "
"reflection probes."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/reflection_probes.rst:27
msgid ""
"Not sure if ReflectionProbe is suited to your needs? See :ref:"
"`doc_introduction_to_global_illumination_comparison` for a comparison of GI "
"techniques available in Godot 4."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/reflection_probes.rst:38
msgid "Reflection probe disabled. Environment sky is used as a fallback."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/reflection_probes.rst:44
#: ../../docs/tutorials/3d/global_illumination/reflection_probes.rst:51
msgid "Reflection probe enabled."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/reflection_probes.rst:51
msgid ""
"Reflection probe enabled with LightmapGI used at the same time. The lightmap "
"appears in the reflection."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/reflection_probes.rst:53
msgid ""
"By combining reflection probes with screen-space reflections, you can get "
"the best of both worlds: high-quality reflections for general room structure "
"(that remain present when off-screen), while also having real-time "
"reflections for small details."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/reflection_probes.rst:62
msgid "Reflections in a room using ReflectionProbe only."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/reflection_probes.rst:62
msgid ""
"Reflections in a room using ReflectionProbe only. Notice how small details "
"don't have any reflections."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/reflection_probes.rst:69
msgid "Reflections in a room using screen-space reflections only."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/reflection_probes.rst:69
msgid ""
"Reflections in a room using screen-space reflections only. Notice how the "
"reflection on the sides of the room's walls is partly missing due to being "
"off-screen."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/reflection_probes.rst:77
msgid ""
"Reflections in a room using ReflectionProbe and screen-space reflections "
"together."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/reflection_probes.rst:77
msgid ""
"Reflections in a room using ReflectionProbe and screen-space reflections "
"together. The screen-space reflections are blended with the reflection "
"probe, acting as a fallback in situations where the reflection probe fails "
"to display any reflection."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/reflection_probes.rst:83
#, fuzzy
msgid "Setting up a ReflectionProbe"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/3d/global_illumination/reflection_probes.rst:85
msgid "Add a :ref:`class_ReflectionProbe` node."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/reflection_probes.rst:86
msgid ""
"Configure the ReflectionProbe's extents in the inspector to fit your scene. "
"To get reasonably accurate reflections, you should generally have one "
"ReflectionProbe node per room (sometimes more for large rooms)."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/reflection_probes.rst:92
msgid ""
"Remember that ReflectionProbe extents don't have to be square, and you can "
"even rotate the ReflectionProbe node to fit rooms that aren't aligned with "
"the X/Z grid. Use this to your advantage to better cover rooms without "
"having to place too many ReflectionProbe nodes."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/reflection_probes.rst:98
msgid "ReflectionProbe properties"
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/reflection_probes.rst:100
msgid ""
"**Update Mode:** Controls when the reflection probe updates. **Once** only "
"renders the scene once every time the ReflectionProbe is moved. This makes "
"it much faster to render compared to the **Always** update mode, which "
"forces the probe to re-render everything around it every frame. Leave this "
"property on **Once** (default) unless you need the reflection probe to "
"update every frame."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/reflection_probes.rst:106
msgid ""
"**Intensity:** The brightness of the reflections and ambient lighting. This "
"usually doesn't need to be changed from its default value of ``1.0``, but "
"you can decrease it ``1.0`` if you find that reflections look too strong."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/reflection_probes.rst:109
msgid ""
"**Max Distance:** Controls the maximum distance used by the "
"ReflectionProbe's internal camera. The distance is always at least equal to "
"the **Extents**, but this can be increased to make objects located outside "
"the extents visible in reflections. *This property does not affect the "
"maximum distance at which the ReflectionProbe itself is visible.*"
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/reflection_probes.rst:114
msgid ""
"**Extents:** The area that will be affected by the ReflectionProbe's "
"lighting and reflections."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/reflection_probes.rst:116
msgid ""
"**Origin Offset:** The origin to use for the internal camera used for "
"reflection probe rendering. This must always be constrained within the "
"**Extents**. If needed, adjust this to prevent the reflection from being "
"obstructed by a solid object located exactly at the center of the "
"ReflectionProbe."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/reflection_probes.rst:121
msgid ""
"**Box Projection:** Controls whether parallax correction should be used when "
"rendering the reflection probe. This adjusts the reflection's appearance "
"depending on the camera's position (relative to the reflection probe). This "
"has a small performance cost, but the quality increase is often worth it in "
"box-shaped rooms. Note that this effect doesn't work quite as well in rooms "
"with less regular shapes (such as ellipse-shaped rooms)."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/reflection_probes.rst:127
msgid ""
"**Interior:** If enabled, ambient lighting will not be sourced from the "
"environment sky, and the background sky won't be rendered onto the "
"reflection probe."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/reflection_probes.rst:130
msgid ""
"**Enable Shadows:** Controls whether real-time light shadows should be "
"rendered within the reflection probe. Enable this to improve reflection "
"quality at the cost of performance. This should be left disabled for "
"reflection probes with the **Always** mode, as it's very expensive to render "
"reflections with shadows every frame. Fully :ref:`baked light "
"<doc_using_lightmap_gi>` shadows are not affected by this setting and will "
"be rendered in the reflection probe regardless."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/reflection_probes.rst:137
msgid ""
"**Cull Mask:** Controls which objects are visible in the reflection. This "
"can be used to improve performance by excluding small objects from the "
"reflection. This can also be used to prevent an object from having self-"
"reflection artifacts in situations where **Origin Offset** can't be used."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/reflection_probes.rst:141
msgid ""
"**Mesh LOD Threshold:** The automatic level of detail threshold to use for "
"rendering meshes within the reflection. This only affects meshes that have "
"automatic LODs generated for them. Higher values can improve performance by "
"using less detailed geometry, especially for objects that are far away from "
"the reflection's origin. The visual difference of using less detailed "
"objects is usually not very noticeable during gameplay, especially in rough "
"reflections."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/reflection_probes.rst:149
msgid ""
"The Ambient category features several properties to adjust ambient lighting "
"rendered by the ReflectionProbe:"
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/reflection_probes.rst:152
msgid ""
"**Mode:** If set to **Disabled**, no ambient light is added by the probe. If "
"set to **Environment**, the ambient light color is automatically sampled "
"from the environment sky (if **Interior** is disabled) and the reflection's "
"average color. If set to **Constant Color**, the color specified in the "
"**Color** property is used instead. The **Constant Color** mode can be used "
"as an approximation of area lighting."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/reflection_probes.rst:158
msgid ""
"**Color:** The color to use when the ambient light mode is set to **Constant "
"Mode**."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/reflection_probes.rst:159
msgid ""
"**Color Energy:** The multiplier to use for the ambient light custom "
"**Color**. This only has an effect when the ambient light mode is **Custom "
"Color**."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/reflection_probes.rst:164
msgid "ReflectionProbe blending"
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/reflection_probes.rst:166
msgid ""
"To make transitions between reflection sources smoother, Godot supports "
"automatic probe blending:"
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/reflection_probes.rst:169
msgid ""
"Up to 4 ReflectionProbes can be blended together at a given location. A "
"ReflectionProbe will also fade out smoothly back to environment lighting "
"when it isn't touching any other ReflectionProbe node."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/reflection_probes.rst:172
msgid ""
"SDFGI and VoxelGI will blend in smoothly with ReflectionProbes if used. This "
"allows placing ReflectionProbes strategically to get more accurate (or fully "
"real-time) reflections where needed, while still having rough reflections "
"available in the VoxelGI or SDFGI's area of influence."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/reflection_probes.rst:177
msgid ""
"To make several ReflectionProbes blend with each other, you need to have "
"part of each ReflectionProbe overlap each other's area. The extents should "
"only overlap as little possible with other reflection probes to improve "
"rendering performance (typically a few units in 3D space)."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/reflection_probes.rst:185
msgid ""
"When using the Forward+ renderer, Godot uses a *clustering* approach for "
"reflection probe rendering. As many reflection probes as desired can be "
"added (as long as performance allows). However, there's still a default "
"limit of 512 *clustered elements* that can be present in the current camera "
"view. A clustered element is an omni light, a spot light, a :ref:`decal "
"<doc_using_decals>` or a :ref:`reflection probe <doc_reflection_probes>`. "
"This limit can be increased by adjusting the **Rendering > Limits > Cluster "
"Builder > Max Clustered Elements** advanced project setting."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/reflection_probes.rst:194
msgid ""
"When using the Forward Mobile backend, only 8 reflection probes can be "
"applied on each individual Mesh *resource*. If there are more reflection "
"probes affecting a single mesh, not all of them will be rendered on the mesh."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/faking_global_illumination.rst:4
msgid "Faking global illumination"
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/faking_global_illumination.rst:7
msgid "Why fake global illumination?"
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/faking_global_illumination.rst:9
msgid ""
"Godot provides several global illumination (GI) techniques, all with their "
"advantages and drawbacks. Nonetheless, it remains possible to avoid using "
"any GI technique and use a handmade approach instead. There are a few "
"reasons for using a \"handmade\" approach to global illumination instead of "
"VoxelGI, SDFGI or baked lightmaps:"
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/faking_global_illumination.rst:15
msgid ""
"You need to have good rendering performance, but can't afford going through "
"a potentially cumbersome lightmap baking process."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/faking_global_illumination.rst:17
msgid ""
"You need an approach to GI that is fully real-time *and* works in "
"procedurally generated levels."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/faking_global_illumination.rst:19
msgid ""
"You need an approach to GI that is fully real-time *and* does not suffer "
"from significant light leaks."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/faking_global_illumination.rst:22
msgid ""
"The approaches described below only cover indirect diffuse lighting, not "
"specular lighting. For specular lighting, consider using ReflectionProbes "
"which are usually cheap enough to be used in conjunction with this fake GI "
"approach."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/faking_global_illumination.rst:28
msgid ""
"Not sure if faking global illumination with lights is suited to your needs? "
"See :ref:`doc_introduction_to_global_illumination_comparison` for a "
"comparison of GI techniques available in Godot 4."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/faking_global_illumination.rst:33
msgid "Faking DirectionalLight3D global illumination"
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/faking_global_illumination.rst:35
msgid ""
"While the sky provides its own directional lighting, the scene's main "
"DirectionalLight3D node typically emits a large amount of light. When using "
"a GI technique, this light would be reflected on solid surfaces and would "
"bounce back on most outdoors shaded surfaces."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/faking_global_illumination.rst:39
msgid ""
"We can fake this by adding a second DirectionalLight3D node with the "
"following changes:"
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/faking_global_illumination.rst:41
msgid ""
"Rotate the light by 180 degrees. This allows it to represent lighting "
"bounced by the main DirectionalLight3D node."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/faking_global_illumination.rst:43
#: ../../docs/tutorials/3d/global_illumination/faking_global_illumination.rst:83
msgid ""
"Set **Shadows** to **Off**. This reduces the secondary light's performance "
"burden while also allowing shaded areas to receive *some* lighting (which is "
"what we want here)."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/faking_global_illumination.rst:45
msgid ""
"Set **Energy** to 10-40% of the original value. There is no \"perfect\" "
"value, so experiment with various energy values depending on the light and "
"your typical material colors."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/faking_global_illumination.rst:48
msgid ""
"Set **Specular** to ``0.0``. Indirect lighting shouldn't emit visible "
"specular lobes, so we need to disable specular lighting entirely for the "
"secondary light."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/faking_global_illumination.rst:53
msgid ""
"This approach works best in scenes that are mostly outdoors. When going "
"indoors, the secondary DirectionalLight3D's light will still be visible as "
"this light has shadows disabled."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/faking_global_illumination.rst:57
msgid ""
"This can be worked around by smoothly decreasing the secondary "
"DirectionalLight3D's energy when entering an indoor area (and doing the "
"opposite when leaving the indoor area). For instance, this can be achieved "
"using an Area3D node and AnimationPlayer."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/faking_global_illumination.rst:62
msgid "Faking positional light global illumination"
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/faking_global_illumination.rst:64
msgid ""
"It's possible to follow the same approach as DirectionalLight3D for "
"positional lights (OmniLight3D and SpotLight3D). However, this will require "
"more manual work as this operation needs to be repeated for every positional "
"light node in the scene to look good."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/faking_global_illumination.rst:69
msgid ""
"In an ideal scenario, additional OmniLight3Ds should be added at every "
"location where a significant amount of light hits a bright enough surface. "
"However, due to time constraints, this isn't always easily feasible "
"(especially when performing procedural level generation)."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/faking_global_illumination.rst:74
msgid ""
"If you're in a hurry, you can place a secondary OmniLight3D node at the same "
"position as the main OmniLight3D node. You can add this node as a child of "
"the main OmniLight3D node to make it easy to move and hide both nodes at the "
"same time."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/faking_global_illumination.rst:79
msgid "In the secondary OmniLight3D node, perform the following changes:"
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/faking_global_illumination.rst:81
msgid ""
"Increase the light's **Range** by 25-50%. This allows the secondary light to "
"lighten what was previously not lit by the original light."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/faking_global_illumination.rst:85
msgid ""
"Set **Energy** to 10-40% of the original value. There is no \"perfect\" "
"value, so experiment with various energy values depending on the light and "
"its surroundings."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/faking_global_illumination.rst:87
msgid ""
"Set **Specular** to 0. Indirect lighting shouldn't emit visible specular "
"lobes, so we need to disable specular lighting entirely for the secondary "
"light."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/faking_global_illumination.rst:90
msgid ""
"For SpotLight3D, the same trick can be used. In this case, the secondary "
"OmniLight3D should be placed in a way that reflects where *most* light will "
"be bounced. This is usually close to the SpotLight3D's primary impact "
"location."
msgstr ""

#: ../../docs/tutorials/3d/global_illumination/faking_global_illumination.rst:94
msgid ""
"In the example below, a SpotLight3D node is used to light up the room's "
"floor. However, since there is no indirect lighting, the rest of the room "
"remains entirely dark. In real life, the room's walls and ceiling would be "
"lit up by light bouncing around. Using an OmniLight3D node positioned "
"between the SpotLight3D's origin and the floor allows simulating this effect:"
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:4
msgid "Environment and post-processing"
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:6
msgid ""
"Godot 4 provides a redesigned Environment resource, as well as a new post-"
"processing system with many available effects right out of the box."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:11
msgid ""
"As of Godot 4, Environment *performance/quality* settings are defined in the "
"project settings instead of in the Environment resource. This makes global "
"adjustments easier, as you no longer have to tweak Environment resources "
"individually to suit various hardware configurations."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:16
msgid ""
"Note that most Environment performance/quality settings are only visible "
"after enabling the **Advanced** toggle in the Project Settings."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:22
msgid ""
"The :ref:`class_Environment` resource stores all the information required "
"for controlling the 2D and 3D rendering environment. This includes the sky, "
"ambient lighting, tone mapping, effects, and adjustments. By itself, it does "
"nothing, but you can enable it by using it in one of the following "
"locations, in order of priority:"
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:29
msgid "Camera3D node (high priority)"
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:31
msgid ""
"An Environment can be set to a Camera3D node. It will have priority over any "
"other setting."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:36
msgid ""
"This is mostly useful when you want to override an existing environment, but "
"in general it's a better idea to use the option below."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:40
msgid "WorldEnvironment node (medium priority, recommended)"
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:42
msgid ""
"The WorldEnvironment node can be added to any scene, but only one can exist "
"per active scene tree. Adding more than one will result in a warning."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:47
msgid ""
"Any Environment added has higher priority than the default Environment "
"(explained below). This means it can be overridden on a per-scene basis, "
"which makes it quite useful."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:52
msgid "Preview environment and sun (low priority)"
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:56
msgid ""
"Since Godot 4, the preview environment and sun system replace the "
"``default_env.tres`` file that was used in Godot 3 projects."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:59
msgid ""
"If no WorldEnvironment node or DirectionalLight3D node is present in the "
"current scene, the editor will display a preview environment and sun "
"instead. This can be disabled using the buttons at the top of the 3D editor:"
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:65
msgid ""
"Clicking on the 3 vertical dots on the right will display a dialog which "
"allows you to customize the appearance of the preview environment:"
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:70
msgid ""
"**The preview sun and sky is only visible in the editor, not in the running "
"project.** Using the buttons at the bottom of the dialog, you can add the "
"preview sun and sky into the scene as nodes."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:76
msgid ""
"If you hold :kbd:`Shift` while clicking **Add Sun to Scene** or **Add "
"Environment to Scene** in the preview environment editor, this will add both "
"a preview sun and environment to the current scene (as if you clicked both "
"buttons separately). Use this to speed up project setup and prototyping."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:82
msgid "Camera attributes"
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:86
msgid ""
"In Godot 4, exposure and depth of field information was split from the "
"Environment resource into a separate CameraAttributes resource. This allows "
"adjusting those properties independently of other Environment settings more "
"easily."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:91
msgid ""
"The :ref:`class_CameraAttributes` resource stores exposure and depth of "
"field information. It also allows enabling automatic exposure adjustments "
"depending on scene brightness."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:95
#, fuzzy
msgid "There are two kinds of CameraAttribute resources available:"
msgstr "Ne postoje ograničenja prilikom korištenja Godot-a"

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:97
msgid ""
"**CameraAttributesPractical:** Features are exposed using arbitrary units, "
"which are easier to reason about for most game use cases."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:99
msgid ""
"**CameraAttributesPhysical:** Features are exposed using real world units, "
"similar to a digital camera. For example, field of view is set using a focal "
"length in millimeters instead of a value in degrees. Recommended when "
"physical accuracy is important, such as for photorealistic rendering."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:104
msgid ""
"Both CameraAttribute resource types allow you to use the same features, but "
"they are configured differently. If you don't know which one to choose, use "
"**CameraAttributesPractical**."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:110
msgid ""
"Using a :ref:`class_CameraAttributesPhysical` on a Camera3D node will lock "
"out FOV and aspect adjustments in that Camera3D, as field of view is "
"adjusted in the CameraAttributesPhysical resource instead. If used in a "
"WorldEnvironment, the CameraAttributesPhysical will not override any "
"Camera3D in the scene."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:116
msgid ""
"A CameraAttributes resource can be added to a Camera3D or a WorldEnvironment "
"node. When the current camera has a CameraAttributes set, it will *override* "
"the one set in WorldEnvironment (if any)."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:120
msgid ""
"In most situations, setting the CameraAttributes resource on the Camera3D "
"node instead of the WorldEnvironment is recommended. Unlike "
"WorldEnvironment, assigning the CameraAttributes resource to the Camera3D "
"node prevents depth of field from displaying in the 3D editor viewport, "
"unless the camera is being previewed."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:127
msgid "Environment options"
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:129
msgid ""
"The following is a detailed description of all environment options and how "
"they are intended to be used."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:135
msgid ""
"The Background section contains settings on how to fill the background "
"(parts of the screen where objects were not drawn). The background not only "
"serves the purpose of displaying an image or color. By default, it also "
"affects how objects are affected by ambient and reflected light. This is "
"called image-based lighting (IBL)."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:141
msgid ""
"As a result, the background sky may greatly impact your scene's overall "
"appearance, even if the sky is never directly visible on screen. This should "
"be taken into account when tweaking lighting in your scene."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:147
#, fuzzy
msgid "There are several background modes available:"
msgstr "Ne postoje ograničenja prilikom korištenja Godot-a"

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:149
msgid ""
"**Clear Color** uses the default clear color defined in the project "
"settings. The background will be a constant color."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:151
msgid "**Custom Color** is like Clear Color, but with a custom color value."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:152
msgid ""
"**Sky** lets you define a background sky material (see below). By default, "
"objects in the scene will reflect this sky material and absorb ambient light "
"from it."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:155
msgid ""
"**Canvas** displays the 2D scene as a background to the 3D scene. This can "
"be used to make environment effects visible on 2D rendering, such as :ref:"
"`glow in 2D <doc_environment_and_post_processing_using_glow_in_2d>`."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:158
msgid ""
"**Keep** does not draw any sky, keeping what was present on previous frames "
"instead. This improves performance in purely indoor scenes, but creates a "
"\"hall of mirrors\" visual glitch if the sky is visible at any time."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:163
msgid "Sky materials"
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:165
msgid ""
"When using the **Sky** background mode (or the ambient/reflected light mode "
"is set to **Sky**), a Sky subresource becomes available to edit in the "
"Environment resource. Editing this subresource allows you to create a "
"SkyMaterial resource within the Sky."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:170
msgid "There are 3 built-in sky materials to choose from:"
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:172
msgid ""
"**PanoramaSkyMaterial:** Use a 360 degree panorama sky image (2:1 aspect "
"ratio recommended). To benefit from high dynamic range, the panorama image "
"must be in an HDR-compatible format such as ``.hdr`` or ``.exr`` rather than "
"a standard dynamic range format like ``.png`` or ``.jpg``."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:176
msgid ""
"**ProceduralSkyMaterial:** Use a procedurally generated sky with adjustable "
"ground, sun, sky and horizon colors. This is the type of sky used in the "
"editor preview. The sun's position is automatically derived from the first 4 "
"DirectionalLight3D nodes present in the scene. There can be up to 4 suns at "
"a given time."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:181
msgid ""
"**PhysicalSkyMaterial:** Use a physically-based procedural sky with "
"adjustable scattering parameters. The sun's position is automatically "
"derived from the first DirectionalLight3D node present in the scene. "
"PhysicalSkyMaterial is slightly more expensive to render compared to "
"ProceduralSkyMaterial. There can be up to 1 sun at a given time."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:187
msgid ""
"Panorama sky images are sometimes called HDRIs (High Dynamic Range Images). "
"You can find freely licensed HDRIs on `Poly Haven <https://polyhaven.com/"
"hdris>`__."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:192
msgid ""
"HDR PanoramaSkyMaterial textures with very bright spots (such as real life "
"photos with the sun visible) may result in visible sparkles on ambient and "
"specular reflections. This is caused by the texture's peak exposure being "
"too high."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:197
msgid ""
"To resolve this, select the panorama texture in the FileSystem dock, go to "
"the Import dock, enable **HDR Clamp Exposure** then click **Reimport**."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:200
msgid ""
"If you need a custom sky material (e.g. for procedural clouds), you can "
"create a custom :ref:`sky shader <doc_sky_shader>`."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:204
msgid "Ambient light"
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:206
msgid ""
"Ambient light (as defined here) is a type of light that affects every piece "
"of geometry with the same intensity. It is global and independent of lights "
"that might be added to the scene. Ambient light is one of the two components "
"of image-based lighting. Unlike reflected light, ambient light does not vary "
"depending on the camera's position and viewing angle."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:212
#, fuzzy
msgid "There are several types of ambient light to choose from:"
msgstr "Ne postoje ograničenja prilikom korištenja Godot-a"

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:214
msgid ""
"**Background:** Source ambient light from the background, such as the sky, "
"custom color or clear color (default). Ambient light intensity will vary "
"depending on the sky image's contents, which can result in more visually "
"appealing ambient lighting. A sky must be set as background for this mode to "
"be visible."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:219
msgid ""
"**Disabled:** Do not use any ambient light. Useful for purely indoor scenes."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:220
msgid ""
"**Color:** Use a constant color for ambient light, ignoring the background "
"sky. Ambient light intensity will be the same on all sides, which may result "
"in the scene's lighting looking more flat. Useful for indoor scenes where "
"pitch black shadows may be too dark, or to maximize performance on low-end "
"devices."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:225
msgid ""
"**Sky:** Source ambient light from a specified sky, even if the background "
"is set to a mode other than **Sky**. If the background mode is already "
"**Sky**, this mode behaves identically to **Background**."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:231
msgid ""
"When the ambient light mode is set to Sky or Background (and background is "
"set to Sky), it's possible to blend between the ambient color and sky using "
"the **Sky Contribution** property. This value is set to ``1.0`` by default, "
"which means that only the ambient sky is used. The ambient color is ignored "
"unless **Sky Contribution** is decreased below ``1.0``."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:237
msgid "Here is a comparison of how different ambient light affects a scene:"
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:241
msgid ""
"Finally, there is an **Energy** setting which is a multiplier. It's useful "
"when working with HDR."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:244
msgid ""
"In general, you should only rely on ambient light alone for simple scenes or "
"large exteriors. You may also do so to boost performance. Ambient light is "
"fast to render, but it doesn't provide the best lighting quality. It's "
"better to generate ambient light from :ref:`ReflectionProbe "
"<doc_reflection_probes>`, :ref:`VoxelGI <doc_using_voxel_gi>` or :ref:`SDFGI "
"<doc_using_sdfgi>`, as these will simulate how indirect light propagates "
"more accurately. Below is a comparison, in terms of quality, between using a "
"flat ambient color and a VoxelGI:"
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:254
msgid ""
"Using one of the methods described above will replace constant ambient "
"lighting with ambient lighting from the probes."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:258
msgid "Reflected light"
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:260
msgid ""
"Reflected light (also called specular light) is the other of the two "
"components of image-based lighting."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:263
msgid "Reflected light can be set to one of 3 modes:"
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:265
msgid ""
"**Background:** Reflect from the background, such as the sky, custom color "
"or clear color (default)."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:267
msgid ""
"**Disabled:** Do not reflect any light from the environment. Useful for "
"purely indoor scenes, or to maximize performance on low-end devices."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:269
msgid ""
"**Sky:** Reflect from the background sky, even if the background is set to a "
"mode other than **Sky**. If the background mode is already **Sky**, this "
"mode behaves identically to **Background**."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:274
msgid "Fog"
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:278
msgid ""
"This section refers to non-volumetric fog only. It is possible to use both "
"non-volumetric fog and :ref:`doc_volumetric_fog` at the same time."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:282
msgid ""
"Fog, as in real life, makes distant objects fade away into a uniform color. "
"There are two kinds of fog in Godot:"
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:285
msgid ""
"**Depth Fog:** This one is applied based on the distance from the camera."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:286
msgid ""
"**Height Fog:** This one is applied to any objects below (or above) a "
"certain height, regardless of the distance from the camera."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:291
msgid ""
"Both of these fog types can have their curve tweaked, making their "
"transition more or less sharp."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:293
msgid "Two properties can be tweaked to make the fog effect more interesting:"
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:295
msgid ""
"The first is **Sun Amount**, which makes use of the Sun Color property of "
"the fog. When looking towards a directional light (usually a sun), the color "
"of the fog will be changed, simulating the sunlight passing through the fog."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:299
msgid ""
"The second is **Transmit Enabled** which simulates more realistic light "
"transmittance. In practice, it makes light stand out more across the fog."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:306
msgid ""
"Fog can cause banding to appear on the viewport, especially at higher "
"density levels. See :ref:`doc_3d_rendering_limitations_color_banding` for "
"guidance on reducing banding."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:311
msgid "Volumetric Fog"
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:313
msgid ""
"Volumetric fog provides a realistic fog effect to the scene, with fog color "
"being affected by the lights that traverse the fog."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:318
msgid ""
"See :ref:`doc_volumetric_fog` for documentation on setting up volumetric fog."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:321
msgid "Tonemap"
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:323
msgid ""
"Tonemap selects the tonemapping curve that will be applied to the scene, "
"from a list of standard curves used in the film and game industries. "
"Tonemapping operators other than Linear are used to make light and dark "
"areas more homogeneous, while also avoiding clipping of bright highlights."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:328
msgid "The tone mapping options are:"
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:330
msgid "**Mode:** The tone mapping mode to use."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:332
msgid ""
"**Linear:** The default tonemapping mode. This is the fastest and simplest "
"tonemapping operator, but it causes bright lighting to look blown out, with "
"noticeable clipping in the output colors."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:335
msgid ""
"**Reinhardt:** Performs a variation on rendered pixels' colors by this "
"formula: ``color = color / (1 + color)``. This avoids clipping bright "
"highlights, but the resulting image can look a bit dull."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:338
msgid ""
"**Filmic:** This avoids clipping bright highlights, with a resulting image "
"that usually looks more vivid than Reinhardt."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:340
msgid ""
"**ACES:** Academy Color Encoding System tonemapper. ACES is slightly more "
"expensive than other options, but it handles bright lighting in a more "
"realistic fashion by desaturating it as it becomes brighter. ACES typically "
"has a more contrasted output compared to Reinhardt and Filmic. ACES is the "
"recommended option when aiming for photorealistic visuals. This tonemapping "
"mode was called \"ACES Fitted\" in Godot 3.x."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:347
msgid ""
"**Exposure:** Tone mapping exposure which simulates amount of light received "
"over time (default: ``1.0``). Higher values result in an overall brighter "
"appearance. If the scene appears too dark as a result of a tonemapping "
"operator or whitepoint change, try increasing this value slightly."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:352
msgid ""
"**White:** Tone mapping whitepoint, which simulates where in the scale white "
"is located (default: ``1.0``). For photorealistic lighting, recommended "
"values are between ``6.0`` and ``8.0``. Higher values result in less blown "
"out highlights, but make the scene appear slightly darker as a whole."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:358
msgid "Mid- and post-processing effects"
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:360
msgid ""
"The Environment resource supports many popular mid- and post-processing "
"effects."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:364
msgid ""
"Screen-space effects such as :abbr:`SSR (Screen-Space Reflections)`, :abbr:"
"`SSAO (Screen-Space Ambient Occlusion)`, :abbr:`SSIL (Screen-Space Indirect "
"Lighting)` and glow do not operate on geometry that is located outside the "
"camera view or is occluded by other opaque geometry. Consider this when "
"tweaking their settings to avoid distracting changes during gameplay."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:372
msgid "Screen-Space Reflections (SSR)"
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:374
#: ../../docs/tutorials/3d/environment_and_post_processing.rst:416
#: ../../docs/tutorials/3d/environment_and_post_processing.rst:490
#: ../../docs/tutorials/3d/environment_and_post_processing.rst:536
#: ../../docs/tutorials/3d/environment_and_post_processing.rst:837
msgid ""
"*This feature is only available when using the Forward+ backend, not Mobile "
"or Compatibility.*"
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:377
msgid ""
"While Godot supports several sources of reflection data such as :ref:"
"`doc_reflection_probes`, they may not provide enough detail for all "
"situations. Scenarios where screen-space reflections make the most sense are "
"when objects are in contact with each other (object over floor, over a "
"table, floating on water, etc)."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:385
msgid ""
"On top of providing more detail, screen-space reflections also work in real-"
"time (while other types of reflections are usually precomputed). This can be "
"used to make characters, cars, etc. reflect on surrounding surfaces when "
"moving around."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:389
msgid ""
"Screen-space reflections can be used at the same time as other reflection "
"sources to benefit from detailed reflections when possible, while having a "
"fallback when screen-space reflections cannot be used (for example, to "
"reflect off-screen objects)."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:394
msgid ""
"A few user-controlled parameters are available to better tweak the technique:"
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:396
msgid ""
"**Max Steps:** Determines the length of the reflection. The bigger this "
"number, the more costly it is to compute."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:398
msgid ""
"**Fade In:** Allows adjusting the fade-in curve, which is useful to make the "
"contact area softer."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:400
msgid ""
"**Fade Out:** Allows adjusting the fade-out curve, so the step limit fades "
"out softly."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:402
msgid ""
"**Depth Tolerance:** Can be used to allow screen-space rays to pass behind "
"objects. The rays will treat each object as if it has this depth in "
"determining if it can pass behind the object. Higher values will make screen-"
"space reflections exhibit fewer \"breakups\", at the cost of some objects "
"creating physically incorrect reflections."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:408
msgid ""
"Keep in mind that screen-space-reflections only work for reflecting opaque "
"geometry. Transparent materials won't be reflected, as they don't write to "
"the depth buffer. This also applies to shaders that use "
"``hint_screen_texture`` or ``hint_depth_texture`` uniforms."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:414
msgid "Screen-Space Ambient Occlusion (SSAO)"
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:419
msgid ""
"As mentioned in the **Ambient** section, areas where light from light nodes "
"does not reach (either because it's outside the radius or shadowed) are lit "
"with ambient light. Godot can simulate this using VoxelGI, ReflectionProbe, "
"the Sky, or a constant ambient color. The problem, however, is that all the "
"methods proposed previously act more on a larger scale (large regions) than "
"at the smaller geometry level."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:426
msgid ""
"Constant ambient color and Sky are the same everywhere, while GI and "
"Reflection probes have more local detail, but not enough to simulate "
"situations where light is not able to fill inside hollow or concave features."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:430
msgid ""
"This can be simulated with Screen Space Ambient Occlusion. As you can see in "
"the image below, its purpose is to make sure concave areas are darker, "
"simulating a narrower path for the light to enter:"
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:436
msgid ""
"It is a common mistake to enable this effect, turn on a light, and not be "
"able to appreciate it. This is because :abbr:`SSAO (Screen-Space Ambient "
"Occlusion)` only acts on *ambient* light. It does not affect direct light."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:440
msgid ""
"This is why, in the image above, the effect is less noticeable under the "
"direct light (on the left). If you want to force :abbr:`SSAO (Screen-Space "
"Ambient Occlusion)` to work with direct light too, use the **Light Affect** "
"parameter. Even though this is not physically correct, some artists like how "
"it looks."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:446
msgid ""
":abbr:`SSAO (Screen-Space Ambient Occlusion)` looks best when combined with "
"a real source of indirect light, like VoxelGI:"
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:451
msgid ""
"Tweaking :abbr:`SSAO (Screen-Space Ambient Occlusion)` is possible with "
"several parameters:"
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:456
msgid ""
"**Radius:** The distance at which objects can occlude each other when "
"calculating screen-space ambient occlusion. Higher values will result in "
"occlusion over a greater distance at the cost of performance and quality."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:459
msgid ""
"**Intensity:** The primary screen-space ambient occlusion intensity. Acts as "
"a multiplier for the screen-space ambient occlusion effect. A higher value "
"results in darker occlusion. Since :abbr:`SSAO (Screen-Space Ambient "
"Occlusion)` is a screen-space effect, it's recommended to remain "
"conservative with this value. :abbr:`SSAO (Screen-Space Ambient Occlusion)` "
"that is too strong can be distracting during gameplay."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:466
msgid ""
"**Power:** The distribution of occlusion. A higher value results in darker "
"occlusion, similar to **Intensity**, but with a sharper falloff."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:468
msgid ""
"**Detail:** Sets the strength of the additional level of detail for the "
"screen-space ambient occlusion effect. A high value makes the detail pass "
"more prominent, but it may contribute to aliasing in your final image."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:471
msgid ""
"**Horizon:** The threshold for considering whether a given point on a "
"surface is occluded or not represented as an angle from the horizon mapped "
"into the 0.0-1.0 range. A value of 1.0 results in no occlusion."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:474
msgid ""
"**Sharpness:** The amount that the screen-space ambient occlusion effect is "
"allowed to blur over the edges of objects. Setting too high will result in "
"aliasing around the edges of objects. Setting too low will make object edges "
"appear blurry."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:478
msgid ""
"**Light Affect:** The screen-space ambient occlusion intensity in direct "
"light. In real life, ambient occlusion only applies to indirect light, which "
"means its effects can't be seen in direct light. Values higher than 0 will "
"make the :abbr:`SSAO (Screen-Space Ambient Occlusion)` effect visible in "
"direct light. Values above ``0.0`` are not physically accurate, but some "
"artists prefer this effect."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:488
msgid "Screen-Space Indirect Lighting (SSIL)"
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:493
msgid ""
":abbr:`SSIL (Screen-Space Indirect Lighting)` provides indirect lighting for "
"small details or dynamic geometry that other global illumination techniques "
"cannot cover. This applies to bounced diffuse lighting, but also emissive "
"materials. When :abbr:`SSIL (Screen-Space Indirect Lighting)` is enabled on "
"its own, the effect may not be that noticeable, which is intended."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:499
msgid ""
"Instead, :abbr:`SSIL (Screen-Space Indirect Lighting)` is meant to be used "
"as a *complement* to other global illumination techniques such as VoxelGI, "
"SDFGI and LightmapGI. :abbr:`SSIL (Screen-Space Indirect Lighting)` also "
"provides a subtle ambient occlusion effect, similar to SSAO but with less "
"detail."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:504
msgid ""
"This feature only provides indirect lighting. It is not a full global "
"illumination solution. This makes it different from screen-space global "
"illumination (SSGI) offered by other 3D engines. :abbr:`SSIL (Screen-Space "
"Indirect Lighting)` can be combined with :abbr:`SSR (Screen-Space "
"Reflections)` and/or :abbr:`SSAO (Screen-Space Ambient Occlusion)` for "
"greater visual quality (at the cost of performance)."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:511
msgid ""
"Tweaking :abbr:`SSIL (Screen-Space Indirect Lighting)` is possible with "
"several parameters:"
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:513
msgid ""
"**Radius:** The distance that bounced lighting can travel when using the "
"screen space indirect lighting effect. A larger value will result in light "
"bouncing further in a scene, but may result in under-sampling artifacts "
"which look like long spikes surrounding light sources."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:517
msgid ""
"**Intensity:** The brightness multiplier for the screen-space indirect "
"lighting effect. A higher value will result in brighter light."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:519
msgid ""
"**Sharpness:** The amount that the screen-space indirect lighting effect is "
"allowed to blur over the edges of objects. Setting too high will result in "
"aliasing around the edges of objects. Setting too low will make object edges "
"appear blurry."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:523
msgid ""
"**Normal Rejection:** Amount of normal rejection used when calculating "
"screen-space indirect lighting. Normal rejection uses the normal of a given "
"sample point to reject samples that are facing away from the current pixel. "
"Normal rejection is necessary to avoid light leaking when only one side of "
"an object is illuminated. However, normal rejection can be disabled if light "
"leaking is desirable, such as when the scene mostly contains emissive "
"objects that emit light from faces that cannot be seen from the camera."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:534
msgid "Signed Distance Field Global Illumination (SDFGI)"
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:539
msgid ""
"Signed distance field global illumination (SDFGI) is a form of real-time "
"global illumination. It is not a screen-space effect, which means it can "
"provide global illumination for off-screen elements (unlike :abbr:`SSIL "
"(Screen-Space Indirect Lighting)`)."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:545
msgid ""
"See :ref:`doc_using_sdfgi` for instructions on setting up this global "
"illumination technique."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:553
msgid "Glow"
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:555
msgid ""
"*This feature is only available when using the Forward+ and Mobile backends, "
"not Compatibility.*"
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:558
msgid ""
"In photography and film, when light amount exceeds the maximum *luminance* "
"(brightness) supported by the media, it generally bleeds outwards to darker "
"regions of the image. This is simulated in Godot with the **Glow** effect."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:564
msgid ""
"By default, even if the effect is enabled, it will be weak or invisible. One "
"of two conditions need to happen for it to actually show:"
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:567
msgid ""
"The light in a pixel surpasses the **HDR Threshold** (where 0 is all light "
"surpasses it, and 1.0 is light over the tonemapper **White** value). "
"Normally, this value is expected to be at 1.0, but it can be lowered to "
"allow more light to bleed. There is also an extra parameter, **HDR Scale**, "
"that allows scaling (making brighter or darker) the light surpassing the "
"threshold."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:576
msgid ""
"The **Bloom** property has a value greater than ``0.0``. As it increases, it "
"sends the whole screen to the glow processor at higher amounts."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:581
msgid "Both will cause the light to start bleeding out of the brighter areas."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:583
msgid "Once glow is visible, it can be controlled with a few extra parameters:"
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:585
msgid ""
"**Intensity** is an overall scale for the effect, it can be made stronger or "
"weaker (``0.0`` removes it)."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:587
msgid ""
"**Strength** is how strong the gaussian filter kernel is processed. Greater "
"values make the filter saturate and expand outwards. In general, changing "
"this is not needed, as the size can be adjusted more efficiently with the "
"**Levels**."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:591
msgid "The **Blend Mode** of the effect can also be changed:"
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:593
msgid ""
"**Additive** is the strongest one, as it only adds the glow effect over the "
"image with no blending involved. In general, it's too strong to be used, but "
"can look good with low-intensity **Bloom** (produces a dream-like effect)."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:596
msgid ""
"**Screen** ensures glow never brightens more than itself and it works great "
"as an all around."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:598
msgid ""
"**Softlight** is the default and weakest one, producing only a subtle color "
"disturbance around the objects. This mode works best on dark scenes."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:600
msgid ""
"**Replace** can be used to :ref:`blur the whole screen "
"<doc_environment_and_post_processing_using_glow_to_blur_the_screen>` or "
"debug the effect. It only shows the glow effect without the image below."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:603
msgid ""
"**Mix** mixes the glow effect with the main image. This can be used for "
"greater artistic control. The mix factor is controlled by the **Mix** "
"property which appears above the blend mode (only when the blend mode is set "
"to Mix). High mix factor values will appear to darken the image unless "
"**Bloom** is increased."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:609
msgid ""
"To change the glow effect size and shape, Godot provides **Levels**. Smaller "
"levels are strong glows that appear around objects, while large levels are "
"hazy glows covering the whole screen:"
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:615
msgid ""
"The real strength of this system, though, is to combine levels to create "
"more interesting glow patterns:"
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:620
msgid ""
"Finally, the glow effect can be controlled using a *glow map*, which is a "
"texture that determines how bright glow should be on each part of the "
"screen. This texture can optionally be colored to tint the glow effect to "
"the glow map's color. The texture is stretched to fit the viewport, so using "
"an aspect ratio that matches your viewport's most common aspect ratio (such "
"as 16:9) is recommended to avoid visible distortion."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:627
msgid "There are 2 main use cases for a glow map texture:"
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:629
msgid "Create a \"lens dirt\" effect using a dirt pattern texture."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:630
msgid ""
"Make glow less strong on specific parts of the screen by using a gradient "
"texture."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:637
msgid "Using glow in 2D"
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:639
#, fuzzy
msgid "There are 2 ways to use glow in 2D:"
msgstr "Ne postoje ograničenja prilikom korištenja Godot-a"

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:641
msgid ""
"Since Godot 4.2, you can enable HDR for 2D rendering when using the Forward+ "
"and Mobile rendering methods. This has a performance cost, but it allows for "
"a greater dynamic range. This also allows you to control which objects glow "
"using their individual **Modulate** or **Self Modulate** properties (use the "
"RAW mode in the color picker). Enabling HDR can also reduce banding in the "
"2D rendering output."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:648
msgid ""
"To enable HDR in 2D, open the Project Settings, enable **Rendering > "
"Viewport > HDR 2D** then restart the editor."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:651
msgid ""
"If you want to maximize performance, you can leave HDR disabled for 2D "
"rendering. However, you will have less control on which objects glow."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:654
msgid ""
"Enable glow, set the environment background mode to **Canvas** then decrease "
"**Glow HDR Threshold** so that pixels that are not overbright will still "
"glow. To prevent UI elements from glowing, make them children of a :ref:"
"`class_CanvasLayer` node. You can control which layers are affected by glow "
"using the **Background > Canvas Max Layer** property of the Environment "
"resource."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:665
msgid "Example of using glow in a 2D scene"
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:665
msgid ""
"Example of using glow in a 2D scene. HDR 2D is enabled, while coins and the "
"bullet have their **Modulate** property increased to overbright values using "
"the RAW mode in the color picker."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:671
msgid ""
"The 2D renderer renders in linear color space if the **Rendering > Viewport "
"> HDR 2D** project setting is enabled, so ``source_color`` must also be used "
"for uniform samplers that are used as color input in ``canvas_item`` "
"shaders. If this is not done, the texture will appear washed out."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:677
msgid ""
"If 2D HDR is disabled, ``source_color`` will keep working correctly in "
"``canvas_item`` shaders, so it's recommend to use it when relevant either "
"way."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:684
msgid "Using glow to blur the screen"
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:686
msgid ""
"Glow can be used to blur the whole viewport, which is useful for background "
"blur when a menu is open. Only 3D rendering will be affected unless the "
"environment's background mode is set to **Canvas**. To prevent UI elements "
"from being blurred when using the Canvas background mode, make them children "
"of a :ref:`class_CanvasLayer` node. You can control which layers are "
"affected by this blurring effect using the **Background > Canvas Max Layer** "
"property of the Environment resource."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:693
msgid "To use glow as a blurring solution:"
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:695
msgid ""
"Enable **Normalized** and adjust levels according to preference. Increasing "
"higher level indices will result in a more blurred image. It's recommended "
"to leave a single glow level at ``1.0`` and leave all other glow levels at "
"``0.0``, but this is not required. Note that the final appearance will vary "
"depending on viewport resolution."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:700
msgid "Set **Intensity** to ``1.0`` and **Bloom** to ``1.0``."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:701
msgid "Set the blend mode to **Replace** and **HDR Luminance Cap** to ``1.0``."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:707
msgid "Example of using glow to blur the 2D rendering in the menu's background"
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:710
msgid "Adjustments"
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:712
msgid ""
"At the end of processing, Godot offers the possibility to do some standard "
"image adjustments."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:717
msgid "**Basic BCS adjustments**"
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:719
msgid ""
"The first adjustment is being able to change the typical **Brightness**, "
"**Contrast**, and **Saturation** properties:"
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:724
msgid "**Color correction using a 1D gradient**"
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:726
msgid ""
"The second adjustment is by supplying a color correction gradient. This can "
"be done by assigning a GradientTexture1D resource to the **Color "
"Correction** property, or by loading a texture containing a horizontal "
"gradient. The leftmost part of the gradient represents black in the source "
"image, whereas the rightmost part of the gradient represents white in the "
"source image."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:732
msgid ""
"A linear black-to-white gradient like the following one will produce no "
"effect:"
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:736
msgid ""
"But creating custom ones will allow to map each channel to a different color:"
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:740
msgid "**Color correction using a 3D LUT**"
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:742
msgid ""
"A 3D look-up-texture (LUT) can also be used for color correction. This is a "
"special texture used to modify each color channel separately from one "
"another (red, green, blue). This image can be of any resolution, but since "
"color correction is low-frequency data, sticking to low resolutions is "
"recommended for performance reasons. A LUT texture's resolution is typically "
"17×17×17, 33×33×33, 51×51×51 or 65×65×65 (the odd size allows for better "
"interpolation)."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:749
msgid ""
"For this to work, the look-up texture's import mode must be set to Texture3D "
"in the Import dock (instead of being imported as a regular Texture2D):"
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:754
msgid ""
"Make sure to configure the number of horizontal and vertical slices to "
"import as well. If you don't do this, the LUT texture will not affect the "
"viewport correctly when used. You can preview how the 3D texture was "
"imported by double-clicking it, in the FileSystem dock, then going to the "
"inspector to flip through the texture's layers."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:760
msgid ""
"You can use this neutral 33×33×33 LUT template as a base (right-click and "
"choose **Save as…**):"
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:765
msgid ""
"With the above LUT template, after changing its import mode to "
"**Texture3D**, set its number of **Horizontal** slices to ``33`` in the "
"Import dock then click **Reimport**. If you load this LUT into the **Color "
"Correction** property, you won't see any visible difference for now since "
"this texture is designed to be a neutral starting point."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:771
msgid ""
"This LUT template can be modified in an image editor to provide a different "
"mood to the image. A common workflow is to place the LUT image next to a "
"screenshot of the project's 3D viewport, then use an image editor to modify "
"both the LUT image and the screenshot at the same time. The LUT can then be "
"saved and applied to the game engine to perform the same color correction in "
"real-time."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:777
msgid ""
"For example, modifying the LUT template in an image editor to give it a "
"\"sepia\" look results in the image on the right:"
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:784
msgid ""
"Adjustments and color correction are applied *after* tonemapping. This means "
"the tonemapping properties defined above still have an effect when "
"adjustments are enabled."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:789
msgid "Camera attribute options"
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:792
msgid "Depth of Field / Far Blur"
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:794
msgid ""
"This effect simulates focal distance on cameras. It blurs objects behind a "
"given range. It has an initial **Distance** with a **Transition** region (in "
"world units):"
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:800
msgid ""
"The **Amount** parameter controls the amount of blur. For larger blurs, "
"tweaking the depth of field quality in the advanced project settings may be "
"needed to avoid artifacts."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:805
msgid "Depth of Field / Near Blur"
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:807
msgid ""
"This effect simulates focal distance on cameras. It blurs objects close to "
"the camera (acts in the opposite direction as far blur). It has an initial "
"**Distance** with a **Transition** region (in world units):"
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:813
msgid ""
"The **Amount** parameter controls the amount of blur. For larger blurs, "
"tweaking the **Quality** may be needed in order to avoid artifacts."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:816
msgid ""
"It is common to use both blurs together to focus the viewer's attention on a "
"given object, or create a so-called `\"tilt shift\" effect <https://en."
"wikipedia.org/wiki/Miniature_faking>`__."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:824
msgid ""
"When using CameraAttributesPhysical instead of CameraAttributesPractical, "
"depth of field is automatically computed from the camera attributes' focus "
"distance, focal length, and aperture."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:829
msgid "Exposure"
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:831
msgid ""
"This multiplies the overall scene brightness visible from the camera. Higher "
"values result in a visually brighter scene."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:835
msgid "Auto Exposure"
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:840
msgid ""
"Even though, in most cases, lighting and texturing are heavily artist "
"controlled, Godot supports a basic high dynamic range implementation with "
"the auto exposure mechanism. This is generally used to add realism when "
"combining interior areas with low light and bright outdoor areas. Auto "
"exposure simulates the camera (or eye) in an effort to adapt between light "
"and dark locations and their different amounts of light."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:849
msgid ""
"Auto exposure needs to evaluate the scene's brightness every frame, which "
"has a moderate performance cost. Therefore, it's recommended to leave Auto "
"Exposure disabled if it doesn't make much of a difference in your scene."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:855
msgid ""
"The simplest way to use auto exposure is to make sure outdoor lights (or "
"other strong lights) have energy beyond 1.0. This is done by tweaking their "
"**Energy** multiplier (on the Light itself). To make it consistent, the "
"**Sky** usually needs to use the energy multiplier too, to match with the "
"directional light. Normally, values between 3.0 and 6.0 are enough to "
"simulate indoor-outdoor conditions."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:861
msgid ""
"By combining Auto Exposure with :ref:"
"`doc_environment_and_post_processing_glow` post-processing, pixels that go "
"over the tonemap **White** will bleed to the glow buffer, creating the "
"typical bloom effect in photography."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:867
msgid ""
"The user-controllable values in the Auto Exposure section come with sensible "
"defaults, but you can still tweak them:"
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:872
msgid ""
"**Scale:** Value to scale the lighting. Higher values produce brighter "
"images, and lower values produce darker ones."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:874
msgid ""
"**Min Sensitivity / Min Exposure Value:** Minimum luminance that auto "
"exposure will aim to adjust for (in ISO when using "
"CameraAttributesPractical, or in EV100 when using CameraAttributesPhysical). "
"Luminance is the average of the light in all the pixels of the screen."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:878
msgid ""
"**Max Sensitivity / Max Exposure Value:** Maximum luminance that auto "
"exposure will aim to adjust for (in ISO when using "
"CameraAttributesPractical, or in EV100 when using CameraAttributesPhysical)."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:881
msgid ""
"**Speed:** Speed at which luminance corrects itself. The higher the value, "
"the faster luminance correction happens. High values may be more suited to "
"fast-paced games, but can be distracting in some scenarios."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:885
msgid ""
"When using CameraAttributesPractical, exposure is set using *sensitivity* "
"defined in ISO instead of an exposure value in EV100. Typical ISO values are "
"between 50 and 3200, with higher values resulting in higher final exposure. "
"In real life, daytime photography generally uses ISO values between 100 and "
"800."
msgstr ""

#: ../../docs/tutorials/3d/environment_and_post_processing.rst:892
msgid ""
"See :ref:`doc_physical_light_and_camera_units` if you wish to use real world "
"units to configure your camera's exposure, field of view and depth of field."
msgstr ""

#: ../../docs/tutorials/3d/volumetric_fog.rst:4
msgid "Volumetric fog and fog volumes"
msgstr ""

#: ../../docs/tutorials/3d/volumetric_fog.rst:8
msgid ""
"Volumetric fog is only supported in the Clustered Forward rendering backend, "
"not Forward Mobile or Compatibility."
msgstr ""

#: ../../docs/tutorials/3d/volumetric_fog.rst:11
msgid ""
"As described in :ref:`doc_environment_and_post_processing`, Godot supports "
"various visual effects including two types of fog: traditional (non-"
"volumetric) fog and volumetric fog. Traditional fog affects the entire scene "
"at once and cannot be customized with :ref:`doc_fog_shader`."
msgstr ""

#: ../../docs/tutorials/3d/volumetric_fog.rst:16
msgid ""
"Volumetric fog can be used at the same time as non-volumetric fog if desired."
msgstr ""

#: ../../docs/tutorials/3d/volumetric_fog.rst:20
msgid "How to set up volumetric fog in Godot."
msgstr ""

#: ../../docs/tutorials/3d/volumetric_fog.rst:21
msgid ""
"What fog volumes are and how they differ from \"global\" volumetric fog."
msgstr ""

#: ../../docs/tutorials/3d/volumetric_fog.rst:25
#, fuzzy
msgid ""
"You can see how volumetric fog works in action using the `Volumetric Fog "
"demo project <https://github.com/godotengine/godot-demo-projects/tree/"
"master/3d/volumetric_fog>`__."
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati različite Godo demo projekte "
"`Godot demo projects <https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/tutorials/3d/volumetric_fog.rst:28
msgid ""
"Here is a comparison between traditional fog (which does not interact with "
"lighting) and volumetric fog, which is able to interact with lighting:"
msgstr ""

#: ../../docs/tutorials/3d/volumetric_fog.rst:34
msgid "Volumetric fog properties"
msgstr ""

#: ../../docs/tutorials/3d/volumetric_fog.rst:36
msgid ""
"After enabling volumetric fog in the WorldEnvironment node's Environment "
"resource, you can edit the following properties:"
msgstr ""

#: ../../docs/tutorials/3d/volumetric_fog.rst:39
msgid ""
"**Density:** The base *exponential* density of the volumetric fog. Set this "
"to the lowest density you want to have globally. FogVolumes can be used to "
"add to or subtract from this density in specific areas. A value of ``0.0`` "
"disables global volumetric fog while allowing FogVolumes to display "
"volumetric fog in specific areas. Fog rendering is exponential as in real "
"life."
msgstr ""

#: ../../docs/tutorials/3d/volumetric_fog.rst:44
msgid ""
"**Albedo:** The Color of the volumetric fog when interacting with lights. "
"Mist and fog have an albedo close to white (``Color(1, 1, 1, 1)``) while "
"smoke has a darker albedo."
msgstr ""

#: ../../docs/tutorials/3d/volumetric_fog.rst:47
msgid ""
"**Emission:** The emitted light from the volumetric fog. Even with emission, "
"volumetric fog will not cast light onto other surfaces. Emission is useful "
"to establish an ambient color. As the volumetric fog effect uses single-"
"scattering only, fog tends to need a little bit of emission to soften the "
"harsh shadows."
msgstr ""

#: ../../docs/tutorials/3d/volumetric_fog.rst:52
msgid ""
"**Emission Energy:** The brightness of the emitted light from the volumetric "
"fog."
msgstr ""

#: ../../docs/tutorials/3d/volumetric_fog.rst:54
msgid ""
"**GI Inject:** Scales the strength of Global Illumination used in the "
"volumetric fog's albedo color. A value of ``0.0`` means that Global "
"Illumination will not impact the volumetric fog. This has a small "
"performance cost when set above ``0.0``."
msgstr ""

#: ../../docs/tutorials/3d/volumetric_fog.rst:58
msgid ""
"**Anisotropy:** The direction of scattered light as it goes through the "
"volumetric fog. A value close to ``1.0`` means almost all light is scattered "
"forward. A value close to ``0.0`` means light is scattered equally in all "
"directions. A value close to ``-1.0`` means light is scattered mostly "
"backward. Fog and mist scatter light slightly forward, while smoke scatters "
"light equally in all directions."
msgstr ""

#: ../../docs/tutorials/3d/volumetric_fog.rst:64
msgid ""
"**Length:** The distance over which the volumetric fog is computed. Increase "
"to compute fog over a greater range, decrease to add more detail when a long "
"range is not needed. For best quality fog, keep this as low as possible."
msgstr ""

#: ../../docs/tutorials/3d/volumetric_fog.rst:67
msgid ""
"**Detail Spread:** The distribution of size down the length of the froxel "
"buffer. A higher value compresses the froxels closer to the camera and "
"places more detail closer to the camera."
msgstr ""

#: ../../docs/tutorials/3d/volumetric_fog.rst:70
msgid ""
"**Ambient Inject:** Scales the strength of ambient light used in the "
"volumetric fog. A value of ``0.0`` means that ambient light will not impact "
"the volumetric fog. This has a small performance cost when set above ``0.0``."
msgstr ""

#: ../../docs/tutorials/3d/volumetric_fog.rst:73
msgid ""
"**Sky Affect:** Controls how much volumetric fog should be drawn onto the "
"background sky. If set to ``0.0``, volumetric fog won't affect sky rendering "
"at all (including FogVolumes)."
msgstr ""

#: ../../docs/tutorials/3d/volumetric_fog.rst:77
msgid ""
"Two additional properties are offered in the **Temporal Reprojection** "
"section:"
msgstr ""

#: ../../docs/tutorials/3d/volumetric_fog.rst:79
msgid ""
"**Temporal Reprojection > Enabled:** Enables temporal reprojection in the "
"volumetric fog. Temporal reprojection blends the current frame's volumetric "
"fog with the last frame's volumetric fog to smooth out jagged edges. The "
"performance cost is minimal, however it does lead to moving FogVolumes and "
"Light3Ds \"ghosting\" and leaving a trail behind them. When temporal "
"reprojection is enabled, try to avoid moving FogVolumes or Light3Ds too "
"fast. Short-lived dynamic lighting effects should have **Volumetric Fog "
"Energy** set to ``0.0`` to avoid ghosting."
msgstr ""

#: ../../docs/tutorials/3d/volumetric_fog.rst:87
msgid ""
"**Temporal Reprojection > Amount:** The amount by which to blend the last "
"frame with the current frame. A higher number results in smoother volumetric "
"fog, but makes \"ghosting\" much worse. A lower value reduces ghosting but "
"can result in the per-frame temporal jitter becoming visible."
msgstr ""

#: ../../docs/tutorials/3d/volumetric_fog.rst:94
msgid ""
"Unlike non-volumetric fog, volumetric fog has a *finite* range. This means "
"volumetric fog cannot entirely cover a large world, as it will eventually "
"stop being rendered in the distance."
msgstr ""

#: ../../docs/tutorials/3d/volumetric_fog.rst:98
msgid ""
"If you wish to hide distant areas from the player, it's recommended to "
"enable both non-volumetric fog and volumetric fog at the same time, and "
"adjust their density accordingly."
msgstr ""

#: ../../docs/tutorials/3d/volumetric_fog.rst:103
msgid "Light interaction with volumetric fog"
msgstr ""

#: ../../docs/tutorials/3d/volumetric_fog.rst:105
msgid ""
"To simulate fog light scattering behavior in real life, all light types will "
"interact with volumetric fog. How much each light will affect volumetric fog "
"can be adjusted using the **Volumetric Fog Energy** property on each light. "
"Enabling shadows on a light will also make those shadows visible on "
"volumetric fog."
msgstr ""

#: ../../docs/tutorials/3d/volumetric_fog.rst:110
msgid ""
"If fog light interaction is not desired for artistic reasons, this can be "
"globally disabled by setting **Volumetric Fog > Albedo** to a pure black "
"color in the Environment resource. Fog light interaction can also be "
"disabled for specific lights by setting its **Volumetric Fog Energy** to "
"``0``. Doing so will also improve performance slightly by excluding the "
"light from volumetric fog computations."
msgstr ""

#: ../../docs/tutorials/3d/volumetric_fog.rst:118
msgid "Using volumetric fog as a volumetric lighting solution"
msgstr ""

#: ../../docs/tutorials/3d/volumetric_fog.rst:120
msgid ""
"While not physically accurate, it is possible to tune volumetric fog's "
"settings to work as volumetric *lighting* solution. This means that unlit "
"parts of the environment will not be darkened anymore by fog, but light will "
"still be able to make fog brighter in specific areas."
msgstr ""

#: ../../docs/tutorials/3d/volumetric_fog.rst:125
msgid ""
"This can be done by setting volumetric fog density to the lowest permitted "
"value *greater than zero* (``0.0001``), then increasing the **Volumetric Fog "
"Energy** property on lights to much higher values than the default to "
"compensate. Values between ``10000`` and ``100000`` usually work well for "
"this."
msgstr ""

#: ../../docs/tutorials/3d/volumetric_fog.rst:135
msgid ""
"There are a few project settings available to adjust volumetric fog "
"performance and quality:"
msgstr ""

#: ../../docs/tutorials/3d/volumetric_fog.rst:138
msgid ""
"**Rendering > Environment > Volumetric Fog > Volume Size:** Base size used "
"to determine size of froxel buffer in the camera X-axis and Y-axis. The "
"final size is scaled by the aspect ratio of the screen, so actual values may "
"differ from what is set. Set a larger size for more detailed fog, set a "
"smaller size for better performance."
msgstr ""

#: ../../docs/tutorials/3d/volumetric_fog.rst:143
msgid ""
"**Rendering > Environment > Volumetric Fog > Volume Depth:** Number of "
"slices to use along the depth of the froxel buffer for volumetric fog. A "
"lower number will be more efficient but may result in artifacts appearing "
"during camera movement."
msgstr ""

#: ../../docs/tutorials/3d/volumetric_fog.rst:147
msgid ""
"**Rendering > Environment > Volumetric Fog > Use Filter:** Enables filtering "
"of the volumetric fog effect prior to integration. This substantially blurs "
"the fog which reduces fine details but also smooths out harsh edges and "
"aliasing artifacts. Disable when more detail is required."
msgstr ""

#: ../../docs/tutorials/3d/volumetric_fog.rst:154
msgid ""
"Volumetric fog can cause banding to appear on the viewport, especially at "
"higher density levels. See :ref:`doc_3d_rendering_limitations_color_banding` "
"for guidance on reducing banding."
msgstr ""

#: ../../docs/tutorials/3d/volumetric_fog.rst:159
msgid "Using fog volumes for local volumetric fog"
msgstr ""

#: ../../docs/tutorials/3d/volumetric_fog.rst:161
msgid ""
"Sometimes, you want fog to be constrained to specific areas. Conversely, you "
"may want to have global volumetric fog but fog should be excluded from "
"certain areas. Both approaches can be followed using FogVolume nodes."
msgstr ""

#: ../../docs/tutorials/3d/volumetric_fog.rst:165
msgid "Here's a quick start guide to using FogVolumes:"
msgstr ""

#: ../../docs/tutorials/3d/volumetric_fog.rst:167
msgid ""
"Make sure **Volumetric Fog** is enabled in the Environment properties. If "
"global volumetric fog is undesired, set its **Density** to ``0.0``."
msgstr ""

#: ../../docs/tutorials/3d/volumetric_fog.rst:169
#, fuzzy
msgid "Create a FogVolume node."
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/3d/volumetric_fog.rst:170
msgid "Assign a new FogMaterial to the FogVolume node's **Material** property."
msgstr ""

#: ../../docs/tutorials/3d/volumetric_fog.rst:171
msgid ""
"In the FogMaterial, set **Density** to a positive value to increase density "
"within the FogVolume, or a negative value to subtract the density from "
"global volumetric fog."
msgstr ""

#: ../../docs/tutorials/3d/volumetric_fog.rst:174
msgid "Configure the FogVolume's extents and shape as needed."
msgstr ""

#: ../../docs/tutorials/3d/volumetric_fog.rst:178
msgid ""
"Thin fog volumes may appear to flicker when the camera moves or rotates. "
"This can be alleviated by increasing the **Rendering > Environment > "
"Volumetric Fog > Volume Depth** project setting (at a performance cost) or "
"by decreasing **Length** in the Environment volumetric fog properties (at no "
"performance cost, but at the cost of lower fog range). Alternatively, the "
"FogVolume can be made thicker and use a lower density in the **Material**."
msgstr ""

#: ../../docs/tutorials/3d/volumetric_fog.rst:187
msgid "FogVolume properties"
msgstr ""

#: ../../docs/tutorials/3d/volumetric_fog.rst:189
msgid ""
"**Extents:** The size of the FogVolume when **Shape** is **Ellipsoid**, "
"**Cone**, **Cylinder** or **Box**. If **Shape** is **Cone** or **Cylinder**, "
"the cone/cylinder will be adjusted to fit within the extents. Non-uniform "
"scaling of cone/cylinder shapes via the **Extents** property is not "
"supported, but you can scale the FogVolume node instead."
msgstr ""

#: ../../docs/tutorials/3d/volumetric_fog.rst:194
msgid ""
"**Shape:** The shape of the FogVolume. This can be set to **Ellipsoid**, "
"**Cone**, **Cylinder**, **Box** or **World** (acts as global volumetric fog)."
msgstr ""

#: ../../docs/tutorials/3d/volumetric_fog.rst:196
msgid ""
"**Material:** The material used by the FogVolume. Can be either a built-in "
"FogMaterial or a custom ShaderMaterial (:ref:`doc_fog_shader`)."
msgstr ""

#: ../../docs/tutorials/3d/volumetric_fog.rst:199
msgid ""
"After choosing **New FogMaterial** in the **Material** property, you can "
"adjust the following properties in FogMaterial:"
msgstr ""

#: ../../docs/tutorials/3d/volumetric_fog.rst:202
msgid ""
"**Density:** The density of the FogVolume. Denser objects are more opaque, "
"but may suffer from under-sampling artifacts that look like stripes. "
"Negative values can be used to subtract fog from other FogVolumes or global "
"volumetric fog."
msgstr ""

#: ../../docs/tutorials/3d/volumetric_fog.rst:206
msgid ""
"**Albedo:** The single-scattering Color of the FogVolume. Internally, member "
"albedo is converted into single-scattering, which is additively blended with "
"other FogVolumes and global volumetric fog's **Albedo**."
msgstr ""

#: ../../docs/tutorials/3d/volumetric_fog.rst:209
msgid ""
"**Emission:** The Color of the light emitted by the FogVolume. Emitted light "
"will not cast light or shadows on other objects, but can be useful for "
"modulating the Color of the FogVolume independently from light sources."
msgstr ""

#: ../../docs/tutorials/3d/volumetric_fog.rst:212
msgid ""
"**Height Falloff:** The rate by which the height-based fog decreases in "
"density as height increases in world space. A high falloff will result in a "
"sharp transition, while a low falloff will result in a smoother transition. "
"A value of ``0.0`` results in uniform-density fog. The height threshold is "
"determined by the height of the associated FogVolume."
msgstr ""

#: ../../docs/tutorials/3d/volumetric_fog.rst:217
msgid ""
"**Edge Fade:** The hardness of the edges of the FogVolume. A higher value "
"will result in softer edges, while a lower value will result in harder edges."
msgstr ""

#: ../../docs/tutorials/3d/volumetric_fog.rst:219
msgid ""
"**Density Texture:** The 3D texture that is used to scale the member density "
"of the FogVolume. This can be used to vary fog density within the FogVolume "
"with any kind of static pattern. For animated effects, consider using a "
"custom :ref:`fog shader <doc_fog_shader>`. You can import any image as a 3D "
"texture by :ref:`changing its import type in the Import dock "
"<doc_importing_images_changing_import_type>`."
msgstr ""

#: ../../docs/tutorials/3d/volumetric_fog.rst:227
msgid "Using 3D noise density textures"
msgstr ""

#: ../../docs/tutorials/3d/volumetric_fog.rst:229
msgid ""
"Since Godot 4.1, there is a NoiseTexture3D resource that can be used to "
"procedurally generate 3D noise. This is well-suited to FogMaterial density "
"textures, which can result in more detailed fog effects:"
msgstr ""

#: ../../docs/tutorials/3d/volumetric_fog.rst:236
msgid "FogMaterial comparison (without and with density texture)"
msgstr ""

#: ../../docs/tutorials/3d/volumetric_fog.rst:236
msgid ""
"Screenshot taken with **Volume Size** project setting set to 192 to make "
"high-frequency detail more visible in the fog."
msgstr ""

#: ../../docs/tutorials/3d/volumetric_fog.rst:239
msgid ""
"To do so, select the **Density Texture** property and choose **New "
"NoiseTexture3D**. Edit this NoiseTexture3D by clicking it, then click "
"**Noise** at the bottom of the NoiseTexture3D properties and choose **New "
"FastNoiseLite**. Adjust the noise texture's width, height and depth "
"according to your fog volume's dimensions."
msgstr ""

#: ../../docs/tutorials/3d/volumetric_fog.rst:244
msgid ""
"To improve performance, it's recommended to use low texture sizes (64×64×64 "
"or lower), as high-frequency detail is difficult to notice in a FogVolume. "
"If you wish to represent more detailed density variations, you will need to "
"increase **Rendering > Environment > Volumetric Fog > Volume Size** in the "
"project settings, which has a performance cost."
msgstr ""

#: ../../docs/tutorials/3d/volumetric_fog.rst:252
msgid ""
"NoiseTexture3D's **Color Ramp** affects FogMaterial density textures, but "
"since only the texture's red channel is sampled, only the color ramp's red "
"channel will affect the resulting density."
msgstr ""

#: ../../docs/tutorials/3d/volumetric_fog.rst:256
msgid ""
"However, using a color ramp will *not* tint the fog volume according to the "
"texture. You would need to use a custom shader that reads a Texture3D to "
"achieve this."
msgstr ""

#: ../../docs/tutorials/3d/volumetric_fog.rst:261
#, fuzzy
msgid "Custom FogVolume shaders"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/3d/volumetric_fog.rst:263
msgid ""
"This page only covers the built-in settings offered by FogMaterial. If you "
"need to customize fog behavior within a FogVolume node (such as creating "
"animated fog), FogVolume nodes' appearance can be customized using :ref:"
"`doc_fog_shader`."
msgstr ""

#: ../../docs/tutorials/3d/volumetric_fog.rst:268
msgid "Faking volumetric fog using quads"
msgstr ""

#: ../../docs/tutorials/3d/volumetric_fog.rst:270
msgid ""
"In some cases, it may be better to use specially configured QuadMeshes as an "
"alternative to volumetric fog:"
msgstr ""

#: ../../docs/tutorials/3d/volumetric_fog.rst:273
msgid ""
"Quads work with any rendering method, including Forward Mobile and "
"Compatibility."
msgstr ""

#: ../../docs/tutorials/3d/volumetric_fog.rst:274
msgid ""
"Quads do not require temporal reprojection to look smooth, which makes them "
"suited to fast-moving dynamic effects such as lasers. They can also "
"represent small details which volumetric fog cannot do efficiently."
msgstr ""

#: ../../docs/tutorials/3d/volumetric_fog.rst:277
msgid "Quads generally have a lower performance cost than volumetric fog."
msgstr ""

#: ../../docs/tutorials/3d/volumetric_fog.rst:279
#, fuzzy
msgid "This approach has a few downsides though:"
msgstr "Ne postoje ograničenja prilikom korištenja Godot-a"

#: ../../docs/tutorials/3d/volumetric_fog.rst:281
msgid ""
"The fog effect has less realistic falloff, especially if the camera enters "
"the fog."
msgstr ""

#: ../../docs/tutorials/3d/volumetric_fog.rst:282
msgid "Transparency sorting issues may occur when sprites overlap."
msgstr ""

#: ../../docs/tutorials/3d/volumetric_fog.rst:283
msgid ""
"Performance will not necessarily be better than volumetric fog if there are "
"lots of sprites close to the camera."
msgstr ""

#: ../../docs/tutorials/3d/volumetric_fog.rst:286
msgid "To create a QuadMesh-based fog sprite:"
msgstr ""

#: ../../docs/tutorials/3d/volumetric_fog.rst:288
msgid ""
"Create a MeshInstance3D node with a QuadMesh resource in the **Mesh** "
"property. Set the size as desired."
msgstr ""

#: ../../docs/tutorials/3d/volumetric_fog.rst:290
msgid "Create a new StandardMaterial3D in the mesh's **Material** property."
msgstr ""

#: ../../docs/tutorials/3d/volumetric_fog.rst:291
msgid ""
"In the StandardMaterial3D, set **Shading > Shading Mode** to **Unshaded**, "
"**Billboard > Mode** to **Enabled**, enable **Proximity Fade** and set "
"**Distance Fade** to **Pixel Alpha**."
msgstr ""

#: ../../docs/tutorials/3d/volumetric_fog.rst:294
msgid ""
"Set the **Albedo > Texture** to the texture below (right-click and choose "
"**Save as…**):"
msgstr ""

#: ../../docs/tutorials/3d/volumetric_fog.rst:298
msgid ""
"*After* setting the albedo texture, go to the Import dock, select the "
"texture and change its compression mode to **Lossless** to improve quality."
msgstr ""

#: ../../docs/tutorials/3d/volumetric_fog.rst:301
msgid ""
"The fog's color is set using the **Albedo > Color** property; its density is "
"set using the color's alpha channel. For best results, you will have to "
"adjust **Proximity Fade > Distance** and **Distance Fade > Max Distance** "
"depending on the size of your QuadMesh."
msgstr ""

#: ../../docs/tutorials/3d/volumetric_fog.rst:306
msgid ""
"Optionally, billboarding may be left disabled if you place the quad in a way "
"where all of its corners are in solid geometry. This can be useful for "
"fogging large planes that the camera cannot enter, such as bottomless pits."
msgstr ""

#: ../../docs/tutorials/3d/3d_antialiasing.rst:4
msgid "3D antialiasing"
msgstr ""

#: ../../docs/tutorials/3d/3d_antialiasing.rst:12
msgid ""
"Godot also supports antialiasing in 2D rendering. This is covered on the :"
"ref:`doc_2d_antialiasing` page."
msgstr ""

#: ../../docs/tutorials/3d/3d_antialiasing.rst:18
msgid ""
"Due to their limited resolution, scenes rendered in 3D can exhibit aliasing "
"artifacts. These artifacts commonly manifest as a \"staircase\" effect on "
"surface edges (edge aliasing) and as flickering and/or sparkles on "
"reflective surfaces (specular aliasing)."
msgstr ""

#: ../../docs/tutorials/3d/3d_antialiasing.rst:23
msgid ""
"In the example below, you can notice how edges have a blocky appearance. The "
"vegetation is also flickering in and out, and thin lines on top of the box "
"have almost disappeared:"
msgstr ""

#: ../../docs/tutorials/3d/3d_antialiasing.rst:33
msgid ""
"To combat this, various antialiasing techniques can be used in Godot. These "
"are detailed below."
msgstr ""

#: ../../docs/tutorials/3d/3d_antialiasing.rst:38
#, fuzzy
msgid ""
"You can compare antialiasing algorithms in action using the `3D Antialiasing "
"demo project <https://github.com/godotengine/godot-demo-projects/tree/"
"master/3d/antialiasing>`__."
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati različite Godo demo projekte "
"`Godot demo projects <https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/tutorials/3d/3d_antialiasing.rst:44
msgid ""
"This technique is the \"historical\" way of dealing with aliasing. MSAA is "
"very effective on geometry edges (especially at higher levels). MSAA does "
"not introduce any blurriness whatsoever."
msgstr ""

#: ../../docs/tutorials/3d/3d_antialiasing.rst:48
msgid ""
"MSAA is available in 3 levels: 2×, 4×, 8×. Higher levels are more effective "
"at antialiasing edges, but are significantly more demanding. In games with "
"modern visuals, sticking to 2× or 4× MSAA is highly recommended as 8× MSAA "
"is usually too demanding."
msgstr ""

#: ../../docs/tutorials/3d/3d_antialiasing.rst:53
msgid ""
"The downside of MSAA is that it only operates on edges. This is because MSAA "
"increases the number of *coverage* samples, but not the number of *color* "
"samples. However, since the number of color samples did not increase, "
"fragment shaders are still run for each pixel only once. Therefore, MSAA "
"does not reduce transparency aliasing for materials using the **Alpha "
"Scissor** transparency mode (1-bit transparency). MSAA is also ineffective "
"on specular aliasing."
msgstr ""

#: ../../docs/tutorials/3d/3d_antialiasing.rst:60
msgid ""
"To mitigate aliasing on alpha scissor materials, :ref:`alpha antialiasing "
"<doc_standard_material_3d_alpha_antialiasing>` (also called *alpha to "
"coverage*) can be enabled on specific materials in the StandardMaterial3D or "
"ORMMaterial3D properties. Alpha to coverage has a moderate performance cost, "
"but it's effective at reducing aliasing on transparent materials without "
"introducing any blurriness."
msgstr ""

#: ../../docs/tutorials/3d/3d_antialiasing.rst:67
msgid ""
"MSAA can be enabled in the Project Settings by changing the value of the "
"**Rendering > Anti Aliasing > Quality > MSAA 3D** setting. It's important to "
"change the value of the **MSAA 3D** setting and not **MSAA 2D**, as these "
"are entirely separate settings."
msgstr ""

#: ../../docs/tutorials/3d/3d_antialiasing.rst:72
msgid ""
"Comparison between no antialiasing (left) and various MSAA levels (right). "
"Note that alpha antialiasing is not used here:"
msgstr ""

#: ../../docs/tutorials/3d/3d_antialiasing.rst:84
msgid "Temporal antialiasing (TAA)"
msgstr ""

#: ../../docs/tutorials/3d/3d_antialiasing.rst:86
msgid ""
"*This is only available in the Clustered Forward backend, not the Forward "
"Mobile or Compatibility backends.*"
msgstr ""

#: ../../docs/tutorials/3d/3d_antialiasing.rst:89
msgid ""
"Temporal antialiasing works by *converging* the result of previously "
"rendered frames into a single, high-quality frame. This is a continuous "
"process that works by jittering the position of all vertices in the scene "
"every frame. This jittering is done to capture sub-pixel detail and should "
"be unnoticeable except in extreme situations."
msgstr ""

#: ../../docs/tutorials/3d/3d_antialiasing.rst:95
msgid ""
"This technique is commonly used in modern games, as it provides the most "
"effective form of antialiasing against specular aliasing and other shader-"
"induced artifacts. TAA also provides full support for transparency "
"antialiasing."
msgstr ""

#: ../../docs/tutorials/3d/3d_antialiasing.rst:100
msgid ""
"TAA introduces a small amount of blur when enabled in still scenes, but this "
"blurring effect becomes more pronounced when the camera is moving. Another "
"downside of TAA is that it can exhibit *ghosting* artifacts behind moving "
"objects. Rendering at a higher framerate will allow TAA to converge faster, "
"therefore making those ghosting artifacts less visible."
msgstr ""

#: ../../docs/tutorials/3d/3d_antialiasing.rst:106
msgid ""
"Temporal antialiasing can be enabled in the Project Settings by changing the "
"value of the **Rendering > Anti Aliasing > Quality > Use TAA** setting."
msgstr ""

#: ../../docs/tutorials/3d/3d_antialiasing.rst:109
msgid "Comparison between no antialiasing (left) and TAA (right):"
msgstr ""

#: ../../docs/tutorials/3d/3d_antialiasing.rst:116
msgid "AMD FidelityFX Super Resolution 2.2 (FSR2)"
msgstr ""

#: ../../docs/tutorials/3d/3d_antialiasing.rst:118
msgid ""
"Since Godot 4.2, there is built-in support for `AMD FidelityFX Super "
"Resolution <https://www.amd.com/en/technologies/fidelityfx-super-"
"resolution>`__ 2.2. This is an :ref:`upscaling method "
"<doc_resolution_scaling>` compatible with all recent GPUs from any vendor. "
"FSR2 is normally designed to improve performance by lowering the internal 3D "
"rendering resolution, then upscaling to the output resolution."
msgstr ""

#: ../../docs/tutorials/3d/3d_antialiasing.rst:125
msgid ""
"However, unlike FSR1, FSR2 also provides temporal antialiasing. This means "
"FSR2 can be used at native resolution for high-quality antialiasing, with "
"the input resolution being equal to the output resolution. In this "
"situation, enabling FSR2 will actually *decrease* performance, but it will "
"significantly improve rendering quality."
msgstr ""

#: ../../docs/tutorials/3d/3d_antialiasing.rst:131
msgid ""
"Using FSR2 at native resolution is more demanding than using TAA at native "
"resolution, so its use is only recommended if you have significant GPU "
"headroom. On the bright side, FSR2 provides better antialiasing coverage "
"with less blurriness compared to TAA, especially in motion."
msgstr ""

#: ../../docs/tutorials/3d/3d_antialiasing.rst:136
msgid ""
"Comparison between no antialiasing (left) and FSR2 at native resolution "
"(right):"
msgstr ""

#: ../../docs/tutorials/3d/3d_antialiasing.rst:142
msgid ""
"By default, the **FSR Sharpness** project setting is set to ``0.2`` (higher "
"values result in less sharpening). For the purposes of comparison, FSR "
"sharpening has been disabled by setting it to ``2.0`` on the above "
"screenshot."
msgstr ""

#: ../../docs/tutorials/3d/3d_antialiasing.rst:149
msgid "Fast approximate antialiasing (FXAA)"
msgstr ""

#: ../../docs/tutorials/3d/3d_antialiasing.rst:151
#: ../../docs/tutorials/3d/3d_antialiasing.rst:178
#: ../../docs/tutorials/3d/3d_antialiasing.rst:219
msgid ""
"*This is only available in the Clustered Forward and Forward Mobile "
"backends, not the Compatibility backend.*"
msgstr ""

#: ../../docs/tutorials/3d/3d_antialiasing.rst:154
msgid ""
"Fast approximate antialiasing is a post-processing antialiasing solution. It "
"is faster to run than any other antialiasing technique and also supports "
"antialiasing transparency. However, since it lacks temporal information, it "
"will not do much against specular aliasing."
msgstr ""

#: ../../docs/tutorials/3d/3d_antialiasing.rst:159
msgid ""
"This technique is still sometimes used in mobile games. However, on desktop "
"platforms, FXAA generally fell out of fashion in favor of temporal "
"antialiasing, which is much more effective against specular aliasing. "
"Nonetheless, exposing FXAA as an in-game option may still be worthwhile for "
"players with low-end GPUs."
msgstr ""

#: ../../docs/tutorials/3d/3d_antialiasing.rst:164
msgid ""
"FXAA introduces a moderate amount of blur when enabled (more than TAA when "
"still, but less than TAA when the camera is moving)."
msgstr ""

#: ../../docs/tutorials/3d/3d_antialiasing.rst:167
msgid ""
"FXAA can be enabled in the Project Settings by changing the value of the "
"**Rendering > Anti Aliasing > Quality > Screen Space AA** setting to "
"**FXAA**."
msgstr ""

#: ../../docs/tutorials/3d/3d_antialiasing.rst:171
msgid "Comparison between no antialiasing (left) and FXAA (right):"
msgstr ""

#: ../../docs/tutorials/3d/3d_antialiasing.rst:176
msgid "Supersample antialiasing (SSAA)"
msgstr ""

#: ../../docs/tutorials/3d/3d_antialiasing.rst:181
msgid ""
"Supersampling provides the highest quality of antialiasing possible, but "
"it's also the most expensive. It works by shading every pixel in the scene "
"multiple times. This allows SSAA to antialias edges, transparency *and* "
"specular aliasing at the same time, without introducing potential ghosting "
"artifacts."
msgstr ""

#: ../../docs/tutorials/3d/3d_antialiasing.rst:186
msgid ""
"The downside of SSAA is its *extremely* high cost. This cost generally makes "
"SSAA difficult to use for game purposes, but you may still find "
"supersampling useful for :ref:`offline rendering <doc_creating_movies>`."
msgstr ""

#: ../../docs/tutorials/3d/3d_antialiasing.rst:190
msgid ""
"Supersample antialiasing is performed by increasing the **Rendering > "
"Scaling 3D > Scale** advanced project setting above ``1.0`` while ensuring "
"**Rendering > Scaling 3D > Mode** is set to **Bilinear** (the default). "
"Since the scale factor is defined per-axis, a scale factor of ``1.5`` will "
"result in 2.25× SSAA while a scale factor of ``2.0`` will result in 4× SSAA. "
"Since Godot uses the hardware's own bilinear filtering to perform the "
"downsampling, the result will look crisper at integer scale factors (namely, "
"``2.0``)."
msgstr ""

#: ../../docs/tutorials/3d/3d_antialiasing.rst:198
msgid ""
"Comparison between no antialiasing (left) and various SSAA levels (right):"
msgstr ""

#: ../../docs/tutorials/3d/3d_antialiasing.rst:206
msgid ""
"Supersampling also has high video RAM requirements, since it needs to render "
"in the target resolution then *downscale* to the window size. For example, "
"displaying a project in 3840×2160 (4K resolution) with 4× SSAA will require "
"rendering the scene in 7680×4320 (8K resolution), which is 4 times more "
"pixels."
msgstr ""

#: ../../docs/tutorials/3d/3d_antialiasing.rst:212
msgid ""
"If you are using a high window size such as 4K, you may find that increasing "
"the resolution scale past a certain value will cause a heavy slowdown (or "
"even a crash) due to running out of VRAM."
msgstr ""

#: ../../docs/tutorials/3d/3d_antialiasing.rst:217
msgid "Screen-space roughness limiter"
msgstr ""

#: ../../docs/tutorials/3d/3d_antialiasing.rst:222
msgid ""
"This is not an edge antialiasing method, but it is a way of reducing "
"specular aliasing in 3D."
msgstr ""

#: ../../docs/tutorials/3d/3d_antialiasing.rst:225
msgid ""
"The screen-space roughness limiter works best on detailed geometry. While it "
"has an effect on roughness map rendering itself, its impact is limited there."
msgstr ""

#: ../../docs/tutorials/3d/3d_antialiasing.rst:228
msgid ""
"The screen-space roughness limiter is enabled by default; it doesn't require "
"any manual setup. It has a small performance impact, so consider disabling "
"it if your project isn't affected by specular aliasing much."
msgstr ""

#: ../../docs/tutorials/3d/3d_antialiasing.rst:233
msgid "Texture roughness limiter on import"
msgstr ""

#: ../../docs/tutorials/3d/3d_antialiasing.rst:235
msgid ""
"Like the screen-space roughness limiter, this is not an edge antialiasing "
"method, but it is a way of reducing specular aliasing in 3D."
msgstr ""

#: ../../docs/tutorials/3d/3d_antialiasing.rst:238
msgid ""
"Roughness limiting on import works by specifying a normal map to use as a "
"guide for limiting roughness. This is done by selecting the roughness map in "
"the FileSystem dock, then going to the Import dock and setting **Roughness > "
"Mode** to the color channel the roughness map is stored in (typically "
"**Green**), then setting the path to the material's normal map. Remember to "
"click **Reimport** at the bottom of the Import dock after setting the path "
"to the normal map."
msgstr ""

#: ../../docs/tutorials/3d/3d_antialiasing.rst:245
msgid ""
"Since this processing occurs purely on import, it has no performance cost "
"whatsoever. However, its visual impact is limited. Limiting roughness on "
"import only helps reduce specular aliasing within textures, not the aliasing "
"that occurs on geometry edges on detailed meshes."
msgstr ""

#: ../../docs/tutorials/3d/3d_antialiasing.rst:251
msgid "Which antialiasing technique should I use?"
msgstr ""

#: ../../docs/tutorials/3d/3d_antialiasing.rst:253
msgid ""
"**There is no \"one size fits all\" antialiasing technique.** Since "
"antialiasing is often demanding on the GPU or can introduce unwanted "
"blurriness, you'll want to add a setting to allow players to disable "
"antialiasing."
msgstr ""

#: ../../docs/tutorials/3d/3d_antialiasing.rst:257
msgid ""
"For projects with a photorealistic art direction, TAA is generally the most "
"suitable option. While TAA can introduce ghosting artifacts, there is no "
"other technique that combats specular aliasing as well as TAA does. The "
"screen-space roughness limiter helps a little, but is far less effective "
"against specular aliasing overall. If you have spare GPU power, you can use "
"FSR2 at native resolution for a better-looking form of temporal antialiasing "
"compared to standard TAA."
msgstr ""

#: ../../docs/tutorials/3d/3d_antialiasing.rst:265
msgid ""
"For projects with a low amount of reflective surfaces (such as a cartoon "
"artstyle), MSAA can work well. MSAA is also a good option if avoiding "
"blurriness and temporal artifacts is important, such as in competitive games."
msgstr ""

#: ../../docs/tutorials/3d/3d_antialiasing.rst:269
msgid ""
"When targeting low-end platforms such as mobile or integrated graphics, FXAA "
"is usually the only viable option. 2× MSAA may be usable in some "
"circumstances, but higher MSAA levels are unlikely to run smoothly on mobile "
"GPUs."
msgstr ""

#: ../../docs/tutorials/3d/3d_antialiasing.rst:273
msgid ""
"Godot allows using multiple antialiasing techniques at the same time. This "
"is usually unnecessary, but it can provide better visuals on high-end GPUs "
"or for :ref:`non-real-time rendering <doc_creating_movies>`. For example, to "
"make moving edges look better when TAA is enabled, you can also enable MSAA "
"at the same time."
msgstr ""

#: ../../docs/tutorials/3d/using_multi_mesh_instance.rst:6
msgid "Using MultiMeshInstance3D"
msgstr ""

#: ../../docs/tutorials/3d/using_multi_mesh_instance.rst:11
msgid ""
"In a normal scenario, you would use a :ref:`MeshInstance3D "
"<class_MeshInstance3D>` node to display a 3D mesh like a human model for the "
"main character, but in some cases, you would like to create multiple "
"instances of the same mesh in a scene. You *could* duplicate the same node "
"multiple times and adjust the transforms manually. This may be a tedious "
"process and the result may look mechanical. Also, this method is not "
"conducive to rapid iterations. :ref:`MultiMeshInstance3D "
"<class_MultiMeshInstance3D>` is one of the possible solutions to this "
"problem."
msgstr ""

#: ../../docs/tutorials/3d/using_multi_mesh_instance.rst:20
msgid ""
"MultiMeshInstance3D, as the name suggests, creates multiple copies of a "
"MeshInstance over a surface of a specific mesh. An example would be having a "
"tree mesh populate a landscape mesh with trees of random scales and "
"orientations."
msgstr ""

#: ../../docs/tutorials/3d/using_multi_mesh_instance.rst:25
msgid "Setting up the nodes"
msgstr ""

#: ../../docs/tutorials/3d/using_multi_mesh_instance.rst:27
msgid ""
"The basic setup requires three nodes: the MultiMeshInstance3D node and two "
"MeshInstance3D nodes."
msgstr ""

#: ../../docs/tutorials/3d/using_multi_mesh_instance.rst:30
msgid ""
"One node is used as the target, the surface mesh that you want to place "
"multiple meshes on. In the tree example, this would be the landscape."
msgstr ""

#: ../../docs/tutorials/3d/using_multi_mesh_instance.rst:33
msgid ""
"The other node is used as the source, the mesh that you want to have "
"duplicated. In the tree case, this would be the tree itself."
msgstr ""

#: ../../docs/tutorials/3d/using_multi_mesh_instance.rst:36
msgid ""
"In our example, we would use a :ref:`Node3D <class_Node3D>` node as the root "
"node of the scene. Your scene tree would look like this:"
msgstr ""

#: ../../docs/tutorials/3d/using_multi_mesh_instance.rst:41
msgid "For simplicity's sake, this tutorial uses built-in primitives."
msgstr ""

#: ../../docs/tutorials/3d/using_multi_mesh_instance.rst:43
msgid ""
"Now you have everything ready. Select the MultiMeshInstance3D node and look "
"at the toolbar, you should see an extra button called ``MultiMesh`` next to "
"``View``. Click it and select *Populate surface* in the dropdown menu. A new "
"window titled *Populate MultiMesh* will pop up."
msgstr ""

#: ../../docs/tutorials/3d/using_multi_mesh_instance.rst:53
msgid "MultiMesh settings"
msgstr ""

#: ../../docs/tutorials/3d/using_multi_mesh_instance.rst:55
msgid "Below are descriptions of the options."
msgstr ""

#: ../../docs/tutorials/3d/using_multi_mesh_instance.rst:58
msgid "Target Surface"
msgstr ""

#: ../../docs/tutorials/3d/using_multi_mesh_instance.rst:60
msgid ""
"The mesh used as the target surface on which to place copies of your source "
"mesh."
msgstr ""

#: ../../docs/tutorials/3d/using_multi_mesh_instance.rst:64
msgid "Source Mesh"
msgstr ""

#: ../../docs/tutorials/3d/using_multi_mesh_instance.rst:66
msgid "The mesh you want duplicated on the target surface."
msgstr ""

#: ../../docs/tutorials/3d/using_multi_mesh_instance.rst:69
msgid "Mesh Up Axis"
msgstr ""

#: ../../docs/tutorials/3d/using_multi_mesh_instance.rst:71
msgid "The axis used as the up axis of the source mesh."
msgstr ""

#: ../../docs/tutorials/3d/using_multi_mesh_instance.rst:74
msgid "Random Rotation"
msgstr ""

#: ../../docs/tutorials/3d/using_multi_mesh_instance.rst:76
msgid "Randomizing the rotation around the up axis of the source mesh."
msgstr ""

#: ../../docs/tutorials/3d/using_multi_mesh_instance.rst:79
msgid "Random Tilt"
msgstr ""

#: ../../docs/tutorials/3d/using_multi_mesh_instance.rst:81
msgid "Randomizing the overall rotation of the source mesh."
msgstr ""

#: ../../docs/tutorials/3d/using_multi_mesh_instance.rst:84
msgid "Random Scale"
msgstr ""

#: ../../docs/tutorials/3d/using_multi_mesh_instance.rst:86
msgid "Randomizing the scale of the source mesh."
msgstr ""

#: ../../docs/tutorials/3d/using_multi_mesh_instance.rst:91
msgid ""
"The scale of the source mesh that will be placed over the target surface."
msgstr ""

#: ../../docs/tutorials/3d/using_multi_mesh_instance.rst:94
msgid "Amount"
msgstr ""

#: ../../docs/tutorials/3d/using_multi_mesh_instance.rst:96
msgid "The amount of mesh instances placed over the target surface."
msgstr ""

#: ../../docs/tutorials/3d/using_multi_mesh_instance.rst:98
msgid ""
"Select the target surface. In the tree case, this should be the landscape "
"node. The source mesh should be the tree node. Adjust the other parameters "
"according to your preference. Press ``Populate`` and multiple copies of the "
"source mesh will be placed over the target mesh. If you are satisfied with "
"the result, you can delete the mesh instance used as the source mesh."
msgstr ""

#: ../../docs/tutorials/3d/using_multi_mesh_instance.rst:104
msgid "The end result should look like this:"
msgstr ""

#: ../../docs/tutorials/3d/using_multi_mesh_instance.rst:108
msgid ""
"To change the result, repeat the previous steps with different parameters."
msgstr ""

#: ../../docs/tutorials/3d/mesh_lod.rst:4
msgid "Mesh level of detail (LOD)"
msgstr ""

#: ../../docs/tutorials/3d/mesh_lod.rst:6
msgid ""
"Level of detail (LOD) is one of the most important ways to optimize "
"rendering performance in a 3D project, along with :ref:"
"`doc_occlusion_culling`."
msgstr ""

#: ../../docs/tutorials/3d/mesh_lod.rst:11
msgid "How mesh LOD can improve your 3D project's rendering performance."
msgstr ""

#: ../../docs/tutorials/3d/mesh_lod.rst:12
msgid "How to set up mesh LOD in Godot."
msgstr ""

#: ../../docs/tutorials/3d/mesh_lod.rst:13
msgid ""
"How to measure mesh LOD's effectiveness in your project (and alternatives "
"you can explore if it doesn't meet your expectations)."
msgstr ""

#: ../../docs/tutorials/3d/mesh_lod.rst:18
#, fuzzy
msgid ""
"You can see how mesh LOD works in action using the `Occlusion Culling and "
"Mesh LOD demo project <https://github.com/godotengine/godot-demo-projects/"
"tree/master/3d/occlusion_culling_mesh_lod>`__."
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati različite Godo demo projekte "
"`Godot demo projects <https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/tutorials/3d/mesh_lod.rst:24
msgid ""
"Historically, level of detail in 3D games involved manually authoring meshes "
"with lower geometry density, then configuring the distance thresholds at "
"which these lower-detailed meshes should be drawn. This approach is still "
"used today when increased control is needed."
msgstr ""

#: ../../docs/tutorials/3d/mesh_lod.rst:29
msgid ""
"However, in projects that have a large amount of detailed 3D assets, setting "
"up LOD manually can be a very time-consuming process. As a result, automatic "
"mesh decimation and LOD configuration is becoming increasingly popular."
msgstr ""

#: ../../docs/tutorials/3d/mesh_lod.rst:33
msgid ""
"Godot provides a way to automatically generate less detailed meshes for LOD "
"usage on import, then use those LOD meshes when needed automatically. This "
"is completely transparent to the user. The `meshoptimizer <https://"
"meshoptimizer.org/>`__ library is used for LOD mesh generation behind the "
"scenes."
msgstr ""

#: ../../docs/tutorials/3d/mesh_lod.rst:39
msgid ""
"Mesh LOD works with any node that draws 3D meshes. This includes "
"MeshInstance3D, MultiMeshInstance3D, GPUParticles3D and CPUParticles3D."
msgstr ""

#: ../../docs/tutorials/3d/mesh_lod.rst:45
msgid ""
"Here is an example of LOD meshes generated on import. Lower detailed meshes "
"will be used when the camera is far away from the object:"
msgstr ""

#: ../../docs/tutorials/3d/mesh_lod.rst:52
msgid "From most detailed (left) to least detailed (right), shaded view"
msgstr ""

#: ../../docs/tutorials/3d/mesh_lod.rst:54
msgid ""
"Here's the same image with wireframe rendering to make the decimation easier "
"to see:"
msgstr ""

#: ../../docs/tutorials/3d/mesh_lod.rst:60
msgid "From most detailed (left) to least detailed (right), wireframe view"
msgstr ""

#: ../../docs/tutorials/3d/mesh_lod.rst:64
msgid ""
"If you need to manually configure level of detail with artist-created "
"meshes, use :ref:`doc_visibility_ranges` instead of automatic mesh LOD."
msgstr ""

#: ../../docs/tutorials/3d/mesh_lod.rst:68
#, fuzzy
msgid "Generating mesh LOD"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/3d/mesh_lod.rst:70
msgid ""
"By default, mesh LOD generation happens automatically for imported 3D scenes "
"(glTF, .blend, Collada, FBX). Once LOD meshes are generated, they will "
"automatically be used when rendering the scene. You don't need to configure "
"anything manually."
msgstr ""

#: ../../docs/tutorials/3d/mesh_lod.rst:75
msgid ""
"However, mesh LOD generation does **not** automatically happen for imported "
"3D meshes (OBJ). This is because OBJ files are not imported as full 3D "
"scenes by default, but only as individual mesh resources to load into a "
"MeshInstance3D node (or GPUParticles3D, CPUParticles3D, ...)."
msgstr ""

#: ../../docs/tutorials/3d/mesh_lod.rst:80
msgid ""
"To make an OBJ file have mesh LOD generated for it, select it in the "
"FileSystem dock, go to the Import dock, change its **Import As** option to "
"**Scene** then click **Reimport**:"
msgstr ""

#: ../../docs/tutorials/3d/mesh_lod.rst:88
msgid "Changing the import type on an OBJ file in the Import dock"
msgstr ""

#: ../../docs/tutorials/3d/mesh_lod.rst:90
msgid "This will require restarting the editor after clicking **Reimport**."
msgstr ""

#: ../../docs/tutorials/3d/mesh_lod.rst:94
msgid ""
"The mesh LOD generation process is not perfect, and may occasionally "
"introduce rendering issues (especially in skinned meshes). Mesh LOD "
"generation can also take a while on complex meshes."
msgstr ""

#: ../../docs/tutorials/3d/mesh_lod.rst:98
msgid ""
"If mesh LOD causes a specific mesh to look broken, you can disable LOD "
"generation for it in the Import dock. This will also speed up resource "
"importing. This can be done globally in the 3D scene's import options, or on "
"a per-mesh basis using the Advanced Import Settings dialog."
msgstr ""

#: ../../docs/tutorials/3d/mesh_lod.rst:103
msgid ""
"See :ref:`Importing 3D scenes "
"<doc_importing_3d_scenes_using_the_import_dock>` for more information."
msgstr ""

#: ../../docs/tutorials/3d/mesh_lod.rst:107
msgid "Comparing mesh LOD visuals and performance"
msgstr ""

#: ../../docs/tutorials/3d/mesh_lod.rst:109
msgid ""
"To disable mesh LOD in the editor for comparison purposes, use the **Disable "
"Mesh LOD** advanced debug draw mode. This can be done using the menu in the "
"top-left corner of the 3D viewport (labeled **Perspective** or "
"**Orthogonal** depending on camera mode):"
msgstr ""

#: ../../docs/tutorials/3d/mesh_lod.rst:118
msgid "Disabling mesh LOD in the 3D viewport's top-left menu"
msgstr ""

#: ../../docs/tutorials/3d/mesh_lod.rst:120
msgid ""
"Enable **View Frame Time** in the same menu to view FPS in the top-right "
"corner. Also enable **View Information** in the same menu to view the number "
"of primitives (vertices + indices) rendered in the bottom-right corner."
msgstr ""

#: ../../docs/tutorials/3d/mesh_lod.rst:124
msgid ""
"If mesh LOD is working correctly in your scene and your camera is far away "
"enough from the mesh, you should notice the number of drawn primitives "
"decreasing and FPS increasing when mesh LOD is left enabled (unless you are "
"CPU-bottlenecked)."
msgstr ""

#: ../../docs/tutorials/3d/mesh_lod.rst:129
msgid ""
"To see mesh LOD decimation in action, change the debug draw mode to "
"**Display Wireframe** in the menu specified above, then adjust the "
"**Rendering > Mesh LOD > LOD Change > Threshold Pixels** project setting."
msgstr ""

#: ../../docs/tutorials/3d/mesh_lod.rst:134
msgid "Configuring mesh LOD performance and quality"
msgstr ""

#: ../../docs/tutorials/3d/mesh_lod.rst:136
msgid ""
"You can adjust how aggressive mesh LOD transitions should be in the root "
"viewport by changing the **Rendering > Mesh LOD > LOD Change > Threshold "
"Pixels** project setting. To change this value at run-time, set "
"``mesh_lod_threshold`` on the root viewport as follows:"
msgstr ""

#: ../../docs/tutorials/3d/mesh_lod.rst:145
msgid ""
"Each viewport has its own ``mesh_lod_threshold`` property, which can be set "
"independently from other viewports."
msgstr ""

#: ../../docs/tutorials/3d/mesh_lod.rst:148
msgid ""
"The default mesh LOD threshold of 1 pixel is tuned to look *perceptually* "
"lossless; it provides a significant performance gain with an unnoticeable "
"loss in quality. Higher values will make LOD transitions happen sooner when "
"the camera moves away, resulting in higher performance but lower quality."
msgstr ""

#: ../../docs/tutorials/3d/mesh_lod.rst:153
msgid ""
"If you need to perform per-object adjustments to mesh LOD, you can adjust "
"how aggressive LOD transitions should be by adjusting the **LOD Bias** "
"property on any node that inherits from GeometryInstance3D. Values *above* "
"``1.0`` will make LOD transitions happen later than usual (resulting in "
"higher quality but lower performance). Values *below* ``1.0`` will make LOD "
"transitions happen sooner than usual (resulting in lower quality but higher "
"performance)."
msgstr ""

#: ../../docs/tutorials/3d/mesh_lod.rst:160
msgid ""
"Additionally, ReflectionProbe nodes have their own **Mesh LOD Threshold** "
"property that can be adjusted to improve rendering performance when the "
"reflection probe updates. This is especially important for ReflectionProbes "
"that use the **Always** update mode."
msgstr ""

#: ../../docs/tutorials/3d/mesh_lod.rst:167
msgid ""
"When rendering the scene, mesh LOD selection uses a screen-space metric. "
"This means it automatically takes camera field of view and viewport "
"resolution into account. Higher camera FOV and lower viewport resolutions "
"will make LOD selection more aggressive; the engine will display heavily "
"decimated models earlier when the camera moves away."
msgstr ""

#: ../../docs/tutorials/3d/mesh_lod.rst:173
msgid ""
"As a result, unlike :ref:`doc_visibility_ranges`, you don't need to do "
"anything specific in your project to take camera FOV and viewport resolution "
"into account."
msgstr ""

#: ../../docs/tutorials/3d/mesh_lod.rst:178
msgid "Using mesh LOD with MultiMesh and particles"
msgstr ""

#: ../../docs/tutorials/3d/mesh_lod.rst:180
msgid ""
"For LOD selection, the point of the node's :abbr:`AABB (Axis-Aligned "
"Bounding Box)` that is the closest to the camera is used as a basis. This "
"applies to any kind of mesh LOD (including for individual MeshInstance3D)s, "
"but this has some implications for nodes that display multiple meshes at "
"once, such as MultiMeshInstance3D, GPUParticles3D and GPUParticles3D. Most "
"importantly, this means that all instances will be drawn with the same LOD "
"level at a given time."
msgstr ""

#: ../../docs/tutorials/3d/mesh_lod.rst:187
msgid ""
"If you are noticing incorrect LOD selection with GPUParticles3D, make sure "
"the node's visibility AABB is configured by selecting the GPUParticles3D "
"node and using **GPUParticles3D > Generate AABB** at the top of the 3D "
"viewport."
msgstr ""

#: ../../docs/tutorials/3d/mesh_lod.rst:192
msgid ""
"If you have instances in a MultiMesh that are far away from each other, they "
"should be placed in a separate MultiMeshInstance3D node. Doing so will also "
"improve rendering performance, as frustum and occlusion culling will be able "
"to cull individual nodes (while they can't cull individual instances in a "
"MultiMesh)."
msgstr ""

#: ../../docs/tutorials/3d/visibility_ranges.rst:4
msgid "Visibility ranges (HLOD)"
msgstr ""

#: ../../docs/tutorials/3d/visibility_ranges.rst:6
msgid ""
"Along with :ref:`doc_mesh_lod` and :ref:`doc_occlusion_culling`, visibility "
"ranges are another tool to improve performance in large, complex 3D scenes."
msgstr ""

#: ../../docs/tutorials/3d/visibility_ranges.rst:12
msgid "What visibility ranges can do and which scenarios they are useful in."
msgstr ""

#: ../../docs/tutorials/3d/visibility_ranges.rst:13
msgid "How to set up visibility ranges (manual LOD) in Godot."
msgstr ""

#: ../../docs/tutorials/3d/visibility_ranges.rst:14
msgid "How to tune visibility ranges for best performance and quality."
msgstr ""

#: ../../docs/tutorials/3d/visibility_ranges.rst:18
msgid ""
"If you only need meshes to become less detailed over distance but don't have "
"manually authored LOD meshes, consider relying on automatic :ref:"
"`doc_mesh_lod` instead."
msgstr ""

#: ../../docs/tutorials/3d/visibility_ranges.rst:22
msgid ""
"Note that automatic mesh LOD and visibility ranges can be used at the same "
"time, even on the same mesh."
msgstr ""

#: ../../docs/tutorials/3d/visibility_ranges.rst:26
msgid "How it works"
msgstr ""

#: ../../docs/tutorials/3d/visibility_ranges.rst:28
msgid ""
"Visibility ranges can be used with any node that inherits from "
"GeometryInstance3D. This means they can be used not only with MeshInstance3D "
"and MultiMeshInstance3D for artist-controlled :abbr:`HLOD (Hierarchical "
"Level of Detail)`, but also GPUParticles3D, CPUParticles3D, Label3D, "
"Sprite3D, AnimatedSprite3D and CSGShape3D."
msgstr ""

#: ../../docs/tutorials/3d/visibility_ranges.rst:33
msgid ""
"Since visibility ranges are configured on a per-node basis, this makes it "
"possible to use different node types as part of a :abbr:`LOD (Level of "
"Detail)` system. For example, you could display a MeshInstance3D "
"representing a tree when up close, and replace it with a Sprite3D impostor "
"in the distance to improve performance."
msgstr ""

#: ../../docs/tutorials/3d/visibility_ranges.rst:38
msgid ""
"The benefit of :abbr:`HLOD (Hierarchical Level of Detail)` over a "
"traditional :abbr:`LOD (Level of Detail)` system is its hierarchical nature. "
"A single larger mesh can replace several smaller meshes, so that the number "
"of draw calls can be reduced at a distance, but culling opportunities can be "
"preserved when up close. For example, you can have a group of houses that "
"uses individual MeshInstance3D nodes (one for each house) when up close, but "
"turns into a single MeshInstance3D that represents a less detailed group of "
"houses (or use a MultiMeshInstance3D)."
msgstr ""

#: ../../docs/tutorials/3d/visibility_ranges.rst:46
msgid ""
"Lastly, visibility ranges can also be used to fade certain objects entirely "
"when the camera gets too close or too far. This can be used for gameplay "
"purposes, but also to reduce visual clutter. For example, Label3D nodes can "
"be faded using visibility ranges when they're too far away to be readable or "
"relevant to the player."
msgstr ""

#: ../../docs/tutorials/3d/visibility_ranges.rst:53
#, fuzzy
msgid "Setting up visibility range"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/3d/visibility_ranges.rst:55
msgid ""
"This is a quick-start guide for configuring a basic LOD system. After "
"following this guide, this LOD system will display a SphereMesh when up "
"close and a BoxMesh when the camera is far away enough. A small hysteresis "
"margin is also configured via the **Begin Margin** and **End Margin** "
"properties. This prevents LODs from popping back and forth too quickly when "
"the camera is moving at the \"edge\" of the LOD transition."
msgstr ""

#: ../../docs/tutorials/3d/visibility_ranges.rst:62
msgid ""
"The visibility range properties can be found in the **Visibility Range** "
"section of the GeometryInstance3D inspector after selecting the "
"MeshInstance3D Node."
msgstr ""

#: ../../docs/tutorials/3d/visibility_ranges.rst:65
msgid ""
"Add a Node3D node that will be used to group the two MeshInstance3D nodes "
"together."
msgstr ""

#: ../../docs/tutorials/3d/visibility_ranges.rst:67
msgid ""
"Add a first MeshInstance3D node as a child of the Node3D. Assign a new "
"SphereMesh to its Mesh property."
msgstr ""

#: ../../docs/tutorials/3d/visibility_ranges.rst:69
msgid ""
"Set the first MeshInstance3D's visibility range **End** to ``10.0`` and "
"**End Margin** to ``1.0``."
msgstr ""

#: ../../docs/tutorials/3d/visibility_ranges.rst:71
msgid ""
"Add a second MeshInstance3D node as a child of the Node3D. Assign a new "
"BoxMesh to its Mesh property."
msgstr ""

#: ../../docs/tutorials/3d/visibility_ranges.rst:73
msgid ""
"Set the second MeshInstance3D's visibility range **Begin** to ``10.0`` and "
"**Begin Margin** to ``1.0``."
msgstr ""

#: ../../docs/tutorials/3d/visibility_ranges.rst:75
msgid ""
"Move the camera away and back towards the object. Notice how the object will "
"transition from a sphere to a box as the camera moves away."
msgstr ""

#: ../../docs/tutorials/3d/visibility_ranges.rst:79
msgid "Visibility range properties"
msgstr ""

#: ../../docs/tutorials/3d/visibility_ranges.rst:81
msgid ""
"In the inspector of any node that inherits from GeometryInstance3D, you can "
"adjust the following properties in the GeometryInstance3D's **Visibility "
"Range** section:"
msgstr ""

#: ../../docs/tutorials/3d/visibility_ranges.rst:84
msgid ""
"**Begin:** The instance will be hidden when the camera is closer to the "
"instance's *origin* than this value (in 3D units)."
msgstr ""

#: ../../docs/tutorials/3d/visibility_ranges.rst:86
msgid ""
"**Begin Margin:** The hysteresis or alpha fade transition distance to use "
"for the close-up transition (in 3D units). The behavior of this property "
"depends on **Fade Mode**."
msgstr ""

#: ../../docs/tutorials/3d/visibility_ranges.rst:89
msgid ""
"**End:** The instance will be hidden when the camera is further away from "
"the instance's *origin* than this value (in 3D units)."
msgstr ""

#: ../../docs/tutorials/3d/visibility_ranges.rst:91
msgid ""
"**End Margin:** The hysteresis or alpha fade transition distance to use for "
"the far-away transition (in 3D units). The behavior of this property depends "
"on **Fade Mode**."
msgstr ""

#: ../../docs/tutorials/3d/visibility_ranges.rst:94
msgid ""
"**Fade Mode:** Controls how the transition between LOD levels should be "
"performed. See below for details."
msgstr ""

#: ../../docs/tutorials/3d/visibility_ranges.rst:100
msgid "Fade mode"
msgstr ""

#: ../../docs/tutorials/3d/visibility_ranges.rst:104
msgid ""
"The fade mode chosen only has a visible impact if either **Visibility Range "
"> Begin Margin** or **Visibility Range > End Margin** is greater than "
"``0.0``."
msgstr ""

#: ../../docs/tutorials/3d/visibility_ranges.rst:108
msgid ""
"In the inspector's **Visibility Range** section, there are 3 fade modes to "
"choose from:"
msgstr ""

#: ../../docs/tutorials/3d/visibility_ranges.rst:111
msgid ""
"**Disabled:** Uses hysteresis to switch between LOD levels instantly. This "
"prevents situations where LOD levels are switched back and forth quickly "
"when the player moves forward and then backward at the LOD transition point. "
"The hysteresis distance is determined by **Visibility Range > Begin Margin** "
"and **Visibility Range > End Margin**. This mode provides the best "
"performance as it doesn't force rendering to become transparent during the "
"fade transition."
msgstr ""

#: ../../docs/tutorials/3d/visibility_ranges.rst:117
msgid ""
"**Self:** Uses alpha blending to smoothly fade between LOD levels. The node "
"will fade-out itself when reaching the limits of its own visibility range. "
"The fade transition distance is determined by **Visibility Range > Begin "
"Margin** and **Visibility Range > End Margin**. This mode forces transparent "
"rendering on the object during its fade transition, so it has a performance "
"impact."
msgstr ""

#: ../../docs/tutorials/3d/visibility_ranges.rst:122
msgid ""
"**Dependencies:** Uses alpha blending to smoothly fade between LOD levels. "
"The node will fade-in its dependencies when reaching the limits of its own "
"visibility range. The fade transition distance is determined by **Visibility "
"Range > Begin Margin** and **Visibility Range > End Margin**. This mode "
"forces transparent rendering on the object during its fade transition, so it "
"has a performance impact. This mode is intended for hierarchical LOD systems "
"using :ref:`Visibility parent <doc_visibility_ranges_visibility_parent>`. It "
"acts the same as **Self** if visibility ranges are used to perform non-"
"hierarchical LOD."
msgstr ""

#: ../../docs/tutorials/3d/visibility_ranges.rst:135
msgid "Visibility parent"
msgstr ""

#: ../../docs/tutorials/3d/visibility_ranges.rst:137
msgid ""
"The **Visibility Parent** property makes it easier to set up :abbr:`HLOD "
"(Hierarchical Level of Detail)`. It allows automatically hiding child nodes "
"if its parent is visible given its current visibility range properties."
msgstr ""

#: ../../docs/tutorials/3d/visibility_ranges.rst:143
msgid ""
"The target of **Visibility Parent** *must* inherit from :ref:"
"`class_GeometryInstance3D`."
msgstr ""

#: ../../docs/tutorials/3d/visibility_ranges.rst:146
msgid ""
"Despite its name, the **Visibility Parent** property *can* point to a node "
"that is not a parent of the node in the scene tree. However, it is "
"impossible to point **Visibility Parent** towards a child node, as this "
"creates a dependency cycle which is not supported. You will get an error "
"message in the Output panel if a dependency cycle occurs."
msgstr ""

#: ../../docs/tutorials/3d/visibility_ranges.rst:152
msgid ""
"Given the following scene tree (where all nodes inherit from "
"GeometryInstance3D):"
msgstr ""

#: ../../docs/tutorials/3d/visibility_ranges.rst:162
msgid ""
"In this example, *BatchOfHouses* is a large mesh designed to represent all "
"child nodes when viewed at a distance. *House1* to *House4* are smaller "
"MeshInstance3Ds representing individual houses. To configure HLOD in this "
"example, we only need to configure two things:"
msgstr ""

#: ../../docs/tutorials/3d/visibility_ranges.rst:167
msgid ""
"Set **Visibility Range Begin** to a number greater than `0.0` so that "
"*BatchOfHouses* only appears when far away enough from the camera. Below "
"this distance, we want *House1* to *House4* to be displayed instead."
msgstr ""

#: ../../docs/tutorials/3d/visibility_ranges.rst:170
msgid ""
"On *House1* to *House4*, assign the **Visibility Parent** property to "
"*BatchOfHouses*."
msgstr ""

#: ../../docs/tutorials/3d/visibility_ranges.rst:172
msgid ""
"This makes it easier to perform further adjustments, as you don't need to "
"adjust the **Visibility Range Begin** of *BatchOfHouses* and **Visibility "
"Range End** of *House1* to *House4*."
msgstr ""

#: ../../docs/tutorials/3d/visibility_ranges.rst:176
msgid ""
"Fade mode is automatically handled by the **Visibility Parent** property, so "
"that the child nodes only become hidden once the parent node is fully faded "
"out. This is done to minimize visible pop-in. Depending on your :abbr:`HLOD "
"(Hierarchical Level of Detail)` setup, you may want to try both the **Self** "
"and **Dependencies** :ref:`fade modes <doc_visibility_ranges_fade_mode>`."
msgstr ""

#: ../../docs/tutorials/3d/visibility_ranges.rst:184
msgid ""
"Nodes hidden via the **Visible** property are essentially removed from the "
"visibility dependency tree, so dependent instances will not take the hidden "
"node or its ancestors into account."
msgstr ""

#: ../../docs/tutorials/3d/visibility_ranges.rst:188
msgid ""
"In practice, this means that if the target of the **Visibility Parent** node "
"is hidden by setting its **Visible** property to ``false``, the node will "
"not be hidden according to the **Visibility Range Begin** value specified in "
"the visibility parent."
msgstr ""

#: ../../docs/tutorials/3d/visibility_ranges.rst:194
msgid "Configuration tips"
msgstr ""

#: ../../docs/tutorials/3d/visibility_ranges.rst:197
msgid "Use simpler materials at a distance to improve performance"
msgstr ""

#: ../../docs/tutorials/3d/visibility_ranges.rst:199
msgid ""
"One way to further improve performance is to use simpler materials for "
"distant LOD meshes. While using LOD meshes will reduce the number of "
"vertices that need to be rendered, the per-pixel shading load for materials "
"remains identical. However, per-pixel shading load is regularly a bottleneck "
"on the GPU in complex 3D scenes. One way to reduce this shading load on the "
"GPU is to use simpler materials when they don't make much of a visual "
"difference."
msgstr ""

#: ../../docs/tutorials/3d/visibility_ranges.rst:206
msgid ""
"Performance gains when doing so should be carefully measured, as increasing "
"the number of *unique* materials in a scene has a performance cost on its "
"own. Still, using simpler materials for distant LOD meshes can still result "
"in a net performance gain as a result of the fewer per-pixel calculations "
"required."
msgstr ""

#: ../../docs/tutorials/3d/visibility_ranges.rst:212
msgid ""
"For example, on the materials used by distant LOD meshes, you can disable "
"expensive material features such as:"
msgstr ""

#: ../../docs/tutorials/3d/visibility_ranges.rst:215
msgid "Normal Map (especially on mobile platforms)"
msgstr ""

#: ../../docs/tutorials/3d/visibility_ranges.rst:223
msgid "Proximity Fade"
msgstr ""

#: ../../docs/tutorials/3d/visibility_ranges.rst:226
#, fuzzy
msgid "Use dithering for LOD transitions"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/3d/visibility_ranges.rst:228
msgid ""
"Godot currently only supports alpha-based fading for visibility ranges. You "
"can however use dithering instead by using several different materials for "
"different LOD levels."
msgstr ""

#: ../../docs/tutorials/3d/visibility_ranges.rst:232
msgid ""
"There are two advantages to using dithering over alpha blending for LOD "
"transitions:"
msgstr ""

#: ../../docs/tutorials/3d/visibility_ranges.rst:234
msgid ""
"Higher performance, as dithering transparency is faster to render compared "
"to alpha blending."
msgstr ""

#: ../../docs/tutorials/3d/visibility_ranges.rst:236
msgid ""
"No visual glitches due to :ref:`transparency sorting issues "
"<doc_3d_rendering_limitations_transparency_sorting>` during LOD transitions."
msgstr ""

#: ../../docs/tutorials/3d/visibility_ranges.rst:240
msgid ""
"The downside of dithering is that a \"noisy\" pattern is visible during LOD "
"fade transitions. This may not be as noticeable at higher viewport "
"resolutions or when temporal antialiasing is enabled."
msgstr ""

#: ../../docs/tutorials/3d/visibility_ranges.rst:244
msgid ""
"Also, as distance fade in BaseMaterial3D only supports fading up close *or* "
"fading when far away, this setup is best used with only two LODs as part of "
"the setup."
msgstr ""

#: ../../docs/tutorials/3d/visibility_ranges.rst:248
msgid ""
"Ensure **Begin Margin** and **End Margin** is set to ``0.0`` on both "
"MeshInstance3D nodes, as hysteresis or alpha fade are not desired here."
msgstr ""

#: ../../docs/tutorials/3d/visibility_ranges.rst:250
msgid ""
"On both MeshInstance3D nodes, *decrease* **Begin** by the desired fade "
"transition distance and *increase* **End** by the same distance. This is "
"required for the dithering transition to actually be visible."
msgstr ""

#: ../../docs/tutorials/3d/visibility_ranges.rst:253
msgid ""
"On the MeshInstance3D that is displayed up close, edit its material in the "
"inspector. Set its **Distance Fade** mode to **Object Dither**. Set **Min "
"Distance** to the same value as the visibility range **End**. Set **Max "
"Distance** to the same value *minus* the fade transition distance."
msgstr ""

#: ../../docs/tutorials/3d/visibility_ranges.rst:257
msgid ""
"On the MeshInstance3D that is displayed far away, edit its material in the "
"inspector. Set its **Distance Fade** mode to **Object Dither**. Set **Min "
"Distance** to the same value as the visibility range **Begin**. Set **Max "
"Distance** to the same value *plus* the fade transition distance."
msgstr ""

#: ../../docs/tutorials/3d/occlusion_culling.rst:4
#: ../../docs/tutorials/performance/optimizing_3d_performance.rst:18
#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:731
msgid "Occlusion culling"
msgstr ""

#: ../../docs/tutorials/3d/occlusion_culling.rst:6
msgid ""
"In a 3D rendering engine, **occlusion culling** is the process of performing "
"hidden geometry removal."
msgstr ""

#: ../../docs/tutorials/3d/occlusion_culling.rst:11
msgid "What are the advantages and pitfalls of occlusion culling."
msgstr ""

#: ../../docs/tutorials/3d/occlusion_culling.rst:12
msgid "How to set up occlusion culling in Godot."
msgstr ""

#: ../../docs/tutorials/3d/occlusion_culling.rst:13
msgid "Troubleshooting common issues with occlusion culling."
msgstr ""

#: ../../docs/tutorials/3d/occlusion_culling.rst:17
#, fuzzy
msgid ""
"You can see how occlusion culling works in action using the `Occlusion "
"Culling and Mesh LOD demo project <https://github.com/godotengine/godot-demo-"
"projects/tree/master/3d/occlusion_culling_mesh_lod>`__."
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati različite Godo demo projekte "
"`Godot demo projects <https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/tutorials/3d/occlusion_culling.rst:21
msgid "Why use occlusion culling"
msgstr ""

#: ../../docs/tutorials/3d/occlusion_culling.rst:23
msgid ""
"In this example scene with hundreds of rooms stacked next to each other, a "
"dynamic object (red sphere) is hidden behind the wall in the lit room (on "
"the left of the door):"
msgstr ""

#: ../../docs/tutorials/3d/occlusion_culling.rst:31
msgid "Example scene with an occlusion culling-friendly layout"
msgstr ""

#: ../../docs/tutorials/3d/occlusion_culling.rst:33
msgid ""
"With occlusion culling disabled, all the rooms behind the lit room have to "
"be rendered. The dynamic object also has to be rendered:"
msgstr ""

#: ../../docs/tutorials/3d/occlusion_culling.rst:40
msgid "Example scene with occlusion culling disabled (wireframe)"
msgstr ""

#: ../../docs/tutorials/3d/occlusion_culling.rst:40
msgid "Example scene with occlusion culling **disabled** (wireframe)"
msgstr ""

#: ../../docs/tutorials/3d/occlusion_culling.rst:42
msgid ""
"With occlusion culling enabled, only the rooms that are actually visible "
"have to be rendered. The dynamic object is also occluded by the wall, and "
"therefore no longer has to be rendered:"
msgstr ""

#: ../../docs/tutorials/3d/occlusion_culling.rst:50
msgid "Example scene with occlusion culling enabled (wireframe)"
msgstr ""

#: ../../docs/tutorials/3d/occlusion_culling.rst:50
msgid "Example scene with occlusion culling **enabled** (wireframe)"
msgstr ""

#: ../../docs/tutorials/3d/occlusion_culling.rst:52
msgid ""
"Since the engine has less work to do (fewer vertices to render and fewer "
"draw calls), performance will increase as long as there are enough occlusion "
"culling opportunities in the scene. This means occlusion culling is most "
"effective in indoor scenes, preferably with many smaller rooms instead of "
"fewer larger rooms. Combine this with :ref:`doc_mesh_lod` and :ref:"
"`doc_visibility_ranges` to further improve performance gains."
msgstr ""

#: ../../docs/tutorials/3d/occlusion_culling.rst:61
msgid ""
"When using the Clustered Forward rendering backend, the engine already "
"performs a *depth prepass*. This consists in rendering a depth-only version "
"of the scene before rendering the scene's actual materials. This is used to "
"ensure each opaque pixel is only shaded once, reducing the cost of overdraw "
"significantly."
msgstr ""

#: ../../docs/tutorials/3d/occlusion_culling.rst:67
msgid ""
"The greatest performance benefits can be observed when using the Forward "
"Mobile rendering backend, as it does not feature a depth prepass for "
"performance reasons. As a result, occlusion culling will actively decrease "
"shading overdraw with that rendering backend."
msgstr ""

#: ../../docs/tutorials/3d/occlusion_culling.rst:72
msgid ""
"Nonetheless, even when using a depth prepass, there is still a noticeable "
"benefit to occlusion culling in complex 3D scenes. However, in scenes with "
"few occlusion culling opportunities, occlusion culling may not be worth the "
"added setup and CPU usage."
msgstr ""

#: ../../docs/tutorials/3d/occlusion_culling.rst:78
msgid "How occlusion culling works in Godot"
msgstr ""

#: ../../docs/tutorials/3d/occlusion_culling.rst:82
msgid ""
"*\"occluder\" refers to the shape blocking the view, while \"occludee\" "
"refers to the object being hidden.*"
msgstr ""

#: ../../docs/tutorials/3d/occlusion_culling.rst:84
msgid ""
"In Godot, occlusion culling works by rasterizing the scene's occluder "
"geometry to a low-resolution buffer on the CPU. This is done using the "
"software raytracing library `Embree <https://github.com/embree/embree>`__."
msgstr ""

#: ../../docs/tutorials/3d/occlusion_culling.rst:88
msgid ""
"The engine then uses this low-resolution buffer to test the occludee's :abbr:"
"`AABB (Axis-Aligned Bounding Box)` against the occluder shapes. The "
"occludee's :abbr:`AABB (Axis-Aligned Bounding Box)` must be *fully occluded* "
"by the occluder shape to be culled."
msgstr ""

#: ../../docs/tutorials/3d/occlusion_culling.rst:93
msgid ""
"As a result, smaller objects are more likely to be effectively culled than "
"larger objects. Larger occluders (such as walls) also tend to be much more "
"effective than smaller ones (such as decoration props)."
msgstr ""

#: ../../docs/tutorials/3d/occlusion_culling.rst:98
#, fuzzy
msgid "Setting up occlusion culling"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/3d/occlusion_culling.rst:100
msgid ""
"The first step to using occlusion culling is to enable the **Rendering > "
"**Occlusion Culling > Use Occlusion Culling** project setting. (Make sure "
"the **Advanced** toggle is enabled in the Project Settings dialog to be able "
"to see it.)"
msgstr ""

#: ../../docs/tutorials/3d/occlusion_culling.rst:105
msgid ""
"This project setting applies immediately, so you don't need to restart the "
"editor."
msgstr ""

#: ../../docs/tutorials/3d/occlusion_culling.rst:107
msgid ""
"After enabling the project setting, you still need to create some occluders. "
"For performance reasons, the engine doesn't automatically use all visible "
"geometry as a basis for occlusion culling. Instead, the engine requires a "
"simplified representation of the scene with only static objects to be baked."
msgstr ""

#: ../../docs/tutorials/3d/occlusion_culling.rst:112
#, fuzzy
msgid "There are two ways to set up occluders in a scene:"
msgstr "Ne postoje ograničenja prilikom korištenja Godot-a"

#: ../../docs/tutorials/3d/occlusion_culling.rst:117
msgid "Automatically baking occluders (recommended)"
msgstr ""

#: ../../docs/tutorials/3d/occlusion_culling.rst:121
msgid ""
"Only MeshInstance3D nodes are currently taken into account in the *occluder* "
"baking process. MultiMeshInstance3D, GPUParticles3D, CPUParticles3D and CSG "
"nodes are **not** taken into account when baking occluders. If you wish "
"those to be treated as occluders, you have to manually create occluder "
"shapes that (roughly) match their geometry."
msgstr ""

#: ../../docs/tutorials/3d/occlusion_culling.rst:127
msgid ""
"This restriction does not apply to *occludees*. Any node type that inherits "
"from GeometryInstance3D can be occluded."
msgstr ""

#: ../../docs/tutorials/3d/occlusion_culling.rst:130
msgid ""
"After enabling the occlusion culling project setting mentioned above, add an "
"OccluderInstance3D node to the scene containing your 3D level."
msgstr ""

#: ../../docs/tutorials/3d/occlusion_culling.rst:133
msgid ""
"Select the OccluderInstance3D node, then click **Bake Occluders** at the top "
"of the 3D editor viewport. After baking, the OccluderInstance3D node will "
"contain an Occluder3D resource that stores a simplified version of your "
"level's geometry. This occluder geometry appears as purple wireframe lines "
"in the 3D view (as long as **View Gizmos** is enabled in the **Perspective** "
"menu). This geometry is then used to provide occlusion culling for both "
"static and dynamic occludees."
msgstr ""

#: ../../docs/tutorials/3d/occlusion_culling.rst:141
msgid ""
"After baking, you may notice that your dynamic objects (such as the player, "
"enemies, etc…) are included in the baked mesh. To prevent this, set the "
"**Bake > Cull Mask** property on the OccluderInstance3D to exclude certain "
"visual layers from being baked."
msgstr ""

#: ../../docs/tutorials/3d/occlusion_culling.rst:146
msgid ""
"For example, you can disable layer 2 on the cull mask, then configure your "
"dynamic objects' MeshInstance3D nodes to be located on the visual layer 2 "
"(instead of layer 1). To do so, select the MeshInstance3D node in question, "
"then on the **VisualInstance3D > Layers** property, uncheck layer 1 then "
"check layer 2. After configuring both cull mask and layers, bake occluders "
"again by following the above process."
msgstr ""

#: ../../docs/tutorials/3d/occlusion_culling.rst:154
msgid "Manually placing occluders"
msgstr ""

#: ../../docs/tutorials/3d/occlusion_culling.rst:156
msgid ""
"This approach is more suited for specialized use cases, such as creating "
"occlusion for MultiMeshInstance3D setups or CSG nodes (due to the "
"aforementioned limitation)."
msgstr ""

#: ../../docs/tutorials/3d/occlusion_culling.rst:159
msgid ""
"After enabling the occlusion culling project setting mentioned above, add an "
"OccluderInstance3D node to the scene containing your 3D level. Select the "
"OccluderInstance3D node, then choose an occluder type to add in the "
"**Occluder** property:"
msgstr ""

#: ../../docs/tutorials/3d/occlusion_culling.rst:164
msgid "QuadOccluder3D (a single plane)"
msgstr ""

#: ../../docs/tutorials/3d/occlusion_culling.rst:165
msgid "BoxOccluder3D (a cuboid)"
msgstr ""

#: ../../docs/tutorials/3d/occlusion_culling.rst:166
msgid "SphereOccluder3D (a sphere-shaped occluder)"
msgstr ""

#: ../../docs/tutorials/3d/occlusion_culling.rst:167
msgid "PolygonOccluder3D (a 2D polygon with as many points as you want)"
msgstr ""

#: ../../docs/tutorials/3d/occlusion_culling.rst:169
msgid ""
"There is also ArrayOccluder3D, whose points can't be modified in the editor "
"but can be useful for procedural generation from a script."
msgstr ""

#: ../../docs/tutorials/3d/occlusion_culling.rst:175
msgid "Previewing occlusion culling"
msgstr ""

#: ../../docs/tutorials/3d/occlusion_culling.rst:177
msgid ""
"You can enable a debug draw mode to preview what the occlusion culling is "
"actually \"seeing\". In the top-left corner of the 3D editor viewport, click "
"the **Perspective** button (or **Orthogonal** depending on your current "
"camera mode), then choose **Display Advanced… > Occlusion Culling Buffer**. "
"This will display the low-resolution buffer that is used by the engine for "
"occlusion culling."
msgstr ""

#: ../../docs/tutorials/3d/occlusion_culling.rst:184
msgid ""
"In the same menu, you can also enable **View Information** and **View Frame "
"Time** to view the number of draw calls and rendered primitives (vertices + "
"indices) in the bottom-right corner, along with the number of frames per "
"second rendered in the top-right corner."
msgstr ""

#: ../../docs/tutorials/3d/occlusion_culling.rst:189
msgid ""
"If you toggle occlusion culling in the project settings while this "
"information is displayed, you can see how much occlusion culling improves "
"performance in your scene. Note that the performance benefit highly depends "
"on the 3D editor camera's view angle, as occlusion culling is only effective "
"if there are occluders in front of the camera."
msgstr ""

#: ../../docs/tutorials/3d/occlusion_culling.rst:195
msgid ""
"To toggle occlusion culling at run-time, set ``use_occlusion_culling`` on "
"the root viewport as follows:"
msgstr ""

#: ../../docs/tutorials/3d/occlusion_culling.rst:202
msgid ""
"Toggling occlusion culling at run-time is useful to compare performance on a "
"running project."
msgstr ""

#: ../../docs/tutorials/3d/occlusion_culling.rst:206
#, fuzzy
msgid "Performance considerations"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/3d/occlusion_culling.rst:209
msgid "Design your levels to take advantage of occlusion culling"
msgstr ""

#: ../../docs/tutorials/3d/occlusion_culling.rst:211
msgid ""
"**This is the most important guideline.** A good level design is not just "
"about what the gameplay demands; it should also be built with occlusion in "
"mind."
msgstr ""

#: ../../docs/tutorials/3d/occlusion_culling.rst:214
msgid ""
"For indoor environments, add opaque walls to \"break\" the line of sight at "
"regular intervals and ensure not too much of the scene can be seen at once."
msgstr ""

#: ../../docs/tutorials/3d/occlusion_culling.rst:217
msgid ""
"For large open scenes, use a pyramid-like structure for the terrain's "
"elevation when possible. This provides the greatest culling opportunities "
"compared to any other terrain shape."
msgstr ""

#: ../../docs/tutorials/3d/occlusion_culling.rst:222
msgid "Avoid moving OccluderInstance3D nodes during gameplay"
msgstr ""

#: ../../docs/tutorials/3d/occlusion_culling.rst:224
msgid ""
"This includes moving the parents of OccluderInstance3D nodes, as this will "
"cause the nodes themselves to move in global space, therefore requiring the :"
"abbr:`BVH (Bounding Volume Hierarchy)` to be rebuilt."
msgstr ""

#: ../../docs/tutorials/3d/occlusion_culling.rst:228
msgid ""
"Toggling an OccluderInstance3D's visibility (or one of its parents' "
"visibility) is not as expensive, as the update only needs to happen once "
"(rather than continuously)."
msgstr ""

#: ../../docs/tutorials/3d/occlusion_culling.rst:232
msgid ""
"For example, if you have a sliding or rotating door, you can make the "
"OccluderInstance3D node not be a child of the door itself (so that the "
"occluder never moves), but you can hide the OccluderInstance3D visibility "
"once the door starts opening. You can then reshow the OccluderInstance3D "
"once the door is fully closed."
msgstr ""

#: ../../docs/tutorials/3d/occlusion_culling.rst:238
msgid ""
"If you absolutely have to move an OccluderInstance3D node during gameplay, "
"use a primitive Occluder3D shape for it instead of a complex baked shape."
msgstr ""

#: ../../docs/tutorials/3d/occlusion_culling.rst:242
msgid "Use the simplest possible occluder shapes"
msgstr ""

#: ../../docs/tutorials/3d/occlusion_culling.rst:244
msgid ""
"If you notice low performance or stuttering in complex 3D scenes, it may "
"mean that the CPU is overloaded as a result of rendering detailed occluders. "
"Select the OccluderInstance3D node, increase the **Bake > Simplification** "
"property then bake occluders again."
msgstr ""

#: ../../docs/tutorials/3d/occlusion_culling.rst:249
msgid ""
"Remember to keep the simplification value reasonable. Values that are too "
"high for the level's geometry may cause incorrect occlusion culling to "
"occur, as in :ref:`doc_occlusion_culling_troubleshooting_false_negative`."
msgstr ""

#: ../../docs/tutorials/3d/occlusion_culling.rst:253
msgid ""
"If this still doesn't lead to low enough CPU usage, you can try adjusting "
"the **Rendering > Occlusion Culling > BVH Build Quality** project setting "
"and/or decreasing **Rendering > Occlusion Culling > Occlusion Rays Per "
"Thread**. You'll need to enable the **Advanced** toggle in the Project "
"Settings dialog to see those settings."
msgstr ""

#: ../../docs/tutorials/3d/occlusion_culling.rst:264
msgid "My occludee isn't being culled when it should be"
msgstr ""

#: ../../docs/tutorials/3d/occlusion_culling.rst:266
msgid "**On the occluder side:**"
msgstr ""

#: ../../docs/tutorials/3d/occlusion_culling.rst:268
msgid ""
"First, double-check that the **Bake > Cull Mask** property in the "
"OccluderInstance3D is set to allow baking the meshes you'd like. The "
"visibility layer of the MeshInstance3D nodes must be present within the cull "
"mask for the mesh to be included in the bake."
msgstr ""

#: ../../docs/tutorials/3d/occlusion_culling.rst:273
msgid ""
"Also note that occluder baking only takes meshes with *opaque* materials "
"into account. Surfaces will *transparent* materials will **not** be included "
"in the bake, even if the texture applied on them is fully opaque."
msgstr ""

#: ../../docs/tutorials/3d/occlusion_culling.rst:277
msgid ""
"Lastly, remember that MultiMeshInstance3D, GPUParticles3D, CPUParticles3D "
"and CSG nodes are **not** taken into account when baking occluders. As a "
"workaround, you can add OccluderInstance3D nodes for those manually."
msgstr ""

#: ../../docs/tutorials/3d/occlusion_culling.rst:281
msgid "**On the occludee side:**"
msgstr ""

#: ../../docs/tutorials/3d/occlusion_culling.rst:283
msgid ""
"Make sure **Extra Cull Margin** is set as low as possible (it should usually "
"be ``0.0``), and that **Ignore Occlusion Culling** is disabled in the "
"object's GeometryInstance3D section."
msgstr ""

#: ../../docs/tutorials/3d/occlusion_culling.rst:287
msgid ""
"Also, check the AABB's size (which is represented by an orange box when "
"selecting the node). This axis-aligned bounding box must be *fully* occluded "
"by the occluder shapes for the occludee to be hidden."
msgstr ""

#: ../../docs/tutorials/3d/occlusion_culling.rst:294
msgid "My occludee is being culled when it shouldn't be"
msgstr ""

#: ../../docs/tutorials/3d/occlusion_culling.rst:296
msgid ""
"The most likely cause for this is that objects that were included in the "
"occluder bake have been moved after baking occluders. For instance, this can "
"occur when moving your level geometry around or rearranging its layout. To "
"fix this, select the OccluderInstance3D node and bake occluders again."
msgstr ""

#: ../../docs/tutorials/3d/occlusion_culling.rst:301
msgid ""
"This can also happen because dynamic objects were included in the bake, even "
"though they shouldn't be. Use the :ref:`occlusion culling debug draw mode "
"<doc_occlusion_culling_preview>` to look for occluder shapes that shouldn't "
"be present, then :ref:`adjust the bake cull mask accordingly "
"<doc_occlusion_culling_baking>`."
msgstr ""

#: ../../docs/tutorials/3d/occlusion_culling.rst:307
msgid ""
"The last possible cause for this is overly aggressive mesh simplification "
"during the occluder baking process. Select the OccluderInstance3D node, "
"decrease the **Bake > Simplification** property then bake occluders again."
msgstr ""

#: ../../docs/tutorials/3d/occlusion_culling.rst:311
msgid ""
"As a last resort, you can enable the **Ignore Occlusion Culling** property "
"on the occludee. This will negate the performance improvements of occlusion "
"culling for that object, but it makes sense to do this for objects that will "
"never be culled (such as a first-person view model)."
msgstr ""

#: ../../docs/tutorials/3d/resolution_scaling.rst:4
msgid "Resolution scaling"
msgstr ""

#: ../../docs/tutorials/3d/resolution_scaling.rst:10
msgid "Why use resolution scaling?"
msgstr ""

#: ../../docs/tutorials/3d/resolution_scaling.rst:12
msgid ""
"With the ever-increasing rendering complexity of modern games, rendering at "
"native resolution isn't always viable anymore, especially on lower-end GPUs."
msgstr ""

#: ../../docs/tutorials/3d/resolution_scaling.rst:15
msgid ""
"Resolution scaling is one of the most direct ways to influence the GPU "
"requirements of a scene. In scenes that are bottlenecked by the GPU (rather "
"than by the CPU), decreasing the resolution scale can improve performance "
"significantly. Resolution scaling is particularly important on mobile GPUs "
"where performance and power budgets are limited."
msgstr ""

#: ../../docs/tutorials/3d/resolution_scaling.rst:21
msgid ""
"While resolution scaling is an important tool to have, remember that "
"resolution scaling is not intended to be a replacement for decreasing "
"graphics settings on lower-end hardware. Consider exposing both resolution "
"scale and graphics settings in your in-game menus."
msgstr ""

#: ../../docs/tutorials/3d/resolution_scaling.rst:28
#, fuzzy
msgid ""
"You can compare resolution scaling modes and factors in action using the `3D "
"Antialiasing demo project <https://github.com/godotengine/godot-demo-"
"projects/tree/master/3d/antialiasing>`__."
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati različite Godo demo projekte "
"`Godot demo projects <https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/tutorials/3d/resolution_scaling.rst:33
msgid ""
"Resolution scaling is currently not available for 2D rendering, but it can "
"be simulated using the ``viewport`` stretch mode. See :ref:"
"`doc_multiple_resolutions` for more information."
msgstr ""

#: ../../docs/tutorials/3d/resolution_scaling.rst:38
msgid "Resolution scaling options"
msgstr ""

#: ../../docs/tutorials/3d/resolution_scaling.rst:40
msgid ""
"In the advanced Project Settings' **Rendering > Scaling 3D** section, you "
"can find several options for 3D resolution scaling:"
msgstr ""

#: ../../docs/tutorials/3d/resolution_scaling.rst:44
#, fuzzy
msgid "Scaling mode"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/3d/resolution_scaling.rst:46
msgid "**Bilinear:** Standard bilinear filtering (default)."
msgstr ""

#: ../../docs/tutorials/3d/resolution_scaling.rst:47
msgid ""
"**FSR 1.0:** `AMD FidelityFX Super Resolution 1.0 <https://gpuopen.com/"
"fidelityfx-superresolution/>`__. Slower, but higher quality compared to "
"bilinear scaling. On very slow GPUs, the cost of FSR1 may be too expensive "
"to be worth using it over bilinear scaling."
msgstr ""

#: ../../docs/tutorials/3d/resolution_scaling.rst:51
msgid ""
"**FSR 2.2:** AMD FidelityFX Super Resolution 2.2 (since Godot 4.2). Slowest, "
"but even higher quality compared to FSR1 and bilinear scaling. On slow GPUs, "
"the cost of FSR2 may be too expensive to be worth using it over bilinear "
"scaling or FSR1. To match FSR2 performance with FSR1, you need to use a "
"lower resolution scale factor."
msgstr ""

#: ../../docs/tutorials/3d/resolution_scaling.rst:57
msgid ""
"Here are comparison images between native resolution, bilinear scaling with "
"50% resolution scale, FSR1, and FSR2 scaling with 50% resolution scale:"
msgstr ""

#: ../../docs/tutorials/3d/resolution_scaling.rst:66
msgid ""
"FSR1 upscaling works best when coupled with another form of antialiasing. "
"Temporal antialiasing (TAA) or multisample antialiasing (MSAA) should "
"preferably be used in this case, as FXAA does not add temporal information "
"and introduces more blurring to the image."
msgstr ""

#: ../../docs/tutorials/3d/resolution_scaling.rst:71
msgid ""
"On the other hand, FSR2 provides its own temporal antialiasing. This means "
"you don't need to enable other antialiasing methods for the resulting image "
"to look smooth. The **Use TAA** project setting is ignored when FSR2 is used "
"as the 3D scaling method, since FSR2's temporal antialiasing takes priority."
msgstr ""

#: ../../docs/tutorials/3d/resolution_scaling.rst:76
msgid "Here's the same comparison, but with 4× MSAA enabled on all images:"
msgstr ""

#: ../../docs/tutorials/3d/resolution_scaling.rst:84
msgid ""
"Notice how the edge upscaling of FSR1 becomes much more convincing once 4× "
"MSAA is enabled. However, FSR2 doesn't benefit much from enabling MSAA since "
"it already performs temporal antialiasing."
msgstr ""

#: ../../docs/tutorials/3d/resolution_scaling.rst:89
msgid "Rendering scale"
msgstr ""

#: ../../docs/tutorials/3d/resolution_scaling.rst:91
msgid ""
"The **Rendering > Scaling 3D > Scale** setting adjusts the resolution scale. "
"``1.0`` represents the full resolution scale, with the 3D rendering "
"resolution matching the 2D rendering resolution. Resolution scales *below* "
"``1.0`` can be used to speed up rendering, at the cost of a blurrier final "
"image and more aliasing."
msgstr ""

#: ../../docs/tutorials/3d/resolution_scaling.rst:96
msgid ""
"The rendering scale can be adjusted at run-time by changing the "
"``scaling_3d_scale`` property on a :ref:`class_Viewport` node."
msgstr ""

#: ../../docs/tutorials/3d/resolution_scaling.rst:99
msgid ""
"Resolution scales *above* ``1.0`` can be used for supersample antialiasing "
"(SSAA). This will provide antialiasing at a *very* high performance cost, "
"and is **not recommended** for most use cases. See :ref:"
"`doc_3d_antialiasing` for more information."
msgstr ""

#: ../../docs/tutorials/3d/resolution_scaling.rst:104
msgid ""
"The tables below list common screen resolutions, the resulting 3D rendering "
"resolution and the number of megapixels that need to be rendered each frame "
"depending on the rendering scale option. Rows are sorted from fastest to "
"slowest in each table."
msgstr ""

#: ../../docs/tutorials/3d/resolution_scaling.rst:111
msgid ""
"The resolution scale is defined on a **per-axis** basis. For example, this "
"means that halving the resolution scale factor will reduce the number of "
"rendered megapixels per frame by a factor of 4, not 2. Therefore, very low "
"or very high resolution scale factors can have a greater performance impact "
"than expected."
msgstr ""

#: ../../docs/tutorials/3d/resolution_scaling.rst:117
msgid "**1920×1080 (Full HD)**"
msgstr ""

#: ../../docs/tutorials/3d/resolution_scaling.rst:120
#: ../../docs/tutorials/3d/resolution_scaling.rst:142
#: ../../docs/tutorials/3d/resolution_scaling.rst:164
msgid "Resolution scale factor"
msgstr ""

#: ../../docs/tutorials/3d/resolution_scaling.rst:120
#: ../../docs/tutorials/3d/resolution_scaling.rst:142
#: ../../docs/tutorials/3d/resolution_scaling.rst:164
msgid "3D rendering resolution"
msgstr ""

#: ../../docs/tutorials/3d/resolution_scaling.rst:120
#: ../../docs/tutorials/3d/resolution_scaling.rst:142
#: ../../docs/tutorials/3d/resolution_scaling.rst:164
msgid "Megapixels rendered per frame"
msgstr ""

#: ../../docs/tutorials/3d/resolution_scaling.rst:122
#: ../../docs/tutorials/3d/resolution_scaling.rst:144
#: ../../docs/tutorials/3d/resolution_scaling.rst:166
msgid "``0.50``"
msgstr ""

#: ../../docs/tutorials/3d/resolution_scaling.rst:122
msgid "960×540"
msgstr ""

#: ../../docs/tutorials/3d/resolution_scaling.rst:122
msgid "0.52 MPix"
msgstr ""

#: ../../docs/tutorials/3d/resolution_scaling.rst:124
#: ../../docs/tutorials/3d/resolution_scaling.rst:146
#: ../../docs/tutorials/3d/resolution_scaling.rst:168
msgid "``0.67``"
msgstr ""

#: ../../docs/tutorials/3d/resolution_scaling.rst:124
msgid "1286×723"
msgstr ""

#: ../../docs/tutorials/3d/resolution_scaling.rst:124
msgid "0.93 MPix"
msgstr ""

#: ../../docs/tutorials/3d/resolution_scaling.rst:126
#: ../../docs/tutorials/3d/resolution_scaling.rst:148
#: ../../docs/tutorials/3d/resolution_scaling.rst:170
msgid "``0.75``"
msgstr ""

#: ../../docs/tutorials/3d/resolution_scaling.rst:126
msgid "1440×810"
msgstr ""

#: ../../docs/tutorials/3d/resolution_scaling.rst:126
msgid "1.17 MPix"
msgstr ""

#: ../../docs/tutorials/3d/resolution_scaling.rst:128
#: ../../docs/tutorials/3d/resolution_scaling.rst:150
#: ../../docs/tutorials/3d/resolution_scaling.rst:172
msgid "``0.85``"
msgstr ""

#: ../../docs/tutorials/3d/resolution_scaling.rst:128
msgid "1632×918"
msgstr ""

#: ../../docs/tutorials/3d/resolution_scaling.rst:128
msgid "1.50 MPix"
msgstr ""

#: ../../docs/tutorials/3d/resolution_scaling.rst:130
#: ../../docs/tutorials/3d/resolution_scaling.rst:152
#: ../../docs/tutorials/3d/resolution_scaling.rst:174
msgid "``1.00`` **(native)**"
msgstr ""

#: ../../docs/tutorials/3d/resolution_scaling.rst:130
msgid "**1920×1080**"
msgstr ""

#: ../../docs/tutorials/3d/resolution_scaling.rst:130
msgid "**2.07 MPix**"
msgstr ""

#: ../../docs/tutorials/3d/resolution_scaling.rst:132
#: ../../docs/tutorials/3d/resolution_scaling.rst:154
#: ../../docs/tutorials/3d/resolution_scaling.rst:176
msgid "``1.33`` (supersampling)"
msgstr ""

#: ../../docs/tutorials/3d/resolution_scaling.rst:132
msgid "2553×1436"
msgstr ""

#: ../../docs/tutorials/3d/resolution_scaling.rst:132
msgid "3.67 MPix"
msgstr ""

#: ../../docs/tutorials/3d/resolution_scaling.rst:134
#: ../../docs/tutorials/3d/resolution_scaling.rst:156
#: ../../docs/tutorials/3d/resolution_scaling.rst:178
msgid "``1.50`` (supersampling)"
msgstr ""

#: ../../docs/tutorials/3d/resolution_scaling.rst:134
#: ../../docs/tutorials/3d/resolution_scaling.rst:170
msgid "2880×1620"
msgstr ""

#: ../../docs/tutorials/3d/resolution_scaling.rst:134
#: ../../docs/tutorials/3d/resolution_scaling.rst:170
msgid "4.67 MPix"
msgstr ""

#: ../../docs/tutorials/3d/resolution_scaling.rst:136
#: ../../docs/tutorials/3d/resolution_scaling.rst:158
#: ../../docs/tutorials/3d/resolution_scaling.rst:180
msgid "``2.00`` (supersampling)"
msgstr ""

#: ../../docs/tutorials/3d/resolution_scaling.rst:136
#: ../../docs/tutorials/3d/resolution_scaling.rst:156
msgid "3840×2160"
msgstr ""

#: ../../docs/tutorials/3d/resolution_scaling.rst:136
#: ../../docs/tutorials/3d/resolution_scaling.rst:156
msgid "8.29 MPix"
msgstr ""

#: ../../docs/tutorials/3d/resolution_scaling.rst:139
msgid "**2560×1440 (QHD)**"
msgstr ""

#: ../../docs/tutorials/3d/resolution_scaling.rst:144
msgid "1280×720"
msgstr ""

#: ../../docs/tutorials/3d/resolution_scaling.rst:144
msgid "0.92 MPix"
msgstr ""

#: ../../docs/tutorials/3d/resolution_scaling.rst:146
msgid "1715×964"
msgstr ""

#: ../../docs/tutorials/3d/resolution_scaling.rst:146
msgid "1.65 MPix"
msgstr ""

#: ../../docs/tutorials/3d/resolution_scaling.rst:148
#: ../../docs/tutorials/3d/resolution_scaling.rst:166
msgid "1920×1080"
msgstr ""

#: ../../docs/tutorials/3d/resolution_scaling.rst:148
#: ../../docs/tutorials/3d/resolution_scaling.rst:166
msgid "2.07 MPix"
msgstr ""

#: ../../docs/tutorials/3d/resolution_scaling.rst:150
msgid "2176×1224"
msgstr ""

#: ../../docs/tutorials/3d/resolution_scaling.rst:150
msgid "2.66 MPix"
msgstr ""

#: ../../docs/tutorials/3d/resolution_scaling.rst:152
msgid "**2560×1440**"
msgstr ""

#: ../../docs/tutorials/3d/resolution_scaling.rst:152
msgid "**3.69 MPix**"
msgstr ""

#: ../../docs/tutorials/3d/resolution_scaling.rst:154
msgid "3404×1915"
msgstr ""

#: ../../docs/tutorials/3d/resolution_scaling.rst:154
msgid "6.52 MPix"
msgstr ""

#: ../../docs/tutorials/3d/resolution_scaling.rst:158
msgid "5120×2880"
msgstr ""

#: ../../docs/tutorials/3d/resolution_scaling.rst:158
msgid "14.75 MPix"
msgstr ""

#: ../../docs/tutorials/3d/resolution_scaling.rst:161
msgid "**3840×2160 (Ultra HD \"4K\")**"
msgstr ""

#: ../../docs/tutorials/3d/resolution_scaling.rst:168
msgid "2572×1447"
msgstr ""

#: ../../docs/tutorials/3d/resolution_scaling.rst:168
msgid "3.72 MPix"
msgstr ""

#: ../../docs/tutorials/3d/resolution_scaling.rst:172
msgid "3264×1836"
msgstr ""

#: ../../docs/tutorials/3d/resolution_scaling.rst:172
msgid "5.99 MPix"
msgstr ""

#: ../../docs/tutorials/3d/resolution_scaling.rst:174
msgid "**3840×2160**"
msgstr ""

#: ../../docs/tutorials/3d/resolution_scaling.rst:174
msgid "**8.29 MPix**"
msgstr ""

#: ../../docs/tutorials/3d/resolution_scaling.rst:176
msgid "5107×2872"
msgstr ""

#: ../../docs/tutorials/3d/resolution_scaling.rst:176
msgid "14.67 MPix"
msgstr ""

#: ../../docs/tutorials/3d/resolution_scaling.rst:178
msgid "5760×3240"
msgstr ""

#: ../../docs/tutorials/3d/resolution_scaling.rst:178
msgid "18.66 MPix"
msgstr ""

#: ../../docs/tutorials/3d/resolution_scaling.rst:180
msgid "7680×4320"
msgstr ""

#: ../../docs/tutorials/3d/resolution_scaling.rst:180
msgid "33.18 MPix"
msgstr ""

#: ../../docs/tutorials/3d/resolution_scaling.rst:184
msgid "FSR Sharpness"
msgstr ""

#: ../../docs/tutorials/3d/resolution_scaling.rst:186
msgid ""
"When using the FSR1 or FSR2 scaling modes, the sharpness can be controlled "
"using the **Rendering > Scaling 3D > FSR Sharpness** advanced project "
"setting."
msgstr ""

#: ../../docs/tutorials/3d/resolution_scaling.rst:189
msgid ""
"The intensity is inverted compared to most other sharpness sliders: *lower* "
"values will result in a sharper final image, while *higher* values will "
"*reduce* the impact of the sharpening filter. ``0.0`` is the sharpest, while "
"``2.0`` is the least sharp. The default value of ``0.2`` provides a balance "
"between preserving the original image's sharpness and avoiding additional "
"aliasing due to oversharpening."
msgstr ""

#: ../../docs/tutorials/3d/resolution_scaling.rst:198
msgid ""
"If you wish to use sharpening when rendering at native resolution, Godot "
"currently doesn't allow using the sharpening component of FSR1 (RCAS) "
"independently from the upscaling component (EASU)."
msgstr ""

#: ../../docs/tutorials/3d/resolution_scaling.rst:202
msgid ""
"As a workaround, you can set the 3D rendering scale to ``0.99``, set the "
"scaling mode to **FSR 1.0** then adjust FSR sharpness as needed. This allows "
"using FSR1 while rendering at a near-native resolution."
msgstr ""

#: ../../docs/tutorials/3d/resolution_scaling.rst:206
msgid ""
"Alternatively, you can set the scaling mode to **FSR 2.2** with the 3D "
"rendering scale set to ``1.0`` if you have enough GPU headroom. This also "
"provides high-quality temporal antialiasing. The **FSR Sharpness** setting "
"remains functional in this case."
msgstr ""

#: ../../docs/tutorials/3d/resolution_scaling.rst:214
msgid "Mipmap bias"
msgstr ""

#: ../../docs/tutorials/3d/resolution_scaling.rst:216
msgid ""
"Godot automatically uses a negative texture mipmap bias when the 3D "
"resolution scale is set below ``1.0``. This allows for better preservation "
"of texture detail at the cost of a grainy appearance on detailed textures."
msgstr ""

#: ../../docs/tutorials/3d/resolution_scaling.rst:220
msgid ""
"The texture LOD bias currently affects both 2D and 3D rendering in the same "
"way. However, keep in mind it only has an effect on textures with mipmaps "
"enabled. Textures used in 2D don't have mipmaps enabled by default, which "
"means only 3D rendering is affected unless you enabled mipmaps on 2D "
"textures in the Import dock."
msgstr ""

#: ../../docs/tutorials/3d/resolution_scaling.rst:226
msgid ""
"The formula used to determine the texture mipmap bias is: "
"``log2f(min(scaling_3d_scale, 1.0)) + custom_texture_mipmap_bias``"
msgstr ""

#: ../../docs/tutorials/3d/resolution_scaling.rst:229
msgid ""
"To counteract the blurriness added by some antialiasing methods, Godot also "
"adds a ``-0.25`` offset when FXAA is enabled, and a ``-0.5`` offset when TAA "
"is enabled. If both are enabled at the same time, a ``-0.75`` offset is "
"used. This mipmap bias offset is applied *before* the resolution scaling "
"offset, so it does not change depending on resolution scale."
msgstr ""

#: ../../docs/tutorials/3d/resolution_scaling.rst:235
msgid ""
"The texture LOD bias can manually be changed by adjusting the **Rendering > "
"Textures > Default Filters > Texture Mipmap Bias** advanced project setting. "
"It can also be changed at run-time on :ref:`Viewports <class_Viewport>` by "
"adjusting the ``texture_mipmap_bias`` property."
msgstr ""

#: ../../docs/tutorials/3d/resolution_scaling.rst:242
msgid ""
"Adjusting the mipmap LOD bias manually can be useful in certain scenarios, "
"but this should be done carefully to prevent the final image from looking "
"grainy in motion."
msgstr ""

#: ../../docs/tutorials/3d/resolution_scaling.rst:246
msgid ""
"*Negative* mipmap LOD bias can also decrease performance due to higher-"
"resolution mips having to be sampled further away. Recommended values for a "
"manual offset are between ``-0.5`` and ``0.0``."
msgstr ""

#: ../../docs/tutorials/3d/resolution_scaling.rst:250
msgid ""
"*Positive* mipmap LOD bias will make mipmapped textures appear blurrier than "
"intended. This may improve performance slightly, but is otherwise not "
"recommended as the loss in visual quality is usually not worth the "
"performance gain."
msgstr ""

#: ../../docs/tutorials/3d/resolution_scaling.rst:255
msgid ""
"The example below shows an extreme case, with a mipmap LOD bias of ``-1.0`` "
"and anisotropic filtering disabled to make the difference more noticeable:"
msgstr ""

#: ../../docs/tutorials/3d/resolution_scaling.rst:264
msgid "Performance does not increase much when decreasing resolution scale"
msgstr ""

#: ../../docs/tutorials/3d/resolution_scaling.rst:266
msgid ""
"If performance doesn't increase much when decreasing resolution scale to a "
"value like ``0.5``, it likely means the performance bottleneck is elsewhere "
"in your scene. For example, your scene could have too many draw calls, "
"causing a CPU bottleneck to occur. Likewise, you may have too many graphics "
"effects enabled for your GPU to handle (such as SDFGI, SSAO or SSR)."
msgstr ""

#: ../../docs/tutorials/3d/resolution_scaling.rst:272
msgid "See the :ref:`doc_performance` tutorials for more information."
msgstr ""

#: ../../docs/tutorials/3d/variable_rate_shading.rst:4
msgid "Variable rate shading"
msgstr ""

#: ../../docs/tutorials/3d/variable_rate_shading.rst:7
msgid "What is variable rate shading?"
msgstr ""

#: ../../docs/tutorials/3d/variable_rate_shading.rst:9
msgid ""
"In modern 3D rendering engines, shaders are much more complex compared to "
"before. The advent of physically-based rendering, real-time global "
"illumination and screen-space effects has increased the number of *per-"
"pixel* shading that must be performed to render each frame. Additionally, "
"screen resolutions also have increased a lot, with 1440p and 4K now being "
"common target resolutions. As a result, the total shading cost in scene "
"rendering usually represents a significant amount of the time taken to "
"render each frame."
msgstr ""

#: ../../docs/tutorials/3d/variable_rate_shading.rst:17
msgid ""
"Variable rate shading (VRS) is a method of decreasing this shading cost by "
"reducing the resolution of *per-pixel* shading (also called *fragment* "
"shading), while keeping the original resolution for rendering geometry. This "
"means geometry edges remain as sharp as they would without VRS. VRS can be "
"combined with any :ref:`doc_3d_antialiasing` technique (MSAA, FXAA, TAA, "
"SSAA)."
msgstr ""

#: ../../docs/tutorials/3d/variable_rate_shading.rst:23
msgid ""
"VRS allows specifying the shading quality in a local manner, which makes it "
"possible to have certain parts of the viewport receive more detailed shading "
"than others. This is particularly useful in virtual reality (VR) to achieve "
"*foveated rendering*, where the center of the viewport is more detailed than "
"the edges."
msgstr ""

#: ../../docs/tutorials/3d/variable_rate_shading.rst:29
msgid ""
"Here's a scene rendered with rate shading disabled then enabled, using the "
"density map linked at the bottom of this page:"
msgstr ""

#: ../../docs/tutorials/3d/variable_rate_shading.rst:36
msgid "Variable rate shading disabled in textured scene"
msgstr ""

#: ../../docs/tutorials/3d/variable_rate_shading.rst:42
msgid ""
"Variable rate shading enabled in textured scene (lower quality but higher "
"performance)"
msgstr ""

#: ../../docs/tutorials/3d/variable_rate_shading.rst:44
msgid ""
"When used in scenes with low-frequency detail (such as scenes with a "
"stylized/low-poly aesthetic), it's possible to achieve similar performance "
"gains but with less reduction in visual quality:"
msgstr ""

#: ../../docs/tutorials/3d/variable_rate_shading.rst:52
msgid "Variable rate shading disabled in untextured scene"
msgstr ""

#: ../../docs/tutorials/3d/variable_rate_shading.rst:58
msgid ""
"Variable rate shading enabled in untextured scene (lower quality but higher "
"performance)"
msgstr ""

#: ../../docs/tutorials/3d/variable_rate_shading.rst:61
msgid "Hardware support"
msgstr ""

#: ../../docs/tutorials/3d/variable_rate_shading.rst:63
msgid "Variable rate shading is only supported on specific GPUs:"
msgstr ""

#: ../../docs/tutorials/3d/variable_rate_shading.rst:65
msgid "**Desktop:**"
msgstr ""

#: ../../docs/tutorials/3d/variable_rate_shading.rst:67
msgid "NVIDIA Turing and newer (including GTX 1600 series)"
msgstr ""

#: ../../docs/tutorials/3d/variable_rate_shading.rst:68
msgid ""
"AMD RDNA2 and newer (both integrated and dedicated GPUs – including Steam "
"Deck)"
msgstr ""

#: ../../docs/tutorials/3d/variable_rate_shading.rst:69
msgid "Intel Arc Alchemist and newer **(dedicated GPUs only)**"
msgstr ""

#: ../../docs/tutorials/3d/variable_rate_shading.rst:71
msgid "Intel integrated graphics do not support variable rate shading."
msgstr ""

#: ../../docs/tutorials/3d/variable_rate_shading.rst:73
msgid "**Mobile SoCs:**"
msgstr ""

#: ../../docs/tutorials/3d/variable_rate_shading.rst:75
msgid "Snapdragon 888 and newer"
msgstr ""

#: ../../docs/tutorials/3d/variable_rate_shading.rst:76
msgid "MediaTek Dimensity 9000 and newer"
msgstr ""

#: ../../docs/tutorials/3d/variable_rate_shading.rst:77
msgid "ARM Mali-G615 and newer"
msgstr ""

#: ../../docs/tutorials/3d/variable_rate_shading.rst:79
msgid ""
"As of January 2023, Apple and Raspberry Pi GPUs do not support variable rate "
"shading."
msgstr ""

#: ../../docs/tutorials/3d/variable_rate_shading.rst:82
msgid "Using variable rate shading in Godot"
msgstr ""

#: ../../docs/tutorials/3d/variable_rate_shading.rst:86
msgid ""
"Both Forward Plus and Forward Mobile rendering methods support variable rate "
"shading. VRS can be used in both pancake (non-XR) and XR display modes."
msgstr ""

#: ../../docs/tutorials/3d/variable_rate_shading.rst:89
msgid ""
"The Compatibility rendering method does **not** support variable rate "
"shading."
msgstr ""

#: ../../docs/tutorials/3d/variable_rate_shading.rst:92
msgid ""
"In the advanced Project Settings, the **Rendering > VRS** section offers "
"settings to control variable rate shading on the root viewport:"
msgstr ""

#: ../../docs/tutorials/3d/variable_rate_shading.rst:95
msgid ""
"**Mode:** Controls the variable rate shading mode. **Disabled** disables "
"variable rate shading. **Texture** uses a manually authored texture to set "
"shading density (see the property below). **XR** automatically generates a "
"texture suited for foveated rendering in virtual/augmented reality."
msgstr ""

#: ../../docs/tutorials/3d/variable_rate_shading.rst:99
msgid ""
"**Texture:** The texture to use to control shading density on the root "
"viewport. Only used if **Mode** is **Texture**."
msgstr ""

#: ../../docs/tutorials/3d/variable_rate_shading.rst:102
msgid ""
"For custom viewports, the VRS mode and texture must be set manually to the :"
"ref:`class_Viewport` node."
msgstr ""

#: ../../docs/tutorials/3d/variable_rate_shading.rst:107
msgid ""
"On unsupported hardware, there is no visual difference when variable rate "
"shading is enabled. You can check whether hardware supports variable rate "
"shading by running the editor or project with the ``--verbose`` :ref:"
"`command line argument <doc_command_line_tutorial>`."
msgstr ""

#: ../../docs/tutorials/3d/variable_rate_shading.rst:113
#, fuzzy
msgid "Creating a VRS density map"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/3d/variable_rate_shading.rst:115
msgid ""
"If using the **Texture** VRS mode, you *must* set a texture to be used as a "
"density map. Otherwise, no effect will be visible."
msgstr ""

#: ../../docs/tutorials/3d/variable_rate_shading.rst:118
msgid ""
"You can create your own VRS density map manually using an image editor, or "
"generate it using another method (e.g. on the CPU using the Image class, or "
"on the GPU using a shader). However, beware of performance implications when "
"generating a VRS image dynamically. If opting for dynamic generation, make "
"sure the VRS image generation process is fast enough to avoid outweighing "
"the performance gains from VRS."
msgstr ""

#: ../../docs/tutorials/3d/variable_rate_shading.rst:125
msgid "The texture must follow these rules:"
msgstr ""

#: ../../docs/tutorials/3d/variable_rate_shading.rst:127
msgid ""
"The texture *must* use a lossless compression format so that colors can be "
"matched precisely."
msgstr ""

#: ../../docs/tutorials/3d/variable_rate_shading.rst:129
msgid ""
"The following VRS densities are mapped to various colors, with brighter "
"colors representing a lower level of shading precision:"
msgstr ""

#: ../../docs/tutorials/3d/variable_rate_shading.rst:133
msgid "Density"
msgstr ""

#: ../../docs/tutorials/3d/variable_rate_shading.rst:135
msgid "1×1 (highest detail)"
msgstr ""

#: ../../docs/tutorials/3d/variable_rate_shading.rst:135
msgid "``rgb(0, 0, 0) - #000000``"
msgstr ""

#: ../../docs/tutorials/3d/variable_rate_shading.rst:137
msgid "1×2"
msgstr ""

#: ../../docs/tutorials/3d/variable_rate_shading.rst:137
msgid "``rgb(0, 85, 0) - #005500``"
msgstr ""

#: ../../docs/tutorials/3d/variable_rate_shading.rst:139
msgid "2×1"
msgstr ""

#: ../../docs/tutorials/3d/variable_rate_shading.rst:139
msgid "``rgb(85, 0, 0) - #550000``"
msgstr ""

#: ../../docs/tutorials/3d/variable_rate_shading.rst:141
msgid "2×2"
msgstr ""

#: ../../docs/tutorials/3d/variable_rate_shading.rst:141
msgid "``rgb(85, 85, 0) - #555500``"
msgstr ""

#: ../../docs/tutorials/3d/variable_rate_shading.rst:143
msgid "2×4"
msgstr ""

#: ../../docs/tutorials/3d/variable_rate_shading.rst:143
msgid "``rgb(85, 170, 0) - #55aa00``"
msgstr ""

#: ../../docs/tutorials/3d/variable_rate_shading.rst:145
msgid "4×2"
msgstr ""

#: ../../docs/tutorials/3d/variable_rate_shading.rst:145
msgid "``rgb(170, 85, 0) - #aa5500``"
msgstr ""

#: ../../docs/tutorials/3d/variable_rate_shading.rst:147
msgid "4×4"
msgstr ""

#: ../../docs/tutorials/3d/variable_rate_shading.rst:147
msgid "``rgb(170, 170, 0) - #aaaa00``"
msgstr ""

#: ../../docs/tutorials/3d/variable_rate_shading.rst:149
msgid "4×8"
msgstr ""

#: ../../docs/tutorials/3d/variable_rate_shading.rst:149
msgid "``rgb(170, 255, 0) - #aaff00``"
msgstr ""

#: ../../docs/tutorials/3d/variable_rate_shading.rst:149
#: ../../docs/tutorials/3d/variable_rate_shading.rst:151
#: ../../docs/tutorials/3d/variable_rate_shading.rst:153
msgid "Not supported on most hardware."
msgstr ""

#: ../../docs/tutorials/3d/variable_rate_shading.rst:151
msgid "8×4"
msgstr ""

#: ../../docs/tutorials/3d/variable_rate_shading.rst:151
msgid "``rgb(255, 170, 0) - #ffaa00``"
msgstr ""

#: ../../docs/tutorials/3d/variable_rate_shading.rst:153
msgid "8×8 (lowest detail)"
msgstr ""

#: ../../docs/tutorials/3d/variable_rate_shading.rst:153
msgid "``rgb(255, 255, 0) - #ffff00``"
msgstr ""

#: ../../docs/tutorials/3d/variable_rate_shading.rst:156
msgid ""
"For example, this VRS density texture provides the highest shading density "
"in the center of the viewport, and the lowest shading density in the corners:"
msgstr ""

#: ../../docs/tutorials/3d/variable_rate_shading.rst:163
msgid "Example VRS density map texture, simulating foveated rendering"
msgstr ""

#: ../../docs/tutorials/3d/variable_rate_shading.rst:165
msgid ""
"There are no size or aspect ratio requirements for the VRS density texture. "
"However, there is no benefit to using a VRS density map that is larger than "
"the viewport resolution divided by the GPU's *tile size*. The tile size is "
"what determines the smallest area of pixels where the shading density can be "
"changed separately from other tiles. On most GPUs, this tile size is 8×8 "
"pixels. You can view the tile size by running Godot with the ``--verbose`` "
"command line argument, as it's printed in the VRS debugging information."
msgstr ""

#: ../../docs/tutorials/3d/variable_rate_shading.rst:173
msgid ""
"Therefore, sticking to a relatively low resolution such as 256×256 (square) "
"or 480×270 (16:9) is recommended. Depending on your use cases, a square "
"texture may be more suited compared to a texture that matches the most "
"common viewport aspect ratio in your project (such as 16:9)."
msgstr ""

#: ../../docs/tutorials/3d/variable_rate_shading.rst:180
msgid ""
"When using variable rate shading, you can use a negative :ref:`texture "
"mipmap LOD bias <doc_resolution_scaling_mipmap_bias>` to reduce blurriness "
"in areas with reduced shading rate."
msgstr ""

#: ../../docs/tutorials/3d/variable_rate_shading.rst:184
msgid ""
"Note that the texture LOD bias is set globally, so this will also affect "
"areas of the viewport with full shading rate. Don't use values that are too "
"low, or textures will appear grainy."
msgstr ""

#: ../../docs/tutorials/3d/variable_rate_shading.rst:189
msgid "Performance comparison"
msgstr ""

#: ../../docs/tutorials/3d/variable_rate_shading.rst:191
msgid ""
"To give an idea of how much VRS can improve performance in theory, here's a "
"performance comparison with the textured example scene shown at the top of "
"this page. The VRS density map example present on this page is used."
msgstr ""

#: ../../docs/tutorials/3d/variable_rate_shading.rst:195
msgid ""
"Results were captured on a GeForce RTX 4090 with the NVIDIA 525.60.11 driver."
msgstr ""

#: ../../docs/tutorials/3d/variable_rate_shading.rst:198
msgid "Resolution"
msgstr ""

#: ../../docs/tutorials/3d/variable_rate_shading.rst:198
msgid "VRS disabled"
msgstr ""

#: ../../docs/tutorials/3d/variable_rate_shading.rst:198
msgid "VRS enabled"
msgstr ""

#: ../../docs/tutorials/3d/variable_rate_shading.rst:198
msgid "Performance improvement"
msgstr ""

#: ../../docs/tutorials/3d/variable_rate_shading.rst:200
msgid "1920×1080 (Full HD)"
msgstr ""

#: ../../docs/tutorials/3d/variable_rate_shading.rst:200
msgid "2832 FPS"
msgstr ""

#: ../../docs/tutorials/3d/variable_rate_shading.rst:200
msgid "3136 FPS"
msgstr ""

#: ../../docs/tutorials/3d/variable_rate_shading.rst:200
msgid "+10.7%"
msgstr ""

#: ../../docs/tutorials/3d/variable_rate_shading.rst:202
msgid "2560×1440 (QHD)"
msgstr ""

#: ../../docs/tutorials/3d/variable_rate_shading.rst:202
msgid "2008 FPS"
msgstr ""

#: ../../docs/tutorials/3d/variable_rate_shading.rst:202
msgid "2256 FPS"
msgstr ""

#: ../../docs/tutorials/3d/variable_rate_shading.rst:202
msgid "+12.3%"
msgstr ""

#: ../../docs/tutorials/3d/variable_rate_shading.rst:204
msgid "3840×2160 (4K)"
msgstr ""

#: ../../docs/tutorials/3d/variable_rate_shading.rst:204
msgid "1236 FPS"
msgstr ""

#: ../../docs/tutorials/3d/variable_rate_shading.rst:204
msgid "1436 FPS"
msgstr ""

#: ../../docs/tutorials/3d/variable_rate_shading.rst:204
msgid "+16.2%"
msgstr ""

#: ../../docs/tutorials/3d/variable_rate_shading.rst:206
msgid "7680×4320 (8K)"
msgstr ""

#: ../../docs/tutorials/3d/variable_rate_shading.rst:206
msgid "384 FPS"
msgstr ""

#: ../../docs/tutorials/3d/variable_rate_shading.rst:206
msgid "473 FPS"
msgstr ""

#: ../../docs/tutorials/3d/variable_rate_shading.rst:206
msgid "+23.1%"
msgstr ""

#: ../../docs/tutorials/3d/variable_rate_shading.rst:209
msgid ""
"In terms of performance improvements, variable rate shading is more "
"beneficial at higher target resolutions. The reduction in visual quality is "
"also less noticeable at high resolutions."
msgstr ""

#: ../../docs/tutorials/3d/variable_rate_shading.rst:215
msgid ""
"For non-VR games, you will probably have to use a less aggressive VRS "
"texture than what was used in this example. As a result, the effective "
"performance gains will be lower."
msgstr ""

#: ../../docs/tutorials/3d/csg_tools.rst:6
msgid "Prototyping levels with CSG"
msgstr ""

#: ../../docs/tutorials/3d/csg_tools.rst:8
msgid ""
"CSG stands for **Constructive Solid Geometry**, and is a tool to combine "
"basic shapes or custom meshes to create more complex shapes. In 3D modeling "
"software, CSG is mostly known as \"Boolean Operators\"."
msgstr ""

#: ../../docs/tutorials/3d/csg_tools.rst:12
msgid ""
"Level prototyping is one of the main uses of CSG in Godot. This technique "
"allows users to create the most common shapes by combining primitives. "
"Interior environments can be created by using inverted primitives."
msgstr ""

#: ../../docs/tutorials/3d/csg_tools.rst:16
msgid ""
"The CSG nodes in Godot are mainly intended for prototyping. There is no "
"built-in support for UV mapping or editing 3D polygons (though extruded 2D "
"polygons can be used with the CSGPolygon3D node)."
msgstr ""

#: ../../docs/tutorials/3d/csg_tools.rst:20
msgid ""
"If you're looking for an easy to use level design tool for a project, you "
"may want to use `Qodot <https://github.com/QodotPlugin/Qodot>`__ instead. It "
"lets you design levels using `TrenchBroom <https://kristianduske.com/"
"trenchbroom/>`__ and import them in Godot."
msgstr ""

#: ../../docs/tutorials/3d/csg_tools.rst:30
#, fuzzy
msgid ""
"You can check how to use CSG nodes to build various shapes (such as stairs "
"or roads) using the `Constructive Solid Geometry demo project <https://"
"github.com/godotengine/godot-demo-projects/tree/master/3d/csg>`__."
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati različite Godo demo projekte "
"`Godot demo projects <https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/tutorials/3d/csg_tools.rst:34
#, fuzzy
msgid "Introduction to CSG nodes"
msgstr "Uvod"

#: ../../docs/tutorials/3d/csg_tools.rst:36
msgid ""
"Like other features of Godot, CSG is supported in the form of nodes. These "
"are the CSG nodes:"
msgstr ""

#: ../../docs/tutorials/3d/csg_tools.rst:39
#, fuzzy
msgid ":ref:`CSGBox3D <class_CSGBox3D>`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/3d/csg_tools.rst:40
msgid ":ref:`CSGCylinder3D <class_CSGCylinder3D>` (also supports cone)"
msgstr ""

#: ../../docs/tutorials/3d/csg_tools.rst:41
msgid ":ref:`CSGSphere3D <class_CSGSphere3D>`"
msgstr ""

#: ../../docs/tutorials/3d/csg_tools.rst:42
msgid ":ref:`CSGTorus3D <class_CSGTorus3D>`"
msgstr ""

#: ../../docs/tutorials/3d/csg_tools.rst:43
#, fuzzy
msgid ":ref:`CSGPolygon3D <class_CSGPolygon3D>`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/3d/csg_tools.rst:44
msgid ":ref:`CSGMesh3D <class_CSGMesh3D>`"
msgstr ""

#: ../../docs/tutorials/3d/csg_tools.rst:45
#, fuzzy
msgid ":ref:`CSGCombiner3D <class_CSGCombiner3D>`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/3d/csg_tools.rst:52
msgid "CSG tools features"
msgstr ""

#: ../../docs/tutorials/3d/csg_tools.rst:54
msgid "Every CSG node supports 3 kinds of boolean operations:"
msgstr ""

#: ../../docs/tutorials/3d/csg_tools.rst:56
msgid ""
"**Union:** Geometry of both primitives is merged, intersecting geometry is "
"removed."
msgstr ""

#: ../../docs/tutorials/3d/csg_tools.rst:58
msgid ""
"**Intersection:** Only intersecting geometry remains, the rest is removed."
msgstr ""

#: ../../docs/tutorials/3d/csg_tools.rst:59
msgid ""
"**Subtraction:** The second shape is subtracted from the first, leaving a "
"dent with its shape."
msgstr ""

#: ../../docs/tutorials/3d/csg_tools.rst:67
msgid "CSGPolygon"
msgstr ""

#: ../../docs/tutorials/3d/csg_tools.rst:69
msgid ""
"The :ref:`CSGPolygon3D <class_CSGPolygon3D>` node extrude along a Polygon "
"drawn in 2D (in X, Y coordinates) in the following ways:"
msgstr ""

#: ../../docs/tutorials/3d/csg_tools.rst:72
msgid "**Depth:** Extruded back a given amount."
msgstr ""

#: ../../docs/tutorials/3d/csg_tools.rst:73
msgid "**Spin:** Extruded while spinning around its origin."
msgstr ""

#: ../../docs/tutorials/3d/csg_tools.rst:74
msgid ""
"**Path:** Extruded along a Path node. This operation is commonly called "
"lofting."
msgstr ""

#: ../../docs/tutorials/3d/csg_tools.rst:81
msgid ""
"The **Path** mode must be provided with a :ref:`Path3D <class_Path3D>` node "
"to work. In the Path node, draw the path and the polygon in CSGPolygon3D "
"will extrude along the given path."
msgstr ""

#: ../../docs/tutorials/3d/csg_tools.rst:87
msgid "Custom meshes"
msgstr ""

#: ../../docs/tutorials/3d/csg_tools.rst:89
msgid ""
"Any mesh can be used for :ref:`CSGMesh3D <class_CSGMesh3D>`; the mesh can be "
"modeled in other software and imported into Godot. Multiple materials are "
"supported. There are some restrictions for geometry:"
msgstr ""

#: ../../docs/tutorials/3d/csg_tools.rst:93
msgid "it must be closed,"
msgstr ""

#: ../../docs/tutorials/3d/csg_tools.rst:94
msgid "it must not self-intersect,"
msgstr ""

#: ../../docs/tutorials/3d/csg_tools.rst:95
msgid "it must not contain internal faces,"
msgstr ""

#: ../../docs/tutorials/3d/csg_tools.rst:96
msgid "every edge must connect to only two other faces."
msgstr ""

#: ../../docs/tutorials/3d/csg_tools.rst:101
msgid "CSGCombiner3D"
msgstr ""

#: ../../docs/tutorials/3d/csg_tools.rst:103
msgid ""
"The :ref:`CSGCombiner3D <class_CSGCombiner3D>` node is an empty shape used "
"for organization. It will only combine children nodes."
msgstr ""

#: ../../docs/tutorials/3d/csg_tools.rst:107
msgid "Processing order"
msgstr ""

#: ../../docs/tutorials/3d/csg_tools.rst:109
msgid ""
"Every CSG node will first process its children nodes and their operations: "
"union, intersection, or subtraction, in tree order, and apply them to itself "
"one after the other."
msgstr ""

#: ../../docs/tutorials/3d/csg_tools.rst:113
msgid ""
"In the interest of performance, make sure CSG geometry remains relatively "
"simple, as complex meshes can take a while to process. If adding objects "
"together (such as table and room objects), create them as separate CSG "
"trees. Forcing too many objects in a single tree will eventually start "
"affecting performance. Only use binary operations where you actually need "
"them."
msgstr ""

#: ../../docs/tutorials/3d/csg_tools.rst:121
msgid "Prototyping a level"
msgstr ""

#: ../../docs/tutorials/3d/csg_tools.rst:123
msgid "We will prototype a room to practice the use of CSG tools."
msgstr ""

#: ../../docs/tutorials/3d/csg_tools.rst:125
msgid ""
"Working in **Orthogonal** projection gives a better view when combining the "
"CSG shapes."
msgstr ""

#: ../../docs/tutorials/3d/csg_tools.rst:128
msgid "Our level will contain these objects:"
msgstr ""

#: ../../docs/tutorials/3d/csg_tools.rst:130
msgid "a room,"
msgstr ""

#: ../../docs/tutorials/3d/csg_tools.rst:131
msgid "a bed,"
msgstr ""

#: ../../docs/tutorials/3d/csg_tools.rst:132
msgid "a lamp,"
msgstr ""

#: ../../docs/tutorials/3d/csg_tools.rst:133
msgid "a desk,"
msgstr ""

#: ../../docs/tutorials/3d/csg_tools.rst:134
msgid "a bookshelf."
msgstr ""

#: ../../docs/tutorials/3d/csg_tools.rst:136
msgid "Create a scene with a Node3D node as root node."
msgstr ""

#: ../../docs/tutorials/3d/csg_tools.rst:138
msgid ""
"The default lighting of the environment doesn't provide clear shading at "
"some angles. Change the display mode using **Display Overdraw** in the 3D "
"viewport menu, or add a DirectionalLight node to help you see clearly."
msgstr ""

#: ../../docs/tutorials/3d/csg_tools.rst:145
msgid ""
"Create a CSGBox3D and name it ``room``, enable **Invert Faces** and change "
"the dimensions of your room."
msgstr ""

#: ../../docs/tutorials/3d/csg_tools.rst:152
msgid "Next, create a CSGCombiner3D and name it ``desk``."
msgstr ""

#: ../../docs/tutorials/3d/csg_tools.rst:154
msgid "A desk has one surface and 4 legs:"
msgstr ""

#: ../../docs/tutorials/3d/csg_tools.rst:156
msgid ""
"Create 1 CSGBox3D children node in **Union** mode for the surface and adjust "
"the dimensions."
msgstr ""

#: ../../docs/tutorials/3d/csg_tools.rst:158
msgid ""
"Create 4 CSGBox3D children nodes in **Union** mode for the legs and adjust "
"the dimensions."
msgstr ""

#: ../../docs/tutorials/3d/csg_tools.rst:161
msgid "Adjust their placement to resemble a desk."
msgstr ""

#: ../../docs/tutorials/3d/csg_tools.rst:165
msgid ""
"CSG nodes inside a CSGCombiner3D will only process their operation within "
"the combiner. Therefore, CSGCombiner3Ds are used to organize CSG nodes."
msgstr ""

#: ../../docs/tutorials/3d/csg_tools.rst:169
msgid "Create a CSGCombiner3D and name it ``bed``."
msgstr ""

#: ../../docs/tutorials/3d/csg_tools.rst:171
msgid ""
"Our bed consists of 3 parts: the bed, the mattress and a pillow. Create a "
"CSGBox3D and adjust its dimension for the bed. Create another CSGBox3D and "
"adjust its dimension for the mattress."
msgstr ""

#: ../../docs/tutorials/3d/csg_tools.rst:177
msgid ""
"We will create another CSGCombiner3D named ``pillow`` as the child of  "
"``bed``. The scene tree should look like this:"
msgstr ""

#: ../../docs/tutorials/3d/csg_tools.rst:182
msgid ""
"We will combine 3 CSGSphere3D nodes in **Union** mode to form a pillow. "
"Scale the Y axis of the spheres and enable **Smooth Faces**."
msgstr ""

#: ../../docs/tutorials/3d/csg_tools.rst:187
msgid ""
"Select the ``pillow`` node and switch the mode to **Subtraction**; the "
"combined spheres will cut a hole into the mattress."
msgstr ""

#: ../../docs/tutorials/3d/csg_tools.rst:192
msgid ""
"Try to re-parent the ``pillow`` node to the root ``Node3D`` node; the hole "
"will disappear."
msgstr ""

#: ../../docs/tutorials/3d/csg_tools.rst:195
msgid ""
"This is to illustrate the effect of CSG processing order. Since the root "
"node is not a CSG node, the CSGCombiner3D nodes are the end of the "
"operations; this shows the use of CSGCombiner3D to organize the CSG scene."
msgstr ""

#: ../../docs/tutorials/3d/csg_tools.rst:200
msgid ""
"Undo the re-parent after observing the effect. The bed you've built should "
"look like this:"
msgstr ""

#: ../../docs/tutorials/3d/csg_tools.rst:205
msgid "Create a CSGCombiner3D and name it ``lamp``."
msgstr ""

#: ../../docs/tutorials/3d/csg_tools.rst:207
msgid ""
"A lamp consists of 3 parts: the stand, the pole and the lampshade. Create a "
"CSGCylinder3D, enable the **Cone** option and make it the stand. Create "
"another CSGCylinder3D and adjust the dimensions to use it as a pole."
msgstr ""

#: ../../docs/tutorials/3d/csg_tools.rst:213
msgid ""
"We will use a CSGPolygon3D for the lampshade. Use the **Spin** mode for the "
"CSGPolygon3D and draw a `trapezoid <https://en.wikipedia.org/wiki/"
"Trapezoid>`_ while in **Front View** (numeric keypad 1); this shape will "
"extrude around the origin and form the lampshade."
msgstr ""

#: ../../docs/tutorials/3d/csg_tools.rst:224
msgid "Adjust the placement of the 3 parts to make it look like a lamp."
msgstr ""

#: ../../docs/tutorials/3d/csg_tools.rst:228
msgid "Create a CSGCombiner3D and name it ``bookshelf``."
msgstr ""

#: ../../docs/tutorials/3d/csg_tools.rst:230
msgid ""
"We will use 3 CSGBox3D nodes for the bookshelf. Create a CSGBox3D and adjust "
"its dimensions; this will be the size of the bookshelf."
msgstr ""

#: ../../docs/tutorials/3d/csg_tools.rst:235
msgid ""
"Duplicate the CSGBox3D and shorten the dimensions of each axis and change "
"the mode to **Subtraction**."
msgstr ""

#: ../../docs/tutorials/3d/csg_tools.rst:242
msgid ""
"You've almost built a shelf. Create one more CSGBox3D for dividing the shelf "
"into two levels."
msgstr ""

#: ../../docs/tutorials/3d/csg_tools.rst:247
msgid ""
"Position your furniture in your room as you like and your scene should look "
"this:"
msgstr ""

#: ../../docs/tutorials/3d/csg_tools.rst:252
msgid ""
"You've successfully prototyped a room level with the CSG tools in Godot. CSG "
"tools can be used for designing all kinds of levels, such as a maze or a "
"city; explore its limitations when designing your game."
msgstr ""

#: ../../docs/tutorials/3d/csg_tools.rst:257
msgid "Using prototype textures"
msgstr ""

#: ../../docs/tutorials/3d/csg_tools.rst:259
msgid ""
"Godot's :ref:`doc_standard_material_3d` supports *triplanar mapping*, which "
"can be used to automatically apply a texture to arbitrary objects without "
"distortion. This is handy when using CSG as Godot doesn't support editing UV "
"maps on CSG nodes yet. Triplanar mapping is relatively slow, which usually "
"restricts its usage to organic surfaces like terrain. Still, when "
"prototyping, it can be used to quickly apply textures to CSG-based levels."
msgstr ""

#: ../../docs/tutorials/3d/csg_tools.rst:266
msgid ""
"If you need some textures for prototyping, Kenney made a `set of CC0-"
"licensed prototype textures <https://kenney.nl/assets/prototype-textures>`__."
msgstr ""

#: ../../docs/tutorials/3d/csg_tools.rst:269
#, fuzzy
msgid "There are two ways to apply a material to a CSG node:"
msgstr "Ne postoje ograničenja prilikom korištenja Godot-a"

#: ../../docs/tutorials/3d/csg_tools.rst:271
msgid ""
"Applying it to a CSGCombiner3D node as a material override (**Geometry > "
"Material Override** in the Inspector). This will affect its children "
"automatically, but will make it impossible to change the material in "
"individual children."
msgstr ""

#: ../../docs/tutorials/3d/csg_tools.rst:275
msgid ""
"Applying a material to individual nodes (**Material** in the Inspector). "
"This way, each CSG node can have its own appearance. Subtractive CSG nodes "
"will apply their material to the nodes they're \"digging\" into."
msgstr ""

#: ../../docs/tutorials/3d/csg_tools.rst:279
msgid ""
"To apply triplanar mapping to a CSG node, select it, go to the Inspector, "
"click the **[empty]** text next to **Material Override** (or **Material** "
"for individual CSG nodes). Choose **New StandardMaterial3D**. Click the "
"newly created material's icon to edit it. Unfold the **Albedo** section and "
"load a texture into the **Texture** property. Now, unfold the **Uv1** "
"section and check **Triplanar**. You can change the texture offset and scale "
"on each axis by playing with the **Scale** and **Offset** properties just "
"above. Higher values in the **Scale** property will cause the texture to "
"repeat more often."
msgstr ""

#: ../../docs/tutorials/3d/csg_tools.rst:288
msgid ""
"You can copy a StandardMaterial3D to reuse it across CSG nodes. To do so, "
"click the dropdown arrow next to a material property in the Inspector and "
"choose **Copy**. To paste it, select the node you'd like to apply the "
"material onto, click the dropdown arrow next to its material property then "
"choose **Paste**."
msgstr ""

#: ../../docs/tutorials/3d/csg_tools.rst:295
#, fuzzy
msgid "Exporting as glTF"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/3d/csg_tools.rst:297
msgid ""
"It can be useful to block out a level using CSG, then export it as a 3d "
"model, to import into 3D modeling software. You can do this by selecting "
"**Scene > Export As... > glTF 2.0 Scene**."
msgstr ""

#: ../../docs/tutorials/3d/using_gridmaps.rst:4
msgid "Using GridMaps"
msgstr ""

#: ../../docs/tutorials/3d/using_gridmaps.rst:9
msgid ""
":ref:`Gridmaps <class_GridMap>` are a tool for creating 3D game levels, "
"similar to the way :ref:`TileMap <doc_using_tilemaps>` works in 2D. You "
"start with a predefined collection of 3D meshes (a :ref:`class_MeshLibrary`) "
"that can be placed on a grid, as if you were building a level with an "
"unlimited amount of Lego blocks."
msgstr ""

#: ../../docs/tutorials/3d/using_gridmaps.rst:15
msgid ""
"Collisions and navigation can also be added to the meshes, just like you "
"would do with the tiles of a tilemap."
msgstr ""

#: ../../docs/tutorials/3d/using_gridmaps.rst:19
msgid "Example project"
msgstr ""

#: ../../docs/tutorials/3d/using_gridmaps.rst:21
#, fuzzy
msgid ""
"To learn how GridMaps work, start by downloading the sample project: "
"`gridmap_starter.zip <https://github.com/godotengine/godot-docs-project-"
"starters/releases/download/latest-4.x/gridmap_starter.zip>`_."
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati različite Godo demo projekte "
"`Godot demo projects <https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/tutorials/3d/using_gridmaps.rst:24
msgid ""
"Unzip this project and add it to the Project Manager using the \"Import\" "
"button."
msgstr ""

#: ../../docs/tutorials/3d/using_gridmaps.rst:28
msgid "Creating a MeshLibrary"
msgstr ""

#: ../../docs/tutorials/3d/using_gridmaps.rst:30
msgid ""
"To begin, you need a :ref:`class_MeshLibrary`, which is a collection of "
"individual meshes that can be used in the gridmap. Open the "
"\"mesh_library_source.tscn\" scene to see an example of how to set up the "
"mesh library."
msgstr ""

#: ../../docs/tutorials/3d/using_gridmaps.rst:36
msgid ""
"As you can see, this scene has a :ref:`class_Node3D` node as its root, and a "
"number of :ref:`class_MeshInstance3D` node children."
msgstr ""

#: ../../docs/tutorials/3d/using_gridmaps.rst:39
msgid ""
"If you don't need any physics in your scene, then you're done. However, in "
"most cases you'll want to assign collision bodies to the meshes."
msgstr ""

#: ../../docs/tutorials/3d/using_gridmaps.rst:43
msgid "Collisions"
msgstr ""

#: ../../docs/tutorials/3d/using_gridmaps.rst:45
msgid ""
"You can manually assign a :ref:`class_StaticBody3D` and :ref:"
"`class_CollisionShape3D` to each mesh. Alternatively, you can use the "
"\"Mesh\" menu to automatically create the collision body based on the mesh "
"data."
msgstr ""

#: ../../docs/tutorials/3d/using_gridmaps.rst:51
msgid ""
"Note that a \"Convex\" collision body will work better for simple meshes. "
"For more complex shapes, select \"Create Trimesh Static Body\". Once each "
"mesh has a physics body and collision shape assigned, your mesh library is "
"ready to be used."
msgstr ""

#: ../../docs/tutorials/3d/using_gridmaps.rst:60
#: ../../docs/tutorials/assets_pipeline/escn_exporter/material.rst:2
msgid "Materials"
msgstr ""

#: ../../docs/tutorials/3d/using_gridmaps.rst:62
msgid ""
"Only the materials from within the meshes are used when generating the mesh "
"library. Materials set on the node will be ignored."
msgstr ""

#: ../../docs/tutorials/3d/using_gridmaps.rst:66
msgid "NavigationMeshes"
msgstr ""

#: ../../docs/tutorials/3d/using_gridmaps.rst:68
msgid ""
"Like all mesh instances, MeshLibrary items can be assigned a :ref:"
"`class_NavigationMesh` resource, which can be created manually, or baked as "
"described below."
msgstr ""

#: ../../docs/tutorials/3d/using_gridmaps.rst:71
msgid ""
"To create the NavigationMesh from a MeshLibrary scene export, place a :ref:"
"`class_NavigationRegion3D` child node below the main MeshInstance3D for the "
"GridMap item. Add a valid NavigationMesh resource to the NavigationRegion3D "
"and some source geometry nodes below and bake the NavigationMesh."
msgstr ""

#: ../../docs/tutorials/3d/using_gridmaps.rst:78
msgid ""
"With small grid cells it is often necessary to reduce the NavigationMesh "
"properties for agent radius and region minimum size."
msgstr ""

#: ../../docs/tutorials/3d/using_gridmaps.rst:83
msgid ""
"Nodes below the NavigationRegion3D are ignored for the MeshLibrary scene "
"export, so additional nodes can be added as source geometry just for baking "
"the navmesh."
msgstr ""

#: ../../docs/tutorials/3d/using_gridmaps.rst:88
msgid ""
"The baked cell size of the NavigationMesh must match the NavigationServer "
"map cell size to properly merge the navigation meshes of different grid "
"cells."
msgstr ""

#: ../../docs/tutorials/3d/using_gridmaps.rst:92
msgid "Exporting the MeshLibrary"
msgstr ""

#: ../../docs/tutorials/3d/using_gridmaps.rst:94
msgid ""
"To export the library, click on **Scene > Export As... > MeshLibrary...**, "
"and save it as a resource."
msgstr ""

#: ../../docs/tutorials/3d/using_gridmaps.rst:99
msgid ""
"You can find an already exported MeshLibrary in the project named "
"\"MeshLibrary.tres\"."
msgstr ""

#: ../../docs/tutorials/3d/using_gridmaps.rst:102
msgid "Using GridMap"
msgstr ""

#: ../../docs/tutorials/3d/using_gridmaps.rst:104
msgid ""
"Create a new scene and add a GridMap node. Add the mesh library by dragging "
"the resource file from the FileSystem dock and dropping it in the \"Theme\" "
"property in the Inspector."
msgstr ""

#: ../../docs/tutorials/3d/using_gridmaps.rst:110
msgid ""
"The \"Cell/Size\" property should be set to the size of your meshes. You can "
"leave it at the default value for the demo. Set the \"Center Y\" property to "
"\"Off\"."
msgstr ""

#: ../../docs/tutorials/3d/using_gridmaps.rst:113
msgid ""
"Now you can start designing the level by choosing a tile from the palette "
"and placing it with Left-Click in the editor window. Use Right-click to "
"remove a tile."
msgstr ""

#: ../../docs/tutorials/3d/using_gridmaps.rst:116
msgid ""
"Use the arrows next to the \"GridMap\" menu to change the floor that you are "
"working on."
msgstr ""

#: ../../docs/tutorials/3d/using_gridmaps.rst:118
msgid ""
"Click on the \"GridMap\" menu to see options and shortcuts. For example, "
"pressing :kbd:`S` rotates a tile around the y-axis."
msgstr ""

#: ../../docs/tutorials/3d/using_gridmaps.rst:123
msgid ""
"Holding :kbd:`Shift` and dragging with the left mouse button will draw a "
"selection box. You can duplicate or clear the selected area using the "
"respective menu options."
msgstr ""

#: ../../docs/tutorials/3d/using_gridmaps.rst:129
msgid ""
"In the menu, you can also change the axis you're drawing on, as well as "
"shift the drawing plane higher or lower on its axis."
msgstr ""

#: ../../docs/tutorials/3d/using_gridmaps.rst:135
msgid "Using GridMap in code"
msgstr ""

#: ../../docs/tutorials/3d/using_gridmaps.rst:137
msgid ""
"See :ref:`class_GridMap` for details on the node's methods and member "
"variables."
msgstr ""

#: ../../docs/tutorials/animation/index.rst:4
msgid ""
"This section of the tutorial covers using the two animation nodes in Godot "
"and the animation editor."
msgstr ""

#: ../../docs/tutorials/animation/index.rst:19
msgid ""
"See :ref:`doc_importing_3d_scenes` for information on importing animations "
"from a 3D model."
msgstr ""

#: ../../docs/tutorials/animation/introduction.rst:4
#, fuzzy
msgid "Introduction to the animation features"
msgstr "Uvod"

#: ../../docs/tutorials/animation/introduction.rst:6
msgid ""
"The :ref:`class_AnimationPlayer` node allows you to create anything from "
"simple to complex animations."
msgstr ""

#: ../../docs/tutorials/animation/introduction.rst:9
msgid "In this guide you learn to:"
msgstr ""

#: ../../docs/tutorials/animation/introduction.rst:11
msgid "Work with the Animation Panel"
msgstr ""

#: ../../docs/tutorials/animation/introduction.rst:12
msgid "Animate any property of any node"
msgstr ""

#: ../../docs/tutorials/animation/introduction.rst:13
msgid "Create a simple animation"
msgstr ""

#: ../../docs/tutorials/animation/introduction.rst:15
msgid ""
"In Godot, you can animate anything available in the Inspector, such as Node "
"transforms, sprites, UI elements, particles, visibility and color of "
"materials, and so on. You can also modify values of script variables and "
"even call functions."
msgstr ""

#: ../../docs/tutorials/animation/introduction.rst:21
msgid "Create an AnimationPlayer node"
msgstr ""

#: ../../docs/tutorials/animation/introduction.rst:23
msgid ""
"To use the animation tools we first have to create an :ref:"
"`class_AnimationPlayer` node."
msgstr ""

#: ../../docs/tutorials/animation/introduction.rst:26
msgid ""
"The AnimationPlayer node type is the data container for your animations. One "
"AnimationPlayer node can hold multiple animations, which can automatically "
"transition to one another."
msgstr ""

#: ../../docs/tutorials/animation/introduction.rst:33
msgid "The AnimationPlayer node"
msgstr ""

#: ../../docs/tutorials/animation/introduction.rst:35
msgid ""
"After you create an AnimationPlayer node, click on it to open the Animation "
"Panel at the bottom of the viewport."
msgstr ""

#: ../../docs/tutorials/animation/introduction.rst:41
msgid "The animation panel position"
msgstr ""

#: ../../docs/tutorials/animation/introduction.rst:43
msgid "The animation panel consists of four parts:"
msgstr ""

#: ../../docs/tutorials/animation/introduction.rst:48
msgid "The animation panel"
msgstr ""

#: ../../docs/tutorials/animation/introduction.rst:50
msgid "Animation controls (i.e. add, load, save, and delete animations)"
msgstr ""

#: ../../docs/tutorials/animation/introduction.rst:51
msgid "The tracks listing"
msgstr ""

#: ../../docs/tutorials/animation/introduction.rst:52
msgid "The timeline with keyframes"
msgstr ""

#: ../../docs/tutorials/animation/introduction.rst:53
msgid ""
"The timeline and track controls, where you can zoom the timeline and edit "
"tracks, for example."
msgstr ""

#: ../../docs/tutorials/animation/introduction.rst:57
msgid "Computer animation relies on keyframes"
msgstr ""

#: ../../docs/tutorials/animation/introduction.rst:59
msgid "A keyframe defines the value of a property at a point in time."
msgstr ""

#: ../../docs/tutorials/animation/introduction.rst:61
msgid ""
"Diamond shapes represent keyframes in the timeline. A line between two "
"keyframes indicates that the value doesn't change between them."
msgstr ""

#: ../../docs/tutorials/animation/introduction.rst:67
msgid "Keyframes in Godot"
msgstr ""

#: ../../docs/tutorials/animation/introduction.rst:69
msgid ""
"You set values of a node's properties and create animation keyframes for "
"them. When the animation runs, the engine will interpolate the values "
"between the keyframes, resulting in them gradually changing over time."
msgstr ""

#: ../../docs/tutorials/animation/introduction.rst:76
msgid "Two keyframes are all it takes to obtain a smooth motion"
msgstr ""

#: ../../docs/tutorials/animation/introduction.rst:78
msgid ""
"The timeline defines how long the animation will take. You can insert "
"keyframes at various points, and change their timing."
msgstr ""

#: ../../docs/tutorials/animation/introduction.rst:84
msgid "The timeline in the animation panel"
msgstr ""

#: ../../docs/tutorials/animation/introduction.rst:86
msgid ""
"Each line in the Animation Panel is an animation track that references a "
"Normal or Transform property of a node. Each track stores a path to a node "
"and its affected property. For example, the position track in the "
"illustration refers to the ``position`` property of the Sprite2D node."
msgstr ""

#: ../../docs/tutorials/animation/introduction.rst:95
msgid "Example of Normal animation tracks"
msgstr ""

#: ../../docs/tutorials/animation/introduction.rst:99
msgid ""
"If you animate the wrong property, you can edit a track's path at any time "
"by double-clicking on it and typing the new path. Play the animation using "
"the \"Play from beginning\" button |Play from beginning| (or pressing :kbd:"
"`Shift + D` on keyboard) to see the changes instantly."
msgstr ""

#: ../../docs/tutorials/animation/introduction.rst:339
msgid "Play from beginning"
msgstr ""

#: ../../docs/tutorials/animation/introduction.rst:105
msgid "Tutorial: Creating a simple animation"
msgstr ""

#: ../../docs/tutorials/animation/introduction.rst:110
msgid ""
"For this tutorial, we'll create a Sprite node with an AnimationPlayer as its "
"child. We will animate the sprite to move between two points on the screen."
msgstr ""

#: ../../docs/tutorials/animation/introduction.rst:116
msgid "Our scene setup"
msgstr ""

#: ../../docs/tutorials/animation/introduction.rst:120
msgid ""
"AnimationPlayer inherits from Node instead of Node2D or Node3D, which means "
"that the child nodes will not inherit the transform from the parent nodes "
"due to a bare Node being present in the hierarchy."
msgstr ""

#: ../../docs/tutorials/animation/introduction.rst:124
msgid ""
"Therefore, it is not recommended to add nodes that have a 2D/3D transform as "
"a child of an AnimationPlayer node."
msgstr ""

#: ../../docs/tutorials/animation/introduction.rst:127
msgid ""
"The sprite holds an image texture. For this tutorial, select the Sprite2D "
"node, click Texture in the Inspector, and then click Load. Select the "
"default Godot icon for the sprite's texture."
msgstr ""

#: ../../docs/tutorials/animation/introduction.rst:132
#, fuzzy
msgid "Adding an animation"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/animation/introduction.rst:134
msgid ""
"Select the AnimationPlayer node and click the \"Animation\" button in the "
"animation editor. From the list, select \"New\" (|Add Animation|) to add a "
"new animation. Enter a name for the animation in the dialog box."
msgstr ""

#: ../../docs/tutorials/animation/introduction.rst:340
#, fuzzy
msgid "Add Animation"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/animation/introduction.rst:141
msgid "Add a new animation"
msgstr ""

#: ../../docs/tutorials/animation/introduction.rst:144
#, fuzzy
msgid "Manage an animation libraries"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/animation/introduction.rst:146
msgid ""
"For reusability, the animation is registered in a list in the animation "
"library resource. If you add an animation to AnimationPlayer without "
"specifying any particular settings, the animation will be registered in the "
"[Global] animation library that AnimationPlayer has by default."
msgstr ""

#: ../../docs/tutorials/animation/introduction.rst:151
#, fuzzy
msgid "Manage animations"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/animation/introduction.rst:153
msgid ""
"If there are multiple animation libraries and you try to add an animation, a "
"dialog box will appear with options."
msgstr ""

#: ../../docs/tutorials/animation/introduction.rst:158
msgid "Add a new animation with library option"
msgstr ""

#: ../../docs/tutorials/animation/introduction.rst:161
msgid "Adding a track"
msgstr ""

#: ../../docs/tutorials/animation/introduction.rst:163
msgid ""
"To add a new track for our sprite, select it and take a look at the toolbar:"
msgstr ""

#: ../../docs/tutorials/animation/introduction.rst:169
msgid "Convenience buttons"
msgstr ""

#: ../../docs/tutorials/animation/introduction.rst:171
msgid ""
"These switches and buttons allow you to add keyframes for the selected "
"node's location, rotation, and scale. Since we are only animating the "
"sprite's position, make sure that only the location switch is selected. The "
"selected switches are blue."
msgstr ""

#: ../../docs/tutorials/animation/introduction.rst:176
msgid ""
"Click on the key button to create the first keyframe. Since we don't have a "
"track set up for the Position property yet, Godot will offer to create it "
"for us. Click **Create**."
msgstr ""

#: ../../docs/tutorials/animation/introduction.rst:180
msgid ""
"Godot will create a new track and insert our first keyframe at the beginning "
"of the timeline:"
msgstr ""

#: ../../docs/tutorials/animation/introduction.rst:186
msgid "The sprite track"
msgstr ""

#: ../../docs/tutorials/animation/introduction.rst:189
msgid "The second keyframe"
msgstr ""

#: ../../docs/tutorials/animation/introduction.rst:191
msgid ""
"We need to set our sprite's end location and how long it will take for it to "
"get there."
msgstr ""

#: ../../docs/tutorials/animation/introduction.rst:193
msgid ""
"Let's say we want it to take two seconds to move between the points. By "
"default, the animation is set to last only one second, so change the "
"animation length to 2 in the controls on the right side of the animation "
"panel's timeline header."
msgstr ""

#: ../../docs/tutorials/animation/introduction.rst:201
msgid "Animation length"
msgstr ""

#: ../../docs/tutorials/animation/introduction.rst:203
msgid ""
"Now, move the sprite right, to its final position. You can use the *Move "
"tool* in the toolbar or set the *Position*'s X value in the *Inspector*."
msgstr ""

#: ../../docs/tutorials/animation/introduction.rst:206
msgid ""
"Click on the timeline header near the two-second mark in the animation panel "
"and then click the key button in the toolbar to create the second keyframe."
msgstr ""

#: ../../docs/tutorials/animation/introduction.rst:210
msgid "Run the animation"
msgstr ""

#: ../../docs/tutorials/animation/introduction.rst:212
msgid "Click on the \"Play from beginning\" (|Play from beginning|) button."
msgstr ""

#: ../../docs/tutorials/animation/introduction.rst:214
msgid "Yay! Our animation runs:"
msgstr ""

#: ../../docs/tutorials/animation/introduction.rst:219
msgid "The animation"
msgstr ""

#: ../../docs/tutorials/animation/introduction.rst:222
msgid "Back and forth"
msgstr ""

#: ../../docs/tutorials/animation/introduction.rst:224
msgid ""
"Godot has an interesting feature that we can use in animations. When "
"Animation Looping is set but there's no keyframe specified at the end of the "
"animation, the first keyframe is also the last."
msgstr ""

#: ../../docs/tutorials/animation/introduction.rst:228
msgid ""
"This means we can extend the animation length to four seconds now, and Godot "
"will also calculate the frames from the last keyframe to the first, moving "
"our sprite back and forth."
msgstr ""

#: ../../docs/tutorials/animation/introduction.rst:235
msgid "Animation loop"
msgstr ""

#: ../../docs/tutorials/animation/introduction.rst:237
msgid ""
"You can change this behavior by changing the track's loop mode. This is "
"covered in the next chapter."
msgstr ""

#: ../../docs/tutorials/animation/introduction.rst:241
#: ../../docs/tutorials/animation/introduction.rst:249
msgid "Track settings"
msgstr ""

#: ../../docs/tutorials/animation/introduction.rst:243
msgid ""
"Each track has a settings panel at the end, where you can set its update "
"mode, track interpolation, and loop mode."
msgstr ""

#: ../../docs/tutorials/animation/introduction.rst:251
msgid ""
"The update mode of a track tells Godot when to update the property values. "
"This can be:"
msgstr ""

#: ../../docs/tutorials/animation/introduction.rst:254
msgid "**Continuous:** Update the property on each frame"
msgstr ""

#: ../../docs/tutorials/animation/introduction.rst:255
msgid "**Discrete:** Only update the property on keyframes"
msgstr ""

#: ../../docs/tutorials/animation/introduction.rst:256
msgid ""
"**Capture:** if the first keyframe's time is greater than ``0.0``, the "
"current value of the property will be remembered and will be blended with "
"the first animation key. For example, you could use the Capture mode to move "
"a node that's located anywhere to a specific location."
msgstr ""

#: ../../docs/tutorials/animation/introduction.rst:265
msgid "Track mode"
msgstr ""

#: ../../docs/tutorials/animation/introduction.rst:267
msgid ""
"You will usually use \"Continuous\" mode. The other types are used to script "
"complex animations."
msgstr ""

#: ../../docs/tutorials/animation/introduction.rst:270
msgid ""
"Track interpolation tells Godot how to calculate the frame values between "
"keyframes. These interpolation modes are supported:"
msgstr ""

#: ../../docs/tutorials/animation/introduction.rst:273
msgid "Nearest: Set the nearest keyframe value"
msgstr ""

#: ../../docs/tutorials/animation/introduction.rst:274
msgid ""
"Linear: Set the value based on a linear function calculation between the two "
"keyframes"
msgstr ""

#: ../../docs/tutorials/animation/introduction.rst:276
msgid ""
"Cubic: Set the value based on a cubic function calculation between the two "
"keyframes"
msgstr ""

#: ../../docs/tutorials/animation/introduction.rst:278
msgid ""
"Linear Angle (Only appears in rotation property): Linear mode with shortest "
"path rotation"
msgstr ""

#: ../../docs/tutorials/animation/introduction.rst:279
msgid ""
"Cubic Angle (Only appears in rotation property): Cubic mode with shortest "
"path rotation"
msgstr ""

#: ../../docs/tutorials/animation/introduction.rst:284
msgid "Track interpolation"
msgstr ""

#: ../../docs/tutorials/animation/introduction.rst:286
msgid ""
"With Cubic interpolation, animation is slower at keyframes and faster "
"between them, which leads to more natural movement. Cubic interpolation is "
"commonly used for character animation. Linear interpolation animates changes "
"at a fixed pace, resulting in a more robotic effect."
msgstr ""

#: ../../docs/tutorials/animation/introduction.rst:291
msgid ""
"Godot supports two loop modes, which affect the animation when it's set to "
"loop:"
msgstr ""

#: ../../docs/tutorials/animation/introduction.rst:297
msgid "Loop modes"
msgstr ""

#: ../../docs/tutorials/animation/introduction.rst:299
msgid ""
"Clamp loop interpolation: When this is selected, the animation stops after "
"the last keyframe for this track. When the first keyframe is reached again, "
"the animation will reset to its values."
msgstr ""

#: ../../docs/tutorials/animation/introduction.rst:302
msgid ""
"Wrap loop interpolation: When this is selected, Godot calculates the "
"animation after the last keyframe to reach the values of the first keyframe "
"again."
msgstr ""

#: ../../docs/tutorials/animation/introduction.rst:307
#: ../../docs/tutorials/animation/introduction.rst:320
msgid "Keyframes for other properties"
msgstr ""

#: ../../docs/tutorials/animation/introduction.rst:309
msgid ""
"Godot's animation system isn't restricted to position, rotation, and scale. "
"You can animate any property."
msgstr ""

#: ../../docs/tutorials/animation/introduction.rst:312
msgid ""
"If you select your sprite while the animation panel is visible, Godot will "
"display a small keyframe button in the *Inspector* for each of the sprite's "
"properties. Click on one of these buttons to add a track and keyframe to the "
"current animation."
msgstr ""

#: ../../docs/tutorials/animation/introduction.rst:323
msgid "Edit keyframes"
msgstr ""

#: ../../docs/tutorials/animation/introduction.rst:325
msgid ""
"You can click on a keyframe in the animation timeline to display and edit "
"its value in the *Inspector*."
msgstr ""

#: ../../docs/tutorials/animation/introduction.rst:331
msgid "Keyframe editor editing a key"
msgstr ""

#: ../../docs/tutorials/animation/introduction.rst:333
msgid ""
"You can also edit the easing value for a keyframe here by clicking and "
"dragging its easing curve. This tells Godot how to interpolate the animated "
"property when it reaches this keyframe."
msgstr ""

#: ../../docs/tutorials/animation/introduction.rst:337
msgid ""
"You can tweak your animations this way until the movement \"looks right.\""
msgstr ""

#: ../../docs/tutorials/animation/introduction.rst:343
msgid "Using RESET tracks"
msgstr ""

#: ../../docs/tutorials/animation/introduction.rst:345
msgid ""
"You can set up a special *RESET* animation to contain the \"default pose\". "
"This is used to ensure that the default pose is restored when you save the "
"scene and open it again in the editor."
msgstr ""

#: ../../docs/tutorials/animation/introduction.rst:349
msgid ""
"For existing tracks, you can add an animation called \"RESET\" (case-"
"sensitive), then add tracks for each property that you want to reset. The "
"only keyframe should be at time 0, and give it the desired default value for "
"each track."
msgstr ""

#: ../../docs/tutorials/animation/introduction.rst:354
msgid ""
"If AnimationPlayer's **Reset On Save** property is set to ``true``, the "
"scene will be saved with the effects of the reset animation applied (as if "
"it had been seeked to time ``0.0``). This only affects the saved file – the "
"property tracks in the editor stay where they were."
msgstr ""

#: ../../docs/tutorials/animation/introduction.rst:360
msgid ""
"If you want to reset the tracks in the editor, select the AnimationPlayer "
"node, open the **Animation** bottom panel then choose **Apply Reset** in the "
"animation editor's **Edit** dropdown menu."
msgstr ""

#: ../../docs/tutorials/animation/introduction.rst:364
msgid ""
"When adding tracks on new animations, the editor will ask you to "
"automatically create a RESET track when using the keyframe icon next to a "
"property in the inspector. This does not apply on tracks created with Godot "
"versions prior to 3.4, as the animation reset track feature was added in 3.4."
msgstr ""

#: ../../docs/tutorials/animation/introduction.rst:369
msgid ""
"RESET tracks is also used as a reference value for blending. See also `For "
"better blending <../animation/animation_tree.html#for-better-blending>`__."
msgstr ""

#: ../../docs/tutorials/animation/animation_track_types.rst:4
#, fuzzy
msgid "Animation Track types"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/animation/animation_track_types.rst:6
msgid ""
"This page gives an overview of the track types available for Godot's "
"animation player node on top of the default property tracks."
msgstr ""

#: ../../docs/tutorials/animation/animation_track_types.rst:11
msgid ""
"We assume you already read :ref:`doc_introduction_animation`, which covers "
"the basics, including property tracks."
msgstr ""

#: ../../docs/tutorials/animation/animation_track_types.rst:17
msgid "Property Track"
msgstr ""

#: ../../docs/tutorials/animation/animation_track_types.rst:19
msgid "The most basic track type. See :ref:`doc_introduction_animation`."
msgstr ""

#: ../../docs/tutorials/animation/animation_track_types.rst:22
msgid "Position 3D / Rotation 3D / Scale 3D Track"
msgstr ""

#: ../../docs/tutorials/animation/animation_track_types.rst:24
msgid ""
"These 3D transform tracks control the location, rotation, and scale of a 3D "
"object. They make it easier to animate a 3D object's transform compared to "
"using regular property tracks."
msgstr ""

#: ../../docs/tutorials/animation/animation_track_types.rst:28
#: ../../docs/tutorials/animation/animation_track_types.rst:35
msgid ""
"It is designed for animations imported from external 3D models and can "
"reduce resource capacity through compression."
msgstr ""

#: ../../docs/tutorials/animation/animation_track_types.rst:31
msgid "Blend Shape Track"
msgstr ""

#: ../../docs/tutorials/animation/animation_track_types.rst:33
msgid ""
"A blend shape track is optimized for animating blend shape in :ref:"
"`MeshInstance3D <class_MeshInstance3D>`."
msgstr ""

#: ../../docs/tutorials/animation/animation_track_types.rst:38
msgid "Call Method Track"
msgstr ""

#: ../../docs/tutorials/animation/animation_track_types.rst:40
msgid ""
"A call method track allow you to call a function at a precise time from "
"within an animation. For example, you can call ``queue_free()`` to delete a "
"node at the end of a death animation."
msgstr ""

#: ../../docs/tutorials/animation/animation_track_types.rst:44
msgid ""
"The events placed on the call method track are not executed when the "
"animation is previewed in the editor for safety."
msgstr ""

#: ../../docs/tutorials/animation/animation_track_types.rst:46
msgid ""
"To create such a track, click \"Add Track -> Call Method Track.\" Then, a "
"window opens and lets you select the node to associate with the track. To "
"call one of the node's methods, right-click the timeline and select \"Insert "
"Key\". A window opens with a list of available methods. Double-click one to "
"finish creating the keyframe."
msgstr ""

#: ../../docs/tutorials/animation/animation_track_types.rst:54
msgid ""
"To change the method call or its arguments, click on the key and head to the "
"inspector dock. There, you can change the method to call. If you expand the "
"\"Args\" section, you will see a list of arguments you can edit."
msgstr ""

#: ../../docs/tutorials/animation/animation_track_types.rst:61
msgid "Bezier Curve Track"
msgstr ""

#: ../../docs/tutorials/animation/animation_track_types.rst:63
msgid ""
"A bezier curve track is similar to a property track, except it allows you to "
"animate a property's value using a bezier curve."
msgstr ""

#: ../../docs/tutorials/animation/animation_track_types.rst:66
msgid ""
"Bezier curve track and property track cannot be blended in :ref:"
"`AnimationPlayer <class_AnimationPlayer>` and :ref:`AnimationTree "
"<class_AnimationTree>`."
msgstr ""

#: ../../docs/tutorials/animation/animation_track_types.rst:68
msgid ""
"To create one, click \"Add Track -> Bezier Curve Track\". As with property "
"tracks, you need to select a node and a property to animate. To open the "
"bezier curve editor, click the curve icon to the right of the animation "
"track."
msgstr ""

#: ../../docs/tutorials/animation/animation_track_types.rst:74
msgid ""
"In the editor, keys are represented by filled diamonds and the outlined "
"diamonds connected to them by a line control curve's shape."
msgstr ""

#: ../../docs/tutorials/animation/animation_track_types.rst:79
msgid "In the right click panel of the editor, you can select the handle mode:"
msgstr ""

#: ../../docs/tutorials/animation/animation_track_types.rst:81
msgid ""
"Free: Allows you to orient a manipulator in any direction without affecting "
"the other's position."
msgstr ""

#: ../../docs/tutorials/animation/animation_track_types.rst:83
msgid ""
"Linear: Does not allow rotation of the manipulator and draws a linear graph."
msgstr ""

#: ../../docs/tutorials/animation/animation_track_types.rst:84
msgid ""
"Balanced: Makes it so manipulators rotate together, but the distance between "
"the key and a manipulator is not mirrored."
msgstr ""

#: ../../docs/tutorials/animation/animation_track_types.rst:86
msgid ""
"Mirrored: Makes the position of one manipulator perfectly mirror the other, "
"including their distance to the key."
msgstr ""

#: ../../docs/tutorials/animation/animation_track_types.rst:92
msgid "Audio Playback Track"
msgstr ""

#: ../../docs/tutorials/animation/animation_track_types.rst:94
msgid ""
"If you want to create an animation with audio, you need to create an audio "
"playback track. To create one, your scene must have either an "
"AudioStreamPlayer, AudioStreamPlayer2D, or AudioStreamPlayer3D node. When "
"creating the track, you must select one of those nodes."
msgstr ""

#: ../../docs/tutorials/animation/animation_track_types.rst:99
msgid ""
"To play a sound in your animation, drag and drop an audio file from the file "
"system dock onto the animation track. You should see the waveform of your "
"audio file in the track."
msgstr ""

#: ../../docs/tutorials/animation/animation_track_types.rst:105
msgid ""
"To remove a sound from the animation, you can right-click it and select "
"\"Delete Key(s)\" or click on it and press the :kbd:`Del` key."
msgstr ""

#: ../../docs/tutorials/animation/animation_track_types.rst:108
msgid ""
"The blend mode allows you to choose whether or not to adjust the audio "
"volume when blending in the :ref:`AnimationTree <class_AnimationTree>`."
msgstr ""

#: ../../docs/tutorials/animation/animation_track_types.rst:113
msgid "Animation Playback Track"
msgstr ""

#: ../../docs/tutorials/animation/animation_track_types.rst:115
msgid ""
"Animation playback tracks allow you to sequence the animations of other "
"animation player nodes in a scene. For example, you can use it to animate "
"several characters in a cut-scene."
msgstr ""

#: ../../docs/tutorials/animation/animation_track_types.rst:119
msgid ""
"To create an animation playback track, select \"New Track -> Animation "
"Playback Track.\""
msgstr ""

#: ../../docs/tutorials/animation/animation_track_types.rst:122
msgid "Then, select the animation player you want to associate with the track."
msgstr ""

#: ../../docs/tutorials/animation/animation_track_types.rst:124
msgid ""
"To add an animation to the track, right-click on it and insert a key. Select "
"the key you just created to select an animation in the inspector dock."
msgstr ""

#: ../../docs/tutorials/animation/animation_track_types.rst:129
msgid ""
"If an animation is already playing and you want to stop it early, you can "
"create a key and have it set to `[STOP]` in the inspector."
msgstr ""

#: ../../docs/tutorials/animation/animation_track_types.rst:132
msgid ""
"If you instanced a scene that contains an animation player into your scene, "
"you need to enable \"Editable Children\" in the scene tree to access its "
"animation player. Also, an animation player cannot reference itself."
msgstr ""

#: ../../docs/tutorials/animation/cutout_animation.rst:6
msgid "Cutout animation"
msgstr ""

#: ../../docs/tutorials/animation/cutout_animation.rst:9
#: ../../docs/tutorials/inputs/inputevent.rst:7
msgid "What is it?"
msgstr ""

#: ../../docs/tutorials/animation/cutout_animation.rst:11
msgid ""
"Traditionally, `cutout animation <https://en.wikipedia.org/wiki/"
"Cutout_animation>`__ is a type of `stop motion animation <https://en."
"wikipedia.org/wiki/Stop_motion>`__ in which pieces of paper (or other thin "
"material) are cut into special shapes and arranged in two-dimensional "
"representations of characters and objects. Characters' bodies are usually "
"made out of several pieces. The pieces are arranged and photographed once "
"for each frame of the film. The animator moves and rotates the parts in "
"small increments between each shot to create the illusion of movement when "
"the images are played back quickly in sequence."
msgstr ""

#: ../../docs/tutorials/animation/cutout_animation.rst:20
msgid ""
"Simulations of cutout animation can now be created using software as seen in "
"`South Park <https://en.wikipedia.org/wiki/South_Park>`__ and `Jake and the "
"Never Land Pirates <https://en.wikipedia.org/wiki/"
"Jake_and_the_Never_Land_Pirates>`__."
msgstr ""

#: ../../docs/tutorials/animation/cutout_animation.rst:24
msgid ""
"In video games, this technique has also become popular. Examples of this are "
"`Paper Mario <https://en.wikipedia.org/wiki/Super_Paper_Mario>`__ or `Rayman "
"Origins <https://en.wikipedia.org/wiki/Rayman_Origins>`__ ."
msgstr ""

#: ../../docs/tutorials/animation/cutout_animation.rst:29
msgid "Cutout animation in Godot"
msgstr ""

#: ../../docs/tutorials/animation/cutout_animation.rst:31
msgid ""
"Godot provides tools for working with cutout rigs, and is ideal for the "
"workflow:"
msgstr ""

#: ../../docs/tutorials/animation/cutout_animation.rst:33
msgid ""
"**The animation system is fully integrated with the engine**: This means "
"animations can control much more than just motion of objects. Textures, "
"sprite sizes, pivots, opacity, color modulation, and more, can all be "
"animated and blended."
msgstr ""

#: ../../docs/tutorials/animation/cutout_animation.rst:37
msgid ""
"**Combine animation styles**: AnimatedSprite2D allows traditional cel "
"animation to be used alongside cutout animation. In cel animation different "
"animation frames use entirely different drawings rather than the same pieces "
"positioned differently. In an otherwise cutout-based animation, cel "
"animation can be used selectively for complex parts such as hands, feet, "
"changing facial expressions, etc."
msgstr ""

#: ../../docs/tutorials/animation/cutout_animation.rst:43
msgid ""
"**Custom Shaped Elements**: Custom shapes can be created with :ref:"
"`Polygon2D <class_Polygon2D>` allowing UV animation, deformations, etc."
msgstr ""

#: ../../docs/tutorials/animation/cutout_animation.rst:46
msgid ""
"**Particle Systems**: A cutout animation rig can be combined with particle "
"systems. This can be useful for magic effects, jetpacks, etc."
msgstr ""

#: ../../docs/tutorials/animation/cutout_animation.rst:48
msgid ""
"**Custom Colliders**: Set colliders and influence areas in different parts "
"of the skeletons, great for bosses and fighting games."
msgstr ""

#: ../../docs/tutorials/animation/cutout_animation.rst:50
msgid ""
"**Animation Tree**: Allows complex combinations and blending between several "
"animations, the same way it works in 3D."
msgstr ""

#: ../../docs/tutorials/animation/cutout_animation.rst:53
#: ../../docs/tutorials/shaders/shader_materials.rst:24
msgid "And much more!"
msgstr ""

#: ../../docs/tutorials/animation/cutout_animation.rst:56
msgid "Making of GBot"
msgstr ""

#: ../../docs/tutorials/animation/cutout_animation.rst:58
msgid ""
"For this tutorial, we will use as demo content the pieces of the `GBot "
"<https://www.youtube.com/watch?"
"v=S13FrWuBMx4&list=UUckpus81gNin1aV8WSffRKw>`__ character, created by "
"Andreas Esau."
msgstr ""

#: ../../docs/tutorials/animation/cutout_animation.rst:64
msgid ""
"Get your assets: `cutout_animation_assets.zip <https://github.com/"
"godotengine/godot-docs-project-starters/releases/download/latest-4.x/"
"cutout_animation_assets.zip>`_."
msgstr ""

#: ../../docs/tutorials/animation/cutout_animation.rst:68
msgid "Setting up the rig"
msgstr ""

#: ../../docs/tutorials/animation/cutout_animation.rst:70
msgid "Create an empty Node2D as root of the scene, we will work under it:"
msgstr ""

#: ../../docs/tutorials/animation/cutout_animation.rst:74
msgid ""
"The first node of the model is the hip. Generally, both in 2D and 3D, the "
"hip is the root of the skeleton. This makes it easier to animate:"
msgstr ""

#: ../../docs/tutorials/animation/cutout_animation.rst:80
msgid ""
"Next will be the torso. The torso needs to be a child of the hip, so create "
"a child sprite and load the torso texture, later accommodate it properly:"
msgstr ""

#: ../../docs/tutorials/animation/cutout_animation.rst:85
msgid ""
"This looks good. Let's see if our hierarchy works as a skeleton by rotating "
"the torso. We can do this be pressing :kbd:`E` to enter rotate mode, and "
"dragging with the left mouse button. To exit rotate mode hit :kbd:`ESC`."
msgstr ""

#: ../../docs/tutorials/animation/cutout_animation.rst:91
msgid "The rotation pivot is wrong and needs to be adjusted."
msgstr ""

#: ../../docs/tutorials/animation/cutout_animation.rst:93
msgid ""
"This small cross in the middle of the :ref:`Sprite2D <class_Sprite2D>` is "
"the rotation pivot:"
msgstr ""

#: ../../docs/tutorials/animation/cutout_animation.rst:99
msgid "Adjusting the pivot"
msgstr ""

#: ../../docs/tutorials/animation/cutout_animation.rst:101
msgid ""
"The pivot can be adjusted by changing the *offset* property in the Sprite2D:"
msgstr ""

#: ../../docs/tutorials/animation/cutout_animation.rst:106
msgid ""
"The pivot can also be adjusted *visually*. While hovering over the desired "
"pivot point,  press :kbd:`V` to move the pivot there for the selected "
"Sprite2D. There is also a tool in the tool bar that has a similar function."
msgstr ""

#: ../../docs/tutorials/animation/cutout_animation.rst:113
msgid ""
"Continue adding body pieces, starting with the right arm. Make sure to put "
"each sprite in its correct place in the hierarchy, so its rotations and "
"translations are relative to its parent:"
msgstr ""

#: ../../docs/tutorials/animation/cutout_animation.rst:119
msgid ""
"With the left arm there's a problem. In 2D, child nodes appear in front of "
"their parents:"
msgstr ""

#: ../../docs/tutorials/animation/cutout_animation.rst:124
msgid ""
"We want the left arm to appear *behind* the hip and the torso. We could move "
"the left arm nodes behind the hip (above the hip node in the scene "
"hierarchy), but then the left arm is no longer in its proper place in the "
"hierarchy. This means it wouldn't be affected by the movement of the torso. "
"We'll fix this problem with ``RemoteTransform2D`` nodes."
msgstr ""

#: ../../docs/tutorials/animation/cutout_animation.rst:130
msgid ""
"You can also fix depth ordering problems by adjusting the Z property of any "
"node inheriting from Node2D."
msgstr ""

#: ../../docs/tutorials/animation/cutout_animation.rst:134
msgid "RemoteTransform2D node"
msgstr ""

#: ../../docs/tutorials/animation/cutout_animation.rst:136
msgid ""
"The :ref:`RemoteTransform2D <class_RemoteTransform2D>` node transforms nodes "
"somewhere else in the hierarchy. This node applies its own transform "
"(including any transformation it inherits from its parents) to the remote "
"node it targets."
msgstr ""

#: ../../docs/tutorials/animation/cutout_animation.rst:140
msgid ""
"This allows us to correct the visibility order of our elements, "
"independently of the locations of those parts in the cutout hierarchy."
msgstr ""

#: ../../docs/tutorials/animation/cutout_animation.rst:143
msgid ""
"Create a ``RemoteTransform2D`` node as a child of the torso. Call it "
"``remote_arm_l``. Create another RemoteTransform2D node inside the first and "
"call it ``remote_hand_l``. Use the ``Remote Path`` property of the two new "
"nodes to target the ``arm_l`` and ``hand_l`` sprites respectively:"
msgstr ""

#: ../../docs/tutorials/animation/cutout_animation.rst:150
msgid ""
"Moving the ``RemoteTransform2D`` nodes now moves the sprites. So we can "
"create animations by adjusting the ``RemoteTransform2D`` transforms:"
msgstr ""

#: ../../docs/tutorials/animation/cutout_animation.rst:156
msgid "Completing the skeleton"
msgstr ""

#: ../../docs/tutorials/animation/cutout_animation.rst:158
msgid ""
"Complete the skeleton by following the same steps for the rest of the parts. "
"The resulting scene should look similar to this:"
msgstr ""

#: ../../docs/tutorials/animation/cutout_animation.rst:163
msgid ""
"The resulting rig will be easy to animate. By selecting the nodes and "
"rotating them you can animate forward kinematics (FK) efficiently."
msgstr ""

#: ../../docs/tutorials/animation/cutout_animation.rst:166
msgid "For simple objects and rigs this is fine, but there are limitations:"
msgstr ""

#: ../../docs/tutorials/animation/cutout_animation.rst:168
msgid ""
"Selecting sprites in the main viewport can become difficult in complex rigs. "
"The scene tree ends up being used to select parts instead, which can be "
"slower."
msgstr ""

#: ../../docs/tutorials/animation/cutout_animation.rst:170
msgid ""
"Inverse Kinematics (IK) is useful for animating extremities like hands and "
"feet, and can't be used with our rig in its current state."
msgstr ""

#: ../../docs/tutorials/animation/cutout_animation.rst:173
msgid "To solve these problems we'll use Godot's skeletons."
msgstr ""

#: ../../docs/tutorials/animation/cutout_animation.rst:176
msgid "Skeletons"
msgstr ""

#: ../../docs/tutorials/animation/cutout_animation.rst:178
msgid ""
"In Godot there is a helper to create \"bones\" between nodes. The bone-"
"linked nodes are called skeletons."
msgstr ""

#: ../../docs/tutorials/animation/cutout_animation.rst:181
msgid ""
"As an example, let's turn the right arm into a skeleton. To create a "
"skeleton, a chain of nodes must be selected from top to bottom:"
msgstr ""

#: ../../docs/tutorials/animation/cutout_animation.rst:186
msgid "Then, click on the Skeleton menu and select ``Make Bones``."
msgstr ""

#: ../../docs/tutorials/animation/cutout_animation.rst:190
msgid "This will add bones covering the arm, but the result may be surprising."
msgstr ""

#: ../../docs/tutorials/animation/cutout_animation.rst:194
msgid ""
"Why does the hand lack a bone? In Godot, a bone connects a node with its "
"parent. And there's currently no child of the hand node. With this knowledge "
"let's try again."
msgstr ""

#: ../../docs/tutorials/animation/cutout_animation.rst:198
msgid ""
"The first step is creating an endpoint node. Any kind of node will do, but :"
"ref:`Marker2D <class_Marker2D>` is preferred because it's visible in the "
"editor. The endpoint node will ensure that the last bone has orientation."
msgstr ""

#: ../../docs/tutorials/animation/cutout_animation.rst:205
msgid ""
"Now select the whole chain, from the endpoint to the arm and create bones:"
msgstr ""

#: ../../docs/tutorials/animation/cutout_animation.rst:210
msgid ""
"The result resembles a skeleton a lot more, and now the arm and forearm can "
"be selected and animated."
msgstr ""

#: ../../docs/tutorials/animation/cutout_animation.rst:213
msgid ""
"Create endpoints for all important extremities. Generate bones for all "
"articulable parts of the cutout, with the hip as the ultimate connection "
"between all of them."
msgstr ""

#: ../../docs/tutorials/animation/cutout_animation.rst:217
msgid ""
"You may notice that an extra bone is created when connecting the hip and "
"torso. Godot has connected the hip node to the scene root with a bone, and "
"we don't want that. To fix this, select the root and hip node, open the "
"Skeleton menu, click ``clear bones``."
msgstr ""

#: ../../docs/tutorials/animation/cutout_animation.rst:224
msgid "Your final skeleton should look something like this:"
msgstr ""

#: ../../docs/tutorials/animation/cutout_animation.rst:228
msgid ""
"You might have noticed a second set of endpoints in the hands. This will "
"make sense soon."
msgstr ""

#: ../../docs/tutorials/animation/cutout_animation.rst:231
msgid ""
"Now that the whole figure is rigged, the next step is setting up the IK "
"chains. IK chains allow for more natural control of extremities."
msgstr ""

#: ../../docs/tutorials/animation/cutout_animation.rst:235
msgid "IK chains"
msgstr ""

#: ../../docs/tutorials/animation/cutout_animation.rst:237
msgid ""
"IK stands for inverse kinematics. It's a convenient technique for animating "
"the position of hands, feet and other extremities of rigs like the one we've "
"made. Imagine you want to pose a character's foot in a specific position on "
"the ground. Without IK chains, each motion of the foot would require "
"rotating and positioning several other bones (the shin and the thigh at "
"least). This would be quite complex and lead to imprecise results. IK allows "
"us to move the foot directly while the shin and thigh self-adjust."
msgstr ""

#: ../../docs/tutorials/animation/cutout_animation.rst:247
msgid ""
"**IK chains in Godot currently work in the editor only**, not at runtime. "
"They are intended to ease the process of setting keyframes, and are not "
"currently useful for techniques like procedural animation."
msgstr ""

#: ../../docs/tutorials/animation/cutout_animation.rst:251
msgid ""
"To create an IK chain, select a chain of bones from endpoint to the base for "
"the chain. For example, to create an IK chain for the right leg, select the "
"following:"
msgstr ""

#: ../../docs/tutorials/animation/cutout_animation.rst:257
msgid "Then enable this chain for IK. Go to Edit > Make IK Chain."
msgstr ""

#: ../../docs/tutorials/animation/cutout_animation.rst:261
msgid "As a result, the base of the chain will turn *Yellow*."
msgstr ""

#: ../../docs/tutorials/animation/cutout_animation.rst:265
msgid ""
"Once the IK chain is set up, grab any child or grand-child of the base of "
"the chain (e.g. a foot), and move it. You'll see the rest of the chain "
"adjust as you adjust its position."
msgstr ""

#: ../../docs/tutorials/animation/cutout_animation.rst:272
msgid "Animation tips"
msgstr ""

#: ../../docs/tutorials/animation/cutout_animation.rst:274
msgid ""
"The following section will be a collection of tips for creating animation "
"for your cutout rigs. For more information on how the animation system in "
"Godot works, see :ref:`doc_introduction_animation`."
msgstr ""

#: ../../docs/tutorials/animation/cutout_animation.rst:279
msgid "Setting keyframes and excluding properties"
msgstr ""

#: ../../docs/tutorials/animation/cutout_animation.rst:281
msgid ""
"Special contextual elements appear in the top toolbar when the animation "
"editor window is open:"
msgstr ""

#: ../../docs/tutorials/animation/cutout_animation.rst:286
msgid ""
"The key button inserts location, rotation, and scale keyframes for the "
"selected objects or bones at the current playhead position."
msgstr ""

#: ../../docs/tutorials/animation/cutout_animation.rst:289
msgid ""
"The \"loc\", \"rot\", and \"scl\" toggle buttons to the left of the key "
"button modify its function, allowing you to specify which of the three "
"properties keyframes will be created for."
msgstr ""

#: ../../docs/tutorials/animation/cutout_animation.rst:293
msgid ""
"Here's an illustration of how this can be useful: Imagine you have a node "
"which already has two keyframes animating its scale only. You want to add an "
"overlapping rotation movement to the same node. The rotation movement should "
"begin and end at different times from the scale change that's already set "
"up. You can use the toggle buttons to have only rotation information added "
"when you add a new keyframe. This way, you can avoid adding unwanted scale "
"keyframes which would disrupt the existing scale animation."
msgstr ""

#: ../../docs/tutorials/animation/cutout_animation.rst:302
#, fuzzy
msgid "Creating a rest pose"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/animation/cutout_animation.rst:304
msgid ""
"Think of a rest pose as a default pose that your cutout rig should be set to "
"when no other pose is active in your game. Create a rest pose as follows:"
msgstr ""

#: ../../docs/tutorials/animation/cutout_animation.rst:307
msgid ""
"1. Make sure the rig parts are positioned in what looks like a \"resting\" "
"arrangement."
msgstr ""

#: ../../docs/tutorials/animation/cutout_animation.rst:310
#, fuzzy
msgid "Create a new animation, rename it \"rest\"."
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/animation/cutout_animation.rst:312
msgid "Select all nodes in your rig (box selection should work fine)."
msgstr ""

#: ../../docs/tutorials/animation/cutout_animation.rst:314
msgid ""
"4. Make sure the \"loc\", \"rot\", and \"scl\" toggle buttons are all active "
"in the toolbar."
msgstr ""

#: ../../docs/tutorials/animation/cutout_animation.rst:317
msgid ""
"5. Press the key button. Keys will be inserted for all selected parts "
"storing their current arrangement. This pose can now be recalled when "
"necessary in your game by playing the \"rest\" animation you've created."
msgstr ""

#: ../../docs/tutorials/animation/cutout_animation.rst:324
msgid "Modifying rotation only"
msgstr ""

#: ../../docs/tutorials/animation/cutout_animation.rst:326
msgid ""
"When animating a cutout rig, often it's only the rotation of the nodes that "
"needs to change. Location and scale are rarely used."
msgstr ""

#: ../../docs/tutorials/animation/cutout_animation.rst:330
msgid ""
"So when inserting keys, you might find it convenient to have only the "
"\"rot\" toggle active most of the time:"
msgstr ""

#: ../../docs/tutorials/animation/cutout_animation.rst:335
msgid ""
"This will avoid the creation of unwanted animation tracks for position and "
"scale."
msgstr ""

#: ../../docs/tutorials/animation/cutout_animation.rst:339
msgid "Keyframing IK chains"
msgstr ""

#: ../../docs/tutorials/animation/cutout_animation.rst:341
msgid ""
"When editing IK chains, it's not necessary to select the whole chain to add "
"keyframes. Selecting the endpoint of the chain and inserting a keyframe will "
"automatically insert keyframes for all other parts of the chain too."
msgstr ""

#: ../../docs/tutorials/animation/cutout_animation.rst:346
msgid "Visually move a sprite behind its parent"
msgstr ""

#: ../../docs/tutorials/animation/cutout_animation.rst:348
msgid ""
"Sometimes it is necessary to have a node change its visual depth relative to "
"its parent node during an animation. Think of a character facing the camera, "
"who pulls something out from behind his back and holds it out in front of "
"him. During this animation the whole arm and the object in his hand would "
"need to change their visual depth relative to the body of the character."
msgstr ""

#: ../../docs/tutorials/animation/cutout_animation.rst:354
msgid ""
"To help with this there's a keyframable \"Behind Parent\" property on all "
"Node2D-inheriting nodes. When planning your rig, think about the movements "
"it will need to perform and give some thought to how you'll use \"Behind "
"Parent\" and/or RemoteTransform2D nodes. They provide overlapping "
"functionality."
msgstr ""

#: ../../docs/tutorials/animation/cutout_animation.rst:362
msgid "Setting easing curves for multiple keys"
msgstr ""

#: ../../docs/tutorials/animation/cutout_animation.rst:364
msgid "To apply the same easing curve to multiple keyframes at once:"
msgstr ""

#: ../../docs/tutorials/animation/cutout_animation.rst:366
msgid "Select the relevant keys."
msgstr ""

#: ../../docs/tutorials/animation/cutout_animation.rst:367
msgid ""
"Click on the pencil icon in the bottom right of the animation panel. This "
"will open the transition editor."
msgstr ""

#: ../../docs/tutorials/animation/cutout_animation.rst:369
msgid "In the transition editor, click on the desired curve to apply it."
msgstr ""

#: ../../docs/tutorials/animation/cutout_animation.rst:374
msgid "2D Skeletal deform"
msgstr ""

#: ../../docs/tutorials/animation/cutout_animation.rst:376
msgid ""
"Skeletal deform can be used to augment a cutout rig, allowing single pieces "
"to deform organically (e.g. antennae that wobble as an insect character "
"walks)."
msgstr ""

#: ../../docs/tutorials/animation/cutout_animation.rst:379
msgid ""
"This process is described in a :ref:`separate tutorial <doc_2d_skeletons>`."
msgstr ""

#: ../../docs/tutorials/animation/2d_skeletons.rst:6
msgid "2D skeletons"
msgstr ""

#: ../../docs/tutorials/animation/2d_skeletons.rst:11
msgid ""
"When working with 3D, skeletal deforms are common for characters and "
"creatures and most 3D modeling applications support it. For 2D, as this "
"function is not used as often, it's difficult to find mainstream software "
"aimed for this."
msgstr ""

#: ../../docs/tutorials/animation/2d_skeletons.rst:15
msgid ""
"One option is to create animations in third-party software such as Spine or "
"Dragonbones. From Godot 3.1 onwards, though, this functionality is supported "
"built-in."
msgstr ""

#: ../../docs/tutorials/animation/2d_skeletons.rst:19
msgid ""
"Why would you want to do skeletal animations directly in Godot? The answer "
"is that there are many advantages to it:"
msgstr ""

#: ../../docs/tutorials/animation/2d_skeletons.rst:22
msgid ""
"Better integration with the engine, so less hassle importing and editing "
"from an external tool."
msgstr ""

#: ../../docs/tutorials/animation/2d_skeletons.rst:24
msgid ""
"Ability to control particle systems, shaders, sounds, call scripts, colors, "
"transparency, etc. in animations."
msgstr ""

#: ../../docs/tutorials/animation/2d_skeletons.rst:26
msgid ""
"The built-in skeletal system in Godot is very efficient and designed for "
"performance."
msgstr ""

#: ../../docs/tutorials/animation/2d_skeletons.rst:29
msgid "The following tutorial will, then, explain 2D skeletal deformations."
msgstr ""

#: ../../docs/tutorials/animation/2d_skeletons.rst:36
msgid ""
"Before starting, we recommend you to go through the :ref:"
"`doc_cutout_animation` tutorial to gain a general understanding of animating "
"within Godot."
msgstr ""

#: ../../docs/tutorials/animation/2d_skeletons.rst:40
msgid ""
"For this tutorial, we will be using a single image to construct our "
"character. Download it from :download:`gBot_pieces.png <img/gBot_pieces."
"png>` or save the image below."
msgstr ""

#: ../../docs/tutorials/animation/2d_skeletons.rst:46
msgid ""
"It is also advised to download the final character image :download:"
"`gBot_complete.png <img/gBot_complete.png>` to have a good reference for "
"putting the different pieces together."
msgstr ""

#: ../../docs/tutorials/animation/2d_skeletons.rst:53
#, fuzzy
msgid "Creating the polygons"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/animation/2d_skeletons.rst:55
msgid ""
"Create a new scene for your model (if it's going to be an animated "
"character, you may want to use a ``CharacterBody2D``). For ease of use, an "
"empty 2D node is created as a root for the polygons."
msgstr ""

#: ../../docs/tutorials/animation/2d_skeletons.rst:59
msgid ""
"Begin with a ``Polygon2D`` node. There is no need to place it anywhere in "
"the scene for now, so simply create it like this:"
msgstr ""

#: ../../docs/tutorials/animation/2d_skeletons.rst:64
msgid ""
"Select it and assign the texture with the character pieces you have "
"downloaded before:"
msgstr ""

#: ../../docs/tutorials/animation/2d_skeletons.rst:69
msgid ""
"Drawing a polygon directly is not advised. Instead, open the \"UV\" dialog "
"for the polygon:"
msgstr ""

#: ../../docs/tutorials/animation/2d_skeletons.rst:74
msgid ""
"Head over to the *Points* mode, select the pencil and draw a polygon around "
"the desired piece:"
msgstr ""

#: ../../docs/tutorials/animation/2d_skeletons.rst:79
msgid ""
"Duplicate the polygon node and give it a proper name. Then, enter the \"UV\" "
"dialog again and replace the old polygon with another one in the new desired "
"piece."
msgstr ""

#: ../../docs/tutorials/animation/2d_skeletons.rst:83
msgid ""
"When you duplicate nodes and the next piece has a similar shape, you can "
"edit the previous polygon instead of drawing a new one."
msgstr ""

#: ../../docs/tutorials/animation/2d_skeletons.rst:86
msgid ""
"After moving the polygon, remember to update the UV by selecting **Edit > "
"Copy Polygon to UV** in the Polygon 2D UV Editor."
msgstr ""

#: ../../docs/tutorials/animation/2d_skeletons.rst:91
msgid "Keep doing this until you mapped all pieces."
msgstr ""

#: ../../docs/tutorials/animation/2d_skeletons.rst:95
msgid ""
"You will notice that pieces for nodes appear in the same layout as they do "
"in the original texture. This is because by default, when you draw a "
"polygon, the UV and points are the same."
msgstr ""

#: ../../docs/tutorials/animation/2d_skeletons.rst:99
msgid ""
"Rearrange the pieces and build the character. This should be pretty quick. "
"There is no need to change pivots, so don't bother making sure rotation "
"pivots for each piece are right; you can leave them be for now."
msgstr ""

#: ../../docs/tutorials/animation/2d_skeletons.rst:105
msgid ""
"Ah, the visual order of the pieces is not correct yet, as some are covering "
"wrong pieces. Rearrange the order of the nodes to fix this:"
msgstr ""

#: ../../docs/tutorials/animation/2d_skeletons.rst:110
msgid ""
"And there you go! It was definitely much easier than in the cutout tutorial."
msgstr ""

#: ../../docs/tutorials/animation/2d_skeletons.rst:113
#, fuzzy
msgid "Creating the skeleton"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/animation/2d_skeletons.rst:115
msgid ""
"Create a ``Skeleton2D`` node as a child of the root node. This will be the "
"base of our skeleton:"
msgstr ""

#: ../../docs/tutorials/animation/2d_skeletons.rst:120
msgid ""
"Create a ``Bone2D`` node as a child of the skeleton. Put it on the hip "
"(usually skeletons start here). The bone will be pointing to the right, but "
"you can ignore this for now."
msgstr ""

#: ../../docs/tutorials/animation/2d_skeletons.rst:126
msgid "Keep creating bones in hierarchy and naming them accordingly."
msgstr ""

#: ../../docs/tutorials/animation/2d_skeletons.rst:130
msgid ""
"At the end of this chain, there will be a *jaw* node. It is, again, very "
"short and pointing to the right. This is normal for bones without children. "
"The length of *tip* bones can be changed with a property in the inspector:"
msgstr ""

#: ../../docs/tutorials/animation/2d_skeletons.rst:136
msgid ""
"In this case, we don't need to rotate the bone (coincidentally the jaw "
"points right in the sprite), but in case you need to, feel free to do it. "
"Again, this is only really needed for tip bones as nodes with children don't "
"usually need a length or a specific rotation."
msgstr ""

#: ../../docs/tutorials/animation/2d_skeletons.rst:141
msgid "Keep going and build the whole skeleton:"
msgstr ""

#: ../../docs/tutorials/animation/2d_skeletons.rst:145
msgid ""
"You will notice that all bones raise an annoying warning about a missing "
"rest pose. This means that it's time to set one. Go to the *skeleton* node "
"and create a rest pose. This pose is the default one, you can come back to "
"it anytime you want (which is very handy for animating):"
msgstr ""

#: ../../docs/tutorials/animation/2d_skeletons.rst:152
msgid ""
"The warnings will go away. If you modify the skeleton (add/remove bones) you "
"will need to set the rest pose again."
msgstr ""

#: ../../docs/tutorials/animation/2d_skeletons.rst:156
msgid "Deforming the polygons"
msgstr ""

#: ../../docs/tutorials/animation/2d_skeletons.rst:158
msgid ""
"Select the previously created polygons and assign the skeleton node to their "
"``Skeleton`` property. This will ensure that they can eventually be deformed "
"by it."
msgstr ""

#: ../../docs/tutorials/animation/2d_skeletons.rst:164
msgid "Click the property highlighted above and select the skeleton node:"
msgstr ""

#: ../../docs/tutorials/animation/2d_skeletons.rst:168
msgid ""
"Again, open the UV editor for the polygon and go to the *Bones* section."
msgstr ""

#: ../../docs/tutorials/animation/2d_skeletons.rst:172
msgid ""
"You will not be able to paint weights yet. For this you need to synchronize "
"the list of bones from the skeleton with the polygon. This step is done only "
"once and manually (unless you modify the skeleton by adding/removing/"
"renaming bones). It ensures that your rigging information is kept in the "
"polygon, even if a skeleton node is accidentally lost or the skeleton "
"modified. Push the \"Sync Bones to Polygon\" button to sync the list."
msgstr ""

#: ../../docs/tutorials/animation/2d_skeletons.rst:181
msgid ""
"The list of bones will automatically appear. By default, your polygon has no "
"weight assigned to any of them. Select the bones you want to assign weight "
"to and paint them:"
msgstr ""

#: ../../docs/tutorials/animation/2d_skeletons.rst:187
msgid ""
"Points in white have a full weight assigned, while points in black are not "
"influenced by the bone. If the same point is painted white for multiple "
"bones, the influence will be distributed amongst them (so usually there is "
"not that much need to use shades in-between unless you want to polish the "
"bending effect)."
msgstr ""

#: ../../docs/tutorials/animation/2d_skeletons.rst:195
msgid ""
"After painting the weights, animating the bones (NOT the polygons!) will "
"have the desired effect of modifying and bending the polygons accordingly. "
"As you only need to animate bones in this approach, work becomes much easier!"
msgstr ""

#: ../../docs/tutorials/animation/2d_skeletons.rst:199
msgid ""
"But it's not all roses. Trying to animate bones that bend the polygon will "
"often yield unexpected results:"
msgstr ""

#: ../../docs/tutorials/animation/2d_skeletons.rst:204
msgid ""
"This happens because Godot generates internal triangles that connect the "
"points when drawing the polygon. They don't always bend the way you would "
"expect. To solve this, you need to set hints in the geometry to clarify how "
"you expect it to deform."
msgstr ""

#: ../../docs/tutorials/animation/2d_skeletons.rst:210
msgid "Internal vertices"
msgstr ""

#: ../../docs/tutorials/animation/2d_skeletons.rst:212
msgid ""
"Open the UV menu for each bone again and go to the *Points* section. Add "
"some internal vertices in the regions where you expect the geometry to bend:"
msgstr ""

#: ../../docs/tutorials/animation/2d_skeletons.rst:217
msgid ""
"Now, go to the *Polygon* section and redraw your own polygons with more "
"detail. Imagine that, as your polygons bend, you need to make sure they "
"deform the least possible, so experiment a bit to find the right setup."
msgstr ""

#: ../../docs/tutorials/animation/2d_skeletons.rst:223
msgid ""
"Once you start drawing, the original polygon will disappear and you will be "
"free to create your own:"
msgstr ""

#: ../../docs/tutorials/animation/2d_skeletons.rst:228
msgid ""
"This amount of detail is usually fine, though you may want to have more fine-"
"grained control over where triangles go. Experiment by yourself until you "
"get the results you like."
msgstr ""

#: ../../docs/tutorials/animation/2d_skeletons.rst:232
msgid ""
"**Note:** Don't forget that your newly added internal vertices also need "
"weight painting! Go to the *Bones* section again to assign them to the right "
"bones."
msgstr ""

#: ../../docs/tutorials/animation/2d_skeletons.rst:235
msgid "Once you are all set, you will get much better results:"
msgstr ""

#: ../../docs/tutorials/animation/animation_tree.rst:4
#, fuzzy
msgid "Using AnimationTree"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/animation/animation_tree.rst:9
msgid ""
"With :ref:`AnimationPlayer <class_AnimationPlayer>`, Godot has one of the "
"most flexible animation systems that you can find in any game engine. The "
"ability to animate almost any property in any node or resource, as well as "
"having dedicated transform, bezier, function calling, audio and sub-"
"animation tracks, is pretty much unique."
msgstr ""

#: ../../docs/tutorials/animation/animation_tree.rst:13
msgid ""
"However, the support for blending those animations via ``AnimationPlayer`` "
"is relatively limited, as only a fixed cross-fade transition time can be set."
msgstr ""

#: ../../docs/tutorials/animation/animation_tree.rst:15
msgid ""
":ref:`AnimationTree <class_AnimationTree>` is a new node introduced in Godot "
"3.1 to deal with advanced transitions. It supersedes the ancient "
"``AnimationTreePlayer``, while adding a huge amount of features and "
"flexibility."
msgstr ""

#: ../../docs/tutorials/animation/animation_tree.rst:19
#, fuzzy
msgid "Creating an AnimationTree"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/animation/animation_tree.rst:21
msgid ""
"Before starting, it must be made clear that an ``AnimationTree`` node does "
"not contain its own animations. Instead, it uses animations contained in an "
"``AnimationPlayer`` node. This way, you can edit your animations (or import "
"them from a 3D scene) as usual and then use this extra node to control the "
"playback."
msgstr ""

#: ../../docs/tutorials/animation/animation_tree.rst:25
msgid ""
"The most common way to use ``AnimationTree`` is in a 3D scene. When "
"importing your scenes from a 3D exchange format, they will usually come with "
"animations built-in (either multiple ones or split from a large one on "
"import). At the end, the imported Godot scene will contain the animations in "
"a ``AnimationPlayer`` node."
msgstr ""

#: ../../docs/tutorials/animation/animation_tree.rst:29
msgid ""
"As you rarely use imported scenes directly in Godot (they are either "
"instantiated or inherited from), you can place the ``AnimationTree`` node in "
"your new scene which contains the imported one. Afterwards, point the "
"``AnimationTree`` node to the ``AnimationPlayer`` that was created in the "
"imported scene."
msgstr ""

#: ../../docs/tutorials/animation/animation_tree.rst:32
msgid ""
"This is how it's done in the `Third Person Shooter demo <https://github.com/"
"godotengine/tps-demo>`_, for reference:"
msgstr ""

#: ../../docs/tutorials/animation/animation_tree.rst:36
msgid ""
"A new scene was created for the player with a ``CharacterBody3D`` as root. "
"Inside this scene, the original ``.dae`` (Collada) file was instantiated and "
"an ``AnimationTree`` node was created."
msgstr ""

#: ../../docs/tutorials/animation/animation_tree.rst:40
#, fuzzy
msgid "Creating a tree"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/animation/animation_tree.rst:42
msgid ""
"There are three main types of nodes that can be used in ``AnimationTree``:"
msgstr ""

#: ../../docs/tutorials/animation/animation_tree.rst:44
msgid ""
"Animation nodes, which reference an animation from the linked "
"``AnimationPlayer``."
msgstr ""

#: ../../docs/tutorials/animation/animation_tree.rst:45
msgid "Animation Root nodes, which are used to blend sub-nodes."
msgstr ""

#: ../../docs/tutorials/animation/animation_tree.rst:46
msgid ""
"Animation Blend nodes, which are used within ``AnimationNodeBlendTree`` as "
"single-graph blending via multiple input ports."
msgstr ""

#: ../../docs/tutorials/animation/animation_tree.rst:48
msgid "To set a root node in ``AnimationTree``, a few types are available:"
msgstr ""

#: ../../docs/tutorials/animation/animation_tree.rst:52
msgid ""
"``AnimationNodeAnimation``: Selects an animation from the list and plays it. "
"This is the simplest root node, and generally not used directly as root."
msgstr ""

#: ../../docs/tutorials/animation/animation_tree.rst:53
msgid ""
"``AnimationNodeBlendTree``: Contains many *blend* type nodes, such as mix, "
"blend2, blend3, one shot, etc. This is one of the most commonly used roots."
msgstr ""

#: ../../docs/tutorials/animation/animation_tree.rst:54
msgid ""
"``AnimationNodeStateMachine``: Contains multiple root nodes as children in a "
"graph. Each node is used as a *state*, and provides multiple functions to "
"alternate between states."
msgstr ""

#: ../../docs/tutorials/animation/animation_tree.rst:55
msgid ""
"``AnimationNodeBlendSpace2D``: Allows placing root nodes in a 2D blend "
"space. Control the blend position in 2D to mix between multiple animations."
msgstr ""

#: ../../docs/tutorials/animation/animation_tree.rst:56
msgid "``AnimationNodeBlendSpace1D``: Simplified version of the above (1D)."
msgstr ""

#: ../../docs/tutorials/animation/animation_tree.rst:59
msgid "Blend tree"
msgstr ""

#: ../../docs/tutorials/animation/animation_tree.rst:61
msgid ""
"An ``AnimationNodeBlendTree`` can contain both root and regular nodes used "
"for blending. Nodes are added to the graph from a menu:"
msgstr ""

#: ../../docs/tutorials/animation/animation_tree.rst:65
msgid ""
"All blend trees contain an ``Output`` node by default, and something has to "
"be connected to it in order for animations to play."
msgstr ""

#: ../../docs/tutorials/animation/animation_tree.rst:67
msgid ""
"The easiest way to test this functionality is to connect an ``Animation`` "
"node to it directly:"
msgstr ""

#: ../../docs/tutorials/animation/animation_tree.rst:71
msgid ""
"This will simply play back the animation. Make sure that the "
"``AnimationTree`` is active for something to actually happen."
msgstr ""

#: ../../docs/tutorials/animation/animation_tree.rst:73
msgid "Following is a short description of available nodes:"
msgstr ""

#: ../../docs/tutorials/animation/animation_tree.rst:76
msgid "Blend2 / Blend3"
msgstr ""

#: ../../docs/tutorials/animation/animation_tree.rst:78
msgid ""
"These nodes will blend between two or three inputs by a user-specified blend "
"value:"
msgstr ""

#: ../../docs/tutorials/animation/animation_tree.rst:82
msgid "For more complex blending, it is advised to use blend spaces instead."
msgstr ""

#: ../../docs/tutorials/animation/animation_tree.rst:84
msgid ""
"Blending can also use filters, i.e. you can control individually which "
"tracks go through the blend function. This is very useful for layering "
"animations on top of each other."
msgstr ""

#: ../../docs/tutorials/animation/animation_tree.rst:90
msgid "OneShot"
msgstr ""

#: ../../docs/tutorials/animation/animation_tree.rst:92
msgid ""
"This node will execute a sub-animation and return once it finishes. Blend "
"times for fading in and out can be customized, as well as filters."
msgstr ""

#: ../../docs/tutorials/animation/animation_tree.rst:96
msgid ""
"After setting the request and changing the animation playback, the one-shot "
"node automatically clears the request on the next process frame by setting "
"its ``request`` value to ``AnimationNodeOneShot.ONE_SHOT_REQUEST_NONE``."
msgstr ""

#: ../../docs/tutorials/animation/animation_tree.rst:128
msgid "TimeSeek"
msgstr ""

#: ../../docs/tutorials/animation/animation_tree.rst:130
msgid ""
"This node can be used to cause a seek command to happen to any sub-children "
"of the animation graph. Use this node type to play an ``Animation`` from the "
"start or a certain playback position inside the ``AnimationNodeBlendTree``."
msgstr ""

#: ../../docs/tutorials/animation/animation_tree.rst:132
msgid ""
"After setting the time and changing the animation playback, the seek node "
"automatically goes into sleep mode on the next process frame by setting its "
"``seek_request`` value to ``-1.0``."
msgstr ""

#: ../../docs/tutorials/animation/animation_tree.rst:156
msgid "TimeScale"
msgstr ""

#: ../../docs/tutorials/animation/animation_tree.rst:158
msgid ""
"Allows scaling the speed of the animation (or reverse it) connected to the "
"`in` input via the `scale` parameter. Setting the `scale` to 0 will pause "
"the animation."
msgstr ""

#: ../../docs/tutorials/animation/animation_tree.rst:161
msgid "Transition"
msgstr ""

#: ../../docs/tutorials/animation/animation_tree.rst:163
msgid ""
"Very simple state machine (when you don't want to cope with a "
"``StateMachine`` node). Animations can be connected to the outputs and "
"transition times can be specified. After setting the request and changing "
"the animation playback, the transition node automatically clears the request "
"on the next process frame by setting its ``transition_request`` value to an "
"empty string (``\"\"``)."
msgstr ""

#: ../../docs/tutorials/animation/animation_tree.rst:196
msgid "BlendSpace2D"
msgstr ""

#: ../../docs/tutorials/animation/animation_tree.rst:198
msgid ""
"``BlendSpace2D`` is a node to do advanced blending in two dimensions. Points "
"are added to a two-dimensional space and then a position can be controlled "
"to determine blending:"
msgstr ""

#: ../../docs/tutorials/animation/animation_tree.rst:203
msgid ""
"The ranges in X and Y can be controlled (and labeled for convenience). By "
"default, points can be placed anywhere (right-click on the coordinate system "
"or use the *add point* button) and triangles will be generated automatically "
"using Delaunay."
msgstr ""

#: ../../docs/tutorials/animation/animation_tree.rst:208
msgid ""
"It is also possible to draw the triangles manually by disabling the *auto "
"triangle* option, though this is rarely necessary:"
msgstr ""

#: ../../docs/tutorials/animation/animation_tree.rst:212
msgid ""
"Finally, it is possible to change the blend mode. By default, blending "
"happens by interpolating points inside the closest triangle. When dealing "
"with 2D animations (frame by frame), you may want to switch to *Discrete* "
"mode. Alternatively, if you want to keep the current play position when "
"switching between discrete animations, there is a *Carry* mode. This mode "
"can be changed in the *Blend* menu:"
msgstr ""

#: ../../docs/tutorials/animation/animation_tree.rst:220
msgid "BlendSpace1D"
msgstr ""

#: ../../docs/tutorials/animation/animation_tree.rst:222
msgid ""
"This is similar to 2D blend spaces, but in one dimension (so triangles are "
"not needed)."
msgstr ""

#: ../../docs/tutorials/animation/animation_tree.rst:225
msgid "StateMachine"
msgstr ""

#: ../../docs/tutorials/animation/animation_tree.rst:227
msgid ""
"This node acts as a state machine with root nodes as states. Root nodes can "
"be created and connected via lines. States are connected via *Transitions*, "
"which are connections with special properties. Transitions are uni-"
"directional, but two can be used to connect in both directions."
msgstr ""

#: ../../docs/tutorials/animation/animation_tree.rst:232
#, fuzzy
msgid "There are many types of transition:"
msgstr "Ne postoje ograničenja prilikom korištenja Godot-a"

#: ../../docs/tutorials/animation/animation_tree.rst:236
msgid ""
"*Immediate*: Will switch to the next state immediately. The current state "
"will end and blend into the beginning of the new one."
msgstr ""

#: ../../docs/tutorials/animation/animation_tree.rst:237
msgid ""
"*Sync*: Will switch to the next state immediately, but will seek the new "
"state to the playback position of the old state."
msgstr ""

#: ../../docs/tutorials/animation/animation_tree.rst:238
msgid ""
"*At End*: Will wait for the current state playback to end, then switch to "
"the beginning of the next state animation."
msgstr ""

#: ../../docs/tutorials/animation/animation_tree.rst:240
msgid ""
"Transitions also have a few properties. Click any transition and it will be "
"displayed in the inspector dock:"
msgstr ""

#: ../../docs/tutorials/animation/animation_tree.rst:244
msgid ""
"*Switch Mode* is the transition type (see above), it can be modified after "
"creation here."
msgstr ""

#: ../../docs/tutorials/animation/animation_tree.rst:245
msgid ""
"*Auto Advance* will turn on the transition automatically when this state is "
"reached. This works best with the *At End* switch mode."
msgstr ""

#: ../../docs/tutorials/animation/animation_tree.rst:246
msgid ""
"*Advance Condition* will turn on auto advance when this condition is set. "
"This is a custom text field that can be filled with a variable name. The "
"variable can be modified from code (more on this later)."
msgstr ""

#: ../../docs/tutorials/animation/animation_tree.rst:248
msgid "*Xfade Time* is the time to cross-fade between this state and the next."
msgstr ""

#: ../../docs/tutorials/animation/animation_tree.rst:249
msgid ""
"*Priority* is used together with the ``travel()`` function from code (more "
"on this later). Lower priority transitions are preferred when travelling "
"through the tree."
msgstr ""

#: ../../docs/tutorials/animation/animation_tree.rst:250
msgid ""
"*Disabled* toggles disabling this transition (when disabled, it will not be "
"used during travel or auto advance)."
msgstr ""

#: ../../docs/tutorials/animation/animation_tree.rst:253
msgid "For better blending"
msgstr ""

#: ../../docs/tutorials/animation/animation_tree.rst:255
msgid ""
"In Godot 4.0+, in order for the blending results to be deterministic "
"(reproducible and always consistent), the blended property values must have "
"a specific initial value. For example, in the case of two animations to be "
"blended, if one animation has a property track and the other does not, the "
"blended animation is calculated as if the latter animation had a property "
"track with the initial value."
msgstr ""

#: ../../docs/tutorials/animation/animation_tree.rst:260
msgid ""
"When using Position/Rotation/Scale 3D tracks for Skeleton3D bones, the "
"initial value is Bone Rest. For other properties, the initial value is ``0`` "
"and if the track is present in the ``RESET`` animation, the value of its "
"first keyframe is used instead."
msgstr ""

#: ../../docs/tutorials/animation/animation_tree.rst:264
msgid ""
"For example, the following AnimationPlayer has two animations, but one of "
"them lacks a Property track for Position."
msgstr ""

#: ../../docs/tutorials/animation/animation_tree.rst:268
msgid ""
"This means that the animation lacking that will treat those Positions as "
"``Vector2(0, 0)``."
msgstr ""

#: ../../docs/tutorials/animation/animation_tree.rst:272
msgid ""
"This problem can be solved by adding a Property track for Position as an "
"initial value to the ``RESET`` animation."
msgstr ""

#: ../../docs/tutorials/animation/animation_tree.rst:278
msgid ""
"Be aware that the ``RESET`` animation exists to define the default pose when "
"loading an object originally. It is assumed to have only one frame and is "
"not expected to be played back using the timeline."
msgstr ""

#: ../../docs/tutorials/animation/animation_tree.rst:281
msgid ""
"Also keep in mind that the Rotation 3D tracks and the Property tracks for 2D "
"rotation with Interpolation Type set to Linear Angle or Cubic Angle will "
"prevent rotation of more than 180 degrees from the initial value as blended "
"animation."
msgstr ""

#: ../../docs/tutorials/animation/animation_tree.rst:285
msgid ""
"This can be useful for Skeleton3Ds to prevent the bones penetrating the body "
"when blending animations. Therefore, Skeleton3D's Bone Rest values should be "
"as close to the midpoint of the movable range as possible. **This means that "
"for humanoid models, it is preferable to import them in a T-pose**."
msgstr ""

#: ../../docs/tutorials/animation/animation_tree.rst:291
msgid ""
"You can see that the shortest rotation path from Bone Rests is prioritized "
"rather than the shortest rotation path between animations."
msgstr ""

#: ../../docs/tutorials/animation/animation_tree.rst:293
msgid ""
"If you need to rotate Skeleton3D itself more than 180 degrees by blend "
"animations for movement, you can use Root Motion."
msgstr ""

#: ../../docs/tutorials/animation/animation_tree.rst:296
msgid "Root motion"
msgstr ""

#: ../../docs/tutorials/animation/animation_tree.rst:298
msgid ""
"When working with 3D animations, a popular technique is for animators to use "
"the root skeleton bone to give motion to the rest of the skeleton. This "
"allows animating characters in a way where steps actually match the floor "
"below. It also allows precise interaction with objects during cinematics."
msgstr ""

#: ../../docs/tutorials/animation/animation_tree.rst:301
msgid ""
"When playing back the animation in Godot, it is possible to select this bone "
"as the *root motion track*. Doing so will cancel the bone transformation "
"visually (the animation will stay in place)."
msgstr ""

#: ../../docs/tutorials/animation/animation_tree.rst:306
msgid ""
"Afterwards, the actual motion can be retrieved via the :ref:`AnimationTree "
"<class_AnimationTree>` API as a transform:"
msgstr ""

#: ../../docs/tutorials/animation/animation_tree.rst:333
msgid ""
"This can be fed to functions such as :ref:`CharacterBody3D.move_and_slide "
"<class_CharacterBody3D_method_move_and_slide>` to control the character "
"movement."
msgstr ""

#: ../../docs/tutorials/animation/animation_tree.rst:335
msgid ""
"There is also a tool node, ``RootMotionView``, that can be placed in a scene "
"and will act as a custom floor for your character and animations (this node "
"is disabled by default during the game)."
msgstr ""

#: ../../docs/tutorials/animation/animation_tree.rst:341
msgid "Controlling from code"
msgstr ""

#: ../../docs/tutorials/animation/animation_tree.rst:343
msgid ""
"After building the tree and previewing it, the only question remaining is "
"\"How is all this controlled from code?\"."
msgstr ""

#: ../../docs/tutorials/animation/animation_tree.rst:345
msgid ""
"Keep in mind that the animation nodes are just resources and, as such, they "
"are shared between all instances using them. Setting values in the nodes "
"directly will affect all instances of the scene that uses this "
"``AnimationTree``. This is generally undesirable, but does have some cool "
"use cases, e.g. you can copy and paste parts of your animation tree, or "
"reuse nodes with a complex layout (such as a state machine or blend space) "
"in different animation trees."
msgstr ""

#: ../../docs/tutorials/animation/animation_tree.rst:350
msgid ""
"The actual animation data is contained in the ``AnimationTree`` node and is "
"accessed via properties. Check the \"Parameters\" section of the "
"``AnimationTree`` node to see all the parameters that can be modified in "
"real-time:"
msgstr ""

#: ../../docs/tutorials/animation/animation_tree.rst:355
msgid ""
"This is handy because it makes it possible to animate them from an "
"``AnimationPlayer``, or even the ``AnimationTree`` itself, allowing the "
"realization of very complex animation logic."
msgstr ""

#: ../../docs/tutorials/animation/animation_tree.rst:358
msgid ""
"To modify these values from code, the property path must be obtained. This "
"is done easily by hovering the mouse over any of the parameters:"
msgstr ""

#: ../../docs/tutorials/animation/animation_tree.rst:362
msgid "Which allows setting them or reading them:"
msgstr ""

#: ../../docs/tutorials/animation/animation_tree.rst:376
msgid "State machine travel"
msgstr ""

#: ../../docs/tutorials/animation/animation_tree.rst:378
msgid ""
"One of the nice features in Godot's ``StateMachine`` implementation is the "
"ability to travel. The graph can be instructed to go from the current state "
"to another one, while visiting all the intermediate ones. This is done via "
"the A\\* algorithm. If there is no path of transitions starting at the "
"current state and finishing at the destination state, the graph teleports to "
"the destination state."
msgstr ""

#: ../../docs/tutorials/animation/animation_tree.rst:382
msgid ""
"To use the travel ability, you should first retrieve the :ref:"
"`AnimationNodeStateMachinePlayback "
"<class_AnimationNodeStateMachinePlayback>` object from the ``AnimationTree`` "
"node (it is exported as a property)."
msgstr ""

#: ../../docs/tutorials/animation/animation_tree.rst:394
msgid ""
"Once retrieved, it can be used by calling one of the many functions it "
"offers:"
msgstr ""

#: ../../docs/tutorials/animation/animation_tree.rst:405
msgid ""
"The state machine must be running before you can travel. Make sure to either "
"call ``start()`` or choose a node to **Autoplay on Load**."
msgstr ""

#: ../../docs/tutorials/animation/playing_videos.rst:4
msgid "Playing videos"
msgstr ""

#: ../../docs/tutorials/animation/playing_videos.rst:6
msgid ""
"Godot supports video playback with the :ref:`class_VideoStreamPlayer` node."
msgstr ""

#: ../../docs/tutorials/animation/playing_videos.rst:9
msgid "Supported playback formats"
msgstr ""

#: ../../docs/tutorials/animation/playing_videos.rst:11
msgid ""
"The only supported format in core is **Ogg Theora** (not to be confused with "
"Ogg Vorbis audio). It's possible for extensions to bring support for "
"additional formats, but no such extensions exist yet as of July 2022."
msgstr ""

#: ../../docs/tutorials/animation/playing_videos.rst:15
msgid ""
"H.264 and H.265 cannot be supported in core Godot, as they are both "
"encumbered by software patents. AV1 is royalty-free, but it remains slow to "
"decode on the CPU and hardware decoding support isn't readily available on "
"all GPUs in use yet."
msgstr ""

#: ../../docs/tutorials/animation/playing_videos.rst:20
msgid ""
"WebM was supported in core in Godot 3.x, but support for it was removed in "
"4.0 as it was too buggy and difficult to maintain."
msgstr ""

#: ../../docs/tutorials/animation/playing_videos.rst:25
msgid ""
"You may find videos with an ``.ogg`` or ``.ogx`` extensions, which are "
"generic extensions for data within an Ogg container."
msgstr ""

#: ../../docs/tutorials/animation/playing_videos.rst:28
msgid ""
"Renaming these file extensions to ``.ogv`` *may* allow the videos to be "
"imported in Godot. However, not all files with ``.ogg`` or ``.ogx`` "
"extensions are videos - some of them may only contain audio."
msgstr ""

#: ../../docs/tutorials/animation/playing_videos.rst:33
#, fuzzy
msgid "Setting up VideoStreamPlayer"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/animation/playing_videos.rst:35
msgid "Create a VideoStreamPlayer node using the Create New Node dialog."
msgstr ""

#: ../../docs/tutorials/animation/playing_videos.rst:36
msgid ""
"Select the VideoStreamPlayer node in the scene tree dock, go to the "
"inspector and load an ``.ogv`` file in the Stream property."
msgstr ""

#: ../../docs/tutorials/animation/playing_videos.rst:39
msgid ""
"If you don't have your video in Ogg Theora format yet, jump to :ref:"
"`doc_playing_videos_recommended_theora_encoding_settings`."
msgstr ""

#: ../../docs/tutorials/animation/playing_videos.rst:42
msgid ""
"If you want the video to play as soon as the scene is loaded, check "
"**Autoplay** in the inspector. If not, leave **Autoplay** disabled and call "
"``play()`` on the VideoStreamPlayer node in a script to start playback when "
"desired."
msgstr ""

#: ../../docs/tutorials/animation/playing_videos.rst:48
msgid "Handling resizing and different aspect ratios"
msgstr ""

#: ../../docs/tutorials/animation/playing_videos.rst:50
msgid ""
"By default in Godot 4.0, the VideoStreamPlayer will automatically be resized "
"to match the video's resolution. You can make it follow usual :ref:"
"`class_Control` sizing by enabling **Expand** on the VideoStreamPlayer node."
msgstr ""

#: ../../docs/tutorials/animation/playing_videos.rst:54
msgid ""
"To adjust how the VideoStreamPlayer node resizes depending on window size, "
"adjust the anchors using the **Layout** menu at the top of the 2D editor "
"viewport. However, this setup may not be powerful enough to handle all use "
"cases, such as playing fullscreen videos without distorting the video (but "
"with empty space on the edges instead). For more control, you can use an :"
"ref:`class_AspectRatioContainer` node, which is designed to handle this kind "
"of use case:"
msgstr ""

#: ../../docs/tutorials/animation/playing_videos.rst:62
msgid ""
"Add an AspectRatioContainer node. Make sure it is not a child of any other "
"container node. Select the AspectRatioContainer node, then set its "
"**Layout** at the top of the 2D editor to **Full Rect**. Set **Ratio** in "
"the AspectRatioContainer node to match your video's aspect ratio. You can "
"use math formulas in the inspector to help yourself. Remember to make one of "
"the operands a float. Otherwise, the division's result will always be an "
"integer."
msgstr ""

#: ../../docs/tutorials/animation/playing_videos.rst:74
msgid ""
"AspectRatioContainer's Ratio property being modified in the editor inspector"
msgstr ""

#: ../../docs/tutorials/animation/playing_videos.rst:74
msgid "This will evaluate to (approximately) 1.777778"
msgstr ""

#: ../../docs/tutorials/animation/playing_videos.rst:77
msgid ""
"Once you've configured the AspectRatioContainer, reparent your "
"VideoStreamPlayer node to be a child of the AspectRatioContainer node. Make "
"sure **Expand** is enabled on the VideoStreamPlayer. Your video should now "
"scale automatically to fit the whole screen while avoiding distortion."
msgstr ""

#: ../../docs/tutorials/animation/playing_videos.rst:84
msgid ""
"See :ref:`doc_multiple_resolutions` for more tips on supporting multiple "
"aspect ratios in your project."
msgstr ""

#: ../../docs/tutorials/animation/playing_videos.rst:88
msgid "Displaying a video on a 3D surface"
msgstr ""

#: ../../docs/tutorials/animation/playing_videos.rst:90
msgid ""
"Using a VideoStreamPlayer node as a child of a :ref:`class_SubViewport` "
"node, it's possible to display any 2D node on a 3D surface. For example, "
"this can be used to display animated billboards when frame-by-frame "
"animation would require too much memory."
msgstr ""

#: ../../docs/tutorials/animation/playing_videos.rst:95
#, fuzzy
msgid "This can be done with the following steps:"
msgstr "Glavna dokumentacija za sajt je podeljena na sledeća poglavlja:"

#: ../../docs/tutorials/animation/playing_videos.rst:97
msgid ""
"Create a :ref:`class_SubViewport` node. Set its size to match your video's "
"size in pixels."
msgstr ""

#: ../../docs/tutorials/animation/playing_videos.rst:99
msgid ""
"Create a VideoStreamPlayer node *as a child of the SubViewport node* and "
"specify a video path in it. Make sure **Expand** is disabled, and enable "
"**Autoplay** if needed."
msgstr ""

#: ../../docs/tutorials/animation/playing_videos.rst:101
msgid ""
"Create a MeshInstance3D node with a PlaneMesh or QuadMesh resource in its "
"Mesh property. Resize the mesh to match the video's aspect ratio (otherwise, "
"it will appear distorted)."
msgstr ""

#: ../../docs/tutorials/animation/playing_videos.rst:103
msgid ""
"Create a new StandardMaterial3D resource in the **Material Override** "
"property in the GeometryInstance3D section."
msgstr ""

#: ../../docs/tutorials/animation/playing_videos.rst:105
msgid ""
"Enable **Local To Scene** in the StandardMaterial3D's Resource section (at "
"the bottom). This is *required* before you can use a ViewportTexture in its "
"Albedo Texture property."
msgstr ""

#: ../../docs/tutorials/animation/playing_videos.rst:107
msgid ""
"In the StandardMaterial3D, set the **Albedo > Texture** property to **New "
"ViewportTexture**. Edit the new resource by clicking it, then specify the "
"path to the SubViewport node in the **Viewport Path** property."
msgstr ""

#: ../../docs/tutorials/animation/playing_videos.rst:110
msgid ""
"Enable **Albedo Texture Force sRGB** in the StandardMaterial3D to prevent "
"colors from being washed out."
msgstr ""

#: ../../docs/tutorials/animation/playing_videos.rst:112
msgid ""
"If the billboard is supposed to emit its own light, set **Shading Mode** to "
"**Unshaded** to improve rendering performance."
msgstr ""

#: ../../docs/tutorials/animation/playing_videos.rst:115
#, fuzzy
msgid ""
"See :ref:`doc_viewports` and the `GUI in 3D demo <https://github.com/"
"godotengine/godot-demo-projects/tree/master/viewport/gui_in_3d>`__ for more "
"information on setting this up."
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati različite Godo demo projekte "
"`Godot demo projects <https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/tutorials/animation/playing_videos.rst:120
#, fuzzy
msgid "Looping a video"
msgstr "Uvod / Početak"

#: ../../docs/tutorials/animation/playing_videos.rst:122
msgid ""
"For looping a video, the **Loop** property can be enabled. This will "
"seamlessly restart the video when it reaches its end."
msgstr ""

#: ../../docs/tutorials/animation/playing_videos.rst:125
msgid ""
"Note that setting the project setting **Video Delay Compensation** to a non-"
"zero value might cause your loop to not be seamless, because the "
"synchronization of audio and video takes place at the start of each loop "
"causing occasional missed frames. Set **Video Delay Compensation** in your "
"project settings to **0** to avoid frame drop issues."
msgstr ""

#: ../../docs/tutorials/animation/playing_videos.rst:132
msgid "Video decoding conditions and recommended resolutions"
msgstr ""

#: ../../docs/tutorials/animation/playing_videos.rst:134
msgid ""
"Video decoding is performed on the CPU, as GPUs don't have hardware "
"acceleration for decoding Theora videos. Modern desktop CPUs can decode Ogg "
"Theora videos at 1440p @ 60 FPS or more, but low-end mobile CPUs will likely "
"struggle with high-resolution videos."
msgstr ""

#: ../../docs/tutorials/animation/playing_videos.rst:139
msgid "To ensure your videos decode smoothly on varied hardware:"
msgstr ""

#: ../../docs/tutorials/animation/playing_videos.rst:141
msgid ""
"When developing games for desktop platforms, it's recommended to encode in "
"1080p at most (preferably at 30 FPS). Most people are still using 1080p or "
"lower resolution displays, so encoding higher-resolution videos may not be "
"worth the increased file size and CPU requirements."
msgstr ""

#: ../../docs/tutorials/animation/playing_videos.rst:145
msgid ""
"When developing games for mobile or web platforms, it's recommended to "
"encode in 720p at most (preferably at 30 FPS or even lower). The visual "
"difference between 720p and 1080p videos on a mobile device is usually not "
"that noticeable."
msgstr ""

#: ../../docs/tutorials/animation/playing_videos.rst:151
msgid "Playback limitations"
msgstr ""

#: ../../docs/tutorials/animation/playing_videos.rst:153
#, fuzzy
msgid ""
"There are several limitations with the current implementation of video "
"playback in Godot:"
msgstr "Ne postoje ograničenja prilikom korištenja Godot-a"

#: ../../docs/tutorials/animation/playing_videos.rst:155
msgid "Seeking a video to a certain point is not supported."
msgstr ""

#: ../../docs/tutorials/animation/playing_videos.rst:156
msgid ""
"Changing playback speed is not supported. VideoStreamPlayer also won't "
"follow :ref:`Engine.time_scale<class_Engine_property_time_scale>`."
msgstr ""

#: ../../docs/tutorials/animation/playing_videos.rst:158
msgid "Streaming a video from a URL is not supported."
msgstr ""

#: ../../docs/tutorials/animation/playing_videos.rst:163
msgid "Recommended Theora encoding settings"
msgstr ""

#: ../../docs/tutorials/animation/playing_videos.rst:165
msgid ""
"A word of advice is to **avoid relying on built-in Ogg Theora exporters** "
"(most of the time). There are 2 reasons you may want to favor using an "
"external program to encode your video:"
msgstr ""

#: ../../docs/tutorials/animation/playing_videos.rst:168
msgid ""
"Some programs such as Blender can render to Ogg Theora. However, the default "
"quality presets are usually very low by today's standards. You may be able "
"to increase the quality options in the software you're using, but you may "
"find the output quality to remain less than ideal (given the increased file "
"size). This usually means that the software only supports encoding to "
"constant bit rate (CBR), instead of variable bit rate (VBR). VBR encoding "
"should be preferred in most scenarios as it provides a better quality to "
"file size ratio."
msgstr ""

#: ../../docs/tutorials/animation/playing_videos.rst:176
msgid "Some other programs can't render to Ogg Theora at all."
msgstr ""

#: ../../docs/tutorials/animation/playing_videos.rst:178
msgid ""
"In this case, you can **render the video to an intermediate high-quality "
"format** (such as a high-bitrate H.264 video) then re-encode it to Ogg "
"Theora. Ideally, you should use a lossless or uncompressed format as an "
"intermediate format to maximize the quality of the output Ogg Theora video, "
"but this can require a lot of disk space."
msgstr ""

#: ../../docs/tutorials/animation/playing_videos.rst:184
msgid ""
"`HandBrake <https://handbrake.fr/>`__ (GUI) and `FFmpeg <https://ffmpeg.org/"
">`__ (CLI) are popular open source tools for this purpose. FFmpeg has a "
"steeper learning curve, but it's more powerful."
msgstr ""

#: ../../docs/tutorials/animation/playing_videos.rst:188
msgid ""
"Here are example FFmpeg commands to convert a MP4 video to Ogg Theora. Since "
"FFmpeg supports a lot of input formats, you should be able to use the "
"commands below with almost any input video format (AVI, MOV, WebM, …)."
msgstr ""

#: ../../docs/tutorials/animation/playing_videos.rst:194
msgid ""
"Make sure your copy of FFmpeg is compiled with libtheora and libvorbis "
"support. You can check this by running ``ffmpeg`` without any arguments, "
"then looking at the ``configuration:`` line in the command output."
msgstr ""

#: ../../docs/tutorials/animation/playing_videos.rst:199
msgid "Balancing quality and file size"
msgstr ""

#: ../../docs/tutorials/animation/playing_videos.rst:201
msgid ""
"The **video quality** level (``-q:v``) must be between ``1`` and ``10``. "
"Quality ``6`` is a good compromise between quality and file size. If "
"encoding at a high resolution (such as 1440p or 4K), you will probably want "
"to decrease ``-q:v`` to ``5`` to keep file sizes reasonable. Since pixel "
"density is higher on a 1440p or 4K video, lower quality presets at higher "
"resolutions will look as good or better compared to low-resolution videos."
msgstr ""

#: ../../docs/tutorials/animation/playing_videos.rst:208
msgid ""
"The **audio quality** level (``-q:a``) must be between ``-1`` and ``10``. "
"Quality ``6`` provides a good compromise between quality and file size. In "
"contrast to video quality, increasing audio quality doesn't increase the "
"output file size nearly as much. Therefore, if you want the cleanest audio "
"possible, you can increase this to ``9`` to get *perceptually lossless* "
"audio. This is especially valuable if your input file already uses lossy "
"audio compression. Higher quality audio does increase the CPU usage of the "
"decoder, so it might lead to audio dropouts in case of high system load. See "
"`this page <https://wiki.hydrogenaud.io/index.php?"
"title=Recommended_Ogg_Vorbis#Recommended_Encoder_Settings>`__ for a table "
"listing Ogg Vorbis audio quality presets and their respective variable "
"bitrates."
msgstr ""

#: ../../docs/tutorials/animation/playing_videos.rst:221
msgid "FFmpeg: Convert while preserving original video resolution"
msgstr ""

#: ../../docs/tutorials/animation/playing_videos.rst:223
msgid ""
"The following command converts the video while keeping its original "
"resolution. The video and audio's bitrate will be variable to maximize "
"quality while saving space in parts of the video/audio that don't require a "
"high bitrate (such as static scenes)."
msgstr ""

#: ../../docs/tutorials/animation/playing_videos.rst:233
msgid "FFmpeg: Resize the video then convert it"
msgstr ""

#: ../../docs/tutorials/animation/playing_videos.rst:235
msgid ""
"The following command resizes a video to be 720 pixels tall (720p), while "
"preserving its existing aspect ratio. This helps decrease the file size "
"significantly if the source is recorded at a higher resolution than 720p:"
msgstr ""

#: ../../docs/tutorials/animation/playing_videos.rst:247
msgid "Chroma Key Videos"
msgstr ""

#: ../../docs/tutorials/animation/playing_videos.rst:249
msgid ""
"Chroma key, commonly known as the \"green screen\" or \"blue screen\" "
"effect, allows you to remove a specific color from an image or video and "
"replace it with another background. This effect is widely used in video "
"production to composite different elements together seamlessly."
msgstr ""

#: ../../docs/tutorials/animation/playing_videos.rst:253
msgid ""
"We will achieve the chroma key effect by writing a custom shader in GDScript "
"and using a `VideoStreamPlayer` node to display the video content."
msgstr ""

#: ../../docs/tutorials/animation/playing_videos.rst:256
msgid "Scene Setup"
msgstr ""

#: ../../docs/tutorials/animation/playing_videos.rst:258
msgid ""
"Ensure that the scene contains a `VideoStreamPlayer` node to play the video "
"and a `Control` node to hold the UI elements for controlling the chroma key "
"effect."
msgstr ""

#: ../../docs/tutorials/animation/playing_videos.rst:263
#, fuzzy
msgid "Writing the Custom Shader"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/animation/playing_videos.rst:265
msgid "To implement the chroma key effect, follow these steps:"
msgstr ""

#: ../../docs/tutorials/animation/playing_videos.rst:267
msgid ""
"Select the `VideoStreamPlayer` node in the scene and go to its properties. "
"Under `CanvasItem > Material`, create a new shader named \"ChromaKeyShader."
"gdshader.\""
msgstr ""

#: ../../docs/tutorials/animation/playing_videos.rst:269
msgid ""
"In the \"ChromaKeyShader.gdshader\" file, write the custom shader code as "
"shown below:"
msgstr ""

#: ../../docs/tutorials/animation/playing_videos.rst:300
msgid ""
"The shader uses the distance calculation to identify pixels close to the "
"chroma key color and discards them, effectively removing the selected color. "
"Pixels that are slightly further away from the chroma key color are faded "
"based on the fade_factor, blending them smoothly with the surrounding "
"colors. This process creates the desired chroma key effect, making it appear "
"as if the background has been replaced with another image or video."
msgstr ""

#: ../../docs/tutorials/animation/playing_videos.rst:306
msgid ""
"The code above represents a simple demonstration of the Chroma Key shader, "
"and users can customize it according to their specific requirements."
msgstr ""

#: ../../docs/tutorials/animation/playing_videos.rst:310
msgid "UI Controls"
msgstr ""

#: ../../docs/tutorials/animation/playing_videos.rst:312
msgid ""
"To allow users to manipulate the chroma key effect in real-time, we created "
"sliders in the `Control` node. The `Control` node's script contains the "
"following functions:"
msgstr ""

#: ../../docs/tutorials/animation/playing_videos.rst:334
msgid ""
"also make sure that the range of the sliders are appropriate, our settings "
"are :"
msgstr ""

#: ../../docs/tutorials/animation/playing_videos.rst:339
#, fuzzy
msgid "Signal Handling"
msgstr "Signali"

#: ../../docs/tutorials/animation/playing_videos.rst:341
msgid ""
"Connect the appropriate signal from the UI elements to the `Control` node's "
"script. you created in the `Control` node's script to control the chroma key "
"effect. These signal handlers will update the shader's uniform variables in "
"response to user input."
msgstr ""

#: ../../docs/tutorials/animation/playing_videos.rst:346
msgid ""
"Save and run the scene to see the chroma key effect in action! With the "
"provided UI controls, you can now adjust the chroma key color, pickup range, "
"and fade amount in real-time, achieving the desired chroma key functionality "
"for your video content."
msgstr ""

#: ../../docs/tutorials/animation/creating_movies.rst:4
#, fuzzy
msgid "Creating movies"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/animation/creating_movies.rst:6
msgid ""
"Godot can record **non-real-time** video and audio from any 2D or 3D "
"project. This kind of recording is also called *offline rendering*. There "
"are many scenarios where this is useful:"
msgstr ""

#: ../../docs/tutorials/animation/creating_movies.rst:10
msgid "Recording game trailers for promotional use."
msgstr ""

#: ../../docs/tutorials/animation/creating_movies.rst:11
msgid ""
"Recording cutscenes that will be :ref:`displayed as pre-recorded videos "
"<doc_playing_videos>` in the final game. This allows for using higher "
"quality settings (at the cost of file size), regardless of the player's "
"hardware."
msgstr ""

#: ../../docs/tutorials/animation/creating_movies.rst:14
msgid ""
"Recording procedurally generated animations or motion design. User "
"interaction remains possible during video recording, and audio can be "
"included as well (although you won't be able to hear it while the video is "
"recording)."
msgstr ""

#: ../../docs/tutorials/animation/creating_movies.rst:17
msgid ""
"Comparing the visual output of graphics settings, shaders, or rendering "
"techniques in an animated scene."
msgstr ""

#: ../../docs/tutorials/animation/creating_movies.rst:20
msgid ""
"With Godot's animation features such as the AnimationPlayer node, Tweeners, "
"particles and shaders, it can effectively be used to create any kind of 2D "
"and 3D animations (and still images)."
msgstr ""

#: ../../docs/tutorials/animation/creating_movies.rst:24
msgid ""
"If you are already used to Godot's workflow, you may find yourself more "
"productive by using Godot for video rendering compared to Blender. That "
"said, renderers designed for non-real-time usage such as Cycles and Eevee "
"can result in better visuals (at the cost of longer rendering times)."
msgstr ""

#: ../../docs/tutorials/animation/creating_movies.rst:29
msgid ""
"Compared to real-time video recording, some advantages of non-real-time "
"recording include:"
msgstr ""

#: ../../docs/tutorials/animation/creating_movies.rst:31
msgid ""
"Use any graphics settings (including extremely demanding settings) "
"regardless of your hardware's capabilities. The output video will *always* "
"have perfect frame pacing; it will never exhibit dropped frames or "
"stuttering. Faster hardware will allow you to render a given animation in "
"less time, but the visual output remains identical."
msgstr ""

#: ../../docs/tutorials/animation/creating_movies.rst:36
msgid ""
"Render at a higher resolution than the screen resolution, without having to "
"rely on driver-specific tools such as NVIDIA's Dynamic Super Resolution or "
"AMD's Virtual Super Resolution."
msgstr ""

#: ../../docs/tutorials/animation/creating_movies.rst:39
msgid ""
"Render at a higher framerate than the video's target framerate, then :ref:"
"`post-process to generate high-quality motion blur "
"<doc_creating_movies_motion_blur>`. This also makes effects that converge "
"over several frames (such as temporal antialiasing, SDFGI and volumetric "
"fog) look better."
msgstr ""

#: ../../docs/tutorials/animation/creating_movies.rst:46
msgid ""
"**This feature is not designed for capturing real-time footage during "
"gameplay.**"
msgstr ""

#: ../../docs/tutorials/animation/creating_movies.rst:48
msgid ""
"Players should use something like `OBS Studio <https://obsproject.com/>`__ "
"or `SimpleScreenRecorder <https://www.maartenbaert.be/simplescreenrecorder/"
">`__ to record gameplay videos, as they do a much better job at intercepting "
"the compositor than Godot can do using Vulkan or OpenGL natively."
msgstr ""

#: ../../docs/tutorials/animation/creating_movies.rst:53
msgid ""
"That said, if your game runs at near-real-time speeds when capturing, you "
"can still use this feature (but it will lack audible sound playback, as "
"sound is saved directly to the video file)."
msgstr ""

#: ../../docs/tutorials/animation/creating_movies.rst:58
msgid "Enabling Movie Maker mode"
msgstr ""

#: ../../docs/tutorials/animation/creating_movies.rst:60
msgid ""
"To enable Movie Maker mode, click the \"movie reel\" button in the top-right "
"corner of the editor *before* running the project:"
msgstr ""

#: ../../docs/tutorials/animation/creating_movies.rst:67
msgid "Movie Maker mode is disabled, click the \"movie reel\" icon to enable"
msgstr ""

#: ../../docs/tutorials/animation/creating_movies.rst:69
msgid ""
"The icon gets a background matching the accent color when Movie Maker mode "
"is enabled:"
msgstr ""

#: ../../docs/tutorials/animation/creating_movies.rst:76
msgid ""
"Movie Maker mode is enabled, click the \"movie reel\" icon again to disable"
msgstr ""

#: ../../docs/tutorials/animation/creating_movies.rst:78
msgid ""
"Movie Maker status is **not** persisted when the editor quits, so you must "
"re-enable Movie Maker mode again after restarting the editor if needed."
msgstr ""

#: ../../docs/tutorials/animation/creating_movies.rst:83
msgid ""
"Toggling Movie Maker mode while running the project will not have any effect "
"until the project is restarted."
msgstr ""

#: ../../docs/tutorials/animation/creating_movies.rst:86
msgid ""
"Before you can record video by running the project, you still need to "
"configure the output file path. This path can be set for all scenes in the "
"Project Settings:"
msgstr ""

#: ../../docs/tutorials/animation/creating_movies.rst:93
msgid "Movie Maker project settings (with Advanced toggle enabled)"
msgstr ""

#: ../../docs/tutorials/animation/creating_movies.rst:95
msgid ""
"Alternatively, you can set the output file path on a per-scene basis by "
"adding a String metadata with the name ``movie_file`` to the scene's **root "
"node**. This is only used when the main scene is set to the scene in "
"question, or when running the scene directly by pressing :kbd:`F6` (:kbd:"
"`Cmd + R` on macOS)."
msgstr ""

#: ../../docs/tutorials/animation/creating_movies.rst:104
msgid "Inspector view after creating a ``movie_file`` metadata of type String"
msgstr ""

#: ../../docs/tutorials/animation/creating_movies.rst:106
msgid ""
"The path specified in the project settings or metadata can be either "
"absolute, or relative to the project root."
msgstr ""

#: ../../docs/tutorials/animation/creating_movies.rst:109
msgid ""
"Once you've configured and enabled Movie Maker mode, it will be "
"automatically used when running the project from the editor."
msgstr ""

#: ../../docs/tutorials/animation/creating_movies.rst:113
msgid "Command line usage"
msgstr ""

#: ../../docs/tutorials/animation/creating_movies.rst:115
msgid ""
"Movie Maker can also be enabled from the :ref:`command line "
"<doc_command_line_tutorial>`:"
msgstr ""

#: ../../docs/tutorials/animation/creating_movies.rst:121
msgid ""
"If the output path is relative, then it is **relative to the project "
"folder**, not the current working directory. In the above example, the file "
"will be written to ``/path/to/your_project/output.avi``. This behavior is "
"similar to the ``--export`` command line argument."
msgstr ""

#: ../../docs/tutorials/animation/creating_movies.rst:126
msgid ""
"Since Movie Maker's output resolution is set by the viewport size, you can "
"adjust the window size on startup to override it if the project uses the "
"``disabled`` or ``canvas_items`` :ref:`stretch mode "
"<doc_multiple_resolutions>`:"
msgstr ""

#: ../../docs/tutorials/animation/creating_movies.rst:134
msgid ""
"Note that the window size is clamped by your display's resolution. See :ref:"
"`doc_creating_movies_recording_at_higher_resolution` if you need to record a "
"video at a higher resolution than the screen resolution."
msgstr ""

#: ../../docs/tutorials/animation/creating_movies.rst:138
msgid ""
"The recording FPS can also be overridden on the command line, without having "
"to edit the Project Settings:"
msgstr ""

#: ../../docs/tutorials/animation/creating_movies.rst:147
msgid ""
"The ``--write-movie`` and ``--fixed-fps`` command line arguments are both "
"available in exported projects. Movie Maker mode cannot be toggled while the "
"project is running, but you can use the :ref:`OS.execute() "
"<class_OS_method_execute>` method to run a second instance of the exported "
"project that will record a video file."
msgstr ""

#: ../../docs/tutorials/animation/creating_movies.rst:153
msgid "Choosing an output format"
msgstr ""

#: ../../docs/tutorials/animation/creating_movies.rst:155
msgid ""
"Output formats are provided by the :ref:`MovieWriter <class_MovieWriter>` "
"class. Godot has 2 built-in :ref:`MovieWriters <class_MovieWriter>`, and "
"more can be implemented by extensions:"
msgstr ""

#: ../../docs/tutorials/animation/creating_movies.rst:160
msgid "AVI (recommended)"
msgstr ""

#: ../../docs/tutorials/animation/creating_movies.rst:162
msgid ""
"AVI container with MJPEG for video and uncompressed audio. Features lossy "
"video compression, resulting in medium file sizes and fast encoding. The "
"lossy compression quality can be adjusted by changing **Editor > Movie "
"Writer > MJPEG Quality**."
msgstr ""

#: ../../docs/tutorials/animation/creating_movies.rst:167
msgid ""
"The resulting file can be viewed in most video players, but it must be "
"converted to another format for viewing on the web or by Godot with the "
"VideoStreamPlayer node. MJPEG does not support transparency. AVI output is "
"currently limited to a file of 4 GB in size at most."
msgstr ""

#: ../../docs/tutorials/animation/creating_movies.rst:172
msgid ""
"To use AVI, specify a path to an ``.avi`` file to be created in the **Editor "
"> Movie Writer > Movie File** project setting."
msgstr ""

#: ../../docs/tutorials/animation/creating_movies.rst:176
msgid "PNG"
msgstr ""

#: ../../docs/tutorials/animation/creating_movies.rst:178
msgid ""
"PNG image sequence for video and WAV for audio. Features lossless video "
"compression, at the cost of large file sizes and slow encoding. This is "
"designed to be :ref:`encoded to a video file with an external tool after "
"recording <doc_creating_movies_converting_avi>`."
msgstr ""

#: ../../docs/tutorials/animation/creating_movies.rst:183
msgid ""
"Transparency is supported, but the root viewport **must** have its "
"``transparent_bg`` property set to ``true`` for transparency to be visible "
"on the output image. This can be achieved by enabling the **Rendering > "
"Transparent Background** advanced project setting. **Display > Window > Size "
"> Transparent** and **Display > Window > Per Pixel Transparency > Enabled** "
"can optionally be enabled to allow transparency to be previewed while "
"recording the video, but they do not have to be enabled for the output image "
"to contain transparency."
msgstr ""

#: ../../docs/tutorials/animation/creating_movies.rst:191
msgid ""
"To use PNG, specify a ``.png`` file to be created in the **Editor > Movie "
"Writer > Movie File** project setting. The generated ``.wav`` file will have "
"the same name as the ``.png`` file (minus the extension)."
msgstr ""

#: ../../docs/tutorials/animation/creating_movies.rst:196
#, fuzzy
msgid "Custom"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/animation/creating_movies.rst:198
msgid ""
"If you need to encode directly to a different format or pipe a stream "
"through third-party software, you can extend the MovieWriter class to create "
"your own movie writers. This should typically be done using GDExtension for "
"performance reasons."
msgstr ""

#: ../../docs/tutorials/animation/creating_movies.rst:204
#: ../../docs/tutorials/plugins/editor/import_plugins.rst:32
msgid "Configuration"
msgstr ""

#: ../../docs/tutorials/animation/creating_movies.rst:206
msgid ""
"In the **Editor > Movie Writer** section of the Project Settings, there are "
"several options you can configure. Some of them are only visible after "
"enabling the **Advanced** toggle in the top-right corner of the Project "
"Settings dialog."
msgstr ""

#: ../../docs/tutorials/animation/creating_movies.rst:210
msgid ""
"**Mix Rate Hz:** The audio mix rate to use in the recorded audio when "
"writing a movie. This can be different from the project's mix rate, but this "
"value must be divisible by the recorded FPS to prevent audio from "
"desynchronizing over time."
msgstr ""

#: ../../docs/tutorials/animation/creating_movies.rst:214
msgid ""
"**Speaker Mode:** The speaker mode to use in the recorded audio when writing "
"a movie (stereo, 5.1 surround or 7.1 surround)."
msgstr ""

#: ../../docs/tutorials/animation/creating_movies.rst:216
msgid ""
"**MJPEG Quality:** The JPEG quality to use when writing a video to an AVI "
"file, between ``0.01`` and ``1.0`` (inclusive). Higher quality values result "
"in better-looking output at the cost of larger file sizes. Recommended "
"quality values are between ``0.75`` and ``0.9``. Even at quality ``1.0``, "
"JPEG compression remains lossy. This setting does not affect audio quality "
"and is ignored when writing to a PNG image sequence."
msgstr ""

#: ../../docs/tutorials/animation/creating_movies.rst:222
msgid ""
"**Movie File:** The output path for the movie. This can be absolute or "
"relative to the project root."
msgstr ""

#: ../../docs/tutorials/animation/creating_movies.rst:224
msgid ""
"**Disable V-Sync:** If enabled, requests V-Sync to be disabled when writing "
"a movie. This can speed up video writing if the hardware is fast enough to "
"render, encode and save the video at a framerate higher than the monitor's "
"refresh rate. This setting has no effect if the operating system or graphics "
"driver forces V-Sync with no way for applications to disable it."
msgstr ""

#: ../../docs/tutorials/animation/creating_movies.rst:229
msgid ""
"**FPS:** The rendered frames per second in the output movie. Higher values "
"result in smoother animation, at the cost of longer rendering times and "
"larger output file sizes. Most video hosting platforms do not support FPS "
"values higher than 60, but you can use a higher value and use that to "
"generate motion blur."
msgstr ""

#: ../../docs/tutorials/animation/creating_movies.rst:237
msgid ""
"When using the ``disabled`` or ``2d`` :ref:`stretch modes "
"<doc_multiple_resolutions>`, the output file's resolution is set by the "
"window size. Make sure to resize the window *before* the splash screen has "
"ended. For this purpose, it's recommended to adjust the **Display > Window > "
"Size > Window Width Override** and **Window Height Override** advanced "
"project settings."
msgstr ""

#: ../../docs/tutorials/animation/creating_movies.rst:244
msgid "See also :ref:`doc_creating_movies_recording_at_higher_resolution`."
msgstr ""

#: ../../docs/tutorials/animation/creating_movies.rst:247
msgid "Quitting Movie Maker mode"
msgstr ""

#: ../../docs/tutorials/animation/creating_movies.rst:249
msgid ""
"To safely quit a project that is using Movie Maker mode, use the X button at "
"the top of the window, or call ``get_tree().quit()`` in a script. You can "
"also use the ``--quit-after N`` command line argument where ``N`` is the "
"number of frames to render before quitting."
msgstr ""

#: ../../docs/tutorials/animation/creating_movies.rst:254
msgid ""
"Pressing :kbd:`F8` (:kbd:`Cmd + .` on macOS) or pressing :kbd:`Ctrl + C` on "
"the terminal running Godot is **not recommended**, as it will result in an "
"improperly formatted AVI file with no duration information. For PNG image "
"sequences, PNG images will not be negatively altered, but the associated WAV "
"file will still lack duration information."
msgstr ""

#: ../../docs/tutorials/animation/creating_movies.rst:260
msgid ""
"Some video players may still be able to play the AVI or WAV file with "
"working video and audio. However, software that makes use of the AVI or WAV "
"file such as video editors may not be able to open the file. :ref:`Using a "
"video converter program <doc_creating_movies_converting_avi>` can help in "
"those cases."
msgstr ""

#: ../../docs/tutorials/animation/creating_movies.rst:266
msgid ""
"If you're using an AnimationPlayer to control a \"main action\" in the scene "
"(such as camera movement), you can enable the **Movie Quit On Finish** "
"property on the AnimationPlayer node in question. When enabled, this "
"property will make Godot quit on its own when an animation is done playing "
"*and* the engine is running in Movie Maker mode. Note that *this property "
"has no effect on looping animations*. Therefore, you need to make sure that "
"the animation is set as non-looping."
msgstr ""

#: ../../docs/tutorials/animation/creating_movies.rst:274
msgid "Using high-quality graphics settings"
msgstr ""

#: ../../docs/tutorials/animation/creating_movies.rst:276
msgid ""
"The ``movie`` :ref:`feature tag <doc_feature_tags>` can be used to override "
"specific project settings. This is useful to enable high-quality graphics "
"settings that wouldn't be fast enough to run in real-time speeds on your "
"hardware. Remember that putting every setting to its maximum value can still "
"slow down movie saving speed, especially when recording at higher "
"resolutions. Therefore, it's still recommended to only increase graphics "
"settings if they make a meaningful difference in the output image."
msgstr ""

#: ../../docs/tutorials/animation/creating_movies.rst:284
msgid ""
"This feature tag can also be queried in a script to increase quality "
"settings that are set in the Environment resource. For example, to further "
"improve SDFGI detail and reduce light leaking:"
msgstr ""

#: ../../docs/tutorials/animation/creating_movies.rst:302
msgid "Rendering at a higher resolution than the screen resolution"
msgstr ""

#: ../../docs/tutorials/animation/creating_movies.rst:304
msgid ""
"The overall rendering quality can be improved significantly by rendering at "
"high resolutions such as 4K or 8K."
msgstr ""

#: ../../docs/tutorials/animation/creating_movies.rst:309
msgid ""
"For 3D rendering, Godot provides a **Rendering > Scaling 3D > Scale** "
"advanced project setting, which can be set above ``1.0`` to obtain "
"*supersample antialiasing*. The 3D rendering is then *downsampled* when it's "
"drawn on the viewport. This provides an expensive but high-quality form of "
"antialiasing, without increasing the final output resolution."
msgstr ""

#: ../../docs/tutorials/animation/creating_movies.rst:315
msgid ""
"Consider using this project setting first, as it avoids slowing down movie "
"writing speeds and increasing output file size compared to actually "
"increasing the output resolution."
msgstr ""

#: ../../docs/tutorials/animation/creating_movies.rst:319
msgid ""
"If you wish to render 2D at a higher resolution, or if you actually need the "
"higher raw pixel output for 3D rendering, you can increase the resolution "
"above what the screen allows."
msgstr ""

#: ../../docs/tutorials/animation/creating_movies.rst:323
msgid ""
"By default, Godot uses the ``disabled`` :ref:`stretch modes "
"<doc_multiple_resolutions>` in projects. If using ``disabled`` or "
"``canvas_items`` stretch mode, the window size dictates the output video "
"resolution."
msgstr ""

#: ../../docs/tutorials/animation/creating_movies.rst:327
msgid ""
"On the other hand, if the project is configured to use the ``viewport`` "
"stretch mode, the viewport resolution dictates the output video resolution. "
"The viewport resolution is set using the **Display > Window > Size > "
"Viewport Width** and **Viewport Height** project settings. This can be used "
"to render a video at a higher resolution than the screen resolution."
msgstr ""

#: ../../docs/tutorials/animation/creating_movies.rst:333
msgid ""
"To make the window smaller during recording without affecting the output "
"video resolution, you can set the **Display > Window > Size > Window Width "
"Override** and **Window Height Override** advanced project settings to "
"values greater than ``0``."
msgstr ""

#: ../../docs/tutorials/animation/creating_movies.rst:338
msgid ""
"To apply a resolution override only when recording a movie, you can override "
"those settings with the ``movie`` :ref:`feature tag <doc_feature_tags>`."
msgstr ""

#: ../../docs/tutorials/animation/creating_movies.rst:342
msgid "Post-processing steps"
msgstr ""

#: ../../docs/tutorials/animation/creating_movies.rst:344
msgid "Some common post-processing steps are listed below."
msgstr ""

#: ../../docs/tutorials/animation/creating_movies.rst:348
msgid ""
"When using several post-processing steps, try to perform all of them in a "
"single FFmpeg command. This will save encoding time and improve quality by "
"avoiding multiple lossy encoding steps."
msgstr ""

#: ../../docs/tutorials/animation/creating_movies.rst:355
msgid "Converting AVI video to MP4"
msgstr ""

#: ../../docs/tutorials/animation/creating_movies.rst:357
msgid ""
"While some platforms such as YouTube support uploading the AVI file "
"directly, many others will require a conversion step beforehand. `HandBrake "
"<https://handbrake.fr/>`__ (GUI) and `FFmpeg <https://ffmpeg.org/>`__ (CLI) "
"are popular open source tools for this purpose. FFmpeg has a steeper "
"learning curve, but it's more powerful."
msgstr ""

#: ../../docs/tutorials/animation/creating_movies.rst:362
msgid ""
"The command below converts an AVI video to a MP4 (H.264) video with a "
"Constant Rate Factor (CRF) of 15. This results in a relatively large file, "
"but is well-suited for platforms that will re-encode your videos to reduce "
"their size (such as most video sharing websites):"
msgstr ""

#: ../../docs/tutorials/animation/creating_movies.rst:371
msgid ""
"To get a smaller file at the cost of quality, *increase* the CRF value in "
"the above command."
msgstr ""

#: ../../docs/tutorials/animation/creating_movies.rst:374
msgid ""
"To get a file with a better size/quality ratio (at the cost of slower "
"encoding times), add ``-preset veryslow`` before ``-crf 15`` in the above "
"command. On the contrary, ``-preset veryfast`` can be used to achieve faster "
"encoding at the cost of a worse size/quality ratio."
msgstr ""

#: ../../docs/tutorials/animation/creating_movies.rst:382
msgid "Converting PNG image sequence + WAV audio to a video"
msgstr ""

#: ../../docs/tutorials/animation/creating_movies.rst:384
msgid ""
"If you chose to record a PNG image sequence with a WAV file beside it, you "
"need to convert it to a video before you can use it elsewhere."
msgstr ""

#: ../../docs/tutorials/animation/creating_movies.rst:387
msgid ""
"The filename for the PNG image sequence generated by Godot always contains 8 "
"digits, starting at 0 with zero-padded numbers. If you specify an output "
"path ``folder/example.png``, Godot will write ``folder/example00000000."
"png``, ``folder/example00000001.png``, and so on in that folder. The audio "
"will be saved at ``folder/example.wav``."
msgstr ""

#: ../../docs/tutorials/animation/creating_movies.rst:393
msgid ""
"The FPS is specified using the ``-r`` argument. It should match the FPS "
"specified during recording. Otherwise, the video will appear to be slowed "
"down or sped up, and audio will be out of sync with the video."
msgstr ""

#: ../../docs/tutorials/animation/creating_movies.rst:401
msgid ""
"If you recorded a PNG image sequence with transparency enabled, you need to "
"use a video format that supports storing transparency. MP4/H.264 doesn't "
"support storing transparency, so you can use WebM/VP9 as an alternative:"
msgstr ""

#: ../../docs/tutorials/animation/creating_movies.rst:412
#, fuzzy
msgid "Cutting video"
msgstr "Uvod / Početak"

#: ../../docs/tutorials/animation/creating_movies.rst:414
msgid ""
"You can trim parts of the video you don't want to keep after the video is "
"recorded. For example, to discard everything before 12.1 seconds and keep "
"only 5.2 seconds of video after that point:"
msgstr ""

#: ../../docs/tutorials/animation/creating_movies.rst:422
msgid ""
"Cutting videos can also be done with the GUI tool `LosslessCut <https://mifi."
"github.io/lossless-cut/>`__."
msgstr ""

#: ../../docs/tutorials/animation/creating_movies.rst:426
msgid "Resizing video"
msgstr ""

#: ../../docs/tutorials/animation/creating_movies.rst:428
msgid ""
"The following command resizes a video to be 1080 pixels tall (1080p), while "
"preserving its existing aspect ratio:"
msgstr ""

#: ../../docs/tutorials/animation/creating_movies.rst:439
#, fuzzy
msgid "Reducing framerate"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/animation/creating_movies.rst:441
msgid ""
"The following command changes a video's framerate to 30 FPS, dropping some "
"of the original frames if there are more in the input video:"
msgstr ""

#: ../../docs/tutorials/animation/creating_movies.rst:449
msgid "Generating accumulation motion blur with FFmpeg"
msgstr ""

#: ../../docs/tutorials/animation/creating_movies.rst:451
msgid ""
"Godot does not have built-in support for motion blur, but it can still be "
"created in recorded videos."
msgstr ""

#: ../../docs/tutorials/animation/creating_movies.rst:454
msgid ""
"If you record the video at a multiple of the original framerate, you can "
"blend the frames together then reduce the frameate to produce a video with "
"*accumulation motion blur*. This motion blur can look very good, but it can "
"take a long time to generate since you have to render many more frames per "
"second (on top of the time spent on post-processing)."
msgstr ""

#: ../../docs/tutorials/animation/creating_movies.rst:460
msgid ""
"Example with a 240 FPS source video, generating 4× motion blur and "
"decreasing its output framerate to 60 FPS:"
msgstr ""

#: ../../docs/tutorials/animation/creating_movies.rst:467
msgid ""
"This also makes effects that converge over several frames (such as temporal "
"antialiasing, SDFGI and volumetric fog) converge faster and therefore look "
"better, since they'll be able to work with more data at a given time. See :"
"ref:`doc_creating_movies_reducing_framerate` if you want to get this benefit "
"without adding motion blur."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/import_process.rst:4
msgid "Import process"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/import_process.rst:7
#, fuzzy
msgid "Importing assets in Godot"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/assets_pipeline/import_process.rst:9
msgid ""
"To import assets in Godot, place your assets (image files, scenes, audio "
"files, fonts, etc) directly in the project folder. There are 2 ways to "
"achieve this:"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/import_process.rst:12
msgid ""
"**For any file type:** Copy files manually with your operating system's file "
"manager."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/import_process.rst:13
msgid ""
"**For file types that can be imported by Godot:** Drag-and-drop files from "
"the operating system's file manager to the editor's FileSystem dock. This "
"only works with *resource* file types (i.e. file types that Godot can "
"import)."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/import_process.rst:17
msgid ""
"Godot will automatically import these files internally and keep the imported "
"resources hidden in a ``res://.godot/imported/`` folder."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/import_process.rst:20
msgid ""
"This means that when trying to access imported assets through code, you need "
"to use the :ref:`Resource Loader<class_ResourceLoader>` as it will "
"automatically take into account where the internal files are saved. If you "
"try and access an imported asset using the :ref:`FileAccess "
"<class_FileAccess>` class, it will work in the editor, but **it will break "
"in the exported project**."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/import_process.rst:26
msgid ""
"However, the :ref:`Resource Loader<class_ResourceLoader>` cannot access non-"
"imported files. Only the :ref:`FileAccess <class_FileAccess>` class can."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/import_process.rst:30
msgid "Changing import parameters"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/import_process.rst:34
msgid ""
"Import parameters are only present in *non-native* Godot resource types. "
"This means Godot's own scene and resource file formats (``.tscn``, ``.scn``, "
"``.tres``, ``.res``) don't have import options you can select in the Import "
"dock."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/import_process.rst:39
msgid ""
"To change the import parameters of an asset in Godot, select the relevant "
"resource in the FileSystem dock:"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/import_process.rst:44
msgid ""
"After adjusting the parameters, click **Reimport**. Be careful: if you "
"select another file in the FileSystem dock before clicking **Reimport**, "
"changes will be discarded. After clicking **Reimport**, the chosen "
"parameters will only be used for this asset and on future reimports."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/import_process.rst:49
msgid ""
"Changing the import parameters of several assets at the same time is also "
"possible. Simply select all of them together in the resources dock and the "
"exposed parameters will apply to all of them when reimporting."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/import_process.rst:54
msgid "Reimporting multiple assets"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/import_process.rst:56
msgid ""
"While working on a project you may find that several assets need to have the "
"same parameters changed, such as enabling mipmaps, but you only want those "
"specific parameters changed. To do this, select every asset you want to "
"reimport in the file system. In the import tab there will now be a checkbox "
"to the left of every import parameter."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/import_process.rst:64
msgid ""
"Select the checkbox of the parameters you want to change on your imported "
"assets, then change the parameters normally. Finally, click the reimport "
"button and every selected asset will be reimported with only those "
"parameters changed."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/import_process.rst:70
msgid "Automatic reimport"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/import_process.rst:72
msgid ""
"When the MD5 checksum of the source asset changes, Godot will perform an "
"automatic reimport of it, applying the preset configured for that specific "
"asset."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/import_process.rst:77
msgid "Files generated"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/import_process.rst:79
msgid ""
"Importing will add an extra ``<asset>.import`` file next to the source file, "
"containing the import configuration."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/import_process.rst:82
msgid ""
"**Make sure to commit these files to your version control system**, as these "
"files contain important metadata."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/import_process.rst:92
msgid ""
"Additionally, extra assets will be present in the hidden ``res://.godot/"
"imported/`` folder:"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/import_process.rst:101
msgid ""
"If any of the files present in this folder is erased (or the whole folder), "
"the asset or assets will be reimported automatically. As such, committing "
"the ``.godot/`` folder to the version control system is not recommended. "
"While committing this folder can shorten reimporting time when checking out "
"on another computer, it requires considerably more space and bandwidth."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/import_process.rst:107
msgid ""
"The default version control metadata that can be generated on project "
"creation will automatically ignore the ``.godot/`` folder."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/import_process.rst:111
msgid "Changing import resource type"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/import_process.rst:113
msgid ""
"Some source assets can be imported as different types of resources. For "
"this, select the relevant type of resource desired then click **Reimport**:"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/import_process.rst:119
msgid "Changing default import parameters"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/import_process.rst:121
msgid ""
"Different types of projects might require different defaults. Changing the "
"import options to a predefined set of options can be achieved by using the "
"**Preset...** Menu. Besides some resource types offering presets, the "
"default settings can be saved and cleared too:"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/import_process.rst:128
msgid ""
"The default import parameters for a given resource type can be changed "
"project-wide using the **Import Defaults** tab of the Project Settings "
"dialog:"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/import_process.rst:134
msgid "Further reading"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/import_process.rst:136
msgid ""
"This workflow takes a little time to get used to, but it enforces a more "
"correct way to deal with resources."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/import_process.rst:139
msgid ""
"There are many types of assets available for import. Continue reading to "
"understand how to work with all of them:"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/import_process.rst:142
#, fuzzy
msgid ":ref:`doc_importing_images`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/assets_pipeline/import_process.rst:143
#, fuzzy
msgid ":ref:`doc_importing_audio_samples`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/assets_pipeline/import_process.rst:144
#, fuzzy
msgid ":ref:`doc_importing_3d_scenes`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/assets_pipeline/import_process.rst:145
#, fuzzy
msgid ":ref:`doc_importing_translations`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:4
msgid "Importing images"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:7
msgid "Supported image formats"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:9
msgid "Godot can import the following image formats:"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:11
msgid ""
"BMP (``.bmp``) - No support for 16-bit per pixel images. Only 1-bit, 4-bit, "
"8-bit, 24-bit, and 32-bit per pixel images are supported."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:13
msgid ""
"DirectDraw Surface (``.dds``) - If mipmaps are present in the texture, they "
"will be loaded directly. This can be used to achieve effects using custom "
"mipmaps."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:16
msgid ""
"Khronos Texture (``.ktx``) - Decoding is done using `libktx <https://github."
"com/KhronosGroup/KTX-Software>`__. Only supports 2D images. Cubemaps, "
"texture arrays and de-padding are not supported."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:19
msgid ""
"OpenEXR (``.exr``) - Supports HDR (highly recommended for panorama skies)."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:21
msgid ""
"Radiance HDR (``.hdr``) - Supports HDR (highly recommended for panorama "
"skies)."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:23
msgid ""
"JPEG (``.jpg``, ``.jpeg``) - Doesn't support transparency per the format's "
"limitations."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:25
msgid ""
"PNG (``.png``) - Precision is limited to 8 bits per channel upon importing "
"(no HDR images)."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:27
msgid "Truevision Targa (``.tga``)"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:28
msgid ""
"SVG (``.svg``) - SVGs are rasterized using `ThorVG <https://www.thorvg.org/"
">`__ when importing them. `Support is limited <https://www.thorvg.org/about#:"
"~:"
"text=among%20the%20svg%20tiny%20specs%2C%20yet%20unsupported%20features%20in%20the%20thorvg%20are%20the%20following>`__; "
"complex vectors may not render correctly. :ref:`Text must be converted to "
"paths <doc_importing_images_svg_text>`; otherwise, it won't appear in the "
"rasterized image. You can check whether ThorVG can render a certain vector "
"correctly using its `web-based viewer <https://www.thorvg.org/viewer>`__. "
"For complex vectors, rendering them to PNGs using `Inkscape <https://"
"inkscape.org/>`__ is often a better solution. This can be automated thanks "
"to its `command-line interface <https://wiki.inkscape.org/wiki/index.php/"
"Using_the_Command_Line#Export_files>`__."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:38
msgid ""
"WebP (``.webp``) - WebP files support transparency and can be compressed "
"lossily or losslessly. The precision is limited to 8 bits per channel."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:44
#: ../../docs/tutorials/assets_pipeline/importing_audio_samples.rst:26
msgid ""
"If you've compiled the Godot editor from source with specific modules "
"disabled, some formats may not be available."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:48
msgid "Importing textures"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:50
msgid ""
"The default action in Godot is to import images as textures. Textures are "
"stored in video memory. Their pixel data can't be accessed directly from the "
"CPU without converting them back to an :ref:`class_Image` in a script. This "
"is what makes drawing them efficient."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:55
msgid ""
"There are over a dozen import options that can be adjusted after selecting "
"an image in the FileSystem dock:"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:62
msgid ""
"Import options in the Import dock after selecting an image in the FileSystem "
"dock"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:62
msgid ""
"Import options in the Import dock after selecting an image in the FileSystem "
"dock. Some of these options are only visible with certain compression modes."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:68
msgid "Changing import type"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:70
msgid ""
"It is possible to choose other types of imported resources in the Import "
"dock:"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:72
msgid ""
"**BitMap:** 1-bit monochrome texture (intended to be used as a click mask "
"in :ref:`class_TextureButton` and :ref:`class_TouchScreenButton`). This "
"resource type cannot be displayed directly onto 2D or 3D nodes, but the "
"pixel values can be queried from a script using :ref:`get_bit "
"<class_BitMap_method_get_bit>`."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:77
msgid ""
"**Cubemap:** Import the texture as a 6-sided cubemap, with interpolation "
"between the cubemap's sides (seamless cubemaps), which can be sampled in "
"custom shaders."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:80
msgid ""
"**CubemapArray:** Import the texture as a collection of 6-sided cubemaps, "
"which can be sampled in custom shaders. This resource type can only be "
"displayed when using the Forward+ or Forward Mobile rendering methods, not "
"Compatibility."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:84
msgid ""
"**Font Data (Monospace Image Font):** Import the image as a bitmap font "
"where all characters have the same width. See :ref:`doc_gui_using_fonts`."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:86
msgid ""
"**Image:** Import the image as-is. This resource type cannot be displayed "
"directly onto 2D or 3D nodes, but the pixel values can be queried from a "
"script using :ref:`get_pixel<class_Image_method_get_pixel>`."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:89
msgid ""
"**Texture2D:** Import the image as a 2-dimensional texture, suited for "
"display on 2D and 3D surfaces. This is the default import mode."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:91
msgid ""
"**Texture2DArray:** Import the image as a collection of 2-dimensional "
"textures. Texture2DArray is similar to a 3-dimensional texture, but without "
"interpolation between layers. Built-in 2D and 3D shaders cannot display "
"texture arrays, so you must create a custom shader in :ref:`2D "
"<doc_canvas_item_shader>` or :ref:`3D <doc_spatial_shader>` to display a "
"texture from a texture array."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:96
msgid ""
"**Texture3D:** Import the image as a 3-dimensional texture. This is *not* a "
"2D texture applied onto a 3D surface. Texture3D is similar to a texture "
"array, but with interpolation between layers. Texture3D is typically used "
"for :ref:`class_FogMaterial` density maps in :ref:`volumetric fog "
"<doc_volumetric_fog>`, :ref:`class_Environment` 3D LUT color correction and "
"custom shaders."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:102
msgid ""
"**TextureAtlas:** Import the image as an *atlas* of different textures. Can "
"be used to reduce memory usage for animated 2D sprites. Only supported in 2D "
"due to missing support in built-in 3D shaders."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:107
msgid "Detect 3D"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:109
msgid ""
"The default import options (no mipmaps and **Lossless** compression) are "
"suited for 2D, but are not ideal for most 3D projects. **Detect 3D** makes "
"Godot aware of when a texture is used in a 3D scene (such as a texture in a :"
"ref:`class_BaseMaterial3D`). If this happens, several import options are "
"changed so the texture flags are friendlier to 3D. Mipmaps are enabled and "
"the compression mode is changed to **VRAM Compressed** unless :ref:"
"`doc_importing_images_detect_3d_compress_to` is changed. The texture is also "
"reimported automatically."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:118
msgid ""
"A message is printed to the Output panel when a texture is detected to be "
"used in 3D."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:120
msgid ""
"If you run into quality issues when a texture is detected to be used in 3D "
"(e.g. for pixel art textures), change the :ref:"
"`doc_importing_images_detect_3d_compress_to` option before using the texture "
"in 3D, or change :ref:`doc_importing_images_compress_mode` to **Lossless** "
"after using the texture in 3D. This is preferable to disabling **Detect "
"3D**, as mipmap generation remains enabled to prevent textures from looking "
"grainy at a distance."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:129
msgid "Import options"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:133
msgid ""
"In Godot 4.0, changing the texture filter and repeat mode is no longer done "
"in the import options."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:136
msgid ""
"Instead, texture filter and repeat modes are changed in the CanvasItem "
"properties in 2D (with a project setting acting as a default), and in a :ref:"
"`per-material configuration in 3D <doc_standard_material_3d_sampling>`. In "
"custom shaders, filter and repeat mode is changed on the ``sampler2D`` "
"uniform using hints described in the :ref:`doc_shading_language` "
"documentation."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:146
#: ../../docs/tutorials/assets_pipeline/importing_audio_samples.rst:164
msgid "Compress > Mode"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:148
msgid ""
"Images are one of the largest assets in a game. To handle them efficiently, "
"they need to be compressed. Godot offers several compression methods, "
"depending on the use case."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:152
msgid ""
"**Lossless:** This is the default and most common compression mode for 2D "
"assets. It shows assets without any kind of artifacting, and disk "
"compression is decent. It will use considerably more amount of video memory "
"than VRAM Compression, though. This is also the recommended setting for "
"pixel art."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:156
msgid ""
"**Lossy:** This is a good choice for large 2D assets. It has some artifacts, "
"but less than VRAM compression and the file size is several times lower "
"compared to Lossless or VRAM Uncompressed. Video memory usage isn't "
"decreased by this mode; it's the same as with Lossless or VRAM Uncompressed."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:160
msgid ""
"**VRAM Compressed:** This is the default and most common compression mode "
"for 3D assets. Size on disk is reduced and video memory usage is also "
"decreased considerably (usually by a factor between 4 and 6). This mode "
"should be avoided for 2D as it exhibits noticeable artifacts, especially for "
"lower-resolution textures."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:165
msgid ""
"**VRAM Uncompressed:** Only useful for formats that can't be compressed, "
"such as raw floating-point images."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:167
msgid ""
"**Basis Universal:** This alternative VRAM compression mode encodes the "
"texture to a format that can be transcoded to most GPU-compressed formats at "
"load-time. This provides very small files that make use of VRAM compression, "
"at the cost of lower quality compared to VRAM Compressed and slow "
"compression times. VRAM usage is usually the same as VRAM Compressed. Basis "
"Universal does not support floating-point image formats (the engine will "
"internally fall back to VRAM Compressed instead)."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:177
#: ../../docs/tutorials/performance/gpu_optimization.rst:230
msgid ""
"Even in 3D, \"pixel art\" textures should have VRAM compression disabled as "
"it will negatively affect their appearance, without improving performance "
"significantly due to their low resolution."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:181
msgid ""
"In this table, each of the 5 options are described together with their "
"advantages and disadvantages (|good| = best, |bad| = worst):"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:185
msgid "Compress mode"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:185
#: ../../docs/tutorials/assets_pipeline/importing_images.rst:209
msgid "Lossless"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:185
#: ../../docs/tutorials/assets_pipeline/importing_images.rst:209
msgid "Lossy"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:185
#: ../../docs/tutorials/assets_pipeline/importing_images.rst:209
msgid "VRAM Compressed"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:185
#: ../../docs/tutorials/assets_pipeline/importing_images.rst:209
msgid "VRAM Uncompressed"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:185
#: ../../docs/tutorials/assets_pipeline/importing_images.rst:209
msgid "Basis Universal"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:187
#: ../../docs/tutorials/export/feature_tags.rst:41
#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:230
#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:344
#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:374
#: ../../docs/contributing/development/core_and_modules/unit_testing.rst:162
#: ../../docs/contributing/development/core_and_modules/unit_testing.rst:195
msgid "**Description**"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:187
msgid "Stored as Lossless WebP / PNG"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:187
msgid "Stored as Lossy WebP"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:187
msgid "Stored as S3TC, BPTC or ETC2 depending on platform"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:187
msgid "Stored as raw pixels"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:187
msgid "Transcoded to VRAM Compressed format"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:189
msgid "**Size on disk**"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:189
msgid "|regular| Small"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:204
msgid "regular"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:189
msgid "|good| Very small"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:189
#: ../../docs/tutorials/assets_pipeline/importing_images.rst:191
msgid "|bad| Large"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:191
msgid "**Memory usage**"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:191
msgid "|good| Small"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:193
msgid "**Performance**"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:193
#: ../../docs/tutorials/assets_pipeline/importing_images.rst:197
msgid "|regular| Normal"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:193
#: ../../docs/tutorials/assets_pipeline/importing_images.rst:197
msgid "|good| Fast"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:195
msgid "**Quality loss**"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:195
msgid "|good| None"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:195
msgid "|regular| Slight"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:195
msgid "|bad| Moderate"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:197
msgid "**Load time**"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:197
msgid "|bad| Slow"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:206
msgid "Estimated memory usage for a single RGBA8 texture with mipmaps enabled:"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:209
msgid "Texture size"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:211
msgid "**128×128**"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:211
#: ../../docs/tutorials/assets_pipeline/importing_images.rst:213
msgid "|good| 85 KiB"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:211
msgid "|good| 21 KiB"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:213
msgid "**256×256**"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:213
#: ../../docs/tutorials/assets_pipeline/importing_images.rst:215
msgid "|good| 341 KiB"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:215
msgid "**512×512**"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:215
#: ../../docs/tutorials/assets_pipeline/importing_images.rst:217
msgid "|good| 1.33 MiB"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:217
msgid "**1024×1024**"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:217
#: ../../docs/tutorials/assets_pipeline/importing_images.rst:219
msgid "|regular| 5.33 MiB"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:219
msgid "**2048×2048**"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:219
#: ../../docs/tutorials/assets_pipeline/importing_images.rst:221
msgid "|bad| 21.33 MiB"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:221
msgid "**4096×4096**"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:221
msgid "|bad| 85.33 MiB"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:226
msgid ""
"In the above table, memory usage will be reduced by 25% for images that do "
"not have an alpha channel (RGB8). Memory usage will be further decreased by "
"25% for images that have mipmaps disabled."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:230
msgid ""
"Notice how at larger resolutions, the impact of VRAM compression is much "
"greater. With a 4:1 compression ratio (6:1 for opaque textures with S3TC), "
"VRAM compression effectively allows a texture to be twice as large on each "
"axis, while using the same amount of memory on the GPU."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:235
msgid ""
"VRAM compression also reduces the memory bandwidth required to sample the "
"texture, which can speed up rendering in memory bandwidth-constrained "
"scenarios (which are frequent on integrated graphics and mobile). These "
"factors combined make VRAM compression a must-have for 3D games with high-"
"resolution textures."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:240
msgid ""
"You can preview how much memory a texture takes by double-clicking it in the "
"FileSystem dock, then looking at the Inspector:"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:247
msgid "Previewing a texture in the Inspector"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:247
msgid ""
"Previewing a texture in the Inspector. Credit: `Red Brick 03 - Poly Haven "
"<https://polyhaven.com/a/red_brick_03>`__"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:250
msgid "Compress > High Quality"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:254
msgid ""
"High-quality VRAM texture compression is only supported in the Forward+ and "
"Forward Mobile rendering methods."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:257
msgid ""
"When using the Compatibility rendering method, this option is always "
"considered disabled."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:260
msgid ""
"If enabled, uses BPTC compression on desktop platforms and :abbr:`ASTC "
"(Adaptive Scalable Texture Compression)` compression on mobile platforms. "
"When using BPTC, BC7 is used for SDR textures and BC6H is used for HDR "
"textures."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:264
msgid ""
"If disabled (default), uses the faster but lower-quality S3TC compression on "
"desktop platforms and ETC2 on mobile/web platforms. When using S3TC, DXT1 "
"(BC1) is used for opaque textures and DXT5 (BC3) is used for transparent or "
"normal map (:abbr:`RGTC (Red-Green Texture Compression)`) textures."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:269
msgid ""
"BPTC and ASTC support VRAM compression for HDR textures, but S3TC and ETC2 "
"do not (see **HDR Compression** below)."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:273
msgid "Compress > HDR Compression"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:277
msgid ""
"This option only has an effect on textures that are imported as HDR formats "
"in Godot (``.hdr`` and ``.exr`` files)."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:280
msgid ""
"If set to **Disabled**, never uses VRAM compression for HDR textures, "
"regardless of whether they're opaque or transparent. Instead, the texture is "
"converted to RGBE9995 (9-bits per channel + 5-bit exponent = 32 bits per "
"pixel) to reduce memory usage compared to a half-float or single-precision "
"float image format."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:285
msgid ""
"If set to **Opaque Only** (default), only uses VRAM compression for opaque "
"HDR textures. This is due to a limitation of HDR formats, as there is no "
"VRAM-compressed HDR format that supports transparency at the same time."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:289
msgid ""
"If set to **Always**, will force VRAM compression even for HDR textures with "
"an alpha channel. To perform this, the alpha channel is discarded on import."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:293
msgid "Compress > Normal Map"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:295
msgid ""
"When using a texture as normal map, only the red and green channels are "
"required. Given regular texture compression algorithms produce artifacts "
"that don't look that nice in normal maps, the :abbr:`RGTC (Red-Green Texture "
"Compression)` compression format is the best fit for this data. Forcing this "
"option to **Enable** will make Godot import the image as :abbr:`RGTC (Red-"
"Green Texture Compression)` compressed. By default, it's set to **Detect**. "
"This means that if the texture is ever detected to be used as a normal map, "
"it will be changed to **Enable** and reimported automatically."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:303
msgid ""
"Note that :abbr:`RGTC (Red-Green Texture Compression)` compression affects "
"the resulting normal map image. You will have to adjust custom shaders that "
"use the normal map's blue channel to take this into account. Built-in "
"material shaders already ignore the blue channel in a normal map (regardless "
"of the actual normal map's contents)."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:309
msgid ""
"In the example below, the normal map with :abbr:`RGTC (Red-Green Texture "
"Compression)` compression is able to preserve its detail much better, while "
"using the same amount of memory as a standard RGBA VRAM-compressed texture:"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:317
msgid ""
"Normal map with standard VRAM compression (left) and with RGTC VRAM "
"compression (right)"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:321
#: ../../docs/tutorials/assets_pipeline/importing_images.rst:422
msgid ""
"Godot requires the normal map to use the X+, Y+ and Z+ coordinates, which is "
"known as an OpenGL-style normal map. If you've imported a material made to "
"be used with another engine, it may be DirectX-style. In this case, the "
"normal map needs to be converted by enabling the **Normal Map Invert Y** "
"import option."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:331
msgid "Compress > Channel Pack"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:333
msgid ""
"If set to **sRGB Friendly** (default), prevents the RG color format from "
"being used as it does not support sRGB color."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:336
msgid ""
"If set to **Optimized**, allows the RG color format to be used if the "
"texture does not use the blue channel."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:339
msgid ""
"A third option **Normal Map (RG Channels)** is *only* available in layered "
"textures (:ref:`class_Cubemap`, :ref:`class_CubemapArray`, :ref:"
"`class_Texture2DArray` and :ref:`class_Texture3D`). This forces all layers "
"from the texture to be imported with the RG color format to reduce memory "
"usage, with only the red and green channels preserved. This only has an "
"effect on textures with the **VRAM Compressed** or **Basis Universal** "
"compression modes."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:349
msgid "Mipmaps > Generate"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:351
msgid ""
"If enabled, smaller versions of the texture are generated on import. For "
"example, a 64×64 texture will generate 6 mipmaps (32×32, 16×16, 8×8, 4×4, "
"2×2, 1×1). This has several benefits:"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:355
msgid ""
"Textures will not become grainy in the distance (in 3D), or if scaled down "
"due to camera zoom or CanvasItem scale (in 2D)."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:357
msgid ""
"Performance will improve if the texture is displayed in the distance, since "
"sampling smaller versions of the original texture is faster and requires "
"less memory bandwidth."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:361
msgid ""
"The downside of mipmaps is that they increase memory usage by roughly 33%."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:363
msgid ""
"It's recommended to enable mipmaps in 3D. However, in 2D, this should only "
"be enabled if your project visibly benefits from having mipmaps enabled. If "
"the camera never zooms out significantly, there won't be a benefit to "
"enabling mipmaps but memory usage will increase."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:369
msgid "Mipmaps > Limit"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:373
msgid ""
"**Mipmaps > Limit** is currently not implemented and has no effect when "
"changed."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:375
msgid ""
"If set to a value greater than ``-1``, limits the maximum number of mipmaps "
"that can be generated. This can be decreased if you don't want textures to "
"become too low-resolution at extreme distances, at the cost of some "
"graininess."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:380
msgid "Roughness > Mode"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:382
msgid ""
"The color channel to consider as a roughness map in this texture. Only "
"effective if **Roughness > Src Normal** is not empty."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:386
msgid "Roughness > Src Normal"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:388
msgid ""
"The path to the texture to consider as a normal map for roughness filtering "
"on import. Specifying this can help decrease specular aliasing slightly in "
"3D."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:391
msgid "Roughness filtering on import is only used in 3D rendering, not 2D."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:394
msgid "Process > Fix Alpha Border"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:396
msgid ""
"This puts pixels of the same surrounding color in transition from "
"transparent to opaque areas. For textures displayed with bilinear filtering, "
"this helps mitigate the outline effect when exporting images from an image "
"editor."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:402
msgid ""
"It's recommended to leave this enabled (as it is by default), unless this "
"causes issues for a particular image."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:406
msgid "Process > Premult Alpha"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:408
msgid ""
"An alternative to fixing darkened borders with **Fix Alpha Border** is to "
"use premultiplied alpha. By enabling this option, the texture will be "
"converted to this format. A premultiplied alpha texture requires specific "
"materials to be displayed correctly:"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:413
msgid ""
"In 2D, a :ref:`class_CanvasItemMaterial` will need to be created and "
"configured to use the **Premul Alpha** blend mode on CanvasItems that use "
"this texture."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:416
msgid ""
"In 3D, there is no support for premultiplied alpha blend mode yet, so this "
"option is only suited for 2D."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:420
msgid "Process > Normal Map Invert Y"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:432
msgid "Process > HDR as sRGB"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:434
msgid ""
"Some HDR images you can find online may be broken and contain sRGB color "
"data (instead of linear color data). It is advised not to use those files. "
"If you absolutely have to, enabling this option on will make them look "
"correct."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:440
msgid ""
"Enabling **HDR as sRGB** on well-formatted HDR images will cause the "
"resulting image to look too dark, so leave this disabled if unsure."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:444
msgid "Process > HDR Clamp Exposure"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:446
msgid ""
"Some HDR panorama images you can find online may contain extremely bright "
"pixels, due to being taken from real life sources without any clipping."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:449
msgid ""
"While these HDR panorama images are accurate to real life, this can cause "
"the radiance map generated by Godot to contain sparkles when used as a "
"background sky. This can be seen in material reflections (even on rough "
"materials in extreme cases). Enabling **HDR Clamp Exposure** can resolve "
"this using a smart clamping formula that does not introduce *visible* "
"clipping – glow will keep working when looking at the background sky."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:457
msgid "Process > Size Limit"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:459
msgid ""
"If set to a value greater than ``0``, the size of the texture is limited on "
"import to a value smaller than or equal to the value specified here. For non-"
"square textures, the size limit affects the longer dimension, with the "
"shorter dimension scaled to preserve aspect ratio. Resizing is performed "
"using cubic interpolation."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:465
msgid ""
"This can be used to reduce memory usage without affecting the source images, "
"or avoid issues with textures not displaying on mobile/web platforms (as "
"these usually can't display textures larger than 4096×4096)."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:472
msgid "Detect 3D > Compress To"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:474
msgid ""
"This changes the :ref:`doc_importing_images_compress_mode` option that is "
"used when a texture is detected as being used in 3D."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:477
msgid ""
"Changing this import option only has an effect if a texture is detected as "
"being used in 3D. Changing this to **Disabled** then reimporting will not "
"change the existing compress mode on a texture (if it's detected to be used "
"in 3D), but choosing **VRAM Compressed** or **Basis Universal** will."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:483
#, fuzzy
msgid "SVG > Scale"
msgstr "Razmera"

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:485
#: ../../docs/tutorials/assets_pipeline/importing_images.rst:497
#: ../../docs/tutorials/assets_pipeline/importing_images.rst:506
msgid "*This is only available for SVG images.*"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:487
msgid ""
"The scale the SVG should be rendered at, with ``1.0`` being the original "
"design size. Higher values result in a larger image. Note that unlike font "
"oversampling, this affects the physical size the SVG is rendered at in 2D. "
"See also **Editor > Scale With Editor Scale** below."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:495
msgid "Editor > Scale With Editor Scale"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:499
msgid ""
"If true, scales the imported image to match the editor's display scale "
"factor. This should be enabled for editor plugin icons and custom class "
"icons, but should be left disabled otherwise."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:504
msgid "Editor > Convert Colors With Editor Theme"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:508
msgid ""
"If checked, converts the imported image's colors to match the editor's icon "
"and font color palette. This assumes the image uses the exact same colors "
"as :ref:`Godot's own color palette for editor icons <doc_editor_icons>`, "
"with the source file designed for a dark editor theme. This should be "
"enabled for editor plugin icons and custom class icons, but should be left "
"disabled otherwise."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:517
#, fuzzy
msgid "Importing SVG images with text"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:519
msgid ""
"As the SVG library used in Godot doesn't support rasterizing text found in "
"SVG images, text must be converted to a path first. Otherwise, text won't "
"appear in the rasterized image."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:523
msgid ""
"There are two ways to achieve this in a non-destructive manner, so you can "
"keep editing the original text afterwards:"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:526
msgid ""
"Select your text object in Inkscape, then duplicate it in place by pressing :"
"kbd:`Ctrl + D` and use **Path > Object to Path**. Hide the original text "
"object afterwards using the **Layers and Objects** dock."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:529
msgid ""
"Use the Inkscape command line to export a SVG from another SVG file with "
"text converted to paths:"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:540
msgid "Supporting high-resolution texture sizes in 2D without artifacts"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:542
msgid ""
"To support :ref:`multiple resolutions <doc_multiple_resolutions>` with crisp "
"visuals at high resolutions, you will need to use high-resolution source "
"images (suited for the highest resolution you wish to support without "
"blurriness, which is typically 4K in modern desktop games)."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:547
#, fuzzy
msgid "There are 2 ways to proceed:"
msgstr "Ne postoje ograničenja prilikom korištenja Godot-a"

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:549
msgid ""
"Use a high base resolution in the project settings (such as 4K), then use "
"the textures at original scale. This is an easier approach."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:551
msgid ""
"Use a low base resolution in the project settings (such as 1080p), then "
"downscale textures when using them. This is often more difficult and can "
"make various calculations in script tedious, so the approach described above "
"is recommended instead."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:556
msgid ""
"After doing this, you may notice that textures become grainy at lower "
"viewport resolutions. To resolve this, enable **Mipmaps** on textures used "
"in 2D in the Import dock. This will increase memory usage."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:560
msgid ""
"Enabling mipmaps can also make textures appear blurrier, but you can choose "
"to make textures sharper (at the cost of some graininess) by setting "
"**Rendering > Textures > Default Filters > Texture Mipmap Bias** to a "
"negative value."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:566
msgid "Use appropriate texture sizes in 3D"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:568
msgid ""
"While there's no \"one size fits all\" recommendation, here are some general "
"recommendations for choosing texture sizes in 3D:"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:571
msgid ""
"The size of a texture should be adjusted to have a consistent texel density "
"compared to surrounding objects. While this cannot be ensured perfectly when "
"sticking to power-of-two texture sizes, it's usually possible to keep "
"texture detail fairly consistent throughout a 3D scene."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:575
msgid ""
"The smaller the object appears on screen, the smaller its texture should be. "
"For example, a tree that only appears in the background doesn't need a "
"texture resolution as high as other objects the player may be able to walk "
"close to."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:578
msgid ""
"Using power-of-two texture sizes is recommended, but is not required. "
"Textures don't have to be square – sizes such as 1024×512 are acceptable."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:580
msgid ""
"There are diminishing returns to using large texture sizes, despite the "
"increased memory usage and loading times. Most modern 3D games not using a "
"pixel art style stick to 2048×2048 textures on average, with 1024×1024 and "
"512×512 for textures spanning smaller surfaces."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:584
msgid ""
"When working with physically-based materials in 3D, you can reduce memory "
"usage and file size without affecting quality too much by using a lower "
"resolution for certain texture maps. This works especially well for textures "
"that only feature low-frequency detail (such as a normal map for a snow "
"texture)."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:590
msgid ""
"If you have control over how the 3D models are created, these tips are also "
"worth exploring:"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:593
msgid ""
"When working with 3D models that are mostly symmetrical, you may be able to "
"use mirrored UVs to double the effective texel density. This may look "
"unnatural when used on human faces though."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:596
msgid ""
"When working with 3D models using a low-poly style and plain colors, you can "
"rely on vertex colors instead of textures to represent colors on the model's "
"surfaces."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_images.rst:602
msgid ""
"Images can be loaded and saved at runtime using :ref:`runtime file loading "
"and saving <doc_runtime_file_loading_and_saving_images>`, including from an "
"exported project."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_audio_samples.rst:4
#: ../../docs/tutorials/assets_pipeline/importing_audio_samples.rst:63
msgid "Importing audio samples"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_audio_samples.rst:7
msgid "Supported audio formats"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_audio_samples.rst:9
msgid ""
"Godot provides 3 options to import your audio data: WAV, Ogg Vorbis and MP3."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_audio_samples.rst:11
msgid "Each format has different advantages:"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_audio_samples.rst:13
msgid ""
"WAV files use raw data or light compression (IMA-ADPCM). They are "
"lightweight on the CPU to play back (hundreds of simultaneous voices in this "
"format are fine). The downside is that they take up a lot of disk space."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_audio_samples.rst:16
msgid ""
"Ogg Vorbis files use a stronger compression that results in much smaller "
"file size, but require significantly more processing power to play back."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_audio_samples.rst:19
msgid ""
"MP3 files use better compression than WAV with IMA-ADPCM, but worse than Ogg "
"Vorbis. This means that a MP3 file with roughly equal quality to Ogg Vorbis "
"will be significantly larger. On the bright side, MP3 requires less CPU "
"usage to play back compared to Ogg Vorbis."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_audio_samples.rst:29
msgid ""
"Here is a comparative chart representing the file size of 1 second of audio "
"with each format:"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_audio_samples.rst:33
msgid "Format"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_audio_samples.rst:33
msgid "1 second of audio"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_audio_samples.rst:35
msgid "WAV 24-bit, 96 kHz, stereo"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_audio_samples.rst:35
msgid "576 KB"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_audio_samples.rst:37
msgid "WAV 16-bit, 44 kHz, mono"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_audio_samples.rst:37
msgid "88 KB"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_audio_samples.rst:39
msgid "WAV 16-bit, IMA-ADPCM, mono"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_audio_samples.rst:39
msgid "22 KB"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_audio_samples.rst:41
msgid "MP3 192 Kb/s, stereo"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_audio_samples.rst:41
msgid "24 KB"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_audio_samples.rst:43
msgid "Ogg Vorbis 128 Kb/s, stereo"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_audio_samples.rst:43
msgid "16 KB"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_audio_samples.rst:45
msgid "Ogg Vorbis 96 Kb/s, stereo"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_audio_samples.rst:45
msgid "12 KB"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_audio_samples.rst:48
msgid ""
"Note that the MP3 and Ogg Vorbis figures can vary depending on the encoding "
"type. The above figures use :abbr:`CBR (Constant Bit Rate)` encoding for "
"simplicity, but most Ogg Vorbis and MP3 files you can find online are "
"encoded with :abbr:`VBR (Variable Bit Rate)` encoding which is more "
"efficient. VBR encoding makes the effective audio file size depend on how "
"\"complex\" the source audio is."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_audio_samples.rst:57
msgid ""
"Consider using WAV for short and repetitive sound effects, and Ogg Vorbis "
"for music, speech, and long sound effects. MP3 is useful for mobile and web "
"projects where CPU resources are limited, especially when playing multiple "
"compressed sounds at the same time (such as long ambient sounds)."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_audio_samples.rst:65
msgid ""
"Several options are available in the Import dock after selecting a WAV file "
"in the FileSystem dock:"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_audio_samples.rst:72
msgid ""
"Import options in the Import dock after selecting a WAV file in the "
"FileSystem dock"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_audio_samples.rst:74
msgid ""
"The set of options available after selecting a Ogg Vorbis or MP3 file is "
"different:"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_audio_samples.rst:80
msgid ""
"Import options in the Import dock after selecting a MP3 file in the "
"FileSystem dock"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_audio_samples.rst:80
msgid ""
"Import options in the Import dock after selecting a MP3 file in the "
"FileSystem dock. Options are identical for Ogg Vorbis files."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_audio_samples.rst:83
msgid ""
"After importing a sound, you can play it back using the AudioStreamPlayer, "
"AudioStreamPlayer2D or AudioStreamPlayer3D nodes. See :ref:"
"`doc_audio_streams` for more information."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_audio_samples.rst:88
msgid "Import options (WAV)"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_audio_samples.rst:91
msgid "Force > 8 Bit"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_audio_samples.rst:93
msgid ""
"If enabled, forces the imported audio to use 8-bit quantization if the "
"source file is 16-bit or higher."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_audio_samples.rst:96
msgid ""
"Enabling this is generally not recommended, as 8-bit quantization decreases "
"audio quality significantly. If you need smaller file sizes, consider using "
"Ogg Vorbis or MP3 audio instead."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_audio_samples.rst:101
msgid "Force > Mono"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_audio_samples.rst:103
msgid ""
"If enabled, forces the imported audio to be mono if the source file is "
"stereo. This decreases the file size by 50% by merging the two channels into "
"one."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_audio_samples.rst:107
msgid "Force > Max Rate"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_audio_samples.rst:109
msgid ""
"If set to a value greater than ``0``, forces the audio's sample rate to be "
"reduced to a value lower than or equal to the value specified here."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_audio_samples.rst:112
msgid ""
"This can decrease file size noticeably on certain sounds, without impacting "
"quality depending on the actual sound's contents. See :ref:"
"`doc_importing_audio_samples_best_practices` for more information."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_audio_samples.rst:117
msgid "Edit > Trim"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_audio_samples.rst:119
msgid ""
"The source audio file may contain long silences at the beginning and/or the "
"end. These silences are inserted by :abbr:`DAWs (Digital Audio "
"Workstations)` when saving to a waveform, which increases their size "
"unnecessarily and add latency to the moment they are played back."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_audio_samples.rst:124
msgid ""
"Enabling **Trim** will automatically trim the beginning and end of the audio "
"if it's lower than -50 dB *after* normalization (see **Edit > Normalize** "
"below). A fade-in/fade-out period of 500 samples is also used during "
"trimming to avoid audible pops."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_audio_samples.rst:130
msgid "Edit > Normalize"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_audio_samples.rst:132
msgid ""
"If enabled, audio volume will be *normalized* so that its peak volume is "
"equal to 0 dB. When enabled, normalization will make audio sound louder "
"depending on its original peak volume."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_audio_samples.rst:137
msgid "Edit > Loop Mode"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_audio_samples.rst:139
msgid ""
"Unlike Ogg Vorbis and MP3, WAV files can contain metadata to indicate "
"whether they're looping (in addition to loop points). By default, Godot will "
"follow this metadata, but you can choose to apply a specific loop mode:"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_audio_samples.rst:143
msgid ""
"**Disabled:** Don't loop audio, even if metadata indicates the file should "
"be played back looping."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_audio_samples.rst:145
msgid "**Forward:** Standard audio looping."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_audio_samples.rst:146
msgid ""
"**Ping-Pong:** Play audio forward until it's done playing, then play it "
"backward and repeat. This is similar to mirrored texture repeat, but for "
"audio."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_audio_samples.rst:149
msgid ""
"**Backward:** Play audio in reverse and loop back to the end when done "
"playing."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_audio_samples.rst:151
msgid ""
"When choosing one of the **Forward**, **Ping-Pong** or **Backward** loop "
"modes, loop points can also be defined to make only a specific part of the "
"sound loop. **Loop Begin** is set in samples after the beginning of the "
"audio file. **Loop End** is also set in samples after the beginning of the "
"audio file, but will use the end of the audio file if set to ``-1``."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_audio_samples.rst:159
#: ../../docs/tutorials/assets_pipeline/importing_audio_samples.rst:186
msgid ""
"In AudioStreamPlayer, the ``finished`` signal won't be emitted for looping "
"audio when it reaches the end of the audio file, as the audio will keep "
"playing indefinitely."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_audio_samples.rst:166
msgid ""
"Two compression modes can be chosen for WAV files: **Disabled** (default) or "
"**RAM (Ima-ADPCM)**. **RAM (Ima-ADPCM)** reduces file size and memory usage "
"a little, at the cost of decreasing quality in an audible manner."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_audio_samples.rst:170
msgid ""
"Ogg Vorbis and MP3 don't decrease quality as much and can provide greater "
"file size reductions, at the cost of higher CPU usage during playback. This "
"higher CPU usage is usually not a problem (especially with MP3), unless "
"playing dozens of compressed sounds at the same time on mobile/web platforms."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_audio_samples.rst:176
msgid "Import options (Ogg Vorbis and MP3)"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_audio_samples.rst:179
msgid "Loop"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_audio_samples.rst:181
msgid ""
"If enabled, the audio will begin playing at the beginning after playback "
"ends by reaching the end of the audio."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_audio_samples.rst:191
msgid "Loop Offset"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_audio_samples.rst:193
msgid ""
"The loop offset determines where audio will start to loop after playback "
"reaches the end of the audio. This can be used to only loop a part of the "
"audio file, which is useful for some ambient sounds or music. The value is "
"determined in seconds relative to the beginning of the audio, so ``0`` will "
"loop the entire audio file."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_audio_samples.rst:199
msgid "Only has an effect if **Loop** is enabled."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_audio_samples.rst:201
msgid ""
"A more convenient editor for **Loop Offset** is provided in the :ref:"
"`Advanced import settings "
"<doc_importing_audio_samples_advanced_import_settings>` dialog, as it lets "
"you preview your changes without having to reimport the audio."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_audio_samples.rst:206
msgid "BPM"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_audio_samples.rst:208
msgid ""
"The Beats Per Minute of the audio track. This should match the BPM measure "
"that was used to compose the track. This is only relevant for music that "
"wishes to make use of interactive music functionality (not implemented yet), "
"not sound effects."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_audio_samples.rst:213
msgid ""
"A more convenient editor for **BPM** is provided in the :ref:`Advanced "
"import settings <doc_importing_audio_samples_advanced_import_settings>` "
"dialog, as it lets you preview your changes without having to reimport the "
"audio."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_audio_samples.rst:218
msgid "Beat Count"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_audio_samples.rst:220
msgid ""
"The beat count of the audio track. This is only relevant for music that "
"wishes to make use of interactive music functionality (not implemented yet), "
"not sound effects."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_audio_samples.rst:224
msgid ""
"A more convenient editor for **Beat Count** is provided in the :ref:"
"`Advanced import settings "
"<doc_importing_audio_samples_advanced_import_settings>` dialog, as it lets "
"you preview your changes without having to reimport the audio."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_audio_samples.rst:229
msgid "Bar Beats"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_audio_samples.rst:231
msgid ""
"The number of bars within a single beat in the audio track. This is only "
"relevant for music that wishes to make use of interactive music "
"functionality (not implemented yet), not sound effects."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_audio_samples.rst:235
msgid ""
"A more convenient editor for **Bar Beats** is provided in the :ref:`Advanced "
"import settings <doc_importing_audio_samples_advanced_import_settings>` "
"dialog, as it lets you preview your changes without having to reimport the "
"audio."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_audio_samples.rst:242
msgid "Advanced import settings (Ogg Vorbis and MP3)"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_audio_samples.rst:244
msgid ""
"If you double-click an Ogg Vorbis or MP3 file in the FileSystem dock (or "
"choose **Advanced…** in the Import dock), you will see a dialog appear:"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_audio_samples.rst:251
msgid ""
"Advanced dialog when double-clicking a Ogg Vorbis or MP3 file in the "
"FileSystem dock"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_audio_samples.rst:253
msgid ""
"This dialog allows you to edit the audio's loop point with a real-time "
"preview, in addition to the :abbr:`BPM (Beats Per Minute)`, beat count and "
"bar beats. These 3 settings are currently unused, but they will be used in "
"the future for interactive music support (which allows smoothly "
"transitioning between different music tracks)."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_audio_samples.rst:261
msgid ""
"Unlike WAV files, Ogg Vorbis and MP3 only support a \"loop begin\" loop "
"point, not a \"loop end\" point. Looping can also be only be standard "
"forward looping, not ping-pong or backward."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_audio_samples.rst:271
#, fuzzy
msgid "Use appropriate quality settings"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/assets_pipeline/importing_audio_samples.rst:273
msgid ""
"While keeping pristine-quality audio sources is important if you're "
"performing editing, using the same quality in the exported project is not "
"necessary. For WAV files, Godot offers several import options to reduce the "
"final file size without modifying the source file on disk."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_audio_samples.rst:278
msgid ""
"To reduce memory usage and file size, choose an appropriate quantization, "
"sample rate and number of channels for your audio:"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_audio_samples.rst:281
msgid ""
"There's no *audible* benefit to using 24-bit audio, especially in a game "
"where several sounds are often playing at the same time (which makes it "
"harder to appreciate individual sounds)."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_audio_samples.rst:284
msgid ""
"Unless you are slowing down the audio at run-time, there's no *audible* "
"benefit to using a sample rate greater than 48 kHz. If you wish to keep a "
"source with a higher sample rate for editing, use the **Force > Max Rate** "
"import option to limit the sample rate of the imported sound (only available "
"for WAV files)."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_audio_samples.rst:289
msgid ""
"Many sound effects can generally be converted to mono as opposed to stereo. "
"If you wish to keep a source with stereo for editing, use the **Force > "
"Mono** import option to convert the imported sound to mono (only available "
"for WAV files)."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_audio_samples.rst:292
msgid ""
"Voices can generally be converted to mono, but can also have their sample "
"rate reduced to 22 kHz without a noticeable loss in quality (unless the "
"voice is very high-pitched). This is because most human voices never go past "
"11 kHz."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_audio_samples.rst:297
msgid "Use real-time audio effects to reduce file size"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_audio_samples.rst:299
msgid ""
"Godot has an :ref:`extensive bus system <doc_audio_buses>` with built-in "
"effects. This saves SFX artists the need to add reverb to the sound effects, "
"reducing their size greatly and ensuring correct trimming."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_audio_samples.rst:305
msgid ""
"As you can see above, sound effects become much larger in file size with "
"reverb added."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_audio_samples.rst:310
msgid ""
"Audio samples can be loaded and saved at runtime using :ref:`runtime file "
"loading and saving <doc_runtime_file_loading_and_saving_audio_video_files>`, "
"including from an exported project."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_translations.rst:4
msgid "Importing translations"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_translations.rst:7
msgid "Games and internationalization"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_translations.rst:9
msgid ""
"The gaming community isn't monolingual or monocultural. It's made up of many "
"different languages and cultures - just like the Godot community! If you "
"want to allow players to experience your game in their language, one of "
"things you'll need to provide is text translations, which Godot supports via "
"internationalized text."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_translations.rst:15
msgid ""
"In regular desktop or mobile applications, internationalized text is usually "
"located in resource files (or .po files for GNU stuff). Games, however, can "
"use several orders of magnitude more text than applications, so they must "
"support efficient methods for dealing with loads of multilingual text."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_translations.rst:21
msgid ""
"There are two approaches to generate multilingual language games and "
"applications. Both are based on a key:value system. The first is to use one "
"of the languages as the key (usually English), the second is to use a "
"specific identifier. The first approach is probably easier for development "
"if a game is released first in English, later in other languages, but a "
"complete nightmare if working with many languages at the same time."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_translations.rst:29
msgid ""
"In general, games use the second approach and a unique ID is used for each "
"string. This allows you to revise the text while it is being translated to "
"other languages. The unique ID can be a number, a string, or a string with a "
"number (it's just a unique string anyway)."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_translations.rst:34
msgid ""
"If you need a more powerful file format, Godot also supports loading "
"translations written in the gettext ``.po`` format. See :ref:"
"`doc_localization_using_gettext` for details."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_translations.rst:39
msgid "Translation format"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_translations.rst:41
msgid ""
"To complete the picture and allow efficient support for translations, Godot "
"has a special importer that can read CSV files. Most spreadsheet editors can "
"export to this format, so the only requirement is that the files have a "
"special arrangement. The CSV files **must** be saved with UTF-8 encoding "
"without a `byte order mark <https://en.wikipedia.org/wiki/"
"Byte_order_mark>`__."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_translations.rst:47
msgid "CSV files must be formatted as follows:"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_translations.rst:50
#: ../../docs/tutorials/assets_pipeline/importing_translations.rst:69
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:228
msgid "keys"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_translations.rst:50
msgid "<lang1>"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_translations.rst:50
msgid "<lang2>"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_translations.rst:50
msgid "<langN>"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_translations.rst:52
msgid "KEY1"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_translations.rst:52
#: ../../docs/tutorials/assets_pipeline/importing_translations.rst:54
#: ../../docs/tutorials/assets_pipeline/importing_translations.rst:56
#: ../../docs/tutorials/io/binary_serialization_api.rst:53
#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:195
#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:197
#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:199
#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:246
#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:254
#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:265
msgid "string"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_translations.rst:54
msgid "KEY2"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_translations.rst:56
msgid "KEYN"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_translations.rst:59
msgid ""
"The \"lang\" tags must represent a language, which must be one of the :ref:"
"`valid locales <doc_locales>` supported by the engine. The \"KEY\" tags must "
"be unique and represent a string universally (they are usually in uppercase, "
"to differentiate from other strings). These keys will be replaced at runtime "
"by the matching translated string. Note that the case is important, \"KEY1\" "
"and \"Key1\" will be different keys. The top-left cell is ignored and can be "
"left empty or having any content. Here's an example:"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_translations.rst:69
#: ../../docs/tutorials/i18n/locales.rst:313
msgid "en"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_translations.rst:69
#: ../../docs/tutorials/i18n/locales.rst:319
msgid "es"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_translations.rst:69
#: ../../docs/tutorials/i18n/locales.rst:497
msgid "ja"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_translations.rst:71
msgid "GREET"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_translations.rst:71
msgid "Hello, friend!"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_translations.rst:71
msgid "Hola, amigo!"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_translations.rst:71
msgid "こんにちは"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_translations.rst:73
msgid "ASK"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_translations.rst:73
msgid "How are you?"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_translations.rst:73
msgid "Cómo está?"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_translations.rst:73
msgid "元気ですか"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_translations.rst:75
msgid "BYE"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_translations.rst:75
msgid "Goodbye"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_translations.rst:75
msgid "Adiós"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_translations.rst:75
msgid "さようなら"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_translations.rst:77
msgid "QUOTE"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_translations.rst:77
msgid "\"Hello\" said the man."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_translations.rst:77
msgid "\"Hola\" dijo el hombre."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_translations.rst:77
msgid "「こんにちは」男は言いました"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_translations.rst:80
msgid ""
"The same example is shown below as a comma-separated plain text file, which "
"should be the result of editing the above in a spreadsheet. When editing the "
"plain text version, be sure to enclose with double quotes any message that "
"contains commas, line breaks or double quotes, so that commas are not parsed "
"as delimiters, line breaks don't create new entries and double quotes are "
"not parsed as enclosing characters. Be sure to escape any double quotes a "
"message may contain by preceding them with another double quote. "
"Alternatively, you can select another delimiter than comma in the import "
"options."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_translations.rst:99
msgid "CSV importer"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_translations.rst:101
msgid ""
"Godot will treat CSV files as translations by default. It will import them "
"and generate one or more compressed translation resource files next to it."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_translations.rst:104
msgid ""
"Importing will also add the translation to the list of translations to load "
"when the game runs, specified in project.godot (or the project settings). "
"Godot allows loading and removing translations at runtime as well."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_translations.rst:109
msgid ""
"Select the ``.csv`` file and access the **Import** dock to define import "
"options. You can toggle the compression of the imported translations, and "
"select the delimiter to use when parsing the CSV file."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_translations.rst:115
msgid "Be sure to click **Reimport** after any change to these options."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/index.rst:4
msgid "Importing 3D scenes"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/index.rst:6
msgid ""
"Godot supports importing 3D scenes from various file formats. This "
"documentation section describes what those formats are, and how to use them, "
"including exporting with the correct conventions and best practices, and how "
"to customize the node type using a suffix in the node name. The import "
"configuration article describes how to customize the imported data using the "
"import dock, the advanced import settings dialog, and inherited scenes."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/index.rst:25
msgid ""
"3D scenes can be loaded at runtime using :ref:`runtime file loading and "
"saving <doc_runtime_file_loading_and_saving_3d_scenes>`, including from an "
"exported project."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/available_formats.rst:4
msgid "Available 3D formats"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/available_formats.rst:6
msgid ""
"When dealing with 3D assets, Godot has a flexible and configurable importer."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/available_formats.rst:8
msgid ""
"Godot works with *scenes*. This means that the entire scene being worked on "
"in your favorite 3D modeling software will be transferred as close as "
"possible."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/available_formats.rst:11
msgid "Godot supports the following 3D *scene file formats*:"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/available_formats.rst:13
msgid ""
"glTF 2.0 **(recommended)**. Godot has support for both text (``.gltf``) and "
"binary (``.glb``) formats."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/available_formats.rst:15
msgid ""
"``.blend`` (Blender). This works by calling Blender to export to glTF in a "
"transparent manner (requires Blender to be installed)."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/available_formats.rst:17
msgid "DAE (COLLADA), an older format that is supported."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/available_formats.rst:18
msgid ""
"OBJ (Wavefront) format + their MTL material files. This is also supported, "
"but pretty limited given the format's limitations (no support for pivots, "
"skeletons, animations, UV2, PBR materials, ...)."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/available_formats.rst:21
msgid ""
"FBX, supported via `FBX2glTF <https://github.com/godotengine/FBX2glTF>`__ "
"integration. This requires installing an external program that links against "
"the proprietary FBX SDK, so we recommend using other formats listed above "
"(if suitable for your workflow)."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/available_formats.rst:25
msgid ""
"Copy the scene file together with the textures and mesh data (if separate) "
"to the project repository, then Godot will do a full import when focusing "
"the editor window."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/available_formats.rst:30
msgid "Exporting glTF 2.0 files from Blender (recommended)"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/available_formats.rst:32
#, fuzzy
msgid "There are 3 ways to export glTF files from Blender:"
msgstr "Ne postoje ograničenja prilikom korištenja Godot-a"

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/available_formats.rst:34
msgid "As a glTF binary file (``.glb``)."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/available_formats.rst:35
msgid "As a glTF text-based file with embedded binary data (``.gltf`` file)"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/available_formats.rst:36
msgid ""
"As a glTF text-based file with separate binary data and textures (``.gltf`` "
"file + ``.bin`` file + textures)."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/available_formats.rst:39
msgid ""
"glTF binary files (``.glb``) are the smallest of the three options. They "
"include the mesh and textures set up in Blender. When brought into Godot the "
"textures are part of the object's material file."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/available_formats.rst:43
msgid ""
"glTF embedded files (``.gltf``) function the same way as binary files. They "
"don't provide extra functionality in Godot, and shouldn't be used since they "
"have a larger file size."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/available_formats.rst:47
msgid ""
"There are two reasons to use glTF with the textures separate. One is to have "
"the scene description in a text based format and the binary data in a "
"separate binary file. This can be useful for version control if you want to "
"review changes in a text-based format. The second is you need the texture "
"files separate from the material file. If you don't need either of those, "
"glTF binary files are fine."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/available_formats.rst:54
msgid ""
"The glTF import process first loads the glTF file's data into an in-memory "
"GLTFState class. This data is then used to generate a Godot scene. When "
"importing files at runtime, this scene can be directly added to the tree. "
"The export process is the reverse of this, a Godot scene is converted to a "
"GLTFState class, then the glTF file is generated from that."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/available_formats.rst:-1
msgid ""
"Diagram explaining the runtime import and export process for glTF files in "
"Godot"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/available_formats.rst:64
msgid ""
"When importing glTF files in the editor, there are two more steps. After "
"generating the Godot scene, the ResourceImporterScene class is used to apply "
"additional import settings, including settings you set through the Import "
"dock and the Advanced Import Settings dialog. This is then saved as a Godot "
"scene file, which is what gets used when you run/export your game."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/available_formats.rst:-1
msgid "Diagram explaining the editor import process for glTF files in Godot"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/available_formats.rst:76
msgid ""
"If your model contains blend shapes (also known as \"shape keys\" and "
"\"morph targets\"), your glTF export setting **Export Deformation Bones "
"Only** needs to be configured to **Enabled** under the Animation export "
"configurations."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/available_formats.rst:80
msgid "Exporting non-deforming bones anyway will lead to incorrect shading."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/available_formats.rst:84
msgid ""
"Blender versions older than 3.2 do not export emissive textures with the "
"glTF file. If your model uses one and you're using an older version of "
"Blender, it must be brought in separately."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/available_formats.rst:96
msgid "Importing ``.blend`` files directly within Godot"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/available_formats.rst:100
msgid ""
"This functionality requires Blender 3.0 or later. For best results, we "
"recommend using Blender 3.5 or later, as it includes many fixes to the glTF "
"exporter."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/available_formats.rst:104
msgid ""
"It is **strongly** recommended to use an official Blender release downloaded "
"from blender.org, as opposed to a Linux distribution package or Flatpak. "
"This avoids any issues related to packaging, such as different library "
"versions that can cause incompatibilities or sandboxing restrictions."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/available_formats.rst:109
msgid ""
"From Godot 4.0 onwards, the editor can directly import ``.blend`` files by "
"calling `Blender <https://www.blender.org/>`__'s glTF export functionality "
"in a transparent manner."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/available_formats.rst:113
msgid ""
"This allows you to iterate on your 3D scenes faster, as you can save the "
"scene in Blender, alt-tab back to Godot then see your changes immediately. "
"When working with version control, this is also more efficient as you no "
"longer need to commit a copy of the exported glTF file to version control."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/available_formats.rst:118
msgid ""
"To use ``.blend`` import, you must install Blender before opening the Godot "
"editor (if opening a project that already contains ``.blend`` files). If you "
"keep Blender installed at its default location, Godot should be able to "
"detect its path automatically. If this isn't the case, configure the path to "
"the directory containing the Blender executable in the Editor Settings "
"(**Filesystem > Import > Blender > Blender 3 Path**)."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/available_formats.rst:125
msgid ""
"If you keep ``.blend`` files within your project folder but don't want them "
"to be imported by Godot, disable **Filesystem > Import > Blender > Enabled** "
"in the advanced Project Settings."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/available_formats.rst:129
msgid ""
"The ``.blend`` import process converts to glTF first, so it still uses "
"Godot's glTF import code. Therefore, the ``.blend`` import process is the "
"same as the glTF import process, but with an extra step at the beginning."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/available_formats.rst:-1
msgid "Diagram explaining the import process for Blender files in Godot"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/available_formats.rst:139
msgid ""
"When working in a team, keep in mind using ``.blend`` files in your project "
"will require *all* team members to have Blender installed. While Blender is "
"a free download, this may add friction when working on the project. ``."
"blend`` import is also not available on the Android and web editors, as "
"these platforms can't call external programs."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/available_formats.rst:145
msgid ""
"If this is problematic, consider using glTF scenes exported from Blender "
"instead."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/available_formats.rst:149
msgid "Exporting DAE files from Blender"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/available_formats.rst:151
msgid ""
"Blender has built-in COLLADA support, but it does not work properly for the "
"needs of game engines and shouldn't be used as-is. However, scenes exported "
"with the built-in Collada support may still work for simple scenes without "
"animation."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/available_formats.rst:155
msgid ""
"For complex scenes or scenes that contain animations, Godot provides a "
"`Blender plugin <https://github.com/godotengine/collada-exporter>`_ that "
"will correctly export COLLADA scenes for use in Godot."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/available_formats.rst:160
msgid "Importing OBJ files in Godot"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/available_formats.rst:162
msgid ""
"OBJ is one of the simplest 3D formats out there, so Godot should be able to "
"import most OBJ files successfully. However, OBJ is also a very limited "
"format: it doesn't support skinning, animation, UV2 or PBR materials."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/available_formats.rst:166
#, fuzzy
msgid "There are 2 ways to use OBJ meshes in Godot:"
msgstr "Ne postoje ograničenja prilikom korištenja Godot-a"

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/available_formats.rst:168
msgid ""
"Load them directly in a MeshInstance3D node, or any other property that "
"expects as mesh (such as GPUParticles3D). This is the default mode."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/available_formats.rst:170
msgid ""
"Change their import mode to **OBJ as Scene** in the Import dock then restart "
"the editor. This allows you to use the same import options as glTF or "
"Collada scenes, such as unwrapping UV2 on import (for :ref:"
"`doc_using_lightmap_gi`)."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/available_formats.rst:176
msgid ""
"Blender 3.4 and later can export RGB vertex colors in OBJ files (this is a "
"nonstandard extension of the OBJ format). Godot is able to import those "
"vertex colors since Godot 4.0, but they will not be displayed on the "
"material unless you enable **Vertex Color > Use As Albedo** on the material."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/available_formats.rst:181
msgid ""
"Vertex colors from OBJ meshes keep their original color space once imported "
"(sRGB/linear), but their brightness is clamped to 1.0 (they can't be "
"overbright)."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/available_formats.rst:186
msgid "Importing FBX files in Godot"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/available_formats.rst:188
msgid ""
"When opening a project containing FBX scenes, you will see a dialog asking "
"you to configure FBX import. Click the link in the dialog to download an "
"FBX2glTF binary, then extract the ZIP archive, place the binary anywhere you "
"wish, then specify its path in the dialog."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/available_formats.rst:193
msgid ""
"If you keep ``.fbx`` files within your project folder but don't want them to "
"be imported by Godot, disable **Filesystem > Import > FBX > Enabled** in the "
"advanced Project Settings."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/available_formats.rst:197
msgid ""
"The FBX import process converts to glTF first, so it still uses Godot's glTF "
"import code. Therefore, the FBX import process is the same as the glTF "
"import process, but with an extra step at the beginning."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/available_formats.rst:-1
msgid "Diagram explaining the import process for FBX files in Godot"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/available_formats.rst:207
msgid ""
"The full installation process for using FBX in Godot is described on the "
"`FBX import page of the Godot website <https://godotengine.org/fbx-"
"import>`__."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/model_export_considerations.rst:4
#, fuzzy
msgid "Model export considerations"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/model_export_considerations.rst:6
msgid ""
"Before exporting a 3D model from a 3D modeling application, such as Blender, "
"there are some considerations that should be taken into account to ensure "
"that the model follows the conventions and best practices for Godot."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/model_export_considerations.rst:11
msgid "3D asset direction conventions"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/model_export_considerations.rst:13
msgid ""
"Godot uses a right-handed, Y-is-up coordinate system, with the -Z axis as "
"the camera's forward direction. This is the same as OpenGL. This implies "
"that +Z is back, +X is right, and -X is left for a camera."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/model_export_considerations.rst:17
msgid ""
"The convention for 3D assets is to face the opposite direction as the "
"camera, so that characters and other assets are facing the camera by "
"default. This convention is extremely common in 3D modeling applications, "
"and is `codified in glTF as part of the glTF 2.0 specification <https://"
"registry.khronos.org/glTF/specs/2.0/glTF-2.0.html#coordinate-system-and-"
"units>`__. This means that for oriented 3D assets (such as characters), the "
"+Z axis is the direction of the front, so -Z is the rear, +X is the left "
"side, and -X is the right side for a 3D asset. In Blender, this means that "
"+Y is rear and -Y is front for an asset."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/model_export_considerations.rst:26
msgid ""
"When rotating an oriented 3D asset in Godot, use the ``use_model_front`` "
"option on the ``look_at`` functions, and use the ``Vector3.MODEL_*`` "
"constants to perform calculations in the oriented asset's local space."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/model_export_considerations.rst:30
msgid ""
"For assets without an intrinsic front side or forward direction, such as a "
"game map or terrain, take note of the cardinal directions instead. The "
"convention in Godot and the vast majority of other applications is that +X "
"is east and -X is west. Due to Godot's right-handed Y-is-up coordinate "
"system, this implies that +Z is south and -Z is north. In Blender, this "
"means that +Y is north and -Y is south."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/model_export_considerations.rst:38
msgid "Exporting textures separately"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/model_export_considerations.rst:40
msgid ""
"While textures can be exported with a model in certain file formats, such as "
"glTF 2.0, you can also export them separately. Godot uses PBR (physically "
"based rendering) for its materials, so if a texturing program can export PBR "
"textures they can work in Godot. This includes the `Substance suite <https://"
"www.substance3d.com/>`__, `ArmorPaint (open source) <https://armorpaint.org/"
">`__, and `Material Maker (open source) <https://github.com/RodZill4/"
"material-maker>`__."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/model_export_considerations.rst:45
#, fuzzy
msgid ""
"For more information on Godot's materials, see :ref:"
"`doc_standard_material_3d`."
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/model_export_considerations.rst:48
#, fuzzy
msgid "Exporting considerations"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/model_export_considerations.rst:50
msgid ""
"Since GPUs can only render triangles, meshes that contain quads or N-gons "
"have to be *triangulated* before they can be rendered. Godot can triangulate "
"meshes on import, but results may be unpredictable or incorrect, especially "
"with N-gons. Regardless of the target application, triangulating *before* "
"exporting the scene will lead to more consistent results and should be done "
"whenever possible."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/model_export_considerations.rst:57
msgid ""
"To avoid issues with incorrect triangulation after importing in Godot, it is "
"recommended to make the 3D modeling software triangulate objects on its own. "
"In Blender, this can be done by adding a Triangulate modifier to your "
"objects and making sure **Apply Modifiers** is checked in the export dialog. "
"Alternatively, depending on the exporter, you may be able to find and enable "
"a **Triangulate Faces** option in the export dialog."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/model_export_considerations.rst:64
msgid ""
"To avoid issues with 3D selection in the editor, it is recommended to apply "
"the object transform in the 3D modeling software before exporting the scene."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/model_export_considerations.rst:69
msgid ""
"It is important that the mesh is not deformed by bones when exporting. Make "
"sure that the skeleton is reset to its T-pose or default rest pose before "
"exporting with your favorite 3D editor."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/model_export_considerations.rst:74
#, fuzzy
msgid "Lighting considerations"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/model_export_considerations.rst:76
msgid ""
"While it's possible to import lights from a 3D scene using the glTF, ``."
"blend`` or Collada formats, it's generally advised to design the scene's "
"lighting in the Godot editor after importing the scene."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/model_export_considerations.rst:80
msgid ""
"This allows you to get a more accurate feel for the final result, as "
"different engines will render lights in a different manner. This also avoids "
"any issues with lights appearing excessively strong or faint as a result of "
"the import process."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/node_type_customization.rst:4
msgid "Node type customization using name suffixes"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/node_type_customization.rst:6
msgid ""
"Many times, when editing a scene, there are common tasks that need to be "
"done after exporting:"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/node_type_customization.rst:9
#, fuzzy
msgid "Adding collision detection to objects."
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/node_type_customization.rst:10
msgid "Setting objects as navigation meshes."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/node_type_customization.rst:11
msgid ""
"Deleting nodes that are not used in the game engine (like specific lights "
"used for modeling)."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/node_type_customization.rst:14
msgid ""
"To simplify this workflow, Godot offers several suffixes that can be added "
"to the names of the objects in your 3D modeling software. When imported, "
"Godot will detect suffixes in object names and will perform actions "
"automatically."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/node_type_customization.rst:20
msgid "All the suffixes described below are **case-sensitive**."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/node_type_customization.rst:23
msgid "Remove nodes (-noimp)"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/node_type_customization.rst:25
msgid ""
"Objects that have the ``-noimp`` suffix will be removed at import-time no "
"matter what their type is. They will not appear in the imported scene."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/node_type_customization.rst:28
msgid ""
"This is equivalent to enabling **Skip Import** for a node in the Advanced "
"Import Settings dialog."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/node_type_customization.rst:32
msgid "Create collisions (-col, -convcol, -colonly, -convcolonly)"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/node_type_customization.rst:34
msgid ""
"The option ``-col`` will work only for Mesh objects. If it is detected, a "
"child static collision node will be added, using the same geometry as the "
"mesh. This will create a triangle mesh collision shape, which is a slow, but "
"accurate option for collision detection. This option is usually what you "
"want for level geometry (but see also ``-colonly`` below)."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/node_type_customization.rst:40
msgid ""
"The option ``-convcol`` will create a :ref:`class_ConvexPolygonShape3D` "
"instead of a :ref:`class_ConcavePolygonShape3D`. Unlike triangle meshes "
"which can be concave, a convex shape can only accurately represent a shape "
"that doesn't have any concave angles (a pyramid is convex, but a hollow box "
"is concave). Due to this, convex collision shapes are generally not suited "
"for level geometry. When representing simple enough meshes, convex collision "
"shapes can result in better performance compared to a triangle collision "
"shape. This option is ideal for simple or dynamic objects that require "
"mostly-accurate collision detection."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/node_type_customization.rst:49
msgid ""
"However, in both cases, the visual geometry may be too complex or not smooth "
"enough for collisions. This can create physics glitches and slow down the "
"engine unnecessarily."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/node_type_customization.rst:53
msgid ""
"To solve this, the ``-colonly`` modifier exists. It will remove the mesh "
"upon importing and will create a :ref:`class_StaticBody3D` collision "
"instead. This helps the visual mesh and actual collision to be separated."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/node_type_customization.rst:57
msgid ""
"The option ``-convcolonly`` works in a similar way, but will create a :ref:"
"`class_ConvexPolygonShape3D` instead using convex decomposition."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/node_type_customization.rst:60
msgid ""
"With Collada files, the option ``-colonly`` can also be used with Blender's "
"empty objects. On import, it will create a :ref:`class_StaticBody3D` with a "
"collision node as a child. The collision node will have one of a number of "
"predefined shapes, depending on Blender's empty draw type:"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/node_type_customization.rst:69
msgid "Choosing a draw type for an Empty on creation in Blender"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/node_type_customization.rst:71
msgid "Single arrow will create a :ref:`class_SeparationRayShape3D`."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/node_type_customization.rst:72
#, fuzzy
msgid "Cube will create a :ref:`class_BoxShape3D`."
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/node_type_customization.rst:73
msgid "Image will create a :ref:`class_WorldBoundaryShape3D`."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/node_type_customization.rst:74
msgid ""
"Sphere (and the others not listed) will create a :ref:`class_SphereShape3D`."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/node_type_customization.rst:76
msgid ""
"When possible, **try to use a few primitive collision shapes** instead of "
"triangle mesh or convex shapes. Primitive shapes often have the best "
"performance and reliability."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/node_type_customization.rst:82
msgid ""
"For better visibility on Blender's editor, you can set the \"X-Ray\" option "
"on collision empties and set some distinct color for them by changing **Edit "
"> Preferences > Themes > 3D Viewport > Empty**."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/node_type_customization.rst:86
msgid ""
"If using Blender 2.79 or older, follow these steps instead: **User "
"Preferences > Themes > 3D View > Empty**."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/node_type_customization.rst:91
msgid ""
"See :ref:`doc_collision_shapes_3d` for a comprehensive overview of collision "
"shapes."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/node_type_customization.rst:95
msgid "Create Occluder (-occ, -occonly)"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/node_type_customization.rst:97
msgid ""
"If a mesh is imported with the ``-occ`` suffix an :ref:`class_occluder3D` "
"node will be created based on the geometry of the mesh, it does not replace "
"the mesh. A mesh node with the ``-occonly`` suffix will be converted to an :"
"ref:`class_occluder3D` on import."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/node_type_customization.rst:103
msgid "Create navigation (-navmesh)"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/node_type_customization.rst:105
msgid ""
"A mesh node with the ``-navmesh`` suffix will be converted to a navigation "
"mesh. The original Mesh object will be removed at import-time."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/node_type_customization.rst:109
msgid "Create a VehicleBody (-vehicle)"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/node_type_customization.rst:111
msgid ""
"A mesh node with the ``-vehicle`` suffix will be imported as a child to a :"
"ref:`class_VehicleBody3D` node."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/node_type_customization.rst:115
msgid "Create a VehicleWheel (-wheel)"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/node_type_customization.rst:117
msgid ""
"A mesh node with the ``-wheel`` suffix will be imported as a child to a :ref:"
"`class_VehicleWheel3D` node."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/node_type_customization.rst:121
msgid "Rigid Body (-rigid)"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/node_type_customization.rst:123
msgid ""
"A mesh node with the ``-rigid`` suffix will be imported as a :ref:"
"`class_RigidBody3D`."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/node_type_customization.rst:126
msgid "Animation loop (-loop, -cycle)"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/node_type_customization.rst:128
msgid ""
"Animation clips in the source 3D file that start or end with the token "
"``loop`` or ``cycle`` will be imported as a Godot :ref:`class_Animation` "
"with the loop flag set. **Unlike the other suffixes described above, this "
"does not require a hyphen.**"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/node_type_customization.rst:132
msgid ""
"In Blender, this requires using the NLA Editor and naming the Action with "
"the ``loop`` or ``cycle`` prefix or suffix."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/import_configuration.rst:4
#, fuzzy
msgid "Import configuration"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/import_configuration.rst:6
msgid ""
"Godot provides several ways to customize the imported data, such as the "
"import dock, the advanced import setting dialog, and inherited scenes. This "
"can be used to make further changes to the imported scene, such as adjusting "
"meshes, adding physics information, and adding new nodes. You can also write "
"a script that runs code at the end of the import process to perform "
"arbitrary customization."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/import_configuration.rst:13
msgid ""
"Note that, when applicable, modifying the original data should be preferred "
"to configuring the scene after import. This helps minimize the differences "
"between the 3D modeling application and the imported scene. See the :ref:"
"`doc_importing_3d_scenes_model_export_considerations` and :ref:"
"`doc_importing_3d_scenes_node_type_customization` articles for more "
"information."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/import_configuration.rst:21
msgid "Import workflows"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/import_configuration.rst:23
msgid ""
"Since Godot can only save its own scene format (``.tscn``/``.scn``), Godot "
"cannot save over the original 3D scene file (which uses a different format). "
"This is also a safer approach as it avoids making accidental changes to the "
"source file."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/import_configuration.rst:28
msgid ""
"To allow customizing the scene and its materials, Godot's scene importer "
"allows for different workflows regarding how data is imported."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/import_configuration.rst:35
msgid "Import dock after selecting a 3D scene in the FileSystem dock"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/import_configuration.rst:37
msgid ""
"This import process is customizable using 3 separate interfaces, depending "
"on your needs:"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/import_configuration.rst:39
msgid ""
"The **Import** dock, after selecting the 3D scene by clicking it once in the "
"FileSystem dock."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/import_configuration.rst:41
msgid ""
"The **Advanced Import Settings** dialog, which can be accessed by double-"
"clicking the 3D scene in the FileSystem dock or by clicking the **Advanced…"
"** button in the Import dock. This allows you to customize per-object "
"options in Godot."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/import_configuration.rst:44
msgid ""
":ref:`Import hints <doc_importing_3d_scenes_import_hints>`, which are "
"special suffixes added to object names in the 3D modeling software. This "
"allows you to customize per-object options in the 3D modeling software."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/import_configuration.rst:48
msgid ""
"For basic customization, using the Import dock suffices. However, for more "
"complex operations such as defining material overrides on a per-material "
"basis, you'll need to use the Advanced Import Settings dialog, import hints, "
"or possibly both."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/import_configuration.rst:55
#, fuzzy
msgid "Using the Import dock"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/import_configuration.rst:57
msgid ""
"The following options can be adjusted in the Import dock after selecting a "
"3D scene in the FileSystem dock:"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/import_configuration.rst:60
msgid ""
"**Root Type:** The node type to use as a root node. Using node types that "
"inherit from Node3D is recommended. Otherwise, you'll lose the ability to "
"position the node directly in the 3D editor."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/import_configuration.rst:63
msgid ""
"**Root Name:** The name of the root node in the imported scene. This is "
"generally not noticeable when instancing the scene in the editor (or drag-"
"and-dropping from the FileSystem dock), as the root node is renamed to match "
"the filename in this case."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/import_configuration.rst:67
msgid ""
"**Apply Root Scale:** If enabled, **Root Scale** will be *applied* on the "
"meshes and animations directly, while keeping the root node's scale to the "
"default `(1, 1, 1)`. This means that if you add a child node later on within "
"the imported scene, it won't be scaled. If disabled, **Root Scale** will "
"multiply the scale of the root node instead."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/import_configuration.rst:73
msgid "**Meshes**"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/import_configuration.rst:75
msgid ""
"**Ensure Tangents:** If checked, generate vertex tangents using `Mikktspace "
"<http://www.mikktspace.com/>`__ if the input meshes don't have tangent data. "
"When possible, it's recommended to let the 3D modeling software generate "
"tangents on export instead on relying on this option. Tangents are required "
"for correct display of normal and height maps, along with any material/"
"shader features that require tangents. If you don't need material features "
"that require tangents, disabling this can reduce output file size and speed "
"up importing if the source 3D file doesn't contain tangents."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/import_configuration.rst:83
msgid ""
"**Generate LODs:** If checked, generates lower detail variants of the mesh "
"which will be displayed in the distance to improve rendering performance. "
"Not all meshes benefit from LOD, especially if they are never rendered from "
"far away. Disabling this can reduce output file size and speed up importing. "
"See :ref:`doc_mesh_lod` for more information."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/import_configuration.rst:88
msgid ""
"**Create Shadow Meshes:** If checked, enables the generation of shadow "
"meshes on import. This optimizes shadow rendering without reducing quality "
"by welding vertices together when possible. This in turn reduces the memory "
"bandwidth required to render shadows. Shadow mesh generation currently "
"doesn't support using a lower detail level than the source mesh (but shadow "
"rendering will make use of LODs when relevant)."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/import_configuration.rst:94
msgid ""
"**Light Baking:** Configures the meshes' :ref:`global illumination mode "
"<class_GeometryInstance3D_property_gi_mode>` in the 3D scene. If set to "
"**Static Lightmaps**, sets the meshes' GI mode to **Static** and generates "
"UV2 on import for :ref:`lightmap baking <doc_using_lightmap_gi>`."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/import_configuration.rst:98
msgid ""
"**Lightmap Texel Size:** Only visible if **Light Baking** is set to **Static "
"Lightmaps**. Controls the size of each texel on the baked lightmap. A "
"smaller value results in more precise lightmaps, at the cost of larger "
"lightmap sizes and longer bake times."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/import_configuration.rst:103
msgid "**Skins**"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/import_configuration.rst:105
msgid ""
"**Use Named Skins:** If checked, use named :ref:`Skins <class_Skin>` for "
"animation. The :ref:`class_MeshInstance3D` node contains 3 properties of "
"relevance here: a skeleton NodePath pointing to the Skeleton3D node (usually "
"``..``), a mesh, and a skin:"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/import_configuration.rst:109
msgid ""
"The :ref:`class_Skeleton3D` node contains a list of bones with names, their "
"pose and rest, a name and a parent bone."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/import_configuration.rst:111
msgid ""
"The mesh is all of the raw vertex data needed to display a mesh. In terms of "
"the mesh, it knows how vertices are weight-painted and uses some internal "
"numbering often imported from 3D modeling software."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/import_configuration.rst:114
msgid ""
"The skin contains the information necessary to bind this mesh onto this "
"Skeleton3D. For every one of the internal bone IDs chosen by the 3D modeling "
"software, it contains two things. Firstly, a Matrix known as the Bind Pose "
"Matrix, Inverse Bind Matrix, or IBM for short. Secondly, the Skin contains "
"each bone's name (if **Use Named Skins** is enabled), or the bone's index "
"within the Skeleton3D list (if **Use Named Skins** is disabled)."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/import_configuration.rst:120
msgid ""
"Together, this information is enough to tell Godot how to use the bone poses "
"in the Skeleton3D node to render the mesh from each MeshInstance3D. Note "
"that each MeshInstance3D may share binds, as is common in models exported "
"from Blender, or each MeshInstance3D may use a separate Skin object, as is "
"common in models exported from other tools such as Maya."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/import_configuration.rst:127
#, fuzzy
msgid "**Animation**"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/import_configuration.rst:129
msgid "**Import:** If checked, import animations from the 3D scene."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/import_configuration.rst:130
msgid ""
"**FPS:** The number of frames per second to use for baking animation curves "
"to a series of points with linear interpolation. It's recommended to "
"configure this value to match the value you're using as a baseline in your "
"3D modeling software. Higher values result in more precise animation with "
"fast movement changes, at the cost of higher file sizes and memory usage. "
"Thanks to interpolation, there is usually not much benefit in going above 30 "
"FPS (as the animation will still appear smooth at higher rendering "
"framerates)."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/import_configuration.rst:137
msgid ""
"**Trimming:** Trim the beginning and end of animations if there are no "
"keyframe changes. This can reduce output file size and memory usage with "
"certain 3D scenes, depending on the contents of their animation tracks."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/import_configuration.rst:140
msgid ""
"**Remove Immutable Tracks:** Remove animation tracks that only contain "
"default values. This can reduce output file size and memory usage with "
"certain 3D scenes, depending on the contents of their animation tracks."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/import_configuration.rst:144
msgid "**Import Script**"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/import_configuration.rst:146
msgid ""
"**Path:** Path to an import script, which can run code *after* the import "
"process has completed for custom processing. See :ref:"
"`doc_importing_3d_scenes_import_script` for more information."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/import_configuration.rst:150
msgid "**glTF**"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/import_configuration.rst:152
msgid ""
"**Embedded Texture Handling:** Controls how textures embedded within glTF "
"scenes should be handled. **Discard All Textures** will not import any "
"textures, which is useful if you wish to manually set up materials in Godot "
"instead. **Extract Textures** extracts textures to external images, "
"resulting in smaller file sizes and more control over import options. "
"**Embed as Basis Universal** and **Embed as Uncompressed** keeps the "
"textures embedded in the imported scene, with and without VRAM compression "
"respectively."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/import_configuration.rst:161
msgid "Using the Advanced Import Settings dialog"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/import_configuration.rst:163
msgid ""
"The first tab you'll see is the **Scene** tab. The options available in the "
"panel on the right are identical to the Import dock, but you have access to "
"a 3D preview. The 3D preview can be rotated by holding down the left mouse "
"button then dragging the mouse. Zoom can be adjusted using the mouse wheel."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/import_configuration.rst:172
msgid "Advanced Import Settings dialog (Scene tab)"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/import_configuration.rst:172
msgid ""
"Advanced Import Settings dialog (Scene tab). Credit: `Modern Arm Chair 01 - "
"Poly Haven <https://polyhaven.com/a/modern_arm_chair_01>`__"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/import_configuration.rst:175
#, fuzzy
msgid "**Configuring node import options**"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/import_configuration.rst:177
msgid ""
"You can select individual nodes that compose the scene while in the "
"**Scene** tab using the tree view at the left:"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/import_configuration.rst:184
msgid "Selecting a node in the Advanced Import Settings dialog (Scene tab)"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/import_configuration.rst:184
msgid "Selecting a node in the Advanced Import Settings dialog (Materials tab)"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/import_configuration.rst:186
msgid "This exposes several per-node import options:"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/import_configuration.rst:188
msgid ""
"**Skip Import:** If checked, the node will not be present in the final "
"imported scene. Enabling this disables all other options."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/import_configuration.rst:190
msgid ""
"**Generate > Physics:** If checked, generates a PhysicsBody3D *parent* node "
"with collision shapes that are *siblings* to the MeshInstance3D node."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/import_configuration.rst:192
msgid ""
"**Generate > NavMesh:** If checked, generates a NavigationRegion3D *child* "
"node for :ref:`navigation <doc_navigation_overview_3d>`. **Mesh + NavMesh** "
"will keep the original mesh visible, while **NavMesh Only** will only import "
"the navigation mesh (without a visual representation). **NavMesh Only** is "
"meant to be used when you've manually authored a simplified mesh for "
"navigation."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/import_configuration.rst:197
msgid ""
"**Generate > Occluder:** If checked, generates an OccluderInstance3D "
"*sibling* node for :ref:`occlusion culling <doc_occlusion_culling>` using "
"the mesh's geometry as a basis for the occluder's shape. **Mesh + Occluder** "
"will keep the original mesh visible, while **Occluder Only** will only "
"import the occluder (without a visual representation). **Occluder Only** is "
"meant to be used when you've manually authored a simplified mesh for "
"occlusion culling."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/import_configuration.rst:204
msgid ""
"These options are only visible if some of the above options are enabled:"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/import_configuration.rst:206
msgid ""
"**Physics > Body Type:** Only visible if **Generate > Physics** is enabled. "
"Controls the PhysicsBody3D that should be created. **Static** creates a "
"StaticBody3D, **Dynamic** creates a RigidBody3D, **Area** creates an Area3D."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/import_configuration.rst:209
msgid ""
"**Physics > Shape Type:** Only visible if **Generate > Physics** is enabled. "
"**Trimesh** allows for precise per-triangle collision, but it can only be "
"used with a **Static** body type. Other types are less precise and may "
"require manual configuration, but can be used with any body type. For static "
"level geometry, use **Trimesh**. For dynamic geometry, use primitive shapes "
"if possible for better performance, or use one of the convex decomposition "
"modes if the shape is large and complex."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/import_configuration.rst:216
msgid ""
"**Decomposition > Advanced:** Only visible if **Physics > Shape Type** is "
"**Decompose Convex**. If checked, allows adjusting advanced decomposition "
"options. If disabled, only a preset **Precision** can be adjusted (which is "
"usually sufficient)."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/import_configuration.rst:220
msgid ""
"**Decomposition > Precision:** Only visible if **Physics > Shape Type** is "
"**Decompose Convex**. Controls the precision to use for convex "
"decomposition. Higher values result in more detailed collision, at the cost "
"of slower generation and increased CPU usage during physics simulation. To "
"improve performance, it's recommended to keep this value as low as possible "
"for your use cases."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/import_configuration.rst:226
msgid ""
"**Occluder > Simplification Distance:** Only visible if **Generate > "
"Occluder** is set to **Mesh + Occluder** or **Occluder Only**. Higher values "
"result in a occluder mesh with fewer vertices (resulting in decreased CPU "
"utilization), at the cost of more occlusion culling issues (such as false "
"positives or false negatives). If you run into objects disappearing when "
"they shouldn't when the camera is near a certain mesh, try decreasing this "
"value."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/import_configuration.rst:233
msgid "**Configuring mesh and material import options**"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/import_configuration.rst:235
msgid ""
"In the Advanced Import Settings dialog, there are 2 ways to select "
"individual meshes or materials:"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/import_configuration.rst:238
msgid ""
"Switch to the **Meshes** or **Materials** tab in the top-left corner of the "
"dialog."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/import_configuration.rst:239
msgid ""
"Stay in the **Scene** tab, but unfold the options on the tree view on the "
"left. After choosing a mesh or material, this presents the same information "
"as the **Meshes** and **Materials** tabs, but in a tree view instead of a "
"list."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/import_configuration.rst:243
msgid ""
"If you select a mesh, different options will appear in the panel on the "
"right:"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/import_configuration.rst:249
msgid "Advanced Import Settings dialog (Meshes tab)"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/import_configuration.rst:251
msgid "The options are as follows:"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/import_configuration.rst:253
msgid ""
"**Save to File:** Saves the :ref:`class_Mesh` *resource* to an external file "
"(this isn't a scene file). You generally don't need to use this for placing "
"the mesh in a 3D scene – instead, you should instance the 3D scene directly. "
"However, having direct access to the Mesh resource is useful for specific "
"nodes, such as :ref:`class_MeshInstance3D`, :ref:"
"`class_MultiMeshInstance3D`, :ref:`class_GPUParticles3D` or :ref:"
"`class_CPUParticles3D`. - You will also need to specify an output file path "
"using the option that appears after enabling **Save to File**. It's "
"recommended to use the ``.res`` output file extension for smaller file sizes "
"and faster loading speeds, as ``.tres`` is inefficient for writing large "
"amounts of data."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/import_configuration.rst:263
msgid ""
"**Generate > Shadow Meshes:** Per-mesh override for the **Meshes > Create "
"Shadow Meshes** scene-wide import option described in :ref:"
"`doc_importing_3d_scenes_using_the_import_dock`. **Default** will use the "
"scene-wide import option, while **Enable** or **Disable** can forcibly "
"enable or disable this behavior on a specific mesh."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/import_configuration.rst:268
msgid ""
"**Generate > Lightmap UV:** Per-mesh override for the **Meshes > Light "
"Baking** scene-wide import option described in :ref:"
"`doc_importing_3d_scenes_using_the_import_dock`. **Default** will use the "
"scene-wide import option, while **Enable** or **Disable** can forcibly "
"enable or disable this behavior on a specific mesh. - Setting this to "
"**Enable** on a scene with the **Static** light baking mode is equivalent to "
"configuring this mesh to use **Static Lightmaps**. Setting this to "
"**Disable** on a scene with the **Static Lightmaps** light baking mode is "
"equivalent to configuring this mesh to use **Static** instead."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/import_configuration.rst:277
msgid ""
"**Generate > LODs:** Per-mesh override for the **Meshes > Generate LODs** "
"scene-wide import option described in :ref:"
"`doc_importing_3d_scenes_using_the_import_dock`. **Default** will use the "
"scene-wide import option, while **Enable** or **Disable** can forcibly "
"enable or disable this behavior on a specific mesh."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/import_configuration.rst:282
msgid ""
"**LODs > Normal Split Angle:** The minimum angle difference between two "
"vertices required to preserve a geometry edge in mesh LOD generation. If "
"running into visual issues with LOD generation, decreasing this value may "
"help (at the cost of less efficient LOD generation)."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/import_configuration.rst:286
msgid ""
"**LODs > Normal Merge Angle:** The minimum angle difference between two "
"vertices required to preserve a geometry edge in mesh LOD generation. If "
"running into visual issues with LOD generation, decreasing this value may "
"help (at the cost of less efficient LOD generation)."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/import_configuration.rst:291
msgid ""
"If you select a material, only one option will appear in the panel on the "
"right:"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/import_configuration.rst:297
msgid "Advanced Import Settings dialog (Materials tab)"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/import_configuration.rst:299
msgid ""
"When **Use External** is checked and an output path is specified, this lets "
"you use an external material instead of the material that is included in the "
"original 3D scene file; see the section below."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/import_configuration.rst:304
#, fuzzy
msgid "Extracting materials to separate files"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/import_configuration.rst:306
msgid ""
"While Godot can import materials authored in 3D modeling software, the "
"default configuration may not be suitable for your needs. For example:"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/import_configuration.rst:309
msgid ""
"You want to configure material features not supported by your 3D application."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/import_configuration.rst:310
msgid ""
"You want to use a different texture filtering mode, as this option is "
"configured in the material since Godot 4.0 (and not in the image)."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/import_configuration.rst:312
msgid ""
"You want to replace one of the materials with an entirely different "
"material, such as a custom shader."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/import_configuration.rst:315
msgid ""
"To be able to modify the 3D scene's materials in the Godot editor, you need "
"to use *external* material resources."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/import_configuration.rst:318
msgid ""
"In the top-left corner of the Advanced Import Settings dialog, choose "
"**Actions… > Extract Materials**:"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/import_configuration.rst:325
msgid ""
"Extracting all built-in materials to external resources in the Advanced "
"Import Settings dialog"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/import_configuration.rst:327
msgid ""
"After choosing this option, select a folder to extract material ``.tres`` "
"files to, then confirm the extraction:"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/import_configuration.rst:334
msgid ""
"Confirming material extraction in the Advanced Import Settings subdialog"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/import_configuration.rst:338
msgid ""
"After extracting materials, the 3D scene will automatically be configured to "
"use external material references. As a result, you don't need to manually "
"enable **Use External** on every material to make the external ``.tres`` "
"material effective."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/import_configuration.rst:343
msgid ""
"When **Use External** is enabled, remember that the Advanced Import Settings "
"dialog will keep displaying the mesh's original materials (the ones designed "
"in the 3D modeling software). This means your customizations to the "
"materials won't be visible within this dialog. To preview your modified "
"materials, you need to place the imported 3D scene in another scene using "
"the editor."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/import_configuration.rst:349
msgid ""
"Godot will not overwrite changes made to extracted materials when the source "
"3D scene is reimported. However, if the material name is changed in the "
"source 3D file, the link between the original material and the extracted "
"material will be lost. As a result, you'll need to use the Advanced Import "
"Settings dialog to associate the renamed material to the existing extracted "
"material."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/import_configuration.rst:355
msgid ""
"The above can be done in the dialog's **Materials** tab by selecting the "
"material, enabling **Save to File**, then specifying the save path using the "
"**Path** option that appears after enabling **Save to File**."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/import_configuration.rst:362
msgid "Using import scripts for automation"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/import_configuration.rst:364
msgid ""
"A special script to process the whole scene after import can be provided. "
"This is great for post-processing, changing materials, doing funny stuff "
"with the geometry, and more."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/import_configuration.rst:368
msgid ""
"Create a script that is not attached to any node by right-clicking in the "
"FileSystem dock and choosing **New > Script…**. In the script editor, write "
"the following:"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/import_configuration.rst:394
msgid ""
"The ``_post_import(scene: Node)`` function takes the imported scene as "
"argument (the parameter is actually the root node of the scene). The scene "
"that will finally be used **must** be returned (even if the scene can be "
"entirely different)."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/import_configuration.rst:399
#, fuzzy
msgid "Using animation libraries"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/import_configuration.rst:401
msgid ""
"As of Godot 4.0, you can choose to import **only** animations from a glTF "
"file and nothing else. This is used in some asset pipelines to distribute "
"animations separately from models. For example, this allows you to use one "
"set of animations for several characters, without having to duplicate "
"animation data in every character."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/import_configuration.rst:407
msgid ""
"To do so, select the glTF file in the FileSystem dock, then change the "
"import mode to Animation Library in the Import dock:"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/import_configuration.rst:414
msgid "Changing the import type to Animation Library in the Import dock"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/import_configuration.rst:416
msgid ""
"Click **Reimport** and restart the editor when prompted. After restarting, "
"the glTF file will be imported as an :ref:`class_AnimationLibrary` instead "
"of a :ref:`class_PackedScene`. This animation library can then be referenced "
"in an :ref:`class_AnimationPlayer` node."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/import_configuration.rst:421
msgid ""
"The import options that are visible after changing the import mode to "
"Animation Library act the same as when using the Scene import mode. See :ref:"
"`doc_importing_3d_scenes_using_the_import_dock` for more information."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/import_configuration.rst:426
#, fuzzy
msgid "Filter script"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/import_configuration.rst:428
msgid ""
"It is possible to specify a filter script in a special syntax to decide "
"which tracks from which animations should be kept."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/import_configuration.rst:431
msgid ""
"The filter script is executed against each imported animation. The syntax "
"consists of two types of statements, the first for choosing which animations "
"to filter, and the second for filtering individual tracks within the matched "
"animation. All name patterns are performed using a case-insensitive "
"expression match, with support for ``?`` and ``*`` wildcards (using :ref:"
"`String.matchn() <class_String_method_matchn>` under the hood)."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/import_configuration.rst:438
msgid ""
"The script must start with an animation filter statement (as denoted by the "
"line beginning with an ``@``). For example, if we would like to apply "
"filters to all imported animations which have a name ending in "
"``\"_Loop\"``::"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/import_configuration.rst:444
msgid ""
"Similarly, additional patterns can be added to the same line, separated by "
"commas. Here is a modified example to additionally *include* all animations "
"with names that begin with ``\"Arm_Left\"``, but also *exclude* all "
"animations which have names ending in ``\"Attack\"``::"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/import_configuration.rst:451
msgid ""
"Following the animation selection filter statement, we add track filtering "
"patterns to indicate which animation tracks should be kept or discarded. If "
"no track filter patterns are specified, then all tracks within the matched "
"animations will be discarded!"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/import_configuration.rst:456
msgid ""
"It's important to note that track filter statements are applied in order for "
"each track within the animation, this means that one line may include a "
"track, a later rule can still discard it. Similarly, a track excluded by an "
"early rule may then be re-included once again by a filter rule further down "
"in the filter script."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/import_configuration.rst:462
msgid ""
"For example: include all tracks in animations with names ending in "
"``\"_Loop\"``, but discard any tracks affecting a ``\"Skeleton\"`` which end "
"in ``\"Control\"``, unless they have ``\"Arm\"`` in their name::"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/import_configuration.rst:471
msgid ""
"In the above example, tracks like ``\"Skeleton:Leg_Control\"`` would be "
"discarded, while tracks such as ``\"Skeleton:Head\"`` or ``\"Skeleton:"
"Arm_Left_Control\"`` would be retained."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/import_configuration.rst:475
msgid ""
"Any track filter lines that do not begin with a ``+`` or ``-`` are ignored."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/import_configuration.rst:478
msgid "Storage"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/import_configuration.rst:480
msgid ""
"By default, animations are saved as built-in. It is possible to save them to "
"a file instead. This allows adding custom tracks to the animations and "
"keeping them after a reimport."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/import_configuration.rst:485
msgid "Optimizer"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/import_configuration.rst:487
msgid ""
"When animations are imported, an optimizer is run, which reduces the size of "
"the animation considerably. In general, this should always be turned on "
"unless you suspect that an animation might be broken due to it being enabled."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/import_configuration.rst:492
msgid "Clips"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/import_configuration.rst:494
msgid ""
"It is possible to specify multiple animations from a single timeline as "
"clips. For this to work, the model must have only one animation that is "
"named ``default``. To create clips, change the clip amount to something "
"greater than zero. You can then name a clip, specify which frames it starts "
"and stops on, and choose whether the animation loops or not."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/import_configuration.rst:501
msgid "Scene inheritance"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/import_configuration.rst:503
msgid ""
"In many cases, it may be desired to make manual modifications to the "
"imported scene. By default, this is not possible because if the source 3D "
"asset changes, Godot will re-import the *whole* scene."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/import_configuration.rst:507
msgid ""
"However, it is possible to make local modifications by using *scene "
"inheritance*. If you try to open the imported scene using **Scene > Open "
"Scene…** or **Scene > Quick Open Scene…**, the following dialog will appear:"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/import_configuration.rst:515
msgid "Dialog when opening an imported 3D scene in the editor"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/import_configuration.rst:517
msgid "In inherited scenes, the only limitations for modification are:"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/import_configuration.rst:519
msgid ""
"Nodes from the base scene can't be removed, but additional nodes can be "
"added anywhere."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/import_configuration.rst:521
msgid ""
"Subresources can't be edited. Instead, you need to save them externally as "
"described above."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/importing_3d_scenes/import_configuration.rst:524
msgid "Other than that, everything is allowed."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/retargeting_3d_skeletons.rst:4
#, fuzzy
msgid "Retargeting 3D Skeletons"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/assets_pipeline/retargeting_3d_skeletons.rst:7
msgid "To share animations among multiple Skeletons"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/retargeting_3d_skeletons.rst:9
msgid ""
"Godot has Position/Rotation/Scale 3D tracks (which this document calls "
"\"Transform\" tracks) with Nodepaths to bones for Skeleton bone animation. "
"This means you can't share animations between multiple Skeletons just by "
"using the same bone names."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/retargeting_3d_skeletons.rst:14
msgid ""
"Godot allows each bone to have a parent-child relationship and can have "
"rotation and scale as well as position, which means that bones that share a "
"name can still have different Transform values."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/retargeting_3d_skeletons.rst:18
msgid ""
"The Skeleton stores the Transform values necessary for the default pose as "
"Bone Rest. If Bone Pose is equal to Bone Rest, it means that the Skeleton is "
"in the default pose."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/retargeting_3d_skeletons.rst:21
msgid ""
"Godot 3.x and Godot 4.0+ have different Bone Pose behaviors. In Godot 3.x, "
"Bone Pose is relative to Bone Rest, but in Godot 4.0+, it includes Bone "
"Rest. See this `article <https://godotengine.org/article/animation-data-"
"redesign-40>`__."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/retargeting_3d_skeletons.rst:25
msgid ""
"Skeletal models have different Bone Rests depending on the environment from "
"which they were exported. For example, the bones of a glTF model output from "
"Blender have \"Edit Bone Orientation\" as the Bone Rest rotation. However, "
"there are skeletal models without any Bone Rest rotations, such as the glTF "
"model output from Maya."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/retargeting_3d_skeletons.rst:30
msgid ""
"To share animations in Godot, it is necessary to match Bone Rests as well as "
"Bone Names to remove unwanted tracks in some cases. In Godot 4.0+, you can "
"do that using the scene importer."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/retargeting_3d_skeletons.rst:35
msgid "Options for Retargeting"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/retargeting_3d_skeletons.rst:38
msgid "Bone Map"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/retargeting_3d_skeletons.rst:40
msgid ""
"When you select the Skeleton3D node in the advanced scene import menu, a "
"menu will appear on the right-hand side containing the \"Retarget\" section. "
"The Retarget section has a single property ``bone_map``."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/retargeting_3d_skeletons.rst:46
msgid ""
"With the Skeleton node selected, first set up a new :ref:`class_bonemap` "
"and :ref:`class_skeletonprofile`. Godot has a preset called :ref:"
"`class_skeletonprofilehumanoid` for humanoid models. This tutorial proceeds "
"with the assumption that you are using :ref:`class_skeletonprofilehumanoid`."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/retargeting_3d_skeletons.rst:50
msgid ""
"If you need a profile for a model such as a beast or creature, you can "
"export a :ref:`class_skeletonprofile` from SkeletonEditor with some "
"information converted from Skeleton."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/retargeting_3d_skeletons.rst:53
msgid ""
"When you use :ref:`class_skeletonprofilehumanoid`, auto-mapping will be "
"performed when the :ref:`class_skeletonprofile` is set. If the auto-mapping "
"does not work well, you can map bones manually."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/retargeting_3d_skeletons.rst:58
msgid ""
"Any missing, duplicate or incorrect parent-child relationship mappings will "
"be indicated by a magenta / red button (depending on the editor setting). It "
"does not block the import process, but it warns that animations may not be "
"shared correctly."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/retargeting_3d_skeletons.rst:62
msgid ""
"The auto-mapping uses pattern matching for the bone names. So we recommend "
"to use common English names for bones."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/retargeting_3d_skeletons.rst:65
msgid ""
"After you set up the ``bone_map``, several options are available in the "
"sections below."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/retargeting_3d_skeletons.rst:70
msgid "Remove Tracks"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/retargeting_3d_skeletons.rst:72
msgid ""
"If you import resources as an :ref:`class_animationlibrary` that will be "
"shared, we recommend to enable these options. However, if you import "
"resources as scenes, these should be disabled in some cases. For example, if "
"you import a character with animated accessories, these options may cause "
"the accessories to not animate."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/retargeting_3d_skeletons.rst:78
msgid "Except Bone Transform"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/retargeting_3d_skeletons.rst:80
msgid "Removes any tracks except the bone Transform track from the animations."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/retargeting_3d_skeletons.rst:83
#, fuzzy
msgid "Unimportant Positions"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/assets_pipeline/retargeting_3d_skeletons.rst:85
msgid ""
"Removes Position tracks other than ``root_bone`` and ``scale_base_bone`` "
"defined in :ref:`class_skeletonprofile` from the animations. In :ref:"
"`class_skeletonprofilehumanoid`, this means that to remove Position tracks "
"other than \"Root\" and \"Hips\". Since Godot 4.0+, animations include Bone "
"Rest in the Transform value. If you disable this option, the animation may "
"change the body shape unpredictably."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/retargeting_3d_skeletons.rst:92
msgid "Unmapped Bones"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/retargeting_3d_skeletons.rst:94
msgid "Removes unmapped bone Transform tracks from the animations."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/retargeting_3d_skeletons.rst:97
msgid "Bone Renamer"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/retargeting_3d_skeletons.rst:100
msgid "Rename Bones"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/retargeting_3d_skeletons.rst:102
msgid "Rename the mapped bones."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/retargeting_3d_skeletons.rst:105
msgid "Unique Node"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/retargeting_3d_skeletons.rst:107
msgid ""
"Makes Skeleton a unique node with the name specified in the "
"``skeleton_name``. This allows the animation track paths to be unified "
"independent of the scene hierarchy."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/retargeting_3d_skeletons.rst:111
msgid "Rest Fixer"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/retargeting_3d_skeletons.rst:113
msgid ""
"Reference poses defined in :ref:`class_skeletonprofilehumanoid` have the "
"following rules:"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/retargeting_3d_skeletons.rst:115
msgid "The humanoid is T-pose"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/retargeting_3d_skeletons.rst:116
msgid "The humanoid is facing +Z in the Right-Handed Y-UP Coordinate System"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/retargeting_3d_skeletons.rst:117
msgid "The humanoid should not have a Transform as Node"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/retargeting_3d_skeletons.rst:118
msgid "Directs the +Y axis from the parent joint to the child joint"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/retargeting_3d_skeletons.rst:119
msgid "+X rotation bends the joint like a muscle contracting"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/retargeting_3d_skeletons.rst:121
msgid ""
"These rules are convenient definitions for blend animation and Inverse "
"Kinematics (IK). If your model does not match this definition, you need to "
"fix it with these options."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/retargeting_3d_skeletons.rst:125
msgid "Apply Node Transform"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/retargeting_3d_skeletons.rst:127
msgid ""
"If the asset is not exported correctly for sharing, the imported Skeleton "
"may have a Transform as a Node. For example, a glTF exported from Blender "
"with no \"Apply Transform\" executed is one such case. It looks like the "
"model matches the definition, but the internal Transforms are different from "
"the definition. This option fixes such models by applying Transforms on "
"import."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/retargeting_3d_skeletons.rst:133
msgid ""
"If the imported scene contains objects other than Skeletons, this option may "
"have a negative effect."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/retargeting_3d_skeletons.rst:136
msgid "Normalize Position Tracks"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/retargeting_3d_skeletons.rst:138
msgid ""
"Position track is used mostly for model movement, but sharing the moving "
"animation between models with different heights may cause the appearance of "
"slipping due to the difference in stride length. This option normalizes the "
"Position track values based on the ``scale_base_bone`` height. The "
"``scale_base_bone`` height is stored in the Skeleton as the "
"``motion_scale``, and the normalized Position track values is multiplied by "
"that value on playback. If this option is disabled, the Position tracks is "
"not normalized and the Skeleton's ``motion_scale`` is always imported as "
"``1.0``."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/retargeting_3d_skeletons.rst:146
msgid ""
"With :ref:`class_skeletonprofilehumanoid`, ``scale_base_bone`` is \"Hips\", "
"therefore the Hips' height is used as the ``motion_scale``."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/retargeting_3d_skeletons.rst:149
msgid "Overwrite Axis"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/retargeting_3d_skeletons.rst:151
msgid ""
"Unifies the models' Bone Rests by overwriting it to match the reference "
"poses defined in the :ref:`class_skeletonprofile`."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/retargeting_3d_skeletons.rst:153
msgid ""
"This is the most important option for sharing animations in Godot 4.0+, but "
"be aware that this option can produce horrible results **if the original "
"Bone Rest set externally is important**. If you want to share animations "
"with keeping the original Bone Rest, consider to use the `Realtime Retarget "
"Module <https://github.com/TokageItLab/realtime_retarget>`__."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/retargeting_3d_skeletons.rst:159
msgid "Fix Silhouette"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/retargeting_3d_skeletons.rst:161
msgid ""
"Attempts to make the model's silhouette match that of the reference poses "
"defined in the :ref:`class_skeletonprofile`, such as T-Pose. This cannot fix "
"silhouettes which are too different, and it may not work for fixing bone "
"roll."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/retargeting_3d_skeletons.rst:164
msgid ""
"With :ref:`class_skeletonprofilehumanoid`, this option does not need to be "
"enabled for T-pose models, but should be enabled for A-pose models. However "
"in that case, the fixed foot results may be bad depending on the heel height "
"of the model, so it may be necessary to add the :ref:`class_skeletonprofile` "
"bone names you do not want fixed in the ``filter`` array, as in the below "
"example."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/retargeting_3d_skeletons.rst:171
msgid ""
"Also, for models with bent knees or feet, it may be necessary to adjust the "
"``scale_base_bone`` height. For that, you can use ``base_height_adjustment`` "
"option."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/exporting_3d_scenes.rst:4
#, fuzzy
msgid "Exporting 3D scenes"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/assets_pipeline/exporting_3d_scenes.rst:7
#: ../../docs/community/asset_library/using_assetlib.rst:10
msgid "Overview"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/exporting_3d_scenes.rst:9
msgid ""
"In Godot, it is possible to export 3D scenes as a glTF 2.0 file. You can "
"export as a glTF binary (``.glb`` file) or glTF embedded with textures "
"(``gltf`` + ``.bin`` + textures). This allows you to create scenes in Godot, "
"such as a CSG mesh blockout for a level, export it to clean it up in a "
"program such as Blender, and then bring it back into Godot."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/exporting_3d_scenes.rst:17
msgid "Only Blender 2.83 and newer can import glTF files exported by Godot."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/exporting_3d_scenes.rst:19
msgid ""
"To export a scene in the editor go to **Scene > Export As... > glTF 2.0 "
"Scene...**"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/exporting_3d_scenes.rst:26
#, fuzzy
msgid "There are several limitations with glTF export."
msgstr "Ne postoje ograničenja prilikom korištenja Godot-a"

#: ../../docs/tutorials/assets_pipeline/exporting_3d_scenes.rst:28
msgid ""
"No support for exporting particles since their implementation varies across "
"engines."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/exporting_3d_scenes.rst:29
msgid "ShaderMaterials cannot be exported."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/exporting_3d_scenes.rst:30
msgid "No support for exporting 2D scenes."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/exporting_3d_scenes.rst:34
msgid ""
"3D scenes can be saved at runtime using :ref:`runtime file loading and "
"saving <doc_runtime_file_loading_and_saving_3d_scenes>`, including from an "
"exported project."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/escn_exporter/index.rst:2
msgid "Blender ESCN exporter"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/escn_exporter/index.rst:4
msgid ""
"This chapter relates to the Blender plugin called \"Godot Blender "
"Exporter\", which can be downloaded here: https://github.com/godotengine/"
"godot-blender-exporter"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/escn_exporter/index.rst:7
msgid ""
"This plugin can be used to export Blender scenes in a Godot-specific scene "
"format called ESCN, which is similar to TSCN (text format) but will be "
"imported as binary SCN for performance."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/escn_exporter/index.rst:12
msgid "Details on exporting"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/escn_exporter/index.rst:27
msgid "Disabling specific objects"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/escn_exporter/index.rst:29
msgid ""
"Sometimes you don't want some objects exported (e.g. high-res models used "
"for baking). An object will not be exported if it is not rendered in the "
"scene. This can be set in the outliner:"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/escn_exporter/index.rst:35
msgid ""
"Objects hidden in the viewport will be exported, but will be hidden in the "
"Godot scene."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/escn_exporter/index.rst:40
msgid "Build pipeline integration"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/escn_exporter/index.rst:42
msgid ""
"If you have hundreds of model files, you don't want your artists to waste "
"time manually exporting their blend files. To combat this, the exporter "
"provides a Python function ``io_scene_godot.export(out_file_path)`` that can "
"be called to export a file. This allows easy integration with other build "
"systems. An example Makefile and Python script that exports all the blends "
"in a directory are present in the `godot-blender-exporter repository "
"<https://github.com/godotengine/godot-blender-exporter>`__."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/escn_exporter/material.rst:5
msgid "Using existing Godot materials"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/escn_exporter/material.rst:7
msgid ""
"One way in which the exporter can handle materials is to attempt to match "
"the Blender material with an existing Godot material. This has the advantage "
"of being able to use all of the features of Godot's material system, but it "
"means that you cannot see your model with the material applied inside "
"Blender."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/escn_exporter/material.rst:12
msgid ""
"To do this, the exporter attempts to find Godot materials with names that "
"match those of the material name in Blender. So if you export an object in "
"Blender with the material name ``PurpleDots`` then the exporter will search "
"for the file ``PurpleDots.tres`` and assign it to the object. If this file "
"is not a ``StandardMaterial3D`` or ``ShaderMaterial`` or if it cannot be "
"found, then the exporter will fall back to exporting the material from "
"Blender."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/escn_exporter/material.rst:20
msgid ""
"Where the exporter searches for the ``.tres`` file is determined by the "
"\"Material Search Paths\" option:"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/escn_exporter/material.rst:34
msgid "This can take the value of:"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/escn_exporter/material.rst:26
msgid ""
"Project Directory - Attempts to find the ``project.Godot`` and recursively "
"searches through subdirectories. If ``project.Godot`` cannot be found it "
"will throw an error. This is useful for most projects where naming conflicts "
"are unlikely."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/escn_exporter/material.rst:30
msgid ""
"Export Directory - Look for materials in subdirectories of the export "
"location. This is useful for projects where you may have duplicate material "
"names and need more control over what material gets assigned."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/escn_exporter/material.rst:33
msgid "None - Do not search for materials. Export them from the Blender file."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/escn_exporter/material.rst:37
msgid "Export of Cycles/EEVEE materials"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/escn_exporter/material.rst:39
msgid ""
"The exporter has a primitive support for converting Cycles/EEVEE material "
"node tree to Godot Shader Material. Note that some of the Shader Node are "
"not supported yet due to difficulties in implementation, which are:"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/escn_exporter/material.rst:43
msgid "all the ``noisy textures``"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/escn_exporter/material.rst:44
msgid "``generated texture coordinates``"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/escn_exporter/material.rst:45
msgid "``group node``"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/escn_exporter/material.rst:46
msgid ""
"shader nodes except ``PrincipledBSDF``, ``Diffuse``, ``Glossy``, ``Glass``, "
"``add shader`` and ``mix shader``"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/escn_exporter/material.rst:50
msgid ""
"If possible, try to use PrincipledBSDF node with GGX distribution as the "
"output shader node, it is the only one guaranteed to be exactly correct. "
"Others are just based on approximation."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/escn_exporter/material.rst:53
msgid ""
"Sometimes materials may not be valid for exporting (e.g. has some "
"unsupported node) or it is using Blender Internal Engine, only the diffuse "
"color and a few flags (e.g. unshaded) are exported and form a "
"StandardMaterial3D."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/escn_exporter/material.rst:59
msgid "Generate external materials"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/escn_exporter/material.rst:61
msgid ""
"The default configuration of material exporting would keep all the materials "
"internal to the ``escn`` file. There is an option which could enable "
"generating external ``.material`` file when the ``escn`` file opens in Godot."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/escn_exporter/material.rst:67
msgid ""
"``.material`` file can be assigned to any material slot to be a external "
"resource."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/escn_exporter/physics.rst:2
msgid "Physics properties"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/escn_exporter/physics.rst:4
msgid ""
"Exporting physics properties is done by enabling \"Rigid Body\" in Blender's "
"physics tab:"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/escn_exporter/physics.rst:10
msgid ""
"By default, a single Blender object with rigid body enabled will export as "
"three nodes: a PhysicsBody, a CollisionShape, and a MeshInstance3D."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/escn_exporter/physics.rst:14
msgid "Body type"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/escn_exporter/physics.rst:16
msgid ""
"Blender only has the concept of \"Active\" and \"Passive\" rigid bodies. "
"These turn into Static and RigidBody nodes. To create a kinematic body, "
"enable the \"animated\" checkbox on an \"Active\" body:"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/escn_exporter/physics.rst:23
#: ../../docs/tutorials/physics/physics_introduction.rst:62
msgid "Collision shapes"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/escn_exporter/physics.rst:25
msgid ""
"Many of the parameters for collision shapes are missing from Blender, and "
"many of the collision shapes are also not present. However, almost all of "
"the options in Blender's rigid body collision and rigid body dynamics "
"interfaces are supported:"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/escn_exporter/physics.rst:39
msgid "There are the following caveats:"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/escn_exporter/physics.rst:33
msgid ""
"Not all of the collision shapes are supported. Only ``Mesh``, ``Convex "
"Hull``, ``Capsule``, ``Sphere`` and ``Box`` are supported in both Blender "
"and Godot"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/escn_exporter/physics.rst:36
msgid ""
"In Godot, you can have different collision groups and collision masks. In "
"Blender you only have collision groups. As a result, the exported object's "
"collision mask is equal to its collision group. Most of the time, this is "
"what you want."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/escn_exporter/physics.rst:42
msgid ""
"To build compound physics shapes, parent together multiple objects with "
"rigid body enabled. The physics properties are taken from the parent-most "
"rigid body, and the rest are used as collision shapes."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/escn_exporter/physics.rst:47
msgid "Collision geometry only"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/escn_exporter/physics.rst:49
msgid ""
"Frequently you want different geometry for your collision meshes and your "
"graphical meshes, but by default, the exporter will export a mesh along with "
"the collision shape. To only export the collision shape, set the object's "
"maximum draw type to Wire:"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/escn_exporter/physics.rst:56
msgid ""
"This will also influence how the object is shown in Blender's viewport. Most "
"of the time, you want your collision geometry to be shown see-through when "
"working on the models, so this works out fairly nicely."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/escn_exporter/lights.rst:4
msgid ""
"By default, lamps in Blender have shadows enabled. This can cause "
"performance issues in Godot."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/escn_exporter/lights.rst:8
msgid ""
"Lamps are exported using their \"Blender Render\" settings. When Blender 2.8 "
"is released, this will be removed and this part of the exporter will change."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/escn_exporter/lights.rst:11
msgid ""
"Sun, point and spot lamps are all exported from Blender along with many of "
"their properties:"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/escn_exporter/lights.rst:16
#, fuzzy
msgid "There are some things to note:"
msgstr "Ne postoje ograničenja prilikom korištenja Godot-a"

#: ../../docs/tutorials/assets_pipeline/escn_exporter/lights.rst:18
msgid ""
"In Blender, a light casts light all the way to infinity. In Godot, it is "
"clamped by the attenuation distance. To most closely match between the "
"viewport and Godot, enable the \"Sphere\" checkbox. (Highlighted green)"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/escn_exporter/lights.rst:21
msgid ""
"Light attenuation models differ between Godot and Blender. The exporter "
"attempts to make them match, but it isn't always very good."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/escn_exporter/lights.rst:23
msgid ""
"Spotlight angular attenuation models also differ between Godot and Blender. "
"The exporter attempts to make them similar, but it doesn't always look the "
"same."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/escn_exporter/lights.rst:26
msgid ""
"There is no difference between buffer shadow and ray shadow in the export."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/escn_exporter/mesh.rst:2
msgid "Mesh"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/escn_exporter/mesh.rst:5
msgid "Modifiers"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/escn_exporter/mesh.rst:6
msgid ""
"There is an exporting option :code:`Apply Modifiers` to control whether mesh "
"modifiers are applied to the exported mesh."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/escn_exporter/mesh.rst:11
msgid "Shape Key"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/escn_exporter/mesh.rst:12
msgid ""
"Exporting mesh shape key is supported, however exporting each shape key is "
"almost like exporting the mesh again, so don't be surprised it takes a "
"relatively long time."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/escn_exporter/mesh.rst:17
msgid ""
"A lot of modifiers are not compatible with shape keys (e.g. subsurface "
"modifier), so if you found you have incorrect shape keys exported, try to "
"disable :code:`Apply Modifiers` and do the exporting again. Besides, it is "
"worthwhile to report the incompatible modifier to the `issue list <https://"
"github.com/godotengine/godot-blender-exporter/issues>`__, which helps to "
"develop the exporter to have a more precise check of modifiers."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/escn_exporter/skeleton.rst:2
msgid "Skeleton"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/escn_exporter/skeleton.rst:7
msgid "Rest Bone"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/escn_exporter/skeleton.rst:9
msgid ""
"Armature object in Blender is exported as a Skeleton node along with rest "
"position (transform in Godot) of bones."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/escn_exporter/skeleton.rst:13
msgid ""
"The three check boxes :code:`Inherit Rotation`, :code:`Inherit Scale`, :code:"
"`Local Location` (colored in red) must be ticked when building armature in "
"Blender, so that the exported bone transform be consistent between Blender "
"and Godot"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/escn_exporter/skeleton.rst:18
msgid ""
"It is important that the mesh is not deformed by bones when exporting in "
"Blender. Make sure that the skeleton is reset to its T-pose or default rest "
"pose."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/escn_exporter/skeleton.rst:22
msgid "Bone Weights"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/escn_exporter/skeleton.rst:24
msgid ""
"Blender puts rigged mesh vertices which have no bone weights at their "
"original position, but these vertices would be placed at (0, 0, 0) in Godot, "
"making the mesh deformed. Therefore, the exporter will raise an error for "
"any vertex with no bone weights detected in a rigged mesh."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/escn_exporter/skeleton.rst:30
msgid "Non-Deform Bone"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/escn_exporter/skeleton.rst:32
msgid ""
"Note that the non-deform bone can be configured as not exported by enabling "
"the :code:`Exclude Control Bones`; the deform bone checkbox is shown in the "
"picture."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/escn_exporter/skeleton.rst:38
msgid "Bone Attachment"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/escn_exporter/skeleton.rst:39
msgid ""
"A bone can be the parent of an object in Blender; this relation is exported "
"as a BoneAttachment node in the Godot scene."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/escn_exporter/animation.rst:8
msgid "Animation supported:"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/escn_exporter/animation.rst:4
msgid "transform animation of all types of objects"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/escn_exporter/animation.rst:5
msgid "transform animation of pose bones"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/escn_exporter/animation.rst:6
msgid "shape key animation"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/escn_exporter/animation.rst:7
msgid "light animation"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/escn_exporter/animation.rst:8
msgid "camera animation"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/escn_exporter/animation.rst:11
msgid "Multiple Actions For Single Object"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/escn_exporter/animation.rst:12
msgid ""
"In most games, one object would have several animations to switch between. "
"This add-on has support for exporting multiple actions all at once into a "
"single AnimationPlayer and makes it easy to switch actions."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/escn_exporter/animation.rst:16
msgid ""
"This workflow makes use of blender nla_tracks. Here is a brief guide on how "
"to use this feature:"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/escn_exporter/animation.rst:19
msgid "**1. Stash active action**"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/escn_exporter/animation.rst:21
msgid ""
"New created action is always an active action bound to object. There are "
"several ways to place an active action into NLA track, one is of course "
"doing it in ``NLA Editor``"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/escn_exporter/animation.rst:28
msgid "Or it can be done stashing the action in ``Dope Sheet``"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/escn_exporter/animation.rst:33
msgid "**2. Check mute status of NLA tracks**"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/escn_exporter/animation.rst:35
msgid ""
"An NLA track can be ``mute`` or ``unmute``, the exporter will export all the "
"``mute`` NLA track as a separate action, while blends all the ``unmute`` NLA "
"tracks into every action (including the action) being exported."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/escn_exporter/animation.rst:41
msgid "**3. Export the scene**"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/escn_exporter/animation.rst:43
msgid "Make sure the ``Export Stashed Actions`` option has been turned on."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/escn_exporter/animation.rst:47
msgid ""
"Then all the stashed actions, as well as the active action, are exported to "
"an AnimationPlayer."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/escn_exporter/animation.rst:54
msgid "Constraints"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/escn_exporter/animation.rst:55
msgid ""
"Sometimes complicated animation is built with object constraint; a usual "
"example is inverse kinematics. The add-on would automatically check if an "
"object has some constraint; if it does, all the constraints are baked into "
"actions and then exported along with the object."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/escn_exporter/animation.rst:62
msgid "Animation Mode"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/escn_exporter/animation.rst:63
msgid ""
"Godot and Blender have different structure to store animation data. In Godot "
"animation data is stored in an AnimationPlayer node, instead of in each "
"animated node. In order to fix this inconsistency and still make the "
"animation play versatile, this add-on has three animation exporting modes."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/escn_exporter/animation.rst:70
msgid "**Mode 'Animation as Actions'**"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/escn_exporter/animation.rst:72
msgid ""
"Treat all the animations as object actions, so in the exported scene, every "
"object would have its own AnimationPlayer and hold its actions."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/escn_exporter/animation.rst:76
msgid "**Mode 'Scene Animation'**"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/escn_exporter/animation.rst:78
msgid ""
"If you want your animation to generate the same result as playing at "
"Blender's timeline, this is what you want. In this mode, all the animations "
"in the scene are placed in just one AnimationPlayer in the scene root."
msgstr ""

#: ../../docs/tutorials/assets_pipeline/escn_exporter/animation.rst:82
msgid "**Mode 'Animation as Action with Squash'**"
msgstr ""

#: ../../docs/tutorials/assets_pipeline/escn_exporter/animation.rst:84
msgid ""
"This mode has very similar behavior of mode 'Animation as Action', but it "
"can generate fewer AnimationPlayers; objects in parent-children relationship "
"would share their AnimationPlayer. It is useful when you have several rigs, "
"and each Skeleton and Mesh has actions; then one rig would have just one "
"AnimationPlayer."
msgstr ""

#: ../../docs/tutorials/audio/audio_buses.rst:6
#: ../../docs/tutorials/audio/audio_buses.rst:50
msgid "Audio buses"
msgstr ""

#: ../../docs/tutorials/audio/audio_buses.rst:11
msgid ""
"Godot's audio processing code has been written with games in mind, with the "
"aim of achieving an optimal balance between performance and sound quality."
msgstr ""

#: ../../docs/tutorials/audio/audio_buses.rst:14
msgid ""
"Godot's audio engine allows any number of audio buses to be created and any "
"number of effect processors can be added to each bus. Only the hardware of "
"the device running your game will limit the number of buses and effects that "
"can be used before performance starts to suffer."
msgstr ""

#: ../../docs/tutorials/audio/audio_buses.rst:20
msgid "Decibel scale"
msgstr ""

#: ../../docs/tutorials/audio/audio_buses.rst:22
msgid ""
"Godot's sound interface is designed to meet the expectations of sound design "
"professionals. To this end, it primarily uses the decibel scale."
msgstr ""

#: ../../docs/tutorials/audio/audio_buses.rst:25
msgid "For those unfamiliar with it, it can be explained with a few facts:"
msgstr ""

#: ../../docs/tutorials/audio/audio_buses.rst:27
msgid ""
"The decibel (dB) scale is a relative scale. It represents the ratio of sound "
"power by using 20 times the base 10 logarithm of the ratio (20 × log\\ :sub:"
"`10`\\ (P/P\\ :sub:`0`\\ ))."
msgstr ""

#: ../../docs/tutorials/audio/audio_buses.rst:30
msgid ""
"For every 6 dB, sound amplitude doubles or halves. 12 dB represents a factor "
"of 4, 18 dB a factor of 8, 20 dB a factor of 10, 40 dB a factor of 100, etc."
msgstr ""

#: ../../docs/tutorials/audio/audio_buses.rst:32
msgid ""
"Since the scale is logarithmic, true zero (no audio) can't be represented."
msgstr ""

#: ../../docs/tutorials/audio/audio_buses.rst:33
msgid ""
"0 dB is the maximum amplitude possible in a digital audio system. This limit "
"is not the human limit, but a limit from the sound hardware. Audio with "
"amplitudes that are too high to be represented properly below 0 dB create a "
"kind of distortion called *clipping*."
msgstr ""

#: ../../docs/tutorials/audio/audio_buses.rst:37
msgid ""
"To avoid clipping, your sound mix should be arranged so that the output of "
"the *master bus* (more on that later) never exceeds 0 dB."
msgstr ""

#: ../../docs/tutorials/audio/audio_buses.rst:39
msgid ""
"Every 6 dB below the 0 dB limit, sound energy is *halved*. It means the "
"sound volume at -6 dB is half as loud as 0dB. -12 dB is half as loud as -6 "
"dB and so on."
msgstr ""

#: ../../docs/tutorials/audio/audio_buses.rst:42
msgid ""
"When working with decibels, sound is considered no longer audible between "
"-60 dB and -80 dB. This makes your working range generally between -60 dB "
"and 0 dB."
msgstr ""

#: ../../docs/tutorials/audio/audio_buses.rst:46
msgid ""
"This can take a bit getting used to, but it's friendlier in the end and will "
"allow you to communicate better with audio professionals."
msgstr ""

#: ../../docs/tutorials/audio/audio_buses.rst:52
msgid "Audio buses can be found in the bottom panel of the Godot editor:"
msgstr ""

#: ../../docs/tutorials/audio/audio_buses.rst:56
msgid ""
"An *audio bus* (also called an *audio channel*) can be considered a place "
"that audio is channeled through on the way to playback through a device's "
"speakers. Audio data can be *modified* and *re-routed* by an audio bus. An "
"audio bus has a VU meter (the bars that light up when sound is played) which "
"indicates the amplitude of the signal passing through."
msgstr ""

#: ../../docs/tutorials/audio/audio_buses.rst:62
msgid ""
"The leftmost bus is the *master bus*. This bus outputs the mix to your "
"speakers so, as mentioned in the *Decibel scale* section above, make sure "
"that your mix level doesn't reach 0 dB in this bus. The rest of the audio "
"buses can be flexibly routed. After modifying the sound, they send it to "
"another bus to the left. The destination bus can be specified for each of "
"the non-master audio buses. Routing always passes audio from buses on the "
"right to buses further to the left. This avoids infinite routing loops."
msgstr ""

#: ../../docs/tutorials/audio/audio_buses.rst:72
msgid ""
"In the above image, the output of *Bus 2* has been routed to the *Master* "
"bus."
msgstr ""

#: ../../docs/tutorials/audio/audio_buses.rst:75
msgid "Playback of audio through a bus"
msgstr ""

#: ../../docs/tutorials/audio/audio_buses.rst:77
msgid ""
"To test passing audio to a bus, create an AudioStreamPlayer node, load an "
"AudioStream and select a target bus for playback:"
msgstr ""

#: ../../docs/tutorials/audio/audio_buses.rst:82
msgid "Finally, toggle the **Playing** property to **On** and sound will flow."
msgstr ""

#: ../../docs/tutorials/audio/audio_buses.rst:86
msgid ""
"You may also be interested in reading about :ref:`doc_audio_streams` now."
msgstr ""

#: ../../docs/tutorials/audio/audio_buses.rst:89
msgid "Adding effects"
msgstr ""

#: ../../docs/tutorials/audio/audio_buses.rst:91
msgid ""
"Audio buses can contain all sorts of effects. These effects modify the sound "
"in one way or another and are applied in order."
msgstr ""

#: ../../docs/tutorials/audio/audio_buses.rst:96
#, fuzzy
msgid "For information on what each effect does, see :ref:`doc_audio_effects`."
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/audio/audio_buses.rst:99
msgid "Automatic bus disabling"
msgstr ""

#: ../../docs/tutorials/audio/audio_buses.rst:101
msgid ""
"There is no need to disable buses manually when not in use. Godot detects "
"that the bus has been silent for a few seconds and disables it (including "
"all effects)."
msgstr ""

#: ../../docs/tutorials/audio/audio_buses.rst:107
msgid "Disabled buses have a blue VU meter instead of a red-green one."
msgstr ""

#: ../../docs/tutorials/audio/audio_buses.rst:110
msgid "Bus rearrangement"
msgstr ""

#: ../../docs/tutorials/audio/audio_buses.rst:112
msgid ""
"Stream Players use bus names to identify a bus, which allows adding, "
"removing and moving buses around while the reference to them is kept. "
"However, if a bus is renamed, the reference will be lost and the Stream "
"Player will output to Master. This system was chosen because rearranging "
"buses is a more common process than renaming them."
msgstr ""

#: ../../docs/tutorials/audio/audio_buses.rst:119
msgid "Default bus layout"
msgstr ""

#: ../../docs/tutorials/audio/audio_buses.rst:121
msgid ""
"The default bus layout is automatically saved to the ``res://"
"default_bus_layout.tres`` file. Custom bus arrangements can be saved and "
"loaded from disk."
msgstr ""

#: ../../docs/tutorials/audio/audio_effects.rst:6
msgid "Audio effects"
msgstr ""

#: ../../docs/tutorials/audio/audio_effects.rst:8
msgid ""
"Godot includes several audio effects that can be added to an audio bus to "
"alter every sound file that goes through that bus."
msgstr ""

#: ../../docs/tutorials/audio/audio_effects.rst:13
msgid ""
"Try them all out to get a sense of how they alter sound. Here follows a "
"short description of the available effects:"
msgstr ""

#: ../../docs/tutorials/audio/audio_effects.rst:17
msgid "Amplify"
msgstr ""

#: ../../docs/tutorials/audio/audio_effects.rst:19
msgid ""
"Amplify changes the volume of the signal. Some care needs to be taken, "
"though: setting the level too high can make the sound digitally clip, which "
"can produce unpleasant crackles and pops."
msgstr ""

#: ../../docs/tutorials/audio/audio_effects.rst:24
msgid "BandLimit and BandPass"
msgstr ""

#: ../../docs/tutorials/audio/audio_effects.rst:26
msgid ""
"These are resonant filters which block frequencies around the *Cutoff* "
"point. BandPass can be used to simulate sound passing through an old "
"telephone line or megaphone. Modulating the BandPass frequency can simulate "
"the sound of a wah-wah guitar pedal, think of the guitar in Jimi Hendrix's "
"*Voodoo Child (Slight Return)*."
msgstr ""

#: ../../docs/tutorials/audio/audio_effects.rst:33
#: ../../docs/tutorials/rendering/viewports.rst:134
msgid "Capture"
msgstr "Ulovi"

#: ../../docs/tutorials/audio/audio_effects.rst:35
msgid ""
"The Capture effect copies the audio frames of the audio bus that it is on "
"into an internal buffer. This can be used to capture data from the "
"microphone or to transmit audio over the network in real-time."
msgstr ""

#: ../../docs/tutorials/audio/audio_effects.rst:40
msgid "Chorus"
msgstr ""

#: ../../docs/tutorials/audio/audio_effects.rst:42
msgid ""
"As the name of the effect implies, the Chorus effect makes a single audio "
"sample sound like an entire chorus. It does this by duplicating a signal and "
"very slightly altering the timing and pitch of each duplicate, and varying "
"that over time via an LFO (low frequency oscillator). The duplicate(s) are "
"then mixed back together with the original signal, producing a lush, wide, "
"and large sound. Although chorus is traditionally used for voices, it can be "
"desirable with almost any type of sound."
msgstr ""

#: ../../docs/tutorials/audio/audio_effects.rst:51
msgid "Compressor"
msgstr ""

#: ../../docs/tutorials/audio/audio_effects.rst:53
msgid ""
"A dynamic range compressor automatically attenuates (ducks) the level of the "
"incoming signal when its amplitude exceeds a certain threshold. The level of "
"attenuation applied is proportional to how far the incoming audio exceeds "
"the threshold. The compressor's Ratio parameter controls the degree of "
"attenuation. One of the main uses of a compressor is to reduce the dynamic "
"range of signals with very loud and quiet parts. Reducing the dynamic range "
"of a signal can make it fit more comfortably in a mix."
msgstr ""

#: ../../docs/tutorials/audio/audio_effects.rst:61
msgid "The compressor has many uses. For example:"
msgstr ""

#: ../../docs/tutorials/audio/audio_effects.rst:63
msgid ""
"It can be used in the Master bus to compress the whole output prior to being "
"hit by a limiter, making the effect of the limiter much more subtle."
msgstr ""

#: ../../docs/tutorials/audio/audio_effects.rst:64
msgid ""
"It can be used in voice channels to ensure they sound as even as possible."
msgstr ""

#: ../../docs/tutorials/audio/audio_effects.rst:65
msgid ""
"It can be *sidechained* by another sound source. This means it can reduce "
"the sound level of one signal using the level of another audio bus for "
"threshold detection. This technique is very common in video game mixing to "
"\"duck\" the level of music or sound effects when in-game or multiplayer "
"voices need to be fully audible."
msgstr ""

#: ../../docs/tutorials/audio/audio_effects.rst:69
msgid ""
"It can accentuate transients by using a slower attack. This can make sound "
"effects more punchy."
msgstr ""

#: ../../docs/tutorials/audio/audio_effects.rst:74
msgid ""
"If your goal is to prevent a signal from exceeding a given amplitude "
"altogether, rather than to reduce the dynamic range of the signal, a :ref:"
"`limiter <doc_audio_buses_limiter>` is likely a better choice than a "
"compressor for this purpose. However, applying compression before a limiter "
"is still good practice."
msgstr ""

#: ../../docs/tutorials/audio/audio_effects.rst:81
msgid "Delay"
msgstr ""

#: ../../docs/tutorials/audio/audio_effects.rst:83
msgid ""
"Digital delay essentially duplicates a signal and repeats it at a specified "
"speed with a volume level that decays for each repeat. Delay is great for "
"simulating the acoustic space of a canyon or large room, where sound bounces "
"have a lot of *delay* between their repeats. This is in contrast to reverb, "
"which has a more natural and blurred sound to it. Using this in conjunction "
"with reverb can create very natural sounding environments!"
msgstr ""

#: ../../docs/tutorials/audio/audio_effects.rst:91
msgid "Distortion"
msgstr ""

#: ../../docs/tutorials/audio/audio_effects.rst:93
msgid "Makes the sound distorted. Godot offers several types of distortion:"
msgstr ""

#: ../../docs/tutorials/audio/audio_effects.rst:95
msgid ""
"*Overdrive* sounds like a guitar distortion pedal or megaphone. Sounds "
"distorted with this sound like they're coming through a low-quality speaker "
"or device."
msgstr ""

#: ../../docs/tutorials/audio/audio_effects.rst:97
msgid "*Tan* sounds like another interesting flavor of overdrive."
msgstr ""

#: ../../docs/tutorials/audio/audio_effects.rst:98
msgid ""
"*Bit crushing* clamps the amplitude of the signal, making it sound flat and "
"crunchy."
msgstr ""

#: ../../docs/tutorials/audio/audio_effects.rst:100
msgid ""
"All three types of distortion can add higher frequency sounds to an original "
"sound, making it stand out better in a mix."
msgstr ""

#: ../../docs/tutorials/audio/audio_effects.rst:103
msgid "EQ"
msgstr ""

#: ../../docs/tutorials/audio/audio_effects.rst:105
msgid ""
"EQ is what all other equalizers inherit from. It can be extended with Custom "
"scripts to create an equalizer with a custom number of bands."
msgstr ""

#: ../../docs/tutorials/audio/audio_effects.rst:109
msgid "EQ6, EQ10, EQ21"
msgstr ""

#: ../../docs/tutorials/audio/audio_effects.rst:111
msgid ""
"Godot provides three equalizers with different numbers of bands, which are "
"represented in the title (6, 10, and 21 bands, respectively). An equalizer "
"on the Master bus can be useful for cutting low and high frequencies that "
"the device's speakers can't reproduce well. For example, phone or tablet "
"speakers usually don't reproduce low frequency sounds well, and could make a "
"limiter or compressor attenuate sounds that aren't even audible to the user "
"anyway."
msgstr ""

#: ../../docs/tutorials/audio/audio_effects.rst:119
msgid ""
"Note: The equalizer effect can be disabled when headphones are plugged in, "
"giving the user the best of both worlds."
msgstr ""

#: ../../docs/tutorials/audio/audio_effects.rst:124
msgid ""
"Filter is what all other filters inherit from and should not be used "
"directly."
msgstr ""

#: ../../docs/tutorials/audio/audio_effects.rst:127
msgid "HighPassFilter"
msgstr ""

#: ../../docs/tutorials/audio/audio_effects.rst:129
msgid ""
"Cuts frequencies below a specific *Cutoff* frequency. HighPassFilter is used "
"to reduce the bass content of a signal."
msgstr ""

#: ../../docs/tutorials/audio/audio_effects.rst:134
msgid "HighShelfFilter"
msgstr ""

#: ../../docs/tutorials/audio/audio_effects.rst:136
msgid "Reduces all frequencies above a specific *Cutoff* frequency."
msgstr ""

#: ../../docs/tutorials/audio/audio_effects.rst:141
msgid "Limiter"
msgstr ""

#: ../../docs/tutorials/audio/audio_effects.rst:143
msgid ""
"A limiter is similar to a compressor, but it's less flexible and designed to "
"prevent a signal's amplitude exceeding a given dB threshold. Adding a "
"limiter to the final point of the Master bus is good practice, as it offers "
"an easy safeguard against clipping."
msgstr ""

#: ../../docs/tutorials/audio/audio_effects.rst:148
msgid "LowPassFilter"
msgstr ""

#: ../../docs/tutorials/audio/audio_effects.rst:150
msgid ""
"Cuts frequencies above a specific *Cutoff* frequency and can also resonate "
"(boost frequencies close to the *Cutoff* frequency). Low pass filters can be "
"used to simulate \"muffled\" sound. For instance, underwater sounds, sounds "
"blocked by walls, or distant sounds."
msgstr ""

#: ../../docs/tutorials/audio/audio_effects.rst:156
msgid "LowShelfFilter"
msgstr ""

#: ../../docs/tutorials/audio/audio_effects.rst:158
msgid "Reduces all frequencies below a specific *Cutoff* frequency."
msgstr ""

#: ../../docs/tutorials/audio/audio_effects.rst:161
msgid "NotchFilter"
msgstr ""

#: ../../docs/tutorials/audio/audio_effects.rst:163
msgid ""
"The opposite of the BandPassFilter, it removes a band of sound from the "
"frequency spectrum at a given *Cutoff* frequency."
msgstr ""

#: ../../docs/tutorials/audio/audio_effects.rst:167
msgid "Panner"
msgstr ""

#: ../../docs/tutorials/audio/audio_effects.rst:169
msgid ""
"The Panner allows the stereo balance of a signal to be adjusted between the "
"left and right channels. Headphones are recommended when configuring in this "
"effect."
msgstr ""

#: ../../docs/tutorials/audio/audio_effects.rst:173
msgid "Phaser"
msgstr ""

#: ../../docs/tutorials/audio/audio_effects.rst:175
msgid ""
"This effect is formed by de-phasing two duplicates of the same sound so they "
"cancel each other out in an interesting way. Phaser produces a pleasant "
"whooshing sound that moves back and forth through the audio spectrum, and "
"can be a great way to create sci-fi effects or Darth Vader-like voices."
msgstr ""

#: ../../docs/tutorials/audio/audio_effects.rst:182
msgid "PitchShift"
msgstr ""

#: ../../docs/tutorials/audio/audio_effects.rst:184
msgid ""
"This effect allows the adjustment of the signal's pitch independently of its "
"speed. All frequencies can be increased/decreased with minimal effect on "
"transients. PitchShift can be useful to create unusually high or deep "
"voices. Do note that altering pitch can sound unnatural when pushed outside "
"of a narrow window."
msgstr ""

#: ../../docs/tutorials/audio/audio_effects.rst:191
msgid "Record"
msgstr ""

#: ../../docs/tutorials/audio/audio_effects.rst:193
msgid "The Record effect allows the user to record sound from a microphone."
msgstr ""

#: ../../docs/tutorials/audio/audio_effects.rst:196
msgid "Reverb"
msgstr ""

#: ../../docs/tutorials/audio/audio_effects.rst:198
msgid ""
"Reverb simulates rooms of different sizes. It has adjustable parameters that "
"can be tweaked to obtain the sound of a specific room. Reverb is commonly "
"outputted from :ref:`Area3Ds <class_Area3D>` (see :ref:`Reverb buses "
"<doc_audio_streams_reverb_buses>`), or to apply a \"chamber\" feel to all "
"sounds."
msgstr ""

#: ../../docs/tutorials/audio/audio_effects.rst:205
msgid "SpectrumAnalyzer"
msgstr ""

#: ../../docs/tutorials/audio/audio_effects.rst:207
msgid ""
"This effect doesn't alter audio, instead, you add this effect to buses you "
"want a spectrum analysis of. This would typically be used for audio "
"visualization. Visualizing voices can be a great way to draw attention to "
"them without just increasing their volume. A demo project using this can be "
"found `here <https://github.com/godotengine/godot-demo-projects/tree/master/"
"audio/spectrum>`__."
msgstr ""

#: ../../docs/tutorials/audio/audio_effects.rst:214
msgid "StereoEnhance"
msgstr ""

#: ../../docs/tutorials/audio/audio_effects.rst:216
msgid "This effect uses a few algorithms to enhance a signal's stereo width."
msgstr ""

#: ../../docs/tutorials/audio/audio_streams.rst:6
msgid "Audio streams"
msgstr ""

#: ../../docs/tutorials/audio/audio_streams.rst:11
msgid ""
"As you might have already read in :ref:`doc_audio_buses`, sound is sent to "
"each bus via an AudioStreamPlayer node. There are different kinds of "
"AudioStreamPlayers. Each one loads an AudioStream and plays it back."
msgstr ""

#: ../../docs/tutorials/audio/audio_streams.rst:16
msgid "AudioStream"
msgstr ""

#: ../../docs/tutorials/audio/audio_streams.rst:18
msgid ""
"An audio stream is an abstract object that emits sound. The sound can come "
"from many places, but is most commonly loaded from the filesystem. Audio "
"files can be loaded as AudioStreams and placed inside an AudioStreamPlayer. "
"You can find information on supported formats and differences in :ref:"
"`doc_importing_audio_samples`."
msgstr ""

#: ../../docs/tutorials/audio/audio_streams.rst:23
msgid ""
"There are other types of AudioStreams, such as AudioStreamRandomPitch. This "
"one makes a random adjustment to the sound's pitch every time it's played "
"back. This can be helpful for adding variation to sounds that are played "
"back often."
msgstr ""

#: ../../docs/tutorials/audio/audio_streams.rst:29
msgid "AudioStreamPlayer"
msgstr ""

#: ../../docs/tutorials/audio/audio_streams.rst:33
msgid ""
"This is the standard, non-positional stream player. It can play to any bus. "
"In 5.1 sound setups, it can send audio to stereo mix or front speakers."
msgstr ""

#: ../../docs/tutorials/audio/audio_streams.rst:37
msgid "AudioStreamPlayer2D"
msgstr ""

#: ../../docs/tutorials/audio/audio_streams.rst:41
msgid ""
"This is a variant of AudioStreamPlayer, but emits sound in a 2D positional "
"environment. When close to the left of the screen, the panning will go left. "
"When close to the right side, it will go right."
msgstr ""

#: ../../docs/tutorials/audio/audio_streams.rst:47
msgid ""
"Area2Ds can be used to divert sound from any AudioStreamPlayer2Ds they "
"contain to specific buses. This makes it possible to create buses with "
"different reverb or sound qualities to handle action happening in a "
"particular parts of your game world."
msgstr ""

#: ../../docs/tutorials/audio/audio_streams.rst:55
msgid "AudioStreamPlayer3D"
msgstr ""

#: ../../docs/tutorials/audio/audio_streams.rst:59
msgid ""
"This is a variant of AudioStreamPlayer, but emits sound in a 3D positional "
"environment. Depending on the location of the player relative to the screen, "
"it can position sound in stereo, 5.1 or 7.1 depending on the chosen audio "
"setup."
msgstr ""

#: ../../docs/tutorials/audio/audio_streams.rst:63
msgid ""
"Similar to AudioStreamPlayer2D, an Area can divert the sound to an audio bus."
msgstr ""

#: ../../docs/tutorials/audio/audio_streams.rst:67
msgid ""
"Unlike for 2D, the 3D version of AudioStreamPlayer has a few more advanced "
"options:"
msgstr ""

#: ../../docs/tutorials/audio/audio_streams.rst:72
msgid "Reverb buses"
msgstr ""

#: ../../docs/tutorials/audio/audio_streams.rst:74
msgid ""
"Godot allows for 3D audio streams that enter a specific Area node to send "
"dry and wet audio to separate buses. This is useful when you have several "
"reverb configurations for different types of rooms. This is done by enabling "
"this type of reverb in the **Reverb Bus** section of the Area's properties:"
msgstr ""

#: ../../docs/tutorials/audio/audio_streams.rst:81
msgid ""
"At the same time, a special bus layout is created where each area receives "
"the reverb info from each area. A Reverb effect needs to be created and "
"configured in each reverb bus to complete the setup for the desired effect:"
msgstr ""

#: ../../docs/tutorials/audio/audio_streams.rst:87
msgid ""
"The Area's **Reverb Bus** section also has a parameter named **Uniformity**. "
"Some types of rooms bounce sounds more than others (like a warehouse), so "
"reverberation can be heard almost uniformly across the room even though the "
"source may be far away. Playing around with this parameter can simulate that "
"effect."
msgstr ""

#: ../../docs/tutorials/audio/audio_streams.rst:94
msgid "Doppler"
msgstr ""

#: ../../docs/tutorials/audio/audio_streams.rst:96
msgid ""
"When the relative velocity between an emitter and listener changes, this is "
"perceived as an increase or decrease in the pitch of the emitted sound. "
"Godot can track velocity changes in the AudioStreamPlayer3D and Camera "
"nodes. Both nodes have this property, which must be enabled manually:"
msgstr ""

#: ../../docs/tutorials/audio/audio_streams.rst:103
msgid ""
"Enable it by setting it depending on how objects will be moved: use **Idle** "
"for objects moved using ``_process``, or **Physics** for objects moved using "
"``_physics_process``. The tracking will happen automatically."
msgstr ""

#: ../../docs/tutorials/audio/sync_with_audio.rst:6
msgid "Sync the gameplay with audio and music"
msgstr ""

#: ../../docs/tutorials/audio/sync_with_audio.rst:11
msgid ""
"In any application or game, sound and music playback will have a slight "
"delay. For games, this delay is often so small that it is negligible. Sound "
"effects will come out a few milliseconds after any play() function is "
"called. For music this does not matter as in most games it does not interact "
"with the gameplay."
msgstr ""

#: ../../docs/tutorials/audio/sync_with_audio.rst:13
msgid ""
"Still, for some games (mainly, rhythm games), it may be required to "
"synchronize player actions with something happening in a song (usually in "
"sync with the BPM). For this, having more precise timing information for an "
"exact playback position is useful."
msgstr ""

#: ../../docs/tutorials/audio/sync_with_audio.rst:15
msgid ""
"Achieving very low playback timing precision is difficult. This is because "
"many factors are at play during audio playback:"
msgstr ""

#: ../../docs/tutorials/audio/sync_with_audio.rst:17
msgid ""
"Audio is mixed in chunks (not continuously), depending on the size of audio "
"buffers used (check latency in project settings)."
msgstr ""

#: ../../docs/tutorials/audio/sync_with_audio.rst:18
msgid "Mixed chunks of audio are not played immediately."
msgstr ""

#: ../../docs/tutorials/audio/sync_with_audio.rst:19
msgid "Graphics APIs display two or three frames late."
msgstr ""

#: ../../docs/tutorials/audio/sync_with_audio.rst:20
msgid "When playing on TVs, some delay may be added due to image processing."
msgstr ""

#: ../../docs/tutorials/audio/sync_with_audio.rst:22
msgid ""
"The most common way to reduce latency is to shrink the audio buffers (again, "
"by editing the latency setting in the project settings). The problem is that "
"when latency is too small, sound mixing will require considerably more CPU. "
"This increases the risk of skipping (a crack in sound because a mix callback "
"was lost)."
msgstr ""

#: ../../docs/tutorials/audio/sync_with_audio.rst:24
msgid ""
"This is a common tradeoff, so Godot ships with sensible defaults that should "
"not need to be altered."
msgstr ""

#: ../../docs/tutorials/audio/sync_with_audio.rst:26
msgid ""
"The problem, in the end, is not this slight delay but synchronizing graphics "
"and audio for games that require it. Beginning with Godot 3.2, some helpers "
"were added to obtain more precise playback timing."
msgstr ""

#: ../../docs/tutorials/audio/sync_with_audio.rst:29
msgid "Using the system clock to sync"
msgstr ""

#: ../../docs/tutorials/audio/sync_with_audio.rst:31
msgid ""
"As mentioned before, If you call :ref:`AudioStreamPlayer."
"play()<class_AudioStreamPlayer_method_play>`, sound will not begin "
"immediately, but when the audio thread processes the next chunk."
msgstr ""

#: ../../docs/tutorials/audio/sync_with_audio.rst:33
msgid ""
"This delay can't be avoided but it can be estimated by calling :ref:"
"`AudioServer."
"get_time_to_next_mix()<class_AudioServer_method_get_time_to_next_mix>`."
msgstr ""

#: ../../docs/tutorials/audio/sync_with_audio.rst:35
msgid ""
"The output latency (what happens after the mix) can also be estimated by "
"calling :ref:`AudioServer."
"get_output_latency()<class_AudioServer_method_get_output_latency>`."
msgstr ""

#: ../../docs/tutorials/audio/sync_with_audio.rst:37
msgid ""
"Add these two and it's possible to guess almost exactly when sound or music "
"will begin playing in the speakers during *_process()*:"
msgstr ""

#: ../../docs/tutorials/audio/sync_with_audio.rst:81
msgid ""
"In the long run, though, as the sound hardware clock is never exactly in "
"sync with the system clock, the timing information will slowly drift away."
msgstr ""

#: ../../docs/tutorials/audio/sync_with_audio.rst:83
msgid ""
"For a rhythm game where a song begins and ends after a few minutes, this "
"approach is fine (and it's the recommended approach). For a game where "
"playback can last a much longer time, the game will eventually go out of "
"sync and a different approach is needed."
msgstr ""

#: ../../docs/tutorials/audio/sync_with_audio.rst:86
msgid "Using the sound hardware clock to sync"
msgstr ""

#: ../../docs/tutorials/audio/sync_with_audio.rst:88
msgid ""
"Using :ref:`AudioStreamPlayer."
"get_playback_position()<class_AudioStreamPlayer_method_get_playback_position>` "
"to obtain the current position for the song sounds ideal, but it's not that "
"useful as-is. This value will increment in chunks (every time the audio "
"callback mixed a block of sound), so many calls can return the same value. "
"Added to this, the value will be out of sync with the speakers too because "
"of the previously mentioned reasons."
msgstr ""

#: ../../docs/tutorials/audio/sync_with_audio.rst:90
msgid ""
"To compensate for the \"chunked\" output, there is a function that can "
"help: :ref:`AudioServer."
"get_time_since_last_mix()<class_AudioServer_method_get_time_since_last_mix>`."
msgstr ""

#: ../../docs/tutorials/audio/sync_with_audio.rst:93
msgid ""
"Adding the return value from this function to *get_playback_position()* "
"increases precision:"
msgstr ""

#: ../../docs/tutorials/audio/sync_with_audio.rst:105
msgid ""
"To increase precision, subtract the latency information (how much it takes "
"for the audio to be heard after it was mixed):"
msgstr ""

#: ../../docs/tutorials/audio/sync_with_audio.rst:116
msgid ""
"The result may be a bit jittery due how multiple threads work. Just check "
"that the value is not less than in the previous frame (discard it if so). "
"This is also a less precise approach than the one before, but it will work "
"for songs of any length, or synchronizing anything (sound effects, as an "
"example) to music."
msgstr ""

#: ../../docs/tutorials/audio/sync_with_audio.rst:118
msgid "Here is the same code as before using this approach:"
msgstr ""

#: ../../docs/tutorials/audio/recording_with_microphone.rst:6
msgid "Recording with microphone"
msgstr ""

#: ../../docs/tutorials/audio/recording_with_microphone.rst:8
msgid ""
"Godot supports in-game audio recording for Windows, macOS, Linux, Android "
"and iOS."
msgstr ""

#: ../../docs/tutorials/audio/recording_with_microphone.rst:11
msgid ""
"A simple demo is included in the official demo projects and will be used as "
"support for this tutorial: `<https://github.com/godotengine/godot-demo-"
"projects/tree/master/audio/mic_record>`_."
msgstr ""

#: ../../docs/tutorials/audio/recording_with_microphone.rst:15
msgid ""
"You will need to enable audio input in the project settings, or you'll just "
"get empty audio files."
msgstr ""

#: ../../docs/tutorials/audio/recording_with_microphone.rst:18
msgid "The structure of the demo"
msgstr ""

#: ../../docs/tutorials/audio/recording_with_microphone.rst:20
msgid ""
"The demo consists of a single scene. This scene includes two major parts: "
"the GUI and the audio."
msgstr ""

#: ../../docs/tutorials/audio/recording_with_microphone.rst:23
msgid ""
"We will focus on the audio part. In this demo, a bus named ``Record`` with "
"the effect ``Record`` is created to handle the audio recording. An "
"``AudioStreamPlayer`` named ``AudioStreamRecord`` is used for recording."
msgstr ""

#: ../../docs/tutorials/audio/recording_with_microphone.rst:59
msgid ""
"The audio recording is handled by the :ref:`class_AudioEffectRecord` "
"resource which has three methods: :ref:`get_recording() "
"<class_AudioEffectRecord_method_get_recording>`, :ref:`is_recording_active() "
"<class_AudioEffectRecord_method_is_recording_active>`, and :ref:"
"`set_recording_active() "
"<class_AudioEffectRecord_method_set_recording_active>`."
msgstr ""

#: ../../docs/tutorials/audio/recording_with_microphone.rst:106
msgid ""
"At the start of the demo, the recording effect is not active. When the user "
"presses the ``RecordButton``, the effect is enabled with "
"``set_recording_active(true)``."
msgstr ""

#: ../../docs/tutorials/audio/recording_with_microphone.rst:110
msgid ""
"On the next button press, as ``effect.is_recording_active()`` is ``true``, "
"the recorded stream can be stored into the ``recording`` variable by calling "
"``effect.get_recording()``."
msgstr ""

#: ../../docs/tutorials/audio/recording_with_microphone.rst:142
msgid ""
"To playback the recording, you assign the recording as the stream of the "
"``AudioStreamPlayer`` and call ``play()``."
msgstr ""

#: ../../docs/tutorials/audio/recording_with_microphone.rst:162
msgid ""
"To save the recording, you call ``save_to_wav()`` with the path to a file. "
"In this demo, the path is defined by the user via a ``LineEdit`` input box."
msgstr ""

#: ../../docs/tutorials/audio/text_to_speech.rst:4
msgid "Text to speech"
msgstr ""

#: ../../docs/tutorials/audio/text_to_speech.rst:7
msgid "Basic Usage"
msgstr ""

#: ../../docs/tutorials/audio/text_to_speech.rst:9
msgid "Basic usage of text-to-speech involves the following one-time steps:"
msgstr ""

#: ../../docs/tutorials/audio/text_to_speech.rst:11
msgid "Enable TTS in the Godot editor for your project"
msgstr ""

#: ../../docs/tutorials/audio/text_to_speech.rst:12
msgid "Query the system for a list of usable voices"
msgstr ""

#: ../../docs/tutorials/audio/text_to_speech.rst:13
msgid "Store the ID of the voice you want to use"
msgstr ""

#: ../../docs/tutorials/audio/text_to_speech.rst:15
msgid ""
"By default, the Godot project-level setting for text-to-speech is disabled, "
"to avoid unnecessary overhead. To enable it:"
msgstr ""

#: ../../docs/tutorials/audio/text_to_speech.rst:17
#, fuzzy
msgid "Go to **Project > Project Settings**"
msgstr "Uvod / Početak"

#: ../../docs/tutorials/audio/text_to_speech.rst:18
msgid "Make sure the **Advanced Settings** toggle is enabled"
msgstr ""

#: ../../docs/tutorials/audio/text_to_speech.rst:19
msgid "Click on **Audio > General**"
msgstr ""

#: ../../docs/tutorials/audio/text_to_speech.rst:20
msgid "Ensure the **Text to Speech** option is checked"
msgstr ""

#: ../../docs/tutorials/audio/text_to_speech.rst:21
msgid "Restart Godot if prompted to do so."
msgstr ""

#: ../../docs/tutorials/audio/text_to_speech.rst:23
msgid ""
"Text-to-speech uses a specific voice. Depending on the user's system, they "
"might have multiple voices installed. Once you have the voice ID, you can "
"use it to speak some text:"
msgstr ""

#: ../../docs/tutorials/audio/text_to_speech.rst:68
msgid "Requirements for functionality"
msgstr ""

#: ../../docs/tutorials/audio/text_to_speech.rst:70
msgid ""
"Godot includes text-to-speech functionality. You can find these under the :"
"ref:`DisplayServer class <class_DisplayServer>`."
msgstr ""

#: ../../docs/tutorials/audio/text_to_speech.rst:72
msgid ""
"Godot depends on system libraries for text-to-speech functionality. These "
"libraries are installed by default on Windows and macOS, but not on all "
"Linux distributions. If they are not present, text-to-speech functionality "
"will not work. Specifically, the ``tts_get_voices()`` method will return an "
"empty list, indicating that there are no usable voices."
msgstr ""

#: ../../docs/tutorials/audio/text_to_speech.rst:74
msgid ""
"Both Godot users on Linux and end-users on Linux running Godot games need to "
"ensure that their system includes the system libraries for text-to-speech to "
"work. Please consult the table below or your own distribution's "
"documentation to determine what libraries you need to install."
msgstr ""

#: ../../docs/tutorials/audio/text_to_speech.rst:77
#: ../../docs/contributing/development/compiling/compiling_for_linuxbsd.rst:51
msgid "Distro-specific one-liners"
msgstr ""

#: ../../docs/tutorials/audio/text_to_speech.rst:79
#: ../../docs/contributing/development/compiling/compiling_for_windows.rst:196
msgid "**Arch Linux**"
msgstr ""

#: ../../docs/tutorials/audio/text_to_speech.rst:87
msgid ""
"If you get the error `Invalid get index '0' (on base: 'PackedStringArray').` "
"for the line `var voice_id = voices[0]`, check if there are any items in "
"`voices`. If not:"
msgstr ""

#: ../../docs/tutorials/audio/text_to_speech.rst:89
msgid "All users: make sure you enabled **Text to Speech** in project settings"
msgstr ""

#: ../../docs/tutorials/audio/text_to_speech.rst:90
msgid ""
"Linux users: ensure you installed the system-specific libraries for text to "
"speech"
msgstr ""

#: ../../docs/tutorials/audio/text_to_speech.rst:95
msgid ""
"The best practices for text-to-speech, in terms of the ideal player "
"experience for blind players, is to send output to the player's screen "
"reader. This preserves the choice of language, speed, pitch, etc. that the "
"user set, as well as allows advanced features like allowing players to "
"scroll backward and forward through text. As of now, Godot doesn't provide "
"this level of integration."
msgstr ""

#: ../../docs/tutorials/audio/text_to_speech.rst:97
msgid ""
"With the current state of the Godot text-to-speech APIs, best practices "
"include:"
msgstr ""

#: ../../docs/tutorials/audio/text_to_speech.rst:99
msgid ""
"Develop the game with text-to-speech enabled, and ensure that everything "
"sounds correct"
msgstr ""

#: ../../docs/tutorials/audio/text_to_speech.rst:100
msgid ""
"Allow players to control which voice to use, and save/persist that selection "
"across game sessions"
msgstr ""

#: ../../docs/tutorials/audio/text_to_speech.rst:101
msgid ""
"Allow players to control the speech rate, and save/persist that selection "
"across game sessions"
msgstr ""

#: ../../docs/tutorials/audio/text_to_speech.rst:103
msgid ""
"This provides your blind players with the most flexibility and comfort "
"available when not using a screen reader, and minimizes the chance of "
"frustrating and alienating them."
msgstr ""

#: ../../docs/tutorials/audio/text_to_speech.rst:106
msgid "Caveats and Other Information"
msgstr ""

#: ../../docs/tutorials/audio/text_to_speech.rst:108
msgid ""
"Expect delays when you call `tts_speak` and `tts_stop`. The actual delay "
"time varies depending on both the OS and on your machine's specifications. "
"This is especially critical on Android and Web, where some of the voices "
"depend on web services, and the actual time to playback depends on server "
"load, network latency, and other factors."
msgstr ""

#: ../../docs/tutorials/audio/text_to_speech.rst:109
msgid ""
"Non-English text works if the correct voices are installed and used. On "
"Windows, you can consult the instructions in `this article`_ to enable "
"additional language voices on Windows."
msgstr ""

#: ../../docs/tutorials/audio/text_to_speech.rst:110
msgid ""
"Non-ASCII characters, such as umlaut, are pronounced correctly if you select "
"the correct voice."
msgstr ""

#: ../../docs/tutorials/audio/text_to_speech.rst:111
msgid ""
"Blind players use a number of screen readers, including JAWS, NVDA, "
"VoiceOver, Narrator, and more."
msgstr ""

#: ../../docs/tutorials/audio/text_to_speech.rst:112
msgid ""
"Windows text-to-speech APIs generally perform better than their equivalents "
"on other systems (e.g. `tts_stop` followed by `tts_speak` immediately speaks "
"the new message)."
msgstr ""

#: ../../docs/tutorials/export/exporting_projects.rst:6
msgid "Exporting projects"
msgstr ""

#: ../../docs/tutorials/export/exporting_projects.rst:11
msgid "Why export?"
msgstr ""

#: ../../docs/tutorials/export/exporting_projects.rst:13
msgid ""
"Originally, Godot did not have any means to export projects. The developers "
"would compile the proper binaries and build the packages for each platform "
"manually."
msgstr ""

#: ../../docs/tutorials/export/exporting_projects.rst:17
msgid ""
"When more developers (and even non-programmers) started using it, and when "
"our company started taking more projects at the same time, it became evident "
"that this was a bottleneck."
msgstr ""

#: ../../docs/tutorials/export/exporting_projects.rst:22
msgid "On PC"
msgstr ""

#: ../../docs/tutorials/export/exporting_projects.rst:24
msgid ""
"Distributing a game project on PC with Godot is rather easy. Drop the Godot "
"binary in the same directory as the ``project.godot`` file, then compress "
"the project directory and you are done."
msgstr ""

#: ../../docs/tutorials/export/exporting_projects.rst:28
msgid ""
"It sounds simple, but there are probably a few reasons why the developer may "
"not want to do this. The first one is that it may not be desirable to "
"distribute loads of files. Some developers may not like curious users "
"peeking at how the game was made, others may find it inelegant, and so on. "
"Another reason is that the developer might prefer a specially-compiled "
"binary, which is smaller in size, more optimized and does not include tools "
"like the editor and debugger."
msgstr ""

#: ../../docs/tutorials/export/exporting_projects.rst:36
msgid ""
"Finally, Godot has a simple but efficient system for :ref:`creating DLCs as "
"extra package files <doc_exporting_pcks>`."
msgstr ""

#: ../../docs/tutorials/export/exporting_projects.rst:40
msgid "On mobile"
msgstr ""

#: ../../docs/tutorials/export/exporting_projects.rst:42
msgid ""
"The same scenario on mobile platforms is a little worse. To distribute a "
"project on those devices, a binary for each of those platforms is built, "
"then added to a native project together with the game data."
msgstr ""

#: ../../docs/tutorials/export/exporting_projects.rst:47
msgid ""
"This can be troublesome because it means that the developer must be "
"familiarized with the SDK of each platform before even being able to export. "
"While learning each SDK is always encouraged, it can be frustrating to be "
"forced to do it at an undesired time."
msgstr ""

#: ../../docs/tutorials/export/exporting_projects.rst:52
msgid ""
"There is also another problem with this approach: different devices prefer "
"some data in different formats to run. The main example of this is texture "
"compression. All PC hardware uses S3TC (BC) compression and that has been "
"standardized for more than a decade, but mobile devices use different "
"formats for texture compression, such as ETC1 and ETC2."
msgstr ""

#: ../../docs/tutorials/export/exporting_projects.rst:59
msgid "Export menu"
msgstr ""

#: ../../docs/tutorials/export/exporting_projects.rst:61
msgid ""
"After many attempts at different export workflows, the current one has "
"proven to work the best. At the time of this writing, not all platforms are "
"supported yet, but the supported platforms continue to grow."
msgstr ""

#: ../../docs/tutorials/export/exporting_projects.rst:65
msgid "To open the export menu, click the **Export** button:"
msgstr ""

#: ../../docs/tutorials/export/exporting_projects.rst:69
msgid ""
"The export menu will open. However, it will be completely empty. This is "
"because we need to add an export preset."
msgstr ""

#: ../../docs/tutorials/export/exporting_projects.rst:74
msgid ""
"To create an export preset, click the **Add…** button at the top of the "
"export menu. This will open a drop-down list of platforms to choose from for "
"an export preset."
msgstr ""

#: ../../docs/tutorials/export/exporting_projects.rst:80
msgid ""
"The default options are often enough to export, so tweaking them is usually "
"not necessary. However, many platforms require additional tools (SDKs) to be "
"installed to be able to export. Additionally, Godot needs export templates "
"installed to create packages. The export menu will complain when something "
"is missing and will not allow the user to export for that platform until "
"they resolve it:"
msgstr ""

#: ../../docs/tutorials/export/exporting_projects.rst:89
msgid ""
"At that time, the user is expected to come back to the documentation and "
"follow instructions on how to properly set up that platform."
msgstr ""

#: ../../docs/tutorials/export/exporting_projects.rst:92
msgid ""
"The buttons at the bottom of the menu allow you to export the project in a "
"few different ways:"
msgstr ""

#: ../../docs/tutorials/export/exporting_projects.rst:95
msgid ""
"Export All: Export the project as a playable build (Godot executable and "
"project data) for all the presets defined. All presets must have an **Export "
"Path** defined for this to work."
msgstr ""

#: ../../docs/tutorials/export/exporting_projects.rst:98
msgid ""
"Export Project: Export the project as a playable build (Godot executable and "
"project data) for the selected preset."
msgstr ""

#: ../../docs/tutorials/export/exporting_projects.rst:100
msgid ""
"Export PCK/ZIP: Export the project resources as a PCK or ZIP package. This "
"is not a playable build, it only exports the project data without a Godot "
"executable."
msgstr ""

#: ../../docs/tutorials/export/exporting_projects.rst:104
#: ../../docs/contributing/development/compiling/introduction_to_the_buildsystem.rst:410
#: ../../docs/contributing/development/compiling/compiling_with_dotnet.rst:201
msgid "Export templates"
msgstr ""

#: ../../docs/tutorials/export/exporting_projects.rst:106
msgid ""
"Apart from setting up the platform, the export templates must be installed "
"to be able to export projects. They can be obtained as a TPZ file (which is "
"a renamed ZIP archive) from the `download page of the website <https://www."
"godotengine.org/download>`_."
msgstr ""

#: ../../docs/tutorials/export/exporting_projects.rst:111
msgid ""
"Once downloaded, they can be installed using the **Install Export "
"Templates** option in the editor:"
msgstr ""

#: ../../docs/tutorials/export/exporting_projects.rst:119
msgid "Resource options"
msgstr ""

#: ../../docs/tutorials/export/exporting_projects.rst:121
msgid ""
"When exporting, Godot makes a list of all the files to export and then "
"creates the package. There are 3 different modes for exporting:"
msgstr ""

#: ../../docs/tutorials/export/exporting_projects.rst:124
#, fuzzy
msgid "Export all resources in the project"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/export/exporting_projects.rst:125
msgid "Export selected scenes (and dependencies)"
msgstr ""

#: ../../docs/tutorials/export/exporting_projects.rst:126
msgid "Export selected resources (and dependencies)"
msgstr ""

#: ../../docs/tutorials/export/exporting_projects.rst:130
msgid ""
"**Export all resources in the project** will export every resource in the "
"project. **Export selected scenes** and **Export selected resources** gives "
"you a list of the scenes or resources in the project, and you have to select "
"every scene or resource you want to export."
msgstr ""

#: ../../docs/tutorials/export/exporting_projects.rst:139
msgid ""
"Files and folders whose name begin with a period will never be included in "
"the exported project. This is done to prevent version control folders like "
"``.git`` from being included in the exported PCK file."
msgstr ""

#: ../../docs/tutorials/export/exporting_projects.rst:143
msgid ""
"Below the list of resources are two filters that can be setup. The first "
"allows non resource files such as ``.txt``, ``.json`` and ``.csv`` to be "
"exported with the project. The second filter can be used to exclude every "
"file of a certain type without manually deselecting every one. For example, "
"``.png`` files."
msgstr ""

#: ../../docs/tutorials/export/exporting_projects.rst:149
#, fuzzy
msgid "Configuration files"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/export/exporting_projects.rst:151
msgid ""
"The export configuration is stored in two files that can both be found in "
"the project directory:"
msgstr ""

#: ../../docs/tutorials/export/exporting_projects.rst:154
msgid ""
"``export_presets.cfg``: This file contains the vast majority of the export "
"configuration and can be safely committed to version control. There is "
"nothing in here that you would normally have to keep secret."
msgstr ""

#: ../../docs/tutorials/export/exporting_projects.rst:157
msgid ""
"``.godot/export_credentials.cfg``: This file contains export options that "
"are considered confidential, like passwords and encryption keys. It should "
"generally **not** be committed to version control or shared with others "
"unless you know exactly what you are doing."
msgstr ""

#: ../../docs/tutorials/export/exporting_projects.rst:162
msgid ""
"Since the credentials file is usually kept out of version control systems, "
"some export options will be missing if you clone the project to a new "
"machine. The easiest way to deal with this is to copy the file manually from "
"the old location to the new one."
msgstr ""

#: ../../docs/tutorials/export/exporting_projects.rst:167
msgid "Exporting from the command line"
msgstr ""

#: ../../docs/tutorials/export/exporting_projects.rst:169
msgid ""
"In production, it is useful to automate builds, and Godot supports this with "
"the ``--export`` and ``--export-debug`` command line parameters. Exporting "
"from the command line still requires an export preset to define the export "
"parameters. A basic invocation of the command would be:"
msgstr ""

#: ../../docs/tutorials/export/exporting_projects.rst:178
msgid ""
"This will export to ``some_name.exe``, assuming there is a preset called "
"\"Windows Desktop\" and the template can be found. (The export preset name "
"must be written within quotes if it contains spaces or special characters.) "
"The output path is *relative to the project path* or *absolute*; **it does "
"not respect the directory the command was invoked from**."
msgstr ""

#: ../../docs/tutorials/export/exporting_projects.rst:184
msgid ""
"The output file extension should match the one used by the Godot export "
"process:"
msgstr ""

#: ../../docs/tutorials/export/exporting_projects.rst:186
#, fuzzy
msgid "Windows: ``.exe``"
msgstr "Windows"

#: ../../docs/tutorials/export/exporting_projects.rst:187
msgid ""
"macOS: ``.zip`` (from all platforms) or ``.dmg`` (only when exporting *from* "
"macOS). ``.app`` is not supported directly, although the generated ZIP "
"archive contains an ``.app`` bundle."
msgstr ""

#: ../../docs/tutorials/export/exporting_projects.rst:189
msgid ""
"Linux: Any extension (including none). ``.x86_64`` is typically used for 64-"
"bit x86 binaries."
msgstr ""

#: ../../docs/tutorials/export/exporting_projects.rst:190
msgid "HTML5: ``.zip``"
msgstr ""

#: ../../docs/tutorials/export/exporting_projects.rst:191
msgid "Android: ``.apk``"
msgstr ""

#: ../../docs/tutorials/export/exporting_projects.rst:192
msgid "iOS: ``.zip``"
msgstr ""

#: ../../docs/tutorials/export/exporting_projects.rst:194
msgid ""
"You can also configure it to export *only* the PCK or ZIP file, allowing a "
"single exported main pack file to be used with multiple Godot executables. "
"When doing so, the export preset name must still be specified on the command "
"line:"
msgstr ""

#: ../../docs/tutorials/export/exporting_projects.rst:202
msgid ""
"It is often useful to combine the ``--export`` flag with the ``--path`` "
"flag, so that you do not need to ``cd`` to the project folder before running "
"the command:"
msgstr ""

#: ../../docs/tutorials/export/exporting_projects.rst:212
msgid ""
"See :ref:`doc_command_line_tutorial` for more information about using Godot "
"from the command line."
msgstr ""

#: ../../docs/tutorials/export/exporting_projects.rst:216
msgid "PCK versus ZIP pack file formats"
msgstr ""

#: ../../docs/tutorials/export/exporting_projects.rst:218
msgid ""
"Each format has its upsides and downsides. PCK is the default and "
"recommended format for most use cases, but you may want to use a ZIP archive "
"instead depending on your needs."
msgstr ""

#: ../../docs/tutorials/export/exporting_projects.rst:222
msgid "**PCK format:**"
msgstr ""

#: ../../docs/tutorials/export/exporting_projects.rst:224
msgid "Uncompressed format. Larger file size, but faster to read/write."
msgstr ""

#: ../../docs/tutorials/export/exporting_projects.rst:225
msgid ""
"Not readable and writable using tools normally present on the user's "
"operating system, even though there are `third-party tools <https://github."
"com/hhyyrylainen/GodotPckTool>`__ to extract and create PCK files."
msgstr ""

#: ../../docs/tutorials/export/exporting_projects.rst:230
msgid "**ZIP format:**"
msgstr ""

#: ../../docs/tutorials/export/exporting_projects.rst:232
msgid "Compressed format. Smaller file size, but slower to read/write."
msgstr ""

#: ../../docs/tutorials/export/exporting_projects.rst:233
msgid ""
"Readable and writable using tools normally present on the user's operating "
"system. This can be useful to make modding easier (see also :ref:"
"`doc_exporting_pcks`)."
msgstr ""

#: ../../docs/tutorials/export/exporting_projects.rst:238
msgid ""
"Due to a `known bug <https://github.com/godotengine/godot/pull/42123>`__, "
"when using a ZIP file as a pack file, the exported binary will not try to "
"use it automatically. Therefore, you have to create a *launcher script* that "
"the player can double-click or run from a terminal to launch the project::"
msgstr ""

#: ../../docs/tutorials/export/exporting_projects.rst:250
msgid ""
"Save the launcher script and place it in the same folder as the exported "
"binary. On Linux, make sure to give executable permissions to the launcher "
"script using the command ``chmod +x launch.sh``."
msgstr ""

#: ../../docs/tutorials/export/exporting_pcks.rst:4
msgid "Exporting packs, patches, and mods"
msgstr ""

#: ../../docs/tutorials/export/exporting_pcks.rst:9
msgid ""
"Oftentimes one would like to add functionality to one's game after it has "
"been deployed."
msgstr ""

#: ../../docs/tutorials/export/exporting_pcks.rst:12
msgid "Examples of this include..."
msgstr ""

#: ../../docs/tutorials/export/exporting_pcks.rst:14
msgid ""
"Downloadable Content: the ability to add features and content to one's game."
msgstr ""

#: ../../docs/tutorials/export/exporting_pcks.rst:15
msgid "Patches: the ability to fix a bug that is present in a shipped product."
msgstr ""

#: ../../docs/tutorials/export/exporting_pcks.rst:16
msgid "Mods: grant other people the ability to create content for one's game."
msgstr ""

#: ../../docs/tutorials/export/exporting_pcks.rst:18
msgid ""
"These tools help developers to extend their development beyond the initial "
"release."
msgstr ""

#: ../../docs/tutorials/export/exporting_pcks.rst:22
msgid "Overview of PCK files"
msgstr ""

#: ../../docs/tutorials/export/exporting_pcks.rst:24
msgid ""
"Godot enables this via a feature called **resource packs** (PCK files, with "
"extension ``.pck``)."
msgstr ""

#: ../../docs/tutorials/export/exporting_pcks.rst:27
msgid "**Advantages:**"
msgstr ""

#: ../../docs/tutorials/export/exporting_pcks.rst:29
msgid "incremental updates/patches"
msgstr ""

#: ../../docs/tutorials/export/exporting_pcks.rst:30
msgid "offer DLCs"
msgstr ""

#: ../../docs/tutorials/export/exporting_pcks.rst:31
msgid "offer mod support"
msgstr ""

#: ../../docs/tutorials/export/exporting_pcks.rst:32
msgid "no source code disclosure needed for mods"
msgstr ""

#: ../../docs/tutorials/export/exporting_pcks.rst:33
msgid "more modular project structure"
msgstr ""

#: ../../docs/tutorials/export/exporting_pcks.rst:34
msgid "users don't have to replace the entire game"
msgstr ""

#: ../../docs/tutorials/export/exporting_pcks.rst:36
msgid ""
"The first part of using them involves exporting and delivering the project "
"to players. Then, when one wants to add functionality or content later on, "
"they just deliver the updates via PCK files to the users."
msgstr ""

#: ../../docs/tutorials/export/exporting_pcks.rst:40
msgid "PCK files usually contain, but are not limited to:"
msgstr ""

#: ../../docs/tutorials/export/exporting_pcks.rst:42
msgid "scripts"
msgstr ""

#: ../../docs/tutorials/export/exporting_pcks.rst:43
msgid "scenes"
msgstr ""

#: ../../docs/tutorials/export/exporting_pcks.rst:44
msgid "shaders"
msgstr ""

#: ../../docs/tutorials/export/exporting_pcks.rst:45
msgid "models"
msgstr ""

#: ../../docs/tutorials/export/exporting_pcks.rst:46
msgid "textures"
msgstr ""

#: ../../docs/tutorials/export/exporting_pcks.rst:47
msgid "sound effects"
msgstr ""

#: ../../docs/tutorials/export/exporting_pcks.rst:48
msgid "music"
msgstr ""

#: ../../docs/tutorials/export/exporting_pcks.rst:49
msgid "any other asset suitable for import into the game"
msgstr ""

#: ../../docs/tutorials/export/exporting_pcks.rst:51
msgid ""
"The PCK files can even be an entirely different Godot project, which the "
"original game loads in at runtime."
msgstr ""

#: ../../docs/tutorials/export/exporting_pcks.rst:55
msgid "Generating PCK files"
msgstr ""

#: ../../docs/tutorials/export/exporting_pcks.rst:57
msgid ""
"In order to pack all resources of a project into a PCK file open the project "
"and go to Project/Export and click on \"Export PCK/Zip\". Also make sure to "
"have an export template selected while doing so."
msgstr ""

#: ../../docs/tutorials/export/exporting_pcks.rst:63
msgid ""
"Another method would be to :ref:`export from the command line "
"<doc_command_line_tutorial_exporting>`. If the output file ends with a PCK "
"or ZIP file extension, then the export process will build that type of file "
"for the chosen platform."
msgstr ""

#: ../../docs/tutorials/export/exporting_pcks.rst:69
msgid ""
"If one wishes to support mods for their game, they will need their users to "
"create similarly exported files. Assuming the original game expects a "
"certain structure for the PCK's resources and/or a certain interface for its "
"scripts, then either..."
msgstr ""

#: ../../docs/tutorials/export/exporting_pcks.rst:74
msgid ""
"The developer must publicize documentation of these expected structures/ "
"interfaces, expect modders to install Godot Engine, and then also expect "
"those modders to conform to the documentation's defined API when building "
"mod content for the game (so that it will work). Users would then use "
"Godot's built in exporting tools to create a PCK file, as detailed above."
msgstr ""

#: ../../docs/tutorials/export/exporting_pcks.rst:80
msgid ""
"The developer uses Godot to build a GUI tool for adding their exact API "
"content to a project. This Godot tool must either run on a tools-enabled "
"build of the engine or have access to one (distributed alongside or perhaps "
"in the original game's files). The tool can then use the Godot executable to "
"export a PCK file from the command line with :ref:`OS.execute() "
"<class_OS_method_execute>`. The game itself shouldn't use a tool-build of "
"the engine (for security), so it's best to keep the modding tool and game "
"separate."
msgstr ""

#: ../../docs/tutorials/export/exporting_pcks.rst:90
msgid "Opening PCK files at runtime"
msgstr ""

#: ../../docs/tutorials/export/exporting_pcks.rst:92
msgid ""
"To import a PCK file, one uses the ProjectSettings singleton. The following "
"example expects a “mod.pck” file in the directory of the games executable. "
"The PCK file contains a “mod_scene.tscn” test scene in its root."
msgstr ""

#: ../../docs/tutorials/export/exporting_pcks.rst:123
msgid ""
"By default, if you import a file with the same file path/name as one you "
"already have in your project, the imported one will replace it. This is "
"something to watch out for when creating DLC or mods. You can solve this "
"problem by using a tool that isolates mods to a specific mods subfolder. "
"However, it is also a way of creating patches for one's own game. A PCK file "
"of this kind can fix the content of a previously loaded PCK."
msgstr ""

#: ../../docs/tutorials/export/exporting_pcks.rst:129
msgid ""
"To opt out of this behavior, pass ``false`` as the second argument to :ref:"
"`ProjectSettings.load_resource_pack() "
"<class_ProjectSettings_method_load_resource_pack>`."
msgstr ""

#: ../../docs/tutorials/export/exporting_pcks.rst:133
msgid ""
"For a C# project, you need to build the DLL and place it in the project "
"directory first. Then, before loading the resource pack, you need to load "
"its DLL as follows: ``Assembly.LoadFile(\"mod.dll\")``"
msgstr ""

#: ../../docs/tutorials/export/exporting_pcks.rst:140
msgid ""
"This tutorial explains how to add mods, patches, or DLC to a game. The most "
"important thing is to identify how one plans to distribute future content "
"for their game and develop a workflow that is customized for that purpose. "
"Godot should make that process smooth regardless of which route a developer "
"pursues."
msgstr ""

#: ../../docs/tutorials/export/feature_tags.rst:4
msgid "Feature tags"
msgstr ""

#: ../../docs/tutorials/export/feature_tags.rst:9
msgid ""
"Godot has a special system to tag availability of features. Each *feature* "
"is represented as a string, which can refer to many of the following:"
msgstr ""

#: ../../docs/tutorials/export/feature_tags.rst:12
msgid "Platform name."
msgstr ""

#: ../../docs/tutorials/export/feature_tags.rst:13
msgid "Platform architecture (64-bit or 32-bit, x86 or ARM)."
msgstr ""

#: ../../docs/tutorials/export/feature_tags.rst:14
msgid "Platform type (desktop, mobile, Web)."
msgstr ""

#: ../../docs/tutorials/export/feature_tags.rst:15
msgid "Supported texture compression algorithms on the platform."
msgstr ""

#: ../../docs/tutorials/export/feature_tags.rst:16
msgid ""
"Whether a build is ``debug`` or ``release`` (``debug`` includes the editor)."
msgstr ""

#: ../../docs/tutorials/export/feature_tags.rst:17
msgid ""
"Whether the project is running from the editor or a \"standalone\" binary."
msgstr ""

#: ../../docs/tutorials/export/feature_tags.rst:18
msgid "Many more things."
msgstr ""

#: ../../docs/tutorials/export/feature_tags.rst:20
msgid "Features can be queried at run-time from the singleton API by calling:"
msgstr ""

#: ../../docs/tutorials/export/feature_tags.rst:31
msgid ""
"OS feature tags are used by GDExtension to determine which libraries to "
"load. For example, a library for ``linux.debug.editor.x86_64`` will be "
"loaded only on a debug editor build for Linux x86_64."
msgstr ""

#: ../../docs/tutorials/export/feature_tags.rst:36
msgid "Default features"
msgstr ""

#: ../../docs/tutorials/export/feature_tags.rst:38
msgid ""
"Here is a list of most feature tags in Godot. Keep in mind they are **case-"
"sensitive**:"
msgstr ""

#: ../../docs/tutorials/export/feature_tags.rst:41
msgid "**Feature tag**"
msgstr ""

#: ../../docs/tutorials/export/feature_tags.rst:43
msgid "**android**"
msgstr ""

#: ../../docs/tutorials/export/feature_tags.rst:43
msgid "Running on Android (but not within a Web browser)"
msgstr ""

#: ../../docs/tutorials/export/feature_tags.rst:45
msgid "**bsd**"
msgstr ""

#: ../../docs/tutorials/export/feature_tags.rst:45
msgid "Running on \\*BSD (but not within a Web browser)"
msgstr ""

#: ../../docs/tutorials/export/feature_tags.rst:47
msgid "**linux**"
msgstr ""

#: ../../docs/tutorials/export/feature_tags.rst:47
msgid "Running on Linux (but not within a Web browser)"
msgstr ""

#: ../../docs/tutorials/export/feature_tags.rst:49
msgid "**macos**"
msgstr ""

#: ../../docs/tutorials/export/feature_tags.rst:49
msgid "Running on macOS (but not within a Web browser)"
msgstr ""

#: ../../docs/tutorials/export/feature_tags.rst:51
msgid "**ios**"
msgstr ""

#: ../../docs/tutorials/export/feature_tags.rst:51
msgid "Running on iOS (but not within a Web browser)"
msgstr ""

#: ../../docs/tutorials/export/feature_tags.rst:53
#, fuzzy
msgid "**windows**"
msgstr "Windows"

#: ../../docs/tutorials/export/feature_tags.rst:53
msgid "Running on Windows"
msgstr ""

#: ../../docs/tutorials/export/feature_tags.rst:55
msgid "**linuxbsd**"
msgstr ""

#: ../../docs/tutorials/export/feature_tags.rst:55
msgid "Running on Linux or \\*BSD"
msgstr ""

#: ../../docs/tutorials/export/feature_tags.rst:57
msgid "**debug**"
msgstr ""

#: ../../docs/tutorials/export/feature_tags.rst:57
msgid "Running on a debug build (including the editor)"
msgstr ""

#: ../../docs/tutorials/export/feature_tags.rst:59
msgid "**release**"
msgstr ""

#: ../../docs/tutorials/export/feature_tags.rst:59
msgid "Running on a release build"
msgstr ""

#: ../../docs/tutorials/export/feature_tags.rst:61
#, fuzzy
msgid "**editor**"
msgstr "**Za uređivač:**"

#: ../../docs/tutorials/export/feature_tags.rst:61
msgid "Running on an editor build"
msgstr ""

#: ../../docs/tutorials/export/feature_tags.rst:63
msgid "**template**"
msgstr ""

#: ../../docs/tutorials/export/feature_tags.rst:63
msgid "Running on a non-editor (export template) build"
msgstr ""

#: ../../docs/tutorials/export/feature_tags.rst:65
msgid "**double**"
msgstr ""

#: ../../docs/tutorials/export/feature_tags.rst:65
msgid "Running on a double-precision build"
msgstr ""

#: ../../docs/tutorials/export/feature_tags.rst:67
msgid "**single**"
msgstr ""

#: ../../docs/tutorials/export/feature_tags.rst:67
msgid "Running on a single-precision build"
msgstr ""

#: ../../docs/tutorials/export/feature_tags.rst:69
msgid "**64**"
msgstr ""

#: ../../docs/tutorials/export/feature_tags.rst:69
msgid "Running on a 64-bit build (any architecture)"
msgstr ""

#: ../../docs/tutorials/export/feature_tags.rst:71
msgid "**32**"
msgstr ""

#: ../../docs/tutorials/export/feature_tags.rst:71
msgid "Running on a 32-bit build (any architecture)"
msgstr ""

#: ../../docs/tutorials/export/feature_tags.rst:73
msgid "**x86_64**"
msgstr ""

#: ../../docs/tutorials/export/feature_tags.rst:73
msgid "Running on a 64-bit x86 build"
msgstr ""

#: ../../docs/tutorials/export/feature_tags.rst:75
msgid "**x86_32**"
msgstr ""

#: ../../docs/tutorials/export/feature_tags.rst:75
msgid "Running on a 32-bit x86 build"
msgstr ""

#: ../../docs/tutorials/export/feature_tags.rst:77
msgid "**x86**"
msgstr ""

#: ../../docs/tutorials/export/feature_tags.rst:77
msgid "Running on an x86 build (any bitness)"
msgstr ""

#: ../../docs/tutorials/export/feature_tags.rst:79
msgid "**arm64**"
msgstr ""

#: ../../docs/tutorials/export/feature_tags.rst:79
msgid "Running on a 64-bit ARM build"
msgstr ""

#: ../../docs/tutorials/export/feature_tags.rst:81
msgid "**arm32**"
msgstr ""

#: ../../docs/tutorials/export/feature_tags.rst:81
msgid "Running on a 32-bit ARM build"
msgstr ""

#: ../../docs/tutorials/export/feature_tags.rst:83
msgid "**arm**"
msgstr ""

#: ../../docs/tutorials/export/feature_tags.rst:83
msgid "Running on an ARM build (any bitness)"
msgstr ""

#: ../../docs/tutorials/export/feature_tags.rst:85
msgid "**rv64**"
msgstr ""

#: ../../docs/tutorials/export/feature_tags.rst:85
msgid "Running on a 64-bit RISC-V build"
msgstr ""

#: ../../docs/tutorials/export/feature_tags.rst:87
msgid "**riscv**"
msgstr ""

#: ../../docs/tutorials/export/feature_tags.rst:87
msgid "Running on a RISC-V build (any bitness)"
msgstr ""

#: ../../docs/tutorials/export/feature_tags.rst:89
msgid "**ppc64**"
msgstr ""

#: ../../docs/tutorials/export/feature_tags.rst:89
msgid "Running on a 64-bit PowerPC build"
msgstr ""

#: ../../docs/tutorials/export/feature_tags.rst:91
msgid "**ppc32**"
msgstr ""

#: ../../docs/tutorials/export/feature_tags.rst:91
msgid "Running on a 32-bit PowerPC build"
msgstr ""

#: ../../docs/tutorials/export/feature_tags.rst:93
msgid "**ppc**"
msgstr ""

#: ../../docs/tutorials/export/feature_tags.rst:93
msgid "Running on a PowerPC build (any bitness)"
msgstr ""

#: ../../docs/tutorials/export/feature_tags.rst:95
msgid "**wasm64**"
msgstr ""

#: ../../docs/tutorials/export/feature_tags.rst:95
msgid "Running on a 64-bit WebAssembly build (not yet possible)"
msgstr ""

#: ../../docs/tutorials/export/feature_tags.rst:97
msgid "**wasm32**"
msgstr ""

#: ../../docs/tutorials/export/feature_tags.rst:97
msgid "Running on a 32-bit WebAssembly build"
msgstr ""

#: ../../docs/tutorials/export/feature_tags.rst:99
msgid "**wasm**"
msgstr ""

#: ../../docs/tutorials/export/feature_tags.rst:99
msgid "Running on a WebAssembly build (any bitness)"
msgstr ""

#: ../../docs/tutorials/export/feature_tags.rst:101
msgid "**mobile**"
msgstr ""

#: ../../docs/tutorials/export/feature_tags.rst:101
msgid "Host OS is a mobile platform"
msgstr ""

#: ../../docs/tutorials/export/feature_tags.rst:103
msgid "**pc**"
msgstr ""

#: ../../docs/tutorials/export/feature_tags.rst:103
msgid "Host OS is a PC platform (desktop/laptop)"
msgstr ""

#: ../../docs/tutorials/export/feature_tags.rst:105
msgid "**web**"
msgstr ""

#: ../../docs/tutorials/export/feature_tags.rst:105
msgid "Host OS is a Web browser"
msgstr ""

#: ../../docs/tutorials/export/feature_tags.rst:107
msgid "**web_android**"
msgstr ""

#: ../../docs/tutorials/export/feature_tags.rst:107
msgid "Host OS is a Web browser running on Android"
msgstr ""

#: ../../docs/tutorials/export/feature_tags.rst:109
msgid "**web_ios**"
msgstr ""

#: ../../docs/tutorials/export/feature_tags.rst:109
msgid "Host OS is a Web browser running on iOS"
msgstr ""

#: ../../docs/tutorials/export/feature_tags.rst:111
msgid "**web_linuxbsd**"
msgstr ""

#: ../../docs/tutorials/export/feature_tags.rst:111
msgid "Host OS is a Web browser running on Linux or \\*BSD"
msgstr ""

#: ../../docs/tutorials/export/feature_tags.rst:113
msgid "**web_macos**"
msgstr ""

#: ../../docs/tutorials/export/feature_tags.rst:113
msgid "Host OS is a Web browser running on macOS"
msgstr ""

#: ../../docs/tutorials/export/feature_tags.rst:115
msgid "**web_windows**"
msgstr ""

#: ../../docs/tutorials/export/feature_tags.rst:115
msgid "Host OS is a Web browser running on Windows"
msgstr ""

#: ../../docs/tutorials/export/feature_tags.rst:117
msgid "**etc**"
msgstr ""

#: ../../docs/tutorials/export/feature_tags.rst:117
msgid "Textures using ETC1 compression are supported"
msgstr ""

#: ../../docs/tutorials/export/feature_tags.rst:119
msgid "**etc2**"
msgstr ""

#: ../../docs/tutorials/export/feature_tags.rst:119
msgid "Textures using ETC2 compression are supported"
msgstr ""

#: ../../docs/tutorials/export/feature_tags.rst:121
msgid "**s3tc**"
msgstr ""

#: ../../docs/tutorials/export/feature_tags.rst:121
msgid "Textures using S3TC (DXT/BC) compression are supported"
msgstr ""

#: ../../docs/tutorials/export/feature_tags.rst:123
msgid "**movie**"
msgstr ""

#: ../../docs/tutorials/export/feature_tags.rst:123
msgid ":ref:`Movie Maker mode <doc_creating_movies>` is active"
msgstr ""

#: ../../docs/tutorials/export/feature_tags.rst:128
msgid ""
"With the exception of texture compression and ``movie`` feature tags, "
"default feature tags are **immutable**. This means that they will *not* "
"change depending on run-time conditions. For example, ``OS."
"has_feature(\"mobile\")`` will return ``false`` when running a project "
"exported to HTML5 on a mobile device."
msgstr ""

#: ../../docs/tutorials/export/feature_tags.rst:134
msgid ""
"To check whether a project exported to HTML5 is running on a mobile device, :"
"ref:`call JavaScript code <doc_javascript_eval>` that reads the browser's "
"user agent."
msgstr ""

#: ../../docs/tutorials/export/feature_tags.rst:139
msgid "Custom features"
msgstr ""

#: ../../docs/tutorials/export/feature_tags.rst:141
msgid ""
"It is possible to add custom features to a build; use the relevant field in "
"the *export preset* used to generate it:"
msgstr ""

#: ../../docs/tutorials/export/feature_tags.rst:148
msgid ""
"Custom feature tags are only used when running the exported project "
"(including with :ref:`doc_one-click_deploy`). They are **not used** when "
"running the project from the editor, even if the export preset marked as "
"**Runnable** for your current platform has custom feature tags defined."
msgstr ""

#: ../../docs/tutorials/export/feature_tags.rst:154
msgid "Overriding project settings"
msgstr ""

#: ../../docs/tutorials/export/feature_tags.rst:156
msgid ""
"Features can be used to override specific configuration values in the "
"*Project Settings*. This allows you to better customize any configuration "
"when doing a build."
msgstr ""

#: ../../docs/tutorials/export/feature_tags.rst:159
msgid ""
"In the following example, a different icon is added for the demo build of "
"the game (which was customized in a special export preset, which, in turn, "
"includes only demo levels)."
msgstr ""

#: ../../docs/tutorials/export/feature_tags.rst:164
msgid "After overriding, a new field is added for this specific configuration:"
msgstr ""

#: ../../docs/tutorials/export/feature_tags.rst:170
msgid ""
"When using the :ref:`project settings \"override.cfg\" functionality "
"<class_ProjectSettings>` (which is unrelated to feature tags), remember that "
"feature tags still apply. Therefore, make sure to *also* override the "
"setting with the desired feature tag(s) if you want them to override base "
"project settings on all platforms and configurations."
msgstr ""

#: ../../docs/tutorials/export/feature_tags.rst:178
msgid "Default overrides"
msgstr ""

#: ../../docs/tutorials/export/feature_tags.rst:180
msgid ""
"There are already a lot of settings that come with overrides by default; "
"they can be found in many sections of the project settings."
msgstr ""

#: ../../docs/tutorials/export/feature_tags.rst:186
msgid "Customizing the build"
msgstr ""

#: ../../docs/tutorials/export/feature_tags.rst:188
msgid ""
"Feature tags can be used to customize a build process too, by writing a "
"custom **ExportPlugin**. They are also used to specify which shared library "
"is loaded and exported in **GDExtension**."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_linux.rst:4
#, fuzzy
msgid "Exporting for Linux"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/export/exporting_for_linux.rst:8
msgid ""
"This page describes how to export a Godot project to Linux. If you're "
"looking to compile editor or export template binaries from source instead, "
"read :ref:`doc_compiling_for_linuxbsd`."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_linux.rst:12
msgid ""
"The simplest way to distribute a game for PC is to copy the executable "
"(``godot``), compress the folder and send it to someone else. However, this "
"is often not desired."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_linux.rst:16
msgid ""
"Godot offers a more elegant approach for PC distribution when using the "
"export system. When exporting for Linux, the exporter takes all the project "
"files and creates a ``data.pck`` file. This file is bundled with a specially "
"optimized binary that is smaller, faster and does not contain the editor and "
"debugger."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_linux.rst:22
#: ../../docs/tutorials/export/exporting_for_macos.rst:219
#: ../../docs/tutorials/export/exporting_for_windows.rst:60
#: ../../docs/tutorials/export/exporting_for_ios.rst:114
#: ../../docs/tutorials/export/exporting_for_android.rst:183
#: ../../docs/tutorials/export/exporting_for_web.rst:392
msgid "Environment variables"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_linux.rst:24
#: ../../docs/tutorials/export/exporting_for_macos.rst:221
#: ../../docs/tutorials/export/exporting_for_windows.rst:62
#: ../../docs/tutorials/export/exporting_for_ios.rst:116
#: ../../docs/tutorials/export/exporting_for_android.rst:185
#: ../../docs/tutorials/export/exporting_for_web.rst:394
msgid ""
"You can use the following environment variables to set export options "
"outside of the editor. During the export process, these override the values "
"that you set in the export menu."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_linux.rst:28
msgid "Linux export environment variables"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_linux.rst:31
#: ../../docs/tutorials/export/exporting_for_macos.rst:228
#: ../../docs/tutorials/export/exporting_for_windows.rst:69
#: ../../docs/tutorials/export/exporting_for_ios.rst:123
#: ../../docs/tutorials/export/exporting_for_android.rst:192
#: ../../docs/tutorials/export/exporting_for_web.rst:401
#, fuzzy
msgid "Export option"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/export/exporting_for_linux.rst:32
#: ../../docs/tutorials/export/exporting_for_macos.rst:229
#: ../../docs/tutorials/export/exporting_for_windows.rst:70
#: ../../docs/tutorials/export/exporting_for_ios.rst:124
#: ../../docs/tutorials/export/exporting_for_android.rst:193
#: ../../docs/tutorials/export/exporting_for_web.rst:402
msgid "Environment variable"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_linux.rst:33
#: ../../docs/tutorials/export/exporting_for_macos.rst:230
#: ../../docs/tutorials/export/exporting_for_windows.rst:71
#: ../../docs/tutorials/export/exporting_for_ios.rst:125
#: ../../docs/tutorials/export/exporting_for_android.rst:194
#: ../../docs/tutorials/export/exporting_for_web.rst:403
msgid "Encryption / Encryption Key"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_linux.rst:34
#: ../../docs/tutorials/export/exporting_for_macos.rst:231
#: ../../docs/tutorials/export/exporting_for_windows.rst:72
#: ../../docs/tutorials/export/exporting_for_ios.rst:126
#: ../../docs/tutorials/export/exporting_for_android.rst:195
#: ../../docs/tutorials/export/exporting_for_web.rst:404
msgid "``GODOT_SCRIPT_ENCRYPTION_KEY``"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_macos.rst:4
#, fuzzy
msgid "Exporting for macOS"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/export/exporting_for_macos.rst:8
msgid ""
"This page describes how to export a Godot project to macOS. If you're "
"looking to compile editor or export template binaries from source instead, "
"read :ref:`doc_compiling_for_macos`."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_macos.rst:12
msgid ""
"macOS apps exported with the official export templates are exported as a "
"single \"Universal 2\" binary ``.app`` bundle, a folder with a specific "
"structure which stores the executable, libraries and all the project files. "
"This bundle can be exported as is, packed in a ZIP archive or DMG disk image "
"(only supported when exporting from a computer running macOS). `Universal "
"binaries for macOS support both Intel x86_64 and ARM64 (Apple silicon, i.e. "
"M1) architectures <https://developer.apple.com/documentation/apple-silicon/"
"building-a-universal-macos-binary>`__."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_macos.rst:19
msgid ""
"Download the Godot export templates. Use the Godot menu: ``Editor > Manage "
"Export Templates``."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_macos.rst:20
msgid ""
"A valid and unique ``Bundle identifier`` should be set in the "
"``Application`` section of the export options."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_macos.rst:24
msgid ""
"Projects exported without code signing and notarization will be blocked by "
"Gatekeeper if they are downloaded from unknown sources, see the :ref:"
"`Running Godot apps on macOS <doc_running_on_macos>` page for more "
"information."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_macos.rst:27
msgid "Code signing and notarization"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_macos.rst:29
msgid ""
"By default, macOS will run only applications that are signed and notarized. "
"If you use any other signing configuration, see :ref:`Running Godot apps on "
"macOS <doc_running_on_macos>` for workarounds."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_macos.rst:31
msgid ""
"To notarize an app, you **must** have a valid `Apple Developer ID "
"Certificate <https://developer.apple.com/>`__."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_macos.rst:34
msgid "If you have an Apple Developer ID Certificate and exporting from macOS"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_macos.rst:36
msgid ""
"Install `Xcode <https://developer.apple.com/xcode/>`__ command line tools "
"and open Xcode at least once or run the ``sudo xcodebuild -license accept`` "
"command to accept license agreement."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_macos.rst:39
#: ../../docs/tutorials/export/exporting_for_macos.rst:63
msgid "To sign exported app"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_macos.rst:41
msgid "Select ``Xcode codesign`` in the ``Code Signing > Codesign`` option."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_macos.rst:42
msgid ""
"Set valid Apple ID certificate identity (certificate \"Common Name\") in the "
"``Code Signing > Identity`` section."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_macos.rst:45
#: ../../docs/tutorials/export/exporting_for_macos.rst:69
msgid "To notarize exported app"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_macos.rst:47
msgid "Select ``Xcode altool`` in the ``Notarization > Notarization`` option."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_macos.rst:48
#: ../../docs/tutorials/export/exporting_for_macos.rst:72
msgid "Disable the ``Debugging`` entitlement."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_macos.rst:49
msgid ""
"Set valid Apple ID login / app. specific password or `App Store Connect "
"<https://developer.apple.com/documentation/appstoreconnectapi>`__ API UUID / "
"Key in the ``Notarization`` section."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_macos.rst:51
msgid ""
"You can use the ``xcrun notarytool history`` command to check notarization "
"status and use the ``xcrun notarytool log {ID}`` command to download the "
"notarization log."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_macos.rst:53
msgid ""
"If you encounter notarization issues, see `Resolving common notarization "
"issues <https://developer.apple.com/documentation/security/"
"notarizing_macos_software_before_distribution/"
"resolving_common_notarization_issues>`__ for more info."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_macos.rst:55
msgid ""
"After notarization is completed, `staple the ticket <https://developer.apple."
"com/documentation/security/notarizing_macos_software_before_distribution/"
"customizing_the_notarization_workflow>`__ to the exported project."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_macos.rst:58
msgid ""
"If you have an Apple Developer ID Certificate and exporting from Linux or "
"Windows"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_macos.rst:60
msgid ""
"Install `PyOxidizer rcodesign <https://github.com/indygreg/apple-platform-rs/"
"tree/main/apple-codesign>`__, and configure the path to ``rcodesign`` in the "
"``Editor Settings > Export > macOS > rcodesign``."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_macos.rst:65
msgid ""
"Select ``PyOxidizer rcodesign`` in the ``Code Signing > Codesign`` option."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_macos.rst:66
msgid ""
"Set valid Apple ID PKCS #12 certificate file and password in the ``Code "
"Signing`` section."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_macos.rst:71
msgid ""
"Select ``PyOxidizer rcodesign`` in the ``Notarization > Notarization`` "
"option."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_macos.rst:73
msgid ""
"Set valid `App Store Connect <https://developer.apple.com/documentation/"
"appstoreconnectapi>`__ API UUID / Key in the ``Notarization`` section."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_macos.rst:75
msgid ""
"You can use the ``rcodesign notary-log`` command to check notarization "
"status."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_macos.rst:77
msgid ""
"After notarization is completed, use the ``rcodesign staple`` command to "
"staple the ticket to the exported project."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_macos.rst:80
msgid "If you do not have an Apple Developer ID Certificate"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_macos.rst:82
msgid ""
"Select ``Built-in (ad-hoc only)`` in the ``Code Signing > Codesign`` option."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_macos.rst:83
msgid "Select ``Disabled`` in the ``Notarization > Notarization`` option."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_macos.rst:85
msgid ""
"In this case Godot will use a ad-hoc signature, which will make running an "
"exported app easier for the end users, see the :ref:`Running Godot apps on "
"macOS <doc_running_on_macos>` page for more information."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_macos.rst:88
#, fuzzy
msgid "Signing Options"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/export/exporting_for_macos.rst:91
#: ../../docs/tutorials/export/exporting_for_macos.rst:111
msgid "Option"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_macos.rst:93
msgid "Codesign"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_macos.rst:93
msgid "Tool to use for code signing."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_macos.rst:95
msgid "Identity"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_macos.rst:95
msgid ""
"The \"Full Name\" or \"Common Name\" of the signing identity, store in the "
"macOS keychain. [1]_"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_macos.rst:97
msgid "Certificate File"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_macos.rst:97
msgid "The PKCS #12 certificate file. [2]_"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_macos.rst:99
msgid "Certificate Password"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_macos.rst:99
msgid "Password for the certificate file. [2]_"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_macos.rst:101
#, fuzzy
msgid "Custom Options"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/export/exporting_for_macos.rst:101
msgid "Array of command line arguments passed to the code signing tool."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_macos.rst:104
msgid "This option is visible only when signing with Xcode codesign."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_macos.rst:105
msgid "These options are visible only when signing with PyOxidizer rcodesign."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_macos.rst:108
msgid "Notarization Options"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_macos.rst:113
#, fuzzy
msgid "Notarization"
msgstr "Uvod"

#: ../../docs/tutorials/export/exporting_for_macos.rst:113
msgid "Tool to use for notarization."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_macos.rst:115
msgid "Apple ID Name"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_macos.rst:115
msgid "Apple ID account name (email address). [3]_"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_macos.rst:117
msgid "Apple ID Password"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_macos.rst:117
msgid ""
"Apple ID app-specific password. See `Using app-specific passwords <https://"
"support.apple.com/en-us/HT204397>`__ to enable two-factor authentication and "
"create app password. [3]_"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_macos.rst:119
msgid "Apple Team ID"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_macos.rst:119
msgid ""
"Team ID (\"Organization Unit\"), if your Apple ID belongs to multiple teams "
"(optional). [3]_"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_macos.rst:121
msgid "API UUID"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_macos.rst:121
msgid ""
"Apple `App Store Connect <https://developer.apple.com/documentation/"
"appstoreconnectapi>`__ API issuer UUID."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_macos.rst:123
msgid "API Key"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_macos.rst:123
msgid ""
"Apple `App Store Connect <https://developer.apple.com/documentation/"
"appstoreconnectapi>`__ API key."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_macos.rst:128
msgid ""
"You should set either Apple ID Name/Password or App Store Connect API UUID/"
"Key."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_macos.rst:130
msgid "These options are visible only when notarizing with Xcode altool."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_macos.rst:132
msgid ""
"See `Notarizing macOS Software Before Distribution <https://developer.apple."
"com/documentation/security/notarizing_macos_software_before_distribution?"
"language=objc>`__ for more info."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_macos.rst:135
msgid "Entitlements"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_macos.rst:138
msgid "Hardened Runtime Entitlements"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_macos.rst:140
msgid ""
"Hardened Runtime entitlements manage security options and resource access "
"policy. See `Hardened Runtime <https://developer.apple.com/documentation/"
"security/hardened_runtime?language=objc>`__ for more info."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_macos.rst:144
#: ../../docs/tutorials/export/exporting_for_macos.rst:187
msgid "Entitlement"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_macos.rst:146
msgid "Allow JIT Code Execution [4]_"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_macos.rst:146
msgid ""
"Allows creating writable and executable memory for JIT code. If you are "
"using add-ons with dynamic or self-modifying native code, enable them "
"according to the add-on documentation."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_macos.rst:148
msgid "Allow Unsigned Executable Memory [4]_"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_macos.rst:148
msgid ""
"Allows creating writable and executable memory without JIT restrictions. If "
"you are using add-ons with dynamic or self-modifying native code, enable "
"them according to the add-on documentation."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_macos.rst:150
msgid "Allow DYLD Environment Variables [4]_"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_macos.rst:150
msgid ""
"Allows app to uss dynamic linker environment variables to inject code. If "
"you are using add-ons with dynamic or self-modifying native code, enable "
"them according to the add-on documentation."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_macos.rst:152
msgid "Disable Library Validation"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_macos.rst:152
msgid ""
"Allows app to load arbitrary libraries and frameworks. Enable it if you are "
"using GDExtension add-ons or ad-hoc signing, or want to support user-"
"provided external add-ons."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_macos.rst:154
msgid "Audio Input"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_macos.rst:154
msgid ""
"Enable if you need to use the microphone or other audio input sources, if "
"it's enabled you should also provide usage message in the `privacy/"
"microphone_usage_description` option."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_macos.rst:156
msgid "Camera"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_macos.rst:156
msgid ""
"Enable if you need to use the camera, if it's enabled you should also "
"provide usage message in the `privacy/camera_usage_description` option."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_macos.rst:158
#: ../../docs/tutorials/io/data_paths.rst:72
#: ../../docs/tutorials/io/data_paths.rst:121
msgid "Location"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_macos.rst:158
msgid ""
"Enable if you need to use location information from Location Services, if "
"it's enabled you should also provide usage message in the `privacy/"
"location_usage_description` option."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_macos.rst:160
msgid "Address Book"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_macos.rst:160
msgid ""
"[5]_ Enable to allow access contacts in the user's address book, if it's "
"enabled you should also provide usage message in the `privacy/"
"address_book_usage_description` option."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_macos.rst:162
msgid "Calendars"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_macos.rst:162
msgid ""
"[5]_ Enable to allow access to the user's calendar, if it's enabled you "
"should also provide usage message in the `privacy/"
"calendar_usage_description` option."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_macos.rst:164
msgid "Photo Library"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_macos.rst:164
msgid ""
"[5]_ Enable to allow access to the user's Photos library, if it's enabled "
"you should also provide usage message in the `privacy/"
"photos_library_usage_description` option."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_macos.rst:166
msgid "Apple Events"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_macos.rst:166
msgid "[5]_ Enable to allow app to send Apple events to other apps."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_macos.rst:168
msgid ""
"[6]_ You can temporarily enable this entitlement to use native debugger "
"(GDB, LLDB) with the exported app. This entitlement should be disabled for "
"production export."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_macos.rst:171
msgid ""
"The ``Allow JIT Code Execution``, ``Allow Unsigned Executable Memory`` and "
"``Allow DYLD Environment Variables`` entitlements are always enabled for the "
"Godot Mono exports, and are not visible in the export options."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_macos.rst:172
msgid ""
"These features aren't supported by Godot out of the box, enable them only if "
"you are using add-ons which require them."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_macos.rst:173
msgid "To notarize an app, you must disable the ``Debugging`` entitlement."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_macos.rst:176
msgid "App Sandbox Entitlement"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_macos.rst:178
msgid ""
"The App Sandbox restricts access to user data, networking and devices. "
"Sandboxed apps can't access most of the file system, can't use custom file "
"dialogs and execute binaries (using ``OS.execute`` and ``OS."
"create_process``) outside the ``.app`` bundle. See `App Sandbox <https://"
"developer.apple.com/documentation/security/app_sandbox?language=objc>`__ for "
"more info."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_macos.rst:184
msgid ""
"To distribute an app through the App Store, you must enable the App Sandbox."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_macos.rst:189
msgid "Enabled"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_macos.rst:189
msgid "Enables App Sandbox."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_macos.rst:191
msgid "Network Server"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_macos.rst:191
msgid "Enable to allow app to listen for incoming network connections."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_macos.rst:193
msgid "Network Client"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_macos.rst:193
msgid "Enable to allow app to establish outgoing network connections."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_macos.rst:195
msgid "Device USB"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_macos.rst:195
msgid ""
"Enable to allow app to interact with USB devices. This entitlement is "
"required to use wired controllers."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_macos.rst:197
msgid "Device Bluetooth"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_macos.rst:197
msgid ""
"Enable to allow app to interact with Bluetooth devices. This entitlement is "
"required to use wireless controllers."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_macos.rst:199
msgid "Files Downloads [7]_"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_macos.rst:199
msgid "Allows read or write access to the user's \"Downloads\" folder."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_macos.rst:201
msgid "Files Pictures [7]_"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_macos.rst:201
msgid "Allows read or write access to the user's \"Pictures\" folder."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_macos.rst:203
msgid "Files Music [7]_"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_macos.rst:203
msgid "Allows read or write access to the user's \"Music\" folder."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_macos.rst:205
msgid "Files Movies [7]_"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_macos.rst:205
msgid "Allows read or write access to the user's \"Movies\" folder."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_macos.rst:207
msgid "Files User Selected [7]_"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_macos.rst:207
msgid ""
"Allows read or write access to arbitrary folder. To gain access, a folder "
"must be selected from the native file dialog by the user."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_macos.rst:209
msgid "Helper Executable"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_macos.rst:209
msgid ""
"List of helper executables to embedded to the app bundle. Sandboxed app are "
"limited to execute only these executable."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_macos.rst:212
msgid ""
"You can optionally provide usage messages for various folders in the "
"`privacy/*_folder_usage_description` options."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_macos.rst:216
msgid ""
"You can override default entitlements by selecting custom entitlements file, "
"in this case all other entitlement are ignored."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_macos.rst:225
msgid "macOS export environment variables"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_macos.rst:232
msgid "Options / Codesign / Certificate File"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_macos.rst:233
msgid "``GODOT_MACOS_CODESIGN_CERTIFICATE_FILE``"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_macos.rst:234
msgid "Options / Codesign / Certificate Password"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_macos.rst:235
msgid "``GODOT_MACOS_CODESIGN_CERTIFICATE_PASSWORD``"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_macos.rst:236
msgid "Options / Codesign / Provisioning Profile"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_macos.rst:237
msgid "``GODOT_MACOS_CODESIGN_PROVISIONING_PROFILE``"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_macos.rst:238
msgid "Options / Notarization / API UUID"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_macos.rst:239
msgid "``GODOT_MACOS_NOTARIZATION_API_UUID``"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_macos.rst:240
msgid "Options / Notarization / API Key"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_macos.rst:241
msgid "``GODOT_MACOS_NOTARIZATION_API_KEY``"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_macos.rst:242
msgid "Options / Notarization / API Key ID"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_macos.rst:243
msgid "``GODOT_MACOS_NOTARIZATION_API_KEY_ID``"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_macos.rst:244
msgid "Options / Notarization / Apple ID Name"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_macos.rst:245
msgid "``GODOT_MACOS_NOTARIZATION_APPLE_ID_NAME``"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_macos.rst:246
msgid "Options / Notarization / Apple ID Password"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_macos.rst:247
msgid "``GODOT_MACOS_NOTARIZATION_APPLE_ID_PASSWORD``"
msgstr ""

#: ../../docs/tutorials/export/running_on_macos.rst:4
msgid "Running Godot apps on macOS"
msgstr ""

#: ../../docs/tutorials/export/running_on_macos.rst:8
msgid ""
"This page covers running Godot projects on macOS. If you haven't exported "
"your project yet, read :ref:`doc_exporting_for_macos` first."
msgstr ""

#: ../../docs/tutorials/export/running_on_macos.rst:11
msgid ""
"By default, macOS will run only applications that are signed and notarized."
msgstr ""

#: ../../docs/tutorials/export/running_on_macos.rst:15
msgid ""
"When running an app from the Downloads folder or when still in quarantine, "
"Gatekeeper will perform *path randomization* as a security measure. This "
"breaks access to relative paths from the app, which the app relies upon to "
"work. To resolve this issue, move the app to the ``/Applications`` folder."
msgstr ""

#: ../../docs/tutorials/export/running_on_macos.rst:20
msgid ""
"In general, macOS apps should avoid relying on relative paths from the "
"application folder."
msgstr ""

#: ../../docs/tutorials/export/running_on_macos.rst:23
msgid ""
"Depending on the way a macOS app is signed and distributed, the following "
"scenarios are possible:"
msgstr ""

#: ../../docs/tutorials/export/running_on_macos.rst:26
msgid "App is signed, notarized and distributed via App Store"
msgstr ""

#: ../../docs/tutorials/export/running_on_macos.rst:30
msgid ""
"App developers need to join the Apple Developer Program, and configure "
"signing and notarization options during export, then upload the app to the "
"App Store."
msgstr ""

#: ../../docs/tutorials/export/running_on_macos.rst:32
msgid ""
"The app should run out of the box, without extra user interaction required."
msgstr ""

#: ../../docs/tutorials/export/running_on_macos.rst:35
msgid "App is signed, notarized and distributed outside App Store"
msgstr ""

#: ../../docs/tutorials/export/running_on_macos.rst:39
msgid ""
"App developers need to join the Apple Developer Program, and configure "
"signing and notarization options during export, then distribute the app as "
"\".DMG\" or \".ZIP\" archive."
msgstr ""

#: ../../docs/tutorials/export/running_on_macos.rst:41
#: ../../docs/tutorials/export/running_on_macos.rst:62
#: ../../docs/tutorials/export/running_on_macos.rst:98
#: ../../docs/tutorials/export/running_on_macos.rst:119
msgid ""
"When you run the app for the first time, the following dialog is displayed:"
msgstr ""

#: ../../docs/tutorials/export/running_on_macos.rst:45
msgid "Click ``Open`` to start the app."
msgstr ""

#: ../../docs/tutorials/export/running_on_macos.rst:47
msgid ""
"If you see the following warning dialog, your Mac is set up to allow apps "
"only from the App Store."
msgstr ""

#: ../../docs/tutorials/export/running_on_macos.rst:51
msgid ""
"To allow third-party apps, open ``System Preferences``, click ``Security & "
"Privacy``, then click ``General``, unlock settings, and select ``App Store "
"and identified developers``."
msgstr ""

#: ../../docs/tutorials/export/running_on_macos.rst:56
msgid "App is signed (including ad-hoc signatures) but not notarized"
msgstr ""

#: ../../docs/tutorials/export/running_on_macos.rst:60
msgid ""
"App developer used self-signed certificate or ad-hoc signing (default Godot "
"behavior for exported project)."
msgstr ""

#: ../../docs/tutorials/export/running_on_macos.rst:66
msgid "To run this app, you can temporarily override Gatekeeper:"
msgstr ""

#: ../../docs/tutorials/export/running_on_macos.rst:68
msgid ""
"Either open ``System Preferences``, click ``Security & Privacy``, then click "
"``General``, and click ``Open Anyway``."
msgstr ""

#: ../../docs/tutorials/export/running_on_macos.rst:72
msgid ""
"Or, right-click (Control-click) on the app icon in the Finder window and "
"select ``Open`` from the menu."
msgstr ""

#: ../../docs/tutorials/export/running_on_macos.rst:76
msgid "Then click ``Open`` in the confirmation dialog."
msgstr ""

#: ../../docs/tutorials/export/running_on_macos.rst:80
msgid "Enter your password if you're prompted."
msgstr ""

#: ../../docs/tutorials/export/running_on_macos.rst:82
msgid ""
"Another option is to disable Gatekeeper entirely. Note that this does "
"decrease the security of your computer by allowing you to run any software "
"you want. To do this, run ``sudo spctl --master-disable`` in the Terminal, "
"enter your password, and then the **Anywhere** option will be available:"
msgstr ""

#: ../../docs/tutorials/export/running_on_macos.rst:89
msgid "Note that Gatekeeper will re-enable itself when macOS updates."
msgstr ""

#: ../../docs/tutorials/export/running_on_macos.rst:92
msgid "App is not signed, executable is linker-signed"
msgstr ""

#: ../../docs/tutorials/export/running_on_macos.rst:96
msgid "App is built using official export templates, but it is not signed."
msgstr ""

#: ../../docs/tutorials/export/running_on_macos.rst:102
msgid ""
"To run this app, you should remove the quarantine extended file attribute "
"manually:"
msgstr ""

#: ../../docs/tutorials/export/running_on_macos.rst:104
#: ../../docs/tutorials/export/running_on_macos.rst:127
msgid ""
"Open ``Terminal.app`` (press :kbd:`Cmd + Space` and enter ``Terminal``)."
msgstr ""

#: ../../docs/tutorials/export/running_on_macos.rst:106
#: ../../docs/tutorials/export/running_on_macos.rst:129
msgid "Navigate to the folder containing the target application."
msgstr ""

#: ../../docs/tutorials/export/running_on_macos.rst:108
#: ../../docs/tutorials/export/running_on_macos.rst:131
msgid ""
"Use the ``cd path_to_the_app_folder`` command, e.g. ``cd ~/Downloads/`` if "
"it's in the ``Downloads`` folder."
msgstr ""

#: ../../docs/tutorials/export/running_on_macos.rst:110
msgid ""
"Run the command ``xattr -dr com.apple.quarantine \"Unsigned Game.app\"`` "
"(including quotation marks and ``.app`` extension)."
msgstr ""

#: ../../docs/tutorials/export/running_on_macos.rst:113
msgid ""
"Neither app nor executable is signed (relevant for Apple Silicon Macs only)"
msgstr ""

#: ../../docs/tutorials/export/running_on_macos.rst:117
msgid ""
"App is built using custom export templates, compiled using OSXCross, and it "
"is not signed at all."
msgstr ""

#: ../../docs/tutorials/export/running_on_macos.rst:123
msgid "To run this app, you can ad-hoc sign it yourself:"
msgstr ""

#: ../../docs/tutorials/export/running_on_macos.rst:125
msgid ""
"Install ``Xcode`` for the App Store, start it and confirm command line tools "
"installation."
msgstr ""

#: ../../docs/tutorials/export/running_on_macos.rst:133
msgid "Run the following commands:"
msgstr ""

#: ../../docs/tutorials/export/running_on_macos.rst:135
msgid ""
"``xattr -dr com.apple.quarantine \"Unsigned Game.app\"`` (including "
"quotation marks and \".app\" extension)."
msgstr ""

#: ../../docs/tutorials/export/running_on_macos.rst:137
msgid ""
"``codesign -s - --force --deep \"Unsigned Game.app\"`` (including quotation "
"marks and \".app\" extension)."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_windows.rst:4
#, fuzzy
msgid "Exporting for Windows"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/export/exporting_for_windows.rst:8
msgid ""
"This page describes how to export a Godot project to Windows. If you're "
"looking to compile editor or export template binaries from source instead, "
"read :ref:`doc_compiling_for_windows`."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_windows.rst:12
msgid ""
"The simplest way to distribute a game for PC is to copy the executable "
"(``godot.exe``), compress the folder and send it to someone else. However, "
"this is often not desired."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_windows.rst:16
msgid ""
"Godot offers a more elegant approach for PC distribution when using the "
"export system. When exporting for Windows, the exporter takes all the "
"project files and creates a ``data.pck`` file. This file is bundled with a "
"specially optimized binary that is smaller, faster and does not contain the "
"editor and debugger."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_windows.rst:22
#, fuzzy
msgid "Code signing"
msgstr "Uvod / Početak"

#: ../../docs/tutorials/export/exporting_for_windows.rst:24
msgid ""
"Godot is capable of automatic code signing on export. To do this you must "
"have the ``Windows SDK`` (on Windows) or `osslsigncode <https://github.com/"
"mtrojnar/osslsigncode>`__ (on any other OS) installed. You will also need a "
"package signing certificate, information on creating one can be found `here "
"<https://docs.microsoft.com/en-us/windows/win32/appxpkg/how-to-create-a-"
"package-signing-certificate?redirectedfrom=MSDN>`__."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_windows.rst:31
msgid ""
"If you export for Windows with embedded PCK files, you will not be able to "
"sign the program as it will break."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_windows.rst:34
msgid ""
"On Windows, PCK embedding is also known to cause false positives in "
"antivirus programs. Therefore, it's recommended to avoid using it unless "
"you're distributing your project via Steam as it bypasses code signing and "
"antivirus checks."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_windows.rst:42
msgid ""
"Settings need to be changed in two places. First, in the editor settings, "
"under **Export > Windows**. Click on the folder next to the ``Sign Tool`` "
"setting, if you're using Windows navigate to and select ``SignTool.exe``, if "
"you're on a different OS select ``osslsigncode``."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_windows.rst:49
msgid ""
"The second location is the Windows export preset, which can be found in "
"**Project > Export...**. Add a windows desktop preset if you haven't "
"already. Under options there is a code signing category."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_windows.rst:55
msgid ""
"``Enabled`` must be set to true, and ``Identity`` must be set to the signing "
"certificate. The other settings can be adjusted as needed. Once this is Done "
"Godot will sign your project on export."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_windows.rst:66
msgid "Windows export environment variables"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_windows.rst:73
msgid "Options / Codesign / Identity Type"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_windows.rst:74
msgid "``GODOT_WINDOWS_CODESIGN_IDENTITY_TYPE``"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_windows.rst:75
msgid "Options / Codesign / Identity"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_windows.rst:76
msgid "``GODOT_WINDOWS_CODESIGN_IDENTITY``"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_windows.rst:77
msgid "Options / Codesign / Password"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_windows.rst:78
msgid "``GODOT_WINDOWS_CODESIGN_PASSWORD``"
msgstr ""

#: ../../docs/tutorials/export/changing_application_icon_for_windows.rst:4
msgid "Changing application icon for Windows"
msgstr ""

#: ../../docs/tutorials/export/changing_application_icon_for_windows.rst:6
msgid ""
"By default, the exported project's icon will be the Godot icon. You will "
"most likely want to change that for your project. There are two types of "
"icons that can be changed on Windows: the file icon and the taskbar icon."
msgstr ""

#: ../../docs/tutorials/export/changing_application_icon_for_windows.rst:11
#, fuzzy
msgid "Creating an ICO file"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/export/changing_application_icon_for_windows.rst:13
msgid ""
"Windows does not use formats such as png or jpg for application icons. "
"Instead, it uses a Windows-only format called ICO. You can create your "
"application icon in any program but you will have to convert it to an ICO "
"file using a program such as GIMP."
msgstr ""

#: ../../docs/tutorials/export/changing_application_icon_for_windows.rst:18
msgid ""
"`This video tutorial <https://www.youtube.com/watch?v=uqV3UfM-n5Y>`_ goes "
"over how to export an ICO file with GIMP."
msgstr ""

#: ../../docs/tutorials/export/changing_application_icon_for_windows.rst:21
msgid ""
"It is also possible to convert a PNG image to an hiDPI-friendly ICO file "
"using this `ImageMagick <https://www.imagemagick.org/>`_ command:"
msgstr ""

#: ../../docs/tutorials/export/changing_application_icon_for_windows.rst:28
msgid ""
"Depending on which version of ImageMagick you installed, you might need to "
"leave out the ``magick`` and run this command instead:"
msgstr ""

#: ../../docs/tutorials/export/changing_application_icon_for_windows.rst:36
msgid ""
"For the ICO file to effectively replace the default Godot icon, it must "
"contain *all* the sizes included in the default Godot icon: 16×16, 32×32, "
"48×48, 64×64, 128×128, 256×256. If the ICO file does not contain all the "
"sizes, the default Godot icon will be kept for the sizes that weren't "
"overridden."
msgstr ""

#: ../../docs/tutorials/export/changing_application_icon_for_windows.rst:41
msgid "The above ImageMagick command takes this into account."
msgstr ""

#: ../../docs/tutorials/export/changing_application_icon_for_windows.rst:44
msgid "Changing the taskbar icon"
msgstr ""

#: ../../docs/tutorials/export/changing_application_icon_for_windows.rst:46
msgid ""
"The taskbar icon is the icon that shows up on the taskbar when your project "
"is running."
msgstr ""

#: ../../docs/tutorials/export/changing_application_icon_for_windows.rst:51
msgid ""
"To change the taskbar icon, go to **Project → Project Settings → Application "
"→ Config → Windows Native Icon**. Click on the folder icon and select your "
"ICO file."
msgstr ""

#: ../../docs/tutorials/export/changing_application_icon_for_windows.rst:57
msgid ""
"This setting only changes the icon for your exported game on Windows. To set "
"the icon for macOS, use ``Macos Native Icon``. And for any other platform, "
"use the ``Icon`` setting."
msgstr ""

#: ../../docs/tutorials/export/changing_application_icon_for_windows.rst:62
msgid "Changing the file icon"
msgstr ""

#: ../../docs/tutorials/export/changing_application_icon_for_windows.rst:64
msgid ""
"In Godot 3.5 and later, you can change the file icon without external tools "
"using `godoticon <https://github.com/pkowal1982/godoticon>`__. Changing the "
"file icon this way should work for executables containing an embedded PCK."
msgstr ""

#: ../../docs/tutorials/export/changing_application_icon_for_windows.rst:71
msgid ""
"There are `known issues <https://github.com/godotengine/godot/"
"issues/33466>`__ when changing the application icon in executables that "
"embed a PCK file. It's recommended to avoid using rcedit for now if you "
"choose to enable the **Embed Pck** option for your Windows export preset in "
"the Export dialog."
msgstr ""

#: ../../docs/tutorials/export/changing_application_icon_for_windows.rst:76
msgid ""
"The file icon is the icon of the executable that you click on to start the "
"project."
msgstr ""

#: ../../docs/tutorials/export/changing_application_icon_for_windows.rst:81
msgid ""
"Before selecting it in the export options, you will need to install an extra "
"tool called **rcedit**. You can download it `here <https://github.com/"
"electron/rcedit/releases>`_."
msgstr ""

#: ../../docs/tutorials/export/changing_application_icon_for_windows.rst:85
msgid ""
"After downloading, you need to tell Godot the path to the rcedit executable "
"on your computer. Go to **Editor → Editor Settings → Export → Windows**. "
"Click on the folder icon for the **rcedit** entry. Navigate to and select "
"the rcedit executable."
msgstr ""

#: ../../docs/tutorials/export/changing_application_icon_for_windows.rst:93
msgid ""
"Linux and macOS users will also need to install `WINE <https://www.winehq."
"org/>`_ to use rcedit."
msgstr ""

#: ../../docs/tutorials/export/changing_application_icon_for_windows.rst:96
msgid ""
"On macOS 10.15 (Catalina) or later, make sure to use a 64-bit version of "
"both WINE and rcedit since 32-bit applications aren't supported anymore."
msgstr ""

#: ../../docs/tutorials/export/changing_application_icon_for_windows.rst:101
msgid ""
"You should now have everything in place to change the file icon. To do that, "
"you will need to specify the icon when exporting. Go to **Project → "
"Export**. Assuming you have already created a Windows Desktop preset, select "
"your icon in ICO format in the **Application → Icon** field."
msgstr ""

#: ../../docs/tutorials/export/changing_application_icon_for_windows.rst:109
msgid ""
"All the supplied metadata must be valid. Most importantly, the version "
"identifiers **must** take the form ``major.minor.patch.revision`` where "
"every component is required and is a positive integer. For instance, "
"``1.2.0.0`` is valid but ``1.2.0`` is not."
msgstr ""

#: ../../docs/tutorials/export/changing_application_icon_for_windows.rst:114
msgid ""
"If you provide invalid metadata in the export preset, the application icon "
"won't change as rcedit will fail to change the executable's metadata."
msgstr ""

#: ../../docs/tutorials/export/changing_application_icon_for_windows.rst:121
msgid ""
"If rcedit fails to change the icon, you can instead :ref:`compile your own "
"Windows export templates <doc_compiling_for_windows>` with the icon changed. "
"To do so, replace `platform/windows/godot.ico <https://github.com/"
"godotengine/godot/blob/master/platform/windows/godot.ico>`__ with your own "
"ICO file *before* compiling export templates."
msgstr ""

#: ../../docs/tutorials/export/changing_application_icon_for_windows.rst:127
msgid ""
"Once this is done, you can specify your export templates as custom export "
"templates in your project's Windows export preset."
msgstr ""

#: ../../docs/tutorials/export/changing_application_icon_for_windows.rst:131
msgid "Testing the result"
msgstr ""

#: ../../docs/tutorials/export/changing_application_icon_for_windows.rst:133
msgid ""
"You can now export the project. If it worked correctly, you should see this:"
msgstr ""

#: ../../docs/tutorials/export/changing_application_icon_for_windows.rst:139
msgid ""
"If your icon isn't showing up properly, on Windows 10, try clearing the icon "
"cache. To do so, open the **Run** dialog and enter ``ie4uinit.exe -"
"ClearIconCache`` or ``ie4uinit.exe -show``."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_ios.rst:4
msgid "Exporting for iOS"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_ios.rst:8
msgid ""
"This page describes how to export a Godot project to iOS. If you're looking "
"to compile export template binaries from source instead, read :ref:"
"`doc_compiling_for_ios`."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_ios.rst:12
msgid ""
"These are the steps to load a Godot project in Xcode. This allows you to "
"build and deploy to an iOS device, build a release for the App Store, and do "
"everything else you can normally do with Xcode."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_ios.rst:18
msgid ""
"Projects written in C# can be exported to iOS as of Godot 4.2, but support "
"is experimental and :ref:`some limitations apply <doc_c_sharp_platforms>`."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_ios.rst:24
msgid ""
"You must export for iOS from a computer running macOS with Xcode installed."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_ios.rst:25
msgid ""
"Download the Godot export templates. Use the Godot menu: Editor > Manage "
"Export Templates"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_ios.rst:28
msgid "Export a Godot project to Xcode"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_ios.rst:30
msgid ""
"In the Godot editor, open the **Export** window from the **Project** menu. "
"When the Export window opens, click **Add..** and select **iOS**."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_ios.rst:33
msgid ""
"The **App Store Team ID** and (Bundle) **Identifier** options in the "
"**Application** category are required. Leaving them blank will cause the "
"exporter to throw an error."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_ios.rst:0
msgid "If you encounter an error during export similar to"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_ios.rst:0
msgid ""
"``JSON text did not start with array or object and option to allow fragments "
"not set``"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_ios.rst:0
msgid "then it might be due to a malformated **App Store Team ID**!"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_ios.rst:0
msgid ""
"The exporter expects a (10 characters long) code like ``ABCDE12XYZ`` and "
"not, e.g., your name as Xcode likes to display in the *Signing & "
"Capabilities* tab."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_ios.rst:0
msgid ""
"You can find the code over at `developer.apple.com <https://developer.apple."
"com/account/resources/certificates/list>`_ next to your name in the top "
"right corner."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_ios.rst:42
msgid ""
"After you click **Export Project**, there are still two important options "
"left:"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_ios.rst:44
msgid ""
"**Path** is an empty folder that will contain the exported Xcode project "
"files."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_ios.rst:45
msgid ""
"**File** will be the name of the Xcode project and several project specific "
"files and directories."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_ios.rst:49
msgid ""
"This tutorial uses **exported_xcode_project_name**, but you will use your "
"project's name. When you see **exported_xcode_project_name** in the "
"following steps, replace it with the name you used instead."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_ios.rst:53
msgid ""
"Avoid using spaces when you choose your **exported_xcode_project_name** as "
"this can lead to corruption in your XCode project file."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_ios.rst:56
msgid "When the export completes, the output folder should look like this:"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_ios.rst:60
msgid ""
"Opening **exported_xcode_project_name.xcodeproj** lets you build and deploy "
"like any other iOS app."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_ios.rst:64
msgid "Active development considerations"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_ios.rst:66
msgid ""
"The above method creates an exported project that you can build for release, "
"but you have to re-export every time you make a change in Godot."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_ios.rst:69
msgid ""
"While developing, you can speed this process up by linking your Godot "
"project files directly into your app."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_ios.rst:72
msgid "In the following example:"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_ios.rst:74
msgid ""
"**exported_xcode_project_name** is the name of the exported iOS application "
"(as above)."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_ios.rst:75
msgid "**godot_project_to_export** is the name of the Godot project."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_ios.rst:77
msgid ""
"**godot_project_to_export** must not be the same as "
"**exported_xcode_project_name** to prevent signing issues in Xcode."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_ios.rst:81
msgid "Steps to link a Godot project folder to Xcode"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_ios.rst:83
msgid "Start from an exported iOS project (follow the steps above)."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_ios.rst:84
msgid "In Finder, drag the Godot project folder into the Xcode file browser."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_ios.rst:88
msgid ""
"3. In the dialog, make sure **Create folder references** is selected. This "
"means you will be able to continue to edit your Godot project in its current "
"location."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_ios.rst:93
msgid "See the **godot_project_to_export** folder in the Xcode file browser."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_ios.rst:94
msgid "Delete **exported_xcode_project_name.pck** from the Xcode project."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_ios.rst:98
msgid ""
"6. Open **exported_xcode_project_name-Info.plist** and add a string property "
"named **godot_path** (this is the real key name) with a value "
"**godot_project_to_export** (this is the name of your project)"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_ios.rst:104
msgid ""
"That's it! You can now edit your project in the Godot editor and build it in "
"Xcode when you want to run it on a device."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_ios.rst:108
#: ../../docs/tutorials/platform/ios/plugins_for_ios.rst:6
msgid "Plugins for iOS"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_ios.rst:110
msgid ""
"Special iOS plugins can be used in Godot. Check out the :ref:"
"`doc_plugins_for_ios` page."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_ios.rst:120
msgid "iOS export environment variables"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_ios.rst:127
msgid "Options / Application / Provisioning Profile UUID Debug"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_ios.rst:128
msgid "``GODOT_IOS_PROVISIONING_PROFILE_UUID_DEBUG``"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_ios.rst:129
msgid "Options / Application / Provisioning Profile UUID Release"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_ios.rst:130
msgid "``GODOT_IOS_PROVISIONING_PROFILE_UUID_RELEASE``"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_ios.rst:136
msgid "xcode-select points at wrong SDK location"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_ios.rst:138
msgid ""
"xcode-select is a tool that comes with Xcode and among other things points "
"at iOS SDKs on your Mac. If you have Xcode installed, opened it, agreed to "
"the license agreement, and installed the command line tools, xcode-select "
"should point at the right location for the iPhone SDK. If it somehow "
"doesn't, Godot will fail exporting to iOS with an error that may look like "
"this:"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_ios.rst:148
msgid ""
"In this case, Godot is trying to find the ``Platforms`` folder containing "
"the iPhone SDK inside the ``/Library/Developer/CommandLineTools/`` folder, "
"but the ``Platforms`` folder with the iPhone SDK is actually located under "
"``/Applications/Xcode.app/Contents/Developer``. To verify this, you can open "
"up Terminal and run the following command to see what xcode-select points at:"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_ios.rst:157
msgid ""
"To fix xcode-select pointing at a wrong location, enter this command in "
"Terminal:"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_ios.rst:163
msgid ""
"After running this command, Godot should be able to successfully export to "
"iOS."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_android.rst:4
msgid "Exporting for Android"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_android.rst:9
msgid ""
"This page describes how to export a Godot project to Android. If you're "
"looking to compile export template binaries from source instead, read :ref:"
"`doc_compiling_for_android`."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_android.rst:13
msgid ""
"Exporting for Android has fewer requirements than compiling Godot for "
"Android. The following steps detail what is needed to set up the Android SDK "
"and the engine."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_android.rst:18
msgid ""
"Projects written in C# can be exported to Android as of Godot 4.2, but "
"support is experimental and :ref:`some limitations apply "
"<doc_c_sharp_platforms>`."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_android.rst:22
#, fuzzy
msgid "Install OpenJDK 17"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/export/exporting_for_android.rst:24
msgid ""
"Download and install `OpenJDK 17 <https://adoptium.net/temurin/releases/?"
"variant=openjdk17>`__."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_android.rst:27
msgid "Download the Android SDK"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_android.rst:29
msgid "Download and install the Android SDK."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_android.rst:31
msgid ""
"You can install the Android SDK using `Android Studio version 4.1 or later "
"<https://developer.android.com/studio/>`__."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_android.rst:33
msgid ""
"Run it once to complete the SDK setup using these `instructions <https://"
"developer.android.com/studio/intro/update#sdk-manager>`__."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_android.rst:34
msgid ""
"Ensure that the `required packages <https://developer.android.com/studio/"
"intro/update#recommended>`__ are installed as well."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_android.rst:36
msgid "Android SDK Platform-Tools version 30.0.5 or later"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_android.rst:37
msgid "Android SDK Build-Tools version 33.0.2"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_android.rst:38
msgid "Android SDK Platform 33"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_android.rst:39
msgid "Android SDK Command-line Tools (latest)"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_android.rst:40
msgid "CMake version 3.10.2.4988404"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_android.rst:41
msgid "NDK version r23c (23.2.8568313)"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_android.rst:43
msgid ""
"Alternatively, you can install the Android SDK with the `sdkmanager` command "
"line tool."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_android.rst:45
msgid ""
"Install the command line tools package using these `instructions <https://"
"developer.android.com/tools/sdkmanager>`__."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_android.rst:46
msgid ""
"Once the command line tools are installed, run the following `sdkmanager` "
"command to complete the setup process:"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_android.rst:54
msgid ""
"If you are using Linux, **do not use an Android SDK provided by your "
"distribution's repositories as it will often be outdated**."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_android.rst:59
msgid "Create a debug.keystore"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_android.rst:61
msgid ""
"Android needs a debug keystore file to install to devices and distribute non-"
"release APKs. If you have used the SDK before and have built projects, ant "
"or eclipse probably generated one for you (in the ``~/.android`` directory "
"on Linux and macOS, in the ``C:\\Users\\<user>\\.android\\`` directory on "
"Windows)."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_android.rst:66
msgid ""
"If you can't find it or need to generate one, the keytool command from the "
"JDK can be used for this purpose::"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_android.rst:71
msgid ""
"This will create a ``debug.keystore`` file in your current directory. You "
"should move it to a memorable location such as ``%USERPROFILE%\\."
"android\\``, because you will need its location in a later step. For more "
"information on ``keytool`` usage, see `this Q&A article <https://ask."
"godotengine.org/21349/jdk-android-file-missing>`__."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_android.rst:75
msgid ""
"It is important that the password is the same for the keystore and the key. "
"This is a `known Android studio issue <https://developer.android.com/studio/"
"known-issues#ki-key-keystore-warning>`__ that also affects Godot projects."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_android.rst:80
msgid "Setting it up in Godot"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_android.rst:82
msgid ""
"Enter the Editor Settings screen. This screen contains the editor settings "
"for the user account in the computer (it's independent of the project)."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_android.rst:88
msgid "Scroll down to the section where the Android settings are located:"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_android.rst:92
msgid "In that screen, 2 paths need to be set:"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_android.rst:94
msgid ""
"The ``Android Sdk Path`` should be the location where the Android SDK was "
"installed. - For example ``%LOCALAPPDATA%\\Android\\Sdk\\`` on Windows or ``/"
"Users/$USER/Library/Android/sdk/`` on macOS."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_android.rst:97
msgid ""
"The debug ``.keystore`` file - It can be found in the folder where you put "
"the ``debug.keystore`` file you created above."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_android.rst:100
msgid "Once that is configured, everything is ready to export to Android!"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_android.rst:104
msgid ""
"If you get an error saying *\"Could not install to device.\"*, make sure you "
"do not have an application with the same Android package name already "
"installed on the device (but signed with a different key)."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_android.rst:108
msgid ""
"If you have an application with the same Android package name but a "
"different signing key already installed on the device, you **must** remove "
"the application in question from the Android device before exporting to "
"Android again."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_android.rst:114
msgid "Providing launcher icons"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_android.rst:116
msgid ""
"Launcher icons are used by Android launcher apps to represent your "
"application to users. Godot only requires high-resolution icons (for "
"``xxxhdpi`` density screens) and will automatically generate lower-"
"resolution variants."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_android.rst:118
#, fuzzy
msgid "There are two types of icons required by Godot:"
msgstr "Ne postoje ograničenja prilikom korištenja Godot-a"

#: ../../docs/tutorials/export/exporting_for_android.rst:120
msgid ""
"**Main Icon:** The \"classic\" icon. This will be used on all Android "
"versions up to Android 8 (Oreo), exclusive. Must be at least 192×192 px."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_android.rst:121
msgid ""
"**Adaptive Icons:** Starting from Android 8 (inclusive), `Adaptive Icons "
"<https://developer.android.com/guide/practices/ui_guidelines/"
"icon_design_adaptive>`_ were introduced. Applications will need to include "
"separate background and foreground icons to have a native look. The user's "
"launcher application will control the icon's animation and masking. Must be "
"at least 432×432 px."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_android.rst:123
msgid ""
"It's important to adhere to some rules when designing adaptive icons. "
"`Google Design has provided a nice article <https://medium.com/google-design/"
"designing-adaptive-icons-515af294c783>`_ that helps to understand those "
"rules and some of the capabilities of adaptive icons."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_android.rst:125
msgid ""
"The most important adaptive icon design rule is to have your icon critical "
"elements inside the safe zone: a centered circle with a diameter of 66dp "
"(264 pixels on ``xxxhdpi``) to avoid being clipped by the launcher."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_android.rst:127
msgid ""
"If you don't provide some of the requested icons, Godot will replace them "
"using a fallback chain, trying the next in line when the current one fails:"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_android.rst:129
msgid ""
"**Main Icon:** Provided main icon -> Project icon -> Default Godot main icon."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_android.rst:130
msgid ""
"**Adaptive Icon Foreground:** Provided foreground icon -> Provided main icon "
"-> Project icon -> Default Godot foreground icon."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_android.rst:131
msgid ""
"**Adaptive Icon Background:** Provided background icon -> Default Godot "
"background icon."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_android.rst:133
msgid ""
"It's highly recommended to provide all the requested icons with their "
"specified resolutions. This way, your application will look great on all "
"Android devices and versions."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_android.rst:137
msgid "Exporting for Google Play Store"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_android.rst:139
msgid ""
"Uploading an APK to Google's Play Store requires you to sign using a non-"
"debug keystore file; such file can be generated like this:"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_android.rst:146
msgid ""
"This keystore and key are used to verify your developer identity, remember "
"the password and keep it in a safe place! Use Google's Android Developer "
"guides to learn more about `APK signing <https://developer.android.com/"
"studio/publish/app-signing>`__."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_android.rst:149
msgid "Now fill in the following forms in your Android Export Presets:"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_android.rst:153
msgid "**Release:** Enter the path to the keystore file you just generated."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_android.rst:154
msgid "**Release User:** Replace with the key alias."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_android.rst:155
msgid ""
"**Release Password:** Key password. Note that the keystore password and the "
"key password currently have to be the same."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_android.rst:157
msgid ""
"Don't forget to uncheck the **Export With Debug** checkbox while exporting."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_android.rst:162
msgid "Optimizing the APK size"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_android.rst:164
msgid ""
"By default, the APK will contain native libraries for both ARMv7 and ARMv8 "
"architectures. This increases its size significantly. To create a smaller "
"APK, uncheck either **Armeabi-v 7a** or **Arm 64 -v 8a** in your project's "
"Android export preset. This will create an APK that only contains a library "
"for a single architecture. Note that applications targeting ARMv7 can also "
"run on ARMv8 devices, but the opposite is not true."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_android.rst:171
msgid ""
"Since August 2019, Google Play requires all applications to be available in "
"64-bit form. This means you cannot upload an APK that contains *just* an "
"ARMv7 library. To solve this, you can upload several APKs to Google Play "
"using its `Multiple APK support <https://developer.android.com/google/play/"
"publishing/multiple-apks>`__. Each APK should target a single architecture; "
"creating an APK for ARMv7 and ARMv8 is usually sufficient to cover most "
"devices in use today."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_android.rst:178
msgid ""
"You can optimize the size further by compiling an Android export template "
"with only the features you need. See :ref:`doc_optimizing_for_size` for more "
"information."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_android.rst:189
msgid "Android export environment variables"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_android.rst:196
msgid "Options / Keystore / Debug"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_android.rst:197
msgid "``GODOT_ANDROID_KEYSTORE_DEBUG_PATH``"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_android.rst:198
msgid "Options / Keystore / Debug User"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_android.rst:199
msgid "``GODOT_ANDROID_KEYSTORE_DEBUG_USER``"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_android.rst:200
msgid "Options / Keystore / Debug Password"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_android.rst:201
msgid "``GODOT_ANDROID_KEYSTORE_DEBUG_PASSWORD``"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_android.rst:202
msgid "Options / Keystore / Release"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_android.rst:203
msgid "``GODOT_ANDROID_KEYSTORE_RELEASE_PATH``"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_android.rst:204
msgid "Options / Keystore / Release User"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_android.rst:205
msgid "``GODOT_ANDROID_KEYSTORE_RELEASE_USER``"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_android.rst:206
msgid "Options / Keystore / Release Password"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_android.rst:207
msgid "``GODOT_ANDROID_KEYSTORE_RELEASE_PASSWORD``"
msgstr ""

#: ../../docs/tutorials/export/android_gradle_build.rst:4
msgid "Gradle builds for Android"
msgstr ""

#: ../../docs/tutorials/export/android_gradle_build.rst:6
msgid ""
"Godot provides the option to build using the gradle buildsystem. Instead of "
"using the already pre-built template that ships with Godot, an Android Java "
"project gets installed into your project folder. Godot will then build it "
"and use it as an export template every time you export the project."
msgstr ""

#: ../../docs/tutorials/export/android_gradle_build.rst:11
msgid "There are some reasons why you may want to do this:"
msgstr ""

#: ../../docs/tutorials/export/android_gradle_build.rst:13
msgid "Modify the project before it's built."
msgstr ""

#: ../../docs/tutorials/export/android_gradle_build.rst:14
msgid "Add external SDKs that build with your project."
msgstr ""

#: ../../docs/tutorials/export/android_gradle_build.rst:16
msgid ""
"Configuring the gradle build is a fairly straightforward process. But first "
"you need to follow the steps in :ref:`exporting for "
"android<doc_exporting_for_android>` up to **Setting it up in Godot**. After "
"doing that, follow the steps below."
msgstr ""

#: ../../docs/tutorials/export/android_gradle_build.rst:21
msgid "Set up the gradle build environment"
msgstr ""

#: ../../docs/tutorials/export/android_gradle_build.rst:23
msgid "Go to the Project menu, and install the *Gradle Build* template:"
msgstr ""

#: ../../docs/tutorials/export/android_gradle_build.rst:27
msgid ""
"Make sure export templates are downloaded. If not, this menu will help you "
"download them."
msgstr ""

#: ../../docs/tutorials/export/android_gradle_build.rst:30
msgid ""
"A Gradle-based Android project will be created under ``res://android/"
"build``. Editing these files is not needed unless you really need to modify "
"the project."
msgstr ""

#: ../../docs/tutorials/export/android_gradle_build.rst:35
msgid "Enabling the gradle build and exporting"
msgstr ""

#: ../../docs/tutorials/export/android_gradle_build.rst:37
msgid ""
"When setting up the Android project in the **Project > Export** dialog, "
"**Gradle Build** needs to be enabled:"
msgstr ""

#: ../../docs/tutorials/export/android_gradle_build.rst:42
msgid ""
"From now on, attempting to export the project or one-click deploy will call "
"the `Gradle <https://gradle.org/>`__ build system to generate fresh "
"templates (this window will appear every time):"
msgstr ""

#: ../../docs/tutorials/export/android_gradle_build.rst:48
msgid ""
"The templates built will be used automatically afterwards, so no further "
"configuration is needed."
msgstr ""

#: ../../docs/tutorials/export/android_gradle_build.rst:53
msgid ""
"When using the gradle Android build system, assets that are placed within a "
"folder whose name begins with an underscore will not be included in the "
"generated APK. This does not apply to assets whose *file* name begins with "
"an underscore."
msgstr ""

#: ../../docs/tutorials/export/android_gradle_build.rst:58
msgid ""
"For example, ``_example/image.png`` will **not** be included as an asset, "
"but ``_image.png`` will."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_web.rst:4
msgid "Exporting for the Web"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_web.rst:8
msgid ""
"This page describes how to export a Godot project to HTML5. If you're "
"looking to compile editor or export template binaries from source instead, "
"read :ref:`doc_compiling_for_web`."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_web.rst:12
msgid ""
"HTML5 export allows publishing games made in Godot Engine to the browser. "
"This requires support for `WebAssembly <https://webassembly.org/>`__, `WebGL "
"<https://www.khronos.org/webgl/>`__ and `SharedArrayBuffer <https://"
"developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/"
"SharedArrayBuffer>`_ in the user's browser."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_web.rst:20
msgid ""
"Projects written in C# using Godot 4 currently cannot be exported to the "
"web. To use C# on web platforms, use Godot 3 instead."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_web.rst:25
msgid ""
"Use the browser-integrated developer console, usually opened with :kbd:`F12` "
"(:kbd:`Cmd + Option + I` on macOS), to view **debug information** like "
"JavaScript, engine, and WebGL errors."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_web.rst:31
msgid ""
"Godot 4's HTML5 exports currently cannot run on macOS and iOS due to "
"upstream bugs with SharedArrayBuffer and WebGL 2.0. We recommend using :ref:"
"`macOS <doc_exporting_for_macos>` and :ref:`iOS <doc_exporting_for_ios>` "
"native export functionality instead, as it will also result in better "
"performance."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_web.rst:36
msgid ""
"Godot 3's HTML5 exports are more compatible with various browsers in "
"general, especially when using the GLES2 rendering backend (which only "
"requires WebGL 1.0)."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_web.rst:41
msgid "WebGL version"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_web.rst:43
msgid ""
"Godot 4.0 and later can only target WebGL 2.0 (using the Compatibility "
"rendering method). There is no stable way to run Vulkan applications on the "
"web yet."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_web.rst:46
msgid ""
"See `Can I use WebGL 2.0 <https://caniuse.com/webgl2>`__ for a list of "
"browser versions supporting WebGL 2.0. Note that Safari has several issues "
"with WebGL 2.0 support that other browsers don't have, so we recommend using "
"a Chromium-based browser or Firefox if possible."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_web.rst:54
msgid "Export options"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_web.rst:56
msgid ""
"If a runnable web export template is available, a button appears between the "
"*Stop scene* and *Play edited Scene* buttons in the editor to quickly open "
"the game in the default browser for testing."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_web.rst:60
msgid ""
"If you plan to use :ref:`VRAM compression <doc_importing_images>` make sure "
"that **Vram Texture Compression** is enabled for the targeted platforms "
"(enabling both **For Desktop** and **For Mobile** will result in a bigger, "
"but more compatible export)."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_web.rst:65
msgid ""
"If a path to a **Custom HTML shell** file is given, it will be used instead "
"of the default HTML page. See :ref:`doc_customizing_html5_shell`."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_web.rst:68
msgid ""
"**Head Include** is appended into the ``<head>`` element of the generated "
"HTML page. This allows to, for example, load webfonts and third-party "
"JavaScript APIs, include CSS, or run JavaScript code."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_web.rst:72
msgid ""
"Each project must generate their own HTML file. On export, several text "
"placeholders are replaced in the generated HTML file specifically for the "
"given export options. Any direct modifications to that HTML file will be "
"lost in future exports. To customize the generated file, use the **Custom "
"HTML shell** option."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_web.rst:82
msgid ""
"For security and privacy reasons, many features that work effortlessly on "
"native platforms are more complicated on the web platform. Following is a "
"list of limitations you should be aware of when porting a Godot game to the "
"web."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_web.rst:88
msgid ""
"Browser vendors are making more and more functionalities only available in "
"`secure contexts <https://developer.mozilla.org/en-US/docs/Web/Security/"
"Secure_Contexts>`_, this means that such features are only be available if "
"the web page is served via a secure HTTPS connection (localhost is usually "
"exempt from such requirement)."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_web.rst:95
msgid "Using cookies for data persistence"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_web.rst:97
msgid ""
"Users must **allow cookies** (specifically IndexedDB) if persistence of the "
"``user://`` file system is desired. When playing a game presented in an "
"``iframe``, **third-party** cookies must also be enabled. Incognito/private "
"browsing mode also prevents persistence."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_web.rst:102
msgid ""
"The method ``OS.is_userfs_persistent()`` can be used to check if the "
"``user://`` file system is persistent, but can give false positives in some "
"cases."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_web.rst:107
msgid "Background processing"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_web.rst:109
msgid ""
"The project will be paused by the browser when the tab is no longer the "
"active tab in the user's browser. This means functions such as "
"``_process()`` and ``_physics_process()`` will no longer run until the tab "
"is made active again by the user (by switching back to the tab). This can "
"cause networked games to disconnect if the user switches tabs for a long "
"duration."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_web.rst:115
msgid ""
"This limitation does not apply to unfocused browser *windows*. Therefore, on "
"the user's side, this can be worked around by running the project in a "
"separate *window* instead of a separate tab."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_web.rst:120
msgid "Full screen and mouse capture"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_web.rst:122
msgid ""
"Browsers do not allow arbitrarily **entering full screen**. The same goes "
"for **capturing the cursor**. Instead, these actions have to occur as a "
"response to a JavaScript input event. In Godot, this means entering full "
"screen from within a pressed input event callback such as ``_input`` or "
"``_unhandled_input``. Querying the :ref:`class_Input` singleton is not "
"sufficient, the relevant input event must currently be active."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_web.rst:129
msgid ""
"For the same reason, the full screen project setting doesn't work unless the "
"engine is started from within a valid input event handler. This requires :"
"ref:`customization of the HTML page <doc_customizing_html5_shell>`."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_web.rst:136
msgid ""
"Some browsers restrict autoplay for audio on websites. The easiest way "
"around this limitation is to request the player to click, tap or press a key/"
"button to enable audio, for instance when displaying a splash screen at the "
"start of your game."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_web.rst:139
msgid ""
"Google offers additional information about their `Web Audio autoplay "
"policies <https://sites.google.com/a/chromium.org/dev/audio-video/"
"autoplay>`__."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_web.rst:142
msgid ""
"Apple's Safari team also posted additional information about their `Auto-"
"Play Policy Changes for macOS <https://webkit.org/blog/7734/auto-play-policy-"
"changes-for-macos/>`__."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_web.rst:145
msgid ""
"Access to microphone requires a :ref:`secure context "
"<doc_javascript_secure_contexts>`."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_web.rst:151
msgid ""
"Low level networking is not implemented due to lacking support in browsers."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_web.rst:153
msgid ""
"Currently, only :ref:`HTTP client <doc_http_client_class>`, :ref:`HTTP "
"requests <doc_http_request_class>`, :ref:`WebSocket (client) "
"<doc_websocket>` and :ref:`WebRTC <doc_webrtc>` are supported."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_web.rst:158
msgid "The HTTP classes also have several restrictions on the HTML5 platform:"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_web.rst:160
msgid "Accessing or changing the ``StreamPeer`` is not possible"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_web.rst:161
msgid "Threaded/Blocking mode is not available"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_web.rst:162
msgid ""
"Cannot progress more than once per frame, so polling in a loop will freeze"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_web.rst:163
msgid "No chunked responses"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_web.rst:164
msgid "Host verification cannot be disabled"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_web.rst:165
msgid ""
"Subject to `same-origin policy <https://developer.mozilla.org/en-US/docs/Web/"
"Security/Same-origin_policy>`__"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_web.rst:168
msgid "Clipboard"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_web.rst:170
msgid ""
"Clipboard synchronization between engine and the operating system requires a "
"browser supporting the `Clipboard API <https://developer.mozilla.org/en-US/"
"docs/Web/API/Clipboard_API>`__, additionally, due to the API asynchronous "
"nature might not be reliable when accessed from GDScript."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_web.rst:175
#: ../../docs/tutorials/export/exporting_for_web.rst:186
msgid "Requires a :ref:`secure context <doc_javascript_secure_contexts>`."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_web.rst:178
msgid "Gamepads"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_web.rst:180
msgid ""
"Gamepads will not be detected until one of their button is pressed. Gamepads "
"might have the wrong mapping depending on the browser/OS/gamepad "
"combination, sadly the `Gamepad API <https://developer.mozilla.org/en-US/"
"docs/Web/API/Gamepad_API/Using_the_Gamepad_API>`__ does not provide a "
"reliable way to detect the gamepad information necessary to remap them based "
"on model/vendor/OS due to privacy considerations."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_web.rst:189
msgid "Boot splash is not displayed"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_web.rst:191
msgid ""
"The default HTML page does not display the boot splash while loading. "
"However, the image is exported as a PNG file, so :ref:`custom HTML pages "
"<doc_customizing_html5_shell>` can display it."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_web.rst:198
msgid "Serving the files"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_web.rst:200
msgid ""
"Exporting for the web generates several files to be served from a web "
"server, including a default HTML page for presentation. A custom HTML file "
"can be used, see :ref:`doc_customizing_html5_shell`."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_web.rst:206
msgid ""
"To ensure low audio latency and the ability to use :ref:`class_Thread` in "
"web exports, Godot 4 web exports always use `SharedArrayBuffer <https://"
"developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/"
"SharedArrayBuffer>`__. This requires a :ref:`secure context "
"<doc_javascript_secure_contexts>`, while also requiring the following CORS "
"headers to be set when serving the files:"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_web.rst:217
msgid ""
"If you don't control the web server or are unable to add response headers, "
"use `coi-serviceworker <https://github.com/gzuidhof/coi-serviceworker>`__ as "
"a workaround."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_web.rst:221
msgid ""
"If the client doesn't receive the required response headers, **the project "
"will not run**."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_web.rst:224
msgid ""
"The generated ``.html`` file can be used as ``DirectoryIndex`` in Apache "
"servers and can be renamed to e.g. ``index.html`` at any time. Its name is "
"never depended on by default."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_web.rst:228
msgid ""
"The HTML page draws the game at maximum size within the browser window. This "
"way, it can be inserted into an ``<iframe>`` with the game's size, as is "
"common on most web game hosting sites."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_web.rst:232
msgid ""
"The other exported files are served as they are, next to the ``.html`` file, "
"names unchanged. The ``.wasm`` file is a binary WebAssembly module "
"implementing the engine. The ``.pck`` file is the Godot main pack containing "
"your game. The ``.js`` file contains start-up code and is used by the ``."
"html`` file to access the engine. The ``.png`` file contains the boot splash "
"image. It is not used in the default HTML page, but is included for :ref:"
"`custom HTML pages <doc_customizing_html5_shell>`."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_web.rst:240
msgid ""
"The ``.pck`` file is binary, usually delivered with the MIME-type :mimetype:"
"`application/octet-stream`. The ``.wasm`` file is delivered as :mimetype:"
"`application/wasm`."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_web.rst:246
msgid ""
"Delivering the WebAssembly module (``.wasm``) with a MIME-type other than :"
"mimetype:`application/wasm` can prevent some start-up optimizations."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_web.rst:250
msgid ""
"Delivering the files with server-side compression is recommended especially "
"for the ``.pck`` and ``.wasm`` files, which are usually large in size. The "
"WebAssembly module compresses particularly well, down to around a quarter of "
"its original size with gzip compression. Consider using Brotli "
"precompression if supported on your web server for further file size savings."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_web.rst:256
msgid "**Hosts that provide on-the-fly compression:** GitHub Pages (gzip)"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_web.rst:258
msgid ""
"**Hosts that don't provide on-the-fly compression:** itch.io, GitLab Pages "
"(`supports manual gzip precompression <https://webd97.de/post/gitlab-pages-"
"compression/>`__)"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_web.rst:263
msgid ""
"The Godot repository includes a `Python script to host a local web server "
"<https://raw.githubusercontent.com/godotengine/godot/master/platform/web/"
"serve.py>`__. This script is intended for testing the web editor, but it can "
"also be used to test exported projects."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_web.rst:267
msgid ""
"Save the linked script to a file called ``serve.py``, move this file to the "
"folder containing the exported project's ``index.html``, then run the "
"following command in a command prompt within the same folder:"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_web.rst:276
msgid ""
"On Windows, you can open a command prompt in the current folder by holding :"
"kbd:`Shift` and right-clicking on empty space in Windows Explorer, then "
"choosing **Open PowerShell window here**."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_web.rst:280
msgid ""
"This will serve the contents of the current folder and open the default web "
"browser automatically."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_web.rst:283
#: ../../docs/contributing/development/compiling/compiling_for_web.rst:125
msgid ""
"Note that for production use cases, this Python-based web server should not "
"be used. Instead, you should use an established web server such as Apache or "
"nginx."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_web.rst:290
msgid "Calling JavaScript from script"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_web.rst:292
msgid ""
"In web builds, the ``JavaScriptBridge`` singleton is implemented. It offers "
"a single method called ``eval`` that works similarly to the JavaScript "
"function of the same name. It takes a string as an argument and executes it "
"as JavaScript code. This allows interacting with the browser in ways not "
"possible with script languages integrated into Godot."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_web.rst:311
msgid ""
"The value of the last JavaScript statement is converted to a GDScript value "
"and returned by ``eval()`` under certain circumstances:"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_web.rst:314
msgid "JavaScript ``number`` is returned as :ref:`class_float`"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_web.rst:315
msgid "JavaScript ``boolean`` is returned as :ref:`class_bool`"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_web.rst:316
msgid "JavaScript ``string`` is returned as :ref:`class_String`"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_web.rst:317
msgid ""
"JavaScript ``ArrayBuffer``, ``TypedArray`` and ``DataView`` are returned as :"
"ref:`PackedByteArray<class_PackedByteArray>`"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_web.rst:334
msgid "Any other JavaScript value is returned as ``null``."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_web.rst:336
msgid ""
"HTML5 export templates may be :ref:`built <doc_compiling_for_web>` without "
"support for the singleton to improve security. With such templates, and on "
"platforms other than HTML5, calling ``JavaScriptBridge.eval`` will also "
"return ``null``. The availability of the singleton can be checked with the "
"``web`` :ref:`feature tag <doc_feature_tags>`:"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_web.rst:367
msgid ""
"GDScript's multi-line strings, surrounded by 3 quotes ``\"\"\"`` as in "
"``my_func3()`` above, are useful to keep JavaScript code readable."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_web.rst:370
msgid ""
"The ``eval`` method also accepts a second, optional Boolean argument, which "
"specifies whether to execute the code in the global execution context, "
"defaulting to ``false`` to prevent polluting the global namespace:"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_web.rst:398
msgid "HTML5 export environment variables"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_dedicated_servers.rst:4
#: ../../docs/tutorials/networking/high_level_multiplayer.rst:409
msgid "Exporting for dedicated servers"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_dedicated_servers.rst:6
msgid ""
"If you want to run a dedicated server for your project on a machine that "
"doesn't have a GPU or display server available, you'll need to run Godot "
"with the ``headless`` display server and ``Dummy`` :ref:`audio driver "
"<class_ProjectSettings_property_audio/driver/driver>`."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_dedicated_servers.rst:10
msgid ""
"Since Godot 4.0, this can be done by running a Godot binary on any platform "
"with the ``--headless`` command line argument, or running a project exported "
"as dedicated server. You do not need to use a specialized server binary "
"anymore, unlike Godot 3.x."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_dedicated_servers.rst:16
#, fuzzy
msgid "Editor versus export template"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/export/exporting_for_dedicated_servers.rst:18
msgid ""
"It is possible to use either an editor or export template (debug or release) "
"binary in headless mode. Which one you should use depends on your use case:"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_dedicated_servers.rst:21
msgid ""
"**Export template:** Use this one for running dedicated servers. It does not "
"contain editor functionality, and is therefore smaller and more optimized."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_dedicated_servers.rst:23
msgid ""
"**Editor:** This binary contains editor functionality and is intended to be "
"used for exporting projects. This binary *can* be used to run dedicated "
"servers, but it's not recommended as it's larger and less optimized."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_dedicated_servers.rst:28
msgid "Export approaches"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_dedicated_servers.rst:30
#, fuzzy
msgid "There are two ways to export a project for a server:"
msgstr "Ne postoje ograničenja prilikom korištenja Godot-a"

#: ../../docs/tutorials/export/exporting_for_dedicated_servers.rst:32
msgid ""
"Create a separate export preset for the platform that will host the server, "
"then export your project as usual."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_dedicated_servers.rst:34
msgid ""
"Export a PCK file only, preferably for the platform that matches the "
"platform that will host the server. Place this PCK file in the same folder "
"as an export template binary, rename the binary to have the same name as the "
"PCK (minus the file extension), then run the binary."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_dedicated_servers.rst:39
msgid ""
"Both methods should result in identical output. The rest of the page will "
"focus on the first approach."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_dedicated_servers.rst:42
msgid "See :ref:`doc_exporting_projects` for more information."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_dedicated_servers.rst:47
#, fuzzy
msgid "Exporting a project for a dedicated server"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/export/exporting_for_dedicated_servers.rst:49
msgid ""
"If you export a project as usual when targeting a server, you will notice "
"that the PCK file is just as large as for the client. This is because it "
"includes all resources, including those the server doesn't need (such as "
"texture data). Additionally, headless mode won't be automatically used; the "
"user will have to specify ``--headless`` to make sure no window spawns."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_dedicated_servers.rst:55
msgid ""
"Many resources such as textures can be stripped from the PCK file to greatly "
"reduce its size. Godot offers a way to do this for textures and materials in "
"a way that preserves references in scene or resource files (built-in or "
"external)."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_dedicated_servers.rst:59
msgid ""
"To begin doing so, make sure you have a dedicated export preset for your "
"server, then select it, go to its **Resources** tab and change its export "
"mode:"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_dedicated_servers.rst:66
msgid ""
"Choosing the **Export as dedicated server** export mode in the export preset"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_dedicated_servers.rst:68
msgid ""
"When this export mode is chosen, the ``dedicated_server`` feature tag is "
"automatically added to the exported project."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_dedicated_servers.rst:73
msgid ""
"If you do not wish to use this export mode but still want the feature tag, "
"you can write the name ``dedicated_server`` in the **Features** tab of the "
"export preset. This will also force ``--headless`` when running the exported "
"project."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_dedicated_servers.rst:78
msgid ""
"After selecting this export mode, you will be presented with a list of "
"resources in the project:"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_dedicated_servers.rst:85
msgid "Choosing resources to keep, keep with stripped visuals or remove"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_dedicated_servers.rst:87
msgid ""
"Ticking a box allows you to override options for the specified file or "
"folder. Checking boxes does **not** affect which files are exported; this is "
"done by the options selected for each checkbox instead."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_dedicated_servers.rst:91
msgid ""
"Files within a checked folder will automatically use the parent's option by "
"default, which is indicated by the **(Inherited)** suffix for the option "
"name (and the option name being grayed out). To change the option for a file "
"whose option is currently inherited, you must tick the box next to it first."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_dedicated_servers.rst:96
msgid ""
"**Strip Visuals:** Export this resource, with visual files (textures and "
"materials) replaced by placeholder classes. Placeholder classes store the "
"image size (as it's sometimes used to position elements in a 2D scene), but "
"nothing else."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_dedicated_servers.rst:99
msgid "**Keep:** Export this resource as usual, with visual files intact."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_dedicated_servers.rst:100
msgid ""
"**Remove:** The file is not included in the PCK. This is useful to ignore "
"scenes and resources that only the client needs. If you do so, make sure the "
"server doesn't reference these client-only scenes and resources in any way."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_dedicated_servers.rst:104
msgid ""
"The general recommendation is to use **Strip Visuals** whenever possible, "
"unless the server needs to access image data such as pixels' colors. For "
"example, if your server generates collision data based on an image's "
"contents, you need to use **Keep** for that particular image."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_dedicated_servers.rst:111
msgid ""
"To check the file structure of your exported PCK, use the **Export PCK/ZIP..."
"** button with a ``.zip`` file extension, then open the resulting ZIP file "
"in a file manager."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_dedicated_servers.rst:117
msgid ""
"Be careful when using the **Remove** mode, as scenes/resources that "
"reference a removed file will no longer be able to load successfully."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_dedicated_servers.rst:120
msgid ""
"If you wish to remove specific resources but make the scenes still be able "
"to load without them, you'll have to remove the reference in the scene file "
"and load the files to the nodes' properties using ``load()`` in a script. "
"This approach can be used to strip resources that Godot doesn't support "
"replacing with placeholders yet, such as audio."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_dedicated_servers.rst:126
msgid ""
"Removing textures is often what makes the greatest impact on the PCK size, "
"so it is recommended to stick with **Strip Visuals** at first."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_dedicated_servers.rst:129
msgid ""
"With the above options used, a PCK for the client (which exports all "
"resources normally) will look as follows:"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_dedicated_servers.rst:160
msgid "The PCK's file structure for the server will look as follows:"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_dedicated_servers.rst:187
#, fuzzy
msgid "Starting the dedicated server"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/export/exporting_for_dedicated_servers.rst:189
msgid ""
"If both your client and server are part of the same Godot project, you will "
"have to add a way to start the server directly using a command-line argument."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_dedicated_servers.rst:192
msgid ""
"If you :ref:`exported the project "
"<doc_exporting_for_dedicated_servers_exporting_project>` using the **Export "
"as dedicated server** export mode (or have added ``dedicated_server`` as a "
"custom feature tag), you can use the ``dedicated_server`` feature tag to "
"detect whether a dedicated server PCK is being used:"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_dedicated_servers.rst:213
msgid ""
"If you also wish to host a server when using the built-in ``--headless`` "
"command line argument, this can be done by adding the following code snippet "
"in your main scene (or an autoload)'s ``_ready()`` method:"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_dedicated_servers.rst:241
msgid ""
"If you wish to use a custom command line argument, this can be done by "
"adding the following code snippet in your main scene (or an autoload)'s "
"``_ready()`` method:"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_dedicated_servers.rst:269
msgid ""
"It's a good idea to add at least one of the above command-line arguments to "
"start a server, as it can be used to test server functionality from the "
"command line without having to export the project."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_dedicated_servers.rst:273
msgid ""
"If your client and server are separate Godot projects, your server should "
"most likely be configured in a way where running the main scene starts a "
"server automatically."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_dedicated_servers.rst:278
#: ../../docs/tutorials/scripting/gdextension/gdextension_cpp_example.rst:696
msgid "Next steps"
msgstr ""

#: ../../docs/tutorials/export/exporting_for_dedicated_servers.rst:280
msgid ""
"On Linux, to make your dedicated server restart after a crash or system "
"reboot, you can `create a systemd service <https://medium.com/@benmorel/"
"creating-a-linux-service-with-systemd-611b5c8b91d6>`__. This also lets you "
"view server logs in a more convenient fashion, with automatic log rotation "
"provided by systemd."
msgstr ""

#: ../../docs/tutorials/export/exporting_for_dedicated_servers.rst:286
msgid ""
"If you have experience with containers, you could also look into wrapping "
"your dedicated server in a `Docker <https://www.docker.com/>`__ container. "
"This way, it can be used more easily in an automatic scaling setup (which is "
"outside the scope of this tutorial)."
msgstr ""

#: ../../docs/tutorials/export/one-click_deploy.rst:4
msgid "One-click deploy"
msgstr ""

#: ../../docs/tutorials/export/one-click_deploy.rst:7
msgid "What is one-click deploy?"
msgstr ""

#: ../../docs/tutorials/export/one-click_deploy.rst:9
msgid ""
"One-click deploy is a feature that is available once a platform is properly "
"configured and a supported device is connected to the computer. Since things "
"can go wrong at many levels (platform may not be configured correctly, SDK "
"may be incorrectly installed, device may be improperly configured, etc.), "
"it's good to let the user know that it exists."
msgstr ""

#: ../../docs/tutorials/export/one-click_deploy.rst:15
msgid ""
"After adding an Android export preset marked as Runnable, Godot can detect "
"when a USB device is connected to the computer and offer the user to "
"automatically export, install and run the project (in debug mode) on the "
"device. This feature is called *one-click deploy*."
msgstr ""

#: ../../docs/tutorials/export/one-click_deploy.rst:22
msgid ""
"One-click deploy is only available once you've added an export template "
"marked as **Runnable** in the Export dialog. You can mark several export "
"presets as runnable, but only one preset per platform may be marked as "
"runnable. If you mark a second preset in a given platform as runnable, the "
"other preset will no longer be marked as runnable."
msgstr ""

#: ../../docs/tutorials/export/one-click_deploy.rst:29
msgid "Supported platforms"
msgstr ""

#: ../../docs/tutorials/export/one-click_deploy.rst:31
msgid ""
"**Android:** Exports the project with debugging enabled and runs it on the "
"connected device."
msgstr ""

#: ../../docs/tutorials/export/one-click_deploy.rst:34
msgid ""
"Make sure to follow the steps described in :ref:`doc_exporting_for_android`. "
"Otherwise, the one-click deploy button won't appear."
msgstr ""

#: ../../docs/tutorials/export/one-click_deploy.rst:37
msgid ""
"If you have more than one device connected, Godot will ask you which device "
"the project should be exported to."
msgstr ""

#: ../../docs/tutorials/export/one-click_deploy.rst:40
msgid ""
"**HTML5:** Starts a local web server and runs the exported project by "
"opening the default web browser."
msgstr ""

#: ../../docs/tutorials/export/one-click_deploy.rst:43
msgid "Support for more platforms such as iOS is planned."
msgstr ""

#: ../../docs/tutorials/export/one-click_deploy.rst:46
msgid "Using one-click deploy"
msgstr ""

#: ../../docs/tutorials/export/one-click_deploy.rst:48
msgid ""
"If deploying to Android, enable developer mode on your mobile device then "
"enable USB debugging in the device's settings."
msgstr ""

#: ../../docs/tutorials/export/one-click_deploy.rst:50
msgid ""
"After enabling USB debugging, connect the device to your PC using an USB "
"cable."
msgstr ""

#: ../../docs/tutorials/export/one-click_deploy.rst:52
msgid "For advanced users, it should also be possible to use wireless ADB."
msgstr ""

#: ../../docs/tutorials/export/one-click_deploy.rst:54
msgid ""
"Make sure there is an export preset marked as **Runnable** for the target "
"platform (Android or HTML5)."
msgstr ""

#: ../../docs/tutorials/export/one-click_deploy.rst:56
msgid ""
"If everything is configured correctly and with no errors, platform-specific "
"icons will appear in the top-right corner of the editor."
msgstr ""

#: ../../docs/tutorials/export/one-click_deploy.rst:58
msgid "Click the button to export to the desired platform in one click."
msgstr ""

#: ../../docs/tutorials/export/one-click_deploy.rst:70
msgid ""
"If you can't see the device in the list of devices when running the ``adb "
"devices`` command in a terminal, it will not be visible by Godot either. To "
"resolve this:"
msgstr ""

#: ../../docs/tutorials/export/one-click_deploy.rst:74
msgid ""
"Check if USB debugging is enabled *and authorized on the device*. Try "
"unlocking your device and accepting the authorization prompt if you see any. "
"If you can't see this prompt, running ``adb devices`` on your PC should make "
"the authorization prompt appear on the device."
msgstr ""

#: ../../docs/tutorials/export/one-click_deploy.rst:78
msgid ""
"Try `revoking the debugging authorization <https://stackoverflow.com/"
"questions/23081263/adb-android-device-unauthorized>`__ in the device's "
"developer settings, then follow the steps again."
msgstr ""

#: ../../docs/tutorials/export/one-click_deploy.rst:80
msgid ""
"Try using USB debugging instead of wireless debugging or vice versa. "
"Sometimes, one of those can work better than the other."
msgstr ""

#: ../../docs/tutorials/export/one-click_deploy.rst:82
msgid ""
"On Linux, you may be missing the required `udev rules <https://github.com/"
"M0Rf30/android-udev-rules>`__ for your device to be recognized."
msgstr ""

#: ../../docs/tutorials/io/index.rst:2
msgid "File and data I/O"
msgstr ""

#: ../../docs/tutorials/io/background_loading.rst:4
msgid "Background loading"
msgstr ""

#: ../../docs/tutorials/io/background_loading.rst:6
msgid ""
"Commonly, games need to load resources asynchronously. When switching the "
"main scene of your game (e.g. going to a new level), you might want to show "
"a loading screen with some indication that progress is being made, or you "
"may want to load additional resources during gameplay."
msgstr ""

#: ../../docs/tutorials/io/background_loading.rst:12
msgid ""
"The standard load method (:ref:`ResourceLoader.load "
"<class_ResourceLoader_method_load>` or GDScript's simpler :ref:`load "
"<class_@GDScript_method_load>`) blocks your thread, making your game appear "
"unresponsive while the resource is being loaded."
msgstr ""

#: ../../docs/tutorials/io/background_loading.rst:17
msgid ""
"One way around this is using ``ResourceLoader`` to load resources "
"asynchronously in background threads."
msgstr ""

#: ../../docs/tutorials/io/background_loading.rst:21
#, fuzzy
msgid "Using ResourceLoader"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/io/background_loading.rst:23
msgid ""
"Generally, you queue requests to load resources for a path using :ref:"
"`ResourceLoader.load_threaded_request "
"<class_ResourceLoader_method_load_threaded_request>`, which will then be "
"loaded in threads in the background."
msgstr ""

#: ../../docs/tutorials/io/background_loading.rst:27
msgid ""
"You can check the status with :ref:`ResourceLoader.load_threaded_get_status "
"<class_ResourceLoader_method_load_threaded_get_status>`. Progress can be "
"obtained by passing an array variable via progress which will return a one "
"element array containing the percentage."
msgstr ""

#: ../../docs/tutorials/io/background_loading.rst:32
msgid ""
"Finally, you retrieve loaded resources by calling :ref:`ResourceLoader."
"load_threaded_get <class_ResourceLoader_method_load_threaded_get>`."
msgstr ""

#: ../../docs/tutorials/io/background_loading.rst:35
msgid ""
"Once you call ``load_threaded_get()``, either the resource finished loading "
"in the background and will be returned instantly or the load will block at "
"this point like ``load()`` would. If you want to guarantee this does not "
"block, you either need to ensure there is enough time between requesting the "
"load and retrieving the resource or you need to check the status manually."
msgstr ""

#: ../../docs/tutorials/io/background_loading.rst:42
#: ../../docs/tutorials/scripting/gdscript/gdscript_documentation_comments.rst:235
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_basics.rst:172
#: ../../docs/tutorials/shaders/visual_shaders.rst:118
#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:232
#: ../../docs/contributing/documentation/class_reference_primer.rst:138
#: ../../docs/contributing/documentation/class_reference_primer.rst:173
#: ../../docs/contributing/documentation/class_reference_primer.rst:195
msgid "Example"
msgstr ""

#: ../../docs/tutorials/io/background_loading.rst:44
msgid ""
"This example demonstrates how to load a scene in the background. We will "
"have a button spawn a enemy when pressed. The enemy will be ``Enemy.tscn`` "
"which we will load on ``_ready`` and instantiate when pressed. The path will "
"be ``\"Enemy.tscn\"`` which is located at ``res://Enemy.tscn``."
msgstr ""

#: ../../docs/tutorials/io/background_loading.rst:49
msgid ""
"First, we will start a request to load the resource and connect the button:"
msgstr ""

#: ../../docs/tutorials/io/background_loading.rst:59
msgid ""
"Now ``_on_button_pressed`` will be called when the button is pressed. This "
"method will be used to spawn an enemy."
msgstr ""

#: ../../docs/tutorials/io/data_paths.rst:4
msgid "File paths in Godot projects"
msgstr ""

#: ../../docs/tutorials/io/data_paths.rst:6
msgid ""
"This page explains how file paths work inside Godot projects. You will learn "
"how to access paths in your projects using the ``res://`` and ``user://`` "
"notations, and where Godot stores project and editor files on your and your "
"users' systems."
msgstr ""

#: ../../docs/tutorials/io/data_paths.rst:11
msgid "Path separators"
msgstr ""

#: ../../docs/tutorials/io/data_paths.rst:13
msgid ""
"To make supporting multiple platforms easier, Godot uses **UNIX-style path "
"separators** (forward slash ``/``). These work on all platforms, **including "
"Windows**."
msgstr ""

#: ../../docs/tutorials/io/data_paths.rst:17
msgid ""
"Instead of writing paths like ``C:\\Projects\\Game``, in Godot, you should "
"write ``C:/Projects/Game``."
msgstr ""

#: ../../docs/tutorials/io/data_paths.rst:20
msgid ""
"Windows-style path separators (backward slash ``\\``) are also supported in "
"some path-related methods, but they need to be doubled (``\\\\``), as ``\\`` "
"is normally used as an escape for characters with a special meaning."
msgstr ""

#: ../../docs/tutorials/io/data_paths.rst:24
msgid ""
"This makes it possible to work with paths returned by other Windows "
"applications. We still recommend using only forward slashes in your own code "
"to guarantee that everything will work as intended."
msgstr ""

#: ../../docs/tutorials/io/data_paths.rst:29
#, fuzzy
msgid "Accessing files in the project folder (``res://``)"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/io/data_paths.rst:31
msgid ""
"Godot considers that a project exists in any folder that contains a "
"``project.godot`` text file, even if the file is empty. The folder that "
"contains this file is your project's root folder."
msgstr ""

#: ../../docs/tutorials/io/data_paths.rst:35
msgid ""
"You can access any file relative to it by writing paths starting with "
"``res://``, which stands for resources. For example, you can access an image "
"file ``character.png`` located in the project's root folder in code with the "
"following path: ``res://character.png``."
msgstr ""

#: ../../docs/tutorials/io/data_paths.rst:41
msgid "Accessing persistent user data (``user://``)"
msgstr ""

#: ../../docs/tutorials/io/data_paths.rst:43
msgid ""
"To store persistent data files, like the player's save or settings, you want "
"to use ``user://`` instead of ``res://`` as your path's prefix. This is "
"because when the game is running, the project's file system will likely be "
"read-only."
msgstr ""

#: ../../docs/tutorials/io/data_paths.rst:47
msgid ""
"The ``user://`` prefix points to a different directory on the user's device. "
"Unlike ``res://``, the directory pointed at by ``user://`` is created "
"automatically and *guaranteed* to be writable to, even in an exported "
"project."
msgstr ""

#: ../../docs/tutorials/io/data_paths.rst:51
msgid ""
"The location of the ``user://`` folder depends on what is configured in the "
"Project Settings:"
msgstr ""

#: ../../docs/tutorials/io/data_paths.rst:54
msgid ""
"By default, the ``user://`` folder is created within Godot's :ref:`editor "
"data path <doc_data_paths_editor_data_paths>` in the ``app_userdata/"
"[project_name]`` folder. This is the default so that prototypes and test "
"projects stay self-contained within Godot's data folder."
msgstr ""

#: ../../docs/tutorials/io/data_paths.rst:58
msgid ""
"If :ref:`application/config/use_custom_user_dir "
"<class_ProjectSettings_property_application/config/use_custom_user_dir>` is "
"enabled in the Project Settings, the ``user://`` folder is created **next "
"to** Godot's editor data path, i.e. in the standard location for "
"applications data."
msgstr ""

#: ../../docs/tutorials/io/data_paths.rst:63
msgid ""
"By default, the folder name will be inferred from the project name, but it "
"can be further customized with :ref:`application/config/custom_user_dir_name "
"<class_ProjectSettings_property_application/config/custom_user_dir_name>`. "
"This path can contain path separators, so you can use it e.g. to group "
"projects of a given studio with a ``Studio Name/Game Name`` structure."
msgstr ""

#: ../../docs/tutorials/io/data_paths.rst:69
msgid "On desktop platforms, the actual directory paths for ``user://`` are:"
msgstr ""

#: ../../docs/tutorials/io/data_paths.rst:72
#: ../../docs/tutorials/io/data_paths.rst:121
#: ../../docs/tutorials/io/binary_serialization_api.rst:43
#: ../../docs/tutorials/io/binary_serialization_api.rst:120
#: ../../docs/tutorials/io/binary_serialization_api.rst:131
#: ../../docs/tutorials/io/binary_serialization_api.rst:140
#: ../../docs/tutorials/io/binary_serialization_api.rst:151
#: ../../docs/tutorials/io/binary_serialization_api.rst:160
#: ../../docs/tutorials/io/binary_serialization_api.rst:169
#: ../../docs/tutorials/io/binary_serialization_api.rst:182
#: ../../docs/tutorials/io/binary_serialization_api.rst:193
#: ../../docs/tutorials/io/binary_serialization_api.rst:208
#: ../../docs/tutorials/io/binary_serialization_api.rst:221
#: ../../docs/tutorials/io/binary_serialization_api.rst:240
#: ../../docs/tutorials/io/binary_serialization_api.rst:255
#: ../../docs/tutorials/io/binary_serialization_api.rst:270
#: ../../docs/tutorials/io/binary_serialization_api.rst:289
#: ../../docs/tutorials/io/binary_serialization_api.rst:314
#: ../../docs/tutorials/io/binary_serialization_api.rst:345
#: ../../docs/tutorials/io/binary_serialization_api.rst:360
#: ../../docs/tutorials/io/binary_serialization_api.rst:369
#: ../../docs/tutorials/io/binary_serialization_api.rst:380
#: ../../docs/tutorials/io/binary_serialization_api.rst:390
#: ../../docs/tutorials/io/binary_serialization_api.rst:412
#: ../../docs/tutorials/io/binary_serialization_api.rst:421
#: ../../docs/tutorials/io/binary_serialization_api.rst:430
#: ../../docs/tutorials/io/binary_serialization_api.rst:442
#: ../../docs/tutorials/io/binary_serialization_api.rst:466
#: ../../docs/tutorials/io/binary_serialization_api.rst:478
#: ../../docs/tutorials/io/binary_serialization_api.rst:490
#: ../../docs/tutorials/io/binary_serialization_api.rst:503
#: ../../docs/tutorials/io/binary_serialization_api.rst:514
#: ../../docs/tutorials/io/binary_serialization_api.rst:525
#: ../../docs/tutorials/io/binary_serialization_api.rst:536
#: ../../docs/tutorials/io/binary_serialization_api.rst:547
#: ../../docs/tutorials/io/binary_serialization_api.rst:555
#: ../../docs/tutorials/io/binary_serialization_api.rst:568
#: ../../docs/tutorials/io/binary_serialization_api.rst:581
#: ../../docs/tutorials/io/binary_serialization_api.rst:596
#: ../../docs/tutorials/plugins/editor/import_plugins.rst:248
#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:23
#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:779
#: ../../docs/tutorials/shaders/visual_shaders.rst:115
#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:91
#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:164
#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:229
msgid "Type"
msgstr ""

#: ../../docs/tutorials/io/data_paths.rst:74
msgid "Default"
msgstr ""

#: ../../docs/tutorials/io/data_paths.rst:0
msgid "Windows: ``%APPDATA%\\Godot\\app_userdata\\[project_name]``"
msgstr ""

#: ../../docs/tutorials/io/data_paths.rst:0
msgid ""
"macOS: ``~/Library/Application Support/Godot/app_userdata/[project_name]``"
msgstr ""

#: ../../docs/tutorials/io/data_paths.rst:0
msgid "Linux: ``~/.local/share/godot/app_userdata/[project_name]``"
msgstr ""

#: ../../docs/tutorials/io/data_paths.rst:78
#, fuzzy
msgid "Custom dir"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/io/data_paths.rst:0
msgid "Windows: ``%APPDATA%\\[project_name]``"
msgstr ""

#: ../../docs/tutorials/io/data_paths.rst:0
msgid "macOS: ``~/Library/Application Support/[project_name]``"
msgstr ""

#: ../../docs/tutorials/io/data_paths.rst:0
msgid "Linux: ``~/.local/share/[project_name]``"
msgstr ""

#: ../../docs/tutorials/io/data_paths.rst:82
#, fuzzy
msgid "Custom dir and name"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/io/data_paths.rst:0
msgid "Windows: ``%APPDATA%\\[custom_user_dir_name]``"
msgstr ""

#: ../../docs/tutorials/io/data_paths.rst:0
msgid "macOS: ``~/Library/Application Support/[custom_user_dir_name]``"
msgstr ""

#: ../../docs/tutorials/io/data_paths.rst:0
msgid "Linux: ``~/.local/share/[custom_user_dir_name]``"
msgstr ""

#: ../../docs/tutorials/io/data_paths.rst:87
msgid ""
"``[project_name]`` is based on the application name defined in the Project "
"Settings, but you can override it on a per-platform basis using :ref:"
"`feature tags <doc_feature_tags>`."
msgstr ""

#: ../../docs/tutorials/io/data_paths.rst:90
msgid ""
"On mobile platforms, this path is unique to the project and is not "
"accessible by other applications for security reasons."
msgstr ""

#: ../../docs/tutorials/io/data_paths.rst:93
msgid ""
"On HTML5 exports, ``user://`` will refer to a virtual filesystem stored on "
"the device via IndexedDB. (Interaction with the main filesystem can still be "
"performed through the :ref:`JavaScriptBridge <class_JavaScriptBridge>` "
"singleton.)"
msgstr ""

#: ../../docs/tutorials/io/data_paths.rst:98
msgid "Converting paths to absolute paths or \"local\" paths"
msgstr ""

#: ../../docs/tutorials/io/data_paths.rst:100
msgid ""
"You can use :ref:`ProjectSettings.globalize_path() "
"<class_ProjectSettings_method_globalize_path>` to convert a \"local\" path "
"like ``res://path/to/file.txt`` to an absolute OS path. For example, :ref:"
"`ProjectSettings.globalize_path() "
"<class_ProjectSettings_method_globalize_path>` can be used to open \"local\" "
"paths in the OS file manager using :ref:`OS.shell_open() "
"<class_OS_method_shell_open>` since it only accepts native OS paths."
msgstr ""

#: ../../docs/tutorials/io/data_paths.rst:107
msgid ""
"To convert an absolute OS path to a \"local\" path starting with ``res://`` "
"or ``user://``, use :ref:`ProjectSettings.localize_path() "
"<class_ProjectSettings_method_localize_path>`. This only works for absolute "
"paths that point to files or folders in your project's root or ``user://`` "
"folders."
msgstr ""

#: ../../docs/tutorials/io/data_paths.rst:115
msgid "Editor data paths"
msgstr ""

#: ../../docs/tutorials/io/data_paths.rst:117
msgid ""
"The editor uses different paths for editor data, editor settings, and cache, "
"depending on the platform. By default, these paths are:"
msgstr ""

#: ../../docs/tutorials/io/data_paths.rst:123
#, fuzzy
msgid "Editor data"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/io/data_paths.rst:0
msgid "Windows: ``%APPDATA%\\Godot\\``"
msgstr ""

#: ../../docs/tutorials/io/data_paths.rst:0
msgid "macOS: ``~/Library/Application Support/Godot/``"
msgstr ""

#: ../../docs/tutorials/io/data_paths.rst:0
msgid "Linux: ``~/.local/share/godot/``"
msgstr ""

#: ../../docs/tutorials/io/data_paths.rst:127
#, fuzzy
msgid "Editor settings"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/io/data_paths.rst:0
msgid "Linux: ``~/.config/godot/``"
msgstr ""

#: ../../docs/tutorials/io/data_paths.rst:131
msgid "Cache"
msgstr ""

#: ../../docs/tutorials/io/data_paths.rst:0
msgid "Windows: ``%TEMP%\\Godot\\``"
msgstr ""

#: ../../docs/tutorials/io/data_paths.rst:0
msgid "macOS: ``~/Library/Caches/Godot/``"
msgstr ""

#: ../../docs/tutorials/io/data_paths.rst:0
msgid "Linux: ``~/.cache/godot/``"
msgstr ""

#: ../../docs/tutorials/io/data_paths.rst:136
msgid "**Editor data** contains export templates and project-specific data."
msgstr ""

#: ../../docs/tutorials/io/data_paths.rst:137
msgid ""
"**Editor settings** contains the main editor settings configuration file as "
"well as various other user-specific customizations (editor layouts, feature "
"profiles, script templates, etc.)."
msgstr ""

#: ../../docs/tutorials/io/data_paths.rst:140
msgid ""
"**Cache** contains data generated by the editor, or stored temporarily. It "
"can safely be removed when Godot is closed."
msgstr ""

#: ../../docs/tutorials/io/data_paths.rst:143
msgid ""
"Godot complies with the `XDG Base Directory Specification <https://"
"specifications.freedesktop.org/basedir-spec/basedir-spec-latest.html>`__ on "
"all platforms. You can override environment variables following the "
"specification to change the editor and project data paths."
msgstr ""

#: ../../docs/tutorials/io/data_paths.rst:148
msgid ""
"If you use `Godot packaged as a Flatpak <https://flathub.org/apps/details/"
"org.godotengine.Godot>`__, the editor data paths will be located in "
"subfolders in ``~/.var/app/org.godotengine.Godot/``."
msgstr ""

#: ../../docs/tutorials/io/data_paths.rst:156
msgid "Self-contained mode"
msgstr ""

#: ../../docs/tutorials/io/data_paths.rst:158
msgid ""
"If you create a file called ``._sc_`` or ``_sc_`` in the same directory as "
"the editor binary (or in `MacOS/Contents/` for a macOS editor .app bundle), "
"Godot will enable *self-contained mode*. This mode makes Godot write all "
"editor data, settings, and cache to a directory named ``editor_data/`` in "
"the same directory as the editor binary. You can use it to create a portable "
"installation of the editor."
msgstr ""

#: ../../docs/tutorials/io/data_paths.rst:165
msgid ""
"The `Steam release of Godot <https://store.steampowered.com/app/404790/>`__ "
"uses self-contained mode by default."
msgstr ""

#: ../../docs/tutorials/io/data_paths.rst:170
msgid ""
"Self-contained mode is not supported in exported projects yet. To read and "
"write files relative to the executable path, use :ref:`OS."
"get_executable_path() <class_OS_method_get_executable_path>`. Note that "
"writing files in the executable path only works if the executable is placed "
"in a writable location (i.e. **not** Program Files or another directory that "
"is read-only for regular users)."
msgstr ""

#: ../../docs/tutorials/io/saving_games.rst:4
msgid "Saving games"
msgstr ""

#: ../../docs/tutorials/io/saving_games.rst:9
msgid ""
"Save games can be complicated. For example, it may be desirable to store "
"information from multiple objects across multiple levels. Advanced save game "
"systems should allow for additional information about an arbitrary number of "
"objects. This will allow the save function to scale as the game grows more "
"complex."
msgstr ""

#: ../../docs/tutorials/io/saving_games.rst:17
msgid ""
"If you're looking to save user configuration, you can use the :ref:"
"`class_ConfigFile` class for this purpose."
msgstr ""

#: ../../docs/tutorials/io/saving_games.rst:22
#, fuzzy
msgid ""
"You can see how saving and loading works in action using the `Saving and "
"Loading (Serialization) demo project <https://github.com/godotengine/godot-"
"demo-projects/blob/master/loading/serialization>`__."
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati različite Godo demo projekte "
"`Godot demo projects <https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/tutorials/io/saving_games.rst:26
msgid "Identify persistent objects"
msgstr ""

#: ../../docs/tutorials/io/saving_games.rst:28
msgid ""
"Firstly, we should identify what objects we want to keep between game "
"sessions and what information we want to keep from those objects. For this "
"tutorial, we will use groups to mark and handle objects to be saved, but "
"other methods are certainly possible."
msgstr ""

#: ../../docs/tutorials/io/saving_games.rst:33
msgid ""
"We will start by adding objects we wish to save to the \"Persist\" group. We "
"can do this through either the GUI or script. Let's add the relevant nodes "
"using the GUI:"
msgstr ""

#: ../../docs/tutorials/io/saving_games.rst:39
msgid ""
"Once this is done, when we need to save the game, we can get all objects to "
"save them and then tell them all to save with this script:"
msgstr ""

#: ../../docs/tutorials/io/saving_games.rst:59
msgid "Serializing"
msgstr ""

#: ../../docs/tutorials/io/saving_games.rst:61
msgid ""
"The next step is to serialize the data. This makes it much easier to read "
"from and store to disk. In this case, we're assuming each member of group "
"Persist is an instanced node and thus has a path. GDScript has helper class :"
"ref:`JSON<class_json>` to convert between dictionary and string, Our node "
"needs to contain a save function that returns this data. The save function "
"will look like this:"
msgstr ""

#: ../../docs/tutorials/io/saving_games.rst:122
msgid ""
"This gives us a dictionary with the style ``{ \"variable_name\":"
"value_of_variable }``, which will be useful when loading."
msgstr ""

#: ../../docs/tutorials/io/saving_games.rst:127
msgid "Saving and reading data"
msgstr ""

#: ../../docs/tutorials/io/saving_games.rst:129
msgid ""
"As covered in the :ref:`doc_filesystem` tutorial, we'll need to open a file "
"so we can write to it or read from it. Now that we have a way to call our "
"groups and get their relevant data, let's use the class :ref:"
"`JSON<class_json>` to convert it into an easily stored string and store them "
"in a file. Doing it this way ensures that each line is its own object, so we "
"have an easy way to pull the data out of the file as well."
msgstr ""

#: ../../docs/tutorials/io/saving_games.rst:205
msgid ""
"Game saved! Now, to load, we'll read each line. Use the :ref:"
"`parse<class_JSON_method_parse>` method to read the JSON string back to a "
"dictionary, and then iterate over the dict to read our values. But we'll "
"need to first create the object and we can use the filename and parent "
"values to achieve that. Here is our load function:"
msgstr ""

#: ../../docs/tutorials/io/saving_games.rst:318
msgid ""
"Now we can save and load an arbitrary number of objects laid out almost "
"anywhere across the scene tree! Each object can store different data "
"depending on what it needs to save."
msgstr ""

#: ../../docs/tutorials/io/saving_games.rst:323
msgid "Some notes"
msgstr ""

#: ../../docs/tutorials/io/saving_games.rst:325
msgid ""
"We have glossed over setting up the game state for loading. It's ultimately "
"up to the project creator where much of this logic goes. This is often "
"complicated and will need to be heavily customized based on the needs of the "
"individual project."
msgstr ""

#: ../../docs/tutorials/io/saving_games.rst:330
msgid ""
"Additionally, our implementation assumes no Persist objects are children of "
"other Persist objects. Otherwise, invalid paths would be created. To "
"accommodate nested Persist objects, consider saving objects in stages. Load "
"parent objects first so they are available for the :ref:`add_child() "
"<class_node_method_add_child>` call when child objects are loaded. You will "
"also need a way to link children to parents as the :ref:`NodePath "
"<class_nodepath>` will likely be invalid."
msgstr ""

#: ../../docs/tutorials/io/saving_games.rst:340
msgid "JSON vs binary serialization"
msgstr ""

#: ../../docs/tutorials/io/saving_games.rst:342
msgid ""
"For simple game state, JSON may work and it generates human-readable files "
"that are easy to debug."
msgstr ""

#: ../../docs/tutorials/io/saving_games.rst:344
msgid ""
"But JSON has many limitations. If you need to store more complex game state "
"or a lot of it, :ref:`binary serialization<doc_binary_serialization_api>` "
"may be a better approach."
msgstr ""

#: ../../docs/tutorials/io/saving_games.rst:349
msgid "JSON limitations"
msgstr ""

#: ../../docs/tutorials/io/saving_games.rst:351
msgid "Here are some important gotchas to know about when using JSON."
msgstr ""

#: ../../docs/tutorials/io/saving_games.rst:353
msgid ""
"**Filesize:** JSON stores data in text format, which is much larger than "
"binary formats."
msgstr ""

#: ../../docs/tutorials/io/saving_games.rst:355
msgid ""
"**Data types:** JSON only offers a limited set of data types. If you have "
"data types that JSON doesn't have, you will need to translate your data to "
"and from types that JSON can handle. For example, some important types that "
"JSON can't parse are: ``Vector2``, ``Vector3``, ``Color``, ``Rect2``, and "
"``Quaternion``."
msgstr ""

#: ../../docs/tutorials/io/saving_games.rst:360
msgid ""
"**Custom logic needed for encoding/decoding:** If you have any custom "
"classes that you want to store with JSON, you will need to write your own "
"logic for encoding and decoding those classes."
msgstr ""

#: ../../docs/tutorials/io/saving_games.rst:365
#, fuzzy
msgid "Binary serialization"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/io/saving_games.rst:367
msgid ""
":ref:`Binary serialization<doc_binary_serialization_api>` is an alternative "
"approach for storing game state, and you can use it with the functions "
"``get_var`` and ``store_var`` of :ref:`class_FileAccess`."
msgstr ""

#: ../../docs/tutorials/io/saving_games.rst:371
msgid "Binary serialization should produce smaller files than JSON."
msgstr ""

#: ../../docs/tutorials/io/saving_games.rst:372
msgid "Binary serialization can handle most common data types."
msgstr ""

#: ../../docs/tutorials/io/saving_games.rst:373
msgid ""
"Binary serialization requires less custom logic for encoding and decoding "
"custom classes."
msgstr ""

#: ../../docs/tutorials/io/saving_games.rst:376
msgid ""
"Note that not all properties are included. Only properties that are "
"configured with the :ref:"
"`PROPERTY_USAGE_STORAGE<class_@GlobalScope_constant_PROPERTY_USAGE_STORAGE>` "
"flag set will be serialized. You can add a new usage flag to a property by "
"overriding the :ref:"
"`_get_property_list<class_Object_private_method__get_property_list>` method "
"in your class. You can also check how property usage is configured by "
"calling ``Object._get_property_list``. See :ref:"
"`PropertyUsageFlags<enum_@GlobalScope_PropertyUsageFlags>` for the possible "
"usage flags."
msgstr ""

#: ../../docs/tutorials/io/runtime_file_loading_and_saving.rst:4
msgid "Runtime file loading and saving"
msgstr ""

#: ../../docs/tutorials/io/runtime_file_loading_and_saving.rst:8
msgid ""
"See :ref:`doc_saving_games` for information on saving and loading game "
"progression."
msgstr ""

#: ../../docs/tutorials/io/runtime_file_loading_and_saving.rst:10
msgid ""
"Sometimes, :ref:`exporting packs, patches, and mods <doc_exporting_pcks>` is "
"not ideal when you want players to be able to load user-generated content in "
"your project. It requires users to generate a PCK or ZIP file through the "
"Godot editor, which contains resources imported by Godot."
msgstr ""

#: ../../docs/tutorials/io/runtime_file_loading_and_saving.rst:15
msgid "Example use cases for runtime file loading and saving include:"
msgstr ""

#: ../../docs/tutorials/io/runtime_file_loading_and_saving.rst:17
msgid "Loading texture packs designed for the game."
msgstr ""

#: ../../docs/tutorials/io/runtime_file_loading_and_saving.rst:18
msgid ""
"Loading user-provided audio tracks and playing them back in an in-game radio "
"station."
msgstr ""

#: ../../docs/tutorials/io/runtime_file_loading_and_saving.rst:19
msgid ""
"Loading custom levels or 3D models that can be designed with any 3D DCC that "
"can export to glTF (including glTF scenes saved by Godot at runtime)."
msgstr ""

#: ../../docs/tutorials/io/runtime_file_loading_and_saving.rst:21
msgid "Using user-provided fonts for menus and HUD."
msgstr ""

#: ../../docs/tutorials/io/runtime_file_loading_and_saving.rst:22
msgid ""
"Saving/loading a file format that can contain multiple files but can still "
"easily be read by other applications (ZIP)."
msgstr ""

#: ../../docs/tutorials/io/runtime_file_loading_and_saving.rst:24
msgid ""
"Loading files created by another game or program, or even game data files "
"from another game not made with Godot."
msgstr ""

#: ../../docs/tutorials/io/runtime_file_loading_and_saving.rst:27
msgid ""
"Runtime file loading can be combined with :ref:`HTTP requests "
"<doc_http_request_class>` to load resources from the Internet directly."
msgstr ""

#: ../../docs/tutorials/io/runtime_file_loading_and_saving.rst:32
msgid ""
"Do **not** use this runtime loading approach to load resources that are part "
"of the project, as it's less efficient and doesn't allow benefiting from "
"Godot's resource handling functionality (such as translation remaps). See :"
"ref:`doc_import_process` for details."
msgstr ""

#: ../../docs/tutorials/io/runtime_file_loading_and_saving.rst:39
#, fuzzy
msgid ""
"You can see how saving and loading works in action using the `Run-time File "
"Saving and Loading (Serialization) demo project <https://github.com/"
"godotengine/godot-demo-projects/blob/master/loading/runtime_save_load>`__."
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati različite Godo demo projekte "
"`Godot demo projects <https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/tutorials/io/runtime_file_loading_and_saving.rst:43
msgid "Plain text and binary files"
msgstr ""

#: ../../docs/tutorials/io/runtime_file_loading_and_saving.rst:45
msgid ""
"Godot's :ref:`class_FileAccess` class provides methods to access files on "
"the filesystem for reading and writing:"
msgstr ""

#: ../../docs/tutorials/io/runtime_file_loading_and_saving.rst:59
msgid ""
"To handle custom binary formats (such as loading file formats not supported "
"by Godot), :ref:`class_FileAccess` provides several methods to read/write "
"integers, floats, strings and more. These FileAccess methods have names that "
"start with ``get_`` and ``store_``."
msgstr ""

#: ../../docs/tutorials/io/runtime_file_loading_and_saving.rst:64
msgid ""
"If you need more control over reading binary files or need to read binary "
"streams that are not part of a file, :ref:`class_PackedByteArray` provides "
"several helper methods to decode/encode series of bytes to integers, floats, "
"strings and more. These PackedByteArray methods have names that start with "
"``decode_`` and ``encode_``. See also :ref:`doc_binary_serialization_api`."
msgstr ""

#: ../../docs/tutorials/io/runtime_file_loading_and_saving.rst:73
msgid "Images"
msgstr ""

#: ../../docs/tutorials/io/runtime_file_loading_and_saving.rst:75
msgid ""
"Image's :ref:`Image.load_from_file <class_Image_method_load_from_file>` "
"static method handles everything, from format detection based on file "
"extension to reading the file from disk."
msgstr ""

#: ../../docs/tutorials/io/runtime_file_loading_and_saving.rst:79
msgid ""
"If you need error handling or more control (such as changing the scale a SVG "
"is loaded at), use one of the following methods depending on the file format:"
msgstr ""

#: ../../docs/tutorials/io/runtime_file_loading_and_saving.rst:82
msgid ""
":ref:`Image.load_jpg_from_buffer <class_Image_method_load_jpg_from_buffer>`"
msgstr ""

#: ../../docs/tutorials/io/runtime_file_loading_and_saving.rst:83
msgid ""
":ref:`Image.load_ktx_from_buffer <class_Image_method_load_ktx_from_buffer>`"
msgstr ""

#: ../../docs/tutorials/io/runtime_file_loading_and_saving.rst:84
msgid ""
":ref:`Image.load_png_from_buffer <class_Image_method_load_png_from_buffer>`"
msgstr ""

#: ../../docs/tutorials/io/runtime_file_loading_and_saving.rst:85
msgid ""
":ref:`Image.load_svg_from_buffer <class_Image_method_load_svg_from_buffer>` "
"or :ref:`Image.load_svg_from_string "
"<class_Image_method_load_svg_from_string>`"
msgstr ""

#: ../../docs/tutorials/io/runtime_file_loading_and_saving.rst:87
msgid ""
":ref:`Image.load_tga_from_buffer <class_Image_method_load_tga_from_buffer>`"
msgstr ""

#: ../../docs/tutorials/io/runtime_file_loading_and_saving.rst:88
msgid ""
":ref:`Image.load_webp_from_buffer <class_Image_method_load_webp_from_buffer>`"
msgstr ""

#: ../../docs/tutorials/io/runtime_file_loading_and_saving.rst:90
msgid ""
"Several image formats can also be saved by Godot at runtime using the "
"following methods:"
msgstr ""

#: ../../docs/tutorials/io/runtime_file_loading_and_saving.rst:93
msgid ""
":ref:`Image.save_png <class_Image_method_save_png>` or :ref:`Image."
"save_png_to_buffer <class_Image_method_save_png_to_buffer>`"
msgstr ""

#: ../../docs/tutorials/io/runtime_file_loading_and_saving.rst:95
msgid ""
":ref:`Image.save_webp <class_Image_method_save_webp>` or :ref:`Image."
"save_webp_to_buffer <class_Image_method_save_webp_to_buffer>`"
msgstr ""

#: ../../docs/tutorials/io/runtime_file_loading_and_saving.rst:97
msgid ""
":ref:`Image.save_jpg <class_Image_method_save_jpg>` or :ref:`Image."
"save_jpg_to_buffer <class_Image_method_save_jpg_to_buffer>`"
msgstr ""

#: ../../docs/tutorials/io/runtime_file_loading_and_saving.rst:99
msgid ""
":ref:`Image.save_exr <class_Image_method_save_exr>` or :ref:`Image."
"save_exr_to_buffer <class_Image_method_save_exr_to_buffer>` *(only available "
"in editor builds, cannot be used in exported projects)*"
msgstr ""

#: ../../docs/tutorials/io/runtime_file_loading_and_saving.rst:103
msgid ""
"The methods with the ``to_buffer`` suffix save the image to a "
"PackedByteArray instead of the filesystem. This is useful to send the image "
"over the network or into a ZIP archive without having to write it on the "
"filesystem. This can increase performance by reducing I/O utilization."
msgstr ""

#: ../../docs/tutorials/io/runtime_file_loading_and_saving.rst:110
msgid ""
"If displaying the loaded image on a 3D surface, make sure to call :ref:"
"`Image.generate_mipmaps <class_Image_method_generate_mipmaps>` so that the "
"texture doesn't look grainy when viewed at a distance. This is also useful "
"in 2D when following instructions on :ref:`reducing aliasing when "
"downsampling <doc_multiple_resolutions_reducing_aliasing_on_downsampling>`."
msgstr ""

#: ../../docs/tutorials/io/runtime_file_loading_and_saving.rst:116
msgid ""
"Example of loading an image and displaying it in a :ref:`class_TextureRect` "
"node (which requires conversion to :ref:`class_ImageTexture`):"
msgstr ""

#: ../../docs/tutorials/io/runtime_file_loading_and_saving.rst:137
msgid "Audio/video files"
msgstr ""

#: ../../docs/tutorials/io/runtime_file_loading_and_saving.rst:139
msgid ""
"Godot supports loading Ogg Vorbis audio at runtime. Note that not *all* "
"files with an ``.ogg`` extension may be Ogg Vorbis files. Some may be Ogg "
"Theora videos, or contain Opus audio within an Ogg container. These files "
"will **not** load correctly as audio files in Godot."
msgstr ""

#: ../../docs/tutorials/io/runtime_file_loading_and_saving.rst:144
msgid ""
"Example of loading an Ogg Vorbis audio file in an :ref:"
"`class_AudioStreamPlayer` node:"
msgstr ""

#: ../../docs/tutorials/io/runtime_file_loading_and_saving.rst:150
msgid ""
"Example of loading an Ogg Theora video file in a :ref:"
"`class_VideoStreamPlayer` node:"
msgstr ""

#: ../../docs/tutorials/io/runtime_file_loading_and_saving.rst:166
msgid ""
"Godot doesn't support runtime loading of MP3 or WAV files yet. Until this is "
"implemented, it's feasible to implement runtime WAV loading using a script "
"since :ref:`class_AudioStreamWAV`'s ``data`` property is exposed to "
"scripting."
msgstr ""

#: ../../docs/tutorials/io/runtime_file_loading_and_saving.rst:171
msgid ""
"It's still possible to *save* WAV files using :ref:`AudioStreamWAV."
"save_to_wav <class_AudioStreamWAV_method_save_to_wav>`, which is useful for "
"procedurally generated audio or microphone recordings."
msgstr ""

#: ../../docs/tutorials/io/runtime_file_loading_and_saving.rst:178
#, fuzzy
msgid "3D scenes"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/io/runtime_file_loading_and_saving.rst:180
msgid ""
"Godot has first-class support for glTF 2.0, both in the editor and exported "
"projects. Using :ref:`class_gltfdocument` and :ref:`class_gltfstate` "
"together, Godot can load and save glTF files in exported projects, in both "
"text (``.gltf``) and binary (``.glb``) formats. The binary format should be "
"preferred as it's faster to write and smaller, but the text format is easier "
"to debug."
msgstr ""

#: ../../docs/tutorials/io/runtime_file_loading_and_saving.rst:186
msgid ""
"Example of loading a glTF scene and appending its root node to the scene:"
msgstr ""

#: ../../docs/tutorials/io/runtime_file_loading_and_saving.rst:214
msgid ""
"When loading a glTF scene, a *base path* must be set so that external "
"resources like textures can be loaded correctly. When loading from a file, "
"the base path is automatically set to the folder containing the file. When "
"loading from a buffer, this base path must be manually set as there is no "
"way for Godot to infer this path."
msgstr ""

#: ../../docs/tutorials/io/runtime_file_loading_and_saving.rst:220
msgid ""
"To set the base path, set :ref:`GLTFState.base_path "
"<class_GLTFState_property_base_path>` on your GLTFState instance *before* "
"calling :ref:`GLTFDocument.append_from_buffer "
"<class_GLTFDocument_method_append_from_buffer>` or :ref:`GLTFDocument."
"append_from_file <class_GLTFDocument_method_append_from_file>`."
msgstr ""

#: ../../docs/tutorials/io/runtime_file_loading_and_saving.rst:229
#, fuzzy
msgid "Fonts"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/io/runtime_file_loading_and_saving.rst:231
msgid ""
":ref:`FontFile.load_dynamic_font <class_FontFile_method_load_bitmap_font>` "
"supports the following font file formats: TTF, OTF, WOFF, WOFF2, PFB, PFM"
msgstr ""

#: ../../docs/tutorials/io/runtime_file_loading_and_saving.rst:234
msgid ""
"On the other hand, :ref:`FontFile.load_bitmap_font "
"<class_FontFile_method_load_bitmap_font>` supports the `BMFont <https://www."
"angelcode.com/products/bmfont/>`__ format (``.fnt`` or ``.font``)."
msgstr ""

#: ../../docs/tutorials/io/runtime_file_loading_and_saving.rst:237
msgid ""
"Additionally, it is possible to load any font that is installed on the "
"system using Godot's support for :ref:`doc_using_fonts_system_fonts`."
msgstr ""

#: ../../docs/tutorials/io/runtime_file_loading_and_saving.rst:240
msgid ""
"Example of loading a font file automatically according to its file "
"extension, then adding it as a theme override to a :ref:`class_Label` node:"
msgstr ""

#: ../../docs/tutorials/io/runtime_file_loading_and_saving.rst:267
msgid "ZIP archives"
msgstr ""

#: ../../docs/tutorials/io/runtime_file_loading_and_saving.rst:269
msgid ""
"Godot supports reading and writing ZIP archives using the :ref:"
"`class_zipreader` and :ref:`class_zippacker` classes. This supports any ZIP "
"file, including files generated by Godot's \"Export PCK/ZIP\" functionality "
"(although these will contain imported Godot resources rather than the "
"original project files)."
msgstr ""

#: ../../docs/tutorials/io/runtime_file_loading_and_saving.rst:276
msgid ""
"Use :ref:`ProjectSettings.load_resource_pack "
"<class_ProjectSettings_method_load_resource_pack>` to load PCK or ZIP files "
"exported by Godot as :ref:`additional data packs <doc_exporting_pcks>`. That "
"approach is preferred for DLCs, as it makes interacting with additional data "
"packs seamless (virtual filesystem)."
msgstr ""

#: ../../docs/tutorials/io/runtime_file_loading_and_saving.rst:281
msgid ""
"This ZIP archive support can be combined with runtime image, 3D scene and "
"audio loading to provide a seamless modding experience without requiring "
"users to go through the Godot editor to generate PCK/ZIP files."
msgstr ""

#: ../../docs/tutorials/io/runtime_file_loading_and_saving.rst:285
msgid ""
"Example that lists files in a ZIP archive in an :ref:`class_ItemList` node, "
"then writes contents read from it to a new ZIP archive (essentially "
"duplicating the archive):"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:6
msgid "Binary serialization API"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:11
msgid ""
"Godot has a serialization API based on Variant. It's used for converting "
"data types to an array of bytes efficiently. This API is exposed via the "
"global :ref:`bytes_to_var() <class_@GlobalScope_method_bytes_to_var>` and :"
"ref:`var_to_bytes() <class_@GlobalScope_method_var_to_bytes>` functions, but "
"it is also used in the ``get_var`` and ``store_var`` methods of :ref:"
"`class_FileAccess` as well as the packet APIs for :ref:`class_PacketPeer`. "
"This format is *not* used for binary scenes and resources."
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:20
msgid "Full Objects vs Object instance IDs"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:22
msgid ""
"If a variable is serialized with ``full_objects = true``, then any Objects "
"contained in the variable will be serialized and included in the result. "
"This is recursive."
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:26
msgid ""
"If ``full_objects = false``, then only the instance IDs will be serialized "
"for any Objects contained in the variable."
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:30
msgid "Packet specification"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:32
msgid ""
"The packet is designed to be always padded to 4 bytes. All values are little-"
"endian-encoded. All packets have a 4-byte header representing an integer, "
"specifying the type of data."
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:36
msgid ""
"The lowest value two bytes are used to determine the type, while the highest "
"value two bytes contain flags::"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:43
#: ../../docs/tutorials/xr/xr_action_map.rst:114
#: ../../docs/tutorials/xr/xr_action_map.rst:186
msgid "Value"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:45
#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:674
msgid "null"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:47
#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:103
msgid "bool"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:49
msgid "integer"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:51
#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:99
#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:172
#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:174
#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:176
#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:178
#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:237
msgid "float"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:55
msgid "vector2"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:57
#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:448
msgid "6"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:57
msgid "rect2"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:59
#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:450
msgid "7"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:59
msgid "vector3"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:61
#: ../../docs/tutorials/io/binary_serialization_api.rst:142
#: ../../docs/tutorials/io/binary_serialization_api.rst:162
#: ../../docs/tutorials/io/binary_serialization_api.rst:173
#: ../../docs/tutorials/io/binary_serialization_api.rst:186
#: ../../docs/tutorials/io/binary_serialization_api.rst:197
#: ../../docs/tutorials/io/binary_serialization_api.rst:212
#: ../../docs/tutorials/io/binary_serialization_api.rst:225
#: ../../docs/tutorials/io/binary_serialization_api.rst:244
#: ../../docs/tutorials/io/binary_serialization_api.rst:259
#: ../../docs/tutorials/io/binary_serialization_api.rst:274
#: ../../docs/tutorials/io/binary_serialization_api.rst:293
#: ../../docs/tutorials/io/binary_serialization_api.rst:318
#: ../../docs/tutorials/io/binary_serialization_api.rst:349
#: ../../docs/tutorials/io/binary_serialization_api.rst:371
#: ../../docs/tutorials/io/binary_serialization_api.rst:384
#: ../../docs/tutorials/io/binary_serialization_api.rst:423
#: ../../docs/tutorials/io/binary_serialization_api.rst:434
#: ../../docs/tutorials/io/binary_serialization_api.rst:516
#: ../../docs/tutorials/io/binary_serialization_api.rst:518
#: ../../docs/tutorials/io/binary_serialization_api.rst:540
#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:452
msgid "8"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:61
msgid "transform2d"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:63
#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:454
msgid "9"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:63
msgid "plane"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:65
msgid "quaternion"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:67
msgid "aabb"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:69
msgid "basis"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:71
msgid "13"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:71
msgid "transform3d"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:73
msgid "14"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:73
msgid "color"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:75
msgid "15"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:75
msgid "node path"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:77
#: ../../docs/tutorials/io/binary_serialization_api.rst:201
#: ../../docs/tutorials/io/binary_serialization_api.rst:229
#: ../../docs/tutorials/io/binary_serialization_api.rst:248
#: ../../docs/tutorials/io/binary_serialization_api.rst:263
#: ../../docs/tutorials/io/binary_serialization_api.rst:278
#: ../../docs/tutorials/io/binary_serialization_api.rst:297
#: ../../docs/tutorials/io/binary_serialization_api.rst:322
#: ../../docs/tutorials/io/binary_serialization_api.rst:353
msgid "16"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:77
msgid "rid"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:79
msgid "17"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:79
msgid "object"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:81
msgid "18"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:81
msgid "dictionary"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:83
msgid "19"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:83
msgid "array"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:85
#: ../../docs/tutorials/io/binary_serialization_api.rst:231
#: ../../docs/tutorials/io/binary_serialization_api.rst:280
#: ../../docs/tutorials/io/binary_serialization_api.rst:299
#: ../../docs/tutorials/io/binary_serialization_api.rst:324
msgid "20"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:85
msgid "raw array"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:87
msgid "21"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:87
msgid "int32 array"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:89
msgid "22"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:89
msgid "int64 array"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:91
msgid "23"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:91
msgid "float32 array"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:93
#: ../../docs/tutorials/io/binary_serialization_api.rst:233
#: ../../docs/tutorials/io/binary_serialization_api.rst:282
#: ../../docs/tutorials/io/binary_serialization_api.rst:301
#: ../../docs/tutorials/io/binary_serialization_api.rst:326
msgid "24"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:93
msgid "float64 array"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:95
msgid "25"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:95
msgid "string array"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:97
msgid "26"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:97
msgid "vector2 array"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:99
msgid "27"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:99
msgid "vector3 array"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:101
#: ../../docs/tutorials/io/binary_serialization_api.rst:303
#: ../../docs/tutorials/io/binary_serialization_api.rst:328
msgid "28"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:101
msgid "color array"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:103
msgid "29"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:103
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:164
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:148
msgid "max"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:106
msgid ""
"Following this is the actual packet contents, which varies for each type of "
"packet. Note that this assumes Godot is compiled with single-precision "
"floats, which is the default. If Godot was compiled with double-precision "
"floats, the length of \"Float\" fields within data structures should be 8, "
"and the offset should be ``(offset - 4) * 2 + 4``. The \"float\" type itself "
"always uses double precision."
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:114
msgid "0: null"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:117
msgid "1: :ref:`bool<class_bool>`"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:120
#: ../../docs/tutorials/io/binary_serialization_api.rst:131
#: ../../docs/tutorials/io/binary_serialization_api.rst:140
#: ../../docs/tutorials/io/binary_serialization_api.rst:151
#: ../../docs/tutorials/io/binary_serialization_api.rst:160
#: ../../docs/tutorials/io/binary_serialization_api.rst:169
#: ../../docs/tutorials/io/binary_serialization_api.rst:182
#: ../../docs/tutorials/io/binary_serialization_api.rst:193
#: ../../docs/tutorials/io/binary_serialization_api.rst:208
#: ../../docs/tutorials/io/binary_serialization_api.rst:221
#: ../../docs/tutorials/io/binary_serialization_api.rst:240
#: ../../docs/tutorials/io/binary_serialization_api.rst:255
#: ../../docs/tutorials/io/binary_serialization_api.rst:270
#: ../../docs/tutorials/io/binary_serialization_api.rst:289
#: ../../docs/tutorials/io/binary_serialization_api.rst:314
#: ../../docs/tutorials/io/binary_serialization_api.rst:345
#: ../../docs/tutorials/io/binary_serialization_api.rst:360
#: ../../docs/tutorials/io/binary_serialization_api.rst:369
#: ../../docs/tutorials/io/binary_serialization_api.rst:380
#: ../../docs/tutorials/io/binary_serialization_api.rst:390
#: ../../docs/tutorials/io/binary_serialization_api.rst:412
#: ../../docs/tutorials/io/binary_serialization_api.rst:421
#: ../../docs/tutorials/io/binary_serialization_api.rst:430
#: ../../docs/tutorials/io/binary_serialization_api.rst:442
#: ../../docs/tutorials/io/binary_serialization_api.rst:466
#: ../../docs/tutorials/io/binary_serialization_api.rst:478
#: ../../docs/tutorials/io/binary_serialization_api.rst:490
#: ../../docs/tutorials/io/binary_serialization_api.rst:503
#: ../../docs/tutorials/io/binary_serialization_api.rst:514
#: ../../docs/tutorials/io/binary_serialization_api.rst:525
#: ../../docs/tutorials/io/binary_serialization_api.rst:536
#: ../../docs/tutorials/io/binary_serialization_api.rst:547
#: ../../docs/tutorials/io/binary_serialization_api.rst:555
#: ../../docs/tutorials/io/binary_serialization_api.rst:568
#: ../../docs/tutorials/io/binary_serialization_api.rst:581
#: ../../docs/tutorials/io/binary_serialization_api.rst:596
msgid "Offset"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:120
#: ../../docs/tutorials/io/binary_serialization_api.rst:131
#: ../../docs/tutorials/io/binary_serialization_api.rst:140
#: ../../docs/tutorials/io/binary_serialization_api.rst:151
#: ../../docs/tutorials/io/binary_serialization_api.rst:160
#: ../../docs/tutorials/io/binary_serialization_api.rst:169
#: ../../docs/tutorials/io/binary_serialization_api.rst:182
#: ../../docs/tutorials/io/binary_serialization_api.rst:193
#: ../../docs/tutorials/io/binary_serialization_api.rst:208
#: ../../docs/tutorials/io/binary_serialization_api.rst:221
#: ../../docs/tutorials/io/binary_serialization_api.rst:240
#: ../../docs/tutorials/io/binary_serialization_api.rst:255
#: ../../docs/tutorials/io/binary_serialization_api.rst:270
#: ../../docs/tutorials/io/binary_serialization_api.rst:289
#: ../../docs/tutorials/io/binary_serialization_api.rst:314
#: ../../docs/tutorials/io/binary_serialization_api.rst:345
#: ../../docs/tutorials/io/binary_serialization_api.rst:360
#: ../../docs/tutorials/io/binary_serialization_api.rst:369
#: ../../docs/tutorials/io/binary_serialization_api.rst:380
#: ../../docs/tutorials/io/binary_serialization_api.rst:390
#: ../../docs/tutorials/io/binary_serialization_api.rst:412
#: ../../docs/tutorials/io/binary_serialization_api.rst:421
#: ../../docs/tutorials/io/binary_serialization_api.rst:430
#: ../../docs/tutorials/io/binary_serialization_api.rst:442
#: ../../docs/tutorials/io/binary_serialization_api.rst:466
#: ../../docs/tutorials/io/binary_serialization_api.rst:478
#: ../../docs/tutorials/io/binary_serialization_api.rst:490
#: ../../docs/tutorials/io/binary_serialization_api.rst:503
#: ../../docs/tutorials/io/binary_serialization_api.rst:514
#: ../../docs/tutorials/io/binary_serialization_api.rst:525
#: ../../docs/tutorials/io/binary_serialization_api.rst:536
#: ../../docs/tutorials/io/binary_serialization_api.rst:547
#: ../../docs/tutorials/io/binary_serialization_api.rst:555
#: ../../docs/tutorials/io/binary_serialization_api.rst:568
#: ../../docs/tutorials/io/binary_serialization_api.rst:581
#: ../../docs/tutorials/io/binary_serialization_api.rst:596
msgid "Len"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:122
#: ../../docs/tutorials/io/binary_serialization_api.rst:133
#: ../../docs/tutorials/io/binary_serialization_api.rst:142
#: ../../docs/tutorials/io/binary_serialization_api.rst:171
#: ../../docs/tutorials/io/binary_serialization_api.rst:362
#: ../../docs/tutorials/io/binary_serialization_api.rst:382
#: ../../docs/tutorials/io/binary_serialization_api.rst:384
#: ../../docs/tutorials/io/binary_serialization_api.rst:392
#: ../../docs/tutorials/io/binary_serialization_api.rst:414
#: ../../docs/tutorials/io/binary_serialization_api.rst:423
#: ../../docs/tutorials/io/binary_serialization_api.rst:432
#: ../../docs/tutorials/io/binary_serialization_api.rst:436
#: ../../docs/tutorials/io/binary_serialization_api.rst:444
#: ../../docs/tutorials/io/binary_serialization_api.rst:468
#: ../../docs/tutorials/io/binary_serialization_api.rst:480
#: ../../docs/tutorials/io/binary_serialization_api.rst:492
#: ../../docs/tutorials/io/binary_serialization_api.rst:505
#: ../../docs/tutorials/io/binary_serialization_api.rst:507
#: ../../docs/tutorials/io/binary_serialization_api.rst:516
#: ../../docs/tutorials/io/binary_serialization_api.rst:518
#: ../../docs/tutorials/io/binary_serialization_api.rst:527
#: ../../docs/tutorials/io/binary_serialization_api.rst:529
#: ../../docs/tutorials/io/binary_serialization_api.rst:538
#: ../../docs/tutorials/io/binary_serialization_api.rst:540
#: ../../docs/tutorials/io/binary_serialization_api.rst:549
#: ../../docs/tutorials/io/binary_serialization_api.rst:557
#: ../../docs/tutorials/io/binary_serialization_api.rst:570
#: ../../docs/tutorials/io/binary_serialization_api.rst:583
#: ../../docs/tutorials/io/binary_serialization_api.rst:598
#: ../../docs/tutorials/scripting/gdscript/gdscript_format_string.rst:142
msgid "Integer"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:122
msgid "0 for False, 1 for True"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:126
msgid "2: :ref:`int<class_int>`"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:128
msgid ""
"If no flags are set (flags == 0), the integer is sent as a 32 bit integer:"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:133
#: ../../docs/tutorials/io/binary_serialization_api.rst:507
msgid "32-bit signed integer"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:136
msgid ""
"If flag ``ENCODE_FLAG_64`` is set (``flags & 1 == 1``), the integer is sent "
"as a 64-bit integer:"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:142
#: ../../docs/tutorials/io/binary_serialization_api.rst:518
msgid "64-bit signed integer"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:146
#, fuzzy
msgid "3: :ref:`float<class_float>`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/io/binary_serialization_api.rst:148
msgid ""
"If no flags are set (flags == 0), the float is sent as a 32 bit single "
"precision:"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:153
#: ../../docs/tutorials/io/binary_serialization_api.rst:162
#: ../../docs/tutorials/io/binary_serialization_api.rst:184
#: ../../docs/tutorials/io/binary_serialization_api.rst:186
#: ../../docs/tutorials/io/binary_serialization_api.rst:195
#: ../../docs/tutorials/io/binary_serialization_api.rst:197
#: ../../docs/tutorials/io/binary_serialization_api.rst:199
#: ../../docs/tutorials/io/binary_serialization_api.rst:201
#: ../../docs/tutorials/io/binary_serialization_api.rst:210
#: ../../docs/tutorials/io/binary_serialization_api.rst:212
#: ../../docs/tutorials/io/binary_serialization_api.rst:214
#: ../../docs/tutorials/io/binary_serialization_api.rst:223
#: ../../docs/tutorials/io/binary_serialization_api.rst:225
#: ../../docs/tutorials/io/binary_serialization_api.rst:227
#: ../../docs/tutorials/io/binary_serialization_api.rst:229
#: ../../docs/tutorials/io/binary_serialization_api.rst:231
#: ../../docs/tutorials/io/binary_serialization_api.rst:233
#: ../../docs/tutorials/io/binary_serialization_api.rst:242
#: ../../docs/tutorials/io/binary_serialization_api.rst:244
#: ../../docs/tutorials/io/binary_serialization_api.rst:246
#: ../../docs/tutorials/io/binary_serialization_api.rst:248
#: ../../docs/tutorials/io/binary_serialization_api.rst:257
#: ../../docs/tutorials/io/binary_serialization_api.rst:259
#: ../../docs/tutorials/io/binary_serialization_api.rst:261
#: ../../docs/tutorials/io/binary_serialization_api.rst:263
#: ../../docs/tutorials/io/binary_serialization_api.rst:272
#: ../../docs/tutorials/io/binary_serialization_api.rst:274
#: ../../docs/tutorials/io/binary_serialization_api.rst:276
#: ../../docs/tutorials/io/binary_serialization_api.rst:278
#: ../../docs/tutorials/io/binary_serialization_api.rst:280
#: ../../docs/tutorials/io/binary_serialization_api.rst:282
#: ../../docs/tutorials/io/binary_serialization_api.rst:291
#: ../../docs/tutorials/io/binary_serialization_api.rst:293
#: ../../docs/tutorials/io/binary_serialization_api.rst:295
#: ../../docs/tutorials/io/binary_serialization_api.rst:297
#: ../../docs/tutorials/io/binary_serialization_api.rst:299
#: ../../docs/tutorials/io/binary_serialization_api.rst:301
#: ../../docs/tutorials/io/binary_serialization_api.rst:303
#: ../../docs/tutorials/io/binary_serialization_api.rst:305
#: ../../docs/tutorials/io/binary_serialization_api.rst:307
#: ../../docs/tutorials/io/binary_serialization_api.rst:316
#: ../../docs/tutorials/io/binary_serialization_api.rst:318
#: ../../docs/tutorials/io/binary_serialization_api.rst:320
#: ../../docs/tutorials/io/binary_serialization_api.rst:322
#: ../../docs/tutorials/io/binary_serialization_api.rst:324
#: ../../docs/tutorials/io/binary_serialization_api.rst:326
#: ../../docs/tutorials/io/binary_serialization_api.rst:328
#: ../../docs/tutorials/io/binary_serialization_api.rst:330
#: ../../docs/tutorials/io/binary_serialization_api.rst:332
#: ../../docs/tutorials/io/binary_serialization_api.rst:334
#: ../../docs/tutorials/io/binary_serialization_api.rst:336
#: ../../docs/tutorials/io/binary_serialization_api.rst:338
#: ../../docs/tutorials/io/binary_serialization_api.rst:347
#: ../../docs/tutorials/io/binary_serialization_api.rst:349
#: ../../docs/tutorials/io/binary_serialization_api.rst:351
#: ../../docs/tutorials/io/binary_serialization_api.rst:353
#: ../../docs/tutorials/io/binary_serialization_api.rst:572
#: ../../docs/tutorials/io/binary_serialization_api.rst:574
#: ../../docs/tutorials/io/binary_serialization_api.rst:585
#: ../../docs/tutorials/io/binary_serialization_api.rst:587
#: ../../docs/tutorials/io/binary_serialization_api.rst:589
#: ../../docs/tutorials/io/binary_serialization_api.rst:600
#: ../../docs/tutorials/io/binary_serialization_api.rst:602
#: ../../docs/tutorials/io/binary_serialization_api.rst:604
#: ../../docs/tutorials/io/binary_serialization_api.rst:606
msgid "Float"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:153
msgid "IEEE 754 single-precision float"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:156
msgid ""
"If flag ``ENCODE_FLAG_64`` is set (``flags & 1 == 1``), the float is sent as "
"a 64-bit double precision number:"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:162
msgid "IEEE 754 double-precision float"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:166
msgid "4: :ref:`String<class_string>`"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:171
msgid "String length (in bytes)"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:173
#: ../../docs/tutorials/io/binary_serialization_api.rst:371
#: ../../docs/tutorials/io/binary_serialization_api.rst:394
#: ../../docs/tutorials/io/binary_serialization_api.rst:434
#: ../../docs/tutorials/io/binary_serialization_api.rst:559
msgid "X"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:173
#: ../../docs/tutorials/io/binary_serialization_api.rst:371
#: ../../docs/tutorials/io/binary_serialization_api.rst:394
#: ../../docs/tutorials/io/binary_serialization_api.rst:434
#: ../../docs/tutorials/io/binary_serialization_api.rst:446
#: ../../docs/tutorials/io/binary_serialization_api.rst:559
msgid "Bytes"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:173
#: ../../docs/tutorials/io/binary_serialization_api.rst:371
#: ../../docs/tutorials/io/binary_serialization_api.rst:394
#: ../../docs/tutorials/io/binary_serialization_api.rst:559
msgid "UTF-8 encoded string"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:176
msgid "This field is padded to 4 bytes."
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:179
msgid "5: :ref:`Vector2<class_vector2>`"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:184
#: ../../docs/tutorials/io/binary_serialization_api.rst:195
#: ../../docs/tutorials/io/binary_serialization_api.rst:210
#: ../../docs/tutorials/io/binary_serialization_api.rst:272
#: ../../docs/tutorials/io/binary_serialization_api.rst:572
#: ../../docs/tutorials/io/binary_serialization_api.rst:585
msgid "X coordinate"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:186
#: ../../docs/tutorials/io/binary_serialization_api.rst:197
#: ../../docs/tutorials/io/binary_serialization_api.rst:212
#: ../../docs/tutorials/io/binary_serialization_api.rst:274
#: ../../docs/tutorials/io/binary_serialization_api.rst:574
#: ../../docs/tutorials/io/binary_serialization_api.rst:587
msgid "Y coordinate"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:190
msgid "6: :ref:`Rect2<class_rect2>`"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:199
#: ../../docs/tutorials/io/binary_serialization_api.rst:278
msgid "X size"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:201
#: ../../docs/tutorials/io/binary_serialization_api.rst:280
msgid "Y size"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:205
msgid "7: :ref:`Vector3<class_vector3>`"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:214
#: ../../docs/tutorials/io/binary_serialization_api.rst:276
#: ../../docs/tutorials/io/binary_serialization_api.rst:589
msgid "Z coordinate"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:218
msgid "8: :ref:`Transform2D<class_transform2d>`"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:223
#: ../../docs/tutorials/io/binary_serialization_api.rst:291
#: ../../docs/tutorials/io/binary_serialization_api.rst:316
msgid "The X component of the X column vector, accessed via [0][0]"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:225
#: ../../docs/tutorials/io/binary_serialization_api.rst:293
#: ../../docs/tutorials/io/binary_serialization_api.rst:318
msgid "The Y component of the X column vector, accessed via [0][1]"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:227
#: ../../docs/tutorials/io/binary_serialization_api.rst:297
#: ../../docs/tutorials/io/binary_serialization_api.rst:322
msgid "The X component of the Y column vector, accessed via [1][0]"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:229
#: ../../docs/tutorials/io/binary_serialization_api.rst:299
#: ../../docs/tutorials/io/binary_serialization_api.rst:324
msgid "The Y component of the Y column vector, accessed via [1][1]"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:231
msgid "The X component of the origin vector, accessed via [2][0]"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:233
msgid "The Y component of the origin vector, accessed via [2][1]"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:237
msgid "9: :ref:`Plane<class_plane>`"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:242
msgid "Normal X"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:244
msgid "Normal Y"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:246
msgid "Normal Z"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:248
msgid "Distance"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:252
#, fuzzy
msgid "10: :ref:`Quaternion<class_quaternion>`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/io/binary_serialization_api.rst:257
msgid "Imaginary X"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:259
msgid "Imaginary Y"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:261
msgid "Imaginary Z"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:263
msgid "Real W"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:267
msgid "11: :ref:`AABB<class_aabb>`"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:282
msgid "Z size"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:286
msgid "12: :ref:`Basis<class_basis>`"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:295
#: ../../docs/tutorials/io/binary_serialization_api.rst:320
msgid "The Z component of the X column vector, accessed via [0][2]"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:301
#: ../../docs/tutorials/io/binary_serialization_api.rst:326
msgid "The Z component of the Y column vector, accessed via [1][2]"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:303
#: ../../docs/tutorials/io/binary_serialization_api.rst:328
msgid "The X component of the Z column vector, accessed via [2][0]"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:305
#: ../../docs/tutorials/io/binary_serialization_api.rst:330
msgid "32"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:305
#: ../../docs/tutorials/io/binary_serialization_api.rst:330
msgid "The Y component of the Z column vector, accessed via [2][1]"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:307
#: ../../docs/tutorials/io/binary_serialization_api.rst:332
msgid "36"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:307
#: ../../docs/tutorials/io/binary_serialization_api.rst:332
msgid "The Z component of the Z column vector, accessed via [2][2]"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:311
#, fuzzy
msgid "13: :ref:`Transform3D<class_transform3d>`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/io/binary_serialization_api.rst:334
msgid "40"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:334
msgid "The X component of the origin vector, accessed via [3][0]"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:336
msgid "44"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:336
msgid "The Y component of the origin vector, accessed via [3][1]"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:338
msgid "48"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:338
msgid "The Z component of the origin vector, accessed via [3][2]"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:342
msgid "14: :ref:`Color<class_color>`"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:347
#: ../../docs/tutorials/io/binary_serialization_api.rst:600
msgid "Red (typically 0..1, can be above 1 for overbright colors)"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:349
#: ../../docs/tutorials/io/binary_serialization_api.rst:602
msgid "Green (typically 0..1, can be above 1 for overbright colors)"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:351
#: ../../docs/tutorials/io/binary_serialization_api.rst:604
msgid "Blue (typically 0..1, can be above 1 for overbright colors)"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:353
#: ../../docs/tutorials/io/binary_serialization_api.rst:606
msgid "Alpha (0..1)"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:357
msgid "15: :ref:`NodePath<class_nodepath>`"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:362
msgid ""
"String length, or new format (val&0x80000000!=0 and NameCount=val&0x7FFFFFFF)"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:366
msgid "For old format:"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:374
msgid "Padded to 4 bytes."
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:377
msgid "For new format:"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:382
msgid "Sub-name count"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:384
msgid "Flags (absolute: val&1 != 0 )"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:387
msgid "For each Name and Sub-Name"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:392
#: ../../docs/tutorials/io/binary_serialization_api.rst:557
msgid "X+0"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:392
#: ../../docs/tutorials/io/binary_serialization_api.rst:557
msgid "String length"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:394
#: ../../docs/tutorials/io/binary_serialization_api.rst:559
msgid "X+4"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:397
msgid "Every name string is padded to 4 bytes."
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:400
msgid "16: :ref:`RID<class_rid>` (unsupported)"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:403
#, fuzzy
msgid "17: :ref:`Object<class_object>`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/io/binary_serialization_api.rst:405
msgid ""
"An Object could be serialized in three different ways: as a null value, with "
"``full_objects = false``, or with ``full_objects = true``."
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:409
msgid "A null value"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:414
msgid "Zero (32-bit signed integer)"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:418
msgid "``full_objects`` disabled"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:423
msgid "The Object instance ID (64-bit signed integer)"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:427
msgid "``full_objects`` enabled"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:432
msgid "Class name (String length)"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:434
msgid "Class name (UTF-8 encoded string)"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:436
msgid "X+8"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:436
#, fuzzy
msgid "The number of properties that are serialized"
msgstr "Ne postoje ograničenja prilikom korištenja Godot-a"

#: ../../docs/tutorials/io/binary_serialization_api.rst:439
msgid "For each property:"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:444
msgid "Y"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:444
msgid "Property name (String length)"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:446
msgid "Y+4"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:446
msgid "Z"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:446
msgid "Property name (UTF-8 encoded string)"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:448
msgid "Y+4+Z"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:448
msgid "W"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:448
msgid "<variable>"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:448
msgid "Property value, using this same format"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:453
msgid ""
"Not all properties are included. Only properties that are configured with "
"the :ref:"
"`PROPERTY_USAGE_STORAGE<class_@GlobalScope_constant_PROPERTY_USAGE_STORAGE>` "
"flag set will be serialized. You can add a new usage flag to a property by "
"overriding the :ref:"
"`_get_property_list<class_Object_private_method__get_property_list>` method "
"in your class. You can also check how property usage is configured by "
"calling ``Object._get_property_list`` See :ref:"
"`PropertyUsageFlags<enum_@GlobalScope_PropertyUsageFlags>` for the possible "
"usage flags."
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:463
msgid "18: :ref:`Dictionary<class_dictionary>`"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:468
#: ../../docs/tutorials/io/binary_serialization_api.rst:480
msgid "val&0x7FFFFFFF = elements, val&0x80000000 = shared (bool)"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:471
msgid ""
"Then what follows is, for amount of \"elements\", pairs of key and value, "
"one after the other, using this same format."
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:475
msgid "19: :ref:`Array<class_array>`"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:483
msgid ""
"Then what follows is, for amount of \"elements\", values one after the "
"other, using this same format."
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:487
#, fuzzy
msgid "20: :ref:`PackedByteArray<class_PackedByteArray>`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/io/binary_serialization_api.rst:492
msgid "Array length (Bytes)"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:494
msgid "8..8+length"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:494
msgid "Byte"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:494
msgid "Byte (0..255)"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:497
msgid "The array data is padded to 4 bytes."
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:500
#, fuzzy
msgid "21: :ref:`PackedInt32Array<class_PackedInt32Array>`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/io/binary_serialization_api.rst:505
#: ../../docs/tutorials/io/binary_serialization_api.rst:516
msgid "Array length (Integers)"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:507
#: ../../docs/tutorials/io/binary_serialization_api.rst:529
msgid "8..8+length\\*4"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:511
#, fuzzy
msgid "22: :ref:`PackedInt64Array<class_PackedInt64Array>`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/io/binary_serialization_api.rst:518
#: ../../docs/tutorials/io/binary_serialization_api.rst:540
#: ../../docs/tutorials/io/binary_serialization_api.rst:572
msgid "8..8+length\\*8"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:522
#, fuzzy
msgid "23: :ref:`PackedFloat32Array<class_PackedFloat32Array>`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/io/binary_serialization_api.rst:527
#: ../../docs/tutorials/io/binary_serialization_api.rst:538
msgid "Array length (Floats)"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:529
msgid "32-bit IEEE 754 single-precision float"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:533
#, fuzzy
msgid "24: :ref:`PackedFloat64Array<class_PackedFloat64Array>`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/io/binary_serialization_api.rst:540
msgid "64-bit IEEE 754 double-precision float"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:544
#, fuzzy
msgid "25: :ref:`PackedStringArray<class_PackedStringArray>`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/io/binary_serialization_api.rst:549
msgid "Array length (Strings)"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:552
msgid "For each String:"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:562
msgid "Every string is padded to 4 bytes."
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:565
#, fuzzy
msgid "26: :ref:`PackedVector2Array<class_PackedVector2Array>`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/io/binary_serialization_api.rst:570
#: ../../docs/tutorials/io/binary_serialization_api.rst:583
#: ../../docs/tutorials/io/binary_serialization_api.rst:598
msgid "Array length"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:574
msgid "8..12+length\\*8"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:578
#, fuzzy
msgid "27: :ref:`PackedVector3Array<class_PackedVector3Array>`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/io/binary_serialization_api.rst:585
msgid "8..8+length\\*12"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:587
msgid "8..12+length\\*12"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:589
msgid "8..16+length\\*12"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:593
#, fuzzy
msgid "28: :ref:`PackedColorArray<class_PackedColorArray>`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/io/binary_serialization_api.rst:600
msgid "8..8+length\\*16"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:602
msgid "8..12+length\\*16"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:604
msgid "8..16+length\\*16"
msgstr ""

#: ../../docs/tutorials/io/binary_serialization_api.rst:606
msgid "8..20+length\\*16"
msgstr ""

#: ../../docs/tutorials/i18n/internationalizing_games.rst:4
msgid "Internationalizing games"
msgstr ""

#: ../../docs/tutorials/i18n/internationalizing_games.rst:9
msgid ""
"Sería excelente que el mundo hablara solo un idioma (It would be great if "
"the world spoke only one language). Unfortunately for us developers, that is "
"not the case. While indie or niche games usually do not need localization, "
"games targeting a more massive market often require localization. Godot "
"offers many tools to make this process more straightforward, so this "
"tutorial is more like a collection of tips and tricks."
msgstr ""

#: ../../docs/tutorials/i18n/internationalizing_games.rst:17
msgid ""
"Localization is usually done by specific studios hired for the job. Despite "
"the huge amount of software and file formats available for this, the most "
"common way to do localization to this day is still with spreadsheets. The "
"process of creating the spreadsheets and importing them is already covered "
"in the :ref:`doc_importing_translations` tutorial. If you haven't read the "
"Importing translations page before, we recommend you give it a read before "
"reading this page."
msgstr ""

#: ../../docs/tutorials/i18n/internationalizing_games.rst:25
msgid ""
"We will be using the official demo as an example; you can `download it from "
"the Asset Library <https://godotengine.org/asset-library/asset/2776>`_."
msgstr ""

#: ../../docs/tutorials/i18n/internationalizing_games.rst:29
msgid "Configuring the imported translation"
msgstr ""

#: ../../docs/tutorials/i18n/internationalizing_games.rst:31
msgid ""
"Translations can get updated and re-imported when they change, but they "
"still have to be added to the project. This is done in **Project → Project "
"Settings → Localization**:"
msgstr ""

#: ../../docs/tutorials/i18n/internationalizing_games.rst:37
msgid "The above dialog is used to add or remove translations project-wide."
msgstr ""

#: ../../docs/tutorials/i18n/internationalizing_games.rst:40
msgid "Localizing resources"
msgstr ""

#: ../../docs/tutorials/i18n/internationalizing_games.rst:42
msgid ""
"It is also possible to instruct Godot to use alternate versions of assets "
"(resources) depending on the current language. This can be used for "
"localized images such as in-game billboards or localized voices."
msgstr ""

#: ../../docs/tutorials/i18n/internationalizing_games.rst:46
msgid "The **Remaps** tab can be used for this:"
msgstr ""

#: ../../docs/tutorials/i18n/internationalizing_games.rst:50
msgid ""
"Select the resource to be remapped then add some alternatives for each "
"locale."
msgstr ""

#: ../../docs/tutorials/i18n/internationalizing_games.rst:54
msgid ""
"The resource remapping system isn't supported for DynamicFonts. To use "
"different fonts depending on the language's script, use the DynamicFont "
"fallback system instead, which lets you define as many fallback fonts as you "
"want."
msgstr ""

#: ../../docs/tutorials/i18n/internationalizing_games.rst:59
msgid ""
"The upside of the DynamicFont fallback system is that it works regardless of "
"the current language, making it ideal for things like multiplayer chat where "
"the text language may not match the client's language."
msgstr ""

#: ../../docs/tutorials/i18n/internationalizing_games.rst:64
msgid "Converting keys to text"
msgstr ""

#: ../../docs/tutorials/i18n/internationalizing_games.rst:66
msgid ""
"Some controls, such as :ref:`Button <class_Button>` and :ref:`Label "
"<class_Label>`, will automatically fetch a translation if their text matches "
"a translation key. For example, if a label's text is "
"\"MAIN_SCREEN_GREETING1\" and that key exists in the current translation, "
"then the text will automatically be translated."
msgstr ""

#: ../../docs/tutorials/i18n/internationalizing_games.rst:71
msgid ""
"This automatic translation behavior may be undesirable in certain cases. For "
"instance, when using a Label to display a player's name, you most likely "
"don't want the player's name to be translated if it matches a translation "
"key. To disable automatic translation on a specific node, disable "
"**Localization > Auto Translate** in the inspector."
msgstr ""

#: ../../docs/tutorials/i18n/internationalizing_games.rst:77
msgid ""
"In code, the :ref:`Object.tr() <class_Object_method_tr>` function can be "
"used. This will just look up the text in the translations and convert it if "
"found:"
msgstr ""

#: ../../docs/tutorials/i18n/internationalizing_games.rst:87
msgid ""
"If no text is displayed after changing the language, try to use a different "
"font. The default project font only supports a subset of the Latin-1 "
"character set, which cannot be used to display languages like Russian or "
"Chinese."
msgstr ""

#: ../../docs/tutorials/i18n/internationalizing_games.rst:91
msgid ""
"A good resource for multilingual fonts is `Noto Fonts <https://www.google."
"com/get/noto/>`__. Make sure to download the correct variation if you're "
"using a less common language."
msgstr ""

#: ../../docs/tutorials/i18n/internationalizing_games.rst:95
msgid ""
"Once you've downloaded the font, load the TTF file into a DynamicFont "
"resource and use it as a custom font of your Control node. For better "
"reusability, associate a new a Theme resource to your root Control node and "
"define the DynamicFont as the Default Font in the theme."
msgstr ""

#: ../../docs/tutorials/i18n/internationalizing_games.rst:101
msgid "Placeholders"
msgstr ""

#: ../../docs/tutorials/i18n/internationalizing_games.rst:103
msgid ""
"To feature placeholders in your translated strings, use :ref:"
"`doc_gdscript_printf` or the equivalent feature in C#. This lets translators "
"move the location of the placeholder in the string freely, which allows "
"translations to sound more natural. Named placeholders with the ``String."
"format()`` function should be used whenever possible, as they also allow "
"translators to choose the *order* in which placeholders appear:"
msgstr ""

#: ../../docs/tutorials/i18n/internationalizing_games.rst:121
#, fuzzy
msgid "Translation contexts"
msgstr "Organizacija dokumentacije"

#: ../../docs/tutorials/i18n/internationalizing_games.rst:123
msgid ""
"If you're using plain English as source strings (rather than message codes "
"``LIKE_THIS``), you may run into ambiguities when you have to translate the "
"same English string to different strings in certain target languages. You "
"can optionally specify a *translation context* to resolve this ambiguity and "
"allow target languages to use different strings, even though the source "
"string is identical:"
msgstr ""

#: ../../docs/tutorials/i18n/internationalizing_games.rst:139
msgid "Pluralization"
msgstr ""

#: ../../docs/tutorials/i18n/internationalizing_games.rst:141
msgid ""
"Most languages require different strings depending on whether an object is "
"in singular or plural form. However, hardcoding the \"is plural\" condition "
"depending on whether there is more than 1 object is not valid in all "
"languages."
msgstr ""

#: ../../docs/tutorials/i18n/internationalizing_games.rst:145
msgid ""
"Some languages have more than two plural forms, and the rules on the number "
"of objects required for each plural form vary. Godot offers support for "
"*pluralization* so that the target locales can handle this automatically."
msgstr ""

#: ../../docs/tutorials/i18n/internationalizing_games.rst:149
msgid ""
"Pluralization is meant to be used with positive (or zero) integer numbers "
"only. Negative and floating-point values usually represent physical entities "
"for which singular and plural don't clearly apply."
msgstr ""

#: ../../docs/tutorials/i18n/internationalizing_games.rst:158
#, fuzzy
msgid "This can be combined with a context if needed:"
msgstr "Glavna dokumentacija za sajt je podeljena na sledeća poglavlja:"

#: ../../docs/tutorials/i18n/internationalizing_games.rst:167
msgid ""
"Providing pluralized translations is only supported with :ref:"
"`doc_localization_using_gettext`, not CSV."
msgstr ""

#: ../../docs/tutorials/i18n/internationalizing_games.rst:171
msgid "Making controls resizable"
msgstr ""

#: ../../docs/tutorials/i18n/internationalizing_games.rst:173
msgid ""
"The same text in different languages can vary greatly in length. For this, "
"make sure to read the tutorial on :ref:`doc_size_and_anchors`, as "
"dynamically adjusting control sizes may help. :ref:`Container "
"<class_Container>` can be useful, as well as the text wrapping options "
"available in :ref:`Label <class_Label>`."
msgstr ""

#: ../../docs/tutorials/i18n/internationalizing_games.rst:179
msgid ""
"To check whether your UI can accommodate translations with longer strings "
"than the original, you can enable *pseudolocalization* in the advanced "
"Project Settings. This will replace all your localizable strings with longer "
"versions of themselves, while also replacing some characters in the original "
"strings with accented versions (while still being readable). Placeholders "
"are kept as-is, so that they keep working when pseudolocalization is enabled."
msgstr ""

#: ../../docs/tutorials/i18n/internationalizing_games.rst:186
msgid ""
"For example, the string ``Hello world, this is %s!`` becomes ``[Ĥéłłô ŵôŕłd́, "
"ŧh̀íš íš %s!]`` when pseudolocalization is enabled."
msgstr ""

#: ../../docs/tutorials/i18n/internationalizing_games.rst:189
msgid ""
"While looking strange at first, pseudolocalization has several benefits:"
msgstr ""

#: ../../docs/tutorials/i18n/internationalizing_games.rst:191
msgid ""
"It lets you spot non-localizable strings quickly, so you can go over them "
"and make them localizable (if it makes sense to do so)."
msgstr ""

#: ../../docs/tutorials/i18n/internationalizing_games.rst:193
msgid ""
"It lets you check UI elements that can't fit long strings. Many languages "
"will feature much longer translations than the source text, so it's "
"important to ensure your UI can accommodate longer-than-usual strings."
msgstr ""

#: ../../docs/tutorials/i18n/internationalizing_games.rst:196
msgid ""
"It lets you check whether your font contains all the characters required to "
"support various languages. However, since the goal of pseudolocalization is "
"to keep the original strings readable, it's not an effective test for "
"checking whether a font can support :abbr:`CJK (Chinese, Japanese, Korean)` "
"or right-to-left languages."
msgstr ""

#: ../../docs/tutorials/i18n/internationalizing_games.rst:202
msgid ""
"The project settings allow you to tune pseudolocalization behavior, so that "
"you can disable parts of it if desired."
msgstr ""

#: ../../docs/tutorials/i18n/internationalizing_games.rst:206
msgid "TranslationServer"
msgstr ""

#: ../../docs/tutorials/i18n/internationalizing_games.rst:208
msgid ""
"Godot has a server handling low-level translation management called the :ref:"
"`TranslationServer <class_TranslationServer>`. Translations can be added or "
"removed during run-time; the current language can also be changed at run-"
"time."
msgstr ""

#: ../../docs/tutorials/i18n/internationalizing_games.rst:216
msgid "Bidirectional text and UI Mirroring"
msgstr ""

#: ../../docs/tutorials/i18n/internationalizing_games.rst:218
msgid ""
"Arabic and Hebrew are written from right to left (except for the numbers and "
"Latin words mixed in), and the user interface for these languages should be "
"mirrored as well. In some languages the shape of a glyph changes depending "
"on the surrounding characters."
msgstr ""

#: ../../docs/tutorials/i18n/internationalizing_games.rst:222
msgid ""
"Support for bidirectional writing systems and UI mirroring is transparent, "
"you don't usually need to change anything or have any knowledge of the "
"specific writing system."
msgstr ""

#: ../../docs/tutorials/i18n/internationalizing_games.rst:225
msgid ""
"For RTL languages, Godot will automatically do the following changes to the "
"UI:"
msgstr ""

#: ../../docs/tutorials/i18n/internationalizing_games.rst:227
msgid "Mirrors left/right anchors and margins."
msgstr ""

#: ../../docs/tutorials/i18n/internationalizing_games.rst:228
msgid "Swaps left and right text alignment."
msgstr ""

#: ../../docs/tutorials/i18n/internationalizing_games.rst:229
msgid ""
"Mirrors horizontal order of the child controls in the containers, and items "
"in Tree/ItemList controls."
msgstr ""

#: ../../docs/tutorials/i18n/internationalizing_games.rst:230
msgid ""
"Uses mirrored order of the internal control elements (e.g. OptionButton "
"dropdown button, checkbox alignment, List column order, Tree item icons and "
"connecting line alignment, e.t.c.), in some cases mirrored controls use "
"separate theme styles."
msgstr ""

#: ../../docs/tutorials/i18n/internationalizing_games.rst:231
msgid ""
"Coordinate system is not mirrored, and non-UI nodes (sprites, e.t.c) are not "
"affected."
msgstr ""

#: ../../docs/tutorials/i18n/internationalizing_games.rst:233
msgid ""
"It is possible to override text and control layout direction by using the "
"following control properties:"
msgstr ""

#: ../../docs/tutorials/i18n/internationalizing_games.rst:235
msgid ""
"``text_direction``, sets the base text direction. When set to \"auto\", "
"direction depends on the first strong directional character in the text "
"according to the Unicode Bidirectional Algorithm,"
msgstr ""

#: ../../docs/tutorials/i18n/internationalizing_games.rst:236
msgid "``language``, overrides current project locale."
msgstr ""

#: ../../docs/tutorials/i18n/internationalizing_games.rst:237
msgid ""
"``structured_text_bidi_override`` property and ``_structured_text_parser`` "
"callback, enables special handling for structured text."
msgstr ""

#: ../../docs/tutorials/i18n/internationalizing_games.rst:238
msgid "``layout_direction``, overrides control mirroring."
msgstr ""

#: ../../docs/tutorials/i18n/internationalizing_games.rst:244
#, fuzzy
msgid ""
"You can see how right-to-left typesetting works in action using the `BiDI "
"and Font Features demo project <https://github.com/godotengine/godot-demo-"
"projects/tree/master/gui/bidi_and_font_features>`__."
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati različite Godo demo projekte "
"`Godot demo projects <https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/tutorials/i18n/internationalizing_games.rst:248
#, fuzzy
msgid "Adding break iterator data to exported project"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/i18n/internationalizing_games.rst:250
msgid ""
"Some languages are written without spaces, and word and line breaking "
"requires more than rules over character sequences. Godot includes ICU rule "
"and dictionary based, break iterator data, but this data is not included "
"into exported projects by default. To include it go to **Project → Project "
"Settings → Localization → Text Server Data** and click **Install support "
"data...**. Break iterator data is about 4 MB large."
msgstr ""

#: ../../docs/tutorials/i18n/internationalizing_games.rst:257
msgid "Structured text BiDi override"
msgstr ""

#: ../../docs/tutorials/i18n/internationalizing_games.rst:259
msgid ""
"Unicode BiDi algorithm is designed to work with natural text and it's "
"incapable of handling text with the higher level order, like file names, "
"URIs, email addresses, regular expressions or source code."
msgstr ""

#: ../../docs/tutorials/i18n/internationalizing_games.rst:265
msgid ""
"For example, the path for this shown directory structure will be displayed "
"incorrectly (top \"LineEdit\" control). \"File\" type structured text "
"override splits text into segments, then BiDi algorithm is applied to each "
"of them individually to correctly display directory names in any language "
"and preserve correct order of the folders (bottom \"LineEdit\" control)."
msgstr ""

#: ../../docs/tutorials/i18n/internationalizing_games.rst:270
msgid ""
"Custom callbacks provide a way to override BiDi for the other types of "
"structured text."
msgstr ""

#: ../../docs/tutorials/i18n/internationalizing_games.rst:273
msgid "Localizing numbers"
msgstr ""

#: ../../docs/tutorials/i18n/internationalizing_games.rst:275
msgid ""
"Controls specifically designed for number input or output (e.g. ProgressBar, "
"SpinBox) will use localized numbering system automatically, for the other "
"control :ref:`TextServer.format_number(string, language) "
"<class_TextServer_method_format_number>` can be used to convert Western "
"Arabic numbers (0..9) to the localized numbering system and :ref:`TextServer."
"parse_number(string, language) <class_TextServer_method_parse_number>` to "
"convert it back."
msgstr ""

#: ../../docs/tutorials/i18n/internationalizing_games.rst:283
msgid "Localizing icons and images"
msgstr ""

#: ../../docs/tutorials/i18n/internationalizing_games.rst:285
msgid ""
"Icons with left and right pointing arrows which may need to be reversed for "
"Arabic and Hebrew locales, in case they indicate movement or direction (e.g. "
"back/forward buttons). Otherwise, they can remain the same."
msgstr ""

#: ../../docs/tutorials/i18n/internationalizing_games.rst:290
#, fuzzy
msgid "Testing translations"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/i18n/internationalizing_games.rst:292
msgid ""
"You may want to test a project's translation before releasing it. Godot "
"provides two ways to do this."
msgstr ""

#: ../../docs/tutorials/i18n/internationalizing_games.rst:295
msgid ""
"First, in the Project Settings, under **Internationalization > Locale** "
"(with advanced settings enabled), there is a **Test** property. Set this "
"property to the locale code of the language you want to test. Godot will run "
"the project with that locale when the project is run (either from the editor "
"or when exported)."
msgstr ""

#: ../../docs/tutorials/i18n/internationalizing_games.rst:302
msgid ""
"Keep in mind that since this is a project setting, it will show up in "
"version control when it is set to a non-empty value. Therefore, it should be "
"set back to an empty value before committing changes to version control."
msgstr ""

#: ../../docs/tutorials/i18n/internationalizing_games.rst:306
msgid ""
"Translations can also be tested when :ref:`running Godot from the command "
"line <doc_command_line_tutorial>`. For example, to test a game in French, "
"the following argument can be supplied:"
msgstr ""

#: ../../docs/tutorials/i18n/internationalizing_games.rst:315
msgid "Translating the project name"
msgstr ""

#: ../../docs/tutorials/i18n/internationalizing_games.rst:317
msgid ""
"The project name becomes the app name when exporting to different operating "
"systems and platforms. To specify the project name in more than one "
"language, create a new setting ``application/name`` in the **Project "
"Settings** and append the locale identifier to it. For instance, for "
"Spanish, this would be ``application/name_es``:"
msgstr ""

#: ../../docs/tutorials/i18n/internationalizing_games.rst:325
msgid ""
"If you are unsure about the language code to use, refer to the :ref:`list of "
"locale codes <doc_locales>`."
msgstr ""

#: ../../docs/tutorials/i18n/localization_using_gettext.rst:4
msgid "Localization using gettext"
msgstr ""

#: ../../docs/tutorials/i18n/localization_using_gettext.rst:6
msgid ""
"In addition to :ref:`doc_importing_translations` in CSV format, Godot also "
"supports loading translation files written in the GNU gettext format (text-"
"based ``.po`` and compiled ``.mo`` since Godot 4.0)."
msgstr ""

#: ../../docs/tutorials/i18n/localization_using_gettext.rst:10
msgid ""
"For an introduction to gettext, check out `A Quick Gettext Tutorial <https://"
"www.labri.fr/perso/fleury/posts/programming/a-quick-gettext-tutorial."
"html>`_. It's written with C projects in mind, but much of the advice also "
"applies to Godot (with the exception of ``xgettext``)."
msgstr ""

#: ../../docs/tutorials/i18n/localization_using_gettext.rst:18
msgid ""
"gettext is a standard format, which can be edited using any text editor or "
"GUI editors such as `Poedit <https://poedit.net/>`_."
msgstr ""

#: ../../docs/tutorials/i18n/localization_using_gettext.rst:20
msgid ""
"gettext is supported by translation platforms such as `Transifex <https://"
"www.transifex.com/>`_ and `Weblate <https://weblate.org/>`_, which makes it "
"easier for people to collaborate to localization."
msgstr ""

#: ../../docs/tutorials/i18n/localization_using_gettext.rst:23
msgid ""
"Compared to CSV, gettext works better with version control systems like Git, "
"as each locale has its own messages file."
msgstr ""

#: ../../docs/tutorials/i18n/localization_using_gettext.rst:25
msgid ""
"Multiline strings are more convenient to edit in gettext files compared to "
"CSV files."
msgstr ""

#: ../../docs/tutorials/i18n/localization_using_gettext.rst:29
msgid "Disadvantages"
msgstr ""

#: ../../docs/tutorials/i18n/localization_using_gettext.rst:31
msgid ""
"gettext is a more complex format than CSV and can be harder to grasp for "
"people new to software localization."
msgstr ""

#: ../../docs/tutorials/i18n/localization_using_gettext.rst:33
msgid ""
"People who maintain localization files will have to install gettext tools on "
"their system. However, as Godot supports using text-based message files (``."
"po``), translators can test their work without having to install gettext "
"tools."
msgstr ""

#: ../../docs/tutorials/i18n/localization_using_gettext.rst:38
msgid "Installing gettext tools"
msgstr ""

#: ../../docs/tutorials/i18n/localization_using_gettext.rst:40
msgid ""
"The command line gettext tools are required to perform maintenance "
"operations, such as updating message files. Therefore, it's strongly "
"recommended to install them."
msgstr ""

#: ../../docs/tutorials/i18n/localization_using_gettext.rst:44
msgid ""
"**Windows:** Download an installer from `this page <https://mlocati.github."
"io/articles/gettext-iconv-windows.html>`_. Any architecture and binary type "
"(shared or static) works; if in doubt, choose the 64-bit static installer."
msgstr ""

#: ../../docs/tutorials/i18n/localization_using_gettext.rst:48
msgid ""
"**macOS:** Install gettext either using `Homebrew <https://brew.sh/>`_ with "
"the ``brew install gettext`` command, or using `MacPorts <https://www."
"macports.org/>`_ with the ``sudo port install gettext`` command."
msgstr ""

#: ../../docs/tutorials/i18n/localization_using_gettext.rst:52
msgid ""
"**Linux:** On most distributions, install the ``gettext`` package from your "
"distribution's package manager."
msgstr ""

#: ../../docs/tutorials/i18n/localization_using_gettext.rst:56
#, fuzzy
msgid "Creating the PO template"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/i18n/localization_using_gettext.rst:59
msgid "Automatic generation using the editor"
msgstr ""

#: ../../docs/tutorials/i18n/localization_using_gettext.rst:61
msgid ""
"Since Godot 4.0, the editor can generate a PO template automatically from "
"specified scene and GDScript files. This POT generation also supports "
"translation contexts and pluralization if used in a script, with the "
"optional second argument of ``tr()`` and the ``tr_n()`` method."
msgstr ""

#: ../../docs/tutorials/i18n/localization_using_gettext.rst:66
msgid ""
"Open the Project Settings' **Localization > POT Generation** tab, then use "
"the **Add…** button to specify the path to your project's scenes and scripts "
"that contain localizable strings:"
msgstr ""

#: ../../docs/tutorials/i18n/localization_using_gettext.rst:74
msgid ""
"Creating a PO template in the Localization > POT Generation tab of the "
"Project Settings"
msgstr ""

#: ../../docs/tutorials/i18n/localization_using_gettext.rst:74
msgid ""
"Creating a PO template in the **Localization > POT Generation** tab of the "
"Project Settings"
msgstr ""

#: ../../docs/tutorials/i18n/localization_using_gettext.rst:76
msgid ""
"After adding at least one scene or script, click **Generate POT** in the top-"
"right corner, then specify the path to the output file. This file can be "
"placed anywhere in the project directory, but it's recommended to keep it in "
"a subdirectory such as ``locale``, as each locale will be defined in its own "
"file."
msgstr ""

#: ../../docs/tutorials/i18n/localization_using_gettext.rst:81
msgid ""
"You can then move over to :ref:`creating a messages file from a PO template "
"<doc_localization_using_gettext_messages_file>`."
msgstr ""

#: ../../docs/tutorials/i18n/localization_using_gettext.rst:86
msgid ""
"Remember to regenerate the PO template after making any changes to "
"localizable strings, or after adding new scenes or scripts. Otherwise, newly "
"added strings will not be localizable and translators won't be able to "
"update translations for outdated strings."
msgstr ""

#: ../../docs/tutorials/i18n/localization_using_gettext.rst:92
msgid "Manual creation"
msgstr ""

#: ../../docs/tutorials/i18n/localization_using_gettext.rst:94
msgid ""
"If the automatic generation approach doesn't work out for your needs, you "
"can create a PO template by hand in a text editor. This file can be placed "
"anywhere in the project directory, but it's recommended to keep it in a "
"subdirectory, as each locale will be defined in its own file."
msgstr ""

#: ../../docs/tutorials/i18n/localization_using_gettext.rst:99
msgid ""
"Create a directory named ``locale`` in the project directory. In this "
"directory, save a file named ``messages.pot`` with the following contents:"
msgstr ""

#: ../../docs/tutorials/i18n/localization_using_gettext.rst:123
msgid ""
"Messages in gettext are made of ``msgid`` and ``msgstr`` pairs. ``msgid`` is "
"the source string (usually in English), ``msgstr`` will be the translated "
"string."
msgstr ""

#: ../../docs/tutorials/i18n/localization_using_gettext.rst:129
msgid ""
"The ``msgstr`` value in PO template files (``.pot``) should **always** be "
"empty. Localization will be done in the generated ``.po`` files instead."
msgstr ""

#: ../../docs/tutorials/i18n/localization_using_gettext.rst:135
msgid "Creating a messages file from a PO template"
msgstr ""

#: ../../docs/tutorials/i18n/localization_using_gettext.rst:137
msgid ""
"The ``msginit`` command is used to turn a PO template into a messages file. "
"For instance, to create a French localization file, use the following "
"command while in the ``locale`` directory:"
msgstr ""

#: ../../docs/tutorials/i18n/localization_using_gettext.rst:145
msgid ""
"The command above will create a file named ``fr.po`` in the same directory "
"as the PO template."
msgstr ""

#: ../../docs/tutorials/i18n/localization_using_gettext.rst:148
msgid ""
"Alternatively, you can do that graphically using Poedit, or by uploading the "
"POT file to your web platform of choice."
msgstr ""

#: ../../docs/tutorials/i18n/localization_using_gettext.rst:152
msgid "Loading a messages file in Godot"
msgstr ""

#: ../../docs/tutorials/i18n/localization_using_gettext.rst:154
msgid ""
"To register a messages file as a translation in a project, open the "
"**Project Settings**, then go to the **Localization** tab. In "
"**Translations**, click **Add…** then choose the ``.po`` or ``.mo`` file in "
"the file dialog. The locale will be inferred from the ``\"Language: "
"<code>\\n\"`` property in the messages file."
msgstr ""

#: ../../docs/tutorials/i18n/localization_using_gettext.rst:160
msgid ""
"See :ref:`doc_internationalizing_games` for more information on importing "
"and testing translations in Godot."
msgstr ""

#: ../../docs/tutorials/i18n/localization_using_gettext.rst:164
msgid "Updating message files to follow the PO template"
msgstr ""

#: ../../docs/tutorials/i18n/localization_using_gettext.rst:166
msgid ""
"After updating the PO template, you will have to update message files so "
"that they contain new strings, while removing strings that are no longer "
"present in the PO template. This can be done automatically using the "
"``msgmerge`` tool:"
msgstr ""

#: ../../docs/tutorials/i18n/localization_using_gettext.rst:176
msgid ""
"If you want to keep a backup of the original message file (which would be "
"saved as ``fr.po~`` in this example), remove the ``--backup=none`` argument."
msgstr ""

#: ../../docs/tutorials/i18n/localization_using_gettext.rst:181
msgid ""
"After running ``msgmerge``, strings which were modified in the source "
"language will have a \"fuzzy\" comment added before them in the ``.po`` "
"file. This comment denotes that the translation should be updated to match "
"the new source string, as the translation will most likely be inaccurate "
"until it's updated."
msgstr ""

#: ../../docs/tutorials/i18n/localization_using_gettext.rst:186
msgid ""
"Strings with \"fuzzy\" comments will **not** be read by Godot until the "
"translation is updated and the \"fuzzy\" comment is removed."
msgstr ""

#: ../../docs/tutorials/i18n/localization_using_gettext.rst:190
msgid "Checking the validity of a PO file or template"
msgstr ""

#: ../../docs/tutorials/i18n/localization_using_gettext.rst:192
msgid ""
"It is possible to check whether a gettext file's syntax is valid by running "
"the command below:"
msgstr ""

#: ../../docs/tutorials/i18n/localization_using_gettext.rst:199
msgid ""
"If there are syntax errors or warnings, they will be displayed in the "
"console. Otherwise, ``msgfmt`` won't output anything."
msgstr ""

#: ../../docs/tutorials/i18n/localization_using_gettext.rst:203
msgid "Using binary MO files (useful for large projects only)"
msgstr ""

#: ../../docs/tutorials/i18n/localization_using_gettext.rst:205
msgid ""
"For large projects with several thousands of strings to translate or more, "
"it can be worth it to use binary (compiled) MO message files instead of text-"
"based PO files. Binary MO files are smaller and faster to read than the "
"equivalent PO files."
msgstr ""

#: ../../docs/tutorials/i18n/localization_using_gettext.rst:210
msgid "You can generate a MO file with the command below:"
msgstr ""

#: ../../docs/tutorials/i18n/localization_using_gettext.rst:216
msgid ""
"If the PO file is valid, this command will create a ``fr.mo`` file besides "
"the PO file. This MO file can then be loaded in Godot as described above."
msgstr ""

#: ../../docs/tutorials/i18n/localization_using_gettext.rst:219
msgid ""
"The original PO file should be kept in version control so you can update "
"your translation in the future. In case you lose the original PO file and "
"wish to decompile a MO file into a text-based PO file, you can do so with:"
msgstr ""

#: ../../docs/tutorials/i18n/localization_using_gettext.rst:227
msgid ""
"The decompiled file will not include comments or fuzzy strings, as these are "
"never compiled in the MO file in the first place."
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:4
msgid "Locale codes"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:8
msgid ""
"Locale code has the following format: ``language_Script_COUNTRY_VARIANT``, "
"where:"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:10
msgid "``language`` - 2 or 3-letter language code, in lower case."
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:11
msgid "``Script`` - optional, 4-letter script code, in title case."
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:12
msgid "``COUNTRY`` - optional, 2-letter country code, in upper case."
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:13
msgid ""
"``VARIANT`` - optional, language variant, region and, sort order. A variant "
"can have any number of underscored keywords."
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:16
msgid "List of supported language codes"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:19
#, fuzzy
msgid "Language code"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/i18n/locales.rst:19
#: ../../docs/tutorials/i18n/locales.rst:1262
#: ../../docs/tutorials/i18n/locales.rst:1647
msgid "Name"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:21
msgid "aa"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:21
msgid "Afar"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:23
msgid "ab"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:23
msgid "Abkhazian"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:25
#, fuzzy
msgid "ace"
msgstr "Zameni"

#: ../../docs/tutorials/i18n/locales.rst:25
msgid "Achinese"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:27
msgid "ach"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:27
msgid "Acoli"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:29
msgid "ada"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:29
msgid "Adangme"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:31
msgid "ady"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:31
msgid "Adyghe"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:33
msgid "ae"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:33
#: ../../docs/tutorials/i18n/locales.rst:1278
msgid "Avestan"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:35
msgid "aeb"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:35
msgid "Tunisian Arabic"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:37
msgid "af"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:37
msgid "Afrikaans"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:39
msgid "afh"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:39
msgid "Afrihili"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:41
msgid "agq"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:41
msgid "Aghem"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:43
msgid "ain"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:43
msgid "Ainu"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:45
msgid "agr"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:45
msgid "Aguaruna"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:47
msgid "ak"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:47
msgid "Akan"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:49
msgid "akk"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:49
msgid "Akkadian"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:51
msgid "akz"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:51
msgid "Alabama"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:53
#, fuzzy
msgid "ale"
msgstr "Razmera"

#: ../../docs/tutorials/i18n/locales.rst:53
msgid "Aleut"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:55
msgid "aln"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:55
msgid "Gheg Albanian"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:57
msgid "alt"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:57
msgid "Southern Altai"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:59
msgid "am"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:59
msgid "Amharic"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:61
msgid "an"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:61
msgid "Aragonese"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:63
msgid "ang"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:63
msgid "Old English"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:65
msgid "anp"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:65
msgid "Angika"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:67
msgid "ar"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:67
#: ../../docs/tutorials/i18n/locales.rst:1272
msgid "Arabic"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:69
msgid "arc"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:69
msgid "Aramaic"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:71
msgid "arn"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:71
msgid "Mapudungun"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:73
msgid "aro"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:73
msgid "Araona"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:75
msgid "arp"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:75
msgid "Arapaho"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:77
msgid "arq"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:77
msgid "Algerian Arabic"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:79
msgid "ars"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:79
msgid "Najdi Arabic"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:81
msgid "arw"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:81
msgid "Arawak"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:83
msgid "ary"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:83
msgid "Moroccan Arabic"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:85
msgid "arz"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:85
msgid "Egyptian Arabic"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:87
#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:186
msgid "as"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:87
msgid "Assamese"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:89
msgid "asa"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:89
msgid "Asu"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:91
msgid "ase"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:91
msgid "American Sign Language"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:93
msgid "ast"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:93
msgid "Asturian"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:95
msgid "av"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:95
msgid "Avaric"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:97
msgid "avk"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:97
msgid "Kotava"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:99
msgid "awa"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:99
msgid "Awadhi"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:101
msgid "ayc"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:101
msgid "Southern Aymara"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:103
msgid "ay"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:103
msgid "Aymara"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:105
msgid "az"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:105
msgid "Azerbaijani"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:107
msgid "ba"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:107
msgid "Bashkir"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:109
msgid "bal"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:109
msgid "Baluchi"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:111
msgid "ban"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:111
#: ../../docs/tutorials/i18n/locales.rst:1280
msgid "Balinese"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:113
msgid "bar"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:113
msgid "Bavarian"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:115
msgid "bas"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:115
msgid "Bassa"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:117
msgid "bax"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:117
msgid "Bamun"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:119
msgid "bbc"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:119
msgid "Batak Toba"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:121
msgid "bbj"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:121
msgid "Ghomala"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:123
msgid "be"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:123
msgid "Belarusian"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:125
msgid "bej"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:125
msgid "Beja"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:127
msgid "bem"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:127
msgid "Bemba"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:129
msgid "ber"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:129
msgid "Berber"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:131
msgid "bew"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:131
msgid "Betawi"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:133
msgid "bez"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:133
msgid "Bena"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:135
msgid "bfd"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:135
msgid "Bafut"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:137
msgid "bfq"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:137
msgid "Badaga"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:139
msgid "bg"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:139
msgid "Bulgarian"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:141
msgid "bhb"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:141
msgid "Bhili"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:143
msgid "bgn"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:143
msgid "Western Balochi"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:145
msgid "bho"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:145
msgid "Bhojpuri"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:147
msgid "bi"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:147
msgid "Bislama"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:149
msgid "bik"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:149
msgid "Bikol"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:151
msgid "bin"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:151
msgid "Bini"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:153
msgid "bjn"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:153
msgid "Banjar"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:155
msgid "bkm"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:155
msgid "Kom"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:157
msgid "bla"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:157
msgid "Siksika"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:159
msgid "bm"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:159
msgid "Bambara"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:161
msgid "bn"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:161
#: ../../docs/tutorials/i18n/locales.rst:1288
msgid "Bengali"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:163
msgid "bo"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:163
#: ../../docs/tutorials/i18n/locales.rst:1610
msgid "Tibetan"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:165
msgid "bpy"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:165
msgid "Bishnupriya"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:167
msgid "bqi"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:167
msgid "Bakhtiari"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:169
msgid "br"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:169
msgid "Breton"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:171
msgid "brh"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:171
msgid "Brahui"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:173
msgid "brx"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:173
msgid "Bodo"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:175
msgid "bs"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:175
msgid "Bosnian"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:177
msgid "bss"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:177
msgid "Akoose"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:179
msgid "bua"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:179
msgid "Buriat"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:181
msgid "bug"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:181
#: ../../docs/tutorials/i18n/locales.rst:1300
msgid "Buginese"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:183
msgid "bum"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:183
msgid "Bulu"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:185
msgid "byn"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:185
msgid "Bilin"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:187
msgid "byv"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:187
msgid "Medumba"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:189
msgid "ca"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:189
msgid "Catalan"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:191
msgid "cad"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:191
msgid "Caddo"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:193
msgid "car"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:193
msgid "Carib"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:195
msgid "cay"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:195
msgid "Cayuga"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:197
msgid "cch"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:197
msgid "Atsam"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:199
msgid "ccp"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:199
#: ../../docs/tutorials/i18n/locales.rst:1304
msgid "Chakma"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:201
msgid "ce"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:201
msgid "Chechen"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:203
msgid "ceb"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:203
msgid "Cebuano"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:205
msgid "cgg"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:205
msgid "Chiga"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:207
msgid "ch"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:207
msgid "Chamorro"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:209
msgid "chb"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:209
msgid "Chibcha"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:211
msgid "chg"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:211
msgid "Chagatai"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:213
msgid "chk"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:213
msgid "Chuukese"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:215
msgid "chm"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:215
msgid "Mari"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:217
msgid "chn"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:217
msgid "Chinook Jargon"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:219
msgid "cho"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:219
msgid "Choctaw"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:221
msgid "chp"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:221
msgid "Chipewyan"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:223
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:383
msgid "chr"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:223
#: ../../docs/tutorials/i18n/locales.rst:1312
msgid "Cherokee"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:225
msgid "chy"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:225
msgid "Cheyenne"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:227
msgid "cic"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:227
msgid "Chickasaw"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:229
msgid "ckb"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:229
msgid "Central Kurdish"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:231
#: ../../docs/tutorials/i18n/locales.rst:249
msgid "csb"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:231
#: ../../docs/tutorials/i18n/locales.rst:249
msgid "Kashubian"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:233
msgid "cmn"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:233
msgid "Mandarin Chinese"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:235
msgid "co"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:235
msgid "Corsican"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:237
msgid "cop"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:237
#: ../../docs/tutorials/i18n/locales.rst:1318
msgid "Coptic"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:239
msgid "cps"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:239
msgid "Capiznon"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:241
msgid "cr"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:241
msgid "Cree"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:243
msgid "crh"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:243
msgid "Crimean Tatar"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:245
msgid "crs"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:245
msgid "Seselwa Creole French"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:247
msgid "cs"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:247
msgid "Czech"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:251
msgid "cu"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:251
msgid "Church Slavic"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:253
msgid "cv"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:253
msgid "Chuvash"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:255
msgid "cy"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:255
msgid "Welsh"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:257
msgid "da"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:257
msgid "Danish"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:259
msgid "dak"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:259
msgid "Dakota"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:261
msgid "dar"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:261
msgid "Dargwa"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:263
msgid "dav"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:263
msgid "Taita"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:265
msgid "de"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:265
msgid "German"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:267
msgid "del"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:267
msgid "Delaware"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:269
msgid "den"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:269
msgid "Slave"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:271
msgid "dgr"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:271
msgid "Dogrib"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:273
msgid "din"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:273
msgid "Dinka"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:275
msgid "dje"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:275
msgid "Zarma"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:277
msgid "doi"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:277
msgid "Dogri"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:279
msgid "dsb"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:279
msgid "Lower Sorbian"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:281
msgid "dtp"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:281
msgid "Central Dusun"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:283
msgid "dua"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:283
msgid "Duala"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:285
msgid "dum"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:285
msgid "Middle Dutch"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:287
msgid "dv"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:287
msgid "Dhivehi"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:289
msgid "dyo"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:289
msgid "Jola-Fonyi"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:291
msgid "dyu"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:291
msgid "Dyula"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:293
msgid "dz"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:293
msgid "Dzongkha"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:295
msgid "dzg"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:295
msgid "Dazaga"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:297
msgid "ebu"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:297
msgid "Embu"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:299
msgid "ee"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:299
msgid "Ewe"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:301
msgid "efi"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:301
msgid "Efik"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:303
msgid "egl"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:303
msgid "Emilian"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:305
msgid "egy"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:305
msgid "Ancient Egyptian"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:307
msgid "eka"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:307
msgid "Ekajuk"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:309
msgid "el"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:309
#: ../../docs/tutorials/i18n/locales.rst:1362
msgid "Greek"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:311
msgid "elx"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:311
msgid "Elamite"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:313
msgid "English"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:315
msgid "enm"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:315
msgid "Middle English"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:317
msgid "eo"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:317
msgid "Esperanto"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:319
msgid "Spanish"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:321
msgid "esu"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:321
msgid "Central Yupik"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:323
msgid "et"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:323
msgid "Estonian"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:325
msgid "eu"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:325
msgid "Basque"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:327
msgid "ewo"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:327
msgid "Ewondo"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:329
msgid "ext"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:329
msgid "Extremaduran"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:331
msgid "fa"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:331
msgid "Persian"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:333
msgid "fan"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:333
msgid "Fang"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:335
msgid "fat"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:335
msgid "Fanti"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:337
msgid "ff"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:337
msgid "Fulah"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:339
msgid "fi"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:339
msgid "Finnish"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:341
msgid "fil"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:341
msgid "Filipino"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:343
msgid "fit"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:343
msgid "Tornedalen Finnish"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:345
msgid "fj"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:345
msgid "Fijian"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:347
msgid "fo"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:347
msgid "Faroese"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:349
msgid "fon"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:349
msgid "Fon"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:351
msgid "fr"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:351
msgid "French"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:353
msgid "frc"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:353
msgid "Cajun French"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:355
msgid "frm"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:355
msgid "Middle French"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:357
msgid "fro"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:357
msgid "Old French"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:359
msgid "frp"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:359
msgid "Arpitan"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:361
msgid "frr"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:361
msgid "Northern Frisian"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:363
msgid "frs"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:363
msgid "Eastern Frisian"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:365
msgid "fur"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:365
msgid "Friulian"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:367
msgid "fy"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:367
msgid "Western Frisian"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:369
msgid "ga"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:369
msgid "Irish"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:371
msgid "gaa"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:371
msgid "Ga"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:373
msgid "gag"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:373
msgid "Gagauz"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:375
msgid "gan"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:375
msgid "Gan Chinese"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:377
msgid "gay"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:377
msgid "Gayo"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:379
msgid "gba"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:379
msgid "Gbaya"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:381
msgid "gbz"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:381
msgid "Zoroastrian Dari"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:383
msgid "gd"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:383
msgid "Scottish Gaelic"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:385
msgid "gez"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:385
msgid "Geez"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:387
msgid "gil"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:387
msgid "Gilbertese"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:389
msgid "gl"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:389
msgid "Galician"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:391
msgid "glk"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:391
msgid "Gilaki"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:393
msgid "gmh"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:393
msgid "Middle High German"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:395
msgid "gn"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:395
msgid "Guarani"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:397
msgid "goh"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:397
msgid "Old High German"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:399
msgid "gom"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:399
msgid "Goan Konkani"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:401
msgid "gon"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:401
msgid "Gondi"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:403
msgid "gor"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:403
msgid "Gorontalo"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:405
msgid "got"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:405
#: ../../docs/tutorials/i18n/locales.rst:1358
msgid "Gothic"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:407
msgid "grb"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:407
msgid "Grebo"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:409
msgid "grc"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:409
msgid "Ancient Greek"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:411
msgid "gsw"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:411
msgid "Swiss German"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:413
msgid "gu"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:413
#: ../../docs/tutorials/i18n/locales.rst:1364
msgid "Gujarati"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:415
msgid "guc"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:415
msgid "Wayuu"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:417
msgid "gur"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:417
msgid "Frafra"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:419
msgid "guz"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:419
msgid "Gusii"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:421
msgid "gv"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:421
msgid "Manx"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:423
msgid "gwi"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:423
msgid "Gwichʼin"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:425
msgid "ha"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:425
msgid "Hausa"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:427
msgid "hai"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:427
msgid "Haida"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:429
msgid "hak"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:429
msgid "Hakka Chinese"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:431
msgid "haw"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:431
msgid "Hawaiian"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:433
msgid "he, iw"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:433
#: ../../docs/tutorials/i18n/locales.rst:1380
msgid "Hebrew"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:435
msgid "hi"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:435
msgid "Hindi"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:437
msgid "hif"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:437
msgid "Fiji Hindi"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:439
msgid "hil"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:439
msgid "Hiligaynon"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:441
msgid "hit"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:441
msgid "Hittite"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:443
msgid "hmn"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:443
msgid "Hmong"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:445
msgid "ho"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:445
msgid "Hiri Motu"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:447
msgid "hne"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:447
msgid "Chhattisgarhi"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:449
msgid "hr"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:449
msgid "Croatian"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:451
msgid "hsb"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:451
msgid "Upper Sorbian"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:453
msgid "hsn"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:453
#, fuzzy
msgid "Xiang Chinese"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/i18n/locales.rst:455
msgid "ht"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:455
msgid "Haitian"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:457
msgid "hu"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:457
msgid "Hungarian"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:459
msgid "hup"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:459
msgid "Hupa"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:461
msgid "hus"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:461
msgid "Huastec"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:463
msgid "hy"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:463
#: ../../docs/tutorials/i18n/locales.rst:1276
msgid "Armenian"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:465
msgid "hz"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:465
msgid "Herero"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:467
msgid "ia"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:467
msgid "Interlingua"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:469
msgid "iba"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:469
msgid "Iban"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:471
msgid "ibb"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:471
msgid "Ibibio"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:473
msgid "id, in"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:473
msgid "Indonesian"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:475
msgid "ie"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:475
msgid "Interlingue"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:477
msgid "ig"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:477
msgid "Igbo"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:479
msgid "ii"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:479
msgid "Sichuan Yi"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:481
msgid "ik"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:481
msgid "Inupiaq"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:483
msgid "ilo"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:483
msgid "Iloko"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:485
msgid "inh"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:485
msgid "Ingush"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:487
msgid "io"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:487
msgid "Ido"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:489
#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:182
msgid "is"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:489
msgid "Icelandic"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:491
msgid "it"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:491
msgid "Italian"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:493
msgid "iu"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:493
msgid "Inuktitut"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:495
msgid "izh"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:495
msgid "Ingrian"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:497
msgid "Japanese"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:499
msgid "jam"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:499
msgid "Jamaican Creole English"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:501
msgid "jbo"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:501
msgid "Lojban"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:503
msgid "jgo"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:503
msgid "Ngomba"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:505
msgid "jmc"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:505
msgid "Machame"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:507
msgid "jpr"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:507
msgid "Judeo-Persian"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:509
msgid "jrb"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:509
msgid "Judeo-Arabic"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:511
msgid "jut"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:511
msgid "Jutish"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:513
msgid "jv"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:513
#: ../../docs/tutorials/i18n/locales.rst:1396
msgid "Javanese"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:515
msgid "ka"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:515
#: ../../docs/tutorials/i18n/locales.rst:1350
msgid "Georgian"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:517
msgid "kaa"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:517
msgid "Kara-Kalpak"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:519
msgid "kab"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:519
msgid "Kabyle"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:521
msgid "kac"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:521
msgid "Kachin"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:523
msgid "kaj"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:523
msgid "Jju"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:525
msgid "kam"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:525
msgid "Kamba"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:527
msgid "kaw"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:527
msgid "Kawi"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:529
msgid "kbd"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:529
msgid "Kabardian"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:531
msgid "kbl"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:531
msgid "Kanembu"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:533
msgid "kcg"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:533
msgid "Tyap"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:535
msgid "kde"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:535
msgid "Makonde"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:537
msgid "kea"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:537
msgid "Kabuverdianu"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:539
msgid "ken"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:539
msgid "Kenyang"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:541
msgid "kfo"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:541
msgid "Koro"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:543
msgid "kg"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:543
msgid "Kongo"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:545
msgid "kgp"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:545
msgid "Kaingang"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:547
msgid "kha"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:547
msgid "Khasi"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:549
msgid "kho"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:549
msgid "Khotanese"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:551
msgid "khq"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:551
msgid "Koyra Chiini"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:553
msgid "khw"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:553
msgid "Khowar"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:555
msgid "ki"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:555
msgid "Kikuyu"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:557
msgid "kiu"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:557
msgid "Kirmanjki"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:559
msgid "kj"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:559
msgid "Kuanyama"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:561
msgid "kk"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:561
msgid "Kazakh"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:563
msgid "kkj"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:563
msgid "Kako"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:565
msgid "kl"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:565
msgid "Kalaallisut"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:567
msgid "kln"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:567
msgid "Kalenjin"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:569
msgid "km"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:569
msgid "Central Khmer"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:571
msgid "kmb"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:571
msgid "Kimbundu"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:573
msgid "kn"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:573
#: ../../docs/tutorials/i18n/locales.rst:1414
msgid "Kannada"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:575
msgid "ko"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:575
msgid "Korean"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:577
msgid "koi"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:577
msgid "Komi-Permyak"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:579
msgid "kok"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:579
msgid "Konkani"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:581
msgid "kos"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:581
msgid "Kosraean"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:583
msgid "kpe"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:583
#: ../../docs/tutorials/i18n/locales.rst:1416
msgid "Kpelle"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:585
msgid "kr"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:585
msgid "Kanuri"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:587
msgid "krc"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:587
msgid "Karachay-Balkar"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:589
msgid "kri"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:589
msgid "Krio"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:591
msgid "krj"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:591
msgid "Kinaray-a"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:593
msgid "krl"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:593
msgid "Karelian"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:595
msgid "kru"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:595
msgid "Kurukh"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:597
msgid "ks"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:597
msgid "Kashmiri"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:599
msgid "ksb"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:599
msgid "Shambala"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:601
msgid "ksf"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:601
msgid "Bafia"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:603
msgid "ksh"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:603
msgid "Colognian"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:605
msgid "ku"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:605
msgid "Kurdish"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:607
msgid "kum"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:607
msgid "Kumyk"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:609
msgid "kut"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:609
msgid "Kutenai"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:611
msgid "kv"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:611
msgid "Komi"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:613
msgid "kw"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:613
msgid "Cornish"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:615
msgid "ky"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:615
msgid "Kirghiz"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:617
#: ../../docs/tutorials/i18n/locales.rst:623
msgid "lag"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:617
#: ../../docs/tutorials/i18n/locales.rst:623
msgid "Langi"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:619
msgid "la"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:619
#: ../../docs/tutorials/i18n/locales.rst:1424
msgid "Latin"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:621
msgid "lad"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:621
msgid "Ladino"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:625
msgid "lah"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:625
msgid "Lahnda"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:627
msgid "lam"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:627
msgid "Lamba"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:629
msgid "lb"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:629
msgid "Luxembourgish"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:631
msgid "lez"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:631
msgid "Lezghian"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:633
msgid "lfn"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:633
msgid "Lingua Franca Nova"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:635
msgid "lg"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:635
msgid "Ganda"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:637
msgid "li"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:637
msgid "Limburgan"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:639
msgid "lij"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:639
msgid "Ligurian"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:641
msgid "liv"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:641
msgid "Livonian"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:643
msgid "lkt"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:643
msgid "Lakota"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:645
msgid "lmo"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:645
msgid "Lombard"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:647
msgid "ln"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:647
msgid "Lingala"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:649
msgid "lo"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:649
#: ../../docs/tutorials/i18n/locales.rst:1422
msgid "Lao"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:651
msgid "lol"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:651
msgid "Mongo"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:653
msgid "lou"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:653
msgid "Louisiana Creole"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:655
msgid "loz"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:655
msgid "Lozi"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:657
msgid "lrc"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:657
msgid "Northern Luri"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:659
msgid "lt"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:659
msgid "Lithuanian"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:661
msgid "ltg"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:661
msgid "Latgalian"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:663
msgid "lu"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:663
msgid "Luba-Katanga"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:665
msgid "lua"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:665
msgid "Luba-Lulua"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:667
msgid "lui"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:667
msgid "Luiseno"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:669
msgid "lun"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:669
msgid "Lunda"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:671
msgid "luo"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:671
msgid "Luo"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:673
msgid "lus"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:673
msgid "Mizo"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:675
msgid "luy"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:675
msgid "Luyia"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:677
msgid "lv"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:677
msgid "Latvian"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:679
msgid "lzh"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:679
msgid "Literary Chinese"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:681
msgid "lzz"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:681
msgid "Laz"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:683
msgid "mad"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:683
msgid "Madurese"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:685
msgid "maf"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:685
msgid "Mafa"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:687
msgid "mag"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:687
msgid "Magahi"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:689
msgid "mai"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:689
msgid "Maithili"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:691
msgid "mak"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:691
#: ../../docs/tutorials/i18n/locales.rst:1446
msgid "Makasar"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:693
msgid "man"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:693
msgid "Mandingo"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:695
msgid "mas"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:695
msgid "Masai"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:697
msgid "mde"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:697
msgid "Maba"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:699
msgid "mdf"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:699
msgid "Moksha"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:701
msgid "mdr"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:701
msgid "Mandar"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:703
msgid "men"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:703
msgid "Mende"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:705
msgid "mer"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:705
msgid "Meru"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:707
msgid "mfe"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:707
msgid "Morisyen"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:709
msgid "mg"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:709
msgid "Malagasy"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:711
msgid "mga"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:711
msgid "Middle Irish"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:713
msgid "mgh"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:713
msgid "Makhuwa-Meetto"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:715
msgid "mgo"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:715
msgid "Metaʼ"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:717
msgid "mh"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:717
msgid "Marshallese"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:719
msgid "mhr"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:719
msgid "Eastern Mari"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:721
msgid "mi"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:721
msgid "Māori"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:723
msgid "mic"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:723
msgid "Mi'kmaq"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:725
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:167
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:149
msgid "min"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:725
msgid "Minangkabau"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:727
msgid "miq"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:727
msgid "Mískito"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:729
msgid "mjw"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:729
msgid "Karbi"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:731
msgid "mk"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:731
msgid "Macedonian"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:733
msgid "ml"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:733
#: ../../docs/tutorials/i18n/locales.rst:1464
msgid "Malayalam"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:735
msgid "mn"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:735
#: ../../docs/tutorials/i18n/locales.rst:1468
msgid "Mongolian"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:737
msgid "mnc"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:737
msgid "Manchu"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:739
msgid "mni"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:739
msgid "Manipuri"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:741
msgid "mnw"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:741
msgid "Mon"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:743
msgid "mos"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:743
msgid "Mossi"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:745
msgid "moh"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:745
msgid "Mohawk"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:747
msgid "mr"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:747
msgid "Marathi"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:749
msgid "mrj"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:749
msgid "Western Mari"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:751
msgid "ms"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:751
msgid "Malay"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:753
msgid "mt"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:753
msgid "Maltese"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:755
msgid "mua"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:755
msgid "Mundang"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:757
msgid "mus"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:757
msgid "Muscogee"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:759
msgid "mwl"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:759
msgid "Mirandese"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:761
msgid "mwr"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:761
msgid "Marwari"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:763
msgid "mwv"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:763
msgid "Mentawai"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:765
msgid "my"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:765
msgid "Burmese"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:767
msgid "mye"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:767
msgid "Myene"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:769
msgid "myv"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:769
msgid "Erzya"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:771
msgid "mzn"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:771
msgid "Mazanderani"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:773
msgid "na"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:773
#: ../../docs/tutorials/i18n/locales.rst:2005
msgid "Nauru"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:775
msgid "nah"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:775
msgid "Nahuatl"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:777
#: ../../docs/tutorials/i18n/locales.rst:783
msgid "nan"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:777
#: ../../docs/tutorials/i18n/locales.rst:783
msgid "Min Nan Chinese"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:779
msgid "nap"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:779
msgid "Neapolitan"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:781
msgid "naq"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:781
msgid "Nama"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:785
msgid "nb, no"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:785
msgid "Norwegian Bokmål"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:787
msgid "nd"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:787
msgid "North Ndebele"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:789
#, fuzzy
msgid "nds"
msgstr "Windows"

#: ../../docs/tutorials/i18n/locales.rst:789
msgid "Low German"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:791
msgid "ne"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:791
msgid "Nepali"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:793
msgid "new"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:793
msgid "Newari"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:795
msgid "nhn"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:795
msgid "Central Nahuatl"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:797
msgid "ng"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:797
msgid "Ndonga"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:799
msgid "nia"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:799
msgid "Nias"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:801
msgid "niu"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:801
msgid "Niuean"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:803
msgid "njo"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:803
msgid "Ao Naga"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:805
msgid "nl"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:805
msgid "Dutch"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:807
msgid "nmg"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:807
msgid "Kwasio"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:809
msgid "nn"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:809
msgid "Norwegian Nynorsk"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:811
msgid "nnh"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:811
msgid "Ngiemboon"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:813
msgid "nog"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:813
msgid "Nogai"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:815
msgid "non"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:815
msgid "Old Norse"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:817
msgid "nov"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:817
msgid "Novial"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:819
msgid "nqo"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:819
#: ../../docs/tutorials/i18n/locales.rst:1492
msgid "N'ko"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:821
msgid "nr"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:821
msgid "South Ndebele"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:823
msgid "nso"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:823
msgid "Pedi"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:825
msgid "nus"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:825
msgid "Nuer"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:827
msgid "nv"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:827
msgid "Navajo"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:829
msgid "nwc"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:829
msgid "Classical Newari"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:831
msgid "ny"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:831
msgid "Nyanja"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:833
msgid "nym"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:833
msgid "Nyamwezi"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:835
msgid "nyn"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:835
msgid "Nyankole"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:837
msgid "nyo"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:837
msgid "Nyoro"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:839
msgid "nzi"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:839
msgid "Nzima"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:841
msgid "oc"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:841
msgid "Occitan"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:843
msgid "oj"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:843
msgid "Ojibwa"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:845
msgid "om"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:845
msgid "Oromo"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:847
msgid "or"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:847
msgid "Odia"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:849
msgid "os"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:849
msgid "Ossetic"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:851
msgid "osa"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:851
#: ../../docs/tutorials/i18n/locales.rst:1504
msgid "Osage"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:853
msgid "ota"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:853
msgid "Ottoman Turkish"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:855
msgid "pa"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:855
msgid "Panjabi"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:857
msgid "pag"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:857
msgid "Pangasinan"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:859
msgid "pal"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:859
msgid "Pahlavi"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:861
msgid "pam"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:861
msgid "Pampanga"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:863
msgid "pap"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:863
msgid "Papiamento"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:865
msgid "pau"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:865
msgid "Palauan"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:867
msgid "pcd"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:867
msgid "Picard"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:869
msgid "pcm"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:869
msgid "Nigerian Pidgin"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:871
msgid "pdc"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:871
msgid "Pennsylvania German"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:873
msgid "pdt"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:873
msgid "Plautdietsch"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:875
msgid "peo"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:875
#: ../../docs/tutorials/i18n/locales.rst:1632
msgid "Old Persian"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:877
msgid "pfl"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:877
msgid "Palatine German"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:879
msgid "phn"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:879
#: ../../docs/tutorials/i18n/locales.rst:1528
msgid "Phoenician"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:881
msgid "pi"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:881
msgid "Pali"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:883
msgid "pl"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:883
msgid "Polish"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:885
msgid "pms"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:885
msgid "Piedmontese"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:887
msgid "pnt"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:887
msgid "Pontic"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:889
msgid "pon"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:889
msgid "Pohnpeian"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:891
msgid "pr"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:891
msgid "Pirate"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:893
msgid "prg"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:893
msgid "Prussian"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:895
msgid "pro"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:895
msgid "Old Provençal"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:897
msgid "prs"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:897
msgid "Dari"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:899
msgid "ps"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:899
msgid "Pushto"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:901
msgid "pt"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:901
msgid "Portuguese"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:903
msgid "qu"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:903
msgid "Quechua"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:905
msgid "quc"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:905
msgid "K'iche"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:907
msgid "qug"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:907
msgid "Chimborazo Highland Quichua"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:909
msgid "quy"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:909
msgid "Ayacucho Quechua"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:911
msgid "quz"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:911
msgid "Cusco Quechua"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:913
msgid "raj"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:913
msgid "Rajasthani"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:915
msgid "rap"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:915
msgid "Rapanui"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:917
msgid "rar"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:917
msgid "Rarotongan"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:919
msgid "rgn"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:919
msgid "Romagnol"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:921
msgid "rif"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:921
msgid "Riffian"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:923
msgid "rm"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:923
msgid "Romansh"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:925
msgid "rn"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:925
msgid "Rundi"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:927
msgid "ro"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:927
msgid "Romanian"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:929
msgid "rof"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:929
msgid "Rombo"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:931
msgid "rom"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:931
msgid "Romany"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:933
msgid "rtm"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:933
msgid "Rotuman"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:935
msgid "ru"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:935
msgid "Russian"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:937
msgid "rue"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:937
msgid "Rusyn"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:939
msgid "rug"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:939
msgid "Roviana"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:941
msgid "rup"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:941
msgid "Aromanian"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:943
msgid "rw"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:943
msgid "Kinyarwanda"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:945
msgid "rwk"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:945
msgid "Rwa"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:947
msgid "sa"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:947
msgid "Sanskrit"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:949
msgid "sad"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:949
msgid "Sandawe"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:951
msgid "sah"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:951
msgid "Sakha"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:953
msgid "sam"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:953
msgid "Samaritan Aramaic"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:955
msgid "saq"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:955
msgid "Samburu"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:957
msgid "sas"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:957
msgid "Sasak"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:959
msgid "sat"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:959
msgid "Santali"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:961
msgid "saz"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:961
#: ../../docs/tutorials/i18n/locales.rst:1554
msgid "Saurashtra"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:963
msgid "sba"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:963
msgid "Ngambay"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:965
msgid "sbp"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:965
msgid "Sangu"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:967
msgid "sc"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:967
msgid "Sardinian"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:969
msgid "scn"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:969
msgid "Sicilian"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:971
msgid "sco"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:971
msgid "Scots"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:973
msgid "sd"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:973
msgid "Sindhi"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:975
msgid "sdc"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:975
msgid "Sassarese Sardinian"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:977
msgid "sdh"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:977
msgid "Southern Kurdish"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:979
msgid "se"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:979
msgid "Northern Sami"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:981
msgid "see"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:981
msgid "Seneca"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:983
msgid "seh"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:983
msgid "Sena"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:985
msgid "sei"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:985
msgid "Seri"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:987
msgid "sel"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:987
msgid "Selkup"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:989
msgid "ses"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:989
msgid "Koyraboro Senni"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:991
msgid "sg"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:991
msgid "Sango"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:993
msgid "sga"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:993
msgid "Old Irish"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:995
msgid "sgs"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:995
msgid "Samogitian"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:997
msgid "sh"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:997
msgid "Serbo-Croatian"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:999
msgid "shi"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:999
msgid "Tachelhit"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1001
msgid "shn"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1001
msgid "Shan"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1003
msgid "shs"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1003
msgid "Shuswap"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1005
msgid "shu"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1005
msgid "Chadian Arabic"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1007
msgid "si"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1007
#: ../../docs/tutorials/i18n/locales.rst:1568
msgid "Sinhala"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1009
msgid "sid"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1009
msgid "Sidamo"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1011
msgid "sk"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1011
msgid "Slovak"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1013
msgid "sl"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1013
msgid "Slovenian"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1015
msgid "sli"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1015
msgid "Lower Silesian"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1017
msgid "sly"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1017
msgid "Selayar"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1019
msgid "sm"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1019
msgid "Samoan"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1021
msgid "sma"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1021
msgid "Southern Sami"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1023
msgid "smj"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1023
msgid "Lule Sami"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1025
msgid "smn"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1025
msgid "Inari Sami"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1027
msgid "sms"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1027
msgid "Skolt Sami"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1029
msgid "sn"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1029
msgid "Shona"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1031
msgid "snk"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1031
msgid "Soninke"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1033
msgid "so"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1033
msgid "Somali"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1035
msgid "sog"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1035
msgid "Sogdien"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1037
msgid "son"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1037
msgid "Songhai"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1039
msgid "sq"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1039
msgid "Albanian"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1041
msgid "sr"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1041
msgid "Serbian"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1043
msgid "srn"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1043
msgid "Sranan Tongo"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1045
msgid "srr"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1045
msgid "Serer"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1047
msgid "ss"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1047
msgid "Swati"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1049
msgid "ssy"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1049
msgid "Saho"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1051
msgid "st"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1051
msgid "Southern Sotho"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1053
msgid "stq"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1053
msgid "Saterland Frisian"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1055
msgid "su"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1055
#: ../../docs/tutorials/i18n/locales.rst:1578
msgid "Sundanese"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1057
msgid "suk"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1057
msgid "Sukuma"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1059
msgid "sus"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1059
msgid "Susu"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1061
msgid "sux"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1061
msgid "Sumerian"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1063
msgid "sv"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1063
msgid "Swedish"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1065
msgid "sw"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1065
msgid "Swahili"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1067
msgid "swb"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1067
msgid "Comorian"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1069
msgid "swc"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1069
msgid "Congo Swahili"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1071
msgid "syc"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1071
msgid "Classical Syriac"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1073
msgid "syr"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1073
#: ../../docs/tutorials/i18n/locales.rst:1582
msgid "Syriac"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1075
msgid "szl"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1075
msgid "Silesian"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1077
msgid "ta"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1077
#: ../../docs/tutorials/i18n/locales.rst:1592
msgid "Tamil"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1079
msgid "tcy"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1079
msgid "Tulu"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1081
msgid "te"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1081
#: ../../docs/tutorials/i18n/locales.rst:1598
msgid "Telugu"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1083
msgid "tem"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1083
msgid "Timne"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1085
msgid "teo"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1085
msgid "Teso"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1087
msgid "ter"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1087
msgid "Tereno"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1089
msgid "tet"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1089
msgid "Tetum"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1091
msgid "tg"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1091
msgid "Tajik"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1093
msgid "th"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1093
#: ../../docs/tutorials/i18n/locales.rst:1608
msgid "Thai"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1095
msgid "the"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1095
msgid "Chitwania Tharu"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1097
msgid "ti"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1097
msgid "Tigrinya"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1099
#, fuzzy
msgid "tig"
msgstr "Uvod / Početak"

#: ../../docs/tutorials/i18n/locales.rst:1099
msgid "Tigre"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1101
msgid "tiv"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1101
msgid "Tiv"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1103
msgid "tk"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1103
msgid "Turkmen"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1105
msgid "tkl"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1105
#: ../../docs/tutorials/i18n/locales.rst:2109
msgid "Tokelau"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1107
msgid "tkr"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1107
msgid "Tsakhur"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1109
msgid "tl"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1109
#: ../../docs/tutorials/i18n/locales.rst:1604
msgid "Tagalog"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1111
msgid "tlh"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1111
#: ../../docs/tutorials/i18n/locales.rst:1530
msgid "Klingon"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1113
msgid "tli"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1113
msgid "Tlingit"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1115
msgid "tly"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1115
msgid "Talysh"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1117
msgid "tmh"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1117
msgid "Tamashek"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1119
msgid "tn"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1119
msgid "Tswana"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1121
msgid "to"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1121
msgid "Tongan"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1123
msgid "tog"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1123
msgid "Nyasa Tonga"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1125
msgid "tpi"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1125
msgid "Tok Pisin"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1127
msgid "tr"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1127
msgid "Turkish"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1129
msgid "tru"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1129
msgid "Turoyo"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1131
msgid "trv"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1131
msgid "Taroko"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1133
msgid "ts"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1133
msgid "Tsonga"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1135
msgid "tsd"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1135
msgid "Tsakonian"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1137
msgid "tsi"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1137
msgid "Tsimshian"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1139
msgid "tt"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1139
msgid "Tatar"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1141
msgid "ttt"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1141
msgid "Muslim Tat"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1143
msgid "tum"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1143
msgid "Tumbuka"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1145
msgid "tvl"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1145
#: ../../docs/tutorials/i18n/locales.rst:2123
msgid "Tuvalu"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1147
msgid "tw"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1147
msgid "Twi"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1149
msgid "twq"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1149
msgid "Tasawaq"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1151
msgid "ty"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1151
msgid "Tahitian"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1153
msgid "tyv"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1153
msgid "Tuvinian"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1155
msgid "tzm"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1155
msgid "Central Atlas Tamazight"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1157
msgid "udm"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1157
msgid "Udmurt"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1159
msgid "ug"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1159
msgid "Uyghur"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1161
msgid "uga"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1161
#: ../../docs/tutorials/i18n/locales.rst:1618
msgid "Ugaritic"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1163
msgid "uk"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1163
msgid "Ukrainian"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1165
msgid "umb"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1165
msgid "Umbundu"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1167
msgid "unm"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1167
msgid "Unami"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1169
msgid "ur"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1169
msgid "Urdu"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1171
msgid "uz"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1171
msgid "Uzbek"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1173
msgid "vai"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1173
#: ../../docs/tutorials/i18n/locales.rst:1620
msgid "Vai"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1175
msgid "ve"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1175
msgid "Venda"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1177
msgid "vec"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1177
msgid "Venetian"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1179
msgid "vep"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1179
msgid "Veps"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1181
msgid "vi"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1181
msgid "Vietnamese"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1183
msgid "vls"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1183
msgid "West Flemish"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1185
msgid "vmf"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1185
msgid "Main-Franconian"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1187
msgid "vo"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1187
msgid "Volapük"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1189
msgid "vot"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1189
msgid "Votic"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1191
msgid "vro"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1191
msgid "Võro"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1193
msgid "vun"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1193
msgid "Vunjo"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1195
msgid "wa"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1195
msgid "Walloon"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1197
msgid "wae"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1197
msgid "Walser"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1199
msgid "wal"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1199
msgid "Wolaytta"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1201
msgid "war"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1201
msgid "Waray"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1203
msgid "was"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1203
msgid "Washo"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1205
msgid "wbp"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1205
msgid "Warlpiri"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1207
msgid "wo"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1207
msgid "Wolof"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1209
msgid "wuu"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1209
msgid "Wu Chinese"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1211
msgid "xal"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1211
msgid "Kalmyk"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1213
msgid "xh"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1213
msgid "Xhosa"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1215
msgid "xmf"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1215
msgid "Mingrelian"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1217
msgid "xog"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1217
msgid "Soga"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1219
msgid "yao"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1219
msgid "Yao"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1221
msgid "yap"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1221
msgid "Yapese"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1223
msgid "yav"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1223
msgid "Yangben"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1225
msgid "ybb"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1225
msgid "Yemba"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1227
msgid "yi"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1227
msgid "Yiddish"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1229
msgid "yo"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1229
msgid "Yoruba"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1231
msgid "yrl"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1231
msgid "Nheengatu"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1233
msgid "yue"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1233
msgid "Yue Chinese"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1235
msgid "yuw"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1235
#: ../../docs/tutorials/i18n/locales.rst:2019
msgid "Papua New Guinea"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1237
msgid "za"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1237
msgid "Zhuang"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1239
msgid "zap"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1239
msgid "Zapotec"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1241
msgid "zbl"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1241
#: ../../docs/tutorials/i18n/locales.rst:1292
msgid "Blissymbols"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1243
msgid "zea"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1243
msgid "Zeelandic"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1245
msgid "zen"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1245
msgid "Zenaga"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1247
msgid "zgh"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1247
msgid "Standard Moroccan Tamazight"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1249
msgid "zh"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1249
msgid "Chinese"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1251
msgid "zu"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1251
msgid "Zulu"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1253
msgid "zun"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1253
msgid "Zuni"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1255
msgid "zza"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1255
msgid "Zaza"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1259
msgid "List of supported script codes"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1262
msgid "Script code"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1264
msgid "Adlm"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1264
msgid "Adlam"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1266
msgid "Afak"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1266
msgid "Afaka"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1268
msgid "Aghb"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1268
msgid "Caucasian Albanian"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1270
msgid "Ahom"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1272
msgid "Arab"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1274
msgid "Armi"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1274
msgid "Imperial Aramaic"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1276
msgid "Armn"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1278
msgid "Avst"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1280
msgid "Bali"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1282
msgid "Bamu"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1282
msgid "Bamum"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1284
msgid "Bass"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1284
msgid "Bassa Vah"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1286
msgid "Batk"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1286
msgid "Batak"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1288
msgid "Beng"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1290
msgid "Bhks"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1290
msgid "Bhaiksuki"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1292
msgid "Blis"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1294
msgid "Bopo"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1294
msgid "Bopomofo"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1296
msgid "Brah"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1296
msgid "Brahmi"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1298
msgid "Brai"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1298
msgid "Braille"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1300
msgid "Bugi"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1302
msgid "Buhd"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1302
msgid "Buhid"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1304
msgid "Cakm"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1306
msgid "Cans"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1306
msgid "Unified Canadian Aboriginal"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1308
msgid "Cari"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1308
msgid "Carian"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1310
msgid "Cham"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1312
msgid "Cher"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1314
msgid "Chrs"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1314
msgid "Chorasmian"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1316
msgid "Cirt"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1316
msgid "Cirth"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1318
msgid "Copt"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1320
msgid "Cpmn"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1320
msgid "Cypro-Minoan"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1322
msgid "Cprt"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1322
msgid "Cypriot"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1324
msgid "Cyrl"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1324
msgid "Cyrillic"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1326
msgid "Deva"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1326
msgid "Devanagari"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1328
msgid "Diak"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1328
msgid "Dives Akuru"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1330
msgid "Dogr"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1330
msgid "Dogra"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1332
msgid "Dsrt"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1332
msgid "Deseret"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1334
msgid "Dupl"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1334
msgid "Duployan"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1336
msgid "Egyd"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1336
msgid "Egyptian demotic"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1338
msgid "Egyh"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1338
msgid "Egyptian hieratic"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1340
msgid "Egyp"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1340
msgid "Egyptian hieroglyphs"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1342
msgid "Elba"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1342
msgid "Elbasan"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1344
msgid "Elym"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1344
msgid "Elymaic"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1346
msgid "Ethi"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1346
msgid "Ethiopic"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1348
msgid "Geok"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1348
msgid "Khutsuri"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1350
msgid "Geor"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1352
msgid "Glag"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1352
msgid "Glagolitic"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1354
msgid "Gong"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1354
msgid "Gunjala Gondi"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1356
msgid "Gonm"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1356
msgid "Masaram Gondi"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1358
msgid "Goth"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1360
msgid "Gran"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1360
msgid "Grantha"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1362
msgid "Grek"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1364
msgid "Gujr"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1366
msgid "Guru"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1366
msgid "Gurmukhi"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1368
msgid "Hang"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1368
msgid "Hangul"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1370
msgid "Hani"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1370
msgid "Han"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1372
msgid "Hano"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1372
msgid "Hanunoo"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1374
msgid "Hans"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1374
msgid "Simplified"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1376
msgid "Hant"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1376
msgid "Traditional"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1378
msgid "Hatr"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1378
msgid "Hatran"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1380
msgid "Hebr"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1382
msgid "Hira"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1382
msgid "Hiragana"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1384
msgid "Hluw"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1384
msgid "Anatolian Hieroglyphs"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1386
msgid "Hmng"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1386
msgid "Pahawh Hmong"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1388
msgid "Hmnp"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1388
msgid "Nyiakeng Puachue Hmong"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1390
msgid "Hung"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1390
msgid "Old Hungarian"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1392
msgid "Inds"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1392
msgid "Indus"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1394
msgid "Ital"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1394
msgid "Old Italic"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1396
#: ../../docs/contributing/development/code_style_guidelines.rst:247
msgid "Java"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1398
msgid "Jurc"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1398
msgid "Jurchen"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1400
msgid "Kali"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1400
msgid "Kayah Li"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1402
msgid "Kana"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1402
msgid "Katakana"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1404
msgid "Khar"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1404
msgid "Kharoshthi"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1406
msgid "Khmr"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1406
msgid "Khmer"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1408
msgid "Khoj"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1408
msgid "Khojki"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1410
msgid "Kitl"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1410
#, fuzzy
msgid "Khitan large script"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/i18n/locales.rst:1412
msgid "Kits"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1412
#, fuzzy
msgid "Khitan small script"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/i18n/locales.rst:1414
msgid "Knda"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1416
msgid "Kpel"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1418
msgid "Kthi"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1418
msgid "Kaithi"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1420
msgid "Lana"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1420
msgid "Tai Tham"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1422
msgid "Laoo"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1424
msgid "Latn"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1426
msgid "Leke"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1428
msgid "Lepc"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1428
msgid "Lepcha"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1430
msgid "Limb"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1430
msgid "Limbu"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1432
msgid "Lina"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1432
msgid "Linear A"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1434
msgid "Linb"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1434
msgid "Linear B"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1436
msgid "Lisu"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1438
msgid "Loma"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1440
msgid "Lyci"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1440
msgid "Lycian"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1442
msgid "Lydi"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1442
msgid "Lydian"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1444
msgid "Mahj"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1444
msgid "Mahajani"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1446
msgid "Maka"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1448
msgid "Mand"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1448
msgid "Mandaic"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1450
msgid "Mani"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1450
msgid "Manichaean"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1452
msgid "Marc"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1452
msgid "Marchen"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1454
msgid "Maya"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1454
msgid "Mayan Hieroglyphs"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1456
msgid "Medf"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1456
msgid "Medefaidrin"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1458
msgid "Mend"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1458
msgid "Mende Kikakui"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1460
msgid "Merc"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1460
msgid "Meroitic Cursive"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1462
msgid "Mero"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1462
msgid "Meroitic Hieroglyphs"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1464
msgid "Mlym"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1466
msgid "Modi"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1468
msgid "Mong"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1470
msgid "Moon"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1472
msgid "Mroo"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1472
msgid "Mro"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1474
msgid "Mtei"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1474
msgid "Meitei Mayek"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1476
msgid "Mult"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1476
msgid "Multani"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1478
msgid "Mymr"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1478
msgid "Myanmar (Burmese)"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1480
msgid "Nand"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1480
msgid "Nandinagari"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1482
msgid "Narb"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1482
msgid "Old North Arabian"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1484
msgid "Nbat"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1484
msgid "Nabataean"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1486
msgid "Newa"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1488
msgid "Nkdb"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1488
msgid "Naxi Dongba"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1490
msgid "Nkgb"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1490
msgid "Nakhi Geba"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1492
msgid "Nkoo"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1494
msgid "Nshu"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1494
msgid "Nüshu"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1496
msgid "Ogam"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1496
msgid "Ogham"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1498
msgid "Olck"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1498
msgid "Ol Chiki"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1500
msgid "Orkh"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1500
msgid "Old Turkic"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1502
msgid "Orya"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1502
msgid "Oriya"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1504
msgid "Osge"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1506
msgid "Osma"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1506
msgid "Osmanya"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1508
msgid "Ougr"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1508
msgid "Old Uyghur"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1510
msgid "Palm"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1510
msgid "Palmyrene"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1512
msgid "Pauc"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1512
msgid "Pau Cin Hau"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1514
msgid "Pcun"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1514
msgid "Proto-Cuneiform"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1516
msgid "Pelm"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1516
msgid "Proto-Elamite"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1518
msgid "Perm"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1518
msgid "Old Permic"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1520
msgid "Phag"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1520
msgid "Phags-pa"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1522
msgid "Phli"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1522
msgid "Inscriptional Pahlavi"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1524
msgid "Phlp"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1524
msgid "Psalter Pahlavi"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1526
msgid "Phlv"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1526
msgid "Book Pahlavi"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1528
msgid "Phnx"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1530
msgid "Piqd"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1532
msgid "Plrd"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1532
msgid "Miao"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1534
msgid "Prti"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1534
msgid "Inscriptional Parthian"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1536
msgid "Psin"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1536
msgid "Proto-Sinaitic"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1538
msgid "Ranj"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1538
msgid "Ranjana"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1540
msgid "Rjng"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1540
msgid "Rejang"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1542
msgid "Rohg"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1542
msgid "Hanifi Rohingya"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1544
msgid "Roro"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1544
msgid "Rongorongo"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1546
msgid "Runr"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1546
msgid "Runic"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1548
msgid "Samr"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1548
msgid "Samaritan"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1550
msgid "Sara"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1550
msgid "Sarati"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1552
msgid "Sarb"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1552
msgid "Old South Arabian"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1554
msgid "Saur"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1556
msgid "Sgnw"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1556
#, fuzzy
msgid "SignWriting"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/i18n/locales.rst:1558
msgid "Shaw"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1558
msgid "Shavian"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1560
msgid "Shrd"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1560
msgid "Sharada"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1562
msgid "Shui"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1562
msgid "Shuishu"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1564
msgid "Sidd"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1564
msgid "Siddham"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1566
msgid "Sind"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1566
msgid "Khudawadi"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1568
msgid "Sinh"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1570
msgid "Sogd"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1570
msgid "Sogdian"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1572
msgid "Sogo"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1572
msgid "Old Sogdian"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1574
msgid "Sora"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1574
msgid "Sora Sompeng"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1576
msgid "Soyo"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1576
msgid "Soyombo"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1578
msgid "Sund"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1580
msgid "Sylo"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1580
msgid "Syloti Nagri"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1582
msgid "Syrc"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1584
msgid "Tagb"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1584
msgid "Tagbanwa"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1586
msgid "Takr"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1586
msgid "Takri"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1588
msgid "Tale"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1588
msgid "Tai Le"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1590
msgid "Talu"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1590
msgid "New Tai Lue"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1592
msgid "Taml"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1594
msgid "Tang"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1594
msgid "Tangut"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1596
msgid "Tavt"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1596
msgid "Tai Viet"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1598
msgid "Telu"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1600
msgid "Teng"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1600
msgid "Tengwar"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1602
msgid "Tfng"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1602
msgid "Tifinagh"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1604
msgid "Tglg"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1606
msgid "Thaa"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1606
msgid "Thaana"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1610
msgid "Tibt"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1612
msgid "Tirh"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1612
msgid "Tirhuta"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1614
msgid "Tnsa"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1614
msgid "Tangsa"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1616
msgid "Toto"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1618
msgid "Ugar"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1620
msgid "Vaii"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1622
msgid "Visp"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1622
msgid "Visible Speech"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1624
msgid "Vith"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1624
msgid "Vithkuqi"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1626
msgid "Wara"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1626
msgid "Warang Citi"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1628
msgid "Wcho"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1628
msgid "Wancho"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1630
msgid "Wole"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1630
msgid "Woleai"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1632
msgid "Xpeo"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1634
msgid "Xsux"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1634
msgid "Cuneiform"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1636
msgid "Yezi"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1636
msgid "Yezidi"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1638
msgid "Yiii"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1638
msgid "Yi"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1640
msgid "Zanb"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1640
msgid "Zanabazar Square"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1644
msgid "List of supported country codes"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1647
msgid "Country code"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1649
msgid "AC"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1649
msgid "Ascension Island"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1651
msgid "AD"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1651
msgid "Andorra"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1653
msgid "AE"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1653
msgid "United Arab Emirates"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1655
msgid "AF"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1655
msgid "Afghanistan"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1657
msgid "AG"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1657
msgid "Antigua and Barbuda"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1659
msgid "AI"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1659
msgid "Anguilla"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1661
msgid "AL"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1661
msgid "Albania"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1663
msgid "AM"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1663
msgid "Armenia"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1665
msgid "AN"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1665
msgid "Netherlands Antilles"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1667
msgid "AO"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1667
msgid "Angola"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1669
msgid "AQ"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1669
msgid "Antarctica"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1671
msgid "AR"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1671
msgid "Argentina"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1673
msgid "AS"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1673
msgid "American Samoa"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1675
msgid "AT"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1675
msgid "Austria"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1677
msgid "AU"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1677
msgid "Australia"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1679
msgid "AW"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1679
msgid "Aruba"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1681
msgid "AX"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1681
msgid "Åland Islands"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1683
msgid "AZ"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1683
msgid "Azerbaijan"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1685
msgid "BA"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1685
msgid "Bosnia and Herzegovina"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1687
msgid "BB"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1687
msgid "Barbados"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1689
msgid "BD"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1689
msgid "Bangladesh"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1691
msgid "BE"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1691
msgid "Belgium"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1693
msgid "BF"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1693
msgid "Burkina Faso"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1695
msgid "BG"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1695
msgid "Bulgaria"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1697
msgid "BH"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1697
msgid "Bahrain"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1699
msgid "BI"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1699
msgid "Burundi"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1701
msgid "BJ"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1701
msgid "Benin"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1703
msgid "BL"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1703
msgid "St. Barthélemy"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1705
msgid "BM"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1705
msgid "Bermuda"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1707
msgid "BN"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1707
msgid "Brunei"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1709
msgid "BO"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1709
msgid "Bolivia"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1711
msgid "BQ"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1711
msgid "Caribbean Netherlands"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1713
msgid "BR"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1713
msgid "Brazil"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1715
msgid "BS"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1715
msgid "Bahamas"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1717
msgid "BT"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1717
msgid "Bhutan"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1719
msgid "BV"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1719
msgid "Bouvet Island"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1721
msgid "BW"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1721
msgid "Botswana"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1723
msgid "BY"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1723
msgid "Belarus"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1725
msgid "BZ"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1725
msgid "Belize"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1727
msgid "CA"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1727
msgid "Canada"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1729
msgid "CC"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1729
msgid "Cocos (Keeling) Islands"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1731
msgid "CD"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1731
msgid "Congo - Kinshasa"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1733
msgid "CF"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1733
msgid "Central African Republic"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1735
msgid "CG"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1735
msgid "Congo - Brazzaville"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1737
msgid "CH"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1737
msgid "Switzerland"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1739
msgid "CI"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1739
msgid "Côte d'Ivoire"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1741
msgid "CK"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1741
msgid "Cook Islands"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1743
msgid "CL"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1743
msgid "Chile"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1745
msgid "CM"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1745
msgid "Cameroon"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1747
msgid "CN"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1747
msgid "China"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1749
msgid "CO"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1749
msgid "Colombia"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1751
msgid "CP"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1751
msgid "Clipperton Island"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1753
msgid "CR"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1753
msgid "Costa Rica"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1755
msgid "CQ"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1755
msgid "Island of Sark"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1757
msgid "CU"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1757
msgid "Cuba"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1759
msgid "CV"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1759
msgid "Cabo Verde"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1761
msgid "CW"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1761
msgid "Curaçao"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1763
msgid "CX"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1763
msgid "Christmas Island"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1765
msgid "CY"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1765
msgid "Cyprus"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1767
msgid "CZ"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1767
msgid "Czechia"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1769
msgid "DE"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1769
msgid "Germany"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1771
msgid "DG"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1771
msgid "Diego Garcia"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1773
msgid "DJ"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1773
#, fuzzy
msgid "Djibouti"
msgstr "O Godot-u"

#: ../../docs/tutorials/i18n/locales.rst:1775
msgid "DK"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1775
msgid "Denmark"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1777
msgid "DM"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1777
msgid "Dominica"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1779
msgid "DO"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1779
msgid "Dominican Republic"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1781
msgid "DZ"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1781
msgid "Algeria"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1783
msgid "EA"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1783
msgid "Ceuta and Melilla"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1785
msgid "EC"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1785
msgid "Ecuador"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1787
msgid "EE"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1787
msgid "Estonia"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1789
msgid "EG"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1789
msgid "Egypt"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1791
msgid "EH"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1791
msgid "Western Sahara"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1793
msgid "ER"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1793
msgid "Eritrea"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1795
msgid "ES"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1795
msgid "Spain"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1797
msgid "ET"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1797
msgid "Ethiopia"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1799
msgid "EU"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1799
msgid "European Union"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1801
msgid "EZ"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1801
msgid "Eurozone"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1803
msgid "FI"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1803
msgid "Finland"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1805
msgid "FJ"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1805
msgid "Fiji"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1807
msgid "FK"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1807
msgid "Falkland Islands"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1809
msgid "FM"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1809
msgid "Micronesia"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1811
msgid "FO"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1811
msgid "Faroe Islands"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1813
msgid "FR"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1813
msgid "France"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1815
msgid "FX"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1815
msgid "France, Metropolitan"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1817
msgid "GA"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1817
msgid "Gabon"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1819
msgid "GB, UK"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1819
msgid "United Kingdom"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1821
msgid "GD"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1821
msgid "Grenada"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1823
msgid "GE"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1823
msgid "Georgia"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1825
msgid "GF"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1825
msgid "French Guiana"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1827
msgid "GG"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1827
msgid "Guernsey"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1829
msgid "GH"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1829
msgid "Ghana"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1831
msgid "GI"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1831
msgid "Gibraltar"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1833
msgid "GL"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1833
msgid "Greenland"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1835
msgid "GM"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1835
msgid "Gambia"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1837
msgid "GN"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1837
msgid "Guinea"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1839
msgid "GP"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1839
msgid "Guadeloupe"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1841
msgid "GQ"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1841
msgid "Equatorial Guinea"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1843
msgid "GR"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1843
msgid "Greece"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1845
msgid "GS"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1845
msgid "South Georgia and South Sandwich Islands"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1847
msgid "GT"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1847
msgid "Guatemala"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1849
msgid "GU"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1849
msgid "Guam"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1851
msgid "GW"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1851
msgid "Guinea-Bissau"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1853
msgid "GY"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1853
msgid "Guyana"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1855
msgid "HK"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1855
msgid "Hong Kong"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1857
msgid "HM"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1857
msgid "Heard Island and McDonald Islands"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1859
msgid "HN"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1859
msgid "Honduras"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1861
msgid "HR"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1861
msgid "Croatia"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1863
msgid "HT"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1863
msgid "Haiti"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1865
msgid "HU"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1865
msgid "Hungary"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1867
msgid "IC"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1867
msgid "Canary Islands"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1869
msgid "ID"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1869
msgid "Indonesia"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1871
msgid "IE"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1871
msgid "Ireland"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1873
msgid "IL"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1873
msgid "Israel"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1875
msgid "IM"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1875
msgid "Isle of Man"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1877
msgid "IN"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1877
msgid "India"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1879
msgid "IO"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1879
msgid "British Indian Ocean Territory"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1881
msgid "IQ"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1881
msgid "Iraq"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1883
msgid "IR"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1883
msgid "Iran"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1885
msgid "IS"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1885
msgid "Iceland"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1887
msgid "IT"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1887
msgid "Italy"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1889
msgid "JE"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1889
msgid "Jersey"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1891
msgid "JM"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1891
msgid "Jamaica"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1893
msgid "JO"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1893
msgid "Jordan"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1895
msgid "JP"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1895
msgid "Japan"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1897
msgid "KE"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1897
msgid "Kenya"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1899
msgid "KG"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1899
msgid "Kyrgyzstan"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1901
msgid "KH"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1901
msgid "Cambodia"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1903
msgid "KI"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1903
msgid "Kiribati"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1905
msgid "KM"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1905
msgid "Comoros"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1907
msgid "KN"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1907
msgid "St. Kitts and Nevis"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1909
msgid "KP"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1909
msgid "North Korea"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1911
msgid "KR"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1911
msgid "South Korea"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1913
msgid "KW"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1913
msgid "Kuwait"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1915
msgid "KY"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1915
msgid "Cayman Islands"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1917
msgid "KZ"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1917
msgid "Kazakhstan"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1919
msgid "LA"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1919
msgid "Laos"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1921
msgid "LB"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1921
msgid "Lebanon"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1923
msgid "LC"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1923
msgid "St. Lucia"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1925
msgid "LI"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1925
msgid "Liechtenstein"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1927
msgid "LK"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1927
msgid "Sri Lanka"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1929
msgid "LR"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1929
msgid "Liberia"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1931
msgid "LS"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1931
msgid "Lesotho"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1933
msgid "LT"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1933
msgid "Lithuania"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1935
msgid "LU"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1935
msgid "Luxembourg"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1937
msgid "LV"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1937
msgid "Latvia"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1939
msgid "LY"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1939
msgid "Libya"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1941
msgid "MA"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1941
msgid "Morocco"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1943
msgid "MC"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1943
msgid "Monaco"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1945
msgid "MD"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1945
msgid "Moldova"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1947
msgid "ME"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1947
msgid "Montenegro"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1949
msgid "MF"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1949
msgid "St. Martin"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1951
msgid "MG"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1951
msgid "Madagascar"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1953
msgid "MH"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1953
msgid "Marshall Islands"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1955
msgid "MK"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1955
msgid "North Macedonia"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1957
msgid "ML"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1957
msgid "Mali"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1959
msgid "MM, BU"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1959
msgid "Myanmar"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1961
msgid "MN"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1961
msgid "Mongolia"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1963
msgid "MO"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1963
msgid "Macao"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1965
msgid "MP"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1965
msgid "Northern Mariana Islands"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1967
msgid "MQ"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1967
msgid "Martinique"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1969
msgid "MR"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1969
msgid "Mauritania"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1971
msgid "MS"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1971
msgid "Montserrat"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1973
msgid "MT"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1973
msgid "Malta"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1975
msgid "MU"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1975
msgid "Mauritius"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1977
msgid "MV"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1977
msgid "Maldives"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1979
msgid "MW"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1979
msgid "Malawi"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1981
msgid "MX"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1981
msgid "Mexico"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1983
msgid "MY"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1983
msgid "Malaysia"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1985
msgid "MZ"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1985
msgid "Mozambique"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1987
msgid "NA"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1987
msgid "Namibia"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1989
msgid "NC"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1989
msgid "New Caledonia"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1991
msgid "NE"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1991
msgid "Niger"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1993
msgid "NF"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1993
msgid "Norfolk Island"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1995
msgid "NG"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1995
msgid "Nigeria"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1997
msgid "NI"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1997
msgid "Nicaragua"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1999
msgid "NL"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:1999
msgid "Netherlands"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2001
msgid "NO"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2001
msgid "Norway"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2003
msgid "NP"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2003
msgid "Nepal"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2005
msgid "NR"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2007
msgid "NU"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2007
msgid "Niue"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2009
msgid "NZ"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2009
msgid "New Zealand"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2011
msgid "OM"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2011
msgid "Oman"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2013
msgid "PA"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2013
msgid "Panama"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2015
msgid "PE"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2015
msgid "Peru"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2017
msgid "PF"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2017
msgid "French Polynesia"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2019
msgid "PG"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2021
msgid "PH"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2021
msgid "Philippines"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2023
msgid "PK"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2023
msgid "Pakistan"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2025
msgid "PL"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2025
msgid "Poland"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2027
msgid "PM"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2027
msgid "St. Pierre and Miquelon"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2029
msgid "PN"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2029
msgid "Pitcairn Islands"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2031
msgid "PR"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2031
msgid "Puerto Rico"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2033
#, fuzzy
msgid "PS"
msgstr "FPS"

#: ../../docs/tutorials/i18n/locales.rst:2033
msgid "Palestine"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2035
msgid "PT"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2035
msgid "Portugal"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2037
msgid "PW"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2037
msgid "Palau"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2039
msgid "PY"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2039
msgid "Paraguay"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2041
msgid "QA"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2041
msgid "Qatar"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2043
msgid "RE"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2043
msgid "Réunion"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2045
msgid "RO"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2045
msgid "Romania"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2047
msgid "RS"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2047
msgid "Serbia"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2049
msgid "RU"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2049
msgid "Russia"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2051
msgid "RW"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2051
msgid "Rwanda"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2053
msgid "SA"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2053
msgid "Saudi Arabia"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2055
msgid "SB"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2055
msgid "Solomon Islands"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2057
msgid "SC"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2057
msgid "Seychelles"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2059
msgid "SD"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2059
msgid "Sudan"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2061
msgid "SE"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2061
msgid "Sweden"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2063
msgid "SG"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2063
msgid "Singapore"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2065
msgid "SH"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2065
msgid "St. Helena, Ascension and Tristan da Cunha"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2067
msgid "SI"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2067
msgid "Slovenia"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2069
msgid "SJ"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2069
msgid "Svalbard and Jan Mayen"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2071
msgid "SK"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2071
msgid "Slovakia"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2073
msgid "SL"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2073
msgid "Sierra Leone"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2075
msgid "SM"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2075
msgid "San Marino"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2077
msgid "SN"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2077
msgid "Senegal"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2079
msgid "SO"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2079
msgid "Somalia"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2081
msgid "SR"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2081
msgid "Suriname"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2083
msgid "SS"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2083
msgid "South Sudan"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2085
msgid "ST"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2085
msgid "Sao Tome and Principe"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2087
msgid "SV"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2087
msgid "El Salvador"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2089
msgid "SX"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2089
msgid "Sint Maarten"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2091
msgid "SY"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2091
msgid "Syria"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2093
msgid "SZ"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2093
msgid "Eswatini"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2095
msgid "TA"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2095
msgid "Tristan da Cunha"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2097
msgid "TC"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2097
msgid "Turks and Caicos Islands"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2099
msgid "TD"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2099
msgid "Chad"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2101
msgid "TF"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2101
msgid "French Southern Territories"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2103
msgid "TG"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2103
msgid "Togo"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2105
msgid "TH"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2105
msgid "Thailand"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2107
msgid "TJ"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2107
msgid "Tajikistan"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2109
msgid "TK"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2111
msgid "TL, TP"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2111
msgid "Timor-Leste"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2113
msgid "TM"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2113
msgid "Turkmenistan"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2115
msgid "TN"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2115
msgid "Tunisia"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2117
msgid "TO"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2117
msgid "Tonga"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2119
msgid "TR"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2119
msgid "Turkey"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2121
msgid "TT"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2121
msgid "Trinidad and Tobago"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2123
msgid "TV"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2125
msgid "TW"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2125
msgid "Taiwan"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2127
msgid "TZ"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2127
msgid "Tanzania"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2129
msgid "UA"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2129
msgid "Ukraine"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2131
msgid "UG"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2131
msgid "Uganda"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2133
msgid "UM"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2133
msgid "U.S. Outlying Islands"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2135
msgid "US"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2135
msgid "United States of America"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2137
msgid "UY"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2137
msgid "Uruguay"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2139
msgid "UZ"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2139
msgid "Uzbekistan"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2141
msgid "VA"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2141
msgid "Holy See"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2143
msgid "VC"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2143
msgid "St. Vincent and the Grenadines"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2145
msgid "VE"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2145
msgid "Venezuela"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2147
msgid "VG"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2147
msgid "British Virgin Islands"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2149
msgid "VI"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2149
msgid "U.S. Virgin Islands"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2151
msgid "VN"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2151
msgid "Viet Nam"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2153
msgid "VU"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2153
msgid "Vanuatu"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2155
msgid "WF"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2155
msgid "Wallis and Futuna"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2157
msgid "WS"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2157
msgid "Samoa"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2159
msgid "XK, KV"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2159
msgid "Kosovo"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2161
msgid "YE"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2161
msgid "Yemen"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2163
msgid "YT"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2163
msgid "Mayotte"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2165
msgid "ZA"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2165
msgid "South Africa"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2167
msgid "ZM"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2167
msgid "Zambia"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2169
msgid "ZW"
msgstr ""

#: ../../docs/tutorials/i18n/locales.rst:2169
msgid "Zimbabwe"
msgstr ""

#: ../../docs/tutorials/i18n/pseudolocalization.rst:4
msgid "Pseudolocalization"
msgstr ""

#: ../../docs/tutorials/i18n/pseudolocalization.rst:9
msgid ""
"When creating a game, the process of localization usually starts when "
"development has finished. This means that translations aren't available "
"during development for testing whether the project is internationalized "
"properly."
msgstr ""

#: ../../docs/tutorials/i18n/pseudolocalization.rst:13
msgid ""
"Godot offers pseudolocalization as a way to test how robust the project is "
"when it comes to locale changes. Pseudolocalization simulates changes that "
"might take place during localization. This way, any issues regarding "
"internationalization can be recognized early on during development."
msgstr ""

#: ../../docs/tutorials/i18n/pseudolocalization.rst:20
#, fuzzy
msgid ""
"You can see how pseudolocalization works in action using the "
"`Pseudolocalizaton demo project <https://github.com/godotengine/godot-demo-"
"projects/tree/master/gui/pseudolocalization>`__."
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati različite Godo demo projekte "
"`Godot demo projects <https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/tutorials/i18n/pseudolocalization.rst:24
msgid "Enabling and configuring pseudolocalization"
msgstr ""

#: ../../docs/tutorials/i18n/pseudolocalization.rst:26
msgid ""
"Enabling pseudolocalization and the configurations related to it is as "
"simple as toggling a checkbox in the project settings. These settings can be "
"found in **Project → Project Settings → General → Internationalization → "
"Pseudolocalization** after enabling the **Advanced** toggle in the project "
"settings dialog:"
msgstr ""

#: ../../docs/tutorials/i18n/pseudolocalization.rst:33
msgid ""
"Pseudolocalization can also be :ref:`toggled at runtime from a script "
"<doc_pseudolocalization_runtime>`."
msgstr ""

#: ../../docs/tutorials/i18n/pseudolocalization.rst:36
msgid "Pseudolocalization configurations"
msgstr ""

#: ../../docs/tutorials/i18n/pseudolocalization.rst:38
msgid ""
"Pseudolocalization in Godot can be set up according to the specific use case "
"of the project. Here are the pseudolocalization properties that can be "
"configured through project settings:"
msgstr ""

#: ../../docs/tutorials/i18n/pseudolocalization.rst:42
msgid ""
"``replace_with_accents``: Replaces all characters in the string with their "
"accented variants. *\"The quick brown fox jumped over the lazy dog\"* will "
"be converted to *\"Ŧh̀é q́üíćḱ ḅŕôŵή f́ôx́ ǰüm̀ṕéd́ ôṽéŕ ŧh̀é łáźý d́ôǵ\"* when this "
"setting is enabled. This can be used to spot untranslated strings that won't "
"have accents, but is also useful to check for missing glyphs in the font(s) "
"used by the project."
msgstr ""

#: ../../docs/tutorials/i18n/pseudolocalization.rst:47
msgid ""
"``double_vowels``: Doubles all the vowels in the string. It is a good "
"approximation to simulate expansion of text during localization. This can be "
"used to check for text that would overflow its container (such as buttons)."
msgstr ""

#: ../../docs/tutorials/i18n/pseudolocalization.rst:51
msgid ""
"``fake_bidi``: Fake bidirectional text (simulates right-to-left text). This "
"is useful to simulate right-to-left writing systems to check for potential "
"layout issues that would occur in languages using right-to-left scripts."
msgstr ""

#: ../../docs/tutorials/i18n/pseudolocalization.rst:53
msgid ""
"``override``: Replaces all the characters in the string with an asterisk "
"(``*``). This is useful for quickly finding text that isn't being localized."
msgstr ""

#: ../../docs/tutorials/i18n/pseudolocalization.rst:55
msgid ""
"``expansion_ratio``: Can be used in cases where doubling the vowels isn't a "
"sufficient approximation. This setting pads the string with underscores "
"(``_``) and expands it by the given ratio. An expansion ratio of ``0.3`` is "
"sufficient for most practical cases; it will increase the length of the "
"string by 30%."
msgstr ""

#: ../../docs/tutorials/i18n/pseudolocalization.rst:59
msgid ""
"``prefix`` and ``suffix``: These properties can be used to specify a prefix "
"and suffix to wrap the text in."
msgstr ""

#: ../../docs/tutorials/i18n/pseudolocalization.rst:61
msgid ""
"``skip_placeholders``: Skips placeholders for string formatting like ``%s`` "
"and ``%f``. This is useful to identify places where more arguments are "
"required for the formatted string to display correctly."
msgstr ""

#: ../../docs/tutorials/i18n/pseudolocalization.rst:65
msgid ""
"All of these properties can be toggled as needed according to the project's "
"use case."
msgstr ""

#: ../../docs/tutorials/i18n/pseudolocalization.rst:70
msgid "Configuring pseudolocalization at runtime"
msgstr ""

#: ../../docs/tutorials/i18n/pseudolocalization.rst:72
msgid ""
"Pseudolocalization can be toggled at runtime using the :ref:"
"`pseudolocalization_enabled<class_TranslationServer_property_pseudolocalization_enabled>` "
"property in TranslationServer. However, if runtime configuration of "
"pseudolocalization properties is required, they can be directly configured "
"using :ref:`ProjectSettings.set_setting(property, value) "
"<class_ProjectSettings_method_set_setting>` and then calling :ref:"
"`TranslationServer.reload_pseudolocalization() "
"<class_TranslationServer_method_reload_pseudolocalization>` which reparses "
"the pseudolocalization properties and reloads the pseudolocalization. The "
"following code snippet shall turn on ``replace_with_accents`` and "
"``double_vowels`` properties and then call ``reload_pseudolocalization()`` "
"for the changes to get reflected::"
msgstr ""

#: ../../docs/tutorials/inputs/index.rst:2
msgid "Input handling"
msgstr ""

#: ../../docs/tutorials/inputs/inputevent.rst:4
msgid "Using InputEvent"
msgstr ""

#: ../../docs/tutorials/inputs/inputevent.rst:9
msgid ""
"Managing input is usually complex, no matter the OS or platform. To ease "
"this a little, a special built-in type is provided, :ref:`InputEvent "
"<class_InputEvent>`. This datatype can be configured to contain several "
"types of input events. Input events travel through the engine and can be "
"received in multiple locations, depending on the purpose."
msgstr ""

#: ../../docs/tutorials/inputs/inputevent.rst:15
msgid "Here is a quick example, closing your game if the escape key is hit:"
msgstr ""

#: ../../docs/tutorials/inputs/inputevent.rst:34
msgid ""
"However, it is cleaner and more flexible to use the provided :ref:`InputMap "
"<class_InputMap>` feature, which allows you to define input actions and "
"assign them different keys. This way, you can define multiple keys for the "
"same action (e.g. the keyboard escape key and the start button on a "
"gamepad). You can then more easily change this mapping in the project "
"settings without updating your code, and even build a key mapping feature on "
"top of it to allow your game to change the key mapping at runtime!"
msgstr ""

#: ../../docs/tutorials/inputs/inputevent.rst:40
msgid ""
"You can set up your InputMap under **Project > Project Settings > Input "
"Map** and then use those actions like this:"
msgstr ""

#: ../../docs/tutorials/inputs/inputevent.rst:60
msgid "How does it work?"
msgstr ""

#: ../../docs/tutorials/inputs/inputevent.rst:62
msgid ""
"Every input event is originated from the user/player (though it's possible "
"to generate an InputEvent and feed them back to the engine, which is useful "
"for gestures). The DisplayServer for each platform will read events from the "
"operating system, then feed them to the root :ref:`Window <class_Window>`."
msgstr ""

#: ../../docs/tutorials/inputs/inputevent.rst:67
msgid ""
"The window's :ref:`Viewport <class_Viewport>` does quite a lot of stuff with "
"the received input, in order:"
msgstr ""

#: ../../docs/tutorials/inputs/inputevent.rst:72
msgid ""
"If the Viewport is embedding Windows, the Viewport tries to interpret the "
"event in its capability as a Window-Manager (e.g. for resizing or moving "
"Windows)."
msgstr ""

#: ../../docs/tutorials/inputs/inputevent.rst:74
msgid ""
"Next if an embedded Window is focused, the event is sent to that Window and "
"processed in the Windows Viewport and afterwards treated as handled. If no "
"embedded Window is focused, the event is sent to the nodes of the current "
"viewport in the following order."
msgstr ""

#: ../../docs/tutorials/inputs/inputevent.rst:77
msgid ""
"First of all, the standard :ref:`Node._input() "
"<class_Node_private_method__input>` function will be called in any node that "
"overrides it (and hasn't disabled input processing with :ref:`Node."
"set_process_input() <class_Node_method_set_process_input>`). If any function "
"consumes the event, it can call :ref:`Viewport.set_input_as_handled() "
"<class_Viewport_method_set_input_as_handled>`, and the event will not spread "
"any more. This ensures that you can filter all events of interest, even "
"before the GUI. For gameplay input, :ref:`Node._unhandled_input() "
"<class_Node_private_method__unhandled_input>` is generally a better fit, "
"because it allows the GUI to intercept the events."
msgstr ""

#: ../../docs/tutorials/inputs/inputevent.rst:82
msgid ""
"Second, it will try to feed the input to the GUI, and see if any control can "
"receive it. If so, the :ref:`Control <class_Control>` will be called via the "
"virtual function :ref:`Control._gui_input() "
"<class_Control_private_method__gui_input>` and the signal \"gui_input\" will "
"be emitted (this function is re-implementable by script by inheriting from "
"it). If the control wants to \"consume\" the event, it will call :ref:"
"`Control.accept_event() <class_Control_method_accept_event>` and the event "
"will not spread any more. Use the :ref:`Control.mouse_filter "
"<class_Control_property_mouse_filter>` property to control whether a :ref:"
"`Control <class_Control>` is notified of mouse events via :ref:`Control."
"_gui_input() <class_Control_private_method__gui_input>` callback, and "
"whether these events are propagated further."
msgstr ""

#: ../../docs/tutorials/inputs/inputevent.rst:92
msgid ""
"If so far no one consumed the event, the :ref:`Node._shortcut_input() "
"<class_Node_private_method__shortcut_input>` callback will be called if "
"overridden (and not disabled with :ref:`Node.set_process_shortcut_input() "
"<class_Node_method_set_process_shortcut_input>`). This happens only for :ref:"
"`InputEventKey <class_InputEventKey>`, :ref:`InputEventShortcut "
"<class_InputEventShortcut>` and :ref:`InputEventJoypadButton "
"<class_InputEventJoypadButton>`. If any function consumes the event, it can "
"call :ref:`Viewport.set_input_as_handled() "
"<class_Viewport_method_set_input_as_handled>`, and the event will not spread "
"any more. The shortcut input callback is ideal for treating events that are "
"intended as shortcuts."
msgstr ""

#: ../../docs/tutorials/inputs/inputevent.rst:99
msgid ""
"If so far no one consumed the event, the :ref:`Node._unhandled_key_input() "
"<class_Node_private_method__unhandled_key_input>` callback will be called if "
"overridden (and not disabled with :ref:`Node."
"set_process_unhandled_key_input() "
"<class_Node_method_set_process_unhandled_key_input>`). This happens only if "
"the event is a :ref:`InputEventKey <class_InputEventKey>`. If any function "
"consumes the event, it can call :ref:`Viewport.set_input_as_handled() "
"<class_Viewport_method_set_input_as_handled>`, and the event will not spread "
"any more. The unhandled key input callback is ideal for key events."
msgstr ""

#: ../../docs/tutorials/inputs/inputevent.rst:105
msgid ""
"If so far no one consumed the event, the :ref:`Node._unhandled_input() "
"<class_Node_private_method__unhandled_input>` callback will be called if "
"overridden (and not disabled with :ref:`Node.set_process_unhandled_input() "
"<class_Node_method_set_process_unhandled_input>`). If any function consumes "
"the event, it can call :ref:`Viewport.set_input_as_handled() "
"<class_Viewport_method_set_input_as_handled>`, and the event will not spread "
"any more. The unhandled input callback is ideal for full-screen gameplay "
"events, so they are not received when a GUI is active."
msgstr ""

#: ../../docs/tutorials/inputs/inputevent.rst:110
msgid ""
"If no one wanted the event so far, and :ref:`Object Picking "
"<class_viewport_property_physics_object_picking>` is turned on, the event is "
"used for object picking. For the root viewport, this can also be enabled in :"
"ref:`Project Settings <class_ProjectSettings_property_physics/common/"
"enable_object_picking>`. In the case of a 3D scene if a :ref:`Camera3D "
"<class_Camera3D>` is assigned to the Viewport, a ray to the physics world "
"(in the ray direction from the click) will be cast. If this ray hits an "
"object, it will call the :ref:`CollisionObject3D._input_event() "
"<class_CollisionObject3D_private_method__input_event>` function in the "
"relevant physics object. In the case of a 2D scene, conceptually the same "
"happens with :ref:`CollisionObject2D._input_event() "
"<class_CollisionObject2D_private_method__input_event>`."
msgstr ""

#: ../../docs/tutorials/inputs/inputevent.rst:119
msgid ""
"When sending events to its child and descendant nodes, the viewport will do "
"so, as depicted in the following graphic, in a reverse depth-first order, "
"starting with the node at the bottom of the scene tree, and ending at the "
"root node. Excluded from this process are Windows and SubViewports."
msgstr ""

#: ../../docs/tutorials/inputs/inputevent.rst:126
msgid ""
"This order doesn't apply to :ref:`Control._gui_input() "
"<class_Control_private_method__gui_input>`, which uses a different method "
"based on event location or focused Control."
msgstr ""

#: ../../docs/tutorials/inputs/inputevent.rst:129
msgid ""
"Since Viewports don't send events to other :ref:`SubViewports "
"<class_SubViewport>`, one of the following methods has to be used:"
msgstr ""

#: ../../docs/tutorials/inputs/inputevent.rst:132
msgid ""
"Use a :ref:`SubViewportContainer <class_SubViewportContainer>`, which "
"automatically sends events to its child :ref:`SubViewports "
"<class_SubViewport>` after :ref:`Node._input() "
"<class_Node_private_method__input>` or :ref:`Control._gui_input() "
"<class_Control_private_method__gui_input>`."
msgstr ""

#: ../../docs/tutorials/inputs/inputevent.rst:135
msgid "Implement event propagation based on the individual requirements."
msgstr ""

#: ../../docs/tutorials/inputs/inputevent.rst:137
msgid ""
"GUI events also travel up the scene tree but, since these events target "
"specific Controls, only direct ancestors of the targeted Control node "
"receive the event."
msgstr ""

#: ../../docs/tutorials/inputs/inputevent.rst:140
msgid ""
"In accordance with Godot's node-based design, this enables specialized child "
"nodes to handle and consume particular events, while their ancestors, and "
"ultimately the scene root, can provide more generalized behavior if needed."
msgstr ""

#: ../../docs/tutorials/inputs/inputevent.rst:146
msgid "Anatomy of an InputEvent"
msgstr ""

#: ../../docs/tutorials/inputs/inputevent.rst:148
msgid ""
":ref:`InputEvent <class_InputEvent>` is just a base built-in type, it does "
"not represent anything and only contains some basic information, such as "
"event ID (which is increased for each event), device index, etc."
msgstr ""

#: ../../docs/tutorials/inputs/inputevent.rst:152
msgid ""
"There are several specialized types of InputEvent, described in the table "
"below:"
msgstr ""

#: ../../docs/tutorials/inputs/inputevent.rst:155
msgid "Event"
msgstr ""

#: ../../docs/tutorials/inputs/inputevent.rst:157
msgid ":ref:`InputEvent <class_InputEvent>`"
msgstr ""

#: ../../docs/tutorials/inputs/inputevent.rst:157
msgid "Empty Input Event."
msgstr ""

#: ../../docs/tutorials/inputs/inputevent.rst:159
msgid ":ref:`InputEventKey <class_InputEventKey>`"
msgstr ""

#: ../../docs/tutorials/inputs/inputevent.rst:159
msgid "Contains a keycode and Unicode value, as well as modifiers."
msgstr ""

#: ../../docs/tutorials/inputs/inputevent.rst:162
msgid ":ref:`InputEventMouseButton <class_InputEventMouseButton>`"
msgstr ""

#: ../../docs/tutorials/inputs/inputevent.rst:162
msgid "Contains click information, such as button, modifiers, etc."
msgstr ""

#: ../../docs/tutorials/inputs/inputevent.rst:165
msgid ":ref:`InputEventMouseMotion <class_InputEventMouseMotion>`"
msgstr ""

#: ../../docs/tutorials/inputs/inputevent.rst:165
msgid ""
"Contains motion information, such as relative and absolute positions and "
"speed."
msgstr ""

#: ../../docs/tutorials/inputs/inputevent.rst:169
msgid ":ref:`InputEventJoypadMotion <class_InputEventJoypadMotion>`"
msgstr ""

#: ../../docs/tutorials/inputs/inputevent.rst:169
msgid "Contains Joystick/Joypad analog axis information."
msgstr ""

#: ../../docs/tutorials/inputs/inputevent.rst:172
msgid ":ref:`InputEventJoypadButton <class_InputEventJoypadButton>`"
msgstr ""

#: ../../docs/tutorials/inputs/inputevent.rst:172
msgid "Contains Joystick/Joypad button information."
msgstr ""

#: ../../docs/tutorials/inputs/inputevent.rst:175
msgid ":ref:`InputEventScreenTouch <class_InputEventScreenTouch>`"
msgstr ""

#: ../../docs/tutorials/inputs/inputevent.rst:175
msgid ""
"Contains multi-touch press/release information. (only available on mobile "
"devices)"
msgstr ""

#: ../../docs/tutorials/inputs/inputevent.rst:179
msgid ":ref:`InputEventScreenDrag <class_InputEventScreenDrag>`"
msgstr ""

#: ../../docs/tutorials/inputs/inputevent.rst:179
msgid ""
"Contains multi-touch drag information. (only available on mobile devices)"
msgstr ""

#: ../../docs/tutorials/inputs/inputevent.rst:182
msgid ":ref:`InputEventMagnifyGesture <class_InputEventMagnifyGesture>`"
msgstr ""

#: ../../docs/tutorials/inputs/inputevent.rst:182
msgid "Contains a position, a factor as well as modifiers."
msgstr ""

#: ../../docs/tutorials/inputs/inputevent.rst:185
msgid ":ref:`InputEventPanGesture <class_InputEventPanGesture>`"
msgstr ""

#: ../../docs/tutorials/inputs/inputevent.rst:185
msgid "Contains a position, a delta as well as modifiers."
msgstr ""

#: ../../docs/tutorials/inputs/inputevent.rst:188
#, fuzzy
msgid ":ref:`InputEventMIDI <class_InputEventMIDI>`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/inputs/inputevent.rst:188
msgid "Contains MIDI-related information."
msgstr ""

#: ../../docs/tutorials/inputs/inputevent.rst:190
msgid ":ref:`InputEventShortcut <class_InputEventShortcut>`"
msgstr ""

#: ../../docs/tutorials/inputs/inputevent.rst:190
msgid "Contains a shortcut."
msgstr ""

#: ../../docs/tutorials/inputs/inputevent.rst:192
msgid ":ref:`InputEventAction <class_InputEventAction>`"
msgstr ""

#: ../../docs/tutorials/inputs/inputevent.rst:192
msgid ""
"Contains a generic action. These events are often generated by the "
"programmer as feedback. (more on this below)"
msgstr ""

#: ../../docs/tutorials/inputs/inputevent.rst:198
#: ../../docs/tutorials/xr/xr_action_map.rst:130
msgid "Actions"
msgstr ""

#: ../../docs/tutorials/inputs/inputevent.rst:200
msgid ""
"Actions are a grouping of zero or more InputEvents into a commonly "
"understood title (for example, the default \"ui_left\" action grouping both "
"joypad-left input and a keyboard's left arrow key). They are not required to "
"represent an InputEvent but are useful because they abstract various inputs "
"when programming the game logic."
msgstr ""

#: ../../docs/tutorials/inputs/inputevent.rst:205
msgid "This allows for:"
msgstr ""

#: ../../docs/tutorials/inputs/inputevent.rst:207
msgid ""
"The same code to work on different devices with different inputs (e.g., "
"keyboard on PC, Joypad on console)."
msgstr ""

#: ../../docs/tutorials/inputs/inputevent.rst:209
msgid "Input to be reconfigured at run-time."
msgstr ""

#: ../../docs/tutorials/inputs/inputevent.rst:210
msgid "Actions to be triggered programmatically at run-time."
msgstr ""

#: ../../docs/tutorials/inputs/inputevent.rst:212
msgid ""
"Actions can be created from the Project Settings menu in the **Input Map** "
"tab and assigned input events."
msgstr ""

#: ../../docs/tutorials/inputs/inputevent.rst:215
msgid ""
"Any event has the methods :ref:`InputEvent.is_action() "
"<class_InputEvent_method_is_action>`, :ref:`InputEvent.is_pressed() "
"<class_InputEvent_method_is_pressed>` and :ref:`InputEvent "
"<class_InputEvent>`."
msgstr ""

#: ../../docs/tutorials/inputs/inputevent.rst:218
msgid ""
"Alternatively, it may be desired to supply the game back with an action from "
"the game code (a good example of this is detecting gestures). The Input "
"singleton has a method for this: :ref:`Input.parse_input_event() "
"<class_input_method_parse_input_event>`. You would normally use it like this:"
msgstr ""

#: ../../docs/tutorials/inputs/inputevent.rst:243
#: ../../docs/tutorials/inputs/input_examples.rst:153
msgid "InputMap"
msgstr ""

#: ../../docs/tutorials/inputs/inputevent.rst:245
msgid ""
"Customizing and re-mapping input from code is often desired. If your whole "
"workflow depends on actions, the :ref:`InputMap <class_InputMap>` singleton "
"is ideal for reassigning or creating different actions at run-time. This "
"singleton is not saved (must be modified manually) and its state is run from "
"the project settings (project.godot). So any dynamic system of this type "
"needs to store settings in the way the programmer best sees fit."
msgstr ""

#: ../../docs/tutorials/inputs/input_examples.rst:4
msgid "Input examples"
msgstr ""

#: ../../docs/tutorials/inputs/input_examples.rst:9
msgid ""
"In this tutorial, you'll learn how to use Godot's :ref:`InputEvent "
"<class_InputEvent>` system to capture player input. There are many different "
"types of input your game may use - keyboard, gamepad, mouse, etc. - and many "
"different ways to turn those inputs into actions in your game. This document "
"will show you some of the most common scenarios, which you can use as "
"starting points for your own projects."
msgstr ""

#: ../../docs/tutorials/inputs/input_examples.rst:16
msgid ""
"For a detailed overview of how Godot's input event system works, see :ref:"
"`doc_inputevent`."
msgstr ""

#: ../../docs/tutorials/inputs/input_examples.rst:20
msgid "Events versus polling"
msgstr ""

#: ../../docs/tutorials/inputs/input_examples.rst:22
msgid ""
"Sometimes you want your game to respond to a certain input event - pressing "
"the \"jump\" button, for example. For other situations, you might want "
"something to happen as long as a key is pressed, such as movement. In the "
"first case, you can use the ``_input()`` function, which will be called "
"whenever an input event occurs. In the second case, Godot provides the :ref:"
"`Input <class_Input>` singleton, which you can use to query the state of an "
"input."
msgstr ""

#: ../../docs/tutorials/inputs/input_examples.rst:29
#: ../../docs/tutorials/platform/ios/plugins_for_ios.rst:509
msgid "Examples:"
msgstr ""

#: ../../docs/tutorials/inputs/input_examples.rst:63
msgid ""
"This gives you the flexibility to mix-and-match the type of input processing "
"you do."
msgstr ""

#: ../../docs/tutorials/inputs/input_examples.rst:66
msgid ""
"For the remainder of this tutorial, we'll focus on capturing individual "
"events in ``_input()``."
msgstr ""

#: ../../docs/tutorials/inputs/input_examples.rst:70
#: ../../docs/tutorials/ui/custom_gui_controls.rst:120
msgid "Input events"
msgstr ""

#: ../../docs/tutorials/inputs/input_examples.rst:72
msgid ""
"Input events are objects that inherit from :ref:`InputEvent "
"<class_InputEvent>`. Depending on the event type, the object will contain "
"specific properties related to that event. To see what events actually look "
"like, add a Node and attach the following script:"
msgstr ""

#: ../../docs/tutorials/inputs/input_examples.rst:98
msgid ""
"As you press keys, move the mouse, and perform other inputs, you'll see each "
"event scroll by in the output window. Here's an example of the output:"
msgstr ""

#: ../../docs/tutorials/inputs/input_examples.rst:117
msgid ""
"As you can see, the results are very different for the different types of "
"input. Key events are even printed as their key symbols. For example, let's "
"consider :ref:`InputEventMouseButton <class_InputEventMouseButton>`. It "
"inherits from the following classes:"
msgstr ""

#: ../../docs/tutorials/inputs/input_examples.rst:122
msgid ""
":ref:`InputEvent <class_InputEvent>` - the base class for all input events"
msgstr ""

#: ../../docs/tutorials/inputs/input_examples.rst:123
msgid ""
":ref:`InputEventWithModifiers <class_InputEventWithModifiers>` - adds the "
"ability to check if modifiers are pressed, such as :kbd:`Shift` or :kbd:"
"`Alt`."
msgstr ""

#: ../../docs/tutorials/inputs/input_examples.rst:124
msgid ""
":ref:`InputEventMouse <class_InputEventMouse>` - adds mouse event "
"properties, such as ``position``"
msgstr ""

#: ../../docs/tutorials/inputs/input_examples.rst:125
msgid ""
":ref:`InputEventMouseButton <class_InputEventMouseButton>` - contains the "
"index of the button that was pressed, whether it was a double-click, etc."
msgstr ""

#: ../../docs/tutorials/inputs/input_examples.rst:127
msgid ""
"It's a good idea to keep the class reference open while you're working with "
"events so you can check the event type's available properties and methods."
msgstr ""

#: ../../docs/tutorials/inputs/input_examples.rst:131
msgid ""
"You can encounter errors if you try to access a property on an input type "
"that doesn't contain it - calling ``position`` on ``InputEventKey`` for "
"example. To avoid this, make sure to test the event type first:"
msgstr ""

#: ../../docs/tutorials/inputs/input_examples.rst:155
msgid ""
"The :ref:`InputMap <class_InputMap>` is the most flexible way to handle a "
"variety of inputs. You use this by creating named input *actions*, to which "
"you can assign any number of input events, such as keypresses or mouse "
"clicks. To see them, and to add your own, open Project -> Project Settings "
"and select the InputMap tab:"
msgstr ""

#: ../../docs/tutorials/inputs/input_examples.rst:164
msgid ""
"A new Godot project includes a number of default actions already defined. To "
"see them, turn on ``Show Built-in Actions`` in the InputMap dialog."
msgstr ""

#: ../../docs/tutorials/inputs/input_examples.rst:168
#, fuzzy
msgid "Capturing actions"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/inputs/input_examples.rst:170
msgid ""
"Once you've defined your actions, you can process them in your scripts using "
"``is_action_pressed()`` and ``is_action_released()`` by passing the name of "
"the action you're looking for:"
msgstr ""

#: ../../docs/tutorials/inputs/input_examples.rst:192
msgid "Keyboard events"
msgstr ""

#: ../../docs/tutorials/inputs/input_examples.rst:194
msgid ""
"Keyboard events are captured in :ref:`InputEventKey <class_InputEventKey>`. "
"While it's recommended to use input actions instead, there may be cases "
"where you want to specifically look at key events. For this example, let's "
"check for the :kbd:`T`:"
msgstr ""

#: ../../docs/tutorials/inputs/input_examples.rst:220
#: ../../docs/tutorials/inputs/input_examples.rst:271
msgid ""
"See :ref:`@GlobalScope_Key <enum_@GlobalScope_Key>` for a list of keycode "
"constants."
msgstr ""

#: ../../docs/tutorials/inputs/input_examples.rst:225
msgid ""
"Due to *keyboard ghosting*, not all key inputs may be registered at a given "
"time if you press too many keys at once. Due to their location on the "
"keyboard, certain keys are more prone to ghosting than others. Some "
"keyboards feature antighosting at a hardware level, but this feature is "
"generally not present on low-end keyboards and laptop keyboards."
msgstr ""

#: ../../docs/tutorials/inputs/input_examples.rst:231
msgid ""
"As a result, it's recommended to use a default keyboard layout that is "
"designed to work well on a keyboard without antighosting. See `this Gamedev "
"Stack Exchange question <https://gamedev.stackexchange.com/a/109002>`__ for "
"more information."
msgstr ""

#: ../../docs/tutorials/inputs/input_examples.rst:237
msgid "Keyboard modifiers"
msgstr ""

#: ../../docs/tutorials/inputs/input_examples.rst:239
msgid ""
"Modifier properties are inherited from :ref:`InputEventWithModifiers "
"<class_InputEventWithModifiers>`. This allows you to check for modifier "
"combinations using boolean properties. Let's imagine you want one thing to "
"happen when the :kbd:`T` is pressed, but something different when it's :kbd:"
"`Shift + T`:"
msgstr ""

#: ../../docs/tutorials/inputs/input_examples.rst:275
msgid "Mouse events"
msgstr ""

#: ../../docs/tutorials/inputs/input_examples.rst:277
msgid ""
"Mouse events stem from the :ref:`InputEventMouse <class_InputEventMouse>` "
"class, and are separated into two types: :ref:`InputEventMouseButton "
"<class_InputEventMouseButton>` and :ref:`InputEventMouseMotion "
"<class_InputEventMouseMotion>`. Note that this means that all mouse events "
"will contain a ``position`` property."
msgstr ""

#: ../../docs/tutorials/inputs/input_examples.rst:283
msgid "Mouse buttons"
msgstr ""

#: ../../docs/tutorials/inputs/input_examples.rst:285
msgid ""
"Capturing mouse buttons is very similar to handling key events. :ref:"
"`@GlobalScope_MouseButton <enum_@GlobalScope_MouseButton>` contains a list "
"of ``MOUSE_BUTTON_*`` constants for each possible button, which will be "
"reported in the event's ``button_index`` property. Note that the scrollwheel "
"also counts as a button - two buttons, to be precise, with both "
"``MOUSE_BUTTON_WHEEL_UP`` and ``MOUSE_BUTTON_WHEEL_DOWN`` being separate "
"events."
msgstr ""

#: ../../docs/tutorials/inputs/input_examples.rst:320
msgid "Mouse motion"
msgstr ""

#: ../../docs/tutorials/inputs/input_examples.rst:322
msgid ""
":ref:`InputEventMouseMotion <class_InputEventMouseMotion>` events occur "
"whenever the mouse moves. You can find the move's distance with the "
"``relative`` property."
msgstr ""

#: ../../docs/tutorials/inputs/input_examples.rst:326
msgid ""
"Here's an example using mouse events to drag-and-drop a :ref:`Sprite2D "
"<class_Sprite2D>` node:"
msgstr ""

#: ../../docs/tutorials/inputs/input_examples.rst:398
msgid "Touch events"
msgstr ""

#: ../../docs/tutorials/inputs/input_examples.rst:400
msgid ""
"If you are using a touchscreen device, you can generate touch events. :ref:"
"`InputEventScreenTouch <class_InputEventScreenTouch>` is equivalent to a "
"mouse click event, and :ref:`InputEventScreenDrag "
"<class_InputEventScreenDrag>` works much the same as mouse motion."
msgstr ""

#: ../../docs/tutorials/inputs/input_examples.rst:405
msgid ""
"To test your touch events on a non-touchscreen device, open Project Settings "
"and go to the \"Input Devices/Pointing\" section. Enable \"Emulate Touch "
"From Mouse\" and your project will interpret mouse clicks and motion as "
"touch events."
msgstr ""

#: ../../docs/tutorials/inputs/mouse_and_input_coordinates.rst:4
msgid "Mouse and input coordinates"
msgstr ""

#: ../../docs/tutorials/inputs/mouse_and_input_coordinates.rst:9
msgid ""
"The reason for this small tutorial is to clear up many common mistakes about "
"input coordinates, obtaining mouse position and screen resolution, etc."
msgstr ""

#: ../../docs/tutorials/inputs/mouse_and_input_coordinates.rst:14
msgid "Hardware display coordinates"
msgstr ""

#: ../../docs/tutorials/inputs/mouse_and_input_coordinates.rst:16
msgid ""
"Using hardware coordinates makes sense in the case of writing complex UIs "
"meant to run on PC, such as editors, MMOs, tools, etc. However, it does not "
"make as much sense outside of that scope."
msgstr ""

#: ../../docs/tutorials/inputs/mouse_and_input_coordinates.rst:21
msgid "Viewport display coordinates"
msgstr ""

#: ../../docs/tutorials/inputs/mouse_and_input_coordinates.rst:23
msgid ""
"Godot uses viewports to display content, and viewports can be scaled by "
"several options (see :ref:`doc_multiple_resolutions` tutorial). Use, then, "
"the functions in nodes to obtain the mouse coordinates and viewport size, "
"for example:"
msgstr ""

#: ../../docs/tutorials/inputs/mouse_and_input_coordinates.rst:55
msgid ""
"Alternatively, it's possible to ask the viewport for the mouse position:"
msgstr ""

#: ../../docs/tutorials/inputs/mouse_and_input_coordinates.rst:66
msgid ""
"When the mouse mode is set to ``Input.MOUSE_MODE_CAPTURED``, the ``event."
"position`` value from ``InputEventMouseMotion`` is the center of the screen. "
"Use ``event.relative`` instead of ``event.position`` and ``event.velocity`` "
"to process mouse movement and position changes."
msgstr ""

#: ../../docs/tutorials/inputs/custom_mouse_cursor.rst:4
msgid "Customizing the mouse cursor"
msgstr ""

#: ../../docs/tutorials/inputs/custom_mouse_cursor.rst:6
msgid ""
"You might want to change the appearance of the mouse cursor in your game in "
"order to suit the overall design. There are two ways to customize the mouse "
"cursor:"
msgstr ""

#: ../../docs/tutorials/inputs/custom_mouse_cursor.rst:10
#: ../../docs/tutorials/inputs/custom_mouse_cursor.rst:28
msgid "Using project settings"
msgstr ""

#: ../../docs/tutorials/inputs/custom_mouse_cursor.rst:11
#: ../../docs/tutorials/inputs/custom_mouse_cursor.rst:46
msgid "Using a script"
msgstr ""

#: ../../docs/tutorials/inputs/custom_mouse_cursor.rst:13
msgid ""
"Using project settings is a simpler (but more limited) way to customize the "
"mouse cursor. The second way is more customizable, but involves scripting:"
msgstr ""

#: ../../docs/tutorials/inputs/custom_mouse_cursor.rst:18
msgid ""
"You could display a \"software\" mouse cursor by hiding the mouse cursor and "
"moving a Sprite2D to the cursor position in a ``_process()`` method, but "
"this will add at least one frame of latency compared to an \"hardware\" "
"mouse cursor. Therefore, it's recommended to use the approach described here "
"whenever possible."
msgstr ""

#: ../../docs/tutorials/inputs/custom_mouse_cursor.rst:24
msgid ""
"If you have to use the \"software\" approach, consider adding an "
"extrapolation step to better display the actual mouse input."
msgstr ""

#: ../../docs/tutorials/inputs/custom_mouse_cursor.rst:30
msgid ""
"Open project settings, go to Display>Mouse Cursor. You will see Custom "
"Image, Custom Image Hotspot and Tooltip Position Offset."
msgstr ""

#: ../../docs/tutorials/inputs/custom_mouse_cursor.rst:35
msgid ""
"Custom Image is the desired image that you would like to set as the mouse "
"cursor. Custom Hotspot is the point in the image that you would like to use "
"as the cursor's detection point."
msgstr ""

#: ../../docs/tutorials/inputs/custom_mouse_cursor.rst:40
msgid ""
"The custom image **must** be 256×256 pixels at most. To avoid rendering "
"issues, sizes lower than or equal to 128×128 are recommended."
msgstr ""

#: ../../docs/tutorials/inputs/custom_mouse_cursor.rst:43
msgid "On the web platform, the maximum allowed cursor image size is 128×128."
msgstr ""

#: ../../docs/tutorials/inputs/custom_mouse_cursor.rst:48
msgid "Create a Node and attach the following script."
msgstr ""

#: ../../docs/tutorials/inputs/custom_mouse_cursor.rst:87
msgid ""
"Check :ref:`Input.set_custom_mouse_cursor() "
"<class_Input_method_set_custom_mouse_cursor>`'s documentation for more "
"information on usage and platform-specific caveats."
msgstr ""

#: ../../docs/tutorials/inputs/custom_mouse_cursor.rst:91
msgid "Cursor list"
msgstr ""

#: ../../docs/tutorials/inputs/custom_mouse_cursor.rst:93
msgid ""
"As documented in the :ref:`Input <class_Input>` class (see the "
"**CursorShape** enum), there are multiple mouse cursors you can define. "
"Which ones you want to use depends on your use case."
msgstr ""

#: ../../docs/tutorials/inputs/controllers_gamepads_joysticks.rst:4
msgid "Controllers, gamepads, and joysticks"
msgstr ""

#: ../../docs/tutorials/inputs/controllers_gamepads_joysticks.rst:6
msgid ""
"Godot supports hundreds of controller models thanks to the community-sourced "
"`SDL game controller database <https://github.com/gabomdq/"
"SDL_GameControllerDB>`__."
msgstr ""

#: ../../docs/tutorials/inputs/controllers_gamepads_joysticks.rst:9
msgid ""
"Controllers are supported on Windows, macOS, Linux, Android, iOS, and HTML5."
msgstr ""

#: ../../docs/tutorials/inputs/controllers_gamepads_joysticks.rst:11
msgid ""
"Note that more specialized devices such as steering wheels, rudder pedals "
"and `HOTAS <https://en.wikipedia.org/wiki/HOTAS>`__ are less tested and may "
"not always work as expected. Overriding force feedback for those devices is "
"also not implemented yet. If you have access to one of those devices, don't "
"hesitate to `report bugs on GitHub <https://github.com/godotengine/godot/"
"blob/master/CONTRIBUTING.md#reporting-bugs>`__."
msgstr ""

#: ../../docs/tutorials/inputs/controllers_gamepads_joysticks.rst:18
#: ../../docs/tutorials/physics/physics_introduction.rst:16
#: ../../docs/tutorials/scripting/gdscript/static_typing.rst:6
msgid "In this guide, you will learn:"
msgstr ""

#: ../../docs/tutorials/inputs/controllers_gamepads_joysticks.rst:20
msgid ""
"**How to write your input logic to support both keyboard and controller "
"inputs.**"
msgstr ""

#: ../../docs/tutorials/inputs/controllers_gamepads_joysticks.rst:21
msgid "**How controllers can behave differently from keyboard/mouse input.**"
msgstr ""

#: ../../docs/tutorials/inputs/controllers_gamepads_joysticks.rst:22
msgid "**Troubleshooting issues with controllers in Godot.**"
msgstr ""

#: ../../docs/tutorials/inputs/controllers_gamepads_joysticks.rst:25
#, fuzzy
msgid "Supporting universal input"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/inputs/controllers_gamepads_joysticks.rst:27
msgid ""
"Thanks to Godot's input action system, Godot makes it possible to support "
"both keyboard and controller input without having to write separate code "
"paths. Instead of hardcoding keys or controller buttons in your scripts, you "
"should create *input actions* in the Project Settings which will then refer "
"to specified key and controller inputs."
msgstr ""

#: ../../docs/tutorials/inputs/controllers_gamepads_joysticks.rst:33
msgid ""
"Input actions are explained in detail on the :ref:`doc_inputevent` page."
msgstr ""

#: ../../docs/tutorials/inputs/controllers_gamepads_joysticks.rst:37
msgid ""
"Unlike keyboard input, supporting both mouse and controller input for an "
"action (such as looking around in a first-person game) will require "
"different code paths since these have to be handled separately."
msgstr ""

#: ../../docs/tutorials/inputs/controllers_gamepads_joysticks.rst:42
msgid "Which Input singleton method should I use?"
msgstr ""

#: ../../docs/tutorials/inputs/controllers_gamepads_joysticks.rst:44
msgid "There are 3 ways to get input in an analog-aware way:"
msgstr ""

#: ../../docs/tutorials/inputs/controllers_gamepads_joysticks.rst:46
msgid ""
"When you have two axes (such as joystick or WASD movement) and want both "
"axes to behave as a single input, use ``Input.get_vector()``:"
msgstr ""

#: ../../docs/tutorials/inputs/controllers_gamepads_joysticks.rst:80
msgid ""
"When you have one axis that can go both ways (such as a throttle on a flight "
"stick), or when you want to handle separate axes individually, use ``Input."
"get_axis()``:"
msgstr ""

#: ../../docs/tutorials/inputs/controllers_gamepads_joysticks.rst:101
msgid ""
"For other types of analog input, such as handling a trigger or handling one "
"direction at a time, use ``Input.get_action_strength()``:"
msgstr ""

#: ../../docs/tutorials/inputs/controllers_gamepads_joysticks.rst:115
msgid ""
"For non-analog digital/boolean input (only \"pressed\" or \"not pressed\" "
"values), such as controller buttons, mouse buttons or keyboard keys, use "
"``Input.is_action_pressed()``:"
msgstr ""

#: ../../docs/tutorials/inputs/controllers_gamepads_joysticks.rst:132
msgid ""
"If you need to know whether an input was *just* pressed in the previous "
"frame, use ``Input.is_action_just_pressed()`` instead of ``Input."
"is_action_pressed()``. Unlike ``Input.is_action_pressed()`` which returns "
"``true`` as long as the input is held, ``Input.is_action_just_pressed()`` "
"will only return ``true`` for one frame after the button has been pressed."
msgstr ""

#: ../../docs/tutorials/inputs/controllers_gamepads_joysticks.rst:139
msgid ""
"In Godot versions before 3.4, such as 3.3, ``Input.get_vector()`` and "
"``Input.get_axis()`` aren't available. Only ``Input.get_action_strength()`` "
"and ``Input.is_action_pressed()`` are available in Godot 3.3."
msgstr ""

#: ../../docs/tutorials/inputs/controllers_gamepads_joysticks.rst:144
#, fuzzy
msgid "Vibration"
msgstr "Uvod"

#: ../../docs/tutorials/inputs/controllers_gamepads_joysticks.rst:146
msgid ""
"Vibration (also called *haptic feedback*) can be used to enhance the feel of "
"a game. For instance, in a racing game, you can convey the surface the car "
"is currently driving on through vibration, or create a sudden vibration on a "
"crash."
msgstr ""

#: ../../docs/tutorials/inputs/controllers_gamepads_joysticks.rst:150
msgid ""
"Use the Input singleton's :ref:"
"`start_joy_vibration<class_Input_method_start_joy_vibration>` method to "
"start vibrating a gamepad. Use :ref:"
"`stop_joy_vibration<class_Input_method_stop_joy_vibration>` to stop "
"vibration early (useful if no duration was specified when starting)."
msgstr ""

#: ../../docs/tutorials/inputs/controllers_gamepads_joysticks.rst:156
msgid ""
"On mobile devices, you can also use :ref:"
"`vibrate_handheld<class_Input_method_vibrate_handheld>` to vibrate the "
"device itself (independently from the gamepad). On Android, this requires "
"the ``VIBRATE`` permission to be enabled in the Android export preset before "
"exporting the project."
msgstr ""

#: ../../docs/tutorials/inputs/controllers_gamepads_joysticks.rst:164
msgid ""
"Vibration can be uncomfortable for certain players. Make sure to provide an "
"in-game slider to disable vibration or reduce its intensity."
msgstr ""

#: ../../docs/tutorials/inputs/controllers_gamepads_joysticks.rst:168
msgid "Differences between keyboard/mouse and controller input"
msgstr ""

#: ../../docs/tutorials/inputs/controllers_gamepads_joysticks.rst:170
msgid ""
"If you're used to handling keyboard and mouse input, you may be surprised by "
"how controllers handle specific situations."
msgstr ""

#: ../../docs/tutorials/inputs/controllers_gamepads_joysticks.rst:174
msgid "Dead zone"
msgstr ""

#: ../../docs/tutorials/inputs/controllers_gamepads_joysticks.rst:176
msgid ""
"Unlike keyboards and mice, controllers offer axes with *analog* inputs. The "
"upside of analog inputs is that they offer additional flexibility for "
"actions. Unlike digital inputs which can only provide strengths of ``0.0`` "
"and ``1.0``, an analog input can provide *any* strength between ``0.0`` and "
"``1.0``. The downside is that without a deadzone system, an analog axis' "
"strength will never be equal to ``0.0`` due to how the controller is "
"physically built. Instead, it will linger at a low value such as ``0.062``. "
"This phenomenon is known as *drifting* and can be more noticeable on old or "
"faulty controllers."
msgstr ""

#: ../../docs/tutorials/inputs/controllers_gamepads_joysticks.rst:185
msgid ""
"Let's take a racing game as a real-world example. Thanks to analog inputs, "
"we can steer the car slowly in one direction or another. However, without a "
"deadzone system, the car would slowly steer by itself even if the player "
"isn't touching the joystick. This is because the directional axis strength "
"won't be equal to ``0.0`` when we expect it to. Since we don't want our car "
"to steer by itself in this case, we define a \"dead zone\" value of ``0.2`` "
"which will ignore all input whose strength is lower than ``0.2``. An ideal "
"dead zone value is high enough to ignore the input caused by joystick "
"drifting, but is low enough to not ignore actual input from the player."
msgstr ""

#: ../../docs/tutorials/inputs/controllers_gamepads_joysticks.rst:195
msgid ""
"Godot features a built-in deadzone system to tackle this problem. The "
"default value is ``0.5``, but you can adjust it on a per-action basis in the "
"Project Settings' Input Map tab. For ``Input.get_vector()``, the deadzone "
"can be specified as an optional 5th parameter. If not specified, it will "
"calculate the average deadzone value from all of the actions in the vector."
msgstr ""

#: ../../docs/tutorials/inputs/controllers_gamepads_joysticks.rst:202
msgid "\"Echo\" events"
msgstr ""

#: ../../docs/tutorials/inputs/controllers_gamepads_joysticks.rst:204
msgid ""
"Unlike keyboard input, holding down a controller button such as a D-pad "
"direction will **not** generate repeated input events at fixed intervals "
"(also known as \"echo\" events). This is because the operating system never "
"sends \"echo\" events for controller input in the first place."
msgstr ""

#: ../../docs/tutorials/inputs/controllers_gamepads_joysticks.rst:209
msgid ""
"If you want controller buttons to send echo events, you will have to "
"generate :ref:`class_InputEvent` objects by code and parse them using :ref:"
"`Input.parse_input_event() <class_Input_method_parse_input_event>` at "
"regular intervals. This can be accomplished with the help of a :ref:"
"`class_Timer` node."
msgstr ""

#: ../../docs/tutorials/inputs/controllers_gamepads_joysticks.rst:216
#, fuzzy
msgid "Window focus"
msgstr "Windows"

#: ../../docs/tutorials/inputs/controllers_gamepads_joysticks.rst:218
msgid ""
"Unlike keyboard input, controller inputs can be seen by **all** windows on "
"the operating system, including unfocused windows."
msgstr ""

#: ../../docs/tutorials/inputs/controllers_gamepads_joysticks.rst:221
msgid ""
"While this is useful for `third-party split screen functionality <https://"
"nucleus-coop.github.io/>`__, it can also have adverse effects. Players may "
"accidentally send controller inputs to the running project while interacting "
"with another window."
msgstr ""

#: ../../docs/tutorials/inputs/controllers_gamepads_joysticks.rst:226
msgid ""
"If you wish to ignore events when the project window isn't focused, you will "
"need to create an :ref:`autoload <doc_singletons_autoload>` called ``Focus`` "
"with the following script and use it to check all your inputs:"
msgstr ""

#: ../../docs/tutorials/inputs/controllers_gamepads_joysticks.rst:258
msgid ""
"Then, instead of using ``Input.is_action_pressed(action)``, use ``Focus."
"input_is_action_pressed(action)`` where ``action`` is the name of the input "
"action. Also, instead of using ``event.is_action_pressed(action)``, use "
"``Focus.event_is_action_pressed(event, action)`` where ``event`` is an "
"InputEvent reference and ``action`` is the name of the input action."
msgstr ""

#: ../../docs/tutorials/inputs/controllers_gamepads_joysticks.rst:265
msgid "Power saving prevention"
msgstr ""

#: ../../docs/tutorials/inputs/controllers_gamepads_joysticks.rst:267
msgid ""
"Unlike keyboard and mouse input, controller inputs do **not** inhibit sleep "
"and power saving measures (such as turning off the screen after a certain "
"amount of time has passed)."
msgstr ""

#: ../../docs/tutorials/inputs/controllers_gamepads_joysticks.rst:271
msgid ""
"To combat this, Godot enables power saving prevention by default when a "
"project is running. If you notice the system is turning off its display when "
"playing with a gamepad, check the value of **Display > Window > Energy "
"Saving > Keep Screen On** in the Project Settings."
msgstr ""

#: ../../docs/tutorials/inputs/controllers_gamepads_joysticks.rst:276
msgid ""
"On Linux, power saving prevention requires the engine to be able to use D-"
"Bus. Check whether D-Bus is installed and reachable if running the project "
"within a Flatpak, as sandboxing restrictions may make this impossible by "
"default."
msgstr ""

#: ../../docs/tutorials/inputs/controllers_gamepads_joysticks.rst:285
msgid ""
"You can view a list of `known issues with controller support <https://github."
"com/godotengine/godot/issues?"
"q=is%3Aopen+is%3Aissue+label%3Atopic%3Ainput+gamepad>`__ on GitHub."
msgstr ""

#: ../../docs/tutorials/inputs/controllers_gamepads_joysticks.rst:290
msgid "My controller isn't recognized by Godot."
msgstr ""

#: ../../docs/tutorials/inputs/controllers_gamepads_joysticks.rst:292
msgid ""
"First, check that your controller is recognized by other applications. You "
"can use the `Gamepad Tester <https://gamepad-tester.com/>`__ website to "
"confirm that your controller is recognized."
msgstr ""

#: ../../docs/tutorials/inputs/controllers_gamepads_joysticks.rst:296
msgid ""
"On Windows Godot only supports up to 4 controllers at a time. This is "
"because Godot uses the XInput API, which is limited to supporting 4 "
"controllers at once. Additional controllers above this limit are ignored by "
"Godot."
msgstr ""

#: ../../docs/tutorials/inputs/controllers_gamepads_joysticks.rst:301
msgid "My controller has incorrectly mapped buttons or axes."
msgstr ""

#: ../../docs/tutorials/inputs/controllers_gamepads_joysticks.rst:303
msgid ""
"First, if your controller provides some kind of firmware update utility, "
"make sure to run it to get the latest fixes from the manufacturer. For "
"instance, Xbox One and Xbox Series controllers can have their firmware "
"updated using the `Xbox Accessories app <https://www.microsoft.com/en-us/p/"
"xbox-accessories/9nblggh30xj3>`__. (This application only runs on Windows, "
"so you have to use a Windows machine or a Windows virtual machine with USB "
"support to update the controller's firmware.) After updating the "
"controller's firmware, unpair the controller and pair it again with your PC "
"if you are using the controller in wireless mode."
msgstr ""

#: ../../docs/tutorials/inputs/controllers_gamepads_joysticks.rst:312
msgid ""
"If buttons are incorrectly mapped, this may be due to an erroneous mapping "
"from the `SDL game controller database <https://github.com/gabomdq/"
"SDL_GameControllerDB>`__. You can contribute an updated mapping to be "
"included in the next Godot version by opening a pull request on the linked "
"repository."
msgstr ""

#: ../../docs/tutorials/inputs/controllers_gamepads_joysticks.rst:317
msgid ""
"There are many ways to create mappings. One option is to use the mapping "
"wizard in the `official Joypads demo <https://godotengine.org/asset-library/"
"asset/2785>`__. Once you have a working mapping for your controller, you can "
"test it by defining the ``SDL_GAMECONTROLLERCONFIG`` environment variable "
"before running Godot:"
msgstr ""

#: ../../docs/tutorials/inputs/controllers_gamepads_joysticks.rst:338
msgid ""
"To test mappings on non-desktop platforms or to distribute your project with "
"additional controller mappings, you can add them by calling :ref:`Input."
"add_joy_mapping() <class_Input_method_add_joy_mapping>` as early as possible "
"in a script's ``_ready()`` function."
msgstr ""

#: ../../docs/tutorials/inputs/controllers_gamepads_joysticks.rst:344
msgid "My controller works on a given platform, but not on another platform."
msgstr ""

#: ../../docs/tutorials/inputs/controllers_gamepads_joysticks.rst:349
msgid ""
"If you're using a self-compiled engine binary, make sure it was compiled "
"with udev support. This is enabled by default, but it is possible to disable "
"udev support by specifying ``udev=no`` on the SCons command line. If you're "
"using an engine binary supplied by a Linux distribution, double-check "
"whether it was compiled with udev support."
msgstr ""

#: ../../docs/tutorials/inputs/controllers_gamepads_joysticks.rst:355
msgid ""
"Controllers can still work without udev support, but it is less reliable as "
"regular polling must be used to check for controllers being connected or "
"disconnected during gameplay (hotplugging)."
msgstr ""

#: ../../docs/tutorials/inputs/controllers_gamepads_joysticks.rst:360
#: ../../docs/tutorials/platform/web/index.rst:6
msgid "HTML5"
msgstr ""

#: ../../docs/tutorials/inputs/controllers_gamepads_joysticks.rst:362
msgid ""
"HTML5 controller support is often less reliable compared to \"native\" "
"platforms. The quality of controller support tends to vary wildly across "
"browsers. As a result, you may have to instruct your players to use a "
"different browser if they can't get their controller to work."
msgstr ""

#: ../../docs/tutorials/inputs/handling_quit_requests.rst:4
msgid "Handling quit requests"
msgstr ""

#: ../../docs/tutorials/inputs/handling_quit_requests.rst:7
msgid "Quitting"
msgstr ""

#: ../../docs/tutorials/inputs/handling_quit_requests.rst:9
msgid ""
"Most platforms have the option to request the application to quit. On "
"desktops, this is usually done with the \"x\" icon on the window title bar. "
"On Android, the back button is used to quit when on the main screen (and to "
"go back otherwise)."
msgstr ""

#: ../../docs/tutorials/inputs/handling_quit_requests.rst:15
msgid "Handling the notification"
msgstr ""

#: ../../docs/tutorials/inputs/handling_quit_requests.rst:17
msgid ""
"On desktop and web platforms, :ref:`Node <class_Node>` receives a special "
"``NOTIFICATION_WM_CLOSE_REQUEST`` notification when quitting is requested "
"from the window manager."
msgstr ""

#: ../../docs/tutorials/inputs/handling_quit_requests.rst:21
msgid ""
"On Android, ``NOTIFICATION_WM_GO_BACK_REQUEST`` is sent instead. Pressing "
"the Back button will exit the application if **Application > Config > Quit "
"On Go Back** is checked in the Project Settings (which is the default)."
msgstr ""

#: ../../docs/tutorials/inputs/handling_quit_requests.rst:28
msgid ""
"``NOTIFICATION_WM_GO_BACK_REQUEST`` isn't supported on iOS, as iOS devices "
"don't have a physical Back button."
msgstr ""

#: ../../docs/tutorials/inputs/handling_quit_requests.rst:31
msgid "Handling the notification is done as follows (on any node):"
msgstr ""

#: ../../docs/tutorials/inputs/handling_quit_requests.rst:48
msgid ""
"When developing mobile apps, quitting is not desired unless the user is on "
"the main screen, so the behavior can be changed."
msgstr ""

#: ../../docs/tutorials/inputs/handling_quit_requests.rst:51
msgid ""
"It is important to note that by default, Godot apps have the built-in "
"behavior to quit when quit is requested from the window manager. This can be "
"changed, so that the user can take care of the complete quitting procedure:"
msgstr ""

#: ../../docs/tutorials/inputs/handling_quit_requests.rst:66
msgid "Sending your own quit notification"
msgstr ""

#: ../../docs/tutorials/inputs/handling_quit_requests.rst:68
msgid ""
"While forcing the application to close can be done by calling :ref:"
"`SceneTree.quit <class_SceneTree_method_quit>`, doing so will not send the "
"``NOTIFICATION_WM_CLOSE_REQUEST`` to the nodes in the scene tree. Quitting "
"by calling :ref:`SceneTree.quit <class_SceneTree_method_quit>` will not "
"allow custom actions to complete (such as saving, confirming the quit, or "
"debugging), even if you try to delay the line that forces the quit."
msgstr ""

#: ../../docs/tutorials/inputs/handling_quit_requests.rst:75
msgid ""
"Instead, if you want to notify the nodes in the scene tree about the "
"upcoming program termination, you should send the notification yourself:"
msgstr ""

#: ../../docs/tutorials/inputs/handling_quit_requests.rst:87
msgid ""
"Sending this notification will inform all nodes about the program "
"termination, but will not terminate the program itself *unlike in 3.X*. In "
"order to achieve the previous behavior, :ref:`SceneTree.quit "
"<class_SceneTree_method_quit>` should be called after the notification."
msgstr ""

#: ../../docs/tutorials/math/vector_math.rst:4
msgid "Vector math"
msgstr ""

#: ../../docs/tutorials/math/vector_math.rst:9
msgid ""
"This tutorial is a short and practical introduction to linear algebra as it "
"applies to game development. Linear algebra is the study of vectors and "
"their uses. Vectors have many applications in both 2D and 3D development and "
"Godot uses them extensively. Developing a good understanding of vector math "
"is essential to becoming a strong game developer."
msgstr ""

#: ../../docs/tutorials/math/vector_math.rst:15
msgid ""
"This tutorial is **not** a formal textbook on linear algebra. We will only "
"be looking at how it is applied to game development. For a broader look at "
"the mathematics, see https://www.khanacademy.org/math/linear-algebra"
msgstr ""

#: ../../docs/tutorials/math/vector_math.rst:21
msgid "Coordinate systems (2D)"
msgstr ""

#: ../../docs/tutorials/math/vector_math.rst:23
msgid ""
"In 2D space, coordinates are defined using a horizontal axis (``x``) and a "
"vertical axis (``y``). A particular position in 2D space is written as a "
"pair of values such as ``(4, 3)``."
msgstr ""

#: ../../docs/tutorials/math/vector_math.rst:29
msgid ""
"If you're new to computer graphics, it might seem odd that the positive "
"``y`` axis points **downwards** instead of upwards, as you probably learned "
"in math class. However, this is common in most computer graphics "
"applications."
msgstr ""

#: ../../docs/tutorials/math/vector_math.rst:34
msgid ""
"Any position in the 2D plane can be identified by a pair of numbers in this "
"way. However, we can also think of the position ``(4, 3)`` as an **offset** "
"from the ``(0, 0)`` point, or **origin**. Draw an arrow pointing from the "
"origin to the point:"
msgstr ""

#: ../../docs/tutorials/math/vector_math.rst:41
msgid ""
"This is a **vector**. A vector represents a lot of useful information. As "
"well as telling us that the point is at ``(4, 3)``, we can also think of it "
"as an angle ``θ`` (theta) and a length (or magnitude) ``m``. In this case, "
"the arrow is a **position vector** - it denotes a position in space, "
"relative to the origin."
msgstr ""

#: ../../docs/tutorials/math/vector_math.rst:47
msgid ""
"A very important point to consider about vectors is that they only represent "
"**relative** direction and magnitude. There is no concept of a vector's "
"position. The following two vectors are identical:"
msgstr ""

#: ../../docs/tutorials/math/vector_math.rst:53
msgid ""
"Both vectors represent a point 4 units to the right and 3 units below some "
"starting point. It does not matter where on the plane you draw the vector, "
"it always represents a relative direction and magnitude."
msgstr ""

#: ../../docs/tutorials/math/vector_math.rst:58
msgid "Vector operations"
msgstr ""

#: ../../docs/tutorials/math/vector_math.rst:60
msgid ""
"You can use either method (x and y coordinates or angle and magnitude) to "
"refer to a vector, but for convenience, programmers typically use the "
"coordinate notation. For example, in Godot, the origin is the top-left "
"corner of the screen, so to place a 2D node named ``Node2D`` 400 pixels to "
"the right and 300 pixels down, use the following code:"
msgstr ""

#: ../../docs/tutorials/math/vector_math.rst:76
msgid ""
"Godot supports both :ref:`Vector2 <class_Vector2>` and :ref:`Vector3 "
"<class_Vector3>` for 2D and 3D usage, respectively. The same mathematical "
"rules discussed in this article apply to both types, and wherever we link to "
"``Vector2`` methods in the class reference, you can also check out their "
"``Vector3`` counterparts."
msgstr ""

#: ../../docs/tutorials/math/vector_math.rst:83
msgid "Member access"
msgstr ""

#: ../../docs/tutorials/math/vector_math.rst:85
msgid ""
"The individual components of the vector can be accessed directly by name."
msgstr ""

#: ../../docs/tutorials/math/vector_math.rst:107
msgid "Adding vectors"
msgstr ""

#: ../../docs/tutorials/math/vector_math.rst:109
msgid ""
"When adding or subtracting two vectors, the corresponding components are "
"added:"
msgstr ""

#: ../../docs/tutorials/math/vector_math.rst:120
msgid ""
"We can also see this visually by adding the second vector at the end of the "
"first:"
msgstr ""

#: ../../docs/tutorials/math/vector_math.rst:125
msgid "Note that adding ``a + b`` gives the same result as ``b + a``."
msgstr ""

#: ../../docs/tutorials/math/vector_math.rst:128
msgid "Scalar multiplication"
msgstr ""

#: ../../docs/tutorials/math/vector_math.rst:130
msgid ""
"Vectors represent both direction and magnitude. A value representing only "
"magnitude is called a **scalar**. Scalars use the :ref:`class_float` type in "
"Godot."
msgstr ""

#: ../../docs/tutorials/math/vector_math.rst:134
msgid "A vector can be multiplied by a **scalar**:"
msgstr ""

#: ../../docs/tutorials/math/vector_math.rst:151
msgid ""
"Multiplying a vector by a positive scalar does not change its direction, "
"only its magnitude. Multiplying with a negative scalar results in a vector "
"in the opposite direction. This is how you **scale** a vector."
msgstr ""

#: ../../docs/tutorials/math/vector_math.rst:156
msgid "Practical applications"
msgstr ""

#: ../../docs/tutorials/math/vector_math.rst:158
msgid "Let's look at two common uses for vector addition and subtraction."
msgstr ""

#: ../../docs/tutorials/math/vector_math.rst:161
msgid "Movement"
msgstr ""

#: ../../docs/tutorials/math/vector_math.rst:163
msgid ""
"A vector can represent **any** quantity with a magnitude and direction. "
"Typical examples are: position, velocity, acceleration, and force. In this "
"image, the spaceship at step 1 has a position vector of ``(1, 3)`` and a "
"velocity vector of ``(2, 1)``. The velocity vector represents how far the "
"ship moves each step. We can find the position for step 2 by adding the "
"velocity to the current position."
msgstr ""

#: ../../docs/tutorials/math/vector_math.rst:171
msgid ""
"Velocity measures the **change** in position per unit of time. The new "
"position is found by adding the velocity multiplied by the elapsed time "
"(here assumed to be one unit, e.g. 1 s) to the previous position."
msgstr ""

#: ../../docs/tutorials/math/vector_math.rst:175
msgid ""
"In a typical 2D game scenario, you would have a velocity in pixels per "
"second, and multiply it by the ``delta`` parameter (time elapsed since the "
"previous frame) from the :ref:`_process() "
"<class_Node_private_method__process>` or :ref:`_physics_process() "
"<class_Node_private_method__physics_process>` callbacks."
msgstr ""

#: ../../docs/tutorials/math/vector_math.rst:182
msgid "Pointing toward a target"
msgstr ""

#: ../../docs/tutorials/math/vector_math.rst:184
msgid ""
"In this scenario, you have a tank that wishes to point its turret at a "
"robot. Subtracting the tank's position from the robot's position gives the "
"vector pointing from the tank to the robot."
msgstr ""

#: ../../docs/tutorials/math/vector_math.rst:190
msgid "To find a vector pointing from ``A`` to ``B``, use ``B - A``."
msgstr ""

#: ../../docs/tutorials/math/vector_math.rst:193
msgid "Unit vectors"
msgstr ""

#: ../../docs/tutorials/math/vector_math.rst:195
msgid ""
"A vector with **magnitude** of ``1`` is called a **unit vector**. They are "
"also sometimes referred to as **direction vectors** or **normals**. Unit "
"vectors are helpful when you need to keep track of a direction."
msgstr ""

#: ../../docs/tutorials/math/vector_math.rst:200
msgid "Normalization"
msgstr ""

#: ../../docs/tutorials/math/vector_math.rst:202
msgid ""
"**Normalizing** a vector means reducing its length to ``1`` while preserving "
"its direction. This is done by dividing each of its components by its "
"magnitude. Because this is such a common operation, Godot provides a "
"dedicated :ref:`normalized() <class_Vector2_method_normalized>` method for "
"this:"
msgstr ""

#: ../../docs/tutorials/math/vector_math.rst:216
msgid ""
"Because normalization involves dividing by the vector's length, you cannot "
"normalize a vector of length ``0``. Attempting to do so would normally "
"result in an error. In GDScript though, trying to call the ``normalized()`` "
"method on a vector of length 0 leaves the value untouched and avoids the "
"error for you."
msgstr ""

#: ../../docs/tutorials/math/vector_math.rst:223
msgid "Reflection"
msgstr ""

#: ../../docs/tutorials/math/vector_math.rst:225
msgid ""
"A common use of unit vectors is to indicate **normals**. Normal vectors are "
"unit vectors aligned perpendicularly to a surface, defining its direction. "
"They are commonly used for lighting, collisions, and other operations "
"involving surfaces."
msgstr ""

#: ../../docs/tutorials/math/vector_math.rst:229
msgid ""
"For example, imagine we have a moving ball that we want to bounce off a wall "
"or other object:"
msgstr ""

#: ../../docs/tutorials/math/vector_math.rst:234
msgid ""
"The surface normal has a value of ``(0, -1)`` because this is a horizontal "
"surface. When the ball collides, we take its remaining motion (the amount "
"left over when it hits the surface) and reflect it using the normal. In "
"Godot, there is a :ref:`bounce() <class_Vector2_method_bounce>` method to "
"handle this. Here is a code example of the above diagram using a :ref:"
"`CharacterBody2D <class_CharacterBody2D>`:"
msgstr ""

#: ../../docs/tutorials/math/vector_math.rst:261
msgid "Dot product"
msgstr ""

#: ../../docs/tutorials/math/vector_math.rst:263
msgid ""
"The **dot product** is one of the most important concepts in vector math, "
"but is often misunderstood. Dot product is an operation on two vectors that "
"returns a **scalar**. Unlike a vector, which contains both magnitude and "
"direction, a scalar value has only magnitude."
msgstr ""

#: ../../docs/tutorials/math/vector_math.rst:268
msgid "The formula for dot product takes two common forms:"
msgstr ""

#: ../../docs/tutorials/math/vector_math.rst:272
#: ../../docs/tutorials/scripting/singletons_autoload.rst:255
msgid "and"
msgstr ""

#: ../../docs/tutorials/math/vector_math.rst:276
msgid ""
"The mathematical notation *||A||* represents the magnitude of vector ``A``, "
"and *A*\\ :sub:`x` means the ``x`` component of vector ``A``."
msgstr ""

#: ../../docs/tutorials/math/vector_math.rst:279
msgid ""
"However, in most cases it is easiest to use the built-in :ref:`dot() "
"<class_Vector2_method_dot>` method. Note that the order of the two vectors "
"does not matter:"
msgstr ""

#: ../../docs/tutorials/math/vector_math.rst:293
msgid ""
"The dot product is most useful when used with unit vectors, making the first "
"formula reduce to just ``cos(θ)``. This means we can use the dot product to "
"tell us something about the angle between two vectors:"
msgstr ""

#: ../../docs/tutorials/math/vector_math.rst:299
msgid ""
"When using unit vectors, the result will always be between ``-1`` (180°) and "
"``1`` (0°)."
msgstr ""

#: ../../docs/tutorials/math/vector_math.rst:303
msgid "Facing"
msgstr ""

#: ../../docs/tutorials/math/vector_math.rst:305
msgid ""
"We can use this fact to detect whether an object is facing toward another "
"object. In the diagram below, the player ``P`` is trying to avoid the "
"zombies ``A`` and ``B``. Assuming a zombie's field of view is **180°**, can "
"they see the player?"
msgstr ""

#: ../../docs/tutorials/math/vector_math.rst:312
msgid ""
"The green arrows ``fA`` and ``fB`` are **unit vectors** representing the "
"zombie's facing direction and the blue semicircle represents its field of "
"view. For zombie ``A``, we find the direction vector ``AP`` pointing to the "
"player using ``P - A`` and normalize it, however, Godot has a helper method "
"to do this called :ref:`direction_to() <class_Vector2_method_direction_to>`. "
"If the angle between this vector and the facing vector is less than 90°, "
"then the zombie can see the player."
msgstr ""

#: ../../docs/tutorials/math/vector_math.rst:320
msgid "In code it would look like this:"
msgstr ""

#: ../../docs/tutorials/math/vector_math.rst:338
msgid "Cross product"
msgstr ""

#: ../../docs/tutorials/math/vector_math.rst:340
msgid ""
"Like the dot product, the **cross product** is an operation on two vectors. "
"However, the result of the cross product is a vector with a direction that "
"is perpendicular to both. Its magnitude depends on their relative angle. If "
"two vectors are parallel, the result of their cross product will be a null "
"vector."
msgstr ""

#: ../../docs/tutorials/math/vector_math.rst:349
msgid "The cross product is calculated like this:"
msgstr ""

#: ../../docs/tutorials/math/vector_math.rst:366
msgid ""
"With Godot, you can use the built-in :ref:`Vector3.cross() "
"<class_Vector3_method_cross>` method:"
msgstr ""

#: ../../docs/tutorials/math/vector_math.rst:378
msgid ""
"The cross product is not mathematically defined in 2D. The :ref:`Vector2."
"cross() <class_Vector2_method_cross>` method is a commonly used analog of "
"the 3D cross product for 2D vectors."
msgstr ""

#: ../../docs/tutorials/math/vector_math.rst:382
msgid ""
"In the cross product, order matters. ``a.cross(b)`` does not give the same "
"result as ``b.cross(a)``. The resulting vectors point in **opposite** "
"directions."
msgstr ""

#: ../../docs/tutorials/math/vector_math.rst:387
msgid "Calculating normals"
msgstr ""

#: ../../docs/tutorials/math/vector_math.rst:389
msgid ""
"One common use of cross products is to find the surface normal of a plane or "
"surface in 3D space. If we have the triangle ``ABC`` we can use vector "
"subtraction to find two edges ``AB`` and ``AC``. Using the cross product, "
"``AB × AC`` produces a vector perpendicular to both: the surface normal."
msgstr ""

#: ../../docs/tutorials/math/vector_math.rst:394
msgid "Here is a function to calculate a triangle's normal:"
msgstr ""

#: ../../docs/tutorials/math/vector_math.rst:418
msgid "Pointing to a target"
msgstr ""

#: ../../docs/tutorials/math/vector_math.rst:420
msgid ""
"In the dot product section above, we saw how it could be used to find the "
"angle between two vectors. However, in 3D, this is not enough information. "
"We also need to know what axis to rotate around. We can find that by "
"calculating the cross product of the current facing direction and the target "
"direction. The resulting perpendicular vector is the axis of rotation."
msgstr ""

#: ../../docs/tutorials/math/vector_math.rst:427
#: ../../docs/tutorials/math/vectors_advanced.rst:586
#: ../../docs/tutorials/xr/introducing_xr_tools.rst:76
msgid "More information"
msgstr ""

#: ../../docs/tutorials/math/vector_math.rst:429
msgid ""
"For more information on using vector math in Godot, see the following "
"articles:"
msgstr ""

#: ../../docs/tutorials/math/vector_math.rst:431
msgid ":ref:`doc_vectors_advanced`"
msgstr ""

#: ../../docs/tutorials/math/vector_math.rst:432
#: ../../docs/tutorials/math/vectors_advanced.rst:590
msgid ":ref:`doc_matrices_and_transforms`"
msgstr ""

#: ../../docs/tutorials/math/vectors_advanced.rst:4
msgid "Advanced vector math"
msgstr ""

#: ../../docs/tutorials/math/vectors_advanced.rst:7
msgid "Planes"
msgstr ""

#: ../../docs/tutorials/math/vectors_advanced.rst:9
msgid ""
"The dot product has another interesting property with unit vectors. Imagine "
"that perpendicular to that vector (and through the origin) passes a plane. "
"Planes divide the entire space into positive (over the plane) and negative "
"(under the plane), and (contrary to popular belief) you can also use their "
"math in 2D:"
msgstr ""

#: ../../docs/tutorials/math/vectors_advanced.rst:17
msgid ""
"Unit vectors that are perpendicular to a surface (so, they describe the "
"orientation of the surface) are called **unit normal vectors**. Though, "
"usually they are just abbreviated as *normals*. Normals appear in planes, 3D "
"geometry (to determine where each face or vertex is siding), etc. A "
"**normal** *is* a **unit vector**, but it's called *normal* because of its "
"usage. (Just like we call (0,0) the Origin!)."
msgstr ""

#: ../../docs/tutorials/math/vectors_advanced.rst:24
msgid ""
"The plane passes by the origin and the surface of it is perpendicular to the "
"unit vector (or *normal*). The side towards the vector points to is the "
"positive half-space, while the other side is the negative half-space. In 3D "
"this is exactly the same, except that the plane is an infinite surface "
"(imagine an infinite, flat sheet of paper that you can orient and is pinned "
"to the origin) instead of a line."
msgstr ""

#: ../../docs/tutorials/math/vectors_advanced.rst:33
msgid "Distance to plane"
msgstr ""

#: ../../docs/tutorials/math/vectors_advanced.rst:35
msgid ""
"Now that it's clear what a plane is, let's go back to the dot product. The "
"dot product between a **unit vector** and any **point in space** (yes, this "
"time we do dot product between vector and position), returns the **distance "
"from the point to the plane**:"
msgstr ""

#: ../../docs/tutorials/math/vectors_advanced.rst:49
msgid ""
"But not just the absolute distance, if the point is in the negative half "
"space the distance will be negative, too:"
msgstr ""

#: ../../docs/tutorials/math/vectors_advanced.rst:54
msgid "This allows us to tell which side of the plane a point is."
msgstr ""

#: ../../docs/tutorials/math/vectors_advanced.rst:57
msgid "Away from the origin"
msgstr ""

#: ../../docs/tutorials/math/vectors_advanced.rst:59
msgid ""
"I know what you are thinking! So far this is nice, but *real* planes are "
"everywhere in space, not only passing through the origin. You want real "
"*plane* action and you want it *now*."
msgstr ""

#: ../../docs/tutorials/math/vectors_advanced.rst:63
msgid ""
"Remember that planes not only split space in two, but they also have "
"*polarity*. This means that it is possible to have perfectly overlapping "
"planes, but their negative and positive half-spaces are swapped."
msgstr ""

#: ../../docs/tutorials/math/vectors_advanced.rst:67
msgid ""
"With this in mind, let's describe a full plane as a **normal** *N* and a "
"**distance from the origin** scalar *D*. Thus, our plane is represented by N "
"and D. For example:"
msgstr ""

#: ../../docs/tutorials/math/vectors_advanced.rst:73
msgid ""
"For 3D math, Godot provides a :ref:`Plane <class_Plane>` built-in type that "
"handles this."
msgstr ""

#: ../../docs/tutorials/math/vectors_advanced.rst:76
msgid ""
"Basically, N and D can represent any plane in space, be it for 2D or 3D "
"(depending on the amount of dimensions of N) and the math is the same for "
"both. It's the same as before, but D is the distance from the origin to the "
"plane, travelling in N direction. As an example, imagine you want to reach a "
"point in the plane, you will just do:"
msgstr ""

#: ../../docs/tutorials/math/vectors_advanced.rst:91
msgid ""
"This will stretch (resize) the normal vector and make it touch the plane. "
"This math might seem confusing, but it's actually much simpler than it "
"seems. If we want to tell, again, the distance from the point to the plane, "
"we do the same but adjusting for distance:"
msgstr ""

#: ../../docs/tutorials/math/vectors_advanced.rst:105
msgid "The same thing, using a built-in function:"
msgstr ""

#: ../../docs/tutorials/math/vectors_advanced.rst:116
msgid "This will, again, return either a positive or negative distance."
msgstr ""

#: ../../docs/tutorials/math/vectors_advanced.rst:118
msgid ""
"Flipping the polarity of the plane can be done by negating both N and D. "
"This will result in a plane in the same position, but with inverted negative "
"and positive half spaces:"
msgstr ""

#: ../../docs/tutorials/math/vectors_advanced.rst:133
msgid ""
"Godot also implements this operator in :ref:`Plane <class_Plane>`. So, using "
"the format below will work as expected:"
msgstr ""

#: ../../docs/tutorials/math/vectors_advanced.rst:145
msgid ""
"So, remember, the plane's main practical use is that we can calculate the "
"distance to it. So, when is it useful to calculate the distance from a point "
"to a plane? Let's see some examples."
msgstr ""

#: ../../docs/tutorials/math/vectors_advanced.rst:150
msgid "Constructing a plane in 2D"
msgstr ""

#: ../../docs/tutorials/math/vectors_advanced.rst:152
msgid ""
"Planes clearly don't come out of nowhere, so they must be built. "
"Constructing them in 2D is easy, this can be done from either a normal (unit "
"vector) and a point, or from two points in space."
msgstr ""

#: ../../docs/tutorials/math/vectors_advanced.rst:156
msgid ""
"In the case of a normal and a point, most of the work is done, as the normal "
"is already computed, so calculate D from the dot product of the normal and "
"the point."
msgstr ""

#: ../../docs/tutorials/math/vectors_advanced.rst:171
msgid ""
"For two points in space, there are actually two planes that pass through "
"them, sharing the same space but with normal pointing to the opposite "
"directions. To compute the normal from the two points, the direction vector "
"must be obtained first, and then it needs to be rotated 90° degrees to "
"either side:"
msgstr ""

#: ../../docs/tutorials/math/vectors_advanced.rst:196
msgid ""
"The rest is the same as the previous example. Either point_a or point_b will "
"work, as they are in the same plane:"
msgstr ""

#: ../../docs/tutorials/math/vectors_advanced.rst:214
msgid ""
"Doing the same in 3D is a little more complex and is explained further down."
msgstr ""

#: ../../docs/tutorials/math/vectors_advanced.rst:218
msgid "Some examples of planes"
msgstr ""

#: ../../docs/tutorials/math/vectors_advanced.rst:220
msgid ""
"Here is an example of what planes are useful for. Imagine you have a `convex "
"<https://www.mathsisfun.com/definitions/convex.html>`__ polygon. For "
"example, a rectangle, a trapezoid, a triangle, or just any polygon where no "
"faces bend inwards."
msgstr ""

#: ../../docs/tutorials/math/vectors_advanced.rst:225
msgid ""
"For every segment of the polygon, we compute the plane that passes by that "
"segment. Once we have the list of planes, we can do neat things, for example "
"checking if a point is inside the polygon."
msgstr ""

#: ../../docs/tutorials/math/vectors_advanced.rst:229
msgid ""
"We go through all planes, if we can find a plane where the distance to the "
"point is positive, then the point is outside the polygon. If we can't, then "
"the point is inside."
msgstr ""

#: ../../docs/tutorials/math/vectors_advanced.rst:235
#: ../../docs/tutorials/math/vectors_advanced.rst:274
msgid "Code should be something like this:"
msgstr ""

#: ../../docs/tutorials/math/vectors_advanced.rst:260
msgid ""
"Pretty cool, huh? But this gets much better! With a little more effort, "
"similar logic will let us know when two convex polygons are overlapping too. "
"This is called the Separating Axis Theorem (or SAT) and most physics engines "
"use this to detect collision."
msgstr ""

#: ../../docs/tutorials/math/vectors_advanced.rst:265
msgid ""
"With a point, just checking if a plane returns a positive distance is enough "
"to tell if the point is outside. With another polygon, we must find a plane "
"where *all* *the* *other* *polygon* *points* return a positive distance to "
"it. This check is performed with the planes of A against the points of B, "
"and then with the planes of B against the points of A:"
msgstr ""

#: ../../docs/tutorials/math/vectors_advanced.rst:365
msgid ""
"As you can see, planes are quite useful, and this is the tip of the iceberg. "
"You might be wondering what happens with non convex polygons. This is "
"usually just handled by splitting the concave polygon into smaller convex "
"polygons, or using a technique such as BSP (which is not used much nowadays)."
msgstr ""

#: ../../docs/tutorials/math/vectors_advanced.rst:372
msgid "Collision detection in 3D"
msgstr ""

#: ../../docs/tutorials/math/vectors_advanced.rst:374
msgid ""
"This is another bonus bit, a reward for being patient and keeping up with "
"this long tutorial. Here is another piece of wisdom. This might not be "
"something with a direct use case (Godot already does collision detection "
"pretty well) but it's used by almost all physics engines and collision "
"detection libraries :)"
msgstr ""

#: ../../docs/tutorials/math/vectors_advanced.rst:380
msgid ""
"Remember that converting a convex shape in 2D to an array of 2D planes was "
"useful for collision detection? You could detect if a point was inside any "
"convex shape, or if two 2D convex shapes were overlapping."
msgstr ""

#: ../../docs/tutorials/math/vectors_advanced.rst:384
msgid ""
"Well, this works in 3D too, if two 3D polyhedral shapes are colliding, you "
"won't be able to find a separating plane. If a separating plane is found, "
"then the shapes are definitely not colliding."
msgstr ""

#: ../../docs/tutorials/math/vectors_advanced.rst:388
msgid ""
"To refresh a bit a separating plane means that all vertices of polygon A are "
"in one side of the plane, and all vertices of polygon B are in the other "
"side. This plane is always one of the face-planes of either polygon A or "
"polygon B."
msgstr ""

#: ../../docs/tutorials/math/vectors_advanced.rst:393
msgid ""
"In 3D though, there is a problem to this approach, because it is possible "
"that, in some cases a separating plane can't be found. This is an example of "
"such situation:"
msgstr ""

#: ../../docs/tutorials/math/vectors_advanced.rst:399
msgid ""
"To avoid it, some extra planes need to be tested as separators, these planes "
"are the cross product between the edges of polygon A and the edges of "
"polygon B"
msgstr ""

#: ../../docs/tutorials/math/vectors_advanced.rst:405
msgid "So the final algorithm is something like:"
msgstr ""

#: ../../docs/tutorials/math/vectors_advanced.rst:588
msgid ""
"For more information on using vector math in Godot, see the following "
"article:"
msgstr ""

#: ../../docs/tutorials/math/vectors_advanced.rst:592
msgid ""
"If you would like additional explanation, you should check out 3Blue1Brown's "
"excellent video series \"Essence of Linear Algebra\": https://www.youtube."
"com/watch?v=fNk_zzaMoSs&list=PLZHQObOWTQDPD3MizzM2xVFitgF8hE_ab"
msgstr ""

#: ../../docs/tutorials/math/matrices_and_transforms.rst:4
msgid "Matrices and transforms"
msgstr ""

#: ../../docs/tutorials/math/matrices_and_transforms.rst:9
msgid ""
"Before reading this tutorial, we recommend that you thoroughly read and "
"understand the :ref:`doc_vector_math` tutorial, as this tutorial requires a "
"knowledge of vectors."
msgstr ""

#: ../../docs/tutorials/math/matrices_and_transforms.rst:13
msgid ""
"This tutorial is about *transformations* and how we represent them in Godot "
"using matrices. It is not a full in-depth guide to matrices. Transformations "
"are most of the time applied as translation, rotation, and scale, so we will "
"focus on how to represent those with matrices."
msgstr ""

#: ../../docs/tutorials/math/matrices_and_transforms.rst:18
msgid ""
"Most of this guide focuses on 2D, using :ref:`class_Transform2D` and :ref:"
"`class_Vector2`, but the way things work in 3D is very similar."
msgstr ""

#: ../../docs/tutorials/math/matrices_and_transforms.rst:21
msgid ""
"As mentioned in the previous tutorial, it is important to remember that in "
"Godot, the Y axis points *down* in 2D. This is the opposite of how most "
"schools teach linear algebra, with the Y axis pointing up."
msgstr ""

#: ../../docs/tutorials/math/matrices_and_transforms.rst:26
msgid ""
"The convention is that the X axis is red, the Y axis is green, and the Z "
"axis is blue. This tutorial is color-coded to match these conventions, but "
"we will also represent the origin vector with a blue color."
msgstr ""

#: ../../docs/tutorials/math/matrices_and_transforms.rst:32
msgid "Matrix components and the Identity matrix"
msgstr ""

#: ../../docs/tutorials/math/matrices_and_transforms.rst:34
msgid ""
"The identity matrix represents a transform with no translation, no rotation, "
"and no scale. Let's start by looking at the identity matrix and how its "
"components relate to how it visually appears."
msgstr ""

#: ../../docs/tutorials/math/matrices_and_transforms.rst:40
msgid ""
"Matrices have rows and columns, and a transformation matrix has specific "
"conventions on what each does."
msgstr ""

#: ../../docs/tutorials/math/matrices_and_transforms.rst:43
msgid ""
"In the image above, we can see that the red X vector is represented by the "
"first column of the matrix, and the green Y vector is likewise represented "
"by the second column. A change to the columns will change these vectors. We "
"will see how they can be manipulated in the next few examples."
msgstr ""

#: ../../docs/tutorials/math/matrices_and_transforms.rst:49
msgid ""
"You should not worry about manipulating rows directly, as we usually work "
"with columns. However, you can think of the rows of the matrix as showing "
"which vectors contribute to moving in a given direction."
msgstr ""

#: ../../docs/tutorials/math/matrices_and_transforms.rst:53
msgid ""
"When we refer to a value such as ``t.x.y``, that's the Y component of the X "
"column vector. In other words, the bottom-left of the matrix. Similarly, ``t."
"x.x`` is top-left, ``t.y.x`` is top-right, and ``t.y.y`` is bottom-right, "
"where ``t`` is the Transform2D."
msgstr ""

#: ../../docs/tutorials/math/matrices_and_transforms.rst:59
msgid "Scaling the transformation matrix"
msgstr ""

#: ../../docs/tutorials/math/matrices_and_transforms.rst:61
msgid ""
"Applying a scale is one of the easiest operations to understand. Let's start "
"by placing the Godot logo underneath our vectors so that we can visually see "
"the effects on an object:"
msgstr ""

#: ../../docs/tutorials/math/matrices_and_transforms.rst:67
msgid ""
"Now, to scale the matrix, all we need to do is multiply each component by "
"the scale we want. Let's scale it up by 2. 1 times 2 becomes 2, and 0 times "
"2 becomes 0, so we end up with this:"
msgstr ""

#: ../../docs/tutorials/math/matrices_and_transforms.rst:73
msgid "To do this in code, we multiply each of the vectors:"
msgstr ""

#: ../../docs/tutorials/math/matrices_and_transforms.rst:92
msgid ""
"If we wanted to return it to its original scale, we can multiply each "
"component by 0.5. That's pretty much all there is to scaling a "
"transformation matrix."
msgstr ""

#: ../../docs/tutorials/math/matrices_and_transforms.rst:96
msgid ""
"To calculate the object's scale from an existing transformation matrix, you "
"can use ``length()`` on each of the column vectors."
msgstr ""

#: ../../docs/tutorials/math/matrices_and_transforms.rst:99
msgid ""
"In actual projects, you can use the ``scaled()`` method to perform scaling."
msgstr ""

#: ../../docs/tutorials/math/matrices_and_transforms.rst:103
#, fuzzy
msgid "Rotating the transformation matrix"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/math/matrices_and_transforms.rst:105
msgid ""
"We'll start the same way as earlier, with the Godot logo underneath the "
"identity matrix:"
msgstr ""

#: ../../docs/tutorials/math/matrices_and_transforms.rst:110
msgid ""
"As an example, let's say we want to rotate our Godot logo clockwise by 90 "
"degrees. Right now the X axis points right and the Y axis points down. If we "
"rotate these in our head, we would logically see that the new X axis should "
"point down and the new Y axis should point left."
msgstr ""

#: ../../docs/tutorials/math/matrices_and_transforms.rst:116
msgid ""
"You can imagine that you grab both the Godot logo and its vectors, and then "
"spin it around the center. Wherever you finish spinning, the orientation of "
"the vectors determines what the matrix is."
msgstr ""

#: ../../docs/tutorials/math/matrices_and_transforms.rst:120
msgid ""
"We need to represent \"down\" and \"left\" in normal coordinates, so means "
"we'll set X to (0, 1) and Y to (-1, 0). These are also the values of "
"``Vector2.DOWN`` and ``Vector2.LEFT``. When we do this, we get the desired "
"result of rotating the object:"
msgstr ""

#: ../../docs/tutorials/math/matrices_and_transforms.rst:127
msgid ""
"If you have trouble understanding the above, try this exercise: Cut a square "
"of paper, draw X and Y vectors on top of it, place it on graph paper, then "
"rotate it and note the endpoints."
msgstr ""

#: ../../docs/tutorials/math/matrices_and_transforms.rst:131
msgid ""
"To perform rotation in code, we need to be able to calculate the values "
"programmatically. This image shows the formulas needed to calculate the "
"transformation matrix from a rotation angle. Don't worry if this part seems "
"complicated, I promise it's the hardest thing you need to know."
msgstr ""

#: ../../docs/tutorials/math/matrices_and_transforms.rst:139
msgid ""
"Godot represents all rotations with radians, not degrees. A full turn is "
"`TAU` or `PI*2` radians, and a quarter turn of 90 degrees is `TAU/4` or "
"`PI/2` radians. Working with `TAU` usually results in more readable code."
msgstr ""

#: ../../docs/tutorials/math/matrices_and_transforms.rst:144
msgid ""
"Fun fact: In addition to Y being *down* in Godot, rotation is represented "
"clockwise. This means that all the math and trig functions behave the same "
"as a Y-is-up CCW system, since these differences \"cancel out\". You can "
"think of rotations in both systems being \"from X to Y\"."
msgstr ""

#: ../../docs/tutorials/math/matrices_and_transforms.rst:150
msgid ""
"In order to perform a rotation of 0.5 radians (about 28.65 degrees), we plug "
"in a value of 0.5 to the formula above and evaluate to find what the actual "
"values should be:"
msgstr ""

#: ../../docs/tutorials/math/matrices_and_transforms.rst:156
msgid "Here's how that would be done in code (place the script on a Node2D):"
msgstr ""

#: ../../docs/tutorials/math/matrices_and_transforms.rst:178
msgid ""
"To calculate the object's rotation from an existing transformation matrix, "
"you can use ``atan2(t.x.y, t.x.x)``, where t is the Transform2D."
msgstr ""

#: ../../docs/tutorials/math/matrices_and_transforms.rst:181
msgid ""
"In actual projects, you can use the ``rotated()`` method to perform "
"rotations."
msgstr ""

#: ../../docs/tutorials/math/matrices_and_transforms.rst:185
msgid "Basis of the transformation matrix"
msgstr ""

#: ../../docs/tutorials/math/matrices_and_transforms.rst:187
msgid ""
"So far we have only been working with the ``x`` and ``y``, vectors, which "
"are in charge of representing rotation, scale, and/or shearing (advanced, "
"covered at the end). The X and Y vectors are together called the *basis* of "
"the transformation matrix. The terms \"basis\" and \"basis vectors\" are "
"important to know."
msgstr ""

#: ../../docs/tutorials/math/matrices_and_transforms.rst:193
msgid ""
"You might have noticed that :ref:`class_Transform2D` actually has three :ref:"
"`class_Vector2` values: ``x``, ``y``, and ``origin``. The ``origin`` value "
"is not part of the basis, but it is part of the transform, and we need it to "
"represent position. From now on we'll keep track of the origin vector in all "
"examples. You can think of origin as another column, but it's often better "
"to think of it as completely separate."
msgstr ""

#: ../../docs/tutorials/math/matrices_and_transforms.rst:201
msgid ""
"Note that in 3D, Godot has a separate :ref:`class_Basis` structure for "
"holding the three :ref:`class_Vector3` values of the basis, since the code "
"can get complex and it makes sense to separate it from :ref:"
"`class_Transform3D` (which is composed of one :ref:`class_Basis` and one "
"extra :ref:`class_Vector3` for the origin)."
msgstr ""

#: ../../docs/tutorials/math/matrices_and_transforms.rst:208
msgid "Translating the transformation matrix"
msgstr ""

#: ../../docs/tutorials/math/matrices_and_transforms.rst:210
msgid ""
"Changing the ``origin`` vector is called *translating* the transformation "
"matrix. Translating is basically a technical term for \"moving\" the object, "
"but it explicitly does not involve any rotation."
msgstr ""

#: ../../docs/tutorials/math/matrices_and_transforms.rst:214
msgid ""
"Let's work through an example to help understand this. We will start with "
"the identity transform like last time, except we will keep track of the "
"origin vector this time."
msgstr ""

#: ../../docs/tutorials/math/matrices_and_transforms.rst:220
msgid ""
"If we want to move the object to a position of (1, 2), we need to set its "
"``origin`` vector to (1, 2):"
msgstr ""

#: ../../docs/tutorials/math/matrices_and_transforms.rst:225
msgid ""
"There is also a ``translated()`` method, which performs a different "
"operation to adding or changing ``origin`` directly. The ``translated()`` "
"method will translate the object *relative to its own rotation*. For "
"example, an object rotated 90 degrees clockwise will move to the right when "
"``translated()`` with ``Vector2.UP``."
msgstr ""

#: ../../docs/tutorials/math/matrices_and_transforms.rst:231
msgid ""
"Godot's 2D uses coordinates based on pixels, so in actual projects you will "
"want to translate by hundreds of units."
msgstr ""

#: ../../docs/tutorials/math/matrices_and_transforms.rst:235
msgid "Putting it all together"
msgstr ""

#: ../../docs/tutorials/math/matrices_and_transforms.rst:237
msgid ""
"We're going to apply everything we mentioned so far onto one transform. To "
"follow along, create a project with a Sprite2D node and use the Godot logo "
"for the texture resource."
msgstr ""

#: ../../docs/tutorials/math/matrices_and_transforms.rst:241
msgid ""
"Let's set the translation to (350, 150), rotate by -0.5 rad, and scale by 3. "
"I've posted a screenshot, and the code to reproduce it, but I encourage you "
"to try and reproduce the screenshot without looking at the code!"
msgstr ""

#: ../../docs/tutorials/math/matrices_and_transforms.rst:280
msgid "Shearing the transformation matrix (advanced)"
msgstr ""

#: ../../docs/tutorials/math/matrices_and_transforms.rst:282
msgid ""
"If you are only looking for how to *use* transformation matrices, feel free "
"to skip this section of the tutorial. This section explores an uncommonly "
"used aspect of transformation matrices for the purpose of building an "
"understanding of them."
msgstr ""

#: ../../docs/tutorials/math/matrices_and_transforms.rst:287
msgid "Node2D provides a shearing property out of the box."
msgstr ""

#: ../../docs/tutorials/math/matrices_and_transforms.rst:289
msgid ""
"You may have noticed that a transform has more degrees of freedom than the "
"combination of the above actions. The basis of a 2D transformation matrix "
"has four total numbers in two :ref:`class_Vector2` values, while a rotation "
"value and a Vector2 for scale only has 3 numbers. The high-level concept for "
"the missing degree of freedom is called *shearing*."
msgstr ""

#: ../../docs/tutorials/math/matrices_and_transforms.rst:295
msgid ""
"Normally, you will always have the basis vectors perpendicular to each "
"other. However, shearing can be useful in some situations, and understanding "
"shearing helps you understand how transforms work."
msgstr ""

#: ../../docs/tutorials/math/matrices_and_transforms.rst:299
msgid ""
"To show you visually how it will look, let's overlay a grid onto the Godot "
"logo:"
msgstr ""

#: ../../docs/tutorials/math/matrices_and_transforms.rst:304
msgid ""
"Each point on this grid is obtained by adding the basis vectors together. "
"The bottom-right corner is X + Y, while the top-right corner is X - Y. If we "
"change the basis vectors, the entire grid moves with it, as the grid is "
"composed of the basis vectors. All lines on the grid that are currently "
"parallel will remain parallel no matter what changes we make to the basis "
"vectors."
msgstr ""

#: ../../docs/tutorials/math/matrices_and_transforms.rst:311
msgid "As an example, let's set Y to (1, 1):"
msgstr ""

#: ../../docs/tutorials/math/matrices_and_transforms.rst:330
msgid ""
"You can't set the raw values of a Transform2D in the editor, so you *must* "
"use code if you want to shear the object."
msgstr ""

#: ../../docs/tutorials/math/matrices_and_transforms.rst:333
msgid ""
"Due to the vectors no longer being perpendicular, the object has been "
"sheared. The bottom-center of the grid, which is (0, 1) relative to itself, "
"is now located at a world position of (1, 1)."
msgstr ""

#: ../../docs/tutorials/math/matrices_and_transforms.rst:337
msgid ""
"The intra-object coordinates are called UV coordinates in textures, so let's "
"borrow that terminology for here. To find the world position from a relative "
"position, the formula is U * X + V * Y, where U and V are numbers and X and "
"Y are the basis vectors."
msgstr ""

#: ../../docs/tutorials/math/matrices_and_transforms.rst:342
msgid ""
"The bottom-right corner of the grid, which is always at the UV position of "
"(1, 1), is at the world position of (2, 1), which is calculated from X*1 + "
"Y*1, which is (1, 0) + (1, 1), or (1 + 1, 0 + 1), or (2, 1). This matches up "
"with our observation of where the bottom-right corner of the image is."
msgstr ""

#: ../../docs/tutorials/math/matrices_and_transforms.rst:348
msgid ""
"Similarly, the top-right corner of the grid, which is always at the UV "
"position of (1, -1), is at the world position of (0, -1), which is "
"calculated from X*1 + Y*-1, which is (1, 0) - (1, 1), or (1 - 1, 0 - 1), or "
"(0, -1). This matches up with our observation of where the top-right corner "
"of the image is."
msgstr ""

#: ../../docs/tutorials/math/matrices_and_transforms.rst:354
msgid ""
"Hopefully you now fully understand the how a transformation matrix affects "
"the object, and the relationship between the basis vectors and how the "
"object's \"UV\" or \"intra-coordinates\" have their world position changed."
msgstr ""

#: ../../docs/tutorials/math/matrices_and_transforms.rst:358
msgid ""
"In Godot, all transform math is done relative to the parent node. When we "
"refer to \"world position\", that would be relative to the node's parent "
"instead, if the node had a parent."
msgstr ""

#: ../../docs/tutorials/math/matrices_and_transforms.rst:362
msgid ""
"If you would like additional explanation, you should check out 3Blue1Brown's "
"excellent video about linear transformations: https://www.youtube.com/watch?"
"v=kYB8IZa5AuE"
msgstr ""

#: ../../docs/tutorials/math/matrices_and_transforms.rst:367
msgid "Practical applications of transforms"
msgstr ""

#: ../../docs/tutorials/math/matrices_and_transforms.rst:369
msgid ""
"In actual projects, you will usually be working with transforms inside "
"transforms by having multiple :ref:`class_Node2D` or :ref:`class_Node3D` "
"nodes parented to each other."
msgstr ""

#: ../../docs/tutorials/math/matrices_and_transforms.rst:373
msgid ""
"However, it's useful to understand how to manually calculate the values we "
"need. We will go over how you could use :ref:`class_Transform2D` or :ref:"
"`class_Transform3D` to manually calculate transforms of nodes."
msgstr ""

#: ../../docs/tutorials/math/matrices_and_transforms.rst:378
msgid "Converting positions between transforms"
msgstr ""

#: ../../docs/tutorials/math/matrices_and_transforms.rst:380
msgid ""
"There are many cases where you'd want to convert a position in and out of a "
"transform. For example, if you have a position relative to the player and "
"would like to find the world (parent-relative) position, or if you have a "
"world position and want to know where it is relative to the player."
msgstr ""

#: ../../docs/tutorials/math/matrices_and_transforms.rst:385
msgid ""
"We can find what a vector relative to the player would be defined in world "
"space as using the ``*`` operator:"
msgstr ""

#: ../../docs/tutorials/math/matrices_and_transforms.rst:399
msgid ""
"And we can use the ``*`` operator in the opposite order to find a what world "
"space position would be if it was defined relative to the player:"
msgstr ""

#: ../../docs/tutorials/math/matrices_and_transforms.rst:413
msgid ""
"If you know in advance that the transform is positioned at (0, 0), you can "
"use the \"basis_xform\" or \"basis_xform_inv\" methods instead, which skip "
"dealing with translation."
msgstr ""

#: ../../docs/tutorials/math/matrices_and_transforms.rst:418
msgid "Moving an object relative to itself"
msgstr ""

#: ../../docs/tutorials/math/matrices_and_transforms.rst:420
msgid ""
"A common operation, especially in 3D games, is to move an object relative to "
"itself. For example, in first-person shooter games, you would want the "
"character to move forward (-Z axis) when you press :kbd:`W`."
msgstr ""

#: ../../docs/tutorials/math/matrices_and_transforms.rst:424
msgid ""
"Since the basis vectors are the orientation relative to the parent, and the "
"origin vector is the position relative to the parent, we can add multiples "
"of the basis vectors to move an object relative to itself."
msgstr ""

#: ../../docs/tutorials/math/matrices_and_transforms.rst:428
msgid "This code moves an object 100 units to its own right:"
msgstr ""

#: ../../docs/tutorials/math/matrices_and_transforms.rst:441
msgid "For moving in 3D, you would need to replace \"x\" with \"basis.x\"."
msgstr ""

#: ../../docs/tutorials/math/matrices_and_transforms.rst:443
msgid ""
"In actual projects, you can use ``translate_object_local`` in 3D or "
"``move_local_x`` and ``move_local_y`` in 2D to do this."
msgstr ""

#: ../../docs/tutorials/math/matrices_and_transforms.rst:447
msgid "Applying transforms onto transforms"
msgstr ""

#: ../../docs/tutorials/math/matrices_and_transforms.rst:449
msgid ""
"One of the most important things to know about transforms is how you can use "
"several of them together. A parent node's transform affects all of its "
"children. Let's dissect an example."
msgstr ""

#: ../../docs/tutorials/math/matrices_and_transforms.rst:453
msgid ""
"In this image, the child node has a \"2\" after the component names to "
"distinguish them from the parent node. It might look a bit overwhelming with "
"so many numbers, but remember that each number is displayed twice (next to "
"the arrows and also in the matrices), and that almost half of the numbers "
"are zero."
msgstr ""

#: ../../docs/tutorials/math/matrices_and_transforms.rst:461
msgid ""
"The only transformations going on here are that the parent node has been "
"given a scale of (2, 1), the child has been given a scale of (0.5, 0.5), and "
"both nodes have been given positions."
msgstr ""

#: ../../docs/tutorials/math/matrices_and_transforms.rst:465
msgid ""
"All child transformations are affected by the parent transformations. The "
"child has a scale of (0.5, 0.5), so you would expect it to be a 1:1 ratio "
"square, and it is, but only relative to the parent. The child's X vector "
"ends up being (1, 0) in world space, because it is scaled by the parent's "
"basis vectors. Similarly, the child node's ``origin`` vector is set to (1, "
"1), but this actually moves it (2, 1) in world space, due to the parent "
"node's basis vectors."
msgstr ""

#: ../../docs/tutorials/math/matrices_and_transforms.rst:474
msgid ""
"To calculate a child transform's world space transform manually, this is the "
"code we would use:"
msgstr ""

#: ../../docs/tutorials/math/matrices_and_transforms.rst:512
msgid ""
"In actual projects, we can find the world transform of the child by applying "
"one transform onto another using the ``*`` operator:"
msgstr ""

#: ../../docs/tutorials/math/matrices_and_transforms.rst:534
msgid "When multiplying matrices, order matters! Don't mix them up."
msgstr ""

#: ../../docs/tutorials/math/matrices_and_transforms.rst:536
msgid "Lastly, applying the identity transform will always do nothing."
msgstr ""

#: ../../docs/tutorials/math/matrices_and_transforms.rst:538
msgid ""
"If you would like additional explanation, you should check out 3Blue1Brown's "
"excellent video about matrix composition: https://www.youtube.com/watch?"
"v=XkY2DOUCWMU"
msgstr ""

#: ../../docs/tutorials/math/matrices_and_transforms.rst:543
msgid "Inverting a transformation matrix"
msgstr ""

#: ../../docs/tutorials/math/matrices_and_transforms.rst:545
msgid ""
"The \"affine_inverse\" function returns a transform that \"undoes\" the "
"previous transform. This can be useful in some situations. Let's take a look "
"at a few examples."
msgstr ""

#: ../../docs/tutorials/math/matrices_and_transforms.rst:549
msgid ""
"Multiplying an inverse transform by the normal transform undoes all "
"transformations:"
msgstr ""

#: ../../docs/tutorials/math/matrices_and_transforms.rst:565
msgid ""
"Transforming a position by a transform and its inverse results in the same "
"position:"
msgstr ""

#: ../../docs/tutorials/math/matrices_and_transforms.rst:584
msgid "How does it all work in 3D?"
msgstr ""

#: ../../docs/tutorials/math/matrices_and_transforms.rst:586
msgid ""
"One of the great things about transformation matrices is that they work very "
"similarly between 2D and 3D transformations. All the code and formulas used "
"above for 2D work the same in 3D, with 3 exceptions: the addition of a third "
"axis, that each axis is of type :ref:`class_Vector3`, and also that Godot "
"stores the :ref:`class_Basis` separately from the :ref:`class_Transform3D`, "
"since the math can get complex and it makes sense to separate it."
msgstr ""

#: ../../docs/tutorials/math/matrices_and_transforms.rst:594
msgid ""
"All of the concepts for how translation, rotation, scale, and shearing work "
"in 3D are all the same compared to 2D. To scale, we take each component and "
"multiply it; to rotate, we change where each basis vector is pointing; to "
"translate, we manipulate the origin; and to shear, we change the basis "
"vectors to be non-perpendicular."
msgstr ""

#: ../../docs/tutorials/math/matrices_and_transforms.rst:602
msgid ""
"If you would like, it's a good idea to play around with transforms to get an "
"understanding of how they work. Godot allows you to edit 3D transform "
"matrices directly from the inspector. You can download this project which "
"has colored lines and cubes to help visualize the :ref:`class_Basis` vectors "
"and the origin in both 2D and 3D: https://github.com/godotengine/godot-demo-"
"projects/tree/master/misc/matrix_transform"
msgstr ""

#: ../../docs/tutorials/math/matrices_and_transforms.rst:609
msgid ""
"You cannot edit Node2D's transform matrix directly in Godot 4.0's inspector. "
"This may be changed in a future release of Godot."
msgstr ""

#: ../../docs/tutorials/math/matrices_and_transforms.rst:612
msgid ""
"If you would like additional explanation, you should check out 3Blue1Brown's "
"excellent video about 3D linear transformations: https://www.youtube.com/"
"watch?v=rHLEWRxRGiM"
msgstr ""

#: ../../docs/tutorials/math/matrices_and_transforms.rst:617
msgid "Representing rotation in 3D (advanced)"
msgstr ""

#: ../../docs/tutorials/math/matrices_and_transforms.rst:619
msgid ""
"The biggest difference between 2D and 3D transformation matrices is how you "
"represent rotation by itself without the basis vectors."
msgstr ""

#: ../../docs/tutorials/math/matrices_and_transforms.rst:622
msgid ""
"With 2D, we have an easy way (atan2) to switch between a transformation "
"matrix and an angle. In 3D, rotation is too complex to represent as one "
"number. There is something called Euler angles, which can represent "
"rotations as a set of 3 numbers, however, they are limited and not very "
"useful, except for trivial cases."
msgstr ""

#: ../../docs/tutorials/math/matrices_and_transforms.rst:628
msgid ""
"In 3D we do not typically use angles, we either use a transformation basis "
"(used pretty much everywhere in Godot), or we use quaternions. Godot can "
"represent quaternions using the :ref:`class_Quaternion` struct. My "
"suggestion to you is to completely ignore how they work under-the-hood, "
"because they are very complicated and unintuitive."
msgstr ""

#: ../../docs/tutorials/math/matrices_and_transforms.rst:634
msgid ""
"However, if you really must know how it works, here are some great "
"resources, which you can follow in order:"
msgstr ""

#: ../../docs/tutorials/math/matrices_and_transforms.rst:637
msgid "https://www.youtube.com/watch?v=mvmuCPvRoWQ"
msgstr ""

#: ../../docs/tutorials/math/matrices_and_transforms.rst:639
msgid "https://www.youtube.com/watch?v=d4EgbgTm0Bg"
msgstr ""

#: ../../docs/tutorials/math/matrices_and_transforms.rst:641
msgid "https://eater.net/quaternions"
msgstr ""

#: ../../docs/tutorials/math/interpolation.rst:6
msgid ""
"Interpolation is a very basic operation in graphics programming. It's good "
"to become familiar with it in order to expand your horizons as a graphics "
"developer."
msgstr ""

#: ../../docs/tutorials/math/interpolation.rst:8
msgid ""
"The basic idea is that you want to transition from A to B. A value ``t``, "
"represents the states in-between."
msgstr ""

#: ../../docs/tutorials/math/interpolation.rst:10
msgid ""
"For example, if ``t`` is 0, then the state is A. If ``t`` is 1, then the "
"state is B. Anything in-between is an *interpolation*."
msgstr ""

#: ../../docs/tutorials/math/interpolation.rst:12
msgid ""
"Between two real (floating-point) numbers, an interpolation can be described "
"as:"
msgstr ""

#: ../../docs/tutorials/math/interpolation.rst:18
msgid "And often simplified to:"
msgstr ""

#: ../../docs/tutorials/math/interpolation.rst:24
msgid ""
"The name of this type of interpolation, which transforms a value into "
"another at *constant speed* is *\"linear\"*. So, when you hear about *Linear "
"Interpolation*, you know they are referring to this formula."
msgstr ""

#: ../../docs/tutorials/math/interpolation.rst:26
msgid ""
"There are other types of interpolations, which will not be covered here. A "
"recommended read afterwards is the :ref:`Bezier <doc_beziers_and_curves>` "
"page."
msgstr ""

#: ../../docs/tutorials/math/interpolation.rst:29
msgid "Vector interpolation"
msgstr ""

#: ../../docs/tutorials/math/interpolation.rst:31
msgid ""
"Vector types (:ref:`Vector2 <class_Vector2>` and :ref:`Vector3 "
"<class_Vector3>`) can also be interpolated, they come with handy functions "
"to do it :ref:`Vector2.lerp() <class_Vector2_method_lerp>` and :ref:`Vector3."
"lerp() <class_Vector3_method_lerp>`."
msgstr ""

#: ../../docs/tutorials/math/interpolation.rst:34
msgid ""
"For cubic interpolation, there are also :ref:`Vector2.cubic_interpolate() "
"<class_Vector2_method_cubic_interpolate>` and :ref:`Vector3."
"cubic_interpolate() <class_Vector3_method_cubic_interpolate>`, which do a :"
"ref:`Bezier <doc_beziers_and_curves>` style interpolation."
msgstr ""

#: ../../docs/tutorials/math/interpolation.rst:36
msgid ""
"Here is example pseudo-code for going from point A to B using interpolation:"
msgstr ""

#: ../../docs/tutorials/math/interpolation.rst:63
msgid "It will produce the following motion:"
msgstr ""

#: ../../docs/tutorials/math/interpolation.rst:68
msgid "Transform interpolation"
msgstr ""

#: ../../docs/tutorials/math/interpolation.rst:70
msgid ""
"It is also possible to interpolate whole transforms (make sure they have "
"either uniform scale or, at least, the same non-uniform scale). For this, "
"the function :ref:`Transform3D.interpolate_with() "
"<class_Transform3D_method_interpolate_with>` can be used."
msgstr ""

#: ../../docs/tutorials/math/interpolation.rst:73
msgid ""
"Here is an example of transforming a monkey from Position1 to Position2:"
msgstr ""

#: ../../docs/tutorials/math/interpolation.rst:77
msgid "Using the following pseudocode:"
msgstr ""

#: ../../docs/tutorials/math/interpolation.rst:104
msgid "And again, it will produce the following motion:"
msgstr ""

#: ../../docs/tutorials/math/interpolation.rst:110
msgid "Smoothing motion"
msgstr ""

#: ../../docs/tutorials/math/interpolation.rst:112
msgid ""
"Interpolation can be used to smooth movement, rotation, etc. Here is an "
"example of a circle following the mouse using smoothed motion:"
msgstr ""

#: ../../docs/tutorials/math/interpolation.rst:137
msgid "Here is how it looks:"
msgstr ""

#: ../../docs/tutorials/math/interpolation.rst:141
msgid ""
"This useful for smoothing camera movement, allies following you (ensuring "
"they stay within a certain range), and many other common game patterns."
msgstr ""

#: ../../docs/tutorials/math/beziers_and_curves.rst:4
msgid "Beziers, curves and paths"
msgstr ""

#: ../../docs/tutorials/math/beziers_and_curves.rst:6
msgid ""
"Bezier curves are a mathematical approximation of natural geometric shapes. "
"We use them to represent a curve with as little information as possible and "
"with a high level of flexibility."
msgstr ""

#: ../../docs/tutorials/math/beziers_and_curves.rst:10
msgid ""
"Unlike more abstract mathematical concepts, Bezier curves were created for "
"industrial design. They are a popular tool in the graphics software industry."
msgstr ""

#: ../../docs/tutorials/math/beziers_and_curves.rst:13
msgid ""
"They rely on :ref:`interpolation<doc_interpolation>`, which we saw in the "
"previous article, combining multiple steps to create smooth curves. To "
"better understand how Bezier curves work, let's start from its simplest "
"form: Quadratic Bezier."
msgstr ""

#: ../../docs/tutorials/math/beziers_and_curves.rst:19
msgid "Quadratic Bezier"
msgstr ""

#: ../../docs/tutorials/math/beziers_and_curves.rst:21
msgid "Take three points, the minimum required for Quadratic Bezier to work:"
msgstr ""

#: ../../docs/tutorials/math/beziers_and_curves.rst:25
msgid ""
"To draw a curve between them, we first interpolate gradually over the two "
"vertices of each of the two segments formed by the three points, using "
"values ranging from 0 to 1. This gives us two points that move along the "
"segments as we change the value of ``t`` from 0 to 1."
msgstr ""

#: ../../docs/tutorials/math/beziers_and_curves.rst:45
msgid ""
"We then interpolate ``q0`` and ``q1`` to obtain a single point ``r`` that "
"moves along a curve."
msgstr ""

#: ../../docs/tutorials/math/beziers_and_curves.rst:59
msgid "This type of curve is called a *Quadratic Bezier* curve."
msgstr ""

#: ../../docs/tutorials/math/beziers_and_curves.rst:63
#: ../../docs/tutorials/math/beziers_and_curves.rst:165
msgid "*(Image credit: Wikipedia)*"
msgstr ""

#: ../../docs/tutorials/math/beziers_and_curves.rst:66
msgid "Cubic Bezier"
msgstr ""

#: ../../docs/tutorials/math/beziers_and_curves.rst:68
msgid ""
"Building upon the previous example, we can get more control by interpolating "
"between four points."
msgstr ""

#: ../../docs/tutorials/math/beziers_and_curves.rst:73
msgid ""
"We first use a function with four parameters to take four points as an "
"input, ``p0``, ``p1``, ``p2`` and ``p3``:"
msgstr ""

#: ../../docs/tutorials/math/beziers_and_curves.rst:88
msgid ""
"We apply a linear interpolation to each couple of points to reduce them to "
"three:"
msgstr ""

#: ../../docs/tutorials/math/beziers_and_curves.rst:104
msgid "We then take our three points and reduce them to two:"
msgstr ""

#: ../../docs/tutorials/math/beziers_and_curves.rst:117
msgid "And to one:"
msgstr ""

#: ../../docs/tutorials/math/beziers_and_curves.rst:130
msgid "Here is the full function:"
msgstr ""

#: ../../docs/tutorials/math/beziers_and_curves.rst:161
msgid ""
"The result will be a smooth curve interpolating between all four points:"
msgstr ""

#: ../../docs/tutorials/math/beziers_and_curves.rst:167
msgid ""
"Cubic Bezier interpolation works the same in 3D, just use ``Vector3`` "
"instead of ``Vector2``."
msgstr ""

#: ../../docs/tutorials/math/beziers_and_curves.rst:171
msgid "Adding control points"
msgstr ""

#: ../../docs/tutorials/math/beziers_and_curves.rst:173
msgid ""
"Building upon Cubic Bezier, we can change the way two of the points work to "
"control the shape of our curve freely. Instead of having ``p0``, ``p1``, "
"``p2`` and ``p3``, we will store them as:"
msgstr ""

#: ../../docs/tutorials/math/beziers_and_curves.rst:177
msgid "``point0 = p0``: Is the first point, the source"
msgstr ""

#: ../../docs/tutorials/math/beziers_and_curves.rst:178
msgid "``control0 = p1 - p0``: Is a vector relative to the first control point"
msgstr ""

#: ../../docs/tutorials/math/beziers_and_curves.rst:179
msgid ""
"``control1 = p3 - p2``: Is a vector relative to the second control point"
msgstr ""

#: ../../docs/tutorials/math/beziers_and_curves.rst:180
msgid "``point1 = p3``: Is the second point, the destination"
msgstr ""

#: ../../docs/tutorials/math/beziers_and_curves.rst:182
msgid ""
"This way, we have two points and two control points which are relative "
"vectors to the respective points. If you've used graphics or animation "
"software before, this might look familiar:"
msgstr ""

#: ../../docs/tutorials/math/beziers_and_curves.rst:188
msgid ""
"This is how graphics software presents Bezier curves to the users, and how "
"they work and look in Godot."
msgstr ""

#: ../../docs/tutorials/math/beziers_and_curves.rst:192
msgid "Curve2D, Curve3D, Path and Path2D"
msgstr ""

#: ../../docs/tutorials/math/beziers_and_curves.rst:194
msgid ""
"There are two objects that contain curves: :ref:`Curve3D <class_Curve3D>` "
"and :ref:`Curve2D <class_Curve2D>` (for 3D and 2D respectively)."
msgstr ""

#: ../../docs/tutorials/math/beziers_and_curves.rst:196
msgid ""
"They can contain several points, allowing for longer paths. It is also "
"possible to set them to nodes: :ref:`Path3D <class_Path3D>` and :ref:`Path2D "
"<class_Path2D>` (also for 3D and 2D respectively):"
msgstr ""

#: ../../docs/tutorials/math/beziers_and_curves.rst:200
msgid ""
"Using them, however, may not be completely obvious, so following is a "
"description of the most common use cases for Bezier curves."
msgstr ""

#: ../../docs/tutorials/math/beziers_and_curves.rst:203
msgid "Evaluating"
msgstr ""

#: ../../docs/tutorials/math/beziers_and_curves.rst:205
msgid ""
"Only evaluating them may be an option, but in most cases it's not very "
"useful. The big drawback with Bezier curves is that if you traverse them at "
"constant speed, from ``t = 0`` to ``t = 1``, the actual interpolation will "
"*not* move at constant speed. The speed is also an interpolation between the "
"distances between points ``p0``, ``p1``, ``p2`` and ``p3`` and there is not "
"a mathematically simple way to traverse the curve at constant speed."
msgstr ""

#: ../../docs/tutorials/math/beziers_and_curves.rst:207
#, fuzzy
msgid "Let's do an example with the following pseudocode:"
msgstr "Glavna dokumentacija za sajt je podeljena na sledeća poglavlja:"

#: ../../docs/tutorials/math/beziers_and_curves.rst:230
msgid ""
"As you can see, the speed (in pixels per second) of the circle varies, even "
"though ``t`` is increased at constant speed. This makes beziers difficult to "
"use for anything practical out of the box."
msgstr ""

#: ../../docs/tutorials/math/beziers_and_curves.rst:235
msgid ""
"Drawing beziers (or objects based on the curve) is a very common use case, "
"but it's also not easy. For pretty much any case, Bezier curves need to be "
"converted to some sort of segments. This is normally difficult, however, "
"without creating a very high amount of them."
msgstr ""

#: ../../docs/tutorials/math/beziers_and_curves.rst:237
msgid ""
"The reason is that some sections of a curve (specifically, corners) may "
"require considerable amounts of points, while other sections may not:"
msgstr ""

#: ../../docs/tutorials/math/beziers_and_curves.rst:241
msgid ""
"Additionally, if both control points were ``0, 0`` (remember they are "
"relative vectors), the Bezier curve would just be a straight line (so "
"drawing a high amount of points would be wasteful)."
msgstr ""

#: ../../docs/tutorials/math/beziers_and_curves.rst:243
msgid ""
"Before drawing Bezier curves, *tessellation* is required. This is often done "
"with a recursive or divide and conquer function that splits the curve until "
"the curvature amount becomes less than a certain threshold."
msgstr ""

#: ../../docs/tutorials/math/beziers_and_curves.rst:245
msgid ""
"The *Curve* classes provide this via the :ref:`Curve2D.tessellate() "
"<class_Curve2D_method_tessellate>` function (which receives optional "
"``stages`` of recursion and angle ``tolerance`` arguments). This way, "
"drawing something based on a curve is easier."
msgstr ""

#: ../../docs/tutorials/math/beziers_and_curves.rst:249
msgid "Traversal"
msgstr ""

#: ../../docs/tutorials/math/beziers_and_curves.rst:251
msgid ""
"The last common use case for the curves is to traverse them. Because of what "
"was mentioned before regarding constant speed, this is also difficult."
msgstr ""

#: ../../docs/tutorials/math/beziers_and_curves.rst:253
msgid ""
"To make this easier, the curves need to be *baked* into equidistant points. "
"This way, they can be approximated with regular interpolation (which can be "
"improved further with a cubic option). To do this, just use the :ref:"
"`Curve3D.sample_baked()<class_Curve3D_method_sample_baked>` method together "
"with :ref:`Curve2D."
"get_baked_length()<class_Curve2D_method_get_baked_length>`. The first call "
"to either of them will bake the curve internally."
msgstr ""

#: ../../docs/tutorials/math/beziers_and_curves.rst:256
msgid ""
"Traversal at constant speed, then, can be done with the following pseudo-"
"code:"
msgstr ""

#: ../../docs/tutorials/math/beziers_and_curves.rst:277
msgid "And the output will, then, move at constant speed:"
msgstr ""

#: ../../docs/tutorials/math/random_number_generation.rst:4
msgid "Random number generation"
msgstr ""

#: ../../docs/tutorials/math/random_number_generation.rst:6
msgid ""
"Many games rely on randomness to implement core game mechanics. This page "
"guides you through common types of randomness and how to implement them in "
"Godot."
msgstr ""

#: ../../docs/tutorials/math/random_number_generation.rst:10
msgid ""
"After giving you a brief overview of useful functions that generate random "
"numbers, you will learn how to get random elements from arrays, "
"dictionaries, and how to use a noise generator in GDScript. Lastly, we'll "
"take a look at cryptographically secure random number generation and how it "
"differs from typical random number generation."
msgstr ""

#: ../../docs/tutorials/math/random_number_generation.rst:18
msgid ""
"Computers cannot generate \"true\" random numbers. Instead, they rely on "
"`pseudorandom number generators <https://en.wikipedia.org/wiki/"
"Pseudorandom_number_generator>`__ (PRNGs)."
msgstr ""

#: ../../docs/tutorials/math/random_number_generation.rst:22
msgid ""
"Godot internally uses the `PCG Family <https://www.pcg-random.org/>`__ of "
"pseudorandom number generators."
msgstr ""

#: ../../docs/tutorials/math/random_number_generation.rst:26
msgid "Global scope versus RandomNumberGenerator class"
msgstr ""

#: ../../docs/tutorials/math/random_number_generation.rst:28
msgid ""
"Godot exposes two ways to generate random numbers: via *global scope* "
"methods or using the :ref:`class_RandomNumberGenerator` class."
msgstr ""

#: ../../docs/tutorials/math/random_number_generation.rst:31
msgid ""
"Global scope methods are easier to set up, but they don't offer as much "
"control."
msgstr ""

#: ../../docs/tutorials/math/random_number_generation.rst:33
msgid ""
"RandomNumberGenerator requires more code to use, but allows creating "
"multiple instances, each with their own seed and state."
msgstr ""

#: ../../docs/tutorials/math/random_number_generation.rst:36
msgid ""
"This tutorial uses global scope methods, except when the method only exists "
"in the RandomNumberGenerator class."
msgstr ""

#: ../../docs/tutorials/math/random_number_generation.rst:40
msgid "The randomize() method"
msgstr ""

#: ../../docs/tutorials/math/random_number_generation.rst:44
msgid ""
"Since Godot 4.0, the random seed is automatically set to a random value when "
"the project starts. This means you don't need to call ``randomize()`` in "
"``_ready()`` anymore to ensure that results are random across project runs. "
"However, you can still use ``randomize()`` if you want to use a specific "
"seed number, or generate it using a different method."
msgstr ""

#: ../../docs/tutorials/math/random_number_generation.rst:50
msgid ""
"In global scope, you can find a :ref:`randomize() "
"<class_@GlobalScope_method_randomize>` method. **This method should be "
"called only once when your project starts to initialize the random seed.** "
"Calling it multiple times is unnecessary and may impact performance "
"negatively."
msgstr ""

#: ../../docs/tutorials/math/random_number_generation.rst:55
msgid ""
"Putting it in your main scene script's ``_ready()`` method is a good choice:"
msgstr ""

#: ../../docs/tutorials/math/random_number_generation.rst:70
msgid ""
"You can also set a fixed random seed instead using :ref:`seed() "
"<class_@GlobalScope_method_seed>`. Doing so will give you *deterministic* "
"results across runs:"
msgstr ""

#: ../../docs/tutorials/math/random_number_generation.rst:90
msgid ""
"When using the RandomNumberGenerator class, you should call ``randomize()`` "
"on the instance since it has its own seed:"
msgstr ""

#: ../../docs/tutorials/math/random_number_generation.rst:105
#, fuzzy
msgid "Getting a random number"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/math/random_number_generation.rst:107
msgid ""
"Let's look at some of the most commonly used functions and methods to "
"generate random numbers in Godot."
msgstr ""

#: ../../docs/tutorials/math/random_number_generation.rst:110
msgid ""
"The function :ref:`randi() <class_@GlobalScope_method_randi>` returns a "
"random number between 0 and 2^32-1. Since the maximum value is huge, you "
"most likely want to use the modulo operator (``%``) to bound the result "
"between 0 and the denominator:"
msgstr ""

#: ../../docs/tutorials/math/random_number_generation.rst:132
msgid ""
":ref:`randf() <class_@GlobalScope_method_randf>` returns a random floating-"
"point number between 0 and 1. This is useful to implement a :ref:"
"`doc_random_number_generation_weighted_random_probability` system, among "
"other things."
msgstr ""

#: ../../docs/tutorials/math/random_number_generation.rst:137
msgid ""
":ref:`randfn() <class_RandomNumberGenerator_method_randfn>` returns a random "
"floating-point number following a `normal distribution <https://en.wikipedia."
"org/wiki/Normal_distribution>`__. This means the returned value is more "
"likely to be around the mean (0.0 by default), varying by the deviation (1.0 "
"by default):"
msgstr ""

#: ../../docs/tutorials/math/random_number_generation.rst:158
msgid ""
":ref:`randf_range() <class_@GlobalScope_method_randf_range>` takes two "
"arguments ``from`` and ``to``, and returns a random floating-point number "
"between ``from`` and ``to``:"
msgstr ""

#: ../../docs/tutorials/math/random_number_generation.rst:168
msgid ""
":ref:`RandomNumberGenerator.randi_range() "
"<class_RandomNumberGenerator_method_randi_range>` takes two arguments "
"``from`` and ``to``, and returns a random integer between ``from`` and "
"``to``:"
msgstr ""

#: ../../docs/tutorials/math/random_number_generation.rst:187
msgid "Get a random array element"
msgstr ""

#: ../../docs/tutorials/math/random_number_generation.rst:189
msgid ""
"We can use random integer generation to get a random element from an array:"
msgstr ""

#: ../../docs/tutorials/math/random_number_generation.rst:233
msgid ""
"To prevent the same fruit from being picked more than once in a row, we can "
"add more logic to this method:"
msgstr ""

#: ../../docs/tutorials/math/random_number_generation.rst:298
msgid ""
"This approach can be useful to make random number generation feel less "
"repetitive. Still, it doesn't prevent results from \"ping-ponging\" between "
"a limited set of values. To prevent this, use the :ref:`shuffle bag "
"<doc_random_number_generation_shuffle_bags>` pattern instead."
msgstr ""

#: ../../docs/tutorials/math/random_number_generation.rst:304
msgid "Get a random dictionary value"
msgstr ""

#: ../../docs/tutorials/math/random_number_generation.rst:306
msgid "We can apply similar logic from arrays to dictionaries as well:"
msgstr ""

#: ../../docs/tutorials/math/random_number_generation.rst:334
msgid "Weighted random probability"
msgstr ""

#: ../../docs/tutorials/math/random_number_generation.rst:336
msgid ""
"The :ref:`randf() <class_@GlobalScope_method_randf>` method returns a "
"floating-point number between 0.0 and 1.0. We can use this to create a "
"\"weighted\" probability where different outcomes have different likelihoods:"
msgstr ""

#: ../../docs/tutorials/math/random_number_generation.rst:399
msgid "\"Better\" randomness using shuffle bags"
msgstr ""

#: ../../docs/tutorials/math/random_number_generation.rst:401
msgid ""
"Taking the same example as above, we would like to pick fruits at random. "
"However, relying on random number generation every time a fruit is selected "
"can lead to a less *uniform* distribution. If the player is lucky (or "
"unlucky), they could get the same fruit three or more times in a row."
msgstr ""

#: ../../docs/tutorials/math/random_number_generation.rst:406
msgid ""
"You can accomplish this using the *shuffle bag* pattern. It works by "
"removing an element from the array after choosing it. After multiple "
"selections, the array ends up empty. When that happens, you reinitialize it "
"to its default value::"
msgstr ""

#: ../../docs/tutorials/math/random_number_generation.rst:436
msgid ""
"When running the above code, there is a chance to get the same fruit twice "
"in a row. Once we picked a fruit, it will no longer be a possible return "
"value unless the array is now empty. When the array is empty, we reset it "
"back to its default value, making it possible to have the same fruit again, "
"but only once."
msgstr ""

#: ../../docs/tutorials/math/random_number_generation.rst:442
msgid "Random noise"
msgstr ""

#: ../../docs/tutorials/math/random_number_generation.rst:444
msgid ""
"The random number generation shown above can show its limits when you need a "
"value that *slowly* changes depending on the input. The input can be a "
"position, time, or anything else."
msgstr ""

#: ../../docs/tutorials/math/random_number_generation.rst:448
msgid ""
"To achieve this, you can use random *noise* functions. Noise functions are "
"especially popular in procedural generation to generate realistic-looking "
"terrain. Godot provides :ref:`class_fastnoiselite` for this, which supports "
"1D, 2D and 3D noise. Here's an example with 1D noise:"
msgstr ""

#: ../../docs/tutorials/math/random_number_generation.rst:491
msgid "Cryptographically secure pseudorandom number generation"
msgstr ""

#: ../../docs/tutorials/math/random_number_generation.rst:493
msgid ""
"So far, the approaches mentioned above are **not** suitable for "
"*cryptographically secure* pseudorandom number generation (CSPRNG). This is "
"fine for games, but this is not sufficient for scenarios where encryption, "
"authentication or signing is involved."
msgstr ""

#: ../../docs/tutorials/math/random_number_generation.rst:498
msgid ""
"Godot offers a :ref:`class_Crypto` class for this. This class can perform "
"asymmetric key encryption/decryption, signing/verification, while also "
"generating cryptographically secure random bytes, RSA keys, HMAC digests, "
"and self-signed :ref:`class_X509Certificate`\\ s."
msgstr ""

#: ../../docs/tutorials/math/random_number_generation.rst:503
msgid ""
"The downside of :abbr:`CSPRNG (Cryptographically secure pseudorandom number "
"generation)` is that it's much slower than standard pseudorandom number "
"generation. Its API is also less convenient to use. As a result, :abbr:"
"`CSPRNG (Cryptographically secure pseudorandom number generation)` should be "
"avoided for gameplay elements."
msgstr ""

#: ../../docs/tutorials/math/random_number_generation.rst:509
msgid ""
"Example of using the Crypto class to generate 2 random integers between "
"``0`` and ``2^32 - 1`` (inclusive):"
msgstr ""

#: ../../docs/tutorials/math/random_number_generation.rst:531
msgid ""
"See :ref:`class_PackedByteArray`'s documentation for other methods you can "
"use to decode the generated bytes into various types of data, such as "
"integers or floats."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_introduction_2d.rst:4
#, fuzzy
msgid "2D navigation overview"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/navigation/navigation_introduction_2d.rst:6
msgid ""
"Godot provides multiple objects, classes and servers to facilitate grid-"
"based or mesh-based navigation and pathfinding for 2D and 3D games. The "
"following section provides a quick overview over all available navigation "
"related objects in Godot for 2D scenes and their primary use."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_introduction_2d.rst:9
msgid "Godot provides the following objects and classes for 2D navigation:"
msgstr ""

#: ../../docs/tutorials/navigation/navigation_introduction_2d.rst:14
#, fuzzy
msgid ":ref:`Astar2D<class_Astar2D>`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/navigation/navigation_introduction_2d.rst:12
msgid ""
"``Astar2D`` objects provide an option to find the shortest path in a graph "
"of weighted **points**."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_introduction_2d.rst:14
msgid ""
"The AStar2D class is best suited for cell-based 2D gameplay that does not "
"require actors to reach any possible position within an area but only "
"predefined, distinct positions."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_introduction_2d.rst:40
#, fuzzy
msgid ":ref:`NavigationServer2D<class_NavigationServer2D>`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/navigation/navigation_introduction_2d.rst:17
msgid ""
"``NavigationServer2D`` provides a powerful server API to find the shortest "
"path between two positions on a area defined by a navigation mesh."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_introduction_2d.rst:19
msgid ""
"The NavigationServer is best suited for 2D realtime gameplay that does "
"require actors to reach any possible position within a navigation mesh "
"defined area. Mesh-based navigation scales well with large game worlds as a "
"large area can often be defined with a single polygon when it would require "
"many, many grid cells."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_introduction_2d.rst:22
#: ../../docs/tutorials/navigation/navigation_introduction_3d.rst:22
msgid ""
"The NavigationServer holds different navigation maps that each consist of "
"regions that hold navigation mesh data. Agents can be placed on a map for "
"avoidance calculation. RIDs are used to reference internal maps, regions, "
"and agents when communicating with the server."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_introduction_2d.rst:40
#: ../../docs/tutorials/navigation/navigation_introduction_3d.rst:40
msgid "The following NavigationServer RID types are available."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_introduction_2d.rst:29
#: ../../docs/tutorials/navigation/navigation_introduction_3d.rst:29
msgid "NavMap RID"
msgstr ""

#: ../../docs/tutorials/navigation/navigation_introduction_2d.rst:28
#: ../../docs/tutorials/navigation/navigation_introduction_3d.rst:28
msgid ""
"Reference to a specific navigation map that holds regions and agents. The "
"map will attempt to join the navigation meshes of the regions by proximity. "
"The map will synchronize regions and agents each physics frame."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_introduction_2d.rst:32
#: ../../docs/tutorials/navigation/navigation_introduction_3d.rst:32
msgid "NavRegion RID"
msgstr ""

#: ../../docs/tutorials/navigation/navigation_introduction_2d.rst:32
#: ../../docs/tutorials/navigation/navigation_introduction_3d.rst:32
msgid ""
"Reference to a specific navigation region that can hold navigation mesh "
"data. The region can be enabled / disabled or the use restricted with a "
"navigation layer bitmask."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_introduction_2d.rst:34
#: ../../docs/tutorials/navigation/navigation_introduction_3d.rst:34
msgid "NavLink RID"
msgstr ""

#: ../../docs/tutorials/navigation/navigation_introduction_2d.rst:35
#: ../../docs/tutorials/navigation/navigation_introduction_3d.rst:35
msgid ""
"Reference to a specific navigation link that connects two navigation mesh "
"positions over arbitrary distances."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_introduction_2d.rst:37
#: ../../docs/tutorials/navigation/navigation_introduction_3d.rst:37
msgid "NavAgent RID"
msgstr ""

#: ../../docs/tutorials/navigation/navigation_introduction_2d.rst:37
msgid ""
"Reference to a specific avoidance agent. The avoidance is specified by a "
"radius value."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_introduction_2d.rst:40
#: ../../docs/tutorials/navigation/navigation_introduction_3d.rst:40
msgid "NavObstacle RID"
msgstr ""

#: ../../docs/tutorials/navigation/navigation_introduction_2d.rst:40
#: ../../docs/tutorials/navigation/navigation_introduction_3d.rst:40
msgid ""
"Reference to a specific avoidance obstacle used to affect and constrain the "
"avoidance velocity of agents."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_introduction_2d.rst:42
msgid ""
"The following scene tree nodes are available as helpers to work with the "
"NavigationServer2D API."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_introduction_2d.rst:49
#, fuzzy
msgid ":ref:`NavigationRegion2D<class_NavigationRegion2D>` Node"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/navigation/navigation_introduction_2d.rst:45
msgid ""
"A Node that holds a NavigationPolygon resource that defines a navigation "
"mesh for the NavigationServer2D."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_introduction_2d.rst:47
#: ../../docs/tutorials/navigation/navigation_introduction_3d.rst:47
msgid "The region can be enabled / disabled."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_introduction_2d.rst:48
#: ../../docs/tutorials/navigation/navigation_introduction_2d.rst:56
#: ../../docs/tutorials/navigation/navigation_introduction_3d.rst:48
#: ../../docs/tutorials/navigation/navigation_introduction_3d.rst:56
msgid ""
"The use in pathfinding can be further restricted through the "
"``navigation_layers`` bitmask."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_introduction_2d.rst:49
msgid ""
"The NavigationServer2D will join the navigation meshes of regions by "
"proximity for a combined navigation mesh."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_introduction_2d.rst:58
#, fuzzy
msgid ":ref:`NavigationLink2D<class_NavigationLink2D>` Node"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/navigation/navigation_introduction_2d.rst:52
#: ../../docs/tutorials/navigation/navigation_introduction_3d.rst:52
msgid ""
"A Node that connects two positions on navigation meshes over arbitrary "
"distances for pathfinding."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_introduction_2d.rst:54
#: ../../docs/tutorials/navigation/navigation_introduction_3d.rst:54
msgid "The link can be enabled / disabled."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_introduction_2d.rst:55
#: ../../docs/tutorials/navigation/navigation_introduction_3d.rst:55
msgid "The link can be made one-way or bidirectional."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_introduction_2d.rst:58
#: ../../docs/tutorials/navigation/navigation_introduction_3d.rst:58
msgid ""
"Links tell the pathfinding that a connection exists and at what cost. The "
"actual agent handling and movement needs to happen in custom scripts."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_introduction_2d.rst:62
#, fuzzy
msgid ":ref:`NavigationAgent2D<class_NavigationAgent2D>` Node"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/navigation/navigation_introduction_2d.rst:61
msgid ""
"A helper Node used to facilitate common NavigationServer2D API calls for "
"pathfinding and avoidance. Use this Node with a Node2D inheriting parent "
"Node."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_introduction_2d.rst:66
#, fuzzy
msgid ":ref:`NavigationObstacle2D<class_NavigationObstacle2D>` Node"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/navigation/navigation_introduction_2d.rst:65
#: ../../docs/tutorials/navigation/navigation_introduction_3d.rst:65
msgid ""
"A Node that can be used to affect and constrain the avoidance velocity of "
"avoidance enabled agents. This Node does NOT affect the pathfinding of "
"agents. You need to change the navigation meshes for that instead."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_introduction_2d.rst:68
#, fuzzy
msgid "The 2D navigation meshes are defined with the following resources:"
msgstr "Glavna dokumentacija za sajt je podeljena na sledeća poglavlja:"

#: ../../docs/tutorials/navigation/navigation_introduction_2d.rst:76
#, fuzzy
msgid ":ref:`NavigationPolygon<class_NavigationPolygon>` Resource"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/navigation/navigation_introduction_2d.rst:71
msgid ""
"A resource that holds 2D navigation mesh data. It provides polygon drawing "
"tools to allow defining navigation areas inside the Editor as well as at "
"runtime."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_introduction_2d.rst:74
msgid ""
"The NavigationRegion2D Node uses this resource to define its navigation area."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_introduction_2d.rst:75
msgid ""
"The NavigationServer2D uses this resource to update the navigation mesh of "
"individual regions."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_introduction_2d.rst:76
msgid ""
"The TileSet Editor creates and uses this resource internally when defining "
"tile navigation areas."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_introduction_2d.rst:80
msgid ""
"You can see how 2D navigation works in action using the `2D Navigation "
"Polygon <https://github.com/godotengine/godot-demo-projects/tree/master/2d/"
"navigation>`__ and `Grid-based Navigation with AStarGrid2D <https://github."
"com/godotengine/godot-demo-projects/tree/master/2d/navigation_astar>`__ demo "
"projects."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_introduction_2d.rst:86
msgid "Setup for 2D scene"
msgstr ""

#: ../../docs/tutorials/navigation/navigation_introduction_2d.rst:88
msgid ""
"The following steps show the basic setup for minimal viable navigation in "
"2D. It uses the NavigationServer2D and a NavigationAgent2D for path movement."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_introduction_2d.rst:91
msgid "Add a NavigationRegion2D Node to the scene."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_introduction_2d.rst:93
msgid ""
"Click on the region node and add a new NavigationPolygon Resource to the "
"region node."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_introduction_2d.rst:97
msgid ""
"Define the movable navigation area with the NavigationPolygon draw tool. "
"Then click the `Bake NavigationPolygon`` button on the toolbar."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_introduction_2d.rst:104
msgid ""
"The navigation mesh defines the area where an actor can stand and move with "
"its center. Leave enough margin between the navigation polygon edges and "
"collision objects to not get path following actors repeatedly stuck on "
"collision."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_introduction_2d.rst:107
msgid ""
"Add a CharacterBody2D node in the scene with a basic collision shape and a "
"sprite or mesh for visuals."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_introduction_2d.rst:110
msgid "Add a NavigationAgent2D node below the character node."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_introduction_2d.rst:114
msgid ""
"Add the following script to the CharacterBody2D node. We make sure to set a "
"movement target after the scene has fully loaded and the NavigationServer "
"had time to sync."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_introduction_2d.rst:216
#: ../../docs/tutorials/navigation/navigation_introduction_3d.rst:217
msgid ""
"On the first frame the NavigationServer map has not synchronized region data "
"and any path query will return empty. Wait for the NavigationServer "
"synchronization by awaiting one frame in the script."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_introduction_3d.rst:4
#, fuzzy
msgid "3D navigation overview"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/navigation/navigation_introduction_3d.rst:6
msgid ""
"Godot provides multiple objects, classes and servers to facilitate grid-"
"based or mesh-based navigation and pathfinding for 2D and 3D games. The "
"following section provides a quick overview over all available navigation "
"related objects in Godot for 3D scenes and their primary use."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_introduction_3d.rst:9
msgid "Godot provides the following objects and classes for 3D navigation:"
msgstr ""

#: ../../docs/tutorials/navigation/navigation_introduction_3d.rst:14
#, fuzzy
msgid ":ref:`Astar3D<class_Astar3D>`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/navigation/navigation_introduction_3d.rst:12
msgid ""
"``Astar3D`` objects provide an option to find the shortest path in a graph "
"of weighted **points**."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_introduction_3d.rst:14
msgid ""
"The AStar3D class is best suited for cell-based 3D gameplay that does not "
"require actors to reach any possible position within an area but only "
"predefined, distinct positions."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_introduction_3d.rst:40
#, fuzzy
msgid ":ref:`NavigationServer3D<class_NavigationServer3D>`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/navigation/navigation_introduction_3d.rst:17
msgid ""
"``NavigationServer3D`` provides a powerful server API to find the shortest "
"path between two positions on an area defined by a navigation mesh."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_introduction_3d.rst:19
msgid ""
"The NavigationServer is best suited for 3D realtime gameplay that does "
"require actors to reach any possible position within a navigation mesh "
"defined area. Mesh-based navigation scales well with large game worlds as a "
"large area can often be defined with a single polygon when it would require "
"many, many grid cells."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_introduction_3d.rst:37
msgid ""
"Reference to a specific avoidance agent. The avoidance is defined by a "
"radius value."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_introduction_3d.rst:42
msgid ""
"The following scene tree nodes are available as helpers to work with the "
"NavigationServer3D API."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_introduction_3d.rst:49
#, fuzzy
msgid ":ref:`NavigationRegion3D<class_NavigationRegion3D>` Node"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/navigation/navigation_introduction_3d.rst:45
msgid ""
"A Node that holds a Navigation Mesh resource that defines a navigation mesh "
"for the NavigationServer3D."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_introduction_3d.rst:49
msgid ""
"The NavigationServer3D will join the navigation meshes of regions by "
"proximity for a combined navigation mesh."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_introduction_3d.rst:58
#, fuzzy
msgid ":ref:`NavigationLink3D<class_NavigationLink3D>` Node"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/navigation/navigation_introduction_3d.rst:62
#, fuzzy
msgid ":ref:`NavigationAgent3D<class_NavigationAgent3D>` Node"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/navigation/navigation_introduction_3d.rst:61
msgid ""
"A helper Node used to facilitate common NavigationServer3D API calls for "
"pathfinding and avoidance. Use this Node with a Node3D inheriting parent "
"Node."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_introduction_3d.rst:66
#, fuzzy
msgid ":ref:`NavigationObstacle3D<class_NavigationObstacle3D>` Node"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/navigation/navigation_introduction_3d.rst:68
#, fuzzy
msgid "The 3D navigation meshes are defined with the following resources:"
msgstr "Glavna dokumentacija za sajt je podeljena na sledeća poglavlja:"

#: ../../docs/tutorials/navigation/navigation_introduction_3d.rst:76
#, fuzzy
msgid ":ref:`NavigationMesh<class_NavigationMesh>` Resource"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/navigation/navigation_introduction_3d.rst:71
msgid ""
"A resource that holds 3D navigation mesh data. It provides 3D geometry "
"baking options to define navigation areas inside the Editor as well as at "
"runtime."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_introduction_3d.rst:74
msgid ""
"The NavigationRegion3D Node uses this resource to define its navigation area."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_introduction_3d.rst:75
msgid ""
"The NavigationServer3D uses this resource to update the navigation mesh of "
"individual regions."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_introduction_3d.rst:76
msgid ""
"The GridMap Editor uses this resource when specific navigation meshes are "
"defined for each grid cell."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_introduction_3d.rst:80
#, fuzzy
msgid ""
"You can see how 3D navigation works in action using the `3D Navigation demo "
"project <https://github.com/godotengine/godot-demo-projects/tree/master/3d/"
"navigation>`__."
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati različite Godo demo projekte "
"`Godot demo projects <https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/tutorials/navigation/navigation_introduction_3d.rst:84
#, fuzzy
msgid "Setup for 3D scene"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/navigation/navigation_introduction_3d.rst:86
msgid ""
"The following steps show a basic setup for minimal viable navigation in 3D. "
"It uses the NavigationServer3D and a NavigationAgent3D for path movement."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_introduction_3d.rst:89
msgid "Add a NavigationRegion3D Node to the scene."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_introduction_3d.rst:91
msgid ""
"Click on the region node and add a new :ref:"
"`NavigationMesh<class_NavigationMesh>` Resource to the region node."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_introduction_3d.rst:96
msgid "Add a new MeshInstance3D node as a child of the region node."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_introduction_3d.rst:98
msgid ""
"Select the MeshInstance3D node and add a new PlaneMesh and increase the xy "
"size to 10."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_introduction_3d.rst:100
msgid ""
"Select the region node again and press the \"Bake Navmesh\" button on the "
"top bar."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_introduction_3d.rst:104
msgid ""
"Now a transparent navigation mesh appears that hovers some distance on top "
"of the PlaneMesh."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_introduction_3d.rst:108
msgid ""
"Add a CharacterBody3D node in the scene with a basic collision shape and "
"some mesh for visuals."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_introduction_3d.rst:110
msgid "Add a NavigationAgent3D node below the character node."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_introduction_3d.rst:114
msgid ""
"Add a script to the CharacterBody3D node with the following content. We make "
"sure to set a movement target after the scene has fully loaded and the "
"NavigationServer had time to sync. Also, add a Camera3D and some light and "
"environment to see something."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationservers.rst:4
#, fuzzy
msgid "Using NavigationServer"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/navigation/navigation_using_navigationservers.rst:6
msgid ""
"2D and 3D version of the NavigationServer are available as :ref:"
"`NavigationServer2D<class_NavigationServer2D>` and :ref:"
"`NavigationServer3D<class_NavigationServer3D>` respectively."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationservers.rst:10
msgid ""
"Both 2D and 3D use the same NavigationServer with NavigationServer3D being "
"the primary server. The NavigationServer2D is a frontend that converts 2D "
"positions into 3D positions and back. Hence it is entirely possible (if not "
"a little cumbersome) to exclusively use the NavigationServer3D API for 2D "
"navigation."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationservers.rst:14
msgid "Communicating with the NavigationServer"
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationservers.rst:16
msgid ""
"To work with the NavigationServer means to prepare parameters for a "
"**query** that can be sent to the NavigationServer for updates or requesting "
"data."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationservers.rst:18
msgid ""
"To reference the internal NavigationServer objects like maps, regions and "
"agents RIDs are used as identification numbers. Every navigation related "
"node in the scene tree has a function that returns the RID for this node."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationservers.rst:22
#, fuzzy
msgid "Threading and Synchronization"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/navigation/navigation_using_navigationservers.rst:24
msgid ""
"The NavigationServer does not update every change immediately but waits "
"until the end of the **physics frame** to synchronize all the changes "
"together."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationservers.rst:27
msgid ""
"Waiting for synchronization is required to apply changes to all maps, "
"regions and agents. Synchronization is done because some updates like a "
"recalculation of the entire navigation map are very expensive and require "
"updated data from all other objects. Also the NavigationServer uses a "
"**threadpool** by default for some functionality like avoidance calculation "
"between agents."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationservers.rst:31
msgid ""
"Waiting is not required for most ``get()`` functions that only request data "
"from the NavigationServer without making changes. Note that not all data "
"will account for changes made in the same frame. E.g. if an avoidance agent "
"changed the navigation map this frame the ``agent_get_map()`` function will "
"still return the old map before the synchronization. The exception to this "
"are nodes that store their values internally before sending the update to "
"the NavigationServer. When a getter on a node is used for a value that was "
"updated in the same frame it will return the already updated value stored on "
"the node."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationservers.rst:37
msgid ""
"The NavigationServer is **thread-safe** as it places all API calls that want "
"to make changes in a queue to be executed in the synchronization phase. "
"Synchronization for the NavigationServer happens in the middle of the "
"physics frame after scene input from scripts and nodes are all done."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationservers.rst:41
msgid ""
"The important takeaway is that most NavigationServer changes take effect "
"after the next physics frame and not immediately. This includes all changes "
"made by navigation related nodes in the scene tree or through scripts."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationservers.rst:44
msgid ""
"The following functions will be executed in the synchronization phase only:"
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationservers.rst:46
msgid "``map_set_active()``"
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationservers.rst:47
msgid "``map_set_up()``"
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationservers.rst:48
msgid "``map_set_cell_size()``"
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationservers.rst:49
msgid "``map_set_edge_connection_margin()``"
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationservers.rst:50
msgid "``region_set_map()``"
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationservers.rst:51
msgid "``region_set_transform()``"
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationservers.rst:52
msgid "``region_set_enter_cost()``"
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationservers.rst:53
msgid "``region_set_travel_cost()``"
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationservers.rst:54
msgid "``region_set_navigation_layers()``"
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationservers.rst:55
msgid "``region_set_navigation_mesh()``"
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationservers.rst:56
msgid "``agent_set_map()``"
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationservers.rst:57
msgid "``agent_set_neighbor_dist()``"
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationservers.rst:58
msgid "``agent_set_max_neighbors()``"
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationservers.rst:59
msgid "``agent_set_time_horizon()``"
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationservers.rst:60
msgid "``agent_set_radius()``"
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationservers.rst:61
msgid "``agent_set_max_speed()``"
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationservers.rst:62
msgid "``agent_set_velocity()``"
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationservers.rst:63
msgid "``agent_set_target_velocity()``"
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationservers.rst:64
msgid "``agent_set_position()``"
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationservers.rst:65
msgid "``agent_set_ignore_y()``"
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationservers.rst:66
msgid "``agent_set_callback()``"
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationservers.rst:67
msgid "``free()``"
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationservers.rst:70
msgid "2D and 3D NavigationServer differences"
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationservers.rst:72
msgid ""
"NavigationServer2D and NavigationServer3D are equivalent in functionality "
"for their dimension and both use the same NavigationServer behind the scene."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationservers.rst:75
msgid ""
"Strictly technical a NavigationServer2D is a myth. The NavigationServer2D is "
"a frontend to facilitate conversions of ``Vector2(x, y)`` to ``Vector3(x, "
"0.0, z)`` and back for the NavigationServer3D API. 2D uses a flat 3D mesh "
"pathfinding and the NavigationServer2D facilitates the conversions. When a "
"guide uses just NavigationServer without the 2D or 3D suffix it usually "
"works for both servers by exchange ``Vector2(x, y)`` with ``Vector3(x, 0.0, "
"z)`` or reverse."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationservers.rst:82
msgid ""
"Technically it is possible to use the tools for creating navigation meshes "
"in one dimension for the other dimension, e.g. baking a 2D navigation mesh "
"with the 3D NavigationMesh when using flat 3D source geometry or creating 3D "
"flat navigation meshes with the polygon outline draw tools of "
"NavigationRegion2D and NavigationPolygons."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationservers.rst:87
msgid ""
"Any RID created with the NavigationServer2D API works on the "
"NavigationServer3D API as well and both 2D and 3D avoidance agents can exist "
"on the same map."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationservers.rst:91
msgid ""
"Regions created in 2D and 3D will merge their navigation meshes when placed "
"on the same map and merge conditions apply. The NavigationServer does not "
"discriminate between NavigationRegion2D and NavigationRegion3D nodes as both "
"are regions on the server. By default those nodes register on different "
"navigation maps so this merge can only happen when maps are changed manually "
"e.g. with scripts."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationservers.rst:95
msgid ""
"Actors with avoidance enabled will avoid both 2D and 3D avoidance agents "
"when placed on the same map."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationservers.rst:98
msgid ""
"It is not possible to use NavigationServer2D while disabling 3D on a Godot "
"custom build."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationservers.rst:101
#, fuzzy
msgid "Waiting for synchronization"
msgstr "Organizacija dokumentacije"

#: ../../docs/tutorials/navigation/navigation_using_navigationservers.rst:103
msgid ""
"At the start of the game, a new scene or procedural navigation changes any "
"path query to a NavigationServer will return empty or wrong."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationservers.rst:105
msgid ""
"The navigation map is still empty or not updated at this point. All nodes "
"from the scene tree need to first upload their navigation related data to "
"the NavigationServer. Each added or changed map, region or agent need to be "
"registered with the NavigationServer. Afterward the NavigationServer "
"requires a **physics frame** for synchronization to update the maps, regions "
"and agents."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationservers.rst:110
msgid ""
"One workaround is to make a deferred call to a custom setup function (so all "
"nodes are ready). The setup function makes all the navigation changes, e.g. "
"adding procedural stuff. Afterwards the function waits for the next physics "
"frame before continuing with path queries."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationservers.rst:167
msgid "Server Avoidance Callbacks"
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationservers.rst:169
msgid ""
"If RVO avoidance agents are registered for avoidance callbacks the "
"NavigationServer dispatches their ``velocity_computed`` signals just before "
"the PhysicsServer synchronization."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationservers.rst:172
msgid ""
"To learn more about NavigationAgents see :ref:"
"`doc_navigation_using_navigationagents`."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationservers.rst:174
msgid ""
"The simplified order of execution for NavigationAgents that use avoidance:"
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationservers.rst:176
msgid "physics frame starts."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationservers.rst:177
msgid "``_physics_process(delta)``."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationservers.rst:178
msgid "``set_velocity()`` on NavigationAgent Node."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationservers.rst:179
msgid "Agent sends velocity and position to NavigationServer."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationservers.rst:180
msgid "NavigationServer waits for synchronization."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationservers.rst:181
msgid ""
"NavigationServer synchronizes and computes avoidance velocities for all "
"registered avoidance agents."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationservers.rst:182
msgid ""
"NavigationServer sends safe velocity vector with signals for each registered "
"avoidance agents."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationservers.rst:183
msgid ""
"Agents receive the signal and move their parent e.g. with ``move_and_slide`` "
"or ``linear_velocity``."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationservers.rst:184
msgid "PhysicsServer synchronizes."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationservers.rst:185
msgid "physics frame ends."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationservers.rst:187
msgid ""
"Therefore moving a physicsbody actor in the callback function with the safe "
"velocity is perfectly thread- and physics-safe as all happens inside the "
"same physics frame before the PhysicsServer commits to changes and does its "
"own calculations."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationmaps.rst:4
#, fuzzy
msgid "Using NavigationMaps"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/navigation/navigation_using_navigationmaps.rst:8
msgid ""
"A NavigationMap is an abstract navigation world on the NavigationServer "
"identified by a NavigationServer :ref:`RID<class_RID>`."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationmaps.rst:10
msgid ""
"A map can hold and connect a near infinite number of navigation regions with "
"navigation meshes to build the traversable areas of a game world for "
"pathfinding."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationmaps.rst:12
msgid ""
"A map can contain avoidance agents. Collision avoidance will be calculated "
"based on the agents present in the map."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationmaps.rst:16
msgid ""
"Different NavigationMaps are completely isolated from each other but "
"navigation regions and avoidance agents can switch between different maps. "
"Switches will become effective on NavigationServer synchronization."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationmaps.rst:20
msgid "Default navigation maps"
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationmaps.rst:22
msgid ""
"By default Godot creates a navigation map for each :ref:"
"`World2D<class_World2D>` and :ref:`World3D<class_World3D>` of the root "
"viewport."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationmaps.rst:24
msgid ""
"The 2D default navigation map RID can be obtained with ``get_world_2d()."
"get_navigation_map()`` from any :ref:`Node2D<class_Node2D>` inheriting Node."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationmaps.rst:26
msgid ""
"The 3D default navigation map RID can be obtained with ``get_world_3d()."
"get_navigation_map()`` from any :ref:`Node3D<class_Node3D>` inheriting Node."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationmaps.rst:43
#, fuzzy
msgid "Creating new navigation maps"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/navigation/navigation_using_navigationmaps.rst:45
msgid ""
"The NavigationServer can create and support as many navigation maps as "
"required for specific gameplay. Additional navigation maps are created and "
"handled by using the NavigationServer API directly e.g. to support different "
"avoidance agent or actor locomotion types."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationmaps.rst:49
msgid ""
"For example uses of different navigation maps see :ref:"
"`doc_navigation_different_actor_types` and :ref:"
"`doc_navigation_different_actor_locomotion`."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationmaps.rst:51
msgid ""
"Each navigation map individually synchronizes queued changes to its "
"navigation regions and avoidance agents. A navigation map that has not "
"received changes will consume little to no processing time. Navigation "
"regions and avoidance agents can only be part of a single navigation map but "
"they can switch map at any time."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationmaps.rst:57
msgid ""
"A navigation map switch will take effect only after the next "
"NavigationServer synchronization."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationmaps.rst:77
msgid ""
"There is no difference between navigation maps created with the "
"NavigationServer2D API or the NavigationServer3D API."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationregions.rst:4
#, fuzzy
msgid "Using NavigationRegions"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/navigation/navigation_using_navigationregions.rst:6
msgid ""
"NavigationRegions are the visual Node representation of a **region** of the "
"navigation **map** on the NavigationServer. Each NavigationRegion node holds "
"a resource for the navigation mesh data."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationregions.rst:9
msgid ""
"Both 2D and 3D version are available as :ref:"
"`NavigationRegion2D<class_NavigationRegion2D>` and :ref:"
"`NavigationRegion3D<class_NavigationRegion3D>` respectively."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationregions.rst:12
msgid ""
"Individual NavigationRegions upload their 2D NavigationPolygon or 3D "
"NavigationMesh resource data to the NavigationServer. The NavigationServer "
"map turns this information into a combined navigation map for pathfinding."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationregions.rst:15
msgid ""
"To create a navigation region using the scene tree add a "
"``NavigationRegion2D`` or ``NavigationRegion3D`` node to the scene. All "
"regions require a navigation mesh resource to function. See :ref:"
"`doc_navigation_using_navigationmeshes` to learn how to create and apply "
"navigation meshes."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationregions.rst:18
msgid ""
"NavigationRegions will automatically push ``global_transform`` changes to "
"the region on the NavigationServer which makes them suitable for moving "
"platforms. The NavigationServer will attempt to connect the navigation "
"meshes of individual regions when they are close enough. For more details "
"see :ref:`doc_navigation_connecting_navmesh`. To connect NavigationRegions "
"over arbitrary distances see :ref:`doc_navigation_using_navigationlinks` to "
"learn how to create and use ``NavigationLinks``."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationregions.rst:24
msgid ""
"While changing the transform of a NavigationRegion node does update the "
"region position on the NavigationServer, changing the scale does not. A "
"navigation mesh resource has no scale and needs to be fully updated when "
"source geometry changes scale."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationregions.rst:28
msgid ""
"Regions can be enabled / disabled and if disabled will not contribute to "
"future pathfinding queries."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationregions.rst:32
msgid ""
"Existing paths will not be automatically updated when a region gets "
"enabled / disabled."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationregions.rst:35
#, fuzzy
msgid "Creating new navigation regions"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/navigation/navigation_using_navigationregions.rst:37
msgid ""
"New NavigationRegion nodes will automatically register to the default world "
"navigation map for their 2D/3D dimension."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationregions.rst:39
msgid ""
"The region RID can then be obtained from NavigationRegion Nodes with "
"``get_region_rid()``."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationregions.rst:48
msgid ""
"New regions can also be created with the NavigationServer API and added to "
"any existing map."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationregions.rst:50
msgid ""
"If regions are created with the NavigationServer API directly they need to "
"be assigned a navigation map manually."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationregions.rst:72
msgid ""
"NavigationRegions can only be assigned to a single NavigationMap. If an "
"existing region is assigned to a new map it will leave the old map."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationmeshes.rst:4
#, fuzzy
msgid "Using navigation meshes"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/navigation/navigation_using_navigationmeshes.rst:8
msgid ""
"2D and 3D versions of the navigation mesh are available as :ref:"
"`NavigationPolygon<class_NavigationPolygon>` and :ref:"
"`NavigationMesh<class_NavigationMesh>`  respectively."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationmeshes.rst:14
msgid ""
"A navigation mesh only describes a traversable area for an agent's center "
"position. Any radius values an agent may have are ignored. If you want "
"pathfinding to account for an agent's (collision) size you need to shrink "
"the navigation mesh accordingly."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationmeshes.rst:17
msgid ""
"Navigation works independently from other engine parts like rendering or "
"physics. Navigation meshes are the only things considered when doing "
"pathfinding, e.g. visuals and collision shapes for example are completely "
"ignored by the navigation system. If you need to take other data (like "
"visuals for example) into account when doing pathfinding, you need to adapt "
"your navigation meshes accordingly. The process of factoring in navigation "
"restrictions in navigation meshes is commonly referred to as navigation mesh "
"baking."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationmeshes.rst:26
msgid "Navigation mesh polygon convex vs concave comparison"
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationmeshes.rst:26
msgid ""
"A navigation mesh describes a surface that an agent can stand on safely with "
"its center compared to physics shapes that describe outer collision bounds."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationmeshes.rst:28
msgid ""
"If you experience clipping or collision problems while following navigation "
"paths, always remember that you need to tell the navigation system what your "
"intentions are through an appropriate navigation mesh. By itself the "
"navigation system will never know \"this is a tree / rock / wall collision "
"shape or visual mesh\" because it only knows that \"here I was told I can "
"path safely because it is on a navigation mesh\"."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationmeshes.rst:33
msgid ""
"Navigation mesh baking can be done either by using a :ref:"
"`NavigationRegion2D<class_NavigationRegion2D>` or :ref:"
"`NavigationRegion3D<class_NavigationRegion3D>`, or by using the :ref:"
"`NavigationServer2D<class_NavigationServer2D>` and :ref:"
"`NavigationServer3D<class_NavigationServer3D>` API directly."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationmeshes.rst:39
msgid "Baking a navigation mesh with a NavigationRegion"
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationmeshes.rst:45
#, fuzzy
msgid "Navigation mesh baking steps"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/navigation/navigation_using_navigationmeshes.rst:45
msgid "Baking a navigation mesh with agent radius offset from geometry."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationmeshes.rst:47
msgid ""
"The navigation mesh baking is made more accessible with the NavigationRegion "
"node. When baking with a NavigationRegion node, the individual parsing, "
"baking, and region update steps are all combined into one function."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationmeshes.rst:50
msgid ""
"The nodes are available in 2D and 3D as :ref:"
"`NavigationRegion2D<class_NavigationRegion2D>` and :ref:"
"`NavigationRegion3D<class_NavigationRegion3D>` respectively."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationmeshes.rst:54
#, fuzzy
msgid "Baking with a NavigationRegion2D"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/navigation/navigation_using_navigationmeshes.rst:56
msgid ""
"When a NavigationRegion2D node is selected in the Editor, bake options as "
"well as polygon draw tools appear in the top bar of the Editor."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationmeshes.rst:60
#, fuzzy
msgid ""
"In order for the region to work a :ref:"
"`NavigationPolygon<class_NavigationPolygon>` resource needs to be added."
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/navigation/navigation_using_navigationmeshes.rst:62
#: ../../docs/tutorials/navigation/navigation_using_navigationmeshes.rst:108
msgid ""
"The properties to parse and bake a navigation mesh are then part of the used "
"resource and can be found in the resource Inspector."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationmeshes.rst:66
#: ../../docs/tutorials/navigation/navigation_using_navigationmeshes.rst:112
#, fuzzy
msgid ""
"The result of the source geometry parsing can be influenced with the "
"following properties."
msgstr "Glavna dokumentacija za sajt je podeljena na sledeća poglavlja:"

#: ../../docs/tutorials/navigation/navigation_using_navigationmeshes.rst:68
#: ../../docs/tutorials/navigation/navigation_using_navigationmeshes.rst:114
msgid ""
"The ``parsed_geometry_type`` that filters if visual objects or physics "
"objects or both should be parsed from the :ref:`SceneTree<class_SceneTree>`. "
"For more details on what objects are parsed and how, see the section about "
"parsing source geometry below."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationmeshes.rst:70
#: ../../docs/tutorials/navigation/navigation_using_navigationmeshes.rst:116
msgid ""
"The ``collision_mask`` filters which physics collision objects are included "
"when the ``parsed_geometry_type`` includes static colliders."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationmeshes.rst:71
#: ../../docs/tutorials/navigation/navigation_using_navigationmeshes.rst:117
msgid ""
"The ``source_geometry_mode`` that defines on which node(s) to start the "
"parsing, and how to traverse the :ref:`SceneTree<class_SceneTree>`."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationmeshes.rst:72
#: ../../docs/tutorials/navigation/navigation_using_navigationmeshes.rst:118
msgid ""
"The ``source_geometry_group_name`` is used when only a certain node group "
"should be parsed. Depends on the selected ``source_geometry_mode``."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationmeshes.rst:74
#: ../../docs/tutorials/navigation/navigation_using_navigationmeshes.rst:120
#, fuzzy
msgid ""
"With the source geometry added, the result of the baking can be controlled "
"with the following properties."
msgstr "Glavna dokumentacija za sajt je podeljena na sledeća poglavlja:"

#: ../../docs/tutorials/navigation/navigation_using_navigationmeshes.rst:76
msgid ""
"The ``cell_size`` sets the rasterization grid size and should match the "
"navigation map size."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationmeshes.rst:77
#: ../../docs/tutorials/navigation/navigation_using_navigationmeshes.rst:123
msgid ""
"The ``agent_radius`` shrinks the baked navigation mesh to have enough margin "
"for the agent (collision) size."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationmeshes.rst:79
msgid "The NavigationRegion2D baking can also be used at runtime with scripts."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationmeshes.rst:87
msgid "To quickly test the 2D baking with default settings:"
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationmeshes.rst:89
#, fuzzy
msgid "Add a :ref:`NavigationRegion2D<class_NavigationRegion2D>`."
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/navigation/navigation_using_navigationmeshes.rst:90
#, fuzzy
msgid ""
"Add a :ref:`NavigationPolygon<class_NavigationPolygon>` resource to the "
"NavigationRegion2D."
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/navigation/navigation_using_navigationmeshes.rst:91
msgid "Add a :ref:`Polygon2D<class_Polygon2D>` below the NavigationRegion2D."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationmeshes.rst:92
msgid ""
"Draw 1 NavigationPolygon outline with the selected NavigationRegion2D draw "
"tool."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationmeshes.rst:93
msgid ""
"Draw 1 Polygon2D outline inside the NavigationPolygon outline with the "
"selected Polygon2D draw tool."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationmeshes.rst:94
#: ../../docs/tutorials/navigation/navigation_using_navigationmeshes.rst:146
msgid "Hit the Editor bake button and a navigation mesh should appear."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationmeshes.rst:100
#, fuzzy
msgid "Baking with a NavigationRegion3D"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/navigation/navigation_using_navigationmeshes.rst:102
msgid ""
"When a NavigationRegion3D node is selected in the Editor, bake options "
"appear in the top bar of the Editor."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationmeshes.rst:106
#, fuzzy
msgid ""
"In order for the region to work a :ref:"
"`NavigationMesh<class_NavigationMesh>` resource needs to be added."
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/navigation/navigation_using_navigationmeshes.rst:122
msgid ""
"The ``cell_size`` and ``cell_height`` sets the rasterization voxel grid size "
"and should match the navigation map size."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationmeshes.rst:124
msgid ""
"The ``agent_height`` excludes areas from the navigation mesh where the agent "
"is too tall to fit in."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationmeshes.rst:125
msgid ""
"The ``agent_max_climb`` and ``agent_max_slope`` removes areas where the "
"height difference between neighboring voxels is too large, or where their "
"surface is too steep."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationmeshes.rst:129
msgid ""
"A too small ``cell_size`` or ``cell_height`` can create so many voxels that "
"it has the potential to freeze the game or even crash."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationmeshes.rst:132
msgid "The NavigationRegion3D baking can also be used at runtime with scripts."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationmeshes.rst:140
msgid "To quickly test the 3D baking with default settings:"
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationmeshes.rst:142
#, fuzzy
msgid "Add a :ref:`NavigationRegion3D<class_NavigationRegion3D>`."
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/navigation/navigation_using_navigationmeshes.rst:143
#, fuzzy
msgid ""
"Add a :ref:`NavigationMesh<class_NavigationMesh>` resource to the "
"NavigationRegion3D."
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/navigation/navigation_using_navigationmeshes.rst:144
msgid ""
"Add a :ref:`MeshInstance3D<class_MeshInstance3D>` below the "
"NavigationRegion3D."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationmeshes.rst:145
msgid "Add a :ref:`PlaneMesh<class_PlaneMesh>` to the MeshInstance3D."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationmeshes.rst:155
msgid "Baking a navigation mesh with the NavigationServer"
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationmeshes.rst:157
msgid ""
"The :ref:`NavigationServer2D<class_NavigationServer2D>` and :ref:"
"`NavigationServer3D<class_NavigationServer3D>` have API functions to call "
"each step of the navigation mesh baking process individually."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationmeshes.rst:159
msgid ""
"``parse_source_geometry_data()`` can be used to parse source geometry to a "
"reusable and serializable resource."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationmeshes.rst:160
msgid ""
"``bake_from_source_geometry_data()`` can be used to bake a navigation mesh "
"from already parsed data e.g. to avoid runtime performance issues with "
"(redundant) parsing."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationmeshes.rst:161
msgid ""
"``bake_from_source_geometry_data_async()`` is the same but bakes the "
"navigation mesh deferred with threads, not blocking the main thread."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationmeshes.rst:163
msgid ""
"Compared to a NavigationRegion, the NavigationServer offers finer control "
"over the navigation mesh baking process. In turn it is more complex to use "
"but also provides more advanced options."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationmeshes.rst:166
msgid ""
"Some other advantages of the NavigationServer over a NavigationRegion are:"
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationmeshes.rst:168
msgid ""
"The server can parse source geometry without baking, e.g. to cache it for "
"later use."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationmeshes.rst:169
msgid ""
"The server allows selecting the root node at which to start the source "
"geometry parsing manually."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationmeshes.rst:170
msgid ""
"The server can accept and bake from procedurally generated source geometry "
"data."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationmeshes.rst:171
msgid ""
"The server can bake multiple navigation meshes in sequence while (re)using "
"the same source geometry data."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationmeshes.rst:173
msgid ""
"To bake navigation meshes with the NavigationServer, source geometry is "
"required. Source geometry is geometry data that should be considered in a "
"navigation mesh baking process. Both navigation meshes for 2D and 3D are "
"created by baking them from source geometry."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationmeshes.rst:177
msgid ""
"2D and 3D versions of the source geometry resources are available as :ref:"
"`NavigationMeshSourceGeometryData2D<class_NavigationMeshSourceGeometryData2D>` "
"and :ref:"
"`NavigationMeshSourceGeometryData3D<class_NavigationMeshSourceGeometryData3D>`  "
"respectively."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationmeshes.rst:181
msgid ""
"Source geometry can be geometry parsed from visual meshes, from physics "
"collision, or procedural created arrays of data, like outlines (2D) and "
"triangle faces (3D). For convenience, source geometry is commonly parsed "
"directly from node setups in the SceneTree. For runtime navigation mesh "
"(re)bakes, be aware that the geometry parsing always happens on the main "
"thread."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationmeshes.rst:188
msgid ""
"The SceneTree is not thread-safe. Parsing source geometry from the SceneTree "
"can only be done on the main thread."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationmeshes.rst:192
msgid ""
"The data from visual meshes and polygons needs to be received from the GPU, "
"stalling the RenderingServer in the process. For runtime (re)baking prefer "
"using physics shapes as parsed source geometry."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationmeshes.rst:195
msgid ""
"Source geometry is stored inside resources so the created geometry can be "
"reused for multiple bakes. E.g. baking multiple navigation meshes for "
"different agent sizes from the same source geometry. This also allows to "
"save source geometry to disk so it can be loaded later, e.g. to avoid the "
"overhead of parsing it again at runtime."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationmeshes.rst:199
msgid ""
"The geometry data should be in general kept very simple. As many edges as "
"are required but as few as possible. Especially in 2D duplicated and nested "
"geometry should be avoided as it forces polygon hole calculation that can "
"result in flipped polygons. An example for nested geometry would be a "
"smaller StaticBody2D shape placed completely inside the bounds of another "
"StaticBody2D shape."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationmeshes.rst:204
#, fuzzy
msgid "Navigation mesh baking common problems"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/navigation/navigation_using_navigationmeshes.rst:206
msgid ""
"There are some common user problems and important caveats to consider when "
"creating or baking navigation meshes."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationmeshes.rst:218
msgid "Navigation mesh baking creates frame rate problems at runtime"
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationmeshes.rst:209
msgid ""
"The navigation mesh baking is by default done on a background thread, so as "
"long as the platform supports threads, the actual baking is rarely the "
"source of any performance issues (assuming a reasonably sized and complex "
"geometry for runtime rebakes)."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationmeshes.rst:212
msgid ""
"The common source for performance issues at runtime is the parsing step for "
"source geometry that involves nodes and the SceneTree. The SceneTree is not "
"thread-safe so all the nodes need to be parsed on the main thread. Some "
"nodes with a lot of data can be very heavy and slow to parse at runtime, e."
"g. a TileMap has one or more polygons for every single used cell and "
"TileMapLayer to parse. Nodes that hold meshes need to request the data from "
"the RenderingServer stalling the rendering in the process."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationmeshes.rst:217
msgid ""
"To improve performance, use more optimized shapes, e.g. collision shapes "
"over detailed visual meshes, and merge and simplify as much geometry as "
"possible upfront. If nothing helps, don't parse the SceneTree and add the "
"source geometry procedural with scripts. If only pure data arrays are used "
"as source geometry, the entire baking process can be done on a background "
"thread."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationmeshes.rst:225
msgid "Navigation mesh creates unintended holes in 2D."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationmeshes.rst:221
msgid ""
"The navigation mesh baking in 2D is done by doing polygon clipping "
"operations based on outline paths. Polygons with \"holes\" are a necessary "
"evil to create more complex 2D polygons but can become unpredictable for "
"users with many complex shapes involved."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationmeshes.rst:224
msgid ""
"To avoid any unexpected problems with polygon hole calculations, avoid "
"nesting any outlines inside other outlines of the same type (traversable / "
"obstruction). This includes the parsed shapes from nodes. E.g. placing a "
"smaller StaticBody2D shape inside a larger StaticBody2D shape can result in "
"the resulting polygon being flipped."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationmeshes.rst:230
msgid "Navigation mesh appears inside geometry in 3D."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationmeshes.rst:228
msgid ""
"The navigation mesh baking in 3D has no concept of \"inside\". The voxel "
"cells used to rasterize the geometry are either occupied or not. Remove the "
"geometry that is on the ground inside the other geometry. If that is not "
"possible, add smaller \"dummy\" geometry inside with as few triangles as "
"possible so the cells are occupied with something."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationmeshes.rst:233
#, fuzzy
msgid "Navigation mesh script templates"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/navigation/navigation_using_navigationmeshes.rst:235
msgid ""
"The following script uses the NavigationServer to parse source geometry from "
"the scene tree, bakes a navigation mesh, and updates a navigation region "
"with the updated navigation mesh."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationmeshes.rst:350
msgid ""
"The following script uses the NavigationServer to update a navigation region "
"with procedurally generated navigation mesh data."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationpaths.rst:4
#, fuzzy
msgid "Using NavigationPaths"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/navigation/navigation_using_navigationpaths.rst:7
#, fuzzy
msgid "Obtaining a NavigationPath"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/navigation/navigation_using_navigationpaths.rst:9
msgid ""
"Navigation paths can be directly queried from the NavigationServer and do "
"not require any additional nodes or objects as long as the navigation map "
"has a navigation mesh to work with."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationpaths.rst:12
msgid ""
"To obtain a 2D path, use ``NavigationServer2D.map_get_path(map, from, to, "
"optimize, navigation_layers)``."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationpaths.rst:14
msgid ""
"To obtain a 3D path, use ``NavigationServer3D.map_get_path(map, from, to, "
"optimize, navigation_layers)``."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationpaths.rst:16
msgid ""
"For more customizable navigation path queries that require additional setup "
"see :ref:`doc_navigation_using_navigationpathqueryobjects`."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationpaths.rst:18
msgid ""
"One of the required parameters for the query is the RID of the navigation "
"map. Each game world has a default navigation map automatically created. The "
"default navigation maps can be retrieved with ``get_world_2d()."
"get_navigation_map()`` from any Node2D inheriting node or ``get_world_3d()."
"get_navigation_map()`` from any Node3D inheriting node. The second and third "
"parameters are the starting position and the target position as Vector2 for "
"2D or Vector3 for 3D."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationpaths.rst:24
msgid ""
"If the ``optimized`` parameter is ``true``, path positions will be shortened "
"along polygon corners with an additional funnel algorithm pass. This works "
"well for free movement on navigation meshes with unequally sized polygons as "
"the path will hug around corners along the polygon corridor found by the A* "
"algorithm. With small cells the A* algorithm creates a very narrow funnel "
"corridor that can create ugly corner paths when used with grids."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationpaths.rst:30
msgid ""
"If the ``optimized`` parameter is ``false``, path positions will be placed "
"at the center of each polygon edge. This works well for pure grid movement "
"on navigation meshes with equally sized polygons as the path will go through "
"the center of the grid cells. Outside of grids due to polygons often "
"covering large open areas with a single, long edge this can create paths "
"with unnecessary long detours."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationpaths.rst:65
msgid ""
"A returned ``path`` by the NavigationServer will be a ``PackedVector2Array`` "
"for 2D or a ``PackedVector3Array`` for 3D. These are just a memory-optimized "
"``Array`` of vector positions. All position vectors inside the array are "
"guaranteed to be inside a NavigationPolygon or NavigationMesh. The path "
"array, if not empty, has the navigation mesh position closest to the "
"starting position at the first index ``path[0]`` position. The closest "
"available navigation mesh position to the target position is the last index "
"``path[path.size()-1]`` position. All indexes between are the path points "
"that an actor should follow to reach the target without leaving the "
"navigation mesh."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationpaths.rst:74
msgid ""
"If the target position is on a different navigation mesh that is not merged "
"or connected the navigation path will lead to the closest possible position "
"on the starting position navigation mesh."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationpaths.rst:77
msgid ""
"The following script moves a Node3D inheriting node along a navigation path "
"using the default navigation map by setting the target position with "
"``set_movement_target()``."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationpathqueryobjects.rst:4
msgid "Using NavigationPathQueryObjects"
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationpathqueryobjects.rst:6
msgid ""
"``NavigationPathQueryObjects`` can be used together with ``NavigationServer."
"query_path()`` to obtain a heavily **customized** navigation path including "
"optional **meta data** about the path."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationpathqueryobjects.rst:9
msgid ""
"This requires more setup compared to obtaining a normal NavigationPath but "
"lets you tailor the pathfinding and provided path data to the different "
"needs of a project."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationpathqueryobjects.rst:12
msgid ""
"NavigationPathQueryObjects consist of a pair of objects, a "
"``NavigationPathQueryParameters`` object holding the customization options "
"for the query and a ``NavigationPathQueryResult`` that receives (regular) "
"updates with the resulting path and meta data from the query."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationpathqueryobjects.rst:15
msgid ""
"2D and 3D versions of ``NavigationPathQueryParameters`` are available as :"
"ref:`NavigationPathQueryParameters2D<class_NavigationPathQueryParameters2D>` "
"and :ref:"
"`NavigationPathQueryParameters3D<class_NavigationPathQueryParameters3D>` "
"respectively."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationpathqueryobjects.rst:19
msgid ""
"2D and 3D versions of ``NavigationPathQueryResult`` are available as :ref:"
"`NavigationPathQueryResult2D<class_NavigationPathQueryResult2D>` and :ref:"
"`NavigationPathQueryResult3D<class_NavigationPathQueryResult3D>` "
"respectively."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationpathqueryobjects.rst:23
msgid ""
"Both parameters and result are used as a pair with the ``NavigationServer."
"query_path()`` function."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationpathqueryobjects.rst:25
msgid ""
"For the available customization options and their use see the class doc of "
"the parameters."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationpathqueryobjects.rst:27
msgid ""
"While not a strict requirement, both objects are intended to be created once "
"in advance, stored in a persistent variable for the agent and reused for "
"every followup path query with updated parameters. This reuse avoids "
"performance implications from frequent object creation if a project has a "
"large quantity of simultaneous agents that regularly update their paths."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationagents.rst:4
#, fuzzy
msgid "Using NavigationAgents"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/navigation/navigation_using_navigationagents.rst:6
msgid ""
"NavigationsAgents are helper nodes that combine functionality for "
"pathfinding, path following and agent avoidance for a Node2D/3D inheriting "
"parent node. They facilitate common calls to the NavigationServer API on "
"behalf of the parent actor node in a more convenient manner for beginners."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationagents.rst:11
msgid ""
"2D and 3D version of NavigationAgents are available as :ref:"
"`NavigationAgent2D<class_NavigationAgent2D>` and :ref:"
"`NavigationAgent3D<class_NavigationAgent3D>` respectively."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationagents.rst:15
msgid ""
"New NavigationAgent nodes will automatically join the default navigation map "
"on the :ref:`World2D<class_World2D>`/:ref:`World3D<class_World3D>`."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationagents.rst:17
msgid ""
"NavigationsAgent nodes are optional and not a hard requirement to use the "
"navigation system. Their entire functionality can be replaced with scripts "
"and direct calls to the NavigationServer API."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationagents.rst:21
msgid "NavigationAgent Pathfinding"
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationagents.rst:23
msgid ""
"NavigationAgents query a new navigation path on their current navigation map "
"when their ``target_position`` is set with a global position."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationagents.rst:25
#, fuzzy
msgid ""
"The result of the pathfinding can be influenced with the following "
"properties."
msgstr "Glavna dokumentacija za sajt je podeljena na sledeća poglavlja:"

#: ../../docs/tutorials/navigation/navigation_using_navigationagents.rst:27
msgid ""
"The ``navigation_layers`` bitmask can be used to limit the navigation meshes "
"that the agent can use."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationagents.rst:28
msgid ""
"The ``pathfinding_algorithm`` controls how the pathfinding travels through "
"the navigation mesh polygons in the path search."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationagents.rst:29
msgid ""
"The ``path_postprocessing`` sets if or how the raw path corridor found by "
"the pathfinding is altered before it is returned."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationagents.rst:30
msgid ""
"The ``path_metadata_flags`` enable the collection of additional path point "
"meta data returned by the path."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationagents.rst:34
msgid ""
"Disabling path meta flags will disable related signal emissions on the agent."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationagents.rst:37
msgid "NavigationAgent Pathfollowing"
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationagents.rst:39
msgid ""
"After a ``target_position`` has been set for the agent, the next position to "
"follow in the path can be retrieved with the ``get_next_path_position()`` "
"function."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationagents.rst:42
msgid ""
"Once the next path position is received move the parent actor node of the "
"agent towards this path position with your own movement code."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationagents.rst:47
msgid ""
"The navigation system never moves the parent node of a NavigationAgent. The "
"movement is entirely in the hands of users and their custom scripts."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationagents.rst:50
msgid ""
"NavigationAgents have their own internal logic to proceed with the current "
"path and call for updates."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationagents.rst:52
msgid ""
"The ``get_next_path_position()`` function is responsible for updating many "
"of the agent's internal states and properties. The function should be "
"repeatedly called *once* every ``physics_process`` until "
"``is_navigation_finished()`` tells that the path is finished. The function "
"should not be called after the target position or path end has been reached "
"as it can make the agent jitter in place due to the repeated path updates. "
"Always check very early in script with ``is_navigation_finished()`` if the "
"path is already finished."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationagents.rst:58
msgid "The following properties influence the path following behavior."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationagents.rst:60
msgid ""
"The ``path_desired_distance`` defines the distance at which the agent "
"advances its internal path index to the next path position."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationagents.rst:61
msgid ""
"The ``target_desired_distance`` defines the distance at which the agent "
"considers the target position to be reached and the path at its end."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationagents.rst:62
msgid ""
"The ``path_max_distance`` defines when an agent requests a new path cause it "
"was moved too far away from the current path point segment."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationagents.rst:64
msgid ""
"The important updates are all triggered with the "
"``get_next_path_position()`` function when called in ``_physics_process()``."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationagents.rst:67
msgid ""
"NavigationAgents can be used with ``process`` but are still limited to a "
"single update that happens in ``physics_process``."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationagents.rst:69
msgid ""
"Script examples for various nodes commonly used with NavigationAgents can be "
"found further below."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationagents.rst:72
msgid "Pathfollowing common problems"
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationagents.rst:74
msgid ""
"There are some common user problems and important caveats to consider when "
"writing agent movement scripts."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationagents.rst:77
msgid "The path is returned empty"
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationagents.rst:77
msgid ""
"If an agent queries a path before the navigation map synchronisation, e.g. "
"in a ``_ready()`` function, the path might return empty. In this case the "
"``get_next_path_position()`` function will return the same position as the "
"agent parent node and the agent will consider the path end reached. This is "
"fixed by making a deferred call or using a callback e.g. waiting for the "
"navigation map changed signal."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationagents.rst:80
msgid "The agent is stuck dancing between two positions"
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationagents.rst:80
msgid ""
"This is usually caused by very frequent path updates every single frame, "
"either deliberate or by accident (e.g. max path distance set too short). The "
"pathfinding needs to find the closest position that are valid on navigation "
"mesh. If a new path is requested every single frame the first path positions "
"might end up switching constantly in front and behind the agent's current "
"position, causing it to dance between the two positions."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationagents.rst:83
msgid "The agent is backtracking sometimes"
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationagents.rst:83
msgid ""
"If an agent moves very fast it might overshoot the path_desired_distance "
"check without ever advancing the path index. This can lead to the agent "
"backtracking to the path point now behind it until it passes the distance "
"check to increase the path index. Increase the desired distances accordingly "
"for your agent speed and update rate usually fixes this as well as a more "
"balanced navigation mesh polygon layout with not too many polygon edges "
"cramped together in small spaces."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationagents.rst:86
msgid "The agent is sometimes looking backwards for a frame"
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationagents.rst:86
msgid ""
"Same as with stuck dancing agents between two positions, this is usually "
"caused by very frequent path updates every single frame. Depending on your "
"navigation mesh layout, and especially when an agent is directly placed over "
"a navigation mesh edge or edge connection, expect path positions to be "
"sometimes slightly \"behind\" your actors current orientation. This happens "
"due to precision issues and can not always be avoided. This is usually only "
"a visible problem if actors are instantly rotated to face the current path "
"position."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationagents.rst:89
msgid "NavigationAgent Avoidance"
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationagents.rst:91
msgid ""
"This section explains how to use the navigation avoidance specific to "
"NavigationAgents."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationagents.rst:93
msgid ""
"In order for NavigationAgents to use the avoidance feature the "
"``enable_avoidance`` property must be set to ``true``."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationagents.rst:97
msgid ""
"The ``velocity_computed`` signal of the NavigationAgent node must be "
"connected to receive the safe velocity calculation result."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationagents.rst:101
msgid ""
"Use ``set_velocity()`` on the NavigationAgent node in ``_physics_process()`` "
"to update the agent with the current velocity of the agent's parent node."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationagents.rst:103
msgid ""
"While avoidance is enabled on the agent the ``safe_velocity`` vector will be "
"received with the velocity_computed signal every physics frame. This "
"velocity vector should be used to move the NavigationAgent's parent node in "
"order to avoidance collision with other avoidance using agents or avoidance "
"obstacles."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationagents.rst:108
msgid ""
"Only other agents on the same map that are registered for avoidance themself "
"will be considered in the avoidance calculation."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationagents.rst:110
msgid "The following NavigationAgent properties are relevant for avoidance:"
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationagents.rst:112
msgid ""
"The property ``height`` is available in 3D only. The height together with "
"the current global y-axis position of the agent determines the vertical "
"placement of the agent in the avoidance simulation. Agents using the 2D "
"avoidance will automatically ignore other agents or obstacles that are below "
"or above them."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationagents.rst:113
msgid ""
"The property ``radius`` controls the size of the avoidance circle, or in "
"case of 3D sphere, around the agent. This area describes the agents body and "
"not the avoidance maneuver distance."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationagents.rst:114
msgid ""
"The property ``neighbor_distance`` controls the search radius of the agent "
"when searching for other agents that should be avoided. A lower value "
"reduces processing cost."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationagents.rst:115
msgid ""
"The property ``max_neighbors`` controls how many other agents are considered "
"in the avoidance calculation if they all have overlapping radius. A lower "
"value reduces processing cost but a too low value may result in agents "
"ignoring the avoidance."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationagents.rst:117
msgid ""
"The properties ``time_horizon_agents`` and ``time_horizon_obstacles`` "
"control the avoidance prediction time for other agents or obstacles in "
"seconds. When agents calculate their safe velocities they choose velocities "
"that can be kept for this amount of seconds without colliding with another "
"avoidance object. The prediction time should be kept as low as possible as "
"agents will slow down their velocities to avoid collision in that timeframe."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationagents.rst:118
msgid ""
"The property ``max_speed`` controls the maximum velocity allowed for the "
"agents avoidance calculation. If the agents parents moves faster than this "
"value the avoidance ``safe_velocity`` might not be accurate enough to avoid "
"collision."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationagents.rst:120
msgid ""
"The property ``use_3d_avoidance`` switches the agent between the 2D "
"avoidance (xz axis) and the 3D avoidance (xyz axis) on the next update. Note "
"that 2D avoidance and 3D avoidance run in separate avoidance simulations so "
"agents split between them do not affect each other."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationagents.rst:122
msgid ""
"The properties ``avoidance_layers`` and ``avoidance_mask`` are bitmasks "
"similar to e.g. physics layers. Agents will only avoid other avoidance "
"objects that are on an avoidance layer that matches at least one of their "
"own avoidance mask bits."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationagents.rst:123
msgid ""
"The ``avoidance_priority`` makes agents with a higher priority ignore agents "
"with a lower priority. This can be used to give certain agents more "
"importance in the avoidance simulation, e.g. important npcs characters, "
"without constantly changing their entire avoidance layers or mask."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationagents.rst:126
msgid ""
"Avoidance exists in its own space and has no information from navigation "
"meshes or physics collision. Behind the scene avoidance agents are just "
"circles with different radius on a flat 2D plane or spheres in an otherwise "
"empty 3D space. NavigationObstacles can be used to add some environment "
"constrains to the avoidance simulation, see :ref:"
"`doc_navigation_using_navigationobstacles`."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationagents.rst:132
msgid ""
"Avoidance does not affect the pathfinding. It should be seen as an "
"additional option for constantly moving objects that cannot be (re)baked to "
"a navigation mesh efficiently in order to move around them."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationagents.rst:134
msgid ""
"Using the NavigationAgent ``enable_avoidance`` property is the preferred "
"option to toggle avoidance. The following code snippets can be used to "
"toggle avoidance on agents, create or delete avoidance callbacks or switch "
"avoidance modes."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationagents.rst:175
#, fuzzy
msgid "NavigationAgent Script Templates"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/navigation/navigation_using_navigationagents.rst:177
msgid ""
"The following sections provides script templates for nodes commonly used "
"with NavigationAgents."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationagents.rst:180
msgid "Actor as Node3D"
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationagents.rst:182
msgid ""
"This script adds basic navigation movement to a :ref:`Node3D <class_Node3D>` "
"with a :ref:`NavigationAgent3D <class_NavigationAgent3D>` child node."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationagents.rst:215
msgid "Actor as CharacterBody3D"
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationagents.rst:217
msgid ""
"This script adds basic navigation movement to a :ref:`CharacterBody3D "
"<class_CharacterBody3D>` with a :ref:`NavigationAgent3D "
"<class_NavigationAgent3D>` child node."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationagents.rst:249
msgid "Actor as RigidBody3D"
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationagents.rst:251
msgid ""
"This script adds basic navigation movement to a :ref:`RigidBody3D "
"<class_RigidBody3D>` with a :ref:`NavigationAgent3D "
"<class_NavigationAgent3D>` child node."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationobstacles.rst:4
#, fuzzy
msgid "Using NavigationObstacles"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/navigation/navigation_using_navigationobstacles.rst:6
msgid ""
"NavigationObstacles can be used either as static or dynamic obstacles to "
"affect avoidance controlled agents."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationobstacles.rst:8
msgid ""
"When used statically NavigationObstacles constrain avoidance controlled "
"agents outside or inside a polygon defined area."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationobstacles.rst:9
msgid ""
"When used dynamically NavigationObstacles push away avoidance controlled "
"agents in a radius around them."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationobstacles.rst:11
msgid ""
"2D and 3D versions of NavigationObstacles nodes are available as :ref:"
"`NavigationObstacle2D<class_NavigationObstacle2D>` and :ref:"
"`NavigationObstacle3D<class_NavigationObstacle3D>`  respectively."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationobstacles.rst:16
msgid ""
"NavigationObstacles do not change or influence the pathfinding in any way. "
"NavigationObstacles only affect the avoidance velocities of agents "
"controlled by avoidance."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationobstacles.rst:20
msgid "Static obstacles"
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationobstacles.rst:22
msgid ""
"A NavigationObstacle is considered static when its ``vertices`` property is "
"populated with an outline array of positions to form a polygon."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationobstacles.rst:26
msgid ""
"Static obstacles act as hard do-not-cross boundaries for avoidance using "
"agents, e.g. similar to physics collision but for avoidance."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationobstacles.rst:27
msgid ""
"Static obstacles define their boundaries with an array of outline "
"``vertices`` (positions), and in case of 3D with an additional ``height`` "
"property."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationobstacles.rst:28
msgid "Static obstacles only work for agents that use the 2D avoidance mode."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationobstacles.rst:29
msgid ""
"Static obstacles define through winding order of the vertices if agents are "
"pushed out or sucked in."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationobstacles.rst:30
msgid ""
"Static obstacles can not change their position. They can only be warped to a "
"new position and rebuild from scratch. Static obstacles as a result are ill-"
"suited for usages where the position is changed every frame as the constant "
"rebuild has a high performance cost."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationobstacles.rst:31
msgid ""
"Static obstacles that are warped to another position can not be predicted by "
"agents. This creates the risk of getting agents stuck should a static "
"obstacle be warped on top of agents."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationobstacles.rst:33
msgid ""
"When the 2D avoidance is used in 3D the y-axis of Vector3 vertices is "
"ignored. Instead, the global y-axis position of the obstacle is used as the "
"elevation level. Agents will ignore static obstacles in 3D that are below or "
"above them. This is automatically determined by global y-axis position of "
"both obstacle and agent as the elevation level as well as their respective "
"height properties."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationobstacles.rst:36
msgid "Dynamic obstacles"
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationobstacles.rst:38
msgid ""
"A NavigationObstacle is considered dynamic when its ``radius`` property is "
"greater than zero."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationobstacles.rst:40
msgid ""
"Dynamic obstacles act as a soft please-move-away-from-me object for "
"avoidance using agents, e.g. similar to how they avoid other agents."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationobstacles.rst:41
msgid ""
"Dynamic obstacles define their boundaries with a single ``radius`` for a 2D "
"circle, or in case of 3D avoidance a sphere shape."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationobstacles.rst:42
msgid ""
"Dynamic obstacles can change their position every frame without additional "
"performance cost."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationobstacles.rst:43
msgid ""
"Dynamic obstacles with a set velocity can be predicted in their movement by "
"agents."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationobstacles.rst:44
msgid ""
"Dynamic obstacles are not a reliable way to constrain agents in crowded or "
"narrow spaces."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationobstacles.rst:46
msgid ""
"While both static and dynamic properties can be active at the same time on "
"the same obstacle this is not recommended for performance. Ideally when an "
"obstacle is moving the static vertices are removed and instead the radius "
"activated. When the obstacle reaches the new final position it should "
"gradually enlarge its radius to push all other agents away. With enough "
"created save space around the obstacle it should add the static vertices "
"again and remove the radius. This helps to avoid getting agents stuck in the "
"suddenly appearing static obstacle when the rebuild static boundary is "
"finished."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationobstacles.rst:49
msgid ""
"Similar to agents the obstacles can make use of the ``avoidance_layers`` "
"bitmask. All agents with a matching bit on their own avoidance mask will "
"avoid the obstacle."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationobstacles.rst:53
msgid "Procedural obstacles"
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationobstacles.rst:55
msgid ""
"New obstacles can be created without a Node directly on the NavigationServer."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationobstacles.rst:57
msgid ""
"Obstacles created with scripts require at least a ``map`` and a "
"``position``. For dynamic use a ``radius`` is required. For static use an "
"array of ``vertices`` is required."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationlinks.rst:4
#, fuzzy
msgid "Using NavigationLinks"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/navigation/navigation_using_navigationlinks.rst:8
msgid ""
"NavigationLinks are used to connect navigation mesh polygons from :ref:"
"`NavigationRegion2D<class_NavigationRegion2D>` and :ref:"
"`NavigationRegion3D<class_NavigationRegion3D>` over arbitrary distances for "
"pathfinding."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationlinks.rst:11
msgid ""
"NavigationLinks are also used to consider movement shortcuts in pathfinding "
"available through interacting with gameplay objects e.g. ladders, jump pads "
"or teleports."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationlinks.rst:14
msgid ""
"2D and 3D versions of NavigationJumplinks nodes are available as :ref:"
"`NavigationLink2D<class_NavigationLink2D>` and :ref:"
"`NavigationLink3D<class_NavigationLink3D>` respectively."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationlinks.rst:18
msgid ""
"Different NavigationRegions can connect their navigation meshes without the "
"need for a NavigationLink as long as they are within navigation map "
"``edge_connection_margin`` and have compatible ``navigation_layers``. As "
"soon as the distance becomes too large, building valid connections becomes a "
"problem - a problem that NavigationLinks can solve."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationlinks.rst:22
msgid ""
"See :ref:`doc_navigation_using_navigationregions` to learn more about the "
"use of navigation regions. See :ref:`doc_navigation_connecting_navmesh` to "
"learn more about how to connect navigation meshes."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationlinks.rst:27
msgid ""
"NavigationLinks share many properties with NavigationRegions like "
"``navigation_layers``. NavigationLinks add a single connection between two "
"positions over an arbitrary distance compared to NavigationRegions that add "
"a more local traversable area with a navigation mesh resource."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationlinks.rst:31
msgid ""
"NavigationLinks have a ``start_position`` and ``end_position`` and can go in "
"both directions when ``bidirectional`` is enabled. When placed a "
"navigationlink connects the navigation mesh polygons closest to its "
"``start_position`` and ``end_position`` within search radius for pathfinding."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationlinks.rst:34
msgid ""
"The polygon search radius can be configured globally in the ProjectSettings "
"under ``navigation/2d_or_3d/default_link_connection_radius`` or set for each "
"navigation **map** individually using the ``NavigationServer."
"map_set_link_connection_radius()`` function."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationlinks.rst:37
msgid ""
"Both ``start_position`` and ``end_position`` have debug markers in the "
"Editor. The visible radius of a position shows the polygon search radius. "
"All navigation mesh polygons inside are compared and the closest is picked "
"for the edge connection. If no valid polygon is found within the search "
"radius the navigation link gets disabled."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationlinks.rst:44
msgid ""
"The link debug visuals can be changed in the Editor :ref:"
"`ProjectSettings<class_ProjectSettings>` under ``debug/shapes/navigation``. "
"The visibility of the debug can also be controlled in the Editor 3D Viewport "
"gizmo menu."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationlinks.rst:49
msgid ""
"NavigationLinks do not move agents between the two link positions by "
"themselves."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationlinks.rst:51
msgid ""
"A navigation link does not provide any automated movement through the link. "
"Instead, when an agent reaches the position of a link, game code needs to "
"react (e.g. through area triggers) and provide means for the agent to move "
"through the link to end up at the links other position (e.g. through "
"teleport or animation) to continue along the path."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationlinks.rst:56
#, fuzzy
msgid "Navigation link script templates"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/navigation/navigation_using_navigationlinks.rst:58
msgid ""
"The following script uses the NavigationServer to create a new navigation "
"link."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationlayers.rst:4
#, fuzzy
msgid "Using NavigationLayers"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/navigation/navigation_using_navigationlayers.rst:6
msgid ""
"NavigationLayers are an optional feature to further control which navigation "
"meshes are considered in a path query and which regions can be connected. "
"They work similar to how physics layers control collision between collision "
"objects or how visual layers control what is rendered to the Viewport."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationlayers.rst:9
msgid ""
"NavigationLayers can be named in the **ProjectSettings** the same as physics "
"layers or visual layers."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationlayers.rst:13
msgid ""
"If two regions have not a single compatible layer they will not be merged by "
"the NavigationServer. See :ref:`doc_navigation_connecting_navmesh` for more "
"information on merging navigation meshes."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationlayers.rst:15
msgid ""
"If a region has not a single compatible navigation layer with the "
"``navigation_layers`` parameter of a path query this regions navigation mesh "
"will be skipped in pathfinding. See :ref:"
"`doc_navigation_using_navigationpaths` for more information on querying the "
"NavigationServer for paths."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationlayers.rst:18
msgid ""
"NavigationLayers are a single ``int`` value that is used as a **bitmask**. "
"Many navigation related nodes have ``set_navigation_layer_value()`` and "
"``get_navigation_layer_value()`` functions to set and get a layer number "
"directly without the need for more complex bitwise operations."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationlayers.rst:23
msgid ""
"In scripts the following helper functions can be used to work with the "
"``navigation_layers`` bitmask."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationlayers.rst:59
msgid ""
"Changing navigation layers for path queries is a performance friendly "
"alternative to enabling / disabling entire navigation regions. Compared to "
"region changes a navigation path query with different navigation layers does "
"not trigger large scale updates on the NavigationServer."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_using_navigationlayers.rst:64
msgid ""
"Changing the navigation layers of NavigationAgent nodes will have an "
"immediate effect on the next path query. Changing the navigation layers of "
"regions will have an immediate effect on the region but any new region "
"connect or disconnect will only be in effect after the next physics frame."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_debug_tools.rst:4
#, fuzzy
msgid "Navigation debug tools"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/navigation/navigation_debug_tools.rst:8
msgid ""
"The debug tools, properties and functions are only available in Godot debug "
"builds. Do not use any of them in code that will be part of a release build."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_debug_tools.rst:12
#, fuzzy
msgid "Enabling navigation debug"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/navigation/navigation_debug_tools.rst:14
msgid ""
"The navigation debug visualizations are enabled by default inside the "
"editor. To visualize navigation meshes and connections at runtime too, "
"enable the option **Visible Navigation** in the editor **Debug** menu."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_debug_tools.rst:19
msgid ""
"In Godot debug builds the navigation debug can also be toggled through the "
"NavigationServer singletons from scripts."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_debug_tools.rst:28
#, fuzzy
msgid "Navigation debug settings"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/navigation/navigation_debug_tools.rst:30
msgid ""
"The appearance of navigation debug can be changed in the ProjectSettings "
"under ``debug/shapes/navigation``. Certain debug features can also be "
"enabled or disabled at will but may require a scene restart to take effect."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_debug_tools.rst:36
#, fuzzy
msgid "Debug navigation mesh polygons"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/navigation/navigation_debug_tools.rst:38
msgid ""
"If ``enable_edge_lines`` is enabled, the edges of navigation mesh polygons "
"will be highlighted. If ``enable_edge_lines_xray`` is also enabled, the "
"edges of navigation meshes will be visible through geometry."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_debug_tools.rst:41
msgid ""
"If ``enable_geometry_face_random_color`` is enabled, the color of each "
"navigation mesh face will be mixed with a random color that is itself mixed "
"with the color specified in ``geometry_face_color``."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_debug_tools.rst:46
msgid "Debug edge connections"
msgstr ""

#: ../../docs/tutorials/navigation/navigation_debug_tools.rst:48
msgid ""
"When two navigation meshes are connected within ``edge_connection_margin`` "
"distance, the connection is overlaid. The color of the overlay is controlled "
"by ``edge_connection_color``. The connections can be made visible through "
"geometry with ``enable_edge_connections_xray``."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_debug_tools.rst:58
msgid "Edge connections are only visible when the NavigationServer is active."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_debug_tools.rst:61
#, fuzzy
msgid "Debug performance"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/navigation/navigation_debug_tools.rst:63
msgid ""
"To measure NavigationServer performance a dedicated monitor exists that can "
"be found within the Editor Debugger under *Debugger->Monitors->Navigation "
"Process*."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_debug_tools.rst:67
msgid ""
"Navigation Process shows how long the NavigationServer spends updating its "
"internals this update frame in milliseconds. Navigation Process works "
"similar to Process for visual frame rendering and Physics Process for "
"collision and fixed updates."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_debug_tools.rst:70
msgid ""
"Navigation Process accounts for all updates to **navigation maps**, "
"**navigation regions** and **navigation agents** as well as all the "
"**avoidance calculations** for the update frame."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_debug_tools.rst:74
msgid ""
"Navigation Process does NOT include pathfinding performance cause "
"pathfinding operates on the navigation map data independently from the "
"server process update."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_debug_tools.rst:76
msgid ""
"Navigation Process should be in general kept as low and as stable as "
"possible for runtime performance to avoid frame rate issues. Note that since "
"the NavigationServer process update happens in the middle of the physics "
"update an increase in Navigation Process will automatically increase Physics "
"Process by the same amount."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_debug_tools.rst:79
msgid ""
"Navigation also provides more detailed statistics about the current "
"navigation related objects and navigation map composition on the "
"NavigationServer."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_debug_tools.rst:83
msgid ""
"Navigation statistics shown here can not be judged as good or bad for "
"performance as it depends entirely on the project what can be considered as "
"reasonable or horribly excessive."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_debug_tools.rst:85
msgid ""
"Navigation statistics help with identifying performance bottlenecks that are "
"less obvious because the source might not always have a visible "
"representation. E.g. pathfinding performance issues created by overly "
"detailed navigation meshes with thousand of edges / polygons or problems "
"caused by procedural navigation gone wrong."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_connecting_navmesh.rst:4
#, fuzzy
msgid "Connecting navigation meshes"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/navigation/navigation_connecting_navmesh.rst:6
msgid ""
"Different NavigationMeshes are automatically merged by the NavigationServer "
"when at least two vertex positions of one edge exactly overlap."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_connecting_navmesh.rst:9
msgid ""
"To connect over arbitrary distances see :ref:"
"`doc_navigation_using_navigationlinks`."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_connecting_navmesh.rst:13
msgid ""
"The same is true for multiple NavigationPolygon resources. As long as their "
"outline points overlap exactly the NavigationServer will merge them. "
"NavigationPolygon outlines must be from different NavigationPolygon "
"resources to connect."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_connecting_navmesh.rst:17
msgid ""
"Overlapping or intersecting outlines on the same NavigationPolygon will fail "
"the navigation mesh creation. Overlapping or intersecting outlines from "
"different NavigationPolygons will often fail to create the navigation region "
"edge connections on the NavigationServer and should be avoided."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_connecting_navmesh.rst:26
msgid ""
"Exactly means exactly for the vertex position merge. Small float errors that "
"happen quite regularly with imported meshes will prevent a successful vertex "
"merge."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_connecting_navmesh.rst:29
msgid ""
"Alternatively navigation meshes are not merged but still considered as "
"**connected** by the NavigationServer when their edges are nearly parallel "
"and within distance to each other. The connection distance is defined by "
"the  ``edge_connection_margin`` for each navigation map. In many cases "
"navigation mesh edges cannot properly connect when they partly overlap. "
"Better avoid any navigation mesh overlap at all time for a consistent merge "
"behavior."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_connecting_navmesh.rst:37
msgid ""
"If navigation debug is enabled and the NavigationServer active the "
"established navigation mesh connections will be visualized. See :ref:"
"`doc_navigation_debug_tools` for more info about navigation debug options."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_connecting_navmesh.rst:40
msgid ""
"The default 2D ``edge_connection_margin`` can be changed in the "
"ProjectSettings under ``navigation/2d/default_edge_connection_margin``."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_connecting_navmesh.rst:42
msgid ""
"The default 3D ``edge_connection_margin`` can be changed in the "
"ProjectSettings under ``navigation/3d/default_edge_connection_margin``."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_connecting_navmesh.rst:44
msgid ""
"The edge connection margin value of any navigation map can also be changed "
"at runtime with the NavigationServer API."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_connecting_navmesh.rst:64
msgid ""
"Changing the edge connection margin will trigger a full update of all "
"navigation mesh connections on the NavigationServer."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_different_actor_types.rst:4
msgid "Support different actor types"
msgstr ""

#: ../../docs/tutorials/navigation/navigation_different_actor_types.rst:8
msgid ""
"To support different actor types due to e.g. their sizes each type requires "
"its own navigation map and navigation mesh baked with an appropriated agent "
"radius and height. The same approach can be used to distinguish between e.g. "
"landwalking, swimming or flying agents."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_different_actor_types.rst:14
msgid ""
"Agents are exclusively defined by a radius and height value for baking "
"navigation meshes, pathfinding and avoidance. More complex shapes are not "
"supported."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_different_actor_locomotion.rst:4
msgid "Support different actor locomotion"
msgstr ""

#: ../../docs/tutorials/navigation/navigation_different_actor_locomotion.rst:8
msgid ""
"To support different actor locomotion like crouching and crawling, a similar "
"map setup as supporting :ref:`doc_navigation_different_actor_types` is "
"required."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_different_actor_locomotion.rst:11
msgid ""
"Bake different navigation meshes with an appropriate height for crouched or "
"crawling actors so they can find paths through those narrow sections in your "
"game world."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_different_actor_locomotion.rst:14
msgid ""
"When an actor changes locomotion state, e.g. stands up, starts crouching or "
"crawling, query the appropriate map for a path."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_different_actor_locomotion.rst:17
msgid ""
"If the avoidance behavior should also change with the locomotion e.g. only "
"avoid while standing or only avoid other agents in the same locomotion "
"state, switch the actor's avoidance agent to another avoidance map with each "
"locomotion change."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_different_actor_locomotion.rst:43
msgid ""
"While a path query can be execute immediately for multiple maps, the "
"avoidance agent map switch will only take effect after the next server "
"synchronization."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_different_actor_area_access.rst:4
msgid "Support different actor area access"
msgstr ""

#: ../../docs/tutorials/navigation/navigation_different_actor_area_access.rst:8
msgid ""
"A typical example for different area access in gameplay are doors that "
"connect rooms with different navigation meshes and are not accessible by all "
"actors all the time."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_different_actor_area_access.rst:11
msgid ""
"Add a NavigationRegion at the door position. Add an appropriate navigation "
"mesh the size of the door that can connect with the surrounding navigation "
"meshes. In order to control access, enable / disable navigation layer bits "
"so path queries that use the same navigation layer bits can find a path "
"through the \"door\" navigation mesh."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_different_actor_area_access.rst:16
msgid ""
"The bitmask can act as a set of door keys or abilities and only actors with "
"at least one matching and enabled bit layer in their pathfinding query will "
"find a path through this region. See :ref:"
"`doc_navigation_advanced_using_navigationlayers` for more information on how "
"to work with navigation layers and the bitmask."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_different_actor_area_access.rst:22
msgid ""
"The entire \"door\" region can also be enabled / disable if required but if "
"disabled will block access for all path queries."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_different_actor_area_access.rst:24
msgid ""
"Prefer working with navigation layers in path queries whenever possible as "
"enabling or disabling navigation layers on a region triggers a costly "
"recalculation of the navigation map connections."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_different_actor_area_access.rst:29
msgid ""
"Changing navigation layers will only affect new path queries but not "
"automatically update existing paths."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_optimizing_performance.rst:4
msgid "Optimizing Navigation Performance"
msgstr ""

#: ../../docs/tutorials/navigation/navigation_optimizing_performance.rst:8
msgid ""
"Common Navigation related performance problems can be categorized into the "
"following topics:"
msgstr ""

#: ../../docs/tutorials/navigation/navigation_optimizing_performance.rst:10
msgid ""
"Performance problems with parsing scene tree nodes for navigation mesh "
"baking."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_optimizing_performance.rst:11
msgid "Performance problems with baking the actual navigation mesh."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_optimizing_performance.rst:12
msgid "Performance problems with NavigationAgent path queries."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_optimizing_performance.rst:13
msgid "Performance problems with the actual path search."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_optimizing_performance.rst:14
msgid "Performance problems with synchronizing the navigation map."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_optimizing_performance.rst:16
msgid ""
"In the following sections information can be found on how to identify and "
"fix or at least mitigate their impact on framerates."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_optimizing_performance.rst:19
msgid "Performance problems with parsing scene tree nodes"
msgstr ""

#: ../../docs/tutorials/navigation/navigation_optimizing_performance.rst:23
msgid ""
"Prefer using simple shapes with as few edges as possible e.g. nothing "
"rounded like a circle, sphere or torus."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_optimizing_performance.rst:25
msgid ""
"Prefer using physics collision shapes over complex visual meshes as source "
"geometry as meshes need to be copied from the GPU and are commonly much more "
"detailed than necessary."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_optimizing_performance.rst:27
msgid ""
"In general avoid using very complex geometry as source geometry for baking "
"navigation meshes. E.g. never use a very detailed visual mesh, as parsing "
"its shape to data arrays and voxelizing it for the navigation mesh baking "
"will take a long time for no real quality gain on the final navigation mesh. "
"Instead, use a very simplified level of detail version of a shape. Even "
"better, use very primitive shapes like boxes and rectangles that only "
"roughly cover the same geometry but still yield a baked result good enough "
"for pathfinding."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_optimizing_performance.rst:31
msgid ""
"Prefer using simple physics collision shapes over visual meshes, as the "
"source geometry for baking navigation meshes. Physics shapes are by default "
"very limited and optimized shapes that are easy and quick to parse. A visual "
"mesh on the other hand can range from simple to complex. On top, to gain "
"access to visual mesh data the parser needs to request the mesh data arrays "
"from the RenderingServer as visual mesh data is stored directly on the GPU "
"and is not cached on the CPU. This requires locking the RenderingServer "
"thread and can severely impact framerate at runtime while the rendering runs "
"multi-threaded. If the rendering runs single-threaded, the framerate impact "
"might be even worse and the mesh parsing might freeze the entire game for a "
"few seconds on complex meshes."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_optimizing_performance.rst:38
msgid "Performance problems with navigation mesh baking"
msgstr ""

#: ../../docs/tutorials/navigation/navigation_optimizing_performance.rst:42
msgid ""
"At runtime, always prefer to use a background thread for baking navigation "
"meshes."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_optimizing_performance.rst:44
msgid ""
"Increase NavigationMesh ``cell_size`` and ``cell_height`` to create less "
"voxels."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_optimizing_performance.rst:46
msgid ""
"Change the ``SamplePartitionType`` from watershed to monotone or layers to "
"gain baking performance."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_optimizing_performance.rst:49
msgid ""
"NEVER scale source geometry with nodes to avoid precision errors. Most scale "
"applies only visually and shapes that are very large at their base scale "
"require still a lot of extra processing even while downscaled."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_optimizing_performance.rst:51
msgid ""
"Baking navigation meshes at runtime should always be done in a background "
"thread if possible. Even small sized navigation meshes can take far longer "
"to bake than what is possible to squeeze into a single frame, at least if "
"the framerate should stay at a bearable level."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_optimizing_performance.rst:53
msgid ""
"Complexity of source geometry data parsed from scene tree nodes has big "
"impact on baking performance as everything needs to be mapped to a grid / "
"voxels. For runtime baking performance the NavigationMesh cell size and cell "
"height should be set as high as possible without causing navigation mesh "
"quality problems for a game. If cell size or cell height is set too low the "
"baking is forced to create an excessive amount of voxels to process the "
"source geometry. If the source geometry spans over a very large game world "
"it is even possible that the baking process runs out off memory in the "
"middle and crashes the game. The partition type can also be lowered "
"depending on how complex the games source geometry is to gain some "
"performance. E.g. games with mostly flat surfaces with blocky geometry can "
"get away with the monotone or layers mode that are a lot faster to bake (e."
"g. because they require no distance field pass)."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_optimizing_performance.rst:60
msgid ""
"Never scale source geometry with nodes. Not only can it result in a lot of "
"precision errors with wrongly matched vertices and edges but also some "
"scaling only exists as visuals and not in the actual parsed data. E.g. if a "
"mesh is downscaled visually in the Editor, e.g. the scale set to 0.001 on a "
"MeshInstance, the mesh still requires a gigantic and very complex voxel grid "
"to be processed for the baking."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_optimizing_performance.rst:64
msgid "Performance problems with NavigationAgent path queries"
msgstr ""

#: ../../docs/tutorials/navigation/navigation_optimizing_performance.rst:68
msgid ""
"Avoid unnecessary path resets and queries every frame in NavigationAgent "
"scripts."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_optimizing_performance.rst:70
msgid "Avoid updating all NavigationAgent paths in the same frame."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_optimizing_performance.rst:72
msgid ""
"Logical errors and wasteful operations in the custom NavigationAgent scripts "
"are very common causes of performance issues, e.g. watch out for resetting "
"the path every single frame. By default NavigationAgents are optimized to "
"only query new paths when the target position changes, the navigation map "
"changes or they are forced too far away from the desired path distance."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_optimizing_performance.rst:75
msgid ""
"E.g. when AI should move to the player, the target position should not be "
"set to the player position every single frame as this queries a new path "
"every frame. Instead, the distance from the current target position to the "
"player position should be compared and only when the player has moved too "
"far away a new target position should be set."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_optimizing_performance.rst:78
msgid ""
"Do not check beforehand if a target position is reachable every frame. What "
"looks like an innocent check is the equivalent of an expensive path query "
"behind the scene. If the plan is to request a new path anyway should the "
"position be reachable, a path should be queried directly. By looking at the "
"last position of the returned path and if that position is in a "
"\"reachable\" distance to the checked position it answers the \"is this "
"position reachable?\" question. This avoids doing the equivalent of two full "
"path queries every frame for the same NavigationAgent."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_optimizing_performance.rst:83
msgid ""
"Divide the total number of NavigationAgents into update groups or use random "
"timers so that they do not all request new paths in the same frame."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_optimizing_performance.rst:86
msgid "Performance problems with the actual path search"
msgstr ""

#: ../../docs/tutorials/navigation/navigation_optimizing_performance.rst:90
msgid ""
"Optimize overdetailed navigation meshes by reducing the amount of polygons "
"and edges."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_optimizing_performance.rst:92
msgid ""
"The cost of the actual path search correlates directly with the amount of "
"navigation mesh polygons and edges and not the real size of a game world. If "
"a giant game world uses very optimized navigation meshes with only few "
"polygons that cover large areas, performance should be acceptable. If the "
"game world is splintered into very small navigation meshes that each have "
"tiny polygons (like for TileMaps) pathfinding performance will be reduced."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_optimizing_performance.rst:96
msgid ""
"A common problem is a sudden performance drop when a target position is not "
"reachable in a path query. This performance drop is \"normal\" and the "
"result of a too large, too unoptimized navigation mesh with way to much "
"polygons and edges to search through. In normal path searches where the "
"target position can be reached quickly the pathfinding will do an early exit "
"as soon as the position is reached which can hide this lack of optimization "
"for a while. If the target position can not be reached the pathfinding has "
"to do a far longer search through the available polygons to confirm that the "
"position is absolutely not reachable."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_optimizing_performance.rst:102
msgid "Performance problems with navigation map synchronization"
msgstr ""

#: ../../docs/tutorials/navigation/navigation_optimizing_performance.rst:106
msgid ""
"Merge navigation meshes polygons by vertex instead of by edge connection "
"wherever possible."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_optimizing_performance.rst:108
msgid ""
"When changes are made to e.g. navigation meshes or navigation regions, the "
"NavigationServer needs to synchronize the navigation map. Depending on the "
"complexity of navigation meshes, this can take a significant amount of time "
"which may impact the framerate."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_optimizing_performance.rst:111
msgid ""
"The NavigationServer merges navigation meshes either by vertex or by edge "
"connection. The merge by vertex happens when the two vertex of two different "
"edges land in the same map grid cells. This is a rather quick and low-cost "
"operation. The merge by edge connection happens in a second pass for all "
"still unmerged edges. All the free edges are checked for possible edge "
"connections by both distance and angle which is rather costly."
msgstr ""

#: ../../docs/tutorials/navigation/navigation_optimizing_performance.rst:115
msgid ""
"So apart from the general rule to have as few polygon edges as possible, as "
"many edges as possible should be merged by vertex upfront so only a few "
"edges are left for the more costly edge connection calculation. The debug "
"Navigation PerformanceMonitor can be used to get statistics on how many "
"polygons and edges are available and how many of them are unmerged or not "
"merged by vertex. If the ratio between vertex merged and edge connections is "
"way off (vertex should be significantly higher) the navigation meshes are "
"properly created or placed very inefficient."
msgstr ""

#: ../../docs/tutorials/networking/high_level_multiplayer.rst:4
msgid "High-level multiplayer"
msgstr ""

#: ../../docs/tutorials/networking/high_level_multiplayer.rst:7
msgid "High-level vs low-level API"
msgstr ""

#: ../../docs/tutorials/networking/high_level_multiplayer.rst:9
msgid ""
"The following explains the differences of high- and low-level networking in "
"Godot as well as some fundamentals. If you want to jump in head-first and "
"add networking to your first nodes, skip to `Initializing the network`_ "
"below. But make sure to read the rest later on!"
msgstr ""

#: ../../docs/tutorials/networking/high_level_multiplayer.rst:11
msgid ""
"Godot always supported standard low-level networking via :abbr:`UDP (User "
"Datagram Protocol)`, :abbr:`TCP (Transmission Control Protocol)` and some "
"higher-level protocols such as :abbr:`HTTP (Hypertext Transfer Protocol)` "
"and :abbr:`SSL (Secure Sockets Layer)`. These protocols are flexible and can "
"be used for almost anything. However, using them to synchronize game state "
"manually can be a large amount of work. Sometimes that work can't be avoided "
"or is worth it, for example when working with a custom server implementation "
"on the backend. But in most cases, it's worthwhile to consider Godot's high-"
"level networking API, which sacrifices some of the fine-grained control of "
"low-level networking for greater ease of use."
msgstr ""

#: ../../docs/tutorials/networking/high_level_multiplayer.rst:14
msgid "This is due to the inherent limitations of the low-level protocols:"
msgstr ""

#: ../../docs/tutorials/networking/high_level_multiplayer.rst:16
msgid ""
"TCP ensures packets will always arrive reliably and in order, but latency is "
"generally higher due to error correction. It's also quite a complex protocol "
"because it understands what a \"connection\" is, and optimizes for goals "
"that often don't suit applications like multiplayer games. Packets are "
"buffered to be sent in larger batches, trading less per-packet overhead for "
"higher latency. This can be useful for things like HTTP, but generally not "
"for games. Some of this can be configured and disabled (e.g. by disabling "
"\"Nagle's algorithm\" for the TCP connection)."
msgstr ""

#: ../../docs/tutorials/networking/high_level_multiplayer.rst:18
msgid ""
"UDP is a simpler protocol, which only sends packets (and has no concept of a "
"\"connection\"). No error correction makes it pretty quick (low latency), "
"but packets may be lost along the way or received in the wrong order. Added "
"to that, the MTU (maximum packet size) for UDP is generally low (only a few "
"hundred bytes), so transmitting larger packets means splitting them, "
"reorganizing them and retrying if a part fails."
msgstr ""

#: ../../docs/tutorials/networking/high_level_multiplayer.rst:23
msgid ""
"In general, TCP can be thought of as reliable, ordered, and slow; UDP as "
"unreliable, unordered and fast. Because of the large difference in "
"performance, it often makes sense to re-build the parts of TCP wanted for "
"games (optional reliability and packet order), while avoiding the unwanted "
"parts (congestion/traffic control features, Nagle's algorithm, etc). Due to "
"this, most game engines come with such an implementation, and Godot is no "
"exception."
msgstr ""

#: ../../docs/tutorials/networking/high_level_multiplayer.rst:26
msgid ""
"In summary, you can use the low-level networking API for maximum control and "
"implement everything on top of bare network protocols or use the high-level "
"API based on :ref:`SceneTree <class_SceneTree>` that does most of the heavy "
"lifting behind the scenes in a generally optimized way."
msgstr ""

#: ../../docs/tutorials/networking/high_level_multiplayer.rst:28
msgid ""
"Most of Godot's supported platforms offer all or most of the mentioned high- "
"and low-level networking features. As networking is always largely hardware "
"and operating system dependent, however, some features may change or not be "
"available on some target platforms. Most notably, the HTML5 platform "
"currently offers WebSockets and WebRTC support but lacks some of the higher-"
"level features, as well as raw access to low-level protocols like TCP and "
"UDP."
msgstr ""

#: ../../docs/tutorials/networking/high_level_multiplayer.rst:34
msgid ""
"More about TCP/IP, UDP, and networking: https://gafferongames.com/post/"
"udp_vs_tcp/"
msgstr ""

#: ../../docs/tutorials/networking/high_level_multiplayer.rst:37
msgid ""
"Gaffer On Games has a lot of useful articles about networking in Games "
"(`here <https://gafferongames.com/categories/game-networking/>`__), "
"including the comprehensive `introduction to networking models in games "
"<https://gafferongames.com/post/"
"what_every_programmer_needs_to_know_about_game_networking/>`__."
msgstr ""

#: ../../docs/tutorials/networking/high_level_multiplayer.rst:41
msgid ""
"Adding networking to your game comes with some responsibility. It can make "
"your application vulnerable if done wrong and may lead to cheats or "
"exploits. It may even allow an attacker to compromise the machines your "
"application runs on and use your servers to send spam, attack others or "
"steal your users' data if they play your game."
msgstr ""

#: ../../docs/tutorials/networking/high_level_multiplayer.rst:46
msgid ""
"This is always the case when networking is involved and has nothing to do "
"with Godot. You can of course experiment, but when you release a networked "
"application, always take care of any possible security concerns."
msgstr ""

#: ../../docs/tutorials/networking/high_level_multiplayer.rst:51
msgid "Mid-level abstraction"
msgstr ""

#: ../../docs/tutorials/networking/high_level_multiplayer.rst:53
msgid ""
"Before going into how we would like to synchronize a game across the "
"network, it can be helpful to understand how the base network API for "
"synchronization works."
msgstr ""

#: ../../docs/tutorials/networking/high_level_multiplayer.rst:55
msgid ""
"Godot uses a mid-level object :ref:`MultiplayerPeer "
"<class_MultiplayerPeer>`. This object is not meant to be created directly, "
"but is designed so that several C++ implementations can provide it."
msgstr ""

#: ../../docs/tutorials/networking/high_level_multiplayer.rst:58
msgid ""
"This object extends from :ref:`PacketPeer <class_PacketPeer>`, so it "
"inherits all the useful methods for serializing, sending and receiving data. "
"On top of that, it adds methods to set a peer, transfer mode, etc. It also "
"includes signals that will let you know when peers connect or disconnect."
msgstr ""

#: ../../docs/tutorials/networking/high_level_multiplayer.rst:60
msgid ""
"This class interface can abstract most types of network layers, topologies "
"and libraries. By default, Godot provides an implementation based on ENet (:"
"ref:`ENetMultiplayerPeer <class_ENetMultiplayerPeer>`), one based on WebRTC "
"(:ref:`WebRTCMultiplayerPeer <class_WebRTCMultiplayerPeer>`), and one based "
"on WebSocket (:ref:`WebSocketPeer <class_WebSocketPeer>`), but this could be "
"used to implement mobile APIs (for ad hoc WiFi, Bluetooth) or custom device/"
"console-specific networking APIs."
msgstr ""

#: ../../docs/tutorials/networking/high_level_multiplayer.rst:66
msgid ""
"For most common cases, using this object directly is discouraged, as Godot "
"provides even higher level networking facilities. This object is still made "
"available in case a game has specific needs for a lower-level API."
msgstr ""

#: ../../docs/tutorials/networking/high_level_multiplayer.rst:70
#, fuzzy
msgid "Hosting considerations"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/networking/high_level_multiplayer.rst:72
msgid ""
"When hosting a server, clients on your :abbr:`LAN (Local Area Network)` can "
"connect using the internal IP address which is usually of the form ``192.168."
"*.*``. This internal IP address is **not** reachable by non-LAN/Internet "
"clients."
msgstr ""

#: ../../docs/tutorials/networking/high_level_multiplayer.rst:77
msgid ""
"On Windows, you can find your internal IP address by opening a command "
"prompt and entering ``ipconfig``. On macOS, open a Terminal and enter "
"``ifconfig``. On Linux, open a terminal and enter ``ip addr``."
msgstr ""

#: ../../docs/tutorials/networking/high_level_multiplayer.rst:81
msgid ""
"If you're hosting a server on your own machine and want non-LAN clients to "
"connect to it, you'll probably have to *forward* the server port on your "
"router. This is required to make your server reachable from the Internet "
"since most residential connections use a `NAT <https://en.wikipedia.org/wiki/"
"Network_address_translation>`__. Godot's high-level multiplayer API only "
"uses UDP, so you must forward the port in UDP, not just TCP."
msgstr ""

#: ../../docs/tutorials/networking/high_level_multiplayer.rst:89
msgid ""
"After forwarding an UDP port and making sure your server uses that port, you "
"can use `this website <https://icanhazip.com/>`__ to find your public IP "
"address. Then give this public IP address to any Internet clients that wish "
"to connect to your server."
msgstr ""

#: ../../docs/tutorials/networking/high_level_multiplayer.rst:94
msgid ""
"Godot's high-level multiplayer API uses a modified version of ENet which "
"allows for full IPv6 support."
msgstr ""

#: ../../docs/tutorials/networking/high_level_multiplayer.rst:98
msgid "Initializing the network"
msgstr ""

#: ../../docs/tutorials/networking/high_level_multiplayer.rst:100
msgid ""
"High level networking in Godot is managed by the :ref:`SceneTree "
"<class_SceneTree>`."
msgstr ""

#: ../../docs/tutorials/networking/high_level_multiplayer.rst:102
msgid ""
"Each node has a ``multiplayer`` property, which is a reference to the "
"``MultiplayerAPI`` instance configured for it by the scene tree. Initially, "
"every node is configured with the same default ``MultiplayerAPI`` object."
msgstr ""

#: ../../docs/tutorials/networking/high_level_multiplayer.rst:105
msgid ""
"It is possible to create a new ``MultiplayerAPI`` object and assign it to a "
"``NodePath`` in the the scene tree, which will override ``multiplayer`` for "
"the node at that path and all of its descendants. This allows sibling nodes "
"to be configured with different peers, which makes it possible to run a "
"server and a client simultaneously in one instance of Godot."
msgstr ""

#: ../../docs/tutorials/networking/high_level_multiplayer.rst:116
msgid ""
"To initialize networking, a ``MultiplayerPeer`` object must be created, "
"initialized as a server or client, and passed to the ``MultiplayerAPI``."
msgstr ""

#: ../../docs/tutorials/networking/high_level_multiplayer.rst:131
msgid "To terminate networking:"
msgstr ""

#: ../../docs/tutorials/networking/high_level_multiplayer.rst:139
#: ../../docs/tutorials/networking/http_client_class.rst:14
#: ../../docs/tutorials/networking/websocket.rst:27
#: ../../docs/tutorials/networking/webrtc.rst:44
msgid ""
"When exporting to Android, make sure to enable the ``INTERNET`` permission "
"in the Android export preset before exporting the project or using one-click "
"deploy. Otherwise, network communication of any kind will be blocked by "
"Android."
msgstr ""

#: ../../docs/tutorials/networking/high_level_multiplayer.rst:145
msgid "Managing connections"
msgstr ""

#: ../../docs/tutorials/networking/high_level_multiplayer.rst:147
msgid ""
"Every peer is assigned a unique ID. The server's ID is always 1, and clients "
"are assigned a random positive integer."
msgstr ""

#: ../../docs/tutorials/networking/high_level_multiplayer.rst:149
msgid ""
"Responding to connections or disconnections is possible by connecting to "
"``MultiplayerAPI``'s signals:"
msgstr ""

#: ../../docs/tutorials/networking/high_level_multiplayer.rst:151
msgid ""
"``peer_connected(id: int)`` This signal is emitted with the newly connected "
"peer's ID on each other peer, and on the new peer multiple times, once with "
"each other peer's ID."
msgstr ""

#: ../../docs/tutorials/networking/high_level_multiplayer.rst:152
msgid ""
"``peer_disconnected(id: int)`` This signal is emitted on every remaining "
"peer when one disconnects."
msgstr ""

#: ../../docs/tutorials/networking/high_level_multiplayer.rst:154
msgid "The rest are only emitted on clients:"
msgstr ""

#: ../../docs/tutorials/networking/high_level_multiplayer.rst:156
msgid "``connected_to_server()``"
msgstr ""

#: ../../docs/tutorials/networking/high_level_multiplayer.rst:157
msgid "``connection_failed()``"
msgstr ""

#: ../../docs/tutorials/networking/high_level_multiplayer.rst:158
msgid "``server_disconnected()``"
msgstr ""

#: ../../docs/tutorials/networking/high_level_multiplayer.rst:160
msgid "To get the unique ID of the associated peer:"
msgstr ""

#: ../../docs/tutorials/networking/high_level_multiplayer.rst:166
msgid "To check whether the peer is server or client:"
msgstr ""

#: ../../docs/tutorials/networking/high_level_multiplayer.rst:173
msgid "Remote procedure calls"
msgstr ""

#: ../../docs/tutorials/networking/high_level_multiplayer.rst:175
msgid ""
"Remote procedure calls, or RPCs, are functions that can be called on other "
"peers. To create one, use the ``@rpc`` annotation before a function "
"definition. To call an RPC, use ``Callable``'s method ``rpc()`` to call in "
"every peer, or ``rpc_id()`` to call in a specific peer."
msgstr ""

#: ../../docs/tutorials/networking/high_level_multiplayer.rst:189
msgid "RPCs will not serialize objects or callables."
msgstr ""

#: ../../docs/tutorials/networking/high_level_multiplayer.rst:191
msgid ""
"For a remote call to be successful, the sending and receiving node need to "
"have the same ``NodePath``, which means they must have the same name. When "
"using ``add_child()`` for nodes which are expected to use RPCs, set the "
"argument ``force_readable_name`` to ``true``."
msgstr ""

#: ../../docs/tutorials/networking/high_level_multiplayer.rst:197
msgid ""
"If a function is annotated with ``@rpc`` on the client script (resp. server "
"script), then this function must also be declared on the server script "
"(resp. client script). Both RPCs must have the same signature which is "
"evaluated with a checksum of **all RPCs**. All RPCs in a script are checked "
"at once, and all RPCs must be declared on both the client scripts and the "
"server scripts, **even functions that are currently not in use**."
msgstr ""

#: ../../docs/tutorials/networking/high_level_multiplayer.rst:203
msgid ""
"The signature of the RPC includes the ``@rpc()`` declaration, the function, "
"return type, AND the nodepath. If an RPC resides in a script attached to ``/"
"root/Main/Node1``, then it must reside in precisely the same path and node "
"on both the client script and the server script. Function arguments "
"(example: ``func sendstuff():`` and ``func sendstuff(arg1, arg2):`` **will "
"pass** signature matching)."
msgstr ""

#: ../../docs/tutorials/networking/high_level_multiplayer.rst:209
msgid ""
"If these conditions are not met (if all RPCs do not pass signature "
"matching), the script may print an error or cause unwanted behavior. The "
"error message may be unrelated to the RPC function you are currently "
"building and testing."
msgstr ""

#: ../../docs/tutorials/networking/high_level_multiplayer.rst:213
msgid ""
"See further explanation and troubleshooting on `this post <https://github."
"com/godotengine/godot/issues/57869#issuecomment-1034215138>`__."
msgstr ""

#: ../../docs/tutorials/networking/high_level_multiplayer.rst:215
msgid ""
"The annotation can take a number of arguments, which have default values. "
"``@rpc`` is equivalent to:"
msgstr ""

#: ../../docs/tutorials/networking/high_level_multiplayer.rst:221
msgid "The parameters and their functions are as follows:"
msgstr ""

#: ../../docs/tutorials/networking/high_level_multiplayer.rst:223
msgid "``mode``:"
msgstr ""

#: ../../docs/tutorials/networking/high_level_multiplayer.rst:225
msgid ""
"``\"authority\"``: Only the multiplayer authority (the server) can call "
"remotely."
msgstr ""

#: ../../docs/tutorials/networking/high_level_multiplayer.rst:226
msgid ""
"``\"any_peer\"``: Clients are allowed to call remotely. Useful for "
"transferring user input."
msgstr ""

#: ../../docs/tutorials/networking/high_level_multiplayer.rst:228
msgid "``sync``:"
msgstr ""

#: ../../docs/tutorials/networking/high_level_multiplayer.rst:230
msgid "``\"call_remote\"``: The function will not be called on the local peer."
msgstr ""

#: ../../docs/tutorials/networking/high_level_multiplayer.rst:231
msgid ""
"``\"call_local\"``: The function can be called on the local peer. Useful "
"when the server is also a player."
msgstr ""

#: ../../docs/tutorials/networking/high_level_multiplayer.rst:233
msgid "``transfer_mode``:"
msgstr ""

#: ../../docs/tutorials/networking/high_level_multiplayer.rst:235
msgid ""
"``\"unreliable\"`` Packets are not acknowledged, can be lost, and can arrive "
"at any order."
msgstr ""

#: ../../docs/tutorials/networking/high_level_multiplayer.rst:236
msgid ""
"``\"unreliable_ordered\"`` Packets are received in the order they were sent "
"in. This is achieved by ignoring packets that arrive later if another that "
"was sent after them has already been received. Can cause packet loss if used "
"incorrectly."
msgstr ""

#: ../../docs/tutorials/networking/high_level_multiplayer.rst:237
msgid ""
"``\"reliable\"`` Resend attempts are sent until packets are acknowledged, "
"and their order is preserved. Has a significant performance penalty."
msgstr ""

#: ../../docs/tutorials/networking/high_level_multiplayer.rst:239
msgid "``transfer_channel`` is the channel index."
msgstr ""

#: ../../docs/tutorials/networking/high_level_multiplayer.rst:241
msgid ""
"The first 3 can be passed in any order, but ``transfer_channel`` must always "
"be last."
msgstr ""

#: ../../docs/tutorials/networking/high_level_multiplayer.rst:243
msgid ""
"The function ``multiplayer.get_remote_sender_id()`` can be used to get the "
"unique id of an rpc sender, when used within the function called by rpc."
msgstr ""

#: ../../docs/tutorials/networking/high_level_multiplayer.rst:259
#, fuzzy
msgid "Channels"
msgstr "Zajednica"

#: ../../docs/tutorials/networking/high_level_multiplayer.rst:260
msgid ""
"Modern networking protocols support channels, which are separate connections "
"within the connection. This allows for multiple streams of packets that do "
"not interfere with each other."
msgstr ""

#: ../../docs/tutorials/networking/high_level_multiplayer.rst:263
msgid ""
"For example, game chat related messages and some of the core gameplay "
"messages should all be sent reliably, but a gameplay message should not wait "
"for a chat message to be acknowledged. This can be achieved by using "
"different channels."
msgstr ""

#: ../../docs/tutorials/networking/high_level_multiplayer.rst:266
msgid ""
"Channels are also useful when used with the unreliable ordered transfer "
"mode. Sending packets of variable size with this transfer mode can cause "
"packet loss, since packets which are slower to arrive are ignored. "
"Separating them into multiple streams of homogeneous packets by using "
"channels allows ordered transfer with little packet loss, and without the "
"latency penalty caused by reliable mode."
msgstr ""

#: ../../docs/tutorials/networking/high_level_multiplayer.rst:270
msgid ""
"The default channel with index 0 is actually three different channels - one "
"for each transfer mode."
msgstr ""

#: ../../docs/tutorials/networking/high_level_multiplayer.rst:273
msgid "Example lobby implementation"
msgstr ""

#: ../../docs/tutorials/networking/high_level_multiplayer.rst:275
msgid ""
"This is an example lobby that can handle peers joining and leaving, notify "
"UI scenes through signals, and start the game after all clients have loaded "
"the game scene."
msgstr ""

#: ../../docs/tutorials/networking/high_level_multiplayer.rst:390
msgid ""
"The game scene's root node should be named Game. In the script attached to "
"it:"
msgstr ""

#: ../../docs/tutorials/networking/high_level_multiplayer.rst:411
msgid ""
"Once you've made a multiplayer game, you may want to export it to run it on "
"a dedicated server with no GPU available. See :ref:"
"`doc_exporting_for_dedicated_servers` for more information."
msgstr ""

#: ../../docs/tutorials/networking/high_level_multiplayer.rst:417
msgid ""
"The code samples on this page aren't designed to run on a dedicated server. "
"You'll have to modify them so the server isn't considered to be a player. "
"You'll also have to modify the game starting mechanism so that the first "
"player who joins can start the game."
msgstr ""

#: ../../docs/tutorials/networking/http_request_class.rst:4
msgid "Making HTTP requests"
msgstr ""

#: ../../docs/tutorials/networking/http_request_class.rst:7
msgid "Why use HTTP?"
msgstr ""

#: ../../docs/tutorials/networking/http_request_class.rst:9
msgid ""
"`HTTP requests <https://developer.mozilla.org/en-US/docs/Web/HTTP>`_ are "
"useful to communicate with web servers and other non-Godot programs."
msgstr ""

#: ../../docs/tutorials/networking/http_request_class.rst:12
msgid ""
"Compared to Godot's other networking features (like :ref:`High-level "
"multiplayer <doc_high_level_multiplayer>`), HTTP requests have more overhead "
"and take more time to get going, so they aren't suited for real-time "
"communication, and aren't great to send lots of small updates as is common "
"for multiplayer gameplay."
msgstr ""

#: ../../docs/tutorials/networking/http_request_class.rst:18
msgid ""
"HTTP, however, offers interoperability with external web resources and is "
"great at sending and receiving large amounts of data, for example to "
"transfer files like game assets. These assets can then be loaded using :ref:"
"`runtime file loading and saving <doc_runtime_loading_and_saving>`."
msgstr ""

#: ../../docs/tutorials/networking/http_request_class.rst:24
msgid ""
"So HTTP may be useful for your game's login system, lobby browser, to "
"retrieve some information from the web or to download game assets."
msgstr ""

#: ../../docs/tutorials/networking/http_request_class.rst:27
msgid ""
"This tutorial assumes some familiarity with Godot and the Godot Editor. "
"Refer to the :ref:`Introduction <toc-learn-introduction>` and the :ref:`Step "
"by step <toc-learn-step_by_step>` tutorial, especially its :ref:`Nodes and "
"Scenes <doc_nodes_and_scenes>` and :ref:`Creating your first script "
"<doc_scripting_first_script>` pages if needed."
msgstr ""

#: ../../docs/tutorials/networking/http_request_class.rst:34
msgid "HTTP requests in Godot"
msgstr ""

#: ../../docs/tutorials/networking/http_request_class.rst:36
msgid ""
"The :ref:`HTTPRequest <class_HTTPRequest>` node is the easiest way to make "
"HTTP requests in Godot. It is backed by the more low-level :ref:`HTTPClient "
"<class_HTTPClient>`, for which a tutorial is available :ref:`here "
"<doc_http_client_class>`."
msgstr ""

#: ../../docs/tutorials/networking/http_request_class.rst:40
msgid ""
"For this example, we will make an HTTP request to GitHub to retrieve the "
"name of the latest Godot release."
msgstr ""

#: ../../docs/tutorials/networking/http_request_class.rst:45
msgid ""
"When exporting to **Android**, make sure to enable the **Internet** "
"permission in the Android export preset before exporting the project or "
"using one-click deploy. Otherwise, network communication of any kind will be "
"blocked by the Android OS."
msgstr ""

#: ../../docs/tutorials/networking/http_request_class.rst:51
#, fuzzy
msgid "Preparing the scene"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/networking/http_request_class.rst:53
msgid ""
"Create a new empty scene, add a root :ref:`Node <class_Node>` and add a "
"script to it. Then add a :ref:`HTTPRequest <class_HTTPRequest>` node as a "
"child."
msgstr ""

#: ../../docs/tutorials/networking/http_request_class.rst:59
#, fuzzy
msgid "Scripting the request"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/networking/http_request_class.rst:61
msgid ""
"When the project is started (so in ``_ready()``), we're going to send an "
"HTTP request to Github using our :ref:`HTTPRequest <class_HTTPRequest>` "
"node, and once the request completes, we're going to parse the returned JSON "
"data, look for the ``name`` field and print that to console."
msgstr ""

#: ../../docs/tutorials/networking/http_request_class.rst:101
msgid ""
"Save the script and the scene, and run the project. The name of the most "
"recent Godot release on Github should be printed to the output log. For more "
"information on parsing JSON, see the class references for :ref:`JSON "
"<class_JSON>`."
msgstr ""

#: ../../docs/tutorials/networking/http_request_class.rst:105
msgid ""
"Note that you may want to check whether the ``result`` equals "
"``RESULT_SUCCESS`` and whether a JSON parsing error occurred, see the JSON "
"class reference and :ref:`HTTPRequest <class_HTTPRequest>` for more."
msgstr ""

#: ../../docs/tutorials/networking/http_request_class.rst:109
msgid ""
"You have to wait for a request to finish before sending another one. Making "
"multiple request at once requires you to have one node per request. A common "
"strategy is to create and delete HTTPRequest nodes at runtime as necessary."
msgstr ""

#: ../../docs/tutorials/networking/http_request_class.rst:114
msgid "Sending data to the server"
msgstr ""

#: ../../docs/tutorials/networking/http_request_class.rst:116
msgid ""
"Until now, we have limited ourselves to requesting data from a server. But "
"what if you need to send data to the server? Here is a common way of doing "
"it:"
msgstr ""

#: ../../docs/tutorials/networking/http_request_class.rst:135
#, fuzzy
msgid "Setting custom HTTP headers"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/networking/http_request_class.rst:137
msgid ""
"Of course, you can also set custom HTTP headers. These are given as a string "
"array, with each string containing a header in the format ``\"header: "
"value\"``. For example, to set a custom user agent (the HTTP ``User-Agent`` "
"header) you could use the following:"
msgstr ""

#: ../../docs/tutorials/networking/http_request_class.rst:154
msgid ""
"Be aware that someone might analyse and decompile your released application "
"and thus may gain access to any embedded authorization information like "
"tokens, usernames or passwords. That means it is usually not a good idea to "
"embed things such as database access credentials inside your game. Avoid "
"providing information useful to an attacker whenever possible."
msgstr ""

#: ../../docs/tutorials/networking/http_client_class.rst:6
msgid "HTTP client class"
msgstr ""

#: ../../docs/tutorials/networking/http_client_class.rst:8
msgid ""
":ref:`HTTPClient <class_HTTPClient>` provides low-level access to HTTP "
"communication. For a higher-level interface, you may want to take a look at :"
"ref:`HTTPRequest <class_HTTPRequest>` first, which has a tutorial available :"
"ref:`here <doc_http_request_class>`."
msgstr ""

#: ../../docs/tutorials/networking/http_client_class.rst:19
msgid ""
"Here's an example of using the :ref:`HTTPClient <class_HTTPClient>` class. "
"It's just a script, so it can be run by executing:"
msgstr ""

#: ../../docs/tutorials/networking/http_client_class.rst:32
msgid "It will connect and fetch a website."
msgstr ""

#: ../../docs/tutorials/networking/ssl_certificates.rst:6
msgid "SSL certificates"
msgstr ""

#: ../../docs/tutorials/networking/ssl_certificates.rst:11
msgid ""
"It is often desired to use SSL connections for communications to avoid \"man "
"in the middle\" attacks. Godot has a connection wrapper, :ref:`StreamPeerTLS "
"<class_StreamPeerTLS>`, which can take a regular connection and add security "
"around it. The :ref:`HTTPClient <class_HTTPClient>` class also supports "
"HTTPS by using this same wrapper."
msgstr ""

#: ../../docs/tutorials/networking/ssl_certificates.rst:18
msgid ""
"Godot includes SSL certificates from Mozilla, but you can provide your own "
"with a .crt file in the project settings:"
msgstr ""

#: ../../docs/tutorials/networking/ssl_certificates.rst:23
msgid ""
"This file should contain any number of public certificates in `PEM format "
"<https://en.wikipedia.org/wiki/Privacy-enhanced_Electronic_Mail>`__."
msgstr ""

#: ../../docs/tutorials/networking/ssl_certificates.rst:26
msgid ""
"Of course, remember to add .crt as filter so the exporter recognizes this "
"when exporting your project."
msgstr ""

#: ../../docs/tutorials/networking/ssl_certificates.rst:31
msgid "There are two ways to obtain certificates:"
msgstr ""

#: ../../docs/tutorials/networking/ssl_certificates.rst:34
msgid "Approach 1: self signed cert"
msgstr ""

#: ../../docs/tutorials/networking/ssl_certificates.rst:36
msgid ""
"The first approach is the simplest: generate a private and public key pair "
"and add the public key (in PEM format) to the .crt file. The private key "
"should go to your server."
msgstr ""

#: ../../docs/tutorials/networking/ssl_certificates.rst:40
msgid ""
"OpenSSL has `some documentation <https://raw.githubusercontent.com/openssl/"
"openssl/master/doc/HOWTO/keys.txt>`__ about this. This approach also **does "
"not require domain validation** nor requires you to spend a considerable "
"amount of money in purchasing certificates from a CA."
msgstr ""

#: ../../docs/tutorials/networking/ssl_certificates.rst:47
msgid "Approach 2: CA cert"
msgstr ""

#: ../../docs/tutorials/networking/ssl_certificates.rst:49
msgid ""
"The second approach consists of using a certificate authority (CA) such as "
"Verisign, Geotrust, etc. This is a more cumbersome process, but it's more "
"\"official\" and ensures your identity is clearly represented."
msgstr ""

#: ../../docs/tutorials/networking/ssl_certificates.rst:54
msgid ""
"Unless you are working with large companies or corporations, or need to "
"connect to someone else's servers (i.e., connecting to Google or some other "
"REST API provider via HTTPS), this method is not as useful."
msgstr ""

#: ../../docs/tutorials/networking/ssl_certificates.rst:58
msgid ""
"Also, when using a CA issued cert, **you must enable domain validation**, to "
"ensure the domain you are connecting to is the one intended, otherwise any "
"website can issue any certificate in the same CA and it will work."
msgstr ""

#: ../../docs/tutorials/networking/ssl_certificates.rst:63
msgid ""
"If you are using Linux, you can use the supplied certs file, generally "
"located in:"
msgstr ""

#: ../../docs/tutorials/networking/ssl_certificates.rst:70
msgid ""
"This file allows HTTPS connections to virtually any website (i.e., Google, "
"Microsoft, etc.)."
msgstr ""

#: ../../docs/tutorials/networking/ssl_certificates.rst:73
msgid ""
"Or pick any of the more specific certificates there if you are connecting to "
"a specific one."
msgstr ""

#: ../../docs/tutorials/networking/websocket.rst:6
#: ../../docs/tutorials/networking/webrtc.rst:16
msgid "WebSocket"
msgstr ""

#: ../../docs/tutorials/networking/websocket.rst:9
msgid "HTML5 and WebSocket"
msgstr ""

#: ../../docs/tutorials/networking/websocket.rst:11
msgid ""
"The WebSocket protocol was standardized in 2011 with the original goal of "
"allowing browsers to create stable and bidirectional connections with a "
"server. Before that, browsers used to only support HTTPRequests, which is "
"not well-suited for bidirectional communication."
msgstr ""

#: ../../docs/tutorials/networking/websocket.rst:14
msgid ""
"The protocol is message based and a very powerful tool to send push "
"notifications to browsers, and has been used to implement chats, turn-based "
"games, etc. It still uses a TCP connection, which is good for reliability "
"but not for latency, so not good for real-time applications like VoIP and "
"fast-paced games (see :ref:`WebRTC <doc_webrtc>` for those use cases)."
msgstr ""

#: ../../docs/tutorials/networking/websocket.rst:16
msgid ""
"Due to its simplicity, its wide compatibility, and being easier to use than "
"a raw TCP connection, WebSocket soon started to spread outside the browsers, "
"in native applications as a mean to communicate with network servers."
msgstr ""

#: ../../docs/tutorials/networking/websocket.rst:18
msgid "Godot supports WebSocket in both native and HTML5 exports."
msgstr ""

#: ../../docs/tutorials/networking/websocket.rst:21
msgid "Using WebSocket in Godot"
msgstr ""

#: ../../docs/tutorials/networking/websocket.rst:23
msgid ""
"WebSocket is implemented in Godot via :ref:`WebSocketPeer "
"<class_WebSocketPeer>`. The WebSocket implementation is compatible with the "
"High Level Multiplayer. See section on :ref:`high-level multiplayer "
"<doc_high_level_multiplayer>` for more details."
msgstr ""

#: ../../docs/tutorials/networking/websocket.rst:33
msgid "Minimal client example"
msgstr ""

#: ../../docs/tutorials/networking/websocket.rst:35
msgid ""
"This example will show you how to create a WebSocket connection to a remote "
"server, and how to send and receive data."
msgstr ""

#: ../../docs/tutorials/networking/websocket.rst:88
#: ../../docs/tutorials/networking/webrtc.rst:100
msgid "This will print:"
msgstr ""

#: ../../docs/tutorials/networking/websocket.rst:96
msgid "Minimal server example"
msgstr ""

#: ../../docs/tutorials/networking/websocket.rst:98
msgid ""
"This example will show you how to create a WebSocket server that listens for "
"remote connections, and how to send and receive data."
msgstr ""

#: ../../docs/tutorials/networking/websocket.rst:154
msgid "This will print (when a client connects) something similar to this:"
msgstr ""

#: ../../docs/tutorials/networking/websocket.rst:162
msgid "Advanced chat demo"
msgstr ""

#: ../../docs/tutorials/networking/websocket.rst:164
msgid ""
"A more advanced chat demo which optionally uses the multiplayer mid-level "
"abstraction and a high level multiplayer demo are available in the `godot "
"demo projects <https://github.com/godotengine/godot-demo-projects>`_ under "
"`networking/websocket_chat` and `networking/websocket_multiplayer`."
msgstr ""

#: ../../docs/tutorials/networking/webrtc.rst:6
#: ../../docs/tutorials/networking/webrtc.rst:23
msgid "WebRTC"
msgstr ""

#: ../../docs/tutorials/networking/webrtc.rst:9
msgid "HTML5, WebSocket, WebRTC"
msgstr ""

#: ../../docs/tutorials/networking/webrtc.rst:11
msgid ""
"One of Godot's great features is its ability to export to the HTML5/"
"WebAssembly platform, allowing your game to run directly in the browser when "
"a user visit your webpage."
msgstr ""

#: ../../docs/tutorials/networking/webrtc.rst:13
msgid ""
"This is a great opportunity for both demos and full games, but used to come "
"with some limitations. In the area of networking, browsers used to support "
"only HTTPRequests until recently, when first WebSocket and then WebRTC were "
"proposed as standards."
msgstr ""

#: ../../docs/tutorials/networking/webrtc.rst:18
msgid ""
"When the WebSocket protocol was standardized in December 2011, it allowed "
"browsers to create stable and bidirectional connections to a WebSocket "
"server. The protocol is a very powerful tool to send push notifications to "
"browsers, and has been used to implement chats, turn-based games, etc."
msgstr ""

#: ../../docs/tutorials/networking/webrtc.rst:20
msgid ""
"WebSockets, though, still use a TCP connection, which is good for "
"reliability but not for latency, so not good for real-time applications like "
"VoIP and fast-paced games."
msgstr ""

#: ../../docs/tutorials/networking/webrtc.rst:25
msgid ""
"For this reason, since 2010, Google started working on a new technology "
"called WebRTC, which later on, in 2017, became a W3C candidate "
"recommendation. WebRTC is a much more complex set of specifications, and "
"relies on many other technologies behind the scenes (ICE, DTLS, SDP) to "
"provide fast, real-time, and secure communication between two peers."
msgstr ""

#: ../../docs/tutorials/networking/webrtc.rst:27
msgid ""
"The idea is to find the fastest route between the two peers and establish "
"whenever possible a direct communication (i.e. try to avoid a relaying "
"server)."
msgstr ""

#: ../../docs/tutorials/networking/webrtc.rst:29
msgid ""
"However, this comes at a price, which is that some media information must be "
"exchanged between the two peers before the communication can start (in the "
"form of Session Description Protocol - SDP strings). This usually takes the "
"form of a so-called WebRTC Signaling Server."
msgstr ""

#: ../../docs/tutorials/networking/webrtc.rst:33
msgid ""
"Peers connect to a signaling server (for example a WebSocket server) and "
"send their media information. The server then relays this information to "
"other peers, allowing them to establish the desired direct communication. "
"Once this step is done, peers can disconnect from the signaling server and "
"keep the direct Peer-to-Peer (P2P) connection open."
msgstr ""

#: ../../docs/tutorials/networking/webrtc.rst:36
msgid "Using WebRTC in Godot"
msgstr ""

#: ../../docs/tutorials/networking/webrtc.rst:38
msgid ""
"WebRTC is implemented in Godot via two main classes :ref:"
"`WebRTCPeerConnection <class_WebRTCPeerConnection>` and :ref:"
"`WebRTCDataChannel <class_WebRTCDataChannel>`, plus the multiplayer API "
"implementation :ref:`WebRTCMultiplayerPeer <class_WebRTCMultiplayerPeer>`. "
"See section on :ref:`high-level multiplayer <doc_high_level_multiplayer>` "
"for more details."
msgstr ""

#: ../../docs/tutorials/networking/webrtc.rst:40
msgid ""
"These classes are available automatically in HTML5, but **require an "
"external GDExtension plugin on native (non-HTML5) platforms**. Check out the "
"`webrtc-native plugin repository <https://github.com/godotengine/webrtc-"
"native>`__ for instructions and to get the latest `release <https://github."
"com/godotengine/webrtc-native/releases>`__."
msgstr ""

#: ../../docs/tutorials/networking/webrtc.rst:50
msgid "Minimal connection example"
msgstr ""

#: ../../docs/tutorials/networking/webrtc.rst:52
msgid ""
"This example will show you how to create a WebRTC connection between two "
"peers in the same application. This is not very useful in real life, but "
"will give you a good overview of how a WebRTC connection is set up."
msgstr ""

#: ../../docs/tutorials/networking/webrtc.rst:108
msgid "Local signaling example"
msgstr ""

#: ../../docs/tutorials/networking/webrtc.rst:110
msgid ""
"This example expands on the previous one, separating the peers in two "
"different scenes, and using a :ref:`singleton <doc_singletons_autoload>` as "
"a signaling server."
msgstr ""

#: ../../docs/tutorials/networking/webrtc.rst:154
msgid "And now for the local signaling server:"
msgstr ""

#: ../../docs/tutorials/networking/webrtc.rst:156
msgid ""
"This local signaling server is supposed to be used as a :ref:`singleton "
"<doc_singletons_autoload>` to connect two peers in the same scene."
msgstr ""

#: ../../docs/tutorials/networking/webrtc.rst:192
msgid "Then you can use it like this:"
msgstr ""

#: ../../docs/tutorials/networking/webrtc.rst:215
msgid "This will print something similar to this:"
msgstr ""

#: ../../docs/tutorials/networking/webrtc.rst:223
msgid "Remote signaling with WebSocket"
msgstr ""

#: ../../docs/tutorials/networking/webrtc.rst:225
msgid ""
"A more advanced demo using WebSocket for signaling peers and :ref:"
"`WebRTCMultiplayerPeer <class_WebRTCMultiplayerPeer>` is available in the "
"`godot demo projects <https://github.com/godotengine/godot-demo-projects>`_ "
"under `networking/webrtc_signaling`."
msgstr ""

#: ../../docs/tutorials/performance/index.rst:9
msgid ""
"Godot follows a balanced performance philosophy. In the performance world, "
"there are always tradeoffs, which consist of trading speed for usability and "
"flexibility. Some practical examples of this are:"
msgstr ""

#: ../../docs/tutorials/performance/index.rst:13
msgid ""
"Rendering large amounts of objects efficiently is easy, but when a large "
"scene must be rendered, it can become inefficient. To solve this, visibility "
"computation must be added to the rendering. This makes rendering less "
"efficient, but at the same time, fewer objects are rendered. Therefore, the "
"overall rendering efficiency is improved."
msgstr ""

#: ../../docs/tutorials/performance/index.rst:19
msgid ""
"Configuring the properties of every material for every object that needs to "
"be rendered is also slow. To solve this, objects are sorted by material to "
"reduce the costs. At the same time, sorting has a cost."
msgstr ""

#: ../../docs/tutorials/performance/index.rst:23
msgid ""
"In 3D physics, a similar situation happens. The best algorithms to handle "
"large amounts of physics objects (such as SAP) are slow at insertion/removal "
"of objects and raycasting. Algorithms that allow faster insertion and "
"removal, as well as raycasting, will not be able to handle as many active "
"objects."
msgstr ""

#: ../../docs/tutorials/performance/index.rst:29
msgid ""
"And there are many more examples of this! Game engines strive to be general-"
"purpose in nature. Balanced algorithms are always favored over algorithms "
"that might be fast in some situations and slow in others, or algorithms that "
"are fast but are more difficult to use."
msgstr ""

#: ../../docs/tutorials/performance/index.rst:34
msgid ""
"Godot is not an exception to this. While it is designed to have backends "
"swappable for different algorithms, the default backends prioritize balance "
"and flexibility over performance."
msgstr ""

#: ../../docs/tutorials/performance/index.rst:38
msgid ""
"With this clear, the aim of this tutorial section is to explain how to get "
"the maximum performance out of Godot. While the tutorials can be read in any "
"order, it is a good idea to start from :ref:`doc_general_optimization`."
msgstr ""

#: ../../docs/tutorials/performance/index.rst:43
#, fuzzy
msgid "Common"
msgstr "Zajednica"

#: ../../docs/tutorials/performance/index.rst:53
msgid "CPU"
msgstr ""

#: ../../docs/tutorials/performance/index.rst:62
msgid "GPU"
msgstr ""

#: ../../docs/tutorials/performance/index.rst:83
#: ../../docs/tutorials/performance/cpu_optimization.rst:193
#: ../../docs/tutorials/performance/using_multiple_threads.rst:7
#: ../../docs/tutorials/performance/thread_safe_apis.rst:9
msgid "Threads"
msgstr ""

#: ../../docs/tutorials/performance/general_optimization.rst:4
msgid "General optimization tips"
msgstr ""

#: ../../docs/tutorials/performance/general_optimization.rst:9
msgid ""
"In an ideal world, computers would run at infinite speed. The only limit to "
"what we could achieve would be our imagination. However, in the real world, "
"it's all too easy to produce software that will bring even the fastest "
"computer to its knees."
msgstr ""

#: ../../docs/tutorials/performance/general_optimization.rst:14
msgid ""
"Thus, designing games and other software is a compromise between what we "
"would like to be possible, and what we can realistically achieve while "
"maintaining good performance."
msgstr ""

#: ../../docs/tutorials/performance/general_optimization.rst:18
msgid "To achieve the best results, we have two approaches:"
msgstr ""

#: ../../docs/tutorials/performance/general_optimization.rst:20
msgid "Work faster."
msgstr ""

#: ../../docs/tutorials/performance/general_optimization.rst:21
msgid "Work smarter."
msgstr ""

#: ../../docs/tutorials/performance/general_optimization.rst:23
msgid "And preferably, we will use a blend of the two."
msgstr ""

#: ../../docs/tutorials/performance/general_optimization.rst:26
msgid "Smoke and mirrors"
msgstr ""

#: ../../docs/tutorials/performance/general_optimization.rst:28
msgid ""
"Part of working smarter is recognizing that, in games, we can often get the "
"player to believe they're in a world that is far more complex, interactive, "
"and graphically exciting than it really is. A good programmer is a magician, "
"and should strive to learn the tricks of the trade while trying to invent "
"new ones."
msgstr ""

#: ../../docs/tutorials/performance/general_optimization.rst:34
msgid "The nature of slowness"
msgstr ""

#: ../../docs/tutorials/performance/general_optimization.rst:36
msgid ""
"To the outside observer, performance problems are often lumped together. But "
"in reality, there are several different kinds of performance problems:"
msgstr ""

#: ../../docs/tutorials/performance/general_optimization.rst:39
msgid ""
"A slow process that occurs every frame, leading to a continuously low frame "
"rate."
msgstr ""

#: ../../docs/tutorials/performance/general_optimization.rst:41
msgid ""
"An intermittent process that causes \"spikes\" of slowness, leading to "
"stalls."
msgstr ""

#: ../../docs/tutorials/performance/general_optimization.rst:43
msgid ""
"A slow process that occurs outside of normal gameplay, for instance, when "
"loading a level."
msgstr ""

#: ../../docs/tutorials/performance/general_optimization.rst:46
msgid "Each of these are annoying to the user, but in different ways."
msgstr ""

#: ../../docs/tutorials/performance/general_optimization.rst:49
#: ../../docs/tutorials/performance/cpu_optimization.rst:7
msgid "Measuring performance"
msgstr ""

#: ../../docs/tutorials/performance/general_optimization.rst:51
msgid ""
"Probably the most important tool for optimization is the ability to measure "
"performance - to identify where bottlenecks are, and to measure the success "
"of our attempts to speed them up."
msgstr ""

#: ../../docs/tutorials/performance/general_optimization.rst:55
msgid "There are several methods of measuring performance, including:"
msgstr ""

#: ../../docs/tutorials/performance/general_optimization.rst:57
msgid "Putting a start/stop timer around code of interest."
msgstr ""

#: ../../docs/tutorials/performance/general_optimization.rst:58
#, fuzzy
msgid "Using the :ref:`Godot profiler <doc_the_profiler>`."
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/performance/general_optimization.rst:59
msgid "Using :ref:`external CPU profilers <doc_using_cpp_profilers>`."
msgstr ""

#: ../../docs/tutorials/performance/general_optimization.rst:60
msgid ""
"Using external GPU profilers/debuggers such as `NVIDIA Nsight Graphics "
"<https://developer.nvidia.com/nsight-graphics>`__, `Radeon GPU Profiler "
"<https://gpuopen.com/rgp/>`__ or `Intel Graphics Performance Analyzers "
"<https://www.intel.com/content/www/us/en/developer/tools/graphics-"
"performance-analyzers/overview.html>`__."
msgstr ""

#: ../../docs/tutorials/performance/general_optimization.rst:64
msgid ""
"Checking the frame rate (with V-Sync disabled). Third-party utilities such "
"as `RivaTuner Statistics Server <https://www.guru3d.com/files-details/rtss-"
"rivatuner-statistics-server-download.html>`__ (Windows) or `MangoHud "
"<https://github.com/flightlessmango/MangoHud>`__ (Linux) can also be useful "
"here."
msgstr ""

#: ../../docs/tutorials/performance/general_optimization.rst:68
msgid ""
"Using an unofficial `debug menu add-on <https://github.com/godot-extended-"
"libraries/godot-debug-menu>`__."
msgstr ""

#: ../../docs/tutorials/performance/general_optimization.rst:70
msgid ""
"Be very aware that the relative performance of different areas can vary on "
"different hardware. It's often a good idea to measure timings on more than "
"one device. This is especially the case if you're targeting mobile devices."
msgstr ""

#: ../../docs/tutorials/performance/general_optimization.rst:77
msgid ""
"CPU profilers are often the go-to method for measuring performance. However, "
"they don't always tell the whole story."
msgstr ""

#: ../../docs/tutorials/performance/general_optimization.rst:80
msgid ""
"Bottlenecks are often on the GPU, \"as a result\" of instructions given by "
"the CPU."
msgstr ""

#: ../../docs/tutorials/performance/general_optimization.rst:82
msgid ""
"Spikes can occur in the operating system processes (outside of Godot) \"as a "
"result\" of instructions used in Godot (for example, dynamic memory "
"allocation)."
msgstr ""

#: ../../docs/tutorials/performance/general_optimization.rst:84
msgid ""
"You may not always be able to profile specific devices like a mobile phone "
"due to the initial setup required."
msgstr ""

#: ../../docs/tutorials/performance/general_optimization.rst:86
msgid ""
"You may have to solve performance problems that occur on hardware you don't "
"have access to."
msgstr ""

#: ../../docs/tutorials/performance/general_optimization.rst:89
msgid ""
"As a result of these limitations, you often need to use detective work to "
"find out where bottlenecks are."
msgstr ""

#: ../../docs/tutorials/performance/general_optimization.rst:93
msgid "Detective work"
msgstr ""

#: ../../docs/tutorials/performance/general_optimization.rst:95
msgid ""
"Detective work is a crucial skill for developers (both in terms of "
"performance, and also in terms of bug fixing). This can include hypothesis "
"testing, and binary search."
msgstr ""

#: ../../docs/tutorials/performance/general_optimization.rst:100
msgid "Hypothesis testing"
msgstr ""

#: ../../docs/tutorials/performance/general_optimization.rst:102
msgid ""
"Say, for example, that you believe sprites are slowing down your game. You "
"can test this hypothesis by:"
msgstr ""

#: ../../docs/tutorials/performance/general_optimization.rst:105
msgid "Measuring the performance when you add more sprites, or take some away."
msgstr ""

#: ../../docs/tutorials/performance/general_optimization.rst:107
msgid ""
"This may lead to a further hypothesis: does the size of the sprite determine "
"the performance drop?"
msgstr ""

#: ../../docs/tutorials/performance/general_optimization.rst:110
msgid ""
"You can test this by keeping everything the same, but changing the sprite "
"size, and measuring performance."
msgstr ""

#: ../../docs/tutorials/performance/general_optimization.rst:114
msgid "Binary search"
msgstr ""

#: ../../docs/tutorials/performance/general_optimization.rst:116
msgid ""
"If you know that frames are taking much longer than they should, but you're "
"not sure where the bottleneck lies. You could begin by commenting out "
"approximately half the routines that occur on a normal frame. Has the "
"performance improved more or less than expected?"
msgstr ""

#: ../../docs/tutorials/performance/general_optimization.rst:121
msgid ""
"Once you know which of the two halves contains the bottleneck, you can "
"repeat this process until you've pinned down the problematic area."
msgstr ""

#: ../../docs/tutorials/performance/general_optimization.rst:125
msgid "Profilers"
msgstr ""

#: ../../docs/tutorials/performance/general_optimization.rst:127
msgid ""
"Profilers allow you to time your program while running it. Profilers then "
"provide results telling you what percentage of time was spent in different "
"functions and areas, and how often functions were called."
msgstr ""

#: ../../docs/tutorials/performance/general_optimization.rst:131
msgid ""
"This can be very useful both to identify bottlenecks and to measure the "
"results of your improvements. Sometimes, attempts to improve performance can "
"backfire and lead to slower performance. **Always use profiling and timing "
"to guide your efforts.**"
msgstr ""

#: ../../docs/tutorials/performance/general_optimization.rst:136
#, fuzzy
msgid ""
"For more info about using Godot's built-in profiler, see :ref:"
"`doc_the_profiler`."
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/performance/general_optimization.rst:139
msgid "Principles"
msgstr ""

#: ../../docs/tutorials/performance/general_optimization.rst:141
msgid "`Donald Knuth <https://en.wikipedia.org/wiki/Donald_Knuth>`__ said:"
msgstr ""

#: ../../docs/tutorials/performance/general_optimization.rst:143
msgid ""
"*Programmers waste enormous amounts of time thinking about, or worrying "
"about, the speed of noncritical parts of their programs, and these attempts "
"at efficiency actually have a strong negative impact when debugging and "
"maintenance are considered. We should forget about small efficiencies, say "
"about 97% of the time: premature optimization is the root of all evil. Yet "
"we should not pass up our opportunities in that critical 3%.*"
msgstr ""

#: ../../docs/tutorials/performance/general_optimization.rst:150
msgid "The messages are very important:"
msgstr ""

#: ../../docs/tutorials/performance/general_optimization.rst:152
msgid ""
"Developer time is limited. Instead of blindly trying to speed up all aspects "
"of a program, we should concentrate our efforts on the aspects that really "
"matter."
msgstr ""

#: ../../docs/tutorials/performance/general_optimization.rst:155
msgid ""
"Efforts at optimization often end up with code that is harder to read and "
"debug than non-optimized code. It is in our interests to limit this to areas "
"that will really benefit."
msgstr ""

#: ../../docs/tutorials/performance/general_optimization.rst:159
msgid ""
"Just because we *can* optimize a particular bit of code, it doesn't "
"necessarily mean that we *should*. Knowing when and when not to optimize is "
"a great skill to develop."
msgstr ""

#: ../../docs/tutorials/performance/general_optimization.rst:163
msgid ""
"One misleading aspect of the quote is that people tend to focus on the "
"subquote *\"premature optimization is the root of all evil\"*. While "
"*premature* optimization is (by definition) undesirable, performant software "
"is the result of performant design."
msgstr ""

#: ../../docs/tutorials/performance/general_optimization.rst:169
msgid "Performant design"
msgstr ""

#: ../../docs/tutorials/performance/general_optimization.rst:171
msgid ""
"The danger with encouraging people to ignore optimization until necessary, "
"is that it conveniently ignores that the most important time to consider "
"performance is at the design stage, before a key has even hit a keyboard. If "
"the design or algorithms of a program are inefficient, then no amount of "
"polishing the details later will make it run fast. It may run *faster*, but "
"it will never run as fast as a program designed for performance."
msgstr ""

#: ../../docs/tutorials/performance/general_optimization.rst:178
msgid ""
"This tends to be far more important in game or graphics programming than in "
"general programming. A performant design, even without low-level "
"optimization, will often run many times faster than a mediocre design with "
"low-level optimization."
msgstr ""

#: ../../docs/tutorials/performance/general_optimization.rst:184
msgid "Incremental design"
msgstr ""

#: ../../docs/tutorials/performance/general_optimization.rst:186
msgid ""
"Of course, in practice, unless you have prior knowledge, you are unlikely to "
"come up with the best design the first time. Instead, you'll often make a "
"series of versions of a particular area of code, each taking a different "
"approach to the problem, until you come to a satisfactory solution. It's "
"important not to spend too much time on the details at this stage until you "
"have finalized the overall design. Otherwise, much of your work will be "
"thrown out."
msgstr ""

#: ../../docs/tutorials/performance/general_optimization.rst:193
msgid ""
"It's difficult to give general guidelines for performant design because this "
"is so dependent on the problem. One point worth mentioning though, on the "
"CPU side, is that modern CPUs are nearly always limited by memory bandwidth. "
"This has led to a resurgence in data-oriented design, which involves "
"designing data structures and algorithms for *cache locality* of data and "
"linear access, rather than jumping around in memory."
msgstr ""

#: ../../docs/tutorials/performance/general_optimization.rst:201
msgid "The optimization process"
msgstr ""

#: ../../docs/tutorials/performance/general_optimization.rst:203
msgid ""
"Assuming we have a reasonable design, and taking our lessons from Knuth, our "
"first step in optimization should be to identify the biggest bottlenecks - "
"the slowest functions, the low-hanging fruit."
msgstr ""

#: ../../docs/tutorials/performance/general_optimization.rst:207
msgid ""
"Once we've successfully improved the speed of the slowest area, it may no "
"longer be the bottleneck. So we should test/profile again and find the next "
"bottleneck on which to focus."
msgstr ""

#: ../../docs/tutorials/performance/general_optimization.rst:211
msgid "The process is thus:"
msgstr ""

#: ../../docs/tutorials/performance/general_optimization.rst:213
msgid "Profile / Identify bottleneck."
msgstr ""

#: ../../docs/tutorials/performance/general_optimization.rst:214
msgid "Optimize bottleneck."
msgstr ""

#: ../../docs/tutorials/performance/general_optimization.rst:215
msgid "Return to step 1."
msgstr ""

#: ../../docs/tutorials/performance/general_optimization.rst:218
msgid "Optimizing bottlenecks"
msgstr ""

#: ../../docs/tutorials/performance/general_optimization.rst:220
msgid ""
"Some profilers will even tell you which part of a function (which data "
"accesses, calculations) are slowing things down."
msgstr ""

#: ../../docs/tutorials/performance/general_optimization.rst:223
msgid ""
"As with design, you should concentrate your efforts first on making sure the "
"algorithms and data structures are the best they can be. Data access should "
"be local (to make best use of CPU cache), and it can often be better to use "
"compact storage of data (again, always profile to test results). Often, you "
"precalculate heavy computations ahead of time. This can be done by "
"performing the computation when loading a level, by loading a file "
"containing precalculated data or simply by storing the results of complex "
"calculations into a script constant and reading its value."
msgstr ""

#: ../../docs/tutorials/performance/general_optimization.rst:232
msgid ""
"Once algorithms and data are good, you can often make small changes in "
"routines which improve performance. For instance, you can move some "
"calculations outside of loops or transform nested ``for`` loops into non-"
"nested loops. (This should be feasible if you know a 2D array's width or "
"height in advance.)"
msgstr ""

#: ../../docs/tutorials/performance/general_optimization.rst:237
msgid ""
"Always retest your timing/bottlenecks after making each change. Some changes "
"will increase speed, others may have a negative effect. Sometimes, a small "
"positive effect will be outweighed by the negatives of more complex code, "
"and you may choose to leave out that optimization."
msgstr ""

#: ../../docs/tutorials/performance/general_optimization.rst:243
msgid "Appendix"
msgstr ""

#: ../../docs/tutorials/performance/general_optimization.rst:246
msgid "Bottleneck math"
msgstr ""

#: ../../docs/tutorials/performance/general_optimization.rst:248
msgid ""
"The proverb *\"a chain is only as strong as its weakest link\"* applies "
"directly to performance optimization. If your project is spending 90% of the "
"time in function ``A``, then optimizing ``A`` can have a massive effect on "
"performance."
msgstr ""

#: ../../docs/tutorials/performance/general_optimization.rst:264
msgid ""
"In this example, improving this bottleneck ``A`` by a factor of 9× decreases "
"overall frame time by 5× while increasing frames per second by 5×."
msgstr ""

#: ../../docs/tutorials/performance/general_optimization.rst:267
msgid ""
"However, if something else is running slowly and also bottlenecking your "
"project, then the same improvement can lead to less dramatic gains:"
msgstr ""

#: ../../docs/tutorials/performance/general_optimization.rst:282
msgid ""
"In this example, even though we have hugely optimized function ``A``, the "
"actual gain in terms of frame rate is quite small."
msgstr ""

#: ../../docs/tutorials/performance/general_optimization.rst:285
msgid ""
"In games, things become even more complicated because the CPU and GPU run "
"independently of one another. Your total frame time is determined by the "
"slower of the two."
msgstr ""

#: ../../docs/tutorials/performance/general_optimization.rst:301
msgid ""
"In this example, we optimized the CPU hugely again, but the frame time "
"didn't improve because we are GPU-bottlenecked."
msgstr ""

#: ../../docs/tutorials/performance/using_servers.rst:6
msgid "Optimization using Servers"
msgstr ""

#: ../../docs/tutorials/performance/using_servers.rst:8
msgid ""
"Engines like Godot provide increased ease of use thanks to their high level "
"constructs and features. Most of them are accessed and used via the :ref:"
"`Scene System<doc_scene_tree>`. Using nodes and resources simplifies project "
"organization and asset management in complex games."
msgstr ""

#: ../../docs/tutorials/performance/using_servers.rst:12
msgid "There are, of course, always drawbacks:"
msgstr ""

#: ../../docs/tutorials/performance/using_servers.rst:14
msgid "There is an extra layer of complexity."
msgstr ""

#: ../../docs/tutorials/performance/using_servers.rst:15
msgid "Performance is lower than when using simple APIs directly."
msgstr ""

#: ../../docs/tutorials/performance/using_servers.rst:16
msgid "It is not possible to use multiple threads to control them."
msgstr ""

#: ../../docs/tutorials/performance/using_servers.rst:17
msgid "More memory is needed."
msgstr ""

#: ../../docs/tutorials/performance/using_servers.rst:19
msgid ""
"In many cases, this is not really a problem (Godot is very optimized, and "
"most operations are handled with signals, so no polling is required). Still, "
"sometimes it can be. For example, dealing with tens of thousands of "
"instances for something that needs to be processed every frame can be a "
"bottleneck."
msgstr ""

#: ../../docs/tutorials/performance/using_servers.rst:23
msgid ""
"This type of situation makes programmers regret they are using a game engine "
"and wish they could go back to a more handcrafted, low level implementation "
"of game code."
msgstr ""

#: ../../docs/tutorials/performance/using_servers.rst:26
msgid "Still, Godot is designed to work around this problem."
msgstr ""

#: ../../docs/tutorials/performance/using_servers.rst:30
#, fuzzy
msgid ""
"You can see how using low-level servers works in action using the `Bullet "
"Shower demo project <https://github.com/godotengine/godot-demo-projects/tree/"
"master/2d/bullet_shower>`__"
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati različite Godo demo projekte "
"`Godot demo projects <https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/tutorials/performance/using_servers.rst:34
msgid "Servers"
msgstr ""

#: ../../docs/tutorials/performance/using_servers.rst:36
msgid ""
"One of the most interesting design decisions for Godot is the fact that the "
"whole scene system is *optional*. While it is not currently possible to "
"compile it out, it can be completely bypassed."
msgstr ""

#: ../../docs/tutorials/performance/using_servers.rst:39
msgid ""
"At the core, Godot uses the concept of Servers. They are very low-level APIs "
"to control rendering, physics, sound, etc. The scene system is built on top "
"of them and uses them directly. The most common servers are:"
msgstr ""

#: ../../docs/tutorials/performance/using_servers.rst:43
msgid ""
":ref:`RenderingServer <class_RenderingServer>`: handles everything related "
"to graphics."
msgstr ""

#: ../../docs/tutorials/performance/using_servers.rst:44
msgid ""
":ref:`PhysicsServer3D <class_PhysicsServer3D>`: handles everything related "
"to 3D physics."
msgstr ""

#: ../../docs/tutorials/performance/using_servers.rst:45
msgid ""
":ref:`PhysicsServer2D <class_PhysicsServer2D>`: handles everything related "
"to 2D physics."
msgstr ""

#: ../../docs/tutorials/performance/using_servers.rst:46
msgid ""
":ref:`AudioServer <class_AudioServer>`: handles everything related to audio."
msgstr ""

#: ../../docs/tutorials/performance/using_servers.rst:48
msgid ""
"Explore their APIs and you will realize that all the functions provided are "
"low-level implementations of everything Godot allows you to do."
msgstr ""

#: ../../docs/tutorials/performance/using_servers.rst:52
msgid "RIDs"
msgstr ""

#: ../../docs/tutorials/performance/using_servers.rst:54
msgid ""
"The key to using servers is understanding Resource ID (:ref:`RID "
"<class_RID>`) objects. These are opaque handles to the server "
"implementation. They are allocated and freed manually. Almost every function "
"in the servers requires RIDs to access the actual resource."
msgstr ""

#: ../../docs/tutorials/performance/using_servers.rst:58
msgid ""
"Most Godot nodes and resources contain these RIDs from the servers "
"internally, and they can be obtained with different functions. In fact, "
"anything that inherits :ref:`Resource <class_Resource>` can be directly "
"casted to an RID. Not all resources contain an RID, though: in such cases, "
"the RID will be empty. The resource can then be passed to server APIs as an "
"RID."
msgstr ""

#: ../../docs/tutorials/performance/using_servers.rst:62
msgid ""
"Resources are reference-counted (see :ref:`RefCounted <class_RefCounted>`), "
"and references to a resource's RID are *not* counted when determining "
"whether the resource is still in use. Make sure to keep a reference to the "
"resource outside the server, or else both it and its RID will be erased."
msgstr ""

#: ../../docs/tutorials/performance/using_servers.rst:67
msgid "For nodes, there are many functions available:"
msgstr ""

#: ../../docs/tutorials/performance/using_servers.rst:69
msgid ""
"For CanvasItem, the :ref:`CanvasItem.get_canvas_item() "
"<class_CanvasItem_method_get_canvas_item>` method will return the canvas "
"item RID in the server."
msgstr ""

#: ../../docs/tutorials/performance/using_servers.rst:71
msgid ""
"For CanvasLayer, the :ref:`CanvasLayer.get_canvas() "
"<class_CanvasLayer_method_get_canvas>` method will return the canvas RID in "
"the server."
msgstr ""

#: ../../docs/tutorials/performance/using_servers.rst:73
msgid ""
"For Viewport, the :ref:`Viewport.get_viewport_rid() "
"<class_Viewport_method_get_viewport_rid>` method will return the viewport "
"RID in the server."
msgstr ""

#: ../../docs/tutorials/performance/using_servers.rst:75
msgid ""
"For 3D, the :ref:`World3D <class_World3D>` resource (obtainable in the :ref:"
"`Viewport <class_Viewport>` and :ref:`Node3D <class_Node3D>` nodes) contains "
"functions to get the *RenderingServer Scenario*, and the *PhysicsServer "
"Space*. This allows creating 3D objects directly with the server API and "
"using them."
msgstr ""

#: ../../docs/tutorials/performance/using_servers.rst:79
msgid ""
"For 2D, the :ref:`World2D <class_World2D>` resource (obtainable in the :ref:"
"`Viewport <class_Viewport>` and :ref:`CanvasItem <class_CanvasItem>` nodes) "
"contains functions to get the *RenderingServer Canvas*, and the "
"*Physics2DServer Space*. This allows creating 2D objects directly with the "
"server API and using them."
msgstr ""

#: ../../docs/tutorials/performance/using_servers.rst:83
msgid ""
"The :ref:`VisualInstance3D<class_VisualInstance3D>` class, allows getting "
"the scenario *instance* and *instance base* via the :ref:`VisualInstance3D."
"get_instance() <class_VisualInstance3D_method_get_instance>` and :ref:"
"`VisualInstance3D.get_base() <class_VisualInstance3D_method_get_base>` "
"respectively."
msgstr ""

#: ../../docs/tutorials/performance/using_servers.rst:87
msgid ""
"Try exploring the nodes and resources you are familiar with and find the "
"functions to obtain the server *RIDs*."
msgstr ""

#: ../../docs/tutorials/performance/using_servers.rst:89
msgid ""
"It is not advised to control RIDs from objects that already have a node "
"associated. Instead, server functions should always be used for creating and "
"controlling new ones and interacting with the existing ones."
msgstr ""

#: ../../docs/tutorials/performance/using_servers.rst:93
#, fuzzy
msgid "Creating a sprite"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/performance/using_servers.rst:95
msgid ""
"This is an example of how to create a sprite from code and move it using the "
"low-level :ref:`CanvasItem <class_CanvasItem>` API."
msgstr ""

#: ../../docs/tutorials/performance/using_servers.rst:146
msgid ""
"The Canvas Item API in the server allows you to add draw primitives to it. "
"Once added, they can't be modified. The Item needs to be cleared and the "
"primitives re-added (this is not the case for setting the transform, which "
"can be done as many times as desired)."
msgstr ""

#: ../../docs/tutorials/performance/using_servers.rst:150
msgid "Primitives are cleared this way:"
msgstr ""

#: ../../docs/tutorials/performance/using_servers.rst:163
msgid "Instantiating a Mesh into 3D space"
msgstr ""

#: ../../docs/tutorials/performance/using_servers.rst:165
msgid ""
"The 3D APIs are different from the 2D ones, so the instantiation API must be "
"used."
msgstr ""

#: ../../docs/tutorials/performance/using_servers.rst:218
msgid "Creating a 2D RigidBody and moving a sprite with it"
msgstr ""

#: ../../docs/tutorials/performance/using_servers.rst:220
msgid ""
"This creates a :ref:`RigidBody2D <class_RigidBody2D>` using the :ref:"
"`PhysicsServer2D <class_PhysicsServer2D>` API, and moves a :ref:`CanvasItem "
"<class_CanvasItem>` when the body moves."
msgstr ""

#: ../../docs/tutorials/performance/using_servers.rst:255
msgid ""
"The 3D version should be very similar, as 2D and 3D physics servers are "
"identical (using :ref:`RigidBody3D <class_RigidBody3D>` and :ref:"
"`PhysicsServer3D <class_PhysicsServer3D>` respectively)."
msgstr ""

#: ../../docs/tutorials/performance/using_servers.rst:259
msgid "Getting data from the servers"
msgstr ""

#: ../../docs/tutorials/performance/using_servers.rst:261
msgid ""
"Try to **never** request any information from ``RenderingServer``, "
"``PhysicsServer2D`` or ``PhysicsServer3D`` by calling functions unless you "
"know what you are doing. These servers will often run asynchronously for "
"performance and calling any function that returns a value will stall them "
"and force them to process anything pending until the function is actually "
"called. This will severely decrease performance if you call them every frame "
"(and it won't be obvious why)."
msgstr ""

#: ../../docs/tutorials/performance/using_servers.rst:267
msgid ""
"Because of this, most APIs in such servers are designed so it's not even "
"possible to request information back, until it's actual data that can be "
"saved."
msgstr ""

#: ../../docs/tutorials/performance/cpu_optimization.rst:4
msgid "CPU optimization"
msgstr ""

#: ../../docs/tutorials/performance/cpu_optimization.rst:9
msgid ""
"We have to know where the \"bottlenecks\" are to know how to speed up our "
"program. Bottlenecks are the slowest parts of the program that limit the "
"rate that everything can progress. Focusing on bottlenecks allows us to "
"concentrate our efforts on optimizing the areas which will give us the "
"greatest speed improvement, instead of spending a lot of time optimizing "
"functions that will lead to small performance improvements."
msgstr ""

#: ../../docs/tutorials/performance/cpu_optimization.rst:16
msgid ""
"For the CPU, the easiest way to identify bottlenecks is to use a profiler."
msgstr ""

#: ../../docs/tutorials/performance/cpu_optimization.rst:19
msgid "CPU profilers"
msgstr ""

#: ../../docs/tutorials/performance/cpu_optimization.rst:21
msgid ""
"Profilers run alongside your program and take timing measurements to work "
"out what proportion of time is spent in each function."
msgstr ""

#: ../../docs/tutorials/performance/cpu_optimization.rst:24
msgid ""
"The Godot IDE conveniently has a built-in profiler. It does not run every "
"time you start your project: it must be manually started and stopped. This "
"is because, like most profilers, recording these timing measurements can "
"slow down your project significantly."
msgstr ""

#: ../../docs/tutorials/performance/cpu_optimization.rst:29
msgid "After profiling, you can look back at the results for a frame."
msgstr ""

#: ../../docs/tutorials/performance/cpu_optimization.rst:35
#, fuzzy
msgid "Screenshot of the Godot profiler"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/performance/cpu_optimization.rst:35
msgid "Results of a profile of one of the demo projects."
msgstr ""

#: ../../docs/tutorials/performance/cpu_optimization.rst:37
msgid ""
"We can see the cost of built-in processes such as physics and audio, as well "
"as seeing the cost of our own scripting functions at the bottom."
msgstr ""

#: ../../docs/tutorials/performance/cpu_optimization.rst:41
msgid ""
"Time spent waiting for various built-in servers may not be counted in the "
"profilers. This is a known bug."
msgstr ""

#: ../../docs/tutorials/performance/cpu_optimization.rst:44
msgid ""
"When a project is running slowly, you will often see an obvious function or "
"process taking a lot more time than others. This is your primary bottleneck, "
"and you can usually increase speed by optimizing this area."
msgstr ""

#: ../../docs/tutorials/performance/cpu_optimization.rst:48
msgid ""
"For more info about using Godot's built-in profiler, see :ref:"
"`doc_debugger_panel`."
msgstr ""

#: ../../docs/tutorials/performance/cpu_optimization.rst:52
msgid "External profilers"
msgstr ""

#: ../../docs/tutorials/performance/cpu_optimization.rst:54
msgid ""
"Although the Godot IDE profiler is very convenient and useful, sometimes you "
"need more power, and the ability to profile the Godot engine source code "
"itself."
msgstr ""

#: ../../docs/tutorials/performance/cpu_optimization.rst:57
msgid ""
"You can :ref:`use a number of third-party C++ profilers "
"<doc_using_cpp_profilers>` to do this."
msgstr ""

#: ../../docs/tutorials/performance/cpu_optimization.rst:63
msgid "Screenshot of Callgrind"
msgstr ""

#: ../../docs/tutorials/performance/cpu_optimization.rst:63
msgid "Example results from Callgrind, which is part of Valgrind."
msgstr ""

#: ../../docs/tutorials/performance/cpu_optimization.rst:65
msgid ""
"From the left, Callgrind is listing the percentage of time within a function "
"and its children (Inclusive), the percentage of time spent within the "
"function itself, excluding child functions (Self), the number of times the "
"function is called, the function name, and the file or module."
msgstr ""

#: ../../docs/tutorials/performance/cpu_optimization.rst:70
msgid ""
"In this example, we can see nearly all time is spent under the ``Main::"
"iteration()`` function. This is the master function in the Godot source code "
"that is called repeatedly. It causes frames to be drawn, physics ticks to be "
"simulated, and nodes and scripts to be updated. A large proportion of the "
"time is spent in the functions to render a canvas (66%), because this "
"example uses a 2D benchmark. Below this, we see that almost 50% of the time "
"is spent outside Godot code in ``libglapi`` and ``i965_dri`` (the graphics "
"driver). This tells us the a large proportion of CPU time is being spent in "
"the graphics driver."
msgstr ""

#: ../../docs/tutorials/performance/cpu_optimization.rst:80
msgid ""
"This is actually an excellent example because, in an ideal world, only a "
"very small proportion of time would be spent in the graphics driver. This is "
"an indication that there is a problem with too much communication and work "
"being done in the graphics API. This specific profiling led to the "
"development of 2D batching, which greatly speeds up 2D rendering by reducing "
"bottlenecks in this area."
msgstr ""

#: ../../docs/tutorials/performance/cpu_optimization.rst:88
msgid "Manually timing functions"
msgstr ""

#: ../../docs/tutorials/performance/cpu_optimization.rst:90
msgid ""
"Another handy technique, especially once you have identified the bottleneck "
"using a profiler, is to manually time the function or area under test. The "
"specifics vary depending on the language, but in GDScript, you would do the "
"following:"
msgstr ""

#: ../../docs/tutorials/performance/cpu_optimization.rst:105
msgid ""
"When manually timing functions, it is usually a good idea to run the "
"function many times (1,000 or more times), instead of just once (unless it "
"is a very slow function). The reason for doing this is that timers often "
"have limited accuracy. Moreover, CPUs will schedule processes in a haphazard "
"manner. Therefore, an average over a series of runs is more accurate than a "
"single measurement."
msgstr ""

#: ../../docs/tutorials/performance/cpu_optimization.rst:111
msgid ""
"As you attempt to optimize functions, be sure to either repeatedly profile "
"or time them as you go. This will give you crucial feedback as to whether "
"the optimization is working (or not)."
msgstr ""

#: ../../docs/tutorials/performance/cpu_optimization.rst:116
msgid "Caches"
msgstr ""

#: ../../docs/tutorials/performance/cpu_optimization.rst:118
msgid ""
"CPU caches are something else to be particularly aware of, especially when "
"comparing timing results of two different versions of a function. The "
"results can be highly dependent on whether the data is in the CPU cache or "
"not. CPUs don't load data directly from the system RAM, even though it's "
"huge in comparison to the CPU cache (several gigabytes instead of a few "
"megabytes). This is because system RAM is very slow to access. Instead, CPUs "
"load data from a smaller, faster bank of memory called cache. Loading data "
"from cache is very fast, but every time you try and load a memory address "
"that is not stored in cache, the cache must make a trip to main memory and "
"slowly load in some data. This delay can result in the CPU sitting around "
"idle for a long time, and is referred to as a \"cache miss\"."
msgstr ""

#: ../../docs/tutorials/performance/cpu_optimization.rst:130
msgid ""
"This means that the first time you run a function, it may run slowly because "
"the data is not in the CPU cache. The second and later times, it may run "
"much faster because the data is in the cache. Due to this, always use "
"averages when timing, and be aware of the effects of cache."
msgstr ""

#: ../../docs/tutorials/performance/cpu_optimization.rst:135
msgid ""
"Understanding caching is also crucial to CPU optimization. If you have an "
"algorithm (routine) that loads small bits of data from randomly spread out "
"areas of main memory, this can result in a lot of cache misses, a lot of the "
"time, the CPU will be waiting around for data instead of doing any work. "
"Instead, if you can make your data accesses localised, or even better, "
"access memory in a linear fashion (like a continuous list), then the cache "
"will work optimally and the CPU will be able to work as fast as possible."
msgstr ""

#: ../../docs/tutorials/performance/cpu_optimization.rst:143
msgid ""
"Godot usually takes care of such low-level details for you. For example, the "
"Server APIs make sure data is optimized for caching already for things like "
"rendering and physics. Still, you should be especially aware of caching when "
"writing GDExtensions."
msgstr ""

#: ../../docs/tutorials/performance/cpu_optimization.rst:151
msgid ""
"Godot supports a number of different languages, and it is worth bearing in "
"mind that there are trade-offs involved. Some languages are designed for "
"ease of use at the cost of speed, and others are faster but more difficult "
"to work with."
msgstr ""

#: ../../docs/tutorials/performance/cpu_optimization.rst:155
msgid ""
"Built-in engine functions run at the same speed regardless of the scripting "
"language you choose. If your project is making a lot of calculations in its "
"own code, consider moving those calculations to a faster language."
msgstr ""

#: ../../docs/tutorials/performance/cpu_optimization.rst:162
msgid ""
":ref:`GDScript <toc-learn-scripting-gdscript>` is designed to be easy to use "
"and iterate, and is ideal for making many types of games. However, in this "
"language, ease of use is considered more important than performance. If you "
"need to make heavy calculations, consider moving some of your project to one "
"of the other languages."
msgstr ""

#: ../../docs/tutorials/performance/cpu_optimization.rst:171
msgid ""
":ref:`C# <toc-learn-scripting-C#>` is popular and has first-class support in "
"Godot. It offers a good compromise between speed and ease of use. Beware of "
"possible garbage collection pauses and leaks that can occur during gameplay, "
"though. A common approach to workaround issues with garbage collection is to "
"use *object pooling*, which is outside the scope of this guide."
msgstr ""

#: ../../docs/tutorials/performance/cpu_optimization.rst:178
msgid "Other languages"
msgstr ""

#: ../../docs/tutorials/performance/cpu_optimization.rst:180
msgid ""
"Third parties provide support for several other languages, including `Rust "
"<https://github.com/godot-rust/gdext>`_."
msgstr ""

#: ../../docs/tutorials/performance/cpu_optimization.rst:186
msgid ""
"Godot is written in C++. Using C++ will usually result in the fastest code. "
"However, on a practical level, it is the most difficult to deploy to end "
"users' machines on different platforms. Options for using C++ include "
"GDExtensions and :ref:`custom modules <doc_custom_modules_in_cpp>`."
msgstr ""

#: ../../docs/tutorials/performance/cpu_optimization.rst:195
msgid ""
"Consider using threads when making a lot of calculations that can run in "
"parallel to each other. Modern CPUs have multiple cores, each one capable of "
"doing a limited amount of work. By spreading work over multiple threads, you "
"can move further towards peak CPU efficiency."
msgstr ""

#: ../../docs/tutorials/performance/cpu_optimization.rst:200
msgid ""
"The disadvantage of threads is that you have to be incredibly careful. As "
"each CPU core operates independently, they can end up trying to access the "
"same memory at the same time. One thread can be reading to a variable while "
"another is writing: this is called a *race condition*. Before you use "
"threads, make sure you understand the dangers and how to try and prevent "
"these race conditions. Threads can make debugging considerably more "
"difficult."
msgstr ""

#: ../../docs/tutorials/performance/cpu_optimization.rst:207
#, fuzzy
msgid "For more information on threads, see :ref:`doc_using_multiple_threads`."
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/performance/cpu_optimization.rst:210
#: ../../docs/tutorials/scripting/scene_tree.rst:33
msgid "SceneTree"
msgstr ""

#: ../../docs/tutorials/performance/cpu_optimization.rst:212
msgid ""
"Although Nodes are an incredibly powerful and versatile concept, be aware "
"that every node has a cost. Built-in functions such as ``_process()`` and "
"``_physics_process()`` propagate through the tree. This housekeeping can "
"reduce performance when you have a very large numbers of nodes (how many "
"exactly depends on the target platform and can range from thousands to tens "
"of thousands so ensure that you profile performance on all target platforms "
"during development)."
msgstr ""

#: ../../docs/tutorials/performance/cpu_optimization.rst:220
msgid ""
"Each node is handled individually in the Godot renderer. Therefore, a "
"smaller number of nodes with more in each can lead to better performance."
msgstr ""

#: ../../docs/tutorials/performance/cpu_optimization.rst:223
msgid ""
"One quirk of the :ref:`SceneTree <class_SceneTree>` is that you can "
"sometimes get much better performance by removing nodes from the SceneTree, "
"rather than by pausing or hiding them. You don't have to delete a detached "
"node. You can for example, keep a reference to a node, detach it from the "
"scene tree using :ref:`Node.remove_child(node) "
"<class_Node_method_remove_child>`, then reattach it later using :ref:`Node."
"add_child(node) <class_Node_method_add_child>`. This can be very useful for "
"adding and removing areas from a game, for example."
msgstr ""

#: ../../docs/tutorials/performance/cpu_optimization.rst:231
msgid ""
"You can avoid the SceneTree altogether by using Server APIs. For more "
"information, see :ref:`doc_using_servers`."
msgstr ""

#: ../../docs/tutorials/performance/cpu_optimization.rst:237
msgid ""
"In some situations, physics can end up becoming a bottleneck. This is "
"particularly the case with complex worlds and large numbers of physics "
"objects."
msgstr ""

#: ../../docs/tutorials/performance/cpu_optimization.rst:240
#, fuzzy
msgid "Here are some techniques to speed up physics:"
msgstr "Ne postoje ograničenja prilikom korištenja Godot-a"

#: ../../docs/tutorials/performance/cpu_optimization.rst:242
msgid ""
"Try using simplified versions of your rendered geometry for collision "
"shapes. Often, this won't be noticeable for end users, but can greatly "
"increase performance."
msgstr ""

#: ../../docs/tutorials/performance/cpu_optimization.rst:245
msgid ""
"Try removing objects from physics when they are out of view / outside the "
"current area, or reusing physics objects (maybe you allow 8 monsters per "
"area, for example, and reuse these)."
msgstr ""

#: ../../docs/tutorials/performance/cpu_optimization.rst:249
msgid ""
"Another crucial aspect to physics is the physics tick rate. In some games, "
"you can greatly reduce the tick rate, and instead of for example, updating "
"physics 60 times per second, you may update them only 30 or even 20 times "
"per second. This can greatly reduce the CPU load."
msgstr ""

#: ../../docs/tutorials/performance/cpu_optimization.rst:254
msgid ""
"The downside of changing physics tick rate is you can get jerky movement or "
"jitter when the physics update rate does not match the frames per second "
"rendered. Also, decreasing the physics tick rate will increase input lag. "
"It's recommended to stick to the default physics tick rate (60 Hz) in most "
"games that feature real-time player movement."
msgstr ""

#: ../../docs/tutorials/performance/cpu_optimization.rst:260
msgid ""
"The solution to jitter is to use *fixed timestep interpolation*, which "
"involves smoothing the rendered positions and rotations over multiple frames "
"to match the physics. You can either implement this yourself or use a `third-"
"party addon <https://github.com/lawnjelly/smoothing-addon>`__. Performance-"
"wise, interpolation is a very cheap operation compared to running a physics "
"tick. It's orders of magnitude faster, so this can be a significant "
"performance win while also reducing jitter."
msgstr ""

#: ../../docs/tutorials/performance/gpu_optimization.rst:4
msgid "GPU optimization"
msgstr ""

#: ../../docs/tutorials/performance/gpu_optimization.rst:9
msgid ""
"The demand for new graphics features and progress almost guarantees that you "
"will encounter graphics bottlenecks. Some of these can be on the CPU side, "
"for instance in calculations inside the Godot engine to prepare objects for "
"rendering. Bottlenecks can also occur on the CPU in the graphics driver, "
"which sorts instructions to pass to the GPU, and in the transfer of these "
"instructions. And finally, bottlenecks also occur on the GPU itself."
msgstr ""

#: ../../docs/tutorials/performance/gpu_optimization.rst:16
msgid ""
"Where bottlenecks occur in rendering is highly hardware-specific. Mobile "
"GPUs in particular may struggle with scenes that run easily on desktop."
msgstr ""

#: ../../docs/tutorials/performance/gpu_optimization.rst:19
msgid ""
"Understanding and investigating GPU bottlenecks is slightly different to the "
"situation on the CPU. This is because, often, you can only change "
"performance indirectly by changing the instructions you give to the GPU. "
"Also, it may be more difficult to take measurements. In many cases, the only "
"way of measuring performance is by examining changes in the time spent "
"rendering each frame."
msgstr ""

#: ../../docs/tutorials/performance/gpu_optimization.rst:26
msgid "Draw calls, state changes, and APIs"
msgstr ""

#: ../../docs/tutorials/performance/gpu_optimization.rst:28
msgid ""
"The following section is not relevant to end-users, but is useful to provide "
"background information that is relevant in later sections."
msgstr ""

#: ../../docs/tutorials/performance/gpu_optimization.rst:31
msgid ""
"Godot sends instructions to the GPU via a graphics API (Vulkan, OpenGL, "
"OpenGL ES or WebGL). The communication and driver activity involved can be "
"quite costly, especially in OpenGL, OpenGL ES and WebGL. If we can provide "
"these instructions in a way that is preferred by the driver and GPU, we can "
"greatly increase performance."
msgstr ""

#: ../../docs/tutorials/performance/gpu_optimization.rst:37
msgid ""
"Nearly every API command in OpenGL requires a certain amount of validation "
"to make sure the GPU is in the correct state. Even seemingly simple commands "
"can lead to a flurry of behind-the-scenes housekeeping. Therefore, the goal "
"is to reduce these instructions to a bare minimum and group together similar "
"objects as much as possible so they can be rendered together, or with the "
"minimum number of these expensive state changes."
msgstr ""

#: ../../docs/tutorials/performance/gpu_optimization.rst:45
msgid "2D batching"
msgstr ""

#: ../../docs/tutorials/performance/gpu_optimization.rst:47
msgid ""
"In 2D, the costs of treating each item individually can be prohibitively "
"high - there can easily be thousands of them on the screen. This is why 2D "
"*batching* is used with OpenGL-based rendering methods. Multiple similar "
"items are grouped together and rendered in a batch, via a single draw call, "
"rather than making a separate draw call for each item. In addition, this "
"means state changes, material and texture changes can be kept to a minimum."
msgstr ""

#: ../../docs/tutorials/performance/gpu_optimization.rst:54
msgid ""
"Vulkan-based rendering methods do not use 2D batching yet. Since draw calls "
"are much cheaper with Vulkan compared to OpenGL, there is less of a need to "
"have 2D batching (although it can still be beneficial in some cases)."
msgstr ""

#: ../../docs/tutorials/performance/gpu_optimization.rst:59
msgid "3D batching"
msgstr ""

#: ../../docs/tutorials/performance/gpu_optimization.rst:61
msgid ""
"In 3D, we still aim to minimize draw calls and state changes. However, it "
"can be more difficult to batch together several objects into a single draw "
"call. 3D meshes tend to comprise hundreds or thousands of triangles, and "
"combining large meshes in real-time is prohibitively expensive. The costs of "
"joining them quickly exceeds any benefits as the number of triangles grows "
"per mesh. A much better alternative is to **join meshes ahead of time** "
"(static meshes in relation to each other). This can be done by artists, or "
"programmatically within Godot using an add-on."
msgstr ""

#: ../../docs/tutorials/performance/gpu_optimization.rst:69
msgid ""
"There is also a cost to batching together objects in 3D. Several objects "
"rendered as one cannot be individually culled. An entire city that is off-"
"screen will still be rendered if it is joined to a single blade of grass "
"that is on screen. Thus, you should always take objects' location and "
"culling into account when attempting to batch 3D objects together. Despite "
"this, the benefits of joining static objects often outweigh other "
"considerations, especially for large numbers of distant or low-poly objects."
msgstr ""

#: ../../docs/tutorials/performance/gpu_optimization.rst:77
msgid ""
"For more information on 3D specific optimizations, see :ref:"
"`doc_optimizing_3d_performance`."
msgstr ""

#: ../../docs/tutorials/performance/gpu_optimization.rst:81
msgid "Reuse shaders and materials"
msgstr ""

#: ../../docs/tutorials/performance/gpu_optimization.rst:83
msgid ""
"The Godot renderer is a little different to what is out there. It's designed "
"to minimize GPU state changes as much as possible. :ref:`StandardMaterial3D "
"<class_StandardMaterial3D>` does a good job at reusing materials that need "
"similar shaders. If custom shaders are used, make sure to reuse them as much "
"as possible. Godot's priorities are:"
msgstr ""

#: ../../docs/tutorials/performance/gpu_optimization.rst:89
msgid ""
"**Reusing Materials:** The fewer different materials in the scene, the "
"faster the rendering will be. If a scene has a huge amount of objects (in "
"the hundreds or thousands), try reusing the materials. In the worst case, "
"use atlases to decrease the amount of texture changes."
msgstr ""

#: ../../docs/tutorials/performance/gpu_optimization.rst:93
msgid ""
"**Reusing Shaders:** If materials can't be reused, at least try to reuse "
"shaders. Note: shaders are automatically reused between StandardMaterial3Ds "
"that share the same configuration (features that are enabled or disabled "
"with a check box) even if they have different parameters."
msgstr ""

#: ../../docs/tutorials/performance/gpu_optimization.rst:99
msgid ""
"If a scene has, for example, 20,000 objects with 20,000 different materials "
"each, rendering will be slow. If the same scene has 20,000 objects, but only "
"uses 100 materials, rendering will be much faster."
msgstr ""

#: ../../docs/tutorials/performance/gpu_optimization.rst:104
msgid "Pixel cost versus vertex cost"
msgstr ""

#: ../../docs/tutorials/performance/gpu_optimization.rst:106
msgid ""
"You may have heard that the lower the number of polygons in a model, the "
"faster it will be rendered. This is *really* relative and depends on many "
"factors."
msgstr ""

#: ../../docs/tutorials/performance/gpu_optimization.rst:109
msgid ""
"On a modern PC and console, vertex cost is low. GPUs originally only "
"rendered triangles. This meant that every frame:"
msgstr ""

#: ../../docs/tutorials/performance/gpu_optimization.rst:112
msgid "All vertices had to be transformed by the CPU (including clipping)."
msgstr ""

#: ../../docs/tutorials/performance/gpu_optimization.rst:113
msgid "All vertices had to be sent to the GPU memory from the main RAM."
msgstr ""

#: ../../docs/tutorials/performance/gpu_optimization.rst:115
msgid ""
"Nowadays, all this is handled inside the GPU, greatly increasing "
"performance. 3D artists usually have the wrong feeling about polycount "
"performance because 3D modeling software (such as Blender, 3ds Max, etc.) "
"need to keep geometry in CPU memory for it to be edited, reducing actual "
"performance. Game engines rely on the GPU more, so they can render many "
"triangles much more efficiently."
msgstr ""

#: ../../docs/tutorials/performance/gpu_optimization.rst:121
msgid ""
"On mobile devices, the story is different. PC and console GPUs are brute-"
"force monsters that can pull as much electricity as they need from the power "
"grid. Mobile GPUs are limited to a tiny battery, so they need to be a lot "
"more power efficient."
msgstr ""

#: ../../docs/tutorials/performance/gpu_optimization.rst:126
msgid ""
"To be more efficient, mobile GPUs attempt to avoid *overdraw*. Overdraw "
"occurs when the same pixel on the screen is being rendered more than once. "
"Imagine a town with several buildings. GPUs don't know what is visible and "
"what is hidden until they draw it. For example, a house might be drawn and "
"then another house in front of it (which means rendering happened twice for "
"the same pixel). PC GPUs normally don't care much about this and just throw "
"more pixel processors to the hardware to increase performance (which also "
"increases power consumption)."
msgstr ""

#: ../../docs/tutorials/performance/gpu_optimization.rst:134
msgid ""
"Using more power is not an option on mobile so mobile devices use a "
"technique called *tile-based rendering* which divides the screen into a "
"grid. Each cell keeps the list of triangles drawn to it and sorts them by "
"depth to minimize *overdraw*. This technique improves performance and "
"reduces power consumption, but takes a toll on vertex performance. As a "
"result, fewer vertices and triangles can be processed for drawing."
msgstr ""

#: ../../docs/tutorials/performance/gpu_optimization.rst:141
msgid ""
"Additionally, tile-based rendering struggles when there are small objects "
"with a lot of geometry within a small portion of the screen. This forces "
"mobile GPUs to put a lot of strain on a single screen tile, which "
"considerably decreases performance as all the other cells must wait for it "
"to complete before displaying the frame."
msgstr ""

#: ../../docs/tutorials/performance/gpu_optimization.rst:147
msgid ""
"To summarize, don't worry about vertex count on mobile, but **avoid "
"concentration of vertices in small parts of the screen**. If a character, "
"NPC, vehicle, etc. is far away (which means it looks tiny), use a smaller "
"level of detail (LOD) model. Even on desktop GPUs, it's preferable to avoid "
"having triangles smaller than the size of a pixel on screen."
msgstr ""

#: ../../docs/tutorials/performance/gpu_optimization.rst:153
msgid "Pay attention to the additional vertex processing required when using:"
msgstr ""

#: ../../docs/tutorials/performance/gpu_optimization.rst:155
msgid "Skinning (skeletal animation)"
msgstr ""

#: ../../docs/tutorials/performance/gpu_optimization.rst:156
msgid "Morphs (shape keys)"
msgstr ""

#: ../../docs/tutorials/performance/gpu_optimization.rst:162
msgid "Pixel/fragment shaders and fill rate"
msgstr ""

#: ../../docs/tutorials/performance/gpu_optimization.rst:164
msgid ""
"In contrast to vertex processing, the costs of fragment (per-pixel) shading "
"have increased dramatically over the years. Screen resolutions have "
"increased: the area of a 4K screen is 8,294,400 pixels, versus 307,200 for "
"an old 640×480 VGA screen. That is 27 times the area! Also, the complexity "
"of fragment shaders has exploded. Physically-based rendering requires "
"complex calculations for each fragment."
msgstr ""

#: ../../docs/tutorials/performance/gpu_optimization.rst:171
msgid ""
"You can test whether a project is fill rate-limited quite easily. Turn off V-"
"Sync to prevent capping the frames per second, then compare the frames per "
"second when running with a large window, to running with a very small "
"window. You may also benefit from similarly reducing your shadow map size if "
"using shadows. Usually, you will find the FPS increases quite a bit using a "
"small window, which indicates you are to some extent fill rate-limited. On "
"the other hand, if there is little to no increase in FPS, then your "
"bottleneck lies elsewhere."
msgstr ""

#: ../../docs/tutorials/performance/gpu_optimization.rst:180
msgid ""
"You can increase performance in a fill rate-limited project by reducing the "
"amount of work the GPU has to do. You can do this by simplifying the shader "
"(perhaps turn off expensive options if you are using a :ref:"
"`StandardMaterial3D <class_StandardMaterial3D>`), or reducing the number and "
"size of textures used. Also, when using non-unshaded particles, consider "
"forcing vertex shading in their material to decrease the shading cost."
msgstr ""

#: ../../docs/tutorials/performance/gpu_optimization.rst:189
msgid ""
"On supported hardware, :ref:`doc_variable_rate_shading` can be used to "
"reduce shading processing costs without impacting the sharpness of edges on "
"the final image."
msgstr ""

#: ../../docs/tutorials/performance/gpu_optimization.rst:193
msgid ""
"**When targeting mobile devices, consider using the simplest possible "
"shaders you can reasonably afford to use.**"
msgstr ""

#: ../../docs/tutorials/performance/gpu_optimization.rst:197
#, fuzzy
msgid "Reading textures"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/performance/gpu_optimization.rst:199
msgid ""
"The other factor in fragment shaders is the cost of reading textures. "
"Reading textures is an expensive operation, especially when reading from "
"several textures in a single fragment shader. Also, consider that filtering "
"may slow it down further (trilinear filtering between mipmaps, and "
"averaging). Reading textures is also expensive in terms of power usage, "
"which is a big issue on mobiles."
msgstr ""

#: ../../docs/tutorials/performance/gpu_optimization.rst:206
msgid ""
"**If you use third-party shaders or write your own shaders, try to use "
"algorithms that require as few texture reads as possible.**"
msgstr ""

#: ../../docs/tutorials/performance/gpu_optimization.rst:210
msgid "Texture compression"
msgstr ""

#: ../../docs/tutorials/performance/gpu_optimization.rst:212
msgid ""
"By default, Godot compresses textures of 3D models when imported using video "
"RAM (VRAM) compression. Video RAM compression isn't as efficient in size as "
"PNG or JPG when stored, but increases performance enormously when drawing "
"large enough textures."
msgstr ""

#: ../../docs/tutorials/performance/gpu_optimization.rst:217
msgid ""
"This is because the main goal of texture compression is bandwidth reduction "
"between memory and the GPU."
msgstr ""

#: ../../docs/tutorials/performance/gpu_optimization.rst:220
msgid ""
"In 3D, the shapes of objects depend more on the geometry than the texture, "
"so compression is generally not noticeable. In 2D, compression depends more "
"on shapes inside the textures, so the artifacts resulting from 2D "
"compression are more noticeable."
msgstr ""

#: ../../docs/tutorials/performance/gpu_optimization.rst:225
msgid ""
"As a warning, most Android devices do not support texture compression of "
"textures with transparency (only opaque), so keep this in mind."
msgstr ""

#: ../../docs/tutorials/performance/gpu_optimization.rst:235
msgid "Post-processing and shadows"
msgstr ""

#: ../../docs/tutorials/performance/gpu_optimization.rst:237
msgid ""
"Post-processing effects and shadows can also be expensive in terms of "
"fragment shading activity. Always test the impact of these on different "
"hardware."
msgstr ""

#: ../../docs/tutorials/performance/gpu_optimization.rst:240
msgid ""
"**Reducing the size of shadowmaps can increase performance**, both in terms "
"of writing and reading the shadowmaps. On top of that, the best way to "
"improve performance of shadows is to turn shadows off for as many lights and "
"objects as possible. Smaller or distant OmniLights/SpotLights can often have "
"their shadows disabled with only a small visual impact."
msgstr ""

#: ../../docs/tutorials/performance/gpu_optimization.rst:247
msgid "Transparency and blending"
msgstr ""

#: ../../docs/tutorials/performance/gpu_optimization.rst:249
msgid ""
"Transparent objects present particular problems for rendering efficiency. "
"Opaque objects (especially in 3D) can be essentially rendered in any order "
"and the Z-buffer will ensure that only the front most objects get shaded. "
"Transparent or blended objects are different. In most cases, they cannot "
"rely on the Z-buffer and must be rendered in \"painter's order\" (i.e. from "
"back to front) to look correct."
msgstr ""

#: ../../docs/tutorials/performance/gpu_optimization.rst:256
msgid ""
"Transparent objects are also particularly bad for fill rate, because every "
"item has to be drawn even if other transparent objects will be drawn on top "
"later on."
msgstr ""

#: ../../docs/tutorials/performance/gpu_optimization.rst:260
msgid ""
"Opaque objects don't have to do this. They can usually take advantage of the "
"Z-buffer by writing to the Z-buffer only first, then only performing the "
"fragment shader on the \"winning\" fragment, the object that is at the front "
"at a particular pixel."
msgstr ""

#: ../../docs/tutorials/performance/gpu_optimization.rst:265
msgid ""
"Transparency is particularly expensive where multiple transparent objects "
"overlap. It is usually better to use transparent areas as small as possible "
"to minimize these fill rate requirements, especially on mobile, where fill "
"rate is very expensive. Indeed, in many situations, rendering more complex "
"opaque geometry can end up being faster than using transparency to \"cheat\"."
msgstr ""

#: ../../docs/tutorials/performance/gpu_optimization.rst:272
msgid "Multi-platform advice"
msgstr ""

#: ../../docs/tutorials/performance/gpu_optimization.rst:274
msgid ""
"If you are aiming to release on multiple platforms, test *early* and test "
"*often* on all your platforms, especially mobile. Developing a game on "
"desktop but attempting to port it to mobile at the last minute is a recipe "
"for disaster."
msgstr ""

#: ../../docs/tutorials/performance/gpu_optimization.rst:278
msgid ""
"In general, you should design your game for the lowest common denominator, "
"then add optional enhancements for more powerful platforms. For example, you "
"may want to use the Compatibility rendering method for both desktop and "
"mobile platforms where you target both."
msgstr ""

#: ../../docs/tutorials/performance/gpu_optimization.rst:284
msgid "Mobile/tiled renderers"
msgstr ""

#: ../../docs/tutorials/performance/gpu_optimization.rst:286
msgid ""
"As described above, GPUs on mobile devices work in dramatically different "
"ways from GPUs on desktop. Most mobile devices use tile renderers. Tile "
"renderers split up the screen into regular-sized tiles that fit into super "
"fast cache memory, which reduces the number of read/write operations to the "
"main memory."
msgstr ""

#: ../../docs/tutorials/performance/gpu_optimization.rst:291
msgid ""
"There are some downsides though. Tiled rendering can make certain techniques "
"much more complicated and expensive to perform. Tiles that rely on the "
"results of rendering in different tiles or on the results of earlier "
"operations being preserved can be very slow. Be very careful to test the "
"performance of shaders, viewport textures and post processing."
msgstr ""

#: ../../docs/tutorials/performance/using_multimesh.rst:6
msgid "Optimization using MultiMeshes"
msgstr ""

#: ../../docs/tutorials/performance/using_multimesh.rst:8
msgid ""
"For large amount of instances (in the thousands), that need to be constantly "
"processed (and certain amount of control needs to be retained), :ref:`using "
"servers directly <doc_using_servers>` is the recommended optimization."
msgstr ""

#: ../../docs/tutorials/performance/using_multimesh.rst:12
msgid ""
"When the amount of objects reach the hundreds of thousands or millions, none "
"of these approaches are efficient anymore. Still, depending on the "
"requirements, there is one more optimization possible."
msgstr ""

#: ../../docs/tutorials/performance/using_multimesh.rst:17
msgid "MultiMeshes"
msgstr ""

#: ../../docs/tutorials/performance/using_multimesh.rst:19
msgid ""
"A :ref:`MultiMesh<class_MultiMesh>` is a single draw primitive that can draw "
"up to millions of objects in one go. It's extremely efficient because it "
"uses the GPU hardware to do this (in OpenGL ES 2.0, it's less efficient "
"because there is no hardware support for it, though)."
msgstr ""

#: ../../docs/tutorials/performance/using_multimesh.rst:23
msgid ""
"The only drawback is that there is no *screen* or *frustum* culling possible "
"for individual instances. This means, that millions of objects will be "
"*always* or *never* drawn, depending on the visibility of the whole "
"MultiMesh. It is possible to provide a custom visibility rect for them, but "
"it will always be *all-or-none* visibility."
msgstr ""

#: ../../docs/tutorials/performance/using_multimesh.rst:28
msgid ""
"If the objects are simple enough (just a couple of vertices), this is "
"generally not much of a problem as most modern GPUs are optimized for this "
"use case. A workaround is to create several MultiMeshes for different areas "
"of the world."
msgstr ""

#: ../../docs/tutorials/performance/using_multimesh.rst:32
msgid ""
"It is also possible to execute some logic inside the vertex shader (using "
"the ``INSTANCE_ID`` or ``INSTANCE_CUSTOM`` built-in constants). For an "
"example of animating thousands of objects in a MultiMesh, see the :ref:"
"`Animating thousands of fish <doc_animating_thousands_of_fish>` tutorial. "
"Information to the shader can be provided via textures (there are floating-"
"point :ref:`Image<class_Image>` formats which are ideal for this)."
msgstr ""

#: ../../docs/tutorials/performance/using_multimesh.rst:38
msgid ""
"Another alternative is to use a GDExtension and C++, which should be "
"extremely efficient (it's possible to set the entire state for all objects "
"using linear memory via the :ref:`RenderingServer.multimesh_set_buffer() "
"<class_RenderingServer_method_multimesh_set_buffer>` function). This way, "
"the array can be created with multiple threads, then set in one call, "
"providing high cache efficiency."
msgstr ""

#: ../../docs/tutorials/performance/using_multimesh.rst:44
msgid ""
"Finally, it's not required to have all MultiMesh instances visible. The "
"amount of visible ones can be controlled with the :ref:`MultiMesh."
"visible_instance_count <class_MultiMesh_property_visible_instance_count>` "
"property. The typical workflow is to allocate the maximum amount of "
"instances that will be used, then change the amount visible depending on how "
"many are currently needed."
msgstr ""

#: ../../docs/tutorials/performance/using_multimesh.rst:50
#, fuzzy
msgid "Multimesh example"
msgstr "Windows"

#: ../../docs/tutorials/performance/using_multimesh.rst:52
msgid ""
"Here is an example of using a MultiMesh from code. Languages other than "
"GDScript may be more efficient for millions of objects, but for a few "
"thousands, GDScript should be fine."
msgstr ""

#: ../../docs/tutorials/performance/optimizing_3d_performance.rst:-1
msgid "optimization"
msgstr ""

#: ../../docs/tutorials/performance/optimizing_3d_performance.rst:7
msgid "Optimizing 3D performance"
msgstr ""

#: ../../docs/tutorials/performance/optimizing_3d_performance.rst:10
msgid "Culling"
msgstr ""

#: ../../docs/tutorials/performance/optimizing_3d_performance.rst:12
msgid ""
"Godot will automatically perform view frustum culling in order to prevent "
"rendering objects that are outside the viewport. This works well for games "
"that take place in a small area, however things can quickly become "
"problematic in larger levels."
msgstr ""

#: ../../docs/tutorials/performance/optimizing_3d_performance.rst:20
msgid ""
"Walking around a town for example, you may only be able to see a few "
"buildings in the street you are in, as well as the sky and a few birds "
"flying overhead. As far as a naive renderer is concerned however, you can "
"still see the entire town. It won't just render the buildings in front of "
"you, it will render the street behind that, with the people on that street, "
"the buildings behind that. You quickly end up in situations where you are "
"attempting to render 10× or 100× more than what is visible."
msgstr ""

#: ../../docs/tutorials/performance/optimizing_3d_performance.rst:28
msgid ""
"Things aren't quite as bad as they seem, because the Z-buffer usually allows "
"the GPU to only fully shade the objects that are at the front. This is "
"called *depth prepass* and is enabled by default in Godot when using the "
"Forward+ or Compatibility rendering methods. However, unneeded objects are "
"still reducing performance."
msgstr ""

#: ../../docs/tutorials/performance/optimizing_3d_performance.rst:34
msgid ""
"One way we can potentially reduce the amount to be rendered is to **take "
"advantage of occlusion**. Godot 4.0 and later offers a new approach to "
"occlusion culling using occluder nodes. See :ref:`doc_occlusion_culling` for "
"instructions on setting up occlusion culling in your scene."
msgstr ""

#: ../../docs/tutorials/performance/optimizing_3d_performance.rst:41
msgid ""
"In some cases, you may have to adapt your level design to add more occlusion "
"opportunities. For example, you may have to add more walls to prevent the "
"player from seeing too far away, which would decrease performance due to the "
"lost opportunities for occlusion culling."
msgstr ""

#: ../../docs/tutorials/performance/optimizing_3d_performance.rst:47
msgid "Transparent objects"
msgstr ""

#: ../../docs/tutorials/performance/optimizing_3d_performance.rst:49
msgid ""
"Godot sorts objects by :ref:`Material <class_Material>` and :ref:`Shader "
"<class_Shader>` to improve performance. This, however, can not be done with "
"transparent objects. Transparent objects are rendered from back to front to "
"make blending with what is behind work. As a result, **try to use as few "
"transparent objects as possible**. If an object has a small section with "
"transparency, try to make that section a separate surface with its own "
"material."
msgstr ""

#: ../../docs/tutorials/performance/optimizing_3d_performance.rst:57
msgid ""
"For more information, see the :ref:`GPU optimizations "
"<doc_gpu_optimization>` doc."
msgstr ""

#: ../../docs/tutorials/performance/optimizing_3d_performance.rst:61
msgid "Level of detail (LOD)"
msgstr ""

#: ../../docs/tutorials/performance/optimizing_3d_performance.rst:63
msgid ""
"In some situations, particularly at a distance, it can be a good idea to "
"**replace complex geometry with simpler versions**. The end user will "
"probably not be able to see much difference. Consider looking at a large "
"number of trees in the far distance. There are several strategies for "
"replacing models at varying distance. You could use lower poly models, or "
"use transparency to simulate more complex geometry."
msgstr ""

#: ../../docs/tutorials/performance/optimizing_3d_performance.rst:70
msgid "Godot 4 offers several ways to control level of detail:"
msgstr ""

#: ../../docs/tutorials/performance/optimizing_3d_performance.rst:72
msgid "An automatic approach on mesh import using :ref:`doc_mesh_lod`."
msgstr ""

#: ../../docs/tutorials/performance/optimizing_3d_performance.rst:73
msgid ""
"A manual approach configured in the 3D node using :ref:"
"`doc_visibility_ranges`."
msgstr ""

#: ../../docs/tutorials/performance/optimizing_3d_performance.rst:74
msgid ""
":ref:`Decals <doc_using_decals>` and :ref:`lights <doc_lights_and_shadows>` "
"can also benefit from level of detail using their respective **Distance "
"Fade** properties."
msgstr ""

#: ../../docs/tutorials/performance/optimizing_3d_performance.rst:78
msgid ""
"While they can be used independently, these approaches are most effective "
"when used together. For example, you can set up visibility ranges to hide "
"particle effects that are too far away from the player to notice. At the "
"same time, you can rely on mesh LOD to make the particle effect's meshes "
"rendered with less detail at a distance."
msgstr ""

#: ../../docs/tutorials/performance/optimizing_3d_performance.rst:84
msgid ""
"Visibility ranges are also a good way to set up *impostors* for distant "
"geometry (see below)."
msgstr ""

#: ../../docs/tutorials/performance/optimizing_3d_performance.rst:88
msgid "Billboards and imposters"
msgstr ""

#: ../../docs/tutorials/performance/optimizing_3d_performance.rst:90
msgid ""
"The simplest version of using transparency to deal with LOD is billboards. "
"For example, you can use a single transparent quad to represent a tree at "
"distance. This can be very cheap to render, unless of course, there are many "
"trees in front of each other. In this case, transparency may start eating "
"into fill rate (for more information on fill rate, see :ref:"
"`doc_gpu_optimization`)."
msgstr ""

#: ../../docs/tutorials/performance/optimizing_3d_performance.rst:96
msgid ""
"An alternative is to render not just one tree, but a number of trees "
"together as a group. This can be especially effective if you can see an area "
"but cannot physically approach it in a game."
msgstr ""

#: ../../docs/tutorials/performance/optimizing_3d_performance.rst:100
msgid ""
"You can make imposters by pre-rendering views of an object at different "
"angles. Or you can even go one step further, and periodically re-render a "
"view of an object onto a texture to be used as an imposter. At a distance, "
"you need to move the viewer a considerable distance for the angle of view to "
"change significantly. This can be complex to get working, but may be worth "
"it depending on the type of project you are making."
msgstr ""

#: ../../docs/tutorials/performance/optimizing_3d_performance.rst:108
msgid "Use instancing (MultiMesh)"
msgstr ""

#: ../../docs/tutorials/performance/optimizing_3d_performance.rst:110
msgid ""
"If several identical objects have to be drawn in the same place or nearby, "
"try using :ref:`MultiMesh <class_MultiMesh>` instead. MultiMesh allows the "
"drawing of many thousands of objects at very little performance cost, making "
"it ideal for flocks, grass, particles, and anything else where you have "
"thousands of identical objects."
msgstr ""

#: ../../docs/tutorials/performance/optimizing_3d_performance.rst:116
msgid ""
"See also the :ref:`Using MultiMesh <doc_using_multimesh>` documentation."
msgstr ""

#: ../../docs/tutorials/performance/optimizing_3d_performance.rst:119
msgid "Bake lighting"
msgstr ""

#: ../../docs/tutorials/performance/optimizing_3d_performance.rst:121
msgid ""
"Lighting objects is one of the most costly rendering operations. Realtime "
"lighting, shadows (especially multiple lights), and :ref:`global "
"illumination <doc_introduction_to_global_illumination>` are especially "
"expensive. They may simply be too much for lower power mobile devices to "
"handle."
msgstr ""

#: ../../docs/tutorials/performance/optimizing_3d_performance.rst:126
msgid ""
"**Consider using baked lighting**, especially for mobile. This can look "
"fantastic, but has the downside that it will not be dynamic. Sometimes, this "
"is a tradeoff worth making."
msgstr ""

#: ../../docs/tutorials/performance/optimizing_3d_performance.rst:130
msgid ""
"See :ref:`doc_using_lightmap_gi` for instructions on using baked lightmaps. "
"For best performance, you should set lights' bake mode to **Static** as "
"opposed to the default **Dynamic**, as this will skip real-time lighting on "
"meshes that have baked lighting."
msgstr ""

#: ../../docs/tutorials/performance/optimizing_3d_performance.rst:135
msgid ""
"The downside of lights with the **Static** bake mode is that they can't cast "
"shadows onto meshes with baked lighting. This can make scenes with outdoor "
"environments and dynamic objects look flat. A good balance between "
"performance and quality is to keep **Dynamic** for the :ref:"
"`class_DirectionalLight3D` node, and use **Static** for most (if not all) "
"omni and spot lights."
msgstr ""

#: ../../docs/tutorials/performance/optimizing_3d_performance.rst:142
msgid "Animation and skinning"
msgstr ""

#: ../../docs/tutorials/performance/optimizing_3d_performance.rst:144
msgid ""
"Animation and vertex animation such as skinning and morphing can be very "
"expensive on some platforms. You may need to lower the polycount "
"considerably for animated models, or limit the number of them on screen at "
"any given time. You can also reduce the animation rate for distant or "
"occluded meshes, or pause the animation entirely if the player is unlikely "
"to notice the animation being stopped."
msgstr ""

#: ../../docs/tutorials/performance/optimizing_3d_performance.rst:151
msgid ""
"The :ref:`class_VisibleOnScreenEnabler3D` and :ref:"
"`class_VisibleOnScreenNotifier3D` nodes can be useful for this purpose."
msgstr ""

#: ../../docs/tutorials/performance/optimizing_3d_performance.rst:155
msgid "Large worlds"
msgstr ""

#: ../../docs/tutorials/performance/optimizing_3d_performance.rst:157
msgid ""
"If you are making large worlds, there are different considerations than what "
"you may be familiar with from smaller games."
msgstr ""

#: ../../docs/tutorials/performance/optimizing_3d_performance.rst:160
msgid ""
"Large worlds may need to be built in tiles that can be loaded on demand as "
"you move around the world. This can prevent memory use from getting out of "
"hand, and also limit the processing needed to the local area."
msgstr ""

#: ../../docs/tutorials/performance/optimizing_3d_performance.rst:164
msgid ""
"There may also be rendering and physics glitches due to floating point error "
"in large worlds. This can be resolved using :ref:"
"`doc_large_world_coordinates`. If using large world coordinates is an "
"option, you may be able to use techniques such as orienting the world around "
"the player (rather than the other way around), or shifting the origin "
"periodically to keep things centred around ``Vector3(0, 0, 0)``."
msgstr ""

#: ../../docs/tutorials/performance/vertex_animation/index.rst:4
msgid "Animating thousands of objects"
msgstr ""

#: ../../docs/tutorials/performance/vertex_animation/animating_thousands_of_fish.rst:6
msgid "Animating thousands of fish with MultiMeshInstance3D"
msgstr ""

#: ../../docs/tutorials/performance/vertex_animation/animating_thousands_of_fish.rst:8
msgid ""
"This tutorial explores a technique used in the game `ABZU <https://www."
"gdcvault.com/play/1024409/Creating-the-Art-of-ABZ>`_ for rendering and "
"animating thousands of fish using vertex animation and static mesh "
"instancing."
msgstr ""

#: ../../docs/tutorials/performance/vertex_animation/animating_thousands_of_fish.rst:12
msgid ""
"In Godot, this can be accomplished with a custom :ref:`Shader "
"<class_Shader>` and a :ref:`MultiMeshInstance3D "
"<class_MultiMeshInstance3D>`. Using the following technique you can render "
"thousands of animated objects, even on low end hardware."
msgstr ""

#: ../../docs/tutorials/performance/vertex_animation/animating_thousands_of_fish.rst:16
msgid ""
"We will start by animating one fish. Then, we will see how to extend that "
"animation to thousands of fish."
msgstr ""

#: ../../docs/tutorials/performance/vertex_animation/animating_thousands_of_fish.rst:20
msgid "Animating one Fish"
msgstr ""

#: ../../docs/tutorials/performance/vertex_animation/animating_thousands_of_fish.rst:22
msgid ""
"We will start with a single fish. Load your fish model into a :ref:"
"`MeshInstance3D <class_MeshInstance3D>` and add a new :ref:`ShaderMaterial "
"<class_ShaderMaterial>`."
msgstr ""

#: ../../docs/tutorials/performance/vertex_animation/animating_thousands_of_fish.rst:25
msgid ""
"Here is the fish we will be using for the example images, you can use any "
"fish model you like."
msgstr ""

#: ../../docs/tutorials/performance/vertex_animation/animating_thousands_of_fish.rst:29
msgid ""
"The fish model in this tutorial is made by `QuaterniusDev <https://"
"quaternius.com>`_ and is shared with a creative commons license. CC0 1.0 "
"Universal (CC0 1.0) Public Domain Dedication https://creativecommons.org/"
"publicdomain/zero/1.0/"
msgstr ""

#: ../../docs/tutorials/performance/vertex_animation/animating_thousands_of_fish.rst:33
msgid ""
"Typically, you would use bones and a :ref:`Skeleton3D <class_Skeleton3D>` to "
"animate objects. However, bones are animated on the CPU and so you end "
"having to calculate thousands of operations every frame and it becomes "
"impossible to have thousands of objects. Using vertex animation in a vertex "
"shader, you avoid using bones and can instead calculate the full animation "
"in a few lines of code and completely on the GPU."
msgstr ""

#: ../../docs/tutorials/performance/vertex_animation/animating_thousands_of_fish.rst:39
msgid "The animation will be made of four key motions:"
msgstr ""

#: ../../docs/tutorials/performance/vertex_animation/animating_thousands_of_fish.rst:41
msgid "A side to side motion"
msgstr ""

#: ../../docs/tutorials/performance/vertex_animation/animating_thousands_of_fish.rst:42
msgid "A pivot motion around the center of the fish"
msgstr ""

#: ../../docs/tutorials/performance/vertex_animation/animating_thousands_of_fish.rst:43
msgid "A panning wave motion"
msgstr ""

#: ../../docs/tutorials/performance/vertex_animation/animating_thousands_of_fish.rst:44
msgid "A panning twist motion"
msgstr ""

#: ../../docs/tutorials/performance/vertex_animation/animating_thousands_of_fish.rst:46
msgid ""
"All the code for the animation will be in the vertex shader with uniforms "
"controlling the amount of motion. We use uniforms to control the strength of "
"the motion so that you can tweak the animation in editor and see the results "
"in real time, without the shader having to recompile."
msgstr ""

#: ../../docs/tutorials/performance/vertex_animation/animating_thousands_of_fish.rst:50
msgid ""
"All the motions will be made using cosine waves applied to ``VERTEX`` in "
"model space. We want the vertices to be in model space so that the motion is "
"always relative to the orientation of the fish. For example, side-to-side "
"will always move the fish back and forth in its left to right direction, "
"instead of on the ``x`` axis in the world orientation."
msgstr ""

#: ../../docs/tutorials/performance/vertex_animation/animating_thousands_of_fish.rst:55
msgid ""
"In order to control the speed of the animation, we will start by defining "
"our own time variable using ``TIME``."
msgstr ""

#: ../../docs/tutorials/performance/vertex_animation/animating_thousands_of_fish.rst:62
msgid ""
"The first motion we will implement is the side to side motion. It can be "
"made by offsetting ``VERTEX.x`` by ``cos`` of ``TIME``. Each time the mesh "
"is rendered, all the vertices will move to the side by the amount of "
"``cos(time)``."
msgstr ""

#: ../../docs/tutorials/performance/vertex_animation/animating_thousands_of_fish.rst:71
msgid "The resulting animation should look something like this:"
msgstr ""

#: ../../docs/tutorials/performance/vertex_animation/animating_thousands_of_fish.rst:75
msgid ""
"Next, we add the pivot. Because the fish is centered at (0, 0), all we have "
"to do is multiply ``VERTEX`` by a rotation matrix for it to rotate around "
"the center of the fish."
msgstr ""

#: ../../docs/tutorials/performance/vertex_animation/animating_thousands_of_fish.rst:78
msgid "We construct a rotation matrix like so:"
msgstr ""

#: ../../docs/tutorials/performance/vertex_animation/animating_thousands_of_fish.rst:87
msgid ""
"And then we apply it in the ``x`` and ``z`` axes by multiplying it by "
"``VERTEX.xz``."
msgstr ""

#: ../../docs/tutorials/performance/vertex_animation/animating_thousands_of_fish.rst:93
msgid "With only the pivot applied you should see something like this:"
msgstr ""

#: ../../docs/tutorials/performance/vertex_animation/animating_thousands_of_fish.rst:97
msgid ""
"The next two motions need to pan down the spine of the fish. For that, we "
"need a new variable, ``body``. ``body`` is a float that is ``0`` at the tail "
"of the fish and ``1`` at its head."
msgstr ""

#: ../../docs/tutorials/performance/vertex_animation/animating_thousands_of_fish.rst:104
msgid ""
"The next motion is a cosine wave that moves down the length of the fish. To "
"make it move along the spine of the fish, we offset the input to ``cos`` by "
"the position along the spine, which is the variable we defined above, "
"``body``."
msgstr ""

#: ../../docs/tutorials/performance/vertex_animation/animating_thousands_of_fish.rst:113
msgid ""
"This looks very similar to the side to side motion we defined above, but in "
"this one, by using ``body`` to offset ``cos`` each vertex along the spine "
"has a different position in the wave making it look like a wave is moving "
"along the fish."
msgstr ""

#: ../../docs/tutorials/performance/vertex_animation/animating_thousands_of_fish.rst:119
msgid ""
"The last motion is the twist, which is a panning roll along the spine. "
"Similarly to the pivot, we first construct a rotation matrix."
msgstr ""

#: ../../docs/tutorials/performance/vertex_animation/animating_thousands_of_fish.rst:128
msgid ""
"We apply the rotation in the ``xy`` axes so that the fish appears to roll "
"around its spine. For this to work, the fish's spine needs to be centered on "
"the ``z`` axis."
msgstr ""

#: ../../docs/tutorials/performance/vertex_animation/animating_thousands_of_fish.rst:135
msgid "Here is the fish with twist applied:"
msgstr ""

#: ../../docs/tutorials/performance/vertex_animation/animating_thousands_of_fish.rst:139
msgid ""
"If we apply all these motions one after another, we get a fluid jelly-like "
"motion."
msgstr ""

#: ../../docs/tutorials/performance/vertex_animation/animating_thousands_of_fish.rst:143
msgid ""
"Normal fish swim mostly with the back half of their body. Accordingly, we "
"need to limit the panning motions to the back half of the fish. To do this, "
"we create a new variable, ``mask``."
msgstr ""

#: ../../docs/tutorials/performance/vertex_animation/animating_thousands_of_fish.rst:146
msgid ""
"``mask`` is a float that goes from ``0`` at the front of the fish to ``1`` "
"at the end using ``smoothstep`` to control the point at which the transition "
"from ``0`` to ``1`` happens."
msgstr ""

#: ../../docs/tutorials/performance/vertex_animation/animating_thousands_of_fish.rst:154
msgid "Below is an image of the fish with ``mask`` used as ``COLOR``:"
msgstr ""

#: ../../docs/tutorials/performance/vertex_animation/animating_thousands_of_fish.rst:158
msgid ""
"For the wave, we multiply the motion by ``mask`` which will limit it to the "
"back half."
msgstr ""

#: ../../docs/tutorials/performance/vertex_animation/animating_thousands_of_fish.rst:165
msgid ""
"In order to apply the mask to the twist, we use ``mix``. ``mix`` allows us "
"to mix the vertex position between a fully rotated vertex and one that is "
"not rotated. We need to use ``mix`` instead of multiplying ``mask`` by the "
"rotated ``VERTEX`` because we are not adding the motion to the ``VERTEX`` we "
"are replacing the ``VERTEX`` with the rotated version. If we multiplied that "
"by ``mask``, we would shrink the fish."
msgstr ""

#: ../../docs/tutorials/performance/vertex_animation/animating_thousands_of_fish.rst:176
msgid "Putting the four motions together gives us the final animation."
msgstr ""

#: ../../docs/tutorials/performance/vertex_animation/animating_thousands_of_fish.rst:180
msgid ""
"Go ahead and play with the uniforms in order to alter the swim cycle of the "
"fish. You will find that you can create a wide variety of swim styles using "
"these four motions."
msgstr ""

#: ../../docs/tutorials/performance/vertex_animation/animating_thousands_of_fish.rst:184
msgid "Making a school of fish"
msgstr ""

#: ../../docs/tutorials/performance/vertex_animation/animating_thousands_of_fish.rst:186
msgid ""
"Godot makes it easy to render thousands of the same object using a "
"MultiMeshInstance3D node."
msgstr ""

#: ../../docs/tutorials/performance/vertex_animation/animating_thousands_of_fish.rst:188
msgid ""
"A MultiMeshInstance3D node is created and used the same way you would make a "
"MeshInstance3D node. For this tutorial, we will name the MultiMeshInstance3D "
"node ``School``, because it will contain a school of fish."
msgstr ""

#: ../../docs/tutorials/performance/vertex_animation/animating_thousands_of_fish.rst:192
msgid ""
"Once you have a MultiMeshInstance3D add a :ref:`MultiMesh "
"<class_MultiMesh>`, and to that MultiMesh add your :ref:`Mesh <class_Mesh>` "
"with the shader from above."
msgstr ""

#: ../../docs/tutorials/performance/vertex_animation/animating_thousands_of_fish.rst:195
msgid ""
"MultiMeshes draw your Mesh with three additional per-instance properties: "
"Transform (rotation, translation, scale), Color, and Custom. Custom is used "
"to pass in 4 multi-use variables using a :ref:`Color <class_Color>`."
msgstr ""

#: ../../docs/tutorials/performance/vertex_animation/animating_thousands_of_fish.rst:199
msgid ""
"``instance_count`` specifies how many instances of the mesh you want to "
"draw. For now, leave ``instance_count`` at ``0`` because you cannot change "
"any of the other parameters while ``instance_count`` is larger than ``0``. "
"We will set ``instance count`` in GDScript later."
msgstr ""

#: ../../docs/tutorials/performance/vertex_animation/animating_thousands_of_fish.rst:203
msgid ""
"``transform_format`` specifies whether the transforms used are 3D or 2D. For "
"this tutorial, select 3D."
msgstr ""

#: ../../docs/tutorials/performance/vertex_animation/animating_thousands_of_fish.rst:205
msgid ""
"For both ``color_format`` and ``custom_data_format`` you can choose between "
"``None``, ``Byte``, and ``Float``. ``None`` means you won't be passing in "
"that data (either a per-instance ``COLOR`` variable, or ``INSTANCE_CUSTOM``) "
"to the shader. ``Byte`` means each number making up the color you pass in "
"will be stored with 8 bits while ``Float`` means each number will be stored "
"in a floating-point number (32 bits). ``Float`` is slower but more precise, "
"``Byte`` will take less memory and be faster, but you may see some visual "
"artifacts."
msgstr ""

#: ../../docs/tutorials/performance/vertex_animation/animating_thousands_of_fish.rst:212
msgid "Now, set ``instance_count`` to the number of fish you want to have."
msgstr ""

#: ../../docs/tutorials/performance/vertex_animation/animating_thousands_of_fish.rst:214
msgid "Next we need to set the per-instance transforms."
msgstr ""

#: ../../docs/tutorials/performance/vertex_animation/animating_thousands_of_fish.rst:216
msgid ""
"There are two ways to set per-instance transforms for MultiMeshes. The first "
"is entirely in editor and is described in the :ref:`MultiMeshInstance3D "
"tutorial <doc_using_multi_mesh_instance>`."
msgstr ""

#: ../../docs/tutorials/performance/vertex_animation/animating_thousands_of_fish.rst:219
msgid ""
"The second is to loop over all the instances and set their transforms in "
"code. Below, we use GDScript to loop over all the instances and set their "
"transform to a random position."
msgstr ""

#: ../../docs/tutorials/performance/vertex_animation/animating_thousands_of_fish.rst:229
msgid ""
"Running this script will place the fish in random positions in a box around "
"the position of the MultiMeshInstance3D."
msgstr ""

#: ../../docs/tutorials/performance/vertex_animation/animating_thousands_of_fish.rst:232
msgid ""
"If performance is an issue for you, try running the scene with fewer fish."
msgstr ""

#: ../../docs/tutorials/performance/vertex_animation/animating_thousands_of_fish.rst:234
msgid ""
"Notice how all the fish are all in the same position in their swim cycle? It "
"makes them look very robotic. The next step is to give each fish a different "
"position in the swim cycle so the entire school looks more organic."
msgstr ""

#: ../../docs/tutorials/performance/vertex_animation/animating_thousands_of_fish.rst:239
msgid "Animating a school of fish"
msgstr ""

#: ../../docs/tutorials/performance/vertex_animation/animating_thousands_of_fish.rst:241
msgid ""
"One of the benefits of animating the fish using ``cos`` functions is that "
"they are animated with one parameter, ``time``. In order to give each fish a "
"unique position in the swim cycle, we only need to offset ``time``."
msgstr ""

#: ../../docs/tutorials/performance/vertex_animation/animating_thousands_of_fish.rst:245
msgid ""
"We do that by adding the per-instance custom value ``INSTANCE_CUSTOM`` to "
"``time``."
msgstr ""

#: ../../docs/tutorials/performance/vertex_animation/animating_thousands_of_fish.rst:251
msgid ""
"Next, we need to pass a value into ``INSTANCE_CUSTOM``. We do that by adding "
"one line into the ``for`` loop from above. In the ``for`` loop we assign "
"each instance a set of four random floats to use."
msgstr ""

#: ../../docs/tutorials/performance/vertex_animation/animating_thousands_of_fish.rst:259
msgid ""
"Now the fish all have unique positions in the swim cycle. You can give them "
"a little more individuality by using ``INSTANCE_CUSTOM`` to make them swim "
"faster or slower by multiplying by ``TIME``."
msgstr ""

#: ../../docs/tutorials/performance/vertex_animation/animating_thousands_of_fish.rst:268
msgid ""
"You can even experiment with changing the per-instance color the same way "
"you changed the per-instance custom value."
msgstr ""

#: ../../docs/tutorials/performance/vertex_animation/animating_thousands_of_fish.rst:271
msgid ""
"One problem that you will run into at this point is that the fish are "
"animated, but they are not moving. You can move them by updating the per-"
"instance transform for each fish every frame. Although doing so will be "
"faster than moving thousands of MeshInstance3Ds per frame, it'll still "
"likely be slow."
msgstr ""

#: ../../docs/tutorials/performance/vertex_animation/animating_thousands_of_fish.rst:276
msgid ""
"In the next tutorial we will cover how to use :ref:`GPUParticles3D "
"<class_GPUParticles3D>` to take advantage of the GPU and move each fish "
"around individually while still receiving the benefits of instancing."
msgstr ""

#: ../../docs/tutorials/performance/vertex_animation/controlling_thousands_of_fish.rst:6
msgid "Controlling thousands of fish with Particles"
msgstr ""

#: ../../docs/tutorials/performance/vertex_animation/controlling_thousands_of_fish.rst:8
msgid ""
"The problem with :ref:`MeshInstance3D <class_MeshInstance3D>` is that it is "
"expensive to update their transform array. It is great for placing many "
"static objects around the scene. But it is still difficult to move the "
"objects around the scene."
msgstr ""

#: ../../docs/tutorials/performance/vertex_animation/controlling_thousands_of_fish.rst:12
msgid ""
"To make each instance move in an interesting way, we will use a :ref:"
"`GPUParticles3D <class_GPUParticles3D>` node. Particles take advantage of "
"GPU acceleration by computing and setting the per-instance information in a :"
"ref:`Shader <class_Shader>`."
msgstr ""

#: ../../docs/tutorials/performance/vertex_animation/controlling_thousands_of_fish.rst:16
msgid ""
"First create a Particles node. Then, under \"Draw Passes\" set the "
"Particle's \"Draw Pass 1\" to your :ref:`Mesh <class_Mesh>`. Then under "
"\"Process Material\" create a new :ref:`ShaderMaterial "
"<class_ShaderMaterial>`."
msgstr ""

#: ../../docs/tutorials/performance/vertex_animation/controlling_thousands_of_fish.rst:20
msgid "Set the ``shader_type`` to ``particles``."
msgstr ""

#: ../../docs/tutorials/performance/vertex_animation/controlling_thousands_of_fish.rst:26
msgid "Then add the following two functions:"
msgstr ""

#: ../../docs/tutorials/performance/vertex_animation/controlling_thousands_of_fish.rst:50
msgid ""
"These functions come from the default :ref:`ParticleProcessMaterial "
"<class_ParticleProcessMaterial>`. They are used to generate a random number "
"from each particle's ``RANDOM_SEED``."
msgstr ""

#: ../../docs/tutorials/performance/vertex_animation/controlling_thousands_of_fish.rst:53
msgid ""
"A unique thing about particle shaders is that some built-in variables are "
"saved across frames. ``TRANSFORM``, ``COLOR``, and ``CUSTOM`` can all be "
"accessed in the shader of the mesh, and also in the particle shader the next "
"time it is run."
msgstr ""

#: ../../docs/tutorials/performance/vertex_animation/controlling_thousands_of_fish.rst:57
msgid ""
"Next, setup your ``start()`` function. Particles shaders contain a "
"``start()`` function and a ``process()`` function."
msgstr ""

#: ../../docs/tutorials/performance/vertex_animation/controlling_thousands_of_fish.rst:60
msgid ""
"The code in the ``start()`` function only runs when the particle system "
"starts. The code in the ``process()`` function will always run."
msgstr ""

#: ../../docs/tutorials/performance/vertex_animation/controlling_thousands_of_fish.rst:63
msgid ""
"We need to generate 4 random numbers: 3 to create a random position and one "
"for the random offset of the swim cycle."
msgstr ""

#: ../../docs/tutorials/performance/vertex_animation/controlling_thousands_of_fish.rst:66
msgid ""
"First, generate 4 seeds inside the ``start()`` function using the ``hash()`` "
"function provided above:"
msgstr ""

#: ../../docs/tutorials/performance/vertex_animation/controlling_thousands_of_fish.rst:75
msgid ""
"Then, use those seeds to generate random numbers using ``rand_from_seed``:"
msgstr ""

#: ../../docs/tutorials/performance/vertex_animation/controlling_thousands_of_fish.rst:84
msgid ""
"Finally, assign ``position`` to ``TRANSFORM[3].xyz``, which is the part of "
"the transform that holds the position information."
msgstr ""

#: ../../docs/tutorials/performance/vertex_animation/controlling_thousands_of_fish.rst:91
msgid "Remember, all this code so far goes inside the ``start()`` function."
msgstr ""

#: ../../docs/tutorials/performance/vertex_animation/controlling_thousands_of_fish.rst:93
msgid ""
"The vertex shader for your mesh can stay the exact same as it was in the "
"previous tutorial."
msgstr ""

#: ../../docs/tutorials/performance/vertex_animation/controlling_thousands_of_fish.rst:95
msgid ""
"Now you can move each fish individually each frame, either by adding to the "
"``TRANSFORM`` directly or by writing to ``VELOCITY``."
msgstr ""

#: ../../docs/tutorials/performance/vertex_animation/controlling_thousands_of_fish.rst:98
msgid ""
"Let's transform the fish by setting their ``VELOCITY`` in the ``start()`` "
"function."
msgstr ""

#: ../../docs/tutorials/performance/vertex_animation/controlling_thousands_of_fish.rst:104
msgid ""
"This is the most basic way to set ``VELOCITY`` every particle (or fish) will "
"have the same velocity."
msgstr ""

#: ../../docs/tutorials/performance/vertex_animation/controlling_thousands_of_fish.rst:106
msgid ""
"Just by setting ``VELOCITY`` you can make the fish swim however you want. "
"For example, try the code below."
msgstr ""

#: ../../docs/tutorials/performance/vertex_animation/controlling_thousands_of_fish.rst:113
msgid "This will give each fish a unique speed between ``2`` and ``10``."
msgstr ""

#: ../../docs/tutorials/performance/vertex_animation/controlling_thousands_of_fish.rst:115
msgid ""
"You can also let each fish change its velocity over time if you set the "
"velocity in the ``process()`` function."
msgstr ""

#: ../../docs/tutorials/performance/vertex_animation/controlling_thousands_of_fish.rst:118
msgid ""
"If you used ``CUSTOM.y`` in the last tutorial, you can also set the speed of "
"the swim animation based on the ``VELOCITY``. Just use ``CUSTOM.y``."
msgstr ""

#: ../../docs/tutorials/performance/vertex_animation/controlling_thousands_of_fish.rst:125
msgid "This code gives you the following behavior:"
msgstr ""

#: ../../docs/tutorials/performance/vertex_animation/controlling_thousands_of_fish.rst:129
msgid ""
"Using a ParticleProcessMaterial you can make the fish behavior as simple or "
"complex as you like. In this tutorial we only set Velocity, but in your own "
"Shaders you can also set ``COLOR``, rotation, scale (through ``TRANSFORM``). "
"Please refer to the :ref:`Particles Shader Reference <doc_particle_shader>` "
"for more information on particle shaders."
msgstr ""

#: ../../docs/tutorials/performance/using_multiple_threads.rst:4
msgid "Using multiple threads"
msgstr ""

#: ../../docs/tutorials/performance/using_multiple_threads.rst:9
msgid ""
"Threads allow simultaneous execution of code. It allows off-loading work "
"from the main thread."
msgstr ""

#: ../../docs/tutorials/performance/using_multiple_threads.rst:12
msgid "Godot supports threads and provides many handy functions to use them."
msgstr ""

#: ../../docs/tutorials/performance/using_multiple_threads.rst:14
msgid ""
"If using other languages (C#, C++), it may be easier to use the threading "
"classes they support."
msgstr ""

#: ../../docs/tutorials/performance/using_multiple_threads.rst:19
msgid ""
"Before using a built-in class in a thread, read :ref:`doc_thread_safe_apis` "
"first to check whether it can be safely used in a thread."
msgstr ""

#: ../../docs/tutorials/performance/using_multiple_threads.rst:23
#, fuzzy
msgid "Creating a Thread"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/performance/using_multiple_threads.rst:25
#, fuzzy
msgid "To create a thread, use the following code:"
msgstr "Glavna dokumentacija za sajt je podeljena na sledeća poglavlja:"

#: ../../docs/tutorials/performance/using_multiple_threads.rst:50
msgid ""
"Your function will, then, run in a separate thread until it returns. Even if "
"the function has returned already, the thread must collect it, so call :ref:"
"`Thread.wait_to_finish()<class_Thread_method_wait_to_finish>`, which will "
"wait until the thread is done (if not done yet), then properly dispose of it."
msgstr ""

#: ../../docs/tutorials/performance/using_multiple_threads.rst:57
msgid ""
"Creating threads at run-time is slow on Windows and should be avoided to "
"prevent stuttering. Semaphores, explained later on this page, should be used "
"instead."
msgstr ""

#: ../../docs/tutorials/performance/using_multiple_threads.rst:62
msgid "Mutexes"
msgstr ""

#: ../../docs/tutorials/performance/using_multiple_threads.rst:64
msgid ""
"Accessing objects or data from multiple threads is not always supported (if "
"you do it, it will cause unexpected behaviors or crashes). Read the :ref:"
"`doc_thread_safe_apis` documentation to understand which engine APIs support "
"multiple thread access."
msgstr ""

#: ../../docs/tutorials/performance/using_multiple_threads.rst:69
msgid ""
"When processing your own data or calling your own functions, as a rule, try "
"to avoid accessing the same data directly from different threads. You may "
"run into synchronization problems, as the data is not always updated between "
"CPU cores when modified. Always use a :ref:`Mutex<class_Mutex>` when "
"accessing a piece of data from different threads."
msgstr ""

#: ../../docs/tutorials/performance/using_multiple_threads.rst:75
msgid ""
"When calling :ref:`Mutex.lock()<class_Mutex_method_lock>`, a thread ensures "
"that all other threads will be blocked (put on suspended state) if they try "
"to *lock* the same mutex. When the mutex is unlocked by calling :ref:`Mutex."
"unlock()<class_Mutex_method_unlock>`, the other threads will be allowed to "
"proceed with the lock (but only one at a time)."
msgstr ""

#: ../../docs/tutorials/performance/using_multiple_threads.rst:81
msgid "Here is an example of using a Mutex:"
msgstr ""

#: ../../docs/tutorials/performance/using_multiple_threads.rst:116
msgid "Semaphores"
msgstr ""

#: ../../docs/tutorials/performance/using_multiple_threads.rst:118
msgid ""
"Sometimes you want your thread to work *\"on demand\"*. In other words, tell "
"it when to work and let it suspend when it isn't doing anything. For this, :"
"ref:`Semaphores<class_Semaphore>` are used. The function :ref:`Semaphore."
"wait()<class_Semaphore_method_wait>` is used in the thread to suspend it "
"until some data arrives."
msgstr ""

#: ../../docs/tutorials/performance/using_multiple_threads.rst:124
msgid ""
"The main thread, instead, uses :ref:`Semaphore."
"post()<class_Semaphore_method_post>` to signal that data is ready to be "
"processed:"
msgstr ""

#: ../../docs/tutorials/performance/thread_safe_apis.rst:6
msgid "Thread-safe APIs"
msgstr ""

#: ../../docs/tutorials/performance/thread_safe_apis.rst:11
msgid ""
"Threads are used to balance processing power across CPUs and cores. Godot "
"supports multithreading, but not in the whole engine."
msgstr ""

#: ../../docs/tutorials/performance/thread_safe_apis.rst:14
msgid ""
"Below is a list of ways multithreading can be used in different areas of "
"Godot."
msgstr ""

#: ../../docs/tutorials/performance/thread_safe_apis.rst:17
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:15
msgid "Global scope"
msgstr ""

#: ../../docs/tutorials/performance/thread_safe_apis.rst:19
msgid ""
":ref:`Global Scope<class_@GlobalScope>` singletons are all thread-safe. "
"Accessing servers from threads is supported (for RenderingServer and Physics "
"servers, ensure threaded or thread-safe operation is enabled in the project "
"settings!)."
msgstr ""

#: ../../docs/tutorials/performance/thread_safe_apis.rst:21
msgid ""
"This makes them ideal for code that creates dozens of thousands of instances "
"in servers and controls them from threads. Of course, it requires a bit more "
"code, as this is used directly and not within the scene tree."
msgstr ""

#: ../../docs/tutorials/performance/thread_safe_apis.rst:24
#: ../../docs/tutorials/scripting/scene_tree.rst:90
msgid "Scene tree"
msgstr ""

#: ../../docs/tutorials/performance/thread_safe_apis.rst:26
msgid ""
"Interacting with the active scene tree is **NOT** thread-safe. Make sure to "
"use mutexes when sending data between threads. If you want to call functions "
"from a thread, the *call_deferred* function may be used:"
msgstr ""

#: ../../docs/tutorials/performance/thread_safe_apis.rst:35
msgid ""
"However, creating scene chunks (nodes in tree arrangement) outside the "
"active tree is fine. This way, parts of a scene can be built or instantiated "
"in a thread, then added in the main thread:"
msgstr ""

#: ../../docs/tutorials/performance/thread_safe_apis.rst:44
msgid ""
"Still, this is only really useful if you have **one** thread loading data. "
"Attempting to load or create scene chunks from multiple threads may work, "
"but you risk resources (which are only loaded once in Godot) tweaked by the "
"multiple threads, resulting in unexpected behaviors or crashes."
msgstr ""

#: ../../docs/tutorials/performance/thread_safe_apis.rst:49
msgid ""
"Only use more than one thread to generate scene data if you *really* know "
"what you are doing and you are sure that a single resource is not being used "
"or set in multiple ones. Otherwise, you are safer just using the servers API "
"(which is fully thread-safe) directly and not touching scene or resources."
msgstr ""

#: ../../docs/tutorials/performance/thread_safe_apis.rst:57
msgid ""
"Instancing nodes that render anything in 2D or 3D (such as Sprite) is *not* "
"thread-safe by default. To make rendering thread-safe, set the **Rendering > "
"Driver > Thread Model** project setting to **Multi-Threaded**."
msgstr ""

#: ../../docs/tutorials/performance/thread_safe_apis.rst:60
msgid ""
"Note that the Multi-Threaded thread model has several known bugs, so it may "
"not be usable in all scenarios."
msgstr ""

#: ../../docs/tutorials/performance/thread_safe_apis.rst:63
msgid ""
"You should avoid calling functions involving direct interaction with the GPU "
"on other threads, such as creating new textures or modifying and retrieving "
"image data, these operations can lead to performance stalls because they "
"require synchronization with the :ref:"
"`RenderingServer<class_RenderingServer>`, as data needs to be transmitted to "
"or updated on the GPU."
msgstr ""

#: ../../docs/tutorials/performance/thread_safe_apis.rst:68
msgid "GDScript arrays, dictionaries"
msgstr ""

#: ../../docs/tutorials/performance/thread_safe_apis.rst:70
msgid ""
"In GDScript, reading and writing elements from multiple threads is OK, but "
"anything that changes the container size (resizing, adding or removing "
"elements) requires locking a mutex."
msgstr ""

#: ../../docs/tutorials/performance/thread_safe_apis.rst:73
#: ../../docs/tutorials/scripting/gdscript/gdscript_exports.rst:227
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_exports.rst:269
#: ../../docs/tutorials/scripting/resources.rst:4
#: ../../docs/contributing/development/core_and_modules/object_class.rst:275
#: ../../docs/contributing/development/file_formats/tscn.rst:259
#: ../../docs/community/tutorials.rst:57
msgid "Resources"
msgstr ""

#: ../../docs/tutorials/performance/thread_safe_apis.rst:75
msgid ""
"Modifying a unique resource from multiple threads is not supported. However "
"handling references on multiple threads is supported, hence loading "
"resources on a thread is as well - scenes, textures, meshes, etc - can be "
"loaded and manipulated on a thread and then added to the active scene on the "
"main thread. The limitation here is as described above, one must be careful "
"not to load the same resource from multiple threads at once, therefore it is "
"easiest to use **one** thread for loading and modifying resources, and then "
"the main thread for adding them."
msgstr ""

#: ../../docs/tutorials/physics/physics_introduction.rst:4
msgid "Physics introduction"
msgstr ""

#: ../../docs/tutorials/physics/physics_introduction.rst:6
msgid ""
"In game development, you often need to know when two objects in the game "
"intersect or come into contact. This is known as **collision detection**. "
"When a collision is detected, you typically want something to happen. This "
"is known as **collision response**."
msgstr ""

#: ../../docs/tutorials/physics/physics_introduction.rst:11
msgid ""
"Godot offers a number of collision objects in 2D and 3D to provide both "
"collision detection and response. Trying to decide which one to use for your "
"project can be confusing. You can avoid problems and simplify development if "
"you understand how each works and what their pros and cons are."
msgstr ""

#: ../../docs/tutorials/physics/physics_introduction.rst:18
msgid "Godot's four collision object types"
msgstr ""

#: ../../docs/tutorials/physics/physics_introduction.rst:19
msgid "How each collision object works"
msgstr ""

#: ../../docs/tutorials/physics/physics_introduction.rst:20
msgid "When and why to choose one type over another"
msgstr ""

#: ../../docs/tutorials/physics/physics_introduction.rst:22
msgid ""
"This document's examples will use 2D objects. Every 2D physics object and "
"collision shape has a direct equivalent in 3D and in most cases they work in "
"much the same way."
msgstr ""

#: ../../docs/tutorials/physics/physics_introduction.rst:27
msgid "Collision objects"
msgstr ""

#: ../../docs/tutorials/physics/physics_introduction.rst:29
msgid ""
"Godot offers four kinds of collision objects which all extend :ref:"
"`CollisionObject2D <class_CollisionObject2D>`. The last three listed below "
"are physics bodies and additionally extend :ref:`PhysicsBody2D "
"<class_PhysicsBody2D>`."
msgstr ""

#: ../../docs/tutorials/physics/physics_introduction.rst:36
msgid ":ref:`Area2D <class_Area2D>`"
msgstr ""

#: ../../docs/tutorials/physics/physics_introduction.rst:33
msgid ""
"``Area2D`` nodes provide **detection** and **influence**. They can detect "
"when objects overlap and can emit signals when bodies enter or exit. An "
"``Area2D`` can also be used to override physics properties, such as gravity "
"or damping, in a defined area."
msgstr ""

#: ../../docs/tutorials/physics/physics_introduction.rst:42
msgid ":ref:`StaticBody2D <class_StaticBody2D>`"
msgstr ""

#: ../../docs/tutorials/physics/physics_introduction.rst:39
msgid ""
"A static body is one that is not moved by the physics engine. It "
"participates in collision detection, but does not move in response to the "
"collision. They are most often used for objects that are part of the "
"environment or that do not need to have any dynamic behavior."
msgstr ""

#: ../../docs/tutorials/physics/physics_introduction.rst:48
msgid ":ref:`RigidBody2D <class_RigidBody2D>`"
msgstr ""

#: ../../docs/tutorials/physics/physics_introduction.rst:45
msgid ""
"This is the node that implements simulated 2D physics. You do not control a "
"``RigidBody2D`` directly, but instead you apply forces to it (gravity, "
"impulses, etc.) and the physics engine calculates the resulting movement. :"
"ref:`Read more about using rigid bodies. <doc_rigid_body>`"
msgstr ""

#: ../../docs/tutorials/physics/physics_introduction.rst:52
msgid ":ref:`CharacterBody2D <class_CharacterBody2D>`"
msgstr ""

#: ../../docs/tutorials/physics/physics_introduction.rst:51
msgid ""
"A body that provides collision detection, but no physics. All movement and "
"collision response must be implemented in code."
msgstr ""

#: ../../docs/tutorials/physics/physics_introduction.rst:55
msgid "Physics material"
msgstr ""

#: ../../docs/tutorials/physics/physics_introduction.rst:57
msgid ""
"Static bodies and rigid bodies can be configured to use a :ref:"
"`PhysicsMaterial <class_PhysicsMaterial>`. This allows adjusting the "
"friction and bounce of an object, and set if it's absorbent and/or rough."
msgstr ""

#: ../../docs/tutorials/physics/physics_introduction.rst:64
msgid ""
"A physics body can hold any number of :ref:`Shape2D <class_Shape2D>` objects "
"as children. These shapes are used to define the object's collision bounds "
"and to detect contact with other objects."
msgstr ""

#: ../../docs/tutorials/physics/physics_introduction.rst:68
msgid ""
"In order to detect collisions, at least one ``Shape2D`` must be assigned to "
"the object."
msgstr ""

#: ../../docs/tutorials/physics/physics_introduction.rst:71
msgid ""
"The most common way to assign a shape is by adding a :ref:`CollisionShape2D "
"<class_CollisionShape2D>` or :ref:`CollisionPolygon2D "
"<class_CollisionPolygon2D>` as a child of the object. These nodes allow you "
"to draw the shape directly in the editor workspace."
msgstr ""

#: ../../docs/tutorials/physics/physics_introduction.rst:75
msgid ""
"Be careful to never scale your collision shapes in the editor. The \"Scale\" "
"property in the Inspector should remain ``(1, 1)``. When changing the size "
"of the collision shape, you should always use the size handles, **not** the "
"``Node2D`` scale handles. Scaling a shape can result in unexpected collision "
"behavior."
msgstr ""

#: ../../docs/tutorials/physics/physics_introduction.rst:84
msgid "Physics process callback"
msgstr ""

#: ../../docs/tutorials/physics/physics_introduction.rst:86
msgid ""
"The physics engine runs at a fixed rate (a default of 60 iterations per "
"second). This rate is typically different from the frame rate which "
"fluctuates based on what is rendered and available resources."
msgstr ""

#: ../../docs/tutorials/physics/physics_introduction.rst:90
msgid ""
"It is important that all physics related code runs at this fixed rate. "
"Therefore Godot differentiates :ref:`between physics and idle processing "
"<doc_idle_and_physics_processing>`. Code that runs each frame is called idle "
"processing and code that runs on each physics tick is called physics "
"processing. Godot provides two different callbacks, one for each of those "
"processing rates."
msgstr ""

#: ../../docs/tutorials/physics/physics_introduction.rst:96
msgid ""
"The physics callback, :ref:`Node._physics_process() "
"<class_Node_private_method__physics_process>`, is called before each physics "
"step. Any code that needs to access a body's properties should be run in "
"here. This method will be passed a ``delta`` parameter, which is a floating-"
"point number equal to the time passed in *seconds* since the last step. When "
"using the default 60 Hz physics update rate, it will typically be equal to "
"``0.01666...`` (but not always, see below)."
msgstr ""

#: ../../docs/tutorials/physics/physics_introduction.rst:105
msgid ""
"It's recommended to always use the ``delta`` parameter when relevant in your "
"physics calculations, so that the game behaves correctly if you change the "
"physics update rate or if the player's device can't keep up."
msgstr ""

#: ../../docs/tutorials/physics/physics_introduction.rst:112
msgid "Collision layers and masks"
msgstr ""

#: ../../docs/tutorials/physics/physics_introduction.rst:114
msgid ""
"One of the most powerful, but frequently misunderstood, collision features "
"is the collision layer system. This system allows you to build up complex "
"interactions between a variety of objects. The key concepts are **layers** "
"and **masks**. Each ``CollisionObject2D`` has 32 different physics layers it "
"can interact with."
msgstr ""

#: ../../docs/tutorials/physics/physics_introduction.rst:120
msgid "Let's look at each of the properties in turn:"
msgstr ""

#: ../../docs/tutorials/physics/physics_introduction.rst:124
msgid "collision_layer"
msgstr ""

#: ../../docs/tutorials/physics/physics_introduction.rst:123
msgid ""
"This describes the layers that the object appears **in**. By default, all "
"bodies are on layer ``1``."
msgstr ""

#: ../../docs/tutorials/physics/physics_introduction.rst:129
msgid "collision_mask"
msgstr ""

#: ../../docs/tutorials/physics/physics_introduction.rst:127
msgid ""
"This describes what layers the body will **scan** for collisions. If an "
"object isn't in one of the mask layers, the body will ignore it. By default, "
"all bodies scan layer ``1``."
msgstr ""

#: ../../docs/tutorials/physics/physics_introduction.rst:131
msgid ""
"These properties can be configured via code, or by editing them in the "
"Inspector."
msgstr ""

#: ../../docs/tutorials/physics/physics_introduction.rst:133
msgid ""
"Keeping track of what you're using each layer for can be difficult, so you "
"may find it useful to assign names to the layers you're using. Names can be "
"assigned in Project Settings -> Layer Names."
msgstr ""

#: ../../docs/tutorials/physics/physics_introduction.rst:140
msgid "GUI example"
msgstr ""

#: ../../docs/tutorials/physics/physics_introduction.rst:142
msgid ""
"You have four node types in your game: Walls, Player, Enemy, and Coin. Both "
"Player and Enemy should collide with Walls. The Player node should detect "
"collisions with both Enemy and Coin, but Enemy and Coin should ignore each "
"other."
msgstr ""

#: ../../docs/tutorials/physics/physics_introduction.rst:147
msgid ""
"Start by naming layers 1-4 \"walls\", \"player\", \"enemies\", and \"coins\" "
"and place each node type in its respective layer using the \"Layer\" "
"property. Then set each node's \"Mask\" property by selecting the layers it "
"should interact with. For example, the Player's settings would look like "
"this:"
msgstr ""

#: ../../docs/tutorials/physics/physics_introduction.rst:158
#, fuzzy
msgid "Code example"
msgstr "Windows"

#: ../../docs/tutorials/physics/physics_introduction.rst:160
msgid ""
"In function calls, layers are specified as a bitmask. Where a function "
"enables all layers by default, the layer mask will be given as "
"``0xffffffff``. Your code can use binary, hexadecimal, or decimal notation "
"for layer masks, depending on your preference."
msgstr ""

#: ../../docs/tutorials/physics/physics_introduction.rst:165
msgid ""
"The code equivalent of the above example where layers 1, 3 and 4 were "
"enabled would be as follows::"
msgstr ""

#: ../../docs/tutorials/physics/physics_introduction.rst:185
msgid "Area2D"
msgstr ""

#: ../../docs/tutorials/physics/physics_introduction.rst:187
msgid ""
"Area nodes provide **detection** and **influence**. They can detect when "
"objects overlap and emit signals when bodies enter or exit. Areas can also "
"be used to override physics properties, such as gravity or damping, in a "
"defined area."
msgstr ""

#: ../../docs/tutorials/physics/physics_introduction.rst:192
msgid "There are three main uses for :ref:`Area2D <class_Area2D>`:"
msgstr ""

#: ../../docs/tutorials/physics/physics_introduction.rst:194
msgid "Overriding physics parameters (such as gravity) in a given region."
msgstr ""

#: ../../docs/tutorials/physics/physics_introduction.rst:196
msgid ""
"Detecting when other bodies enter or exit a region or what bodies are "
"currently in a region."
msgstr ""

#: ../../docs/tutorials/physics/physics_introduction.rst:198
msgid "Checking other areas for overlap."
msgstr ""

#: ../../docs/tutorials/physics/physics_introduction.rst:200
msgid "By default, areas also receive mouse and touchscreen input."
msgstr ""

#: ../../docs/tutorials/physics/physics_introduction.rst:203
msgid "StaticBody2D"
msgstr ""

#: ../../docs/tutorials/physics/physics_introduction.rst:205
msgid ""
"A static body is one that is not moved by the physics engine. It "
"participates in collision detection, but does not move in response to the "
"collision. However, it can impart motion or rotation to a colliding body "
"**as if** it were moving, using its ``constant_linear_velocity`` and "
"``constant_angular_velocity`` properties."
msgstr ""

#: ../../docs/tutorials/physics/physics_introduction.rst:210
msgid ""
"``StaticBody2D`` nodes are most often used for objects that are part of the "
"environment or that do not need to have any dynamic behavior."
msgstr ""

#: ../../docs/tutorials/physics/physics_introduction.rst:213
msgid "Example uses for ``StaticBody2D``:"
msgstr ""

#: ../../docs/tutorials/physics/physics_introduction.rst:215
msgid "Platforms (including moving platforms)"
msgstr ""

#: ../../docs/tutorials/physics/physics_introduction.rst:216
msgid "Conveyor belts"
msgstr ""

#: ../../docs/tutorials/physics/physics_introduction.rst:217
msgid "Walls and other obstacles"
msgstr ""

#: ../../docs/tutorials/physics/physics_introduction.rst:220
msgid "RigidBody2D"
msgstr ""

#: ../../docs/tutorials/physics/physics_introduction.rst:222
msgid ""
"This is the node that implements simulated 2D physics. You do not control a :"
"ref:`RigidBody2D <class_RigidBody2D>` directly. Instead, you apply forces to "
"it and the physics engine calculates the resulting movement, including "
"collisions with other bodies, and collision responses, such as bouncing, "
"rotating, etc."
msgstr ""

#: ../../docs/tutorials/physics/physics_introduction.rst:228
msgid ""
"You can modify a rigid body's behavior via properties such as \"Mass\", "
"\"Friction\", or \"Bounce\", which can be set in the Inspector."
msgstr ""

#: ../../docs/tutorials/physics/physics_introduction.rst:231
msgid ""
"The body's behavior is also affected by the world's properties, as set in "
"`Project Settings -> Physics`, or by entering an :ref:`Area2D "
"<class_Area2D>` that is overriding the global physics properties."
msgstr ""

#: ../../docs/tutorials/physics/physics_introduction.rst:235
msgid ""
"When a rigid body is at rest and hasn't moved for a while, it goes to sleep. "
"A sleeping body acts like a static body, and its forces are not calculated "
"by the physics engine. The body will wake up when forces are applied, either "
"by a collision or via code."
msgstr ""

#: ../../docs/tutorials/physics/physics_introduction.rst:241
msgid "Using RigidBody2D"
msgstr ""

#: ../../docs/tutorials/physics/physics_introduction.rst:243
msgid ""
"One of the benefits of using a rigid body is that a lot of behavior can be "
"had \"for free\" without writing any code. For example, if you were making "
"an \"Angry Birds\"-style game with falling blocks, you would only need to "
"create RigidBody2Ds and adjust their properties. Stacking, falling, and "
"bouncing would automatically be calculated by the physics engine."
msgstr ""

#: ../../docs/tutorials/physics/physics_introduction.rst:249
msgid ""
"However, if you do wish to have some control over the body, you should take "
"care - altering the ``position``, ``linear_velocity``, or other physics "
"properties of a rigid body can result in unexpected behavior. If you need to "
"alter any of the physics-related properties, you should use the :ref:"
"`_integrate_forces() <class_RigidBody2D_private_method__integrate_forces>` "
"callback instead of ``_physics_process()``. In this callback, you have "
"access to the body's :ref:`PhysicsDirectBodyState2D "
"<class_PhysicsDirectBodyState2D>`, which allows for safely changing "
"properties and synchronizing them with the physics engine."
msgstr ""

#: ../../docs/tutorials/physics/physics_introduction.rst:258
msgid "For example, here is the code for an \"Asteroids\" style spaceship:"
msgstr ""

#: ../../docs/tutorials/physics/physics_introduction.rst:305
msgid ""
"Note that we are not setting the ``linear_velocity`` or ``angular_velocity`` "
"properties directly, but rather applying forces (``thrust`` and ``torque``) "
"to the body and letting the physics engine calculate the resulting movement."
msgstr ""

#: ../../docs/tutorials/physics/physics_introduction.rst:309
msgid ""
"When a rigid body goes to sleep, the ``_integrate_forces()`` function will "
"not be called. To override this behavior, you will need to keep the body "
"awake by creating a collision, applying a force to it, or by disabling the :"
"ref:`can_sleep <class_RigidBody2D_property_can_sleep>` property. Be aware "
"that this can have a negative effect on performance."
msgstr ""

#: ../../docs/tutorials/physics/physics_introduction.rst:316
msgid "Contact reporting"
msgstr ""

#: ../../docs/tutorials/physics/physics_introduction.rst:318
msgid ""
"By default, rigid bodies do not keep track of contacts, because this can "
"require a huge amount of memory if many bodies are in the scene. To enable "
"contact reporting, set the :ref:`max_contacts_reported "
"<class_RigidBody2D_property_max_contacts_reported>` property to a non-zero "
"value. The contacts can then be obtained via :ref:`PhysicsDirectBodyState2D."
"get_contact_count() "
"<class_PhysicsDirectBodyState2D_method_get_contact_count>` and related "
"functions."
msgstr ""

#: ../../docs/tutorials/physics/physics_introduction.rst:325
msgid ""
"Contact monitoring via signals can be enabled via the :ref:`contact_monitor "
"<class_RigidBody2D_property_contact_monitor>` property. See :ref:"
"`RigidBody2D <class_RigidBody2D>` for the list of available signals."
msgstr ""

#: ../../docs/tutorials/physics/physics_introduction.rst:332
msgid ""
":ref:`CharacterBody2D <class_CharacterBody2D>` bodies detect collisions with "
"other bodies, but are not affected by physics properties like gravity or "
"friction. Instead, they must be controlled by the user via code. The physics "
"engine will not move a character body."
msgstr ""

#: ../../docs/tutorials/physics/physics_introduction.rst:337
msgid ""
"When moving a character body, you should not set its ``position`` directly. "
"Instead, you use the ``move_and_collide()`` or ``move_and_slide()`` methods. "
"These methods move the body along a given vector, and it will instantly stop "
"if a collision is detected with another body. After the body has collided, "
"any collision response must be coded manually."
msgstr ""

#: ../../docs/tutorials/physics/physics_introduction.rst:344
msgid "Character collision response"
msgstr ""

#: ../../docs/tutorials/physics/physics_introduction.rst:346
msgid ""
"After a collision, you may want the body to bounce, to slide along a wall, "
"or to alter the properties of the object it hit. The way you handle "
"collision response depends on which method you used to move the "
"CharacterBody2D."
msgstr ""

#: ../../docs/tutorials/physics/physics_introduction.rst:351
msgid ":ref:`move_and_collide <class_PhysicsBody2D_method_move_and_collide>`"
msgstr ""

#: ../../docs/tutorials/physics/physics_introduction.rst:353
msgid ""
"When using ``move_and_collide()``, the function returns a :ref:"
"`KinematicCollision2D <class_KinematicCollision2D>` object, which contains "
"information about the collision and the colliding body. You can use this "
"information to determine the response."
msgstr ""

#: ../../docs/tutorials/physics/physics_introduction.rst:358
msgid ""
"For example, if you want to find the point in space where the collision "
"occurred:"
msgstr ""

#: ../../docs/tutorials/physics/physics_introduction.rst:391
msgid "Or to bounce off of the colliding object:"
msgstr ""

#: ../../docs/tutorials/physics/physics_introduction.rst:422
msgid ":ref:`move_and_slide <class_CharacterBody2D_method_move_and_slide>`"
msgstr ""

#: ../../docs/tutorials/physics/physics_introduction.rst:424
msgid ""
"Sliding is a common collision response; imagine a player moving along walls "
"in a top-down game or running up and down slopes in a platformer. While it's "
"possible to code this response yourself after using ``move_and_collide()``, "
"``move_and_slide()`` provides a convenient way to implement sliding movement "
"without writing much code."
msgstr ""

#: ../../docs/tutorials/physics/physics_introduction.rst:430
msgid ""
"``move_and_slide()`` automatically includes the timestep in its calculation, "
"so you should **not** multiply the velocity vector by ``delta``."
msgstr ""

#: ../../docs/tutorials/physics/physics_introduction.rst:434
msgid ""
"For example, use the following code to make a character that can walk along "
"the ground (including slopes) and jump when standing on the ground:"
msgstr ""

#: ../../docs/tutorials/physics/physics_introduction.rst:504
msgid ""
"See :ref:`doc_kinematic_character_2d` for more details on using "
"``move_and_slide()``, including a demo project with detailed code."
msgstr ""

#: ../../docs/tutorials/physics/rigid_body.rst:4
msgid "Using RigidBody"
msgstr ""

#: ../../docs/tutorials/physics/rigid_body.rst:7
msgid "What is a rigid body?"
msgstr ""

#: ../../docs/tutorials/physics/rigid_body.rst:9
msgid ""
"A rigid body is one that is directly controlled by the physics engine in "
"order to simulate the behavior of physical objects. In order to define the "
"shape of the body, it must have one or more :ref:`Shape3D <class_Shape3D>` "
"objects assigned. Note that setting the position of these shapes will affect "
"the body's center of mass."
msgstr ""

#: ../../docs/tutorials/physics/rigid_body.rst:13
msgid "How to control a rigid body"
msgstr ""

#: ../../docs/tutorials/physics/rigid_body.rst:15
msgid ""
"A rigid body's behavior can be altered by setting its properties, such as "
"mass and weight. A physics material needs to be added to the rigid body to "
"adjust its friction and bounce, and set if it's absorbent and/or rough. "
"These properties can be set in the Inspector or via code. See :ref:"
"`RigidBody3D <class_RigidBody3D>` and :ref:`PhysicsMaterial "
"<class_PhysicsMaterial>` for the full list of properties and their effects."
msgstr ""

#: ../../docs/tutorials/physics/rigid_body.rst:21
msgid ""
"There are several ways to control a rigid body's movement, depending on your "
"desired application."
msgstr ""

#: ../../docs/tutorials/physics/rigid_body.rst:23
msgid ""
"If you only need to place a rigid body once, for example to set its initial "
"location, you can use the methods provided by the :ref:`Node3D "
"<class_Node3D>` node, such as ``set_global_transform()`` or ``look_at()``. "
"However, these methods cannot be called every frame or the physics engine "
"will not be able to correctly simulate the body's state. As an example, "
"consider a rigid body that you want to rotate so that it points towards "
"another object. A common mistake when implementing this kind of behavior is "
"to use ``look_at()`` every frame, which breaks the physics simulation. "
"Below, we'll demonstrate how to implement this correctly."
msgstr ""

#: ../../docs/tutorials/physics/rigid_body.rst:26
msgid ""
"The fact that you can't use ``set_global_transform()`` or ``look_at()`` "
"methods doesn't mean that you can't have full control of a rigid body. "
"Instead, you can control it by using the ``_integrate_forces()`` callback. "
"In this method, you can add *forces*, apply *impulses*, or set the "
"*velocity* in order to achieve any movement you desire."
msgstr ""

#: ../../docs/tutorials/physics/rigid_body.rst:29
msgid "The \"look at\" method"
msgstr ""

#: ../../docs/tutorials/physics/rigid_body.rst:31
msgid ""
"As described above, using the Node3D's ``look_at()`` method can't be used "
"each frame to follow a target. Here is a custom ``look_at()`` method called "
"``look_follow()`` that will work with rigid bodies:"
msgstr ""

#: ../../docs/tutorials/physics/rigid_body.rst:80
msgid ""
"This method uses the rigid body's ``angular_velocity`` property to rotate "
"the body. The axis to rotate around is given by the cross product between "
"the current forward direction and the direction one wants to look in. The "
"``clamp`` is a simple method used to prevent the amount of rotation from "
"going past the direction which is wanted to be looked in, as the total "
"amount of rotation needed is given by the arccosine of the dot product. This "
"method can be used with ``axis_lock_angular_*`` as well. If more precise "
"control is needed, solutions such as ones relying on :ref:`class_Quaternion` "
"may be required, as discussed in :ref:`doc_using_transforms`."
msgstr ""

#: ../../docs/tutorials/physics/using_area_2d.rst:4
msgid "Using Area2D"
msgstr ""

#: ../../docs/tutorials/physics/using_area_2d.rst:9
msgid ""
"Godot offers a number of collision objects to provide both collision "
"detection and response. Trying to decide which one to use for your project "
"can be confusing. You can avoid problems and simplify development if you "
"understand how each of them works and what their pros and cons are. In this "
"tutorial, we'll look at the :ref:`Area2D <class_Area2D>` node and show some "
"examples of how it can be used."
msgstr ""

#: ../../docs/tutorials/physics/using_area_2d.rst:15
msgid ""
"This document assumes you're familiar with Godot's various physics bodies. "
"Please read :ref:`doc_physics_introduction` first."
msgstr ""

#: ../../docs/tutorials/physics/using_area_2d.rst:19
msgid "What is an area?"
msgstr ""

#: ../../docs/tutorials/physics/using_area_2d.rst:21
msgid ""
"An Area2D defines a region of 2D space. In this space you can detect other :"
"ref:`CollisionObject2D <class_CollisionObject2D>` nodes overlapping, "
"entering, and exiting. Areas also allow for overriding local physics "
"properties. We'll explore each of these functions below."
msgstr ""

#: ../../docs/tutorials/physics/using_area_2d.rst:27
msgid "Area properties"
msgstr ""

#: ../../docs/tutorials/physics/using_area_2d.rst:29
msgid "Areas have many properties you can use to customize their behavior."
msgstr ""

#: ../../docs/tutorials/physics/using_area_2d.rst:33
msgid ""
"The ``Gravity``, ``Linear Damp``, and ``Angular Damp`` sections are used to "
"configure the area's physics override behavior. We'll look at how to use "
"those in the *Area influence* section below."
msgstr ""

#: ../../docs/tutorials/physics/using_area_2d.rst:37
msgid ""
"``Monitoring`` and ``Monitorable`` are used to enable and disable the area."
msgstr ""

#: ../../docs/tutorials/physics/using_area_2d.rst:39
msgid ""
"The ``Audio Bus`` section allows you to override audio in the area, for "
"example to apply an audio effect when the player moves through."
msgstr ""

#: ../../docs/tutorials/physics/using_area_2d.rst:42
msgid ""
"Note that Area2D extends :ref:`CollisionObject2D <class_CollisionObject2D>`, "
"so it also provides properties inherited from that class. The ``Collision`` "
"section of ``CollisionObject2D`` is where you configure the area's collision "
"layer(s) and mask(s)."
msgstr ""

#: ../../docs/tutorials/physics/using_area_2d.rst:48
msgid "Overlap detection"
msgstr ""

#: ../../docs/tutorials/physics/using_area_2d.rst:50
msgid ""
"Perhaps the most common use of Area2D nodes is for contact and overlap "
"detection. When you need to know that two objects have touched, but don't "
"need physical collision, you can use an area to notify you of the contact."
msgstr ""

#: ../../docs/tutorials/physics/using_area_2d.rst:54
msgid ""
"For example, let's say we're making a coin for the player to pick up. The "
"coin is not a solid object - the player can't stand on it or push it - we "
"just want it to disappear when the player touches it."
msgstr ""

#: ../../docs/tutorials/physics/using_area_2d.rst:58
msgid "Here's the node setup for the coin:"
msgstr ""

#: ../../docs/tutorials/physics/using_area_2d.rst:62
msgid ""
"To detect the overlap, we'll connect the appropriate signal on the Area2D. "
"Which signal to use depends on the player's node type. If the player is "
"another area, use ``area_entered``. However, let's assume our player is a "
"``CharacterBody2D`` (and therefore a ``CollisionObject2D`` type), so we'll "
"connect the ``body_entered`` signal."
msgstr ""

#: ../../docs/tutorials/physics/using_area_2d.rst:68
msgid ""
"If you're not familiar with using signals, see :ref:`doc_signals` for an "
"introduction."
msgstr ""

#: ../../docs/tutorials/physics/using_area_2d.rst:91
msgid "Now our player can collect the coins!"
msgstr ""

#: ../../docs/tutorials/physics/using_area_2d.rst:93
msgid "Some other usage examples:"
msgstr ""

#: ../../docs/tutorials/physics/using_area_2d.rst:95
msgid ""
"Areas are great for bullets and other projectiles that hit and deal damage, "
"but don't need any other physics such as bouncing."
msgstr ""

#: ../../docs/tutorials/physics/using_area_2d.rst:96
msgid ""
"Use a large circular area around an enemy to define its \"detect\" radius. "
"When the player is outside the area, the enemy can't \"see\" it."
msgstr ""

#: ../../docs/tutorials/physics/using_area_2d.rst:97
msgid ""
"\"Security cameras\" - In a large level with multiple cameras, attach areas "
"to each camera and activate them when the player enters."
msgstr ""

#: ../../docs/tutorials/physics/using_area_2d.rst:99
msgid ""
"See the :ref:`doc_your_first_2d_game` for an example of using Area2D in a "
"game."
msgstr ""

#: ../../docs/tutorials/physics/using_area_2d.rst:102
msgid "Area influence"
msgstr ""

#: ../../docs/tutorials/physics/using_area_2d.rst:104
msgid ""
"The second major use for area nodes is to alter physics. By default, the "
"area won't do this, but you can enable this with the ``Space Override`` "
"property. When areas overlap, they are processed in ``Priority`` order "
"(higher priority areas are processed first). There are four options for "
"override:"
msgstr ""

#: ../../docs/tutorials/physics/using_area_2d.rst:109
msgid ""
"*Combine* - The area adds its values to what has been calculated so far."
msgstr ""

#: ../../docs/tutorials/physics/using_area_2d.rst:110
msgid ""
"*Replace* - The area replaces physics properties, and lower priority areas "
"are ignored."
msgstr ""

#: ../../docs/tutorials/physics/using_area_2d.rst:111
msgid ""
"*Combine-Replace* - The area adds its gravity/damping values to whatever has "
"been calculated so far (in priority order), ignoring any lower priority "
"areas."
msgstr ""

#: ../../docs/tutorials/physics/using_area_2d.rst:112
msgid ""
"*Replace-Combine* - The area replaces any gravity/damping calculated so far, "
"but keeps calculating the rest of the areas."
msgstr ""

#: ../../docs/tutorials/physics/using_area_2d.rst:114
msgid ""
"Using these properties, you can create very complex behavior with multiple "
"overlapping areas."
msgstr ""

#: ../../docs/tutorials/physics/using_area_2d.rst:117
msgid "The physics properties that can be overridden are:"
msgstr ""

#: ../../docs/tutorials/physics/using_area_2d.rst:119
msgid "*Gravity* - Gravity's strength inside the area."
msgstr ""

#: ../../docs/tutorials/physics/using_area_2d.rst:120
msgid "*Gravity Direction* - This vector does not need to be normalized."
msgstr ""

#: ../../docs/tutorials/physics/using_area_2d.rst:121
msgid ""
"*Linear Damp* - How quickly objects stop moving - linear velocity lost per "
"second."
msgstr ""

#: ../../docs/tutorials/physics/using_area_2d.rst:122
msgid ""
"*Angular Damp* - How quickly objects stop spinning - angular velocity lost "
"per second."
msgstr ""

#: ../../docs/tutorials/physics/using_area_2d.rst:125
msgid "Point gravity"
msgstr ""

#: ../../docs/tutorials/physics/using_area_2d.rst:127
msgid ""
"The ``Gravity Point`` property allows you to create an \"attractor\". "
"Gravity in the area will be calculated towards a point, given by the ``Point "
"Center`` property. Values are relative to the Area2D, so for example using "
"``(0, 0)`` will attract objects to the center of the area."
msgstr ""

#: ../../docs/tutorials/physics/using_area_2d.rst:133
#: ../../docs/tutorials/physics/using_character_body_2d.rst:215
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_features.rst:110
#: ../../docs/contributing/development/compiling/compiling_with_dotnet.rst:144
msgid "Examples"
msgstr ""

#: ../../docs/tutorials/physics/using_area_2d.rst:135
msgid ""
"The example project attached below has three areas demonstrating physics "
"override."
msgstr ""

#: ../../docs/tutorials/physics/using_area_2d.rst:140
msgid ""
"You can download this project here: `area_2d_starter.zip <https://github.com/"
"godotengine/godot-docs-project-starters/releases/download/latest-4.x/"
"area_2d_starter.zip>`_"
msgstr ""

#: ../../docs/tutorials/physics/using_character_body_2d.rst:4
msgid "Using CharacterBody2D/3D"
msgstr ""

#: ../../docs/tutorials/physics/using_character_body_2d.rst:9
msgid ""
"Godot offers several collision objects to provide both collision detection "
"and response. Trying to decide which one to use for your project can be "
"confusing. You can avoid problems and simplify development if you understand "
"how each of them works and what their pros and cons are. In this tutorial, "
"we'll look at the :ref:`CharacterBody2D <class_CharacterBody2D>` node and "
"show some examples of how to use it."
msgstr ""

#: ../../docs/tutorials/physics/using_character_body_2d.rst:16
msgid ""
"While this document uses ``CharacterBody2D`` in its examples, the same "
"concepts apply in 3D as well."
msgstr ""

#: ../../docs/tutorials/physics/using_character_body_2d.rst:20
msgid "What is a character body?"
msgstr ""

#: ../../docs/tutorials/physics/using_character_body_2d.rst:22
msgid ""
"``CharacterBody2D`` is for implementing bodies that are controlled via code. "
"Character bodies detect collisions with other bodies when moving, but are "
"not affected by engine physics properties, like gravity or friction. While "
"this means that you have to write some code to create their behavior, it "
"also means you have more precise control over how they move and react."
msgstr ""

#: ../../docs/tutorials/physics/using_character_body_2d.rst:28
msgid ""
"This document assumes you're familiar with Godot's various physics bodies. "
"Please read :ref:`doc_physics_introduction` first, for an overview of the "
"physics options."
msgstr ""

#: ../../docs/tutorials/physics/using_character_body_2d.rst:32
msgid ""
"A `CharacterBody2D` can be affected by gravity and other forces, but you "
"must calculate the movement in code. The physics engine will not move a "
"`CharacterBody2D`."
msgstr ""

#: ../../docs/tutorials/physics/using_character_body_2d.rst:37
msgid "Movement and collision"
msgstr ""

#: ../../docs/tutorials/physics/using_character_body_2d.rst:39
msgid ""
"When moving a ``CharacterBody2D``, you should not set its ``position`` "
"property directly. Instead, you use the ``move_and_collide()`` or "
"``move_and_slide()`` methods. These methods move the body along a given "
"vector and detect collisions."
msgstr ""

#: ../../docs/tutorials/physics/using_character_body_2d.rst:43
msgid ""
"You should handle physics body movement in the ``_physics_process()`` "
"callback."
msgstr ""

#: ../../docs/tutorials/physics/using_character_body_2d.rst:45
msgid ""
"The two movement methods serve different purposes, and later in this "
"tutorial, you'll see examples of how they work."
msgstr ""

#: ../../docs/tutorials/physics/using_character_body_2d.rst:49
msgid "move_and_collide"
msgstr ""

#: ../../docs/tutorials/physics/using_character_body_2d.rst:51
msgid ""
"This method takes one required parameter: a :ref:`Vector2 <class_Vector2>` "
"indicating the body's relative movement. Typically, this is your velocity "
"vector multiplied by the frame timestep (``delta``). If the engine detects a "
"collision anywhere along this vector, the body will immediately stop moving. "
"If this happens, the method will return a :ref:`KinematicCollision2D "
"<class_KinematicCollision2D>` object."
msgstr ""

#: ../../docs/tutorials/physics/using_character_body_2d.rst:57
msgid ""
"``KinematicCollision2D`` is an object containing data about the collision "
"and the colliding object. Using this data, you can calculate your collision "
"response."
msgstr ""

#: ../../docs/tutorials/physics/using_character_body_2d.rst:61
msgid ""
"``move_and_collide`` is most useful when you just want to move the body and "
"detect collision, but don't need any automatic collision response. For "
"example, if you need a bullet that ricochets off a wall, you can directly "
"change the angle of the velocity when you detect a collision. See below for "
"an example."
msgstr ""

#: ../../docs/tutorials/physics/using_character_body_2d.rst:67
msgid "move_and_slide"
msgstr ""

#: ../../docs/tutorials/physics/using_character_body_2d.rst:69
msgid ""
"The ``move_and_slide()`` method is intended to simplify the collision "
"response in the common case where you want one body to slide along the "
"other. It is especially useful in platformers or top-down games, for example."
msgstr ""

#: ../../docs/tutorials/physics/using_character_body_2d.rst:73
msgid ""
"When calling ``move_and_slide()``, the function uses a number of node "
"properties to calculate its slide behavior. These properties can be found in "
"the Inspector, or set in code."
msgstr ""

#: ../../docs/tutorials/physics/using_character_body_2d.rst:77
msgid "``velocity`` - *default value:* ``Vector2( 0, 0 )``"
msgstr ""

#: ../../docs/tutorials/physics/using_character_body_2d.rst:79
msgid ""
"This property represents the body's velocity vector in pixels per second. "
"``move_and_slide()`` will modify this value automatically when colliding."
msgstr ""

#: ../../docs/tutorials/physics/using_character_body_2d.rst:82
msgid "``motion_mode`` - *default value:* ``MOTION_MODE_GROUNDED``"
msgstr ""

#: ../../docs/tutorials/physics/using_character_body_2d.rst:84
msgid ""
"This property is typically used to distinguish between side-scrolling and "
"top-down movement. When using the default value, you can use the "
"``is_on_floor()``, ``is_on_wall()``, and ``is_on_ceiling()`` methods to "
"detect what type of surface the body is in contact with, and the body will "
"interact with slopes. When using ``MOTION_MODE_FLOATING``, all collisions "
"will be considered \"walls\"."
msgstr ""

#: ../../docs/tutorials/physics/using_character_body_2d.rst:90
msgid "``up_direction`` - *default value:* ``Vector2( 0, -1 )``"
msgstr ""

#: ../../docs/tutorials/physics/using_character_body_2d.rst:92
msgid ""
"This property allows you to define what surfaces the engine should consider "
"being the floor. Its value lets you use the ``is_on_floor()``, "
"``is_on_wall()``, and ``is_on_ceiling()`` methods to detect what type of "
"surface the body is in contact with. The default value means that the top "
"side of horizontal surfaces will be considered \"ground\"."
msgstr ""

#: ../../docs/tutorials/physics/using_character_body_2d.rst:98
msgid "``floor_stop_on_slope`` - *default value:* ``true``"
msgstr ""

#: ../../docs/tutorials/physics/using_character_body_2d.rst:100
msgid ""
"This parameter prevents a body from sliding down slopes when standing still."
msgstr ""

#: ../../docs/tutorials/physics/using_character_body_2d.rst:102
msgid ""
"``wall_min_slide_angle`` - *default value:* ``0.261799`` (in radians, "
"equivalent to ``15`` degrees)"
msgstr ""

#: ../../docs/tutorials/physics/using_character_body_2d.rst:104
msgid ""
"This is the minimum angle where the body is allowed to slide when it hits a "
"slope."
msgstr ""

#: ../../docs/tutorials/physics/using_character_body_2d.rst:107
msgid ""
"``floor_max_angle`` - *default value:* ``0.785398`` (in radians, equivalent "
"to ``45`` degrees)"
msgstr ""

#: ../../docs/tutorials/physics/using_character_body_2d.rst:109
msgid ""
"This parameter is the maximum angle before a surface is no longer considered "
"a \"floor.\""
msgstr ""

#: ../../docs/tutorials/physics/using_character_body_2d.rst:111
msgid ""
"There are many other properties that can be used to modify the body's "
"behavior under specific circumstances. See the :ref:`CharacterBody2D "
"<class_CharacterBody2D>` docs for full details."
msgstr ""

#: ../../docs/tutorials/physics/using_character_body_2d.rst:116
msgid "Detecting collisions"
msgstr ""

#: ../../docs/tutorials/physics/using_character_body_2d.rst:118
msgid ""
"When using ``move_and_collide()`` the function returns a "
"``KinematicCollision2D`` directly, and you can use this in your code."
msgstr ""

#: ../../docs/tutorials/physics/using_character_body_2d.rst:121
msgid ""
"When using ``move_and_slide()`` it's possible to have multiple collisions "
"occur, as the slide response is calculated. To process these collisions, use "
"``get_slide_collision_count()`` and ``get_slide_collision()``:"
msgstr ""

#: ../../docs/tutorials/physics/using_character_body_2d.rst:156
msgid ""
"`get_slide_collision_count()` only counts times the body has collided and "
"changed direction."
msgstr ""

#: ../../docs/tutorials/physics/using_character_body_2d.rst:158
msgid ""
"See :ref:`KinematicCollision2D <class_KinematicCollision2D>` for details on "
"what collision data is returned."
msgstr ""

#: ../../docs/tutorials/physics/using_character_body_2d.rst:162
msgid "Which movement method to use?"
msgstr ""

#: ../../docs/tutorials/physics/using_character_body_2d.rst:164
msgid ""
"A common question from new Godot users is: \"How do you decide which "
"movement function to use?\" Often, the response is to use "
"``move_and_slide()`` because it seems simpler, but this is not necessarily "
"the case. One way to think of it is that ``move_and_slide()`` is a special "
"case, and ``move_and_collide()`` is more general. For example, the following "
"two code snippets result in the same collision response:"
msgstr ""

#: ../../docs/tutorials/physics/using_character_body_2d.rst:196
msgid ""
"Anything you do with ``move_and_slide()`` can also be done with "
"``move_and_collide()``, but it might take a little more code. However, as "
"we'll see in the examples below, there are cases where ``move_and_slide()`` "
"doesn't provide the response you want."
msgstr ""

#: ../../docs/tutorials/physics/using_character_body_2d.rst:200
msgid ""
"In the example above, ``move_and_slide()`` automatically alters the "
"``velocity`` variable. This is because when the character collides with the "
"environment, the function recalculates the speed internally to reflect the "
"slowdown."
msgstr ""

#: ../../docs/tutorials/physics/using_character_body_2d.rst:205
msgid ""
"For example, if your character fell on the floor, you don't want it to "
"accumulate vertical speed due to the effect of gravity. Instead, you want "
"its vertical speed to reset to zero."
msgstr ""

#: ../../docs/tutorials/physics/using_character_body_2d.rst:209
msgid ""
"``move_and_slide()`` may also recalculate the kinematic body's velocity "
"several times in a loop as, to produce a smooth motion, it moves the "
"character and collides up to five times by default. At the end of the "
"process, the character's new velocity is available for use on the next frame."
msgstr ""

#: ../../docs/tutorials/physics/using_character_body_2d.rst:217
msgid ""
"To see these examples in action, download the sample project: "
"`character_body_2d_starter.zip <https://github.com/godotengine/godot-docs-"
"project-starters/releases/download/latest-4.x/character_body_2d_starter."
"zip>`_"
msgstr ""

#: ../../docs/tutorials/physics/using_character_body_2d.rst:221
msgid "Movement and walls"
msgstr ""

#: ../../docs/tutorials/physics/using_character_body_2d.rst:223
msgid ""
"If you've downloaded the sample project, this example is in \"basic_movement."
"tscn\"."
msgstr ""

#: ../../docs/tutorials/physics/using_character_body_2d.rst:225
msgid ""
"For this example, add a ``CharacterBody2D`` with two children: a "
"``Sprite2D`` and a ``CollisionShape2D``. Use the Godot \"icon.svg\" as the "
"Sprite2D's texture (drag it from the Filesystem dock to the *Texture* "
"property of the ``Sprite2D``). In the ``CollisionShape2D``'s *Shape* "
"property, select \"New RectangleShape2D\" and size the rectangle to fit over "
"the sprite image."
msgstr ""

#: ../../docs/tutorials/physics/using_character_body_2d.rst:231
msgid ""
"See :ref:`doc_2d_movement` for examples of implementing 2D movement schemes."
msgstr ""

#: ../../docs/tutorials/physics/using_character_body_2d.rst:233
msgid "Attach a script to the CharacterBody2D and add the following code:"
msgstr ""

#: ../../docs/tutorials/physics/using_character_body_2d.rst:272
msgid ""
"Run this scene and you'll see that ``move_and_collide()`` works as expected, "
"moving the body along the velocity vector. Now let's see what happens when "
"you add some obstacles. Add a :ref:`StaticBody2D <class_StaticBody2D>` with "
"a rectangular collision shape. For visibility, you can use a Sprite2D, a "
"Polygon2D, or turn on \"Visible Collision Shapes\" from the \"Debug\" menu."
msgstr ""

#: ../../docs/tutorials/physics/using_character_body_2d.rst:278
msgid ""
"Run the scene again and try moving into the obstacle. You'll see that the "
"``CharacterBody2D`` can't penetrate the obstacle. However, try moving into "
"the obstacle at an angle and you'll find that the obstacle acts like glue - "
"it feels like the body gets stuck."
msgstr ""

#: ../../docs/tutorials/physics/using_character_body_2d.rst:282
msgid ""
"This happens because there is no *collision response*. "
"``move_and_collide()`` stops the body's movement when a collision occurs. We "
"need to code whatever response we want from the collision."
msgstr ""

#: ../../docs/tutorials/physics/using_character_body_2d.rst:286
msgid "Try changing the function to ``move_and_slide()`` and running again."
msgstr ""

#: ../../docs/tutorials/physics/using_character_body_2d.rst:288
msgid ""
"``move_and_slide()`` provides a default collision response of sliding the "
"body along the collision object. This is useful for a great many game types, "
"and may be all you need to get the behavior you want."
msgstr ""

#: ../../docs/tutorials/physics/using_character_body_2d.rst:293
msgid "Bouncing/reflecting"
msgstr ""

#: ../../docs/tutorials/physics/using_character_body_2d.rst:295
msgid ""
"What if you don't want a sliding collision response? For this example "
"(\"bounce_and_collide.tscn\" in the sample project), we have a character "
"shooting bullets and we want the bullets to bounce off the walls."
msgstr ""

#: ../../docs/tutorials/physics/using_character_body_2d.rst:299
msgid ""
"This example uses three scenes. The main scene contains the Player and "
"Walls. The Bullet and Wall are separate scenes so that they can be instanced."
msgstr ""

#: ../../docs/tutorials/physics/using_character_body_2d.rst:302
msgid ""
"The Player is controlled by the ``w`` and ``s`` keys for forward and back. "
"Aiming uses the mouse pointer. Here is the code for the Player, using "
"``move_and_slide()``:"
msgstr ""

#: ../../docs/tutorials/physics/using_character_body_2d.rst:376
msgid "And the code for the Bullet:"
msgstr ""

#: ../../docs/tutorials/physics/using_character_body_2d.rst:437
msgid ""
"The action happens in ``_physics_process()``. After using "
"``move_and_collide()``, if a collision occurs, a ``KinematicCollision2D`` "
"object is returned (otherwise, the return is ``null``)."
msgstr ""

#: ../../docs/tutorials/physics/using_character_body_2d.rst:441
msgid ""
"If there is a returned collision, we use the ``normal`` of the collision to "
"reflect the bullet's ``velocity`` with the ``Vector2.bounce()`` method."
msgstr ""

#: ../../docs/tutorials/physics/using_character_body_2d.rst:444
msgid ""
"If the colliding object (``collider``) has a ``hit`` method, we also call "
"it. In the example project, we've added a flashing color effect to the Wall "
"to demonstrate this."
msgstr ""

#: ../../docs/tutorials/physics/using_character_body_2d.rst:451
msgid "Platformer movement"
msgstr ""

#: ../../docs/tutorials/physics/using_character_body_2d.rst:453
msgid ""
"Let's try one more popular example: the 2D platformer. ``move_and_slide()`` "
"is ideal for quickly getting a functional character controller up and "
"running. If you've downloaded the sample project, you can find this in "
"\"platformer.tscn\"."
msgstr ""

#: ../../docs/tutorials/physics/using_character_body_2d.rst:457
msgid ""
"For this example, we'll assume you have a level made of one or more "
"``StaticBody2D`` objects. They can be any shape and size. In the sample "
"project, we're using :ref:`Polygon2D <class_Polygon2D>` to create the "
"platform shapes."
msgstr ""

#: ../../docs/tutorials/physics/using_character_body_2d.rst:461
msgid "Here's the code for the player body:"
msgstr ""

#: ../../docs/tutorials/physics/using_character_body_2d.rst:524
msgid ""
"In this code we're using ``move_and_slide()`` as described above - to move "
"the body along its velocity vector, sliding along any collision surfaces "
"such as the ground or a platform. We're also using ``is_on_floor()`` to "
"check if a jump should be allowed. Without this, you'd be able to \"jump\" "
"in midair; great if you're making Flappy Bird, but not for a platformer game."
msgstr ""

#: ../../docs/tutorials/physics/using_character_body_2d.rst:530
msgid ""
"There is a lot more that goes into a complete platformer character: "
"acceleration, double-jumps, coyote-time, and many more. The code above is "
"just a starting point. You can use it as a base to expand into whatever "
"movement behavior you need for your own projects."
msgstr ""

#: ../../docs/tutorials/physics/ray-casting.rst:4
msgid "Ray-casting"
msgstr ""

#: ../../docs/tutorials/physics/ray-casting.rst:9
msgid ""
"One of the most common tasks in game development is casting a ray (or custom "
"shaped object) and checking what it hits. This enables complex behaviors, "
"AI, etc. to take place. This tutorial will explain how to do this in 2D and "
"3D."
msgstr ""

#: ../../docs/tutorials/physics/ray-casting.rst:14
msgid ""
"Godot stores all the low level game information in servers, while the scene "
"is only a frontend. As such, ray casting is generally a lower-level task. "
"For simple raycasts, nodes like :ref:`RayCast3D <class_RayCast3D>` and :ref:"
"`RayCast2D <class_RayCast2D>` will work, as they return every frame what the "
"result of a raycast is."
msgstr ""

#: ../../docs/tutorials/physics/ray-casting.rst:21
msgid ""
"Many times, though, ray-casting needs to be a more interactive process so a "
"way to do this by code must exist."
msgstr ""

#: ../../docs/tutorials/physics/ray-casting.rst:25
msgid "Space"
msgstr ""

#: ../../docs/tutorials/physics/ray-casting.rst:27
msgid ""
"In the physics world, Godot stores all the low level collision and physics "
"information in a *space*. The current 2d space (for 2D Physics) can be "
"obtained by accessing :ref:`CanvasItem.get_world_2d().space "
"<class_CanvasItem_method_get_world_2d>`. For 3D, it's :ref:`Node3D."
"get_world_3d().space <class_Node3D_method_get_world_3d>`."
msgstr ""

#: ../../docs/tutorials/physics/ray-casting.rst:33
msgid ""
"The resulting space :ref:`RID <class_RID>` can be used in :ref:"
"`PhysicsServer3D <class_PhysicsServer3D>` and :ref:`PhysicsServer2D "
"<class_PhysicsServer2D>` respectively for 3D and 2D."
msgstr ""

#: ../../docs/tutorials/physics/ray-casting.rst:38
msgid "Accessing space"
msgstr ""

#: ../../docs/tutorials/physics/ray-casting.rst:40
msgid ""
"Godot physics runs by default in the same thread as game logic, but may be "
"set to run on a separate thread to work more efficiently. Due to this, the "
"only time accessing space is safe is during the :ref:`Node."
"_physics_process() <class_Node_private_method__physics_process>` callback. "
"Accessing it from outside this function may result in an error due to space "
"being *locked*."
msgstr ""

#: ../../docs/tutorials/physics/ray-casting.rst:47
msgid ""
"To perform queries into physics space, the :ref:`PhysicsDirectSpaceState2D "
"<class_PhysicsDirectSpaceState2D>` and :ref:`PhysicsDirectSpaceState3D "
"<class_PhysicsDirectSpaceState3D>` must be used."
msgstr ""

#: ../../docs/tutorials/physics/ray-casting.rst:52
msgid "Use the following code in 2D:"
msgstr ""

#: ../../docs/tutorials/physics/ray-casting.rst:69
msgid "Or more directly:"
msgstr ""

#: ../../docs/tutorials/physics/ray-casting.rst:84
msgid "And in 3D:"
msgstr ""

#: ../../docs/tutorials/physics/ray-casting.rst:100
msgid "Raycast query"
msgstr ""

#: ../../docs/tutorials/physics/ray-casting.rst:102
msgid ""
"For performing a 2D raycast query, the method :ref:"
"`PhysicsDirectSpaceState2D.intersect_ray() "
"<class_PhysicsDirectSpaceState2D_method_intersect_ray>` may be used. For "
"example:"
msgstr ""

#: ../../docs/tutorials/physics/ray-casting.rst:125
msgid ""
"The result is a dictionary. If the ray didn't hit anything, the dictionary "
"will be empty. If it did hit something, it will contain collision "
"information:"
msgstr ""

#: ../../docs/tutorials/physics/ray-casting.rst:139
msgid ""
"The ``result`` dictionary when a collision occurs contains the following "
"data:"
msgstr ""

#: ../../docs/tutorials/physics/ray-casting.rst:154
msgid ""
"The data is similar in 3D space, using Vector3 coordinates. Note that to "
"enable collisions with Area3D, the boolean parameter ``collide_with_areas`` "
"must be set to ``true``."
msgstr ""

#: ../../docs/tutorials/physics/ray-casting.rst:175
msgid "Collision exceptions"
msgstr ""

#: ../../docs/tutorials/physics/ray-casting.rst:177
msgid ""
"A common use case for ray casting is to enable a character to gather data "
"about the world around it. One problem with this is that the same character "
"has a collider, so the ray will only detect its parent's collider, as shown "
"in the following image:"
msgstr ""

#: ../../docs/tutorials/physics/ray-casting.rst:184
msgid ""
"To avoid self-intersection, the ``intersect_ray()`` parameters object can "
"take an array of exceptions via its ``exclude`` property. This is an example "
"of how to use it from a CharacterBody2D or any other collision object node:"
msgstr ""

#: ../../docs/tutorials/physics/ray-casting.rst:214
msgid "The exceptions array can contain objects or RIDs."
msgstr ""

#: ../../docs/tutorials/physics/ray-casting.rst:217
msgid "Collision Mask"
msgstr ""

#: ../../docs/tutorials/physics/ray-casting.rst:219
msgid ""
"While the exceptions method works fine for excluding the parent body, it "
"becomes very inconvenient if you need a large and/or dynamic list of "
"exceptions. In this case, it is much more efficient to use the collision "
"layer/mask system."
msgstr ""

#: ../../docs/tutorials/physics/ray-casting.rst:223
msgid ""
"The ``intersect_ray()`` parameters object can also be supplied a collision "
"mask. For example, to use the same mask as the parent body, use the "
"``collision_mask`` member variable. The array of exceptions can be supplied "
"as the last argument as well:"
msgstr ""

#: ../../docs/tutorials/physics/ray-casting.rst:253
msgid ""
"See :ref:`doc_physics_introduction_collision_layer_code_example` for details "
"on how to set the collision mask."
msgstr ""

#: ../../docs/tutorials/physics/ray-casting.rst:256
msgid "3D ray casting from screen"
msgstr ""

#: ../../docs/tutorials/physics/ray-casting.rst:258
msgid ""
"Casting a ray from screen to 3D physics space is useful for object picking. "
"There is not much need to do this because :ref:`CollisionObject3D "
"<class_CollisionObject3D>` has an \"input_event\" signal that will let you "
"know when it was clicked, but in case there is any desire to do it manually, "
"here's how."
msgstr ""

#: ../../docs/tutorials/physics/ray-casting.rst:264
msgid ""
"To cast a ray from the screen, you need a :ref:`Camera3D <class_Camera3D>` "
"node. A ``Camera3D`` can be in two projection modes: perspective and "
"orthogonal. Because of this, both the ray origin and direction must be "
"obtained. This is because ``origin`` changes in orthogonal mode, while "
"``normal`` changes in perspective mode:"
msgstr ""

#: ../../docs/tutorials/physics/ray-casting.rst:272
msgid "To obtain it using a camera, the following code can be used:"
msgstr ""

#: ../../docs/tutorials/physics/ray-casting.rst:299
msgid ""
"Remember that during ``_input()``, the space may be locked, so in practice "
"this query should be run in ``_physics_process()``."
msgstr ""

#: ../../docs/tutorials/physics/ragdoll_system.rst:4
msgid "Ragdoll system"
msgstr ""

#: ../../docs/tutorials/physics/ragdoll_system.rst:9
msgid ""
"Since version 3.1, Godot supports ragdoll physics. Ragdolls rely on physics "
"simulation to create realistic procedural animation. They are used for death "
"animations in many games."
msgstr ""

#: ../../docs/tutorials/physics/ragdoll_system.rst:11
msgid ""
"In this tutorial, we will be using the Platformer3D demo to set up a ragdoll."
msgstr ""

#: ../../docs/tutorials/physics/ragdoll_system.rst:13
msgid ""
"You can download the Platformer3D demo on `GitHub <https://github.com/"
"godotengine/godot-demo-projects/tree/master/3d/platformer>`_ or using the "
"`Asset Library <https://godotengine.org/asset-library/asset/2748>`_."
msgstr ""

#: ../../docs/tutorials/physics/ragdoll_system.rst:16
msgid "Setting up the ragdoll"
msgstr ""

#: ../../docs/tutorials/physics/ragdoll_system.rst:19
msgid "Creating physical bones"
msgstr ""

#: ../../docs/tutorials/physics/ragdoll_system.rst:21
msgid ""
"Like many other features in the engine, there is a node to set up a ragdoll: "
"the :ref:`PhysicalBone3D <class_PhysicalBone3D>` node. To simplify the "
"setup, you can generate ``PhysicalBone`` nodes with the \"Create physical "
"skeleton\" feature in the skeleton node."
msgstr ""

#: ../../docs/tutorials/physics/ragdoll_system.rst:23
msgid ""
"Open the platformer demo in Godot, and then the Robi scene. Select the "
"``Skeleton`` node. A skeleton button appears on the top bar menu:"
msgstr ""

#: ../../docs/tutorials/physics/ragdoll_system.rst:27
msgid ""
"Click it and select the ``Create physical skeleton`` option. Godot will "
"generate ``PhysicalBone`` nodes and collision shapes for each bone in the "
"skeleton and pin joints to connect them together:"
msgstr ""

#: ../../docs/tutorials/physics/ragdoll_system.rst:31
msgid ""
"Some of the generated bones aren't necessary: the ``MASTER`` bone for "
"example. So we're going to clean up the skeleton by removing them."
msgstr ""

#: ../../docs/tutorials/physics/ragdoll_system.rst:34
msgid "Cleaning up the skeleton"
msgstr ""

#: ../../docs/tutorials/physics/ragdoll_system.rst:36
msgid ""
"Each ``PhysicalBone`` the engine needs to simulate has a performance cost, "
"so you want to remove every bone that is too small to make a difference in "
"the simulation, as well as all utility bones."
msgstr ""

#: ../../docs/tutorials/physics/ragdoll_system.rst:38
msgid ""
"For example, if we take a humanoid, you do not want to have physical bones "
"for each finger. You can use a single bone for the entire hand instead, or "
"one for the palm, one for the thumb, and a last one for the other four "
"fingers."
msgstr ""

#: ../../docs/tutorials/physics/ragdoll_system.rst:40
msgid ""
"Remove these physical bones: ``MASTER``, ``waist``, ``neck``, "
"``headtracker``. This gives us an optimized skeleton and makes it easier to "
"control the ragdoll."
msgstr ""

#: ../../docs/tutorials/physics/ragdoll_system.rst:43
msgid "Collision shape adjustment"
msgstr ""

#: ../../docs/tutorials/physics/ragdoll_system.rst:45
msgid ""
"The next task is adjusting the collision shape and the size of physical "
"bones to match the part of the body that each bone should simulate."
msgstr ""

#: ../../docs/tutorials/physics/ragdoll_system.rst:50
msgid "Joints adjustment"
msgstr ""

#: ../../docs/tutorials/physics/ragdoll_system.rst:52
msgid ""
"Once you adjusted the collision shapes, your ragdoll is almost ready. You "
"just want to adjust the pin joints to get a better simulation. "
"``PhysicalBone`` nodes have an unconstrained pin joint assigned to them by "
"default. To change the pin joint, select the ``PhysicalBone`` and change the "
"constraint type in the ``Joint`` section. There, you can change the "
"constraint's orientation and its limits."
msgstr ""

#: ../../docs/tutorials/physics/ragdoll_system.rst:56
msgid "This is the final result:"
msgstr ""

#: ../../docs/tutorials/physics/ragdoll_system.rst:61
msgid "Simulating the ragdoll"
msgstr ""

#: ../../docs/tutorials/physics/ragdoll_system.rst:63
msgid ""
"The ragdoll is now ready to use. To start the simulation and play the "
"ragdoll animation, you need to call the ``physical_bones_start_simulation`` "
"method. Attach a script to the skeleton node and call the method in the "
"``_ready`` method:"
msgstr ""

#: ../../docs/tutorials/physics/ragdoll_system.rst:71
msgid ""
"To stop the simulation, call the ``physical_bones_stop_simulation()`` method."
msgstr ""

#: ../../docs/tutorials/physics/ragdoll_system.rst:75
msgid ""
"You can also limit the simulation to only a few bones. To do so, pass the "
"bone names as a parameter. Here's an example of partial ragdoll simulation:"
msgstr ""

#: ../../docs/tutorials/physics/ragdoll_system.rst:80
msgid "Collision layer and mask"
msgstr ""

#: ../../docs/tutorials/physics/ragdoll_system.rst:82
msgid ""
"Make sure to set up your collision layers and masks properly so the "
"``CharacterBody3D``'s capsule doesn't get in the way of the physics "
"simulation:"
msgstr ""

#: ../../docs/tutorials/physics/ragdoll_system.rst:86
#, fuzzy
msgid ""
"For more information, read :ref:"
"`doc_physics_introduction_collision_layers_and_masks`."
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/physics/kinematic_character_2d.rst:4
msgid "Kinematic character (2D)"
msgstr ""

#: ../../docs/tutorials/physics/kinematic_character_2d.rst:9
msgid ""
"Yes, the name sounds strange. \"Kinematic Character\". What is that? The "
"reason for the name is that, when physics engines came out, they were called "
"\"Dynamics\" engines (because they dealt mainly with collision responses). "
"Many attempts were made to create a character controller using the dynamics "
"engines, but it wasn't as easy as it seemed. Godot has one of the best "
"implementations of dynamic character controller you can find (as it can be "
"seen in the 2d/platformer demo), but using it requires a considerable level "
"of skill and understanding of physics engines (or a lot of patience with "
"trial and error)."
msgstr ""

#: ../../docs/tutorials/physics/kinematic_character_2d.rst:19
msgid ""
"Some physics engines, such as Havok seem to swear by dynamic character "
"controllers as the best option, while others (PhysX) would rather promote "
"the kinematic one."
msgstr ""

#: ../../docs/tutorials/physics/kinematic_character_2d.rst:23
msgid "So, what is the difference?:"
msgstr ""

#: ../../docs/tutorials/physics/kinematic_character_2d.rst:25
msgid ""
"A **dynamic character controller** uses a rigid body with an infinite "
"inertia tensor. It's a rigid body that can't rotate. Physics engines always "
"let objects move and collide, then solve their collisions all together. This "
"makes dynamic character controllers able to interact with other physics "
"objects seamlessly, as seen in the platformer demo. However, these "
"interactions are not always predictable. Collisions can take more than one "
"frame to be solved, so a few collisions may seem to displace a tiny bit. "
"Those problems can be fixed, but require a certain amount of skill."
msgstr ""

#: ../../docs/tutorials/physics/kinematic_character_2d.rst:34
msgid ""
"A **kinematic character controller** is assumed to always begin in a non-"
"colliding state, and will always move to a non-colliding state. If it starts "
"in a colliding state, it will try to free itself like rigid bodies do, but "
"this is the exception, not the rule. This makes their control and motion a "
"lot more predictable and easier to program. However, as a downside, they "
"can't directly interact with other physics objects, unless done by hand in "
"code."
msgstr ""

#: ../../docs/tutorials/physics/kinematic_character_2d.rst:42
msgid ""
"This short tutorial focuses on the kinematic character controller. It uses "
"the old-school way of handling collisions, which is not necessarily simpler "
"under the hood, but well hidden and presented as an API."
msgstr ""

#: ../../docs/tutorials/physics/kinematic_character_2d.rst:47
msgid "Physics process"
msgstr ""

#: ../../docs/tutorials/physics/kinematic_character_2d.rst:49
msgid ""
"To manage the logic of a kinematic body or character, it is always advised "
"to use physics process, because it's called before physics step and its "
"execution is in sync with physics server, also it is called the same amount "
"of times per second, always. This makes physics and motion calculation work "
"in a more predictable way than using regular process, which might have "
"spikes or lose precision if the frame rate is too high or too low."
msgstr ""

#: ../../docs/tutorials/physics/kinematic_character_2d.rst:79
msgid ""
"To have something to test, here's the scene (from the tilemap tutorial): "
"`kinematic_character_2d_starter.zip <https://github.com/godotengine/godot-"
"docs-project-starters/releases/download/latest-4.x/"
"kinematic_character_2d_starter.zip>`_. We'll be creating a new scene for the "
"character. Use the robot sprite and create a scene like this:"
msgstr ""

#: ../../docs/tutorials/physics/kinematic_character_2d.rst:86
msgid ""
"You'll notice that there's a warning icon next to our CollisionShape2D node; "
"that's because we haven't defined a shape for it. Create a new CircleShape2D "
"in the shape property of CollisionShape2D. Click on <CircleShape2D> to go to "
"the options for it, and set the radius to 30:"
msgstr ""

#: ../../docs/tutorials/physics/kinematic_character_2d.rst:93
msgid ""
"**Note: As mentioned before in the physics tutorial, the physics engine "
"can't handle scale on most types of shapes (only collision polygons, planes "
"and segments work), so always change the parameters (such as radius) of the "
"shape instead of scaling it. The same is also true for the kinematic/rigid/"
"static bodies themselves, as their scale affects the shape scale.**"
msgstr ""

#: ../../docs/tutorials/physics/kinematic_character_2d.rst:100
msgid ""
"Now, create a script for the character, the one used as an example above "
"should work as a base."
msgstr ""

#: ../../docs/tutorials/physics/kinematic_character_2d.rst:103
msgid ""
"Finally, instance that character scene in the tilemap, and make the map "
"scene the main one, so it runs when pressing play."
msgstr ""

#: ../../docs/tutorials/physics/kinematic_character_2d.rst:109
msgid "Moving the kinematic character"
msgstr ""

#: ../../docs/tutorials/physics/kinematic_character_2d.rst:111
msgid ""
"Go back to the character scene, and open the script, the magic begins now! "
"Kinematic body will do nothing by default, but it has a useful function "
"called ``CharacterBody2D.move_and_collide()``. This function takes a :ref:"
"`Vector2 <class_Vector2>` as an argument, and tries to apply that motion to "
"the kinematic body. If a collision happens, it stops right at the moment of "
"the collision."
msgstr ""

#: ../../docs/tutorials/physics/kinematic_character_2d.rst:118
msgid "So, let's move our sprite downwards until it hits the floor:"
msgstr ""

#: ../../docs/tutorials/physics/kinematic_character_2d.rst:141
msgid ""
"The result is that the character will move, but stop right when hitting the "
"floor. Pretty cool, huh?"
msgstr ""

#: ../../docs/tutorials/physics/kinematic_character_2d.rst:144
msgid ""
"The next step will be adding gravity to the mix, this way it behaves a "
"little more like a regular game character:"
msgstr ""

#: ../../docs/tutorials/physics/kinematic_character_2d.rst:179
msgid ""
"Now the character falls smoothly. Let's make it walk to the sides, left and "
"right when touching the directional keys. Remember that the values being "
"used (for speed at least) are pixels/second."
msgstr ""

#: ../../docs/tutorials/physics/kinematic_character_2d.rst:183
msgid "This adds basic support for walking when pressing left and right:"
msgstr ""

#: ../../docs/tutorials/physics/kinematic_character_2d.rst:241
msgid "And give it a try."
msgstr ""

#: ../../docs/tutorials/physics/kinematic_character_2d.rst:243
msgid ""
"This is a good starting point for a platformer. A more complete demo can be "
"found in the demo zip distributed with the engine, or in the https://github."
"com/godotengine/godot-demo-projects/tree/master/2d/kinematic_character."
msgstr ""

#: ../../docs/tutorials/physics/soft_body.rst:6
msgid "Using SoftBody"
msgstr ""

#: ../../docs/tutorials/physics/soft_body.rst:8
msgid ""
"Soft bodies (or *soft-body dynamics*) simulate movement, changing shape and "
"other physical properties of deformable objects. This can for example be "
"used to simulate cloth or to create more realistic characters."
msgstr ""

#: ../../docs/tutorials/physics/soft_body.rst:12
msgid "Basic set-up"
msgstr ""

#: ../../docs/tutorials/physics/soft_body.rst:14
msgid ""
"A :ref:`SoftBody3D <class_SoftBody3D>` node is used for soft body "
"simulations."
msgstr ""

#: ../../docs/tutorials/physics/soft_body.rst:16
msgid "We will create a bouncy cube to demonstrate the setup of a soft body."
msgstr ""

#: ../../docs/tutorials/physics/soft_body.rst:18
msgid ""
"Create a new scene with a ``Node3D`` node as root. Then, create a "
"``Softbody`` node. Add a ``CubeMesh`` in the ``mesh`` property of the node "
"in the inspector and increase the subdivision of the mesh for simulation."
msgstr ""

#: ../../docs/tutorials/physics/soft_body.rst:22
msgid ""
"Set the parameters to obtain the type of soft body you aim for. Try to keep "
"the ``Simulation Precision`` above 5, otherwise, the soft body may collapse."
msgstr ""

#: ../../docs/tutorials/physics/soft_body.rst:26
msgid ""
"Handle some parameters with care, as some value can lead to strange results. "
"For example, if the shape is not completely closed and you set pressure to "
"more than 0, the softbody will fly around like a plastic bag under strong "
"wind."
msgstr ""

#: ../../docs/tutorials/physics/soft_body.rst:28
msgid "Play the scene to view the simulation."
msgstr ""

#: ../../docs/tutorials/physics/soft_body.rst:30
msgid ""
"To improve the simulation's result, increase the ``Simulation Precision``, "
"this will give significant improvement at the cost of performance."
msgstr ""

#: ../../docs/tutorials/physics/soft_body.rst:33
msgid "Cloak simulation"
msgstr ""

#: ../../docs/tutorials/physics/soft_body.rst:35
msgid "Let's make a cloak in the Platformer3D demo."
msgstr ""

#: ../../docs/tutorials/physics/soft_body.rst:37
msgid ""
"You can download the Platformer3D demo on `GitHub <https://github.com/"
"godotengine/godot-demo-projects/tree/master/3d/platformer>`_ or `the Asset "
"Library <https://godotengine.org/asset-library/asset/2748>`_."
msgstr ""

#: ../../docs/tutorials/physics/soft_body.rst:39
msgid ""
"Open the ``Player`` scene, add a ``SoftBody`` node and assign a "
"``PlaneMesh`` to it."
msgstr ""

#: ../../docs/tutorials/physics/soft_body.rst:41
msgid ""
"Open the ``PlaneMesh`` properties and set the size(x: 0.5 y: 1) then set "
"``Subdivide Width`` and ``Subdivide Depth`` to 5. Adjust the ``SoftBody``'s "
"position. You should end up with something like this:"
msgstr ""

#: ../../docs/tutorials/physics/soft_body.rst:45
msgid "Subdivision generates a more tessellated mesh for better simulations."
msgstr ""

#: ../../docs/tutorials/physics/soft_body.rst:47
msgid ""
"Add a :ref:`BoneAttachment3D <class_BoneAttachment3D>` node under the "
"skeleton node and select the Neck bone to attach the cloak to the character "
"skeleton."
msgstr ""

#: ../../docs/tutorials/physics/soft_body.rst:49
msgid ""
"``BoneAttachment3D`` node is to attach objects to a bone of a armature. The "
"attached object will follow the bone's movement, weapon of a character can "
"be attached this way."
msgstr ""

#: ../../docs/tutorials/physics/soft_body.rst:53
msgid ""
"To create pinned joints, select the upper vertices in the ``SoftBody`` node:"
msgstr ""

#: ../../docs/tutorials/physics/soft_body.rst:57
msgid ""
"The pinned joints can be found in ``SoftBody``'s ``Attachments`` property, "
"choose the ``BoneAttachment`` as the ``SpatialAttachment`` for each pinned "
"joints, the pinned joints are now attached to the neck."
msgstr ""

#: ../../docs/tutorials/physics/soft_body.rst:61
msgid ""
"Last step is to avoid clipping by adding the Kinematic Body `Player` to "
"``Parent Collision Ignore`` of the ``SoftBody``."
msgstr ""

#: ../../docs/tutorials/physics/soft_body.rst:65
msgid "Play the scene and the cloak should simulate correctly."
msgstr ""

#: ../../docs/tutorials/physics/soft_body.rst:69
msgid ""
"This covers the basic settings of softbody, experiment with the parameters "
"to achieve the effect you are aiming for when making your game."
msgstr ""

#: ../../docs/tutorials/physics/collision_shapes_2d.rst:4
msgid "Collision shapes (2D)"
msgstr ""

#: ../../docs/tutorials/physics/collision_shapes_2d.rst:6
#: ../../docs/tutorials/physics/collision_shapes_3d.rst:6
msgid "This guide explains:"
msgstr ""

#: ../../docs/tutorials/physics/collision_shapes_2d.rst:8
msgid "The types of collision shapes available in 2D in Godot."
msgstr ""

#: ../../docs/tutorials/physics/collision_shapes_2d.rst:9
msgid "Using an image converted to a polygon as a collision shape."
msgstr ""

#: ../../docs/tutorials/physics/collision_shapes_2d.rst:10
msgid "Performance considerations regarding 2D collisions."
msgstr ""

#: ../../docs/tutorials/physics/collision_shapes_2d.rst:12
#: ../../docs/tutorials/physics/collision_shapes_3d.rst:12
msgid ""
"Godot provides many kinds of collision shapes, with different performance "
"and accuracy tradeoffs."
msgstr ""

#: ../../docs/tutorials/physics/collision_shapes_2d.rst:15
msgid ""
"You can define the shape of a :ref:`class_PhysicsBody2D` by adding one or "
"more :ref:`CollisionShape2Ds <class_CollisionShape2D>` or :ref:"
"`CollisionPolygon2Ds <class_CollisionPolygon2D>` as child nodes. Note that "
"you must add a :ref:`class_Shape2D` *resource* to collision shape nodes in "
"the Inspector dock."
msgstr ""

#: ../../docs/tutorials/physics/collision_shapes_2d.rst:23
msgid ""
"When you add multiple collision shapes to a single PhysicsBody2D, you don't "
"have to worry about them overlapping. They won't \"collide\" with each other."
msgstr ""

#: ../../docs/tutorials/physics/collision_shapes_2d.rst:27
#: ../../docs/tutorials/physics/collision_shapes_3d.rst:26
msgid "Primitive collision shapes"
msgstr ""

#: ../../docs/tutorials/physics/collision_shapes_2d.rst:29
#: ../../docs/tutorials/physics/collision_shapes_3d.rst:28
msgid "Godot provides the following primitive collision shape types:"
msgstr ""

#: ../../docs/tutorials/physics/collision_shapes_2d.rst:31
#, fuzzy
msgid ":ref:`class_RectangleShape2D`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/physics/collision_shapes_2d.rst:32
#, fuzzy
msgid ":ref:`class_CircleShape2D`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/physics/collision_shapes_2d.rst:33
#, fuzzy
msgid ":ref:`class_CapsuleShape2D`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/physics/collision_shapes_2d.rst:34
#, fuzzy
msgid ":ref:`class_SegmentShape2D`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/physics/collision_shapes_2d.rst:35
msgid ":ref:`class_SeparationRayShape2D` (designed for characters)"
msgstr ""

#: ../../docs/tutorials/physics/collision_shapes_2d.rst:36
msgid ":ref:`class_WorldBoundaryShape2D` (infinite plane)"
msgstr ""

#: ../../docs/tutorials/physics/collision_shapes_2d.rst:38
#: ../../docs/tutorials/physics/collision_shapes_3d.rst:35
msgid ""
"You can represent the collision of most smaller objects using one or more "
"primitive shapes. However, for more complex objects, such as a large ship or "
"a whole level, you may need convex or concave shapes instead. More on that "
"below."
msgstr ""

#: ../../docs/tutorials/physics/collision_shapes_2d.rst:42
#: ../../docs/tutorials/physics/collision_shapes_3d.rst:39
msgid ""
"We recommend favoring primitive shapes for dynamic objects such as "
"RigidBodies and CharacterBodies as their behavior is the most reliable. They "
"often provide better performance as well."
msgstr ""

#: ../../docs/tutorials/physics/collision_shapes_2d.rst:47
#: ../../docs/tutorials/physics/collision_shapes_3d.rst:44
msgid "Convex collision shapes"
msgstr ""

#: ../../docs/tutorials/physics/collision_shapes_2d.rst:51
msgid ""
"Godot currently doesn't offer a built-in way to create 2D convex collision "
"shapes. This section is mainly here for reference purposes."
msgstr ""

#: ../../docs/tutorials/physics/collision_shapes_2d.rst:54
msgid ""
":ref:`Convex collision shapes <class_ConvexPolygonShape2D>` are a compromise "
"between primitive collision shapes and concave collision shapes. They can "
"represent shapes of any complexity, but with an important caveat. As their "
"name implies, an individual shape can only represent a *convex* shape. For "
"instance, a pyramid is *convex*, but a hollow box is *concave*. To define a "
"concave object with a single collision shape, you need to use a concave "
"collision shape."
msgstr ""

#: ../../docs/tutorials/physics/collision_shapes_2d.rst:61
#: ../../docs/tutorials/physics/collision_shapes_3d.rst:53
msgid ""
"Depending on the object's complexity, you may get better performance by "
"using multiple convex shapes instead of a concave collision shape. Godot "
"lets you use *convex decomposition* to generate convex shapes that roughly "
"match a hollow object. Note this performance advantage no longer applies "
"after a certain amount of convex shapes. For large and complex objects such "
"as a whole level, we recommend using concave shapes instead."
msgstr ""

#: ../../docs/tutorials/physics/collision_shapes_2d.rst:69
#: ../../docs/tutorials/physics/collision_shapes_3d.rst:76
msgid "Concave or trimesh collision shapes"
msgstr ""

#: ../../docs/tutorials/physics/collision_shapes_2d.rst:71
msgid ""
":ref:`Concave collision shapes <class_ConcavePolygonShape2D>`, also called "
"trimesh collision shapes, can take any form, from a few triangles to "
"thousands of triangles. Concave shapes are the slowest option but are also "
"the most accurate in Godot. **You can only use concave shapes within "
"StaticBodies.** They will not work with CharacterBodies or RigidBodies "
"unless the RigidBody's mode is Static."
msgstr ""

#: ../../docs/tutorials/physics/collision_shapes_2d.rst:79
#: ../../docs/tutorials/physics/collision_shapes_3d.rst:86
msgid ""
"Even though concave shapes offer the most accurate *collision*, contact "
"reporting can be less precise than primitive shapes."
msgstr ""

#: ../../docs/tutorials/physics/collision_shapes_2d.rst:82
msgid ""
"When not using TileMaps for level design, concave shapes are the best "
"approach for a level's collision."
msgstr ""

#: ../../docs/tutorials/physics/collision_shapes_2d.rst:85
msgid ""
"You can configure the CollisionPolygon2D node's *build mode* in the "
"inspector. If it is set to **Solids** (the default), collisions will include "
"the polygon and its contained area. If it is set to **Segments**, collisions "
"will only include the polygon edges."
msgstr ""

#: ../../docs/tutorials/physics/collision_shapes_2d.rst:90
msgid ""
"You can generate a concave collision shape from the editor by selecting a "
"Sprite2D and using the **Sprite2D** menu at the top of the 2D viewport. The "
"Sprite2D menu dropdown exposes an option called **Create CollisionPolygon2D "
"Sibling**. Once you click it, it displays a menu with 3 settings:"
msgstr ""

#: ../../docs/tutorials/physics/collision_shapes_2d.rst:95
msgid ""
"**Simplification:** Higher values will result in a less detailed shape, "
"which improves performance at the cost of accuracy."
msgstr ""

#: ../../docs/tutorials/physics/collision_shapes_2d.rst:97
msgid ""
"**Shrink (Pixels):** Higher values will shrink the generated collision "
"polygon relative to the sprite's edges."
msgstr ""

#: ../../docs/tutorials/physics/collision_shapes_2d.rst:99
msgid ""
"**Grow (Pixels):** Higher values will grow the generated collision polygon "
"relative to the sprite's edges. Note that setting Grow and Shrink to equal "
"values may yield different results than leaving both of them on 0."
msgstr ""

#: ../../docs/tutorials/physics/collision_shapes_2d.rst:105
msgid ""
"If you have an image with many small details, it's recommended to create a "
"simplified version and use it to generate the collision polygon. This can "
"result in better performance and game feel, since the player won't be "
"blocked by small, decorative details."
msgstr ""

#: ../../docs/tutorials/physics/collision_shapes_2d.rst:110
msgid ""
"To use a separate image for collision polygon generation, create another "
"Sprite2D, generate a collision polygon sibling from it then remove the "
"Sprite2D node. This way, you can exclude small details from the generated "
"collision."
msgstr ""

#: ../../docs/tutorials/physics/collision_shapes_2d.rst:115
#: ../../docs/tutorials/physics/collision_shapes_3d.rst:115
msgid "Performance caveats"
msgstr ""

#: ../../docs/tutorials/physics/collision_shapes_2d.rst:117
#: ../../docs/tutorials/physics/collision_shapes_3d.rst:117
msgid ""
"You aren't limited to a single collision shape per PhysicsBody. Still, we "
"recommend keeping the number of shapes as low as possible to improve "
"performance, especially for dynamic objects like RigidBodies and "
"CharacterBodies. On top of that, avoid translating, rotating, or scaling "
"CollisionShapes to benefit from the physics engine's internal optimizations."
msgstr ""

#: ../../docs/tutorials/physics/collision_shapes_2d.rst:123
#: ../../docs/tutorials/physics/collision_shapes_3d.rst:123
msgid ""
"When using a single non-transformed collision shape in a StaticBody, the "
"engine's *broad phase* algorithm can discard inactive PhysicsBodies. The "
"*narrow phase* will then only have to take into account the active bodies' "
"shapes. If a StaticBody has many collision shapes, the broad phase will "
"fail. The narrow phase, which is slower, must then perform a collision check "
"against each shape."
msgstr ""

#: ../../docs/tutorials/physics/collision_shapes_2d.rst:129
#: ../../docs/tutorials/physics/collision_shapes_3d.rst:129
msgid ""
"If you run into performance issues, you may have to make tradeoffs in terms "
"of accuracy. Most games out there don't have a 100% accurate collision. They "
"find creative ways to hide it or otherwise make it unnoticeable during "
"normal gameplay."
msgstr ""

#: ../../docs/tutorials/physics/collision_shapes_3d.rst:4
msgid "Collision shapes (3D)"
msgstr ""

#: ../../docs/tutorials/physics/collision_shapes_3d.rst:8
msgid "The types of collision shapes available in 3D in Godot."
msgstr ""

#: ../../docs/tutorials/physics/collision_shapes_3d.rst:9
msgid "Using a convex or a concave mesh as a collision shape."
msgstr ""

#: ../../docs/tutorials/physics/collision_shapes_3d.rst:10
msgid "Performance considerations regarding 3D collisions."
msgstr ""

#: ../../docs/tutorials/physics/collision_shapes_3d.rst:15
msgid ""
"You can define the shape of a :ref:`class_PhysicsBody3D` by adding one or "
"more :ref:`CollisionShape3Ds <class_CollisionShape3D>` as child nodes. Note "
"that you must add a :ref:`class_Shape3D` *resource* to collision shape nodes "
"in the Inspector dock."
msgstr ""

#: ../../docs/tutorials/physics/collision_shapes_3d.rst:22
msgid ""
"When you add multiple collision shapes to a single PhysicsBody, you don't "
"have to worry about them overlapping. They won't \"collide\" with each other."
msgstr ""

#: ../../docs/tutorials/physics/collision_shapes_3d.rst:30
#, fuzzy
msgid ":ref:`class_BoxShape3D`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/physics/collision_shapes_3d.rst:31
#, fuzzy
msgid ":ref:`class_SphereShape3D`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/physics/collision_shapes_3d.rst:32
#, fuzzy
msgid ":ref:`class_CapsuleShape3D`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/physics/collision_shapes_3d.rst:33
#, fuzzy
msgid ":ref:`class_CylinderShape3D`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/physics/collision_shapes_3d.rst:46
msgid ""
":ref:`Convex collision shapes <class_ConvexPolygonShape3D>` are a compromise "
"between primitive collision shapes and concave collision shapes. They can "
"represent shapes of any complexity, but with an important caveat. As their "
"name implies, an individual shape can only represent a *convex* shape. For "
"instance, a pyramid is *convex*, but a hollow box is *concave*. To define a "
"concave object with a single collision shape, you need to use a concave "
"collision shape."
msgstr ""

#: ../../docs/tutorials/physics/collision_shapes_3d.rst:60
msgid ""
"You can generate one or several convex collision shapes from the editor by "
"selecting a MeshInstance3D and using the **Mesh** menu at the top of the 3D "
"viewport. The editor exposes two generation modes:"
msgstr ""

#: ../../docs/tutorials/physics/collision_shapes_3d.rst:64
msgid ""
"**Create Single Convex Collision Sibling** uses the Quickhull algorithm. It "
"creates one CollisionShape node with an automatically generated convex "
"collision shape. Since it only generates a single shape, it provides good "
"performance and is ideal for small objects."
msgstr ""

#: ../../docs/tutorials/physics/collision_shapes_3d.rst:69
msgid ""
"**Create Multiple Convex Collision Siblings** uses the V-HACD algorithm. It "
"creates several CollisionShape nodes, each with a convex shape. Since it "
"generates multiple shapes, it is more accurate for concave objects at the "
"cost of performance. For objects with medium complexity, it will likely be "
"faster than using a single concave collision shape."
msgstr ""

#: ../../docs/tutorials/physics/collision_shapes_3d.rst:78
msgid ""
":ref:`Concave collision shapes <class_ConcavePolygonShape3D>`, also called "
"trimesh collision shapes, can take any form, from a few triangles to "
"thousands of triangles. Concave shapes are the slowest option but are also "
"the most accurate in Godot. **You can only use concave shapes within "
"StaticBodies.** They will not work with CharacterBodies or RigidBodies "
"unless the RigidBody's mode is Static."
msgstr ""

#: ../../docs/tutorials/physics/collision_shapes_3d.rst:89
msgid ""
"When not using GridMaps for level design, concave shapes are the best "
"approach for a level's collision. That said, if your level has small "
"details, you may want to exclude those from collision for performance and "
"game feel. To do so, you can build a simplified collision mesh in a 3D "
"modeler and have Godot generate a collision shape for it automatically. More "
"on that below"
msgstr ""

#: ../../docs/tutorials/physics/collision_shapes_3d.rst:95
msgid ""
"Note that unlike primitive and convex shapes, a concave collision shape "
"doesn't have an actual \"volume\". You can place objects both *outside* of "
"the shape as well as *inside*."
msgstr ""

#: ../../docs/tutorials/physics/collision_shapes_3d.rst:99
msgid ""
"You can generate a concave collision shape from the editor by selecting a "
"MeshInstance3D and using the **Mesh** menu at the top of the 3D viewport. "
"The editor exposes two options:"
msgstr ""

#: ../../docs/tutorials/physics/collision_shapes_3d.rst:103
msgid ""
"**Create Trimesh Static Body** is a convenient option. It creates a "
"StaticBody containing a concave shape matching the mesh's geometry."
msgstr ""

#: ../../docs/tutorials/physics/collision_shapes_3d.rst:106
msgid ""
"**Create Trimesh Collision Sibling** creates a CollisionShape node with a "
"concave shape matching the mesh's geometry."
msgstr ""

#: ../../docs/tutorials/physics/collision_shapes_3d.rst:111
msgid ""
"See :ref:`doc_importing_3d_scenes` for information on how to export models "
"for Godot and automatically generate collision shapes on import."
msgstr ""

#: ../../docs/tutorials/physics/large_world_coordinates.rst:4
msgid "Large world coordinates"
msgstr ""

#: ../../docs/tutorials/physics/large_world_coordinates.rst:8
msgid ""
"Large world coordinates are mainly useful in 3D projects; they are rarely "
"required in 2D projects. Also, unlike 3D rendering, 2D rendering currently "
"doesn't benefit from increased precision when large world coordinates are "
"enabled."
msgstr ""

#: ../../docs/tutorials/physics/large_world_coordinates.rst:14
msgid "Why use large world coordinates?"
msgstr ""

#: ../../docs/tutorials/physics/large_world_coordinates.rst:16
msgid ""
"In Godot, physics simulation and rendering both rely on *floating-point* "
"numbers. However, in computing, floating-point numbers have **limited "
"precision and range**. This can be a problem for games with huge worlds, "
"such as space or planetary-scale simulation games."
msgstr ""

#: ../../docs/tutorials/physics/large_world_coordinates.rst:21
msgid ""
"Precision is the greatest when the value is close to ``0.0``. Precision "
"becomes gradually lower as the value increases or decreases away from "
"``0.0``. This occurs every time the floating-point number's *exponent* "
"increases, which happens when the floating-point number surpasses a power of "
"2 value (2, 4, 8, 16, …). Every time this occurs, the number's minimum step "
"will *increase*, resulting in a loss of precision."
msgstr ""

#: ../../docs/tutorials/physics/large_world_coordinates.rst:28
msgid ""
"In practice, this means that as the player moves away from the world origin "
"(``Vector2(0, 0)`` in 2D games or ``Vector3(0, 0, 0)`` in 3D games), "
"precision will decrease."
msgstr ""

#: ../../docs/tutorials/physics/large_world_coordinates.rst:32
msgid ""
"This loss of precision can result in objects appearing to \"vibrate\" when "
"far away from the world origin, as the model's position will snap to the "
"nearest value that can be represented in a floating-point number. This can "
"also result in physics glitches that only occur when the player is far from "
"the world origin."
msgstr ""

#: ../../docs/tutorials/physics/large_world_coordinates.rst:38
msgid ""
"The range determines the minimum and maximum values that can be stored in "
"the number. If the player tries to move past this range, they will simply "
"not be able to. However, in practice, floating-point precision almost always "
"becomes a problem before the range does."
msgstr ""

#: ../../docs/tutorials/physics/large_world_coordinates.rst:43
msgid ""
"The range and precision (minimum step between two exponent intervals) are "
"determined by the floating-point number type. The *theoretical* range allows "
"extremely high values to be stored in single-precision floats, but with very "
"low precision. In practice, a floating-point type that cannot represent all "
"integer values is not very useful. At extreme values, precision becomes so "
"low that the number cannot even distinguish two separate *integer* values "
"from each other."
msgstr ""

#: ../../docs/tutorials/physics/large_world_coordinates.rst:50
msgid ""
"This is the range where individual integer values can be represented in a "
"floating-point number:"
msgstr ""

#: ../../docs/tutorials/physics/large_world_coordinates.rst:53
msgid ""
"**Single-precision float range (represent all integers):** Between "
"-16,777,216 and 16,777,216"
msgstr ""

#: ../../docs/tutorials/physics/large_world_coordinates.rst:54
msgid ""
"**Double-precision float range (represent all integers):** Between -9 "
"quadrillion and 9 quadrillion"
msgstr ""

#: ../../docs/tutorials/physics/large_world_coordinates.rst:57
msgid "Range"
msgstr ""

#: ../../docs/tutorials/physics/large_world_coordinates.rst:57
msgid "Single step"
msgstr ""

#: ../../docs/tutorials/physics/large_world_coordinates.rst:57
msgid "Double step"
msgstr ""

#: ../../docs/tutorials/physics/large_world_coordinates.rst:59
msgid "[1; 2]"
msgstr ""

#: ../../docs/tutorials/physics/large_world_coordinates.rst:59
msgid "~0.0000001"
msgstr ""

#: ../../docs/tutorials/physics/large_world_coordinates.rst:59
#: ../../docs/tutorials/physics/large_world_coordinates.rst:61
#: ../../docs/tutorials/physics/large_world_coordinates.rst:63
msgid "~1e-15"
msgstr ""

#: ../../docs/tutorials/physics/large_world_coordinates.rst:59
msgid "Precision becomes greater near 0.0 (this table is abbreviated)."
msgstr ""

#: ../../docs/tutorials/physics/large_world_coordinates.rst:61
msgid "[2; 4]"
msgstr ""

#: ../../docs/tutorials/physics/large_world_coordinates.rst:61
msgid "~0.0000002"
msgstr ""

#: ../../docs/tutorials/physics/large_world_coordinates.rst:63
msgid "[4; 8]"
msgstr ""

#: ../../docs/tutorials/physics/large_world_coordinates.rst:63
msgid "~0.0000005"
msgstr ""

#: ../../docs/tutorials/physics/large_world_coordinates.rst:65
msgid "[8; 16]"
msgstr ""

#: ../../docs/tutorials/physics/large_world_coordinates.rst:65
msgid "~0.000001"
msgstr ""

#: ../../docs/tutorials/physics/large_world_coordinates.rst:65
#: ../../docs/tutorials/physics/large_world_coordinates.rst:67
#: ../../docs/tutorials/physics/large_world_coordinates.rst:69
msgid "~1e-14"
msgstr ""

#: ../../docs/tutorials/physics/large_world_coordinates.rst:67
msgid "[16; 32]"
msgstr ""

#: ../../docs/tutorials/physics/large_world_coordinates.rst:67
msgid "~0.000002"
msgstr ""

#: ../../docs/tutorials/physics/large_world_coordinates.rst:69
msgid "[32; 64]"
msgstr ""

#: ../../docs/tutorials/physics/large_world_coordinates.rst:69
msgid "~0.000004"
msgstr ""

#: ../../docs/tutorials/physics/large_world_coordinates.rst:71
msgid "[64; 128]"
msgstr ""

#: ../../docs/tutorials/physics/large_world_coordinates.rst:71
msgid "~0.000008"
msgstr ""

#: ../../docs/tutorials/physics/large_world_coordinates.rst:71
#: ../../docs/tutorials/physics/large_world_coordinates.rst:73
#: ../../docs/tutorials/physics/large_world_coordinates.rst:75
msgid "~1e-13"
msgstr ""

#: ../../docs/tutorials/physics/large_world_coordinates.rst:73
msgid "[128; 256]"
msgstr ""

#: ../../docs/tutorials/physics/large_world_coordinates.rst:73
msgid "~0.000015"
msgstr ""

#: ../../docs/tutorials/physics/large_world_coordinates.rst:75
msgid "[256; 512]"
msgstr ""

#: ../../docs/tutorials/physics/large_world_coordinates.rst:75
msgid "~0.00003"
msgstr ""

#: ../../docs/tutorials/physics/large_world_coordinates.rst:77
msgid "[512; 1024]"
msgstr ""

#: ../../docs/tutorials/physics/large_world_coordinates.rst:77
msgid "~0.00006"
msgstr ""

#: ../../docs/tutorials/physics/large_world_coordinates.rst:77
#: ../../docs/tutorials/physics/large_world_coordinates.rst:79
#: ../../docs/tutorials/physics/large_world_coordinates.rst:81
#: ../../docs/tutorials/physics/large_world_coordinates.rst:84
#: ../../docs/tutorials/physics/large_world_coordinates.rst:87
msgid "~1e-12"
msgstr ""

#: ../../docs/tutorials/physics/large_world_coordinates.rst:79
msgid "[1024; 2048]"
msgstr ""

#: ../../docs/tutorials/physics/large_world_coordinates.rst:79
msgid "~0.0001"
msgstr ""

#: ../../docs/tutorials/physics/large_world_coordinates.rst:81
msgid "[2048; 4096]"
msgstr ""

#: ../../docs/tutorials/physics/large_world_coordinates.rst:81
msgid "~0.0002"
msgstr ""

#: ../../docs/tutorials/physics/large_world_coordinates.rst:81
msgid ""
"Maximum *recommended* single-precision range for a first-person 3D game "
"without rendering artifacts or physics glitches."
msgstr ""

#: ../../docs/tutorials/physics/large_world_coordinates.rst:84
msgid "[4096; 8192]"
msgstr ""

#: ../../docs/tutorials/physics/large_world_coordinates.rst:84
msgid "~0.0005"
msgstr ""

#: ../../docs/tutorials/physics/large_world_coordinates.rst:84
msgid ""
"Maximum *recommended* single-precision range for a third-person 3D game "
"without rendering artifacts or physics glitches."
msgstr ""

#: ../../docs/tutorials/physics/large_world_coordinates.rst:87
msgid "[8192; 16384]"
msgstr ""

#: ../../docs/tutorials/physics/large_world_coordinates.rst:87
msgid "~0.001"
msgstr ""

#: ../../docs/tutorials/physics/large_world_coordinates.rst:89
msgid "[16384; 32768]"
msgstr ""

#: ../../docs/tutorials/physics/large_world_coordinates.rst:89
msgid "~0.0019"
msgstr ""

#: ../../docs/tutorials/physics/large_world_coordinates.rst:89
#: ../../docs/tutorials/physics/large_world_coordinates.rst:92
#: ../../docs/tutorials/physics/large_world_coordinates.rst:95
msgid "~1e-11"
msgstr ""

#: ../../docs/tutorials/physics/large_world_coordinates.rst:89
msgid ""
"Maximum *recommended* single-precision range for a top-down 3D game without "
"rendering artifacts or physics glitches."
msgstr ""

#: ../../docs/tutorials/physics/large_world_coordinates.rst:92
msgid "[32768; 65536]"
msgstr ""

#: ../../docs/tutorials/physics/large_world_coordinates.rst:92
msgid "~0.0039"
msgstr ""

#: ../../docs/tutorials/physics/large_world_coordinates.rst:92
msgid ""
"Maximum *recommended* single-precision range for any 3D game. Double "
"precision (large world coordinates) is usually required past this point."
msgstr ""

#: ../../docs/tutorials/physics/large_world_coordinates.rst:95
msgid "[65536; 131072]"
msgstr ""

#: ../../docs/tutorials/physics/large_world_coordinates.rst:95
msgid "~0.0078"
msgstr ""

#: ../../docs/tutorials/physics/large_world_coordinates.rst:97
msgid "[131072; 262144]"
msgstr ""

#: ../../docs/tutorials/physics/large_world_coordinates.rst:97
msgid "~0.0156"
msgstr ""

#: ../../docs/tutorials/physics/large_world_coordinates.rst:97
msgid "~1e-10"
msgstr ""

#: ../../docs/tutorials/physics/large_world_coordinates.rst:99
msgid "> 262144"
msgstr ""

#: ../../docs/tutorials/physics/large_world_coordinates.rst:99
msgid "> ~0.0313"
msgstr ""

#: ../../docs/tutorials/physics/large_world_coordinates.rst:99
msgid "~1e-10 (0.0000000001)"
msgstr ""

#: ../../docs/tutorials/physics/large_world_coordinates.rst:99
msgid ""
"Double-precision remains far more precise than single-precision past this "
"value."
msgstr ""

#: ../../docs/tutorials/physics/large_world_coordinates.rst:103
msgid ""
"When using single-precision floats, it is possible to go past the suggested "
"ranges, but more visible artifacting will occur and physics glitches will be "
"more common (such as the player not walking straight in certain directions)."
msgstr ""

#: ../../docs/tutorials/physics/large_world_coordinates.rst:109
msgid ""
"See the `Demystifying Floating Point Precision <https://blog.demofox."
"org/2017/11/21/>`__ article for more information."
msgstr ""

#: ../../docs/tutorials/physics/large_world_coordinates.rst:113
msgid "How large world coordinates work"
msgstr ""

#: ../../docs/tutorials/physics/large_world_coordinates.rst:115
msgid ""
"Large world coordinates (also known as **double-precision physics**) "
"increase the precision level of all floating-point computations within the "
"engine."
msgstr ""

#: ../../docs/tutorials/physics/large_world_coordinates.rst:118
msgid ""
"By default, :ref:`class_float` is 64-bit in GDScript, but :ref:"
"`class_Vector2`, :ref:`class_Vector3` and :ref:`class_Vector4` are 32-bit. "
"This means that the precision of vector types is much more limited. To "
"resolve this, we can increase the number of bits used to represent a "
"floating-point number in a Vector type. This results in an *exponential* "
"increase in precision, which means the final value is not just twice as "
"precise, but potentially thousands of times more precise at high values. The "
"maximum value that can be represented is also greatly increased by going "
"from a single-precision float to a double-precision float."
msgstr ""

#: ../../docs/tutorials/physics/large_world_coordinates.rst:128
msgid ""
"To avoid model snapping issues when far away from the world origin, Godot's "
"3D rendering engine will increase its precision for rendering operations "
"when large world coordinates are enabled. The shaders do not use double-"
"precision floats for performance reasons, but an `alternative solution "
"<https://github.com/godotengine/godot/pull/66178>`__ is used to emulate "
"double precision for rendering using single-precision floats."
msgstr ""

#: ../../docs/tutorials/physics/large_world_coordinates.rst:136
msgid ""
"Enabling large world coordinates comes with a performance and memory usage "
"penalty, especially on 32-bit CPUs. Only enable large world coordinates if "
"you actually need them."
msgstr ""

#: ../../docs/tutorials/physics/large_world_coordinates.rst:140
msgid ""
"This feature is tailored towards mid-range/high-end desktop platforms. Large "
"world coordinates may not perform well on low-end mobile devices, unless you "
"take steps to reduce CPU usage with other means (such as decreasing the "
"number of physics ticks per second)."
msgstr ""

#: ../../docs/tutorials/physics/large_world_coordinates.rst:145
msgid ""
"On low-end platforms, an *origin shifting* approach can be used instead to "
"allow for large worlds without using double-precision physics and rendering. "
"Origin shifting works with single-precision floats, but it introduces more "
"complexity to game logic, especially in multiplayer games. Therefore, origin "
"shifting is not detailed on this page."
msgstr ""

#: ../../docs/tutorials/physics/large_world_coordinates.rst:152
msgid "Who are large world coordinates for?"
msgstr ""

#: ../../docs/tutorials/physics/large_world_coordinates.rst:154
msgid ""
"Large world coordinates are typically required for 3D space or planetary-"
"scale simulation games. This extends to games that require supporting *very* "
"fast movement speeds, but also very slow *and* precise movements at times."
msgstr ""

#: ../../docs/tutorials/physics/large_world_coordinates.rst:158
msgid ""
"On the other hand, it's important to only use large world coordinates when "
"actually required (for performance reasons). Large world coordinates are "
"usually **not** required for:"
msgstr ""

#: ../../docs/tutorials/physics/large_world_coordinates.rst:162
msgid "2D games, as precision issues are usually less noticeable."
msgstr ""

#: ../../docs/tutorials/physics/large_world_coordinates.rst:163
msgid "Games with small-scale or medium-scale worlds."
msgstr ""

#: ../../docs/tutorials/physics/large_world_coordinates.rst:164
msgid ""
"Games with large worlds, but split into different levels with loading "
"sequences in between. You can center each level portion around the world "
"origin to avoid precision issues without a performance penalty."
msgstr ""

#: ../../docs/tutorials/physics/large_world_coordinates.rst:167
msgid ""
"Open world games with a *playable on-foot area* not exceeding 8192×8192 "
"meters (centered around the world origin). As shown in the above table, the "
"level of precision remains acceptable within that range, even for a first-"
"person game."
msgstr ""

#: ../../docs/tutorials/physics/large_world_coordinates.rst:171
msgid ""
"**If in doubt**, you probably don't need to use large world coordinates in "
"your project. For reference, most modern AAA open world titles don't use a "
"large world coordinates system and still rely on single-precision floats for "
"both rendering and physics."
msgstr ""

#: ../../docs/tutorials/physics/large_world_coordinates.rst:177
msgid "Enabling large world coordinates"
msgstr ""

#: ../../docs/tutorials/physics/large_world_coordinates.rst:179
msgid ""
"This process requires recompiling the editor and all export template "
"binaries you intend to use. If you only intend to export your project in "
"release mode, you can skip the compilation of debug export templates. In any "
"case, you'll need to compile an editor build so you can test your large "
"precision world without having to export the project every time."
msgstr ""

#: ../../docs/tutorials/physics/large_world_coordinates.rst:185
msgid ""
"See the :ref:`Compiling <toc-devel-compiling>` section for compiling "
"instructions for each target platform. You will need to add the "
"``precision=double`` SCons option when compiling the editor and export "
"templates."
msgstr ""

#: ../../docs/tutorials/physics/large_world_coordinates.rst:189
msgid ""
"The resulting binaries will be named with a ``.double`` suffix to "
"distinguish them from single-precision binaries (which lack any precision "
"suffix). You can then specify the binaries as custom export templates in "
"your project's export presets in the Export dialog."
msgstr ""

#: ../../docs/tutorials/physics/large_world_coordinates.rst:195
msgid "Compatibility between single-precision and double-precision builds"
msgstr ""

#: ../../docs/tutorials/physics/large_world_coordinates.rst:197
msgid ""
"When saving a *binary* resource using the :ref:`class_ResourceSaver` "
"singleton, a special flag is stored in the file if the resource was saved "
"using a build that uses double-precision numbers. As a result, all binary "
"resources will change on disk when you switch to a double-precision build "
"and save over them."
msgstr ""

#: ../../docs/tutorials/physics/large_world_coordinates.rst:202
msgid ""
"Both single-precision and double-precision builds support using the :ref:"
"`class_ResourceLoader` singleton on resources that use this special flag. "
"This means single-precision builds can load resources saved using double-"
"precision builds and vice versa. Text-based resources don't store a double-"
"precision flag, as they don't require such a flag for correct reading."
msgstr ""

#: ../../docs/tutorials/physics/large_world_coordinates.rst:209
msgid "Known incompatibilities"
msgstr ""

#: ../../docs/tutorials/physics/large_world_coordinates.rst:211
msgid ""
"In a networked multiplayer game, the server and all clients should be using "
"the same build type to ensure precision remains consistent across clients. "
"Using different build types *may* work, but various issues can occur."
msgstr ""

#: ../../docs/tutorials/physics/large_world_coordinates.rst:214
msgid ""
"The GDExtension API changes in an incompatible way in double-precision "
"builds. This means extensions **must** be rebuilt to work with double-"
"precision builds. On the extension developer's end, the ``REAL_T_IS_DOUBLE`` "
"define is enabled when building a GDExtension with ``precision=double``. "
"``real_t`` can be used as an alias for ``float`` in single-precision builds, "
"and ``double`` in double-precision builds."
msgstr ""

#: ../../docs/tutorials/physics/large_world_coordinates.rst:224
msgid ""
"Since 3D rendering shaders don't actually use double-precision floats, there "
"are some limitations when it comes to 3D rendering precision:"
msgstr ""

#: ../../docs/tutorials/physics/large_world_coordinates.rst:227
msgid ""
"Shaders using the ``skip_vertex_transform`` or ``world_vertex_coords`` don't "
"benefit from increased precision."
msgstr ""

#: ../../docs/tutorials/physics/large_world_coordinates.rst:229
msgid ""
":ref:`Triplanar mapping <doc_standard_material_3d_triplanar_mapping>` "
"doesn't benefit from increased precision. Materials using triplanar mapping "
"will exhibit visible jittering when far away from the world origin."
msgstr ""

#: ../../docs/tutorials/physics/large_world_coordinates.rst:233
msgid ""
"2D rendering currently doesn't benefit from increased precision when large "
"world coordinates are enabled. This can cause visible model snapping to "
"occur when far away from the world origin (starting from a few million "
"pixels at typical zoom levels). 2D physics calculations will still benefit "
"from increased precision though."
msgstr ""

#: ../../docs/tutorials/physics/troubleshooting_physics_issues.rst:4
msgid "Troubleshooting physics issues"
msgstr ""

#: ../../docs/tutorials/physics/troubleshooting_physics_issues.rst:6
msgid ""
"When working with a physics engine, you may encounter unexpected results."
msgstr ""

#: ../../docs/tutorials/physics/troubleshooting_physics_issues.rst:8
msgid ""
"While many of these issues can be resolved through configuration, some of "
"them are the result of engine bugs. For known issues related to the physics "
"engine, see `open physics-related issues on GitHub <https://github.com/"
"godotengine/godot/issues?q=is%3Aopen+is%3Aissue+label%3Atopic%3Aphysics>`__. "
"Looking through `closed issues <https://github.com/godotengine/godot/issues?"
"q=+is%3Aclosed+is%3Aissue+label%3Atopic%3Aphysics>`__ can also help answer "
"questions related to physics engine behavior."
msgstr ""

#: ../../docs/tutorials/physics/troubleshooting_physics_issues.rst:17
msgid "Objects are passing through each other at high speeds"
msgstr ""

#: ../../docs/tutorials/physics/troubleshooting_physics_issues.rst:19
msgid ""
"This is known as *tunneling*. Enabling **Continuous CD** in the RigidBody "
"properties can sometimes resolve this issue. If this does not help, there "
"are other solutions you can try:"
msgstr ""

#: ../../docs/tutorials/physics/troubleshooting_physics_issues.rst:23
msgid ""
"Make your static collision shapes thicker. For example, if you have a thin "
"floor that the player can't get below in some way, you can make the collider "
"thicker than the floor's visual representation."
msgstr ""

#: ../../docs/tutorials/physics/troubleshooting_physics_issues.rst:26
msgid ""
"Modify your fast-moving object's collision shape depending on its movement "
"speed. The faster the object moves, the larger the collision shape should "
"extend outside of the object to ensure it can collide with thin walls more "
"reliably."
msgstr ""

#: ../../docs/tutorials/physics/troubleshooting_physics_issues.rst:30
msgid ""
"Increase **Physics Ticks Per Second** in the advanced Project Settings. "
"While this has other benefits (such as more stable simulation and reduced "
"input lag), this increases CPU utilization and may not be viable for mobile/"
"web platforms. Multipliers of the default value of ``60`` (such as ``120``, "
"``180`` or ``240``) should be preferred for a smooth appearance on most "
"displays."
msgstr ""

#: ../../docs/tutorials/physics/troubleshooting_physics_issues.rst:37
msgid "Stacked objects are unstable and wobbly"
msgstr ""

#: ../../docs/tutorials/physics/troubleshooting_physics_issues.rst:39
msgid ""
"Despite seeming like a simple problem, stable RigidBody simulation with "
"stacked objects is difficult to implement in a physics engine. This is "
"caused by integrating forces going against each other. The more stacked "
"objects are present, the stronger the forces will be against each other. "
"This eventually causes the simulation to become wobbly, making the objects "
"unable to rest on top of each other without moving."
msgstr ""

#: ../../docs/tutorials/physics/troubleshooting_physics_issues.rst:46
msgid ""
"Increasing the physics simulation rate can help alleviate this issue. To do "
"so, increase **Physics Ticks Per Second** in the advanced Project Settings. "
"Note that increases CPU utilization and may not be viable for mobile/web "
"platforms. Multipliers of the default value of ``60`` (such as ``120``, "
"``180`` or ``240``) should be preferred for a smooth appearance on most "
"displays."
msgstr ""

#: ../../docs/tutorials/physics/troubleshooting_physics_issues.rst:53
msgid "Scaled physics bodies or collision shapes do not collide correctly"
msgstr ""

#: ../../docs/tutorials/physics/troubleshooting_physics_issues.rst:55
msgid ""
"Godot does not currently support scaling of physics bodies or collision "
"shapes. As a workaround, change the collision shape's extents instead of "
"changing its scale. If you want the visual representation's scale to change "
"as well, change the scale of the underlying visual representation (Sprite2D, "
"MeshInstance3D, …) and change the collision shape's extents separately. Make "
"sure the collision shape is not a child of the visual representation in this "
"case."
msgstr ""

#: ../../docs/tutorials/physics/troubleshooting_physics_issues.rst:62
msgid ""
"Since resources are shared by default, you'll have to make the collision "
"shape resource unique if you don't want the change to be applied to all "
"nodes using the same collision shape resource in the scene. This can be done "
"by calling ``duplicate()`` in a script on the collision shape resource "
"*before* changing its size."
msgstr ""

#: ../../docs/tutorials/physics/troubleshooting_physics_issues.rst:69
msgid "Thin objects are wobbly when resting on the floor"
msgstr ""

#: ../../docs/tutorials/physics/troubleshooting_physics_issues.rst:71
#, fuzzy
msgid "This can be due to one of two causes:"
msgstr "Glavna dokumentacija za sajt je podeljena na sledeća poglavlja:"

#: ../../docs/tutorials/physics/troubleshooting_physics_issues.rst:73
msgid "The floor's collision shape is too thin."
msgstr ""

#: ../../docs/tutorials/physics/troubleshooting_physics_issues.rst:74
msgid "The RigidBody's collision shape is too thin."
msgstr ""

#: ../../docs/tutorials/physics/troubleshooting_physics_issues.rst:76
msgid ""
"In the first case, this can be alleviated by making the floor's collision "
"shape thicker. For example, if you have a thin floor that the player can't "
"get below in some way, you can make the collider thicker than the floor's "
"visual representation."
msgstr ""

#: ../../docs/tutorials/physics/troubleshooting_physics_issues.rst:81
msgid ""
"In the second case, this can usually only be resolved by increasing the "
"physics simulation rate (as making the shape thicker would cause a "
"disconnect between the RigidBody's visual representation and its collision)."
msgstr ""

#: ../../docs/tutorials/physics/troubleshooting_physics_issues.rst:85
msgid ""
"In both cases, increasing the physics simulation rate can also help "
"alleviate this issue. To do so, increase **Physics Ticks Per Second** in the "
"advanced Project Settings. Note that this increases CPU utilization and may "
"not be viable for mobile/web platforms. Multipliers of the default value of "
"``60`` (such as ``120``, ``180`` or ``240``) should be preferred for a "
"smooth appearance on most displays."
msgstr ""

#: ../../docs/tutorials/physics/troubleshooting_physics_issues.rst:93
msgid "Cylinder collision shapes are unstable"
msgstr ""

#: ../../docs/tutorials/physics/troubleshooting_physics_issues.rst:95
msgid ""
"During the transition from Bullet to GodotPhysics in Godot 4, cylinder "
"collision shapes had to be reimplemented from scratch. However, cylinder "
"collision shapes are one of the most difficult shapes to support, which is "
"why many other physics engines don't provide any support for them. There are "
"several known bugs with cylinder collision shapes currently."
msgstr ""

#: ../../docs/tutorials/physics/troubleshooting_physics_issues.rst:101
msgid ""
"We recommend using box or capsule collision shapes for characters for now. "
"Boxes generally provide the best reliability, but have the downside of "
"making the character take more space diagonally. Capsule collision shapes do "
"not have this downside, but their shape can make precision platforming more "
"difficult."
msgstr ""

#: ../../docs/tutorials/physics/troubleshooting_physics_issues.rst:107
msgid "VehicleBody simulation is unstable, especially at high speeds"
msgstr ""

#: ../../docs/tutorials/physics/troubleshooting_physics_issues.rst:109
msgid ""
"When a physics body moves at a high speed, it travels a large distance "
"between each physics step. For instance, when using the 1 unit = 1 meter "
"convention in 3D, a vehicle moving at 360 km/h will travel 100 units per "
"second. With the default physics simulation rate of 60 Hz, the vehicle moves "
"by ~1.67 units each physics tick. This means that small objects may be "
"ignored entirely by the vehicle (due to tunneling), but also that the "
"simulation has little data to work with in general at such a high speed."
msgstr ""

#: ../../docs/tutorials/physics/troubleshooting_physics_issues.rst:117
msgid ""
"Fast-moving vehicles can benefit a lot from an increased physics simulation "
"rate. To do so, increase **Physics Ticks Per Second** in the advanced "
"Project Settings. Note that this increases CPU utilization and may not be "
"viable for mobile/web platforms. Multipliers of the default value of ``60`` "
"(such as ``120``, ``180`` or ``240``) should be preferred for a smooth "
"appearance on most displays."
msgstr ""

#: ../../docs/tutorials/physics/troubleshooting_physics_issues.rst:125
msgid "Collision results in bumps when an object moves across tiles"
msgstr ""

#: ../../docs/tutorials/physics/troubleshooting_physics_issues.rst:127
msgid ""
"This is a known issue in the physics engine caused by the object bumping on "
"a shape's edges, even though that edge is covered by another shape. This can "
"occur in both 2D and 3D."
msgstr ""

#: ../../docs/tutorials/physics/troubleshooting_physics_issues.rst:131
msgid ""
"The best way to work around this issue is to create a \"composite\" "
"collider. This means that instead of individual tiles having their "
"collision, you create a single collision shape representing the collision "
"for a group of tiles. Typically, you should split composite colliders on a "
"per-island basis (which means each group of touching tiles gets its own "
"collider)."
msgstr ""

#: ../../docs/tutorials/physics/troubleshooting_physics_issues.rst:137
msgid ""
"Using a composite collider can also improve physics simulation performance "
"in certain cases. However, since the composite collision shape is much more "
"complex, this may not be a net performance win in all cases."
msgstr ""

#: ../../docs/tutorials/physics/troubleshooting_physics_issues.rst:142
msgid "Framerate drops when an object touches another object"
msgstr ""

#: ../../docs/tutorials/physics/troubleshooting_physics_issues.rst:144
msgid ""
"This is likely due to one of the objects using a collision shape that is too "
"complex. Convex collision shapes should use a number of shapes as low as "
"possible for performance reasons. When relying on Godot's automatic "
"generation, it's possible that you ended up with dozens if not hundreds of "
"shapes created for a single convex shape collision resource."
msgstr ""

#: ../../docs/tutorials/physics/troubleshooting_physics_issues.rst:150
msgid ""
"In some cases, replacing a convex collider with a couple of primitive "
"collision shapes (box, sphere, or capsule) can deliver better performance."
msgstr ""

#: ../../docs/tutorials/physics/troubleshooting_physics_issues.rst:153
msgid ""
"This issue can also occur with StaticBodies that use very detailed trimesh "
"(concave) collisions. In this case, use a simplified representation of the "
"level geometry as a collider. Not only this will improve physics simulation "
"performance significantly, but this can also improve stability by letting "
"you remove small fixtures and crevices from being considered by collision."
msgstr ""

#: ../../docs/tutorials/physics/troubleshooting_physics_issues.rst:160
msgid "Physics simulation is unreliable when far away from the world origin"
msgstr ""

#: ../../docs/tutorials/physics/troubleshooting_physics_issues.rst:162
msgid ""
"This is caused by floating-point precision errors, which become more "
"pronounced as the physics simulation occurs further away from the world "
"origin. This issue also affects rendering, which results in wobbly camera "
"movement when far away from the world origin. See :ref:"
"`doc_large_world_coordinates` for more information."
msgstr ""

#: ../../docs/tutorials/platform/android/android_library.rst:4
#, fuzzy
msgid "Godot Android library"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/platform/android/android_library.rst:6
msgid ""
"The Godot Engine for Android platforms is designed to be used as an `Android "
"library <https://developer.android.com/studio/projects/android-library>`_. "
"This architecture enables several key features on Android platforms:"
msgstr ""

#: ../../docs/tutorials/platform/android/android_library.rst:9
msgid ""
"Ability to integrate the Gradle build system within the Godot Editor, which "
"provides the ability to leverage more components from the Android ecosystem "
"such as libraries and tools"
msgstr ""

#: ../../docs/tutorials/platform/android/android_library.rst:11
msgid "Ability to make the engine portable and embeddable:"
msgstr ""

#: ../../docs/tutorials/platform/android/android_library.rst:13
msgid ""
"Key in enabling the port of the Godot Editor to Android and mobile XR devices"
msgstr ""

#: ../../docs/tutorials/platform/android/android_library.rst:14
msgid ""
"Key in allowing the integration and reuse of Godot's capabilities within "
"existing codebase"
msgstr ""

#: ../../docs/tutorials/platform/android/android_library.rst:16
msgid ""
"Below we describe some of the use-cases and scenarios this architecture "
"enables."
msgstr ""

#: ../../docs/tutorials/platform/android/android_library.rst:19
#, fuzzy
msgid "Using the Godot Android library"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/platform/android/android_library.rst:21
msgid ""
"The Godot Android library is packaged as an AAR archive file and hosted on "
"`MavenCentral <https://central.sonatype.com/artifact/org.godotengine/"
"godot>`_ along with `its documentation <https://javadoc.io/doc/org."
"godotengine/godot/latest/index.html>`_."
msgstr ""

#: ../../docs/tutorials/platform/android/android_library.rst:23
msgid ""
"It provides access to Godot APIs and capabilities on Android platforms for "
"the following non-exhaustive use-cases."
msgstr ""

#: ../../docs/tutorials/platform/android/android_library.rst:26
#: ../../docs/tutorials/platform/android/android_plugin.rst:4
#, fuzzy
msgid "Godot Android plugins"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/platform/android/android_library.rst:28
msgid ""
"Android plugins are powerful tools to extend the capabilities of the Godot "
"Engine by tapping into the functionality provided by Android platforms and "
"ecosystem."
msgstr ""

#: ../../docs/tutorials/platform/android/android_library.rst:31
msgid ""
"An Android plugin is an Android library with a dependency on the Godot "
"Android library which the plugin uses to integrate into the engine's "
"lifecycle and to access Godot APIs, granting it powerful capabilities such "
"as GDExtension support which allows to update / mod the engine behavior as "
"needed."
msgstr ""

#: ../../docs/tutorials/platform/android/android_library.rst:35
msgid ""
"For more information, see :ref:`Godot Android plugins <doc_android_plugin>`."
msgstr ""

#: ../../docs/tutorials/platform/android/android_library.rst:38
msgid "Embedding Godot in existing Android projects"
msgstr ""

#: ../../docs/tutorials/platform/android/android_library.rst:40
msgid ""
"The Godot Engine can be embedded within existing Android applications or "
"libraries, allowing developers to leverage mature and battle-tested code and "
"libraries better suited to a specific task."
msgstr ""

#: ../../docs/tutorials/platform/android/android_library.rst:43
msgid ""
"The hosting component is responsible for driving the engine lifecycle via "
"Godot's Android APIs. These APIs can also be used to provide bidirectional "
"communication between the host and the embedded Godot instance allowing for "
"greater control over the desired experience."
msgstr ""

#: ../../docs/tutorials/platform/android/android_library.rst:47
msgid ""
"We showcase how this is done using a sample Android app that embeds the "
"Godot Engine as an Android view, and uses it to render 3D GLTF models."
msgstr ""

#: ../../docs/tutorials/platform/android/android_library.rst:50
msgid ""
"The `GLTF Viewer <https://github.com/m4gr3d/Godot-Android-Samples/tree/"
"master/apps/gltf_viewer>`_ sample app uses an `Android RecyclerView "
"component <https://developer.android.com/develop/ui/views/layout/"
"recyclerview>`_ to create a list of GLTF items, populated from `Kenney's "
"Food Kit pack <https://kenney.nl/assets/food-kit>`_. When an item on the "
"list is selected, the app's logic interacts with the embedded Godot Engine "
"to render the selected GLTF item as a 3D model."
msgstr ""

#: ../../docs/tutorials/platform/android/android_library.rst:56
msgid ""
"The sample app source code can be found `on GitHub <https://github.com/"
"m4gr3d/Godot-Android-Samples/tree/master/apps/gltf_viewer>`_. Follow the "
"instructions on `its README <https://github.com/m4gr3d/Godot-Android-Samples/"
"blob/master/apps/gltf_viewer/README.md>`_ to build and install it."
msgstr ""

#: ../../docs/tutorials/platform/android/android_library.rst:59
msgid "Below we break-down the steps used to create the GLTF Viewer app."
msgstr ""

#: ../../docs/tutorials/platform/android/android_library.rst:63
msgid ""
"Currently only a single instance of the Godot Engine is supported per "
"process. You can configure the process the Android Activity runs under using "
"the `android:process attribute <https://developer.android.com/guide/topics/"
"manifest/activity-element#proc>`_."
msgstr ""

#: ../../docs/tutorials/platform/android/android_library.rst:68
msgid ""
"Automatic resizing / orientation configuration events are not supported and "
"may cause a crash. You can disable those events:"
msgstr ""

#: ../../docs/tutorials/platform/android/android_library.rst:71
msgid ""
"By locking to a specific orientation using the `android:screenOrientation "
"attribute <https://developer.android.com/guide/topics/manifest/activity-"
"element#screen>`_."
msgstr ""

#: ../../docs/tutorials/platform/android/android_library.rst:72
msgid ""
"By declaring that the Activity will handle these configuration events using "
"the `android:configChanges attribute <https://developer.android.com/guide/"
"topics/manifest/activity-element#config>`_."
msgstr ""

#: ../../docs/tutorials/platform/android/android_library.rst:75
#, fuzzy
msgid "1. Create the Android app"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/platform/android/android_library.rst:79
msgid ""
"The Android sample app was created using `Android Studio <https://developer."
"android.com/studio>`_ and using `Gradle <https://developer.android.com/"
"build>`_ as the build system."
msgstr ""

#: ../../docs/tutorials/platform/android/android_library.rst:82
msgid ""
"The Android ecosystem provides multiple tools, IDEs, build systems for "
"creating Android apps so feel free to use what you're familiar with, and "
"update the steps below accordingly (contributions to this documentation are "
"welcomed as well!)."
msgstr ""

#: ../../docs/tutorials/platform/android/android_library.rst:86
msgid ""
"Set up an Android application project. It may be a brand new empty project, "
"or an existing project"
msgstr ""

#: ../../docs/tutorials/platform/android/android_library.rst:87
msgid ""
"Add the `maven dependency for the Godot Android library <https://central."
"sonatype.com/artifact/org.godotengine/godot>`_"
msgstr ""

#: ../../docs/tutorials/platform/android/android_library.rst:89
msgid ""
"If using ``gradle``, add the following to the ``dependency`` section of the "
"app's gradle build file. Make sure to update ``<version>`` to the latest "
"version of the Godot Android library:"
msgstr ""

#: ../../docs/tutorials/platform/android/android_library.rst:95
msgid ""
"If using ``gradle``, include the following ``aaptOptions`` configuration "
"under the ``android > defaultConfig`` section of the app's gradle build "
"file. Doing so allows ``gradle`` to include Godot's hidden directories when "
"building the app binary."
msgstr ""

#: ../../docs/tutorials/platform/android/android_library.rst:97
msgid ""
"If your build system does not support including hidden directories, you can "
"`configure the Godot project to not use hidden directories <https://docs."
"godotengine.org/en/stable/classes/class_projectsettings.html#class-"
"projectsettings-property-application-config-use-hidden-project-data-"
"directory>`_ by deselecting ``Project Settings... > Application > Config > "
"Use Hidden Project Data Directory``."
msgstr ""

#: ../../docs/tutorials/platform/android/android_library.rst:111
msgid ""
"Create / update the application's Activity that will be hosting the Godot "
"Engine instance. For the sample app, this is `MainActivity <https://github."
"com/m4gr3d/Godot-Android-Samples/blob/master/apps/gltf_viewer/src/main/java/"
"fhuyakou/godot/app/android/gltfviewer/MainActivity.kt>`_"
msgstr ""

#: ../../docs/tutorials/platform/android/android_library.rst:113
msgid ""
"The host Activity should implement the `GodotHost interface <https://github."
"com/godotengine/godot/blob/master/platform/android/java/lib/src/org/"
"godotengine/godot/GodotHost.java>`_"
msgstr ""

#: ../../docs/tutorials/platform/android/android_library.rst:114
msgid ""
"The sample app uses `Fragments <https://developer.android.com/guide/"
"fragments>`_ to organize its UI, so it uses `GodotFragment <https://github."
"com/godotengine/godot/blob/master/platform/android/java/lib/src/org/"
"godotengine/godot/GodotFragment.java>`_, a fragment component provided by "
"the Godot Android library to automatically host and manage the Godot Engine "
"instance."
msgstr ""

#: ../../docs/tutorials/platform/android/android_library.rst:139
msgid ""
"The Godot Android library also provide `GodotActivity <https://github.com/"
"godotengine/godot/blob/master/platform/android/java/lib/src/org/godotengine/"
"godot/GodotActivity.kt>`_, an Activity component that can be extended to "
"automatically host and manage the Godot Engine instance."
msgstr ""

#: ../../docs/tutorials/platform/android/android_library.rst:141
msgid ""
"Alternatively, applications can directly create a `Godot <https://github.com/"
"godotengine/godot/blob/master/platform/android/java/lib/src/org/godotengine/"
"godot/Godot.kt>`_ instance, host and manage it themselves."
msgstr ""

#: ../../docs/tutorials/platform/android/android_library.rst:143
msgid ""
"Using `GodotHost#getHostPlugins(...) <https://github.com/m4gr3d/Godot-"
"Android-Samples/blob/0e3440f357f8be5b4c63a4fe75766793199a99d0/apps/"
"gltf_viewer/src/main/java/fhuyakou/godot/app/android/gltfviewer/MainActivity."
"kt#L55>`_, the sample app creates a `runtime GodotPlugin instance <https://"
"github.com/m4gr3d/Godot-Android-Samples/blob/master/apps/gltf_viewer/src/"
"main/java/fhuyakou/godot/app/android/gltfviewer/AppPlugin.kt>`_ that's used "
"to send :ref:`signals <doc_signals>` to the ``gdscript`` logic"
msgstr ""

#: ../../docs/tutorials/platform/android/android_library.rst:145
msgid ""
"The runtime ``GodotPlugin`` can also be used by ``gdscript`` logic to access "
"JVM methods. For more information, see :ref:`Godot Android plugins "
"<doc_android_plugin>`."
msgstr ""

#: ../../docs/tutorials/platform/android/android_library.rst:147
msgid "Add any additional logic that will be used by your application"
msgstr ""

#: ../../docs/tutorials/platform/android/android_library.rst:149
msgid ""
"For the sample app, this includes adding the `ItemsSelectionFragment "
"fragment <https://github.com/m4gr3d/Godot-Android-Samples/blob/master/apps/"
"gltf_viewer/src/main/java/fhuyakou/godot/app/android/gltfviewer/"
"ItemsSelectionFragment.kt>`_ (and related classes), a fragment used to build "
"and show the list of GLTF items"
msgstr ""

#: ../../docs/tutorials/platform/android/android_library.rst:151
msgid ""
"Open the ``AndroidManifest.xml`` file, and configure the orientation if "
"needed using the `android:screenOrientation attribute <https://developer."
"android.com/guide/topics/manifest/activity-element#screen>`_"
msgstr ""

#: ../../docs/tutorials/platform/android/android_library.rst:153
msgid ""
"If needed, disable automatic resizing / orientation configuration changes "
"using the `android:configChanges attribute <https://developer.android.com/"
"guide/topics/manifest/activity-element#config>`_"
msgstr ""

#: ../../docs/tutorials/platform/android/android_library.rst:167
#, fuzzy
msgid "2. Create the Godot project"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/platform/android/android_library.rst:171
msgid ""
"On Android, Godot's project files are exported to the ``assets`` directory "
"of the generated ``apk`` binary."
msgstr ""

#: ../../docs/tutorials/platform/android/android_library.rst:173
msgid ""
"We leverage that architecture to bind our Android app and Godot project "
"together by creating the Godot project in the Android app's ``assets`` "
"directory."
msgstr ""

#: ../../docs/tutorials/platform/android/android_library.rst:175
msgid ""
"Note that it's also possible to create the Godot project in a separate "
"directory and export it as a `PCK or ZIP file <https://docs.godotengine.org/"
"en/stable/tutorials/export/exporting_projects.html#pck-versus-zip-pack-file-"
"formats>`_ to the Android app's ``assets`` directory. Using this approach "
"requires passing the ``--main-pack "
"<pck_or_zip_filepath_relative_to_assets_dir>`` argument to the hosted Godot "
"Engine instance using `GodotHost#getCommandLine() <https://github.com/"
"godotengine/godot/blob/6916349697a4339216469e9bf5899b983d78db07/platform/"
"android/java/lib/src/org/godotengine/godot/GodotHost.java#L45>`_."
msgstr ""

#: ../../docs/tutorials/platform/android/android_library.rst:179
msgid ""
"The instructions below and the sample app follow the first approach of "
"creating the Godot project in the Android app's ``assets`` directory."
msgstr ""

#: ../../docs/tutorials/platform/android/android_library.rst:182
msgid ""
"As mentioned in the **note** above, open the Godot Editor and create a Godot "
"project directly (no subfolder) in the ``assets`` directory of the Android "
"application project"
msgstr ""

#: ../../docs/tutorials/platform/android/android_library.rst:184
msgid ""
"See the sample app's `Godot project <https://github.com/m4gr3d/Godot-Android-"
"Samples/tree/master/apps/gltf_viewer/src/main/assets>`_ for reference"
msgstr ""

#: ../../docs/tutorials/platform/android/android_library.rst:186
#, fuzzy
msgid "Configure the Godot project as desired"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/platform/android/android_library.rst:188
msgid ""
"Make sure the `orientation <https://docs.godotengine.org/en/stable/classes/"
"class_projectsettings.html#class-projectsettings-property-display-window-"
"handheld-orientation>`_ set for the Godot project matches the one set in the "
"Android app's manifest"
msgstr ""

#: ../../docs/tutorials/platform/android/android_library.rst:189
msgid ""
"For Android, make sure `textures/vram_compression/import_etc2_astc <https://"
"docs.godotengine.org/en/stable/classes/class_projectsettings.html#class-"
"projectsettings-property-rendering-textures-vram-compression-import-etc2-"
"astc>`_ is set to `true`"
msgstr ""

#: ../../docs/tutorials/platform/android/android_library.rst:191
msgid "Update the Godot project script logic as needed"
msgstr ""

#: ../../docs/tutorials/platform/android/android_library.rst:193
msgid ""
"For the sample app, the `script logic <https://github.com/m4gr3d/Godot-"
"Android-Samples/blob/master/apps/gltf_viewer/src/main/assets/main.gd>`_ "
"queries for the runtime ``GodotPlugin`` instance and uses it to register for "
"signals fired by the app logic"
msgstr ""

#: ../../docs/tutorials/platform/android/android_library.rst:194
msgid ""
"The app logic fires a signal every time an item is selected in the list. The "
"signal contains the filepath of the GLTF model, which is used by the "
"``gdscript`` logic to render the model."
msgstr ""

#: ../../docs/tutorials/platform/android/android_library.rst:228
#, fuzzy
msgid "3. Build and run the app"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/platform/android/android_library.rst:230
msgid ""
"Once you complete configuration of your Godot project, build and run the "
"Android app. If set up correctly, the host Activity will initialize the "
"embedded Godot Engine on startup. The Godot Engine will check the ``assets`` "
"directory for project files to load (unless configured to look for a ``main "
"pack``), and will proceed to run the project."
msgstr ""

#: ../../docs/tutorials/platform/android/android_library.rst:234
msgid ""
"While the app is running on device, you can check `Android logcat <https://"
"developer.android.com/studio/debug/logcat>`_ to investigate any errors or "
"crashes."
msgstr ""

#: ../../docs/tutorials/platform/android/android_library.rst:236
msgid ""
"For reference, check the `build and install instructions <https://github.com/"
"m4gr3d/Godot-Android-Samples/blob/master/apps/gltf_viewer/README.md>`_ for "
"the GLTF Viewer sample app."
msgstr ""

#: ../../docs/tutorials/platform/android/android_plugin.rst:9
msgid ""
"Android plugins are powerful tools to extend the capabilities of the Godot "
"engine by tapping into the functionality provided by Android platforms and "
"ecosystem."
msgstr ""

#: ../../docs/tutorials/platform/android/android_plugin.rst:12
msgid ""
"For example in Godot 4, Android plugins are used to support multiple Android-"
"based XR platforms without encumbering the core codebase with vendor "
"specific code or binaries."
msgstr ""

#: ../../docs/tutorials/platform/android/android_plugin.rst:16
msgid "Android plugin"
msgstr ""

#: ../../docs/tutorials/platform/android/android_plugin.rst:18
msgid ""
"**Version 1 (v1)** of the Android plugin system was introduced in Godot 3 "
"and compatible with Godot 4.0 and 4.1. That version allowed developers to "
"augment the Godot engine with Java, Kotlin and native functionality."
msgstr ""

#: ../../docs/tutorials/platform/android/android_plugin.rst:21
msgid ""
"Starting in Godot 4.2, Android plugins built on the v1 architecture are now "
"deprecated. Instead, Godot 4.2 introduces a new **Version 2 (v2)** "
"architecture for Android plugins."
msgstr ""

#: ../../docs/tutorials/platform/android/android_plugin.rst:25
msgid "v2 Architecture"
msgstr ""

#: ../../docs/tutorials/platform/android/android_plugin.rst:29
msgid ""
"Godot Android plugin leverages the :ref:`Gradle build system "
"<doc_android_gradle_build>`."
msgstr ""

#: ../../docs/tutorials/platform/android/android_plugin.rst:32
msgid ""
"Building on the previous v1 architecture, Android plugins continue to be "
"derived from the `Android archive library <https://developer.android.com/"
"studio/projects/android-library#aar-contents>`_."
msgstr ""

#: ../../docs/tutorials/platform/android/android_plugin.rst:35
msgid ""
"At its core, a Godot Android plugin v2 is an Android library with a "
"dependency on the :ref:`Godot Android library <doc_android_library>`, and a "
"custom Android library manifest."
msgstr ""

#: ../../docs/tutorials/platform/android/android_plugin.rst:38
msgid ""
"This architecture allows Android plugins to extend the functionality of the "
"engine with:"
msgstr ""

#: ../../docs/tutorials/platform/android/android_plugin.rst:40
msgid "Android platform APIs"
msgstr ""

#: ../../docs/tutorials/platform/android/android_plugin.rst:41
msgid "Android libraries"
msgstr ""

#: ../../docs/tutorials/platform/android/android_plugin.rst:42
#, fuzzy
msgid "Kotlin and Java libraries"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/platform/android/android_plugin.rst:43
msgid "Native libraries (via JNI)"
msgstr ""

#: ../../docs/tutorials/platform/android/android_plugin.rst:44
#, fuzzy
msgid "GDExtension libraries"
msgstr "Razvoj"

#: ../../docs/tutorials/platform/android/android_plugin.rst:46
msgid ""
"Each plugin has an init class extending from the `GodotPlugin <https://"
"github.com/godotengine/godot/blob/0a7f75ec7b465604b6496c8f5f1d638aed250d6d/"
"platform/android/java/lib/src/org/godotengine/godot/plugin/GodotPlugin."
"java#L80>`_ class which is provided by the :ref:`Godot Android library "
"<doc_android_library>`."
msgstr ""

#: ../../docs/tutorials/platform/android/android_plugin.rst:49
msgid ""
"The ``GodotPlugin`` class provides APIs to access the running Godot instance "
"and hook into its lifecycle. It is loaded at runtime by the Godot engine."
msgstr ""

#: ../../docs/tutorials/platform/android/android_plugin.rst:52
msgid "v2 Packaging format"
msgstr ""

#: ../../docs/tutorials/platform/android/android_plugin.rst:54
msgid ""
"v1 Android plugins required a custom ``gdap`` configuration file that was "
"used by the Godot Editor to detect and load them. However this approach had "
"several drawbacks, primary ones being that it lacked flexibility and "
"departed from the `existing Godot EditorExportPlugin format, delivery and "
"installation flow <https://docs.godotengine.org/en/stable/tutorials/plugins/"
"editor/installing_plugins.html>`_."
msgstr ""

#: ../../docs/tutorials/platform/android/android_plugin.rst:58
msgid ""
"This has been resolved for v2 Android plugins by deprecating the ``gdap`` "
"packaging and configuration mechanism in favor of the existing Godot "
"``EditorExportPlugin`` packaging format. The ``EditorExportPlugin`` API in "
"turn has been extended to properly support Android plugins."
msgstr ""

#: ../../docs/tutorials/platform/android/android_plugin.rst:64
#, fuzzy
msgid "Building a v2 Android plugin"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/platform/android/android_plugin.rst:66
msgid ""
"A github project template **is provided** at https://github.com/m4gr3d/Godot-"
"Android-Plugin-Template as a **quickstart for building Godot Android plugins "
"for Godot 4.2+**. You can follow the `template README <https://github.com/"
"m4gr3d/Godot-Android-Plugin-Template#readme>`_ to set up your own Godot "
"Android plugin project."
msgstr ""

#: ../../docs/tutorials/platform/android/android_plugin.rst:71
msgid ""
"To provide further understanding, here is a break-down of the steps used to "
"create the project template:"
msgstr ""

#: ../../docs/tutorials/platform/android/android_plugin.rst:73
msgid ""
"Create an Android library module using `these instructions <https://"
"developer.android.com/studio/projects/android-library>`_"
msgstr ""

#: ../../docs/tutorials/platform/android/android_plugin.rst:75
msgid ""
"Add the Godot Android library as a dependency by updating the module's "
"``gradle`` `build file <https://github.com/m4gr3d/Godot-Android-Plugin-"
"Template/blob/main/plugin/build.gradle.kts#L42>`_::"
msgstr ""

#: ../../docs/tutorials/platform/android/android_plugin.rst:81
msgid ""
"The Godot Android library is `hosted on MavenCentral <https://central."
"sonatype.com/artifact/org.godotengine/godot>`_, and updated for each release."
msgstr ""

#: ../../docs/tutorials/platform/android/android_plugin.rst:83
msgid ""
"Create `GodotAndroidPlugin <https://github.com/m4gr3d/Godot-Android-Plugin-"
"Template/blob/a01286b4cb459133bf07b11dfabdfd3980268797/plugin/src/main/java/"
"org/godotengine/plugin/android/template/GodotAndroidPlugin.kt#L10>`_, an "
"init class for the plugin extending `GodotPlugin <https://github.com/"
"godotengine/godot/blob/0a7f75ec7b465604b6496c8f5f1d638aed250d6d/platform/"
"android/java/lib/src/org/godotengine/godot/plugin/GodotPlugin.java#L80>`_."
msgstr ""

#: ../../docs/tutorials/platform/android/android_plugin.rst:85
msgid ""
"If the plugin exposes Kotlin or Java methods to be called from GDScript, "
"they must be annotated with `@UsedByGodot <https://github.com/godotengine/"
"godot/blob/0a7f75ec7b465604b6496c8f5f1d638aed250d6d/platform/android/java/"
"lib/src/org/godotengine/godot/plugin/UsedByGodot.java#L45>`_. The name "
"called from GDScript **must match the method name exactly**. There is **no** "
"coercing ``snake_case`` to ``camelCase``. For example, from GDScript::"
msgstr ""

#: ../../docs/tutorials/platform/android/android_plugin.rst:91
msgid ""
"If the plugin uses `signals <https://docs.godotengine.org/en/stable/"
"getting_started/step_by_step/signals.html>`_, the init class must return the "
"set of signals used by overriding `GodotPlugin::getPluginSignals() <https://"
"github.com/godotengine/godot/blob/fa3428ff25bc577d2a3433090478a6d615567056/"
"platform/android/java/lib/src/org/godotengine/godot/plugin/GodotPlugin."
"java#L302>`_. To emit signals, the plugin can use the `GodotPlugin::"
"emitSignal(...) method <https://github.com/godotengine/godot/"
"blob/0a7f75ec7b465604b6496c8f5f1d638aed250d6d/platform/android/java/lib/src/"
"org/godotengine/godot/plugin/GodotPlugin.java#L317>`_."
msgstr ""

#: ../../docs/tutorials/platform/android/android_plugin.rst:93
msgid ""
"Update the plugin ``AndroidManifest.xml`` `file <https://github.com/m4gr3d/"
"Godot-Android-Plugin-Template/blob/main/plugin/src/main/AndroidManifest."
"xml>`_ with the following meta-data::"
msgstr ""

#: ../../docs/tutorials/platform/android/android_plugin.rst:100
msgid "Where:"
msgstr ""

#: ../../docs/tutorials/platform/android/android_plugin.rst:102
msgid "``PluginName`` is the name of the plugin"
msgstr ""

#: ../../docs/tutorials/platform/android/android_plugin.rst:103
msgid ""
"``plugin.init.ClassFullName`` is the full component name (package + class "
"name) of the plugin init class (e.g: ``org.godotengine.plugin.android."
"template.GodotAndroidPlugin``)."
msgstr ""

#: ../../docs/tutorials/platform/android/android_plugin.rst:105
msgid ""
"Create the `EditorExportPlugin configuration <https://github.com/m4gr3d/"
"Godot-Android-Plugin-Template/tree/main/plugin/export_scripts_template>`_ to "
"package the plugin. The steps used to create the configuration can be seen "
"in the `Packaging a v2 Android plugin`_ section."
msgstr ""

#: ../../docs/tutorials/platform/android/android_plugin.rst:109
msgid "Building a v2 Android plugin with GDExtension capabilities"
msgstr ""

#: ../../docs/tutorials/platform/android/android_plugin.rst:111
msgid ""
"Similar to GDNative support in v1 Android plugins, v2 Android plugins "
"support the ability to integrate GDExtension capabilities."
msgstr ""

#: ../../docs/tutorials/platform/android/android_plugin.rst:113
msgid ""
"A github project template is provided at https://github.com/m4gr3d/"
"GDExtension-Android-Plugin-Template as a quickstart for building GDExtension "
"Android plugins for Godot 4.2+. You can follow the `template's README "
"<https://github.com/m4gr3d/GDExtension-Android-Plugin-Template#readme>`_ to "
"set up your own Godot Android plugin project."
msgstr ""

#: ../../docs/tutorials/platform/android/android_plugin.rst:120
#, fuzzy
msgid "Migrating a v1 Android plugin to v2"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/platform/android/android_plugin.rst:122
msgid ""
"Use the following steps if you have a v1 Android plugin you want to migrate "
"to v2:"
msgstr ""

#: ../../docs/tutorials/platform/android/android_plugin.rst:124
msgid "Update the plugin's manifest file:"
msgstr ""

#: ../../docs/tutorials/platform/android/android_plugin.rst:126
msgid ""
"Change the ``org.godotengine.plugin.v1`` prefix to ``org.godotengine.plugin."
"v2``"
msgstr ""

#: ../../docs/tutorials/platform/android/android_plugin.rst:128
msgid "Update the Godot Android library build dependency:"
msgstr ""

#: ../../docs/tutorials/platform/android/android_plugin.rst:130
msgid ""
"You can continue using the ``godot-lib.<version>.<status>.aar`` binary from "
"`Godot's download page <https://godotengine.org/download>`_ if that's your "
"preference. Make sure it's updated to the latest stable version."
msgstr ""

#: ../../docs/tutorials/platform/android/android_plugin.rst:131
msgid "Or you can switch to the MavenCentral provided dependency::"
msgstr ""

#: ../../docs/tutorials/platform/android/android_plugin.rst:137
msgid ""
"After updating the Godot Android library dependency, sync or build the "
"plugin and resolve any compile errors:"
msgstr ""

#: ../../docs/tutorials/platform/android/android_plugin.rst:139
msgid ""
"The ``Godot`` instance provided by ``GodotPlugin::getGodot()`` no longer has "
"access to a ``android.content.Context`` reference. Use ``GodotPlugin::"
"getActivity()`` instead."
msgstr ""

#: ../../docs/tutorials/platform/android/android_plugin.rst:141
msgid ""
"Delete the ``gdap`` configuration file(s) and follow the instructions in the "
"`Packaging a v2 Android plugin`_ section to set up the plugin configuration."
msgstr ""

#: ../../docs/tutorials/platform/android/android_plugin.rst:144
#, fuzzy
msgid "Packaging a v2 Android plugin"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/platform/android/android_plugin.rst:146
msgid ""
"As mentioned, a v2 Android plugin is now provided to the Godot Editor as an "
"``EditorExportPlugin`` plugin, so it shares a lot of the `same packaging "
"steps <https://docs.godotengine.org/en/stable/tutorials/plugins/editor/"
"making_plugins.html#creating-a-plugin>`_."
msgstr ""

#: ../../docs/tutorials/platform/android/android_plugin.rst:148
msgid ""
"Add the plugin output binaries within the plugin directory (e.g: in ``addons/"
"<plugin_name>/``)"
msgstr ""

#: ../../docs/tutorials/platform/android/android_plugin.rst:150
msgid ""
"Add the `tool script <https://docs.godotengine.org/en/stable/tutorials/"
"plugins/editor/making_plugins.html#the-script-file>`_ for the export "
"functionality within the plugin directory (e.g: in ``addons/<plugin_name>/``)"
msgstr ""

#: ../../docs/tutorials/platform/android/android_plugin.rst:152
msgid ""
"The created script must be a ``@tool`` script, or else it will not work "
"properly"
msgstr ""

#: ../../docs/tutorials/platform/android/android_plugin.rst:153
msgid ""
"The export tool script is used to configure the Android plugin and hook it "
"within the Godot Editor's export process. It should look something like "
"this::"
msgstr ""

#: ../../docs/tutorials/platform/android/android_plugin.rst:195
msgid ""
"Here are the set of `EditorExportPlugin APIs <https://docs.godotengine.org/"
"en/stable/classes/class_editorexportplugin.html>`_ most relevant to use in "
"this tool script:"
msgstr ""

#: ../../docs/tutorials/platform/android/android_plugin.rst:197
msgid ""
"`_supports_platform <https://docs.godotengine.org/en/latest/classes/"
"class_editorexportplugin.html#class-editorexportplugin-method-supports-"
"platform>`_: returns ``true`` if the plugin supports the given platform. For "
"Android plugins, this must return ``true`` when ``platform`` is "
"`EditorExportPlatformAndroid <https://docs.godotengine.org/en/stable/classes/"
"class_editorexportplatformandroid.html>`_"
msgstr ""

#: ../../docs/tutorials/platform/android/android_plugin.rst:198
msgid ""
"`_get_android_libraries <https://docs.godotengine.org/en/latest/classes/"
"class_editorexportplugin.html#class-editorexportplugin-method-get-android-"
"libraries>`_: retrieve the local paths of the Android libraries binaries "
"(AAR files) provided by the plugin"
msgstr ""

#: ../../docs/tutorials/platform/android/android_plugin.rst:199
msgid ""
"`_get_android_dependencies <https://docs.godotengine.org/en/latest/classes/"
"class_editorexportplugin.html#class-editorexportplugin-method-get-android-"
"dependencies>`_: retrieve the set of Android maven dependencies (e.g: `org."
"godot.example:my-plugin:0.0.0`) provided by the plugin"
msgstr ""

#: ../../docs/tutorials/platform/android/android_plugin.rst:200
msgid ""
"`_get_android_dependencies_maven_repos <https://docs.godotengine.org/en/"
"latest/classes/class_editorexportplugin.html#class-editorexportplugin-method-"
"get-android-dependencies-maven-repos>`_: retrieve the urls of the maven "
"repos for the android dependencies provided by ``_get_android_dependencies``"
msgstr ""

#: ../../docs/tutorials/platform/android/android_plugin.rst:201
msgid ""
"`_get_android_manifest_activity_element_contents <https://docs.godotengine."
"org/en/latest/classes/class_editorexportplugin.html#class-editorexportplugin-"
"method-get-android-manifest-activity-element-contents>`_: update the "
"contents of the `<activity>` element in the generated Android manifest"
msgstr ""

#: ../../docs/tutorials/platform/android/android_plugin.rst:202
msgid ""
"`_get_android_manifest_application_element_contents <https://docs."
"godotengine.org/en/latest/classes/class_editorexportplugin.html#class-"
"editorexportplugin-method-get-android-manifest-application-element-"
"contents>`_: update the contents of the `<application>` element in the "
"generated Android manifest"
msgstr ""

#: ../../docs/tutorials/platform/android/android_plugin.rst:203
msgid ""
"`_get_android_manifest_element_contents <https://docs.godotengine.org/en/"
"latest/classes/class_editorexportplugin.html#class-editorexportplugin-method-"
"get-android-manifest-element-contents>`_: update the contents of the "
"`<manifest>` element in the generated Android manifest"
msgstr ""

#: ../../docs/tutorials/platform/android/android_plugin.rst:205
msgid ""
"The ``_get_android_manifest_*`` methods allow the plugin to automatically "
"provide changes to the app's manifest which are preserved when the Godot "
"Editor is updated, resolving a long standing issue with v1 Android plugins."
msgstr ""

#: ../../docs/tutorials/platform/android/android_plugin.rst:209
msgid ""
"Create a ``plugin.cfg``. This is an INI file with metadata about your "
"plugin::"
msgstr ""

#: ../../docs/tutorials/platform/android/android_plugin.rst:219
msgid ""
"For reference, here is the `folder structure for the Godot Android plugin "
"project template <https://github.com/m4gr3d/Godot-Android-Plugin-Template/"
"tree/main/plugin/export_scripts_template>`_. At build time, the contents of "
"the ``export_scripts_template`` directory as well as the generated plugin "
"binaries are copied to the ``addons/<plugin_name>`` directory:"
msgstr ""

#: ../../docs/tutorials/platform/android/android_plugin.rst:232
msgid "Packaging a v2 Android plugin with GDExtension capabilities"
msgstr ""

#: ../../docs/tutorials/platform/android/android_plugin.rst:234
msgid ""
"For GDExtension, we follow the same steps as for `Packaging a v2 Android "
"plugin`_ and add the `GDExtension config file <https://docs.godotengine.org/"
"en/stable/tutorials/scripting/gdextension/gdextension_cpp_example.html#using-"
"the-gdextension-module>`_ in the same location as ``plugin.cfg``."
msgstr ""

#: ../../docs/tutorials/platform/android/android_plugin.rst:237
msgid ""
"For reference, here is the `folder structure for the GDExtension Android "
"plugin project template <https://github.com/m4gr3d/GDExtension-Android-"
"Plugin-Template/tree/main/plugin/export_scripts_template>`_. At build time, "
"the contents of the ``export_scripts_template`` directory as well as the "
"generated plugin binaries are copied to the ``addons/<plugin_name>`` "
"directory:"
msgstr ""

#: ../../docs/tutorials/platform/android/android_plugin.rst:251
msgid "Here is what the ``plugin.gdextension`` config file should look like::"
msgstr ""

#: ../../docs/tutorials/platform/android/android_plugin.rst:266
msgid ""
"Of note is the ``android_aar_plugin`` field that specifies this GDExtension "
"module is provided as part of a v2 Android plugin. During the export "
"process, this will indicate to the Godot Editor that the GDExtension native "
"shared libraries are exported by the Android plugin AAR binaries."
msgstr ""

#: ../../docs/tutorials/platform/android/android_plugin.rst:269
msgid ""
"For GDExtension Android plugins, the plugin init class must override "
"`GodotPlugin::getPluginGDExtensionLibrariesPaths() <https://github.com/"
"godotengine/godot/blob/0a7f75ec7b465604b6496c8f5f1d638aed250d6d/platform/"
"android/java/lib/src/org/godotengine/godot/plugin/GodotPlugin.java#L277>`_, "
"and return the paths to the bundled GDExtension libraries config files (``*."
"gdextension``)."
msgstr ""

#: ../../docs/tutorials/platform/android/android_plugin.rst:272
msgid ""
"The paths must be relative to the Android library's ``assets`` directory. At "
"runtime, the plugin will provide these paths to the Godot engine which will "
"use them to load and initialize the bundled GDExtension libraries."
msgstr ""

#: ../../docs/tutorials/platform/android/android_plugin.rst:276
#, fuzzy
msgid "Using a v2 Android plugin"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/platform/android/android_plugin.rst:280
msgid "Godot 4.2 or higher is required"
msgstr ""

#: ../../docs/tutorials/platform/android/android_plugin.rst:282
msgid ""
"v2 Android plugin requires the use of the `Gradle build process <https://"
"docs.godotengine.org/en/stable/classes/class_editorexportplatformandroid."
"html#class-editorexportplatformandroid-property-gradle-build-use-gradle-"
"build>`_."
msgstr ""

#: ../../docs/tutorials/platform/android/android_plugin.rst:284
msgid ""
"The provided github project templates include demo Godot projects for quick "
"testing."
msgstr ""

#: ../../docs/tutorials/platform/android/android_plugin.rst:287
msgid ""
"Copy the plugin's output directory (``addons/<plugin_name>``) to the target "
"Godot project's directory"
msgstr ""

#: ../../docs/tutorials/platform/android/android_plugin.rst:289
msgid ""
"Open the project in the Godot Editor; the Editor should detect the plugin"
msgstr ""

#: ../../docs/tutorials/platform/android/android_plugin.rst:291
msgid ""
"Navigate to ``Project`` -> ``Project Settings...`` -> ``Plugins``, and "
"ensure the plugin is enabled"
msgstr ""

#: ../../docs/tutorials/platform/android/android_plugin.rst:293
msgid ""
"Install the Godot Android build template by clicking on ``Project`` -> "
"``Install Android Build Template...``"
msgstr ""

#: ../../docs/tutorials/platform/android/android_plugin.rst:295
msgid "Navigate to ``Project`` -> ``Export...``"
msgstr ""

#: ../../docs/tutorials/platform/android/android_plugin.rst:297
msgid "In the ``Export`` window, create an ``Android export preset``"
msgstr ""

#: ../../docs/tutorials/platform/android/android_plugin.rst:299
msgid ""
"In the ``Android export preset``, scroll to ``Gradle Build`` and set ``Use "
"Gradle Build`` to ``true``"
msgstr ""

#: ../../docs/tutorials/platform/android/android_plugin.rst:301
msgid ""
"Update the project's scripts as needed to access the plugin's functionality. "
"For example::"
msgstr ""

#: ../../docs/tutorials/platform/android/android_plugin.rst:307
msgid "Connect an Android device to your machine and run the project on it"
msgstr ""

#: ../../docs/tutorials/platform/android/android_plugin.rst:311
#, fuzzy
msgid "Using a v2 Android plugin as an Android library"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/platform/android/android_plugin.rst:313
msgid ""
"Since they are also Android libraries, Godot v2 Android plugins can be "
"stripped from their ``EditorExportPlugin`` packaging and provided as raw "
"``AAR`` binaries for use as libraries alongside the :ref:`Godot Android "
"library <doc_android_library>` by Android apps."
msgstr ""

#: ../../docs/tutorials/platform/android/android_plugin.rst:315
msgid ""
"If targeting this use-case, make sure to include additional instructions for "
"how the ``AAR`` binaries should be included (e.g: custom additions to the "
"Android app's manifest)."
msgstr ""

#: ../../docs/tutorials/platform/android/android_plugin.rst:318
msgid "Reference implementations"
msgstr ""

#: ../../docs/tutorials/platform/android/android_plugin.rst:320
#, fuzzy
msgid ""
"`Godot Android Plugins Samples <https://github.com/m4gr3d/Godot-Android-"
"Samples/tree/master/plugins>`_"
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati raznorazne `Godot demo projects "
"<https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/tutorials/platform/android/android_plugin.rst:321
#, fuzzy
msgid ""
"`Godot Android Plugin Template <https://github.com/m4gr3d/Godot-Android-"
"Plugin-Template>`_"
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati raznorazne `Godot demo projects "
"<https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/tutorials/platform/android/android_plugin.rst:322
msgid ""
"`GDExtension Android Plugin Template <https://github.com/m4gr3d/GDExtension-"
"Android-Plugin-Template>`_"
msgstr ""

#: ../../docs/tutorials/platform/android/android_plugin.rst:323
#, fuzzy
msgid ""
"`Godot OpenXR Loaders <https://github.com/GodotVR/godot_openxr_loaders>`_"
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati raznorazne `Godot demo projects "
"<https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/tutorials/platform/android/android_plugin.rst:327
#, fuzzy
msgid "Tips and Guidelines"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/platform/android/android_plugin.rst:330
msgid "Simplify access to the exposed Java / Kotlin APIs"
msgstr ""

#: ../../docs/tutorials/platform/android/android_plugin.rst:332
msgid ""
"To make it easier to access the exposed Java / Kotlin APIs in the Godot "
"Editor, it's recommended to provide one (or multiple) gdscript wrapper "
"class(es) for your plugin users to interface with."
msgstr ""

#: ../../docs/tutorials/platform/android/android_plugin.rst:335
#: ../../docs/tutorials/scripting/gdscript/gdscript_documentation_comments.rst:46
#: ../../docs/tutorials/scripting/gdscript/gdscript_documentation_comments.rst:97
#, fuzzy
msgid "For example::"
msgstr "Windows"

#: ../../docs/tutorials/platform/android/android_plugin.rst:358
msgid "Support using the GDExtension functionality in the Godot Editor"
msgstr ""

#: ../../docs/tutorials/platform/android/android_plugin.rst:360
msgid ""
"If planning to use the GDExtension functionality in the Godot Editor, it is "
"recommended that the GDExtension's native binaries are compiled not just for "
"Android, but also for the OS onto which developers / users intend to run the "
"Godot Editor. Not doing so may prevent developers / users from writing code "
"that accesses the plugin from within the Godot Editor."
msgstr ""

#: ../../docs/tutorials/platform/android/android_plugin.rst:365
msgid ""
"This may involve creating dummy plugins for the host OS just so the API is "
"published to the editor. You can use the [godot-cpp-template](https://github."
"com/godotengine/godot-cpp-template) github template for reference on how to "
"do so."
msgstr ""

#: ../../docs/tutorials/platform/android/android_plugin.rst:370
msgid "Godot crashes upon load"
msgstr ""

#: ../../docs/tutorials/platform/android/android_plugin.rst:372
msgid "Check ``adb logcat`` for possible problems, then:"
msgstr ""

#: ../../docs/tutorials/platform/android/android_plugin.rst:374
msgid ""
"Check that the methods exposed by the plugin used the following Java types: "
"``void``, ``boolean``, ``int``, ``float``, ``java.lang.String``, ``org."
"godotengine.godot.Dictionary``, ``int[]``, ``byte[]``, ``float[]``, ``java."
"lang.String[]``."
msgstr ""

#: ../../docs/tutorials/platform/android/android_plugin.rst:375
msgid "More complex datatypes are not supported for now."
msgstr ""

#: ../../docs/tutorials/platform/android/android_in_app_purchases.rst:4
msgid "Android in-app purchases"
msgstr ""

#: ../../docs/tutorials/platform/android/android_in_app_purchases.rst:6
msgid ""
"Godot offers a first-party ``GodotGooglePlayBilling`` Android plugin "
"compatible with Godot 4 which uses the `Google Play Billing library <https://"
"developer.android.com/google/play/billing>`_."
msgstr ""

#: ../../docs/tutorials/platform/android/android_in_app_purchases.rst:10
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0001.rst:8
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0002.rst:8
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0101.rst:8
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0102.rst:8
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0103.rst:8
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0104.rst:8
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0105.rst:8
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0106.rst:8
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0107.rst:8
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0201.rst:8
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0202.rst:8
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0203.rst:8
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0301.rst:8
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0302.rst:8
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0303.rst:8
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0401.rst:8
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0402.rst:8
msgid "Usage"
msgstr ""

#: ../../docs/tutorials/platform/android/android_in_app_purchases.rst:15
msgid ""
"Make sure you have enabled and successfully set up :ref:`Android Gradle "
"Builds <doc_android_gradle_build>`. Follow the compiling instructions on the "
"``GodotGooglePlayBilling`` `github page <https://github.com/godotengine/"
"godot-google-play-billing>`__."
msgstr ""

#: ../../docs/tutorials/platform/android/android_in_app_purchases.rst:18
msgid ""
"Then put the files `./godot-google-play-billing/build/outputs/aar/"
"GodotGooglePlayBilling.***.release.aar` and `./GodotGooglePlayBilling.gdap` "
"into your project in the `res://android/plugins` folder."
msgstr ""

#: ../../docs/tutorials/platform/android/android_in_app_purchases.rst:20
msgid ""
"The plugin should now show up in the Android export settings, where you can "
"enable it."
msgstr ""

#: ../../docs/tutorials/platform/android/android_in_app_purchases.rst:24
#, fuzzy
msgid "Initialize the plugin"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/platform/android/android_in_app_purchases.rst:26
msgid "To use the ``GodotGooglePlayBilling`` API:"
msgstr ""

#: ../../docs/tutorials/platform/android/android_in_app_purchases.rst:28
msgid "Obtain a reference to the ``GodotGooglePlayBilling`` singleton"
msgstr ""

#: ../../docs/tutorials/platform/android/android_in_app_purchases.rst:29
msgid "Connect handlers for the plugin signals"
msgstr ""

#: ../../docs/tutorials/platform/android/android_in_app_purchases.rst:30
msgid "Call ``startConnection``"
msgstr ""

#: ../../docs/tutorials/platform/android/android_in_app_purchases.rst:32
msgid "Initialization example:"
msgstr ""

#: ../../docs/tutorials/platform/android/android_in_app_purchases.rst:63
msgid ""
"The API must be in a connected state prior to use. The ``connected`` signal "
"is sent when the connection process succeeds. You can also use ``isReady()`` "
"to determine if the plugin is ready for use. The ``getConnectionState()`` "
"function returns the current connection state of the plugin."
msgstr ""

#: ../../docs/tutorials/platform/android/android_in_app_purchases.rst:68
msgid "Return values for ``getConnectionState()``:"
msgstr ""

#: ../../docs/tutorials/platform/android/android_in_app_purchases.rst:82
#, fuzzy
msgid "Query available items"
msgstr "Ne postoje ograničenja prilikom korištenja Godot-a"

#: ../../docs/tutorials/platform/android/android_in_app_purchases.rst:84
msgid ""
"Once the API has connected, query SKUs using ``querySkuDetails()``. You must "
"successfully complete a SKU query before calling the ``purchase()`` or "
"``queryPurchases()`` functions, or they will return an error. "
"``querySkuDetails()`` takes two parameters: an array of SKU name strings, "
"and a string specifying the type of SKU being queried. The SKU type string "
"should be ``\"inapp\"`` for normal in-app purchases or ``\"subs\"`` for "
"subscriptions. The name strings in the array should match the SKU product "
"ids defined in the Google Play Console entry for your app."
msgstr ""

#: ../../docs/tutorials/platform/android/android_in_app_purchases.rst:92
msgid "Example use of ``querySkuDetails()``:"
msgstr ""

#: ../../docs/tutorials/platform/android/android_in_app_purchases.rst:109
msgid "Query user purchases"
msgstr ""

#: ../../docs/tutorials/platform/android/android_in_app_purchases.rst:111
msgid ""
"To retrieve a user's purchases, call the ``queryPurchases()`` function "
"passing a string with the type of SKU to query. The SKU type string should "
"be ``\"inapp\"`` for normal in-app purchases or ``\"subs\"`` for "
"subscriptions. The ``query_purchases_response`` signal is sent with the "
"result. The signal has a single parameter: a :ref:`Dictionary "
"<class_Dictionary>` with a status code and either an array of purchases or "
"an error message. Only active subscriptions and non-consumed one-time "
"purchases are included in the purchase array."
msgstr ""

#: ../../docs/tutorials/platform/android/android_in_app_purchases.rst:120
msgid "Example use of ``queryPurchases()``:"
msgstr ""

#: ../../docs/tutorials/platform/android/android_in_app_purchases.rst:137
msgid ""
"You should query purchases during startup after successfully retrieving SKU "
"details. Since the user may make a purchase or resolve a pending transaction "
"from outside your app, you should recheck for purchases when resuming from "
"the background. To accomplish this, you can use the ``billing_resume`` "
"signal."
msgstr ""

#: ../../docs/tutorials/platform/android/android_in_app_purchases.rst:142
msgid "Example use of ``billing_resume``:"
msgstr ""

#: ../../docs/tutorials/platform/android/android_in_app_purchases.rst:151
msgid ""
"For more information on processing the purchase items returned by "
"``queryPurchases()``, see `Processing a purchase item`_"
msgstr ""

#: ../../docs/tutorials/platform/android/android_in_app_purchases.rst:156
msgid "Purchase an item"
msgstr ""

#: ../../docs/tutorials/platform/android/android_in_app_purchases.rst:158
msgid ""
"To initiate the purchase flow for an item, call ``purchase()`` passing the "
"product id string of the SKU you wish to purchase. Reminder: you **must** "
"query the SKU details for an item before you can pass it to ``purchase()``."
msgstr ""

#: ../../docs/tutorials/platform/android/android_in_app_purchases.rst:163
msgid "Example use of ``purchase()``:"
msgstr ""

#: ../../docs/tutorials/platform/android/android_in_app_purchases.rst:170
msgid ""
"The payment flow will send a ``purchases_updated`` signal on success or a "
"``purchase_error`` signal on failure."
msgstr ""

#: ../../docs/tutorials/platform/android/android_in_app_purchases.rst:184
#, fuzzy
msgid "Processing a purchase item"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/platform/android/android_in_app_purchases.rst:186
msgid ""
"The ``query_purchases_response`` and ``purchases_updated`` signals provide "
"an array of purchases in :ref:`Dictionary <class_Dictionary>` format. The "
"purchase Dictionary includes keys that map to values of the Google Play "
"Billing `Purchase <https://developer.android.com/reference/com/android/"
"billingclient/api/Purchase>`_ class."
msgstr ""

#: ../../docs/tutorials/platform/android/android_in_app_purchases.rst:191
msgid "Purchase fields:"
msgstr ""

#: ../../docs/tutorials/platform/android/android_in_app_purchases.rst:213
msgid "Check purchase state"
msgstr ""

#: ../../docs/tutorials/platform/android/android_in_app_purchases.rst:215
msgid ""
"Check the ``purchase_state`` value of a purchase to determine if a purchase "
"was completed or is still pending."
msgstr ""

#: ../../docs/tutorials/platform/android/android_in_app_purchases.rst:218
msgid "PurchaseState values:"
msgstr ""

#: ../../docs/tutorials/platform/android/android_in_app_purchases.rst:230
msgid ""
"If a purchase is in a ``PENDING`` state, you should not award the contents "
"of the purchase or do any further processing of the purchase until it "
"reaches the ``PURCHASED`` state. If you have a store interface, you may wish "
"to display information about pending purchases needing to be completed in "
"the Google Play Store. For more details on pending purchases, see `Handling "
"pending transactions <https://developer.android.com/google/play/billing/"
"integrate#pending>`_ in the Google Play Billing Library documentation."
msgstr ""

#: ../../docs/tutorials/platform/android/android_in_app_purchases.rst:240
msgid "Consumables"
msgstr ""

#: ../../docs/tutorials/platform/android/android_in_app_purchases.rst:242
msgid ""
"If your in-app item is not a one-time purchase but a consumable item (e.g. "
"coins) which can be purchased multiple times, you can consume an item by "
"calling ``consumePurchase()`` passing the ``purchase_token`` value from the "
"purchase dictionary. Calling ``consumePurchase()`` automatically "
"acknowledges a purchase. Consuming a product allows the user to purchase it "
"again, it will no longer appear in subsequent ``queryPurchases()`` calls "
"unless it is repurchased."
msgstr ""

#: ../../docs/tutorials/platform/android/android_in_app_purchases.rst:249
msgid "Example use of ``consumePurchase()``:"
msgstr ""

#: ../../docs/tutorials/platform/android/android_in_app_purchases.rst:274
msgid "Acknowledging purchases"
msgstr ""

#: ../../docs/tutorials/platform/android/android_in_app_purchases.rst:276
msgid ""
"If your in-app item is a one-time purchase, you must acknowledge the "
"purchase by calling the ``acknowledgePurchase()`` function, passing the "
"``purchase_token`` value from the purchase dictionary. If you do not "
"acknowledge a purchase within three days, the user automatically receives a "
"refund, and Google Play revokes the purchase. If you are calling "
"``comsumePurchase()`` it automatically acknowledges the purchase and you do "
"not need to call ``acknowledgePurchase()``."
msgstr ""

#: ../../docs/tutorials/platform/android/android_in_app_purchases.rst:283
msgid "Example use of ``acknowledgePurchase()``:"
msgstr ""

#: ../../docs/tutorials/platform/android/android_in_app_purchases.rst:310
#, fuzzy
msgid "Subscriptions"
msgstr "Uvod"

#: ../../docs/tutorials/platform/android/android_in_app_purchases.rst:312
msgid ""
"Subscriptions work mostly like regular in-app items. Use ``\"subs\"`` as the "
"second argument to ``querySkuDetails()`` to get subscription details. Pass "
"``\"subs\"`` to ``queryPurchases()`` to get subscription purchase details."
msgstr ""

#: ../../docs/tutorials/platform/android/android_in_app_purchases.rst:316
msgid ""
"You can check ``is_auto_renewing`` in the a subscription purchase returned "
"from ``queryPurchases()`` to see if a user has cancelled an auto-renewing "
"subscription."
msgstr ""

#: ../../docs/tutorials/platform/android/android_in_app_purchases.rst:320
msgid ""
"You need to acknowledge new subscription purchases, but not automatic "
"subscription renewals."
msgstr ""

#: ../../docs/tutorials/platform/android/android_in_app_purchases.rst:323
msgid ""
"If you support upgrading or downgrading between different subscription "
"levels, you should use ``updateSubscription()`` to use the subscription "
"update flow to change an active subscription. Like ``purchase()``, results "
"are returned by the ``purchases_updated`` and ``purchase_error`` signals. "
"There are three parameters to ``updateSubscription()``:"
msgstr ""

#: ../../docs/tutorials/platform/android/android_in_app_purchases.rst:329
msgid "The purchase token of the currently active subscription"
msgstr ""

#: ../../docs/tutorials/platform/android/android_in_app_purchases.rst:330
msgid "The product id string of the subscription SKU to change to"
msgstr ""

#: ../../docs/tutorials/platform/android/android_in_app_purchases.rst:331
msgid "The proration mode to apply to the subscription."
msgstr ""

#: ../../docs/tutorials/platform/android/android_in_app_purchases.rst:333
msgid "The proration values are defined as:"
msgstr ""

#: ../../docs/tutorials/platform/android/android_in_app_purchases.rst:358
msgid "Default behavior is ``IMMEDIATE_WITH_TIME_PRORATION``."
msgstr ""

#: ../../docs/tutorials/platform/android/android_in_app_purchases.rst:360
msgid "Example use of ``updateSubscription``:"
msgstr ""

#: ../../docs/tutorials/platform/android/android_in_app_purchases.rst:368
msgid ""
"The ``confirmPriceChange()`` function can be used to launch price change "
"confirmation flow for a subscription. Pass the product id of the "
"subscription SKU subject to the price change. The result will be sent by the "
"``price_change_acknowledged`` signal."
msgstr ""

#: ../../docs/tutorials/platform/android/android_in_app_purchases.rst:372
msgid "Example use of ``confirmPriceChange()``:"
msgstr ""

#: ../../docs/tutorials/platform/ios/index.rst:4
#, fuzzy
msgid "iOS plugins"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/platform/ios/ios_plugin.rst:6
#, fuzzy
msgid "Creating iOS plugins"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/platform/ios/ios_plugin.rst:8
msgid ""
"This page explains what iOS plugins can do for you, how to use an existing "
"plugin, and the steps to code a new one."
msgstr ""

#: ../../docs/tutorials/platform/ios/ios_plugin.rst:10
msgid ""
"iOS plugins allow you to use third-party libraries and support iOS-specific "
"features like In-App Purchases, GameCenter integration, ARKit support, and "
"more."
msgstr ""

#: ../../docs/tutorials/platform/ios/ios_plugin.rst:13
#, fuzzy
msgid "Loading and using an existing plugin"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/platform/ios/ios_plugin.rst:15
msgid ""
"An iOS plugin requires a ``.gdip`` configuration file, a binary file which "
"can be either ``.a`` static library or ``.xcframework`` containing ``.a`` "
"static libraries, and possibly other dependencies. To use it, you need to:"
msgstr ""

#: ../../docs/tutorials/platform/ios/ios_plugin.rst:17
msgid ""
"Copy the plugin's files to your Godot project's ``res://ios/plugins`` "
"directory. You can also group files in a sub-directory, like ``res://ios/"
"plugins/my_plugin``."
msgstr ""

#: ../../docs/tutorials/platform/ios/ios_plugin.rst:19
msgid ""
"The Godot editor automatically detects and imports ``.gdip`` files inside "
"``res://ios/plugins`` and its subdirectories."
msgstr ""

#: ../../docs/tutorials/platform/ios/ios_plugin.rst:21
msgid ""
"You can find and activate detected plugins by going to Project -> Export... -"
"> iOS and in the Options tab, scrolling to the Plugins section."
msgstr ""

#: ../../docs/tutorials/platform/ios/ios_plugin.rst:25
msgid ""
"When a plugin is active, you can access it in your using ``Engine."
"get_singleton()``::"
msgstr ""

#: ../../docs/tutorials/platform/ios/ios_plugin.rst:33
msgid ""
"The plugin's files have to be in the ``res://ios/plugins/`` directory or a "
"subdirectory, otherwise the Godot editor will not automatically detect them."
msgstr ""

#: ../../docs/tutorials/platform/ios/ios_plugin.rst:36
#, fuzzy
msgid "Creating an iOS plugin"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/platform/ios/ios_plugin.rst:38
msgid ""
"At its core, a Godot iOS plugin is an iOS library (*.a* archive file or *."
"xcframework* containing static libraries) with the following requirements:"
msgstr ""

#: ../../docs/tutorials/platform/ios/ios_plugin.rst:40
msgid "The library must have a dependency on the Godot engine headers."
msgstr ""

#: ../../docs/tutorials/platform/ios/ios_plugin.rst:42
msgid "The library must come with a ``.gdip`` configuration file."
msgstr ""

#: ../../docs/tutorials/platform/ios/ios_plugin.rst:44
msgid ""
"An iOS plugin can have the same functionality as a Godot module but provides "
"more flexibility and doesn't require to rebuild the engine."
msgstr ""

#: ../../docs/tutorials/platform/ios/ios_plugin.rst:46
msgid ""
"Here are the steps to get a plugin's development started. We recommend using "
"`Xcode <https://developer.apple.com/develop/>`_ as your development "
"environment."
msgstr ""

#: ../../docs/tutorials/platform/ios/ios_plugin.rst:48
#, fuzzy
msgid ""
"The `Godot iOS Plugins <https://github.com/godotengine/godot-ios-plugins>`_."
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati raznorazne `Godot demo projects "
"<https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/tutorials/platform/ios/ios_plugin.rst:50
msgid ""
"The `Godot iOS plugin template <https://github.com/naithar/"
"godot_ios_plugin>`_ gives you all the boilerplate you need to get your iOS "
"plugin started."
msgstr ""

#: ../../docs/tutorials/platform/ios/ios_plugin.rst:53
#, fuzzy
msgid "To build an iOS plugin:"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/platform/ios/ios_plugin.rst:55
msgid "Create an Objective-C static library for your plugin inside Xcode."
msgstr ""

#: ../../docs/tutorials/platform/ios/ios_plugin.rst:57
msgid ""
"Add the Godot engine header files as a dependency for your plugin library in "
"``HEADER_SEARCH_PATHS``. You can find the setting inside the ``Build "
"Settings`` tab:"
msgstr ""

#: ../../docs/tutorials/platform/ios/ios_plugin.rst:59
#, fuzzy
msgid ""
"Download the Godot engine source from the `Godot GitHub page <https://github."
"com/godotengine/godot>`_."
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati raznorazne `Godot demo projects "
"<https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/tutorials/platform/ios/ios_plugin.rst:61
msgid ""
"Run SCons to generate headers. You can learn the process by reading :ref:"
"`doc_compiling_for_ios`. You don't have to wait for compilation to complete "
"to move forward as headers are generated before the engine starts to compile."
msgstr ""

#: ../../docs/tutorials/platform/ios/ios_plugin.rst:63
msgid ""
"You should use the same header files for iOS plugins and for the iOS export "
"template."
msgstr ""

#: ../../docs/tutorials/platform/ios/ios_plugin.rst:65
msgid ""
"In the ``Build Settings`` tab, specify the compilation flags for your static "
"library in ``OTHER_CFLAGS``. The most important ones are ``-fcxx-modules``, "
"``-fmodules``, and ``-DDEBUG`` if you need debug support. Other flags should "
"be the same you use to compile Godot. For instance:"
msgstr ""

#: ../../docs/tutorials/platform/ios/ios_plugin.rst:71
msgid ""
"Add the required logic for your plugin and build your library to generate a "
"``.a`` file. You will probably need to build both ``debug`` and ``release`` "
"target ``.a`` files. Depending on your needs, pick either or both. If you "
"need both debug and release ``.a`` files, their name should match following "
"pattern: ``[PluginName].[TargetType].a``. You can also build the static "
"library with your SCons configuration."
msgstr ""

#: ../../docs/tutorials/platform/ios/ios_plugin.rst:73
msgid ""
"The iOS plugin system also supports ``.xcframework`` files. To generate one, "
"you can use a command such as:"
msgstr ""

#: ../../docs/tutorials/platform/ios/ios_plugin.rst:79
msgid ""
"Create a Godot iOS Plugin configuration file to help the system detect and "
"load your plugin:"
msgstr ""

#: ../../docs/tutorials/platform/ios/ios_plugin.rst:81
msgid ""
"The configuration file extension must be ``gdip`` (e.g.: ``MyPlugin.gdip``)."
msgstr ""

#: ../../docs/tutorials/platform/ios/ios_plugin.rst:83
msgid "The configuration file format is as follow::"
msgstr ""

#: ../../docs/tutorials/platform/ios/ios_plugin.rst:115
msgid "The ``config`` section and fields are required and defined as follow:"
msgstr ""

#: ../../docs/tutorials/platform/ios/ios_plugin.rst:117
msgid "**name**: name of the plugin"
msgstr ""

#: ../../docs/tutorials/platform/ios/ios_plugin.rst:119
msgid ""
"**binary**: this should be the filepath of the plugin library (``a`` or "
"``xcframework``) file."
msgstr ""

#: ../../docs/tutorials/platform/ios/ios_plugin.rst:121
msgid ""
"The filepath can be relative (e.g.: ``MyPlugin.a``, ``MyPlugin."
"xcframework``) in which case it's relative to the directory where the "
"``gdip`` file is located."
msgstr ""

#: ../../docs/tutorials/platform/ios/ios_plugin.rst:122
msgid ""
"The filepath can be absolute: ``res://some_path/MyPlugin.a`` or ``res://"
"some_path/MyPlugin.xcframework``."
msgstr ""

#: ../../docs/tutorials/platform/ios/ios_plugin.rst:123
msgid ""
"In case you need multitarget library usage, the filename should be "
"``MyPlugin.a`` and ``.a`` files should be named as ``MyPlugin.release.a`` "
"and ``MyPlugin.debug.a``."
msgstr ""

#: ../../docs/tutorials/platform/ios/ios_plugin.rst:124
msgid ""
"In case you use multitarget ``xcframework`` libraries, their filename in the "
"configuration should be ``MyPlugin.xcframework``. The ``.xcframework`` files "
"should be named as ``MyPlugin.release.xcframework`` and ``MyPlugin.debug."
"xcframework``."
msgstr ""

#: ../../docs/tutorials/platform/ios/ios_plugin.rst:126
msgid ""
"The ``dependencies`` and ``plist`` sections are optional and defined as "
"follow:"
msgstr ""

#: ../../docs/tutorials/platform/ios/ios_plugin.rst:128
msgid "**dependencies**:"
msgstr ""

#: ../../docs/tutorials/platform/ios/ios_plugin.rst:130
msgid ""
"**linked**: contains a list of iOS frameworks that the iOS application "
"should be linked with."
msgstr ""

#: ../../docs/tutorials/platform/ios/ios_plugin.rst:132
msgid ""
"**embedded**: contains a list of iOS frameworks or libraries that should be "
"both linked and embedded into the resulting iOS application."
msgstr ""

#: ../../docs/tutorials/platform/ios/ios_plugin.rst:134
msgid ""
"**system**: contains a list of iOS system frameworks that are required for "
"plugin."
msgstr ""

#: ../../docs/tutorials/platform/ios/ios_plugin.rst:136
msgid ""
"**capabilities**: contains a list of iOS capabilities that is required for "
"plugin. A list of available capabilities can be found at `Apple "
"UIRequiredDeviceCapabilities documentation page <https://developer.apple.com/"
"documentation/bundleresources/information_property_list/"
"uirequireddevicecapabilities>`_."
msgstr ""

#: ../../docs/tutorials/platform/ios/ios_plugin.rst:138
msgid ""
"**files**: contains a list of files that should be copied on export. This is "
"useful for data files or images."
msgstr ""

#: ../../docs/tutorials/platform/ios/ios_plugin.rst:140
msgid ""
"**linker_flags**: contains a list of linker flags to add to the Xcode "
"project when exporting the plugin."
msgstr ""

#: ../../docs/tutorials/platform/ios/ios_plugin.rst:142
msgid ""
"**plist**: should have keys and values that should be present in ``Info."
"plist`` file."
msgstr ""

#: ../../docs/tutorials/platform/ios/ios_plugin.rst:144
msgid "Each line should follow pattern: ``KeyName:KeyType=KeyValue``"
msgstr ""

#: ../../docs/tutorials/platform/ios/ios_plugin.rst:145
msgid ""
"Supported values for ``KeyType`` are ``string``, ``integer``, ``boolean``, "
"``raw``, ``string_input``"
msgstr ""

#: ../../docs/tutorials/platform/ios/ios_plugin.rst:146
msgid ""
"If no type is used (e.g.: ``KeyName=\"KeyValue\"``) ``string`` type will be "
"used."
msgstr ""

#: ../../docs/tutorials/platform/ios/ios_plugin.rst:147
msgid ""
"If ``raw`` type is used value for corresponding key will be stored in ``Info."
"plist`` as is."
msgstr ""

#: ../../docs/tutorials/platform/ios/ios_plugin.rst:148
msgid ""
"If ``string_input`` type is used you will be able to modify value in Export "
"window."
msgstr ""

#: ../../docs/tutorials/platform/ios/plugins_for_ios.rst:8
msgid ""
"Godot provides StoreKit, GameCenter, iCloud services and other plugins. They "
"are using same model of asynchronous calls explained below."
msgstr ""

#: ../../docs/tutorials/platform/ios/plugins_for_ios.rst:11
msgid "ARKit and Camera access are also provided as plugins."
msgstr ""

#: ../../docs/tutorials/platform/ios/plugins_for_ios.rst:13
#, fuzzy
msgid ""
"Latest updates, documentation and source code can be found at `Godot iOS "
"plugins repository <https://github.com/godotengine/godot-ios-plugins>`_"
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati raznorazne `Godot demo projects "
"<https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/tutorials/platform/ios/plugins_for_ios.rst:16
msgid "Accessing plugin singletons"
msgstr ""

#: ../../docs/tutorials/platform/ios/plugins_for_ios.rst:18
msgid ""
"To access plugin functionality, you first need to check that the plugin is "
"exported and available by calling the `Engine.has_singleton()` function, "
"which returns a registered singleton."
msgstr ""

#: ../../docs/tutorials/platform/ios/plugins_for_ios.rst:22
msgid "Here's an example of how to do this in GDScript:"
msgstr ""

#: ../../docs/tutorials/platform/ios/plugins_for_ios.rst:42
msgid "Asynchronous methods"
msgstr ""

#: ../../docs/tutorials/platform/ios/plugins_for_ios.rst:44
msgid ""
"When requesting an asynchronous operation, the method will look like this:"
msgstr ""

#: ../../docs/tutorials/platform/ios/plugins_for_ios.rst:51
msgid ""
"The parameter will usually be a Dictionary, with the information necessary "
"to make the request, and the call will have two phases. First, the method "
"will immediately return an Error value. If the Error is not 'OK', the call "
"operation is completed, with an error probably caused locally (no internet "
"connection, API incorrectly configured, etc). If the error value is 'OK', a "
"response event will be produced and added to the 'pending events' queue. "
"Example:"
msgstr ""

#: ../../docs/tutorials/platform/ios/plugins_for_ios.rst:78
msgid ""
"Remember that when a call returns OK, the API will *always* produce an event "
"through the pending_event interface, even if it's an error, or a network "
"timeout, etc. You should be able to, for example, safely block the interface "
"waiting for a reply from the server. If any of the APIs don't behave this "
"way it should be treated as a bug."
msgstr ""

#: ../../docs/tutorials/platform/ios/plugins_for_ios.rst:84
msgid "The pending event interface consists of two methods:"
msgstr ""

#: ../../docs/tutorials/platform/ios/plugins_for_ios.rst:86
msgid ""
"``get_pending_event_count()`` Returns the number of pending events on the "
"queue."
msgstr ""

#: ../../docs/tutorials/platform/ios/plugins_for_ios.rst:89
msgid ""
"``Variant pop_pending_event()`` Pops the first event from the queue and "
"returns it."
msgstr ""

#: ../../docs/tutorials/platform/ios/plugins_for_ios.rst:93
msgid "Store Kit"
msgstr ""

#: ../../docs/tutorials/platform/ios/plugins_for_ios.rst:95
msgid ""
"Implemented in `Godot iOS InAppStore plugin <https://github.com/godotengine/"
"godot-ios-plugins/blob/master/plugins/inappstore/in_app_store.mm>`_."
msgstr ""

#: ../../docs/tutorials/platform/ios/plugins_for_ios.rst:97
msgid ""
"The Store Kit API is accessible through the ``InAppStore`` singleton. It is "
"initialized automatically."
msgstr ""

#: ../../docs/tutorials/platform/ios/plugins_for_ios.rst:100
msgid "The following methods are available and documented below:"
msgstr ""

#: ../../docs/tutorials/platform/ios/plugins_for_ios.rst:118
msgid "``purchase``"
msgstr ""

#: ../../docs/tutorials/platform/ios/plugins_for_ios.rst:120
msgid ""
"Purchases a product ID through the Store Kit API. You have to call "
"``finish_transaction(product_id)`` once you receive a successful response or "
"call ``set_auto_finish_transaction(true)`` prior to calling ``purchase()``. "
"These two methods ensure the transaction is completed."
msgstr ""

#: ../../docs/tutorials/platform/ios/plugins_for_ios.rst:127
msgid ""
"Takes a dictionary as a parameter, with one field, ``product_id``, a string "
"with your product ID. Example:"
msgstr ""

#: ../../docs/tutorials/platform/ios/plugins_for_ios.rst:135
#: ../../docs/tutorials/platform/ios/plugins_for_ios.rst:175
#: ../../docs/tutorials/platform/ios/plugins_for_ios.rst:199
#: ../../docs/tutorials/platform/ios/plugins_for_ios.rst:277
#: ../../docs/tutorials/platform/ios/plugins_for_ios.rst:322
#: ../../docs/tutorials/platform/ios/plugins_for_ios.rst:369
#: ../../docs/tutorials/platform/ios/plugins_for_ios.rst:398
#: ../../docs/tutorials/platform/ios/plugins_for_ios.rst:428
#: ../../docs/tutorials/platform/ios/plugins_for_ios.rst:460
#: ../../docs/tutorials/platform/ios/plugins_for_ios.rst:517
msgid "Response event"
msgstr ""

#: ../../docs/tutorials/platform/ios/plugins_for_ios.rst:137
#: ../../docs/tutorials/platform/ios/plugins_for_ios.rst:177
#: ../../docs/tutorials/platform/ios/plugins_for_ios.rst:279
#: ../../docs/tutorials/platform/ios/plugins_for_ios.rst:324
#: ../../docs/tutorials/platform/ios/plugins_for_ios.rst:371
#: ../../docs/tutorials/platform/ios/plugins_for_ios.rst:400
#: ../../docs/tutorials/platform/ios/plugins_for_ios.rst:430
#: ../../docs/tutorials/platform/ios/plugins_for_ios.rst:462
#: ../../docs/tutorials/platform/ios/plugins_for_ios.rst:519
msgid "The response event will be a dictionary with the following fields:"
msgstr ""

#: ../../docs/tutorials/platform/ios/plugins_for_ios.rst:139
#: ../../docs/tutorials/platform/ios/plugins_for_ios.rst:281
#: ../../docs/tutorials/platform/ios/plugins_for_ios.rst:326
#: ../../docs/tutorials/platform/ios/plugins_for_ios.rst:373
#: ../../docs/tutorials/platform/ios/plugins_for_ios.rst:402
#: ../../docs/tutorials/platform/ios/plugins_for_ios.rst:432
#: ../../docs/tutorials/platform/ios/plugins_for_ios.rst:464
msgid "On error:"
msgstr ""

#: ../../docs/tutorials/platform/ios/plugins_for_ios.rst:149
#: ../../docs/tutorials/platform/ios/plugins_for_ios.rst:292
#: ../../docs/tutorials/platform/ios/plugins_for_ios.rst:337
#: ../../docs/tutorials/platform/ios/plugins_for_ios.rst:383
#: ../../docs/tutorials/platform/ios/plugins_for_ios.rst:412
#: ../../docs/tutorials/platform/ios/plugins_for_ios.rst:442
#: ../../docs/tutorials/platform/ios/plugins_for_ios.rst:474
msgid "On success:"
msgstr ""

#: ../../docs/tutorials/platform/ios/plugins_for_ios.rst:160
msgid "``request_product_info``"
msgstr ""

#: ../../docs/tutorials/platform/ios/plugins_for_ios.rst:162
msgid "Requests the product info on a list of product IDs."
msgstr ""

#: ../../docs/tutorials/platform/ios/plugins_for_ios.rst:167
msgid ""
"Takes a dictionary as a parameter, with a single ``product_ids`` key to "
"which a string array of product IDs is assigned. Example:"
msgstr ""

#: ../../docs/tutorials/platform/ios/plugins_for_ios.rst:193
msgid "``restore_purchases``"
msgstr ""

#: ../../docs/tutorials/platform/ios/plugins_for_ios.rst:195
msgid ""
"Restores previously made purchases on user's account. This will create "
"response events for each previously purchased product ID."
msgstr ""

#: ../../docs/tutorials/platform/ios/plugins_for_ios.rst:201
msgid "The response events will be dictionaries with the following fields:"
msgstr ""

#: ../../docs/tutorials/platform/ios/plugins_for_ios.rst:212
msgid "``set_auto_finish_transaction``"
msgstr ""

#: ../../docs/tutorials/platform/ios/plugins_for_ios.rst:214
msgid ""
"If set to ``true``, once a purchase is successful, your purchase will be "
"finalized automatically. Call this method prior to calling ``purchase()``."
msgstr ""

#: ../../docs/tutorials/platform/ios/plugins_for_ios.rst:220
msgid ""
"Takes a boolean as a parameter which specifies if purchases should be "
"automatically finalized. Example:"
msgstr ""

#: ../../docs/tutorials/platform/ios/plugins_for_ios.rst:228
msgid "``finish_transaction``"
msgstr ""

#: ../../docs/tutorials/platform/ios/plugins_for_ios.rst:230
msgid ""
"If you don't want transactions to be automatically finalized, call this "
"method after you receive a successful purchase response."
msgstr ""

#: ../../docs/tutorials/platform/ios/plugins_for_ios.rst:237
msgid ""
"Takes a string ``product_id`` as an argument. ``product_id`` specifies what "
"product to finalize the purchase on. Example:"
msgstr ""

#: ../../docs/tutorials/platform/ios/plugins_for_ios.rst:245
msgid "Game Center"
msgstr ""

#: ../../docs/tutorials/platform/ios/plugins_for_ios.rst:247
msgid ""
"Implemented in `Godot iOS GameCenter plugin <https://github.com/godotengine/"
"godot-ios-plugins/blob/master/plugins/gamecenter/game_center.mm>`_."
msgstr ""

#: ../../docs/tutorials/platform/ios/plugins_for_ios.rst:249
msgid ""
"The Game Center API is available through the ``GameCenter`` singleton. It "
"has the following methods:"
msgstr ""

#: ../../docs/tutorials/platform/ios/plugins_for_ios.rst:264
msgid "and the pending events interface:"
msgstr ""

#: ../../docs/tutorials/platform/ios/plugins_for_ios.rst:272
msgid "``authenticate``"
msgstr ""

#: ../../docs/tutorials/platform/ios/plugins_for_ios.rst:274
msgid "Authenticates a user in Game Center."
msgstr ""

#: ../../docs/tutorials/platform/ios/plugins_for_ios.rst:303
msgid "``post_score``"
msgstr ""

#: ../../docs/tutorials/platform/ios/plugins_for_ios.rst:305
msgid "Posts a score to a Game Center leaderboard."
msgstr ""

#: ../../docs/tutorials/platform/ios/plugins_for_ios.rst:310
msgid "Takes a dictionary as a parameter, with two fields:"
msgstr ""

#: ../../docs/tutorials/platform/ios/plugins_for_ios.rst:312
msgid "``score`` a float number"
msgstr ""

#: ../../docs/tutorials/platform/ios/plugins_for_ios.rst:313
msgid "``category`` a string with the category name"
msgstr ""

#: ../../docs/tutorials/platform/ios/plugins_for_ios.rst:315
#: ../../docs/tutorials/platform/ios/plugins_for_ios.rst:362
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:89
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:270
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:335
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:346
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:359
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:853
#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:95
#: ../../docs/contributing/development/code_style_guidelines.rst:159
msgid "Example:"
msgstr ""

#: ../../docs/tutorials/platform/ios/plugins_for_ios.rst:347
msgid "``award_achievement``"
msgstr ""

#: ../../docs/tutorials/platform/ios/plugins_for_ios.rst:349
msgid "Modifies the progress of a Game Center achievement."
msgstr ""

#: ../../docs/tutorials/platform/ios/plugins_for_ios.rst:354
msgid "Takes a Dictionary as a parameter, with 3 fields:"
msgstr ""

#: ../../docs/tutorials/platform/ios/plugins_for_ios.rst:356
msgid "``name`` (string) the achievement name"
msgstr ""

#: ../../docs/tutorials/platform/ios/plugins_for_ios.rst:357
msgid ""
"``progress`` (float) the achievement progress from 0.0 to 100.0 (passed to "
"``GKAchievement::percentComplete``)"
msgstr ""

#: ../../docs/tutorials/platform/ios/plugins_for_ios.rst:359
msgid ""
"``show_completion_banner`` (bool) whether Game Center should display an "
"achievement banner at the top of the screen"
msgstr ""

#: ../../docs/tutorials/platform/ios/plugins_for_ios.rst:393
msgid "``reset_achievements``"
msgstr ""

#: ../../docs/tutorials/platform/ios/plugins_for_ios.rst:395
msgid "Clears all Game Center achievements. The function takes no parameters."
msgstr ""

#: ../../docs/tutorials/platform/ios/plugins_for_ios.rst:422
msgid "``request_achievements``"
msgstr ""

#: ../../docs/tutorials/platform/ios/plugins_for_ios.rst:424
msgid ""
"Request all the Game Center achievements the player has made progress on. "
"The function takes no parameters."
msgstr ""

#: ../../docs/tutorials/platform/ios/plugins_for_ios.rst:454
msgid "``request_achievement_descriptions``"
msgstr ""

#: ../../docs/tutorials/platform/ios/plugins_for_ios.rst:456
msgid ""
"Request the descriptions of all existing Game Center achievements regardless "
"of progress. The function takes no parameters."
msgstr ""

#: ../../docs/tutorials/platform/ios/plugins_for_ios.rst:491
msgid "``show_game_center``"
msgstr ""

#: ../../docs/tutorials/platform/ios/plugins_for_ios.rst:493
msgid ""
"Displays the built in Game Center overlay showing leaderboards, "
"achievements, and challenges."
msgstr ""

#: ../../docs/tutorials/platform/ios/plugins_for_ios.rst:499
msgid "Takes a Dictionary as a parameter, with two fields:"
msgstr ""

#: ../../docs/tutorials/platform/ios/plugins_for_ios.rst:501
msgid ""
"``view`` (string) (optional) the name of the view to present. Accepts "
"\"default\", \"leaderboards\", \"achievements\", or \"challenges\". Defaults "
"to \"default\"."
msgstr ""

#: ../../docs/tutorials/platform/ios/plugins_for_ios.rst:504
msgid ""
"``leaderboard_name`` (string) (optional) the name of the leaderboard to "
"present. Only used when \"view\" is \"leaderboards\" (or \"default\" is "
"configured to show leaderboards). If not specified, Game Center will display "
"the aggregate leaderboard."
msgstr ""

#: ../../docs/tutorials/platform/ios/plugins_for_ios.rst:521
msgid "On close:"
msgstr ""

#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:6
msgid "HTML5 shell class reference"
msgstr ""

#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:8
msgid ""
"Projects exported for the Web expose the :js:class:`Engine` class to the "
"JavaScript environment, that allows fine control over the engine's start-up "
"process."
msgstr ""

#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:11
msgid ""
"This API is built in an asynchronous manner and requires basic understanding "
"of `Promises <https://developer.mozilla.org/en-US/docs/Web/JavaScript/Guide/"
"Using_promises>`__."
msgstr ""

#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:15
#, fuzzy
msgid "Engine"
msgstr "O Godot pokretaču igre"

#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:17
msgid ""
"The ``Engine`` class provides methods for loading and starting exported "
"projects on the Web. For default export settings, this is already part of "
"the exported HTML page. To understand practical use of the ``Engine`` class, "
"see :ref:`Custom HTML page for Web export <doc_customizing_html5_shell>`."
msgstr ""

#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:22
msgid "Static Methods"
msgstr ""

#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:25
#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:36
#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:38
#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:40
#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:42
#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:68
#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:101
#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:123
#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:141
#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:160
msgid "Promise"
msgstr ""

#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:25
msgid ":js:attr:`load <Engine.load>` **(** string basePath **)**"
msgstr ""

#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:27
#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:44
#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:46
#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:213
msgid "void"
msgstr ""

#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:27
msgid ":js:attr:`unload <Engine.unload>` **(** **)**"
msgstr ""

#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:29
#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:86
#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:191
#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:228
#: ../../docs/tutorials/shaders/visual_shaders.rst:106
msgid "boolean"
msgstr ""

#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:29
msgid ""
":js:attr:`isWebGLAvailable <Engine.isWebGLAvailable>` **(** *[ number "
"majorVersion=1 ]* **)**"
msgstr ""

#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:33
msgid "Instance Methods"
msgstr ""

#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:36
msgid ""
":js:attr:`init <Engine.prototype.init>` **(** *[ string basePath ]* **)**"
msgstr ""

#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:38
msgid ""
":js:attr:`preloadFile <Engine.prototype.preloadFile>` **(** string\\|"
"ArrayBuffer file *[, string path ]* **)**"
msgstr ""

#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:40
msgid ""
":js:attr:`start <Engine.prototype.start>` **(** EngineConfig override **)**"
msgstr ""

#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:42
msgid ""
":js:attr:`startGame <Engine.prototype.startGame>` **(** EngineConfig "
"override **)**"
msgstr ""

#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:44
msgid ""
":js:attr:`copyToFS <Engine.prototype.copyToFS>` **(** string path, "
"ArrayBuffer buffer **)**"
msgstr ""

#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:46
msgid ":js:attr:`requestQuit <Engine.prototype.requestQuit>` **(** **)**"
msgstr ""

#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:51
msgid "Create a new Engine instance with the given configuration."
msgstr ""

#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:0
#: ../../docs/contributing/development/configuring_an_ide/kdevelop.rst:59
#: ../../docs/contributing/development/configuring_an_ide/qt_creator.rst:61
#: ../../docs/contributing/development/configuring_an_ide/xcode.rst:33
msgid "Arguments"
msgstr ""

#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:53
msgid "The initial config for this instance."
msgstr ""

#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:56
msgid "**Static Methods**"
msgstr ""

#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:60
msgid "Load the engine from the specified base path."
msgstr ""

#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:62
#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:95
msgid "Base path of the engine to load."
msgstr ""

#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:0
msgid "Returns"
msgstr ""

#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:65
msgid "A Promise that resolves once the engine is loaded."
msgstr ""

#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:0
msgid "Return type"
msgstr ""

#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:72
msgid "Unload the engine to free memory."
msgstr ""

#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:74
msgid ""
"This method will be called automatically depending on the configuration. "
"See :js:attr:`unloadAfterInit`."
msgstr ""

#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:78
msgid ""
"Check whether WebGL is available. Optionally, specify a particular version "
"of WebGL to check for."
msgstr ""

#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:80
msgid "The major WebGL version to check for."
msgstr ""

#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:83
msgid "If the given major version of WebGL is available."
msgstr ""

#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:88
msgid "**Instance Methods**"
msgstr ""

#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:92
msgid ""
"Initialize the engine instance. Optionally, pass the base path to the engine "
"to load it, if it hasn't been loaded yet. See :js:meth:`Engine.load`."
msgstr ""

#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:98
msgid "A ``Promise`` that resolves once the engine is loaded and initialized."
msgstr ""

#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:105
msgid ""
"Load a file so it is available in the instance's file system once it runs. "
"Must be called **before** starting the instance."
msgstr ""

#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:108
msgid ""
"If not provided, the ``path`` is derived from the URL of the loaded file."
msgstr ""

#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:110
msgid ""
"The file to preload.  If a ``string`` the file will be loaded from that "
"path.  If an ``ArrayBuffer`` or a view on one, the buffer will used as the "
"content of the file."
msgstr ""

#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:111
msgid "The file to preload."
msgstr ""

#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:113
msgid "If a ``string`` the file will be loaded from that path."
msgstr ""

#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:115
msgid ""
"If an ``ArrayBuffer`` or a view on one, the buffer will used as the content "
"of the file."
msgstr ""

#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:117
msgid ""
"Path by which the file will be accessible. Required, if ``file`` is not a "
"string."
msgstr ""

#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:120
msgid "A Promise that resolves once the file is loaded."
msgstr ""

#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:127
msgid ""
"Start the engine instance using the given override configuration (if any). :"
"js:meth:`startGame <Engine.prototype.startGame>` can be used in typical "
"cases instead."
msgstr ""

#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:130
msgid ""
"This will initialize the instance if it is not initialized. For manual "
"initialization, see :js:meth:`init <Engine.prototype.init>`. The engine must "
"be loaded beforehand."
msgstr ""

#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:133
msgid ""
"Fails if a canvas cannot be found on the page, or not specified in the "
"configuration."
msgstr ""

#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:135
#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:154
msgid "An optional configuration override."
msgstr ""

#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:138
msgid "Promise that resolves once the engine started."
msgstr ""

#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:145
msgid ""
"Start the game instance using the given configuration override (if any)."
msgstr ""

#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:147
msgid ""
"This will initialize the instance if it is not initialized. For manual "
"initialization, see :js:meth:`init <Engine.prototype.init>`."
msgstr ""

#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:149
msgid ""
"This will load the engine if it is not loaded, and preload the main pck."
msgstr ""

#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:151
msgid ""
"This method expects the initial config (or the override) to have both the :"
"js:attr:`executable` and :js:attr:`mainPack` properties set (normally done "
"by the editor during export)."
msgstr ""

#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:157
msgid "Promise that resolves once the game started."
msgstr ""

#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:164
msgid ""
"Create a file at the specified ``path`` with the passed as ``buffer`` in the "
"instance's file system."
msgstr ""

#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:166
msgid "The location where the file will be created."
msgstr ""

#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:169
msgid "The content of the file."
msgstr ""

#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:174
msgid "Request that the current instance quit."
msgstr ""

#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:176
msgid ""
"This is akin the user pressing the close button in the window manager, and "
"will have no effect if the engine has crashed, or is stuck in a loop."
msgstr ""

#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:180
msgid "Engine configuration"
msgstr ""

#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:182
msgid ""
"An object used to configure the Engine instance based on godot export "
"options, and to override those in custom HTML templates if needed."
msgstr ""

#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:186
#: ../../docs/tutorials/scripting/how_to_read_the_godot_api.rst:61
msgid "Properties"
msgstr ""

#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:0
#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:189
msgid "type"
msgstr ""

#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:189
msgid "name"
msgstr ""

#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:191
msgid ":js:attr:`unloadAfterInit`"
msgstr ""

#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:193
#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:238
msgid "HTMLCanvasElement"
msgstr ""

#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:193
msgid ":js:attr:`canvas`"
msgstr ""

#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:195
msgid ":js:attr:`executable`"
msgstr ""

#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:197
msgid ":js:attr:`mainPack`"
msgstr ""

#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:199
msgid ":js:attr:`locale`"
msgstr ""

#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:201
#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:280
msgid "number"
msgstr ""

#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:201
msgid ":js:attr:`canvasResizePolicy`"
msgstr ""

#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:203
#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:292
msgid "Array.<string>"
msgstr ""

#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:203
msgid ":js:attr:`args`"
msgstr ""

#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:205
#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:207
#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:209
#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:211
#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:213
#, fuzzy
msgid "function"
msgstr "Uvod"

#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:205
msgid ":js:attr:`onExecute`"
msgstr ""

#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:207
msgid ":js:attr:`onExit`"
msgstr ""

#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:209
msgid ":js:attr:`onProgress`"
msgstr ""

#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:211
msgid ":js:attr:`onPrint`"
msgstr ""

#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:213
msgid ":js:attr:`onPrintError`"
msgstr ""

#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:218
msgid ""
"The Engine configuration object. This is just a typedef, create it like a "
"regular object, e.g.:"
msgstr ""

#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:220
msgid "``const MyConfig = { executable: 'godot', unloadAfterInit: false }``"
msgstr ""

#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:222
msgid "**Property Descriptions**"
msgstr ""

#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:226
msgid ""
"Whether the unload the engine automatically after the instance is "
"initialized."
msgstr ""

#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:0
msgid "value"
msgstr ""

#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:230
msgid "``true``"
msgstr ""

#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:234
msgid "The HTML DOM Canvas object to use."
msgstr ""

#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:236
msgid ""
"By default, the first canvas element in the document will be used is none is "
"specified."
msgstr ""

#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:240
#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:256
#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:267
#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:346
msgid "``null``"
msgstr ""

#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:244
msgid ""
"The name of the WASM file without the extension. (Set by Godot Editor export "
"process)."
msgstr ""

#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:248
msgid "``\"\"``"
msgstr ""

#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:252
msgid ""
"An alternative name for the game pck to load. The executable name is used "
"otherwise."
msgstr ""

#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:260
msgid "Specify a language code to select the proper localization for the game."
msgstr ""

#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:262
msgid ""
"The browser locale will be used if none is specified. See complete list of :"
"ref:`supported locales <doc_locales>`."
msgstr ""

#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:271
msgid ""
"The canvas resize policy determines how the canvas should be resized by "
"Godot."
msgstr ""

#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:273
msgid ""
"``0`` means Godot won't do any resizing. This is useful if you want to "
"control the canvas size from javascript code in your template."
msgstr ""

#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:276
msgid ""
"``1`` means Godot will resize the canvas on start, and when changing window "
"size via engine functions."
msgstr ""

#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:278
msgid ""
"``2`` means Godot will adapt the canvas size to match the whole browser "
"window."
msgstr ""

#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:282
msgid "``2``"
msgstr ""

#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:286
msgid "The arguments to be passed as command line arguments on startup."
msgstr ""

#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:288
msgid "See :ref:`command line tutorial <doc_command_line_tutorial>`."
msgstr ""

#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:290
msgid ""
"**Note**: :js:meth:`startGame <Engine.prototype.startGame>` will always add "
"the ``--main-pack`` argument."
msgstr ""

#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:294
msgid "``[]``"
msgstr ""

#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:298
msgid "A callback function for handling Godot's ``OS.execute`` calls."
msgstr ""

#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:300
msgid ""
"This is for example used in the Web Editor template to switch between "
"Project Manager and editor, and for running the game."
msgstr ""

#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:302
msgid "The path that Godot's wants executed."
msgstr ""

#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:305
msgid "The arguments of the \"command\" to execute."
msgstr ""

#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:310
msgid "A callback function for being notified when the Godot instance quits."
msgstr ""

#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:312
msgid ""
"**Note**: This function will not be called if the engine crashes or become "
"unresponsive."
msgstr ""

#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:314
msgid "The status code returned by Godot on exit."
msgstr ""

#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:319
msgid "A callback function for displaying download progress."
msgstr ""

#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:321
msgid ""
"The function is called once per frame while downloading files, so the usage "
"of ``requestAnimationFrame()`` is not necessary."
msgstr ""

#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:324
msgid ""
"If the callback function receives a total amount of bytes as 0, this means "
"that it is impossible to calculate. Possible reasons include:"
msgstr ""

#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:327
msgid "Files are delivered with server-side chunked compression"
msgstr ""

#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:328
msgid "Files are delivered with server-side compression on Chromium"
msgstr ""

#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:329
msgid ""
"Not all file downloads have started yet (usually on servers without multi-"
"threading)"
msgstr ""

#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:331
msgid "The current amount of downloaded bytes so far."
msgstr ""

#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:334
msgid "The total amount of bytes to be downloaded."
msgstr ""

#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:339
msgid ""
"A callback function for handling the standard output stream. This method "
"should usually only be used in debug pages."
msgstr ""

#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:341
msgid "By default, ``console.log()`` is used."
msgstr ""

#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:343
msgid "A variadic number of arguments to be printed."
msgstr ""

#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:348
msgid ""
"A callback function for handling the standard error stream. This method "
"should usually only be used in debug pages."
msgstr ""

#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:350
msgid "By default, ``console.error()`` is used."
msgstr ""

#: ../../docs/tutorials/platform/web/html5_shell_classref.rst:352
msgid "A variadic number of arguments to be printed as errors."
msgstr ""

#: ../../docs/tutorials/platform/web/customizing_html5_shell.rst:6
msgid "Custom HTML page for Web export"
msgstr ""

#: ../../docs/tutorials/platform/web/customizing_html5_shell.rst:8
msgid ""
"While Web export templates provide a default HTML page fully capable of "
"launching the project without any further customization, it may be "
"beneficial to create a custom HTML page. While the game itself cannot easily "
"be directly controlled from the outside yet, such page allows to customize "
"the initialization process for the engine."
msgstr ""

#: ../../docs/tutorials/platform/web/customizing_html5_shell.rst:13
msgid "Some use-cases where customizing the default page is useful include:"
msgstr ""

#: ../../docs/tutorials/platform/web/customizing_html5_shell.rst:15
msgid "Loading files from a different directory than the page;"
msgstr ""

#: ../../docs/tutorials/platform/web/customizing_html5_shell.rst:16
msgid "Loading a ``.zip`` file instead of a ``.pck`` file as the main pack;"
msgstr ""

#: ../../docs/tutorials/platform/web/customizing_html5_shell.rst:17
msgid "Loading the engine from a different directory than the main pack file;"
msgstr ""

#: ../../docs/tutorials/platform/web/customizing_html5_shell.rst:18
msgid ""
"Adding a click-to-play button so that games can be started in the fullscreen "
"mode;"
msgstr ""

#: ../../docs/tutorials/platform/web/customizing_html5_shell.rst:19
msgid ""
"Loading some extra files before the engine starts, making them available in "
"the project file system as soon as possible;"
msgstr ""

#: ../../docs/tutorials/platform/web/customizing_html5_shell.rst:21
msgid ""
"Passing custom command line arguments, e.g. ``-s`` to start a ``MainLoop`` "
"script."
msgstr ""

#: ../../docs/tutorials/platform/web/customizing_html5_shell.rst:23
msgid ""
"The default HTML page is available in the Godot Engine repository at `/misc/"
"dist/html/full-size.html <https://github.com/godotengine/godot/blob/master/"
"misc/dist/html/full-size.html>`__ but the following template can be used as "
"a much simpler example:"
msgstr ""

#: ../../docs/tutorials/platform/web/customizing_html5_shell.rst:47
msgid ""
"As shown by the example above, it is mostly a regular HTML document, with "
"few placeholders which needs to be replaced during export, an html "
"``<canvas>`` element, and some simple JavaScript code that calls the :js:"
"class:`Engine` class."
msgstr ""

#: ../../docs/tutorials/platform/web/customizing_html5_shell.rst:51
msgid "The only required placeholders are:"
msgstr ""

#: ../../docs/tutorials/platform/web/customizing_html5_shell.rst:53
msgid ""
"``$GODOT_URL``: The name of the main JavaScript file, which provides the :js:"
"class:`Engine` class required to start the engine and that must be included "
"in the HTML as a ``<script>``. The name is generated from the *Export Path* "
"during the export process."
msgstr ""

#: ../../docs/tutorials/platform/web/customizing_html5_shell.rst:58
msgid ""
"``$GODOT_CONFIG``: A JavaScript object, containing the export options and "
"can be later overridden. See :js:attr:`EngineConfig` for the full list of "
"overrides."
msgstr ""

#: ../../docs/tutorials/platform/web/customizing_html5_shell.rst:62
msgid ""
"The following optional placeholders will enable some extra features in your "
"custom HTML template."
msgstr ""

#: ../../docs/tutorials/platform/web/customizing_html5_shell.rst:64
msgid ""
"``$GODOT_PROJECT_NAME``: The project name as defined in the Project "
"Settings. It is a good idea to use it as a ``<title>`` in your template."
msgstr ""

#: ../../docs/tutorials/platform/web/customizing_html5_shell.rst:68
msgid ""
"``$GODOT_HEAD_INCLUDE``: A custom string to include in the HTML document "
"just before the end of the ``<head>`` tag. It is customized in the export "
"options under the *Html / Head Include* section. While you fully control the "
"HTML page you create, this variable can be useful for configuring parts of "
"the HTML ``head`` element from the Godot Editor, e.g. for different Web "
"export presets."
msgstr ""

#: ../../docs/tutorials/platform/web/customizing_html5_shell.rst:74
msgid ""
"When the custom page is ready, it can be selected in the export options "
"under the *Html / Custom Html Shell* section."
msgstr ""

#: ../../docs/tutorials/platform/web/customizing_html5_shell.rst:80
#, fuzzy
msgid "Starting the project"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/platform/web/customizing_html5_shell.rst:81
msgid ""
"To be able to start the game, you need to write a script that initializes "
"the engine — the control code. This process consists of three steps, but as "
"shown here, most of them can be skipped depending on how much customization "
"is needed."
msgstr ""

#: ../../docs/tutorials/platform/web/customizing_html5_shell.rst:85
msgid ""
"See the :ref:`HTML5 shell class reference <doc_html5_shell_classref>`, for "
"the full list of methods and options available."
msgstr ""

#: ../../docs/tutorials/platform/web/customizing_html5_shell.rst:87
msgid ""
"First, the engine must be loaded, then it needs to be initialized, and after "
"this the project can finally be started. You can perform every of these "
"steps manually and with great control. However, in the simplest case all you "
"need to do is to create an instance of the :js:class:`Engine` class with the "
"exported configuration, and then call the :js:meth:`engine.startGame <Engine."
"prototype.startGame>` method optionally overriding any :js:attr:"
"`EngineConfig` parameters."
msgstr ""

#: ../../docs/tutorials/platform/web/customizing_html5_shell.rst:103
msgid ""
"This snippet of code automatically loads and initializes the engine before "
"starting the game. It uses the given configuration to load the engine. The :"
"js:meth:`engine.startGame <Engine.prototype.startGame>` method is "
"asynchronous and returns a ``Promise``. This allows your control code to "
"track if the game was loaded correctly without blocking execution or relying "
"on polling."
msgstr ""

#: ../../docs/tutorials/platform/web/customizing_html5_shell.rst:108
msgid ""
"In case your project needs to have special control over the start arguments "
"and dependency files, the :js:meth:`engine.start <Engine.prototype.start>` "
"method can be used instead. Note, that this method do not automatically "
"preload the ``pck`` file, so you will probably want to manually preload it "
"(and any other extra file) via the :js:meth:`engine.preloadFile <Engine."
"prototype.preloadFile>` method."
msgstr ""

#: ../../docs/tutorials/platform/web/customizing_html5_shell.rst:113
msgid ""
"Optionally, you can also manually :js:meth:`engine.init <Engine.prototype."
"init>` to perform specific actions after the module initialization, but "
"before the engine starts."
msgstr ""

#: ../../docs/tutorials/platform/web/customizing_html5_shell.rst:116
msgid ""
"This process is a bit more complex, but gives you full control over the "
"engine startup process."
msgstr ""

#: ../../docs/tutorials/platform/web/customizing_html5_shell.rst:135
msgid ""
"To load the engine manually the :js:meth:`Engine.load` static method must be "
"called. As this method is static, multiple engine instances can be spawned "
"if the share the same ``wasm``."
msgstr ""

#: ../../docs/tutorials/platform/web/customizing_html5_shell.rst:138
msgid ""
"Multiple instances cannot be spawned by default, as the engine is "
"immediately unloaded after it is initialized. To prevent this from happening "
"see the :js:attr:`unloadAfterInit` override option. It is still possible to "
"unload the engine manually afterwards by calling the :js:meth:`Engine."
"unload` static method. Unloading the engine frees browser memory by "
"unloading files that are no longer needed once the instance is initialized."
msgstr ""

#: ../../docs/tutorials/platform/web/customizing_html5_shell.rst:144
msgid "Customizing the behavior"
msgstr ""

#: ../../docs/tutorials/platform/web/customizing_html5_shell.rst:145
msgid ""
"In the Web environment several methods can be used to guarantee that the "
"game will work as intended."
msgstr ""

#: ../../docs/tutorials/platform/web/customizing_html5_shell.rst:147
msgid ""
"If you target a specific version of WebGL, or just want to check if WebGL is "
"available at all, you can call the :js:meth:`Engine.isWebGLAvailable` "
"method. It optionally takes an argument that allows to test for a specific "
"major version of WebGL."
msgstr ""

#: ../../docs/tutorials/platform/web/customizing_html5_shell.rst:151
msgid ""
"As the real executable file does not exist in the Web environment, the "
"engine only stores a virtual filename formed from the base name of loaded "
"engine files. This value affects the output of the :ref:`OS."
"get_executable_path() <class_OS_method_get_executable_path>` method and "
"defines the name of the automatically started main pack. The :js:attr:"
"`executable` override option can be used to override this value."
msgstr ""

#: ../../docs/tutorials/platform/web/customizing_html5_shell.rst:158
msgid "Customizing the presentation"
msgstr ""

#: ../../docs/tutorials/platform/web/customizing_html5_shell.rst:159
msgid ""
"Several configuration options can be used to further customize the look and "
"behavior of the game on your page."
msgstr ""

#: ../../docs/tutorials/platform/web/customizing_html5_shell.rst:161
msgid ""
"By default, the first canvas element on the page is used for rendering. To "
"use a different canvas element the :js:attr:`canvas` override option can be "
"used. It requires a reference to the DOM element itself."
msgstr ""

#: ../../docs/tutorials/platform/web/customizing_html5_shell.rst:170
msgid ""
"The way the engine resize the canvas can be configured via the :js:attr:"
"`canvasResizePolicy` override option."
msgstr ""

#: ../../docs/tutorials/platform/web/customizing_html5_shell.rst:173
msgid ""
"If your game takes some time to load, it may be useful to display a custom "
"loading UI which tracks the progress. This can be achieved with the :js:attr:"
"`onProgress` callback option, which allows to set up a callback function "
"that will be called regularly as the engine loads new bytes."
msgstr ""

#: ../../docs/tutorials/platform/web/customizing_html5_shell.rst:184
msgid ""
"Be aware that in some cases ``total`` can be ``0``. This means that it "
"cannot be calculated."
msgstr ""

#: ../../docs/tutorials/platform/web/customizing_html5_shell.rst:186
msgid ""
"If your game supports multiple languages, the :js:attr:`locale` override "
"option can be used to force a specific locale, provided you have a valid "
"language code string. It may be good to use server-side logic to determine "
"which languages a user may prefer. This way the language code can be taken "
"from the ``Accept-Language`` HTTP header, or determined by a GeoIP service."
msgstr ""

#: ../../docs/tutorials/platform/web/customizing_html5_shell.rst:193
msgid ""
"To debug exported projects, it may be useful to read the standard output and "
"error streams generated by the engine. This is similar to the output shown "
"in the editor console window. By default, standard ``console.log`` and "
"``console.warn`` are used for the output and error streams respectively. "
"This behavior can be customized by setting your own functions to handle "
"messages."
msgstr ""

#: ../../docs/tutorials/platform/web/customizing_html5_shell.rst:198
msgid ""
"Use the :js:attr:`onPrint` override option to set a callback function for "
"the output stream, and the :js:attr:`onPrintError` override option to set a "
"callback function for the error stream."
msgstr ""

#: ../../docs/tutorials/platform/web/customizing_html5_shell.rst:211
msgid ""
"When handling the engine output, keep in mind that it may not be desirable "
"to print it out in the finished product."
msgstr ""

#: ../../docs/tutorials/platform/consoles.rst:4
#, fuzzy
msgid "Console support in Godot"
msgstr "Koji jezici su podržani u Godot-u?"

#: ../../docs/tutorials/platform/consoles.rst:7
#, fuzzy
msgid "Console porting process"
msgstr "Koji jezici su podržani u Godot-u?"

#: ../../docs/tutorials/platform/consoles.rst:9
msgid ""
"In order to develop for consoles in Godot, you need access to the console "
"SDK and export templates for it. These export templates need to be developed "
"either by yourself or someone hired to do it, or provided by a third party "
"company."
msgstr ""

#: ../../docs/tutorials/platform/consoles.rst:13
msgid ""
"Currently, the only console Godot officially supports is Steam Deck (through "
"the official Linux export templates)."
msgstr ""

#: ../../docs/tutorials/platform/consoles.rst:16
msgid "The reason other consoles are not officially supported are:"
msgstr ""

#: ../../docs/tutorials/platform/consoles.rst:18
msgid ""
"To develop for consoles, one must be licensed as a company. As an open "
"source project, Godot has no legal structure to provide console ports."
msgstr ""

#: ../../docs/tutorials/platform/consoles.rst:20
msgid ""
"Console SDKs are secret and covered by non-disclosure agreements. Even if we "
"could get access to them, we could not publish the platform-specific code "
"under an open source license."
msgstr ""

#: ../../docs/tutorials/platform/consoles.rst:24
msgid ""
"As explained, however, it is possible to port your games to consoles thanks "
"to services provided by third-party companies."
msgstr ""

#: ../../docs/tutorials/platform/consoles.rst:29
msgid ""
"In practice, the process is quite similar to Unity and Unreal Engine. In "
"other words, there is no engine that is legally allowed to distribute "
"console export templates without requiring the user to prove that they are a "
"licensed console developer."
msgstr ""

#: ../../docs/tutorials/platform/consoles.rst:35
msgid "Console publishing process"
msgstr ""

#: ../../docs/tutorials/platform/consoles.rst:37
msgid ""
"Regardless of the engine used to create the game, the process to publish a "
"game to a console platform is as follows:"
msgstr ""

#: ../../docs/tutorials/platform/consoles.rst:40
msgid ""
"Register a developer account on the console manufacturer's website, then "
"sign NDAs and publishing contracts. This requires you to have a registered "
"legal entity."
msgstr ""

#: ../../docs/tutorials/platform/consoles.rst:43
msgid ""
"Gain access to the publishing platform by passing the acceptance process. "
"This can take up to several months. Note that this step is significantly "
"easier if an established publisher is backing your game. Nintendo is "
"generally known to be more accepting of smaller developers, but this is not "
"guaranteed."
msgstr ""

#: ../../docs/tutorials/platform/consoles.rst:47
msgid ""
"Get access to developer tools and order a console specially made for "
"developers (*devkit*). The cost of those devkits is confidential."
msgstr ""

#: ../../docs/tutorials/platform/consoles.rst:49
msgid "Port the engine to the console platform or pay a company to do it."
msgstr ""

#: ../../docs/tutorials/platform/consoles.rst:50
msgid ""
"To be published, your game needs to be rated in the regions you'd like to "
"sell it in. For example, game ratings are handled by `ESRB <https://www.esrb."
"org/>`__ in North America, and `PEGI <https://pegi.info/>`__ in Europe. "
"Indie developers can generally get a rating for cheaper compared to more "
"established developers."
msgstr ""

#: ../../docs/tutorials/platform/consoles.rst:55
msgid ""
"Due to the complexity of the process, many studios and developers prefer to "
"outsource console porting."
msgstr ""

#: ../../docs/tutorials/platform/consoles.rst:58
msgid ""
"You can read more about the console publishing process in this article: "
"`Godot and consoles, all you need to know <https://godotengine.org/article/"
"godot-consoles-all-you-need-know/>`__"
msgstr ""

#: ../../docs/tutorials/platform/consoles.rst:62
msgid "Third-party support"
msgstr ""

#: ../../docs/tutorials/platform/consoles.rst:64
msgid ""
"Console ports of Godot are offered by third-party companies (which have "
"ported Godot on their own). These companies also offer publishing of your "
"games to various consoles."
msgstr ""

#: ../../docs/tutorials/platform/consoles.rst:68
msgid "Following is the list of providers:"
msgstr ""

#: ../../docs/tutorials/platform/consoles.rst:70
msgid ""
"`Lone Wolf Technology <https://www.lonewolftechnology.com/>`_ offers Switch "
"and Playstation 4 porting and publishing of Godot games."
msgstr ""

#: ../../docs/tutorials/platform/consoles.rst:72
msgid ""
"`Pineapple Works <https://pineapple.works/>`_ offers Switch, Xbox One & Xbox "
"Series X/S (GDK) porting and publishing of Godot games (GDScript/C#)."
msgstr ""

#: ../../docs/tutorials/platform/consoles.rst:74
msgid ""
"`RAWRLAB games <https://www.rawrlab.com/>`_ offers Switch porting of Godot "
"games."
msgstr ""

#: ../../docs/tutorials/platform/consoles.rst:76
msgid ""
"`mazette! games <https://mazette.games/>`_ offers Switch, Xbox One and Xbox "
"Series X/S porting and publishing of Godot games."
msgstr ""

#: ../../docs/tutorials/platform/consoles.rst:78
msgid ""
"`Olde Sküül <https://oldeskuul.com/>`_ offers Switch, Xbox One, Playstation "
"4 & Playstation 5 porting and publishing of Godot games."
msgstr ""

#: ../../docs/tutorials/platform/consoles.rst:80
msgid ""
"`Tuanisapps <https://www.tuanisapps.com/>`_ offers Switch porting and "
"publishing of Godot games."
msgstr ""

#: ../../docs/tutorials/platform/consoles.rst:82
msgid ""
"`Seaven Studio <https://www.seaven-studio.com/>`_ offers Switch, Xbox One, "
"Xbox Series, PlayStation 4 & PlayStation 5 porting of Godot games."
msgstr ""

#: ../../docs/tutorials/platform/consoles.rst:86
msgid ""
"If your company offers porting, or porting *and* publishing services for "
"Godot games, feel free to `contact the Godot Foundation <https://godot."
"foundation/#contact>`_ to add your company to the list above."
msgstr ""

#: ../../docs/tutorials/plugins/editor/installing_plugins.rst:4
#, fuzzy
msgid "Installing plugins"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/plugins/editor/installing_plugins.rst:6
msgid ""
"Godot features an editor plugin system with numerous plugins developed by "
"the community. Plugins can extend the editor's functionality with new nodes, "
"additional docks, convenience features, and more."
msgstr ""

#: ../../docs/tutorials/plugins/editor/installing_plugins.rst:11
#, fuzzy
msgid "Finding plugins"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/plugins/editor/installing_plugins.rst:13
msgid ""
"The preferred way to find Godot plugins is to use the `Asset Library "
"<https://godotengine.org/asset-library/>`_. While it can be browsed online, "
"it's more convenient to use it directly from the editor. To do so, click the "
"**AssetLib** tab at the top of the editor:"
msgstr ""

#: ../../docs/tutorials/plugins/editor/installing_plugins.rst:20
msgid "You can also find assets on code hosting websites such as GitHub."
msgstr ""

#: ../../docs/tutorials/plugins/editor/installing_plugins.rst:24
msgid ""
"Some repositories describe themselves as \"plugins\" but may not actually be "
"*editor* plugins. This is especially the case for scripts that are intended "
"to be used in a running project. You don't need to enable such plugins to "
"use them. Download them and extract the files in your project folder."
msgstr ""

#: ../../docs/tutorials/plugins/editor/installing_plugins.rst:29
msgid ""
"One way to distinguish editor plugins from non-editor plugins is to look for "
"a ``plugin.cfg`` file in the repository that hosts the plugin. If the "
"repository contains a ``plugin.cfg`` file in a folder placed in the ``addons/"
"`` folder, then it is an editor plugin."
msgstr ""

#: ../../docs/tutorials/plugins/editor/installing_plugins.rst:35
#, fuzzy
msgid "Installing a plugin"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/plugins/editor/installing_plugins.rst:37
msgid ""
"To install a plugin, download it as a ZIP archive. On the Asset Library, "
"this can be done using the **Download** button, either from the editor or "
"using the Web interface."
msgstr ""

#: ../../docs/tutorials/plugins/editor/installing_plugins.rst:41
msgid ""
"On GitHub, if a plugin has *tags* (versions) declared, go to the "
"**Releases** tab to download a stable release. This ensures you download a "
"version that was declared to be stable by its author."
msgstr ""

#: ../../docs/tutorials/plugins/editor/installing_plugins.rst:45
msgid ""
"On GitHub, if the plugin doesn't have any *tags* declared, use the "
"**Download ZIP** button to download a ZIP of the latest revision:"
msgstr ""

#: ../../docs/tutorials/plugins/editor/installing_plugins.rst:50
msgid ""
"Extract the ZIP archive and move the ``addons/`` folder it contains into "
"your project folder. If your project already contains an ``addons/`` folder, "
"move the plugin's ``addons/`` folder into your project folder to merge the "
"new folder contents with the existing one. Your file manager may ask you "
"whether to write into the folder; answer **Yes**. No files will be "
"overwritten in the process."
msgstr ""

#: ../../docs/tutorials/plugins/editor/installing_plugins.rst:57
msgid "Enabling a plugin"
msgstr ""

#: ../../docs/tutorials/plugins/editor/installing_plugins.rst:59
msgid ""
"To enable the freshly installed plugin, open **Project > Project Settings** "
"at the top of the editor then go the **Plugins** tab. If the plugin was "
"packaged correctly, you should see it in the list of plugins. Click on the "
"**Enable** checkbox to enable the plugin."
msgstr ""

#: ../../docs/tutorials/plugins/editor/installing_plugins.rst:67
msgid ""
"You can use the plugin immediately after enabling it; there's no need to "
"restart the editor. Likewise, disabling a plugin can be done without having "
"to restart the editor."
msgstr ""

#: ../../docs/tutorials/plugins/editor/making_plugins.rst:4
msgid "Making plugins"
msgstr ""

#: ../../docs/tutorials/plugins/editor/making_plugins.rst:7
msgid "About plugins"
msgstr ""

#: ../../docs/tutorials/plugins/editor/making_plugins.rst:9
msgid ""
"A plugin is a great way to extend the editor with useful tools. It can be "
"made entirely with GDScript and standard scenes, without even reloading the "
"editor. Unlike modules, you don't need to create C++ code nor recompile the "
"engine. While this makes plugins less powerful, there are still many things "
"you can do with them. Note that a plugin is similar to any scene you can "
"already make, except it is created using a script to add editor "
"functionality."
msgstr ""

#: ../../docs/tutorials/plugins/editor/making_plugins.rst:16
msgid ""
"This tutorial will guide you through the creation of two plugins so you can "
"understand how they work and be able to develop your own. The first is a "
"custom node that you can add to any scene in the project, and the other is a "
"custom dock added to the editor."
msgstr ""

#: ../../docs/tutorials/plugins/editor/making_plugins.rst:22
msgid "Creating a plugin"
msgstr ""

#: ../../docs/tutorials/plugins/editor/making_plugins.rst:24
msgid ""
"Before starting, create a new empty project wherever you want. This will "
"serve as a base to develop and test the plugins."
msgstr ""

#: ../../docs/tutorials/plugins/editor/making_plugins.rst:27
msgid ""
"The first thing you need for the editor to identify a new plugin is to "
"create two files: a ``plugin.cfg`` for configuration and a tool script with "
"the functionality. Plugins have a standard path like ``addons/plugin_name`` "
"inside the project folder. Godot provides a dialog for generating those "
"files and placing them where they need to be."
msgstr ""

#: ../../docs/tutorials/plugins/editor/making_plugins.rst:33
msgid ""
"In the main toolbar, click the ``Project`` dropdown. Then click ``Project "
"Settings...``. Go to the ``Plugins`` tab and then click on the ``Create New "
"Plugin`` button in the top-right."
msgstr ""

#: ../../docs/tutorials/plugins/editor/making_plugins.rst:37
msgid "You will see the dialog appear, like so:"
msgstr ""

#: ../../docs/tutorials/plugins/editor/making_plugins.rst:41
msgid ""
"The placeholder text in each field describes how it affects the plugin's "
"creation of the files and the config file's values."
msgstr ""

#: ../../docs/tutorials/plugins/editor/making_plugins.rst:44
msgid "To continue with the example, use the following values:"
msgstr ""

#: ../../docs/tutorials/plugins/editor/making_plugins.rst:71
msgid ""
"Unchecking the ``Activate now?`` option in C# is always required because, "
"like every other C# script, the EditorPlugin script needs to be compiled "
"which requires building the project. After building the project the plugin "
"can be enabled in the ``Plugins`` tab of ``Project Settings``."
msgstr ""

#: ../../docs/tutorials/plugins/editor/making_plugins.rst:76
msgid "You should end up with a directory structure like this:"
msgstr ""

#: ../../docs/tutorials/plugins/editor/making_plugins.rst:80
msgid ""
"``plugin.cfg`` is an INI file with metadata about your plugin. The name and "
"description help people understand what it does. Your name helps you get "
"properly credited for your work. The version number helps others know if "
"they have an outdated version; if you are unsure on how to come up with the "
"version number, check out `Semantic Versioning <https://semver.org/>`_. The "
"main script file will instruct Godot what your plugin does in the editor "
"once it is active."
msgstr ""

#: ../../docs/tutorials/plugins/editor/making_plugins.rst:89
msgid "The script file"
msgstr ""

#: ../../docs/tutorials/plugins/editor/making_plugins.rst:91
msgid ""
"Upon creation of the plugin, the dialog will automatically open the "
"EditorPlugin script for you. The script has two requirements that you cannot "
"change: it must be a ``@tool`` script, or else it will not load properly in "
"the editor, and it must inherit from :ref:`class_EditorPlugin`."
msgstr ""

#: ../../docs/tutorials/plugins/editor/making_plugins.rst:98
msgid ""
"In addition to the EditorPlugin script, any other GDScript that your plugin "
"uses must *also* be a tool. Any GDScript without ``@tool`` imported into the "
"editor will act like an empty file!"
msgstr ""

#: ../../docs/tutorials/plugins/editor/making_plugins.rst:102
msgid ""
"It's important to deal with initialization and clean-up of resources. A good "
"practice is to use the virtual function :ref:`_enter_tree() "
"<class_Node_private_method__enter_tree>` to initialize your plugin and :ref:"
"`_exit_tree() <class_Node_private_method__exit_tree>` to clean it up. "
"Thankfully, the dialog generates these callbacks for you. Your script should "
"look something like this:"
msgstr ""

#: ../../docs/tutorials/plugins/editor/making_plugins.rst:146
msgid "This is a good template to use when creating new plugins."
msgstr ""

#: ../../docs/tutorials/plugins/editor/making_plugins.rst:149
msgid "A custom node"
msgstr ""

#: ../../docs/tutorials/plugins/editor/making_plugins.rst:151
msgid ""
"Sometimes you want a certain behavior in many nodes, such as a custom scene "
"or control that can be reused. Instancing is helpful in a lot of cases, but "
"sometimes it can be cumbersome, especially if you're using it in many "
"projects. A good solution to this is to make a plugin that adds a node with "
"a custom behavior."
msgstr ""

#: ../../docs/tutorials/plugins/editor/making_plugins.rst:159
msgid ""
"Nodes added via an EditorPlugin are \"CustomType\" nodes. While they work "
"with any scripting language, they have fewer features than :ref:`the Script "
"Class system <doc_gdscript_basics_class_name>`. If you are writing GDScript "
"or NativeScript, we recommend using Script Classes instead."
msgstr ""

#: ../../docs/tutorials/plugins/editor/making_plugins.rst:164
msgid ""
"To create a new node type, you can use the function :ref:`add_custom_type() "
"<class_EditorPlugin_method_add_custom_type>` from the :ref:"
"`class_EditorPlugin` class. This function can add new types to the editor "
"(nodes or resources). However, before you can create the type, you need a "
"script that will act as the logic for the type. While that script doesn't "
"have to use the ``@tool`` annotation, it can be added so the script runs in "
"the editor."
msgstr ""

#: ../../docs/tutorials/plugins/editor/making_plugins.rst:171
msgid ""
"For this tutorial, we'll create a button that prints a message when clicked. "
"For that, we'll need a script that extends from :ref:`class_Button`. It "
"could also extend :ref:`class_BaseButton` if you prefer:"
msgstr ""

#: ../../docs/tutorials/plugins/editor/making_plugins.rst:208
msgid ""
"That's it for our basic button. You can save this as ``my_button.gd`` inside "
"the plugin folder. You'll also need a 16×16 icon to show in the scene tree. "
"If you don't have one, you can grab the default one from the engine and save "
"it in your `addons/my_custom_node` folder as `icon.png`, or use the default "
"Godot logo (`preload(\"res://icon.svg\")`)."
msgstr ""

#: ../../docs/tutorials/plugins/editor/making_plugins.rst:216
#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1804
msgid ""
"SVG images that are used as custom node icons should have the **Editor > "
"Scale With Editor Scale** and **Editor > Convert Icons With Editor Theme** :"
"ref:`import options <doc_importing_images_editor_import_options>` enabled. "
"This allows icons to follow the editor's scale and theming settings if the "
"icons are designed with the same color palette as Godot's own icons."
msgstr ""

#: ../../docs/tutorials/plugins/editor/making_plugins.rst:224
msgid ""
"Now, we need to add it as a custom type so it shows on the **Create New "
"Node** dialog. For that, change the ``custom_node.gd`` script to the "
"following:"
msgstr ""

#: ../../docs/tutorials/plugins/editor/making_plugins.rst:271
msgid ""
"With that done, the plugin should already be available in the plugin list in "
"the **Project Settings**, so activate it as explained in `Checking the "
"results`_."
msgstr ""

#: ../../docs/tutorials/plugins/editor/making_plugins.rst:274
msgid "Then try it out by adding your new node:"
msgstr ""

#: ../../docs/tutorials/plugins/editor/making_plugins.rst:278
msgid ""
"When you add the node, you can see that it already has the script you "
"created attached to it. Set a text to the button, save and run the scene. "
"When you click the button, you can see some text in the console:"
msgstr ""

#: ../../docs/tutorials/plugins/editor/making_plugins.rst:285
msgid "A custom dock"
msgstr ""

#: ../../docs/tutorials/plugins/editor/making_plugins.rst:287
msgid ""
"Sometimes, you need to extend the editor and add tools that are always "
"available. An easy way to do it is to add a new dock with a plugin. Docks "
"are just scenes based on Control, so they are created in a way similar to "
"usual GUI scenes."
msgstr ""

#: ../../docs/tutorials/plugins/editor/making_plugins.rst:291
msgid ""
"Creating a custom dock is done just like a custom node. Create a new "
"``plugin.cfg`` file in the ``addons/my_custom_dock`` folder, then add the "
"following content to it:"
msgstr ""

#: ../../docs/tutorials/plugins/editor/making_plugins.rst:316
msgid ""
"Then create the script ``custom_dock.gd`` in the same folder. Fill it with "
"the :ref:`template we've seen before <doc_making_plugins_template_code>` to "
"get a good start."
msgstr ""

#: ../../docs/tutorials/plugins/editor/making_plugins.rst:320
msgid ""
"Since we're trying to add a new custom dock, we need to create the contents "
"of the dock. This is nothing more than a standard Godot scene: just create a "
"new scene in the editor then edit it."
msgstr ""

#: ../../docs/tutorials/plugins/editor/making_plugins.rst:324
msgid ""
"For an editor dock, the root node **must** be a :ref:`Control "
"<class_Control>` or one of its child classes. For this tutorial, you can "
"create a single button. The name of the root node will also be the name that "
"appears on the dock tab, so be sure to give it a short and descriptive name. "
"Also, don't forget to add some text to your button."
msgstr ""

#: ../../docs/tutorials/plugins/editor/making_plugins.rst:332
msgid ""
"Save this scene as ``my_dock.tscn``. Now, we need to grab the scene we "
"created then add it as a dock in the editor. For this, you can rely on the "
"function :ref:`add_control_to_dock() "
"<class_EditorPlugin_method_add_control_to_dock>` from the :ref:`EditorPlugin "
"<class_EditorPlugin>` class."
msgstr ""

#: ../../docs/tutorials/plugins/editor/making_plugins.rst:337
msgid ""
"You need to select a dock position and define the control to add (which is "
"the scene you just created). Don't forget to **remove the dock** when the "
"plugin is deactivated. The script could look like this:"
msgstr ""

#: ../../docs/tutorials/plugins/editor/making_plugins.rst:397
msgid ""
"Note that, while the dock will initially appear at its specified position, "
"the user can freely change its position and save the resulting layout."
msgstr ""

#: ../../docs/tutorials/plugins/editor/making_plugins.rst:401
msgid "Checking the results"
msgstr ""

#: ../../docs/tutorials/plugins/editor/making_plugins.rst:403
msgid ""
"It's now time to check the results of your work. Open the **Project "
"Settings** and click on the **Plugins** tab. Your plugin should be the only "
"one on the list."
msgstr ""

#: ../../docs/tutorials/plugins/editor/making_plugins.rst:409
msgid ""
"You can see the plugin is not enabled. Click the **Enable** checkbox to "
"activate the plugin. The dock should become visible before you even close "
"the settings window. You should now have a custom dock:"
msgstr ""

#: ../../docs/tutorials/plugins/editor/making_plugins.rst:417
msgid "Going beyond"
msgstr ""

#: ../../docs/tutorials/plugins/editor/making_plugins.rst:419
msgid ""
"Now that you've learned how to make basic plugins, you can extend the editor "
"in several ways. Lots of functionality can be added to the editor with "
"GDScript; it is a powerful way to create specialized editors without having "
"to delve into C++ modules."
msgstr ""

#: ../../docs/tutorials/plugins/editor/making_plugins.rst:424
msgid ""
"You can make your own plugins to help yourself and share them in the `Asset "
"Library <https://godotengine.org/asset-library/>`_ so that people can "
"benefit from your work."
msgstr ""

#: ../../docs/tutorials/plugins/editor/making_plugins.rst:431
msgid "Registering autoloads/singletons in plugins"
msgstr ""

#: ../../docs/tutorials/plugins/editor/making_plugins.rst:433
msgid ""
"It is possible for editor plugins to automatically register :ref:`autoloads "
"<doc_singletons_autoload>` when the plugin is enabled. This also includes "
"unregistering the autoload when the plugin is disabled."
msgstr ""

#: ../../docs/tutorials/plugins/editor/making_plugins.rst:437
msgid ""
"This makes setting up plugins faster for users, as they no longer have to "
"manually add autoloads to their project settings if your editor plugin "
"requires the use of an autoload."
msgstr ""

#: ../../docs/tutorials/plugins/editor/making_plugins.rst:441
msgid "Use the following code to register a singleton from an editor plugin:"
msgstr ""

#: ../../docs/tutorials/plugins/editor/making_main_screen_plugins.rst:6
msgid "Making main screen plugins"
msgstr ""

#: ../../docs/tutorials/plugins/editor/making_main_screen_plugins.rst:9
msgid "What this tutorial covers"
msgstr ""

#: ../../docs/tutorials/plugins/editor/making_main_screen_plugins.rst:11
msgid ""
"Main screen plugins allow you to create new UIs in the central part of the "
"editor, which appear next to the \"2D\", \"3D\", \"Script\", and "
"\"AssetLib\" buttons. Such editor plugins are referred as \"Main screen "
"plugins\"."
msgstr ""

#: ../../docs/tutorials/plugins/editor/making_main_screen_plugins.rst:16
msgid ""
"This tutorial leads you through the creation of a basic main screen plugin. "
"For the sake of simplicity, our main screen plugin will contain a single "
"button that prints text to the console."
msgstr ""

#: ../../docs/tutorials/plugins/editor/making_main_screen_plugins.rst:21
msgid "Initializing the plugin"
msgstr ""

#: ../../docs/tutorials/plugins/editor/making_main_screen_plugins.rst:23
msgid ""
"First create a new plugin from the Plugins menu. For this tutorial, we'll "
"put it in a folder called ``main_screen``, but you can use any name you'd "
"like."
msgstr ""

#: ../../docs/tutorials/plugins/editor/making_main_screen_plugins.rst:26
msgid ""
"The plugin script will come with ``_enter_tree()`` and ``_exit_tree()`` "
"methods, but for a main screen plugin we need to add a few extra methods. "
"Add five extra methods such that the script looks like this:"
msgstr ""

#: ../../docs/tutorials/plugins/editor/making_main_screen_plugins.rst:100
msgid ""
"The important part in this script is the ``_has_main_screen()`` function, "
"which is overloaded so it returns ``true``. This function is automatically "
"called by the editor on plugin activation, to tell it that this plugin adds "
"a new center view to the editor. For now, we'll leave this script as-is and "
"we'll come back to it later."
msgstr ""

#: ../../docs/tutorials/plugins/editor/making_main_screen_plugins.rst:107
msgid "Main screen scene"
msgstr ""

#: ../../docs/tutorials/plugins/editor/making_main_screen_plugins.rst:109
msgid ""
"Create a new scene with a root node derived from ``Control`` (for this "
"example plugin, we'll make the root node a ``CenterContainer``). Select this "
"root node, and in the viewport, click the ``Layout`` menu and select ``Full "
"Rect``. You also need to enable the ``Expand`` vertical size flag in the "
"inspector. The panel now uses all the space available in the main viewport."
msgstr ""

#: ../../docs/tutorials/plugins/editor/making_main_screen_plugins.rst:116
msgid ""
"Next, let's add a button to our example main screen plugin. Add a ``Button`` "
"node, and set the text to \"Print Hello\" or similar. Add a script to the "
"button like this:"
msgstr ""

#: ../../docs/tutorials/plugins/editor/making_main_screen_plugins.rst:144
msgid ""
"Then connect the \"pressed\" signal to itself. If you need help with "
"signals, see the :ref:`doc_signals` article."
msgstr ""

#: ../../docs/tutorials/plugins/editor/making_main_screen_plugins.rst:147
msgid ""
"We are done with the main screen panel. Save the scene as ``main_panel."
"tscn``."
msgstr ""

#: ../../docs/tutorials/plugins/editor/making_main_screen_plugins.rst:150
msgid "Update the plugin script"
msgstr ""

#: ../../docs/tutorials/plugins/editor/making_main_screen_plugins.rst:152
msgid ""
"We need to update the ``main_screen_plugin.gd`` script so the plugin "
"instances our main panel scene and places it where it needs to be. Here is "
"the full plugin script:"
msgstr ""

#: ../../docs/tutorials/plugins/editor/making_main_screen_plugins.rst:252
msgid ""
"A couple of specific lines were added. ``MainPanel`` is a constant that "
"holds a reference to the scene, and we instance it into "
"`main_panel_instance`."
msgstr ""

#: ../../docs/tutorials/plugins/editor/making_main_screen_plugins.rst:255
msgid ""
"The ``_enter_tree()`` function is called before ``_ready()``. This is where "
"we instance the main panel scene, and add them as children of specific parts "
"of the editor. We use ``EditorInterface.get_editor_main_screen()`` to obtain "
"the main editor screen and add our main panel instance as a child to it. We "
"call the ``_make_visible(false)`` function to hide the main panel so it "
"doesn't compete for space when first activating the plugin."
msgstr ""

#: ../../docs/tutorials/plugins/editor/making_main_screen_plugins.rst:262
msgid ""
"The ``_exit_tree()`` function is called when the plugin is deactivated. If "
"the main screen still exists, we call ``queue_free()`` to free the instance "
"and remove it from memory."
msgstr ""

#: ../../docs/tutorials/plugins/editor/making_main_screen_plugins.rst:266
msgid ""
"The ``_make_visible()`` function is overridden to hide or show the main "
"panel as needed. This function is automatically called by the editor when "
"the user clicks on the main viewport buttons at the top of the editor."
msgstr ""

#: ../../docs/tutorials/plugins/editor/making_main_screen_plugins.rst:270
msgid ""
"The ``_get_plugin_name()`` and ``_get_plugin_icon()`` functions control the "
"displayed name and icon for the plugin's main viewport button."
msgstr ""

#: ../../docs/tutorials/plugins/editor/making_main_screen_plugins.rst:273
msgid ""
"Another function you can add is the ``handles()`` function, which allows you "
"to handle a node type, automatically focusing the main screen when the type "
"is selected. This is similar to how clicking on a 3D node will automatically "
"switch to the 3D viewport."
msgstr ""

#: ../../docs/tutorials/plugins/editor/making_main_screen_plugins.rst:279
msgid "Try the plugin"
msgstr ""

#: ../../docs/tutorials/plugins/editor/making_main_screen_plugins.rst:281
msgid ""
"Activate the plugin in the Project Settings. You'll observe a new button "
"next to 2D, 3D, Script above the main viewport. Clicking it will take you to "
"your new main screen plugin, and the button in the middle will print text."
msgstr ""

#: ../../docs/tutorials/plugins/editor/making_main_screen_plugins.rst:285
msgid ""
"If you would like to try a finished version of this plugin, check out the "
"plugin demos here: https://github.com/godotengine/godot-demo-projects/tree/"
"master/plugins"
msgstr ""

#: ../../docs/tutorials/plugins/editor/making_main_screen_plugins.rst:289
msgid ""
"If you would like to see a more complete example of what main screen plugins "
"are capable of, check out the 2.5D demo projects here: https://github.com/"
"godotengine/godot-demo-projects/tree/master/misc/2.5d"
msgstr ""

#: ../../docs/tutorials/plugins/editor/import_plugins.rst:6
msgid "Import plugins"
msgstr ""

#: ../../docs/tutorials/plugins/editor/import_plugins.rst:8
msgid ""
"This tutorial assumes you already know how to make generic plugins. If in "
"doubt, refer to the :ref:`doc_making_plugins` page. This also assumes you "
"are acquainted with Godot's import system."
msgstr ""

#: ../../docs/tutorials/plugins/editor/import_plugins.rst:15
msgid ""
"An import plugin is a special type of editor tool that allows custom "
"resources to be imported by Godot and be treated as first-class resources. "
"The editor itself comes bundled with a lot of import plugins to handle the "
"common resources like PNG images, Collada and glTF models, Ogg Vorbis "
"sounds, and many more."
msgstr ""

#: ../../docs/tutorials/plugins/editor/import_plugins.rst:20
msgid ""
"This tutorial shows how to create an import plugin to load a custom text "
"file as a material resource. This text file will contain three numeric "
"values separated by comma, which represents the three channels of a color, "
"and the resulting color will be used as the albedo (main color) of the "
"imported material. In this example it contains the pure blue color (zero "
"red, zero green, and full blue):"
msgstr ""

#: ../../docs/tutorials/plugins/editor/import_plugins.rst:34
msgid ""
"First we need a generic plugin that will handle the initialization and "
"destruction of our import plugin. Let's add the ``plugin.cfg`` file first:"
msgstr ""

#: ../../docs/tutorials/plugins/editor/import_plugins.rst:47
msgid ""
"Then we need the ``material_import.gd`` file to add and remove the import "
"plugin when needed:"
msgstr ""

#: ../../docs/tutorials/plugins/editor/import_plugins.rst:69
msgid ""
"When this plugin is activated, it will create a new instance of the import "
"plugin (which we'll soon make) and add it to the editor using the :ref:"
"`add_import_plugin() <class_EditorPlugin_method_add_import_plugin>` method. "
"We store a reference to it in a class member ``import_plugin`` so we can "
"refer to it later when removing it. The :ref:`remove_import_plugin() "
"<class_EditorPlugin_method_remove_import_plugin>` method is called when the "
"plugin is deactivated to clean up the memory and let the editor know the "
"import plugin isn't available anymore."
msgstr ""

#: ../../docs/tutorials/plugins/editor/import_plugins.rst:78
msgid ""
"Note that the import plugin is a reference type, so it doesn't need to be "
"explicitly released from memory with the ``free()`` function. It will be "
"released automatically by the engine when it goes out of scope."
msgstr ""

#: ../../docs/tutorials/plugins/editor/import_plugins.rst:83
msgid "The EditorImportPlugin class"
msgstr ""

#: ../../docs/tutorials/plugins/editor/import_plugins.rst:85
msgid ""
"The main character of the show is the :ref:`EditorImportPlugin class "
"<class_EditorImportPlugin>`. It is responsible for implementing the methods "
"that are called by Godot when it needs to know how to deal with files."
msgstr ""

#: ../../docs/tutorials/plugins/editor/import_plugins.rst:90
msgid "Let's begin to code our plugin, one method at time:"
msgstr ""

#: ../../docs/tutorials/plugins/editor/import_plugins.rst:102
msgid ""
"The first method is the :ref:"
"`_get_importer_name()<class_EditorImportPlugin_private_method__get_importer_name>`. "
"This is a unique name for your plugin that is used by Godot to know which "
"import was used in a certain file. When the files needs to be reimported, "
"the editor will know which plugin to call."
msgstr ""

#: ../../docs/tutorials/plugins/editor/import_plugins.rst:113
msgid ""
"The :ref:"
"`_get_visible_name()<class_EditorImportPlugin_private_method__get_visible_name>` "
"method is responsible for returning the name of the type it imports and it "
"will be shown to the user in the Import dock."
msgstr ""

#: ../../docs/tutorials/plugins/editor/import_plugins.rst:117
msgid ""
"You should choose this name as a continuation to \"Import as\", e.g. "
"*\"Import as Silly Material\"*. You can name it whatever you want but we "
"recommend a descriptive name for your plugin."
msgstr ""

#: ../../docs/tutorials/plugins/editor/import_plugins.rst:126
msgid ""
"Godot's import system detects file types by their extension. In the :ref:"
"`_get_recognized_extensions()<class_EditorImportPlugin_private_method__get_recognized_extensions>` "
"method you return an array of strings to represent each extension that this "
"plugin can understand. If an extension is recognized by more than one "
"plugin, the user can select which one to use when importing the files."
msgstr ""

#: ../../docs/tutorials/plugins/editor/import_plugins.rst:132
msgid ""
"Common extensions like ``.json`` and ``.txt`` might be used by many plugins. "
"Also, there could be files in the project that are just data for the game "
"and should not be imported. You have to be careful when importing to "
"validate the data. Never expect the file to be well-formed."
msgstr ""

#: ../../docs/tutorials/plugins/editor/import_plugins.rst:142
msgid ""
"The imported files are saved in the ``.import`` folder at the project's "
"root. Their extension should match the type of resource you are importing, "
"but since Godot can't tell what you'll use (because there might be multiple "
"valid extensions for the same resource), you need to declare what will be "
"used in the import."
msgstr ""

#: ../../docs/tutorials/plugins/editor/import_plugins.rst:148
msgid ""
"Since we're importing a Material, we'll use the special extension for such "
"resource types. If you are importing a scene, you can use ``scn``. Generic "
"resources can use the ``res`` extension. However, this is not enforced in "
"any way by the engine."
msgstr ""

#: ../../docs/tutorials/plugins/editor/import_plugins.rst:158
msgid ""
"The imported resource has a specific type, so the editor can know which "
"property slot it belongs to. This allows drag and drop from the FileSystem "
"dock to a property in the Inspector."
msgstr ""

#: ../../docs/tutorials/plugins/editor/import_plugins.rst:162
msgid ""
"In our case it's a :ref:`class_StandardMaterial3D`, which can be applied to "
"3D objects."
msgstr ""

#: ../../docs/tutorials/plugins/editor/import_plugins.rst:165
msgid ""
"If you need to import different types from the same extension, you have to "
"create multiple import plugins. You can abstract the import code on another "
"file to avoid duplication in this regard."
msgstr ""

#: ../../docs/tutorials/plugins/editor/import_plugins.rst:170
msgid "Options and presets"
msgstr ""

#: ../../docs/tutorials/plugins/editor/import_plugins.rst:172
msgid ""
"Your plugin can provide different options to allow the user to control how "
"the resource will be imported. If a set of selected options is common, you "
"can also create different presets to make it easier for the user. The "
"following image shows how the options will appear in the editor:"
msgstr ""

#: ../../docs/tutorials/plugins/editor/import_plugins.rst:179
msgid ""
"Since there might be many presets and they are identified with a number, "
"it's a good practice to use an enum so you can refer to them using names."
msgstr ""

#: ../../docs/tutorials/plugins/editor/import_plugins.rst:193
msgid ""
"Now that the enum is defined, let's keep looking at the methods of an import "
"plugin:"
msgstr ""

#: ../../docs/tutorials/plugins/editor/import_plugins.rst:201
msgid ""
"The :ref:`_get_preset_count() "
"<class_EditorImportPlugin_private_method__get_preset_count>` method returns "
"the amount of presets that this plugins defines. We only have one preset "
"now, but we can make this method future-proof by returning the size of our "
"``Presets`` enumeration."
msgstr ""

#: ../../docs/tutorials/plugins/editor/import_plugins.rst:216
msgid ""
"Here we have the :ref:`_get_preset_name() "
"<class_EditorImportPlugin_private_method__get_preset_name>` method, which "
"gives names to the presets as they will be presented to the user, so be sure "
"to use short and clear names."
msgstr ""

#: ../../docs/tutorials/plugins/editor/import_plugins.rst:221
msgid ""
"We can use the ``match`` statement here to make the code more structured. "
"This way it's easy to add new presets in the future. We use the catch all "
"pattern to return something too. Although Godot won't ask for presets beyond "
"the preset count you defined, it's always better to be on the safe side."
msgstr ""

#: ../../docs/tutorials/plugins/editor/import_plugins.rst:226
msgid ""
"If you have only one preset you could simply return its name directly, but "
"if you do this you have to be careful when you add more presets."
msgstr ""

#: ../../docs/tutorials/plugins/editor/import_plugins.rst:241
msgid ""
"This is the method which defines the available options. :ref:"
"`_get_import_options() "
"<class_EditorImportPlugin_private_method__get_import_options>` returns an "
"array of dictionaries, and each dictionary contains a few keys that are "
"checked to customize the option as its shown to the user. The following "
"table shows the possible keys:"
msgstr ""

#: ../../docs/tutorials/plugins/editor/import_plugins.rst:248
msgid "Key"
msgstr ""

#: ../../docs/tutorials/plugins/editor/import_plugins.rst:250
msgid "``name``"
msgstr ""

#: ../../docs/tutorials/plugins/editor/import_plugins.rst:250
#: ../../docs/tutorials/plugins/editor/import_plugins.rst:256
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:353
#: ../../docs/contributing/development/core_and_modules/core_types.rst:174
msgid "String"
msgstr ""

#: ../../docs/tutorials/plugins/editor/import_plugins.rst:250
msgid ""
"The name of the option. When showed, underscores become spaces and first "
"letters are capitalized."
msgstr ""

#: ../../docs/tutorials/plugins/editor/import_plugins.rst:252
msgid "``default_value``"
msgstr ""

#: ../../docs/tutorials/plugins/editor/import_plugins.rst:252
msgid "Any"
msgstr ""

#: ../../docs/tutorials/plugins/editor/import_plugins.rst:252
msgid "The default value of the option for this preset."
msgstr ""

#: ../../docs/tutorials/plugins/editor/import_plugins.rst:254
msgid "``property_hint``"
msgstr ""

#: ../../docs/tutorials/plugins/editor/import_plugins.rst:254
#: ../../docs/tutorials/plugins/editor/import_plugins.rst:258
#: ../../docs/tutorials/scripting/gdscript/gdscript_documentation_comments.rst:80
msgid "Enum value"
msgstr ""

#: ../../docs/tutorials/plugins/editor/import_plugins.rst:254
msgid ""
"One of the :ref:`PropertyHint <enum_@GlobalScope_PropertyHint>` values to "
"use as hint."
msgstr ""

#: ../../docs/tutorials/plugins/editor/import_plugins.rst:256
msgid "``hint_string``"
msgstr ""

#: ../../docs/tutorials/plugins/editor/import_plugins.rst:256
msgid ""
"The hint text of the property. The same as you'd add in the ``export`` "
"statement in GDScript."
msgstr ""

#: ../../docs/tutorials/plugins/editor/import_plugins.rst:258
msgid "``usage``"
msgstr ""

#: ../../docs/tutorials/plugins/editor/import_plugins.rst:258
msgid ""
"One of the :ref:`PropertyUsageFlags <enum_@GlobalScope_PropertyUsageFlags>` "
"values to define the usage."
msgstr ""

#: ../../docs/tutorials/plugins/editor/import_plugins.rst:261
msgid ""
"The ``name`` and ``default_value`` keys are **mandatory**, the rest are "
"optional."
msgstr ""

#: ../../docs/tutorials/plugins/editor/import_plugins.rst:263
msgid ""
"Note that the ``_get_import_options`` method receives the preset number, so "
"you can configure the options for each different preset (especially the "
"default value). In this example we use the ``match`` statement, but if you "
"have lots of options and the presets only change the value you may want to "
"create the array of options first and then change it based on the preset."
msgstr ""

#: ../../docs/tutorials/plugins/editor/import_plugins.rst:269
msgid ""
"The ``_get_import_options`` method is called even if you don't define "
"presets (by making ``_get_preset_count`` return zero). You have to return an "
"array even it's empty, otherwise you can get errors."
msgstr ""

#: ../../docs/tutorials/plugins/editor/import_plugins.rst:279
msgid ""
"For the :ref:`_get_option_visibility() "
"<class_EditorImportPlugin_private_method__get_option_visibility>` method, we "
"simply return ``true`` because all of our options (i.e. the single one we "
"defined) are visible all the time."
msgstr ""

#: ../../docs/tutorials/plugins/editor/import_plugins.rst:284
msgid ""
"If you need to make certain option visible only if another is set with a "
"certain value, you can add the logic in this method."
msgstr ""

#: ../../docs/tutorials/plugins/editor/import_plugins.rst:288
msgid "The ``import`` method"
msgstr ""

#: ../../docs/tutorials/plugins/editor/import_plugins.rst:290
msgid ""
"The heavy part of the process, responsible for converting the files into "
"resources, is covered by the :ref:`_import() "
"<class_EditorImportPlugin_private_method__import>` method. Our sample code "
"is a bit long, so let's split in a few parts:"
msgstr ""

#: ../../docs/tutorials/plugins/editor/import_plugins.rst:303
msgid ""
"The first part of our import method opens and reads the source file. We use "
"the :ref:`FileAccess <class_FileAccess>` class to do that, passing the "
"``source_file`` parameter which is provided by the editor."
msgstr ""

#: ../../docs/tutorials/plugins/editor/import_plugins.rst:307
msgid ""
"If there's an error when opening the file, we return it to let the editor "
"know that the import wasn't successful."
msgstr ""

#: ../../docs/tutorials/plugins/editor/import_plugins.rst:322
msgid ""
"This code takes the line of the file it read before and splits it in pieces "
"that are separated by a comma. If there are more or less than the three "
"values, it considers the file invalid and reports an error."
msgstr ""

#: ../../docs/tutorials/plugins/editor/import_plugins.rst:326
msgid ""
"Then it creates a new :ref:`Color <class_Color>` variable and sets its "
"values according to the input file. If the ``use_red_anyway`` option is "
"enabled, then it sets the color as a pure red instead."
msgstr ""

#: ../../docs/tutorials/plugins/editor/import_plugins.rst:335
msgid ""
"This part makes a new :ref:`StandardMaterial3D <class_StandardMaterial3D>` "
"that is the imported resource. We create a new instance of it and then set "
"its albedo color as the value we got before."
msgstr ""

#: ../../docs/tutorials/plugins/editor/import_plugins.rst:343
msgid ""
"This is the last part and quite an important one, because here we save the "
"made resource to the disk. The path of the saved file is generated and "
"informed by the editor via the ``save_path`` parameter. Note that this comes "
"**without** the extension, so we add it using :ref:`string formatting "
"<doc_gdscript_printf>`. For this we call the ``_get_save_extension`` method "
"that we defined earlier, so we can be sure that they won't get out of sync."
msgstr ""

#: ../../docs/tutorials/plugins/editor/import_plugins.rst:350
msgid ""
"We also return the result from the :ref:`ResourceSaver.save() "
"<class_ResourceSaver_method_save>` method, so if there's an error in this "
"step, the editor will know about it."
msgstr ""

#: ../../docs/tutorials/plugins/editor/import_plugins.rst:355
msgid "Platform variants and generated files"
msgstr ""

#: ../../docs/tutorials/plugins/editor/import_plugins.rst:357
msgid ""
"You may have noticed that our plugin ignored two arguments of the ``import`` "
"method. Those are *return arguments* (hence the ``r`` at the beginning of "
"their name), which means that the editor will read from them after calling "
"your import method. Both of them are arrays that you can fill with "
"information."
msgstr ""

#: ../../docs/tutorials/plugins/editor/import_plugins.rst:362
msgid ""
"The ``r_platform_variants`` argument is used if you need to import the "
"resource differently depending on the target platform. While it's called "
"*platform* variants, it is based on the presence of :ref:`feature tags "
"<doc_feature_tags>`, so even the same platform can have multiple variants "
"depending on the setup."
msgstr ""

#: ../../docs/tutorials/plugins/editor/import_plugins.rst:367
msgid ""
"To import a platform variant, you need to save it with the feature tag "
"before the extension, and then push the tag to the ``r_platform_variants`` "
"array so the editor can know that you did."
msgstr ""

#: ../../docs/tutorials/plugins/editor/import_plugins.rst:371
msgid ""
"For example, let's say we save a different material for a mobile platform. "
"We would need to do something like the following:"
msgstr ""

#: ../../docs/tutorials/plugins/editor/import_plugins.rst:379
msgid ""
"The ``r_gen_files`` argument is meant for extra files that are generated "
"during your import process and need to be kept. The editor will look at it "
"to understand the dependencies and make sure the extra file is not "
"inadvertently deleted."
msgstr ""

#: ../../docs/tutorials/plugins/editor/import_plugins.rst:384
msgid ""
"This is also an array and should be filled with full paths of the files you "
"save. As an example, let's create another material for the next pass and "
"save it in a different file:"
msgstr ""

#: ../../docs/tutorials/plugins/editor/import_plugins.rst:400
msgid "Trying the plugin"
msgstr ""

#: ../../docs/tutorials/plugins/editor/import_plugins.rst:402
msgid ""
"This has been theoretical, but now that the import plugin is done, let's "
"test it. Make sure you created the sample file (with the contents described "
"in the introduction section) and save it as ``test.mtxt``. Then activate the "
"plugin in the Project Settings."
msgstr ""

#: ../../docs/tutorials/plugins/editor/import_plugins.rst:407
msgid ""
"If everything goes well, the import plugin is added to the editor and the "
"file system is scanned, making the custom resource appear on the FileSystem "
"dock. If you select it and focus the Import dock, you can see the only "
"option to select there."
msgstr ""

#: ../../docs/tutorials/plugins/editor/import_plugins.rst:412
msgid ""
"Create a MeshInstance3D node in the scene, and for its Mesh property set up "
"a new SphereMesh. Unfold the Material section in the Inspector and then drag "
"the file from the FileSystem dock to the material property. The object will "
"update in the viewport with the blue color of the imported material."
msgstr ""

#: ../../docs/tutorials/plugins/editor/import_plugins.rst:419
msgid ""
"Go to Import dock, enable the \"Use Red Anyway\" option, and click on "
"\"Reimport\". This will update the imported material and should "
"automatically update the view showing the red color instead."
msgstr ""

#: ../../docs/tutorials/plugins/editor/import_plugins.rst:423
msgid ""
"And that's it! Your first import plugin is done! Now get creative and make "
"plugins for your own beloved formats. This can be quite useful to write your "
"data in a custom format and then use it in Godot as if they were native "
"resources. This shows how the import system is powerful and extendable."
msgstr ""

#: ../../docs/tutorials/plugins/editor/3d_gizmos.rst:6
#, fuzzy
msgid "3D gizmo plugins"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/plugins/editor/3d_gizmos.rst:11
msgid ""
"3D gizmo plugins are used by the editor and custom plugins to define the "
"gizmos attached to any kind of Node3D node."
msgstr ""

#: ../../docs/tutorials/plugins/editor/3d_gizmos.rst:14
msgid ""
"This tutorial shows the two main approaches to defining your own custom "
"gizmos. The first option works well for simple gizmos and creates less "
"clutter in your plugin structure, and the second one will let you store some "
"per-gizmo data."
msgstr ""

#: ../../docs/tutorials/plugins/editor/3d_gizmos.rst:18
msgid ""
"This tutorial assumes you already know how to make generic plugins. If in "
"doubt, refer to the :ref:`doc_making_plugins` page."
msgstr ""

#: ../../docs/tutorials/plugins/editor/3d_gizmos.rst:22
msgid "The EditorNode3DGizmoPlugin"
msgstr ""

#: ../../docs/tutorials/plugins/editor/3d_gizmos.rst:24
msgid ""
"Regardless of the approach we choose, we will need to create a new :ref:"
"`EditorNode3DGizmoPlugin <class_EditorNode3DGizmoPlugin>`. This will allow "
"us to set a name for the new gizmo type and define other behaviors such as "
"whether the gizmo can be hidden or not."
msgstr ""

#: ../../docs/tutorials/plugins/editor/3d_gizmos.rst:29
msgid "This would be a basic setup:"
msgstr ""

#: ../../docs/tutorials/plugins/editor/3d_gizmos.rst:61
msgid ""
"For simple gizmos, inheriting :ref:`EditorNode3DGizmoPlugin "
"<class_EditorNode3DGizmoPlugin>` is enough. If you want to store some per-"
"gizmo data or you are porting a Godot 3.0 gizmo to 3.1+, you should go with "
"the second approach."
msgstr ""

#: ../../docs/tutorials/plugins/editor/3d_gizmos.rst:67
msgid "Simple approach"
msgstr ""

#: ../../docs/tutorials/plugins/editor/3d_gizmos.rst:69
msgid ""
"The first step is to, in our custom gizmo plugin, override the :ref:"
"`_has_gizmo()<class_EditorNode3DGizmoPlugin_private_method__has_gizmo>` "
"method so that it returns ``true`` when the node parameter is of our target "
"type."
msgstr ""

#: ../../docs/tutorials/plugins/editor/3d_gizmos.rst:83
msgid ""
"Then we can override methods like :ref:"
"`_redraw()<class_EditorNode3DGizmoPlugin_private_method__redraw>` or all the "
"handle related ones."
msgstr ""

#: ../../docs/tutorials/plugins/editor/3d_gizmos.rst:117
msgid ""
"Note that we created a material in the `_init` method, and retrieved it in "
"the `_redraw` method using :ref:"
"`get_material()<class_EditorNode3DGizmoPlugin_method_get_material>`. This "
"method retrieves one of the material's variants depending on the state of "
"the gizmo (selected and/or editable)."
msgstr ""

#: ../../docs/tutorials/plugins/editor/3d_gizmos.rst:122
msgid "So the final plugin would look somewhat like this:"
msgstr ""

#: ../../docs/tutorials/plugins/editor/3d_gizmos.rst:163
msgid ""
"Note that we just added some handles in the `_redraw` method, but we still "
"need to implement the rest of handle-related callbacks in :ref:"
"`EditorNode3DGizmoPlugin <class_EditorNode3DGizmoPlugin>` to get properly "
"working handles."
msgstr ""

#: ../../docs/tutorials/plugins/editor/3d_gizmos.rst:168
msgid "Alternative approach"
msgstr ""

#: ../../docs/tutorials/plugins/editor/3d_gizmos.rst:170
msgid ""
"In some cases we want to provide our own implementation of :ref:"
"`EditorNode3DGizmo<class_EditorNode3DGizmo>`, maybe because we want to have "
"some state stored in each gizmo or because we are porting an old gizmo "
"plugin and we don't want to go through the rewriting process."
msgstr ""

#: ../../docs/tutorials/plugins/editor/3d_gizmos.rst:174
msgid ""
"In these cases all we need to do is, in our new gizmo plugin, override :ref:"
"`_create_gizmo()<class_EditorNode3DGizmoPlugin_private_method__create_gizmo>`, "
"so it returns our custom gizmo implementation for the Node3D nodes we want "
"to target."
msgstr ""

#: ../../docs/tutorials/plugins/editor/3d_gizmos.rst:199
msgid ""
"This way all the gizmo logic and drawing methods can be implemented in a new "
"class extending :ref:`EditorNode3DGizmo<class_EditorNode3DGizmo>`, like so:"
msgstr ""

#: ../../docs/tutorials/plugins/editor/3d_gizmos.rst:237
msgid ""
"Note that we just added some handles in the `_redraw` method, but we still "
"need to implement the rest of handle-related callbacks in :ref:"
"`EditorNode3DGizmo<class_EditorNode3DGizmo>` to get properly working handles."
msgstr ""

#: ../../docs/tutorials/plugins/editor/inspector_plugins.rst:4
#, fuzzy
msgid "Inspector plugins"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/plugins/editor/inspector_plugins.rst:6
msgid ""
"The inspector dock allows you to create custom widgets to edit properties "
"through plugins. This can be beneficial when working with custom datatypes "
"and resources, although you can use the feature to change the inspector "
"widgets for built-in types. You can design custom controls for specific "
"properties, entire objects, and even separate controls associated with "
"particular datatypes."
msgstr ""

#: ../../docs/tutorials/plugins/editor/inspector_plugins.rst:12
msgid ""
"This guide explains how to use the :ref:`class_EditorInspectorPlugin` and :"
"ref:`class_EditorProperty` classes to create a custom interface for "
"integers, replacing the default behavior with a button that generates random "
"values between 0 and 99."
msgstr ""

#: ../../docs/tutorials/plugins/editor/inspector_plugins.rst:20
msgid "The default behavior on the left and the end result on the right."
msgstr ""

#: ../../docs/tutorials/plugins/editor/inspector_plugins.rst:24
#, fuzzy
msgid "Setting up your plugin"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/plugins/editor/inspector_plugins.rst:26
msgid "Create a new empty plugin to get started."
msgstr ""

#: ../../docs/tutorials/plugins/editor/inspector_plugins.rst:28
msgid "See :ref:`doc_making_plugins` guide to set up your new plugin."
msgstr ""

#: ../../docs/tutorials/plugins/editor/inspector_plugins.rst:30
msgid ""
"Let's assume you've called your plugin folder ``my_inspector_plugin``. If "
"so, you should end up with a new ``addons/my_inspector_plugin`` folder that "
"contains two files: ``plugin.cfg`` and ``plugin.gd``."
msgstr ""

#: ../../docs/tutorials/plugins/editor/inspector_plugins.rst:34
msgid ""
"As before, ``plugin.gd`` is a script extending :ref:`class_EditorPlugin` and "
"you need to introduce new code for its ``_enter_tree`` and ``_exit_tree`` "
"methods. To set up your inspector plugin, you must load its script, then "
"create and add the instance by calling ``add_inspector_plugin()``. If the "
"plugin is disabled, you should remove the instance you have added by calling "
"``remove_inspector_plugin()``."
msgstr ""

#: ../../docs/tutorials/plugins/editor/inspector_plugins.rst:41
msgid ""
"Here, you are loading a script and not a packed scene. Therefore you should "
"use ``new()`` instead of ``instance()``."
msgstr ""

#: ../../docs/tutorials/plugins/editor/inspector_plugins.rst:88
#, fuzzy
msgid "Interacting with the inspector"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/plugins/editor/inspector_plugins.rst:90
msgid ""
"To interact with the inspector dock, your ``my_inspector_plugin.gd`` script "
"must extend the :ref:`class_EditorInspectorPlugin` class. This class "
"provides several virtual methods that affect how the inspector handles "
"properties."
msgstr ""

#: ../../docs/tutorials/plugins/editor/inspector_plugins.rst:94
msgid ""
"To have any effect at all, the script must implement the ``_can_handle()`` "
"method. This function is called for each edited :ref:`class_Object` and must "
"return ``true`` if this plugin should handle the object or its properties."
msgstr ""

#: ../../docs/tutorials/plugins/editor/inspector_plugins.rst:98
msgid "This includes any :ref:`class_Resource` attached to the object."
msgstr ""

#: ../../docs/tutorials/plugins/editor/inspector_plugins.rst:100
msgid ""
"You can implement four other methods to add controls to the inspector at "
"specific positions. The ``_parse_begin()`` and ``_parse_end()`` methods are "
"called only once at the beginning and the end of parsing for each object, "
"respectively. They can add controls at the top or bottom of the inspector "
"layout by calling ``add_custom_control()``."
msgstr ""

#: ../../docs/tutorials/plugins/editor/inspector_plugins.rst:106
msgid ""
"As the editor parses the object, it calls the ``_parse_category()`` and "
"``_parse_property()`` methods. There, in addition to "
"``add_custom_control()``, you can call both ``add_property_editor()`` and "
"``add_property_editor_for_multiple_properties()``. Use these last two "
"methods to specifically add :ref:`class_EditorProperty`-based controls."
msgstr ""

#: ../../docs/tutorials/plugins/editor/inspector_plugins.rst:173
#, fuzzy
msgid "Adding an interface to edit properties"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/plugins/editor/inspector_plugins.rst:175
msgid ""
"The :ref:`class_EditorProperty` class is a special type of :ref:"
"`class_Control` that can interact with the inspector dock's edited objects. "
"It doesn't display anything but can house any other control nodes, including "
"complex scenes."
msgstr ""

#: ../../docs/tutorials/plugins/editor/inspector_plugins.rst:179
msgid ""
"There are three essential parts to the script extending :ref:"
"`class_EditorProperty`:"
msgstr ""

#: ../../docs/tutorials/plugins/editor/inspector_plugins.rst:182
msgid ""
"You must define the ``_init()`` method to set up the control nodes' "
"structure."
msgstr ""

#: ../../docs/tutorials/plugins/editor/inspector_plugins.rst:185
msgid ""
"You should implement the ``_update_property()`` to handle changes to the "
"data from the outside."
msgstr ""

#: ../../docs/tutorials/plugins/editor/inspector_plugins.rst:188
msgid ""
"A signal must be emitted at some point to inform the inspector that the "
"control has changed the property using ``emit_changed``."
msgstr ""

#: ../../docs/tutorials/plugins/editor/inspector_plugins.rst:191
msgid ""
"You can display your custom widget in two ways. Use just the default "
"``add_child()`` method to display it to the right of the property name, and "
"use ``add_child()`` followed by ``set_bottom_editor()`` to position it below "
"the name."
msgstr ""

#: ../../docs/tutorials/plugins/editor/inspector_plugins.rst:311
msgid ""
"Using the example code above you should be able to make a custom widget that "
"replaces the default :ref:`class_SpinBox` control for integers with a :ref:"
"`class_Button` that generates random values."
msgstr ""

#: ../../docs/tutorials/plugins/editor/visual_shader_plugins.rst:4
#, fuzzy
msgid "Visual Shader plugins"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/plugins/editor/visual_shader_plugins.rst:6
msgid ""
"Visual Shader plugins are used to create custom :ref:`class_VisualShader` "
"nodes in GDScript."
msgstr ""

#: ../../docs/tutorials/plugins/editor/visual_shader_plugins.rst:9
msgid ""
"The creation process is different from usual editor plugins. You do not need "
"to create a ``plugin.cfg`` file to register it; instead, create and save a "
"script file and it will be ready to use, provided the custom node is "
"registered with ``class_name``."
msgstr ""

#: ../../docs/tutorials/plugins/editor/visual_shader_plugins.rst:14
msgid ""
"This short tutorial will explain how to make a Perlin-3D noise node "
"(original code from this `GPU noise shaders plugin <https://github.com/curly-"
"brace/Godot-3.0-Noise-Shaders/blob/master/assets/gpu_noise_shaders/"
"classic_perlin3d.tres>`_."
msgstr ""

#: ../../docs/tutorials/plugins/editor/visual_shader_plugins.rst:18
msgid ""
"Create a Sprite2D and assign a :ref:`class_ShaderMaterial` to its material "
"slot:"
msgstr ""

#: ../../docs/tutorials/plugins/editor/visual_shader_plugins.rst:22
msgid "Assign :ref:`class_VisualShader` to the shader slot of the material:"
msgstr ""

#: ../../docs/tutorials/plugins/editor/visual_shader_plugins.rst:26
msgid ""
"Don't forget to change its mode to \"CanvasItem\" (if you are using a "
"Sprite2D):"
msgstr ""

#: ../../docs/tutorials/plugins/editor/visual_shader_plugins.rst:30
msgid ""
"Create a script which derives from :ref:`class_VisualShaderNodeCustom`. This "
"is all you need to initialize your plugin."
msgstr ""

#: ../../docs/tutorials/plugins/editor/visual_shader_plugins.rst:197
msgid ""
"Save it and open the Visual Shader. You should see your new node type within "
"the member's dialog under the Addons category (if you can't see your new "
"node, try restarting the editor):"
msgstr ""

#: ../../docs/tutorials/plugins/editor/visual_shader_plugins.rst:201
msgid "Place it on a graph and connect the required ports:"
msgstr ""

#: ../../docs/tutorials/plugins/editor/visual_shader_plugins.rst:205
msgid ""
"That is everything you need to do, as you can see it is easy to create your "
"own custom VisualShader nodes!"
msgstr ""

#: ../../docs/tutorials/plugins/running_code_in_the_editor.rst:4
msgid "Running code in the editor"
msgstr ""

#: ../../docs/tutorials/plugins/running_code_in_the_editor.rst:7
msgid "What is ``@tool``?"
msgstr ""

#: ../../docs/tutorials/plugins/running_code_in_the_editor.rst:9
msgid ""
"``@tool`` is a powerful line of code that, when added at the top of your "
"script, makes it execute in the editor. You can also decide which parts of "
"the script execute in the editor, which in game, and which in both."
msgstr ""

#: ../../docs/tutorials/plugins/running_code_in_the_editor.rst:13
msgid ""
"You can use it for doing many things, but it is mostly useful in level "
"design for visually presenting things that are hard to predict ourselves. "
"Here are some use cases:"
msgstr ""

#: ../../docs/tutorials/plugins/running_code_in_the_editor.rst:17
msgid ""
"If you have a cannon that shoots cannonballs affected by physics (gravity), "
"you can draw the cannonball's trajectory in the editor, making level design "
"a lot easier."
msgstr ""

#: ../../docs/tutorials/plugins/running_code_in_the_editor.rst:20
msgid ""
"If you have jumppads with varying jump heights, you can draw the maximum "
"jump height a player would reach if it jumped on one, also making level "
"design easier."
msgstr ""

#: ../../docs/tutorials/plugins/running_code_in_the_editor.rst:23
msgid ""
"If your player doesn't use a sprite, but draws itself using code, you can "
"make that drawing code execute in the editor to see your player."
msgstr ""

#: ../../docs/tutorials/plugins/running_code_in_the_editor.rst:28
msgid ""
"``@tool`` scripts run inside the editor, and let you access the scene tree "
"of the currently edited scene. This is a powerful feature which also comes "
"with caveats, as the editor does not include protections for potential "
"misuse of ``@tool`` scripts. Be **extremely** cautious when manipulating the "
"scene tree, especially via :ref:`Node."
"queue_free<class_Node_method_queue_free>`, as it can cause crashes if you "
"free a node while the editor runs logic involving it."
msgstr ""

#: ../../docs/tutorials/plugins/running_code_in_the_editor.rst:37
msgid "How to use ``@tool``"
msgstr ""

#: ../../docs/tutorials/plugins/running_code_in_the_editor.rst:39
msgid ""
"To turn a script into a tool, add the ``@tool`` annotation at the top of "
"your code."
msgstr ""

#: ../../docs/tutorials/plugins/running_code_in_the_editor.rst:41
msgid ""
"To check if you are currently in the editor, use: ``Engine."
"is_editor_hint()``."
msgstr ""

#: ../../docs/tutorials/plugins/running_code_in_the_editor.rst:43
msgid "For example, if you want to execute some code only in the editor, use:"
msgstr ""

#: ../../docs/tutorials/plugins/running_code_in_the_editor.rst:58
msgid ""
"On the other hand, if you want to execute code only in game, simply negate "
"the same statement:"
msgstr ""

#: ../../docs/tutorials/plugins/running_code_in_the_editor.rst:74
msgid ""
"Pieces of code that do not have either of the 2 conditions above will run "
"both in-editor and in-game."
msgstr ""

#: ../../docs/tutorials/plugins/running_code_in_the_editor.rst:77
msgid "Here is how a ``_process()`` function might look for you:"
msgstr ""

#: ../../docs/tutorials/plugins/running_code_in_the_editor.rst:110
msgid ""
"Modifications in the editor are permanent. For example, in the following "
"case, when we remove the script, the node will keep its rotation. Be careful "
"to avoid making unwanted modifications."
msgstr ""

#: ../../docs/tutorials/plugins/running_code_in_the_editor.rst:116
msgid ""
"Extending a ``@tool`` script does not automatically make the extending "
"script a ``@tool``. Omitting ``@tool`` from the extending script will "
"disable tool behavior from the super class. Therefore the extending script "
"should also specify the ``@tool`` annotation."
msgstr ""

#: ../../docs/tutorials/plugins/running_code_in_the_editor.rst:122
msgid "Try ``@tool`` out"
msgstr ""

#: ../../docs/tutorials/plugins/running_code_in_the_editor.rst:124
msgid ""
"Add a ``Sprite2D`` node to your scene and set the texture to Godot icon. "
"Attach and open a script, and change it to this:"
msgstr ""

#: ../../docs/tutorials/plugins/running_code_in_the_editor.rst:149
msgid ""
"Save the script and return to the editor. You should now see your object "
"rotate. If you run the game, it will also rotate."
msgstr ""

#: ../../docs/tutorials/plugins/running_code_in_the_editor.rst:156
msgid ""
"If you don't see the changes, reload the scene (close it and open it again)."
msgstr ""

#: ../../docs/tutorials/plugins/running_code_in_the_editor.rst:158
msgid ""
"Now let's choose which code runs when. Modify your ``_process()`` function "
"to look like this:"
msgstr ""

#: ../../docs/tutorials/plugins/running_code_in_the_editor.rst:184
msgid ""
"Save the script. Now the object will spin clockwise in the editor, but if "
"you run the game, it will spin counter-clockwise."
msgstr ""

#: ../../docs/tutorials/plugins/running_code_in_the_editor.rst:188
msgid "Editing variables"
msgstr ""

#: ../../docs/tutorials/plugins/running_code_in_the_editor.rst:190
msgid ""
"Add and export a variable speed to the script. To update the speed and also "
"reset the rotation angle add a setter ``set(new_speed)`` which is executed "
"with the input from the inspector. Modify ``_process()`` to include the "
"rotation speed."
msgstr ""

#: ../../docs/tutorials/plugins/running_code_in_the_editor.rst:240
msgid ""
"Code from other nodes doesn't run in the editor. Your access to other nodes "
"is limited. You can access the tree and nodes, and their default properties, "
"but you can't access user variables. If you want to do so, other nodes have "
"to run in the editor too. Autoload nodes cannot be accessed in the editor at "
"all."
msgstr ""

#: ../../docs/tutorials/plugins/running_code_in_the_editor.rst:247
#, fuzzy
msgid "Reporting node configuration warnings"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/plugins/running_code_in_the_editor.rst:249
msgid ""
"Godot uses a *node configuration warning* system to warn users about "
"incorrectly configured nodes. When a node isn't configured correctly, a "
"yellow warning sign appears next to the node's name in the Scene dock. When "
"you hover or click on the icon, a warning message pops up. You can use this "
"feature in your scripts to help you and your team avoid mistakes when "
"setting up scenes."
msgstr ""

#: ../../docs/tutorials/plugins/running_code_in_the_editor.rst:255
msgid ""
"When using node configuration warnings, when any value that should affect or "
"remove the warning changes, you need to call :ref:"
"`update_configuration_warnings<class_Node_method_update_configuration_warnings>` . "
"By default, the warning only updates when closing and reopening the scene."
msgstr ""

#: ../../docs/tutorials/plugins/running_code_in_the_editor.rst:290
msgid "Running one-off scripts using EditorScript"
msgstr ""

#: ../../docs/tutorials/plugins/running_code_in_the_editor.rst:292
msgid ""
"Sometimes, you need to run code just one time to automate a certain task "
"that is not available in the editor out of the box. Some examples might be:"
msgstr ""

#: ../../docs/tutorials/plugins/running_code_in_the_editor.rst:295
msgid ""
"Use as a playground for GDScript or C# scripting without having to run a "
"project. ``print()`` output is displayed in the editor Output panel."
msgstr ""

#: ../../docs/tutorials/plugins/running_code_in_the_editor.rst:297
msgid ""
"Scale all light nodes in the currently edited scene, as you noticed your "
"level ends up looking too dark or too bright after placing lights where "
"desired."
msgstr ""

#: ../../docs/tutorials/plugins/running_code_in_the_editor.rst:299
msgid ""
"Replace nodes that were copy-pasted with scene instances to make them easier "
"to modify later."
msgstr ""

#: ../../docs/tutorials/plugins/running_code_in_the_editor.rst:302
msgid ""
"This is available in Godot by extending :ref:`class_EditorScript` in a "
"script. This provides a way to run individual scripts in the editor without "
"having to create an editor plugin."
msgstr ""

#: ../../docs/tutorials/plugins/running_code_in_the_editor.rst:306
msgid ""
"To create an EditorScript, right-click a folder or empty space in the "
"FileSystem dock then choose **New > Script...**. In the script creation "
"dialog, click the tree icon to choose an object to extend from (or enter "
"``EditorScript`` directly in the field on the left, though note this is case-"
"sensitive):"
msgstr ""

#: ../../docs/tutorials/plugins/running_code_in_the_editor.rst:315
#, fuzzy
msgid "Creating an editor script in the script editor creation dialog"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/plugins/running_code_in_the_editor.rst:317
msgid ""
"This will automatically select a script template that is suited for "
"EditorScripts, with a ``_run()`` method already inserted:"
msgstr ""

#: ../../docs/tutorials/plugins/running_code_in_the_editor.rst:329
msgid ""
"This ``_run()`` method is executed when you use **File > Run** or the "
"keyboard shortcut :kbd:`Ctrl + Shift + X` while the EditorScript is the "
"currently open script in the script editor. This keyboard shortcut is only "
"effective when currently focused on the script editor."
msgstr ""

#: ../../docs/tutorials/plugins/running_code_in_the_editor.rst:334
msgid "Scripts that extend EditorScript must be ``@tool`` scripts to function."
msgstr ""

#: ../../docs/tutorials/plugins/running_code_in_the_editor.rst:338
msgid ""
"EditorScripts have no undo/redo functionality, so **make sure to save your "
"scene before running one** if the script is designed to modify any data."
msgstr ""

#: ../../docs/tutorials/plugins/running_code_in_the_editor.rst:341
msgid ""
"To access nodes in the currently edited scene, use the :ref:`EditorScript."
"get_scene <class_EditorScript_method_get_scene>` method which returns the "
"root Node of the currently edited scene. Here's an example that recursively "
"gets all nodes in the currently edited scene and doubles the range of all "
"OmniLight3D nodes:"
msgstr ""

#: ../../docs/tutorials/plugins/running_code_in_the_editor.rst:374
msgid ""
"You can change the currently edited scene at the top of the editor even "
"while the Script view is open. This will affect the return value of :ref:"
"`EditorScript.get_scene <class_EditorScript_method_get_scene>`, so make sure "
"you've selected the scene you intend to iterate upon before running the "
"script."
msgstr ""

#: ../../docs/tutorials/plugins/running_code_in_the_editor.rst:381
#: ../../docs/tutorials/scripting/nodes_and_scene_instances.rst:178
msgid "Instancing scenes"
msgstr ""

#: ../../docs/tutorials/plugins/running_code_in_the_editor.rst:383
msgid ""
"You can instantiate packed scenes normally and add them to the scene "
"currently opened in the editor. By default, nodes or scenes added with :ref:"
"`Node.add_child(node) <class_Node_method_add_child>` are **not** visible in "
"the Scene tree dock and are **not** persisted to disk. If you wish the node "
"or scene to be visible in the scene tree dock and persisted to disk when "
"saving the scene, you need to set the child node's :ref:`owner "
"<class_Node_property_owner>` property to the currently edited scene root."
msgstr ""

#: ../../docs/tutorials/plugins/running_code_in_the_editor.rst:391
msgid "If you are using ``@tool``:"
msgstr ""

#: ../../docs/tutorials/plugins/running_code_in_the_editor.rst:416
msgid "If you are using :ref:`EditorScript<class_EditorScript>`:"
msgstr ""

#: ../../docs/tutorials/plugins/running_code_in_the_editor.rst:447
msgid ""
"Using ``@tool`` improperly can yield many errors. It is advised to first "
"write the code how you want it, and only then add the ``@tool`` annotation "
"to the top. Also, make sure to separate code that runs in-editor from code "
"that runs in-game. This way, you can find bugs more easily."
msgstr ""

#: ../../docs/tutorials/rendering/viewports.rst:4
msgid "Using Viewports"
msgstr ""

#: ../../docs/tutorials/rendering/viewports.rst:9
msgid ""
"Think of a :ref:`Viewport <class_Viewport>` as a screen onto which the game "
"is projected. In order to see the game, we need to have a surface on which "
"to draw it. That surface is the Root Viewport."
msgstr ""

#: ../../docs/tutorials/rendering/viewports.rst:15
msgid ""
":ref:`SubViewports <class_SubViewport>` are a kind of Viewport that can be "
"added to the scene so that there are multiple surfaces to draw on. When we "
"are drawing to a SubViewport, we call it a render target. We can access the "
"contents of a render target by accessing its corresponding :ref:`texture "
"<class_Viewport_method_get_texture>`. By using a SubViewport as render "
"target, we can either render multiple scenes simultaneously or we can render "
"to a :ref:`ViewportTexture <class_ViewportTexture>` which is applied to an "
"object in the scene, for example a dynamic skybox."
msgstr ""

#: ../../docs/tutorials/rendering/viewports.rst:22
msgid ""
":ref:`SubViewports <class_SubViewport>` have a variety of use cases, "
"including:"
msgstr ""

#: ../../docs/tutorials/rendering/viewports.rst:24
msgid "Rendering 3D objects within a 2D game"
msgstr ""

#: ../../docs/tutorials/rendering/viewports.rst:25
msgid "Rendering 2D elements in a 3D game"
msgstr ""

#: ../../docs/tutorials/rendering/viewports.rst:26
msgid "Rendering dynamic textures"
msgstr ""

#: ../../docs/tutorials/rendering/viewports.rst:27
msgid "Generating procedural textures at runtime"
msgstr ""

#: ../../docs/tutorials/rendering/viewports.rst:28
msgid "Rendering multiple cameras in the same scene"
msgstr ""

#: ../../docs/tutorials/rendering/viewports.rst:30
msgid ""
"What all these use cases have in common is that you are given the ability to "
"draw objects to a texture as if it were another screen and can then choose "
"what to do with the resulting texture."
msgstr ""

#: ../../docs/tutorials/rendering/viewports.rst:34
msgid ""
"Another kind of Viewports in Godot are :ref:`Windows <class_Window>`. They "
"allow their content to be projected onto a window. While the Root Viewport "
"is a Window, they are less flexible. If you want to use the texture of a "
"Viewport, you'll be working with :ref:`SubViewports <class_SubViewport>` "
"most of the time."
msgstr ""

#: ../../docs/tutorials/rendering/viewports.rst:40
msgid ""
":ref:`Viewports <class_Viewport>` are also responsible for delivering "
"properly adjusted and scaled input events to their children nodes. By "
"default :ref:`SubViewports <class_SubViewport>` don't automatically receive "
"input, unless they receive it from their direct :ref:`SubViewportContainer "
"<class_SubViewportContainer>` parent node. In this case, input can be "
"disabled with the :ref:`Disable Input "
"<class_Viewport_property_gui_disable_input>` property."
msgstr ""

#: ../../docs/tutorials/rendering/viewports.rst:48
msgid ""
"For more information on how Godot handles input, please read the :ref:`Input "
"Event Tutorial <doc_inputevent>`."
msgstr ""

#: ../../docs/tutorials/rendering/viewports.rst:53
msgid ""
"Godot supports 3D sound (in both 2D and 3D nodes). More on this can be found "
"in the :ref:`Audio Streams Tutorial <doc_audio_streams>`. For this type of "
"sound to be audible, the :ref:`Viewport <class_Viewport>` needs to be "
"enabled as a listener (for 2D or 3D). If you are using a :ref:`SubViewport "
"<class_SubViewport>` to display your :ref:`World3D <class_World3D>` or :ref:"
"`World2D <class_World2D>`, don't forget to enable this!"
msgstr ""

#: ../../docs/tutorials/rendering/viewports.rst:60
msgid "Cameras (2D & 3D)"
msgstr ""

#: ../../docs/tutorials/rendering/viewports.rst:62
msgid ""
"When using a :ref:`Camera3D <class_Camera3D>` or :ref:`Camera2D "
"<class_Camera2D>`, it will always display on the closest parent :ref:"
"`Viewport <class_Viewport>` (going towards the root). For example, in the "
"following hierarchy:"
msgstr ""

#: ../../docs/tutorials/rendering/viewports.rst:69
msgid ""
"``CameraA`` will display on the Root :ref:`Viewport <class_Viewport>` and it "
"will draw ``MeshA``. ``CameraB`` will be captured by the :ref:`SubViewport "
"<class_SubViewport>` along with ``MeshB``. Even though ``MeshB`` is in the "
"scene hierarchy, it will still not be drawn to the Root Viewport. Similarly, "
"``MeshA`` will not be visible from the SubViewport because SubViewports only "
"capture nodes below them in the hierarchy."
msgstr ""

#: ../../docs/tutorials/rendering/viewports.rst:75
msgid ""
"There can only be one active camera per :ref:`Viewport <class_Viewport>`, so "
"if there is more than one, make sure that the desired one has the :ref:"
"`current <class_Camera3D_property_current>` property set, or make it the "
"current camera by calling:"
msgstr ""

#: ../../docs/tutorials/rendering/viewports.rst:83
msgid ""
"By default, cameras will render all objects in their world. In 3D, cameras "
"can use their :ref:`cull_mask <class_Camera3D_property_cull_mask>` property "
"combined with the :ref:`VisualInstance3D's <class_VisualInstance3D>` :ref:"
"`layer <class_VisualInstance3D_property_layers>` property to restrict which "
"objects are rendered."
msgstr ""

#: ../../docs/tutorials/rendering/viewports.rst:89
msgid "Scale & stretching"
msgstr ""

#: ../../docs/tutorials/rendering/viewports.rst:91
msgid ""
":ref:`SubViewports <class_SubViewport>` have a :ref:"
"`size<class_SubViewport_property_size>` property, which represents the size "
"of the SubViewport in pixels. For SubViewports which are children of :ref:"
"`SubViewportContainers <class_SubViewportContainer>`, these values are "
"overridden, but for all others, this sets their resolution."
msgstr ""

#: ../../docs/tutorials/rendering/viewports.rst:95
msgid ""
"It is also possible to scale the 2D content and make the :ref:`SubViewport "
"<class_SubViewport>` resolution different from the one specified in size, by "
"calling:"
msgstr ""

#: ../../docs/tutorials/rendering/viewports.rst:103
msgid ""
"For information on scaling and stretching with the Root Viewport visit the :"
"ref:`Multiple Resolutions Tutorial <doc_multiple_resolutions>`"
msgstr ""

#: ../../docs/tutorials/rendering/viewports.rst:106
msgid "Worlds"
msgstr ""

#: ../../docs/tutorials/rendering/viewports.rst:108
msgid ""
"For 3D, a :ref:`Viewport <class_Viewport>` will contain a :ref:`World3D "
"<class_World3D>`. This is basically the universe that links physics and "
"rendering together. Node3D-based nodes will register using the World3D of "
"the closest Viewport. By default, newly created Viewports do not contain a "
"World3D but use the same as their parent Viewport. The Root Viewport always "
"contains a World3D, which is the one objects are rendered to by default."
msgstr ""

#: ../../docs/tutorials/rendering/viewports.rst:115
msgid ""
"A :ref:`World3D <class_World3D>` can be set in a :ref:`Viewport "
"<class_Viewport>` using the :ref:`World "
"3D<class_Viewport_property_world_3d>` property, that will separate all "
"children nodes of this :ref:`Viewport <class_Viewport>` and will prevent "
"them from interacting with the parent Viewport's World3D. This is especially "
"useful in scenarios where, for example, you might want to show a separate "
"character in 3D imposed over the game (like in StarCraft)."
msgstr ""

#: ../../docs/tutorials/rendering/viewports.rst:122
msgid ""
"As a helper for situations where you want to create :ref:`Viewports "
"<class_Viewport>` that display single objects and don't want to create a :"
"ref:`World3D <class_World3D>`, Viewport has the option to use its :ref:`Own "
"World3D <class_Viewport_property_own_world_3d>`. This is useful when you "
"want to instance 3D characters or objects in :ref:`World2D <class_World2D>`."
msgstr ""

#: ../../docs/tutorials/rendering/viewports.rst:127
msgid ""
"For 2D, each :ref:`Viewport <class_Viewport>` always contains its own :ref:"
"`World2D <class_World2D>`. This suffices in most cases, but in case sharing "
"them may be desired, it is possible to do so by setting :ref:"
"`world_2d<class_Viewport_property_world_2d>` on the Viewport through code."
msgstr ""

#: ../../docs/tutorials/rendering/viewports.rst:131
msgid ""
"For an example of how this works, see the demo projects `3D in 2D <https://"
"github.com/godotengine/godot-demo-projects/tree/master/viewport/3d_in_2d>`_ "
"and `2D in 3D <https://github.com/godotengine/godot-demo-projects/tree/"
"master/viewport/2d_in_3d>`_ respectively."
msgstr ""

#: ../../docs/tutorials/rendering/viewports.rst:136
msgid ""
"It is possible to query a capture of the :ref:`Viewport <class_Viewport>` "
"contents. For the Root Viewport, this is effectively a screen capture. This "
"is done with the following code:"
msgstr ""

#: ../../docs/tutorials/rendering/viewports.rst:149
msgid ""
"But if you use this in ``_ready()`` or from the first frame of the :ref:"
"`Viewport's <class_Viewport>` initialization, you will get an empty texture "
"because there is nothing to get as texture. You can deal with it using (for "
"example):"
msgstr ""

#: ../../docs/tutorials/rendering/viewports.rst:160
msgid "Viewport Container"
msgstr ""

#: ../../docs/tutorials/rendering/viewports.rst:162
msgid ""
"If the :ref:`SubViewport <class_SubViewport>` is a child of a :ref:"
"`SubViewportContainer <class_SubViewportContainer>`, it will become active "
"and display anything it has inside. The layout looks like this:"
msgstr ""

#: ../../docs/tutorials/rendering/viewports.rst:166
msgid ""
"The :ref:`SubViewport <class_SubViewport>` will cover the area of its "
"parent :ref:`SubViewportContainer <class_SubViewportContainer>` completely "
"if :ref:`Stretch<class_SubViewportContainer_property_stretch>` is set to "
"``true`` in the SubViewportContainer."
msgstr ""

#: ../../docs/tutorials/rendering/viewports.rst:171
msgid ""
"The size of the :ref:`SubViewportContainer <class_SubViewportContainer>` "
"cannot be smaller than the size of the :ref:`SubViewport "
"<class_SubViewport>`."
msgstr ""

#: ../../docs/tutorials/rendering/viewports.rst:176
msgid ""
"Due to the fact that the :ref:`Viewport <class_Viewport>` is an entryway "
"into another rendering surface, it exposes a few rendering properties that "
"can be different from the project settings. You can choose to use a "
"different level of :ref:`MSAA <class_Viewport_property_msaa_2d>` for each "
"Viewport. The default behavior is ``Disabled``."
msgstr ""

#: ../../docs/tutorials/rendering/viewports.rst:180
msgid ""
"If you know that the :ref:`Viewport <class_Viewport>` is only going to be "
"used for 2D, you can :ref:`Disable 3D<class_Viewport_property_disable_3d>`. "
"Godot will then restrict how the Viewport is drawn. Disabling 3D is slightly "
"faster and uses less memory compared to enabled 3D. It's a good idea to "
"disable 3D if your viewport doesn't render anything in 3D."
msgstr ""

#: ../../docs/tutorials/rendering/viewports.rst:186
msgid ""
"If you need to render 3D shadows in the viewport, make sure to set the "
"viewport's :ref:"
"`positional_shadow_atlas_size<class_Viewport_property_positional_shadow_atlas_size>` "
"property to a value higher than ``0``. Otherwise, shadows won't be rendered. "
"By default, the equivalent project setting is set to ``4096`` on desktop "
"platforms and ``2048`` on mobile platforms."
msgstr ""

#: ../../docs/tutorials/rendering/viewports.rst:189
msgid ""
"Godot also provides a way of customizing how everything is drawn inside :ref:"
"`Viewports <class_Viewport>` using :ref:`Debug "
"Draw<class_Viewport_property_debug_draw>`. Debug Draw allows you to specify "
"a mode which determines how the Viewport will display things drawn inside "
"it. Debug Draw is ``Disabled`` by default. Some other options are "
"``Unshaded``, ``Overdraw``, and ``Wireframe``. For a full list, refer to "
"the :ref:`Viewport Documentation<class_Viewport_property_debug_draw>`."
msgstr ""

#: ../../docs/tutorials/rendering/viewports.rst:193
msgid "**Debug Draw = Disabled** (default): The scene is drawn normally."
msgstr ""

#: ../../docs/tutorials/rendering/viewports.rst:197
msgid ""
"**Debug Draw = Unshaded**: Unshaded draws the scene without using lighting "
"information so all the objects appear flatly colored in their albedo color."
msgstr ""

#: ../../docs/tutorials/rendering/viewports.rst:201
msgid ""
"**Debug Draw = Overdraw**: Overdraw draws the meshes semi-transparent with "
"an additive blend so you can see how the meshes overlap."
msgstr ""

#: ../../docs/tutorials/rendering/viewports.rst:205
msgid ""
"**Debug Draw = Wireframe**: Wireframe draws the scene using only the edges "
"of triangles in the meshes."
msgstr ""

#: ../../docs/tutorials/rendering/viewports.rst:211
msgid ""
"Debug Draw modes are currently **not** supported when using the "
"Compatibility rendering method. They will appear as regular draw modes."
msgstr ""

#: ../../docs/tutorials/rendering/viewports.rst:215
msgid "Render target"
msgstr ""

#: ../../docs/tutorials/rendering/viewports.rst:217
msgid ""
"When rendering to a :ref:`SubViewport <class_SubViewport>`, whatever is "
"inside will not be visible in the scene editor. To display the contents, you "
"have to draw the SubViewport's :ref:`ViewportTexture "
"<class_ViewportTexture>` somewhere. This can be requested via code using "
"(for example):"
msgstr ""

#: ../../docs/tutorials/rendering/viewports.rst:227
msgid ""
"Or it can be assigned in the editor by selecting \"New ViewportTexture\""
msgstr ""

#: ../../docs/tutorials/rendering/viewports.rst:231
msgid ""
"and then selecting the :ref:`Viewport <class_Viewport>` you want to use."
msgstr ""

#: ../../docs/tutorials/rendering/viewports.rst:235
msgid ""
"Every frame, the :ref:`Viewport's <class_Viewport>` texture is cleared away "
"with the default clear color (or a transparent color if :ref:`Transparent "
"BG<class_Viewport_property_transparent_bg>` is set to ``true``). This can be "
"changed by setting :ref:`Clear "
"Mode<class_SubViewport_property_render_target_clear_mode>` to ``Never`` or "
"``Next Frame``. As the name implies, Never means the texture will never be "
"cleared, while next frame will clear the texture on the next frame and then "
"set itself to Never."
msgstr ""

#: ../../docs/tutorials/rendering/viewports.rst:240
msgid ""
"By default, re-rendering of the :ref:`SubViewport <class_SubViewport>` "
"happens when its :ref:`ViewportTexture <class_ViewportTexture>` has been "
"drawn in a frame. If visible, it will be rendered, otherwise, it will not. "
"This behavior can be changed by setting :ref:`Update "
"Mode<class_SubViewport_property_render_target_update_mode>` to ``Never``, "
"``Once``, ``Always``, or ``When Parent Visible``. Never and Always will "
"never or always re-render respectively. Once will re-render the next frame "
"and change to Never afterwards. This can be used to manually update the "
"Viewport. This flexibility allows users to render an image once and then use "
"the texture without incurring the cost of rendering every frame."
msgstr ""

#: ../../docs/tutorials/rendering/viewports.rst:248
#, fuzzy
msgid ""
"Make sure to check the Viewport demos. They are available in the viewport "
"folder of the demos archive, or at https://github.com/godotengine/godot-demo-"
"projects/tree/master/viewport."
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati različite Godo demo projekte "
"`Godot demo projects <https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/tutorials/rendering/multiple_resolutions.rst:4
msgid "Multiple resolutions"
msgstr ""

#: ../../docs/tutorials/rendering/multiple_resolutions.rst:7
msgid "The problem of multiple resolutions"
msgstr ""

#: ../../docs/tutorials/rendering/multiple_resolutions.rst:9
msgid ""
"Developers often have trouble understanding how to best support multiple "
"resolutions in their games. For desktop and console games, this is more or "
"less straightforward, as most screen aspect ratios are 16:9 and resolutions "
"are standard (720p, 1080p, 1440p, 4K, …)."
msgstr ""

#: ../../docs/tutorials/rendering/multiple_resolutions.rst:14
msgid ""
"For mobile games, at first, it was easy. For many years, the iPhone and iPad "
"used the same resolution. When *Retina* was implemented, they just doubled "
"the pixel density; most developers had to supply assets in default and "
"double resolutions."
msgstr ""

#: ../../docs/tutorials/rendering/multiple_resolutions.rst:19
msgid ""
"Nowadays, this is no longer the case, as there are plenty of different "
"screen sizes, densities, and aspect ratios. Non-conventional sizes are also "
"becoming increasingly popular, such as ultrawide displays."
msgstr ""

#: ../../docs/tutorials/rendering/multiple_resolutions.rst:23
msgid ""
"For 3D games, there is not much of a need to support multiple resolutions "
"(from the aesthetic point of view). The 3D geometry will just fill the "
"screen based on the field of view, disregarding the aspect ratio. The main "
"reason one may want to support this, in this case, is for *performance* "
"reasons (running in lower resolution to increase frames per second)."
msgstr ""

#: ../../docs/tutorials/rendering/multiple_resolutions.rst:29
msgid ""
"For 2D and game UIs, this is a different matter, as art needs to be created "
"using specific pixel sizes in software such as Photoshop, GIMP or Krita."
msgstr ""

#: ../../docs/tutorials/rendering/multiple_resolutions.rst:32
msgid ""
"Since layouts, aspect ratios, resolutions, and pixel densities can change so "
"much, it is no longer possible to design UIs for every specific screen. "
"Another method must be used."
msgstr ""

#: ../../docs/tutorials/rendering/multiple_resolutions.rst:37
msgid "One size fits all"
msgstr ""

#: ../../docs/tutorials/rendering/multiple_resolutions.rst:39
msgid ""
"The most common approach is to use a single *base* resolution and then fit "
"it to everything else. This resolution is how most players are expected to "
"play the game (given their hardware). For mobile, Google has useful `stats "
"<https://developer.android.com/about/dashboards>`_ online, and for desktop, "
"Steam `also does <https://store.steampowered.com/hwsurvey/>`_."
msgstr ""

#: ../../docs/tutorials/rendering/multiple_resolutions.rst:45
msgid ""
"As an example, Steam shows that the most common *primary display resolution* "
"is 1920×1080, so a sensible approach is to develop a game for this "
"resolution, then handle scaling for different sizes and aspect ratios."
msgstr ""

#: ../../docs/tutorials/rendering/multiple_resolutions.rst:49
msgid "Godot provides several useful tools to do this easily."
msgstr ""

#: ../../docs/tutorials/rendering/multiple_resolutions.rst:53
#, fuzzy
msgid ""
"You can see how Godot's support for multiple resolutions works in action "
"using the `Multiple Resolutions and Aspect Ratios demo project <https://"
"github.com/godotengine/godot-demo-projects/tree/master/gui/"
"multiple_resolutions>`__."
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati različite Godo demo projekte "
"`Godot demo projects <https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/tutorials/rendering/multiple_resolutions.rst:57
msgid "Base size"
msgstr ""

#: ../../docs/tutorials/rendering/multiple_resolutions.rst:59
msgid ""
"A base size for the window can be specified in the Project Settings under "
"**Display → Window**."
msgstr ""

#: ../../docs/tutorials/rendering/multiple_resolutions.rst:64
msgid ""
"However, what it does is not completely obvious; the engine will *not* "
"attempt to switch the monitor to this resolution. Rather, think of this "
"setting as the \"design size\", i.e. the size of the area that you work with "
"in the editor. This setting corresponds directly to the size of the blue "
"rectangle in the 2D editor."
msgstr ""

#: ../../docs/tutorials/rendering/multiple_resolutions.rst:70
msgid ""
"There is often a need to support devices with screen and window sizes that "
"are different from this base size. Godot offers many ways to control how the "
"viewport will be resized and stretched to different screen sizes."
msgstr ""

#: ../../docs/tutorials/rendering/multiple_resolutions.rst:77
msgid ""
"On this page, *window* refers to the screen area allotted to your game by "
"the system, while *viewport* refers to the root object (accessible from "
"``get_tree().root``) which the game controls to fill this screen area. This "
"viewport is a :ref:`Window <class_Window>` instance. Recall from the :ref:"
"`introduction <doc_viewports>` that *all* Window objects are viewports."
msgstr ""

#: ../../docs/tutorials/rendering/multiple_resolutions.rst:83
msgid ""
"To configure the stretch base size at runtime from a script, use the "
"``get_tree().root.content_scale_size`` property (see :ref:`Window."
"content_scale_size <class_Window_property_content_scale_size>`). Changing "
"this value can indirectly change the size of 2D elements. However, to "
"provide an user-accessible scaling option, using :ref:"
"`doc_multiple_resolutions_stretch_scale` is recommended as it's easier to "
"adjust."
msgstr ""

#: ../../docs/tutorials/rendering/multiple_resolutions.rst:93
msgid ""
"Godot follows a modern approach to multiple resolutions. The engine will "
"never change the monitor's resolution on its own. While changing the "
"monitor's resolution is the most efficient approach, it's also the least "
"reliable approach as it can leave the monitor stuck on a low resolution if "
"the game crashes. This is especially common on macOS or Linux which don't "
"handle resolution changes as well as Windows."
msgstr ""

#: ../../docs/tutorials/rendering/multiple_resolutions.rst:100
msgid ""
"Changing the monitor's resolution also removes any control from the game "
"developer over filtering and aspect ratio stretching, which can be important "
"to ensure correct display for pixel art games."
msgstr ""

#: ../../docs/tutorials/rendering/multiple_resolutions.rst:104
msgid ""
"On top of that, changing the monitor's resolution makes alt-tabbing in and "
"out of a game much slower since the monitor has to change resolutions every "
"time this is done."
msgstr ""

#: ../../docs/tutorials/rendering/multiple_resolutions.rst:109
msgid "Resizing"
msgstr ""

#: ../../docs/tutorials/rendering/multiple_resolutions.rst:111
msgid ""
"There are several types of devices, with several types of screens, which in "
"turn have different pixel density and resolutions. Handling all of them can "
"be a lot of work, so Godot tries to make the developer's life a little "
"easier. The :ref:`Viewport <class_Viewport>` node has several functions to "
"handle resizing, and the root node of the scene tree is always a viewport "
"(scenes loaded are instanced as a child of it, and it can always be accessed "
"by calling ``get_tree().root`` or ``get_node(\"/root\")``)."
msgstr ""

#: ../../docs/tutorials/rendering/multiple_resolutions.rst:120
msgid ""
"In any case, while changing the root Viewport params is probably the most "
"flexible way to deal with the problem, it can be a lot of work, code and "
"guessing, so Godot provides a set of parameters in the project settings to "
"handle multiple resolutions."
msgstr ""

#: ../../docs/tutorials/rendering/multiple_resolutions.rst:126
msgid "Stretch settings"
msgstr ""

#: ../../docs/tutorials/rendering/multiple_resolutions.rst:128
msgid ""
"Stretch settings are located in the project settings and provide several "
"options:"
msgstr ""

#: ../../docs/tutorials/rendering/multiple_resolutions.rst:133
msgid "Stretch Mode"
msgstr ""

#: ../../docs/tutorials/rendering/multiple_resolutions.rst:135
msgid ""
"The **Stretch Mode** setting defines how the base size is stretched to fit "
"the resolution of the window or screen. The animations below use a \"base "
"size\" of just 16×9 pixels to demonstrate the effect of different stretch "
"modes. A single sprite, also 16×9 pixels in size, covers the entire "
"viewport, and a diagonal :ref:`Line2D <class_Line2D>` is added on top of it:"
msgstr ""

#: ../../docs/tutorials/rendering/multiple_resolutions.rst:146
msgid ""
"**Stretch Mode = Disabled** (default): No stretching happens. One unit in "
"the scene corresponds to one pixel on the screen. In this mode, the "
"**Stretch Aspect** setting has no effect."
msgstr ""

#: ../../docs/tutorials/rendering/multiple_resolutions.rst:152
msgid ""
"**Stretch Mode = Canvas Items**: In this mode, the base size specified in "
"width and height in the project settings is stretched to cover the whole "
"screen (taking the **Stretch Aspect** setting into account). This means that "
"everything is rendered directly at the target resolution. 3D is unaffected, "
"while in 2D, there is no longer a 1:1 correspondence between sprite pixels "
"and screen pixels, which may result in scaling artifacts."
msgstr ""

#: ../../docs/tutorials/rendering/multiple_resolutions.rst:162
msgid ""
"**Stretch Mode = Viewport**: Viewport scaling means that the size of the "
"root :ref:`Viewport <class_Viewport>` is set precisely to the base size "
"specified in the Project Settings' **Display** section. The scene is "
"rendered to this viewport first. Finally, this viewport is scaled to fit the "
"screen (taking the **Stretch Aspect** setting into account)."
msgstr ""

#: ../../docs/tutorials/rendering/multiple_resolutions.rst:171
msgid ""
"To configure the stretch mode at runtime from a script, use the ``get_tree()."
"root.content_scale_mode`` property (see :ref:`Window.content_scale_mode "
"<class_Window_property_content_scale_mode>` and the :ref:`ContentScaleMode "
"<enum_Window_ContentScaleMode>` enum)."
msgstr ""

#: ../../docs/tutorials/rendering/multiple_resolutions.rst:177
msgid "Stretch Aspect"
msgstr ""

#: ../../docs/tutorials/rendering/multiple_resolutions.rst:179
msgid ""
"The second setting is the stretch aspect. Note that this only takes effect "
"if **Stretch Mode** is set to something other than **Disabled**."
msgstr ""

#: ../../docs/tutorials/rendering/multiple_resolutions.rst:182
msgid ""
"In the animations below, you will notice gray and black areas. The black "
"areas are added by the engine and cannot be drawn into. The gray areas are "
"part of your scene, and can be drawn to. The gray areas correspond to the "
"region outside the blue frame you see in the 2D editor."
msgstr ""

#: ../../docs/tutorials/rendering/multiple_resolutions.rst:187
msgid ""
"**Stretch Aspect = Ignore**: Ignore the aspect ratio when stretching the "
"screen. This means that the original resolution will be stretched to exactly "
"fill the screen, even if it's wider or narrower. This may result in "
"nonuniform stretching: things looking wider or taller than designed."
msgstr ""

#: ../../docs/tutorials/rendering/multiple_resolutions.rst:195
msgid ""
"**Stretch Aspect = Keep**: Keep aspect ratio when stretching the screen. "
"This means that the viewport retains its original size regardless of the "
"screen resolution, and black bars will be added to the top/bottom of the "
"screen (\"letterboxing\") or the sides (\"pillarboxing\")."
msgstr ""

#: ../../docs/tutorials/rendering/multiple_resolutions.rst:201
msgid ""
"This is a good option if you know the aspect ratio of your target devices in "
"advance, or if you don't want to handle different aspect ratios."
msgstr ""

#: ../../docs/tutorials/rendering/multiple_resolutions.rst:207
msgid ""
"**Stretch Aspect = Keep Width**: Keep aspect ratio when stretching the "
"screen. If the screen is wider than the base size, black bars are added at "
"the left and right (pillarboxing). But if the screen is taller than the base "
"resolution, the viewport will be grown in the vertical direction (and more "
"content will be visible to the bottom). You can also think of this as "
"\"Expand Vertically\"."
msgstr ""

#: ../../docs/tutorials/rendering/multiple_resolutions.rst:214
msgid ""
"This is usually the best option for creating GUIs or HUDs that scale, so "
"some controls can be anchored to the bottom (:ref:`doc_size_and_anchors`)."
msgstr ""

#: ../../docs/tutorials/rendering/multiple_resolutions.rst:220
msgid ""
"**Stretch Aspect = Keep Height**: Keep aspect ratio when stretching the "
"screen. If the screen is taller than the base size, black bars are added at "
"the top and bottom (letterboxing). But if the screen is wider than the base "
"resolution, the viewport will be grown in the horizontal direction (and more "
"content will be visible to the right). You can also think of this as "
"\"Expand Horizontally\"."
msgstr ""

#: ../../docs/tutorials/rendering/multiple_resolutions.rst:227
msgid ""
"This is usually the best option for 2D games that scroll horizontally (like "
"runners or platformers)."
msgstr ""

#: ../../docs/tutorials/rendering/multiple_resolutions.rst:232
msgid ""
"**Stretch Aspect = Expand**: Keep aspect ratio when stretching the screen, "
"but keep neither the base width nor height. Depending on the screen aspect "
"ratio, the viewport will either be larger in the horizontal direction (if "
"the screen is wider than the base size) or in the vertical direction (if the "
"screen is taller than the original size)."
msgstr ""

#: ../../docs/tutorials/rendering/multiple_resolutions.rst:243
msgid ""
"To support both portrait and landscape mode with a similar automatically "
"determined scale factor, set your project's base resolution to be a *square* "
"(1:1 aspect ratio) instead of a rectangle. For instance, if you wish to "
"design for 1280×720 as the base resolution but wish to support both portrait "
"and landscape mode, use 720×720 as the project's base window size in the "
"Project Settings."
msgstr ""

#: ../../docs/tutorials/rendering/multiple_resolutions.rst:250
msgid ""
"To allow the user to choose their preferred screen orientation at run-time, "
"remember to set **Display > Window > Handheld > Orientation** to ``sensor``."
msgstr ""

#: ../../docs/tutorials/rendering/multiple_resolutions.rst:253
msgid ""
"To configure the stretch aspect at runtime from a script, use the "
"``get_tree().root.content_scale_aspect`` property (see :ref:`Window."
"content_scale_aspect <class_Window_property_content_scale_aspect>` and the :"
"ref:`ContentScaleAspect <enum_Window_ContentScaleAspect>` enum)."
msgstr ""

#: ../../docs/tutorials/rendering/multiple_resolutions.rst:261
msgid "Stretch Scale"
msgstr ""

#: ../../docs/tutorials/rendering/multiple_resolutions.rst:263
msgid ""
"The **Scale** setting allows you to add an extra scaling factor on top of "
"what the **Stretch** options above already provide. The default value of "
"``1.0`` means that no additional scaling occurs."
msgstr ""

#: ../../docs/tutorials/rendering/multiple_resolutions.rst:267
msgid ""
"For example, if you set **Scale** to ``2.0`` and leave **Stretch Mode** on "
"**Disabled**, each unit in your scene will correspond to 2×2 pixels on the "
"screen. This is a good way to provide scaling options for non-game "
"applications."
msgstr ""

#: ../../docs/tutorials/rendering/multiple_resolutions.rst:271
msgid ""
"If **Stretch Mode** is set to **canvas_items**, 2D elements will be scaled "
"relative to the base window size, then multiplied by the **Scale** setting. "
"This can be exposed to players to allow them to adjust the automatically "
"determined scale to their liking, for better accessibility."
msgstr ""

#: ../../docs/tutorials/rendering/multiple_resolutions.rst:276
msgid ""
"If **Stretch Mode** is set to **viewport**, the viewport's resolution is "
"divided by **Scale**. This makes pixels look larger and reduces rendering "
"resolution (with a given window size), which can improve performance."
msgstr ""

#: ../../docs/tutorials/rendering/multiple_resolutions.rst:280
msgid ""
"To configure the stretch scale at runtime from a script, use the "
"``get_tree().root.content_scale_factor`` property (see :ref:`Window."
"content_scale_factor <class_Window_property_content_scale_factor>`)."
msgstr ""

#: ../../docs/tutorials/rendering/multiple_resolutions.rst:287
msgid "Stretch Scale Mode"
msgstr ""

#: ../../docs/tutorials/rendering/multiple_resolutions.rst:289
msgid ""
"Since Godot 4.2, the **Stretch Scale Mode** setting allows you to constrain "
"the automatically determined scale factor (as well as the manually specified "
"**Stretch Scale** setting) to integer values. By default, this setting is "
"set to ``fractional``, which allows any scale factor to be applied "
"(including fractional values such as ``2.5``). When set to ``integer``, the "
"value is rounded down to the nearest integer. For example, instead of using "
"a scale factor of ``2.5``, it would be rounded down to ``2.0``. This is "
"useful to prevent distortion when displaying pixel art."
msgstr ""

#: ../../docs/tutorials/rendering/multiple_resolutions.rst:298
msgid ""
"Compare this pixel art which is displayed with the ``viewport`` stretch "
"mode, with the stretch scale mode set to ``fractional``:"
msgstr ""

#: ../../docs/tutorials/rendering/multiple_resolutions.rst:305
msgid "Fractional scaling example (incorrect pixel art appearance)"
msgstr ""

#: ../../docs/tutorials/rendering/multiple_resolutions.rst:305
msgid ""
"Checkerboard doesn't look \"even\". Line widths in the logo and text varies "
"wildly."
msgstr ""

#: ../../docs/tutorials/rendering/multiple_resolutions.rst:307
msgid ""
"This pixel art is also displayed with the ``viewport`` stretch mode, but the "
"stretch scale mode is set to ``integer`` this time:"
msgstr ""

#: ../../docs/tutorials/rendering/multiple_resolutions.rst:314
msgid "Integer scaling example (correct pixel art appearance)"
msgstr ""

#: ../../docs/tutorials/rendering/multiple_resolutions.rst:314
msgid "Checkerboard looks perfectly even. Line widths are consistent."
msgstr ""

#: ../../docs/tutorials/rendering/multiple_resolutions.rst:316
msgid ""
"For example, if your viewport base size is 640×360 and the window size is "
"1366×768:"
msgstr ""

#: ../../docs/tutorials/rendering/multiple_resolutions.rst:318
msgid ""
"When using ``fractional``, the viewport is displayed at a resolution of "
"1366×768 (scale factor is roughly 2.133×). The entire window space is used. "
"Each pixel in the viewport corresponds to 2.133×2.133 pixels in the "
"displayed area. However, since displays can only display \"whole\" pixels, "
"this will lead to uneven pixel scaling which results in incorrect appearance "
"of pixel art."
msgstr ""

#: ../../docs/tutorials/rendering/multiple_resolutions.rst:323
msgid ""
"When using ``integer``, the viewport is displayed at a resolution of "
"1280×720 (scale factor is 2×). The remaining space is filled with black bars "
"on all four sides, so that each pixel in the viewport corresponds to 2×2 "
"pixels in the displayed area."
msgstr ""

#: ../../docs/tutorials/rendering/multiple_resolutions.rst:328
msgid ""
"This setting is effective with any stretch mode. However, when using the "
"``disabled`` stretch mode, it will only affect the **Stretch Scale** setting "
"by rounding it *down* to the nearest integer value. This can be used for 3D "
"games that have a pixel art UI, so that the visible area in the 3D viewport "
"doesn't reduce in size (which occurs when using ``canvas_items`` or "
"``viewport`` stretch mode with the ``integer`` scale mode)."
msgstr ""

#: ../../docs/tutorials/rendering/multiple_resolutions.rst:337
#: ../../docs/tutorials/rendering/jitter_stutter.rst:103
msgid ""
"Games should use the **Exclusive Fullscreen** window mode, as opposed to "
"**Fullscreen** which is designed to prevent Windows from automatically "
"treating the window as if it was exclusive fullscreen."
msgstr ""

#: ../../docs/tutorials/rendering/multiple_resolutions.rst:341
#: ../../docs/tutorials/rendering/jitter_stutter.rst:107
msgid ""
"**Fullscreen** is meant to be used by GUI applications that want to use per-"
"pixel transparency without a risk of having it disabled by the OS. It "
"achieves this by leaving a 1-pixel line at the bottom of the screen. By "
"contrast, **Exclusive Fullscreen** uses the actual screen size and allows "
"Windows to reduce jitter and input lag for fullscreen games."
msgstr ""

#: ../../docs/tutorials/rendering/multiple_resolutions.rst:347
msgid ""
"When using integer scaling, this is particularly important as the 1-pixel "
"height reduction from the **Fullscreen** mode can cause integer scaling to "
"use a smaller scale factor than expected."
msgstr ""

#: ../../docs/tutorials/rendering/multiple_resolutions.rst:352
msgid "Common use case scenarios"
msgstr ""

#: ../../docs/tutorials/rendering/multiple_resolutions.rst:354
msgid ""
"The following settings are recommended to support multiple resolutions and "
"aspect ratios well."
msgstr ""

#: ../../docs/tutorials/rendering/multiple_resolutions.rst:358
msgid "Desktop game"
msgstr ""

#: ../../docs/tutorials/rendering/multiple_resolutions.rst:360
msgid "**Non-pixel art:**"
msgstr ""

#: ../../docs/tutorials/rendering/multiple_resolutions.rst:362
msgid ""
"Set the base window width to ``1920`` and window height to ``1080``. If you "
"have a display smaller than 1920×1080, set **Window Width Override** and "
"**Window Height Override** to lower values to make the window smaller when "
"the project starts."
msgstr ""

#: ../../docs/tutorials/rendering/multiple_resolutions.rst:365
msgid ""
"Alternatively, if you're targeting high-end devices primarily, set the base "
"window width to ``3840`` and window height to ``2160``. This allows you to "
"provide higher resolution 2D assets, resulting in crisper visuals at the "
"cost of higher memory usage and file sizes. Note that this will make non-"
"mipmapped textures grainy on low resolution devices, so make sure to follow "
"the instructions described in :ref:"
"`doc_multiple_resolutions_reducing_aliasing_on_downsampling`."
msgstr ""

#: ../../docs/tutorials/rendering/multiple_resolutions.rst:372
#: ../../docs/tutorials/rendering/multiple_resolutions.rst:418
#: ../../docs/tutorials/rendering/multiple_resolutions.rst:445
msgid "Set the stretch mode to ``canvas_items``."
msgstr ""

#: ../../docs/tutorials/rendering/multiple_resolutions.rst:373
#: ../../docs/tutorials/rendering/multiple_resolutions.rst:419
#: ../../docs/tutorials/rendering/multiple_resolutions.rst:446
msgid ""
"Set the stretch aspect to ``expand``. This allows for supporting multiple "
"aspect ratios and makes better use of tall smartphone displays (such as 18:9 "
"or 19:9 aspect ratios)."
msgstr ""

#: ../../docs/tutorials/rendering/multiple_resolutions.rst:375
#: ../../docs/tutorials/rendering/multiple_resolutions.rst:421
#: ../../docs/tutorials/rendering/multiple_resolutions.rst:448
msgid ""
"Configure Control nodes' anchors to snap to the correct corners using the "
"**Layout** menu."
msgstr ""

#: ../../docs/tutorials/rendering/multiple_resolutions.rst:377
msgid "**Pixel art:**"
msgstr ""

#: ../../docs/tutorials/rendering/multiple_resolutions.rst:379
msgid ""
"Set the base window size to the viewport size you intend to use. Most pixel "
"art games use viewport sizes between 256×224 and 640×480. 640×360 is a good "
"baseline, as it scales to 1280×720, 1920×1080, 2560×1440, and 3840×2160 "
"without any black bars when using integer scaling. Higher viewport sizes "
"will require using higher resolution artwork, unless you intend to show more "
"of the game world at a given time."
msgstr ""

#: ../../docs/tutorials/rendering/multiple_resolutions.rst:385
msgid "Set the stretch mode to ``viewport``."
msgstr ""

#: ../../docs/tutorials/rendering/multiple_resolutions.rst:386
msgid ""
"Set the stretch aspect to ``keep`` to enforce a single aspect ratio (with "
"black bars). As an alternative, you can set the stretch aspect to ``expand`` "
"to support multiple aspect ratios."
msgstr ""

#: ../../docs/tutorials/rendering/multiple_resolutions.rst:389
msgid ""
"If using the ``expand`` stretch aspect, Configure Control nodes' anchors to "
"snap to the correct corners using the **Layout** menu."
msgstr ""

#: ../../docs/tutorials/rendering/multiple_resolutions.rst:391
msgid ""
"Set the stretch scale mode to ``integer``. This prevents uneven pixel "
"scaling from occurring, which makes pixel art not display as intended."
msgstr ""

#: ../../docs/tutorials/rendering/multiple_resolutions.rst:396
msgid ""
"The ``viewport`` stretch mode provides low-resolution rendering that is then "
"stretched to the final window size. If you are OK with sprites being able to "
"move or rotate in \"sub-pixel\" positions or wish to have a high resolution "
"3D viewport, you should use the ``canvas_items`` stretch mode instead of the "
"``viewport`` stretch mode."
msgstr ""

#: ../../docs/tutorials/rendering/multiple_resolutions.rst:403
msgid "Mobile game in landscape mode"
msgstr ""

#: ../../docs/tutorials/rendering/multiple_resolutions.rst:405
msgid ""
"Godot is configured to use landscape mode by default. This means you don't "
"need to change the display orientation project setting."
msgstr ""

#: ../../docs/tutorials/rendering/multiple_resolutions.rst:408
msgid "Set the base window width to ``1280`` and window height to ``720``."
msgstr ""

#: ../../docs/tutorials/rendering/multiple_resolutions.rst:409
msgid ""
"Alternatively, if you're targeting high-end devices primarily, set the base "
"window width to ``1920`` and window height to ``1080``. This allows you to "
"provide higher resolution 2D assets, resulting in crisper visuals at the "
"cost of higher memory usage and file sizes. Many devices have even higher "
"resolution displays (1440p), but the difference with 1080p is barely visible "
"given the small size of smartphone displays. Note that this will make non-"
"mipmapped textures grainy on low resolution devices, so make sure to follow "
"the instructions described in :ref:"
"`doc_multiple_resolutions_reducing_aliasing_on_downsampling`."
msgstr ""

#: ../../docs/tutorials/rendering/multiple_resolutions.rst:425
msgid ""
"To better support tablets and foldable phones (which frequently feature "
"displays with aspect ratios close to 4:3), consider using a base resolution "
"that has a 4:3 aspect ratio while following the rest of the instructions "
"here. For instance, you can set the base window width to ``1280`` and the "
"base window height to ``960``."
msgstr ""

#: ../../docs/tutorials/rendering/multiple_resolutions.rst:432
msgid "Mobile game in portrait mode"
msgstr ""

#: ../../docs/tutorials/rendering/multiple_resolutions.rst:434
msgid "Set the base window width to ``720`` and window height to ``1280``."
msgstr ""

#: ../../docs/tutorials/rendering/multiple_resolutions.rst:435
msgid ""
"Alternatively, if you're targeting high-end devices primarily, set the base "
"window width to ``1080`` and window height to ``1920``. This allows you to "
"provide higher resolution 2D assets, resulting in crisper visuals at the "
"cost of higher memory usage and file sizes. Many devices have even higher "
"resolution displays (1440p), but the difference with 1080p is barely visible "
"given the small size of smartphone displays. Note that this will make non-"
"mipmapped textures grainy on low resolution devices, so make sure to follow "
"the instructions described in :ref:"
"`doc_multiple_resolutions_reducing_aliasing_on_downsampling`."
msgstr ""

#: ../../docs/tutorials/rendering/multiple_resolutions.rst:444
msgid "Set **Display > Window > Handheld > Orientation** to ``portrait``."
msgstr ""

#: ../../docs/tutorials/rendering/multiple_resolutions.rst:452
msgid ""
"To better support tablets and foldable phones (which frequently feature "
"displays with aspect ratios close to 4:3), consider using a base resolution "
"that has a 3:4 aspect ratio while following the rest of the instructions "
"here. For instance, you can set the base window width to ``960`` and the "
"base window height to ``1280``."
msgstr ""

#: ../../docs/tutorials/rendering/multiple_resolutions.rst:459
msgid "Non-game application"
msgstr ""

#: ../../docs/tutorials/rendering/multiple_resolutions.rst:461
msgid ""
"Set the base window width and height to the smallest window size that you "
"intend to target. This is not required, but this ensures that you design "
"your UI with small window sizes in mind."
msgstr ""

#: ../../docs/tutorials/rendering/multiple_resolutions.rst:463
msgid "Keep the stretch mode to its default value, ``disabled``."
msgstr ""

#: ../../docs/tutorials/rendering/multiple_resolutions.rst:464
msgid ""
"Keep the stretch aspect to its default value, ``ignore`` (its value won't be "
"used since the stretch mode is ``disabled``)."
msgstr ""

#: ../../docs/tutorials/rendering/multiple_resolutions.rst:466
msgid ""
"You can define a minimum window size by calling ``get_window()."
"set_min_size()`` in a script's ``_ready()`` function. This prevents the user "
"from resizing the application below a certain size, which could break the UI "
"layout."
msgstr ""

#: ../../docs/tutorials/rendering/multiple_resolutions.rst:472
msgid ""
"Godot doesn't support manually overriding the 2D scale factor yet, so it is "
"not possible to have hiDPI support in non-game applications. Due to this, it "
"is recommended to leave **Allow Hidpi** disabled in non-game applications to "
"allow for the OS to use its low-DPI fallback."
msgstr ""

#: ../../docs/tutorials/rendering/multiple_resolutions.rst:478
msgid "hiDPI support"
msgstr ""

#: ../../docs/tutorials/rendering/multiple_resolutions.rst:480
msgid ""
"By default, Godot projects are considered DPI-aware by the operating system. "
"This is controlled by the **Display > Window > Dpi > Allow Hidpi** project "
"setting, which should be left enabled whenever possible. Disabling DPI "
"awareness can break fullscreen behavior on Windows."
msgstr ""

#: ../../docs/tutorials/rendering/multiple_resolutions.rst:485
msgid ""
"Since Godot projects are DPI-aware, they may appear at a very small window "
"size when launching on an hiDPI display (proportionally to the screen "
"resolution). For a game, the most common way to work around this issue is to "
"make them fullscreen by default. Alternatively, you could set the window "
"size in an :ref:`autoload <doc_singletons_autoload>`'s ``_ready()`` function "
"according to the screen size."
msgstr ""

#: ../../docs/tutorials/rendering/multiple_resolutions.rst:492
msgid "To ensure 2D elements don't appear too small on hiDPI displays:"
msgstr ""

#: ../../docs/tutorials/rendering/multiple_resolutions.rst:494
msgid ""
"For games, use the ``canvas_items`` or ``viewport`` stretch modes so that 2D "
"elements are automatically resized according to the current window size."
msgstr ""

#: ../../docs/tutorials/rendering/multiple_resolutions.rst:496
msgid ""
"For non-game applications, use the ``disabled`` stretch mode and set the "
"stretch scale to a value corresponding to the display scale factor in an :"
"ref:`autoload <doc_singletons_autoload>`'s ``_ready()`` function. The "
"display scale factor is set in the operating system's settings and can be "
"queried using :ref:"
"`screen_get_scale<class_DisplayServer_method_screen_get_scale>`. This method "
"is currently only implemented on macOS. On other operating systems, you will "
"need to implement a method to guess the display scale factor based on the "
"screen resolution (with a setting to let the user override this if needed). "
"This is the approach currently used by the Godot editor."
msgstr ""

#: ../../docs/tutorials/rendering/multiple_resolutions.rst:506
msgid ""
"The **Allow Hidpi** setting is only effective on Windows and macOS. It's "
"ignored on all other platforms."
msgstr ""

#: ../../docs/tutorials/rendering/multiple_resolutions.rst:511
msgid ""
"The Godot editor itself is always marked as DPI-aware. Running the project "
"from the editor will only be DPI-aware if **Allow Hidpi** is enabled in the "
"Project Settings."
msgstr ""

#: ../../docs/tutorials/rendering/multiple_resolutions.rst:518
msgid "Reducing aliasing on downsampling"
msgstr ""

#: ../../docs/tutorials/rendering/multiple_resolutions.rst:520
msgid ""
"If the game has a very high base resolution (e.g. 3840×2160), aliasing might "
"appear when downsampling to something considerably lower like 1280×720."
msgstr ""

#: ../../docs/tutorials/rendering/multiple_resolutions.rst:523
msgid ""
"To resolve this, you can :ref:`enable mipmaps "
"<doc_importing_images_mipmaps>` on all your 2D textures. However, enabling "
"mipmaps will increase memory usage which can be an issue on low-end mobile "
"devices."
msgstr ""

#: ../../docs/tutorials/rendering/multiple_resolutions.rst:528
msgid "Handling aspect ratios"
msgstr ""

#: ../../docs/tutorials/rendering/multiple_resolutions.rst:530
msgid ""
"Once scaling for different resolutions is accounted for, make sure that your "
"*user interface* also scales for different aspect ratios. This can be done "
"using :ref:`anchors <doc_size_and_anchors>` and/or :ref:`containers "
"<doc_gui_containers>`."
msgstr ""

#: ../../docs/tutorials/rendering/multiple_resolutions.rst:536
msgid "Field of view scaling"
msgstr ""

#: ../../docs/tutorials/rendering/multiple_resolutions.rst:538
msgid ""
"The 3D Camera node's **Keep Aspect** property defaults to the **Keep "
"Height** scaling mode (also called *Hor+*). This is usually the best value "
"for desktop games and mobile games in landscape mode, as widescreen displays "
"will automatically use a wider field of view."
msgstr ""

#: ../../docs/tutorials/rendering/multiple_resolutions.rst:543
msgid ""
"However, if your 3D game is intended to be played in portrait mode, it may "
"make more sense to use **Keep Width** instead (also called *Vert-*). This "
"way, smartphones with an aspect ratio taller than 16:9 (e.g. 19:9) will use "
"a *taller* field of view, which is more logical here."
msgstr ""

#: ../../docs/tutorials/rendering/multiple_resolutions.rst:549
msgid "Scaling 2D and 3D elements differently using Viewports"
msgstr ""

#: ../../docs/tutorials/rendering/multiple_resolutions.rst:551
msgid ""
"Using multiple Viewport nodes, you can have different scales for various "
"elements. For instance, you can use this to render the 3D world at a low "
"resolution while keeping 2D elements at the native resolution. This can "
"improve performance significantly while keeping the HUD and other 2D "
"elements crisp."
msgstr ""

#: ../../docs/tutorials/rendering/multiple_resolutions.rst:556
msgid ""
"This is done by using the root Viewport node only for 2D elements, then "
"creating a Viewport node to display the 3D world and displaying it using a "
"SubViewportContainer or TextureRect node. There will effectively be two "
"viewports in the final project. One upside of using TextureRect over "
"SubViewportContainer is that it allows enable linear filtering. This makes "
"scaled 3D viewports look better in many cases."
msgstr ""

#: ../../docs/tutorials/rendering/multiple_resolutions.rst:563
#, fuzzy
msgid ""
"See the `3D viewport scaling demo <https://github.com/godotengine/godot-demo-"
"projects/tree/master/viewport/3d_scaling>`__ for examples."
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati različite Godo demo projekte "
"`Godot demo projects <https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/tutorials/rendering/jitter_stutter.rst:4
msgid "Fixing jitter, stutter and input lag"
msgstr ""

#: ../../docs/tutorials/rendering/jitter_stutter.rst:7
msgid "What is jitter, stutter and input lag?"
msgstr ""

#: ../../docs/tutorials/rendering/jitter_stutter.rst:9
msgid ""
"*Jitter* and *stutter* are two different alterations to visible motion of "
"objects on screen that may affect a game, even when running at full speed. "
"These effects are mostly visible in games where the world moves at a "
"constant speed in a fixed direction, like runners or platformers."
msgstr ""

#: ../../docs/tutorials/rendering/jitter_stutter.rst:14
msgid ""
"*Input lag* is unrelated to jitter and stutter, but is sometimes discussed "
"alongside. Input lag refers to visible on-screen delay when performing "
"actions with the mouse, keyboard, controller or touchscreen. It can be "
"related to game code, engine code or external factors (such as hardware). "
"Input lag is most noticeable in games that use the mouse to aim, such as "
"first-person games. Input lag can't be completely eliminated, but it can be "
"reduced in several ways."
msgstr ""

#: ../../docs/tutorials/rendering/jitter_stutter.rst:22
msgid "Distinguishing between jitter and stutter"
msgstr ""

#: ../../docs/tutorials/rendering/jitter_stutter.rst:24
msgid ""
"A game running at a normal framerate without exhibiting any effect will "
"appear smooth:"
msgstr ""

#: ../../docs/tutorials/rendering/jitter_stutter.rst:28
msgid "A game exhibiting *jitter* will shake constantly in a very subtle way:"
msgstr ""

#: ../../docs/tutorials/rendering/jitter_stutter.rst:32
msgid ""
"Finally, a game exhibiting *stutter* will appear smooth, but appear to "
"*stop* or *roll back a frame* every few seconds:"
msgstr ""

#: ../../docs/tutorials/rendering/jitter_stutter.rst:39
msgid "Jitter"
msgstr ""

#: ../../docs/tutorials/rendering/jitter_stutter.rst:41
msgid ""
"There can be many causes of jitter, the most typical one happens when the "
"game *physics frequency* (usually 60 Hz) runs at a different resolution than "
"the monitor refresh rate. Check whether your monitor refresh rate is "
"different from 60 Hz."
msgstr ""

#: ../../docs/tutorials/rendering/jitter_stutter.rst:46
msgid ""
"This is generally not a problem, given that most monitors are 60 Hz, and "
"starting with Godot 3.1, a frame timer was introduced that tries to "
"synchronize with refresh as well as possible."
msgstr ""

#: ../../docs/tutorials/rendering/jitter_stutter.rst:50
msgid ""
"Sometimes only some objects appear to jitter (character or background). This "
"happens when they are processed in different time sources (one is processed "
"in the physics step while another is processed in the idle step). Godot 3.1 "
"does some improvements to this, from allowing kinematic bodies to be "
"animated in the regular ``_process()`` loop, to further fixes in the frame "
"timer."
msgstr ""

#: ../../docs/tutorials/rendering/jitter_stutter.rst:58
msgid ""
"You can use physics interpolation to mitigate physics-related jittering. See "
"`lawnjelly's smoothing-addon <https://github.com/lawnjelly/smoothing-"
"addon>`__ for an add-on that can be dropped into any project to enable "
"physics interpolation."
msgstr ""

#: ../../docs/tutorials/rendering/jitter_stutter.rst:63
msgid "Stutter"
msgstr ""

#: ../../docs/tutorials/rendering/jitter_stutter.rst:65
msgid ""
"Stutter may happen due to two different reasons. The first, and most obvious "
"one, is the game not being able to keep full framerate performance. Solving "
"this is game specific and will require optimization."
msgstr ""

#: ../../docs/tutorials/rendering/jitter_stutter.rst:69
msgid ""
"The second is more complicated, because it is often not associated to the "
"engine or game but the underlying operating system. Here is some information "
"regarding stutter on different OSs."
msgstr ""

#: ../../docs/tutorials/rendering/jitter_stutter.rst:73
msgid ""
"On platforms that support disabling V-Sync, stuttering can be made less "
"noticeable by disabling V-Sync in the project settings. This will however "
"cause tearing to appear, especially on monitors with low refresh rates. If "
"your monitor supports it, consider enabling variable refresh rate (G-Sync/"
"FreeSync) while leaving V-Sync enabled. This avoids mitigating some forms of "
"stuttering without introducing tearing."
msgstr ""

#: ../../docs/tutorials/rendering/jitter_stutter.rst:80
msgid ""
"Forcing your graphics card to use the maximum performance profile can also "
"help reduce stuttering, at the cost of increased GPU power draw."
msgstr ""

#: ../../docs/tutorials/rendering/jitter_stutter.rst:86
msgid ""
"Windows is known to cause stutter in windowed games. This mostly depends on "
"the hardware installed, drivers version and processes running in parallel (e."
"g. having many browser tabs open may cause stutter in a running game). To "
"avoid this, starting with 3.1, Godot raises the game priority to \"Above "
"Normal\". This helps considerably but may not completely eliminate stutter."
msgstr ""

#: ../../docs/tutorials/rendering/jitter_stutter.rst:92
msgid ""
"Eliminating this completely requires giving your game full privileges to "
"become \"time critical\", which is not advised. Some games may do it, but it "
"is advised to learn to live with this problem, as it is common for Windows "
"games and most users won't play games windowed (games that are played in a "
"window, e.g. puzzle games, will usually not exhibit this problem anyway)."
msgstr ""

#: ../../docs/tutorials/rendering/jitter_stutter.rst:98
msgid ""
"For fullscreen, Windows gives special priority to the game so stutter is no "
"longer visible and very rare. This is how most games are played."
msgstr ""

#: ../../docs/tutorials/rendering/jitter_stutter.rst:116
msgid ""
"Stutter may be visible on desktop Linux, but this is usually associated with "
"different video drivers and compositors. Some compositors may also trigger "
"this problem (e.g. KWin), so it is advised to try using a different one to "
"rule it out as the cause. Some window managers such as KWin and Xfwm allow "
"you to manually disable compositing, which can improve performance (at the "
"cost of tearing)."
msgstr ""

#: ../../docs/tutorials/rendering/jitter_stutter.rst:123
msgid ""
"There is no workaround for driver or compositor stuttering, other than "
"reporting it as an issue to the driver or compositor developers. Stutter may "
"be more present when playing in windowed mode as opposed to fullscreen, even "
"with compositing disabled."
msgstr ""

#: ../../docs/tutorials/rendering/jitter_stutter.rst:128
msgid ""
"`Feral GameMode <https://github.com/FeralInteractive/gamemode>`__ can be "
"used to automatically apply optimizations (such as forcing the GPU "
"performance profile) when running specific processes."
msgstr ""

#: ../../docs/tutorials/rendering/jitter_stutter.rst:135
msgid ""
"Generally, macOS is stutter-free, although recently some bugs were reported "
"when running on fullscreen (this is a macOS bug). If you have a machine "
"exhibiting this behavior, please let us know."
msgstr ""

#: ../../docs/tutorials/rendering/jitter_stutter.rst:142
msgid ""
"Generally, Android is stutter and jitter-free because the running activity "
"gets all the priority. That said, there may be problematic devices (older "
"Kindle Fire is known to be one). If you see this problem on Android, please "
"let us know."
msgstr ""

#: ../../docs/tutorials/rendering/jitter_stutter.rst:149
msgid ""
"iOS devices are generally stutter-free, but older devices running newer "
"versions of the operating system may exhibit problems. This is generally "
"unavoidable."
msgstr ""

#: ../../docs/tutorials/rendering/jitter_stutter.rst:153
msgid "Input lag"
msgstr ""

#: ../../docs/tutorials/rendering/jitter_stutter.rst:156
msgid "Project configuration"
msgstr ""

#: ../../docs/tutorials/rendering/jitter_stutter.rst:158
msgid ""
"On platforms that support disabling V-Sync, input lag can be made less "
"noticeable by disabling V-Sync in the project settings. This will however "
"cause tearing to appear, especially on monitors with low refresh rates."
msgstr ""

#: ../../docs/tutorials/rendering/jitter_stutter.rst:162
msgid ""
"Increasing the number of physics iterations per second can also reduce "
"physics-induced input latency. This is especially noticeable when using "
"physics interpolation (which improves smoothness but increases latency). To "
"do so, set **Physics > Common > Physics Ticks Per Second** to a value higher "
"than the default ``60``, or set ``Engine.physics_ticks_per_second`` at run-"
"time in a script. Values that are a multiple of the monitor refresh rate "
"(typically ``60``) work best when physics interpolation is disabled, as they "
"will avoid jitter. This means values such as ``120``, ``180`` and ``240`` "
"are good starting points. As a bonus, higher physics FPSes make tunneling "
"and physics instability issues less likely to occur."
msgstr ""

#: ../../docs/tutorials/rendering/jitter_stutter.rst:173
msgid ""
"The downside of increasing physics FPS is that CPU usage will increase, "
"which can lead to performance bottlenecks in games that have heavy physics "
"simulation code. This can be alleviated by increasing physics FPS only in "
"situations where low latency is critical, or by letting players adjust "
"physics FPS to match their hardware. However, different physics FPS will "
"lead to different outcomes in physics simulation, even when ``delta`` is "
"consistently used in your game logic. This can give certain players an "
"advantage over others. Therefore, allowing the player to change the physics "
"FPS themselves should be avoided for competitive multiplayer games."
msgstr ""

#: ../../docs/tutorials/rendering/jitter_stutter.rst:183
msgid ""
"Lastly, you can disable input buffering on a per-rendered frame basis by "
"calling ``Input.set_use_accumulated_input(false)`` in a script. This will "
"make it so the ``_input()`` and ``_unhandled_input()`` functions in your "
"scripts are called on every input, rather than accumulating inputs and "
"waiting for a frame to be rendered. Disabling input accumulation will "
"increase CPU usage, so it should be done with caution."
msgstr ""

#: ../../docs/tutorials/rendering/jitter_stutter.rst:191
msgid "Hardware/OS-specific"
msgstr ""

#: ../../docs/tutorials/rendering/jitter_stutter.rst:193
msgid ""
"If your monitor supports it, consider enabling variable refresh rate (G-Sync/"
"FreeSync) while leaving V-Sync enabled, then cap the framerate in the "
"project settings to a slightly lower value than your monitor's maximum "
"refresh rate as per `this page <https://blurbusters.com/howto-low-lag-vsync-"
"on/>`__. For example, on a 144 Hz monitor, you can set the project's "
"framerate cap to ``141``. This may be counterintuitive at first, but capping "
"the FPS below the maximum refresh rate range ensures that the OS never has "
"to wait for vertical blanking to finish. This leads to *similar* input lag "
"as V-Sync disabled with the same framerate cap (usually less than 1 ms "
"greater), but without any tearing."
msgstr ""

#: ../../docs/tutorials/rendering/jitter_stutter.rst:204
msgid ""
"This can be done by changing the **Application > Run > Max FPS** project "
"setting or assigning ``Engine.max_fps`` at run-time in a script."
msgstr ""

#: ../../docs/tutorials/rendering/jitter_stutter.rst:207
msgid ""
"On some platforms, you can also opt into a low-latency mode in the graphics "
"driver options (such as the NVIDIA Control Panel on Windows). The **Ultra** "
"setting will give you the lowest possible latency, at the cost of slightly "
"lower average framerates. Forcing the GPU to use the maximum performance "
"profile can also further reduce input lag, at the cost of higher power "
"consumption (and resulting heat/fan noise)."
msgstr ""

#: ../../docs/tutorials/rendering/jitter_stutter.rst:214
msgid ""
"Finally, make sure your monitor is running at its highest possible refresh "
"rate in the OS' display settings."
msgstr ""

#: ../../docs/tutorials/rendering/jitter_stutter.rst:217
msgid ""
"Also, ensure that your mouse is configured to use its highest polling rate "
"(typically 1,000 Hz for gaming mice, sometimes more). High USB polling rates "
"can however result in high CPU usage, so 500 Hz may be a safer bet on low-"
"end CPUs. If your mouse offers multiple :abbr:`DPI (Dots Per Inch)` "
"settings, consider also `using the highest possible setting and reducing in-"
"game sensitivity to reduce mouse latency <https://www.youtube.com/watch?"
"v=6AoRfv9W110>`__."
msgstr ""

#: ../../docs/tutorials/rendering/jitter_stutter.rst:223
msgid ""
"On Linux, disabling compositing in window managers that allow it (such as "
"KWin or Xfwm) can reduce input lag significantly."
msgstr ""

#: ../../docs/tutorials/rendering/jitter_stutter.rst:227
msgid "Reporting jitter, stutter or input lag problems"
msgstr ""

#: ../../docs/tutorials/rendering/jitter_stutter.rst:229
msgid ""
"If you are reporting a stutter or jitter problem (opening an issue) not "
"caused by any of the above reasons, please specify very clearly all the "
"information possible about device, operating system, driver versions, etc. "
"This may help to better troubleshoot it."
msgstr ""

#: ../../docs/tutorials/rendering/jitter_stutter.rst:234
msgid ""
"If you are reporting input lag problems, please include a capture made with "
"a high speed camera (such as your phone's slow motion video mode). The "
"capture **must** have both the screen and the input device visible so that "
"the number of frames between an input and the on-screen result can be "
"counted. Also, make sure to mention your monitor's refresh rate and your "
"input device's polling rate (especially for mice)."
msgstr ""

#: ../../docs/tutorials/rendering/jitter_stutter.rst:241
msgid ""
"Also, make sure to use the correct term (jitter, stutter, input lag) based "
"on the exhibited behavior. This will help understand your issue much faster. "
"Provide a project that can be used to reproduce the issue, and if possible, "
"include a screen capture demonstrating the bug."
msgstr ""

#: ../../docs/tutorials/scripting/index.rst:4
#, fuzzy
msgid ""
"This section covers programming languages and core features to code your "
"games in Godot."
msgstr "Koji jezici su podržani u Godot-u?"

#: ../../docs/tutorials/scripting/index.rst:7
msgid ""
"Here, you will find information that is not already covered in more specific "
"sections. For instance, to learn about inputs, we recommend you to read :ref:"
"`Inputs <toc-learn-features-inputs>`."
msgstr ""

#: ../../docs/tutorials/scripting/index.rst:14
msgid "The sections below each focus on a given programming language."
msgstr ""

#: ../../docs/tutorials/scripting/index.rst:25
msgid "Core features"
msgstr ""

#: ../../docs/tutorials/scripting/index.rst:27
msgid ""
"Some features are specific to the engine and are available in all supported "
"languages. Whether you code in GDScript, C#, or another language, the pages "
"below will help you make the most of Godot."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/index.rst:19
msgid ""
"See :ref:`doc_gdscript_grammar` if you are interested in writing a third-"
"party tool that interacts with GDScript, such as a linter or formatter."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:4
msgid "GDScript reference"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:6
msgid ""
":ref:`GDScript<doc_gdscript>` is a high-level, `object-oriented <https://en."
"wikipedia.org/wiki/Object-oriented_programming>`_, `imperative <https://en."
"wikipedia.org/wiki/Imperative_programming>`_, and `gradually typed <https://"
"en.wikipedia.org/wiki/Gradual_typing>`_ programming language built for "
"Godot. It uses an indentation-based syntax similar to languages like `Python "
"<https://en.wikipedia.org/wiki/Python_%28programming_language%29>`_. Its "
"goal is to be optimized for and tightly integrated with Godot Engine, "
"allowing great flexibility for content creation and integration."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:15
msgid "GDScript is entirely independent from Python and is not based on it."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:18
msgid "History"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:22
msgid ""
"Documentation about GDScript's history has been moved to the :ref:"
"`Frequently Asked Questions <doc_faq_what_is_gdscript>`."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:26
msgid "Example of GDScript"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:28
msgid ""
"Some people can learn better by taking a look at the syntax, so here's an "
"example of how GDScript looks."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:117
msgid ""
"If you have previous experience with statically typed languages such as C, C+"
"+, or C# but never used a dynamically typed one before, it is advised you "
"read this tutorial: :ref:`doc_gdscript_more_efficiently`."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:122
#: ../../docs/contributing/development/best_practices_for_engine_contributors.rst:16
msgid "Language"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:124
msgid ""
"In the following, an overview is given to GDScript. Details, such as which "
"methods are available to arrays or other objects, should be looked up in the "
"linked class descriptions."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:129
msgid "Identifiers"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:131
msgid ""
"Any string that restricts itself to alphabetic characters (``a`` to ``z`` "
"and ``A`` to ``Z``), digits (``0`` to ``9``) and ``_`` qualifies as an "
"identifier. Additionally, identifiers must not begin with a digit. "
"Identifiers are case-sensitive (``foo`` is different from ``FOO``)."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:136
msgid ""
"Identifiers may also contain most Unicode characters part of `UAX#31 "
"<https://www.unicode.org/reports/tr31/>`__. This allows you to use "
"identifier names written in languages other than English. Unicode characters "
"that are considered \"confusable\" for ASCII characters and emoji are not "
"allowed in identifiers."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:143
msgid "Keywords"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:145
msgid ""
"The following is the list of keywords supported by the language. Since "
"keywords are reserved words (tokens), they can't be used as identifiers. "
"Operators (like ``in``, ``not``, ``and`` or ``or``) and names of built-in "
"types as listed in the following sections are also reserved."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:150
msgid ""
"Keywords are defined in the `GDScript tokenizer <https://github.com/"
"godotengine/godot/blob/master/modules/gdscript/gdscript_tokenizer.cpp>`_ in "
"case you want to take a look under the hood."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:154
msgid "Keyword"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:156
msgid "if"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:156
#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:158
#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:160
msgid "See `if/else/elif`_."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:158
msgid "elif"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:160
msgid "else"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:162
#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1533
msgid "for"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:162
msgid "See for_."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:164
#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1521
msgid "while"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:164
msgid "See while_."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:166
#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1592
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:424
msgid "match"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:166
msgid "See match_."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:168
msgid "break"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:168
msgid "Exits the execution of the current ``for`` or ``while`` loop."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:170
msgid "continue"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:170
msgid ""
"Immediately skips to the next iteration of the ``for`` or ``while`` loop."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:172
msgid "pass"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:172
msgid ""
"Used where a statement is required syntactically but execution of code is "
"undesired, e.g. in empty functions."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:174
msgid "return"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:174
msgid "Returns a value from a function."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:176
msgid "class"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:176
msgid "Defines an inner class. See `Inner classes`_."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:178
msgid "class_name"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:178
msgid ""
"Defines the script as a globally accessible class with the specified name. "
"See `Registering named classes`_."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:180
msgid "extends"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:180
msgid "Defines what class to extend with the current class."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:182
msgid ""
"Tests whether a variable extends a given class, or is of a given built-in "
"type."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:184
msgid "in"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:184
msgid ""
"Tests whether a value is within a string, array, range, dictionary, or node. "
"When used with ``for``, it iterates through them instead of testing."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:186
msgid "Cast the value to a given type if possible."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:188
msgid "self"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:188
msgid "Refers to current class instance."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:190
msgid "signal"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:190
msgid "Defines a signal."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:192
msgid "func"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:192
msgid "Defines a function."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:194
msgid "static"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:194
msgid "Defines a static function or a static member variable."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:196
msgid "const"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:196
msgid "Defines a constant."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:198
msgid "enum"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:198
msgid "Defines an enum."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:200
msgid "var"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:200
msgid "Defines a variable."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:202
msgid "breakpoint"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:202
msgid ""
"Editor helper for debugger breakpoints. Unlike breakpoints created by "
"clicking in the gutter, ``breakpoint`` is stored in the script itself. This "
"makes it persistent across different machines when using version control."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:205
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:249
msgid "preload"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:205
msgid "Preloads a class or variable. See `Classes as resources`_."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:207
msgid "await"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:207
msgid ""
"Waits for a signal or a coroutine to finish. See `Awaiting for signals or "
"coroutines`_."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:209
msgid "yield"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:209
msgid "Previously used for coroutines. Kept as keyword for transition."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:211
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:241
msgid "assert"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:211
msgid ""
"Asserts a condition, logs error on failure. Ignored in non-debug builds. See "
"`Assert keyword`_."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:213
msgid "Used to represent that a function does not return any value."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:215
msgid "PI"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:215
msgid "PI constant."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:217
msgid "TAU"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:217
msgid "TAU constant."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:219
msgid "INF"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:219
msgid "Infinity constant. Used for comparisons and as result of calculations."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:221
msgid "NAN"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:221
msgid ""
"NAN (not a number) constant. Used as impossible result from calculations."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:225
#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:430
msgid "Operators"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:227
msgid "The following is the list of supported operators and their precedence."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:230
msgid "**Operator**"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:232
msgid "``(`` ``)``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:232
msgid "Grouping (highest priority)"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:234
msgid ""
"Parentheses are not really an operator, but allow you to explicitly specify "
"the precedence of an operation."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:237
msgid "``x[index]``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:237
#, fuzzy
msgid "Subscription"
msgstr "Uvod"

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:239
msgid "``x.attribute``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:239
msgid "Attribute reference"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:241
msgid "``foo()``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:241
msgid "Function call"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:243
msgid "``await x``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:243
msgid "`Awaiting for signals or coroutines`_"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:245
msgid "``x is Node``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:245
msgid "Type checking"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:247
msgid ""
"See also :ref:`is_instance_of() <class_@GDScript_method_is_instance_of>` "
"function."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:250
msgid "``x ** y``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:250
msgid "Power"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:252
msgid ""
"Multiplies ``x`` by itself ``y`` times, similar to calling :ref:`pow() "
"<class_@GlobalScope_method_pow>` function."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:255
msgid ""
"**Note:** In GDScript, the ``**`` operator is `left-associative <https://en."
"wikipedia.org/wiki/Operator_associativity>`_. See a detailed note after the "
"table."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:259
msgid "``~x``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:259
msgid "Bitwise NOT"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:0
msgid "``+x``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:0
msgid "``-x``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:261
msgid "Identity / Negation"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:0
msgid "``x * y``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:0
msgid "``x / y``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:0
msgid "``x % y``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:264
msgid "Multiplication / Division / Remainder"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:266
msgid ""
"The ``%`` operator is additionally used for :ref:`format strings "
"<doc_gdscript_printf>`."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:269
msgid ""
"**Note:** These operators have the same behavior as C++, which may be "
"unexpected for users coming from Python, JavaScript, etc. See a detailed "
"note after the table."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:0
msgid "``x + y``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:0
msgid "``x - y``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:273
msgid "Addition (or Concatenation) / Subtraction"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:0
msgid "``x << y``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:0
msgid "``x >> y``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:276
msgid "Bit shifting"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:279
msgid "``x & y``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:279
msgid "Bitwise AND"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:281
msgid "``x ^ y``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:281
msgid "Bitwise XOR"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:283
msgid "``x | y``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:283
msgid "Bitwise OR"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:0
msgid "``x == y``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:0
msgid "``x != y``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:0
msgid "``x < y``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:0
msgid "``x > y``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:0
msgid "``x <= y``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:0
msgid "``x >= y``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:285
msgid "Comparison"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:287
msgid "See a detailed note after the table."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:0
msgid "``x in y``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:0
msgid "``x not in y``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:292
msgid "Inclusion checking"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:294
msgid "``in`` is also used with the for_ keyword as part of the syntax."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:0
msgid "``not x``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:0
msgid "``!x``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:296
msgid "Boolean NOT and its :ref:`unrecommended <boolean_operators>` alias"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:0
msgid "``x and y``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:0
msgid "``x && y``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:299
msgid "Boolean AND and its :ref:`unrecommended <boolean_operators>` alias"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:0
msgid "``x or y``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:0
msgid "``x || y``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:302
msgid "Boolean OR and its :ref:`unrecommended <boolean_operators>` alias"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:305
msgid "``true_expr if cond else false_expr``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:305
msgid "Ternary if/else"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:307
msgid "``x as Node``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:307
msgid "`Type casting <casting_>`_"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:0
msgid "``x = y``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:0
msgid "``x += y``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:0
msgid "``x -= y``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:0
msgid "``x *= y``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:0
msgid "``x /= y``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:0
msgid "``x **= y``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:0
msgid "``x %= y``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:0
msgid "``x &= y``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:0
msgid "``x |= y``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:0
msgid "``x ^= y``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:0
msgid "``x <<= y``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:0
msgid "``x >>= y``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:309
msgid "Assignment (lowest priority)"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:311
msgid "You cannot use an assignment operator inside an expression."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:325
msgid "The behavior of some operators may differ from what you expect:"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:327
msgid ""
"If both operands of the ``/`` operator are :ref:`int <class_int>`, then "
"integer division is performed instead of fractional. For example ``5 / 2 == "
"2``, not ``2.5``. If this is not desired, use at least one :ref:`float "
"<class_float>` literal (``x / 2.0``), cast (``float(x) / y``), or multiply "
"by ``1.0`` (``x * 1.0 / y``)."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:329
msgid ""
"The ``%`` operator is only available for ints, for floats use the :ref:"
"`fmod() <class_@GlobalScope_method_fmod>` function."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:330
msgid ""
"For negative values, the ``%`` operator and ``fmod()`` use `truncation "
"<https://en.wikipedia.org/wiki/Truncation>`_ instead of rounding towards "
"negative infinity. This means that the remainder has a sign. If you need the "
"remainder in a mathematical sense, use the :ref:`posmod() "
"<class_@GlobalScope_method_posmod>` and :ref:`fposmod() "
"<class_@GlobalScope_method_fposmod>` functions instead."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:333
msgid ""
"The ``**`` operator is `left-associative <https://en.wikipedia.org/wiki/"
"Operator_associativity>`_. This means that ``2 ** 2 ** 3`` is equal to ``(2 "
"** 2) ** 3``. Use parentheses to explicitly specify precedence you need, for "
"example ``2 ** (2 ** 3)``."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:335
msgid ""
"The ``==`` and ``!=`` operators sometimes allow you to compare values of "
"different types (for example, ``1 == 1.0`` is true), but in other cases it "
"can cause a runtime error. If you're not sure about the types of the "
"operands, you can safely use the :ref:`is_same() "
"<class_@GlobalScope_method_is_same>` function (but note that it is more "
"strict about types and references). To compare floats, use the :ref:"
"`is_equal_approx() <class_@GlobalScope_method_is_equal_approx>` and :ref:"
"`is_zero_approx() <class_@GlobalScope_method_is_zero_approx>` functions "
"instead."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:341
msgid "Literals"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:344
msgid "**Example(s)**"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:346
msgid "Null value"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:348
msgid "``false``, ``true``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:348
msgid "Boolean values"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:350
msgid "``45``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:350
msgid "Base 10 integer"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:352
msgid "``0x8f51``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:352
msgid "Base 16 (hexadecimal) integer"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:354
msgid "``0b101010``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:354
msgid "Base 2 (binary) integer"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:356
msgid "``3.14``, ``58.1e-10``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:356
msgid "Floating-point number (real)"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:358
msgid "``\"Hello\"``, ``'Hi'``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:358
msgid "Regular strings"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:360
msgid "``\"\"\"Hello\"\"\"``, ``'''Hi'''``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:360
msgid "Triple-quoted regular strings"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:362
msgid "``r\"Hello\"``, ``r'Hi'``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:362
msgid "Raw strings"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:364
msgid "``r\"\"\"Hello\"\"\"``, ``r'''Hi'''``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:364
msgid "Triple-quoted raw strings"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:366
msgid "``&\"name\"``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:366
#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:704
#, fuzzy
msgid ":ref:`StringName <class_StringName>`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:368
msgid "``^\"Node/Label\"``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:368
#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:711
msgid ":ref:`NodePath <class_NodePath>`"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:371
msgid ""
"There are also two constructs that look like literals, but actually are not:"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:374
#: ../../docs/tutorials/scripting/gdscript/gdscript_format_string.rst:249
#: ../../docs/tutorials/scripting/gdscript/gdscript_format_string.rst:271
#: ../../docs/tutorials/scripting/gdscript/gdscript_format_string.rst:284
msgid "**Example**"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:376
msgid "``$NodePath``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:376
msgid "Shorthand for ``get_node(\"NodePath\")``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:378
msgid "``%UniqueNode``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:378
msgid "Shorthand for ``get_node(\"%UniqueNode\")``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:381
msgid ""
"Integers and floats can have their numbers separated with ``_`` to make them "
"more readable. The following ways to write numbers are all valid::"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:389
msgid "**Regular string literals** can contain the following escape sequences:"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:392
msgid "**Escape sequence**"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:392
msgid "**Expands to**"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:394
msgid "``\\n``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:394
msgid "Newline (line feed)"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:396
msgid "``\\t``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:396
msgid "Horizontal tab character"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:398
msgid "``\\r``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:398
msgid "Carriage return"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:400
msgid "``\\a``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:400
msgid "Alert (beep/bell)"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:402
msgid "``\\b``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:402
msgid "Backspace"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:404
msgid "``\\f``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:404
msgid "Formfeed page break"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:406
msgid "``\\v``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:406
msgid "Vertical tab character"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:408
msgid "``\\\"``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:408
msgid "Double quote"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:410
msgid "``\\'``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:410
msgid "Single quote"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:412
msgid "``\\\\``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:412
msgid "Backslash"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:414
msgid "``\\uXXXX``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:414
msgid "UTF-16 Unicode codepoint ``XXXX`` (hexadecimal, case-insensitive)"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:418
msgid "``\\UXXXXXX``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:418
msgid "UTF-32 Unicode codepoint ``XXXXXX`` (hexadecimal, case-insensitive)"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:423
#, fuzzy
msgid ""
"There are two ways to represent an escaped Unicode character above "
"``0xFFFF``:"
msgstr "Ne postoje ograničenja prilikom korištenja Godot-a"

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:425
msgid ""
"as a `UTF-16 surrogate pair <https://en.wikipedia.org/wiki/"
"UTF-16#Code_points_from_U+010000_to_U+10FFFF>`_ ``\\uXXXX\\uXXXX``."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:426
msgid "as a single UTF-32 codepoint ``\\UXXXXXX``."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:428
msgid ""
"Also, using ``\\`` followed by a newline inside a string will allow you to "
"continue it in the next line, without inserting a newline character in the "
"string itself."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:431
msgid ""
"A string enclosed in quotes of one type (for example ``\"``) can contain "
"quotes of another type (for example ``'``) without escaping. Triple-quoted "
"strings allow you to avoid escaping up to two consecutive quotes of the same "
"type (unless they are adjacent to the string edges)."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:435
msgid ""
"**Raw string literals** always encode the string as it appears in the source "
"code. This is especially useful for regular expressions. Raw strings do not "
"process escape sequences, but you can \"escape\" a quote or backslash (they "
"replace themselves)."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:444
msgid "GDScript also supports :ref:`format strings <doc_gdscript_printf>`."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:447
#, fuzzy
msgid "Annotations"
msgstr "Funkcije"

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:449
msgid ""
"There are some special tokens in GDScript that act like keywords but are "
"not, they are *annotations* instead. Every annotation start with the ``@`` "
"character and is specified by a name. A detailed description and example for "
"each annotation can be found inside the :ref:`GDScript class reference "
"<class_@GDScript>`."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:454
msgid ""
"Annotations affect how the script is treated by external tools and usually "
"don't change the behavior."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:457
msgid "For instance, you can use it to export a value to the editor::"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:462
msgid ""
"For more information about exporting properties, read the :ref:`GDScript "
"exports <doc_gdscript_exports>` article."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:465
msgid ""
"Any constant expression compatible with the required argument type can be "
"passed as an annotation argument value::"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:472
msgid ""
"Annotations can be specified one per line or all in the same line. They "
"affect the next statement that isn't an annotation. Annotations can have "
"arguments sent between parentheses and separated by commas."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:476
msgid "Both of these are the same::"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:487
msgid "``@onready`` annotation"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:489
msgid ""
"When using nodes, it's common to desire to keep references to parts of the "
"scene in a variable. As scenes are only warranted to be configured when "
"entering the active scene tree, the sub-nodes can only be obtained when a "
"call to ``Node._ready()`` is made."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:502
msgid ""
"This can get a little cumbersome, especially when nodes and external "
"references pile up. For this, GDScript has the ``@onready`` annotation, that "
"defers initialization of a member variable until ``_ready()`` is called. It "
"can replace the above code with a single line::"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:511
msgid ""
"Applying ``@onready`` and any ``@export`` annotation to the same variable "
"doesn't work as you might expect. The ``@onready`` annotation will cause the "
"default value to be set after the ``@export`` takes effect and will override "
"it::"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:529
msgid ""
"Therefore, the ``ONREADY_WITH_EXPORT`` warning is generated, which is "
"treated as an error by default. We do not recommend disabling or ignoring it."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:533
msgid "Comments"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:535
msgid ""
"Anything from a ``#`` to the end of the line is ignored and is considered a "
"comment."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:544
msgid ""
"In the Godot script editor, special keywords are highlighted within comments "
"to bring the user's attention to specific comments:"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:547
msgid ""
"**Critical** *(appears in red)*: ``ALERT``, ``ATTENTION``, ``CAUTION``, "
"``CRITICAL``, ``DANGER``, ``SECURITY``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:549
msgid ""
"**Warning** *(appears in yellow)*: ``BUG``, ``DEPRECATED``, ``FIXME``, "
"``HACK``, ``TASK``, ``TBD``, ``TODO``, ``WARNING``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:551
msgid ""
"**Notice** *(appears in green)*: ``INFO``, ``NOTE``, ``NOTICE``, ``TEST``, "
"``TESTING``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:554
msgid ""
"These keywords are case-sensitive, so they must be written in uppercase for "
"them to be recognized:"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:564
msgid ""
"The list of highlighted keywords and their colors can be changed in the "
"**Text Editor > Theme > Comment Markers** section of the Editor Settings."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:570
#, fuzzy
msgid "Code regions"
msgstr "Uvod / Početak"

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:572
msgid ""
"Code regions are special types of comments that the script editor "
"understands as *foldable regions*. This means that after writing code region "
"comments, you can collapse and expand the region by clicking the arrow that "
"appears at the left of the comment. This arrow appears within a purple "
"square to be distinguishable from standard code folding."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:578
msgid "The syntax is as follows:"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:596
msgid ""
"To create a code region quickly, select several lines in the script editor, "
"right-click the selection then choose **Create Code Region**. The region "
"description will be selected automatically for editing."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:600
msgid "It is possible to nest code regions within other code regions."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:602
#, fuzzy
msgid "Here's a concrete usage example of code regions:"
msgstr "Ne postoje ograničenja prilikom korištenja Godot-a"

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:624
msgid ""
"This can be useful to organize large chunks of code into easier to "
"understand sections. However, remember that external editors generally don't "
"support this feature, so make sure your code is easy to follow even when not "
"relying on folding code regions."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:631
msgid ""
"Individual functions and indented sections (such as ``if`` and ``for``) can "
"*always* be collapsed in the script editor. This means you should avoid "
"using a code region to contain a single function or indented section, as it "
"won't bring much of a benefit. Code regions work best when they're used to "
"group multiple elements together."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:638
#, fuzzy
msgid "Line continuation"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:640
msgid ""
"A line of code in GDScript can be continued on the next line by using a "
"backslash (``\\``). Add one at the end of a line and the code on the next "
"line will act like it's where the backslash is. Here is an example:"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:649
msgid "A line can be continued multiple times like this:"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:659
msgid "Built-in types"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:661
msgid ""
"Built-in types are stack-allocated. They are passed as values. This means a "
"copy is created on each assignment or when passing them as arguments to "
"functions. The exceptions are ``Object``, ``Array``, ``Dictionary``, and "
"packed arrays (such as ``PackedByteArray``), which are passed by reference "
"so they are shared. All arrays, ``Dictionary``, and some objects (``Node``, "
"``Resource``) have a ``duplicate()`` method that allows you to make a copy."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:669
msgid "Basic built-in types"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:671
msgid "A variable in GDScript can be assigned to several built-in types."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:676
msgid ""
"``null`` is an empty data type that contains no information and can not be "
"assigned any other value."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:680
msgid ":ref:`bool <class_bool>`"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:682
msgid "Short for \"boolean\", it can only contain ``true`` or ``false``."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:685
#, fuzzy
msgid ":ref:`int <class_int>`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:687
msgid ""
"Short for \"integer\", it stores whole numbers (positive and negative). It "
"is stored as a 64-bit value, equivalent to ``int64_t`` in C++."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:691
msgid ":ref:`float <class_float>`"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:693
msgid ""
"Stores real numbers, including decimals, using floating-point values. It is "
"stored as a 64-bit value, equivalent to ``double`` in C++. Note: Currently, "
"data structures such as ``Vector2``, ``Vector3``, and ``PackedFloat32Array`` "
"store 32-bit single-precision ``float`` values."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:699
msgid ":ref:`String <class_String>`"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:701
msgid ""
"A sequence of characters in `Unicode format <https://en.wikipedia.org/wiki/"
"Unicode>`_."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:706
msgid ""
"An immutable string that allows only one instance of each name. They are "
"slower to create and may result in waiting for locks when multithreading. In "
"exchange, they're very fast to compare, which makes them good candidates for "
"dictionary keys."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:713
msgid ""
"A pre-parsed path to a node or a node property.  It can be easily assigned "
"to, and from, a String. They are useful to interact with the tree to get a "
"node, or affecting properties like with :ref:`Tweens <class_Tween>`."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:718
msgid "Vector built-in types"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:721
msgid ":ref:`Vector2 <class_Vector2>`"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:723
msgid ""
"2D vector type containing ``x`` and ``y`` fields. Can also be accessed as an "
"array."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:727
#, fuzzy
msgid ":ref:`Vector2i <class_Vector2i>`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:729
msgid ""
"Same as a Vector2 but the components are integers. Useful for representing "
"items in a 2D grid."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:733
msgid ":ref:`Rect2 <class_Rect2>`"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:735
msgid ""
"2D Rectangle type containing two vectors fields: ``position`` and ``size``. "
"Also contains an ``end`` field which is ``position + size``."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:739
msgid ":ref:`Vector3 <class_Vector3>`"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:741
msgid ""
"3D vector type containing ``x``, ``y`` and ``z`` fields. This can also be "
"accessed as an array."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:745
#, fuzzy
msgid ":ref:`Vector3i <class_Vector3i>`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:747
msgid ""
"Same as Vector3 but the components are integers. Can be use for indexing "
"items in a 3D grid."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:751
msgid ":ref:`Transform2D <class_Transform2D>`"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:753
msgid "3×2 matrix used for 2D transforms."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:756
msgid ":ref:`Plane <class_Plane>`"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:758
msgid ""
"3D Plane type in normalized form that contains a ``normal`` vector field and "
"a ``d`` scalar distance."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:762
#, fuzzy
msgid ":ref:`Quaternion <class_Quaternion>`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:764
msgid ""
"Quaternion is a datatype used for representing a 3D rotation. It's useful "
"for interpolating rotations."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:768
msgid ":ref:`AABB <class_AABB>`"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:770
msgid ""
"Axis-aligned bounding box (or 3D box) contains 2 vectors fields: "
"``position`` and ``size``. Also contains an ``end`` field which is "
"``position + size``."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:775
msgid ":ref:`Basis <class_Basis>`"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:777
msgid ""
"3x3 matrix used for 3D rotation and scale. It contains 3 vector fields "
"(``x``, ``y`` and ``z``) and can also be accessed as an array of 3D vectors."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:782
#, fuzzy
msgid ":ref:`Transform3D <class_Transform3D>`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:784
msgid ""
"3D Transform contains a Basis field ``basis`` and a Vector3 field ``origin``."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:788
msgid "Engine built-in types"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:791
msgid ":ref:`Color <class_Color>`"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:793
msgid ""
"Color data type contains ``r``, ``g``, ``b``, and ``a`` fields. It can also "
"be accessed as ``h``, ``s``, and ``v`` for hue/saturation/value."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:797
msgid ":ref:`RID <class_RID>`"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:799
msgid "Resource ID (RID). Servers use generic RIDs to reference opaque data."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:802
msgid ":ref:`Object <class_Object>`"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:804
msgid "Base class for anything that is not a built-in type."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:807
msgid "Container built-in types"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:810
msgid ":ref:`Array <class_Array>`"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:812
msgid ""
"Generic sequence of arbitrary object types, including other arrays or "
"dictionaries (see below). The array can resize dynamically. Arrays are "
"indexed starting from index ``0``. Negative indices count from the end."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:827
msgid "Typed arrays"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:829
msgid ""
"Godot 4.0 added support for typed arrays. On write operations, Godot checks "
"that element values match the specified type, so the array cannot contain "
"invalid values. The GDScript static analyzer takes typed arrays into "
"account, however array methods like ``front()`` and ``back()`` still have "
"the ``Variant`` return type."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:834
msgid ""
"Typed arrays have the syntax ``Array[Type]``, where ``Type`` can be any "
"``Variant`` type, native or user class, or enum. Nested array types (like "
"``Array[Array[int]]``) are not supported."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:845
msgid "``Array`` and ``Array[Variant]`` are the same thing."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:849
msgid ""
"Arrays are passed by reference, so the array element type is also an "
"attribute of the in-memory structure referenced by a variable in runtime. "
"The static type of a variable restricts the structures that it can reference "
"to. Therefore, you **cannot** assign an array with a different element type, "
"even if the type is a subtype of the required type."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:854
msgid ""
"If you want to *convert* a typed array, you can create a new array and use "
"the :ref:`Array.assign() <class_Array_method_assign>` method::"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:869
msgid ""
"The only exception was made for the ``Array`` (``Array[Variant]``) type, for "
"user convenience and compatibility with old code. However, operations on "
"untyped arrays are considered unsafe."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:873
msgid "Packed arrays"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:875
msgid ""
"GDScript arrays are allocated linearly in memory for speed. Large arrays "
"(more than tens of thousands of elements) may however cause memory "
"fragmentation. If this is a concern, special types of arrays are available. "
"These only accept a single data type. They avoid memory fragmentation and "
"use less memory, but are atomic and tend to run slower than generic arrays. "
"They are therefore only recommended to use for large data sets:"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:882
msgid ""
":ref:`PackedByteArray <class_PackedByteArray>`: An array of bytes (integers "
"from 0 to 255)."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:883
msgid ""
":ref:`PackedInt32Array <class_PackedInt32Array>`: An array of 32-bit "
"integers."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:884
msgid ""
":ref:`PackedInt64Array <class_PackedInt64Array>`: An array of 64-bit "
"integers."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:885
msgid ""
":ref:`PackedFloat32Array <class_PackedFloat32Array>`: An array of 32-bit "
"floats."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:886
msgid ""
":ref:`PackedFloat64Array <class_PackedFloat64Array>`: An array of 64-bit "
"floats."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:887
msgid ""
":ref:`PackedStringArray <class_PackedStringArray>`: An array of strings."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:888
msgid ""
":ref:`PackedVector2Array <class_PackedVector2Array>`: An array of :ref:"
"`Vector2 <class_Vector2>` values."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:889
msgid ""
":ref:`PackedVector3Array <class_PackedVector3Array>`: An array of :ref:"
"`Vector3 <class_Vector3>` values."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:890
msgid ""
":ref:`PackedColorArray <class_PackedColorArray>`: An array of :ref:`Color "
"<class_Color>` values."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:893
msgid ":ref:`Dictionary <class_Dictionary>`"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:895
msgid "Associative container which contains values referenced by unique keys."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:908
msgid ""
"Lua-style table syntax is also supported. Lua-style uses ``=`` instead of ``:"
"`` and doesn't use quotes to mark string keys (making for slightly less to "
"write). However, keys written in this form can't start with a digit (like "
"any GDScript identifier), and must be string literals."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:922
msgid ""
"To add a key to an existing dictionary, access it like an existing key and "
"assign to it::"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:938
msgid ""
"The bracket syntax can be used to access properties of any :ref:"
"`class_Object`, not just Dictionaries. Keep in mind it will cause a script "
"error when attempting to index a non-existing property. To avoid this, use "
"the :ref:`Object.get() <class_Object_method_get>` and :ref:`Object.set() "
"<class_Object_method_set>` methods instead."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:945
#, fuzzy
msgid ":ref:`Signal <class_Signal>`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:947
msgid ""
"A signal is a message that can be emitted by an object to those who want to "
"listen to it. The Signal type can be used for passing the emitter around."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:950
msgid ""
"Signals are better used by getting them from actual objects, e.g. ``$Button."
"button_up``."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:953
#, fuzzy
msgid ":ref:`Callable <class_Callable>`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:955
msgid ""
"Contains an object and a function, which is useful for passing functions as "
"values (e.g. when connecting to signals)."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:958
msgid ""
"Getting a method as a member returns a callable. ``var x = $Sprite2D."
"rotate`` will set the value of ``x`` to a callable with ``$Sprite2D`` as the "
"object and ``rotate`` as the method."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:962
msgid "You can call it using the ``call`` method: ``x.call(PI)``."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:965
msgid "Data"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:968
#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:85
#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:152
#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:223
msgid "Variables"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:970
msgid ""
"Variables can exist as class members or local to functions. They are created "
"with the ``var`` keyword and may, optionally, be assigned a value upon "
"initialization."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:981
msgid ""
"Variables can optionally have a type specification. When a type is "
"specified, the variable will be forced to have always that same type, and "
"trying to assign an incompatible value will raise an error."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:985
msgid ""
"Types are specified in the variable declaration using a ``:`` (colon) symbol "
"after the variable name, followed by the type."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:993
msgid ""
"If the variable is initialized within the declaration, the type can be "
"inferred, so it's possible to omit the type name::"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:999
msgid ""
"Type inference is only possible if the assigned value has a defined type, "
"otherwise it will raise an error."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1002
msgid "Valid types are:"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1004
msgid "Built-in types (Array, Vector2, int, String, etc.)."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1005
msgid "Engine classes (Node, Resource, Reference, etc.)."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1006
msgid ""
"Constant names if they contain a script resource (``MyScript`` if you "
"declared ``const MyScript = preload(\"res://my_script.gd\")``)."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1007
msgid ""
"Other classes in the same script, respecting scope (``InnerClass."
"NestedClass`` if you declared ``class NestedClass`` inside the ``class "
"InnerClass`` in the same scope)."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1008
msgid "Script classes declared with the ``class_name`` keyword."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1009
msgid "Autoloads registered as singletons."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1013
msgid ""
"While ``Variant`` is a valid type specification, it's not an actual type. It "
"only means there's no set type and is equivalent to not having a static type "
"at all. Therefore, inference is not allowed by default for ``Variant``, "
"since it's likely a mistake."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1018
msgid ""
"You can turn off this check, or make it only a warning, by changing it in "
"the project settings. See :ref:`doc_gdscript_warning_system` for details."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1022
msgid "Initialization order"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1024
#, fuzzy
msgid "Member variables are initialized in the following order:"
msgstr "Glavna dokumentacija za sajt je podeljena na sledeća poglavlja:"

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1026
msgid ""
"Depending on the variable's static type, the variable is either ``null`` "
"(untyped variables and objects) or has a default value of the type (``0`` "
"for ``int``, ``false`` for ``bool``, etc.)."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1029
msgid ""
"The specified values are assigned in the order of the variables in the "
"script, from top to bottom. - *(Only for ``Node``-derived classes)* If the "
"``@onready`` annotation is applied to a variable, its initialization is "
"deferred to step 5."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1032
msgid "If defined, the ``_init()`` method is called."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1033
msgid ""
"When instantiating scenes and resources, the exported values are assigned."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1034
msgid ""
"*(Only for ``Node``-derived classes)* ``@onready`` variables are initialized."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1035
msgid ""
"*(Only for ``Node``-derived classes)* If defined, the ``_ready()`` method is "
"called."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1039
msgid ""
"You can specify a complex expression as a variable initializer, including "
"function calls. Make sure the variables are initialized in the correct "
"order, otherwise your values may be overwritten. For example::"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1055
msgid "Will print::"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1061
msgid ""
"To fix this, move the ``_data`` variable definition above the ``a`` "
"definition or remove the empty dictionary assignment (``= {}``)."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1065
msgid "Static variables"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1067
msgid "A class member variable can be declared static::"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1071
msgid ""
"Static variables belong to the class, not instances. This means that static "
"variables share values between multiple instances, unlike regular member "
"variables."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1074
msgid ""
"From inside a class, you can access static variables from any function, both "
"static and non-static. From outside the class, you can access static "
"variables using the class or an instance (the second is not recommended as "
"it is less readable)."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1080
msgid ""
"The ``@export`` and ``@onready`` annotations cannot be applied to a static "
"variable. Local variables cannot be static."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1083
msgid ""
"The following example defines a ``Person`` class with a static variable "
"named ``max_id``. We increment the ``max_id`` in the ``_init()`` function. "
"This makes it easy to keep track of the number of ``Person`` instances in "
"our game."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1102
msgid ""
"In this code, we create two instances of our ``Person`` class and check that "
"the class and every instance have the same ``max_id`` value, because the "
"variable is static and accessible to every instance."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1121
msgid "Static variables can have type hints, setters and getters::"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1131
msgid "A base class static variable can also be accessed via a child class::"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1147
msgid "``@static_unload`` annotation"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1149
msgid ""
"Since GDScript classes are resources, having static variables in a script "
"prevents it from being unloaded even if there are no more instances of that "
"class and no other references left. This can be important if static "
"variables store large amounts of data or hold references to other project "
"resources, such as scenes. You should clean up this data manually, or use "
"the :ref:`@static_unload <class_@GDScript_annotation_@static_unload>` "
"annotation if static variables don't store important data and can be reset."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1157
msgid ""
"Currently, due to a bug, scripts are never freed, even if ``@static_unload`` "
"annotation is used."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1159
msgid ""
"Note that ``@static_unload`` applies to the entire script (including inner "
"classes) and must be placed at the top of the script, before ``class_name`` "
"and ``extends``::"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1166
msgid "See also `Static functions`_ and `Static constructor`_."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1169
#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:89
msgid "Casting"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1171
msgid ""
"Values assigned to typed variables must have a compatible type. If it's "
"needed to coerce a value to be of a certain type, in particular for object "
"types, you can use the casting operator ``as``."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1175
msgid ""
"Casting between object types results in the same object if the value is of "
"the same type or a subtype of the cast type."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1183
msgid ""
"If the value is not a subtype, the casting operation will result in a "
"``null`` value."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1190
msgid ""
"For built-in types, they will be forcibly converted if possible, otherwise "
"the engine will raise an error."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1199
msgid ""
"Casting is also useful to have better type-safe variables when interacting "
"with the scene tree::"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1209
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:22
#: ../../docs/tutorials/scripting/how_to_read_the_godot_api.rst:129
#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:297
#: ../../docs/tutorials/shaders/shaders_style_guide.rst:312
#: ../../docs/contributing/development/core_and_modules/object_class.rst:103
msgid "Constants"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1211
msgid ""
"Constants are values you cannot change when the game is running. Their value "
"must be known at compile-time. Using the ``const`` keyword allows you to "
"give a constant value a name. Trying to assign a value to a constant after "
"it's declared will give you an error."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1216
msgid "We recommend using constants whenever a value is not meant to change."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1229
msgid ""
"Although the type of constants is inferred from the assigned value, it's "
"also possible to add explicit type specification::"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1235
msgid "Assigning a value of an incompatible type will raise an error."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1237
msgid ""
"You can also create constants inside a function, which is useful to name "
"local magic values."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1242
msgid ""
"Since objects, arrays and dictionaries are passed by reference, constants "
"are \"flat\". This means that if you declare a constant array or dictionary, "
"it can still be modified afterwards. They can't be reassigned with another "
"value though."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1247
msgid "Enums"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1249
msgid ""
"Enums are basically a shorthand for constants, and are pretty useful if you "
"want to assign consecutive integers to some constant."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1263
msgid ""
"If you pass a name to the enum, it will put all the keys inside a constant :"
"ref:`Dictionary <class_Dictionary>` of that name. This means all constant "
"methods of a dictionary can also be used with a named enum."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1267
msgid ""
"Keys in a named enum are not registered as global constants. They should be "
"accessed prefixed by the enum's name (``Name.KEY``)."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1292
#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:564
msgid "Functions"
msgstr "Funkcije"

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1294
msgid ""
"Functions always belong to a `class <Classes_>`_. The scope priority for "
"variable look-up is: local → class member → global. The ``self`` variable is "
"always available and is provided as an option for accessing class members, "
"but is not always required (and should *not* be sent as the function's first "
"argument, unlike Python)."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1307
msgid ""
"A function can ``return`` at any point. The default return value is ``null``."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1309
msgid ""
"If a function contains only one line of code, it can be written on one line::"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1317
msgid ""
"Functions can also have type specification for the arguments and for the "
"return value. Types for arguments can be added in a similar way to "
"variables::"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1323
msgid ""
"If a function argument has a default value, it's possible to infer the type::"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1328
msgid ""
"The return type of the function can be specified after the arguments list "
"using the arrow token (``->``)::"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1334
msgid ""
"Functions that have a return type **must** return a proper value. Setting "
"the type as ``void`` means the function doesn't return anything. Void "
"functions can return early with the ``return`` keyword, but they can't "
"return any value."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1343
msgid ""
"Non-void functions must **always** return a value, so if your code has "
"branching statements (such as an ``if``/``else`` construct), all the "
"possible paths must have a return. E.g., if you have a ``return`` inside an "
"``if`` block but not after it, the editor will raise an error because if the "
"block is not executed, the function won't have a valid value to return."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1351
msgid "Referencing functions"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1353
msgid ""
"Functions are first-class items in terms of the :ref:`Callable "
"<class_Callable>` object. Referencing a function by name without calling it "
"will automatically generate the proper callable. This can be used to pass "
"functions as arguments."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1373
msgid ""
"Callables **must** be called with the ``call`` method. You cannot use the "
"``()`` operator directly. This behavior is implemented to avoid performance "
"issues on direct function calls."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1378
#, fuzzy
msgid "Lambda functions"
msgstr "Uvod"

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1380
msgid ""
"Lambda functions allow you to declare functions that do not belong to a "
"class. Instead a :ref:`Callable <class_Callable>` object is created and "
"assigned to a variable directly. This can be useful to create Callables to "
"pass around without polluting the class scope."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1388
msgid "Lambda functions can be named for debugging purposes::"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1393
msgid ""
"Note that if you want to return a value from a lambda, an explicit "
"``return`` is required (you can't omit ``return``)::"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1399
msgid ""
"Lambda functions capture the local environment. Local variables are passed "
"by value, so they won't be updated in the lambda if changed in the local "
"function::"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1407
msgid ""
"The values of the outer scope behave like constants. Therefore, if you "
"declare an array or dictionary, it can still be modified afterwards."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1410
msgid "Static functions"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1412
msgid ""
"A function can be declared static. When a function is static, it has no "
"access to the instance member variables or ``self``. A static function has "
"access to static variables. Also static functions are useful to make "
"libraries of helper functions::"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1418
msgid "Lambdas cannot be declared static."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1420
msgid "See also `Static variables`_ and `Static constructor`_."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1423
msgid "Statements and control flow"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1425
msgid ""
"Statements are standard and can be assignments, function calls, control flow "
"structures, etc (see below). ``;`` as a statement separator is entirely "
"optional."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1430
msgid "Expressions"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1432
msgid ""
"Expressions are sequences of operators and their operands in orderly "
"fashion. An expression by itself can be a statement too, though only calls "
"are reasonable to use as statements since other expressions don't have side "
"effects."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1435
msgid ""
"Expressions return values that can be assigned to valid targets. Operands to "
"some operator can be another expression. An assignment is not an expression "
"and thus does not return any value."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1438
#, fuzzy
msgid "Here are some examples of expressions::"
msgstr "Ne postoje ograničenja prilikom korištenja Godot-a"

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1454
msgid ""
"Identifiers, attributes, and subscripts are valid assignment targets. Other "
"expressions cannot be on the left side of an assignment."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1458
msgid "if/else/elif"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1460
msgid ""
"Simple conditions are created by using the ``if``/``else``/``elif`` syntax. "
"Parenthesis around conditions are allowed, but not required. Given the "
"nature of the tab-based indentation, ``elif`` can be used instead of "
"``else``/``if`` to maintain a level of indentation."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1474
msgid "Short statements can be written on the same line as the condition::"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1481
msgid ""
"Sometimes, you might want to assign a different initial value based on a "
"boolean expression. In this case, ternary-if expressions come in handy::"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1487
msgid ""
"Ternary-if expressions can be nested to handle more than 2 cases. When "
"nesting ternary-if expressions, it is recommended to wrap the complete "
"expression over multiple lines to preserve readability::"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1510
msgid ""
"You may also wish to check if a value is contained within something. You can "
"use an ``if`` statement combined with the ``in`` operator to accomplish "
"this::"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1523
msgid ""
"Simple loops are created by using ``while`` syntax. Loops can be broken "
"using ``break`` or continued using ``continue`` (which skips to the next "
"iteration of the loop without executing any further code in the current "
"iteration):"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1535
msgid ""
"To iterate through a range, such as an array or table, a *for* loop is used. "
"When iterating over an array, the current array element is stored in the "
"loop variable. When iterating over a dictionary, the *key* is stored in the "
"loop variable."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1570
msgid ""
"If you want to assign values on an array as it is being iterated through, it "
"is best to use ``for i in array.size()``."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1579
msgid ""
"The loop variable is local to the for-loop and assigning to it will not "
"change the value on the array. Objects passed by reference (such as nodes) "
"can still be manipulated by calling methods on the loop variable."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1594
msgid ""
"A ``match`` statement is used to branch execution of a program. It's the "
"equivalent of the ``switch`` statement found in many other languages, but "
"offers some additional features."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1599
msgid ""
"``match`` is more type strict than the ``==`` operator. For example ``1`` "
"will **not** match ``1.0``. The only exception is ``String`` vs "
"``StringName`` matching: for example, the String ``\"hello\"`` is considered "
"equal to the StringName ``&\"hello\"``."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1603
msgid "Basic syntax"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1615
msgid "Crash-course for people who are familiar with switch statements"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1617
msgid "Replace ``switch`` with ``match``."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1618
msgid "Remove ``case``."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1619
msgid "Remove any ``break``\\ s."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1620
msgid "Change ``default`` to a single underscore."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1623
#, fuzzy
msgid "Control flow"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1625
msgid ""
"The patterns are matched from top to bottom. If a pattern matches, the first "
"corresponding block will be executed. After that, the execution continues "
"below the ``match`` statement."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1630
msgid ""
"The special ``continue`` behavior in ``match`` supported in 3.x was removed "
"in Godot 4.0."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1632
msgid "The following pattern types are available:"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1643
msgid "Literal pattern"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1635
msgid "Matches a `literal <Literals_>`_::"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1654
msgid "Expression pattern"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1646
msgid ""
"Matches a constant expression, an identifier, or an attribute access (``A."
"B``)::"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1667
msgid "Wildcard pattern"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1657
msgid "This pattern matches everything. It's written as a single underscore."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1659
msgid ""
"It can be used as the equivalent of the ``default`` in a ``switch`` "
"statement in other languages::"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1679
msgid "Binding pattern"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1670
msgid ""
"A binding pattern introduces a new variable. Like the wildcard pattern, it "
"matches everything - and also gives that value a name. It's especially "
"useful in array and dictionary patterns::"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1700
msgid "Array pattern"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1682
msgid ""
"Matches an array. Every single element of the array pattern is a pattern "
"itself, so you can nest them."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1684
msgid ""
"The length of the array is tested first, it has to be the same size as the "
"pattern, otherwise the pattern doesn't match."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1686
msgid ""
"**Open-ended array**: An array can be bigger than the pattern by making the "
"last subpattern ``..``."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1688
msgid "Every subpattern has to be comma-separated."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1727
msgid "Dictionary pattern"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1703
msgid ""
"Works in the same way as the array pattern. Every key has to be a constant "
"pattern."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1705
msgid ""
"The size of the dictionary is tested first, it has to be the same size as "
"the pattern, otherwise the pattern doesn't match."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1707
msgid ""
"**Open-ended dictionary**: A dictionary can be bigger than the pattern by "
"making the last subpattern ``..``."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1709
msgid "Every subpattern has to be comma separated."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1711
msgid ""
"If you don't specify a value, then only the existence of the key is checked."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1713
msgid "A value pattern is separated from the key pattern with a ``:``."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1738
msgid "Multiple patterns"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1730
msgid ""
"You can also specify multiple patterns separated by a comma. These patterns "
"aren't allowed to have any bindings in them."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1741
msgid "Pattern guards"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1743
msgid ""
"Only one branch can be executed per ``match``. Once a branch is chosen, the "
"rest are not checked. If you want to use the same pattern for multiple "
"branches or to prevent choosing a branch with too general pattern, you can "
"specify a guard expression after the list of patterns with the ``when`` "
"keyword::"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1761
msgid ""
"If there is no matching pattern for the current branch, the guard expression "
"is **not** evaluated and the patterns of the next branch are checked."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1763
msgid "If a matching pattern is found, the guard expression is evaluated."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1765
msgid ""
"If it's true, then the body of the branch is executed and ``match`` ends."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1766
msgid "If it's false, then the patterns of the next branch are checked."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1769
msgid "Classes"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1771
msgid ""
"By default, all script files are unnamed classes. In this case, you can only "
"reference them using the file's path, using either a relative or an absolute "
"path. For example, if you name a script file ``character.gd``::"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1787
msgid "Registering named classes"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1789
msgid ""
"You can give your class a name to register it as a new type in Godot's "
"editor. For that, you use the ``class_name`` keyword. You can optionally use "
"the ``@icon`` annotation with a path to an image, to use it as an icon. Your "
"class will then appear with its new icon in the editor::"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1810
msgid "Here's a class file example:"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1831
msgid ""
"If you want to use ``extends`` too, you can keep both on the same line::"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1837
msgid ""
"Godot initializes non-static variables every time you create an instance, "
"and this includes arrays and dictionaries. This is in the spirit of thread "
"safety, since scripts can be initialized in separate threads without the "
"user knowing."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1842
#: ../../docs/tutorials/scripting/how_to_read_the_godot_api.rst:13
#: ../../docs/tutorials/scripting/cross_language_scripting.rst:190
msgid "Inheritance"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1844
msgid "A class (stored as a file) can inherit from:"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1846
msgid "A global class."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1847
msgid "Another class file."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1848
msgid "An inner class inside another class file."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1850
msgid "Multiple inheritance is not allowed."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1852
msgid "Inheritance uses the ``extends`` keyword::"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1865
msgid ""
"If inheritance is not explicitly defined, the class will default to "
"inheriting :ref:`class_RefCounted`."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1868
msgid ""
"To check if a given instance inherits from a given class, the ``is`` keyword "
"can be used::"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1880
msgid ""
"To call a function in a *super class* (i.e. one ``extend``-ed in your "
"current class), use the ``super`` keyword::"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1885
msgid ""
"This is especially useful because functions in extending classes replace "
"functions with the same name in their super classes. If you still want to "
"call them, you can use ``super``::"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1892
msgid ""
"If you need to call a different function from the super class, you can "
"specify the function name with the attribute operator::"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1903
msgid ""
"One of the common misconceptions is trying to override *non-virtual* engine "
"methods such as ``get_class()``, ``queue_free()``, etc. This is not "
"supported for technical reasons."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1906
msgid ""
"In Godot 3, you can *shadow* engine methods in GDScript, and it will work if "
"you call this method in GDScript. However, the engine will **not** execute "
"your code if the method is called inside the engine on some event."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1909
msgid ""
"In Godot 4, even shadowing may not always work, as GDScript optimizes native "
"method calls. Therefore, we added the ``NATIVE_METHOD_OVERRIDE`` warning, "
"which is treated as an error by default. We strongly advise against "
"disabling or ignoring the warning."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1913
msgid ""
"Note that this does not apply to virtual methods such as ``_ready()``, "
"``_process()`` and others (marked with the ``virtual`` qualifier in the "
"documentation and the names start with an underscore). These methods are "
"specifically for customizing engine behavior and can be overridden in "
"GDScript. Signals and notifications can also be useful for these purposes."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1919
msgid "Class constructor"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1921
msgid ""
"The class constructor, called on class instantiation, is named ``_init``. If "
"you want to call the base class constructor, you can also use the ``super`` "
"syntax. Note that every class has an implicit constructor that it's always "
"called (defining the default values of class variables). ``super`` is used "
"to call the explicit constructor::"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1930
msgid "This is better explained through examples. Consider this scenario::"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1954
#, fuzzy
msgid "There are a few things to keep in mind here:"
msgstr "Ne postoje ograničenja prilikom korištenja Godot-a"

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1956
msgid ""
"If the inherited class (``state.gd``) defines a ``_init`` constructor that "
"takes arguments (``e`` in this case), then the inheriting class (``idle."
"gd``) *must* define ``_init`` as well and pass appropriate parameters to "
"``_init`` from ``state.gd``."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1959
msgid ""
"``idle.gd`` can have a different number of arguments than the base class "
"``state.gd``."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1960
msgid ""
"In the example above, ``e`` passed to the ``state.gd`` constructor is the "
"same ``e`` passed in to ``idle.gd``."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1962
msgid ""
"If ``idle.gd``'s ``_init`` constructor takes 0 arguments, it still needs to "
"pass some value to the ``state.gd`` base class, even if it does nothing. "
"This brings us to the fact that you can pass expressions to the base "
"constructor as well, not just variables, e.g.::"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1972
msgid "Static constructor"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1974
msgid ""
"A static constructor is a static function ``_static_init`` that is called "
"automatically when the class is loaded, after the static variables have been "
"initialized::"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1982
msgid ""
"A static constructor cannot take arguments and must not return any value."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1987
msgid "Inner classes"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:1989
msgid ""
"A class file can contain inner classes. Inner classes are defined using the "
"``class`` keyword. They are instanced using the ``ClassName.new()`` function."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:2014
msgid "Classes as resources"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:2016
msgid ""
"Classes stored as files are treated as :ref:`resources <class_GDScript>`. "
"They must be loaded from disk to access them in other classes. This is done "
"using either the ``load`` or ``preload`` functions (see below). Instancing "
"of a loaded class resource is done by calling the ``new`` function on the "
"class object::"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:2033
msgid "Exports"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:2037
msgid ""
"Documentation about exports has been moved to :ref:`doc_gdscript_exports`."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:2043
msgid "Properties (setters and getters)"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:2045
msgid ""
"Sometimes, you want a class' member variable to do more than just hold data "
"and actually perform some validation or computation whenever its value "
"changes. It may also be desired to encapsulate its access in some way."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:2049
msgid ""
"For this, GDScript provides a special syntax to define properties using the "
"``set`` and ``get`` keywords after a variable declaration. Then you can "
"define a code block that will be executed when the variable is accessed or "
"assigned."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:2053
#: ../../docs/tutorials/scripting/gdscript/static_typing.rst:175
msgid "Example::"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:2064
msgid ""
"Unlike ``setget`` in previous Godot versions, the properties setter and "
"getter are **always** called (except as noted below), even when accessed "
"inside the same class (with or without prefixing with ``self.``). This makes "
"the behavior consistent. If you need direct access to the value, use another "
"variable for direct access and make the property code use that name."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:2070
msgid "Alternative syntax"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:2072
msgid ""
"Also there is another notation to use existing class functions if you want "
"to split the code from the variable declaration or you need to reuse the "
"code across multiple properties (but you can't distinguish which property "
"the setter/getter is being called for)::"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:2078
#, fuzzy
msgid "This can also be done in the same line::"
msgstr "Glavna dokumentacija za sajt je podeljena na sledeća poglavlja:"

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:2082
msgid ""
"The setter and getter must use the same notation, mixing styles for the same "
"variable is not allowed."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:2086
msgid ""
"You cannot specify type hints for *inline* setters and getters. This is done "
"on purpose to reduce the boilerplate. If the variable is typed, then the "
"setter's argument is automatically of the same type, and the getter's return "
"value must match it. Separated setter/getter functions can have type hints, "
"and the type must match the variable's type or be a wider type."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:2091
msgid "When setter/getter is not called"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:2093
msgid ""
"When a variable is initialized, the value of the initializer will be written "
"directly to the variable. Including if the ``@onready`` annotation is "
"applied to the variable."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:2096
msgid ""
"Using the variable's name to set it inside its own setter or to get it "
"inside its own getter will directly access the underlying member, so it "
"won't generate infinite recursion and saves you from explicitly declaring "
"another variable::"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:2107
msgid "This also applies to the alternative syntax::"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:2116
msgid ""
"The exception does **not** propagate to other functions called in the setter/"
"getter. For example, the following code **will** cause an infinite "
"recursion::"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:2129
msgid "Tool mode"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:2131
msgid ""
"By default, scripts don't run inside the editor and only the exported "
"properties can be changed. In some cases, it is desired that they do run "
"inside the editor (as long as they don't execute game code or manually avoid "
"doing so). For this, the ``@tool`` annotation exists and must be placed at "
"the top of the file::"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:2144
msgid "See :ref:`doc_running_code_in_the_editor` for more information."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:2146
msgid ""
"Be cautious when freeing nodes with ``queue_free()`` or ``free()`` in a tool "
"script (especially the script's owner itself). As tool scripts run their "
"code in the editor, misusing them may lead to crashing the editor."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:2154
msgid "Memory management"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:2156
msgid ""
"Godot implements reference counting to free certain instances that are no "
"longer used, instead of a garbage collector, or requiring purely manual "
"management. Any instance of the :ref:`class_RefCounted` class (or any class "
"that inherits it, such as :ref:`class_Resource`) will be freed automatically "
"when no longer in use. For an instance of any class that is not a :ref:"
"`class_RefCounted` (such as :ref:`class_Node` or the base :ref:"
"`class_Object` type), it will remain in memory until it is deleted with "
"``free()`` (or ``queue_free()`` for Nodes)."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:2167
msgid ""
"If a :ref:`class_Node` is deleted via ``free()`` or ``queue_free()``, all of "
"its children will also recursively be deleted."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:2170
msgid ""
"To avoid reference cycles that can't be freed, a :ref:`class_WeakRef` "
"function is provided for creating weak references, which allow access to the "
"object without preventing a :ref:`class_RefCounted` from freeing. Here is an "
"example:"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:2195
msgid ""
"Alternatively, when not using references, the "
"``is_instance_valid(instance)`` can be used to check if an object has been "
"freed."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:2204
msgid ""
"Signals are a tool to emit messages from an object that other objects can "
"react to. To create custom signals for a class, use the ``signal`` keyword."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:2217
msgid ""
"Signals are a `Callback <https://en.wikipedia.org/wiki/"
"Callback_(computer_programming)>`_ mechanism. They also fill the role of "
"Observers, a common programming pattern. For more information, read the "
"`Observer tutorial <https://gameprogrammingpatterns.com/observer.html>`_ in "
"the Game Programming Patterns ebook."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:2224
msgid ""
"You can connect these signals to methods the same way you connect built-in "
"signals of nodes like :ref:`class_Button` or :ref:`class_RigidBody3D`."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:2227
msgid ""
"In the example below, we connect the ``health_depleted`` signal from a "
"``Character`` node to a ``Game`` node. When the ``Character`` node emits the "
"signal, the game node's ``_on_character_health_depleted`` is called::"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:2241
msgid "You can emit as many arguments as you want along with a signal."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:2243
msgid ""
"Here is an example where this is useful. Let's say we want a life bar on "
"screen to react to health changes with an animation, but we want to keep the "
"user interface separate from the player in our scene tree."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:2247
msgid ""
"In our ``character.gd`` script, we define a ``health_changed`` signal and "
"emit it with :ref:`Signal.emit() <class_Signal_method_emit>`, and from a "
"``Game`` node higher up our scene tree, we connect it to the ``Lifebar`` "
"using the :ref:`Signal.connect() <class_Signal_method_connect>` method::"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:2286
msgid ""
"In the ``Game`` node, we get both the ``Character`` and ``Lifebar`` nodes, "
"then connect the character, that emits the signal, to the receiver, the "
"``Lifebar`` node in this case."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:2300
msgid ""
"This allows the ``Lifebar`` to react to health changes without coupling it "
"to the ``Character`` node."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:2303
msgid ""
"You can write optional argument names in parentheses after the signal's "
"definition::"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:2309
msgid ""
"These arguments show up in the editor's node dock, and Godot can use them to "
"generate callback functions for you. However, you can still emit any number "
"of arguments when you emit signals; it's up to you to emit the correct "
"values."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:2315
msgid ""
"GDScript can bind an array of values to connections between a signal and a "
"method. When the signal is emitted, the callback method receives the bound "
"values. These bound arguments are unique to each connection, and the values "
"will stay the same."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:2320
msgid ""
"You can use this array of values to add extra constant information to the "
"connection if the emitted signal itself doesn't give you access to all the "
"data that you need."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:2324
msgid ""
"Building on the example above, let's say we want to display a log of the "
"damage taken by each character on the screen, like ``Player1 took 22 damage."
"``. The ``health_changed`` signal doesn't give us the name of the character "
"that took damage. So when we connect the signal to the in-game console, we "
"can add the character's name in the binds array argument::"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:2338
msgid ""
"Our ``BattleLog`` node receives each element in the binds array as an extra "
"argument::"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:2351
#, fuzzy
msgid "Awaiting for signals or coroutines"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:2353
msgid ""
"The ``await`` keyword can be used to create `coroutines <https://en."
"wikipedia.org/wiki/Coroutine>`_ which wait until a signal is emitted before "
"continuing execution. Using the ``await`` keyword with a signal or a call to "
"a function that is also a coroutine will immediately return the control to "
"the caller. When the signal is emitted (or the called coroutine finishes), "
"it will resume execution from the point on where it stopped."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:2358
msgid ""
"For example, to stop execution until the user presses a button, you can do "
"something like this::"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:2366
msgid ""
"In this case, the ``wait_confirmation`` becomes a coroutine, which means "
"that the caller also needs to await for it::"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:2376
msgid ""
"Note that requesting a coroutine's return value without ``await`` will "
"trigger an error::"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:2381
msgid ""
"However, if you don't depend on the result, you can just call it "
"asynchronously, which won't stop execution and won't make the current "
"function a coroutine::"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:2388
msgid ""
"If you use await with an expression that isn't a signal nor a coroutine, the "
"value will be returned immediately and the function won't give the control "
"back to the caller::"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:2398
msgid ""
"This also means that returning a signal from a function that isn't a "
"coroutine will make the caller await on that signal::"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:2407
msgid ""
"Unlike ``yield`` in previous Godot versions, you cannot obtain the function "
"state object. This is done to ensure type safety. With this type safety in "
"place, a function cannot say that it returns an ``int`` while it actually "
"returns a function state object during runtime."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:2413
msgid "Assert keyword"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:2415
msgid ""
"The ``assert`` keyword can be used to check conditions in debug builds. "
"These assertions are ignored in non-debug builds. This means that the "
"expression passed as argument won't be evaluated in a project exported in "
"release mode. Due to this, assertions must **not** contain expressions that "
"have side effects. Otherwise, the behavior of the script would vary "
"depending on whether the project is run in a debug build."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:2427
msgid ""
"When running a project from the editor, the project will be paused if an "
"assertion error occurs."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_basics.rst:2430
msgid ""
"You can optionally pass a custom error message to be shown if the assertion "
"fails::"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_advanced.rst:4
msgid "GDScript: An introduction to dynamic languages"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_advanced.rst:9
msgid ""
"This tutorial aims to be a quick reference for how to use GDScript more "
"efficiently. It focuses on common cases specific to the language, but also "
"covers a lot of information on dynamically typed languages."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_advanced.rst:13
msgid ""
"It's meant to be especially useful for programmers with little or no "
"previous experience with dynamically typed languages."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_advanced.rst:17
msgid "Dynamic nature"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_advanced.rst:20
msgid "Pros & cons of dynamic typing"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_advanced.rst:22
msgid ""
"GDScript is a Dynamically Typed language. As such, its main advantages are "
"that:"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_advanced.rst:25
msgid "The language is easy to get started with."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_advanced.rst:26
msgid "Most code can be written and changed quickly and without hassle."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_advanced.rst:27
msgid "Less code written means less errors & mistakes to fix."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_advanced.rst:28
msgid "The code is easy to read (little clutter)."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_advanced.rst:29
msgid "No compilation is required to test."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_advanced.rst:30
msgid "Runtime is tiny."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_advanced.rst:31
msgid "It has duck-typing and polymorphism by nature."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_advanced.rst:33
msgid "While the main disadvantages are:"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_advanced.rst:35
msgid "Less performance than statically typed languages."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_advanced.rst:36
msgid "More difficult to refactor (symbols can't be traced)."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_advanced.rst:37
msgid ""
"Some errors that would typically be detected at compile time in statically "
"typed languages only appear while running the code (because expression "
"parsing is more strict)."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_advanced.rst:40
msgid ""
"Less flexibility for code-completion (some variable types are only known at "
"run-time)."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_advanced.rst:43
msgid ""
"This, translated to reality, means that Godot used with GDScript is a "
"combination designed to create games quickly and efficiently. For games that "
"are very computationally intensive and can't benefit from the engine built-"
"in tools (such as the Vector types, Physics Engine, Math library, etc), the "
"possibility of using C++ is present too. This allows you to still create "
"most of the game in GDScript and add small bits of C++ in the areas that "
"need a performance boost."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_advanced.rst:52
msgid "Variables & assignment"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_advanced.rst:54
msgid ""
"All variables in a dynamically typed language are \"variant\"-like. This "
"means that their type is not fixed, and is only modified through assignment. "
"Example:"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_advanced.rst:58
#: ../../docs/tutorials/scripting/gdscript/gdscript_advanced.rst:80
msgid "Static:"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_advanced.rst:66
#: ../../docs/tutorials/scripting/gdscript/gdscript_advanced.rst:94
msgid "Dynamic:"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_advanced.rst:75
msgid "As function arguments:"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_advanced.rst:77
msgid ""
"Functions are of dynamic nature too, which means they can be called with "
"different arguments, for example:"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_advanced.rst:107
msgid "Pointers & referencing:"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_advanced.rst:109
msgid ""
"In static languages, such as C or C++ (and to some extent Java and C#), "
"there is a distinction between a variable and a pointer/reference to a "
"variable. The latter allows the object to be modified by other functions by "
"passing a reference to the original one."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_advanced.rst:114
msgid ""
"In C# or Java, everything not a built-in type (int, float, sometimes String) "
"is always a pointer or a reference. References are also garbage-collected "
"automatically, which means they are erased when no longer used. Dynamically "
"typed languages tend to use this memory model, too. Some Examples:"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_advanced.rst:120
msgid "C++:"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_advanced.rst:136
msgid "Java:"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_advanced.rst:154
msgid "GDScript:"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_advanced.rst:166
msgid ""
"In GDScript, only base types (int, float, string and the vector types) are "
"passed by value to functions (value is copied). Everything else (instances, "
"arrays, dictionaries, etc) is passed as reference. Classes that inherit :ref:"
"`class_RefCounted` (the default if nothing is specified) will be freed when "
"not used, but manual memory management is allowed too if inheriting manually "
"from :ref:`class_Object`."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_advanced.rst:174
#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:207
msgid "Arrays"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_advanced.rst:176
msgid ""
"Arrays in dynamically typed languages can contain many different mixed "
"datatypes inside and are always dynamic (can be resized at any time). "
"Compare for example arrays in statically typed languages:"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_advanced.rst:203
msgid "And in GDScript:"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_advanced.rst:212
msgid ""
"In dynamically typed languages, arrays can also double as other datatypes, "
"such as lists:"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_advanced.rst:222
msgid "Or unordered sets:"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_advanced.rst:231
msgid "Dictionaries"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_advanced.rst:233
msgid ""
"Dictionaries are a powerful tool in dynamically typed languages. Most "
"programmers that come from statically typed languages (such as C++ or C#) "
"ignore their existence and make their life unnecessarily more difficult. "
"This datatype is generally not present in such languages (or only in limited "
"form)."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_advanced.rst:239
msgid ""
"Dictionaries can map any value to any other value with complete disregard "
"for the datatype used as either key or value. Contrary to popular belief, "
"they are efficient because they can be implemented with hash tables. They "
"are, in fact, so efficient that some languages will go as far as "
"implementing arrays as dictionaries."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_advanced.rst:245
msgid "Example of Dictionary:"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_advanced.rst:252
msgid ""
"Dictionaries are also dynamic, keys can be added or removed at any point at "
"little cost:"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_advanced.rst:261
msgid ""
"In most cases, two-dimensional arrays can often be implemented more easily "
"with dictionaries. Here's a battleship game example:"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_advanced.rst:294
msgid ""
"Dictionaries can also be used as data markup or quick structures. While "
"GDScript's dictionaries resemble python dictionaries, it also supports Lua "
"style syntax and indexing, which makes it useful for writing initial states "
"and quick structs:"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_advanced.rst:319
msgid "For & while"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_advanced.rst:321
msgid ""
"Iterating using the C-style for loop in C-derived languages can be quite "
"complex:"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_advanced.rst:342
msgid ""
"Because of this, GDScript makes the opinionated decision to have a for-in "
"loop over iterables instead:"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_advanced.rst:349
msgid ""
"Container datatypes (arrays and dictionaries) are iterable. Dictionaries "
"allow iterating the keys:"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_advanced.rst:357
msgid "Iterating with indices is also possible:"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_advanced.rst:364
msgid "The range() function can take 3 arguments:"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_advanced.rst:372
msgid "Some examples involving C-style for loops:"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_advanced.rst:382
msgid "Translate to:"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_advanced.rst:395
msgid "And backwards looping done through a negative counter:"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_advanced.rst:401
msgid "Becomes:"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_advanced.rst:409
msgid "While"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_advanced.rst:411
msgid "while() loops are the same everywhere:"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_advanced.rst:422
msgid "Custom iterators"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_advanced.rst:423
msgid ""
"You can create custom iterators in case the default ones don't quite meet "
"your needs by overriding the Variant class's ``_iter_init``, ``_iter_next``, "
"and ``_iter_get`` functions in your script. An example implementation of a "
"forward iterator follows:"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_advanced.rst:455
msgid "And it can be used like any other iterator:"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_advanced.rst:463
msgid ""
"Make sure to reset the state of the iterator in ``_iter_init``, otherwise "
"nested for-loops that use custom iterators will not work as expected."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_advanced.rst:467
msgid "Duck typing"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_advanced.rst:469
msgid ""
"One of the most difficult concepts to grasp when moving from a statically "
"typed language to a dynamic one is duck typing. Duck typing makes overall "
"code design much simpler and straightforward to write, but it's not obvious "
"how it works."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_advanced.rst:474
msgid ""
"As an example, imagine a situation where a big rock is falling down a "
"tunnel, smashing everything on its way. The code for the rock, in a "
"statically typed language would be something like:"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_advanced.rst:485
msgid ""
"This way, everything that can be smashed by a rock would have to inherit "
"Smashable. If a character, enemy, piece of furniture, small rock were all "
"smashable, they would need to inherit from the class Smashable, possibly "
"requiring multiple inheritance. If multiple inheritance was undesired, then "
"they would have to inherit a common class like Entity. Yet, it would not be "
"very elegant to add a virtual method ``smash()`` to Entity only if a few of "
"them can be smashed."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_advanced.rst:493
msgid ""
"With dynamically typed languages, this is not a problem. Duck typing makes "
"sure you only have to define a ``smash()`` function where required and "
"that's it. No need to consider inheritance, base classes, etc."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_advanced.rst:502
msgid ""
"And that's it. If the object that hit the big rock has a smash() method, it "
"will be called. No need for inheritance or polymorphism. Dynamically typed "
"languages only care about the instance having the desired method or member, "
"not what it inherits or the class type. The definition of Duck Typing should "
"make this clearer:"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_advanced.rst:508
msgid ""
"*\"When I see a bird that walks like a duck and swims like a duck and quacks "
"like a duck, I call that bird a duck\"*"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_advanced.rst:511
msgid "In this case, it translates to:"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_advanced.rst:513
msgid ""
"*\"If the object can be smashed, don't care what it is, just smash it.\"*"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_advanced.rst:515
msgid "Yes, we should call it Hulk typing instead."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_advanced.rst:517
msgid ""
"It's possible that the object being hit doesn't have a smash() function. "
"Some dynamically typed languages simply ignore a method call when it doesn't "
"exist, but GDScript is stricter, so checking if the function exists is "
"desirable:"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_advanced.rst:528
msgid ""
"Then, simply define that method and anything the rock touches can be smashed."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_exports.rst:4
#, fuzzy
msgid "GDScript exported properties"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/scripting/gdscript/gdscript_exports.rst:6
msgid ""
"In Godot, class members can be exported. This means their value gets saved "
"along with the resource (such as the :ref:`scene <class_PackedScene>`) "
"they're attached to. They will also be available for editing in the property "
"editor. Exporting is done by using the ``@export`` annotation."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_exports.rst:15
msgid ""
"In that example the value ``5`` will be saved and visible in the property "
"editor."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_exports.rst:17
msgid ""
"An exported variable must be initialized to a constant expression or have a "
"type specifier in the variable. Some of the export annotations have a "
"specific type and don't need the variable to be typed (see the *Examples* "
"section below)."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_exports.rst:21
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_exports.rst:24
msgid ""
"One of the fundamental benefits of exporting member variables is to have "
"them visible and editable in the editor. This way, artists and game "
"designers can modify values that later influence how the program runs. For "
"this, a special export syntax is provided."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_exports.rst:28
msgid ""
"Exporting properties can also be done in other languages such as C#. The "
"syntax varies depending on the language. See :ref:`doc_c_sharp_exports` for "
"information on C# exports."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_exports.rst:33
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_exports.rst:37
msgid "Basic use"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_exports.rst:35
msgid ""
"If the exported value assigns a constant or constant expression, the type "
"will be inferred and used in the editor."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_exports.rst:42
msgid "If there's no default value, you can add a type to the variable."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_exports.rst:48
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_exports.rst:74
msgid "Resources and nodes can be exported."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_exports.rst:56
#, fuzzy
msgid "Grouping Exports"
msgstr "Uvod"

#: ../../docs/tutorials/scripting/gdscript/gdscript_exports.rst:58
msgid ""
"It is possible to group your exported properties inside the Inspector with "
"the :ref:`@export_group <class_@GDScript_annotation_@export_group>` "
"annotation. Every exported property after this annotation will be added to "
"the group. Start a new group or use ``@export_group(\"\")`` to break out."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_exports.rst:68
msgid ""
"The second argument of the annotation can be used to only group properties "
"with the specified prefix."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_exports.rst:71
msgid ""
"Groups cannot be nested, use :ref:`@export_subgroup "
"<class_@GDScript_annotation_@export_subgroup>` to create subgroups within a "
"group."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_exports.rst:80
msgid ""
"You can also change the name of your main category, or create additional "
"categories in the property list with the :ref:`@export_category "
"<class_@GDScript_annotation_@export_category>` annotation."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_exports.rst:95
msgid ""
"The list of properties is organized based on the class inheritance and new "
"categories break that expectation. Use them carefully, especially when "
"creating projects for public use."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_exports.rst:100
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_exports.rst:130
msgid "Strings as paths"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_exports.rst:102
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_exports.rst:134
#, fuzzy
msgid "String as a path to a file."
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/scripting/gdscript/gdscript_exports.rst:108
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_exports.rst:141
msgid "String as a path to a directory."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_exports.rst:114
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_exports.rst:148
msgid "String as a path to a file, custom filter provided as hint."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_exports.rst:120
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_exports.rst:155
msgid ""
"Using paths in the global filesystem is also possible, but only in scripts "
"in tool mode."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_exports.rst:123
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_exports.rst:158
msgid "String as a path to a PNG file in the global filesystem."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_exports.rst:129
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_exports.rst:165
msgid "String as a path to a directory in the global filesystem."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_exports.rst:135
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_exports.rst:172
msgid ""
"The multiline annotation tells the editor to show a large input field for "
"editing over multiple lines."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_exports.rst:143
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_exports.rst:181
msgid "Limiting editor input ranges"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_exports.rst:145
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_exports.rst:186
msgid "Allow integer values from 0 to 20."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_exports.rst:151
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_exports.rst:193
msgid "Allow integer values from -10 to 20."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_exports.rst:157
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_exports.rst:200
msgid "Allow floats from -10 to 20 and snap the value to multiples of 0.2."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_exports.rst:163
msgid ""
"The limits can be only for the slider if you add the hints \"or_greater\" "
"and/or \"or_less\"."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_exports.rst:172
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_exports.rst:217
msgid "Floats with easing hint"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_exports.rst:174
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_exports.rst:219
msgid "Display a visual representation of the 'ease()' function when editing."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_exports.rst:182
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_exports.rst:228
#, fuzzy
msgid "Colors"
msgstr "**Za uređivač:**"

#: ../../docs/tutorials/scripting/gdscript/gdscript_exports.rst:184
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_exports.rst:230
msgid "Regular color given as red-green-blue-alpha value."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_exports.rst:190
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_exports.rst:237
msgid "Color given as red-green-blue value (alpha will always be 1)."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_exports.rst:199
msgid ""
"Since Godot 4.0, nodes can be directly exported as properties in a script "
"without having to use NodePaths:"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_exports.rst:211
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_exports.rst:256
msgid ""
"Exporting NodePaths like in Godot 3.x is still possible, in case you need it:"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_exports.rst:218
msgid ""
"If you want to limit the types of nodes for NodePaths, you can use the :ref:"
"`@export_node_path<class_@GDScript_annotation_@export_node_path>` annotation:"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_exports.rst:233
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_exports.rst:276
msgid ""
"In the Inspector, you can then drag and drop a resource file from the "
"FileSystem dock into the variable slot."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_exports.rst:236
msgid ""
"Opening the inspector dropdown may result in an extremely long list of "
"possible classes to create, however. Therefore, if you specify an extension "
"of Resource such as:"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_exports.rst:244
msgid ""
"The drop-down menu will be limited to AnimationNode and all its inherited "
"classes."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_exports.rst:247
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_exports.rst:292
msgid ""
"It must be noted that even if the script is not being run while in the "
"editor, the exported properties are still editable. This can be used in "
"conjunction with a :ref:`script in \"tool\" mode <doc_gdscript_tool_mode>`."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_exports.rst:252
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_exports.rst:297
msgid "Exporting bit flags"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_exports.rst:254
msgid ""
"Integers used as bit flags can store multiple ``true``/``false`` (boolean) "
"values in one property. By using the ``@export_flags`` annotation, they can "
"be set from the editor::"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_exports.rst:261
msgid ""
"You must provide a string description for each flag. In this example, "
"``Fire`` has value 1, ``Water`` has value 2, ``Earth`` has value 4 and "
"``Wind`` corresponds to value 8. Usually, constants should be defined "
"accordingly (e.g. ``const ELEMENT_WIND = 8`` and so on)."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_exports.rst:266
#: ../../docs/tutorials/scripting/gdscript/gdscript_exports.rst:311
msgid "You can add explicit values using a colon::"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_exports.rst:270
msgid ""
"Only power of 2 values are valid as bit flags options. The lowest allowed "
"value is 1, as 0 means that nothing is selected. You can also add options "
"that are a combination of other flags::"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_exports.rst:277
msgid ""
"Export annotations are also provided for the physics, render, and navigation "
"layers defined in the project settings::"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_exports.rst:286
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_exports.rst:366
msgid ""
"Using bit flags requires some understanding of bitwise operations. If in "
"doubt, use boolean variables instead."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_exports.rst:290
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_exports.rst:370
#, fuzzy
msgid "Exporting enums"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/scripting/gdscript/gdscript_exports.rst:292
msgid ""
"Properties can be exported with a type hint referencing an enum to limit "
"their values to the values of the enumeration. The editor will create a "
"widget in the Inspector, enumerating the following as \"Thing 1\", \"Thing "
"2\", \"Another Thing\". The value will be stored as an integer."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_exports.rst:301
msgid ""
"Integer and string properties can also be limited to a specific list of "
"values using the :ref:`@export_enum "
"<class_@GDScript_annotation_@export_enum>` annotation. The editor will "
"create a widget in the Inspector, enumerating the following as Warrior, "
"Magician, Thief. The value will be stored as an integer, corresponding to "
"the index of the selected option (i.e. ``0``, ``1``,  or ``2``)."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_exports.rst:315
msgid "If the type is String, the value will be stored as a string."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_exports.rst:321
msgid "If you want to set an initial value, you must specify it explicitly::"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_exports.rst:326
msgid "Exporting arrays"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_exports.rst:328
msgid ""
"Exported arrays can have initializers, but they must be constant expressions."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_exports.rst:330
msgid ""
"If the exported array specifies a type which inherits from Resource, the "
"array values can be set in the inspector by dragging and dropping multiple "
"files from the FileSystem dock at once."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_exports.rst:334
msgid "The default value **must** be a constant expression."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_exports.rst:340
msgid "Exported arrays can specify type (using the same hints as before)."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_exports.rst:349
msgid ""
"You can omit the default value, but it would then be ``null`` if not "
"assigned."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_exports.rst:356
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_exports.rst:456
msgid ""
"Arrays with specified types which inherit from resource can be set by drag-"
"and-dropping multiple files from the FileSystem dock."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_exports.rst:364
msgid "Packed type arrays also work, but only initialized empty:"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_exports.rst:372
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_exports.rst:526
msgid "Setting exported variables from a tool script"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_exports.rst:374
msgid ""
"When changing an exported variable's value from a script in :ref:"
"`doc_gdscript_tool_mode`, the value in the inspector won't be updated "
"automatically. To update it, call :ref:`notify_property_list_changed() "
"<class_Object_method_notify_property_list_changed>` after setting the "
"exported variable's value."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_exports.rst:381
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_exports.rst:535
msgid "Advanced exports"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_exports.rst:383
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_exports.rst:537
msgid ""
"Not every type of export can be provided on the level of the language itself "
"to avoid unnecessary design complexity. The following describes some more or "
"less common exporting features which can be implemented with a low-level API."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_exports.rst:387
msgid ""
"Before reading further, you should get familiar with the way properties are "
"handled and how they can be customized with :ref:`_set() "
"<class_Object_private_method__set>`, :ref:`_get() "
"<class_Object_private_method__get>`, and :ref:`_get_property_list() "
"<class_Object_private_method__get_property_list>` methods as described in :"
"ref:`doc_accessing_data_or_logic_from_object`."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_exports.rst:394
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_exports.rst:548
msgid ""
"For binding properties using the above methods in C++, see :ref:"
"`doc_binding_properties_using_set_get_property_list`."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_exports.rst:397
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_exports.rst:551
msgid ""
"The script must operate in the ``tool`` mode so the above methods can work "
"from within the editor."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_documentation_comments.rst:4
#, fuzzy
msgid "GDScript documentation comments"
msgstr "Organizacija dokumentacije"

#: ../../docs/tutorials/scripting/gdscript/gdscript_documentation_comments.rst:6
msgid ""
"In GDScript, comments can be used to document your code and add descriptions "
"to the members of a script. There are two differences between a normal "
"comment and a documentation comment. Firstly, a documentation comment should "
"start with double hash symbols ``##``. Secondly, it must immediately precede "
"a script member, or for script descriptions, be placed at the top of the "
"script. If an exported variable is documented, its description is used as a "
"tooltip in the editor. This documentation can be generated as XML files by "
"the editor."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_documentation_comments.rst:15
#, fuzzy
msgid "Documenting a script"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/scripting/gdscript/gdscript_documentation_comments.rst:17
msgid ""
"Comments documenting a script must come before any member documentation. A "
"suggested format for script documentation can be divided into three parts."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_documentation_comments.rst:20
msgid "A brief description of the script."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_documentation_comments.rst:21
#, fuzzy
msgid "Detailed description."
msgstr "Uvod"

#: ../../docs/tutorials/scripting/gdscript/gdscript_documentation_comments.rst:22
msgid "Tutorials and deprecated/experimental marks."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_documentation_comments.rst:24
msgid ""
"To separate these from each other, the documentation comments use special "
"tags. The tag must be at the beginning of a line (ignoring preceding white "
"space) and must have the format ``@``, followed by the keyword."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_documentation_comments.rst:29
#: ../../docs/tutorials/scripting/gdscript/gdscript_documentation_comments.rst:87
msgid "Tags"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_documentation_comments.rst:32
#, fuzzy
msgid "Brief description"
msgstr "Uvod"

#: ../../docs/tutorials/scripting/gdscript/gdscript_documentation_comments.rst:32
msgid "No tag. Lives at the very beginning of the documentation section."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_documentation_comments.rst:35
msgid "No tag. Use one blank line to separate the description from the brief."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_documentation_comments.rst:38
#, fuzzy
msgid "Tutorial"
msgstr "Tutorijali"

#: ../../docs/tutorials/scripting/gdscript/gdscript_documentation_comments.rst:0
msgid "``@tutorial:``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_documentation_comments.rst:0
msgid "``@tutorial(The Title Here):``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_documentation_comments.rst:41
#: ../../docs/tutorials/scripting/gdscript/gdscript_documentation_comments.rst:92
msgid "Deprecated"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_documentation_comments.rst:41
#: ../../docs/tutorials/scripting/gdscript/gdscript_documentation_comments.rst:92
msgid "``@deprecated``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_documentation_comments.rst:43
#: ../../docs/tutorials/scripting/gdscript/gdscript_documentation_comments.rst:94
msgid "Experimental"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_documentation_comments.rst:43
#: ../../docs/tutorials/scripting/gdscript/gdscript_documentation_comments.rst:94
msgid "``@experimental``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_documentation_comments.rst:60
msgid ""
"If there is any space in between the tag name and colon, for example "
"``@tutorial  :``, it won't be treated as a valid tag and will be ignored."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_documentation_comments.rst:65
msgid ""
"When the description spans multiple lines, the preceding and trailing white "
"spaces will be stripped and joined with a single space. To preserve the line "
"break use ``[br]``. See also `BBCode and class reference`_ below."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_documentation_comments.rst:70
#, fuzzy
msgid "Documenting script members"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/scripting/gdscript/gdscript_documentation_comments.rst:72
msgid "Members that are applicable for documentation:"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_documentation_comments.rst:74
msgid "Inner class"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_documentation_comments.rst:75
msgid "Constant"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_documentation_comments.rst:76
#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1101
#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:286
#: ../../docs/tutorials/shaders/shader_reference/particle_shader.rst:78
#: ../../docs/tutorials/shaders/shader_reference/particle_shader.rst:178
msgid "Function"
msgstr "Funkcija"

#: ../../docs/tutorials/scripting/gdscript/gdscript_documentation_comments.rst:78
#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:91
#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:164
#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:229
msgid "Variable"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_documentation_comments.rst:79
msgid "Enum"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_documentation_comments.rst:82
msgid ""
"Documentation of a script member must immediately precede the member or its "
"annotations if it has any. The description can have more than one line but "
"every line must start with the double hash symbol ``##`` to be considered as "
"part of the documentation."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_documentation_comments.rst:90
msgid "No tag."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_documentation_comments.rst:103
msgid "Alternatively, you can use inline documentation comments::"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_documentation_comments.rst:122
msgid ""
"The script documentation will update in the editor help window every time "
"the script is updated. If any member variable or function name starts with "
"an underscore, it will be treated as private. It will not appear in the "
"documentation and will be ignored in the help window."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_documentation_comments.rst:127
#, fuzzy
msgid "Complete script example"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/scripting/gdscript/gdscript_documentation_comments.rst:201
msgid "``@deprecated`` and ``@experimental`` tags"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_documentation_comments.rst:203
msgid ""
"You can mark a class or any of its members as deprecated or experimental. "
"This will add the corresponding indicator in the built-in documentation "
"viewer. This can be especially useful for plugin and library creators."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_documentation_comments.rst:209
msgid ""
"**Deprecated** marks a non-recommended API that is subject to removal or "
"incompatible change in a future major release. Usually the API is kept for "
"backwards compatibility."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_documentation_comments.rst:211
msgid ""
"**Experimental** marks a new unstable API that may be changed or removed in "
"the current major branch. Using this API is not recommended in production "
"code."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_documentation_comments.rst:216
msgid ""
"While technically you can use both ``@deprecated`` and ``@experimental`` "
"tags on the same class/member, this is not recommended as it is against "
"common conventions."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_documentation_comments.rst:220
msgid "BBCode and class reference"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_documentation_comments.rst:222
msgid ""
"The editor help window which renders the documentation supports :ref:`bbcode "
"<doc_bbcode_in_richtextlabel>`. As a result it's possible to align and "
"format the documentation. Color texts, images, fonts, tables, URLs, "
"animation effects, etc. can be added with the :ref:`bbcode "
"<doc_bbcode_in_richtextlabel>`."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_documentation_comments.rst:226
msgid ""
"Godot's class reference supports BBCode-like tags. They add nice formatting "
"to the text which could also be used in the documentation. See also :ref:"
"`class reference bbcode <doc_class_reference_bbcode>`."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_documentation_comments.rst:229
#: ../../docs/contributing/documentation/class_reference_primer.rst:134
msgid ""
"Whenever you link to a member of another class, you need to specify the "
"class name. For links to the same class, the class name is optional and can "
"be omitted."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_documentation_comments.rst:232
#, fuzzy
msgid "Here's the list of available tags:"
msgstr "Ne postoje ograničenja prilikom korištenja Godot-a"

#: ../../docs/tutorials/scripting/gdscript/gdscript_documentation_comments.rst:235
#: ../../docs/contributing/documentation/class_reference_primer.rst:138
#: ../../docs/contributing/documentation/class_reference_primer.rst:173
#: ../../docs/contributing/documentation/class_reference_primer.rst:195
#, fuzzy
msgid "Tag and Description"
msgstr "Uvod"

#: ../../docs/tutorials/scripting/gdscript/gdscript_documentation_comments.rst:235
#: ../../docs/contributing/documentation/class_reference_primer.rst:138
#: ../../docs/contributing/documentation/class_reference_primer.rst:173
#: ../../docs/contributing/documentation/class_reference_primer.rst:195
msgid "Result"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_documentation_comments.rst:0
#: ../../docs/contributing/documentation/class_reference_primer.rst:0
msgid "``[Class]``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_documentation_comments.rst:0
#: ../../docs/contributing/documentation/class_reference_primer.rst:0
#, fuzzy
msgid "Link to class"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/scripting/gdscript/gdscript_documentation_comments.rst:237
#: ../../docs/contributing/documentation/class_reference_primer.rst:140
#, fuzzy
msgid "``Move the [Sprite2D].``"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/scripting/gdscript/gdscript_documentation_comments.rst:237
#: ../../docs/contributing/documentation/class_reference_primer.rst:140
#, fuzzy
msgid "Move the :ref:`class_Sprite2D`."
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/scripting/gdscript/gdscript_documentation_comments.rst:0
#: ../../docs/contributing/documentation/class_reference_primer.rst:0
msgid "``[annotation Class.name]``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_documentation_comments.rst:0
#: ../../docs/contributing/documentation/class_reference_primer.rst:0
#, fuzzy
msgid "Link to annotation"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/scripting/gdscript/gdscript_documentation_comments.rst:240
#: ../../docs/contributing/documentation/class_reference_primer.rst:143
msgid "``See [annotation @GDScript.@export].``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_documentation_comments.rst:240
#: ../../docs/contributing/documentation/class_reference_primer.rst:143
msgid "See :ref:`@GDScript.@export <class_@GDScript_annotation_@export>`."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_documentation_comments.rst:0
#: ../../docs/contributing/documentation/class_reference_primer.rst:0
msgid "``[constant Class.name]``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_documentation_comments.rst:0
#: ../../docs/contributing/documentation/class_reference_primer.rst:0
#, fuzzy
msgid "Link to constant"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/scripting/gdscript/gdscript_documentation_comments.rst:243
#: ../../docs/contributing/documentation/class_reference_primer.rst:146
msgid "``See [constant @GlobalScope.KEY_F1].``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_documentation_comments.rst:243
#: ../../docs/contributing/documentation/class_reference_primer.rst:146
msgid "See :ref:`@GlobalScope.KEY_F1 <class_@GlobalScope_constant_KEY_F1>`."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_documentation_comments.rst:0
#: ../../docs/contributing/documentation/class_reference_primer.rst:0
msgid "``[enum Class.name]``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_documentation_comments.rst:0
#: ../../docs/contributing/documentation/class_reference_primer.rst:0
#, fuzzy
msgid "Link to enum"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/scripting/gdscript/gdscript_documentation_comments.rst:246
#: ../../docs/contributing/documentation/class_reference_primer.rst:149
msgid "``See [enum Mesh.ArrayType].``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_documentation_comments.rst:246
#: ../../docs/contributing/documentation/class_reference_primer.rst:149
msgid "See :ref:`Mesh.ArrayType <enum_Mesh_ArrayType>`."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_documentation_comments.rst:0
#: ../../docs/contributing/documentation/class_reference_primer.rst:0
msgid "``[method Class.name]``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_documentation_comments.rst:0
#: ../../docs/contributing/documentation/class_reference_primer.rst:0
#, fuzzy
msgid "Link to method"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/scripting/gdscript/gdscript_documentation_comments.rst:249
#: ../../docs/contributing/documentation/class_reference_primer.rst:152
msgid "``Call [method Node3D.hide].``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_documentation_comments.rst:249
#: ../../docs/contributing/documentation/class_reference_primer.rst:152
msgid "Call :ref:`Node3D.hide() <class_Node3D_method_hide>`."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_documentation_comments.rst:0
#: ../../docs/contributing/documentation/class_reference_primer.rst:0
msgid "``[member Class.name]``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_documentation_comments.rst:0
#: ../../docs/contributing/documentation/class_reference_primer.rst:0
#, fuzzy
msgid "Link to member"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/scripting/gdscript/gdscript_documentation_comments.rst:252
#: ../../docs/contributing/documentation/class_reference_primer.rst:155
msgid "``Get [member Node2D.scale].``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_documentation_comments.rst:252
#: ../../docs/contributing/documentation/class_reference_primer.rst:155
msgid "Get :ref:`Node2D.scale <class_Node2D_property_scale>`."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_documentation_comments.rst:0
#: ../../docs/contributing/documentation/class_reference_primer.rst:0
msgid "``[signal Class.name]``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_documentation_comments.rst:0
#: ../../docs/contributing/documentation/class_reference_primer.rst:0
#, fuzzy
msgid "Link to signal"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/scripting/gdscript/gdscript_documentation_comments.rst:255
#: ../../docs/contributing/documentation/class_reference_primer.rst:158
msgid "``Emit [signal Node.renamed].``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_documentation_comments.rst:255
#: ../../docs/contributing/documentation/class_reference_primer.rst:158
msgid "Emit :ref:`Node.renamed <class_Node_signal_renamed>`."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_documentation_comments.rst:0
#: ../../docs/contributing/documentation/class_reference_primer.rst:0
msgid "``[theme_item Class.name]``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_documentation_comments.rst:0
#: ../../docs/contributing/documentation/class_reference_primer.rst:0
#, fuzzy
msgid "Link to theme item"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/scripting/gdscript/gdscript_documentation_comments.rst:258
#: ../../docs/contributing/documentation/class_reference_primer.rst:161
msgid "``See [theme_item Label.font].``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_documentation_comments.rst:258
#: ../../docs/contributing/documentation/class_reference_primer.rst:161
msgid "See :ref:`Label.font <class_Label_theme_font_font>`."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_documentation_comments.rst:0
#: ../../docs/contributing/documentation/class_reference_primer.rst:0
msgid "``[param name]``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_documentation_comments.rst:0
#: ../../docs/contributing/documentation/class_reference_primer.rst:0
msgid "Formats a parameter name (as code)"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_documentation_comments.rst:261
#: ../../docs/contributing/documentation/class_reference_primer.rst:175
msgid "``Takes [param size] for the size.``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_documentation_comments.rst:261
#: ../../docs/contributing/documentation/class_reference_primer.rst:175
msgid "Takes ``size`` for the size."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_documentation_comments.rst:0
#: ../../docs/contributing/documentation/class_reference_primer.rst:0
msgid "``[br]``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_documentation_comments.rst:0
#: ../../docs/contributing/documentation/class_reference_primer.rst:0
msgid "Line break"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_documentation_comments.rst:0
#: ../../docs/contributing/documentation/class_reference_primer.rst:0
msgid "``Line 1.[br]``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_documentation_comments.rst:0
#: ../../docs/contributing/documentation/class_reference_primer.rst:0
msgid "``Line 2.``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_documentation_comments.rst:0
#: ../../docs/contributing/documentation/class_reference_primer.rst:0
msgid "Line 1."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_documentation_comments.rst:0
#: ../../docs/contributing/documentation/class_reference_primer.rst:0
msgid "Line 2."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_documentation_comments.rst:0
#: ../../docs/contributing/documentation/class_reference_primer.rst:0
msgid "``[b]`` ``[/b]``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_documentation_comments.rst:0
#: ../../docs/contributing/documentation/class_reference_primer.rst:0
msgid "Bold"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_documentation_comments.rst:267
#: ../../docs/contributing/documentation/class_reference_primer.rst:181
msgid "``Some [b]bold[/b] text.``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_documentation_comments.rst:267
#: ../../docs/contributing/documentation/class_reference_primer.rst:181
msgid "Some **bold** text."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_documentation_comments.rst:0
#: ../../docs/contributing/documentation/class_reference_primer.rst:0
msgid "``[i]`` ``[/i]``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_documentation_comments.rst:0
#: ../../docs/contributing/documentation/class_reference_primer.rst:0
msgid "Italic"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_documentation_comments.rst:270
#: ../../docs/contributing/documentation/class_reference_primer.rst:184
msgid "``Some [i]italic[/i] text.``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_documentation_comments.rst:270
#: ../../docs/contributing/documentation/class_reference_primer.rst:184
msgid "Some *italic* text."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_documentation_comments.rst:0
#: ../../docs/contributing/documentation/class_reference_primer.rst:0
msgid "``[kbd]`` ``[/kbd]``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_documentation_comments.rst:0
#: ../../docs/contributing/documentation/class_reference_primer.rst:0
msgid "Keyboard/mouse shortcut"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_documentation_comments.rst:273
#: ../../docs/contributing/documentation/class_reference_primer.rst:187
msgid "``Some [kbd]Ctrl + C[/kbd] key.``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_documentation_comments.rst:273
#: ../../docs/contributing/documentation/class_reference_primer.rst:187
msgid "Some :kbd:`Ctrl + C` key."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_documentation_comments.rst:0
#: ../../docs/contributing/documentation/class_reference_primer.rst:0
msgid "``[code]`` ``[/code]``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_documentation_comments.rst:0
#: ../../docs/contributing/documentation/class_reference_primer.rst:0
msgid "Monospace"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_documentation_comments.rst:276
#: ../../docs/contributing/documentation/class_reference_primer.rst:197
msgid "``Some [code]monospace[/code] text.``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_documentation_comments.rst:276
#: ../../docs/contributing/documentation/class_reference_primer.rst:197
msgid "Some ``monospace`` text."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_documentation_comments.rst:0
#: ../../docs/contributing/documentation/class_reference_primer.rst:0
msgid "``[codeblock]`` ``[/codeblock]``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_documentation_comments.rst:0
#: ../../docs/contributing/documentation/class_reference_primer.rst:0
msgid "Multiline preformatted block"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_documentation_comments.rst:279
#: ../../docs/contributing/documentation/class_reference_primer.rst:200
#: ../../docs/contributing/documentation/class_reference_primer.rst:203
#: ../../docs/contributing/documentation/class_reference_primer.rst:206
#: ../../docs/contributing/documentation/class_reference_primer.rst:209
msgid "*See below.*"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_documentation_comments.rst:285
#: ../../docs/contributing/documentation/class_reference_primer.rst:167
msgid "Currently only :ref:`class_@GDScript` has annotations."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_documentation_comments.rst:286
#: ../../docs/contributing/documentation/class_reference_primer.rst:215
msgid "``[code]`` disables BBCode until the parser encounters ``[/code]``."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_documentation_comments.rst:287
#: ../../docs/contributing/documentation/class_reference_primer.rst:216
msgid ""
"``[codeblock]`` disables BBCode until the parser encounters ``[/codeblock]``."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_documentation_comments.rst:291
msgid ""
"Use ``[codeblock]`` for pre-formatted code blocks. Inside ``[codeblock]``, "
"always use **four spaces** for indentation (the parser will delete tabs)."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:4
msgid "GDScript style guide"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:6
msgid ""
"This style guide lists conventions to write elegant GDScript. The goal is to "
"encourage writing clean, readable code and promote consistency across "
"projects, discussions, and tutorials. Hopefully, this will also support the "
"development of auto-formatting tools."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:11
msgid ""
"Since GDScript is close to Python, this guide is inspired by Python's `PEP 8 "
"<https://www.python.org/dev/peps/pep-0008/>`__ programming style guide."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:15
#: ../../docs/tutorials/shaders/shaders_style_guide.rst:16
msgid ""
"Style guides aren't meant as hard rulebooks. At times, you may not be able "
"to apply some of the guidelines below. When that happens, use your best "
"judgment, and ask fellow developers for insights."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:19
#: ../../docs/tutorials/shaders/shaders_style_guide.rst:20
msgid ""
"In general, keeping your code consistent in your projects and within your "
"team is more important than following this guide to a tee."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:24
msgid ""
"Godot's built-in script editor uses a lot of these conventions by default. "
"Let it help you."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:27
msgid "Here is a complete class example based on these guidelines:"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:110
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_style_guide.rst:31
#: ../../docs/tutorials/shaders/shaders_style_guide.rst:51
msgid "Formatting"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:113
#: ../../docs/tutorials/shaders/shaders_style_guide.rst:54
msgid "Encoding and special characters"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:115
#: ../../docs/tutorials/shaders/shaders_style_guide.rst:56
msgid ""
"Use line feed (**LF**) characters to break lines, not CRLF or CR. *(editor "
"default)*"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:116
#: ../../docs/tutorials/shaders/shaders_style_guide.rst:57
msgid "Use one line feed character at the end of each file. *(editor default)*"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:117
#: ../../docs/tutorials/shaders/shaders_style_guide.rst:58
msgid ""
"Use **UTF-8** encoding without a `byte order mark <https://en.wikipedia.org/"
"wiki/Byte_order_mark>`_. *(editor default)*"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:118
#: ../../docs/tutorials/shaders/shaders_style_guide.rst:59
msgid "Use **Tabs** instead of spaces for indentation. *(editor default)*"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:121
#: ../../docs/tutorials/shaders/shaders_style_guide.rst:62
msgid "Indentation"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:123
msgid "Each indent level should be one greater than the block containing it."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:125
#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:149
#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:172
#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:229
#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:257
#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:313
#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:358
#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:399
#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:431
#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:460
#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:490
#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:549
#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:570
#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:589
#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:912
#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:942
#: ../../docs/tutorials/shaders/shaders_style_guide.rst:66
#: ../../docs/tutorials/shaders/shaders_style_guide.rst:85
#: ../../docs/tutorials/shaders/shaders_style_guide.rst:112
#: ../../docs/tutorials/shaders/shaders_style_guide.rst:163
#: ../../docs/tutorials/shaders/shaders_style_guide.rst:195
#: ../../docs/tutorials/shaders/shaders_style_guide.rst:227
#: ../../docs/tutorials/shaders/shaders_style_guide.rst:257
#: ../../docs/tutorials/shaders/shaders_style_guide.rst:281
#: ../../docs/tutorials/shaders/shaders_style_guide.rst:332
msgid "**Good**:"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:134
#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:159
#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:197
#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:242
#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:265
#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:325
#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:379
#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:408
#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:440
#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:469
#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:502
#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:558
#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:578
#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:601
#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:924
#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:962
#: ../../docs/tutorials/shaders/shaders_style_guide.rst:74
#: ../../docs/tutorials/shaders/shaders_style_guide.rst:93
#: ../../docs/tutorials/shaders/shaders_style_guide.rst:122
#: ../../docs/tutorials/shaders/shaders_style_guide.rst:172
#: ../../docs/tutorials/shaders/shaders_style_guide.rst:202
#: ../../docs/tutorials/shaders/shaders_style_guide.rst:235
#: ../../docs/tutorials/shaders/shaders_style_guide.rst:265
#: ../../docs/tutorials/shaders/shaders_style_guide.rst:287
#: ../../docs/tutorials/shaders/shaders_style_guide.rst:346
msgid "**Bad**:"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:146
#: ../../docs/tutorials/shaders/shaders_style_guide.rst:82
msgid ""
"Use 2 indent levels to distinguish continuation lines from regular code "
"blocks."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:169
msgid ""
"Exceptions to this rule are arrays, dictionaries, and enums. Use a single "
"indentation level to distinguish continuation lines:"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:223
msgid "Trailing comma"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:225
msgid ""
"Use a trailing comma on the last line in arrays, dictionaries, and enums. "
"This results in easier refactoring and better diffs in version control as "
"the last line doesn't need to be modified when adding new elements."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:255
msgid ""
"Trailing commas are unnecessary in single-line lists, so don't add them in "
"this case."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:274
#: ../../docs/tutorials/shaders/shaders_style_guide.rst:133
msgid "Blank lines"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:276
msgid "Surround functions and class definitions with two blank lines:"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:291
msgid "Use one blank line inside functions to separate logical sections."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:295
msgid ""
"We use a single line between classes and function definitions in the class "
"reference and in short code snippets in this documentation."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:299
#: ../../docs/tutorials/shaders/shaders_style_guide.rst:150
msgid "Line length"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:301
#: ../../docs/tutorials/shaders/shaders_style_guide.rst:152
msgid "Keep individual lines of code under 100 characters."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:303
msgid ""
"If you can, try to keep lines under 80 characters. This helps to read the "
"code on small displays and with two scripts opened side-by-side in an "
"external text editor. For example, when looking at a differential revision."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:308
#: ../../docs/tutorials/shaders/shaders_style_guide.rst:159
msgid "One statement per line"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:310
msgid ""
"Never combine multiple statements on a single line. No, C programmers, not "
"even with a single line conditional statement."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:335
#: ../../docs/tutorials/shaders/shaders_style_guide.rst:180
msgid "The only exception to that rule is the ternary operator:"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:342
msgid "Format multiline statements for readability"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:344
msgid ""
"When you have particularly long ``if`` statements or nested ternary "
"expressions, wrapping them over multiple lines improves readability. Since "
"continuation lines are still part of the same expression, 2 indent levels "
"should be used instead of one."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:348
msgid ""
"GDScript allows wrapping statements using multiple lines using parentheses "
"or backslashes. Parentheses are favored in this style guide since they make "
"for easier refactoring. With backslashes, you have to ensure that the last "
"line never contains a backslash at the end. With parentheses, you don't have "
"to worry about the last line having a backslash at the end."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:354
msgid ""
"When wrapping a conditional expression over multiple lines, the ``and``/"
"``or`` keywords should be placed at the beginning of the line continuation, "
"not at the end of the previous line."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:393
msgid "Avoid unnecessary parentheses"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:395
msgid ""
"Avoid parentheses in expressions and conditional statements. Unless "
"necessary for order of operations or wrapping over multiple lines, they only "
"reduce readability."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:420
msgid "Boolean operators"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:422
msgid ""
"Prefer the plain English versions of boolean operators, as they are the most "
"accessible:"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:424
msgid "Use ``and`` instead of ``&&``."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:425
msgid "Use ``or`` instead of ``||``."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:426
msgid "Use ``not`` instead of ``!``."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:428
msgid ""
"You may also use parentheses around boolean operators to clear any "
"ambiguity. This can make long expressions easier to read."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:450
#: ../../docs/tutorials/shaders/shaders_style_guide.rst:190
msgid "Comment spacing"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:452
msgid ""
"Regular comments (``#``) and documentation comments (``##``) should start "
"with a space, but not code that you comment out. Additionally, code region "
"comments (``#region``/``#endregion``) must follow that precise syntax, so "
"they should not start with a space."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:457
msgid ""
"Using a space for regular and documentation comments helps differentiate "
"text comments from disabled code."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:480
msgid ""
"In the script editor, to toggle commenting of the selected code, press :kbd:"
"`Ctrl + K`. This feature adds/removes a single ``#`` sign before any code on "
"the selected lines."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:485
#: ../../docs/tutorials/shaders/shaders_style_guide.rst:222
msgid "Whitespace"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:487
msgid ""
"Always use one space around operators and after commas. Also, avoid extra "
"spaces in dictionary references and function calls."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:514
#: ../../docs/tutorials/shaders/shaders_style_guide.rst:243
msgid "Don't use spaces to align expressions vertically:"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:523
msgid "Quotes"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:525
msgid ""
"Use double quotes unless single quotes make it possible to escape fewer "
"characters in a given string. See the examples below:"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:543
msgid "Numbers"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:545
msgid ""
"Don't omit the leading or trailing zero in floating-point numbers. "
"Otherwise, this makes them less readable and harder to distinguish from "
"integers at a glance."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:567
msgid ""
"Use lowercase for letters in hexadecimal numbers, as their lower height "
"makes the number easier to read."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:586
msgid ""
"Take advantage of GDScript's underscores in literals to make large numbers "
"more readable."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:616
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_style_guide.rst:197
#: ../../docs/tutorials/shaders/shaders_style_guide.rst:294
msgid "Naming conventions"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:618
#: ../../docs/tutorials/shaders/shaders_style_guide.rst:296
msgid ""
"These naming conventions follow the Godot Engine style. Breaking these will "
"make your code clash with the built-in naming conventions, leading to "
"inconsistent code."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:623
msgid "File names"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:625
msgid ""
"Use snake_case for file names. For named classes, convert the PascalCase "
"class name to snake_case::"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:638
msgid ""
"This is consistent with how C++ files are named in Godot's source code. This "
"also avoids case sensitivity issues that can crop up when exporting a "
"project from Windows to other platforms."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:643
msgid "Classes and nodes"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:645
msgid "Use PascalCase for class and node names:"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:651
msgid "Also use PascalCase when loading a class into a constant or a variable:"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:658
#: ../../docs/tutorials/shaders/shaders_style_guide.rst:301
msgid "Functions and variables"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:660
#: ../../docs/tutorials/shaders/shaders_style_guide.rst:303
msgid "Use snake\\_case to name functions and variables:"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:667
msgid ""
"Prepend a single underscore (\\_) to virtual methods functions the user must "
"override, private functions, and private variables:"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:678
msgid "Use the past tense to name signals:"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:686
msgid "Constants and enums"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:688
#: ../../docs/tutorials/shaders/shaders_style_guide.rst:314
msgid ""
"Write constants with CONSTANT\\_CASE, that is to say in all caps with an "
"underscore (\\_) to separate words:"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:695
msgid ""
"Use PascalCase for enum *names* and CONSTANT\\_CASE for their members, as "
"they are constants:"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:709
#: ../../docs/tutorials/shaders/shaders_style_guide.rst:361
msgid "Code order"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:711
msgid ""
"This first section focuses on code order. For formatting, see :ref:"
"`formatting`. For naming conventions, see :ref:`naming_conventions`."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:714
msgid "We suggest to organize GDScript code this way:"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:739
#: ../../docs/tutorials/shaders/shaders_style_guide.rst:380
msgid ""
"We optimized the order to make it easy to read the code from top to bottom, "
"to help developers reading the code for the first time understand how it "
"works, and to avoid errors linked to the order of variable declarations."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:743
msgid "This code order follows four rules of thumb:"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:745
msgid "Properties and signals come first, followed by methods."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:746
msgid "Public comes before private."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:747
msgid "Virtual callbacks come before the class's interface."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:748
msgid ""
"The object's construction and initialization functions, ``_init`` and "
"``_ready``, come before functions that modify the object at runtime."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:753
msgid "Class declaration"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:755
msgid ""
"If the code is meant to run in the editor, place the ``@tool`` annotation on "
"the first line of the script."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:758
msgid ""
"Follow with the ``class_name`` if necessary. You can turn a GDScript file "
"into a global type in your project using this feature. For more information, "
"see :ref:`doc_gdscript`."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:762
msgid "Then, add the ``extends`` keyword if the class extends a built-in type."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:764
msgid ""
"Following that, you should have the class's optional :ref:`documentation "
"comments <doc_gdscript_documentation_comments>`. You can use that to explain "
"the role of your class to your teammates, how it works, and how other "
"developers should use it, for example."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:779
msgid "Signals and properties"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:781
msgid ""
"Write signal declarations, followed by properties, that is to say, member "
"variables, after the docstring."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:784
msgid ""
"Enums should come after signals, as you can use them as export hints for "
"other properties."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:787
msgid ""
"Then, write constants, exported variables, public, private, and onready "
"variables, in that order."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:814
msgid ""
"The GDScript compiler evaluates onready variables right before the "
"``_ready`` callback. You can use that to cache node dependencies, that is to "
"say, to get child nodes in the scene that your class relies on. This is what "
"the example above shows."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:820
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_style_guide.rst:268
msgid "Member variables"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:822
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_style_guide.rst:270
msgid ""
"Don't declare member variables if they are only used locally in a method, as "
"it makes the code more difficult to follow. Instead, declare them as local "
"variables in the method's body."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:827
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_style_guide.rst:275
#: ../../docs/tutorials/shaders/shaders_style_guide.rst:391
msgid "Local variables"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:829
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_style_guide.rst:277
#: ../../docs/tutorials/shaders/shaders_style_guide.rst:393
msgid ""
"Declare local variables as close as possible to their first use. This makes "
"it easier to follow the code, without having to scroll too much to find "
"where the variable was declared."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:834
msgid "Methods and static functions"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:836
msgid "After the class's properties come the methods."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:838
msgid ""
"Start with the ``_init()`` callback method, that the engine will call upon "
"creating the object in memory. Follow with the ``_ready()`` callback, that "
"Godot calls when it adds a node to the scene tree."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:842
msgid ""
"These functions should come first because they show how the object is "
"initialized."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:845
msgid ""
"Other built-in virtual callbacks, like ``_unhandled_input()`` and "
"``_physics_process``, should come next. These control the object's main loop "
"and interactions with the game engine."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:849
msgid ""
"The rest of the class's interface, public and private methods, come after "
"that, in that order."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:886
msgid "Static typing"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:888
msgid ""
"Since Godot 3.1, GDScript supports :ref:`optional static "
"typing<doc_gdscript_static_typing>`."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:891
msgid "Declared types"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:893
msgid "To declare a variable's type, use ``<variable>: <type>``:"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:899
msgid "To declare the return type of a function, use ``-> <type>``:"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:906
msgid "Inferred types"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:908
msgid ""
"In most cases you can let the compiler infer the type, using ``:=``. Prefer "
"``:=`` when the type is written on the same line as the assignment, "
"otherwise prefer writing the type explicitly."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:921
msgid ""
"Include the type hint when the type is ambiguous, and omit the type hint "
"when it's redundant."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:936
msgid ""
"In some cases, the type must be stated explicitly, otherwise the behavior "
"will not be as expected because the compiler will only be able to use the "
"function's return type. For example, ``get_node()`` cannot infer a type "
"unless the scene or file of the node is loaded in memory. In this case, you "
"should set the type explicitly."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:950
msgid ""
"Alternatively, you can use the ``as`` keyword to cast the return type, and "
"that type will be used to infer the type of the var."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_styleguide.rst:960
msgid ""
"This option is also considered more :ref:`type-"
"safe<doc_gdscript_static_typing_safe_lines>` than the first."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/static_typing.rst:4
msgid "Static typing in GDScript"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/static_typing.rst:8
msgid "how to use static typing in GDScript;"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/static_typing.rst:9
msgid "that static types can help you avoid bugs;"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/static_typing.rst:10
msgid "that static typing improves your experience with the editor."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/static_typing.rst:12
msgid ""
"Where and how you use this language feature is entirely up to you: you can "
"use it only in some sensitive GDScript files, use it everywhere, or don't "
"use it at all."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/static_typing.rst:15
msgid ""
"Static types can be used on variables, constants, functions, parameters, and "
"return types."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/static_typing.rst:19
msgid "A brief look at static typing"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/static_typing.rst:21
msgid ""
"With static typing, GDScript can detect more errors without even running the "
"code. Also type hints give you and your teammates more information as you're "
"working, as the arguments' types show up when you call a method. Static "
"typing improves editor autocompletion and :ref:`documentation "
"<doc_gdscript_documentation_comments>` of your scripts."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/static_typing.rst:27
msgid ""
"Imagine you're programming an inventory system. You code an ``Item`` class, "
"then an ``Inventory``. To add items to the inventory, the people who work "
"with your code should always pass an ``Item`` to the ``Inventory.add()`` "
"method. With types, you can enforce this::"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/static_typing.rst:41
msgid ""
"Static types also give you better code completion options. Below, you can "
"see the difference between a dynamic and a static typed completion options."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/static_typing.rst:44
msgid ""
"You've probably encountered a lack of autocomplete suggestions after a dot:"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/static_typing.rst:-1
msgid "Completion options for dynamic typed code."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/static_typing.rst:49
msgid ""
"This is due to dynamic code. Godot cannot know what value type you're "
"passing to the function. If you write the type explicitly however, you will "
"get all methods, properties, constants, etc. from the value:"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/static_typing.rst:-1
msgid "Completion options for static typed code."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/static_typing.rst:58
msgid ""
"If you prefer static typing, we recommend enabling the **Text Editor > "
"Completion > Add Type Hints** editor setting. Also consider enabling `some "
"warnings <Warning system_>`_ that are disabled by default."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/static_typing.rst:62
msgid ""
"Also, typed GDScript improves performance by using optimized opcodes when "
"operand/argument types are known at compile time. More GDScript "
"optimizations are planned in the future, such as JIT/AOT compilation."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/static_typing.rst:66
msgid ""
"Overall, typed programming gives you a more structured experience. It helps "
"prevent errors and improves the self-documenting aspect of your scripts. "
"This is especially helpful when you're working in a team or on a long-term "
"project: studies have shown that developers spend most of their time reading "
"other people's code, or scripts they wrote in the past and forgot about. The "
"clearer and the more structured the code, the faster it is to understand, "
"the faster you can move forward."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/static_typing.rst:75
msgid "How to use static typing"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/static_typing.rst:77
msgid ""
"To define the type of a variable, parameter, or constant, write a colon "
"after the name, followed by its type. E.g. ``var health: int``. This forces "
"the variable's type to always stay the same::"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/static_typing.rst:86
msgid ""
"Godot will try to infer types if you write a colon, but you omit the type::"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/static_typing.rst:95
msgid "There is no difference between ``=`` and ``:=`` for constants."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/static_typing.rst:96
msgid ""
"You don't need to write type hints for constants, as Godot sets it "
"automatically from the assigned value. But you can still do so to make the "
"intent of your code clearer. Also, this is useful for typed arrays (like "
"``const A: Array[int] = [1, 2, 3]``), since untyped arrays are used by "
"default."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/static_typing.rst:102
msgid "What can be a type hint"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/static_typing.rst:104
msgid "Here is a complete list of what can be used as a type hint:"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/static_typing.rst:106
msgid ""
"``Variant``. Any type. In most cases this is not much different from an "
"untyped declaration, but increases readability. As a return type, forces the "
"function to explicitly return some value."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/static_typing.rst:109
msgid ""
"*(Only return type)* ``void``. Indicates that the function does not return "
"any value."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/static_typing.rst:110
msgid ":ref:`Built-in types <doc_gdscript_builtin_types>`."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/static_typing.rst:111
msgid "Native classes (``Object``, ``Node``, ``Area2D``, ``Camera2D``, etc.)."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/static_typing.rst:112
msgid ":ref:`Global classes <doc_gdscript_basics_class_name>`."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/static_typing.rst:113
msgid ":ref:`Inner classes <doc_gdscript_basics_inner_classes>`."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/static_typing.rst:114
msgid ""
"Global, native and custom named enums. Note that an enum type is just an "
"``int``, there is no guarantee that the value belongs to the set of enum "
"values."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/static_typing.rst:116
msgid ""
"Constants (including local ones) if they contain a preloaded class or enum."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/static_typing.rst:118
msgid ""
"You can use any class, including your custom classes, as types. There are "
"two ways to use them in scripts. The first method is to preload the script "
"you want to use as a type in a constant::"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/static_typing.rst:125
msgid ""
"The second method is to use the ``class_name`` keyword when you create. For "
"the example above, your ``rifle.gd`` would look like this::"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/static_typing.rst:131
msgid ""
"If you use ``class_name``, Godot registers the ``Rifle`` type globally in "
"the editor, and you can use it anywhere, without having to preload it into a "
"constant::"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/static_typing.rst:137
msgid "Specify the return type of a function with the arrow ``->``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/static_typing.rst:139
msgid ""
"To define the return type of a function, write a dash and a right angle "
"bracket ``->`` after its declaration, followed by the return type::"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/static_typing.rst:145
msgid ""
"The type ``void`` means the function does not return anything. You can use "
"any type, as with variables::"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/static_typing.rst:152
msgid "You can also use your own classes as return types::"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/static_typing.rst:164
msgid "Covariance and contravariance"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/static_typing.rst:166
msgid ""
"When inheriting base class methods, you should follow the `Liskov "
"substitution principle <https://en.wikipedia.org/wiki/"
"Liskov_substitution_principle>`__."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/static_typing.rst:169
msgid ""
"**Covariance:** When you inherit a method, you can specify a return type "
"that is more specific (**subtype**) than the parent method."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/static_typing.rst:172
msgid ""
"**Contravariance:** When you inherit a method, you can specify a parameter "
"type that is less specific (**supertype**) than the parent method."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/static_typing.rst:194
msgid "Specify the element type of an ``Array``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/static_typing.rst:196
msgid "To define the type of an ``Array``, enclose the type name in ``[]``."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/static_typing.rst:198
msgid ""
"An array's type applies to ``for`` loop variables, as well as some operators "
"like ``[]``, ``[]=``, and ``+``. Array methods (such as ``push_back``) and "
"other operators (such as ``==``) are still untyped. Built-in types, native "
"and custom classes, and enums may be used as element types. Nested array "
"types are not supported."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/static_typing.rst:218
msgid ""
"Since Godot 4.2, you can also specify a type for the loop variable in a "
"``for`` loop. For instance, you can write::"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/static_typing.rst:225
msgid ""
"The array will remain untyped, but the ``name`` variable within the ``for`` "
"loop will always be of ``String`` type."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/static_typing.rst:229
msgid "Type casting"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/static_typing.rst:231
msgid ""
"Type casting is an important concept in typed languages. Casting is the "
"conversion of a value from one type to another."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/static_typing.rst:234
msgid ""
"Imagine an ``Enemy`` in your game, that ``extends Area2D``. You want it to "
"collide with the ``Player``, a ``CharacterBody2D`` with a script called "
"``PlayerController`` attached to it. You use the ``body_entered`` signal to "
"detect the collision. With typed code, the body you detect is going to be a "
"generic ``PhysicsBody2D``, and not your ``PlayerController`` on the "
"``_on_body_entered`` callback."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/static_typing.rst:240
msgid ""
"You can check if this ``PhysicsBody2D`` is your ``Player`` with the ``as`` "
"keyword, and using the colon ``:`` again to force the variable to use this "
"type. This forces the variable to stick to the ``PlayerController`` type::"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/static_typing.rst:251
msgid ""
"As we're dealing with a custom type, if the ``body`` doesn't extend "
"``PlayerController``, the ``player`` variable will be set to ``null``. We "
"can use this to check if the body is the player or not. We will also get "
"full autocompletion on the player variable thanks to that cast."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/static_typing.rst:258
msgid ""
"The ``as`` keyword silently casts the variable to ``null`` in case of a type "
"mismatch at runtime, without an error/warning. While this may be convenient "
"in some cases, it can also lead to bugs. Use the ``as`` keyword only if this "
"behavior is intended. A safer alternative is to use the ``is`` keyword::"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/static_typing.rst:272
msgid "or ``assert()`` statement::"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/static_typing.rst:284
msgid ""
"If you try to cast with a built-in type and it fails, Godot will throw an "
"error."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/static_typing.rst:289
msgid "Safe lines"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/static_typing.rst:291
msgid ""
"You can also use casting to ensure safe lines. Safe lines are a tool to tell "
"you when ambiguous lines of code are type-safe. As you can mix and match "
"typed and dynamic code, at times, Godot doesn't have enough information to "
"know if an instruction will trigger an error or not at runtime."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/static_typing.rst:296
msgid ""
"This happens when you get a child node. Let's take a timer for example: with "
"dynamic code, you can get the node with ``$Timer``. GDScript supports `duck-"
"typing <https://stackoverflow.com/a/4205163/8125343>`__, so even if your "
"timer is of type ``Timer``, it is also a ``Node`` and an ``Object``, two "
"classes it extends. With dynamic GDScript, you also don't care about the "
"node's type as long as it has the methods you need to call."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/static_typing.rst:303
msgid ""
"You can use casting to tell Godot the type you expect when you get a node: "
"``($Timer as Timer)``, ``($Player as CharacterBody2D)``, etc. Godot will "
"ensure the type works and if so, the line number will turn green at the left "
"of the script editor."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/static_typing.rst:311
msgid "Unsafe vs Safe Line"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/static_typing.rst:311
msgid "Unsafe line (line 7) vs Safe Lines (line 6 and 8)"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/static_typing.rst:315
msgid ""
"Safe lines do not always mean better or more reliable code. See the note "
"above about the ``as`` keyword. For example::"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/static_typing.rst:321
msgid ""
"Even though ``node_2`` declaration is marked as an unsafe line, it is more "
"reliable than ``node_1`` declaration. Because if you change the node type in "
"the scene and accidentally forget to change it in the script, the error will "
"be detected immediately when the scene is loaded. Unlike ``node_1``, which "
"will be silently cast to ``null`` and the error will be detected later."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/static_typing.rst:329
msgid ""
"You can turn off safe lines or change their color in the editor settings."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/static_typing.rst:332
msgid "Typed or dynamic: stick to one style"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/static_typing.rst:334
msgid ""
"Typed GDScript and dynamic GDScript can coexist in the same project. But "
"it's recommended to stick to either style for consistency in your codebase, "
"and for your peers. It's easier for everyone to work together if you follow "
"the same guidelines, and faster to read and understand other people's code."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/static_typing.rst:339
msgid ""
"Typed code takes a little more writing, but you get the benefits we "
"discussed above. Here's an example of the same, empty script, in a dynamic "
"style::"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/static_typing.rst:352
msgid "And with static typing::"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/static_typing.rst:364
msgid ""
"As you can see, you can also use types with the engine's virtual methods. "
"Signal callbacks, like any methods, can also use types. Here's a "
"``body_entered`` signal in a dynamic style::"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/static_typing.rst:371
msgid "And the same callback, with type hints::"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/static_typing.rst:377
msgid "Warning system"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/static_typing.rst:381
msgid ""
"Detailed documentation about the GDScript warning system has been moved to :"
"ref:`doc_gdscript_warning_system`."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/static_typing.rst:384
msgid ""
"From version 3.1, Godot gives you warnings about your code as you write it: "
"the engine identifies sections of your code that may lead to issues at "
"runtime, but lets you decide whether or not you want to leave the code as it "
"is."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/static_typing.rst:388
msgid ""
"We have a number of warnings aimed specifically at users of typed GDScript. "
"By default, these warnings are disabled, you can enable them in Project "
"Settings (**Debug > GDScript**, make sure **Advanced Settings** is enabled)."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/static_typing.rst:392
msgid ""
"You can enable the ``UNTYPED_DECLARATION`` warning if you want to always use "
"static types. Additionally, you can enable the ``INFERRED_DECLARATION`` "
"warning if you prefer a more readable and reliable, but more verbose syntax."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/static_typing.rst:396
msgid ""
"``UNSAFE_*`` warnings make unsafe operations more noticeable, than unsafe "
"lines. Currently, ``UNSAFE_*`` warnings do not cover all cases that unsafe "
"lines cover."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/static_typing.rst:400
msgid "Common unsafe operations and their safe counterparts"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/static_typing.rst:403
msgid "``UNSAFE_PROPERTY_ACCESS`` and ``UNSAFE_METHOD_ACCESS`` warnings"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/static_typing.rst:405
msgid ""
"In this example, we aim to set a property and call a method on an object "
"that has a script attached with ``class_name MyScript`` and that ``extends "
"Node2D``. If we have a reference to the object as a ``Node2D`` (for "
"instance, as it was passed to us by the physics system), we can first check "
"if the property and method exist and then set and call them if they do::"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/static_typing.rst:417
msgid ""
"However, this code will produce ``UNSAFE_PROPERTY_ACCESS`` and "
"``UNSAFE_METHOD_ACCESS`` warnings as the property and method are not present "
"in the referenced type - in this case a ``Node2D``. To make these operations "
"safe, you can first check if the object is of type ``MyScript`` using the "
"``is`` keyword and then declare a variable with the type ``MyScript`` on "
"which you can set its properties and call its methods::"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/static_typing.rst:429
msgid ""
"Alternatively, you can declare a variable and use the ``as`` operator to try "
"to cast the object. You'll then want to check whether the cast was "
"successful by confirming that the variable was assigned::"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/static_typing.rst:439
msgid "``UNSAFE_CAST`` warning"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/static_typing.rst:441
msgid ""
"In this example, we would like the label connected to an object entering our "
"collision area to show the area's name. Once the object enters the collision "
"area, the physics system sends a signal with a ``Node2D`` object, and the "
"most straightforward (but not statically typed) solution to do what we want "
"could be achieved like this::"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/static_typing.rst:450
msgid ""
"This piece of code produces an ``UNSAFE_PROPERTY_ACCESS`` warning because "
"``label`` is not defined in ``Node2D``. To solve this, we could first check "
"if the ``label`` property exist and cast it to type ``Label`` before "
"settings its text property like so::"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/static_typing.rst:459
msgid ""
"However, this produces an ``UNSAFE_CAST`` warning because ``body.label`` is "
"of a ``Variant`` type. To safely get the property in the type you want, you "
"can use the ``Object.get()`` method which returns the object as a "
"``Variant`` value or returns ``null`` if the property doesn't exist. You can "
"then determine whether the property contains an object of the right type "
"using the ``is`` keyword, and finally declare a statically typed variable "
"with the object::"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/static_typing.rst:473
msgid "Cases where you can't specify types"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/static_typing.rst:475
msgid ""
"To wrap up this introduction, let's mention cases where you can't use type "
"hints. This will trigger a **syntax error**."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/static_typing.rst:478
msgid ""
"You can't specify the type of individual elements in an array or a "
"dictionary::"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/static_typing.rst:487
msgid "Nested types are not currently supported::"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/static_typing.rst:491
msgid "Typed dictionaries are not currently supported::"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/static_typing.rst:498
msgid ""
"Typed GDScript is a powerful tool. It helps you write more structured code, "
"avoid common errors, and create scalable and reliable systems. Static types "
"improve GDScript performance and more optimizations are planned for the "
"future."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/warning_system.rst:4
msgid "GDScript warning system"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/warning_system.rst:6
msgid ""
"The GDScript warning system complements :ref:`static typing "
"<doc_gdscript_static_typing>` (but it can work without static typing too). "
"It's here to help you avoid mistakes that are hard to spot during "
"development, and that may lead to runtime errors."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/warning_system.rst:11
msgid ""
"You can configure warnings in the Project Settings under the section called "
"**GDScript**:"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/warning_system.rst:17
msgid ""
"You must enable **Advanced Settings** in order to see the GDScript section "
"in the sidebar. You can also search for \"GDScript\" when Advanced Settings "
"is off."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/warning_system.rst:21
msgid ""
"You can find a list of warnings for the active GDScript file in the script "
"editor's status bar. The example below has 2 warnings:"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/warning_system.rst:26
msgid ""
"To ignore specific warnings in one file, insert an annotation of the form "
"``@warning_ignore(\"warning-id\")``, or click on the ignore link to the left "
"of the warning's description. Godot will add an annotation above the "
"corresponding line and the code won't trigger the corresponding warning "
"anymore:"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/warning_system.rst:34
msgid ""
"Warnings won't prevent the game from running, but you can turn them into "
"errors if you'd like. This way your game won't compile unless you fix all "
"warnings. Head to the ``GDScript`` section of the Project Settings to turn "
"on this option to the warning that you want. Here's the same file as the "
"previous example with the warning ``unused_variable`` as an error turned on:"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_format_string.rst:4
msgid "GDScript format strings"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_format_string.rst:6
msgid ""
"GDScript offers a feature called *format strings*, which allows reusing text "
"templates to succinctly create different but similar strings."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_format_string.rst:9
msgid ""
"Format strings are just like normal strings, except they contain certain "
"placeholder character-sequences. These placeholders can then easily be "
"replaced by parameters handed to the format string."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_format_string.rst:13
msgid ""
"As an example, with ``%s`` as a placeholder, the format string ``\"Hello %s, "
"how are you?\"`` can easily be changed to ``\"Hello World, how are you?\"``. "
"Notice the placeholder is in the middle of the string; modifying it without "
"format strings could be cumbersome."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_format_string.rst:20
msgid "Usage in GDScript"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_format_string.rst:22
msgid "Examine this concrete GDScript example:"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_format_string.rst:35
msgid ""
"Placeholders always start with a ``%``, but the next character or "
"characters, the *format specifier*, determines how the given value is "
"converted to a string."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_format_string.rst:39
msgid ""
"The ``%s`` seen in the example above is the simplest placeholder and works "
"for most use cases: it converts the value by the same method by which an "
"implicit String conversion or ``str()`` would convert it. Strings remain "
"unchanged, Booleans turn into either ``\"True\"`` or ``\"False\"``, an "
"integral or real number becomes a decimal, other types usually return their "
"data in a human-readable string."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_format_string.rst:46
msgid ""
"There is also another way to format text in GDScript, namely the ``String."
"format()`` method. It replaces all occurrences of a key in the string with "
"the corresponding value. The method can handle arrays or dictionaries for "
"the key/value pairs."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_format_string.rst:50
msgid ""
"Arrays can be used as key, index, or mixed style (see below examples). Order "
"only matters when the index or mixed style of Array is used."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_format_string.rst:53
msgid "A quick example in GDScript:"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_format_string.rst:66
msgid ""
"There are other `format specifiers`_, but they are only applicable when "
"using the ``%`` operator."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_format_string.rst:71
msgid "Multiple placeholders"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_format_string.rst:73
msgid ""
"Format strings may contain multiple placeholders. In such a case, the values "
"are handed in the form of an array, one value per placeholder (unless using "
"a format specifier with ``*``, see `dynamic padding`_):"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_format_string.rst:85
msgid ""
"Note the values are inserted in order. Remember all placeholders must be "
"replaced at once, so there must be an appropriate number of values."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_format_string.rst:90
msgid "Format specifiers"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_format_string.rst:92
msgid ""
"There are format specifiers other than ``s`` that can be used in "
"placeholders. They consist of one or more characters. Some of them work by "
"themselves like ``s``, some appear before other characters, some only work "
"with certain values or characters."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_format_string.rst:99
msgid "Placeholder types"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_format_string.rst:101
msgid ""
"One and only one of these must always appear as the last character in a "
"format specifier. Apart from ``s``, these require certain types of "
"parameters."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_format_string.rst:105
msgid "``s``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_format_string.rst:105
msgid ""
"**Simple** conversion to String by the same method as implicit String "
"conversion."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_format_string.rst:108
msgid "``c``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_format_string.rst:108
msgid ""
"A single **Unicode character**. Expects an unsigned 8-bit integer (0-255) "
"for a code point or a single-character string."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_format_string.rst:111
msgid "``d``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_format_string.rst:111
msgid ""
"A **decimal integral** number. Expects an integral or real number (will be "
"floored)."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_format_string.rst:114
msgid "``o``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_format_string.rst:114
msgid ""
"An **octal integral** number. Expects an integral or real number (will be "
"floored)."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_format_string.rst:117
msgid "``x``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_format_string.rst:117
msgid ""
"A **hexadecimal integral** number with **lower-case** letters. Expects an "
"integral or real number (will be floored)."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_format_string.rst:120
msgid "``X``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_format_string.rst:120
msgid ""
"A **hexadecimal integral** number with **upper-case** letters. Expects an "
"integral or real number (will be floored)."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_format_string.rst:123
msgid "``f``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_format_string.rst:123
msgid "A **decimal real** number. Expects an integral or real number."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_format_string.rst:125
msgid "``v``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_format_string.rst:125
msgid ""
"A **vector**. Expects any float or int-based vector object ( ``Vector2``, "
"``Vector3``, ``Vector4``, ``Vector2i``, ``Vector3i`` or ``Vector4i``). Will "
"display the vector coordinates in parentheses, formatting each coordinate as "
"if it was an ``%f``, and using the same modifiers."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_format_string.rst:134
msgid "Placeholder modifiers"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_format_string.rst:136
msgid ""
"These characters appear before the above. Some of them work only under "
"certain conditions."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_format_string.rst:140
msgid "``+``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_format_string.rst:140
msgid "In number specifiers, **show + sign** if positive."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_format_string.rst:142
msgid ""
"Set **padding**. Padded with spaces or with zeroes if integer starts with "
"``0`` in an integer or real number placeholder. The leading ``0`` is ignored "
"if ``-`` is present. When used after ``.``, see ``.``."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_format_string.rst:147
msgid "``.``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_format_string.rst:147
msgid ""
"Before ``f`` or ``v``, set **precision** to 0 decimal places. Can be "
"followed up with numbers to change. Padded with zeroes."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_format_string.rst:150
msgid "``-``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_format_string.rst:150
msgid "**Pad to the right** rather than the left."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_format_string.rst:152
msgid "``*``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_format_string.rst:152
msgid ""
"**Dynamic padding**, expect additional integral parameter to set padding or "
"precision after ``.``, see `dynamic padding`_."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_format_string.rst:158
msgid "Padding"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_format_string.rst:160
msgid ""
"The ``.`` (*dot*), ``*`` (*asterisk*), ``-`` (*minus sign*) and digit (``0``-"
"``9``) characters are used for padding. This allows printing several values "
"aligned vertically as if in a column, provided a fixed-width font is used."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_format_string.rst:165
msgid "To pad a string to a minimum length, add an integer to the specifier:"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_format_string.rst:173
msgid ""
"If the integer starts with ``0``, integral values are padded with zeroes "
"instead of white space:"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_format_string.rst:181
msgid ""
"Precision can be specified for real numbers by adding a ``.`` (*dot*) with "
"an integer following it. With no integer after ``.``, a precision of 0 is "
"used, rounding to integral value. The integer to use for padding must appear "
"before the dot."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_format_string.rst:193
msgid ""
"The ``-`` character will cause padding to the right rather than the left, "
"useful for right text alignment:"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_format_string.rst:204
msgid "Dynamic padding"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_format_string.rst:206
msgid ""
"By using the ``*`` (*asterisk*) character, the padding or precision can be "
"set without modifying the format string. It is used in place of an integer "
"in the format specifier. The values for padding and precision are then "
"passed when formatting:"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_format_string.rst:219
msgid ""
"It is still possible to pad with zeroes in integer placeholders by adding "
"``0`` before ``*``:"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_format_string.rst:229
msgid "Escape sequence"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_format_string.rst:231
msgid ""
"To insert a literal ``%`` character into a format string, it must be escaped "
"to avoid reading it as a placeholder. This is done by doubling the character:"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_format_string.rst:242
msgid "Format method examples"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_format_string.rst:244
msgid ""
"The following are some examples of how to use the various invocations of the "
"``String.format``  method."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_format_string.rst:249
#: ../../docs/tutorials/scripting/gdscript/gdscript_format_string.rst:271
msgid "**Type**"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_format_string.rst:249
msgid "**Style**"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_format_string.rst:249
#: ../../docs/tutorials/scripting/gdscript/gdscript_format_string.rst:271
#: ../../docs/tutorials/scripting/gdscript/gdscript_format_string.rst:284
msgid "**Result**"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_format_string.rst:251
#: ../../docs/tutorials/scripting/gdscript/gdscript_format_string.rst:253
#: ../../docs/tutorials/scripting/gdscript/gdscript_format_string.rst:255
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:802
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:192
msgid "Dictionary"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_format_string.rst:251
#: ../../docs/tutorials/scripting/gdscript/gdscript_format_string.rst:257
msgid "key"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_format_string.rst:251
msgid ""
"``\"Hi, {name} v{version}!\".format({\"name\":\"Godette\", \"version\":"
"\"3.0\"})``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_format_string.rst:251
#: ../../docs/tutorials/scripting/gdscript/gdscript_format_string.rst:253
#: ../../docs/tutorials/scripting/gdscript/gdscript_format_string.rst:255
#: ../../docs/tutorials/scripting/gdscript/gdscript_format_string.rst:257
#: ../../docs/tutorials/scripting/gdscript/gdscript_format_string.rst:259
#: ../../docs/tutorials/scripting/gdscript/gdscript_format_string.rst:261
#: ../../docs/tutorials/scripting/gdscript/gdscript_format_string.rst:263
msgid "Hi, Godette v3.0!"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_format_string.rst:253
#: ../../docs/tutorials/scripting/gdscript/gdscript_format_string.rst:259
msgid "index"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_format_string.rst:253
msgid "``\"Hi, {0} v{1}!\".format({\"0\":\"Godette\", \"1\":\"3.0\"})``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_format_string.rst:255
#: ../../docs/tutorials/scripting/gdscript/gdscript_format_string.rst:261
msgid "mix"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_format_string.rst:255
msgid ""
"``\"Hi, {0} v{version}!\".format({\"0\":\"Godette\", \"version\":\"3.0\"})``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_format_string.rst:257
#: ../../docs/tutorials/scripting/gdscript/gdscript_format_string.rst:259
#: ../../docs/tutorials/scripting/gdscript/gdscript_format_string.rst:261
#: ../../docs/tutorials/scripting/gdscript/gdscript_format_string.rst:263
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:790
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:98
msgid "Array"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_format_string.rst:257
msgid ""
"``\"Hi, {name} v{version}!\".format([[\"version\",\"3.0\"], [\"name\","
"\"Godette\"]])``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_format_string.rst:259
msgid "``\"Hi, {0} v{1}!\".format([\"Godette\",\"3.0\"])``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_format_string.rst:261
msgid "``\"Hi, {name} v{0}!\".format([3.0, [\"name\",\"Godette\"]])``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_format_string.rst:263
msgid "no index"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_format_string.rst:263
msgid "``\"Hi, {} v{}!\".format([\"Godette\", 3.0], \"{}\")``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_format_string.rst:266
msgid ""
"Placeholders can also be customized when using ``String.format``, here's "
"some examples of that functionality."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_format_string.rst:273
msgid "Infix (default)"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_format_string.rst:273
msgid "``\"Hi, {0} v{1}\".format([\"Godette\", \"3.0\"], \"{_}\")``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_format_string.rst:273
#: ../../docs/tutorials/scripting/gdscript/gdscript_format_string.rst:275
#: ../../docs/tutorials/scripting/gdscript/gdscript_format_string.rst:277
msgid "Hi, Godette v3.0"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_format_string.rst:275
msgid "Postfix"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_format_string.rst:275
msgid "``\"Hi, 0% v1%\".format([\"Godette\", \"3.0\"], \"_%\")``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_format_string.rst:277
msgid "Prefix"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_format_string.rst:277
msgid "``\"Hi, %0 v%1\".format([\"Godette\", \"3.0\"], \"%_\")``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_format_string.rst:280
msgid ""
"Combining both the ``String.format`` method and the ``%`` operator could be "
"useful, as ``String.format`` does not have a way to manipulate the "
"representation of numbers."
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_format_string.rst:286
msgid ""
"``\"Hi, {0} v{version}\".format({0:\"Godette\", \"version\":\"%0.2f\" % "
"3.114})``"
msgstr ""

#: ../../docs/tutorials/scripting/gdscript/gdscript_format_string.rst:286
msgid "Hi, Godette v3.11"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/index.rst:2
msgid "C#/.NET"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/index.rst:4
msgid ""
"C# is a high-level programming language developed by Microsoft. Godot "
"supports C# as an option for a scripting language, alongside Godot's own :"
"ref:`GDScript<toc-learn-scripting-gdscript>`."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/index.rst:7
msgid ""
"The standard Godot executable does not contain C# support out of the box. "
"Instead, to enable C# support for your project you need to `download a .NET "
"version <https://godotengine.org/download/>`_ of the editor from the Godot "
"website."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/index.rst:22
msgid "Godot API for C#"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/index.rst:24
msgid ""
"As a general purpose game engine Godot offers some high-level features as a "
"part of its API. Articles below explain how these features integrate into C# "
"and how C# API may be different from GDScript."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/index.rst:42
#, fuzzy
msgid "C# platform support"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/scripting/c_sharp/index.rst:44
msgid ""
"As of Godot 4.2 projects written in C# support all desktop platforms "
"(Windows, Linux, and macOS), as well as Android and iOS."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/index.rst:47
msgid "Android support is currently experimental and has a few limitations."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/index.rst:49
msgid ""
"Projects targeting Android need to target .NET 7.0 or higher. This requires "
"modifying the `.csproj` file generated by Godot for existing projects. The "
"following property is added to new projects created with 4.2 and can be "
"added to existing projects:"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/index.rst:58
msgid "Only some Android architectures are supported: ``arm64`` and ``x64``."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/index.rst:60
msgid "iOS support is currently experimental and has a few limitations."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/index.rst:62
msgid ""
"Projects targeting iOS need to target .NET 8.0 or higher. This requires "
"modifying the `.csproj` file generated by Godot for existing projects. The "
"following property is added to new projects created with 4.2 and can be "
"added to existing projects:"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/index.rst:71
msgid ""
"The official export templates for the iOS simulator only supports the "
"``x64`` architecture."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/index.rst:73
msgid "Exporting to iOS can only be done from a MacOS device."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/index.rst:75
msgid ""
"Currently, projects written in C# cannot be exported to the web platform. To "
"use C# on that platform, consider Godot 3 instead."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_basics.rst:4
msgid "C# basics"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_basics.rst:9
msgid ""
"This page provides a brief introduction to C#, both what it is and how to "
"use it in Godot. Afterwards, you may want to look at :ref:`how to use "
"specific features <doc_c_sharp_features>`, read about the :ref:`differences "
"between the C# and the GDScript API <doc_c_sharp_differences>`, and "
"(re)visit the :ref:`Scripting section <doc_scripting>` of the step-by-step "
"tutorial."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_basics.rst:16
msgid ""
"C# is a high-level programming language developed by Microsoft. In Godot, it "
"is implemented with .NET 6.0."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_basics.rst:21
msgid ""
"Projects written in C# using Godot 4 currently cannot be exported to the web "
"platform. To use C# on the web platform, consider Godot 3 instead. Android "
"and iOS platform support is available as of Godot 4.2, but is experimental "
"and :ref:`some limitations apply <doc_c_sharp_platforms>`."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_basics.rst:28
msgid ""
"This is **not** a full-scale tutorial on the C# language as a whole. If you "
"aren't already familiar with its syntax or features, see the `Microsoft C# "
"guide <https://docs.microsoft.com/en-us/dotnet/csharp/index>`_ or look for a "
"suitable introduction elsewhere."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_basics.rst:38
msgid ""
"Godot bundles the parts of .NET needed to run already compiled games. "
"However, Godot does not bundle the tools required to build and compile "
"games, such as MSBuild and the C# compiler. These are included in the .NET "
"SDK, and need to be installed separately."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_basics.rst:43
msgid ""
"In summary, you must have installed the .NET SDK **and** the .NET-enabled "
"version of Godot."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_basics.rst:46
msgid ""
"Download and install the latest stable version of the SDK from the `.NET "
"download page <https://dotnet.microsoft.com/download>`__."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_basics.rst:51
msgid ""
"Be sure to install the 64-bit version of the SDK(s) if you are using the 64-"
"bit version of Godot."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_basics.rst:54
msgid ""
"If you are building Godot from source, make sure to follow the steps to "
"enable .NET support in your build as outlined in the :ref:"
"`doc_compiling_with_dotnet` page."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_basics.rst:59
msgid "Configuring an external editor"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_basics.rst:61
msgid ""
"C# support in Godot's built-in script editor is minimal. Consider using an "
"external IDE or editor, such as  `Visual Studio Code <https://code."
"visualstudio.com/>`__ or MonoDevelop. These provide autocompletion, "
"debugging, and other useful features for C#. To select an external editor in "
"Godot, click on **Editor → Editor Settings** and scroll down to **Dotnet**. "
"Under **Dotnet**, click on **Editor**, and select your external editor of "
"choice. Godot currently supports the following external editors:"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_basics.rst:70
#, fuzzy
msgid "Visual Studio 2022"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_basics.rst:72
#, fuzzy
msgid "MonoDevelop"
msgstr "Razvoj"

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_basics.rst:73
msgid "Visual Studio for Mac"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_basics.rst:76
msgid "See the following sections for how to configure an external editor:"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_basics.rst:81
msgid ""
"After reading the \"Prerequisites\" section, you can download and install "
"`JetBrains Rider <https://www.jetbrains.com/rider/download>`__."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_basics.rst:84
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_basics.rst:99
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_basics.rst:132
#, fuzzy
msgid "In Godot's **Editor → Editor Settings** menu:"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_basics.rst:86
msgid ""
"Set **Dotnet** -> **Editor** -> **External Editor** to **JetBrains Rider**."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_basics.rst:88
msgid "In Rider:"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_basics.rst:90
msgid "Set **MSBuild version** to **.NET Core**."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_basics.rst:91
msgid "Install the **Godot support** plugin."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_basics.rst:96
msgid ""
"After reading the \"Prerequisites\" section, you can download and install "
"`Visual Studio Code <https://code.visualstudio.com/download>`__ (aka VS "
"Code)."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_basics.rst:101
msgid ""
"Set **Dotnet** -> **Editor** -> **External Editor** to **Visual Studio "
"Code**."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_basics.rst:103
#, fuzzy
msgid "In Visual Studio Code:"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_basics.rst:105
msgid ""
"Install the `C# <https://marketplace.visualstudio.com/items?itemName=ms-"
"dotnettools.csharp>`__ extension."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_basics.rst:109
msgid ""
"If you are using Linux you need to install the `Mono SDK <https://www.mono-"
"project.com/download/stable/#download-lin>`__ for the C# tools plugin to "
"work."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_basics.rst:112
msgid ""
"To configure a project for debugging, you need a ``tasks.json`` and ``launch."
"json`` file in the ``.vscode`` folder with the necessary configuration. An "
"example configuration can be found `here <https://github.com/godotengine/"
"godot-csharp-vscode/issues/43#issuecomment-1258321229>`__ . In the ``launch."
"json`` file, make sure the ``program`` parameter in the relevant "
"configuration points to your Godot executable, either by changing it to the "
"path of the executable or by defining a ``GODOT4`` environment variable that "
"points to the executable. Now, when you start the debugger in Visual Studio "
"Code, your Godot project will run."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_basics.rst:120
#, fuzzy
msgid "Visual Studio (Windows only)"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_basics.rst:122
msgid ""
"Download and install the latest version of `Visual Studio <https://"
"visualstudio.microsoft.com/downloads/>`__. Visual Studio will include the "
"required SDKs if you have the correct workloads selected, so you don't need "
"to manually install the things listed in the \"Prerequisites\" section."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_basics.rst:128
msgid "While installing Visual Studio, select this workload:"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_basics.rst:130
#, fuzzy
msgid ".NET desktop development"
msgstr "Razvoj"

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_basics.rst:134
msgid ""
"Set **Dotnet** -> **Editor** -> **External Editor** to **Visual Studio**."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_basics.rst:136
msgid ""
"If you see an error like \"Unable to find package Godot.NET.Sdk\", your "
"NuGet configuration may be incorrect and need to be fixed."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_basics.rst:139
msgid ""
"A simple way to fix the NuGet configuration file is to regenerate it. In a "
"file explorer window, go to ``%AppData%\\NuGet``. Rename or delete the "
"``NuGet.Config`` file. When you build your Godot project again, the file "
"will be automatically created with default values."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_basics.rst:145
msgid "Creating a C# script"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_basics.rst:147
msgid ""
"After you successfully set up C# for Godot, you should see the following "
"option when selecting **Attach Script** in the context menu of a node in "
"your scene:"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_basics.rst:152
msgid ""
"Note that while some specifics change, most concepts work the same when "
"using C# for scripting. If you're new to Godot, you may want to follow the "
"tutorials on :ref:`doc_scripting` at this point. While some documentation "
"pages still lack C# examples, most notions can be transferred from GDScript."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_basics.rst:159
msgid "Project setup and workflow"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_basics.rst:161
msgid ""
"When you create the first C# script, Godot initializes the C# project files "
"for your Godot project. This includes generating a C# solution (``.sln``) "
"and a project file (``.csproj``), as well as some utility files and folders "
"(``.godot/mono``). All of these but ``.godot/mono`` are important and should "
"be committed to your version control system. Everything under ``.godot`` can "
"be safely added to the ignore list of your VCS. When troubleshooting, it can "
"sometimes help to delete the ``.godot/mono`` folder and let it regenerate."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_basics.rst:174
msgid ""
"Here's a blank C# script with some comments to demonstrate how it works."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_basics.rst:200
msgid ""
"As you can see, functions normally in global scope in GDScript like Godot's "
"``print`` function are available in the ``GD`` static class which is part of "
"the ``Godot`` namespace. For a full list of methods in the ``GD`` class, see "
"the class reference pages for :ref:`@GDScript <class_@gdscript>` and :ref:"
"`@GlobalScope <class_@globalscope>`."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_basics.rst:208
msgid ""
"Keep in mind that the class you wish to attach to your node should have the "
"same name as the ``.cs`` file. Otherwise, you will get the following error:"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_basics.rst:211
msgid "*\"Cannot find class XXX for script res://XXX.cs\"*"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_basics.rst:214
msgid "General differences between C# and GDScript"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_basics.rst:216
msgid ""
"The C# API uses ``PascalCase`` instead of ``snake_case`` in GDScript/C++. "
"Where possible, fields and getters/setters have been converted to "
"properties. In general, the C# Godot API strives to be as idiomatic as is "
"reasonably possible."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_basics.rst:220
msgid "For more information, see the :ref:`doc_c_sharp_differences` page."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_basics.rst:224
msgid ""
"You need to (re)build the project assemblies whenever you want to see new "
"exported variables or signals in the editor. This build can be manually "
"triggered by clicking the **Build** button in the top right corner of the "
"editor."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_basics.rst:231
msgid ""
"You will also need to rebuild the project assemblies to apply changes in "
"\"tool\" scripts."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_basics.rst:235
msgid "Current gotchas and known issues"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_basics.rst:237
msgid ""
"As C# support is quite new in Godot, there are some growing pains and things "
"that need to be ironed out. Below is a list of the most important issues you "
"should be aware of when diving into C# in Godot, but if in doubt, also take "
"a look over the official `issue tracker for .NET issues <https://github.com/"
"godotengine/godot/labels/topic%3Adotnet>`_."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_basics.rst:243
msgid ""
"Writing editor plugins is possible, but it is currently quite convoluted."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_basics.rst:244
msgid ""
"State is currently not saved and restored when hot-reloading, with the "
"exception of exported variables."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_basics.rst:246
msgid ""
"Attached C# scripts should refer to a class that has a class name that "
"matches the file name."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_basics.rst:248
msgid ""
"There are some methods such as ``Get()``/``Set()``, ``Call()``/"
"``CallDeferred()`` and signal connection method ``Connect()`` that rely on "
"Godot's ``snake_case`` API naming conventions. So when using e.g. "
"``CallDeferred(\"AddChild\")``, ``AddChild`` will not work because the API "
"is expecting the original ``snake_case`` version ``add_child``. However, you "
"can use any custom properties or methods without this limitation. Prefer "
"using the exposed ``StringName`` in the ``PropertyName``, ``MethodName`` and "
"``SignalName`` to avoid extra ``StringName`` allocations and worrying about "
"snake_case naming."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_basics.rst:258
msgid ""
"As of Godot 4.0, exporting .NET projects is supported for desktop platforms "
"(Linux, Windows and macOS). Other platforms will gain support in future 4.x "
"releases."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_basics.rst:263
#, fuzzy
msgid "Common pitfalls"
msgstr "Zajednica"

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_basics.rst:265
msgid ""
"You might encounter the following error when trying to modify some values in "
"Godot objects, e.g. when trying to change the X coordinate of a ``Node2D``:"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_basics.rst:281
msgid ""
"This is perfectly normal. Structs (in this example, a ``Vector2``) in C# are "
"copied on assignment, meaning that when you retrieve such an object from a "
"property or an indexer, you get a copy of it, not the object itself. "
"Modifying said copy without reassigning it afterwards won't achieve anything."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_basics.rst:286
msgid ""
"The workaround is simple: retrieve the entire struct, modify the value you "
"want to modify, and reassign the property."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_basics.rst:295
msgid ""
"Since C# 10, it is also possible to use `with expressions <https://learn."
"microsoft.com/en-us/dotnet/csharp/language-reference/operators/with-"
"expression>`_ on structs, allowing you to do the same thing in a single line."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_basics.rst:302
msgid ""
"You can read more about this error on the `C# language reference <https://"
"learn.microsoft.com/en-us/dotnet/csharp/language-reference/compiler-messages/"
"cs1612>`_."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_basics.rst:305
msgid "Performance of C# in Godot"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_basics.rst:307
msgid ""
"According to some preliminary `benchmarks <https://github.com/cart/godot3-"
"bunnymark>`_, the performance of C# in Godot — while generally in the same "
"order of magnitude — is roughly **~4×** that of GDScript in some naive "
"cases. C++ is still a little faster; the specifics are going to vary "
"according to your use case. GDScript is likely fast enough for most general "
"scripting workloads."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_basics.rst:313
msgid ""
"Most properties of Godot C# objects that are based on ``GodotObject`` (e.g. "
"any ``Node`` like ``Control`` or ``Node3D`` like ``Camera3D``) require "
"native (interop) calls as they talk to Godot's C++ core. Consider assigning "
"values of such properties into a local variable if you need to modify or "
"read them multiple times at a single code location:"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_basics.rst:349
msgid ""
"Passing raw arrays (such as ``byte[]``) or ``string`` to Godot's C# API "
"requires marshalling which is comparatively pricey."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_basics.rst:352
msgid ""
"The implicit conversion from ``string`` to ``NodePath`` or ``StringName`` "
"incur both the native interop and marshalling costs as the ``string`` has to "
"be marshalled and passed to the respective native constructor."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_basics.rst:356
msgid "Using NuGet packages in Godot"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_basics.rst:358
msgid ""
"`NuGet <https://www.nuget.org/>`_ packages can be installed and used with "
"Godot, as with any C# project. Many IDEs are able to add packages directly. "
"They can also be added manually by adding the package reference in the ``."
"csproj`` file located in the project root:"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_basics.rst:372
msgid ""
"As of Godot 3.2.3, Godot automatically downloads and sets up newly added "
"NuGet packages the next time it builds the project."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_basics.rst:376
msgid "Profiling your C# code"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_basics.rst:378
msgid ""
"The following tools may be used for performance and memory profiling of your "
"managed code:"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_basics.rst:380
msgid "JetBrains Rider with dotTrace/dotMemory plugin."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_basics.rst:381
msgid "Standalone JetBrains dotTrace/dotMemory."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_basics.rst:382
#, fuzzy
msgid "Visual Studio."
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_basics.rst:384
msgid ""
"Profiling managed and unmanaged code at once is possible with both JetBrains "
"tools and Visual Studio, but limited to Windows."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_features.rst:4
#, fuzzy
msgid "C# language features"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_features.rst:6
msgid ""
"This page provides an overview of the commonly used features of both C# and "
"Godot and how they are used together."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_features.rst:12
msgid "Type conversion and casting"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_features.rst:14
msgid ""
"C# is a statically typed language. Therefore, you can't do the following:"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_features.rst:21
msgid ""
"The method ``GetNode()`` returns a ``Node`` instance. You must explicitly "
"convert it to the desired derived type, ``Sprite2D`` in this case."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_features.rst:24
msgid "For this, you have various options in C#."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_features.rst:26
msgid "**Casting and Type Checking**"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_features.rst:28
msgid ""
"Throws ``InvalidCastException`` if the returned node cannot be cast to "
"Sprite2D. You would use it instead of the ``as`` operator if you are pretty "
"sure it won't fail."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_features.rst:36
msgid "**Using the AS operator**"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_features.rst:38
msgid ""
"The ``as`` operator returns ``null`` if the node cannot be cast to Sprite2D, "
"and for that reason, it cannot be used with value types."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_features.rst:47
msgid "**Using the generic methods**"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_features.rst:49
msgid ""
"Generic methods are also provided to make this type conversion transparent."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_features.rst:51
msgid ""
"``GetNode<T>()`` casts the node before returning it. It will throw an "
"``InvalidCastException`` if the node cannot be cast to the desired type."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_features.rst:58
msgid ""
"``GetNodeOrNull<T>()`` uses the ``as`` operator and will return ``null`` if "
"the node cannot be cast to the desired type."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_features.rst:66
msgid "**Type checking using the IS operator**"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_features.rst:68
msgid ""
"To check if the node can be cast to Sprite2D, you can use the ``is`` "
"operator. The ``is`` operator returns false if the node cannot be cast to "
"Sprite2D, otherwise it returns true. Note that when the ``is`` operator is "
"used against ``null`` the result is always going to be ``false``."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_features.rst:85
msgid ""
"You can also declare a new variable to conditionally store the result of the "
"cast if the ``is`` operator returns ``true``."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_features.rst:96
msgid ""
"For more advanced type checking, you can look into `Pattern Matching "
"<https://docs.microsoft.com/en-us/dotnet/csharp/pattern-matching>`_."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_features.rst:100
msgid "Preprocessor defines"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_features.rst:102
msgid ""
"Godot has a set of defines that allow you to change your C# code depending "
"on the environment you are compiling to."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_features.rst:105
msgid ""
"If you created your project before Godot 3.2, you have to modify or "
"regenerate your `csproj` file to use this feature (compare "
"``<DefineConstants>`` with a new 3.2+ project)."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_features.rst:112
msgid "For example, you can change code based on the platform:"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_features.rst:129
msgid ""
"Or you can detect which engine your code is in, useful for making cross-"
"engine libraries:"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_features.rst:144
msgid ""
"Or you can write scripts that target multiple Godot versions and take "
"advantage of features that are only available on some of those versions:"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_features.rst:159
msgid "Full list of defines"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_features.rst:161
msgid "``GODOT`` is always defined for Godot projects."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_features.rst:163
msgid ""
"``TOOLS`` is defined when building with the Debug configuration (editor and "
"editor player)."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_features.rst:165
msgid ""
"``GODOT_REAL_T_IS_DOUBLE`` is defined when the ``GodotFloat64`` property is "
"set to ``true``."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_features.rst:167
msgid ""
"One of ``GODOT_64`` or ``GODOT_32`` is defined depending on if the "
"architecture is 64-bit or 32-bit."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_features.rst:169
msgid ""
"One of ``GODOT_LINUXBSD``, ``GODOT_WINDOWS``, ``GODOT_OSX``, "
"``GODOT_ANDROID``, ``GODOT_IOS``, ``GODOT_HTML5``, or ``GODOT_SERVER`` "
"depending on the OS. These names may change in the future. These are created "
"from the ``get_name()`` method of the :ref:`OS <class_OS>` singleton, but "
"not every possible OS the method returns is an OS that Godot with .NET runs "
"on."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_features.rst:176
msgid ""
"``GODOTX``, ``GODOTX_Y``, ``GODOTX_Y_Z``, ``GODOTx_OR_GREATER``, "
"``GODOTX_y_OR_GREATER``, and ``GODOTX_Y_z_OR_GREATER``, where ``X``, ``Y``, "
"and ``Z`` are replaced by the current major, minor and patch version of "
"Godot. ``x``, ``y``, and ``z`` are replaced by all values from 0 to the "
"current version number for that component."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_features.rst:184
msgid ""
"These defines were first added in Godot 4.0.4 and 4.1. Version defines for "
"prior versions do not exist, regardless of the current Godot version."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_features.rst:187
msgid ""
"For example: Godot 4.0.5 defines ``GODOT4``, ``GODOT4_OR_GREATER``, "
"``GODOT4_0``, ``GODOT4_0_OR_GREATER``, ``GODOT4_0_5``, "
"``GODOT4_0_4_OR_GREATER``, and ``GODOT4_0_5_OR_GREATER``. Godot 4.3.2 "
"defines ``GODOT4``, ``GODOT4_OR_GREATER``, ``GODOT4_3``, "
"``GODOT4_0_OR_GREATER``, ``GODOT4_1_OR_GREATER``, ``GODOT4_2_OR_GREATER``, "
"``GODOT4_3_OR_GREATER``, ``GODOT4_3_2``, ``GODOT4_3_0_OR_GREATER``, "
"``GODOT4_3_1_OR_GREATER``, and ``GODOT4_3_2_OR_GREATER``."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_features.rst:195
msgid ""
"When **exporting**, the following may also be defined depending on the "
"export features:"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_features.rst:197
msgid ""
"One of ``GODOT_PC``, ``GODOT_MOBILE``, or ``GODOT_WEB`` depending on the "
"platform type."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_features.rst:199
msgid ""
"One of ``GODOT_WINDOWS``, ``GODOT_LINUXBSD``, ``GODOT_MACOS``, "
"``GODOT_ANDROID``, ``GODOT_IOS``, or ``GODOT_WEB`` depending on the platform."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_features.rst:201
#, fuzzy
msgid ""
"To see an example project, see the OS testing demo: https://github.com/"
"godotengine/godot-demo-projects/tree/master/misc/os_test"
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati različite Godo demo projekte "
"`Godot demo projects <https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:4
msgid "C# API differences to GDScript"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:6
msgid "This is a (incomplete) list of API differences between C# and GDScript."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:9
msgid "General differences"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:11
msgid ""
"As explained in the :ref:`doc_c_sharp`, C# generally uses ``PascalCase`` "
"instead of the ``snake_case`` used in GDScript and C++."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:17
msgid ""
"Global functions and some constants had to be moved to classes, since C# "
"does not allow declaring them in namespaces. Most global constants were "
"moved to their own enums."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:24
msgid ""
"In C#, only primitive types can be constant. For example, the ``TAU`` "
"constant is replaced by the ``Mathf.Tau`` constant, but the ``Vector2."
"RIGHT`` constant is replaced by the ``Vector2.Right`` read-only property. "
"This behaves similarly to a constant, but can't be used in some contexts "
"like ``switch`` statements."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:29
msgid ""
"Global enum constants were moved to their own enums. For example, ``ERR_*`` "
"constants were moved to the ``Error`` enum."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:32
msgid "Special cases:"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:37
msgid "``TYPE_*``"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:37
msgid "``Variant.Type`` enum"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:38
msgid "``OP_*``"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:38
msgid "``Variant.Operator`` enum"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:42
msgid "Math functions"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:44
msgid ""
"Math global functions, like ``abs``, ``acos``, ``asin``, ``atan`` and "
"``atan2``, are located under ``Mathf`` as ``Abs``, ``Acos``, ``Asin``, "
"``Atan`` and ``Atan2``. The ``PI`` constant can be found as ``Mathf.Pi``."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:48
msgid ""
"C# also provides static `System.Math`_ and `System.MathF`_ classes that may "
"contain other useful mathematical operations."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:55
msgid "Random functions"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:57
msgid ""
"Random global functions, like ``rand_range`` and ``rand_seed``, are located "
"under ``GD``. Example: ``GD.RandRange`` and ``GD.RandSeed``."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:60
msgid ""
"Consider using `System.Random`_ or, if you need cryptographically strong "
"randomness, `System.Security.Cryptography.RandomNumberGenerator`_."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:67
msgid "Other functions"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:69
msgid ""
"Many other global functions like ``print`` and ``var_to_str`` are located "
"under ``GD``. Example: ``GD.Print`` and ``GD.VarToStr``."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:72
msgid "Exceptions:"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:77
msgid "``weakref(obj)``"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:77
msgid "``GodotObject.WeakRef(obj)``"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:78
msgid "``instance_from_id(id)``"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:78
msgid "``GodotObject.InstanceFromId(id)``"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:79
msgid "``is_instance_id_valid(id)``"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:79
msgid "``GodotObject.IsInstanceIdValid(id)``"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:80
msgid "``is_instance_valid(obj)``"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:80
msgid "``GodotObject.IsInstanceValid(obj)``"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:84
msgid "Tips"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:86
msgid ""
"Sometimes it can be useful to use the ``using static`` directive. This "
"directive allows to access the members and nested types of a class without "
"specifying the class name."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:104
msgid "Full list of equivalences"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:106
msgid "List of Godot's global scope functions and their equivalent in C#:"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:111
msgid "abs"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:111
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:112
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:113
msgid "Mathf.Abs"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:112
msgid "absf"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:113
msgid "absi"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:114
msgid "acos"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:114
msgid "Mathf.Acos"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:115
msgid "acosh"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:115
msgid "Mathf.Acosh"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:116
msgid "angle_difference"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:116
msgid "Mathf.AngleDifference"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:117
msgid "asin"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:117
msgid "Mathf.Asin"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:118
msgid "asinh"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:118
msgid "Mathf.Asinh"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:119
msgid "atan"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:119
msgid "Mathf.Atan"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:120
msgid "atan2"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:120
msgid "Mathf.Atan2"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:121
msgid "atanh"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:121
msgid "Mathf.Atanh"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:122
msgid "bezier_derivative"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:122
msgid "Mathf.BezierDerivative"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:123
#, fuzzy
msgid "bezier_interpolate"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:123
msgid "Mathf.BezierInterpolate"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:124
msgid "bytes_to_var"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:124
msgid "GD.BytesToVar"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:125
msgid "bytes_to_var_with_objects"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:125
msgid "GD.BytesToVarWithObjects"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:126
msgid "ceil"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:126
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:127
msgid "Mathf.Ceil"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:127
msgid "ceilf"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:128
msgid "ceili"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:128
msgid "Mathf.CeilToInt"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:129
msgid "clamp"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:129
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:130
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:131
msgid "Mathf.Clamp"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:130
msgid "clampf"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:131
msgid "clampi"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:132
msgid "cos"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:132
msgid "Mathf.Cos"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:133
msgid "cosh"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:133
msgid "Mathf.Cosh"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:134
msgid "cubic_interpolate"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:134
#, fuzzy
msgid "Mathf.CubicInterpolate"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:135
#, fuzzy
msgid "cubic_interpolate_angle"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:135
msgid "Mathf.CubicInterpolateAngle"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:136
msgid "cubic_interpolate_angle_in_time"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:136
msgid "Mathf.CubicInterpolateInTime"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:137
msgid "cubic_interpolate_in_time"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:137
msgid "Mathf.CubicInterpolateAngleInTime"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:138
msgid "db_to_linear"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:138
msgid "Mathf.DbToLinear"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:139
msgid "deg_to_rad"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:139
msgid "Mathf.DegToRad"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:140
msgid "ease"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:140
msgid "Mathf.Ease"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:141
msgid "error_string"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:141
msgid "Error.ToString"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:142
msgid "exp"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:142
msgid "Mathf.Exp"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:143
msgid "floor"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:143
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:144
msgid "Mathf.Floor"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:144
msgid "floorf"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:145
msgid "floori"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:145
msgid "Mathf.FloorToInt"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:146
msgid "fmod"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:146
msgid "operator %"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:147
msgid "fposmod"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:147
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:173
msgid "Mathf.PosMod"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:148
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:400
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:140
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:225
msgid "hash"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:148
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:140
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:225
msgid "GD.Hash"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:149
msgid "instance_from_id"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:149
msgid "GodotObject.InstanceFromId"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:150
msgid "inverse_lerp"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:150
msgid "Mathf.InverseLerp"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:151
msgid "is_equal_approx"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:151
msgid "Mathf.IsEqualApprox"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:152
msgid "is_finite"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:152
msgid "Mathf.IsFinite or `float.IsFinite`_ or `double.IsFinite`_"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:153
msgid "is_inf"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:153
msgid "Mathf.IsInf or `float.IsInfinity`_ or `double.IsInfinity`_"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:154
msgid "is_instance_id_valid"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:154
msgid "GodotObject.IsInstanceIdValid"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:155
msgid "is_instance_valid"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:155
msgid "GodotObject.IsInstanceValid"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:156
msgid "is_nan"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:156
msgid "Mathf.IsNaN or `float.IsNaN`_ or `double.IsNaN`_"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:157
msgid "is_same"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:157
msgid "operator == or `object.ReferenceEquals`_"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:158
msgid "is_zero_approx"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:158
msgid "Mathf.IsZeroApprox"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:159
msgid "lerp"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:159
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:161
msgid "Mathf.Lerp"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:160
msgid "lerp_angle"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:160
msgid "Mathf.LerpAngle"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:161
msgid "lerpf"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:162
msgid "linear_to_db"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:162
msgid "Mathf.LinearToDb"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:163
msgid "log"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:163
msgid "Mathf.Log"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:164
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:165
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:166
msgid "Mathf.Max"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:165
msgid "maxf"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:166
msgid "maxi"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:167
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:168
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:169
msgid "Mathf.Min"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:168
msgid "minf"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:169
msgid "mini"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:170
msgid "move_toward"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:170
msgid "Mathf.MoveToward"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:171
msgid "nearest_po2"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:171
msgid "Mathf.NearestPo2"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:172
msgid "pingpong"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:172
msgid "Mathf.PingPong"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:173
msgid "posmod"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:174
msgid "pow"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:174
msgid "Mathf.Pow"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:175
msgid "print"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:175
msgid "GD.Print"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:176
msgid "print_rich"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:176
msgid "GD.PrintRich"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:177
msgid "print_verbose"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:177
msgid "Use OS.IsStdoutVerbose and GD.Print"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:178
msgid "printerr"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:178
msgid "GD.PrintErr"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:179
msgid "printraw"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:179
msgid "GD.PrintRaw"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:180
msgid "prints"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:180
msgid "GD.PrintS"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:181
msgid "printt"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:181
msgid "GD.PrintT"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:182
msgid "push_error"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:182
msgid "GD.PushError"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:183
msgid "push_warning"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:183
msgid "GD.PushWarning"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:184
msgid "rad_to_deg"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:184
msgid "Mathf.RadToDeg"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:185
msgid "rand_from_seed"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:185
msgid "GD.RandFromSeed"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:186
msgid "randf"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:186
msgid "GD.Randf"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:187
msgid "randf_range"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:187
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:190
msgid "GD.RandRange"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:188
msgid "randfn"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:188
msgid "GD.Randfn"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:189
msgid "randi"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:189
msgid "GD.Randi"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:190
msgid "randi_range"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:191
msgid "randomize"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:191
msgid "GD.Randomize"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:192
msgid "remap"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:192
msgid "Mathf.Remap"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:193
msgid "rid_allocate_id"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:193
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:194
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:244
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:246
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:247
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:249
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:250
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:383
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:397
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:398
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:399
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:403
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:440
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:445
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:127
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:136
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:137
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:138
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:144
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:145
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:168
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:169
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:171
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:172
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:221
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:224
msgid "N/A"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:194
msgid "rid_from_int64"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:195
msgid "rotate_toward"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:195
msgid "Mathf.RotateToward"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:196
msgid "round"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:196
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:197
msgid "Mathf.Round"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:197
msgid "roundf"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:198
msgid "roundi"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:198
msgid "Mathf.RoundToInt"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:199
msgid "seed"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:199
msgid "GD.Seed"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:200
msgid "sign"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:200
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:201
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:202
msgid "Mathf.Sign"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:201
msgid "signf"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:202
msgid "signi"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:203
msgid "sin"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:203
msgid "Mathf.Sin"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:204
msgid "sinh"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:204
msgid "Mathf.Sinh"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:205
msgid "smoothstep"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:205
msgid "Mathf.SmoothStep"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:206
msgid "snapped"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:206
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:207
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:208
msgid "Mathf.Snapped"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:207
msgid "snappedf"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:208
msgid "snappedi"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:209
msgid "sqrt"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:209
msgid "Mathf.Sqrt"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:210
msgid "step_decimals"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:210
msgid "Mathf.StepDecimals"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:211
msgid "str"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:211
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:392
#, fuzzy
msgid "Use `$ string interpolation`_"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:212
msgid "str_to_var"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:212
msgid "GD.StrToVar"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:213
msgid "tan"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:213
msgid "Mathf.Tan"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:214
msgid "tanh"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:214
msgid "Mathf.Tanh"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:215
msgid "type_convert"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:215
msgid "Variant.As<T> or GD.Convert"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:216
msgid "type_string"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:216
msgid "Variant.Type.ToString"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:217
msgid "typeof"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:217
msgid "Variant.VariantType"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:218
msgid "var_to_bytes"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:218
msgid "GD.VarToBytes"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:219
msgid "var_to_bytes_with_objects"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:219
msgid "GD.VarToBytesWithObjects"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:220
msgid "var_to_str"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:220
msgid "GD.VarToStr"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:221
msgid "weakref"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:221
msgid "GodotObject.WeakRef"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:222
msgid "wrap"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:222
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:223
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:224
msgid "Mathf.Wrap"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:223
msgid "wrapf"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:224
msgid "wrapi"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:236
msgid "List of GDScript utility functions and their equivalent in C#:"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:241
msgid "`System.Diagnostics.Debug.Assert`_"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:242
msgid "char"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:242
msgid "Use explicit conversion: ``(char)65``"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:243
msgid "convert"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:243
msgid "GD.Convert"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:244
msgid "dict_to_inst"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:245
msgid "get_stack"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:245
msgid "`System.Environment.StackTrace`_"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:246
msgid "inst_to_dict"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:247
msgid "len"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:248
msgid "load"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:248
msgid "GD.Load"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:250
msgid "print_debug"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:251
msgid "print_stack"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:251
msgid "GD.Print(`System.Environment.StackTrace`_)"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:252
msgid "range"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:252
msgid "GD.Range or `System.Linq.Enumerable.Range`_"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:253
msgid "type_exists"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:253
msgid "ClassDB.ClassExists(type)"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:260
msgid ""
"``preload``, as it works in GDScript, is not available in C#. Use ``GD."
"Load`` or ``ResourceLoader.Load`` instead."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:264
msgid "``@export`` annotation"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:266
msgid ""
"Use the ``[Export]`` attribute instead of the GDScript ``@export`` "
"annotation. This attribute can also be provided with optional :ref:"
"`PropertyHint<enum_@GlobalScope_PropertyHint>` and ``hintString`` "
"parameters. Default values can be set by assigning a value."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:291
msgid "See also: :ref:`doc_c_sharp_exports`."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:294
msgid "``signal`` keyword"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:296
msgid ""
"Use the ``[Signal]`` attribute to declare a signal instead of the GDScript "
"``signal`` keyword. This attribute should be used on a `delegate`, whose "
"name signature will be used to define the signal. The `delegate` must have "
"the ``EventHandler`` suffix, an `event` will be generated in the class with "
"the same name but without the suffix, use that event's name with "
"``EmitSignal``."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:305
msgid "See also: :ref:`doc_c_sharp_signals`."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:308
msgid "`@onready` annotation"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:310
msgid ""
"GDScript has the ability to defer the initialization of a member variable "
"until the ready function is called with `@onready` (cf. :ref:"
"`doc_gdscript_onready_annotation`). For example:"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:318
msgid ""
"However C# does not have this ability. To achieve the same effect you need "
"to do this."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:330
msgid "Singletons"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:332
msgid ""
"Singletons are available as static classes rather than using the singleton "
"pattern. This is to make code less verbose than it would be with an "
"``Instance`` property."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:341
msgid ""
"However, in some very rare cases this is not enough. For example, you may "
"want to access a member from the base class ``GodotObject``, like "
"``Connect``. For such use cases we provide a static property named "
"``Singleton`` that returns the singleton instance. The type of this instance "
"is ``GodotObject``."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:355
msgid ""
"Use ``System.String`` (``string``). Most of Godot's String methods have an "
"equivalent in ``System.String`` or are provided by the ``StringExtensions`` "
"class as extension methods."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:366
msgid ""
"Strings are immutable in .NET, so all methods that manipulate a string don't "
"modify the original string and return a newly created string with the "
"modifications applied. To avoid creating multiple string allocations "
"consider using a `StringBuilder`_."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:371
msgid "List of Godot's String methods and their equivalent in C#:"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:376
msgid "begins_with"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:376
msgid "`string.StartsWith`_"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:377
msgid "bigrams"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:377
msgid "StringExtensions.Bigrams"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:378
msgid "bin_to_int"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:378
msgid "StringExtensions.BinToInt"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:379
msgid "c_escape"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:379
msgid "StringExtensions.CEscape"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:380
msgid "c_unescape"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:380
msgid "StringExtensions.CUnescape"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:381
msgid "capitalize"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:381
msgid "StringExtensions.Capitalize"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:382
msgid "casecmp_to"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:382
msgid ""
"StringExtensions.CasecmpTo or StringExtensions.CompareTo (Consider using "
"`string.Equals`_ or `string.Compare`_)"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:384
msgid "contains"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:384
#, fuzzy
msgid "`string.Contains`_"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:385
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:129
msgid "count"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:385
msgid "StringExtensions.Count (Consider using `RegEx`_)"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:386
msgid "countn"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:386
msgid "StringExtensions.CountN (Consider using `RegEx`_)"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:387
msgid "dedent"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:387
msgid "StringExtensions.Dedent"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:388
msgid "ends_with"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:388
msgid "`string.EndsWith`_"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:389
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:131
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:220
msgid "erase"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:389
msgid ""
"`string.Remove`_ (Consider using `StringBuilder`_ to manipulate strings)"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:390
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:134
msgid "find"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:390
msgid ""
"StringExtensions.Find (Consider using `string.IndexOf`_ or `string."
"IndexOfAny`_)"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:391
msgid "findn"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:391
msgid ""
"StringExtensions.FindN (Consider using `string.IndexOf`_ or `string."
"IndexOfAny`_)"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:392
msgid "format"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:393
msgid "get_base_dir"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:393
msgid "StringExtensions.GetBaseDir"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:394
msgid "get_basename"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:394
msgid "StringExtensions.GetBaseName"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:395
msgid "get_extension"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:395
msgid "StringExtensions.GetExtension"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:396
msgid "get_file"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:396
msgid "StringExtensions.GetFile"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:397
msgid "get_slice"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:398
msgid "get_slice_count"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:399
msgid "get_slicec"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:400
msgid ""
"StringExtensions.Hash (Consider using `object.GetHashCode`_ unless you need "
"to guarantee the same behavior as in GDScript)"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:401
msgid "hex_decode"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:401
msgid ""
"StringExtensions.HexDecode (Consider using `System.Convert.FromHexString`_)"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:402
msgid "hex_to_int"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:402
msgid ""
"StringExtensions.HexToInt (Consider using `int.Parse`_ or `long.Parse`_ with "
"`System.Globalization.NumberStyles.HexNumber`_)"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:403
msgid "humanize_size"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:404
msgid "indent"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:404
msgid "StringExtensions.Indent"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:405
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:141
#, fuzzy
msgid "insert"
msgstr "Unesi Ključ"

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:405
msgid ""
"`string.Insert`_ (Consider using `StringBuilder`_ to manipulate strings)"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:406
msgid "is_absolute_path"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:406
msgid "StringExtensions.IsAbsolutePath"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:407
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:142
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:226
msgid "is_empty"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:407
msgid "`string.IsNullOrEmpty`_ or `string.IsNullOrWhiteSpace`_"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:408
msgid "is_relative_path"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:408
msgid "StringExtensions.IsRelativePath"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:409
msgid "is_subsequence_of"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:409
msgid "StringExtensions.IsSubsequenceOf"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:410
msgid "is_subsequence_ofn"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:410
msgid "StringExtensions.IsSubsequenceOfN"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:411
msgid "is_valid_filename"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:411
msgid "StringExtensions.IsValidFileName"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:412
msgid "is_valid_float"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:412
msgid ""
"StringExtensions.IsValidFloat (Consider using `float.TryParse`_ or `double."
"TryParse`_)"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:413
msgid "is_valid_hex_number"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:413
msgid "StringExtensions.IsValidHexNumber"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:414
msgid "is_valid_html_color"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:414
msgid "StringExtensions.IsValidHtmlColor"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:415
msgid "is_valid_identifier"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:415
msgid "StringExtensions.IsValidIdentifier"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:416
msgid "is_valid_int"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:416
msgid ""
"StringExtensions.IsValidInt (Consider using `int.TryParse`_ or `long."
"TryParse`_)"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:417
msgid "is_valid_ip_address"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:417
msgid "StringExtensions.IsValidIPAddress"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:418
msgid "join"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:418
msgid "`string.Join`_"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:419
msgid "json_escape"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:419
msgid "StringExtensions.JSONEscape"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:420
msgid "left"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:420
msgid ""
"StringExtensions.Left (Consider using `string.Substring`_ or `string."
"AsSpan`_)"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:421
msgid "length"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:421
msgid "`string.Length`_"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:422
msgid "lpad"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:422
msgid "`string.PadLeft`_"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:423
msgid "lstrip"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:423
msgid "`string.TrimStart`_"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:424
msgid "StringExtensions.Match (Consider using `RegEx`_)"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:425
msgid "matchn"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:425
msgid "StringExtensions.MatchN (Consider using `RegEx`_)"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:426
msgid "md5_buffer"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:426
msgid ""
"StringExtensions.Md5Buffer (Consider using `System.Security.Cryptography.MD5."
"HashData`_)"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:427
msgid "md5_text"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:427
msgid ""
"StringExtensions.Md5Text (Consider using `System.Security.Cryptography.MD5."
"HashData`_ with StringExtensions.HexEncode)"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:428
msgid "naturalnocasecmp_to"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:428
msgid "N/A (Consider using `string.Equals`_ or `string.Compare`_)"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:429
msgid "nocasecmp_to"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:429
msgid ""
"StringExtensions.NocasecmpTo or StringExtensions.CompareTo (Consider using "
"`string.Equals`_ or `string.Compare`_)"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:430
msgid "num"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:430
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:432
msgid "`float.ToString`_ or `double.ToString`_"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:431
msgid "num_int64"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:431
msgid "`int.ToString`_ or `long.ToString`_"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:432
msgid "num_scientific"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:433
msgid "num_uint64"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:433
msgid "`uint.ToString`_ or `ulong.ToString`_"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:434
msgid "pad_decimals"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:434
msgid "StringExtensions.PadDecimals"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:435
msgid "pad_zeros"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:435
msgid "StringExtensions.PadZeros"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:436
msgid "path_join"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:436
msgid "StringExtensions.PathJoin"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:437
msgid "repeat"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:437
msgid "Use `string constructor`_ or a `StringBuilder`_"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:438
#, fuzzy
msgid "replace"
msgstr "Zameni"

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:438
msgid "`string.Replace`_ or `RegEx`_"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:439
#, fuzzy
msgid "replacen"
msgstr "Zameni"

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:439
msgid ""
"StringExtensions.ReplaceN (Consider using `string.Replace`_ or `RegEx`_)"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:440
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:159
msgid "reverse"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:441
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:160
msgid "rfind"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:441
msgid ""
"StringExtensions.RFind (Consider using `string.LastIndexOf`_ or `string."
"LastIndexOfAny`_)"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:442
msgid "rfindn"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:442
msgid ""
"StringExtensions.RFindN (Consider using `string.LastIndexOf`_ or `string."
"LastIndexOfAny`_)"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:443
msgid "right"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:443
msgid ""
"StringExtensions.Right (Consider using `string.Substring`_ or `string."
"AsSpan`_)"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:444
msgid "rpad"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:444
msgid "`string.PadRight`_"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:445
msgid "rsplit"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:446
msgid "rstrip"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:446
msgid "`string.TrimEnd`_"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:447
msgid "sha1_buffer"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:447
msgid ""
"StringExtensions.Sha1Buffer (Consider using `System.Security.Cryptography."
"SHA1.HashData`_)"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:448
msgid "sha1_text"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:448
msgid ""
"StringExtensions.Sha1Text (Consider using `System.Security.Cryptography.SHA1."
"HashData`_ with StringExtensions.HexEncode)"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:449
msgid "sha256_buffer"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:449
msgid ""
"StringExtensions.Sha256Buffer (Consider using `System.Security.Cryptography."
"SHA256.HashData`_)"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:450
msgid "sha256_text"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:450
msgid ""
"StringExtensions.Sha256Text (Consider using `System.Security.Cryptography."
"SHA256.HashData`_ with StringExtensions.HexEncode)"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:451
msgid "similarity"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:451
msgid "StringExtensions.Similarity"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:452
msgid "simplify_path"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:452
msgid "StringExtensions.SimplifyPath"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:453
msgid "split"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:453
msgid "StringExtensions.Split (Consider using `string.Split`_)"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:454
msgid "split_floats"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:454
msgid "StringExtensions.SplitFloat"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:455
msgid "strip_edges"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:455
msgid ""
"StringExtensions.StripEdges (Consider using `string.Trim`_, `string."
"TrimStart`_ or `string.TrimEnd`_)"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:456
msgid "strip_escapes"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:456
msgid "StringExtensions.StripEscapes"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:457
msgid "substr"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:457
msgid ""
"StringExtensions.Substr (Consider using `string.Substring`_ or `string."
"AsSpan`_)"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:458
msgid "to_ascii_buffer"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:458
msgid ""
"StringExtensions.ToAsciiBuffer (Consider using `System.Text.Encoding.ASCII."
"GetBytes`_)"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:459
msgid "to_camel_case"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:459
msgid "StringExtensions.ToCamelCase"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:460
msgid "to_float"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:460
msgid ""
"StringExtensions.ToFloat (Consider using `float.TryParse`_ or `double."
"TryParse`_)"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:461
msgid "to_int"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:461
msgid ""
"StringExtensions.ToInt (Consider using `int.TryParse`_ or `long.TryParse`_)"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:462
msgid "to_lower"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:462
msgid "`string.ToLower`_"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:463
msgid "to_pascal_case"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:463
msgid "StringExtensions.ToPascalCase"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:464
msgid "to_snake_case"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:464
msgid "StringExtensions.ToSnakeCase"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:465
msgid "to_upper"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:465
msgid "`string.ToUpper`_"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:466
msgid "to_utf16_buffer"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:466
msgid ""
"StringExtensions.ToUtf16Buffer (Consider using `System.Text.Encoding.UTF16."
"GetBytes`_)"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:467
msgid "to_utf32_buffer"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:467
msgid ""
"StringExtensions.ToUtf32Buffer (Consider using `System.Text.Encoding.UTF32."
"GetBytes`_)"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:468
msgid "to_utf8_buffer"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:468
msgid ""
"StringExtensions.ToUtf8Buffer (Consider using `System.Text.Encoding.UTF8."
"GetBytes`_)"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:469
msgid "to_wchar_buffer"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:469
msgid ""
"StringExtensions.ToUtf16Buffer in Windows and StringExtensions.ToUtf32Buffer "
"in other platforms"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:470
msgid "trim_prefix"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:470
msgid "StringExtensions.TrimPrefix"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:471
msgid "trim_suffix"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:471
msgid "StringExtensions.TrimSuffix"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:472
msgid "unicode_at"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:472
msgid "`string[int]`_ indexer"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:473
msgid "uri_decode"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:473
msgid ""
"StringExtensions.URIDecode (Consider using `System.Uri.UnescapeDataString`_)"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:474
#, fuzzy
msgid "uri_encode"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:474
msgid ""
"StringExtensions.URIEncode (Consider using `System.Uri.EscapeDataString`_)"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:475
msgid "validate_node_name"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:475
msgid "StringExtensions.ValidateNodeName"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:476
msgid "xml_escape"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:476
msgid "StringExtensions.XMLEscape"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:477
msgid "xml_unescape"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:477
msgid "StringExtensions.XMLUnescape"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:480
msgid ""
"List of Godot's PackedByteArray methods that create a String and their C# "
"equivalent:"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:485
msgid "get_string_from_ascii"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:485
msgid ""
"StringExtensions.GetStringFromAscii (Consider using `System.Text.Encoding."
"ASCII.GetString`_)"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:486
msgid "get_string_from_utf16"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:486
msgid ""
"StringExtensions.GetStringFromUtf16 (Consider using `System.Text.Encoding."
"UTF16.GetString`_)"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:487
msgid "get_string_from_utf32"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:487
msgid ""
"StringExtensions.GetStringFromUtf32 (Consider using `System.Text.Encoding."
"UTF32.GetString`_)"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:488
msgid "get_string_from_utf8"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:488
msgid ""
"StringExtensions.GetStringFromUtf8 (Consider using `System.Text.Encoding."
"UTF8.GetString`_)"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:489
msgid "hex_encode"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:489
msgid ""
"StringExtensions.HexEncode (Consider using `System.Convert.ToHexString`_)"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:492
msgid ""
".NET contains many path utility methods available under the `System.IO."
"Path`_ class that can be used when not dealing with Godot paths (paths that "
"start with ``res://`` or ``user://``)"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:560
#: ../../docs/contributing/development/core_and_modules/core_types.rst:214
#: ../../docs/contributing/development/file_formats/tscn.rst:167
msgid "NodePath"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:562
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:644
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:696
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:717
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:730
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:764
msgid "The following method was converted to a property with a different name:"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:567
msgid "``is_empty()``"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:567
msgid "``IsEmpty``"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:573
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:591
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:628
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:659
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:676
msgid ""
"The following methods were converted to properties with their respective "
"names changed:"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:578
msgid "``get_name()``"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:578
msgid "``Name``"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:579
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:596
msgid "``get_object()``"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:579
msgid "``Owner``"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:582
msgid ""
"The ``Signal`` type implements the awaitable pattern which means it can be "
"used with the ``await`` keyword. See :ref:`doc_c_sharp_differences_await`."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:585
msgid ""
"Instead of using the ``Signal`` type, the recommended way to use Godot "
"signals in C# is to use the generated C# events. See :ref:"
"`doc_c_sharp_signals`."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:589
msgid "Callable"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:596
msgid "``Target``"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:597
msgid "``get_method()``"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:597
msgid "``Method``"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:600
msgid "Currently C# supports ``Callable`` if one of the following holds:"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:602
msgid "``Callable`` was created using the C# ``Callable`` type."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:603
msgid ""
"``Callable`` is a basic version of the engine's ``Callable``. Custom "
"``Callable``\\ s are unsupported. A ``Callable`` is custom when any of the "
"following holds:"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:606
msgid ""
"``Callable`` has bound information (``Callable``\\ s created with ``bind``/"
"``unbind`` are unsupported)."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:607
msgid ""
"``Callable`` was created from other languages through the GDExtension API."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:609
msgid ""
"Some methods such as ``bind`` and ``unbind`` are not implemented, use "
"lambdas instead:"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:621
msgid ""
"The lambda captures the ``name`` variable so it can be bound to the "
"``SayHello`` method."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:624
#: ../../docs/contributing/development/core_and_modules/core_types.rst:225
msgid "RID"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:626
msgid "This type is named ``Rid`` in C# to follow the .NET naming convention."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:633
msgid "``get_id()``"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:633
msgid "``Id``"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:634
msgid "``is_valid()``"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:634
msgid "``IsValid``"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:638
msgid "Basis"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:640
msgid ""
"Structs cannot have parameterless constructors in C#. Therefore, ``new "
"Basis()`` initializes all primitive members to their default value. Use "
"``Basis.Identity`` for the equivalent of ``Basis()`` in GDScript and C++."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:649
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:665
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:682
msgid "``get_scale()``"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:649
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:665
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:682
msgid "``Scale``"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:653
msgid "Transform2D"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:655
msgid ""
"Structs cannot have parameterless constructors in C#. Therefore, ``new "
"Transform2D()`` initializes all primitive members to their default value. "
"Please use ``Transform2D.Identity`` for the equivalent of ``Transform2D()`` "
"in GDScript and C++."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:664
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:681
msgid "``get_rotation()``"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:664
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:681
msgid "``Rotation``"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:666
msgid "``get_skew()``"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:666
msgid "``Skew``"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:670
msgid "Transform3D"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:672
msgid ""
"Structs cannot have parameterless constructors in C#. Therefore, ``new "
"Transform3D()`` initializes all primitive members to their default value. "
"Please use ``Transform3D.Identity`` for the equivalent of ``Transform3D()`` "
"in GDScript and C++."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:686
msgid "Rect2"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:688
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:709
msgid ""
"The following field was converted to a property with a *slightly* different "
"name:"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:693
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:714
msgid "``end``"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:693
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:714
msgid "``End``"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:701
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:722
msgid "``get_area()``"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:701
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:722
msgid "``Area``"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:705
msgid "Rect2i"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:707
msgid ""
"This type is named ``Rect2I`` in C# to follow the .NET naming convention."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:726
msgid "AABB"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:728
msgid "This type is named ``Aabb`` in C# to follow the .NET naming convention."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:735
msgid "``get_volume()``"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:735
msgid "``Volume``"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:739
msgid "Quaternion"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:741
msgid ""
"Structs cannot have parameterless constructors in C#. Therefore, ``new "
"Quaternion()`` initializes all primitive members to their default value. "
"Please use ``Quaternion.Identity`` for the equivalent of ``Quaternion()`` in "
"GDScript and C++."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:746
#, fuzzy
msgid "Projection"
msgstr "Uvod"

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:748
msgid ""
"Structs cannot have parameterless constructors in C#. Therefore, ``new "
"Projection()`` initializes all primitive members to their default value. "
"Please use ``Projection.Identity`` for the equivalent of ``Projection()`` in "
"GDScript and C++."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:755
msgid ""
"Structs cannot have parameterless constructors in C#. Therefore, ``new "
"Color()`` initializes all primitive members to their default value (which "
"represents the transparent black color). Please use ``Colors.Black`` for the "
"equivalent of ``Color()`` in GDScript and C++."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:759
msgid ""
"The global ``Color8`` method to construct a Color from bytes is available as "
"a static method in the Color type."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:762
msgid ""
"The Color constants are available in the ``Colors`` static class as readonly "
"properties."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:769
msgid "``get_luminance()``"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:769
msgid "``Luminance``"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:772
msgid "The following method was converted to a method with a different name:"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:777
msgid "``html(String)``"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:777
msgid "``FromHtml(ReadOnlySpan<char>)``"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:780
msgid "The following methods are available as constructors:"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:785
msgid "``hex(int)``"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:785
msgid "``Color(uint)``"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:786
msgid "``hex64(int)``"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:786
msgid "``Color(ulong)``"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:792
msgid "The equivalent of packed arrays are ``System.Array``."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:794
msgid ""
"See also :ref:`PackedArray in C# <doc_c_sharp_collections_packedarray>`."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:796
msgid ""
"Use ``Godot.Collections.Array`` for an untyped ``Variant`` array. ``Godot."
"Collections.Array<T>`` is a type-safe wrapper around ``Godot.Collections."
"Array``."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:799
msgid "See also :ref:`Array in C# <doc_c_sharp_collections_array>`."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:804
msgid ""
"Use ``Godot.Collections.Dictionary`` for an untyped ``Variant`` dictionary. "
"``Godot.Collections.Dictionary<TKey, TValue>`` is a type-safe wrapper around "
"``Godot.Collections.Dictionary``."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:807
msgid "See also :ref:`Dictionary in C# <doc_c_sharp_collections_dictionary>`."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:810
msgid "Variant"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:812
msgid ""
"``Godot.Variant`` is used to represent Godot's native :ref:`Variant "
"<class_Variant>` type. Any Variant-compatible type can be converted from/to "
"it."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:815
msgid "See also: :ref:`doc_c_sharp_variant`."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:818
msgid "Communicating with other scripting languages"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:820
msgid "This is explained extensively in :ref:`doc_cross_language_scripting`."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:825
msgid "``await`` keyword"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:827
msgid ""
"Something similar to GDScript's ``await`` keyword can be achieved with C#'s "
"`await keyword <https://docs.microsoft.com/en-US/dotnet/csharp/language-"
"reference/keywords/await>`_."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:830
msgid ""
"The ``await`` keyword in C# can be used with any awaitable expression. It's "
"commonly used with operands of the types `Task`_, `Task<TResult>`_, "
"`ValueTask`_, or `ValueTask<TResult>`_."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:833
msgid "An expression ``t`` is awaitable if one of the following holds:"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:835
msgid "``t`` is of compile-time type ``dynamic``."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:836
msgid ""
"``t`` has an accessible instance or extension method called ``GetAwaiter`` "
"with no parameters and no type parameters, and a return type ``A`` for which "
"all of the following hold:"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:840
msgid ""
"``A`` implements the interface ``System.Runtime.CompilerServices."
"INotifyCompletion``."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:841
msgid ""
"``A`` has an accessible, readable instance property ``IsCompleted`` of type "
"``bool``."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:842
msgid ""
"``A`` has an accessible instance method ``GetResult`` with no parameters and "
"no type parameters."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_differences.rst:850
msgid ""
"An equivalent of awaiting a signal in GDScript can be achieved with the "
"``await`` keyword and ``GodotObject.ToSignal``."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:4
#, fuzzy
msgid "C# collections"
msgstr "Kopiraj Označeno"

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:6
msgid ""
"The .NET base class library contains multiple collection types that can be "
"used to store and manipulate data. Godot also provide some collection types "
"that are tightly integrated with the rest of the engine."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:11
#, fuzzy
msgid "Choose a collection"
msgstr "Kopiraj Označeno"

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:13
msgid ""
"The main difference between the `.NET collections <https://learn.microsoft."
"com/en-us/dotnet/standard/collections/>`_ and the Godot collections is that "
"the .NET collections are implemented in C# while the Godot collections are "
"implemented in C++ and the Godot C# API is a wrapper over it, this is an "
"important distinction since it means every operation on a Godot collection "
"requires marshaling which can be expensive especially inside a loop."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:19
msgid ""
"Due to the performance implications, using Godot collections is only "
"recommended when absolutely necessary (such as interacting with the Godot "
"API). Godot only understands its own collection types, so it's required to "
"use them when talking to the engine."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:24
msgid ""
"If you have a collection of elements that don't need to be passed to a Godot "
"API, using a .NET collection would be more performant."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:29
msgid ""
"It's also possible to convert between .NET collections and Godot "
"collections. The Godot collections contain constructors from generic .NET "
"collection interfaces that copy their elements, and the Godot collections "
"can be used with the `LINQ <https://learn.microsoft.com/en-us/dotnet/"
"standard/linq>`_ ``ToList``, ``ToArray`` and ``ToDictionary`` methods. But "
"keep in mind this conversion requires marshaling every element in the "
"collection and copies it to a new collection so it can be expensive."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:37
msgid ""
"Despite this, the Godot collections are optimized to try and avoid "
"unnecessary marshaling, so methods like ``Sort`` or ``Reverse`` are "
"implemented with a single interop call and don't need to marshal every "
"element. Keep an eye out for generic APIs that take collection interfaces "
"like `LINQ <https://learn.microsoft.com/en-us/dotnet/standard/linq>`_ "
"because every method requires iterating the collection and, therefore, "
"marshaling every element. Prefer using the instance methods of the Godot "
"collections when possible."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:44
msgid ""
"To choose which collection type to use for each situation, consider the "
"following questions:"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:46
msgid ""
"Does your collection need to interact with the Godot engine? (e.g.: the type "
"of an exported property, calling a Godot method)."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:49
msgid ""
"If yes, since Godot only supports :ref:`Variant-compatible "
"<doc_c_sharp_variant>` types, use a Godot collection."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:51
msgid ""
"If not, consider `choosing an appropriate .NET collection <https://learn."
"microsoft.com/en-us/dotnet/standard/collections/selecting-a-collection-"
"class>`_."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:53
msgid ""
"Do you need a Godot collection that represents a list or sequential set of "
"data?"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:55
msgid ""
"Godot :ref:`arrays <doc_c_sharp_collections_array>` are similar to the C# "
"collection ``List<T>``."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:56
msgid ""
"Godot :ref:`packed arrays <doc_c_sharp_collections_packedarray>` are more "
"memory-efficient arrays, in C# use one of the supported ``System.Array`` "
"types."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:59
msgid ""
"Do you need a Godot collection that maps a set of keys to a set of values?"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:61
msgid ""
"Godot :ref:`dictionaries <doc_c_sharp_collections_dictionary>` store pairs "
"of keys and values and allow easy access to the values by their associated "
"key."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:65
msgid "Godot collections"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:70
msgid "PackedArray"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:72
msgid ""
"Godot packed arrays are implemented as an array of a specific type, allowing "
"it to be more tightly packed as each element has the size of the specific "
"type, not ``Variant``."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:75
msgid "In C#, packed arrays are replaced by ``System.Array``:"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:80
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_variant.rst:68
msgid "``PackedInt32Array``"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:80
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_variant.rst:68
msgid "``int[]``"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:81
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_variant.rst:69
msgid "``PackedInt64Array``"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:81
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_variant.rst:69
msgid "``long[]``"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:82
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_variant.rst:67
msgid "``PackedByteArray``"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:82
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_variant.rst:67
msgid "``byte[]``"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:83
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_variant.rst:70
msgid "``PackedFloat32Array``"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:83
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_variant.rst:70
msgid "``float[]``"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:84
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_variant.rst:71
msgid "``PackedFloat64Array``"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:84
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_variant.rst:71
msgid "``double[]``"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:85
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_variant.rst:72
msgid "``PackedStringArray``"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:85
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_variant.rst:72
msgid "``string[]``"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:86
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_variant.rst:75
msgid "``PackedColorArray``"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:86
msgid "``Color[]``"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:87
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_variant.rst:73
msgid "``PackedVector2Array``"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:87
msgid "``Vector2[]``"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:88
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_variant.rst:74
msgid "``PackedVector3Array``"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:88
msgid "``Vector3[]``"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:91
msgid ""
"Other C# arrays are not supported by the Godot C# API since a packed array "
"equivalent does not exist. See :ref:`Variant <doc_c_sharp_variant>` for a "
"list of all the compatible types."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:100
msgid ""
"Godot arrays are implemented as an array of ``Variant`` and can contain "
"several elements of any type. In C#, the equivalent type is ``Godot."
"Collections.Array``."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:103
msgid ""
"The generic ``Godot.Collections.Array<T>`` type allows restricting the "
"element type to a :ref:`Variant-compatible <doc_c_sharp_variant>` type."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:106
msgid ""
"An untyped ``Godot.Collections.Array`` can be converted to a typed array "
"using the ``Godot.Collections.Array<T>(Godot.Collections.Array)`` "
"constructor."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:111
msgid ""
"Despite the name, Godot arrays are more similar to the C# collection "
"``List<T>`` than ``System.Array``. Their size is not fixed and can grow or "
"shrink as elements are added/removed from the collection."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:115
msgid "List of Godot's Array methods and their equivalent in C#:"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:120
msgid "all"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:120
msgid "`System.Linq.Enumerable.All`_"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:121
msgid "any"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:121
msgid "`System.Linq.Enumerable.Any`_"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:122
msgid "append"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:122
msgid "Add"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:123
msgid "append_array"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:123
msgid "AddRange"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:124
msgid "assign"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:124
msgid "Clear and AddRange"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:125
msgid "back"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:125
msgid ""
"``Array[^1]`` or `System.Linq.Enumerable.Last`_ or `System.Linq.Enumerable."
"LastOrDefault`_"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:126
msgid "bsearch"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:126
msgid "BinarySearch"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:127
msgid "bsearch_custom"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:128
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:218
#: ../../docs/contributing/documentation/docs_writing_guidelines.rst:163
msgid "clear"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:128
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:218
msgid "Clear"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:129
msgid "`System.Linq.Enumerable.Count`_"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:130
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:219
msgid "duplicate"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:131
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:220
msgid "Remove"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:132
msgid "fill"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:132
msgid "Fill"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:133
msgid "filter"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:133
msgid "Use `System.Linq.Enumerable.Where`_"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:134
msgid "IndexOf"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:135
msgid "front"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:135
msgid ""
"``Array[0]`` or `System.Linq.Enumerable.First`_ or `System.Linq.Enumerable."
"FirstOrDefault`_"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:136
msgid "get_typed_builtin"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:137
msgid "get_typed_class_name"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:138
msgid "get_typed_script"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:139
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:223
msgid "has"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:139
#, fuzzy
msgid "Contains"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:141
#, fuzzy
msgid "Insert"
msgstr "Unesi Ključ"

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:142
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:226
msgid "Use ``Count == 0``"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:143
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:227
msgid "is_read_only"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:143
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:227
msgid "IsReadOnly"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:144
msgid "is_same_typed"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:145
msgid "is_typed"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:146
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:229
msgid "make_read_only"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:146
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:229
msgid "MakeReadOnly"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:147
msgid "map"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:147
msgid "`System.Linq.Enumerable.Select`_"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:148
msgid "Max"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:149
msgid "Min"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:150
msgid "pick_random"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:150
msgid "PickRandom (Consider using `System.Random`_)"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:151
msgid "pop_at"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:151
msgid "``Array[i]`` with ``RemoveAt(i)``"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:152
msgid "pop_back"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:152
msgid "``Array[^1]`` with ``RemoveAt(Count - 1)``"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:153
msgid "pop_front"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:153
msgid "``Array[0]`` with ``RemoveAt(0)``"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:154
msgid "push_back"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:154
msgid "``Insert(Count, item)``"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:155
msgid "push_front"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:155
msgid "``Insert(0, item)``"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:156
msgid "reduce"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:156
msgid "`System.Linq.Enumerable.Aggregate`_"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:157
msgid "remove_at"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:157
msgid "RemoveAt"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:158
msgid "resize"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:158
msgid "Resize"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:159
msgid "Reverse"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:160
msgid "LastIndexOf"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:161
msgid "shuffle"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:161
msgid "Shuffle"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:162
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:231
msgid "size"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:162
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:231
msgid "Count"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:163
msgid "slice"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:163
msgid "Slice"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:164
msgid "sort"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:164
msgid "Sort"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:165
msgid "sort_custom"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:165
msgid "`System.Linq.Enumerable.OrderBy`_"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:166
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:233
msgid "operator !="
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:166
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:233
msgid "!RecursiveEqual"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:167
msgid "operator +"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:168
msgid "operator <"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:169
msgid "operator <="
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:170
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:234
msgid "operator =="
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:170
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:234
msgid "RecursiveEqual"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:171
msgid "operator >"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:172
msgid "operator >="
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:173
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:235
msgid "operator []"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:173
msgid "Array[int] indexer"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:194
msgid ""
"Godot dictionaries are implemented as a dictionary with ``Variant`` keys and "
"values. In C#, the equivalent type is ``Godot.Collections.Dictionary``."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:197
msgid ""
"The generic ``Godot.Collections.Dictionary<TKey, TValue>`` type allows "
"restricting the key and value types to a :ref:`Variant-compatible "
"<doc_c_sharp_variant>` type."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:200
msgid ""
"An untyped ``Godot.Collections.Dictionary`` can be converted to a typed "
"dictionary using the ``Godot.Collections.Dictionary<TKey, TValue>(Godot."
"Collections.Dictionary)`` constructor."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:205
msgid ""
"If you need a dictionary where the key is typed but not the value, use "
"``Variant`` as the ``TValue`` generic parameter of the typed dictionary."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:213
msgid "List of Godot's Dictionary methods and their equivalent in C#:"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:221
msgid "find_key"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:222
msgid "get"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:222
msgid "Dictionary[Variant] indexer or TryGetValue"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:223
#, fuzzy
msgid "ContainsKey"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:224
msgid "has_all"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:228
msgid "Keys"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:230
msgid "merge"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:230
msgid "Merge"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:232
msgid "values"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:232
msgid "Values"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_collections.rst:235
msgid "Dictionary[Variant] indexer, Add or TryGetValue"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_variant.rst:4
msgid "C# Variant"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_variant.rst:6
msgid ""
"For a detailed explanation of Variant in general, see the :ref:`Variant "
"<class_Variant>` documentation page."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_variant.rst:8
msgid ""
"``Godot.Variant`` is used to represent Godot's native :ref:`Variant "
"<class_Variant>` type. Any Variant-compatible type can be converted from/to "
"it. We recommend avoiding ``Godot.Variant`` unless it is necessary to "
"interact with untyped engine APIs. Take advantage of C#'s type safety when "
"possible."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_variant.rst:12
msgid ""
"Any of ``Variant.As{TYPE}`` methods or the generic ``Variant.As<T>`` method "
"can be used to convert a ``Godot.Variant`` to a C# type. Since the ``Godot."
"Variant`` type contains implicit conversions defined for all the supported "
"types, calling these methods directly is usually not necessary."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_variant.rst:16
msgid ""
"Use ``CreateFrom`` method overloads or the generic ``Variant.From<T>`` "
"method to convert a C# type to a ``Godot.Variant``."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_variant.rst:21
msgid ""
"Since the Variant type in C# is a struct, it can't be null. To create a "
"\"null\" Variant use the ``default`` keyword or the parameterless "
"constructor."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_variant.rst:25
msgid "Variant-compatible types"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_variant.rst:27
msgid ""
"All the `built-in value types <https://docs.microsoft.com/en-us/dotnet/"
"csharp/language-reference/keywords/built-in-types-table>`_, except "
"``decimal``, ``nint`` and ``nuint``."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_variant.rst:29
msgid "``string``."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_variant.rst:30
msgid "Classes derived from :ref:`GodotObject <class_Object>`."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_variant.rst:31
msgid "Collections types defined in the ``Godot.Collections`` namespace."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_variant.rst:33
msgid "Full list of Variant types and their equivalent C# type:"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_variant.rst:36
msgid "Variant.Type"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_variant.rst:36
msgid "C# Type"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_variant.rst:38
msgid "``Nil``"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_variant.rst:38
msgid "``null`` (Not a type)"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_variant.rst:39
msgid "``Bool``"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_variant.rst:39
msgid "``bool``"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_variant.rst:40
msgid "``Int``"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_variant.rst:40
msgid "``long`` (Godot stores 64-bit integers in Variant)"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_variant.rst:41
msgid "``Float``"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_variant.rst:41
msgid "``double`` (Godot stores 64-bit floats in Variant)"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_variant.rst:42
#: ../../docs/tutorials/scripting/creating_script_templates.rst:233
msgid "``String``"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_variant.rst:42
msgid "``string``"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_variant.rst:43
msgid "``Vector2``"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_variant.rst:43
msgid "``Godot.Vector2``"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_variant.rst:44
msgid "``Vector2I``"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_variant.rst:44
msgid "``Godot.Vector2I``"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_variant.rst:45
msgid "``Rect2``"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_variant.rst:45
msgid "``Godot.Rect2``"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_variant.rst:46
msgid "``Rect2I``"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_variant.rst:46
msgid "``Godot.Rect2I``"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_variant.rst:47
msgid "``Vector3``"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_variant.rst:47
msgid "``Godot.Vector3``"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_variant.rst:48
msgid "``Vector3I``"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_variant.rst:48
msgid "``Godot.Vector3I``"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_variant.rst:49
msgid "``Transform2D``"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_variant.rst:49
msgid "``Godot.Transform2D``"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_variant.rst:50
msgid "``Vector4``"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_variant.rst:50
msgid "``Godot.Vector4``"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_variant.rst:51
msgid "``Vector4I``"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_variant.rst:51
msgid "``Godot.Vector4I``"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_variant.rst:52
msgid "``Plane``"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_variant.rst:52
msgid "``Godot.Plane``"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_variant.rst:53
msgid "``Quaternion``"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_variant.rst:53
msgid "``Godot.Quaternion``"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_variant.rst:54
msgid "``Aabb``"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_variant.rst:54
msgid "``Godot.Aabb``"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_variant.rst:55
msgid "``Basis``"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_variant.rst:55
msgid "``Godot.Basis``"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_variant.rst:56
msgid "``Transform3D``"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_variant.rst:56
msgid "``Godot.Transform3D``"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_variant.rst:57
#, fuzzy
msgid "``Projection``"
msgstr "Uvod / Početak"

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_variant.rst:57
msgid "``Godot.Projection``"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_variant.rst:58
msgid "``Color``"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_variant.rst:58
msgid "``Godot.Color``"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_variant.rst:59
msgid "``StringName``"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_variant.rst:59
msgid "``Godot.StringName``"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_variant.rst:60
#, fuzzy
msgid "``NodePath``"
msgstr "Uvod / Početak"

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_variant.rst:60
msgid "``Godot.NodePath``"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_variant.rst:61
msgid "``Rid``"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_variant.rst:61
msgid "``Godot.Rid``"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_variant.rst:62
msgid "``Object``"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_variant.rst:62
msgid "``Godot.GodotObject`` or any derived type."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_variant.rst:63
msgid "``Callable``"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_variant.rst:63
msgid "``Godot.Callable``"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_variant.rst:64
#, fuzzy
msgid "``Signal``"
msgstr "Signali"

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_variant.rst:64
msgid "``Godot.Signal``"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_variant.rst:65
#, fuzzy
msgid "``Dictionary``"
msgstr "Uvod"

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_variant.rst:65
msgid "``Godot.Collections.Dictionary``"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_variant.rst:66
msgid "``Array``"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_variant.rst:66
msgid "``Godot.Collections.Array``"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_variant.rst:73
msgid "``Godot.Vector2[]``"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_variant.rst:74
msgid "``Godot.Vector3[]``"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_variant.rst:75
msgid "``Godot.Color[]``"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_variant.rst:80
msgid ""
"Godot uses 64-bit integers and floats in Variant. Smaller integer and float "
"types such as ``int``, ``short`` and ``float`` are supported since they can "
"fit in the bigger type. Be aware that an implicit conversion is performed so "
"using the wrong type will result in potential precision loss."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_variant.rst:87
msgid ""
"Enums are supported by ``Godot.Variant`` since their underlying type is an "
"integer type which are all compatible. However, implicit conversions don't "
"exist, enums must be manually converted to their underlying integer type "
"before they can converted to/from ``Godot.Variant`` or use the generic "
"``Variant.As<T>`` and ``Variant.From<T>`` methods to convert them."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_variant.rst:104
msgid "Using Variant in a generic context"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_variant.rst:106
msgid ""
"When using generics, you may be interested in restricting the generic ``T`` "
"type to be only one of the Variant-compatible types. This can be achieved "
"using the ``[MustBeVariant]`` attribute."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_variant.rst:117
msgid ""
"Combined with the generic ``Variant.From<T>`` allows you to obtain an "
"instance of ``Godot.Variant`` from an instance of a generic ``T`` type. Then "
"it can be used in any API that only supports the ``Godot.Variant`` struct."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_variant.rst:134
msgid ""
"In order to invoke a method with a generic parameter annotated with the "
"``[MustBeVariant]`` attribute, the value must be a Variant-compatible type "
"or a generic ``T`` type annotated with the ``[MustBeVariant]`` attribute as "
"well."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_signals.rst:4
msgid "C# signals"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_signals.rst:6
msgid ""
"For a detailed explanation of signals in general, see the :ref:`doc_signals` "
"section in the step by step tutorial."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_signals.rst:9
msgid ""
"While it is still possible to use signals through the ``Connect``/"
"``Disconnect`` API, C# gives us a more idiomatic way to implement the :ref:"
"`observer pattern<doc_key_concepts_signals>`."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_signals.rst:13
msgid "Signals as C# events"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_signals.rst:15
msgid ""
"To provide more type-safety, Godot signals are also all available through "
"`events <https://learn.microsoft.com/en-us/dotnet/csharp/events-overview>`_. "
"You can handle these events, as any other event, with the ``+=`` and ``-=`` "
"operators."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_signals.rst:23
msgid ""
"In addition, you can always access signal names associated with a node type "
"through its nested ``SignalName`` class. This is useful when, for example, "
"you want to await on a signal (see :ref:`doc_c_sharp_differences_await`)."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_signals.rst:32
msgid ""
"While all engine signals connected as events are automatically disconnected "
"when nodes are freed, custom signals aren't. Meaning that: you will need to "
"manually disconnect (using ``-=``) all the custom signals you connected as "
"C# events (using ``+=``)."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_signals.rst:37
msgid "Custom signals as C# events"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_signals.rst:39
msgid ""
"To declare a custom event in your C# script, use the ``[Signal]`` attribute "
"on a public delegate type. Note that the name of this delegate needs to end "
"with ``EventHandler``."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_signals.rst:50
msgid ""
"Once this is done, Godot will create the appropriate events automatically "
"behind the scenes. You can then use said events as you'd do for any other "
"Godot signal. Note that events are named using your delegate's name minus "
"the final ``EventHandler`` part."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_signals.rst:69
msgid ""
"If you want to connect to these signals in the editor, you will need to "
"(re)build the project to see them appear."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_signals.rst:72
msgid ""
"You can click the **Build** button in the upper-right corner of the editor "
"to do so."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_signals.rst:75
#, fuzzy
msgid "Signal emission"
msgstr "Signali"

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_signals.rst:77
msgid ""
"To emit signals, use the ``EmitSignal`` method. Note that, as for signals "
"defined by the engine, your custom signal names are listed under the nested "
"``SignalName`` class."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_signals.rst:88
msgid ""
"In contrast with other C# events, you cannot use ``Invoke`` to raise events "
"tied to Godot signals."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_signals.rst:90
msgid ""
"Signals support arguments of any :ref:`Variant-compatible "
"<doc_c_sharp_variant>` type."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_signals.rst:92
msgid ""
"Consequently, any ``Node`` or ``RefCounted`` will be compatible "
"automatically, but custom data objects will need to inherit from "
"``GodotObject`` or one of its subclasses."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_signals.rst:106
msgid "Bound values"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_signals.rst:108
msgid ""
"Sometimes you'll want to bind values to a signal when the connection is "
"established, rather than (or in addition to) when the signal is emitted. To "
"do so, you can use an anonymous function like in the following example."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_signals.rst:112
msgid ""
"Here, the :ref:`Button.Pressed <class_BaseButton_signal_pressed>` signal do "
"not take any argument. But we want to use the same ``ModifyValue`` for both "
"the \"plus\" and \"minus\" buttons. So we bind the modifier value at the "
"time we're connecting the signals."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_signals.rst:135
msgid "Signal creation at runtime"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_signals.rst:137
msgid ""
"Finally, you can create custom signals directly while your game is running. "
"Use the ``AddUserSignal`` method for that. Be aware that it should be "
"executed before any use of said signals (either connecting to them or "
"emitting them). Also, note that signals created this way won't be visible "
"through the ``SignalName`` nested class."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_exports.rst:4
#, fuzzy
msgid "C# exported properties"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_exports.rst:6
msgid ""
"In Godot, class members can be exported. This means their value gets saved "
"along with the resource (such as the :ref:`scene <class_PackedScene>`) "
"they're attached to. They will also be available for editing in the property "
"editor. Exporting is done by using the ``[Export]`` attribute."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_exports.rst:21
msgid ""
"In that example the value ``5`` will be saved, and after building the "
"current project it will be visible in the property editor."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_exports.rst:29
msgid ""
"Exporting can only be done with :ref:`Variant-compatible "
"<doc_c_sharp_variant>` types."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_exports.rst:33
msgid ""
"Exporting properties can also be done in GDScript, for information on that "
"see :ref:`doc_gdscript_exports`."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_exports.rst:39
msgid "Exporting can work with fields and properties."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_exports.rst:49
msgid ""
"Exported members can specify a default value; otherwise, the `default value "
"of the type <https://learn.microsoft.com/en-us/dotnet/csharp/language-"
"reference/builtin-types/default-values>`_ is used instead."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_exports.rst:85
#, fuzzy
msgid "Grouping exports"
msgstr "Uvod"

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_exports.rst:87
msgid ""
"It is possible to group your exported properties inside the Inspector with "
"the ``[ExportGroup]`` attribute. Every exported property after this "
"attribute will be added to the group. Start a new group or use "
"``[ExportGroup(\"\")]`` to break out."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_exports.rst:97
msgid ""
"The second argument of the attribute can be used to only group properties "
"with the specified prefix."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_exports.rst:99
msgid ""
"Groups cannot be nested, use ``[ExportSubgroup]`` to create subgroups within "
"a group."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_exports.rst:109
msgid ""
"You can also change the name of your main category, or create additional "
"categories in the property list with the ``[ExportCategory]`` attribute."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_exports.rst:126
msgid ""
"The list of properties is organized based on the class inheritance, and new "
"categories break that expectation. Use them carefully, especially when "
"creating projects for public use."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_exports.rst:132
msgid "Property hints can be used to export strings as paths"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_exports.rst:183
msgid ""
"Using the range property hint allows you to limit what can be input as a "
"value using the editor."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_exports.rst:207
msgid ""
"If you add the hints \"or_greater\" and/or \"or_less\" you can go above or "
"below the limits when adjusting the value by typing it instead of using the "
"slider."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_exports.rst:247
msgid ""
"Since Godot 4.0, nodes can be directly exported without having to use "
"NodePaths."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_exports.rst:254
msgid ""
"Custom node classes can also be used, see :ref:`doc_c_sharp_global_classes`."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_exports.rst:279
msgid ""
"Opening the inspector dropdown may result in an extremely long list of "
"possible classes to create, however. Therefore, if you specify a type "
"derived from Resource such as:"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_exports.rst:288
msgid ""
"The drop-down menu will be limited to AnimationNode and all its inherited "
"classes. Custom resource classes can also be used, see :ref:"
"`doc_c_sharp_global_classes`."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_exports.rst:299
msgid ""
"Members whose type is an enum with the ``[Flags]`` attribute can be exported "
"and their values are limited to the members of the enum type. The editor "
"will create a widget in the Inspector, allowing to select none, one, or "
"multiple of the enum members. The value will be stored as an integer."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_exports.rst:322
msgid ""
"Integers used as bit flags can store multiple ``true``/``false`` (boolean) "
"values in one property. By using the ``Flags`` property hint, they can be "
"set from the editor."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_exports.rst:332
msgid ""
"You must provide a string description for each flag. In this example, "
"``Fire`` has value 1, ``Water`` has value 2, ``Earth`` has value 4 and "
"``Wind`` corresponds to value 8. Usually, constants should be defined "
"accordingly (e.g. ``private const int ElementWind = 8`` and so on)."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_exports.rst:337
#: ../../docs/tutorials/scripting/c_sharp/c_sharp_exports.rst:399
msgid "You can add explicit values using a colon:"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_exports.rst:344
msgid ""
"Only power of 2 values are valid as bit flags options. The lowest allowed "
"value is 1, as 0 means that nothing is selected. You can also add options "
"that are a combination of other flags:"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_exports.rst:353
msgid ""
"Export annotations are also provided for the physics and render layers "
"defined in the project settings."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_exports.rst:372
msgid ""
"Members whose type is an enum can be exported and their values are limited "
"to the members of the enum type. The editor will create a widget in the "
"Inspector, enumerating the following as \"Thing 1\", \"Thing 2\", \"Another "
"Thing\". The value will be stored as an integer."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_exports.rst:388
msgid ""
"Integer and string members can also be limited to a specific list of values "
"using the ``[Export]`` annotation with the ``PropertyHint.Enum`` hint. The "
"editor will create a widget in the Inspector, enumerating the following as "
"Warrior, Magician, Thief. The value will be stored as an integer, "
"corresponding to the index of the selected option (i.e. ``0``, ``1``, or "
"``2``)."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_exports.rst:406
msgid "If the type is ``string``, the value will be stored as a string."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_exports.rst:413
msgid "If you want to set an initial value, you must specify it explicitly:"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_exports.rst:421
#, fuzzy
msgid "Exporting collections"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_exports.rst:423
msgid ""
"As explained in the :ref:`C# Variant <doc_c_sharp_variant>` documentation, "
"only certain C# arrays and the collection types defined in the ``Godot."
"Collections`` namespace are Variant-compatible, therefore, only those types "
"can be exported."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_exports.rst:428
#, fuzzy
msgid "Exporting Godot arrays"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_exports.rst:435
msgid ""
"Using the generic ``Godot.Collections.Array<T>`` allows to specify the type "
"of the array elements which will be used as a hint for the editor. The "
"Inspector will restrict the elements to the specified type."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_exports.rst:444
msgid ""
"The default value of Godot arrays is null, a different default can be "
"specified:"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_exports.rst:468
#, fuzzy
msgid "Exporting Godot dictionaries"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_exports.rst:475
msgid ""
"Using the generic ``Godot.Collections.Dictionary<TKey, TValue>`` allows to "
"specify the type of the key and value elements of the dictionary."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_exports.rst:480
msgid ""
"Typed dictionaries are currently unsupported in the Godot editor, so the "
"Inspector will not restrict the types that can be assigned, potentially "
"resulting in runtime exceptions."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_exports.rst:489
msgid ""
"The default value of Godot dictionaries is null, a different default can be "
"specified:"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_exports.rst:502
#, fuzzy
msgid "Exporting C# arrays"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_exports.rst:504
msgid ""
"C# arrays can exported as long as the element type is a :ref:`Variant-"
"compatible <doc_c_sharp_variant>` type."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_exports.rst:514
msgid ""
"The default value of C# arrays is null, a different default can be specified:"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_exports.rst:528
msgid ""
"When changing an exported variable's value from a script in :ref:"
"`doc_gdscript_tool_mode`, the value in the inspector won't be updated "
"automatically. To update it, call :ref:`NotifyPropertyListChanged() "
"<class_Object_method_notify_property_list_changed>` after setting the "
"exported variable's value."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_exports.rst:541
msgid ""
"Before reading further, you should get familiar with the way properties are "
"handled and how they can be customized with :ref:`_Set() "
"<class_Object_private_method__set>`, :ref:`_Get() "
"<class_Object_private_method__get>`, and :ref:`_GetPropertyList() "
"<class_Object_private_method__get_property_list>` methods as described in :"
"ref:`doc_accessing_data_or_logic_from_object`."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_global_classes.rst:4
msgid "C# global classes"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_global_classes.rst:6
msgid ""
"Global classes (also known as named scripts) are types registered in Godot's "
"editor so they can be used more conveniently. These classes show up in the "
"*Add Node* and *Create Resource* dialogs, and :ref:`exported properties "
"<doc_c_sharp_exports>` are restricted to instances of the global class or "
"derived classes. Global classes are registered with the ``[GlobalClass]`` "
"attribute."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_global_classes.rst:20
msgid ""
"The ``MyNode`` type will be registered as a global class with the same name "
"as the type's name."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_global_classes.rst:24
msgid ""
"The ``[Icon]`` attribute also allows to provide the path to an icon so it "
"can be used as the class' icon in the editor."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_global_classes.rst:46
msgid ""
"The ``Stats`` class is a custom resource registered as a global class. :ref:"
"`Exporting properties <doc_c_sharp_exports>` of the type ``Stats`` will only "
"allow instances of this resource type to be assigned, and the inspector will "
"let you create and load instances of this type easily."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_style_guide.rst:4
msgid "C# style guide"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_style_guide.rst:6
msgid ""
"Having well-defined and consistent coding conventions is important for every "
"project, and Godot is no exception to this rule."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_style_guide.rst:9
msgid ""
"This page contains a coding style guide, which is followed by developers of "
"and contributors to Godot itself. As such, it is mainly intended for those "
"who want to contribute to the project, but since the conventions and "
"guidelines mentioned in this article are those most widely adopted by the "
"users of the language, we encourage you to do the same, especially if you do "
"not have such a guide yet."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_style_guide.rst:14
msgid ""
"This article is by no means an exhaustive guide on how to follow the "
"standard coding conventions or best practices. If you feel unsure of an "
"aspect which is not covered here, please refer to more comprehensive "
"documentation, such as `C# Coding Conventions <https://docs.microsoft.com/en-"
"us/dotnet/csharp/programming-guide/inside-a-program/coding-conventions>`_ or "
"`Framework Design Guidelines <https://docs.microsoft.com/en-us/dotnet/"
"standard/design-guidelines/naming-guidelines>`_."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_style_guide.rst:21
msgid "Language specification"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_style_guide.rst:23
msgid ""
"Godot currently uses **C# version 7.0** in its engine and example source "
"code. So, before we move to a newer version, care must be taken to avoid "
"mixing language features only available in C# 7.1 or later."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_style_guide.rst:27
msgid ""
"For detailed information on C# features in different versions, please see "
"`What's New in C# <https://docs.microsoft.com/en-us/dotnet/csharp/whats-new/"
">`_."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_style_guide.rst:34
msgid "General guidelines"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_style_guide.rst:36
msgid "Use line feed (**LF**) characters to break lines, not CRLF or CR."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_style_guide.rst:37
msgid ""
"Use one line feed character at the end of each file, except for `csproj` "
"files."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_style_guide.rst:38
msgid ""
"Use **UTF-8** encoding without a `byte order mark <https://en.wikipedia.org/"
"wiki/Byte_order_mark>`_."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_style_guide.rst:39
msgid ""
"Use **4 spaces** instead of tabs for indentation (which is referred to as "
"\"soft tabs\")."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_style_guide.rst:40
msgid ""
"Consider breaking a line into several if it's longer than 100 characters."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_style_guide.rst:44
#: ../../docs/tutorials/shaders/shaders_style_guide.rst:103
msgid "Line breaks and blank lines"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_style_guide.rst:46
msgid ""
"For a general indentation rule, follow `the \"Allman Style\" <https://en."
"wikipedia.org/wiki/Indentation_style#Allman_style>`_ which recommends "
"placing the brace associated with a control statement on the next line, "
"indented to the same level:"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_style_guide.rst:63
msgid "However, you may choose to omit line breaks inside brackets:"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_style_guide.rst:65
msgid "For simple property accessors."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_style_guide.rst:66
msgid "For simple object, array, or collection initializers."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_style_guide.rst:67
msgid "For abstract auto property, indexer, or event declarations."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_style_guide.rst:89
msgid "Insert a blank line:"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_style_guide.rst:91
msgid "After a list of ``using`` statements."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_style_guide.rst:92
msgid "Between method, properties, and inner type declarations."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_style_guide.rst:93
msgid "At the end of each file."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_style_guide.rst:95
msgid ""
"Field and constant declarations can be grouped together according to "
"relevance. In that case, consider inserting a blank line between the groups "
"for easier reading."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_style_guide.rst:98
msgid "Avoid inserting a blank line:"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_style_guide.rst:100
msgid "After ``{``, the opening brace."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_style_guide.rst:101
msgid "Before ``}``, the closing brace."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_style_guide.rst:102
msgid "After a comment block or a single-line comment."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_style_guide.rst:103
msgid "Adjacent to another blank line."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_style_guide.rst:142
msgid "Using spaces"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_style_guide.rst:144
msgid "Insert a space:"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_style_guide.rst:146
msgid "Around a binary and ternary operator."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_style_guide.rst:147
msgid ""
"Between an opening parenthesis and ``if``, ``for``, ``foreach``, ``catch``, "
"``while``, ``lock`` or ``using`` keywords."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_style_guide.rst:148
msgid "Before and within a single line accessor block."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_style_guide.rst:149
msgid "Between accessors in a single line accessor block."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_style_guide.rst:150
msgid "After a comma which is not at the end of a line."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_style_guide.rst:151
msgid "After a semicolon in a ``for`` statement."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_style_guide.rst:152
msgid "After a colon in a single line ``case`` statement."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_style_guide.rst:153
msgid "Around a colon in a type declaration."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_style_guide.rst:154
msgid "Around a lambda arrow."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_style_guide.rst:155
msgid ""
"After a single-line comment symbol (``//``), and before it if used at the "
"end of a line."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_style_guide.rst:157
msgid "Do not use a space:"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_style_guide.rst:159
msgid "After type cast parentheses."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_style_guide.rst:160
msgid "Within single line initializer braces."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_style_guide.rst:162
msgid ""
"The following example shows a proper use of spaces, according to some of the "
"above mentioned conventions:"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_style_guide.rst:199
msgid ""
"Use **PascalCase** for all namespaces, type names and member level "
"identifiers (i.e. methods, properties, constants, events), except for "
"private fields:"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_style_guide.rst:220
msgid ""
"Use **camelCase** for all other identifiers (i.e. local variables, method "
"arguments), and use an underscore (``_``) as a prefix for private fields "
"(but not for methods or properties, as explained above):"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_style_guide.rst:234
msgid ""
"There's an exception with acronyms which consist of two letters, like "
"``UI``, which should be written in uppercase letters where PascalCase would "
"be expected, and in lowercase letters otherwise."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_style_guide.rst:237
msgid ""
"Note that ``id`` is **not** an acronym, so it should be treated as a normal "
"identifier:"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_style_guide.rst:248
msgid ""
"It is generally discouraged to use a type name as a prefix of an identifier, "
"like ``string strText`` or ``float fPower``, for example. An exception is "
"made, however, for interfaces, which **should**, in fact, have an uppercase "
"letter ``I`` prefixed to their names, like ``IInventoryHolder`` or "
"``IDamageable``."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_style_guide.rst:252
msgid ""
"Lastly, consider choosing descriptive names and do not try to shorten them "
"too much if it affects readability."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_style_guide.rst:255
msgid ""
"For instance, if you want to write code to find a nearby enemy and hit it "
"with a weapon, prefer:"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_style_guide.rst:261
msgid "Rather than:"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_style_guide.rst:282
msgid "Implicitly typed local variables"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_style_guide.rst:284
msgid ""
"Consider using implicitly typing (``var``) for declaration of a local "
"variable, but do so **only when the type is evident** from the right side of "
"the assignment:"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_style_guide.rst:314
msgid "Other considerations"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_style_guide.rst:316
msgid "Use explicit access modifiers."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_style_guide.rst:317
msgid "Use properties instead of non-private fields."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_style_guide.rst:318
msgid ""
"Use modifiers in this order: ``public``/``protected``/``private``/"
"``internal``/``virtual``/``override``/``abstract``/``new``/``static``/"
"``readonly``."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_style_guide.rst:320
msgid ""
"Avoid using fully-qualified names or ``this.`` prefix for members when it's "
"not necessary."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_style_guide.rst:321
msgid "Remove unused ``using`` statements and unnecessary parentheses."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_style_guide.rst:322
msgid "Consider omitting the default initial value for a type."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_style_guide.rst:323
msgid ""
"Consider using null-conditional operators or type initializers to make the "
"code more compact."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/c_sharp_style_guide.rst:324
msgid ""
"Use safe cast when there is a possibility of the value being a different "
"type, and use direct cast otherwise."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/diagnostics/index.rst:4
msgid "C# diagnostics"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/diagnostics/index.rst:6
msgid ""
"Godot includes analyzers that inspect your C# source code to check for "
"invalid or unsupported code and let you know that something is wrong during "
"build time."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/diagnostics/index.rst:10
msgid "Rules"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0001.rst:2
msgid ""
"GD0001: Missing partial modifier on declaration of type that derives from "
"GodotObject"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0001.rst:7
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0002.rst:7
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0101.rst:7
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0102.rst:7
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0103.rst:7
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0104.rst:7
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0105.rst:7
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0106.rst:7
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0107.rst:7
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0201.rst:7
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0202.rst:7
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0203.rst:7
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0301.rst:7
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0302.rst:7
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0303.rst:7
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0401.rst:7
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0402.rst:7
msgid "**Rule ID**"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0001.rst:7
msgid "GD0001"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0001.rst:8
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0002.rst:8
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0101.rst:8
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0102.rst:8
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0103.rst:8
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0104.rst:8
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0105.rst:8
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0106.rst:8
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0107.rst:8
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0201.rst:8
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0202.rst:8
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0203.rst:8
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0301.rst:8
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0302.rst:8
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0303.rst:8
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0401.rst:8
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0402.rst:8
msgid "**Category**"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0001.rst:9
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0002.rst:9
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0101.rst:9
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0102.rst:9
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0103.rst:9
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0104.rst:9
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0105.rst:9
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0106.rst:9
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0107.rst:9
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0201.rst:9
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0202.rst:9
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0203.rst:9
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0301.rst:9
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0302.rst:9
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0303.rst:9
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0401.rst:9
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0402.rst:9
msgid "**Fix is breaking or non-breaking**"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0001.rst:9
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0002.rst:9
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0103.rst:9
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0104.rst:9
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0105.rst:9
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0106.rst:9
#, fuzzy
msgid "Non-breaking"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0001.rst:10
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0002.rst:10
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0101.rst:12
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0102.rst:12
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0103.rst:10
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0104.rst:10
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0105.rst:10
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0106.rst:10
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0107.rst:10
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0201.rst:10
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0202.rst:12
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0203.rst:12
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0301.rst:10
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0302.rst:10
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0303.rst:10
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0401.rst:12
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0402.rst:10
msgid "**Enabled by default**"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0001.rst:10
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0002.rst:10
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0101.rst:12
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0102.rst:12
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0103.rst:10
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0104.rst:10
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0105.rst:10
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0106.rst:10
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0107.rst:10
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0201.rst:10
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0202.rst:12
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0203.rst:12
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0301.rst:10
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0302.rst:10
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0303.rst:10
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0401.rst:12
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0402.rst:10
msgid "Yes"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0001.rst:14
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0002.rst:14
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0101.rst:16
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0102.rst:16
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0103.rst:14
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0104.rst:14
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0105.rst:14
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0106.rst:14
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0107.rst:14
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0201.rst:14
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0202.rst:16
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0203.rst:16
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0301.rst:14
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0302.rst:14
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0303.rst:14
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0401.rst:16
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0402.rst:14
msgid "Cause"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0001.rst:16
msgid "A type that derives from ``GodotObject`` is not declared partial."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0001.rst:19
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0002.rst:19
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0101.rst:22
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0102.rst:22
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0103.rst:20
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0104.rst:20
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0105.rst:19
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0106.rst:20
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0107.rst:20
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0201.rst:20
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0202.rst:23
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0203.rst:22
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0301.rst:20
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0302.rst:21
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0303.rst:19
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0401.rst:22
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0402.rst:19
#, fuzzy
msgid "Rule description"
msgstr "Uvod"

#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0001.rst:21
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0002.rst:21
msgid ""
"Godot source generators add generated code to user-defined types to "
"implement the integration with the engine. Source generators can't add "
"generated code to types that aren't declared partial."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0001.rst:34
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0002.rst:42
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0101.rst:37
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0102.rst:41
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0103.rst:43
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0104.rst:37
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0105.rst:36
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0106.rst:50
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0107.rst:26
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0201.rst:43
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0202.rst:43
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0203.rst:40
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0301.rst:39
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0302.rst:46
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0303.rst:27
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0401.rst:45
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0402.rst:36
msgid "How to fix violations"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0001.rst:36
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0002.rst:44
msgid ""
"To fix a violation of this rule, add the ``partial`` keyword to the type "
"declaration."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0001.rst:40
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0002.rst:48
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0101.rst:43
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0102.rst:47
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0103.rst:52
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0104.rst:43
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0105.rst:41
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0106.rst:56
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0107.rst:32
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0201.rst:48
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0202.rst:56
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0203.rst:53
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0301.rst:46
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0302.rst:52
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0303.rst:32
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0401.rst:51
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0402.rst:42
msgid "When to suppress warnings"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0001.rst:42
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0002.rst:50
msgid ""
"Do not suppress a warning from this rule. Types that derive from "
"``GodotObject`` but aren't partial can't be enhanced by the source "
"generators, resulting in unexpected runtime errors."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0002.rst:2
msgid ""
"GD0002: Missing partial modifier on declaration of type which contains "
"nested classes that derive from GodotObject"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0002.rst:7
msgid "GD0002"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0002.rst:16
msgid ""
"A type that derives from ``GodotObject`` is contained in a non-partial type "
"declaration."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0101.rst:2
msgid "GD0101: Attempted to export static member"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0101.rst:7
msgid "GD0101"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0101.rst:9
msgid "Breaking - If the ``static`` keyword is removed"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0101.rst:11
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0102.rst:11
msgid "Non-breaking - If the ``[Export]`` attribute is removed"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0101.rst:18
msgid ""
"A static member is annotated with the ``[Export]`` attribute. Static members "
"can't be exported."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0101.rst:24
msgid "Godot doesn't allow exporting static members."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0101.rst:39
msgid ""
"To fix a violation of this rule, remove the ``[Export]`` attribute or remove "
"the ``static`` keyword."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0101.rst:45
msgid ""
"Do not suppress a warning from this rule. Static members can't be exported "
"so they will be ignored by Godot, resulting in runtime errors."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0102.rst:2
msgid "GD0102: The type of the exported member is not supported"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0102.rst:7
msgid "GD0102"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0102.rst:9
msgid "Breaking - If the member type is changed"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0102.rst:18
msgid ""
"An unsupported type is specified for a member annotated with the "
"``[Export]`` attribute when a :ref:`Variant-compatible "
"<doc_c_sharp_variant>` type is expected."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0102.rst:24
msgid ""
"Every exported member must be Variant-compatible so it can be marshalled by "
"the engine."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0102.rst:43
msgid ""
"To fix a violation of this rule, change the member's type to be Variant-"
"compatible or remove the ``[Export]`` attribute."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0102.rst:49
msgid ""
"Do not suppress a warning from this rule. Members with types that can't be "
"marshalled will result in runtime errors."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0103.rst:2
msgid "GD0103: The exported member is read-only"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0103.rst:7
msgid "GD0103"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0103.rst:16
msgid ""
"A read-only member is annotated with the ``[Export]`` attribute. Read-only "
"members can't be exported."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0103.rst:22
msgid "Godot doesn't allow exporting read-only members."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0103.rst:45
msgid ""
"To fix a violation of this rule for fields, remove the ``readonly`` keyword "
"or remove the ``[Export]`` attribute."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0103.rst:48
msgid ""
"To fix a violation of this rule for properties, make sure the property "
"declares both a getter and a setter, or remove the ``[Export]`` attribute."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0103.rst:54
msgid ""
"Do not suppress a warning from this rule. Read-only members can't be "
"exported so they will be ignored by Godot, resulting in runtime errors."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0104.rst:2
msgid "GD0104: The exported property is write-only"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0104.rst:7
msgid "GD0104"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0104.rst:16
msgid ""
"A write-only property is annotated with the ``[Export]`` attribute. Write-"
"only properties can't be exported."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0104.rst:22
msgid "Godot doesn't allow exporting write-only properties."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0104.rst:39
msgid ""
"To fix a violation of this rule, make sure the property declares both a "
"getter and a setter, or remove the ``[Export]`` attribute."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0104.rst:45
msgid ""
"Do not suppress a warning from this rule. Write-only members can't be "
"exported so they will be ignored by Godot, resulting in runtime errors."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0105.rst:2
msgid "GD0105: Attempted to export indexer property"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0105.rst:7
msgid "GD0105"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0105.rst:16
msgid ""
"An indexer is annotated with the ``[Export]`` attribute. Indexers can't be "
"exported."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0105.rst:21
msgid "Godot doesn't allow exporting indexer properties."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0105.rst:38
msgid "To fix a violation of this rule, remove the ``[Export]`` attribute."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0105.rst:43
msgid ""
"Do not suppress a warning from this rule. Indexers can't be exported so they "
"will be ignored by Godot, resulting in runtime errors."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0106.rst:2
msgid "GD0106: Attempted to export explicit interface property implementation"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0106.rst:7
msgid "GD0106"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0106.rst:16
msgid ""
"An explicit interface property implementation is annotated with the "
"``[Export]`` attribute. Properties that implement an interface explicitly "
"can't be exported."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0106.rst:22
msgid ""
"Godot doesn't allow exporting explicit interface property implementations. "
"When an interface member is implemented explicitly, the member is hidden and "
"consumers can't access them unless the type is converted to the interface "
"first. Explicitly implemented members can also share the same name of other "
"members in the type, so it could create naming conflicts with other exported "
"members."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0106.rst:52
msgid ""
"To fix a violation of this rule, implement the interface implicitly or "
"remove the ``[Export]`` attribute."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0106.rst:58
msgid ""
"Do not suppress a warning from this rule. Explicit interface property "
"implementations can't be exported so they will be ignored by Godot, "
"resulting in runtime errors."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0107.rst:2
msgid "GD0107: Types not derived from Node should not export Node members"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0107.rst:7
msgid "GD0107"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0107.rst:9
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0201.rst:9
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0301.rst:9
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0302.rst:9
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0402.rst:9
#, fuzzy
msgid "Breaking"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0107.rst:16
msgid ""
"A type that doesn't derive from ``Node`` contains an exported field or "
"property of a type that derives from ``Node``."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0107.rst:22
msgid ""
"Exported nodes are serialized as ``NodePath``. Only types derived from "
"``Node`` are able to get the node instance from the ``NodePath``."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0107.rst:28
msgid ""
"To fix a violation of this rule, avoid exporting ``Node`` members on a type "
"that doesn't derive from ``Node``, or consider exporting a ``NodePath``."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0107.rst:34
msgid ""
"Do not suppress a warning from this rule. Types that don't derive from "
"``Node`` will be unable to retrieve the right node instance for exported "
"``Node`` members, resulting in unexpected runtime errors."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0201.rst:2
msgid "GD0201: The name of the delegate must end with 'EventHandler'"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0201.rst:7
msgid "GD0201"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0201.rst:16
msgid ""
"A delegate annotated with the ``[Signal]`` attribute has a name that doesn't "
"end with 'EventHandler'."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0201.rst:22
msgid ""
"Godot source generators will generate C# events using the name of the "
"delegate with the 'EventHandler' suffix removed. Adding the 'EventHandler' "
"suffix to the name of delegates used in events is a `.NET naming convention "
"<https://learn.microsoft.com/en-us/dotnet/standard/design-guidelines/names-"
"of-classes-structs-and-interfaces#names-of-common-types>`_."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0201.rst:26
msgid ""
"Using a suffix for the delegate allows the generated event to use the name "
"without the suffix avoiding a naming conflict."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0201.rst:39
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0202.rst:39
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0203.rst:36
msgid ""
"Take a look at the :ref:`C# signals <doc_c_sharp_signals>` documentation for "
"more information about how to declare and use signals."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0201.rst:45
msgid ""
"To fix a violation of this rule, add 'EventHandler' to the end of the "
"delegate name."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0201.rst:50
msgid ""
"Do not suppress a warning from this rule. Signal delegates without the "
"suffix will be ignored by the source generator, so the signal won't be "
"registered."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0202.rst:2
msgid ""
"GD0202: The parameter of the delegate signature of the signal is not "
"supported"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0202.rst:7
msgid "GD0202"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0202.rst:9
msgid "Breaking - If the parameter type is changed"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0202.rst:11
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0203.rst:11
msgid "Non-breaking - If the ``[Signal]`` attribute is removed"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0202.rst:18
msgid ""
"An unsupported type is specified for a parameter of a delegate annotated "
"with the ``[Signal]`` attribute when a :ref:`Variant-compatible "
"<doc_c_sharp_variant>` type is expected."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0202.rst:25
msgid ""
"Every signal parameter must be Variant-compatible so it can be marshalled "
"when emitting the signal and invoking the callbacks."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0202.rst:45
msgid ""
"To fix a violation of this rule, change the parameter type to be Variant-"
"compatible or remove the ``[Signal]`` attribute from the delegate. Note that "
"removing the attribute will mean the signal is not registered."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0202.rst:51
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0203.rst:48
msgid ""
"If the signal doesn't need to interact with Godot, consider using `C# events "
"<https://learn.microsoft.com/en-us/dotnet/csharp/programming-guide/events/"
">`_ directly. Pure C# events allow you to use any C# type for its parameters."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0202.rst:58
msgid ""
"Do not suppress a warning from this rule. Signal delegates with parameters "
"that can't be marshalled will result in runtime errors when emitting the "
"signal or invoking the callbacks."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0203.rst:2
msgid "GD0203: The delegate signature of the signal must return void"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0203.rst:7
msgid "GD0203"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0203.rst:9
msgid "Breaking - If the return type is changed"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0203.rst:18
msgid ""
"A delegate annotated with the ``[Signal]`` attribute has a return type when "
"``void`` was expected."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0203.rst:24
msgid ""
"Every signal must return ``void``. There can be multiple callbacks "
"registered for each signal, if signal callbacks could return something it "
"wouldn't be possible to determine which of the returned values to use."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0203.rst:42
msgid ""
"To fix a violation of this rule, change the delegate to return ``void`` or "
"remove the ``[Signal]`` attribute from the delegate. Note that removing the "
"attribute will mean the signal is not registered."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0203.rst:55
msgid ""
"Do not suppress a warning from this rule. Signal delegates that return "
"something will result in unexpected runtime errors."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0301.rst:2
msgid "GD0301: The generic type argument must be a Variant compatible type"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0301.rst:7
msgid "GD0301"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0301.rst:16
msgid ""
"An unsupported type is specified for a generic type argument when a :ref:"
"`Variant-compatible <doc_c_sharp_variant>` type is expected."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0301.rst:22
msgid ""
"When a generic type parameter is annotated with the ``[MustBeVariant]`` "
"attribute, the generic type is required to be a Variant-compatible type. For "
"example, the generic ``Godot.Collections.Array<T>`` type only supports items "
"of a type that can be converted to Variant."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0301.rst:41
msgid ""
"To fix a violation of this rule, change the generic type argument to be a "
"Variant-compatible type or use a different API that doesn't require the "
"generic type argument to be a Variant-compatible type."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0301.rst:48
#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0302.rst:54
msgid ""
"Do not suppress a warning from this rule. API that contains generic type "
"arguments annotated with the ``[MustBeVariant]`` attribute usually has this "
"requirement because the values will be passed to the engine, if the type "
"can't be marshalled it will result in runtime errors."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0302.rst:2
msgid ""
"GD0302: The generic type parameter must be annotated with the MustBeVariant "
"attribute"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0302.rst:7
msgid "GD0302"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0302.rst:16
msgid ""
"A generic type is specified for a generic type argument when a :ref:`Variant-"
"compatible <doc_c_sharp_variant>` type is expected, but the specified "
"generic type is not annotated with the ``[MustBeVariant]`` attribute."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0302.rst:23
msgid ""
"When a generic type parameter is annotated with the ``[MustBeVariant]`` "
"attribute, the generic type is required to be a Variant-compatible type. "
"When the type used is also a generic type, this generic type must be "
"annotated with the ``[MustBeVariant]`` attribute as well. For example, the "
"generic ``Godot.Collections.Array<T>`` type only supports items of a type "
"that can be converted to Variant, a generic type can be specified if it's "
"properly annotated."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0302.rst:48
msgid ""
"To fix a violation of this rule, add the ``[MustBeVariant]`` attribute to "
"the generic type that is used as a generic type argument that must be "
"Variant-compatible."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0303.rst:2
msgid ""
"GD0303: Symbol parent of a type argument that must be Variant compatible was "
"not handled"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0303.rst:7
msgid "GD0303"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0303.rst:9
msgid "Not fixable"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0303.rst:16
msgid "This is a bug in the engine and must be reported."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0303.rst:21
msgid ""
"The ``MustBeVariantAnalyzer`` has found an unhandled case in the user source "
"code. Please, open an `issue <https://github.com/godotengine/godot/issues>`_ "
"and attach a minimal reproduction project so it can be fixed."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0303.rst:29
msgid "Violations of this rule can't be fixed."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0303.rst:34
msgid ""
"Suppressing a warning from this rule may result in unexpected errors, since "
"the case found by the analyzer may need to be handled by the user to prevent "
"types that are not Variant-compatible from reaching the engine. Attempting "
"to marshal incompatible types will result in runtime errors."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0401.rst:2
msgid "GD0401: The class must derive from GodotObject or a derived class"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0401.rst:7
msgid "GD0401"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0401.rst:9
msgid "Breaking - If changing the inheritance chain"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0401.rst:11
msgid "Non-breaking - If removing the ``[GlobalClass]`` attribute"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0401.rst:18
msgid ""
"A type annotated with the ``[GlobalClass]`` attribute does not derive from "
"``GodotObject``."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0401.rst:24
msgid ""
"The ``[GlobalClass]`` has no effect for types that don't derive from "
"``GodotObject``. Every :ref:`global class <doc_c_sharp_global_classes>` must "
"ultimately derive from ``GodotObject`` so it can be marshalled."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0401.rst:47
msgid ""
"To fix a violation of this rule, change the type to derive from "
"``GodotObject`` or remove the ``[GlobalClass]`` attribute."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0401.rst:53
msgid ""
"Do not suppress a warning from this rule. Adding the ``[GlobalClass]`` to a "
"type that doesn't derive from ``GodotObject`` is an easy mistake to make and "
"this warning helps users realize that it may result in unexpected errors."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0402.rst:2
msgid "GD0402: The class must not contain generic arguments"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0402.rst:7
msgid "GD0402"
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0402.rst:16
msgid "A generic type is annotated with the ``[GlobalClass]`` attribute."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0402.rst:21
msgid ""
"The Godot editor assumes every :ref:`global class "
"<doc_c_sharp_global_classes>` is instantiable, but generic types can't be "
"instantiated because the type arguments are unbound."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0402.rst:38
msgid ""
"To fix a violation of this rule, change the type to remove the generic type "
"parameters or remove the ``[GlobalClass]`` attribute."
msgstr ""

#: ../../docs/tutorials/scripting/c_sharp/diagnostics/GD0402.rst:44
msgid ""
"Do not suppress a warning from this rule. Adding the ``[GlobalClass]`` to a "
"generic type is an easy mistake to make and this warning helps users realize "
"that it may result in unexpected errors."
msgstr ""

#: ../../docs/tutorials/scripting/gdextension/index.rst:2
#: ../../docs/contributing/development/compiling/compiling_for_web.rst:69
msgid "GDExtension"
msgstr ""

#: ../../docs/tutorials/scripting/gdextension/what_is_gdextension.rst:4
msgid "What is GDExtension?"
msgstr ""

#: ../../docs/tutorials/scripting/gdextension/what_is_gdextension.rst:9
msgid ""
"**GDExtension** is a Godot-specific technology that lets the engine interact "
"with native `shared libraries <https://en.wikipedia.org/wiki/"
"Library_(computing)#Shared_libraries>`__ at run-time. You can use it to run "
"native code without compiling it with the engine."
msgstr ""

#: ../../docs/tutorials/scripting/gdextension/what_is_gdextension.rst:13
msgid ""
"GDExtension is *not* a scripting language and has no relation to :ref:"
"`GDScript <doc_gdscript>`."
msgstr ""

#: ../../docs/tutorials/scripting/gdextension/what_is_gdextension.rst:17
msgid "Differences between GDExtension and C++ modules"
msgstr ""

#: ../../docs/tutorials/scripting/gdextension/what_is_gdextension.rst:19
msgid ""
"You can use both GDExtension and :ref:`C++ modules "
"<doc_custom_modules_in_cpp>` to run C or C++ code in a Godot project."
msgstr ""

#: ../../docs/tutorials/scripting/gdextension/what_is_gdextension.rst:22
msgid ""
"They also both allow you to integrate third-party libraries into Godot. The "
"one you should choose depends on your needs."
msgstr ""

#: ../../docs/tutorials/scripting/gdextension/what_is_gdextension.rst:27
#: ../../docs/tutorials/scripting/gdextension/gdextension_cpp_example.rst:45
msgid ""
"Our long-term goal is that GDExtensions targeting an earlier version of "
"Godot will work in later minor versions, but not vice-versa. For example, a "
"GDExtension targeting Godot 4.2 should work just fine in Godot 4.3, but one "
"targeting Godot 4.3 won't work in Godot 4.2."
msgstr ""

#: ../../docs/tutorials/scripting/gdextension/what_is_gdextension.rst:32
#: ../../docs/tutorials/scripting/gdextension/gdextension_cpp_example.rst:49
msgid ""
"However, GDExtension is currently *experimental*, which means that we may "
"break compatibility in order to fix major bugs or include critical features. "
"For example, GDExtensions created for Godot 4.0 aren't compatible with Godot "
"4.1 (see :ref:`updating_your_gdextension_for_godot_4_1`)."
msgstr ""

#: ../../docs/tutorials/scripting/gdextension/what_is_gdextension.rst:38
msgid "Advantages of GDExtension"
msgstr ""

#: ../../docs/tutorials/scripting/gdextension/what_is_gdextension.rst:40
msgid ""
"Unlike modules, GDExtension doesn't require compiling the engine's source "
"code, making it easier to distribute your work. It gives you access to most "
"of the API available to GDScript and C#, allowing you to code game logic "
"with full control regarding performance. It's ideal if you need high-"
"performance code you'd like to distribute as an add-on in the :ref:`asset "
"library <doc_what_is_assetlib>`."
msgstr ""

#: ../../docs/tutorials/scripting/gdextension/what_is_gdextension.rst:46
msgid "Also:"
msgstr ""

#: ../../docs/tutorials/scripting/gdextension/what_is_gdextension.rst:48
msgid ""
"GDExtension is not limited to C and C++. Thanks to :ref:`third-party "
"bindings <doc_what_is_gdnative_third_party_bindings>`, you can use it with "
"many other languages."
msgstr ""

#: ../../docs/tutorials/scripting/gdextension/what_is_gdextension.rst:51
msgid ""
"You can use the same compiled GDExtension library in the editor and exported "
"project. With C++ modules, you have to recompile all the export templates "
"you plan to use if you require its functionality at run-time."
msgstr ""

#: ../../docs/tutorials/scripting/gdextension/what_is_gdextension.rst:54
msgid ""
"GDExtension only requires you to compile your library, not the whole engine. "
"That's unlike C++ modules, which are statically compiled into the engine. "
"Every time you change a module, you need to recompile the engine. Even with "
"incremental builds, this process is slower than using GDExtension."
msgstr ""

#: ../../docs/tutorials/scripting/gdextension/what_is_gdextension.rst:60
msgid "Advantages of C++ modules"
msgstr ""

#: ../../docs/tutorials/scripting/gdextension/what_is_gdextension.rst:62
msgid ""
"We recommend :ref:`C++ modules <doc_custom_modules_in_cpp>` in cases where "
"GDExtension isn't enough:"
msgstr ""

#: ../../docs/tutorials/scripting/gdextension/what_is_gdextension.rst:65
msgid ""
"C++ modules provide deeper integration into the engine. GDExtension's access "
"is not as deep as static modules."
msgstr ""

#: ../../docs/tutorials/scripting/gdextension/what_is_gdextension.rst:67
msgid ""
"You can use C++ modules to provide additional features in a project without "
"carrying native library files around. This extends to exported projects."
msgstr ""

#: ../../docs/tutorials/scripting/gdextension/what_is_gdextension.rst:72
msgid ""
"If you notice that specific systems are not accessible via GDExtension but "
"are via custom modules, feel free to open an issue on the `godot-cpp "
"repository <https://github.com/godotengine/godot-cpp>`__ to discuss "
"implementation options for exposing the missing functionality."
msgstr ""

#: ../../docs/tutorials/scripting/gdextension/what_is_gdextension.rst:78
msgid "Supported languages"
msgstr ""

#: ../../docs/tutorials/scripting/gdextension/what_is_gdextension.rst:80
msgid ""
"The Godot developers officially support the following language bindings for "
"GDExtension:"
msgstr ""

#: ../../docs/tutorials/scripting/gdextension/what_is_gdextension.rst:83
#, fuzzy
msgid "C++ :ref:`(tutorial) <doc_gdextension_cpp_example>`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/scripting/gdextension/what_is_gdextension.rst:87
msgid ""
"There are no plans to support additional languages with GDExtension "
"officially. That said, the community offers several bindings for other "
"languages (see below)."
msgstr ""

#: ../../docs/tutorials/scripting/gdextension/what_is_gdextension.rst:93
msgid "The bindings below are developed and maintained by the community:"
msgstr ""

#: ../../docs/tutorials/scripting/gdextension/what_is_gdextension.rst:98
#, fuzzy
msgid "`D <https://github.com/godot-dlang/godot-dlang>`__"
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati raznorazne `Godot demo projects "
"<https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/tutorials/scripting/gdextension/what_is_gdextension.rst:99
#, fuzzy
msgid "`Go <https://github.com/grow-graphics/gd>`__"
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati raznorazne `Godot demo projects "
"<https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/tutorials/scripting/gdextension/what_is_gdextension.rst:100
#, fuzzy
msgid "`Haxe <https://hxgodot.github.io/>`__"
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati raznorazne `Godot demo projects "
"<https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/tutorials/scripting/gdextension/what_is_gdextension.rst:101
#, fuzzy
msgid "`Rust <https://github.com/godot-rust/gdext>`__"
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati raznorazne `Godot demo projects "
"<https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/tutorials/scripting/gdextension/what_is_gdextension.rst:102
#, fuzzy
msgid "`Swift <https://github.com/migueldeicaza/SwiftGodot>`__"
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati raznorazne `Godot demo projects "
"<https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/tutorials/scripting/gdextension/what_is_gdextension.rst:106
msgid ""
"Not all bindings mentioned here may be production-ready. Make sure to "
"research options thoroughly before starting a project with one of those. "
"Also, double-check whether the binding is compatible with the Godot version "
"you're using."
msgstr ""

#: ../../docs/tutorials/scripting/gdextension/what_is_gdextension.rst:112
msgid "Version compatibility"
msgstr ""

#: ../../docs/tutorials/scripting/gdextension/what_is_gdextension.rst:114
msgid ""
"GDExtension add-ons compiled for a given Godot version are only guaranteed "
"to work with the same minor release series. For example, a GDExtension add-"
"on compiled for Godot 4.0 will only work with Godot 4.0, 4.0.1, 4.0.2. In "
"addition, GDExtension is not compatible with Godot 3.x."
msgstr ""

#: ../../docs/tutorials/scripting/gdextension/what_is_gdextension.rst:119
msgid ""
"GDExtension add-ons are also only compatible with engine builds that use the "
"level of floating-point precision the extension was compiled for. This means "
"that if you use a engine build with double-precision floats, the extension "
"must also be compiled for double-precision floats. See :ref:"
"`doc_large_world_coordinates` for details."
msgstr ""

#: ../../docs/tutorials/scripting/gdextension/gdextension_cpp_example.rst:4
msgid "GDExtension C++ example"
msgstr ""

#: ../../docs/tutorials/scripting/gdextension/gdextension_cpp_example.rst:9
msgid ""
"The C++ bindings for GDExtension are built on top of the C GDExtension API "
"and provide a nicer way to \"extend\" nodes and other built-in classes in "
"Godot using C++. This new system allows the extension of Godot to nearly the "
"same level as statically linked C++ modules."
msgstr ""

#: ../../docs/tutorials/scripting/gdextension/gdextension_cpp_example.rst:14
#, fuzzy
msgid ""
"You can download the included example in the test folder of the godot-cpp "
"repository `on GitHub <https://github.com/godotengine/godot-cpp>`__."
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati raznorazne `Godot demo projects "
"<https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/tutorials/scripting/gdextension/gdextension_cpp_example.rst:20
msgid "There are a few prerequisites you'll need:"
msgstr ""

#: ../../docs/tutorials/scripting/gdextension/gdextension_cpp_example.rst:22
msgid "a Godot 4 executable,"
msgstr ""

#: ../../docs/tutorials/scripting/gdextension/gdextension_cpp_example.rst:23
msgid "a C++ compiler,"
msgstr ""

#: ../../docs/tutorials/scripting/gdextension/gdextension_cpp_example.rst:24
msgid "SCons as a build tool,"
msgstr ""

#: ../../docs/tutorials/scripting/gdextension/gdextension_cpp_example.rst:25
#, fuzzy
msgid ""
"a copy of the `godot-cpp repository <https://github.com/godotengine/godot-"
"cpp>`__."
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati raznorazne `Godot demo projects "
"<https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/tutorials/scripting/gdextension/gdextension_cpp_example.rst:28
msgid ""
"See also :ref:`Compiling <toc-devel-compiling>` as the build tools are "
"identical to the ones you need to compile Godot from source."
msgstr ""

#: ../../docs/tutorials/scripting/gdextension/gdextension_cpp_example.rst:31
msgid ""
"You can download the `godot-cpp repository <https://github.com/godotengine/"
"godot-cpp>`__ from GitHub or let Git do the work for you. Note that this "
"repository has different branches for different versions of Godot. "
"GDExtensions will not work in older versions of Godot (only Godot 4 and up) "
"and vice versa, so make sure you download the correct branch."
msgstr ""

#: ../../docs/tutorials/scripting/gdextension/gdextension_cpp_example.rst:36
msgid ""
"To use `GDExtension <https://godotengine.org/article/introducing-gd-"
"extensions>`__ you need to use the godot-cpp branch that matches the version "
"of Godot that you are targeting. For example, if you're targeting Godot 4.1, "
"use the ``4.1`` branch, which is what is shown through out this tutorial."
msgstr ""

#: ../../docs/tutorials/scripting/gdextension/gdextension_cpp_example.rst:41
msgid ""
"The ``master`` branch is the development branch which is updated regularly "
"to work with Godot's ``master`` branch."
msgstr ""

#: ../../docs/tutorials/scripting/gdextension/gdextension_cpp_example.rst:54
msgid ""
"If you are versioning your project using Git, it is recommended to add it as "
"a Git submodule:"
msgstr ""

#: ../../docs/tutorials/scripting/gdextension/gdextension_cpp_example.rst:66
msgid "Alternatively, you can also clone it to the project folder:"
msgstr ""

#: ../../docs/tutorials/scripting/gdextension/gdextension_cpp_example.rst:76
msgid ""
"If you decide to download the repository or clone it into your folder, make "
"sure to keep the folder layout the same as we've setup here. Much of the "
"code we'll be showcasing here assumes the project has this layout."
msgstr ""

#: ../../docs/tutorials/scripting/gdextension/gdextension_cpp_example.rst:80
msgid ""
"If you cloned the example from the link specified in the introduction, the "
"submodules are not automatically initialized. You will need to execute the "
"following commands:"
msgstr ""

#: ../../docs/tutorials/scripting/gdextension/gdextension_cpp_example.rst:89
msgid "This will initialize the repository in your project folder."
msgstr ""

#: ../../docs/tutorials/scripting/gdextension/gdextension_cpp_example.rst:92
msgid "Building the C++ bindings"
msgstr ""

#: ../../docs/tutorials/scripting/gdextension/gdextension_cpp_example.rst:94
msgid ""
"Now that we've downloaded our prerequisites, it is time to build the C++ "
"bindings."
msgstr ""

#: ../../docs/tutorials/scripting/gdextension/gdextension_cpp_example.rst:97
msgid ""
"The repository contains a copy of the metadata for the current Godot "
"release, but if you need to build these bindings for a newer version of "
"Godot, simply call the Godot executable:"
msgstr ""

#: ../../docs/tutorials/scripting/gdextension/gdextension_cpp_example.rst:105
msgid ""
"The resulting ``extension_api.json`` file will be created in the "
"executable's directory. Copy it to the project folder and add "
"``custom_api_file=<PATH_TO_FILE>`` to the scons command below."
msgstr ""

#: ../../docs/tutorials/scripting/gdextension/gdextension_cpp_example.rst:109
msgid ""
"To generate and compile the bindings, use this command (replacing "
"``<platform>`` with ``windows``, ``linux`` or ``macos`` depending on your "
"OS):"
msgstr ""

#: ../../docs/tutorials/scripting/gdextension/gdextension_cpp_example.rst:112
msgid ""
"The build process automatically detects the number of CPU threads to use for "
"parallel builds. To specify a number of CPU threads to use, add ``-jN`` at "
"the end of the SCons command line where ``N`` is the number of CPU threads "
"to use."
msgstr ""

#: ../../docs/tutorials/scripting/gdextension/gdextension_cpp_example.rst:122
msgid ""
"This step will take a while. When it is completed, you should have static "
"libraries that can be compiled into your project stored in ``godot-cpp/bin/"
"``."
msgstr ""

#: ../../docs/tutorials/scripting/gdextension/gdextension_cpp_example.rst:127
msgid "You may need to add ``bits=64`` to the command on Windows or Linux."
msgstr ""

#: ../../docs/tutorials/scripting/gdextension/gdextension_cpp_example.rst:130
msgid "Creating a simple plugin"
msgstr ""

#: ../../docs/tutorials/scripting/gdextension/gdextension_cpp_example.rst:132
msgid ""
"Now it's time to build an actual plugin. We'll start by creating an empty "
"Godot project in which we'll place a few files."
msgstr ""

#: ../../docs/tutorials/scripting/gdextension/gdextension_cpp_example.rst:135
msgid ""
"Open Godot and create a new project. For this example, we will place it in a "
"folder called ``demo`` inside our GDExtension's folder structure."
msgstr ""

#: ../../docs/tutorials/scripting/gdextension/gdextension_cpp_example.rst:138
msgid ""
"In our demo project, we'll create a scene containing a Node called \"Main\" "
"and we'll save it as ``main.tscn``. We'll come back to that later."
msgstr ""

#: ../../docs/tutorials/scripting/gdextension/gdextension_cpp_example.rst:141
msgid ""
"Back in the top-level GDExtension module folder, we're also going to create "
"a subfolder called ``src`` in which we'll place our source files."
msgstr ""

#: ../../docs/tutorials/scripting/gdextension/gdextension_cpp_example.rst:144
msgid ""
"You should now have ``demo``, ``godot-cpp``, and ``src`` directories in your "
"GDExtension module."
msgstr ""

#: ../../docs/tutorials/scripting/gdextension/gdextension_cpp_example.rst:147
msgid "Your folder structure should now look like this:"
msgstr ""

#: ../../docs/tutorials/scripting/gdextension/gdextension_cpp_example.rst:159
msgid ""
"In the ``src`` folder, we'll start with creating our header file for the "
"GDExtension node we'll be creating. We will name it ``gdexample.h``:"
msgstr ""

#: ../../docs/tutorials/scripting/gdextension/gdextension_cpp_example.rst:191
msgid ""
"There are a few things of note to the above. We include ``sprite2d.hpp`` "
"which contains bindings to the Sprite2D class. We'll be extending this class "
"in our module."
msgstr ""

#: ../../docs/tutorials/scripting/gdextension/gdextension_cpp_example.rst:195
msgid ""
"We're using the namespace ``godot``, since everything in GDExtension is "
"defined within this namespace."
msgstr ""

#: ../../docs/tutorials/scripting/gdextension/gdextension_cpp_example.rst:198
msgid ""
"Then we have our class definition, which inherits from our Sprite2D through "
"a container class. We'll see a few side effects of this later on. The "
"``GDCLASS`` macro sets up a few internal things for us."
msgstr ""

#: ../../docs/tutorials/scripting/gdextension/gdextension_cpp_example.rst:202
msgid "After that, we declare a single member variable called ``time_passed``."
msgstr ""

#: ../../docs/tutorials/scripting/gdextension/gdextension_cpp_example.rst:204
msgid ""
"In the next block we're defining our methods, we have our constructor and "
"destructor defined, but there are two other functions that will likely look "
"familiar to some, and one new method."
msgstr ""

#: ../../docs/tutorials/scripting/gdextension/gdextension_cpp_example.rst:208
msgid ""
"The first is ``_bind_methods``, which is a static function that Godot will "
"call to find out which methods can be called and which properties it "
"exposes. The second is our ``_process`` function, which will work exactly "
"the same as the ``_process`` function you're used to in GDScript."
msgstr ""

#: ../../docs/tutorials/scripting/gdextension/gdextension_cpp_example.rst:213
msgid "Let's implement our functions by creating our ``gdexample.cpp`` file:"
msgstr ""

#: ../../docs/tutorials/scripting/gdextension/gdextension_cpp_example.rst:242
msgid ""
"This one should be straightforward. We're implementing each method of our "
"class that we defined in our header file."
msgstr ""

#: ../../docs/tutorials/scripting/gdextension/gdextension_cpp_example.rst:245
msgid ""
"Note our ``_process`` function, which keeps track of how much time has "
"passed and calculates a new position for our sprite using a sine and cosine "
"function."
msgstr ""

#: ../../docs/tutorials/scripting/gdextension/gdextension_cpp_example.rst:248
msgid ""
"There is one more C++ file we need; we'll name it ``register_types.cpp``. "
"Our GDExtension plugin can contain multiple classes, each with their own "
"header and source file like we've implemented ``GDExample`` up above. What "
"we need now is a small bit of code that tells Godot about all the classes in "
"our GDExtension plugin."
msgstr ""

#: ../../docs/tutorials/scripting/gdextension/gdextension_cpp_example.rst:293
msgid ""
"The ``initialize_example_module`` and ``uninitialize_example_module`` "
"functions get called respectively when Godot loads our plugin and when it "
"unloads it. All we're doing here is parse through the functions in our "
"bindings module to initialize them, but you might have to set up more things "
"depending on your needs. We call the function ``register_class`` for each of "
"our classes in our library."
msgstr ""

#: ../../docs/tutorials/scripting/gdextension/gdextension_cpp_example.rst:299
msgid ""
"The important function is the third function called "
"``example_library_init``. We first call a function in our bindings library "
"that creates an initialization object. This object registers the "
"initialization and termination functions of the GDExtension. Furthermore, it "
"sets the level of initialization (core, servers, scene, editor, level)."
msgstr ""

#: ../../docs/tutorials/scripting/gdextension/gdextension_cpp_example.rst:304
msgid ""
"At last, we need the header file for the ``register_types.cpp`` named "
"``register_types.h``."
msgstr ""

#: ../../docs/tutorials/scripting/gdextension/gdextension_cpp_example.rst:323
msgid "Compiling the plugin"
msgstr ""

#: ../../docs/tutorials/scripting/gdextension/gdextension_cpp_example.rst:325
msgid ""
"We cannot easily write by hand a ``SConstruct`` file that SCons would use "
"for building. For the purpose of this example, just use :download:`this "
"hardcoded SConstruct file <files/cpp_example/SConstruct>` we've prepared. "
"We'll cover a more customizable, detailed example on how to use these build "
"files in a subsequent tutorial."
msgstr ""

#: ../../docs/tutorials/scripting/gdextension/gdextension_cpp_example.rst:333
msgid ""
"This ``SConstruct`` file was written to be used with the latest ``godot-"
"cpp`` master, you may need to make small changes using it with older "
"versions or refer to the ``SConstruct`` file in the Godot 4.0 documentation."
msgstr ""

#: ../../docs/tutorials/scripting/gdextension/gdextension_cpp_example.rst:337
msgid ""
"Once you've downloaded the ``SConstruct`` file, place it in your GDExtension "
"folder structure alongside ``godot-cpp``, ``src`` and ``demo``, then run:"
msgstr ""

#: ../../docs/tutorials/scripting/gdextension/gdextension_cpp_example.rst:344
msgid "You should now be able to find the module in ``demo/bin/<platform>``."
msgstr ""

#: ../../docs/tutorials/scripting/gdextension/gdextension_cpp_example.rst:348
msgid ""
"Here, we've compiled both godot-cpp and our gdexample library as debug "
"builds. For optimized builds, you should compile them using the "
"``target=template_release`` switch."
msgstr ""

#: ../../docs/tutorials/scripting/gdextension/gdextension_cpp_example.rst:353
#, fuzzy
msgid "Using the GDExtension module"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/scripting/gdextension/gdextension_cpp_example.rst:355
msgid ""
"Before we jump back into Godot, we need to create one more file in ``demo/"
"bin/``."
msgstr ""

#: ../../docs/tutorials/scripting/gdextension/gdextension_cpp_example.rst:358
msgid ""
"This file lets Godot know what dynamic libraries should be loaded for each "
"platform and the entry function for the module. It is called ``gdexample."
"gdextension``."
msgstr ""

#: ../../docs/tutorials/scripting/gdextension/gdextension_cpp_example.rst:387
msgid ""
"This file contains a ``configuration`` section that controls the entry "
"function of the module. You should also set the minimum compatible Godot "
"version with ``compatability_minimum``, which prevents older version of "
"Godot from trying to load your extension."
msgstr ""

#: ../../docs/tutorials/scripting/gdextension/gdextension_cpp_example.rst:391
msgid ""
"The ``libraries`` section is the important bit: it tells Godot the location "
"of the dynamic library in the project's filesystem for each supported "
"platform. It will also result in *just* that file being exported when you "
"export the project, which means the data pack won't contain libraries that "
"are incompatible with the target platform."
msgstr ""

#: ../../docs/tutorials/scripting/gdextension/gdextension_cpp_example.rst:397
msgid ""
"Finally, the ``dependencies`` section allows you to name additional dynamic "
"libraries that should be included as well. This is important when your "
"GDExtension plugin implements someone else's library and requires you to "
"supply a third-party dynamic library with your project."
msgstr ""

#: ../../docs/tutorials/scripting/gdextension/gdextension_cpp_example.rst:402
msgid "Here is another overview to check the correct file structure:"
msgstr ""

#: ../../docs/tutorials/scripting/gdextension/gdextension_cpp_example.rst:425
msgid ""
"Time to jump back into Godot. We load up the main scene we created way back "
"in the beginning and now add a newly available GDExample node to the scene:"
msgstr ""

#: ../../docs/tutorials/scripting/gdextension/gdextension_cpp_example.rst:430
msgid ""
"We're going to assign the Godot logo to this node as our texture, disable "
"the ``centered`` property:"
msgstr ""

#: ../../docs/tutorials/scripting/gdextension/gdextension_cpp_example.rst:435
msgid "We're finally ready to run the project:"
msgstr ""

#: ../../docs/tutorials/scripting/gdextension/gdextension_cpp_example.rst:440
#, fuzzy
msgid "Custom editor icon"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/scripting/gdextension/gdextension_cpp_example.rst:441
msgid ""
"By default, Godot uses the node icon in the scene dock for GDExtension "
"nodes. The custom icon can be added via the ``gdextension`` file. The node's "
"icon is set by reference to its name and resource path of an SVG file."
msgstr ""

#: ../../docs/tutorials/scripting/gdextension/gdextension_cpp_example.rst:445
#: ../../docs/tutorials/scripting/creating_script_templates.rst:72
#: ../../docs/contributing/development/core_and_modules/object_class.rst:143
#: ../../docs/contributing/documentation/class_reference_primer.rst:223
msgid "For example:"
msgstr ""

#: ../../docs/tutorials/scripting/gdextension/gdextension_cpp_example.rst:453
msgid ""
"The path should point to a 16 by 16 pixel SVG image. Read the guide for :ref:"
"`creating icons <doc_editor_icons>` for more information."
msgstr ""

#: ../../docs/tutorials/scripting/gdextension/gdextension_cpp_example.rst:457
msgid "Adding properties"
msgstr ""

#: ../../docs/tutorials/scripting/gdextension/gdextension_cpp_example.rst:459
msgid ""
"GDScript allows you to add properties to your script using the ``export`` "
"keyword. In GDExtension you have to register the properties with a getter "
"and setter function or directly implement the ``_get_property_list``, "
"``_get`` and ``_set`` methods of an object (but that goes far beyond the "
"scope of this tutorial)."
msgstr ""

#: ../../docs/tutorials/scripting/gdextension/gdextension_cpp_example.rst:465
msgid ""
"Lets add a property that allows us to control the amplitude of our wave."
msgstr ""

#: ../../docs/tutorials/scripting/gdextension/gdextension_cpp_example.rst:467
msgid ""
"In our ``gdexample.h`` file we need to add a member variable and getter and "
"setter functions:"
msgstr ""

#: ../../docs/tutorials/scripting/gdextension/gdextension_cpp_example.rst:482
msgid ""
"In our ``gdexample.cpp`` file we need to make a number of changes, we will "
"only show the methods we end up changing, don't remove the lines we're "
"omitting:"
msgstr ""

#: ../../docs/tutorials/scripting/gdextension/gdextension_cpp_example.rst:518
msgid ""
"Once you compile the module with these changes in place, you will see that a "
"property has been added to our interface. You can now change this property "
"and when you run your project, you will see that our Godot icon travels "
"along a larger figure."
msgstr ""

#: ../../docs/tutorials/scripting/gdextension/gdextension_cpp_example.rst:523
msgid ""
"Let's do the same but for the speed of our animation and use a setter and "
"getter function. Our ``gdexample.h`` header file again only needs a few more "
"lines of code:"
msgstr ""

#: ../../docs/tutorials/scripting/gdextension/gdextension_cpp_example.rst:538
msgid ""
"This requires a few more changes to our ``gdexample.cpp`` file, again we're "
"only showing the methods that have changed so don't remove anything we're "
"omitting:"
msgstr ""

#: ../../docs/tutorials/scripting/gdextension/gdextension_cpp_example.rst:577
msgid ""
"Now when the project is compiled, we'll see another property called speed. "
"Changing its value will make the animation go faster or slower. Furthermore, "
"we added a property range which describes in which range the value can be. "
"The first two arguments are the minimum and maximum value and the third is "
"the step size."
msgstr ""

#: ../../docs/tutorials/scripting/gdextension/gdextension_cpp_example.rst:584
msgid ""
"For simplicity, we've only used the hint_range of the property method. There "
"are a lot more options to choose from. These can be used to further "
"configure how properties are displayed and set on the Godot side."
msgstr ""

#: ../../docs/tutorials/scripting/gdextension/gdextension_cpp_example.rst:591
msgid ""
"Last but not least, signals fully work in GDExtension as well. Having your "
"extension react to a signal given out by another object requires you to call "
"``connect`` on that object. We can't think of a good example for our "
"wobbling Godot icon, we would need to showcase a far more complete example."
msgstr ""

#: ../../docs/tutorials/scripting/gdextension/gdextension_cpp_example.rst:596
msgid "This is the required syntax:"
msgstr ""

#: ../../docs/tutorials/scripting/gdextension/gdextension_cpp_example.rst:602
msgid ""
"To connect our signal ``the_signal`` from some other node with our method "
"``my_method``, we need to provide the ``connect`` method with the name of "
"the signal and a ``Callable``. The ``Callable`` holds information about an "
"object on which a method can be called. In our case, it associates our "
"current object instance ``this`` with the method ``my_method`` of the "
"object. Then the ``connect`` method will add this to the observers of "
"``the_signal``. Whenever ``the_signal`` is now emitted, Godot knows which "
"method of which object it needs to call."
msgstr ""

#: ../../docs/tutorials/scripting/gdextension/gdextension_cpp_example.rst:610
msgid ""
"Note that you can only call ``my_method`` if you've previously registered it "
"in your ``_bind_methods`` method. Otherwise Godot will not know about the "
"existence of ``my_method``."
msgstr ""

#: ../../docs/tutorials/scripting/gdextension/gdextension_cpp_example.rst:614
msgid ""
"To learn more about ``Callable``, check out the class reference here: :ref:"
"`Callable <class_Callable>`."
msgstr ""

#: ../../docs/tutorials/scripting/gdextension/gdextension_cpp_example.rst:616
msgid ""
"Having your object sending out signals is more common. For our wobbling "
"Godot icon, we'll do something silly just to show how it works. We're going "
"to emit a signal every time a second has passed and pass the new location "
"along."
msgstr ""

#: ../../docs/tutorials/scripting/gdextension/gdextension_cpp_example.rst:620
msgid ""
"In our ``gdexample.h`` header file, we need to define a new member "
"``time_emit``:"
msgstr ""

#: ../../docs/tutorials/scripting/gdextension/gdextension_cpp_example.rst:630
msgid ""
"This time, the changes in ``gdexample.cpp`` are more elaborate. First, "
"you'll need to set ``time_emit = 0.0;`` in either our ``_init`` method or in "
"our constructor. We'll look at the other 2 needed changes one by one."
msgstr ""

#: ../../docs/tutorials/scripting/gdextension/gdextension_cpp_example.rst:634
msgid ""
"In our ``_bind_methods`` method, we need to declare our signal. This is done "
"as follows:"
msgstr ""

#: ../../docs/tutorials/scripting/gdextension/gdextension_cpp_example.rst:646
msgid ""
"Here, our ``ADD_SIGNAL`` macro can be a single call with a ``MethodInfo`` "
"argument. ``MethodInfo``'s first parameter will be the signal's name, and "
"its remaining parameters are ``PropertyInfo`` types which describe the "
"essentials of each of the method's parameters. ``PropertyInfo`` parameters "
"are defined with the data type of the parameter, and then the name that the "
"parameter will have by default."
msgstr ""

#: ../../docs/tutorials/scripting/gdextension/gdextension_cpp_example.rst:652
msgid ""
"So here, we add a signal, with a ``MethodInfo`` which names the signal "
"\"position_changed\". The ``PropertyInfo`` parameters describe two essential "
"arguments, one of type ``Object``, the other of type ``Vector2``, "
"respectively named \"node\" and \"new_pos\"."
msgstr ""

#: ../../docs/tutorials/scripting/gdextension/gdextension_cpp_example.rst:656
msgid "Next, we'll need to change our ``_process`` method:"
msgstr ""

#: ../../docs/tutorials/scripting/gdextension/gdextension_cpp_example.rst:678
msgid ""
"After a second has passed, we emit our signal and reset our counter. We can "
"add our parameter values directly to ``emit_signal``."
msgstr ""

#: ../../docs/tutorials/scripting/gdextension/gdextension_cpp_example.rst:681
msgid ""
"Once the GDExtension library is compiled, we can go into Godot and select "
"our sprite node. In the **Node** dock, we can find our new signal and link "
"it up by pressing the **Connect** button or double-clicking the signal. "
"We've added a script on our main node and implemented our signal like this:"
msgstr ""

#: ../../docs/tutorials/scripting/gdextension/gdextension_cpp_example.rst:693
msgid "Every second, we output our position to the console."
msgstr ""

#: ../../docs/tutorials/scripting/gdextension/gdextension_cpp_example.rst:698
msgid ""
"We hope the above example showed you the basics. You can build upon this "
"example to create full-fledged scripts to control nodes in Godot using C++."
msgstr ""

#: ../../docs/tutorials/scripting/how_to_read_the_godot_api.rst:4
msgid "How to read the Godot API"
msgstr ""

#: ../../docs/tutorials/scripting/how_to_read_the_godot_api.rst:6
msgid ""
"On this page, you'll learn how to read the class reference for the Godot API."
msgstr ""

#: ../../docs/tutorials/scripting/how_to_read_the_godot_api.rst:8
msgid ""
"The API, or Application Programming Interface, is an index of what Godot "
"offers users. It provides a brief summary of which classes exist, how they "
"are related to each other, what features they have, and how to use them."
msgstr ""

#: ../../docs/tutorials/scripting/how_to_read_the_godot_api.rst:17
msgid "At the top of each file, you will see the name of the class."
msgstr ""

#: ../../docs/tutorials/scripting/how_to_read_the_godot_api.rst:19
msgid ""
"The \"Inherits\" section lists each class the current one inherits. Here "
"``CanvasItem`` inherits ``Node`` and ``Node`` inherits ``Object``."
msgstr ""

#: ../../docs/tutorials/scripting/how_to_read_the_godot_api.rst:22
msgid ""
"The \"Inherited By\" section lists each class which directly inherits the "
"current class. Here ``Control`` and ``Node2D`` both inherit ``CanvasItem``."
msgstr ""

#: ../../docs/tutorials/scripting/how_to_read_the_godot_api.rst:26
#, fuzzy
msgid "Brief Description"
msgstr "Uvod"

#: ../../docs/tutorials/scripting/how_to_read_the_godot_api.rst:30
msgid ""
"Next a brief description of the class. This text appears in Godot Editor "
"popups for creating Nodes, Resources, and other types."
msgstr ""

#: ../../docs/tutorials/scripting/how_to_read_the_godot_api.rst:38
msgid ""
"Next a more detailed description the class, its features, and its use "
"case(s)."
msgstr ""

#: ../../docs/tutorials/scripting/how_to_read_the_godot_api.rst:40
msgid "Things you may find here:"
msgstr ""

#: ../../docs/tutorials/scripting/how_to_read_the_godot_api.rst:42
msgid "Specifics of how the class works."
msgstr ""

#: ../../docs/tutorials/scripting/how_to_read_the_godot_api.rst:44
msgid "Code samples of common use cases."
msgstr ""

#: ../../docs/tutorials/scripting/how_to_read_the_godot_api.rst:46
msgid "Usage details which are shared between each of the class's methods."
msgstr ""

#: ../../docs/tutorials/scripting/how_to_read_the_godot_api.rst:48
msgid "Warnings about required dependencies or configuration."
msgstr ""

#: ../../docs/tutorials/scripting/how_to_read_the_godot_api.rst:50
msgid "Links to other related parts of the Godot API."
msgstr ""

#: ../../docs/tutorials/scripting/how_to_read_the_godot_api.rst:53
#, fuzzy
msgid "Tutorials"
msgstr "Tutorijali"

#: ../../docs/tutorials/scripting/how_to_read_the_godot_api.rst:57
msgid ""
"The page then provides links to parts of the manual which mention or make "
"use of the current class."
msgstr ""

#: ../../docs/tutorials/scripting/how_to_read_the_godot_api.rst:65
msgid ""
"The Properties table lists the variables which belong to each instance of "
"the class, also known as the \"properties.\""
msgstr ""

#: ../../docs/tutorials/scripting/how_to_read_the_godot_api.rst:68
msgid ""
"The left column contains the data type of the property. The text is also a "
"link to that data type's Godot API page."
msgstr ""

#: ../../docs/tutorials/scripting/how_to_read_the_godot_api.rst:71
msgid ""
"The center column contains the name of the property. The text is also a link "
"to that property's full description on the page. Use this name to get the "
"property's data or set a new value to it."
msgstr ""

#: ../../docs/tutorials/scripting/how_to_read_the_godot_api.rst:75
msgid ""
"The right column contains the default value of the property. To initialize "
"it with a different value, you must set a different value via script or the "
"Inspector."
msgstr ""

#: ../../docs/tutorials/scripting/how_to_read_the_godot_api.rst:80
msgid "Methods"
msgstr ""

#: ../../docs/tutorials/scripting/how_to_read_the_godot_api.rst:84
msgid ""
"The Methods table lists the functions which belong to each instance of the "
"class, also known as the \"methods.\""
msgstr ""

#: ../../docs/tutorials/scripting/how_to_read_the_godot_api.rst:87
msgid "The left column contains the data type of the method's return value."
msgstr ""

#: ../../docs/tutorials/scripting/how_to_read_the_godot_api.rst:89
msgid ""
"The right column contains the name, parameters, and qualifiers of the "
"method. The name is the text before the opening parenthesis. It is also a "
"link to the method's full description on the page. Use this name to call the "
"method."
msgstr ""

#: ../../docs/tutorials/scripting/how_to_read_the_godot_api.rst:93
msgid ""
"For each parameter, the page details its data type, name, and default value, "
"if any."
msgstr ""

#: ../../docs/tutorials/scripting/how_to_read_the_godot_api.rst:96
msgid "Possible qualifiers include..."
msgstr ""

#: ../../docs/tutorials/scripting/how_to_read_the_godot_api.rst:98
msgid "``const``: the method does not change any data in the class instance."
msgstr ""

#: ../../docs/tutorials/scripting/how_to_read_the_godot_api.rst:99
msgid ""
"``virtual``: the method does nothing but wait for a script to override it."
msgstr ""

#: ../../docs/tutorials/scripting/how_to_read_the_godot_api.rst:100
msgid "``vararg``: the method can accept an arbitrary number of arguments."
msgstr ""

#: ../../docs/tutorials/scripting/how_to_read_the_godot_api.rst:107
msgid ""
"The Signals list details the names and parameters of events which \"signal\" "
"a change in game state to other class instances."
msgstr ""

#: ../../docs/tutorials/scripting/how_to_read_the_godot_api.rst:110
msgid ""
"Like the Methods table, any parameters will include their data type and name."
msgstr ""

#: ../../docs/tutorials/scripting/how_to_read_the_godot_api.rst:112
msgid ""
"Each signal also has a detailed explanation of when the signal is emitted."
msgstr ""

#: ../../docs/tutorials/scripting/how_to_read_the_godot_api.rst:115
#, fuzzy
msgid "Enumerations"
msgstr "Uvod"

#: ../../docs/tutorials/scripting/how_to_read_the_godot_api.rst:119
msgid ""
"The Enumerations list details the enumerable data types associated with the "
"current class."
msgstr ""

#: ../../docs/tutorials/scripting/how_to_read_the_godot_api.rst:122
msgid ""
"For each enumeration, the page states its name and then lists its possible "
"values."
msgstr ""

#: ../../docs/tutorials/scripting/how_to_read_the_godot_api.rst:125
msgid ""
"For each enumeration value, the page states its name, its integer value, and "
"an explanation of its use case(s) and/or affects."
msgstr ""

#: ../../docs/tutorials/scripting/how_to_read_the_godot_api.rst:133
msgid ""
"The Constants list details named integer constants in the current class."
msgstr ""

#: ../../docs/tutorials/scripting/how_to_read_the_godot_api.rst:135
msgid ""
"For each constant, the page states its name, its integer value, and an "
"explanation of its use case(s) and/or affects."
msgstr ""

#: ../../docs/tutorials/scripting/how_to_read_the_godot_api.rst:138
msgid ""
"``NOTIFICATION_*`` constants' descriptions will state which engine event "
"triggers the notification."
msgstr ""

#: ../../docs/tutorials/scripting/how_to_read_the_godot_api.rst:142
#, fuzzy
msgid "Property Descriptions"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/scripting/how_to_read_the_godot_api.rst:146
msgid "The Property Descriptions list details everything about each property."
msgstr ""

#: ../../docs/tutorials/scripting/how_to_read_the_godot_api.rst:148
msgid "It restates the data type and name of the property."
msgstr ""

#: ../../docs/tutorials/scripting/how_to_read_the_godot_api.rst:150
msgid ""
"Every property in the Godot API is bound to a pair of setter and getter "
"functions. Using either is equivalent. They are listed here."
msgstr ""

#: ../../docs/tutorials/scripting/how_to_read_the_godot_api.rst:153
msgid ""
"Below that is a detailed summary of what the property's data represents, its "
"use case(s) and/or the affects of changing it. It may include code samples "
"and/or links to relevant parts of the Godot API."
msgstr ""

#: ../../docs/tutorials/scripting/how_to_read_the_godot_api.rst:157
msgid ""
"Knowing the setter and getter names is useful when one must bind a method "
"name or :ref:`Callable<class_Callable>` to something."
msgstr ""

#: ../../docs/tutorials/scripting/how_to_read_the_godot_api.rst:161
#, fuzzy
msgid "Method Descriptions"
msgstr "Uvod"

#: ../../docs/tutorials/scripting/how_to_read_the_godot_api.rst:165
msgid "The Method Descriptions list details everything about each method."
msgstr ""

#: ../../docs/tutorials/scripting/how_to_read_the_godot_api.rst:167
msgid ""
"It restates the method's return data type, parameter names/types/defaults, "
"and qualifiers."
msgstr ""

#: ../../docs/tutorials/scripting/how_to_read_the_godot_api.rst:170
msgid ""
"Below that is a detailed summary of what the method does and its use "
"case(s). It may include code samples and/or links to relevant parts of the "
"Godot API."
msgstr ""

#: ../../docs/tutorials/scripting/debug/index.rst:2
msgid "Debug"
msgstr ""

#: ../../docs/tutorials/scripting/debug/overview_of_debugging_tools.rst:4
msgid "Overview of debugging tools"
msgstr ""

#: ../../docs/tutorials/scripting/debug/overview_of_debugging_tools.rst:6
msgid ""
"This guide will give you an overview of the available debugging tools in the "
"engine."
msgstr ""

#: ../../docs/tutorials/scripting/debug/overview_of_debugging_tools.rst:9
msgid ""
"Godot comes with a powerful debugger and profilers to track down bugs, "
"inspect your game at runtime, monitor essential metrics, and measure "
"performances. It also offers options to visualize collision boxes and "
"navigation polygons in the running game."
msgstr ""

#: ../../docs/tutorials/scripting/debug/overview_of_debugging_tools.rst:14
msgid ""
"Finally, you have options to debug the game running on a remote device and "
"to reload changes to your scenes or your code while the game is running."
msgstr ""

#: ../../docs/tutorials/scripting/debug/overview_of_debugging_tools.rst:18
msgid "Debugger Panel"
msgstr ""

#: ../../docs/tutorials/scripting/debug/overview_of_debugging_tools.rst:20
msgid ""
"Many of Godot's debugging tools are part of the Debugger panel, which you "
"can find information about in :ref:`doc_debugger_panel`."
msgstr ""

#: ../../docs/tutorials/scripting/debug/overview_of_debugging_tools.rst:24
msgid "Debug menu options"
msgstr ""

#: ../../docs/tutorials/scripting/debug/overview_of_debugging_tools.rst:26
msgid ""
"There are a few common debug options you can toggle on or off when running "
"your game in the editor, which can help you in debugging your game."
msgstr ""

#: ../../docs/tutorials/scripting/debug/overview_of_debugging_tools.rst:29
msgid "You can find these options in the **Debug** editor menu."
msgstr ""

#: ../../docs/tutorials/scripting/debug/overview_of_debugging_tools.rst:33
msgid "Here are the descriptions of the options:"
msgstr ""

#: ../../docs/tutorials/scripting/debug/overview_of_debugging_tools.rst:36
msgid "Deploy with Remote Debug"
msgstr ""

#: ../../docs/tutorials/scripting/debug/overview_of_debugging_tools.rst:38
msgid ""
"When exporting and deploying, the resulting executable will attempt to "
"connect to the IP of your computer for debugging."
msgstr ""

#: ../../docs/tutorials/scripting/debug/overview_of_debugging_tools.rst:42
msgid "Small Deploy with Network FS"
msgstr ""

#: ../../docs/tutorials/scripting/debug/overview_of_debugging_tools.rst:44
msgid ""
"This option speeds up testing for games with a large footprint on remote "
"devices."
msgstr ""

#: ../../docs/tutorials/scripting/debug/overview_of_debugging_tools.rst:46
msgid ""
"When **Small Deploy with Network FS** is on, instead of exporting the full "
"game, deploying the game builds a minimal executable. The editor then "
"provides files from the project over the network."
msgstr ""

#: ../../docs/tutorials/scripting/debug/overview_of_debugging_tools.rst:50
msgid ""
"Also, on Android, the game is deployed using the USB cable to speed up "
"deployment."
msgstr ""

#: ../../docs/tutorials/scripting/debug/overview_of_debugging_tools.rst:53
msgid "Visible Collision Shapes"
msgstr ""

#: ../../docs/tutorials/scripting/debug/overview_of_debugging_tools.rst:55
msgid ""
"This option makes collision shapes and raycast nodes visible in the running "
"game."
msgstr ""

#: ../../docs/tutorials/scripting/debug/overview_of_debugging_tools.rst:58
msgid "Visible Navigation"
msgstr ""

#: ../../docs/tutorials/scripting/debug/overview_of_debugging_tools.rst:60
msgid "Navigation meshes and polygons will be visible on the running game."
msgstr ""

#: ../../docs/tutorials/scripting/debug/overview_of_debugging_tools.rst:63
msgid "Sync Scene Changes"
msgstr ""

#: ../../docs/tutorials/scripting/debug/overview_of_debugging_tools.rst:65
msgid ""
"With this option, any change you make to a scene in the editor at runtime "
"appears instantly. When used remotely on a device, this is more efficient "
"with the network filesystem."
msgstr ""

#: ../../docs/tutorials/scripting/debug/overview_of_debugging_tools.rst:70
msgid "Sync Script Changes"
msgstr ""

#: ../../docs/tutorials/scripting/debug/overview_of_debugging_tools.rst:72
msgid ""
"Any script that is saved will be reloaded on the running game. When used "
"remotely on a device, this is more efficient with the network filesystem."
msgstr ""

#: ../../docs/tutorials/scripting/debug/overview_of_debugging_tools.rst:78
msgid "Script editor debug tools and options"
msgstr ""

#: ../../docs/tutorials/scripting/debug/overview_of_debugging_tools.rst:80
msgid ""
"The script editor has its own set of debug tools for use with breakpoints "
"and two options. The breakpoint tools can also be found in the **Debugger** "
"tab of the debugger."
msgstr ""

#: ../../docs/tutorials/scripting/debug/overview_of_debugging_tools.rst:86
#: ../../docs/tutorials/scripting/debug/debugger_panel.rst:27
msgid ""
"You can create a breakpoint by clicking the gutter in the left of the script "
"editor (on the left of the line numbers). When hovering this gutter, you "
"will see a transparent red dot appearing, which turns into an opaque red dot "
"after the breakpoint is placed by clicking. Click the red dot again to "
"remove the breakpoint. Breakpoints created this way persist across editor "
"restarts, even if the script wasn't saved when exiting the editor."
msgstr ""

#: ../../docs/tutorials/scripting/debug/overview_of_debugging_tools.rst:93
#: ../../docs/tutorials/scripting/debug/debugger_panel.rst:34
msgid ""
"You can also use the ``breakpoint`` keyword in GDScript to create a "
"breakpoint that is stored in the script itself. Unlike breakpoints created "
"by clicking in the gutter, this keyword-based breakpoint is persistent "
"across different machines when using version control."
msgstr ""

#: ../../docs/tutorials/scripting/debug/overview_of_debugging_tools.rst:100
msgid ""
"The **Break** button causes a break in the script like a breakpoint would. "
"**Continue** makes the game continue after pausing at a breakpoint. **Step "
"Over** goes to the next line of code, and **Step Into** goes into a function "
"if possible. Otherwise, it does the same thing as **Step Over**."
msgstr ""

#: ../../docs/tutorials/scripting/debug/overview_of_debugging_tools.rst:105
msgid ""
"The **Keep Debugger Open** option keeps the debugger open after a scene has "
"been closed. The **Debug with External Editor** option lets you debug your "
"game with an external editor. This option is also accessible in **Editor "
"Settings > Debugger**."
msgstr ""

#: ../../docs/tutorials/scripting/debug/overview_of_debugging_tools.rst:110
msgid ""
"When the debugger breaks on a breakpoint, a green triangle arrow is visible "
"in the script editor's gutter. This arrow indicates the line of code the "
"debugger broke on."
msgstr ""

#: ../../docs/tutorials/scripting/debug/overview_of_debugging_tools.rst:115
msgid "Debug project settings"
msgstr ""

#: ../../docs/tutorials/scripting/debug/overview_of_debugging_tools.rst:117
msgid ""
"In the project settings, there is a **Debug** category with three "
"subcategories which control different things."
msgstr ""

#: ../../docs/tutorials/scripting/debug/overview_of_debugging_tools.rst:121
#, fuzzy
msgid "Settings"
msgstr "Uvod / Početak"

#: ../../docs/tutorials/scripting/debug/overview_of_debugging_tools.rst:123
msgid ""
"These are some general settings such as printing the current FPS to the "
"**Output** panel, the maximum amount of functions when profiling and others."
msgstr ""

#: ../../docs/tutorials/scripting/debug/overview_of_debugging_tools.rst:130
msgid ""
"These settings allow you to toggle specific GDScript warnings, such as for "
"unused variables. You can also turn off warnings completely."
msgstr ""

#: ../../docs/tutorials/scripting/debug/overview_of_debugging_tools.rst:134
msgid "Shapes"
msgstr ""

#: ../../docs/tutorials/scripting/debug/overview_of_debugging_tools.rst:136
msgid ""
"Shapes are where you can adjust the color of shapes that only appear for "
"debugging purposes, such as collision and navigation shapes."
msgstr ""

#: ../../docs/tutorials/scripting/debug/overview_of_debugging_tools.rst:140
msgid "Remote in scene dock"
msgstr ""

#: ../../docs/tutorials/scripting/debug/overview_of_debugging_tools.rst:142
msgid ""
"When running a game in the editor two options appear at the top of the "
"**Scene** dock, **Remote** and **Local**. While using **Remote** you can "
"inspect or change the nodes' parameters in the running project."
msgstr ""

#: ../../docs/tutorials/scripting/debug/overview_of_debugging_tools.rst:148
msgid ""
"Some editor settings related to debugging can be found inside the **Editor "
"Settings**, under the **Network > Debug** and **Debugger** sections."
msgstr ""

#: ../../docs/tutorials/scripting/debug/debugger_panel.rst:4
msgid "Debugger panel"
msgstr ""

#: ../../docs/tutorials/scripting/debug/debugger_panel.rst:6
msgid ""
"Many of Godot's debugging tools, including the debugger, can be found in the "
"debugger panel at the bottom of the screen. Click on **Debugger** to open it."
msgstr ""

#: ../../docs/tutorials/scripting/debug/debugger_panel.rst:11
msgid ""
"The debugger panel is split into several tabs, each focusing on a specific "
"task."
msgstr ""

#: ../../docs/tutorials/scripting/debug/debugger_panel.rst:16
msgid ""
"The Debugger tab opens automatically when the GDScript compiler reaches a "
"breakpoint in your code."
msgstr ""

#: ../../docs/tutorials/scripting/debug/debugger_panel.rst:19
msgid ""
"It gives you a `stack trace <https://en.wikipedia.org/wiki/Stack_trace>`__, "
"information about the state of the object, and buttons to control the "
"program's execution. When the debugger breaks on a breakpoint, a green "
"triangle arrow is visible in the script editor's gutter. This arrow "
"indicates the line of code the debugger broke on."
msgstr ""

#: ../../docs/tutorials/scripting/debug/debugger_panel.rst:39
msgid "You can use the buttons in the top-right corner to:"
msgstr ""

#: ../../docs/tutorials/scripting/debug/debugger_panel.rst:41
msgid ""
"Skip all breakpoints. That way, you can save breakpoints for future "
"debugging sessions."
msgstr ""

#: ../../docs/tutorials/scripting/debug/debugger_panel.rst:43
msgid "Copy the current error message."
msgstr ""

#: ../../docs/tutorials/scripting/debug/debugger_panel.rst:44
msgid ""
"**Step Into** the code. This button takes you to the next line of code, and "
"if it's a function, it steps line-by-line through the function."
msgstr ""

#: ../../docs/tutorials/scripting/debug/debugger_panel.rst:46
msgid ""
"**Step Over** the code. This button goes to the next line of code, but it "
"doesn't step line-by-line through functions."
msgstr ""

#: ../../docs/tutorials/scripting/debug/debugger_panel.rst:48
msgid "**Break**. This button pauses the game's execution."
msgstr ""

#: ../../docs/tutorials/scripting/debug/debugger_panel.rst:49
msgid "**Continue**. This button resumes the game after a breakpoint or pause."
msgstr ""

#: ../../docs/tutorials/scripting/debug/debugger_panel.rst:52
msgid "Errors"
msgstr ""

#: ../../docs/tutorials/scripting/debug/debugger_panel.rst:54
msgid ""
"This is where error and warning messages are printed while running the game."
msgstr ""

#: ../../docs/tutorials/scripting/debug/debugger_panel.rst:56
msgid ""
"You can disable specific warnings in **Project Settings > Debug > GDScript**."
msgstr ""

#: ../../docs/tutorials/scripting/debug/debugger_panel.rst:59
msgid "Profiler"
msgstr ""

#: ../../docs/tutorials/scripting/debug/debugger_panel.rst:61
msgid ""
"The profiler is used to see what code is running while your project is in "
"use, and how that effects performance."
msgstr ""

#: ../../docs/tutorials/scripting/debug/debugger_panel.rst:66
msgid ""
"A detailed explanation of how to use the profiler can be found in the "
"dedicated :ref:`doc_the_profiler` page."
msgstr ""

#: ../../docs/tutorials/scripting/debug/debugger_panel.rst:70
msgid "Visual Profiler"
msgstr ""

#: ../../docs/tutorials/scripting/debug/debugger_panel.rst:72
msgid ""
"The Visual Profiler can be used to monitor what is taking the most time when "
"rendering a frame on the CPU and GPU respectively. This allows tracking "
"sources of potential CPU and GPU bottlenecks caused by rendering."
msgstr ""

#: ../../docs/tutorials/scripting/debug/debugger_panel.rst:78
msgid ""
"The Visual Profiler only measures CPU time taken for rendering tasks, such "
"as performing draw calls. The Visual Profiler does **not** include CPU time "
"taken for other tasks such as scripting and physics. Use the standard "
"Profiler tab to track non-rendering-related CPU tasks."
msgstr ""

#: ../../docs/tutorials/scripting/debug/debugger_panel.rst:83
msgid ""
"To use the visual profiler, run the project, switch to the **Visual "
"Profiler** tab within the Debugger bottom panel, then click **Start**:"
msgstr ""

#: ../../docs/tutorials/scripting/debug/debugger_panel.rst:89
msgid ""
"Visual Profiler tab after clicking Start, waiting for a few seconds, then "
"clicking Stop"
msgstr ""

#: ../../docs/tutorials/scripting/debug/debugger_panel.rst:89
msgid ""
"Visual Profiler tab after clicking **Start**, waiting for a few seconds, "
"then clicking **Stop**"
msgstr ""

#: ../../docs/tutorials/scripting/debug/debugger_panel.rst:91
msgid ""
"You will see categories and results appearing as the profiler is running. "
"Graph lines also appear, with the left side being a CPU framegraph and the "
"right side being a GPU framegraph."
msgstr ""

#: ../../docs/tutorials/scripting/debug/debugger_panel.rst:95
msgid ""
"Click **Stop** to finish profiling, which will keep the results visible but "
"frozen in place. Results remain visible after stopping the running project, "
"but not after exiting the editor."
msgstr ""

#: ../../docs/tutorials/scripting/debug/debugger_panel.rst:99
msgid ""
"Click on result categories on the left to highlight them in the CPU and GPU "
"graphs on the right. You can also click on the graph to move the cursor to a "
"specific frame number and highlight the selected data type in the result "
"categories on the left."
msgstr ""

#: ../../docs/tutorials/scripting/debug/debugger_panel.rst:104
msgid ""
"You can switch the result display between a time value (in milliseconds per "
"frame) or a percentage of the target frametime (which is currently hardcoded "
"to 16.67 milliseconds, or 60 FPS)."
msgstr ""

#: ../../docs/tutorials/scripting/debug/debugger_panel.rst:108
msgid ""
"If framerate spikes occur during profiling, this can cause the graph to be "
"poorly scaled. Disable **Fit to Frame** so that the graph will zoom onto the "
"60 FPS+ portion."
msgstr ""

#: ../../docs/tutorials/scripting/debug/debugger_panel.rst:114
msgid ""
"Remember that Visual Profiler results can vary **heavily** based on viewport "
"resolution, which is determined by the window size if using the ``disabled`` "
"or ``canvas_items`` :ref:`stretch modes <doc_multiple_resolutions>`."
msgstr ""

#: ../../docs/tutorials/scripting/debug/debugger_panel.rst:119
msgid ""
"When comparing results across different runs, make sure to use the same "
"viewport size for all runs."
msgstr ""

#: ../../docs/tutorials/scripting/debug/debugger_panel.rst:122
msgid ""
"Visual Profiler is supported when using any rendering method (Forward+, "
"Mobile or Compatibility), but the reported categories will vary depending on "
"the current rendering method as well as the enabled graphics features. For "
"example, when using Forward+, a simple 2D scene with shadow-casting lights "
"will result in the following categories appearing:"
msgstr ""

#: ../../docs/tutorials/scripting/debug/debugger_panel.rst:131
msgid "Example results from a 2D scene in the Visual Profiler"
msgstr ""

#: ../../docs/tutorials/scripting/debug/debugger_panel.rst:133
msgid ""
"To give another example with Forward+, a 3D scene with shadow-casting lights "
"and various effects enabled will result in the following categories enabled:"
msgstr ""

#: ../../docs/tutorials/scripting/debug/debugger_panel.rst:139
msgid "Example results from a 3D scene in the Visual Profiler"
msgstr ""

#: ../../docs/tutorials/scripting/debug/debugger_panel.rst:141
msgid ""
"Notice how in the 3D example, several of the categories have **(Parallel)** "
"appended to their name. This hints that multiple tasks are being performed "
"in parallel on the GPU. This generally means that disabling only one of the "
"features involved won't improve performance as much as anticipated, as the "
"other task still needs to be performed sequentially."
msgstr ""

#: ../../docs/tutorials/scripting/debug/debugger_panel.rst:148
msgid "Network Profiler"
msgstr ""

#: ../../docs/tutorials/scripting/debug/debugger_panel.rst:150
msgid ""
"The Network Profiler contains a list of all the nodes that communicate over "
"the multiplayer API and, for each one, some counters on the amount of "
"incoming and outgoing network interactions. It also features a bandwidth "
"meter that displays the total bandwidth usage at any given moment."
msgstr ""

#: ../../docs/tutorials/scripting/debug/debugger_panel.rst:157
msgid ""
"The bandwidth meter does **not** take the :ref:`doc_high_level_multiplayer` "
"API's own compression system into account. This means that changing the "
"compression algorithm used will not change the metrics reported by the "
"bandwidth meter."
msgstr ""

#: ../../docs/tutorials/scripting/debug/debugger_panel.rst:163
msgid "Monitors"
msgstr ""

#: ../../docs/tutorials/scripting/debug/debugger_panel.rst:165
msgid ""
"The monitors are graphs of several aspects of the game while its running "
"such as FPS, memory usage, how many nodes are in a scene and more. All "
"monitors keep track of stats automatically, so even if one monitor isn't "
"open while the game is running, you can open it later and see how the values "
"changed."
msgstr ""

#: ../../docs/tutorials/scripting/debug/debugger_panel.rst:172
msgid ""
"In addition to the default performance monitors, you can also create :ref:"
"`custom performance monitors <doc_custom_performance_monitors>` to track "
"arbitrary values in your project."
msgstr ""

#: ../../docs/tutorials/scripting/debug/debugger_panel.rst:177
msgid "Video RAM"
msgstr ""

#: ../../docs/tutorials/scripting/debug/debugger_panel.rst:179
msgid ""
"The **Video RAM** tab shows the video RAM usage of the game while it is "
"running. It provides a list of every resource using video RAM by resource "
"path, the type of resource it is, what format it is in, and how much Video "
"RAM that resource is using. There is also a total video RAM usage number at "
"the top right of the panel."
msgstr ""

#: ../../docs/tutorials/scripting/debug/debugger_panel.rst:187
msgid "Misc"
msgstr ""

#: ../../docs/tutorials/scripting/debug/debugger_panel.rst:189
msgid ""
"The **Misc** tab contains tools to identify the control nodes you are "
"clicking at runtime:"
msgstr ""

#: ../../docs/tutorials/scripting/debug/debugger_panel.rst:192
msgid ""
"**Clicked Control** tells you where the clicked node is in the scene tree."
msgstr ""

#: ../../docs/tutorials/scripting/debug/debugger_panel.rst:193
msgid "**Clicked Control Type** tells you the type of the node you clicked is."
msgstr ""

#: ../../docs/tutorials/scripting/debug/the_profiler.rst:4
msgid "The Profiler"
msgstr ""

#: ../../docs/tutorials/scripting/debug/the_profiler.rst:6
msgid ""
"You run your game from Godot and play around. It's fun, it's becoming "
"feature complete, and you feel it's getting close to release."
msgstr ""

#: ../../docs/tutorials/scripting/debug/the_profiler.rst:9
msgid ""
"But then, you open the skill tree, and it grinds to a halt as something "
"snags in your code. Watching the skill tree scroll by like it's a slide show "
"is unacceptable. What went wrong? Is it positioning the skill tree elements, "
"the UI, or rendering?"
msgstr ""

#: ../../docs/tutorials/scripting/debug/the_profiler.rst:14
msgid ""
"You could try to optimize everything and run the game repeatedly, but you "
"can be smarter about this and narrow down the possibilities. Enter Godot's "
"profiler."
msgstr ""

#: ../../docs/tutorials/scripting/debug/the_profiler.rst:18
#, fuzzy
msgid "An overview of the profiler"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/scripting/debug/the_profiler.rst:20
msgid ""
"You can open the profiler by opening the **Debugger** panel and clicking on "
"the **Profiler** tab."
msgstr ""

#: ../../docs/tutorials/scripting/debug/the_profiler.rst:25
msgid ""
"Godot's profiler does not automatically run because profiling is performance-"
"intensive. It has to continually measure everything happening in the game "
"and report back to the debugger, so it's off by default."
msgstr ""

#: ../../docs/tutorials/scripting/debug/the_profiler.rst:29
msgid ""
"To begin profiling, click on the **Start** button in the top-left. Run your "
"game and data will start appearing. You can also start profiling at any time "
"before or during gameplay, depending on if you want."
msgstr ""

#: ../../docs/tutorials/scripting/debug/the_profiler.rst:35
msgid ""
"The profiler does not currently support C# scripts. C# scripts can be "
"profiled using JetBrains Rider and JetBrains dotTrace with the Godot support "
"plugin."
msgstr ""

#: ../../docs/tutorials/scripting/debug/the_profiler.rst:38
msgid ""
"You can clear the data by clicking the **Clear** button anytime. Use the "
"**Measure** drop-down menu to change the type of data you measure. The "
"measurements panel and the graph will update accordingly."
msgstr ""

#: ../../docs/tutorials/scripting/debug/the_profiler.rst:43
msgid "The measured data"
msgstr ""

#: ../../docs/tutorials/scripting/debug/the_profiler.rst:45
msgid ""
"The profiler's interface is split into two. There is a list of functions on "
"the left and the performance graph on the right."
msgstr ""

#: ../../docs/tutorials/scripting/debug/the_profiler.rst:48
msgid ""
"The main measurements are frame time, physics frame, idle time, and physics "
"time."
msgstr ""

#: ../../docs/tutorials/scripting/debug/the_profiler.rst:50
msgid ""
"The **frame time** is the time it takes Godot to execute all the logic for "
"an entire image, from physics to rendering."
msgstr ""

#: ../../docs/tutorials/scripting/debug/the_profiler.rst:52
msgid ""
"**Physics frame** is the time Godot has allocated between physics updates. "
"In an ideal scenario, the frame time is whatever you chose: 16.66 "
"milliseconds by default, which corresponds to 60FPS. It's a frame of "
"reference you can use for everything else around it."
msgstr ""

#: ../../docs/tutorials/scripting/debug/the_profiler.rst:56
msgid ""
"**Idle time** is the time Godot took to update logic other than physics, "
"such as code that lives in `_process` or timers and cameras set to update on "
"**Idle**."
msgstr ""

#: ../../docs/tutorials/scripting/debug/the_profiler.rst:59
msgid ""
"**Physics time** is the time Godot took to update physics tasks, like "
"`_physics_process` and built-in nodes set to **Physics** update."
msgstr ""

#: ../../docs/tutorials/scripting/debug/the_profiler.rst:62
msgid ""
"**Frame Time** includes rendering time. Say you find a mysterious spike of "
"lag in your game, but your physics and scripts are all running fast. The "
"delay could be due to the appearance of particles or visual effects!"
msgstr ""

#: ../../docs/tutorials/scripting/debug/the_profiler.rst:67
msgid ""
"By default, Godot ticks on Frame Time and Physics Time. This gives you an "
"overview of how long each frame takes relative to the allocated desired "
"physics FPS. You can toggle functions on and off by clicking the checkboxes "
"on the left. Other facilities make appearances as you go down the list, like "
"Physics 2D, Physics, and Audio, before reaching Script functions, where your "
"code appears."
msgstr ""

#: ../../docs/tutorials/scripting/debug/the_profiler.rst:73
msgid ""
"If you click on the graph, you change which frame's information appears on "
"the left. In the top right, there is also a frame counter where you can "
"manually adjust the frame you are looking at more granularly."
msgstr ""

#: ../../docs/tutorials/scripting/debug/the_profiler.rst:78
msgid "Scope of measurement and measurement windows"
msgstr ""

#: ../../docs/tutorials/scripting/debug/the_profiler.rst:80
msgid ""
"You can change what measurement you are looking at using the **Measure** "
"drop-down menu. By default, it starts with Frame Time and lists the time it "
"takes to go through the frame in milliseconds. The average time is the "
"average time any given function took when called more than once. For "
"example, a function that took 0.05 milliseconds to run five times should "
"give you an average of 0.01 milliseconds."
msgstr ""

#: ../../docs/tutorials/scripting/debug/the_profiler.rst:87
msgid ""
"If accurate milliseconds count is not important, and you want to see "
"proportions of time relative to the rest of the frame, use percentage "
"measurements. Frame % is relative to Frame Time, and Physics % is relative "
"to Physics Time."
msgstr ""

#: ../../docs/tutorials/scripting/debug/the_profiler.rst:91
msgid ""
"The last option is the scope of the time. **Inclusive** measures the time a "
"function took **with** any nested function calls. For example:"
msgstr ""

#: ../../docs/tutorials/scripting/debug/the_profiler.rst:96
msgid ""
"`get_neighbors`, `find_nearest_neighbor` and `move_subject` all took a lot "
"of time. You could be fooled into thinking that this is because all three of "
"them are slow."
msgstr ""

#: ../../docs/tutorials/scripting/debug/the_profiler.rst:100
msgid ""
"But when changed to **Self**, Godot measures the time spent in the function "
"body without considering function calls it made itself."
msgstr ""

#: ../../docs/tutorials/scripting/debug/the_profiler.rst:105
msgid ""
"You can see that `get_neighbors` and `move_subject` have lost a lot of their "
"importance. In effect, that means that `get_neighbors` and `move_subject` "
"have spent more time waiting for some other function call to finish than "
"not, and `find_nearest_neighbor` is **actually** slow."
msgstr ""

#: ../../docs/tutorials/scripting/debug/the_profiler.rst:111
#, fuzzy
msgid "Debugging slow code with the profiler"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/scripting/debug/the_profiler.rst:113
msgid ""
"Finding slow code with the profiler boils down to running your game and "
"watching the performance graph as it draws. When an unacceptable spike "
"occurs in the frame time, you can click on the graph to pause your game and "
"narrow the _Frame #_ to the spike's start. You may need to jump back and "
"forth between frames and functions to find the root cause."
msgstr ""

#: ../../docs/tutorials/scripting/debug/the_profiler.rst:119
msgid ""
"Under the Script functions, turn on the checkboxes for some functions to "
"find which take time. These are the functions you need to review and "
"optimize."
msgstr ""

#: ../../docs/tutorials/scripting/debug/the_profiler.rst:123
msgid "Measuring manually in microseconds"
msgstr ""

#: ../../docs/tutorials/scripting/debug/the_profiler.rst:125
msgid ""
"If your function is complex, it could be challenging to figure out which "
"part needs optimization. Is it your math or the way you access other pieces "
"of data to do the math with? Is it the `for` loop? The `if` statements?"
msgstr ""

#: ../../docs/tutorials/scripting/debug/the_profiler.rst:129
msgid ""
"You can narrow down the measurement by manually counting ticks as the code "
"runs with some temporary functions. The two functions are part of the `Time` "
"class object. They are `get_ticks_msec` and `get_ticks_usec`. The first "
"measures in milliseconds (1,000 per second), and the second measures in "
"microseconds (1,000,000 per second)."
msgstr ""

#: ../../docs/tutorials/scripting/debug/the_profiler.rst:135
msgid ""
"Either one returns the amount of time since the game engine started in their "
"respective time frame."
msgstr ""

#: ../../docs/tutorials/scripting/debug/the_profiler.rst:138
msgid ""
"If you wrap a piece of code with a start and end count of microseconds, the "
"difference between the two is the amount of time it took to run that piece "
"of code."
msgstr ""

#: ../../docs/tutorials/scripting/debug/the_profiler.rst:160
msgid ""
"As you become a more experienced programmer, this technique becomes less "
"necessary. You begin to learn what parts of a running program are slow. "
"Knowing that loops and branches can be slow comes from experience, and you "
"gain experience by measuring and doing research."
msgstr ""

#: ../../docs/tutorials/scripting/debug/the_profiler.rst:165
msgid ""
"But between the profiler and the ticks functions, you should have enough to "
"get started finding which parts of your code need optimization."
msgstr ""

#: ../../docs/tutorials/scripting/debug/custom_performance_monitors.rst:4
#, fuzzy
msgid "Custom performance monitors"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/scripting/debug/custom_performance_monitors.rst:9
msgid ""
"As explained in the :ref:`doc_debugger_panel` documentation, Godot features "
"a **Debugger > Monitors** bottom panel that allows tracking various values "
"with graphs showing their evolution over time. The data for those graphs is "
"sourced from the engine's :ref:`class_Performance` singleton."
msgstr ""

#: ../../docs/tutorials/scripting/debug/custom_performance_monitors.rst:14
msgid ""
"Since Godot 4.0, you can declare custom values to be displayed in the "
"Monitors tab. Example use cases for custom performance monitors include:"
msgstr ""

#: ../../docs/tutorials/scripting/debug/custom_performance_monitors.rst:17
msgid ""
"Displaying performance metrics that are specific to your project. For "
"instance, in a voxel game, you could create a performance monitor to track "
"the number of chunks that are loaded every second."
msgstr ""

#: ../../docs/tutorials/scripting/debug/custom_performance_monitors.rst:20
msgid ""
"Displaying in-game metrics that are not strictly related to performance, but "
"are still useful to graph for debugging purposes. For instance, you could "
"track the number of enemies present in the game to make sure your spawning "
"mechanic works as intended."
msgstr ""

#: ../../docs/tutorials/scripting/debug/custom_performance_monitors.rst:26
#, fuzzy
msgid "Creating a custom performance monitor"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/scripting/debug/custom_performance_monitors.rst:28
msgid ""
"In this example, we'll create a custom performance monitor to track how many "
"enemies are present in the currently running project."
msgstr ""

#: ../../docs/tutorials/scripting/debug/custom_performance_monitors.rst:31
msgid ""
"The main scene features a :ref:`class_Timer` node with the following script "
"attached:"
msgstr ""

#: ../../docs/tutorials/scripting/debug/custom_performance_monitors.rst:61
msgid ""
"The second parameter of :ref:`Performance."
"add_custom_monitor<class_Performance_method_add_custom_monitor>` is a :ref:"
"`class_Callable`."
msgstr ""

#: ../../docs/tutorials/scripting/debug/custom_performance_monitors.rst:65
msgid ""
"``enemy.tscn`` is a scene with a Node2D root node and Timer child node. The "
"Node2D has the following script attached:"
msgstr ""

#: ../../docs/tutorials/scripting/debug/custom_performance_monitors.rst:84
msgid ""
"In this example, since we spawn 20 enemies per second, and each enemy "
"despawns 2.5 seconds after they spawn, we expect the number of enemies "
"present in the scene to stabilize to 50. We can make sure about this by "
"looking at the graph."
msgstr ""

#: ../../docs/tutorials/scripting/debug/custom_performance_monitors.rst:88
msgid ""
"To visualize the graph created from this custom performance monitor, run the "
"project, switch to the editor while the project is running and open "
"**Debugger > Monitors** at the bottom of the editor window. Scroll down to "
"the newly available **Game** section and check **Enemies**. You should see a "
"graph appearing as follows:"
msgstr ""

#: ../../docs/tutorials/scripting/debug/custom_performance_monitors.rst:98
#, fuzzy
msgid "Example editor graph from a custom performance monitor"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/scripting/debug/custom_performance_monitors.rst:102
msgid ""
"The performance monitor handling code doesn't have to live in the same "
"script as the nodes themselves. You may choose to move the performance "
"monitor registration and getter function to an :ref:`autoload "
"<doc_singletons_autoload>` instead."
msgstr ""

#: ../../docs/tutorials/scripting/debug/custom_performance_monitors.rst:108
msgid "Querying a performance monitor in a project"
msgstr ""

#: ../../docs/tutorials/scripting/debug/custom_performance_monitors.rst:110
msgid ""
"If you wish to display the value of the performance monitor in the running "
"project's window (rather than the editor), use ``Performance."
"get_custom_monitor(\"category/name\")`` to fetch the value of the custom "
"monitor. You can display the value using a :ref:`class_Label`, :ref:"
"`class_RichTextLabel`, :ref:`doc_custom_drawing_in_2d`, :ref:`doc_3d_text`, "
"etc."
msgstr ""

#: ../../docs/tutorials/scripting/debug/custom_performance_monitors.rst:117
msgid ""
"This method can be used in exported projects as well (debug and release "
"mode), which allows you to create visualizations outside the editor."
msgstr ""

#: ../../docs/tutorials/scripting/idle_and_physics_processing.rst:4
msgid "Idle and Physics Processing"
msgstr ""

#: ../../docs/tutorials/scripting/idle_and_physics_processing.rst:6
msgid ""
"Games run in a loop. Each frame, you need to update the state of your game "
"world before drawing it on screen. Godot provides two virtual methods in the "
"Node class to do so: :ref:`Node._process() "
"<class_Node_private_method__process>` and :ref:`Node._physics_process() "
"<class_Node_private_method__physics_process>`. If you define either or both "
"in a script, the engine will call them automatically."
msgstr ""

#: ../../docs/tutorials/scripting/idle_and_physics_processing.rst:12
#, fuzzy
msgid "There are two types of processing available to you:"
msgstr "Ne postoje ograničenja prilikom korištenja Godot-a"

#: ../../docs/tutorials/scripting/idle_and_physics_processing.rst:14
msgid ""
"**Idle processing** allows you to run code that updates a node every frame, "
"as often as possible."
msgstr ""

#: ../../docs/tutorials/scripting/idle_and_physics_processing.rst:16
msgid ""
"**Physics processing** happens at a fixed rate, 60 times per second by "
"default. This is independent of your game's actual framerate, and keeps "
"physics running smoothly. You should use it for anything that involves the "
"physics engine, like moving a body that collides with the environment."
msgstr ""

#: ../../docs/tutorials/scripting/idle_and_physics_processing.rst:21
msgid ""
"You can activate idle processing by defining the ``_process()`` method in a "
"script. You can turn it off and back on by calling :ref:`Node.set_process() "
"<class_Node_method_set_process>`."
msgstr ""

#: ../../docs/tutorials/scripting/idle_and_physics_processing.rst:25
msgid "The engine calls this method every time it draws a frame:"
msgstr ""

#: ../../docs/tutorials/scripting/idle_and_physics_processing.rst:41
msgid ""
"Keep in mind that the frequency at which the engine calls ``_process()`` "
"depends on your application's framerate, which varies over time and across "
"devices."
msgstr ""

#: ../../docs/tutorials/scripting/idle_and_physics_processing.rst:44
msgid ""
"The function's ``delta`` parameter is the time elapsed in seconds since the "
"previous call to ``_process()``. Use this parameter to make calculations "
"independent of the framerate. For example, you should always multiply a "
"speed value by ``delta`` to animate a moving object."
msgstr ""

#: ../../docs/tutorials/scripting/idle_and_physics_processing.rst:49
msgid ""
"Physics processing works with a similar virtual function: "
"``_physics_process()``. Use it for calculations that must happen before each "
"physics step, like moving a character that collides with the game world. As "
"mentioned above, ``_physics_process()`` runs at fixed time intervals as much "
"as possible to keep the physics interactions stable. You can change the "
"interval between physics steps in the Project Settings, under Physics -> "
"Common -> Physics Fps. By default, it's set to run 60 times per second."
msgstr ""

#: ../../docs/tutorials/scripting/idle_and_physics_processing.rst:57
msgid "The engine calls this method before every physics step:"
msgstr ""

#: ../../docs/tutorials/scripting/idle_and_physics_processing.rst:73
msgid ""
"The function ``_process()`` is not synchronized with physics. Its rate "
"depends on hardware and game optimization. It also runs after the physics "
"step in single-threaded games."
msgstr ""

#: ../../docs/tutorials/scripting/idle_and_physics_processing.rst:77
msgid ""
"You can see the ``_process()`` function at work by creating a scene with a "
"single Label node, with the following script attached to it:"
msgstr ""

#: ../../docs/tutorials/scripting/idle_and_physics_processing.rst:106
msgid "When you run the scene, you should see a counter increasing each frame."
msgstr ""

#: ../../docs/tutorials/scripting/groups.rst:4
msgid "Groups"
msgstr ""

#: ../../docs/tutorials/scripting/groups.rst:6
msgid ""
"Groups in Godot work like tags in other software. You can add a node to as "
"many groups as you want. Then, in code, you can use the SceneTree to:"
msgstr ""

#: ../../docs/tutorials/scripting/groups.rst:9
msgid "Get a list of nodes in a group."
msgstr ""

#: ../../docs/tutorials/scripting/groups.rst:10
msgid "Call a method on all nodes in a group."
msgstr ""

#: ../../docs/tutorials/scripting/groups.rst:11
msgid "Send a notification to all nodes in a group."
msgstr ""

#: ../../docs/tutorials/scripting/groups.rst:13
msgid "This is a useful feature to organize large scenes and decouple code."
msgstr ""

#: ../../docs/tutorials/scripting/groups.rst:17
msgid "Managing groups"
msgstr ""

#: ../../docs/tutorials/scripting/groups.rst:19
msgid ""
"Groups are created by adding a node to a new group name, and likewise they "
"are removed by removing all nodes from a given group."
msgstr ""

#: ../../docs/tutorials/scripting/groups.rst:22
#, fuzzy
msgid "There are two ways to add/remove nodes to groups:"
msgstr "Ne postoje ograničenja prilikom korištenja Godot-a"

#: ../../docs/tutorials/scripting/groups.rst:24
#, fuzzy
msgid "During design, by using the Node dock in the editor."
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/scripting/groups.rst:25
msgid ""
"During execution, by calling :ref:`Node.add_to_group() "
"<class_Node_method_add_to_group>` or :ref:`Node.remove_from_group() "
"<class_Node_method_remove_from_group>`."
msgstr ""

#: ../../docs/tutorials/scripting/groups.rst:30
#, fuzzy
msgid "Using the Node dock"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/scripting/groups.rst:32
msgid ""
"You can add nodes in the current scene to groups using the Groups tab in the "
"Node dock."
msgstr ""

#: ../../docs/tutorials/scripting/groups.rst:37
msgid ""
"Select one or more nodes in the Scene dock and write the group name in the "
"field, then click Add."
msgstr ""

#: ../../docs/tutorials/scripting/groups.rst:42
msgid "You should now see the group appear."
msgstr ""

#: ../../docs/tutorials/scripting/groups.rst:46
msgid ""
"In a complex project, you may end up with many groups or large scenes with "
"many nodes. You can add or remove any node to groups using the Group Editor "
"window. To access it, click the Manage Groups button."
msgstr ""

#: ../../docs/tutorials/scripting/groups.rst:52
msgid ""
"The Group Editor window appears. Here's a screenshot from a complex project "
"to illustrate the tool's purpose."
msgstr ""

#: ../../docs/tutorials/scripting/groups.rst:57
msgid "It has three columns:"
msgstr ""

#: ../../docs/tutorials/scripting/groups.rst:59
msgid "A list of groups used by nodes in the current scene."
msgstr ""

#: ../../docs/tutorials/scripting/groups.rst:60
msgid "A list of nodes that are not part of the selected group."
msgstr ""

#: ../../docs/tutorials/scripting/groups.rst:61
msgid "A list of nodes in the group."
msgstr ""

#: ../../docs/tutorials/scripting/groups.rst:63
msgid ""
"The fields at the bottom allow you to add new groups or filter nodes in the "
"second and third columns."
msgstr ""

#: ../../docs/tutorials/scripting/groups.rst:66
msgid ""
"Any node name that's greyed out means the node was added to the group in a "
"different scene and you cannot edit it here. This happens on scene instances "
"in particular."
msgstr ""

#: ../../docs/tutorials/scripting/groups.rst:71
#, fuzzy
msgid "Using code"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/scripting/groups.rst:73
msgid ""
"You can also manage groups from scripts. The following code adds the node to "
"which you attach the script to the ``guards`` group as soon as it enters the "
"scene tree."
msgstr ""

#: ../../docs/tutorials/scripting/groups.rst:92
msgid ""
"Imagine you're creating an infiltration game. When an enemy spots the "
"player, you want all guards and robots to be on alert."
msgstr ""

#: ../../docs/tutorials/scripting/groups.rst:95
msgid ""
"In the fictional example below, we use ``SceneTree.call_group()`` to alert "
"all enemies that the player was spotted."
msgstr ""

#: ../../docs/tutorials/scripting/groups.rst:111
msgid ""
"The above code calls the function ``enter_alert_mode`` on every member of "
"the group ``guards``."
msgstr ""

#: ../../docs/tutorials/scripting/groups.rst:114
msgid ""
"To get the full list of nodes in the ``guards`` group as an array, you can "
"call :ref:`SceneTree.get_nodes_in_group() "
"<class_SceneTree_method_get_nodes_in_group>`:"
msgstr ""

#: ../../docs/tutorials/scripting/groups.rst:127
msgid ""
"The :ref:`SceneTree <class_SceneTree>` class provides many more useful "
"methods to interact with scenes, their node hierarchy, and groups. It allows "
"you to switch scenes easily or reload them, quit the game or pause and "
"unpause it. It also provides useful signals."
msgstr ""

#: ../../docs/tutorials/scripting/nodes_and_scene_instances.rst:4
msgid "Nodes and scene instances"
msgstr ""

#: ../../docs/tutorials/scripting/nodes_and_scene_instances.rst:6
msgid ""
"This guide explains how to get nodes, create nodes, add them as a child, and "
"instantiate scenes from code."
msgstr ""

#: ../../docs/tutorials/scripting/nodes_and_scene_instances.rst:10
#, fuzzy
msgid "Getting nodes"
msgstr "Uvod / Početak"

#: ../../docs/tutorials/scripting/nodes_and_scene_instances.rst:12
msgid ""
"You can get a reference to a node by calling the :ref:`Node.get_node() "
"<class_Node_method_get_node>` method. For this to work, the child node must "
"be present in the scene tree. Getting it in the parent node's ``_ready()`` "
"function guarantees that."
msgstr ""

#: ../../docs/tutorials/scripting/nodes_and_scene_instances.rst:17
msgid ""
"If, for example,  you have a scene tree like this, and you want to get a "
"reference to the Sprite2D and Camera2D nodes to access them in your script."
msgstr ""

#: ../../docs/tutorials/scripting/nodes_and_scene_instances.rst:22
msgid "To do so, you can use the following code."
msgstr ""

#: ../../docs/tutorials/scripting/nodes_and_scene_instances.rst:47
msgid ""
"Note that you get nodes using their name, not their type. Above, "
"\"Sprite2D\" and \"Camera2D\" are the nodes' names in the scene."
msgstr ""

#: ../../docs/tutorials/scripting/nodes_and_scene_instances.rst:52
msgid ""
"If you rename the Sprite2D node as Skin in the Scene dock, you have to "
"change the line that gets the node to ``get_node(\"Skin\")`` in the script."
msgstr ""

#: ../../docs/tutorials/scripting/nodes_and_scene_instances.rst:58
#, fuzzy
msgid "Node paths"
msgstr "Uvod / Početak"

#: ../../docs/tutorials/scripting/nodes_and_scene_instances.rst:60
msgid ""
"When getting a reference to a node, you're not limited to getting a direct "
"child. The ``get_node()`` function supports paths, a bit like when working "
"with a file browser. Add a slash to separate nodes."
msgstr ""

#: ../../docs/tutorials/scripting/nodes_and_scene_instances.rst:64
msgid ""
"Take the following example scene, with the script attached to the "
"UserInterface node."
msgstr ""

#: ../../docs/tutorials/scripting/nodes_and_scene_instances.rst:69
msgid "To get the AnimationPlayer node, you would use the following code."
msgstr ""

#: ../../docs/tutorials/scripting/nodes_and_scene_instances.rst:90
msgid ""
"As with file paths, you can use \"..\" to get a parent node. The best "
"practice is to avoid doing that though not to break encapsulation. You can "
"also start the path with a forward slash to make it absolute, in which case "
"your topmost node would be \"/root\", the application's predefined root "
"viewport."
msgstr ""

#: ../../docs/tutorials/scripting/nodes_and_scene_instances.rst:97
msgid "Syntactic sugar"
msgstr ""

#: ../../docs/tutorials/scripting/nodes_and_scene_instances.rst:99
msgid ""
"You can use two shorthands to shorten your code in GDScript. Firstly, "
"putting the ``@onready`` annotation before a member variable makes it "
"initialize right before the ``_ready()`` callback."
msgstr ""

#: ../../docs/tutorials/scripting/nodes_and_scene_instances.rst:107
msgid ""
"There is also a short notation for ``get_node()``: the dollar sign, \"$\". "
"You place it before the name or path of the node you want to get."
msgstr ""

#: ../../docs/tutorials/scripting/nodes_and_scene_instances.rst:116
msgid "Creating nodes"
msgstr ""

#: ../../docs/tutorials/scripting/nodes_and_scene_instances.rst:118
msgid ""
"To create a node from code, call its ``new()`` method like for any other "
"class-based datatype."
msgstr ""

#: ../../docs/tutorials/scripting/nodes_and_scene_instances.rst:121
msgid ""
"You can store the newly created node's reference in a variable and call "
"``add_child()`` to add it as a child of the node to which you attached the "
"script."
msgstr ""

#: ../../docs/tutorials/scripting/nodes_and_scene_instances.rst:146
msgid ""
"To delete a node and free it from memory, you can call its ``queue_free()`` "
"method. Doing so queues the node for deletion at the end of the current "
"frame after it has finished processing. At that point, the engine removes "
"the node from the scene and frees the object in memory."
msgstr ""

#: ../../docs/tutorials/scripting/nodes_and_scene_instances.rst:160
msgid ""
"Before calling ``sprite2d.queue_free()``, the remote scene tree looks like "
"this."
msgstr ""

#: ../../docs/tutorials/scripting/nodes_and_scene_instances.rst:164
msgid ""
"After the engine freed the node, the remote scene tree doesn't display the "
"sprite anymore."
msgstr ""

#: ../../docs/tutorials/scripting/nodes_and_scene_instances.rst:169
msgid ""
"You can alternatively call ``free()`` to immediately destroy the node. You "
"should do this with care as any reference to it will instantly become "
"``null``. We recommend using ``queue_free()`` unless you know what you're "
"doing."
msgstr ""

#: ../../docs/tutorials/scripting/nodes_and_scene_instances.rst:173
msgid ""
"When you free a node, it also frees all its children. Thanks to this, to "
"delete an entire branch of the scene tree, you only have to free the topmost "
"parent node."
msgstr ""

#: ../../docs/tutorials/scripting/nodes_and_scene_instances.rst:180
msgid ""
"Scenes are templates from which you can create as many reproductions as "
"you'd like. This operation is called instancing, and doing it from code "
"happens in two steps:"
msgstr ""

#: ../../docs/tutorials/scripting/nodes_and_scene_instances.rst:184
msgid "Loading the scene from the local drive."
msgstr ""

#: ../../docs/tutorials/scripting/nodes_and_scene_instances.rst:185
msgid ""
"Creating an instance of the loaded :ref:`PackedScene <class_PackedScene>` "
"resource."
msgstr ""

#: ../../docs/tutorials/scripting/nodes_and_scene_instances.rst:197
msgid ""
"Preloading the scene can improve the user's experience as the load operation "
"happens when the compiler reads the script and not at runtime. This feature "
"is only available with GDScript."
msgstr ""

#: ../../docs/tutorials/scripting/nodes_and_scene_instances.rst:206
msgid ""
"At that point, ``scene`` is a packed scene resource, not a node. To create "
"the actual node, you need to call :ref:`PackedScene.instantiate() "
"<class_PackedScene_method_instantiate>`. It returns a tree of nodes that you "
"can use as a child of your current node."
msgstr ""

#: ../../docs/tutorials/scripting/nodes_and_scene_instances.rst:222
msgid ""
"The advantage of this two-step process is you can keep a packed scene loaded "
"and create new instances on the fly. For example, to quickly instance "
"several enemies or bullets."
msgstr ""

#: ../../docs/tutorials/scripting/overridable_functions.rst:4
msgid "Overridable functions"
msgstr ""

#: ../../docs/tutorials/scripting/overridable_functions.rst:6
msgid ""
"Godot's Node class provides virtual functions you can override to update "
"nodes every frame or on specific events, like when they enter the scene tree."
msgstr ""

#: ../../docs/tutorials/scripting/overridable_functions.rst:9
msgid "This document presents the ones you'll use most often."
msgstr ""

#: ../../docs/tutorials/scripting/overridable_functions.rst:11
msgid ""
"Under the hood, these functions rely on Godot's low-level notifications "
"system. To learn more about it, see :ref:`doc_godot_notifications`."
msgstr ""

#: ../../docs/tutorials/scripting/overridable_functions.rst:15
msgid ""
"Two functions allow you to initialize and get nodes besides the class's "
"constructor: ``_enter_tree()`` and ``_ready()``."
msgstr ""

#: ../../docs/tutorials/scripting/overridable_functions.rst:18
msgid ""
"When the node enters the Scene Tree, it becomes active and the engine calls "
"its ``_enter_tree()`` method. That node's children may not be part of the "
"active scene yet. As you can remove and re-add nodes to the scene tree, this "
"function may be called multiple times throughout a node's lifetime."
msgstr ""

#: ../../docs/tutorials/scripting/overridable_functions.rst:23
msgid ""
"Most of the time, you'll use ``_ready()`` instead. This function is called "
"only once in a node's lifetime, after ``_enter_tree()``. ``_ready()`` "
"ensures that all children have entered the scene tree first, so you can "
"safely call ``get_node()`` on them."
msgstr ""

#: ../../docs/tutorials/scripting/overridable_functions.rst:27
msgid ""
"To learn more about getting node references, read :ref:"
"`doc_nodes_and_scene_instances`."
msgstr ""

#: ../../docs/tutorials/scripting/overridable_functions.rst:30
msgid ""
"Another related callback is ``_exit_tree()``, which the engine calls every "
"time a node is about to exit the scene tree. This can be when you call :ref:"
"`Node.remove_child() <class_Node_method_remove_child>` or when you free a "
"node."
msgstr ""

#: ../../docs/tutorials/scripting/overridable_functions.rst:71
msgid ""
"The two virtual methods ``_process()`` and ``_physics_process()`` allow you "
"to update the node, every frame and every physics frame respectively. For "
"more information, read the dedicated documentation: :ref:"
"`doc_idle_and_physics_processing`."
msgstr ""

#: ../../docs/tutorials/scripting/overridable_functions.rst:101
msgid ""
"Two more essential built-in node callback functions are :ref:`Node."
"_unhandled_input() <class_Node_private_method__unhandled_input>` and :ref:"
"`Node._input() <class_Node_private_method__input>`, which you use to both "
"receive and process individual input events. The ``_unhandled_input()`` "
"method receives every key press, mouse click, etc. that have not been "
"handled already in an ``_input()`` callback or in a user interface "
"component. You want to use it for gameplay input in general. The "
"``_input()`` callback allows you to intercept and process input events "
"before ``_unhandled_input()`` gets them."
msgstr ""

#: ../../docs/tutorials/scripting/overridable_functions.rst:110
msgid ""
"To learn more about inputs in Godot, see the :ref:`Input section <toc-learn-"
"features-inputs>`."
msgstr ""

#: ../../docs/tutorials/scripting/overridable_functions.rst:139
msgid ""
"There are some more overridable functions like :ref:`Node."
"_get_configuration_warnings() "
"<class_Node_private_method__get_configuration_warnings>`. Specialized node "
"types provide more callbacks like :ref:`CanvasItem._draw() "
"<class_CanvasItem_private_method__draw>` to draw programmatically or :ref:"
"`Control._gui_input() <class_Control_private_method__gui_input>` to handle "
"clicks and input on UI elements."
msgstr ""

#: ../../docs/tutorials/scripting/cross_language_scripting.rst:4
#, fuzzy
msgid "Cross-language scripting"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/scripting/cross_language_scripting.rst:6
msgid ""
"Godot allows you to mix and match scripting languages to suit your needs. "
"This means a single project can define nodes in both C# and GDScript. This "
"page will go through the possible interactions between two nodes written in "
"different languages."
msgstr ""

#: ../../docs/tutorials/scripting/cross_language_scripting.rst:11
msgid ""
"The following two scripts will be used as references throughout this page."
msgstr ""

#: ../../docs/tutorials/scripting/cross_language_scripting.rst:63
msgid "Instantiating nodes"
msgstr ""

#: ../../docs/tutorials/scripting/cross_language_scripting.rst:65
msgid ""
"If you're not using nodes from the scene tree, you'll probably want to "
"instantiate nodes directly from the code."
msgstr ""

#: ../../docs/tutorials/scripting/cross_language_scripting.rst:69
msgid "Instantiating C# nodes from GDScript"
msgstr ""

#: ../../docs/tutorials/scripting/cross_language_scripting.rst:71
msgid ""
"Using C# from GDScript doesn't need much work. Once loaded (see :ref:"
"`doc_gdscript_classes_as_resources`), the script can be instantiated with :"
"ref:`new() <class_CSharpScript_method_new>`."
msgstr ""

#: ../../docs/tutorials/scripting/cross_language_scripting.rst:82
msgid ""
"When creating ``.cs`` scripts, you should always keep in mind that the class "
"Godot will use is the one named like the ``.cs`` file itself. If that class "
"does not exist in the file, you'll see the following error: ``Invalid call. "
"Nonexistent function `new` in base``."
msgstr ""

#: ../../docs/tutorials/scripting/cross_language_scripting.rst:87
msgid "For example, MyCoolNode.cs should contain a class named MyCoolNode."
msgstr ""

#: ../../docs/tutorials/scripting/cross_language_scripting.rst:89
msgid ""
"The C# class needs to derive a Godot class, for example ``GodotObject``. "
"Otherwise, the same error will occur."
msgstr ""

#: ../../docs/tutorials/scripting/cross_language_scripting.rst:92
msgid ""
"You also need to check your ``.cs`` file is referenced in the project's ``."
"csproj`` file. Otherwise, the same error will occur."
msgstr ""

#: ../../docs/tutorials/scripting/cross_language_scripting.rst:96
msgid "Instantiating GDScript nodes from C#"
msgstr ""

#: ../../docs/tutorials/scripting/cross_language_scripting.rst:98
msgid ""
"From the C# side, everything work the same way. Once loaded, the GDScript "
"can be instantiated with :ref:`GDScript.New() <class_GDScript_method_new>`."
msgstr ""

#: ../../docs/tutorials/scripting/cross_language_scripting.rst:106
msgid ""
"Here we are using an :ref:`class_Object`, but you can use type conversion "
"like explained in :ref:`doc_c_sharp_features_type_conversion_and_casting`."
msgstr ""

#: ../../docs/tutorials/scripting/cross_language_scripting.rst:110
msgid "Accessing fields"
msgstr ""

#: ../../docs/tutorials/scripting/cross_language_scripting.rst:113
msgid "Accessing C# fields from GDScript"
msgstr ""

#: ../../docs/tutorials/scripting/cross_language_scripting.rst:115
msgid ""
"Accessing C# fields from GDScript is straightforward, you shouldn't have "
"anything to worry about."
msgstr ""

#: ../../docs/tutorials/scripting/cross_language_scripting.rst:125
msgid "Accessing GDScript fields from C#"
msgstr ""

#: ../../docs/tutorials/scripting/cross_language_scripting.rst:127
msgid ""
"As C# is statically typed, accessing GDScript from C# is a bit more "
"convoluted, you will have to use :ref:`GodotObject.Get() "
"<class_Object_method_get>` and :ref:`GodotObject.Set() "
"<class_Object_method_set>`. The first argument is the name of the field you "
"want to access."
msgstr ""

#: ../../docs/tutorials/scripting/cross_language_scripting.rst:137
msgid ""
"Keep in mind that when setting a field value you should only use types the "
"GDScript side knows about. Essentially, you want to work with built-in types "
"as described in :ref:`doc_gdscript` or classes extending :ref:`class_Object`."
msgstr ""

#: ../../docs/tutorials/scripting/cross_language_scripting.rst:142
msgid "Calling methods"
msgstr ""

#: ../../docs/tutorials/scripting/cross_language_scripting.rst:145
msgid "Calling C# methods from GDScript"
msgstr ""

#: ../../docs/tutorials/scripting/cross_language_scripting.rst:147
msgid ""
"Again, calling C# methods from GDScript should be straightforward. The "
"marshalling process will do its best to cast the arguments to match function "
"signatures. If that's impossible, you'll see the following error: ``Invalid "
"call. Nonexistent function `FunctionName```."
msgstr ""

#: ../../docs/tutorials/scripting/cross_language_scripting.rst:163
msgid "Calling GDScript methods from C#"
msgstr ""

#: ../../docs/tutorials/scripting/cross_language_scripting.rst:165
msgid ""
"To call GDScript methods from C# you'll need to use :ref:`GodotObject.Call() "
"<class_Object_method_call>`. The first argument is the name of the method "
"you want to call. The following arguments will be passed to said method."
msgstr ""

#: ../../docs/tutorials/scripting/cross_language_scripting.rst:184
msgid ""
"As you can see, if the first argument of the called method is an array, "
"you'll need to cast it as ``object``. Otherwise, each element of your array "
"will be treated as a single argument and the function signature won't match."
msgstr ""

#: ../../docs/tutorials/scripting/cross_language_scripting.rst:192
msgid ""
"A GDScript file may not inherit from a C# script. Likewise, a C# script may "
"not inherit from a GDScript file. Due to how complex this would be to "
"implement, this limitation is unlikely to be lifted in the future. See `this "
"GitHub issue <https://github.com/godotengine/godot/issues/38352>`__ for more "
"information."
msgstr ""

#: ../../docs/tutorials/scripting/creating_script_templates.rst:4
#, fuzzy
msgid "Creating script templates"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/scripting/creating_script_templates.rst:6
msgid ""
"Godot provides a way to use script templates as seen in the ``Script Create "
"Dialog`` while creating a new script:"
msgstr ""

#: ../../docs/tutorials/scripting/creating_script_templates.rst:11
msgid ""
"A set of built-in script templates are provided with the editor, but it is "
"also possible to create new ones and set them by default, both per project "
"and at editor scope."
msgstr ""

#: ../../docs/tutorials/scripting/creating_script_templates.rst:15
msgid ""
"Templates are linked to a specific node type, so when you create a script "
"you will only see the templates corresponding to that particular node, or "
"one of its parent types. For example, if you are creating a script for a "
"CharacterBody3D, you will only see templates defined for CharacterBody3Ds, "
"Node3Ds or Nodes."
msgstr ""

#: ../../docs/tutorials/scripting/creating_script_templates.rst:22
#, fuzzy
msgid "Locating the templates"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/scripting/creating_script_templates.rst:24
msgid "There are two places where templates can be managed."
msgstr ""

#: ../../docs/tutorials/scripting/creating_script_templates.rst:27
msgid "Editor-defined templates"
msgstr ""

#: ../../docs/tutorials/scripting/creating_script_templates.rst:29
msgid ""
"These are available globally throughout any project. The location of these "
"templates are determined per each OS:"
msgstr ""

#: ../../docs/tutorials/scripting/creating_script_templates.rst:32
msgid "Windows: ``%APPDATA%\\Godot\\script_templates\\``"
msgstr ""

#: ../../docs/tutorials/scripting/creating_script_templates.rst:33
msgid "Linux: ``$HOME/.config/godot/script_templates/``"
msgstr ""

#: ../../docs/tutorials/scripting/creating_script_templates.rst:34
msgid "macOS: ``$HOME/Library/Application Support/Godot/script_templates/``"
msgstr ""

#: ../../docs/tutorials/scripting/creating_script_templates.rst:36
msgid ""
"If you're getting Godot from somewhere other than the official website, such "
"as Steam, the folder might be in a different location. You can find it using "
"the Godot editor. Go to ``Editor > Open Editor Data/Settings Folder`` and it "
"will open a folder in your file browser, inside that folder is the "
"``script_templates`` folder."
msgstr ""

#: ../../docs/tutorials/scripting/creating_script_templates.rst:43
msgid "Project-defined templates"
msgstr ""

#: ../../docs/tutorials/scripting/creating_script_templates.rst:45
msgid ""
"The default path to search for templates is the ``res://script_templates/`` "
"directory. The path can be changed by configuring the ``editor/"
"script_templates_search_path`` setting in the :ref:`ProjectSettings "
"<class_ProjectSettings>`, both via code and the editor."
msgstr ""

#: ../../docs/tutorials/scripting/creating_script_templates.rst:50
msgid ""
"If no ``script_templates`` directory is found within a project, it is simply "
"ignored."
msgstr ""

#: ../../docs/tutorials/scripting/creating_script_templates.rst:54
msgid "Template organization and naming"
msgstr ""

#: ../../docs/tutorials/scripting/creating_script_templates.rst:56
msgid ""
"Both editor and project defined templates are organized in the following way:"
msgstr ""

#: ../../docs/tutorials/scripting/creating_script_templates.rst:62
msgid "where:"
msgstr ""

#: ../../docs/tutorials/scripting/creating_script_templates.rst:64
msgid ""
"``template_path`` is one of the 2 locations discussed in the previous two "
"sections"
msgstr ""

#: ../../docs/tutorials/scripting/creating_script_templates.rst:66
msgid ""
"``node_type`` is the node it will apply to (for example, :ref:`Node "
"<class_Node>`, or :ref:`CharacterBody3D <class_CharacterBody3D>`)"
msgstr ""

#: ../../docs/tutorials/scripting/creating_script_templates.rst:68
msgid ""
"``file`` is the custom name you can chose for the template (for example: "
"``platformer_movement`` or ``smooth_camera``)"
msgstr ""

#: ../../docs/tutorials/scripting/creating_script_templates.rst:70
msgid ""
"``extension``: will indicate which language the template will apply to (it "
"should be ``gd`` for GDScript or ``cs`` for C#)"
msgstr ""

#: ../../docs/tutorials/scripting/creating_script_templates.rst:74
msgid "``template_scripts/Node/smooth_camera.gd``"
msgstr ""

#: ../../docs/tutorials/scripting/creating_script_templates.rst:75
msgid "``template_scripts/CharacterBody3D/platformer_movement.gd``"
msgstr ""

#: ../../docs/tutorials/scripting/creating_script_templates.rst:79
msgid "Default behaviour and overriding it"
msgstr ""

#: ../../docs/tutorials/scripting/creating_script_templates.rst:81
msgid "By default:"
msgstr ""

#: ../../docs/tutorials/scripting/creating_script_templates.rst:83
msgid ""
"the template's name is the same as the file name (minus the extension, "
"prettyfied)"
msgstr ""

#: ../../docs/tutorials/scripting/creating_script_templates.rst:85
msgid "the description is empty"
msgstr ""

#: ../../docs/tutorials/scripting/creating_script_templates.rst:87
msgid "the space indent is set to 4"
msgstr ""

#: ../../docs/tutorials/scripting/creating_script_templates.rst:89
msgid "the template will not be set as the default for the given node"
msgstr ""

#: ../../docs/tutorials/scripting/creating_script_templates.rst:92
msgid ""
"It is possible to customize this behaviour by adding meta headers at the "
"start of your file, like this:"
msgstr ""

#: ../../docs/tutorials/scripting/creating_script_templates.rst:112
msgid ""
"In this case, the name will be set to \"Platformer movement\", with the "
"given custom description, and it will be set as the default template for the "
"node in which directory it has been saved."
msgstr ""

#: ../../docs/tutorials/scripting/creating_script_templates.rst:115
msgid ""
"This is an example of utilizing custom templates at editor and project level:"
msgstr ""

#: ../../docs/tutorials/scripting/creating_script_templates.rst:119
msgid ""
"The script templates have the same extension as the regular script files. "
"This may lead to an issue of a script parser treating those templates as "
"actual scripts within a project. To avoid this, make sure to ignore the "
"directory containing them by creating an empty ``.gdignore`` file. The "
"directory won't be visible throughout the project's filesystem anymore, yet "
"the templates can be modified by an external text editor anytime."
msgstr ""

#: ../../docs/tutorials/scripting/creating_script_templates.rst:128
msgid ""
"By default, every C# file inside the project directory is included in the "
"compilation. Script templates must be manually excluded from the C# project "
"to avoid build errors. See `Exclude files from the build <https://learn."
"microsoft.com/en-us/visualstudio/msbuild/how-to-exclude-files-from-the-"
"build>`_ in the Microsoft documentation."
msgstr ""

#: ../../docs/tutorials/scripting/creating_script_templates.rst:132
msgid ""
"It is possible to create editor-level templates that have the same level as "
"a project-specific templates, and also that have the same name as a built-in "
"one, all will be shown on the new script dialog."
msgstr ""

#: ../../docs/tutorials/scripting/creating_script_templates.rst:137
msgid "Default template"
msgstr ""

#: ../../docs/tutorials/scripting/creating_script_templates.rst:139
msgid ""
"To override the default template, create a custom template at editor or "
"project level inside a ``Node`` directory (or a more specific type, if only "
"a subtype wants to be overridden) and start the file with the ``meta-"
"default: true`` header."
msgstr ""

#: ../../docs/tutorials/scripting/creating_script_templates.rst:143
msgid ""
"Only one template can be set as default at the same time for the same node "
"type."
msgstr ""

#: ../../docs/tutorials/scripting/creating_script_templates.rst:145
msgid ""
"The ``Default`` templates for basic Nodes, for both GDScript and C#, are "
"shown here so you can use these as the base for creating other templates:"
msgstr ""

#: ../../docs/tutorials/scripting/creating_script_templates.rst:187
msgid ""
"The Godot editor provides a set of useful built-in node-specific templates, "
"such as ``basic_movement`` for both :ref:`CharacterBody2D "
"<class_CharacterBody2D>` and :ref:`CharacterBody3D <class_CharacterBody3D>` "
"and ``plugin`` for :ref:`EditorPlugin <class_EditorPlugin>`."
msgstr ""

#: ../../docs/tutorials/scripting/creating_script_templates.rst:193
msgid "List of template placeholders"
msgstr ""

#: ../../docs/tutorials/scripting/creating_script_templates.rst:195
msgid ""
"The following describes the complete list of built-in template placeholders "
"which are currently implemented."
msgstr ""

#: ../../docs/tutorials/scripting/creating_script_templates.rst:199
msgid "Base placeholders"
msgstr ""

#: ../../docs/tutorials/scripting/creating_script_templates.rst:202
msgid "Placeholder"
msgstr ""

#: ../../docs/tutorials/scripting/creating_script_templates.rst:204
msgid "``_BINDINGS_NAMESPACE_``"
msgstr ""

#: ../../docs/tutorials/scripting/creating_script_templates.rst:204
msgid "The name of the Godot namespace (used in C# only)."
msgstr ""

#: ../../docs/tutorials/scripting/creating_script_templates.rst:206
msgid "``_CLASS_``"
msgstr ""

#: ../../docs/tutorials/scripting/creating_script_templates.rst:206
msgid "The name of the new class."
msgstr ""

#: ../../docs/tutorials/scripting/creating_script_templates.rst:208
msgid "``_BASE_``"
msgstr ""

#: ../../docs/tutorials/scripting/creating_script_templates.rst:208
msgid "The base type a new script inherits from."
msgstr ""

#: ../../docs/tutorials/scripting/creating_script_templates.rst:210
msgid "``_TS_``"
msgstr ""

#: ../../docs/tutorials/scripting/creating_script_templates.rst:210
msgid ""
"Indentation placeholder. The exact type and number of whitespace characters "
"used for indentation is determined by the ``text_editor/indent/type`` and "
"``text_editor/indent/size`` settings in the :ref:`EditorSettings "
"<class_EditorSettings>` respectively. Can be overridden by the ``meta-space-"
"indent`` header on the template."
msgstr ""

#: ../../docs/tutorials/scripting/creating_script_templates.rst:220
msgid "Type placeholders"
msgstr ""

#: ../../docs/tutorials/scripting/creating_script_templates.rst:222
msgid ""
"There used to be, in Godot 3.x, placeholders for GDScript type hints that "
"would get replaced whenever a template was used to create a new script, such "
"as: ``%INT_TYPE%``, ``%STRING_TYPE%``, ``%FLOAT_TYPE%`` or ``%VOID_RETURN%``."
msgstr ""

#: ../../docs/tutorials/scripting/creating_script_templates.rst:226
msgid ""
"The placeholders no longer work for Godot 4.x, but if the setting "
"``text_editor/completion/add_type_hints`` from :ref:`EditorSettings "
"<class_EditorSettings>` is disabled, type hints for parameters and return "
"types will be automatically removed for a few base types:"
msgstr ""

#: ../../docs/tutorials/scripting/creating_script_templates.rst:232
msgid "``int``"
msgstr ""

#: ../../docs/tutorials/scripting/creating_script_templates.rst:234
msgid "``Array[String]``"
msgstr ""

#: ../../docs/tutorials/scripting/creating_script_templates.rst:235
msgid "``float``"
msgstr ""

#: ../../docs/tutorials/scripting/creating_script_templates.rst:236
msgid "``void``"
msgstr ""

#: ../../docs/tutorials/scripting/creating_script_templates.rst:237
msgid "``:=`` will be transformed into ``=``"
msgstr ""

#: ../../docs/tutorials/scripting/evaluating_expressions.rst:4
msgid "Evaluating expressions"
msgstr ""

#: ../../docs/tutorials/scripting/evaluating_expressions.rst:6
msgid ""
"Godot provides an :ref:`class_Expression` class you can use to evaluate "
"expressions."
msgstr ""

#: ../../docs/tutorials/scripting/evaluating_expressions.rst:8
msgid "An expression can be:"
msgstr ""

#: ../../docs/tutorials/scripting/evaluating_expressions.rst:10
msgid "A mathematical expression such as ``(2 + 4) * 16/4.0``."
msgstr ""

#: ../../docs/tutorials/scripting/evaluating_expressions.rst:11
msgid "A built-in method call like ``deg_to_rad(90)``."
msgstr ""

#: ../../docs/tutorials/scripting/evaluating_expressions.rst:12
msgid ""
"A method call on an user-provided script like ``update_health()``, if "
"``base_instance`` is set to a value other than ``null`` when calling :ref:"
"`Expression.execute() <class_Expression_method_execute>`."
msgstr ""

#: ../../docs/tutorials/scripting/evaluating_expressions.rst:18
msgid ""
"The Expression class is independent from GDScript. It's available even if "
"you compile Godot with the GDScript module disabled."
msgstr ""

#: ../../docs/tutorials/scripting/evaluating_expressions.rst:24
msgid "To evaluate a mathematical expression, use::"
msgstr ""

#: ../../docs/tutorials/scripting/evaluating_expressions.rst:31
msgid "The following operators are available:"
msgstr ""

#: ../../docs/tutorials/scripting/evaluating_expressions.rst:34
#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:436
msgid "Operator"
msgstr ""

#: ../../docs/tutorials/scripting/evaluating_expressions.rst:34
#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:817
#: ../../docs/contributing/development/core_and_modules/custom_godot_servers.rst:502
msgid "Notes"
msgstr ""

#: ../../docs/tutorials/scripting/evaluating_expressions.rst:36
msgid "Addition ``+``"
msgstr ""

#: ../../docs/tutorials/scripting/evaluating_expressions.rst:36
msgid ""
"Can also be used to concatenate strings and arrays: - ``\"hello\" + \" "
"world\"`` = ``hello world`` - ``[1, 2] + [3, 4]`` = ``[1, 2, 3, 4]``"
msgstr ""

#: ../../docs/tutorials/scripting/evaluating_expressions.rst:40
#, fuzzy
msgid "Subtraction (``-``)"
msgstr "Uvod"

#: ../../docs/tutorials/scripting/evaluating_expressions.rst:42
msgid "Multiplication (``*``)"
msgstr ""

#: ../../docs/tutorials/scripting/evaluating_expressions.rst:44
msgid "Division (``/``)"
msgstr ""

#: ../../docs/tutorials/scripting/evaluating_expressions.rst:44
msgid ""
"Performs and integer division if both operands are integers. If at least one "
"of them is a floating-point number, returns a floating-point value."
msgstr ""

#: ../../docs/tutorials/scripting/evaluating_expressions.rst:47
msgid "Modulo (``%``)"
msgstr ""

#: ../../docs/tutorials/scripting/evaluating_expressions.rst:47
msgid "Returns the remainder of an integer division."
msgstr ""

#: ../../docs/tutorials/scripting/evaluating_expressions.rst:50
msgid ""
"Spaces around operators are optional. Also, keep in mind the usual `order of "
"operations <https://en.wikipedia.org/wiki/Order_of_operations>`__ applies. "
"Use parentheses to override the order of operations if needed."
msgstr ""

#: ../../docs/tutorials/scripting/evaluating_expressions.rst:54
msgid ""
"All the Variant types supported in Godot can be used: integers, floating-"
"point numbers, strings, arrays, dictionaries, colors, vectors, …"
msgstr ""

#: ../../docs/tutorials/scripting/evaluating_expressions.rst:57
msgid "Arrays and dictionaries can be indexed like in GDScript::"
msgstr ""

#: ../../docs/tutorials/scripting/evaluating_expressions.rst:74
msgid "Passing variables to an expression"
msgstr ""

#: ../../docs/tutorials/scripting/evaluating_expressions.rst:76
msgid ""
"You can pass variables to an expression. These variables will then become "
"available in the expression's \"context\" and will be substituted when used "
"in the expression::"
msgstr ""

#: ../../docs/tutorials/scripting/evaluating_expressions.rst:89
msgid ""
"Both the variable names and variable values **must** be specified as an "
"array, even if you only define one variable. Also, variable names are **case-"
"sensitive**."
msgstr ""

#: ../../docs/tutorials/scripting/evaluating_expressions.rst:93
msgid "Setting a base instance for the expression"
msgstr ""

#: ../../docs/tutorials/scripting/evaluating_expressions.rst:95
msgid ""
"By default, an expression has a base instance of ``null``. This means the "
"expression has no base instance associated to it."
msgstr ""

#: ../../docs/tutorials/scripting/evaluating_expressions.rst:98
msgid ""
"When calling :ref:`Expression.execute() <class_Expression_method_execute>`, "
"you can set the value of the ``base_instance`` parameter to a specific "
"object instance such as ``self``, another script instance or even a "
"singleton::"
msgstr ""

#: ../../docs/tutorials/scripting/evaluating_expressions.rst:119
msgid "Associating a base instance allows doing the following:"
msgstr ""

#: ../../docs/tutorials/scripting/evaluating_expressions.rst:121
msgid "Reference the instance's constants (``const``) in the expression."
msgstr ""

#: ../../docs/tutorials/scripting/evaluating_expressions.rst:122
msgid "Reference the instance's member variables (``var``) in the expression."
msgstr ""

#: ../../docs/tutorials/scripting/evaluating_expressions.rst:123
msgid ""
"Call methods defined in the instance and use their return values in the "
"expression."
msgstr ""

#: ../../docs/tutorials/scripting/evaluating_expressions.rst:127
msgid ""
"Setting a base instance to a value other than ``null`` allows referencing "
"constants, member variables, and calling all methods defined in the script "
"attached to the instance. Allowing users to enter expressions may allow "
"cheating in your game, or may even introduce security vulnerabilities if you "
"allow arbitrary clients to run expressions on other players' devices."
msgstr ""

#: ../../docs/tutorials/scripting/evaluating_expressions.rst:134
msgid "Example script"
msgstr ""

#: ../../docs/tutorials/scripting/evaluating_expressions.rst:136
msgid "The script below demonstrates what the Expression class is capable of::"
msgstr ""

#: ../../docs/tutorials/scripting/evaluating_expressions.rst:181
msgid "The output from the script will be::"
msgstr ""

#: ../../docs/tutorials/scripting/evaluating_expressions.rst:199
#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1094
msgid "Built-in functions"
msgstr ""

#: ../../docs/tutorials/scripting/evaluating_expressions.rst:201
msgid ""
"All methods in the :ref:`Global Scope<class_@GlobalScope>` are available in "
"the Expression class, even if no base instance is bound to the expression. "
"The same parameters and return types are available."
msgstr ""

#: ../../docs/tutorials/scripting/evaluating_expressions.rst:205
msgid ""
"However, unlike GDScript, parameters are **always required** even if they're "
"specified as being optional in the class reference. In contrast, this "
"restriction on arguments doesn't apply to user-made functions when you bind "
"a base instance to the expression."
msgstr ""

#: ../../docs/tutorials/scripting/change_scenes_manually.rst:4
msgid "Change scenes manually"
msgstr ""

#: ../../docs/tutorials/scripting/change_scenes_manually.rst:6
msgid ""
"Sometimes it helps to have more control over how one swaps scenes around. A :"
"ref:`Viewport <class_Viewport>`'s child nodes will render to the image it "
"generates, this holds true even for nodes outside of the \"current\" scene. "
"Autoloads fall into this category, but so do scenes which one instances and "
"adds to the tree at runtime:"
msgstr ""

#: ../../docs/tutorials/scripting/change_scenes_manually.rst:38
msgid ""
"To complete the cycle and swap out the new scene with the old one, "
"developers have a choice to make. Many strategies exist for removing a scene "
"from view of the :ref:`Viewport <class_Viewport>`. The tradeoffs involve "
"balancing operation speed and memory consumption as well as balancing data "
"access and integrity."
msgstr ""

#: ../../docs/tutorials/scripting/change_scenes_manually.rst:44
msgid ""
"**We can delete the existing scene.** :ref:`SceneTree.change_scene_to_file() "
"<class_SceneTree_method_change_scene_to_file>` and :ref:`SceneTree."
"change_scene_to_packed() <class_SceneTree_method_change_scene_to_packed>` "
"will delete the current scene immediately. Developers can also delete the "
"main scene though. Assuming the root node's name is \"Main\", one could do "
"``get_node(\"/root/Main\").free()`` to delete the whole scene."
msgstr ""

#: ../../docs/tutorials/scripting/change_scenes_manually.rst:51
msgid "Unloads memory."
msgstr ""

#: ../../docs/tutorials/scripting/change_scenes_manually.rst:53
msgid "Pro: RAM is no longer dragging the dead weight."
msgstr ""

#: ../../docs/tutorials/scripting/change_scenes_manually.rst:55
msgid ""
"Con: Returning to that scene is now more expensive since it must be loaded "
"back into memory again (takes time AND memory). Not a problem if returning "
"soon is unnecessary."
msgstr ""

#: ../../docs/tutorials/scripting/change_scenes_manually.rst:59
msgid ""
"Con: No longer have access to that scene's data. Not a problem if using that "
"data soon is unnecessary."
msgstr ""

#: ../../docs/tutorials/scripting/change_scenes_manually.rst:62
msgid ""
"Note: It can be useful to preserve the data in a soon-to-be-deleted scene by "
"re-attaching one or more of its nodes to a different scene, or even directly "
"to the :ref:`SceneTree <class_SceneTree>`."
msgstr ""

#: ../../docs/tutorials/scripting/change_scenes_manually.rst:66
msgid "Processing stops."
msgstr ""

#: ../../docs/tutorials/scripting/change_scenes_manually.rst:68
msgid ""
"Pro: No nodes means no process, physics process, or input handling. The CPU "
"is available to work on the new scene's contents."
msgstr ""

#: ../../docs/tutorials/scripting/change_scenes_manually.rst:71
msgid ""
"Con: Those nodes' processing and input handling no longer operate. Not a "
"problem if using the updated data is unnecessary."
msgstr ""

#: ../../docs/tutorials/scripting/change_scenes_manually.rst:74
msgid ""
"**We can hide the existing scene.** By changing the visibility or collision "
"detection of the nodes, we can hide the entire node sub-tree from the "
"player's perspective."
msgstr ""

#: ../../docs/tutorials/scripting/change_scenes_manually.rst:78
msgid "Memory still exists."
msgstr ""

#: ../../docs/tutorials/scripting/change_scenes_manually.rst:80
msgid "Pro: One can still access the data if need be."
msgstr ""

#: ../../docs/tutorials/scripting/change_scenes_manually.rst:82
msgid "Pro: There's no need to move any more nodes around to save data."
msgstr ""

#: ../../docs/tutorials/scripting/change_scenes_manually.rst:84
msgid ""
"Con: More data is being kept in memory which will be become a problem on "
"memory-sensitive platforms like web or mobile."
msgstr ""

#: ../../docs/tutorials/scripting/change_scenes_manually.rst:87
msgid "Processing continues."
msgstr ""

#: ../../docs/tutorials/scripting/change_scenes_manually.rst:89
msgid ""
"Pro: Data continues to receive processing updates, so the scene will keep "
"updated any data within it that relies on delta time or frame data."
msgstr ""

#: ../../docs/tutorials/scripting/change_scenes_manually.rst:93
msgid ""
"Pro: Nodes are still members of groups (since groups belong to the :ref:"
"`SceneTree <class_SceneTree>`)."
msgstr ""

#: ../../docs/tutorials/scripting/change_scenes_manually.rst:96
msgid ""
"Con: The CPU's attention is now divided between both scenes. Too much load "
"could result in low frame rates. One should be sure to test performance as "
"they go to ensure the target platform can support the load they are giving "
"it."
msgstr ""

#: ../../docs/tutorials/scripting/change_scenes_manually.rst:101
msgid ""
"**We can remove the existing scene from the tree.** Assign a variable to the "
"existing scene's root node. Then use :ref:`Node.remove_child(Node) "
"<class_Node_method_remove_child>` to detach the entire scene from the tree."
msgstr ""

#: ../../docs/tutorials/scripting/change_scenes_manually.rst:106
msgid "Memory still exists (similar pros/cons as with hiding it from view)."
msgstr ""

#: ../../docs/tutorials/scripting/change_scenes_manually.rst:108
msgid "Processing stops (similar pros/cons as with deleting it completely)."
msgstr ""

#: ../../docs/tutorials/scripting/change_scenes_manually.rst:110
msgid ""
"Pro: This variation of \"hiding\" it is much easier to show/hide. Rather "
"than potentially keeping track of multiple changes to the scene, one must "
"only call the one method add/remove_child pair of methods. It is similar to "
"disabling game objects in other engines."
msgstr ""

#: ../../docs/tutorials/scripting/change_scenes_manually.rst:115
msgid ""
"Con: Unlike with hiding it from view only, the data contained within the "
"scene will become stale if it relies on delta time, input, groups, or other "
"data that is derived from :ref:`SceneTree <class_SceneTree>` access."
msgstr ""

#: ../../docs/tutorials/scripting/change_scenes_manually.rst:120
msgid ""
"There are also cases where one may wish to have many scenes present at the "
"same time. Perhaps one is adding their own singleton at runtime, or "
"preserving a a scene's data between scene changes (adding the scene to the "
"root node)."
msgstr ""

#: ../../docs/tutorials/scripting/change_scenes_manually.rst:133
msgid ""
"Perhaps instead they wish to display multiple scenes at the same time using :"
"ref:`SubViewportContainers <class_SubViewportContainer>`. This is optimal in "
"cases where the intent is to render different content in different parts of "
"the screen. Minimaps and split-screen multiplayer are good examples."
msgstr ""

#: ../../docs/tutorials/scripting/change_scenes_manually.rst:138
msgid ""
"Each option will have cases where it is best appropriate, so one must "
"examine the effects of each and determine what path best fits their unique "
"situation."
msgstr ""

#: ../../docs/tutorials/scripting/instancing_with_signals.rst:7
msgid "Instancing with signals"
msgstr ""

#: ../../docs/tutorials/scripting/instancing_with_signals.rst:9
msgid ""
"Signals provide a way to decouple game objects, allowing you to avoid "
"forcing a fixed arrangement of nodes. One sign that a signal might be called "
"for is when you find yourself using ``get_parent()``. Referring directly to "
"a node's parent means that you can't easily move that node to another "
"location in the scene tree. This can be especially problematic when you are "
"instancing objects at runtime and may want to place them in an arbitrary "
"location in the running scene tree."
msgstr ""

#: ../../docs/tutorials/scripting/instancing_with_signals.rst:16
msgid "Below we'll consider an example of such a situation: firing bullets."
msgstr ""

#: ../../docs/tutorials/scripting/instancing_with_signals.rst:19
msgid "Shooting example"
msgstr ""

#: ../../docs/tutorials/scripting/instancing_with_signals.rst:21
msgid ""
"Consider a player character that can rotate and shoot towards the mouse. "
"Every time the mouse button is clicked, we create an instance of the bullet "
"at the player's location. See :ref:`doc_instancing` for details."
msgstr ""

#: ../../docs/tutorials/scripting/instancing_with_signals.rst:25
msgid ""
"We'll use an ``Area2D`` for the bullet, which moves in a straight line at a "
"given velocity:"
msgstr ""

#: ../../docs/tutorials/scripting/instancing_with_signals.rst:52
msgid ""
"However, if the bullets are added as children of the player, then they will "
"remain \"attached\" to the player as it rotates:"
msgstr ""

#: ../../docs/tutorials/scripting/instancing_with_signals.rst:57
msgid ""
"Instead, we need the bullets to be independent of the player's movement - "
"once fired, they should continue traveling in a straight line and the player "
"can no longer affect them. Instead of being added to the scene tree as a "
"child of the player, it makes more sense to add the bullet as a child of the "
"\"main\" game scene, which may be the player's parent or even further up the "
"tree."
msgstr ""

#: ../../docs/tutorials/scripting/instancing_with_signals.rst:63
msgid "You could do this by adding the bullet to the main scene directly:"
msgstr ""

#: ../../docs/tutorials/scripting/instancing_with_signals.rst:76
msgid ""
"However, this will lead to a different problem. Now if you try to test your "
"\"Player\" scene independently, it will crash on shooting, because there is "
"no parent node to access. This makes it a lot harder to test your player "
"code independently and also means that if you decide to change your main "
"scene's node structure, the player's parent may no longer be the appropriate "
"node to receive the bullets."
msgstr ""

#: ../../docs/tutorials/scripting/instancing_with_signals.rst:83
msgid ""
"The solution to this is to use a signal to \"emit\" the bullets from the "
"player. The player then has no need to \"know\" what happens to the bullets "
"after that - whatever node is connected to the signal can \"receive\" the "
"bullets and take the appropriate action to spawn them."
msgstr ""

#: ../../docs/tutorials/scripting/instancing_with_signals.rst:88
msgid "Here is the code for the player using signals to emit the bullet:"
msgstr ""

#: ../../docs/tutorials/scripting/instancing_with_signals.rst:135
msgid ""
"In the main scene, we then connect the player's signal (it will appear in "
"the \"Node\" tab of the Inspector)"
msgstr ""

#: ../../docs/tutorials/scripting/instancing_with_signals.rst:159
msgid ""
"Now the bullets will maintain their own movement independent of the player's "
"rotation:"
msgstr ""

#: ../../docs/tutorials/scripting/pausing_games.rst:4
msgid "Pausing games and process mode"
msgstr ""

#: ../../docs/tutorials/scripting/pausing_games.rst:9
msgid ""
"In most games it is desirable to, at some point, interrupt the game to do "
"something else, such as taking a break or changing options. Implementing a "
"fine-grained control for what can be paused (and what cannot) is a lot of "
"work, so a simple framework for pausing is provided in Godot."
msgstr ""

#: ../../docs/tutorials/scripting/pausing_games.rst:16
msgid "How pausing works"
msgstr ""

#: ../../docs/tutorials/scripting/pausing_games.rst:18
msgid ""
"To pause the game the pause state must be set. This is done by assigning "
"``true`` to the :ref:`SceneTree.paused <class_SceneTree_property_paused>` "
"property:"
msgstr ""

#: ../../docs/tutorials/scripting/pausing_games.rst:30
msgid ""
"Doing this will cause two things. First, 2D and 3D physics will be stopped "
"for all nodes. Second, the behavior of certain nodes will stop or start "
"depending on their process mode."
msgstr ""

#: ../../docs/tutorials/scripting/pausing_games.rst:34
msgid ""
"The physics servers can be made active while the game is paused by using "
"their ``set_active`` methods."
msgstr ""

#: ../../docs/tutorials/scripting/pausing_games.rst:38
msgid "Process Modes"
msgstr ""

#: ../../docs/tutorials/scripting/pausing_games.rst:40
msgid ""
"Each node in Godot has a \"Process Mode\" that defines when it processes. It "
"can be found and changed under a node's :ref:`Node <class_Node>` properties "
"in the inspector."
msgstr ""

#: ../../docs/tutorials/scripting/pausing_games.rst:45
msgid "You can also alter the property with code:"
msgstr ""

#: ../../docs/tutorials/scripting/pausing_games.rst:60
msgid "This is what each mode tells a node to do:"
msgstr ""

#: ../../docs/tutorials/scripting/pausing_games.rst:62
msgid ""
"**Inherit**: Process depending on the state of the parent, grandparent, etc. "
"The first parent that has a non-Inherit state."
msgstr ""

#: ../../docs/tutorials/scripting/pausing_games.rst:64
msgid ""
"**Pausable**: Process the node (and its children in Inherit mode) only when "
"the game is not paused."
msgstr ""

#: ../../docs/tutorials/scripting/pausing_games.rst:66
msgid ""
"**WhenPaused**: Process the node (and its children in Inherit mode) *only* "
"when the game is paused."
msgstr ""

#: ../../docs/tutorials/scripting/pausing_games.rst:68
msgid ""
"**Always**: Process the node (and its children in Inherit mode) no matter "
"what. Paused or not, this node will process."
msgstr ""

#: ../../docs/tutorials/scripting/pausing_games.rst:70
msgid ""
"**Disabled**: The node (and its children in Inherit mode) will not process "
"at all."
msgstr ""

#: ../../docs/tutorials/scripting/pausing_games.rst:73
msgid ""
"By default, all nodes have this property in the \"Inherit\" state. If the "
"parent is set to \"Inherit\", then the grandparent will be checked and so "
"on. If a state can't be found in any of the grandparents, the pause state in "
"SceneTree is used. This means that, by default, when the game is paused "
"every node will be paused. Several things happen when a node stops "
"processing."
msgstr ""

#: ../../docs/tutorials/scripting/pausing_games.rst:79
msgid ""
"The ``_process``, ``_physics_process``, ``_input``, and ``_input_event`` "
"functions will not be called. However signals still work and cause their "
"connected function to run, even if that function's script is attached to a "
"node that is not currently being processed."
msgstr ""

#: ../../docs/tutorials/scripting/pausing_games.rst:83
msgid ""
"Animation nodes will pause their current animation, audio nodes will pause "
"their current audio stream, and particles will pause. These resume "
"automatically when the game is no longer paused."
msgstr ""

#: ../../docs/tutorials/scripting/pausing_games.rst:87
msgid ""
"It is important to note that even if a node is processing while the game is "
"paused physics will **NOT** work for it by default. As stated earlier this "
"is because the physics servers are turned off. The physics servers can be "
"made active while the game is paused by using their ``set_active`` methods."
msgstr ""

#: ../../docs/tutorials/scripting/pausing_games.rst:93
#, fuzzy
msgid "Pause menu example"
msgstr "Windows"

#: ../../docs/tutorials/scripting/pausing_games.rst:95
msgid "Start by creating a button that will be used to pause the game."
msgstr ""

#: ../../docs/tutorials/scripting/pausing_games.rst:97
msgid ""
"Create a menu containing a close button, set the **Process Mode** of the "
"menu's root node to **When Paused**, then hide the menu. Since the process "
"mode is set to **When Paused** on the root node, all its children and "
"grandchildren will inherit that process mode. This way, all the nodes in the "
"menu will start processing when the game is paused."
msgstr ""

#: ../../docs/tutorials/scripting/pausing_games.rst:102
msgid ""
"Attach a script to the menu's root node, connect the pause button created "
"earlier to a new method in the script, and inside that method pause the game "
"and show the pause menu."
msgstr ""

#: ../../docs/tutorials/scripting/pausing_games.rst:120
msgid ""
"Finally, connect the menu's close button to a new method in the script. "
"Inside that method, unpause the game and hide the pause menu."
msgstr ""

#: ../../docs/tutorials/scripting/pausing_games.rst:138
msgid "You should now have a working pause menu."
msgstr ""

#: ../../docs/tutorials/scripting/filesystem.rst:4
msgid "File system"
msgstr ""

#: ../../docs/tutorials/scripting/filesystem.rst:9
msgid ""
"A file system manages how assets are stored and how they are accessed. A "
"well-designed file system also allows multiple developers to edit the same "
"source files and assets while collaborating. Godot stores all assets as "
"files in its file system."
msgstr ""

#: ../../docs/tutorials/scripting/filesystem.rst:15
msgid "Implementation"
msgstr ""

#: ../../docs/tutorials/scripting/filesystem.rst:17
msgid ""
"The file system stores resources on disk. Anything, from a script, to a "
"scene or a PNG image is a resource to the engine. If a resource contains "
"properties that reference other resources on disk, the paths to those "
"resources are also included. If a resource has sub-resources that are built-"
"in, the resource is saved in a single file together with all the bundled sub-"
"resources. For example, a font resource is often bundled together with the "
"font textures."
msgstr ""

#: ../../docs/tutorials/scripting/filesystem.rst:24
msgid ""
"The Godot file system avoids using metadata files. Existing asset managers "
"and VCSs are better than anything we can implement, so Godot tries its best "
"to play along with Subversion, Git, Mercurial, etc."
msgstr ""

#: ../../docs/tutorials/scripting/filesystem.rst:28
msgid "Example of file system contents:"
msgstr ""

#: ../../docs/tutorials/scripting/filesystem.rst:39
msgid "project.godot"
msgstr ""

#: ../../docs/tutorials/scripting/filesystem.rst:41
msgid ""
"The ``project.godot`` file is the project description file, and it is always "
"found at the root of the project. In fact, its location defines where the "
"root is. This is the first file that Godot looks for when opening a project."
msgstr ""

#: ../../docs/tutorials/scripting/filesystem.rst:45
msgid ""
"This file contains the project configuration in plain text, using the win."
"ini format. Even an empty ``project.godot`` can function as a basic "
"definition of a blank project."
msgstr ""

#: ../../docs/tutorials/scripting/filesystem.rst:50
msgid "Path delimiter"
msgstr ""

#: ../../docs/tutorials/scripting/filesystem.rst:52
msgid ""
"Godot only supports ``/`` as a path delimiter. This is done for portability "
"reasons. All operating systems support this, even Windows, so a path such as "
"``C:\\project\\project.godot`` needs to be typed as ``C:/project/project."
"godot``."
msgstr ""

#: ../../docs/tutorials/scripting/filesystem.rst:58
msgid "Resource path"
msgstr ""

#: ../../docs/tutorials/scripting/filesystem.rst:60
msgid ""
"When accessing resources, using the host OS file system layout can be "
"cumbersome and non-portable. To solve this problem, the special path ``res://"
"`` was created."
msgstr ""

#: ../../docs/tutorials/scripting/filesystem.rst:64
msgid ""
"The path ``res://`` will always point at the project root (where ``project."
"godot`` is located, so ``res://project.godot`` is always valid)."
msgstr ""

#: ../../docs/tutorials/scripting/filesystem.rst:68
msgid ""
"This file system is read-write only when running the project locally from "
"the editor. When exported or when running on different devices (such as "
"phones or consoles, or running from DVD), the file system will become read-"
"only and writing will no longer be permitted."
msgstr ""

#: ../../docs/tutorials/scripting/filesystem.rst:74
msgid "User path"
msgstr ""

#: ../../docs/tutorials/scripting/filesystem.rst:76
msgid ""
"Writing to disk is still needed for tasks such as saving game state or "
"downloading content packs. To this end, the engine ensures that there is a "
"special path ``user://`` that is always writable. This path resolves "
"differently depending on the OS the project is running on. Local path "
"resolution is further explained in :ref:`doc_data_paths`."
msgstr ""

#: ../../docs/tutorials/scripting/filesystem.rst:83
msgid "Host file system"
msgstr ""

#: ../../docs/tutorials/scripting/filesystem.rst:85
msgid ""
"Alternatively host file system paths can also be used, but this is not "
"recommended for a released product as these paths are not guaranteed to work "
"on all platforms. However, using host file system paths can be useful when "
"writing development tools in Godot."
msgstr ""

#: ../../docs/tutorials/scripting/filesystem.rst:91
msgid "Drawbacks"
msgstr ""

#: ../../docs/tutorials/scripting/filesystem.rst:93
msgid ""
"There are some drawbacks to this file system design. The first issue is that "
"moving assets around (renaming them or moving them from one path to another "
"inside the project) will break existing references to these assets. These "
"references will have to be re-defined to point at the new asset location."
msgstr ""

#: ../../docs/tutorials/scripting/filesystem.rst:98
msgid ""
"To avoid this, do all your move, delete and rename operations from within "
"Godot, on the FileSystem dock. Never move assets from outside Godot, or "
"dependencies will have to be fixed manually (Godot detects this and helps "
"you fix them anyway, but why go the hard route?)."
msgstr ""

#: ../../docs/tutorials/scripting/filesystem.rst:103
msgid ""
"The second is that, under Windows and macOS, file and path names are case "
"insensitive. If a developer working in a case insensitive host file system "
"saves an asset as ``myfile.PNG``, but then references it as ``myfile.png``, "
"it will work fine on their platform, but not on other platforms, such as "
"Linux, Android, etc. This may also apply to exported binaries, which use a "
"compressed package to store all files."
msgstr ""

#: ../../docs/tutorials/scripting/filesystem.rst:109
msgid ""
"It is recommended that your team clearly define a naming convention for "
"files when working with Godot. One fool-proof convention is to only allow "
"lowercase file and path names."
msgstr ""

#: ../../docs/tutorials/scripting/resources.rst:7
msgid "Nodes and resources"
msgstr ""

#: ../../docs/tutorials/scripting/resources.rst:9
msgid ""
"Up to this tutorial, we focused on the :ref:`Node <class_Node>` class in "
"Godot as that's the one you use to code behavior and most of the engine's "
"features rely on it. There is another datatype that is just as important: :"
"ref:`Resource <class_Resource>`."
msgstr ""

#: ../../docs/tutorials/scripting/resources.rst:15
msgid ""
"*Nodes* give you functionality: they draw sprites, 3D models, simulate "
"physics, arrange user interfaces, etc. **Resources** are **data "
"containers**. They don't do anything on their own: instead, nodes use the "
"data contained in resources."
msgstr ""

#: ../../docs/tutorials/scripting/resources.rst:19
msgid ""
"Anything Godot saves or loads from disk is a resource. Be it a scene (a ``."
"tscn`` or an ``.scn`` file), an image, a script... Here are some :ref:"
"`Resource <class_Resource>` examples:"
msgstr ""

#: ../../docs/tutorials/scripting/resources.rst:22
#, fuzzy
msgid ":ref:`Texture <class_Texture>`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/scripting/resources.rst:23
#, fuzzy
msgid ":ref:`Script <class_Script>`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/scripting/resources.rst:24
#, fuzzy
msgid ":ref:`Mesh <class_Mesh>`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/scripting/resources.rst:25
#, fuzzy
msgid ":ref:`Animation <class_Animation>`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/scripting/resources.rst:26
#, fuzzy
msgid ":ref:`AudioStream <class_AudioStream>`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/scripting/resources.rst:27
#, fuzzy
msgid ":ref:`Font <class_Font>`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/scripting/resources.rst:28
#, fuzzy
msgid ":ref:`Translation <class_Translation>`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/scripting/resources.rst:30
msgid ""
"When the engine loads a resource from disk, **it only loads it once**. If a "
"copy of that resource is already in memory, trying to load the resource "
"again will return the same copy every time. As resources only contain data, "
"there is no need to duplicate them."
msgstr ""

#: ../../docs/tutorials/scripting/resources.rst:35
msgid ""
"Every object, be it a Node or a Resource, can export properties. There are "
"many types of Properties, like String, integer, Vector2, etc., and any of "
"these types can become a resource. This means that both nodes and resources "
"can contain resources as properties:"
msgstr ""

#: ../../docs/tutorials/scripting/resources.rst:43
msgid "External vs built-in"
msgstr ""

#: ../../docs/tutorials/scripting/resources.rst:45
msgid "There are two ways to save resources. They can be:"
msgstr ""

#: ../../docs/tutorials/scripting/resources.rst:47
msgid "**External** to a scene, saved on the disk as individual files."
msgstr ""

#: ../../docs/tutorials/scripting/resources.rst:48
msgid ""
"**Built-in**, saved inside the ``.tscn`` or the ``.scn`` file they're "
"attached to."
msgstr ""

#: ../../docs/tutorials/scripting/resources.rst:50
msgid ""
"To be more specific, here's a :ref:`Texture2D <class_Texture2D>` in a :ref:"
"`Sprite2D <class_Sprite2D>` node:"
msgstr ""

#: ../../docs/tutorials/scripting/resources.rst:55
msgid ""
"Clicking the resource preview allows us to view the resource's properties."
msgstr ""

#: ../../docs/tutorials/scripting/resources.rst:59
msgid ""
"The path property tells us where the resource comes from. In this case, it "
"comes from a PNG image called ``robi.png``. When the resource comes from a "
"file like this, it is an external resource. If you erase the path or this "
"path is empty, it becomes a built-in resource."
msgstr ""

#: ../../docs/tutorials/scripting/resources.rst:64
msgid ""
"The switch between built-in and external resources happens when you save the "
"scene. In the example above, if you erase the path ``\"res://robi.png\"`` "
"and save, Godot will save the image inside the ``.tscn`` scene file."
msgstr ""

#: ../../docs/tutorials/scripting/resources.rst:70
msgid ""
"Even if you save a built-in resource, when you instance a scene multiple "
"times, the engine will only load one copy of it."
msgstr ""

#: ../../docs/tutorials/scripting/resources.rst:74
msgid "Loading resources from code"
msgstr ""

#: ../../docs/tutorials/scripting/resources.rst:76
msgid ""
"There are two ways to load resources from code. First, you can use the "
"``load()`` function anytime:"
msgstr ""

#: ../../docs/tutorials/scripting/resources.rst:96
msgid ""
"You can also ``preload`` resources. Unlike ``load``, this function will read "
"the file from disk and load it at compile-time. As a result, you cannot call "
"``preload`` with a variable path: you need to use a constant string."
msgstr ""

#: ../../docs/tutorials/scripting/resources.rst:113
msgid "Loading scenes"
msgstr ""

#: ../../docs/tutorials/scripting/resources.rst:115
msgid ""
"Scenes are also resources, but there is a catch. Scenes saved to disk are "
"resources of type :ref:`PackedScene <class_PackedScene>`. The scene is "
"packed inside a :ref:`Resource <class_Resource>`."
msgstr ""

#: ../../docs/tutorials/scripting/resources.rst:119
msgid ""
"To get an instance of the scene, you have to use the :ref:`PackedScene."
"instantiate() <class_PackedScene_method_instantiate>` method."
msgstr ""

#: ../../docs/tutorials/scripting/resources.rst:140
msgid ""
"This method creates the nodes in the scene's hierarchy, configures them, and "
"returns the root node of the scene. You can then add it as a child of any "
"other node."
msgstr ""

#: ../../docs/tutorials/scripting/resources.rst:144
msgid ""
"The approach has several advantages. As the :ref:`PackedScene.instantiate() "
"<class_PackedScene_method_instantiate>` function is fast, you can create new "
"enemies, bullets, effects, etc. without having to load them again from disk "
"each time. Remember that, as always, images, meshes, etc. are all shared "
"between the scene instances."
msgstr ""

#: ../../docs/tutorials/scripting/resources.rst:151
msgid "Freeing resources"
msgstr ""

#: ../../docs/tutorials/scripting/resources.rst:153
msgid ""
"When a :ref:`Resource <class_Resource>` is no longer in use, it will "
"automatically free itself. Since, in most cases, Resources are contained in "
"Nodes, when you free a node, the engine frees all the resources it owns as "
"well if no other node uses them."
msgstr ""

#: ../../docs/tutorials/scripting/resources.rst:158
msgid "Creating your own resources"
msgstr ""

#: ../../docs/tutorials/scripting/resources.rst:160
msgid ""
"Like any Object in Godot, users can also script Resources. Resource scripts "
"inherit the ability to freely translate between object properties and "
"serialized text or binary data (\\*.tres, \\*.res). They also inherit the "
"reference-counting memory management from the RefCounted type."
msgstr ""

#: ../../docs/tutorials/scripting/resources.rst:165
msgid ""
"This comes with many distinct advantages over alternative data structures, "
"such as JSON, CSV, or custom TXT files. Users can only import these assets "
"as a :ref:`Dictionary <class_Dictionary>` (JSON) or as a :ref:`FileAccess "
"<class_FileAccess>` to parse. What sets Resources apart is their inheritance "
"of :ref:`Object <class_Object>`, :ref:`RefCounted <class_RefCounted>`, and :"
"ref:`Resource <class_Resource>` features:"
msgstr ""

#: ../../docs/tutorials/scripting/resources.rst:172
msgid ""
"They can define constants, so constants from other data fields or objects "
"are not needed."
msgstr ""

#: ../../docs/tutorials/scripting/resources.rst:174
msgid ""
"They can define methods, including setter/getter methods for properties. "
"This allows for abstraction and encapsulation of the underlying data. If the "
"Resource script's structure needs to change, the game using the Resource "
"need not also change."
msgstr ""

#: ../../docs/tutorials/scripting/resources.rst:176
msgid ""
"They can define signals, so Resources can trigger responses to changes in "
"the data they manage."
msgstr ""

#: ../../docs/tutorials/scripting/resources.rst:178
msgid ""
"They have defined properties, so users know 100% that their data will exist."
msgstr ""

#: ../../docs/tutorials/scripting/resources.rst:180
msgid ""
"Resource auto-serialization and deserialization is a built-in Godot Engine "
"feature. Users do not need to implement custom logic to import/export a "
"resource file's data."
msgstr ""

#: ../../docs/tutorials/scripting/resources.rst:182
msgid ""
"Resources can even serialize sub-Resources recursively, meaning users can "
"design even more sophisticated data structures."
msgstr ""

#: ../../docs/tutorials/scripting/resources.rst:184
msgid ""
"Users can save Resources as version-control-friendly text files (\\*.tres). "
"Upon exporting a game, Godot serializes resource files as binary files (\\*."
"res) for increased speed and compression."
msgstr ""

#: ../../docs/tutorials/scripting/resources.rst:186
msgid ""
"Godot Engine's Inspector renders and edits Resource files out-of-the-box. As "
"such, users often do not need to implement custom logic to visualize or edit "
"their data. To do so, double-click the resource file in the FileSystem dock "
"or click the folder icon in the Inspector and open the file in the dialog."
msgstr ""

#: ../../docs/tutorials/scripting/resources.rst:188
msgid ""
"They can extend **other** resource types besides just the base Resource."
msgstr ""

#: ../../docs/tutorials/scripting/resources.rst:190
msgid "Godot makes it easy to create custom Resources in the Inspector."
msgstr ""

#: ../../docs/tutorials/scripting/resources.rst:192
msgid ""
"Create a plain Resource object in the Inspector. This can even be a type "
"that derives Resource, so long as your script is extending that type."
msgstr ""

#: ../../docs/tutorials/scripting/resources.rst:193
msgid "Set the ``script`` property in the Inspector to be your script."
msgstr ""

#: ../../docs/tutorials/scripting/resources.rst:195
msgid ""
"The Inspector will now display your Resource script's custom properties. If "
"one edits those values and saves the resource, the Inspector serializes the "
"custom properties too! To save a resource from the Inspector, click the "
"Inspector's tools menu (top right), and select \"Save\" or \"Save As...\"."
msgstr ""

#: ../../docs/tutorials/scripting/resources.rst:200
msgid ""
"If the script's language supports :ref:`script classes "
"<doc_gdscript_basics_class_name>`, then it streamlines the process. Defining "
"a name for your script alone will add it to the Inspector's creation dialog. "
"This will auto-add your script to the Resource object you create."
msgstr ""

#: ../../docs/tutorials/scripting/resources.rst:205
msgid ""
"Let's see some examples. Create a :ref:`Resource <class_Resource>` and name "
"it ``bot_stats``. It should appear in your file tab with the full name "
"``bot_stats.tres``. Without a script, it's useless, so let's add some data "
"and logic! Attach a script to it named ``bot_stats.gd`` (or just create a "
"new script, and then drag it to it)."
msgstr ""

#: ../../docs/tutorials/scripting/resources.rst:262
msgid ""
"Now, create a :ref:`CharacterBody3D <class_CharacterBody3D>`, name it "
"``Bot``, and add the following script to it:"
msgstr ""

#: ../../docs/tutorials/scripting/resources.rst:300
msgid ""
"Now, select the :ref:`CharacterBody3D <class_CharacterBody3D>` node which we "
"named ``bot``, and drag&drop the ``bot_stats.tres`` resource onto the "
"Inspector. It should print 10! Obviously, this setup can be used for more "
"advanced features than this, but as long you really understand *how* it all "
"worked, you should figure out everything else related to Resources."
msgstr ""

#: ../../docs/tutorials/scripting/resources.rst:304
msgid ""
"Resource scripts are similar to Unity's ScriptableObjects. The Inspector "
"provides built-in support for custom resources. If desired though, users can "
"even design their own Control-based tool scripts and combine them with an :"
"ref:`EditorPlugin <class_EditorPlugin>` to create custom visualizations and "
"editors for their data."
msgstr ""

#: ../../docs/tutorials/scripting/resources.rst:310
msgid ""
"Unreal Engine's DataTables and CurveTables are also easy to recreate with "
"Resource scripts. DataTables are a String mapped to a custom struct, similar "
"to a Dictionary mapping a String to a secondary custom Resource script."
msgstr ""

#: ../../docs/tutorials/scripting/resources.rst:345
msgid ""
"Instead of inlining the Dictionary values, one could also, alternatively:"
msgstr ""

#: ../../docs/tutorials/scripting/resources.rst:347
msgid ""
"Import a table of values from a spreadsheet and generate these key-value "
"pairs."
msgstr ""

#: ../../docs/tutorials/scripting/resources.rst:349
msgid ""
"Design a visualization within the editor and create a plugin that adds it to "
"the Inspector when you open these types of Resources."
msgstr ""

#: ../../docs/tutorials/scripting/resources.rst:352
msgid ""
"CurveTables are the same thing, except mapped to an Array of float values or "
"a :ref:`Curve <class_Curve>`/:ref:`Curve2D <class_Curve2D>` resource object."
msgstr ""

#: ../../docs/tutorials/scripting/resources.rst:357
msgid ""
"Beware that resource files (\\*.tres/\\*.res) will store the path of the "
"script they use in the file. When loaded, they will fetch and load this "
"script as an extension of their type. This means that trying to assign a "
"subclass, i.e. an inner class of a script (such as using the ``class`` "
"keyword in GDScript) won't work. Godot will not serialize the custom "
"properties on the script subclass properly."
msgstr ""

#: ../../docs/tutorials/scripting/resources.rst:363
msgid ""
"In the example below, Godot would load the ``Node`` script, see that it "
"doesn't extend ``Resource``, and then determine that the script failed to "
"load for the Resource object since the types are incompatible."
msgstr ""

#: ../../docs/tutorials/scripting/singletons_autoload.rst:4
msgid "Singletons (Autoload)"
msgstr ""

#: ../../docs/tutorials/scripting/singletons_autoload.rst:9
msgid ""
"Godot's scene system, while powerful and flexible, has a drawback: there is "
"no method for storing information (e.g. a player's score or inventory) that "
"is needed by more than one scene."
msgstr ""

#: ../../docs/tutorials/scripting/singletons_autoload.rst:13
msgid ""
"It's possible to address this with some workarounds, but they come with "
"their own limitations:"
msgstr ""

#: ../../docs/tutorials/scripting/singletons_autoload.rst:16
msgid ""
"You can use a \"master\" scene that loads and unloads other scenes as its "
"children. However, this means you can no longer run those scenes "
"individually and expect them to work correctly."
msgstr ""

#: ../../docs/tutorials/scripting/singletons_autoload.rst:19
msgid ""
"Information can be stored to disk in ``user://`` and then loaded by scenes "
"that require it, but frequently saving and loading data is cumbersome and "
"may be slow."
msgstr ""

#: ../../docs/tutorials/scripting/singletons_autoload.rst:23
msgid ""
"The `Singleton pattern <https://en.wikipedia.org/wiki/Singleton_pattern>`_ "
"is a useful tool for solving the common use case where you need to store "
"persistent information between scenes. In our case, it's possible to reuse "
"the same scene or class for multiple singletons as long as they have "
"different names."
msgstr ""

#: ../../docs/tutorials/scripting/singletons_autoload.rst:29
msgid "Using this concept, you can create objects that:"
msgstr ""

#: ../../docs/tutorials/scripting/singletons_autoload.rst:31
msgid "Are always loaded, no matter which scene is currently running."
msgstr ""

#: ../../docs/tutorials/scripting/singletons_autoload.rst:32
msgid "Can store global variables such as player information."
msgstr ""

#: ../../docs/tutorials/scripting/singletons_autoload.rst:33
msgid "Can handle switching scenes and between-scene transitions."
msgstr ""

#: ../../docs/tutorials/scripting/singletons_autoload.rst:34
msgid ""
"*Act* like a singleton, since GDScript does not support global variables by "
"design."
msgstr ""

#: ../../docs/tutorials/scripting/singletons_autoload.rst:36
msgid "Autoloading nodes and scripts can give us these characteristics."
msgstr ""

#: ../../docs/tutorials/scripting/singletons_autoload.rst:40
msgid ""
"Godot won't make an Autoload a \"true\" singleton as per the singleton "
"design pattern. It may still be instanced more than once by the user if "
"desired."
msgstr ""

#: ../../docs/tutorials/scripting/singletons_autoload.rst:45
msgid ""
"If you're creating an autoload as part of an editor plugin, consider :ref:"
"`registering it automatically in the Project Settings "
"<doc_making_plugins_autoload>` when the plugin is enabled."
msgstr ""

#: ../../docs/tutorials/scripting/singletons_autoload.rst:50
msgid "Autoload"
msgstr ""

#: ../../docs/tutorials/scripting/singletons_autoload.rst:52
msgid ""
"You can create an Autoload to load a scene or a script that inherits from :"
"ref:`class_Node`."
msgstr ""

#: ../../docs/tutorials/scripting/singletons_autoload.rst:57
msgid ""
"When autoloading a script, a :ref:`class_Node` will be created and the "
"script will be attached to it. This node will be added to the root viewport "
"before any other scenes are loaded."
msgstr ""

#: ../../docs/tutorials/scripting/singletons_autoload.rst:63
msgid ""
"To autoload a scene or script, select **Project > Project Settings** from "
"the menu and switch to the **Autoload** tab."
msgstr ""

#: ../../docs/tutorials/scripting/singletons_autoload.rst:68
msgid ""
"Here you can add any number of scenes or scripts. Each entry in the list "
"requires a name, which is assigned as the node's ``name`` property. The "
"order of the entries as they are added to the global scene tree can be "
"manipulated using the up/down arrow keys. Like regular scenes, the engine "
"will read these nodes in top-to-bottom order."
msgstr ""

#: ../../docs/tutorials/scripting/singletons_autoload.rst:76
msgid ""
"If the **Enable** column is checked (which is the default), then the "
"singleton can be accessed directly in GDScript:"
msgstr ""

#: ../../docs/tutorials/scripting/singletons_autoload.rst:84
msgid ""
"Note that autoload objects (scripts and/or scenes) are accessed just like "
"any other node in the scene tree. In fact, if you look at the running scene "
"tree, you'll see the autoloaded nodes appear:"
msgstr ""

#: ../../docs/tutorials/scripting/singletons_autoload.rst:92
msgid ""
"Autoloads must **not** be removed using ``free()`` or ``queue_free()`` at "
"runtime, or the engine will crash."
msgstr ""

#: ../../docs/tutorials/scripting/singletons_autoload.rst:96
msgid "Custom scene switcher"
msgstr ""

#: ../../docs/tutorials/scripting/singletons_autoload.rst:98
msgid ""
"This tutorial will demonstrate building a scene switcher using autoloads. "
"For basic scene switching, you can use the :ref:`SceneTree."
"change_scene_to_file() <class_SceneTree_method_change_scene_to_file>` method "
"(see :ref:`doc_scene_tree` for details). However, if you need more complex "
"behavior when changing scenes, this method provides more functionality."
msgstr ""

#: ../../docs/tutorials/scripting/singletons_autoload.rst:104
msgid ""
"To begin, download the template from here: `singleton_autoload_starter.zip "
"<https://github.com/godotengine/godot-docs-project-starters/releases/"
"download/latest-4.x/singleton_autoload_starter.zip>`_ and open it in Godot."
msgstr ""

#: ../../docs/tutorials/scripting/singletons_autoload.rst:108
msgid ""
"The project contains two scenes: ``scene_1.tscn`` and ``scene_2.tscn``. Each "
"scene contains a label displaying the scene name and a button with its "
"``pressed()`` signal connected. When you run the project, it starts in "
"``scene_1.tscn``. However, pressing the button does nothing."
msgstr ""

#: ../../docs/tutorials/scripting/singletons_autoload.rst:114
#, fuzzy
msgid "Creating the script"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/scripting/singletons_autoload.rst:116
msgid ""
"Open the **Script** window and create a new script called ``global.gd``. "
"Make sure it inherits from ``Node``:"
msgstr ""

#: ../../docs/tutorials/scripting/singletons_autoload.rst:121
msgid ""
"The next step is to add this script to the autoLoad list. Open **Project > "
"Project Settings** from the menu, switch to the **Autoload** tab and select "
"the script by clicking the browse button or typing its path: ``res://global."
"gd``. Press **Add** to add it to the autoload list:"
msgstr ""

#: ../../docs/tutorials/scripting/singletons_autoload.rst:128
msgid ""
"Now whenever we run any scene in the project, this script will always be "
"loaded."
msgstr ""

#: ../../docs/tutorials/scripting/singletons_autoload.rst:130
msgid ""
"Returning to the script, it needs to fetch the current scene in the "
"`_ready()` function. Both the current scene (the one with the button) and "
"``global.gd`` are children of root, but autoloaded nodes are always first. "
"This means that the last child of root is always the loaded scene."
msgstr ""

#: ../../docs/tutorials/scripting/singletons_autoload.rst:161
msgid ""
"Now we need a function for changing the scene. This function needs to free "
"the current scene and replace it with the requested one."
msgstr ""

#: ../../docs/tutorials/scripting/singletons_autoload.rst:230
msgid ""
"Using :ref:`Object.call_deferred() <class_Object_method_call_deferred>`, the "
"second function will only run once all code from the current scene has "
"completed. Thus, the current scene will not be removed while it is still "
"being used (i.e. its code is still running)."
msgstr ""

#: ../../docs/tutorials/scripting/singletons_autoload.rst:235
msgid ""
"Finally, we need to fill the empty callback functions in the two scenes:"
msgstr ""

#: ../../docs/tutorials/scripting/singletons_autoload.rst:275
msgid ""
"Run the project and test that you can switch between scenes by pressing the "
"button."
msgstr ""

#: ../../docs/tutorials/scripting/singletons_autoload.rst:280
msgid ""
"When scenes are small, the transition is instantaneous. However, if your "
"scenes are more complex, they may take a noticeable amount of time to "
"appear. To learn how to handle this, see the next tutorial: :ref:"
"`doc_background_loading`."
msgstr ""

#: ../../docs/tutorials/scripting/singletons_autoload.rst:284
msgid ""
"Alternatively, if the loading time is relatively short (less than 3 seconds "
"or so), you can display a \"loading plaque\" by showing some kind of 2D "
"element just before changing the scene. You can then hide it just after the "
"scene is changed. This can be used to indicate to the player that a scene is "
"being loaded."
msgstr ""

#: ../../docs/tutorials/scripting/scene_tree.rst:4
msgid "Using SceneTree"
msgstr ""

#: ../../docs/tutorials/scripting/scene_tree.rst:9
msgid ""
"In previous tutorials, everything revolved around the concept of nodes. "
"Scenes are collections of nodes. They become active once they enter the "
"*scene tree*."
msgstr ""

#: ../../docs/tutorials/scripting/scene_tree.rst:14
msgid "MainLoop"
msgstr ""

#: ../../docs/tutorials/scripting/scene_tree.rst:16
msgid ""
"The way Godot works internally is as follows. There is the :ref:`OS "
"<class_OS>` class, which is the only instance that runs at the beginning. "
"Afterwards, all drivers, servers, scripting languages, scene system, etc are "
"loaded."
msgstr ""

#: ../../docs/tutorials/scripting/scene_tree.rst:21
msgid ""
"When initialization is complete, :ref:`OS <class_OS>` needs to be supplied "
"a :ref:`MainLoop <class_MainLoop>` to run. Up to this point, all this is "
"internals working (you can check main/main.cpp file in the source code if "
"you are ever interested to see how this works internally)."
msgstr ""

#: ../../docs/tutorials/scripting/scene_tree.rst:27
msgid ""
"The user program, or game, starts in the MainLoop. This class has a few "
"methods, for initialization, idle (frame-synchronized callback), fixed "
"(physics-synchronized callback), and input. Again, this is low level and "
"when making games in Godot, writing your own MainLoop seldom makes sense."
msgstr ""

#: ../../docs/tutorials/scripting/scene_tree.rst:35
msgid ""
"One of the ways to explain how Godot works is that it's a high level game "
"engine over a low level middleware."
msgstr ""

#: ../../docs/tutorials/scripting/scene_tree.rst:38
msgid ""
"The scene system is the game engine, while the :ref:`OS <class_OS>` and "
"servers are the low level API."
msgstr ""

#: ../../docs/tutorials/scripting/scene_tree.rst:41
msgid ""
"The scene system provides its own main loop to OS, :ref:`SceneTree "
"<class_SceneTree>`. This is automatically instanced and set when running a "
"scene, no need to do any extra work."
msgstr ""

#: ../../docs/tutorials/scripting/scene_tree.rst:46
msgid ""
"It's important to know that this class exists because it has a few important "
"uses:"
msgstr ""

#: ../../docs/tutorials/scripting/scene_tree.rst:49
msgid ""
"It contains the root :ref:`Viewport <class_Viewport>`, to which a scene is "
"added as a child when it's first opened to become part of the *Scene Tree* "
"(more on that next)."
msgstr ""

#: ../../docs/tutorials/scripting/scene_tree.rst:52
msgid ""
"It contains information about the groups and has the means to call all nodes "
"in a group or get a list of them."
msgstr ""

#: ../../docs/tutorials/scripting/scene_tree.rst:54
msgid ""
"It contains some global state functionality, such as setting pause mode or "
"quitting the process."
msgstr ""

#: ../../docs/tutorials/scripting/scene_tree.rst:57
msgid ""
"When a node is part of the Scene Tree, the :ref:`SceneTree "
"<class_SceneTree>` singleton can be obtained by calling :ref:`Node."
"get_tree() <class_Node_method_get_tree>`."
msgstr ""

#: ../../docs/tutorials/scripting/scene_tree.rst:63
msgid "Root viewport"
msgstr ""

#: ../../docs/tutorials/scripting/scene_tree.rst:65
msgid ""
"The root :ref:`Viewport <class_Viewport>` is always at the top of the scene. "
"From a node, it can be obtained in two different ways:"
msgstr ""

#: ../../docs/tutorials/scripting/scene_tree.rst:80
msgid ""
"This node contains the main viewport. Anything that is a child of a :ref:"
"`Viewport <class_Viewport>` is drawn inside of it by default, so it makes "
"sense that the top of all nodes is always a node of this type otherwise "
"nothing would be seen."
msgstr ""

#: ../../docs/tutorials/scripting/scene_tree.rst:85
msgid ""
"While other viewports can be created in the scene (for split-screen effects "
"and such), this one is the only one that is never created by the user. It's "
"created automatically inside SceneTree."
msgstr ""

#: ../../docs/tutorials/scripting/scene_tree.rst:92
msgid ""
"When a node is connected, directly or indirectly, to the root viewport, it "
"becomes part of the *scene tree*."
msgstr ""

#: ../../docs/tutorials/scripting/scene_tree.rst:95
msgid ""
"This means that as explained in previous tutorials, it will get the "
"``_enter_tree()`` and ``_ready()`` callbacks (as well as ``_exit_tree()``)."
msgstr ""

#: ../../docs/tutorials/scripting/scene_tree.rst:100
msgid ""
"When nodes enter the *Scene Tree*, they become active. They get access to "
"everything they need to process, get input, display 2D and 3D visuals, "
"receive and send notifications, play sounds, etc. When they are removed from "
"the *scene tree*, they lose these abilities."
msgstr ""

#: ../../docs/tutorials/scripting/scene_tree.rst:106
msgid "Tree order"
msgstr ""

#: ../../docs/tutorials/scripting/scene_tree.rst:108
msgid ""
"Most node operations in Godot, such as drawing 2D, processing, or getting "
"notifications are done in *tree order*, or top to bottom as seen in the "
"editor (also known as pre-order traversal):"
msgstr ""

#: ../../docs/tutorials/scripting/scene_tree.rst:114
msgid ""
"For example, the top node in a scene has its ``_process()`` function called "
"first, then the node below it has its ``_process()`` function called, then "
"the node below that and so on."
msgstr ""

#: ../../docs/tutorials/scripting/scene_tree.rst:118
msgid ""
"An important exception is the ``_ready()`` function: each parent node has "
"its ``_ready()`` function called only after all its child nodes have their "
"``_ready()`` functions called, so that the parent knows its children are "
"completely ready to be accessed. This is also known as post-order traversal. "
"In the above image, ``NameLabel`` would be notified first (but only after "
"its children, if it had any!), followed by ``Name``, etc., and ``Panel`` "
"would be notified last."
msgstr ""

#: ../../docs/tutorials/scripting/scene_tree.rst:126
msgid ""
"The order of operations can also be overridden using the "
"``process_priority`` node property. Nodes with a lower number are called "
"first. For example, nodes with the priorities \"0, 1, 2, 3\" would be called "
"in that order from left to right."
msgstr ""

#: ../../docs/tutorials/scripting/scene_tree.rst:131
msgid "\"Becoming active\" by entering the *Scene Tree*"
msgstr ""

#: ../../docs/tutorials/scripting/scene_tree.rst:133
msgid "A scene is loaded from disk or created by scripting."
msgstr ""

#: ../../docs/tutorials/scripting/scene_tree.rst:134
msgid ""
"The root node of that scene (only one root, remember?) is added as either a "
"child of the \"root\" Viewport (from SceneTree), or to any of its "
"descendants."
msgstr ""

#: ../../docs/tutorials/scripting/scene_tree.rst:137
msgid ""
"Every node of the newly added scene will receive the \"enter_tree\" "
"notification ( ``_enter_tree()`` callback in GDScript) in top-to-bottom "
"order (pre-order traversal)."
msgstr ""

#: ../../docs/tutorials/scripting/scene_tree.rst:140
msgid ""
"Every node will receive the \"ready\" notification ( ``_ready()`` callback "
"in GDScript) for convenience, once all its children have received the "
"\"ready\" notification (post-order traversal)."
msgstr ""

#: ../../docs/tutorials/scripting/scene_tree.rst:143
msgid ""
"When a scene (or part of it) is removed, they receive the \"exit scene\" "
"notification ( ``_exit_tree()`` callback in GDScript) in bottom-to-top order "
"(the exact reverse of top-to-bottom order)."
msgstr ""

#: ../../docs/tutorials/scripting/scene_tree.rst:148
msgid "Changing current scene"
msgstr ""

#: ../../docs/tutorials/scripting/scene_tree.rst:150
msgid ""
"After a scene is loaded, you may want to change this scene for another one. "
"One way to do this is to use the :ref:`SceneTree.change_scene_to_file() "
"<class_SceneTree_method_change_scene_to_file>` function:"
msgstr ""

#: ../../docs/tutorials/scripting/scene_tree.rst:168
msgid ""
"Rather than using file paths, one can also use ready-made :ref:`PackedScene "
"<class_PackedScene>` resources using the equivalent function :ref:`SceneTree."
"change_scene_to_packed(PackedScene scene) "
"<class_SceneTree_method_change_scene_to_packed>`:"
msgstr ""

#: ../../docs/tutorials/scripting/scene_tree.rst:189
msgid ""
"These are quick and useful ways to switch scenes but have the drawback that "
"the game will stall until the new scene is loaded and running. At some point "
"in the development of your game, it may be preferable to create proper "
"loading screens with progress bar, animated indicators or threaded "
"(background) loading. This must be done manually using :ref:"
"`doc_singletons_autoload` and :ref:`doc_background_loading`."
msgstr ""

#: ../../docs/tutorials/scripting/scene_unique_nodes.rst:4
msgid "Scene Unique Nodes"
msgstr ""

#: ../../docs/tutorials/scripting/scene_unique_nodes.rst:9
msgid ""
"Using ``get_node()`` to reference nodes from a script can sometimes be "
"fragile. If you move a button in a UI scene from one panel to another, the "
"button's node path changes, and if a script uses ``get_node()`` with a hard-"
"coded node path, the script will not be able to find the button anymore."
msgstr ""

#: ../../docs/tutorials/scripting/scene_unique_nodes.rst:14
msgid ""
"In situations like this, the node can be turned into a scene unique node to "
"avoid having to update the script every time the node's path is changed."
msgstr ""

#: ../../docs/tutorials/scripting/scene_unique_nodes.rst:19
#, fuzzy
msgid "Creation and usage"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/scripting/scene_unique_nodes.rst:21
msgid ""
"In the Scene tree dock, right-click on a node and select **Access as Unique "
"Name** in the context menu."
msgstr ""

#: ../../docs/tutorials/scripting/scene_unique_nodes.rst:26
msgid ""
"After selecting the option, the node will now have a percent symbol (**%**) "
"next to its name in the scene tree:"
msgstr ""

#: ../../docs/tutorials/scripting/scene_unique_nodes.rst:31
msgid ""
"You can now use the node in your script. For example, you can reference it "
"with a ``get_node()`` method call by typing the % symbol, followed by the "
"node's name:"
msgstr ""

#: ../../docs/tutorials/scripting/scene_unique_nodes.rst:47
msgid "Same-scene limitation"
msgstr ""

#: ../../docs/tutorials/scripting/scene_unique_nodes.rst:49
msgid ""
"A scene unique node can only be retrieved by a node inside the same scene. "
"To demonstrate this limitation, consider this example **Player** scene that "
"instances a **Sword** scene:"
msgstr ""

#: ../../docs/tutorials/scripting/scene_unique_nodes.rst:55
msgid ""
"Here are the results of ``get_node()`` calls inside the **Player** script:"
msgstr ""

#: ../../docs/tutorials/scripting/scene_unique_nodes.rst:57
msgid "``get_node(\"%Eyes\")`` returns the **Eyes** node."
msgstr ""

#: ../../docs/tutorials/scripting/scene_unique_nodes.rst:58
msgid "``get_node(\"%Hilt\")`` returns ``null``."
msgstr ""

#: ../../docs/tutorials/scripting/scene_unique_nodes.rst:60
msgid ""
"These are the results of ``get_node()`` calls inside the **Sword** script:"
msgstr ""

#: ../../docs/tutorials/scripting/scene_unique_nodes.rst:62
msgid "``get_node(\"%Eyes\")`` returns ``null``."
msgstr ""

#: ../../docs/tutorials/scripting/scene_unique_nodes.rst:63
msgid "``get_node(\"%Hilt\")`` returns the **Hilt** node."
msgstr ""

#: ../../docs/tutorials/scripting/scene_unique_nodes.rst:65
msgid ""
"If a script has access to a node in another scene, it can call "
"``get_node()`` on that node to get scene unique nodes from that node's "
"scene. This also works in a node path, which avoids multiple ``get_node()`` "
"calls. Here are two ways to get the **Hilt** node from the **Player** script "
"using scene unique nodes:"
msgstr ""

#: ../../docs/tutorials/scripting/scene_unique_nodes.rst:70
msgid ""
"``get_node(\"Hand/Sword\").get_node(\"%Hilt\")`` returns the **Hilt** node."
msgstr ""

#: ../../docs/tutorials/scripting/scene_unique_nodes.rst:71
msgid "``get_node(\"Hand/Sword/%Hilt\")`` also returns the **Hilt** node."
msgstr ""

#: ../../docs/tutorials/scripting/scene_unique_nodes.rst:73
msgid ""
"Scene unique names don't only work at the end of a node path. They can be "
"used in the middle to navigate from one node to another. For example, the "
"**Sword** node is marked as a scene unique node in the **Player** scene, so "
"this is possible:"
msgstr ""

#: ../../docs/tutorials/scripting/scene_unique_nodes.rst:77
msgid "``get_node(\"%Sword/%Hilt\")`` returns the **Hilt** node."
msgstr ""

#: ../../docs/tutorials/scripting/scene_unique_nodes.rst:80
msgid "Alternatives"
msgstr ""

#: ../../docs/tutorials/scripting/scene_unique_nodes.rst:82
msgid ""
"Scene unique nodes are a useful tool to navigate a scene. However, there are "
"some situations where other techniques may be better."
msgstr ""

#: ../../docs/tutorials/scripting/scene_unique_nodes.rst:85
msgid ""
"A :ref:`Group <doc_groups>` allows locating a node (or a group of many "
"nodes) from any other node, no matter what scene the two nodes are located "
"in."
msgstr ""

#: ../../docs/tutorials/scripting/scene_unique_nodes.rst:88
msgid ""
"A :ref:`Singleton (Autoload) <doc_singletons_autoload>` is an always loaded "
"node that can be accessed directly by any node regardless of the scene. "
"These are useful when some data or functionality is shared globally."
msgstr ""

#: ../../docs/tutorials/scripting/scene_unique_nodes.rst:92
msgid ""
":ref:`Node.find_child() <class_Node_method_find_child>` finds a node by name "
"without knowing its full path. This seems similar to a scene unique node, "
"but this method is able to find nodes in nested scenes, and doesn't require "
"marking the node in the scene editor in any way. However, this method is "
"slow. Scene unique nodes are cached by Godot and are fast to retrieve, but "
"each time the method is called, ``find_child()`` needs to check every "
"descendant (every child, grandchild, and so on)."
msgstr ""

#: ../../docs/tutorials/shaders/introduction_to_shaders.rst:4
#, fuzzy
msgid "Introduction to shaders"
msgstr "Uvod"

#: ../../docs/tutorials/shaders/introduction_to_shaders.rst:6
msgid ""
"This page explains what shaders are and will give you an overview of how "
"they work in Godot. For a detailed reference of the engine's shading "
"language, see :ref:`doc_shading_language`."
msgstr ""

#: ../../docs/tutorials/shaders/introduction_to_shaders.rst:10
msgid ""
"Shaders are a special kind of program that runs on Graphics Processing Units "
"(GPUs). They were initially used to shade 3D scenes but can nowadays do much "
"more. You can use them to control how the engine draws geometry and pixels "
"on the screen, allowing you to achieve all sorts of effects."
msgstr ""

#: ../../docs/tutorials/shaders/introduction_to_shaders.rst:15
msgid ""
"Modern rendering engines like Godot draw everything with shaders: graphics "
"cards can run thousands of instructions in parallel, leading to incredible "
"rendering speed."
msgstr ""

#: ../../docs/tutorials/shaders/introduction_to_shaders.rst:19
msgid ""
"Because of their parallel nature, though, shaders don't process information "
"the way a typical program does. Shader code runs on each vertex or pixel in "
"isolation. You cannot store data between frames either. As a result, when "
"working with shaders, you need to code and think differently from other "
"programming languages."
msgstr ""

#: ../../docs/tutorials/shaders/introduction_to_shaders.rst:25
msgid ""
"Suppose you want to update all the pixels in a texture to a given color. In "
"GDScript, your code would use ``for`` loops::"
msgstr ""

#: ../../docs/tutorials/shaders/introduction_to_shaders.rst:32
msgid ""
"Your code is already part of a loop in a shader, so the corresponding code "
"would look like this."
msgstr ""

#: ../../docs/tutorials/shaders/introduction_to_shaders.rst:43
msgid ""
"The graphics card calls the ``fragment()`` function once or more for each "
"pixel it has to draw. More on that below."
msgstr ""

#: ../../docs/tutorials/shaders/introduction_to_shaders.rst:47
msgid "Shaders in Godot"
msgstr ""

#: ../../docs/tutorials/shaders/introduction_to_shaders.rst:49
msgid ""
"Godot provides a shading language based on the popular OpenGL Shading "
"Language (GLSL) but simplified. The engine handles some of the lower-level "
"initialization work for you, making it easier to write complex shaders."
msgstr ""

#: ../../docs/tutorials/shaders/introduction_to_shaders.rst:53
msgid ""
"In Godot, shaders are made up of main functions called \"processor "
"functions\". Processor functions are the entry point for your shader into "
"the program. There are seven different processor functions."
msgstr ""

#: ../../docs/tutorials/shaders/introduction_to_shaders.rst:57
msgid ""
"The ``vertex()`` function runs over all the vertices in the mesh and sets "
"their positions and some other per-vertex variables. Used in :ref:"
"`canvas_item shaders <doc_canvas_item_shader>` and :ref:`spatial shaders "
"<doc_spatial_shader>`."
msgstr ""

#: ../../docs/tutorials/shaders/introduction_to_shaders.rst:62
msgid ""
"The ``fragment()`` function runs for every pixel covered by the mesh. It "
"uses values output by the ``vertex()`` function, interpolated between the "
"vertices. Used in :ref:`canvas_item shaders <doc_canvas_item_shader>` and :"
"ref:`spatial shaders <doc_spatial_shader>`."
msgstr ""

#: ../../docs/tutorials/shaders/introduction_to_shaders.rst:67
msgid ""
"The ``light()`` function runs for every pixel and for every light. It takes "
"variables from the ``fragment()`` function and from its previous runs. Used "
"in :ref:`canvas_item shaders <doc_canvas_item_shader>` and :ref:`spatial "
"shaders <doc_spatial_shader>`."
msgstr ""

#: ../../docs/tutorials/shaders/introduction_to_shaders.rst:72
msgid ""
"The ``start()`` function runs for every particle in a particle system once "
"when the particle is first spawned. Used in :ref:`particles shaders "
"<doc_particle_shader>`."
msgstr ""

#: ../../docs/tutorials/shaders/introduction_to_shaders.rst:76
msgid ""
"The ``process()`` function runs for every particle in a particle system for "
"each frame. Used in :ref:`particles shaders <doc_particle_shader>`."
msgstr ""

#: ../../docs/tutorials/shaders/introduction_to_shaders.rst:79
msgid ""
"The ``sky()`` function runs for every pixel in the radiance cubemap when the "
"radiance cubemap needs to be updated, and for every pixel on the current "
"screen. Used in :ref:`sky shaders <doc_sky_shader>`."
msgstr ""

#: ../../docs/tutorials/shaders/introduction_to_shaders.rst:83
msgid ""
"The ``fog()`` function runs for every froxel in the volumetric fog froxel "
"buffer that intersects with the :ref:`FogVolume <class_FogVolume>`. Used by :"
"ref:`fog shaders <doc_fog_shader>`."
msgstr ""

#: ../../docs/tutorials/shaders/introduction_to_shaders.rst:89
msgid ""
"The ``light()`` function won't run if the ``vertex_lighting`` render mode is "
"enabled, or if **Rendering > Quality > Shading > Force Vertex Shading** is "
"enabled in the Project Settings. It's enabled by default on mobile platforms."
msgstr ""

#: ../../docs/tutorials/shaders/introduction_to_shaders.rst:96
msgid ""
"Godot also exposes an API for users to write totally custom GLSL shaders. "
"For more information see :ref:`doc_compute_shaders`."
msgstr ""

#: ../../docs/tutorials/shaders/introduction_to_shaders.rst:100
msgid "Shader types"
msgstr ""

#: ../../docs/tutorials/shaders/introduction_to_shaders.rst:102
msgid ""
"Instead of supplying a general-purpose configuration for all uses (2D, 3D, "
"particles, sky, fog), you must specify the type of shader you're writing. "
"Different types support different render modes, built-in variables, and "
"processing functions."
msgstr ""

#: ../../docs/tutorials/shaders/introduction_to_shaders.rst:107
msgid ""
"In Godot, all shaders need to specify their type in the first line, like so:"
msgstr ""

#: ../../docs/tutorials/shaders/introduction_to_shaders.rst:113
#, fuzzy
msgid "Here are the available types:"
msgstr "Ne postoje ograničenja prilikom korištenja Godot-a"

#: ../../docs/tutorials/shaders/introduction_to_shaders.rst:115
#, fuzzy
msgid ":ref:`spatial <doc_spatial_shader>` for 3D rendering."
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/shaders/introduction_to_shaders.rst:116
msgid ":ref:`canvas_item <doc_canvas_item_shader>` for 2D rendering."
msgstr ""

#: ../../docs/tutorials/shaders/introduction_to_shaders.rst:117
#, fuzzy
msgid ":ref:`particles <doc_particle_shader>` for particle systems."
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/shaders/introduction_to_shaders.rst:118
msgid ":ref:`sky <doc_sky_shader>` to render :ref:`Skies <class_Sky>`."
msgstr ""

#: ../../docs/tutorials/shaders/introduction_to_shaders.rst:119
msgid ""
":ref:`fog <doc_fog_shader>` to render :ref:`FogVolumes <class_FogVolume>`"
msgstr ""

#: ../../docs/tutorials/shaders/introduction_to_shaders.rst:122
#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:12
#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:14
#: ../../docs/tutorials/shaders/shader_reference/particle_shader.rst:31
#: ../../docs/tutorials/shaders/shader_reference/sky_shader.rst:105
msgid "Render modes"
msgstr ""

#: ../../docs/tutorials/shaders/introduction_to_shaders.rst:124
msgid ""
"Shaders have optional render modes you can specify on the second line, after "
"the shader type, like so:"
msgstr ""

#: ../../docs/tutorials/shaders/introduction_to_shaders.rst:132
msgid ""
"Render modes alter the way Godot applies the shader. For example, the "
"``unshaded`` mode makes the engine skip the built-in light processor "
"function."
msgstr ""

#: ../../docs/tutorials/shaders/introduction_to_shaders.rst:135
msgid ""
"Each shader type has different render modes. See the reference for each "
"shader type for a complete list of render modes."
msgstr ""

#: ../../docs/tutorials/shaders/introduction_to_shaders.rst:139
msgid "Vertex processor"
msgstr ""

#: ../../docs/tutorials/shaders/introduction_to_shaders.rst:141
msgid ""
"The ``vertex()`` processing function is called once for every vertex in "
"``spatial`` and ``canvas_item`` shaders. For ``particles`` shaders, it is "
"called once for every particle."
msgstr ""

#: ../../docs/tutorials/shaders/introduction_to_shaders.rst:145
msgid ""
"Each vertex in your world's geometry has properties like a position and "
"color. The function modifies those values and passes them to the fragment "
"function. You can also use it to send extra data to the fragment function "
"using varyings."
msgstr ""

#: ../../docs/tutorials/shaders/introduction_to_shaders.rst:149
msgid ""
"By default, Godot transforms your vertex information for you, which is "
"necessary to project geometry onto the screen. You can use render modes to "
"transform the data yourself; see the :ref:`Spatial shader doc "
"<doc_spatial_shader>` for an example."
msgstr ""

#: ../../docs/tutorials/shaders/introduction_to_shaders.rst:155
msgid "Fragment processor"
msgstr ""

#: ../../docs/tutorials/shaders/introduction_to_shaders.rst:157
msgid ""
"The ``fragment()`` processing function is used to set up the Godot material "
"parameters per pixel. This code runs on every visible pixel the object or "
"primitive draws. It is only available in ``spatial``, ``canvas_item``, and "
"``sky`` shaders."
msgstr ""

#: ../../docs/tutorials/shaders/introduction_to_shaders.rst:161
msgid ""
"The standard use of the fragment function is to set up material properties "
"used to calculate lighting. For example, you would set values for "
"``ROUGHNESS``, ``RIM``, or ``TRANSMISSION``, which would tell the light "
"function how the lights respond to that fragment. This makes it possible to "
"control a complex shading pipeline without the user having to write much "
"code. If you don't need this built-in functionality, you can ignore it and "
"write your own light processing function, and Godot will optimize it away. "
"For example, if you do not write a value to ``RIM``, Godot will not "
"calculate rim lighting. During compilation, Godot checks to see if ``RIM`` "
"is used; if not, it cuts all the corresponding code out. Therefore, you will "
"not waste calculations on the effects that you do not use."
msgstr ""

#: ../../docs/tutorials/shaders/introduction_to_shaders.rst:174
msgid "Light processor"
msgstr ""

#: ../../docs/tutorials/shaders/introduction_to_shaders.rst:176
msgid ""
"The ``light()`` processor runs per pixel too, and it runs once for every "
"light that affects the object. It does not run if no lights affect the "
"object. It exists as a function called inside the ``fragment()`` processor "
"and typically operates on the material properties setup inside the "
"``fragment()`` function."
msgstr ""

#: ../../docs/tutorials/shaders/introduction_to_shaders.rst:181
msgid ""
"The ``light()`` processor works differently in 2D than it does in 3D; for a "
"description of how it works in each, see their documentation, :ref:"
"`CanvasItem shaders <doc_canvas_item_shader>` and :ref:`Spatial shaders "
"<doc_spatial_shader>`, respectively."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/index.rst:2
msgid "Shading reference"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:4
msgid "Shading language"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:9
msgid ""
"Godot uses a shading language similar to GLSL ES 3.0. Most datatypes and "
"functions are supported, and the few remaining ones will likely be added "
"over time."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:13
msgid ""
"If you are already familiar with GLSL, the :ref:`Godot Shader Migration "
"Guide<doc_converting_glsl_to_godot_shaders>` is a resource that will help "
"you transition from regular GLSL to Godot's shading language."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:18
msgid "Data types"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:20
msgid "Most GLSL ES 3.0 datatypes are supported:"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:25
msgid "**void**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:25
msgid "Void datatype, useful only for functions that return nothing."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:27
#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:819
msgid "**bool**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:27
msgid "Boolean datatype, can only contain ``true`` or ``false``."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:29
#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:821
msgid "**bvec2**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:29
msgid "Two-component vector of booleans."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:31
#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:831
msgid "**bvec3**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:31
msgid "Three-component vector of booleans."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:33
#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:833
msgid "**bvec4**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:33
msgid "Four-component vector of booleans."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:35
#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:821
#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:831
#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:833
#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:835
#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:843
msgid "**int**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:35
msgid "Signed scalar integer."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:37
#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:837
msgid "**ivec2**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:37
msgid "Two-component vector of signed integers."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:39
#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:839
msgid "**ivec3**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:39
msgid "Three-component vector of signed integers."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:41
#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:841
msgid "**ivec4**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:41
msgid "Four-component vector of signed integers."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:43
#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:843
msgid "**uint**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:43
msgid "Unsigned scalar integer; can't contain negative numbers."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:45
#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:845
msgid "**uvec2**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:45
msgid "Two-component vector of unsigned integers."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:47
#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:847
msgid "**uvec3**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:47
msgid "Three-component vector of unsigned integers."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:49
#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:849
msgid "**uvec4**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:49
msgid "Four-component vector of unsigned integers."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:51
#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:851
msgid "**float**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:51
msgid "Floating-point scalar."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:53
#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:853
msgid "**vec2**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:53
msgid "Two-component vector of floating-point values."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:55
#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:855
msgid "**vec3**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:55
msgid "Three-component vector of floating-point values."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:57
#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:857
msgid "**vec4**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:57
msgid "Four-component vector of floating-point values."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:59
#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:867
msgid "**mat2**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:59
msgid "2x2 matrix, in column major order."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:61
#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:870
msgid "**mat3**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:61
msgid "3x3 matrix, in column major order."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:63
msgid "**mat4**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:63
msgid "4x4 matrix, in column major order."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:65
#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:785
#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:787
#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:789
#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:791
#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:793
#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:795
#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:797
#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:801
#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:803
#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:805
#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:807
#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:809
#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:875
msgid "**sampler2D**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:65
msgid "Sampler type for binding 2D textures, which are read as float."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:67
#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:877
msgid "**isampler2D**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:67
msgid "Sampler type for binding 2D textures, which are read as signed integer."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:69
#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:879
msgid "**usampler2D**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:69
msgid ""
"Sampler type for binding 2D textures, which are read as unsigned integer."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:71
#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:881
msgid "**sampler2DArray**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:71
msgid "Sampler type for binding 2D texture arrays, which are read as float."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:73
#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:883
msgid "**isampler2DArray**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:73
msgid ""
"Sampler type for binding 2D texture arrays, which are read as signed integer."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:75
#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:885
msgid "**usampler2DArray**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:75
msgid ""
"Sampler type for binding 2D texture arrays, which are read as unsigned "
"integer."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:77
#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:887
msgid "**sampler3D**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:77
msgid "Sampler type for binding 3D textures, which are read as float."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:79
#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:889
msgid "**isampler3D**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:79
msgid "Sampler type for binding 3D textures, which are read as signed integer."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:81
#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:891
msgid "**usampler3D**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:81
msgid ""
"Sampler type for binding 3D textures, which are read as unsigned integer."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:83
#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:893
msgid "**samplerCube**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:83
msgid "Sampler type for binding Cubemaps, which are read as float."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:85
#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:895
msgid "**samplerCubeArray**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:85
msgid "Sampler type for binding Cubemap arrays, which are read as float."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:91
msgid ""
"Just like GLSL ES 3.0, implicit casting between scalars and vectors of the "
"same size but different type is not allowed. Casting of types of different "
"size is also not allowed. Conversion must be done explicitly via "
"constructors."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:103
msgid ""
"Default integer constants are signed, so casting is always needed to convert "
"to unsigned:"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:113
msgid "Members"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:115
msgid ""
"Individual scalar members of vector types are accessed via the \"x\", \"y\", "
"\"z\" and \"w\" members. Alternatively, using \"r\", \"g\", \"b\" and \"a\" "
"also works and is equivalent. Use whatever fits best for your needs."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:119
msgid ""
"For matrices, use the ``m[column][row]`` indexing syntax to access each "
"scalar, or ``m[idx]`` to access a vector by row index. For example, for "
"accessing the y position of an object in a mat4 you use ``m[3][1]``."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:124
msgid "Constructing"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:126
msgid "Construction of vector types must always pass:"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:138
msgid ""
"Construction of matrix types requires vectors of the same dimension as the "
"matrix. You can also build a diagonal matrix using ``matx(float)`` syntax. "
"Accordingly, ``mat4(1.0)`` is an identity matrix."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:148
msgid ""
"Matrices can also be built from a matrix of another dimension. There are two "
"rules:"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:151
msgid ""
"1. If a larger matrix is constructed from a smaller matrix, the additional "
"rows and columns are set to the values they would have in an identity "
"matrix. 2. If a smaller matrix is constructed from a larger matrix, the top, "
"left submatrix of the larger matrix is used."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:163
msgid "Swizzling"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:165
msgid ""
"It is possible to obtain any combination of components in any order, as long "
"as the result is another vector type (or scalar). This is easier shown than "
"explained:"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:183
#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:116
msgid "Precision"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:185
msgid ""
"It is possible to add precision modifiers to datatypes; use them for "
"uniforms, variables, arguments and varyings:"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:195
msgid ""
"Using lower precision for some operations can speed up the math involved (at "
"the cost of less precision). This is rarely needed in the vertex processor "
"function (where full precision is needed most of the time), but is often "
"useful in the fragment processor."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:200
msgid ""
"Some architectures (mainly mobile) can benefit significantly from this, but "
"there are downsides such as the additional overhead of conversion between "
"precisions. Refer to the documentation of the target architecture for "
"further information. In many cases, mobile drivers cause inconsistent or "
"unexpected behavior and it is best to avoid specifying precision unless "
"necessary."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:209
msgid "Arrays are containers for multiple variables of a similar type."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:212
msgid "Local arrays"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:214
msgid ""
"Local arrays are declared in functions. They can use all of the allowed "
"datatypes, except samplers. The array declaration follows a C-style syntax: "
"``[const] + [precision] + typename + identifier + [array size]``."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:224
msgid "They can be initialized at the beginning like:"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:236
msgid ""
"You can declare multiple arrays (even with different sizes) in one "
"expression:"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:246
msgid "To access an array element, use the indexing syntax:"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:256
msgid ""
"Arrays also have a built-in function ``.length()`` (not to be confused with "
"the built-in ``length()`` function). It doesn't accept any parameters and "
"will return the array's size."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:269
msgid ""
"If you use an index either below 0 or greater than array size - the shader "
"will crash and break rendering. To prevent this, use ``length()``, ``if``, "
"or ``clamp()`` functions to ensure the index is between 0 and the array's "
"length. Always carefully test and check your code. If you pass a constant "
"expression or a number, the editor will check its bounds to prevent this "
"crash."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:277
msgid "Global arrays"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:279
msgid "You can declare arrays at global space like:"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:293
msgid ""
"Global arrays have to be declared as global constants, otherwise they can be "
"declared the same as local arrays."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:299
msgid ""
"Use the ``const`` keyword before the variable declaration to make that "
"variable immutable, which means that it cannot be modified. All basic types, "
"except samplers can be declared as constants. Accessing and using a constant "
"value is slightly faster than using a uniform. Constants must be initialized "
"at their declaration."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:313
msgid ""
"Constants cannot be modified and additionally cannot have hints, but "
"multiple of them (if they have the same type) can be declared in a single "
"expression e.g"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:320
msgid "Similar to variables, arrays can also be declared with ``const``."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:330
msgid ""
"Constants can be declared both globally (outside of any function) or locally "
"(inside a function). Global constants are useful when you want to have "
"access to a value throughout your shader that does not need to be modified. "
"Like uniforms, global constants are shared between all shader stages, but "
"they are not accessible outside of the shader."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:342
msgid ""
"Constants of the ``float`` type must be initialized using ``.`` notation "
"after the decimal part or by using the scientific notation. The optional "
"``f`` post-suffix is also supported."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:352
msgid ""
"Constants of the ``uint`` (unsigned int) type must have a ``u`` suffix to "
"differentiate them from signed integers. Alternatively, this can be done by "
"using the ``uint(x)`` built-in conversion function."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:361
msgid "Structs"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:363
msgid ""
"Structs are compound types which can be used for better abstraction of "
"shader code. You can declare them at the global scope like:"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:374
msgid "After declaration, you can instantiate and initialize them like:"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:386
msgid "Or use struct constructor for same purpose:"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:392
msgid ""
"Structs may contain other struct or array, you can also instance them as "
"global constant:"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:412
msgid "You can also pass them to functions:"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:432
msgid ""
"Godot shading language supports the same set of operators as GLSL ES 3.0. "
"Below is the list of them in precedence order:"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:436
msgid "Precedence"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:436
msgid "Class"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:438
msgid "1 (highest)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:438
msgid "parenthetical grouping"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:438
msgid "**()**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:440
msgid "unary"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:440
msgid "**+, -, !, ~**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:442
msgid "multiplicative"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:442
msgid "**/, \\*, %**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:444
msgid "additive"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:444
msgid "**+, -**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:446
msgid "bit-wise shift"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:446
msgid "**<<, >>**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:448
msgid "relational"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:448
msgid "**<, >, <=, >=**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:450
msgid "equality"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:450
msgid "**==, !=**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:452
msgid "bit-wise AND"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:452
msgid "**&**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:454
msgid "bit-wise exclusive OR"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:454
msgid "**^**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:456
msgid "bit-wise inclusive OR"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:456
msgid "**|**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:458
msgid "logical AND"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:458
msgid "**&&**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:460
msgid "12 (lowest)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:460
msgid "logical inclusive OR"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:460
msgid "**||**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:464
msgid "Flow control"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:466
msgid "Godot Shading language supports the most common types of flow control:"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:515
msgid ""
"Keep in mind that in modern GPUs, an infinite loop can exist and can freeze "
"your application (including editor). Godot can't protect you from this, so "
"be careful not to make this mistake!"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:519
msgid ""
"Also, when comparing floating-point values against a number, make sure to "
"compare them against a *range* instead of an exact number."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:522
msgid ""
"A comparison like ``if (value == 0.3)`` may not evaluate to ``true``. "
"Floating-point math is often approximate and can defy expectations. It can "
"also behave differently depending on the hardware."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:526
msgid "**Don't** do this."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:537
msgid ""
"Instead, always perform a range comparison with an epsilon value. The larger "
"the floating-point number (and the less precise the floating-point number), "
"the larger the epsilon value should be."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:548
msgid ""
"See `floating-point-gui.de <https://floating-point-gui.de/>`__ for more "
"information."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:552
msgid "Discarding"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:554
msgid ""
"Fragment and light functions can use the ``discard`` keyword. If used, the "
"fragment is discarded and nothing is written."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:557
msgid ""
"Beware that ``discard`` has a performance cost when used, as it will prevent "
"the depth prepass from being effective on any surfaces using the shader. "
"Also, a discarded pixel still needs to be rendered in the vertex shader, "
"which means a shader that uses ``discard`` on all of its pixels is still "
"more expensive to render compared to not rendering any object in the first "
"place."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:566
msgid ""
"It is possible to define functions in a Godot shader. They use the following "
"syntax:"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:582
msgid ""
"You can only use functions that have been defined above (higher in the "
"editor) the function from which you are calling them. Redefining a function "
"that has already been defined above (or is a built-in function name) will "
"cause an error."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:586
msgid "Function arguments can have special qualifiers:"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:588
msgid "**in**: Means the argument is only for reading (default)."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:589
msgid "**out**: Means the argument is only for writing."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:590
msgid "**inout**: Means the argument is fully passed via reference."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:591
msgid ""
"**const**: Means the argument is a constant and cannot be changed, may be "
"combined with **in** qualifier."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:594
msgid "Example below:"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:604
msgid ""
"Unlike GLSL, Godot's shader language does **not** support function "
"overloading. This means that a function cannot be defined several times with "
"different argument types or numbers of arguments. As a workaround, use "
"different names for functions that accept a different number of arguments or "
"arguments of different types."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:611
#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:59
msgid "Varyings"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:613
msgid ""
"To send data from the vertex to the fragment (or light) processor function, "
"*varyings* are used. They are set for every primitive vertex in the *vertex "
"processor*, and the value is interpolated for every pixel in the *fragment "
"processor*."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:635
msgid "Varying can also be an array:"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:652
msgid ""
"It's also possible to send data from *fragment* to *light* processors using "
"*varying* keyword. To do so you can assign it in the *fragment* and later "
"use it in the *light* function."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:668
msgid ""
"Note that varying may not be assigned in custom functions or a *light "
"processor* function like:"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:688
msgid ""
"This limitation was introduced to prevent incorrect usage before "
"initialization."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:691
msgid "Interpolation qualifiers"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:693
msgid ""
"Certain values are interpolated during the shading pipeline. You can modify "
"how these interpolations are done by using *interpolation qualifiers*."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:710
msgid "There are two possible interpolation qualifiers:"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:713
msgid "Qualifier"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:715
msgid "**flat**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:715
msgid "The value is not interpolated."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:717
msgid "**smooth**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:717
msgid ""
"The value is interpolated in a perspective-correct fashion. This is the "
"default."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:722
#: ../../docs/tutorials/shaders/your_first_shader/your_first_3d_shader.rst:226
msgid "Uniforms"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:724
msgid ""
"Passing values to shaders is possible. These are global to the whole shader "
"and are called *uniforms*. When a shader is later assigned to a material, "
"the uniforms will appear as editable parameters in it. Uniforms can't be "
"written from within the shader."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:737
msgid ""
"You can set uniforms in the editor in the material. Or you can set them "
"through GDScript:"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:746
msgid ""
"The first argument to ``set_shader_parameter`` is the name of the uniform in "
"the shader. It must match *exactly* to the name of the uniform in the shader "
"or else it will not be recognized."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:750
msgid ""
"Any GLSL type except for *void* can be a uniform. Additionally, Godot "
"provides optional shader hints to make the compiler understand for what the "
"uniform is used, and how the editor should allow users to modify it."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:763
msgid ""
"It's important to understand that textures *that are supplied as color* "
"require hints for proper sRGB -> linear conversion (i.e. ``source_color``), "
"as Godot's 3D engine renders in linear color space. If this is not done, the "
"texture will appear washed out."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:770
msgid ""
"The 2D renderer also renders in linear color space if the **Rendering > "
"Viewport > HDR 2D** project setting is enabled, so ``source_color`` must "
"also be used in ``canvas_item`` shaders. If 2D HDR is disabled, "
"``source_color`` will keep working correctly in ``canvas_item`` shaders, so "
"it's recommend to use it either way."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:776
msgid "Full list of hints below:"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:779
msgid "Hint"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:781
msgid "**vec3, vec4**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:781
#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:785
msgid "source_color"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:781
msgid "Used as color."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:783
msgid "**int, float**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:783
msgid "hint_range(min, max[, step])"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:783
msgid "Restricted to values in a range (with min/max/step)."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:785
msgid "Used as albedo color."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:787
msgid "hint_normal"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:787
msgid "Used as normalmap."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:789
msgid "hint_default_white"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:789
msgid "As value or albedo color, default to opaque white."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:791
msgid "hint_default_black"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:791
msgid "As value or albedo color, default to opaque black."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:793
msgid "hint_default_transparent"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:793
msgid "As value or albedo color, default to transparent black."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:795
msgid "hint_anisotropy"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:795
msgid "As flowmap, default to right."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:797
msgid "hint_roughness[_r, _g, _b, _a, _normal, _gray]"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:797
msgid ""
"Used for roughness limiter on import (attempts reducing specular aliasing). "
"``_normal`` is a normal map that guides the roughness limiter, with "
"roughness increasing in areas that have high-frequency detail."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:801
msgid "filter[_nearest, _linear][_mipmap][_anisotropic]"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:801
msgid "Enabled specified texture filtering."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:803
msgid "repeat[_enable, _disable]"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:803
msgid "Enabled texture repeating."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:805
msgid "hint_screen_texture"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:805
msgid "Texture is the screen texture."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:807
msgid "hint_depth_texture"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:807
msgid "Texture is the depth texture."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:809
msgid "hint_normal_roughness_texture"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:809
msgid "Texture is the normal roughness texture (only supported in Forward+)."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:812
msgid ""
"GDScript uses different variable types than GLSL does, so when passing "
"variables from GDScript to shaders, Godot converts the type automatically. "
"Below is a table of the corresponding types:"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:817
msgid "GLSL type"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:817
msgid "GDScript type"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:821
#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:831
#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:833
msgid "Bitwise packed int where bit 0 (LSB) corresponds to x."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:823
msgid "For example, a bvec2 of (bx, by) could be created in the following way:"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:837
#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:845
msgid "**Vector2i**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:839
#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:847
msgid "**Vector3i**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:841
#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:849
msgid "**Vector4i**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:853
msgid "**Vector2**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:855
msgid "**Vector3**, **Color**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:855
msgid "When Color is used, it will be interpreted as (r, g, b)."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:857
msgid "**Vector4**, **Color**, **Rect2**, **Plane**, **Quaternion**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:857
msgid "When Color is used, it will be interpreted as (r, g, b, a)."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:859
msgid ""
"When Rect2 is used, it will be interpreted as (position.x, position.y, size."
"x, size.y)."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:862
msgid ""
"When Plane is used it will be interpreted as (normal.x, normal.y, normal.z, "
"d)."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:867
msgid "**Transform2D**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:872
msgid "**mat4** **mat4**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:872
msgid "**Projection**, **Transform3D**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:872
msgid "When a Transform3D is used, the w Vector is set to the identity."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:875
#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:877
#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:879
msgid "**Texture2D**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:881
#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:883
#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:885
msgid "**Texture2DArray**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:887
#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:889
#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:891
msgid "**Texture3D**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:893
msgid "**Cubemap**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:895
msgid "**CubemapArray**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:898
msgid ""
"Be careful when setting shader uniforms from GDScript, no error will be "
"thrown if the type does not match. Your shader will just exhibit undefined "
"behavior."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:902
msgid "Uniforms can also be assigned default values:"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:911
msgid ""
"Note that when adding a default value and a hint, the default value goes "
"after the hint."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:913
msgid ""
"If you need to make multiple uniforms to be grouped in the specific category "
"of an inspector, you can use a `group_uniform` keyword like:"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:920
msgid "You can close the group by using:"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:926
msgid ""
"The syntax also supports subgroups (it's not mandatory to declare the base "
"group before this):"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:933
msgid "Global uniforms"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:935
msgid ""
"Sometimes, you want to modify a parameter in many different shaders at once. "
"With a regular uniform, this takes a lot of work as all these shaders need "
"to be tracked and the uniform needs to be set for each of them. Global "
"uniforms allow you to create and update uniforms that will be available in "
"all shaders, in every shader type (``canvas_item``, ``spatial``, "
"``particles``, ``sky`` and ``fog``)."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:942
msgid ""
"Global uniforms are especially useful for environmental effects that affect "
"many objects in a scene, like having foliage bend when the player is nearby, "
"or having objects move with the wind."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:946
msgid ""
"To create a global uniform, open the **Project Settings** then go to the "
"**Shader Globals** tab. Specify a name for the uniform (case-sensitive) and "
"a type, then click **Add** in the top-right corner of the dialog. You can "
"then edit the value assigned to the uniform by clicking the value in the "
"list of uniforms:"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:956
msgid ""
"Adding a global uniform in the Shader Globals tab of the Project Settings"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:958
msgid "After creating a global uniform, you can use it in a shader as follows:"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:970
msgid ""
"Note that the global uniform *must* exist in the Project Settings at the "
"time the shader is saved, or compilation will fail. While you can assign a "
"default value using ``global uniform vec4 my_color = ...`` in the shader "
"code, it will be ignored as the global uniform must always be defined in the "
"Project Settings anyway."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:976
msgid ""
"To change the value of a global uniform at run-time, use the :ref:"
"`RenderingServer.global_shader_parameter_set "
"<class_RenderingServer_method_global_shader_parameter_set>` method in a "
"script:"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:984
msgid ""
"Assigning global uniform values can be done as many times as desired without "
"impacting performance, as setting data doesn't require synchronization "
"between the CPU and GPU."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:988
msgid "You can also add or remove global uniforms at run-time:"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:995
msgid ""
"Adding or removing global uniforms at run-time has a performance cost, "
"although it's not as pronounced compared to getting global uniform values "
"from a script (see the warning below)."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1001
msgid ""
"While you *can* query the value of a global uniform at run-time in a script "
"using ``RenderingServer.global_shader_parameter_get(\"uniform_name\")``, "
"this has a large performance penalty as the rendering thread needs to "
"synchronize with the calling thread."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1006
msgid ""
"Therefore, it's not recommended to read global shader uniform values "
"continuously in a script. If you need to read values in a script after "
"setting them, consider creating an :ref:`autoload <doc_singletons_autoload>` "
"where you store the values you need to query at the same time you're setting "
"them as global uniforms."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1015
msgid "Per-instance uniforms"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1019
msgid "Per-instance uniforms are only available in ``spatial`` (3D) shaders."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1021
msgid ""
"Sometimes, you want to modify a parameter on each node using the material. "
"As an example, in a forest full of trees, when you want each tree to have a "
"slightly different color that is editable by hand. Without per-instance "
"uniforms, this requires creating a unique material for each tree (each with "
"a slightly different hue). This makes material management more complex, and "
"also has a performance overhead due to the scene requiring more unique "
"material instances. Vertex colors could also be used here, but they'd "
"require creating unique copies of the mesh for each different color, which "
"also has a performance overhead."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1030
msgid ""
"Per-instance uniforms are set on each GeometryInstance3D, rather than on "
"each Material instance. Take this into account when working with meshes that "
"have multiple materials assigned to them, or MultiMesh setups."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1046
msgid ""
"After saving the shader, you can change the per-instance uniform's value "
"using the inspector:"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1053
msgid ""
"Setting a per-instance uniform's value in the GeometryInstance3D section of "
"the inspector"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1055
msgid ""
"Per-instance uniform values can also be set at run-time using :ref:"
"`set_instance_shader_parameter "
"<class_GeometryInstance3D_method_set_instance_shader_parameter>` method on a "
"node that inherits from :ref:`class_GeometryInstance3D`:"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1063
msgid ""
"When using per-instance uniforms, there are some restrictions you should be "
"aware of:"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1065
msgid ""
"**Per-instance uniforms do not support textures**, only regular scalar and "
"vector types. As a workaround, you can pass a texture array as a regular "
"uniform, then pass the index of the texture to be drawn using a per-instance "
"uniform."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1069
msgid "There is a practical maximum limit of 16 instance uniforms per shader."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1070
msgid ""
"If your mesh uses multiple materials, the parameters for the first mesh "
"material found will \"win\" over the subsequent ones, unless they have the "
"same name, index *and* type. In this case, all parameters are affected "
"correctly."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1073
msgid ""
"If you run into the above situation, you can avoid clashes by manually "
"specifying the index (0-15) of the instance uniform by using the "
"``instance_index`` hint:"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1082
msgid "Built-in variables"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1084
msgid ""
"A large number of built-in variables are available, like ``UV``, ``COLOR`` "
"and ``VERTEX``. What variables are available depends on the type of shader "
"(``spatial``, ``canvas_item`` or ``particle``) and the function used "
"(``vertex``, ``fragment`` or ``light``). For a list of the built-in "
"variables that are available, please see the corresponding pages:"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1087
#, fuzzy
msgid ":ref:`Spatial shaders <doc_spatial_shader>`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1088
msgid ":ref:`Canvas item shaders <doc_canvas_item_shader>`"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1089
msgid ":ref:`Particle shaders <doc_particle_shader>`"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1090
#, fuzzy
msgid ":ref:`Sky shaders <doc_sky_shader>`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1091
#, fuzzy
msgid ":ref:`Fog shaders <doc_fog_shader>`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1096
msgid ""
"A large number of built-in functions are supported, conforming to GLSL ES "
"3.0. When vec_type (float), vec_int_type, vec_uint_type, vec_bool_type "
"nomenclature is used, it can be scalar or vector."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1101
msgid "Description / Return value"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1103
msgid "vec_type **radians** (vec_type degrees)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1103
msgid "Convert degrees to radians."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1105
msgid "vec_type **degrees** (vec_type radians)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1105
msgid "Convert radians to degrees."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1107
msgid "vec_type **sin** (vec_type x)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1107
msgid "Sine."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1109
msgid "vec_type **cos** (vec_type x)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1109
msgid "Cosine."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1111
msgid "vec_type **tan** (vec_type x)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1111
msgid "Tangent."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1113
msgid "vec_type **asin** (vec_type x)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1113
msgid "Arcsine."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1115
msgid "vec_type **acos** (vec_type x)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1115
msgid "Arccosine."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1117
msgid "vec_type **atan** (vec_type y_over_x)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1117
#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1119
msgid "Arctangent."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1119
msgid "vec_type **atan** (vec_type y, vec_type x)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1121
msgid "vec_type **sinh** (vec_type x)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1121
msgid "Hyperbolic sine."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1123
msgid "vec_type **cosh** (vec_type x)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1123
msgid "Hyperbolic cosine."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1125
msgid "vec_type **tanh** (vec_type x)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1125
msgid "Hyperbolic tangent."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1127
msgid "vec_type **asinh** (vec_type x)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1127
msgid "Inverse hyperbolic sine."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1129
msgid "vec_type **acosh** (vec_type x)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1129
msgid "Inverse hyperbolic cosine."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1131
msgid "vec_type **atanh** (vec_type x)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1131
msgid "Inverse hyperbolic tangent."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1133
msgid "vec_type **pow** (vec_type x, vec_type y)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1133
msgid "Power (undefined if ``x`` < 0 or if ``x`` == 0 and ``y`` <= 0)."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1135
msgid "vec_type **exp** (vec_type x)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1135
msgid "Base-e exponential."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1137
msgid "vec_type **exp2** (vec_type x)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1137
msgid "Base-2 exponential."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1139
msgid "vec_type **log** (vec_type x)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1139
msgid "Natural logarithm."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1141
msgid "vec_type **log2** (vec_type x)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1141
msgid "Base-2 logarithm."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1143
msgid "vec_type **sqrt** (vec_type x)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1143
msgid "Square root."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1145
msgid "vec_type **inversesqrt** (vec_type x)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1145
msgid "Inverse square root."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1147
msgid "vec_type **abs** (vec_type x)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1149
msgid "ivec_type **abs** (ivec_type x)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1147
msgid "Absolute value (returns positive value if negative)."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1151
msgid "vec_type **sign** (vec_type x)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1153
msgid "ivec_type **sign** (ivec_type x)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1151
msgid ""
"Sign (returns ``1.0`` if positive, ``-1.0`` if negative, ``0.0`` if zero)."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1155
msgid "vec_type **floor** (vec_type x)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1155
msgid "Round to the integer below."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1157
msgid "vec_type **round** (vec_type x)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1157
msgid "Round to the nearest integer."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1159
msgid "vec_type **roundEven** (vec_type x)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1159
msgid "Round to the nearest even integer."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1161
msgid "vec_type **trunc** (vec_type x)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1161
#, fuzzy
msgid "Truncation."
msgstr "Uvod"

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1163
msgid "vec_type **ceil** (vec_type x)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1163
msgid "Round to the integer above."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1165
msgid "vec_type **fract** (vec_type x)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1165
msgid "Fractional (returns ``x - floor(x)``)."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1167
msgid "vec_type **mod** (vec_type x, vec_type y)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1169
msgid "vec_type **mod** (vec_type x, float y)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1167
msgid "Modulo (division remainder)."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1171
msgid "vec_type **modf** (vec_type x, out vec_type i)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1171
msgid "Fractional of ``x``, with ``i`` as integer part."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1173
msgid "vec_type  **min** (vec_type a, vec_type b)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1173
msgid "Lowest value between ``a`` and ``b``."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1175
msgid "vec_type  **max** (vec_type a, vec_type b)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1175
msgid "Highest value between ``a`` and ``b``."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1177
msgid "vec_type **clamp** (vec_type x, vec_type min, vec_type max)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1177
msgid "Clamp ``x`` between ``min`` and ``max`` (inclusive)."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1179
msgid "float **mix** (float a, float b, float c)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1181
msgid "vec_type **mix** (vec_type a, vec_type b, float c)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1183
msgid "vec_type **mix** (vec_type a, vec_type b, bvec_type c)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1179
msgid "Linear interpolate between ``a`` and ``b`` by ``c``."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1185
msgid "vec_type **fma** (vec_type a, vec_type b, vec_type c)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1185
msgid ""
"Performs a fused multiply-add operation: ``(a * b + c)`` (faster than doing "
"it manually)."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1188
msgid "vec_type **step** (vec_type a, vec_type b)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1188
msgid "``b[i] < a[i] ? 0.0 : 1.0``."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1190
msgid "vec_type **step** (float a, vec_type b)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1190
msgid "``b[i] < a ? 0.0 : 1.0``."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1192
msgid "vec_type **smoothstep** (vec_type a, vec_type b, vec_type c)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1194
msgid "vec_type **smoothstep** (float a, float b, vec_type c)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1192
msgid "Hermite interpolate between ``a`` and ``b`` by ``c``."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1196
msgid "bvec_type **isnan** (vec_type x)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1196
msgid "Returns ``true`` if scalar or vector component is ``NaN``."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1198
msgid "bvec_type **isinf** (vec_type x)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1198
msgid "Returns ``true`` if scalar or vector component is ``INF``."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1200
msgid "ivec_type **floatBitsToInt** (vec_type x)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1200
msgid "Float->Int bit copying, no conversion."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1202
msgid "uvec_type **floatBitsToUint** (vec_type x)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1202
msgid "Float->UInt bit copying, no conversion."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1204
msgid "vec_type **intBitsToFloat** (ivec_type x)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1204
msgid "Int->Float bit copying, no conversion."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1206
msgid "vec_type **uintBitsToFloat** (uvec_type x)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1206
msgid "UInt->Float bit copying, no conversion."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1208
msgid "float **length** (vec_type x)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1208
msgid "Vector length."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1210
msgid "float **distance** (vec_type a, vec_type b)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1210
msgid "Distance between vectors i.e ``length(a - b)``."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1212
msgid "float **dot** (vec_type a, vec_type b)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1212
msgid "Dot product."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1214
msgid "vec3 **cross** (vec3 a, vec3 b)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1214
msgid "Cross product."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1216
msgid "vec_type **normalize** (vec_type x)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1216
msgid "Normalize to unit length."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1218
msgid "vec3 **reflect** (vec3 I, vec3 N)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1218
msgid "Reflect."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1220
msgid "vec3 **refract** (vec3 I, vec3 N, float eta)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1220
msgid "Refract."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1222
msgid "vec_type **faceforward** (vec_type N, vec_type I, vec_type Nref)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1222
msgid "If ``dot(Nref, I)`` < 0, return ``N``, otherwise ``-N``."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1224
msgid "mat_type **matrixCompMult** (mat_type x, mat_type y)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1224
msgid "Matrix component multiplication."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1226
msgid "mat_type **outerProduct** (vec_type column, vec_type row)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1226
msgid "Matrix outer product."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1228
msgid "mat_type **transpose** (mat_type m)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1228
msgid "Transpose matrix."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1230
msgid "float **determinant** (mat_type m)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1230
msgid "Matrix determinant."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1232
msgid "mat_type **inverse** (mat_type m)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1232
msgid "Inverse matrix."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1234
msgid "bvec_type **lessThan** (vec_type x, vec_type y)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1234
msgid "Bool vector comparison on < int/uint/float vectors."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1236
msgid "bvec_type **greaterThan** (vec_type x, vec_type y)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1236
msgid "Bool vector comparison on > int/uint/float vectors."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1238
msgid "bvec_type **lessThanEqual** (vec_type x, vec_type y)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1238
msgid "Bool vector comparison on <= int/uint/float vectors."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1240
msgid "bvec_type **greaterThanEqual** (vec_type x, vec_type y)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1240
msgid "Bool vector comparison on >= int/uint/float vectors."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1242
msgid "bvec_type **equal** (vec_type x, vec_type y)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1242
msgid "Bool vector comparison on == int/uint/float vectors."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1244
msgid "bvec_type **notEqual** (vec_type x, vec_type y)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1244
msgid "Bool vector comparison on != int/uint/float vectors."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1246
msgid "bool **any** (bvec_type x)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1246
msgid "``true`` if any component is ``true``, ``false`` otherwise."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1248
msgid "bool **all** (bvec_type x)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1248
msgid "``true`` if all components are ``true``, ``false`` otherwise."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1250
msgid "bvec_type **not** (bvec_type x)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1250
msgid "Invert boolean vector."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1252
msgid "ivec2 **textureSize** (gsampler2D s, int lod)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1254
msgid "ivec3 **textureSize** (gsampler2DArray s, int lod)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1256
msgid "ivec3 **textureSize** (gsampler3D s, int lod)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1258
msgid "ivec2 **textureSize** (samplerCube s, int lod)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1260
msgid "ivec2 **textureSize** (samplerCubeArray s, int lod)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1252
#, fuzzy
msgid "Get the size of a texture."
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1254
#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1332
msgid ""
"The LOD defines which mipmap level is used. An LOD value of ``0`` will use "
"the full resolution texture."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1262
msgid "vec2 **textureQueryLod** (gsampler2D s, vec2 p)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1264
msgid "vec3 **textureQueryLod** (gsampler2DArray s, vec2 p)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1266
msgid "vec2 **textureQueryLod** (gsampler3D s, vec3 p)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1268
msgid "vec2 **textureQueryLod** (samplerCube s, vec3 p)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1262
msgid ""
"Compute the level-of-detail that would be used to sample from a texture. The "
"``x`` component of the resulted value is the mipmap array that would be "
"accessed. The ``y`` component is computed level-of-detail relative to the "
"base level (regardless of the mipmap levels of the texture)."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1270
msgid "int **textureQueryLevels** (gsampler2D s)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1272
msgid "int **textureQueryLevels** (gsampler2DArray s)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1274
msgid "int **textureQueryLevels** (gsampler3D s)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1276
msgid "int **textureQueryLevels** (samplerCube s)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1270
msgid "Get the number of accessible mipmap levels of a texture."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1272
msgid ""
"If the texture is unassigned to a sampler, ``1`` is returned (Godot always "
"internally assigns a texture even to an empty sampler)."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1278
msgid "gvec4_type **texture** (gsampler2D s, vec2 p [, float bias])"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1280
msgid "gvec4_type **texture** (gsampler2DArray s, vec3 p [, float bias])"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1282
msgid "gvec4_type **texture** (gsampler3D s, vec3 p [, float bias])"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1284
msgid "vec4 **texture** (samplerCube s, vec3 p [, float bias])"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1286
msgid "vec4 **texture** (samplerCubeArray s, vec4 p [, float bias])"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1278
msgid "Perform a texture read."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1288
msgid "gvec4_type **textureProj** (gsampler2D s, vec3 p [, float bias])"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1290
msgid "gvec4_type **textureProj** (gsampler2D s, vec4 p [, float bias])"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1292
msgid "gvec4_type **textureProj** (gsampler3D s, vec4 p [, float bias])"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1288
msgid "Perform a texture read with projection."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1294
msgid "gvec4_type **textureLod** (gsampler2D s, vec2 p, float lod)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1296
msgid "gvec4_type **textureLod** (gsampler2DArray s, vec3 p, float lod)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1298
msgid "gvec4_type **textureLod** (gsampler3D s, vec3 p, float lod)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1300
msgid "vec4 **textureLod** (samplerCube s, vec3 p, float lod)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1302
msgid "vec4 **textureLod** (samplerCubeArray s, vec4 p, float lod)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1294
msgid "Perform a texture read at custom mipmap."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1296
#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1306
msgid ""
"The LOD defines which mipmap level is used. An LOD value of ``0.0`` will use "
"the full resolution texture. If the texture lacks mipmaps, all LOD values "
"will act like ``0.0``."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1304
msgid "gvec4_type **textureProjLod** (gsampler2D s, vec3 p, float lod)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1306
msgid "gvec4_type **textureProjLod** (gsampler2D s, vec4 p, float lod)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1308
msgid "gvec4_type **textureProjLod** (gsampler3D s, vec4 p, float lod)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1304
msgid "Performs a texture read with projection/LOD."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1310
msgid "gvec4_type **textureGrad** (gsampler2D s, vec2 p, vec2 dPdx, vec2 dPdy)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1313
msgid ""
"gvec4_type **textureGrad** (gsampler2DArray s, vec3 p, vec2 dPdx, vec2 dPdy)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1316
msgid "gvec4_type **textureGrad** (gsampler3D s, vec3 p, vec2 dPdx, vec2 dPdy)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1319
msgid "vec4 **textureGrad** (samplerCube s, vec3 p, vec3 dPdx, vec3 dPdy)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1321
msgid "vec4 **textureGrad** (samplerCubeArray s, vec3 p, vec3 dPdx, vec3 dPdy)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1310
msgid "Performs a texture read with explicit gradients."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1324
msgid ""
"gvec4_type **textureProjGrad** (gsampler2D s, vec3 p, vec2 dPdx, vec2 dPdy)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1326
msgid ""
"gvec4_type **textureProjGrad** (gsampler2D s, vec4 p, vec2 dPdx, vec2 dPdy)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1328
msgid ""
"gvec4_type **textureProjGrad** (gsampler3D s, vec4 p, vec3 dPdx, vec3 dPdy)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1324
msgid ""
"Performs a texture read with projection/LOD and with explicit gradients."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1330
msgid "gvec4_type **texelFetch** (gsampler2D s, ivec2 p, int lod)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1332
msgid "gvec4_type **texelFetch** (gsampler2DArray s, ivec3 p, int lod)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1334
msgid "gvec4_type **texelFetch** (gsampler3D s, ivec3 p, int lod)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1330
msgid "Fetches a single texel using integer coordinates."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1336
msgid "gvec4_type **textureGather** (gsampler2D s, vec2 p [, int comps])"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1338
msgid "gvec4_type **textureGather** (gsampler2DArray s, vec3 p [, int comps])"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1340
msgid "vec4 **textureGather** (samplerCube s, vec3 p [, int comps])"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1336
msgid ""
"Gathers four texels from a texture. Use ``comps`` within range of 0..3 to "
"define which component (x, y, z, w) is returned. If ``comps`` is not "
"provided: 0 (or x-component) is used."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1342
msgid "vec_type **dFdx** (vec_type p)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1342
msgid ""
"Derivative in ``x`` using local differencing. Internally, can use either "
"``dFdxCoarse`` or ``dFdxFine``, but the decision for which to use is made by "
"the GPU driver."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1346
msgid "vec_type **dFdxCoarse** (vec_type p)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1346
msgid ""
"Calculates derivative with respect to ``x`` window coordinate using local "
"differencing based on the value of ``p`` for the current fragment "
"neighbour(s), and will possibly, but not necessarily, include the value for "
"the current fragment. This function is not available on ``gl_compatibility`` "
"profile."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1352
msgid "vec_type **dFdxFine** (vec_type p)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1352
msgid ""
"Calculates derivative with respect to ``x`` window coordinate using local "
"differencing based on the value of ``p`` for the current fragment and its "
"immediate neighbour(s). This function is not available on "
"``gl_compatibility`` profile."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1357
msgid "vec_type **dFdy** (vec_type p)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1357
msgid ""
"Derivative in ``y`` using local differencing. Internally, can use either "
"``dFdyCoarse`` or ``dFdyFine``, but the decision for which to use is made by "
"the GPU driver."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1361
msgid "vec_type **dFdyCoarse** (vec_type p)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1361
msgid ""
"Calculates derivative with respect to ``y`` window coordinate using local "
"differencing based on the value of ``p`` for the current fragment "
"neighbour(s), and will possibly, but not necessarily, include the value for "
"the current fragment. This function is not available on ``gl_compatibility`` "
"profile."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1367
msgid "vec_type **dFdyFine** (vec_type p)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1367
msgid ""
"Calculates derivative with respect to ``y`` window coordinate using local "
"differencing based on the value of ``p`` for the current fragment and its "
"immediate neighbour(s). This function is not available on "
"``gl_compatibility`` profile."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1372
msgid "vec_type **fwidth** (vec_type p)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1372
msgid ""
"Sum of absolute derivative in ``x`` and ``y``. This is the equivalent of "
"using ``abs(dFdx(p)) + abs(dFdy(p))``."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1375
msgid "vec_type **fwidthCoarse** (vec_type p)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1375
msgid ""
"Sum of absolute derivative in ``x`` and ``y``. This is the equivalent of "
"using ``abs(dFdxCoarse(p)) + abs(dFdyCoarse(p))``. This function is not "
"available on ``gl_compatibility`` profile."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1380
msgid "vec_type **fwidthFine** (vec_type p)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1380
msgid ""
"Sum of absolute derivative in ``x`` and ``y``. This is the equivalent of "
"using ``abs(dFdxFine(p)) + abs(dFdyFine(p))``. This function is not "
"available on ``gl_compatibility`` profile."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1385
msgid "uint **packHalf2x16** (vec2 v)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1387
msgid "vec2 **unpackHalf2x16** (uint v)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1385
msgid ""
"Convert two 32-bit floating-point numbers into 16-bit and pack them into a "
"32-bit unsigned integer and vice-versa."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1389
msgid "uint **packUnorm2x16** (vec2 v)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1391
msgid "vec2 **unpackUnorm2x16** (uint v)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1389
msgid ""
"Convert two 32-bit floating-point numbers (clamped within 0..1 range) into "
"16-bit and pack them into a 32-bit unsigned integer and vice-versa."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1393
msgid "uint **packSnorm2x16** (vec2 v)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1395
msgid "vec2 **unpackSnorm2x16** (uint v)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1393
msgid ""
"Convert two 32-bit floating-point numbers (clamped within -1..1 range) into "
"16-bit and pack them into a 32-bit unsigned integer and vice-versa."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1397
msgid "uint **packUnorm4x8** (vec4 v)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1399
msgid "vec4 **unpackUnorm4x8** (uint v)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1397
msgid ""
"Convert four 32-bit floating-point numbers (clamped within 0..1 range) into "
"8-bit and pack them into a 32-bit unsigned integer and vice-versa."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1401
msgid "uint **packSnorm4x8** (vec4 v)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1403
msgid "vec4 **unpackSnorm4x8** (uint v)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1401
msgid ""
"Convert four 32-bit floating-point numbers (clamped within -1..1 range) into "
"8-bit and pack them into a 32-bit unsigned integer and vice-versa."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1405
msgid "ivec_type **bitfieldExtract** (ivec_type value, int offset, int bits)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1407
msgid "uvec_type **bitfieldExtract** (uvec_type value, int offset, int bits)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1405
msgid "Extracts a range of bits from an integer."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1409
msgid ""
"ivec_type **bitfieldInsert** (ivec_type base, ivec_type insert, int offset, "
"int bits)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1412
msgid ""
"uvec_type **bitfieldInsert** (uvec_type base, uvec_type insert, int offset, "
"int bits)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1409
msgid "Insert a range of bits into an integer."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1415
msgid "ivec_type **bitfieldReverse** (ivec_type value)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1417
msgid "uvec_type **bitfieldReverse** (uvec_type value)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1415
msgid "Reverse the order of bits in an integer."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1419
msgid "ivec_type **bitCount** (ivec_type value)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1421
msgid "uvec_type **bitCount** (uvec_type value)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1419
msgid "Counts the number of 1 bits in an integer."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1423
msgid "ivec_type **findLSB** (ivec_type value)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1425
msgid "uvec_type **findLSB** (uvec_type value)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1423
msgid "Find the index of the least significant bit set to 1 in an integer."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1427
msgid "ivec_type **findMSB** (ivec_type value)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1429
msgid "uvec_type **findMSB** (uvec_type value)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1427
msgid "Find the index of the most significant bit set to 1 in an integer."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1431
msgid ""
"void **imulExtended** (ivec_type x, ivec_type y, out ivec_type msb, out "
"ivec_type lsb)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1434
msgid ""
"void **umulExtended** (uvec_type x, uvec_type y, out uvec_type msb, out "
"uvec_type lsb)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1431
msgid ""
"Multiplies two 32-bit numbers and produce a 64-bit result. ``x`` - the first "
"number. ``y`` - the second number. ``msb`` - will contain the most "
"significant bits. ``lsb`` - will contain the least significant bits."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1437
msgid "uvec_type **uaddCarry** (uvec_type x, uvec_type y, out uvec_type carry)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1437
msgid "Adds two unsigned integers and generates carry."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1439
msgid ""
"uvec_type **usubBorrow** (uvec_type x, uvec_type y, out uvec_type borrow)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1439
msgid "Subtracts two unsigned integers and generates borrow."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1441
msgid "vec_type **ldexp** (vec_type x, out ivec_type exp)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1441
msgid "Assemble a floating-point number from a value and exponent."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1443
msgid ""
"If this product is too large to be represented in the floating-point type "
"the result is undefined."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1446
msgid "vec_type **frexp** (vec_type x, out ivec_type exp)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1446
msgid ""
"Splits a floating-point number(``x``) into significand (in the range of "
"[0.5, 1.0]) and an integral exponent."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shading_language.rst:1449
msgid ""
"For ``x`` equals zero the significand and exponent are both zero. For ``x`` "
"of infinity or NaN, the results are undefined."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shader_preprocessor.rst:4
msgid "Shader preprocessor"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shader_preprocessor.rst:7
msgid "Why use a shader preprocessor?"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shader_preprocessor.rst:9
msgid ""
"In programming languages, a *preprocessor* allows changing the code before "
"the compiler reads it. Unlike the compiler, the preprocessor does not care "
"about whether the syntax of the preprocessed code is valid. The preprocessor "
"always performs what the *directives* tell it to do. A directive is a "
"statement starting with a hash symbol (``#``). It is not a *keyword* of the "
"shader language (such as ``if`` or ``for``), but a special kind of token "
"within the language."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shader_preprocessor.rst:17
msgid ""
"From Godot 4.0 onwards, you can use a shader preprocessor within text-based "
"shaders. The syntax is similar to what most GLSL shader compilers support "
"(which in turn is similar to the C/C++ preprocessor)."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shader_preprocessor.rst:23
msgid ""
"The shader preprocessor is not available in :ref:`visual shaders "
"<doc_visual_shaders>`. If you need to introduce preprocessor statements to a "
"visual shader, you can convert it to a text-based shader using the **Convert "
"to Shader** option in the VisualShader inspector resource dropdown. This "
"conversion is a one-way operation; text shaders cannot be converted back to "
"visual shaders."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shader_preprocessor.rst:30
#, fuzzy
msgid "Directives"
msgstr "Uvod"

#: ../../docs/tutorials/shaders/shader_reference/shader_preprocessor.rst:33
msgid "General syntax"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shader_preprocessor.rst:35
msgid ""
"Preprocessor directives do not use brackets (``{}``), but can use "
"parentheses."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shader_preprocessor.rst:36
msgid ""
"Preprocessor directives **never** end with semicolons (with the exception of "
"``#define``, where this is allowed but potentially dangerous)."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shader_preprocessor.rst:38
msgid ""
"Preprocessor directives can span several lines by ending each line with a "
"backslash (``\\``). The first line break *not* featuring a backslash will "
"end the preprocessor statement."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shader_preprocessor.rst:43
msgid "#define"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shader_preprocessor.rst:45
msgid "**Syntax:** ``#define <identifier> [replacement_code]``."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shader_preprocessor.rst:47
msgid ""
"Defines the identifier after that directive as a macro, and replaces all "
"successive occurrences of it with the replacement code given in the shader. "
"Replacement is performed on a \"whole words\" basis, which means no "
"replacement is performed if the string is part of another string (without "
"any spaces or operators separating it)."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shader_preprocessor.rst:53
msgid ""
"Defines with replacements may also have one or more *arguments*, which can "
"then be passed when referencing the define (similar to a function call)."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shader_preprocessor.rst:56
msgid ""
"If the replacement code is not defined, the identifier may only be used with "
"``#ifdef`` or ``#ifndef`` directives."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shader_preprocessor.rst:59
msgid ""
"If the *concatenation* symbol (``##``) is present in the replacement code "
"then it will be removed upon macro insertion, together with any space "
"surrounding it, and join the surrounding words and arguments into a new "
"token."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shader_preprocessor.rst:74
msgid ""
"Compared to constants (``const CONSTANT = value;``), ``#define`` can be used "
"anywhere within the shader (including in uniform hints). ``#define`` can "
"also be used to insert arbitrary shader code at any location, while "
"constants can't do that."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shader_preprocessor.rst:109
msgid ""
"Defining a ``#define`` for an identifier that is already defined results in "
"an error. To prevent this, use ``#undef <identifier>``."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shader_preprocessor.rst:113
msgid "#undef"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shader_preprocessor.rst:115
msgid "**Syntax:** ``#undef identifier``"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shader_preprocessor.rst:117
msgid ""
"The ``#undef`` directive may be used to cancel a previously defined "
"``#define`` directive:"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shader_preprocessor.rst:138
msgid ""
"Without ``#undef`` in the above example, there would be a macro redefinition "
"error."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shader_preprocessor.rst:141
msgid "#if"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shader_preprocessor.rst:143
msgid "**Syntax:** ``#if <condition>``"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shader_preprocessor.rst:145
msgid ""
"The ``#if`` directive checks whether the ``condition`` passed. If it "
"evaluates to a non-zero value, the code block is included, otherwise it is "
"skipped."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shader_preprocessor.rst:148
msgid ""
"To evaluate correctly, the condition must be an expression giving a simple "
"floating-point, integer or boolean result. There may be multiple condition "
"blocks connected by ``&&`` (AND) or ``||`` (OR) operators. It may be "
"continued by a ``#else`` block, but **must** be ended with the ``#endif`` "
"directive."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shader_preprocessor.rst:163
msgid ""
"Using the ``defined()`` *preprocessor function*, you can check whether the "
"passed identifier is defined a by ``#define`` placed above that directive. "
"This is useful for creating multiple shader versions in the same file. It "
"may be continued by a ``#else`` block, but must be ended with the ``#endif`` "
"directive."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shader_preprocessor.rst:168
msgid ""
"The ``defined()`` function's result can be negated by using the ``!`` "
"(boolean NOT) symbol in front of it. This can be used to check whether a "
"define is *not* set."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shader_preprocessor.rst:181
msgid ""
"Be careful, as ``defined()`` must only wrap a single identifier within "
"parentheses, never more:"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shader_preprocessor.rst:192
msgid ""
"In the shader editor, preprocessor branches that evaluate to ``false`` (and "
"are therefore excluded from the final compiled shader) will appear grayed "
"out. This does not apply to run-time ``if`` statements."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shader_preprocessor.rst:196
msgid "**#if preprocessor versus if statement: Performance caveats**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shader_preprocessor.rst:198
msgid ""
"The :ref:`shading language <doc_shading_language>` supports run-time ``if`` "
"statements:"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shader_preprocessor.rst:210
msgid ""
"If the uniform is never changed, this behaves identical to the following "
"usage of the ``#if`` preprocessor statement:"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shader_preprocessor.rst:223
msgid ""
"However, the ``#if`` variant can be faster in certain scenarios. This is "
"because all run-time branches in a shader are still compiled and variables "
"within those branches may still take up register space, even if they are "
"never run in practice."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shader_preprocessor.rst:228
msgid ""
"Modern GPUs are `quite effective <https://medium.com/@jasonbooth_86226/"
"branching-on-a-gpu-18bfc83694f2>`__ at performing \"static\" branching. "
"\"Static\" branching refers to ``if`` statements where *all* pixels/vertices "
"evaluate to the same result in a given shader invocation. However, high "
"amounts of :abbr:`VGPRs (Vector General-Purpose Register)` (which can be "
"caused by having too many branches) can still slow down shader execution "
"significantly."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shader_preprocessor.rst:235
msgid "#elif"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shader_preprocessor.rst:237
msgid ""
"The ``#elif`` directive stands for \"else if\" and checks the condition "
"passed if the above ``#if`` evaluated to ``false``. ``#elif`` can only be "
"used within an ``#if`` block. It is possible to use several ``#elif`` "
"statements after an ``#if`` statement."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shader_preprocessor.rst:255
msgid "Like with ``#if``, the ``defined()`` preprocessor function can be used:"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shader_preprocessor.rst:270
msgid "#ifdef"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shader_preprocessor.rst:272
msgid "**Syntax:** ``#ifdef <identifier>``"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shader_preprocessor.rst:274
msgid ""
"This is a shorthand for ``#if defined(...)``. Checks whether the passed "
"identifier is defined by ``#define`` placed above that directive. This is "
"useful for creating multiple shader versions in the same file. It may be "
"continued by a ``#else`` block, but must be ended with the ``#endif`` "
"directive."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shader_preprocessor.rst:287
msgid ""
"The processor does *not* support ``#elifdef`` as a shortcut for ``#elif "
"defined(...)``. Instead, use the following series of ``#ifdef`` and "
"``#else`` when you need more than two branches:"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shader_preprocessor.rst:306
msgid "#ifndef"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shader_preprocessor.rst:308
msgid "**Syntax:** ``#ifndef <identifier>``"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shader_preprocessor.rst:310
msgid ""
"This is a shorthand for ``#if !defined(...)``. Similar to ``#ifdef``, but "
"checks whether the passed identifier is **not** defined by ``#define`` "
"before that directive."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shader_preprocessor.rst:314
msgid ""
"This is the exact opposite of ``#ifdef``; it will always match in situations "
"where ``#ifdef`` would never match, and vice versa."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shader_preprocessor.rst:330
msgid "#else"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shader_preprocessor.rst:332
msgid "**Syntax:** ``#else``"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shader_preprocessor.rst:334
msgid ""
"Defines the optional block which is included when the previously defined "
"``#if``, ``#elif``, ``#ifdef`` or ``#ifndef`` directive evaluates to false."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shader_preprocessor.rst:352
msgid "#endif"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shader_preprocessor.rst:354
msgid "**Syntax:** ``#endif``"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shader_preprocessor.rst:356
msgid ""
"Used as terminator for the ``#if``, ``#ifdef``, ``#ifndef`` or subsequent "
"``#else`` directives."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shader_preprocessor.rst:359
msgid "#include"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shader_preprocessor.rst:361
msgid "**Syntax:** ``#include \"path\"``"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shader_preprocessor.rst:363
msgid ""
"The ``#include`` directive includes the *entire* content of a shader include "
"file in a shader. ``\"path\"`` can be an absolute ``res://`` path or "
"relative to the current shader file. Relative paths are only allowed in "
"shaders that are saved to ``.gdshader`` or ``.gdshaderinc`` files, while "
"absolute paths can be used in shaders that are built into a scene/resource "
"file."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shader_preprocessor.rst:369
msgid ""
"You can create new shader includes by using the **File > Create Shader "
"Include** menu option of the shader editor, or by creating a new :ref:"
"`ShaderInclude<class_ShaderInclude>` resource in the FileSystem dock."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shader_preprocessor.rst:373
msgid ""
"Shader includes can be included from within any shader, or other shader "
"include, at any point in the file."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shader_preprocessor.rst:376
msgid ""
"When including shader includes in the global scope of a shader, it is "
"recommended to do this after the initial ``shader_type`` statement."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shader_preprocessor.rst:379
msgid ""
"You can also include shader includes from within the body a function. Please "
"note that the shader editor is likely going to report errors for your shader "
"include's code, as it may not be valid outside of the context that it was "
"written for. You can either choose to ignore these errors (the shader will "
"still compile fine), or you can wrap the include in an ``#ifdef`` block that "
"checks for a define from your shader."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shader_preprocessor.rst:385
msgid ""
"``#include`` is useful for creating libraries of helper functions (or "
"macros) and reducing code duplication. When using ``#include``, be careful "
"about naming collisions, as redefining functions or macros is not allowed."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shader_preprocessor.rst:389
msgid "``#include`` is subject to several restrictions:"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shader_preprocessor.rst:391
msgid ""
"Only shader include resources (ending with ``.gdshaderinc``) can be "
"included. ``.gdshader`` files cannot be included by another shader, but a ``."
"gdshaderinc`` file can include other ``.gdshaderinc`` files."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shader_preprocessor.rst:394
msgid "Cyclic dependencies are **not** allowed and will result in an error."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shader_preprocessor.rst:395
msgid "To avoid infinite recursion, include depth is limited to 25 steps."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shader_preprocessor.rst:397
msgid "Example shader include file:"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shader_preprocessor.rst:409
msgid "Example base shader (using the include file we created above):"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shader_preprocessor.rst:425
msgid "#pragma"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shader_preprocessor.rst:427
msgid "**Syntax:** ``#pragma value``"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shader_preprocessor.rst:429
msgid ""
"The ``#pragma`` directive provides additional information to the "
"preprocessor or compiler."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/shader_preprocessor.rst:431
msgid ""
"Currently, it may have only one value: ``disable_preprocessor``. If you "
"don't need the preprocessor, use that directive to speed up shader "
"compilation by excluding the preprocessor step."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:4
msgid "Spatial shaders"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:6
msgid ""
"Spatial shaders are used for shading 3D objects. They are the most complex "
"type of shader Godot offers. Spatial shaders are highly configurable with "
"different render modes and different rendering options (e.g. Subsurface "
"Scattering, Transmission, Ambient Occlusion, Rim lighting etc). Users can "
"optionally write vertex, fragment, and light processor functions to affect "
"how objects are drawn."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:15
#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:17
#: ../../docs/tutorials/shaders/shader_reference/particle_shader.rst:34
#: ../../docs/tutorials/shaders/shader_reference/sky_shader.rst:130
msgid "Render mode"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:17
#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:19
msgid "**blend_mix**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:17
#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:19
msgid "Mix blend mode (alpha is transparency), default."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:19
#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:21
msgid "**blend_add**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:19
#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:21
msgid "Additive blend mode."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:21
#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:23
msgid "**blend_sub**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:21
#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:23
msgid "Subtractive blend mode."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:23
#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:25
msgid "**blend_mul**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:23
#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:25
msgid "Multiplicative blend mode."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:25
msgid "**depth_draw_opaque**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:25
msgid "Only draw depth for opaque geometry (not transparent)."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:27
msgid "**depth_draw_always**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:27
msgid "Always draw depth (opaque and transparent)."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:29
msgid "**depth_draw_never**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:29
msgid "Never draw depth."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:31
msgid "**depth_prepass_alpha**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:31
msgid "Do opaque depth pre-pass for transparent geometry."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:33
msgid "**depth_test_disabled**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:33
msgid "Disable depth testing."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:35
msgid "**sss_mode_skin**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:35
msgid "Subsurface Scattering mode for skin."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:37
msgid "**cull_back**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:37
msgid "Cull back-faces (default)."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:39
msgid "**cull_front**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:39
msgid "Cull front-faces."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:41
msgid "**cull_disabled**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:41
msgid "Culling disabled (double sided)."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:43
#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:31
msgid "**unshaded**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:43
#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:31
msgid "Result is just albedo. No lighting/shading happens in material."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:45
msgid "**wireframe**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:45
msgid "Geometry draws using lines."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:47
msgid "**diffuse_burley**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:47
msgid "Burley (Disney PBS) for diffuse (default)."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:49
msgid "**diffuse_lambert**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:49
msgid "Lambert shading for diffuse."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:51
msgid "**diffuse_lambert_wrap**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:51
msgid "Lambert wrapping (roughness dependent) for diffuse."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:53
msgid "**diffuse_toon**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:53
msgid "Toon shading for diffuse."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:55
msgid "**specular_schlick_ggx**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:55
msgid "Schlick-GGX for specular (default)."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:57
msgid "**specular_toon**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:57
msgid "Toon for specular."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:59
msgid "**specular_disabled**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:59
msgid "Disable specular."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:61
#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:35
msgid "**skip_vertex_transform**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:61
msgid "VERTEX/NORMAL/etc. need to be transformed manually in vertex function."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:63
#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:37
msgid "**world_vertex_coords**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:63
msgid "VERTEX/NORMAL/etc. are modified in world coordinates instead of local."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:65
msgid "**ensure_correct_normals**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:65
msgid "Use when non-uniform scale is applied to mesh."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:67
msgid "**shadows_disabled**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:67
msgid "Disable computing shadows in shader."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:69
msgid "**ambient_light_disabled**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:69
msgid "Disable contribution from ambient light and radiance map."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:71
msgid "**shadow_to_opacity**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:75
msgid "**vertex_lighting**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:75
msgid "Use vertex-based lighting."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:77
msgid "**particle_trails**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:77
msgid "Enables the trails when used on particles geometry."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:79
msgid "**alpha_to_coverage**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:79
#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:81
#, fuzzy
msgid ""
"Alpha antialiasing mode, see `here <https://github.com/godotengine/godot/"
"pull/40364>`_ for more."
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati raznorazne `Godot demo projects "
"<https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:81
msgid "**alpha_to_coverage_and_one**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:83
msgid "**fog_disabled**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:83
msgid ""
"Disable receiving depth-based or volumetric fog. Useful for blend_add "
"materials like particles."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:87
#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:41
#: ../../docs/tutorials/shaders/shader_reference/particle_shader.rst:46
#: ../../docs/tutorials/shaders/shader_reference/sky_shader.rst:140
#: ../../docs/tutorials/shaders/shader_reference/fog_shader.rst:22
msgid "Built-ins"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:89
#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:43
#: ../../docs/tutorials/shaders/shader_reference/particle_shader.rst:48
msgid ""
"Values marked as \"in\" are read-only. Values marked as \"out\" are for "
"optional writing and will not necessarily contain sensible values. Values "
"marked as \"inout\" provide a sensible default value, and can optionally be "
"written to. Samplers are not subjects of writing and they are not marked."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:95
#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:49
#: ../../docs/tutorials/shaders/shader_reference/particle_shader.rst:54
#: ../../docs/tutorials/shaders/shader_reference/sky_shader.rst:147
#: ../../docs/tutorials/shaders/shader_reference/fog_shader.rst:30
msgid "Global built-ins"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:97
#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:51
#: ../../docs/tutorials/shaders/shader_reference/particle_shader.rst:56
msgid "Global built-ins are available everywhere, including custom functions."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:100
#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:153
#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:247
#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:411
#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:54
#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:101
#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:159
#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:232
#: ../../docs/tutorials/shaders/shader_reference/particle_shader.rst:59
#: ../../docs/tutorials/shaders/shader_reference/particle_shader.rst:131
#: ../../docs/tutorials/shaders/shader_reference/particle_shader.rst:148
#: ../../docs/tutorials/shaders/shader_reference/sky_shader.rst:155
#: ../../docs/tutorials/shaders/shader_reference/sky_shader.rst:194
#: ../../docs/tutorials/shaders/shader_reference/fog_shader.rst:36
#: ../../docs/tutorials/shaders/shader_reference/fog_shader.rst:58
msgid "Built-in"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:102
#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:56
#: ../../docs/tutorials/shaders/shader_reference/particle_shader.rst:61
#: ../../docs/tutorials/shaders/shader_reference/sky_shader.rst:157
#: ../../docs/tutorials/shaders/shader_reference/fog_shader.rst:38
msgid "in float **TIME**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:102
#: ../../docs/tutorials/shaders/shader_reference/particle_shader.rst:61
#: ../../docs/tutorials/shaders/shader_reference/sky_shader.rst:157
#: ../../docs/tutorials/shaders/shader_reference/fog_shader.rst:38
msgid "Global time, in seconds."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:104
#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:62
#: ../../docs/tutorials/shaders/shader_reference/particle_shader.rst:63
#: ../../docs/tutorials/shaders/shader_reference/sky_shader.rst:180
#: ../../docs/tutorials/shaders/shader_reference/fog_shader.rst:40
msgid "in float **PI**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:104
#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:62
#: ../../docs/tutorials/shaders/shader_reference/particle_shader.rst:63
msgid ""
"A ``PI`` constant (``3.141592``). A ration of circle's circumference to its "
"diameter and amount of radians in half turn."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:107
#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:65
#: ../../docs/tutorials/shaders/shader_reference/particle_shader.rst:66
#: ../../docs/tutorials/shaders/shader_reference/sky_shader.rst:183
#: ../../docs/tutorials/shaders/shader_reference/fog_shader.rst:43
msgid "in float **TAU**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:107
#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:65
#: ../../docs/tutorials/shaders/shader_reference/particle_shader.rst:66
#: ../../docs/tutorials/shaders/shader_reference/sky_shader.rst:183
#: ../../docs/tutorials/shaders/shader_reference/fog_shader.rst:43
msgid ""
"A ``TAU`` constant (``6.283185``). An equivalent of ``PI * 2`` and amount of "
"radians in full turn."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:110
#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:68
#: ../../docs/tutorials/shaders/shader_reference/particle_shader.rst:69
#: ../../docs/tutorials/shaders/shader_reference/sky_shader.rst:186
#: ../../docs/tutorials/shaders/shader_reference/fog_shader.rst:46
msgid "in float **E**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:110
#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:68
#: ../../docs/tutorials/shaders/shader_reference/particle_shader.rst:69
#: ../../docs/tutorials/shaders/shader_reference/sky_shader.rst:186
#: ../../docs/tutorials/shaders/shader_reference/fog_shader.rst:46
msgid ""
"A ``E`` constant (``2.718281``). Euler's number and a base of the natural "
"logarithm."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:114
#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:73
msgid "Vertex built-ins"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:116
msgid ""
"Vertex data (``VERTEX``, ``NORMAL``, ``TANGENT``, ``BITANGENT``) are "
"presented in local model space. If not written to, these values will not be "
"modified and be passed through as they came."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:120
msgid ""
"They can optionally be presented in world space by using the "
"*world_vertex_coords* render mode."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:122
msgid ""
"Users can disable the built-in modelview transform (projection will still "
"happen later) and do it manually with the following code:"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:136
msgid ""
"Other built-ins, such as UV, UV2 and COLOR, are also passed through to the "
"fragment function if not modified."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:138
msgid ""
"Users can override the modelview and projection transforms using the "
"``POSITION`` built-in. When ``POSITION`` is used, the value from ``VERTEX`` "
"is ignored and projection does not happen. However, the value passed to the "
"fragment shader still comes from ``VERTEX``."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:142
#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:93
msgid ""
"For instancing, the INSTANCE_CUSTOM variable contains the instance custom "
"data. When using particles, this information is usually:"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:145
#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:96
msgid "**x**: Rotation angle in radians."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:146
#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:97
msgid "**y**: Phase during lifetime (0 to 1)."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:147
#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:98
msgid "**z**: Animation frame."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:149
msgid ""
"This allows you to easily adjust the shader to a particle system using "
"default particles material. When writing a custom particle shader, this "
"value can be used as desired."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:155
#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:249
#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:413
msgid "in vec2 **VIEWPORT_SIZE**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:155
#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:249
#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:413
msgid "Size of viewport (in pixels)."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:157
#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:274
#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:424
msgid "in mat4 **VIEW_MATRIX**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:157
#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:274
#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:424
msgid "World space to view space transform."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:159
#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:276
#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:422
msgid "in mat4 **INV_VIEW_MATRIX**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:159
#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:276
#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:422
msgid "View space to world space transform."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:161
#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:280
#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:428
msgid "in mat4 **INV_PROJECTION_MATRIX**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:161
#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:280
#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:428
msgid "Clip space to view space transform."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:163
#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:282
msgid "in vec3 **NODE_POSITION_WORLD**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:163
msgid "Node world space position."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:165
#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:284
msgid "in vec3 **NODE_POSITION_VIEW**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:165
msgid "Node view space position."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:167
#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:286
msgid "in vec3 **CAMERA_POSITION_WORLD**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:167
msgid "Camera world space position."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:169
#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:288
msgid "in vec3 **CAMERA_DIRECTION_WORLD**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:169
msgid "Camera world space direction."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:171
#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:267
#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:461
msgid "in bool **OUTPUT_IS_SRGB**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:171
#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:267
#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:461
msgid ""
"``true`` when output is in sRGB color space (this is ``true`` in the "
"Compatibility renderer, ``false`` in Forward+ and Forward Mobile)."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:175
msgid "in int **INSTANCE_ID**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:175
#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:114
msgid "Instance ID for instancing."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:177
#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:116
msgid "in vec4 **INSTANCE_CUSTOM**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:177
msgid "Instance custom data (for particles, mostly)."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:179
#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:292
msgid "in int **VIEW_INDEX**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:179
#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:292
msgid ""
"The view that we are rendering. ``VIEW_MONO_LEFT`` (``0``) for Mono (not "
"multiview) or left eye, ``VIEW_RIGHT`` (``1``) for right eye."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:183
#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:296
msgid "in int **VIEW_MONO_LEFT**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:183
#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:296
msgid "Constant for Mono or left eye, always ``0``."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:185
#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:298
msgid "in int **VIEW_RIGHT**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:185
#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:298
msgid "Constant for right eye, always ``1``."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:187
#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:300
msgid "in vec3 **EYE_OFFSET**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:187
#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:300
msgid ""
"Position offset for the eye being rendered. Only applicable for multiview "
"rendering."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:190
msgid "inout vec3 **VERTEX**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:190
msgid "Vertex in local coordinates."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:192
#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:126
msgid "in int **VERTEX_ID**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:192
#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:126
msgid "The index of the current vertex in the vertex buffer."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:194
#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:312
#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:187
msgid "inout vec3 **NORMAL**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:194
msgid "Normal in local coordinates."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:196
#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:314
msgid "inout vec3 **TANGENT**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:196
msgid "Tangent in local coordinates."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:198
#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:316
msgid "inout vec3 **BINORMAL**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:198
msgid "Binormal in local coordinates."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:200
msgid "out vec4 **POSITION**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:200
msgid "If written to, overrides final vertex position."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:202
#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:129
msgid "inout vec2 **UV**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:202
msgid "UV main channel."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:204
msgid "inout vec2 **UV2**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:204
msgid "UV secondary channel."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:206
#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:131
#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:203
#: ../../docs/tutorials/shaders/shader_reference/particle_shader.rst:94
msgid "inout vec4 **COLOR**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:206
msgid "Color from vertices."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:208
#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:338
msgid "out float **ROUGHNESS**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:208
msgid "Roughness for vertex lighting."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:210
#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:133
msgid "inout float **POINT_SIZE**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:210
msgid "Point size for point rendering."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:212
msgid "inout mat4 **MODELVIEW_MATRIX**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:212
msgid "Model space to view space transform (use if possible)."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:214
msgid "inout mat3 **MODELVIEW_NORMAL_MATRIX**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:216
msgid "inout mat4 **MODEL_MATRIX**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:216
#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:270
#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:420
msgid "Model space to world space transform."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:218
msgid "inout mat3 **MODEL_NORMAL_MATRIX**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:220
msgid "inout mat4 **PROJECTION_MATRIX**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:220
#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:278
#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:426
msgid "View space to clip space transform."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:222
msgid "inout uvec4 **BONE_INDICES**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:224
msgid "inout vec4 **BONE_WEIGHTS**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:226
msgid "in vec4 **CUSTOM0**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:228
msgid "in vec4 **CUSTOM1**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:230
msgid "in vec4 **CUSTOM2**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:232
msgid "in vec4 **CUSTOM3**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:237
msgid ""
"``MODELVIEW_MATRIX`` combines both the ``MODEL_MATRIX`` and ``VIEW_MATRIX`` "
"and is better suited when floating point issues may arise. For example, if "
"the object is very far away from the world origin, you may run into floating "
"point issues when using the separated ``MODEL_MATRIX`` and ``VIEW_MATRIX``."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:240
#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:137
msgid "Fragment built-ins"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:242
msgid ""
"The default use of a Godot fragment processor function is to set up the "
"material properties of your object and to let the built-in renderer handle "
"the final shading. However, you are not required to use all these "
"properties, and if you don't write to them, Godot will optimize away the "
"corresponding functionality."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:251
#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:415
#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:161
#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:234
msgid "in vec4 **FRAGCOORD**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:251
#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:415
msgid ""
"Coordinate of pixel center in screen space. ``xy`` specifies position in "
"window, ``z`` specifies fragment depth if ``DEPTH`` is not used. Origin is "
"lower-left."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:254
msgid "in bool **FRONT_FACING**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:254
msgid "``true`` if current face if front face."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:256
#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:436
msgid "in vec3 **VIEW**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:256
msgid ""
"Normalized vector from fragment position to camera (in view space). This is "
"the same for both perspective and orthogonal cameras."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:259
#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:432
#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:180
#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:241
msgid "in vec2 **UV**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:259
#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:432
msgid "UV that comes from vertex function."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:261
#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:434
msgid "in vec2 **UV2**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:261
#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:434
msgid "UV2 that comes from vertex function."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:263
#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:239
msgid "in vec4 **COLOR**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:263
msgid "COLOR that comes from vertex function."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:265
#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:166
#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:251
msgid "in vec2 **POINT_COORD**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:265
msgid "Point Coordinate for drawing points with POINT_SIZE."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:270
#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:420
#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:103
msgid "in mat4 **MODEL_MATRIX**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:272
msgid "in mat3 **MODEL_NORMAL_MATRIX**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:278
#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:426
msgid "in mat4 **PROJECTION_MATRIX**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:282
msgid "Node position, in world space."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:284
msgid "Node position, in view space."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:286
msgid "Camera position, in world space."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:288
msgid "Camera direction, in world space."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:290
msgid "in vec3 **VERTEX**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:290
msgid "Vertex that comes from vertex function (default, in view space)."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:302
#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:184
msgid "sampler2D **SCREEN_TEXTURE**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:302
#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:184
msgid ""
"Removed in Godot 4. Use a ``sampler2D`` with ``hint_screen_texture`` instead."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:304
#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:182
#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:249
#: ../../docs/tutorials/shaders/shader_reference/sky_shader.rst:198
msgid "in vec2 **SCREEN_UV**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:304
#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:182
#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:249
msgid "Screen UV coordinate for current pixel."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:306
msgid "sampler2D **DEPTH_TEXTURE**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:306
msgid ""
"Removed in Godot 4. Use a ``sampler2D`` with ``hint_depth_texture`` instead."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:308
msgid "out float **DEPTH**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:308
msgid ""
"Custom depth value (0..1). If ``DEPTH`` is being written to in any shader "
"branch, then you are responsible for setting the ``DEPTH`` for **all** other "
"branches. Otherwise, the graphics API will leave them uninitialized."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:312
msgid "Normal that comes from vertex function (default, in view space)."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:314
msgid "Tangent that comes from vertex function."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:316
msgid "Binormal that comes from vertex function."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:318
#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:191
msgid "out vec3 **NORMAL_MAP**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:318
msgid "Set normal here if reading normal from a texture instead of NORMAL."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:320
#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:194
msgid "out float **NORMAL_MAP_DEPTH**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:320
msgid "Depth from variable above. Defaults to 1.0."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:322
#: ../../docs/tutorials/shaders/shader_reference/fog_shader.rst:72
msgid "out vec3 **ALBEDO**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:322
msgid "Albedo (default white)."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:324
#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:469
#: ../../docs/tutorials/shaders/shader_reference/sky_shader.rst:208
msgid "out float **ALPHA**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:324
#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:469
msgid ""
"Alpha (0..1); if written to, the material will go to the transparent "
"pipeline."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:326
msgid "out float **ALPHA_SCISSOR_THRESHOLD**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:326
msgid "If written to, values below a certain amount of alpha are discarded."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:328
msgid "out float **ALPHA_HASH_SCALE**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:330
msgid "out float **ALPHA_ANTIALIASING_EDGE**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:332
msgid "out vec2 **ALPHA_TEXTURE_COORDINATE**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:334
msgid "out float **METALLIC**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:334
msgid "Metallic (0..1)."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:336
msgid "out float **SPECULAR**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:336
msgid ""
"Specular. Defaults to 0.5, best not to modify unless you want to change IOR."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:338
msgid "Roughness (0..1)."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:340
msgid "out float **RIM**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:340
msgid "Rim (0..1). If used, Godot calculates rim lighting."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:342
msgid "out float **RIM_TINT**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:342
msgid ""
"Rim Tint, goes from 0 (white) to 1 (albedo). If used, Godot calculates rim "
"lighting."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:344
msgid "out float **CLEARCOAT**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:344
msgid "Small added specular blob. If used, Godot calculates Clearcoat."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:346
msgid "out float **CLEARCOAT_GLOSS**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:346
msgid "Gloss of Clearcoat. If used, Godot calculates Clearcoat."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:348
msgid "out float **ANISOTROPY**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:348
msgid "For distorting the specular blob according to tangent space."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:350
msgid "out vec2 **ANISOTROPY_FLOW**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:350
msgid "Distortion direction, use with flowmaps."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:352
msgid "out float **SSS_STRENGTH**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:352
msgid ""
"Strength of Subsurface Scattering. If used, Subsurface Scattering will be "
"applied to object."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:354
msgid "out vec4 **SSS_TRANSMITTANCE_COLOR**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:356
msgid "out float **SSS_TRANSMITTANCE_DEPTH**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:358
msgid "out float **SSS_TRANSMITTANCE_BOOST**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:360
msgid "inout vec3 **BACKLIGHT**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:362
msgid "out float **AO**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:362
msgid "Strength of Ambient Occlusion. For use with pre-baked AO."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:364
msgid "out float **AO_LIGHT_AFFECT**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:364
msgid "How much AO affects lights (0..1; default 0)."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:366
#: ../../docs/tutorials/shaders/shader_reference/fog_shader.rst:78
msgid "out vec3 **EMISSION**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:366
msgid "Emission color (can go over 1,1,1 for HDR)."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:368
#: ../../docs/tutorials/shaders/shader_reference/sky_shader.rst:210
msgid "out vec4 **FOG**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:368
msgid "If written to, blends final pixel color with FOG.rgb based on FOG.a."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:370
msgid "out vec4 **RADIANCE**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:370
msgid ""
"If written to, blends environment map radiance with RADIANCE.rgb based on "
"RADIANCE.a."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:372
msgid "out vec4 **IRRADIANCE**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:372
msgid ""
"If written to, blends environment map IRRADIANCE with IRRADIANCE.rgb based "
"on IRRADIANCE.a."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:377
#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:475
msgid ""
"Shaders going through the transparent pipeline when ``ALPHA`` is written to "
"may exhibit transparency sorting issues. Read the :ref:`transparency sorting "
"section in the 3D rendering limitations page "
"<doc_3d_rendering_limitations_transparency_sorting>` for more information "
"and ways to avoid issues."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:383
#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:208
msgid "Light built-ins"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:385
msgid ""
"Writing light processor functions is completely optional. You can skip the "
"light function by setting render_mode to ``unshaded``. If no light function "
"is written, Godot will use the material properties written to in the "
"fragment function to calculate the lighting for you (subject to the "
"render_mode)."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:390
msgid ""
"The light function is called for every light in every pixel. It is called "
"within a loop for each light type."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:393
msgid ""
"Below is an example of a custom light function using a Lambertian lighting "
"model:"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:401
msgid ""
"If you want the lights to add together, add the light contribution to "
"``DIFFUSE_LIGHT`` using ``+=``, rather than overwriting it."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:405
msgid ""
"The ``light()`` function won't be run if the ``vertex_lighting`` render mode "
"is enabled, or if **Rendering > Quality > Shading > Force Vertex Shading** "
"is enabled in the Project Settings. (It's enabled by default on mobile "
"platforms.)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:430
#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:237
msgid "in vec3 **NORMAL**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:430
msgid "Normal vector, in view space."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:436
msgid "View vector, in view space."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:438
msgid "in vec3 **LIGHT**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:438
msgid "Light Vector, in view space."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:440
msgid "in vec3 **LIGHT_COLOR**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:440
msgid ""
"Color of light multiplied by ``energy * PI``. The ``PI`` multiplication is "
"present because physically-based lighting models include a division by "
"``PI``."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:445
msgid "in float **SPECULAR_AMOUNT**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:445
msgid ""
"2.0 * ``light_specular`` property for ``OmniLight3D`` and ``SpotLight3D``. "
"1.0 for ``DirectionalLight3D``."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:449
#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:262
msgid "in bool **LIGHT_IS_DIRECTIONAL**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:449
msgid "``true`` if this pass is a ``DirectionalLight3D``."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:451
msgid "in float **ATTENUATION**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:451
msgid "Attenuation based on distance or shadow."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:453
msgid "in vec3 **ALBEDO**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:453
msgid "Base albedo."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:455
msgid "in vec3 **BACKLIGHT**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:457
msgid "in float **METALLIC**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:457
msgid "Metallic."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:459
msgid "in float **ROUGHNESS**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:459
msgid "Roughness."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:465
msgid "out vec3 **DIFFUSE_LIGHT**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:465
msgid "Diffuse light result."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:467
msgid "out vec3 **SPECULAR_LIGHT**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:467
msgid "Specular light result."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/spatial_shader.rst:480
msgid ""
"Transparent materials also cannot cast shadows or appear in "
"``hint_screen_texture`` and ``hint_depth_texture`` uniforms. This in turn "
"prevents those materials from appearing in screen-space reflections or "
"refraction. :ref:`SDFGI <doc_using_sdfgi>` sharp reflections are not visible "
"on transparent materials (only rough reflections are visible on transparent "
"materials)."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:4
msgid "CanvasItem shaders"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:6
msgid ""
"CanvasItem shaders are used to draw all 2D elements in Godot. These include "
"all nodes that inherit from CanvasItems, and all GUI elements."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:9
msgid ""
"CanvasItem shaders contain less built-in variables and functionality than "
"Spatial shaders, but they maintain the same basic structure with vertex, "
"fragment, and light processor functions."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:27
msgid "**blend_premul_alpha**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:27
msgid "Pre-multiplied alpha blend mode."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:29
msgid "**blend_disabled**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:29
msgid "Disable blending, values (including alpha) are written as-is."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:33
msgid "**light_only**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:33
msgid "Only draw on light pass."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:35
msgid "VERTEX needs to be transformed manually in vertex function."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:37
msgid "VERTEX is modified in world coordinates instead of local."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:56
msgid ""
"Global time since the engine has started, in seconds (always positive). It's "
"subject to the rollover setting (which is 3,600 seconds by default). It's "
"not affected by :ref:`time_scale<class_Engine_property_time_scale>` or "
"pausing, but you can define a global shader uniform to add a \"scaled\" "
"``TIME`` variable if desired."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:75
msgid ""
"Vertex data (``VERTEX``) is presented in local space (pixel coordinates, "
"relative to the Node2D's origin). If not written to, these values will not "
"be modified and be passed through as they came."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:78
msgid ""
"The user can disable the built-in model to world transform (world to screen "
"and projection will still happen later) and do it manually with the "
"following code:"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:91
msgid ""
"Other built-ins, such as UV and COLOR, are also passed through to the "
"fragment function if not modified."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:103
msgid ""
"Local space to world space transform. World space is the coordinates you "
"normally use in the editor."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:106
msgid "in mat4 **CANVAS_MATRIX**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:106
msgid ""
"World space to canvas space transform. In canvas space the origin is the "
"upper-left corner of the screen and coordinates ranging from (0, 0) to "
"viewport size."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:111
msgid "in mat4 **SCREEN_MATRIX**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:111
msgid ""
"Canvas space to clip space. In clip space coordinates ranging from (-1, -1) "
"to (1, 1)."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:114
msgid "in int  **INSTANCE_ID**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:116
msgid "Instance custom data."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:118
#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:174
msgid "in bool **AT_LIGHT_PASS**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:118
#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:174
msgid "Always ``false``."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:120
#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:170
#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:245
msgid "in vec2 **TEXTURE_PIXEL_SIZE**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:120
#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:170
msgid ""
"Normalized pixel size of default 2D texture. For a Sprite2D with a texture "
"of size 64x32px, **TEXTURE_PIXEL_SIZE** = ``vec2(1/64, 1/32)``"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:124
#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:196
msgid "inout vec2 **VERTEX**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:124
msgid "Vertex, in local space."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:129
msgid "Normalized texture coordinates. Range from 0 to 1."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:131
msgid "Color from vertex primitive."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:133
msgid "Point size for point drawing."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:139
msgid ""
"Certain Nodes (for example, :ref:`Sprite2Ds <class_Sprite2D>`) display a "
"texture by default. However, when a custom fragment function is attached to "
"these nodes, the texture lookup needs to be done manually. Godot provides "
"the texture color in the ``COLOR`` built-in variable multiplied by the "
"node's color. To read the texture color by itself, you can use:"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:149
msgid ""
"Similarly, if a normal map is used in the :ref:`CanvasTexture "
"<class_CanvasTexture>`, Godot uses it by default and assigns its value to "
"the built-in ``NORMAL`` variable. If you are using a normal map meant for "
"use in 3D, it will appear inverted. In order to use it in your shader, you "
"must assign it to the ``NORMALMAP`` property. Godot will handle converting "
"it for use in 2D and overwriting ``NORMAL``."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:161
#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:234
msgid ""
"Coordinate of pixel center. In screen space. ``xy`` specifies position in "
"window. Origin is lower-left."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:164
msgid "in vec2 **SCREEN_PIXEL_SIZE**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:164
msgid "Size of individual pixels. Equal to inverse of resolution."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:166
msgid "Coordinate for drawing points."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:168
#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:243
msgid "sampler2D **TEXTURE**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:168
msgid "Default 2D texture."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:176
msgid "sampler2D **SPECULAR_SHININESS_TEXTURE**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:176
msgid "Specular shininess texture of this object."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:178
#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:268
msgid "in vec4 **SPECULAR_SHININESS**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:178
msgid "Specular shininess color, as sampled from the texture."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:180
msgid "UV from vertex function."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:187
msgid "Normal read from **NORMAL_TEXTURE**. Writable."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:189
msgid "sampler2D **NORMAL_TEXTURE**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:189
msgid "Default 2D normal texture."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:191
msgid ""
"Configures normal maps meant for 3D for use in 2D. If used, overrides "
"**NORMAL**."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:194
msgid "Normalmap depth for scaling."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:196
msgid "Pixel position in screen space."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:198
msgid "inout vec2 **SHADOW_VERTEX**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:198
msgid "Same as ``VERTEX`` but can be written to alter shadows."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:200
msgid "inout vec3 **LIGHT_VERTEX**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:200
msgid ""
"Same as ``VERTEX`` but can be written to alter lighting. Z component "
"represents height."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:203
msgid ""
"Color from vertex function multiplied by the **TEXTURE** color. Also output "
"color value."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:210
msgid ""
"Light processor functions work differently in Godot 4.x than they did in "
"Godot 3.x. In Godot 4.x all lighting is done during the regular draw pass. "
"In other words, Godot no longer draws the object again for each light."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:214
msgid ""
"Use render_mode ``unshaded`` if you do not want the light processor function "
"to run. Use render_mode ``light_only`` if you only want to see the impact of "
"lighting on an object; this can be useful when you only want the object "
"visible where it is covered by light."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:219
msgid ""
"If you define a light function it will replace the built in light function, "
"even if your light function is empty."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:222
msgid ""
"Below is an example of a light shader that takes a CanvasItem's normal map "
"into account:"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:237
msgid "Input Normal."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:239
msgid "Input Color. This is the output of the fragment function."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:241
msgid "UV from vertex function, equivalent to the UV in the fragment function."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:243
msgid "Current texture in use for CanvasItem."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:245
msgid ""
"Normalized pixel size of **TEXTURE**. For a Sprite2D with a **TEXTURE** of "
"size 64x32px, **TEXTURE_PIXEL_SIZE** = ``vec2(1/64, 1/32)``"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:251
msgid "UV for Point Sprite."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:253
msgid "in vec4 **LIGHT_COLOR**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:253
msgid "Color of Light multiplied by Light's texture."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:255
msgid "in float **LIGHT_ENERGY**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:255
msgid "Energy multiplier of Light."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:257
msgid "in vec3 **LIGHT_POSITION**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:257
msgid ""
"Position of Light in screen space. If using a ``DirectionalLight2D`` this is "
"always ``vec3(0,0,0)``."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:260
msgid "in vec3 **LIGHT_DIRECTION**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:260
msgid "Direction of Light in screen space."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:262
msgid "``true`` if this pass is a ``DirectionalLight2D``."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:264
msgid "in vec3 **LIGHT_VERTEX**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:264
msgid "Pixel position, in screen space as modified in the fragment function."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:266
msgid "inout vec4 **LIGHT**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:266
msgid "Output color for this Light."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:268
msgid "Specular shininess, as set in the object's texture."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:270
msgid "out vec4 **SHADOW_MODULATE**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:270
msgid "Multiply shadows cast at this point by this color."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:274
#, fuzzy
msgid "SDF functions"
msgstr "Funkcije"

#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:276
msgid ""
"There are a few additional functions implemented to sample an automatically "
"generated Signed Distance Field texture. These functions available for "
"Fragment and Light functions of CanvasItem shaders."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:280
msgid ""
"The signed distance field is generated from :ref:`class_LightOccluder2D` "
"nodes present in the scene with the **SDF Collision** property enabled "
"(which is the default). See the :ref:`2D lights and shadows "
"<doc_2d_lights_and_shadows_setting_up_shadows>` documentation for more "
"information."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:288
msgid "float **texture_sdf** (vec2 sdf_pos)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:288
msgid "Performs an SDF texture lookup."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:290
msgid "vec2 **texture_sdf_normal** (vec2 sdf_pos)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:290
msgid "Calculates a normal from the SDF texture."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:292
msgid "vec2 **sdf_to_screen_uv** (vec2 sdf_pos)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:292
msgid "Converts a SDF to screen UV."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:294
msgid "vec2 **screen_uv_to_sdf** (vec2 uv)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/canvas_item_shader.rst:294
msgid "Converts screen UV to a SDF."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/particle_shader.rst:4
msgid "Particle shaders"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/particle_shader.rst:6
msgid ""
"Particle shaders are a special type of shader that runs before the object is "
"drawn. They are used for calculating material properties such as color, "
"position, and rotation. They are drawn with any regular material for "
"CanvasItem or Spatial, depending on whether they are 2D or 3D."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/particle_shader.rst:11
msgid ""
"Particle shaders are unique because they are not used to draw the object "
"itself; they are used to calculate particle properties, which are then used "
"by a CanvasItem or Spatial shader. They contain two processor functions: "
"``start()`` and ``process()``."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/particle_shader.rst:16
msgid ""
"Unlike other shader types, particle shaders keep the data that was output "
"the previous frame. Therefore, particle shaders can be used for complex "
"effects that take place over multiple frames."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/particle_shader.rst:22
msgid ""
"Particle shaders are only available with GPU-based particle nodes (:ref:"
"`class_GPUParticles2D` and :ref:`class_GPUParticles3D`)."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/particle_shader.rst:25
msgid ""
"CPU-based particle nodes (:ref:`class_CPUParticles2D` and :ref:"
"`class_CPUParticles3D`) are *rendered* on the GPU (which means they can use "
"custom CanvasItem or Spatial shaders), but their motion is *simulated* on "
"the CPU."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/particle_shader.rst:36
msgid "**keep_data**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/particle_shader.rst:36
msgid "Do not clear previous data on restart."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/particle_shader.rst:38
msgid "**disable_force**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/particle_shader.rst:38
msgid "Disable attractor force."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/particle_shader.rst:40
msgid "**disable_velocity**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/particle_shader.rst:40
msgid "Ignore **VELOCITY** value."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/particle_shader.rst:42
msgid "**collision_use_scale**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/particle_shader.rst:42
msgid "Scale the particle's size for collisions."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/particle_shader.rst:73
msgid "Start and Process built-ins"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/particle_shader.rst:75
msgid ""
"These properties can be accessed from both the ``start()`` and ``process()`` "
"functions."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/particle_shader.rst:80
msgid "in float **LIFETIME**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/particle_shader.rst:80
msgid "Particle lifetime."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/particle_shader.rst:82
msgid "in float **DELTA**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/particle_shader.rst:82
msgid "Delta process time."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/particle_shader.rst:84
msgid "in uint **NUMBER**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/particle_shader.rst:84
msgid "Unique number since emission start."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/particle_shader.rst:86
msgid "in uint **INDEX**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/particle_shader.rst:86
msgid "Particle index (from total particles)."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/particle_shader.rst:88
msgid "in mat4 **EMISSION_TRANSFORM**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/particle_shader.rst:88
msgid "Emitter transform (used for non-local systems)."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/particle_shader.rst:90
msgid "in uint **RANDOM_SEED**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/particle_shader.rst:90
msgid "Random seed used as base for random."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/particle_shader.rst:92
msgid "inout bool **ACTIVE**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/particle_shader.rst:92
msgid "``true`` when the particle is active, can be set ``false``."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/particle_shader.rst:94
msgid ""
"Particle color, can be written to and accessed in mesh's vertex function."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/particle_shader.rst:96
msgid "inout vec3 **VELOCITY**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/particle_shader.rst:96
msgid "Particle velocity, can be modified."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/particle_shader.rst:98
msgid "inout mat4 **TRANSFORM**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/particle_shader.rst:98
msgid "Particle transform."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/particle_shader.rst:100
msgid "inout vec4 **CUSTOM**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/particle_shader.rst:100
msgid ""
"Custom particle data. Accessible from shader of mesh as **INSTANCE_CUSTOM**."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/particle_shader.rst:102
msgid "inout float **MASS**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/particle_shader.rst:102
msgid ""
"Particle mass, intended to be used with attractors. Equals ``1.0`` by "
"default."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/particle_shader.rst:104
msgid "in vec4 **USERDATAX**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/particle_shader.rst:104
msgid ""
"Vector that enables the integration of supplementary user-defined data into "
"the particle process shader. ``USERDATAX`` are six built-ins identified by "
"number, ``X`` can be numbers between 1 and 6."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/particle_shader.rst:107
msgid "in uint **FLAG_EMIT_POSITION**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/particle_shader.rst:107
msgid ""
"A flag for using on the last argument of ``emit_subparticle`` function to "
"assign a position to a new particle's transform."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/particle_shader.rst:109
msgid "in uint **FLAG_EMIT_ROT_SCALE**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/particle_shader.rst:109
msgid ""
"A flag for using on the last argument of ``emit_subparticle`` function to "
"assign the rotation and scale to a new particle's transform."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/particle_shader.rst:111
msgid "in uint **FLAG_EMIT_VELOCITY**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/particle_shader.rst:111
msgid ""
"A flag for using on the last argument of ``emit_subparticle`` function to "
"assign a velocity to a new particle."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/particle_shader.rst:113
msgid "in uint **FLAG_EMIT_COLOR**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/particle_shader.rst:113
msgid ""
"A flag for using on the last argument of ``emit_subparticle`` function to "
"assign a color to a new particle."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/particle_shader.rst:115
msgid "in uint **FLAG_EMIT_CUSTOM**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/particle_shader.rst:115
msgid ""
"A flag for using on the last argument of ``emit_subparticle`` function to "
"assign a custom data vector to a new particle."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/particle_shader.rst:117
msgid "in vec3 **EMITTER_VELOCITY**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/particle_shader.rst:117
msgid "Velocity of the Particles node."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/particle_shader.rst:119
msgid "in float **INTERPOLATE_TO_END**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/particle_shader.rst:119
msgid "Value of ``interp_to_end`` property of Particles node."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/particle_shader.rst:121
msgid "in uint **AMOUNT_RATIO**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/particle_shader.rst:121
msgid "Value of ``amount_ratio`` property of Particles node."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/particle_shader.rst:124
msgid ""
"In order to use the ``COLOR`` variable in a StandardMaterial3D, set "
"``vertex_color_use_as_albedo`` to ``true``. In a ShaderMaterial, access it "
"with the ``COLOR`` variable."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/particle_shader.rst:128
msgid "Start built-ins"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/particle_shader.rst:133
msgid "in bool **RESTART_POSITION**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/particle_shader.rst:133
msgid ""
"``true`` if particle is restarted, or emitted without a custom position (i."
"e. this particle was created by ``emit_subparticle()`` without the "
"``FLAG_EMIT_POSITION`` flag)."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/particle_shader.rst:135
msgid "in bool **RESTART_ROT_SCALE**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/particle_shader.rst:135
msgid ""
"``true`` if particle is restarted, or emitted without a custom rotation or "
"scale (i.e. this particle was created by ``emit_subparticle()`` without the "
"``FLAG_EMIT_ROT_SCALE`` flag)."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/particle_shader.rst:137
msgid "in bool **RESTART_VELOCITY**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/particle_shader.rst:137
msgid ""
"``true`` if particle is restarted, or emitted without a custom velocity (i."
"e. this particle was created by ``emit_subparticle()`` without the "
"``FLAG_EMIT_VELOCITY`` flag)."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/particle_shader.rst:139
msgid "in bool **RESTART_COLOR**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/particle_shader.rst:139
msgid ""
"``true`` if particle is restarted, or emitted without a custom color (i.e. "
"this particle was created by ``emit_subparticle()`` without the "
"``FLAG_EMIT_COLOR`` flag)."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/particle_shader.rst:141
msgid "in bool **RESTART_CUSTOM**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/particle_shader.rst:141
msgid ""
"``true`` if particle is restarted, or emitted without a custom property (i."
"e. this particle was created by ``emit_subparticle()`` without the "
"``FLAG_EMIT_CUSTOM`` flag)."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/particle_shader.rst:145
msgid "Process built-ins"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/particle_shader.rst:150
msgid "in bool **RESTART**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/particle_shader.rst:150
msgid "``true`` if the current process frame is first for the particle."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/particle_shader.rst:152
msgid "in bool **COLLIDED**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/particle_shader.rst:152
msgid "``true`` when the particle has collided with a particle collider."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/particle_shader.rst:154
msgid "in vec3 **COLLISION_NORMAL**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/particle_shader.rst:154
msgid ""
"A normal of the last collision. If there is no collision detected it is "
"equal to ``vec3(0.0)``."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/particle_shader.rst:156
msgid "in float **COLLISION_DEPTH**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/particle_shader.rst:156
msgid ""
"A length of normal of the last collision. If there is no collision detected "
"it is equal to ``0.0``."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/particle_shader.rst:158
msgid "in vec3 **ATTRACTOR_FORCE**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/particle_shader.rst:158
msgid "A combined force of the attractors at the moment on that particle."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/particle_shader.rst:162
#, fuzzy
msgid "Process functions"
msgstr "Uvod"

#: ../../docs/tutorials/shaders/shader_reference/particle_shader.rst:164
msgid ""
"``emit_subparticle`` is currently the only custom function supported by "
"particles shaders. It allows users to add a new particle with specified "
"parameters from a sub-emitter. The newly created particle will only use the "
"properties that match the ``flags`` parameter. For example, the following "
"code will emit a particle with a specified position, velocity, and color, "
"but unspecified rotation, scale, and custom value:"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/particle_shader.rst:180
msgid ""
"bool **emit_subparticle** (mat4 xform, vec3 velocity, vec4 color, vec4 "
"custom, uint flags)"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/particle_shader.rst:180
msgid "Emits a particle from a sub-emitter."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/sky_shader.rst:4
#, fuzzy
msgid "Sky shaders"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/shaders/shader_reference/sky_shader.rst:6
msgid ""
"Sky shaders are a special type of shader used for drawing sky backgrounds "
"and for updating radiance cubemaps which are used for image-based lighting "
"(IBL). Sky shaders only have one processing function, the ``sky()`` function."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/sky_shader.rst:11
msgid "There are three places the sky shader is used."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/sky_shader.rst:13
msgid ""
"First the sky shader is used to draw the sky when you have selected to use a "
"Sky as the background in your scene."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/sky_shader.rst:15
msgid ""
"Second, the sky shader is used to update the radiance cubemap when using the "
"Sky for ambient color or reflections."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/sky_shader.rst:17
msgid ""
"Third, the sky shader is used to draw the lower res subpasses which can be "
"used in the high-res background or cubemap pass."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/sky_shader.rst:20
msgid ""
"In total, this means the sky shader can run up to six times per frame, "
"however, in practice it will be much less than that because the radiance "
"cubemap does not need to be updated every frame, and not all subpasses will "
"be used. You can change the behavior of the shader based on where it is "
"called by checking the ``AT_*_PASS`` booleans. For example:"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/sky_shader.rst:43
msgid ""
"When using the sky shader to draw a background, the shader will be called "
"for all non-occluded fragments on the screen. However, for the background's "
"subpasses, the shader will be called for every pixel of the subpass."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/sky_shader.rst:47
msgid ""
"When using the sky shader to update the radiance cubemap, the sky shader "
"will be called for every pixel in the cubemap. On the other hand, the shader "
"will only be called when the radiance cubemap needs to be updated. The "
"radiance cubemap needs to be updated when any of the shader parameters are "
"updated. For example, if ``TIME`` is used in the shader, then the radiance "
"cubemap will update every frame. The following list of changes force an "
"update of the radiance cubemap:"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/sky_shader.rst:55
msgid "``TIME`` is used."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/sky_shader.rst:56
msgid "``POSITION`` is used and the camera position changes."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/sky_shader.rst:57
msgid ""
"If any ``LIGHTX_*`` properties are used and any :ref:`DirectionalLight3D "
"<class_DirectionalLight3D>` changes."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/sky_shader.rst:59
msgid "If any uniform is changed in the shader."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/sky_shader.rst:60
msgid "If the screen is resized and either of the subpasses are used."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/sky_shader.rst:62
msgid ""
"Try to avoid updating the radiance cubemap needlessly. If you do need to "
"update the radiance cubemap each frame, make sure your :ref:`Sky process "
"mode <class_Sky_property_process_mode>` is set to :ref:`REALTIME "
"<class_Sky_constant_PROCESS_MODE_REALTIME>`."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/sky_shader.rst:67
msgid ""
"Note that the :ref:`process mode <class_Sky_property_process_mode>` only "
"affects the rendering of the radiance cubemap. The visible sky is always "
"rendered by calling the fragment shader for every pixel. With complex "
"fragment shaders, this can result in a high rendering overhead. If the sky "
"is static (the conditions listed above are met) or changes slowly, running "
"the full fragment shader every frame is not needed. This can be avoided by "
"rendering the full sky into the radiance cubemap, and reading from this "
"cubemap when rendering the visible sky. With a completely static sky, this "
"means that it needs to be rendered only once."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/sky_shader.rst:77
msgid ""
"The following code renders the full sky into the radiance cubemap and reads "
"from that cubemap for displaying the visible sky:"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/sky_shader.rst:99
msgid ""
"This way, the complex calculations happen only in the cubemap pass, which "
"can be optimized by setting the sky's :ref:`process mode "
"<class_Sky_property_process_mode>` and the :ref:`radiance size "
"<class_Sky_property_radiance_size>` to get the desired balance between "
"performance and visual fidelity."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/sky_shader.rst:107
msgid ""
"Subpasses allow you to do more expensive calculations at a lower resolution "
"to speed up your shaders. For example the following code renders clouds at a "
"lower resolution than the rest of the sky:"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/sky_shader.rst:132
msgid "**use_half_res_pass**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/sky_shader.rst:132
msgid "Allows the shader to write to and access the half resolution pass."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/sky_shader.rst:134
msgid "**use_quarter_res_pass**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/sky_shader.rst:134
msgid "Allows the shader to write to and access the quarter resolution pass."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/sky_shader.rst:136
msgid "**disable_fog**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/sky_shader.rst:136
msgid "If used, fog will not affect the sky."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/sky_shader.rst:142
#: ../../docs/tutorials/shaders/shader_reference/fog_shader.rst:24
msgid ""
"Values marked as \"in\" are read-only. Values marked as \"out\" are for "
"optional writing and will not necessarily contain sensible values. Samplers "
"cannot be written to so they are not marked."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/sky_shader.rst:149
#: ../../docs/tutorials/shaders/shader_reference/fog_shader.rst:32
msgid ""
"Global built-ins are available everywhere, including in custom functions."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/sky_shader.rst:151
msgid ""
"There are 4 ``LIGHTX`` lights, accessed as ``LIGHT0``, ``LIGHT1``, "
"``LIGHT2``, and ``LIGHT3``."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/sky_shader.rst:159
msgid "in vec3 **POSITION**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/sky_shader.rst:159
msgid "Camera position in world space"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/sky_shader.rst:161
msgid "samplerCube **RADIANCE**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/sky_shader.rst:161
msgid ""
"Radiance cubemap. Can only be read from during background pass. Check ``!"
"AT_CUBEMAP_PASS`` before using."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/sky_shader.rst:163
msgid "in bool **AT_HALF_RES_PASS**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/sky_shader.rst:163
msgid "Currently rendering to half resolution pass."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/sky_shader.rst:165
msgid "in bool **AT_QUARTER_RES_PASS**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/sky_shader.rst:165
msgid "Currently rendering to quarter resolution pass."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/sky_shader.rst:167
msgid "in bool **AT_CUBEMAP_PASS**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/sky_shader.rst:167
msgid "Currently rendering to radiance cubemap."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/sky_shader.rst:169
msgid "in bool **LIGHTX_ENABLED**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/sky_shader.rst:169
msgid ""
"``LightX`` is visible and in the scene. If ``false``, other light properties "
"may be garbage."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/sky_shader.rst:171
msgid "in float **LIGHTX_ENERGY**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/sky_shader.rst:171
msgid "Energy multiplier for ``LIGHTX``."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/sky_shader.rst:173
msgid "in vec3 **LIGHTX_DIRECTION**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/sky_shader.rst:173
msgid "Direction that ``LIGHTX`` is facing."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/sky_shader.rst:175
msgid "in vec3 **LIGHTX_COLOR**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/sky_shader.rst:175
msgid "Color of ``LIGHTX``."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/sky_shader.rst:177
msgid "in float **LIGHTX_SIZE**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/sky_shader.rst:177
msgid ""
"Angular diameter of ``LIGHTX`` in the sky. Expressed in radians. For "
"reference, the sun from earth is about .0087 radians (0.5 degrees)."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/sky_shader.rst:180
#: ../../docs/tutorials/shaders/shader_reference/fog_shader.rst:40
msgid ""
"A ``PI`` constant (``3.141592``). A ratio of a circle's circumference to its "
"diameter and amount of radians in half turn."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/sky_shader.rst:191
msgid "Sky built-ins"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/sky_shader.rst:196
msgid "in vec3 **EYEDIR**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/sky_shader.rst:196
msgid ""
"Normalized direction of current pixel. Use this as your basic direction for "
"procedural effects."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/sky_shader.rst:198
msgid ""
"Screen UV coordinate for current pixel. Used to map a texture to the full "
"screen."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/sky_shader.rst:200
msgid "in vec2 **SKY_COORDS**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/sky_shader.rst:200
msgid "Sphere UV. Used to map a panorama texture to the sky."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/sky_shader.rst:202
msgid "in vec4 **HALF_RES_COLOR**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/sky_shader.rst:202
msgid ""
"Color value of corresponding pixel from half resolution pass. Uses linear "
"filter."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/sky_shader.rst:204
msgid "in vec4 **QUARTER_RES_COLOR**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/sky_shader.rst:204
msgid ""
"Color value of corresponding pixel from quarter resolution pass. Uses linear "
"filter."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/sky_shader.rst:206
msgid "out vec3 **COLOR**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/sky_shader.rst:206
msgid "Output color."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/sky_shader.rst:208
msgid "Output alpha value, can only be used in subpasses."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/fog_shader.rst:4
#, fuzzy
msgid "Fog shaders"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/shaders/shader_reference/fog_shader.rst:6
msgid ""
"Fog shaders are used to define how fog is added (or subtracted) from a scene "
"in a given area. Fog shaders are always used together with :ref:`FogVolumes "
"<class_FogVolume>` and volumetric fog. Fog shaders only have one processing "
"function, the ``fog()`` function."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/fog_shader.rst:11
msgid ""
"The resolution of the fog shaders depends on the resolution of the "
"volumetric fog froxel grid. Accordingly, the level of detail that a fog "
"shader can add depends on how close the :ref:`FogVolume <class_FogVolume>` "
"is to the camera."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/fog_shader.rst:16
msgid ""
"Fog shaders are a special form of compute shader that is called once for "
"every froxel that is touched by an axis aligned bounding box of the "
"associated :ref:`FogVolume <class_FogVolume>`. This means that froxels that "
"just barely touch a given :ref:`FogVolume <class_FogVolume>` will still be "
"used."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/fog_shader.rst:51
msgid "Fog built-ins"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/fog_shader.rst:53
msgid ""
"All of the output values of fog volumes overlap one another. This allows :"
"ref:`FogVolumes <class_FogVolume>` to be rendered efficiently as they can "
"all be drawn at once."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/fog_shader.rst:60
msgid "in vec3 **WORLD_POSITION**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/fog_shader.rst:60
msgid "Position of current froxel cell in world space."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/fog_shader.rst:62
msgid "in vec3 **OBJECT_POSITION**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/fog_shader.rst:62
msgid ""
"Position of the center of the current :ref:`FogVolume <class_FogVolume>` in "
"world space."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/fog_shader.rst:64
msgid "in vec3 **UVW**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/fog_shader.rst:64
msgid ""
"3-dimensional uv, used to map a 3D texture to the current :ref:`FogVolume "
"<class_FogVolume>`."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/fog_shader.rst:66
msgid "in vec3 **SIZE**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/fog_shader.rst:66
msgid ""
"Size of the current :ref:`FogVolume <class_FogVolume>` when its :ref:"
"`shape<class_FogVolume_property_shape>` has a size."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/fog_shader.rst:69
msgid "in vec3 **SDF**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/fog_shader.rst:69
msgid ""
"Signed distance field to the surface of the :ref:`FogVolume "
"<class_FogVolume>`. Negative if inside volume, positive otherwise."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/fog_shader.rst:72
msgid ""
"Output base color value, interacts with light to produce final color. Only "
"written to fog volume if used."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/fog_shader.rst:75
msgid "out float **DENSITY**"
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/fog_shader.rst:75
msgid ""
"Output density value. Can be negative to allow subtracting one volume from "
"another. Density must be used for fog shader to write anything at all."
msgstr ""

#: ../../docs/tutorials/shaders/shader_reference/fog_shader.rst:78
msgid ""
"Output emission color value, added to color during light pass to produce "
"final color. Only written to fog volume if used."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/index.rst:2
msgid "Your first shader"
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/index.rst:4
msgid ""
"This tutorial series will walk you through writing your first shader. It is "
"intended for people who have very little prior experience with shaders and "
"want to get started with the basics. This tutorial will not cover advanced "
"topics and it is not comprehensive. For a comprehensive and detailed "
"overview of shaders in Godot see the :ref:`Shading Reference Page <toc-"
"shading-reference>`."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/index.rst:10
msgid ""
"The \"your first shader\" tutorials walk you through the process of writing "
"a shader step-by-step."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/index.rst:13
msgid ""
"For a more general introduction into shaders and the OpenGL Shading "
"Language, use `The Book of Shaders <https://thebookofshaders.com>`_."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_first_2d_shader.rst:4
msgid "Your first 2D shader"
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_first_2d_shader.rst:9
msgid ""
"Shaders are special programs that execute on the GPU and are used for "
"rendering graphics. All modern rendering is done with shaders. For a more "
"detailed description of what shaders are please see :ref:`What are shaders "
"<doc_introduction_to_shaders>`."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_first_2d_shader.rst:14
msgid ""
"This tutorial will focus on the practical aspects of writing shader programs "
"by walking you through the process of writing a shader with both vertex and "
"fragment functions. This tutorial targets absolute beginners to shaders."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_first_2d_shader.rst:18
msgid ""
"If you have experience writing shaders and are just looking for an overview "
"of how shaders work in Godot, see the :ref:`Shading Reference <toc-shading-"
"reference>`."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_first_2d_shader.rst:25
msgid ""
":ref:`CanvasItem shaders <doc_canvas_item_shader>` are used to draw all 2D "
"objects in Godot, while :ref:`Spatial <doc_spatial_shader>` shaders are used "
"to draw all 3D objects."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_first_2d_shader.rst:29
msgid ""
"In order to use a shader it must be attached inside a :ref:`Material "
"<class_Material>` which must be attached to an object. Materials are a type "
"of :ref:`Resource <doc_resources>`. To draw multiple objects with the same "
"material, the material must be attached to each object."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_first_2d_shader.rst:34
msgid ""
"All objects derived from a :ref:`CanvasItem <class_CanvasItem>` have a "
"material property. This includes all :ref:`GUI elements <class_Control>`, :"
"ref:`Sprite2Ds <class_Sprite2D>`, :ref:`TileMaps <class_Tilemap>`, :ref:"
"`MeshInstance2Ds <class_MeshInstance2D>` etc. They also have an option to "
"inherit their parent's material. This can be useful if you have a large "
"number of nodes that you want to use the same material."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_first_2d_shader.rst:41
msgid ""
"To begin, create a Sprite2D node. :ref:`You can use any CanvasItem "
"<doc_custom_drawing_in_2d>`, so long as it is drawing to the canvas, so for "
"this tutorial we will use a Sprite2D, as it is the easiest CanvasItem to "
"start drawing with."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_first_2d_shader.rst:45
msgid ""
"In the Inspector, click beside \"Texture\" where it says \"[empty]\" and "
"select \"Load\", then select \"icon.svg\". For new projects, this is the "
"Godot icon. You should now see the icon in the viewport."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_first_2d_shader.rst:49
msgid ""
"Next, look down in the Inspector, under the CanvasItem section, click beside "
"\"Material\" and select \"New ShaderMaterial\". This creates a new Material "
"resource. Click on the sphere that appears. Godot currently doesn't know "
"whether you are writing a CanvasItem Shader or a Spatial Shader and it "
"previews the output of spatial shaders. So what you are seeing is the output "
"of the default Spatial Shader."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_first_2d_shader.rst:56
msgid ""
"Click beside \"Shader\" and select \"New Shader\". Finally, click on the "
"shader you just created and the shader editor will open. You are now ready "
"to begin writing your first shader."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_first_2d_shader.rst:61
msgid "Your first CanvasItem shader"
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_first_2d_shader.rst:63
msgid ""
"In Godot, all shaders start with a line specifying what type of shader they "
"are. It uses the following format:"
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_first_2d_shader.rst:70
msgid ""
"Because we are writing a CanvasItem shader, we specify ``canvas_item`` in "
"the first line. All our code will go beneath this declaration."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_first_2d_shader.rst:73
msgid ""
"This line tells the engine which built-in variables and functionality to "
"supply you with."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_first_2d_shader.rst:76
msgid ""
"In Godot you can override three functions to control how the shader "
"operates; ``vertex``, ``fragment``, and ``light``. This tutorial will walk "
"you through writing a shader with both vertex and fragment functions. Light "
"functions are significantly more complex than vertex and fragment functions "
"and so will not be covered here."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_first_2d_shader.rst:83
msgid "Your first fragment function"
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_first_2d_shader.rst:85
msgid ""
"The fragment function runs for every pixel in a Sprite2D and determines what "
"color that pixel should be."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_first_2d_shader.rst:88
msgid ""
"They are restricted to the pixels covered by the Sprite2D, that means you "
"cannot use one to, for example, create an outline around a Sprite2D."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_first_2d_shader.rst:91
msgid ""
"The most basic fragment function does nothing except assign a single color "
"to every pixel."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_first_2d_shader.rst:94
msgid ""
"We do so by writing a ``vec4`` to the built-in variable ``COLOR``. ``vec4`` "
"is shorthand for constructing a vector with 4 numbers. For more information "
"about vectors see the :ref:`Vector math tutorial <doc_vector_math>`. "
"``COLOR`` is both an input variable to the fragment function and the final "
"output from it."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_first_2d_shader.rst:107
msgid ""
"Congratulations! You're done. You have successfully written your first "
"shader in Godot."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_first_2d_shader.rst:110
msgid "Now let's make things more complex."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_first_2d_shader.rst:112
msgid ""
"There are many inputs to the fragment function that you can use for "
"calculating ``COLOR``. ``UV`` is one of them. UV coordinates are specified "
"in your Sprite2D (without you knowing it!) and they tell the shader where to "
"read from textures for each part of the mesh."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_first_2d_shader.rst:117
msgid ""
"In the fragment function you can only read from ``UV``, but you can use it "
"in other functions or to assign values to ``COLOR`` directly."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_first_2d_shader.rst:120
msgid "``UV`` varies between 0-1 from left-right and from top-bottom."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_first_2d_shader.rst:133
msgid "Using ``TEXTURE`` built-in"
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_first_2d_shader.rst:135
msgid ""
"The default fragment function reads from the set Sprite2D texture and "
"displays it."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_first_2d_shader.rst:137
msgid ""
"When you want to adjust a color in a Sprite2D you can adjust the color from "
"the texture manually like in the code below."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_first_2d_shader.rst:147
msgid ""
"Certain nodes, like Sprite2Ds, have a dedicated texture variable that can be "
"accessed in the shader using ``TEXTURE``. If you want to use the Sprite2D "
"texture to combine with other colors, you can use the ``UV`` with the "
"``texture`` function to access this variable. Use them to redraw the "
"Sprite2D with the texture."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_first_2d_shader.rst:162
msgid "Uniform input"
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_first_2d_shader.rst:164
msgid ""
"Uniform input is used to pass data into a shader that will be the same "
"across the entire shader."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_first_2d_shader.rst:167
msgid ""
"You can use uniforms by defining them at the top of your shader like so:"
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_first_2d_shader.rst:173
msgid ""
"For more information about usage see the :ref:`Shading Language doc "
"<doc_shading_language>`."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_first_2d_shader.rst:176
msgid "Add a uniform to change the amount of blue in our Sprite2D."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_first_2d_shader.rst:187
msgid ""
"Now you can change the amount of blue in the Sprite2D from the editor. Look "
"back at the Inspector under where you created your shader. You should see a "
"section called \"Shader Param\". Unfold that section and you will see the "
"uniform you just declared. If you change the value in the editor, it will "
"overwrite the default value you provided in the shader."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_first_2d_shader.rst:194
msgid "Interacting with shaders from code"
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_first_2d_shader.rst:196
msgid ""
"You can change uniforms from code using the function "
"``set_shader_parameter()`` which is called on the node's material resource. "
"With a Sprite2D node, the following code can be used to set the ``blue`` "
"uniform."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_first_2d_shader.rst:205
msgid ""
"Note that the name of the uniform is a string. The string must match exactly "
"with how it is written in the shader, including spelling and case."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_first_2d_shader.rst:209
msgid "Your first vertex function"
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_first_2d_shader.rst:211
msgid "Now that we have a fragment function, let's write a vertex function."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_first_2d_shader.rst:213
msgid ""
"Use the vertex function to calculate where on the screen each vertex should "
"end up."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_first_2d_shader.rst:216
msgid ""
"The most important variable in the vertex function is ``VERTEX``. Initially, "
"it specifies the vertex coordinates in your model, but you also write to it "
"to determine where to actually draw those vertices. ``VERTEX`` is a ``vec2`` "
"that is initially presented in local-space (i.e. not relative to the camera, "
"viewport, or parent nodes)."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_first_2d_shader.rst:222
msgid "You can offset the vertices by directly adding to ``VERTEX``."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_first_2d_shader.rst:230
msgid ""
"Combined with the ``TIME`` built-in variable, this can be used for basic "
"animation."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_first_2d_shader.rst:243
msgid ""
"At their core, shaders do what you have seen so far, they compute ``VERTEX`` "
"and ``COLOR``. It is up to you to dream up more complex mathematical "
"strategies for assigning values to those variables."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_first_2d_shader.rst:247
msgid ""
"For inspiration, take a look at some of the more advanced shader tutorials, "
"and look at other sites like `Shadertoy <https://www.shadertoy.com/results?"
"query=&sort=popular&from=10&num=4>`_ and `The Book of Shaders <https://"
"thebookofshaders.com>`_."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_first_3d_shader.rst:4
msgid "Your first 3D shader"
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_first_3d_shader.rst:6
msgid ""
"You have decided to start writing your own custom Spatial shader. Maybe you "
"saw a cool trick online that was done with shaders, or you have found that "
"the :ref:`StandardMaterial3D <class_StandardMaterial3D>` isn't quite meeting "
"your needs. Either way, you have decided to write your own and now you need "
"to figure out where to start."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_first_3d_shader.rst:12
msgid ""
"This tutorial will explain how to write a Spatial shader and will cover more "
"topics than the :ref:`CanvasItem <doc_your_first_canvasitem_shader>` "
"tutorial."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_first_3d_shader.rst:15
msgid ""
"Spatial shaders have more built-in functionality than CanvasItem shaders. "
"The expectation with spatial shaders is that Godot has already provided the "
"functionality for common use cases and all the user needs to do in the "
"shader is set the proper parameters. This is especially true for a PBR "
"(physically based rendering) workflow."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_first_3d_shader.rst:21
msgid ""
"This is a two-part tutorial. In this first part we will create terrain using "
"vertex displacement from a heightmap in the vertex function. In the :ref:"
"`second part <doc_your_second_spatial_shader>` we will take the concepts "
"from this tutorial and set up custom materials in a fragment shader by "
"writing an ocean water shader."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_first_3d_shader.rst:27
msgid ""
"This tutorial assumes some basic shader knowledge such as types (``vec2``, "
"``float``, ``sampler2D``), and functions. If you are uncomfortable with "
"these concepts it is best to get a gentle introduction from `The Book of "
"Shaders <https://thebookofshaders.com>`_ before completing this tutorial."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_first_3d_shader.rst:34
msgid "Where to assign my material"
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_first_3d_shader.rst:36
msgid ""
"In 3D, objects are drawn using :ref:`Meshes <class_Mesh>`. Meshes are a "
"resource type that store geometry (the shape of your object) and materials "
"(the color and how the object reacts to light) in units called \"surfaces\". "
"A Mesh can have multiple surfaces, or just one. Typically, you would import "
"a mesh from another program (e.g. Blender). But Godot also has a few :ref:"
"`PrimitiveMeshes <class_primitivemesh>` that allow you to add basic geometry "
"to a scene without importing Meshes."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_first_3d_shader.rst:44
msgid ""
"There are multiple node types that you can use to draw a mesh. The main one "
"is :ref:`MeshInstance3D <class_MeshInstance3D>`, but you can also use :ref:"
"`GPUParticles3D <class_GPUParticles3D>`, :ref:`MultiMeshes "
"<class_MultiMesh>` (with a :ref:`MultiMeshInstance3D "
"<class_MultiMeshInstance3D>`), or others."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_first_3d_shader.rst:49
msgid ""
"Typically, a material is associated with a given surface in a mesh, but some "
"nodes, like MeshInstance3D, allow you to override the material for a "
"specific surface, or for all surfaces."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_first_3d_shader.rst:53
msgid ""
"If you set a material on the surface or mesh itself, then all "
"MeshInstance3Ds that share that mesh will share that material. However, if "
"you want to reuse the same mesh across multiple mesh instances, but have "
"different materials for each instance then you should set the material on "
"the MeshInstance3D."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_first_3d_shader.rst:58
msgid ""
"For this tutorial we will set our material on the mesh itself rather than "
"taking advantage of the MeshInstance3D's ability to override materials."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_first_3d_shader.rst:64
msgid ""
"Add a new :ref:`MeshInstance3D <class_MeshInstance3D>` node to your scene."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_first_3d_shader.rst:66
msgid ""
"In the inspector tab beside \"Mesh\" click \"[empty]\" and select \"New "
"PlaneMesh\". Then click on the image of a plane that appears."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_first_3d_shader.rst:69
msgid "This adds a :ref:`PlaneMesh <class_planemesh>` to our scene."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_first_3d_shader.rst:71
msgid ""
"Then, in the viewport, click in the upper left corner on the button that "
"says \"Perspective\". A menu will appear. In the middle of the menu are "
"options for how to display the scene. Select 'Display Wireframe'."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_first_3d_shader.rst:75
msgid "This will allow you to see the triangles making up the plane."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_first_3d_shader.rst:79
msgid ""
"Now set ``Subdivide Width`` and ``Subdivide Depth`` of the :ref:`PlaneMesh "
"<class_planemesh>` to ``32``."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_first_3d_shader.rst:83
msgid ""
"You can see that there are now many more triangles in the :ref:"
"`MeshInstance3D<class_MeshInstance3D>`. This will give us more vertices to "
"work with and thus allow us to add more detail."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_first_3d_shader.rst:89
msgid ""
":ref:`PrimitiveMeshes <class_primitivemesh>`, like PlaneMesh, only have one "
"surface, so instead of an array of materials there is only one. Click beside "
"\"Material\" where it says \"[empty]\" and select \"New ShaderMaterial\". "
"Then click the sphere that appears."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_first_3d_shader.rst:94
msgid ""
"Now click beside \"Shader\" where it says \"[empty]\" and select \"New "
"Shader\"."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_first_3d_shader.rst:96
msgid ""
"The shader editor should now pop up and you are ready to begin writing your "
"first Spatial shader!"
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_first_3d_shader.rst:100
msgid "Shader magic"
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_first_3d_shader.rst:104
msgid ""
"The new shader is already generated with a ``shader_type`` variable and the "
"``fragment()`` function. The first thing Godot shaders need is a declaration "
"of what type of shader they are. In this case the ``shader_type`` is set to "
"``spatial`` because this is a spatial shader."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_first_3d_shader.rst:115
msgid ""
"For now ignore the ``fragment()`` function and define the ``vertex()`` "
"function. The ``vertex()`` function determines where the vertices of your :"
"ref:`MeshInstance3D<class_MeshInstance3D>` appear in the final scene. We "
"will be using it to offset the height of each vertex and make our flat plane "
"appear like a little terrain."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_first_3d_shader.rst:121
msgid "We define the vertex shader like so:"
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_first_3d_shader.rst:129
msgid ""
"With nothing in the ``vertex()`` function, Godot will use its default vertex "
"shader. We can easily start to make changes by adding a single line:"
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_first_3d_shader.rst:138
msgid "Adding this line, you should get an image like the one below."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_first_3d_shader.rst:142
msgid ""
"Okay, let's unpack this. The ``y`` value of the ``VERTEX`` is being "
"increased. And we are passing the ``x`` and ``z`` components of the "
"``VERTEX`` as arguments to ``cos`` and ``sin``; that gives us a wave-like "
"appearance across the ``x`` and ``z`` axes."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_first_3d_shader.rst:147
msgid ""
"What we want to achieve is the look of little hills; after all. ``cos`` and "
"``sin`` already look kind of like hills. We do so by scaling the inputs to "
"the ``cos`` and ``sin`` functions."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_first_3d_shader.rst:159
msgid ""
"This looks better, but it is still too spiky and repetitive, let's make it a "
"little more interesting."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_first_3d_shader.rst:163
msgid "Noise heightmap"
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_first_3d_shader.rst:165
msgid ""
"Noise is a very popular tool for faking the look of terrain. Think of it as "
"similar to the cosine function where you have repeating hills except, with "
"noise, each hill has a different height."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_first_3d_shader.rst:169
msgid ""
"Godot provides the :ref:`NoiseTexture2D <class_noisetexture2D>` resource for "
"generating a noise texture that can be accessed from a shader."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_first_3d_shader.rst:172
msgid ""
"To access a texture in a shader add the following code near the top of your "
"shader, outside the ``vertex()`` function."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_first_3d_shader.rst:179
msgid ""
"This will allow you to send a noise texture to the shader. Now look in the "
"inspector under your material. You should see a section called \"Shader "
"Params\". If you open it up, you'll see a section called \"noise\"."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_first_3d_shader.rst:183
msgid ""
"Click beside it where it says \"[empty]\" and select \"New NoiseTexture2D\". "
"Then in your :ref:`NoiseTexture2D <class_noisetexture2D>` click beside where "
"it says \"Noise\" and select \"New FastNoiseLite\"."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_first_3d_shader.rst:187
msgid ""
":ref:`FastNoiseLite <class_fastnoiselite>` is used by the NoiseTexture2D to "
"generate a heightmap."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_first_3d_shader.rst:190
msgid "Once you set it up and should look like this."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_first_3d_shader.rst:194
msgid ""
"Now, access the noise texture using the ``texture()`` function. "
"``texture()`` takes a texture as the first argument and a ``vec2`` for the "
"position on the texture as the second argument. We use the ``x`` and ``z`` "
"channels of ``VERTEX`` to determine where on the texture to look up. Note "
"that the PlaneMesh coordinates are within the [-1,1] range (for a size of "
"2), while the texture coordinates are within [0,1], so to normalize we "
"divide by the size of the PlaneMesh by 2.0 and add 0.5. ``texture()`` "
"returns a ``vec4`` of the ``r, g, b, a`` channels at the position. Since the "
"noise texture is grayscale, all of the values are the same, so we can use "
"any one of the channels as the height. In this case we'll use the ``r``, or "
"``x`` channel."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_first_3d_shader.rst:212
msgid ""
"Note: ``xyzw`` is the same as ``rgba`` in GLSL, so instead of ``texture()."
"x`` above, we could use ``texture().r``. See the `OpenGL documentation "
"<https://www.khronos.org/opengl/wiki/Data_Type_(GLSL)#Vectors>`_ for more "
"details."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_first_3d_shader.rst:217
msgid "Using this code you can see the texture creates random looking hills."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_first_3d_shader.rst:221
msgid ""
"Right now it is too spiky, we want to soften the hills a bit. To do that, we "
"will use a uniform. You already used a uniform above to pass in the noise "
"texture, now let's learn how they work."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_first_3d_shader.rst:228
msgid ""
"Uniform variables allow you to pass data from the game into the shader. They "
"are very useful for controlling shader effects. Uniforms can be almost any "
"datatype that can be used in the shader. To use a uniform, you declare it in "
"your :ref:`Shader<class_Shader>` using the keyword ``uniform``."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_first_3d_shader.rst:233
msgid "Let's make a uniform that changes the height of the terrain."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_first_3d_shader.rst:240
msgid ""
"Godot lets you initialize a uniform with a value; here, ``height_scale`` is "
"set to ``0.5``. You can set uniforms from GDScript by calling the function "
"``set_shader_parameter()`` on the material corresponding to the shader. The "
"value passed from GDScript takes precedence over the value used to "
"initialize it in the shader."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_first_3d_shader.rst:251
msgid ""
"Changing uniforms in Spatial-based nodes is different from CanvasItem-based "
"nodes. Here, we set the material inside the PlaneMesh resource. In other "
"mesh resources you may need to first access the material by calling "
"``surface_get_material()``. While in the MeshInstance3D you would access the "
"material using ``get_surface_material()`` or ``material_override``."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_first_3d_shader.rst:258
msgid ""
"Remember that the string passed into ``set_shader_parameter()`` must match "
"the name of the uniform variable in the :ref:`Shader<class_Shader>`. You can "
"use the uniform variable anywhere inside your :ref:`Shader<class_Shader>`. "
"Here, we will use it to set the height value instead of arbitrarily "
"multiplying by ``0.5``."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_first_3d_shader.rst:267
#: ../../docs/tutorials/shaders/your_first_shader/your_second_3d_shader.rst:313
msgid "Now it looks much better."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_first_3d_shader.rst:271
msgid ""
"Using uniforms, we can even change the value every frame to animate the "
"height of the terrain. Combined with :ref:`Tweens <class_Tween>`, this can "
"be especially useful for animations."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_first_3d_shader.rst:276
msgid "Interacting with light"
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_first_3d_shader.rst:278
msgid ""
"First, turn wireframe off. To do so, click in the upper-left of the Viewport "
"again, where it says \"Perspective\", and select \"Display Normal\"."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_first_3d_shader.rst:283
msgid ""
"Note how the mesh color goes flat. This is because the lighting on it is "
"flat. Let's add a light!"
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_first_3d_shader.rst:286
msgid ""
"First, we will add an :ref:`OmniLight3D<class_OmniLight3D>` to the scene."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_first_3d_shader.rst:290
msgid ""
"You can see the light affecting the terrain, but it looks odd. The problem "
"is the light is affecting the terrain as if it were a flat plane. This is "
"because the light shader uses the normals from the :ref:`Mesh <class_mesh>` "
"to calculate light."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_first_3d_shader.rst:295
msgid ""
"The normals are stored in the Mesh, but we are changing the shape of the "
"Mesh in the shader, so the normals are no longer correct. To fix this, we "
"can recalculate the normals in the shader or use a normal texture that "
"corresponds to our noise. Godot makes both easy for us."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_first_3d_shader.rst:300
msgid ""
"You can calculate the new normal manually in the vertex function and then "
"just set ``NORMAL``. With ``NORMAL`` set, Godot will do all the difficult "
"lighting calculations for us. We will cover this method in the next part of "
"this tutorial, for now we will read normals from a texture."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_first_3d_shader.rst:305
msgid ""
"Instead we will rely on the NoiseTexture again to calculate normals for us. "
"We do that by passing in a second noise texture."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_first_3d_shader.rst:312
msgid ""
"Set this second uniform texture to another :ref:`NoiseTexture2D "
"<class_noisetexture2D>` with another :ref:`FastNoiseLite "
"<class_fastnoiselite>`. But this time, check **As Normalmap**."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_first_3d_shader.rst:317
msgid ""
"Now, because this is a normalmap and not a per-vertex normal, we are going "
"to assign it in the ``fragment()`` function. The ``fragment()`` function "
"will be explained in more detail in the next part of this tutorial."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_first_3d_shader.rst:326
msgid ""
"When we have normals that correspond to a specific vertex we set ``NORMAL``, "
"but if you have a normalmap that comes from a texture, set the normal using "
"``NORMAL_MAP``. This way Godot will handle the wrapping of texture around "
"the mesh automatically."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_first_3d_shader.rst:331
msgid ""
"Lastly, in order to ensure that we are reading from the same places on the "
"noise texture and the normalmap texture, we are going to pass the ``VERTEX."
"xz`` position from the ``vertex()`` function to the ``fragment()`` function. "
"We do that with varyings."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_first_3d_shader.rst:336
msgid ""
"Above the ``vertex()`` define a ``vec2`` called ``tex_position``. And inside "
"the ``vertex()`` function assign ``VERTEX.xz`` to ``tex_position``."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_first_3d_shader.rst:350
msgid ""
"And now we can access ``tex_position`` from the ``fragment()`` function."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_first_3d_shader.rst:358
msgid ""
"With the normals in place the light now reacts to the height of the mesh "
"dynamically."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_first_3d_shader.rst:363
msgid ""
"We can even drag the light around and the lighting will update automatically."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_first_3d_shader.rst:367
msgid ""
"Here is the full code for this tutorial. You can see it is not very long as "
"Godot handles most of the difficult stuff for you."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_first_3d_shader.rst:390
msgid ""
"That is everything for this part. Hopefully, you now understand the basics "
"of vertex shaders in Godot. In the next part of this tutorial we will write "
"a fragment function to accompany this vertex function and we will cover a "
"more advanced technique to turn this terrain into an ocean of moving waves."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_second_3d_shader.rst:4
msgid "Your second 3D shader"
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_second_3d_shader.rst:6
msgid ""
"From a high-level, what Godot does is give the user a bunch of parameters "
"that can be optionally set (``AO``, ``SSS_Strength``, ``RIM``, etc.). These "
"parameters correspond to different complex effects (Ambient Occlusion, "
"SubSurface Scattering, Rim Lighting, etc.). When not written to, the code is "
"thrown out before it is compiled and so the shader does not incur the cost "
"of the extra feature. This makes it easy for users to have complex PBR-"
"correct shading, without writing complex shaders. Of course, Godot also "
"allows you to ignore all these parameters and write a fully customized "
"shader."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_second_3d_shader.rst:15
msgid ""
"For a full list of these parameters see the :ref:`spatial shader "
"<doc_spatial_shader>` reference doc."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_second_3d_shader.rst:18
msgid ""
"A difference between the vertex function and a fragment function is that the "
"vertex function runs per vertex and sets properties such as ``VERTEX`` "
"(position) and ``NORMAL``, while the fragment shader runs per pixel and, "
"most importantly, sets the ``ALBEDO`` color of the :ref:"
"`MeshInstance3D<class_MeshInstance3D>`."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_second_3d_shader.rst:24
msgid "Your first spatial fragment function"
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_second_3d_shader.rst:26
msgid ""
"As mentioned in the previous part of this tutorial. The standard use of the "
"fragment function in Godot is to set up different material properties and "
"let Godot handle the rest. In order to provide even more flexibility, Godot "
"also provides things called render modes. Render modes are set at the top of "
"the shader, directly below ``shader_type``, and they specify what sort of "
"functionality you want the built-in aspects of the shader to have."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_second_3d_shader.rst:33
msgid ""
"For example, if you do not want to have lights affect an object, set the "
"render mode to ``unshaded``:"
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_second_3d_shader.rst:40
msgid ""
"You can also stack multiple render modes together. For example, if you want "
"to use toon shading instead of more-realistic PBR shading, set the diffuse "
"mode and specular mode to toon:"
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_second_3d_shader.rst:48
msgid ""
"This model of built-in functionality allows you to write complex custom "
"shaders by changing only a few parameters."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_second_3d_shader.rst:51
msgid ""
"For a full list of render modes see the :ref:`Spatial shader reference "
"<doc_spatial_shader>`."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_second_3d_shader.rst:54
msgid ""
"In this part of the tutorial, we will walk through how to take the bumpy "
"terrain from the previous part and turn it into an ocean."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_second_3d_shader.rst:57
msgid ""
"First let's set the color of the water. We do that by setting ``ALBEDO``."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_second_3d_shader.rst:59
msgid "``ALBEDO`` is a ``vec3`` that contains the color of the object."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_second_3d_shader.rst:61
msgid "Let's set it to a nice shade of blue."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_second_3d_shader.rst:71
msgid ""
"We set it to a very dark shade of blue because most of the blueness of the "
"water will come from reflections from the sky."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_second_3d_shader.rst:74
msgid ""
"The PBR model that Godot uses relies on two main parameters: ``METALLIC`` "
"and ``ROUGHNESS``."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_second_3d_shader.rst:77
msgid ""
"``ROUGHNESS`` specifies how smooth/rough the surface of a material is. A low "
"``ROUGHNESS`` will make a material appear like a shiny plastic, while a high "
"roughness makes the material appear more solid in color."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_second_3d_shader.rst:81
msgid ""
"``METALLIC`` specifies how much like a metal the object is. It is better set "
"close to ``0`` or ``1``. Think of ``METALLIC`` as changing the balance "
"between the reflection and the ``ALBEDO`` color. A high ``METALLIC`` almost "
"ignores ``ALBEDO`` altogether, and looks like a mirror of the sky. While a "
"low ``METALLIC`` has a more equal representation of sky color and ``ALBEDO`` "
"color."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_second_3d_shader.rst:87
msgid ""
"``ROUGHNESS`` increases from ``0`` to ``1`` from left to right while "
"``METALLIC`` increase from ``0`` to ``1`` from top to bottom."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_second_3d_shader.rst:92
msgid ""
"``METALLIC`` should be close to ``0`` or ``1`` for proper PBR shading. Only "
"set it between them for blending between materials."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_second_3d_shader.rst:95
msgid ""
"Water is not a metal, so we will set its ``METALLIC`` property to ``0.0``. "
"Water is also highly reflective, so we will set its ``ROUGHNESS`` property "
"to be quite low as well."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_second_3d_shader.rst:109
msgid ""
"Now we have a smooth plastic looking surface. It is time to think about some "
"particular properties of water that we want to emulate. There are two main "
"ones that will take this from a weird plastic surface to nice stylized "
"water. The first is specular reflections. Specular reflections are those "
"bright spots you see from where the sun reflects directly into your eye. The "
"second is fresnel reflectance. Fresnel reflectance is the property of "
"objects to become more reflective at shallow angles. It is the reason why "
"you can see into water below you, but farther away it reflects the sky."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_second_3d_shader.rst:118
msgid ""
"In order to increase the specular reflections, we will do two things. First, "
"we will change the render mode for specular to toon because the toon render "
"mode has larger specular highlights."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_second_3d_shader.rst:128
msgid ""
"Second we will add rim lighting. Rim lighting increases the effect of light "
"at glancing angles. Usually it is used to emulate the way light passes "
"through fabric on the edges of an object, but we will use it here to help "
"achieve a nice watery effect."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_second_3d_shader.rst:144
msgid ""
"In order to add fresnel reflectance, we will compute a fresnel term in our "
"fragment shader. Here, we aren't going to use a real fresnel term for "
"performance reasons. Instead, we'll approximate it using the dot product of "
"the ``NORMAL`` and ``VIEW`` vectors. The ``NORMAL`` vector points away from "
"the mesh's surface, while the ``VIEW`` vector is the direction between your "
"eye and that point on the surface. The dot product between them is a handy "
"way to tell when you are looking at the surface head-on or at a glancing "
"angle."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_second_3d_shader.rst:156
msgid ""
"And mix it into both ``ROUGHNESS`` and ``ALBEDO``. This is the benefit of "
"ShaderMaterials over StandardMaterial3Ds. With StandardMaterial3D, we could "
"set these properties with a texture, or to a flat number. But with shaders "
"we can set them based on any mathematical function that we can dream up."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_second_3d_shader.rst:174
msgid ""
"And now, with only 5 lines of code, you can have complex looking water. Now "
"that we have lighting, this water is looking too bright. Let's darken it. "
"This is done easily by decreasing the values of the ``vec3`` we pass into "
"``ALBEDO``. Let's set them to ``vec3(0.01, 0.03, 0.05)``."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_second_3d_shader.rst:182
msgid "Animating with ``TIME``"
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_second_3d_shader.rst:184
msgid ""
"Going back to the vertex function, we can animate the waves using the built-"
"in variable ``TIME``."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_second_3d_shader.rst:187
msgid ""
"``TIME`` is a built-in variable that is accessible from the vertex and "
"fragment functions."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_second_3d_shader.rst:191
msgid ""
"In the last tutorial we calculated height by reading from a heightmap. For "
"this tutorial, we will do the same. Put the heightmap code in a function "
"called ``height()``."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_second_3d_shader.rst:201
msgid ""
"In order to use ``TIME`` in the ``height()`` function, we need to pass it in."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_second_3d_shader.rst:208
msgid "And make sure to correctly pass it in inside the vertex function."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_second_3d_shader.rst:218
msgid ""
"Instead of using a normalmap to calculate normals. We are going to compute "
"them manually in the ``vertex()`` function. To do so use the following line "
"of code."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_second_3d_shader.rst:225
msgid ""
"We need to compute ``NORMAL`` manually because in the next section we will "
"be using math to create complex-looking waves."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_second_3d_shader.rst:228
msgid ""
"Now, we are going to make the ``height()`` function a little more "
"complicated by offsetting ``position`` by the cosine of ``TIME``."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_second_3d_shader.rst:238
msgid ""
"This results in waves that move slowly, but not in a very natural way. The "
"next section will dig deeper into using shaders to create more complex "
"effects, in this case realistic waves, by adding a few more mathematical "
"functions."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_second_3d_shader.rst:243
msgid "Advanced effects: waves"
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_second_3d_shader.rst:245
msgid ""
"What makes shaders so powerful is that you can achieve complex effects by "
"using math. To illustrate this, we are going to take our waves to the next "
"level by modifying the ``height()`` function and by introducing a new "
"function called ``wave()``."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_second_3d_shader.rst:250
msgid ""
"``wave()`` has one parameter, ``position``, which is the same as it is in "
"``height()``."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_second_3d_shader.rst:253
msgid ""
"We are going to call ``wave()`` multiple times in ``height()`` in order to "
"fake the way waves look."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_second_3d_shader.rst:264
msgid "At first this looks complicated. So let's go through it line-by-line."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_second_3d_shader.rst:270
msgid ""
"Offset the position by the ``noise`` texture. This will make the waves "
"curve, so they won't be straight lines completely aligned with the grid."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_second_3d_shader.rst:277
msgid ""
"Define a wave-like function using ``sin()`` and ``position``. Normally "
"``sin()`` waves are very round. We use ``abs()`` to absolute to give them a "
"sharp ridge and constrain them to the 0-1 range. And then we subtract it "
"from ``1.0`` to put the peak on top."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_second_3d_shader.rst:286
msgid ""
"Multiply the x-directional wave by the y-directional wave and raise it to a "
"power to sharpen the peaks. Then subtract that from ``1.0`` so that the "
"ridges become peaks and raise that to a power to sharpen the ridges."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_second_3d_shader.rst:290
msgid ""
"We can now replace the contents of our ``height()`` function with ``wave()``."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_second_3d_shader.rst:299
msgid "Using this, you get:"
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_second_3d_shader.rst:303
msgid ""
"The shape of the sin wave is too obvious. So let's spread the waves out a "
"bit. We do this by scaling ``position``."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_second_3d_shader.rst:317
msgid ""
"We can do even better if we layer multiple waves on top of each other at "
"varying frequencies and amplitudes. What this means is that we are going to "
"scale position for each one to make the waves thinner or wider (frequency). "
"And we are going to multiply the output of the wave to make them shorter or "
"taller (amplitude)."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_second_3d_shader.rst:323
msgid ""
"Here is an example for how you could layer the four waves to achieve nicer "
"looking waves."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_second_3d_shader.rst:336
msgid ""
"Note that we add time to two and subtract it from the other two. This makes "
"the waves move in different directions creating a complex effect. Also note "
"that the amplitudes (the number the result is multiplied by) all add up to "
"``1.0``. This keeps the wave in the 0-1 range."
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_second_3d_shader.rst:341
msgid ""
"With this code you should end up with more complex looking waves and all you "
"had to do was add a bit of math!"
msgstr ""

#: ../../docs/tutorials/shaders/your_first_shader/your_second_3d_shader.rst:346
msgid ""
"For more information about Spatial shaders read the :ref:`Shading Language "
"<doc_shading_language>` doc and the :ref:`Spatial Shaders "
"<doc_spatial_shader>` doc. Also look at more advanced tutorials in the :ref:"
"`Shading section <toc-learn-features-shading>` and the :ref:`3D <toc-learn-"
"features-3d>` sections."
msgstr ""

#: ../../docs/tutorials/shaders/shader_materials.rst:4
msgid "Shader materials"
msgstr ""

#: ../../docs/tutorials/shaders/shader_materials.rst:9
msgid ""
"For the most common cases, Godot provides ready to use materials for most "
"types of shaders, such as :ref:`StandardMaterial3D "
"<class_StandardMaterial3D>`, :ref:`CanvasItemMaterial "
"<class_CanvasItemMaterial>` and :ref:`ParticleProcessMaterial "
"<class_ParticleProcessMaterial>`. They are flexible implementations that "
"cover most use cases."
msgstr ""

#: ../../docs/tutorials/shaders/shader_materials.rst:14
msgid ""
"Shader materials allow writing a custom shader directly, for maximum "
"flexibility. Examples of this are:"
msgstr ""

#: ../../docs/tutorials/shaders/shader_materials.rst:17
msgid "Create procedural textures."
msgstr ""

#: ../../docs/tutorials/shaders/shader_materials.rst:18
msgid "Create complex texture blending effects."
msgstr ""

#: ../../docs/tutorials/shaders/shader_materials.rst:19
msgid "Create animated materials, or materials that change over time."
msgstr ""

#: ../../docs/tutorials/shaders/shader_materials.rst:20
msgid "Create refractive effects or other advanced effects."
msgstr ""

#: ../../docs/tutorials/shaders/shader_materials.rst:21
msgid "Create special lighting shaders for more exotic materials."
msgstr ""

#: ../../docs/tutorials/shaders/shader_materials.rst:22
msgid "Animate vertices, like tree leaves or grass."
msgstr ""

#: ../../docs/tutorials/shaders/shader_materials.rst:23
msgid "Create custom particle code."
msgstr ""

#: ../../docs/tutorials/shaders/shader_materials.rst:26
msgid ""
"Godot provides built in functionality to make frequent operations easier. "
"Additionally, Godot's shader editor will detect errors as you type, so you "
"can see your edited shaders in real-time. It is also possible to edit "
"shaders using a visual, node-based graph editor."
msgstr ""

#: ../../docs/tutorials/shaders/shader_materials.rst:32
msgid "Creating a ShaderMaterial"
msgstr ""

#: ../../docs/tutorials/shaders/shader_materials.rst:34
msgid ""
"Create a new ShaderMaterial in some object of your choice. Go to the "
"\"Material\" property and create a ShaderMaterial."
msgstr ""

#: ../../docs/tutorials/shaders/shader_materials.rst:39
msgid ""
"Next, click on the shader material to see its properties. From here you can "
"create a shader or visual shader. Regular shaders use code to set their "
"properties while a visual shader uses a node based workflow."
msgstr ""

#: ../../docs/tutorials/shaders/shader_materials.rst:43
msgid ""
"If you need to you can convert a visual shader to a text shader. However you "
"can't convert a text shader to a visual shader."
msgstr ""

#: ../../docs/tutorials/shaders/shader_materials.rst:46
msgid "Choose one of them and you can start editing your shader."
msgstr ""

#: ../../docs/tutorials/shaders/shader_materials.rst:50
msgid ""
"If you create a regular shader click on it and the shader editor will open."
msgstr ""

#: ../../docs/tutorials/shaders/shader_materials.rst:54
msgid ""
"If you create a visual shader the visual shader editor will open "
"automatically."
msgstr ""

#: ../../docs/tutorials/shaders/shader_materials.rst:58
msgid ""
"In the visual shader editor you can click a button and see what your visual "
"shader looks like as shader code. This can be useful if you're trying to "
"replicate a text shader as nodes, or it can be used as a preview for "
"converting your visual shader to a text shader."
msgstr ""

#: ../../docs/tutorials/shaders/shader_materials.rst:67
msgid "To learn more about visual shaders, read :ref:`doc_visual_shaders`."
msgstr ""

#: ../../docs/tutorials/shaders/shader_materials.rst:70
msgid "Converting to ShaderMaterial"
msgstr ""

#: ../../docs/tutorials/shaders/shader_materials.rst:72
msgid ""
"It is possible to convert from StandardMaterial3D, CanvasItemMaterial and "
"ParticleProcessMaterial to ShaderMaterial. To do so, go to the material "
"properties and select the convert option."
msgstr ""

#: ../../docs/tutorials/shaders/shader_materials.rst:80
msgid ""
"Using the convert option will turn the StandardMaterial3D into a "
"ShaderMaterial with a text shader, not a visual shader."
msgstr ""

#: ../../docs/tutorials/shaders/visual_shaders.rst:4
#, fuzzy
msgid "Using VisualShaders"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/shaders/visual_shaders.rst:6
msgid "VisualShaders are the visual alternative for creating shaders."
msgstr ""

#: ../../docs/tutorials/shaders/visual_shaders.rst:8
msgid ""
"As shaders are inherently linked to visuals, the graph-based approach with "
"previews of textures, materials, etc. offers a lot of additional convenience "
"compared to purely script-based shaders. On the other hand, VisualShaders do "
"not expose all features of the shader script and using both in parallel "
"might be necessary for specific effects."
msgstr ""

#: ../../docs/tutorials/shaders/visual_shaders.rst:16
msgid ""
"If you are not familiar with shaders, start by reading :ref:"
"`doc_introduction_to_shaders`."
msgstr ""

#: ../../docs/tutorials/shaders/visual_shaders.rst:20
#, fuzzy
msgid "Creating a VisualShader"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/shaders/visual_shaders.rst:22
msgid ""
"VisualShaders can be created in any :ref:`class_ShaderMaterial`. To begin "
"using VisualShaders, create a new ``ShaderMaterial`` in an object of your "
"choice."
msgstr ""

#: ../../docs/tutorials/shaders/visual_shaders.rst:27
msgid ""
"Then assign a :ref:`class_VisualShader` resource to the ``Shader`` property."
msgstr ""

#: ../../docs/tutorials/shaders/visual_shaders.rst:31
msgid ""
"Click on the new ``Shader`` resource and the Create Shader dialog will open "
"automatically. Change the Type option to VisualShader in the dropdown."
msgstr ""

#: ../../docs/tutorials/shaders/visual_shaders.rst:36
msgid ""
"The layout of the Visual Shader Editor comprises two parts: the upper "
"toolbar and the graph itself."
msgstr ""

#: ../../docs/tutorials/shaders/visual_shaders.rst:41
msgid "From left to right in the toolbar:"
msgstr ""

#: ../../docs/tutorials/shaders/visual_shaders.rst:43
msgid ""
"The ``Add Node`` button displays a popup menu to let you add nodes to the "
"shader graph."
msgstr ""

#: ../../docs/tutorials/shaders/visual_shaders.rst:45
msgid ""
"The drop-down menu is the shader type: Vertex, Fragment and Light. Like for "
"script shaders, it defines what built-in nodes will be available."
msgstr ""

#: ../../docs/tutorials/shaders/visual_shaders.rst:47
msgid ""
"The following buttons and number input control the zooming level, grid "
"snapping and distance between grid lines (in pixels)."
msgstr ""

#: ../../docs/tutorials/shaders/visual_shaders.rst:49
msgid ""
"The last icon shows the generated shader code corresponding to your graph."
msgstr ""

#: ../../docs/tutorials/shaders/visual_shaders.rst:53
msgid ""
"Although VisualShaders do not require coding, they share the same logic with "
"script shaders. It is advised to learn the basics of both to have a good "
"understanding of the shading pipeline."
msgstr ""

#: ../../docs/tutorials/shaders/visual_shaders.rst:57
msgid ""
"The visual shader graph is converted to a script shader behind the scene, "
"and you can see this code by pressing the last button in the toolbar. This "
"can be convenient to understand what a given node does and how to reproduce "
"it in scripts."
msgstr ""

#: ../../docs/tutorials/shaders/visual_shaders.rst:63
msgid "Using the Visual Shader Editor"
msgstr ""

#: ../../docs/tutorials/shaders/visual_shaders.rst:65
msgid ""
"By default, every new ``VisualShader`` will have an output node. Every node "
"connection ends at one of the output node's sockets. A node is the basic "
"unit to create your shader. To add a new node, click on the ``Add Node`` "
"button on the upper left corner or right click on any empty location in the "
"graph, and a menu will pop up."
msgstr ""

#: ../../docs/tutorials/shaders/visual_shaders.rst:73
msgid "This popup has the following properties:"
msgstr ""

#: ../../docs/tutorials/shaders/visual_shaders.rst:75
msgid ""
"If you right-click on the graph, this menu will be called at the cursor "
"position and the created node, in that case, will also be placed under that "
"position; otherwise, it will be created at the graph's center."
msgstr ""

#: ../../docs/tutorials/shaders/visual_shaders.rst:78
msgid ""
"It can be resized horizontally and vertically allowing more content to be "
"shown. Size transform and tree content position are saved between the calls, "
"so if you suddenly closed the popup you can easily restore its previous "
"state."
msgstr ""

#: ../../docs/tutorials/shaders/visual_shaders.rst:81
msgid ""
"The ``Expand All`` and ``Collapse All`` options in the drop-down option menu "
"can be used to easily list the available nodes."
msgstr ""

#: ../../docs/tutorials/shaders/visual_shaders.rst:83
msgid "You can also drag and drop nodes from the popup onto the graph."
msgstr ""

#: ../../docs/tutorials/shaders/visual_shaders.rst:85
msgid ""
"While the popup has nodes sorted in categories, it can seem overwhelming at "
"first. Try to add some of the nodes, plug them in the output socket and "
"observe what happens."
msgstr ""

#: ../../docs/tutorials/shaders/visual_shaders.rst:89
msgid ""
"When connecting any ``scalar`` output to a ``vector`` input, all components "
"of the vector will take the value of the scalar."
msgstr ""

#: ../../docs/tutorials/shaders/visual_shaders.rst:92
msgid ""
"When connecting any ``vector`` output to a ``scalar`` input, the value of "
"the scalar will be the average of the vector's components."
msgstr ""

#: ../../docs/tutorials/shaders/visual_shaders.rst:96
#, fuzzy
msgid "Visual Shader node interface"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/shaders/visual_shaders.rst:98
msgid ""
"Visual shader nodes have input and output ports. The input ports are located "
"on the left side of the node, and output ports are located on the right side "
"of the node."
msgstr ""

#: ../../docs/tutorials/shaders/visual_shaders.rst:102
msgid "These ports are colored to differentiate type of port:"
msgstr ""

#: ../../docs/tutorials/shaders/visual_shaders.rst:104
msgid "scalar"
msgstr ""

#: ../../docs/tutorials/shaders/visual_shaders.rst:105
msgid "vector"
msgstr ""

#: ../../docs/tutorials/shaders/visual_shaders.rst:107
#, fuzzy
msgid "transform"
msgstr "Windows"

#: ../../docs/tutorials/shaders/visual_shaders.rst:108
msgid "sampler"
msgstr ""

#: ../../docs/tutorials/shaders/visual_shaders.rst:111
msgid "Port types"
msgstr ""

#: ../../docs/tutorials/shaders/visual_shaders.rst:119
#, fuzzy
msgid "Scalar"
msgstr "Razmera"

#: ../../docs/tutorials/shaders/visual_shaders.rst:120
msgid "Cyan"
msgstr ""

#: ../../docs/tutorials/shaders/visual_shaders.rst:121
msgid "Scalar is a single value."
msgstr ""

#: ../../docs/tutorials/shaders/visual_shaders.rst:122
msgid "|scalar|"
msgstr ""

#: ../../docs/tutorials/shaders/visual_shaders.rst:123
#: ../../docs/contributing/development/core_and_modules/core_types.rst:142
msgid "Vector"
msgstr ""

#: ../../docs/tutorials/shaders/visual_shaders.rst:124
msgid "Purple"
msgstr ""

#: ../../docs/tutorials/shaders/visual_shaders.rst:125
msgid "Vector is a set of values."
msgstr ""

#: ../../docs/tutorials/shaders/visual_shaders.rst:126
msgid "|vector|"
msgstr ""

#: ../../docs/tutorials/shaders/visual_shaders.rst:127
msgid "Boolean"
msgstr ""

#: ../../docs/tutorials/shaders/visual_shaders.rst:128
msgid "Blue"
msgstr ""

#: ../../docs/tutorials/shaders/visual_shaders.rst:129
msgid "On or off, true or false."
msgstr ""

#: ../../docs/tutorials/shaders/visual_shaders.rst:130
msgid "|boolean|"
msgstr ""

#: ../../docs/tutorials/shaders/visual_shaders.rst:132
msgid "Orange"
msgstr ""

#: ../../docs/tutorials/shaders/visual_shaders.rst:133
msgid "A matrix, usually used to transform vertices."
msgstr ""

#: ../../docs/tutorials/shaders/visual_shaders.rst:134
#, fuzzy
msgid "|transform|"
msgstr "Windows"

#: ../../docs/tutorials/shaders/visual_shaders.rst:135
msgid "Sampler"
msgstr ""

#: ../../docs/tutorials/shaders/visual_shaders.rst:136
msgid "Yellow"
msgstr ""

#: ../../docs/tutorials/shaders/visual_shaders.rst:137
msgid "A texture sampler. It can be used to sample textures."
msgstr ""

#: ../../docs/tutorials/shaders/visual_shaders.rst:138
msgid "|sampler|"
msgstr ""

#: ../../docs/tutorials/shaders/visual_shaders.rst:140
msgid ""
"All of the types are used in the calculations of vertices, fragments, and "
"lights in the shader. For example: matrix multiplication, vector addition, "
"or scalar division."
msgstr ""

#: ../../docs/tutorials/shaders/visual_shaders.rst:143
msgid "There are other types but these are the main ones."
msgstr ""

#: ../../docs/tutorials/shaders/visual_shaders.rst:146
#, fuzzy
msgid "Visual Shader nodes"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/shaders/visual_shaders.rst:148
msgid ""
"Below are some special nodes that are worth knowing about. The list is not "
"exhaustive and might be expanded with more nodes and examples."
msgstr ""

#: ../../docs/tutorials/shaders/visual_shaders.rst:152
msgid "Expression node"
msgstr ""

#: ../../docs/tutorials/shaders/visual_shaders.rst:154
msgid ""
"The ``Expression`` node allows you to write Godot Shading Language (GLSL-"
"like) expressions inside your visual shaders. The node has buttons to add "
"any amount of required input and output ports and can be resized. You can "
"also set up the name and type of each port. The expression you have entered "
"will apply immediately to the material (once the focus leaves the expression "
"text box). Any parsing or compilation errors will be printed to the Output "
"tab. The outputs are initialized to their zero value by default. The node is "
"located under the Special tab and can be used in all shader modes."
msgstr ""

#: ../../docs/tutorials/shaders/visual_shaders.rst:165
msgid ""
"The possibilities of this node are almost limitless – you can write complex "
"procedures, and use all the power of text-based shaders, such as loops, the "
"``discard`` keyword, extended types, etc. For example:"
msgstr ""

#: ../../docs/tutorials/shaders/visual_shaders.rst:172
msgid "Fresnel node"
msgstr ""

#: ../../docs/tutorials/shaders/visual_shaders.rst:174
msgid ""
"The ``Fresnel`` node is designed to accept normal and view vectors and "
"produces a scalar which is the saturated dot product between them. "
"Additionally, you can setup the inversion and the power of equation. The "
"``Fresnel`` node is great for adding a rim-like lighting effect to objects."
msgstr ""

#: ../../docs/tutorials/shaders/visual_shaders.rst:182
msgid "Boolean node"
msgstr ""

#: ../../docs/tutorials/shaders/visual_shaders.rst:184
msgid ""
"The ``Boolean`` node can be converted to ``Scalar`` or ``Vector`` to "
"represent ``0`` or ``1`` and ``(0, 0, 0)`` or ``(1, 1, 1)`` respectively. "
"This property can be used to enable or disable some effect parts with one "
"click."
msgstr ""

#: ../../docs/tutorials/shaders/visual_shaders.rst:191
msgid "If node"
msgstr ""

#: ../../docs/tutorials/shaders/visual_shaders.rst:193
msgid ""
"The ``If`` node allows you to setup a vector which will be returned the "
"result of the comparison between ``a`` and ``b``. There are three vectors "
"which can be returned: ``a == b`` (in that case the tolerance parameter is "
"provided as a comparison threshold – by default it is equal to the minimal "
"value, i.e. ``0.00001``), ``a > b`` and ``a < b``."
msgstr ""

#: ../../docs/tutorials/shaders/visual_shaders.rst:202
msgid "Switch node"
msgstr ""

#: ../../docs/tutorials/shaders/visual_shaders.rst:204
msgid ""
"The ``Switch`` node returns a vector if the boolean condition is ``true`` or "
"``false``. ``Boolean`` was introduced above. If you convert a vector to a "
"true boolean, all components of the vector should be above zero."
msgstr ""

#: ../../docs/tutorials/shaders/compute_shaders.rst:4
#, fuzzy
msgid "Using compute shaders"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/shaders/compute_shaders.rst:6
msgid ""
"This tutorial will walk you through the process of creating a minimal "
"compute shader. But first, a bit of background on compute shaders and how "
"they work with Godot."
msgstr ""

#: ../../docs/tutorials/shaders/compute_shaders.rst:12
msgid ""
"This tutorial assumes you are familiar with shaders generally. If you are "
"new to shaders please read :ref:`doc_introduction_to_shaders` and :ref:`your "
"first shader <toc-your-first-shader>` before proceeding with this tutorial."
msgstr ""

#: ../../docs/tutorials/shaders/compute_shaders.rst:16
msgid ""
"A compute shader is a special type of shader program that is orientated "
"towards general purpose programming. In other words, they are more flexible "
"than vertex shaders and fragment shaders as they don't have a fixed purpose "
"(i.e. transforming vertices or writing colors to an image). Unlike fragment "
"shaders and vertex shaders, compute shaders have very little going on behind "
"the scenes. The code you write is what the GPU runs and very little else. "
"This can make them a very useful tool to offload heavy calculations to the "
"GPU."
msgstr ""

#: ../../docs/tutorials/shaders/compute_shaders.rst:24
msgid "Now let's get started by creating a short compute shader."
msgstr ""

#: ../../docs/tutorials/shaders/compute_shaders.rst:26
msgid ""
"First, in the **external** text editor of your choice, create a new file "
"called ``compute_example.glsl`` in your project folder. When you write "
"compute shaders in Godot, you write them in GLSL directly. The Godot shader "
"language is based on GLSL. If you are familiar with normal shaders in Godot, "
"the syntax below will look somewhat familiar."
msgstr ""

#: ../../docs/tutorials/shaders/compute_shaders.rst:34
msgid ""
"Compute shaders can only be used from RenderingDevice-based renderers (the "
"Forward+ or Mobile renderer). To follow along with this tutorial, ensure "
"that you are using the Forward+ or Mobile renderer. The setting for which is "
"located in the top right-hand corner of the editor."
msgstr ""

#: ../../docs/tutorials/shaders/compute_shaders.rst:39
msgid ""
"Note that compute shader support is generally poor on mobile devices (due to "
"driver bugs), even if they are technically supported."
msgstr ""

#: ../../docs/tutorials/shaders/compute_shaders.rst:42
msgid "Let's take a look at this compute shader code:"
msgstr ""

#: ../../docs/tutorials/shaders/compute_shaders.rst:64
msgid ""
"This code takes an array of floats, multiplies each element by 2 and store "
"the results back in the buffer array. Now let's look at it line-by-line."
msgstr ""

#: ../../docs/tutorials/shaders/compute_shaders.rst:72
msgid "These two lines communicate two things:"
msgstr ""

#: ../../docs/tutorials/shaders/compute_shaders.rst:74
msgid ""
"The following code is a compute shader. This is a Godot-specific hint that "
"is needed for the editor to properly import the shader file."
msgstr ""

#: ../../docs/tutorials/shaders/compute_shaders.rst:75
msgid "The code is using GLSL version 450."
msgstr ""

#: ../../docs/tutorials/shaders/compute_shaders.rst:77
msgid ""
"You should never have to change these two lines for your custom compute "
"shaders."
msgstr ""

#: ../../docs/tutorials/shaders/compute_shaders.rst:84
msgid ""
"Next, we communicate the number of invocations to be used in each workgroup. "
"Invocations are instances of the shader that are running within the same "
"workgroup. When we launch a compute shader from the CPU, we tell it how many "
"workgroups to run. Workgroups run in parallel to each other. While running "
"one workgroup, you cannot access information in another workgroup. However, "
"invocations in the same workgroup can have some limited access to other "
"invocations."
msgstr ""

#: ../../docs/tutorials/shaders/compute_shaders.rst:91
msgid "Think about workgroups and invocations as a giant nested ``for`` loop."
msgstr ""

#: ../../docs/tutorials/shaders/compute_shaders.rst:111
msgid ""
"Workgroups and invocations are an advanced topic. For now, remember that we "
"will be running two invocations per workgroup."
msgstr ""

#: ../../docs/tutorials/shaders/compute_shaders.rst:122
msgid ""
"Here we provide information about the memory that the compute shader will "
"have access to. The ``layout`` property allows us to tell the shader where "
"to look for the buffer, we will need to match these ``set`` and ``binding`` "
"positions from the CPU side later."
msgstr ""

#: ../../docs/tutorials/shaders/compute_shaders.rst:127
msgid ""
"The ``restrict`` keyword tells the shader that this buffer is only going to "
"be accessed from one place in this shader. In other words, we won't bind "
"this buffer in another ``set`` or ``binding`` index. This is important as it "
"allows the shader compiler to optimize the shader code. Always use "
"``restrict`` when you can."
msgstr ""

#: ../../docs/tutorials/shaders/compute_shaders.rst:133
msgid ""
"This is an *unsized* buffer, which means it can be any size. So we need to "
"be careful not to read from an index larger than the size of the buffer."
msgstr ""

#: ../../docs/tutorials/shaders/compute_shaders.rst:144
msgid ""
"Finally, we write the ``main`` function which is where all the logic "
"happens. We access a position in the storage buffer using the "
"``gl_GlobalInvocationID`` built in variables. ``gl_GlobalInvocationID`` "
"gives you the global unique ID for the current invocation."
msgstr ""

#: ../../docs/tutorials/shaders/compute_shaders.rst:149
msgid ""
"To continue, write the code above into your newly created ``compute_example."
"glsl`` file."
msgstr ""

#: ../../docs/tutorials/shaders/compute_shaders.rst:153
msgid "Create a local RenderingDevice"
msgstr ""

#: ../../docs/tutorials/shaders/compute_shaders.rst:155
msgid ""
"To interact with and execute a compute shader, we need a script. Create a "
"new script in the language of your choice and attach it to any Node in your "
"scene."
msgstr ""

#: ../../docs/tutorials/shaders/compute_shaders.rst:159
msgid ""
"Now to execute our shader we need a local :ref:`class_RenderingDevice` which "
"can be created using the :ref:`class_RenderingServer`:"
msgstr ""

#: ../../docs/tutorials/shaders/compute_shaders.rst:173
msgid ""
"After that, we can load the newly created shader file ``compute_example."
"glsl`` and create a precompiled version of it using this:"
msgstr ""

#: ../../docs/tutorials/shaders/compute_shaders.rst:193
msgid ""
"Local RenderingDevices cannot be debugged using tools such as `RenderDoc "
"<https://renderdoc.org/>`__."
msgstr ""

#: ../../docs/tutorials/shaders/compute_shaders.rst:197
msgid "Provide input data"
msgstr ""

#: ../../docs/tutorials/shaders/compute_shaders.rst:199
msgid ""
"As you might remember, we want to pass an input array to our shader, "
"multiply each element by 2 and get the results."
msgstr ""

#: ../../docs/tutorials/shaders/compute_shaders.rst:202
msgid ""
"We need to create a buffer to pass values to a compute shader. We are "
"dealing with an array of floats, so we will use a storage buffer for this "
"example. A storage buffer takes an array of bytes and allows the CPU to "
"transfer data to and from the GPU."
msgstr ""

#: ../../docs/tutorials/shaders/compute_shaders.rst:207
msgid "So let's initialize an array of floats and create a storage buffer:"
msgstr ""

#: ../../docs/tutorials/shaders/compute_shaders.rst:231
msgid ""
"With the buffer in place we need to tell the rendering device to use this "
"buffer. To do that we will need to create a uniform (like in normal shaders) "
"and assign it to a uniform set which we can pass to our shader later."
msgstr ""

#: ../../docs/tutorials/shaders/compute_shaders.rst:258
msgid "Defining a compute pipeline"
msgstr ""

#: ../../docs/tutorials/shaders/compute_shaders.rst:260
msgid ""
"The next step is to create a set of instructions our GPU can execute. We "
"need a pipeline and a compute list for that."
msgstr ""

#: ../../docs/tutorials/shaders/compute_shaders.rst:263
msgid "The steps we need to do to compute our result are:"
msgstr ""

#: ../../docs/tutorials/shaders/compute_shaders.rst:265
#, fuzzy
msgid "Create a new pipeline."
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/shaders/compute_shaders.rst:266
msgid "Begin a list of instructions for our GPU to execute."
msgstr ""

#: ../../docs/tutorials/shaders/compute_shaders.rst:267
msgid "Bind our compute list to our pipeline"
msgstr ""

#: ../../docs/tutorials/shaders/compute_shaders.rst:268
msgid "Bind our buffer uniform to our pipeline"
msgstr ""

#: ../../docs/tutorials/shaders/compute_shaders.rst:269
msgid "Specify how many workgroups to use"
msgstr ""

#: ../../docs/tutorials/shaders/compute_shaders.rst:270
#, fuzzy
msgid "End the list of instructions"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/shaders/compute_shaders.rst:293
msgid ""
"Note that we are dispatching the compute shader with 5 work groups in the X "
"axis, and one in the others. Since we have 2 local invocations in the X axis "
"(specified in our shader), 10 compute shader invocations will be launched in "
"total. If you read or write to indices outside of the range of your buffer, "
"you may access memory outside of your shaders control or parts of other "
"variables which may cause issues on some hardware."
msgstr ""

#: ../../docs/tutorials/shaders/compute_shaders.rst:301
msgid "Execute a compute shader"
msgstr ""

#: ../../docs/tutorials/shaders/compute_shaders.rst:303
msgid ""
"After all of this we are almost done, but we still need to execute our "
"pipeline. So far we have only recorded what we would like the GPU to do; we "
"have not actually run the shader program."
msgstr ""

#: ../../docs/tutorials/shaders/compute_shaders.rst:307
msgid ""
"To execute our compute shader we need to submit the pipeline to the GPU and "
"wait for the execution to finish:"
msgstr ""

#: ../../docs/tutorials/shaders/compute_shaders.rst:323
msgid ""
"Ideally, you would not call ``sync()`` to synchronize the RenderingDevice "
"right away as it will cause the CPU to wait for the GPU to finish working. "
"In our example, we synchronize right away because we want our data available "
"for reading right away. In general, you will want to wait *at least* 2 or 3 "
"frames before synchronizing so that the GPU is able to run in parallel with "
"the CPU."
msgstr ""

#: ../../docs/tutorials/shaders/compute_shaders.rst:331
msgid ""
"Long computations can cause Windows graphics drivers to \"crash\" due to :"
"abbr:`TDR (Timeout Detection and Recovery)` being triggered by Windows. This "
"is a mechanism that reinitializes the graphics driver after a certain amount "
"of time has passed without any activity from the graphics driver (usually 5 "
"to 10 seconds)."
msgstr ""

#: ../../docs/tutorials/shaders/compute_shaders.rst:337
msgid ""
"Depending on the duration your compute shader takes to execute, you may need "
"to split it into multiple dispatches to reduce the time each dispatch takes "
"and reduce the chances of triggering a TDR. Given TDR is time-dependent, "
"slower GPUs may be more prone to TDRs when running a given compute shader "
"compared to a faster GPU."
msgstr ""

#: ../../docs/tutorials/shaders/compute_shaders.rst:344
msgid "Retrieving results"
msgstr ""

#: ../../docs/tutorials/shaders/compute_shaders.rst:346
msgid ""
"You may have noticed that, in the example shader, we modified the contents "
"of the storage buffer. In other words, the shader read from our array and "
"stored the data in the same array again so our results are already there. "
"Let's retrieve the data and print the results to our console."
msgstr ""

#: ../../docs/tutorials/shaders/compute_shaders.rst:369
msgid ""
"With that, you have everything you need to get started working with compute "
"shaders."
msgstr ""

#: ../../docs/tutorials/shaders/compute_shaders.rst:374
msgid ""
"The demo projects repository contains a `Compute Shader Heightmap demo "
"<https://github.com/godotengine/godot-demo-projects/tree/master/misc/"
"compute_shader_heightmap>`__ This project performs heightmap image "
"generation on the CPU and GPU separately, which lets you compare how a "
"similar algorithm can be implemented in two different ways (with the GPU "
"implementation being faster in most cases)."
msgstr ""

#: ../../docs/tutorials/shaders/screen-reading_shaders.rst:4
msgid "Screen-reading shaders"
msgstr ""

#: ../../docs/tutorials/shaders/screen-reading_shaders.rst:9
msgid ""
"It is often desired to make a shader that reads from the same screen to "
"which it's writing. 3D APIs, such as OpenGL or DirectX, make this very "
"difficult because of internal hardware limitations. GPUs are extremely "
"parallel, so reading and writing causes all sorts of cache and coherency "
"problems. As a result, not even the most modern hardware supports this "
"properly."
msgstr ""

#: ../../docs/tutorials/shaders/screen-reading_shaders.rst:16
msgid ""
"The workaround is to make a copy of the screen, or a part of the screen, to "
"a back-buffer and then read from it while drawing. Godot provides a few "
"tools that make this process easy."
msgstr ""

#: ../../docs/tutorials/shaders/screen-reading_shaders.rst:21
#, fuzzy
msgid "Screen texture"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/shaders/screen-reading_shaders.rst:23
msgid ""
"Godot :ref:`doc_shading_language` has a special texture to access the "
"already rendered contents of the screen. It is used by specifying a hint "
"when declaring a ``sampler2D`` uniform: ``hint_screen_texture``. A special "
"built-in varying ``SCREEN_UV`` can be used to obtain the UV relative to the "
"screen for the current fragment. As a result, this canvas_item fragment "
"shader results in an invisible object, because it only shows what lies "
"behind:"
msgstr ""

#: ../../docs/tutorials/shaders/screen-reading_shaders.rst:40
msgid ""
"``textureLod`` is used here as we only want to read from the bottom mipmap. "
"If you want to read from a blurred version of the texture instead, you can "
"increase the third argument to ``textureLod`` and change the hint "
"``filter_nearest`` to ``filter_nearest_mipmap`` (or any other filter with "
"mipmaps enabled). If using a filter with mipmaps, Godot will automatically "
"calculate the blurred texture for you."
msgstr ""

#: ../../docs/tutorials/shaders/screen-reading_shaders.rst:49
msgid ""
"If the filter mode is not changed to a filter mode that contains ``mipmap`` "
"in its name, ``textureLod`` with a LOD parameter greater than ``0.0`` will "
"have the same appearance as with the ``0.0`` LOD parameter."
msgstr ""

#: ../../docs/tutorials/shaders/screen-reading_shaders.rst:54
msgid "Screen texture example"
msgstr ""

#: ../../docs/tutorials/shaders/screen-reading_shaders.rst:56
msgid ""
"The screen texture can be used for many things. There is a special demo for "
"*Screen Space Shaders*, that you can download to see and learn. One example "
"is a simple shader to adjust brightness, contrast and saturation:"
msgstr ""

#: ../../docs/tutorials/shaders/screen-reading_shaders.rst:82
msgid "Behind the scenes"
msgstr ""

#: ../../docs/tutorials/shaders/screen-reading_shaders.rst:84
msgid ""
"While this seems magical, it's not. In 2D, when ``hint_screen_texture`` is "
"first found in a node that is about to be drawn, Godot does a full-screen "
"copy to a back-buffer. Subsequent nodes that use it in shaders will not have "
"the screen copied for them, because this ends up being inefficient. In 3D, "
"the screen is copied after the opaque geometry pass, but before the "
"transparent geometry pass, so transparent objects will not be captured in "
"the screen texture."
msgstr ""

#: ../../docs/tutorials/shaders/screen-reading_shaders.rst:91
msgid ""
"As a result, in 2D, if shaders that use ``hint_screen_texture`` overlap, the "
"second one will not use the result of the first one, resulting in unexpected "
"visuals:"
msgstr ""

#: ../../docs/tutorials/shaders/screen-reading_shaders.rst:97
msgid ""
"In the above image, the second sphere (top right) is using the same source "
"for the screen texture as the first one below, so the first one "
"\"disappears\", or is not visible."
msgstr ""

#: ../../docs/tutorials/shaders/screen-reading_shaders.rst:101
msgid ""
"In 2D, this can be corrected via the :ref:`BackBufferCopy "
"<class_BackBufferCopy>` node, which can be instantiated between both "
"spheres. BackBufferCopy can work by either specifying a screen region or the "
"whole screen:"
msgstr ""

#: ../../docs/tutorials/shaders/screen-reading_shaders.rst:107
msgid "With correct back-buffer copying, the two spheres blend correctly:"
msgstr ""

#: ../../docs/tutorials/shaders/screen-reading_shaders.rst:113
msgid ""
"In 3D, materials that use ``hint_screen_texture`` are considered transparent "
"themselves and will not appear in the resulting screen texture of other "
"materials. If you plan to instance a scene that uses a material with "
"``hint_screen_texture``, you will need to use a BackBufferCopy node."
msgstr ""

#: ../../docs/tutorials/shaders/screen-reading_shaders.rst:118
msgid ""
"In 3D, there is less flexibility to solve this particular issue because the "
"screen texture is only captured once. Be careful when using the screen "
"texture in 3D as it won't capture transparent objects and may capture some "
"opaque objects that are in front of the object using the screen texture."
msgstr ""

#: ../../docs/tutorials/shaders/screen-reading_shaders.rst:123
msgid ""
"You can reproduce the back-buffer logic in 3D by creating a :ref:`Viewport "
"<class_Viewport>` with a camera in the same position as your object, and "
"then use the :ref:`Viewport's <class_Viewport>` texture instead of the "
"screen texture."
msgstr ""

#: ../../docs/tutorials/shaders/screen-reading_shaders.rst:128
msgid "Back-buffer logic"
msgstr ""

#: ../../docs/tutorials/shaders/screen-reading_shaders.rst:130
msgid ""
"So, to make it clearer, here's how the backbuffer copying logic works in 2D "
"in Godot:"
msgstr ""

#: ../../docs/tutorials/shaders/screen-reading_shaders.rst:133
msgid ""
"If a node uses ``hint_screen_texture``, the entire screen is copied to the "
"back buffer before drawing that node. This only happens the first time; "
"subsequent nodes do not trigger this."
msgstr ""

#: ../../docs/tutorials/shaders/screen-reading_shaders.rst:136
msgid ""
"If a BackBufferCopy node was processed before the situation in the point "
"above (even if ``hint_screen_texture`` was not used), the behavior described "
"in the point above does not happen. In other words, automatic copying of the "
"entire screen only happens if ``hint_screen_texture`` is used in a node for "
"the first time and no BackBufferCopy node (not disabled) was found before in "
"tree-order."
msgstr ""

#: ../../docs/tutorials/shaders/screen-reading_shaders.rst:142
msgid ""
"BackBufferCopy can copy either the entire screen or a region. If set to only "
"a region (not the whole screen) and your shader uses pixels not in the "
"region copied, the result of that read is undefined (most likely garbage "
"from previous frames). In other words, it's possible to use BackBufferCopy "
"to copy back a region of the screen and then read the screen texture from a "
"different region. Avoid this behavior!"
msgstr ""

#: ../../docs/tutorials/shaders/screen-reading_shaders.rst:151
#: ../../docs/tutorials/shaders/advanced_postprocessing.rst:70
msgid "Depth texture"
msgstr ""

#: ../../docs/tutorials/shaders/screen-reading_shaders.rst:153
msgid ""
"For 3D shaders, it's also possible to access the screen depth buffer. For "
"this, the ``hint_depth_texture`` hint is used. This texture is not linear; "
"it must be converted using the inverse projection matrix."
msgstr ""

#: ../../docs/tutorials/shaders/screen-reading_shaders.rst:157
msgid ""
"The following code retrieves the 3D position below the pixel being drawn:"
msgstr ""

#: ../../docs/tutorials/shaders/screen-reading_shaders.rst:170
msgid "Normal-roughness texture"
msgstr ""

#: ../../docs/tutorials/shaders/screen-reading_shaders.rst:174
msgid ""
"Normal-roughness texture is only supported in the Forward+ rendering method, "
"not Mobile or Compatibility."
msgstr ""

#: ../../docs/tutorials/shaders/screen-reading_shaders.rst:177
msgid ""
"Similarly, the normal-roughness texture can be used to read the normals and "
"roughness of objects rendered in the depth prepass. The normal is stored in "
"the ``.xyz`` channels (mapped to the 0-1 range) while the roughness is "
"stored in the ``.w`` channel."
msgstr ""

#: ../../docs/tutorials/shaders/screen-reading_shaders.rst:192
#, fuzzy
msgid "Redefining screen textures"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/shaders/screen-reading_shaders.rst:194
msgid ""
"The screen texture hints (``hint_screen_texture``, ``hint_depth_texture``, "
"and ``hint_normal_roughness_texture``) can be used with multiple uniforms. "
"For example, you may want to read from the texture multiple times with a "
"different repeat flag or filter flag."
msgstr ""

#: ../../docs/tutorials/shaders/screen-reading_shaders.rst:199
msgid ""
"The following example shows a shader that reads the screen space normal with "
"linear filtering, but reads the screen space roughness using nearest "
"neighbor filtering."
msgstr ""

#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:4
msgid "Converting GLSL to Godot shaders"
msgstr ""

#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:6
msgid ""
"This document explains the differences between Godot's shading language and "
"GLSL and gives practical advice on how to migrate shaders from other "
"sources, such as Shadertoy and The Book of Shaders, into Godot shaders."
msgstr ""

#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:10
msgid ""
"For detailed information on Godot's shading language, please refer to the :"
"ref:`Shading Language <doc_shading_language>` reference."
msgstr ""

#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:14
msgid "GLSL"
msgstr ""

#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:16
msgid ""
"Godot uses a shading language based on GLSL with the addition of a few "
"quality-of-life features. Accordingly, most features available in GLSL are "
"available in Godot's shading language."
msgstr ""

#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:21
msgid "Shader programs"
msgstr ""

#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:23
msgid ""
"In GLSL, each shader uses a separate program. You have one program for the "
"vertex shader and one for the fragment shader. In Godot, you have a single "
"shader that contains a ``vertex`` and/or a ``fragment`` function. If you "
"only choose to write one, Godot will supply the other."
msgstr ""

#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:28
msgid ""
"Godot allows uniform variables and functions to be shared by defining the "
"fragment and vertex shaders in one file. In GLSL, the vertex and fragment "
"programs cannot share variables except when varyings are used."
msgstr ""

#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:33
msgid "Vertex attributes"
msgstr ""

#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:35
msgid ""
"In GLSL, you can pass in per-vertex information using attributes and have "
"the flexibility to pass in as much or as little as you want. In Godot, you "
"have a set number of input attributes, including ``VERTEX`` (position), "
"``COLOR``, ``UV``, ``UV2``, ``NORMAL``. Each shaders' page in the shader "
"reference section of the documentation comes with a complete list of its "
"vertex attributes."
msgstr ""

#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:42
#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:97
msgid "gl_Position"
msgstr ""

#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:44
msgid ""
"``gl_Position`` receives the final position of a vertex specified in the "
"vertex shader. It is specified by the user in clip space. Typically, in "
"GLSL, the model space vertex position is passed in using a vertex attribute "
"called ``position`` and you handle the conversion from model space to clip "
"space manually."
msgstr ""

#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:49
msgid ""
"In Godot, ``VERTEX`` specifies the vertex position in model space at the "
"beginning of the ``vertex`` function. Godot also handles the final "
"conversion to clip space after the user-defined ``vertex`` function is run. "
"If you want to skip the conversion from model to view space, you can set the "
"``render_mode`` to ``skip_vertex_transform``. If you want to skip all "
"transforms, set ``render_mode`` to ``skip_vertex_transform`` and set the "
"``PROJECTION_MATRIX`` to ``mat4(1.0)`` in order to nullify the final "
"transform from view space to clip space."
msgstr ""

#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:61
msgid ""
"Varyings are a type of variable that can be passed from the vertex shader to "
"the fragment shader. In modern GLSL (3.0 and up), varyings are defined with "
"the ``in`` and ``out`` keywords. A variable going out of the vertex shader "
"is defined with ``out`` in the vertex shader and ``in`` inside the fragment "
"shader."
msgstr ""

#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:67
#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:216
msgid "Main"
msgstr ""

#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:69
msgid ""
"In GLSL, each shader program looks like a self-contained C-style program. "
"Accordingly, the main entry point is ``main``. If you are copying a vertex "
"shader, rename ``main`` to ``vertex`` and if you are copying a fragment "
"shader, rename ``main`` to ``fragment``."
msgstr ""

#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:75
msgid "Macros"
msgstr ""

#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:77
msgid ""
"The :ref:`Godot shader preprocessor<doc_shader_preprocessor>` supports the "
"following macros:"
msgstr ""

#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:79
msgid "``#define`` / ``#undef``"
msgstr ""

#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:80
msgid ""
"``#if``, ``#elif``, ``#else``, ``#endif``, ``defined()``, ``#ifdef``, "
"``#ifndef``"
msgstr ""

#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:81
msgid ""
"``#include`` (only ``.gdshaderinc`` files and with a maximum depth of 25)"
msgstr ""

#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:82
msgid ""
"``#pragma disable_preprocessor``, which disables preprocessing for the rest "
"of the file"
msgstr ""

#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:87
msgid ""
"GLSL has many built-in variables that are hard-coded. These variables are "
"not uniforms, so they are not editable from the main program."
msgstr ""

#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:91
#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:164
#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:229
msgid "Equivalent"
msgstr ""

#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:93
#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:231
msgid "gl_FragColor"
msgstr ""

#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:93
#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:166
#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:231
msgid "out vec4"
msgstr ""

#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:93
#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:166
#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:231
msgid "COLOR"
msgstr ""

#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:93
#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:166
#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:231
msgid "Output color for each pixel."
msgstr ""

#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:95
#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:233
msgid "gl_FragCoord"
msgstr ""

#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:95
#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:97
#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:180
#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:182
#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:233
msgid "vec4"
msgstr ""

#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:95
#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:233
msgid "FRAGCOORD"
msgstr ""

#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:95
#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:168
#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:233
msgid "For full screen quads. For smaller quads, use UV."
msgstr ""

#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:97
msgid "VERTEX"
msgstr ""

#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:97
msgid "Position of Vertex, output from Vertex Shader."
msgstr ""

#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:99
msgid "gl_PointSize"
msgstr ""

#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:99
msgid "POINT_SIZE"
msgstr ""

#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:99
msgid "Size of Point primitive."
msgstr ""

#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:101
msgid "gl_PointCoord"
msgstr ""

#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:101
#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:168
#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:235
#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:239
msgid "vec2"
msgstr ""

#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:101
msgid "POINT_COORD"
msgstr ""

#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:101
msgid "Position on point when drawing Point primitives."
msgstr ""

#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:103
msgid "gl_FrontFacing"
msgstr ""

#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:103
msgid "FRONT_FACING"
msgstr ""

#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:103
msgid "True if front face of primitive."
msgstr ""

#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:109
#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:190
#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:243
msgid "Coordinates"
msgstr ""

#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:111
msgid ""
"``gl_FragCoord`` in GLSL and ``FRAGCOORD`` in the Godot shading language use "
"the same coordinate system. If using UV in Godot, the y-coordinate will be "
"flipped upside down."
msgstr ""

#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:118
msgid ""
"In GLSL, you can define the precision of a given type (float or int) at the "
"top of the shader with the ``precision`` keyword. In Godot, you can set the "
"precision of individual variables as you need by placing precision "
"qualifiers ``lowp``, ``mediump``, and ``highp`` before the type when "
"defining the variable. For more information, see the :ref:`Shading Language "
"<doc_shading_language>` reference."
msgstr ""

#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:126
msgid "Shadertoy"
msgstr ""

#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:128
msgid ""
"`Shadertoy <https://www.shadertoy.com/results?"
"query=&sort=popular&from=10&num=4>`_ is a website that makes it easy to "
"write fragment shaders and create `pure magic <https://www.shadertoy.com/"
"view/4tjGRh>`_."
msgstr ""

#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:132
msgid ""
"Shadertoy does not give the user full control over the shader. It handles "
"all the input and uniforms and only lets the user write the fragment shader."
msgstr ""

#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:136
#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:209
msgid "Types"
msgstr ""

#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:138
msgid ""
"Shadertoy uses the webgl spec, so it runs a slightly different version of "
"GLSL. However, it still has the regular types, including constants and "
"macros."
msgstr ""

#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:142
msgid "mainImage"
msgstr ""

#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:144
msgid ""
"The main point of entry to a Shadertoy shader is the ``mainImage`` function. "
"``mainImage`` has two parameters, ``fragColor`` and ``fragCoord``, which "
"correspond to ``COLOR`` and ``FRAGCOORD`` in Godot, respectively. These "
"parameters are handled automatically in Godot, so you do not need to include "
"them as parameters yourself. Anything in the ``mainImage`` function should "
"be copied into the ``fragment`` function when porting to Godot."
msgstr ""

#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:154
msgid ""
"In order to make writing fragment shaders straightforward and easy, "
"Shadertoy handles passing a lot of helpful information from the main program "
"into the fragment shader for you. A few of these have no equivalents in "
"Godot because Godot has chosen not to make them available by default. This "
"is okay because Godot gives you the ability to make your own uniforms. For "
"variables whose equivalents are listed as \"Provide with Uniform\", users "
"are responsible for creating that uniform themselves. The description gives "
"the reader a hint about what they can pass in as a substitute."
msgstr ""

#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:166
msgid "fragColor"
msgstr ""

#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:168
msgid "fragCoord"
msgstr ""

#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:168
msgid "FRAGCOORD.xy"
msgstr ""

#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:170
msgid "iResolution"
msgstr ""

#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:170
#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:184
msgid "vec3"
msgstr ""

#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:170
#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:235
msgid "1.0 / SCREEN_PIXEL_SIZE"
msgstr ""

#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:170
#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:235
msgid "Can also pass in manually."
msgstr ""

#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:172
msgid "iTime"
msgstr ""

#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:172
#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:237
msgid "TIME"
msgstr ""

#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:172
#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:237
msgid "Time since shader started."
msgstr ""

#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:174
msgid "iTimeDelta"
msgstr ""

#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:174
#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:176
#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:178
#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:180
#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:182
#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:239
msgid "Provide with Uniform"
msgstr ""

#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:174
msgid "Time to render previous frame."
msgstr ""

#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:176
msgid "iFrame"
msgstr ""

#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:176
msgid "Frame number."
msgstr ""

#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:178
msgid "iChannelTime[4]"
msgstr ""

#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:178
msgid "Time since that particular texture started."
msgstr ""

#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:180
msgid "iMouse"
msgstr ""

#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:180
#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:239
msgid "Mouse position in pixel coordinates."
msgstr ""

#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:182
msgid "iDate"
msgstr ""

#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:182
msgid "Current date, expressed in seconds."
msgstr ""

#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:184
msgid "iChannelResolution[4]"
msgstr ""

#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:184
msgid "1.0 / TEXTURE_PIXEL_SIZE"
msgstr ""

#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:184
msgid "Resolution of particular texture."
msgstr ""

#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:186
msgid "iChanneli"
msgstr ""

#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:186
msgid "Sampler2D"
msgstr ""

#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:186
msgid "TEXTURE"
msgstr ""

#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:186
msgid "Godot provides only one built-in; user can make more."
msgstr ""

#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:192
msgid ""
"``fragCoord`` behaves the same as ``gl_FragCoord`` in :ref:`GLSL "
"<glsl_coordinates>` and ``FRAGCOORD`` in Godot."
msgstr ""

#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:197
msgid "The Book of Shaders"
msgstr ""

#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:199
msgid ""
"Similar to Shadertoy, `The Book of Shaders <https://thebookofshaders.com>`_ "
"provides access to a fragment shader in the web browser, with which the user "
"may interact. The user is restricted to writing fragment shader code with a "
"set list of uniforms passed in and with no ability to add additional "
"uniforms."
msgstr ""

#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:204
msgid ""
"For further help on porting shaders to various frameworks generally, The "
"Book of Shaders provides a `page <https://thebookofshaders.com/04>`_ on "
"running shaders in various frameworks."
msgstr ""

#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:211
msgid ""
"The Book of Shaders uses the webgl spec, so it runs a slightly different "
"version of GLSL. However, it still has the regular types, including "
"constants and macros."
msgstr ""

#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:218
msgid ""
"The entry point for a Book of Shaders fragment shader is ``main``, just like "
"in GLSL. Everything written in a Book of Shaders ``main`` function should be "
"copied into Godot's ``fragment`` function."
msgstr ""

#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:225
msgid ""
"The Book of Shaders sticks closer to plain GLSL than Shadertoy does. It also "
"implements fewer uniforms than Shadertoy."
msgstr ""

#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:235
msgid "u_resolution"
msgstr ""

#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:237
msgid "u_time"
msgstr ""

#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:239
msgid "u_mouse"
msgstr ""

#: ../../docs/tutorials/shaders/converting_glsl_to_godot_shaders.rst:245
msgid ""
"The Book of Shaders uses the same coordinate system as :ref:`GLSL "
"<glsl_coordinates>`."
msgstr ""

#: ../../docs/tutorials/shaders/shaders_style_guide.rst:4
#, fuzzy
msgid "Shaders style guide"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/shaders/shaders_style_guide.rst:6
msgid ""
"This style guide lists conventions to write elegant shaders. The goal is to "
"encourage writing clean, readable code and promote consistency across "
"projects, discussions, and tutorials. Hopefully, this will also support the "
"development of auto-formatting tools."
msgstr ""

#: ../../docs/tutorials/shaders/shaders_style_guide.rst:11
msgid ""
"Since the Godot shader language is close to C-style languages and GLSL, this "
"guide is inspired by Godot's own GLSL formatting. You can view examples of "
"GLSL files in Godot's source code `here <https://github.com/godotengine/"
"godot/blob/master/drivers/gles3/shaders/>`__."
msgstr ""

#: ../../docs/tutorials/shaders/shaders_style_guide.rst:23
msgid ""
"Godot's built-in shader editor uses a lot of these conventions by default. "
"Let it help you."
msgstr ""

#: ../../docs/tutorials/shaders/shaders_style_guide.rst:26
msgid "Here is a complete shader example based on these guidelines:"
msgstr ""

#: ../../docs/tutorials/shaders/shaders_style_guide.rst:64
msgid ""
"Each indent level should be one tab greater than the block containing it."
msgstr ""

#: ../../docs/tutorials/shaders/shaders_style_guide.rst:105
msgid ""
"For a general indentation rule, follow `the \"1TBS Style\" <https://en."
"wikipedia.org/wiki/Indentation_style#Variant:_1TBS_(OTBS)>`_ which "
"recommends placing the brace associated with a control statement on the same "
"line. Always use braces for statements, even if they only span one line. "
"This makes them easier to refactor and avoids mistakes when adding more "
"lines to an ``if`` statement or similar."
msgstr ""

#: ../../docs/tutorials/shaders/shaders_style_guide.rst:135
msgid "Surround function definitions with one (and only one) blank line:"
msgstr ""

#: ../../docs/tutorials/shaders/shaders_style_guide.rst:147
msgid ""
"Use one (and only one) blank line inside functions to separate logical "
"sections."
msgstr ""

#: ../../docs/tutorials/shaders/shaders_style_guide.rst:154
msgid ""
"If you can, try to keep lines under 80 characters. This helps to read the "
"code on small displays and with two shaders opened side-by-side in an "
"external text editor. For example, when looking at a differential revision."
msgstr ""

#: ../../docs/tutorials/shaders/shaders_style_guide.rst:161
msgid "Never combine multiple statements on a single line."
msgstr ""

#: ../../docs/tutorials/shaders/shaders_style_guide.rst:192
msgid ""
"Regular comments should start with a space, but not code that you comment "
"out. This helps differentiate text comments from disabled code."
msgstr ""

#: ../../docs/tutorials/shaders/shaders_style_guide.rst:209
msgid ""
"Don't use multiline comment syntax if your comment can fit on a single line:"
msgstr ""

#: ../../docs/tutorials/shaders/shaders_style_guide.rst:217
msgid ""
"In the shader editor, to make the selected code a comment (or uncomment it), "
"press :kbd:`Ctrl + K`. This feature adds or removes ``//`` at the start of "
"the selected lines."
msgstr ""

#: ../../docs/tutorials/shaders/shaders_style_guide.rst:224
msgid ""
"Always use one space around operators and after commas. Also, avoid "
"extraneous spaces in function calls."
msgstr ""

#: ../../docs/tutorials/shaders/shaders_style_guide.rst:251
msgid "Floating-point numbers"
msgstr ""

#: ../../docs/tutorials/shaders/shaders_style_guide.rst:253
msgid ""
"Always specify at least one digit for both the integer and fractional part. "
"This makes it easier to distinguish floating-point numbers from integers, as "
"well as distinguishing numbers greater than 1 from those lower than 1."
msgstr ""

#: ../../docs/tutorials/shaders/shaders_style_guide.rst:274
msgid "Accessing vector members"
msgstr ""

#: ../../docs/tutorials/shaders/shaders_style_guide.rst:276
msgid ""
"Use ``r``, ``g``, ``b``, and ``a`` when accessing a vector's members if it "
"contains a color. If the vector contains anything else than a color, use "
"``x``, ``y``, ``z``, and ``w``. This allows those reading your code to "
"better understand what the underlying data represents."
msgstr ""

#: ../../docs/tutorials/shaders/shaders_style_guide.rst:322
msgid "Preprocessor directives"
msgstr ""

#: ../../docs/tutorials/shaders/shaders_style_guide.rst:324
msgid ""
":ref:`doc_shader_preprocessor` directives should be written in "
"CONSTANT__CASE. Directives should be written without any indentation before "
"them, even if nested within a function."
msgstr ""

#: ../../docs/tutorials/shaders/shaders_style_guide.rst:328
msgid ""
"To preserve the natural flow of indentation when shader errors are printed "
"to the console, extra indentation should **not** be added within ``#if``, "
"``#ifdef`` or ``#ifndef`` blocks:"
msgstr ""

#: ../../docs/tutorials/shaders/shaders_style_guide.rst:363
msgid "We suggest to organize shader code this way:"
msgstr ""

#: ../../docs/tutorials/shaders/shaders_style_guide.rst:384
msgid "This code order follows two rules of thumb:"
msgstr ""

#: ../../docs/tutorials/shaders/shaders_style_guide.rst:386
msgid "Metadata and properties first, followed by methods."
msgstr ""

#: ../../docs/tutorials/shaders/shaders_style_guide.rst:387
msgid ""
"\"Public\" comes before \"private\". In a shader language's context, "
"\"public\" refers to what's easily adjustable by the user (uniforms)."
msgstr ""

#: ../../docs/tutorials/shaders/using_viewport_as_texture.rst:4
msgid "Using a Viewport as a texture"
msgstr ""

#: ../../docs/tutorials/shaders/using_viewport_as_texture.rst:9
msgid ""
"This tutorial will introduce you to using the :ref:`Viewport "
"<class_Viewport>` as a texture that can be applied to 3D objects. In order "
"to do so, it will walk you through the process of making a procedural planet "
"like the one below:"
msgstr ""

#: ../../docs/tutorials/shaders/using_viewport_as_texture.rst:15
msgid ""
"This tutorial does not cover how to code a dynamic atmosphere like the one "
"this planet has."
msgstr ""

#: ../../docs/tutorials/shaders/using_viewport_as_texture.rst:17
msgid ""
"This tutorial assumes you are familiar with how to set up a basic scene "
"including: a :ref:`Camera3D <class_Camera3D>`, a :ref:`light source "
"<class_OmniLight3D>`, a :ref:`MeshInstance3D <class_MeshInstance3D>` with a :"
"ref:`Primitive Mesh <class_PrimitiveMesh>`, and applying a :ref:"
"`StandardMaterial3D <class_StandardMaterial3D>` to the mesh. The focus will "
"be on using the :ref:`Viewport <class_Viewport>` to dynamically create "
"textures that can be applied to the mesh."
msgstr ""

#: ../../docs/tutorials/shaders/using_viewport_as_texture.rst:23
msgid "In this tutorial, we'll cover the following topics:"
msgstr ""

#: ../../docs/tutorials/shaders/using_viewport_as_texture.rst:25
msgid "How to use a :ref:`Viewport <class_Viewport>` as a render texture"
msgstr ""

#: ../../docs/tutorials/shaders/using_viewport_as_texture.rst:26
msgid "Mapping a texture to a sphere with equirectangular mapping"
msgstr ""

#: ../../docs/tutorials/shaders/using_viewport_as_texture.rst:27
msgid "Fragment shader techniques for procedural planets"
msgstr ""

#: ../../docs/tutorials/shaders/using_viewport_as_texture.rst:28
msgid ""
"Setting a Roughness map from a :ref:`Viewport Texture "
"<class_ViewportTexture>`"
msgstr ""

#: ../../docs/tutorials/shaders/using_viewport_as_texture.rst:31
msgid "Setting up the Viewport"
msgstr ""

#: ../../docs/tutorials/shaders/using_viewport_as_texture.rst:33
msgid "First, add a :ref:`Viewport <class_Viewport>` to the scene."
msgstr ""

#: ../../docs/tutorials/shaders/using_viewport_as_texture.rst:35
msgid ""
"Next, set the size of the :ref:`Viewport <class_Viewport>` to ``(1024, "
"512)``. The :ref:`Viewport <class_Viewport>` can actually be any size so "
"long as the width is double the height. The width needs to be double the "
"height so that the image will accurately map onto the sphere, as we will be "
"using equirectangular projection, but more on that later."
msgstr ""

#: ../../docs/tutorials/shaders/using_viewport_as_texture.rst:42
msgid ""
"Next, disable HDR and disable 3D. We don't need HDR because our planet's "
"surface will not be especially bright, so values between ``0`` and ``1`` "
"will be fine. And we will be using a :ref:`ColorRect <class_ColorRect>` to "
"render the surface, so we don't need 3D either."
msgstr ""

#: ../../docs/tutorials/shaders/using_viewport_as_texture.rst:46
msgid ""
"Select the Viewport and add a :ref:`ColorRect <class_ColorRect>` as a child."
msgstr ""

#: ../../docs/tutorials/shaders/using_viewport_as_texture.rst:48
msgid ""
"Set the anchors \"Right\" and \"Bottom\" to ``1``, then make sure all the "
"margins are set to ``0``. This will ensure that the :ref:`ColorRect "
"<class_ColorRect>` takes up the entire :ref:`Viewport <class_Viewport>`."
msgstr ""

#: ../../docs/tutorials/shaders/using_viewport_as_texture.rst:53
msgid ""
"Next, we add a :ref:`Shader Material <class_ShaderMaterial>` to the :ref:"
"`ColorRect <class_ColorRect>` (ColorRect > CanvasItem > Material > Material "
"> ``New ShaderMaterial``)."
msgstr ""

#: ../../docs/tutorials/shaders/using_viewport_as_texture.rst:55
msgid ""
"Basic familiarity with shading is recommended for this tutorial. However, "
"even if you are new to shaders, all the code will be provided, so you should "
"have no problem following along."
msgstr ""

#: ../../docs/tutorials/shaders/using_viewport_as_texture.rst:58
msgid ""
"ColorRect > CanvasItem > Material > Material > click / Edit > ShaderMaterial "
"> Shader > ``New Shader`` > click / Edit:"
msgstr ""

#: ../../docs/tutorials/shaders/using_viewport_as_texture.rst:68
msgid "The above code renders a gradient like the one below."
msgstr ""

#: ../../docs/tutorials/shaders/using_viewport_as_texture.rst:72
msgid ""
"Now we have the basics of a :ref:`Viewport <class_Viewport>` that we render "
"to and we have a unique image that we can apply to the sphere."
msgstr ""

#: ../../docs/tutorials/shaders/using_viewport_as_texture.rst:76
msgid "Applying the texture"
msgstr ""

#: ../../docs/tutorials/shaders/using_viewport_as_texture.rst:78
msgid ""
"MeshInstance3D > GeometryInstance > Geometry > Material Override > ``New "
"StandardMaterial3D``:"
msgstr ""

#: ../../docs/tutorials/shaders/using_viewport_as_texture.rst:80
msgid ""
"Now we go into the :ref:`MeshInstance3D <class_MeshInstance3D>` and add a :"
"ref:`StandardMaterial3D <class_StandardMaterial3D>` to it. No need for a "
"special :ref:`Shader Material <class_ShaderMaterial>` (although that would "
"be a good idea for more advanced effects, like the atmosphere in the example "
"above)."
msgstr ""

#: ../../docs/tutorials/shaders/using_viewport_as_texture.rst:84
msgid ""
"MeshInstance3D > GeometryInstance > Geometry > Material Override > "
"``click`` / ``Edit``:"
msgstr ""

#: ../../docs/tutorials/shaders/using_viewport_as_texture.rst:86
msgid ""
"Open the newly created :ref:`StandardMaterial3D <class_StandardMaterial3D>` "
"and scroll down to the \"Albedo\" section and click beside the \"Texture\" "
"property to add an Albedo Texture. Here we will apply the texture we made. "
"Choose \"New ViewportTexture\""
msgstr ""

#: ../../docs/tutorials/shaders/using_viewport_as_texture.rst:92
msgid ""
"Then, from the menu that pops up, select the Viewport that we rendered to "
"earlier."
msgstr ""

#: ../../docs/tutorials/shaders/using_viewport_as_texture.rst:96
msgid ""
"Your sphere should now be colored in with the colors we rendered to the "
"Viewport."
msgstr ""

#: ../../docs/tutorials/shaders/using_viewport_as_texture.rst:100
msgid ""
"Notice the ugly seam that forms where the texture wraps around? This is "
"because we are picking a color based on UV coordinates and UV coordinates do "
"not wrap around the texture. This is a classic problem in 2D map projection. "
"Game developers often have a 2-dimensional map they want to project onto a "
"sphere, but when it wraps around, it has large seams. There is an elegant "
"workaround for this problem that we will illustrate in the next section."
msgstr ""

#: ../../docs/tutorials/shaders/using_viewport_as_texture.rst:107
msgid "Making the planet texture"
msgstr ""

#: ../../docs/tutorials/shaders/using_viewport_as_texture.rst:109
msgid ""
"So now, when we render to our :ref:`Viewport <class_Viewport>`, it appears "
"magically on the sphere. But there is an ugly seam created by our texture "
"coordinates. So how do we get a range of coordinates that wrap around the "
"sphere in a nice way? One solution is to use a function that repeats on the "
"domain of our texture. ``sin`` and ``cos`` are two such functions. Let's "
"apply them to the texture and see what happens."
msgstr ""

#: ../../docs/tutorials/shaders/using_viewport_as_texture.rst:120
msgid ""
"Not too bad. If you look around, you can see that the seam has now "
"disappeared, but in its place, we have pinching at the poles. This pinching "
"is due to the way Godot maps textures to spheres in its :ref:"
"`StandardMaterial3D <class_StandardMaterial3D>`. It uses a projection "
"technique called equirectangular projection, which translates a spherical "
"map onto a 2D plane."
msgstr ""

#: ../../docs/tutorials/shaders/using_viewport_as_texture.rst:125
msgid ""
"If you are interested in a little extra information on the technique, we "
"will be converting from spherical coordinates into Cartesian coordinates. "
"Spherical coordinates map the longitude and latitude of the sphere, while "
"Cartesian coordinates are, for all intents and purposes, a vector from the "
"center of the sphere to the point."
msgstr ""

#: ../../docs/tutorials/shaders/using_viewport_as_texture.rst:130
msgid ""
"For each pixel, we will calculate its 3D position on the sphere. From that, "
"we will use 3D noise to determine a color value. By calculating the noise in "
"3D, we solve the problem of the pinching at the poles. To understand why, "
"picture the noise being calculated across the surface of the sphere instead "
"of across the 2D plane. When you calculate across the surface of the sphere, "
"you never hit an edge, and hence you never create a seam or a pinch point on "
"the pole. The following code converts the ``UVs`` into Cartesian coordinates."
msgstr ""

#: ../../docs/tutorials/shaders/using_viewport_as_texture.rst:149
msgid "And if we use ``unit`` as an output ``COLOR`` value, we get:"
msgstr ""

#: ../../docs/tutorials/shaders/using_viewport_as_texture.rst:153
msgid ""
"Now that we can calculate the 3D position of the surface of the sphere, we "
"can use 3D noise to make the planet. We will be using this noise function "
"directly from a `Shadertoy <https://www.shadertoy.com/view/Xsl3Dl>`_:"
msgstr ""

#: ../../docs/tutorials/shaders/using_viewport_as_texture.rst:181
msgid ""
"All credit goes to the author, Inigo Quilez. It is published under the "
"``MIT`` licence."
msgstr ""

#: ../../docs/tutorials/shaders/using_viewport_as_texture.rst:183
msgid ""
"Now to use ``noise``, add the following to the    ``fragment`` function:"
msgstr ""

#: ../../docs/tutorials/shaders/using_viewport_as_texture.rst:192
msgid "In order to highlight the texture, we set the material to unshaded."
msgstr ""

#: ../../docs/tutorials/shaders/using_viewport_as_texture.rst:194
msgid ""
"You can see now that the noise indeed wraps seamlessly around the sphere. "
"Although this looks nothing like the planet you were promised. So let's move "
"onto something more colorful."
msgstr ""

#: ../../docs/tutorials/shaders/using_viewport_as_texture.rst:198
msgid "Coloring the planet"
msgstr ""

#: ../../docs/tutorials/shaders/using_viewport_as_texture.rst:200
msgid ""
"Now to make the planet colors. While there are many ways to do this, for "
"now, we will stick with a gradient between water and land."
msgstr ""

#: ../../docs/tutorials/shaders/using_viewport_as_texture.rst:203
msgid ""
"To make a gradient in GLSL, we use the ``mix`` function. ``mix`` takes two "
"values to interpolate between and a third argument to choose how much to "
"interpolate between them; in essence, it *mixes* the two values together. In "
"other APIs, this function is often called ``lerp``. However, ``lerp`` is "
"typically reserved for mixing two floats together; ``mix`` can take any "
"values whether it be floats or vector types."
msgstr ""

#: ../../docs/tutorials/shaders/using_viewport_as_texture.rst:213
msgid ""
"The first color is blue for the ocean. The second color is a kind of reddish "
"color (because all alien planets need red terrain). And finally, they are "
"mixed together by ``n * 0.5 + 0.5``. ``n`` smoothly varies between ``-1`` "
"and ``1``. So we map it into the ``0-1`` range that ``mix`` expects. Now you "
"can see that the colors change between blue and red."
msgstr ""

#: ../../docs/tutorials/shaders/using_viewport_as_texture.rst:220
msgid ""
"That is a little more blurry than we want. Planets typically have a "
"relatively clear separation between land and sea. In order to do that, we "
"will change the last term to ``smoothstep(-0.1, 0.0, n)``. And thus the "
"whole line becomes:"
msgstr ""

#: ../../docs/tutorials/shaders/using_viewport_as_texture.rst:228
msgid ""
"What ``smoothstep`` does is return ``0`` if the third argument is below the "
"first and ``1`` if the third argument is larger than the second and smoothly "
"blends between ``0`` and ``1`` if the third number is between the first and "
"the second. So in this line, ``smoothstep`` returns ``0`` whenever ``n`` is "
"less than ``-0.1`` and it returns ``1`` whenever ``n`` is above ``0``."
msgstr ""

#: ../../docs/tutorials/shaders/using_viewport_as_texture.rst:235
msgid ""
"One more thing to make this a little more planet-y. The land shouldn't be so "
"blobby; let's make the edges a little rougher. A trick that is often used in "
"shaders to make rough looking terrain with noise is to layer levels of noise "
"over one another at various frequencies. We use one layer to make the "
"overall blobby structure of the continents. Then another layer breaks up the "
"edges a bit, and then another, and so on. What we will do is calculate ``n`` "
"with four lines of shader code instead of just one. ``n`` becomes:"
msgstr ""

#: ../../docs/tutorials/shaders/using_viewport_as_texture.rst:249
msgid "And now the planet looks like:"
msgstr ""

#: ../../docs/tutorials/shaders/using_viewport_as_texture.rst:253
msgid "And with shading turned back on, it looks like:"
msgstr ""

#: ../../docs/tutorials/shaders/using_viewport_as_texture.rst:258
msgid "Making an ocean"
msgstr ""

#: ../../docs/tutorials/shaders/using_viewport_as_texture.rst:260
msgid ""
"One final thing to make this look more like a planet. The ocean and the land "
"reflect light differently. So we want the ocean to shine a little more than "
"the land. We can do this by passing a fourth value into the ``alpha`` "
"channel of our output ``COLOR`` and using it as a Roughness map."
msgstr ""

#: ../../docs/tutorials/shaders/using_viewport_as_texture.rst:268
msgid ""
"This line returns ``0.3`` for water and ``1.0`` for land. This means that "
"the land is going to be quite rough, while the water will be quite smooth."
msgstr ""

#: ../../docs/tutorials/shaders/using_viewport_as_texture.rst:271
msgid ""
"And then, in the material, under the \"Metallic\" section, make sure "
"``Metallic`` is set to ``0`` and ``Specular`` is set to ``1``. The reason "
"for this is the water reflects light really well, but isn't metallic. These "
"values are not physically accurate, but they are good enough for this demo."
msgstr ""

#: ../../docs/tutorials/shaders/using_viewport_as_texture.rst:275
msgid ""
"Next, under the \"Roughness\" section, set ``Roughness`` to ``1`` and set "
"the roughness texture to a :ref:`Viewport Texture <class_ViewportTexture>` "
"pointing to our planet texture :ref:`Viewport <class_Viewport>`. Finally, "
"set the ``Texture Channel`` to ``Alpha``. This instructs the renderer to use "
"the ``alpha`` channel of our output ``COLOR`` as the ``Roughness`` value."
msgstr ""

#: ../../docs/tutorials/shaders/using_viewport_as_texture.rst:282
msgid ""
"You'll notice that very little changes except that the planet is no longer "
"reflecting the sky. This is happening because, by default, when something is "
"rendered with an alpha value, it gets drawn as a transparent object over the "
"background. And since the default background of the :ref:`Viewport "
"<class_Viewport>` is opaque, the ``alpha`` channel of the :ref:`Viewport "
"Texture <class_ViewportTexture>` is ``1``, resulting in the planet texture "
"being drawn with slightly fainter colors and a ``Roughness`` value of ``1`` "
"everywhere. To correct this, we go into the :ref:`Viewport <class_Viewport>` "
"and enable the \"Transparent Bg\" property. Since we are now rendering one "
"transparent object on top of another, we want to enable "
"``blend_premul_alpha``:"
msgstr ""

#: ../../docs/tutorials/shaders/using_viewport_as_texture.rst:295
msgid ""
"This pre-multiplies the colors by the ``alpha`` value and then blends them "
"correctly together. Typically, when blending one transparent color on top of "
"another, even if the background has an ``alpha`` of ``0`` (as it does in "
"this case), you end up with weird color bleed issues. Setting "
"``blend_premul_alpha`` fixes that."
msgstr ""

#: ../../docs/tutorials/shaders/using_viewport_as_texture.rst:299
msgid ""
"Now the planet should look like it is reflecting light on the ocean but not "
"the land. If you haven't done so already, add an :ref:`OmniLight3D "
"<class_OmniLight3D>` to the scene so you can move it around and see the "
"effect of the reflections on the ocean."
msgstr ""

#: ../../docs/tutorials/shaders/using_viewport_as_texture.rst:305
msgid ""
"And there you have it. A procedural planet generated using a :ref:`Viewport "
"<class_Viewport>`."
msgstr ""

#: ../../docs/tutorials/shaders/custom_postprocessing.rst:4
msgid "Custom post-processing"
msgstr ""

#: ../../docs/tutorials/shaders/custom_postprocessing.rst:9
msgid ""
"Godot provides many post-processing effects out of the box, including Bloom, "
"DOF, and SSAO, which are described in :ref:"
"`doc_environment_and_post_processing`. However, advanced use cases may "
"require custom effects. This article explains how to write your own custom "
"effects."
msgstr ""

#: ../../docs/tutorials/shaders/custom_postprocessing.rst:14
msgid ""
"The easiest way to implement a custom post-processing shader is to use "
"Godot's built-in ability to read from the screen texture. If you're not "
"familiar with this, you should read the :ref:`Screen Reading Shaders "
"Tutorial <doc_screen-reading_shaders>` first."
msgstr ""

#: ../../docs/tutorials/shaders/custom_postprocessing.rst:20
msgid "Single pass post-processing"
msgstr ""

#: ../../docs/tutorials/shaders/custom_postprocessing.rst:22
msgid ""
"Post-processing effects are shaders applied to a frame after Godot has "
"rendered it. To apply a shader to a frame, create a :ref:`CanvasLayer "
"<class_CanvasLayer>`, and give it a :ref:`ColorRect <class_ColorRect>`. "
"Assign a new :ref:`ShaderMaterial <class_ShaderMaterial>` to the newly "
"created ``ColorRect``, and set the ``ColorRect``'s layout to \"Full Rect\"."
msgstr ""

#: ../../docs/tutorials/shaders/custom_postprocessing.rst:28
#: ../../docs/tutorials/shaders/custom_postprocessing.rst:105
msgid "Your scene tree will look something like this:"
msgstr ""

#: ../../docs/tutorials/shaders/custom_postprocessing.rst:34
msgid ""
"Another more efficient method is to use a :ref:`BackBufferCopy "
"<class_BackBufferCopy>` to copy a region of the screen to a buffer and to "
"access it in a shader script through a ``sampler2D`` using "
"``hint_screen_texture``."
msgstr ""

#: ../../docs/tutorials/shaders/custom_postprocessing.rst:41
msgid ""
"As of the time of writing, Godot does not support rendering to multiple "
"buffers at the same time. Your post-processing shader will not have access "
"to other render passes and buffers not exposed by Godot (such as depth or "
"normal/roughness). You only have access to the rendered frame and buffers "
"exposed by Godot as samplers."
msgstr ""

#: ../../docs/tutorials/shaders/custom_postprocessing.rst:47
msgid ""
"For this demo, we will use this :ref:`Sprite <class_Sprite2D>` of a sheep."
msgstr ""

#: ../../docs/tutorials/shaders/custom_postprocessing.rst:51
msgid ""
"Assign a new :ref:`Shader <class_Shader>` to the ``ColorRect``'s "
"``ShaderMaterial``. You can access the frame's texture and UV with a "
"``sampler2D`` using ``hint_screen_texture`` and the built in ``SCREEN_UV`` "
"uniforms."
msgstr ""

#: ../../docs/tutorials/shaders/custom_postprocessing.rst:56
msgid ""
"Copy the following code to your shader. The code below is a hex pixelization "
"shader by `arlez80 <https://bitbucket.org/arlez80/hex-mosaic/src/master/>`_,"
msgstr ""

#: ../../docs/tutorials/shaders/custom_postprocessing.rst:87
msgid "The sheep will look something like this:"
msgstr ""

#: ../../docs/tutorials/shaders/custom_postprocessing.rst:92
msgid "Multi-pass post-processing"
msgstr ""

#: ../../docs/tutorials/shaders/custom_postprocessing.rst:94
msgid ""
"Some post-processing effects like blurs are resource intensive. You can make "
"them run a lot faster if you break them down in multiple passes. In a "
"multipass material, each pass takes the result from the previous pass as an "
"input and processes it."
msgstr ""

#: ../../docs/tutorials/shaders/custom_postprocessing.rst:99
msgid ""
"To produce a multi-pass post-processing shader, you stack ``CanvasLayer`` "
"and ``ColorRect`` nodes. In the example above, you use a ``CanvasLayer`` "
"object to render a shader using the frame on the layer below. Apart from the "
"node structure, the steps are the same as with the single-pass post-"
"processing shader."
msgstr ""

#: ../../docs/tutorials/shaders/custom_postprocessing.rst:109
msgid ""
"As an example, you could write a full screen Gaussian blur effect by "
"attaching the following pieces of code to each of the ``ColorRect`` nodes. "
"The order in which you apply the shaders depends on the position of the "
"``CanvasLayer`` in the scene tree, higher means sooner. For this blur "
"shader, the order does not matter."
msgstr ""

#: ../../docs/tutorials/shaders/custom_postprocessing.rst:155
msgid ""
"Using the above code, you should end up with a full screen blur effect like "
"below."
msgstr ""

#: ../../docs/tutorials/shaders/advanced_postprocessing.rst:4
msgid "Advanced post-processing"
msgstr ""

#: ../../docs/tutorials/shaders/advanced_postprocessing.rst:9
msgid ""
"This tutorial describes an advanced method for post-processing in Godot. In "
"particular, it will explain how to write a post-processing shader that uses "
"the depth buffer. You should already be familiar with post-processing "
"generally and, in particular, with the methods outlined in the :ref:`custom "
"post-processing tutorial <doc_custom_postprocessing>`."
msgstr ""

#: ../../docs/tutorials/shaders/advanced_postprocessing.rst:15
msgid "Full screen quad"
msgstr ""

#: ../../docs/tutorials/shaders/advanced_postprocessing.rst:17
msgid ""
"One way to make custom post-processing effects is by using a viewport. "
"However, there are two main drawbacks of using a Viewport:"
msgstr ""

#: ../../docs/tutorials/shaders/advanced_postprocessing.rst:20
msgid "The depth buffer cannot be accessed"
msgstr ""

#: ../../docs/tutorials/shaders/advanced_postprocessing.rst:21
msgid "The effect of the post-processing shader is not visible in the editor"
msgstr ""

#: ../../docs/tutorials/shaders/advanced_postprocessing.rst:23
msgid ""
"To get around the limitation on using the depth buffer, use a :ref:"
"`MeshInstance3D <class_MeshInstance3D>` with a :ref:`QuadMesh "
"<class_QuadMesh>` primitive. This allows us to use a shader and to access "
"the depth texture of the scene. Next, use a vertex shader to make the quad "
"cover the screen at all times so that the post-processing effect will be "
"applied at all times, including in the editor."
msgstr ""

#: ../../docs/tutorials/shaders/advanced_postprocessing.rst:29
msgid ""
"First, create a new MeshInstance3D and set its mesh to a QuadMesh. This "
"creates a quad centered at position ``(0, 0, 0)`` with a width and height of "
"``1``. Set the width and height to ``2`` and enable **Flip Faces**. Right "
"now, the quad occupies a position in world space at the origin. However, we "
"want it to move with the camera so that it always covers the entire screen. "
"To do this, we will bypass the coordinate transforms that translate the "
"vertex positions through the difference coordinate spaces and treat the "
"vertices as if they were already in clip space."
msgstr ""

#: ../../docs/tutorials/shaders/advanced_postprocessing.rst:38
msgid ""
"The vertex shader expects coordinates to be output in clip space, which are "
"coordinates ranging from ``-1`` at the left and bottom of the screen to "
"``1`` at the top and right of the screen. This is why the QuadMesh needs to "
"have height and width of ``2``. Godot handles the transform from model to "
"view space to clip space behind the scenes, so we need to nullify the "
"effects of Godot's transformations. We do this by setting the ``POSITION`` "
"built-in to our desired position. ``POSITION`` bypasses the built-in "
"transformations and sets the vertex position directly."
msgstr ""

#: ../../docs/tutorials/shaders/advanced_postprocessing.rst:54
msgid ""
"Even with this vertex shader, the quad keeps disappearing. This is due to "
"frustum culling, which is done on the CPU. Frustum culling uses the camera "
"matrix and the AABBs of Meshes to determine if the Mesh will be visible "
"*before* passing it to the GPU. The CPU has no knowledge of what we are "
"doing with the vertices, so it assumes the coordinates specified refer to "
"world positions, not clip space positions, which results in Godot culling "
"the quad when we turn away from the center of the scene. In order to keep "
"the quad from being culled, there are a few options:"
msgstr ""

#: ../../docs/tutorials/shaders/advanced_postprocessing.rst:62
msgid ""
"Add the QuadMesh as a child to the camera, so the camera is always pointed "
"at it"
msgstr ""

#: ../../docs/tutorials/shaders/advanced_postprocessing.rst:63
msgid ""
"Set the Geometry property ``extra_cull_margin`` as large as possible in the "
"QuadMesh"
msgstr ""

#: ../../docs/tutorials/shaders/advanced_postprocessing.rst:65
msgid ""
"The second option ensures that the quad is visible in the editor, while the "
"first option guarantees that it will still be visible even if the camera "
"moves outside the cull margin. You can also use both options."
msgstr ""

#: ../../docs/tutorials/shaders/advanced_postprocessing.rst:72
msgid ""
"To read from the depth texture, we first need to create a texture uniform "
"set to the depth buffer by using ``hint_depth_texture``."
msgstr ""

#: ../../docs/tutorials/shaders/advanced_postprocessing.rst:79
msgid ""
"Once defined, the depth texture can be read with the ``texture()`` function."
msgstr ""

#: ../../docs/tutorials/shaders/advanced_postprocessing.rst:85
msgid ""
"Similar to accessing the screen texture, accessing the depth texture is only "
"possible when reading from the current viewport. The depth texture cannot be "
"accessed from another viewport to which you have rendered."
msgstr ""

#: ../../docs/tutorials/shaders/advanced_postprocessing.rst:89
msgid ""
"The values returned by ``depth_texture`` are between ``0.0`` and ``1.0`` and "
"are nonlinear. When displaying depth directly from the ``depth_texture``, "
"everything will look almost white unless it is very close. This is because "
"the depth buffer stores objects closer to the camera using more bits than "
"those further, so most of the detail in depth buffer is found close to the "
"camera. In order to make the depth value align with world or model "
"coordinates, we need to linearize the value. When we apply the projection "
"matrix to the vertex position, the z value is made nonlinear, so to "
"linearize it, we multiply it by the inverse of the projection matrix, which "
"in Godot, is accessible with the variable ``INV_PROJECTION_MATRIX``."
msgstr ""

#: ../../docs/tutorials/shaders/advanced_postprocessing.rst:99
msgid ""
"Firstly, take the screen space coordinates and transform them into "
"normalized device coordinates (NDC). NDC run ``-1.0`` to ``1.0`` in ``x`` "
"and ``y`` directions and from ``0.0`` to ``1.0`` in the ``z`` direction when "
"using the Vulkan backend. Reconstruct the NDC using ``SCREEN_UV`` for the "
"``x`` and ``y`` axis, and the depth value for ``z``."
msgstr ""

#: ../../docs/tutorials/shaders/advanced_postprocessing.rst:107
msgid ""
"This tutorial assumes the use of the Vulkan renderer, which uses NDCs with a "
"Z-range of ``[0.0, 1.0]``. In contrast, OpenGL uses NDCs with a Z-range of "
"``[-1.0, 1.0]``."
msgstr ""

#: ../../docs/tutorials/shaders/advanced_postprocessing.rst:117
msgid ""
"Convert NDC to view space by multiplying the NDC by "
"``INV_PROJECTION_MATRIX``. Recall that view space gives positions relative "
"to the camera, so the ``z`` value will give us the distance to the point."
msgstr ""

#: ../../docs/tutorials/shaders/advanced_postprocessing.rst:130
msgid ""
"Because the camera is facing the negative ``z`` direction, the position will "
"have a negative ``z`` value. In order to get a usable depth value, we have "
"to negate ``view.z``."
msgstr ""

#: ../../docs/tutorials/shaders/advanced_postprocessing.rst:133
msgid ""
"The world position can be constructed from the depth buffer using the "
"following code. Note that the ``INV_VIEW_MATRIX`` is needed to transform the "
"position from view space into world space, so it needs to be passed to the "
"fragment shader with a varying."
msgstr ""

#: ../../docs/tutorials/shaders/advanced_postprocessing.rst:152
msgid "An optimization"
msgstr ""

#: ../../docs/tutorials/shaders/advanced_postprocessing.rst:154
msgid ""
"You can benefit from using a single large triangle rather than using a full "
"screen quad. The reason for this is explained `here <https://michaldrobot."
"com/2014/04/01/gcn-execution-patterns-in-full-screen-passes>`_. However, the "
"benefit is quite small and only beneficial when running especially complex "
"fragment shaders."
msgstr ""

#: ../../docs/tutorials/shaders/advanced_postprocessing.rst:159
msgid ""
"Set the Mesh in the MeshInstance3D to an :ref:`ArrayMesh <class_ArrayMesh>`. "
"An ArrayMesh is a tool that allows you to easily construct a Mesh from "
"Arrays for vertices, normals, colors, etc."
msgstr ""

#: ../../docs/tutorials/shaders/advanced_postprocessing.rst:163
msgid "Now, attach a script to the MeshInstance3D and use the following code:"
msgstr ""

#: ../../docs/tutorials/shaders/advanced_postprocessing.rst:185
msgid ""
"The triangle is specified in normalized device coordinates. Recall, NDC run "
"from ``-1.0`` to ``1.0`` in both the ``x`` and ``y`` directions. This makes "
"the screen ``2`` units wide and ``2`` units tall. In order to cover the "
"entire screen with a single triangle, use a triangle that is ``4`` units "
"wide and ``4`` units tall, double its height and width."
msgstr ""

#: ../../docs/tutorials/shaders/advanced_postprocessing.rst:192
msgid ""
"Assign the same vertex shader from above and everything should look exactly "
"the same."
msgstr ""

#: ../../docs/tutorials/shaders/advanced_postprocessing.rst:194
msgid ""
"The one drawback to using an ArrayMesh over using a QuadMesh is that the "
"ArrayMesh is not visible in the editor because the triangle is not "
"constructed until the scene is run. To get around that, construct a single "
"triangle Mesh in a modeling program and use that in the MeshInstance3D "
"instead."
msgstr ""

#: ../../docs/tutorials/shaders/making_trees.rst:4
msgid "Making trees"
msgstr ""

#: ../../docs/tutorials/shaders/making_trees.rst:6
msgid ""
"This is a short tutorial on how to make trees and other types of vegetation "
"from scratch."
msgstr ""

#: ../../docs/tutorials/shaders/making_trees.rst:8
msgid ""
"The aim is to not focus on the modeling techniques (there are plenty of "
"tutorials about that), but how to make them look good in Godot."
msgstr ""

#: ../../docs/tutorials/shaders/making_trees.rst:13
msgid "Start with a tree"
msgstr ""

#: ../../docs/tutorials/shaders/making_trees.rst:15
msgid "I took this tree from SketchFab:"
msgstr ""

#: ../../docs/tutorials/shaders/making_trees.rst:19
msgid "https://sketchfab.com/models/ea5e6ed7f9d6445ba69589d503e8cebf"
msgstr ""

#: ../../docs/tutorials/shaders/making_trees.rst:21
msgid "and opened it in Blender."
msgstr ""

#: ../../docs/tutorials/shaders/making_trees.rst:24
msgid "Paint with vertex colors"
msgstr ""

#: ../../docs/tutorials/shaders/making_trees.rst:26
msgid ""
"The first thing you may want to do is to use the vertex colors to paint how "
"much the tree will sway when there is wind. Just use the vertex color "
"painting tool of your favorite 3D modeling program and paint something like "
"this:"
msgstr ""

#: ../../docs/tutorials/shaders/making_trees.rst:30
msgid ""
"This is a bit exaggerated, but the idea is that color indicates how much "
"sway affects every part of the tree. This scale here represents it better:"
msgstr ""

#: ../../docs/tutorials/shaders/making_trees.rst:35
msgid "Write a custom shader for the leaves"
msgstr ""

#: ../../docs/tutorials/shaders/making_trees.rst:37
msgid "This is an example of a shader for leaves:"
msgstr ""

#: ../../docs/tutorials/shaders/making_trees.rst:44
msgid ""
"This is a spatial shader. There is no front/back culling (so leaves can be "
"seen from both sides), and alpha prepass is used, so there are less depth "
"artifacts that result from using transparency (and leaves cast shadow). "
"Finally, for the sway effect, world coordinates are recommended, so the tree "
"can be duplicated, moved, etc. and it will still work together with other "
"trees."
msgstr ""

#: ../../docs/tutorials/shaders/making_trees.rst:51
msgid ""
"Here, the texture is read, as well as a transmission color, which is used to "
"add some back-lighting to the leaves, simulating subsurface scattering."
msgstr ""

#: ../../docs/tutorials/shaders/making_trees.rst:67
msgid ""
"This is the code to create the sway of the leaves. It's basic (just uses a "
"sinewave multiplying by the time and axis position, but works well). Notice "
"that the strength is multiplied by the color. Every axis uses a different "
"small near 1.0 multiplication factor so axes don't appear in sync."
msgstr ""

#: ../../docs/tutorials/shaders/making_trees.rst:70
msgid "Finally, all that's left is the fragment shader:"
msgstr ""

#: ../../docs/tutorials/shaders/making_trees.rst:83
msgid "And this is pretty much it."
msgstr ""

#: ../../docs/tutorials/shaders/making_trees.rst:85
msgid ""
"The trunk shader is similar, except it does not write to the alpha channel "
"(thus no alpha prepass is needed) and does not require transmission to work. "
"Both shaders can be improved by adding normal mapping, AO and other maps."
msgstr ""

#: ../../docs/tutorials/shaders/making_trees.rst:88
msgid "Improving the shader"
msgstr ""

#: ../../docs/tutorials/shaders/making_trees.rst:90
msgid ""
"There are many more resources on how to do this that you can read. Now that "
"you know the basics, a recommended read is the chapter from GPU Gems3 about "
"how Crysis does this (focus mostly on the sway code, as many other "
"techniques shown there are obsolete):"
msgstr ""

#: ../../docs/tutorials/shaders/making_trees.rst:93
msgid "https://developer.nvidia.com/gpugems/GPUGems3/gpugems3_ch16.html"
msgstr ""

#: ../../docs/tutorials/ui/index.rst:4
msgid "User interface (UI)"
msgstr ""

#: ../../docs/tutorials/ui/index.rst:6
msgid ""
"In this section of the tutorial we explain the basics of creating a "
"graphical user interface (GUI) in Godot."
msgstr ""

#: ../../docs/tutorials/ui/index.rst:10
msgid "UI building blocks"
msgstr ""

#: ../../docs/tutorials/ui/index.rst:12
msgid ""
"Like everything else in Godot the user interface is built using nodes, "
"specifically :ref:`Control <class_Control>` nodes. There are many different "
"types of controls which are useful for creating specific types of GUIs. For "
"simplicity we can separate them into two groups: content and layout."
msgstr ""

#: ../../docs/tutorials/ui/index.rst:17
msgid "Typical content controls include:"
msgstr ""

#: ../../docs/tutorials/ui/index.rst:19
#, fuzzy
msgid ":ref:`Buttons <class_Button>`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/ui/index.rst:20
#, fuzzy
msgid ":ref:`Labels <class_Label>`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/ui/index.rst:21
msgid ":ref:`LineEdits <class_LineEdit>` and :ref:`TextEdits <class_TextEdit>`"
msgstr ""

#: ../../docs/tutorials/ui/index.rst:23
msgid "Typical layout controls include:"
msgstr ""

#: ../../docs/tutorials/ui/index.rst:25
#, fuzzy
msgid ":ref:`BoxContainers <class_BoxContainer>`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/ui/index.rst:26
#, fuzzy
msgid ":ref:`MarginContainers <class_MarginContainer>`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/ui/index.rst:27
#, fuzzy
msgid ":ref:`ScrollContainers <class_ScrollContainer>`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/ui/index.rst:28
#, fuzzy
msgid ":ref:`TabContainers <class_TabContainer>`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/ui/index.rst:29
#, fuzzy
msgid ":ref:`Popups <class_Popup>`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/ui/index.rst:31
msgid "The following pages explain the basics of using such controls."
msgstr ""

#: ../../docs/tutorials/ui/index.rst:44
msgid "GUI skinning and themes"
msgstr ""

#: ../../docs/tutorials/ui/index.rst:46
msgid ""
"Godot features an in-depth skinning/theming system for control nodes. The "
"pages in this section explain the benefits of that system and how to set it "
"up in your projects."
msgstr ""

#: ../../docs/tutorials/ui/index.rst:59
#, fuzzy
msgid "Control node tutorials"
msgstr "Tutorijali"

#: ../../docs/tutorials/ui/index.rst:61
msgid ""
"The following articles cover specific details of using particular control "
"nodes."
msgstr ""

#: ../../docs/tutorials/ui/size_and_anchors.rst:6
msgid "Size and anchors"
msgstr ""

#: ../../docs/tutorials/ui/size_and_anchors.rst:8
msgid ""
"If a game was always going to be run on the same device and at the same "
"resolution, positioning controls would be a simple matter of setting the "
"position and size of each one of them. Unfortunately, that is rarely the "
"case."
msgstr ""

#: ../../docs/tutorials/ui/size_and_anchors.rst:13
msgid ""
"Only TVs nowadays have a standard resolution and aspect ratio. Everything "
"else, from computer monitors to tablets, portable consoles and mobile phones "
"have different resolutions and aspect ratios."
msgstr ""

#: ../../docs/tutorials/ui/size_and_anchors.rst:17
msgid ""
"There are several ways to handle this, but for now, let's just imagine that "
"the screen resolution has changed and the controls need to be re-positioned. "
"Some will need to follow the bottom of the screen, others the top of the "
"screen, or maybe the right or left margins."
msgstr ""

#: ../../docs/tutorials/ui/size_and_anchors.rst:24
msgid ""
"This is done by editing the *margin* properties of controls. Each control "
"has four margins: left, right, bottom, and top, which correspond to the "
"respective edges of the control. By default, all of them represent a "
"distance in pixels relative to the top-left corner of the parent control or "
"(in case there is no parent control) the viewport."
msgstr ""

#: ../../docs/tutorials/ui/size_and_anchors.rst:32
msgid ""
"So to make the control wider you can make the right margin larger and/or "
"make the left margin smaller. This lets you set the exact placement and "
"shape of the control."
msgstr ""

#: ../../docs/tutorials/ui/size_and_anchors.rst:36
msgid ""
"The *anchor* properties adjust where the margin distances are relative *to*. "
"Each margin has an individual anchor that can be adjusted from the beginning "
"to the end of the parent. So the vertical (top, bottom) anchors adjust from "
"0 (top of parent) to 1.0 (bottom of parent) with 0.5 being the center, and "
"the control margins will be placed relative to that point. The horizontal "
"(left, right) anchors similarly adjust from left to right of the parent."
msgstr ""

#: ../../docs/tutorials/ui/size_and_anchors.rst:44
msgid ""
"Note that when you wish the edge of a control to be above or left of the "
"anchor point, you must change the margin value to be negative."
msgstr ""

#: ../../docs/tutorials/ui/size_and_anchors.rst:47
msgid ""
"For example: when horizontal anchors are changed to 1, the margin values "
"become relative to the top-right corner of the parent control or viewport."
msgstr ""

#: ../../docs/tutorials/ui/size_and_anchors.rst:52
msgid ""
"Adjusting the two horizontal or the two vertical anchors to different values "
"will make the control change size when the parent control does. Here, the "
"control is set to anchor its bottom-right corner to the parent's bottom-"
"right, while the top-left control margins are still anchored to the top-left "
"of the parent, so when re-sizing the parent, the control will always cover "
"it, leaving a 20 pixel margin:"
msgstr ""

#: ../../docs/tutorials/ui/size_and_anchors.rst:62
#, fuzzy
msgid "Centering a control"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/ui/size_and_anchors.rst:64
msgid ""
"To center a control in its parent, set its anchors to 0.5 and each margin to "
"half of its relevant dimension. For example, the code below shows how a "
"TextureRect can be centered in its parent:"
msgstr ""

#: ../../docs/tutorials/ui/size_and_anchors.rst:102
msgid ""
"Setting each anchor to 0.5 moves the reference point for the margins to the "
"center of its parent. From there, we set negative margins so that the "
"control gets its natural size."
msgstr ""

#: ../../docs/tutorials/ui/size_and_anchors.rst:107
msgid "Layout Presets"
msgstr ""

#: ../../docs/tutorials/ui/size_and_anchors.rst:109
msgid ""
"Instead of manually adjusting the margin and anchor values, you can use the "
"toolbar's Layout menu, above the viewport. Besides centering, it gives you "
"many options to align and resize control nodes."
msgstr ""

#: ../../docs/tutorials/ui/gui_containers.rst:6
#, fuzzy
msgid "Using Containers"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/ui/gui_containers.rst:8
msgid ""
":ref:`Anchors <doc_size_and_anchors>` are an efficient way to handle "
"different aspect ratios for basic multiple resolution handling in GUIs."
msgstr ""

#: ../../docs/tutorials/ui/gui_containers.rst:11
msgid "For more complex user interfaces, they can become difficult to use."
msgstr ""

#: ../../docs/tutorials/ui/gui_containers.rst:13
msgid ""
"This is often the case of games, such as RPGs, online chats, tycoons or "
"simulations. Another common case where more advanced layout features may be "
"required is in-game tools (or simply just tools)."
msgstr ""

#: ../../docs/tutorials/ui/gui_containers.rst:16
msgid ""
"All these situations require a more capable OS-like user interface, with "
"advanced layout and formatting. For that, :ref:`Containers "
"<class_container>` are more useful."
msgstr ""

#: ../../docs/tutorials/ui/gui_containers.rst:20
msgid "Container layout"
msgstr ""

#: ../../docs/tutorials/ui/gui_containers.rst:22
msgid ""
"Containers provide a huge amount of layout power (as an example, the Godot "
"editor user interface is entirely done using them):"
msgstr ""

#: ../../docs/tutorials/ui/gui_containers.rst:26
msgid ""
"When a :ref:`Container <class_Container>`-derived node is used, all "
"children :ref:`Control <class_Control>` nodes give up their own positioning "
"ability. This means the *Container* will control their positioning and any "
"attempt to manually alter these nodes will be either ignored or invalidated "
"the next time their parent is resized."
msgstr ""

#: ../../docs/tutorials/ui/gui_containers.rst:30
msgid ""
"Likewise, when a *Container* derived node is resized, all its children will "
"be re-positioned according to it, with a behavior based on the type of "
"container used:"
msgstr ""

#: ../../docs/tutorials/ui/gui_containers.rst:35
msgid "Example of *HBoxContainer* resizing children buttons."
msgstr ""

#: ../../docs/tutorials/ui/gui_containers.rst:37
msgid ""
"The real strength of containers is that they can be nested (as nodes), "
"allowing the creation of very complex layouts that resize effortlessly."
msgstr ""

#: ../../docs/tutorials/ui/gui_containers.rst:40
#, fuzzy
msgid "Sizing options"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/ui/gui_containers.rst:42
msgid ""
"When adding a node to a container, the way the container treats each child "
"depends mainly on their *container sizing options*. These options can be "
"found by inspecting the layout of any *Control* that is a child of a "
"*Container*."
msgstr ""

#: ../../docs/tutorials/ui/gui_containers.rst:47
msgid ""
"Sizing options are independent for vertical and horizontal sizing and not "
"all containers make use of them (but most do):"
msgstr ""

#: ../../docs/tutorials/ui/gui_containers.rst:49
msgid ""
"**Fill**: Ensures the control *fills* the designated area within the "
"container. No matter if a control *expands* or not (see below), it will only "
"*fill* the designated area when this is toggled on (it is by default)."
msgstr ""

#: ../../docs/tutorials/ui/gui_containers.rst:51
msgid ""
"**Expand**: Attempts to use as much space as possible in the parent "
"container (in each axis). Controls that don't expand will be pushed away by "
"those that do. Between expanding controls, the amount of space they take "
"from each other is determined by the *Stretch Ratio* (see below). This "
"option is only available when the parent Container is of the right type, for "
"example the *HBoxContainer* has this option for horizontal sizing."
msgstr ""

#: ../../docs/tutorials/ui/gui_containers.rst:56
msgid ""
"**Shrink Begin** When expanding, try to remain at the left or top of the "
"expanded area."
msgstr ""

#: ../../docs/tutorials/ui/gui_containers.rst:58
msgid ""
"**Shrink Center** When expanding, try to remain at the center of the "
"expanded area."
msgstr ""

#: ../../docs/tutorials/ui/gui_containers.rst:60
msgid ""
"**Shrink End** When expanding, try to remain at the right or bottom of the "
"expanded area."
msgstr ""

#: ../../docs/tutorials/ui/gui_containers.rst:62
msgid ""
"**Stretch Ratio**: The ratio of how much expanded controls take up the "
"available space in relation to each other. A control with \"2\", will take "
"up twice as much available space as one with \"1\"."
msgstr ""

#: ../../docs/tutorials/ui/gui_containers.rst:65
msgid ""
"Experimenting with these flags and different containers is recommended to "
"get a better grasp on how they work."
msgstr ""

#: ../../docs/tutorials/ui/gui_containers.rst:68
msgid "Container types"
msgstr ""

#: ../../docs/tutorials/ui/gui_containers.rst:70
msgid ""
"Godot provides several container types out of the box as they serve "
"different purposes:"
msgstr ""

#: ../../docs/tutorials/ui/gui_containers.rst:73
msgid "Box Containers"
msgstr ""

#: ../../docs/tutorials/ui/gui_containers.rst:75
msgid ""
"Arranges child controls vertically or horizontally (via :ref:`HBoxContainer "
"<class_HBoxContainer>` and :ref:`VBoxContainer <class_VBoxContainer>`). In "
"the opposite of the designated direction (as in, vertical for an horizontal "
"container), it just expands the children."
msgstr ""

#: ../../docs/tutorials/ui/gui_containers.rst:81
msgid ""
"These containers make use of the *Ratio* property for children with the "
"*Expand* flag set."
msgstr ""

#: ../../docs/tutorials/ui/gui_containers.rst:84
msgid "Grid Container"
msgstr ""

#: ../../docs/tutorials/ui/gui_containers.rst:86
msgid ""
"Arranges child controls in a grid layout (via :ref:`GridContainer "
"<class_GridContainer>`, amount of columns must be specified). Uses both the "
"vertical and horizontal expand flags."
msgstr ""

#: ../../docs/tutorials/ui/gui_containers.rst:92
msgid "Margin Container"
msgstr ""

#: ../../docs/tutorials/ui/gui_containers.rst:94
msgid ""
"Child controls are expanded towards the bounds of this control (via :ref:"
"`MarginContainer <class_MarginContainer>`). Padding will be added on the "
"margins depending on the theme configuration."
msgstr ""

#: ../../docs/tutorials/ui/gui_containers.rst:100
msgid ""
"Again, keep in mind that the margins are a *Theme* value, so they need to be "
"edited from the constants overrides section of each control:"
msgstr ""

#: ../../docs/tutorials/ui/gui_containers.rst:106
msgid "Tab Container"
msgstr ""

#: ../../docs/tutorials/ui/gui_containers.rst:108
msgid ""
"Allows you to place several child controls stacked on top of each other "
"(via :ref:`TabContainer <class_TabContainer>`), with only the *current* one "
"visible."
msgstr ""

#: ../../docs/tutorials/ui/gui_containers.rst:113
msgid ""
"Changing the *current* one is done via tabs located at the top of the "
"container, via clicking:"
msgstr ""

#: ../../docs/tutorials/ui/gui_containers.rst:117
msgid ""
"The titles are generated from the node names by default (although they can "
"be overridden via *TabContainer* API)."
msgstr ""

#: ../../docs/tutorials/ui/gui_containers.rst:119
msgid ""
"Settings such as tab placement and *StyleBox* can be modified in the "
"*TabContainer* theme overrides."
msgstr ""

#: ../../docs/tutorials/ui/gui_containers.rst:122
msgid "Split Container"
msgstr ""

#: ../../docs/tutorials/ui/gui_containers.rst:124
msgid ""
"Accepts only one or two children controls, then places them side to side "
"with a divisor (via :ref:`HSplitContainer <class_HSplitContainer>` and :ref:"
"`VSplitContainer <class_VSplitContainer>`). Respects both horizontal and "
"vertical flags, as well as *Ratio*."
msgstr ""

#: ../../docs/tutorials/ui/gui_containers.rst:130
msgid ""
"The divisor can be dragged around to change the size relation between both "
"children:"
msgstr ""

#: ../../docs/tutorials/ui/gui_containers.rst:136
msgid "PanelContainer"
msgstr ""

#: ../../docs/tutorials/ui/gui_containers.rst:138
msgid ""
"A container that draws a *StyleBox*, then expands children to cover its "
"whole area (via :ref:`PanelContainer <class_PanelContainer>`, respecting the "
"*StyleBox* margins). It respects both the horizontal and vertical sizing "
"options."
msgstr ""

#: ../../docs/tutorials/ui/gui_containers.rst:144
msgid ""
"This container is useful as top-level, or just to add custom backgrounds to "
"sections of a layout."
msgstr ""

#: ../../docs/tutorials/ui/gui_containers.rst:147
msgid "ScrollContainer"
msgstr ""

#: ../../docs/tutorials/ui/gui_containers.rst:149
msgid ""
"Accepts a single child node. If this node is bigger than the container, "
"scrollbars will be added to allow panning the node around (via :ref:"
"`ScrollContainer <class_ScrollContainer>`). Both vertical and horizontal "
"size options are respected, and the behavior can be turned on or off per "
"axis in the properties."
msgstr ""

#: ../../docs/tutorials/ui/gui_containers.rst:156
msgid ""
"Mouse wheel and touch drag (when touch is available) are also valid ways to "
"pan the child control around."
msgstr ""

#: ../../docs/tutorials/ui/gui_containers.rst:160
msgid ""
"As in the example above, one of the most common ways to use this container "
"is together with a *VBoxContainer* as child."
msgstr ""

#: ../../docs/tutorials/ui/gui_containers.rst:163
#, fuzzy
msgid "AspectRatioContainer"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/ui/gui_containers.rst:165
msgid ""
"A container type that arranges its child controls in a way that preserves "
"their proportions automatically when the container is resized. (via :ref:"
"`AspectRatioContainer <class_AspectRatioContainer>`). It has multiple "
"stretch modes, providing options for adjusting the child controls' sizes "
"concerning the container: \"fill,\" \"width control height,\" \"height "
"control width,\" and \"cover.\""
msgstr ""

#: ../../docs/tutorials/ui/gui_containers.rst:173
msgid ""
"useful when you have a container that needs to be dynamic and responsive to "
"different screen sizes, and you want the child elements to scale "
"proportionally without losing their intended shapes."
msgstr ""

#: ../../docs/tutorials/ui/gui_containers.rst:179
#, fuzzy
msgid "FlowContainer"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/ui/gui_containers.rst:181
msgid ""
"FlowContainer is a container that arranges its child controls either "
"horizontally or vertically, (via :ref:`HFlowContainer "
"<class_HFlowContainer>` and via :ref:`VFlowContainer "
"<class_VFlowContainer>`). and when the available space runs out, it wraps "
"the children to the next line or column, similar to how text wraps in a book."
msgstr ""

#: ../../docs/tutorials/ui/gui_containers.rst:188
msgid ""
"useful for creating flexible layouts where the child controls adjust "
"automatically to the available space without overlapping."
msgstr ""

#: ../../docs/tutorials/ui/gui_containers.rst:193
#, fuzzy
msgid "CenterContainer"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/ui/gui_containers.rst:195
msgid ""
"CenterContainer is a container that automatically keeps all of its child "
"controls centered within it at their minimum size. It ensures that the child "
"controls are always aligned to the center, making it easier to create "
"centered layouts without manual positioning. (via :ref:`CenterContainer "
"<class_CenterContainer>`)."
msgstr ""

#: ../../docs/tutorials/ui/gui_containers.rst:206
msgid ""
"This is a special control that will only accept a single *Viewport* node as "
"child, and it will display it as if it was an image (via :ref:"
"`SubViewportContainer <class_SubViewportContainer>`)."
msgstr ""

#: ../../docs/tutorials/ui/gui_containers.rst:210
#, fuzzy
msgid "Creating custom Containers"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/ui/gui_containers.rst:212
msgid ""
"It is possible to create a custom container using a script. Here is an "
"example of a container that fits children to its rect size:"
msgstr ""

#: ../../docs/tutorials/ui/custom_gui_controls.rst:6
msgid "Custom GUI controls"
msgstr ""

#: ../../docs/tutorials/ui/custom_gui_controls.rst:9
msgid "So many controls..."
msgstr ""

#: ../../docs/tutorials/ui/custom_gui_controls.rst:11
msgid ""
"Yet there are never enough. Creating your own custom controls that act just "
"the way you want them to is an obsession of almost every GUI programmer. "
"Godot provides plenty of them, but they may not work exactly the way you "
"want. Before contacting the developers with a pull-request to support "
"diagonal scrollbars, at least it will be good to know how to create these "
"controls easily from script."
msgstr ""

#: ../../docs/tutorials/ui/custom_gui_controls.rst:21
msgid ""
"For drawing, it is recommended to check the :ref:`doc_custom_drawing_in_2d` "
"tutorial. The same applies. Some functions are worth mentioning due to their "
"usefulness when drawing, so they will be detailed next:"
msgstr ""

#: ../../docs/tutorials/ui/custom_gui_controls.rst:26
msgid "Checking control size"
msgstr ""

#: ../../docs/tutorials/ui/custom_gui_controls.rst:28
msgid ""
"Unlike 2D nodes, \"size\" is important with controls, as it helps to "
"organize them in proper layouts. For this, the :ref:`Control.size "
"<class_Control_property_size>` property is provided. Checking it during "
"``_draw()`` is vital to ensure everything is kept in-bounds."
msgstr ""

#: ../../docs/tutorials/ui/custom_gui_controls.rst:35
msgid "Checking focus"
msgstr ""

#: ../../docs/tutorials/ui/custom_gui_controls.rst:37
msgid ""
"Some controls (such as buttons or text editors) might provide input focus "
"for keyboard or joypad input. Examples of this are entering text or pressing "
"a button. This is controlled with the :ref:`Control.focus_mode "
"<class_Control_property_focus_mode>` property. When drawing, and if the "
"control supports input focus, it is always desired to show some sort of "
"indicator (highlight, box, etc.) to indicate that this is the currently "
"focused control. To check for this status, the :ref:`Control.has_focus() "
"<class_Control_method_has_focus>` method exists. Example"
msgstr ""

#: ../../docs/tutorials/ui/custom_gui_controls.rst:71
msgid "Sizing"
msgstr ""

#: ../../docs/tutorials/ui/custom_gui_controls.rst:73
msgid ""
"As mentioned before, size is important to controls. This allows them to lay "
"out properly, when set into grids, containers, or anchored. Controls, most "
"of the time, provide a *minimum size* to help properly lay them out. For "
"example, if controls are placed vertically on top of each other using a :ref:"
"`VBoxContainer <class_VBoxContainer>`, the minimum size will make sure your "
"custom control is not squished by the other controls in the container."
msgstr ""

#: ../../docs/tutorials/ui/custom_gui_controls.rst:81
msgid ""
"To provide this callback, just override :ref:`Control._get_minimum_size() "
"<class_Control_private_method__get_minimum_size>`, for example:"
msgstr ""

#: ../../docs/tutorials/ui/custom_gui_controls.rst:98
msgid "Alternatively, set it using a function:"
msgstr ""

#: ../../docs/tutorials/ui/custom_gui_controls.rst:116
msgid ""
"Controls provide a few helpers to make managing input events much easier "
"than regular nodes."
msgstr ""

#: ../../docs/tutorials/ui/custom_gui_controls.rst:122
msgid ""
"There are a few tutorials about input before this one, but it's worth "
"mentioning that controls have a special input method that only works when:"
msgstr ""

#: ../../docs/tutorials/ui/custom_gui_controls.rst:126
msgid "The mouse pointer is over the control."
msgstr ""

#: ../../docs/tutorials/ui/custom_gui_controls.rst:127
msgid ""
"The button was pressed over this control (control always captures input "
"until button is released)"
msgstr ""

#: ../../docs/tutorials/ui/custom_gui_controls.rst:129
msgid ""
"Control provides keyboard/joypad focus via :ref:`Control.focus_mode "
"<class_Control_property_focus_mode>`."
msgstr ""

#: ../../docs/tutorials/ui/custom_gui_controls.rst:132
msgid ""
"This function is :ref:`Control._gui_input() "
"<class_Control_private_method__gui_input>`. Simply override it in your "
"control. No processing needs to be set."
msgstr ""

#: ../../docs/tutorials/ui/custom_gui_controls.rst:155
msgid ""
"For more information about events themselves, check the :ref:"
"`doc_inputevent` tutorial."
msgstr ""

#: ../../docs/tutorials/ui/custom_gui_controls.rst:159
#: ../../docs/contributing/development/core_and_modules/object_class.rst:245
msgid "Notifications"
msgstr ""

#: ../../docs/tutorials/ui/custom_gui_controls.rst:161
msgid ""
"Controls also have many useful notifications for which no dedicated callback "
"exists, but which can be checked with the _notification callback:"
msgstr ""

#: ../../docs/tutorials/ui/gui_navigation.rst:4
msgid "Keyboard/Controller Navigation and Focus"
msgstr ""

#: ../../docs/tutorials/ui/gui_navigation.rst:6
msgid ""
"It is a common requirement for a user interface to have full keyboard and "
"controller support for navigation and interaction. There are two main "
"reasons why this is beneficial for projects: improved accessibility (not "
"everyone can use mouse or touch controls for interactions), and getting your "
"project ready for :ref:`consoles <doc_consoles>` (or just for people who "
"prefer to game with a controller on PC)."
msgstr ""

#: ../../docs/tutorials/ui/gui_navigation.rst:13
msgid ""
"Navigating between UI elements with keyboard or controller is done by "
"changing which node is actively selected. This is also called changing UI "
"focus. Every :ref:`Control <class_Control>` node in Godot is capable of "
"having focus. By default, some control nodes have the ability to "
"automatically grab focus reacting to built-in UI actions such as ``ui_up``, "
"``ui_down``, ``ui_focus_next``, etc. These actions can be seen in the "
"project settings in the input map and can be modified."
msgstr ""

#: ../../docs/tutorials/ui/gui_navigation.rst:22
msgid ""
"Because these actions are used for focus they should not be used for any "
"gameplay code."
msgstr ""

#: ../../docs/tutorials/ui/gui_navigation.rst:26
#, fuzzy
msgid "Node settings"
msgstr "Uvod / Početak"

#: ../../docs/tutorials/ui/gui_navigation.rst:28
msgid ""
"In addition to the built-in logic, you can define what is known as focus "
"neighbors for each individual control node. This allows to finely tune the "
"path the UI focus takes across the user interface of your project. The "
"settings for individual nodes can be found in the Inspector dock, under the "
"\"Focus\" category of the \"Control\" section."
msgstr ""

#: ../../docs/tutorials/ui/gui_navigation.rst:36
msgid ""
"Neighbor options are used to define nodes for 4-directional navigation, such "
"as using arrow keys or a D-pad on a controller. For example, the bottom "
"neighbor will be used when navigating down with the down arrow or by pushing "
"down on the D-pad. The \"Next\" and \"Previous\" options are used with the "
"focus shift button, such as :kbd:`Tab` on desktop operating systems."
msgstr ""

#: ../../docs/tutorials/ui/gui_navigation.rst:43
msgid "A node can lose focus if it becomes hidden."
msgstr ""

#: ../../docs/tutorials/ui/gui_navigation.rst:45
msgid ""
"The mode setting defines how a node can be focused. **All** means a node can "
"be focused by clicking on it with the mouse, or selecting it with a keyboard "
"or controller. **Click** means it can only be focused on by clicking on it. "
"Finally, **None** means it can't be focused at all. Different control nodes "
"have different default settings for this based on how they are typically "
"used, for example, :ref:`Label <class_Label>` nodes are set to \"None\" by "
"default, while :ref:`buttons <class_Button>` are set to \"All\"."
msgstr ""

#: ../../docs/tutorials/ui/gui_navigation.rst:53
msgid ""
"Make sure to properly configure your scenes for focus and navigation. If a "
"node has no focus neighbor configured, the engine will try to guess the next "
"control automatically. This may result in unintended behavior, especially in "
"a complex user interface that doesn't have well-defined vertical or "
"horizontal navigation flow."
msgstr ""

#: ../../docs/tutorials/ui/gui_navigation.rst:59
msgid "Necessary code"
msgstr ""

#: ../../docs/tutorials/ui/gui_navigation.rst:61
msgid ""
"For keyboard and controller navigation to work correctly, any node must be "
"focused on using code when the scene starts. Without doing this, pressing "
"buttons or keys won't do anything. Here is a basic example of setting "
"initial focus with code:"
msgstr ""

#: ../../docs/tutorials/ui/gui_navigation.rst:78
msgid ""
"Now when the scene starts the \"Start Button\" node will be focused, and the "
"keyboard or a controller can be used to navigate between it and other UI "
"elements."
msgstr ""

#: ../../docs/tutorials/ui/control_node_gallery.rst:4
msgid "Control node gallery"
msgstr ""

#: ../../docs/tutorials/ui/control_node_gallery.rst:6
msgid "Here is a list of common Control nodes with their name next to them:"
msgstr ""

#: ../../docs/tutorials/ui/control_node_gallery.rst:10
#, fuzzy
msgid ""
"The Control Gallery demo pictured above can be found `on GitHub <https://"
"github.com/godotengine/godot-demo-projects/tree/master/gui/"
"control_gallery>`__."
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati različite Godo demo projekte "
"`Godot demo projects <https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/tutorials/ui/gui_skinning.rst:4
#, fuzzy
msgid "Introduction to GUI skinning"
msgstr "Uvod"

#: ../../docs/tutorials/ui/gui_skinning.rst:6
msgid ""
"It is essential for a game to provide clear, informative, and yet visually "
"pleasing user interface to its players. While :ref:`Control <class_Control>` "
"nodes come with a decently functional look out of the box, there is always "
"room for uniqueness and case-specific tuning. For this purpose Godot engine "
"includes a system for GUI skinning (or theming), which allows you to "
"customize the look of every control in your user interface, including your "
"custom controls."
msgstr ""

#: ../../docs/tutorials/ui/gui_skinning.rst:13
msgid ""
"Here is an example of this system in action — a game with the GUI that is "
"radically different from the default UI theme of the engine:"
msgstr ""

#: ../../docs/tutorials/ui/gui_skinning.rst:19
msgid "A \"Gear Up!\" screen in Tank Kings, courtesy of Winterpixel Games"
msgstr ""

#: ../../docs/tutorials/ui/gui_skinning.rst:21
msgid ""
"Beyond achieving a unique look for your game, this system also enables "
"developers to provide customization options to the end users, including "
"accessibility settings. UI themes are applied in a cascading manner (i.e. "
"they propagate from parent controls to their children), which means that "
"font settings or adjustments for colorblind users can be applied in a single "
"place and affect the entire UI tree. Of course this system can also be used "
"for gameplay purposes: your hero-based game can change its style for the "
"selected player character, or you can give different flavors to the sides in "
"your team-based project."
msgstr ""

#: ../../docs/tutorials/ui/gui_skinning.rst:31
msgid "Basics of themes"
msgstr ""

#: ../../docs/tutorials/ui/gui_skinning.rst:33
msgid ""
"The skinning system is driven by the :ref:`Theme <class_Theme>` resource. "
"Every Godot project has an inherent default theme that contains the settings "
"used by the built-in control nodes. This is what gives the controls their "
"distinct look out of the box. A theme only describes the configuration, "
"however, and it is still the job of each individual control to use that "
"configuration in the way it requires to display itself. This is important to "
"remember when implementing :ref:`your own custom controls "
"<doc_custom_gui_controls>`."
msgstr ""

#: ../../docs/tutorials/ui/gui_skinning.rst:42
msgid ""
"Even the Godot editor itself relies on the default theme. But it doesn't "
"look the same as a Godot project, because it applies its own heavily "
"customized theme on top of the default one. In principle, this works exactly "
"like it would in your game as explained :ref:`below "
"<doc_gui_theme_in_project>`."
msgstr ""

#: ../../docs/tutorials/ui/gui_skinning.rst:48
msgid "Theme items"
msgstr ""

#: ../../docs/tutorials/ui/gui_skinning.rst:50
msgid ""
"The configuration that is stored in a theme consists of theme items. Each "
"item has a unique name and must be one of the following data types:"
msgstr ""

#: ../../docs/tutorials/ui/gui_skinning.rst:53
#, fuzzy
msgid "**Color**"
msgstr "**Za uređivač:**"

#: ../../docs/tutorials/ui/gui_skinning.rst:55
msgid ""
"A :ref:`color <class_Color>` value, which is often used for fonts and "
"backgrounds. Colors can also be used for modulation of controls and icons."
msgstr ""

#: ../../docs/tutorials/ui/gui_skinning.rst:59
msgid "**Constant**"
msgstr ""

#: ../../docs/tutorials/ui/gui_skinning.rst:61
msgid ""
"An integer value, which can be used either for numeric properties of "
"controls (such as the item separation in a :ref:`BoxContainer "
"<class_BoxContainer>`), or for boolean flags (such as the drawing of "
"relationship lines in a :ref:`Tree <class_Tree>`)."
msgstr ""

#: ../../docs/tutorials/ui/gui_skinning.rst:67
msgid ""
"A :ref:`font <class_Font>` resource, which is used by controls that display "
"text. Fonts contain most text rendering settings, except for its size and "
"color. On top of that, alignment and text direction are controlled by "
"individual controls."
msgstr ""

#: ../../docs/tutorials/ui/gui_skinning.rst:72
msgid "**Font size**"
msgstr ""

#: ../../docs/tutorials/ui/gui_skinning.rst:74
msgid ""
"An integer value, which is used alongside a font to determine the size at "
"which the text should be displayed."
msgstr ""

#: ../../docs/tutorials/ui/gui_skinning.rst:77
msgid "**Icon**"
msgstr ""

#: ../../docs/tutorials/ui/gui_skinning.rst:79
msgid ""
"A :ref:`texture <class_Texture2D>` resource, which is normally used to "
"display an icon (on a :ref:`Button <class_Button>`, for example)."
msgstr ""

#: ../../docs/tutorials/ui/gui_skinning.rst:82
msgid "**StyleBox**"
msgstr ""

#: ../../docs/tutorials/ui/gui_skinning.rst:84
msgid ""
"A :ref:`StyleBox <class_StyleBox>` resource, a collection of configuration "
"options which define the way a UI panel should be displayed. This is not "
"limited to the :ref:`Panel <class_Panel>` control, as styleboxes are used by "
"many controls for their backgrounds and overlays."
msgstr ""

#: ../../docs/tutorials/ui/gui_skinning.rst:90
msgid "Theme types"
msgstr ""

#: ../../docs/tutorials/ui/gui_skinning.rst:92
msgid ""
"To help with the organization of its items each theme is separated into "
"types, and each item must belong to a single type. In other words, each "
"theme item is defined by its name, its data type and its theme type. This "
"combination must be unique within the theme. For example, there cannot be "
"two color items named ``font_color`` in a type called ``Label``, but there "
"can be another ``font_color`` item in a type ``LineEdit``."
msgstr ""

#: ../../docs/tutorials/ui/gui_skinning.rst:99
msgid ""
"The default Godot theme comes with multiple theme types already defined, one "
"for every built-in control node that uses UI skinning. The example above "
"contains actual theme items present in the default theme. You can refer to "
"the **Theme Properties** section in the class reference for each control to "
"see which items are available to it and its child classes."
msgstr ""

#: ../../docs/tutorials/ui/gui_skinning.rst:106
msgid ""
"Child classes can use theme items defined for their parent class (``Button`` "
"and its derivatives being a good example of that). In fact, every control "
"can use every theme item of any theme type, if it needs to (but for the "
"clarity and predictability we try to avoid that in the engine)."
msgstr ""

#: ../../docs/tutorials/ui/gui_skinning.rst:111
msgid ""
"It is important to remember that for child classes that process is "
"automated. Whenever a built-in control requests a theme item from the theme "
"it can omit the theme type, and its class name will be used instead. On top "
"of that, the class names of its parent classes will also be used in turn. "
"This allows changes to the parent class, such as ``Button``, to affect all "
"derived classes without the need to customize every one of them."
msgstr ""

#: ../../docs/tutorials/ui/gui_skinning.rst:118
msgid ""
"You can also define your own theme types, and additionally customize both "
"built-in controls and your own controls. Because built-in controls have no "
"knowledge of your custom theme types, you must utilize scripts to access "
"those items. All control nodes have several methods that allow to fetch "
"theme items from the theme that is applied to them. Those methods accept the "
"theme type as one of the arguments."
msgstr ""

#: ../../docs/tutorials/ui/gui_skinning.rst:135
msgid ""
"To give more customization opportunities types can also be linked together "
"as type variations. This is another use-case for custom theme types. For "
"example, a theme can contain a type ``Header`` which can be marked as a "
"variation of the base ``Label`` type. An individual ``Label`` control can "
"then be set to use the ``Header`` variation for its type, and every time a "
"theme item is requested from a theme this variation will be used before any "
"other type. This allows to store various presets of theme items for the same "
"class of the control node in the single ``Theme`` resource."
msgstr ""

#: ../../docs/tutorials/ui/gui_skinning.rst:145
msgid ""
"Only variations available from the default theme or defined in the custom "
"project theme are shown in the Inspector dock as options. You can still "
"input manually the name of a variation that is defined outside of those two "
"places, but it is recommended to keep all variations to the project theme."
msgstr ""

#: ../../docs/tutorials/ui/gui_skinning.rst:150
msgid ""
"You can learn more about creating and using theme type variations in a :ref:"
"`dedicated article <doc_gui_theme_type_variations>`."
msgstr ""

#: ../../docs/tutorials/ui/gui_skinning.rst:154
msgid "Customizing a control"
msgstr ""

#: ../../docs/tutorials/ui/gui_skinning.rst:156
msgid ""
"Each control node can be customized directly without the use of themes. This "
"is called local overrides. Every theme property from the control's class "
"reference can be overridden directly on the control itself, using either the "
"Inspector dock, or scripts. This allows to make granular changes to a "
"particular part of the UI, while not affecting anything else in the project, "
"including this control's children."
msgstr ""

#: ../../docs/tutorials/ui/gui_skinning.rst:166
msgid ""
"Local overrides are less useful for the visual flair of your user interface, "
"especially if you aim for consistency. However, for layout nodes these are "
"essential. Nodes such as :ref:`BoxContainer <class_BoxContainer>` and :ref:"
"`GridContainer <class_GridContainer>` use theme constants for defining "
"separation between their children, and :ref:`MarginContainer "
"<class_MarginContainer>` stores its customizable margins in its theme items."
msgstr ""

#: ../../docs/tutorials/ui/gui_skinning.rst:173
msgid ""
"Whenever a control has a local theme item override, this is the value that "
"it uses. Values provided by the theme are ignored."
msgstr ""

#: ../../docs/tutorials/ui/gui_skinning.rst:179
#, fuzzy
msgid "Customizing a project"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/ui/gui_skinning.rst:181
msgid ""
"Out of the box each project adopts the default project theme provided by "
"Godot. The default theme itself is constant and cannot be changed, but its "
"items can be overridden with a custom theme. Custom themes can be applied in "
"two ways: as a project setting, and as a node property throughout the tree "
"of control nodes."
msgstr ""

#: ../../docs/tutorials/ui/gui_skinning.rst:186
msgid ""
"There are two project settings that can be adjusted to affect your entire "
"project: :ref:`gui/theme/custom<class_ProjectSettings_property_gui/theme/"
"custom>` allows you to set a custom project-wide theme, and :ref:`gui/theme/"
"custom_font<class_ProjectSettings_property_gui/theme/custom_font>` does the "
"same to the default fallback font. When a theme item is requested by a "
"control node the custom project theme, if present, is checked first. Only if "
"it doesn't have the item the default theme is checked."
msgstr ""

#: ../../docs/tutorials/ui/gui_skinning.rst:193
msgid ""
"This allows you to configure the default look of every Godot control with a "
"single theme resource, but you can go more granular than that. Every control "
"node also has a :ref:`theme <class_Control_property_theme>` property, which "
"allows you to set a custom theme for the branch of nodes starting with that "
"control. This means that the control and all of its children, and their "
"children in turn, would first check that custom theme resource before "
"falling back on the project and the default themes."
msgstr ""

#: ../../docs/tutorials/ui/gui_skinning.rst:201
msgid ""
"Instead of changing the project setting you can set the custom theme "
"resource to the root-most control node of your entire UI branch to almost "
"the same effect. While in the running project it will behave as expected, "
"individual scenes will still display using the default theme when previewing "
"or running them directly. To fix that you can set the same theme resource to "
"the root control of each individual scene."
msgstr ""

#: ../../docs/tutorials/ui/gui_skinning.rst:207
msgid ""
"For example, you can have a certain style for buttons in your project theme, "
"but want a different look for buttons inside of a popup dialog. You can set "
"a custom theme resource to the root control of your popup and define a "
"different style for buttons within that resource. As long as the chain of "
"control nodes between the root of the popup and the buttons is "
"uninterrupted, those buttons will use the styles defined in the theme "
"resource that is closest to them. All other controls will still be styled "
"using the project-wide theme and the default theme styles."
msgstr ""

#: ../../docs/tutorials/ui/gui_skinning.rst:215
msgid ""
"To sum it up, for an arbitrary control its theme item lookup would look "
"something like this:"
msgstr ""

#: ../../docs/tutorials/ui/gui_skinning.rst:218
msgid "Check for local overrides of the same data type and name."
msgstr ""

#: ../../docs/tutorials/ui/gui_skinning.rst:219
msgid "Using control's type variation, class name and parent class names:"
msgstr ""

#: ../../docs/tutorials/ui/gui_skinning.rst:221
msgid ""
"Check every control starting from itself and see if it has a theme property "
"set;"
msgstr ""

#: ../../docs/tutorials/ui/gui_skinning.rst:222
msgid ""
"If it does, check that theme for the matching item of the same name, data "
"and theme type;"
msgstr ""

#: ../../docs/tutorials/ui/gui_skinning.rst:223
msgid ""
"If there is no custom theme or it doesn't have the item, move to the parent "
"control;"
msgstr ""

#: ../../docs/tutorials/ui/gui_skinning.rst:224
msgid ""
"Repeat steps a-c. until the root of the tree is reached, or a non-control "
"node is reached."
msgstr ""

#: ../../docs/tutorials/ui/gui_skinning.rst:226
msgid ""
"Using control's type variation, class name and parent class names check the "
"project-wide theme, if it's present."
msgstr ""

#: ../../docs/tutorials/ui/gui_skinning.rst:227
msgid ""
"Using control's type variation, class name and parent class names check the "
"default theme."
msgstr ""

#: ../../docs/tutorials/ui/gui_skinning.rst:229
msgid ""
"Even if the item doesn't exist in any theme, a corresponding default value "
"for that data type will be returned."
msgstr ""

#: ../../docs/tutorials/ui/gui_skinning.rst:233
msgid "Beyond controls"
msgstr ""

#: ../../docs/tutorials/ui/gui_skinning.rst:235
msgid ""
"Naturally, themes are an ideal type of resource for storing configuration "
"for something visual. While the support for theming is built into control "
"nodes, other nodes can use them as well, just like any other resource."
msgstr ""

#: ../../docs/tutorials/ui/gui_skinning.rst:239
msgid ""
"An example of using themes for something beyond controls can be a modulation "
"of sprites for the same units on different teams in a strategy game. A theme "
"resource can define a collection of colors, and sprites (with a help from "
"scripts) can use those colors to draw the texture. The main benefit being "
"that you could make different themes using the same theme items for red, "
"blue, and green teams, and swap them with a single resource change."
msgstr ""

#: ../../docs/tutorials/ui/gui_using_theme_editor.rst:4
#, fuzzy
msgid "Using the theme editor"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/ui/gui_using_theme_editor.rst:6
msgid ""
"This article explains how to create and manage UI themes using the Godot "
"editor and its theme editor tool. We recommend getting familiar with the "
"basics behind GUI skinning/theming by reading :ref:`doc_gui_skinning` before "
"starting."
msgstr ""

#: ../../docs/tutorials/ui/gui_using_theme_editor.rst:10
msgid ""
"The theme editor is a bottom panel tool that activates automatically, when "
"a :ref:`Theme <class_Theme>` resource is selected for editing. It contains "
"the necessary UI for adding, removing, and adjusting theme types and theme "
"items. It features a preview section for testing your changes live, as well "
"as a window dialog for doing bulk operations of the theme items."
msgstr ""

#: ../../docs/tutorials/ui/gui_using_theme_editor.rst:17
msgid "Creating a theme"
msgstr ""

#: ../../docs/tutorials/ui/gui_using_theme_editor.rst:19
msgid ""
"Like any other resources, themes can be created directly in the file system "
"dock by right-clicking and selecting **New Resource...**, then selecting "
"**Theme** and clicking **Create**. This is especially useful for creating "
"project-wide themes."
msgstr ""

#: ../../docs/tutorials/ui/gui_using_theme_editor.rst:24
msgid ""
"Themes also can be created from any control node. Select a control node in "
"the scene hierarchy, then in the inspector go to the ``theme`` property. "
"From there you can select **New Theme**."
msgstr ""

#: ../../docs/tutorials/ui/gui_using_theme_editor.rst:31
msgid ""
"This will create an empty theme and open up the theme editor. Keep in mind "
"that resources created this way are bundled with the scene by default. Use "
"the context menu to save the new theme to a file instead."
msgstr ""

#: ../../docs/tutorials/ui/gui_using_theme_editor.rst:35
msgid ""
"While the theme editor provides the tools to manage theme types and items, "
"themes also include the default, fallback font that you can edit only using "
"the Inspector dock. Same applies to the contents of complex resource types, "
"such as :ref:`StyleBoxes <class_StyleBox>` and icons — they open for editing "
"in the Inspector."
msgstr ""

#: ../../docs/tutorials/ui/gui_using_theme_editor.rst:44
msgid "Theme editor overview"
msgstr ""

#: ../../docs/tutorials/ui/gui_using_theme_editor.rst:49
msgid ""
"The theme editor has two main parts. The main theme editor, located at the "
"bottom of the Godot editor, aims to provide users with tools to quickly "
"create, edit, and delete theme items and types. It gives visual tools for "
"picking and changing controls, abstracting the underlying theme concepts. "
"The **Manage Theme Items** dialog, on the other hand, tries to address the "
"needs of those who want to change themes manually. It's also useful for "
"creating a new editor theme."
msgstr ""

#: ../../docs/tutorials/ui/gui_using_theme_editor.rst:57
msgid "Theme previews"
msgstr ""

#: ../../docs/tutorials/ui/gui_using_theme_editor.rst:59
msgid ""
"The left-hand side of the main editor has a set of preview tabs. The "
"**Default Preview** tab is visible out of the box and contains most of the "
"frequently used controls in various states. Previews are interactive, so "
"intermediate states (e.g. hover) can be previewed as well."
msgstr ""

#: ../../docs/tutorials/ui/gui_using_theme_editor.rst:66
msgid ""
"Additional tabs can be created from arbitrary scenes in your project. The "
"scene must have a control node as its root to function as a preview. To add "
"a new tab click the **Add Preview** button and select the saved scene from "
"your file system."
msgstr ""

#: ../../docs/tutorials/ui/gui_using_theme_editor.rst:73
msgid ""
"If you make changes to the scene, they will not be reflected in the preview "
"automatically. To update the preview click the reload button on the toolbar."
msgstr ""

#: ../../docs/tutorials/ui/gui_using_theme_editor.rst:76
msgid ""
"Previews can also be used to quickly select the theme type to edit. Select "
"the picker tool from the toolbar and hover over the preview area to "
"highlight control nodes. Highlighted control nodes display their class name, "
"or type variation if available. Clicking on the highlighted control opens it "
"for editing on the right-hand side."
msgstr ""

#: ../../docs/tutorials/ui/gui_using_theme_editor.rst:85
msgid "Theme types and items"
msgstr ""

#: ../../docs/tutorials/ui/gui_using_theme_editor.rst:87
msgid ""
"The right-hand side of the theme editor provides a list of theme types "
"available in the edited theme resource, and the contents of the selected "
"type. The list of type's items is divided into several tabs, corresponding "
"to each data type available in the theme (colors, constants, styles, etc.). "
"If the **Show Default** option is enabled, then for each built-in type its "
"default theme values are displayed, greyed out. If the option is disabled, "
"only the items available in the edited theme itself are displayed."
msgstr ""

#: ../../docs/tutorials/ui/gui_using_theme_editor.rst:98
msgid ""
"Individual items from the default theme can be added to the current theme by "
"clicking on the **Override** button next to the item. You can also override "
"all the default items of the selected theme type by clicking on the "
"**Override All** button. Overridden properties can then be removed with the "
"**Remove Item** button. Properties can also be renamed using the **Rename "
"Item** button, and completely custom properties can be added to the list "
"using the text field below it."
msgstr ""

#: ../../docs/tutorials/ui/gui_using_theme_editor.rst:105
msgid ""
"Overridden theme items can be edited directly in the right-hand panel, "
"unless they are resources. Resources have rudimentary controls available for "
"them, but must be edited in the Inspector dock instead."
msgstr ""

#: ../../docs/tutorials/ui/gui_using_theme_editor.rst:112
msgid ""
"Styleboxes have an unique feature available, where you can pin an individual "
"stylebox from the list. Pinned stylebox acts like the leader of the pack, "
"and all styleboxes of the same type are updated alongside it when you change "
"its properties. This allows you to edit properties of several styleboxes at "
"the same time."
msgstr ""

#: ../../docs/tutorials/ui/gui_using_theme_editor.rst:121
msgid ""
"While theme types can be picked from a preview, they can also be added "
"manually. Clicking the plus button next to the type list opens the **Add "
"item Type** menu. In that menu you can either select a type from the list, "
"or you can enter an arbitrary name to create a custom type. Text field also "
"filters the list of control nodes."
msgstr ""

#: ../../docs/tutorials/ui/gui_using_theme_editor.rst:131
msgid "Manage and import items"
msgstr ""

#: ../../docs/tutorials/ui/gui_using_theme_editor.rst:133
msgid ""
"Clicking the **Manage Items** button brings up the **Manage Theme Items** "
"dialog. In the **Edit Items** tab you can view and add theme types, as well "
"as view and edit the theme items of the selected type."
msgstr ""

#: ../../docs/tutorials/ui/gui_using_theme_editor.rst:140
msgid ""
"You can create, rename and remove individual theme items here by clicking "
"the corresponding **Add X Item** and specifying their name. You can also "
"mass delete theme items either by their data type (using the brush icon in "
"the list) or by their quality. **Remove Class Items** will remove all built-"
"in theme items you have customized for a control node type. **Remove Custom "
"Items** will remove all the custom theme items for the selected type. "
"Finally, **Remove All Items** will remove everything from the type."
msgstr ""

#: ../../docs/tutorials/ui/gui_using_theme_editor.rst:148
msgid ""
"From the **Import Items** tab you can import theme items from other themes. "
"You can import items from the default Godot theme, the Godot editor theme, "
"or another custom theme. You can import individual or multiple items, and "
"you can decide whether to copy or omit their data as well. There are several "
"ways you can select and deselect the items, including by hand, by hierarchy, "
"by data type, and everything. Opting to include the data will copy all theme "
"items as they are to your theme. Omitting the data will create the items of "
"the corresponding data type and name, but will leave them empty, creating a "
"template of a theme in a way."
msgstr ""

#: ../../docs/tutorials/ui/gui_theme_type_variations.rst:4
msgid "Theme type variations"
msgstr ""

#: ../../docs/tutorials/ui/gui_theme_type_variations.rst:6
msgid ""
"When designing a user interface there may be times when a :ref:`Control "
"<class_Control>` node needs to have a different look than what is normally "
"defined by a :ref:`Theme <class_Theme>`. Every control node has theme "
"property overrides, which allow you to redefine the styling for each "
"individual UI element."
msgstr ""

#: ../../docs/tutorials/ui/gui_theme_type_variations.rst:14
msgid ""
"This approach quickly becomes hard to manage, if you need to share the same "
"custom look between several controls. Imagine that you use gray, blue, and "
"red variants of :ref:`Button <class_Button>` throughout your project. "
"Setting it up every time you add a new button element to your interface is a "
"tedious task."
msgstr ""

#: ../../docs/tutorials/ui/gui_theme_type_variations.rst:19
msgid ""
"To help with the organization and to better utilize the :ref:`power of "
"themes <doc_gui_skinning>` you can use theme type variations. These work "
"like normal theme types, but instead of being self-sufficient and standalone "
"they extend another, base type."
msgstr ""

#: ../../docs/tutorials/ui/gui_theme_type_variations.rst:23
msgid ""
"Following the previous example, your theme can have some styles, colors, and "
"fonts defined for the ``Button`` type, customizing the looks of every button "
"element in your UI. To then have a gray, red, or blue button you would "
"create a new type, e.g. ``GrayButton``, and mark it as a variation of the "
"base ``Button`` type."
msgstr ""

#: ../../docs/tutorials/ui/gui_theme_type_variations.rst:28
msgid ""
"Type variations can replace some aspects of the base type, but keep others. "
"They can also define properties that the base style hasn't defined. For "
"example, your ``GrayButton`` can override the ``normal`` style from the base "
"``Button`` and add ``font_color`` that ``Button`` has never defined. The "
"control will use a combination of both types giving priority to the type "
"variation."
msgstr ""

#: ../../docs/tutorials/ui/gui_theme_type_variations.rst:35
msgid ""
"The way controls resolve what theme items they use from each type and each "
"theme is better described in the :ref:`Customizing a project "
"<doc_gui_theme_in_project>` section of the \"Introduction to GUI skinning\" "
"article."
msgstr ""

#: ../../docs/tutorials/ui/gui_theme_type_variations.rst:40
#, fuzzy
msgid "Creating a type variation"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/ui/gui_theme_type_variations.rst:42
msgid ""
"To create a type variation open the theme editor, then click the plus icon "
"next to the **Type** dropdown on the right side of the editor. Type in what "
"you want to name your theme type variation in the text box, then click **Add "
"Type**."
msgstr ""

#: ../../docs/tutorials/ui/gui_theme_type_variations.rst:46
msgid ""
"Below the **Type** dropdown are the property tabs. Switch to the tab with a "
"wrench and screwdriver icon."
msgstr ""

#: ../../docs/tutorials/ui/gui_theme_type_variations.rst:52
msgid ""
"Click on the plus icon next to the **Base Type** field. You can select the "
"base type there, which would typically be the name of a control node class "
"(e.g., ``Button``, ``Label``, etc). Type variations can also chain and "
"extend other type variations. This works in the same way control nodes "
"inherit styling of their base class. For example, ``CheckButton`` inherits "
"styles from ``Button`` because corresponding node types extend each other."
msgstr ""

#: ../../docs/tutorials/ui/gui_theme_type_variations.rst:58
msgid ""
"After you select the base type, you should now be able to see its properties "
"on the other tabs in the theme editor. You can edit them as usual."
msgstr ""

#: ../../docs/tutorials/ui/gui_theme_type_variations.rst:62
#, fuzzy
msgid "Using a type variation"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/ui/gui_theme_type_variations.rst:64
msgid ""
"Now that a type variation has been created you can apply it to your nodes. "
"In the inspector dock, under the **Theme** property of a control node, you "
"can find the **Theme Type Variation** property. It is empty by default, "
"which means that only the base type has an effect on this node."
msgstr ""

#: ../../docs/tutorials/ui/gui_theme_type_variations.rst:69
msgid ""
"You can either select a type variation from a dropdown list, or input its "
"name manually. Variations appear on the list only if the type variation "
"belongs to the project-wide theme, which you can configure in the project "
"settings. For any other case you have to input the name of the variation "
"manually. Click on the pencil icon to the right. Then type in the name of "
"the type variation and click the check mark icon or press enter. If a type "
"variation with that name exists it will now be used by the node."
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:4
#, fuzzy
msgid "Using Fonts"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/ui/gui_using_fonts.rst:6
msgid "Godot allows you to set specific fonts for different UI nodes."
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:8
msgid ""
"There are three different places where you can setup font usage. The first "
"is the theme editor. Choose the node you want to set the font for and select "
"the font tab. The second is in the inspector for control nodes under **Theme "
"Overrides > Fonts**. Lastly, in the inspector settings for themes under "
"**Default Font**."
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:14
msgid ""
"If no font override is specified anywhere, `Open Sans <https://fonts.google."
"com/specimen/Open+Sans>`__ SemiBold is used as the default project font."
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:20
msgid ""
"Since Godot 4.0, font sizes are no longer defined in the font itself but are "
"instead defined in the node that uses the font. This is done in the **Theme "
"Overrides > Font Sizes** section of the inspector."
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:24
msgid ""
"This allows changing the font size without having to duplicate the font "
"resource for every different font size."
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:27
msgid ""
"There are 2 kinds of font files: *dynamic* (TTF/OTF/WOFF/WOFF2 formats) and "
"*bitmap* (BMFont ``.fnt`` format or monospaced image). Dynamic fonts are the "
"most commonly used option, as they can be resized and still look crisp at "
"higher sizes. Thanks to their vector-based nature, they can also contain a "
"lot more glyphs while keeping a reasonable file size compared to bitmap "
"fonts. Dynamic fonts also support some advanced features that bitmap fonts "
"cannot support, such as *ligatures* (several characters transforming into a "
"single different design)."
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:37
msgid ""
"You can find freely licensed font files on websites such as `Google Fonts "
"<https://fonts.google.com/>`__ and `Font Library <https://fontlibrary.org/"
">`__."
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:41
msgid ""
"Fonts are covered by copyright. Double-check the license of a font before "
"using it, as not all fonts allow commercial use without purchasing a license."
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:46
#, fuzzy
msgid ""
"You can see how fonts work in action using the `BiDI and Font Features demo "
"project <https://github.com/godotengine/godot-demo-projects/tree/master/gui/"
"bidi_and_font_features>`__."
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati različite Godo demo projekte "
"`Godot demo projects <https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/tutorials/ui/gui_using_fonts.rst:50
msgid "Dynamic fonts"
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:52
msgid "Godot supports the following dynamic font formats:"
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:54
msgid "TrueType Font or Collection (``.ttf``, ``.ttc``)"
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:55
msgid "OpenType Font or Collection (``.otf``, ``.otc``)"
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:56
msgid "Web Open Font Format 1 (``.woff``)"
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:57
msgid "Web Open Font Format 2 (``.woff2``, since Godot 3.5)"
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:59
msgid ""
"While ``.woff`` and especially ``.woff2`` tend to result in smaller file "
"sizes, there is no universally \"better\" font format. In most situations, "
"it's recommended to use the font format that was shipped on the font "
"developer's website."
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:65
msgid "Bitmap fonts"
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:67
msgid ""
"Godot supports the BMFont (``.fnt``) bitmap font format. This is a format "
"created by the `BMFont <https://www.angelcode.com/products/bmfont/>`__ "
"program. Many BMFont-compatible programs also exist, like `BMGlyph <https://"
"www.bmglyph.com/>`__."
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:71
msgid ""
"Alternatively, you can import any image to be used as a bitmap font. This is "
"only supported for **monospaced** fonts (fonts where each character has the "
"same width). To do so, select the image in the FileSystem dock, go to the "
"Import dock, change its import type to **Font Data (Monospace Image Font)** "
"then click **Reimport**:"
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:81
msgid "Changing import type to Font Data (Monospace Image Font)"
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:81
msgid "Changing import type to **Font Data (Monospace Image Font)**"
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:83
msgid ""
"The font's character set layout can be in any order, but orders that match "
"standard Unicode are recommended as they'll require far less configuration "
"to import. For example, the bitmap font below contains `ASCII <https://en."
"wikipedia.org/wiki/ASCII>`__ characters and follows standard ASCII ordering:"
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:92
msgid "Bitmap font example"
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:92
msgid ""
"Credit: `LibreQuake <https://github.com/MissLav/LibreQuake/blob/master/lq1/"
"gfx-wad/CONCHARS.png>`__ (scaled and cropped to exclude extended range)"
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:95
msgid ""
"The following import options can be used to import the above font image "
"successfully:"
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:102
msgid "Import options to use for the above example font"
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:104
msgid ""
"The **Character Ranges** option is an array that maps each position on the "
"image (in tile coordinates, not pixels). The font atlas is traversed from "
"left to right and top to bottom. Characters can be specified with decimal "
"numbers (``127``), hexadecimal numbers (``0x007f``) or between *single* "
"quotes (``'~'``). Ranges can be specified with a hyphen between characters."
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:110
msgid ""
"For instance, ``0-127`` (or ``0x0000-0x007f``) denotes the full ASCII range. "
"As another example, ``' '-'~'`` is equivalent to ``32-127`` and denotes the "
"range of *printable* (visible) ASCII characters."
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:114
msgid ""
"Make sure the **Character Ranges** option doesn't exceed the number of "
"**Columns** × **Rows** defined. Otherwise, the font will fail to import."
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:117
msgid ""
"If your font image contains margins not used for font glyphs (such as "
"attribution information), try adjusting **Image Margin**. This is a margin "
"applied only once around the whole image."
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:121
msgid ""
"If your font image contains guides (in the form of lines between glyphs) or "
"if spacing between characters appears incorrect, try adjusting **Character "
"Margin**. This margin is applied for every imported glyph."
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:126
#: ../../docs/tutorials/ui/gui_using_fonts.rst:135
#, fuzzy
msgid "Loading a font file"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/ui/gui_using_fonts.rst:128
msgid ""
"To load a font file (dynamic or bitmap), use the resource dropdown's **Quick "
"Load** or **Load** option next to a font property, then navigate to the font "
"file in question:"
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:137
msgid ""
"You can also drag-and-drop a font file from the FileSystem dock to the "
"inspector property that accepts a Font resource."
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:142
msgid ""
"In Godot 4.0 and later, texture filter and repeat properties are defined in "
"the location where the texture is used, rather than on the texture itself. "
"This also applies to fonts (both dynamic fonts and bitmap fonts)."
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:146
msgid ""
"Fonts that have a pixel art appearance should have bilinear filtering "
"disabled by changing the **Rendering > Textures > Canvas Textures > Default "
"Texture Filter** project setting to **Nearest**."
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:150
msgid ""
"The font size must also be an integer multiple of the design size (which "
"varies on a per-font basis), and the Control node using the font must be "
"scaled by an integer multiple as well. Otherwise, the font may look blurry. "
"Font sizes in Godot are specified in pixels (px), not points (pt). Keep this "
"in mind when comparing font sizes across different software."
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:156
msgid ""
"The texture filter mode can also be set on individual nodes that inherit "
"from CanvasItem by setting :ref:`CanvasItem.texture_filter "
"<class_CanvasItem_property_texture_filter>`."
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:160
#, fuzzy
msgid "Font outlines and shadows"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/ui/gui_using_fonts.rst:162
msgid ""
"Font outlines and shadows can be used to improve readability when the "
"background color isn't known in advance. For instance, this is the case for "
"HUD elements that are drawn over a 2D/3D scene."
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:166
msgid ""
"Font outlines are available in most nodes that derive from Control, in "
"addition to :ref:`class_Label3D`."
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:169
msgid ""
"To enable outline for a font on a given node, configure the theme overrides "
"**Font Outline Color** and **Outline Size** in the inspector. The result "
"should look like this:"
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:177
#, fuzzy
msgid "Font outline example"
msgstr "Windows"

#: ../../docs/tutorials/ui/gui_using_fonts.rst:181
msgid ""
"If using a font with MSDF rendering, its **MSDF Pixel Range** import option "
"be set to at least *twice* the value of the outline size for outline "
"rendering to look correct. Otherwise, the outline may appear to be cut off "
"earlier than intended."
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:186
msgid ""
"Support for font shadows is more limited: they are only available in :ref:"
"`class_Label` and :ref:`class_RichTextLabel`. Additionally, font shadows "
"always have a hard edge (but you can reduce their opacity to make them look "
"more subtle). To enable font shadows on a given node, configure the **Font "
"Shadow Color**, **Shadow Offset X**, and **Shadow Offset Y** theme overrides "
"in a Label or RichTextLabel node accordingly:"
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:197
msgid "Configuring font shadow in a Label node"
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:199
msgid "The result should look like this:"
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:205
#, fuzzy
msgid "Font shadow example"
msgstr "Windows"

#: ../../docs/tutorials/ui/gui_using_fonts.rst:209
msgid ""
"You can create local overrides to font display in Label nodes by creating a :"
"ref:`class_LabelSettings` resource that you reuse across Label nodes. This "
"resource takes priority over :ref:`theme properties <doc_gui_skinning>`."
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:214
#, fuzzy
msgid "Advanced font features"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/ui/gui_using_fonts.rst:219
msgid "Antialiasing"
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:221
msgid ""
"You can adjust how the font should be smoothed out when rendering by "
"adjusting *antialiasing* and *hinting*. These are different properties, with "
"different use cases."
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:225
msgid ""
"Antialiasing controls how glyph edges should be smoothed out when "
"rasterizing the font. The default antialiasing method (**Grayscale**) works "
"well on every display technology. However, at small sizes, grayscale "
"antialiasing may result in fonts looking blurry."
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:230
msgid ""
"The antialiasing sharpness can be improved by using LCD subpixel "
"optimization, which exploits the subpixel patterns of most LCD displays by "
"offsetting the font antialiasing on a per-channel basis (red/green/blue). "
"The downside is that this can introduce \"fringing\" on edges, especially on "
"display technologies that don't use standard RGB subpixels (such as OLED "
"displays)."
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:236
msgid ""
"In most games, it's recommended to stick to the default **Grayscale** "
"antialiasing. For non-game applications, LCD subpixel optimization is worth "
"exploring."
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:244
msgid "Font antialiasing comparison"
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:244
msgid "From top to bottom: Disabled, Grayscale, LCD Subpixel (RGB)"
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:248
msgid ""
"Antialiasing cannot be changed on :ref:`MSDF-rendered fonts "
"<doc_using_fonts_msdf>` – these are always rendered with grayscale "
"antialiasing."
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:254
msgid "Hinting"
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:256
msgid ""
"Hinting controls how aggressively glyph edges should be snapped to pixels "
"when rasterizing the font. **None** results in the smoothest appearance, "
"which can make the font look blurry at small sizes. **Light** (default) is "
"sharper by snapping glyph edges to pixels on the Y axis only, while **Full** "
"is even sharper by snapping glyph edges to pixels on both X and Y axes. "
"Depending on personal preference, you may prefer using one hinting mode over "
"the other."
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:267
msgid "Font hinting comparison"
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:267
msgid "From top to bottom: None, Light, Full hinting"
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:271
msgid ""
"If changing the hinting mode has no visible effect after clicking "
"**Reimport**, it's usually because the font doesn't include hinting "
"instructions. This can be resolved by looking for a version of the font file "
"that includes hinting instructions, or enabling **Force Autohinter** in the "
"Import dock. This will use `FreeType <https://freetype.org/>`__'s autohinter "
"to automatically add hinting instructions to the imported font."
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:281
msgid "Subpixel positioning"
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:283
msgid ""
"Subpixel positioning can be adjusted. This is a `FreeType <https://freetype."
"org/>`__ feature that allows glyphs to be rendered more closely to their "
"intended form. The default setting of **Auto** automatically enables "
"subpixel positioning at small sizes, but disables it at large font sizes to "
"improve rasterization performance."
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:289
msgid ""
"You can force the subpixel positioning mode to **Disabled**, **One half of a "
"pixel** or **One quarter of a pixel**. **One quarter of a pixel** provides "
"the best quality, at the cost of longer rasterization times."
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:293
msgid ""
"Changing antialiasing, hinting and subpixel positioning has the most visible "
"effect at smaller font sizes."
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:298
msgid ""
"Fonts that have a pixel art appearance should have their subpixel "
"positioning mode set to **Disabled**. Otherwise, the font may appear to have "
"uneven pixel sizes."
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:302
msgid ""
"This step is not required for bitmap fonts, as subpixel positioning is only "
"relevant for dynamic fonts (which are usually made of vector elements)."
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:308
msgid "Mipmaps"
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:310
msgid ""
"By default, fonts do not have mipmaps generated to reduce memory usage and "
"speed up rasterization. However, this can cause downscaled fonts to become "
"grainy. This can be especially noticeable with :ref:`doc_3d_text` that "
"doesn't have **Fixed Size** enabled. This can also occur when displaying "
"text with a traditional rasterized (non-:ref:`MSDF <doc_using_fonts_msdf>`) "
"font in a Control node that has its scale lower than ``(1, 1)``."
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:317
msgid ""
"After selecting a font in the FileSystem dock, you can enable the "
"**Mipmaps** in the Import dock to improve downscaled font rendering "
"appearance."
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:320
msgid ""
"Mipmaps can be enabled on MSDF fonts as well. This can improve font "
"rendering quality a little at smaller-than-default sizes, but MSDF fonts are "
"already resistant to graininess out of the box."
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:327
msgid "MSDF font rendering"
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:329
msgid ""
"Multi-channel signed distance field (MSDF) font rendering allows rendering "
"fonts at any size, without having to re-rasterize them when their size "
"changes."
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:332
msgid ""
"MSDF font rendering has 2 upsides over traditional font rasterization, which "
"Godot uses by default:"
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:335
msgid "The font will always look crisp, even at huge sizes."
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:336
msgid ""
"There is less stuttering when rendering characters *at large font sizes* for "
"the first time, as there is no rasterization performed."
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:339
msgid "The downsides of MSDF font rendering are:"
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:341
msgid ""
"Higher baseline cost for font rendering. This is usually not noticeable on "
"desktop platforms, but it can have an impact on low-end mobile devices."
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:343
msgid ""
"Fonts at small sizes will not look as clear as rasterized fonts, due to the "
"lack of hinting."
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:345
msgid ""
"Rendering new glyphs for the first time *at small font sizes* may be more "
"expensive compared to traditional rasterized fonts. :ref:"
"`doc_using_fonts_font_prerendering` can be used to alleviate this."
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:348
msgid "LCD subpixel optimization cannot be enabled for MSDF fonts."
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:349
msgid ""
"Fonts with self-intersecting outlines will not render correctly in MSDF "
"mode. If you notice rendering issues on fonts downloaded from websites such "
"as `Google Fonts <https://fonts.google.com>`__, try downloading the font "
"from the font author's official website instead."
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:358
msgid "Comparison of font rasterization methods"
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:358
msgid ""
"Comparison of font rasterization methods. From top to bottom: rasterized "
"without oversampling, rasterized with oversampling, MSDF"
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:361
msgid ""
"To enable MSDF rendering for a given font, select it in the FileSystem dock, "
"go to the Import dock, enable **Multichannel Signed Distance Field**, then "
"click **Reimport**:"
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:369
msgid "Enabling MSDF in the font's import options"
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:374
#, fuzzy
msgid "Using emoji"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/ui/gui_using_fonts.rst:376
msgid "Godot has limited support for emoji fonts:"
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:378
msgid "CBDT/CBLC (embedded PNGs) and SVG emoji fonts are supported."
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:379
msgid "COLR/CPAL emoji fonts (custom vector format) are **not** supported."
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:380
msgid ""
"EMJC bitmap image compression (used by iOS' system emoji font) is **not** "
"supported. This means that to support emoji on iOS, you must use a custom "
"font that uses SVG or PNG bitmap compression instead."
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:384
msgid ""
"For Godot to be able to display emoji, the font used (or one of its :ref:"
"`fallbacks <doc_using_fonts_font_fallbacks>`) needs to include them. "
"Otherwise, emoji won't be displayed and placeholder \"tofu\" characters will "
"appear instead:"
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:393
msgid "Default appearance when trying to use emoji in a label"
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:395
msgid ""
"After adding a font to display emoji such as `Noto Color Emoji <https://"
"fonts.google.com/noto/specimen/Noto+Color+Emoji>`__, you get the expected "
"result:"
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:403
msgid "Correct appearance after adding an emoji font to the label"
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:405
msgid ""
"To use a regular font alongside emoji, it's recommended to specify a :ref:"
"`fallback font <doc_using_fonts_font_fallbacks>` that points to the emoji "
"font in the regular font's advanced import options. If you wish to use the "
"default project font while displaying emoji, leave the **Base Font** "
"property in FontVariation empty while adding a font fallback pointing to the "
"emoji font:"
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:414
msgid ""
"Emoji fonts are quite large in size, so you may want to :ref:`load a system "
"font <doc_using_fonts_system_fonts>` to provide emoji glyphs rather than "
"bundling it with your project. This allows providing full emoji support in "
"your project without increasing the size of its exported PCK. The downside "
"is that emoji will look different depending on the platform, and loading "
"system fonts is not supported on all platforms."
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:421
msgid "It's possible to use a system font as a fallback font too."
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:424
#, fuzzy
msgid "Using icon fonts"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/ui/gui_using_fonts.rst:426
msgid ""
"Tools like `Fontello <https://fontello.com/>`__ can be used to generate font "
"files containing vectors imported from SVG files. This can be used to render "
"custom vector elements as part of your text, or to create extruded 3D icons "
"with :ref:`doc_3d_text` and TextMesh."
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:433
msgid ""
"Fontello currently does not support creating multicolored fonts (which Godot "
"can render). As of November 2022, support for multicolored fonts in icon "
"font generation tools remains scarce."
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:437
msgid ""
"Depending on your use cases, this may lead to better results compared to "
"using the ``img`` tag in :ref:`RichTextLabel <doc_bbcode_in_richtextlabel>`. "
"Unlike bitmap images (including SVGs which are rasterized on import by "
"Godot), true vector data can be resized to any size without losing quality."
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:442
msgid ""
"After downloading the generated font file, load it in your Godot project "
"then specify it as a custom font for a Label, RichTextLabel or Label3D node. "
"Switch over to the Fontello web interface, then copy the character by "
"selecting it then pressing :kbd:`Ctrl + C` (:kbd:`Cmd + C` on macOS). Paste "
"the character in the **Text** property of your Label node. The character "
"will appear as a placeholder glyph in the inspector, but it should appear "
"correctly in the 2D/3D viewport."
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:449
msgid ""
"To use an icon font alongside a traditional font in the same Control, you "
"can specify the icon font as a :ref:`fallback "
"<doc_using_fonts_font_fallbacks>`. This works because icon fonts use the "
"Unicode *private use area*, which is reserved for use by custom fonts and "
"doesn't contain standard glyphs by design."
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:456
msgid ""
"Several modern icon fonts such as `Font Awesome 6 <https://fontawesome.com/"
"download>`__ have a desktop variant that uses *ligatures* to specify icons. "
"This allows you to specify icons by entering their name directly in the "
"**Text** property of any node that can display fonts. Once the icon's name "
"is fully entered as text (such as ``house``), it will be replaced by the "
"icon."
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:462
msgid ""
"While easier to use, this approach cannot be used with font fallbacks as the "
"main font's characters will take priority over the fallback font's ligatures."
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:468
msgid "Font fallbacks"
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:470
msgid ""
"Godot supports defining one or more fallbacks when the main font lacks a "
"glyph to be displayed. There are 2 main use cases for defining font "
"fallbacks:"
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:473
msgid ""
"Use a font that only supports Latin character sets, but use another font to "
"be able to display text another character set such as Cyrillic."
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:475
msgid "Use a font to render text, and another font to render emoji or icons."
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:477
#: ../../docs/tutorials/ui/gui_using_fonts.rst:654
#: ../../docs/tutorials/ui/gui_using_fonts.rst:832
msgid ""
"Open the Advanced Import Settings dialog by double-clicking the font file in "
"the FileSystem dock. You can also select the font in the FileSystem dock, go "
"to the Import dock then choose **Advanced…** at the bottom:"
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:484
#: ../../docs/tutorials/ui/gui_using_fonts.rst:661
#: ../../docs/tutorials/ui/gui_using_fonts.rst:839
#, fuzzy
msgid "Import dock"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/ui/gui_using_fonts.rst:486
msgid ""
"In the dialog that appears, look for **Fallbacks** section on the sidebar on "
"the right, click the **Array[Font] (size 0)** text to expand the property, "
"then click **Add Element**:"
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:493
msgid "Adding font fallback"
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:495
msgid ""
"Click the dropdown arrow on the new element, then choose a font file using "
"the **Quick Load** or **Load** options:"
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:501
msgid "Loading font fallback"
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:503
msgid ""
"It is possible to add fallback fonts while using the default project font. "
"To do so, leave the **Base Font** property empty while adding one or more "
"font fallbacks."
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:509
msgid ""
"Font fallbacks can also be defined on a local basis similar to :ref:"
"`doc_using_fonts_opentype_font_features`, but this is not covered here for "
"brevity reasons."
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:516
msgid "Variable fonts"
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:518
msgid ""
"Godot has full support for `variable fonts <https://variablefonts.io/>`__, "
"which allow you to use a single font file to represent various font weights "
"and styles (regular, bold, italic, …). This must be supported by the font "
"file you're using."
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:522
msgid ""
"To use a variable font, create a :ref:`class_FontVariation` resource in the "
"location where you intend to use the font, then load a font file within the "
"FontVariation resource:"
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:529
#: ../../docs/tutorials/ui/gui_using_fonts.rst:682
#, fuzzy
msgid "Creating a FontVariation resource"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/ui/gui_using_fonts.rst:534
msgid "Loading a font file into the FontVariation resource"
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:536
msgid ""
"Scroll down to the FontVariation's **Variation** section, then click the "
"**Variation Coordinates** text to expand the list of axes that can be "
"adjusted:"
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:542
msgid "List of variation axes"
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:544
msgid ""
"The set of axes you can adjust depends on the font loaded. Some variable "
"fonts only support one axis of adjustment (typically *weight* or *slant*), "
"while others may support multiple axes of adjustment."
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:548
msgid ""
"For example, here's the `Inter V <https://rsms.me/inter/>`__ font with a "
"*weight* of ``900`` and a *slant* of ``-10``:"
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:554
msgid "Variable font example (Inter V)"
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:558
msgid ""
"While variable font axis names and scales aren't standardized, some common "
"conventions are usually followed by font designers. For instance, the "
"*weight* axis typically uses ``400`` as the \"regular\" font weight and "
"``700`` as the \"bold\" font weight."
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:563
msgid ""
"You can save the FontVariation to a ``.tres`` resource file to reuse it in "
"other places:"
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:569
msgid "Saving FontVariation to an external resource file"
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:572
msgid "Faux bold and italic"
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:574
msgid ""
"When writing text in bold or italic, using font variants specifically "
"designed for this looks better. Spacing between glyphs will be more "
"consistent when using a bold font, and certain glyphs' shapes may change "
"entirely in italic variants (compare \"a\" and *\"a\"*)."
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:579
msgid ""
"However, real bold and italic fonts require shipping more font files, which "
"increases distribution size. A single :ref:`variable font "
"<doc_using_fonts_variable_fonts>` file can also be used, but this file will "
"be larger than a single non-variable font. While file size is usually not an "
"issue for desktop projects, it can be a concern for mobile/web projects that "
"strive to keep distribution size as low as possible."
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:585
msgid ""
"To allow bold and italic fonts to be displayed without having to ship "
"additional fonts (or use a variable font that is larger in size), Godot "
"supports *faux* bold and italic."
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:593
msgid ""
"Faux bold/italic (top), real bold/italic (bottom). Normal font used: Open "
"Sans SemiBold"
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:595
msgid ""
"Faux bold and italic is automatically used in :ref:`class_RichTextLabel`'s "
"bold and italic tags if no custom fonts are provided for bold and/or italic."
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:598
msgid ""
"To use faux bold, create a FontVariation resource in a property where a Font "
"resource is expected. Set **Variation > Embolden** to a positive value to "
"make a font bolder, or to a negative value to make it less bold. Recommended "
"values are between ``0.5`` and ``1.2`` depending on the font."
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:603
msgid ""
"Faux italic is created by skewing the text, which is done by modifying the "
"per-character transform. This is also provided in FontVariation using the "
"**Variation > Transform** property. Setting the ``yx`` component of the "
"character transform to a positive value will italicize the text. Recommended "
"values are between ``0.2`` and ``0.4`` depending on the font."
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:610
msgid "Adjusting font spacing"
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:612
msgid ""
"For stylistic purposes or for better readability, you may want to adjust how "
"a font is presented in Godot."
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:615
msgid ""
"Create a FontVariation resource in a property where a Font resource is "
"expected. There are 4 properties available in the **Variation > Extra "
"Spacing** section, which accept positive and negative values:"
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:619
msgid "**Glyph:** Additional spacing between every glyph."
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:620
msgid "**Space:** Additional spacing between words."
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:621
msgid ""
"**Top:** Additional spacing above glyphs. This is used for multiline text, "
"but also to calculate the minimum size of controls such as :ref:"
"`class_Label` and :ref:`class_Button`."
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:624
msgid ""
"**Top:** Additional spacing below glyphs. This is used for multiline text, "
"but also to calculate the minimum size of controls such as :ref:"
"`class_Label` and :ref:`class_Button`."
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:628
msgid ""
"The **Variation > Transform** property can also be adjusted to stretch "
"characters horizontally or vertically. This is specifically done by "
"adjusting the ``xx`` (horizontal scale) and ``yy`` (vertical scale) "
"components. Remember to adjust glyph spacing to account for any changes, as "
"glyph transform doesn't affect how much space each glyph takes in the text. "
"Non-uniform scaling of this kind should be used sparingly, as fonts are "
"generally not designed to be displayed with stretching."
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:639
#, fuzzy
msgid "OpenType font features"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/ui/gui_using_fonts.rst:641
msgid ""
"Godot supports enabling OpenType font features, which are a standardized way "
"to define alternate characters that can be toggled without having to swap "
"font files entirely. Despite being named OpenType font features, these are "
"also supported in TrueType (``.ttf``) and WOFF/WOFF2 font files."
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:646
msgid ""
"Support for OpenType features highly depends on the font used. Some fonts "
"don't support any OpenType features, while other fonts can support dozens of "
"toggleable features."
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:650
#, fuzzy
msgid "There are 2 ways to use OpenType font features:"
msgstr "Ne postoje ograničenja prilikom korištenja Godot-a"

#: ../../docs/tutorials/ui/gui_using_fonts.rst:652
msgid "**Globally on a font file**"
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:663
msgid ""
"In the dialog that appears, look for the **Metadata Overrides > OpenType "
"Features** section on the sidebar on the right, click the **Features (0 of N "
"set)** text to expand the property, then click **Add Feature**:"
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:671
msgid "OpenType feature overrides in Advanced Import Settings"
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:673
msgid "**In a specific font usage (FontVariation)**"
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:675
msgid ""
"To use a font feature, create a FontVariation resource like you would do for "
"a :ref:`variable font <doc_using_fonts_variable_fonts>`, then load a font "
"file within the FontVariation resource:"
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:687
msgid "Loading a font file into a FontVariation resource"
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:689
msgid ""
"Scroll down to the FontVariation's **OpenType Features** section, click the "
"**Features (0 of N set)** text to expand the property, then click **Add "
"Feature** and select the desired feature in the dropdown:"
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:696
msgid "Specifying OpenType features in a FontVariation resource"
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:698
msgid ""
"For example, here's the `Inter <https://rsms.me/inter/>`__ font without the "
"*Slashed Zero* feature (top), then with the *Slashed Zero* OpenType feature "
"enabled (bottom):"
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:705
msgid "OpenType feature comparison (Inter)"
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:707
msgid ""
"You can disable ligatures and/or kerning for a specific font by adding "
"OpenType features, then unchecking them in the inspector:"
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:713
msgid "Disabling ligatures and kerning for a font"
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:718
msgid "System fonts"
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:722
msgid ""
"Loading system fonts is only supported on Windows, macOS, Linux, Android and "
"iOS."
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:724
msgid ""
"However, loading system fonts on Android is unreliable as there is no "
"official API for doing so. Godot has to rely on parsing system configuration "
"files, which can be modified by third-party Android vendors. This may result "
"in non-functional system font loading."
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:729
msgid ""
"System fonts are a different type of resource compared to imported fonts. "
"They are never actually imported into the project, but are loaded at run-"
"time. This has 2 benefits:"
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:733
msgid ""
"The fonts are not included within the exported PCK file, leading to a "
"smaller file size for the exported project."
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:735
msgid ""
"Since fonts are not included with the exported project, this avoids "
"licensing issues that would occur if proprietary system fonts were "
"distributed alongside the project."
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:739
msgid ""
"The engine automatically uses system fonts as fallback fonts, which makes it "
"possible to display CJK characters and emoji without having to load a custom "
"font. There are some restrictions that apply though, as mentioned in the :"
"ref:`Using emoji <doc_using_fonts_emoji>` section."
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:744
msgid ""
"Create a :ref:`class_SystemFont` resource in the location where you desire "
"to use the system font:"
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:750
#, fuzzy
msgid "Creating a SystemFont resource"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/ui/gui_using_fonts.rst:755
msgid "Specifying a font name to use in a SystemFont resource"
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:757
msgid ""
"You can either specify one or more font names explicitly (such as "
"``Arial``), or specify the name of a font *alias* that maps to a "
"\"standard\" default font for the system:"
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:764
msgid "Font alias"
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:764
msgid "macOS/iOS"
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:766
msgid "``sans-serif``"
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:766
msgid "Arial"
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:766
msgid "Helvetica"
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:766
#: ../../docs/tutorials/ui/gui_using_fonts.rst:768
#: ../../docs/tutorials/ui/gui_using_fonts.rst:770
#: ../../docs/tutorials/ui/gui_using_fonts.rst:772
#: ../../docs/tutorials/ui/gui_using_fonts.rst:774
msgid "*Handled by fontconfig*"
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:766
msgid "Roboto / Noto Sans"
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:768
msgid "``serif``"
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:768
msgid "Times New Roman"
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:768
msgid "Times"
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:768
msgid "Noto Serif"
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:770
msgid "``monospace``"
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:770
msgid "Courier New"
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:770
msgid "Courier"
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:770
#: ../../docs/tutorials/ui/gui_using_fonts.rst:774
msgid "Droid Sans Mono"
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:772
msgid "``cursive``"
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:772
msgid "Comic Sans MS"
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:772
msgid "Apple Chancery"
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:772
#, fuzzy
msgid "Dancing Script"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/ui/gui_using_fonts.rst:774
msgid "``fantasy``"
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:774
msgid "Gabriola"
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:774
msgid "Papyrus"
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:777
msgid ""
"On Android, Roboto is used for Latin/Cyrillic text and Noto Sans is used for "
"other languages' glyphs such as CJK. On third-party Android distributions, "
"the exact font selection may differ."
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:781
msgid ""
"If specifying more than one font, the first font that is found on the system "
"will be used (from top to bottom). Font names and aliases are case-"
"insensitive on all platforms."
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:785
msgid ""
"Like for font variations, you can save the SystemFont arrangement to a "
"resource file to reuse it in other places."
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:788
msgid ""
"Remember that different system fonts have different metrics, which means "
"that text that can fit within a rectangle on one platform may not be doing "
"so on another platform. Always reserve some additional space during "
"development so that labels can extend further if needed."
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:795
msgid ""
"Unlike Windows and macOS/iOS, the set of default fonts shipped on Linux "
"depends on the distribution. This means that on different Linux "
"distributions, different fonts may be displayed for a given system font name "
"or alias."
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:800
msgid ""
"It is also possible to load fonts at runtime even if they aren't installed "
"on the system. See :ref:`Runtime loading and saving "
"<doc_runtime_file_loading_and_saving_fonts>` for details."
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:807
msgid "Font prerendering"
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:809
msgid ""
"When using traditional rasterized fonts, Godot caches glyphs on a per-font "
"and per-size basis. This reduces stuttering, but it can still occur the "
"first time a glyph is displayed when running the project. This can be "
"especially noticeable at higher font sizes or on mobile devices."
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:814
msgid ""
"When using MSDF fonts, they only need to be rasterized once to a special "
"signed distance field texture. This means caching can be done purely on a "
"per-font basis, without taking the font size into consideration. However, "
"the initial rendering of MSDF fonts is slower compared to a traditional "
"rasterized font at a medium size."
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:820
msgid ""
"To avoid stuttering issues related to font rendering, it is possible to "
"*prerender* certain glyphs. This can be done for all glyphs you intend to "
"use (for optimal results), or only for common glyphs that are most likely to "
"appear during gameplay (to reduce file size). Glyphs that aren't pre-"
"rendered will be rasterized on-the-fly as usual."
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:828
msgid ""
"In both cases (traditional and MSDF), font rasterization is done on the CPU. "
"This means that the GPU performance doesn't affect how long it takes for "
"fonts to be rasterized."
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:841
msgid ""
"Move to the **Pre-render Configurations** tab of the Advanced Import "
"Settings dialog, then add a configuration by clicking the \"plus\" symbol:"
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:848
msgid ""
"Adding a new prerendering configuration in the Advanced Import Settings "
"dialog"
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:850
msgid ""
"After adding a configuration, make sure it is selected by clicking its name "
"once. You can also rename the configuration by double-clicking it."
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:853
msgid ""
"There are 2 ways to add glyphs to be prerendered to a given configuration. "
"It is possible to use both approaches in a cumulative manner:"
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:856
#, fuzzy
msgid "**Using text from translations**"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/ui/gui_using_fonts.rst:858
msgid ""
"For most projects, this approach is the most convenient to use, as it "
"automatically sources text from your language translations. The downside is "
"that it can only be used if your project supports :ref:`internationalization "
"<doc_internationalizing_games>`. Otherwise, stick to the \"Using custom "
"text\" approach described below."
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:864
msgid ""
"After adding translations to the Project Settings, use the **Glyphs from the "
"Translations** tab to check translations by double-clicking them, then click "
"**Shape All Strings in the Translations and Add Glyphs** at the bottom:"
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:872
msgid ""
"Enabling prerendering in the Advanced Import Settings dialog with the Glyphs "
"from the Translations tab"
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:872
msgid ""
"Enabling prerendering in the Advanced Import Settings dialog with the "
"**Glyphs from the Translations** tab"
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:876
msgid ""
"The list of prerendered glyphs is not automatically updated when "
"translations are updated, so you need to repeat this process if your "
"translations have changed significantly."
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:880
msgid "**Using custom text**"
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:882
msgid ""
"While it requires manually specifying text that will appear in the game, "
"this is the most efficient approach for games which don't feature user text "
"input. This approach is worth exploring for mobile games to reduce the file "
"size of the distributed app."
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:887
msgid ""
"To use existing text as a baseline for prerendering, go to the **Glyphs from "
"the Text** sub-tab of the Advanced Import Settings dialog, enter text in the "
"window on the right, then click **Shape Text and Add Glyphs** at the bottom "
"of the dialog:"
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:896
msgid ""
"Enabling prerendering in the Advanced Import Settings dialog, Glyphs from "
"the Text tab"
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:896
msgid ""
"Enabling prerendering in the Advanced Import Settings dialog with the "
"**Glyphs from the Text** tab"
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:900
msgid ""
"If your project supports :ref:`internationalization "
"<doc_internationalizing_games>`, you can paste the contents of your CSV or "
"PO files in the above box to quickly prerender all possible characters that "
"may be rendered during gameplay (excluding user-provided or non-translatable "
"strings)."
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:905
msgid "**By enabling character sets**"
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:907
msgid ""
"The second method requires less configuration and fewer updates if your "
"game's text changes, and is more suited to text-heavy games or multiplayer "
"games with chat. On the other hand, it may cause glyphs that never show up "
"in the game to be prerendered, which is less efficient in terms of file size."
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:912
msgid ""
"To use existing text as a baseline for prerendering, go to the **Glyphs from "
"the Character Map** sub-tab of the Advanced Import Settings dialog, then "
"*double-click* character sets to be enabled on the right:"
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:920
msgid ""
"Enabling prerendering in the Advanced Import Settings dialog, Glyphs from "
"the Character Map tab"
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:920
msgid ""
"Enabling prerendering in the Advanced Import Settings dialog with the "
"**Glyphs from the Character Map** tab"
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:922
msgid ""
"To ensure full prerendering, the character sets you need to enable depend on "
"which languages are supported in your game. For English, only **Basic "
"Latin** needs to be enabled. Enabling **Latin-1 Supplement** as well allows "
"fully covering many more languages, such as French, German and Spanish. For "
"Russian, **Cyrillic** needs to be enabled, and so on."
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:929
#, fuzzy
msgid "Default project font properties"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/ui/gui_using_fonts.rst:931
msgid ""
"In the **GUI > Theme** section of the advanced Project Settings, you can "
"choose how the default font should be rendered:"
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:934
msgid ""
"**Default Font Antialiasing:** Controls the :ref:`antialiasing "
"<doc_using_fonts_antialiasing>` method used for the default project font."
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:937
msgid ""
"**Default Font Hinting:** Controls the :ref:`hinting "
"<doc_using_fonts_hinting>` method used for the default project font."
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:940
msgid ""
"**Default Font Subpixel Positioning:** Controls the :ref:`subpixel "
"positioning <doc_using_fonts_subpixel_positioning>` method for the default "
"project font."
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:943
msgid ""
"**Default Font Multichannel Signed Distance Field:** If ``true``, makes the "
"default project font use :ref:`MSDF font rendering <doc_using_fonts_msdf>` "
"instead of traditional rasterization."
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:946
msgid ""
"**Default Font Generate Mipmaps:** If ``true``, enables :ref:`mipmap "
"<doc_using_fonts_mipmaps>` generation and usage for the default project font."
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:952
msgid ""
"These project settings *only* affect the default project font (the one that "
"is hardcoded in the engine binary)."
msgstr ""

#: ../../docs/tutorials/ui/gui_using_fonts.rst:955
msgid ""
"Custom fonts' properties are governed by their respective import options "
"instead. You can use the **Import Defaults** section of the Project Settings "
"dialog to override default import options for custom fonts."
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:4
msgid "BBCode in RichTextLabel"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:9
msgid ""
":ref:`class_Label` nodes are great for displaying basic text, but they have "
"limitations. If you want to change the color of the text, or its alignment, "
"you can only do that to the entire label. You can't make a part of the text "
"have another color, or have a part of the text centered. To get around these "
"limitations, you would use a :ref:`class_RichTextLabel`."
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:14
msgid ""
":ref:`class_RichTextLabel` allows for complex formatting of text using a "
"markup syntax or the built-in API. It uses BBCodes for the markup syntax, a "
"system of tags that designate formatting rules for a part of the text. You "
"may be familiar with them if you ever used forums (also known as `bulletin "
"boards`, hence the \"BB\" in \"BBCode\")."
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:19
msgid ""
"Unlike Label, RichTextLabel also comes with its own vertical scrollbar. This "
"scrollbar is automatically displayed if the text does not fit within the "
"control's size. The scrollbar can be disabled by unchecking the **Scroll "
"Active** property in the RichTextLabel inspector."
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:24
msgid ""
"Note that the BBCode tags can also be used to some extent in the XML source "
"of the class reference. For more information, see :ref:"
"`doc_class_reference_primer`."
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:29
#, fuzzy
msgid ""
"You can see how BBCode in RichTextLabel works in action using the `Rich Text "
"Label with BBCode demo project <https://github.com/godotengine/godot-demo-"
"projects/tree/master/gui/rich_text_bbcode>`__."
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati različite Godo demo projekte "
"`Godot demo projects <https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:33
msgid "Using BBCode"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:35
msgid ""
"By default, :ref:`class_RichTextLabel` functions like a normal :ref:"
"`class_Label`. It has the :ref:`property_text "
"<class_RichTextLabel_property_text>` property, which you can edit to have "
"uniformly formatted text. To be able to use BBCode for rich text formatting, "
"you need to turn on the BBCode mode by setting :ref:`bbcode_enabled "
"<class_RichTextLabel_property_bbcode_enabled>`. After that, you can edit "
"the :ref:`text <class_RichTextLabel_property_text>` property using available "
"tags. Both properties are located at the top of the inspector after "
"selecting a RichTextLabel node."
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:45
msgid ""
"For example, ``BBCode [color=green]test[/color]`` would render the word "
"\"test\" with a green color."
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:50
msgid ""
"Most BBCodes consist of 3 parts: the opening tag, the content and the "
"closing tag. The opening tag delimits the start of the formatted part, and "
"can also carry some configuration options. Some opening tags, like the "
"``color`` one shown above, also require a value to work. Other opening tags "
"may accept multiple options (separated by spaces within the opening tag). "
"The closing tag delimits the end of the formatted part. In some cases, both "
"the closing tag and the content can be omitted."
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:58
msgid ""
"Unlike BBCode in HTML, leading/trailing whitespace is not removed by a "
"RichTextLabel upon display. Duplicate spaces are also displayed as-is in the "
"final output. This means that when displaying a code block in a "
"RichTextLabel, you don't need to use a preformatted text tag."
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:73
msgid ""
"RichTextLabel doesn't support entangled BBCode tags. For example, instead of "
"using:"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:80
msgid "Use:"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:89
msgid "Handling user input safely"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:91
msgid ""
"In a scenario where users may freely input text (such as chat in a "
"multiplayer game), you should make sure users cannot use arbitrary BBCode "
"tags that will be parsed by RichTextLabel. This is to avoid inappropriate "
"use of formatting, which can be problematic if ``[url]`` tags are handled by "
"your RichTextLabel (as players may be able to create clickable links to "
"phishing sites or similar)."
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:97
msgid ""
"Using RichTextLabel's ``[lb]`` and/or ``[rb]`` tags, we can replace the "
"opening and/or closing brackets of any BBCode tag in a message with those "
"escaped tags. This prevents users from using BBCode that will be parsed as "
"tags – instead, the BBCode will be displayed as text."
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:106
msgid ""
"Example of unescaped user input resulting in BBCode injection (2nd line) and "
"escaped user input (3rd line)"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:108
msgid "The above image was created using the following script:"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:137
msgid "Stripping BBCode tags"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:139
msgid ""
"For certain use cases, it can be desired to remove BBCode tags from the "
"string. This is useful when displaying the RichTextLabel's text in another "
"Control that does not support BBCode (such as a tooltip):"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:155
msgid ""
"Removing BBCode tags entirely isn't advised for user input, as it can modify "
"the displayed text without users understanding why part of their message was "
"removed. :ref:`Escaping user input "
"<doc_bbcode_in_richtextlabel_handling_user_input_safely>` should be "
"preferred instead."
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:164
msgid ""
"In most cases, you can use BBCode directly as-is since text formatting is "
"rarely a heavy task. However, with particularly large RichTextLabels (such "
"as console logs spanning thousands of lines), you may encounter stuttering "
"during gameplay when the RichTextLabel's text is updated."
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:169
#, fuzzy
msgid "There are several ways to alleviate this:"
msgstr "Ne postoje ograničenja prilikom korištenja Godot-a"

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:171
msgid ""
"Use the ``append_text()`` function instead of appending to the ``text`` "
"property. This function will only parse BBCode for the added text, rather "
"than parsing BBCode from the entire ``text`` property."
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:174
msgid ""
"Use ``push_[tag]()`` and ``pop()`` functions to add tags to RichTextLabel "
"instead of using BBCode."
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:176
msgid ""
"Enable the **Threading > Threaded** property in RichTextLabel. This won't "
"speed up processing, but it will prevent the main thread from blocking, "
"which avoids stuttering during gameplay. Only enable threading if it's "
"actually needed in your project, as threading has some overhead."
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:184
msgid "Using push_[tag]() and pop() functions instead of BBCode"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:186
msgid ""
"If you don't want to use BBCode for performance reasons, you can use "
"functions provided by RichTextLabel to create formatting tags without "
"writing BBCode in the text."
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:190
msgid ""
"Every BBCode tag (including effects) has a ``push_[tag]()`` function (where "
"``[tag]`` is the tag's name). There are also a few convenience functions "
"available, such as ``push_bold_italics()`` that combines both "
"``push_bold()`` and ``push_italics()`` into a single tag. See the :ref:"
"`RichTextLabel class reference <class_RichTextLabel>` for a complete list of "
"``push_[tag]()`` functions."
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:197
msgid ""
"The ``pop()`` function is used to end *any* tag. Since BBCode is a tag "
"*stack*, using ``pop()`` will close the most recently started tags first."
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:200
msgid ""
"The following script will result in the same visual output as using ``BBCode "
"[color=green]test [i]example[/i][/color]``:"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:218
msgid ""
"Do **not** set the ``text`` property directly when using formatting "
"functions. Appending to the ``text`` property will erase all modifications "
"made to the RichTextLabel using the ``append_text()``, ``push_[tag]()`` and "
"``pop()`` functions."
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:224
#: ../../docs/contributing/development/core_and_modules/inheritance_class_tree.rst:10
msgid "Reference"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:231
msgid "Tag"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:0
msgid "**b**"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:0
msgid ""
"Makes ``{text}`` use the bold (or bold italics) font of ``RichTextLabel``."
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:237
msgid "``[b]{text}[/b]``"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:0
msgid "**i**"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:0
msgid ""
"Makes ``{text}`` use the italics (or bold italics) font of ``RichTextLabel``."
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:242
msgid "``[i]{text}[/i]``"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:0
msgid "**u**"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:0
msgid "Makes ``{text}`` underlined."
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:247
msgid "``[u]{text}[/u]``"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:0
msgid "**s**"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:0
msgid "Makes ``{text}`` strikethrough."
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:252
msgid "``[s]{text}[/s]``"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:0
msgid "**code**"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:0
msgid "Makes ``{text}`` use the mono font of ``RichTextLabel``."
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:257
msgid "``[code]{text}[/code]``"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:0
msgid "**p**"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:0
msgid ""
"Adds new paragraph with ``{text}``. Supports configuration options, see :ref:"
"`doc_bbcode_in_richtextlabel_paragraph_options`."
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:0
msgid "``[p]{text}[/p]``"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:0
msgid "``[p {options}]{text}[/p]``"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:0
msgid "**center**"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:0
msgid "Makes ``{text}`` horizontally centered."
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:0
msgid "Same as ``[p align=center]``."
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:270
msgid "``[center]{text}[/center]``"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:0
msgid "**left**"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:0
msgid "Makes ``{text}`` horizontally left-aligned."
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:0
msgid "Same as ``[p align=left]``."
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:276
msgid "``[left]{text}[/left]``"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:0
msgid "**right**"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:0
msgid "Makes ``{text}`` horizontally right-aligned."
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:0
msgid "Same as ``[p align=right]``."
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:282
msgid "``[right]{text}[/right]``"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:0
msgid "**fill**"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:0
msgid "Makes ``{text}`` fill the full width of ``RichTextLabel``."
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:0
msgid "Same as ``[p align=fill]``."
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:288
msgid "``[fill]{text}[/fill]``"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:0
msgid "**indent**"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:0
msgid ""
"Indents ``{text}`` once. The indentation width is the same as with ``[ul]`` "
"or ``[ol]``, but without a bullet point."
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:294
msgid "``[indent]{text}[/indent]``"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:0
msgid "**url**"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:0
msgid ""
"Creates a hyperlink (underlined and clickable text). Can contain optional "
"``{text}`` or display ``{link}`` as is."
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:0
msgid ""
"**Must be handled with the \"meta_clicked\" signal to have an effect,** see :"
"ref:`doc_bbcode_in_richtextlabel_handling_url_tag_clicks`."
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:0
msgid "``[url]{link}[/url]``"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:0
msgid "``[url={link}]{text}[/url]``"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:0
msgid "**hint**"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:0
msgid ""
"Creates a tooltip hint that is displayed when hovering the text with the "
"mouse. Tooltip text should not be quoted (quotes will appear as-is in the "
"tooltip otherwise)."
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:0
msgid "``[hint={tooltip text displayed on hover}]{text}[/hint]``"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:0
msgid "**img**"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:0
msgid ""
"Inserts an image from the ``{path}`` (can be any valid :ref:"
"`class_Texture2D` resource)."
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:0
msgid ""
"If ``{width}`` is provided, the image will try to fit that width maintaining "
"the aspect ratio."
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:0
msgid ""
"If both ``{width}`` and ``{height}`` are provided, the image will be scaled "
"to that size."
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:0
msgid ""
"If ``{valign}`` configuration is provided, the image will try to align to "
"the surrounding text, see :ref:`doc_bbcode_in_richtextlabel_image_alignment`."
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:0
msgid ""
"Supports configuration options, see :ref:"
"`doc_bbcode_in_richtextlabel_image_options`."
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:0
msgid "``[img]{path}[/img]``"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:0
msgid "``[img={width}]{path}[/img]``"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:0
msgid "``[img={width}x{height}]{path}[/img]``"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:0
msgid "``[img={valign}]{path}[/img]``"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:0
msgid "``[img {options}]{path}[/img]``"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:0
msgid "**font**"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:0
msgid "Makes ``{text}`` use a font resource from the ``{path}``."
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:0
msgid ""
"Supports configuration options, see :ref:"
"`doc_bbcode_in_richtextlabel_font_options`."
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:0
msgid "``[font={path}]{text}[/font]``"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:0
msgid "``[font {options}]{text}[/font]``"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:0
msgid "**font_size**"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:0
msgid "Use custom font size for ``{text}``."
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:335
msgid "``[font_size={size}]{text}[/font_size]``"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:0
msgid "**dropcap**"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:0
msgid ""
"Use a different font size and color for ``{text}``, while making the tag's "
"contents span multiple lines if it's large enough."
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:0
msgid ""
"A `drop cap <https://www.computerhope.com/jargon/d/dropcap.htm>`__ is "
"typically one uppercase character, but ``[dropcap]`` supports containing "
"multiple characters. ``margins`` values are comma-separated and can be "
"positive, zero or negative. Negative top and bottom margins are particularly "
"useful to allow the rest of the paragraph to display below the dropcap."
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:346
msgid ""
"``[dropcap font_size={size} color={color} margins={left},{top},{right},"
"{bottom}]{text}[/dropcap]``"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:0
msgid "**opentype_features**"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:0
msgid ""
"Enables custom OpenType font features for ``{text}``. Features must be "
"provided as a comma-separated ``{list}``."
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:0
msgid "``[opentype_features={list}]``"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:0
msgid "``{text}``"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:0
msgid "``[/opentype_features]``"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:0
msgid "**lang**"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:0
msgid ""
"Overrides the language for ``{text}`` that is set by the **BiDi > Language** "
"property in :ref:`class_RichTextLabel`. ``{code}`` must be an ISO :ref:"
"`language code <doc_locales>`. This can be used to enforce the use of a "
"specific script for a language without starting a new paragraph. Some font "
"files may contain script-specific substitutes, in which case they will be "
"used."
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:363
msgid "``[lang={code}]{text}[/lang]``"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:0
#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:556
msgid "**color**"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:0
msgid ""
"Changes the color of ``{text}``. Color must be provided by a common name "
"(see :ref:`doc_bbcode_in_richtextlabel_named_colors`) or using the HEX "
"format (e.g. ``#ff00ff``, see :ref:`doc_bbcode_in_richtextlabel_hex_colors`)."
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:370
msgid "``[color={code/name}]{text}[/color]``"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:0
#, fuzzy
msgid "**bgcolor**"
msgstr "**Za uređivač:**"

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:0
msgid ""
"Draws the color behind ``{text}``. This can be used to highlight text. "
"Accepts same values as the ``color`` tag."
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:376
msgid "``[bgcolor={code/name}]{text}[/bgcolor]``"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:0
#, fuzzy
msgid "**fgcolor**"
msgstr "**Za uređivač:**"

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:0
msgid ""
"Draws the color in front of ``{text}``. This can be used to \"redact\" text "
"by using an opaque foreground color. Accepts same values as the ``color`` "
"tag."
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:382
msgid "``[fgcolor={code/name}]{text}[/fgcolor]``"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:0
msgid "**outline_size**"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:0
msgid "Use custom font outline size for ``{text}``."
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:0
msgid "``[outline_size={size}]``"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:0
msgid "``[/outline_size]``"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:0
#, fuzzy
msgid "**outline_color**"
msgstr "**Za uređivač:**"

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:0
msgid ""
"Use custom outline color for ``{text}``. Accepts same values as the "
"``color`` tag."
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:0
msgid "``[outline_color={code/name}]``"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:0
msgid "``[/outline_color]``"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:0
msgid "**table**"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:0
msgid ""
"Creates a table with the ``{number}`` of columns. Use the ``cell`` tag to "
"define table cells."
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:402
msgid "``[table={number}]{cells}[/table]``"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:0
msgid "**cell**"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:0
msgid "Adds a cell with ``{text}`` to the table."
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:0
msgid ""
"If ``{ratio}`` is provided, the cell will try to expand to that value "
"proportionally to other cells and their ratio values."
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:0
msgid ""
"Supports configuration options, see :ref:"
"`doc_bbcode_in_richtextlabel_cell_options`."
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:0
msgid "``[cell]{text}[/cell]``"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:0
msgid "``[cell={ratio}]{text}[/cell]``"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:0
msgid "``[cell {options}]{text}[/cell]``"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:0
msgid "**ul**"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:0
msgid ""
"Adds an unordered list. List ``{items}`` must be provided by putting one "
"item per line of text."
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:0
msgid ""
"The bullet point can be customized using the ``{bullet}`` parameter, see :"
"ref:`doc_bbcode_in_richtextlabel_unordered_list_bullet`."
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:0
msgid "``[ul]{items}[/ul]``"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:0
msgid "``[ul bullet={bullet}]{items}[/ul]``"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:0
msgid "**ol**"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:0
msgid ""
"Adds an ordered (numbered) list of the given ``{type}`` (see :ref:"
"`doc_bbcode_in_richtextlabel_list_types`). List ``{items}`` must be provided "
"by putting one item per line of text."
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:427
msgid "``[ol type={type}]{items}[/ol]``"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:0
msgid "**lb**, **rb**"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:0
msgid "Adds ``[`` and ``]`` respectively. Allows escaping BBCode markup."
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:0
msgid ""
"These are self-closing tags, which means you do not need to close them (and "
"there is no ``[/lb]`` or ``[/rb]`` closing tag)."
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:0
msgid "``[lb]b[rb]text[lb]/b[rb]`` will display as ``[b]text[/b]``."
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:0
msgid ""
"Several Unicode control characters can be added using their own self-closing "
"tags."
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:0
msgid "This can result in easier maintenance compared to pasting those"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:0
msgid "control characters directly in the text."
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:0
msgid ""
"``[lrm]`` (left-to-right mark), ``[rlm]`` (right-to-left mark), ``[lre]`` "
"(left-to-right embedding),"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:0
msgid ""
"``[rle]`` (right-to-left embedding), ``[lro]`` (left-to-right override), "
"``[rlo]`` (right-to-left override),"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:0
msgid ""
"``[pdf]`` (pop directional formatting), ``[alm]`` (Arabic letter mark), "
"``[lri]`` (left-to-right isolate),"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:0
msgid ""
"``[rli]`` (right-to-left isolate), ``[fsi]`` (first strong isolate), "
"``[pdi]`` (pop directional isolate),"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:0
msgid ""
"``[zwj]`` (zero-width joiner), ``[zwnj]`` (zero-width non-joiner), ``[wj]`` "
"(word joiner),"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:0
msgid "``[shy]`` (soft hyphen)"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:449
msgid ""
"Tags for bold (``[b]``) and italics (``[i]``) formatting work best if the "
"appropriate custom fonts are set up in the RichTextLabelNode's theme "
"overrides. If no custom bold or italic fonts are defined, `faux bold and "
"italic fonts <https://fonts.google.com/knowledge/glossary/"
"faux_fake_pseudo_synthesized>`__ will be generated by Godot. These fonts "
"rarely look good in comparison to hand-made bold/italic font variants."
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:455
msgid ""
"The monospaced (``[code]``) tag **only** works if a custom font is set up in "
"the RichTextLabel node's theme overrides. Otherwise, monospaced text will "
"use the regular font."
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:458
msgid "There are no BBCode tags to control vertical centering of text yet."
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:460
msgid "Options can be skipped for all tags."
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:465
msgid "Paragraph options"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:467
msgid "**align**"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:470
#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:480
#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:490
#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:500
#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:510
#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:559
#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:569
#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:579
#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:589
#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:631
#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:641
#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:681
#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:692
#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:702
msgid "`Values`"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:470
msgid "``left``, ``center``, ``right``, ``fill``"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:472
#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:482
#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:492
#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:502
#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:512
#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:561
#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:571
#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:581
#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:591
#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:633
#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:643
#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:683
#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:694
#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:704
msgid "`Default`"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:472
msgid "``left``"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:475
msgid "Text horizontal alignment."
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:477
msgid "**bidi_override**, **st**"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:480
msgid ""
"``default``, ``uri``, ``file``, ``email``, ``list``, ``none``, ``custom``"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:482
msgid "``default``"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:485
msgid "Structured text override."
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:487
msgid "**direction**, **dir**"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:490
msgid "``ltr``, ``rtl``, ``auto``"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:492
#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:502
#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:561
#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:571
#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:581
#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:591
#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:633
#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:643
#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:694
#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:704
msgid "Inherit"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:495
#, fuzzy
msgid "Base BiDi direction."
msgstr "Uvod"

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:497
msgid "**language**, **lang**"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:500
msgid "ISO language codes. See :ref:`doc_locales`"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:505
msgid ""
"Locale override. Some font files may contain script-specific substitutes, in "
"which case they will be used."
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:507
msgid "**tab_stops**"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:510
msgid "List of floating-point numbers, e.g. ``10.0,30.0``"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:512
msgid "Width of the space character in the font"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:515
msgid ""
"Overrides the horizontal offsets for each tab character. When the end of the "
"list is reached, the tab stops will loop over. For example, if you set "
"``tab_stops`` to ``10.0,30.0``, the first tab will be at ``10`` pixels, the "
"second tab will be at ``10 + 30 = 40`` pixels, and the third tab will be at "
"``10 + 30 + 10 = 50`` pixels from the origin of the RichTextLabel."
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:524
msgid "Handling ``[url]`` tag clicks"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:526
msgid ""
"By default, ``[url]`` tags do nothing when clicked. This is to allow "
"flexible use of ``[url]`` tags rather than limiting them to opening URLs in "
"a web browser."
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:529
msgid ""
"To handle clicked ``[url]`` tags, connect the ``RichTextLabel`` node's :ref:"
"`meta_clicked <class_RichTextLabel_signal_meta_clicked>` signal to a script "
"function."
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:532
msgid ""
"For example, the following method can be connected to ``meta_clicked`` to "
"open clicked URLs using the user's default web browser::"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:542
msgid ""
"For more advanced use cases, it's also possible to store JSON in an "
"``[url]`` tag's option and parse it in the function that handles the "
"``meta_clicked`` signal. For example:"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:554
msgid "Image options"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:559
#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:692
#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:702
msgid "Color name or color in HEX format"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:564
msgid "Color tint of the image (modulation)."
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:566
msgid "**height**"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:569
#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:579
msgid "Number in pixels"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:574
msgid "Target height of the image."
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:576
msgid "**width**"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:584
msgid "Target width of the image."
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:586
msgid "**region**"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:589
msgid "x,y,width,height in pixels"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:594
msgid ""
"Region rect of the image. This can be used to display a single image from a "
"spritesheet."
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:599
msgid "Image vertical alignment"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:601
msgid ""
"When a vertical alignment value is provided with the ``[img]`` tag the image "
"will try to align itself against the surrounding text. Alignment is "
"performed using a vertical point of the image and a vertical point of the "
"text. There are 3 possible points on the image (``top``, ``center``, and "
"``bottom``) and 4 possible points on the text (``top``, ``center``, "
"``baseline``, and ``bottom``), which can be used in any combination."
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:608
msgid ""
"To specify both points, use their full or short names as a value of the "
"image tag:"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:615
msgid ""
"You can also specify just one value (``top``, ``center``, or ``bottom``) to "
"make use of a corresponding preset (``top-top``, ``center-center``, and "
"``bottom-bottom`` respectively)."
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:619
msgid ""
"Short names for the values are ``t`` (``top``), ``c`` (``center``), ``l`` "
"(``baseline``), and ``b`` (``bottom``)."
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:626
#, fuzzy
msgid "Font options"
msgstr "Funkcije"

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:628
msgid "**name**, **n**"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:631
msgid "A valid Font resource path."
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:636
msgid "Font resource path."
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:638
msgid "**size**, **s**"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:641
msgid "Number in pixels."
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:646
msgid "Custom font size."
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:652
msgid "Named colors"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:654
msgid ""
"For tags that allow specifying a color by name you can use names of the "
"constants from the built-in :ref:`class_Color` class. Named classes can be "
"specified in a number of styles using different casings: ``DARK_RED``, "
"``DarkRed``, and ``darkred`` will give the same exact result."
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:662
msgid "Hexadecimal color codes"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:664
msgid ""
"For opaque RGB colors, any valid 6-digit hexadecimal code is supported, e.g. "
"``[color=#ffffff]white[/color]``. Shorthand RGB color codes such as ``#6f2`` "
"(equivalent to ``#66ff22``) are also supported."
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:668
msgid ""
"For transparent RGB colors, any RGBA 8-digit hexadecimal code can be used, e."
"g. ``[color=#ffffff88]translucent white[/color]``. Note that the alpha "
"channel is the **last** component of the color code, not the first one. "
"Short RGBA color codes such as ``#6f28`` (equivalent to ``#66ff2288``) are "
"supported as well."
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:676
msgid "Cell options"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:678
msgid "**expand**"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:681
msgid "Integer number"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:686
msgid ""
"Cell expansion ratio. This defines which cells will try to expand to "
"proportionally to other cells and their expansion ratios."
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:689
msgid "**border**"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:697
msgid "Cell border color."
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:699
msgid "**bg**"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:707
msgid ""
"Cell background color. For alternating odd/even row backgrounds, you can use "
"``bg=odd_color,even_color``."
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:713
msgid "Unordered list bullet"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:715
msgid ""
"By default, the ``[ul]`` tag uses the ``U+2022`` \"Bullet\" Unicode glyph as "
"the bullet character. This behavior is similar to web browsers. The bullet "
"character can be customized using ``[ul bullet={bullet}]``. If provided, "
"this ``{bullet}`` parameter must be a *single* character with no enclosing "
"quotes (for example, ``[bullet=*]``). Additional characters are ignored. The "
"bullet character's width does not affect the list's formatting."
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:722
msgid ""
"See `Bullet (typography) on Wikipedia <https://en.wikipedia.org/wiki/"
"Bullet_(typography)>`__ for a list of common bullet characters that you can "
"paste directly in the ``bullet`` parameter."
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:728
msgid "Ordered list types"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:730
msgid ""
"Ordered lists can be used to automatically mark items with numbers or "
"letters in ascending order. This tag supports the following type options:"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:734
msgid "``1`` - Numbers, using language specific numbering system if possible."
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:735
msgid "``a``, ``A`` - Lower and upper case Latin letters."
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:736
msgid "``i``, ``I`` - Lower and upper case Roman numerals."
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:739
msgid "Text effects"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:741
msgid ""
"BBCode can also be used to create different text effects that can optionally "
"be animated. Five customizable effects are provided out of the box, and you "
"can easily create your own. By default, animated effects will pause :ref:"
"`when the SceneTree is paused <doc_pausing_games>`. You can change this "
"behavior by adjusting the RichTextLabel's **Process > Mode** property."
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:747
msgid ""
"All examples below mention the default values for options in the listed tag "
"format."
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:751
msgid ""
"Text effects that move characters' position may result in characters being "
"clipped by the RichTextLabel node bounds."
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:754
msgid ""
"You can resolve this by disabling **Control > Layout > Clip Contents** in "
"the inspector after selecting the RichTextLabel node, or ensuring there is "
"enough margin added around the text by using line breaks above and below the "
"line using the effect."
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:760
msgid "Pulse"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:764
msgid ""
"Pulse creates an animated pulsing effect that multiplies each character's "
"opacity and color. It can be used to bring attention to specific text. Its "
"tag format is ``[pulse freq=1.0 color=#ffffff40 ease=-2.0]{text}[/pulse]``."
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:768
msgid ""
"``freq`` controls the frequency of the half-pulsing cycle (higher is "
"faster). A full pulsing cycle takes ``2 * (1.0 / freq)`` seconds. ``color`` "
"is the target color multiplier for blinking. The default mostly fades out "
"text, but not entirely. ``ease`` is the easing function exponent to use. "
"Negative values provide in-out easing, which is why the default is ``-2.0``."
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:775
msgid "Wave"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:779
msgid ""
"Wave makes the text go up and down. Its tag format is ``[wave amp=50.0 "
"freq=5.0 connected=1]{text}[/wave]``."
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:782
msgid ""
"``amp`` controls how high and low the effect goes, and ``freq`` controls how "
"fast the text goes up and down. A ``freq`` value of ``0`` will result in no "
"visible waves, and negative ``freq`` values won't display any waves either. "
"If ``connected`` is ``1`` (default), glyphs with ligatures will be moved "
"together. If ``connected`` is ``0``, each glyph is moved individually even "
"if they are joined by ligatures. This can work around certain rendering "
"issues with font ligatures."
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:791
msgid "Tornado"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:795
msgid ""
"Tornado makes the text move around in a circle. Its tag format is ``[tornado "
"radius=10.0 freq=1.0 connected=1]{text}[/tornado]``."
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:798
msgid ""
"``radius`` is the radius of the circle that controls the offset, ``freq`` is "
"how fast the text moves in a circle. A ``freq`` value of ``0`` will pause "
"the animation, while negative ``freq`` will play the animation backwards. If "
"``connected`` is ``1`` (default), glyphs with ligatures will be moved "
"together. If ``connected`` is ``0``, each glyph is moved individually even "
"if they are joined by ligatures. This can work around certain rendering "
"issues with font ligatures."
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:807
msgid "Shake"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:811
msgid ""
"Shake makes the text shake. Its tag format is ``[shake rate=20.0 level=5 "
"connected=1]{text}[/shake]``."
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:814
msgid ""
"``rate`` controls how fast the text shakes, ``level`` controls how far the "
"text is offset from the origin. If ``connected`` is ``1`` (default), glyphs "
"with ligatures will be moved together. If ``connected`` is ``0``, each glyph "
"is moved individually even if they are joined by ligatures. This can work "
"around certain rendering issues with font ligatures."
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:821
msgid "Fade"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:825
msgid ""
"Fade creates a static fade effect that multiplies each character's opacity. "
"Its tag format is ``[fade start=4 length=14]{text}[/fade]``."
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:828
msgid ""
"``start`` controls the starting position of the falloff relative to where "
"the fade command is inserted, ``length`` controls over how many characters "
"should the fade out take place."
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:833
msgid "Rainbow"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:837
msgid ""
"Rainbow gives the text a rainbow color that changes over time. Its tag "
"format is ``[rainbow freq=1.0 sat=0.8 val=0.8]{text}[/rainbow]``."
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:840
msgid ""
"``freq`` is the number of full rainbow cycles per second, ``sat`` is the "
"saturation of the rainbow, ``val`` is the value of the rainbow. A ``freq`` "
"value of ``0`` will pause the animation, while negative ``freq`` will play "
"the animation backwards."
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:845
msgid ""
"Font outlines are *not* affected by the rainbow effect (they keep their "
"original color). Existing font colors are overridden by the rainbow effect. "
"However, CanvasItem's **Modulate** and **Self Modulate** properties will "
"affect how the rainbow effect looks, as modulation multiplies its final "
"colors."
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:851
msgid "Custom BBCode tags and text effects"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:853
msgid ""
"You can extend the :ref:`class_RichTextEffect` resource type to create your "
"own custom BBCode tags. Create a new script file that extends the :ref:"
"`class_RichTextEffect` resource type and give the script a ``class_name`` so "
"that the effect can be selected in the inspector. Add the ``@tool`` "
"annotation to your GDScript file if you wish to have these custom effects "
"run within the editor itself. The RichTextLabel does not need to have a "
"script attached, nor does it need to be running in ``tool`` mode. The new "
"effect can be registered in the Inspector by adding it to the **Markup > "
"Custom Effects** array, or in code with the :ref:`install_effect() "
"<class_RichTextLabel_method_install_effect>` method:"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:866
msgid ""
"Selecting a custom RichTextEffect after saving a script that extends "
"RichTextEffect with a ``class_name``"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:870
msgid ""
"If the custom effect is not registered within the RichTextLabel's **Markup > "
"Custom Effects** property, no effect will be visible and the original tag "
"will be left as-is."
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:874
msgid ""
"There is only one function that you need to extend: "
"``_process_custom_fx(char_fx)``. Optionally, you can also provide a custom "
"BBCode identifier simply by adding a member name ``bbcode``. The code will "
"check the ``bbcode`` property automatically or will use the name of the file "
"to determine what the BBCode tag should be."
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:880
msgid "``_process_custom_fx``"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:882
msgid ""
"This is where the logic of each effect takes place and is called once per "
"glyph during the draw phase of text rendering. This passes in a :ref:"
"`class_CharFXTransform` object, which holds a few variables to control how "
"the associated glyph is rendered:"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:886
msgid ""
"``identity`` specifies which custom effect is being processed. You should "
"use that for code flow control."
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:888
msgid "``outline`` is ``true`` if effect is called for drawing text outline."
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:889
msgid ""
"``range`` tells you how far into a given custom effect block you are in as "
"an index."
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:891
msgid ""
"``elapsed_time`` is the total amount of time the text effect has been "
"running."
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:892
msgid ""
"``visible`` will tell you whether the glyph is visible or not and will also "
"allow you to hide a given portion of text."
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:894
msgid ""
"``offset`` is an offset position relative to where the given glyph should "
"render under normal circumstances."
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:896
msgid "``color`` is the color of a given glyph."
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:897
msgid ""
"``glyph_index`` and ``font`` is glyph being drawn and font data resource "
"used to draw it."
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:898
msgid ""
"Finally, ``env`` is a :ref:`class_Dictionary` of parameters assigned to a "
"given custom effect. You can use :ref:`get() <class_Dictionary_method_get>` "
"with an optional default value to retrieve each parameter, if specified by "
"the user. For example ``[custom_fx spread=0.5 color=#FFFF00]test[/"
"custom_fx]`` would have a float ``spread`` and Color ``color`` parameters in "
"its ``env`` Dictionary. See below for more usage examples."
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:904
msgid ""
"The last thing to note about this function is that it is necessary to return "
"a boolean ``true`` value to verify that the effect processed correctly. This "
"way, if there's a problem with rendering a given glyph, it will back out of "
"rendering custom effects entirely until the user fixes whatever error "
"cropped up in their custom effect logic."
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:909
msgid "Here are some examples of custom effects:"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:912
msgid "Ghost"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:935
msgid "Matrix"
msgstr ""

#: ../../docs/tutorials/ui/bbcode_in_richtextlabel.rst:973
msgid "This will add a few new BBCode commands, which can be used like so:"
msgstr ""

#: ../../docs/tutorials/xr/index.rst:5
msgid "Basic Tutorial"
msgstr ""

#: ../../docs/tutorials/xr/index.rst:30
msgid ""
"Documentation for XR in Godot 4.0 XR is still a work in progress. Please "
"check back in the future."
msgstr ""

#: ../../docs/tutorials/xr/setting_up_xr.rst:4
#, fuzzy
msgid "Setting up XR"
msgstr "Uvod / Početak"

#: ../../docs/tutorials/xr/setting_up_xr.rst:7
#, fuzzy
msgid "Introduction to the XR system in Godot"
msgstr "Uvod"

#: ../../docs/tutorials/xr/setting_up_xr.rst:9
msgid ""
"Godot provides a modular XR system that abstracts many of the different XR "
"platform specifics away from the user. At the core sits the :ref:`XRServer "
"<class_xrserver>` which acts as a central interface to the XR system that "
"allows users to discover interfaces and interact with the components of the "
"XR system."
msgstr ""

#: ../../docs/tutorials/xr/setting_up_xr.rst:12
msgid ""
"Each supported XR platform is implemented as an :ref:`XRInterface "
"<class_xrinterface>`. Supported interfaces register themselves with the :ref:"
"`XRServer <class_xrserver>` and can be queried with the ``find_interface`` "
"method on the :ref:`XRServer <class_xrserver>`. When the desired interface "
"is found it can be initialized by calling ``initialize`` on the interface."
msgstr ""

#: ../../docs/tutorials/xr/setting_up_xr.rst:15
msgid ""
"A registered interface means nothing more than that the interface is "
"available, if the interface is not supported by the host system, "
"initialization may fail and return ``false``. This can have many reasons and "
"sadly the reasons differ from platform to platform. It can be because the "
"user hasn't installed the required software, or that the user simply hasn't "
"plugged in their headset. You as a developer must thus react properly on an "
"interface failing to initialize."
msgstr ""

#: ../../docs/tutorials/xr/setting_up_xr.rst:17
msgid ""
"Due to the special requirements for output in XR, especially for head "
"mounted devices that supply different images to each eye, the :ref:`XRServer "
"<class_xrserver>` in Godot will override various features in the rendering "
"system. For stand-alone devices this means the final output is handled by "
"the :ref:`XRInterface <class_xrinterface>` and Godot's usual output system "
"is disabled. For desktop XR devices that work as a second screen it is "
"possible to dedicate a separate :ref:`Viewport <class_viewport>` to handle "
"the XR output, leaving the main Godot window available for displaying "
"alternative content."
msgstr ""

#: ../../docs/tutorials/xr/setting_up_xr.rst:20
msgid ""
"Note that only one interface can be responsible for handling the output to "
"an XR device, this is known as the primary interface and by default will be "
"the first interface that is initialized. Godot currently thus only supports "
"implementations with a single headset. It is possible, but increasingly "
"uncommon, to have a secondary interface, for example to add tracking to an "
"otherwise 3DOF only device."
msgstr ""

#: ../../docs/tutorials/xr/setting_up_xr.rst:23
msgid ""
"There are three XR specific node types that you will find in nearly all XR "
"applications:"
msgstr ""

#: ../../docs/tutorials/xr/setting_up_xr.rst:25
msgid ""
":ref:`XROrigin3D <class_xrorigin3d>` represents, for all intents and "
"purposes, the center point of your play space. That is an oversimplified "
"statement but we'll go into more detail later. All objects tracked in "
"physical space by the XR platform are positioned in relation to this point."
msgstr ""

#: ../../docs/tutorials/xr/setting_up_xr.rst:26
msgid ""
":ref:`XRCamera3D <class_xrcamera3d>` represents the (stereo) camera that is "
"used when rendering output for the XR device. The positioning of this node "
"is controlled by the XR system and updated automatically using the tracking "
"information provided by the XR platform."
msgstr ""

#: ../../docs/tutorials/xr/setting_up_xr.rst:27
msgid ""
":ref:`XRController3D <class_xrcontroller3d>` represents a controller used by "
"the player, commonly there are two, one held in each hand. These nodes give "
"access to various states on these controllers and send out signals when the "
"player presses buttons on them. The positioning of this node is controlled "
"by the XR system and updated automatically using the tracking information "
"provided by the XR platform."
msgstr ""

#: ../../docs/tutorials/xr/setting_up_xr.rst:29
msgid ""
"There are other XR related nodes and there is much more to say about these "
"three nodes, but we'll get into that later on."
msgstr ""

#: ../../docs/tutorials/xr/setting_up_xr.rst:32
msgid "Prerequisites for XR in Godot 4"
msgstr ""

#: ../../docs/tutorials/xr/setting_up_xr.rst:34
msgid ""
"While in Godot 3 most things worked out of the box, Godot 4 needs a little "
"more setup. This is mainly due to the more advanced nature of the Vulkan "
"renderer. There are many rendering features in Vulkan the XR system uses "
"that aren't enabled by default. They are very easy to turn on, simply open "
"up your project settings and tick the XR shaders tickbox in the XR section:"
msgstr ""

#: ../../docs/tutorials/xr/setting_up_xr.rst:39
msgid ""
"As Godot 4 is still in development, many post process effects have not yet "
"been updated to support stereoscopic rendering. Using these will have "
"adverse effects."
msgstr ""

#: ../../docs/tutorials/xr/setting_up_xr.rst:42
msgid ""
"Godot 4 has 3 renderer options, Compatibility, Mobile, and Forward+. In the "
"future XR desktop projects should use Forward+, and projects for stand-alone "
"headsets should use Mobile. However Compatibility is the recommended "
"renderer for now due to it having the best XR performance."
msgstr ""

#: ../../docs/tutorials/xr/setting_up_xr.rst:46
#, fuzzy
msgid "OpenXR"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/xr/setting_up_xr.rst:48
msgid ""
"OpenXR is a new industry standard that allows different XR platforms to "
"present themselves through a standardised API to XR applications. This "
"standard is an open standard maintained by the Khronos Group and thus aligns "
"very well with Godot's interests."
msgstr ""

#: ../../docs/tutorials/xr/setting_up_xr.rst:50
msgid ""
"The Vulkan implementation of OpenXR is closely integrated with Vulkan, "
"taking over part of the Vulkan system. This requires tight integration of "
"certain core graphics features in the Vulkan renderer which are needed "
"before the XR system is setup. This was one of the main deciding factors to "
"include OpenXR as a core interface."
msgstr ""

#: ../../docs/tutorials/xr/setting_up_xr.rst:52
msgid ""
"This also means OpenXR needs to be enabled when Godot starts in order to set "
"things up correctly. The required setting can be found in your project "
"settings:"
msgstr ""

#: ../../docs/tutorials/xr/setting_up_xr.rst:56
msgid ""
"As setup is brought forward with OpenXR you can find several other settings "
"related to OpenXR here as well. These can't be changed while your "
"application is running. The default settings will get us started and we will "
"go into detail in another section of the documentation."
msgstr ""

#: ../../docs/tutorials/xr/setting_up_xr.rst:60
#, fuzzy
msgid "Setting up the XR scene"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/xr/setting_up_xr.rst:62
msgid ""
"Every XR application needs at least an :ref:`XROrigin3D <class_xrorigin3d>` "
"and an :ref:`XRCamera3D <class_xrcamera3d>` node. Most will have two :ref:"
"`XRController3D <class_xrcontroller3d>`, one for the left hand and one for "
"the right. Keep in mind that the camera and controller nodes should be "
"children of the origin node. Add these nodes to a new scene and rename the "
"controller nodes to ``LeftHand`` and ``RightHand``, your scene should look "
"something like this:"
msgstr ""

#: ../../docs/tutorials/xr/setting_up_xr.rst:66
msgid ""
"Next you need to configure the controllers, select the left hand and set it "
"up as follows:"
msgstr ""

#: ../../docs/tutorials/xr/setting_up_xr.rst:70
msgid "And the right hand:"
msgstr ""

#: ../../docs/tutorials/xr/setting_up_xr.rst:74
msgid ""
"Right now all these nodes are on the floor, they will be positioned "
"correctly in runtime. To help during development, it can be helpful to move "
"the camera upwards so its ``y`` is set to ``1.7``, and move the controller "
"nodes to ``-0.5, 1.0, -0.5`` and ``0.5, 1.0, -0.5`` for respectively the "
"left and right hand."
msgstr ""

#: ../../docs/tutorials/xr/setting_up_xr.rst:76
msgid ""
"Next we need to add a script to our root node. Add the following code into "
"this script:"
msgstr ""

#: ../../docs/tutorials/xr/setting_up_xr.rst:126
msgid ""
"This code fragment assumes we are using OpenXR, if you wish to use any of "
"the other interfaces you can change the ``find_interface`` call."
msgstr ""

#: ../../docs/tutorials/xr/setting_up_xr.rst:130
msgid ""
"As you can see in the code snippet above, we turn off v-sync. When using "
"OpenXR you are outputting the rendering results to an HMD that often "
"requires us to run at 90Hz or higher. If your monitor is a 60hz monitor and "
"v-sync is turned on, you will limit the output to 60 frames per second."
msgstr ""

#: ../../docs/tutorials/xr/setting_up_xr.rst:134
msgid "XR interfaces like OpenXR perform their own sync."
msgstr ""

#: ../../docs/tutorials/xr/setting_up_xr.rst:136
msgid ""
"Also note that by default the physics engine runs at 60Hz as well and this "
"can result in choppy physics. You should set ``Engine."
"physics_ticks_per_second`` to a higher value."
msgstr ""

#: ../../docs/tutorials/xr/setting_up_xr.rst:139
msgid ""
"If you run your project at this point in time, everything will work but you "
"will be in a dark world. So to finish off our starting point add a :ref:"
"`DirectionalLight3D <class_directionallight3d>` and a :ref:`WorldEnvironment "
"<class_worldenvironment>` node to your scene. You may wish to also add a "
"mesh instance as a child to each controller node just to temporarily "
"visualise them. Make sure you configure a sky in your world environment."
msgstr ""

#: ../../docs/tutorials/xr/setting_up_xr.rst:143
msgid ""
"Now run your project, you should be floating somewhere in space and be able "
"to look around."
msgstr ""

#: ../../docs/tutorials/xr/setting_up_xr.rst:147
msgid ""
"While traditional level switching can definitely be used with XR "
"applications, where this scene setup is repeated in each level, most find it "
"easier to set this up once and loading levels as a subscene. If you do "
"switch scenes and replicate the XR setup in each one, do make sure you do "
"not run ``initialize`` multiple times. The effect can be unpredictable "
"depending on the XR interface used."
msgstr ""

#: ../../docs/tutorials/xr/setting_up_xr.rst:149
msgid ""
"For the rest of this basic tutorial series we will create a game that uses a "
"single scene."
msgstr ""

#: ../../docs/tutorials/xr/deploying_to_android.rst:4
#, fuzzy
msgid "Deploying to Android"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/xr/deploying_to_android.rst:8
msgid ""
"Most standalone headsets run on Android and OpenXR support is making its way "
"to these platforms."
msgstr ""

#: ../../docs/tutorials/xr/deploying_to_android.rst:10
msgid ""
"Before following the OpenXR-specific instructions here, you'll need to first "
"setup your system to export to Android in general, including:"
msgstr ""

#: ../../docs/tutorials/xr/deploying_to_android.rst:12
#, fuzzy
msgid "Installing OpenJDK 17"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/xr/deploying_to_android.rst:13
#, fuzzy
msgid "Installing Android Studio"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/xr/deploying_to_android.rst:14
#, fuzzy
msgid "Creating a debug.keystore"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/xr/deploying_to_android.rst:15
msgid "Configuring the location of the Android SDK and debug.keystore in Godot"
msgstr ""

#: ../../docs/tutorials/xr/deploying_to_android.rst:17
msgid ""
"See :ref:`doc_exporting_for_android` for the full details, and return here "
"when you've finished these steps."
msgstr ""

#: ../../docs/tutorials/xr/deploying_to_android.rst:20
#, fuzzy
msgid "Gradle Android build"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/xr/deploying_to_android.rst:23
msgid ""
"Official support for the Android platform wasn't added to the OpenXR "
"specification initially resulting in various vendors creating custom loaders "
"to make OpenXR available on their headsets. While the long term expectation "
"is that all vendors will adopt the official OpenXR loader, for now these "
"loaders need to be added to your project."
msgstr ""

#: ../../docs/tutorials/xr/deploying_to_android.rst:26
msgid ""
"In order to include the vendor-specific OpenXR loader into your project, you "
"will need to setup a gradle Android build."
msgstr ""

#: ../../docs/tutorials/xr/deploying_to_android.rst:28
msgid "Select **Install Android Build Template...** from the **Project** menu:"
msgstr ""

#: ../../docs/tutorials/xr/deploying_to_android.rst:32
msgid ""
"This will create a folder called **android** inside of your project that "
"contains all the runtime files needed on Android. You can now customize this "
"installation. Godot won't show this in the editor but you can find it with a "
"file browser."
msgstr ""

#: ../../docs/tutorials/xr/deploying_to_android.rst:34
msgid ""
"You can read more about gradle builds here: :ref:`doc_android_gradle_build`."
msgstr ""

#: ../../docs/tutorials/xr/deploying_to_android.rst:37
#, fuzzy
msgid "Installing the vendors plugin"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/xr/deploying_to_android.rst:40
msgid ""
"The Android plugin structure has been restructured in Godot 4.2, and the "
"loader plugin was renamed to vendors plugin as it now includes more than "
"just loaders. If you've previously installed the loader plugin you need to "
"delete it from the `android/plugins` folder."
msgstr ""

#: ../../docs/tutorials/xr/deploying_to_android.rst:43
msgid ""
"The vendors plugin can be downloaded from the asset library, search for "
"\"OpenXR vendors\" and install the plugin:"
msgstr ""

#: ../../docs/tutorials/xr/deploying_to_android.rst:47
msgid "You will find the installed files inside the **addons** folder."
msgstr ""

#: ../../docs/tutorials/xr/deploying_to_android.rst:49
#, fuzzy
msgid ""
"Alternatively you can manually install the vendors plugin by downloading the "
"v2.x version of the plugin `from the release page here <https://github.com/"
"GodotVR/godot_openxr_vendors/releases>`__."
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati raznorazne `Godot demo projects "
"<https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/tutorials/xr/deploying_to_android.rst:51
msgid ""
"You will need to copy the `assets/addons/godotopenxrvendors` folder from the "
"zip file into your projects `addons` folder."
msgstr ""

#: ../../docs/tutorials/xr/deploying_to_android.rst:53
#, fuzzy
msgid ""
"You can find the main repository of the vendors plugin `here <https://github."
"com/GodotVR/godot_openxr_vendors>`__."
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati raznorazne `Godot demo projects "
"<https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/tutorials/xr/deploying_to_android.rst:56
#, fuzzy
msgid "Enabling the vendors plugin"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/xr/deploying_to_android.rst:58
msgid ""
"The vendors plugin needs to be enabled before the export settings become "
"accessible. Open **Project** and select **Project Settings...**. Go to the "
"**Plugins** tab. Enable the **GodotOpenXRVendors** plugin."
msgstr ""

#: ../../docs/tutorials/xr/deploying_to_android.rst:66
#, fuzzy
msgid "Creating the export presets"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/xr/deploying_to_android.rst:67
msgid ""
"You will need to setup a separate export preset for each device, as each "
"device will need its own loader included."
msgstr ""

#: ../../docs/tutorials/xr/deploying_to_android.rst:69
msgid ""
"Open **Project** and select **Export..**. Click on **Add..** and select "
"**Android**. Next change the name of the export preset for the device you're "
"setting this up for, say **Meta Quest**. And enable **Use Gradle Build**. If "
"you want to use one-click deploy (described below), ensure that **Runnable** "
"is enabled."
msgstr ""

#: ../../docs/tutorials/xr/deploying_to_android.rst:75
msgid ""
"If the loader plugins were installed correctly you should find entries for "
"the different headsets, select the entry for meta:"
msgstr ""

#: ../../docs/tutorials/xr/deploying_to_android.rst:79
msgid "Also change the **XR Mode** to **OpenXR**."
msgstr ""

#: ../../docs/tutorials/xr/deploying_to_android.rst:81
msgid ""
"Scroll to the bottom of the list and you'll find additional XR feature "
"sections, currently only **Meta XR Features** is available. The hand "
"tracking and passthrough settings here currently only work for the Meta "
"Quest and you will need to select the appropriate settings if you wish to "
"use these features."
msgstr ""

#: ../../docs/tutorials/xr/deploying_to_android.rst:86
msgid "Now you can repeat the same process for the other devices."
msgstr ""

#: ../../docs/tutorials/xr/deploying_to_android.rst:89
msgid ""
"There are separate loaders for the Meta Quest, Pico and Lynx R1 headsets."
msgstr ""

#: ../../docs/tutorials/xr/deploying_to_android.rst:91
msgid ""
"The fourth option is the official Khronos loader, in due time all headsets "
"should work with this loader. At the moment this loader has been tested with "
"the Magic Leap 2 and standalone HTC headsets."
msgstr ""

#: ../../docs/tutorials/xr/deploying_to_android.rst:95
msgid ""
"While the Mobile Vulkan renderer has many optimizations targeted at mobile "
"devices, we're still working out the kinks. It is highly advisable to use "
"the compatibility renderer (OpenGL) for the time being when targeting "
"Android based XR devices."
msgstr ""

#: ../../docs/tutorials/xr/deploying_to_android.rst:99
msgid "Running on your device from the Godot editor"
msgstr ""

#: ../../docs/tutorials/xr/deploying_to_android.rst:100
msgid ""
"If you've setup your export settings as described above, and your headset is "
"connected to your computer and correctly recognized, you can launch it "
"directly from the Godot editor using :ref:`doc_one-click_deploy`:"
msgstr ""

#: ../../docs/tutorials/xr/deploying_to_android.rst:104
msgid ""
"For some devices on some platforms, you may need to perform some extra steps "
"in order for your device to be recognized correctly, so be sure to check the "
"developer documentation from your headset vendor."
msgstr ""

#: ../../docs/tutorials/xr/deploying_to_android.rst:106
msgid ""
"For example, with the Meta Quest 2, you need to enable developer mode on the "
"headset, and if you're on Windows, you'll need to install special ADB "
"drivers. See the `official Meta Quest developer documentation <https://"
"developer.oculus.com/documentation/native/android/mobile-device-setup/>`_ "
"for more details."
msgstr ""

#: ../../docs/tutorials/xr/deploying_to_android.rst:108
msgid ""
"If you're having any issues with one-click deploy, check the :ref:"
"`Troubleshooting section <doc_one-click_deploy_troubleshooting>`."
msgstr ""

#: ../../docs/tutorials/xr/introducing_xr_tools.rst:4
#, fuzzy
msgid "Introducing XR tools"
msgstr "Uvod"

#: ../../docs/tutorials/xr/introducing_xr_tools.rst:6
msgid ""
"Out of the box Godot gives you all the basic support to setup an XR project. "
"XR specific game mechanics however need to be implemented on top of this "
"foundation. While Godot makes this relatively easy this can still be a "
"daunting task."
msgstr ""

#: ../../docs/tutorials/xr/introducing_xr_tools.rst:10
msgid ""
"For this reason Godot has developed a toolkit called `Godot XR Tools "
"<https://github.com/GodotVR/godot-xr-tools>`_ that implements many of the "
"basic mechanics found in XR games, from locomotion to object interaction to "
"UI interaction."
msgstr ""

#: ../../docs/tutorials/xr/introducing_xr_tools.rst:13
msgid ""
"This toolkit is designed to work with both OpenXR and WebXR runtimes. We'll "
"be using this as a base for our documentation here. It helps developers hit "
"the ground running but for more specific use cases building your own logic "
"is just as valid. In that case XR tools can help in providing inspiration."
msgstr ""

#: ../../docs/tutorials/xr/introducing_xr_tools.rst:19
msgid ""
"The current stable release of Godot XR Tools available on the Asset Library "
"is the version for Godot 3. The port of Godot XR Tools for Godot 4 is "
"available for download from the github website. We will walk through the "
"step of downloading and installing it here. We will update the documentation "
"once Godot XR Tools becomes available for Godot 4 through the asset library."
msgstr ""

#: ../../docs/tutorials/xr/introducing_xr_tools.rst:25
#, fuzzy
msgid "Installing XR Tools"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/xr/introducing_xr_tools.rst:27
msgid ""
"Continuing on from our project we started in :ref:`doc_setting_up_xr` we "
"want to add in the Godot XR Tools library. This can be downloaded from the "
"`Godot XR Tools releases page <https://github.com/GodotVR/godot-xr-tools/"
"releases>`_. Simply find the latest pre-release for Godot 4 and then under "
"assets download the ``godot-xr-tools.zip`` file."
msgstr ""

#: ../../docs/tutorials/xr/introducing_xr_tools.rst:31
msgid ""
"Once downloaded unzip the file. You will notice the files are held within a "
"``godot-xr-tools`` subfolder. Inside of this folder you will find an "
"``addons`` folder. It is this folder that you want to copy in its entirety "
"to your Godot project folder, your project should now look something like "
"this:"
msgstr ""

#: ../../docs/tutorials/xr/introducing_xr_tools.rst:38
msgid ""
"Now open up your project in Godot, if you haven't already, and give it a "
"minute or so to import all the resources of the plugin."
msgstr ""

#: ../../docs/tutorials/xr/introducing_xr_tools.rst:40
msgid ""
"Next open the ``Project`` menu and select ``Project Settings..``. Now go to "
"the ``Plugins`` tab and enable the plugin."
msgstr ""

#: ../../docs/tutorials/xr/introducing_xr_tools.rst:46
msgid "Basic hands"
msgstr ""

#: ../../docs/tutorials/xr/introducing_xr_tools.rst:48
msgid ""
"Just to get a feel of things we're going to add a few standard components "
"that dress up our scene starting with hands for our player."
msgstr ""

#: ../../docs/tutorials/xr/introducing_xr_tools.rst:50
msgid ""
"OpenXR supports full hand tracking however there currently are significant "
"differences in capabilities between the different XR Runtimes."
msgstr ""

#: ../../docs/tutorials/xr/introducing_xr_tools.rst:52
msgid ""
"As a reliable alternative Godot XR Tools comes with a number of rigged hand "
"scenes that react on trigger and grip inputs of your controller. These hands "
"come in low and high poly versions, come in a few configurations, a number "
"of animation files to control finger positions and a number of different "
"textures."
msgstr ""

#: ../../docs/tutorials/xr/introducing_xr_tools.rst:55
msgid ""
"In your scene tree select your left hand :ref:`XRController3D "
"<class_xrcontroller3d>` node. Now click on the ``instantiate Child Scene`` "
"button to add a child scene. And select ``addons/godot-xr-tools/hands/scenes/"
"lowpoly/left_hand_low.tscn``."
msgstr ""

#: ../../docs/tutorials/xr/introducing_xr_tools.rst:59
msgid ""
"As you can see from the path of this scene, low poly models are in the "
"``lowpoly`` subfolder while high poly models are in the ``highpoly`` "
"subfolder. You will want to use the low poly versions if you plan to release "
"your game on mobile devices."
msgstr ""

#: ../../docs/tutorials/xr/introducing_xr_tools.rst:62
msgid "The default hand we chose is just a hand. The other options are:"
msgstr ""

#: ../../docs/tutorials/xr/introducing_xr_tools.rst:64
msgid "tac_glove - the hand is wearing a glove with fingers exposed"
msgstr ""

#: ../../docs/tutorials/xr/introducing_xr_tools.rst:65
msgid "full_glove - the hand is wearing a glove that covers the entire hand"
msgstr ""

#: ../../docs/tutorials/xr/introducing_xr_tools.rst:67
msgid ""
"Finally each hand comes in a ``physics`` version. This exposes all the "
"bones. We'll look at how that can be used in another tutorial."
msgstr ""

#: ../../docs/tutorials/xr/introducing_xr_tools.rst:71
msgid "We repeat the same for the right hand."
msgstr ""

#: ../../docs/tutorials/xr/introducing_xr_tools.rst:78
msgid ""
"We'll continue with adding features to our tutorial project using Godot XR "
"tools in the next couple of pages. More detailed information about the "
"toolkit can be found `on the toolkits help pages <https://godotvr.github.io/"
"godot-xr-tools/>`_."
msgstr ""

#: ../../docs/tutorials/xr/basic_xr_locomotion.rst:4
msgid "Basic XR Locomotion"
msgstr ""

#: ../../docs/tutorials/xr/basic_xr_locomotion.rst:6
msgid ""
"For basic locomotion we're going to continue using our Godot XR Tools "
"library. The library contains both basic movement features as more advanced "
"features."
msgstr ""

#: ../../docs/tutorials/xr/basic_xr_locomotion.rst:9
#, fuzzy
msgid "Adding our player body"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/xr/basic_xr_locomotion.rst:11
msgid ""
"The first step we need to do is to add a helper node to our :ref:`XROrigin3D "
"<class_xrorigin3d>` node. Because XR supports roomscale tracking you can't "
"simply add your XR setup to a :ref:`CharacterBody3D <class_characterbody3d>` "
"node and expect things to work. You will run into trouble when the user "
"moves around their physical space and is no longer standing in the center of "
"their room. Godot XR Tools embeds the needed logic into a helper node called "
"``PlayerBody``."
msgstr ""

#: ../../docs/tutorials/xr/basic_xr_locomotion.rst:16
msgid ""
"Select your :ref:`XROrigin3D <class_xrorigin3d>` node and click on the "
"``instantiate Child Scene`` button to add a child scene. Select ``addons/"
"godot-xr-tools/player/player_body.tscn`` and add this node."
msgstr ""

#: ../../docs/tutorials/xr/basic_xr_locomotion.rst:20
#, fuzzy
msgid "Adding a floor"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/xr/basic_xr_locomotion.rst:22
msgid ""
"This node governs the in game movement of your character and will "
"immediately react to gravity. So to prevent our player from infinitely "
"falling down we'll quickly add a floor to our scene."
msgstr ""

#: ../../docs/tutorials/xr/basic_xr_locomotion.rst:25
msgid ""
"We start by adding a :ref:`StaticBody3D <class_staticbody3d>` node to our "
"root node and we rename this to ``Floor``. We add a :ref:`MeshInstance3D "
"<class_meshinstance3d>` node as a child node for our ``Floor``. Then create "
"a new :ref:`PlaneMesh <class_planemesh>` as it's mesh. For now we set the "
"size of the mesh to 100 x 100 meters. Next we add a :ref:`CollisionShape3D "
"<class_collisionshape3d>` node as a child node for our ``Floor``. Then "
"create a ``BoxShape`` as our shape. We set the size of this box shape to 100 "
"x 1 x 100 meters. We also need to move our collision shape down by 0.5 "
"meters so the top of our box is flush with the floor."
msgstr ""

#: ../../docs/tutorials/xr/basic_xr_locomotion.rst:34
msgid ""
"To make it easier to see that we're actually moving around our world, a "
"white floor isn't going to do it. For this we add a material to our "
"PlaneMesh and set the albedo to a grid texture we've created with `Wahooneys "
"excellent free texture generator <https://wahooney.itch.io/texture-grid-"
"generator>`_."
msgstr ""

#: ../../docs/tutorials/xr/basic_xr_locomotion.rst:40
#, fuzzy
msgid "Direct movement"
msgstr "Uvod"

#: ../../docs/tutorials/xr/basic_xr_locomotion.rst:42
msgid ""
"We're going to start adding some basic direct movement to our setup. This "
"allows the user to move through the virtual world using joystick input."
msgstr ""

#: ../../docs/tutorials/xr/basic_xr_locomotion.rst:46
msgid ""
"It is important to note that moving through the virtual world while the "
"player is standing still in the real world, can be nausea inducing "
"especially for players who are new to VR. The default settings on our "
"movement functions are fairly conservative. We advise you to stick to these "
"defaults but offer features in game to enable less comfortable settings for "
"more experienced users who are used to playing VR games."
msgstr ""

#: ../../docs/tutorials/xr/basic_xr_locomotion.rst:50
msgid ""
"We want to enable this on the right hand controller. We do this by adding a "
"subscene to the right hand :ref:`XRController3D <class_xrcontroller3d>` "
"node. Select ``addons/godot-xr-tools/functions/movement_direct.tscn`` as the "
"scene to add."
msgstr ""

#: ../../docs/tutorials/xr/basic_xr_locomotion.rst:54
msgid ""
"This function adds forward and backwards movement to the player by using the "
"joystick on the right hand controller. It has an option to also add left/"
"right strafe but by default this is disabled."
msgstr ""

#: ../../docs/tutorials/xr/basic_xr_locomotion.rst:57
msgid ""
"Instead, we are going to add the ability for the player to also turn with "
"this joystick. We will add another subscene to our controller node, select "
"``addons/godot-xr-tools/functions/movement_turn.tscn`` for this."
msgstr ""

#: ../../docs/tutorials/xr/basic_xr_locomotion.rst:60
msgid ""
"The turn system by default uses a snap turn approach. This means that "
"turning happens in steps. This may seem jarring however it is a tried and "
"tested method of combating motion sickness. You can easily switch to a mode "
"that offers smooth turning by changing the ``mode`` property on the turn "
"node."
msgstr ""

#: ../../docs/tutorials/xr/basic_xr_locomotion.rst:65
msgid ""
"If you run your game at this point in time you will find that you can move "
"through the world freely using the right hand joystick."
msgstr ""

#: ../../docs/tutorials/xr/basic_xr_locomotion.rst:68
msgid "Teleport"
msgstr ""

#: ../../docs/tutorials/xr/basic_xr_locomotion.rst:70
msgid ""
"An alternative to direct movement that some users find more pleasant is the "
"ability to teleport to another location within your game world. Godot XR "
"Tools supports this through the teleport function and we will be adding this "
"to our left hand controller."
msgstr ""

#: ../../docs/tutorials/xr/basic_xr_locomotion.rst:73
msgid ""
"Add a new child scene to your left hand :ref:`XRController3D "
"<class_xrcontroller3d>` node by selecting the ``addons/godot-xr-tools/"
"functions/function_teleport.tscn`` scene."
msgstr ""

#: ../../docs/tutorials/xr/basic_xr_locomotion.rst:75
msgid ""
"With this scene added the player will be able to teleport around the world "
"by pressing the trigger on the left hand controller, pointing where they "
"want to go, and then releasing the trigger. The player can also adjust the "
"orientation by using the left hand controllers joystick."
msgstr ""

#: ../../docs/tutorials/xr/basic_xr_locomotion.rst:78
msgid ""
"If you've followed all instructions correctly your scene should now look "
"something like this:"
msgstr ""

#: ../../docs/tutorials/xr/basic_xr_locomotion.rst:83
msgid "More advanced movement features"
msgstr ""

#: ../../docs/tutorials/xr/basic_xr_locomotion.rst:85
msgid ""
"Godot XR Tools adds many more movement features such as gliding, a grapple "
"hook implementation, a jetpack, climbing mechanics, etc."
msgstr ""

#: ../../docs/tutorials/xr/basic_xr_locomotion.rst:87
msgid ""
"Most work similarly to the basic movement features we've handled so far, "
"simply add the relevant subscene from the plugin to the controller that "
"implements it."
msgstr ""

#: ../../docs/tutorials/xr/basic_xr_locomotion.rst:89
msgid ""
"We'll look at some of these in more detail later on in this tutorial where "
"additional setup is required (such as climbing) but for others please look "
"at Godot XR Tools own help pages for details."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:4
msgid "The XR action map"
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:6
msgid ""
"Godot has an action map feature as part of the XR system. At this point in "
"time this system is part of the OpenXR module. There are plans to encompass "
"WebXR into this in the near future hence we call it the XR action map system "
"in this document. It implements the built-in action map system of OpenXR "
"mostly exactly as it is offered."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:11
msgid ""
"The XR action map system exposes input, positional data and output for XR "
"controllers to your game/application. It does this by exposing named actions "
"that can be tailored to your game/application and binding these to the "
"actual inputs and outputs on your XR devices."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:14
msgid ""
"As the XR action map is currently part of the OpenXR module, OpenXR needs to "
"be enabled in your project settings to expose it:"
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:18
msgid ""
"You will then find the XR Action Map interface in the bottom of the screen:"
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:23
msgid ""
"Godot's built-in input system has many things in common with the XR action "
"map system. In fact our original idea was to add functionality to the "
"existing input system and expose the data to the OpenXR action map system. "
"We may revisit that idea at some point but as it turns out there were just "
"too many problems to overcome. To name a few:"
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:28
msgid ""
"Godot's input system mainly centers around button inputs, XR adds triggers, "
"axis, poses and haptics (output) into the mix. This would greatly complicate "
"the input system with features that won't work for normal controllers or "
"contrast with the current approach. It was felt this would lead to confusion "
"for the majority of Godot users."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:31
msgid ""
"Godot's input system works with raw input data that is parsed and triggers "
"emitting actions. This input data is made available to the end user. OpenXR "
"completely hides raw data and does all the parsing for us, we only get "
"access to already parsed action data. This inconsistency is likely to lead "
"to bugs when an unsuspecting user tries to use an XR device as a normal "
"input device."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:35
msgid ""
"Godot's input system allows changes to what inputs are bound to actions in "
"runtime, OpenXR does not."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:36
msgid ""
"Godot's input system is based on device ids which are meaningless in OpenXR."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:38
msgid ""
"This does mean that a game/application that mixes traditional inputs with XR "
"controllers will have a separation. For most applications either one or the "
"other is used and this is not seen as a problem. In the end, it's a "
"limitation of the system."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:43
msgid "The default action map"
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:45
msgid ""
"Godot will automatically create a default action map if no action map file "
"is found."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:48
msgid ""
"This default map was designed to help developers port their XR games/"
"applications from Godot 3 to Godot 4. As a result this map essentially binds "
"all known inputs on all controllers supported by default, to actions one on "
"one. This is not a good example of setting up an action map. It does allow a "
"new developer to have a starting point when they want to become familiar "
"with Godot XR. It prevents having to design a proper action map for their "
"game/application first."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:54
msgid ""
"For this walkthrough we're going to start with a blank action map. You can "
"simply delete the \"Godot action set\" entry at the top by pressing the "
"trash can icon. This will clear out all actions. You might also want to "
"remove the controllers that you do not wish to setup, more on this later."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:60
#, fuzzy
msgid "Action sets"
msgstr "Funkcije"

#: ../../docs/tutorials/xr/xr_action_map.rst:63
msgid ""
"Before we dive in, you will see the term XR runtime used throughout this "
"document. With XR runtime we mean the software that is controlling and "
"interacting with the AR or VR headset. The XR runtime then exposes this to "
"us through an API such as OpenXR. So:"
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:68
msgid "for Steam this is SteamVR,"
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:69
msgid ""
"for Meta on desktop this is the Oculus Client (including when using Quest "
"link),"
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:70
msgid "for Meta on Quest this is the Quest's native OpenXR client,"
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:71
msgid "on Linux this could be Monado, etc."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:73
msgid ""
"The action map allows us to organize our actions in sets. Each set can be "
"enabled or disabled on its own."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:76
msgid ""
"The concept here is that you could have different sets that provide bindings "
"in different scenarios. You could have:"
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:79
msgid "a ``Character control`` set for when you're walking around,"
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:80
msgid "a ``Vehicle control`` set for when you're operating a vehicle,"
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:81
msgid "a ``Menu`` set for when a menu is open."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:83
msgid ""
"Only the action set applicable to the current state of your game/application "
"can then be enabled."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:85
msgid ""
"This is especially important if you wish to bind the same input on a "
"controller to a different action. For instance:"
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:88
msgid "in your ``Character control`` set you may have an action ``Jump``,"
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:89
msgid "in your ``Vehicle control`` set you may have an action ``Accelerate``,"
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:90
msgid "in your ``Menu`` set you may have an action ``Select``."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:92
msgid "All are bound to the trigger on your controller."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:94
msgid ""
"OpenXR will only bind an input or output to a single action. If the same "
"input or output is bound to multiple actions the one in the active action "
"set with the highest priority will be the one updated/used. So in our above "
"example it will thus be important that only one action set is active."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:98
msgid ""
"For your first XR game/application we highly recommend starting with just a "
"single action set and to not over-engineer things."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:100
msgid ""
"For our walkthrough in this document we will thus create a single action set "
"called ``my_first_action_set``. We do this by pressing the ``Add action "
"set`` button:"
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:105
#: ../../docs/tutorials/xr/xr_action_map.rst:177
msgid "The columns in our table are as follows:"
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:113
#: ../../docs/tutorials/xr/xr_action_map.rst:185
msgid "Col"
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:117
msgid "my_first_action_set"
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:118
msgid ""
"This is the internal name of the action set. OpenXR doesn't specify specific "
"restrictions on this name other then size, however some XR runtimes will not "
"like spaces or special characters."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:121
msgid "My first action set"
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:122
msgid ""
"This is a human-readable name for the action set. Some XR runtimes will "
"display this name to the end user, for example in configuration dialogs."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:126
msgid ""
"This is the priority of the action set. If multiple active action sets have "
"actions bound to the same controllers inputs or outputs, the action set with "
"the highest priority value will determine the action that is updated."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:132
msgid ""
"In the XR action map, actions are the entities that your game/application "
"will interact with. For instance, we can define an action ``Shoot`` and the "
"input bound to that action will trigger the ``button_pressed`` signal on the "
"relevant :ref:`XRController3D <class_xrcontroller3d>` node in your scene "
"with ``Shoot`` as the ``name`` parameter of the signal."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:135
msgid ""
"You can also poll the current state of an action. :ref:`XRController3D "
"<class_xrcontroller3d>` for instance has an ``is_button_pressed`` method."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:138
msgid ""
"Actions can be used for both input and output and each action has a type "
"that defines its behavior."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:140
msgid "The ``Bool`` type is used for discrete input like buttons."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:141
msgid "The ``Float`` type is used for analogue input like triggers."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:143
msgid ""
"These two are special as they are the only ones that are interchangeable. "
"OpenXR will handle conversions between ``Bool`` and ``Float`` inputs and "
"actions. You can get the value of a ``Float`` type action by calling the "
"method ``get_float`` on your :ref:`XRController3D <class_xrcontroller3d>` "
"node. It emits the ``input_float_changed`` signal when changed."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:149
msgid ""
"Where analogue inputs are queried as buttons a threshold is applied. This "
"threshold is currently managed exclusively by the XR runtime. There are "
"plans to extend Godot to provide some level of control over these thresholds "
"in the future."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:153
msgid ""
"The ``Vector2`` type defines the input as an axis input. Touchpads, "
"thumbsticks and similar inputs are exposed as vectors. You can get the value "
"of a ``Vector2`` type action by calling the method ``get_vector2`` on your :"
"ref:`XRController3D <class_xrcontroller3d>` node. It emits the "
"``input_vector2_changed`` signal when changed."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:158
msgid ""
"The ``Pose`` type defines a spatially tracked input. Multiple \"pose\" "
"inputs are available in OpenXR: ``aim``, ``grip`` and ``palm``. Your :ref:"
"`XRController3D <class_xrcontroller3d>` node is automatically positioned "
"based on the pose action assigned to ``pose`` property of this node. More "
"about poses later."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:164
msgid ""
"The OpenXR implementation in Godot also exposes a special pose called "
"``Skeleton``. This is part of the hand tracking implementation. This pose is "
"exposed through the ``skeleton`` action that is supported outside of the "
"action map system. It is thus always present if hand tracking is supported. "
"You don't need to bind actions to this pose to use it."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:170
msgid ""
"Finally, the only output type is ``Haptic`` and it allows us to set the "
"intensity of haptic feedback, such as controller vibration. Controllers can "
"have multiple haptic outputs and support for haptic vests is coming to "
"OpenXR."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:173
msgid ""
"So lets add an action for our aim pose, we do this by clicking on the ``+`` "
"button for our action set:"
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:189
msgid "aim_pose"
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:190
msgid ""
"This is the internal name of the action. OpenXR doesn't specify specific "
"restrictions on this name other then size, however some XR runtimes will not "
"like spaces or special characters."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:193
msgid "Aim pose"
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:194
msgid ""
"This is a human-readable name for the action. Some XR runtimes will display "
"this name to the end user, for example in configuration dialogs."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:197
msgid "Pose"
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:198
#, fuzzy
msgid "The type of this action."
msgstr "Ne postoje ograničenja prilikom korištenja Godot-a"

#: ../../docs/tutorials/xr/xr_action_map.rst:200
msgid ""
"OpenXR defines a number of bindable input poses that are commonly available "
"for controllers. There are no rules for which poses are supported for "
"different controllers. The poses OpenXR currently defines are:"
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:204
msgid ""
"The aim pose on most controllers is positioned slightly in front of the "
"controller and aims forward. This is a great pose to use for laser pointers "
"or to align the muzzle of a weapon with."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:206
msgid ""
"The grip pose on most controllers is positioned where the grip button is "
"placed on the controller. The orientation of this pose differs between "
"controllers and can differ for the same controller on different XR runtimes."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:208
msgid ""
"The palm pose on most controllers is positioned in the center of the palm of "
"the hand holding the controller. This is a new pose that is not available on "
"all XR runtimes."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:212
msgid ""
"If hand tracking is used, there are currently big differences in "
"implementations between the different XR runtimes. As a result the action "
"map is currently not suitable for hand tracking. Work is being done on this "
"so stay tuned."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:215
msgid ""
"Let's complete our list of actions for a very simple shooting game/"
"application:"
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:219
msgid "The actions we have added are:"
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:221
msgid ""
"movement, which allows the user to move around outside of normal room scale "
"tracking."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:222
msgid "grab, which detects that the user wants to hold something."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:223
msgid ""
"shoot, which detects that the user wants to fire the weapon they are holding."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:224
msgid "haptic, which allows us to output haptic feedback."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:226
msgid ""
"Now note that we don't distinguish between the left and right hand. This is "
"something that is determined at the next stage. We've implemented the action "
"system in such a way that you can bind the same action to both hands. The "
"appropriate :ref:`XRController3D <class_xrcontroller3d>` node will emit the "
"signal."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:232
msgid ""
"For both grab and shoot we've used the ``Bool`` type. As mentioned before, "
"OpenXR does automatic conversions from an analogue controls however not all "
"XR Runtimes currently apply sensible thresholds."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:235
msgid ""
"We recommend as a workaround to use the ``Float`` type when interacting with "
"triggers and grip buttons and apply your own threshold."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:237
msgid ""
"For buttons like A/B/X/Y and similar where there is no analogue option, the "
"``Bool`` type works fine."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:240
msgid ""
"You can bind the same action to multiple inputs for the same controller on "
"the same profile. In this case the XR runtime will attempt to combine the "
"inputs."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:243
msgid ""
"For ``Bool`` inputs, this will perform an ``OR`` operation between the "
"buttons."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:244
msgid ""
"For ``Float`` inputs, this will take the highest value of the bound inputs."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:245
msgid ""
"The behavior for ``Pose`` inputs is undefined, but the first bound input is "
"likely to be used."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:247
msgid ""
"You shouldn't bind multiple actions of the same action set to the same "
"controller input. If you do this, or if actions are bound from multiple "
"action sets but they have overlapping priorities, the behavior is undefined. "
"The XR runtime may simply not accept your action map, or it may take this on "
"a first come first serve basis."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:251
msgid ""
"We are still investigating the restrictions around binding multiple actions "
"to the same output as this scenario makes sense. The OpenXR specification "
"seems to not allow this."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:254
msgid "Now that we have our basic actions defined, it's time to hook them up."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:257
msgid "Profiles"
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:259
msgid ""
"In OpenXR controller bindings are captured in so-called \"Interaction "
"Profiles\". We've simply shortened it to \"Profiles\" because it takes up "
"less space."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:262
msgid ""
"This generic name is chosen because controllers don't cover the entire "
"system. Currently there are also profiles for trackers, remotes and tracked "
"pens. There are also provisions for devices such as treadmills, haptic vests "
"and such even though those are not part of the specification yet."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:267
msgid ""
"It is important to know that OpenXR has strict checking on supported "
"devices. The core specification identifies a number of controllers and "
"similar devices with their supported inputs and outputs. Every XR runtime "
"must accept these interaction profiles even if they aren't applicable."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:271
msgid ""
"New devices are added through extensions and XR runtimes must specify which "
"ones they support. XR runtimes that do not support a device added through "
"extensions will not accept these profiles. XR runtimes that do not support "
"added input or output types will often crash if supplied."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:275
msgid ""
"As such Godot keeps meta data of all available devices, their inputs and "
"outputs and which extension adds support for them. You can create "
"interaction profiles for all devices you wish to support. Godot will filter "
"out those not supported by the XR runtime the user is using."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:279
msgid ""
"This does mean that in order to support new devices, you might need to "
"update to a more recent version of Godot."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:281
msgid ""
"It is however also important to note that the action map has been designed "
"with this in mind. When new devices enter the market, or when your users use "
"devices that you do not have access to, the action map system relies on the "
"XR runtime. It is the XR runtime's job to choose the best fitting "
"interaction profile that has been specified and adapt it for the controller "
"the user is using."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:285
msgid ""
"How the XR runtime does this is left to the implementation of the runtime "
"and there are thus vast differences between the runtimes. Some runtimes "
"might even permit users to edit the bindings themselves."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:288
msgid ""
"A common approach for a runtime is to look for a matching interaction "
"profile first. If this is not found it will check the most common profiles "
"such as that of the \"Touch controller\" and do a conversion. If all else "
"fails, it will check the generic :ref:`\"Simple controller\" "
"<doc_xr_action_map_simple>`."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:293
msgid ""
"There is an important conclusion to be made here: When a controller is "
"found, and the action map is applied to it, the XR runtime is not limited to "
"the exact configurations you set up in Godot's action map editor. While the "
"runtime will generally choose a suitable mapping based on one of the "
"bindings you set up in the action map, it can deviate from it."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:297
msgid ""
"For example, when the Touch controller profile is used any of the following "
"scenarios could be true:"
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:299
msgid "we could be using a Quest 1 controller,"
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:300
msgid "we could be using a Quest 2 controller,"
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:301
msgid ""
"we could be using a Quest Pro controller but no Quest Pro profile was given "
"or the XR runtime being used does not support the Quest Pro controller,"
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:302
msgid ""
"it could be a completely different controller for which no profile was given "
"but the XR runtime is using the touch bindings as a base."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:304
msgid ""
"Ergo, there currently is no way to know with certainty, which controller the "
"user is actually using."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:307
msgid ""
"Finally, and this trips up a lot of people, the bindings aren't set in "
"stone. It is fully allowed, and even expected, that an XR runtime allows a "
"user to customise the bindings."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:310
msgid ""
"At the moment none of the XR runtimes offer this functionality though "
"SteamVR has an existing UI from OpenVRs action map system that is still "
"accessible. This is actively being worked on however."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:314
msgid "Our first controller binding"
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:316
msgid ""
"Let's set up our first controller binding, using the Touch controller as an "
"example."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:318
msgid ""
"Press \"Add profile\", find the Touch controller, and add it. If it is not "
"in the list, then it may already have been added."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:323
msgid ""
"Our UI now shows panels for both the left and right controllers. The panels "
"contain all of the possible inputs and outputs for each controller. We can "
"use the ``+`` next to each entry to bind it to an action:"
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:329
msgid "Let's finish our configuration:"
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:333
msgid ""
"Each action is bound the given input or output for both controllers to "
"indicate that we support the action on either controller. The exception is "
"the movement action which is bound only to the right hand controller. It is "
"likely that we would want to use the left hand thumbstick for a different "
"purpose, say a teleport function."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:337
msgid ""
"In developing your game/application you have to account for the possibility "
"that the user changes the binding and binds the movement to the left hand "
"thumbstick."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:339
msgid ""
"Also note that our shoot and grab boolean actions are linked to inputs of "
"type ``Float``. As mentioned before OpenXR will do conversions between the "
"two, but do read the warning given on that subject earlier in this document."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:343
msgid "Some of the inputs seem to appear in our list multiple times."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:345
msgid ""
"For instance we can find the ``X`` button twice, once as ``X click`` and "
"then as ``X touch``. This is due to the Touch controller having a capacitive "
"sensor."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:348
msgid "``X touch`` will be true if the user is merely touching the X button."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:349
msgid ""
"``X click`` will be true when the user is actually pressing down on the "
"button."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:351
msgid "Similarly for the thumbstick we have:"
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:353
msgid ""
"``Thumbstick touch`` which will be true if the user is touching the "
"thumbstick."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:354
msgid ""
"``Thumbstick`` which gives a value for the direction the thumbstick is "
"pushed to."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:355
msgid ""
"``Thumbstick click`` which is true when the user is pressing down on the "
"thumbstick."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:357
msgid ""
"It is important to note that only a select number of XR controllers support "
"touch sensors or have click features on thumbsticks. Keep that in mind when "
"designing your game/application. Make sure these are used for optional "
"features of your game/application."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:364
#, fuzzy
msgid "The simple controller"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/xr/xr_action_map.rst:366
msgid ""
"The \"Simple controller\" is a generic controller that OpenXR offers as a "
"fallback. We'll apply our mapping:"
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:371
msgid ""
"As becomes painfully clear, the simple controller is often far too simple "
"and falls short for anything but the simplest of VR games/applications."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:373
msgid ""
"This is why many XR runtimes only use it as a last resort and will attempt "
"to use bindings from one of the more popular systems as a fallback first."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:376
msgid ""
"Due to the simple controller likely not covering the needs of your game, it "
"is tempting to provide bindings for every controller supported by OpenXR. "
"The default action map seems to suggest this as a valid course of action. As "
"mentioned before, the default action map was designed for ease of migration "
"from Godot 3."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:380
msgid ""
"It is the recommendation from the OpenXR Working Group that only bindings "
"for controllers actually tested by the developer are setup. The XR runtimes "
"are designed with this in mind. They can perform a better job of rebinding a "
"provided binding than a developer can make educated guesses. Especially as "
"the developer can't test if this leads to a comfortable experience for the "
"end user."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:385
msgid ""
"This is our advice as well: limit your action map to the interaction "
"profiles for devices you have actually tested your game with. The Oculus "
"Touch controller is widely used as a fallback controller by many runtimes. "
"If you are able to test your game using a Meta Rift or Quest and add this "
"profile there is a high probability your game will work with other headsets."
msgstr ""

#: ../../docs/tutorials/xr/xr_room_scale.rst:4
msgid "Room scale in XR"
msgstr ""

#: ../../docs/tutorials/xr/xr_room_scale.rst:6
msgid ""
"One of the staples of XR projects is the ability to walk around freely in a "
"large space. This space is often constrained by the room the player is "
"physically in with tracking sensors placed within this space. With the "
"advent of inside out tracking however ever larger play spaces are possible."
msgstr ""

#: ../../docs/tutorials/xr/xr_room_scale.rst:10
msgid ""
"As a developer this introduces a number of interesting challenges. In this "
"document we will look at a number of the challenges you may face and outline "
"some solutions. We'll discuss the issues and challenges for seated XR games "
"in another document."
msgstr ""

#: ../../docs/tutorials/xr/xr_room_scale.rst:15
msgid ""
"Often developers sit behind their desk while building the foundation to "
"their game. In this mode the issues with developing for room scale don't "
"show themselves until it is too late. The advice here is to start testing "
"while standing up and walking around as early as possible. Once you are "
"happy your foundation is solid, you can develop in comfort while remaining "
"seated."
msgstr ""

#: ../../docs/tutorials/xr/xr_room_scale.rst:20
msgid ""
"In traditional first person games a player is represented by a :ref:"
"`CharacterBody3D <class_characterbody3d>` node. This node is moved by "
"processing traditional controller, mouse or keyboard input. A camera is "
"attached to this node at a location roughly where the player's head will be."
msgstr ""

#: ../../docs/tutorials/xr/xr_room_scale.rst:24
msgid ""
"Applying this model to the XR setup, we add an :ref:`XROrigin3D "
"<class_xrorigin3d>` node as a child of the character body, and add a :ref:"
"`XRCamera3D <class_xrcamera3d>` as a child of the origin node. At face value "
"this seems to work. However, upon closer examination this model does not "
"take into account that there are two forms of movement in XR. The movement "
"through controller input, and the physical movement of the player in the "
"real world."
msgstr ""

#: ../../docs/tutorials/xr/xr_room_scale.rst:29
msgid ""
"As a result, the origin node does not represent the position of the player. "
"It represents the center, or start of, the tracking space in which the "
"player can physically move. As the player moves around their room this "
"movement is represented through the tracking of the players headset. In game "
"this translates to the camera node's position being updated accordingly. For "
"all intents and purposes, we are tracking a disembodied head. Unless body "
"tracking is available, we have no knowledge of the position or orientation "
"of the player's body."
msgstr ""

#: ../../docs/tutorials/xr/xr_room_scale.rst:38
msgid ""
"The first problem this causes is fairly obvious. When the player moves with "
"controller input, we can use the same approach in normal games and move the "
"player in a forward direction. However the player isn't where we think they "
"are and as we move forward we're checking collisions in the wrong location."
msgstr ""

#: ../../docs/tutorials/xr/xr_room_scale.rst:44
msgid ""
"The second problem really shows itself when the player walks further away "
"from the center of the tracking space and uses controller input to turn. If "
"we rotate our character body, the player will be moved around the room in a "
"circular fashion."
msgstr ""

#: ../../docs/tutorials/xr/xr_room_scale.rst:49
msgid ""
"If we fix the above issues, we will find a third issue. When the path for "
"the player is blocked in the virtual world, the player can still physically "
"move forward."
msgstr ""

#: ../../docs/tutorials/xr/xr_room_scale.rst:54
msgid ""
"We will look at solving the first two problem with two separate solutions, "
"and then discuss dealing with the third."
msgstr ""

#: ../../docs/tutorials/xr/xr_room_scale.rst:57
msgid "Origin centric solution"
msgstr ""

#: ../../docs/tutorials/xr/xr_room_scale.rst:59
msgid ""
"Looking at the first approach for solving this we are going to change our "
"structure. This is the approach currently implemented in XR Tools."
msgstr ""

#: ../../docs/tutorials/xr/xr_room_scale.rst:64
msgid ""
"In this setup we mark the character body as top level so it does not move "
"with the origin."
msgstr ""

#: ../../docs/tutorials/xr/xr_room_scale.rst:66
msgid ""
"We also have a helper node that tells us where our neck joint is in relation "
"to our camera. We use this to determine where our body center is."
msgstr ""

#: ../../docs/tutorials/xr/xr_room_scale.rst:69
msgid "Processing our character movement is now done in three steps."
msgstr ""

#: ../../docs/tutorials/xr/xr_room_scale.rst:72
#, fuzzy
msgid ""
"The `Origin centric movement demo <https://github.com/godotengine/godot-demo-"
"projects/tree/master/xr/openxr_origin_centric_movement>`__ contains a more "
"elaborate example of the technique described below."
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati različite Godo demo projekte "
"`Godot demo projects <https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/tutorials/xr/xr_room_scale.rst:75
#: ../../docs/tutorials/xr/xr_room_scale.rst:226
msgid "Step 1"
msgstr ""

#: ../../docs/tutorials/xr/xr_room_scale.rst:77
msgid ""
"In the first step we're going to process the physical movement of the "
"player. We determine where the player is right now, and attempt to move our "
"character body there."
msgstr ""

#: ../../docs/tutorials/xr/xr_room_scale.rst:113
msgid ""
"Note that we're returning ``true`` from our "
"``_process_on_physical_movement`` function when we couldn't move our player "
"all the way."
msgstr ""

#: ../../docs/tutorials/xr/xr_room_scale.rst:116
#: ../../docs/tutorials/xr/xr_room_scale.rst:302
msgid "Step 2"
msgstr ""

#: ../../docs/tutorials/xr/xr_room_scale.rst:118
msgid ""
"The second step is to handle rotation of the player as a result of user "
"input."
msgstr ""

#: ../../docs/tutorials/xr/xr_room_scale.rst:120
#: ../../docs/tutorials/xr/xr_room_scale.rst:307
msgid ""
"As the input used can differ based on your needs we are simply calling the "
"function ``_get_rotational_input``. This function should obtain the "
"necessary input and return the rotational speed in radians per second."
msgstr ""

#: ../../docs/tutorials/xr/xr_room_scale.rst:124
msgid ""
"For our example we are going to keep this simple and straight forward. We "
"are not going to worry about comfort features such as snap turning and "
"applying a vignette. We highly recommend implementing such comfort features."
msgstr ""

#: ../../docs/tutorials/xr/xr_room_scale.rst:163
msgid ""
"We've added the call for processing our rotation to our physics process but "
"we are only executing this if we were able to move our player fully. This "
"means that if the player moves somewhere they shouldn't, we don't process "
"further movement."
msgstr ""

#: ../../docs/tutorials/xr/xr_room_scale.rst:167
#: ../../docs/tutorials/xr/xr_room_scale.rst:326
msgid "Step 3"
msgstr ""

#: ../../docs/tutorials/xr/xr_room_scale.rst:169
msgid ""
"The third and final step is moving the player forwards, backwards or "
"sideways as a result of user input."
msgstr ""

#: ../../docs/tutorials/xr/xr_room_scale.rst:171
#: ../../docs/tutorials/xr/xr_room_scale.rst:331
msgid ""
"Just like with the rotation the inputs differ from project to project so we "
"are simply calling the function ``_get_movement_input``. This function "
"should obtain the necessary input and return a directional vector scaled to "
"the required velocity."
msgstr ""

#: ../../docs/tutorials/xr/xr_room_scale.rst:175
msgid ""
"Just like with rotation we're keeping it simple. Here too it is advisable to "
"look at adding comfort settings."
msgstr ""

#: ../../docs/tutorials/xr/xr_room_scale.rst:211
#, fuzzy
msgid "Character body centric solution"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/xr/xr_room_scale.rst:213
msgid ""
"In this setup we are going to keep our character body as our root node and "
"as such is easier to combine with traditional game mechanics."
msgstr ""

#: ../../docs/tutorials/xr/xr_room_scale.rst:217
msgid ""
"Here we have a standard character body with collision shape, and our XR "
"origin node and camera as normal children. We also have our neck helper node."
msgstr ""

#: ../../docs/tutorials/xr/xr_room_scale.rst:220
msgid ""
"Processing our character movement is done in the same three steps but "
"implemented slightly differently."
msgstr ""

#: ../../docs/tutorials/xr/xr_room_scale.rst:223
#, fuzzy
msgid ""
"The `Character centric movement demo <https://github.com/godotengine/godot-"
"demo-projects/tree/master/xr/openxr_character_centric_movement>`__ contains "
"a more elaborate example of the technique described below."
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati različite Godo demo projekte "
"`Godot demo projects <https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/tutorials/xr/xr_room_scale.rst:228
msgid ""
"In this approach step 1 is where all the magic happens. Just like with our "
"previous approach we will be applying our physical movement to the character "
"body, but we will counter that movement on the origin node."
msgstr ""

#: ../../docs/tutorials/xr/xr_room_scale.rst:232
msgid ""
"This will ensure that the players location stays in sync with the character "
"body's location."
msgstr ""

#: ../../docs/tutorials/xr/xr_room_scale.rst:281
msgid ""
"In essence the code above will move the character body to where the player "
"is, and then move the origin node back in equal amounts. The result is that "
"the player stays centered above the character body."
msgstr ""

#: ../../docs/tutorials/xr/xr_room_scale.rst:284
msgid ""
"We start with applying the rotation. The character body should be facing "
"where the player was looking the previous frame. We calculate our camera "
"orientation in the space of the character body. We can now calculate the "
"angle by which the player has rotated their head. We rotate our character "
"body by the same amount so our character body faces the same direction as "
"the player. And then we reverse the rotation on the origin node so the "
"camera ends up aligned with the player again."
msgstr ""

#: ../../docs/tutorials/xr/xr_room_scale.rst:291
msgid ""
"For the movement we do much the same. The character body should be where the "
"player was standing the previous frame. We calculate by how much the player "
"has moved from this location. Then we attempt to move the character body to "
"this location."
msgstr ""

#: ../../docs/tutorials/xr/xr_room_scale.rst:296
msgid ""
"As the player may hit a collision body and be stopped, we only move the "
"origin point back by the amount we actually moved the character body. The "
"player may thus move away from this location but that will be reflected in "
"the positioning of the player."
msgstr ""

#: ../../docs/tutorials/xr/xr_room_scale.rst:299
msgid "As with our previous solution we return true if this is the case."
msgstr ""

#: ../../docs/tutorials/xr/xr_room_scale.rst:304
msgid ""
"In this step we again apply the rotation based on controller input. However "
"in this case the code is nearly identical to how one would implement this in "
"a normal first person game."
msgstr ""

#: ../../docs/tutorials/xr/xr_room_scale.rst:328
msgid ""
"For step three we again apply the movement based on controller input. "
"However just like at step 2, we can now implement this as we would in a "
"normal first person game."
msgstr ""

#: ../../docs/tutorials/xr/xr_room_scale.rst:359
msgid "When the player walks to somewhere they shouldn't"
msgstr ""

#: ../../docs/tutorials/xr/xr_room_scale.rst:361
msgid ""
"Think of a situation where the player is outside a locked room. You don't "
"want the player to go into that room until the door is unlocked. You also "
"don't want the player to see what is in this room."
msgstr ""

#: ../../docs/tutorials/xr/xr_room_scale.rst:365
msgid ""
"The logic for moving the player through controller input nicely prevents "
"this. The player encounters a static body, and the code prevents the player "
"from moving into the room."
msgstr ""

#: ../../docs/tutorials/xr/xr_room_scale.rst:368
msgid ""
"However with XR, nothing is preventing the player from taking a real step "
"forward."
msgstr ""

#: ../../docs/tutorials/xr/xr_room_scale.rst:370
msgid ""
"With both the approaches worked out up above we will prevent the character "
"body from moving where the player can't go. As the player has physically "
"moved to this location, the camera will now have moved into the room."
msgstr ""

#: ../../docs/tutorials/xr/xr_room_scale.rst:373
msgid ""
"The logical solution would be to prevent the movement altogether and adjust "
"the placement of the XR origin point so the player stays outside of the room."
msgstr ""

#: ../../docs/tutorials/xr/xr_room_scale.rst:376
msgid ""
"The problem with this approach is that physical movement is now not "
"replicated in the virtual space. This will cause nausea for the player."
msgstr ""

#: ../../docs/tutorials/xr/xr_room_scale.rst:379
msgid ""
"What many XR games do instead, is to measure the distance between where the "
"player physically is, and where the players virtual body has been left "
"behind. As this distance increases, usually to a distance of a few "
"centimeters, the screen slowly blacks out."
msgstr ""

#: ../../docs/tutorials/xr/xr_room_scale.rst:383
msgid ""
"Our solutions up above would allow us to add this logic into the code at the "
"end of step 1."
msgstr ""

#: ../../docs/tutorials/xr/xr_room_scale.rst:385
msgid "Further improvements to the code presented could be:"
msgstr ""

#: ../../docs/tutorials/xr/xr_room_scale.rst:387
msgid "allowing controller input as long as this distance is still small,"
msgstr ""

#: ../../docs/tutorials/xr/xr_room_scale.rst:388
msgid ""
"still applying gravity to the player even when controller input is disabled."
msgstr ""

#: ../../docs/tutorials/xr/xr_room_scale.rst:391
msgid ""
"The movement demos in our demo repository contain an example of blacking out "
"the screen when a user walks into restricted areas."
msgstr ""

#: ../../docs/tutorials/xr/xr_room_scale.rst:394
msgid "Further suggestions for improvements"
msgstr ""

#: ../../docs/tutorials/xr/xr_room_scale.rst:396
msgid ""
"The above provides two good options as starting points for implementing room "
"scale XR games."
msgstr ""

#: ../../docs/tutorials/xr/xr_room_scale.rst:398
msgid ""
"A few more things that are worth pointing out that you will likely want to "
"implement:"
msgstr ""

#: ../../docs/tutorials/xr/xr_room_scale.rst:400
msgid ""
"The height of the camera can be used to detect whether the player is "
"standing up, crouching, jumping or lying down. You can adjust the size and "
"orientation of the collision shape accordingly. Extra bonus points for "
"adding multiple collision shapes so the head and body have their own, more "
"accurately sized, shapes."
msgstr ""

#: ../../docs/tutorials/xr/xr_room_scale.rst:403
msgid ""
"When a scene first loads, the player may be far away from the center of the "
"tracking space. This could result in the player spawning into a different "
"room than our origin point. The game will now attempt, and fail, to move the "
"player body from the starting point to where the player is standing. You "
"should implement a reset function that moves the origin point so the player "
"is in the correct starting position."
msgstr ""

#: ../../docs/tutorials/xr/xr_room_scale.rst:408
msgid ""
"Both of the above improvements require the player to be ready and standing "
"up straight. There is no guarantee as the player may still be putting their "
"headset on."
msgstr ""

#: ../../docs/tutorials/xr/xr_room_scale.rst:411
msgid ""
"Many games, including XR Tools, solve this by introducing an intro screen or "
"loading screen where the player must press a button when they are ready. "
"This starting environment is often a large location where the positioning of "
"the player has little impact on what the player sees. When the player is "
"ready, and presses the button, this is the moment you record the position "
"and height of the camera."
msgstr ""

#: ../../docs/tutorials/xr/openxr_hand_tracking.rst:4
msgid "The OpenXR hand tracking"
msgstr ""

#: ../../docs/tutorials/xr/openxr_hand_tracking.rst:6
msgid ""
"Hand tracking is the process by which the position and orientation of the "
"players hands are tracked, including the orientation of the players fingers. "
"We can identify 3 categories of this:"
msgstr ""

#: ../../docs/tutorials/xr/openxr_hand_tracking.rst:10
msgid ""
"One, hand tracking through external sensors such as cameras. This is what "
"Hololens, Quest, UltraLeap and similar devices do. This often results in "
"very accurate tracking of all fingers of the players hands."
msgstr ""

#: ../../docs/tutorials/xr/openxr_hand_tracking.rst:14
msgid ""
"Two, hand tracking through VR gloves. This method is still mostly "
"experimental but is likely to gain popularity soon. Gloves often have good "
"finger tracking capabilities but their real selling point is the ability to "
"restrict movement. This allows the sensation of touch. Gloves are often also "
"recognised as controllers and often will have additional controls such as "
"buttons embedded."
msgstr ""

#: ../../docs/tutorials/xr/openxr_hand_tracking.rst:20
msgid ""
"Three, inferred hand tracking. This has been the de facto approach since the "
"early days of VR. As we know the player is holding a controller and we know "
"the position of this controller, we can infer where to render the players "
"hand. Fingers can be positioned based on the controls the player is "
"interacting with. Many modern VR controllers have additional sensors to help "
"determine finger positions on the controller."
msgstr ""

#: ../../docs/tutorials/xr/openxr_hand_tracking.rst:29
msgid ""
"Traditionally inferred hand tracking has been the responsibility of the "
"game. However the principles behind the action map have somewhat limited the "
"viable options here. Valve is currently the only XR Runtime that has "
"implemented inferred hand tracking as part of the hand tracking extension. "
"There is an expectation that other XR Runtimes will follow this example in "
"the near future."
msgstr ""

#: ../../docs/tutorials/xr/openxr_hand_tracking.rst:34
msgid ""
"Until then we recommend that if your game depends on inferred hand tracking, "
"to use the hand assets that are part of Godot XR Tools."
msgstr ""

#: ../../docs/tutorials/xr/openxr_hand_tracking.rst:38
msgid "Tracking through interaction profiles"
msgstr ""

#: ../../docs/tutorials/xr/openxr_hand_tracking.rst:40
msgid ""
"Tracking the location and state of controllers are performed through "
"interaction profiles. Bindings can be set within the :ref:`action map "
"<doc_xr_action_map>`."
msgstr ""

#: ../../docs/tutorials/xr/openxr_hand_tracking.rst:43
msgid ""
"However it is important to realise that in OpenXR controllers are bound to "
"paths indicating the usage of these controllers. I.e. the controller held in "
"the players left hand is bound to ``/user/hand/left`` while the controller "
"in the players right hand is bound to ``/user/hand/right``. And while not "
"yet supported outside of the HTC tracker extension, it is likely OpenXR will "
"be extended with paths such as ``/user/foot/left`` and ``/user/foot/right`` "
"at some point."
msgstr ""

#: ../../docs/tutorials/xr/openxr_hand_tracking.rst:51
msgid ""
"This paradigm therefore begs the question what happens to a controller that "
"is not being held by a user. There is no answer to this question yet, this "
"is still being debated and the specification may change in the near future. "
"The behavior is thus undefined and can be different for different platforms."
msgstr ""

#: ../../docs/tutorials/xr/openxr_hand_tracking.rst:55
msgid ""
"The most common is that the controller will remain bound regardless of "
"whether the player is actually holding the controller."
msgstr ""

#: ../../docs/tutorials/xr/openxr_hand_tracking.rst:57
msgid ""
"However there are runtimes, such as the Quest, that can unbind a controller "
"when it is not being held by the user."
msgstr ""

#: ../../docs/tutorials/xr/openxr_hand_tracking.rst:59
msgid ""
"This may become the norm in the future and the expectation is that the "
"action map system will be enhanced accordingly."
msgstr ""

#: ../../docs/tutorials/xr/openxr_hand_tracking.rst:62
msgid "The hand tracking extension"
msgstr ""

#: ../../docs/tutorials/xr/openxr_hand_tracking.rst:64
msgid ""
"OpenXR has an extension that exposes hand tracking functionality. This "
"extension allows a game to request the hand skeleton with all bone positions "
"for each hand."
msgstr ""

#: ../../docs/tutorials/xr/openxr_hand_tracking.rst:70
msgid ""
"Copyright (c) 2017-2022, The Khronos Group Inc. SPDX-License-Identifier: CC-"
"BY-4.0"
msgstr ""

#: ../../docs/tutorials/xr/openxr_hand_tracking.rst:72
msgid ""
"The above image shows the joints that have to be provided by each XR runtime "
"that implements this extension."
msgstr ""

#: ../../docs/tutorials/xr/openxr_hand_tracking.rst:74
msgid ""
"Currently Godot exposes this functionality through the :ref:`OpenXRHand "
"<class_openxrhand>` node. This is a helper node that will retrieve the hand "
"tracking data from OpenXR and apply it to a skeleton in Godot. You select "
"either the left or right hand through the ``hand`` property on this node."
msgstr ""

#: ../../docs/tutorials/xr/openxr_hand_tracking.rst:78
msgid ""
"The hand asset itself has to be provided by the developer and is thus "
"separate from the OpenXRHand node. You set the ``hand_skeleton`` on the "
"OpenXRHand node to the skeleton it needs to apply the tracking data to."
msgstr ""

#: ../../docs/tutorials/xr/openxr_hand_tracking.rst:81
msgid ""
"If supported by the XR runtime you can also set the ``motion_range`` "
"property to limit how far the hand can close."
msgstr ""

#: ../../docs/tutorials/xr/openxr_hand_tracking.rst:83
msgid "The skeleton for this asset has to have the following bones:"
msgstr ""

#: ../../docs/tutorials/xr/openxr_hand_tracking.rst:85
#, fuzzy
msgid "OpenXR hand skeleton"
msgstr "Kreiranje Sadržaja"

#: ../../docs/tutorials/xr/openxr_hand_tracking.rst:89
msgid "Left hand"
msgstr ""

#: ../../docs/tutorials/xr/openxr_hand_tracking.rst:90
msgid "Right hand"
msgstr ""

#: ../../docs/tutorials/xr/openxr_hand_tracking.rst:91
msgid "Palm_L"
msgstr ""

#: ../../docs/tutorials/xr/openxr_hand_tracking.rst:92
msgid "Palm_R"
msgstr ""

#: ../../docs/tutorials/xr/openxr_hand_tracking.rst:93
msgid "Wrist_L"
msgstr ""

#: ../../docs/tutorials/xr/openxr_hand_tracking.rst:94
msgid "Wrist_R"
msgstr ""

#: ../../docs/tutorials/xr/openxr_hand_tracking.rst:95
msgid "Thumb_Metacarpal_L"
msgstr ""

#: ../../docs/tutorials/xr/openxr_hand_tracking.rst:96
msgid "Thumb_Metacarpal_R"
msgstr ""

#: ../../docs/tutorials/xr/openxr_hand_tracking.rst:97
msgid "Thumb_Proximal_L"
msgstr ""

#: ../../docs/tutorials/xr/openxr_hand_tracking.rst:98
msgid "Thumb_Proximal_R"
msgstr ""

#: ../../docs/tutorials/xr/openxr_hand_tracking.rst:99
msgid "Thumb_Distal_L"
msgstr ""

#: ../../docs/tutorials/xr/openxr_hand_tracking.rst:100
msgid "Thumb_Distal_R"
msgstr ""

#: ../../docs/tutorials/xr/openxr_hand_tracking.rst:101
msgid "Thumb_Tip_L"
msgstr ""

#: ../../docs/tutorials/xr/openxr_hand_tracking.rst:102
msgid "Thumb_Tip_R"
msgstr ""

#: ../../docs/tutorials/xr/openxr_hand_tracking.rst:103
msgid "Index_Metacarpal_L"
msgstr ""

#: ../../docs/tutorials/xr/openxr_hand_tracking.rst:104
msgid "Index_Metacarpal_R"
msgstr ""

#: ../../docs/tutorials/xr/openxr_hand_tracking.rst:105
msgid "Index_Proximal_L"
msgstr ""

#: ../../docs/tutorials/xr/openxr_hand_tracking.rst:106
msgid "Index_Proximal_R"
msgstr ""

#: ../../docs/tutorials/xr/openxr_hand_tracking.rst:107
msgid "Index_Intermediate_L"
msgstr ""

#: ../../docs/tutorials/xr/openxr_hand_tracking.rst:108
msgid "Index_Intermediate_R"
msgstr ""

#: ../../docs/tutorials/xr/openxr_hand_tracking.rst:109
msgid "Index_Distal_L"
msgstr ""

#: ../../docs/tutorials/xr/openxr_hand_tracking.rst:110
msgid "Index_Distal_R"
msgstr ""

#: ../../docs/tutorials/xr/openxr_hand_tracking.rst:111
msgid "Index_Tip_L"
msgstr ""

#: ../../docs/tutorials/xr/openxr_hand_tracking.rst:112
msgid "Index_Tip_R"
msgstr ""

#: ../../docs/tutorials/xr/openxr_hand_tracking.rst:113
msgid "Middle_Metacarpal_L"
msgstr ""

#: ../../docs/tutorials/xr/openxr_hand_tracking.rst:114
msgid "Middle_Metacarpal_R"
msgstr ""

#: ../../docs/tutorials/xr/openxr_hand_tracking.rst:115
msgid "Middle_Proximal_L"
msgstr ""

#: ../../docs/tutorials/xr/openxr_hand_tracking.rst:116
msgid "Middle_Proximal_R"
msgstr ""

#: ../../docs/tutorials/xr/openxr_hand_tracking.rst:117
msgid "Middle_Intermediate_L"
msgstr ""

#: ../../docs/tutorials/xr/openxr_hand_tracking.rst:118
msgid "Middle_Intermediate_R"
msgstr ""

#: ../../docs/tutorials/xr/openxr_hand_tracking.rst:119
msgid "Middle_Distal_L"
msgstr ""

#: ../../docs/tutorials/xr/openxr_hand_tracking.rst:120
msgid "Middle_Distal_R"
msgstr ""

#: ../../docs/tutorials/xr/openxr_hand_tracking.rst:121
msgid "Middle_Tip_L"
msgstr ""

#: ../../docs/tutorials/xr/openxr_hand_tracking.rst:122
msgid "Middle_Tip_R"
msgstr ""

#: ../../docs/tutorials/xr/openxr_hand_tracking.rst:123
msgid "Ring_Metacarpal_L"
msgstr ""

#: ../../docs/tutorials/xr/openxr_hand_tracking.rst:124
msgid "Ring_Metacarpal_R"
msgstr ""

#: ../../docs/tutorials/xr/openxr_hand_tracking.rst:125
msgid "Ring_Proximal_L"
msgstr ""

#: ../../docs/tutorials/xr/openxr_hand_tracking.rst:126
msgid "Ring_Proximal_R"
msgstr ""

#: ../../docs/tutorials/xr/openxr_hand_tracking.rst:127
msgid "Ring_Intermediate_L"
msgstr ""

#: ../../docs/tutorials/xr/openxr_hand_tracking.rst:128
msgid "Ring_Intermediate_R"
msgstr ""

#: ../../docs/tutorials/xr/openxr_hand_tracking.rst:129
msgid "Ring_Distal_L"
msgstr ""

#: ../../docs/tutorials/xr/openxr_hand_tracking.rst:130
msgid "Ring_Distal_R"
msgstr ""

#: ../../docs/tutorials/xr/openxr_hand_tracking.rst:131
msgid "Ring_Tip_L"
msgstr ""

#: ../../docs/tutorials/xr/openxr_hand_tracking.rst:132
msgid "Ring_Tip_R"
msgstr ""

#: ../../docs/tutorials/xr/openxr_hand_tracking.rst:133
msgid "Little_Metacarpal_L"
msgstr ""

#: ../../docs/tutorials/xr/openxr_hand_tracking.rst:134
msgid "Little_Metacarpal_R"
msgstr ""

#: ../../docs/tutorials/xr/openxr_hand_tracking.rst:135
msgid "Little_Proximal_L"
msgstr ""

#: ../../docs/tutorials/xr/openxr_hand_tracking.rst:136
msgid "Little_Proximal_R"
msgstr ""

#: ../../docs/tutorials/xr/openxr_hand_tracking.rst:137
msgid "Little_Intermediate_L"
msgstr ""

#: ../../docs/tutorials/xr/openxr_hand_tracking.rst:138
msgid "Little_Intermediate_R"
msgstr ""

#: ../../docs/tutorials/xr/openxr_hand_tracking.rst:139
msgid "Little_Distal_L"
msgstr ""

#: ../../docs/tutorials/xr/openxr_hand_tracking.rst:140
msgid "Little_Distal_R"
msgstr ""

#: ../../docs/tutorials/xr/openxr_hand_tracking.rst:141
msgid "Little_Tip_L"
msgstr ""

#: ../../docs/tutorials/xr/openxr_hand_tracking.rst:142
msgid "Little_Tip_R"
msgstr ""

#: ../../docs/tutorials/xr/openxr_hand_tracking.rst:146
msgid ""
"The skeleton data returned from different XR runtimes are often not "
"compatible which poses a problem for cross platform development."
msgstr ""

#: ../../docs/tutorials/xr/openxr_hand_tracking.rst:148
msgid ""
"For instance both Microsoft and Meta runtimes base the skeleton on the "
"actual hands of the player. These skeletons will thus conform to the size of "
"the players hand."
msgstr ""

#: ../../docs/tutorials/xr/openxr_hand_tracking.rst:151
msgid ""
"Contrast that to Valve where a fixed skeleton is used if inferred hand "
"tracking is applied."
msgstr ""

#: ../../docs/tutorials/xr/openxr_hand_tracking.rst:153
msgid ""
"We are still gathering experience on how best to deal with these differences "
"in the platforms."
msgstr ""

#: ../../docs/tutorials/xr/openxr_hand_tracking.rst:155
msgid "When exporting to Meta Quest you need to enable the following setting:"
msgstr ""

#: ../../docs/tutorials/xr/openxr_hand_tracking.rst:160
msgid "Body tracking"
msgstr ""

#: ../../docs/tutorials/xr/openxr_hand_tracking.rst:162
msgid ""
"At the time of writing, OpenXR does not support body tracking as part of the "
"core spec. We are expecting this to change in the near future as more and "
"more body tracking solutions are hitting the market."
msgstr ""

#: ../../docs/tutorials/xr/openxr_hand_tracking.rst:165
msgid ""
"For now the only option available here is through HTC trackers. There is an "
"extension that becomes available if HTC trackers are supported by the XR "
"runtime. These are fully exposed through the action map system."
msgstr ""

#: ../../docs/tutorials/xr/openxr_hand_tracking.rst:169
msgid ""
"Godot has full support for these and you can setup the trackers in the "
"action map. Each tracker is assigned a usage within the SteamVR interface."
msgstr ""

#: ../../docs/tutorials/xr/openxr_hand_tracking.rst:172
#, fuzzy
msgid "These are exposed through the following trackers:"
msgstr "Glavna dokumentacija za sajt je podeljena na sledeća poglavlja:"

#: ../../docs/tutorials/xr/openxr_hand_tracking.rst:174
msgid "HTC trackers"
msgstr ""

#: ../../docs/tutorials/xr/openxr_hand_tracking.rst:178
msgid "/user/vive_tracker_htcx/role/handheld_object"
msgstr ""

#: ../../docs/tutorials/xr/openxr_hand_tracking.rst:179
msgid "/user/vive_tracker_htcx/role/left_foot"
msgstr ""

#: ../../docs/tutorials/xr/openxr_hand_tracking.rst:180
msgid "/user/vive_tracker_htcx/role/right_foot"
msgstr ""

#: ../../docs/tutorials/xr/openxr_hand_tracking.rst:181
msgid "/user/vive_tracker_htcx/role/left_shoulder"
msgstr ""

#: ../../docs/tutorials/xr/openxr_hand_tracking.rst:182
msgid "/user/vive_tracker_htcx/role/right_shoulder"
msgstr ""

#: ../../docs/tutorials/xr/openxr_hand_tracking.rst:183
msgid "/user/vive_tracker_htcx/role/left_elbow"
msgstr ""

#: ../../docs/tutorials/xr/openxr_hand_tracking.rst:184
msgid "/user/vive_tracker_htcx/role/right_elbow"
msgstr ""

#: ../../docs/tutorials/xr/openxr_hand_tracking.rst:185
msgid "/user/vive_tracker_htcx/role/left_knee"
msgstr ""

#: ../../docs/tutorials/xr/openxr_hand_tracking.rst:186
msgid "/user/vive_tracker_htcx/role/right_knee"
msgstr ""

#: ../../docs/tutorials/xr/openxr_hand_tracking.rst:187
msgid "/user/vive_tracker_htcx/role/waist"
msgstr ""

#: ../../docs/tutorials/xr/openxr_hand_tracking.rst:188
msgid "/user/vive_tracker_htcx/role/chest"
msgstr ""

#: ../../docs/tutorials/xr/openxr_hand_tracking.rst:189
msgid "/user/vive_tracker_htcx/role/camera"
msgstr ""

#: ../../docs/tutorials/xr/openxr_hand_tracking.rst:190
msgid "/user/vive_tracker_htcx/role/keyboard"
msgstr ""

#: ../../docs/tutorials/xr/openxr_hand_tracking.rst:194
msgid "Some final words"
msgstr ""

#: ../../docs/tutorials/xr/openxr_hand_tracking.rst:196
msgid ""
"Hand tracking is an area that is still under active development and we are "
"expecting improvements in the near future."
msgstr ""

#: ../../docs/tutorials/xr/openxr_hand_tracking.rst:198
msgid ""
"The underlying principle that we're hoping will eventuate is that the action "
"map will be used to handle interactions, while the hand tracking extension "
"will primarily be a means for visualising the players hand. The hope here is "
"that improvements to the OpenXR specification will ensure better portability "
"between platforms."
msgstr ""

#: ../../docs/tutorials/xr/openxr_passthrough.rst:4
msgid "The OpenXR passthrough"
msgstr ""

#: ../../docs/tutorials/xr/openxr_passthrough.rst:6
msgid ""
"Passthrough is a technique where camera images are used to present the "
"environment of the user as the background. This turns a VR headset into an "
"AR headset, often referred to as Mixed Reality or MR."
msgstr ""

#: ../../docs/tutorials/xr/openxr_passthrough.rst:11
msgid ""
"As passthrough is relatively new there isn't a singular way this is "
"implemented across platforms. There may be additions in the future so this "
"is a work in progress."
msgstr ""

#: ../../docs/tutorials/xr/openxr_passthrough.rst:15
msgid "Passthrough extension"
msgstr ""

#: ../../docs/tutorials/xr/openxr_passthrough.rst:17
msgid ""
"OpenXR has a vendor extension for passthrough submitted by Meta. Currently "
"this extension is only supported on Quest and PICO but may be adopted by "
"other headsets in the future."
msgstr ""

#: ../../docs/tutorials/xr/openxr_passthrough.rst:20
msgid ""
":ref:`XRInterface <class_xrinterface>` has entry points for passthrough so "
"different interfaces can implement this feature. For :ref:`OpenXRInterface "
"<class_openxrinterface>` the meta passthrough extension is implemented here."
msgstr ""

#: ../../docs/tutorials/xr/openxr_passthrough.rst:23
msgid ""
"In code you can call ``is_passthrough_supported`` to check if this extension "
"is available. If so you can simply enable passthrough by calling "
"``start_passthrough``. You can call ``stop_passthrough`` to disable "
"passthrough."
msgstr ""

#: ../../docs/tutorials/xr/openxr_passthrough.rst:27
msgid ""
"You do need to make sure the background is transparent. You need to enable "
"the ``transparent_bg`` property on the viewport. Some background environment "
"settings will still fill the background with an opaque color, you can use a "
"``custom color`` with a color that has alpha set to 0."
msgstr ""

#: ../../docs/tutorials/xr/openxr_passthrough.rst:32
msgid "The OpenXR runtime will display the camera image as the background."
msgstr ""

#: ../../docs/tutorials/xr/openxr_passthrough.rst:36
msgid "For privacy reasons **no access** is given to the camera image."
msgstr ""

#: ../../docs/tutorials/xr/openxr_passthrough.rst:40
msgid ""
"After passthrough is enabled it is possible to change settings that will "
"break passthrough. Be sure not to disable the ``transparent_bg`` setting or "
"change the environment blend mode. This will result in the camera image no "
"longer being visible but you still incur the overhead."
msgstr ""

#: ../../docs/tutorials/xr/openxr_passthrough.rst:44
msgid "Always use ``stop_passthrough`` if you wish to turn off passthrough."
msgstr ""

#: ../../docs/tutorials/xr/openxr_passthrough.rst:46
msgid ""
"Finally, for using passthrough on the Quest you must set the following "
"export property:"
msgstr ""

#: ../../docs/tutorials/xr/openxr_passthrough.rst:51
msgid "Passthrough through AR"
msgstr ""

#: ../../docs/tutorials/xr/openxr_passthrough.rst:53
msgid ""
"Some of the headsets recently adding OpenXR support have taken a different "
"approach. They simply mimic being an AR device. The Lynx R1 is such a device "
"but others may be doing the same."
msgstr ""

#: ../../docs/tutorials/xr/openxr_passthrough.rst:56
msgid ""
"The following thus applies to both passthrough devices that mimic AR, and "
"actual AR devices."
msgstr ""

#: ../../docs/tutorials/xr/openxr_passthrough.rst:58
msgid ""
"If ``is_passthrough_supported`` returns false the next step is to call "
"``get_supported_environment_blend_modes``. This will return a list of "
"supported blend modes for submitting the main render image to OpenXR."
msgstr ""

#: ../../docs/tutorials/xr/openxr_passthrough.rst:61
msgid ""
"We need to check if ``XR_ENV_BLEND_MODE_ALPHA_BLEND`` is present in this "
"list. If so we can tell OpenXR to expect an image that can be alpha blended "
"with a background. To do this, we simply call "
"``set_environment_blend_mode(xr_interface.XR_ENV_BLEND_MODE_ALPHA_BLEND)``."
msgstr ""

#: ../../docs/tutorials/xr/openxr_passthrough.rst:65
msgid ""
"We must also set ``transparent_bg`` to true and adjust the environment to "
"ensure we submit the right image."
msgstr ""

#: ../../docs/tutorials/xr/openxr_passthrough.rst:68
msgid "Putting it together"
msgstr ""

#: ../../docs/tutorials/xr/openxr_passthrough.rst:70
msgid "Putting the above together we can use the following code as a base:"
msgstr ""

#: ../../docs/contributing/ways_to_contribute.rst:4
msgid "Ways to contribute"
msgstr ""

#: ../../docs/contributing/ways_to_contribute.rst:6
msgid ""
"Godot Engine is a non-profit, community-driven free and open source project. "
"Almost all (but our lead dev Juan, more on that below) developers are "
"working *pro bono* on their free time, out of personal interest and for the "
"love of creating a libre engine of exceptional quality."
msgstr ""

#: ../../docs/contributing/ways_to_contribute.rst:11
msgid ""
"This means that to thrive, Godot needs as many users as possible to get "
"involved by contributing to the engine. There are many ways to contribute to "
"such a big project, making it possible for everybody to bring something "
"positive to the engine, regardless of their skill set:"
msgstr ""

#: ../../docs/contributing/ways_to_contribute.rst:16
msgid ""
"**Be part of the community.** The best way to contribute to Godot and help "
"it become ever better is simply to use the engine and promote it by word-of-"
"mouth, in the credits or splash screen of your games, blog posts, tutorials, "
"videos, demos, gamedev or free software events, support on the Q&A, forums, "
"Contributors Chat, Discord, etc. Participate! Being a user and advocate "
"helps spread the word about our great engine, which has no marketing budget "
"and can therefore only rely on its community to become more mainstream."
msgstr ""

#: ../../docs/contributing/ways_to_contribute.rst:25
msgid ""
"**Make games.** It's no secret that, to convince new users and especially "
"the industry at large that Godot is a relevant market player, we need great "
"games made with Godot. We know that the engine has a lot of potential, both "
"for 2D and 3D games, but given its young age we still lack big releases that "
"will draw attention to Godot. So keep working on your awesome projects, each "
"new game increases our credibility on the gamedev market!"
msgstr ""

#: ../../docs/contributing/ways_to_contribute.rst:32
msgid ""
"**Get involved in the engine's development.** This can be by contributing "
"code via pull requests, testing the development snapshots or directly the "
"git *master* branch, report bugs or suggest enhancements on the issue "
"tracker, improve the official documentation (both the class reference and "
"tutorials) and its translations. The following sections will cover each of "
"those \"direct\" ways of contributing to the engine."
msgstr ""

#: ../../docs/contributing/ways_to_contribute.rst:40
msgid ""
"**Donate.** Godot is a non-profit project, but it can still benefit from "
"user donations for many things. Apart from usual expenses such as hosting "
"costs or promotional material on events, we also use donation money to "
"acquire hardware when necessary (e.g. we used donation money to buy a "
"MacBook Pro to implement Retina/HiDPI support and various other macOS-"
"related features). Most importantly, we also used donation money to hire "
"core developers so they can work full-time on the engine. Even with a low "
"monthly wage, we need a steady donation income to continue doing this, which "
"has been very beneficial to the project so far. So if you want to donate "
"some money to the project, check `our website <https://godotengine.org/"
"donate>`_ for details."
msgstr ""

#: ../../docs/contributing/ways_to_contribute.rst:54
msgid "Contributing code"
msgstr ""

#: ../../docs/contributing/ways_to_contribute.rst:56
msgid ""
"The possibility to study, use, modify and redistribute modifications of the "
"engine's source code are the fundamental rights that Godot's `MIT <https://"
"tldrlegal.com/license/mit-license>`_ license grants you, making it `free and "
"open source software <https://en.wikipedia.org/wiki/Free_and_open-"
"source_software>`_."
msgstr ""

#: ../../docs/contributing/ways_to_contribute.rst:61
msgid ""
"As such, everyone is entitled to modify `Godot's source code <https://github."
"com/godotengine/godot>`_, and send those modifications back to the upstream "
"project in the form of a patch (a text file describing the changes in a "
"ready-to-apply manner) or - in the modern workflow that we use - via a so-"
"called \"pull request\" (PR), i.e. a proposal to directly merge one or more "
"Git commits (patches) into the main development branch."
msgstr ""

#: ../../docs/contributing/ways_to_contribute.rst:68
msgid "Contributing code changes upstream has two big advantages:"
msgstr ""

#: ../../docs/contributing/ways_to_contribute.rst:70
msgid ""
"Your own code will be reviewed and improved by other developers, and will be "
"further maintained directly in the upstream project, so you won't have to "
"reapply your own changes every time you move to a newer version. On the "
"other hand it comes with a responsibility, as your changes have to be "
"generic enough to be beneficial to all users, and not just your project; so "
"in some cases it might still be relevant to keep your changes only for your "
"own project, if they are too specific."
msgstr ""

#: ../../docs/contributing/ways_to_contribute.rst:78
msgid ""
"The whole community will benefit from your work, and other contributors will "
"behave the same way, contributing code that will be beneficial to you. At "
"the time of this writing, over 2,000 developers have contributed code "
"changes to the engine!"
msgstr ""

#: ../../docs/contributing/ways_to_contribute.rst:83
msgid ""
"To ensure good collaboration and overall quality, the Godot developers "
"enforce some rules for code contributions, for example regarding the style "
"to use in the C++ code (indentation, brackets, etc.) or the Git and PR "
"workflow."
msgstr ""

#: ../../docs/contributing/ways_to_contribute.rst:87
msgid ""
"A good place to start is by searching for issues tagged as `good first issue "
"<https://github.com/godotengine/godot/issues?"
"q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22>`_ on GitHub."
msgstr ""

#: ../../docs/contributing/ways_to_contribute.rst:91
msgid ""
"Technical details about the PR workflow are outlined in a specific section, :"
"ref:`doc_pr_workflow`."
msgstr ""

#: ../../docs/contributing/ways_to_contribute.rst:94
msgid ""
"Details about the code style guidelines and the ``clang-format`` tool used "
"to enforce them are outlined in :ref:`doc_code_style_guidelines`."
msgstr ""

#: ../../docs/contributing/ways_to_contribute.rst:98
msgid ""
"All pull requests must go through a review process before being accepted. "
"Depending on the scope of the changes, it may take some time for a "
"maintainer responsible for the modified part of the engine to provide their "
"review. We value all of our contributors and ask them to be patient in the "
"meantime, as it is expected that in an open source project like Godot, there "
"is going to be way more contributions than people validating them."
msgstr ""

#: ../../docs/contributing/ways_to_contribute.rst:105
msgid ""
"To make sure that your time and efforts aren't wasted, it is recommended to "
"vet the idea first before implementing it and putting it for a review as a "
"PR. To that end, Godot has a `proposal system <https://github.com/"
"godotengine/godot-proposals>`_. Its usage is encouraged to plan changes and "
"discuss them with the community. Implementation details can also be "
"discussed with other contributors on the `Godot Contributors Chat <https://"
"chat.godotengine.org/>`_."
msgstr ""

#: ../../docs/contributing/ways_to_contribute.rst:111
msgid ""
"Proposals are only required when working on an enhancement or a new feature. "
"Bug reports are sufficient for fixing issues."
msgstr ""

#: ../../docs/contributing/ways_to_contribute.rst:115
msgid "Testing and reporting issues"
msgstr ""

#: ../../docs/contributing/ways_to_contribute.rst:117
msgid ""
"Another great way of contributing to the engine is to test development "
"releases or the development branch and to report issues. It is also helpful "
"to report issues discovered in stable releases, so that they can be fixed in "
"the development branch and in future maintenance releases."
msgstr ""

#: ../../docs/contributing/ways_to_contribute.rst:123
msgid "Testing development versions"
msgstr ""

#: ../../docs/contributing/ways_to_contribute.rst:125
msgid "To help with the testing, you have several possibilities:"
msgstr ""

#: ../../docs/contributing/ways_to_contribute.rst:127
msgid ""
"Compile the engine from source yourself, following the instructions of the :"
"ref:`Compiling <toc-devel-compiling>` page for your platform."
msgstr ""

#: ../../docs/contributing/ways_to_contribute.rst:130
msgid ""
"Test official pre-release binaries when they are announced (usually on the "
"blog and other community platforms), such as alpha, beta and release "
"candidate (RC) builds."
msgstr ""

#: ../../docs/contributing/ways_to_contribute.rst:133
msgid ""
"Test \"trusted\" unofficial builds of the development branch; just ask "
"community members for reliable providers. Whenever possible, it's best to "
"use official binaries or to compile yourself though, to be sure about the "
"provenance of your binaries."
msgstr ""

#: ../../docs/contributing/ways_to_contribute.rst:138
msgid ""
"As mentioned previously, it is also helpful to keep your eyes peeled for "
"potential bugs that might still be present in the stable releases, "
"especially when using some niche features of the engine which might get less "
"testing by the developers."
msgstr ""

#: ../../docs/contributing/ways_to_contribute.rst:144
msgid "Filing an issue on GitHub"
msgstr ""

#: ../../docs/contributing/ways_to_contribute.rst:146
msgid ""
"Godot uses `GitHub's issue tracker <https://github.com/godotengine/godot/"
"issues>`_ for bug reports. When you start filing a bug report, you’ll be "
"given a form to fill out. Please try to follow it so that all issues are "
"consistent and provide the required information."
msgstr ""

#: ../../docs/contributing/ways_to_contribute.rst:152
#: ../../docs/contributing/documentation/contributing_to_the_documentation.rst:4
msgid "Contributing to the documentation"
msgstr ""

#: ../../docs/contributing/ways_to_contribute.rst:154
msgid ""
"There are two separate resources referred to as \"documentation\" in Godot:"
msgstr ""

#: ../../docs/contributing/ways_to_contribute.rst:156
msgid ""
"**The class reference.** This is the documentation for the complete Godot "
"API as exposed to GDScript and the other scripting languages. It can be "
"consulted offline, directly in Godot's code editor, or online at Godot :ref:"
"`Class Reference <doc_class_reference>`. To contribute to the class "
"reference, you have to edit the XML file corresponding to the class and make "
"a pull request. See :ref:`doc_updating_the_class_reference` and :ref:"
"`doc_class_reference_primer` for more details."
msgstr ""

#: ../../docs/contributing/ways_to_contribute.rst:164
msgid ""
"**The tutorials and engine documentation and its translations.** This is the "
"part you are reading now, which is distributed in the HTML format. Its "
"contents are generated from plain text files in the reStructured Text (rst) "
"format, to which you can contribute via pull requests on the `godot-docs "
"<https://github.com/godotengine/godot-docs>`_ GitHub repository. See :ref:"
"`doc_contributing_to_the_documentation` for more details."
msgstr ""

#: ../../docs/contributing/ways_to_contribute.rst:172
#, fuzzy
msgid "Contributing translations"
msgstr "Kreiranje Sadržaja"

#: ../../docs/contributing/ways_to_contribute.rst:174
msgid ""
"To make Godot accessible to everyone, including users who may prefer "
"resources in their native language instead of English, our community helps "
"translate both the Godot editor and its documentation in many languages."
msgstr ""

#: ../../docs/contributing/ways_to_contribute.rst:178
msgid "See :ref:`doc_editor_and_docs_localization` for more details."
msgstr ""

#: ../../docs/contributing/workflow/index.rst:4
#, fuzzy
msgid "Contribution workflow"
msgstr "Kreiranje Sadržaja"

#: ../../docs/contributing/workflow/index.rst:6
msgid ""
"Godot is a large project, both in terms of the codebase and the workload for "
"contributors. The guides below serve as a helper when you get stuck dealing "
"with Git or GitHub, or if you are generally interested in how maintainers "
"approach the project."
msgstr ""

#: ../../docs/contributing/workflow/bisecting_regressions.rst:4
msgid "Bisecting regressions"
msgstr ""

#: ../../docs/contributing/workflow/bisecting_regressions.rst:8
msgid ""
"Bisecting is a way to find regressions in software. After reporting a bug on "
"the `Godot repository on GitHub <https://github.com/godotengine/godot>`__, "
"you may be asked by a contributor to *bisect* the issue. Bisecting makes it "
"possible for contributors to fix bugs faster, as they can know in advance "
"which commit caused the regression. Your effort will be widely appreciated :)"
msgstr ""

#: ../../docs/contributing/workflow/bisecting_regressions.rst:14
msgid "The guide below explains how to find a regression by bisecting."
msgstr ""

#: ../../docs/contributing/workflow/bisecting_regressions.rst:17
msgid "What is bisecting?"
msgstr ""

#: ../../docs/contributing/workflow/bisecting_regressions.rst:19
msgid ""
"Godot developers use the `Git <https://git-scm.com/>`__ version control "
"system. In the context of Git, bisecting is the process of performing a "
"manual `binary search <https://en.wikipedia.org/wiki/"
"Binary_search_algorithm>`__ to determine when a regression appeared. While "
"it's typically used for bugs, it can also be used to find other kinds of "
"unexpected changes such as performance regressions."
msgstr ""

#: ../../docs/contributing/workflow/bisecting_regressions.rst:27
msgid "Using official builds to speed up bisecting"
msgstr ""

#: ../../docs/contributing/workflow/bisecting_regressions.rst:29
msgid ""
"Before using Git's ``bisect`` command, we strongly recommend trying to "
"reproduce the bug with an older (or newer) official release. This greatly "
"reduces the range of commits that potentially need to be built from source "
"and tested. You can find binaries of official releases, as well as alphas, "
"betas, and release candidates `here <https://downloads.tuxfamily.org/"
"godotengine/>`__."
msgstr ""

#: ../../docs/contributing/workflow/bisecting_regressions.rst:35
msgid ""
"If you have experience with Godot 3.x and can reproduce an issue with Godot "
"4.0, we recommend trying to reproduce the issue in the latest Godot 3.x "
"version (if the feature exhibiting the bug is present in 3.x). This can be "
"used to check whether the issue is a regression in 4.0 or not."
msgstr ""

#: ../../docs/contributing/workflow/bisecting_regressions.rst:40
msgid ""
"If the issue **is present** in 3.x, then you'll need to check whether the "
"issue occurs in older 3.x versions as well."
msgstr ""

#: ../../docs/contributing/workflow/bisecting_regressions.rst:42
msgid ""
"If the issue is **not present** in 3.x, then you can try older 4.0 alphas "
"and betas to determine when the regression started."
msgstr ""

#: ../../docs/contributing/workflow/bisecting_regressions.rst:47
msgid ""
"Project files may be incompatible between Godot versions. **Make a backup of "
"your project** before starting the bisection process."
msgstr ""

#: ../../docs/contributing/workflow/bisecting_regressions.rst:50
msgid ""
"Going from the oldest to the newest build generally reduces the risk of the "
"project not being able to successfully open in the editor, thanks to "
"backwards compatibility. Try to reduce your project to the smallest "
"repeatable example too. The more minimal the project is, the more likely "
"you'll be able to open it without compatibility issues in newer engine "
"versions."
msgstr ""

#: ../../docs/contributing/workflow/bisecting_regressions.rst:58
msgid "The Git bisect command"
msgstr ""

#: ../../docs/contributing/workflow/bisecting_regressions.rst:60
msgid ""
"If you've found a build that didn't exhibit the bug in the above testing "
"process, you can now start bisecting the regression. The Git version control "
"system offers a built-in command for this: ``git bisect``. This makes the "
"process semi-automated as you only have to build the engine, run it and try "
"to reproduce the bug."
msgstr ""

#: ../../docs/contributing/workflow/bisecting_regressions.rst:68
msgid ""
"Before bisecting a regression, you need to set up a build environment to "
"compile Godot from source. To do so, read the :ref:`Compiling <toc-devel-"
"compiling>` page for your target platform. (Compiling Godot from source "
"doesn't require C++ programming knowledge.)"
msgstr ""

#: ../../docs/contributing/workflow/bisecting_regressions.rst:73
msgid ""
"Note that compiling Godot can take a while on slow hardware (up an hour for "
"each full rebuild on a slow dual-core CPU). This means the full process can "
"take up to several hours. If your hardware is too slow, you may want to stop "
"there and report the results of your \"pre-bisecting\" on the GitHub issue "
"so another contributor can continue bisecting from there."
msgstr ""

#: ../../docs/contributing/workflow/bisecting_regressions.rst:80
msgid "Determine the commit hashes"
msgstr ""

#: ../../docs/contributing/workflow/bisecting_regressions.rst:82
msgid ""
"To start bisecting, you must first determine the commit hashes (identifiers) "
"of the \"bad\" and \"good\" build. \"bad\" refers to the build that exhibits "
"the bug, whereas \"good\" refers to the version that doesn't exhibit the "
"bug. If you're using a pre-release build as the \"good\" or \"bad\" build, "
"browse the `download mirror <https://downloads.tuxfamily.org/godotengine/"
">`__, go to the folder that contains the pre-release you downloaded and look "
"for the ``README.txt`` file. The commit hash is written inside that file."
msgstr ""

#: ../../docs/contributing/workflow/bisecting_regressions.rst:90
msgid ""
"If you're using a stable release as the \"good\" or \"bad\" build, use one "
"of the following commit hashes depending on the version:"
msgstr ""

#: ../../docs/contributing/workflow/bisecting_regressions.rst:119
msgid ""
"You can also use this Bash function to retrieve the Git commit hash of a pre-"
"release build (add it to your ``$HOME/.bashrc`` or similar):"
msgstr ""

#: ../../docs/contributing/workflow/bisecting_regressions.rst:130
msgid "Example usage:"
msgstr ""

#: ../../docs/contributing/workflow/bisecting_regressions.rst:136
msgid ""
"To refer to the latest state of the master branch, you can use ``master`` "
"instead of a commit hash. Note that unlike tagged releases or snapshot "
"commit hashes, ``master`` is a perpetually moving target."
msgstr ""

#: ../../docs/contributing/workflow/bisecting_regressions.rst:141
#, fuzzy
msgid "Build the engine"
msgstr "Kreiranje Sadržaja"

#: ../../docs/contributing/workflow/bisecting_regressions.rst:143
msgid ""
":ref:`Get Godot's source code using Git <doc_getting_source>`. Once this is "
"done, in the terminal window, use ``cd`` to reach the Godot repository "
"folder and enter the following command:"
msgstr ""

#: ../../docs/contributing/workflow/bisecting_regressions.rst:155
msgid "Compile Godot. This assumes you've set up a build environment:"
msgstr ""

#: ../../docs/contributing/workflow/bisecting_regressions.rst:162
#, fuzzy
msgid "Run the engine"
msgstr "Kreiranje Sadržaja"

#: ../../docs/contributing/workflow/bisecting_regressions.rst:164
msgid ""
"Run the binary located in the ``bin/`` folder and try to reproduce the bug."
msgstr ""

#: ../../docs/contributing/workflow/bisecting_regressions.rst:168
msgid ""
":ref:`Double-check the output file name "
"<doc_introduction_to_the_buildsystem_resulting_binary>` in ``bin/`` to make "
"sure you're actually running the binary you've just compiled. Different "
"Godot versions will output binaries with different names."
msgstr ""

#: ../../docs/contributing/workflow/bisecting_regressions.rst:172
msgid "If the build **still** exhibits the bug, run the following command:"
msgstr ""

#: ../../docs/contributing/workflow/bisecting_regressions.rst:178
msgid "If the build **does not** exhibit the bug, run the following command:"
msgstr ""

#: ../../docs/contributing/workflow/bisecting_regressions.rst:184
msgid ""
"After entering one of the commands above, Git will switch to a different "
"commit. You should now build Godot again, try to reproduce the bug, then "
"enter ``git bisect good`` or ``git bisect bad`` depending on the result. "
"You'll have to repeat this several times. The longer the commit range, the "
"more steps will be required. 5 to 10 steps are usually sufficient to find "
"most regressions; Git will remind you of the number of steps remaining (in "
"the worst case scenario)."
msgstr ""

#: ../../docs/contributing/workflow/bisecting_regressions.rst:191
msgid ""
"Once you've completed enough steps, Git will display the commit hash where "
"the regression appeared. Write this commit hash as a comment to the GitHub "
"issue you've bisected. This will help in solving the issue. Thanks again for "
"contributing to Godot :)"
msgstr ""

#: ../../docs/contributing/workflow/bisecting_regressions.rst:198
msgid ""
"You can read the full documentation on ``git bisect`` `here <https://git-scm."
"com/docs/git-bisect>`__."
msgstr ""

#: ../../docs/contributing/workflow/bug_triage_guidelines.rst:4
msgid "Bug triage guidelines"
msgstr ""

#: ../../docs/contributing/workflow/bug_triage_guidelines.rst:6
msgid ""
"This page describes the typical workflow of the bug triage team aka bugsquad "
"when handling issues and pull requests on Godot's `GitHub repository "
"<https://github.com/godotengine/godot>`__. It is bound to evolve together "
"with the bugsquad, so do not hesitate to propose modifications to the "
"following guidelines."
msgstr ""

#: ../../docs/contributing/workflow/bug_triage_guidelines.rst:13
msgid "Issues management"
msgstr ""

#: ../../docs/contributing/workflow/bug_triage_guidelines.rst:15
msgid "GitHub proposes various features to manage issues:"
msgstr ""

#: ../../docs/contributing/workflow/bug_triage_guidelines.rst:17
msgid "Set one or several labels from a predefined list"
msgstr ""

#: ../../docs/contributing/workflow/bug_triage_guidelines.rst:18
msgid "Set one milestone from a predefined list"
msgstr ""

#: ../../docs/contributing/workflow/bug_triage_guidelines.rst:19
msgid "Keep track of the issue in the project dashboard"
msgstr ""

#: ../../docs/contributing/workflow/bug_triage_guidelines.rst:20
msgid ""
"Define one contributor as \"assignee\" among the Godot engine organization "
"members"
msgstr ""

#: ../../docs/contributing/workflow/bug_triage_guidelines.rst:23
msgid ""
"As the Godot engine organization on GitHub currently has a restricted number "
"of contributors, we do not use assignees extensively for now. All "
"contributors are welcome to take on any issue, if relevant after mentioning "
"it on the issue ticket and/or discussing the best way to resolve it with "
"other developers."
msgstr ""

#: ../../docs/contributing/workflow/bug_triage_guidelines.rst:29
msgid "For the time being, we do not use the project dashboard feature either."
msgstr ""

#: ../../docs/contributing/workflow/bug_triage_guidelines.rst:31
msgid ""
"As far as possible, we try to assign labels (and milestones, when relevant) "
"to both issues and pull requests."
msgstr ""

#: ../../docs/contributing/workflow/bug_triage_guidelines.rst:35
msgid "Labels"
msgstr ""

#: ../../docs/contributing/workflow/bug_triage_guidelines.rst:37
msgid "The following labels are currently defined in the Godot repository:"
msgstr ""

#: ../../docs/contributing/workflow/bug_triage_guidelines.rst:39
msgid "**Categories:**"
msgstr ""

#: ../../docs/contributing/workflow/bug_triage_guidelines.rst:41
#: ../../docs/contributing/workflow/bug_triage_guidelines.rst:158
msgid ""
"*Archived*: either a duplicate of another issue, or invalid. Such an issue "
"would also be closed."
msgstr ""

#: ../../docs/contributing/workflow/bug_triage_guidelines.rst:43
msgid ""
"*Breaks compat*: describes something that can only be fixed by breaking "
"compatibility with existing projects."
msgstr ""

#: ../../docs/contributing/workflow/bug_triage_guidelines.rst:45
msgid "*Bug*: describes something that is not working properly."
msgstr ""

#: ../../docs/contributing/workflow/bug_triage_guidelines.rst:46
#: ../../docs/contributing/workflow/bug_triage_guidelines.rst:162
msgid ""
"*Cherrypick*: describes something that can be backported to a stable branch "
"after being merged in the ``master`` branch."
msgstr ""

#: ../../docs/contributing/workflow/bug_triage_guidelines.rst:48
msgid ""
"*Confirmed*: has been confirmed by at least one other contributor than the "
"bug reporter (typically for *Bug* reports). The purpose of this label is to "
"let developers know which issues are still reproducible when they want to "
"select what to work on. It is therefore a good practice to add in a comment "
"on what platform and what version or commit of Godot the issue could be "
"reproduced; if a developer looks at the issue one year later, the "
"*Confirmed* label may not be relevant anymore."
msgstr ""

#: ../../docs/contributing/workflow/bug_triage_guidelines.rst:56
msgid ""
"*Crash:* describes a bug that causes the engine to crash. This label is only "
"used for \"hard\" crashes, not freezes."
msgstr ""

#: ../../docs/contributing/workflow/bug_triage_guidelines.rst:58
#: ../../docs/contributing/workflow/bug_triage_guidelines.rst:165
msgid ""
"*Discussion*: the issue is not consensual and needs further discussion to "
"define what exactly should be done to address the topic."
msgstr ""

#: ../../docs/contributing/workflow/bug_triage_guidelines.rst:61
msgid ""
"*Documentation*: issue related to the documentation. Mainly to request "
"enhancements in the API documentation. Issues related to the ReadTheDocs "
"documentation should be filed on the `godot-docs <https://github.com/"
"godotengine/godot-docs>`_ repository."
msgstr ""

#: ../../docs/contributing/workflow/bug_triage_guidelines.rst:65
msgid ""
"*Enhancement*: describes a proposed enhancement to an existing functionality."
msgstr ""

#: ../../docs/contributing/workflow/bug_triage_guidelines.rst:67
msgid ""
"*Feature proposal*: describes a wish for a new feature to be implemented. "
"Note that the main Godot repository no longer accepts feature requests. "
"Please use `godot-proposals <https://github.com/godotengine/godot-"
"proposals>`__ instead."
msgstr ""

#: ../../docs/contributing/workflow/bug_triage_guidelines.rst:71
msgid ""
"*For PR meeting*: the issue needs to be discussed in a pull request meeting. "
"These meetings are public and are held on the `Godot Contributors Chat "
"<https://chat.godotengine.org/>`_."
msgstr ""

#: ../../docs/contributing/workflow/bug_triage_guidelines.rst:73
#: ../../docs/contributing/workflow/bug_triage_guidelines.rst:169
msgid ""
"*Good first issue*: the issue is *assumed* to be an easy one to fix, which "
"makes it a great fit for new contributors who want to become familiar with "
"the code base. It should be removed while an active PR is available, that "
"resolves this issue."
msgstr ""

#: ../../docs/contributing/workflow/bug_triage_guidelines.rst:77
msgid ""
"*High priority:* the issue is particularly important as it can prevent "
"people from releasing their projects or cause data loss."
msgstr ""

#: ../../docs/contributing/workflow/bug_triage_guidelines.rst:79
msgid ""
"*Needs testing*: the issue/pull request could not be completely tested and "
"thus need further testing. This can mean that it needs to be tested on "
"different hardware/software configurations or even that the steps to "
"reproduce are not certain."
msgstr ""

#: ../../docs/contributing/workflow/bug_triage_guidelines.rst:83
#: ../../docs/contributing/workflow/bug_triage_guidelines.rst:173
msgid ""
"*Needs work*: the pull request needs additional work before it can be merged."
msgstr ""

#: ../../docs/contributing/workflow/bug_triage_guidelines.rst:84
msgid ""
"*Performance*: issues that directly impact engine or editor performance. Can "
"also be used for pull requests that improve performance or add low-end-"
"friendly options. Should not be coupled with *Usability*."
msgstr ""

#: ../../docs/contributing/workflow/bug_triage_guidelines.rst:87
msgid "*Production*: Relates to the production team."
msgstr ""

#: ../../docs/contributing/workflow/bug_triage_guidelines.rst:88
msgid ""
"*Regression*: the bug appeared after a stable release not exhibiting the bug "
"was released."
msgstr ""

#: ../../docs/contributing/workflow/bug_triage_guidelines.rst:90
#: ../../docs/contributing/workflow/bug_triage_guidelines.rst:175
msgid ""
"*Salvageable*: the pull request can't be merged due to design issues or "
"merge conflicts and its author is not active anymore. However, it can still "
"be picked up by an external contributor to bring it to a mergeable state. To "
"do so, you need to open a new pull request based on the original pull "
"request."
msgstr ""

#: ../../docs/contributing/workflow/bug_triage_guidelines.rst:94
#: ../../docs/contributing/workflow/bug_triage_guidelines.rst:179
msgid ""
"*Tracker*: issue used to track other issues (like all issues related to the "
"plugin system)."
msgstr ""

#: ../../docs/contributing/workflow/bug_triage_guidelines.rst:96
msgid ""
"*Usability*: issues that directly impact user usability. Should not be "
"coupled with *Performance*."
msgstr ""

#: ../../docs/contributing/workflow/bug_triage_guidelines.rst:98
msgid ""
"The categories are used for general triage of the issues. They can be "
"combined in some way when relevant, e.g. an issue can be labelled "
"*Enhancement* and *Usability* at the same time if it's an issue to improve "
"usability. Or *Feature proposal* and *Discussion* if it's a non-consensual "
"feature request, or one that is not precise enough to be worked on. At least "
"one of the categories *Bug*, *Enhancement* or *Discussion* is used to "
"describe an issue or pull request."
msgstr ""

#: ../../docs/contributing/workflow/bug_triage_guidelines.rst:106
msgid "**Topics:**"
msgstr ""

#: ../../docs/contributing/workflow/bug_triage_guidelines.rst:108
msgid ""
"*2D*: relates to 2D-specific issues. Should be coupled with one of the "
"labels below, and should not be coupled with *3D*."
msgstr ""

#: ../../docs/contributing/workflow/bug_triage_guidelines.rst:109
msgid ""
"*3D*: relates to 3D-specific issues. Should be coupled with one of the "
"labels below, and should not be coupled with *2D*."
msgstr ""

#: ../../docs/contributing/workflow/bug_triage_guidelines.rst:110
msgid "*Animation*: relates to the Animation system, editors and importers."
msgstr ""

#: ../../docs/contributing/workflow/bug_triage_guidelines.rst:111
msgid "*Assetlib*: relates to issues with the asset library."
msgstr ""

#: ../../docs/contributing/workflow/bug_triage_guidelines.rst:112
msgid "*Audio*: relates to the audio features (low and high level)."
msgstr ""

#: ../../docs/contributing/workflow/bug_triage_guidelines.rst:113
msgid ""
"*Buildsystem*: relates to building issues, either linked to the SCons "
"buildsystem or to compiler peculiarities."
msgstr ""

#: ../../docs/contributing/workflow/bug_triage_guidelines.rst:115
msgid "*Codestyle*: relates to the programming style used within the codebase."
msgstr ""

#: ../../docs/contributing/workflow/bug_triage_guidelines.rst:116
msgid ""
"*Core*: anything related to the core engine. Specific topics are split off "
"separately as they crop up."
msgstr ""

#: ../../docs/contributing/workflow/bug_triage_guidelines.rst:117
msgid "*Dotnet*: relates to the C# / Dotnet bindings."
msgstr ""

#: ../../docs/contributing/workflow/bug_triage_guidelines.rst:118
msgid "*Editor*: relates to issues in the editor (mainly UI)."
msgstr ""

#: ../../docs/contributing/workflow/bug_triage_guidelines.rst:119
msgid "*Export*: relates to the export system and templates."
msgstr ""

#: ../../docs/contributing/workflow/bug_triage_guidelines.rst:120
msgid "*GDExtension*: relates to the GDExtension system for native extensions."
msgstr ""

#: ../../docs/contributing/workflow/bug_triage_guidelines.rst:121
msgid "*GDScript*: relates to GDScript."
msgstr ""

#: ../../docs/contributing/workflow/bug_triage_guidelines.rst:122
msgid ""
"*GUI*: relates to GUI (Control) nodes or to Nodes that compose user "
"interfaces."
msgstr ""

#: ../../docs/contributing/workflow/bug_triage_guidelines.rst:123
msgid "*Import*: relates to the resource import system."
msgstr ""

#: ../../docs/contributing/workflow/bug_triage_guidelines.rst:124
msgid "*Input*: relates to the input system."
msgstr ""

#: ../../docs/contributing/workflow/bug_triage_guidelines.rst:125
msgid "*Multiplayer*: relates to multiplayer (high-level networking) systems."
msgstr ""

#: ../../docs/contributing/workflow/bug_triage_guidelines.rst:126
msgid ""
"*Navigation*: relates to the navigation system (including A* and navmeshes)."
msgstr ""

#: ../../docs/contributing/workflow/bug_triage_guidelines.rst:127
msgid "*Network*: relates to (lot-level) networking."
msgstr ""

#: ../../docs/contributing/workflow/bug_triage_guidelines.rst:128
#, fuzzy
msgid "*Particles*: particles, particle systems and their editors."
msgstr "Kreiranje Sadržaja"

#: ../../docs/contributing/workflow/bug_triage_guidelines.rst:129
msgid "*Physics*: relates to the physics engine (2D/3D)."
msgstr ""

#: ../../docs/contributing/workflow/bug_triage_guidelines.rst:130
msgid "*Plugin*: relates to problems encountered while writing plugins."
msgstr ""

#: ../../docs/contributing/workflow/bug_triage_guidelines.rst:131
msgid "*Porting*: relates to some specific platforms or exporting projects."
msgstr ""

#: ../../docs/contributing/workflow/bug_triage_guidelines.rst:132
msgid "*Rendering*: relates to the 2D and 3D rendering engines."
msgstr ""

#: ../../docs/contributing/workflow/bug_triage_guidelines.rst:133
msgid "*Shaders*: relates to the Godot shader language or visual shaders."
msgstr ""

#: ../../docs/contributing/workflow/bug_triage_guidelines.rst:134
msgid "*Tests*: relates to unit tests."
msgstr ""

#: ../../docs/contributing/workflow/bug_triage_guidelines.rst:135
msgid "*Thirdparty*: relates to third-party libraries used in Godot."
msgstr ""

#: ../../docs/contributing/workflow/bug_triage_guidelines.rst:136
msgid "*XR*: relates to Augmented Reality or Virtual Reality."
msgstr ""

#: ../../docs/contributing/workflow/bug_triage_guidelines.rst:138
msgid ""
"Issues would typically correspond to only one topic, though it's not "
"unthinkable to see issues that fit two bills. The general idea is that there "
"will be specialized contributors teams behind all topics, so they can focus "
"on the issues labelled with their team's topic."
msgstr ""

#: ../../docs/contributing/workflow/bug_triage_guidelines.rst:143
msgid "**Platforms:**"
msgstr ""

#: ../../docs/contributing/workflow/bug_triage_guidelines.rst:145
msgid "*Android*, *iOS*, *Linux*, *macOS*, *Web*, *Windows*"
msgstr ""

#: ../../docs/contributing/workflow/bug_triage_guidelines.rst:147
msgid ""
"By default, it is assumed that a given issue applies to all platforms. If "
"one of the platform labels is used, it is then exclusive and the previous "
"assumption doesn't stand anymore (so if it's a bug on e.g. Android and Linux "
"exclusively, select those two platforms)."
msgstr ""

#: ../../docs/contributing/workflow/bug_triage_guidelines.rst:153
msgid "Documentation labels"
msgstr ""

#: ../../docs/contributing/workflow/bug_triage_guidelines.rst:155
#, fuzzy
msgid ""
"In the `documentation repository <https://github.com/godotengine/godot-"
"docs>`__, we use the following labels:"
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati raznorazne `Godot demo projects "
"<https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/contributing/workflow/bug_triage_guidelines.rst:160
msgid ""
"*Bug*: Incorrect information in an existing page. Not to be used for "
"*missing* information."
msgstr ""

#: ../../docs/contributing/workflow/bug_triage_guidelines.rst:164
msgid "*Dependencies*: describes pull requests that update a dependency file."
msgstr ""

#: ../../docs/contributing/workflow/bug_triage_guidelines.rst:168
msgid "*Enhancement*: new information to be added in an existing page."
msgstr ""

#: ../../docs/contributing/workflow/bug_triage_guidelines.rst:174
msgid "*Python*: Pull requests that update Python code."
msgstr ""

#: ../../docs/contributing/workflow/bug_triage_guidelines.rst:182
msgid "**Area:**"
msgstr ""

#: ../../docs/contributing/workflow/bug_triage_guidelines.rst:184
msgid ""
"*About*: Issues and PRs related to the About section of the documentation "
"and other general articles."
msgstr ""

#: ../../docs/contributing/workflow/bug_triage_guidelines.rst:185
msgid ""
"*Class reference*: the issue is about the class reference, not a "
"documentation page."
msgstr ""

#: ../../docs/contributing/workflow/bug_triage_guidelines.rst:186
msgid ""
"*Community*: Issues and PRs related to the Community section of the "
"documentation."
msgstr ""

#: ../../docs/contributing/workflow/bug_triage_guidelines.rst:187
msgid ""
"*Contributing*: Issues and PRs related to the Contributing/Development "
"section of the documentation."
msgstr ""

#: ../../docs/contributing/workflow/bug_triage_guidelines.rst:188
msgid ""
"*Getting started*: Issues and PRs related to the Getting Started section of "
"the documentation."
msgstr ""

#: ../../docs/contributing/workflow/bug_triage_guidelines.rst:189
msgid ""
"*Manual*: Issues and PRs related to the Manual/Tutorials section of the "
"documentation."
msgstr ""

#: ../../docs/contributing/workflow/bug_triage_guidelines.rst:191
msgid "**Content:**"
msgstr ""

#: ../../docs/contributing/workflow/bug_triage_guidelines.rst:193
msgid ""
"*Images*: Issues and PRs involving outdated or incorrect images in articles."
msgstr ""

#: ../../docs/contributing/workflow/bug_triage_guidelines.rst:194
msgid ""
"*New page*: Issues and PRs related to creation of new documentation pages "
"for new or undocumented features."
msgstr ""

#: ../../docs/contributing/workflow/bug_triage_guidelines.rst:195
msgid "*Organization*: Issues and PRs related to reorganizing the content."
msgstr ""

#: ../../docs/contributing/workflow/bug_triage_guidelines.rst:196
msgid ""
"*Proofreading*: Issues and PRs related to proofreading the documentation."
msgstr ""

#: ../../docs/contributing/workflow/bug_triage_guidelines.rst:197
msgid ""
"*Redirect*: Issues and PRs involving moving content and adding a redirect "
"rule on the backend."
msgstr ""

#: ../../docs/contributing/workflow/bug_triage_guidelines.rst:198
msgid ""
"*Website*: Issues related to adding website features and fixing bugs, "
"whether on the front or back-end,"
msgstr ""

#: ../../docs/contributing/workflow/bug_triage_guidelines.rst:200
msgid "**Topic:**"
msgstr ""

#: ../../docs/contributing/workflow/bug_triage_guidelines.rst:202
msgid ""
"The available topics describe the same content as the topics in the main "
"repository."
msgstr ""

#: ../../docs/contributing/workflow/bug_triage_guidelines.rst:206
msgid "Milestones"
msgstr ""

#: ../../docs/contributing/workflow/bug_triage_guidelines.rst:208
msgid ""
"`Milestones <https://github.com/godotengine/godot/milestones>`_ correspond "
"to planned future versions of Godot for which there is an existing roadmap. "
"Issues that fit in the said roadmap should be filed under the corresponding "
"milestone; if they don't correspond to any current roadmap, they should be "
"left without milestone. As a rule of thumb, an issue corresponds to a given "
"milestone if it concerns a feature that is new in the milestone, or a "
"critical bug that can't be accepted in any future stable release, or "
"anything that Juan wants to work on right now. :)"
msgstr ""

#: ../../docs/contributing/workflow/bug_triage_guidelines.rst:217
msgid ""
"Contributors are free to pick issues regardless of their assigned milestone; "
"if a fix is proposed for a bug that was not deemed urgent and thus without "
"milestone, it would likely still be very welcome."
msgstr ""

#: ../../docs/contributing/workflow/pr_workflow.rst:4
msgid "Pull request workflow"
msgstr ""

#: ../../docs/contributing/workflow/pr_workflow.rst:8
msgid ""
"The so-called \"PR workflow\" used by Godot is common to many projects using "
"Git, and should be familiar to veteran free software contributors. The idea "
"is that only a small number (if any) commit directly to the *master* branch. "
"Instead, contributors *fork* the project (i.e. create a copy of it, which "
"they can modify as they wish), and then use the GitHub interface to request "
"a *pull* from one of their fork's branches to one branch of the original "
"(often named *upstream*) repository."
msgstr ""

#: ../../docs/contributing/workflow/pr_workflow.rst:16
msgid ""
"The resulting *pull request* (PR) can then be reviewed by other "
"contributors, which might approve it, reject it, or most often request that "
"modifications be done. Once approved, the PR can then be merged by one of "
"the core developers, and its commit(s) will become part of the target branch "
"(usually the *master* branch)."
msgstr ""

#: ../../docs/contributing/workflow/pr_workflow.rst:22
msgid ""
"We will go together through an example to show the typical workflow and "
"associated Git commands. But first, let's have a quick look at the "
"organization of Godot's Git repository."
msgstr ""

#: ../../docs/contributing/workflow/pr_workflow.rst:27
msgid "Git source repository"
msgstr ""

#: ../../docs/contributing/workflow/pr_workflow.rst:29
msgid ""
"The `repository on GitHub <https://github.com/godotengine/godot>`_ is a `Git "
"<https://git-scm.com>`_ code repository together with an embedded issue "
"tracker and PR system."
msgstr ""

#: ../../docs/contributing/workflow/pr_workflow.rst:33
#, fuzzy
msgid ""
"If you are contributing to the documentation, its repository can be found "
"`here <https://github.com/godotengine/godot-docs>`_."
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati raznorazne `Godot demo projects "
"<https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/contributing/workflow/pr_workflow.rst:36
msgid ""
"The Git version control system is the tool used to keep track of successive "
"edits to the source code - to contribute efficiently to Godot, learning the "
"basics of the Git command line is *highly* recommended. There exist some "
"graphical interfaces for Git, but they usually encourage users to take bad "
"habits regarding the Git and PR workflow, and we therefore recommend not to "
"use them. In particular, we advise not to use GitHub's online editor for "
"code contributions (although it's tolerated for small fixes or documentation "
"changes) as it enforces one commit per file and per modification, which "
"quickly leads to PRs with an unreadable Git history (especially after peer "
"review)."
msgstr ""

#: ../../docs/contributing/workflow/pr_workflow.rst:46
msgid ""
"The first sections of Git's \"Book\" are a good introduction to the tool's "
"philosophy and the various commands you need to master in your daily "
"workflow. You can read them online on the `Git SCM <https://git-scm.com/book/"
"en/v2>`_ website. You can also try out `GitHub's interactive guide <https://"
"try.github.io/>`__."
msgstr ""

#: ../../docs/contributing/workflow/pr_workflow.rst:52
msgid "The branches on the Git repository are organized as follows:"
msgstr ""

#: ../../docs/contributing/workflow/pr_workflow.rst:54
msgid ""
"The ``master`` branch is where the development of the next major version "
"occurs. As a development branch, it can be unstable and is not meant for use "
"in production. This is where PRs should be done in priority."
msgstr ""

#: ../../docs/contributing/workflow/pr_workflow.rst:58
msgid ""
"The stable branches are named after their version, e.g. ``3.1`` and ``2.1``. "
"They are used to backport bugfixes and enhancements from the ``master`` "
"branch to the currently maintained stable release (e.g. 3.1.2 or 2.1.6). As "
"a rule of thumb, the last stable branch is maintained until the next minor "
"version (e.g. the ``3.0`` branch was maintained until the release of Godot "
"3.1). If you want to make PRs against a maintained stable branch, please "
"check first if your changes are also relevant for the ``master`` branch, and "
"if so make the PR for the ``master`` branch in priority. Release managers "
"can then cherry-pick the fix to a stable branch if relevant."
msgstr ""

#: ../../docs/contributing/workflow/pr_workflow.rst:68
msgid ""
"There might occasionally be feature branches, usually meant to be merged "
"into the ``master`` branch at some time."
msgstr ""

#: ../../docs/contributing/workflow/pr_workflow.rst:72
msgid "Forking and cloning"
msgstr ""

#: ../../docs/contributing/workflow/pr_workflow.rst:74
msgid ""
"The first step is to *fork* the `godotengine/godot <https://github.com/"
"godotengine/godot>`_ repository on GitHub. To do so, you will need to have a "
"GitHub account and to be logged in. In the top right corner of the "
"repository's GitHub page, you should see the \"Fork\" button as shown below:"
msgstr ""

#: ../../docs/contributing/workflow/pr_workflow.rst:81
msgid ""
"Click it, and after a while you should be redirected to your own fork of the "
"Godot repo, with your GitHub username as namespace:"
msgstr ""

#: ../../docs/contributing/workflow/pr_workflow.rst:86
msgid ""
"You can then *clone* your fork, i.e. create a local copy of the online "
"repository (in Git speak, the *origin remote*). If you haven't already, "
"download Git from `its website <https://git-scm.com>`_ if you're using "
"Windows or macOS, or install it through your package manager if you're using "
"Linux."
msgstr ""

#: ../../docs/contributing/workflow/pr_workflow.rst:91
msgid ""
"If you are on Windows, open Git Bash to type commands. macOS and Linux users "
"can use their respective terminals."
msgstr ""

#: ../../docs/contributing/workflow/pr_workflow.rst:94
msgid "To clone your fork from GitHub, use the following command:"
msgstr ""

#: ../../docs/contributing/workflow/pr_workflow.rst:100
msgid ""
"In our examples, the \"$\" character denotes the command line prompt on "
"typical UNIX shells. It is not part of the command and should not be typed."
msgstr ""

#: ../../docs/contributing/workflow/pr_workflow.rst:104
msgid ""
"After a little while, you should have a ``godot`` directory in your current "
"working directory. Move into it using the ``cd`` command:"
msgstr ""

#: ../../docs/contributing/workflow/pr_workflow.rst:111
msgid ""
"We will start by setting up a reference to the original repository that we "
"forked:"
msgstr ""

#: ../../docs/contributing/workflow/pr_workflow.rst:118
msgid ""
"This will create a reference named ``upstream`` pointing to the original "
"``godotengine/godot`` repository. This will be useful when you want to pull "
"new commits from its ``master`` branch to update your fork. You have another "
"remote reference named ``origin``, which points to your fork (``USERNAME/"
"godot``)."
msgstr ""

#: ../../docs/contributing/workflow/pr_workflow.rst:123
msgid ""
"You only need to do the above steps once, as long as you keep that local "
"``godot`` folder (which you can move around if you want, the relevant "
"metadata is hidden in its ``.git`` subfolder)."
msgstr ""

#: ../../docs/contributing/workflow/pr_workflow.rst:127
msgid ""
"*Branch it, pull it, code it, stage it, commit, push it, rebase it... "
"technologic.*"
msgstr ""

#: ../../docs/contributing/workflow/pr_workflow.rst:130
msgid ""
"This bad take on Daft Punk's *Technologic* shows the general conception Git "
"beginners have of its workflow: lots of strange commands to learn by copy "
"and paste, hoping they will work as expected. And that's actually not a bad "
"way to learn, as long as you're curious and don't hesitate to question your "
"search engine when lost, so we will give you the basic commands to know when "
"working in Git."
msgstr ""

#: ../../docs/contributing/workflow/pr_workflow.rst:138
msgid ""
"In the following, we will assume as an example that you want to implement a "
"feature in Godot's Project Manager, which is coded in the ``editor/"
"project_manager.cpp`` file."
msgstr ""

#: ../../docs/contributing/workflow/pr_workflow.rst:143
msgid "Branching"
msgstr ""

#: ../../docs/contributing/workflow/pr_workflow.rst:145
msgid ""
"By default, the ``git clone`` should have put you on the ``master`` branch "
"of your fork (``origin``). To start your own feature development, we will "
"create a feature branch:"
msgstr ""

#: ../../docs/contributing/workflow/pr_workflow.rst:157
msgid "This command is equivalent:"
msgstr ""

#: ../../docs/contributing/workflow/pr_workflow.rst:164
msgid "If you want to go back to the ``master`` branch, you'd use:"
msgstr ""

#: ../../docs/contributing/workflow/pr_workflow.rst:170
msgid ""
"You can see which branch you are currently on with the ``git branch`` "
"command:"
msgstr ""

#: ../../docs/contributing/workflow/pr_workflow.rst:180
msgid ""
"Be sure to always go back to the ``master`` branch before creating a new "
"branch, as your current branch will be used as the base for the new one. "
"Alternatively, you can specify a custom base branch after the new branch's "
"name:"
msgstr ""

#: ../../docs/contributing/workflow/pr_workflow.rst:189
msgid "Updating your branch"
msgstr ""

#: ../../docs/contributing/workflow/pr_workflow.rst:191
msgid ""
"This would not be needed the first time (just after you forked the upstream "
"repository). However, the next time you want to work on something, you will "
"notice that your fork's ``master`` is several commits behind the upstream "
"``master`` branch: pull requests from other contributors would have been "
"merged in the meantime."
msgstr ""

#: ../../docs/contributing/workflow/pr_workflow.rst:197
msgid ""
"To ensure there won't be conflicts between the feature you develop and the "
"current upstream ``master`` branch, you will have to update your branch by "
"*pulling* the upstream branch."
msgstr ""

#: ../../docs/contributing/workflow/pr_workflow.rst:205
msgid ""
"The ``--rebase`` argument will ensure that any local changes that you "
"committed will be re-applied *on top* of the pulled branch, which is usually "
"what we want in our PR workflow. This way, when you open a pull request, "
"your own commits will be the only difference with the upstream ``master`` "
"branch."
msgstr ""

#: ../../docs/contributing/workflow/pr_workflow.rst:210
msgid ""
"While rebasing, conflicts may arise if your commits modified code that has "
"been changed in the upstream branch in the meantime. If that happens, Git "
"will stop at the conflicting commit and will ask you to resolve the "
"conflicts. You can do so with any text editor, then stage the changes (more "
"on that later), and proceed with ``git rebase --continue``. Repeat the "
"operation if later commits have conflicts too, until the rebase operation "
"completes."
msgstr ""

#: ../../docs/contributing/workflow/pr_workflow.rst:217
msgid ""
"If you're unsure about what is going on during a rebase and you panic (no "
"worry, we all do the first few times), you can abort the rebase with ``git "
"rebase --abort``. You will then be back to the original state of your branch "
"before calling ``git pull --rebase``."
msgstr ""

#: ../../docs/contributing/workflow/pr_workflow.rst:222
msgid ""
"If you omit the ``--rebase`` argument, you will instead create a merge "
"commit which tells Git what to make of the two distinct branches. If any "
"conflicts arise, they would be resolved all at once via this merge commit."
msgstr ""

#: ../../docs/contributing/workflow/pr_workflow.rst:226
msgid ""
"While this is a valid workflow and the default behavior of ``git pull``, "
"merge commits within PRs are frowned upon in our PR workflow. We only use "
"them when merging PRs into the upstream branch."
msgstr ""

#: ../../docs/contributing/workflow/pr_workflow.rst:230
msgid ""
"The philosophy is that a PR should represent the final stage of the changes "
"made to the codebase, and we are not interested in mistakes and fixes that "
"would have been done in intermediate stages before merging. Git gives us "
"great tools to \"rewrite the history\" and make it as if we got things right "
"the first time, and we're happy to use it to ensure that changes are easy to "
"review and understand long after they have been merged."
msgstr ""

#: ../../docs/contributing/workflow/pr_workflow.rst:237
msgid ""
"If you have already created a merge commit without using ``rebase``, or have "
"made any other changes that have resulted in undesired history, the best "
"option is to use an *interactive rebase* on the upstream branch. See the :"
"ref:`dedicated section <doc_pr_workflow_rebase>` for instructions."
msgstr ""

#: ../../docs/contributing/workflow/pr_workflow.rst:242
msgid ""
"If at any time you want to *reset* a local branch to a given commit or "
"branch, you can do so with ``git reset --hard <commit ID>`` or ``git reset --"
"hard <remote>/<branch>`` (e.g. ``git reset --hard upstream/master``)."
msgstr ""

#: ../../docs/contributing/workflow/pr_workflow.rst:246
msgid ""
"Be warned that this will remove any changes that you might have committed in "
"this branch. If you ever lose commits by mistake, use the ``git reflog`` "
"command to find the commit ID of the previous state that you would like to "
"restore, and use it as argument of ``git reset --hard`` to go back to that "
"state."
msgstr ""

#: ../../docs/contributing/workflow/pr_workflow.rst:252
msgid "Making changes"
msgstr ""

#: ../../docs/contributing/workflow/pr_workflow.rst:254
msgid ""
"You would then do your changes to our example's ``editor/project_manager."
"cpp`` file with your usual development environment (text editor, IDE, etc.)."
msgstr ""

#: ../../docs/contributing/workflow/pr_workflow.rst:258
msgid ""
"By default, those changes are *unstaged*. The staging area is a layer "
"between your working directory (where you make your modifications) and the "
"local Git repository (the commits and all the metadata in the ``.git`` "
"folder). To bring changes from the working directory to the Git repository, "
"you need to *stage* them with the ``git add`` command, and then to commit "
"them with the ``git commit`` command."
msgstr ""

#: ../../docs/contributing/workflow/pr_workflow.rst:265
msgid ""
"There are various commands you should know to review your current work, "
"before staging it, while it is staged, and after it has been committed."
msgstr ""

#: ../../docs/contributing/workflow/pr_workflow.rst:268
msgid ""
"``git diff`` will show you the current unstaged changes, i.e. the "
"differences between your working directory and the staging area."
msgstr ""

#: ../../docs/contributing/workflow/pr_workflow.rst:270
msgid ""
"``git checkout -- <files>`` will undo the unstaged changes to the given "
"files."
msgstr ""

#: ../../docs/contributing/workflow/pr_workflow.rst:272
msgid "``git add <files>`` will *stage* the changes on the listed files."
msgstr ""

#: ../../docs/contributing/workflow/pr_workflow.rst:273
msgid ""
"``git diff --staged`` will show the current staged changes, i.e. the "
"differences between the staging area and the last commit."
msgstr ""

#: ../../docs/contributing/workflow/pr_workflow.rst:275
msgid "``git reset HEAD <files>`` will *unstage* changes to the listed files."
msgstr ""

#: ../../docs/contributing/workflow/pr_workflow.rst:276
msgid ""
"``git status`` will show you what are the currently staged and unstaged "
"modifications."
msgstr ""

#: ../../docs/contributing/workflow/pr_workflow.rst:278
msgid ""
"``git commit`` will commit the staged files. It will open a text editor (you "
"can define the one you want to use with the ``GIT_EDITOR`` environment "
"variable or the ``core.editor`` setting in your Git configuration) to let "
"you write a commit log. You can use ``git commit -m \"Cool commit log\"`` to "
"write the log directly."
msgstr ""

#: ../../docs/contributing/workflow/pr_workflow.rst:283
msgid ""
"``git commit --amend`` lets you amend the last commit with your currently "
"staged changes (added with ``git add``). This is the best option if you want "
"to fix a mistake in the last commit (bug, typo, style issue, etc.)."
msgstr ""

#: ../../docs/contributing/workflow/pr_workflow.rst:286
msgid ""
"``git log`` will show you the last commits of your current branch. If you "
"did local commits, they should be shown at the top."
msgstr ""

#: ../../docs/contributing/workflow/pr_workflow.rst:288
msgid ""
"``git show`` will show you the changes of the last commit. You can also "
"specify a commit hash to see the changes for that commit."
msgstr ""

#: ../../docs/contributing/workflow/pr_workflow.rst:291
msgid ""
"That's a lot to memorize! Don't worry, just check this cheat sheet when you "
"need to make changes, and learn by doing."
msgstr ""

#: ../../docs/contributing/workflow/pr_workflow.rst:294
msgid "Here's how the shell history could look like on our example:"
msgstr ""

#: ../../docs/contributing/workflow/pr_workflow.rst:326
msgid ""
"With this, we should have two new commits in our ``better-project-manager`` "
"branch which were not in the ``master`` branch. They are still only local "
"though, the remote fork does not know about them, nor does the upstream repo."
msgstr ""

#: ../../docs/contributing/workflow/pr_workflow.rst:331
msgid "Pushing changes to a remote"
msgstr ""

#: ../../docs/contributing/workflow/pr_workflow.rst:333
msgid ""
"That's where ``git push`` will come into play. In Git, a commit is always "
"done in the local repository (unlike Subversion where a commit will modify "
"the remote repository directly). You need to *push* the new commits to a "
"remote branch to share them with the world. The syntax for this is:"
msgstr ""

#: ../../docs/contributing/workflow/pr_workflow.rst:342
msgid ""
"The part about the remote branch can be omitted if you want it to have the "
"same name as the local branch, which is our case in this example, so we will "
"do:"
msgstr ""

#: ../../docs/contributing/workflow/pr_workflow.rst:350
msgid ""
"Git will ask you for your username and password. For your password, enter "
"your GitHub Personal Access Token (PAT). If you do not have a GitHub "
"Personal Access Token, or do not have one with the correct permissions for "
"your newly forked repository, you will need to create one. Follow this link "
"to create your Personal Access Token: `Creating a personal access token "
"<https://docs.github.com/en/authentication/keeping-your-account-and-data-"
"secure/creating-a-personal-access-token>`_."
msgstr ""

#: ../../docs/contributing/workflow/pr_workflow.rst:357
msgid ""
"After you have successfully verified your account using your PAT, the "
"changes will be sent to your remote repository. If you check the fork's page "
"on GitHub, you should see a new branch with your added commits."
msgstr ""

#: ../../docs/contributing/workflow/pr_workflow.rst:362
msgid "Issuing a pull request"
msgstr ""

#: ../../docs/contributing/workflow/pr_workflow.rst:364
msgid ""
"When you load your fork's branch on GitHub, you should see a line saying "
"*\"This branch is 2 commits ahead of godotengine:master.\"* (and potentially "
"some commits behind, if your ``master`` branch was out of sync with the "
"upstream ``master`` branch)."
msgstr ""

#: ../../docs/contributing/workflow/pr_workflow.rst:371
msgid ""
"On that line, there is a \"Pull request\" link. Clicking it will open a form "
"that will let you issue a pull request on the ``godotengine/godot`` upstream "
"repository. It should show you your two commits, and state \"Able to "
"merge\". If not (e.g. it has way more commits, or says there are merge "
"conflicts), don't create the PR yet, something went wrong. Go to our `Godot "
"Contributors Chat <https://chat.godotengine.org/>`_ and ask for support :)"
msgstr ""

#: ../../docs/contributing/workflow/pr_workflow.rst:378
msgid ""
"Use an explicit title for the PR and put the necessary details in the "
"comment area. You can drag and drop screenshots, GIFs or zipped projects if "
"relevant, to showcase what your work implements. Click \"Create a pull "
"request\", and tadaa!"
msgstr ""

#: ../../docs/contributing/workflow/pr_workflow.rst:384
msgid "Modifying a pull request"
msgstr ""

#: ../../docs/contributing/workflow/pr_workflow.rst:386
msgid ""
"While it is reviewed by other contributors, you will often need to make "
"changes to your yet-unmerged PR, either because contributors requested them, "
"or because you found issues yourself while testing."
msgstr ""

#: ../../docs/contributing/workflow/pr_workflow.rst:390
msgid ""
"The good news is that you can modify a pull request simply by acting on the "
"branch you made the pull request from. You can e.g. make a new commit on "
"that branch, push it to your fork, and the PR will be updated automatically:"
msgstr ""

#: ../../docs/contributing/workflow/pr_workflow.rst:405
msgid ""
"However, be aware that in our PR workflow, we favor commits that bring the "
"codebase from one functional state to another functional state, without "
"having intermediate commits fixing up bugs in your own code or style issues. "
"Most of the time, we will prefer a single commit in a given PR (unless "
"there's a good reason to keep the changes separate). Instead of authoring a "
"new commit, consider using ``git commit --amend`` to amend the previous "
"commit with your fixes. The above example would then become:"
msgstr ""

#: ../../docs/contributing/workflow/pr_workflow.rst:435
msgid "The interactive rebase"
msgstr ""

#: ../../docs/contributing/workflow/pr_workflow.rst:437
msgid ""
"If you didn't follow the above steps closely to *amend* changes into a "
"commit instead of creating fixup commits, or if you authored your changes "
"without being aware of our workflow and Git usage tips, reviewers might "
"request you to *rebase* your branch to *squash* some or all of the commits "
"into one."
msgstr ""

#: ../../docs/contributing/workflow/pr_workflow.rst:442
msgid ""
"Indeed, if some commits have been made following reviews to fix bugs, typos, "
"etc. in the original commit, they are not relevant to a future changelog "
"reader who would want to know what happened in the Godot codebase, or when "
"and how a given file was last modified."
msgstr ""

#: ../../docs/contributing/workflow/pr_workflow.rst:447
msgid ""
"To squash those extraneous commits into the main one, we will have to "
"*rewrite history*. Right, we have that power. You may read that it's a bad "
"practice, and it's true when it comes to branches of the upstream repo. But "
"in your fork, you can do whatever you want, and everything is allowed to get "
"neat PRs :)"
msgstr ""

#: ../../docs/contributing/workflow/pr_workflow.rst:452
msgid ""
"We will use the *interactive rebase* ``git rebase -i`` to do this. This "
"command takes a commit ID or a branch name as argument, and will let you "
"modify all commits between that commit/branch and the last one in your "
"working branch, the so-called ``HEAD``."
msgstr ""

#: ../../docs/contributing/workflow/pr_workflow.rst:457
msgid ""
"While you can give any commit ID to ``git rebase -i`` and review everything "
"in between, the most common and convenient workflow involves rebasing on the "
"upstream ``master`` branch, which you can do with:"
msgstr ""

#: ../../docs/contributing/workflow/pr_workflow.rst:465
msgid ""
"Referencing branches in Git is a bit tricky due to the distinction between "
"remote and local branches. Here, ``upstream/master`` (with a `/`) is a local "
"branch which has been pulled from the ``upstream`` remote's ``master`` "
"branch."
msgstr ""

#: ../../docs/contributing/workflow/pr_workflow.rst:470
msgid ""
"Interactive rebases can only be done on local branches, so the `/` is "
"important here. As the upstream remote changes frequently, your local "
"``upstream/master`` branch may become outdated, so you can update it with "
"``git fetch upstream master``. Contrarily to ``git pull --rebase upstream "
"master`` which would update your currently checked out branch, ``fetch`` "
"will only update the ``upstream/master`` reference (which is distinct from "
"your local ``master`` branch... yes it's confusing, but you'll become "
"familiar with this little by little)."
msgstr ""

#: ../../docs/contributing/workflow/pr_workflow.rst:480
msgid ""
"This will open a text editor (``vi`` by default, see `Git docs <https://git-"
"scm.com/book/en/v2/Customizing-Git-Git-Configuration#_core_editor>`_ to "
"configure your favorite one) with something which may look like this:"
msgstr ""

#: ../../docs/contributing/workflow/pr_workflow.rst:489
msgid ""
"The editor will also show instructions regarding how you can act on those "
"commits. In particular, it should tell you that \"pick\" means to use that "
"commit (do nothing), and that \"squash\" and \"fixup\" can be used to *meld* "
"the commit in its parent commit. The difference between \"squash\" and "
"\"fixup\" is that \"fixup\" will discard the commit log from the squashed "
"commit. In our example, we are not interested in keeping the log of the "
"\"Fix a typo\" commit, so we use:"
msgstr ""

#: ../../docs/contributing/workflow/pr_workflow.rst:502
msgid ""
"Upon saving and quitting the editor, the rebase will occur. The second "
"commit will be melded into the first one, and ``git log`` and ``git show`` "
"should now confirm that you have only one commit with the changes from both "
"previous commits."
msgstr ""

#: ../../docs/contributing/workflow/pr_workflow.rst:507
msgid ""
"But! You rewrote the history, and now your local and remote branches have "
"diverged. Indeed, commit 1b4aad7 in the above example will have changed, and "
"therefore got a new commit hash. If you try to push to your remote branch, "
"it will raise an error:"
msgstr ""

#: ../../docs/contributing/workflow/pr_workflow.rst:521
msgid ""
"This is reasonable behavior, Git will not let you push changes that would "
"override remote content. But that's actually what we want to do here, so we "
"will have to *force* it:"
msgstr ""

#: ../../docs/contributing/workflow/pr_workflow.rst:529
msgid ""
"And tadaa! Git will happily *replace* your remote branch with what you had "
"locally (so make sure that's what you wanted, using ``git log``). This will "
"also update the PR accordingly."
msgstr ""

#: ../../docs/contributing/workflow/pr_workflow.rst:534
msgid "Rebasing onto another branch"
msgstr ""

#: ../../docs/contributing/workflow/pr_workflow.rst:536
msgid ""
"If you have accidentally opened your PR on the wrong branch, or need to "
"target another branch for some reason, you might need to filter out a lot of "
"commits that differ between the old branch (for example ``4.2``) and the new "
"branch (for example ``master``). This can make rebasing difficult and "
"tedious. Fortunately ``git`` has a command just for this situation, ``git "
"rebase --onto``."
msgstr ""

#: ../../docs/contributing/workflow/pr_workflow.rst:541
msgid ""
"If your PR was created from the ``4.2`` branch and you want to update it to "
"instead start at ``master`` the following steps *should* fix this in one "
"step:"
msgstr ""

#: ../../docs/contributing/workflow/pr_workflow.rst:548
msgid ""
"This will take all the commits on your branch *after* the ``4.2`` branch, "
"and then splice them on top of ``master``, ignoring any commits from the "
"``4.2`` branch not on the ``master`` branch. You may still need to do some "
"fixing, but this command should save you a lot of tedious work removing "
"commits."
msgstr ""

#: ../../docs/contributing/workflow/pr_workflow.rst:552
msgid ""
"Just like above for the interactive rebase you need to force push your "
"branch to handle the different changes:"
msgstr ""

#: ../../docs/contributing/workflow/pr_workflow.rst:559
msgid "Deleting a Git branch"
msgstr ""

#: ../../docs/contributing/workflow/pr_workflow.rst:561
msgid ""
"After your pull request gets merged, there's one last thing you should do: "
"delete your Git branch for the PR. There won't be issues if you don't delete "
"your branch, but it's good practice to do so. You'll need to do this twice, "
"once for the local branch and another for the remote branch on GitHub."
msgstr ""

#: ../../docs/contributing/workflow/pr_workflow.rst:566
msgid "To delete our better Project Manager branch locally, use this command:"
msgstr ""

#: ../../docs/contributing/workflow/pr_workflow.rst:572
msgid ""
"Alternatively, if the branch hadn't been merged yet and we wanted to delete "
"it anyway, instead of ``-d`` you would use ``-D``."
msgstr ""

#: ../../docs/contributing/workflow/pr_workflow.rst:575
msgid "Next, to delete the remote branch on GitHub use this command:"
msgstr ""

#: ../../docs/contributing/workflow/pr_workflow.rst:581
msgid ""
"You can also delete the remote branch from the GitHub PR itself, a button "
"should appear once it has been merged or closed."
msgstr ""

#: ../../docs/contributing/workflow/pr_review_guidelines.rst:4
msgid "Pull request review process"
msgstr ""

#: ../../docs/contributing/workflow/pr_review_guidelines.rst:8
msgid ""
"This page is intended to provide insight into the pull request (PR) review "
"process that we aspire to. As such, it is primarily targeted at engine "
"maintainers who are responsible for reviewing and approving pull requests. "
"That being said, much of the content is useful for prospective contributors "
"wanting to know how to ensure that their PR is merged."
msgstr ""

#: ../../docs/contributing/workflow/pr_review_guidelines.rst:14
msgid ""
"From a high level, the ideal life cycle of a pull request looks like the "
"following:"
msgstr ""

#: ../../docs/contributing/workflow/pr_review_guidelines.rst:17
msgid ""
"A contributor opens a PR that fixes a specific problem (optimally closing a "
"GitHub `issue <https://github.com/godotengine/godot>`_ or implementing a "
"`proposal <https://github.com/godotengine/godot-proposals>`_)."
msgstr ""

#: ../../docs/contributing/workflow/pr_review_guidelines.rst:21
msgid ""
"Other contributors provide feedback on the PR (including reviewing and/or "
"approving the PR, as appropriate)."
msgstr ""

#: ../../docs/contributing/workflow/pr_review_guidelines.rst:24
msgid ""
"An engine maintainer reviews the code and provides feedback, requests "
"changes, or approves the pull request, as appropriate."
msgstr ""

#: ../../docs/contributing/workflow/pr_review_guidelines.rst:27
msgid ""
"Another maintainer reviews the code with a focus on code style/clarity and "
"approves it once satisfied."
msgstr ""

#: ../../docs/contributing/workflow/pr_review_guidelines.rst:30
msgid ""
"A team leader or a member of the `production team <https://godotengine.org/"
"teams#production>`_ merges the pull request if satisfied that it has been "
"sufficiently reviewed."
msgstr ""

#: ../../docs/contributing/workflow/pr_review_guidelines.rst:34
msgid ""
"This document will explain steps 2, 3, 4, and 5 in more detail. For a more "
"detailed explanation of the pull request workflow please see the :ref:`pull "
"request workflow document <doc_pr_workflow>`."
msgstr ""

#: ../../docs/contributing/workflow/pr_review_guidelines.rst:39
msgid ""
"In practice these steps may blend together. Oftentimes maintainers will "
"provide comments on code style and code quality at the same time and will "
"approve a pull request for both."
msgstr ""

#: ../../docs/contributing/workflow/pr_review_guidelines.rst:43
msgid ""
"Typically the first interaction on a pull request will be an engine "
"maintainer assigning tags to the pull request and flagging it for review by "
"someone familiar with that area of code."
msgstr ""

#: ../../docs/contributing/workflow/pr_review_guidelines.rst:47
msgid ""
"Engine maintainers are folks who are \"members\" of the Godot project "
"repository on GitHub and/or are listed on the `Teams page <https://"
"godotengine.org/teams>`_ on the Godot website. Maintainers are responsible "
"for a given area of the engine. Typically this means they are the people who "
"are given more trust to approve and recommend pull requests for merging."
msgstr ""

#: ../../docs/contributing/workflow/pr_review_guidelines.rst:53
msgid ""
"Even if you are not a maintainer, you can still help by reviewing code, "
"providing feedback on PRs and testing PRs locally on your machine to confirm "
"that they work as intended. Many of the currently active maintainers started "
"out doing this before they became maintainers."
msgstr ""

#: ../../docs/contributing/workflow/pr_review_guidelines.rst:59
msgid "Code review and testing"
msgstr ""

#: ../../docs/contributing/workflow/pr_review_guidelines.rst:61
msgid ""
"The following is a list of things that contributors and engine maintainers "
"can do to conduct a substantive code review of a pull request."
msgstr ""

#: ../../docs/contributing/workflow/pr_review_guidelines.rst:65
msgid ""
"If you want to conduct a code review, but can't do everything on this list, "
"say that in your review comment. For example, it is still very helpful to "
"provide comments on code, even if you can't build the pull request locally "
"to test the pull request (or vice versa). Feel free to review the code, just "
"remember to make a note at the end of your review that you have reviewed the "
"code only and have not tested the changes locally."
msgstr ""

#: ../../docs/contributing/workflow/pr_review_guidelines.rst:73
msgid "1. Confirm that the problem exists"
msgstr ""

#: ../../docs/contributing/workflow/pr_review_guidelines.rst:75
msgid ""
"PRs need to solve problems and problems need to be documented. Make sure "
"that the pull request links and closes (or at least addresses) a bug or a "
"proposal. If it doesn't, consider asking the contributor to update the "
"opening message of the PR to explain the problem that the PR aims to solve "
"in more detail."
msgstr ""

#: ../../docs/contributing/workflow/pr_review_guidelines.rst:81
msgid ""
"It should be clear _why_ a pull request is needed before it is merged. This "
"assists reviewers in determining whether a PR does what it says it does and "
"it helps contributors in the future understand why the code is the way it is."
msgstr ""

#: ../../docs/contributing/workflow/pr_review_guidelines.rst:86
msgid "2. Test the PR and look for regressions"
msgstr ""

#: ../../docs/contributing/workflow/pr_review_guidelines.rst:88
msgid ""
"While strict code review and CI help to ensure that all pull requests work "
"as intended, mistakes happen and sometimes contributors push code that "
"creates a problem in addition to solving a problem. Maintainers will avoid "
"merging code that contains a regression even if it solves the problem as "
"intended."
msgstr ""

#: ../../docs/contributing/workflow/pr_review_guidelines.rst:93
msgid ""
"When reviewing a pull request, ensure that the PR does what it says it does "
"(i.e. fixes the linked bug or implements the new feature) and nothing "
"outside of the PR target area is broken by the change. You can do this by "
"running the editor and trying out some common functions of the editor "
"(adding objects to a scene, running GDScript, opening and closing menus "
"etc.). Also, while reviewing the code, look for suspicious changes in other "
"parts of the engine. Sometimes during rebasing changes slip through that "
"contributors are not aware of."
msgstr ""

#: ../../docs/contributing/workflow/pr_review_guidelines.rst:102
msgid "3. Do a code review"
msgstr ""

#: ../../docs/contributing/workflow/pr_review_guidelines.rst:104
msgid ""
"Code reviews are usually done by people who are already experienced in a "
"given area. They may be able to provide ideas to make code faster, more "
"organized, or more idiomatic. But, even if you are not very experienced, you "
"may want to conduct a code review to provide feedback within the scope of "
"what you are comfortable reviewing. Doing so is valuable for the area "
"maintainer (as a second set of eyes on a problem is always helpful) and it "
"is also helpful for you as it will help you get more familiar with that area "
"of code and will expose you to how other people solve problems. In fact, "
"reviewing the code of experienced engine maintainers is a great way to get "
"to know the codebase."
msgstr ""

#: ../../docs/contributing/workflow/pr_review_guidelines.rst:114
msgid ""
"Here are some things to think about and look out for as you review the code:"
msgstr ""

#: ../../docs/contributing/workflow/pr_review_guidelines.rst:116
msgid ""
"**Code only touches the areas announced in the PR (and the commit message).**"
msgstr ""

#: ../../docs/contributing/workflow/pr_review_guidelines.rst:119
msgid ""
"It can be tempting to fix random things in the code, as you see them. "
"However, this can quickly make a pull request difficult to review and can "
"make it hard to dig through in the commit history. Small touch-ups next to "
"the related area are alright, but often bugs that you can find along the way "
"are better fixed in their own PRs."
msgstr ""

#: ../../docs/contributing/workflow/pr_review_guidelines.rst:125
msgid "**Code properly uses Godot's own APIs and patterns.**"
msgstr ""

#: ../../docs/contributing/workflow/pr_review_guidelines.rst:127
msgid ""
"Consistency is very important, and a solution that already exists in the "
"codebase is preferable to an ad-hoc solution."
msgstr ""

#: ../../docs/contributing/workflow/pr_review_guidelines.rst:130
msgid "**Are core areas affected by the change?**"
msgstr ""

#: ../../docs/contributing/workflow/pr_review_guidelines.rst:132
msgid ""
"Sometimes a PR that is supposed to solve a local problem can have a far-"
"reaching effect way outside of its scope. Usually it is best to keep code "
"changes local to where the problem arises. If you think that the solution "
"requires changes outside the scope of the problem, it is usually best to "
"seek the opinion of a team leader who may have another idea for how to solve "
"the problem."
msgstr ""

#: ../../docs/contributing/workflow/pr_review_guidelines.rst:140
msgid "4. Iterate with the contributor and improve the PR"
msgstr ""

#: ../../docs/contributing/workflow/pr_review_guidelines.rst:142
msgid ""
"Maintainers should provide feedback and suggestions for improvement if they "
"spot things in the code that they would like changed. Preferably, "
"suggestions should come in order of importance: first, address overall code "
"design and the approach to solving the problem, then make sure the code is "
"complying with the engine's best practices, and lastly, do the :ref:`code "
"style review <doc_code_style_review>`."
msgstr ""

#: ../../docs/contributing/workflow/pr_review_guidelines.rst:150
msgid "**Communicate barriers to merging early in the review process.**"
msgstr ""

#: ../../docs/contributing/workflow/pr_review_guidelines.rst:152
msgid ""
"If the PR has clear blockers or will likely not get merged for whatever "
"other reason, that fact should be communicated as early and clearly as "
"possible. We want to avoid stringing people along because it feels bad to "
"say \"sorry, no\"."
msgstr ""

#: ../../docs/contributing/workflow/pr_review_guidelines.rst:156
msgid ""
"As you review pull requests, keep the Godot `Code of Conduct <https://"
"godotengine.org/code-of-conduct>`_ in mind. Especially the following:"
msgstr ""

#: ../../docs/contributing/workflow/pr_review_guidelines.rst:159
msgid "Politeness is expected at all times. Be kind and courteous."
msgstr ""

#: ../../docs/contributing/workflow/pr_review_guidelines.rst:161
msgid "Always assume positive intent from others."
msgstr ""

#: ../../docs/contributing/workflow/pr_review_guidelines.rst:163
msgid "Feedback is always welcome but keep your criticism constructive."
msgstr ""

#: ../../docs/contributing/workflow/pr_review_guidelines.rst:165
msgid ""
"Here are some things to avoid as you iterate on a pull request with a "
"contributor:"
msgstr ""

#: ../../docs/contributing/workflow/pr_review_guidelines.rst:168
msgid "**Needless double reviews.**"
msgstr ""

#: ../../docs/contributing/workflow/pr_review_guidelines.rst:170
msgid ""
"In other words, review the full PR at once and avoid coming back endless "
"times to point out issues that you could have noted in the first review. Of "
"course, this can't always be avoided, but we should try to catch everything "
"at once."
msgstr ""

#: ../../docs/contributing/workflow/pr_review_guidelines.rst:174
msgid "**Being overly nitpicky.**"
msgstr ""

#: ../../docs/contributing/workflow/pr_review_guidelines.rst:176
msgid ""
"Code quality can be flexible depending on the area of the engine you are "
"working in. In general, our standard for code quality is much higher in core "
"areas and in performance-sensitive areas than it is in editor code for "
"example."
msgstr ""

#: ../../docs/contributing/workflow/pr_review_guidelines.rst:181
msgid "**Expanding the scope of a pull request.**"
msgstr ""

#: ../../docs/contributing/workflow/pr_review_guidelines.rst:183
msgid ""
"Providing context or related/similar issues or proposals that may be fixed "
"similarly can be helpful, but adding a \"may as well fix that thing over "
"there as well while at it\" or \"could we add to this as well?\" isn't "
"always fair to the contributor. Use your judgement when deciding whether "
"additional fixes are within scope, but try to keep the scope as close to the "
"original pull request as possible."
msgstr ""

#: ../../docs/contributing/workflow/pr_review_guidelines.rst:190
msgid ""
"And ultimately, don't feel pressured to deal with the PR all alone. Feel "
"free to ask for a helping hand on the `Godot Contributors Chat <https://chat."
"godotengine.org>`_, in the appropriate channel or in #general. Other teams "
"may already be tagged for review, so you can also wait or ask for their "
"assistance."
msgstr ""

#: ../../docs/contributing/workflow/pr_review_guidelines.rst:197
msgid "5. Approve the pull request"
msgstr ""

#: ../../docs/contributing/workflow/pr_review_guidelines.rst:199
msgid ""
"After reviewing the code, if you think that the code is ready to be merged "
"into the engine, then go ahead and \"approve\" it. Make sure to also comment "
"and specify the nature of your review (i.e. say whether you ran the code "
"locally, whether you reviewed for style as well as correctness, etc.). Even "
"if you are not an engine maintainer, approving a pull request signals to "
"others that the code is good and likely solves the problem the PR says it "
"does. Approving a pull request as a non-engine maintainer does not guarantee "
"that the code will be merged, other people will still review it, so don't be "
"shy."
msgstr ""

#: ../../docs/contributing/workflow/pr_review_guidelines.rst:211
#, fuzzy
msgid "Code style review"
msgstr "Kreiranje Sadržaja"

#: ../../docs/contributing/workflow/pr_review_guidelines.rst:213
msgid ""
"Generally speaking, we aim to conduct a code review before a style/clarity "
"review as contributors typically want to know if their general approach is "
"acceptable before putting in the effort to make nitpicky changes to style. "
"In other words, maintainers shouldn't ask contributors to change the style "
"of code that may need to be rewritten in subsequent reviews. Similarly, "
"maintainers should avoid asking for contributors to rebase PRs if the PR has "
"not been reviewed."
msgstr ""

#: ../../docs/contributing/workflow/pr_review_guidelines.rst:221
msgid ""
"That being said, not everyone feels confident enough to provide a review on "
"code correctness, in that case, providing comments on code style and clarity "
"ahead of a more substantive code review is totally appropriate and more than "
"welcome."
msgstr ""

#: ../../docs/contributing/workflow/pr_review_guidelines.rst:225
msgid ""
"In practice the code style review can be done as part of the substantive "
"code review. The important thing is that both the substantive code and the "
"code style need to be reviewed and considered before a pull request is "
"merged."
msgstr ""

#: ../../docs/contributing/workflow/pr_review_guidelines.rst:229
msgid ""
"When reviewing code style pay particular attention to ensuring that the pull "
"request follows the :ref:`doc_code_style_guidelines`. While ``clang-format`` "
"and various CI checks can catch a lot of inconsistencies, they are far from "
"perfect and are unable to detect some issues. For example, you should check "
"that:"
msgstr ""

#: ../../docs/contributing/workflow/pr_review_guidelines.rst:234
msgid "The style of header includes is respected."
msgstr ""

#: ../../docs/contributing/workflow/pr_review_guidelines.rst:235
msgid "Identifiers use ``snake_case`` and follow our naming conventions."
msgstr ""

#: ../../docs/contributing/workflow/pr_review_guidelines.rst:236
msgid ""
"Method parameters start with ``p_*`` or ``r_*`` (if they are used to return "
"a value)."
msgstr ""

#: ../../docs/contributing/workflow/pr_review_guidelines.rst:238
msgid "Braces are used appropriately, even for one-liner conditionals."
msgstr ""

#: ../../docs/contributing/workflow/pr_review_guidelines.rst:239
msgid ""
"Code is properly spaced (exactly one empty line between methods, no "
"unnecessary empty lines inside of method bodies)."
msgstr ""

#: ../../docs/contributing/workflow/pr_review_guidelines.rst:244
msgid ""
"This list is not complete and doesn't aim to be complete. Refer to the "
"linked style guide document for a complete set of rules. Keep in mind that "
"``clang-format`` may not catch things you hope it would, so pay attention "
"and try to build a sense of what exactly it can and cannot detect."
msgstr ""

#: ../../docs/contributing/workflow/pr_review_guidelines.rst:251
msgid "Merging pull requests"
msgstr ""

#: ../../docs/contributing/workflow/pr_review_guidelines.rst:253
msgid ""
"In general, pull requests should only be merged by members of the production "
"team or team leaders for pull requests in their area of the engine. For "
"example, the networking team leader could merge a networking pull request "
"that doesn't substantially change non-networking sections of code."
msgstr ""

#: ../../docs/contributing/workflow/pr_review_guidelines.rst:258
msgid ""
"In practice it is best to wait for a member of the production team to merge "
"the pull request as they keep a close eye on the entire codebase and will "
"likely have a better sense of what other recent/upcoming changes this pull "
"request may conflict with (or any other reason that it may make sense to "
"delay the pull request). Feel free to leave a comment saying that the PR "
"should be ready to merge."
msgstr ""

#: ../../docs/contributing/workflow/pr_review_guidelines.rst:265
msgid ""
"The following are the steps to take before merging a pull request. The "
"degree to which you adhere to these steps can be flexible for simple/"
"straightforward pull requests, but they should be carefully taken for "
"complex or risky pull requests."
msgstr ""

#: ../../docs/contributing/workflow/pr_review_guidelines.rst:269
msgid ""
"As a contributor you can help move a pull request forward by doing some of "
"these steps yourself."
msgstr ""

#: ../../docs/contributing/workflow/pr_review_guidelines.rst:273
msgid "1. Get feedback from the right people/teams"
msgstr ""

#: ../../docs/contributing/workflow/pr_review_guidelines.rst:275
msgid ""
"Production team members should ensure that the right people look at a pull "
"request before it is merged. In some cases this may require multiple people "
"to weigh in. In other cases, only one substantive approval is needed before "
"the code can be merged."
msgstr ""

#: ../../docs/contributing/workflow/pr_review_guidelines.rst:280
msgid ""
"In general, try not to merge things based on one review alone, especially if "
"it is your own. Get a second opinion from another maintainer, and make sure "
"all the teams that may be impacted have been reasonably represented by the "
"reviewers. For example, if a pull request adds to the documentation, it's "
"often useful to let the area maintainers check it for factual correctness "
"and let documentation maintainers check it for formatting, style, and "
"grammar."
msgstr ""

#: ../../docs/contributing/workflow/pr_review_guidelines.rst:287
msgid ""
"A good rule of thumb is that at least one subject matter expert should have "
"approved the pull request for correctness, and at least one other maintainer "
"should have approved the pull request for code style. Either of those people "
"could be the person merging the pull request."
msgstr ""

#: ../../docs/contributing/workflow/pr_review_guidelines.rst:292
msgid ""
"Make sure that the reviews and approvals were left by people competent in "
"that specific engine area. It is possible that even a long-standing member "
"of the Godot organization left a review without having the relevant "
"expertise."
msgstr ""

#: ../../docs/contributing/workflow/pr_review_guidelines.rst:298
msgid ""
"An easy way to find PRs that may be ready for merging is filtering by "
"approved PRs and sorting by recently updated. For example, in the main Godot "
"repository, you can use `this link <https://github.com/godotengine/godot/"
"pulls?q=is%3Apr+is%3Aopen+review%3Aapproved+sort%3Aupdated-desc>`_."
msgstr ""

#: ../../docs/contributing/workflow/pr_review_guidelines.rst:304
msgid "2. Get feedback from the community"
msgstr ""

#: ../../docs/contributing/workflow/pr_review_guidelines.rst:306
msgid ""
"If a pull request is having trouble attracting reviewers, you may need to "
"reach out more broadly to ask for help reviewing. Consider asking:"
msgstr ""

#: ../../docs/contributing/workflow/pr_review_guidelines.rst:309
msgid ""
"the person who reported the bug if the pull request fixes the bug for them,"
msgstr ""

#: ../../docs/contributing/workflow/pr_review_guidelines.rst:310
msgid ""
"contributors who have recently edited that file if they could take a look, or"
msgstr ""

#: ../../docs/contributing/workflow/pr_review_guidelines.rst:311
msgid ""
"a more experienced maintainer from another area if they could provide "
"feedback."
msgstr ""

#: ../../docs/contributing/workflow/pr_review_guidelines.rst:314
msgid "3. Git checklist"
msgstr ""

#: ../../docs/contributing/workflow/pr_review_guidelines.rst:316
msgid "**Make sure that the PR comes in one commit.**"
msgstr ""

#: ../../docs/contributing/workflow/pr_review_guidelines.rst:318
msgid ""
"When each commit is self-contained and could be used to build a clean and "
"working version of the engine, it may be okay to merge a pull request with "
"multiple commits, but in general, we require that all pull requests only "
"have one commit. This helps us keep the Git history clean."
msgstr ""

#: ../../docs/contributing/workflow/pr_review_guidelines.rst:323
msgid ""
"**Fixes made during the review process must be squashed into the main commit."
"**"
msgstr ""

#: ../../docs/contributing/workflow/pr_review_guidelines.rst:326
msgid ""
"For multi-commit PRs check that those fixes are amended in the relevant "
"commits, and are not just applied on top of everything."
msgstr ""

#: ../../docs/contributing/workflow/pr_review_guidelines.rst:329
msgid "**Make sure that the PR has no merge conflicts.**"
msgstr ""

#: ../../docs/contributing/workflow/pr_review_guidelines.rst:331
msgid ""
"Contributors may need to rebase their changes on top of the relevant branch "
"(e.g. ``master`` or ``3.x``) and manually fix merge conflicts. Even if there "
"are no merge conflicts, contributors may need to rebase especially old PRs "
"as the GitHub conflict checker may not catch all conflicts, or the CI may "
"have changed since it was originally run."
msgstr ""

#: ../../docs/contributing/workflow/pr_review_guidelines.rst:337
msgid "**Check for proper commit attribution.**"
msgstr ""

#: ../../docs/contributing/workflow/pr_review_guidelines.rst:339
msgid ""
"If a contributor uses an author signature that is not listed in their GitHub "
"account, GitHub won't link the merged pull request to their account. This "
"keeps them from getting proper credit in the GitHub history and makes them "
"appear like a new contributor on the GitHub UI even after several "
"contributions."
msgstr ""

#: ../../docs/contributing/workflow/pr_review_guidelines.rst:345
msgid ""
"Ultimately, it's up to the user if they want to fix it, but they can do so "
"by authoring the Git commit with the same email they use for their GitHub "
"account, or by adding the email they used for the Git commit to their GitHub "
"profile."
msgstr ""

#: ../../docs/contributing/workflow/pr_review_guidelines.rst:350
msgid "**Check for proper commit messages.**"
msgstr ""

#: ../../docs/contributing/workflow/pr_review_guidelines.rst:352
msgid ""
"While we don't have a very strict ruleset for commit messages, we still "
"require them to be short yet descriptive and use proper English. As a "
"maintainer you've probably written them enough times to know how to make "
"one, but for a general template think about *\"Fix <issue> in <part of "
"codebase>\"*. For a more detailed recommendation see the `contributing.md "
"<https://github.com/godotengine/godot/blob/master/CONTRIBUTING.md#format-"
"your-commit-messages-with-readability-in-mind>`_ page in the main Godot "
"repository."
msgstr ""

#: ../../docs/contributing/workflow/pr_review_guidelines.rst:361
msgid "4. GitHub checklist"
msgstr ""

#: ../../docs/contributing/workflow/pr_review_guidelines.rst:363
msgid "**Validate the target branch of the PR.**"
msgstr ""

#: ../../docs/contributing/workflow/pr_review_guidelines.rst:365
msgid ""
"Most Godot development happens around in the ``master`` branch. Therefore "
"most pull requests must be made against it. From there pull requests can "
"then be backported to other branches. Be wary of people making PRs on the "
"version they are using (e.g, ``3.3``) and guide them to make a change "
"against a higher-order branch (e.g. ``3.x``). If the change is not "
"applicable for the ``master`` branch, the initial PR can be made against the "
"current maintenance branch, such as ``3.x``. It's okay for people to make "
"multiple PRs for each target branch, especially if the changes cannot be "
"easily backported. Cherry-picking is also an option, if possible. Use the "
"appropriate labels if the PR can be cherrypicked (e.g. ``cherrypick:3.x``)."
msgstr ""

#: ../../docs/contributing/workflow/pr_review_guidelines.rst:378
msgid ""
"It is possible to change the target branch of the PR, that has already been "
"submitted, but be aware of the consequences. As it cannot be synchronized "
"with the push, the target branch change will inevitable tag the entire list "
"of maintainers for review. It may also render the CI incapable of running "
"properly. A push should help with that, but if nothing else, recommend "
"opening a new, fresh PR."
msgstr ""

#: ../../docs/contributing/workflow/pr_review_guidelines.rst:385
msgid "**Make sure that the appropriate milestone is assigned.**"
msgstr ""

#: ../../docs/contributing/workflow/pr_review_guidelines.rst:387
msgid ""
"This will make it more obvious which version would include the submitted "
"changes, should the pull request be merged now. Note, that the milestone is "
"not a binding contract and does not guarantee that this version is "
"definitely going to include the PR. If the pull request is not merged before "
"the version is released, the milestone will be moved (and the PR itself may "
"require a target branch change)."
msgstr ""

#: ../../docs/contributing/workflow/pr_review_guidelines.rst:394
msgid ""
"Similarly, when merging a PR with a higher milestone than the current "
"version, or a \"wildcard\" milestone (e.g. \"4.x\"), ensure to update the "
"milestone to the current version."
msgstr ""

#: ../../docs/contributing/workflow/pr_review_guidelines.rst:398
msgid ""
"**Make sure that the opening message of the PR contains the magic words "
"\"Closes #...\" or \"Fixes #...\".**"
msgstr ""

#: ../../docs/contributing/workflow/pr_review_guidelines.rst:401
msgid ""
"These link the PR and the referenced issue together and allow GitHub to auto-"
"close the latter when you merge the changes. Note, that this only works for "
"the PRs that target the ``master`` branch. For others you need to pay "
"attention and close the related issues manually. Do it with *\"Fixed by #..."
"\"* or *\"Resolved by #...\"* comment to clearly indicate the act for future "
"contributors."
msgstr ""

#: ../../docs/contributing/workflow/pr_review_guidelines.rst:408
msgid ""
"**For the issues that get closed by the PR add the closest relevant "
"milestone.**"
msgstr ""

#: ../../docs/contributing/workflow/pr_review_guidelines.rst:411
msgid ""
"In other words, if the PR is targeting the ``master`` branch, but is then "
"also cherrypicked for ``3.x``, the next ``3.x`` release would be the "
"appropriate milestone for the closed issue."
msgstr ""

#: ../../docs/contributing/workflow/pr_review_guidelines.rst:416
msgid "5. Merge the pull request"
msgstr ""

#: ../../docs/contributing/workflow/pr_review_guidelines.rst:418
msgid ""
"If it is appropriate for you to be merging a pull request (i.e. you are on "
"the production team or you are the team leader for that area), you are "
"confident that the pull request has been sufficiently reviewed, and once you "
"carry out these steps you can go ahead and merge the pull request."
msgstr ""

#: ../../docs/contributing/workflow/testing_pull_requests.rst:4
msgid "Testing pull requests"
msgstr ""

#: ../../docs/contributing/workflow/testing_pull_requests.rst:6
msgid ""
"Many people are developing new features or fixing bugs on GitHub. To help "
"with engine development, you may be asked to test those pull requests with a "
"Godot build that includes code from the pull request in question."
msgstr ""

#: ../../docs/contributing/workflow/testing_pull_requests.rst:10
msgid ""
"Thanks to GitHub Actions, all `pull requests <https://github.com/godotengine/"
"godot/pulls>`__ have continuous builds available. These builds let you try "
"out pull requests without having to compile anything from source."
msgstr ""

#: ../../docs/contributing/workflow/testing_pull_requests.rst:15
msgid "Downloading a compiled build"
msgstr ""

#: ../../docs/contributing/workflow/testing_pull_requests.rst:17
msgid ""
"You can download pull request builds from GitHub Actions. Since only signed "
"in users may download builds directly from GitHub Actions, the procedure "
"varies depending on whether you have a GitHub account or not."
msgstr ""

#: ../../docs/contributing/workflow/testing_pull_requests.rst:23
msgid ""
"Due to a GitHub Actions limitation, builds are only available for 90 days "
"after the pull request was last updated. If you still wish to try a pull "
"request locally, you can :ref:`compile the pull request branch from source "
"<doc_testing_pull_requests_compile>` instead."
msgstr ""

#: ../../docs/contributing/workflow/testing_pull_requests.rst:30
msgid "If you have a GitHub account"
msgstr ""

#: ../../docs/contributing/workflow/testing_pull_requests.rst:32
msgid ""
"Open the pull request page. Click the **Checks** tab near the top of the "
"page:"
msgstr ""

#: ../../docs/contributing/workflow/testing_pull_requests.rst:36
msgid "Click the **Artifacts** dropdown on the right of the page:"
msgstr ""

#: ../../docs/contributing/workflow/testing_pull_requests.rst:40
msgid ""
"In the dropdown, click the artifact's name to download it. Remember to "
"scroll if you cannot see the name of the platform you're looking for:"
msgstr ""

#: ../../docs/contributing/workflow/testing_pull_requests.rst:45
msgid ""
"Extract the ZIP archive then run the executable. Note that Windows and macOS "
"binaries are **not** code signed. This means you may have to bypass a "
"security warning before you can run the executable. On Windows, if you "
"frequently test pull request builds, it may be better to disable Windows "
"SmartScreen permanently in the Windows security settings. On macOS, see :ref:"
"`doc_running_on_macos` for instructions on bypassing Gatekeeper."
msgstr ""

#: ../../docs/contributing/workflow/testing_pull_requests.rst:53
msgid "If you don't have a GitHub account"
msgstr ""

#: ../../docs/contributing/workflow/testing_pull_requests.rst:55
msgid ""
"If you don't have a GitHub account and can't sign up for one, you can use "
"the third-party `nightly.link <https://nightly.link>`__ service to generate "
"a universal download link."
msgstr ""

#: ../../docs/contributing/workflow/testing_pull_requests.rst:59
#: ../../docs/contributing/workflow/testing_pull_requests.rst:93
msgid ""
"Open the pull request page. Click the *fork*'s branch name near the top of "
"the page:"
msgstr ""

#: ../../docs/contributing/workflow/testing_pull_requests.rst:63
msgid ""
"Now that you are on the fork's branch page, click the ``.github`` folder at "
"the top of the file list. Then, click on the ``workflows`` folder (which is "
"inside the ``.github`` folder). Click the workflow file for the platform you "
"wish to download artifacts for. *After* clicking on the file (which opens "
"the file view), copy the page URL from your browser's address bar."
msgstr ""

#: ../../docs/contributing/workflow/testing_pull_requests.rst:68
msgid ""
"Open the `nightly.link <https://nightly.link>`__ website and paste the URL "
"you just copied into the text field located below the heading **Paste a "
"GitHub link, get a nightly.link!**. After pasting the URL, click **Get "
"links** on the right. If the format of the URL you pasted is correct, you "
"should be presented with a page like this:"
msgstr ""

#: ../../docs/contributing/workflow/testing_pull_requests.rst:76
msgid "Click the URL of the artifact you wish to download."
msgstr ""

#: ../../docs/contributing/workflow/testing_pull_requests.rst:78
msgid ""
"Extract the ZIP archive then run the executable. Note that Windows and macOS "
"binaries are not code signed. This means you may have to bypass a security "
"warning before you can run the executable. If you frequently test pull "
"request builds, it may be better to disable Windows SmartScreen or `disable "
"macOS Gatekeeper <https://disable-gatekeeper.github.io/>`__ permanently."
msgstr ""

#: ../../docs/contributing/workflow/testing_pull_requests.rst:87
msgid "Compiling a pull request branch from source"
msgstr ""

#: ../../docs/contributing/workflow/testing_pull_requests.rst:89
msgid ""
"This approach may be needed for pull requests that were last updated more "
"than 90 days ago, or to test on platforms and configurations that are not "
"supported by Godot's GitHub Actions setup."
msgstr ""

#: ../../docs/contributing/workflow/testing_pull_requests.rst:97
msgid ""
"Now that you are on the fork's branch page, click the green **Code** button "
"on the right of the page then choose **Download ZIP** in the dropdown:"
msgstr ""

#: ../../docs/contributing/workflow/testing_pull_requests.rst:102
msgid ""
"Extract the ZIP archive and follow the :ref:`compiling <toc-devel-"
"compiling>` instructions for your operating system."
msgstr ""

#: ../../docs/contributing/development/index.rst:6
msgid ""
"The guides below explain how to contribute to the engine's codebase. You "
"will learn about best practices when working on solutions and features, the "
"code style and the internal structure of the codebase, how to set up your "
"working environment, and more."
msgstr ""

#: ../../docs/contributing/development/index.rst:10
#: ../../docs/contributing/documentation/index.rst:10
msgid ""
"Be sure to also check the :ref:`workflow guidelines "
"<doc_contributing_workflow>`, especially if you're new to using Git or "
"GitHub."
msgstr ""

#: ../../docs/contributing/development/index.rst:22
msgid "Buildsystem and work environment"
msgstr ""

#: ../../docs/contributing/development/index.rst:33
msgid "Engine architecture"
msgstr ""

#: ../../docs/contributing/development/best_practices_for_engine_contributors.rst:4
msgid "Best practices for engine contributors"
msgstr ""

#: ../../docs/contributing/development/best_practices_for_engine_contributors.rst:9
msgid ""
"Godot has a large amount of users who have the ability to contribute because "
"the project itself is aimed mainly at users who can code. That being said, "
"not all of them have the same level of experience working in large projects "
"or in software engineering, which can lead to common misunderstandings and "
"bad practices during the process of contributing code to the project."
msgstr ""

#: ../../docs/contributing/development/best_practices_for_engine_contributors.rst:18
msgid ""
"The scope of this document is to be a list of best practices for "
"contributors to follow, as well as to create a language they can use to "
"refer to common situations that arise in the process of submitting their "
"contributions."
msgstr ""

#: ../../docs/contributing/development/best_practices_for_engine_contributors.rst:22
msgid ""
"While a generalized list of software development best practices might be "
"useful, we'll focus on the situations that are most common in our project."
msgstr ""

#: ../../docs/contributing/development/best_practices_for_engine_contributors.rst:25
msgid ""
"Contributions are most of the time categorized as bug fixes, enhancements or "
"new features. To abstract this idea, we will call them *Solutions*, because "
"they always seek to solve something that can be described as a *Problem*."
msgstr ""

#: ../../docs/contributing/development/best_practices_for_engine_contributors.rst:30
msgid "Best Practices"
msgstr ""

#: ../../docs/contributing/development/best_practices_for_engine_contributors.rst:33
msgid "#1: The problem always comes first"
msgstr ""

#: ../../docs/contributing/development/best_practices_for_engine_contributors.rst:35
msgid ""
"Many contributors are extremely creative and just enjoy the process of "
"designing abstract data structures, creating nice user interfaces, or simply "
"love programming. Whatever the case may be, they come up with cool ideas, "
"which may or may not solve real problems."
msgstr ""

#: ../../docs/contributing/development/best_practices_for_engine_contributors.rst:42
msgid ""
"These are usually called *solutions in search of a problem*. In an ideal "
"world, they would not be harmful but, in reality, code takes time to write, "
"takes up space and requires maintenance once it exists. Avoiding the "
"addition of anything unnecessary is always considered a good practice in "
"software development."
msgstr ""

#: ../../docs/contributing/development/best_practices_for_engine_contributors.rst:48
msgid "#2: To solve the problem, it has to exist in the first place"
msgstr ""

#: ../../docs/contributing/development/best_practices_for_engine_contributors.rst:50
msgid ""
"This is a variation of the previous practice. Adding anything unnecessary is "
"not a good idea, but what constitutes what is necessary and what isn't?"
msgstr ""

#: ../../docs/contributing/development/best_practices_for_engine_contributors.rst:55
msgid ""
"The answer to this question is that the problem needs to *exist* before it "
"can be actually solved. It must not be speculation or a belief. The user "
"must be using the software as intended to create something they *need*. In "
"this process, the user may stumble upon a problem that requires a solution "
"to proceed, or in order to achieve greater productivity. In this case, *a "
"solution is needed*."
msgstr ""

#: ../../docs/contributing/development/best_practices_for_engine_contributors.rst:61
msgid ""
"Believing that problems may arise in the future and that the software needs "
"to be ready to solve them by the time they appear is called *\"Future "
"proofing\"* and its characterized by lines of thought such as:"
msgstr ""

#: ../../docs/contributing/development/best_practices_for_engine_contributors.rst:65
msgid "I think it would be useful for users to..."
msgstr ""

#: ../../docs/contributing/development/best_practices_for_engine_contributors.rst:66
msgid "I think users will eventually need to..."
msgstr ""

#: ../../docs/contributing/development/best_practices_for_engine_contributors.rst:68
msgid ""
"This is generally considered a bad habit because trying to solve problems "
"that *don't actually exist* in the present will often lead to code that will "
"be written but never used, or that is considerably more complex to use and "
"maintain than it needs to be."
msgstr ""

#: ../../docs/contributing/development/best_practices_for_engine_contributors.rst:74
msgid "#3: The problem has to be complex or frequent"
msgstr ""

#: ../../docs/contributing/development/best_practices_for_engine_contributors.rst:76
msgid ""
"Software is designed to solve problems, but we can't expect it to solve "
"*every problem that exists under the sun*. As a game engine, Godot will help "
"you make games better and faster, but it won't make an *entire game* for "
"you. A line must be drawn somewhere."
msgstr ""

#: ../../docs/contributing/development/best_practices_for_engine_contributors.rst:83
msgid ""
"Whether a problem is worth solving is determined by the effort that is "
"required to work around it. The required effort depends on:"
msgstr ""

#: ../../docs/contributing/development/best_practices_for_engine_contributors.rst:86
msgid "The complexity of the problem"
msgstr ""

#: ../../docs/contributing/development/best_practices_for_engine_contributors.rst:87
msgid "The frequency the problem"
msgstr ""

#: ../../docs/contributing/development/best_practices_for_engine_contributors.rst:89
msgid ""
"If the problem is *too complex* for most users to solve, then the software "
"should offer a ready-made solution for it. Likewise, if the problem is easy "
"for the user to work around, offering such a solution is unnecessary."
msgstr ""

#: ../../docs/contributing/development/best_practices_for_engine_contributors.rst:93
msgid ""
"The exception, however, is when the user encounters a problem *frequently "
"enough* that having to do the simple solution every time becomes an "
"annoyance. In this case, the software should offer a solution to simplify "
"the use case."
msgstr ""

#: ../../docs/contributing/development/best_practices_for_engine_contributors.rst:97
msgid ""
"It's usually easy to tell if a problem is complex or frequent, but it can be "
"difficult. This is why discussing with other developers (next point) is "
"always advised."
msgstr ""

#: ../../docs/contributing/development/best_practices_for_engine_contributors.rst:102
msgid "#4: The solution must be discussed with others"
msgstr ""

#: ../../docs/contributing/development/best_practices_for_engine_contributors.rst:104
msgid ""
"Often, users will be immersed in their own projects when they stumble upon "
"problems. These users will naturally try to solve the problem from their "
"perspective, thinking only about their own use case. As a result, user "
"proposed solutions don't always contemplate all use cases and are often "
"biased towards the user's own requirements."
msgstr ""

#: ../../docs/contributing/development/best_practices_for_engine_contributors.rst:112
msgid ""
"For developers, the perspective is different. They may find the user's "
"problem too unique to justify a solution (instead of a workaround), or they "
"might suggest a partial (usually simpler or lower level) solution that "
"applies to a wider range of known problems and leave the rest of the "
"solution up to the user."
msgstr ""

#: ../../docs/contributing/development/best_practices_for_engine_contributors.rst:118
msgid ""
"In any case, before attempting to contribute, it is important to discuss the "
"actual problems with the other developers or contributors, so a better "
"agreement on implementation can be reached."
msgstr ""

#: ../../docs/contributing/development/best_practices_for_engine_contributors.rst:122
msgid ""
"The only exception is when an area of code has a clear agreed upon owner, "
"who talks to users directly and has the most knowledge to implement a "
"solution directly."
msgstr ""

#: ../../docs/contributing/development/best_practices_for_engine_contributors.rst:126
msgid ""
"Also, Godot's philosophy is to favor ease of use and maintenance over "
"absolute performance. Performance optimizations will be considered, but they "
"may not be accepted if they make something too difficult to use or if they "
"add too much complexity to the codebase."
msgstr ""

#: ../../docs/contributing/development/best_practices_for_engine_contributors.rst:132
msgid "#5: To each problem, its own solution"
msgstr ""

#: ../../docs/contributing/development/best_practices_for_engine_contributors.rst:134
msgid ""
"For programmers, it is always a most enjoyable challenge to find the most "
"optimal solutions to problems. It is possible to go overboard, though. "
"Sometimes, contributors will try to come up with solutions that solve as "
"many problems as possible."
msgstr ""

#: ../../docs/contributing/development/best_practices_for_engine_contributors.rst:139
msgid ""
"The situation will often take a turn for the worse when, in order to make "
"this solution appear even more fantastic and flexible, the pure speculation-"
"based problems (as described in #2) also make their appearance on stage."
msgstr ""

#: ../../docs/contributing/development/best_practices_for_engine_contributors.rst:145
msgid ""
"The main problem is that, in reality, it rarely works this way. Most of the "
"time, writing an individual solution to each problem results in code that is "
"simpler and more maintainable."
msgstr ""

#: ../../docs/contributing/development/best_practices_for_engine_contributors.rst:149
msgid ""
"Additionally, solutions that target individual problems are better for the "
"users. Targeted solutions allow users find something that does exactly what "
"they need, without having to learn a more complex system they will only need "
"for simple tasks."
msgstr ""

#: ../../docs/contributing/development/best_practices_for_engine_contributors.rst:154
msgid ""
"Big and flexible solutions also have an additional drawback which is that, "
"over time, they are rarely flexible enough for all users. Users end up "
"requesting more and more functionality which ends up making the API and "
"codebase more and more complex."
msgstr ""

#: ../../docs/contributing/development/best_practices_for_engine_contributors.rst:160
msgid "#6: Cater to common use cases, leave the door open for the rare ones"
msgstr ""

#: ../../docs/contributing/development/best_practices_for_engine_contributors.rst:162
msgid ""
"This is a continuation of the previous point, which further explains why "
"this way of thinking and designing software is preferred."
msgstr ""

#: ../../docs/contributing/development/best_practices_for_engine_contributors.rst:165
msgid ""
"As mentioned before (in point #2), it is very difficult for us (as human "
"beings who design software) to actually understand all future user needs. "
"Trying to write very flexible structures that cater to many use cases at "
"once is often a mistake."
msgstr ""

#: ../../docs/contributing/development/best_practices_for_engine_contributors.rst:170
msgid ""
"We may come up with something we believe is brilliant but later find out "
"that users will never even use half of it or that they require features that "
"don't quite fit into our original design, forcing us to either throw it away "
"or make it even more complex."
msgstr ""

#: ../../docs/contributing/development/best_practices_for_engine_contributors.rst:175
msgid ""
"The question is then, how do we design software that both allows users to do "
"*what we know they need to do* now and allows them to do *what we don't yet "
"know they'll need to do* in the future?"
msgstr ""

#: ../../docs/contributing/development/best_practices_for_engine_contributors.rst:181
msgid ""
"The answer to this question is that, to ensure users still can do what they "
"want to do, we need to give them access to a *low level API* that they can "
"use to achieve what they want, even if it's more work for them because it "
"means reimplementing some logic that already exists."
msgstr ""

#: ../../docs/contributing/development/best_practices_for_engine_contributors.rst:186
msgid ""
"In real-life scenarios, these use cases will be at most rare and uncommon "
"anyway, so it makes sense a custom solution needs to be written. This is why "
"it's important to still provide users the basic building blocks to do it."
msgstr ""

#: ../../docs/contributing/development/best_practices_for_engine_contributors.rst:191
msgid "#7: Prefer local solutions"
msgstr ""

#: ../../docs/contributing/development/best_practices_for_engine_contributors.rst:193
msgid ""
"When looking for a solution to a problem, be it implementing a new feature "
"or fixing a bug, sometimes the easiest path is to add data or a new function "
"in the core layers of code."
msgstr ""

#: ../../docs/contributing/development/best_practices_for_engine_contributors.rst:197
msgid ""
"The main problem here is, adding something to the core layers that will only "
"be used from a single location far away will not only make the code more "
"difficult to follow (split in two), but also make the core API larger, more "
"complex, more difficult to understand in general."
msgstr ""

#: ../../docs/contributing/development/best_practices_for_engine_contributors.rst:202
msgid ""
"This is bad, because readability and cleanness of core APIs is always of "
"extreme importance given how much code relies on it, and because it's key "
"for new contributors as a starting point to learning the codebase."
msgstr ""

#: ../../docs/contributing/development/best_practices_for_engine_contributors.rst:210
msgid ""
"A common reason for wanting to do this is that it's usually less code to "
"simply add a hack in the core layers."
msgstr ""

#: ../../docs/contributing/development/best_practices_for_engine_contributors.rst:213
msgid ""
"Doing so is not advised. Generally, the code for a solution should be closer "
"to where the problem originates, even if it involves additional, duplicated, "
"more complex, or less efficient code. More creativity might be needed, but "
"this path is always the advised one."
msgstr ""

#: ../../docs/contributing/development/best_practices_for_engine_contributors.rst:219
msgid "#8: Don't use complex canned solutions for simple problems"
msgstr ""

#: ../../docs/contributing/development/best_practices_for_engine_contributors.rst:221
msgid ""
"Not every problem has a simple solution and, many times, the right choice is "
"to use a third party library to solve the problem."
msgstr ""

#: ../../docs/contributing/development/best_practices_for_engine_contributors.rst:224
msgid ""
"As Godot requires to be shipped in a large amount of platforms, we can't "
"link libraries dynamically. Instead, we bundle them in our source tree."
msgstr ""

#: ../../docs/contributing/development/best_practices_for_engine_contributors.rst:229
msgid ""
"As a result, we are very picky with what goes in, and we tend to prefer "
"smaller libraries (single header ones are our favorite). We will only bundle "
"something larger if there is no other choice."
msgstr ""

#: ../../docs/contributing/development/best_practices_for_engine_contributors.rst:235
msgid ""
"Libraries must use a permissive enough license to be included into Godot. "
"Some examples of acceptable licenses are Apache 2.0, BSD, MIT, ISC, and MPL "
"2.0. In particular, we cannot accept libraries licensed under the GPL or "
"LGPL since these licenses effectively disallow static linking in proprietary "
"software (which Godot is distributed as in most exported projects). This "
"requirement also applies to the editor, since we may want to run it on iOS "
"in the long term. Since iOS doesn't support dynamic linking, static linking "
"is the only option on that platform."
msgstr ""

#: ../../docs/contributing/development/code_style_guidelines.rst:4
msgid "Code style guidelines"
msgstr ""

#: ../../docs/contributing/development/code_style_guidelines.rst:8
msgid ""
"When contributing to Godot's source code, you will be expected to follow the "
"style guidelines outlined below. Some of them are checked via the Continuous "
"Integration process and reviewers will ask you to fix potential issues, so "
"best setup your system as outlined below to ensure all your commits follow "
"the guidelines."
msgstr ""

#: ../../docs/contributing/development/code_style_guidelines.rst:15
msgid "C++ and Objective-C"
msgstr ""

#: ../../docs/contributing/development/code_style_guidelines.rst:17
msgid ""
"There are no written guidelines, but the code style agreed upon by the "
"developers is enforced via the `clang-format <https://clang.llvm.org/docs/"
"ClangFormat.html>`__ code beautifier, which takes care for you of all our "
"conventions. To name a few:"
msgstr ""

#: ../../docs/contributing/development/code_style_guidelines.rst:22
msgid ""
"Indentation and alignment are both tab based (respectively one and two tabs)"
msgstr ""

#: ../../docs/contributing/development/code_style_guidelines.rst:23
msgid "One space around math and assignments operators as well as after commas"
msgstr ""

#: ../../docs/contributing/development/code_style_guidelines.rst:24
msgid ""
"Pointer and reference operators are affixed to the variable identifier, not "
"to the type name"
msgstr ""

#: ../../docs/contributing/development/code_style_guidelines.rst:26
msgid "See further down regarding header includes"
msgstr ""

#: ../../docs/contributing/development/code_style_guidelines.rst:28
msgid ""
"The rules used by clang-format are outlined in the `.clang-format <https://"
"github.com/godotengine/godot/blob/master/.clang-format>`__ file of the Godot "
"repository."
msgstr ""

#: ../../docs/contributing/development/code_style_guidelines.rst:32
msgid ""
"As long as you ensure that your style matches the surrounding code and that "
"you not introducing trailing whitespace or space-based indentation, you "
"should be fine. If you plan to contribute regularly, however, we strongly "
"advise that you set up clang-format locally to check and automatically fix "
"all your commits."
msgstr ""

#: ../../docs/contributing/development/code_style_guidelines.rst:37
msgid ""
"Godot's code style should *not* be applied to third-party code, i.e. that is "
"included in Godot's source tree but was not written specifically for our "
"project. Such code usually comes from different upstream projects with their "
"own style guides (or lack thereof), and don't want to introduce differences "
"that would make syncing with upstream repositories harder."
msgstr ""

#: ../../docs/contributing/development/code_style_guidelines.rst:44
msgid ""
"Third-party code is usually included in the ``thirdparty/`` folder and can "
"thus easily be excluded from formatting scripts. For the rare cases where a "
"third-party code snippet needs to be included directly within a Godot file, "
"you can use ``/* clang-format off */`` and ``/* clang-format on */`` to tell "
"clang-format to ignore a chunk of code."
msgstr ""

#: ../../docs/contributing/development/code_style_guidelines.rst:53
msgid ""
"These guidelines only cover code formatting. See :ref:"
"`doc_cpp_usage_guidelines` for a list of language features that are "
"permitted in pull requests."
msgstr ""

#: ../../docs/contributing/development/code_style_guidelines.rst:57
msgid "Using clang-format locally"
msgstr ""

#: ../../docs/contributing/development/code_style_guidelines.rst:59
msgid ""
"First of all, you will need to install clang-format. As of now, you need to "
"use **clang-format 13** to be compatible with Godot's format. Later versions "
"might be suitable, but previous versions may not support all used options, "
"or format some things differently, leading to style issues in pull requests."
msgstr ""

#: ../../docs/contributing/development/code_style_guidelines.rst:65
#: ../../docs/contributing/development/code_style_guidelines.rst:269
msgid "Installation"
msgstr ""

#: ../../docs/contributing/development/code_style_guidelines.rst:67
msgid "Here's how to install clang-format:"
msgstr ""

#: ../../docs/contributing/development/code_style_guidelines.rst:69
msgid ""
"Linux: It will usually be available out-of-the-box with the clang toolchain "
"packaged by your distribution. If your distro version is not the required "
"one, you can download a pre-compiled version from the `LLVM website <https://"
"releases.llvm.org/download.html>`__, or if you are on a Debian derivative, "
"use the `upstream repos <https://apt.llvm.org/>`__."
msgstr ""

#: ../../docs/contributing/development/code_style_guidelines.rst:74
msgid ""
"macOS and Windows: You can download precompiled binaries from the `LLVM "
"website <https://releases.llvm.org/download.html>`__. You may need to add "
"the path to the binary's folder to your system's ``PATH`` environment "
"variable to be able to call ``clang-format`` out of the box."
msgstr ""

#: ../../docs/contributing/development/code_style_guidelines.rst:79
msgid ""
"You then have different possibilities to apply clang-format to your changes:"
msgstr ""

#: ../../docs/contributing/development/code_style_guidelines.rst:82
#: ../../docs/contributing/development/code_style_guidelines.rst:281
msgid "Manual usage"
msgstr ""

#: ../../docs/contributing/development/code_style_guidelines.rst:84
msgid ""
"You can apply clang-format manually for one or more files with the following "
"command:"
msgstr ""

#: ../../docs/contributing/development/code_style_guidelines.rst:91
msgid ""
"``-i`` means that the changes should be written directly to the file (by "
"default clang-format would only output the fixed version to the terminal)."
msgstr ""

#: ../../docs/contributing/development/code_style_guidelines.rst:93
msgid ""
"The path can point to several files, either one after the other or using "
"wildcards like in a typical Unix shell. Be careful when globbing so that you "
"don't run clang-format on compiled objects (.o and .a files) that are in "
"Godot's tree. So better use ``core/*.{cpp,h}`` than ``core/*``."
msgstr ""

#: ../../docs/contributing/development/code_style_guidelines.rst:99
#: ../../docs/contributing/development/code_style_guidelines.rst:296
msgid "Pre-commit hook"
msgstr ""

#: ../../docs/contributing/development/code_style_guidelines.rst:101
msgid ""
"For ease of use, we provide a pre-commit hook for Git that will run clang-"
"format automatically on all your commits to check them, and let you apply "
"its changes in the final commit."
msgstr ""

#: ../../docs/contributing/development/code_style_guidelines.rst:105
msgid ""
"This \"hook\" is a script that can be found in ``misc/hooks``, refer to that "
"folder's README.md for installation instructions."
msgstr ""

#: ../../docs/contributing/development/code_style_guidelines.rst:108
msgid ""
"If your clang-format is not in the ``PATH``, you may have to edit the ``pre-"
"commit-clang-format`` to point to the correct binary for it to work. The "
"hook was tested on Linux and macOS, but should also work in the Git Shell on "
"Windows."
msgstr ""

#: ../../docs/contributing/development/code_style_guidelines.rst:114
msgid "IDE plugin"
msgstr ""

#: ../../docs/contributing/development/code_style_guidelines.rst:116
msgid ""
"Most IDEs or code editors have beautifier plugins that can be configured to "
"run clang-format automatically, for example, each time you save a file."
msgstr ""

#: ../../docs/contributing/development/code_style_guidelines.rst:119
msgid "Here is a non-exhaustive list of beautifier plugins for some IDEs:"
msgstr ""

#: ../../docs/contributing/development/code_style_guidelines.rst:121
msgid ""
"Qt Creator: `Beautifier plugin <https://doc.qt.io/qtcreator/creator-"
"beautifier.html>`__"
msgstr ""

#: ../../docs/contributing/development/code_style_guidelines.rst:122
msgid ""
"Visual Studio Code: `Clang-Format <https://marketplace.visualstudio.com/"
"items?itemName=xaver.clang-format>`__"
msgstr ""

#: ../../docs/contributing/development/code_style_guidelines.rst:123
msgid ""
"Visual Studio: `Clang Power Tools 2022 <https://marketplace.visualstudio.com/"
"items?itemName=caphyon.ClangPowerTools2022>`__"
msgstr ""

#: ../../docs/contributing/development/code_style_guidelines.rst:124
msgid "vim: `vim-clang-format <https://github.com/rhysd/vim-clang-format>`__"
msgstr ""

#: ../../docs/contributing/development/code_style_guidelines.rst:125
msgid ""
"CLion: Starting from version ``2019.1``, no plugin is required. Instead, "
"enable `ClangFormat <https://www.jetbrains.com/help/clion/clangformat-as-"
"alternative-formatter.html#clion-support>`__"
msgstr ""

#: ../../docs/contributing/development/code_style_guidelines.rst:128
msgid "(Pull requests are welcome to extend this list with tested plugins.)"
msgstr ""

#: ../../docs/contributing/development/code_style_guidelines.rst:133
msgid "Header includes"
msgstr ""

#: ../../docs/contributing/development/code_style_guidelines.rst:135
msgid ""
"When adding new C++ or Objective-C files or including new headers in "
"existing ones, the following rules should be followed:"
msgstr ""

#: ../../docs/contributing/development/code_style_guidelines.rst:138
msgid ""
"The first lines in the file should be Godot's copyright header and MIT "
"license, copy-pasted from another file. Make sure to adjust the filename."
msgstr ""

#: ../../docs/contributing/development/code_style_guidelines.rst:140
msgid ""
"In a ``.h`` header, include guards should be used with the form "
"``FILENAME_H``."
msgstr ""

#: ../../docs/contributing/development/code_style_guidelines.rst:143
msgid ""
"In a ``.cpp`` file (e.g. ``filename.cpp``), the first include should be the "
"one where the class is declared (e.g. ``#include \"filename.h\"``), followed "
"by an empty line for separation."
msgstr ""

#: ../../docs/contributing/development/code_style_guidelines.rst:146
msgid ""
"Then come headers from Godot's own code base, included in alphabetical order "
"(enforced by ``clang-format``) with paths relative to the root folder. Those "
"includes should be done with quotes, e.g. ``#include \"core/object.h\"``. "
"The block of Godot header includes should then be followed by an empty line "
"for separation."
msgstr ""

#: ../../docs/contributing/development/code_style_guidelines.rst:151
msgid ""
"Finally, third-party headers (either from ``thirdparty`` or from the "
"system's include paths) come next and should be included with the < and > "
"symbols, e.g. ``#include <png.h>``. The block of third-party headers should "
"also be followed by an empty line for separation."
msgstr ""

#: ../../docs/contributing/development/code_style_guidelines.rst:155
msgid ""
"Godot and third-party headers should be included in the file that requires "
"them, i.e. in the `.h` header if used in the declarative code or in the `."
"cpp` if used only in the imperative code."
msgstr ""

#: ../../docs/contributing/development/code_style_guidelines.rst:249
msgid ""
"Godot's Java code (mostly in ``platform/android``) is also enforced via "
"``clang-format``, so see the instructions above to set it up. Keep in mind "
"that this style guide only applies to code written and maintained by Godot, "
"not third-party code such as the ``java/src/com/google`` subfolder."
msgstr ""

#: ../../docs/contributing/development/code_style_guidelines.rst:255
msgid "Python"
msgstr ""

#: ../../docs/contributing/development/code_style_guidelines.rst:257
msgid ""
"Godot's SCons buildsystem is written in Python, and various scripts included "
"in the source tree are also using Python."
msgstr ""

#: ../../docs/contributing/development/code_style_guidelines.rst:260
msgid ""
"For those, we follow the `Black style guide <https://github.com/psf/"
"black#the-black-code-style>`__. Blacken your Python changes using `Black "
"<https://pypi.org/project/black/>`__."
msgstr ""

#: ../../docs/contributing/development/code_style_guidelines.rst:264
msgid "Using black locally"
msgstr ""

#: ../../docs/contributing/development/code_style_guidelines.rst:266
msgid ""
"First of all, you will need to install Black. Black requires Python 3.7+ to "
"run."
msgstr ""

#: ../../docs/contributing/development/code_style_guidelines.rst:271
msgid "Here's how to install black:"
msgstr ""

#: ../../docs/contributing/development/code_style_guidelines.rst:278
msgid "You then have different possibilities to apply black to your changes:"
msgstr ""

#: ../../docs/contributing/development/code_style_guidelines.rst:283
msgid ""
"You can apply ``black`` manually to one or more files with the following "
"command:"
msgstr ""

#: ../../docs/contributing/development/code_style_guidelines.rst:290
msgid ""
"``-l 120`` means that the allowed number of characters per line is 120. This "
"number was agreed upon by the developers."
msgstr ""

#: ../../docs/contributing/development/code_style_guidelines.rst:292
msgid ""
"The path can point to several files, either one after the other or using "
"wildcards like in a typical Unix shell."
msgstr ""

#: ../../docs/contributing/development/code_style_guidelines.rst:298
msgid ""
"For ease of use, we provide a pre-commit hook for Git that will run black "
"automatically on all your commits to check them, and let you apply its "
"changes in the final commit."
msgstr ""

#: ../../docs/contributing/development/code_style_guidelines.rst:302
msgid ""
"This \"hook\" is a script which can be found in ``misc/hooks``. Refer to "
"that folder's ``README.md`` for installation instructions."
msgstr ""

#: ../../docs/contributing/development/code_style_guidelines.rst:307
#, fuzzy
msgid "Editor integration"
msgstr "Kreiranje Sadržaja"

#: ../../docs/contributing/development/code_style_guidelines.rst:309
msgid ""
"Many IDEs or code editors have beautifier plugins that can be configured to "
"run black automatically, for example, each time you save a file. For "
"details, you can check `Black editor integration <https://github.com/psf/"
"black#editor-integration>`__."
msgstr ""

#: ../../docs/contributing/development/code_style_guidelines.rst:314
#, fuzzy
msgid "Comment style guide"
msgstr "Kreiranje Sadržaja"

#: ../../docs/contributing/development/code_style_guidelines.rst:316
msgid ""
"This comment style guide applies to all programming languages used within "
"Godot's codebase."
msgstr ""

#: ../../docs/contributing/development/code_style_guidelines.rst:319
msgid ""
"Begin comments with a space character to distinguish them from disabled code."
msgstr ""

#: ../../docs/contributing/development/code_style_guidelines.rst:320
msgid ""
"Use sentence case for comments. Begin comments with an uppercase character "
"and always end them with a period."
msgstr ""

#: ../../docs/contributing/development/code_style_guidelines.rst:322
msgid "Reference variable/function names and values using backticks."
msgstr ""

#: ../../docs/contributing/development/code_style_guidelines.rst:323
msgid "Wrap comments to ~100 characters."
msgstr ""

#: ../../docs/contributing/development/code_style_guidelines.rst:324
msgid ""
"You can use ``TODO:``, ``FIXME:``, ``NOTE:``, or ``HACK:`` as admonitions "
"when needed."
msgstr ""

#: ../../docs/contributing/development/code_style_guidelines.rst:327
#: ../../docs/contributing/development/code_style_guidelines.rst:350
msgid "**Example:**"
msgstr ""

#: ../../docs/contributing/development/code_style_guidelines.rst:335
msgid ""
"Don't repeat what the code says in a comment. Explain the *why* rather than "
"*how*."
msgstr ""

#: ../../docs/contributing/development/code_style_guidelines.rst:337
msgid "**Bad:**"
msgstr ""

#: ../../docs/contributing/development/code_style_guidelines.rst:344
msgid ""
"You can use Javadoc-style comments above function or macro definitions. It's "
"recommended to use Javadoc-style comments *only* for methods which are not "
"exposed to scripting. This is because exposed methods should be documented "
"in the :ref:`class reference XML <doc_updating_the_class_reference>` instead."
msgstr ""

#: ../../docs/contributing/development/code_style_guidelines.rst:362
msgid ""
"For member variables, don't use Javadoc-style comments but use single-line "
"comments instead:"
msgstr ""

#: ../../docs/contributing/development/cpp_usage_guidelines.rst:4
msgid "C++ usage guidelines"
msgstr ""

#: ../../docs/contributing/development/cpp_usage_guidelines.rst:7
#: ../../docs/contributing/development/compiling/optimizing_for_size.rst:9
msgid "Rationale"
msgstr ""

#: ../../docs/contributing/development/cpp_usage_guidelines.rst:9
msgid ""
"Since Godot 4.0, the C++ standard used throughout the codebase is a subset "
"of **C++17**. While modern C++ brings a lot of opportunities to write "
"faster, more readable code, we chose to restrict our usage of C++ to a "
"subset for a few reasons:"
msgstr ""

#: ../../docs/contributing/development/cpp_usage_guidelines.rst:14
msgid ""
"It makes it easier to review code in online editors. This is because engine "
"contributors don't always have access to a full-featured IDE while reviewing "
"code."
msgstr ""

#: ../../docs/contributing/development/cpp_usage_guidelines.rst:17
msgid ""
"It makes the code easier to grasp for beginner contributors (who may not be "
"professional C++ programmers). Godot's codebase is known to be easy to learn "
"from, and we'd like to keep it that way."
msgstr ""

#: ../../docs/contributing/development/cpp_usage_guidelines.rst:21
msgid ""
"To get your pull request merged, it needs to follow the C++ usage guidelines "
"outlined here. Of course, you can use features not allowed here in your own "
"C++ modules or GDExtensions."
msgstr ""

#: ../../docs/contributing/development/cpp_usage_guidelines.rst:27
msgid ""
"Prior to Godot 4.0, the C++ standard used throughout the codebase was C++03, "
"with a handful of C++14 extensions. If you are contributing a pull request "
"to the `3.x` branch rather than `master`, your code can't use C++17 "
"features. Instead, your code must be able to be built with a C++14 compiler."
msgstr ""

#: ../../docs/contributing/development/cpp_usage_guidelines.rst:32
msgid ""
"The guidelines below don't apply to third-party dependencies, although we "
"generally favor small libraries instead of larger solutions. See also :ref:"
"`doc_best_practices_for_engine_contributors`."
msgstr ""

#: ../../docs/contributing/development/cpp_usage_guidelines.rst:38
msgid "See :ref:`doc_code_style_guidelines` for formatting guidelines."
msgstr ""

#: ../../docs/contributing/development/cpp_usage_guidelines.rst:41
msgid "Disallowed features"
msgstr ""

#: ../../docs/contributing/development/cpp_usage_guidelines.rst:43
msgid ""
"**Any feature not listed below is allowed.** Using features like "
"``constexpr`` variables and ``nullptr`` is encouraged when possible. Still, "
"try to keep your use of modern C++ features conservative. Their use needs to "
"serve a real purpose, such as improving code readability or performance."
msgstr ""

#: ../../docs/contributing/development/cpp_usage_guidelines.rst:49
msgid "Standard Template Library"
msgstr ""

#: ../../docs/contributing/development/cpp_usage_guidelines.rst:51
msgid ""
"We don't allow using the `STL <https://en.wikipedia.org/wiki/"
"Standard_Template_Library>`__ as Godot provides its own data types (among "
"other things). See :ref:`doc_faq_why_not_stl` for more information."
msgstr ""

#: ../../docs/contributing/development/cpp_usage_guidelines.rst:55
msgid ""
"This means that pull requests should **not** use ``std::string``, ``std::"
"vector`` and the like. Instead, use Godot's datatypes as described below:"
msgstr ""

#: ../../docs/contributing/development/cpp_usage_guidelines.rst:58
msgid "Use ``String`` instead of ``std::string``."
msgstr ""

#: ../../docs/contributing/development/cpp_usage_guidelines.rst:59
msgid ""
"Use ``Vector`` instead of ``std::vector``. In some cases, ``LocalVector`` "
"can be used as an alternative (ask core developers first)."
msgstr ""

#: ../../docs/contributing/development/cpp_usage_guidelines.rst:61
msgid "Use ``Array`` instead of ``std::array``."
msgstr ""

#: ../../docs/contributing/development/cpp_usage_guidelines.rst:65
msgid ""
"Godot also has a List datatype (which is a linked list). While List is "
"already used in the codebase, it typically performs worse than other "
"datatypes like Vector and Array. Therefore, List should be avoided in new "
"code unless necessary."
msgstr ""

#: ../../docs/contributing/development/cpp_usage_guidelines.rst:70
msgid "``auto`` keyword"
msgstr ""

#: ../../docs/contributing/development/cpp_usage_guidelines.rst:72
msgid ""
"Please don't use the ``auto`` keyword for type inference. While it can avoid "
"repetition, it can also lead to confusing code:"
msgstr ""

#: ../../docs/contributing/development/cpp_usage_guidelines.rst:83
msgid ""
"Keep in mind hover documentation often isn't readily available for pull "
"request reviewers. Most of the time, reviewers will use GitHub's online "
"viewer to review pull requests."
msgstr ""

#: ../../docs/contributing/development/cpp_usage_guidelines.rst:87
msgid ""
"We chose to forbid ``auto`` instead of allowing it on a case-by-case basis "
"to avoid having to decide on difficult edge cases. Thank you for your "
"understanding."
msgstr ""

#: ../../docs/contributing/development/cpp_usage_guidelines.rst:91
msgid "Lambdas"
msgstr ""

#: ../../docs/contributing/development/cpp_usage_guidelines.rst:93
msgid ""
"Lambdas should be used conservatively when they make code effectively faster "
"or simpler, and do not impede readability. Please ask before using lambdas "
"in a pull request."
msgstr ""

#: ../../docs/contributing/development/cpp_usage_guidelines.rst:98
msgid "``#pragma once`` directive"
msgstr ""

#: ../../docs/contributing/development/cpp_usage_guidelines.rst:100
msgid ""
"To follow the existing style, please use standard ``#ifdef``-based include "
"guards instead of ``#pragma once`` in new files."
msgstr ""

#: ../../docs/contributing/development/cpp_usage_guidelines.rst:105
msgid ""
"See :ref:`doc_code_style_guidelines_header_includes` for guidelines on "
"sorting includes in C++ and Objective-C files."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/index.rst:4
msgid "Configuring an IDE"
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/index.rst:6
msgid ""
"We assume that you have already `cloned <https://github.com/godotengine/"
"godot>`_ and :ref:`compiled <toc-devel-compiling>` Godot."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/index.rst:9
msgid ""
"You can easily develop Godot with any text editor and by invoking ``scons`` "
"on the command line, but if you want to work with an IDE (Integrated "
"Development Environment), here are setup instructions for some popular ones:"
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/index.rst:27
msgid ""
"It is possible to use other IDEs, but their setup is not documented yet."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/index.rst:29
msgid ""
"If your editor supports the `language server protocol <https://microsoft."
"github.io/language-server-protocol/>`__, you can use `clangd <https://clangd."
"llvm.org>`__ for completion, diagnostics, and more. You can generate a "
"compilation database for use with clangd one of two ways:"
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/android_studio.rst:4
msgid "Android Studio"
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/android_studio.rst:6
msgid ""
"`Android Studio <https://developer.android.com/studio>`_ is a free IDE for "
"Android development made by `Google <https://about.google/>`_ and `JetBrains "
"<https://www.jetbrains.com/>`_. It's based on `IntelliJ IDEA <https://www."
"jetbrains.com/idea/>`_ and has a feature-rich editor which supports Java and "
"C/C++. It can be used to work on Godot's core engine as well as the Android "
"platform codebase."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/android_studio.rst:13
#: ../../docs/contributing/development/configuring_an_ide/clion.rst:10
#: ../../docs/contributing/development/configuring_an_ide/kdevelop.rst:9
#: ../../docs/contributing/development/configuring_an_ide/qt_creator.rst:9
#: ../../docs/contributing/development/configuring_an_ide/rider.rst:10
#: ../../docs/contributing/development/configuring_an_ide/visual_studio.rst:12
#: ../../docs/contributing/development/configuring_an_ide/visual_studio_code.rst:10
#: ../../docs/contributing/development/configuring_an_ide/xcode.rst:10
msgid "Importing the project"
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/android_studio.rst:15
msgid "From the Android Studio's welcome window select **Open**."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/android_studio.rst:21
msgid "Android Studio's welcome window."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/android_studio.rst:23
msgid ""
"Navigate to ``<Godot root directory>/platform/android/java`` and select the "
"``settings.gradle`` file."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/android_studio.rst:24
msgid "Android Studio will import and index the project."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/android_studio.rst:27
msgid "Android Studio project layout"
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/android_studio.rst:29
msgid ""
"The project is organized using `Android Studio's modules <https://developer."
"android.com/studio/projects#ApplicationModules>`_:"
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/android_studio.rst:34
msgid "``lib`` module:"
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/android_studio.rst:32
msgid ""
"Located under ``<Godot root directory>/platform/android/java/lib``, this is "
"a **library module** that organizes"
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/android_studio.rst:33
msgid ""
"the Godot java and native code and make it available as a reusable "
"dependency / artifact."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/android_studio.rst:34
msgid ""
"The artifact generated by this module is made available for other Android "
"modules / projects to use as a dependency, via `MavenCentral <https://repo1."
"maven.org/maven2/org/godotengine/godot/>`_."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/android_studio.rst:39
msgid "``editor`` module:"
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/android_studio.rst:37
msgid ""
"Located under ``<Godot root directory>/platform/android/java/editor``, this "
"is an **application module** that holds"
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/android_studio.rst:38
msgid "the source code for the Android port of the Godot Editor."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/android_studio.rst:39
#: ../../docs/contributing/development/configuring_an_ide/android_studio.rst:44
msgid "This module has a dependency on the ``lib`` module."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/android_studio.rst:44
msgid "``app`` module:"
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/android_studio.rst:42
msgid ""
"Located under ``<Godot root directory>/platform/android/java/app``, this is "
"an **application module** that holds"
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/android_studio.rst:43
msgid "the source code for the Android build templates."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/android_studio.rst:47
#, fuzzy
msgid "Building & debugging the editor module"
msgstr "Kreiranje Sadržaja"

#: ../../docs/contributing/development/configuring_an_ide/android_studio.rst:55
msgid "To build the ``editor`` module:"
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/android_studio.rst:50
msgid ""
"Select the `Run/Debug Configurations drop down <https://developer.android."
"com/studio/run/rundebugconfig#running>`_ and select ``editor``."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/android_studio.rst:56
msgid ""
"Select **Run > Run 'editor'** from the top menu or `click the Run icon "
"<https://developer.android.com/studio/run/rundebugconfig#running>`_."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/android_studio.rst:72
msgid "To debug the ``editor`` module:"
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/android_studio.rst:58
#: ../../docs/contributing/development/configuring_an_ide/android_studio.rst:91
msgid ""
"Open the **Build Variants** window using **View > Tools Windows > Build "
"Variants** from the top menu."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/android_studio.rst:59
msgid ""
"In the **Build Variants** window, make sure that in the **Active Build "
"Variant** column, the ``:editor`` entry is set to **dev**."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/android_studio.rst:65
#: ../../docs/contributing/development/configuring_an_ide/android_studio.rst:98
msgid ""
"Open the **Run/Debug Configurations** window by clicking on **Run > Edit "
"Configurations...** on the top menu."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/android_studio.rst:66
msgid ""
"In the **Run/Debug Configurations** window, select the ``editor`` entry, and "
"under **Debugger** make sure the **Debug Type** is set to ``Dual (Java + "
"Native)``"
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/android_studio.rst:72
msgid ""
"Select **Run > Debug 'editor'** from the top menu or `click the Debug icon "
"<https://developer.android.com/studio/run/rundebugconfig#running>`_."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/android_studio.rst:75
msgid "Building & debugging the app module"
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/android_studio.rst:77
msgid ""
"The ``app`` module requires the presence of a Godot project in its "
"``assets`` directory (``<Godot root directory>/platform/android/java/app/"
"assets``) to run. This is usually handled by the Godot Editor during the "
"export process. While developing in Android Studio, it's necessary to "
"manually add a Godot project under that directory to replicate the export "
"process. Once that's done, you can follow the instructions below to run/"
"debug the ``app`` module:"
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/android_studio.rst:88
msgid "To build the ``app`` module:"
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/android_studio.rst:83
msgid ""
"Select the `Run/Debug Configurations drop down <https://developer.android."
"com/studio/run/rundebugconfig#running>`_ and select ``app``."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/android_studio.rst:89
msgid ""
"Select **Run > Run 'app'** from the top menu or `click the Run icon <https://"
"developer.android.com/studio/run/rundebugconfig#running>`_."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/android_studio.rst:106
msgid "To debug the ``app`` module:"
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/android_studio.rst:92
msgid ""
"In the **Build Variants** window, make sure that in the **Active Build "
"Variant** column, the ``:app`` entry is set to **dev**."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/android_studio.rst:99
msgid ""
"In the **Run/Debug Configurations** window, select the ``app`` entry, and "
"under **Debugger** make sure the **Debug Type** is set to ``Dual (Java + "
"Native)``"
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/android_studio.rst:105
msgid ""
"Select **Run > Debug 'app'** from the top menu or `click the Debug icon "
"<https://developer.android.com/studio/run/rundebugconfig#running>`_."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/android_studio.rst:108
#, fuzzy
msgid ""
"If you run into any issues, ask for help in `Godot's Android dev channel "
"<https://chat.godotengine.org/channel/android>`__."
msgstr ""
"Takođe pogledajte `licencu na Godot sajtu <https://godotengine.org/"
"license>`_."

#: ../../docs/contributing/development/configuring_an_ide/clion.rst:4
msgid "CLion"
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/clion.rst:6
msgid ""
"`CLion <https://www.jetbrains.com/clion/>`_ is a commercial `JetBrains "
"<https://www.jetbrains.com/>`_ IDE for C++."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/clion.rst:12
msgid ""
"CLion can import a project's `compilation database file <https://clang.llvm."
"org/docs/JSONCompilationDatabase.html>`_, commonly named ``compile_commands."
"json``. To generate the compilation database file, open the terminal, change "
"to the Godot root directory, and run:"
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/clion.rst:18
msgid ""
"Then, open the Godot root directory with CLion. CLion will import the "
"compilation database, index the codebase, and provide autocompletion and "
"other advanced code navigation and refactoring functionality."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/clion.rst:21
#: ../../docs/contributing/development/configuring_an_ide/rider.rst:37
#, fuzzy
msgid "Compiling and debugging the project"
msgstr "Kreiranje Sadržaja"

#: ../../docs/contributing/development/configuring_an_ide/clion.rst:23
msgid ""
"CLion does not support compiling and debugging Godot via SCons out of the "
"box. This can be achieved by creating a custom build target and run "
"configuration in CLion. Before creating a custom build target, you must :ref:"
"`compile Godot <toc-devel-compiling>` once on the command line, to generate "
"the Godot executable. Open the terminal, change into the Godot root "
"directory, and execute:"
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/clion.rst:29
msgid "To add a custom build target that invokes SCons for compilation:"
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/clion.rst:31
msgid ""
"Open CLion and navigate to **Preferences > Build, Execution, Deployment > "
"Custom Build Targets**"
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/clion.rst:36
msgid "Click **Add target** and give the target a name, e.g. ``Godot debug``."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/clion.rst:41
msgid ""
"Click **...** next to the **Build:** selectbox, then click the **+** button "
"in the **External Tools** dialog to add a new external tool."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/clion.rst:46
msgid ""
"Give the tool a name, e.g. ``Build Godot debug``, set **Program** to "
"``scons``, set **Arguments** to the compilation settings you want (see :ref:"
"`compiling Godot <toc-devel-compiling>`), and set the **Working directory** "
"to ``$ProjectFileDir$``, which equals the Godot root directory. Click **OK** "
"to create the tool."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/clion.rst:48
msgid ""
"CLion does not expand shell commands like ``scons -j$(nproc)``. Use concrete "
"values instead, e.g. ``scons -j8``."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/clion.rst:53
msgid ""
"Back in the **External Tools** dialog, click the **+** again to add a second "
"external tool for cleaning the Godot build via SCons. Give the tool a name, "
"e.g. ``Clean Godot debug``, set **Program** to ``scons``, set **Arguments** "
"to ``-c`` (which will clean the build), and set the **Working directory** to "
"``$ProjectFileDir$``. Click **OK** to create the tool."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/clion.rst:58
msgid ""
"Close the **External Tools** dialog. In the **Custom Build Target** dialog "
"for the custom ``Godot debug`` build target, select the **Build Godot "
"debug** tool from the **Build** select box, and select the **Clean Godot "
"debug** tool from the **Clean** select box. Click **OK** to create the "
"custom build target."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/clion.rst:63
msgid "In the main IDE window, click **Add Configuration**."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/clion.rst:68
msgid ""
"In the **Run/Debug Configuration** dialog, click **Add new...**, then select "
"**Custom Build Application** to create a new custom run/debug configuration."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/clion.rst:73
msgid ""
"Give the run/debug configuration a name, e.g. ``Godot debug``, select the "
"``Godot debug`` custom build target as the **Target**. Select the Godot "
"executable in the ``bin/`` folder as the **Executable**, and set the "
"**Program arguments** to ``--editor --path path-to-your-project/``, where "
"``path-to-your-project/`` should be a path pointing to an existing Godot "
"project. If you omit the ``--path`` argument, you will only be able to debug "
"the Godot Project Manager window. Click **OK** to create the run/debug "
"configuration."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/clion.rst:78
msgid ""
"You can now build, run, debug, profile, and Valgrind check the Godot editor "
"via the run configuration."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/clion.rst:83
msgid ""
"When playing a scene, the Godot editor will spawn a separate process. You "
"can debug this process in CLion by going to **Run > Attach to process...**, "
"typing ``godot``, and selecting the Godot process with the highest **pid** "
"(process ID), which will usually be the running project."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/code_blocks.rst:4
msgid "Code::Blocks"
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/code_blocks.rst:6
msgid ""
"`Code::Blocks <https://codeblocks.org/>`_ is a free, open source, cross "
"platform IDE."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/code_blocks.rst:9
#, fuzzy
msgid "Creating a new project"
msgstr "Kreiranje Sadržaja"

#: ../../docs/contributing/development/configuring_an_ide/code_blocks.rst:11
msgid ""
"From Code::Blocks' main screen, click **Create a new project** or select "
"**File > New > Project...**."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/code_blocks.rst:17
msgid ""
"In the **New from template** window, from **Projects**, select **Empty "
"project**, and click **Go**."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/code_blocks.rst:23
msgid "Click Next, to pass the welcome to the new empty project wizard."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/code_blocks.rst:29
msgid ""
"The project file should be created in the root of the cloned project folder. "
"To achieve this, first, ensure that the **Project title** is the same as the "
"folder name that Godot was cloned into. Unless you cloned the project into a "
"folder with a different name, this will be ``godot``."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/code_blocks.rst:31
msgid ""
"Second, ensure that the **Folder to create project in** is the folder you "
"ran the Git clone command from, not the ``godot`` project folder. Confirm "
"that the **Resulting filename** field will create the project file in the "
"root of the cloned project folder."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/code_blocks.rst:37
msgid ""
"The compiler and configuration settings are managed through **SCons** and "
"will be configured later. However, it's worth deselecting the **Create "
"\"Release\" configuration** option; so only a single build target is created "
"before clicking **Finish**."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/code_blocks.rst:44
msgid "Configuring the build"
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/code_blocks.rst:46
msgid ""
"The first step is to change the project properties. Right-click on the new "
"project and select **Properties...**."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/code_blocks.rst:52
msgid ""
"Check the **This is a custom Makefile** property. Click OK to save the "
"changes."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/code_blocks.rst:58
msgid ""
"The next step is to change the build options. Right-click on the new project "
"and select **Build Options...**."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/code_blocks.rst:64
msgid ""
"Select the **\"Make\" commands** tab and remove all the existing commands "
"for all the build targets. For each build target enter the **SCons** command "
"for creating the desired build in the **Build project/target** field. The "
"minimum is ``scons``. For details on the **SCons** build options, see :ref:"
"`doc_introduction_to_the_buildsystem`. It's also useful to add the ``scons --"
"clean`` command in the **Clean project/target** field to the project's "
"default commands."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/code_blocks.rst:66
msgid ""
"If you're using Windows, all the commands need to be preceded with ``cmd /"
"c`` to initialize the command interpreter."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/code_blocks.rst:76
#, fuzzy
msgid "Windows example:"
msgstr "Windows"

#: ../../docs/contributing/development/configuring_an_ide/code_blocks.rst:82
msgid ""
"Code::Blocks should now be configured to build Godot; so either select "
"**Build > Build**, click the gear button, or press :kbd:`Ctrl + F9`."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/code_blocks.rst:85
msgid "Configuring the run"
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/code_blocks.rst:87
msgid ""
"Once **SCons** has successfully built the desired target, reopen the project "
"**Properties...** and select the **Build targets** tab. In the **Output "
"filename** field, browse to the ``bin`` folder and select the compiled file."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/code_blocks.rst:89
msgid ""
"Deselect the **Auto-generate filename prefix** and **Auto-generate filename "
"extension** options."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/code_blocks.rst:95
msgid ""
"Code::Blocks should now be configured to run your compiled Godot executable; "
"so either select **Build > Run**, click the green arrow button, or press :"
"kbd:`Ctrl + F10`."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/code_blocks.rst:97
msgid ""
"There are two additional points worth noting. First, if required, the "
"**Execution working dir** field can be used to test specific projects, by "
"setting it to the folder containing the ``project.godot`` file. Second, the "
"**Build targets** tab can be used to add and remove build targets for "
"working with and creating different builds."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/code_blocks.rst:100
#, fuzzy
msgid "Adding files to the project"
msgstr "Kreiranje Sadržaja"

#: ../../docs/contributing/development/configuring_an_ide/code_blocks.rst:102
msgid ""
"To add all the Godot code files to the project, right-click on the new "
"project and select **Add files recursively...**."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/code_blocks.rst:108
msgid ""
"It should automatically select the project folder; so simply click **Open**. "
"By default, all code files are included, so simply click **OK**."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/code_blocks.rst:115
#: ../../docs/contributing/development/configuring_an_ide/qt_creator.rst:92
msgid "Code style configuration"
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/code_blocks.rst:117
msgid ""
"Before editing any files, remember that all code needs to comply with the :"
"ref:`doc_code_style_guidelines`. One important difference with Godot is the "
"use of tabs for indents. Therefore, the key default editor setting that "
"needs to be changed in Code::Blocks is to enable tabs for indents. This "
"setting can be found by selecting **Settings > Editor**."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/code_blocks.rst:123
msgid ""
"Under **General Settings**, on the **Editor Settings** tab, under **Tab "
"Options** check **Use TAB character**."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/code_blocks.rst:129
#, fuzzy
msgid ""
"That's it. You're ready to start contributing to Godot using the Code::"
"Blocks IDE. Remember to save the project file and the **Workspace**. If you "
"run into any issues, ask for help in one of `Godot's community channels "
"<https://godotengine.org/community>`__."
msgstr ""
"Takođe pogledajte `licencu na Godot sajtu <https://godotengine.org/"
"license>`_."

#: ../../docs/contributing/development/configuring_an_ide/kdevelop.rst:4
msgid "KDevelop"
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/kdevelop.rst:6
msgid ""
"`KDevelop <https://www.kdevelop.org>`_ is a free, open source IDE for all "
"desktop platforms."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/kdevelop.rst:11
msgid "From the KDevelop's main screen select **Open Project**."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/kdevelop.rst:17
msgid "KDevelop's main screen."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/kdevelop.rst:19
msgid "Navigate to the Godot root folder and select it."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/kdevelop.rst:20
msgid ""
"On the next screen, choose **Custom Build System** for the **Project "
"Manager**."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/kdevelop.rst:26
msgid ""
"After the project has been imported, open the project configuration by right-"
"clicking on it in the **Projects** panel and selecting **Open Configuration.."
"** option."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/kdevelop.rst:33
msgid ""
"Under **Language Support** open the **Includes/Imports** tab and add the "
"following paths:"
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/kdevelop.rst:49
msgid "Apply the changes."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/kdevelop.rst:50
msgid ""
"Under **Custom Build System** add a new build configuration with the "
"following settings:"
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/kdevelop.rst:53
msgid "Build Directory"
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/kdevelop.rst:53
msgid "*blank*"
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/kdevelop.rst:55
msgid "Enable"
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/kdevelop.rst:55
msgid "**True**"
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/kdevelop.rst:57
msgid "Executable"
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/kdevelop.rst:57
#: ../../docs/contributing/development/configuring_an_ide/qt_creator.rst:59
msgid "**scons**"
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/kdevelop.rst:59
#: ../../docs/contributing/development/configuring_an_ide/qt_creator.rst:61
#: ../../docs/contributing/development/configuring_an_ide/xcode.rst:33
msgid ""
"See :ref:`doc_introduction_to_the_buildsystem` for a full list of arguments."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/kdevelop.rst:66
msgid "Apply the changes and close the configuration window."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/kdevelop.rst:69
#: ../../docs/contributing/development/configuring_an_ide/qt_creator.rst:73
#: ../../docs/contributing/development/configuring_an_ide/visual_studio.rst:32
#: ../../docs/contributing/development/configuring_an_ide/visual_studio_code.rst:62
#: ../../docs/contributing/development/configuring_an_ide/xcode.rst:71
#, fuzzy
msgid "Debugging the project"
msgstr "Kreiranje Sadržaja"

#: ../../docs/contributing/development/configuring_an_ide/kdevelop.rst:71
msgid "Select **Run > Configure Launches...** from the top menu."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/kdevelop.rst:77
msgid "Click **Add** to create a new launch configuration."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/kdevelop.rst:78
msgid ""
"Select **Executable** option and specify the path to your executable located "
"in the ``<Godot root directory>/bin`` folder. The name depends on your build "
"configuration, e.g. ``godot.linuxbsd.editor.dev.x86_64`` for 64-bit LinuxBSD "
"platform with ``platform=editor`` and ``dev_build=yes``."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/kdevelop.rst:87
#: ../../docs/contributing/development/configuring_an_ide/qt_creator.rst:111
#: ../../docs/contributing/development/configuring_an_ide/visual_studio.rst:69
#: ../../docs/contributing/development/configuring_an_ide/visual_studio_code.rst:159
#: ../../docs/contributing/development/configuring_an_ide/xcode.rst:108
#, fuzzy
msgid ""
"If you run into any issues, ask for help in one of `Godot's community "
"channels <https://godotengine.org/community>`__."
msgstr ""
"Takođe pogledajte `licencu na Godot sajtu <https://godotengine.org/"
"license>`_."

#: ../../docs/contributing/development/configuring_an_ide/qt_creator.rst:4
msgid "Qt Creator"
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/qt_creator.rst:6
msgid ""
"`Qt Creator <https://doc.qt.io/qtcreator/index.html>`_ is a free, open "
"source IDE for all desktop platforms."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/qt_creator.rst:11
msgid ""
"From the Qt Creator's main screen select **New Project > Import Project > "
"Import Existing Project**."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/qt_creator.rst:17
msgid "Under **Location** select the Godot root folder."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/qt_creator.rst:23
msgid ""
"Next, you can choose which folders and files will be visible to the project. "
"While C/C++ files are added automatically, other extensions can be "
"potentially useful: ``*.glsl`` for shader files, ``*.py`` for buildsystem "
"files, ``*.java`` for Android platform development, ``*.mm`` for macOS "
"platform development."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/qt_creator.rst:32
msgid ""
"You can change this configuration later by right-clicking on your project "
"and selecting the **Edit Files...** option."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/qt_creator.rst:40
msgid "Finish the import."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/qt_creator.rst:41
msgid ""
"Open the ``project_name.includes`` file and add a line containing ``.`` to "
"it to correctly enable the code completion."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/qt_creator.rst:48
msgid "From the left-side menu select **Projects** and open the **Build** tab."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/qt_creator.rst:49
msgid "Delete the predefined ``make`` build step."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/qt_creator.rst:55
msgid ""
"Click **Add Build Step > Custom Process Step** to add a new build step with "
"the following settings:"
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/qt_creator.rst:68
msgid ""
"If the build fails with ``Could not start process \"scons\"``, it can mean "
"that ``scons`` is not in your ``PATH`` environment variable. In this case, "
"you'll have to specify the full path to the SCons binary."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/qt_creator.rst:75
msgid "From the left-side menu select **Projects** and open the **Run** tab."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/qt_creator.rst:76
msgid ""
"Under **Executable** specify the path to your executable located in the "
"``<Godot root directory>/bin`` folder. The name depends on your build "
"configuration, e.g. ``godot.linuxbsd.editor.dev.x86_64`` for 64-bit LinuxBSD "
"platform with ``platform=editor`` and ``dev_build=yes``. You can use "
"``%{buildDir}`` to reference the project root, e.g: ``%{buildDir}/bin/godot."
"linuxbsd.editor.dev.x86_64``."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/qt_creator.rst:81
msgid ""
"If you want to run a specific project, specify its root folder under "
"**Working directory**."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/qt_creator.rst:82
msgid ""
"If you want to run the editor, add ``-e`` to the **Command line arguments** "
"field."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/qt_creator.rst:88
#: ../../docs/contributing/development/configuring_an_ide/visual_studio.rst:57
msgid ""
"To learn more about command line arguments, refer to the :ref:`command line "
"tutorial <doc_command_line_tutorial>`."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/qt_creator.rst:94
msgid ""
"Developers must follow the project's :ref:`code style "
"<doc_code_style_guidelines>` and the IDE should help them follow it. By "
"default, Qt Creator uses spaces for indentation which doesn't match the "
"Godot code style guidelines. You can change this behavior by changing the "
"**Code Style** in **Tools > Options > C++**."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/qt_creator.rst:103
msgid ""
"Click on **Edit** to change the current settings, then click on **Copy Built-"
"in Code Style** button to set a new code style. Set a name for it (e.g. "
"Godot) and change the Tab policy to be **Tabs Only**."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/rider.rst:4
msgid "Rider"
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/rider.rst:6
msgid ""
"`Rider <https://www.jetbrains.com/rider/>`_ is a commercial `JetBrains "
"<https://www.jetbrains.com/>`_ IDE for C# and C++ that uses the same "
"solution system as Visual Studio."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/rider.rst:12
msgid ""
"If you already use Visual Studio as your main IDE, you can use the same "
"solution file in Rider. Rider and Visual Studio use the same solution "
"format, so you can switch between the two IDEs without rebuilding the "
"solution file. Debug configurations need to be changed when going from one "
"IDE to another."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/rider.rst:16
msgid ""
"Rider requires a solution file to work on a project. While Godot does not "
"come with the solution file, it can be generated using SCons."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/rider.rst:19
#: ../../docs/contributing/development/configuring_an_ide/visual_studio.rst:17
msgid ""
"Navigate to the Godot root folder and open a Command Prompt or PowerShell "
"window."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/rider.rst:20
msgid "Copy, paste and run the next command to generate the solution."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/rider.rst:26
msgid ""
"The ``vsproj`` parameter signals that you want Visual Studio solution "
"generated. The ``dev_build`` parameter makes sure the debug symbols are "
"included, allowing to e.g. step through code using breakpoints."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/rider.rst:29
msgid ""
"If you have Rider setup as your main IDE for .sln, you can now open the "
"project by double-clicking on the ``godot.sln`` in the project root or by "
"using the **Open** option inside of Rider."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/rider.rst:32
msgid ""
"Rider could fail to build the first time you open the project. If that is "
"the case, you can close Rider and open the solution in Visual Studio, build "
"it, close Visual Studio, and open the solution in Rider again. You are now "
"able to build the project from Rider."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/rider.rst:38
msgid ""
"Rider comes with a built-in debugger that can be used to debug the Godot "
"project. You can launch the debugger by pressing the **Debug** icon at the "
"top of the screen, this only works for the Project manager, if you want to "
"debug the editor, you need to configure the debugger first."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/rider.rst:45
msgid ""
"Click on the **Godot > Edit Configurations** option at the top of the screen."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/rider.rst:50
msgid ""
"Delete what is under **Program arguments** and paste the following line:"
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/rider.rst:56
msgid ""
"This will tell the executable to debug the specified project without using "
"the project manager. Use the root path to the project folder, not ``project."
"godot`` file path."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/rider.rst:62
msgid "Finally click on apply and ok to save the changes."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/rider.rst:64
msgid ""
"You can now launch the debugger by pressing the **Debug** icon at the top of "
"the screen and it will open the project to debug."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/rider.rst:66
msgid ""
"Alternatively you can use **Run > Attach to Process** to attach the debugger "
"to a running Godot instance."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/visual_studio.rst:4
#, fuzzy
msgid "Visual Studio"
msgstr "Kreiranje Sadržaja"

#: ../../docs/contributing/development/configuring_an_ide/visual_studio.rst:6
msgid ""
"`Visual Studio Community <https://visualstudio.microsoft.com>`__ is a "
"Windows-only IDE by `Microsoft <https://microsoft.com>`_ that's free for "
"individual use or non-commercial use within organizations. It has many "
"useful features, such as memory view, performance view, source control and "
"more."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/visual_studio.rst:14
msgid ""
"Visual Studio requires a solution file to work on a project. While Godot "
"does not come with the solution file, it can be generated using SCons."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/visual_studio.rst:0
msgid ""
"Run ``scons platform=windows vsproj=yes dev_build=yes`` to generate the "
"solution with debug symbols."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/visual_studio.rst:0
msgid ""
"The ``vsproj`` parameter signals that you want Visual Studio solution "
"generated."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/visual_studio.rst:0
msgid ""
"The ``dev_build`` parameter makes sure the debug symbols are included, "
"allowing to e.g. step through code using breakpoints."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/visual_studio.rst:21
msgid ""
"You can now open the project by double-clicking on the ``godot.sln`` in the "
"project root or by using the **Open a project or solution** option inside of "
"the Visual Studio."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/visual_studio.rst:23
msgid "Use the **Build** top menu to build the project."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/visual_studio.rst:25
msgid ""
"Visual Studio must be configured with the C++ package. It can be selected in "
"the installer:"
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/visual_studio.rst:34
msgid ""
"Visual Studio features a powerful debugger. This allows the user to examine "
"Godot's source code, stop at specific points in the code, inspect the "
"current execution context, and make live changes to the codebase."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/visual_studio.rst:38
msgid ""
"You can launch the project with the debugger attached using the **Debug > "
"Start Debugging** option from the top menu. However, unless you want to "
"debug the Project Manager specifically, you'd need to configure debugging "
"options first. This is due to the fact that when the Godot Project Manager "
"opens a project, the initial process is terminated and the debugger gets "
"detached."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/visual_studio.rst:43
msgid ""
"To configure the launch options to use with the debugger use **Project > "
"Properties** from the top menu:"
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/visual_studio.rst:49
msgid ""
"Open the **Debugging** section and under **Command Arguments** add two new "
"arguments: the ``-e`` flag opens the editor instead of the Project Manager, "
"and the ``--path`` argument tells the executable to open the specified "
"project (must be provided as an *absolute* path to the project root, not the "
"``project.godot`` file; if the path contains spaces be sure to pass it "
"inside double quotation marks)."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/visual_studio.rst:60
msgid ""
"Even if you start the project without a debugger attached it can still be "
"connected to the running process using **Debug > Attach to Process...** menu."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/visual_studio.rst:63
msgid ""
"To check that everything is working, put a breakpoint in ``main.cpp`` and "
"press :kbd:`F5` to start debugging."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/visual_studio_code.rst:6
msgid ""
"`Visual Studio Code <https://code.visualstudio.com>`_ is a free cross-"
"platform code editor by `Microsoft <https://microsoft.com>`_ (not to be "
"confused with :ref:`doc_configuring_an_ide_vs`)."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/visual_studio_code.rst:12
msgid ""
"Make sure the C/C++ extension is installed. You can find instructions in the "
"`official documentation <https://code.visualstudio.com/docs/languages/"
"cpp>`_. Alternatively, `clangd <https://open-vsx.org/extension/llvm-vs-code-"
"extensions/vscode-clangd>`_ can be used instead."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/visual_studio_code.rst:16
msgid "When using the clangd extension, run ``scons compiledb=yes``."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/visual_studio_code.rst:17
msgid ""
"From the Visual Studio Code's main screen open the Godot root folder with "
"**File > Open Folder...**."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/visual_studio_code.rst:19
msgid ""
"Press :kbd:`Ctrl + Shift + P` to open the command prompt window and enter "
"*Configure Task*."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/visual_studio_code.rst:24
msgid "Select the **Create tasks.json file from template** option."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/visual_studio_code.rst:29
msgid "Then select **Others**."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/visual_studio_code.rst:34
msgid ""
"If there is no such option as **Create tasks.json file from template** "
"available, either delete the file if it already exists in your folder or "
"create a ``.vscode/tasks.json`` file manually. See `Tasks in Visual Studio "
"Code <https://code.visualstudio.com/docs/editor/tasks#_custom-tasks>`_ for "
"more details on tasks."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/visual_studio_code.rst:36
msgid ""
"Within the ``tasks.json`` file find the ``\"tasks\"`` array and add a new "
"section to it:"
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/visual_studio_code.rst:56
msgid "An example of a filled out ``tasks.json``."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/visual_studio_code.rst:58
msgid ""
"Arguments can be different based on your own setup and needs. See :ref:"
"`doc_introduction_to_the_buildsystem` for a full list of arguments."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/visual_studio_code.rst:64
msgid ""
"To run and debug the project you need to create a new configuration in the "
"``launch.json`` file."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/visual_studio_code.rst:66
msgid "Press :kbd:`Ctrl + Shift + D` to open the Run panel."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/visual_studio_code.rst:67
msgid ""
"If ``launch.json`` file is missing you will be prompted to create a new one."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/visual_studio_code.rst:72
msgid ""
"Select **C++ (GDB/LLDB)**. There may be another platform specific option "
"here. If selected, adjust the configuration example provided accordingly."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/visual_studio_code.rst:74
msgid ""
"Within the ``launch.json`` file find the ``\"configurations\"`` array and "
"add a new section to it:"
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/visual_studio_code.rst:142
msgid "An example of a filled out ``launch.json``."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/visual_studio_code.rst:147
msgid ""
"Due to sporadic performance issues, it is recommended to use LLDB over GDB "
"on Unix-based systems. Make sure that the `CodeLLDB extension <https://"
"marketplace.visualstudio.com/items?itemName=vadimcn.vscode-lldb>`_ is "
"installed."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/visual_studio_code.rst:151
msgid ""
"If you encounter issues with lldb, you may consider using gdb (see the "
"LinuxBSD_gdb configuration)."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/visual_studio_code.rst:153
msgid ""
"Do note that lldb may work better with LLVM-based builds. See :ref:"
"`doc_compiling_for_linuxbsd` for further information."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/visual_studio_code.rst:155
msgid ""
"The name under ``program`` depends on your build configuration, e.g. ``godot."
"linuxbsd.editor.dev.x86_64`` for 64-bit LinuxBSD platform with "
"``target=editor`` and ``dev_build=yes``."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/visual_studio_code.rst:164
msgid ""
"To get linting on class reference XML files, install the `vscode-xml "
"extension <https://marketplace.visualstudio.com/items?itemName=redhat.vscode-"
"xml>`__."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/xcode.rst:4
msgid "Xcode"
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/xcode.rst:6
msgid ""
"`Xcode <https://developer.apple.com/xcode>`_ is a free macOS-only IDE. You "
"can download it from the Mac App Store."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/xcode.rst:12
msgid ""
"From Xcode's main screen create a new project using the **Other > External "
"Build System** template."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/xcode.rst:18
msgid ""
"Now choose a name for your project and set the path to scons executable in "
"build tool (to find the path you can type ``where scons`` in a terminal)."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/xcode.rst:24
msgid ""
"Open the main target from the **Targets** section and select the **Info** "
"tab."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/xcode.rst:30
#, fuzzy
msgid "Fill out the form with the following settings:"
msgstr "Glavna dokumentacija za sajt je podeljena na sledeća poglavlja:"

#: ../../docs/contributing/development/configuring_an_ide/xcode.rst:35
msgid "Directory"
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/xcode.rst:35
msgid "A full path to the Godot root folder"
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/xcode.rst:38
msgid ""
"Add a Command Line Tool target which will be used for indexing the project "
"by choosing **File > New > Target...**."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/xcode.rst:45
msgid "Select **macOS > Application > Command Line Tool**."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/xcode.rst:51
msgid ""
"Name it something so you know not to compile with this target (e.g. "
"``GodotXcodeIndex``)."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/xcode.rst:53
msgid ""
"For this target open the **Build Settings** tab and look for **Header Search "
"Paths**."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/xcode.rst:54
msgid ""
"Set **Header Search Paths** to the absolute path to the Godot root folder. "
"You need to include subdirectories as well. To achieve that, add two two "
"asterisks (``**``) to the end of the path, e.g. ``/Users/me/repos/godot-"
"source/**``."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/xcode.rst:58
msgid ""
"Add the Godot source to the project by dragging and dropping it into the "
"project file browser."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/xcode.rst:59
msgid ""
"Select **Create groups** for the **Added folders** option and check *only* "
"your command line indexing target in the **Add to targets** section."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/xcode.rst:66
msgid "Xcode will now index the files. This may take a few minutes."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/xcode.rst:67
msgid ""
"Once Xcode is done indexing, you should have jump-to-definition, "
"autocompletion, and full syntax highlighting."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/xcode.rst:73
msgid ""
"To enable debugging support you need to edit the external build target's "
"build and run schemes."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/xcode.rst:75
msgid "Open the scheme editor of the external build target."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/xcode.rst:76
msgid "Locate the **Build > Post Actions** section."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/xcode.rst:77
msgid "Add a new script run action"
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/xcode.rst:78
msgid ""
"Under **Provide build settings from** select your project. This allows to "
"reference the project directory within the script."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/xcode.rst:80
msgid ""
"Create a script that will give the binary a name that Xcode can recognize, e."
"g.:"
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/xcode.rst:90
msgid "Build the external build target."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/xcode.rst:92
msgid "Open the scheme editor again and select **Run**."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/xcode.rst:98
msgid ""
"Set the **Executable** to the file you linked in your post-build action "
"script."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/xcode.rst:99
msgid "Check **Debug executable**."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/xcode.rst:100
msgid ""
"You can add two arguments on the **Arguments** tab: the ``-e`` flag opens "
"the editor instead of the Project Manager, and the ``--path`` argument tells "
"the executable to open the specified project (must be provided as an "
"*absolute* path to the project root, not the ``project.godot`` file)."
msgstr ""

#: ../../docs/contributing/development/configuring_an_ide/xcode.rst:105
msgid ""
"To check that everything is working, put a breakpoint in ``platform/macos/"
"godot_main_macos.mm`` and run the project."
msgstr ""

#: ../../docs/contributing/development/compiling/index.rst:2
#, fuzzy
msgid "Building from source"
msgstr "Kreiranje Sadržaja"

#: ../../docs/contributing/development/compiling/index.rst:6
msgid ""
"Godot prides itself on being very easy to build, by C++ projects' "
"standards. :ref:`Godot uses the SCons build system <doc_faq_why_scons>`, and "
"after the initial setup compiling the engine for your current platform "
"should be as easy as running::"
msgstr ""

#: ../../docs/contributing/development/compiling/index.rst:12
msgid ""
"But you will probably need to use at least some of the available options to "
"configure the build to match your specific needs, be it a custom engine "
"fork, a lightweight build stripped of extra modules, or an executable "
"targetting engine development."
msgstr ""

#: ../../docs/contributing/development/compiling/index.rst:16
msgid ""
"The articles below should help you navigate configuration options available, "
"as well as prerequisites required to compile Godot exactly the way you need."
msgstr ""

#: ../../docs/contributing/development/compiling/index.rst:20
msgid "Basics of building Godot"
msgstr ""

#: ../../docs/contributing/development/compiling/index.rst:22
msgid ""
"Let's start with basics, and learn how to get Godot's source code, and then "
"which options to use to compile it regardless of your target platform."
msgstr ""

#: ../../docs/contributing/development/compiling/index.rst:33
#, fuzzy
msgid "Building for target platforms"
msgstr "Kreiranje Sadržaja"

#: ../../docs/contributing/development/compiling/index.rst:35
msgid ""
"Below you can find instructions for compiling the engine for your specific "
"target platform. Note that Godot supports cross-compilation, which means you "
"can compile it for a target platform that doesn't match your current "
"platform (say, target Linux while being on Windows). The guides will try "
"their best to cover all possible situations."
msgstr ""

#: ../../docs/contributing/development/compiling/index.rst:53
msgid "Other compilation targets and options"
msgstr ""

#: ../../docs/contributing/development/compiling/index.rst:55
msgid ""
"Some additional universal compilation options require further setup. Namely, "
"while Godot does have C#/.NET support as a part of its main codebase, it "
"does not get compiled by default to reduce the executable size for users who "
"don't need C# for their projects."
msgstr ""

#: ../../docs/contributing/development/compiling/index.rst:59
msgid ""
"Articles below explain how to configure the buildsystem for cases like this, "
"and also cover some optimization techniques."
msgstr ""

#: ../../docs/contributing/development/compiling/getting_source.rst:4
msgid "Getting the source"
msgstr ""

#: ../../docs/contributing/development/compiling/getting_source.rst:9
msgid "Downloading the Godot source code"
msgstr ""

#: ../../docs/contributing/development/compiling/getting_source.rst:11
msgid ""
"Before :ref:`getting into the SCons build system "
"<doc_introduction_to_the_buildsystem>` and compiling Godot, you need to "
"actually download the Godot source code."
msgstr ""

#: ../../docs/contributing/development/compiling/getting_source.rst:14
msgid ""
"The source code is available on `GitHub <https://github.com/godotengine/"
"godot>`__ and while you can manually download it via the website, in general "
"you want to do it via the ``git`` version control system."
msgstr ""

#: ../../docs/contributing/development/compiling/getting_source.rst:18
msgid ""
"If you are compiling in order to make contributions or pull requests, you "
"should follow the instructions from the :ref:`Pull Request workflow "
"<doc_pr_workflow>`."
msgstr ""

#: ../../docs/contributing/development/compiling/getting_source.rst:21
msgid ""
"If you don't know much about ``git`` yet, there are a great number of "
"`tutorials <https://git-scm.com/book>`__ available on various websites."
msgstr ""

#: ../../docs/contributing/development/compiling/getting_source.rst:24
msgid ""
"In general, you need to install ``git`` and/or one of the various GUI "
"clients."
msgstr ""

#: ../../docs/contributing/development/compiling/getting_source.rst:26
msgid ""
"Afterwards, to get the latest development version of the Godot source code "
"(the unstable ``master`` branch), you can use ``git clone``."
msgstr ""

#: ../../docs/contributing/development/compiling/getting_source.rst:29
msgid ""
"If you are using the ``git`` command line client, this is done by entering "
"the following in a terminal:"
msgstr ""

#: ../../docs/contributing/development/compiling/getting_source.rst:38
msgid ""
"For any stable release, visit the `release page <https://github.com/"
"godotengine/godot/releases>`__ and click on the link for the release you "
"want. You can then download and extract the source from the download link on "
"the page."
msgstr ""

#: ../../docs/contributing/development/compiling/getting_source.rst:42
msgid ""
"With ``git``, you can also clone a stable release by specifying its branch "
"or tag after the ``--branch`` (or just ``-b``) argument::"
msgstr ""

#: ../../docs/contributing/development/compiling/getting_source.rst:51
msgid ""
"There are also generally branches besides ``master`` for each major version."
msgstr ""

#: ../../docs/contributing/development/compiling/getting_source.rst:53
msgid ""
"After downloading the Godot source code, you can :ref:`continue to compiling "
"Godot <doc_introduction_to_the_buildsystem>`."
msgstr ""

#: ../../docs/contributing/development/compiling/introduction_to_the_buildsystem.rst:4
msgid "Introduction to the buildsystem"
msgstr ""

#: ../../docs/contributing/development/compiling/introduction_to_the_buildsystem.rst:9
msgid ""
"Godot is a primarily C++ project and it :ref:`uses the SCons build system. "
"<doc_faq_why_scons>` We love SCons for how maintainable and easy to set up "
"it makes our buildsystem. And thanks to that compiling Godot from source can "
"be as simple as running::"
msgstr ""

#: ../../docs/contributing/development/compiling/introduction_to_the_buildsystem.rst:15
msgid ""
"This produces an *export template* for your current platform, operating "
"system, and architecture. An export template is a build of the engine that "
"is used for running exported projects. To build the *editor* instead you can "
"run the following command::"
msgstr ""

#: ../../docs/contributing/development/compiling/introduction_to_the_buildsystem.rst:21
msgid ""
"If you plan to debug or develop the engine, then you might want to add "
"another option to the command::"
msgstr ""

#: ../../docs/contributing/development/compiling/introduction_to_the_buildsystem.rst:26
msgid ""
"Following sections in the article will explain these and other universal "
"options in more detail. But before you can compile Godot, you need to "
"install a few prerequisites. Please refer to the platform documentation to "
"learn more:"
msgstr ""

#: ../../docs/contributing/development/compiling/introduction_to_the_buildsystem.rst:30
#, fuzzy
msgid ":ref:`doc_compiling_for_android`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/contributing/development/compiling/introduction_to_the_buildsystem.rst:31
#, fuzzy
msgid ":ref:`doc_compiling_for_ios`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/contributing/development/compiling/introduction_to_the_buildsystem.rst:32
#, fuzzy
msgid ":ref:`doc_compiling_for_linuxbsd`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/contributing/development/compiling/introduction_to_the_buildsystem.rst:33
#, fuzzy
msgid ":ref:`doc_compiling_for_macos`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/contributing/development/compiling/introduction_to_the_buildsystem.rst:34
#, fuzzy
msgid ":ref:`doc_compiling_for_web`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/contributing/development/compiling/introduction_to_the_buildsystem.rst:35
#, fuzzy
msgid ":ref:`doc_compiling_for_windows`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/contributing/development/compiling/introduction_to_the_buildsystem.rst:37
msgid ""
"These articles cover in great detail both how to setup your environment to "
"compile Godot on a specific platform, and how to compile for that platform. "
"Please feel free to go back and forth between them and this article to "
"reference platform-specific and universal configuration options."
msgstr ""

#: ../../docs/contributing/development/compiling/introduction_to_the_buildsystem.rst:42
#, fuzzy
msgid "Using multi-threading"
msgstr "Kreiranje Sadržaja"

#: ../../docs/contributing/development/compiling/introduction_to_the_buildsystem.rst:44
msgid ""
"The build process may take a while, depending on how powerful your system "
"is. By default, Godot's SCons setup is configured to use all CPU threads but "
"one (to keep the system responsive during compilation). If you want to "
"adjust how many CPU threads SCons will use, use the ``-j <threads>`` "
"parameter to specify how many threads will be used for the build."
msgstr ""

#: ../../docs/contributing/development/compiling/introduction_to_the_buildsystem.rst:49
msgid "Example for using 4 threads::"
msgstr ""

#: ../../docs/contributing/development/compiling/introduction_to_the_buildsystem.rst:54
msgid "Platform selection"
msgstr ""

#: ../../docs/contributing/development/compiling/introduction_to_the_buildsystem.rst:56
msgid ""
"Godot's build system will begin by detecting the platforms it can build for. "
"If not detected, the platform will simply not appear on the list of "
"available platforms. The build requirements for each platform are described "
"in the rest of this tutorial section."
msgstr ""

#: ../../docs/contributing/development/compiling/introduction_to_the_buildsystem.rst:61
msgid ""
"SCons is invoked by just calling ``scons``. If no platform is specified, "
"SCons will detect the target platform automatically based on the host "
"platform. It will then start building for the target platform right away."
msgstr ""

#: ../../docs/contributing/development/compiling/introduction_to_the_buildsystem.rst:65
msgid "To list the available target platforms, use ``scons platform=list``::"
msgstr ""

#: ../../docs/contributing/development/compiling/introduction_to_the_buildsystem.rst:79
msgid ""
"To build for a platform (for example, ``linuxbsd``), run with the "
"``platform=`` (or ``p=`` to make it short) argument:"
msgstr ""

#: ../../docs/contributing/development/compiling/introduction_to_the_buildsystem.rst:89
msgid "Resulting binary"
msgstr ""

#: ../../docs/contributing/development/compiling/introduction_to_the_buildsystem.rst:91
msgid ""
"The resulting binaries will be placed in the ``bin/`` subdirectory, "
"generally with this naming convention::"
msgstr ""

#: ../../docs/contributing/development/compiling/introduction_to_the_buildsystem.rst:96
msgid "For the previous build attempt, the result would look like this:"
msgstr ""

#: ../../docs/contributing/development/compiling/introduction_to_the_buildsystem.rst:103
msgid ""
"This means that the binary is for Linux *or* \\*BSD (*not* both), is not "
"optimized, has the whole editor compiled in, and is meant for 64 bits."
msgstr ""

#: ../../docs/contributing/development/compiling/introduction_to_the_buildsystem.rst:106
msgid "A Windows binary with the same configuration will look like this:"
msgstr ""

#: ../../docs/contributing/development/compiling/introduction_to_the_buildsystem.rst:113
msgid ""
"Copy that binary to any location you like, as it contains the Project "
"Manager, editor and all means to execute the game. However, it lacks the "
"data to export it to the different platforms. For that the export templates "
"are needed (which can be either downloaded from `godotengine.org <https://"
"godotengine.org/>`__, or you can build them yourself)."
msgstr ""

#: ../../docs/contributing/development/compiling/introduction_to_the_buildsystem.rst:119
msgid ""
"Aside from that, there are a few standard options that can be set in all "
"build targets, and which will be explained below."
msgstr ""

#: ../../docs/contributing/development/compiling/introduction_to_the_buildsystem.rst:125
msgid "Target"
msgstr ""

#: ../../docs/contributing/development/compiling/introduction_to_the_buildsystem.rst:127
msgid ""
"Target controls if the editor is contained and debug flags are used. All "
"builds are optimized. Each mode means:"
msgstr ""

#: ../../docs/contributing/development/compiling/introduction_to_the_buildsystem.rst:130
msgid ""
"``target=editor``: Build with editor, optimized, with debugging code "
"(defines: ``TOOLS_ENABLED``, ``DEBUG_ENABLED``, ``-O2``/``/O2``)"
msgstr ""

#: ../../docs/contributing/development/compiling/introduction_to_the_buildsystem.rst:131
msgid ""
"``target=template_debug``: Build with C++ debugging symbols (defines: "
"``DEBUG_ENABLED``, ``-O2``/``/O2``)"
msgstr ""

#: ../../docs/contributing/development/compiling/introduction_to_the_buildsystem.rst:132
msgid ""
"``target=template_release``: Build without symbols (defines: ``-O3``/``/O2``)"
msgstr ""

#: ../../docs/contributing/development/compiling/introduction_to_the_buildsystem.rst:134
msgid ""
"The editor is enabled by default in all PC targets (Linux, Windows, macOS), "
"disabled for everything else. Disabling the editor produces a binary that "
"can run projects but does not include the editor or the Project Manager."
msgstr ""

#: ../../docs/contributing/development/compiling/introduction_to_the_buildsystem.rst:143
#, fuzzy
msgid "Development and production aliases"
msgstr "Razvoj"

#: ../../docs/contributing/development/compiling/introduction_to_the_buildsystem.rst:145
msgid ""
"When creating builds for development (running debugging/:ref:`profiling "
"<doc_using_cpp_profilers>` tools), you often have different goals compared "
"to production builds (making binaries as fast and small as possible)."
msgstr ""

#: ../../docs/contributing/development/compiling/introduction_to_the_buildsystem.rst:149
msgid "Godot provides two aliases for this purpose:"
msgstr ""

#: ../../docs/contributing/development/compiling/introduction_to_the_buildsystem.rst:151
msgid ""
"``dev_mode=yes`` is an alias for ``verbose=yes warnings=extra werror=yes "
"tests=yes``. This enables warnings-as-errors behavior (similar to Godot's "
"continuous integration setup) and also builds :ref:`unit tests "
"<doc_unit_testing>` so you can run them locally."
msgstr ""

#: ../../docs/contributing/development/compiling/introduction_to_the_buildsystem.rst:155
msgid ""
"``production=yes`` is an alias for ``use_static_cpp=yes debug_symbols=no "
"lto=auto``. Statically linking libstdc++ allows for better binary "
"portability when compiling for Linux. This alias also enables link-time "
"optimization when compiling for Linux, Web and Windows with MinGW, but keeps "
"LTO disabled when compiling for macOS, iOS or Windows with MSVC. This is "
"because LTO on those platforms is very slow to link or has issues with the "
"generated code."
msgstr ""

#: ../../docs/contributing/development/compiling/introduction_to_the_buildsystem.rst:162
msgid ""
"You can manually override options from those aliases by specifying them on "
"the same command line with different values. For example, you can use "
"``scons production=yes debug_symbols=yes`` to create production-optimized "
"binaries with debugging symbols included."
msgstr ""

#: ../../docs/contributing/development/compiling/introduction_to_the_buildsystem.rst:168
msgid "Dev build"
msgstr ""

#: ../../docs/contributing/development/compiling/introduction_to_the_buildsystem.rst:172
msgid ""
"``dev_build`` should **not** be confused with ``dev_mode``, which is an "
"alias for several development-related options (see above)."
msgstr ""

#: ../../docs/contributing/development/compiling/introduction_to_the_buildsystem.rst:175
msgid ""
"When doing engine development the ``dev_build`` option can be used together "
"with ``target`` to enable dev-specific code. ``dev_build`` defines "
"``DEV_ENABLED``, disables optimization (``-O0``/``/0d``), enables generating "
"debug symbols, and does not define ``NDEBUG`` (so ``assert()`` works in "
"thirdparty libraries)."
msgstr ""

#: ../../docs/contributing/development/compiling/introduction_to_the_buildsystem.rst:184
msgid ""
"This flag appends the ``.dev`` suffix (for development) to the generated "
"binary name."
msgstr ""

#: ../../docs/contributing/development/compiling/introduction_to_the_buildsystem.rst:189
msgid ""
"There are additional SCons options to enable *sanitizers*, which are tools "
"you can enable at compile-time to better debug certain engine issues. See :"
"ref:`doc_using_sanitizers` for more information."
msgstr ""

#: ../../docs/contributing/development/compiling/introduction_to_the_buildsystem.rst:194
#, fuzzy
msgid "Debugging symbols"
msgstr "Kreiranje Sadržaja"

#: ../../docs/contributing/development/compiling/introduction_to_the_buildsystem.rst:196
msgid ""
"By default, ``debug_symbols=no`` is used, which means **no** debugging "
"symbols are included in compiled binaries. Use ``debug_symbols=yes`` to "
"include debug symbols within compiled binaries, which allows debuggers and "
"profilers to work correctly. Debugging symbols are also required for Godot's "
"crash stacktraces to display with references to source code files and lines."
msgstr ""

#: ../../docs/contributing/development/compiling/introduction_to_the_buildsystem.rst:202
msgid ""
"The downside is that debugging symbols are large files (significantly larger "
"than the binaries themselves). As a result, official binaries currently do "
"not include debugging symbols. This means you need to compile Godot yourself "
"to have access to debugging symbols."
msgstr ""

#: ../../docs/contributing/development/compiling/introduction_to_the_buildsystem.rst:207
msgid ""
"When using ``debug_symbols=yes``, you can also use "
"``separate_debug_symbols=yes`` to put debug information in a separate file "
"with a ``.debug`` suffix. This allows distributing both files independently. "
"Note that on Windows, when compiling with MSVC, debugging information is "
"*always* written to a separate ``.pdb`` file regardless of "
"``separate_debug_symbols``."
msgstr ""

#: ../../docs/contributing/development/compiling/introduction_to_the_buildsystem.rst:215
msgid ""
"Use the ``strip <path/to/binary>`` command to remove debugging symbols from "
"a binary you've already compiled."
msgstr ""

#: ../../docs/contributing/development/compiling/introduction_to_the_buildsystem.rst:219
msgid "Optimization level"
msgstr ""

#: ../../docs/contributing/development/compiling/introduction_to_the_buildsystem.rst:221
msgid "Several compiler optimization levels can be chosen from:"
msgstr ""

#: ../../docs/contributing/development/compiling/introduction_to_the_buildsystem.rst:223
msgid ""
"``optimize=speed_trace`` *(default when targeting non-Web platforms)*: "
"Favors execution speed at the cost of larger binary size. Optimizations may "
"sometimes negatively impact debugger usage (stack traces may be less "
"accurate. If this occurs to you, use ``optimize=debug`` instead."
msgstr ""

#: ../../docs/contributing/development/compiling/introduction_to_the_buildsystem.rst:227
msgid ""
"``optimize=speed``: Favors even more execution speed, at the cost of even "
"larger binary size compared to ``optimize=speed_trace``. Even less friendly "
"to debugging compared to ``optimize=debug``, as this uses the most "
"aggressive optimizations available."
msgstr ""

#: ../../docs/contributing/development/compiling/introduction_to_the_buildsystem.rst:231
msgid ""
"``optimize=size`` *(default when targeting the Web platform)*: Favors small "
"binaries at the cost of slower execution speed."
msgstr ""

#: ../../docs/contributing/development/compiling/introduction_to_the_buildsystem.rst:233
msgid ""
"``optimize=debug``: Only enables optimizations that do not impact debugging "
"in any way. This results in faster binaries than ``optimize=none``, but "
"slower binaries than ``optimize=speed_trace``."
msgstr ""

#: ../../docs/contributing/development/compiling/introduction_to_the_buildsystem.rst:236
msgid ""
"``optimize=none``: Do not perform any optimization. This provides the "
"fastest build times, but the slowest execution times."
msgstr ""

#: ../../docs/contributing/development/compiling/introduction_to_the_buildsystem.rst:238
msgid ""
"``optimize=custom`` *(advanced users only)*: Do not pass optimization "
"arguments to the C/C++ compilers. You will have to pass arguments manually "
"using the ``CFLAGS``, ``CCFLAGS`` and ``CXXFLAGS`` SCons options."
msgstr ""

#: ../../docs/contributing/development/compiling/introduction_to_the_buildsystem.rst:243
msgid "Architecture"
msgstr ""

#: ../../docs/contributing/development/compiling/introduction_to_the_buildsystem.rst:245
msgid ""
"The ``arch`` option is meant to control the CPU or OS version intended to "
"run the binaries. It is focused mostly on desktop platforms and ignored "
"everywhere else."
msgstr ""

#: ../../docs/contributing/development/compiling/introduction_to_the_buildsystem.rst:249
msgid ""
"Supported values for the ``arch`` option are **auto**, **x86_32**, "
"**x86_64**, **arm32**, **arm64**, **rv64**, **ppc32**, **ppc64** and "
"**wasm32**."
msgstr ""

#: ../../docs/contributing/development/compiling/introduction_to_the_buildsystem.rst:256
msgid ""
"This flag appends the value of ``arch`` to resulting binaries when "
"relevant.  The default value ``arch=auto`` detects the architecture that "
"matches the host platform."
msgstr ""

#: ../../docs/contributing/development/compiling/introduction_to_the_buildsystem.rst:263
msgid "Custom modules"
msgstr ""

#: ../../docs/contributing/development/compiling/introduction_to_the_buildsystem.rst:265
msgid ""
"It's possible to compile modules residing outside of Godot's directory tree, "
"along with the built-in modules."
msgstr ""

#: ../../docs/contributing/development/compiling/introduction_to_the_buildsystem.rst:268
msgid ""
"A ``custom_modules`` build option can be passed to the command line before "
"compiling. The option represents a comma-separated list of directory paths "
"containing a collection of independent C++ modules that can be seen as C++ "
"packages, just like the built-in ``modules/`` directory."
msgstr ""

#: ../../docs/contributing/development/compiling/introduction_to_the_buildsystem.rst:273
msgid ""
"For instance, it's possible to provide both relative, absolute, and user "
"directory paths containing such modules:"
msgstr ""

#: ../../docs/contributing/development/compiling/introduction_to_the_buildsystem.rst:282
msgid ""
"If there's any custom module with the exact directory name as a built-in "
"module, the engine will only compile the custom one. This logic can be used "
"to override built-in module implementations."
msgstr ""

#: ../../docs/contributing/development/compiling/introduction_to_the_buildsystem.rst:288
#, fuzzy
msgid ":ref:`doc_custom_modules_in_cpp`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/contributing/development/compiling/introduction_to_the_buildsystem.rst:291
#, fuzzy
msgid "Cleaning generated files"
msgstr "Kreiranje Sadržaja"

#: ../../docs/contributing/development/compiling/introduction_to_the_buildsystem.rst:293
msgid ""
"Sometimes, you may encounter an error due to generated files being present. "
"You can remove them by using ``scons --clean <options>``, where "
"``<options>`` is the list of build options you've used to build Godot "
"previously."
msgstr ""

#: ../../docs/contributing/development/compiling/introduction_to_the_buildsystem.rst:297
msgid ""
"Alternatively, you can use ``git clean -fixd`` which will clean build "
"artifacts for all platforms and configurations. Beware, as this will remove "
"all untracked and ignored files in the repository. Don't run this command if "
"you have uncommitted work!"
msgstr ""

#: ../../docs/contributing/development/compiling/introduction_to_the_buildsystem.rst:303
msgid "Other build options"
msgstr ""

#: ../../docs/contributing/development/compiling/introduction_to_the_buildsystem.rst:305
msgid ""
"There are several other build options that you can use to configure the way "
"Godot should be built (compiler, debug options, etc.) as well as the "
"features to include/disable."
msgstr ""

#: ../../docs/contributing/development/compiling/introduction_to_the_buildsystem.rst:309
msgid ""
"Check the output of ``scons --help`` for details about each option for the "
"version you are willing to compile."
msgstr ""

#: ../../docs/contributing/development/compiling/introduction_to_the_buildsystem.rst:315
msgid "Overriding the build options"
msgstr ""

#: ../../docs/contributing/development/compiling/introduction_to_the_buildsystem.rst:318
#, fuzzy
msgid "Using a file"
msgstr "Kreiranje Sadržaja"

#: ../../docs/contributing/development/compiling/introduction_to_the_buildsystem.rst:320
msgid ""
"The default ``custom.py`` file can be created at the root of the Godot "
"Engine source to initialize any SCons build options passed via the command "
"line:"
msgstr ""

#: ../../docs/contributing/development/compiling/introduction_to_the_buildsystem.rst:332
msgid ""
"You can also disable some of the builtin modules before compiling, saving "
"some time it takes to build the engine. See :ref:`doc_optimizing_for_size` "
"page for more details."
msgstr ""

#: ../../docs/contributing/development/compiling/introduction_to_the_buildsystem.rst:337
msgid ""
"You can use the online `Godot build options generator <https://godot-build-"
"options-generator.github.io/>`__ to generate a ``custom.py`` file containing "
"SCons options. You can then save this file and place it at the root of your "
"Godot source directory."
msgstr ""

#: ../../docs/contributing/development/compiling/introduction_to_the_buildsystem.rst:342
msgid ""
"Another custom file can be specified explicitly with the ``profile`` command "
"line option, both overriding the default build configuration:"
msgstr ""

#: ../../docs/contributing/development/compiling/introduction_to_the_buildsystem.rst:349
msgid ""
"Build options set from the file can be overridden by the command line "
"options."
msgstr ""

#: ../../docs/contributing/development/compiling/introduction_to_the_buildsystem.rst:352
msgid "It's also possible to override the options conditionally:"
msgstr ""

#: ../../docs/contributing/development/compiling/introduction_to_the_buildsystem.rst:367
msgid "Using the SCONSFLAGS"
msgstr ""

#: ../../docs/contributing/development/compiling/introduction_to_the_buildsystem.rst:369
msgid ""
"``SCONSFLAGS`` is an environment variable which is used by the SCons to set "
"the options automatically without having to supply them via the command line."
msgstr ""

#: ../../docs/contributing/development/compiling/introduction_to_the_buildsystem.rst:372
msgid ""
"For instance, you may want to force a number of CPU threads with the "
"aforementioned ``-j`` option for all future builds:"
msgstr ""

#: ../../docs/contributing/development/compiling/introduction_to_the_buildsystem.rst:389
msgid "SCU (single compilation unit) build"
msgstr ""

#: ../../docs/contributing/development/compiling/introduction_to_the_buildsystem.rst:391
msgid ""
"Regular builds tend to be bottlenecked by including large numbers of headers "
"in each compilation translation unit. Primarily to speed up development "
"(rather than for production builds), Godot offers a \"single compilation "
"unit\" build (aka \"Unity / Jumbo\" build)."
msgstr ""

#: ../../docs/contributing/development/compiling/introduction_to_the_buildsystem.rst:396
msgid ""
"For the folders accelerated by this option, multiple ``.cpp`` files are "
"compiled in each translation unit, so headers can be shared between multiple "
"files, which can dramatically decrease build times."
msgstr ""

#: ../../docs/contributing/development/compiling/introduction_to_the_buildsystem.rst:400
msgid "To make a SCU build, use the ``scu_build=yes`` SCons option."
msgstr ""

#: ../../docs/contributing/development/compiling/introduction_to_the_buildsystem.rst:402
msgid ""
"When developing a Pull Request using SCU builds, be sure to make a regular "
"build prior to submitting the PR. This is because SCU builds by nature "
"include headers from earlier ``.cpp`` files in the translation unit, "
"therefore won't catch all the includes you will need in a regular build. The "
"CI will catch these errors but it will usually be faster to catch them on a "
"local build on your machine."
msgstr ""

#: ../../docs/contributing/development/compiling/introduction_to_the_buildsystem.rst:412
msgid ""
"Official export templates are downloaded from the Godot Engine site: "
"`godotengine.org <https://godotengine.org/>`__. However, you might want to "
"build them yourself (in case you want newer ones, you are using custom "
"modules, or simply don't trust your own shadow)."
msgstr ""

#: ../../docs/contributing/development/compiling/introduction_to_the_buildsystem.rst:417
msgid ""
"If you download the official export templates package and unzip it, you will "
"notice that most files are optimized binaries or packages for each platform:"
msgstr ""

#: ../../docs/contributing/development/compiling/introduction_to_the_buildsystem.rst:440
msgid ""
"To create those yourself, follow the instructions detailed for each platform "
"in this same tutorial section. Each platform explains how to create its own "
"template."
msgstr ""

#: ../../docs/contributing/development/compiling/introduction_to_the_buildsystem.rst:444
msgid ""
"The ``version.txt`` file should contain the corresponding Godot version "
"identifier. This file is used to install export templates in a version-"
"specific directory to avoid conflicts. For instance, if you are building "
"export templates for Godot 3.1.1, ``version.txt`` should contain ``3.1.1."
"stable`` on the first line (and nothing else). This version identifier is "
"based on the ``major``, ``minor``, ``patch`` (if present) and ``status`` "
"lines of the `version.py file in the Godot Git repository <https://github."
"com/godotengine/godot/blob/master/version.py>`__."
msgstr ""

#: ../../docs/contributing/development/compiling/introduction_to_the_buildsystem.rst:452
msgid ""
"If you are developing for multiple platforms, macOS is definitely the most "
"convenient host platform for cross-compilation, since you can cross-compile "
"for every target. Linux and Windows come in second place, but Linux has the "
"advantage of being the easier platform to set this up."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_windows.rst:4
msgid "Compiling for Windows"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_windows.rst:10
msgid ""
"This page describes how to compile Windows editor and export template "
"binaries from source. If you're looking to export your project to Windows "
"instead, read :ref:`doc_exporting_for_windows`."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_windows.rst:16
msgid "For compiling under Windows, the following is required:"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_windows.rst:18
msgid ""
"`Visual Studio Community <https://www.visualstudio.com/vs/community/>`_, "
"version 2017 or later. VS 2019 is recommended. **Make sure to read "
"\"Installing Visual Studio caveats\" below or you will have to run/download "
"the installer again.**"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_windows.rst:22
msgid ""
"`MinGW-w64 <https://mingw-w64.org/>`_ with GCC can be used as an alternative "
"to Visual Studio. Be sure to install/configure it to use the ``posix`` "
"thread model. **Important:** When using MinGW to compile the ``master`` "
"branch, you need GCC 9 or later."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_windows.rst:25
msgid ""
"`Python 3.6+ <https://www.python.org/downloads/windows/>`_. **Make sure to "
"enable the option to add Python to the ``PATH`` in the installer.**"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_windows.rst:27
msgid ""
"`SCons 3.0+ <https://scons.org/pages/download.html>`_ build system. Using "
"the latest release is recommended, especially for proper support of recent "
"Visual Studio releases."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_windows.rst:31
msgid ""
"If you have `Scoop <https://scoop.sh/>`_ installed, you can easily install "
"MinGW and other dependencies using the following command::"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_windows.rst:36
msgid ""
"If you have `MSYS2 <https://www.msys2.org/>`_ installed, you can easily "
"install MinGW and other dependencies using the following command::"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_windows.rst:42
msgid ""
"For each MSYS2 MinGW subsystem, you should then run `pip3 install scons` in "
"its shell."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_windows.rst:45
#: ../../docs/contributing/development/compiling/compiling_for_linuxbsd.rst:44
#: ../../docs/contributing/development/compiling/compiling_for_macos.rst:39
#: ../../docs/contributing/development/compiling/compiling_for_android.rst:43
#: ../../docs/contributing/development/compiling/compiling_for_ios.rst:39
#: ../../docs/contributing/development/compiling/compiling_for_web.rst:22
msgid ""
"To get the Godot source code for compiling, see :ref:`doc_getting_source`."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_windows.rst:48
#: ../../docs/contributing/development/compiling/compiling_for_linuxbsd.rst:46
#: ../../docs/contributing/development/compiling/compiling_for_macos.rst:42
#: ../../docs/contributing/development/compiling/compiling_for_android.rst:46
#: ../../docs/contributing/development/compiling/compiling_for_ios.rst:42
#: ../../docs/contributing/development/compiling/compiling_for_web.rst:25
msgid ""
"For a general overview of SCons usage for Godot, see :ref:"
"`doc_introduction_to_the_buildsystem`."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_windows.rst:52
msgid "Setting up SCons"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_windows.rst:54
msgid ""
"To install SCons, open the command prompt and run the following command::"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_windows.rst:58
msgid ""
"If you are prompted with the message ``Defaulting to user installation "
"because normal site-packages is not writeable``, you may have to run that "
"command again using elevated permissions. Open a new command prompt as an "
"Administrator then run the command again to ensure that SCons is available "
"from the ``PATH``."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_windows.rst:64
msgid ""
"To check whether you have installed Python and SCons correctly, you can type "
"``python --version`` and ``scons --version`` into a command prompt (``cmd."
"exe``)."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_windows.rst:68
msgid ""
"If the commands above don't work, make sure to add Python to your ``PATH`` "
"environment variable after installing it, then check again. You can do so by "
"running the Python installer again and enabling the option to add Python to "
"the ``PATH``."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_windows.rst:73
msgid ""
"If SCons cannot detect your Visual Studio installation, it might be that "
"your SCons version is too old. Update it to the latest version with ``python "
"-m pip install --upgrade scons``."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_windows.rst:80
msgid "Installing Visual Studio caveats"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_windows.rst:82
msgid ""
"If installing Visual Studio 2017 or 2019, make sure to enable **C++** in the "
"list of workflows to install."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_windows.rst:85
msgid ""
"If installing Visual Studio 2015, make sure to run a **Custom** installation "
"instead of **Typical** and select **C++** as a language there."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_windows.rst:88
msgid ""
"If you've already made the mistake of installing Visual Studio without C++ "
"support, run the installer again; it should present you a **Modify** button. "
"Running the installer from *Add/Remove Programs* will only give you a "
"**Repair** option, which won't let you install C++ tools."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_windows.rst:94
msgid "Downloading Godot's source"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_windows.rst:96
msgid "Refer to :ref:`doc_getting_source` for detailed instructions."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_windows.rst:98
msgid ""
"The tutorial will assume from now on that you placed the source code in ``C:"
"\\godot``."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_windows.rst:103
msgid ""
"To prevent slowdowns caused by continuous virus scanning during compilation, "
"add the Godot source folder to the list of exceptions in your antivirus "
"software."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_windows.rst:107
msgid ""
"For Windows Defender, hit the :kbd:`Windows` key, type \"Windows Security\" "
"then hit :kbd:`Enter`. Click on **Virus & threat protection** on the left "
"panel. Under **Virus & threat protection settings** click on **Mange "
"Settings** and scroll down to **Exclusions**. Click **Add or remove "
"exclusions** then add the Godot source folder."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_windows.rst:117
msgid "Selecting a compiler"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_windows.rst:119
msgid ""
"SCons will automatically find and use an existing Visual Studio "
"installation. If you do not have Visual Studio installed, it will attempt to "
"use MinGW instead. If you already have Visual Studio installed and want to "
"use MinGW, pass ``use_mingw=yes`` to the SCons command line. Note that MSVC "
"builds cannot be performed from the MSYS2 or MinGW shells. Use either ``cmd."
"exe`` or PowerShell instead."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_windows.rst:126
msgid ""
"During development, using the Visual Studio compiler is usually a better "
"idea, as it links the Godot binary much faster than MinGW. However, MinGW "
"can produce more optimized binaries using link-time optimization (see "
"below), making it a better choice for production use."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_windows.rst:132
msgid "Running SCons"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_windows.rst:134
msgid ""
"After opening a command prompt, change to the root directory of the engine "
"source code (using ``cd``) and type:"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_windows.rst:141
msgid ""
"When compiling with multiple CPU threads, SCons may warn about pywin32 being "
"missing. You can safely ignore this warning."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_windows.rst:144
msgid ""
"If all goes well, the resulting binary executable will be placed in ``C:"
"\\godot\\bin\\`` with the name ``godot.windows.editor.x86_32.exe`` or "
"``godot.windows.editor.x86_64.exe``. By default, SCons will build a binary "
"matching your CPU architecture, but this can be overridden using "
"``arch=x86_64`` or ``arch=x86_32``."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_windows.rst:150
msgid ""
"This executable file contains the whole engine and runs without any "
"dependencies. Running it will bring up the Project Manager."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_windows.rst:153
msgid ""
"If you are compiling Godot for production use, then you can make the final "
"executable smaller and faster by adding the SCons option "
"``target=template_release``."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_windows.rst:157
msgid ""
"If you are compiling Godot with MinGW, you can make the binary even smaller "
"and faster by adding the SCons option ``lto=full``. As link-time "
"optimization is a memory-intensive process, this will require about 7 GB of "
"available RAM while compiling."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_windows.rst:162
#: ../../docs/contributing/development/compiling/compiling_for_linuxbsd.rst:277
#: ../../docs/contributing/development/compiling/compiling_for_macos.rst:67
msgid ""
"If you want to use separate editor settings for your own Godot builds and "
"official releases, you can enable :ref:`doc_data_paths_self_contained_mode` "
"by creating a file called ``._sc_`` or ``_sc_`` in the ``bin/`` folder."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_windows.rst:168
#, fuzzy
msgid "Development in Visual Studio"
msgstr "Razvoj"

#: ../../docs/contributing/development/compiling/compiling_for_windows.rst:170
msgid ""
"Using an IDE is not required to compile Godot, as SCons takes care of "
"everything. But if you intend to do engine development or debugging of the "
"engine's C++ code, you may be interested in configuring a code editor or an "
"IDE."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_windows.rst:174
msgid ""
"Folder-based editors don't require any particular setup to start working "
"with Godot's codebase. To edit projects with Visual Studio they need to be "
"set up as a solution."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_windows.rst:177
msgid ""
"You can create a Visual Studio solution via SCons by running SCons with the "
"``vsproj=yes`` parameter, like this::"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_windows.rst:182
msgid ""
"You will be able to open Godot's source in a Visual Studio solution now, and "
"able to build Godot using Visual Studio's **Build** button."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_windows.rst:185
msgid "See :ref:`doc_configuring_an_ide_vs` for further details."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_windows.rst:188
msgid "Cross-compiling for Windows from other operating systems"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_windows.rst:190
msgid ""
"If you are a Linux or macOS user, you need to install `MinGW-w64 <https://"
"mingw-w64.org/doku.php>`__, which typically comes in 32-bit and 64-bit "
"variants. The package names may differ based on your distribution, here are "
"some known ones:"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_windows.rst:200
msgid "**Debian** / **Ubuntu**"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_windows.rst:204
#: ../../docs/contributing/development/compiling/compiling_for_linuxbsd.rst:439
msgid "**Fedora**"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_windows.rst:209
msgid "**macOS**"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_windows.rst:213
msgid "**Mageia**"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_windows.rst:219
msgid ""
"Before attempting the compilation, SCons will check for the following "
"binaries in your ``PATH`` environment variable::"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_windows.rst:225
msgid ""
"If the binaries are not located in the ``PATH`` (e.g. ``/usr/bin``), you can "
"define the following environment variable to give a hint to the build "
"system::"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_windows.rst:231
msgid ""
"Where ``/path/to/mingw`` is the path containing the ``bin`` directory where "
"``i686-w64-mingw32-gcc`` and ``x86_64-w64-mingw32-gcc`` are located (e.g. ``/"
"opt/mingw-w64`` if the binaries are located in ``/opt/mingw-w64/bin``)."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_windows.rst:235
msgid ""
"To make sure you are doing things correctly, executing the following in the "
"shell should result in a working compiler (the version output may differ "
"based on your system)::"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_windows.rst:242
msgid ""
"When cross-compiling for Windows using MinGW-w64, keep in mind only "
"``x86_64`` and ``x86_32`` architectures are supported. Be sure to specify "
"the right ``arch=`` option when invoking SCons if building from a different "
"architecture."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_windows.rst:250
msgid ""
"Cross-compiling from some Ubuntu versions may lead to `this bug <https://"
"github.com/godotengine/godot/issues/9258>`_, due to a default configuration "
"lacking support for POSIX threading."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_windows.rst:254
msgid ""
"You can change that configuration following those instructions, for 64-bit::"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_windows.rst:262
msgid "And for 32-bit::"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_windows.rst:270
msgid "Creating Windows export templates"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_windows.rst:272
msgid ""
"Windows export templates are created by compiling Godot without the editor, "
"with the following flags:"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_windows.rst:282
msgid ""
"If you plan on replacing the standard export templates, copy these to the "
"following location, replacing ``<version>`` with the version identifier "
"(such as ``3.1.1.stable`` or ``3.2.dev``):"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_windows.rst:290
msgid "With the following names::"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_windows.rst:297
msgid ""
"However, if you are using custom modules or custom engine code, you may "
"instead want to configure your binaries as custom export templates here:"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_windows.rst:303
msgid ""
"You don't need to copy them in this case, just reference the resulting files "
"in the ``bin\\`` directory of your Godot source folder, so the next time you "
"build, you will automatically have the custom templates referenced."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_linuxbsd.rst:4
#, fuzzy
msgid "Compiling for Linux, \\*BSD"
msgstr "Kreiranje Sadržaja"

#: ../../docs/contributing/development/compiling/compiling_for_linuxbsd.rst:10
msgid ""
"This page describes how to compile Linux editor and export template binaries "
"from source. If you're looking to export your project to Linux instead, "
"read :ref:`doc_exporting_for_linux`."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_linuxbsd.rst:16
msgid ""
"For compiling under Linux or other Unix variants, the following is required:"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_linuxbsd.rst:19
msgid "GCC 7+ or Clang 6+."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_linuxbsd.rst:21
#: ../../docs/contributing/development/compiling/compiling_for_android.rst:29
msgid "`Python 3.6+ <https://www.python.org/downloads/>`_."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_linuxbsd.rst:23
#: ../../docs/contributing/development/compiling/compiling_for_macos.rst:19
#: ../../docs/contributing/development/compiling/compiling_for_android.rst:30
#: ../../docs/contributing/development/compiling/compiling_for_ios.rst:17
msgid "`SCons 3.0+ <https://scons.org/pages/download.html>`_ build system."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_linuxbsd.rst:27
msgid ""
"If your distribution uses Python 2 by default, or you are using a version of "
"SCons prior to 3.1.2, you will need to change the version of Python that "
"SCons uses by changing the shebang (the first line) of the SCons script file "
"to ``#! /usr/bin/python3``. Use the command ``which scons`` to find the "
"location of the SCons script file."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_linuxbsd.rst:32
msgid "pkg-config (used to detect the development libraries listed below)."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_linuxbsd.rst:33
#, fuzzy
msgid "Development libraries:"
msgstr "Razvoj"

#: ../../docs/contributing/development/compiling/compiling_for_linuxbsd.rst:35
msgid "X11, Xcursor, Xinerama, Xi and XRandR."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_linuxbsd.rst:36
msgid "MesaGL."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_linuxbsd.rst:37
msgid "ALSA."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_linuxbsd.rst:38
msgid "PulseAudio."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_linuxbsd.rst:40
msgid "*Optional* - libudev (build with ``udev=yes``)."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_linuxbsd.rst:55
#: ../../docs/contributing/development/debugging/vulkan/vulkan_validation_layers.rst:64
#, fuzzy
msgid "Alpine Linux"
msgstr "Windows"

#: ../../docs/contributing/development/compiling/compiling_for_linuxbsd.rst:75
#: ../../docs/contributing/development/debugging/vulkan/vulkan_validation_layers.rst:70
msgid "Arch Linux"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_linuxbsd.rst:93
#: ../../docs/contributing/development/debugging/vulkan/vulkan_validation_layers.rst:76
msgid "Debian/Ubuntu"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_linuxbsd.rst:112
#: ../../docs/contributing/development/debugging/vulkan/vulkan_validation_layers.rst:82
msgid "Fedora"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_linuxbsd.rst:133
#: ../../docs/contributing/development/debugging/vulkan/vulkan_validation_layers.rst:88
msgid "FreeBSD"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_linuxbsd.rst:148
#: ../../docs/contributing/development/debugging/vulkan/vulkan_validation_layers.rst:94
msgid "Gentoo"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_linuxbsd.rst:163
#: ../../docs/contributing/development/debugging/vulkan/vulkan_validation_layers.rst:100
msgid "Mageia"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_linuxbsd.rst:181
#: ../../docs/contributing/development/debugging/vulkan/vulkan_validation_layers.rst:106
msgid "OpenBSD"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_linuxbsd.rst:190
#: ../../docs/contributing/development/debugging/vulkan/vulkan_validation_layers.rst:112
msgid "openSUSE"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_linuxbsd.rst:209
msgid "NetBSD"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_linuxbsd.rst:219
msgid "For audio support, you can optionally install ``pulseaudio``."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_linuxbsd.rst:221
#: ../../docs/contributing/development/debugging/vulkan/vulkan_validation_layers.rst:118
msgid "Solus"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_linuxbsd.rst:240
msgid ""
"Start a terminal, go to the root dir of the engine source code and type:"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_linuxbsd.rst:248
msgid ""
"Prior to Godot 4.0, the Linux/\\*BSD target was called ``x11`` instead of "
"``linuxbsd``. If you are looking to compile Godot 3.x, make sure to use the "
"`3.x branch of this documentation <https://docs.godotengine.org/en/3.6/"
"development/compiling/compiling_for_x11.html>`__."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_linuxbsd.rst:252
msgid ""
"If all goes well, the resulting binary executable will be placed in the "
"\"bin\" subdirectory. This executable file contains the whole engine and "
"runs without any dependencies. Executing it will bring up the Project "
"Manager."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_linuxbsd.rst:259
msgid "If you wish to compile using Clang rather than GCC, use this command:"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_linuxbsd.rst:265
msgid ""
"Using Clang appears to be a requirement for OpenBSD, otherwise fonts would "
"not build."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_linuxbsd.rst:268
msgid ""
"If you are compiling Godot for production use, then you can make the final "
"executable smaller and faster by adding the SCons options "
"``target=template_release production=yes``."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_linuxbsd.rst:272
msgid ""
"If you are compiling Godot with GCC, you can make the binary even smaller "
"and faster by adding the SCons option ``lto=full``. As link-time "
"optimization is a memory-intensive process, this will require about 7 GB of "
"available RAM while compiling."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_linuxbsd.rst:283
#: ../../docs/contributing/development/compiling/compiling_for_macos.rst:94
msgid "Running a headless/server build"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_linuxbsd.rst:285
#: ../../docs/contributing/development/compiling/compiling_for_macos.rst:96
msgid ""
"To run in *headless* mode which provides editor functionality to export "
"projects in an automated manner, use the normal build::"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_linuxbsd.rst:290
#: ../../docs/contributing/development/compiling/compiling_for_macos.rst:101
msgid "And then use the ``--headless`` command line argument::"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_linuxbsd.rst:294
#: ../../docs/contributing/development/compiling/compiling_for_macos.rst:105
msgid ""
"To compile a debug *server* build which can be used with :ref:`remote "
"debugging tools <doc_command_line_tutorial>`, use::"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_linuxbsd.rst:299
msgid ""
"To compile a *server* build which is optimized to run dedicated game "
"servers, use::"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_linuxbsd.rst:305
#: ../../docs/contributing/development/compiling/compiling_for_macos.rst:116
#: ../../docs/contributing/development/compiling/compiling_for_web.rst:33
msgid "Building export templates"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_linuxbsd.rst:307
msgid ""
"Linux binaries usually won't run on distributions that are older than the "
"distribution they were built on. If you wish to distribute binaries that "
"work on most distributions, you should build them on an old distribution "
"such as Ubuntu 16.04. You can use a virtual machine or a container to set up "
"a suitable build environment."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_linuxbsd.rst:315
msgid ""
"To build Linux or \\*BSD export templates, run the build system with the "
"following parameters:"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_linuxbsd.rst:318
msgid "(32 bits)"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_linuxbsd.rst:325
msgid "(64 bits)"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_linuxbsd.rst:332
msgid ""
"Note that cross-compiling for the opposite bits (64/32) as your host "
"platform is not always straight-forward and might need a chroot environment."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_linuxbsd.rst:335
msgid ""
"To create standard export templates, the resulting files in the ``bin/`` "
"folder must be copied to:"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_linuxbsd.rst:342
msgid ""
"and named like this (even for \\*BSD which is seen as \"Linux/X11\" by "
"Godot):"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_linuxbsd.rst:351
msgid ""
"However, if you are writing your custom modules or custom C++ code, you "
"might instead want to configure your binaries as custom export templates "
"here:"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_linuxbsd.rst:357
msgid ""
"You don't even need to copy them, you can just reference the resulting files "
"in the ``bin/`` directory of your Godot source folder, so the next time you "
"build, you automatically have the custom templates referenced."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_linuxbsd.rst:362
msgid "Using Clang and LLD for faster development"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_linuxbsd.rst:364
msgid ""
"You can also use Clang and LLD to build Godot. This has two upsides compared "
"to the default GCC + GNU ld setup:"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_linuxbsd.rst:367
msgid ""
"LLD links Godot significantly faster compared to GNU ld or gold. This leads "
"to faster iteration times."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_linuxbsd.rst:369
msgid "Clang tends to give more useful error messages compared to GCC."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_linuxbsd.rst:371
msgid ""
"To do so, install Clang and the ``lld`` package from your distribution's "
"package manager then use the following SCons command::"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_linuxbsd.rst:376
msgid ""
"After the build is completed, a new binary with a ``.llvm`` suffix will be "
"created in the ``bin/`` folder."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_linuxbsd.rst:379
msgid ""
"It's still recommended to use GCC for production builds as they can be "
"compiled using link-time optimization, making the resulting binaries smaller "
"and faster."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_linuxbsd.rst:382
msgid "If this error occurs::"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_linuxbsd.rst:386
#, fuzzy
msgid "There are two solutions:"
msgstr "Ne postoje ograničenja prilikom korištenja Godot-a"

#: ../../docs/contributing/development/compiling/compiling_for_linuxbsd.rst:388
msgid "In your SCons command, add the parameter ``use_static_cpp=no``."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_linuxbsd.rst:389
msgid ""
"Follow `these instructions <https://github.com/ivmai/"
"libatomic_ops#installation-and-usage>`__ to configure, build, and install "
"``libatomic_ops``. Then, copy ``/usr/lib/libatomic_ops.a`` to ``/usr/lib/"
"libatomic.a``, or create a soft link to ``libatomic_ops`` by command ``ln -"
"s /usr/lib/libatomic_ops.a /usr/lib/libatomic.a``. The soft link can ensure "
"the latest ``libatomic_ops`` will be used without the need to copy it "
"everytime when it is updated."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_linuxbsd.rst:395
#, fuzzy
msgid "Using mold for faster development"
msgstr "Uvod"

#: ../../docs/contributing/development/compiling/compiling_for_linuxbsd.rst:397
msgid ""
"For even faster linking compared to LLD, you can use `mold <https://github."
"com/rui314/mold>`__. mold can be used with either GCC or Clang."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_linuxbsd.rst:400
msgid ""
"As of January 2023, mold is not readily available in Linux distribution "
"repositories, so you will have to install its binaries manually."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_linuxbsd.rst:403
#, fuzzy
msgid ""
"Download mold binaries from its `releases page <https://github.com/rui314/"
"mold/releases/latest>`__."
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati raznorazne `Godot demo projects "
"<https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/contributing/development/compiling/compiling_for_linuxbsd.rst:404
msgid ""
"Extract the ``.tar.gz`` file, then move the extraced folder to a location "
"such as ``.local/share/mold``."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_linuxbsd.rst:405
msgid ""
"Add ``$HOME/.local/share/mold/bin`` to your user's ``PATH`` environment "
"variable. For example, you can add the following line at the end of your "
"``$HOME/.bash_profile`` file:"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_linuxbsd.rst:412
msgid ""
"Open a new terminal (or run ``source \"$HOME/.bash_profile\"``), then use "
"the following SCons command when compiling Godot::"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_linuxbsd.rst:418
#, fuzzy
msgid "Using system libraries for faster development"
msgstr "Uvod"

#: ../../docs/contributing/development/compiling/compiling_for_linuxbsd.rst:420
msgid ""
"`Godot bundles the source code of various third-party libraries. <https://"
"github.com/godotengine/godot/tree/master/thirdparty>`__ You can choose to "
"use system versions of third-party libraries instead. This makes the Godot "
"binary faster to link, as third-party libraries are dynamically linked. "
"Therefore, they don't need to be statically linked every time you build the "
"engine (even on small incremental changes)."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_linuxbsd.rst:426
msgid ""
"However, not all Linux distributions have packages for third-party libraries "
"available (or they may not be up-to-date)."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_linuxbsd.rst:429
msgid ""
"Moving to system libraries can reduce linking times by several seconds on "
"slow CPUs, but it requires manual testing depending on your Linux "
"distribution. Also, you may not be able to use system libraries for "
"everything due to bugs in the system library packages (or in the build "
"system, as this feature is less tested)."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_linuxbsd.rst:435
msgid ""
"To compile Godot with system libraries, install these dependencies *on top* "
"of the ones listed in the :ref:`doc_compiling_for_linuxbsd_oneliners`:"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_linuxbsd.rst:446
msgid ""
"After installing all required packages, use the following command to build "
"Godot:"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_linuxbsd.rst:455
msgid ""
"You can view a list of all built-in libraries that have system alternatives "
"by running ``scons -h``, then looking for options starting with ``builtin_``."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_linuxbsd.rst:460
msgid ""
"When using system libraries, the resulting library is **not** portable "
"across Linux distributions anymore. Do not use this approach for creating "
"binaries you intend to distribute to others, unless you're creating a "
"package for a Linux distribution."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_linuxbsd.rst:466
#: ../../docs/contributing/development/compiling/compiling_for_macos.rst:172
#, fuzzy
msgid "Using Pyston for faster development"
msgstr "Uvod"

#: ../../docs/contributing/development/compiling/compiling_for_linuxbsd.rst:468
msgid ""
"You can use `Pyston <https://www.pyston.org/>`__ to run SCons. Pyston is a "
"JIT-enabled implementation of the Python language (which SCons is written "
"in). It is currently only compatible with Linux. Pyston can speed up "
"incremental builds significantly, often by a factor between 1.5× and 2×. "
"Pyston can be combined with Clang and LLD to get even faster builds."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_linuxbsd.rst:474
msgid ""
"Download the `latest portable Pyston release <https://github.com/pyston/"
"pyston/releases/latest>`__."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_linuxbsd.rst:475
msgid ""
"Extract the portable ``.tar.gz`` to a set location, such as ``$HOME/.local/"
"opt/pyston/`` (create folders as needed)."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_linuxbsd.rst:476
msgid ""
"Use ``cd`` to reach the extracted Pyston folder from a terminal, then run "
"``./pyston -m pip install scons`` to install SCons within Pyston."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_linuxbsd.rst:478
msgid ""
"To make SCons via Pyston easier to run, create a symbolic link of its "
"wrapper script to a location in your ``PATH`` environment variable::"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_linuxbsd.rst:483
msgid ""
"Instead of running ``scons <build arguments>``, run ``pyston-scons <build "
"arguments>`` to compile Godot."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_linuxbsd.rst:486
msgid ""
"If you can't run ``pyston-scons`` after creating the symbolic link, make "
"sure ``$HOME/.local/bin/`` is part of your user's ``PATH`` environment "
"variable."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_linuxbsd.rst:491
msgid ""
"Alternatively, you can run ``python -m pip install pyston_lite_autoload`` "
"then run SCons as usual. This will automatically load a subset of Pyston's "
"optimizations in any Python program you run. However, this won't bring as "
"much of a performance improvement compared to installing \"full\" Pyston."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_macos.rst:4
msgid "Compiling for macOS"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_macos.rst:10
msgid ""
"This page describes how to compile macOS editor and export template binaries "
"from source. If you're looking to export your project to macOS instead, "
"read :ref:`doc_exporting_for_macos`."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_macos.rst:16
msgid "For compiling under macOS, the following is required:"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_macos.rst:18
#: ../../docs/contributing/development/compiling/compiling_for_ios.rst:16
msgid "`Python 3.6+ <https://www.python.org/downloads/macos/>`_."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_macos.rst:20
msgid ""
"`Xcode <https://apps.apple.com/us/app/xcode/id497799835>`_ (or the more "
"lightweight Command Line Tools for Xcode)."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_macos.rst:22
msgid ""
"`Vulkan SDK <https://sdk.lunarg.com/sdk/download/latest/mac/vulkan-sdk."
"dmg>`_ for MoltenVK (macOS doesn't support Vulkan out of the box)."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_macos.rst:25
#: ../../docs/contributing/development/compiling/compiling_for_ios.rst:25
msgid ""
"If you have `Homebrew <https://brew.sh/>`_ installed, you can easily install "
"SCons using the following command::"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_macos.rst:30
#: ../../docs/contributing/development/compiling/compiling_for_ios.rst:30
msgid ""
"Installing Homebrew will also fetch the Command Line Tools for Xcode "
"automatically if you don't have them already."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_macos.rst:33
#: ../../docs/contributing/development/compiling/compiling_for_ios.rst:33
msgid ""
"Similarly, if you have `MacPorts <https://www.macports.org/>`_ installed, "
"you can easily install SCons using the following command::"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_macos.rst:48
msgid "Start a terminal, go to the root directory of the engine source code."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_macos.rst:50
msgid "To compile for Intel (x86-64) powered Macs, use::"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_macos.rst:54
msgid "To compile for Apple Silicon (ARM64) powered Macs, use::"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_macos.rst:58
msgid ""
"To support both architectures in a single \"Universal 2\" binary, run the "
"above two commands and then use ``lipo`` to bundle them together::"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_macos.rst:62
msgid ""
"If all goes well, the resulting binary executable will be placed in the "
"``bin/`` subdirectory. This executable file contains the whole engine and "
"runs without any dependencies. Executing it will bring up the Project "
"Manager."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_macos.rst:72
msgid ""
"To create an ``.app`` bundle like in the official builds, you need to use "
"the template located in ``misc/dist/macos_tools.app``. Typically, for an "
"optimized editor binary built with ``dev_build=yes``::"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_macos.rst:84
#: ../../docs/contributing/development/compiling/compiling_for_macos.rst:157
msgid ""
"If you are building the ``master`` branch, you also need to include support "
"for the MoltenVK Vulkan portability library. By default, it will be linked "
"statically from your installation of the Vulkan SDK for macOS. You can also "
"choose to link it dynamically by passing ``use_volk=yes`` and including the "
"dynamic library in your ``.app`` bundle::"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_macos.rst:110
msgid ""
"To compile a release *server* build which is optimized to run dedicated game "
"servers, use::"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_macos.rst:118
msgid ""
"To build macOS export templates, you have to compile using the targets "
"without the editor: ``target=template_release`` (release template) and "
"``target=template_debug``."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_macos.rst:122
msgid ""
"Official templates are universal binaries which support both Intel x86_64 "
"and ARM64 architectures. You can also create export templates that support "
"only one of those two architectures by leaving out the ``lipo`` step below."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_macos.rst:126
msgid "For Intel x86_64::"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_macos.rst:131
msgid "For Arm64 (Apple M1)::"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_macos.rst:136
msgid ""
"To support both architectures in a single \"Universal 2\" binary, run the "
"above two commands blocks and then use ``lipo`` to bundle them together::"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_macos.rst:142
msgid ""
"To create an ``.app`` bundle like in the official builds, you need to use "
"the template located in ``misc/dist/macos_template.app``. The release and "
"debug builds should be placed in ``macos_template.app/Contents/MacOS`` with "
"the names ``godot_macos_release.universal`` and ``godot_macos_debug."
"universal`` respectively. You can do so with the following commands "
"(assuming a universal build, otherwise replace the ``.universal`` extension "
"with the one of your arch-specific binaries)::"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_macos.rst:166
msgid ""
"You can then zip the ``macos_template.app`` folder to reproduce the ``macos."
"zip`` template from the official Godot distribution::"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_macos.rst:174
msgid ""
"You can use `Pyston <https://www.pyston.org/>`__ to run SCons. Pyston is a "
"JIT-enabled implementation of the Python language (which SCons is written "
"in). Its \"full\" version is currently only compatible with Linux, but "
"Pyston-lite is also compatible with macOS (both x86 and ARM). Pyston can "
"speed up incremental builds significantly, often by a factor between 1.5× "
"and 2×. Pyston can be combined with alternative linkers such as LLD or Mold "
"to get even faster builds."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_macos.rst:181
msgid ""
"To install Pyston-lite, run ``python -m pip install pyston_lite_autoload`` "
"then run SCons as usual. This will automatically load a subset of Pyston's "
"optimizations in any Python program you run. However, this won't bring as "
"much of a performance improvement compared to installing \"full\" Pyston "
"(which currently can't be done on macOS)."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_macos.rst:188
msgid "Cross-compiling for macOS from Linux"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_macos.rst:190
msgid ""
"It is possible to compile for macOS in a Linux environment (and maybe also "
"in Windows using the Windows Subsystem for Linux). For that, you'll need to "
"install `OSXCross <https://github.com/tpoechtrager/osxcross>`__ to be able "
"to use macOS as a target. First, follow the instructions to install it:"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_macos.rst:195
msgid ""
"Clone the `OSXCross repository <https://github.com/tpoechtrager/osxcross>`__ "
"somewhere on your machine (or download a ZIP file and extract it somewhere), "
"e.g.::"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_macos.rst:201
msgid ""
"Follow the instructions to package the SDK: https://github.com/tpoechtrager/"
"osxcross#packaging-the-sdk"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_macos.rst:203
msgid ""
"Follow the instructions to install OSXCross: https://github.com/tpoechtrager/"
"osxcross#installation"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_macos.rst:206
msgid ""
"After that, you will need to define the ``OSXCROSS_ROOT`` as the path to the "
"OSXCross installation (the same place where you cloned the repository/"
"extracted the zip), e.g.::"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_macos.rst:212
msgid "Now you can compile with SCons like you normally would::"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_macos.rst:216
msgid ""
"If you have an OSXCross SDK version different from the one expected by the "
"SCons buildsystem, you can specify a custom one with the ``osxcross_sdk`` "
"argument::"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_android.rst:4
msgid "Compiling for Android"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_android.rst:10
msgid ""
"This page describes how to compile Android export template binaries from "
"source. If you're looking to export your project to Android instead, read :"
"ref:`doc_exporting_for_android`."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_android.rst:14
msgid "Note"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_android.rst:16
msgid ""
"In most cases, using the built-in deployer and export templates is good "
"enough. Compiling the Android APK manually is mostly useful for custom "
"builds or custom packages for the deployer."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_android.rst:20
msgid ""
"Also, you still need to follow the steps mentioned in the :ref:"
"`doc_exporting_for_android` tutorial before attempting to build a custom "
"export template."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_android.rst:27
msgid "For compiling under Windows, Linux or macOS, the following is required:"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_android.rst:31
msgid ""
"`Android SDK <https://developer.android.com/studio/#command-tools>`_ "
"(command-line tools are sufficient)."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_android.rst:34
msgid "Required SDK components will be automatically installed."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_android.rst:36
#, fuzzy
msgid "On Linux,"
msgstr "Windows"

#: ../../docs/contributing/development/compiling/compiling_for_android.rst:36
msgid ""
"**do not use an Android SDK provided by your distribution's repositories as "
"it will often be outdated**."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_android.rst:38
msgid "Gradle (will be downloaded and installed automatically if missing)."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_android.rst:39
msgid "JDK 17 (either OpenJDK or Oracle JDK)."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_android.rst:41
msgid ""
"You can download a build from `ojdkbuild <https://adoptium.net/temurin/"
"releases/?variant=openjdk17>`_."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_android.rst:52
msgid "Setting up the buildsystem"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_android.rst:54
msgid ""
"Set the environment variable ``ANDROID_HOME`` to point to the Android SDK. "
"If you downloaded the Android command-line tools, this would be the folder "
"where you extracted the contents of the ZIP archive."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_android.rst:58
msgid "Install the necessary SDK components in this folder:"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_android.rst:60
msgid ""
"Accept the SDK component licenses by running the following command where "
"``android_sdk_path`` is the path to the Android SDK, then answering all the "
"prompts with ``y``:"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_android.rst:67
msgid ""
"Complete setup by running the following command where ``android_sdk_path`` "
"is the path to the Android SDK."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_android.rst:73
msgid ""
"To set the environment variable on Windows, press :kbd:`Windows + R`, type "
"\"control system\", then click on **Advanced system settings** in the left "
"pane, then click on **Environment variables** on the window that appears."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_android.rst:77
msgid ""
"To set the environment variable on Linux or macOS, use ``export "
"ANDROID_HOME=/path/to/android-sdk`` where ``/path/to/android-sdk`` points to "
"the root of the SDK directories."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_android.rst:82
msgid "Building the export templates"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_android.rst:84
msgid ""
"Godot needs two export templates for Android: the optimized \"release\" "
"template (``android_release.apk``) and the debug template (``android_debug."
"apk``). As Google will require all APKs to include ARMv8 (64-bit) libraries "
"starting from August 2019, the commands below will build an APK containing "
"both ARMv7 and ARMv8 libraries."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_android.rst:90
msgid ""
"Compiling the standard export templates is done by calling SCons from the "
"Godot root directory with the following arguments:"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_android.rst:93
msgid ""
"Release template (used when exporting with **Debugging Enabled** unchecked)"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_android.rst:106
msgid "The resulting APK will be located at ``bin/android_release.apk``."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_android.rst:108
msgid "Debug template (used when exporting with **Debugging Enabled** checked)"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_android.rst:121
msgid "The resulting APK will be located at ``bin/android_debug.apk``."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_android.rst:125
msgid ""
"If you want to enable Vulkan validation layers, see :ref:`Vulkan validation "
"layers on Android <doc_vulkan_validation_layers_android>`."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_android.rst:129
msgid "Adding support for x86 devices"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_android.rst:131
msgid ""
"If you also want to include support for x86 and x86-64 devices, run the "
"SCons command a third and fourth time with the ``arch=x86_32``, and "
"``arch=x86_64`` arguments before building the APK with Gradle. For example, "
"for the release template:"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_android.rst:149
msgid ""
"This will create a fat binary that works on all platforms. The final APK "
"size of exported projects will depend on the platforms you choose to support "
"when exporting; in other words, unused platforms will be removed from the "
"APK."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_android.rst:155
#, fuzzy
msgid "Cleaning the generated export templates"
msgstr "Kreiranje Sadržaja"

#: ../../docs/contributing/development/compiling/compiling_for_android.rst:157
msgid ""
"You can use the following commands to remove the generated export templates:"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_android.rst:169
msgid "Using the export templates"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_android.rst:171
msgid ""
"Godot needs release and debug APKs that were compiled against the same "
"version/commit as the editor. If you are using official binaries for the "
"editor, make sure to install the matching export templates, or build your "
"own from the same version."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_android.rst:176
msgid ""
"When exporting your game, Godot opens the APK, changes a few things inside "
"and adds your files."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_android.rst:180
msgid "Installing the templates"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_android.rst:182
msgid ""
"The newly-compiled templates (``android_debug.apk`` and ``android_release."
"apk``) must be copied to Godot's templates folder with their respective "
"names. The templates folder can be located in:"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_android.rst:186
msgid "Windows: ``%APPDATA%\\Godot\\export_templates\\<version>\\``"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_android.rst:187
msgid "Linux: ``$HOME/.local/share/godot/export_templates/<version>/``"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_android.rst:188
msgid ""
"macOS: ``$HOME/Library/Application Support/Godot/export_templates/<version>/"
"``"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_android.rst:190
msgid ""
"``<version>`` is of the form ``major.minor[.patch].status`` using values "
"from ``version.py`` in your Godot source repository (e.g. ``3.0.5.stable`` "
"or ``3.1.dev``). You also need to write this same version string to a "
"``version.txt`` file located next to your export templates."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_android.rst:197
msgid ""
"However, if you are writing your custom modules or custom C++ code, you "
"might instead want to configure your APKs as custom export templates here:"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_android.rst:203
msgid ""
"You don't even need to copy them, you can just reference the resulting file "
"in the ``bin\\`` directory of your Godot source folder, so that the next "
"time you build you will automatically have the custom templates referenced."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_android.rst:209
#, fuzzy
msgid "Building the Godot editor"
msgstr "Kreiranje Sadržaja"

#: ../../docs/contributing/development/compiling/compiling_for_android.rst:211
msgid ""
"Compiling the editor is done by calling SCons from the Godot root directory "
"with the following arguments:"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_android.rst:227
msgid ""
"The resulting APK will be located at ``bin/android_editor_builds/"
"android_editor-release.apk``."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_android.rst:230
#, fuzzy
msgid "Removing the Editor templates"
msgstr "Kreiranje Sadržaja"

#: ../../docs/contributing/development/compiling/compiling_for_android.rst:232
msgid ""
"You can use the following commands to remove the generated editor templates:"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_android.rst:243
#, fuzzy
msgid "Installing the Godot editor"
msgstr "Kreiranje Sadržaja"

#: ../../docs/contributing/development/compiling/compiling_for_android.rst:245
msgid ""
"With an Android device with Developer Options enabled, connect the Android "
"device to your computer via its charging cable to a USB/USB-C port. Open up "
"a Terminal/Command Prompt and run the following commands from the root "
"directory with the following arguments:"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_android.rst:256
msgid "Platform doesn't appear in SCons"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_android.rst:258
msgid ""
"Double-check that you've set the ``ANDROID_HOME`` environment variable. This "
"is required for the platform to appear in SCons' list of detected platforms. "
"See :ref:`Setting up the buildsystem "
"<doc_android_setting_up_the_buildsystem>` for more information."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_android.rst:265
msgid "Application not installed"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_android.rst:267
msgid ""
"Android might complain the application is not correctly installed. If so:"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_android.rst:270
msgid "Check that the debug keystore is properly generated."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_android.rst:271
msgid "Check that the jarsigner executable is from JDK 8."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_android.rst:273
msgid ""
"If it still fails, open a command line and run `logcat <https://developer."
"android.com/studio/command-line/logcat>`_:"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_android.rst:279
msgid ""
"Then check the output while the application is installed; the error message "
"should be presented there. Seek assistance if you can't figure it out."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_android.rst:284
msgid "Application exits immediately"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_android.rst:286
msgid ""
"If the application runs but exits immediately, this might be due to one of "
"the following reasons:"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_android.rst:289
msgid ""
"Make sure to use export templates that match your editor version; if you use "
"a new Godot version, you *have* to update the templates too."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_android.rst:291
msgid ""
"``libgodot_android.so`` is not in ``libs/<arch>/`` where ``<arch>`` is the "
"device's architecture."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_android.rst:293
msgid ""
"The device's architecture does not match the exported one(s). Make sure your "
"templates were built for that device's architecture, and that the export "
"settings included support for that architecture."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_android.rst:297
msgid "In any case, ``adb logcat`` should also show the cause of the error."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_ios.rst:4
msgid "Compiling for iOS"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_ios.rst:10
msgid ""
"This page describes how to compile iOS export template binaries from source. "
"If you're looking to export your project to iOS instead, read :ref:"
"`doc_exporting_for_ios`."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_ios.rst:18
msgid "`Xcode <https://apps.apple.com/us/app/xcode/id497799835>`_."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_ios.rst:20
msgid "If you are building the ``master`` branch:"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_ios.rst:22
msgid ""
"Download and follow README instructions to build a static ``.xcframework`` "
"from the `MoltenVK SDK <https://github.com/KhronosGroup/MoltenVK#fetching-"
"moltenvk-source-code>`__."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_ios.rst:48
msgid "Open a Terminal, go to the root dir of the engine source code and type:"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_ios.rst:54
msgid "for a debug build, or:"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_ios.rst:60
msgid ""
"for a release build (check ``platform/ios/detect.py`` for the compiler flags "
"used for each configuration)."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_ios.rst:63
msgid "Alternatively, you can run"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_ios.rst:70
msgid "for a Simulator libraries."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_ios.rst:72
msgid ""
"To create an Xcode project like in the official builds, you need to use the "
"template located in ``misc/dist/ios_xcode``. The release and debug libraries "
"should be placed in ``libgodot.ios.debug.xcframework`` and ``libgodot.ios."
"release.xcframework`` respectively."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_ios.rst:86
msgid ""
"The MoltenVK static ``.xcframework`` folder must also be placed in the "
"``ios_xcode`` folder once it has been created."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_ios.rst:92
msgid ""
"To run on a device or simulator, follow these instructions: :ref:"
"`doc_exporting_for_ios`."
msgstr ""

#: ../../docs/contributing/development/compiling/cross-compiling_for_ios_on_linux.rst:4
msgid "Cross-compiling for iOS on Linux"
msgstr ""

#: ../../docs/contributing/development/compiling/cross-compiling_for_ios_on_linux.rst:8
msgid ""
"The procedure for this is somewhat complex and requires a lot of steps, but "
"once you have the environment properly configured you can compile Godot for "
"iOS anytime you want."
msgstr ""

#: ../../docs/contributing/development/compiling/cross-compiling_for_ios_on_linux.rst:13
msgid "Disclaimer"
msgstr ""

#: ../../docs/contributing/development/compiling/cross-compiling_for_ios_on_linux.rst:15
msgid ""
"While it is possible to compile for iOS on a Linux environment, Apple is "
"very restrictive about the tools to be used (especially hardware-wise), "
"allowing pretty much only their products to be used for development. So this "
"is **not official**. However, in 2010 Apple said they relaxed some of the "
"`App Store review guidelines <https://developer.apple.com/app-store/review/"
"guidelines/>`__ to allow any tool to be used, as long as the resulting "
"binary does not download any code, which means it should be OK to use the "
"procedure described here and cross-compiling the binary."
msgstr ""

#: ../../docs/contributing/development/compiling/cross-compiling_for_ios_on_linux.rst:27
msgid ""
"`XCode with the iOS SDK <https://developer.apple.com/xcode/download>`__ (a "
"dmg image, for newer versions a **xip** file is going to be downloaded.)"
msgstr ""

#: ../../docs/contributing/development/compiling/cross-compiling_for_ios_on_linux.rst:29
msgid ""
"`Clang >= 3.5 <https://clang.llvm.org>`__ for your development machine "
"installed and in the ``PATH``. It has to be version >= 3.5 to target "
"``arm64`` architecture."
msgstr ""

#: ../../docs/contributing/development/compiling/cross-compiling_for_ios_on_linux.rst:32
msgid ""
"`Fuse <https://github.com/libfuse/libfuse>`__ for mounting and unmounting "
"the dmg image."
msgstr ""

#: ../../docs/contributing/development/compiling/cross-compiling_for_ios_on_linux.rst:34
msgid ""
"`darling-dmg <https://github.com/darlinghq/darling-dmg>`__, which needs to "
"be built from source. The procedure for that is explained below."
msgstr ""

#: ../../docs/contributing/development/compiling/cross-compiling_for_ios_on_linux.rst:38
msgid ""
"For newer versions you should download `xar <https://mackyle.github.io/xar/"
">`__ and `pbzx <https://github.com/NiklasRosenstein/pbzx>`__."
msgstr ""

#: ../../docs/contributing/development/compiling/cross-compiling_for_ios_on_linux.rst:40
msgid ""
"For building darling-dmg, you'll need the development packages of the "
"following libraries: fuse, icu, openssl, zlib, bzip2."
msgstr ""

#: ../../docs/contributing/development/compiling/cross-compiling_for_ios_on_linux.rst:42
msgid ""
"For building xar and pbzx you may want to follow `this guide <https://gist."
"github.com/phracker/1944ce190e01963c550566b749bd2b54>`__."
msgstr ""

#: ../../docs/contributing/development/compiling/cross-compiling_for_ios_on_linux.rst:45
msgid ""
"`cctools-port <https://github.com/tpoechtrager/cctools-port>`__ for the "
"needed build tools. The procedure for building is quite peculiar and is "
"described below."
msgstr ""

#: ../../docs/contributing/development/compiling/cross-compiling_for_ios_on_linux.rst:49
msgid "This also has some extra dependencies: automake, autogen, libtool."
msgstr ""

#: ../../docs/contributing/development/compiling/cross-compiling_for_ios_on_linux.rst:52
msgid "Configuring the environment"
msgstr ""

#: ../../docs/contributing/development/compiling/cross-compiling_for_ios_on_linux.rst:55
msgid "darling-dmg"
msgstr ""

#: ../../docs/contributing/development/compiling/cross-compiling_for_ios_on_linux.rst:57
msgid "Clone the repository on your machine:"
msgstr ""

#: ../../docs/contributing/development/compiling/cross-compiling_for_ios_on_linux.rst:63
msgid "Build it:"
msgstr ""

#: ../../docs/contributing/development/compiling/cross-compiling_for_ios_on_linux.rst:75
msgid "Preparing the SDK"
msgstr ""

#: ../../docs/contributing/development/compiling/cross-compiling_for_ios_on_linux.rst:77
msgid "Mount the XCode image:"
msgstr ""

#: ../../docs/contributing/development/compiling/cross-compiling_for_ios_on_linux.rst:87
msgid "For newer versions you should extract the **xip** file:"
msgstr ""

#: ../../docs/contributing/development/compiling/cross-compiling_for_ios_on_linux.rst:97
msgid ""
"Note that for the commands below, you may need to replace the version (`X."
"x`) with whatever iOS SDK version you're using."
msgstr ""

#: ../../docs/contributing/development/compiling/cross-compiling_for_ios_on_linux.rst:99
msgid "Extract the iOS SDK:"
msgstr ""

#: ../../docs/contributing/development/compiling/cross-compiling_for_ios_on_linux.rst:109
msgid "Pack the SDK:"
msgstr ""

#: ../../docs/contributing/development/compiling/cross-compiling_for_ios_on_linux.rst:117
msgid "Toolchain"
msgstr ""

#: ../../docs/contributing/development/compiling/cross-compiling_for_ios_on_linux.rst:119
msgid "Build cctools:"
msgstr ""

#: ../../docs/contributing/development/compiling/cross-compiling_for_ios_on_linux.rst:127
msgid ""
"Copy the tools to a nicer place. Note that the SCons scripts for building "
"will look under ``usr/bin`` inside the directory you provide for the "
"toolchain binaries, so you must copy to such subdirectory, akin to the "
"following commands:"
msgstr ""

#: ../../docs/contributing/development/compiling/cross-compiling_for_ios_on_linux.rst:137
msgid ""
"Now you should have the iOS toolchain binaries in ``/home/user/iostoolchain/"
"usr/bin``."
msgstr ""

#: ../../docs/contributing/development/compiling/cross-compiling_for_ios_on_linux.rst:141
msgid "Compiling Godot for iPhone"
msgstr ""

#: ../../docs/contributing/development/compiling/cross-compiling_for_ios_on_linux.rst:143
msgid ""
"Once you've done the above steps, you should keep two things in your "
"environment: the built toolchain and the iPhoneOS SDK directory. Those can "
"stay anywhere you want since you have to provide their paths to the SCons "
"build command."
msgstr ""

#: ../../docs/contributing/development/compiling/cross-compiling_for_ios_on_linux.rst:148
msgid ""
"For the iPhone platform to be detected, you need the ``OSXCROSS_IOS`` "
"environment variable defined to anything."
msgstr ""

#: ../../docs/contributing/development/compiling/cross-compiling_for_ios_on_linux.rst:155
msgid ""
"Now you can compile for iPhone using SCons like the standard Godot way, with "
"some additional arguments to provide the correct paths:"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_web.rst:4
msgid "Compiling for the Web"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_web.rst:8
msgid ""
"This page describes how to compile HTML5 editor and export template binaries "
"from source. If you're looking to export your project to HTML5 instead, "
"read :ref:`doc_exporting_for_web`."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_web.rst:16
msgid "To compile export templates for the Web, the following is required:"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_web.rst:18
msgid "`Emscripten 3.1.39+ <https://emscripten.org>`__."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_web.rst:19
msgid "`Python 3.6+ <https://www.python.org/>`__."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_web.rst:20
msgid "`SCons 3.0+ <https://scons.org/pages/download.html>`__ build system."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_web.rst:28
msgid ""
"Emscripten 3.1.39+ is recommended, but older 3.x versions are known to work."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_web.rst:30
msgid ""
"Please note that the minimum requirement for GDExtension support is 3.1.14."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_web.rst:35
msgid ""
"Before starting, confirm that ``emcc`` is available in your PATH. This is "
"usually configured by the Emscripten SDK, e.g. when invoking ``emsdk "
"activate`` and ``source ./emsdk_env.sh``/``emsdk_env.bat``."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_web.rst:39
msgid ""
"Open a terminal and navigate to the root directory of the engine source "
"code. Then instruct SCons to build the Web platform. Specify ``target`` as "
"either ``template_release`` for a release build or ``template_debug`` for a "
"debug build::"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_web.rst:46
msgid ""
"By default, the :ref:`JavaScript singleton <doc_javascript_eval>` will be "
"built into the engine. Official export templates also have the JavaScript "
"singleton enabled. Since ``eval()`` calls can be a security concern, the "
"``javascript_eval`` option can be used to build without the singleton::"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_web.rst:54
msgid ""
"The engine will now be compiled to WebAssembly by Emscripten. Once finished, "
"the resulting file will be placed in the ``bin`` subdirectory. Its name is "
"``godot.web.template_release.wasm32.zip`` for release or ``godot.web."
"template_debug.wasm32.zip`` for debug."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_web.rst:59
msgid ""
"Finally, rename the zip archive to ``web_release.zip`` for the release "
"template::"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_web.rst:64
msgid "And ``web_debug.zip`` for the debug template::"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_web.rst:71
msgid ""
"The default export templates do not include GDExtension support for "
"performance and compatibility reasons. See the :ref:`export page "
"<doc_javascript_export_options>` for more info."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_web.rst:75
msgid ""
"You can build the export templates using the option ``dlink_enabled=yes`` to "
"enable GDExtension support::"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_web.rst:81
msgid ""
"Once finished, the resulting file will be placed in the ``bin`` "
"subdirectory. Its name will have ``_dlink`` added."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_web.rst:84
msgid ""
"Finally, rename the zip archives to ``web_dlink_release.zip`` and "
"``web_dlink_release.zip`` for the release template::"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_web.rst:91
#, fuzzy
msgid "Building the editor"
msgstr "Kreiranje Sadržaja"

#: ../../docs/contributing/development/compiling/compiling_for_web.rst:93
msgid ""
"It is also possible to build a version of the Godot editor that can run in "
"the browser. The editor version is not recommended over the native build. "
"You can build the editor with::"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_web.rst:99
msgid ""
"Once finished, the resulting file will be placed in the ``bin`` "
"subdirectory. Its name will be ``godot.web.editor.wasm32.zip``. You can "
"upload the zip content to your web server and visit it with your browser to "
"use the editor."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_web.rst:103
msgid ""
"Refer to the :ref:`export page <doc_javascript_export_options>` for the web "
"server requirements."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_web.rst:108
msgid ""
"The Godot repository includes a `Python script to host a local web server "
"<https://raw.githubusercontent.com/godotengine/godot/master/platform/web/"
"serve.py>`__. This can be used to test the web editor locally."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_web.rst:112
msgid ""
"After compiling the editor, extract the ZIP archive that was created in the "
"``bin/`` folder, then run the following command in the Godot repository root:"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_for_web.rst:121
msgid ""
"This will serve the contents of the ``bin/`` folder and open the default web "
"browser automatically. In the page that opens, access ``godot.tools.html`` "
"and you should be able to test the web editor this way."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_with_dotnet.rst:4
#, fuzzy
msgid "Compiling with .NET"
msgstr "Kreiranje Sadržaja"

#: ../../docs/contributing/development/compiling/compiling_with_dotnet.rst:11
msgid "`.NET SDK 6.0+ <https://dotnet.microsoft.com/download>`_"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_with_dotnet.rst:13
msgid ""
"You can use ``dotnet --info`` to check which .NET SDK versions are installed."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_with_dotnet.rst:16
msgid "Enable the .NET module"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_with_dotnet.rst:18
msgid ""
"C# support for Godot has historically used the `Mono <https://www.mono-"
"project.com/>`_ runtime instead of the `.NET Runtime <https://github.com/"
"dotnet/runtime>`_ and internally many things are still named ``mono`` "
"instead of ``dotnet`` or otherwise referred to as ``mono``."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_with_dotnet.rst:24
msgid ""
"By default, the .NET module is disabled when building. To enable it, add the "
"option ``module_mono_enabled=yes`` to the SCons command line, while "
"otherwise following the instructions for building the desired Godot binaries."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_with_dotnet.rst:29
msgid "Generate the glue"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_with_dotnet.rst:31
msgid ""
"Parts of the sources of the managed libraries are generated from the "
"ClassDB. These source files must be generated before building the managed "
"libraries. They can be generated by any .NET-enabled Godot editor binary by "
"running it with the parameters ``--headless --generate-mono-glue`` followed "
"by the path to an output directory. This path must be ``modules/mono/glue`` "
"in the Godot directory::"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_with_dotnet.rst:40
msgid ""
"This command will tell Godot to generate the C# bindings for the Godot API "
"at ``modules/mono/glue/GodotSharp/GodotSharp/Generated``, and the C# "
"bindings for the editor tools at ``modules/mono/glue/GodotSharp/"
"GodotSharpEditor/Generated``. Once these files are generated, you can build "
"Godot's managed libraries for all the desired targets without having to "
"repeat this process."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_with_dotnet.rst:46
msgid ""
"``<godot_binary>`` refers to the editor binary you compiled with the .NET "
"module enabled. Its exact name will differ based on your system and "
"configuration, but should be of the form ``bin/godot.<platform>.editor."
"<arch>.mono``, e.g. ``bin/godot.linuxbsd.editor.x86_64.mono`` or ``bin/godot."
"windows.editor.x86_32.mono.exe``. Be especially aware of the **.mono** "
"suffix! If you've previously compiled Godot without .NET support, you might "
"have similarly named binaries without this suffix. These binaries can't be "
"used to generate the .NET glue."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_with_dotnet.rst:55
msgid ""
"The glue sources must be regenerated every time the ClassDB-registered API "
"changes. That is, for example, when a new method is registered to the "
"scripting API or one of the parameters of such a method changes. Godot will "
"print an error at startup if there is an API mismatch between ClassDB and "
"the glue sources."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_with_dotnet.rst:62
#, fuzzy
msgid "Building the managed libraries"
msgstr "Kreiranje Sadržaja"

#: ../../docs/contributing/development/compiling/compiling_with_dotnet.rst:64
msgid ""
"Once you have generated the .NET glue, you can build the managed libraries "
"with the ``build_assemblies.py`` script::"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_with_dotnet.rst:69
msgid ""
"If everything went well, the ``GodotSharp`` directory, containing the "
"managed libraries, should have been created in the ``bin`` directory."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_with_dotnet.rst:72
msgid ""
"By default, all development builds share a version number, which can cause "
"some issues with caching of the NuGet packages. To solve this issue either "
"use ``GODOT_VERSION_STATUS`` to give every build a unique version or delete "
"``GodotNuGetFallbackFolder`` after every build to clear the package cache."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_with_dotnet.rst:78
msgid ""
"Unlike \"classical\" Godot builds, when building with the .NET module "
"enabled (and depending on the target platform), a data directory may be "
"created both for the editor and for exported projects. This directory is "
"important for proper functioning and must be distributed together with "
"Godot. More details about this directory in :ref:`Data "
"directory<compiling_with_dotnet_data_directory>`."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_with_dotnet.rst:86
msgid "Build Platform"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_with_dotnet.rst:88
msgid ""
"Provide the ``--godot-platform=<platform>`` argument to control for which "
"platform specific the libraries are built. Omit this argument to build for "
"the current system."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_with_dotnet.rst:92
msgid ""
"This currently only controls the inclusion of the support for Visual Studio "
"as an external editor, the libraries are otherwise identical."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_with_dotnet.rst:96
msgid "NuGet packages"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_with_dotnet.rst:98
msgid ""
"The API assemblies, source generators, and custom MSBuild project SDK are "
"distributed as NuGet packages. This is all transparent to the user, but it "
"can make things complicated during development."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_with_dotnet.rst:102
msgid ""
"In order to use Godot with a development version of those packages, a local "
"NuGet source must be created where MSBuild can find them."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_with_dotnet.rst:105
msgid ""
"First, pick a location for the local NuGet source. If you don't have a "
"preference, create an empty directory at one of these recommended locations:"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_with_dotnet.rst:108
msgid "On Windows, ``C:\\Users\\<username>\\MyLocalNugetSource``"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_with_dotnet.rst:109
msgid "On Linux, \\*BSD, etc., ``~/MyLocalNugetSource``"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_with_dotnet.rst:111
msgid "This path is referred to later as ``<my_local_source>``."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_with_dotnet.rst:113
msgid ""
"After picking a directory, run this .NET CLI command to configure NuGet to "
"use your local source:"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_with_dotnet.rst:120
msgid ""
"When you run the ``build_assemblies.py`` script, pass ``<my_local_source>`` "
"to the ``--push-nupkgs-local`` option:"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_with_dotnet.rst:127
msgid ""
"This option ensures the packages will be added to the specified local NuGet "
"source and that conflicting versions of the package are removed from the "
"NuGet cache. It's recommended to always use this option when building the C# "
"solutions during development to avoid mistakes."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_with_dotnet.rst:133
msgid "Double Precision Support (REAL_T_IS_DOUBLE)"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_with_dotnet.rst:135
msgid ""
"When building Godot with double precision support, i.e. the "
"``precision=double`` argument for scons, the managed libraries must be "
"adjusted to match by passing the ``--precision=double`` argument:"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_with_dotnet.rst:147
msgid "Example (Windows)"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_with_dotnet.rst:164
msgid "Example (Linux, \\*BSD)"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_with_dotnet.rst:182
msgid "Data directory"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_with_dotnet.rst:184
msgid ""
"The data directory is a dependency for Godot binaries built with the .NET "
"module enabled. It contains important files for the correct functioning of "
"Godot. It must be distributed together with the Godot executable."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_with_dotnet.rst:191
msgid ""
"The name of the data directory for the Godot editor will always be "
"``GodotSharp``. This directory contains an ``Api`` subdirectory with the "
"Godot API assemblies and a ``Tools`` subdirectory with the tools required by "
"the editor, like the ``GodotTools`` assemblies and its dependencies."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_with_dotnet.rst:196
msgid ""
"On macOS, if the Godot editor is distributed as a bundle, the ``GodotSharp`` "
"directory may be placed in the ``<bundle_name>.app/Contents/Resources/`` "
"directory inside the bundle."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_with_dotnet.rst:203
msgid ""
"The data directory for exported projects is generated by the editor during "
"the export. It is named ``data_<APPNAME>_<ARCH>``, where ``<APPNAME>`` is "
"the application name as specified in the project setting ``application/"
"config/name`` and ``<ARCH>`` is the current architecture of the export."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_with_dotnet.rst:208
msgid ""
"In the case of multi-architecture exports multiple such data directories "
"will be generated."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_with_dotnet.rst:212
msgid "Command-line options"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_with_dotnet.rst:214
msgid ""
"The following is the list of command-line options available when building "
"with the .NET module:"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_with_dotnet.rst:217
msgid "**module_mono_enabled**\\ =yes | **no**"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_with_dotnet.rst:219
msgid "Build Godot with the .NET module enabled."
msgstr ""

#: ../../docs/contributing/development/compiling/optimizing_for_size.rst:4
msgid "Optimizing a build for size"
msgstr ""

#: ../../docs/contributing/development/compiling/optimizing_for_size.rst:11
msgid ""
"Sometimes, it is desired to optimize a build for size rather than speed. "
"This means not compiling unused functions from the engine, as well as using "
"specific compiler flags to aid on decreasing build size. Common situations "
"include creating builds for mobile and Web platforms."
msgstr ""

#: ../../docs/contributing/development/compiling/optimizing_for_size.rst:16
msgid ""
"This tutorial aims to give an overview on different methods to create a "
"smaller binary. Before continuing, it is recommended to read the previous "
"tutorials on compiling Godot for each platform."
msgstr ""

#: ../../docs/contributing/development/compiling/optimizing_for_size.rst:20
msgid ""
"The options below are listed from the most important (greatest size savings) "
"to the least important (lowest size savings)."
msgstr ""

#: ../../docs/contributing/development/compiling/optimizing_for_size.rst:24
msgid "Stripping binaries"
msgstr ""

#: ../../docs/contributing/development/compiling/optimizing_for_size.rst:26
msgid "**Space savings:** Very high"
msgstr ""

#: ../../docs/contributing/development/compiling/optimizing_for_size.rst:27
#: ../../docs/contributing/development/compiling/optimizing_for_size.rst:56
#: ../../docs/contributing/development/compiling/optimizing_for_size.rst:80
#: ../../docs/contributing/development/compiling/optimizing_for_size.rst:96
#: ../../docs/contributing/development/compiling/optimizing_for_size.rst:133
#: ../../docs/contributing/development/compiling/optimizing_for_size.rst:151
msgid "**Difficulty:** Easy"
msgstr ""

#: ../../docs/contributing/development/compiling/optimizing_for_size.rst:28
#: ../../docs/contributing/development/compiling/optimizing_for_size.rst:57
msgid "**Performed in official builds:** Yes"
msgstr ""

#: ../../docs/contributing/development/compiling/optimizing_for_size.rst:30
msgid ""
"If you build Windows (MinGW), Linux or macOS binaries from source, remember "
"to strip debug symbols from binaries by installing the ``strip`` package "
"from your distribution then running:"
msgstr ""

#: ../../docs/contributing/development/compiling/optimizing_for_size.rst:38
msgid "On Windows, ``strip.exe`` is included in most MinGW toolchain setups."
msgstr ""

#: ../../docs/contributing/development/compiling/optimizing_for_size.rst:40
msgid ""
"This will reduce the size of compiled binaries by a factor between 5× and "
"10×. The downside is that crash backtraces will no longer provide accurate "
"information (which is useful for troubleshooting the cause of a crash). :ref:"
"`C++ profilers <doc_using_cpp_profilers>` will also no longer be able to "
"display function names (this does not affect the built-in GDScript profiler)."
msgstr ""

#: ../../docs/contributing/development/compiling/optimizing_for_size.rst:48
msgid ""
"The above command will not work on Windows binaries compiled with MSVC and "
"platforms such as Android and Web. Instead, pass ``debug_symbols=no`` on the "
"SCons command line when compiling."
msgstr ""

#: ../../docs/contributing/development/compiling/optimizing_for_size.rst:53
msgid "Compiling with link-time optimization"
msgstr ""

#: ../../docs/contributing/development/compiling/optimizing_for_size.rst:55
#: ../../docs/contributing/development/compiling/optimizing_for_size.rst:79
#: ../../docs/contributing/development/compiling/optimizing_for_size.rst:95
msgid "**Space savings:** High"
msgstr ""

#: ../../docs/contributing/development/compiling/optimizing_for_size.rst:59
msgid ""
"Enabling link-time optimization produces more efficient binaries, both in "
"terms of performance and file size. It works by eliminating duplicate "
"template functions and unused code. It can currently be used with the GCC "
"and MSVC compilers:"
msgstr ""

#: ../../docs/contributing/development/compiling/optimizing_for_size.rst:68
msgid ""
"Linking becomes much slower and more RAM-consuming with this option, so it "
"should be used only for release builds:"
msgstr ""

#: ../../docs/contributing/development/compiling/optimizing_for_size.rst:71
msgid ""
"When compiling the ``master`` branch, you need to have at least 8 GB of RAM "
"available for successful linking with LTO enabled."
msgstr ""

#: ../../docs/contributing/development/compiling/optimizing_for_size.rst:73
msgid ""
"When compiling the ``3.x`` branch, you need to have at least 6 GB of RAM "
"available for successful linking with LTO enabled."
msgstr ""

#: ../../docs/contributing/development/compiling/optimizing_for_size.rst:77
msgid "Optimizing for size instead of speed"
msgstr ""

#: ../../docs/contributing/development/compiling/optimizing_for_size.rst:81
msgid "**Performed in official builds:** Yes, but only for web builds"
msgstr ""

#: ../../docs/contributing/development/compiling/optimizing_for_size.rst:83
msgid ""
"Godot 3.1 onwards allows compiling using size optimizations (instead of "
"speed). To enable this, set the ``optimize`` flag to ``size``:"
msgstr ""

#: ../../docs/contributing/development/compiling/optimizing_for_size.rst:90
msgid "Some platforms such as WebAssembly already use this mode by default."
msgstr ""

#: ../../docs/contributing/development/compiling/optimizing_for_size.rst:93
msgid "Disabling advanced text server"
msgstr ""

#: ../../docs/contributing/development/compiling/optimizing_for_size.rst:97
#: ../../docs/contributing/development/compiling/optimizing_for_size.rst:134
#: ../../docs/contributing/development/compiling/optimizing_for_size.rst:152
#: ../../docs/contributing/development/compiling/optimizing_for_size.rst:193
msgid "**Performed in official builds:** No"
msgstr ""

#: ../../docs/contributing/development/compiling/optimizing_for_size.rst:99
msgid ""
"By default, Godot uses an advanced text server with the support for the "
"following features:"
msgstr ""

#: ../../docs/contributing/development/compiling/optimizing_for_size.rst:102
msgid ""
"Right-to-left typesetting and complex scripts, required to write languages "
"such as Arabic and Hebrew."
msgstr ""

#: ../../docs/contributing/development/compiling/optimizing_for_size.rst:104
msgid ""
"Font ligatures and OpenType features (such as small capitals, fractions and "
"slashed zero)."
msgstr ""

#: ../../docs/contributing/development/compiling/optimizing_for_size.rst:107
msgid ""
"Godot provides a fallback text server that isn't compiled by default. This "
"text server can be used as a lightweight alternative to the default advanced "
"text server:"
msgstr ""

#: ../../docs/contributing/development/compiling/optimizing_for_size.rst:115
msgid ""
"If you only intend on supporting Latin, Greek and Cyrillic-based languages "
"in your project, the fallback text server should suffice."
msgstr ""

#: ../../docs/contributing/development/compiling/optimizing_for_size.rst:118
msgid ""
"This fallback text server can also process large amounts of text more "
"quickly than the advanced text server. This makes the fallback text server a "
"good fit for mobile/web projects."
msgstr ""

#: ../../docs/contributing/development/compiling/optimizing_for_size.rst:124
msgid ""
"Remember to always pass ``module_text_server_fb_enabled=yes`` when using "
"``module_text_server_adv_enabled=no``. Otherwise, the compiled binary won't "
"contain any text server, which means no text will be displayed at all when "
"running the project."
msgstr ""

#: ../../docs/contributing/development/compiling/optimizing_for_size.rst:130
msgid "Disabling 3D"
msgstr ""

#: ../../docs/contributing/development/compiling/optimizing_for_size.rst:132
#: ../../docs/contributing/development/compiling/optimizing_for_size.rst:150
msgid "**Space savings:** Moderate"
msgstr ""

#: ../../docs/contributing/development/compiling/optimizing_for_size.rst:136
msgid ""
"For 2D games, having the whole 3D engine available usually makes no sense. "
"Because of this, there is a build flag to disable it:"
msgstr ""

#: ../../docs/contributing/development/compiling/optimizing_for_size.rst:143
msgid ""
"Tools must be disabled in order to use this flag, as the editor is not "
"designed to operate without 3D support. Without it, the binary size can be "
"reduced by about 15%."
msgstr ""

#: ../../docs/contributing/development/compiling/optimizing_for_size.rst:148
msgid "Disabling advanced GUI objects"
msgstr ""

#: ../../docs/contributing/development/compiling/optimizing_for_size.rst:154
msgid ""
"Most small games don't require complex GUI controls such as Tree, ItemList, "
"TextEdit or GraphEdit. They can be disabled using a build flag:"
msgstr ""

#: ../../docs/contributing/development/compiling/optimizing_for_size.rst:161
msgid "This is everything that will be disabled:"
msgstr ""

#: ../../docs/contributing/development/compiling/optimizing_for_size.rst:163
msgid "FileDialog"
msgstr ""

#: ../../docs/contributing/development/compiling/optimizing_for_size.rst:164
msgid "PopupMenu"
msgstr ""

#: ../../docs/contributing/development/compiling/optimizing_for_size.rst:165
msgid "Tree"
msgstr ""

#: ../../docs/contributing/development/compiling/optimizing_for_size.rst:166
#, fuzzy
msgid "TextEdit"
msgstr "Tutorijali"

#: ../../docs/contributing/development/compiling/optimizing_for_size.rst:167
#, fuzzy
msgid "CodeEdit"
msgstr "Tutorijali"

#: ../../docs/contributing/development/compiling/optimizing_for_size.rst:168
msgid "SyntaxHighlighter"
msgstr ""

#: ../../docs/contributing/development/compiling/optimizing_for_size.rst:169
msgid "CodeHighlighter"
msgstr ""

#: ../../docs/contributing/development/compiling/optimizing_for_size.rst:170
msgid "TreeItem"
msgstr ""

#: ../../docs/contributing/development/compiling/optimizing_for_size.rst:171
msgid "OptionButton"
msgstr ""

#: ../../docs/contributing/development/compiling/optimizing_for_size.rst:172
msgid "SpinBox"
msgstr ""

#: ../../docs/contributing/development/compiling/optimizing_for_size.rst:173
msgid "ColorPicker"
msgstr ""

#: ../../docs/contributing/development/compiling/optimizing_for_size.rst:174
msgid "ColorPickerButton"
msgstr ""

#: ../../docs/contributing/development/compiling/optimizing_for_size.rst:175
msgid "RichTextlabel"
msgstr ""

#: ../../docs/contributing/development/compiling/optimizing_for_size.rst:176
msgid "RichTextEffect"
msgstr ""

#: ../../docs/contributing/development/compiling/optimizing_for_size.rst:177
msgid "CharFXTransform"
msgstr ""

#: ../../docs/contributing/development/compiling/optimizing_for_size.rst:178
msgid "AcceptDialog"
msgstr ""

#: ../../docs/contributing/development/compiling/optimizing_for_size.rst:179
msgid "ConfirmationDialog"
msgstr ""

#: ../../docs/contributing/development/compiling/optimizing_for_size.rst:180
#, fuzzy
msgid "MarginContainer"
msgstr "Kreiranje Sadržaja"

#: ../../docs/contributing/development/compiling/optimizing_for_size.rst:182
#, fuzzy
msgid "SplitContainer"
msgstr "Kreiranje Sadržaja"

#: ../../docs/contributing/development/compiling/optimizing_for_size.rst:183
#, fuzzy
msgid "HSplitContainer"
msgstr "Kreiranje Sadržaja"

#: ../../docs/contributing/development/compiling/optimizing_for_size.rst:184
#, fuzzy
msgid "VSplitContainer"
msgstr "Kreiranje Sadržaja"

#: ../../docs/contributing/development/compiling/optimizing_for_size.rst:185
msgid "GraphNode"
msgstr ""

#: ../../docs/contributing/development/compiling/optimizing_for_size.rst:189
msgid "Disabling unwanted modules"
msgstr ""

#: ../../docs/contributing/development/compiling/optimizing_for_size.rst:191
msgid "**Space savings:** Very low to moderate depending on modules"
msgstr ""

#: ../../docs/contributing/development/compiling/optimizing_for_size.rst:192
msgid "**Difficulty:** Medium to hard depending on modules"
msgstr ""

#: ../../docs/contributing/development/compiling/optimizing_for_size.rst:195
msgid ""
"A lot of Godot's functions are offered as modules. You can see a list of "
"modules with the following command:"
msgstr ""

#: ../../docs/contributing/development/compiling/optimizing_for_size.rst:202
msgid ""
"The list of modules that can be disabled will appear, together with all "
"build options. If you are working on a simple 2D game, you could disable a "
"lot of them:"
msgstr ""

#: ../../docs/contributing/development/compiling/optimizing_for_size.rst:210
msgid ""
"If this proves not to work for your use case, you should review the list of "
"modules and see which ones you actually still need for your game (e.g. you "
"might want to keep networking-related modules, regex support, ``minimp3``/"
"``ogg``/``vorbis`` to play music, or ``theora`` to play videos)."
msgstr ""

#: ../../docs/contributing/development/compiling/optimizing_for_size.rst:215
msgid ""
"Alternatively, you can supply a list of disabled modules by creating "
"``custom.py`` at the root of the source, with the contents similar to the "
"following:"
msgstr ""

#: ../../docs/contributing/development/compiling/optimizing_for_size.rst:260
#, fuzzy
msgid ":ref:`doc_overriding_build_options`."
msgstr "Kreiranje Sadržaja"

#: ../../docs/contributing/development/compiling/optimizing_for_size.rst:263
msgid "Optimizing the distribution of your project"
msgstr ""

#: ../../docs/contributing/development/compiling/optimizing_for_size.rst:266
msgid "Desktop"
msgstr ""

#: ../../docs/contributing/development/compiling/optimizing_for_size.rst:270
msgid ""
"This section is only relevant when distributing the files on a desktop "
"platform that doesn't perform its own compression or packing. As such, this "
"advice is relevant when you distribute ZIP archives on itch.io or GitHub "
"Releases."
msgstr ""

#: ../../docs/contributing/development/compiling/optimizing_for_size.rst:275
msgid ""
"Platforms like Steam already apply their own compression scheme, so you "
"don't need to create a ZIP archive to distribute files in the first place."
msgstr ""

#: ../../docs/contributing/development/compiling/optimizing_for_size.rst:278
msgid ""
"As an aside, you can look into optimizing the distribution of your project "
"itself. This can be done even without recompiling the export template."
msgstr ""

#: ../../docs/contributing/development/compiling/optimizing_for_size.rst:281
msgid ""
"`7-Zip <https://7-zip.org/>`__ can be used to create ZIP archives that are "
"more efficient than usual, while remaining compatible with every ZIP "
"extractor (including Windows' own built-in extractor). ZIP size reduction in "
"a large project can reach dozens of megabytes compared to a typical ZIP "
"compressor, although average savings are in the 1-5 MB range. Creating this "
"ZIP archive will take longer than usual, but it will extract just as fast as "
"any other ZIP archive."
msgstr ""

#: ../../docs/contributing/development/compiling/optimizing_for_size.rst:289
msgid ""
"When using the 7-Zip GUI, this is done by creating a ZIP archive with the "
"Ultra compression mode. When using the command line, this is done using the "
"following command:"
msgstr ""

#: ../../docs/contributing/development/compiling/optimizing_for_size.rst:300
msgid ""
"Enabling gzip or Brotli compression for all file types from the web export "
"(especially the ``.wasm`` and ``.pck``) can reduce the download size "
"significantly, leading to faster loading times, especially on slow "
"connections."
msgstr ""

#: ../../docs/contributing/development/compiling/optimizing_for_size.rst:304
msgid ""
"Creating precompressed gzip or Brotli files with a high compression level "
"can be even more efficient, as long as the web server is configured to serve "
"those files when they exist. When supported, Brotli should be preferred over "
"gzip as it has a greater potential for file size reduction."
msgstr ""

#: ../../docs/contributing/development/compiling/optimizing_for_size.rst:309
#, fuzzy
msgid "See :ref:`doc_exporting_for_web_serving_the_files` for instructions."
msgstr "Kreiranje Sadržaja"

#: ../../docs/contributing/development/compiling/compiling_with_script_encryption_key.rst:4
#, fuzzy
msgid "Compiling with PCK encryption key"
msgstr "Kreiranje Sadržaja"

#: ../../docs/contributing/development/compiling/compiling_with_script_encryption_key.rst:8
msgid ""
"The export dialog gives you the option to encrypt your PCK file with a 256-"
"bit AES key when releasing your project. This will make sure your scenes, "
"scripts and other resources are not stored in plain text and can not easily "
"be ripped by some script kiddie."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_with_script_encryption_key.rst:13
msgid ""
"Of course, the key needs to be stored in the binary, but if it's compiled, "
"optimized and without symbols, it would take some effort to find it."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_with_script_encryption_key.rst:16
msgid ""
"For this to work, you need to build the export templates from source, with "
"that same key."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_with_script_encryption_key.rst:21
msgid ""
"This will **not** work if you use official, precompiled export templates. It "
"is absolutely **required** to compile your own export templates to use PCK "
"encryption."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_with_script_encryption_key.rst:27
msgid ""
"By default, Android exports store assets directly in the APK file and aren't "
"affected by PCK encryption. To use PCK encryption on Android, enable **APK "
"expansion** in the export options."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_with_script_encryption_key.rst:34
msgid ""
"Generate a 256-bit AES key in hexadecimal format. You can use the aes-256-"
"cbc variant from `this service <https://asecuritysite.com/encryption/"
"keygen>`_."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_with_script_encryption_key.rst:37
msgid ""
"Alternatively, you can generate it yourself using `OpenSSL <https://www."
"openssl.org/>`__ command-line tools:"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_with_script_encryption_key.rst:44
msgid "The output in ``godot.gdkey`` should be similar to:"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_with_script_encryption_key.rst:51
msgid ""
"You can generate the key without redirecting the output to a file, but that "
"way you can minimize the risk of exposing the key."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_with_script_encryption_key.rst:54
msgid ""
"Set this key as environment variable in the console that you will use to "
"compile Godot, like this:"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_with_script_encryption_key.rst:70
msgid ""
"Compile Godot export templates and set them as custom export templates in "
"the export preset options."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_with_script_encryption_key.rst:73
msgid "Set the encryption key in the **Encryption** tab of the export preset:"
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_with_script_encryption_key.rst:77
msgid ""
"Add filters for the files/folders to encrypt. **By default**, include "
"filters are empty and **nothing will be encrypted**."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_with_script_encryption_key.rst:80
msgid ""
"Export the project. The project should run with the files encrypted now."
msgstr ""

#: ../../docs/contributing/development/compiling/compiling_with_script_encryption_key.rst:85
msgid ""
"If you get an error like below, it means the key wasn't properly included in "
"your Godot build. Godot is encrypting PCK file during export, but can't read "
"it at runtime."
msgstr ""

#: ../../docs/contributing/development/debugging/index.rst:2
#, fuzzy
msgid "Debugging and profiling"
msgstr "Kreiranje Sadržaja"

#: ../../docs/contributing/development/debugging/index.rst:4
msgid ""
"This section contains pages that provide guidance if you're looking at the "
"engine code trying to find an underlying issue or an optimization "
"possibility."
msgstr ""

#: ../../docs/contributing/development/debugging/index.rst:17
#, fuzzy
msgid "Debugging the editor"
msgstr "Kreiranje Sadržaja"

#: ../../docs/contributing/development/debugging/index.rst:19
msgid ""
"When working on the Godot editor keep in mind that by default the executable "
"will start in the Project Manager mode. Opening a project from the Project "
"Manager spawns a new process, which stops the debugging session. To avoid "
"that you should launch directly into the project using ``-e`` and ``--path`` "
"launch options."
msgstr ""

#: ../../docs/contributing/development/debugging/index.rst:25
msgid "For example, using ``gdb`` directly, you may do this:"
msgstr ""

#: ../../docs/contributing/development/debugging/index.rst:32
msgid ""
"You can also run the editor directly from your project's folder. In that "
"case, only the ``-e`` option is required."
msgstr ""

#: ../../docs/contributing/development/debugging/index.rst:41
msgid ""
"You can learn more about these launch options and other command line "
"arguments in the :ref:`command line tutorial <doc_command_line_tutorial>`."
msgstr ""

#: ../../docs/contributing/development/debugging/index.rst:44
msgid ""
"If you're using a code editor or an IDE to debug Godot, check out our :ref:"
"`configuration guides <doc_configuring_an_ide>`, which cover the setup "
"process for building and debugging with your particular editor."
msgstr ""

#: ../../docs/contributing/development/debugging/using_cpp_profilers.rst:4
#, fuzzy
msgid "Using C++ profilers"
msgstr "Kreiranje Sadržaja"

#: ../../docs/contributing/development/debugging/using_cpp_profilers.rst:6
msgid ""
"To optimize Godot's performance, you need to know what to optimize first. To "
"this end, profilers are useful tools."
msgstr ""

#: ../../docs/contributing/development/debugging/using_cpp_profilers.rst:11
msgid ""
"There is a :ref:`built-in GDScript profiler <doc_the_profiler>` in the "
"editor, but using C++ profiler may be useful in cases where the GDScript "
"profiler is not accurate enough or is missing information due to bugs in the "
"profiler."
msgstr ""

#: ../../docs/contributing/development/debugging/using_cpp_profilers.rst:16
msgid "Recommended profilers"
msgstr ""

#: ../../docs/contributing/development/debugging/using_cpp_profilers.rst:18
msgid "`VerySleepy <http://www.codersnotes.com/sleepy/>`__ (Windows only)"
msgstr ""

#: ../../docs/contributing/development/debugging/using_cpp_profilers.rst:19
msgid "`HotSpot <https://github.com/KDAB/hotspot>`__ (Linux only)"
msgstr ""

#: ../../docs/contributing/development/debugging/using_cpp_profilers.rst:20
msgid "`Xcode Instruments <https://developer.apple.com/xcode/>`__ (macOS only)"
msgstr ""

#: ../../docs/contributing/development/debugging/using_cpp_profilers.rst:22
msgid ""
"These profilers may not be the most powerful or flexible options, but their "
"standalone operation and limited feature set tends to make them easier to "
"use."
msgstr ""

#: ../../docs/contributing/development/debugging/using_cpp_profilers.rst:26
msgid "Setting up Godot"
msgstr ""

#: ../../docs/contributing/development/debugging/using_cpp_profilers.rst:28
msgid ""
"To get useful profiling information, it is **absolutely required** to use a "
"Godot build that includes debugging symbols. Official binaries do not "
"include debugging symbols, since these would make the download size "
"significantly larger."
msgstr ""

#: ../../docs/contributing/development/debugging/using_cpp_profilers.rst:32
msgid ""
"To get profiling data that best matches the production environment (but with "
"debugging symbols), you should compile binaries with the ``production=yes "
"debug_symbols=yes`` SCons options."
msgstr ""

#: ../../docs/contributing/development/debugging/using_cpp_profilers.rst:35
msgid ""
"It is possible to run a profiler on less optimized builds (e.g. "
"``target=template_debug`` without LTO), but results will naturally be less "
"representative of real world conditions."
msgstr ""

#: ../../docs/contributing/development/debugging/using_cpp_profilers.rst:40
msgid ""
"Do *not* strip debugging symbols on the binaries using the ``strip`` command "
"after compiling the binaries. Otherwise, you will no longer get useful "
"profiling information when running a profiler."
msgstr ""

#: ../../docs/contributing/development/debugging/using_cpp_profilers.rst:45
msgid "Benchmarking startup/shutdown times"
msgstr ""

#: ../../docs/contributing/development/debugging/using_cpp_profilers.rst:47
msgid ""
"If you're looking into optimizing Godot's startup/shutdown performance, you "
"can tell the profiler to use the ``--quit`` command line option on the Godot "
"binary. This will exit Godot just after it finished starting. The ``--quit`` "
"option works with ``--editor``, ``--project-manager`` or ``--path <path to "
"project directory>`` (which runs a project directly)."
msgstr ""

#: ../../docs/contributing/development/debugging/using_cpp_profilers.rst:55
msgid ""
"See :ref:`doc_command_line_tutorial` for more command line arguments "
"supported by Godot."
msgstr ""

#: ../../docs/contributing/development/debugging/using_cpp_profilers.rst:59
msgid "Profiler-specific instructions"
msgstr ""

#: ../../docs/contributing/development/debugging/using_cpp_profilers.rst:62
msgid "VerySleepy"
msgstr ""

#: ../../docs/contributing/development/debugging/using_cpp_profilers.rst:64
msgid ""
"Start the Godot editor or your project first. If you start the Project "
"Manager, make sure to edit or run a project first. Otherwise, the profiler "
"will not track the child process since the Project Manager will spawn a "
"child process for every project edited or run."
msgstr ""

#: ../../docs/contributing/development/debugging/using_cpp_profilers.rst:68
msgid ""
"Open VerySleepy and select the Godot executable in the list of processes on "
"the left:"
msgstr ""

#: ../../docs/contributing/development/debugging/using_cpp_profilers.rst:72
msgid "Click the **Profile All** button on the right to start profiling."
msgstr ""

#: ../../docs/contributing/development/debugging/using_cpp_profilers.rst:73
msgid ""
"Perform the actions you wish to profile in the editor or project. When "
"you're done, click **Stop** (*not* Abort)."
msgstr ""

#: ../../docs/contributing/development/debugging/using_cpp_profilers.rst:74
msgid "Wait for the results window to appear."
msgstr ""

#: ../../docs/contributing/development/debugging/using_cpp_profilers.rst:75
msgid ""
"Once the results window appears, filter the view to remove external modules "
"(such as the graphics driver). You can filter by module by finding a line "
"whose **Module** matches the Godot executable name, right-clicking that line "
"then choosing **Filter Module to <Godot executable name>** in the dropdown "
"that appears."
msgstr ""

#: ../../docs/contributing/development/debugging/using_cpp_profilers.rst:79
msgid "Your results window should now look something like this:"
msgstr ""

#: ../../docs/contributing/development/debugging/using_cpp_profilers.rst:84
msgid "HotSpot"
msgstr ""

#: ../../docs/contributing/development/debugging/using_cpp_profilers.rst:86
msgid "Open HotSpot. Click **Record Data**:"
msgstr ""

#: ../../docs/contributing/development/debugging/using_cpp_profilers.rst:90
msgid ""
"In the next window, specify the path to the Godot binary that includes debug "
"symbols."
msgstr ""

#: ../../docs/contributing/development/debugging/using_cpp_profilers.rst:91
msgid ""
"Specify command line arguments to run a specific project, with or without "
"the editor."
msgstr ""

#: ../../docs/contributing/development/debugging/using_cpp_profilers.rst:92
msgid ""
"The path to the working directory can be anything if an absolute path is "
"used for the ``--path`` command line argument. Otherwise, it must be set to "
"that the relative path to the project is valid."
msgstr ""

#: ../../docs/contributing/development/debugging/using_cpp_profilers.rst:95
msgid ""
"Make sure **Elevate Privileges** is checked if you have administrative "
"privileges. While not essential for profiling Godot, this will ensure all "
"events can be captured. Otherwise, some events may be missing in the "
"capture. Your settings should now look something like this:"
msgstr ""

#: ../../docs/contributing/development/debugging/using_cpp_profilers.rst:102
msgid ""
"Click **Start Recording** and perform the actions you wish to profile in the "
"editor/project."
msgstr ""

#: ../../docs/contributing/development/debugging/using_cpp_profilers.rst:103
msgid ""
"Quit the editor/project normally or use the **Stop Profiling** button in "
"HotSpot to stop profiling early. Stopping profiling early can result in "
"cleaner profiles if you're not interested in the engine's quit procedure."
msgstr ""

#: ../../docs/contributing/development/debugging/using_cpp_profilers.rst:106
msgid ""
"Click **View Results** and wait for the profiling visualization to be "
"generated:"
msgstr ""

#: ../../docs/contributing/development/debugging/using_cpp_profilers.rst:110
msgid ""
"Use the tabs at the top to navigate between the different views. These views "
"show the same data, but in different ways. The **Flame Graph** tab is a good "
"way to see which functions take up the most time at a glance. These "
"functions are therefore the most important ones to optimize, since "
"optimizing them will improve performance the most."
msgstr ""

#: ../../docs/contributing/development/debugging/using_cpp_profilers.rst:115
msgid ""
"At the bottom of all tabs except **Summary**, you will also see a list of "
"CPU threads started by the engine among with the CPU utilization for each "
"thread. This lets you see threads that can be a bottleneck at a given point "
"in time."
msgstr ""

#: ../../docs/contributing/development/debugging/using_cpp_profilers.rst:123
msgid ""
"If you don't want the startup procedure to be included in the profile, you "
"can also attach HotSpot to a running process by clicking **Record Data** "
"then setting the **Launch Application** dropdown option to **Attach To "
"Process(es)**."
msgstr ""

#: ../../docs/contributing/development/debugging/using_cpp_profilers.rst:128
msgid ""
"This process attachment-based workflow is similar to the one used by "
"VerySleepy."
msgstr ""

#: ../../docs/contributing/development/debugging/using_cpp_profilers.rst:131
msgid "Xcode Instruments"
msgstr ""

#: ../../docs/contributing/development/debugging/using_cpp_profilers.rst:133
msgid ""
"Open Xcode. Select **Open Developer Tool** - **Instruments** from the "
"**Xcode** app menu:"
msgstr ""

#: ../../docs/contributing/development/debugging/using_cpp_profilers.rst:134
msgid "Double-click on **Time Profiler** in the **Instruments** window:"
msgstr ""

#: ../../docs/contributing/development/debugging/using_cpp_profilers.rst:138
msgid ""
"In the Time Profiler window, click on the **Target** menu, select **Choose "
"target...** and specify the path to the Godot binary, command line arguments "
"and environment variables in the next window."
msgstr ""

#: ../../docs/contributing/development/debugging/using_cpp_profilers.rst:144
msgid ""
"You can also attach the Time Profiler to a running process by selecting it "
"from the **Target** menu."
msgstr ""

#: ../../docs/contributing/development/debugging/using_cpp_profilers.rst:147
msgid ""
"Click the **Start an immediate mode recording** button to start profiling."
msgstr ""

#: ../../docs/contributing/development/debugging/using_cpp_profilers.rst:151
msgid ""
"Perform the actions you wish to profile in the editor or project. When "
"you're done, click the **Stop** button."
msgstr ""

#: ../../docs/contributing/development/debugging/using_cpp_profilers.rst:154
msgid "Wait for the results to appear."
msgstr ""

#: ../../docs/contributing/development/debugging/using_cpp_profilers.rst:155
msgid ""
"At the bottom of the window you will see a call tree for all CPU threads "
"started, and the **Heaviest Stack Trace** overview."
msgstr ""

#: ../../docs/contributing/development/debugging/using_cpp_profilers.rst:157
msgid ""
"Select **Hide system libraries** in the **Call Tree** menu (at the bottom of "
"window) to remove external modules."
msgstr ""

#: ../../docs/contributing/development/debugging/using_cpp_profilers.rst:159
msgid ""
"You can use the timeline at the top of the window to display details for the "
"specific time period."
msgstr ""

#: ../../docs/contributing/development/debugging/using_sanitizers.rst:4
#, fuzzy
msgid "Using sanitizers"
msgstr "Kreiranje Sadržaja"

#: ../../docs/contributing/development/debugging/using_sanitizers.rst:7
msgid "What are sanitizers?"
msgstr ""

#: ../../docs/contributing/development/debugging/using_sanitizers.rst:9
msgid ""
"Sanitizers are static instrumentation tools that help find bugs that "
"traditional debuggers usually cannot catch. This is particularly useful when "
"combined with :ref:`doc_unit_testing` in continuous integration."
msgstr ""

#: ../../docs/contributing/development/debugging/using_sanitizers.rst:13
msgid ""
"Sanitizers can be used on Windows, macOS and Linux by using the Clang "
"(LLVM), GCC or Visual Studio compilers. :ref:`Certain platforms "
"<doc_using_sanitizers_platform_specific_sanitizers>` may also have their own "
"sanitizers available. In situations where a single sanitizer is provided by "
"several different compilers, remember that their output and behavior will "
"differ slightly."
msgstr ""

#: ../../docs/contributing/development/debugging/using_sanitizers.rst:21
#, fuzzy
msgid "Using sanitizers on Godot"
msgstr "Kreiranje Sadržaja"

#: ../../docs/contributing/development/debugging/using_sanitizers.rst:23
msgid ""
"Sanitizers **require** recompiling the binary. This means you cannot use "
"official Godot binaries to run sanitizers."
msgstr ""

#: ../../docs/contributing/development/debugging/using_sanitizers.rst:26
msgid ""
"When :ref:`compiling <toc-devel-compiling>` with any of the sanitizers "
"enabled, the resulting binary will have the ``.san`` suffix added to its "
"name to distinguish it from a binary without sanitizers."
msgstr ""

#: ../../docs/contributing/development/debugging/using_sanitizers.rst:30
msgid ""
"There is a performance impact as many additional runtime checks need to be "
"performed. Memory utilization will also increase. It is possible to enable "
"certain combinations of multiple sanitizers in a single build. Beware of the "
"performance impact when using multiple sanitizers at once though, as the "
"resulting binary may be excessively slow."
msgstr ""

#: ../../docs/contributing/development/debugging/using_sanitizers.rst:36
msgid ""
"Certain options can be passed to sanitizers without having to recompile the "
"binary using environment variables."
msgstr ""

#: ../../docs/contributing/development/debugging/using_sanitizers.rst:42
msgid "Address sanitizer (ASAN)"
msgstr ""

#: ../../docs/contributing/development/debugging/using_sanitizers.rst:44
#: ../../docs/contributing/development/debugging/using_sanitizers.rst:77
#: ../../docs/contributing/development/debugging/using_sanitizers.rst:120
#: ../../docs/contributing/development/debugging/using_sanitizers.rst:146
msgid "Available in Clang and GCC."
msgstr ""

#: ../../docs/contributing/development/debugging/using_sanitizers.rst:45
msgid "**Supported platforms:** Linux, macOS, Windows (Visual Studio), Web"
msgstr ""

#: ../../docs/contributing/development/debugging/using_sanitizers.rst:46
msgid ""
"`Clang ASAN documentation <https://clang.llvm.org/docs/AddressSanitizer."
"html>`__"
msgstr ""

#: ../../docs/contributing/development/debugging/using_sanitizers.rst:48
msgid ""
"The address sanitizer is generally the most frequently used sanitizer. It "
"can diagnose issues such as buffer overruns and out-of-bounds access. If the "
"engine crashes with a message such as ``free(): invalid pointer``, this is "
"typically the result of a buffer overrun. (This message is printed by the C "
"runtime, not Godot.)"
msgstr ""

#: ../../docs/contributing/development/debugging/using_sanitizers.rst:54
msgid ""
"In certain situations (such as detecting uninitialized memory reads), the "
"address sanitizer doesn't suffice. The :ref:"
"`doc_using_sanitizers_memory_sanitizer` should be used instead."
msgstr ""

#: ../../docs/contributing/development/debugging/using_sanitizers.rst:58
msgid ""
"It is also possible to detect use-after-return situations by specifying the "
"``ASAN_OPTIONS=detect_stack_use_after_return=1`` environment variable before "
"*running* Godot (not when compiling it). This increases the address "
"sanitizer's runtime overhead, so only enable this feature when you actually "
"need it."
msgstr ""

#: ../../docs/contributing/development/debugging/using_sanitizers.rst:63
msgid ""
"To enable the address sanitizer in a Godot build, pass the ``use_asan=yes`` "
"SCons option when compiling. Enabling ASAN generally makes the resulting "
"binary about 2× slower."
msgstr ""

#: ../../docs/contributing/development/debugging/using_sanitizers.rst:69
#: ../../docs/contributing/development/debugging/using_sanitizers.rst:112
#: ../../docs/contributing/development/debugging/using_sanitizers.rst:138
msgid ""
"Due to a `design decision <https://stackoverflow.com/questions/36971902/why-"
"cant-clang-enable-all-sanitizers/>`__, the address, memory and thread "
"sanitizers are mutually exclusive. This means you can only use one of those "
"sanitizers in a given binary."
msgstr ""

#: ../../docs/contributing/development/debugging/using_sanitizers.rst:75
msgid "Leak sanitizer (LSAN)"
msgstr ""

#: ../../docs/contributing/development/debugging/using_sanitizers.rst:78
msgid "**Supported platforms:** Linux, Web"
msgstr ""

#: ../../docs/contributing/development/debugging/using_sanitizers.rst:79
msgid ""
"`Clang LSAN documentation <https://clang.llvm.org/docs/LeakSanitizer.html>`__"
msgstr ""

#: ../../docs/contributing/development/debugging/using_sanitizers.rst:81
msgid ""
"The leak sanitizer can detect memory leaks, which are situations where "
"memory that is no longer in use is never freed by the running program. This "
"can potentially lead to out-of-memory situations if the program runs for "
"long enough. Since Godot may run on :ref:`dedicated servers "
"<doc_exporting_for_dedicated_servers>` for months or even years without a "
"restart, it's important to fix memory leaks when they occur."
msgstr ""

#: ../../docs/contributing/development/debugging/using_sanitizers.rst:88
msgid ""
"To enable the leak sanitizer in a Godot build, pass the ``use_lsan=yes`` "
"SCons option when compiling. Enabling LSAN only has a small performance "
"overhead, but the program will be much slower to exit as leak detection "
"occurs when the program exits."
msgstr ""

#: ../../docs/contributing/development/debugging/using_sanitizers.rst:96
msgid "Memory sanitizer (MSAN)"
msgstr ""

#: ../../docs/contributing/development/debugging/using_sanitizers.rst:98
msgid "Available in Clang only, not GCC."
msgstr ""

#: ../../docs/contributing/development/debugging/using_sanitizers.rst:99
msgid "**Supported platforms:** Linux"
msgstr ""

#: ../../docs/contributing/development/debugging/using_sanitizers.rst:100
msgid ""
"`Clang MSAN documentation <https://clang.llvm.org/docs/MemorySanitizer."
"html>`__"
msgstr ""

#: ../../docs/contributing/development/debugging/using_sanitizers.rst:102
msgid ""
"The memory sanitizer complements the :ref:"
"`doc_using_sanitizers_address_sanitizer`. Unlike the address sanitizer, the "
"memory sanitizer can detect uninitialized memory reads."
msgstr ""

#: ../../docs/contributing/development/debugging/using_sanitizers.rst:106
msgid ""
"To enable the memory sanitizer in a Godot build, pass the ``use_msan=yes`` "
"SCons option when compiling. Enabling MSAN generally makes the resulting "
"binary about 3× slower."
msgstr ""

#: ../../docs/contributing/development/debugging/using_sanitizers.rst:118
msgid "Thread sanitizer (TSAN)"
msgstr ""

#: ../../docs/contributing/development/debugging/using_sanitizers.rst:121
msgid "**Supported platforms:** Linux, macOS"
msgstr ""

#: ../../docs/contributing/development/debugging/using_sanitizers.rst:122
msgid ""
"`Clang TSAN documentation <https://clang.llvm.org/docs/ThreadSanitizer."
"html>`__"
msgstr ""

#: ../../docs/contributing/development/debugging/using_sanitizers.rst:124
msgid ""
"The thread sanitizer is used to track down race conditions related to "
"multithreading. A race condition is when multiple threads try to modify the "
"same data at the same time. Since thread scheduling can be ordered in any "
"fashion by the operating system, this leads to incorrect behavior that only "
"occurs occasionally (and can be difficult to track as a result). To prevent "
"a race condition, you need to add a lock to ensure only one thread can "
"access the shared data at a given time."
msgstr ""

#: ../../docs/contributing/development/debugging/using_sanitizers.rst:132
msgid ""
"To enable the thread sanitizer in a Godot build, pass the ``use_tsan=yes`` "
"SCons option when compiling. Enabling TSAN generally makes the resulting "
"binary 10× slower, while also multiplying memory usage by an approximately "
"8× factor."
msgstr ""

#: ../../docs/contributing/development/debugging/using_sanitizers.rst:144
msgid "Undefined behavior sanitizer (UBSAN)"
msgstr ""

#: ../../docs/contributing/development/debugging/using_sanitizers.rst:147
msgid "**Supported platforms:** Linux, macOS, Web"
msgstr ""

#: ../../docs/contributing/development/debugging/using_sanitizers.rst:148
msgid ""
"`Clang UBSAN documentation <https://clang.llvm.org/docs/"
"UndefinedBehaviorSanitizer.html>`__"
msgstr ""

#: ../../docs/contributing/development/debugging/using_sanitizers.rst:150
msgid ""
"The undefined behavior sanitizer is used to track down situations where the "
"program exhibits random and unpredictable behavior. This is due to C/C++ "
"code that is accepted by the compiler, but is not *correct*. Compiling with "
"a different set of optimizations can also change the observed results of "
"undefined behavior."
msgstr ""

#: ../../docs/contributing/development/debugging/using_sanitizers.rst:156
msgid ""
"To enable the undefined behavior sanitizer in a Godot build, pass the "
"``use_ubsan=yes`` SCons option when compiling. Enabling UBSAN only has a "
"small performance overhead."
msgstr ""

#: ../../docs/contributing/development/debugging/using_sanitizers.rst:163
msgid "Platform-specific sanitizers"
msgstr ""

#: ../../docs/contributing/development/debugging/using_sanitizers.rst:168
msgid ""
"When :ref:`compiling for the Web <doc_compiling_for_web>`, there are 2 "
"additional sanitizer SCons options available:"
msgstr ""

#: ../../docs/contributing/development/debugging/using_sanitizers.rst:171
msgid ""
"``use_assertions=yes`` enables runtime Emscripten assertions, which can "
"catch various issues."
msgstr ""

#: ../../docs/contributing/development/debugging/using_sanitizers.rst:173
msgid ""
"``use_safe_heap=yes`` enables `Emscripten's SAFE_HEAP sanitizer <https://"
"emscripten.org/docs/debugging/Sanitizers.html>`__. It provides similar "
"functionality to ASAN, but it focuses on issues that are specific to "
"WebAssembly. ``SAFE_HEAP`` is not guaranteed to be compatible with ASAN and "
"UBSAN in the same binary, so you may have to build it separately."
msgstr ""

#: ../../docs/contributing/development/debugging/macos_debug.rst:2
#, fuzzy
msgid "Debugging on macOS"
msgstr "Kreiranje Sadržaja"

#: ../../docs/contributing/development/debugging/macos_debug.rst:5
#, fuzzy
msgid "Debugging Godot editor"
msgstr "Kreiranje Sadržaja"

#: ../../docs/contributing/development/debugging/macos_debug.rst:7
msgid ""
"Attaching a debugger to the signed macOS process requires the \"com.apple."
"security.get-task-allow\" entitlement, which is not enabled by default, "
"since apps can't be notarized as long as it is enabled. If you want to debug "
"an official build of the editor it should be re-signed with the proper "
"entitlements."
msgstr ""

#: ../../docs/contributing/development/debugging/macos_debug.rst:10
msgid ""
"Create an ``editor.entitlements`` text file with the following contents:"
msgstr ""

#: ../../docs/contributing/development/debugging/macos_debug.rst:37
msgid "Then use the following command to re-sign the editor::"
msgstr ""

#: ../../docs/contributing/development/debugging/macos_debug.rst:42
#, fuzzy
msgid "Debugging exported project"
msgstr "Kreiranje Sadržaja"

#: ../../docs/contributing/development/debugging/macos_debug.rst:44
msgid ""
"To allow debugging, select the ``codesign\\debugging`` (``com.apple.security."
"get-task-allow``) entitlement during the export. When it is selected, "
"notarization is not supported and should be disabled."
msgstr ""

#: ../../docs/contributing/development/debugging/vulkan/index.rst:2
#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:163
msgid "Vulkan"
msgstr ""

#: ../../docs/contributing/development/debugging/vulkan/vulkan_validation_layers.rst:4
msgid "Validation layers"
msgstr ""

#: ../../docs/contributing/development/debugging/vulkan/vulkan_validation_layers.rst:6
msgid ""
"Validation layers enable developers to verify their application's correct "
"use of the Vulkan API. Validation layers can be enabled in both debug and "
"release builds, including in exported projects."
msgstr ""

#: ../../docs/contributing/development/debugging/vulkan/vulkan_validation_layers.rst:12
msgid ""
"Enabling validation layers has a performance impact, so only enable them "
"when you actually need the output to debug the application."
msgstr ""

#: ../../docs/contributing/development/debugging/vulkan/vulkan_validation_layers.rst:18
#: ../../docs/contributing/development/debugging/vulkan/vulkan_validation_layers.rst:44
msgid ""
"Install the Vulkan SDK `<https://vulkan.lunarg.com/sdk/home>`__, which "
"contains validation layers as part of its default installation. No need to "
"enable any optional features in the installer; installing the core Vulkan "
"SDK suffices. You don't need to reboot after installing the SDK, but you may "
"need to close and reopen your current terminal."
msgstr ""

#: ../../docs/contributing/development/debugging/vulkan/vulkan_validation_layers.rst:24
msgid ""
"After installing the Vulkan SDK, run Godot with the ``--gpu-validation`` :"
"ref:`command line argument <doc_command_line_tutorial>`. You can also "
"specify ``--gpu-abort`` which will make Godot quit as soon as a validation "
"error happens. This can prevent your system from freezing if a validation "
"error occurs."
msgstr ""

#: ../../docs/contributing/development/debugging/vulkan/vulkan_validation_layers.rst:34
msgid ""
"Official Godot macOS builds do **not** support validation layers, as these "
"are statically linked against the Vulkan SDK. Dynamic linking must be used "
"instead."
msgstr ""

#: ../../docs/contributing/development/debugging/vulkan/vulkan_validation_layers.rst:38
msgid ""
"In practice, this means that using validation layers on macOS **requires** "
"you to use a Godot build compiled with the ``use_volk=yes`` SCons option. :"
"ref:`doc_compiling_for_macos`. If testing validation layers on an exported "
"project, you must recompile the export template and specify it as a custom "
"export template in your project's macOS export preset."
msgstr ""

#: ../../docs/contributing/development/debugging/vulkan/vulkan_validation_layers.rst:50
msgid ""
"After installing the Vulkan SDK, run a Godot binary that was compiled with "
"``use_volk=yes`` SCons option. Specify the ``--gpu-validation`` :ref:"
"`command line argument <doc_command_line_tutorial>`. You can also specify "
"``--gpu-abort`` which will make Godot quit as soon as a validation error "
"happens. This can prevent your system from freezing if a validation error "
"occurs."
msgstr ""

#: ../../docs/contributing/development/debugging/vulkan/vulkan_validation_layers.rst:60
msgid "Install Vulkan validation layers from your distribution's repositories:"
msgstr ""

#: ../../docs/contributing/development/debugging/vulkan/vulkan_validation_layers.rst:124
msgid ""
"You don't need to reboot after installing the validation layers, but you may "
"need to close and reopen your current terminal."
msgstr ""

#: ../../docs/contributing/development/debugging/vulkan/vulkan_validation_layers.rst:127
msgid ""
"After installing the package, run Godot with the ``--gpu-validation`` :ref:"
"`command line argument <doc_command_line_tutorial>`. You can also specify "
"``--gpu-abort`` which will make Godot quit as soon as a validation error "
"happens. This can prevent your system from freezing if a validation error "
"occurs."
msgstr ""

#: ../../docs/contributing/development/debugging/vulkan/vulkan_validation_layers.rst:137
msgid ""
"After enabling validation layers on Android, a developer can see errors and "
"warning messages in the ``adb logcat`` output."
msgstr ""

#: ../../docs/contributing/development/debugging/vulkan/vulkan_validation_layers.rst:143
msgid "Validation layers are currently **not** supported on iOS."
msgstr ""

#: ../../docs/contributing/development/debugging/vulkan/vulkan_validation_layers.rst:148
msgid ""
"Validation layers are **not** supported on the web platform, as there is no "
"support for Vulkan there."
msgstr ""

#: ../../docs/contributing/development/debugging/vulkan/vulkan_validation_layers.rst:152
msgid "Enabling validation layers"
msgstr ""

#: ../../docs/contributing/development/debugging/vulkan/vulkan_validation_layers.rst:155
msgid "Build validation layers from official sources"
msgstr ""

#: ../../docs/contributing/development/debugging/vulkan/vulkan_validation_layers.rst:157
msgid ""
"To build Android libraries, follow the instructions on `Khronos' repository  "
"<https://github.com/KhronosGroup/Vulkan-ValidationLayers/blob/master/BUILD."
"md#building-on-android>`__. After a successful build, the libraries will be "
"located in ``Vulkan-ValidationLayers/build-android/libs``."
msgstr ""

#: ../../docs/contributing/development/debugging/vulkan/vulkan_validation_layers.rst:162
msgid "Copy libraries"
msgstr ""

#: ../../docs/contributing/development/debugging/vulkan/vulkan_validation_layers.rst:164
msgid ""
"Copy libraries from ``Vulkan-ValidationLayers/build-android/libs`` to "
"``godot/platform/android/java/app/libs/debug/vulkan_validation_layers``."
msgstr ""

#: ../../docs/contributing/development/debugging/vulkan/vulkan_validation_layers.rst:167
msgid ""
"Your Godot source directory tree should look like on the example below::"
msgstr ""

#: ../../docs/contributing/development/debugging/vulkan/vulkan_validation_layers.rst:182
msgid ""
"If the subdirectory ``libs/debug/vulkan_validation_layers`` doesn't exist, "
"create it."
msgstr ""

#: ../../docs/contributing/development/debugging/vulkan/vulkan_validation_layers.rst:185
#, fuzzy
msgid "Compile and run the Android app"
msgstr "Kreiranje Sadržaja"

#: ../../docs/contributing/development/debugging/vulkan/vulkan_validation_layers.rst:187
msgid ""
"Linked validation layers are automatically loaded and enabled in Android "
"debug builds. You can use Godot's :ref:`doc_one-click_deploy` feature to "
"quickly test your project with the validation layers enabled."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/index.rst:2
msgid "Engine core and modules"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/index.rst:4
msgid ""
"The following pages are meant to introduce the global organization of Godot "
"Engine's source code, and give useful tips for extending and fixing the "
"engine on the C++ side."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/index.rst:8
msgid "Getting started with Godot's source code"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/index.rst:10
msgid ""
"This section covers the basics that you will encounter in (almost) every "
"source file."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/index.rst:26
msgid "Extending Godot by modifying its source code"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/index.rst:28
msgid ""
"This section covers what you can do by modifying Godot's C++ source code."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/godot_architecture_diagram.rst:4
msgid "Godot's architecture diagram"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/godot_architecture_diagram.rst:6
msgid ""
"The following diagram describes the architecture used by Godot, from the "
"core components down to the abstracted drivers, via the scene structure and "
"the servers."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/common_engine_methods_and_macros.rst:4
msgid "Common engine methods and macros"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/common_engine_methods_and_macros.rst:6
msgid ""
"Godot's C++ codebase makes use of dozens of custom methods and macros which "
"are used in almost every file. This page is geared towards beginner "
"contributors, but it can also be useful for those writing custom C++ modules."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/common_engine_methods_and_macros.rst:11
msgid "Print text"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/common_engine_methods_and_macros.rst:42
msgid ""
"If you need to add placeholders in your messages, use format strings as "
"described below."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/common_engine_methods_and_macros.rst:46
msgid "Format a string"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/common_engine_methods_and_macros.rst:48
msgid ""
"The ``vformat()`` function returns a formatted :ref:`class_String`. It "
"behaves in a way similar to C's ``sprintf()``:"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/common_engine_methods_and_macros.rst:62
msgid ""
"In most cases, try to use ``vformat()`` instead of string concatenation as "
"it makes for more readable code."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/common_engine_methods_and_macros.rst:66
msgid "Convert an integer or float to a string"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/common_engine_methods_and_macros.rst:68
msgid ""
"This is not needed when printing numbers using ``print_line()``, but you may "
"still need to perform manual conversion for some other use cases."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/common_engine_methods_and_macros.rst:80
msgid "Internationalize a string"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/common_engine_methods_and_macros.rst:82
#, fuzzy
msgid "There are two types of internationalization in Godot's codebase:"
msgstr "Ne postoje ograničenja prilikom korištenja Godot-a"

#: ../../docs/contributing/development/core_and_modules/common_engine_methods_and_macros.rst:84
msgid ""
"``TTR()``: **Editor (\"tools\") translations** will only be processed in the "
"editor. If a user uses the same text in one of their projects, it won't be "
"translated if they provide a translation for it. When contributing to the "
"engine, this is generally the macro you should use for localizable strings."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/common_engine_methods_and_macros.rst:88
msgid ""
"``RTR()``: **Run-time translations** will be automatically localized in "
"projects if they provide a translation for the given string. This kind of "
"translation shouldn't be used in editor-only code."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/common_engine_methods_and_macros.rst:99
msgid ""
"To insert placeholders in localizable strings, wrap the localization macro "
"in a ``vformat()`` call as follows:"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/common_engine_methods_and_macros.rst:109
msgid ""
"When using ``vformat()`` and a translation macro together, always wrap the "
"translation macro in ``vformat()``, not the other way around. Otherwise, the "
"string will never match the translation as it will have the placeholder "
"already replaced when it's passed to TranslationServer."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/common_engine_methods_and_macros.rst:115
msgid "Clamp a value"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/common_engine_methods_and_macros.rst:117
msgid ""
"Godot provides macros for clamping a value with a lower bound (``MAX``), an "
"upper bound (``MIN``) or both (``CLAMP``):"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/common_engine_methods_and_macros.rst:129
msgid ""
"This works with any type that can be compared to other values (like ``int`` "
"and ``float``)."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/common_engine_methods_and_macros.rst:133
msgid "Microbenchmarking"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/common_engine_methods_and_macros.rst:135
msgid ""
"If you want to benchmark a piece of code but don't know how to use a "
"profiler, use this snippet:"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/common_engine_methods_and_macros.rst:147
msgid ""
"This will print the time spent between the ``begin`` declaration and the "
"``end`` declaration."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/common_engine_methods_and_macros.rst:152
msgid ""
"You may have to ``#include \"core/os/os.h\"`` if it's not present already."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/common_engine_methods_and_macros.rst:154
msgid ""
"When opening a pull request, make sure to remove this snippet as well as the "
"include if it wasn't there previously."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/common_engine_methods_and_macros.rst:158
#, fuzzy
msgid "Get project/editor settings"
msgstr "Kreiranje Sadržaja"

#: ../../docs/contributing/development/core_and_modules/common_engine_methods_and_macros.rst:160
#, fuzzy
msgid "There are four macros available for this:"
msgstr "Ne postoje ograničenja prilikom korištenja Godot-a"

#: ../../docs/contributing/development/core_and_modules/common_engine_methods_and_macros.rst:172
msgid ""
"If a default value has been specified elsewhere, don't specify it again to "
"avoid repetition:"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/common_engine_methods_and_macros.rst:182
msgid ""
"It's recommended to use ``GLOBAL_DEF``/``EDITOR_DEF`` only once per setting "
"and use ``GLOBAL_GET``/``EDITOR_GET`` in all other places where it's "
"referenced."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/common_engine_methods_and_macros.rst:186
msgid "Error macros"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/common_engine_methods_and_macros.rst:188
msgid ""
"Godot features many error macros to make error reporting more convenient."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/common_engine_methods_and_macros.rst:192
msgid ""
"Conditions in error macros work in the **opposite** way of GDScript's built-"
"in ``assert()`` function. An error is reached if the condition inside "
"evaluates to ``true``, not ``false``."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/common_engine_methods_and_macros.rst:198
msgid ""
"Only variants with custom messages are documented here, as these should "
"always be used in new contributions. Make sure the custom message provided "
"includes enough information for people to diagnose the issue, even if they "
"don't know C++. In case a method was passed invalid arguments, you can print "
"the invalid value in question to ease debugging."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/common_engine_methods_and_macros.rst:204
msgid ""
"For internal error checking where displaying a human-readable message isn't "
"necessary, remove ``_MSG`` at the end of the macro name and don't supply a "
"message argument."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/common_engine_methods_and_macros.rst:208
msgid ""
"Also, always try to return processable data so the engine can keep running "
"well."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/common_engine_methods_and_macros.rst:252
msgid ""
"See `core/error/error_macros.h <https://github.com/godotengine/godot/blob/"
"master/core/error/error_macros.h>`__ in Godot's codebase for more "
"information about each error macro."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/common_engine_methods_and_macros.rst:255
msgid ""
"Some functions return an error code (materialized by a return type of "
"``Error``). This value can be returned directly from an error macro. See the "
"list of available error codes in `core/error/error_list.h <https://github."
"com/godotengine/godot/blob/master/core/error/error_list.h>`__."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/core_types.rst:4
msgid "Core types"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/core_types.rst:6
msgid ""
"Godot has a rich set of classes and templates that compose its core, and "
"everything is built upon them."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/core_types.rst:9
msgid ""
"This reference will try to list them in order for their better understanding."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/core_types.rst:13
msgid "Definitions"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/core_types.rst:15
msgid ""
"Godot uses the standard C99 datatypes, such as ``uint8_t``, ``uint32_t``, "
"``int64_t``, etc. which are nowadays supported by every compiler. "
"Reinventing the wheel for those is not fun, as it makes code more difficult "
"to read."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/core_types.rst:20
msgid ""
"In general, care is not taken to use the most efficient datatype for a given "
"task unless using large structures or arrays. ``int`` is used through most "
"of the code unless necessary. This is done because nowadays every device has "
"at least a 32 bits bus and can do such operations in one cycle. It makes "
"code more readable too."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/core_types.rst:26
msgid ""
"For files or memory sizes, ``size_t`` is used, which is warranted to be 64 "
"bits."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/core_types.rst:29
msgid ""
"For Unicode characters, CharType instead of wchar_t is used, because many "
"architectures have 4 bytes long wchar_t, where 2 bytes might be desired. "
"However, by default, this has not been forced and CharType maps directly to "
"wchar_t."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/core_types.rst:35
#: ../../docs/contributing/development/core_and_modules/core_types.rst:132
#: ../../docs/contributing/development/core_and_modules/core_types.rst:166
#: ../../docs/contributing/development/core_and_modules/core_types.rst:182
#: ../../docs/contributing/development/core_and_modules/core_types.rst:198
#: ../../docs/contributing/development/core_and_modules/core_types.rst:209
#: ../../docs/contributing/development/core_and_modules/core_types.rst:220
#: ../../docs/contributing/development/core_and_modules/core_types.rst:233
#: ../../docs/contributing/development/core_and_modules/variant_class.rst:38
#: ../../docs/contributing/development/core_and_modules/variant_class.rst:57
#: ../../docs/contributing/development/core_and_modules/object_class.rst:36
#: ../../docs/contributing/development/core_and_modules/object_class.rst:98
#: ../../docs/contributing/development/core_and_modules/object_class.rst:270
#: ../../docs/contributing/development/core_and_modules/object_class.rst:286
#: ../../docs/contributing/development/core_and_modules/object_class.rst:307
#: ../../docs/contributing/development/core_and_modules/object_class.rst:326
#: ../../docs/contributing/development/core_and_modules/custom_godot_servers.rst:471
#: ../../docs/contributing/development/core_and_modules/custom_audiostreams.rst:23
#: ../../docs/contributing/development/core_and_modules/custom_audiostreams.rst:117
#: ../../docs/contributing/development/core_and_modules/custom_audiostreams.rst:348
msgid "References:"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/core_types.rst:37
#, fuzzy
msgid ""
"`core/typedefs.h <https://github.com/godotengine/godot/blob/master/core/"
"typedefs.h>`__"
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati raznorazne `Godot demo projects "
"<https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/contributing/development/core_and_modules/core_types.rst:40
msgid "Memory model"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/core_types.rst:42
msgid ""
"PC is a wonderful architecture. Computers often have gigabytes of RAM, "
"terabytes of storage and gigahertz of CPU, and when an application needs "
"more resources the OS will swap out the inactive ones. Other architectures "
"(like mobile or consoles) are in general more limited."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/core_types.rst:47
msgid ""
"The most common memory model is the heap, where an application will request "
"a region of memory, and the underlying OS will try to fit it somewhere and "
"return it. This often works best and is flexible, but over time and with "
"abuse, this can lead to segmentation."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/core_types.rst:52
msgid ""
"Segmentation slowly creates holes that are too small for most common "
"allocations, so that memory is wasted. There is a lot of literature about "
"heap and segmentation, so this topic will not be developed further here. "
"Modern operating systems use paged memory, which helps mitigate the problem "
"of segmentation but doesn't solve it."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/core_types.rst:58
msgid ""
"However, in many studies and tests, it is shown that given enough memory, if "
"the maximum allocation size is below a given threshold in proportion to the "
"maximum heap size and proportion of memory intended to be unused, "
"segmentation will not be a problem over time as it will remain constant. In "
"other words, leave 10-20% of your memory free and perform all small "
"allocations and you are fine."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/core_types.rst:65
msgid ""
"Godot ensures that all objects that can be allocated dynamically are small "
"(less than a few kb at most). But what happens if an allocation is too large "
"(like an image or mesh geometry or large array)? In this case Godot has the "
"option to use a dynamic memory pool. This memory needs to be locked to be "
"accessed, and if an allocation runs out of memory, the pool will be "
"rearranged and compacted on demand. Depending on the need of the game, the "
"programmer can configure the dynamic memory pool size."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/core_types.rst:74
msgid "Allocating memory"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/core_types.rst:76
msgid ""
"Godot has many tools for tracking memory usage in a game, especially during "
"debug. Because of this, the regular C and C++ library calls should not be "
"used. Instead, a few other ones are provided."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/core_types.rst:80
msgid "For C-style allocation, Godot provides a few macros:"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/core_types.rst:88
msgid ""
"These are equivalent to the usual malloc, realloc, free of the standard C "
"library."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/core_types.rst:91
msgid "For C++-style allocation, special macros are provided:"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/core_types.rst:101
msgid "which are equivalent to new, delete, new[] and delete[]."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/core_types.rst:103
msgid ""
"memnew/memdelete also use a little C++ magic and notify Objects right after "
"they are created, and right before they are deleted."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/core_types.rst:106
msgid ""
"For dynamic memory, the PoolVector<> template is provided. PoolVector is a "
"standard vector class, and is very similar to vector in the C++ standard "
"library. To create a PoolVector buffer, use this:"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/core_types.rst:114
msgid ""
"PoolVector can be accessed using the [] operator and a few helpers exist for "
"this:"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/core_types.rst:126
msgid ""
"These operations allow fast read/write from PoolVectors and keep it locked "
"until they go out of scope. However, PoolVectors should be used for small, "
"dynamic memory operations, as read() and write() are too slow for a large "
"amount of accesses."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/core_types.rst:134
#, fuzzy
msgid ""
"`core/os/memory.h <https://github.com/godotengine/godot/blob/master/core/os/"
"memory.h>`__"
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati raznorazne `Godot demo projects "
"<https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/contributing/development/core_and_modules/core_types.rst:135
#, fuzzy
msgid ""
"`core/pool_vector.h <https://github.com/godotengine/godot/blob/master/core/"
"pool_vector.cpp>`__"
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati raznorazne `Godot demo projects "
"<https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/contributing/development/core_and_modules/core_types.rst:138
msgid "Containers"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/core_types.rst:140
msgid "Godot provides also a set of common containers:"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/core_types.rst:143
msgid "List"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/core_types.rst:144
msgid "Set"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/core_types.rst:145
msgid "Map"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/core_types.rst:147
msgid ""
"They aim to be as minimal as possible, as templates in C++ are often inlined "
"and make the binary size much fatter, both in debug symbols and code. List, "
"Set and Map can be iterated using pointers, like this:"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/core_types.rst:158
msgid "The Vector<> class also has a few nice features:"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/core_types.rst:160
msgid ""
"It does copy on write, so making copies of it is cheap as long as they are "
"not modified."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/core_types.rst:162
msgid ""
"It supports multi-threading, by using atomic operations on the reference "
"counter."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/core_types.rst:168
#, fuzzy
msgid ""
"`core/templates/vector.h <https://github.com/godotengine/godot/blob/master/"
"core/templates/vector.h>`__"
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati raznorazne `Godot demo projects "
"<https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/contributing/development/core_and_modules/core_types.rst:169
#, fuzzy
msgid ""
"`core/templates/list.h <https://github.com/godotengine/godot/blob/master/"
"core/templates/list.h>`__"
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati raznorazne `Godot demo projects "
"<https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/contributing/development/core_and_modules/core_types.rst:170
#, fuzzy
msgid ""
"`core/templates/set.h <https://github.com/godotengine/godot/blob/master/core/"
"templates/hash_set.h>`__"
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati raznorazne `Godot demo projects "
"<https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/contributing/development/core_and_modules/core_types.rst:171
#, fuzzy
msgid ""
"`core/templates/map.h <https://github.com/godotengine/godot/blob/master/core/"
"templates/hash_map.h>`__"
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati raznorazne `Godot demo projects "
"<https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/contributing/development/core_and_modules/core_types.rst:176
msgid ""
"Godot also provides a String class. This class has a huge amount of "
"features, full Unicode support in all the functions (like case operations) "
"and utf8 parsing/extracting, as well as helpers for conversion and "
"visualization."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/core_types.rst:184
#, fuzzy
msgid ""
"`core/string/ustring.h <https://github.com/godotengine/godot/blob/master/"
"core/string/ustring.h>`__"
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati raznorazne `Godot demo projects "
"<https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/contributing/development/core_and_modules/core_types.rst:187
msgid "StringName"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/core_types.rst:189
msgid ""
"StringNames are like a String, but they are unique. Creating a StringName "
"from a string results in a unique internal pointer for all equal strings. "
"StringNames are useful for using strings as identifier, as comparing them is "
"basically comparing a pointer."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/core_types.rst:194
msgid ""
"Creation of a StringName (especially a new one) is slow, but comparison is "
"fast."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/core_types.rst:200
#, fuzzy
msgid ""
"`core/string/string_name.h <https://github.com/godotengine/godot/blob/master/"
"core/string/string_name.h>`__"
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati raznorazne `Godot demo projects "
"<https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/contributing/development/core_and_modules/core_types.rst:203
msgid "Math types"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/core_types.rst:205
msgid ""
"There are several linear math types available in the core/math directory."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/core_types.rst:211
#, fuzzy
msgid ""
"`core/math <https://github.com/godotengine/godot/tree/master/core/math>`__"
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati raznorazne `Godot demo projects "
"<https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/contributing/development/core_and_modules/core_types.rst:216
msgid ""
"This is a special datatype used for storing paths in a scene tree and "
"referencing them fast."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/core_types.rst:222
#, fuzzy
msgid ""
"`core/string/node_path.h <https://github.com/godotengine/godot/blob/master/"
"core/string/node_path.h>`__"
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati raznorazne `Godot demo projects "
"<https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/contributing/development/core_and_modules/core_types.rst:227
msgid ""
"RIDs are resource IDs. Servers use these to reference data stored in them. "
"RIDs are opaque, meaning that the data they reference can't be accessed "
"directly. RIDs are unique, even for different types of referenced data."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/core_types.rst:235
#: ../../docs/contributing/development/core_and_modules/custom_godot_servers.rst:315
#, fuzzy
msgid ""
"`core/templates/rid.h <https://github.com/godotengine/godot/blob/master/core/"
"templates/rid.h>`__"
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati raznorazne `Godot demo projects "
"<https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/contributing/development/core_and_modules/variant_class.rst:4
msgid "Variant class"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/variant_class.rst:9
msgid ""
"Variant is the most important datatype of Godot, it's the most important "
"class in the engine. A Variant takes up only 20 bytes and can store almost "
"any engine datatype inside of it. Variants are rarely used to hold "
"information for long periods of time, instead they are used mainly for "
"communication, editing, serialization and generally moving data around."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/variant_class.rst:16
msgid "A Variant can:"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/variant_class.rst:18
msgid "Store almost any datatype"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/variant_class.rst:19
msgid ""
"Perform operations between many variants (GDScript uses Variant as its "
"atomic/native datatype)."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/variant_class.rst:21
msgid "Be hashed, so it can be compared quickly to other variants"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/variant_class.rst:22
msgid "Be used to convert safely between datatypes"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/variant_class.rst:23
msgid ""
"Be used to abstract calling methods and their arguments (Godot exports all "
"its functions through variants)"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/variant_class.rst:25
msgid "Be used to defer calls or move data between threads."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/variant_class.rst:26
msgid "Be serialized as binary and stored to disk, or transferred via network."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/variant_class.rst:28
msgid ""
"Be serialized to text and use it for printing values and editable settings."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/variant_class.rst:30
msgid "Work as an exported property, so the editor can edit it universally."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/variant_class.rst:31
msgid "Be used for dictionaries, arrays, parsers, etc."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/variant_class.rst:33
msgid ""
"Basically, thanks to the Variant class, writing Godot itself was a much, "
"much easier task, as it allows for highly dynamic constructs not common of C+"
"+ with little effort. Become a friend of Variant today."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/variant_class.rst:40
#, fuzzy
msgid ""
"`core/variant/variant.h <https://github.com/godotengine/godot/blob/master/"
"core/variant/variant.h>`__"
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati raznorazne `Godot demo projects "
"<https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/contributing/development/core_and_modules/variant_class.rst:43
msgid "Containers: Dictionary and Array"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/variant_class.rst:45
msgid ""
"Both are implemented using variants. A Dictionary can match any datatype "
"used as key to any other datatype. An Array just holds an array of Variants. "
"Of course, a Variant can also hold a Dictionary and an Array inside, making "
"it even more flexible."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/variant_class.rst:50
msgid ""
"Modifications to a container will modify all references to it. A Mutex "
"should be created to lock it if multi threaded access is desired."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/variant_class.rst:54
msgid ""
"Copy-on-write (COW) mode support for containers was dropped with Godot 3.0."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/variant_class.rst:59
#, fuzzy
msgid ""
"`core/variant/dictionary.h <https://github.com/godotengine/godot/blob/master/"
"core/variant/dictionary.h>`__"
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati raznorazne `Godot demo projects "
"<https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/contributing/development/core_and_modules/variant_class.rst:60
#, fuzzy
msgid ""
"`core/variant/array.h <https://github.com/godotengine/godot/blob/master/core/"
"variant/array.h>`__"
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati raznorazne `Godot demo projects "
"<https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/contributing/development/core_and_modules/object_class.rst:4
msgid "Object class"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/object_class.rst:8
msgid ""
"This page describes the C++ implementation of objects in Godot. Looking for "
"the Object class reference? :ref:`Have a look here. <class_Object>`"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/object_class.rst:12
msgid "General definition"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/object_class.rst:14
msgid ""
":ref:`Object <class_object>` is the base class for almost everything. Most "
"classes in Godot inherit directly or indirectly from it. Objects provide "
"reflection and editable properties, and declaring them is a matter of using "
"a single macro like this:"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/object_class.rst:26
msgid "This adds a lot of functionality to Objects. For example:"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/object_class.rst:38
#, fuzzy
msgid ""
"`core/object/object.h <https://github.com/godotengine/godot/blob/master/core/"
"object/object.h>`__"
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati raznorazne `Godot demo projects "
"<https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/contributing/development/core_and_modules/object_class.rst:41
msgid "Registering an Object"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/object_class.rst:43
msgid ""
"ClassDB is a static class that holds the entire list of registered classes "
"that inherit from Object, as well as dynamic bindings to all their methods "
"properties and integer constants."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/object_class.rst:47
msgid "Classes are registered by calling:"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/object_class.rst:53
msgid ""
"Registering it will allow the class to be instanced by scripts, code, or "
"creating them again when deserializing."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/object_class.rst:56
msgid "Registering as virtual is the same but it can't be instanced."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/object_class.rst:62
msgid ""
"Object-derived classes can override the static function ``static void "
"_bind_methods()``. When one class is registered, this static function is "
"called to register all the object methods, properties, constants, etc. It's "
"only called once. If an Object derived class is instanced but has not been "
"registered, it will be registered as virtual automatically."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/object_class.rst:69
msgid ""
"Inside ``_bind_methods``, there are a couple of things that can be done. "
"Registering functions is one:"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/object_class.rst:76
msgid "Default values for arguments can be passed as parameters at the end:"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/object_class.rst:82
msgid ""
"Default values must be provided in the same order as they are declared, "
"skipping required arguments and then providing default values for the "
"optional ones. This matches the syntax for declaring methods in C++."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/object_class.rst:86
msgid ""
"``D_METHOD`` is a macro that converts \"methodname\" to a StringName for "
"more efficiency. Argument names are used for introspection, but when "
"compiling on release, the macro ignores them, so the strings are unused and "
"optimized away."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/object_class.rst:91
msgid "Check ``_bind_methods`` of Control or Object for more examples."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/object_class.rst:93
msgid ""
"If just adding modules and functionality that is not expected to be "
"documented as thoroughly, the ``D_METHOD()`` macro can safely be ignored and "
"a string passing the name can be passed for brevity."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/object_class.rst:100
#, fuzzy
msgid ""
"`core/object/class_db.h <https://github.com/godotengine/godot/blob/master/"
"core/object/class_db.h>`__"
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati raznorazne `Godot demo projects "
"<https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/contributing/development/core_and_modules/object_class.rst:105
msgid "Classes often have enums such as:"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/object_class.rst:114
msgid ""
"For these to work when binding to methods, the enum must be declared "
"convertible to int. A macro is provided to help with this:"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/object_class.rst:121
msgid "The constants can also be bound inside ``_bind_methods``, by using:"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/object_class.rst:129
msgid "Properties (set/get)"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/object_class.rst:131
msgid "Objects export properties, properties are useful for the following:"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/object_class.rst:133
msgid "Serializing and deserializing the object."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/object_class.rst:134
msgid "Creating a list of editable values for the Object derived class."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/object_class.rst:136
msgid ""
"Properties are usually defined by the PropertyInfo() class and constructed "
"as:"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/object_class.rst:149
msgid ""
"This is an integer property named \"amount\". The hint is a range, and the "
"range goes from 0 to 49 in steps of 1 (integers). It is only usable for the "
"editor (editing the value visually) but won't be serialized."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/object_class.rst:153
msgid "Another example:"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/object_class.rst:159
msgid ""
"This is a string property, can take any string but the editor will only "
"allow the defined hint ones. Since no usage flags were specified, the "
"default ones are PROPERTY_USAGE_STORAGE and PROPERTY_USAGE_EDITOR."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/object_class.rst:163
msgid ""
"There are plenty of hints and usage flags available in object.h, give them a "
"check."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/object_class.rst:166
msgid ""
"Properties can also work like C# properties and be accessed from script "
"using indexing, but this usage is generally discouraged, as using functions "
"is preferred for legibility. Many properties are also bound with categories, "
"such as \"animation/frame\" which also make indexing impossible unless using "
"operator []."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/object_class.rst:172
msgid ""
"From ``_bind_methods()``, properties can be created and bound as long as set/"
"get functions exist. Example:"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/object_class.rst:179
msgid "This creates the property using the setter and the getter."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/object_class.rst:184
msgid "Binding properties using ``_set``/``_get``/``_get_property_list``"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/object_class.rst:186
msgid ""
"An additional method of creating properties exists when more flexibility is "
"desired (i.e. adding or removing properties on context)."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/object_class.rst:189
msgid ""
"The following functions can be overridden in an Object derived class, they "
"are NOT virtual, DO NOT make them virtual, they are called for every "
"override and the previous ones are not invalidated (multilevel call)."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/object_class.rst:201
msgid ""
"This is also a little less efficient since ``p_property`` must be compared "
"against the desired names in serial order."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/object_class.rst:205
msgid "Dynamic casting"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/object_class.rst:207
msgid ""
"Godot provides dynamic casting between Object-derived classes, for example:"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/object_class.rst:217
msgid ""
"If cast fails, NULL is returned. This system uses RTTI, but it also works "
"fine (although a bit slower) when RTTI is disabled. This is useful on "
"platforms where a small binary size is ideal, such as HTML5 or consoles "
"(with low memory footprint)."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/object_class.rst:225
msgid ""
"Objects can have a set of signals defined (similar to Delegates in other "
"languages). This example shows how to connect to them:"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/object_class.rst:234
msgid ""
"The method ``_node_entered_tree`` must be registered to the class using "
"``ClassDB::bind_method`` (explained before)."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/object_class.rst:237
msgid ""
"Adding signals to a class is done in ``_bind_methods``, using the "
"``ADD_SIGNAL`` macro, for example:"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/object_class.rst:247
msgid ""
"All objects in Godot have a :ref:`_notification "
"<class_Object_private_method__notification>` method that allows it to "
"respond to engine level callbacks that may relate to it. More information "
"can be found on the :ref:`doc_godot_notifications` page."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/object_class.rst:252
#: ../../docs/contributing/development/core_and_modules/custom_godot_servers.rst:19
#: ../../docs/contributing/development/core_and_modules/custom_godot_servers.rst:312
#: ../../docs/contributing/development/core_and_modules/custom_resource_format_loaders.rst:18
#: ../../docs/contributing/development/core_and_modules/custom_resource_format_loaders.rst:39
#: ../../docs/contributing/development/core_and_modules/custom_resource_format_loaders.rst:303
#: ../../docs/contributing/development/core_and_modules/custom_resource_format_loaders.rst:356
#: ../../docs/contributing/development/editor/creating_icons.rst:102
msgid "References"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/object_class.rst:254
msgid ""
":ref:`RefCounted <class_RefCounted>` inherits from Object and holds a "
"reference count. It is the base for reference counted object types. "
"Declaring them must be done using Ref<> template. For example:"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/object_class.rst:266
msgid ""
"``myref`` is reference counted. It will be freed when no more Ref<> "
"templates point to it."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/object_class.rst:272
#, fuzzy
msgid ""
"`core/object/reference.h <https://github.com/godotengine/godot/blob/master/"
"core/object/ref_counted.h>`__"
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati raznorazne `Godot demo projects "
"<https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/contributing/development/core_and_modules/object_class.rst:277
msgid ""
":ref:`Resource <class_resource>` inherits from Reference, so all resources "
"are reference counted. Resources can optionally contain a path, which "
"reference a file on disk. This can be set with ``resource.set_path(path)``, "
"though this is normally done by the resource loader. No two different "
"resources can have the same path; attempting to do so will result in an "
"error."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/object_class.rst:283
msgid "Resources without a path are fine too."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/object_class.rst:288
#, fuzzy
msgid ""
"`core/io/resource.h <https://github.com/godotengine/godot/blob/master/core/"
"io/resource.h>`__"
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati raznorazne `Godot demo projects "
"<https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/contributing/development/core_and_modules/object_class.rst:291
msgid "Resource loading"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/object_class.rst:293
msgid "Resources can be loaded with the ResourceLoader API, like this:"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/object_class.rst:299
msgid ""
"If a reference to that resource has been loaded previously and is in memory, "
"the resource loader will return that reference. This means that there can be "
"only one resource loaded from a file referenced on disk at the same time."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/object_class.rst:304
msgid "resourceinteractiveloader (TODO)"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/object_class.rst:309
#, fuzzy
msgid ""
"`core/io/resource_loader.h <https://github.com/godotengine/godot/blob/master/"
"core/io/resource_loader.h>`__"
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati raznorazne `Godot demo projects "
"<https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/contributing/development/core_and_modules/object_class.rst:312
msgid "Resource saving"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/object_class.rst:314
msgid "Saving a resource can be done with the resource saver API:"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/object_class.rst:320
msgid ""
"The instance will be saved, and sub resources that have a path to a file "
"will be saved as a reference to that resource. Sub resources without a path "
"will be bundled with the saved resource and assigned sub-IDs, like ``res://"
"someresource.res::1``. This also helps to cache them when loaded."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/object_class.rst:328
#, fuzzy
msgid ""
"`core/io/resource_saver.h <https://github.com/godotengine/godot/blob/master/"
"core/io/resource_saver.h>`__"
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati raznorazne `Godot demo projects "
"<https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/contributing/development/core_and_modules/inheritance_class_tree.rst:2
msgid "Inheritance class tree"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/inheritance_class_tree.rst:5
msgid "Object"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/inheritance_class_tree.rst:15
msgid "Control"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/inheritance_class_tree.rst:29
msgid "Source files: :download:`class_tree.zip <files/class_tree.zip>`."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:4
msgid "Internal rendering architecture"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:6
msgid ""
"This page is a high-level overview of Godot 4's internal renderer design. It "
"does not apply to previous Godot versions."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:9
msgid ""
"The goal of this page is to document design decisions taken to best suit :"
"ref:`Godot's design philosophy "
"<doc_best_practices_for_engine_contributors>`, while providing a starting "
"point for new rendering contributors."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:13
msgid ""
"If you have questions about rendering internals not answered here, feel free "
"to ask in the ``#rendering`` channel of the `Godot Contributors Chat "
"<https://chat.godotengine.org/channel/rendering>`__."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:19
msgid ""
"If you have difficulty understanding concepts on this page, it is "
"recommended to go through an OpenGL tutorial such as `LearnOpenGL <https://"
"learnopengl.com/>`__."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:23
msgid ""
"Modern low-level APIs (Vulkan/Direct3D 12) require intermediate knowledge of "
"higher-level APIs (OpenGL/Direct3D 11) to be used effectively. Thankfully, "
"contributors rarely need to work directly with low-level APIs. Godot's "
"renderers are built entirely on OpenGL and RenderingDevice, which is our "
"abstraction over Vulkan/Direct3D 12."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:32
#, fuzzy
msgid "Rendering methods"
msgstr "Kreiranje Sadržaja"

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:35
msgid "Forward+"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:37
msgid ""
"This is a forward renderer that uses a *clustered* approach to lighting."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:39
msgid ""
"Clustered lighting uses a compute shader to group lights into a 3D frustum "
"aligned grid. Then, at render time, pixels can lookup what lights affect the "
"grid cell they are in and only run light calculations for lights that might "
"affect that pixel."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:44
msgid ""
"This approach can greatly speed up rendering performance on desktop "
"hardware, but is substantially less efficient on mobile."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:48
msgid "Forward Mobile"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:50
msgid ""
"This is a forward renderer that uses a traditional single-pass approach to "
"lighting."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:52
msgid ""
"Intended for mobile platforms, but can also run on desktop platforms. This "
"rendering method is optimized to perform well on mobile GPUs. Mobile GPUs "
"have a very different architecture compared to desktop GPUs due to their "
"unique constraints around battery usage, heat, and overall bandwidth "
"limitations of reading and writing data. Compute shaders also have very "
"limited support or aren't supported at all. As a result, the mobile renderer "
"purely uses raster-based shaders (fragment/vertex)."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:60
msgid ""
"Unlike desktop GPUs, mobile GPUs perform *tile-based rendering*. Instead of "
"rendering the whole image as a single unit, the image is divided in smaller "
"tiles that fit within the faster internal memory of the mobile GPU. Each "
"tile is rendered and then written out to the destination texture. This all "
"happens automatically on the graphics driver."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:66
msgid ""
"The problem is that this introduces bottlenecks in our traditional approach. "
"For desktop rendering, we render all opaque geometry, then handle the "
"background, then transparent geometry, then post-processing. Each pass will "
"need to read the current result into tile memory, perform its operations and "
"then write it out again. We then wait for all tiles to be completed before "
"moving on to the next pass."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:73
msgid ""
"The first important change in the mobile renderer is that the mobile "
"renderer does not use the RGBA16F texture formats that the desktop renderer "
"does. Instead, it is using a R10G10B10A2 UNORM texture format. This halves "
"the bandwidth required and has further improvements as mobile hardware often "
"further optimizes for 32-bit formats. The tradeoff is that the mobile "
"renderer has limited HDR capabilities due to the reduced precision and "
"maximum values in the color data."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:80
msgid ""
"The second important change is the use of sub-passes whenever possible. Sub-"
"passes allows us to perform the rendering steps end-to-end per tile saving "
"on the overhead introduced by reading from and writing to the tiles between "
"each rendering pass. The ability to use sub-passes is limited by the "
"inability to read neighboring pixels, as we're constrained to working within "
"a single tile."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:86
msgid ""
"This limitation of subpasses results in not being able to implement features "
"such as glow and depth of field efficiently. Similarly, if there is a "
"requirement to read from the screen texture or depth texture, we must fully "
"write out the rendering result limiting our ability to use sub-passes. When "
"such features are enabled, a mix of sub-passes and normal passes are used, "
"and these features result in a notable performance penalty."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:93
msgid ""
"On desktop platforms, the use of sub-passes won't have any impact on "
"performance. However, this rendering method can still perform better than "
"Clustered Forward in simple scenes thanks to its lower complexity and lower "
"bandwidth usage. This is especially noticeable on low-end GPUs, integrated "
"graphics or in VR applications."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:99
msgid ""
"Given its low-end focus, this rendering method does not provide high-end "
"rendering features such as SDFGI and :ref:`doc_volumetric_fog`. Several post-"
"processing effects are also not available."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:106
msgid "Compatibility"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:110
msgid ""
"This is the only rendering method available when using the OpenGL driver. "
"This rendering method is not available when using Vulkan or Direct3D 12."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:113
msgid ""
"This is a traditional (non-clustered) forward renderer. It's intended for "
"old GPUs that don't have Vulkan support, but still works very efficiently on "
"newer hardware. Specifically, it is optimized for older and lower-end mobile "
"devices However, many optimizations carry over making it a good choice for "
"older and lower-end desktop as well."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:119
msgid ""
"Like the Mobile renderer, the Compatibility renderer uses an R10G10B10A2 "
"UNORM texture for 3D rendering. Unlike the mobile renderer, colors are "
"tonemapped and stored in sRGB format so there is no HDR support. This avoids "
"the need for a tonemapping pass and allows us to use the lower bit texture "
"without substantial banding."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:125
msgid ""
"The Compatibility renderer uses a traditional forward single-pass approach "
"to drawing objects with lights, but it uses a multi-pass approach to draw "
"lights with shadows. Specifically, in the first pass, it can draw multiple "
"lights without shadows and up to one DirectionalLight3D with shadows. In "
"each subsequent pass, it can draw up to one OmniLight3D, one SpotLight3D and "
"one DirectionalLight3D with shadows. Lights with shadows will affect the "
"scene differently than lights without shadows, as the lighting is blended in "
"sRGB space instead of linear space. This difference in lighting will impact "
"how the scene looks and needs to be kept in mind when designing scenes for "
"the Compatibility renderer."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:136
msgid ""
"Given its low-end focus, this rendering method does not provide high-end "
"rendering features (even less so compared to Forward Mobile). Most post-"
"processing effects are not available."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:141
msgid "Why not deferred rendering?"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:143
msgid ""
"Forward rendering generally provides a better tradeoff for performance "
"versus flexibility, especially when a clustered approach to lighting is "
"used. While deferred rendering can be faster in some cases, it's also less "
"flexible and requires using hacks to be able to use MSAA. Since games with a "
"less realistic art style can benefit a lot from MSAA, we chose to go with "
"forward rendering for Godot 4 (like Godot 3)."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:150
msgid ""
"That said, parts of the forward renderer *are* performed with a deferred "
"approach to allow for some optimizations when possible. This applies to "
"VoxelGI and SDFGI in particular."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:154
msgid ""
"A clustered deferred renderer may be developed in the future. This renderer "
"could be used in situations where performance is favored over flexibility."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:158
#, fuzzy
msgid "Rendering drivers"
msgstr "Kreiranje Sadržaja"

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:160
msgid "Godot 4 supports the following graphics APIs:"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:165
msgid ""
"This is the main driver in Godot 4, with most of the development focus going "
"towards this driver."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:168
msgid ""
"Vulkan 1.0 is required as a baseline, with optional Vulkan 1.1 and 1.2 "
"features used when available. `volk <https://github.com/zeux/volk>`__ is "
"used as a Vulkan loader, and `Vulkan Memory Allocator <https://github.com/"
"GPUOpen-LibrariesAndSDKs/VulkanMemoryAllocator>`__ is used for memory "
"management."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:174
msgid ""
"Both the Forward+ and Mobile :ref:"
"`doc_internal_rendering_architecture_methods` are supported when using the "
"Vulkan driver."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:178
msgid "**Vulkan context creation:**"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:180
#, fuzzy
msgid ""
"`drivers/vulkan/vulkan_context.cpp <https://github.com/godotengine/godot/"
"blob/4.2/drivers/vulkan/vulkan_context.cpp>`__"
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati raznorazne `Godot demo projects "
"<https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:182
msgid "**Direct3D 12 context creation:**"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:184
#, fuzzy
msgid ""
"`drivers/d3d12/d3d12_context.cpp <https://github.com/godotengine/godot/blob/"
"master/drivers/d3d12/d3d12_context.cpp>`__"
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati raznorazne `Godot demo projects "
"<https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:187
#, fuzzy
msgid "Direct3D 12"
msgstr "Uvod"

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:189
msgid ""
"Like Vulkan, the Direct3D 12 driver targets modern platforms only. It is "
"designed to target both Windows and Xbox (whereas Vulkan can't be used "
"directly on Xbox)."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:192
msgid ""
"Both the Forward+ and Mobile :ref:"
"`doc_internal_rendering_architecture_methods` can be used with Direct3D 12."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:195
msgid ""
":ref:`doc_internal_rendering_architecture_core_shaders` are shared with the "
"Vulkan renderer. Shaders are transpiled from GLSL to HLSL using Mesa NIR "
"(`more information <https://godotengine.org/article/d3d12-adventures-in-"
"shaderland/>`__). This means you don't need to know HLSL to work on the "
"Direct3D 12 renderer, although knowing the language's basics is recommended "
"to ease debugging."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:201
msgid ""
"**This driver is still experimental and only available in Godot 4.3 and "
"later.** While Direct3D 12 allows supporting Direct3D-exclusive features on "
"Windows 11 such as windowed optimizations and Auto HDR, Vulkan is still "
"recommended for most projects. See the `pull request that introduced "
"Direct3D 12 support <https://github.com/godotengine/godot/pull/70315>`__ for "
"more information."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:208
msgid "Metal"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:210
msgid ""
"Godot supports Metal rendering via `MoltenVK <https://github.com/"
"KhronosGroup/MoltenVK>`__, as macOS and iOS do not support Vulkan natively. "
"This is done automatically when specifying the Vulkan driver in the Project "
"Settings."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:214
msgid ""
"MoltenVK makes driver maintenance easy at the cost of some performance "
"overhead. Also, MoltenVK has several limitations that a native Metal driver "
"implementation wouldn't have. Both the clustered and mobile :ref:"
"`doc_internal_rendering_architecture_methods` can be used with a Metal "
"backend via MoltenVK."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:220
msgid ""
"A native Metal driver is planned in the future for better performance and "
"compatibility."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:224
msgid "OpenGL"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:226
msgid ""
"This driver uses OpenGL ES 3.0 and targets legacy and low-end devices that "
"don't support Vulkan. OpenGL 3.3 Core Profile is used on desktop platforms "
"to run this driver, as most graphics drivers on desktop don't support OpenGL "
"ES. WebGL 2.0 is used for web exports."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:231
msgid ""
"Only the :ref:`doc_internal_rendering_architecture_compatibility` rendering "
"method can be used with the OpenGL driver."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:234
msgid ""
":ref:`doc_internal_rendering_architecture_core_shaders` are entirely "
"different from the Vulkan renderer."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:237
msgid ""
"**As of May 2023, this driver is still in development.** Many features are "
"still not implemented, especially in 3D."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:241
msgid "Summary of rendering drivers/methods"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:243
msgid ""
"The following rendering API + rendering method combinations are currently "
"possible:"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:245
msgid "Vulkan + Forward+"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:246
msgid "Vulkan + Forward Mobile"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:247
msgid "Direct3D 12 + Forward+"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:248
msgid "Direct3D 12 + Forward Mobile"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:249
msgid "Metal + Forward+ (via MoltenVK)"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:250
msgid "Metal + Forward Mobile (via MoltenVK)"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:251
msgid "OpenGL + Compatibility"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:253
msgid ""
"Each combination has its own limitations and performance characteristics. "
"Make sure to test your changes on all rendering methods if possible before "
"opening a pull request."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:258
msgid "RenderingDevice abstraction"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:262
msgid "The OpenGL driver does not use the RenderingDevice abstraction."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:264
msgid ""
"To make the complexity of modern low-level graphics APIs more manageable, "
"Godot uses its own abstraction called RenderingDevice."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:267
msgid ""
"This means that when writing code for modern rendering methods, you don't "
"actually use the Vulkan or Direct3D 12 APIs directly. While this is still "
"lower-level than an API like OpenGL, this makes working on the renderer "
"easier, as RenderingDevice will abstract many API-specific quirks for you. "
"The RenderingDevice presents a similar level of abstraction as Metal or "
"WebGPU."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:273
msgid "**Vulkan RenderingDevice implementation:**"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:275
#, fuzzy
msgid ""
"`drivers/vulkan/rendering_device_vulkan.cpp <https://github.com/godotengine/"
"godot/blob/4.2/drivers/vulkan/rendering_device_vulkan.cpp>`__"
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati raznorazne `Godot demo projects "
"<https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:277
msgid "**Direct3D 12 RenderingDevice implementation:**"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:279
#, fuzzy
msgid ""
"`drivers/d3d12/rendering_device_driver_d3d12.cpp <https://github.com/"
"godotengine/godot/blob/master/drivers/d3d12/rendering_device_driver_d3d12."
"cpp>`__"
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati raznorazne `Godot demo projects "
"<https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:282
msgid "Core rendering classes architecture"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:284
msgid ""
"This diagram represents the structure of rendering classes in Godot, "
"including the RenderingDevice abstraction:"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:288
msgid ""
"`View at full size <https://raw.githubusercontent.com/godotengine/godot-docs/"
"master/contributing/development/core_and_modules/img/"
"rendering_architecture_diagram.webp>`__"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:293
#, fuzzy
msgid "Core shaders"
msgstr "Kreiranje Sadržaja"

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:295
msgid ""
"While shaders in Godot projects are written using a :ref:`custom language "
"inspired by GLSL <doc_shading_language>`, core shaders are written directly "
"in GLSL."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:299
msgid ""
"These core shaders are embedded in the editor and export template binaries "
"at compile-time. To see any changes you've made to those GLSL shaders, you "
"need to recompile the editor or export template binary."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:303
msgid ""
"Some material features such as height mapping, refraction and proximity fade "
"are not part of core shaders, and are performed in the default "
"BaseMaterial3D using the Godot shader language instead (not GLSL). This is "
"done by procedurally generating the required shader code depending on the "
"features enabled in the material."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:309
msgid ""
"By convention, shader files with ``_inc`` in their name are included in "
"other GLSL files for better code reuse. Standard GLSL preprocessing is used "
"to achieve this."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:315
msgid ""
"Core material shaders will be used by every material in the scene – both "
"with the default BaseMaterial3D and custom shaders. As a result, these "
"shaders must be kept as simple as possible to avoid performance issues and "
"ensure shader compilation doesn't become too slow."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:320
msgid ""
"If you use ``if`` branching in a shader, performance may decrease as :abbr:"
"`VGPR (Vector General-Purpose Register)` usage will increase in the shader. "
"This happens even if all pixels evaluate to ``true`` or ``false`` in a given "
"frame."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:325
msgid ""
"If you use ``#if`` preprocessor branching, the number of required shader "
"versions will increase in the scene. In a worst-case scenario, adding a "
"single boolean ``#define`` can *double* the number of shader versions that "
"may need to be compiled in a given scene. In some cases, Vulkan "
"specialization constants can be used as a faster (but more limited) "
"alternative."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:332
msgid ""
"This means there is a high barrier to adding new built-in material features "
"in Godot, both in the core shaders and BaseMaterial3D. While BaseMaterial3D "
"can make use of dynamic code generation to only include the shader code if "
"the feature is enabled, it'll still require generating more shader versions "
"when these features are used in a project. This can make shader compilation "
"stutter more noticeable in complex 3D scenes."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:339
msgid ""
"See `The Shader Permutation Problem <https://therealmjp.github.io/posts/"
"shader-permutations-part1/>`__ and `Branching on a GPU <https://medium.com/"
"@jasonbooth_86226/branching-on-a-gpu-18bfc83694f2>`__ blog posts for more "
"information."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:345
msgid "**Core GLSL material shaders:**"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:347
#, fuzzy
msgid ""
"Forward+: `servers/rendering/renderer_rd/shaders/forward_clustered/"
"scene_forward_clustered.glsl <https://github.com/godotengine/godot/blob/4.2/"
"servers/rendering/renderer_rd/shaders/forward_clustered/"
"scene_forward_clustered.glsl>`__"
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati raznorazne `Godot demo projects "
"<https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:348
#, fuzzy
msgid ""
"Forward Mobile: `servers/rendering/renderer_rd/shaders/forward_mobile/"
"scene_forward_mobile.glsl <https://github.com/godotengine/godot/blob/4.2/"
"servers/rendering/renderer_rd/shaders/forward_mobile/scene_forward_mobile."
"glsl>`__"
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati raznorazne `Godot demo projects "
"<https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:349
#, fuzzy
msgid ""
"Compatibility: `drivers/gles3/shaders/scene.glsl <https://github.com/"
"godotengine/godot/blob/4.2/drivers/gles3/shaders/scene.glsl>`__"
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati raznorazne `Godot demo projects "
"<https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:351
msgid "**Material shader generation:**"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:353
#, fuzzy
msgid ""
"`scene/resources/material.cpp <https://github.com/godotengine/godot/blob/4.2/"
"scene/resources/material.cpp>`__"
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati raznorazne `Godot demo projects "
"<https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:355
msgid ""
"**Other GLSL shaders for Forward+ and Forward Mobile rendering methods:**"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:357
#, fuzzy
msgid ""
"`servers/rendering/renderer_rd/shaders/ <https://github.com/godotengine/"
"godot/blob/4.2/servers/rendering/renderer_rd/shaders/>`__"
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati raznorazne `Godot demo projects "
"<https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:358
#, fuzzy
msgid ""
"`modules/lightmapper_rd/ <https://github.com/godotengine/godot/blob/4.2/"
"modules/lightmapper_rd>`__"
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati raznorazne `Godot demo projects "
"<https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:360
msgid "**Other GLSL shaders for the Compatibility rendering method:**"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:362
#, fuzzy
msgid ""
"`drivers/gles3/shaders/ <https://github.com/godotengine/godot/blob/4.2/"
"drivers/gles3/shaders/>`__"
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati raznorazne `Godot demo projects "
"<https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:365
msgid "2D and 3D rendering separation"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:369
msgid ""
"The following is only applicable in the Forward+ and Forward Mobile "
"rendering methods, not in Compatibility. Multiple Viewports can be used to "
"emulate this when using the Compatibility backend, or to perform 2D "
"resolution scaling."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:374
msgid ""
"2D and 3D are rendered to separate buffers, as 2D rendering in Godot is "
"performed in :abbr:`LDR (Low Dynamic Range)` sRGB-space while 3D rendering "
"uses :abbr:`HDR (High Dynamic Range)` linear space."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:378
msgid ""
"The color format used for 2D rendering is RGB8 (RGBA8 if the **Transparent** "
"property on the Viewport is enabled). 3D rendering uses a 24-bit unsigned "
"normalized integer depth buffer, or 32-bit signed floating-point if a 24-bit "
"depth buffer is not supported by the hardware. 2D rendering does not use a "
"depth buffer."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:384
msgid ""
"3D resolution scaling is performed differently depending on whether bilinear "
"or FSR 1.0 scaling is used. When bilinear scaling is used, no special "
"upscaling shader is run. Instead, the viewport's texture is stretched and "
"displayed with a linear sampler (which makes the filtering happen directly "
"on the hardware). This allows maximizing the performance of bilinear 3D "
"scaling."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:390
msgid ""
"The ``configure()`` function in RenderSceneBuffersRD reallocates the 2D/3D "
"buffers when the resolution or scaling changes."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:393
msgid ""
"Dynamic resolution scaling isn't supported yet, but is planned in a future "
"Godot release."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:396
msgid "**2D and 3D rendering buffer configuration C++ code:**"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:398
#, fuzzy
msgid ""
"`servers/rendering/renderer_rd/storage_rd/render_scene_buffers_rd.cpp "
"<https://github.com/godotengine/godot/blob/4.2/servers/rendering/renderer_rd/"
"storage_rd/render_scene_buffers_rd.cpp>`__"
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati raznorazne `Godot demo projects "
"<https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:400
msgid "**FSR 1.0:**"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:402
#, fuzzy
msgid ""
"`servers/rendering/renderer_rd/effects/fsr.cpp <https://github.com/"
"godotengine/godot/blob/4.2/servers/rendering/renderer_rd/effects/fsr.cpp>`__"
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati raznorazne `Godot demo projects "
"<https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:403
#, fuzzy
msgid ""
"`thirdparty/amd-fsr/ <https://github.com/godotengine/godot/tree/master/"
"thirdparty/amd-fsr>`__"
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati raznorazne `Godot demo projects "
"<https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:406
msgid "2D rendering techniques"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:408
msgid ""
"2D light rendering is performed in a single pass to allow for better "
"performance with large amounts of lights."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:411
msgid ""
"The Forward+ and Mobile rendering methods don't feature 2D batching yet, but "
"it's planned for a future release."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:414
msgid ""
"The Compatibility backend features 2D batching to improve performance, which "
"is especially noticeable with lots of text on screen."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:417
msgid ""
"MSAA can be enabled in 2D to provide \"automatic\" line and polygon "
"antialiasing, but FXAA does not affect 2D rendering as it's calculated "
"before 2D rendering begins. Godot's 2D drawing methods such as the Line2D "
"node or some CanvasItem ``draw_*()`` methods provide their own way of "
"antialiasing based on triangle strips and vertex colors, which don't require "
"MSAA to work."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:423
msgid ""
"A 2D signed distance field representing LightOccluder2D nodes in the "
"viewport is automatically generated if an user shader requests it. This can "
"be used for various effects in custom shaders, such as 2D global "
"illumination. It is also used to calculate particle collisions in 2D."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:428
msgid "**2D SDF generation GLSL shader:**"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:430
#, fuzzy
msgid ""
"`servers/rendering/renderer_rd/shaders/canvas_sdf.glsl <https://github.com/"
"godotengine/godot/blob/4.2/servers/rendering/renderer_rd/shaders/canvas_sdf."
"glsl>`__"
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati raznorazne `Godot demo projects "
"<https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:433
msgid "3D rendering techniques"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:436
#, fuzzy
msgid "Batching and instancing"
msgstr "Kreiranje Sadržaja"

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:438
msgid ""
"In the Forward+ backend, Vulkan instancing is used to group rendering of "
"identical objects for performance. This is not as fast as static mesh "
"merging, but it still allows instances to be culled individually."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:443
msgid "Light, decal and reflection probe rendering"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:447
msgid ""
"Reflection probe and decal rendering are currently not available in the "
"Compatibility backend."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:450
msgid ""
"As its name implies, the Forward+ backend uses clustered lighting. This "
"allows using as many lights as you want; performance largely depends on "
"screen coverage. Shadow-less lights can be almost free if they don't occupy "
"much space on screen."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:455
msgid ""
"All rendering methods also support rendering up to 8 directional lights at "
"the same time (albeit with lower shadow quality when more than one light has "
"shadows enabled)."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:459
msgid ""
"The Forward Mobile backend uses a single-pass lighting approach, with a "
"limitation of 8 OmniLights + 8 SpotLights affecting each Mesh *resource* "
"(plus a limitation of 256 OmniLights + 256 SpotLights in the camera view). "
"These limits are hardcoded and can't be adjusted in the project settings."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:464
msgid ""
"The Compatibility backend uses a hybrid single-pass + multi-pass lighting "
"approach. Lights without shadows are rendered in a single pass. Lights with "
"shadows are rendered in multiple passes. This is required for performance "
"reasons on mobile devices. As a result, performance does not scale well with "
"many shadow-casting lights. It is recommended to only have a handful of "
"lights with shadows in the camera frustum at a time and for those lights to "
"be spread apart so that each object is only touched by 1 or 2 shadowed "
"lights at a time. The maximum number of lights visible at once can be "
"adjusted in the project settings."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:474
msgid ""
"In all 3 methods, lights without shadows are much cheaper than lights with "
"shadows. To improve performance, lights are only updated when the light is "
"modified or when objects in its radius are modified. Godot currently doesn't "
"separate static shadow rendering from dynamic shadow rendering, but this is "
"planned in a future release."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:480
msgid ""
"Clustering is also used for reflection probes and decal rendering in the "
"Forward+ backend."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:486
msgid ""
"Both Forward+ and Forward Mobile methods use :abbr:`PCF (Percentage Closer "
"Filtering)` to filter shadow maps and create a soft penumbra. Instead of "
"using a fixed PCF pattern, these methods use a vogel disk pattern which "
"allows for changing the number of samples and smoothly changing the quality."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:492
msgid ""
"Godot also supports percentage-closer soft shadows (PCSS) for more realistic "
"shadow penumbra rendering. PCSS shadows are limited to the Forward+ backend "
"as they're too demanding to be usable in the Forward Mobile backend. PCSS "
"also uses a vogel-disk shaped kernel."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:497
msgid ""
"Additionally, both shadow-mapping techniques rotate the kernel on a per-"
"pixel basis to help soften under-sampling artifacts."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:500
msgid ""
"The Compatibility backend doesn't support shadow mapping for any light types "
"yet."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:503
msgid "Temporal antialiasing"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:507
#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:622
#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:699
msgid ""
"Only available in the Forward+ backend, not the Forward Mobile or "
"Compatibility methods."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:510
msgid ""
"Godot uses a custom TAA implementation based on the old TAA implementation "
"from `Spartan Engine <https://github.com/PanosK92/SpartanEngine>`__."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:513
msgid ""
"Temporal antialiasing requires motion vectors to work. If motion vectors are "
"not correctly generated, ghosting will occur when the camera or objects move."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:516
msgid ""
"Motion vectors are generated on the GPU in the main material shader. This is "
"done by running the vertex shader corresponding to the previous rendered "
"frame (with the previous camera transform) in addition to the vertex shader "
"for the current rendered frame, then storing the difference between them in "
"a color buffer."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:521
msgid ""
"Alternatively, FSR 2.2 can be used as an upscaling solution that also "
"provides its own temporal antialiasing algorithm. FSR 2.2 is implemented on "
"top of the RenderingDevice abstraction as opposed to using AMD's reference "
"code directly."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:525
msgid "**TAA resolve:**"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:527
#, fuzzy
msgid ""
"`servers/rendering/renderer_rd/shaders/effects/taa_resolve.glsl <https://"
"github.com/godotengine/godot/blob/4.2/servers/rendering/renderer_rd/shaders/"
"effects/taa_resolve.glsl>`__"
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati raznorazne `Godot demo projects "
"<https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:529
msgid "**FSR 2.2:**"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:531
#, fuzzy
msgid ""
"`servers/rendering/renderer_rd/effects/fsr2.cpp <https://github.com/"
"godotengine/godot/blob/4.2/servers/rendering/renderer_rd/effects/fsr2.cpp>`__"
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati raznorazne `Godot demo projects "
"<https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:532
#, fuzzy
msgid ""
"`servers/rendering/renderer_rd/shaders/effects/fsr2/ <https://github.com/"
"godotengine/godot/tree/master/servers/rendering/renderer_rd/shaders/effects/"
"fsr2>`__"
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati raznorazne `Godot demo projects "
"<https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:533
#, fuzzy
msgid ""
"`thirdparty/amd-fsr2/ <https://github.com/godotengine/godot/tree/master/"
"thirdparty/amd-fsr2>`__"
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati raznorazne `Godot demo projects "
"<https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:540
msgid ""
"VoxelGI and SDFGI are only available in the Forward+ backend, not the "
"Forward Mobile or Compatibility methods."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:543
msgid ""
"LightmapGI *baking* is only available in the Forward+ and Forward Mobile "
"methods, and can only be performed within the editor (not in an exported "
"project). LightmapGI *rendering* will eventually be supported by the "
"Compatibility backend."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:548
msgid ""
"Godot supports voxel-based GI (VoxelGI), signed distance field GI (SDFGI) "
"and lightmap baking and rendering (LightmapGI). These techniques can be used "
"simultaneously if desired."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:552
msgid ""
"Lightmap baking happens on the GPU using Vulkan compute shaders. The GPU-"
"based lightmapper is implemented in the LightmapperRD class, which inherits "
"from the Lightmapper class. This allows for implementing additional "
"lightmappers, paving the way for a future port of the CPU-based lightmapper "
"present in Godot 3.x. This would allow baking lightmaps while using the "
"Compatibility backend."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:558
msgid "**Core GI C++ code:**"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:560
#, fuzzy
msgid ""
"`servers/rendering/renderer_rd/environment/gi.cpp <https://github.com/"
"godotengine/godot/blob/4.2/servers/rendering/renderer_rd/environment/gi."
"cpp>`__"
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati raznorazne `Godot demo projects "
"<https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:561
#, fuzzy
msgid ""
"`scene/3d/voxel_gi.cpp <https://github.com/godotengine/godot/blob/4.2/"
"scene/3d/voxel_gi.cpp>`__ - VoxelGI node"
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati raznorazne `Godot demo projects "
"<https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:562
#, fuzzy
msgid ""
"`editor/plugins/voxel_gi_editor_plugin.cpp <https://github.com/godotengine/"
"godot/blob/4.2/editor/plugins/voxel_gi_editor_plugin.cpp>`__ - Editor UI for "
"the VoxelGI node"
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati raznorazne `Godot demo projects "
"<https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:564
msgid "**Core GI GLSL shaders:**"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:566
#, fuzzy
msgid ""
"`servers/rendering/renderer_rd/shaders/environment/voxel_gi.glsl <https://"
"github.com/godotengine/godot/blob/4.2/servers/rendering/renderer_rd/shaders/"
"environment/voxel_gi.glsl>`__"
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati raznorazne `Godot demo projects "
"<https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:567
#, fuzzy
msgid ""
"`servers/rendering/renderer_rd/shaders/environment/voxel_gi_debug.glsl "
"<https://github.com/godotengine/godot/blob/4.2/servers/rendering/renderer_rd/"
"shaders/environment/voxel_gi_debug.glsl>`__ - VoxelGI debug draw mode"
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati raznorazne `Godot demo projects "
"<https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:568
#, fuzzy
msgid ""
"`servers/rendering/renderer_rd/shaders/environment/sdfgi_debug.glsl <https://"
"github.com/godotengine/godot/blob/4.2/servers/rendering/renderer_rd/shaders/"
"environment/sdfgi_debug.glsl>`__ - SDFGI Cascades debug draw mode"
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati raznorazne `Godot demo projects "
"<https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:569
#, fuzzy
msgid ""
"`servers/rendering/renderer_rd/shaders/environment/sdfgi_debug_probes.glsl "
"<https://github.com/godotengine/godot/blob/4.2/servers/rendering/renderer_rd/"
"shaders/environment/sdfgi_debug_probes.glsl>`__ - SDFGI Probes debug draw "
"mode"
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati raznorazne `Godot demo projects "
"<https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:570
#, fuzzy
msgid ""
"`servers/rendering/renderer_rd/shaders/environment/sdfgi_integrate.glsl "
"<https://github.com/godotengine/godot/blob/4.2/servers/rendering/renderer_rd/"
"shaders/environment/sdfgi_integrate.glsl>`__"
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati raznorazne `Godot demo projects "
"<https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:571
#, fuzzy
msgid ""
"`servers/rendering/renderer_rd/shaders/environment/sdfgi_preprocess.glsl "
"<https://github.com/godotengine/godot/blob/4.2/servers/rendering/renderer_rd/"
"shaders/environment/sdfgi_preprocess.glsl>`__"
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati raznorazne `Godot demo projects "
"<https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:572
#, fuzzy
msgid ""
"`servers/rendering/renderer_rd/shaders/environment/sdfgi_direct_light.glsl "
"<https://github.com/godotengine/godot/blob/4.2/servers/rendering/renderer_rd/"
"shaders/environment/sdfgi_direct_light.glsl>`__"
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati raznorazne `Godot demo projects "
"<https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:574
msgid "**Lightmapper C++ code:**"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:576
#, fuzzy
msgid ""
"`scene/3d/lightmap_gi.cpp <https://github.com/godotengine/godot/blob/4.2/"
"scene/3d/lightmap_gi.cpp>`__ - LightmapGI node"
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati raznorazne `Godot demo projects "
"<https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:577
#, fuzzy
msgid ""
"`editor/plugins/lightmap_gi_editor_plugin.cpp <https://github.com/"
"godotengine/godot/blob/4.2/editor/plugins/lightmap_gi_editor_plugin.cpp>`__ "
"- Editor UI for the LightmapGI node"
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati raznorazne `Godot demo projects "
"<https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:578
#, fuzzy
msgid ""
"`scene/3d/lightmapper.cpp <https://github.com/godotengine/godot/blob/4.2/"
"scene/3d/lightmapper.cpp>`__ - Abstract class"
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati raznorazne `Godot demo projects "
"<https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:579
#, fuzzy
msgid ""
"`modules/lightmapper_rd/lightmapper_rd.cpp <https://github.com/godotengine/"
"godot/blob/4.2/modules/lightmapper_rd/lightmapper_rd.cpp>`__ - GPU-based "
"lightmapper implementation"
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati raznorazne `Godot demo projects "
"<https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:581
msgid "**Lightmapper GLSL shaders:**"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:583
#, fuzzy
msgid ""
"`modules/lightmapper_rd/lm_raster.glsl <https://github.com/godotengine/godot/"
"blob/4.2/modules/lightmapper_rd/lm_raster.glsl>`__"
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati raznorazne `Godot demo projects "
"<https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:584
#, fuzzy
msgid ""
"`modules/lightmapper_rd/lm_compute.glsl <https://github.com/godotengine/"
"godot/blob/4.2/modules/lightmapper_rd/lm_compute.glsl>`__"
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati raznorazne `Godot demo projects "
"<https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:585
#, fuzzy
msgid ""
"`modules/lightmapper_rd/lm_blendseams.glsl <https://github.com/godotengine/"
"godot/blob/4.2/modules/lightmapper_rd/lm_blendseams.glsl>`__"
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati raznorazne `Godot demo projects "
"<https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:588
msgid "Depth of field"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:592
msgid ""
"Only available in the Forward+ and Forward Mobile methods, not the "
"Compatibility backend."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:595
msgid ""
"The Forward+ and Forward Mobile methods use different approaches to DOF "
"rendering, with different visual results. This is done to best match the "
"performance characteristics of the target hardware. In Clustered Forward, "
"DOF is performed using a compute shader. In Forward Mobile, DOF is performed "
"using a fragment shader (raster)."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:601
msgid ""
"Box, hexagon and circle bokeh shapes are available (from fastest to "
"slowest). Depth of field can optionally be jittered every frame to improve "
"its appearance when temporal antialiasing is enabled."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:605
msgid "**Depth of field C++ code:**"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:607
#, fuzzy
msgid ""
"`servers/rendering/renderer_rd/effects/bokeh_dof.cpp <https://github.com/"
"godotengine/godot/blob/4.2/servers/rendering/renderer_rd/effects/bokeh_dof."
"cpp>`__"
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati raznorazne `Godot demo projects "
"<https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:609
msgid "**Depth of field GLSL shader (compute - used for Forward+):**"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:611
#, fuzzy
msgid ""
"`servers/rendering/renderer_rd/shaders/effects/bokeh_dof.glsl <https://"
"github.com/godotengine/godot/blob/4.2/servers/rendering/renderer_rd/shaders/"
"effects/bokeh_dof.glsl>`__"
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati raznorazne `Godot demo projects "
"<https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:613
msgid "**Depth of field GLSL shader (raster - used for Forward Mobile):**"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:615
#, fuzzy
msgid ""
"`servers/rendering/renderer_rd/shaders/effects/bokeh_dof_raster.glsl "
"<https://github.com/godotengine/godot/blob/4.2/servers/rendering/renderer_rd/"
"shaders/effects/bokeh_dof_raster.glsl>`__"
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati raznorazne `Godot demo projects "
"<https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:618
msgid "Screen-space effects (SSAO, SSIL, SSR, SSS)"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:625
msgid ""
"The Forward+ backend supports screen-space ambient occlusion, screen-space "
"indirect lighting, screen-space reflections and subsurface scattering."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:628
msgid ""
"SSAO uses an implementation derived from Intel's `ASSAO <https://www.intel."
"com/content/www/us/en/developer/articles/technical/adaptive-screen-space-"
"ambient-occlusion.html>`__ (converted to Vulkan). SSIL is derived from SSAO "
"to provide high-performance indirect lighting."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:633
msgid ""
"When both SSAO and SSIL are enabled, parts of SSAO and SSIL are shared to "
"reduce the performance impact."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:636
msgid ""
"SSAO and SSIL are performed at half resolution by default to improve "
"performance. SSR is always performed at half resolution to improve "
"performance."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:639
msgid "**Screen-space effects C++ code:**"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:641
#, fuzzy
msgid ""
"`servers/rendering/renderer_rd/effects/ss_effects.cpp <https://github.com/"
"godotengine/godot/blob/4.2/servers/rendering/renderer_rd/effects/ss_effects."
"cpp>`__"
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati raznorazne `Godot demo projects "
"<https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:643
msgid "**Screen-space ambient occlusion GLSL shader:**"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:645
#, fuzzy
msgid ""
"`servers/rendering/renderer_rd/shaders/effects/ssao.glsl <https://github.com/"
"godotengine/godot/blob/4.2/servers/rendering/renderer_rd/shaders/effects/"
"ssao.glsl>`__"
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati raznorazne `Godot demo projects "
"<https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:646
#, fuzzy
msgid ""
"`servers/rendering/renderer_rd/shaders/effects/ssao_blur.glsl <https://"
"github.com/godotengine/godot/blob/4.2/servers/rendering/renderer_rd/shaders/"
"effects/ssao_blur.glsl>`__"
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati raznorazne `Godot demo projects "
"<https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:647
#, fuzzy
msgid ""
"`servers/rendering/renderer_rd/shaders/effects/ssao_interleave.glsl <https://"
"github.com/godotengine/godot/blob/4.2/servers/rendering/renderer_rd/shaders/"
"effects/ssao_interleave.glsl>`__"
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati raznorazne `Godot demo projects "
"<https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:648
#, fuzzy
msgid ""
"`servers/rendering/renderer_rd/shaders/effects/ssao_importance_map.glsl "
"<https://github.com/godotengine/godot/blob/4.2/servers/rendering/renderer_rd/"
"shaders/effects/ssao_importance_map.glsl>`__"
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati raznorazne `Godot demo projects "
"<https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:650
msgid "**Screen-space indirect lighting GLSL shader:**"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:652
#, fuzzy
msgid ""
"`servers/rendering/renderer_rd/shaders/effects/ssil.glsl <https://github.com/"
"godotengine/godot/blob/4.2/servers/rendering/renderer_rd/shaders/effects/"
"ssil.glsl>`__"
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati raznorazne `Godot demo projects "
"<https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:653
#, fuzzy
msgid ""
"`servers/rendering/renderer_rd/shaders/effects/ssil_blur.glsl <https://"
"github.com/godotengine/godot/blob/4.2/servers/rendering/renderer_rd/shaders/"
"effects/ssil_blur.glsl>`__"
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati raznorazne `Godot demo projects "
"<https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:654
#, fuzzy
msgid ""
"`servers/rendering/renderer_rd/shaders/effects/ssil_interleave.glsl <https://"
"github.com/godotengine/godot/blob/4.2/servers/rendering/renderer_rd/shaders/"
"effects/ssil_interleave.glsl>`__"
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati raznorazne `Godot demo projects "
"<https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:655
#, fuzzy
msgid ""
"`servers/rendering/renderer_rd/shaders/effects/ssil_importance_map.glsl "
"<https://github.com/godotengine/godot/blob/4.2/servers/rendering/renderer_rd/"
"shaders/effects/ssil_importance_map.glsl>`__"
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati raznorazne `Godot demo projects "
"<https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:657
msgid "**Screen-space reflections GLSL shader:**"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:659
#, fuzzy
msgid ""
"`servers/rendering/renderer_rd/shaders/effects/screen_space_reflection.glsl "
"<https://github.com/godotengine/godot/blob/4.2/servers/rendering/renderer_rd/"
"shaders/effects/screen_space_reflection.glsl>`__"
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati raznorazne `Godot demo projects "
"<https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:660
#, fuzzy
msgid ""
"`servers/rendering/renderer_rd/shaders/effects/screen_space_reflection_scale."
"glsl <https://github.com/godotengine/godot/blob/4.2/servers/rendering/"
"renderer_rd/shaders/effects/screen_space_reflection_scale.glsl>`__"
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati raznorazne `Godot demo projects "
"<https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:661
#, fuzzy
msgid ""
"`servers/rendering/renderer_rd/shaders/effects/"
"screen_space_reflection_filter.glsl <https://github.com/godotengine/godot/"
"blob/4.2/servers/rendering/renderer_rd/shaders/effects/"
"screen_space_reflection_filter.glsl>`__"
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati raznorazne `Godot demo projects "
"<https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:663
msgid "**Subsurface scattering GLSL:**"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:665
#, fuzzy
msgid ""
"`servers/rendering/renderer_rd/shaders/effects/subsurface_scattering.glsl "
"<https://github.com/godotengine/godot/blob/4.2/servers/rendering/renderer_rd/"
"shaders/effects/subsurface_scattering.glsl>`__"
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati raznorazne `Godot demo projects "
"<https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:668
msgid "Sky rendering"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:672
#, fuzzy
msgid ":ref:`doc_sky_shader`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:674
msgid ""
"Godot supports using shaders to render the sky background. The radiance map "
"(which is used to provide ambient light and reflections for PBR materials) "
"is automatically updated based on the sky shader."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:678
msgid ""
"The SkyMaterial resources such as ProceduralSkyMaterial, PhysicalSkyMaterial "
"and PanoramaSkyMaterial generate a built-in shader for sky rendering. This "
"is similar to what BaseMaterial3D provides for 3D scene materials."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:682
msgid ""
"A detailed technical implementation can be found in the `Custom sky shaders "
"in Godot 4.0 <https://godotengine.org/article/custom-sky-shaders-"
"godot-4-0>`__ article."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:686
msgid "**Sky rendering C++ code:**"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:688
#, fuzzy
msgid ""
"`servers/rendering/renderer_rd/environment/sky.cpp <https://github.com/"
"godotengine/godot/blob/4.2/servers/rendering/renderer_rd/environment/sky."
"cpp>`__ - Sky rendering"
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati raznorazne `Godot demo projects "
"<https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:689
#, fuzzy
msgid ""
"`scene/resources/sky.cpp <https://github.com/godotengine/godot/blob/4.2/"
"scene/resources/sky.cpp>`__ - Sky resource (not to be confused with sky "
"rendering)"
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati raznorazne `Godot demo projects "
"<https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:690
#, fuzzy
msgid ""
"`scene/resources/sky_material.cpp <https://github.com/godotengine/godot/"
"blob/4.2/scene/resources/sky_material.cpp>`__ SkyMaterial resources (used in "
"the Sky resource)"
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati raznorazne `Godot demo projects "
"<https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:692
msgid "**Sky rendering GLSL shader:**"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:695
msgid "Volumetric fog"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:704
#, fuzzy
msgid ":ref:`doc_fog_shader`"
msgstr "Kreiranje Sadržaja"

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:706
msgid ""
"Godot supports a frustum-aligned voxel (froxel) approach to volumetric fog "
"rendering. As opposed to a post-processing filter, this approach is more "
"general-purpose as it can work with any light type. Fog can also use shaders "
"for custom behavior, which allows animating the fog or using a 3D texture to "
"represent density."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:712
msgid ""
"The FogMaterial resource generates a built-in shader for FogVolume nodes. "
"This is similar to what BaseMaterial3D provides for 3D scene materials."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:715
msgid ""
"A detailed technical explanation can be found in the `Fog Volumes arrive in "
"Godot 4.0 <https://godotengine.org/article/fog-volumes-arrive-in-godot-4>`__ "
"article."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:719
msgid "**Volumetric fog C++ code:**"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:721
#, fuzzy
msgid ""
"`servers/rendering/renderer_rd/environment/fog.cpp <https://github.com/"
"godotengine/godot/blob/4.2/servers/rendering/renderer_rd/environment/fog."
"cpp>`__ - General volumetric fog"
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati raznorazne `Godot demo projects "
"<https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:722
#, fuzzy
msgid ""
"`scene/3d/fog_volume.cpp <https://github.com/godotengine/godot/blob/4.2/"
"scene/3d/fog_volume.cpp>`__ - FogVolume node"
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati raznorazne `Godot demo projects "
"<https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:723
#, fuzzy
msgid ""
"`scene/resources/fog_material.cpp <https://github.com/godotengine/godot/"
"blob/4.2/scene/resources/fog_material.cpp>`__ - FogMaterial resource (used "
"by FogVolume)"
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati raznorazne `Godot demo projects "
"<https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:725
msgid "**Volumetric fog GLSL shaders:**"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:727
#, fuzzy
msgid ""
"`servers/rendering/renderer_rd/shaders/environment/volumetric_fog.glsl "
"<https://github.com/godotengine/godot/blob/4.2/servers/rendering/renderer_rd/"
"shaders/environment/volumetric_fog.glsl>`__"
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati raznorazne `Godot demo projects "
"<https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:728
#, fuzzy
msgid ""
"`servers/rendering/renderer_rd/shaders/environment/volumetric_fog_process."
"glsl <https://github.com/godotengine/godot/blob/4.2/servers/rendering/"
"renderer_rd/shaders/environment/volumetric_fog_process.glsl>`__"
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati raznorazne `Godot demo projects "
"<https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:733
msgid ""
"While modern GPUs can handle drawing a lot of triangles, the number of draw "
"calls in complex scenes can still be a bottleneck (even with Vulkan and "
"Direct3D 12)."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:737
msgid ""
"Godot 4 supports occlusion culling to reduce overdraw (when the depth "
"prepass is disabled) and reduce vertex throughput. This is done by "
"rasterizing a low-resolution buffer on the CPU using `Embree <https://github."
"com/embree/embree>`__. The buffer's resolution depends on the number of CPU "
"threads on the system, as this is done in parallel. This buffer includes "
"occluder shapes that were baked in the editor or created at run-time."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:745
msgid ""
"As complex occluders can introduce a lot of strain on the CPU, baked "
"occluders can be simplified automatically when generated in the editor."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:748
msgid ""
"Godot's occlusion culling doesn't support dynamic occluders yet, but "
"OccluderInstance3D nodes can still have their visibility toggled or be "
"moved. However, this will be slow when updating complex occluders this way. "
"Therefore, updating occluders at run-time is best done only on simple "
"occluder shapes such as quads or cuboids."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:754
msgid ""
"This CPU-based approach has a few advantages over other solutions, such as "
"portals and rooms or a GPU-based culling solution:"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:757
msgid ""
"No manual setup required (but can be tweaked manually for best performance)."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:758
msgid ""
"No frame delay, which is problematic in cutscenes during camera cuts or when "
"the camera moves fast behind a wall."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:760
msgid ""
"Works the same on all rendering drivers and methods, with no unpredictable "
"behavior depending on the driver or GPU hardware."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:763
msgid ""
"Occlusion culling is performed by registering occluder meshes, which is done "
"using OccluderInstance3D *nodes* (which themselves use Occluder3D "
"*resources*). RenderingServer then performs occlusion culling by calling "
"Embree in RendererSceneOcclusionCull."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:768
msgid "**Occlusion culling C++ code:**"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:770
#, fuzzy
msgid ""
"`scene/3d/occluder_instance_3d.cpp <https://github.com/godotengine/godot/"
"blob/4.2/scene/3d/occluder_instance_3d.cpp>`__"
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati raznorazne `Godot demo projects "
"<https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:771
#, fuzzy
msgid ""
"`servers/rendering/renderer_scene_occlusion_cull.cpp <https://github.com/"
"godotengine/godot/blob/4.2/servers/rendering/renderer_scene_occlusion_cull."
"cpp>`__"
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati raznorazne `Godot demo projects "
"<https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:774
msgid "Visibility range (LOD)"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:776
msgid ""
"Godot supports manually authored hierarchical level of detail (HLOD), with "
"distances specified by the user in the inspector."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:779
msgid ""
"In RenderingSceneCull, the ``_scene_cull()`` and ``_render_scene()`` "
"functions are where most of the LOD determination happens. Each viewport can "
"render the same mesh with different LODs (to allow for split screen "
"rendering to look correct)."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:783
msgid "**Visibility range C++ code:**"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:785
#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:816
#, fuzzy
msgid ""
"`servers/rendering/renderer_scene_cull.cpp <https://github.com/godotengine/"
"godot/blob/4.2/servers/rendering/renderer_scene_cull.cpp>`__"
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati raznorazne `Godot demo projects "
"<https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:788
msgid "Automatic mesh LOD"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:790
msgid ""
"The ImporterMesh class is used for the 3D mesh import workflow in the "
"editor. Its ``generate_lods()`` function handles generating using the "
"`meshoptimizer <https://meshoptimizer.org/>`__ library."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:794
msgid ""
"LOD mesh generation also generates shadow meshes at the same time. These are "
"meshes that have their vertices welded regardless of smoothing and "
"materials. This is used to improve shadow rendering performance by lowering "
"the vertex throughput required to render shadows."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:799
msgid ""
"The RenderingSceneCull class's ``_render_scene()`` function determines which "
"mesh LOD should be used when rendering. Each viewport can render the same "
"mesh with different LODs (to allow for split screen rendering to look "
"correct)."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:803
msgid ""
"The mesh LOD is automatically chosen based on a screen coverage metric. This "
"takes resolution and camera FOV changes into account without requiring user "
"intervention. The threshold multiplier can be adjusted in the project "
"settings."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:807
msgid ""
"To improve performance, shadow rendering and reflection probe rendering also "
"choose their own mesh LOD thresholds (which can be different from the main "
"scene rendering)."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:810
msgid "**Mesh LOD generation on import C++ code:**"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:812
#, fuzzy
msgid ""
"`scene/resources/importer_mesh.cpp <https://github.com/godotengine/godot/"
"blob/4.2/scene/resources/importer_mesh.cpp>`__"
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati raznorazne `Godot demo projects "
"<https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/contributing/development/core_and_modules/internal_rendering_architecture.rst:814
msgid "**Mesh LOD determination C++ code:**"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/2d_coordinate_systems.rst:4
msgid "2D coordinate systems and 2D transforms"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/2d_coordinate_systems.rst:9
msgid ""
"This is a detailed overview of the available 2D coordinate systems and 2D "
"transforms that are built in. The basic concepts are covered in :ref:"
"`doc_viewport_and_canvas_transforms`."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/2d_coordinate_systems.rst:12
msgid ""
":ref:`Transform2D <class_Transform2D>` are matrices that convert coordinates "
"from one coordinate system to an other. In order to use them, it is "
"beneficial to know which coordinate systems are available in Godot. For a "
"deeper understanding, the :ref:`doc_matrices_and_transforms` tutorial offers "
"insights to the underlying functionality."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/2d_coordinate_systems.rst:18
msgid "Godot 2D coordinate systems"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/2d_coordinate_systems.rst:20
msgid ""
"The following graphic gives an overview of Godot 2D coordinate systems and "
"the available node-transforms, transform-functions and coordinate-system "
"related functions. At the left is the OS Window Manager screen, at the right "
"are the :ref:`CanvasItems <class_CanvasItem>`. For simplicity reasons this "
"graphic doesn't include :ref:`SubViewport <class_SubViewport>`, :ref:"
"`SubViewportContainer <class_SubViewportContainer>`, :ref:"
"`ParallaxLayer<class_ParallaxLayer>` and :ref:"
"`ParallaxBackground<class_ParallaxBackground>` all of which also influence "
"transforms."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/2d_coordinate_systems.rst:27
msgid ""
"The graphic is based on a node tree of the following form: ``Root Window "
"(embed Windows)`` ⇒ ``Window (don't embed Windows)`` ⇒ ``CanvasLayer`` ⇒ "
"``CanvasItem`` ⇒ ``CanvasItem`` ⇒ ``CanvasItem``. There are more complex "
"combinations possible, like deeply nested Window and SubViewports, however "
"this example intends to provide an overview of the methodology in general."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/2d_coordinate_systems.rst:35
msgid "Click graphic to enlarge."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/2d_coordinate_systems.rst:38
msgid "**Item Coordinates**"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/2d_coordinate_systems.rst:38
msgid ""
"This is the local coordinate system of a :ref:`CanvasItem "
"<class_CanvasItem>`."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/2d_coordinate_systems.rst:44
msgid "**Parent Item Coordinates**"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/2d_coordinate_systems.rst:41
msgid ""
"This is the local coordinate system of the parent's *CanvasItem*. When "
"positioning *CanvasItems* in the *Canvas*, they usually inherit the "
"transformations of their parent *CanvasItems*. An exceptions is :ref:"
"`CanvasItems.top_level <class_CanvasItem_property_top_level>`."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/2d_coordinate_systems.rst:50
msgid "**Canvas Coordinates**"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/2d_coordinate_systems.rst:47
msgid ""
"As mentioned in the previous tutorial :ref:`doc_canvas_layers`, there are "
"two types of canvases (*Viewport* canvas and *CanvasLayer* canvas) and both "
"have a canvas coordinate system. These are also called world coordinates. A "
"*Viewport* can contain multiple *Canvases* with different coordinate systems."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/2d_coordinate_systems.rst:53
msgid "**Viewport Coordinates**"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/2d_coordinate_systems.rst:53
msgid "This is the coordinate system of the :ref:`Viewport <class_Viewport>`."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/2d_coordinate_systems.rst:56
msgid "**Camera Coordinates**"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/2d_coordinate_systems.rst:56
msgid ""
"This is only used internally for functionality like 3D-camera ray "
"projections."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/2d_coordinate_systems.rst:64
msgid "**Embedder Coordinates / Screen Coordinates**"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/2d_coordinate_systems.rst:59
msgid ""
"Every *Viewport* (*Window* or *SubViewport*) in the scene tree is embedded "
"either in a different node or in the OS Window Manager. This coordinate "
"system's origin is identical to the top-left corner of the *Window* or "
"*SubViewport* and its scale is the one of the embedder or the OS Window "
"Manager."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/2d_coordinate_systems.rst:64
msgid ""
"If the embedder is the OS Window Manager, then they are also called Screen "
"Coordinates."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/2d_coordinate_systems.rst:72
msgid "**Absolute Embedder Coordinates / Absolute Screen Coordinates**"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/2d_coordinate_systems.rst:67
msgid ""
"The origin of this coordinate system is the top-left corner of the embedding "
"node or the OS Window Manager screen. Its scale is the one of the embedder "
"or the OS Window Manager."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/2d_coordinate_systems.rst:70
msgid ""
"If the embedder is the OS Window Manager, then they are also called Absolute "
"Screen Coordinates."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/2d_coordinate_systems.rst:75
msgid "Node transforms"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/2d_coordinate_systems.rst:77
msgid ""
"Each of the mentioned nodes have one or more transforms associated with them "
"and the combination of these nodes infer the transforms between the "
"different coordinate systems. With a few exceptions, the transforms are :ref:"
"`Transform2D <class_Transform2D>` and the following list shows details and "
"effects of each of them."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/2d_coordinate_systems.rst:95
msgid "**CanvasItem transform**"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/2d_coordinate_systems.rst:83
msgid "*CanvasItems* are either *Control*-nodes or *Node2D*-nodes."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/2d_coordinate_systems.rst:85
msgid ""
"For *Control* nodes this transform consists of a :ref:`position "
"<class_Control_property_position>` relative to the parent's origin and a :"
"ref:`scale <class_Control_property_scale>` and :ref:`rotation "
"<class_Control_property_rotation>` around a :ref:`pivot point "
"<class_Control_property_pivot_offset>`."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/2d_coordinate_systems.rst:90
msgid ""
"For *Node2D* nodes :ref:`transform <class_Node2D_property_transform>` "
"consists of :ref:`position <class_Node2D_property_position>`, :ref:`rotation "
"<class_Node2D_property_rotation>`, :ref:`scale "
"<class_Node2D_property_scale>` and :ref:`skew <class_Node2D_property_skew>`."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/2d_coordinate_systems.rst:94
msgid ""
"The transform affects the item itself and usually also child-*CanvasItems* "
"and in the case of a *SubViewportContainer* it affects the contained "
"*SubViewport*."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/2d_coordinate_systems.rst:100
msgid "**CanvasLayer transform**"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/2d_coordinate_systems.rst:98
msgid ""
"The *CanvasLayer's* :ref:`transform <class_CanvasLayer_property_transform>` "
"affects all *CanvasItems* within the *CanvasLayer*. It doesn't affect other "
"*CanvasLayers* or *Windows* in its *Viewport*."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/2d_coordinate_systems.rst:107
msgid "**CanvasLayer follow viewport transform**"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/2d_coordinate_systems.rst:103
msgid ""
"The *follow viewport transform* is an automatically calculated transform, "
"that is based on the *Viewport's* :ref:`canvas transform "
"<class_Viewport_property_canvas_transform>` and the *CanvasLayer's* :ref:"
"`follow viewport scale <class_CanvasLayer_property_follow_viewport_scale>` "
"and can be used, if :ref:`enabled "
"<class_CanvasLayer_property_follow_viewport_enabled>`, to achieve a pseudo "
"3D effect. It affects the same child nodes as the *CanvasLayer transform*."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/2d_coordinate_systems.rst:113
msgid "**Viewport canvas transform**"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/2d_coordinate_systems.rst:110
msgid ""
"The :ref:`canvas transform <class_Viewport_property_canvas_transform>` "
"affects all *CanvasItems* in the *Viewport's* default canvas. It also "
"affects *CanvasLayers*, that have follow viewport transform enabled. The "
"*Viewport's* active :ref:`Camera2D <class_Camera2D>` works by changing this "
"transform. It doesn't affect this *Viewport's* embedded *Windows*."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/2d_coordinate_systems.rst:118
msgid "**Viewport global canvas transform**"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/2d_coordinate_systems.rst:116
msgid ""
"*Viewports* also have a :ref:`global canvas transform "
"<class_Viewport_property_global_canvas_transform>`. This is the master "
"transform and affects all individual *Canvas Layer* and embedded *Window* "
"transforms. This is primarily used in Godot's CanvasItem Editor."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/2d_coordinate_systems.rst:129
msgid "**Viewport stretch transform**"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/2d_coordinate_systems.rst:121
msgid ""
"Finally, *Viewports* have a *stretch transform*, which is used when resizing "
"or stretching the viewport. This transform is used for :ref:`Windows "
"<class_Window>` as described in :ref:`doc_multiple_resolutions`, but can "
"also be manually set on *SubViewports* by means of :ref:`size "
"<class_SubViewport_property_size>` and :ref:`size_2d_override "
"<class_SubViewport_property_size_2d_override>`. It's :ref:`translation "
"<class_Transform2D_method_get_origin>`, :ref:`rotation "
"<class_Transform2D_method_get_rotation>` and :ref:`skew "
"<class_Transform2D_method_get_skew>` are the default values and it can only "
"have non-default :ref:`scale <class_Transform2D_method_get_scale>`."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/2d_coordinate_systems.rst:135
msgid "**Window transform**"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/2d_coordinate_systems.rst:132
msgid ""
"In order to scale and position the *Window's* content as described in :ref:"
"`doc_multiple_resolutions`, each :ref:`Window <class_Window>` contains a "
"*window transform*. It is for example responsible for the black bars at the "
"*Window's* sides so that the *Viewport* is displayed with a fixed aspect "
"ratio."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/2d_coordinate_systems.rst:139
msgid "**Window position**"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/2d_coordinate_systems.rst:138
msgid ""
"Every *Window* also has a :ref:`position <class_Window_property_position>` "
"to describe its position within its embedder. The embedder can be another "
"*Viewport* or the OS Window Manager."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/2d_coordinate_systems.rst:146
msgid "**SubViewportContainer shrink transform**"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/2d_coordinate_systems.rst:142
msgid ""
":ref:`stretch <class_SubViewportContainer_property_stretch>` together with :"
"ref:`stretch_shrink <class_SubViewportContainer_property_stretch_shrink>` "
"declare for a *SubViewportContainer* if and by what integer factor the "
"contained *SubViewport* should be scaled in comparison to the container's "
"size."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_modules_in_cpp.rst:4
msgid "Custom modules in C++"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_modules_in_cpp.rst:7
#: ../../docs/contributing/development/core_and_modules/binding_to_external_libraries.rst:7
msgid "Modules"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_modules_in_cpp.rst:9
msgid ""
"Godot allows extending the engine in a modular way. New modules can be "
"created and then enabled/disabled. This allows for adding new engine "
"functionality at every level without modifying the core, which can be split "
"for use and reuse in different modules."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_modules_in_cpp.rst:14
msgid ""
"Modules are located in the ``modules/`` subdirectory of the build system. By "
"default, dozens of modules are enabled, such as GDScript (which, yes, is not "
"part of the base engine), the Mono runtime, a regular expressions module, "
"and others. As many new modules as desired can be created and combined. The "
"SCons build system will take care of it transparently."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_modules_in_cpp.rst:22
#: ../../docs/contributing/development/core_and_modules/custom_godot_servers.rst:26
#: ../../docs/contributing/development/core_and_modules/custom_resource_format_loaders.rst:24
#: ../../docs/contributing/development/core_and_modules/custom_audiostreams.rst:29
msgid "What for?"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_modules_in_cpp.rst:24
msgid ""
"While it's recommended that most of a game be written in scripting (as it is "
"an enormous time saver), it's perfectly possible to use C++ instead. Adding "
"C++ modules can be useful in the following scenarios:"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_modules_in_cpp.rst:28
msgid "Binding an external library to Godot (like PhysX, FMOD, etc)."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_modules_in_cpp.rst:29
msgid "Optimize critical parts of a game."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_modules_in_cpp.rst:30
msgid "Adding new functionality to the engine and/or editor."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_modules_in_cpp.rst:31
msgid "Porting an existing game to Godot."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_modules_in_cpp.rst:32
msgid "Write a whole, new game in C++ because you can't live without C++."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_modules_in_cpp.rst:35
msgid "Creating a new module"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_modules_in_cpp.rst:37
msgid ""
"Before creating a module, make sure to :ref:`download the source code of "
"Godot and compile it <toc-devel-compiling>`."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_modules_in_cpp.rst:40
msgid ""
"To create a new module, the first step is creating a directory inside "
"``modules/``. If you want to maintain the module separately, you can "
"checkout a different VCS into modules and use it."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_modules_in_cpp.rst:44
msgid ""
"The example module will be called \"summator\" (``godot/modules/summator``). "
"Inside we will create a summator class:"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_modules_in_cpp.rst:74
msgid "And then the cpp file."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_modules_in_cpp.rst:104
msgid ""
"Then, the new class needs to be registered somehow, so two more files need "
"to be created:"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_modules_in_cpp.rst:113
#: ../../docs/contributing/development/core_and_modules/binding_to_external_libraries.rst:79
msgid ""
"These files must be in the top-level folder of your module (next to your "
"``SCsub`` and ``config.py`` files) for the module to be registered properly."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_modules_in_cpp.rst:116
#: ../../docs/contributing/development/core_and_modules/binding_to_external_libraries.rst:82
msgid "These files should contain the following:"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_modules_in_cpp.rst:151
msgid ""
"Next, we need to create a ``SCsub`` file so the build system compiles this "
"module:"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_modules_in_cpp.rst:162
msgid ""
"With multiple sources, you can also add each file individually to a Python "
"string list:"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_modules_in_cpp.rst:170
msgid ""
"This allows for powerful possibilities using Python to construct the file "
"list using loops and logic statements. Look at some modules that ship with "
"Godot by default for examples."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_modules_in_cpp.rst:174
#: ../../docs/contributing/development/core_and_modules/binding_to_external_libraries.rst:164
msgid ""
"To add include directories for the compiler to look at you can append it to "
"the environment's paths:"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_modules_in_cpp.rst:182
msgid ""
"If you want to add custom compiler flags when building your module, you need "
"to clone ``env`` first, so it won't add those flags to whole Godot build "
"(which can cause errors). Example ``SCsub`` with custom flags:"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_modules_in_cpp.rst:200
msgid ""
"And finally, the configuration file for the module, this is a Python script "
"that must be named ``config.py``:"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_modules_in_cpp.rst:213
msgid ""
"The module is asked if it's OK to build for the specific platform (in this "
"case, ``True`` means it will build for every platform)."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_modules_in_cpp.rst:216
msgid ""
"And that's it. Hope it was not too complex! Your module should look like "
"this:"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_modules_in_cpp.rst:228
msgid ""
"You can then zip it and share the module with everyone else. When building "
"for every platform (instructions in the previous sections), your module will "
"be included."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_modules_in_cpp.rst:232
msgid ""
"There is a parameter limit of 5 in C++ modules for things such as "
"subclasses. This can be raised to 13 by including the header file ``core/"
"method_bind_ext.gen.inc``."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_modules_in_cpp.rst:237
#: ../../docs/contributing/development/core_and_modules/binding_to_external_libraries.rst:220
msgid "Using the module"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_modules_in_cpp.rst:239
#: ../../docs/contributing/development/core_and_modules/binding_to_external_libraries.rst:222
msgid "You can now use your newly created module from any script:"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_modules_in_cpp.rst:251
msgid "The output will be ``60``."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_modules_in_cpp.rst:253
msgid ""
"The previous Summator example is great for small, custom modules, but what "
"if you want to use a larger, external library? Refer to :ref:"
"`doc_binding_to_external_libraries` for details about binding to external "
"libraries."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_modules_in_cpp.rst:258
msgid ""
"If your module is meant to be accessed from the running project (not just "
"from the editor), you must also recompile every export template you plan to "
"use, then specify the path to the custom template in each export preset. "
"Otherwise, you'll get errors when running the project as the module isn't "
"compiled in the export template. See the :ref:`Compiling <toc-devel-"
"compiling>` pages for more information."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_modules_in_cpp.rst:267
msgid "Compiling a module externally"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_modules_in_cpp.rst:269
msgid ""
"Compiling a module involves moving the module's sources directly under the "
"engine's ``modules/`` directory. While this is the most straightforward way "
"to compile a module, there are a couple of reasons as to why this might not "
"be a practical thing to do:"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_modules_in_cpp.rst:274
msgid ""
"Having to manually copy modules sources every time you want to compile the "
"engine with or without the module, or taking additional steps needed to "
"manually disable a module during compilation with a build option similar to "
"``module_summator_enabled=no``. Creating symbolic links may also be a "
"solution, but you may additionally need to overcome OS restrictions like "
"needing the symbolic link privilege if doing this via script."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_modules_in_cpp.rst:281
msgid ""
"Depending on whether you have to work with the engine's source code, the "
"module files added directly to ``modules/`` changes the working tree to the "
"point where using a VCS (like ``git``) proves to be cumbersome as you need "
"to make sure that only the engine-related code is committed by filtering "
"changes."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_modules_in_cpp.rst:287
msgid ""
"So if you feel like the independent structure of custom modules is needed, "
"lets take our \"summator\" module and move it to the engine's parent "
"directory:"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_modules_in_cpp.rst:295
msgid ""
"Compile the engine with our module by providing ``custom_modules`` build "
"option which accepts a comma-separated list of directory paths containing "
"custom C++ modules, similar to the following:"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_modules_in_cpp.rst:303
msgid ""
"The build system shall detect all modules under the ``../modules`` directory "
"and compile them accordingly, including our \"summator\" module."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_modules_in_cpp.rst:308
msgid ""
"Any path passed to ``custom_modules`` will be converted to an absolute path "
"internally as a way to distinguish between custom and built-in modules. It "
"means that things like generating module documentation may rely on a "
"specific path structure on your machine."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_modules_in_cpp.rst:315
msgid ""
":ref:`Introduction to the buildsystem - Custom modules build option "
"<doc_buildsystem_custom_modules>`."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_modules_in_cpp.rst:318
msgid "Customizing module types initialization"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_modules_in_cpp.rst:320
msgid ""
"Modules can interact with other built-in engine classes during runtime and "
"even affect the way core types are initialized. So far, we've been using "
"``register_summator_types`` as a way to bring in module classes to be "
"available within the engine."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_modules_in_cpp.rst:325
msgid ""
"A crude order of the engine setup can be summarized as a list of the "
"following type registration methods:"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_modules_in_cpp.rst:344
msgid ""
"Our ``Summator`` class is initialized during the ``register_module_types()`` "
"call. Imagine that we need to satisfy some common module run-time dependency "
"(like singletons), or allow us to override existing engine method callbacks "
"before they can be assigned by the engine itself. In that case, we want to "
"ensure that our module classes are registered *before* any other built-in "
"type."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_modules_in_cpp.rst:350
msgid ""
"This is where we can define an optional ``preregister_summator_types()`` "
"method which will be called before anything else during the "
"``preregister_module_types()`` engine setup stage."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_modules_in_cpp.rst:354
msgid ""
"We now need to add this method to ``register_types`` header and source files:"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_modules_in_cpp.rst:366
msgid ""
"Unlike other register methods, we have to explicitly define "
"``MODULE_SUMMATOR_HAS_PREREGISTER`` to let the build system know what "
"relevant method calls to include at compile time. The module's name has to "
"be converted to uppercase as well."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_modules_in_cpp.rst:394
msgid "Improving the build system for development"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_modules_in_cpp.rst:398
msgid ""
"This shared library support is not designed to support distributing a module "
"to other users without recompiling the engine. For that purpose, use a "
"GDExtension instead."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_modules_in_cpp.rst:402
msgid ""
"So far, we defined a clean SCsub that allows us to add the sources of our "
"new module as part of the Godot binary."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_modules_in_cpp.rst:405
msgid ""
"This static approach is fine when we want to build a release version of our "
"game, given we want all the modules in a single binary."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_modules_in_cpp.rst:408
msgid ""
"However, the trade-off is that every single change requires a full "
"recompilation of the game. Even though SCons is able to detect and recompile "
"only the file that was changed, finding such files and eventually linking "
"the final binary takes a long time."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_modules_in_cpp.rst:412
msgid ""
"The solution to avoid such a cost is to build our own module as a shared "
"library that will be dynamically loaded when starting our game's binary."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_modules_in_cpp.rst:453
msgid ""
"Once compiled, we should end up with a ``bin`` directory containing both the "
"``godot*`` binary and our ``libsummator*.so``. However given the .so is not "
"in a standard directory (like ``/usr/lib``), we have to help our binary find "
"it during runtime with the ``LD_LIBRARY_PATH`` environment variable:"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_modules_in_cpp.rst:464
msgid ""
"You have to ``export`` the environment variable. Otherwise, you won't be "
"able to run your project from the editor."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_modules_in_cpp.rst:467
msgid ""
"On top of that, it would be nice to be able to select whether to compile our "
"module as shared library (for development) or as a part of the Godot binary "
"(for release). To do that we can define a custom flag to be passed to SCons "
"using the ``ARGUMENT`` command:"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_modules_in_cpp.rst:498
msgid ""
"Now by default ``scons`` command will build our module as part of Godot's "
"binary and as a shared library when passing ``summator_shared=yes``."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_modules_in_cpp.rst:501
msgid ""
"Finally, you can even speed up the build further by explicitly specifying "
"your shared module as target in the SCons command:"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_modules_in_cpp.rst:509
msgid "Writing custom documentation"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_modules_in_cpp.rst:511
msgid ""
"Writing documentation may seem like a boring task, but it is highly "
"recommended to document your newly created module to make it easier for "
"users to benefit from it. Not to mention that the code you've written one "
"year ago may become indistinguishable from the code that was written by "
"someone else, so be kind to your future self!"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_modules_in_cpp.rst:517
msgid "There are several steps in order to setup custom docs for the module:"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_modules_in_cpp.rst:519
msgid ""
"Make a new directory in the root of the module. The directory name can be "
"anything, but we'll be using the ``doc_classes`` name throughout this "
"section."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_modules_in_cpp.rst:522
msgid "Now, we need to edit ``config.py``, add the following snippet:"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_modules_in_cpp.rst:534
msgid ""
"The ``get_doc_path()`` function is used by the build system to determine the "
"location of the docs. In this case, they will be located in the ``modules/"
"summator/doc_classes`` directory. If you don't define this, the doc path for "
"your module will fall back to the main ``doc/classes`` directory."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_modules_in_cpp.rst:540
msgid ""
"The ``get_doc_classes()`` method is necessary for the build system to know "
"which registered classes belong to the module. You need to list all of your "
"classes here. The classes that you don't list will end up in the main ``doc/"
"classes`` directory."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_modules_in_cpp.rst:547
msgid ""
"You can use Git to check if you have missed some of your classes by checking "
"the untracked files with ``git status``. For example::"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_modules_in_cpp.rst:552
msgid "Example output::"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_modules_in_cpp.rst:564
#, fuzzy
msgid "Now we can generate the documentation:"
msgstr "O dokumentaciji"

#: ../../docs/contributing/development/core_and_modules/custom_modules_in_cpp.rst:566
msgid ""
"We can do this via running Godot's doctool i.e. ``godot --doctool <path>``, "
"which will dump the engine API reference to the given ``<path>`` in XML "
"format."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_modules_in_cpp.rst:569
msgid ""
"In our case we'll point it to the root of the cloned repository. You can "
"point it to an another folder, and just copy over the files that you need."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_modules_in_cpp.rst:572
msgid "Run command:"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_modules_in_cpp.rst:578
msgid ""
"Now if you go to the ``godot/modules/summator/doc_classes`` folder, you will "
"see that it contains a ``Summator.xml`` file, or any other classes, that you "
"referenced in your ``get_doc_classes`` function."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_modules_in_cpp.rst:582
msgid ""
"Edit the file(s) following :ref:`doc_class_reference_primer` and recompile "
"the engine."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_modules_in_cpp.rst:584
msgid ""
"Once the compilation process is finished, the docs will become accessible "
"within the engine's built-in documentation system."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_modules_in_cpp.rst:587
msgid ""
"In order to keep documentation up-to-date, all you'll have to do is simply "
"modify one of the XML files and recompile the engine from now on."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_modules_in_cpp.rst:590
msgid ""
"If you change your module's API, you can also re-extract the docs, they will "
"contain the things that you previously added. Of course if you point it to "
"your godot folder, make sure you don't lose work by extracting older docs "
"from an older engine build on top of the newer ones."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_modules_in_cpp.rst:595
msgid ""
"Note that if you don't have write access rights to your supplied ``<path>``, "
"you might encounter an error similar to the following:"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_modules_in_cpp.rst:606
#, fuzzy
msgid "Writing custom unit tests"
msgstr "Kreiranje Sadržaja"

#: ../../docs/contributing/development/core_and_modules/custom_modules_in_cpp.rst:608
msgid ""
"It's possible to write self-contained unit tests as part of a C++ module. If "
"you are not familiar with the unit testing process in Godot yet, please "
"refer to :ref:`doc_unit_testing`."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_modules_in_cpp.rst:612
#, fuzzy
msgid "The procedure is the following:"
msgstr "Glavna dokumentacija za sajt je podeljena na sledeća poglavlja:"

#: ../../docs/contributing/development/core_and_modules/custom_modules_in_cpp.rst:614
msgid "Create a new directory named ``tests/`` under your module's root:"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_modules_in_cpp.rst:622
msgid ""
"Create a new test suite: ``test_summator.h``. The header must be prefixed "
"with ``test_`` so that the build system can collect it and include it as "
"part of the ``tests/test_main.cpp`` where the tests are run."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_modules_in_cpp.rst:626
msgid "Write some test cases. Here's an example:"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_modules_in_cpp.rst:661
msgid ""
"Compile the engine with ``scons tests=yes``, and run the tests with the "
"following command:"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_modules_in_cpp.rst:668
msgid "You should see the passing assertions now."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_modules_in_cpp.rst:673
msgid "Adding custom editor icons"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_modules_in_cpp.rst:675
msgid ""
"Similarly to how you can write self-contained documentation within a module, "
"you can also create your own custom icons for classes to appear in the "
"editor."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_modules_in_cpp.rst:678
msgid ""
"For the actual process of creating editor icons to be integrated within the "
"engine, please refer to :ref:`doc_editor_icons` first."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_modules_in_cpp.rst:681
msgid "Once you've created your icon(s), proceed with the following steps:"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_modules_in_cpp.rst:683
msgid ""
"Make a new directory in the root of the module named ``icons``. This is the "
"default path for the engine to look for module's editor icons."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_modules_in_cpp.rst:686
msgid ""
"Move your newly created ``svg`` icons (optimized or not) into that folder."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_modules_in_cpp.rst:688
msgid ""
"Recompile the engine and run the editor. Now the icon(s) will appear in "
"editor's interface where appropriate."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_modules_in_cpp.rst:691
msgid ""
"If you'd like to store your icons somewhere else within your module, add the "
"following code snippet to ``config.py`` to override the default path:"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_modules_in_cpp.rst:700
msgid "Summing up"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_modules_in_cpp.rst:702
msgid "Remember to:"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_modules_in_cpp.rst:704
msgid "Use ``GDCLASS`` macro for inheritance, so Godot can wrap it."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_modules_in_cpp.rst:705
msgid ""
"Use ``_bind_methods`` to bind your functions to scripting, and to allow them "
"to work as callbacks for signals."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_modules_in_cpp.rst:707
msgid ""
"**Avoid multiple inheritance for classes exposed to Godot**, as ``GDCLASS`` "
"doesn't support this. You can still use multiple inheritance in your own "
"classes as long as they're not exposed to Godot's scripting API."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_modules_in_cpp.rst:711
msgid ""
"But this is not all, depending what you do, you will be greeted with some "
"(hopefully positive) surprises."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_modules_in_cpp.rst:714
msgid ""
"If you inherit from :ref:`class_Node` (or any derived node type, such as "
"Sprite2D), your new class will appear in the editor, in the inheritance tree "
"in the \"Add Node\" dialog."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_modules_in_cpp.rst:717
msgid ""
"If you inherit from :ref:`class_Resource`, it will appear in the resource "
"list, and all the exposed properties can be serialized when saved/loaded."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_modules_in_cpp.rst:720
msgid ""
"By this same logic, you can extend the Editor and almost any area of the "
"engine."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/binding_to_external_libraries.rst:4
msgid "Binding to external libraries"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/binding_to_external_libraries.rst:9
msgid ""
"The Summator example in :ref:`doc_custom_modules_in_cpp` is great for small, "
"custom modules, but what if you want to use a larger, external library? "
"Let's look at an example using `Festival <https://www.cstr.ed.ac.uk/projects/"
"festival/>`_, a speech synthesis (text-to-speech) library written in C++."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/binding_to_external_libraries.rst:14
msgid ""
"To bind to an external library, set up a module directory similar to the "
"Summator example:"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/binding_to_external_libraries.rst:20
msgid "Next, you will create a header file with a TTS class:"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/binding_to_external_libraries.rst:45
msgid "And then you'll add the cpp file."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/binding_to_external_libraries.rst:70
msgid ""
"Just as before, the new class needs to be registered somehow, so two more "
"files need to be created:"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/binding_to_external_libraries.rst:112
msgid ""
"Next, you need to create a ``SCsub`` file so the build system compiles this "
"module:"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/binding_to_external_libraries.rst:124
msgid ""
"You'll need to install the external library on your machine to get the .a "
"library files. See the library's official documentation for specific "
"instructions on how to do this for your operation system. We've included the "
"installation commands for Linux below, for reference."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/binding_to_external_libraries.rst:135
msgid ""
"The voices that Festival uses (and any other potential external/3rd-party "
"resource) all have varying licenses and terms of use; some (if not most) of "
"them may be be problematic with Godot, even if the Festival Library itself "
"is MIT License compatible. Please be sure to check the licenses and terms of "
"use."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/binding_to_external_libraries.rst:140
msgid ""
"The external library will also need to be installed inside your module to "
"make the source files accessible to the compiler, while also keeping the "
"module code self-contained. The festival and speech_tools libraries can be "
"installed from the modules/tts/ directory via git using the following "
"commands:"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/binding_to_external_libraries.rst:150
msgid ""
"If you don't want the external repository source files committed to your "
"repository, you can link to them instead by adding them as submodules (from "
"within the modules/tts/ directory), as seen below:"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/binding_to_external_libraries.rst:159
msgid ""
"Please note that Git submodules are not used in the Godot repository. If you "
"are developing a module to be merged into the main Godot repository, you "
"should not use submodules. If your module doesn't get merged in, you can "
"always try to implement the external library as a GDExtension."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/binding_to_external_libraries.rst:184
msgid ""
"If you want to add custom compiler flags when building your module, you need "
"to clone `env` first, so it won't add those flags to whole Godot build "
"(which can cause errors). Example `SCsub` with custom flags:"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/binding_to_external_libraries.rst:202
msgid "The final module should look like this:"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/binding_to_external_libraries.rst:231
msgid "And the output will be ``is_spoken: True`` if the text is spoken."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_godot_servers.rst:4
msgid "Custom Godot servers"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_godot_servers.rst:9
msgid ""
"Godot implements multi-threading as servers. Servers are daemons which "
"manage data, process it, and push the result. Servers implement the mediator "
"pattern which interprets resource ID and process data for the engine and "
"other modules. In addition, the server claims ownership for its RID "
"allocations."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_godot_servers.rst:15
msgid ""
"This guide assumes the reader knows how to create C++ modules and Godot data "
"types. If not, refer to :ref:`doc_custom_modules_in_cpp`."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_godot_servers.rst:21
msgid ""
"`Why does Godot use servers and RIDs? <https://godotengine.org/article/why-"
"does-godot-use-servers-and-rids>`__"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_godot_servers.rst:22
msgid "`Singleton pattern <https://en.wikipedia.org/wiki/Singleton_pattern>`__"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_godot_servers.rst:23
msgid "`Mediator pattern <https://en.wikipedia.org/wiki/Mediator_pattern>`__"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_godot_servers.rst:28
msgid "Adding artificial intelligence."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_godot_servers.rst:29
msgid "Adding custom asynchronous threads."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_godot_servers.rst:30
msgid "Adding support for a new input device."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_godot_servers.rst:31
msgid "Adding writing threads."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_godot_servers.rst:32
msgid "Adding a custom VoIP protocol."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_godot_servers.rst:33
msgid "And more..."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_godot_servers.rst:36
msgid "Creating a Godot server"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_godot_servers.rst:38
msgid ""
"At minimum, a server must have a static instance, a sleep timer, a thread "
"loop, an initialization state and a cleanup procedure."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_godot_servers.rst:270
msgid "Custom managed resource data"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_godot_servers.rst:272
msgid ""
"Godot servers implement a mediator pattern. All data types inherit "
"``RID_Data``. ``RID_Owner<MyRID_Data>`` owns the object when ``make_rid`` is "
"called. During debug mode only, RID_Owner maintains a list of RIDs. In "
"practice, RIDs are similar to writing object-oriented C code."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_godot_servers.rst:314
msgid ":ref:`RID<class_rid>`"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_godot_servers.rst:318
msgid "Registering the class in GDScript"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_godot_servers.rst:320
msgid ""
"Servers are allocated in ``register_types.cpp``. The constructor sets the "
"static instance and ``init()`` creates the managed thread; "
"``unregister_types.cpp`` cleans up the server."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_godot_servers.rst:324
msgid ""
"Since a Godot server class creates an instance and binds it to a static "
"singleton, binding the class might not reference the correct instance. "
"Therefore, a dummy class must be created to reference the proper Godot "
"server."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_godot_servers.rst:328
msgid ""
"In ``register_server_types()``, ``Engine::get_singleton()->add_singleton`` "
"is used to register the dummy class in GDScript."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_godot_servers.rst:372
msgid ""
"`servers/register_server_types.cpp <https://github.com/godotengine/godot/"
"blob/master/servers/register_server_types.cpp>`__"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_godot_servers.rst:375
msgid "Bind methods"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_godot_servers.rst:377
msgid ""
"The dummy class binds singleton methods to GDScript. In most cases, the "
"dummy class methods wraps around."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_godot_servers.rst:385
msgid "Binding Signals"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_godot_servers.rst:387
msgid ""
"It is possible to emit signals to GDScript by calling the GDScript dummy "
"object."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_godot_servers.rst:462
msgid "MessageQueue"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_godot_servers.rst:464
msgid ""
"In order to send commands into SceneTree, MessageQueue is a thread-safe "
"buffer to queue set and call methods for other threads. To queue a command, "
"obtain the target object RID and use either ``push_call``, ``push_set``, or "
"``push_notification`` to execute the desired behavior. The queue will be "
"flushed whenever either ``SceneTree::idle`` or ``SceneTree::iteration`` is "
"executed."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_godot_servers.rst:473
#, fuzzy
msgid ""
"`core/object/message_queue.cpp <https://github.com/godotengine/godot/blob/"
"master/core/object/message_queue.cpp>`__"
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati raznorazne `Godot demo projects "
"<https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/contributing/development/core_and_modules/custom_godot_servers.rst:476
msgid "Summing it up"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_godot_servers.rst:478
msgid "Here is the GDScript sample code:"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_godot_servers.rst:504
msgid ""
"The actual `Hilbert Hotel <https://en.wikipedia.org/wiki/"
"Hilbert%27s_paradox_of_the_Grand_Hotel>`__ is impossible."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_godot_servers.rst:505
msgid "Connecting signal example code is pretty hacky."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_resource_format_loaders.rst:4
msgid "Custom resource format loaders"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_resource_format_loaders.rst:9
msgid ""
"ResourceFormatLoader is a factory interface for loading file assets. "
"Resources are primary containers. When load is called on the same file path "
"again, the previous loaded Resource will be referenced. Naturally, loaded "
"resources must be stateless."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_resource_format_loaders.rst:14
msgid ""
"This guide assumes the reader knows how to create C++ modules and Godot data "
"types. If not, refer to this guide: :ref:`doc_custom_modules_in_cpp`"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_resource_format_loaders.rst:20
msgid ":ref:`ResourceLoader<class_resourceloader>`"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_resource_format_loaders.rst:21
#: ../../docs/contributing/development/core_and_modules/custom_resource_format_loaders.rst:358
msgid ""
"`core/io/resource_loader.cpp <https://github.com/godotengine/godot/blob/"
"master/core/io/resource_loader.cpp>`_"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_resource_format_loaders.rst:26
msgid "Adding new support for many file formats"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_resource_format_loaders.rst:27
msgid "Audio formats"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_resource_format_loaders.rst:28
msgid "Video formats"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_resource_format_loaders.rst:29
msgid "Machine learning models"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_resource_format_loaders.rst:32
msgid "What not?"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_resource_format_loaders.rst:34
msgid "Raster images"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_resource_format_loaders.rst:36
msgid "ImageFormatLoader should be used to load images."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_resource_format_loaders.rst:41
msgid ""
"`core/io/image_loader.h <https://github.com/godotengine/godot/blob/master/"
"core/io/image_loader.h>`_"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_resource_format_loaders.rst:45
msgid "Creating a ResourceFormatLoader"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_resource_format_loaders.rst:47
msgid ""
"Each file format consist of a data container and a ``ResourceFormatLoader``."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_resource_format_loaders.rst:49
msgid ""
"ResourceFormatLoaders are classes which return all the necessary metadata "
"for supporting new extensions in Godot. The class must return the format "
"name and the extension string."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_resource_format_loaders.rst:53
msgid ""
"In addition, ResourceFormatLoaders must convert file paths into resources "
"with the ``load`` function. To load a resource, ``load`` must read and "
"handle data serialization."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_resource_format_loaders.rst:109
#, fuzzy
msgid "Creating a ResourceFormatSaver"
msgstr "Kreiranje Sadržaja"

#: ../../docs/contributing/development/core_and_modules/custom_resource_format_loaders.rst:111
msgid ""
"If you'd like to be able to edit and save a resource, you can implement a "
"``ResourceFormatSaver``:"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_resource_format_loaders.rst:158
msgid "Creating custom data types"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_resource_format_loaders.rst:160
msgid ""
"Godot may not have a proper substitute within its :ref:`doc_core_types` or "
"managed resources. Godot needs a new registered data type to understand "
"additional binary formats such as machine learning models."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_resource_format_loaders.rst:164
msgid "Here is an example of creating a custom datatype:"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_resource_format_loaders.rst:262
msgid "Considerations"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_resource_format_loaders.rst:264
msgid ""
"Some libraries may not define certain common routines such as IO handling. "
"Therefore, Godot call translations are required."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_resource_format_loaders.rst:267
msgid ""
"For example, here is the code for translating ``FileAccess`` calls into "
"``std::istream``."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_resource_format_loaders.rst:305
msgid "`istream <https://cplusplus.com/reference/istream/istream/>`_"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_resource_format_loaders.rst:306
msgid ""
"`streambuf <https://cplusplus.com/reference/streambuf/streambuf/?"
"kw=streambuf>`_"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_resource_format_loaders.rst:307
#, fuzzy
msgid ""
"`core/io/file_access.h <https://github.com/godotengine/godot/blob/master/"
"core/os/file_access.h>`_"
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati raznorazne `Godot demo projects "
"<https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/contributing/development/core_and_modules/custom_resource_format_loaders.rst:310
msgid "Registering the new file format"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_resource_format_loaders.rst:312
msgid ""
"Godot registers ``ResourcesFormatLoader`` with a ``ResourceLoader`` handler. "
"The handler selects the proper loader automatically when ``load`` is called."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_resource_format_loaders.rst:361
msgid "Loading it on GDScript"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_resource_format_loaders.rst:363
msgid ""
"Save a file called ``demo.json`` with the following contents and place it in "
"the project's root folder:"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_resource_format_loaders.rst:379
msgid "Then attach the following script to any node::"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_audiostreams.rst:4
msgid "Custom AudioStreams"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_audiostreams.rst:9
msgid ""
"AudioStream is the base class of all audio emitting objects. "
"AudioStreamPlayer binds onto an AudioStream to emit PCM data into an "
"AudioServer which manages audio drivers."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_audiostreams.rst:13
msgid ""
"All audio resources require two audio based classes: AudioStream and "
"AudioStreamPlayback. As a data container, AudioStream contains the resource "
"and exposes itself to GDScript. AudioStream references its own internal "
"custom AudioStreamPlayback which translates AudioStream into PCM data."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_audiostreams.rst:19
msgid ""
"This guide assumes the reader knows how to create C++ modules. If not, refer "
"to this guide :ref:`doc_custom_modules_in_cpp`."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_audiostreams.rst:25
#: ../../docs/contributing/development/core_and_modules/custom_audiostreams.rst:119
#: ../../docs/contributing/development/core_and_modules/custom_audiostreams.rst:350
msgid ""
"`servers/audio/audio_stream.h <https://github.com/godotengine/godot/blob/"
"master/servers/audio/audio_stream.h>`__"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_audiostreams.rst:26
#: ../../docs/contributing/development/core_and_modules/custom_audiostreams.rst:351
#, fuzzy
msgid ""
"`scene/audio/audio_stream_player.cpp <https://github.com/godotengine/godot/"
"blob/master/scene/audio/audio_stream_player.cpp>`__"
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati raznorazne `Godot demo projects "
"<https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/contributing/development/core_and_modules/custom_audiostreams.rst:31
msgid "Binding external libraries (like Wwise, FMOD, etc)."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_audiostreams.rst:32
msgid "Adding custom audio queues"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_audiostreams.rst:33
msgid "Adding support for more audio formats"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_audiostreams.rst:36
msgid "Create an AudioStream"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_audiostreams.rst:38
msgid ""
"An AudioStream consists of three components: data container, stream name, "
"and an AudioStreamPlayback friend class generator. Audio data can be loaded "
"in a number of ways such as with an internal counter for a tone generator, "
"internal/external buffer, or a file reference."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_audiostreams.rst:43
msgid ""
"Some AudioStreams need to be stateless such as objects loaded from "
"ResourceLoader. ResourceLoader loads once and references the same object "
"regardless how many times ``load`` is called on a specific resource. "
"Therefore, playback state must be self-contained in AudioStreamPlayback."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_audiostreams.rst:123
msgid "Create an AudioStreamPlayback"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_audiostreams.rst:125
msgid ""
"AudioStreamPlayer uses ``mix`` callback to obtain PCM data. The callback "
"must match sample rate and fill the buffer."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_audiostreams.rst:127
msgid ""
"Since AudioStreamPlayback is controlled by the audio thread, i/o and dynamic "
"memory allocation are forbidden."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_audiostreams.rst:232
msgid "Resampling"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_audiostreams.rst:234
msgid ""
"Godot's AudioServer currently uses 44100 Hz sample rate. When other sample "
"rates are needed such as 48000, either provide one or use "
"AudioStreamPlaybackResampled. Godot provides cubic interpolation for audio "
"resampling."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_audiostreams.rst:238
msgid ""
"Instead of overloading ``mix``, AudioStreamPlaybackResampled uses "
"``_mix_internal`` to query AudioFrames and ``get_stream_sampling_rate`` to "
"query current mix rate."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_audiostreams.rst:349
msgid ""
"`core/math/audio_frame.h <https://github.com/godotengine/godot/blob/master/"
"core/math/audio_frame.h>`__"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_platform_ports.rst:4
msgid "Custom platform ports"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_platform_ports.rst:6
msgid ""
"Similar to :ref:`doc_custom_modules_in_cpp`, Godot's multi-platform "
"architecture is designed in a way that allows creating platform ports "
"without modifying any existing source code."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_platform_ports.rst:10
msgid ""
"An example of a custom platform port distributed independently from the "
"engine is `FRT <https://github.com/efornara/frt>`__, which targets single-"
"board computers. Note that this platform port currently targets Godot 3.x; "
"therefore, it does not use the :ref:`class_DisplayServer` abstraction that "
"is new in Godot 4."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_platform_ports.rst:15
msgid "Some reasons to create custom platform ports might be:"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_platform_ports.rst:17
msgid ""
"You want to :ref:`port your game to consoles <doc_consoles>`, but wish to "
"write the platform layer yourself. This is a long and arduous process, as it "
"requires signing NDAs with console manufacturers, but it allows you to have "
"full control over the console porting process."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_platform_ports.rst:21
msgid ""
"You want to port Godot to an exotic platform that isn't currently supported."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_platform_ports.rst:23
msgid ""
"If you have questions about creating a custom platform port, feel free to "
"ask in the ``#platforms`` channel of the `Godot Contributors Chat <https://"
"chat.godotengine.org/channel/platforms>`__."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_platform_ports.rst:29
msgid ""
"Godot is a modern engine with modern requirements. Even if you only intend "
"to run simple 2D projects on the target platform, it still requires an "
"amount of memory that makes it unviable to run on most retro consoles. For "
"reference, in Godot 4, an empty project with nothing visible requires about "
"100 MB of RAM to run on Linux (50 MB in headless mode)."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_platform_ports.rst:35
msgid ""
"If you want to run Godot on heavily memory-constrained platforms, older "
"Godot versions have lower memory requirements. The porting process is "
"similar, with the exception of :ref:`class_DisplayServer` not being split "
"from the :ref:`class_OS` singleton."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_platform_ports.rst:41
#, fuzzy
msgid "Official platform ports"
msgstr "Kreiranje Sadržaja"

#: ../../docs/contributing/development/core_and_modules/custom_platform_ports.rst:43
msgid ""
"The official platform ports can be used as a reference when creating a "
"custom platform port:"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_platform_ports.rst:45
#, fuzzy
msgid ""
"`Windows <https://github.com/godotengine/godot/tree/master/platform/"
"windows>`__"
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati raznorazne `Godot demo projects "
"<https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/contributing/development/core_and_modules/custom_platform_ports.rst:46
#, fuzzy
msgid ""
"`macOS <https://github.com/godotengine/godot/tree/master/platform/macos>`__"
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati raznorazne `Godot demo projects "
"<https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/contributing/development/core_and_modules/custom_platform_ports.rst:47
#, fuzzy
msgid ""
"`Linux/\\*BSD <https://github.com/godotengine/godot/tree/master/platform/"
"linuxbsd>`__"
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati raznorazne `Godot demo projects "
"<https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/contributing/development/core_and_modules/custom_platform_ports.rst:48
#, fuzzy
msgid ""
"`Android <https://github.com/godotengine/godot/tree/master/platform/"
"android>`__"
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati raznorazne `Godot demo projects "
"<https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/contributing/development/core_and_modules/custom_platform_ports.rst:49
#, fuzzy
msgid "`iOS <https://github.com/godotengine/godot/tree/master/platform/ios>`__"
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati raznorazne `Godot demo projects "
"<https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/contributing/development/core_and_modules/custom_platform_ports.rst:50
#, fuzzy
msgid "`Web <https://github.com/godotengine/godot/tree/master/platform/web>`__"
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati raznorazne `Godot demo projects "
"<https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/contributing/development/core_and_modules/custom_platform_ports.rst:52
msgid ""
"While platform code is usually self-contained, there are exceptions to this "
"rule. For instance, audio drivers that are shared across several platforms "
"and rendering backends are located in the `drivers/ folder <https://github."
"com/godotengine/godot/tree/master/drivers>`__ of the Godot source code."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_platform_ports.rst:59
#, fuzzy
msgid "Creating a custom platform port"
msgstr "Kreiranje Sadržaja"

#: ../../docs/contributing/development/core_and_modules/custom_platform_ports.rst:61
msgid ""
"Creating a custom platform port is a large undertaking which requires prior "
"knowledge of the platform's SDKs. Depending on what features you need, the "
"amount of work needed varies:"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_platform_ports.rst:66
msgid "Required features of a platform port"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_platform_ports.rst:68
msgid ""
"At the very least, a platform port must have methods from the :ref:"
"`class_OS` singleton implemented to be buildable and usable for headless "
"operation. A ``logo.svg`` (32×32) vector image must also be present within "
"the platform folder. This logo is displayed in the Export dialog for each "
"export preset targeting the platform in question."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_platform_ports.rst:74
msgid ""
"See `this implementation <https://github.com/godotengine/godot/blob/master/"
"platform/linuxbsd/os_linuxbsd.cpp>`__ for the Linux/\\*BSD platform as an "
"example. See also the `OS singleton header <https://github.com/godotengine/"
"godot/blob/master/core/os/os.h>`__ for reference."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_platform_ports.rst:81
msgid ""
"If your target platform is UNIX-like, consider inheriting from the "
"``OS_Unix`` class to get much of the work done automatically."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_platform_ports.rst:84
msgid ""
"If the platform is not UNIX-like, you might use the `Windows port <https://"
"github.com/godotengine/godot/blob/master/platform/windows/os_windows.cpp>` "
"as a reference."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_platform_ports.rst:88
msgid "**detect.py file**"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_platform_ports.rst:90
msgid ""
"A ``detect.py`` file must be created within the platform's folder with all "
"methods implemented. This file is required for SCons to detect the platform "
"as a valid option for compiling. See the `detect.py file <https://github.com/"
"godotengine/godot/blob/master/platform/linuxbsd/detect.py>`__ for the Linux/"
"\\*BSD platform as an example."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_platform_ports.rst:96
msgid "All methods should be implemented within ``detect.py`` as follows:"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_platform_ports.rst:98
msgid ""
"``is_active()``: Can be used to temporarily disable building for a platform. "
"This should generally always return ``True``."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_platform_ports.rst:100
msgid "``get_name()``: Returns the platform's user-visible name as a string."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_platform_ports.rst:101
msgid ""
"``can_build()``: Return ``True`` if the host system is able to build for the "
"target platform, ``False`` otherwise. Do not put slow checks here, as this "
"is queried when the list of platforms is requested by the user. Use "
"``configure()`` for extensive dependency checks instead."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_platform_ports.rst:105
msgid ""
"``get_opts()``: Returns the list of SCons build options that can be defined "
"by the user for this platform."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_platform_ports.rst:107
msgid ""
"``get_flags()``: Returns the list of overridden SCons flags for this "
"platform."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_platform_ports.rst:108
msgid ""
"``configure()``: Perform build configuration, such as selecting compiler "
"options depending on SCons options chosen."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_platform_ports.rst:112
msgid "Optional features of a platform port"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_platform_ports.rst:114
msgid ""
"In practice, headless operation doesn't suffice if you want to see anything "
"on screen and handle input devices. You may also want audio output for most "
"games."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_platform_ports.rst:118
msgid ""
"*Some links on this list point to the Linux/\\*BSD platform implementation "
"as a reference.*"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_platform_ports.rst:120
msgid ""
"One or more `DisplayServers <https://github.com/godotengine/godot/blob/"
"master/platform/linuxbsd/x11/display_server_x11.cpp>`__, with the windowing "
"methods implemented. DisplayServer also covers features such as mouse "
"support, touchscreen support and tablet driver (for pen input). See the "
"`DisplayServer singleton header <https://github.com/godotengine/godot/blob/"
"master/servers/display_server.h>`__ for reference."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_platform_ports.rst:127
msgid ""
"For platforms not featuring full windowing support (or if it's not relevant "
"for the port you are making), most windowing functions can be left mostly "
"unimplemented. These functions can be made to only check if the window ID is "
"``MAIN_WINDOW_ID`` and specific operations like resizing may be tied to the "
"platform's screen resolution feature (if relevant). Any attempt to create or "
"manipulate other window IDs can be rejected."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_platform_ports.rst:133
msgid ""
"*If the target platform supports the graphics APIs in question:* Rendering "
"context for `Vulkan <https://github.com/godotengine/godot/blob/master/"
"platform/linuxbsd/x11/vulkan_context_x11.cpp>`__, `OpenGL 3.3 or OpenGL ES "
"3.0 <https://github.com/godotengine/godot/blob/master/platform/linuxbsd/x11/"
"gl_manager_x11.cpp>`__."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_platform_ports.rst:136
msgid ""
"Input handlers for `keyboard <https://github.com/godotengine/godot/blob/"
"master/platform/linuxbsd/x11/key_mapping_x11.cpp>`__ and `controller "
"<https://github.com/godotengine/godot/blob/master/platform/linuxbsd/"
"joypad_linux.cpp>`__."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_platform_ports.rst:138
msgid ""
"One or more `audio drivers <https://github.com/godotengine/godot/blob/master/"
"drivers/pulseaudio/audio_driver_pulseaudio.cpp>`__. The audio driver can be "
"located in the ``platform/`` folder (this is done for the Android and Web "
"platforms), or in the ``drivers/`` folder if multiple platforms may be using "
"this audio driver. See the `AudioServer singleton header <https://github.com/"
"godotengine/godot/blob/master/servers/audio_server.h>`__ for reference."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_platform_ports.rst:144
msgid ""
"`Crash handler <https://github.com/godotengine/godot/blob/master/platform/"
"linuxbsd/crash_handler_linuxbsd.cpp>`__, for printing crash backtraces when "
"the game crashes. This allows for easier troubleshooting on platforms where "
"logs aren't readily accessible."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_platform_ports.rst:147
#, fuzzy
msgid ""
"`Text-to-speech driver <https://github.com/godotengine/godot/blob/master/"
"platform/linuxbsd/tts_linux.cpp>`__ (for accessibility)."
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati raznorazne `Godot demo projects "
"<https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/contributing/development/core_and_modules/custom_platform_ports.rst:149
msgid ""
"`Export handler <https://github.com/godotengine/godot/tree/master/platform/"
"linuxbsd/export>`__ (for exporting from the editor, including :ref:`doc_one-"
"click_deploy`). Not required if you intend to export only a PCK from the "
"editor, then run the export template binary directly by renaming it to match "
"the PCK file. See the `EditorExportPlatform header <https://github.com/"
"godotengine/godot/blob/master/editor/export/editor_export_platform.h>`__ for "
"reference. ``run_icon.svg`` (16×16) should be present within the platform "
"folder if :ref:`doc_one-click_deploy` is implemented for the target "
"platform. This icon is displayed at the top of the editor when one-click "
"deploy is set up for the target platform."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_platform_ports.rst:160
msgid ""
"If the target platform doesn't support running Vulkan, OpenGL 3.3 or OpenGL "
"ES 3.0, you have two options:"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_platform_ports.rst:163
msgid ""
"Use a library at run-time to translate Vulkan or OpenGL calls to another "
"graphics API. For example, `MoltenVK <https://moltengl.com/moltenvk/>`__ is "
"used on macOS to translate Vulkan to Metal at run-time."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_platform_ports.rst:166
msgid ""
"Create a new renderer from scratch. This is a large undertaking, especially "
"if you want to support both 2D and 3D rendering with advanced features."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_platform_ports.rst:170
msgid "Distributing a custom platform port"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_platform_ports.rst:174
msgid ""
"Before distributing a custom platform port, make sure you're allowed to "
"distribute all the code that is being linked against. Console SDKs are "
"typically under NDAs which prevent redistribution to the public."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_platform_ports.rst:178
msgid ""
"Platform ports are designed to be as self-contained as possible. Most of the "
"code can be kept within a single folder located in ``platform/``. Like :ref:"
"`doc_custom_modules_in_cpp`, this allows for streamlining the build process "
"by making it possible to ``git clone`` a platform folder within a Godot "
"repository clone's ``platform/`` folder, then run ``scons platform=<name>``. "
"No other steps are necessary for building, unless third-party platform-"
"specific dependencies need to be installed first."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/custom_platform_ports.rst:186
msgid ""
"However, when a custom rendering backend is needed, another folder must be "
"added in ``drivers/``. In this case, the platform port can be distributed as "
"a fork of the Godot repository, or as a collection of several folders that "
"can be added over a Godot Git repository clone."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/unit_testing.rst:4
#, fuzzy
msgid "Unit testing"
msgstr "Kreiranje Sadržaja"

#: ../../docs/contributing/development/core_and_modules/unit_testing.rst:6
msgid ""
"Godot Engine allows to write unit tests directly in C++. The engine "
"integrates the `doctest <https://github.com/onqtam/doctest>`_ unit testing "
"framework which gives ability to write test suites and test cases next to "
"production code, but since the tests in Godot go through a different "
"``main`` entry point, the tests reside in a dedicated ``tests/`` directory "
"instead, which is located at the root of the engine source code."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/unit_testing.rst:14
msgid "Platform and target support"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/unit_testing.rst:16
msgid ""
"C++ unit tests can be run on Linux, macOS, and Windows operating systems."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/unit_testing.rst:18
msgid ""
"Tests can only be run with editor ``tools`` enabled, which means that export "
"templates cannot be tested currently."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/unit_testing.rst:22
#, fuzzy
msgid "Running tests"
msgstr "Kreiranje Sadržaja"

#: ../../docs/contributing/development/core_and_modules/unit_testing.rst:24
msgid ""
"Before tests can be actually run, the engine must be compiled with the "
"``tests`` build option enabled (and any other build option you typically "
"use), as the tests are not compiled as part of the engine by default:"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/unit_testing.rst:32
msgid ""
"Once the build is done, run the tests with a ``--test`` command-line option:"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/unit_testing.rst:38
msgid ""
"The test run can be configured with the various doctest-specific command-"
"line options. To retrieve the full list of supported options, run the ``--"
"test`` command with the ``--help`` option:"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/unit_testing.rst:46
msgid ""
"Any other options and arguments after the ``--test`` command are treated as "
"arguments for doctest."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/unit_testing.rst:51
msgid ""
"Tests are compiled automatically if you use the ``dev_mode=yes`` SCons "
"option. ``dev_mode=yes`` is recommended if you plan on contributing to the "
"engine development as it will automatically treat compilation warnings as "
"errors. The continuous integration system will fail if any compilation "
"warnings are detected, so you should strive to fix all warnings before "
"opening a pull request."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/unit_testing.rst:59
msgid "Filtering tests"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/unit_testing.rst:61
msgid ""
"By default, all tests are run if you don't supply any extra arguments after "
"the ``--test`` command. But if you're writing new tests or would like to see "
"the successful assertions output coming from those tests for debugging "
"purposes, you can run the tests of interest with the various filtering "
"options provided by doctest."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/unit_testing.rst:67
msgid ""
"The wildcard syntax ``*`` is supported for matching any number of characters "
"in test suites, test cases, and source file names:"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/unit_testing.rst:71
msgid "**Filter options**"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/unit_testing.rst:71
msgid "**Shorthand**"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/unit_testing.rst:71
msgid "**Examples**"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/unit_testing.rst:73
msgid "``--test-suite``"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/unit_testing.rst:73
msgid "``-ts``"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/unit_testing.rst:73
msgid "``-ts=\"*[GDScript]*\"``"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/unit_testing.rst:75
msgid "``--test-case``"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/unit_testing.rst:75
msgid "``-tc``"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/unit_testing.rst:75
msgid "``-tc=\"*[String]*\"``"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/unit_testing.rst:77
msgid "``--source-file``"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/unit_testing.rst:77
msgid "``-sf``"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/unit_testing.rst:77
msgid "``-sf=\"*test_color*\"``"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/unit_testing.rst:80
msgid "For instance, to run only the ``String`` unit tests, run:"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/unit_testing.rst:86
msgid ""
"Successful assertions output can be enabled with the ``--success`` (``-s``) "
"option, and can be combined with any combination of filtering options above, "
"for instance:"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/unit_testing.rst:94
msgid ""
"Specific tests can be skipped with corresponding ``-exclude`` options. As of "
"now, some tests include random stress tests which take a while to execute. "
"In order to skip those kind of tests, run the following command:"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/unit_testing.rst:103
#, fuzzy
msgid "Writing tests"
msgstr "Kreiranje Sadržaja"

#: ../../docs/contributing/development/core_and_modules/unit_testing.rst:105
msgid ""
"Test suites represent C++ header files which must be included as part of the "
"main test entry point in ``tests/test_main.cpp``. Most test suites are "
"located directly under ``tests/`` directory."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/unit_testing.rst:109
msgid ""
"All header files are prefixed with ``test_``, and this is a naming "
"convention which the Godot build system relies on to detect tests throughout "
"the engine."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/unit_testing.rst:112
msgid "Here's a minimal working test suite with a single test case written:"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/unit_testing.rst:132
msgid ""
"The ``tests/test_macros.h`` header encapsulates everything which is needed "
"for writing C++ unit tests in Godot. It includes doctest assertion and "
"logging macros such as ``CHECK`` as seen above, and of course the "
"definitions for writing test cases themselves."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/unit_testing.rst:139
msgid ""
"`tests/test_macros.h <https://github.com/godotengine/godot/blob/master/tests/"
"test_macros.h>`_ source code for currently implemented macros and aliases "
"for them."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/unit_testing.rst:142
msgid ""
"Test cases are created using ``TEST_CASE`` function-like macro. Each test "
"case must have a brief description written in parentheses, optionally "
"including custom tags which allow to filter the tests at run-time, such as "
"``[String]``, ``[Stress]`` etc."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/unit_testing.rst:147
msgid ""
"Test cases are written in a dedicated namespace. This is not required, but "
"allows to prevent naming collisions for when other static helper functions "
"are written to accommodate the repeating testing procedures such as "
"populating common test data for each test, or writing parameterized tests."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/unit_testing.rst:152
msgid ""
"Godot supports writing tests per C++ module. For instructions on how to "
"write module tests, refer to :ref:`doc_custom_module_unit_tests`."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/unit_testing.rst:156
#, fuzzy
msgid "Assertions"
msgstr "Uvod"

#: ../../docs/contributing/development/core_and_modules/unit_testing.rst:158
msgid ""
"A list of all commonly used assertions used throughout the Godot tests, "
"sorted by severity."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/unit_testing.rst:162
msgid "**Assertion**"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/unit_testing.rst:164
msgid "``REQUIRE``"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/unit_testing.rst:164
msgid ""
"Test if condition holds true. Fails the entire test immediately if the "
"condition does not hold true."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/unit_testing.rst:166
msgid "``REQUIRE_FALSE``"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/unit_testing.rst:166
msgid ""
"Test if condition does not hold true. Fails the entire test immediately if "
"the condition holds true."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/unit_testing.rst:168
msgid "``CHECK``"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/unit_testing.rst:168
msgid ""
"Test if condition holds true. Marks the test run as failing, but allow to "
"run other assertions."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/unit_testing.rst:170
msgid "``CHECK_FALSE``"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/unit_testing.rst:170
msgid ""
"Test if condition does not hold true. Marks the test run as failing, but "
"allow to run other assertions."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/unit_testing.rst:172
msgid "``WARN``"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/unit_testing.rst:172
msgid ""
"Test if condition holds true. Does not fail the test under any circumstance, "
"but logs a warning if something does not hold true."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/unit_testing.rst:174
msgid "``WARN_FALSE``"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/unit_testing.rst:174
msgid ""
"Test if condition does not hold true. Does not fail the test under any "
"circumstance, but logs a warning if something holds true."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/unit_testing.rst:177
msgid ""
"All of the above assertions have corresponding ``*_MESSAGE`` macros, which "
"allow to print optional message with rationale of what should happen."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/unit_testing.rst:180
msgid ""
"Prefer to use ``CHECK`` for self-explanatory assertions and "
"``CHECK_MESSAGE`` for more complex ones if you think that it deserves a "
"better explanation."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/unit_testing.rst:185
msgid ""
"`doctest: Assertion macros <https://github.com/onqtam/doctest/blob/master/"
"doc/markdown/assertions.md>`_."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/unit_testing.rst:188
msgid "Logging"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/unit_testing.rst:190
msgid ""
"The test output is handled by doctest itself, and does not rely on Godot "
"printing or logging functionality at all, so it's recommended to use "
"dedicated macros which allow to log test output in a format written by "
"doctest."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/unit_testing.rst:195
msgid "**Macro**"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/unit_testing.rst:197
msgid "``MESSAGE``"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/unit_testing.rst:197
msgid "Prints a message."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/unit_testing.rst:199
msgid "``FAIL_CHECK``"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/unit_testing.rst:199
msgid ""
"Marks the test as failing, but continue the execution. Can be wrapped in "
"conditionals for complex checks."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/unit_testing.rst:201
msgid "``FAIL``"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/unit_testing.rst:201
msgid ""
"Fails the test immediately. Can be wrapped in conditionals for complex "
"checks."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/unit_testing.rst:204
msgid ""
"Different reporters can be chosen at run-time. For instance, here's how the "
"output can be redirected to a XML file:"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/unit_testing.rst:213
msgid ""
"`doctest: Logging macros <https://github.com/onqtam/doctest/blob/master/doc/"
"markdown/logging.md>`_."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/unit_testing.rst:216
#, fuzzy
msgid "Testing failure paths"
msgstr "Kreiranje Sadržaja"

#: ../../docs/contributing/development/core_and_modules/unit_testing.rst:218
msgid ""
"Sometimes, it's not always feasible to test for an *expected* result. With "
"the Godot development philosophy of that the engine should not crash and "
"should gracefully recover whenever a non-fatal error occurs, it's important "
"to check that those failure paths are indeed safe to execute without "
"crashing the engine."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/unit_testing.rst:223
msgid ""
"*Unexpected* behavior can be tested in the same way as anything else. The "
"only problem this creates is that the error printing shall unnecessarily "
"pollute the test output with errors coming from the engine itself (even if "
"the end result is successful)."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/unit_testing.rst:228
msgid ""
"To alleviate this problem, use ``ERR_PRINT_OFF`` and ``ERR_PRINT_ON`` macros "
"directly within test cases to temporarily disable the error output coming "
"from the engine, for instance:"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/unit_testing.rst:244
msgid "Test tools"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/unit_testing.rst:246
msgid ""
"Test tools are advanced methods which allow you to run arbitrary procedures "
"to facilitate the process of manual testing and debugging the engine "
"internals."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/unit_testing.rst:249
msgid ""
"These tools can be run by supplying the name of a tool after the ``--test`` "
"command-line option. For instance, the GDScript module implements and "
"registers several tools to help the debugging of the tokenizer, parser, and "
"compiler:"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/unit_testing.rst:259
msgid ""
"If any such tool is detected, then the rest of the unit tests are skipped."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/unit_testing.rst:261
msgid ""
"Test tools can be registered anywhere throughout the engine as the "
"registering mechanism closely resembles of what doctest provides while "
"registering test cases using dynamic initialization technique, but usually "
"these can be registered at corresponding ``register_types.cpp`` sources (per "
"module or core)."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/unit_testing.rst:266
msgid ""
"Here's an example of how GDScript registers test tools in ``modules/gdscript/"
"register_types.cpp``:"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/unit_testing.rst:289
msgid ""
"The custom command-line parsing can be performed by a test tool itself with "
"the help of OS :ref:`get_cmdline_args<class_OS_method_get_cmdline_args>` "
"method."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/unit_testing.rst:293
msgid "Integration tests for GDScript"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/unit_testing.rst:295
msgid ""
"Godot uses doctest to prevent regressions in GDScript during development. "
"There are several types of test scripts which can be written:"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/unit_testing.rst:298
msgid "tests for expected errors;"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/unit_testing.rst:299
msgid "tests for warnings;"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/unit_testing.rst:300
#, fuzzy
msgid "tests for features."
msgstr "Kreiranje Sadržaja"

#: ../../docs/contributing/development/core_and_modules/unit_testing.rst:302
msgid ""
"Therefore, the process of writing integration tests for GDScript is the "
"following:"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/unit_testing.rst:304
msgid ""
"Pick a type of a test script you'd like to write, and create a new GDScript "
"file under the ``modules/gdscript/tests/scripts`` directory within "
"corresponding sub-directory."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/unit_testing.rst:308
msgid ""
"Write GDScript code. The test script must have a function called ``test()`` "
"which takes no arguments. Such function will be called by the test runner. "
"The test should not have any dependency unless it's part of the test too. "
"Global classes (using ``class_name``) are registered before the runner "
"starts, so those should work if needed."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/unit_testing.rst:314
msgid "Here's an example test script:"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/unit_testing.rst:322
msgid "Change directory to the Godot source repository root."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/unit_testing.rst:328
msgid ""
"Generate ``*.out`` files to update the expected results from the output:"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/unit_testing.rst:334
msgid ""
"You may add the ``--print-filenames`` option to see filenames as their test "
"outputs are generated. If you are working on a new feature that is causing "
"hard crashes, you can use this option to quickly find which test file causes "
"the crash and debug from there."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/unit_testing.rst:339
msgid "Run GDScript tests with:"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/unit_testing.rst:345
msgid "This also accepts the ``--print-filenames`` option (see above)."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/unit_testing.rst:347
msgid "If no errors are printed and everything goes well, you're done!"
msgstr ""

#: ../../docs/contributing/development/core_and_modules/unit_testing.rst:351
msgid ""
"Make sure the output does have the expected values before submitting a pull "
"request. If ``--gdscript-generate-tests`` produces ``*.out`` files which are "
"unrelated to newly added tests, you should revert those files back and only "
"commit ``*.out`` files for new tests."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/unit_testing.rst:358
msgid ""
"The GDScript test runner is meant for testing the GDScript implementation, "
"not for testing user scripts nor testing the engine using scripts. We "
"recommend writing new tests for already resolved `issues related to GDScript "
"at GitHub <https://github.com/godotengine/godot/issues?"
"q=is%3Aissue+label%3Atopic%3Agdscript+is%3Aclosed>`_, or writing tests for "
"currently working features."
msgstr ""

#: ../../docs/contributing/development/core_and_modules/unit_testing.rst:366
msgid ""
"If your test case requires that there is no ``test()`` function present "
"inside the script file, you can disable the runtime section of the test by "
"naming the script file so that it matches the pattern ``*.notest.gd``. For "
"example, \"test_empty_file.notest.gd\"."
msgstr ""

#: ../../docs/contributing/development/file_formats/index.rst:2
msgid "Godot file formats"
msgstr ""

#: ../../docs/contributing/development/file_formats/gdscript_grammar.rst:6
msgid "GDScript grammar"
msgstr ""

#: ../../docs/contributing/development/file_formats/gdscript_grammar.rst:8
msgid ""
"This is the formal grammar of GDScript written in `EBNF <https://en."
"wikipedia.org/wiki/Extended_Backus%E2%80%93Naur_form>`_, for reference "
"purposes."
msgstr ""

#: ../../docs/contributing/development/file_formats/gdscript_grammar.rst:11
msgid ""
"This grammar is descriptive only, derived from the reference documentation "
"and current implementation. The GDScript parser is **not** generated from a "
"grammar definition. Inconsistencies here likely mean an error in this "
"grammar, not a bug in GDScript."
msgstr ""

#: ../../docs/contributing/development/file_formats/tscn.rst:4
msgid "TSCN file format"
msgstr ""

#: ../../docs/contributing/development/file_formats/tscn.rst:6
msgid ""
"The TSCN (text scene) file format represents a single scene tree inside "
"Godot. Unlike binary SCN files, TSCN files have the advantage of being "
"mostly human-readable and easy for version control systems to manage."
msgstr ""

#: ../../docs/contributing/development/file_formats/tscn.rst:10
msgid ""
"The ESCN (exported scene) file format is identical to the TSCN file format, "
"but is used to indicate to Godot that the file has been exported from "
"another program and should not be edited by the user from within Godot. "
"Unlike SCN and TSCN files, during import, ESCN files are compiled to binary "
"SCN files stored inside the ``.godot/imported/`` folder. This reduces the "
"data size and speeds up loading, as binary formats are faster to load "
"compared to text-based formats."
msgstr ""

#: ../../docs/contributing/development/file_formats/tscn.rst:18
msgid ""
"To make files more compact, properties equal to the default value are not "
"stored in scene/resource files. It is possible to write them manually, but "
"they will be discarded when saving the file."
msgstr ""

#: ../../docs/contributing/development/file_formats/tscn.rst:22
msgid ""
"For those looking for a complete description, the parsing is handled in the "
"file `resource_format_text.cpp <https://github.com/godotengine/godot/blob/"
"master/scene/resources/resource_format_text.cpp>`_ in the "
"``ResourceFormatLoaderText`` class."
msgstr ""

#: ../../docs/contributing/development/file_formats/tscn.rst:28
msgid ""
"The scene and resource file formats have changed significantly in Godot 4, "
"with the introduction of string-based UIDs to replace incremental integer "
"IDs."
msgstr ""

#: ../../docs/contributing/development/file_formats/tscn.rst:32
msgid ""
"Mesh, skeleton and animation data is also stored differently compared to "
"Godot 3. You can read about some of the changes in this article: `Animation "
"data rework for 4.0 <https://godotengine.org/article/animation-data-"
"redesign-40/>`__"
msgstr ""

#: ../../docs/contributing/development/file_formats/tscn.rst:36
msgid ""
"Scenes and resources saved with Godot 4.x contain ``format=3`` in their "
"header, whereas Godot 3.x uses ``format=2`` instead."
msgstr ""

#: ../../docs/contributing/development/file_formats/tscn.rst:40
msgid "File structure"
msgstr ""

#: ../../docs/contributing/development/file_formats/tscn.rst:42
msgid "There are five main sections inside the TSCN file:"
msgstr ""

#: ../../docs/contributing/development/file_formats/tscn.rst:44
#, fuzzy
msgid "File descriptor"
msgstr "Uvod"

#: ../../docs/contributing/development/file_formats/tscn.rst:45
#: ../../docs/contributing/development/file_formats/tscn.rst:279
msgid "External resources"
msgstr ""

#: ../../docs/contributing/development/file_formats/tscn.rst:46
#: ../../docs/contributing/development/file_formats/tscn.rst:304
msgid "Internal resources"
msgstr ""

#: ../../docs/contributing/development/file_formats/tscn.rst:48
msgid "Connections"
msgstr ""

#: ../../docs/contributing/development/file_formats/tscn.rst:50
msgid ""
"The file descriptor looks like ``[gd_scene load_steps=4 format=3 uid=\"uid://"
"cecaux1sm7mo0\"]`` and should be the first entry in the file. The "
"``load_steps`` parameter is equal to the total amount of resources (internal "
"and external) plus one (for the file itself). If the file has no resources, "
"``load_steps`` is omitted. The engine will still load the file correctly if "
"``load_steps`` is incorrect, but this will affect loading bars and any other "
"piece of code relying on that value."
msgstr ""

#: ../../docs/contributing/development/file_formats/tscn.rst:57
msgid ""
"``uid`` is an unique string-based identifier representing the scene. This is "
"used by the engine to track files that are moved around, even while the "
"editor is closed. Scripts can also load UID-based resources using the "
"``uid://`` path prefix to avoid relying on filesystem paths. This makes it "
"possible to move around a file in the project, but still be able to load it "
"in scripts without having to modify the script. Godot does not use external "
"files to keep track of IDs, which means no central metadata storage location "
"is required within the project. See `this pull request <https://github.com/"
"godotengine/godot/pull/50786>`__ for detailed information."
msgstr ""

#: ../../docs/contributing/development/file_formats/tscn.rst:67
msgid ""
"These sections should appear in order, but it can be hard to distinguish "
"them. The only difference between them is the first element in the heading "
"for all of the items in the section. For example, the heading of all "
"external resources should start with ``[ext_resource ...]``."
msgstr ""

#: ../../docs/contributing/development/file_formats/tscn.rst:72
msgid ""
"A TSCN file may contain single-line comments starting with a semicolon (``;"
"``). However, comments will be discarded when saving the file using the "
"Godot editor. Whitespace within a TSCN file is not significant (except "
"within strings), but extraneous whitespace will be discarded when saving the "
"file."
msgstr ""

#: ../../docs/contributing/development/file_formats/tscn.rst:78
msgid "Entries inside the file"
msgstr ""

#: ../../docs/contributing/development/file_formats/tscn.rst:80
msgid ""
"A heading looks like ``[<resource_type> key1=value1 key2=value2 "
"key3=value3 ...]`` where resource_type is one of:"
msgstr ""

#: ../../docs/contributing/development/file_formats/tscn.rst:84
msgid "``ext_resource``"
msgstr ""

#: ../../docs/contributing/development/file_formats/tscn.rst:85
msgid "``sub_resource``"
msgstr ""

#: ../../docs/contributing/development/file_formats/tscn.rst:86
msgid "``node``"
msgstr ""

#: ../../docs/contributing/development/file_formats/tscn.rst:87
msgid "``connection``"
msgstr ""

#: ../../docs/contributing/development/file_formats/tscn.rst:89
msgid ""
"Below every heading comes zero or more ``key = value`` pairs. The values can "
"be complex datatypes such as Arrays, Transforms, Colors, and so on. For "
"example, a Node3D looks like:"
msgstr ""

#: ../../docs/contributing/development/file_formats/tscn.rst:101
msgid ""
"The scene tree is made up of… nodes! The heading of each node consists of "
"its name, parent and (most of the time) a type. For example: ``[node "
"name=\"PlayerCamera\" type=\"Camera\" parent=\"Player/Head\"]``"
msgstr ""

#: ../../docs/contributing/development/file_formats/tscn.rst:105
msgid "Other valid keywords include:"
msgstr ""

#: ../../docs/contributing/development/file_formats/tscn.rst:107
msgid "``instance``"
msgstr ""

#: ../../docs/contributing/development/file_formats/tscn.rst:108
msgid "``instance_placeholder``"
msgstr ""

#: ../../docs/contributing/development/file_formats/tscn.rst:109
msgid "``owner``"
msgstr ""

#: ../../docs/contributing/development/file_formats/tscn.rst:110
msgid ""
"``index`` (sets the order of appearance in the tree; if absent, inherited "
"nodes will take precedence over plain ones)"
msgstr ""

#: ../../docs/contributing/development/file_formats/tscn.rst:111
msgid "``groups``"
msgstr ""

#: ../../docs/contributing/development/file_formats/tscn.rst:113
msgid ""
"The first node in the file, which is also the scene root, must **not** have "
"a ``parent=\"Path/To/Node\"`` entry in its heading. All scene files should "
"have exactly *one* scene root. If it doesn't, Godot will fail to import the "
"file. The parent path of other nodes should be absolute, but shouldn't "
"contain the scene root's name. If the node is a direct child of the scene "
"root, the path should be ``\".\"``. Here is an example scene tree (but "
"without any node content):"
msgstr ""

#: ../../docs/contributing/development/file_formats/tscn.rst:130
msgid ""
"To make the file structure easier to grasp, you can saving a file with any "
"given node or resource then inspect it yourself in an external editor. You "
"can also make incremental changes in the Godot editor, and keep an external "
"text editor open on the ``.tscn`` or ``.tres`` file with auto-reload enabled "
"to see what changes."
msgstr ""

#: ../../docs/contributing/development/file_formats/tscn.rst:136
msgid ""
"Here is an example of a scene containing a RigidBody3D-based ball with "
"collision, visuals (mesh + light) and a camera parented to the RigidBody3D:"
msgstr ""

#: ../../docs/contributing/development/file_formats/tscn.rst:169
msgid ""
"A tree structure is not enough to represent the whole scene. Godot uses a "
"``NodePath(Path/To/Node)`` structure to refer to another node or attribute "
"of the node anywhere in the scene tree. Paths are relative to the current "
"node, with ``NodePath(\".\")`` pointing to the current node and "
"``NodePath(\"\")`` pointing to no node at all."
msgstr ""

#: ../../docs/contributing/development/file_formats/tscn.rst:175
msgid ""
"For instance, MeshInstance3D uses ``NodePath()`` to point to its skeleton. "
"Likewise, Animation tracks use ``NodePath()`` to point to node properties to "
"animate."
msgstr ""

#: ../../docs/contributing/development/file_formats/tscn.rst:179
msgid ""
"NodePath can also point to a property using a ``:property_name`` suffix, and "
"even point to a specific component for vector, transform and color types. "
"This is used by Animation resources to point to specific properties to "
"animate. For example, ``NodePath(\"MeshInstance3D:scale.x\")`` points to the "
"``x`` component of the ``scale`` Vector3 property in MeshInstance3D."
msgstr ""

#: ../../docs/contributing/development/file_formats/tscn.rst:185
msgid ""
"For example, the ``skeleton`` property in the MeshInstance3D node called "
"``mesh`` points to its parent, ``Armature01``:"
msgstr ""

#: ../../docs/contributing/development/file_formats/tscn.rst:194
msgid "Skeleton3D"
msgstr ""

#: ../../docs/contributing/development/file_formats/tscn.rst:196
msgid ""
"The :ref:`class_Skeleton3D` node inherits the Node3D node, but may alsohave "
"a list of bones described in key-value pairs in the format ``bones/<id>/"
"<attribute> = value``. The bone attributes consist of:"
msgstr ""

#: ../../docs/contributing/development/file_formats/tscn.rst:200
msgid "``position``: Vector3"
msgstr ""

#: ../../docs/contributing/development/file_formats/tscn.rst:201
msgid "``rotation``: Quaternion"
msgstr ""

#: ../../docs/contributing/development/file_formats/tscn.rst:202
msgid "``scale``: Vector3"
msgstr ""

#: ../../docs/contributing/development/file_formats/tscn.rst:204
msgid ""
"These attributes are all optional. For instance, a bone may only define "
"``position`` or ``rotation`` without defining the other properties."
msgstr ""

#: ../../docs/contributing/development/file_formats/tscn.rst:207
msgid "Here's an example of a skeleton node with two bones:"
msgstr ""

#: ../../docs/contributing/development/file_formats/tscn.rst:219
msgid "BoneAttachment3D"
msgstr ""

#: ../../docs/contributing/development/file_formats/tscn.rst:221
msgid ""
"The :ref:`class_BoneAttachment3D` node is an intermediate node to describe "
"some node being parented to a single bone in a Skeleton node. The "
"BoneAttachment has a ``bone_name = \"name of bone\"`` property, as well as a "
"property for the matching bone index."
msgstr ""

#: ../../docs/contributing/development/file_formats/tscn.rst:226
msgid ""
"An example of a :ref:`class_Marker3D` node parented to a bone in Skeleton:"
msgstr ""

#: ../../docs/contributing/development/file_formats/tscn.rst:239
msgid "AnimationPlayer"
msgstr ""

#: ../../docs/contributing/development/file_formats/tscn.rst:241
msgid ""
"The :ref:`class_AnimationPlayer` node works with one or more animation "
"libraries stored in :ref:`class_AnimationLibrary` resources. An animation "
"library is a collection of individual :ref:`class_Animation` resources, "
"whose structure is documented :ref:`here <doc_tscn_animation>`."
msgstr ""

#: ../../docs/contributing/development/file_formats/tscn.rst:246
msgid ""
"This split between animations themselves and animation libraries was done in "
"Godot 4, so that animations can be imported separately from 3D meshes, which "
"is a common workflow in 3D animation software. See the `original pull "
"request <https://github.com/godotengine/godot/pull/59980>`__ for details."
msgstr ""

#: ../../docs/contributing/development/file_formats/tscn.rst:251
msgid ""
"If the library name is empty, then it acts acts the unique source of "
"animations for this AnimationPlayer. This allows using ``<animation_name>`` "
"directly to play animations from script. If you name the library, then you "
"must play it as ``<library_name>/<animation_name>``. This ensures backwards "
"compatibility and keeps the existing workflow if you don't want to use "
"multiple animation libraries."
msgstr ""

#: ../../docs/contributing/development/file_formats/tscn.rst:261
msgid ""
"Resources are components that make up the nodes. For example, a "
"MeshInstance3D node will have an accompanying ArrayMesh resource. The "
"ArrayMesh resource may be either internal or external to the TSCN file."
msgstr ""

#: ../../docs/contributing/development/file_formats/tscn.rst:265
msgid ""
"References to the resources are handled by unique string-based IDs in the "
"resource's heading. This is different from the ``uid`` property, which each "
"external resource also has (but subresources don't)."
msgstr ""

#: ../../docs/contributing/development/file_formats/tscn.rst:269
msgid ""
"External resources and internal resources are referred to with "
"``ExtResource(\"id\")`` and ``SubResource(\"id\")``, respectively. Because "
"there have different methods to refer to internal and external resources, "
"you can have the same ID for both an internal and external resource."
msgstr ""

#: ../../docs/contributing/development/file_formats/tscn.rst:274
msgid ""
"For example, to refer to the resource ``[ext_resource type=\"Material\" "
"uid=\"uid://c4cp0al3ljsjv\" path=\"res://material.tres\" id=\"1_7bt6s\"]``, "
"you would use ``ExtResource(\"1_7bt6s\")``."
msgstr ""

#: ../../docs/contributing/development/file_formats/tscn.rst:281
msgid ""
"External resources are links to resources not contained within the TSCN file "
"itself. An external resource consists of a path, a type, an UID (used to map "
"its filesystem location to an unique identifier) and an ID (used to refer to "
"the resource in the scene file)."
msgstr ""

#: ../../docs/contributing/development/file_formats/tscn.rst:286
msgid ""
"Godot always generates absolute paths relative to the resource directory and "
"thus prefixed with ``res://``, but paths relative to the TSCN file's "
"location are also valid."
msgstr ""

#: ../../docs/contributing/development/file_formats/tscn.rst:290
msgid "Some example external resources are:"
msgstr ""

#: ../../docs/contributing/development/file_formats/tscn.rst:297
msgid ""
"Like TSCN files, a TRES file may contain single-line comments starting with "
"a semicolon (``;``). However, comments will be discarded when saving the "
"resource using the Godot editor. Whitespace within a TRES file is not "
"significant (except within strings), but extraneous whitespace will be "
"discarded when saving the file."
msgstr ""

#: ../../docs/contributing/development/file_formats/tscn.rst:306
msgid ""
"A TSCN file can contain meshes, materials and other data. These are "
"contained in the *internal resources* section of the file. The heading for "
"an internal resource looks similar to those of external resources, except "
"that it doesn't have a path. Internal resources also have ``key=value`` "
"pairs under each heading. For example, a capsule collision shape looks like:"
msgstr ""

#: ../../docs/contributing/development/file_formats/tscn.rst:318
msgid ""
"Some internal resources contain links to other internal resources (such as a "
"mesh having a material). In this case, the referring resource must appear "
"*before* the reference to it. This means that order matters in the file's "
"internal resources section."
msgstr ""

#: ../../docs/contributing/development/file_formats/tscn.rst:326
msgid ""
"An ArrayMesh consists of several surfaces contained in the ``_surfaces`` "
"array (notice the leading underscore). Each surface's data is stored in a "
"dictionary with the following keys:"
msgstr ""

#: ../../docs/contributing/development/file_formats/tscn.rst:330
msgid ""
"``aabb``: The computed axis-aligned bounding box for visibility. ``Mesh."
"PrimitiveType`` Godot enum. ``0`` = points, ``1`` = lines, ``2`` = line "
"strip, ``3`` = triangles (most common), ``4`` = triangle strip."
msgstr ""

#: ../../docs/contributing/development/file_formats/tscn.rst:333
msgid ""
"``attribute_data``: Vertex attribute data, such as normals, tangents, vertex "
"colors, UV1, UV2 and custom vertex data."
msgstr ""

#: ../../docs/contributing/development/file_formats/tscn.rst:335
msgid ""
"``bone_aabbs``: The axis-aligned bounding box of each bone for visibility."
msgstr ""

#: ../../docs/contributing/development/file_formats/tscn.rst:336
msgid "``format``: The surface's buffer format."
msgstr ""

#: ../../docs/contributing/development/file_formats/tscn.rst:337
msgid ""
"``index_count``: The number of indices in the surface. This must match "
"``index_data``'s size."
msgstr ""

#: ../../docs/contributing/development/file_formats/tscn.rst:339
msgid ""
"``index_data``: The index data, which determines which vertices from "
"``vertex_data`` are drawn."
msgstr ""

#: ../../docs/contributing/development/file_formats/tscn.rst:341
msgid ""
"``lods``: Level of detail variations, stored as an array. Each LOD level "
"represents two values in the array. The first value is the percentage of "
"screen space the LOD level is most suited for (edge length); the second "
"value is the list of indices that should be drawn for the given LOD level."
msgstr ""

#: ../../docs/contributing/development/file_formats/tscn.rst:345
msgid "``material``: The material used when drawing the surface."
msgstr ""

#: ../../docs/contributing/development/file_formats/tscn.rst:346
msgid ""
"``name``: The surface's name. This can be used in scripts and is imported "
"from 3D DCCs."
msgstr ""

#: ../../docs/contributing/development/file_formats/tscn.rst:348
msgid "``primitive``: The surface's primitive type, matching the"
msgstr ""

#: ../../docs/contributing/development/file_formats/tscn.rst:349
msgid "``skin_data``: Bone weight data."
msgstr ""

#: ../../docs/contributing/development/file_formats/tscn.rst:350
msgid ""
"``vertex_count``: Number of vertices in the surface. This must match "
"``vertex_data``'s size."
msgstr ""

#: ../../docs/contributing/development/file_formats/tscn.rst:351
msgid "``vertex_data``: The vertex position data."
msgstr ""

#: ../../docs/contributing/development/file_formats/tscn.rst:353
msgid ""
"Here's an example of an ArrayMesh saved to its own ``.tres`` file. Some "
"fields were shortened with ``...`` for brevity:"
msgstr ""

#: ../../docs/contributing/development/file_formats/tscn.rst:385
#, fuzzy
msgid "Each animation has the following properties:"
msgstr "Glavna dokumentacija za sajt je podeljena na sledeća poglavlja:"

#: ../../docs/contributing/development/file_formats/tscn.rst:387
msgid ""
"``length``: The animation's length in seconds. Note that keyframes may be "
"placed outside the ``[0; length]`` interval, but they may have no effect "
"depending on the interpolation mode chosen."
msgstr ""

#: ../../docs/contributing/development/file_formats/tscn.rst:390
msgid ""
"``loop_mode``: ``0`` = no looping, ``1`` = wrap-around looping, ``2`` = "
"clamped looping."
msgstr ""

#: ../../docs/contributing/development/file_formats/tscn.rst:392
msgid ""
"``step``: The step size to use when editing this animation in the editor. "
"This is only used in the editor; it doesn't affect animation playback in any "
"way."
msgstr ""

#: ../../docs/contributing/development/file_formats/tscn.rst:395
msgid ""
"Each track is described by a list of key-value pairs in the format ``tracks/"
"<id>/<attribute>``. Each track includes:"
msgstr ""

#: ../../docs/contributing/development/file_formats/tscn.rst:398
msgid ""
"``type``: The track's type. This defines what kind of properties may be "
"animated by this track, and how it'll be exposed to the user in the editor. "
"Valid types are ``value`` (generic property track), ``position_3d``, "
"``rotation_3d``, ``scale_3d``, ``blend_shape`` (optimized 3D animation "
"tracks), ``method`` (method call tracks), ``bezier`` (Bezier curve tracks), "
"``audio`` (audio playback tracks), ``animation`` (tracks that play other "
"animations)."
msgstr ""

#: ../../docs/contributing/development/file_formats/tscn.rst:405
msgid ""
"``imported``: ``true`` if the track was created from an imported 3D scene, "
"``false`` if it was manually created by the user in the Godot editor or "
"using a script."
msgstr ""

#: ../../docs/contributing/development/file_formats/tscn.rst:408
msgid ""
"``enabled``: ``true`` if the track is effective, ``false`` if it was "
"disabled in the editor."
msgstr ""

#: ../../docs/contributing/development/file_formats/tscn.rst:410
msgid ""
"``path``: Path to the node property that will be affected by the track. The "
"property is written after the node path with a ``:`` separator."
msgstr ""

#: ../../docs/contributing/development/file_formats/tscn.rst:412
msgid ""
"``interp``: The interpolation mode to use. ``0`` = nearest, ``1`` = linear, "
"``2`` = cubic, ``3`` = linear angle, ``4`` = cubic angle."
msgstr ""

#: ../../docs/contributing/development/file_formats/tscn.rst:414
msgid ""
"``loop_wrap``: ``true`` if the track is designed to wrap around when the "
"animation is looping, ``false`` if the track clamps to the first/last "
"keyframes."
msgstr ""

#: ../../docs/contributing/development/file_formats/tscn.rst:417
msgid ""
"``keys``: The animation track's values. This attribute's structure depends "
"on the ``type``."
msgstr ""

#: ../../docs/contributing/development/file_formats/tscn.rst:419
msgid ""
"Here is a scene containing an AnimationPlayer that scales down a cube over "
"time using a generic property track. The AnimationLibrary workflow was not "
"used, so the animation library has an empty name (but the animation is still "
"given a ``scale_down`` name). Note that the ``RESET`` track was not created "
"in this AnimationPlayer for brevity:"
msgstr ""

#: ../../docs/contributing/development/file_formats/tscn.rst:465
msgid ""
"For generic property ``value`` tracks, ``keys`` is a dictionary containing 3 "
"arrays with positions in ``times`` (PackedFloat32Array), easing values in "
"``transitions`` (PackedFloat32Array) and values in ``values`` (Array). There "
"is an additional ``update`` property, which is an integer with the values "
"``0`` = continuous, ``1`` = discrete, ``2`` = capture."
msgstr ""

#: ../../docs/contributing/development/file_formats/tscn.rst:471
msgid ""
"Here is a second Animation resource that makes use of the 3D Position and 3D "
"Rotation tracks. These tracks (in addition to the 3D Scale track) replace "
"Transform tracks from Godot 3. They are optimized for fast playback and can "
"optionally be compressed."
msgstr ""

#: ../../docs/contributing/development/file_formats/tscn.rst:476
msgid ""
"The downside of these optimized track types is that they can't use custom "
"easing values. Instead, all keyframes use linear interpolation. That said, "
"you can still opt for using nearest or cubic interpolation for all keyframes "
"in a given track by changing the track's interpolation mode."
msgstr ""

#: ../../docs/contributing/development/file_formats/tscn.rst:503
msgid ""
"For 3D position, rotation and scale tracks, ``keys`` is a PackedFloat32Array "
"with all values stored in a sequence."
msgstr ""

#: ../../docs/contributing/development/file_formats/tscn.rst:506
msgid ""
"In the visual guide below, ``T`` is the keyframe's time in seconds since the "
"start of the animation, ``E`` is the keyframe's transition (currently always "
"``1``). For 3D position and scale tracks, ``X``, ``Y``, ``Z`` are the "
"Vector3's coordinates. For 3D rotation tracks, ``X``, ``Y``, ``Z`` and ``W`` "
"are the Quaternion's coordinates."
msgstr ""

#: ../../docs/contributing/development/editor/index.rst:2
#, fuzzy
msgid "Editor development"
msgstr "Razvoj"

#: ../../docs/contributing/development/editor/introduction_to_editor_development.rst:4
#, fuzzy
msgid "Introduction to editor development"
msgstr "Uvod"

#: ../../docs/contributing/development/editor/introduction_to_editor_development.rst:6
msgid "On this page, you will learn:"
msgstr ""

#: ../../docs/contributing/development/editor/introduction_to_editor_development.rst:8
msgid "The **design decisions** behind the Godot editor."
msgstr ""

#: ../../docs/contributing/development/editor/introduction_to_editor_development.rst:9
msgid "How to work efficiently on the Godot editor's C++ code."
msgstr ""

#: ../../docs/contributing/development/editor/introduction_to_editor_development.rst:11
msgid ""
"This guide is aimed at current or future engine contributors. To create "
"editor plugins in GDScript, see :ref:`doc_making_plugins` instead."
msgstr ""

#: ../../docs/contributing/development/editor/introduction_to_editor_development.rst:16
msgid ""
"If you are new to Godot, we recommended you to read :ref:"
"`doc_godot_design_philosophy` before continuing. Since the Godot editor is a "
"Godot project written in C++, much of the engine's philosophy applies to the "
"editor."
msgstr ""

#: ../../docs/contributing/development/editor/introduction_to_editor_development.rst:22
msgid "Technical choices"
msgstr ""

#: ../../docs/contributing/development/editor/introduction_to_editor_development.rst:24
msgid ""
"The Godot editor is drawn using Godot's renderer and :ref:`UI system "
"<doc_user_interface>`. It does *not* rely on a toolkit such as GTK or Qt. "
"This is similar in spirit to software like Blender. While using toolkits "
"makes it easier to achieve a \"native\" appearance, they are also quite "
"heavy and their licensing is not compatible with Godot's."
msgstr ""

#: ../../docs/contributing/development/editor/introduction_to_editor_development.rst:30
msgid ""
"The editor is fully written in C++. It can't contain any GDScript or C# code."
msgstr ""

#: ../../docs/contributing/development/editor/introduction_to_editor_development.rst:33
msgid "Directory structure"
msgstr ""

#: ../../docs/contributing/development/editor/introduction_to_editor_development.rst:35
msgid ""
"The editor's code is fully self-contained in the `editor/ <https://github."
"com/godotengine/godot/tree/master/editor>`__ folder of the Godot source "
"repository."
msgstr ""

#: ../../docs/contributing/development/editor/introduction_to_editor_development.rst:39
msgid ""
"Some editor functionality is also implemented via :ref:`modules "
"<doc_custom_modules_in_cpp>`. Some of these are only enabled in editor "
"builds to decrease the binary size of export templates. See the `modules/ "
"<https://github.com/godotengine/godot/tree/master/modules>`__ folder in the "
"Godot source repository."
msgstr ""

#: ../../docs/contributing/development/editor/introduction_to_editor_development.rst:45
msgid "Some important files in the editor are:"
msgstr ""

#: ../../docs/contributing/development/editor/introduction_to_editor_development.rst:47
msgid ""
"`editor/editor_node.cpp <https://github.com/godotengine/godot/blob/master/"
"editor/editor_node.cpp>`__: Main editor initialization file. Effectively the "
"\"main scene\" of the editor."
msgstr ""

#: ../../docs/contributing/development/editor/introduction_to_editor_development.rst:49
msgid ""
"`editor/project_manager.cpp <https://github.com/godotengine/godot/blob/"
"master/editor/project_manager.cpp>`__: Main Project Manager initialization "
"file. Effectively the \"main scene\" of the Project Manager."
msgstr ""

#: ../../docs/contributing/development/editor/introduction_to_editor_development.rst:51
msgid ""
"`editor/plugins/canvas_item_editor_plugin.cpp <https://github.com/"
"godotengine/godot/blob/master/editor/plugins/canvas_item_editor_plugin."
"cpp>`__: The 2D editor viewport and related functionality (toolbar at the "
"top, editing modes, overlaid helpers/panels, …)."
msgstr ""

#: ../../docs/contributing/development/editor/introduction_to_editor_development.rst:53
msgid ""
"`editor/plugins/node_3d_editor_plugin.cpp <https://github.com/godotengine/"
"godot/blob/master/editor/plugins/node_3d_editor_plugin.cpp>`__: The 3D "
"editor viewport and related functionality (toolbar at the top, editing "
"modes, overlaid panels, …)."
msgstr ""

#: ../../docs/contributing/development/editor/introduction_to_editor_development.rst:55
msgid ""
"`editor/plugins/node_3d_editor_gizmos.cpp <https://github.com/godotengine/"
"godot/blob/master/editor/plugins/node_3d_editor_gizmos.cpp>`__: Where the 3D "
"editor gizmos are defined and drawn. This file doesn't have a 2D counterpart "
"as 2D gizmos are drawn by the nodes themselves."
msgstr ""

#: ../../docs/contributing/development/editor/introduction_to_editor_development.rst:60
msgid "Editor dependencies in ``scene/`` files"
msgstr ""

#: ../../docs/contributing/development/editor/introduction_to_editor_development.rst:62
msgid ""
"When working on an editor feature, you may have to modify files in Godot's "
"GUI nodes, which you can find in the ``scene/`` folder."
msgstr ""

#: ../../docs/contributing/development/editor/introduction_to_editor_development.rst:65
msgid ""
"One rule to keep in mind is that you must **not** introduce new dependencies "
"to ``editor/`` includes in other folders such as ``scene/``. This applies "
"even if you use ``#ifdef TOOLS_ENABLED``."
msgstr ""

#: ../../docs/contributing/development/editor/introduction_to_editor_development.rst:69
msgid ""
"To make the codebase easier to follow and more self-contained, the allowed "
"dependency order is:"
msgstr ""

#: ../../docs/contributing/development/editor/introduction_to_editor_development.rst:72
msgid "``editor/`` -> ``scene/`` -> ``servers/`` -> ``core/``"
msgstr ""

#: ../../docs/contributing/development/editor/introduction_to_editor_development.rst:74
msgid ""
"This means that files in ``editor/`` can depend on includes from ``scene/``, "
"``servers/``, and ``core/``. But, for example, while ``scene/`` can depend "
"on includes from ``servers/`` and ``core/``, it cannot depend on includes "
"from ``editor/``."
msgstr ""

#: ../../docs/contributing/development/editor/introduction_to_editor_development.rst:78
msgid ""
"Currently, there are some dependencies to ``editor/`` includes in ``scene/`` "
"files, but `they are in the process of being removed <https://github.com/"
"godotengine/godot/issues/53295>`__."
msgstr ""

#: ../../docs/contributing/development/editor/introduction_to_editor_development.rst:83
#, fuzzy
msgid "Development tips"
msgstr "Razvoj"

#: ../../docs/contributing/development/editor/introduction_to_editor_development.rst:85
msgid ""
"To iterate quickly on the editor, we recommend to set up a test project and :"
"ref:`open it from the command line <doc_command_line_tutorial>` after "
"compiling the editor. This way, you don't have to go through the Project "
"Manager every time you start Godot."
msgstr ""

#: ../../docs/contributing/development/editor/creating_icons.rst:4
msgid "Editor icons"
msgstr ""

#: ../../docs/contributing/development/editor/creating_icons.rst:6
msgid ""
"When a new class is created and exposed to scripting, the editor's interface "
"will display it with a default icon representing the base class it inherits "
"from. In most cases, it's still recommended to create icons for new classes "
"to improve the user experience."
msgstr ""

#: ../../docs/contributing/development/editor/creating_icons.rst:12
#, fuzzy
msgid "Creating icons"
msgstr "Kreiranje Sadržaja"

#: ../../docs/contributing/development/editor/creating_icons.rst:14
msgid ""
"To create new icons, you first need a vector graphics editor installed. For "
"instance, you can use the open source `Inkscape <https://inkscape.org/>`_ "
"editor."
msgstr ""

#: ../../docs/contributing/development/editor/creating_icons.rst:17
msgid "Clone the ``godot`` repository containing all the editor icons:"
msgstr ""

#: ../../docs/contributing/development/editor/creating_icons.rst:23
msgid ""
"The icons must be created in a vector graphics editor in SVG format. There "
"are two main requirements to follow:"
msgstr ""

#: ../../docs/contributing/development/editor/creating_icons.rst:26
msgid ""
"Icons must be 16×16. In Inkscape, you can configure the document size in "
"**File > Document Properties**."
msgstr ""

#: ../../docs/contributing/development/editor/creating_icons.rst:28
msgid ""
"Lines should be snapped to pixels whenever possible to remain crisp at lower "
"DPI. You can create a 16×16 grid in Inkscape to make this easier."
msgstr ""

#: ../../docs/contributing/development/editor/creating_icons.rst:31
msgid ""
"Once you're satisfied with the icon's design, save the icon in the cloned "
"repository's ``editor/icons`` folder. The icon name should match the "
"intended name in a case-sensitive manner. For example, to create an icon for "
"CPUParticles2D, name the file ``CPUParticles2D.svg``."
msgstr ""

#: ../../docs/contributing/development/editor/creating_icons.rst:37
msgid "Color conversion for light editor themes"
msgstr ""

#: ../../docs/contributing/development/editor/creating_icons.rst:39
msgid ""
"If the user has configured their editor to use a light theme, Godot will "
"convert the icon's colors based on a `set of predefined color mappings "
"<https://github.com/godotengine/godot/blob/4.0.2-stable/editor/editor_themes."
"cpp#L60-L160>`__. This is to ensure the icon always displays with a "
"sufficient contrast rate. Try to restrict your icon's color palette to "
"colors found in the list above. Otherwise, your icon may become difficult to "
"read on a light background."
msgstr ""

#: ../../docs/contributing/development/editor/creating_icons.rst:47
msgid "Icon optimization"
msgstr ""

#: ../../docs/contributing/development/editor/creating_icons.rst:49
msgid ""
"Because the editor renders SVGs once at load time, they need to be small in "
"size so they can be efficiently parsed. Editor icons must be first optimized "
"before being added to the engine, to do so:"
msgstr ""

#: ../../docs/contributing/development/editor/creating_icons.rst:53
msgid ""
"Install `svgcleaner <https://github.com/RazrFalcon/svgcleaner>`__ by "
"downloading a binary from its `Releases tab <https://github.com/RazrFalcon/"
"svgcleaner/releases/latest>`__ and placing it into a location in your "
"``PATH`` environment variable."
msgstr ""

#: ../../docs/contributing/development/editor/creating_icons.rst:58
msgid ""
"Run the command below, replacing ``svg_source.svg`` with the path to your "
"SVG file (which can be a relative or absolute path):"
msgstr ""

#: ../../docs/contributing/development/editor/creating_icons.rst:65
msgid ""
"The ``--multipass`` switch improves compression, so make sure to include it. "
"The optimized icon will be saved to ``svg_optimized.svg``. You can also "
"change the destination parameter to any relative or absolute path you'd like."
msgstr ""

#: ../../docs/contributing/development/editor/creating_icons.rst:71
msgid ""
"While this optimization step won't impact the icon's quality noticeably, it "
"will still remove editor-only information such as guides. Therefore, it's "
"recommended to keep the source SVG around if you need to make further "
"changes."
msgstr ""

#: ../../docs/contributing/development/editor/creating_icons.rst:77
msgid "Integrating and sharing the icons"
msgstr ""

#: ../../docs/contributing/development/editor/creating_icons.rst:79
msgid ""
"If you're contributing to the engine itself, you should make a pull request "
"to add optimized icons to ``editor/icons`` in the main repository. Recompile "
"the engine to make it pick up new icons for classes."
msgstr ""

#: ../../docs/contributing/development/editor/creating_icons.rst:83
msgid ""
"It's also possible to create custom icons within a module. If you're "
"creating your own module and don't plan to integrate it with Godot, you "
"don't need to make a separate pull request for your icons to be available "
"within the editor as they can be self-contained."
msgstr ""

#: ../../docs/contributing/development/editor/creating_icons.rst:88
msgid ""
"For specific instructions on how to create module icons, refer to :ref:"
"`Creating custom module icons<doc_custom_module_icons>`."
msgstr ""

#: ../../docs/contributing/development/editor/creating_icons.rst:94
msgid "If icons don't appear in the editor, make sure that:"
msgstr ""

#: ../../docs/contributing/development/editor/creating_icons.rst:96
msgid ""
"Each icon's filename matches the naming requirement as described previously."
msgstr ""

#: ../../docs/contributing/development/editor/creating_icons.rst:98
msgid ""
"``modules/svg`` is enabled (it should be enabled by default). Without it, "
"icons won't appear in the editor at all."
msgstr ""

#: ../../docs/contributing/development/editor/creating_icons.rst:104
msgid ""
"`editor/icons <https://github.com/godotengine/godot/tree/master/editor/"
"icons>`__"
msgstr ""

#: ../../docs/contributing/development/editor/editor_style_guide.rst:4
#, fuzzy
msgid "Editor style guide"
msgstr "Kreiranje Sadržaja"

#: ../../docs/contributing/development/editor/editor_style_guide.rst:9
msgid "Thanks for your interest in contributing to the Godot editor!"
msgstr ""

#: ../../docs/contributing/development/editor/editor_style_guide.rst:11
msgid ""
"This page describes the grammar and writing style used throughout the Godot "
"editor. Following this style guide will help your contribution get merged "
"faster since there will be fewer review steps required."
msgstr ""

#: ../../docs/contributing/development/editor/editor_style_guide.rst:16
#, fuzzy
msgid "Writing style"
msgstr "Kreiranje Sadržaja"

#: ../../docs/contributing/development/editor/editor_style_guide.rst:18
msgid ""
"**Write messages (errors, warnings, ...) as full sentences.** They should "
"start with an uppercase letter and end with a period."
msgstr ""

#: ../../docs/contributing/development/editor/editor_style_guide.rst:20
msgid ""
"**Try to keep sentences short.** This makes it more likely that their "
"translations will be short as well, which is a good thing to avoid UI bugs."
msgstr ""

#: ../../docs/contributing/development/editor/editor_style_guide.rst:22
msgid ""
"**Use contractions.** For example, use \"isn't\" instead of \"is not\". An "
"exception to this rule can be made when you specifically want to emphasize "
"one of the contraction's words."
msgstr ""

#: ../../docs/contributing/development/editor/editor_style_guide.rst:25
msgid ""
"**Use double quotes in messages** (``\"\"``) instead of single quotes "
"(``''``). Double quotes should be used to quote user input, file paths and "
"possibly other things depending on the context."
msgstr ""

#: ../../docs/contributing/development/editor/editor_style_guide.rst:31
msgid ""
"Try to follow the :ref:`doc_docs_writing_guidelines` in addition to the "
"guidelines outlined above."
msgstr ""

#: ../../docs/contributing/development/editor/editor_style_guide.rst:35
msgid "Button and menu texts"
msgstr ""

#: ../../docs/contributing/development/editor/editor_style_guide.rst:37
msgid "Capitalize text in buttons and menu actions:"
msgstr ""

#: ../../docs/contributing/development/editor/editor_style_guide.rst:39
msgid "**Good:** *Open Editor Data Folder*"
msgstr ""

#: ../../docs/contributing/development/editor/editor_style_guide.rst:40
msgid "**Bad:** *Open editor data folder*"
msgstr ""

#: ../../docs/contributing/development/editor/editor_style_guide.rst:42
msgid ""
"If a menu action opens a modal dialog, suffix it with an ellipsis (``...``)."
msgstr ""

#: ../../docs/contributing/development/editor/editor_style_guide.rst:44
msgid "**Good:** *Editor Settings...*"
msgstr ""

#: ../../docs/contributing/development/editor/editor_style_guide.rst:45
#, fuzzy
msgid "**Bad:** *Editor Settings*"
msgstr "Kreiranje Sadržaja"

#: ../../docs/contributing/development/editor/editor_style_guide.rst:48
#, fuzzy
msgid "Inspector sections"
msgstr "Kreiranje Sadržaja"

#: ../../docs/contributing/development/editor/editor_style_guide.rst:50
msgid ""
"In general, don't create sections that contain less than 3 items. Sections "
"that contain few items make it difficult to navigate the inspector, while "
"missing the benefits of using sections such as folding."
msgstr ""

#: ../../docs/contributing/development/editor/editor_style_guide.rst:54
msgid ""
"There are some valid exceptions for this, such as material features in :ref:"
"`class_StandardMaterial3D`."
msgstr ""

#: ../../docs/contributing/development/editor/editor_style_guide.rst:57
msgid "This advice also applies to the Project Settings and Editor Settings."
msgstr ""

#: ../../docs/contributing/development/editor/editor_style_guide.rst:60
#, fuzzy
msgid "Inspector performance hints"
msgstr "Kreiranje Sadržaja"

#: ../../docs/contributing/development/editor/editor_style_guide.rst:62
msgid ""
"Enum properties that noticeably impact performance should have a performance "
"hint associated. The hint should refer to the *absolute* performance impact, "
"rather than being relative to the other options provided in the enum. Here "
"are some examples taken from the Godot editor:"
msgstr ""

#: ../../docs/contributing/development/editor/editor_style_guide.rst:67
msgid "**Screen-space antialiasing:** *Disabled (Fastest), FXAA (Fast)*"
msgstr ""

#: ../../docs/contributing/development/editor/editor_style_guide.rst:68
msgid ""
"**MSAA quality:** *Disabled (Fastest), 2x (Fast), 4x (Average), 8x (Slow), "
"16x (Slower)*"
msgstr ""

#: ../../docs/contributing/development/editor/editor_style_guide.rst:70
msgid ""
"**DirectionalLight mode:** *Orthogonal (Fast), PSSM 2 Splits (Average), PSSM "
"4 Splits (Slow)*"
msgstr ""

#: ../../docs/contributing/development/editor/editor_style_guide.rst:73
msgid ""
"For consistency, try to stick to the terms below (from fastest to slowest):"
msgstr ""

#: ../../docs/contributing/development/editor/editor_style_guide.rst:75
msgid "*Fastest, Faster, Fast, Average, Slow, Slower, Slowest*"
msgstr ""

#: ../../docs/contributing/development/editor/editor_style_guide.rst:77
msgid ""
"Their usage doesn't have to be contiguous. For example, you can use only "
"\"Fast\" and \"Slow\" from the list above."
msgstr ""

#: ../../docs/contributing/development/editor/editor_style_guide.rst:80
msgid ""
"If you're adding a new enum, its values should be ordered from the fastest "
"option to the slowest option."
msgstr ""

#: ../../docs/contributing/development/editor/editor_style_guide.rst:84
msgid "Tooltips"
msgstr ""

#: ../../docs/contributing/development/editor/editor_style_guide.rst:86
msgid ""
"Consider adding tooltips whenever the action performed by a button or menu "
"action isn't obvious. You can also provide additional context or highlight "
"caveats in the tooltip."
msgstr ""

#: ../../docs/contributing/development/editor/editor_style_guide.rst:90
msgid ""
"You can do this by calling ``set_tooltip(TTR(\"Text here.\"))`` on the "
"Control-based node in question. If the tooltip is particularly long (more "
"than ~80 characters), wrap it over several lines by adding line breaks using "
"``\\n``."
msgstr ""

#: ../../docs/contributing/development/editor/editor_style_guide.rst:94
msgid ""
"Tooltips should follow the writing style described above. In addition to "
"this, use indicative mood instead of imperative mood:"
msgstr ""

#: ../../docs/contributing/development/editor/editor_style_guide.rst:97
msgid "**Good:** *Computes global illumination for the selected GIProbe.*"
msgstr ""

#: ../../docs/contributing/development/editor/editor_style_guide.rst:98
msgid "**Bad:** *Compute global illumination for the selected GIProbe.*"
msgstr ""

#: ../../docs/contributing/documentation/index.rst:4
#, fuzzy
msgid "Writing documentation"
msgstr "Organizacija dokumentacije"

#: ../../docs/contributing/documentation/index.rst:6
msgid ""
"We always need help to improve the documentation, be it the class reference "
"or the manual. Below, you can find our content and writing guidelines and "
"concrete guides to make changes to the documentation."
msgstr ""

#: ../../docs/contributing/documentation/index.rst:14
msgid "Guidelines"
msgstr ""

#: ../../docs/contributing/documentation/index.rst:16
msgid ""
"Here are the principles and guidelines we strive to follow to write "
"accessible documentation."
msgstr ""

#: ../../docs/contributing/documentation/index.rst:28
#, fuzzy
msgid "Writing the manual"
msgstr "Kreiranje Sadržaja"

#: ../../docs/contributing/documentation/index.rst:30
msgid ""
"These articles explain how to contribute to this very documentation, and how "
"to build the online version locally for testing."
msgstr ""

#: ../../docs/contributing/documentation/index.rst:41
msgid "Class reference guides"
msgstr ""

#: ../../docs/contributing/documentation/index.rst:43
msgid "The pages below focus on the class reference."
msgstr ""

#: ../../docs/contributing/documentation/index.rst:45
msgid ""
"As the reference is included in the Godot editor, its source files are part "
"of the `godot repository <https://github.com/godotengine/godot>`_. We use "
"XML files to write it, so the process to contribute to the class reference "
"differs from writing the online manual."
msgstr ""

#: ../../docs/contributing/documentation/index.rst:58
#, fuzzy
msgid "Translating the documentation"
msgstr "Organizacija dokumentacije"

#: ../../docs/contributing/documentation/index.rst:60
msgid ""
"The community is always working hard on making Godot and its documentation "
"available to more people. Localizing the documentation is a colossal and "
"ongoing effort you can be part of."
msgstr ""

#: ../../docs/contributing/documentation/content_guidelines.rst:4
msgid "Content guidelines"
msgstr ""

#: ../../docs/contributing/documentation/content_guidelines.rst:6
msgid ""
"This document outlines what should be included in the official "
"documentation. Below, you will find a couple of principles and "
"recommendations for writing accessible content."
msgstr ""

#: ../../docs/contributing/documentation/content_guidelines.rst:10
msgid "We want to achieve two goals:"
msgstr ""

#: ../../docs/contributing/documentation/content_guidelines.rst:12
msgid ""
"**Empathize with our users.** We should write in a way that makes it easy "
"for them to learn from the docs."
msgstr ""

#: ../../docs/contributing/documentation/content_guidelines.rst:14
msgid ""
"**Write a complete reference manual**. Our goal here is not to teach "
"programming fundamentals. Instead, our goal is to provide a reference for "
"how Godot's features work."
msgstr ""

#: ../../docs/contributing/documentation/content_guidelines.rst:19
msgid "Guidelines and principles"
msgstr ""

#: ../../docs/contributing/documentation/content_guidelines.rst:21
msgid ""
"Below are the guidelines we should strive to follow. They are not hard "
"rules, though: sometimes, a topic will require breaking one or more of them. "
"Still, we should strive to achieve the two goals listed above."
msgstr ""

#: ../../docs/contributing/documentation/content_guidelines.rst:26
msgid "Writing complete and accessible documentation"
msgstr ""

#: ../../docs/contributing/documentation/content_guidelines.rst:28
msgid ""
"**A feature doesn't exist unless it is documented**. If a user can't find "
"information about a feature and how it works, it doesn't exist to them. We "
"should ensure that we cover everything Godot does."
msgstr ""

#: ../../docs/contributing/documentation/content_guidelines.rst:34
msgid ""
"When adding or updating an engine feature, the documentation team needs to "
"know about it. Contributors should open an issue on the `godot-docs` "
"repository when their work gets merged and requires documentation."
msgstr ""

#: ../../docs/contributing/documentation/content_guidelines.rst:38
msgid ""
"Do your best to keep documents **under 1000 words in length**. If a page "
"goes past that threshold, consider splitting it into two parts. Limiting "
"page size forces us to write concisely and to break up large documents so "
"that each page focuses on a particular problem."
msgstr ""

#: ../../docs/contributing/documentation/content_guidelines.rst:43
msgid ""
"Each page or section of a page should clearly state what **problem** it "
"tackles and what it will teach the user. Users need to know if they're "
"reading the correct guide for solving the problems they're encountering. For "
"example, instead of writing the heading \"Signals\", consider writing "
"\"Reacting to changes with signals\". The second title makes it clear what "
"the purpose of signals is."
msgstr ""

#: ../../docs/contributing/documentation/content_guidelines.rst:51
msgid ""
"Long section titles lead to long entries in the side menu, which can make "
"navigation cumbersome. Try to keep headings five words long or less."
msgstr ""

#: ../../docs/contributing/documentation/content_guidelines.rst:54
msgid ""
"If the page assumes specific knowledge of other Godot features, mention it "
"and link to the corresponding documentation. For instance, a page about "
"physics may use signals, in which case you could note that the signals "
"tutorial is a prerequisite. You may also link to other websites for "
"prerequisites beyond the documentation's scope. For example, you could link "
"to an introduction to programming in the getting started guide, or a website "
"that teaches math theory in the math section."
msgstr ""

#: ../../docs/contributing/documentation/content_guidelines.rst:63
msgid "Limiting cognitive load"
msgstr ""

#: ../../docs/contributing/documentation/content_guidelines.rst:65
msgid ""
"Limit the cognitive load required to read the documentation. The simpler and "
"more explicit language we use, the more efficient it becomes for people to "
"learn. You can do so by:"
msgstr ""

#: ../../docs/contributing/documentation/content_guidelines.rst:69
msgid "Introducing only one new concept at a time whenever possible."
msgstr ""

#: ../../docs/contributing/documentation/content_guidelines.rst:70
msgid "Using simple English, as we recommend in our writing guidelines."
msgstr ""

#: ../../docs/contributing/documentation/content_guidelines.rst:71
msgid ""
"Including one or more **concrete usage examples**. Prefer a real-world "
"example to one that uses names like ``foo``, ``bar``, or ``baz``."
msgstr ""

#: ../../docs/contributing/documentation/content_guidelines.rst:74
msgid ""
"While many people may understand more complex language and abstract "
"examples, you will lose others. Understandable writing and practical "
"examples benefit everyone."
msgstr ""

#: ../../docs/contributing/documentation/content_guidelines.rst:78
msgid ""
"Always make an effort to **put yourself in the user's shoes**. When we "
"understand something thoroughly, it becomes obvious to us. We may fail to "
"think about details relevant to a newcomer, but **good documentation meets "
"users where they are**. We should explain each feature's capabilities or "
"intended uses with the most straightforward language possible."
msgstr ""

#: ../../docs/contributing/documentation/content_guidelines.rst:84
msgid ""
"Try to remember what you first needed to know when learning about the "
"feature or concept. What new terms did you need to learn? What confused you? "
"What was the hardest to grasp? You will want users to review your work, and "
"we recommend you practice explaining the feature before writing about it."
msgstr ""

#: ../../docs/contributing/documentation/content_guidelines.rst:91
msgid ""
"Programming fundamentals are a prerequisite for using a complex engine like "
"Godot. Talking about variables, functions, or classes is acceptable. But we "
"should favor plain language over specific terminology like "
"\"metaprogramming\". If you need to use precise terms, be sure to define "
"them."
msgstr ""

#: ../../docs/contributing/documentation/docs_writing_guidelines.rst:4
#, fuzzy
msgid "Writing guidelines"
msgstr "Kreiranje Sadržaja"

#: ../../docs/contributing/documentation/docs_writing_guidelines.rst:6
msgid ""
"The Godot community is rich and international. Users come from all around "
"the world. Some of them are young, and many aren't native English speakers. "
"That's why we must all write using a clear and a common language. For the "
"class reference, the goal is to make it easy to read for everyone and "
"precise."
msgstr ""

#: ../../docs/contributing/documentation/docs_writing_guidelines.rst:12
msgid "In summary, always try to:"
msgstr ""

#: ../../docs/contributing/documentation/docs_writing_guidelines.rst:14
#: ../../docs/contributing/documentation/docs_writing_guidelines.rst:44
msgid "Use the active voice"
msgstr ""

#: ../../docs/contributing/documentation/docs_writing_guidelines.rst:15
#: ../../docs/contributing/documentation/docs_writing_guidelines.rst:79
msgid "Use precise action verbs"
msgstr ""

#: ../../docs/contributing/documentation/docs_writing_guidelines.rst:16
#: ../../docs/contributing/documentation/docs_writing_guidelines.rst:101
msgid "Avoid verbs that end in -ing"
msgstr ""

#: ../../docs/contributing/documentation/docs_writing_guidelines.rst:17
msgid "Remove unnecessary adverbs and adjectives."
msgstr ""

#: ../../docs/contributing/documentation/docs_writing_guidelines.rst:18
msgid ""
"Ban these 8 words: obvious, simple, basic, easy, actual, just, clear, and "
"however"
msgstr ""

#: ../../docs/contributing/documentation/docs_writing_guidelines.rst:19
#: ../../docs/contributing/documentation/docs_writing_guidelines.rst:219
msgid "Use explicit references"
msgstr ""

#: ../../docs/contributing/documentation/docs_writing_guidelines.rst:20
#: ../../docs/contributing/documentation/docs_writing_guidelines.rst:240
msgid "Use 's to show possession"
msgstr ""

#: ../../docs/contributing/documentation/docs_writing_guidelines.rst:21
msgid "Use the Oxford comma"
msgstr ""

#: ../../docs/contributing/documentation/docs_writing_guidelines.rst:23
msgid "There are 3 rules to describe classes:"
msgstr ""

#: ../../docs/contributing/documentation/docs_writing_guidelines.rst:25
#: ../../docs/contributing/documentation/docs_writing_guidelines.rst:377
msgid "Give an overview of the node in the brief description"
msgstr ""

#: ../../docs/contributing/documentation/docs_writing_guidelines.rst:26
#: ../../docs/contributing/documentation/docs_writing_guidelines.rst:406
msgid "Mention what methods return if it's useful"
msgstr ""

#: ../../docs/contributing/documentation/docs_writing_guidelines.rst:27
#: ../../docs/contributing/documentation/docs_writing_guidelines.rst:431
msgid "Use \"if true\" to describe booleans"
msgstr ""

#: ../../docs/contributing/documentation/docs_writing_guidelines.rst:31
msgid ""
"A technical writer's job is to pack as much information as possible into the "
"smallest and clearest sentences possible. These guidelines will help you "
"work towards that goal."
msgstr ""

#: ../../docs/contributing/documentation/docs_writing_guidelines.rst:37
msgid ""
"See the :ref:`content guidelines <doc_content_guidelines>` for information "
"on the types of documentation you can write in the official documentation."
msgstr ""

#: ../../docs/contributing/documentation/docs_writing_guidelines.rst:41
msgid "7 rules for clear English"
msgstr ""

#: ../../docs/contributing/documentation/docs_writing_guidelines.rst:46
msgid ""
"Use the active voice when possible. Take the classes, methods, and constants "
"you describe as the subject. It's natural to write using the passive voice, "
"but it's harder to read and produces longer sentences."
msgstr ""

#: ../../docs/contributing/documentation/docs_writing_guidelines.rst:52
msgid "Passive:"
msgstr ""

#: ../../docs/contributing/documentation/docs_writing_guidelines.rst:58
msgid "Active:"
msgstr ""

#: ../../docs/contributing/documentation/docs_writing_guidelines.rst:64
#: ../../docs/contributing/documentation/docs_writing_guidelines.rst:412
msgid "**Don't** use the passive voice:"
msgstr ""

#: ../../docs/contributing/documentation/docs_writing_guidelines.rst:71
msgid "**Do** use the node's name as a noun:"
msgstr ""

#: ../../docs/contributing/documentation/docs_writing_guidelines.rst:81
msgid ""
"Favor precise yet common verbs over generic ones like ``make``, ``set``, and "
"any expression you can replace with a single word."
msgstr ""

#: ../../docs/contributing/documentation/docs_writing_guidelines.rst:84
msgid ""
"**Don't** repeat the method's name. It already states it sets the pivot "
"value to a new one:"
msgstr ""

#: ../../docs/contributing/documentation/docs_writing_guidelines.rst:92
msgid ""
"**Do** explain what's the consequence of this \"set\": use precise verbs "
"like ``place``, ``position``, ``rotate``, ``fade``, etc."
msgstr ""

#: ../../docs/contributing/documentation/docs_writing_guidelines.rst:103
msgid ""
"The progressive forms describe continuous actions. E.g. \"is calling\", \"is "
"moving\"."
msgstr ""

#: ../../docs/contributing/documentation/docs_writing_guidelines.rst:106
msgid "**Don't** use the progressive form for instant changes."
msgstr ""

#: ../../docs/contributing/documentation/docs_writing_guidelines.rst:113
msgid "**Do** use simple present, past, or future."
msgstr ""

#: ../../docs/contributing/documentation/docs_writing_guidelines.rst:120
msgid ""
"Exception: If the subject is not clear, replacing \"ing\" verbs is not an "
"improvement. For example, in the previous sentence, \"it replaces\" would "
"not make much sense where \"replacing\" currently is."
msgstr ""

#: ../../docs/contributing/documentation/docs_writing_guidelines.rst:124
msgid ""
"You may use the progressive tense to describe actions that are continuous in "
"time. Anything like animation or coroutines."
msgstr ""

#: ../../docs/contributing/documentation/docs_writing_guidelines.rst:129
msgid ""
"Verbs can turn into adjectival nouns with -ing. This is not a conjugation, "
"so you may use them: ``the remaining movement``, ``the missing file``, etc."
msgstr ""

#: ../../docs/contributing/documentation/docs_writing_guidelines.rst:134
msgid "Remove unnecessary adverbs and adjectives"
msgstr ""

#: ../../docs/contributing/documentation/docs_writing_guidelines.rst:136
msgid ""
"Write as few adjectives and adverbs as possible. Only use them if they add "
"key information to the description."
msgstr ""

#: ../../docs/contributing/documentation/docs_writing_guidelines.rst:139
msgid ""
"**Don't** use redundant or meaningless adverbs. Words that lengthen the "
"documentation but don't add any information:"
msgstr ""

#: ../../docs/contributing/documentation/docs_writing_guidelines.rst:146
msgid "**Do** write short sentences in a simple, descriptive language:"
msgstr ""

#: ../../docs/contributing/documentation/docs_writing_guidelines.rst:153
msgid "Ban these 8 words"
msgstr ""

#: ../../docs/contributing/documentation/docs_writing_guidelines.rst:155
msgid "**Don't** ever use these 8 banned words:"
msgstr ""

#: ../../docs/contributing/documentation/docs_writing_guidelines.rst:157
msgid "obvious"
msgstr ""

#: ../../docs/contributing/documentation/docs_writing_guidelines.rst:158
msgid "simple"
msgstr ""

#: ../../docs/contributing/documentation/docs_writing_guidelines.rst:159
msgid "basic"
msgstr ""

#: ../../docs/contributing/documentation/docs_writing_guidelines.rst:160
msgid "easy"
msgstr ""

#: ../../docs/contributing/documentation/docs_writing_guidelines.rst:161
msgid "actual"
msgstr ""

#: ../../docs/contributing/documentation/docs_writing_guidelines.rst:162
msgid "just"
msgstr ""

#: ../../docs/contributing/documentation/docs_writing_guidelines.rst:164
msgid "however (some uses)"
msgstr ""

#: ../../docs/contributing/documentation/docs_writing_guidelines.rst:166
msgid ""
"Game creation and programming aren't simple, and nothing's easy to someone "
"learning to use the API for the first time. Other words in the list, like "
"``just`` or ``actual`` won't add any info to the sentence. Don't use "
"corresponding adverbs either: obviously, simply, basically, easily, "
"actually, clearly."
msgstr ""

#: ../../docs/contributing/documentation/docs_writing_guidelines.rst:172
msgid ""
"**Don't** example. The banned words lengthen the description and take "
"attention away from the most important info:"
msgstr ""

#: ../../docs/contributing/documentation/docs_writing_guidelines.rst:180
msgid "**Do** remove them:"
msgstr ""

#: ../../docs/contributing/documentation/docs_writing_guidelines.rst:187
msgid ""
"\"Simple\" never helps. Remember, for other users, anything could be complex "
"or frustrate them. There's nothing like a good old *it's simple* to make you "
"cringe. Here's the old brief description, the first sentence on the Timer "
"node's page:"
msgstr ""

#: ../../docs/contributing/documentation/docs_writing_guidelines.rst:197
msgid "**Do** explain what the node does instead:"
msgstr ""

#: ../../docs/contributing/documentation/docs_writing_guidelines.rst:204
msgid "**Don't** use \"basic\", it is too vague:"
msgstr ""

#: ../../docs/contributing/documentation/docs_writing_guidelines.rst:211
msgid "**Do** use the brief description to offer an overview of the node:"
msgstr ""

#: ../../docs/contributing/documentation/docs_writing_guidelines.rst:221
msgid "Favor explicit references over implicit ones."
msgstr ""

#: ../../docs/contributing/documentation/docs_writing_guidelines.rst:223
msgid ""
"**Don't** use words like \"the former\", \"the latter\", etc. They're not "
"the most common in English, and they require you to check the reference."
msgstr ""

#: ../../docs/contributing/documentation/docs_writing_guidelines.rst:230
msgid "**Do** repeat words. They remove all ambiguity:"
msgstr ""

#: ../../docs/contributing/documentation/docs_writing_guidelines.rst:236
msgid ""
"If you need to repeat the same variable name 3 or 4 times, you probably need "
"to rephrase your description."
msgstr ""

#: ../../docs/contributing/documentation/docs_writing_guidelines.rst:242
msgid ""
"Avoid \"The milk **of** the cow\". It feels unnatural in English. Write "
"\"The cow's milk\" instead."
msgstr ""

#: ../../docs/contributing/documentation/docs_writing_guidelines.rst:245
msgid "**Don't** write \"of the X\":"
msgstr ""

#: ../../docs/contributing/documentation/docs_writing_guidelines.rst:251
msgid ""
"**Do** use ``'s``. It lets you put the main subject at the start of the "
"sentence, and keep it short:"
msgstr ""

#: ../../docs/contributing/documentation/docs_writing_guidelines.rst:259
msgid "Use the Oxford comma to enumerate anything"
msgstr ""

#: ../../docs/contributing/documentation/docs_writing_guidelines.rst:261
msgid "From the Oxford dictionary:"
msgstr ""

#: ../../docs/contributing/documentation/docs_writing_guidelines.rst:263
msgid ""
"The 'Oxford comma' is an optional comma before the word 'and' at the end of "
"a list: *We sell books, videos, and magazines.*"
msgstr ""

#: ../../docs/contributing/documentation/docs_writing_guidelines.rst:266
msgid ""
"[...] Not all writers and publishers use it, but it can clarify the meaning "
"of a sentence when the items in a list are not single words: *These items "
"are available in black and white, red and yellow, and blue and green.*"
msgstr ""

#: ../../docs/contributing/documentation/docs_writing_guidelines.rst:269
msgid "**Don't** leave the last element of a list without a comma:"
msgstr ""

#: ../../docs/contributing/documentation/docs_writing_guidelines.rst:275
msgid ""
"**Do** add a comma before `and` or `or`, for the last element of a list with "
"more than two elements."
msgstr ""

#: ../../docs/contributing/documentation/docs_writing_guidelines.rst:284
msgid "How to write methods and classes"
msgstr ""

#: ../../docs/contributing/documentation/docs_writing_guidelines.rst:287
msgid "Dynamic vs static typing"
msgstr ""

#: ../../docs/contributing/documentation/docs_writing_guidelines.rst:289
msgid ""
"The code examples in the documentation should follow a consistent style not "
"to confuse users. As static type hints are an optional feature of GDScript, "
"we chose to stick to writing dynamic code. This leads to writing GDScript "
"that is concise and accessible."
msgstr ""

#: ../../docs/contributing/documentation/docs_writing_guidelines.rst:294
msgid "The exception is topics that explain static typing concepts to users."
msgstr ""

#: ../../docs/contributing/documentation/docs_writing_guidelines.rst:296
msgid "**Don't** add a type hint with a colon or by casting:"
msgstr ""

#: ../../docs/contributing/documentation/docs_writing_guidelines.rst:306
msgid "**Do** write constants and variables with dynamic typing:"
msgstr ""

#: ../../docs/contributing/documentation/docs_writing_guidelines.rst:316
msgid "**Don't** write functions with inferred arguments or return types:"
msgstr ""

#: ../../docs/contributing/documentation/docs_writing_guidelines.rst:327
msgid "**Do** write functions using dynamic typing:"
msgstr ""

#: ../../docs/contributing/documentation/docs_writing_guidelines.rst:339
msgid "Use real-world code examples where appropriate"
msgstr ""

#: ../../docs/contributing/documentation/docs_writing_guidelines.rst:341
msgid ""
"Real-world examples are more accessible to beginners than abstract ``foos`` "
"and ``bars``. You can also copy them directly from your game projects, "
"ensuring that any code snippet compiles without errors."
msgstr ""

#: ../../docs/contributing/documentation/docs_writing_guidelines.rst:345
msgid ""
"Writing ``var speed = 10`` rather than ``var my_var = 10`` allows beginners "
"to understand code better. It gives them a frame of reference as to where "
"they could use the code snippets in a live project."
msgstr ""

#: ../../docs/contributing/documentation/docs_writing_guidelines.rst:349
msgid "**Don't** write made-up examples:"
msgstr ""

#: ../../docs/contributing/documentation/docs_writing_guidelines.rst:360
msgid "**Do** write concrete examples:"
msgstr ""

#: ../../docs/contributing/documentation/docs_writing_guidelines.rst:372
msgid ""
"Of course, there are times when using real-world examples is impractical. In "
"those situations, you should still avoid using names such as ``my_var``, "
"``foo()`` or ``my_func()`` and consider more meaningful names for your "
"examples."
msgstr ""

#: ../../docs/contributing/documentation/docs_writing_guidelines.rst:379
msgid ""
"The brief description is the reference's most important sentence. It's the "
"user's first contact with a node:"
msgstr ""

#: ../../docs/contributing/documentation/docs_writing_guidelines.rst:382
msgid "It's the only description in the \"Create New Node\" dialog."
msgstr ""

#: ../../docs/contributing/documentation/docs_writing_guidelines.rst:383
msgid "It's at the top of every page in the reference"
msgstr ""

#: ../../docs/contributing/documentation/docs_writing_guidelines.rst:385
msgid ""
"The brief description should explain the node's role and its functionality, "
"in up to 200 characters."
msgstr ""

#: ../../docs/contributing/documentation/docs_writing_guidelines.rst:388
msgid "**Don't** write tiny and vague summaries:"
msgstr ""

#: ../../docs/contributing/documentation/docs_writing_guidelines.rst:395
msgid "**Do** give an overview of the node's functionality:"
msgstr ""

#: ../../docs/contributing/documentation/docs_writing_guidelines.rst:402
msgid ""
"Use the node's full description to provide more information, and a code "
"example, if possible."
msgstr ""

#: ../../docs/contributing/documentation/docs_writing_guidelines.rst:408
msgid ""
"Some methods return important values. Describe them at the end of the "
"description, ideally on a new line. No need to mention the return values for "
"any method whose name starts with ``set`` or ``get``."
msgstr ""

#: ../../docs/contributing/documentation/docs_writing_guidelines.rst:419
msgid "**Do** always use \"Returns\"."
msgstr ""

#: ../../docs/contributing/documentation/docs_writing_guidelines.rst:426
msgid ""
"Notice the exception to the \"direct voice\" rule: with the move method, an "
"external collider can influence the method and the body that calls ``move``. "
"In this case, you can use the passive voice."
msgstr ""

#: ../../docs/contributing/documentation/docs_writing_guidelines.rst:433
msgid ""
"For boolean member variables, always use ``if true`` and/or ``if false``, to "
"stay explicit. ``Controls whether or not`` may be ambiguous and won't work "
"for every member variable."
msgstr ""

#: ../../docs/contributing/documentation/docs_writing_guidelines.rst:437
msgid ""
"Also, surround boolean values, variable names and methods with ``[code][/"
"code]``."
msgstr ""

#: ../../docs/contributing/documentation/docs_writing_guidelines.rst:439
msgid "**Do** start with \"if true\":"
msgstr ""

#: ../../docs/contributing/documentation/docs_writing_guidelines.rst:448
msgid "Use ``[code]`` around arguments"
msgstr ""

#: ../../docs/contributing/documentation/docs_writing_guidelines.rst:450
msgid ""
"In the class reference, always surround arguments with ``[code][/code]``. In "
"the documentation and in Godot, it will display like ``this``. When you edit "
"XML files in the Godot repository, replace existing arguments written like "
"'this' or \\`this\\` with ``[code]this[/code]``."
msgstr ""

#: ../../docs/contributing/documentation/docs_writing_guidelines.rst:457
msgid "Common vocabulary to use in Godot's documentation"
msgstr ""

#: ../../docs/contributing/documentation/docs_writing_guidelines.rst:459
msgid ""
"The developers chose some specific words to refer to areas of the interface. "
"They're used in the sources, in the documentation, and you should always use "
"them instead of synonyms, so the users know what you're talking about."
msgstr ""

#: ../../docs/contributing/documentation/docs_writing_guidelines.rst:467
msgid "Overview of the interface and common vocabulary"
msgstr ""

#: ../../docs/contributing/documentation/docs_writing_guidelines.rst:469
msgid ""
"In the top left corner of the editor lie the ``main menus``. In the center, "
"the buttons change the ``workspace``. And together the buttons in the top "
"right are the ``playtest buttons``. The area in the center, that displays "
"the 2D or the 3D space, is the ``viewport``. At its top, you find a list of "
"``tools`` inside the ``toolbar``."
msgstr ""

#: ../../docs/contributing/documentation/docs_writing_guidelines.rst:475
msgid ""
"The tabs or dockable panels on either side of the viewport are ``docks``. "
"You have the ``FileSystem dock``, the ``Scene dock`` that contains your "
"scene tree, the ``Import dock``, the ``Node dock``, and the ``Inspector`` or "
"``Inspector dock``. With the default layout you may call the tabbed docks "
"``tabs``: the ``Scene tab``, the ``Node tab``..."
msgstr ""

#: ../../docs/contributing/documentation/docs_writing_guidelines.rst:481
msgid ""
"The Animation, Debugger, etc. at the bottom of the viewport are ``panels``. "
"Together they make up the ``bottom panels``."
msgstr ""

#: ../../docs/contributing/documentation/docs_writing_guidelines.rst:484
msgid ""
"Foldable areas of the Inspector are ``sections``. The node's parent class "
"names, which you can't fold, are ``Classes`` e.g. the ``CharacterBody2D "
"class``. And individual lines with key-value pairs are ``properties``. E.g. "
"``position`` or ``modulate color`` are both ``properties``."
msgstr ""

#: ../../docs/contributing/documentation/docs_writing_guidelines.rst:491
msgid "Keyboard shortcut guidelines"
msgstr ""

#: ../../docs/contributing/documentation/docs_writing_guidelines.rst:493
msgid ""
"Keyboard and mouse shortcuts should make use of the ``:kbd:`` tag, which "
"allows shortcuts to stand out from the rest of the text and inline code. Use "
"the compact form for modifier keys (:kbd:`Ctrl`/:kbd:`Cmd`) instead of their "
"spelled out form (:kbd:`Control`/:kbd:`Command`). For combinations, use the "
"``+`` symbol with a space on either side of the symbol."
msgstr ""

#: ../../docs/contributing/documentation/docs_writing_guidelines.rst:499
msgid ""
"Make sure to mention shortcuts that differ on macOS compared to other "
"platforms. On macOS, ``Cmd`` often replaces ``Ctrl`` in keyboard shortcuts."
msgstr ""

#: ../../docs/contributing/documentation/docs_writing_guidelines.rst:502
msgid ""
"Try to integrate the shortcut into sentences the best you can. Here are some "
"examples with the ``:kbd:`` tag left as-is for better visibility:"
msgstr ""

#: ../../docs/contributing/documentation/docs_writing_guidelines.rst:505
msgid ""
"Press ``:kbd:`Ctrl + Alt + T``` to toggle the panel (``:kbd:`Cmd + Alt + "
"T``` on macOS)."
msgstr ""

#: ../../docs/contributing/documentation/docs_writing_guidelines.rst:506
msgid ""
"Press ``:kbd:`Space``` and hold the left mouse button to pan in the 2D "
"editor."
msgstr ""

#: ../../docs/contributing/documentation/docs_writing_guidelines.rst:507
msgid "Press ``:kbd:`Shift + Up Arrow``` to move the node upwards by 8 pixels."
msgstr ""

#: ../../docs/contributing/documentation/docs_image_guidelines.rst:4
#, fuzzy
msgid "Creating documentation images"
msgstr "Organizacija dokumentacije"

#: ../../docs/contributing/documentation/docs_image_guidelines.rst:6
msgid ""
"Throughout documentation images are often needed to make the explanation of "
"a feature or concept as clear as possible for a reader. This page will "
"explain the process from beginning to end."
msgstr ""

#: ../../docs/contributing/documentation/docs_image_guidelines.rst:11
#, fuzzy
msgid "Capturing an image"
msgstr "Kreiranje Sadržaja"

#: ../../docs/contributing/documentation/docs_image_guidelines.rst:13
msgid ""
"To take a picture of something in Godot a screen capture tool can be used."
msgstr ""

#: ../../docs/contributing/documentation/docs_image_guidelines.rst:15
msgid ""
"On Windows 10 and 11 that would be the Snip & Sketch program. Pressing :kbd:"
"`Windows + Shift + S` lets you take a screenshot of a portion of the screen "
"and save it to the clipboard. After pressing those keys, click and drag over "
"the area you wish to take a picture of."
msgstr ""

#: ../../docs/contributing/documentation/docs_image_guidelines.rst:21
msgid ""
"On macOS, pressing :kbd:`Shift + Command + 3` does the same. To take a "
"picture of the entire screen press :kbd:`Shift + Command + 4`. All "
"screenshots taken will be saved to the desktop."
msgstr ""

#: ../../docs/contributing/documentation/docs_image_guidelines.rst:25
msgid ""
"Each Linux desktop environment has it's own screenshot tool. For example, on "
"KDE Plasma the program Spectacle is used for taking screenshots. If your "
"distribution doesn't come with one by default try searching its package "
"repository, or Flathub if that's supported."
msgstr ""

#: ../../docs/contributing/documentation/docs_image_guidelines.rst:30
msgid ""
"All screenshots should ideally be taken on a 1080p screen. Anything higher "
"resolution is adding detail that doesn't make the documentation better and "
"dramatically increases file size. If you're taking screenshots on a higher "
"resolution screen the screenshot should be scaled down. There are "
"instructions on how to do this later on this page."
msgstr ""

#: ../../docs/contributing/documentation/docs_image_guidelines.rst:37
msgid "Format conversion"
msgstr ""

#: ../../docs/contributing/documentation/docs_image_guidelines.rst:39
msgid ""
"The current format for images in Godot's documentation is WebP (``.webp``). "
"While some Linux programs will support saving screenshots in this format, "
"macOS and the Snip & Sketch program on Windows do not. For images that don't "
"need editing, such as precise cropping or adding outlines, Squoosh can be "
"used. `Squoosh <https://squoosh.app/>`_ is a converter developed by Google, "
"is open source, and doesn't give Google any image rights by using it. When "
"choosing compression if you can get an image that's under 300KB in size use "
"lossless compression. If it's over 300KB, use just enough lossy compression "
"to get it under that size. If this results in noticable compression "
"artifacts using less compression is fine, even if the file size is bigger."
msgstr ""

#: ../../docs/contributing/documentation/docs_image_guidelines.rst:50
msgid ""
"If you already have an image editor such as GIMP, Krita or Photoshop "
"installed it may have the ability to open an image then save it as a WebP "
"file."
msgstr ""

#: ../../docs/contributing/documentation/docs_image_guidelines.rst:54
msgid "Cropping"
msgstr ""

#: ../../docs/contributing/documentation/docs_image_guidelines.rst:56
msgid ""
"For a screenshot of a 2D or 3D scene in the editor the above steps will be "
"enough. But for most UI images some extra work should be done, specifically "
"cropping to make an image look clean. Below is an example of good cropping."
msgstr ""

#: ../../docs/contributing/documentation/docs_image_guidelines.rst:62
msgid ""
"For cropping Krita is the recommended program. While some screenshot "
"programs do have cropping built in it's not always easy to get something "
"precise. And while Krita is designed as a painting program the cropping tool "
"gives you pixel precision by default. Of course, feel free to use a "
"different program you are familiar with."
msgstr ""

#: ../../docs/contributing/documentation/docs_image_guidelines.rst:67
msgid ""
"If you've never used Krita before download it from the `official Krita "
"website <https://krita.org/en/download/krita-desktop/>`_, on Linux you may "
"also be able to download it from your distributions repository, flathub is "
"also an option. Once it's installed on your computer open Krita then open "
"the image you want to crop. This button on the left panel is the crop tool."
msgstr ""

#: ../../docs/contributing/documentation/docs_image_guidelines.rst:74
msgid ""
"After selecting it, click on the image, you should now have cropping tools "
"available."
msgstr ""

#: ../../docs/contributing/documentation/docs_image_guidelines.rst:78
msgid ""
"Click and drag the white boxes to adjust what gets cropped, if you zoom in "
"close to the image you will see the individual pixels in an image, which is "
"useful for precision."
msgstr ""

#: ../../docs/contributing/documentation/docs_image_guidelines.rst:84
msgid ""
"If you make a mistake and overcrop don't worry, cropping is non-destructive "
"in Krita and can be adjusted. Click on the image with your cropping tool "
"still selected and the controls will return."
msgstr ""

#: ../../docs/contributing/documentation/docs_image_guidelines.rst:89
msgid "Scaling down an image"
msgstr ""

#: ../../docs/contributing/documentation/docs_image_guidelines.rst:91
msgid ""
"As explained earlier on this page, all images taken on a screen that is a "
"higher resolution than 1080p should be scaled down. To do this in Krita "
"click on **Image** on the top bar, and from the dropdown menu select **Scale "
"Image To New Size**. This menu can also be opened by pressing :kbd:`Ctrl + "
"Alt + I`. On this menu you want to adjust the pixel dimensions. For anything "
"taken on a 4K monitor change the value of the width and height to half of "
"its current value, for anything taken on a 1440p monitor multiply the width "
"and height by 0.75. Make sure the **Constrain Proportions** box at the "
"bottom of the menu is checked so you only have to change 1 value."
msgstr ""

#: ../../docs/contributing/documentation/docs_image_guidelines.rst:101
msgid "Saving as WebP in Krita"
msgstr ""

#: ../../docs/contributing/documentation/docs_image_guidelines.rst:103
msgid ""
"To save an image as webp if it isn't already one, Go to **File > Save As**. "
"Select **webp** from the **Save as type:** dropdown, then choose wherever "
"you want to save it. After clicking **Save** a menu will popup with webp "
"options. Make sure **Losses** is checked and **Quality** is set to 100%. "
"This means the image will not lose detail and will be as small as possible."
msgstr ""

#: ../../docs/contributing/documentation/docs_image_guidelines.rst:108
msgid ""
"If the image is over 300KB in size try compressing it losslessly using "
"`Squoosh <https://squoosh.app/>`_. If it's still over 300KB change to lossy "
"compression and slowly increase the compression until it's under 300KB. If "
"this results in noticeable compression artifacts using less compression is "
"fine, even if the file size is bigger."
msgstr ""

#: ../../docs/contributing/documentation/docs_image_guidelines.rst:114
msgid "Outlines arrows and text"
msgstr ""

#: ../../docs/contributing/documentation/docs_image_guidelines.rst:116
msgid ""
"Sometimes an image needs something extra to properly direct the readers "
"attention, or make something clear. Outlines and arrows can be used for this "
"purpose. For these types of edits Inkscape is the recommended open source "
"program, it can be downloaded from the `official Inkscape website <https://"
"inkscape.org/>`_. Like Krita, if you're on Linux you can also check your "
"distributions repository or get it from Flathub."
msgstr ""

#: ../../docs/contributing/documentation/docs_image_guidelines.rst:123
msgid ""
"A full tutorial on creating outlines is not provided here, we recommend "
"searching for various tutorials on how to use it online. However there are "
"two standards for doc image outlines and arrows. First, the color should be "
"yellow, specifically this hex color: ``fffb44`` (``fffb44ff`` if there is a "
"transparency value like in Inkscape). This color was chosen specifically to "
"make sure color blind people do not have issues reading the documentation, "
"other colors can be used in addition to this yellow if multiple outlines on "
"an image are needed, red should be avoided. The second standard is that all "
"outlines and arrow lines should be 2 pixels wide."
msgstr ""

#: ../../docs/contributing/documentation/docs_image_guidelines.rst:132
msgid ""
"Finally, some images might require text to differentiate multiple parts of "
"an image. There are no strict requirements other than use an easy to read "
"non fancy font. As for color the yellow color from before should also be "
"used, but black or other colors can be used if appropriate. For example, if "
"yellow blends into the image, or if there are multiple outlines in multiple "
"colors."
msgstr ""

#: ../../docs/contributing/documentation/docs_image_guidelines.rst:139
#, fuzzy
msgid "Adding an image to a documentation page"
msgstr "Organizacija dokumentacije"

#: ../../docs/contributing/documentation/docs_image_guidelines.rst:141
msgid ""
"Once you've finished working on your image, it can be added to the "
"documentation. All images are stored in folders named ``img`` next to the "
"page they are used in."
msgstr ""

#: ../../docs/contributing/documentation/docs_image_guidelines.rst:144
msgid ""
"To add your image, add it to the ``img`` folder that's in the same folder as "
"the ``.rst`` file for the page (create it if it doesn't exist). In the ``."
"rst`` page, images should be included with the following code snippet::"
msgstr ""

#: ../../docs/contributing/documentation/docs_image_guidelines.rst:150
msgid ""
"Where ``documentation_image.webp`` would be changed to the name of the image "
"you created. Name your images in a way that makes their meaning clear, "
"possibly with a prefix that makes their relationship to a documentation page "
"explicit."
msgstr ""

#: ../../docs/contributing/documentation/contributing_to_the_documentation.rst:6
msgid ""
"This guide explains how to contribute to Godot's documentation, be it by "
"writing or reviewing pages."
msgstr ""

#: ../../docs/contributing/documentation/contributing_to_the_documentation.rst:11
msgid ""
"If you want to translate pages or the class reference from English to other "
"languages, read :ref:`doc_editor_and_docs_localization`."
msgstr ""

#: ../../docs/contributing/documentation/contributing_to_the_documentation.rst:17
msgid ""
"To modify or create pages in the reference manual, you need to edit ``.rst`` "
"files in the `godot-docs GitHub repository <https://github.com/godotengine/"
"godot-docs>`_. Modifying those pages in a pull request triggers a rebuild of "
"the online documentation upon merging."
msgstr ""

#: ../../docs/contributing/documentation/contributing_to_the_documentation.rst:22
msgid ""
"For details on Git usage and the pull request workflow, please refer to the :"
"ref:`doc_pr_workflow` page. Most of what it describes regarding the main "
"godotengine/godot repository is also valid for the docs repository."
msgstr ""

#: ../../docs/contributing/documentation/contributing_to_the_documentation.rst:27
msgid ""
"The class reference's source files are in the `Godot engine repository "
"<https://github.com/godotengine/godot>`_. We generate the :ref:`Class "
"Reference <doc_class_reference>` section of this documentation from them. If "
"you want to update the description of a class, its methods, or properties, "
"read :ref:`doc_updating_the_class_reference`."
msgstr ""

#: ../../docs/contributing/documentation/contributing_to_the_documentation.rst:35
#, fuzzy
msgid "What is the Godot documentation"
msgstr "O dokumentaciji"

#: ../../docs/contributing/documentation/contributing_to_the_documentation.rst:37
msgid ""
"The Godot documentation is intended as a comprehensive reference manual for "
"the Godot game engine. It is not meant to contain step-by-step tutorials, "
"except for two game creation tutorials in the Getting Started section."
msgstr ""

#: ../../docs/contributing/documentation/contributing_to_the_documentation.rst:41
msgid ""
"We strive to write factual content in an accessible and well-written "
"language. To contribute, you should also read:"
msgstr ""

#: ../../docs/contributing/documentation/contributing_to_the_documentation.rst:44
msgid ""
":ref:`doc_docs_writing_guidelines`. There, you will find rules and "
"recommendations to write in a way that everyone understands."
msgstr ""

#: ../../docs/contributing/documentation/contributing_to_the_documentation.rst:46
msgid ""
":ref:`doc_content_guidelines`. They explain the principles we follow to "
"write the documentation and the kind of content we accept."
msgstr ""

#: ../../docs/contributing/documentation/contributing_to_the_documentation.rst:50
#, fuzzy
msgid "Contributing changes"
msgstr "Kreiranje Sadržaja"

#: ../../docs/contributing/documentation/contributing_to_the_documentation.rst:52
msgid ""
"**Pull Requests should use the** ``master`` **branch by default.** Only make "
"Pull Requests against other branches (e.g. ``2.1`` or ``3.0``) if your "
"changes only apply to that specific version of Godot."
msgstr ""

#: ../../docs/contributing/documentation/contributing_to_the_documentation.rst:56
msgid ""
"Though less convenient to edit than a wiki, this Git repository is where we "
"write the documentation. Having direct access to the source files in a "
"revision control system is a plus to ensure our documentation quality."
msgstr ""

#: ../../docs/contributing/documentation/contributing_to_the_documentation.rst:61
msgid "Editing existing pages"
msgstr ""

#: ../../docs/contributing/documentation/contributing_to_the_documentation.rst:63
msgid ""
"To edit an existing page, locate its ``.rst`` source file and open it in "
"your favorite text editor. You can then commit the changes, push them to "
"your fork, and make a pull request. **Note that the pages in** ``classes/`` "
"**should not be edited here.** They are automatically generated from Godot's "
"`XML class reference <https://github.com/godotengine/godot/tree/master/doc/"
"classes>`__. See :ref:`doc_updating_the_class_reference` for details."
msgstr ""

#: ../../docs/contributing/documentation/contributing_to_the_documentation.rst:70
msgid ""
"To build the manual and test changes on your computer, see :ref:"
"`doc_building_the_manual`."
msgstr ""

#: ../../docs/contributing/documentation/contributing_to_the_documentation.rst:74
msgid "Editing pages online"
msgstr ""

#: ../../docs/contributing/documentation/contributing_to_the_documentation.rst:76
msgid ""
"You can edit the documentation online by clicking the **Edit on GitHub** "
"link in the top-right of every page."
msgstr ""

#: ../../docs/contributing/documentation/contributing_to_the_documentation.rst:79
msgid ""
"Doing so takes you to the GitHub text editor. You need to have a GitHub "
"account and to log in to use it. Once logged in, you can propose change like "
"so:"
msgstr ""

#: ../../docs/contributing/documentation/contributing_to_the_documentation.rst:82
msgid "Click the **Edit on GitHub** button."
msgstr ""

#: ../../docs/contributing/documentation/contributing_to_the_documentation.rst:84
msgid ""
"On the GitHub page you're taken to, click the pencil icon in the top-right "
"corner near the **Raw**, **Blame**, and **Delete** buttons. It has the "
"tooltip \"Fork this project and edit the file\"."
msgstr ""

#: ../../docs/contributing/documentation/contributing_to_the_documentation.rst:88
#, fuzzy
msgid "Edit the text in the text editor."
msgstr "Kreiranje Sadržaja"

#: ../../docs/contributing/documentation/contributing_to_the_documentation.rst:90
msgid ""
"At the bottom of the web page, summarize the changes you made and click the "
"button **Propose file change**. Make sure to replace the placeholder "
"\"Update file.rst\" by a short but clear one-line description, as this is "
"the commit title."
msgstr ""

#: ../../docs/contributing/documentation/contributing_to_the_documentation.rst:94
msgid ""
"On the following screens, click the **Create pull request** button until you "
"see a message like *Username wants to merge 1 commit into godotengine:master "
"from Username:patch-1*."
msgstr ""

#: ../../docs/contributing/documentation/contributing_to_the_documentation.rst:98
msgid ""
"Another contributor will review your changes and merge them into the docs if "
"they're good. They may also make changes or ask you to do so before merging."
msgstr ""

#: ../../docs/contributing/documentation/contributing_to_the_documentation.rst:102
#, fuzzy
msgid "Adding new pages"
msgstr "Kreiranje Sadržaja"

#: ../../docs/contributing/documentation/contributing_to_the_documentation.rst:104
msgid ""
"Before adding a new page, please ensure that it fits in the documentation:"
msgstr ""

#: ../../docs/contributing/documentation/contributing_to_the_documentation.rst:106
msgid ""
"Look for `existing issues <https://github.com/godotengine/godot-docs/"
"issues>`_ or open a new one to see if the page is necessary."
msgstr ""

#: ../../docs/contributing/documentation/contributing_to_the_documentation.rst:109
msgid "Ensure there isn't a page that already covers the topic."
msgstr ""

#: ../../docs/contributing/documentation/contributing_to_the_documentation.rst:110
msgid "Read our :ref:`doc_content_guidelines`."
msgstr ""

#: ../../docs/contributing/documentation/contributing_to_the_documentation.rst:112
msgid ""
"To add a new page, create a ``.rst`` file with a meaningful name in the "
"section you want to add a file to, e.g. ``tutorials/3d/light_baking.rst``."
msgstr ""

#: ../../docs/contributing/documentation/contributing_to_the_documentation.rst:115
msgid ""
"You should then add your page to the relevant \"toctree\" (table of "
"contents, e.g. ``tutorials/3d/index.rst``). Add your new filename to the "
"list on a new line, using a relative path and no extension, e.g. here "
"``light_baking``."
msgstr ""

#: ../../docs/contributing/documentation/contributing_to_the_documentation.rst:120
msgid "Titles"
msgstr ""

#: ../../docs/contributing/documentation/contributing_to_the_documentation.rst:122
msgid "Always begin pages with their title and a Sphinx reference name:"
msgstr ""

#: ../../docs/contributing/documentation/contributing_to_the_documentation.rst:131
msgid ""
"The reference ``_doc_insert_your_title_here`` and the title should match."
msgstr ""

#: ../../docs/contributing/documentation/contributing_to_the_documentation.rst:133
msgid ""
"The reference allows linking to this page using the ``:ref:`` format, e.g. "
"``:ref:`doc_insert_your_title_here``` would link to the above example page "
"(note the lack of leading underscore in the reference)."
msgstr ""

#: ../../docs/contributing/documentation/contributing_to_the_documentation.rst:137
msgid "Write your titles like plain sentences, without capitalizing each word:"
msgstr ""

#: ../../docs/contributing/documentation/contributing_to_the_documentation.rst:139
msgid "**Good:** Understanding signals in Godot"
msgstr ""

#: ../../docs/contributing/documentation/contributing_to_the_documentation.rst:140
msgid "**Bad:** Understanding Signals In Godot"
msgstr ""

#: ../../docs/contributing/documentation/contributing_to_the_documentation.rst:142
msgid ""
"Only proper nouns, projects, people, and node class names should have their "
"first letter capitalized."
msgstr ""

#: ../../docs/contributing/documentation/contributing_to_the_documentation.rst:146
msgid "Sphinx and reStructuredText syntax"
msgstr ""

#: ../../docs/contributing/documentation/contributing_to_the_documentation.rst:148
msgid ""
"Check Sphinx's `reST Primer <https://www.sphinx-doc.org/en/stable/rest."
"html>`__ and the `official reference <https://docutils.sourceforge.net/rst."
"html>`__ for details on the syntax."
msgstr ""

#: ../../docs/contributing/documentation/contributing_to_the_documentation.rst:152
msgid ""
"Sphinx uses specific reST comments to do specific operations, like defining "
"the table of contents (``.. toctree::``) or cross-referencing pages. Check "
"the `official Sphinx documentation <https://www.sphinx-doc.org/en/stable/"
"index.html>`__ for more details. To learn how to use Sphinx directives like "
"``.. note::`` or ``.. seealso::``, check out the `Sphinx directives "
"documentation <https://www.sphinx-doc.org/en/master/usage/restructuredtext/"
"directives.html>`__."
msgstr ""

#: ../../docs/contributing/documentation/contributing_to_the_documentation.rst:161
msgid "Adding images and attachments"
msgstr ""

#: ../../docs/contributing/documentation/contributing_to_the_documentation.rst:163
msgid ""
"To add images, please put them in an ``img/`` folder next to the ``.rst`` "
"file with a meaningful name and include them in your page with:"
msgstr ""

#: ../../docs/contributing/documentation/contributing_to_the_documentation.rst:170
msgid ""
"Alternatively, you can use the `figure` directive, which gives the image a "
"contrasting border and allows centering it on the page."
msgstr ""

#: ../../docs/contributing/documentation/contributing_to_the_documentation.rst:178
msgid ""
"You can also include attachments as support material for a tutorial, by "
"placing them into a ``files/`` folder next to the ``.rst`` file, and using "
"this inline markup:"
msgstr ""

#: ../../docs/contributing/documentation/contributing_to_the_documentation.rst:185
msgid ""
"Consider using the `godot-docs-project-starters <https://github.com/"
"godotengine/godot-docs-project-starters>` repository for hosting support "
"materials, such as project templates and asset packs. You can use a direct "
"link to the generated archive from that repository with the regular link "
"markup:"
msgstr ""

#: ../../docs/contributing/documentation/contributing_to_the_documentation.rst:196
msgid "License"
msgstr ""

#: ../../docs/contributing/documentation/contributing_to_the_documentation.rst:198
#, fuzzy
msgid ""
"This documentation and every page it contains is published under the terms "
"of the `Creative Commons Attribution 3.0 license (CC BY 3.0) <https://"
"creativecommons.org/licenses/by/3.0/>`_, with attribution to \"Juan "
"Linietsky, Ariel Manzur and the Godot community\"."
msgstr ""
"Sav sadržaj dokumentacije je pod popustljivom (`CC-BY 3.0 <https://"
"creativecommons.org/licenses/by/3.0/>`_) licencom, sa atribucijom \"Juan "
"Linietsky, Ariel Manzur and the Godot Engine community\"."

#: ../../docs/contributing/documentation/contributing_to_the_documentation.rst:203
msgid ""
"By contributing to the documentation on the GitHub repository, you agree "
"that your changes are distributed under this license."
msgstr ""

#: ../../docs/contributing/documentation/building_the_manual.rst:4
#, fuzzy
msgid "Building the manual with Sphinx"
msgstr "Kreiranje Sadržaja"

#: ../../docs/contributing/documentation/building_the_manual.rst:6
msgid ""
"This page explains how to build a local copy of the Godot manual using the "
"Sphinx docs engine. This allows you to have local HTML files and build the "
"documentation as a PDF, EPUB, or LaTeX file, for example."
msgstr ""

#: ../../docs/contributing/documentation/building_the_manual.rst:10
msgid "Before you get started, make sure that you have:"
msgstr ""

#: ../../docs/contributing/documentation/building_the_manual.rst:12
#, fuzzy
msgid "`Git <https://git-scm.com/>`_"
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati raznorazne `Godot demo projects "
"<https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/contributing/documentation/building_the_manual.rst:13
msgid ""
"`make <https://www.gnu.org/software/make/>`_ (unless you're using Windows)"
msgstr ""

#: ../../docs/contributing/documentation/building_the_manual.rst:14
msgid "`Python <https://www.python.org/>`_ 3"
msgstr ""

#: ../../docs/contributing/documentation/building_the_manual.rst:16
msgid ""
"Python 3 should come with the ``pip3`` command. You may need to write "
"``python3 -m pip`` (Unix) or  ``py -m pip`` (Windows) instead of ``pip3``. "
"If both approaches fail, `make sure that you have pip3 installed <https://"
"pip.pypa.io/en/stable/installation/>`__."
msgstr ""

#: ../../docs/contributing/documentation/building_the_manual.rst:21
msgid ""
"*(Optional)* Set up a virtual environment. Virtual environments prevent "
"potential conflicts between the Python packages in ``requirements.txt`` and "
"other Python packages that are installed on your system."
msgstr ""

#: ../../docs/contributing/documentation/building_the_manual.rst:25
msgid "Create the virtual environment:"
msgstr ""

#: ../../docs/contributing/documentation/building_the_manual.rst:35
#: ../../docs/contributing/documentation/building_the_manual.rst:51
#: ../../docs/contributing/documentation/building_the_manual.rst:67
#: ../../docs/contributing/documentation/building_the_manual.rst:151
msgid "Other platforms"
msgstr ""

#: ../../docs/contributing/documentation/building_the_manual.rst:41
msgid "Activate the virtual environment:"
msgstr ""

#: ../../docs/contributing/documentation/building_the_manual.rst:57
msgid "*(Optional)* Update pre-installed packages:"
msgstr ""

#: ../../docs/contributing/documentation/building_the_manual.rst:73
msgid "Clone the docs repo:"
msgstr ""

#: ../../docs/contributing/documentation/building_the_manual.rst:79
msgid "Change directory into the docs repo:"
msgstr ""

#: ../../docs/contributing/documentation/building_the_manual.rst:85
msgid "Install the required packages:"
msgstr ""

#: ../../docs/contributing/documentation/building_the_manual.rst:91
#, fuzzy
msgid "Build the docs:"
msgstr "Kreiranje Sadržaja"

#: ../../docs/contributing/documentation/building_the_manual.rst:98
msgid ""
"On Windows, that command will run ``make.bat`` instead of GNU Make (or an "
"alternative)."
msgstr ""

#: ../../docs/contributing/documentation/building_the_manual.rst:100
msgid ""
"Alternatively, you can build the documentation by running the sphinx-build "
"program manually:"
msgstr ""

#: ../../docs/contributing/documentation/building_the_manual.rst:106
msgid ""
"The compilation will take some time as the ``classes/`` folder contains "
"hundreds of files. See :ref:`doc_building_the_manual:performance`."
msgstr ""

#: ../../docs/contributing/documentation/building_the_manual.rst:109
msgid ""
"You can then browse the documentation by opening ``_build/html/index.html`` "
"in your web browser."
msgstr ""

#: ../../docs/contributing/documentation/building_the_manual.rst:113
#, fuzzy
msgid "Dealing with errors"
msgstr "Kreiranje Sadržaja"

#: ../../docs/contributing/documentation/building_the_manual.rst:115
msgid "If you run into errors, you may try the following command:"
msgstr ""

#: ../../docs/contributing/documentation/building_the_manual.rst:121
msgid ""
"If you get a ``MemoryError`` or ``EOFError``, you can remove the ``classes/"
"`` folder and run ``make`` again. This will drop the class references from "
"the final HTML documentation but will keep the rest intact."
msgstr ""

#: ../../docs/contributing/documentation/building_the_manual.rst:127
msgid ""
"If you delete the ``classes/`` folder, do not use ``git add .`` when working "
"on a pull request or the whole ``classes/`` folder will be removed when you "
"commit. See `#3157 <https://github.com/godotengine/godot-docs/"
"issues/3157>`__ for more detail."
msgstr ""

#: ../../docs/contributing/documentation/building_the_manual.rst:134
#, fuzzy
msgid "Hints for performance"
msgstr "Kreiranje Sadržaja"

#: ../../docs/contributing/documentation/building_the_manual.rst:137
msgid "RAM usage"
msgstr ""

#: ../../docs/contributing/documentation/building_the_manual.rst:139
msgid ""
"Building the documentation requires at least 8 GB of RAM to run without disk "
"swapping, which slows it down. If you have at least 16 GB of RAM, you can "
"speed up compilation by running:"
msgstr ""

#: ../../docs/contributing/documentation/building_the_manual.rst:157
msgid ""
"You can use ``-j auto`` to use all available CPU threads, but this can use a "
"lot of RAM if you have a lot of CPU threads. For instance, on a system with "
"32 CPU threads, ``-j auto`` (which corresponds to ``-j 32`` here) can "
"require 20+ GB of RAM for Sphinx alone."
msgstr ""

#: ../../docs/contributing/documentation/building_the_manual.rst:163
msgid "Specifying a list of files"
msgstr ""

#: ../../docs/contributing/documentation/building_the_manual.rst:165
msgid ""
"You can specify a list of files to build, which can greatly speed up "
"compilation:"
msgstr ""

#: ../../docs/contributing/documentation/updating_the_class_reference.rst:4
msgid "Contributing to the class reference"
msgstr ""

#: ../../docs/contributing/documentation/updating_the_class_reference.rst:8
msgid ""
"The :ref:`Class reference <doc_class_reference>` is a set of articles "
"describing the public API of the engine. This includes descriptions for "
"various classes, methods, properties, and global objects, available for "
"scripting. The class reference is available online, from the documentation "
"sidebar, and in the Godot editor, from the help menu."
msgstr ""

#: ../../docs/contributing/documentation/updating_the_class_reference.rst:14
msgid ""
"As the engine grows and features are added or modified, some parts of the "
"class reference become obsolete and new descriptions and examples need to be "
"added. While developers are encouraged to document all of their work in the "
"class reference when submitting a pull request, we can't expect everyone to "
"be able to write high quality documentation, so there is always work for "
"contributors like you to polish existing and create missing reference "
"material."
msgstr ""

#: ../../docs/contributing/documentation/updating_the_class_reference.rst:21
msgid "The source of the class reference"
msgstr ""

#: ../../docs/contributing/documentation/updating_the_class_reference.rst:23
msgid ""
"As the class reference is available in two places, online and in the editor, "
"we need to take care to keep things in sync. To achieve this the `main Godot "
"repository <https://github.com/godotengine/godot/>`_ is picked as the source "
"of truth, and the documentation for the class reference is tracked there."
msgstr ""

#: ../../docs/contributing/documentation/updating_the_class_reference.rst:29
msgid ""
"You should **not** edit ``.rst`` files in the ``classes/`` folder of the "
"`documentation repository <https://github.com/godotengine/godot-docs/>`_. "
"These files are generated automatically and are synced manually by project "
"maintainers. Read further to learn how to correctly edit the class reference."
msgstr ""

#: ../../docs/contributing/documentation/updating_the_class_reference.rst:34
msgid ""
"In the main repository the class reference is stored in XML files, one for "
"each exposed class or global object. The majority of these files is located "
"in `doc/classes/ <https://github.com/godotengine/godot/tree/master/doc/"
"classes>`_, but some modules contain their own documentation as well. You "
"will find it in the ``modules/<module_name>/doc_classes/`` directory. To "
"learn more about editing XML files refer to :ref:"
"`doc_class_reference_primer`."
msgstr ""

#: ../../docs/contributing/documentation/updating_the_class_reference.rst:42
msgid ""
"For details on Git usage and the pull request workflow, please refer to the :"
"ref:`doc_pr_workflow` page."
msgstr ""

#: ../../docs/contributing/documentation/updating_the_class_reference.rst:45
msgid ""
"If you want to translate the class reference from English to another "
"language, see :ref:`doc_editor_and_docs_localization`. This guide is also "
"available as a `video tutorial on YouTube <https://www.youtube.com/watch?"
"v=5jeHXxeX-JY>`_."
msgstr ""

#: ../../docs/contributing/documentation/updating_the_class_reference.rst:50
msgid ""
"**Important:** If you plan to make large changes, you should create an issue "
"on the `godot-docs repository <https://github.com/godotengine/godot-docs/>`_ "
"or comment on an existing issue. Doing so lets others know you're already "
"taking care of a given class."
msgstr ""

#: ../../docs/contributing/documentation/updating_the_class_reference.rst:56
msgid "What to contribute"
msgstr ""

#: ../../docs/contributing/documentation/updating_the_class_reference.rst:58
msgid ""
"The natural place to start contributing is the classes that you are most "
"familiar with. This ensures that the added description will be based on "
"experience and the necessary know-how, not just the name of a method or a "
"property. We advise not to add low effort descriptions, no matter how "
"appealing it may look. Such descriptions obscure the need for documentation "
"and are hard to identify automatically."
msgstr ""

#: ../../docs/contributing/documentation/updating_the_class_reference.rst:66
msgid ""
"Following this principle is important and allows us to create tools for "
"contributors. Such as the class reference's `completion status tracker "
"<https://godotengine.github.io/doc-status/>`_. You can use it to quickly "
"find documentation pages missing descriptions."
msgstr ""

#: ../../docs/contributing/documentation/updating_the_class_reference.rst:70
msgid ""
"If you decide to document a class, but don't know what a particular method "
"does, don't worry. Leave it for now, and list the methods you skipped when "
"you open a pull request with your changes. Another writer will take care of "
"it."
msgstr ""

#: ../../docs/contributing/documentation/updating_the_class_reference.rst:74
msgid ""
"You can still look at the methods' implementation in Godot's source code on "
"GitHub. If you have doubts, feel free to ask on the `Q&A website <https://"
"ask.godotengine.org/>`_ and `Godot Contributors Chat <https://chat."
"godotengine.org/>`_."
msgstr ""

#: ../../docs/contributing/documentation/updating_the_class_reference.rst:80
msgid ""
"Unless you make minor changes, like fixing a typo, we do not recommend using "
"the GitHub web editor to edit the class reference's XML files. It lacks "
"features to edit XML well, like keeping indentations consistent, and it does "
"not allow amending commits based on reviews."
msgstr ""

#: ../../docs/contributing/documentation/updating_the_class_reference.rst:85
msgid ""
"It also doesn't allow you to test your changes in the engine or with "
"validation scripts as described in :ref:`doc_class_reference_editing_xml`."
msgstr ""

#: ../../docs/contributing/documentation/updating_the_class_reference.rst:90
msgid "Updating class reference when working on the engine"
msgstr ""

#: ../../docs/contributing/documentation/updating_the_class_reference.rst:92
msgid ""
"When you create a new class or modify an existing engine's API, you need to "
"re-generate the XML files in ``doc/classes/``."
msgstr ""

#: ../../docs/contributing/documentation/updating_the_class_reference.rst:95
msgid ""
"To do so, you first need to compile Godot. See the :ref:"
"`doc_introduction_to_the_buildsystem` page to learn how. Then, execute the "
"compiled Godot binary from the Godot root directory with the ``--doctool`` "
"option. For example, if you're on 64-bit Linux, the command might be:"
msgstr ""

#: ../../docs/contributing/documentation/updating_the_class_reference.rst:103
msgid ""
"The exact set of suffixes may be different. Carefully read through the "
"linked article to learn more about that."
msgstr ""

#: ../../docs/contributing/documentation/updating_the_class_reference.rst:106
msgid ""
"The XML files in ``doc/classes/`` should then be up-to-date with current "
"Godot Engine features. You can then check what changed using the ``git "
"diff`` command."
msgstr ""

#: ../../docs/contributing/documentation/updating_the_class_reference.rst:109
msgid ""
"Please only include changes that are relevant to your work on the API in "
"your commits. You can discard changes in other XML files using ``git "
"checkout``, but consider reporting if you notice unrelated files being "
"updated. Ideally, running this command should only bring up the changes that "
"you yourself have made."
msgstr ""

#: ../../docs/contributing/documentation/class_reference_primer.rst:4
msgid "Class reference primer"
msgstr ""

#: ../../docs/contributing/documentation/class_reference_primer.rst:6
msgid ""
"This page explains how to write the class reference. You will learn where to "
"write new descriptions for the classes, methods, and properties for Godot's "
"built-in node types."
msgstr ""

#: ../../docs/contributing/documentation/class_reference_primer.rst:12
msgid ""
"To learn to submit your changes to the Godot project using the Git version "
"control system, see :ref:`doc_updating_the_class_reference`."
msgstr ""

#: ../../docs/contributing/documentation/class_reference_primer.rst:15
msgid ""
"The reference for each class is contained in an XML file like the one below:"
msgstr ""

#: ../../docs/contributing/documentation/class_reference_primer.rst:65
msgid ""
"It starts with brief and long descriptions. In the generated docs, the brief "
"description is always at the top of the page, while the long description "
"lies below the list of methods, variables, and constants. You can find "
"methods, member variables, constants, and signals in separate XML nodes."
msgstr ""

#: ../../docs/contributing/documentation/class_reference_primer.rst:70
msgid ""
"For each, you want to learn how they work in Godot's source code. Then, fill "
"their documentation by completing or improving the text in these tags:"
msgstr ""

#: ../../docs/contributing/documentation/class_reference_primer.rst:73
msgid "`<brief_description>`"
msgstr ""

#: ../../docs/contributing/documentation/class_reference_primer.rst:74
#, fuzzy
msgid "`<description>`"
msgstr "Uvod"

#: ../../docs/contributing/documentation/class_reference_primer.rst:75
#: ../../docs/contributing/documentation/class_reference_primer.rst:80
msgid "`<constant>`"
msgstr ""

#: ../../docs/contributing/documentation/class_reference_primer.rst:76
msgid ""
"`<method>` (in its `<description>` tag; return types and arguments don't "
"take separate documentation strings)"
msgstr ""

#: ../../docs/contributing/documentation/class_reference_primer.rst:78
msgid "`<member>`"
msgstr ""

#: ../../docs/contributing/documentation/class_reference_primer.rst:79
msgid ""
"`<signal>` (in its `<description>` tag; arguments don't take separate "
"documentation strings)"
msgstr ""

#: ../../docs/contributing/documentation/class_reference_primer.rst:82
msgid ""
"Write in a clear and simple language. Always follow the :ref:`writing "
"guidelines <doc_docs_writing_guidelines>` to keep your descriptions short "
"and easy to read. **Do not leave empty lines** in the descriptions: each "
"line in the XML file will result in a new paragraph, even if it is empty."
msgstr ""

#: ../../docs/contributing/documentation/class_reference_primer.rst:90
msgid "How to edit class XML"
msgstr ""

#: ../../docs/contributing/documentation/class_reference_primer.rst:92
msgid ""
"Edit the file for your chosen class in ``doc/classes/`` to update the class "
"reference. The folder contains an XML file for each class. The XML lists the "
"constants and methods you will find in the class reference. Godot generates "
"and updates the XML automatically."
msgstr ""

#: ../../docs/contributing/documentation/class_reference_primer.rst:97
msgid ""
"For some modules in the engine's source code, you'll find the XML files in "
"the ``modules/<module_name>/doc_classes/`` directory instead."
msgstr ""

#: ../../docs/contributing/documentation/class_reference_primer.rst:100
msgid ""
"Edit it using your favorite text editor. If you use a code editor, make sure "
"that it doesn't change the indent style: you should use tabs for the XML and "
"four spaces inside BBCode-style blocks. More on that below."
msgstr ""

#: ../../docs/contributing/documentation/class_reference_primer.rst:104
msgid ""
"To check that the modifications you've made are correct in the generated "
"documentation, navigate to the ``doc/`` folder and run the command ``make "
"rst``. This will convert the XML files to the online documentation's format "
"and output errors if anything's wrong."
msgstr ""

#: ../../docs/contributing/documentation/class_reference_primer.rst:109
msgid ""
"Alternatively, you can build Godot and open the modified page in the built-"
"in code reference. To learn how to compile the engine, read the :ref:"
"`compilation guide <toc-devel-compiling>`."
msgstr ""

#: ../../docs/contributing/documentation/class_reference_primer.rst:113
msgid ""
"We recommend using a code editor that supports XML files like Vim, Atom, "
"Visual Studio Code, Notepad++, or another to comfortably edit the file. You "
"can also use their search feature to find classes and properties quickly."
msgstr ""

#: ../../docs/contributing/documentation/class_reference_primer.rst:119
msgid ""
"If you use Visual Studio Code, you can install the `vscode-xml extension "
"<https://marketplace.visualstudio.com/items?itemName=redhat.vscode-xml>`__ "
"to get linting for class reference XML files."
msgstr ""

#: ../../docs/contributing/documentation/class_reference_primer.rst:126
msgid "Improve formatting with BBCode style tags"
msgstr ""

#: ../../docs/contributing/documentation/class_reference_primer.rst:128
msgid ""
"Godot's XML class reference supports BBCode-like tags for linking as well as "
"formatting text and code. In the tables below you can find the available "
"tags, usage examples and the results after conversion to reStructuredText."
msgstr ""

#: ../../docs/contributing/documentation/class_reference_primer.rst:132
msgid "Linking"
msgstr ""

#: ../../docs/contributing/documentation/class_reference_primer.rst:170
#, fuzzy
msgid "Formatting text"
msgstr "Kreiranje Sadržaja"

#: ../../docs/contributing/documentation/class_reference_primer.rst:192
#, fuzzy
msgid "Formatting code"
msgstr "Kreiranje Sadržaja"

#: ../../docs/contributing/documentation/class_reference_primer.rst:0
msgid "``[codeblocks]`` ``[/codeblocks]``"
msgstr ""

#: ../../docs/contributing/documentation/class_reference_primer.rst:0
msgid "Codeblock for multiple languages"
msgstr ""

#: ../../docs/contributing/documentation/class_reference_primer.rst:0
msgid "``[gdscript]`` ``[/gdscript]``"
msgstr ""

#: ../../docs/contributing/documentation/class_reference_primer.rst:0
msgid "GDScript codeblock tab in codeblocks"
msgstr ""

#: ../../docs/contributing/documentation/class_reference_primer.rst:0
msgid "``[csharp]`` ``[/csharp]``"
msgstr ""

#: ../../docs/contributing/documentation/class_reference_primer.rst:0
msgid "C# codeblock tab in codeblocks"
msgstr ""

#: ../../docs/contributing/documentation/class_reference_primer.rst:220
msgid ""
"Use ``[codeblock]`` for pre-formatted code blocks. Inside ``[codeblock]``, "
"always use **four spaces** for indentation. The parser will delete tabs."
msgstr ""

#: ../../docs/contributing/documentation/class_reference_primer.rst:233
msgid "Will display as:"
msgstr ""

#: ../../docs/contributing/documentation/class_reference_primer.rst:241
msgid ""
"If you need to have different code version in GDScript and C#, use "
"``[codeblocks]`` instead. If you use ``[codeblocks]``, you also need to have "
"at least one of the language-specific tags, ``[gdscript]`` and ``[csharp]``."
msgstr ""

#: ../../docs/contributing/documentation/class_reference_primer.rst:245
msgid ""
"Always write GDScript code examples first! You can use this `experimental "
"code translation tool <https://github.com/HaSa1002/codetranslator>`_ to "
"speed up your workflow."
msgstr ""

#: ../../docs/contributing/documentation/class_reference_primer.rst:266
msgid "The above will display as:"
msgstr ""

#: ../../docs/contributing/documentation/class_reference_primer.rst:283
msgid ""
"To denote important information, add a paragraph starting with \"[b]Note:[/"
"b]\" at the end of the description:"
msgstr ""

#: ../../docs/contributing/documentation/class_reference_primer.rst:290
msgid ""
"To denote crucial information that could cause security issues or loss of "
"data if not followed carefully, add a paragraph starting with \"[b]Warning:[/"
"b]\" at the end of the description:"
msgstr ""

#: ../../docs/contributing/documentation/class_reference_primer.rst:298
msgid ""
"For deprecated properties, add a paragraph starting with \"[i]Deprecated.[/"
"i]\". Notice the use of italics instead of bold:"
msgstr ""

#: ../../docs/contributing/documentation/class_reference_primer.rst:305
msgid ""
"In all the paragraphs described above, make sure the punctuation is part of "
"the BBCode tags for consistency."
msgstr ""

#: ../../docs/contributing/documentation/editor_and_docs_localization.rst:4
msgid "Editor and documentation localization"
msgstr ""

#: ../../docs/contributing/documentation/editor_and_docs_localization.rst:8
msgid ""
"Godot aims to make game development available to everyone, including people "
"who may not know or be comfortable with English. Therefore, we do our best "
"to make the most important resources available in many languages, thanks to "
"the translation effort of the community."
msgstr ""

#: ../../docs/contributing/documentation/editor_and_docs_localization.rst:13
msgid "These resources include:"
msgstr ""

#: ../../docs/contributing/documentation/editor_and_docs_localization.rst:15
msgid ""
"The `Godot editor's interface <https://hosted.weblate.org/projects/godot-"
"engine/godot/>`__ (ca. 15,000 words)."
msgstr ""

#: ../../docs/contributing/documentation/editor_and_docs_localization.rst:17
msgid ""
"The `online documentation <https://hosted.weblate.org/projects/godot-engine/"
"godot-docs/>`__ (editor manual and tutorials, ca. 300,000 words)."
msgstr ""

#: ../../docs/contributing/documentation/editor_and_docs_localization.rst:19
msgid ""
"The `class reference <https://hosted.weblate.org/projects/godot-engine/godot-"
"class-reference/>`__, available both online and in the editor (ca. 200,000 "
"words)."
msgstr ""

#: ../../docs/contributing/documentation/editor_and_docs_localization.rst:22
msgid ""
"To manage translations, we use the GNU gettext file format (``PO`` files), "
"and the open source `Weblate <https://weblate.org>`__ web-based localization "
"platform, which allows easy collaboration of many contributors to complete "
"the translation for the various components, and keep them up to date. Click "
"the bold links above to access each resource on Weblate."
msgstr ""

#: ../../docs/contributing/documentation/editor_and_docs_localization.rst:28
msgid ""
"This page gives an overview of the general translation workflow on Weblate, "
"and some resource-specific instructions on e.g. how to handle some keywords "
"or the localization of images."
msgstr ""

#: ../../docs/contributing/documentation/editor_and_docs_localization.rst:34
msgid ""
"Translating all the official Godot content is a massive undertaking, so we "
"advise prioritizing the resources as they are listed above: first the editor "
"interface, then the online documentation, and eventually the class reference "
"if there are enough translators to keep up with updates."
msgstr ""

#: ../../docs/contributing/documentation/editor_and_docs_localization.rst:40
msgid "Using Weblate for translations"
msgstr ""

#: ../../docs/contributing/documentation/editor_and_docs_localization.rst:42
msgid ""
"While our translations eventually reside in the Git repositories of the "
"Godot engine and its documentation, all translation updates are handled "
"through Weblate, and thus direct pull requests to the Git repositories are "
"not accepted. Translations are synced manually between Weblate and the Godot "
"repositories by maintainers."
msgstr ""

#: ../../docs/contributing/documentation/editor_and_docs_localization.rst:48
msgid ""
"You should therefore `register on Weblate <https://hosted.weblate.org/"
"accounts/register/>`__ to contribute to Godot's translations."
msgstr ""

#: ../../docs/contributing/documentation/editor_and_docs_localization.rst:51
msgid ""
"Once signed in, browse to the Godot resource which you want to contribute to "
"(in this page we will use the `editor translation <https://hosted.weblate."
"org/projects/godot-engine/godot/>`__ as an example) to find the list of all "
"languages:"
msgstr ""

#: ../../docs/contributing/documentation/editor_and_docs_localization.rst:59
msgid ""
"Feel free to consult Weblate's own documentation on the `translation "
"workflow <https://docs.weblate.org/en/latest/user/translating.html>`__ for "
"more details."
msgstr ""

#: ../../docs/contributing/documentation/editor_and_docs_localization.rst:64
msgid "Adding a new language"
msgstr ""

#: ../../docs/contributing/documentation/editor_and_docs_localization.rst:66
msgid ""
"If your language is already listed, click on its name to access the "
"overview, and skip the rest of this section."
msgstr ""

#: ../../docs/contributing/documentation/editor_and_docs_localization.rst:69
msgid ""
"If your language is not listed, scroll to the bottom of the list of "
"languages and click the \"Start new translation\" button, and select the "
"language you want to translate to:"
msgstr ""

#: ../../docs/contributing/documentation/editor_and_docs_localization.rst:77
msgid ""
"If your language is spoken in several countries with only limited regional "
"variations, please consider adding it with its generic variant (e.g. ``fr`` "
"for French) instead of a regional variant (e.g. ``fr_FR`` for French "
"(France), ``fr_CA`` for French (Canada), or ``fr_DZ`` for French (Algeria))."
msgstr ""

#: ../../docs/contributing/documentation/editor_and_docs_localization.rst:82
msgid ""
"Godot has a huge amount of content to translate, so duplicating the work for "
"regional variants should only be done if the language variations are "
"significant enough. Additionally, if a translation is done with for a "
"regional variant, it will only be available automatically for users located "
"in this region (or having their system language configured for this region)."
msgstr ""

#: ../../docs/contributing/documentation/editor_and_docs_localization.rst:88
msgid ""
"When regional variations are significant enough to warrant separate "
"translations, we advise to focus on completing a generic variant first if "
"possible, then duplicate the fully completed translation for regional "
"variants and do the relevant edits. This is typically a good strategy for e."
"g. Spanish (work on ``es`` first, then duplicate it to ``es_AR``, ``es_ES``, "
"``es_MX``, etc. if necessary) or Portuguese (``pt_BR`` vs ``pt_PT``)."
msgstr ""

#: ../../docs/contributing/documentation/editor_and_docs_localization.rst:97
msgid "Translation interface"
msgstr ""

#: ../../docs/contributing/documentation/editor_and_docs_localization.rst:99
msgid ""
"Once a language has been selected, you will see an overview of the "
"translation status, including how many strings are left to translate or "
"review. Each item can be clicked and used to browse through the "
"corresponding list. You can also click the \"Translate\" button to get "
"started on the list of strings needing action."
msgstr ""

#: ../../docs/contributing/documentation/editor_and_docs_localization.rst:107
msgid ""
"After selecting a list of clicking \"Translate\", you will see the main "
"translation interface where all the work happens:"
msgstr ""

#: ../../docs/contributing/documentation/editor_and_docs_localization.rst:112
msgid "On that page, you have:"
msgstr ""

#: ../../docs/contributing/documentation/editor_and_docs_localization.rst:114
msgid ""
"A toolbar which lets you cycle through strings of the current list, change "
"to another predefined list or do a custom search, etc. There is also a "
"\"Zen\" editing mode with a simplified interface."
msgstr ""

#: ../../docs/contributing/documentation/editor_and_docs_localization.rst:117
msgid ""
"The actual string you are working on in the \"Translation\" panel. By "
"default, there should be the English source string and an edit box for your "
"language. If you are familiar with other languages, you can add them in your "
"user settings to give you more context for translation. Once you are done "
"editing the current string, press \"Save\" to confirm changes and move to "
"the next entry. Alternatively, use the \"Skip\" button to skip it. The "
"\"Needs editing\" checkbox means that the original string was updated, and "
"the translation therefore needs review to take those changes into account "
"(in PO jargon, these are so-called \"fuzzy\" strings). Such strings won't be "
"used in the translation until fixed."
msgstr ""

#: ../../docs/contributing/documentation/editor_and_docs_localization.rst:127
msgid ""
"The bottom panel has various tools which can help with the translation "
"effort, such as context from nearby strings (usually from the same editor "
"tool or documentation page, so they might use similar terms), comments from "
"other translators, machine translations, and a list of all other existing "
"translations for that string."
msgstr ""

#: ../../docs/contributing/documentation/editor_and_docs_localization.rst:132
msgid ""
"On the top right, the glossary shows terms for which an entry has been added "
"previously, and which are included in the current string. For example, if "
"you decided with fellow translators to use a specific translation for the "
"\"node\" term in Godot, you can add it to the glossary to ensure that other "
"translators use the same convention."
msgstr ""

#: ../../docs/contributing/documentation/editor_and_docs_localization.rst:137
msgid ""
"The bottom right panel includes information on the source string. The most "
"relevant item is the \"source string location\", which links you to the "
"original string on GitHub. You may need to search for the string in the page "
"to locate it and its surrounding context."
msgstr ""

#: ../../docs/contributing/documentation/editor_and_docs_localization.rst:143
#, fuzzy
msgid "Locating original content"
msgstr "Kreiranje Sadržaja"

#: ../../docs/contributing/documentation/editor_and_docs_localization.rst:145
msgid ""
"PO files are an ordered list of source strings (``msgid``) and their "
"translation (``msgstr``), and by default, Weblate will present the strings "
"in that order. It can therefore be useful to understand how the content is "
"organized in the PO files to help you locate the original content and use it "
"as a reference when translating."
msgstr ""

#: ../../docs/contributing/documentation/editor_and_docs_localization.rst:153
msgid ""
"It is primordial to use the original context as reference when translating, "
"as many words have several possible translations depending on the context. "
"Using the wrong translation can actually be detrimental to the user and make "
"things harder to understand than if they stayed in English. Using the "
"context also makes the translation effort much easier and more enjoyable, as "
"you can see directly if the translation you wrote will make sense in context."
msgstr ""

#: ../../docs/contributing/documentation/editor_and_docs_localization.rst:161
msgid ""
"The editor interface's translation template is generated by parsing all the "
"C++ source code in **alphabetical order**, so all the strings defined in a "
"given file will be grouped together. For example, if the \"source string "
"location\" indicates ``editor/code_editor.cpp``, the current string (and the "
"nearby ones) is defined in the ``editor/code_editor.cpp`` code file, and is "
"thereby related to the code editors in Godot (GDScript, shaders)."
msgstr ""

#: ../../docs/contributing/documentation/editor_and_docs_localization.rst:167
msgid ""
"The online documentation's translation template is generated from the source "
"RST files in the same order as seen in the **table of contents**, so for "
"example the first strings are from the front page of the documentation. The "
"recommended workflow is therefore to find a unique string corresponding to a "
"page that you want to translate, and then translate all the strings with the "
"same source string location while comparing with the online version of that "
"page in English. An example of source string location could be "
"``getting_started/step_by_step/nodes_and_scenes.rst`` for the page :ref:"
"`doc_nodes_and_scenes`."
msgstr ""

#: ../../docs/contributing/documentation/editor_and_docs_localization.rst:176
msgid ""
"The class reference's translation template is generated from the source XML "
"files in **alphabetical order**, which is also the same as the order of the "
"table of contents for the online version. You can therefore locate the "
"source string corresponding to the brief description of a given class to "
"find the first string to translate and all other descriptions from that "
"class should be in the subsequent strings on Weblate. For example, the "
"descriptions for the :ref:`class_Node2D` class would have the source string "
"location ``doc/classes/Node2D.xml``."
msgstr ""

#: ../../docs/contributing/documentation/editor_and_docs_localization.rst:185
msgid ""
"A handy tool to locate specific pages/classes is to use Weblate's advanced "
"search feature, and especially the \"Location strings\" query (which can "
"also be used with the ``location:`` token, e.g. ``location:nodes_and_scenes."
"rst``):"
msgstr ""

#: ../../docs/contributing/documentation/editor_and_docs_localization.rst:195
msgid ""
"When a given source string is used in multiple source locations, they will "
"all be concatenated into one. For example, the above ``location:"
"nodes_and_scenes.rst`` query would land first on the \"Introduction\" source "
"string which is used in dozens of pages, including some that come before "
"``nodes_and_scenes.rst`` in the template. Clicking the \"Next\" button then "
"brings us to the \"Scene and nodes\" title string displayed above. So it may "
"happen that a given paragraph or section title is not at the location you'd "
"expect it when reading the online version of a page."
msgstr ""

#: ../../docs/contributing/documentation/editor_and_docs_localization.rst:206
msgid "Respecting the markup syntax"
msgstr ""

#: ../../docs/contributing/documentation/editor_and_docs_localization.rst:208
msgid ""
"Each translation resource originates from a different source code format, "
"and having some notions on the markup language used for each resource is "
"important to avoid creating syntax errors in your translations."
msgstr ""

#: ../../docs/contributing/documentation/editor_and_docs_localization.rst:213
msgid "Editor interface (C++)"
msgstr ""

#: ../../docs/contributing/documentation/editor_and_docs_localization.rst:215
msgid "The editor translations originate from C++ strings, and may use:"
msgstr ""

#: ../../docs/contributing/documentation/editor_and_docs_localization.rst:217
msgid ""
"**C format specifiers** such as ``%s`` (a string) or ``%d`` (a number). "
"These specifiers are replaced by content at runtime, and should be preserved "
"and placed in your translation where necessary for it to be meaningful after "
"substitution. You may need to refer to the source string location to "
"understand what kind of content will be substituted if it's not clear from "
"the sentence. Example (``%s``  will be substituted with a file name or "
"path)::"
msgstr ""

#: ../../docs/contributing/documentation/editor_and_docs_localization.rst:230
msgid ""
"**C escape characters** such as ``\\n`` (line break) or ``\\t`` "
"(tabulation). In the Weblate editor, the ``\\n`` characters are replaced by "
"``↵`` (return) and ``\\t`` by ``↹``. Tabs are not used much, but you should "
"make sure to use line breaks in the same way as the original English string "
"(Weblate will issue a warning if you don't). Line breaks might sometimes be "
"used for vertical spacing, or manual wrapping of long lines which would "
"otherwise be too long especially in the editor translation). Example::"
msgstr ""

#: ../../docs/contributing/documentation/editor_and_docs_localization.rst:247
msgid ""
"Only logical order of the characters matters, in the right-to-left text, "
"format specifiers may be displayed as ``s%``."
msgstr ""

#: ../../docs/contributing/documentation/editor_and_docs_localization.rst:251
#, fuzzy
msgid "Online documentation (RST)"
msgstr "Organizacija dokumentacije"

#: ../../docs/contributing/documentation/editor_and_docs_localization.rst:253
msgid ""
"The documentation translations originate from reStructuredText (RST) files, "
"which also use their own markup syntax to style text, create internal and "
"external links, etc. Here are some examples::"
msgstr ""

#: ../../docs/contributing/documentation/editor_and_docs_localization.rst:295
msgid ""
"See Sphinx's `reStructured Text primer <https://www.sphinx-doc.org/en/master/"
"usage/restructuredtext/basics.html>`__ for a quick overview of the markup "
"language you may find in source strings. You may encounter especially the "
"inline markup (bold, italics, inline code) and the internal and external "
"hyperlink markup."
msgstr ""

#: ../../docs/contributing/documentation/editor_and_docs_localization.rst:301
msgid "Class reference (BBCode)"
msgstr ""

#: ../../docs/contributing/documentation/editor_and_docs_localization.rst:303
msgid ""
"The class reference is documented in the main Godot repository using XML "
"files, and with BBCode-like markup for styling and internal references."
msgstr ""

#: ../../docs/contributing/documentation/editor_and_docs_localization.rst:306
msgid ""
"Some of the tags used are from the original BBCode (e.g. ``[b]Bold[/b]`` and "
"``[i]Italics[/i]``), while others are Godot-specific and used for advanced "
"features such as inline code (e.g. ``[code]true[/code]``), linking to "
"another class (e.g. ``[Node2D]``) or to a property in a given class (e.g. "
"``[member Node2D.position]``), or for multiline code blocks. Example::"
msgstr ""

#: ../../docs/contributing/documentation/editor_and_docs_localization.rst:318
msgid ""
"In the above example, ``[code]name[/code]``, ``[code]alpha[/code]``, and "
"``[Color]`` should *not* be translated, as they refer respectively to "
"argument names and a class of the Godot API. Similarly, the contents of the "
"``[codeblock]`` should not be translated, as ``ColorN`` is a function of the "
"Godot API and ``\"red\"`` is one of the named colors it supports. At most, "
"you can translate the name of the variable which holds the result (``red "
"= ...``)."
msgstr ""

#: ../../docs/contributing/documentation/editor_and_docs_localization.rst:325
msgid ""
"Note also that in the XML, each line is a paragraph, so you should not add "
"line breaks if they are not part of the original translation."
msgstr ""

#: ../../docs/contributing/documentation/editor_and_docs_localization.rst:330
msgid ""
"See our documentation for class reference writers for the :ref:`list of "
"BBCode-like tags <doc_class_reference_bbcode>` which are used throughout the "
"class reference."
msgstr ""

#: ../../docs/contributing/documentation/editor_and_docs_localization.rst:335
msgid "Offline translation and testing"
msgstr ""

#: ../../docs/contributing/documentation/editor_and_docs_localization.rst:337
msgid ""
"While we advise using the Weblate interface to write translations, you also "
"have the possibility to download the PO file locally to translate it with "
"your preferred PO editing application, such as `Poedit <https://poedit.net/"
">`__ or `Lokalize <https://userbase.kde.org/Lokalize>`__."
msgstr ""

#: ../../docs/contributing/documentation/editor_and_docs_localization.rst:342
msgid ""
"To download the PO file locally, browse to the translation overview for your "
"language, and select the first item in the \"Files\" menu:"
msgstr ""

#: ../../docs/contributing/documentation/editor_and_docs_localization.rst:347
msgid ""
"Once you are done with a series of edits, use the \"Upload translation\" "
"item in that same menu and select your file. Choose \"Add as translation\" "
"for the file upload mode."
msgstr ""

#: ../../docs/contributing/documentation/editor_and_docs_localization.rst:353
msgid ""
"If a significant amount of time has passed between your download of the PO "
"file and the upload of the edited version, there is a risk to overwrite the "
"translations authored by other contributors in the meantime. This is why we "
"advise to use the online interface so that you always work on the latest "
"version."
msgstr ""

#: ../../docs/contributing/documentation/editor_and_docs_localization.rst:359
msgid ""
"If you want to test changes locally (especially for the editor translation), "
"you can use the downloaded PO file and :ref:`compile Godot from source <toc-"
"devel-compiling>`."
msgstr ""

#: ../../docs/contributing/documentation/editor_and_docs_localization.rst:362
msgid ""
"Rename the editor translation PO file to ``<lang>.po`` (e.g. ``eo.po`` for "
"Esperanto) and place it in the ``editor/translations/`` folder (`GitHub "
"<https://github.com/godotengine/godot/tree/master/editor/translations>`__)."
msgstr ""

#: ../../docs/contributing/documentation/editor_and_docs_localization.rst:366
msgid ""
"You can also test class reference changes the same way by renaming the PO "
"file similarly and placing it in the ``doc/translations/`` folder (`GitHub "
"<https://github.com/godotengine/godot/tree/master/doc/translations>`__)."
msgstr ""

#: ../../docs/contributing/documentation/editor_and_docs_localization.rst:371
msgid "Localizing documentation images"
msgstr ""

#: ../../docs/contributing/documentation/editor_and_docs_localization.rst:373
msgid ""
"The online documentation includes many images, which can be screenshots of "
"the Godot editor, custom-made graphs, of any other kind of visual content. "
"Some of it includes text and might thus be relevant to localize in your "
"language."
msgstr ""

#: ../../docs/contributing/documentation/editor_and_docs_localization.rst:377
msgid ""
"This part is not handled via Weblate, but directly on the `godot-docs-l10n "
"<https://github.com/godotengine/godot-docs-l10n>`_ Git repository where the "
"documentation translations are synced from Weblate."
msgstr ""

#: ../../docs/contributing/documentation/editor_and_docs_localization.rst:383
msgid ""
"The workflow is not the most straightforward and requires some knowledge of "
"Git. We plan to work on a simplified Web tool which could be used to manage "
"image localization in a convenient way, abstracting away these steps."
msgstr ""

#: ../../docs/contributing/documentation/editor_and_docs_localization.rst:387
msgid ""
"To translate an image, you should first locate it in the original English "
"documentation. To do so, browse the relevant page in the docs, e.g. :ref:"
"`doc_intro_to_the_editor_interface`. Click the \"Edit on GitHub\" link in "
"the top right corner:"
msgstr ""

#: ../../docs/contributing/documentation/editor_and_docs_localization.rst:394
msgid ""
"On GitHub, click on the image you want to translate. If relevant, click on "
"\"Download\" to download it locally and edit it with an image edition tool. "
"Note the full path to the image as it will be needed further down (here "
"``getting_started/step_by_step/img/project_manager_first_open.png``)."
msgstr ""

#: ../../docs/contributing/documentation/editor_and_docs_localization.rst:401
msgid ""
"Create your localized version of the image, either by editing the English "
"one, or by taking a screenshot of the editor with your language, if it's an "
"editor screenshot. Some images may also have source files available in SVG "
"format, so you can browse the ``img/`` folder which contains them to check "
"for that."
msgstr ""

#: ../../docs/contributing/documentation/editor_and_docs_localization.rst:406
msgid ""
"Name your localized image like the original one, but with the language code "
"added before the extension, e.g. ``project_manager_first_open.png`` would "
"become ``project_manager_first_open.fr.png`` for the French localization."
msgstr ""

#: ../../docs/contributing/documentation/editor_and_docs_localization.rst:410
msgid ""
"Finally, on godot-docs-l10n_, recreate the same folder structure as for the "
"original image in the ``images`` subfolder (`GitHub <https://github.com/"
"godotengine/godot-docs-l10n/tree/master/images>`_), and place your "
"translated image there. In our example, the end result should be ``images/"
"getting_started/step_by_step/img/project_manager_first_open.fr.png``."
msgstr ""

#: ../../docs/contributing/documentation/editor_and_docs_localization.rst:416
msgid ""
"Repeat this for other images and :ref:`make a Pull Request "
"<doc_pr_workflow>`."
msgstr ""

#: ../../docs/community/asset_library/index.rst:2
msgid "Asset Library"
msgstr ""

#: ../../docs/community/asset_library/what_is_assetlib.rst:4
msgid "About the Asset Library"
msgstr ""

#: ../../docs/community/asset_library/what_is_assetlib.rst:6
msgid ""
"The Godot Asset Library, otherwise known as the AssetLib, is a repository of "
"user-submitted Godot addons, scripts, tools, and other resources, "
"collectively referred to as assets. They're available to all Godot users for "
"download directly from within the engine, but it can also be accessed at "
"Godot's `official website <https://godotengine.org/asset-library/asset>`_."
msgstr ""

#: ../../docs/community/asset_library/what_is_assetlib.rst:11
msgid ""
"On the surface, the Asset Library might look and function similar to asset "
"stores available for other engines, such as Unity's Asset Store, or Unreal "
"Engine's Marketplace, where you can submit both freely-available assets, as "
"well as paid, commercial ones. In addition, often times such assets are "
"distributed under non-free, proprietary licenses, limiting what you can do "
"with them."
msgstr ""

#: ../../docs/community/asset_library/what_is_assetlib.rst:17
msgid ""
"The Asset Library is different - all assets are distributed free of charge, "
"and under a host of open source licenses (such as the MIT license, the GPL, "
"and the Boost Software License). This makes the AssetLib more similar to the "
"software repositories of a Linux distribution."
msgstr ""

#: ../../docs/community/asset_library/what_is_assetlib.rst:21
msgid ""
"This set of pages will cover how to use the AssetLib (both from inside "
"Godot, and on the website), how you can submit your own assets, and what the "
"guidelines for submission are."
msgstr ""

#: ../../docs/community/asset_library/what_is_assetlib.rst:24
msgid ""
"Please note that the AssetLib is relatively young - it may have various pain "
"points, bugs, and usability issues. As with all Godot projects, the code "
"repository is available on `GitHub <https://github.com/godotengine/godot-"
"asset-library>`_, where you can submit pull requests and issues, so please "
"do not hesitate to visit it!"
msgstr ""

#: ../../docs/community/asset_library/what_is_assetlib.rst:29
msgid "Types of assets"
msgstr ""

#: ../../docs/community/asset_library/what_is_assetlib.rst:31
msgid ""
"Be aware that there are, broadly, two different types of assets you can post."
msgstr ""

#: ../../docs/community/asset_library/what_is_assetlib.rst:33
msgid ""
"Assets labeled as \"Templates\", \"Projects\", or \"Demos\" appear under the "
"\"Asset Library Projects\" tab in the Godot Project Manager. These assets "
"are standalone Godot projects that can run by themselves."
msgstr ""

#: ../../docs/community/asset_library/what_is_assetlib.rst:37
msgid ""
"Other assets show up inside of the Godot editor under the \"AssetLib\" main "
"screen tab, next to \"2D\", \"3D\", and \"Script\". These assets are meant "
"to be downloaded and placed into an existing Godot project."
msgstr ""

#: ../../docs/community/asset_library/what_is_assetlib.rst:45
msgid "Can paid assets be uploaded to the asset library?"
msgstr ""

#: ../../docs/community/asset_library/what_is_assetlib.rst:47
msgid ""
"Not to the official one, though in the future, there might be other asset "
"libraries which allow it. That said, you are allowed to monetize and sell "
"Godot assets outside the Asset Library."
msgstr ""

#: ../../docs/community/asset_library/using_assetlib.rst:4
msgid "Using the Asset Library"
msgstr ""

#: ../../docs/community/asset_library/using_assetlib.rst:7
msgid "On the website"
msgstr ""

#: ../../docs/community/asset_library/using_assetlib.rst:12
msgid ""
"As mentioned before, you can access the web frontend of the Asset Library on "
"`Godot's official website <https://godotengine.org/asset-library/asset>`_. "
"This is what it looks like when you first visit it:"
msgstr ""

#: ../../docs/community/asset_library/using_assetlib.rst:18
msgid ""
"At the top, you see the **header**, which takes you to various other parts "
"of the AssetLib - at the moment, it's empty, as we are not logged in."
msgstr ""

#: ../../docs/community/asset_library/using_assetlib.rst:22
msgid "Searching"
msgstr ""

#: ../../docs/community/asset_library/using_assetlib.rst:24
msgid ""
"In the center is the **search bar + settings** section, and the **assets** "
"section below it - this lets you filter out certain kinds of assets based on "
"a host of criteria. These include the asset **category** (such as 2D tools, "
"scripts and demos), **engine version** they are intended for, **sorting "
"order** (by update date, by name, etc.) and **support level**."
msgstr ""

#: ../../docs/community/asset_library/using_assetlib.rst:30
msgid ""
"While most other filter settings should be fairly self-explanatory, it's "
"worth going over what \"support level\" means in the Asset Library. "
"Currently there are three support levels, and each asset can belong to only "
"one."
msgstr ""

#: ../../docs/community/asset_library/using_assetlib.rst:34
msgid ""
"**Official** assets are created and maintained by the official Godot Engine "
"developers. Currently, these include the official engine demos, which "
"showcase how various areas of the engine work."
msgstr ""

#: ../../docs/community/asset_library/using_assetlib.rst:38
msgid ""
"**Community** assets are submitted and maintained by the members of the "
"Godot community."
msgstr ""

#: ../../docs/community/asset_library/using_assetlib.rst:41
msgid ""
"**Testing** assets are works-in-progress, and may contain bugs and usability "
"issues. They are not recommended for use in serious projects, but you are "
"encouraged to download, test them, and submit issues to the original authors."
msgstr ""

#: ../../docs/community/asset_library/using_assetlib.rst:45
msgid ""
"You can mix and match any of the search filters and criteria, and upon "
"clicking the Search button, receive the list of all assets in the Library "
"that match them."
msgstr ""

#: ../../docs/community/asset_library/using_assetlib.rst:50
msgid ""
"Note that the search results are not updated in real-time, so you will have "
"to re-submit the search query each time you change the query settings."
msgstr ""

#: ../../docs/community/asset_library/using_assetlib.rst:54
msgid "Breakdown of an asset"
msgstr ""

#: ../../docs/community/asset_library/using_assetlib.rst:56
msgid ""
"Now let's take a look at what an asset's page looks like and what it "
"contains."
msgstr ""

#: ../../docs/community/asset_library/using_assetlib.rst:60
msgid "Asset's thumbnail/icon."
msgstr ""

#: ../../docs/community/asset_library/using_assetlib.rst:61
msgid "Asset's name."
msgstr ""

#: ../../docs/community/asset_library/using_assetlib.rst:62
msgid "Current version number of the asset."
msgstr ""

#: ../../docs/community/asset_library/using_assetlib.rst:63
msgid "Asset's category, Godot version, and support status."
msgstr ""

#: ../../docs/community/asset_library/using_assetlib.rst:64
msgid "Asset's original author/submitter."
msgstr ""

#: ../../docs/community/asset_library/using_assetlib.rst:65
msgid "The license the asset is distributed under."
msgstr ""

#: ../../docs/community/asset_library/using_assetlib.rst:66
msgid "The date of the asset's latest edit/update."
msgstr ""

#: ../../docs/community/asset_library/using_assetlib.rst:67
msgid "A textual description of the asset."
msgstr ""

#: ../../docs/community/asset_library/using_assetlib.rst:68
msgid "Links related to the asset (download link, file list, issue tracker)."
msgstr ""

#: ../../docs/community/asset_library/using_assetlib.rst:69
msgid "Images and videos showcasing the asset."
msgstr ""

#: ../../docs/community/asset_library/using_assetlib.rst:72
msgid "Registering and logging in"
msgstr ""

#: ../../docs/community/asset_library/using_assetlib.rst:74
msgid ""
"In order to upload assets to the AssetLib, you need to be logged in, and to "
"do that, you need a registered user account. In the future, this may also "
"give you access to other features, such as commenting on or rating the "
"existing assets. You do *not* need to be logged in to browse and download "
"the assets."
msgstr ""

#: ../../docs/community/asset_library/using_assetlib.rst:79
msgid "The login/registration page can be accessed from the AssetLib header."
msgstr ""

#: ../../docs/community/asset_library/using_assetlib.rst:83
msgid ""
"From here, you can register your account, which requires a valid email "
"address, a username, and a (preferably strong) password."
msgstr ""

#: ../../docs/community/asset_library/using_assetlib.rst:88
msgid "Then, you can use your username and password to log in."
msgstr ""

#: ../../docs/community/asset_library/using_assetlib.rst:92
msgid ""
"This will change the look of the AssetLib header. Now you get access to a "
"handful of new functions:"
msgstr ""

#: ../../docs/community/asset_library/using_assetlib.rst:95
msgid ""
"The feed, which shows a list of status updates on your submitted assets (and "
"possibly more in the future)."
msgstr ""

#: ../../docs/community/asset_library/using_assetlib.rst:96
msgid "A list of your uploaded assets."
msgstr ""

#: ../../docs/community/asset_library/using_assetlib.rst:97
msgid "The ability to submit new assets."
msgstr ""

#: ../../docs/community/asset_library/using_assetlib.rst:101
msgid ""
"You can learn how to submit assets to the Library, and what the asset "
"submission guidelines are, in the next part of this tutorial, :ref:"
"`doc_submitting_to_assetlib`."
msgstr ""

#: ../../docs/community/asset_library/using_assetlib.rst:107
msgid "In the editor"
msgstr ""

#: ../../docs/community/asset_library/using_assetlib.rst:111
msgid ""
"The editor will display different categories of assets depending on whether "
"you're browsing the Project Manager's **Asset Library Projects** tab or the "
"editor's **AssetLib** tab."
msgstr ""

#: ../../docs/community/asset_library/using_assetlib.rst:115
msgid ""
"The Project Manager's **Asset Library Projects** tab will only display "
"assets that are standalone projects by themselves. This is denoted on the "
"asset library with the *Templates*, *Demos* and *Projects* categories."
msgstr ""

#: ../../docs/community/asset_library/using_assetlib.rst:119
msgid ""
"The editor's **AssetLib** tab will only display assets that are *not* "
"standalone projects by themselves. In other words, it will display assets "
"from all categories except *Templates*, *Demos* and *Projects*."
msgstr ""

#: ../../docs/community/asset_library/using_assetlib.rst:123
msgid "You can also access the AssetLib directly from Godot:"
msgstr ""

#: ../../docs/community/asset_library/using_assetlib.rst:129
msgid ""
"Click on it, and Godot will fetch info about the assets from the AssetLib. "
"Once it's finished, you will see a window similar to what the AssetLib "
"website looks like, with some differences:"
msgstr ""

#: ../../docs/community/asset_library/using_assetlib.rst:135
msgid ""
"Similarly to the web version of the AssetLib, here you can search for assets "
"by category, name, and sort them by factors such as name or edit date."
msgstr ""

#: ../../docs/community/asset_library/using_assetlib.rst:138
msgid ""
"Notably, you can only fetch assets for the current version of Godot you are "
"running. Projects, Demos and Templates can be downloaded from the Project "
"Manager view of the AssetLib. Addons (tools, scripts, materials etc.) can be "
"downloaded from the in-project AssetLib and added to the current project. In "
"addition, unlike when using the web frontend, the search results are updated "
"in real-time (you do not have to press Search after every change to your "
"search query for the changes to take place)."
msgstr ""

#: ../../docs/community/asset_library/using_assetlib.rst:146
msgid ""
"In the future, you will be able to choose a different AssetLib provider to "
"fetch assets from (using the Site dropdown menu), however currently only the "
"official `Godot website <https://godotengine.org>`_ version of the AssetLib "
"is supported, as well as the version that may be running on your local "
"machine's web server (the localhost option)."
msgstr ""

#: ../../docs/community/asset_library/using_assetlib.rst:152
msgid "When you click on an asset, you will see more information about it."
msgstr ""

#: ../../docs/community/asset_library/using_assetlib.rst:156
msgid ""
"If you click on the Install button, Godot will fetch an archive of the "
"asset, and will track download progress of it at the bottom of the editor "
"window. If the download fails, you can retry it using the Retry button."
msgstr ""

#: ../../docs/community/asset_library/using_assetlib.rst:162
msgid ""
"When it finishes, you can proceed to install it using the Install button. "
"This will bring up the Package Installer window."
msgstr ""

#: ../../docs/community/asset_library/using_assetlib.rst:167
msgid ""
"Here you can see a list of all the files that will be installed. You can "
"tick off any of the files that you do not wish to install, and Godot will "
"also inform you about any problems with files that it cannot install. These "
"files will be shown in red, and hovering over them will show you a message "
"stating why it cannot be installed."
msgstr ""

#: ../../docs/community/asset_library/using_assetlib.rst:175
msgid ""
"Once you are done, you can press the Install button, which will unzip all "
"the files in the archive, and import any assets contained therein, such as "
"images or 3D models. Once this is done, you should see a message stating "
"that the Package installation is complete."
msgstr ""

#: ../../docs/community/asset_library/using_assetlib.rst:182
msgid ""
"You may also use the Import button to import asset archives obtained "
"elsewhere (such as downloading them directly from the AssetLib web "
"frontend), which will take you through the same package installation "
"procedure as with the assets downloaded directly via Godot that we just "
"covered."
msgstr ""

#: ../../docs/community/asset_library/submitting_to_assetlib.rst:4
msgid "Submitting to the Asset Library"
msgstr ""

#: ../../docs/community/asset_library/submitting_to_assetlib.rst:9
msgid ""
"This tutorial aims to serve as a guide on how you can submit your own assets "
"to the `Godot Asset Library <https://godotengine.org/asset-library/asset>`_ "
"and share them with the Godot community."
msgstr ""

#: ../../docs/community/asset_library/submitting_to_assetlib.rst:13
msgid ""
"As mentioned in the :ref:`doc_using_assetlib` document, in order to be able "
"to submit assets to the AssetLib, you need to have a registered account, and "
"be logged in."
msgstr ""

#: ../../docs/community/asset_library/submitting_to_assetlib.rst:18
msgid "Submission guidelines"
msgstr ""

#: ../../docs/community/asset_library/submitting_to_assetlib.rst:20
msgid ""
"Before submitting your asset, please ensure it follows all of the "
"requirements, and also consider following the recommendations."
msgstr ""

#: ../../docs/community/asset_library/submitting_to_assetlib.rst:26
msgid ""
"Generally speaking, most assets people submit to the asset library are "
"accepted. However, in order for your asset to be accepted, there are a few "
"requirements your asset needs to meet to be approved."
msgstr ""

#: ../../docs/community/asset_library/submitting_to_assetlib.rst:30
msgid ""
"The asset must **work**. If the asset doesn't run or otherwise doesn't work "
"in the specified Godot version, then it will be rejected."
msgstr ""

#: ../../docs/community/asset_library/submitting_to_assetlib.rst:33
msgid ""
"The asset must have a proper **.gitignore** file. It's important to keep "
"redundant data out of the repository. `Here's a template. <https://raw."
"githubusercontent.com/aaronfranke/gitignore/godot/Godot.gitignore>`_"
msgstr ""

#: ../../docs/community/asset_library/submitting_to_assetlib.rst:37
msgid ""
"No **submodules**, or any submodules must be non-essential. GitHub does not "
"include submodules in the downloaded ZIP file, so if the asset needs the "
"contents of the submodule, your asset won't work."
msgstr ""

#: ../../docs/community/asset_library/submitting_to_assetlib.rst:41
msgid ""
"The **license** needs to be correct. The license listed on the asset library "
"must match the license in the repository. The repo MUST have a license file, "
"called either \"LICENSE\" or \"LICENSE.md\". This file must contain the "
"license text itself and a copyright statement that includes the year(s) and "
"copyright holder."
msgstr ""

#: ../../docs/community/asset_library/submitting_to_assetlib.rst:47
msgid ""
"Use proper **English** for the name and description of your asset. This "
"includes using correct capitalization, and using full sentences in the "
"description. You can also include other languages, but there should at least "
"be an English version."
msgstr ""

#: ../../docs/community/asset_library/submitting_to_assetlib.rst:52
msgid ""
"The icon link must be a **direct link**. For icons hosted on GitHub, the "
"link must start with \"raw.githubusercontent.com\", not \"github.com\"."
msgstr ""

#: ../../docs/community/asset_library/submitting_to_assetlib.rst:56
msgid "Recommendations"
msgstr ""

#: ../../docs/community/asset_library/submitting_to_assetlib.rst:58
msgid ""
"These things are not required for your asset to be approved, but if you "
"follow these recommendations, you can help make the asset library a better "
"place for all users."
msgstr ""

#: ../../docs/community/asset_library/submitting_to_assetlib.rst:62
msgid ""
"When creating non-project assets, it is common practice to place your files "
"inside of an **addons/asset_name/** folder. Do this to avoid having your "
"files clash with other assets, or with the files of users installing your "
"asset. This folder will **not** be automatically generated when a user "
"installs your asset."
msgstr ""

#: ../../docs/community/asset_library/submitting_to_assetlib.rst:67
msgid ""
"Fix or suppress all script **warnings**. The warning system is there to help "
"identify issues with your code, but people using your asset don't need to "
"see them."
msgstr ""

#: ../../docs/community/asset_library/submitting_to_assetlib.rst:71
msgid ""
"Make your code conform to the official **style guides**. Having a consistent "
"style helps other people read your code, and it also helps if other people "
"wish to contribute to your asset. See: the :ref:`doc_gdscript_styleguide` or "
"the :ref:`doc_c_sharp_styleguide`."
msgstr ""

#: ../../docs/community/asset_library/submitting_to_assetlib.rst:76
msgid ""
"If you have screenshots in your repo, place them in their own subfolder and "
"add an empty **.gdignore** file in the same folder (note: **gd**, not "
"**git**). This prevents Godot from importing your screenshots. On Windows, "
"open a command prompt in the project folder and run ``type nul > .gdignore`` "
"to create a file whose name starts with a period."
msgstr ""

#: ../../docs/community/asset_library/submitting_to_assetlib.rst:82
msgid ""
"If your asset is a library for working with other files, consider including "
"**example files** in the asset."
msgstr ""

#: ../../docs/community/asset_library/submitting_to_assetlib.rst:85
msgid ""
"Consider adding a **.gitattributes** file to your repo. This file allows "
"giving extra instructions to Git, such as specifying line endings and "
"listing files not required for your asset to function with the ``export-"
"ignore`` directive. This directive removes such files from the resulting ZIP "
"file, preventing them from being downloaded by the asset library users. "
"These are common examples of **.gitattributes**:"
msgstr ""

#: ../../docs/community/asset_library/submitting_to_assetlib.rst:94
#, fuzzy
msgid "Projects / Templates"
msgstr "Kreiranje Sadržaja"

#: ../../docs/community/asset_library/submitting_to_assetlib.rst:101
msgid "Addons / Asset Packs"
msgstr ""

#: ../../docs/community/asset_library/submitting_to_assetlib.rst:113
msgid ""
"If you are submitting a plugin, add a **copy** of your license and readme to "
"the plugin folder itself. This is the folder that users are guaranteed to "
"keep with their project, so a copy ensures they always have those files "
"handy (and helps them fulfill your licensing terms)."
msgstr ""

#: ../../docs/community/asset_library/submitting_to_assetlib.rst:118
msgid ""
"While the asset library allows more than just GitHub, consider hosting your "
"asset's source code on **GitHub**. Other services may not work reliably, and "
"a lack of familiarity can be a barrier to contributors."
msgstr ""

#: ../../docs/community/asset_library/submitting_to_assetlib.rst:123
msgid "Submitting"
msgstr ""

#: ../../docs/community/asset_library/submitting_to_assetlib.rst:125
msgid ""
"Once you are logged in, you will be able to head over to the \"Submit "
"Assets\" page of the AssetLib, which will look like this:"
msgstr ""

#: ../../docs/community/asset_library/submitting_to_assetlib.rst:130
msgid ""
"While it may look like a lot (and there is more as you scroll down), each "
"field is described in terms of what you should put in. We will nonetheless "
"go over what is required in the submission form here as well."
msgstr ""

#: ../../docs/community/asset_library/submitting_to_assetlib.rst:135
msgid "**Asset Name**:"
msgstr ""

#: ../../docs/community/asset_library/submitting_to_assetlib.rst:135
msgid ""
"The name of your asset. Should be a unique, descriptive title of what your "
"asset is."
msgstr ""

#: ../../docs/community/asset_library/submitting_to_assetlib.rst:141
msgid "**Category**:"
msgstr ""

#: ../../docs/community/asset_library/submitting_to_assetlib.rst:138
msgid ""
"The category that your asset belongs to, and will be shown in search "
"results. The category is split into **Addons** and **Projects**. In-editor, "
"assets of the Project type (Templates, Demos, Projects) only show up when "
"viewing the AssetLib from the Project Manager, while assets of the Addon "
"type will only be visible from inside a project."
msgstr ""

#: ../../docs/community/asset_library/submitting_to_assetlib.rst:147
msgid "**Godot version**:"
msgstr ""

#: ../../docs/community/asset_library/submitting_to_assetlib.rst:144
msgid ""
"The version of the engine that the asset works with. Currently, it's not "
"possible to have a single asset entry contain downloads for multiple engine "
"versions, so you may need to re-submit the asset multiple times, with an "
"entry for each Godot version it supports. This is particularly important "
"when dealing with major versions of the engine, such as Godot 2.x and Godot "
"3.x."
msgstr ""

#: ../../docs/community/asset_library/submitting_to_assetlib.rst:154
msgid "**Version**:"
msgstr ""

#: ../../docs/community/asset_library/submitting_to_assetlib.rst:150
msgid ""
"The version number of the asset. While you are free to choose and use any "
"versioning scheme that you like, you may want to look into something such as "
"`SemVer <https://semver.org>`_ if you want your asset's versioning scheme to "
"be clear and consistent. Note that there is also an internal version number, "
"incremented every time the asset download URL is changed or updated."
msgstr ""

#: ../../docs/community/asset_library/submitting_to_assetlib.rst:159
msgid "**Repository host**:"
msgstr ""

#: ../../docs/community/asset_library/submitting_to_assetlib.rst:157
msgid ""
"Assets uploaded to the AssetLib are not hosted on it directly. Instead, they "
"point to repositories hosted on third-party Git providers, such as GitHub, "
"GitLab or Bitbucket. This is where you choose which provider your asset "
"uses, so the site can compute the final download link."
msgstr ""

#: ../../docs/community/asset_library/submitting_to_assetlib.rst:162
msgid "**Repository URL**:"
msgstr ""

#: ../../docs/community/asset_library/submitting_to_assetlib.rst:162
msgid ""
"The URL to your asset's files/webpage. This will vary based on your choice "
"of provider, but it should look similar to `https://github.com/<user>/"
"<project>`."
msgstr ""

#: ../../docs/community/asset_library/submitting_to_assetlib.rst:167
msgid "**Issues URL**:"
msgstr ""

#: ../../docs/community/asset_library/submitting_to_assetlib.rst:165
msgid ""
"The URL to your asset's issue tracker. Again, this will differ from "
"repository host to repository host, but will likely look similar to `https://"
"github.com/<user>/<project>/issues`. You may leave this field empty if you "
"use your provider's issue tracker, and it's part of the same repository."
msgstr ""

#: ../../docs/community/asset_library/submitting_to_assetlib.rst:171
msgid "**Download Commit**:"
msgstr ""

#: ../../docs/community/asset_library/submitting_to_assetlib.rst:170
msgid ""
"The commit of the asset. For example, "
"`b1d3172f89b86e52465a74f63a74ac84c491d3e1`. The site computes the actual "
"download URL from this."
msgstr ""

#: ../../docs/community/asset_library/submitting_to_assetlib.rst:179
msgid "**Icon URL**:"
msgstr ""

#: ../../docs/community/asset_library/submitting_to_assetlib.rst:174
msgid ""
"The URL to your asset's icon (which will be used as a thumbnail in the "
"AssetLib search results and on the asset's page). Should be an image in "
"either the PNG or JPG format."
msgstr ""

#: ../../docs/community/asset_library/submitting_to_assetlib.rst:178
msgid ""
"The **icon** must be square (1:1 aspect ratio). It should have a minimum "
"resolution of 128×128 pixels."
msgstr ""

#: ../../docs/community/asset_library/submitting_to_assetlib.rst:184
msgid "**License**:"
msgstr ""

#: ../../docs/community/asset_library/submitting_to_assetlib.rst:182
msgid ""
"The license under which you are distributing the asset. The list includes a "
"variety of free and open source software licenses, such as GPL (v2 and v3), "
"MIT, BSD and Boost Software License. You can visit `OpenSource.org <https://"
"opensource.org>`_ for a detailed description of each of the listed licenses."
msgstr ""

#: ../../docs/community/asset_library/submitting_to_assetlib.rst:190
msgid "**Description**:"
msgstr ""

#: ../../docs/community/asset_library/submitting_to_assetlib.rst:187
msgid ""
"Finally, you can use the Description field for a textual overview of your "
"asset, its features and behavior, a changelog, et cetera. In the future, "
"formatting with Markdown will be supported, but currently, your only option "
"is plain text."
msgstr ""

#: ../../docs/community/asset_library/submitting_to_assetlib.rst:192
msgid ""
"You may also include up to three video and/or image previews, which will be "
"shown at the bottom of the asset page. Use the \"Enable\" checkbox on each "
"of the preview submission boxes to enable them."
msgstr ""

#: ../../docs/community/asset_library/submitting_to_assetlib.rst:196
msgid "**Type**:"
msgstr ""

#: ../../docs/community/asset_library/submitting_to_assetlib.rst:197
msgid "Either an image, or a video."
msgstr ""

#: ../../docs/community/asset_library/submitting_to_assetlib.rst:198
msgid "**Image/YouTube URL**:"
msgstr ""

#: ../../docs/community/asset_library/submitting_to_assetlib.rst:199
msgid "Either a link to the image, or to a video, hosted on YouTube."
msgstr ""

#: ../../docs/community/asset_library/submitting_to_assetlib.rst:203
msgid "**Thumbnail URL**:"
msgstr ""

#: ../../docs/community/asset_library/submitting_to_assetlib.rst:201
msgid ""
"A URL to an image that will be used as a thumbnail for the preview. This "
"option will be removed eventually, and thumbnails will be automatically "
"computed instead."
msgstr ""

#: ../../docs/community/asset_library/submitting_to_assetlib.rst:205
msgid ""
"Once you are done, press \"Submit\". Your asset will be entered into the "
"review queue. You can check all assets currently pending a review `here "
"<https://godotengine.org/asset-library/asset/edit?&asset=-1>`_ . The "
"approval process is manual and may take up to a few days for your asset to "
"be accepted (or rejected), so please be patient!"
msgstr ""

#: ../../docs/community/asset_library/submitting_to_assetlib.rst:212
msgid ""
"You may have some luck accelerating the approval process by messaging the "
"moderators and AssetLib reviewers on the `Godot Contributors Chat <https://"
"chat.godotengine.org/>`_, or the official Discord server."
msgstr ""

#: ../../docs/community/asset_library/submitting_to_assetlib.rst:216
msgid ""
"You will be informed when your asset is reviewed. If it was rejected, you "
"will be told why that may have been, and you will be able to submit it again "
"with the appropriate changes."
msgstr ""

#: ../../docs/community/channels.rst:4
#, fuzzy
msgid "Community channels"
msgstr "Zajednica"

#: ../../docs/community/channels.rst:6
msgid ""
"So, where is the Godot community and where can you ask questions and get "
"help?"
msgstr ""

#: ../../docs/community/channels.rst:8
msgid ""
"Note that some of these channels are run and moderated by members of the "
"Godot community or third parties."
msgstr ""

#: ../../docs/community/channels.rst:10
#, fuzzy
msgid ""
"A brief overview over these and other channels is also available on the "
"`Godot website <https://godotengine.org/community>`_."
msgstr ""
"Takođe pogledajte `licencu na Godot sajtu <https://godotengine.org/"
"license>`_."

#: ../../docs/community/channels.rst:13
msgid "Forums"
msgstr ""

#: ../../docs/community/channels.rst:15
msgid "`Official Godot Forum <https://forum.godotengine.org/>`_"
msgstr ""

#: ../../docs/community/channels.rst:16
msgid "`Community Forum <https://godotforums.org/>`_"
msgstr ""

#: ../../docs/community/channels.rst:19
msgid "Chats"
msgstr ""

#: ../../docs/community/channels.rst:21
msgid "`Godot Contributors Chat <https://chat.godotengine.org/>`_"
msgstr ""

#: ../../docs/community/channels.rst:22
msgid "`Discord <https://discord.gg/4JBkykG>`_"
msgstr ""

#: ../../docs/community/channels.rst:23
msgid ""
"`Matrix (IRC compatible) <https://matrix.to/#/#godotengine:matrix.org>`_"
msgstr ""

#: ../../docs/community/channels.rst:24
msgid ""
"`IRC (#godotengine on Libera.Chat) <https://web.libera.chat/?"
"channels=#godotengine>`_"
msgstr ""

#: ../../docs/community/channels.rst:28
msgid ""
"As of January 2021, core developer chat has moved to the Godot Contributors "
"Chat platform listed above. IRC is less active. Please stick around to get "
"an answer, as it may take several hours for someone to see and answer your "
"questions."
msgstr ""

#: ../../docs/community/channels.rst:33
msgid "Social networks and other sites"
msgstr ""

#: ../../docs/community/channels.rst:35
msgid "`GitHub <https://github.com/godotengine/>`_"
msgstr ""

#: ../../docs/community/channels.rst:36
msgid "`Facebook group <https://www.facebook.com/groups/godotengine/>`_"
msgstr ""

#: ../../docs/community/channels.rst:37
msgid ""
"`Twitter <https://twitter.com/godotengine>`_ (see also the `#GodotEngine "
"<https://twitter.com/hashtag/GodotEngine>`_ hashtag)"
msgstr ""

#: ../../docs/community/channels.rst:39
msgid "`Reddit <https://www.reddit.com/r/godot>`_"
msgstr ""

#: ../../docs/community/channels.rst:40
msgid "`YouTube <https://www.youtube.com/c/GodotEngineOfficial>`_"
msgstr ""

#: ../../docs/community/channels.rst:41
msgid "`Steam <https://steamcommunity.com/app/404790>`_"
msgstr ""

#: ../../docs/community/channels.rst:42
#, fuzzy
msgid "`itch.io <https://godotengine.itch.io/godot>`_"
msgstr ""
"Uz ovu dokumentaciju takođe možete pogledati raznorazne `Godot demo projects "
"<https://github.com/godotengine/godot-demo-projects>`_."

#: ../../docs/community/channels.rst:43
msgid "`linkin.bio <https://linkin.bio/godot>`_"
msgstr ""

#: ../../docs/community/channels.rst:46
msgid "Language-based communities"
msgstr ""

#: ../../docs/community/channels.rst:48
msgid ""
"See the `User groups <https://godotengine.org/community/user-groups>`_ page "
"of the website for a list of local communities."
msgstr ""

#: ../../docs/community/tutorials.rst:4
msgid "Tutorials and resources"
msgstr ""

#: ../../docs/community/tutorials.rst:6
msgid ""
"This is a list of third-party tutorials and resources created by the Godot "
"community. For resources, remember that there is the official `Godot Asset "
"Library <https://godotengine.org/asset-library/asset>`_ full of official and "
"community resources too! Also, have a look at this `huge list over at Reddit "
"<https://www.reddit.com/r/godot/comments/an0iq5/"
"godot_tutorials_list_of_video_and_written/>`_."
msgstr ""

#: ../../docs/community/tutorials.rst:8
msgid ""
"Think there is something missing here? Feel free to submit a `Pull Request "
"<https://github.com/godotengine/godot-docs/blob/master/community/tutorials."
"rst>`_ as always."
msgstr ""

#: ../../docs/community/tutorials.rst:11
msgid "Where to start"
msgstr ""

#: ../../docs/community/tutorials.rst:13
msgid ""
"The Godot video tutorials by `GDQuest <https://www.youtube.com/channel/"
"UCxboW7x0jZqFdvMdCFKTMsQ/playlists>`_ are well-regarded in the community and "
"often recommended as a gentle introduction to beginners."
msgstr ""

#: ../../docs/community/tutorials.rst:15
msgid ""
"GDQuest's *Learn GDScript From Zero* is a free and open source interactive "
"tutorial for absolute beginners to learn to program with Godot's GDScript "
"language. It is available as a `desktop application <https://gdquest.itch.io/"
"learn-godot-gdscript>`_  or `in the browser <https://gdquest.github.io/learn-"
"gdscript>`_."
msgstr ""

#: ../../docs/community/tutorials.rst:17
msgid ""
"Some tutorials mentioned below provide more advanced tutorials, e.g. on 3D "
"or shaders."
msgstr ""

#: ../../docs/community/tutorials.rst:20
msgid "Video tutorials"
msgstr ""

#: ../../docs/community/tutorials.rst:22
msgid ""
"`BornCG <https://www.youtube.com/playlist?"
"list=PLda3VoSoc_TTp8Ng3C57spnNkOw3Hm_35>`_ (2D and 3D, GDScript)"
msgstr ""

#: ../../docs/community/tutorials.rst:23
msgid ""
"`Clear Code <https://www.youtube.com/watch?v=nAh_Kx5Zh5Q>`_ (2D, GDScript, "
"Programming Basics)"
msgstr ""

#: ../../docs/community/tutorials.rst:24
msgid ""
"`FencerDevLog <https://www.youtube.com/@FencerDevLog>`_ (2D, 3D, GDScript, "
"Shaders)"
msgstr ""

#: ../../docs/community/tutorials.rst:25
msgid ""
"`FinePointCGI <https://www.youtube.com/channel/UCSojAWUnEUTUcdA9iJ6bryQ>`_ "
"(2D, 3D, GDScript and C#)"
msgstr ""

#: ../../docs/community/tutorials.rst:26
msgid ""
"`GDQuest <https://www.youtube.com/channel/UCxboW7x0jZqFdvMdCFKTMsQ/"
"playlists>`_ (2D and 3D, GDScript and C#)"
msgstr ""

#: ../../docs/community/tutorials.rst:27
msgid ""
"`Game Dev Artisan <https://www.youtube.com/@GameDevArtisan>`_ (2D, GDScript)"
msgstr ""

#: ../../docs/community/tutorials.rst:28
msgid ""
"`Game Development Center <https://www.youtube.com/c/GameDevelopmentCenter>`_ "
"(2D, networked multiplayer, GDScript)"
msgstr ""

#: ../../docs/community/tutorials.rst:29
msgid ""
"`Game Endeavor <https://www.youtube.com/channel/UCLweX1UtQjRjj7rs_0XQ2Eg/"
"videos>`_ (2D, GDScript)"
msgstr ""

#: ../../docs/community/tutorials.rst:30
msgid "`Gwizz <https://www.youtube.com/@Gwizz1027>`_ (2D, GDScript)"
msgstr ""

#: ../../docs/community/tutorials.rst:31
msgid ""
"`Godotneers <https://www.youtube.com/@godotneers>`_ (2D, Shaders, GDScript)"
msgstr ""

#: ../../docs/community/tutorials.rst:32
msgid "`HeartBeast <https://www.youtube.com/@uheartbeast>`_ (2D, GDScript)"
msgstr ""

#: ../../docs/community/tutorials.rst:33
msgid ""
"`KidsCanCode <https://www.youtube.com/channel/UCNaPQ5uLX5iIEHUCLmfAgKg/"
"playlists>`__ (2D and 3D, GDScript)"
msgstr ""

#: ../../docs/community/tutorials.rst:34
msgid "`Maker Tech <https://www.youtube.com/@MakerTech/>`_ (2D, GDScript)"
msgstr ""

#: ../../docs/community/tutorials.rst:35
msgid "`Pigdev <https://www.youtube.com/@pigdev>`_ (2D, GDScript)"
msgstr ""

#: ../../docs/community/tutorials.rst:36
msgid ""
"`Queble <https://www.youtube.com/@queblegamedevelopment4143>`_ (2D, GDScript)"
msgstr ""

#: ../../docs/community/tutorials.rst:37
msgid "`Quiver <https://quiver.dev/>`_ (2D, GDScript)"
msgstr ""

#: ../../docs/community/tutorials.rst:40
#, fuzzy
msgid "Text tutorials"
msgstr "Tutorijali"

#: ../../docs/community/tutorials.rst:42
msgid "`FinepointCGI website by Mitch <https://finepointcgi.io/>`__"
msgstr ""

#: ../../docs/community/tutorials.rst:43
msgid "`GDScript website by Andrew Wilkes <https://gdscript.com>`__"
msgstr ""

#: ../../docs/community/tutorials.rst:44
msgid ""
"`Godot Recipes by KidsCanCode <https://kidscancode.org/godot_recipes/4.x/>`__"
msgstr ""

#: ../../docs/community/tutorials.rst:45
msgid ""
"`Godot Tutorials by SomethingLikeGames <https://www.somethinglikegames.de/en/"
"tags/godot-engine/>`__"
msgstr ""

#: ../../docs/community/tutorials.rst:46
msgid "`Game Dev Artisan website <https://gamedevartisan.com/>`__"
msgstr ""

#: ../../docs/community/tutorials.rst:47
msgid ""
"`Night Quest Games Blog <https://www.nightquestgames.com/blog-articles/>`__"
msgstr ""

#: ../../docs/community/tutorials.rst:50
msgid "Devlogs"
msgstr ""

#: ../../docs/community/tutorials.rst:52
msgid ""
"`Bastiaan Olij (AR & VR) <https://www.youtube.com/channel/UCrbLJYzJjDf2p-"
"vJC011lYw/videos>`_"
msgstr ""

#: ../../docs/community/tutorials.rst:53
msgid "`bitbrain <https://www.youtube.com/@bitbraindev>`_"
msgstr ""

#: ../../docs/community/tutorials.rst:54
msgid "`DevDuck (2D) <https://www.youtube.com/@devduck/videos>`_"
msgstr ""

#: ../../docs/community/tutorials.rst:59
msgid ""
"`awesome-godot: A curated list of free/libre plugins, scripts and add-ons "
"<https://github.com/godotengine/awesome-godot>`_"
msgstr ""

#: ../../docs/community/tutorials.rst:60
msgid "`Godot Asset Library <https://godotengine.org/asset-library/asset>`_"
msgstr ""

#: ../../docs/community/tutorials.rst:61
msgid ""
"`Godot Shaders: A community-driven shader library <https://godotshaders.com/"
">`_"
msgstr ""

#: ../../docs/community/tutorials.rst:62
msgid ""
"`Zeef Godot Engine: A curated directory of resources by Andre Schmitz "
"<https://godot-engine.zeef.com/andre.antonio.schmitz>`_"
msgstr ""