I am testing Gramps version 6.0.8 installed as a “.deb” package on Linux Xubuntu 26.04.1.
I have noticed a translation issue “in French” in the “Edit Person” window.
The label for the field corresponding to the person’s First Name is displayed as “Given” instead of “First Name” as it was in previous versions of Gramps.
Is there a workaround I can apply while waiting for a future corrected version?
Is there a quick way to extract where such context was added? This would give @Poun64 a checklist of place to validate. Perhaps the additional context broke them all? And if not all, we could isolate where (and why) there was a difference.
Understood that the additiinal “given name” context was in just those 2 places.
My question was about if broader applications of the context flag were implemented at the same time. And if those broke translations elsewhere. More importantly, if they did NOT break translations, whether analyzing the differences could teach us about how to fix/avoid the breakages.
Could you point us to where that was addressed? (Or the terminology used so we can search the PRs?)
This would allow me to point out for @Poun64 the other places in code modules that he (and other users of localization) might have to tweak in the 6.0.8 version.
(Since 6.0.8 is the current release and the schedule for the next release is not yet set in stone.)
In the Translation update section of the What to do for a release document, I added the line “After updating the pot file, push the changes and wait for Weblate to update the po files. Merge the corresponding pull request from Weblate.”.
… it looks like you’re running gramps from source (not via package or installation)?
I’m not (yet) on branch 6.0. Previously, when we saw the debug tools menu, it was because we were launching gramps from source (rather than after an installation that formats translations - binaries via msgfmt).
It’s as if we had installed version (say) 6.0.4, then downloaded the sources and launched gramps from the latest GitHub version or the 6.0.8 version sources. Is that the case?
It’s just new strings with context. If there hasn’t been an update to the fr.po file before the release of the version, then it’s probably logical that the new string remains in English.