diff options
| -rw-r--r-- | svl/source/numbers/zforscan.cxx | 10 |
1 files changed, 4 insertions, 6 deletions
diff --git a/svl/source/numbers/zforscan.cxx b/svl/source/numbers/zforscan.cxx index a59617dd4d23..d0a462e90d85 100644 --- a/svl/source/numbers/zforscan.cxx +++ b/svl/source/numbers/zforscan.cxx @@ -1162,6 +1162,8 @@ sal_Int32 ImpSvNumberformatScan::ScanType() That are the Excel rules. BUT, we break it because certainly in something like {HH YYYY-MM-DD} the MM is NOT meant to be minute, so not if MM is between YY and DD or DD and YY. + Actually not if any date specific keyword followed a time + setting keyword. */ nIndexPre = PreviousKeyword(i); nIndexNex = NextKeyword(i); @@ -1169,12 +1171,7 @@ sal_Int32 ImpSvNumberformatScan::ScanType() nIndexPre == NF_KEY_HH || // HH nIndexNex == NF_KEY_S || // S nIndexNex == NF_KEY_SS || // SS - (bIsTimeDetected && - !(((nIndexPre == NF_KEY_YY || nIndexPre == NF_KEY_YYYY) && - (nIndexNex == NF_KEY_D || nIndexNex == NF_KEY_DD)) || - ((nIndexPre == NF_KEY_D || nIndexPre == NF_KEY_DD) && - (nIndexNex == NF_KEY_YY || nIndexNex == NF_KEY_YYYY))) - ) || // tdf#101147 + bIsTimeDetected || // tdf#101147 PreviousChar(i) == '[' ) // [M { eNewType = css::util::NumberFormat::TIME; @@ -1212,6 +1209,7 @@ sal_Int32 ImpSvNumberformatScan::ScanType() case NF_KEY_R : // R case NF_KEY_RR : // RR eNewType = css::util::NumberFormat::DATE; + bIsTimeDetected = false; break; case NF_KEY_CCC: // CCC eNewType = css::util::NumberFormat::CURRENCY; |