IMCONJUGATE Function (Calligra Sheets)

• Introduced: First release not established; the name is present in Calligra 2.4.0 source.
• Supported in: Calligra Sheets 26.08.2, with no retirement established.
• Scope: Desktop Sheets with the Engineering module. Examples use English semicolon-separated formulas.
• Checked: October 14, 2026. Formulas were executed through the official 25.04.2 engine library and checked against source and independent mathematics. This is not GUI-cell or workbook-import evidence; 26.08.2 was source-checked, not executed.

IMCONJUGATE maps a+b·i to a−b·i. It keeps the real component and reverses the imaginary sign. Geometrically this reflects a point across the real axis. The engine returns a complex value, not merely the magnitude or a sign change applied to the whole input. Function help.

=IMCONJUGATE(complexValue)

Exactly one argument is required. Use COMPLEX to build a value from numeric components, or supply a supported complex text value. Real inputs retain their real component and have zero imaginary component. The tested i and j text forms both parsed successfully. Registration and implementation, with versioned help.

Results are shown as (real,imaginary) component pairs, not a literal cell format. Numeric zero is shown as 0 even when the internal component is signed zero.

Put 3 in A2 and 4 in B2. =IMCONJUGATE(COMPLEX(A2;B2)) has components (3,−4). This is different from multiplying the original value by −1, which would produce components (−3,−4). Extract the two components separately when checking a transformation.

The recorded =IMPRODUCT(COMPLEX(3;4);IMCONJUGATE(COMPLEX(3;4))) has components (25,0). Algebraically, (a+bi)(a−bi)=a²+b², so the result is real and equals squared magnitude. Here 9+16=25. This is a useful check for a small finite complex value.

Conjugating twice recovers the original mathematical components. It also preserves magnitude while reversing a non-boundary phase sign. Keep branch-boundary and zero cases separate if phase is used later; a zero imaginary component can carry a signed-zero representation internally.

The engine converted invalid text “abc” and an empty string to zero, then conjugated that zero. TRUE became the real value 1. These successful outputs do not establish that the original text was valid; the shared complex converter’s parse-failure flag is not checked by this wrapper. A missing argument returned #VALUE!.

The help describes a string result, but the inspected engine produces its complex value type. The table’s (real,imaginary) pairs expose those stored components. They do not prescribe the cell’s displayed text, suffix or number format.

The complex conversion helper explains the text and Boolean cases above. The inspected Engineering module and complex converter are byte-identical between 25.04.2 and 26.08.2. That source comparison does not establish every locale, import path or extreme-value case.