Sync Sphinx and Weblate templates with current docs

2025-12-31 09:49:22 +03:00 · 2020-07-30 18:43:55 +02:00
parent 702e9aa125
commit 61351bef2a
327 changed files with 11679 additions and 4591 deletions
--- a/2
+++ b/2
--- a/sphinx/templates/about/docs_changelog.pot
+++ b/sphinx/templates/about/docs_changelog.pot
@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2020-07-06 14:52+0200\n"
+"POT-Creation-Date: 2020-07-30 19:14+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
--- a/sphinx/templates/about/faq.pot
+++ b/sphinx/templates/about/faq.pot
@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2020-07-06 14:52+0200\n"
+"POT-Creation-Date: 2020-07-30 19:14+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
--- a/sphinx/templates/about/index.pot
+++ b/sphinx/templates/about/index.pot
@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2020-07-06 14:52+0200\n"
+"POT-Creation-Date: 2020-07-30 19:14+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
--- a/sphinx/templates/about/introduction.pot
+++ b/sphinx/templates/about/introduction.pot
@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2020-07-06 14:52+0200\n"
+"POT-Creation-Date: 2020-07-30 19:14+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
--- a/sphinx/templates/about/list_of_features.pot
+++ b/sphinx/templates/about/list_of_features.pot
--- a/sphinx/templates/about/release_policy.pot
+++ b/sphinx/templates/about/release_policy.pot
@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2020-07-06 14:52+0200\n"
+"POT-Creation-Date: 2020-07-30 19:14+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
--- a/sphinx/templates/community/channels.pot
+++ b/sphinx/templates/community/channels.pot
@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2020-07-06 14:52+0200\n"
+"POT-Creation-Date: 2020-07-30 19:14+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
@@ -45,27 +45,27 @@ msgid "IRC on Freenode"
 msgstr ""

 #: ../../docs/community/channels.rst:20
-msgid "`General: #godotengine <http://webchat.freenode.net/?channels=#godotengine>`_"
+msgid "`General: #godotengine <https://webchat.freenode.net/?channels=#godotengine>`_"
 msgstr ""

 #: ../../docs/community/channels.rst:21
-msgid "`Engine development: #godotengine-devel <http://webchat.freenode.net/?channels=#godotengine-devel>`_"
+msgid "`Engine development: #godotengine-devel <https://webchat.freenode.net/?channels=#godotengine-devel>`_"
 msgstr ""

 #: ../../docs/community/channels.rst:22
-msgid "`Documentation: #godotengine-doc <http://webchat.freenode.net/?channels=#godotengine-doc>`_"
+msgid "`Documentation: #godotengine-doc <https://webchat.freenode.net/?channels=#godotengine-doc>`_"
 msgstr ""

 #: ../../docs/community/channels.rst:23
-msgid "`Pull request meetings: #godotengine-meeting <http://webchat.freenode.net/?channels=#godotengine-meeting>`_"
+msgid "`Pull request meetings: #godotengine-meeting <https://webchat.freenode.net/?channels=#godotengine-meeting>`_"
 msgstr ""

 #: ../../docs/community/channels.rst:24
-msgid "`GDNative: #godotengine-gdnative <http://webchat.freenode.net/?channels=#godotengine-gdnative>`_"
+msgid "`GDNative: #godotengine-gdnative <https://webchat.freenode.net/?channels=#godotengine-gdnative>`_"
 msgstr ""

 #: ../../docs/community/channels.rst:25
-msgid "`Website and public relations: #godotengine-atelier <http://webchat.freenode.net/?channels=#godotengine-atelier>`_"
+msgid "`Website and public relations: #godotengine-atelier <https://webchat.freenode.net/?channels=#godotengine-atelier>`_"
 msgstr ""

 #: ../../docs/community/channels.rst:26
@@ -77,7 +77,7 @@ msgid "Other chats"
 msgstr ""

 #: ../../docs/community/channels.rst:31
-msgid "`Discord Server <https://discordapp.com/invite/zH7NUgz>`_"
+msgid "`Discord <https://discord.gg/4JBkykG>`_"
 msgstr ""

 #: ../../docs/community/channels.rst:32
@@ -121,26 +121,26 @@ msgid "`Facebook group <https://www.facebook.com/groups/godotengine/>`_"
 msgstr ""

 #: ../../docs/community/channels.rst:48
-msgid "`Twitter (also, #godotengine) <https://twitter.com/godotengine>`_"
-msgstr ""
-
-#: ../../docs/community/channels.rst:49
-msgid "`Reddit <https://www.reddit.com/r/godot>`_"
+msgid "`Twitter <https://twitter.com/godotengine>`_ (see also the `#GodotEngine <https://twitter.com/hashtag/GodotEngine>`_ hashtag)"
 msgstr ""

 #: ../../docs/community/channels.rst:50
-msgid "`YouTube <https://www.youtube.com/c/GodotEngineOfficial>`_"
+msgid "`Reddit <https://www.reddit.com/r/godot>`_"
 msgstr ""

 #: ../../docs/community/channels.rst:51
+msgid "`YouTube <https://www.youtube.com/c/GodotEngineOfficial>`_"
+msgstr ""
+
+#: ../../docs/community/channels.rst:52
 msgid "`Steam <https://steamcommunity.com/app/404790>`_"
 msgstr ""

-#: ../../docs/community/channels.rst:54
+#: ../../docs/community/channels.rst:55
 msgid "Forum"
 msgstr ""

-#: ../../docs/community/channels.rst:56
-msgid "`Forum (godotforums.org) <https://godotforums.org/>`_"
+#: ../../docs/community/channels.rst:57
+msgid "`Godot Forums <https://godotforums.org/>`_"
 msgstr ""

--- a/sphinx/templates/community/contributing/best_practices_for_engine_contributors.pot
+++ b/sphinx/templates/community/contributing/best_practices_for_engine_contributors.pot
@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2020-07-06 14:52+0200\n"
+"POT-Creation-Date: 2020-07-30 19:14+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
@@ -28,211 +28,215 @@ msgstr ""
 msgid "Godot has a large amount of users who have the ability to contribute, given the project itself is aimed mainly at users with the ability to do programming. Despite this, 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/community/contributing/best_practices_for_engine_contributors.rst:12
+#: ../../docs/community/contributing/best_practices_for_engine_contributors.rst:16
 msgid "Language"
 msgstr ""

-#: ../../docs/community/contributing/best_practices_for_engine_contributors.rst:14
+#: ../../docs/community/contributing/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 creating a language they can use to refer to common situations that arise in the process of submitting their contributions."
 msgstr ""

-#: ../../docs/community/contributing/best_practices_for_engine_contributors.rst:16
+#: ../../docs/community/contributing/best_practices_for_engine_contributors.rst:22
 msgid "While some may find it useful to extend this to general software development, our intention is to just restrict to situations that are most common in our project."
 msgstr ""

-#: ../../docs/community/contributing/best_practices_for_engine_contributors.rst:18
+#: ../../docs/community/contributing/best_practices_for_engine_contributors.rst:26
 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/community/contributing/best_practices_for_engine_contributors.rst:21
+#: ../../docs/community/contributing/best_practices_for_engine_contributors.rst:31
 msgid "Best Practices"
 msgstr ""

-#: ../../docs/community/contributing/best_practices_for_engine_contributors.rst:24
+#: ../../docs/community/contributing/best_practices_for_engine_contributors.rst:34
 msgid "#1: The problem always comes first"
 msgstr ""

-#: ../../docs/community/contributing/best_practices_for_engine_contributors.rst:26
+#: ../../docs/community/contributing/best_practices_for_engine_contributors.rst:36
 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 not be actually solving any actual problems."
 msgstr ""

-#: ../../docs/community/contributing/best_practices_for_engine_contributors.rst:30
+#: ../../docs/community/contributing/best_practices_for_engine_contributors.rst:43
 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 space as source and binary and requires maintenance once it exists. Avoiding the addition of anything unnecessary is always considered a good practice in software development."
 msgstr ""

-#: ../../docs/community/contributing/best_practices_for_engine_contributors.rst:33
+#: ../../docs/community/contributing/best_practices_for_engine_contributors.rst:50
 msgid "#2: The problem has to exist"
 msgstr ""

-#: ../../docs/community/contributing/best_practices_for_engine_contributors.rst:35
+#: ../../docs/community/contributing/best_practices_for_engine_contributors.rst:52
 msgid "This is a variation of the previous practice. I believe most developers agree that adding anything unnecessary is not a good idea, but what constitutes what is necessary and what isn't?"
 msgstr ""

-#: ../../docs/community/contributing/best_practices_for_engine_contributors.rst:39
+#: ../../docs/community/contributing/best_practices_for_engine_contributors.rst:58
 msgid "The answer to this question is that the problem needs to *exist*. 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 into a problem that requires a solution in order to continue, or in order to achieve greater productivity. In this case, *a solution is needed*."
 msgstr ""

-#: ../../docs/community/contributing/best_practices_for_engine_contributors.rst:41
+#: ../../docs/community/contributing/best_practices_for_engine_contributors.rst:64
 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/community/contributing/best_practices_for_engine_contributors.rst:43
+#: ../../docs/community/contributing/best_practices_for_engine_contributors.rst:68
 msgid "I think it would be useful for users to..."
 msgstr ""

-#: ../../docs/community/contributing/best_practices_for_engine_contributors.rst:44
+#: ../../docs/community/contributing/best_practices_for_engine_contributors.rst:69
 msgid "I think users will eventually need to..."
 msgstr ""

-#: ../../docs/community/contributing/best_practices_for_engine_contributors.rst:46
+#: ../../docs/community/contributing/best_practices_for_engine_contributors.rst:71
 msgid "This is generally considered a bad habit, because trying to solve problems that *don't actually exist* in the present will very often lead to code that will be written but never used, or to code that is considerably more complex to use and maintain than it needs to be."
 msgstr ""

-#: ../../docs/community/contributing/best_practices_for_engine_contributors.rst:49
+#: ../../docs/community/contributing/best_practices_for_engine_contributors.rst:77
 msgid "#3: The problem has to be complex or frequent"
 msgstr ""

-#: ../../docs/community/contributing/best_practices_for_engine_contributors.rst:51
+#: ../../docs/community/contributing/best_practices_for_engine_contributors.rst:79
 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 solve problems for you, so it helps you to make games better and faster, but it won't make the *entire game* for you. A line must be drawn somewhere."
 msgstr ""

-#: ../../docs/community/contributing/best_practices_for_engine_contributors.rst:55
+#: ../../docs/community/contributing/best_practices_for_engine_contributors.rst:86
 msgid "Whether a problem is worth solving is determined by the difficulty the user has to work around it. This difficulty can be expressed as:"
 msgstr ""

-#: ../../docs/community/contributing/best_practices_for_engine_contributors.rst:57
+#: ../../docs/community/contributing/best_practices_for_engine_contributors.rst:89
 msgid "The complexity of the problem"
 msgstr ""

-#: ../../docs/community/contributing/best_practices_for_engine_contributors.rst:58
+#: ../../docs/community/contributing/best_practices_for_engine_contributors.rst:90
 msgid "The frequency the problem"
 msgstr ""

-#: ../../docs/community/contributing/best_practices_for_engine_contributors.rst:60
+#: ../../docs/community/contributing/best_practices_for_engine_contributors.rst:92
 msgid "If the problem is *too complex* for most users to solve, the software must offer a ready-made solution for it. Likewise, if the problem is easy for the user to workaround, offering such a solution is unnecessary and it's up to the user to do it."
 msgstr ""

-#: ../../docs/community/contributing/best_practices_for_engine_contributors.rst:62
+#: ../../docs/community/contributing/best_practices_for_engine_contributors.rst:97
 msgid "The exception, however, is when the user stumbles into this problem *frequently enough* that having to do the simple solution every time becomes an annoyance. In this case, the software must offer a solution to simplify this use case."
 msgstr ""

-#: ../../docs/community/contributing/best_practices_for_engine_contributors.rst:64
+#: ../../docs/community/contributing/best_practices_for_engine_contributors.rst:101
 msgid "In our experience, in most cases it's usually obvious to tell when a problem is complex or frequent, but cases may arise where drawing this line is difficult. This is why discussing with other developers (next point) is always advised."
 msgstr ""

-#: ../../docs/community/contributing/best_practices_for_engine_contributors.rst:67
+#: ../../docs/community/contributing/best_practices_for_engine_contributors.rst:106
 msgid "#4: The solution must be discussed with others"
 msgstr ""

-#: ../../docs/community/contributing/best_practices_for_engine_contributors.rst:69
+#: ../../docs/community/contributing/best_practices_for_engine_contributors.rst:108
 msgid "It is often the case that, when users stumble upon problems, they are only immersed in their own project, so they will naturally try to solve the problem from their own perspective, thinking only about their use case."
 msgstr ""

-#: ../../docs/community/contributing/best_practices_for_engine_contributors.rst:71
+#: ../../docs/community/contributing/best_practices_for_engine_contributors.rst:112
 msgid "Because of this, user proposed solutions don't always contemplate other use cases that developers are often aware of, so they are often biased towards their own requirements."
 msgstr ""

-#: ../../docs/community/contributing/best_practices_for_engine_contributors.rst:75
+#: ../../docs/community/contributing/best_practices_for_engine_contributors.rst:118
 msgid "For developers, the perspective is different. They may find the user's problem too unique to justify a solution (instead of a user workaround), or maybe they will 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/community/contributing/best_practices_for_engine_contributors.rst:77
+#: ../../docs/community/contributing/best_practices_for_engine_contributors.rst:124
 msgid "In any case, before attempting a contribution, 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/community/contributing/best_practices_for_engine_contributors.rst:79
+#: ../../docs/community/contributing/best_practices_for_engine_contributors.rst:128
 msgid "The only exception, in this case, is when an area of code has a clear owner (agreed by the other contributors), who talks to users directly and has the most knowledge to implement a solution directly."
 msgstr ""

-#: ../../docs/community/contributing/best_practices_for_engine_contributors.rst:82
+#: ../../docs/community/contributing/best_practices_for_engine_contributors.rst:132
+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/community/contributing/best_practices_for_engine_contributors.rst:138
 msgid "#5: To each problem, its own solution"
 msgstr ""

-#: ../../docs/community/contributing/best_practices_for_engine_contributors.rst:84
+#: ../../docs/community/contributing/best_practices_for_engine_contributors.rst:140
 msgid "For programmers, it is always a most enjoyable challenge to find the most optimal solutions to problems. Things, however, may go overboard sometimes and programmers will try to come up with solutions that solve as many problems as possible."
 msgstr ""

-#: ../../docs/community/contributing/best_practices_for_engine_contributors.rst:86
+#: ../../docs/community/contributing/best_practices_for_engine_contributors.rst:145
 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/community/contributing/best_practices_for_engine_contributors.rst:90
+#: ../../docs/community/contributing/best_practices_for_engine_contributors.rst:151
 msgid "The main problem is that, in reality, it rarely works this way. Most of the time, just writing an individual solution to each problem results in code that is simpler and more maintainable."
 msgstr ""

-#: ../../docs/community/contributing/best_practices_for_engine_contributors.rst:92
+#: ../../docs/community/contributing/best_practices_for_engine_contributors.rst:155
 msgid "Additionally, solutions that target individual problems are better for the users, as they find something that does exactly what they need, without having to learn and remember a more complex system they will only need for simple tasks."
 msgstr ""

-#: ../../docs/community/contributing/best_practices_for_engine_contributors.rst:94
+#: ../../docs/community/contributing/best_practices_for_engine_contributors.rst:160
 msgid "Big and flexible solutions also have an additional drawback which is that, over time, they are rarely flexible enough for all users, which keep requesting more functions added (and making the API and codebase more and more complex)."
 msgstr ""

-#: ../../docs/community/contributing/best_practices_for_engine_contributors.rst:97
+#: ../../docs/community/contributing/best_practices_for_engine_contributors.rst:165
 msgid "#6: Cater to common use cases, leave the door open for the rare ones"
 msgstr ""

