[bug-gettext] [bug #50910] Indicate reused strings in msgmerge verbose output

Follow-up Comment #4, bug #50910 (project gettext): For me, that's clearly b). I also understand the possible confusion concerning the build process. I think that during the recent years, build toolchains in the GNOME world partially lost the habit/interest to do more than compiling the .po to .m

[bug-gettext] [bug #50910] Indicate reused strings in msgmerge verbose output

Follow-up Comment #3, bug #50910 (project gettext): Thanks for explaining. Now I understand. The point of keeping the history is precisely to save some work from the translator in such situations. The question is how much work you want to save her: a) If you think the translator should review th

[bug-gettext] [bug #50910] Indicate reused strings in msgmerge verbose output

Follow-up Comment #2, bug #50910 (project gettext): OK, I'll try! Time t: a module is translated at 100% in language ll. The committed ll.po contains some unused obsolete strings (from previous history). Time t+1: the source code changes and adds a new string which maps exactly to one of the ll.

[bug-gettext] [bug #50910] Indicate reused strings in msgmerge verbose output

Update of bug #50910 (project gettext): Category: PO, POT => None Status:None => Need Info ___ Follow-up Comment #1: Please, can you exp

[bug-gettext] [bug #50910] Indicate reused strings in msgmerge verbose output

URL: Summary: Indicate reused strings in msgmerge verbose output Project: GNU gettext Submitted by: claudep Submitted on: Tue 02 May 2017 07:34:40 AM UTC Category: PO, POT