MONTHS

THIS PAGE PUBLISHES NO EXAMPLES AND ALMOST NO SEMANTICS, AND THIS FILE SAYS SO RATHER THAN INVENTING THEM. MONTHS's entire entry is: "Calculates the difference in months between two dates", a Syntax block, "StartDate is the first date", "EndDate is the second date", and "Type calculates the type of difference. Possible values include 0 (interval) and 1 (in calendar months)." There is no Example section, no statement of sign convention for reversed dates, and no statement of what happens for any Type other than 0 or 1 -- note the page's own hedge, 'possible values INCLUDE'. Nothing is asserted about any of those. What IS asserted is the two parenthetical glosses, on a date pair chosen so that the two readings give DIFFERENT answers and the case can therefore tell them apart. Under 'in calendar months' the difference is between the months themselves, January to March = 2, regardless of the day-of-month. STORAGE FORM, ESTABLISHED EMPIRICALLY IN BOTH DIRECTIONS BEFORE THIS FILE WAS RUN. A LibreOffice-only function has no OOXML name of its own -- the .xlsx format was frozen on Excel's function set -- so LibreOffice invents one, and this harness must write exactly the token LibreOffice's own .xlsx filter reads. Both directions were measured rather than assumed. IMPORT: every candidate spelling was written into a workbook by openpyxl (which caches no value, so the engine must evaluate from scratch) and round-tripped through `soffice --headless --convert-to xlsx` on all four pinned builds. EXPORT: the same formulas were fed to each build through its own formula parser and written back out to .xlsx, and the stored token was read out of the raw sheet XML. The token recorded for this function in harness/xlfn_map.py is the one both directions agree on across all four builds; the per-function note above says which it is. BATCH PROVENANCE (batch I, group C -- LibreOffice-only functions). This function has x == false AND g == false in docs/data/compat.json: NEITHER Microsoft NOR Google documents it, so this corpus makes no claim about either of those engines, nothing here is measured against their documentation, and the Excel column on the published page reads 'n/a (not an Excel function)' rather than a verdict. The authority is LibreOffice's own help, cited by full URL, by the date it was read (2026-08-31), and by the help version the page serves -- the URLs in this file are pinned to /25.8/ rather than /latest/ so the citation still means this text after the help site rolls forward, and /25.8/ is the help for the newest of the four engine builds the corpus executes. GOOGLE SHEETS: this batch builds the Sheets chunk whose ingest will record presence or absence in that engine. Until that ingest lands, the Sheets column on the published page reads 'Not yet' and nothing in this file claims anything about it. (Stated positively on purpose. scripts/check_honesty.py bans the blanket negative shape of this sentence outright -- it was once a true site-wide claim and is now false for more than 500 functions -- and that guard is worth keeping blunt, so this note carries the same per-function fact in a form the guard does not have to make an exception for.) LibreOffice's MONTHS help page, read live on 2026-08-31 at https://help.libreoffice.org/25.8/en-US/text/scalc/01/04060111.html.

DERIVED from the other gloss, 'interval', on the identical arguments: an interval counts whole elapsed months, and from 31 January only one whole month has elapsed by 1 March (the second would complete on 31 March). This is the case that separates the two Types; if both returned 2 the Type argument would be doing nothing. LibreOffice's MONTHS help page, read live on 2026-08-31 at https://help.libreoffice.org/25.8/en-US/text/scalc/01/04060111.html.

DERIVED from either gloss: a full year from the 15th to the 15th is twelve whole elapsed months and also twelve calendar months. A case where the two readings coincide is the control for the pair above -- it fixes the SCALE of the answer (months, not days or years) independently of the Type semantics. LibreOffice's MONTHS help page, read live on 2026-08-31 at https://help.libreoffice.org/25.8/en-US/text/scalc/01/04060111.html.

THIS PAGE PUBLISHES NO EXAMPLES AND ALMOST NO SEMANTICS, AND THIS FILE SAYS SO RATHER THAN INVENTING THEM. MONTHS's entire entry is: "Calculates the difference in months between two dates", a Syntax block, "StartDate is the first date", "EndDate is the second date", and "Type calculates the type of difference. Possible values include 0 (interval) and 1 (in calendar months)." There is no Example section, no statement of sign convention for reversed dates, and no statement of what happens for any Type other than 0 or 1 -- note the page's own hedge, 'possible values INCLUDE'. Nothing is asserted about any of those. What IS asserted is the two parenthetical glosses, on a date pair chosen so that the two readings give DIFFERENT answers and the case can therefore tell them apart. Under 'in calendar months' the difference is between the months themselves, January to March = 2, regardless of the day-of-month. STORAGE FORM, ESTABLISHED EMPIRICALLY IN BOTH DIRECTIONS BEFORE THIS FILE WAS RUN. A LibreOffice-only function has no OOXML name of its own -- the .xlsx format was frozen on Excel's function set -- so LibreOffice invents one, and this harness must write exactly the token LibreOffice's own .xlsx filter reads. Both directions were measured rather than assumed. IMPORT: every candidate spelling was written into a workbook by openpyxl (which caches no value, so the engine must evaluate from scratch) and round-tripped through `soffice --headless --convert-to xlsx` on all four pinned builds. EXPORT: the same formulas were fed to each build through its own formula parser and written back out to .xlsx, and the stored token was read out of the raw sheet XML. The token recorded for this function in harness/xlfn_map.py is the one both directions agree on across all four builds; the per-function note above says which it is. BATCH PROVENANCE (batch I, group C -- LibreOffice-only functions). This function has x == false AND g == false in docs/data/compat.json: NEITHER Microsoft NOR Google documents it, so this corpus makes no claim about either of those engines, nothing here is measured against their documentation, and the Excel column on the published page reads 'n/a (not an Excel function)' rather than a verdict. The authority is LibreOffice's own help, cited by full URL, by the date it was read (2026-08-31), and by the help version the page serves -- the URLs in this file are pinned to /25.8/ rather than /latest/ so the citation still means this text after the help site rolls forward, and /25.8/ is the help for the newest of the four engine builds the corpus executes. GOOGLE SHEETS: this batch builds the Sheets chunk whose ingest will record presence or absence in that engine. Until that ingest lands, the Sheets column on the published page reads 'Not yet' and nothing in this file claims anything about it. (Stated positively on purpose. scripts/check_honesty.py bans the blanket negative shape of this sentence outright -- it was once a true site-wide claim and is now false for more than 500 functions -- and that guard is worth keeping blunt, so this note carries the same per-function fact in a form the guard does not have to make an exception for.) LibreOffice's MONTHS help page, read live on 2026-08-31 at https://help.libreoffice.org/25.8/en-US/text/scalc/01/04060111.html.

