I fixed this on DateTime trunk (what will be 3.0.2). A different code path was taken there and it didn't respect the datefmt setting.
I fixed this on DateTime trunk (what will be 3.0.2). A different code path was taken there and it didn't respect the datefmt setting.