-#: ../../docs/community/contributing/best_practices_for_engine_contributors.rst:99
+#: ../../docs/community/contributing/best_practices_for_engine_contributors.rst:167
 msgid "This is a continuation of the previous point, which further explains why this way of thinking and designing software is preferred."
 msgstr ""

-#: ../../docs/community/contributing/best_practices_for_engine_contributors.rst:101
+#: ../../docs/community/contributing/best_practices_for_engine_contributors.rst:170
 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/community/contributing/best_practices_for_engine_contributors.rst:103
+#: ../../docs/community/contributing/best_practices_for_engine_contributors.rst:175
 msgid "We may come up with something we believe is brilliant, but when it's actually used, we will find that users will never even use half of it, or that they will require features that don't quite accommodate our original design, forcing us to either throw it away or make it even more complex."
 msgstr ""

-#: ../../docs/community/contributing/best_practices_for_engine_contributors.rst:105
+#: ../../docs/community/contributing/best_practices_for_engine_contributors.rst:180
 msgid "The question is then, how to design software that gives users what *we know they need*, but that is flexible enough to allow them to do *what we don't know they might need* in the future?"
 msgstr ""

-#: ../../docs/community/contributing/best_practices_for_engine_contributors.rst:109
+#: ../../docs/community/contributing/best_practices_for_engine_contributors.rst:186
 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/community/contributing/best_practices_for_engine_contributors.rst:111
+#: ../../docs/community/contributing/best_practices_for_engine_contributors.rst:191
 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/community/contributing/best_practices_for_engine_contributors.rst:114
+#: ../../docs/community/contributing/best_practices_for_engine_contributors.rst:196
 msgid "#7: Solutions must be local"
 msgstr ""

-#: ../../docs/community/contributing/best_practices_for_engine_contributors.rst:116
+#: ../../docs/community/contributing/best_practices_for_engine_contributors.rst:198
 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/community/contributing/best_practices_for_engine_contributors.rst:118
+#: ../../docs/community/contributing/best_practices_for_engine_contributors.rst:202
 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/community/contributing/best_practices_for_engine_contributors.rst:120
+#: ../../docs/community/contributing/best_practices_for_engine_contributors.rst:207
 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/community/contributing/best_practices_for_engine_contributors.rst:126
+#: ../../docs/community/contributing/best_practices_for_engine_contributors.rst:215
 msgid "The common reasoning for wanting to do this is that it's usually less code to simply add a hack in the core layers."
 msgstr ""

-#: ../../docs/community/contributing/best_practices_for_engine_contributors.rst:128
+#: ../../docs/community/contributing/best_practices_for_engine_contributors.rst:218
 msgid "Despite this, this practice is not advised. Generally, the code for a solution should be closer to where the problem originates, even if it involves more code, duplicated, more complex or is less efficient. More creativity might be needed, but this path is always the advised one."
 msgstr ""

-#: ../../docs/community/contributing/best_practices_for_engine_contributors.rst:131
+#: ../../docs/community/contributing/best_practices_for_engine_contributors.rst:224
 msgid "#8: Don't use complex canned solutions for simple problems"
 msgstr ""

-#: ../../docs/community/contributing/best_practices_for_engine_contributors.rst:133
+#: ../../docs/community/contributing/best_practices_for_engine_contributors.rst:226
 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/community/contributing/best_practices_for_engine_contributors.rst:135
+#: ../../docs/community/contributing/best_practices_for_engine_contributors.rst:229
 msgid "As Godot requires to be shipped in a large amount of platforms, we just can't link libraries dynamically. Instead, we bundle them in our source tree."
 msgstr ""

-#: ../../docs/community/contributing/best_practices_for_engine_contributors.rst:139
+#: ../../docs/community/contributing/best_practices_for_engine_contributors.rst:234
 msgid "As a result, we are very picky with what goes in, and we tend to prefer smaller libraries (in fact, single header ones are our favorite). Only in cases where there is no other choice we end up bundling something larger."
 msgstr ""

--- a/sphinx/templates/community/contributing/bisecting_regressions.pot
+++ b/sphinx/templates/community/contributing/bisecting_regressions.pot
@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2020-07-06 14:52+0200\n"
+"POT-Creation-Date: 2020-07-30 19:14+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
--- a/sphinx/templates/community/contributing/bug_triage_guidelines.pot
+++ b/sphinx/templates/community/contributing/bug_triage_guidelines.pot
@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2020-07-06 14:52+0200\n"
+"POT-Creation-Date: 2020-07-30 19:14+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
--- a/sphinx/templates/community/contributing/code_style_guidelines.pot
+++ b/sphinx/templates/community/contributing/code_style_guidelines.pot
@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2020-07-06 14:52+0200\n"
+"POT-Creation-Date: 2020-07-30 19:14+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
--- a/sphinx/templates/community/contributing/docs_writing_guidelines.pot
+++ b/sphinx/templates/community/contributing/docs_writing_guidelines.pot
@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2020-07-06 14:52+0200\n"
+"POT-Creation-Date: 2020-07-30 19:14+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
@@ -52,12 +52,12 @@ msgid "Ban these 8 words: obvious, simple, basic, easy, actual, just, clear, and
 msgstr ""

 #: ../../docs/community/contributing/docs_writing_guidelines.rst:19
-#: ../../docs/community/contributing/docs_writing_guidelines.rst:210
+#: ../../docs/community/contributing/docs_writing_guidelines.rst:214
 msgid "Use explicit references"
 msgstr ""

 #: ../../docs/community/contributing/docs_writing_guidelines.rst:20
-#: ../../docs/community/contributing/docs_writing_guidelines.rst:231
+#: ../../docs/community/contributing/docs_writing_guidelines.rst:235
 msgid "Use 's to show possession"
 msgstr ""

@@ -70,17 +70,17 @@ msgid "There are 3 rules to describe classes:"
 msgstr ""

 #: ../../docs/community/contributing/docs_writing_guidelines.rst:25
-#: ../../docs/community/contributing/docs_writing_guidelines.rst:368
+#: ../../docs/community/contributing/docs_writing_guidelines.rst:372
 msgid "Give an overview of the node in the brief description"
 msgstr ""

 #: ../../docs/community/contributing/docs_writing_guidelines.rst:26
-#: ../../docs/community/contributing/docs_writing_guidelines.rst:397
+#: ../../docs/community/contributing/docs_writing_guidelines.rst:401
 msgid "Mention what methods return if it's useful"
 msgstr ""

 #: ../../docs/community/contributing/docs_writing_guidelines.rst:27
-#: ../../docs/community/contributing/docs_writing_guidelines.rst:422
+#: ../../docs/community/contributing/docs_writing_guidelines.rst:426
 msgid "Use \"if true\" to describe booleans"
 msgstr ""

@@ -105,7 +105,7 @@ msgid "Active:"
 msgstr ""

 #: ../../docs/community/contributing/docs_writing_guidelines.rst:59
-#: ../../docs/community/contributing/docs_writing_guidelines.rst:403
+#: ../../docs/community/contributing/docs_writing_guidelines.rst:407
 msgid "**Don't** use the passive voice:"
 msgstr ""

@@ -138,346 +138,350 @@ msgid "**Do** use simple present, preterit or future."
 msgstr ""

 #: ../../docs/community/contributing/docs_writing_guidelines.rst:115
+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/community/contributing/docs_writing_guidelines.rst:119
 msgid "You may use the progressive tense to describe actions that are continuous in time. Anything like animation or coroutines."
 msgstr ""

-#: ../../docs/community/contributing/docs_writing_guidelines.rst:120
+#: ../../docs/community/contributing/docs_writing_guidelines.rst:124
 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/community/contributing/docs_writing_guidelines.rst:125
+#: ../../docs/community/contributing/docs_writing_guidelines.rst:129
 msgid "Remove unnecessary adverbs and adjectives"
 msgstr ""

-#: ../../docs/community/contributing/docs_writing_guidelines.rst:127
+#: ../../docs/community/contributing/docs_writing_guidelines.rst:131
 msgid "Write as few adjectives and adverbs as possible. Only use them if they add key information to the description."
 msgstr ""

-#: ../../docs/community/contributing/docs_writing_guidelines.rst:130
+#: ../../docs/community/contributing/docs_writing_guidelines.rst:134
 msgid "**Don't** use redundant or meaningless adverbs. Words that lengthen the documentation but don't add any information:"
 msgstr ""

-#: ../../docs/community/contributing/docs_writing_guidelines.rst:137
+#: ../../docs/community/contributing/docs_writing_guidelines.rst:141
 msgid "**Do** write short sentences in a simple, descriptive language:"
 msgstr ""

-#: ../../docs/community/contributing/docs_writing_guidelines.rst:144
+#: ../../docs/community/contributing/docs_writing_guidelines.rst:148
 msgid "Ban these 8 words"
 msgstr ""

-#: ../../docs/community/contributing/docs_writing_guidelines.rst:146
+#: ../../docs/community/contributing/docs_writing_guidelines.rst:150
 msgid "**Don't** ever use these 8 banned words:"
 msgstr ""

-#: ../../docs/community/contributing/docs_writing_guidelines.rst:148
+#: ../../docs/community/contributing/docs_writing_guidelines.rst:152
 msgid "obvious"
 msgstr ""

-#: ../../docs/community/contributing/docs_writing_guidelines.rst:149
+#: ../../docs/community/contributing/docs_writing_guidelines.rst:153
 msgid "simple"
 msgstr ""

-#: ../../docs/community/contributing/docs_writing_guidelines.rst:150
+#: ../../docs/community/contributing/docs_writing_guidelines.rst:154
 msgid "basic"
 msgstr ""

-#: ../../docs/community/contributing/docs_writing_guidelines.rst:151
+#: ../../docs/community/contributing/docs_writing_guidelines.rst:155
 msgid "easy"
 msgstr ""

-#: ../../docs/community/contributing/docs_writing_guidelines.rst:152
+#: ../../docs/community/contributing/docs_writing_guidelines.rst:156
 msgid "actual"
 msgstr ""

-#: ../../docs/community/contributing/docs_writing_guidelines.rst:153
+#: ../../docs/community/contributing/docs_writing_guidelines.rst:157
 msgid "just"
 msgstr ""

-#: ../../docs/community/contributing/docs_writing_guidelines.rst:154
+#: ../../docs/community/contributing/docs_writing_guidelines.rst:158
 msgid "clear"
 msgstr ""

-#: ../../docs/community/contributing/docs_writing_guidelines.rst:155
+#: ../../docs/community/contributing/docs_writing_guidelines.rst:159
 msgid "however (some uses)"
 msgstr ""

-#: ../../docs/community/contributing/docs_writing_guidelines.rst:157
+#: ../../docs/community/contributing/docs_writing_guidelines.rst:161
 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/community/contributing/docs_writing_guidelines.rst:163
+#: ../../docs/community/contributing/docs_writing_guidelines.rst:167
 msgid "**Don't** example. The banned words lengthen the description and take attention away from the most important info:"
 msgstr ""

-#: ../../docs/community/contributing/docs_writing_guidelines.rst:171
+#: ../../docs/community/contributing/docs_writing_guidelines.rst:175
 msgid "**Do** remove them:"
 msgstr ""

-#: ../../docs/community/contributing/docs_writing_guidelines.rst:178
+#: ../../docs/community/contributing/docs_writing_guidelines.rst:182
 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/community/contributing/docs_writing_guidelines.rst:188
+#: ../../docs/community/contributing/docs_writing_guidelines.rst:192
 msgid "**Do** explain what the node does instead:"
 msgstr ""

-#: ../../docs/community/contributing/docs_writing_guidelines.rst:195
+#: ../../docs/community/contributing/docs_writing_guidelines.rst:199
 msgid "**Don't** use \"basic\", it is too vague:"
 msgstr ""

-#: ../../docs/community/contributing/docs_writing_guidelines.rst:202
+#: ../../docs/community/contributing/docs_writing_guidelines.rst:206
 msgid "**Do** use the brief description to offer an overview of the node:"
 msgstr ""

-#: ../../docs/community/contributing/docs_writing_guidelines.rst:212
+#: ../../docs/community/contributing/docs_writing_guidelines.rst:216
 msgid "Favor explicit references over implicit ones."
 msgstr ""

-#: ../../docs/community/contributing/docs_writing_guidelines.rst:214
+#: ../../docs/community/contributing/docs_writing_guidelines.rst:218
 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/community/contributing/docs_writing_guidelines.rst:221
+#: ../../docs/community/contributing/docs_writing_guidelines.rst:225
 msgid "**Do** repeat words. They remove all ambiguity:"
 msgstr ""

-#: ../../docs/community/contributing/docs_writing_guidelines.rst:227
+#: ../../docs/community/contributing/docs_writing_guidelines.rst:231
 msgid "If you need to repeat the same variable name 3 or 4 times, you probably need to rephrase your description."
 msgstr ""

-#: ../../docs/community/contributing/docs_writing_guidelines.rst:233
+#: ../../docs/community/contributing/docs_writing_guidelines.rst:237
 msgid "Avoid \"The milk **of** the cow\". It feels unnatural in English. Write \"The cow's milk\" instead."
 msgstr ""

-#: ../../docs/community/contributing/docs_writing_guidelines.rst:236
+#: ../../docs/community/contributing/docs_writing_guidelines.rst:240
 msgid "**Don't** write \"of the X\":"
 msgstr ""

-#: ../../docs/community/contributing/docs_writing_guidelines.rst:242
+#: ../../docs/community/contributing/docs_writing_guidelines.rst:246
 msgid "**Do** use ``'s``. It lets you put the main subject at the start of the sentence, and keep it short:"
 msgstr ""

-#: ../../docs/community/contributing/docs_writing_guidelines.rst:250
+#: ../../docs/community/contributing/docs_writing_guidelines.rst:254
 msgid "Use the Oxford comma to enumerate anything"
 msgstr ""

-#: ../../docs/community/contributing/docs_writing_guidelines.rst:252
+#: ../../docs/community/contributing/docs_writing_guidelines.rst:256
 msgid "From the Oxford dictionary:"
 msgstr ""

-#: ../../docs/community/contributing/docs_writing_guidelines.rst:254
+#: ../../docs/community/contributing/docs_writing_guidelines.rst:258
 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/community/contributing/docs_writing_guidelines.rst:257
+#: ../../docs/community/contributing/docs_writing_guidelines.rst:261
 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/community/contributing/docs_writing_guidelines.rst:260
+#: ../../docs/community/contributing/docs_writing_guidelines.rst:264
 msgid "**Don't** leave the last element of a list without a comma:"
 msgstr ""

-#: ../../docs/community/contributing/docs_writing_guidelines.rst:266
+#: ../../docs/community/contributing/docs_writing_guidelines.rst:270
 msgid "**Do** add a comma before `and` or `or`, for the last element of a list with more than two elements."
 msgstr ""

-#: ../../docs/community/contributing/docs_writing_guidelines.rst:275
+#: ../../docs/community/contributing/docs_writing_guidelines.rst:279
 msgid "How to write methods and classes"
 msgstr ""

-#: ../../docs/community/contributing/docs_writing_guidelines.rst:278
+#: ../../docs/community/contributing/docs_writing_guidelines.rst:282
 msgid "Dynamic vs static typing"
 msgstr ""

-#: ../../docs/community/contributing/docs_writing_guidelines.rst:280
+#: ../../docs/community/contributing/docs_writing_guidelines.rst:284
 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/community/contributing/docs_writing_guidelines.rst:285
+#: ../../docs/community/contributing/docs_writing_guidelines.rst:289
 msgid "The exception is topics that explain static typing concepts to users."
 msgstr ""

-#: ../../docs/community/contributing/docs_writing_guidelines.rst:287
+#: ../../docs/community/contributing/docs_writing_guidelines.rst:291
 msgid "**Don't** add a type hint with a colon or by casting:"
 msgstr ""

-#: ../../docs/community/contributing/docs_writing_guidelines.rst:297
+#: ../../docs/community/contributing/docs_writing_guidelines.rst:301
 msgid "**Do** write constants variables with dynamic typing:"
 msgstr ""

-#: ../../docs/community/contributing/docs_writing_guidelines.rst:307
+#: ../../docs/community/contributing/docs_writing_guidelines.rst:311
 msgid "**Don't** write functions with inferred arguments or return types:"
 msgstr ""

-#: ../../docs/community/contributing/docs_writing_guidelines.rst:318
+#: ../../docs/community/contributing/docs_writing_guidelines.rst:322
 msgid "**Do** write functions using dynamic typing:"
 msgstr ""

-#: ../../docs/community/contributing/docs_writing_guidelines.rst:330
+#: ../../docs/community/contributing/docs_writing_guidelines.rst:334
 msgid "Use real-world code examples where appropriate"
 msgstr ""

-#: ../../docs/community/contributing/docs_writing_guidelines.rst:332
+#: ../../docs/community/contributing/docs_writing_guidelines.rst:336
 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/community/contributing/docs_writing_guidelines.rst:336
+#: ../../docs/community/contributing/docs_writing_guidelines.rst:340
 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/community/contributing/docs_writing_guidelines.rst:340
+#: ../../docs/community/contributing/docs_writing_guidelines.rst:344
 msgid "**Don't** write made-up examples:"
 msgstr ""

-#: ../../docs/community/contributing/docs_writing_guidelines.rst:351
+#: ../../docs/community/contributing/docs_writing_guidelines.rst:355
 msgid "**Do** write concrete examples:"
 msgstr ""

-#: ../../docs/community/contributing/docs_writing_guidelines.rst:363
+#: ../../docs/community/contributing/docs_writing_guidelines.rst:367
 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/community/contributing/docs_writing_guidelines.rst:370
+#: ../../docs/community/contributing/docs_writing_guidelines.rst:374
 msgid "The brief description is the reference's most important sentence. It's the user's first contact with a node:"
 msgstr ""

-#: ../../docs/community/contributing/docs_writing_guidelines.rst:373
+#: ../../docs/community/contributing/docs_writing_guidelines.rst:377
 msgid "It's the only description in the \"Create New Node\" dialog."
 msgstr ""

-#: ../../docs/community/contributing/docs_writing_guidelines.rst:374
+#: ../../docs/community/contributing/docs_writing_guidelines.rst:378
 msgid "It's at the top of every page in the reference"
 msgstr ""

-#: ../../docs/community/contributing/docs_writing_guidelines.rst:376
+#: ../../docs/community/contributing/docs_writing_guidelines.rst:380
 msgid "The brief description should explain the node's role and its functionality, in up to 200 characters."
 msgstr ""

-#: ../../docs/community/contributing/docs_writing_guidelines.rst:379
+#: ../../docs/community/contributing/docs_writing_guidelines.rst:383
 msgid "**Don't** write tiny and vague summaries:"
 msgstr ""

-#: ../../docs/community/contributing/docs_writing_guidelines.rst:386
+#: ../../docs/community/contributing/docs_writing_guidelines.rst:390
 msgid "**Do** give an overview of the node's functionality:"
 msgstr ""

-#: ../../docs/community/contributing/docs_writing_guidelines.rst:393
+#: ../../docs/community/contributing/docs_writing_guidelines.rst:397
 msgid "Use the node's full description to provide more information, and a code example, if possible."
 msgstr ""

-#: ../../docs/community/contributing/docs_writing_guidelines.rst:399
+#: ../../docs/community/contributing/docs_writing_guidelines.rst:403
 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/community/contributing/docs_writing_guidelines.rst:410
+#: ../../docs/community/contributing/docs_writing_guidelines.rst:414
 msgid "**Do** always use \"Returns\"."
 msgstr ""

-#: ../../docs/community/contributing/docs_writing_guidelines.rst:417
+#: ../../docs/community/contributing/docs_writing_guidelines.rst:421
 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/community/contributing/docs_writing_guidelines.rst:424
+#: ../../docs/community/contributing/docs_writing_guidelines.rst:428
 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/community/contributing/docs_writing_guidelines.rst:428
+#: ../../docs/community/contributing/docs_writing_guidelines.rst:432
 msgid "Also, surround boolean values, variable names and methods with ``[code][/code]``."
 msgstr ""

-#: ../../docs/community/contributing/docs_writing_guidelines.rst:430
+#: ../../docs/community/contributing/docs_writing_guidelines.rst:434
 msgid "**Do** start with \"if true\":"
 msgstr ""

-#: ../../docs/community/contributing/docs_writing_guidelines.rst:439
+#: ../../docs/community/contributing/docs_writing_guidelines.rst:443
 msgid "Use ``[code]`` around arguments"
 msgstr ""

-#: ../../docs/community/contributing/docs_writing_guidelines.rst:441
+#: ../../docs/community/contributing/docs_writing_guidelines.rst:445
 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/community/contributing/docs_writing_guidelines.rst:448
+#: ../../docs/community/contributing/docs_writing_guidelines.rst:452
 msgid "Common vocabulary to use in Godot's documentation"
 msgstr ""

-#: ../../docs/community/contributing/docs_writing_guidelines.rst:450
+#: ../../docs/community/contributing/docs_writing_guidelines.rst:454
 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/community/contributing/docs_writing_guidelines.rst:458
+#: ../../docs/community/contributing/docs_writing_guidelines.rst:462
 msgid "Overview of the interface and common vocabulary"
 msgstr ""

-#: ../../docs/community/contributing/docs_writing_guidelines.rst:460
+#: ../../docs/community/contributing/docs_writing_guidelines.rst:464
 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/community/contributing/docs_writing_guidelines.rst:466
+#: ../../docs/community/contributing/docs_writing_guidelines.rst:470
 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/community/contributing/docs_writing_guidelines.rst:472
+#: ../../docs/community/contributing/docs_writing_guidelines.rst:476
 msgid "The Animation, Debugger, etc. at the bottom of the viewport are ``panels``. Together they make up the ``bottom panels``."
 msgstr ""

-#: ../../docs/community/contributing/docs_writing_guidelines.rst:475
+#: ../../docs/community/contributing/docs_writing_guidelines.rst:479
 msgid "Foldable areas of the Inspector are ``sections``. The node's parent class names, which you can't fold, are ``Classes`` e.g. the ``KinematicBody2D class``. And individual lines with key-value pairs are ``properties``. E.g. ``position`` or ``modulate color`` are both ``properties``."
 msgstr ""

-#: ../../docs/community/contributing/docs_writing_guidelines.rst:482
+#: ../../docs/community/contributing/docs_writing_guidelines.rst:486
 msgid "Keyboard shortcut guidelines"
 msgstr ""

-#: ../../docs/community/contributing/docs_writing_guidelines.rst:484
+#: ../../docs/community/contributing/docs_writing_guidelines.rst:488
 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/community/contributing/docs_writing_guidelines.rst:490
+#: ../../docs/community/contributing/docs_writing_guidelines.rst:494
 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/community/contributing/docs_writing_guidelines.rst:493
+#: ../../docs/community/contributing/docs_writing_guidelines.rst:497
 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/community/contributing/docs_writing_guidelines.rst:496
+#: ../../docs/community/contributing/docs_writing_guidelines.rst:500
 msgid "Press ``:kbd:`Ctrl + Alt + T``` to toggle the panel (``:kbd:`Cmd + Alt + T``` on macOS)."
 msgstr ""

-#: ../../docs/community/contributing/docs_writing_guidelines.rst:497
+#: ../../docs/community/contributing/docs_writing_guidelines.rst:501
 msgid "Press ``:kbd:`Space``` and hold the left mouse button to pan in the 2D editor."
 msgstr ""

-#: ../../docs/community/contributing/docs_writing_guidelines.rst:498
+#: ../../docs/community/contributing/docs_writing_guidelines.rst:502
 msgid "Press ``:kbd:`Shift + Up Arrow``` to move the node upwards by 8 pixels."
 msgstr ""

-#: ../../docs/community/contributing/docs_writing_guidelines.rst:501
+#: ../../docs/community/contributing/docs_writing_guidelines.rst:505
 msgid "Image contribution guidelines"
 msgstr ""

-#: ../../docs/community/contributing/docs_writing_guidelines.rst:503
+#: ../../docs/community/contributing/docs_writing_guidelines.rst:507
 msgid "A significant part of the documentation is images, and there are several important guidelines to follow."
 msgstr ""

-#: ../../docs/community/contributing/docs_writing_guidelines.rst:506
+#: ../../docs/community/contributing/docs_writing_guidelines.rst:510
 msgid "First, you should always be using the default editor theme and text when taking screenshots."
 msgstr ""

-#: ../../docs/community/contributing/docs_writing_guidelines.rst:509
+#: ../../docs/community/contributing/docs_writing_guidelines.rst:513
 msgid "To improve the appearance of 3D screenshots, use 4× MSAA, enable anisotropic filtering on the project's textures, and set the anisotropic filter quality to 16× in Project Settings."
 msgstr ""

-#: ../../docs/community/contributing/docs_writing_guidelines.rst:513
+#: ../../docs/community/contributing/docs_writing_guidelines.rst:517
 msgid "Screenshot sizes should not exceed 1920×1080 to ensure fast loading on slower connections."
 msgstr ""

-#: ../../docs/community/contributing/docs_writing_guidelines.rst:516
+#: ../../docs/community/contributing/docs_writing_guidelines.rst:520
 msgid "When you need to highlight an area of the editor to show something, like a button or option, use a 2 pixel thick outline without a bevel."
 msgstr ""

-#: ../../docs/community/contributing/docs_writing_guidelines.rst:519
+#: ../../docs/community/contributing/docs_writing_guidelines.rst:523
 msgid "Before you add or replace any images in the documentation, they should be run through a PNG compressor to save size. The built in lossless compressor in programs like Krita or Photoshop should be enough. For heavier images, also look into using a lossy compressor, such as `pngquant <https://pngquant.org/>`_ where almost no image quality is lost during compression."
 msgstr ""

--- a/sphinx/templates/community/contributing/documentation_guidelines.pot
+++ b/sphinx/templates/community/contributing/documentation_guidelines.pot
@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2020-07-06 14:52+0200\n"
+"POT-Creation-Date: 2020-07-30 19:14+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
--- a/sphinx/templates/community/contributing/editor_and_docs_localization.pot
+++ b/sphinx/templates/community/contributing/editor_and_docs_localization.pot
@@ -0,0 +1,298 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2014-2020, 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.
+# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: Godot Engine latest\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2020-07-30 19:14+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../docs/community/contributing/editor_and_docs_localization.rst:4
+msgid "Editor and docs localization"
+msgstr ""
+
+#: ../../docs/community/contributing/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/community/contributing/editor_and_docs_localization.rst:13
+msgid "These resources include:"
+msgstr ""
+
+#: ../../docs/community/contributing/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/community/contributing/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/community/contributing/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/community/contributing/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/community/contributing/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/community/contributing/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/community/contributing/editor_and_docs_localization.rst:40
+msgid "Using Weblate for translations"
+msgstr ""
+
+#: ../../docs/community/contributing/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/community/contributing/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/community/contributing/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/community/contributing/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/community/contributing/editor_and_docs_localization.rst:64
+msgid "Adding a new language"
+msgstr ""
+
+#: ../../docs/community/contributing/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/community/contributing/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/community/contributing/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/community/contributing/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/community/contributing/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/community/contributing/editor_and_docs_localization.rst:97
+msgid "Translation interface"
+msgstr ""
+
+#: ../../docs/community/contributing/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/community/contributing/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/community/contributing/editor_and_docs_localization.rst:112
+msgid "On that page, you have:"
+msgstr ""
+
+#: ../../docs/community/contributing/editor_and_docs_localization.rst:114
+msgid "A toolbar which lets you cycle through strings of the current list, change to another pre-defined list or do a custom search, etc. There is also a \"Zen\" editing mode with a simplified interface."
+msgstr ""
+
+#: ../../docs/community/contributing/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/community/contributing/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/community/contributing/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/community/contributing/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/community/contributing/editor_and_docs_localization.rst:143
+msgid "Locating original content"
+msgstr ""
+
+#: ../../docs/community/contributing/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/community/contributing/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/community/contributing/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/community/contributing/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/scenes_and_nodes.rst`` for the page :ref:`doc_scenes_and_nodes`."
+msgstr ""
+
+#: ../../docs/community/contributing/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/community/contributing/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:scenes_and_nodes.rst``):"
+msgstr ""
+
+#: ../../docs/community/contributing/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:scenes_and_nodes.rst`` query would land first on the \"Introduction\" source string which is used in dozens of pages, including some that come before ``scenes_and_nodes.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/community/contributing/editor_and_docs_localization.rst:206
+msgid "Respecting the markup syntax"
+msgstr ""
+
+#: ../../docs/community/contributing/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/community/contributing/editor_and_docs_localization.rst:213
+msgid "Editor interface (C++)"
+msgstr ""
+
+#: ../../docs/community/contributing/editor_and_docs_localization.rst:215
+msgid "The editor translations originate from C++ strings, and may use:"
+msgstr ""
+
+#: ../../docs/community/contributing/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/community/contributing/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/community/contributing/editor_and_docs_localization.rst:247
+msgid "Online documentation (RST)"
+msgstr ""
+
+#: ../../docs/community/contributing/editor_and_docs_localization.rst:249
+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/community/contributing/editor_and_docs_localization.rst:291
+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/community/contributing/editor_and_docs_localization.rst:297
+msgid "Class reference (BBCode)"
+msgstr ""
+
+#: ../../docs/community/contributing/editor_and_docs_localization.rst:299
+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/community/contributing/editor_and_docs_localization.rst:302
+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/community/contributing/editor_and_docs_localization.rst:314
+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/community/contributing/editor_and_docs_localization.rst:321
+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/community/contributing/editor_and_docs_localization.rst:326
+msgid "See our documentation for class reference writers for the :ref:`list of BBCode-like tags <doc_updating_the_class_reference_bbcode>` which are used throughout the class reference."
+msgstr ""
+
+#: ../../docs/community/contributing/editor_and_docs_localization.rst:331
+msgid "Offline translation and testing"
+msgstr ""
+
+#: ../../docs/community/contributing/editor_and_docs_localization.rst:333
+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/community/contributing/editor_and_docs_localization.rst:338
+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/community/contributing/editor_and_docs_localization.rst:343
+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/community/contributing/editor_and_docs_localization.rst:349
+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/community/contributing/editor_and_docs_localization.rst:355
+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/community/contributing/editor_and_docs_localization.rst:358
+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/community/contributing/editor_and_docs_localization.rst:362
+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/community/contributing/editor_and_docs_localization.rst:367
+msgid "Localizing documentation images"
+msgstr ""
+
+#: ../../docs/community/contributing/editor_and_docs_localization.rst:369
+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/community/contributing/editor_and_docs_localization.rst:373
+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/community/contributing/editor_and_docs_localization.rst:379
+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/community/contributing/editor_and_docs_localization.rst:383
+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/community/contributing/editor_and_docs_localization.rst:390
+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/community/contributing/editor_and_docs_localization.rst:397
+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/community/contributing/editor_and_docs_localization.rst:402
+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/community/contributing/editor_and_docs_localization.rst:406
+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/community/contributing/editor_and_docs_localization.rst:412
+msgid "Repeat this for other images and :ref:`make a Pull Request <doc_pr_workflow>`."
+msgstr ""
+
--- a/sphinx/templates/community/contributing/index.pot
+++ b/sphinx/templates/community/contributing/index.pot
@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2020-07-06 14:52+0200\n"
+"POT-Creation-Date: 2020-07-30 19:14+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
--- a/sphinx/templates/community/contributing/pr_workflow.pot
+++ b/sphinx/templates/community/contributing/pr_workflow.pot
@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2020-07-06 14:52+0200\n"
+"POT-Creation-Date: 2020-07-30 19:14+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
--- a/sphinx/templates/community/contributing/updating_the_class_reference.pot
+++ b/sphinx/templates/community/contributing/updating_the_class_reference.pot
@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2020-07-06 14:52+0200\n"
+"POT-Creation-Date: 2020-07-30 19:14+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
@@ -17,7 +17,7 @@ msgstr ""
 "Content-Transfer-Encoding: 8bit\n"

 #: ../../docs/community/contributing/updating_the_class_reference.rst:4
