Contact

UNICHAR in Collabora Office: Build Unicode Symbols from Explicit Code Numbers

Text Intermediate Collabora Office Calc

Create Unicode labels in Collabora Calc, inspect reproducible BMP symbols and distinguish code numbers from literal digit strings.

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

Quick answer: UNICHAR converts a numeric Unicode code into its character. =UNICHAR(169) has the documented result ©.

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 the scope of a code number

=UNICHAR(Number)

The Collabora reference describes conversion from a code number to a Unicode character or letter. Its explicit example uses decimal code 169 for the copyright symbol.

The input is a number, not a string containing the printed notation “U+00A9.” The familiar U+ notation expresses a hexadecimal code point; the ordinary formula above supplies its decimal value.

The following examples use named characters in Unicode’s Basic Multilingual Plane, avoiding surrogate-pair and supplementary-plane behavior that the short product page does not describe. Font appearance can differ even when the underlying character is the same.

Example 1: construct a small symbol dictionary

Enter only the first numeric column in A2:A7. Put =UNICHAR(A2) in B2 and fill down. The descriptions are explanatory labels.

A, decimal code B, expected character Description
65 A Latin capital A
169 © Copyright sign
176 ° Degree sign
233 é Latin small e with acute
937 Ω Greek capital omega
36554 車 CJK character used in the URL example

These are independently mapped character controls. The displayed © control is also directly reproduced in the Collabora function reference.

A formula returning ° produces a character; it does not convert a numeric angle from radians to degrees. That calculation belongs to DEGREES. A label’s symbol and its quantity should agree, but they are separate operations.

Example 2: assemble an explicit label

Put numeric temperature 23 in D2. For a fixed label control, enter:

="23 "&UNICHAR(176)&"C"

Expected text: 23 °C. The space is a literal ordinary space and the degree sign is generated from its code.

This specific label intentionally supplies the digits as text. It does not establish how every numeric cell is implicitly formatted during concatenation. For an automated measurement report, decide a numeric-to-text formatting policy explicitly rather than relying on cell appearance.

Similarly, =UNICHAR(169)&" Example Studio" gives © Example Studio. The fictional text is an example of character assembly, not a statement about legal ownership or a date.

Advanced example: verify the generated first character

In C2 enter =UNICODE(B2) and fill through C7. Expected numbers are 65, 169, 176, 233, 937 and 36554, matching A2:A7. In D2 enter =A2=C2 and fill down; all six comparisons are expected TRUE.

UNICODE reads the first character of text. That makes it a useful reverse control for these one-character outputs. It does not mean it serializes every character of a longer string automatically.

For instance, =UNICODE(UNICHAR(169)&" report") still yields 169. The appended label does not change the first character.

Advanced example: distinguish a code from printed digits

=UNICHAR(65) yields A, while the literal text 65 consists of the characters 6 and 5. Applying =UNICODE("65") gives 54, the code for the first digit 6.

This distinction matters in imported data. A column of numeric codes needs decoding; a column containing already decoded characters should not be reinterpreted as decimal code values merely because some entries look numeric.

Reproduction limits

The short dedicated page does not give an accepted integer range, fractional truncation rule, invalid-code error table or Unicode normalization policy. This guide does not certify zero, negative values, isolated surrogate codes or supplementary-plane output behavior.

Combining sequences and precomposed characters can look similar while containing different code sequences. Keep the original text when exact identity matters, and do not infer identity from a screenshot alone. These simple one-code-point fixtures avoid that ambiguity while remaining useful for labels and inspection.

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.