Replies: 2 comments
-
|
@nijel This also happens when I'm away from the keyboard for extended periods of time. Upon coming back and "Save and continue", I get this exact same message even though the source string hasn't changed. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
This can happen when server side cached results expire while translating. The proper fix is planned in #9953. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Multiple people have been reporting their changes not being saved in Weblate. I believe this error is the culprit. I can assure no one is touching the source strings, ever. I think it's caused by multiple people working on the same component at the same time and that changes the offset of state:<translated and pressing "Save and continue" causes to lose changes made in the translation. My hypothesis is further strengthened by the fact that "Save and continue" leads to another string is that is not adjacent to the previous one and pressing the left arrow doesn't go back to the string the user was facing just before. This problem is especially painful when it comes to the really long pieces of text.
Beta Was this translation helpful? Give feedback.
All reactions