Since ota5 hours are displayed as "uu" in dutch

Bug #1476270 reported by erikonthenet on 2015-07-20
36
This bug affects 7 people
Affects Status Importance Assigned to Milestone
Telegram app
High
Unassigned

Bug Description

since ota5, time is not displayed correctly in dutch. For example, instead of "17:13", it says "uu:13".
This representation is displayed in message time and in last-seen time.

Probably a translation error in the used time format. Rebooted my phone in English, time is then displayed correctly.
Used phone: BQ E4.5

Michał Karnicki (karni) on 2015-07-20
Changed in libqtelegram:
status: New → Triaged
importance: Undecided → High
erikonthenet (erik-loosman) wrote :

Proposed solution: telegram-app:
/po/nl.po line 157
change msgstr to hh:ss

Michał Karnicki (karni) wrote :

Derp. This missed a critical update release to QA by minutes :( We'll get it in the next one :) Thank you for your suggestion!

erikonthenet (erik-loosman) wrote :
Michał Karnicki (karni) wrote :

Hi Eriko,
Have you found that within launchpad translation and fixed it there? Or just modified the file? Launchpad would overwrite it as long as the translation is incorrect.
I am terribly sorry about the delay on this bug, I can imagine it's frustrating. I'm working on a major update right now..

Timo Vanwynsberghe (timovwb) wrote :

Still not fixed in OTA-6!

Michał Karnicki (karni) on 2015-10-02
tags: added: v2
Michał Karnicki (karni) on 2015-10-02
tags: added: v2-verify
removed: v2
Michał Karnicki (karni) on 2015-10-02
Changed in telegram-app:
milestone: none → alpha1
status: Triaged → Fix Committed
Michał Karnicki (karni) wrote :

Fixed it via lp translations. Not sure how it's possible *I* translated it incorrectly, as I don't know Dutch, but hey \o/

Changed in telegram-app:
milestone: alpha1 → alpha2
Ferry Toth (ftoth) wrote :

Still not fixed in OTA 7

Ferry Toth (ftoth) wrote :

That would be Telegram 3.6

Michał Karnicki (karni) on 2015-11-17
Changed in telegram-app:
status: Fix Committed → Fix Released
Ferry Toth (ftoth) wrote :

I confirm this issue is resolved in v2.0.4.0 (arrived in the store around 17 nov 2015)

Michał Karnicki (karni) wrote :

Thank you, Ferry Toth!

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers