Multilingual custom extension

[sfederici]

Is it possible to add multilingual translations to custom turbowarp extensions? If so, how? Thanks in advance

[CubesterYT]

As in making extensions support other languages? Then yes, it's possible, as of recently, you can use Scratch.translate("STRING") on any strings to be able to get automatically translated by supporting transifex backed translations.

[VariedadesJuanYT]

y donde pongo ese codigo?

[GarboMuffin]

Documentation to be written on this soon

If you intend to submit the extensions here, it's easiest to just do this as our build server has various tricks:

Scratch.translate("English version");

// Or with context:
Scratch.translate({
  default: "English version",
  description: "This text appears as 'developer comments' in Transifex"
});

If you want to do it manually for a custom extension:

// Instead of hardcoding English/Italian/whatever strings, use this:
Scratch.translate({
  id: "stringid", // just needs to be unique within the extension
  default: "English version"
});

// To tell Scratch.translate about the different languages, do this once at the start, before calling Scratch.translate():
Scratch.translate.setup({
  it: {
    stringid: "Italian version"
  },
  es: {
    stringid: "Spanish version"
  }
});

[CST1229]

I think you have to put the Scratch.translate.setup() call before the Scratch.extensions.register() (and inside the IIFE), and probably also include the [CONDITION] as part of the string. Also, that example Scratch.translate call there in the second code block should be in the first, like

text: Scratch.translate({
	id: "foreverif",
	default: "forever if [CONDITION]"
});

[sfederici]

Oh, I see. That makes sense, even if it doesn't explain to me how

Scratch.translate("English version");

would work then.

Anyway, I don't think [CONDITION] should be included. It would be really weird to me if it should. I'm going to test and I will let you know.

[sfederici]

Yes, it works. I have put

Scratch.translate.setup({
	it: {
		"foreverif": "per sempre quando"
	}
});

at the beginning of the IIFE and then I used

text: Scratch.translate({ id: "foreverif", default: "forever if"}) + " [CONDITION]",

inside the new block definition.

Now, when I load the test pong.sb3 file, everything works, even changing the language from en to it.

[CST1229]

Anyway, I don't think [CONDITION] should be included. It would be really weird to me if it should.

Some languages may reorder inputs, or put text at the end of the block, and blocks can also have multiple inputs. Both the vanilla Scratch blocks and the vanilla extension blocks have the inputs in the string for this reason.

[sfederici]

Yes, you are right. I will give it a try

[sfederici]

I would gladly submit the extension, but the guidelines say that submitted extensions should be of general interest. I don't know if adding back the "forever if" block of Scratch 1.4 could be considered of general interest?

[GarboMuffin]

Extension review is currently very sporadic and slow. You can try if you want but I would suggest just doing your manual approach and let submitting it here be a secondary side thing

[sfederici]

Ok thanks