GNOME Bugzilla – Bug 600387
"Replace all" removes the fuzzy status from all strings regardless
Last modified: 2019-02-27 15:15:22 UTC
When using Search & replace, it changes the status of all fuzzy strings, even if they are not involved in the replacement. This is wrong, it may only change the status of those affected.
This has just bitten me as well. This is a rather severe bug, marking it as such. Renaming summary. Steps to reproduce: 1. Open a PO file with fuzzy strings 2. Search -> Find and replace 3. Enter some arbitrary Find and Replace strings. 4. Hit "Replace all" All fuzzies are marked translated
You are right. I'll try to fix it ASAP.
What happened with this bug? I'm using gTranslator compiled from master branch and this bug persists. Search and repalce is a very useful tool, but it is unusable if the po file has fuzzy strings. Thanks :)
Well, nacho does some work on gtranslator as I can see from the git commits, but apparently he has not had enough time or other priorities to work on this one. I would be happy if he looked at this, too. Patches are always welcome :) At the moment I do not have enough spare time to look into this.
*** Bug 657069 has been marked as a duplicate of this bug. ***
Well, the main problem here is that the search is probably the crappiest part of gtranslator. Maybe we can make a hack to fix this, but fixing it correctly which is the reason I didn't do it as it would require quite some rewrite needs a lot of time. Hack: We must set a flag in the tab specifying that the tab is in search mode, this way when we change the message we keep the state. Correct: Right now we keep 2 lists, the first point would be to fix this, where the TreeModel would implement an iterable interface and we would feed that interable list instead of having the treemodel and the GList. Once we have that ready things would become easier and we could think on easier fixes for replace and other problems derivated on this.
We are mass-closing old gtranslator issues as the latest versions of gtranslator (3.30 or later) should fix most of the reported problems and as there is unfortunately no capacity to retest all of them separately. https://mail.gnome.org/archives/desktop-devel-list/2019-February/msg00059.html If the issue described in this report still happens in gtranslator version 3.30 or later, please file a new ticket under https://gitlab.gnome.org/GNOME/gtranslator/issues/ - thanks for your understanding! We are sorry that your report was not handled / fixed after you reported it - many free and open source software projects receive more bug reports and feature requests than they have developers who have free time to work on them. If you would like to get involved and contribute on gtranslator code, please check https://wiki.gnome.org/Git/Developers