After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 707562 - Plural forms for "%d elements"
Plural forms for "%d elements"
Status: RESOLVED FIXED
Product: anjuta
Classification: Applications
Component: plugins: project-manager
git master
Other All
: Normal normal
: ---
Assigned To: Naba Kumar
Anjuta maintainers
Depends on:
Blocks:
 
 
Reported: 2013-09-05 13:02 UTC by Marek Černocký
Modified: 2013-09-10 19:59 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Fix (1.01 KB, patch)
2013-09-07 08:57 UTC, Sébastien Granjoux 		none Details | Review

Description Marek Černocký 2013-09-05 13:02:32 UTC 
Message

"Are you sure you want to remove %d elements from the project?\n\n"
(plugins/project-manager/plugin.c)

requires to use ngettext instead gettext because some languages has more complex rules the "one or more".
Comment 1 Sébastien Granjoux 2013-09-07 06:54:11 UTC 
This message is used only when there is at least 2 elements to remove. I will add a comment for translator to indicate this.

So, it should be fine for languages making the different between one and more. For other languages, indeed I need to use ngettext but we are currently in string freeze period, so I need to ask before pushing such change.
Comment 2 Sébastien Granjoux 2013-09-07 08:57:45 UTC 
Created attachment 254333 [details] [review]
Fix
Comment 3 Johannes Schmid 2013-09-08 11:37:16 UTC 
I think that is still not ok. There are languages that even makes differences between two and three or ten and more so ngettext needs to be used in any case. It is not difficult to do - so I think we should just use ngettext to respect those grammers.
Comment 4 Sébastien Granjoux 2013-09-08 16:59:25 UTC 
(In reply to comment #3)
> I think that is still not ok. There are languages that even makes differences
> between two and three or ten and more so ngettext needs to be used in any case.
> It is not difficult to do - so I think we should just use ngettext to respect
> those grammers.

I haven't written that ngettext is not needed. It's needed to use ngettext for those languages, I have used it in the patch.

Now, for languages where there is only a difference between one and more than one, the patch is not needed and a comment for translator is enough which can be push without breaking the string freeze.
Comment 5 Johannes Schmid 2013-09-08 17:38:37 UTC 
Sorry, misread your comment in the first place...