JIS in Collabora Office: Convert Half-Width Text to Full Width

=JIS(Text)

Text is the required string, or a reference to a cell containing it. There are no optional format, language, or encoding arguments.

The dedicated Collabora help describes single-byte/half-width ASCII and katakana being converted to double-byte/full-width characters. Those are the product’s width terms. In a Unicode workflow, character width should not be mistaken for a promise about the number of bytes used by every file encoding.

JIS is a character conversion, not Japanese translation. It does not turn an English word into its Japanese meaning or convert a numeric identifier into a different numeric value.

Enter the following text values into A2:A5. In B2 enter =JIS(A2) and fill down.

The LibreOffice text example is explicitly supplied by Collabora’s help; it is a sample string, not a claim about another spreadsheet application’s behavior. The first two rows independently apply standard full-width ASCII letter/digit mappings, and the last row follows the documented unchanged-full-width rule.

Uppercase and lowercase remain distinct. JIS changes width; it does not uppercase all letters. If a workflow also requires case normalization, UPPER or LOWER addresses that separate operation.

=JIS("ﾗｲﾄ")

The vendor’s documented output is ライト. The input contains half-width katakana; the output contains the corresponding full-width katakana. Enter the exact characters rather than replacing them with visually similar Latin letters.

This simple control contains no separate dakuten or handakuten mark. It should not be generalized into a tested rule for every multi-character combination, punctuation variant, or combining sequence. The help links a separate conversion table for detailed mappings, but native behavior for those additional cases is not verified in this guide.

Suppose two imported records use ABC123 and ＡＢＣ１２３ for the same intended label. Put them in A2 and A5 as above. Their JIS-normalized outputs are independently expected to be the same full-width string.

Use a separate B column for the converted key and leave A untouched. This lets you compare normalized labels without losing the exact source spelling. For a simple control, =B2=B5 has independently expected result TRUE because the two resulting strings are identical.

Whether normalization is appropriate depends on the identifier system. Some systems intentionally distinguish width or character forms. Do not merge records solely because a normalization step makes their labels coincide; check the underlying record identity as well.

With B2 containing ＡＢＣ１２３, =JIS(B2) should remain ＡＢＣ１２３ under the documented full-width rule. This makes a useful repeated-conversion control for that simple string.

LEN can help inspect character counts, but equal counts do not prove the strings are equal. ABC123 and ＡＢＣ１２３ each have six visible characters while using different Unicode characters. To diagnose an import, retain actual text values rather than relying only on appearance or length.

If a result looks unchanged, inspect whether the input was already full-width, whether the font makes the difference subtle, and whether the characters fall within the documented ASCII/katakana conversion purpose. A font change can alter appearance without changing the underlying text.

The dedicated section does not enumerate numeric coercion, blank-input behavior, exact native error codes, or all punctuation and combining-mark mappings. Use text inputs and the explicit controls above before applying the function to a large import. This guide does not claim a complete Unicode normalization algorithm or a guaranteed reversible round trip through another function.

When exporting, verify the receiving system’s character and encoding requirements independently. Full-width text is not automatically accepted wherever a system asks for ASCII, and JIS does not configure the file’s encoding.

The exact function is documented in Collabora Office 26.04 desktop help, retrieved and reviewed on October 17, 2026. This establishes a documentation scope, not the first release that introduced the function or the last version in which it works; those versions and any retirement date remain unestablished. Collabora Online and mobile support are not inferred from desktop help, nor is behavior in another spreadsheet product.

The examples are documentation-based expectations with independent calculations. They have not been executed in Collabora Office. No application screenshot or native error/coercion certification is implied. Formulas use English function names and semicolon argument separators.

• Collabora Office 26.04: JIS (checked October 17, 2026).
• Editorial testing standards.