GNOME Bugzilla – Bug 508313
fileformatchooser - Use plural forms
Last modified: 2021-06-10 20:51:43 UTC
Please use plural forms instead of (s) because in some languages (at least Spanish) the translation would be broken: #: ../cut-n-paste/fileformatchooser/eggfileformatchooser.c:417 msgid "Extension(s)" msgstr "" In Spanish singular is "Extensión" and plural "Extensiones" (note the tilde), therefore we can't have a good translation without plural forms. Thank you.
Thanks, let's resolve more generic problem first
aloriel, why doesn't msgid "Extension(s)" msgstr "Extensiones" work for you?
Because «extensiones» is plural, means more than one, and the string means that can be only one.
well, *you* said "use plural forms", not me...
what? I don't get it. In order to do a good translation either plural forms can be used or split the string into two: "Extension" and "Extensions". That's it.
The problem here is that Extension(s) is the column label, and the column may contain rows with only one and rows with more than one... Moving to libegg.
The problem is that the whole format chooser UI is broken. For example personally I don't see the purpose of the table duplicating the contents of combobox with format names. We'll remove formattable from Evince soon.
The "Extension(s)" should be changed to "Extensions" if the number of rows is not easily countable in the fileformatchooser before the string is displayed. If the number of rows can be counted before the string is displayed either use plural forms technique or two strings: "Extension" and "Extensions". I am not sure whether two strings will work for all languages, but it is enough for my language (Slovak).
any updates, still not fixed
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org. As part of that, we are mass-closing older open tickets in bugzilla.gnome.org which have not seen updates for a longer time (resources are unfortunately quite limited so not every ticket can get handled). If you can still reproduce the situation described in this ticket in a recent and supported software version of libegg, then please follow https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines and create a new ticket at https://gitlab.gnome.org/GNOME/libegg/-/issues/ Thank you for your understanding and your help.