Lots of languages have genders to refer to things, so a table can be male or female and such (weird I know, but languages have had organic evolution...).

The problem are this strings:

msgid "Select <b>New</b> to add an alarm"

msgid "Select <b>New</b> to add a world clock"

#. Translators: "New" refers to a world clock or an alarm
msgid "New"

The "New" strings where there's a polite comment to translators indicating that can be clock or alarm falls into that problem described before, at least in Catalan, and I'm sure in many other languages, Clock (rellotge, male) and Alarm (alarma, female) can not share the same New (nou - male, nova - female).

Fortunately gettext is already aware of this facts and allows to provide a context for a given string.

See [1] for the technical details on how to define a context for a string.

Foot note: as we are currently in hard code freeze and this also breaks string freeze, please push the fix once the .0 is out. Is not so critical to have it fixed ASAP, but would be nice to have it before it lands on major distributions (which usually take the .1 GNOME releases).


[1] https://live.gnome.org/TranslationProject/DevGuidelines/Translation%20contexts