ENCODEURL in Collabora Office: Encode Non-ASCII Text for URL Components

• 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.

=ENCODEURL(Text)

Text is the string to encode. Collabora describes the function for accented characters, non-ASCII alphabets and Asian words. The reference demonstrates both Japanese 車 and the Cyrillic word автомобиль.

This guide uses non-ASCII character fixtures whose expected percent encodings can be independently calculated from their UTF-8 bytes. The exact examples in the official page agree with that model. The page does not specify the complete ASCII safe-character set, every reserved punctuation rule or a decoder contract.

Encoding a component does not itself send a request, open a browser or validate a destination. The formulas below only create text.

Enter 車 in A2 and автомобиль in A3. In B2 use =ENCODEURL(A2) and fill through B3.

The first input is a single character represented by three UTF-8 bytes. The Cyrillic input has ten characters and twenty UTF-8 bytes in this control.

Each encoded byte occupies three visible characters: a percent sign and two hexadecimal digits. The expected encoded lengths are therefore 9 and 60, independently checked with the displayed strings. Do not assume one percent triplet always corresponds to one complete Unicode character.

Enter é, Ω and © in D2:D4. Calculate E with =ENCODEURL(D2) filled down.

These expected results follow the same UTF-8 percent-encoding model as the documented examples. They are not new native test observations.

UNICODE identifies the character code, while ENCODEURL produces an encoded byte sequence. The decimal code for é is 233, but its encoded text is not simply %E9 under this UTF-8 model.

Use the reserved example destination below as text only. Put 車 in G2 and enter:

="https://example.invalid/search?q="&ENCODEURL(G2)

Expected text: https://example.invalid/search?q=%E8%BB%8A. The fixed URL structure remains outside the function call; only the parameter value is encoded.

This fixture does not navigate to the address or transmit the text. It shows how a component can be assembled without assuming that encoding an entire URL will preserve its structural punctuation. Follow the receiving system’s parameter specification before using such a formula in a real workflow.

The code number for 車 is decimal 36554, hexadecimal 8ECA. Its UTF-8 bytes are E8, BB and 8A. Hence the URL encoding is %E8%BB%8A, not a percent sign followed by the character’s whole code number.

This difference is useful when inspecting imported multilingual identifiers. UNICHAR constructs a character from its code; it does not directly generate the percent-byte representation.

A visibly similar accented string can have a different underlying sequence, such as a precomposed letter versus a letter followed by a combining mark. The guide does not claim that ENCODEURL normalizes those inputs into identical text.

Collabora identifies this function as COM.MICROSOFT.ENCODEURL, outside the cited OpenFormula 1.3 function standard. That is a documented namespace statement, not proof that an exported formula will execute in every other application.

The dedicated source does not establish all whitespace, reserved-ASCII, already-encoded-percent, invalid-input or error cases. Do not promise a safe-character whitelist or automatic prevention of double encoding from this evidence. The complete documented examples and additional independent non-ASCII controls are the scope certified here.

• Collabora Office 26.04: ENCODEURL.
• Editorial testing standards.

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.