-
Notifications
You must be signed in to change notification settings - Fork 241
New issue
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
translation: Improvements and fixes in French translation #3703
Conversation
Instead of redscreen, printer would show BSOD because it failed to write error to usb serial. So writes to USB-CDC are skipped from ISR. Its not possible to acquire mutex to write to USB from ISR, and even if it would be somehow implemented, it wouldn't probably flush the message in time anyway.
…zle offset calibration
If one dwarf finished much earlier than another, it would reset the PID and the other would fail the test. BFW-4607
It was migrating p=17 which was default at that time, but never used. Now the default is 14 and will follow the default if we want change.
If ISR would happen during that function, the crash_s.loop would stay true during the loop when crash_s.set_state(Crash_s::RECOVERY) is set.
This reverts commit fb4e117.
Handle unexpected dirs (blocking the uploaded file) and missing destination dirs in a better way than just "Unknown error". BFW-4543.
* Use 5 retries in a row. * Reset back to 5 when we make some progress. BFW-4547.
Apparently, our remove & stuff didn't report EISDIR properly. We go with stat instead of fopen to figure stuff out. BFW-4147.
When we have a download failure, back up the position before retrying so we don't lose any data unnecessarily. Slightly related to BFW-4647 (that one made it more observable for some reason).
Code unification & simplification ‒ create a transfer in a "failed" state and "retry" it later. Apart from making the code shorter and less duplicate, it also makes sure the download order is initialized before the first request (needed for future commits). (The code was duplicated for historical reasons ‒ originally, Download could fail at startup; this is no longer possible) BFW-4647.
The variant of construction with a destination path is no longer used, remove from the code. As a result, the initialization can't fail ‒ it can become a constructor directly. BFW-4647.
Change the order of downloading textual gcodes from header -> tail -> body to tail -> header + body (the latter one being in one chunk). We need both the header and tail before we start the print, but we don't care in which order we get them. This way we save one request (one seek) ‒ cheaper for us, cheaper for the server and likely few seconds faster before the print starts. BFW-4647.
To postpone a closure until the end of a scope / turn a closure into RAII.
To be used on reprint button when we want toolmapping screen to show. BFW-4568
We don't have consent from the user right now and they are not encrypted. Shouldn't go to "production". BFW-3468.
A carbon copy of the relevant part of Developer Guidelines from wiki.
Add MINI+ and MK3.9 to the list of supported models.
…better gcode debugging
Also please relabel your PR to "translation: Improvements and fixes in French translation" according to the Contribution guidelines here. Thanks ! |
Internal reference: BFW-5039 |
If it is still relevant, could you also include the "déchargé" mentioned here: #3372 |
@aginies Your improvements to our french translations are appreciated, we just need to neaten it a bit.
You can try to rebase in place with rebase --onto, but since you commited all the changes into your fork's master, it may be a little difficult. I would suggest you close this PR and create a new one, that will merge from new_branch to prusa3d:master:
If you have any trouble, just let me know. |
To speed up the process, I have rebased it on the current master here #4016. Thank you for the contribution. |
Few improvments fixes and one error fix in the French po file.