-msgid "Contribute to the Class Reference"
+msgid "Contributing to the class reference"
 msgstr ""

 #: ../../docs/community/contributing/updating_the_class_reference.rst:8
@@ -213,7 +213,7 @@ msgid "Edit the file for your chosen class in ``doc/classes/`` to update the cla
 msgstr ""

 #: ../../docs/community/contributing/updating_the_class_reference.rst:169
-msgid "Edit it using your favorite text editor. If you use a code editor, make sure that it doesn't change the indent style: tabs for the XML, and 4 spaces inside BBcode-style blocks. More on that below."
+msgid "Edit it using your favorite text editor. If you use a code editor, make sure that it doesn't change the indent style: tabs for the XML, and 4 spaces inside BBCode-style blocks. More on that below."
 msgstr ""

 #: ../../docs/community/contributing/updating_the_class_reference.rst:171
@@ -268,243 +268,243 @@ msgstr ""
 msgid "Use a code editor like Vim, Atom, Code, Notepad++ or anything similar to edit the file quickly. Use the search function to find classes fast."
 msgstr ""

-#: ../../docs/community/contributing/updating_the_class_reference.rst:232
-msgid "Improve formatting with BBcode style tags"
+#: ../../docs/community/contributing/updating_the_class_reference.rst:233
+msgid "Improve formatting with BBCode style tags"
 msgstr ""

-#: ../../docs/community/contributing/updating_the_class_reference.rst:234
-msgid "Godot's class reference supports BBcode-like tags. They add nice formatting to the text. Here's the list of available tags:"
+#: ../../docs/community/contributing/updating_the_class_reference.rst:235
+msgid "Godot's class reference supports BBCode-like tags. They add nice formatting to the text. Here's the list of available tags:"
 msgstr ""

-#: ../../docs/community/contributing/updating_the_class_reference.rst:237
+#: ../../docs/community/contributing/updating_the_class_reference.rst:238
 msgid "Tag"
 msgstr ""

-#: ../../docs/community/contributing/updating_the_class_reference.rst:237
+#: ../../docs/community/contributing/updating_the_class_reference.rst:238
 msgid "Effect"
 msgstr ""

-#: ../../docs/community/contributing/updating_the_class_reference.rst:237
+#: ../../docs/community/contributing/updating_the_class_reference.rst:238
 msgid "Usage"
 msgstr ""

-#: ../../docs/community/contributing/updating_the_class_reference.rst:237
+#: ../../docs/community/contributing/updating_the_class_reference.rst:238
 msgid "Result"
 msgstr ""

-#: ../../docs/community/contributing/updating_the_class_reference.rst:239
+#: ../../docs/community/contributing/updating_the_class_reference.rst:240
 msgid "[Class]"
 msgstr ""

-#: ../../docs/community/contributing/updating_the_class_reference.rst:239
+#: ../../docs/community/contributing/updating_the_class_reference.rst:240
 msgid "Link a class"
 msgstr ""

-#: ../../docs/community/contributing/updating_the_class_reference.rst:239
+#: ../../docs/community/contributing/updating_the_class_reference.rst:240
 msgid "Move the [Sprite]."
 msgstr ""

-#: ../../docs/community/contributing/updating_the_class_reference.rst:239
+#: ../../docs/community/contributing/updating_the_class_reference.rst:240
 msgid "Move the :ref:`class_sprite`."
 msgstr ""

-#: ../../docs/community/contributing/updating_the_class_reference.rst:241
+#: ../../docs/community/contributing/updating_the_class_reference.rst:242
 msgid "[method methodname]"
 msgstr ""

-#: ../../docs/community/contributing/updating_the_class_reference.rst:241
+#: ../../docs/community/contributing/updating_the_class_reference.rst:242
 msgid "Link to a method in this class"
 msgstr ""

-#: ../../docs/community/contributing/updating_the_class_reference.rst:241
+#: ../../docs/community/contributing/updating_the_class_reference.rst:242
 msgid "Call [method hide]."
 msgstr ""

-#: ../../docs/community/contributing/updating_the_class_reference.rst:241
-#: ../../docs/community/contributing/updating_the_class_reference.rst:243
+#: ../../docs/community/contributing/updating_the_class_reference.rst:242
+#: ../../docs/community/contributing/updating_the_class_reference.rst:244
 msgid "See :ref:`hide <class_spatial_method_hide>`."
 msgstr ""

-#: ../../docs/community/contributing/updating_the_class_reference.rst:243
+#: ../../docs/community/contributing/updating_the_class_reference.rst:244
 msgid "[method Class.methodname]"
 msgstr ""

-#: ../../docs/community/contributing/updating_the_class_reference.rst:243
+#: ../../docs/community/contributing/updating_the_class_reference.rst:244
 msgid "Link to another class's method"
 msgstr ""

-#: ../../docs/community/contributing/updating_the_class_reference.rst:243
+#: ../../docs/community/contributing/updating_the_class_reference.rst:244
 msgid "Call [method Spatial.hide]."
 msgstr ""

-#: ../../docs/community/contributing/updating_the_class_reference.rst:245
+#: ../../docs/community/contributing/updating_the_class_reference.rst:246
 msgid "[member membername]"
 msgstr ""

-#: ../../docs/community/contributing/updating_the_class_reference.rst:245
+#: ../../docs/community/contributing/updating_the_class_reference.rst:246
 msgid "Link to a member in this class"
 msgstr ""

-#: ../../docs/community/contributing/updating_the_class_reference.rst:245
+#: ../../docs/community/contributing/updating_the_class_reference.rst:246
 msgid "Get [member scale]."
 msgstr ""

-#: ../../docs/community/contributing/updating_the_class_reference.rst:245
-#: ../../docs/community/contributing/updating_the_class_reference.rst:247
+#: ../../docs/community/contributing/updating_the_class_reference.rst:246
+#: ../../docs/community/contributing/updating_the_class_reference.rst:248
 msgid "Get :ref:`scale <class_node2d_property_scale>`."
 msgstr ""

-#: ../../docs/community/contributing/updating_the_class_reference.rst:247
+#: ../../docs/community/contributing/updating_the_class_reference.rst:248
 msgid "[member Class.membername]"
 msgstr ""

-#: ../../docs/community/contributing/updating_the_class_reference.rst:247
+#: ../../docs/community/contributing/updating_the_class_reference.rst:248
 msgid "Link to another class's member"
 msgstr ""

-#: ../../docs/community/contributing/updating_the_class_reference.rst:247
+#: ../../docs/community/contributing/updating_the_class_reference.rst:248
 msgid "Get [member Node2D.scale]."
 msgstr ""

-#: ../../docs/community/contributing/updating_the_class_reference.rst:249
+#: ../../docs/community/contributing/updating_the_class_reference.rst:250
 msgid "[signal signalname]"
 msgstr ""

-#: ../../docs/community/contributing/updating_the_class_reference.rst:249
+#: ../../docs/community/contributing/updating_the_class_reference.rst:250
 msgid "Link to a signal in this class"
 msgstr ""

-#: ../../docs/community/contributing/updating_the_class_reference.rst:249
+#: ../../docs/community/contributing/updating_the_class_reference.rst:250
 msgid "Emit [signal renamed]."
 msgstr ""

-#: ../../docs/community/contributing/updating_the_class_reference.rst:249
-#: ../../docs/community/contributing/updating_the_class_reference.rst:251
+#: ../../docs/community/contributing/updating_the_class_reference.rst:250
+#: ../../docs/community/contributing/updating_the_class_reference.rst:252
 msgid "Emit :ref:`renamed <class_node_signal_renamed>`."
 msgstr ""

-#: ../../docs/community/contributing/updating_the_class_reference.rst:251
+#: ../../docs/community/contributing/updating_the_class_reference.rst:252
 msgid "[signal Class.signalname]"
 msgstr ""

-#: ../../docs/community/contributing/updating_the_class_reference.rst:251
+#: ../../docs/community/contributing/updating_the_class_reference.rst:252
 msgid "Link to another class's signal"
 msgstr ""

-#: ../../docs/community/contributing/updating_the_class_reference.rst:251
+#: ../../docs/community/contributing/updating_the_class_reference.rst:252
 msgid "Emit [signal Node.renamed]."
 msgstr ""

-#: ../../docs/community/contributing/updating_the_class_reference.rst:253
+#: ../../docs/community/contributing/updating_the_class_reference.rst:254
 msgid "[b] [/b]"
 msgstr ""

-#: ../../docs/community/contributing/updating_the_class_reference.rst:253
+#: ../../docs/community/contributing/updating_the_class_reference.rst:254
 msgid "Bold"
 msgstr ""

-#: ../../docs/community/contributing/updating_the_class_reference.rst:253
+#: ../../docs/community/contributing/updating_the_class_reference.rst:254
 msgid "Some [b]bold[/b] text."
 msgstr ""

-#: ../../docs/community/contributing/updating_the_class_reference.rst:253
+#: ../../docs/community/contributing/updating_the_class_reference.rst:254
 msgid "Some **bold** text."
 msgstr ""

-#: ../../docs/community/contributing/updating_the_class_reference.rst:255
+#: ../../docs/community/contributing/updating_the_class_reference.rst:256
 msgid "[i] [/i]"
 msgstr ""

-#: ../../docs/community/contributing/updating_the_class_reference.rst:255
+#: ../../docs/community/contributing/updating_the_class_reference.rst:256
 msgid "Italic"
 msgstr ""

-#: ../../docs/community/contributing/updating_the_class_reference.rst:255
+#: ../../docs/community/contributing/updating_the_class_reference.rst:256
 msgid "Some [i]italic[/i] text."
 msgstr ""

-#: ../../docs/community/contributing/updating_the_class_reference.rst:255
+#: ../../docs/community/contributing/updating_the_class_reference.rst:256
 msgid "Some *italic* text."
 msgstr ""

-#: ../../docs/community/contributing/updating_the_class_reference.rst:257
+#: ../../docs/community/contributing/updating_the_class_reference.rst:258
 msgid "[code] [/code]"
 msgstr ""

-#: ../../docs/community/contributing/updating_the_class_reference.rst:257
+#: ../../docs/community/contributing/updating_the_class_reference.rst:258
 msgid "Monospace"
 msgstr ""

-#: ../../docs/community/contributing/updating_the_class_reference.rst:257
+#: ../../docs/community/contributing/updating_the_class_reference.rst:258
 msgid "Some [code]monospace[/code] text."
 msgstr ""

-#: ../../docs/community/contributing/updating_the_class_reference.rst:257
+#: ../../docs/community/contributing/updating_the_class_reference.rst:258
 msgid "Some ``monospace`` text."
 msgstr ""

-#: ../../docs/community/contributing/updating_the_class_reference.rst:259
+#: ../../docs/community/contributing/updating_the_class_reference.rst:260
 msgid "[kbd] [/kbd]"
 msgstr ""

-#: ../../docs/community/contributing/updating_the_class_reference.rst:259
+#: ../../docs/community/contributing/updating_the_class_reference.rst:260
 msgid "Keyboard/mouse shortcut"
 msgstr ""

-#: ../../docs/community/contributing/updating_the_class_reference.rst:259
+#: ../../docs/community/contributing/updating_the_class_reference.rst:260
 msgid "Some [kbd]Ctrl + C[/kbd] key."
 msgstr ""

-#: ../../docs/community/contributing/updating_the_class_reference.rst:259
+#: ../../docs/community/contributing/updating_the_class_reference.rst:260
 msgid "Some :kbd:`Ctrl + C` key."
 msgstr ""

-#: ../../docs/community/contributing/updating_the_class_reference.rst:261
+#: ../../docs/community/contributing/updating_the_class_reference.rst:262
 msgid "[codeblock] [/codeblock]"
 msgstr ""

-#: ../../docs/community/contributing/updating_the_class_reference.rst:261
+#: ../../docs/community/contributing/updating_the_class_reference.rst:262
 msgid "Multiline preformatted block"
 msgstr ""

-#: ../../docs/community/contributing/updating_the_class_reference.rst:261
-#: ../../docs/community/contributing/updating_the_class_reference.rst:261
+#: ../../docs/community/contributing/updating_the_class_reference.rst:262
+#: ../../docs/community/contributing/updating_the_class_reference.rst:262
 msgid "*See below.*"
 msgstr ""

-#: ../../docs/community/contributing/updating_the_class_reference.rst:264
+#: ../../docs/community/contributing/updating_the_class_reference.rst:265
 msgid "Use ``[codeblock]`` for pre-formatted code blocks. Inside ``[codeblock]``, always use **four spaces** for indentation (the parser will delete tabs). Example:"
 msgstr ""

-#: ../../docs/community/contributing/updating_the_class_reference.rst:274
+#: ../../docs/community/contributing/updating_the_class_reference.rst:275
 msgid "Will display as:"
 msgstr ""

-#: ../../docs/community/contributing/updating_the_class_reference.rst:284
+#: ../../docs/community/contributing/updating_the_class_reference.rst:285
 msgid "I don't know what this method does!"
 msgstr ""

-#: ../../docs/community/contributing/updating_the_class_reference.rst:286
+#: ../../docs/community/contributing/updating_the_class_reference.rst:287
 msgid "No problem. Leave it behind, and list the methods you skipped when you request a pull of your changes. Another writer will take care of it."
 msgstr ""

-#: ../../docs/community/contributing/updating_the_class_reference.rst:288
+#: ../../docs/community/contributing/updating_the_class_reference.rst:289
 msgid "You can still have a look at the methods' implementation in Godot's source code on GitHub. Also, if you have doubts, feel free to ask on the `Q&A website <https://godotengine.org/qa/>`__ and on IRC (freenode, #godotengine)."
 msgstr ""

-#: ../../docs/community/contributing/updating_the_class_reference.rst:292
+#: ../../docs/community/contributing/updating_the_class_reference.rst:293
 msgid "Localization"
 msgstr ""

-#: ../../docs/community/contributing/updating_the_class_reference.rst:294
+#: ../../docs/community/contributing/updating_the_class_reference.rst:295
 msgid "The documentation can be translated in any language on `Hosted Weblate <https://hosted.weblate.org/projects/godot-engine/godot-docs/>`__."
 msgstr ""

-#: ../../docs/community/contributing/updating_the_class_reference.rst:297
+#: ../../docs/community/contributing/updating_the_class_reference.rst:298
 msgid "Translated strings are synced manually by documentation maintainers in the `godot-docs-l10n <https://github.com/godotengine/godot-docs-l10n>`__ repository."
 msgstr ""

-#: ../../docs/community/contributing/updating_the_class_reference.rst:301
+#: ../../docs/community/contributing/updating_the_class_reference.rst:302
 msgid "Languages with a good level of completion have their own localized instances of ReadTheDocs. Open an issue on the ``godot-docs-l10n`` repository if you think that a new language is complete enough to get its own instance."
 msgstr ""

--- a/sphinx/templates/community/contributing/ways_to_contribute.pot
+++ b/sphinx/templates/community/contributing/ways_to_contribute.pot
@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2020-07-06 14:52+0200\n"
+"POT-Creation-Date: 2020-07-30 19:14+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
@@ -168,3 +168,15 @@ msgstr ""
 msgid "**The tutorials and engine documentation and its translations.** This is the part you are reading now, which is distributed in the HTML, PDF and EPUB formats. 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_documentation_guidelines` for more details."
 msgstr ""

