Comment 3 for bug 300057

This was fixed by adding a translation of the %x format in the po/es.po file.

These commits also mean that Glom will guess a date format (sometimes wrongly) when the translator has not provided one. This will be in a new glom 1.8.x release soon:

2008-11-21 Murray Cumming <email address hidden>

 * glom/libglom/data_structure/glomconversions.c:
 sanity_check_date_text_representation_uses_4_digit_years():
 Default to dd/mm/yyyy for dates when the translator has not provided
 a 4-digit-year date syntax for the locale, printing a warning that the
 default might not be suitable. This seems better than failing.

2008-11-21 Murray Cumming <email address hidden>

 * glom/libglom/data_structure/glomconversions.[h|cc]:
 Added sanity_check_date_parsing() and
 sanity_check_date_text_representation_uses_4_digit_years().
 * glom/main.cc: Use them to show informative warnings at startup.
 The translators comment for %x mentions those warnings now too.
 * po/es.po: Add a translation for %x because the es locales do not
 use 4-digit years for this.
 Ubuntu bug https://bugs.launchpad.net/ubuntu/+source/glom/+bug/300057

 * glom/test_pyembed.cc: Add a cast to avoid a warning.
 * glom/utility_widgets/db_adddel/db_adddel.cc: Initialize InnerIgnore
 members to avoid warnings, though these would always be initialized in
 real life.