-
Bug
-
Resolution: Works As Intended
-
None
-
22w46a
-
Confirmed
-
Text
-
Low
-
Platform
The Bug:
File size units within some strings are inconsistently capitalized.
I believe this is a valid problem because Microsoft themselves generally considers usages other than "KB" to be incorrect. See https://www.microsoft.com/en-us/language/Search?&searchTerm=kB&langID=262&Source=true&productid=0
Affected Strings:
Before reading the table, please note the following:
- Words colored in GREEN are correct.
- Words colored in RED are incorrect.
| Translation Key | Current String | Expected String | String URL on Crowdin |
|---|---|---|---|
| selectWorld.edit.backupSize | size: %s MB | size: %s MB | https://crowdin.com/translate/minecraft/10038/enus-engb#5331878 |
| resourcepack.progress | Downloading file (%s MB)... | Downloading file (%s MB)... | https://crowdin.com/translate/minecraft/10038/enus-engb#5340390 |
| telemetry.property.dedicated_memory_kb.title | Dedicated Memory (kB) | Dedicated Memory (KB) | https://crowdin.com/translate/minecraft/10038/enus-engb#5343207 |
Steps to Reproduce:
- Display the affected string as listed above by using the command provided below.
/tellraw @s {"translate":"telemetry.property.dedicated_memory_kb.title"} - Look at the capitalization of the file size units within the string.
- Take note as to whether or not file size units within some strings are inconsistently capitalized.
Observed Behavior:
File size units are inconsistently capitalized.
Expected Behavior:
File size units would be consistently capitalized.