Empty translations

Empty translations

H Verdy, you have created some /aa translations and emptied some later. Therefore they were exported with "". A revert was necessary: https://gerrit.wikimedia.org/r/c/mediawiki/extensions/AbuseFilter/+/806522

As reminder: Emptying messages does not work. You have to delete them.

Raymond16:34, 20 June 2022

Yes but I cannot delete them. There was a quirk during navigation, and the language selection was unexpectedly changed to "aa" instead of "fr".

For now there's no way in the Translate UI to revert a creation by accident (the deletion is denied, EVEN in the case where I am the only author); reverts only work when there is a previous version which can be restored.

So I as I could not delete them (permission denied), I juste emptied them (but as it was impossible to validate them, I marked them as "fuzzy" manually: NO resource were submited as completely empty, they contained exactly "!!FUZZY!!" after my revert).

They should have NEVER been exported at all, given the existing translation rate, but if this happened, you have a bug in your exporting rules, which bypass/ignore the minimum completion level or that can even export new messages containing only "!!FUZZY!!")

After that I though it was still safe; your export occured later (and I was not using the site for several hours as I was not even at home) to use my PC and I had no other connection.

Theses creations were expected (even if I thought that those resources were already translated, I thought they were renamed in the source or edited to be reformulated. (so they needed to be trnalated again, or they were not correctly moved and there was some transient effect). Checking them after setting again the language in "fr", I saw they were already all translated and unaffectd in French (and not just the 5 messages affected only in Afar), so I returned to select "aa" and blanked them with just the "!!FUZZY!!" mark (the only thing that was accepted).

Thanks for deleting them anyway. I did my maximum that I could perform in a short time with no more than a few minutes.

I don't know why the language selection was unpectedly changed to "aa" Afar (I could not find any reason in the recent navigation) when looking at my browser history) I suppose this could have been caused by some server timeout or a lost UI event that was not captured by my browser (but may be this is a bug in the Javascript for ULS which may in some unknown circonstances select instantly the first language code avaialble without showing that this selection occured "automatically", e.g. some duplicate click event managed in some racing conditions. This happened in a browser tab that was open (but idle) for several hours. Some UI evnet in that case may have been handled in the background and caused by other events carptured by the browser from the navigation in an unrelated tab, or by some broadcasted event genereted by Windows. These are suppositions, I can't explain why this occured.

Note that such unexpected switch to one language to another affect other users (rarely, but this happens for unexplained reasons that I cannot reproduce for now; and I've already noticved in the past that this alsos occured by yourself, and you did not notice it when I reverted you when you submitted translations to an unrealted language). Note that "aa" (Afar) is NOT even in one of my prefered languages. And I already had a couple of tabs opened with French selected in the USL, they were not affected; so this occured in a single , when I closed some other tabs open on TWN that I did not need to keep in the browser.

Take note that I had noticed the error and made my attempts to fix it (this affected only 5 messages in the same translation module). Note also that I did not use the ULS selector, I just refrenshed the page for the affected tabb and it was already showing "fr" as the current selection: I looked at my own history, and to investigate, and see what resoiurceds could have been affected, and made my maximum to revert these small "damages" (which were not dramatic, these were only recent "creations" in a langua for a module that acually had no prior translation for that message group, and I acted promptly to fix it, soit was certainly not exported anywhere and no other wikis were affected).

Verdy p (talk)19:09, 20 June 2022