The bug
It appears en_us.json
(and therefore likely all other languages as well) contains translations which are not / no longer used.
Important: Please verify that the translations are really not used anymore. Some translation keys are generated dynamically which makes detecting whether they are used rather difficult.
Affected translation keys
Keys ending with *
indicate that all translation keys with the prefix before the *
are affected.
Translation key | Note |
---|---|
| Intended, see MC-109844 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Intended? Customized generation has been removed, but will be readded again? |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
|
|
| Not used anymore? See MC-92330 |
| Not used anymore? See MC-92330 |
|
|
|
|
| |
| |
| |
| |
| |
|
|
|
|
|
|
|
|
|
|
|
|
Linked issues
is cloned by 1
relates to 1
Attachments
Comments 6
@@unknown, what exactly do you mean by "resolved"? Do you mean fixed? The cases mentioned in this report were not fixed as part of MC-109844. Generally we prefer cloning reports nowadays instead of continuously reopening an existing report if we notice new cases.
In table row 10, it is said that all createWorld.customize.*
translation strings are no longer used in the game. This is partially incorrect:
Only the
createWorld.customize.custom.*
translation strings are actually unused.The
createWorld.customize.buffet.*
,createWorld.customize.flat.*
,createWorld.customize.presets
, andcreateWorld.customize.presets.*
translation strings, however, are still in use as of the latest version of the game, as can be seen in the attached screenshots.
In table row 4, it is said that the menu.working
translation string is no longer used in the game. This might be incorrect as well:
This translation string is output by the
progressStart
and – consequentially – theprogressStartNoAbort
methods of thenet.minecraft.client.gui.screens.ProgressScreen
class. The latter method is called by thesave
method of thenet.minecraft.server.level.ServerLevel
class.
I personally think this bug report should be resolved, as MC-109844 is the same issue and it has been fixed.