Hi, Not sure where you exactly see a bug here. There are quite a number of unit-tests which verify various formats/variations, maybe you can put your case into a unit-test as well? That would make it easier to comment if you should be using some API differently or if there is indeed a bug here.
Thanks... Dominik. On Thu, Apr 5, 2018 at 8:06 PM, Blake Watson <[email protected]> wrote: > This appears to be a bug. I thought maybe it was related to the Windows > locale short-date format, but even that seems to return the century. > > On further testing, EVERY date format seems to return m/d/yy, regardless of > the format string. > > On Wed, Apr 4, 2018 at 4:26 PM, Blake Watson <[email protected]> > wrote: > > > The formatting for Excel...say no more...but I'm having an issue with > > century vs. no century. > > > > If I just use the basic short format in Excel, it includes the century > and > > appears to be: > > > > m/d/yy > > > > Which, when I run the apply function, I get no century. (I can see why I > > wouldn't.) When I take the century out in Excel, the format seems to be: > > > > m/d/yy;@ > > > > Am I missing something or is this a discrepancy? > > > > > > -- > > > > *Blake Watson* > > > > *PNMAC* > > Application Development Manager > > 5898 Condor Drive > > Moorpark, CA 93021 > > (805) 330.4911 x7742 > > [email protected] > > www.PennyMacUSA.com <http://www.pennymacusa.com/> > > > > > > -- > > *Blake Watson* > > *PNMAC* > Application Development Manager > 5898 Condor Drive > Moorpark, CA 93021 > (805) 330.4911 x7742 > [email protected] > www.PennyMacUSA.com <http://www.pennymacusa.com/> >
