Skip to content
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

Closed
wants to merge 155 commits into from

Conversation

aginies
Copy link

@aginies aginies commented Jan 22, 2024

Few improvments fixes and one error fix in the French po file.

LukasLendvorsky and others added 30 commits November 23, 2023 18:26
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.
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.
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.
@bkerler
Copy link
Contributor

bkerler commented Jan 24, 2024

Also please relabel your PR to "translation: Improvements and fixes in French translation" according to the Contribution guidelines here. Thanks !

@aginies aginies changed the title Imporvements and fixes in French translation translation: Improvements and fixes in French translation Jan 30, 2024
@vorner
Copy link
Contributor

vorner commented Feb 2, 2024

Internal reference: BFW-5039

@teotwaki
Copy link

teotwaki commented Feb 3, 2024

If it is still relevant, could you also include the "déchargé" mentioned here: #3372

@michalrudolf
Copy link
Contributor

@aginies Your improvements to our french translations are appreciated, we just need to neaten it a bit.

  • All of the commits, that edit french .po file, should be squashed into one commit (you can list the various changes in the commit message).
  • You have to rebase the changes on current prusa3d:master.

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:

  1. Do a soft reset of all of your commits git reset XXXX where XXXX is hash of the last master's commit before your changes
  2. Stash the changes git stash
  3. Pull current prusa3d::master git pull {prusa3d remote} master
  4. Create a new branch on up-to-date master git checkout -b {new_branch name}
  5. Pop the stashed changes git stash pop
  6. Commit all the changes
  7. Push the branch to your fork and create a new PR
  8. Mention me and this PR in the new PR's description

If you have any trouble, just let me know.

@michalrudolf
Copy link
Contributor

To speed up the process, I have rebased it on the current master here #4016. Thank you for the contribution.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
translations language packages
Projects
None yet
Development

Successfully merging this pull request may close these issues.