Please delete MediaWiki:Centralauth-logout-progress/ka
https://translatewiki.net/wiki/MediaWiki:Centralauth-logout-progress/ka is obviously not Georgian but English. Could someone please delete that page?
Couldn't you just provide the actual Georgian translation instead of deleting (which will still have the effect to display the message in another fallback language, may be in Russian on some wikis that have such fallback, but most often in English ! There's nothing wrong in fact if there are some messages untranslated still in English (or partly in English). On Translatewiki.net (or other wikis using the translate extension), this is sometimes a transitory step, just allowing to initialize a set of pages with working links, before the whole set gets translated, without breaking things.
If you detect an English message that you want others to translate, the best thing to do is to just insert a "!!FUZZY!!" prefix before it, so that the message remains marked as needing an actual translation. You never need to delete that page, and this preserves its history.
I am convinced that this "!!FUZZY!!" prefix should be autodetected by the Translate tool, not even being displayed in the editable form when it is at start of a message, but replaced by a "yellow notification" displayed at top, and by a checkbox "mark this message as fuzzy" near the Save button. Internally the page will contain the edited message (even partly translated) but the "!!FUZZY!!" prefix will still be there: you can still continue editing it (in several steps), but as long as you don't uncheck that checkbox, saving it will still not change that status and it will be impossible to "validate" that message. A validator however can look at "!!FUZZY!!" messages and accept its content without having to do any editing, he will just unckeck that box and save again.
@Verdy p: feel free to just become part of the Georgian translation team and to just provide the translation. There is nothing wrong if there are some messages untranslated and nothing every challenged that so nobody knows why you bring that up even. For random FUZZY discussions please use a discussion forum.
@AKlapper: I know I can do that, but for this topic I cannot help. My reply was general. There are some reasons why resources get marked as fuzzy, and there's also a way to mark an existing translation as being fuzzy again, without deleting it completely (which is bad as it cancels all its history), when it is still actually requested and a fuzzy translation may still have contents whose translation is still unclear (frequently this is because the source message is ambiguous, and lacks documentation about its usage, e.g. missing clear distinction between isolated verbs and nouns in English, or multiple meanings of the same orthographic term). Another reason is that most of the message was considered OK, but there's an issue in the existing translation caused by an update in the source message. Making some resources fuzzy is enough to solve those issues without deleting them. Another viable reason is that a single resource for a translatable page is marked fuzzy (only copying the English source) in order to force the translation tool to create the first version of the target page (which has incoming links to it): even if the whole page is still not translated, it is still best that it displays the English fallback content, even if the whole page remains to be translated. Finally another reason is that it also allows importing resources from an older translated page (but whose translation was manual, still present in its history, and its existing content will be manually parsed to import and convert it to the translate tool. So the "fuzzy" mark is an intermediary step before looking for other existing pages to find the terminology previously adopted. It's a useful feature, even for actual translators.