GNOME Bugzilla – Bug 745763
Typos in anjuta am plugin: "overwritting"
Last modified: 2015-03-25 21:07:45 UTC
There are several instances in the documentation of the typo "overwritting": https://git.gnome.org/browse/anjuta/tree/plugins/am-project/am-properties.c#n476 https://git.gnome.org/browse/anjuta/tree/plugins/am-project/am-properties.c#n651 etc. The attached patch aims to fix those.
In the documentation!? But I even linked to the am-project plugin... Oh well, you get what I mean I hope.
Created attachment 298752 [details] [review] Proposed patch.
Review of attachment 298752 [details] [review]: Thank you for your fixes. I have just committed it.
Does Anjuta follow the GNOME release cycle? This commit changes a string and we're in string freeze (or at least change announcement period if you have yet to publish a 3.15.91 tarball).
(In reply to Alexandre Franke from comment #4) > Does Anjuta follow the GNOME release cycle? This commit changes a string and > we're in string freeze (or at least change announcement period if you have > yet to publish a 3.15.91 tarball). Indeed Anjuta try to follow the GNOME release cycle. I have reverted this commit and I will push it after the release. Thank you for reporting this error.
No please don't do that. Fixing a typo is a good thing and you'd be granted the two approval from i18n if you just asked for it.
(In reply to Alexandre Franke from comment #6) > No please don't do that. Fixing a typo is a good thing and you'd be granted > the two approval from i18n if you just asked for it. Sorry, I have already reverted this commit. I have understood that asking for an approval was only a second choice. As I'm not a translator, I cannot evaluate the burden cause by this change so I have chosen the easiest solution. Then, a problem is that such bugs are found mostly by translators, as the user don't care much about the documentation, so typically during the string freeze period when translators are working. According to the rule, they can be fixed only 6 months later, it's not perfect but I'm not sure there is a better solution. Anyway, for this particular case, this spelling mistake is present since probably a few years, I think it can wait 6 additional months. André has tagged this bug as "string", I will try to remember it. This will be a case where the translated version of the documentation will be better than the original.
I have committed the patch after the release.