The Bug:
There is a comma missing after the word "Sorry" within a launcher string used for a generic error message.
This is a very minor issue however, this word should have a comma present after it, in order for the string to make grammatical sense. A comma should always be used after an introductory clause or phrase, and not using it under these circumstances would be grammatically incorrect.
Below is a table I've constructed that highlights this error. You can find information about what the current and expected string is and would be, some context regarding it, and a link to the appropriate string on crowdin.
Current String | Expected String | String Context | String URL on Crowdin |
|---|---|---|---|
Sorry you have encountered a problem; please try restarting your Launcher. | Sorry, you have encountered a problem; please try restarting your Launcher. | #: ..\..\apps\launcher\src\routes\Java\components\JavaSubMenu\index.tsx:112 | https://crowdin.com/translate/minecraft-launcher/9420/en-engb#5271099 |
h3. Steps to Reproduce:
Locate the affected string as listed above.
Take note as to whether or not there is a comma missing after the word "Sorry" within a launcher string used for a generic error message.
Observed Behavior:
There is a comma missing after the word "Sorry" within a launcher string used for a generic error message.
Expected Behavior:
A comma would be present after the word "Sorry" so that the string makes grammatical sense.
Not a bug. Both "Sorry ..." and "Sorry, ..." can be used here with equally apropos application. One implies "Sorry (that an error-state has occurred)..." The other expresses the developer's sympathy with the user experiencing such. Suggesting a missing comma is incorrect here is both incorrect and a waste of dev cycle resources in reporting.