| Would you consider adding a new date conversion (maybe "@CONVDATE")
| in which you can specify both an input and an output format? The
| usage would be something like, on a system using format 2 default,
| there is a format 1 input, and you need output in format 4.
If you don't mind a bit more coding, another useful conversion would be for
time, between AM/PM and 24-hour modes, where the AM/PM may be before or
after the TOD, and may but need not have separating whitespace, and the "M"
might be dropped, e.g., "a2:15", "2:15 AM", "02:15P". If no letters in the
parameter, assume 24-hour format for input, and use "hh:mm AM" as output
format. If "a" or "p" is in the parameter, assume AM or PM input,
respectively, and ouput in HH:MM. Note that seconds and even milliseconds
may be in the input, and that the field separator btw. hours and minutes as
well as between minutes and seconds need not be the colon : - e.g. on my
system it might be the period. @TIMECONV sounds like a good name... I have
no objection to separate functions for the two converion directions, but I'd
consider it quite useful in that case if the output format would also be
acceptable as input, so @AMPM_to_24HR would accept 23.25.59 as input and
would return it unchanged. This last feature would make it unnecessary to
know in advance what time format a particular source has, putting it through
the converter would yield the user's standard format.