+#: ../../docs/community/contributing/ways_to_contribute.rst:195
+msgid "Contributing translations"
+msgstr ""
+
+#: ../../docs/community/contributing/ways_to_contribute.rst:197
+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/community/contributing/ways_to_contribute.rst:201
+msgid "See :ref:`doc_editor_and_docs_localization` for more details."
+msgstr ""
+
--- a/sphinx/templates/community/tutorials.pot
+++ b/sphinx/templates/community/tutorials.pot
@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2020-07-06 14:52+0200\n"
+"POT-Creation-Date: 2020-07-30 19:14+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
--- a/sphinx/templates/development/compiling/compiling_for_android.pot
+++ b/sphinx/templates/development/compiling/compiling_for_android.pot
@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2020-07-06 14:52+0200\n"
+"POT-Creation-Date: 2020-07-30 19:14+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
--- a/sphinx/templates/development/compiling/compiling_for_ios.pot
+++ b/sphinx/templates/development/compiling/compiling_for_ios.pot
@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2020-07-06 14:52+0200\n"
+"POT-Creation-Date: 2020-07-30 19:14+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
--- a/sphinx/templates/development/compiling/compiling_for_osx.pot
+++ b/sphinx/templates/development/compiling/compiling_for_osx.pot
@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2020-07-06 14:52+0200\n"
+"POT-Creation-Date: 2020-07-30 19:14+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
--- a/sphinx/templates/development/compiling/compiling_for_uwp.pot
+++ b/sphinx/templates/development/compiling/compiling_for_uwp.pot
@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2020-07-06 14:52+0200\n"
+"POT-Creation-Date: 2020-07-30 19:14+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
--- a/sphinx/templates/development/compiling/compiling_for_web.pot
+++ b/sphinx/templates/development/compiling/compiling_for_web.pot
@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2020-07-06 14:52+0200\n"
+"POT-Creation-Date: 2020-07-30 19:14+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
--- a/sphinx/templates/development/compiling/compiling_for_windows.pot
+++ b/sphinx/templates/development/compiling/compiling_for_windows.pot
@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2020-07-06 14:52+0200\n"
+"POT-Creation-Date: 2020-07-30 19:14+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
--- a/sphinx/templates/development/compiling/compiling_for_x11.pot
+++ b/sphinx/templates/development/compiling/compiling_for_x11.pot
@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2020-07-06 14:52+0200\n"
+"POT-Creation-Date: 2020-07-30 19:14+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
--- a/sphinx/templates/development/compiling/compiling_with_mono.pot
+++ b/sphinx/templates/development/compiling/compiling_with_mono.pot
@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2020-07-06 14:52+0200\n"
+"POT-Creation-Date: 2020-07-30 19:14+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
--- a/sphinx/templates/development/compiling/compiling_with_script_encryption_key.pot
+++ b/sphinx/templates/development/compiling/compiling_with_script_encryption_key.pot
@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2020-07-06 14:52+0200\n"
+"POT-Creation-Date: 2020-07-30 19:14+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
--- a/sphinx/templates/development/compiling/cross-compiling_for_ios_on_linux.pot
+++ b/sphinx/templates/development/compiling/cross-compiling_for_ios_on_linux.pot
@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2020-07-06 14:52+0200\n"
+"POT-Creation-Date: 2020-07-30 19:14+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
--- a/sphinx/templates/development/compiling/getting_source.pot
+++ b/sphinx/templates/development/compiling/getting_source.pot
@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2020-07-06 14:52+0200\n"
+"POT-Creation-Date: 2020-07-30 19:14+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
--- a/sphinx/templates/development/compiling/index.pot
+++ b/sphinx/templates/development/compiling/index.pot
@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2020-07-06 14:52+0200\n"
+"POT-Creation-Date: 2020-07-30 19:14+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
--- a/sphinx/templates/development/compiling/introduction_to_the_buildsystem.pot
+++ b/sphinx/templates/development/compiling/introduction_to_the_buildsystem.pot
@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2020-07-06 14:52+0200\n"
+"POT-Creation-Date: 2020-07-30 19:14+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
--- a/sphinx/templates/development/compiling/optimizing_for_size.pot
+++ b/sphinx/templates/development/compiling/optimizing_for_size.pot
@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2020-07-06 14:52+0200\n"
+"POT-Creation-Date: 2020-07-30 19:14+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
--- a/sphinx/templates/development/cpp/binding_to_external_libraries.pot
+++ b/sphinx/templates/development/cpp/binding_to_external_libraries.pot
@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2020-07-06 14:52+0200\n"
+"POT-Creation-Date: 2020-07-30 19:14+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
--- a/sphinx/templates/development/cpp/common_engine_methods_and_macros.pot
+++ b/sphinx/templates/development/cpp/common_engine_methods_and_macros.pot
@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2020-07-06 14:52+0200\n"
+"POT-Creation-Date: 2020-07-30 19:14+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
--- a/sphinx/templates/development/cpp/configuring_an_ide/android_studio.pot
+++ b/sphinx/templates/development/cpp/configuring_an_ide/android_studio.pot
@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2020-07-06 14:52+0200\n"
+"POT-Creation-Date: 2020-07-30 19:14+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
--- a/sphinx/templates/development/cpp/configuring_an_ide/clion.pot
+++ b/sphinx/templates/development/cpp/configuring_an_ide/clion.pot
@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2020-07-06 14:52+0200\n"
+"POT-Creation-Date: 2020-07-30 19:14+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
--- a/sphinx/templates/development/cpp/configuring_an_ide/code_blocks.pot
+++ b/sphinx/templates/development/cpp/configuring_an_ide/code_blocks.pot
@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2020-07-06 14:52+0200\n"
+"POT-Creation-Date: 2020-07-30 19:14+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
--- a/sphinx/templates/development/cpp/configuring_an_ide/index.pot
+++ b/sphinx/templates/development/cpp/configuring_an_ide/index.pot
@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2020-07-06 14:52+0200\n"
+"POT-Creation-Date: 2020-07-30 19:14+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
--- a/sphinx/templates/development/cpp/configuring_an_ide/kdevelop.pot
+++ b/sphinx/templates/development/cpp/configuring_an_ide/kdevelop.pot
@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2020-07-06 14:52+0200\n"
+"POT-Creation-Date: 2020-07-30 19:14+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
--- a/sphinx/templates/development/cpp/configuring_an_ide/qt_creator.pot
+++ b/sphinx/templates/development/cpp/configuring_an_ide/qt_creator.pot
@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2020-07-06 14:52+0200\n"
+"POT-Creation-Date: 2020-07-30 19:14+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
--- a/sphinx/templates/development/cpp/configuring_an_ide/visual_studio.pot
+++ b/sphinx/templates/development/cpp/configuring_an_ide/visual_studio.pot
@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2020-07-06 14:52+0200\n"
+"POT-Creation-Date: 2020-07-30 19:14+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
--- a/sphinx/templates/development/cpp/configuring_an_ide/visual_studio_code.pot
+++ b/sphinx/templates/development/cpp/configuring_an_ide/visual_studio_code.pot
@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2020-07-06 14:52+0200\n"
+"POT-Creation-Date: 2020-07-30 19:14+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
--- a/sphinx/templates/development/cpp/configuring_an_ide/xcode.pot
+++ b/sphinx/templates/development/cpp/configuring_an_ide/xcode.pot
@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2020-07-06 14:52+0200\n"
+"POT-Creation-Date: 2020-07-30 19:14+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
--- a/sphinx/templates/development/cpp/core_types.pot
+++ b/sphinx/templates/development/cpp/core_types.pot
@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2020-07-06 14:52+0200\n"
+"POT-Creation-Date: 2020-07-30 19:14+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
--- a/sphinx/templates/development/cpp/custom_audiostreams.pot
+++ b/sphinx/templates/development/cpp/custom_audiostreams.pot
@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2020-07-06 14:52+0200\n"
+"POT-Creation-Date: 2020-07-30 19:14+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
--- a/sphinx/templates/development/cpp/custom_godot_servers.pot
+++ b/sphinx/templates/development/cpp/custom_godot_servers.pot
@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2020-07-06 14:52+0200\n"
+"POT-Creation-Date: 2020-07-30 19:14+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
--- a/sphinx/templates/development/cpp/custom_modules_in_cpp.pot
+++ b/sphinx/templates/development/cpp/custom_modules_in_cpp.pot
@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2020-07-06 14:52+0200\n"
+"POT-Creation-Date: 2020-07-30 19:14+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
--- a/sphinx/templates/development/cpp/custom_resource_format_loaders.pot
+++ b/sphinx/templates/development/cpp/custom_resource_format_loaders.pot
@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2020-07-06 14:52+0200\n"
+"POT-Creation-Date: 2020-07-30 19:14+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
--- a/sphinx/templates/development/cpp/index.pot
+++ b/sphinx/templates/development/cpp/index.pot
@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2020-07-06 14:52+0200\n"
+"POT-Creation-Date: 2020-07-30 19:14+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
--- a/sphinx/templates/development/cpp/inheritance_class_tree.pot
+++ b/sphinx/templates/development/cpp/inheritance_class_tree.pot
@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2020-07-06 14:52+0200\n"
+"POT-Creation-Date: 2020-07-30 19:14+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
--- a/sphinx/templates/development/cpp/introduction_to_godot_development.pot
+++ b/sphinx/templates/development/cpp/introduction_to_godot_development.pot
@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2020-07-06 14:52+0200\n"
+"POT-Creation-Date: 2020-07-30 19:14+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
--- a/sphinx/templates/development/cpp/object_class.pot
+++ b/sphinx/templates/development/cpp/object_class.pot
@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2020-07-06 14:52+0200\n"
+"POT-Creation-Date: 2020-07-30 19:14+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
@@ -20,256 +20,260 @@ msgstr ""
 msgid "Object class"
 msgstr ""

-#: ../../docs/development/cpp/object_class.rst:7
+#: ../../docs/development/cpp/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/development/cpp/object_class.rst:12
 msgid "General definition"
 msgstr ""

-#: ../../docs/development/cpp/object_class.rst:9
+#: ../../docs/development/cpp/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/development/cpp/object_class.rst:21
+#: ../../docs/development/cpp/object_class.rst:26
 msgid "This makes Objects gain a lot of functionality, like for example"
 msgstr ""

-#: ../../docs/development/cpp/object_class.rst:31
-#: ../../docs/development/cpp/object_class.rst:89
-#: ../../docs/development/cpp/object_class.rst:254
-#: ../../docs/development/cpp/object_class.rst:270
-#: ../../docs/development/cpp/object_class.rst:291
-#: ../../docs/development/cpp/object_class.rst:310
+#: ../../docs/development/cpp/object_class.rst:36
+#: ../../docs/development/cpp/object_class.rst:94
+#: ../../docs/development/cpp/object_class.rst:259
+#: ../../docs/development/cpp/object_class.rst:275
+#: ../../docs/development/cpp/object_class.rst:296
+#: ../../docs/development/cpp/object_class.rst:315
 msgid "References:"
 msgstr ""

-#: ../../docs/development/cpp/object_class.rst:33
+#: ../../docs/development/cpp/object_class.rst:38
 msgid "`core/object.h <https://github.com/godotengine/godot/blob/master/core/object.h>`__"
 msgstr ""

-#: ../../docs/development/cpp/object_class.rst:36
+#: ../../docs/development/cpp/object_class.rst:41
 msgid "Registering an Object"
 msgstr ""

-#: ../../docs/development/cpp/object_class.rst:38
+#: ../../docs/development/cpp/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/development/cpp/object_class.rst:42
+#: ../../docs/development/cpp/object_class.rst:47
 msgid "Classes are registered by calling:"
 msgstr ""

-#: ../../docs/development/cpp/object_class.rst:48
+#: ../../docs/development/cpp/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/development/cpp/object_class.rst:51
+#: ../../docs/development/cpp/object_class.rst:56
 msgid "Registering as virtual is the same but it can't be instanced."
 msgstr ""

-#: ../../docs/development/cpp/object_class.rst:57
+#: ../../docs/development/cpp/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/development/cpp/object_class.rst:64
+#: ../../docs/development/cpp/object_class.rst:69
 msgid "Inside ``_bind_methods``, there are a couple of things that can be done. Registering functions is one:"
 msgstr ""

-#: ../../docs/development/cpp/object_class.rst:71
+#: ../../docs/development/cpp/object_class.rst:76
 msgid "Default values for arguments can be passed in reverse order:"
 msgstr ""

-#: ../../docs/development/cpp/object_class.rst:77
+#: ../../docs/development/cpp/object_class.rst:82
 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/development/cpp/object_class.rst:82
+#: ../../docs/development/cpp/object_class.rst:87
 msgid "Check ``_bind_methods`` of Control or Object for more examples."
 msgstr ""

-#: ../../docs/development/cpp/object_class.rst:84
+#: ../../docs/development/cpp/object_class.rst:89
 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/development/cpp/object_class.rst:91
+#: ../../docs/development/cpp/object_class.rst:96
 msgid "`core/class_db.h <https://github.com/godotengine/godot/blob/master/core/class_db.h>`__"
 msgstr ""

-#: ../../docs/development/cpp/object_class.rst:94
+#: ../../docs/development/cpp/object_class.rst:99
 msgid "Constants"
 msgstr ""

-#: ../../docs/development/cpp/object_class.rst:96
+#: ../../docs/development/cpp/object_class.rst:101
 msgid "Classes often have enums such as:"
 msgstr ""

-#: ../../docs/development/cpp/object_class.rst:105
+#: ../../docs/development/cpp/object_class.rst:110
 msgid "For these to work when binding to methods, the enum must be declared convertible to int, for this a macro is provided:"
 msgstr ""

-#: ../../docs/development/cpp/object_class.rst:112
+#: ../../docs/development/cpp/object_class.rst:117
 msgid "The constants can also be bound inside ``_bind_methods``, by using:"
 msgstr ""

-#: ../../docs/development/cpp/object_class.rst:120
+#: ../../docs/development/cpp/object_class.rst:125
 msgid "Properties (set/get)"
 msgstr ""

-#: ../../docs/development/cpp/object_class.rst:122
+#: ../../docs/development/cpp/object_class.rst:127
 msgid "Objects export properties, properties are useful for the following:"
 msgstr ""

-#: ../../docs/development/cpp/object_class.rst:124
+#: ../../docs/development/cpp/object_class.rst:129
 msgid "Serializing and deserializing the object."
 msgstr ""

-#: ../../docs/development/cpp/object_class.rst:125
+#: ../../docs/development/cpp/object_class.rst:130
 msgid "Creating a list of editable values for the Object derived class."
 msgstr ""

-#: ../../docs/development/cpp/object_class.rst:127
+#: ../../docs/development/cpp/object_class.rst:132
 msgid "Properties are usually defined by the PropertyInfo() class. Usually constructed as:"
 msgstr ""

-#: ../../docs/development/cpp/object_class.rst:134
+#: ../../docs/development/cpp/object_class.rst:139
 msgid "For example:"
 msgstr ""

-#: ../../docs/development/cpp/object_class.rst:140
+#: ../../docs/development/cpp/object_class.rst:145
 msgid "This is an integer property, named \"amount\", hint is a range, range goes from 0 to 49 in steps of 1 (integers). It is only usable for the editor (edit value visually) but won't be serialized."
 msgstr ""

-#: ../../docs/development/cpp/object_class.rst:144
+#: ../../docs/development/cpp/object_class.rst:149
 msgid "Another example:"
 msgstr ""

-#: ../../docs/development/cpp/object_class.rst:150
+#: ../../docs/development/cpp/object_class.rst:155
 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/development/cpp/object_class.rst:154
+#: ../../docs/development/cpp/object_class.rst:159
 msgid "There are plenty of hints and usage flags available in object.h, give them a check."
 msgstr ""

-#: ../../docs/development/cpp/object_class.rst:157
+#: ../../docs/development/cpp/object_class.rst:162
 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/development/cpp/object_class.rst:163
+#: ../../docs/development/cpp/object_class.rst:168
 msgid "From ``_bind_methods()``, properties can be created and bound as long as set/get functions exist. Example:"
 msgstr ""

-#: ../../docs/development/cpp/object_class.rst:170
+#: ../../docs/development/cpp/object_class.rst:175
 msgid "This creates the property using the setter and the getter."
 msgstr ""

-#: ../../docs/development/cpp/object_class.rst:175
+#: ../../docs/development/cpp/object_class.rst:180
 msgid "Binding properties using ``_set``/``_get``/``_get_property_list``"
 msgstr ""

