Bug 170437 - Document how LibreOffice treats non-integer values for function parameters, that expect integer values
Summary: Document how LibreOffice treats non-integer values for function parameters, t...
Status: UNCONFIRMED
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Documentation (show other bugs)
Version:
(earliest affected)
26.8.0.0 alpha0+ master
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2026-01-22 16:00 UTC by Regina Henschel
Modified: 2026-01-22 16:00 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Regina Henschel 2026-01-22 16:00:03 UTC 
The ODF standard has in section 'Convert to Integer' (6.3.6 in part 4, ODF 1.4) the sentence,
"If the function or operator does not specify any particular conversion operation, then the conversion from a non-integer Number into an integer is implementation-defined."

"implementation-defined" means, that LibreOffice has to document its behavior.

A specification is missing in https://wiki.documentfoundation.org/Development/ODF_Implementer_Notes/List_of_LibreOffice_ODF_implementation-defined_items#Conversion_to_Integer

I suggest to add a general remark there:
"Non-integer values are truncated to integer. If a function has a special behavior in regard to a parameter, that requires data type Integer, its behavior is described in the online help of that function."

I have not yet collected all functions that expect data type Integer for a parameter. Several financial functions and ADDRESS are affected, for example.

Thus besides the general remark in the Wiki, the task here is to collect the affected functions, and look, whether they behave different than truncating.