Written today/02-29

From GATE
< Written today
Revision as of 11:10, 24 March 2020 by Lorenzo Mancini (talk | contribs) (Created page with "<nowiki> </nowiki>{{#ask: has certain date::1550-02-29|format=ul|sep=<br>}}<nowiki> </nowiki>{{#ask: has certain date::1551-02-29|format=ul|sep=<br>}}<nowiki> </nowiki...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

... further resultsUnable to interpret the "1550-02-29" input value as valid date or time component with "Month 2 in year 1550 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1551-02-29" input value as valid date or time component with "Month 2 in year 1551 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1553-02-29" input value as valid date or time component with "Month 2 in year 1553 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1554-02-29" input value as valid date or time component with "Month 2 in year 1554 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1555-02-29" input value as valid date or time component with "Month 2 in year 1555 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1557-02-29" input value as valid date or time component with "Month 2 in year 1557 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1558-02-29" input value as valid date or time component with "Month 2 in year 1558 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1559-02-29" input value as valid date or time component with "Month 2 in year 1559 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1561-02-29" input value as valid date or time component with "Month 2 in year 1561 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1562-02-29" input value as valid date or time component with "Month 2 in year 1562 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1563-02-29" input value as valid date or time component with "Month 2 in year 1563 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1565-02-29" input value as valid date or time component with "Month 2 in year 1565 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1566-02-29" input value as valid date or time component with "Month 2 in year 1566 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1567-02-29" input value as valid date or time component with "Month 2 in year 1567 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1569-02-29" input value as valid date or time component with "Month 2 in year 1569 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1570-02-29" input value as valid date or time component with "Month 2 in year 1570 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1571-02-29" input value as valid date or time component with "Month 2 in year 1571 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1573-02-29" input value as valid date or time component with "Month 2 in year 1573 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1574-02-29" input value as valid date or time component with "Month 2 in year 1574 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1575-02-29" input value as valid date or time component with "Month 2 in year 1575 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1577-02-29" input value as valid date or time component with "Month 2 in year 1577 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1578-02-29" input value as valid date or time component with "Month 2 in year 1578 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1579-02-29" input value as valid date or time component with "Month 2 in year 1579 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1581-02-29" input value as valid date or time component with "Month 2 in year 1581 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1582-02-29" input value as valid date or time component with "Month 2 in year 1582 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1583-02-29" input value as valid date or time component with "Month 2 in year 1583 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1585-02-29" input value as valid date or time component with "Month 2 in year 1585 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1586-02-29" input value as valid date or time component with "Month 2 in year 1586 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1587-02-29" input value as valid date or time component with "Month 2 in year 1587 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1589-02-29" input value as valid date or time component with "Month 2 in year 1589 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1590-02-29" input value as valid date or time component with "Month 2 in year 1590 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1591-02-29" input value as valid date or time component with "Month 2 in year 1591 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1593-02-29" input value as valid date or time component with "Month 2 in year 1593 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1594-02-29" input value as valid date or time component with "Month 2 in year 1594 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1595-02-29" input value as valid date or time component with "Month 2 in year 1595 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1597-02-29" input value as valid date or time component with "Month 2 in year 1597 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1598-02-29" input value as valid date or time component with "Month 2 in year 1598 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1599-02-29" input value as valid date or time component with "Month 2 in year 1599 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1601-02-29" input value as valid date or time component with "Month 2 in year 1601 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1602-02-29" input value as valid date or time component with "Month 2 in year 1602 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1603-02-29" input value as valid date or time component with "Month 2 in year 1603 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1605-02-29" input value as valid date or time component with "Month 2 in year 1605 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1606-02-29" input value as valid date or time component with "Month 2 in year 1606 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1607-02-29" input value as valid date or time component with "Month 2 in year 1607 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1609-02-29" input value as valid date or time component with "Month 2 in year 1609 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1610-02-29" input value as valid date or time component with "Month 2 in year 1610 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1611-02-29" input value as valid date or time component with "Month 2 in year 1611 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1613-02-29" input value as valid date or time component with "Month 2 in year 1613 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1614-02-29" input value as valid date or time component with "Month 2 in year 1614 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1615-02-29" input value as valid date or time component with "Month 2 in year 1615 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1617-02-29" input value as valid date or time component with "Month 2 in year 1617 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1618-02-29" input value as valid date or time component with "Month 2 in year 1618 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1619-02-29" input value as valid date or time component with "Month 2 in year 1619 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1621-02-29" input value as valid date or time component with "Month 2 in year 1621 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1622-02-29" input value as valid date or time component with "Month 2 in year 1622 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1623-02-29" input value as valid date or time component with "Month 2 in year 1623 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1625-02-29" input value as valid date or time component with "Month 2 in year 1625 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1626-02-29" input value as valid date or time component with "Month 2 in year 1626 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1627-02-29" input value as valid date or time component with "Month 2 in year 1627 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1629-02-29" input value as valid date or time component with "Month 2 in year 1629 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1630-02-29" input value as valid date or time component with "Month 2 in year 1630 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1631-02-29" input value as valid date or time component with "Month 2 in year 1631 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1633-02-29" input value as valid date or time component with "Month 2 in year 1633 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1634-02-29" input value as valid date or time component with "Month 2 in year 1634 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1635-02-29" input value as valid date or time component with "Month 2 in year 1635 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1637-02-29" input value as valid date or time component with "Month 2 in year 1637 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1638-02-29" input value as valid date or time component with "Month 2 in year 1638 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1639-02-29" input value as valid date or time component with "Month 2 in year 1639 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1641-02-29" input value as valid date or time component with "Month 2 in year 1641 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1642-02-29" input value as valid date or time component with "Month 2 in year 1642 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1643-02-29" input value as valid date or time component with "Month 2 in year 1643 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1645-02-29" input value as valid date or time component with "Month 2 in year 1645 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1646-02-29" input value as valid date or time component with "Month 2 in year 1646 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1647-02-29" input value as valid date or time component with "Month 2 in year 1647 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1649-02-29" input value as valid date or time component with "Month 2 in year 1649 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1650-02-29" input value as valid date or time component with "Month 2 in year 1650 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1651-02-29" input value as valid date or time component with "Month 2 in year 1651 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1653-02-29" input value as valid date or time component with "Month 2 in year 1653 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1654-02-29" input value as valid date or time component with "Month 2 in year 1654 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1655-02-29" input value as valid date or time component with "Month 2 in year 1655 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1657-02-29" input value as valid date or time component with "Month 2 in year 1657 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1658-02-29" input value as valid date or time component with "Month 2 in year 1658 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1659-02-29" input value as valid date or time component with "Month 2 in year 1659 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1661-02-29" input value as valid date or time component with "Month 2 in year 1661 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1662-02-29" input value as valid date or time component with "Month 2 in year 1662 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1663-02-29" input value as valid date or time component with "Month 2 in year 1663 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1665-02-29" input value as valid date or time component with "Month 2 in year 1665 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1666-02-29" input value as valid date or time component with "Month 2 in year 1666 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1667-02-29" input value as valid date or time component with "Month 2 in year 1667 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1669-02-29" input value as valid date or time component with "Month 2 in year 1669 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1670-02-29" input value as valid date or time component with "Month 2 in year 1670 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1671-02-29" input value as valid date or time component with "Month 2 in year 1671 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1673-02-29" input value as valid date or time component with "Month 2 in year 1673 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1674-02-29" input value as valid date or time component with "Month 2 in year 1674 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1675-02-29" input value as valid date or time component with "Month 2 in year 1675 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1677-02-29" input value as valid date or time component with "Month 2 in year 1677 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1678-02-29" input value as valid date or time component with "Month 2 in year 1678 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1679-02-29" input value as valid date or time component with "Month 2 in year 1679 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1681-02-29" input value as valid date or time component with "Month 2 in year 1681 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1682-02-29" input value as valid date or time component with "Month 2 in year 1682 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1683-02-29" input value as valid date or time component with "Month 2 in year 1683 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1685-02-29" input value as valid date or time component with "Month 2 in year 1685 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1686-02-29" input value as valid date or time component with "Month 2 in year 1686 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1687-02-29" input value as valid date or time component with "Month 2 in year 1687 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1689-02-29" input value as valid date or time component with "Month 2 in year 1689 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1690-02-29" input value as valid date or time component with "Month 2 in year 1690 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1691-02-29" input value as valid date or time component with "Month 2 in year 1691 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1693-02-29" input value as valid date or time component with "Month 2 in year 1693 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1694-02-29" input value as valid date or time component with "Month 2 in year 1694 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1695-02-29" input value as valid date or time component with "Month 2 in year 1695 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1697-02-29" input value as valid date or time component with "Month 2 in year 1697 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1698-02-29" input value as valid date or time component with "Month 2 in year 1698 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1699-02-29" input value as valid date or time component with "Month 2 in year 1699 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1700-02-29" input value as valid date or time component with "Month 2 in year 1700 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1701-02-29" input value as valid date or time component with "Month 2 in year 1701 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1702-02-29" input value as valid date or time component with "Month 2 in year 1702 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1703-02-29" input value as valid date or time component with "Month 2 in year 1703 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1705-02-29" input value as valid date or time component with "Month 2 in year 1705 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1706-02-29" input value as valid date or time component with "Month 2 in year 1706 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1707-02-29" input value as valid date or time component with "Month 2 in year 1707 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1709-02-29" input value as valid date or time component with "Month 2 in year 1709 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1710-02-29" input value as valid date or time component with "Month 2 in year 1710 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1711-02-29" input value as valid date or time component with "Month 2 in year 1711 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1713-02-29" input value as valid date or time component with "Month 2 in year 1713 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1714-02-29" input value as valid date or time component with "Month 2 in year 1714 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1715-02-29" input value as valid date or time component with "Month 2 in year 1715 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1717-02-29" input value as valid date or time component with "Month 2 in year 1717 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1718-02-29" input value as valid date or time component with "Month 2 in year 1718 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1719-02-29" input value as valid date or time component with "Month 2 in year 1719 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1721-02-29" input value as valid date or time component with "Month 2 in year 1721 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1722-02-29" input value as valid date or time component with "Month 2 in year 1722 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1723-02-29" input value as valid date or time component with "Month 2 in year 1723 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1725-02-29" input value as valid date or time component with "Month 2 in year 1725 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1726-02-29" input value as valid date or time component with "Month 2 in year 1726 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1727-02-29" input value as valid date or time component with "Month 2 in year 1727 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1729-02-29" input value as valid date or time component with "Month 2 in year 1729 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1730-02-29" input value as valid date or time component with "Month 2 in year 1730 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1731-02-29" input value as valid date or time component with "Month 2 in year 1731 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1733-02-29" input value as valid date or time component with "Month 2 in year 1733 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1734-02-29" input value as valid date or time component with "Month 2 in year 1734 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1735-02-29" input value as valid date or time component with "Month 2 in year 1735 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1737-02-29" input value as valid date or time component with "Month 2 in year 1737 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1738-02-29" input value as valid date or time component with "Month 2 in year 1738 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1739-02-29" input value as valid date or time component with "Month 2 in year 1739 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1741-02-29" input value as valid date or time component with "Month 2 in year 1741 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1742-02-29" input value as valid date or time component with "Month 2 in year 1742 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1743-02-29" input value as valid date or time component with "Month 2 in year 1743 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1745-02-29" input value as valid date or time component with "Month 2 in year 1745 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1746-02-29" input value as valid date or time component with "Month 2 in year 1746 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1747-02-29" input value as valid date or time component with "Month 2 in year 1747 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1749-02-29" input value as valid date or time component with "Month 2 in year 1749 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1750-02-29" input value as valid date or time component with "Month 2 in year 1750 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1751-02-29" input value as valid date or time component with "Month 2 in year 1751 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1753-02-29" input value as valid date or time component with "Month 2 in year 1753 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1754-02-29" input value as valid date or time component with "Month 2 in year 1754 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1755-02-29" input value as valid date or time component with "Month 2 in year 1755 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1757-02-29" input value as valid date or time component with "Month 2 in year 1757 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1758-02-29" input value as valid date or time component with "Month 2 in year 1758 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1759-02-29" input value as valid date or time component with "Month 2 in year 1759 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1761-02-29" input value as valid date or time component with "Month 2 in year 1761 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1762-02-29" input value as valid date or time component with "Month 2 in year 1762 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1763-02-29" input value as valid date or time component with "Month 2 in year 1763 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1765-02-29" input value as valid date or time component with "Month 2 in year 1765 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1766-02-29" input value as valid date or time component with "Month 2 in year 1766 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1767-02-29" input value as valid date or time component with "Month 2 in year 1767 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1769-02-29" input value as valid date or time component with "Month 2 in year 1769 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1770-02-29" input value as valid date or time component with "Month 2 in year 1770 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1771-02-29" input value as valid date or time component with "Month 2 in year 1771 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1773-02-29" input value as valid date or time component with "Month 2 in year 1773 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1774-02-29" input value as valid date or time component with "Month 2 in year 1774 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1775-02-29" input value as valid date or time component with "Month 2 in year 1775 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1777-02-29" input value as valid date or time component with "Month 2 in year 1777 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1778-02-29" input value as valid date or time component with "Month 2 in year 1778 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1779-02-29" input value as valid date or time component with "Month 2 in year 1779 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1781-02-29" input value as valid date or time component with "Month 2 in year 1781 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1782-02-29" input value as valid date or time component with "Month 2 in year 1782 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1783-02-29" input value as valid date or time component with "Month 2 in year 1783 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1785-02-29" input value as valid date or time component with "Month 2 in year 1785 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1786-02-29" input value as valid date or time component with "Month 2 in year 1786 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1787-02-29" input value as valid date or time component with "Month 2 in year 1787 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1789-02-29" input value as valid date or time component with "Month 2 in year 1789 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1790-02-29" input value as valid date or time component with "Month 2 in year 1790 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1791-02-29" input value as valid date or time component with "Month 2 in year 1791 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1793-02-29" input value as valid date or time component with "Month 2 in year 1793 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1794-02-29" input value as valid date or time component with "Month 2 in year 1794 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1795-02-29" input value as valid date or time component with "Month 2 in year 1795 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1797-02-29" input value as valid date or time component with "Month 2 in year 1797 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1798-02-29" input value as valid date or time component with "Month 2 in year 1798 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1799-02-29" input value as valid date or time component with "Month 2 in year 1799 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1800-02-29" input value as valid date or time component with "Month 2 in year 1800 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1801-02-29" input value as valid date or time component with "Month 2 in year 1801 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1802-02-29" input value as valid date or time component with "Month 2 in year 1802 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1803-02-29" input value as valid date or time component with "Month 2 in year 1803 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1805-02-29" input value as valid date or time component with "Month 2 in year 1805 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1806-02-29" input value as valid date or time component with "Month 2 in year 1806 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1807-02-29" input value as valid date or time component with "Month 2 in year 1807 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1809-02-29" input value as valid date or time component with "Month 2 in year 1809 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1810-02-29" input value as valid date or time component with "Month 2 in year 1810 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1811-02-29" input value as valid date or time component with "Month 2 in year 1811 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1813-02-29" input value as valid date or time component with "Month 2 in year 1813 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1814-02-29" input value as valid date or time component with "Month 2 in year 1814 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1815-02-29" input value as valid date or time component with "Month 2 in year 1815 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1817-02-29" input value as valid date or time component with "Month 2 in year 1817 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1818-02-29" input value as valid date or time component with "Month 2 in year 1818 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1819-02-29" input value as valid date or time component with "Month 2 in year 1819 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1821-02-29" input value as valid date or time component with "Month 2 in year 1821 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1822-02-29" input value as valid date or time component with "Month 2 in year 1822 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1823-02-29" input value as valid date or time component with "Month 2 in year 1823 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1825-02-29" input value as valid date or time component with "Month 2 in year 1825 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1826-02-29" input value as valid date or time component with "Month 2 in year 1826 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1827-02-29" input value as valid date or time component with "Month 2 in year 1827 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1829-02-29" input value as valid date or time component with "Month 2 in year 1829 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1830-02-29" input value as valid date or time component with "Month 2 in year 1830 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1831-02-29" input value as valid date or time component with "Month 2 in year 1831 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1833-02-29" input value as valid date or time component with "Month 2 in year 1833 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1834-02-29" input value as valid date or time component with "Month 2 in year 1834 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1835-02-29" input value as valid date or time component with "Month 2 in year 1835 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1837-02-29" input value as valid date or time component with "Month 2 in year 1837 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1838-02-29" input value as valid date or time component with "Month 2 in year 1838 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1839-02-29" input value as valid date or time component with "Month 2 in year 1839 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1841-02-29" input value as valid date or time component with "Month 2 in year 1841 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1842-02-29" input value as valid date or time component with "Month 2 in year 1842 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1843-02-29" input value as valid date or time component with "Month 2 in year 1843 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1845-02-29" input value as valid date or time component with "Month 2 in year 1845 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1846-02-29" input value as valid date or time component with "Month 2 in year 1846 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1847-02-29" input value as valid date or time component with "Month 2 in year 1847 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1849-02-29" input value as valid date or time component with "Month 2 in year 1849 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1850-02-29" input value as valid date or time component with "Month 2 in year 1850 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1851-02-29" input value as valid date or time component with "Month 2 in year 1851 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1853-02-29" input value as valid date or time component with "Month 2 in year 1853 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1854-02-29" input value as valid date or time component with "Month 2 in year 1854 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1855-02-29" input value as valid date or time component with "Month 2 in year 1855 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1857-02-29" input value as valid date or time component with "Month 2 in year 1857 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1858-02-29" input value as valid date or time component with "Month 2 in year 1858 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1859-02-29" input value as valid date or time component with "Month 2 in year 1859 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1861-02-29" input value as valid date or time component with "Month 2 in year 1861 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1862-02-29" input value as valid date or time component with "Month 2 in year 1862 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1863-02-29" input value as valid date or time component with "Month 2 in year 1863 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1865-02-29" input value as valid date or time component with "Month 2 in year 1865 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1866-02-29" input value as valid date or time component with "Month 2 in year 1866 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1867-02-29" input value as valid date or time component with "Month 2 in year 1867 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1869-02-29" input value as valid date or time component with "Month 2 in year 1869 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1870-02-29" input value as valid date or time component with "Month 2 in year 1870 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1871-02-29" input value as valid date or time component with "Month 2 in year 1871 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1873-02-29" input value as valid date or time component with "Month 2 in year 1873 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1874-02-29" input value as valid date or time component with "Month 2 in year 1874 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1875-02-29" input value as valid date or time component with "Month 2 in year 1875 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1877-02-29" input value as valid date or time component with "Month 2 in year 1877 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1878-02-29" input value as valid date or time component with "Month 2 in year 1878 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1879-02-29" input value as valid date or time component with "Month 2 in year 1879 did not have 29 days in this calendar model." being reported.

... further resultsUnable to interpret the "1881-02-29" input value as valid date or time component with "Month 2 in year 1881 did not have 29 days in this calendar model." being reported. [[:#ask: 1882-02-29Unable to interpret the "1882-02-29" input value as valid date or time component with "Month 2 in year 1882 did not have 29 days in this calendar model." being reported.]] [[:#ask: 1883-02-29Unable to interpret the "1883-02-29" input value as valid date or time component with "Month 2 in year 1883 did not have 29 days in this calendar model." being reported.]] [[:#ask: 1885-02-29Unable to interpret the "1885-02-29" input value as valid date or time component with "Month 2 in year 1885 did not have 29 days in this calendar model." being reported.]] [[:#ask: 1886-02-29Unable to interpret the "1886-02-29" input value as valid date or time component with "Month 2 in year 1886 did not have 29 days in this calendar model." being reported.]] [[:#ask: 1887-02-29Unable to interpret the "1887-02-29" input value as valid date or time component with "Month 2 in year 1887 did not have 29 days in this calendar model." being reported.]] [[:#ask: 1889-02-29Unable to interpret the "1889-02-29" input value as valid date or time component with "Month 2 in year 1889 did not have 29 days in this calendar model." being reported.]] [[:#ask: 1890-02-29Unable to interpret the "1890-02-29" input value as valid date or time component with "Month 2 in year 1890 did not have 29 days in this calendar model." being reported.]] [[:#ask: 1891-02-29Unable to interpret the "1891-02-29" input value as valid date or time component with "Month 2 in year 1891 did not have 29 days in this calendar model." being reported.]] [[:#ask: 1893-02-29Unable to interpret the "1893-02-29" input value as valid date or time component with "Month 2 in year 1893 did not have 29 days in this calendar model." being reported.]] [[:#ask: 1894-02-29Unable to interpret the "1894-02-29" input value as valid date or time component with "Month 2 in year 1894 did not have 29 days in this calendar model." being reported.]] [[:#ask: 1895-02-29Unable to interpret the "1895-02-29" input value as valid date or time component with "Month 2 in year 1895 did not have 29 days in this calendar model." being reported.]] [[:#ask: 1897-02-29Unable to interpret the "1897-02-29" input value as valid date or time component with "Month 2 in year 1897 did not have 29 days in this calendar model." being reported.]] [[:#ask: 1898-02-29Unable to interpret the "1898-02-29" input value as valid date or time component with "Month 2 in year 1898 did not have 29 days in this calendar model." being reported.]] [[:#ask: 1899-02-29Unable to interpret the "1899-02-29" input value as valid date or time component with "Month 2 in year 1899 did not have 29 days in this calendar model." being reported.]]

Retrieved from "https://gate.unigre.it/mediawiki/index.php?title=Written_today/02-29&oldid=78264"
Powered by MediaWiki
Powered by Semantic MediaWiki