forked from amazingfate/loongoffice
The remaining cases when loading old and wrong ISOWEEKNUM that can't be mapped to either new WEEKNUM or ISOWEEKNUM now are mapped to WEEKNUM_OOO(date,mode) with calculations identical to the old and wrong OOo WEEKNUM. These WEEKNUM_OOO cases are still wrongly saved as ISOWEEKNUM so can be read by 5.0 or earlier versions as the old WEEKNUM, which should be changed for 5.3 or later. WEEKNUM_OOO is not offered in the Function Wizard to prevent deliberate usage. Also reverts the interim unit test change to sc/qa/unit/data/contentCSV/date-time-functions.csv that was necessary to catch the error generated by ISOWEEKNUM with two arguments. Change-Id: I874c4c7225900f03b879f2947512ae02270cbd4f
247 B
247 B
| 1 | 30347 |
|---|---|
| 2 | 38,1,27,457,13937,57 |
| 3 | 19925 |
| 4 | 30,31,1,21 |
| 5 | 3652 |
| 6 | 5150 |
| 7 | 30,28,29 |
| 8 | 366,365 |
| 9 | 41749 |
| 10 | 36890 |
| 11 | 37346 |
| 12 | 17 |
| 13 | 1,0 |
| 14 | 58,59,45 |
| 15 | 4 |
| 16 | 2,3 |
| 17 | 17 |
| 18 | 15 |
| 19 | .18 |
| 20 | 0,0.6666666667,0.5 |
| 21 | 4,3,4 |
| 22 | 52 |
| 23 | 1,1,52 |
| 24 | 1,52 |
| 25 | 52 |
| 26 | 10,11 |
| 27 | 52,52 |
| 28 | 37253 |
| 29 | 1899,1900,1991 |
| 30 | 0.5,0.4972677596,0.5055555556,0.498630137,0.5 |
| 31 | 1,2 |