DERIVED from the other gloss, 'interval', on the identical arguments: an interval counts whole elapsed months, and from 31 January only one whole month has elapsed by 1 March (the second would complete on 31 March). This is the case that separates the two Types; if both returned 2 the Type argument would be doing nothing. LibreOffice's MONTHS help page, read live on 2026-08-31 at https://help.libreoffice.org/25.8/en-US/text/scalc/01/04060111.html.

DERIVED from either gloss: a full year from the 15th to the 15th is twelve whole elapsed months and also twelve calendar months. A case where the two readings coincide is the control for the pair above -- it fixes the SCALE of the answer (months, not days or years) independently of the Type semantics. LibreOffice's MONTHS help page, read live on 2026-08-31 at https://help.libreoffice.org/25.8/en-US/text/scalc/01/04060111.html.

THIS PAGE PUBLISHES NO EXAMPLES AND ALMOST NO SEMANTICS, AND THIS FILE SAYS SO RATHER THAN INVENTING THEM. MONTHS's entire entry is: "Calculates the difference in months between two dates", a Syntax block, "StartDate is the first date", "EndDate is the second date", and "Type calculates the type of difference. Possible values include 0 (interval) and 1 (in calendar months)." There is no Example section, no statement of sign convention for reversed dates, and no statement of what happens for any Type other than 0 or 1 -- note the page's own hedge, 'possible values INCLUDE'. Nothing is asserted about any of those. What IS asserted is the two parenthetical glosses, on a date pair chosen so that the two readings give DIFFERENT answers and the case can therefore tell them apart. Under 'in calendar months' the difference is between the months themselves, January to March = 2, regardless of the day-of-month. STORAGE FORM, ESTABLISHED EMPIRICALLY IN BOTH DIRECTIONS BEFORE THIS FILE WAS RUN. A LibreOffice-only function has no OOXML name of its own -- the .xlsx format was frozen on Excel's function set -- so LibreOffice invents one, and this harness must write exactly the token LibreOffice's own .xlsx filter reads. Both directions were measured rather than assumed. IMPORT: every candidate spelling was written into a workbook by openpyxl (which caches no value, so the engine must evaluate from scratch) and round-tripped through `soffice --headless --convert-to xlsx` on all four pinned builds. EXPORT: the same formulas were fed to each build through its own formula parser and written back out to .xlsx, and the stored token was read out of the raw sheet XML. The token recorded for this function in harness/xlfn_map.py is the one both directions agree on across all four builds; the per-function note above says which it is. BATCH PROVENANCE (batch I, group C -- LibreOffice-only functions). This function has x == false AND g == false in docs/data/compat.json: NEITHER Microsoft NOR Google documents it, so this corpus makes no claim about either of those engines, nothing here is measured against their documentation, and the Excel column on the published page reads 'n/a (not an Excel function)' rather than a verdict. The authority is LibreOffice's own help, cited by full URL, by the date it was read (2026-08-31), and by the help version the page serves -- the URLs in this file are pinned to /25.8/ rather than /latest/ so the citation still means this text after the help site rolls forward, and /25.8/ is the help for the newest of the four engine builds the corpus executes. GOOGLE SHEETS: this batch builds the Sheets chunk whose ingest will record presence or absence in that engine. Until that ingest lands, the Sheets column on the published page reads 'Not yet' and nothing in this file claims anything about it. (Stated positively on purpose. scripts/check_honesty.py bans the blanket negative shape of this sentence outright -- it was once a true site-wide claim and is now false for more than 500 functions -- and that guard is worth keeping blunt, so this note carries the same per-function fact in a form the guard does not have to make an exception for.) LibreOffice's MONTHS help page, read live on 2026-08-31 at https://help.libreoffice.org/25.8/en-US/text/scalc/01/04060111.html.

DERIVED from the other gloss, 'interval', on the identical arguments: an interval counts whole elapsed months, and from 31 January only one whole month has elapsed by 1 March (the second would complete on 31 March). This is the case that separates the two Types; if both returned 2 the Type argument would be doing nothing. LibreOffice's MONTHS help page, read live on 2026-08-31 at https://help.libreoffice.org/25.8/en-US/text/scalc/01/04060111.html.

DERIVED from either gloss: a full year from the 15th to the 15th is twelve whole elapsed months and also twelve calendar months. A case where the two readings coincide is the control for the pair above -- it fixes the SCALE of the answer (months, not days or years) independently of the Type semantics. LibreOffice's MONTHS help page, read live on 2026-08-31 at https://help.libreoffice.org/25.8/en-US/text/scalc/01/04060111.html.