#4 case sensitivity in getoptXXX()

[Robert Simms]

getoptint() and getoptstr() are case sensitive in their
matching of option names with what users have entered in
their User options file or through other config files.

Some have uppercasing (ReportCodeset) and some don't
(codeset).

It would take a burden off of the user to allow these option
names to be case-insensitive.

So my guess would be to wrap a lowercasing function
around the two strings being compared in these getoptXXX()
functions.

The only caveat is to anyone who might use characters from
outside basic ASCII for user option names.

[Anonymous]

Logged In: YES
user_id=60964

Actually the option values are stored in a table, so they
need to be decased (to whatever) before being stored in the
table.