NavList:
A Community Devoted to the Preservation and Practice of Celestial Navigation and Other Methods of Traditional Wayfinding
From: Simon Horwith
Date: 2021 Jan 29, 14:32 -0500
Hi Tony, you wrote:
"I tried to enter the date in Russian, and as expected, the parser failed."
Please try now. Does "1 фев 1999" (random date) produce the expected result? And "25 декабрь 2035"? I had intended to add Russian months. Then shelved the idea due to lack of interest. But it was easy. It took me less time to change the code than it has taken to compose this email."I would not remind you about Chinese and|or Hindu, etc..."
And Arabic! But how dare you minimize the 800+ languages of Papua New Guinea by referring to them as "etc"! ;) That's like referring to the "Professor and Maryann" as "and the rest" (review some important scholarship on this topic).You added:
"The people behind ISO-8601 are really clever"
No, they're not. :)
"they propose the one and only logical way of the date representation. After all - you do not write an amount of money starting with the pennies, you start with millions, then - you write thousands, then - hundreds, ans so on, the same SHOULD apply to the date: years, then months, then..."
Ha ha ha haaa.... [wait, have to catch my breath]... AAaaa ha ha ha haa! That's genuinely hilarious. I'm sorry, but hyper-nerds like the people who draft these goofy ISO documents sometimes act like they live in an alternate reality.I don't see any reason to add this ISO standard. If you prefer a numerical date then the format "25-12-2021" will work just fine, and "25-12", too.
Frank Reed
Clockwork Mapping / ReedNavigation.com
Conanicut Island USA