-#: ../../docs/development/cpp/object_class.rst:177
+#: ../../docs/development/cpp/object_class.rst:182
 msgid "An additional method of creating properties exists when more flexibility is desired (i.e. adding or removing properties on context)."
 msgstr ""

-#: ../../docs/development/cpp/object_class.rst:180
+#: ../../docs/development/cpp/object_class.rst:185
 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/development/cpp/object_class.rst:192
+#: ../../docs/development/cpp/object_class.rst:197
 msgid "This is also a little less efficient since ``p_property`` must be compared against the desired names in serial order."
 msgstr ""

-#: ../../docs/development/cpp/object_class.rst:196
+#: ../../docs/development/cpp/object_class.rst:201
 msgid "Dynamic casting"
 msgstr ""

-#: ../../docs/development/cpp/object_class.rst:198
+#: ../../docs/development/cpp/object_class.rst:203
 msgid "Godot provides dynamic casting between Object-derived classes, for example:"
 msgstr ""

-#: ../../docs/development/cpp/object_class.rst:208
+#: ../../docs/development/cpp/object_class.rst:213
 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/development/cpp/object_class.rst:214
+#: ../../docs/development/cpp/object_class.rst:219
 msgid "Signals"
 msgstr ""

-#: ../../docs/development/cpp/object_class.rst:216
+#: ../../docs/development/cpp/object_class.rst:221
 msgid "Objects can have a set of signals defined (similar to Delegates in other languages). Connecting to them is rather easy:"
 msgstr ""

-#: ../../docs/development/cpp/object_class.rst:225
+#: ../../docs/development/cpp/object_class.rst:230
 msgid "The method ``_node_entered_tree`` must be registered to the class using ``ClassDB::bind_method`` (explained before)."
 msgstr ""

-#: ../../docs/development/cpp/object_class.rst:228
+#: ../../docs/development/cpp/object_class.rst:233
 msgid "Adding signals to a class is done in ``_bind_methods``, using the ``ADD_SIGNAL`` macro, for example:"
 msgstr ""

-#: ../../docs/development/cpp/object_class.rst:236
+#: ../../docs/development/cpp/object_class.rst:241
 msgid "References"
 msgstr ""

-#: ../../docs/development/cpp/object_class.rst:238
+#: ../../docs/development/cpp/object_class.rst:243
 msgid ":ref:`Reference <class_reference>` 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/development/cpp/object_class.rst:250
+#: ../../docs/development/cpp/object_class.rst:255
 msgid "``myref`` is reference counted. It will be freed when no more Ref<> templates point to it."
 msgstr ""

-#: ../../docs/development/cpp/object_class.rst:256
+#: ../../docs/development/cpp/object_class.rst:261
 msgid "`core/reference.h <https://github.com/godotengine/godot/blob/master/core/reference.h>`__"
 msgstr ""

-#: ../../docs/development/cpp/object_class.rst:259
+#: ../../docs/development/cpp/object_class.rst:264
 msgid "Resources:"
 msgstr ""

-#: ../../docs/development/cpp/object_class.rst:261
+#: ../../docs/development/cpp/object_class.rst:266
 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)``. This is normally done by the resource loader though. No two different resources can have the same path, attempt to do so will result in an error."
 msgstr ""

-#: ../../docs/development/cpp/object_class.rst:267
+#: ../../docs/development/cpp/object_class.rst:272
 msgid "Resources without a path are fine too."
 msgstr ""

-#: ../../docs/development/cpp/object_class.rst:272
+#: ../../docs/development/cpp/object_class.rst:277
 msgid "`core/resource.h <https://github.com/godotengine/godot/blob/master/core/resource.h>`__"
 msgstr ""

-#: ../../docs/development/cpp/object_class.rst:275
+#: ../../docs/development/cpp/object_class.rst:280
 msgid "Resource loading"
 msgstr ""

-#: ../../docs/development/cpp/object_class.rst:277
+#: ../../docs/development/cpp/object_class.rst:282
 msgid "Resources can be loaded with the ResourceLoader API, like this:"
 msgstr ""

-#: ../../docs/development/cpp/object_class.rst:283
+#: ../../docs/development/cpp/object_class.rst:288
 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/development/cpp/object_class.rst:288
+#: ../../docs/development/cpp/object_class.rst:293
 msgid "resourceinteractiveloader (TODO)"
 msgstr ""

-#: ../../docs/development/cpp/object_class.rst:293
+#: ../../docs/development/cpp/object_class.rst:298
 msgid "`core/io/resource_loader.h <https://github.com/godotengine/godot/blob/master/core/io/resource_loader.h>`__"
 msgstr ""

-#: ../../docs/development/cpp/object_class.rst:296
+#: ../../docs/development/cpp/object_class.rst:301
 msgid "Resource saving"
 msgstr ""

-#: ../../docs/development/cpp/object_class.rst:298
+#: ../../docs/development/cpp/object_class.rst:303
 msgid "Saving a resource can be done with the resource saver API:"
 msgstr ""

-#: ../../docs/development/cpp/object_class.rst:304
+#: ../../docs/development/cpp/object_class.rst:309
 msgid "Instance will be saved. 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/development/cpp/object_class.rst:312
+#: ../../docs/development/cpp/object_class.rst:317
 msgid "`core/io/resource_saver.h <https://github.com/godotengine/godot/blob/master/core/io/resource_saver.h>`__"
 msgstr ""

--- a/sphinx/templates/development/cpp/variant_class.pot
+++ b/sphinx/templates/development/cpp/variant_class.pot
@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2020-07-06 14:52+0200\n"
+"POT-Creation-Date: 2020-07-30 19:14+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
--- a/sphinx/templates/development/editor/creating_icons.pot
+++ b/sphinx/templates/development/editor/creating_icons.pot
@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2020-07-06 14:52+0200\n"
+"POT-Creation-Date: 2020-07-30 19:14+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
--- a/sphinx/templates/development/editor/editor_style_guide.pot
+++ b/sphinx/templates/development/editor/editor_style_guide.pot
@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2020-07-06 14:52+0200\n"
+"POT-Creation-Date: 2020-07-30 19:14+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
--- a/sphinx/templates/development/editor/index.pot
+++ b/sphinx/templates/development/editor/index.pot
@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2020-07-06 14:52+0200\n"
+"POT-Creation-Date: 2020-07-30 19:14+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
--- a/sphinx/templates/development/file_formats/gdscript_grammar.pot
+++ b/sphinx/templates/development/file_formats/gdscript_grammar.pot
@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2020-07-06 14:52+0200\n"
+"POT-Creation-Date: 2020-07-30 19:14+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
--- a/sphinx/templates/development/file_formats/index.pot
+++ b/sphinx/templates/development/file_formats/index.pot
@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2020-07-06 14:52+0200\n"
+"POT-Creation-Date: 2020-07-30 19:14+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
--- a/sphinx/templates/development/file_formats/tscn.pot
+++ b/sphinx/templates/development/file_formats/tscn.pot
@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2020-07-06 14:52+0200\n"
+"POT-Creation-Date: 2020-07-30 19:14+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
@@ -16,418 +16,418 @@ msgstr ""
 "Content-Type: text/plain; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"

-#: ../../docs/development/file_formats/tscn.rst:2
+#: ../../docs/development/file_formats/tscn.rst:4
 msgid "TSCN file format"
 msgstr ""

-#: ../../docs/development/file_formats/tscn.rst:4
+#: ../../docs/development/file_formats/tscn.rst:6
 msgid "The TSCN (text scene) file format represents a single scene tree inside Godot. TSCN files have the advantage of being mostly human-readable and easy for version control systems to manage. During import, TSCN files are compiled into binary ``.scn`` files stored inside the .import folder. This reduces the data size and speeds up loading."
 msgstr ""

-#: ../../docs/development/file_formats/tscn.rst:10
+#: ../../docs/development/file_formats/tscn.rst:12
 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."
 msgstr ""

-#: ../../docs/development/file_formats/tscn.rst:14
+#: ../../docs/development/file_formats/tscn.rst:16
 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/development/file_formats/tscn.rst:19
+#: ../../docs/development/file_formats/tscn.rst:21
 msgid "File structure"
 msgstr ""

-#: ../../docs/development/file_formats/tscn.rst:21
+#: ../../docs/development/file_formats/tscn.rst:23
 msgid "There are five main sections inside the TSCN file:"
 msgstr ""

-#: ../../docs/development/file_formats/tscn.rst:23
+#: ../../docs/development/file_formats/tscn.rst:25
 msgid "File Descriptor"
 msgstr ""

-#: ../../docs/development/file_formats/tscn.rst:24
-#: ../../docs/development/file_formats/tscn.rst:273
+#: ../../docs/development/file_formats/tscn.rst:26
+#: ../../docs/development/file_formats/tscn.rst:275
 msgid "External resources"
 msgstr ""

-#: ../../docs/development/file_formats/tscn.rst:25
-#: ../../docs/development/file_formats/tscn.rst:295
+#: ../../docs/development/file_formats/tscn.rst:27
+#: ../../docs/development/file_formats/tscn.rst:297
 msgid "Internal resources"
 msgstr ""

-#: ../../docs/development/file_formats/tscn.rst:26
+#: ../../docs/development/file_formats/tscn.rst:28
 msgid "Nodes"
 msgstr ""

-#: ../../docs/development/file_formats/tscn.rst:27
+#: ../../docs/development/file_formats/tscn.rst:29
 msgid "Connections"
 msgstr ""

-#: ../../docs/development/file_formats/tscn.rst:29
+#: ../../docs/development/file_formats/tscn.rst:31
 msgid "The file descriptor looks like ``[gd_scene load_steps=1 format=2]`` and should be the first entry in the file. The ``load_steps`` parameter should (in theory) be the number of resources within the file. However, in practice, its value seems not to matter."
 msgstr ""

-#: ../../docs/development/file_formats/tscn.rst:34
+#: ../../docs/development/file_formats/tscn.rst:36
 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/development/file_formats/tscn.rst:39
+#: ../../docs/development/file_formats/tscn.rst:41
 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."
 msgstr ""

-#: ../../docs/development/file_formats/tscn.rst:43
+#: ../../docs/development/file_formats/tscn.rst:45
 msgid "Entries inside the file"
 msgstr ""

-#: ../../docs/development/file_formats/tscn.rst:45
+#: ../../docs/development/file_formats/tscn.rst:47
 msgid "A heading looks like ``[<resource_type> key=value key=value key=value ...]`` where resource_type is one of:"
 msgstr ""

-#: ../../docs/development/file_formats/tscn.rst:49
+#: ../../docs/development/file_formats/tscn.rst:51
 msgid "``ext_resource``"
 msgstr ""

-#: ../../docs/development/file_formats/tscn.rst:50
+#: ../../docs/development/file_formats/tscn.rst:52
 msgid "``sub_resource``"
 msgstr ""

-#: ../../docs/development/file_formats/tscn.rst:51
+#: ../../docs/development/file_formats/tscn.rst:53
 msgid "``node``"
 msgstr ""

-#: ../../docs/development/file_formats/tscn.rst:52
+#: ../../docs/development/file_formats/tscn.rst:54
 msgid "``connection``"
 msgstr ""

-#: ../../docs/development/file_formats/tscn.rst:54
+#: ../../docs/development/file_formats/tscn.rst:56
 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 spatial node looks like:"
 msgstr ""

-#: ../../docs/development/file_formats/tscn.rst:65
+#: ../../docs/development/file_formats/tscn.rst:67
 msgid "The scene tree"
 msgstr ""

-#: ../../docs/development/file_formats/tscn.rst:67
+#: ../../docs/development/file_formats/tscn.rst:69
 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 type=\"Camera\" name=\"PlayerCamera\" parent=\"Player/Head\"]``"
 msgstr ""

-#: ../../docs/development/file_formats/tscn.rst:71
+#: ../../docs/development/file_formats/tscn.rst:73
 msgid "Other valid keywords include:"
 msgstr ""

-#: ../../docs/development/file_formats/tscn.rst:73
+#: ../../docs/development/file_formats/tscn.rst:75
 msgid "``instance``"
 msgstr ""

-#: ../../docs/development/file_formats/tscn.rst:74
+#: ../../docs/development/file_formats/tscn.rst:76
 msgid "``instance_placeholder``"
 msgstr ""

-#: ../../docs/development/file_formats/tscn.rst:75
+#: ../../docs/development/file_formats/tscn.rst:77
 msgid "``owner``"
 msgstr ""

-#: ../../docs/development/file_formats/tscn.rst:76
+#: ../../docs/development/file_formats/tscn.rst:78
 msgid "``index`` (if two nodes have the same name)"
 msgstr ""

-#: ../../docs/development/file_formats/tscn.rst:77
+#: ../../docs/development/file_formats/tscn.rst:79
 msgid "``groups``"
 msgstr ""

-#: ../../docs/development/file_formats/tscn.rst:79
+#: ../../docs/development/file_formats/tscn.rst:81
 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/development/file_formats/tscn.rst:95
+#: ../../docs/development/file_formats/tscn.rst:97
 msgid "Similar to the internal resource, the document for each node is currently incomplete. Fortunately, it is easy to find out because you can simply save a file with that node in it. Some example nodes are:"
 msgstr ""

-#: ../../docs/development/file_formats/tscn.rst:134
+#: ../../docs/development/file_formats/tscn.rst:136
 msgid "NodePath"
 msgstr ""

-#: ../../docs/development/file_formats/tscn.rst:136
+#: ../../docs/development/file_formats/tscn.rst:138
 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. For instance, MeshInstance uses ``NodePath()`` to point to its skeleton. Likewise, Animation tracks use ``NodePath()`` to point to node properties to animate."
 msgstr ""

-#: ../../docs/development/file_formats/tscn.rst:161
+#: ../../docs/development/file_formats/tscn.rst:163
 msgid "Skeleton"
 msgstr ""

-#: ../../docs/development/file_formats/tscn.rst:163
+#: ../../docs/development/file_formats/tscn.rst:165
 msgid "The Skeleton node inherits the Spatial node, but also may have a list of bones described in key-value pairs in the format ``bones/Id/Attribute=Value``. The bone attributes consist of:"
 msgstr ""

-#: ../../docs/development/file_formats/tscn.rst:167
+#: ../../docs/development/file_formats/tscn.rst:169
 msgid "``name``"
 msgstr ""

-#: ../../docs/development/file_formats/tscn.rst:168
+#: ../../docs/development/file_formats/tscn.rst:170
 msgid "``parent``"
 msgstr ""

-#: ../../docs/development/file_formats/tscn.rst:169
+#: ../../docs/development/file_formats/tscn.rst:171
 msgid "``rest``"
 msgstr ""

-#: ../../docs/development/file_formats/tscn.rst:170
+#: ../../docs/development/file_formats/tscn.rst:172
 msgid "``pose``"
 msgstr ""

-#: ../../docs/development/file_formats/tscn.rst:171
-#: ../../docs/development/file_formats/tscn.rst:391
+#: ../../docs/development/file_formats/tscn.rst:173
+#: ../../docs/development/file_formats/tscn.rst:393
 msgid "``enabled``"
 msgstr ""

-#: ../../docs/development/file_formats/tscn.rst:172
+#: ../../docs/development/file_formats/tscn.rst:174
 msgid "``bound_children``"
 msgstr ""

-#: ../../docs/development/file_formats/tscn.rst:174
+#: ../../docs/development/file_formats/tscn.rst:176
 msgid "``name`` must be the first attribute of each bone."
 msgstr ""

-#: ../../docs/development/file_formats/tscn.rst:175
+#: ../../docs/development/file_formats/tscn.rst:177
 msgid "``parent`` is the index of parent bone in the bone list, with parent index, the bone list is built to a bone tree."
 msgstr ""

-#: ../../docs/development/file_formats/tscn.rst:177
+#: ../../docs/development/file_formats/tscn.rst:179
 msgid "``rest`` is the transform matrix of bone in its \"resting\" position."
 msgstr ""

