This reverts commit 489e66d2.
It was breaking string freeze and it's not needed on the stable branch.
https://mail.gnome.org/archives/gnome-i18n/2017-February/msg00026.html

The compiler is now more picky about modifiers

When resetting the timer, the values for the spinbuttons are determined
from the timer starting amount in seconds. In order to get the correct
number of minutes from this value, we must first account for the number
of hours present (mod 3600) before converting from seconds to minutes
(truncated division by 60).

https://bugzilla.gnome.org/show_bug.cgi?id=774479

Switching to a standalone view sets the header bar title to the name of
the location. Leaving the view does not reset the title like it should.

https://bugzilla.gnome.org/show_bug.cgi?id=772677

https://bugzilla.gnome.org/show_bug.cgi?id=749983

https://bugzilla.gnome.org/show_bug.cgi?id=771936

day_label() compares the day of the year between timezones to determine
whether it should display a "Yesterday" or "Tomorrow" label on a user's
configured world clocks. It accounts for the case where it is Dec 31st
at the user's location (variable t below) but Jan 1st at a remote
location (variable d) by performing the following check:

if (d < t) {
  // If it is Dec 31st here and Jan 1st there (d = 1), then "tomorrow"
  return d == 1 ? _("Tomorrow") : _("Yesterday");

But (d < t) && (d == 1) will also be true when d = 1 and t = 2. This
causes the "Tomorrow" label to be displayed on world clocks where it
is in fact still yesterday, if the user's current date is Jan 2nd.

The same thing happens when the user's current day is Jan 1st - world
clocks that should display "Tomorrow" display "Yesterday" instead.

To fix this, we can simply account for the Jan 2nd edge case when
d < t as follows:

  return (d == 1 && t != 2) ? _("Tomorrow") : _("Yesterday");

and similar for the (d > t) case.

https://bugzilla.gnome.org/show_bug.cgi?id=722465

https://bugzilla.gnome.org/show_bug.cgi?id=767495

https://bugzilla.gnome.org/show_bug.cgi?id=768437

This restores the previous font proportions with the new gtk.

msgfmt --desktop ignores the default keywords if custom keyword is
specified.  This behavior is inconsistent and should be fixed in msgfmt,
but list those missing keywords to work around the issue.

https://bugzilla.gnome.org/show_bug.cgi?id=771641

Signed-off-by: Trần Ngọc Quân <vnwildman@gmail.com>