Glom 1.8.1 Year error with date fields

Bug #300057 reported by Maximiliano
2
Affects Status Importance Assigned to Milestone
glom (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: glom

Create a data field
Enter data like 19/11/2008
Glom asume 2008 like 1908

Related branches

Revision history for this message
Murray Cumming (murrayc) wrote :

What locale are you using? This is probably only a (fixable) problem in that locale.

Revision history for this message
Maximiliano (meilan) wrote :

May be, Spanish, Uruguay, utf-8

LANG=es_UY.UTF-8
LC_CTYPE="es_UY.UTF-8"
LC_NUMERIC="es_UY.UTF-8"
LC_TIME="es_UY.UTF-8"
LC_COLLATE="es_UY.UTF-8"
LC_MONETARY="es_UY.UTF-8"
LC_MESSAGES="es_UY.UTF-8"
LC_PAPER="es_UY.UTF-8"
LC_NAME="es_UY.UTF-8"
LC_ADDRESS="es_UY.UTF-8"
LC_TELEPHONE="es_UY.UTF-8"
LC_MEASUREMENT="es_UY.UTF-8"
LC_IDENTIFICATION="es_UY.UTF-8"
LC_ALL=

Revision history for this message
Murray Cumming (murrayc) wrote :

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.

Changed in glom:
status: New → Fix Committed
Revision history for this message
Maximiliano (meilan) wrote : Re: [Bug 300057] Re: Glom 1.8.1 Year error with date fields

Thanks.

El vie, 21-11-2008 a las 14:38 +0000, Murray Cumming escribió:
> 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.
>
>
> ** Changed in: glom (Ubuntu)
> Status: New => Fix Committed
>
--
                  ____________________________________
                             Estudio MEILÁN
                     (arquitectura y construcción)
                  Avda. Artigas y Zabala - Piriápolis
                            Tel. (043) 27431
                  ___________________________________

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package glom - 1.8.5-0ubuntu1

---------------
glom (1.8.5-0ubuntu1) jaunty; urgency=low

  * New upstream release (LP: #256701), fixes LP bugs:
    + Clear the text in property dialogs for text items (LP: #309147)
    + Don't crash when showing and then hiding the grid (LP: #303453)
    + Temporarily remember the sort order so it is the same when navigating
      away and back (LP: #303422)
    + Use the list's sort order for the top-level records in the report
      (LP: #303425)
    + Users/Groups: Disable drag-and-drop for the treeview, because it is
      useless and confusing (LP: #299573)
    + Import: Sort the fields list alphabetically (LP: #306593)
    + delete primary key make unusuable the database (LP: #299549)
    + Spanish translate incomplete (LP: #299556)
    + import date format error (LP: #299591)
    + can't delete data from table list view (LP: #299853)
    + Field definition: default value not saved (LP: #299896)
    + reports crashing (LP: #300054)
    + Year error with date fields (LP: #300057)
    + list view: 2 records added instead of 1 (LP: #300819)
  * debian/control: Refreshed dependencies for libglom-dev.
  * debian/control: Updated build-deps to match configure checks. goocavnasmm
    build-dep bumped to version without .la files.
  * debian/rules: Don't delete the directory containing the templates.
  * debian/control, debian/rules, debian/glom-doc.*: Split out
    arch-independent manual and examples into separate package glom-doc, which
    is now recommended by glom (glom will still work if they're not available)
  * debian/copyright: Rewritten to new machine-readable format.

 -- Iain Lane <email address hidden> Sun, 11 Jan 2009 17:12:01 +0000

Changed in glom:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.