-#: ../../docs/development/file_formats/tscn.rst:178
+#: ../../docs/development/file_formats/tscn.rst:180
 msgid "``pose`` is the pose matrix; use ``rest`` as the basis."
 msgstr ""

-#: ../../docs/development/file_formats/tscn.rst:179
+#: ../../docs/development/file_formats/tscn.rst:181
 msgid "``bound_children`` is a list of ``NodePath()`` which point to BoneAttachments belonging to this bone."
 msgstr ""

-#: ../../docs/development/file_formats/tscn.rst:182
+#: ../../docs/development/file_formats/tscn.rst:184
 msgid "Here's an example of a skeleton node with two bones:"
 msgstr ""

-#: ../../docs/development/file_formats/tscn.rst:203
+#: ../../docs/development/file_formats/tscn.rst:205
 msgid "BoneAttachment"
 msgstr ""

-#: ../../docs/development/file_formats/tscn.rst:205
+#: ../../docs/development/file_formats/tscn.rst:207
 msgid "BoneAttachment 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=NameOfBone`` attribute, and the corresponding bone being the parent has the BoneAttachment node in its ``bound_children`` list."
 msgstr ""

-#: ../../docs/development/file_formats/tscn.rst:210
+#: ../../docs/development/file_formats/tscn.rst:212
 msgid "An example of one MeshInstance parented to a bone in Skeleton:"
 msgstr ""

-#: ../../docs/development/file_formats/tscn.rst:235
+#: ../../docs/development/file_formats/tscn.rst:237
 msgid "AnimationPlayer"
 msgstr ""

-#: ../../docs/development/file_formats/tscn.rst:237
+#: ../../docs/development/file_formats/tscn.rst:239
 msgid "AnimationPlayer works as an animation library. It stores animations listed in the format ``anim/Name=SubResource(ResourceId)``; each line refers to an Animation resource. All the animation resources use the root node of AnimationPlayer. The root node is stored as ``root_node=NodePath(Path/To/Node)``."
 msgstr ""

-#: ../../docs/development/file_formats/tscn.rst:257
+#: ../../docs/development/file_formats/tscn.rst:259
 msgid "Resources"
 msgstr ""

-#: ../../docs/development/file_formats/tscn.rst:259
+#: ../../docs/development/file_formats/tscn.rst:261
 msgid "Resources are components that make up the nodes. For example, a MeshInstance node will have an accompanying ArrayMesh resource. The ArrayMesh resource may be either internal or external to the TSCN file."
 msgstr ""

-#: ../../docs/development/file_formats/tscn.rst:263
+#: ../../docs/development/file_formats/tscn.rst:265
 msgid "References to the resources are handled by ``id`` numbers in the resource's heading. 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/development/file_formats/tscn.rst:269
+#: ../../docs/development/file_formats/tscn.rst:271
 msgid "For example, to refer to the resource ``[ext_resource id=3 type=\"PackedScene\" path=....]``, you would use ``ExtResource(3)``."
 msgstr ""

-#: ../../docs/development/file_formats/tscn.rst:275
+#: ../../docs/development/file_formats/tscn.rst:277
 msgid "External resources are links to resources not contained within the TSCN file itself. An external resource consists of a path, a type and an ID."
 msgstr ""

-#: ../../docs/development/file_formats/tscn.rst:278
+#: ../../docs/development/file_formats/tscn.rst:280
 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/development/file_formats/tscn.rst:282
+#: ../../docs/development/file_formats/tscn.rst:284
 msgid "Some example external resources are:"
 msgstr ""

-#: ../../docs/development/file_formats/tscn.rst:290
+#: ../../docs/development/file_formats/tscn.rst:292
 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."
 msgstr ""

-#: ../../docs/development/file_formats/tscn.rst:297
+#: ../../docs/development/file_formats/tscn.rst:299
 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/development/file_formats/tscn.rst:311
+#: ../../docs/development/file_formats/tscn.rst:313
 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/development/file_formats/tscn.rst:316
+#: ../../docs/development/file_formats/tscn.rst:318
 msgid "Unfortunately, documentation on the formats for these subresources isn't complete. Some examples can be found by inspecting saved resource files, but others can only be found by looking through Godot's source."
 msgstr ""

-#: ../../docs/development/file_formats/tscn.rst:321
+#: ../../docs/development/file_formats/tscn.rst:323
 msgid "ArrayMesh"
 msgstr ""

-#: ../../docs/development/file_formats/tscn.rst:323
+#: ../../docs/development/file_formats/tscn.rst:325
 msgid "ArrayMesh consists of several surfaces, each in the format ``surface\\Index={}``. Each surface is a set of vertices and a material."
 msgstr ""

-#: ../../docs/development/file_formats/tscn.rst:326
+#: ../../docs/development/file_formats/tscn.rst:328
 msgid "TSCN files support two surface formats:"
 msgstr ""

-#: ../../docs/development/file_formats/tscn.rst:328
+#: ../../docs/development/file_formats/tscn.rst:330
 msgid "For the old format, each surface has three essential keys:"
 msgstr ""

-#: ../../docs/development/file_formats/tscn.rst:330
+#: ../../docs/development/file_formats/tscn.rst:332
 msgid "``primitive``"
 msgstr ""

-#: ../../docs/development/file_formats/tscn.rst:331
+#: ../../docs/development/file_formats/tscn.rst:333
 msgid "``arrays``"
 msgstr ""

-#: ../../docs/development/file_formats/tscn.rst:332
+#: ../../docs/development/file_formats/tscn.rst:334
 msgid "``morph_arrays``"
 msgstr ""

-#: ../../docs/development/file_formats/tscn.rst:334
+#: ../../docs/development/file_formats/tscn.rst:336
 msgid "``primitive`` is an enumerate variable, ``primitive=4`` which is ``PRIMITIVE_TRIANGLES`` is frequently used."
 msgstr ""

-#: ../../docs/development/file_formats/tscn.rst:337
+#: ../../docs/development/file_formats/tscn.rst:339
 msgid "``arrays`` is a two-dimensional array, it contains:"
 msgstr ""

-#: ../../docs/development/file_formats/tscn.rst:339
+#: ../../docs/development/file_formats/tscn.rst:341
 msgid "Vertex positions array"
 msgstr ""

-#: ../../docs/development/file_formats/tscn.rst:340
+#: ../../docs/development/file_formats/tscn.rst:342
 msgid "Tangents array"
 msgstr ""

-#: ../../docs/development/file_formats/tscn.rst:341
+#: ../../docs/development/file_formats/tscn.rst:343
 msgid "Vertex colors array"
 msgstr ""

-#: ../../docs/development/file_formats/tscn.rst:342
+#: ../../docs/development/file_formats/tscn.rst:344
 msgid "UV array 1"
 msgstr ""

-#: ../../docs/development/file_formats/tscn.rst:343
+#: ../../docs/development/file_formats/tscn.rst:345
 msgid "UV array 2"
 msgstr ""

-#: ../../docs/development/file_formats/tscn.rst:344
+#: ../../docs/development/file_formats/tscn.rst:346
 msgid "Bone indexes array"
 msgstr ""

-#: ../../docs/development/file_formats/tscn.rst:345
+#: ../../docs/development/file_formats/tscn.rst:347
 msgid "Bone weights array"
 msgstr ""

-#: ../../docs/development/file_formats/tscn.rst:346
+#: ../../docs/development/file_formats/tscn.rst:348
 msgid "Vertex indexes array"
 msgstr ""

-#: ../../docs/development/file_formats/tscn.rst:348
+#: ../../docs/development/file_formats/tscn.rst:350
 msgid "``morph_arrays`` is an array of morphs. Each morph is exactly an ``arrays`` without the vertex indexes array."
 msgstr ""

-#: ../../docs/development/file_formats/tscn.rst:351
+#: ../../docs/development/file_formats/tscn.rst:353
 msgid "An example of ArrayMesh:"
 msgstr ""

-#: ../../docs/development/file_formats/tscn.rst:375
+#: ../../docs/development/file_formats/tscn.rst:377
 msgid "Animation"
 msgstr ""

-#: ../../docs/development/file_formats/tscn.rst:377
+#: ../../docs/development/file_formats/tscn.rst:379
 msgid "An animation resource consists of tracks. Besides, it has ``length``, ``loop`` and ``step`` applied to all the tracks."
 msgstr ""

-#: ../../docs/development/file_formats/tscn.rst:380
+#: ../../docs/development/file_formats/tscn.rst:382
 msgid "``length`` and ``step`` are both durations in seconds."
 msgstr ""

-#: ../../docs/development/file_formats/tscn.rst:382
+#: ../../docs/development/file_formats/tscn.rst:384
 msgid "Each track is described by a list of key-value pairs in the format ``tracks/Id/Attribute``. Each track includes:"
 msgstr ""

-#: ../../docs/development/file_formats/tscn.rst:385
+#: ../../docs/development/file_formats/tscn.rst:387
 msgid "``type``"
 msgstr ""

-#: ../../docs/development/file_formats/tscn.rst:386
+#: ../../docs/development/file_formats/tscn.rst:388
 msgid "``path``"
 msgstr ""

-#: ../../docs/development/file_formats/tscn.rst:387
+#: ../../docs/development/file_formats/tscn.rst:389
 msgid "``interp``"
 msgstr ""

-#: ../../docs/development/file_formats/tscn.rst:388
+#: ../../docs/development/file_formats/tscn.rst:390
 msgid "``keys``"
 msgstr ""

-#: ../../docs/development/file_formats/tscn.rst:389
+#: ../../docs/development/file_formats/tscn.rst:391
 msgid "``loop_wrap``"
 msgstr ""

-#: ../../docs/development/file_formats/tscn.rst:390
+#: ../../docs/development/file_formats/tscn.rst:392
 msgid "``imported``"
 msgstr ""

-#: ../../docs/development/file_formats/tscn.rst:393
+#: ../../docs/development/file_formats/tscn.rst:395
 msgid "The ``type`` must be the first attribute of each track. The value of ``type`` can be:"
 msgstr ""

-#: ../../docs/development/file_formats/tscn.rst:396
+#: ../../docs/development/file_formats/tscn.rst:398
 msgid "``transform``"
 msgstr ""

-#: ../../docs/development/file_formats/tscn.rst:397
+#: ../../docs/development/file_formats/tscn.rst:399
 msgid "``value``"
 msgstr ""

-#: ../../docs/development/file_formats/tscn.rst:398
+#: ../../docs/development/file_formats/tscn.rst:400
 msgid "``method``"
 msgstr ""

-#: ../../docs/development/file_formats/tscn.rst:400
+#: ../../docs/development/file_formats/tscn.rst:402
 msgid "The ``path`` has the format ``NodePath(Path/To/Node:attribute)``. It's the path to the animated node or attribute, relative to the root node defined in the AnimationPlayer."
 msgstr ""

-#: ../../docs/development/file_formats/tscn.rst:404
+#: ../../docs/development/file_formats/tscn.rst:406
 msgid "The ``interp`` is the method to interpolate frames from the keyframes. It is an enum variable with one of the following values:"
 msgstr ""

-#: ../../docs/development/file_formats/tscn.rst:407
+#: ../../docs/development/file_formats/tscn.rst:409
 msgid "``0`` (constant)"
 msgstr ""

-#: ../../docs/development/file_formats/tscn.rst:408
+#: ../../docs/development/file_formats/tscn.rst:410
 msgid "``1`` (linear)"
 msgstr ""

-#: ../../docs/development/file_formats/tscn.rst:409
+#: ../../docs/development/file_formats/tscn.rst:411
 msgid "``2`` (cubic)"
 msgstr ""

-#: ../../docs/development/file_formats/tscn.rst:411
+#: ../../docs/development/file_formats/tscn.rst:413
 msgid "The ``keys`` correspond to the keyframes. It appears as a ``PoolRealArray()``, but may have a different structure for tracks with different types."
 msgstr ""

-#: ../../docs/development/file_formats/tscn.rst:414
+#: ../../docs/development/file_formats/tscn.rst:416
 msgid "A Transform track uses every 12 real numbers in the ``keys`` to describe a keyframe. The first number is the timestamp. The second number is the transition followed by a 3-number translation vector, followed by a 4-number rotation quaternion (X, Y, Z, W) and finally a 3-number scale vector. The default transition in a Transform track is 1.0."
 msgstr ""

--- a/sphinx/templates/getting_started/editor/command_line_tutorial.pot
+++ b/sphinx/templates/getting_started/editor/command_line_tutorial.pot
@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2020-07-06 14:52+0200\n"
+"POT-Creation-Date: 2020-07-30 19:14+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
--- a/sphinx/templates/getting_started/editor/default_key_mapping.pot
+++ b/sphinx/templates/getting_started/editor/default_key_mapping.pot
@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2020-07-06 14:52+0200\n"
+"POT-Creation-Date: 2020-07-30 19:14+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
--- a/sphinx/templates/getting_started/editor/external_editor.pot
+++ b/sphinx/templates/getting_started/editor/external_editor.pot
@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2020-07-06 14:52+0200\n"
+"POT-Creation-Date: 2020-07-30 19:14+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
--- a/sphinx/templates/getting_started/editor/index.pot
+++ b/sphinx/templates/getting_started/editor/index.pot
@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2020-07-06 14:52+0200\n"
+"POT-Creation-Date: 2020-07-30 19:14+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
--- a/sphinx/templates/getting_started/editor/unity_to_godot.pot
+++ b/sphinx/templates/getting_started/editor/unity_to_godot.pot
@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2020-07-06 14:52+0200\n"
+"POT-Creation-Date: 2020-07-30 19:14+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
--- a/sphinx/templates/getting_started/scripting/c_sharp/c_sharp_basics.pot
+++ b/sphinx/templates/getting_started/scripting/c_sharp/c_sharp_basics.pot
@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2020-07-06 14:52+0200\n"
+"POT-Creation-Date: 2020-07-30 19:14+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
@@ -309,10 +309,6 @@ msgid "Configuring Visual Studio Code for debugging"
 msgstr ""

 #: ../../docs/getting_started/scripting/c_sharp/c_sharp_basics.rst:296
-msgid "To configure Visual Studio Code for debugging open up a project in Godot. Click on Project and open the project settings. Scroll down and click on Debugger Agent under the Mono category. Then turn on the setting \"wait for debugger.\" Next, copy the port number and open up Visual Studio Code."
-msgstr ""
-
-#: ../../docs/getting_started/scripting/c_sharp/c_sharp_basics.rst:301
-msgid "You need to download the Mono Debug extension from Microsoft. Then open the Godot project folder. Go to the run tab and click on create a launch.json file. Select C# Mono from the dropdown menu. When the launch.json file is automatically opened, change the port number to the number you copied previously and save the file. On the run tab, switch the run setting from launch to attach. Whenever you want to debug, make sure Wait for Debugger is turned on in Godot, run the project, and run the debugger in Visual Studio Code."
+msgid "To configure debugging, open Visual Studio Code and download the Mono Debug extension from Microsoft and the Godot extension by Ignacio. Then open the Godot project folder in VS Code. Go to the Run tab and click on **create a launch.json file**. Select **C# Godot** from the dropdown menu. Now, when you start the debugger in VS Code your Godot project will run."
 msgstr ""

