Yes, that would be a good change.
The general goal of String conversions was to mimic the type's
toString() and valueOf() methods, but there are some exceptions that are
left over from OFBiz. I tried to remove the OFBiz-specific code when I
ported the code to Commons, but I can see I missed a
HI All:
This is for the string to Boolean converter, but I suppose this applies to
other converters.
Would providing an alternate string for "true" be in the spirit of
[convert]? What about for "false"?
The current converter would be enhanced to support this, the alt strings
would be provided in
