Page MenuHomePhabricator

Don't intermingle local and international time notations
Closed, InvalidPublic


+++ This bug was initially created as a clone of Bug #18849 +++
+++ Reported by Jidanni +++

In r50778 the of Taiwan has been implemented.

An excellent reuse of code could be had here by now also implementing the of North Korea, as it is the
exactly the same as Taiwan's (year 98=2009).

While you are at it, consider implementing , as the article says
"Japanese era names are still in use. Government offices usually require
era names and years for official papers."

So just as here in Taiwan, one can imagine many government etc. offices where
they would be overjoyed to be able to use such dates.

As I am very much not the right man for this job, I would like to leave this bug
in the system to give others an opportunity to evaluate and/or implement it.

Bug 18849 comment 4
attachment 6139
Group international time notation systems together at top instead of split

Bug 18849 comment 5
Please apply attachment 6139 to stop intermingling local and international time
They will then be international first, then local afterwards.

Bug 18849 comment 6
ISO has always come as last, why change that?

Version: 1.16.x
Severity: enhancement



Event Timeline

bzimport raised the priority of this task from to Medium.Nov 21 2014, 10:39 PM
bzimport set Reference to bz18932.
bzimport added a subscriber: Unknown Object (MLST).

Bug 18849 comment 7
OK, I see. Then instead of putting all international before local, put
all local before international. What ever you do, don't intermingle them.

As the default date format is not using the international format (e.g. ISO),
also the ISO date format would be always come as last.

As current, it does not showing that the date formats are intermingle against
each other, so the bug would be closed as INVALID.