Page MenuHomePhabricator

Implement Japanese and North Korean calendars
Closed, ResolvedPublic

Description

In r50778 the http://en.wikipedia.org/wiki/Minguo_calendar of Taiwan has been implemented.

An excellent reuse of code could be had here by now also implementing the
http://en.wikipedia.org/wiki/Juche#Calendar of North Korea, as it is the
exactly the same as Taiwan's (year 98=2009).

While you are at it, consider implementing
http://en.wikipedia.org/wiki/Japanese_era_name , 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.


Version: 1.16.x
Severity: enhancement

Details

Reference
bz18849

Event Timeline

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

OK, I see you say 平成 for Japanese, please
also add the familiar names for Taiwan, see the note I made at
http://www.mediawiki.org/wiki/Special:Code/MediaWiki/50778#code-comments
please.

One can guess that you should also offer the two character prefix
주체(主體) for Korea, but maybe they only use one character...

Speaking of which, perhaps also add a short 民98年... one character
choice for Taiwan too.

Created attachment 6139
Group international time notation systems together at top instead of split

Attached:

Please apply attachment 6139 to stop intermingling local and international time notations.
They will then be international first, then local afterwards.

ISO has always come as last, why change that?

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

The position of the ISO date is a seperate issue for that, please add the
comments in the bug 18931 instead.

The original purpose of this bug has been FIXED before.

Sorry my mistake, please add the comments to the bug 18932 instead.