Comment 8 for bug 1986803

Revision history for this message
In , Amin Husni (aminhusni-5) wrote :

Problem Summary
====================

Date format problem when representing time in ms_MY. 12-hour clock is used despite AM/PM localization string is empty.

Expectation:
When running the command `date`, output was `Rabu 17 Ogos 2022 20:35:36 +08`

What happened instead:
When running the command `date`, output was `Rabu 17 Ogos 2022 08:35:36 +08`

These were run during the PM side of time. When running it in the morning, it shows as expected.

Problem Detail
====================

The current locale format does specify to print AM/PM markers but the localized strings for AM/PM are empty.

I am confident that we do not actually have an established time format in a standardization sense. At least when I try to find it on The Official Website of Department of Standards Malaysia.
However, for the official Malaysian time format according to Kamus Dewan Bahasa (Institute of Language and Literature), AM and PM are not used in the language.

Ref (translated):
https://prpm.dbp.gov.my/Cari1?keyword=pm&d=175768&

In Malay Language, the words am and pm are not used, instead for the time period 1.00 am - 11.59 am is called morning, 12.00 pm - 1.59 pm is called noon, 2.00 pm - 6.59 is called evening, 7.00 pm - 11.59 pm is called night and 12.00 am - 12.59 generally called midnight.

Original source text:
Dalam bahasa Melayu perkataan am dan pm tidak diunakan, sebaliknya untuk tempoh masa 1.00 am - 11.59 am dinamakan pagi, 12.00 pm - 1.59 pm dinamakan tengah hari, 2.00 pm - 6.59 dinamakan petang, 7.00 pm - 11.59 pm dinamakan malam dan 12.00 am - 12.59 am dinamakan tengah malam.

With that said, I think this is definitely not going to work with the localization files.

One way I would suggest solving this is to compromise on a 24-hour format since that is the international standard notation of time (ISO 8601).

Additional Bug Reference
====================

https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1986803