On Tue, 25 Mar 2003, Eugene van der Pijll wrote: > Unfortunately, us kalandariophiles are a minority on this list; I > suspect Dave in particular of wanting to use DateTime for all kinds of > worldy, modern, boring stuff.
Well, I'm interested in other calendars as well. My wife's Taiwanese so I've been meaning to get around to working on DateTime::Calendar::Chinese in honor of her ;) > No, DateTime::Language can't know about all the wonderful calendars in > the world. For most calendars (including Ethiopic, I presume) one or > two languages will suffice: one in the local alphabet, and one > transcribed to the Roman alphabet. The latter should then be included > in all language modules... Exactly what I was thinking. We can't expect people who create DateTime::Language::Dutch to also provide Dutch names for the Ethiopic calendar's months. So you're probably stuck with your own little hierarchy of DateTime::Calendar::Ethiopic::Language modules. Whee, 5 levels of namespace! I expect Ethiopic is something of an exception, in that it'll probably require a fair number of language modules. But for something like the Chinese calendar, I'm planning to offer Romanized Mandarin and Unicode Traditional Chinese, and then people can convert from the latter as needed. > (Or move those month names to their own module DT::C::E::Language; but > that's an implementation detail. I would like to have a consistent API > for all calendars, but I don't care about the implementations.) Yes, API consistency inasmuch as it is possible is a good thing. It'll probably take a few different DateTime::Calendar modules before we can figure out exactly what this should look like, though. -dave /*======================= House Absolute Consulting www.houseabsolute.com =======================*/
