The bug
In Minecraft version 1.8 the game used one translation string when a block or item name was invalid:
commands.give.notFound=There is no such item with name %dHowever at some point this translation was replaced by two new ones (very likely in version 1.8.1):
commands.give.item.notFound=There is no such item with name %d
commands.give.block.notFound=There is no such block with name %dEven though they were added for an official release they are untranslated for all languages other than "English (US)" and are not listed on crowdin (website used for translations) either.
How to reproduce
Open Minecraft 1.8.9 which should have translations for all game elements
Set the language to something different than English
Use the following command
/setblock ~ ~ ~ s
Linked issues
is duplicated by 1
relates to 2
Comments 14
Invalid
Translations have changed:
1.8
commands.give.notFound=There is no such item with name %d16w06a
commands.give.item.notFound=There is no such item with name %d
commands.give.block.notFound=There is no such block with name %dThat is very likely also the reason why no translation is used
I know, but these translations are used (in 1.8) when the game tries to convert the String Id to a block or item, which is also the case for commands like /setblock
This bug is confirmable. It is a bug. Please reopen.
The block name "s" was just an example of an unexisting name of block.
This is a bug that when you enter that invalid block into the /setblock command, it will stay untranslated.
Just try to randomly change your language, and type the command written above. It will still be shown in English.
You are right, it should have a translation already as this bug appeared in 1.8.1, however there is no translation for this on crowdin
Actually, you changed it to a different bug. The error message for the /setblock is commands.setblock.notFound. There is an translation for this in Crowdin, but it is actually not implemented into the game. commands.give... is another bug.
I created MC-97347 because the commands.setblock.notFound error message seems to be outdated.
Confirmed.