Dev Archipelago: Translate Basics islands to Spanish

[manuq]

This translates:

• The dialogue of the Basics Elder to engage with the quests.
• The content in the StoryBook that this elder presents.
• The signposts of the "Basics" Dev islands / quests.

ThreadbareEditor addon: Add translation parser for quests

So the .tres file is recognized by the translation system, and title and
description of Quests can be extracted to the catalog.

Update the list of translatable files:

Add the following new files:

• All three .tscn files from Dev Basics.
• Basics Elder dialogue
• Dev Basics quests (two quest.tres files)

Regenerate the template POT file and update Spanish translation.

Resolves #2844

[github-actions]

Play this branch at https://play.threadbare.game/branches/endlessm/archipelago-spanish/.

(This launches the game from the start, not directly at the change(s) in this pull request.)

[manuq]

Playtest instructions:

1. Play the game from this link, which should start in Dev Archipelago: https://play.threadbare.game/branches/endlessm/main/#dev/dev_archipelago

2. Press ESC and from the Options tab set the game in Spanish:

3. Talk to this Elder (ignore the fact that it says "Template Elder" in the input HUD):

4. Engage with demo "Teletransportadores" and play it.

5. Exit that first demo. The way to exit is by going to the Pause menu and select "Abandonar misión".

6. Talk to the same Elder again and engage with the other demo "Visuales".

That's it! Here are some screenshots:

[wjt]

You mentioned somewhere that "Basics" doesn't translate cleanly into Spanish. I wonder if we should actually change the English word too. "Rudiments", "Fundamentals"? (I don't know if these work in US English.)

[manuq]

You mentioned somewhere that "Basics" doesn't translate cleanly into Spanish. I wonder if we should actually change the English word too. "Rudiments", "Fundamentals"? (I don't know if these work in US English.)

The title or surname I used for this elder is "Anciano ConceptosBásicos" which would translate back literally to "BasicConcepts Elder".

[manuq]

@wjt I have rebased this now with Dialogue Manager 4.1 and tested generating the POT file: there are no changes. Then I tried deactivating "Use Static IDs as Translation Keys":

The only thing it does to existing dialogues is removing the msgctxt from dialogue lines:

 #. TRANSLATORS: Character: Basics Elder
 #: scenes/dev/components/dev_archipelago_basics_elder.dialogue:3
-msgctxt "dialogue"
 msgid "[[Hi|Hello|Greetings]], StoryWeaver. Welcome to Dev Archipelago!"
 msgstr ""
 
 #. TRANSLATORS: Character: Basics Elder
 #: scenes/dev/components/dev_archipelago_basics_elder.dialogue:4
-msgctxt "dialogue"
 msgid "This is a place of creativity, play, and experimentation!"
 msgstr ""
 
 #. TRANSLATORS: Character: Basics Elder
 #: scenes/dev/components/dev_archipelago_basics_elder.dialogue:5
-msgctxt "dialogue"
 msgid "While I can't explain all of what happens here, I invite you to learn about the basics of our unraveling world!"
 msgstr ""

Then I tested generating those IDs from within the Dialogue Manager tab:

And regenerating the POT. Now I see why the recommendation is to deactivate the setting for gettext:

Now:

 #. TRANSLATORS: Character: Basics Elder
+#. Line: [[Hi|Hello|Greetings]], StoryWeaver. Welcome to Dev Archipelago!
 #: scenes/dev/components/dev_archipelago_basics_elder.dialogue:3
 msgctxt "dialogue"
-msgid "[[Hi|Hello|Greetings]], StoryWeaver. Welcome to Dev Archipelago!"
+msgid "cjo0b4vsho0yh_722844"
 msgstr ""
 
 #. TRANSLATORS: Character: Basics Elder
+#. Line: This is a place of creativity, play, and experimentation!
 #: scenes/dev/components/dev_archipelago_basics_elder.dialogue:4
 msgctxt "dialogue"
-msgid "This is a place of creativity, play, and experimentation!"
+msgid "cjo0b4vsho0yh_248a95"
 msgstr ""
 
 #. TRANSLATORS: Character: Basics Elder
+#. Line: While I can't explain all of what happens here, I invite you to learn about the basics of our unraveling world!
 #: scenes/dev/components/dev_archipelago_basics_elder.dialogue:5
 msgctxt "dialogue"
-msgid "While I can't explain all of what happens here, I invite you to learn about the basics of our unraveling world!"
+msgid "cjo0b4vsho0yh_285cb3"
 msgstr ""

And after reactivating "Use Static IDs as Translation Keys" I see the static IDs used as "msgctxt", while the string keeps being translatable:

 #. TRANSLATORS: Character: Basics Elder
 #: scenes/dev/components/dev_archipelago_basics_elder.dialogue:3
-msgctxt "dialogue"
+msgctxt "cjo0b4vsho0yh_722844"
 msgid "[[Hi|Hello|Greetings]], StoryWeaver. Welcome to Dev Archipelago!"
 msgstr ""
 
 #. TRANSLATORS: Character: Basics Elder
 #: scenes/dev/components/dev_archipelago_basics_elder.dialogue:4
-msgctxt "dialogue"
+msgctxt "cjo0b4vsho0yh_248a95"
 msgid "This is a place of creativity, play, and experimentation!"
 msgstr ""
 
 #. TRANSLATORS: Character: Basics Elder
 #: scenes/dev/components/dev_archipelago_basics_elder.dialogue:5
-msgctxt "dialogue"
+msgctxt "cjo0b4vsho0yh_285cb3"
 msgid "While I can't explain all of what happens here, I invite you to learn about the basics of our unraveling world!"
 msgstr ""

So we have 2 options:

• Leave "Use Static IDs as Translation Keys" enabled and document to not add Static IDs to dialogues
• Or disable "Use Static IDs as Translation Keys".

[wjt]

LGTM.

So we have 2 options:

1. Leave "Use Static IDs as Translation Keys" enabled and document to not add Static IDs to dialogues
2. Or disable "Use Static IDs as Translation Keys"

I suggest 2 - this does something sensible regardless of whether we eventually use static IDs.

[wjt]

Wow. I expected that there would be some vfunc on nodes/resources that gets translations for their properties; or maybe some property export flag that means "translate me". But no! In fact the built-in translations of properties of scenes is an implementation of EditorTranslationParserPlugin with loads of hardcoded special cases, e.g. "If a node is a direct child of a TabContainer, then its name should be translated".

[manuq]

Good to know! Great source to use as reference too. For example, the use of get_recognized_extensions_for_type().

[wjt]

This branch seems to break the Enemy Interaction Elder but I can't figure out why.

False alarm. I think there's some upgrade bug in Dialogue Manager which can be worked around by deleting .godot. I'll file a separate bug.