Brainstorm

• So far, it seems like a good idea to keep the library in strict ANSI C to facilitate easily binding it to other languages such as PHP and Python for web developers, or inclusion into other projects such as any of the front ends for the Sword project.  Using C++ is another possibility if the bulk of developers begin to show strong preference for it instead.
• On the Wishlist page, there is a comment about using the library to do basic calculations and conversions between differing calendars.  This would obviously be most easily accomplished by using a common calendar or number of some sort as an in-between to convert to and from for each calendar type (use an int?).
• Avoid outputting English language strings as much as possible.  The library should not be telling people what language to display their calendar in.