After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 648678 - g_date_time_format(): support %O flags for localized numbers
g_date_time_format(): support %O flags for localized numbers
Status: RESOLVED FIXED
Product: glib
Classification: Platform
Component: general
unspecified
Other Linux
: Normal major
: ---
Assigned To: gtkdev
gtkdev
: 650086 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2011-04-26 16:24 UTC by Arash Mousavi
Modified: 2011-05-26 15:24 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
wip patch (9.01 KB, patch)
2011-05-05 15:33 UTC, Matthias Clasen
none Details | Review

Description Arash Mousavi 2011-04-26 16:24:16 UTC
usually using %O flags in translations should cause the system to show numbers in locale formats e.g. if %H shows 23, using %OH in Persian locale should show ۲۳. But using these flags causes the Shell to freeze at startup (like whats happening in 3.0.1 version and Persian language)
Comment 1 Owen Taylor 2011-04-26 16:30:21 UTC
The shell simply uses g_date_time_format() for this, so the enhancement would have to be done in GLib.
Comment 2 Dan Winship 2011-05-04 12:19:02 UTC
glibc also supports a bunch of other useful formats. Eg, non-0-prefixed hours and days. bug 647320 suggests supporting those as well.
Comment 3 Matthias Clasen 2011-05-05 15:33:35 UTC
Created attachment 187287 [details] [review]
wip patch

Here is an unfinished patch that adds support for the O, -, _ and 0 modifiers to g_date_time_format(). Patch is missing docs and tests.
Comment 4 Hedayat Vatankhah 2011-05-17 07:12:18 UTC
Will this patch fix bug #553770 and #511626?!
Thanks for the patch anyway! :)
Comment 5 Hedayat Vatankhah 2011-05-17 07:13:22 UTC
Sorry for the wrong formatting: bug #511626 and bug #553770
Comment 6 Owen Taylor 2011-05-26 15:24:05 UTC
*** Bug 650086 has been marked as a duplicate of this bug. ***