<this is for all of the scratch resource libraries, but I'm too lazy to change it>

So, we all know the sprite library, that tool when we need a sprite?

Well, it turns out, the asset names don't get translated when you change languages in Scratch???

If the sprite library is important for us, it is for people who speak other languages too!

I have Scratch in Latin American Spanish, and while coding a project, I realized that the asset names weren't in Spanish, it's like this for the other languages too.

This is shocking, since, even though you can simply view the assets, if someone tries to search for an asset in their language, it won't show up. The sprite searcher makes is way easier to search for sprites, but it does no good if it doesn't work in your language.

Scratch is meant to be inclusive, and this pushes it back.


So, ya, that's my suggestion, translate asset names when Scratch is in a different language!

Considering that some assets have multiple English words, I would support this. This helps internationalize Scratch when reading costumes, especially if someone doesn't know English.

Wow, I hadn't even noticed there *was* a search feature in the asset library, for exactly the reason mentioned that if you search in a language other than English, nothing shows up. I just scroll through all the assets looking for what I want. Absolutely support this suggestion, because it would make it so much easier for non-English speakers to use Scratch.

They might not even need to actually translate the string that shows on the page - eg. since a picture of an apple is fairly obvious it's an apple, they could keep the text as “apple”, but have the search engine find it even if the user searches for “manzana” or “apfel” or “яблоко” or….

That would be particularly useful for users who have a non-latin keyboard (Arabic, Russian etc.) because even if they know the English word to search for it, they would need to change the keyboard on their device just to type it in. Which, I agree, is not super user-friendly or inclusive.

BUmp

What would be used to translate it? Google translate?

Scratchedbyyou wrote:

What would be used to translate it? Google translate?

Translators, like the rest of the Scratch website was translated.

-Rodri wrote:

Scratchedbyyou wrote:

What would be used to translate it? Google translate?

Translators, like the rest of the Scratch website was translated.

You mean human translators? It's not like they will go through every project to translate every asset. It would need to be done by a program.
Edit: Op was miscommunicated

Scratchedbyyou wrote:

-Rodri wrote:

Scratchedbyyou wrote:

What would be used to translate it? Google translate?

Translators, like the rest of the Scratch website was translated.

You mean human translators? It's not like they will go through every project to translate every asset. It would need to be done by a program.

Well ya. I thought you were asking who was gonna like actually translate the asset names, not actually change them manually.

Scratchedbyyou wrote:

You mean human translators? It's not like they will go through every project to translate every asset. It would need to be done by a program.

I think -Rodri means translate the asset library, not every asset in every project.

ilovestories wrote:

Scratchedbyyou wrote:

You mean human translators? It's not like they will go through every project to translate every asset. It would need to be done by a program.

I think -Rodri means translate the asset library, not every asset in every project.

The op needs more clarification, they just said assets.
Edit: They clarified it now.

Scratchedbyyou wrote:

The op needs more clarification, they just said assets.

This sentence clarified it for me:

-Rodri wrote:

This is shocking, since, even though you can view the assets, if someone tries to search for an asset in their language, it won't show up.

Ok now that it was clarified that the assets in just the libraries would be translated, yeah I see no problem at all! (Except it could cost money )

Scratchedbyyou wrote:

Ok now that it was clarified that the assets in just the libraries would be translated, yeah I see no problem at all! (Except it could cost money )

Scratch already has a translating extension and also has the entire website translated to multiple languages, why would they need to spend more money.

Support

bu/\/\p

starlightsparker wrote:

Scratchedbyyou wrote:

Ok now that it was clarified that the assets in just the libraries would be translated, yeah I see no problem at all! (Except it could cost money )

Scratch already has a translating extension and also has the entire website translated to multiple languages, why would they need to spend more money.

Support

The op wants human translators to do it which can cost money

-Rodri wrote:

Scratchedbyyou wrote:

What would be used to translate it? Google translate?

Translators, like the rest of the Scratch website was translated.

Scratchedbyyou wrote:

starlightsparker wrote:

Scratchedbyyou wrote:

Ok now that it was clarified that the assets in just the libraries would be translated, yeah I see no problem at all! (Except it could cost money )

Scratch already has a translating extension and also has the entire website translated to multiple languages, why would they need to spend more money.

Support

The op wants human translators to do it which can cost money

-Rodri wrote:

Scratchedbyyou wrote:

What would be used to translate it? Google translate?

Translators, like the rest of the Scratch website was translated.

Well, everything in live costs money (for the most part). Would you rather run the chance of having inaccurate translations with a translator? it's not like the sprite library is that big.

-Rodri wrote:

Well, everything in live costs money (for the most part). Would you rather run the chance of having inaccurate translations with a translator? it's not like the sprite library is that big.

339 sprites, to be exact.

Scratchedbyyou wrote:

starlightsparker wrote:

Scratchedbyyou wrote:

Ok now that it was clarified that the assets in just the libraries would be translated, yeah I see no problem at all! (Except it could cost money )

Scratch already has a translating extension and also has the entire website translated to multiple languages, why would they need to spend more money.

Support

The op wants human translators to do it which can cost money

Scratch already maintains translations for their site through human translators and Transifex. Translations through their Transifex do not cost any money

ilovestories wrote:

-Rodri wrote:

Well, everything in live costs money (for the most part). Would you rather run the chance of having inaccurate translations with a translator? it's not like the sprite library is that big.

339 sprites, to be exact.

Which is much smaller than the total number of pages that they've had to translate. Also, in some languages the translations wouldn't fully apply, or be easily repeatable, such as the letter sprites.

BigNate469 wrote:

ilovestories wrote:

-Rodri wrote:

Well, everything in live costs money (for the most part). Would you rather run the chance of having inaccurate translations with a translator? it's not like the sprite library is that big.

339 sprites, to be exact.

Which is much smaller than the total number of pages that they've had to translate. Also, in some languages the translations wouldn't fully apply, or be easily repeatable, such as the letter sprites.

Also to note that's only ~339 words to translate (saying each sprite has one word name long, prob not, but an estimate). That's only like two paragraphs or three.