[Bug 1986803] Re: Incorrect/misleading Time Format For ms_MY (AM/PM)

[Bug Watch Updater]

Launchpad has imported 1 comments from the remote bug at
https://sourceware.org/bugzilla/show_bug.cgi?id=29504.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.

------------------------------------------------------------------------
On 2022-08-17T21:12:55+00:00 Amin Husni 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

Reply at:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1986803/comments/6


** Changed in: glibc
       Status: Unknown => New

** Changed in: glibc
   Importance: Unknown => Medium

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to glibc in Ubuntu.
https://bugs.launchpad.net/bugs/1986803

Title:
  Incorrect/misleading Time Format For ms_MY (AM/PM)

Status in GLibC:
  New
Status in glibc package in Ubuntu:
  New

Bug description:
  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.

  Additional Information:
  Description:	Ubuntu 22.04.1 LTS
  Release:	22.04

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: locales 2.35-0ubuntu3.1
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 17 20:30:44 2022
  InstallationDate: Installed on 2022-08-12 (4 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1)
  PackageArchitecture: all
  SourcePackage: glibc
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/glibc/+bug/1986803/+subscriptions