We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MK4S
6.2.0-RC1
MMU3
PrusaLink/PrusaConnect
Typo/weird spelling in error message for code: "XX535"
"it might have beet not executed correctly."
Files/lines affected:
Prusa-Firmware-Buddy/lib/Prusa-Error-Codes/yaml/buddy-error-codes.yaml
Line 695 in f684f7b
Prusa-Firmware-Buddy/src/lang/po/Prusa-Firmware-Buddy.pot
Line 2414 in f684f7b
Prusa-Firmware-Buddy/src/lang/po/jp/Prusa-Firmware-Buddy_jp.po
Line 2567 in f684f7b
Prusa-Firmware-Buddy/src/lang/po/fr/Prusa-Firmware-Buddy_fr.po
Line 2522 in f684f7b
Prusa-Firmware-Buddy/src/lang/po/de/Prusa-Firmware-Buddy_de.po
Prusa-Firmware-Buddy/src/lang/po/es/Prusa-Firmware-Buddy_es.po
Line 2545 in f684f7b
Prusa-Firmware-Buddy/src/lang/po/it/Prusa-Firmware-Buddy_it.po
Line 2548 in f684f7b
Prusa-Firmware-Buddy/src/lang/po/pl/Prusa-Firmware-Buddy_pl.po
Line 2532 in f684f7b
Prusa-Firmware-Buddy/src/lang/po/cs/Prusa-Firmware-Buddy_cs.po
Line 2492 in f684f7b
Guess it should say "It might not have been executed correctly."?
No response
The text was updated successfully, but these errors were encountered:
Hello, this has already been fixed by prusa3d/Prusa-Error-Codes#171, but has not been merged into the 6.2 yet - I will arrange the merge.
Sorry, something went wrong.
CZDanol
No branches or pull requests
Printer model
MK4S
Firmware version
6.2.0-RC1
Upgrades and modifications
MMU3
Printing from...
PrusaLink/PrusaConnect
Describe the bug
Typo/weird spelling in error message for code: "XX535"
"it might have beet not executed correctly."
How to reproduce
Files/lines affected:
Prusa-Firmware-Buddy/lib/Prusa-Error-Codes/yaml/buddy-error-codes.yaml
Line 695 in f684f7b
Prusa-Firmware-Buddy/src/lang/po/Prusa-Firmware-Buddy.pot
Line 2414 in f684f7b
Prusa-Firmware-Buddy/src/lang/po/jp/Prusa-Firmware-Buddy_jp.po
Line 2567 in f684f7b
Prusa-Firmware-Buddy/src/lang/po/fr/Prusa-Firmware-Buddy_fr.po
Line 2522 in f684f7b
Prusa-Firmware-Buddy/src/lang/po/de/Prusa-Firmware-Buddy_de.po
Line 2567 in f684f7b
Prusa-Firmware-Buddy/src/lang/po/es/Prusa-Firmware-Buddy_es.po
Line 2545 in f684f7b
Prusa-Firmware-Buddy/src/lang/po/it/Prusa-Firmware-Buddy_it.po
Line 2548 in f684f7b
Prusa-Firmware-Buddy/src/lang/po/pl/Prusa-Firmware-Buddy_pl.po
Line 2532 in f684f7b
Prusa-Firmware-Buddy/src/lang/po/cs/Prusa-Firmware-Buddy_cs.po
Line 2492 in f684f7b
Expected behavior
Guess it should say "It might not have been executed correctly."?
Files
No response
The text was updated successfully, but these errors were encountered: