Contact

DECIMAL in Collabora Office: Decode Base-Specific Text and Audit Imported Codes

Text Intermediate Collabora Office Calc

Parse positive numeral strings in Collabora Calc, use documented hexadecimal and binary decorations and avoid confusing code text with decimal arithmetic.

Verification status: See the evidence and test scope described in this guide. How formula examples are checked

Quick answer: DECIMAL interprets text in a specified radix from 2 through 36 and returns its positive numeric quantity. =DECIMAL("3H";36) has independently expected result 125.

Availability and version history

  • Introduced: the original Collabora release and launch date are not established by the reviewed sources.
  • Availability: documented in Collabora Office 26.04 desktop help.
  • Platform scope: online and mobile deployment support is not inferred from the desktop documentation.
  • Checked: October 14, 2026. Function-specific documentation and independent controls; no native Collabora execution.

Syntax and documented text rules

=DECIMAL("Text"; Radix)

Radix is an integer from 2 through 36. The input is not case-sensitive, and the dedicated page says spaces and tabs are ignored.

For radix 16, leading x, X, 0x or 0X and a trailing h or H are disregarded. For radix 2, a trailing b or B is disregarded. Other characters outside the selected numeral system generate an error; the page does not name a universal error code.

The reference describes a positive integer result. Zero, signed strings, fractional syntax and maximum exact values are not established by this page. The controls below use positive quantities with documented decorations.

Example 1: normalize several representations

Format A2:A6 as Text and enter the text column; enter the radices in B2:B6. In C2 use =DECIMAL(A2;B2) and fill down.

A, text B, radix C, expected number
1111101 2 125
175 8 125
125 10 125
7D 16 125
3H 36 125

The digits have different place values. Octal 175 is 1×64+7×8+5. Base-36 3H is 3×36+17. Both equal 125, but treating the visible strings as ordinary decimal data would not preserve that meaning.

The original text and radix together form the input record. A string without its radix can be ambiguous: 10 means ten in radix 10, sixteen in radix 16 and two in radix 2.

Example 2: use documented prefix and suffix conventions

Formula Expected number
=DECIMAL("0x7D";16) 125
=DECIMAL("x7d";16) 125
=DECIMAL("7Dh";16) 125
=DECIMAL("1111101B";2) 125
=DECIMAL(" 7 D ";16) 125

The final row follows the stated ignored-space rule. It is a parsing convenience, not a promise that every external identifier specification permits internal spaces.

The decorations depend on the radix. Do not strip all trailing letters indiscriminately: in base 36, H is the digit seventeen rather than a hexadecimal marker.

Advanced example: separate structural validity from a valid number

A fictional two-character base-36 field contains 3H. Its quantity is 125. The longer string 03H also decodes to 125, so numeric equality cannot enforce the original two-character field width.

Use a separate length or structure check if the file contract requires exactly two characters. LEN can inspect the text length, while DECIMAL answers the numeric interpretation question.

Similarly, G is invalid in radix 16 but a valid digit sixteen in radix 36. =DECIMAL("1G";36) has independently expected result 52; =DECIMAL("1G";16) is a documented invalid-character case, with its exact native error code left unassigned.

Advanced example: calculate on decoded quantities

Enter hexadecimal strings 2D and 31 in E2:E3. Their decimal quantities are 45 and 49. Compute:

=DECIMAL(E2;16)+DECIMAL(E3;16)

Expected sum: 94. To display that total in hexadecimal, use =BASE(DECIMAL(E2;16)+DECIMAL(E3;16);16;2), giving 5E.

BASE reconstructs a chosen positive representation. Neither function restores arbitrary original letter case, prefixes or leading zeros unless your output rules supply them.

Signed notation and verification limits

A short hexadecimal FF is positive 255 under this positional model. This guide does not assign a two’s-complement negative meaning to a long string just because a specialized HEX2DEC converter uses a signed-width contract.

Keep these contracts distinct. General coercion, invalid radix errors, precision boundaries and negative input handling remain unverified. The examples are independent positional calculations based on the product’s explicit radix and text rules, not native application captures.

References and verification

Complete dedicated product documentation reviewed. Outputs are independent decimal, positional, character or type models, or explicit vendor controls; no native Collabora execution. Formulas use English names and semicolon separators. Optional-argument brackets describe syntax and are not typed into working formulas.