--- a/sphinx/templates/getting_started/scripting/c_sharp/c_sharp_differences.pot
+++ b/sphinx/templates/getting_started/scripting/c_sharp/c_sharp_differences.pot
@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2020-07-06 14:52+0200\n"
+"POT-Creation-Date: 2020-07-30 19:14+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
--- a/sphinx/templates/getting_started/scripting/c_sharp/c_sharp_features.pot
+++ b/sphinx/templates/getting_started/scripting/c_sharp/c_sharp_features.pot
@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2020-07-06 14:52+0200\n"
+"POT-Creation-Date: 2020-07-30 19:14+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
--- a/sphinx/templates/getting_started/scripting/c_sharp/c_sharp_style_guide.pot
+++ b/sphinx/templates/getting_started/scripting/c_sharp/c_sharp_style_guide.pot
@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2020-07-06 14:52+0200\n"
+"POT-Creation-Date: 2020-07-30 19:14+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
--- a/sphinx/templates/getting_started/scripting/c_sharp/index.pot
+++ b/sphinx/templates/getting_started/scripting/c_sharp/index.pot
@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2020-07-06 14:52+0200\n"
+"POT-Creation-Date: 2020-07-30 19:14+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
--- a/sphinx/templates/getting_started/scripting/creating_script_templates.pot
+++ b/sphinx/templates/getting_started/scripting/creating_script_templates.pot
@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2020-07-06 14:52+0200\n"
+"POT-Creation-Date: 2020-07-30 19:14+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
--- a/sphinx/templates/getting_started/scripting/cross_language_scripting.pot
+++ b/sphinx/templates/getting_started/scripting/cross_language_scripting.pot
@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2020-07-06 14:52+0200\n"
+"POT-Creation-Date: 2020-07-30 19:14+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
--- a/sphinx/templates/getting_started/scripting/gdscript/gdscript_advanced.pot
+++ b/sphinx/templates/getting_started/scripting/gdscript/gdscript_advanced.pot
@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2020-07-06 14:52+0200\n"
+"POT-Creation-Date: 2020-07-30 19:14+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
--- a/sphinx/templates/getting_started/scripting/gdscript/gdscript_basics.pot
+++ b/sphinx/templates/getting_started/scripting/gdscript/gdscript_basics.pot
--- a/sphinx/templates/getting_started/scripting/gdscript/gdscript_exports.pot
+++ b/sphinx/templates/getting_started/scripting/gdscript/gdscript_exports.pot
@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2020-07-06 14:52+0200\n"
+"POT-Creation-Date: 2020-07-30 19:14+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
@@ -53,98 +53,94 @@ msgid "Exporting bit flags"
 msgstr ""

 #: ../../docs/getting_started/scripting/gdscript/gdscript_exports.rst:143
-msgid "Integers used as bit flags can store multiple ``true``/``false`` (boolean) values in one property. By using the export hint ``int, FLAGS``, they can be set from the editor::"
+msgid "Integers used as bit flags can store multiple ``true``/``false`` (boolean) values in one property. By using the export hint ``int, FLAGS, ...``, they can be set from the editor::"
 msgstr ""

 #: ../../docs/getting_started/scripting/gdscript/gdscript_exports.rst:150
-msgid "Restricting the flags to a certain number of named flags is also possible. The syntax is similar to the enumeration syntax::"
+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/getting_started/scripting/gdscript/gdscript_exports.rst:156
-msgid "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/getting_started/scripting/gdscript/gdscript_exports.rst:161
+#: ../../docs/getting_started/scripting/gdscript/gdscript_exports.rst:155
 msgid "Export hints are also provided for the physics and render layers defined in the project settings::"
 msgstr ""

-#: ../../docs/getting_started/scripting/gdscript/gdscript_exports.rst:168
-msgid "Using bit flags requires some understanding of bitwise operations. If in doubt, boolean variables should be exported instead."
+#: ../../docs/getting_started/scripting/gdscript/gdscript_exports.rst:162
+msgid "Using bit flags requires some understanding of bitwise operations. If in doubt, use boolean variables instead."
 msgstr ""

-#: ../../docs/getting_started/scripting/gdscript/gdscript_exports.rst:172
+#: ../../docs/getting_started/scripting/gdscript/gdscript_exports.rst:166
 msgid "Exporting arrays"
 msgstr ""

-#: ../../docs/getting_started/scripting/gdscript/gdscript_exports.rst:174
-msgid "Exporting arrays works, but with an important caveat: while regular arrays are created local to every class instance, exported arrays are *shared* between all instances. This means that editing them in one instance will cause them to change in all other instances. Exported arrays can have initializers, but they must be constant expressions."
+#: ../../docs/getting_started/scripting/gdscript/gdscript_exports.rst:168
+msgid "Exported arrays can have initializers, but they must be constant expressions."
 msgstr ""

-#: ../../docs/getting_started/scripting/gdscript/gdscript_exports.rst:180
+#: ../../docs/getting_started/scripting/gdscript/gdscript_exports.rst:170
 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/getting_started/scripting/gdscript/gdscript_exports.rst:220
+#: ../../docs/getting_started/scripting/gdscript/gdscript_exports.rst:208
 msgid "Setting exported variables from a tool script"
 msgstr ""

-#: ../../docs/getting_started/scripting/gdscript/gdscript_exports.rst:222
+#: ../../docs/getting_started/scripting/gdscript/gdscript_exports.rst:210
 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:`property_list_changed_notify() <class_Object_method_property_list_changed_notify>` after setting the exported variable's value."
 msgstr ""

-#: ../../docs/getting_started/scripting/gdscript/gdscript_exports.rst:229
+#: ../../docs/getting_started/scripting/gdscript/gdscript_exports.rst:217
 msgid "Advanced exports"
 msgstr ""

-#: ../../docs/getting_started/scripting/gdscript/gdscript_exports.rst:231
+#: ../../docs/getting_started/scripting/gdscript/gdscript_exports.rst:219
 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/getting_started/scripting/gdscript/gdscript_exports.rst:235
+#: ../../docs/getting_started/scripting/gdscript/gdscript_exports.rst:223
 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_method__get_property_list>`, :ref:`_get() <class_Object_method__get_property_list>`, and :ref:`_get_property_list() <class_Object_method__get_property_list>` methods as described in :ref:`doc_accessing_data_or_logic_from_object`."
 msgstr ""

-#: ../../docs/getting_started/scripting/gdscript/gdscript_exports.rst:242
+#: ../../docs/getting_started/scripting/gdscript/gdscript_exports.rst:230
 msgid "For binding properties using the above methods in C++, see :ref:`doc_binding_properties_using_set_get_property_list`."
 msgstr ""

-#: ../../docs/getting_started/scripting/gdscript/gdscript_exports.rst:245
+#: ../../docs/getting_started/scripting/gdscript/gdscript_exports.rst:233
 msgid "The script must operate in the ``tool`` mode so the above methods can work from within the editor."
 msgstr ""

-#: ../../docs/getting_started/scripting/gdscript/gdscript_exports.rst:249
+#: ../../docs/getting_started/scripting/gdscript/gdscript_exports.rst:237
 msgid "Adding script categories"
 msgstr ""

-#: ../../docs/getting_started/scripting/gdscript/gdscript_exports.rst:251
+#: ../../docs/getting_started/scripting/gdscript/gdscript_exports.rst:239
 msgid "For better visual distinguishing of properties, a special script category can be embedded into the inspector to act as a separator. ``Script Variables`` is one example of a built-in category."
 msgstr ""

-#: ../../docs/getting_started/scripting/gdscript/gdscript_exports.rst:268
+#: ../../docs/getting_started/scripting/gdscript/gdscript_exports.rst:256
 msgid "``name`` is the name of a category to be added to the inspector;"
 msgstr ""

-#: ../../docs/getting_started/scripting/gdscript/gdscript_exports.rst:270
+#: ../../docs/getting_started/scripting/gdscript/gdscript_exports.rst:258
 msgid "``PROPERTY_USAGE_CATEGORY`` indicates that the property should be treated as a script category specifically, so the type ``TYPE_NIL`` can be ignored as it won't be actually used for the scripting logic, yet it must be defined anyway."
 msgstr ""

-#: ../../docs/getting_started/scripting/gdscript/gdscript_exports.rst:275
+#: ../../docs/getting_started/scripting/gdscript/gdscript_exports.rst:263
 msgid "Grouping properties"
 msgstr ""

-#: ../../docs/getting_started/scripting/gdscript/gdscript_exports.rst:277
+#: ../../docs/getting_started/scripting/gdscript/gdscript_exports.rst:265
 msgid "A list of properties with similar names can be grouped."
 msgstr ""

-#: ../../docs/getting_started/scripting/gdscript/gdscript_exports.rst:291
+#: ../../docs/getting_started/scripting/gdscript/gdscript_exports.rst:279
 msgid "``name`` is the name of a group which is going to be displayed as collapsible list of properties;"
 msgstr ""

-#: ../../docs/getting_started/scripting/gdscript/gdscript_exports.rst:294
+#: ../../docs/getting_started/scripting/gdscript/gdscript_exports.rst:282
 msgid "every successive property added after the group property will be collapsed and shortened as determined by the prefix defined via the ``hint_string`` key. For instance, ``rotate_speed`` is going to be shortened to ``speed`` in this case."
 msgstr ""

-#: ../../docs/getting_started/scripting/gdscript/gdscript_exports.rst:298
+#: ../../docs/getting_started/scripting/gdscript/gdscript_exports.rst:286
 msgid "``PROPERTY_USAGE_GROUP`` indicates that the property should be treated as a script group specifically, so the type ``TYPE_NIL`` can be ignored as it won't be actually used for the scripting logic, yet it must be defined anyway."
 msgstr ""

--- a/sphinx/templates/getting_started/scripting/gdscript/gdscript_format_string.pot
+++ b/sphinx/templates/getting_started/scripting/gdscript/gdscript_format_string.pot
@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2020-07-06 14:52+0200\n"
+"POT-Creation-Date: 2020-07-30 19:14+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
--- a/sphinx/templates/getting_started/scripting/gdscript/gdscript_styleguide.pot
+++ b/sphinx/templates/getting_started/scripting/gdscript/gdscript_styleguide.pot
@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2020-07-06 14:52+0200\n"
+"POT-Creation-Date: 2020-07-30 19:14+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
--- a/sphinx/templates/getting_started/scripting/gdscript/index.pot
+++ b/sphinx/templates/getting_started/scripting/gdscript/index.pot
@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2020-07-06 14:52+0200\n"
+"POT-Creation-Date: 2020-07-30 19:14+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
--- a/sphinx/templates/getting_started/scripting/gdscript/static_typing.pot
+++ b/sphinx/templates/getting_started/scripting/gdscript/static_typing.pot
@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2020-07-06 14:52+0200\n"
+"POT-Creation-Date: 2020-07-30 19:14+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
--- a/sphinx/templates/getting_started/scripting/gdscript/warning_system.pot
+++ b/sphinx/templates/getting_started/scripting/gdscript/warning_system.pot
@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2020-07-06 14:52+0200\n"
+"POT-Creation-Date: 2020-07-30 19:14+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
--- a/sphinx/templates/getting_started/scripting/index.pot
+++ b/sphinx/templates/getting_started/scripting/index.pot
@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2020-07-06 14:52+0200\n"
+"POT-Creation-Date: 2020-07-30 19:14+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
--- a/sphinx/templates/getting_started/scripting/visual_script/custom_visualscript_nodes.pot
+++ b/sphinx/templates/getting_started/scripting/visual_script/custom_visualscript_nodes.pot
@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2020-07-06 14:52+0200\n"
+"POT-Creation-Date: 2020-07-30 19:14+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
--- a/sphinx/templates/getting_started/scripting/visual_script/getting_started.pot
+++ b/sphinx/templates/getting_started/scripting/visual_script/getting_started.pot
@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2020-07-06 14:52+0200\n"
+"POT-Creation-Date: 2020-07-30 19:14+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
--- a/sphinx/templates/getting_started/scripting/visual_script/index.pot
+++ b/sphinx/templates/getting_started/scripting/visual_script/index.pot
@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2020-07-06 14:52+0200\n"
+"POT-Creation-Date: 2020-07-30 19:14+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
--- a/sphinx/templates/getting_started/scripting/visual_script/nodes_purposes.pot
+++ b/sphinx/templates/getting_started/scripting/visual_script/nodes_purposes.pot
@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2020-07-06 14:52+0200\n"
+"POT-Creation-Date: 2020-07-30 19:14+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
--- a/sphinx/templates/getting_started/scripting/visual_script/what_is_visual_scripting.pot
+++ b/sphinx/templates/getting_started/scripting/visual_script/what_is_visual_scripting.pot
@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2020-07-06 14:52+0200\n"
+"POT-Creation-Date: 2020-07-30 19:14+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
--- a/sphinx/templates/getting_started/step_by_step/animations.pot
+++ b/sphinx/templates/getting_started/step_by_step/animations.pot
@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2020-07-06 14:52+0200\n"
+"POT-Creation-Date: 2020-07-30 19:14+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
--- a/sphinx/templates/getting_started/step_by_step/exporting.pot
+++ b/sphinx/templates/getting_started/step_by_step/exporting.pot
@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2020-07-06 14:52+0200\n"
+"POT-Creation-Date: 2020-07-30 19:14+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
--- a/sphinx/templates/getting_started/step_by_step/filesystem.pot
+++ b/sphinx/templates/getting_started/step_by_step/filesystem.pot
@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2020-07-06 14:52+0200\n"
+"POT-Creation-Date: 2020-07-30 19:14+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
--- a/sphinx/templates/getting_started/step_by_step/godot_design_philosophy.pot
+++ b/sphinx/templates/getting_started/step_by_step/godot_design_philosophy.pot
@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2020-07-06 14:52+0200\n"
+"POT-Creation-Date: 2020-07-30 19:14+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
--- a/sphinx/templates/getting_started/step_by_step/index.pot
+++ b/sphinx/templates/getting_started/step_by_step/index.pot
@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2020-07-06 14:52+0200\n"
+"POT-Creation-Date: 2020-07-30 19:14+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
--- a/sphinx/templates/getting_started/step_by_step/instancing.pot
+++ b/sphinx/templates/getting_started/step_by_step/instancing.pot
@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2020-07-06 14:52+0200\n"
+"POT-Creation-Date: 2020-07-30 19:14+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
--- a/sphinx/templates/getting_started/step_by_step/instancing_continued.pot
+++ b/sphinx/templates/getting_started/step_by_step/instancing_continued.pot
@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2020-07-06 14:52+0200\n"
+"POT-Creation-Date: 2020-07-30 19:14+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
--- a/sphinx/templates/getting_started/step_by_step/intro_to_the_editor_interface.pot
+++ b/sphinx/templates/getting_started/step_by_step/intro_to_the_editor_interface.pot
@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2020-07-06 14:52+0200\n"
+"POT-Creation-Date: 2020-07-30 19:14+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
--- a/sphinx/templates/getting_started/step_by_step/resources.pot
+++ b/sphinx/templates/getting_started/step_by_step/resources.pot
@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2020-07-06 14:52+0200\n"
+"POT-Creation-Date: 2020-07-30 19:14+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
--- a/sphinx/templates/getting_started/step_by_step/scene_tree.pot
+++ b/sphinx/templates/getting_started/step_by_step/scene_tree.pot
@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2020-07-06 14:52+0200\n"
+"POT-Creation-Date: 2020-07-30 19:14+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
--- a/sphinx/templates/getting_started/step_by_step/scenes_and_nodes.pot
+++ b/sphinx/templates/getting_started/step_by_step/scenes_and_nodes.pot
@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2020-07-06 14:52+0200\n"
+"POT-Creation-Date: 2020-07-30 19:14+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
--- a/sphinx/templates/getting_started/step_by_step/scripting.pot
+++ b/sphinx/templates/getting_started/step_by_step/scripting.pot
@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2020-07-06 14:52+0200\n"
+"POT-Creation-Date: 2020-07-30 19:14+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
@@ -305,7 +305,7 @@ msgid "Also, remember that nodes are referenced by name, not by type."
 msgstr ""

 #: ../../docs/getting_started/step_by_step/scripting.rst:334
-msgid "The right-hand panel of the connect dialogue is for binding specific values to the connected function's parameters. You can add and remove values of different types."
+msgid "The 'advanced' panel of the connect dialogue is for binding specific values to the connected function's parameters. You can add and remove values of different types."
 msgstr ""

 #: ../../docs/getting_started/step_by_step/scripting.rst:338
--- a/sphinx/templates/getting_started/step_by_step/scripting_continued.pot
+++ b/sphinx/templates/getting_started/step_by_step/scripting_continued.pot
@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2020-07-06 14:52+0200\n"
+"POT-Creation-Date: 2020-07-30 19:14+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
--- a/Show More
+++ b/Show More