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 753973 - Gnome shell calendar should use localised numbers for Farsi/Persian
Gnome shell calendar should use localised numbers for Farsi/Persian
Status: RESOLVED OBSOLETE
Product: l10n
Classification: Infrastructure
Component: Persian [fa]
git master
Other Linux
: Normal normal
: ---
Assigned To: mahyar
mahyar
Depends on:
Blocks:
 
 
Reported: 2015-08-23 01:52 UTC by Amir Mohammadi
Modified: 2019-03-20 10:53 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Gnome shell clock times are wrong (56.71 KB, image/png)
2015-08-23 01:52 UTC, Amir Mohammadi
Details

Description Amir Mohammadi 2015-08-23 01:52:50 UTC
Created attachment 309879 [details]
Gnome shell clock times are wrong

I am using an RTL language, Persian فارسی (LANG=fa_IR.UTF-8), on my system and there are some bugs in Gnome shell.

I think this problem arises because localised numbers are not being used. Some languages use Arabic numbers and this is not done in Gnome shell and causes an RTL bug when clock values are displayed.

If you look at the attachment, the world clock values are wrong. For example one of the times is 41:04 which actually should be 04:41 or better yet it should be ۰۴:۴۱.

Moreover, the day numbers in calendar are shown like 1, 2, 3, ... while they should be ۱, ۲, ۳, ...

I think if localised numbers were used the RTL bug in clock will be fixed.
Comment 1 André Klapper 2015-08-23 16:28:43 UTC
Thanks for reporting this.

The PO file at https://l10n.gnome.org/vertimus/gnome-shell/master/po/fa has some translations.
Some of those strftime formats look potentially broken to me, for example the line 
   msgstr "<b>دیروز</b>، <b>%OH:%OM"

Some are just inconsistent, like e.g.
   msgid "%l∶%M %p"
   msgstr "%Ol∶%OM %p"
using a %p and keeping the %l but
   msgid "Yesterday, %l∶%M %p"
   msgstr "دیروز، %OI:%OM"
not using a %p and converting the %l to %I.

I'm moving this bug report from gnome-shell developers to Persian translators for the time being.
Comment 2 André Klapper 2015-08-25 10:46:53 UTC
Amir: The underlying problem might actually be bug 673235 instead.

Still I'd keep this ticket open for the inconsistency in the PO file...
Comment 3 Amir Mohammadi 2015-08-25 11:37:13 UTC
Dear André,

Thank you for looking into this problem. Bug 673235 only fixes a part of my problem. My biggest problem is the world clock part which shows the clocks incorrectly.

I looked around the problem seems to arise from one of these places:
https://github.com/GNOME/gnome-shell/blob/gnome-3-16/js/misc/util.js#L191
or
https://github.com/GNOME/gnome-shell/blob/gnome-3-16/js/misc/util.js#L246
called from here:
https://github.com/GNOME/gnome-shell/blob/gnome-3-16/js/ui/dateMenu.js#L208

the po file
https://l10n.gnome.org/POT/gnome-shell.gnome-3-16/gnome-shell.gnome-3-16.fa.po
#. Translators: Time in 24h format */
#: ../js/misc/util.js:191
msgid "%H∶%M"
msgstr "%OH∶%OM"


Now I don't know exactly in which part it decides to use Latin numbers instead of Arabic numbers. Do you?
Comment 4 André Klapper 2015-08-25 12:36:10 UTC
(In reply to Amir Mohammadi from comment #3)
> Now I don't know exactly in which part it decides to use Latin numbers
> instead of Arabic numbers. Do you?

Personally I don't, but please ask on the mailing list at https://mail.gnome.org/mailman/listinfo/gnome-i18n and/or the #i18n IRC channel (see https://wiki.gnome.org/Community/GettingInTouch/IRC ) to get answers. Thanks!
Comment 5 GNOME Infrastructure Team 2019-03-20 10:53:41 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/Teams/Translation/migration/issues/33.