18.02.2018 13:36 Robert Antoni Buj i Gelonch <robert.buj(a)gmail.com> wrote:
> > 1. Patch glibc in Fedora until upstream glibc will be patched and patch
> > GNOME
> etc. to be consistent with the new placeholders.
> >
glib2 (GNOME, XFCE, ...) will use native libs (glibc in Linux) to convert
dates to strings for now [1]
[1]
https://github.com/GNOME/glib/commit/be4f96b6502c01d2a51d60b7a669c8ef82e2...
Partially yes, partially no. First of all, tt will use native
libs if native libs provide the list of month names correctly.
That means that everything works perfectly on glibc 2.27 (Fedora 28),
except the languages which have not yet been updated (e.g.,
Catalan). The build scripts recognize the supported API but
do not proofread the list of months and date formats in all
languages. :-) If the same glib2 is built on older Linux
(Fedora 27 or RHEL) or non-Linux (BSD, OS X, Windows) it will
use the translator delivered strings.
And this is the place which makes me worried. The commit which
you quoted requires the translators to update their list of months.
In most cases DamnedLies should suggest the existing translations
and they should just confirm that the translations are correct
and uncheck the fuzzy flag. So far only the following languages
have been updated to provide full list of month names: Portuguese
(Brazilian), Polish, Friulian, Galician, Indonesian and German.
Total number of supported languages is 98; this includes 3 variants
of English so we can count 95. (Catalan is not updated: Robert, you
have pushed an old *.po file).
Second, g_date_time_format is not the only function which displays
dates in glib2, another one is g_date_strftime() which will work
OK in Unix platforms but needs an update for Windows. [2]
Thank you for your concerns, Robert and Yuri. Most of these bugs
are upstream but I think someone at Fedora side should take care
of tracking the problems and providing test cases. I will appreciate
if someone joins my efforts.
Regards,
Rafal
[2]
https://bugzilla.gnome.org/show_bug.cgi?id=749206