The new block:

(translate [] from [English v] to [Spanish v] :: pen)

Why should it be replaced?
1. You would expect

(translate [quince] to [Spanish v] :: pen)

to report “membrillo”, right? However, it still reports “quince”.
That's because the Spanish word “quince” means “fifteen”.
However, the English word “quince” is “membrillo” in Spanish.
So here's how that will be fixed using this:

(translate [quince] from [English v] to [Spanish v] :: pen) // membrillo
(translate [quince] from [Spanish v] to [English v] :: pen) // fifteen

Pretty simple, right?
This is very annoying, especially for word checkers for a language or anything that uses a built-in electronic word bank or dictionary (such as a word search or find).
Please replace it. Now.

There are currently some errors with google translate, but this would be very hard to get google to fix, also, google translate is the most advanced translating technology right now

staffordboys wrote:

There are currently some errors with google translate, but this would be very hard to get google to fix, also, google translate is the most advanced translating technology right now

Google Translate does produce the intended result that OP mentioned, even if you haven't selected a language in the input language area.

There's probably something with Scratch's implementation of Google Translate that's causing something to happen - it's not from Google's side

How about instead a block like this:

set translate from language to [English v] ::pen
set translate from language to [Spanish v] ::pen
set translate from language to [Detect Language v] ::pen

The text could probably be shortened to make the block smaller.

If you provide more context, such as using “the quince” instead, it'll properly translate to “el membrillo.” If you're making a word dictionary, including the article might be helpful for languages with grammatical gender because its often reflected in the article. However, I agree that the source language should be settable somehow.

I definitely support this, I can understand why this would confuse people. I mean, c'mon, there are plenty of word spellings that aren't exclusive to one language.

Thy aforementioned is not-so-greatly annoying, for little chance there is a project uses such block, and that it would, perchance, need a translation of the word “quince” or another such word, so minimal priority shall be placed here. However, with no reason to keep and with reason to change, a change is worthy.