Essentially reorganise the modules, rename some functions, and create a Date property on draconitic moon cycle, that enables anticipating possible eclipses.

French revolutionary:

• 12 months with 30 days,
• one "month" of 5 or 6 complementary days.

Cycles:

• Franciade: 4 or 5 years cycle, the last year being a sextile year (366 days)
• 33 year cycle: 7 4-years Franciade, 1 5-years Franciade.

To do:

• Open branch
• Extend CalendarCycleComputation in order to handle the 4 or 5 years Franciade
• Construct the conversion routine
• Add the line with French Rev calendar to standard layout pages

Instead of "free" functions:

• package in classes the base calendrical computations, with new names in order to help progressive transition (partially done for Temporal-experiences.
• add to this basic package TZmsOffset
• Try to extend Date object instead of adding properties - CustomDate (calendar)
• Define pldr - Private Locale Data Register (keep ?)
• Extend Intl.DateTimeFormat class using pldr, or pldr1, pldr2 etc.

Milesian month names of different languages are specified in an XML file that conforms to Unicode LDRL. Error messages need to be designed in different languages. As of now, month names and messages have been "isolated" in special Javascript files. Now we want to fix them in XML files that are handled as loadable files, in a different domain. This branch is for this tries.

Why the window.setInterval command inserted in clock display software does not work if inserted on a web site ?

Enable to choose one of the CLDR registred calendar and to display the date in this calendar.

The converter uses the UTC date at 00:00. This may differ from the local date. Using "now" should set to the terminal's local date.

The javascript module demonstrator (with nothing else) needs manual changes if integrated in a same CMS site. Use a common initiator.

Modify JS as to demonstrate how a new option hiddenEra would work.