GNOME Bugzilla – Bug 570902
Support "--previous" msgmerge option
Last modified: 2019-02-27 15:14:52 UTC
Using the "--previous" option from msgmerge, the generates PO shows something like this: #: ../src/brasero-src-image.c:244 ../src/brasero-burn-options.c:308 #, fuzzy #| msgid "Please, select another image." msgid "Please select another image." msgstr "Scegliere un'altra immagine." Files generated for http://l10n.gnome.org are currently using this feature. Could be a really good idea support this in Gtranslator 2.0, but honestly I've no stong or really good idea about the proper place to show the previous message. One solution could be put an icon near "Original Text" label and show the previous message in a tooltip that appears when you mouse-over this icon. Please note could be good remove the "previous" message from PO file on unfuzzy(+save), in order to keep clean the file (if you unfuzzy, you no longer need the reference to previous message, I suppose).
I also think that removing the "previous" message would be a good and (guessing) a relatively easy to implement start towards full --previous support. A suggestion on how to show "previous" strings without modifying the current UI would simply be to show a "Previous line:" in the context panel.
I'm totally +1 on this one. Where to show the string? I would say that a showing it below the msgid string would be OK for most of the strings, it's not an ideal solution for long strings though... What would be really cool though, is showing them as a meld-like diff, because if you do care about the previous string is mostly just to see what differences are from the old to the new one, does it add a dot at the end, or it removes it, does it only capitalize some letters.. So maybe coloring (meld-like) the actual string or a split view with the old and the new one would be really useful to spot the differences between the strings. Something like: +-----------+-----------+ | new_msgid | old_msgid | +-----------+-----------+ | msgstr | +-----------+-----------+ So that if the translation does not have any previous string the UI does not change that much: +-----------------------+ | new_msgid | +-----------------------+ | msgstr | +-----------------------+ Cheers,
*** Bug 790971 has been marked as a duplicate of this bug. ***
I'm also totally +1 on this. I've been contributing for years to a project that does not use gettext, but a 'git diff' system, to update the translated manuals. This feature would bring together the best of the two worlds. I like Gil's mockup.
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