Zoho Sheet ARABIC Function: Roman Numerals to Numbers

Zoho’s official ARABIC reference was retrieved on October 15, 2026. This establishes documentation in the rolling web service, not the original introduction release or a final functioning-version endpoint; both historical endpoints remain unverified. Mobile/offline parity is not established. Additional numerical examples below were independently calculated. No native Zoho Sheet execution or cross-product import test was performed.

ARABIC("text")

The quoted placeholder in Zoho’s signature represents a Roman string. For a literal, include quotes, such as ARABIC("MM"); for a cell reference, use ARABIC(A2) without quotes. Quoting "A2" would pass those literal characters instead of the cell’s content.

The help describes Roman values from 1 through 3999, and separately states that an empty string returns 0. It also documents case-insensitive conversion: MM and mm have the same numeric meaning. The empty-string exception is not evidence that whitespace, a physically empty cell, a numeric zero or arbitrary invalid text behaves identically.

Create ArabicControls. Enter text VI in A2, MMMCMXCIX in A3 and MM in A4. Enter =ARABIC(A2) in B2 and fill through B4. Expected results are 6,3999,2000. The first two correspond to vendor literals; MM supplies an explicit input for the documented 2000 result rather than leaving its referenced cell unspecified.

In D2 enter =ARABIC(""), expected 0. In D3 enter =ARABIC("mm"), expected 2000. These are different tests: D2 exercises the documented empty-string exception, while D3 tests case insensitivity.

Create NumeralValues with Original, Value, Double_value and Standard_label in A1:D1. Enter the text below in A2:A9 and fill B2 =ARABIC(A2), C2 =2*B2 and D2 =ROMAN(B2;0) through row 9.

D should reproduce the standard uppercase strings in this selected table. ROMAN is the reverse-direction function, with an explicitly supplied simplification mode of 0. Do not apply it blindly to D2 of ArabicControls: its zero result lies outside the documented ROMAN range.

Duplicate NumeralValues as ChangedNumeral and change A5 from IX to X. B5 changes from 9 to 10, C5 from 18 to 20, and D5 becomes X. Other rows remain unchanged.

Create CaseAudit with Source, Number, Exact_uppercase and Original_length in A1:D1. Enter MM, mm, Mm in A2:A4. Fill these formulas through row 4:

B2: =ARABIC(A2)
C2: =EXACT(A2;"MM")
D2: =LEN(A2)

B is 2000 throughout; C is TRUE,FALSE,FALSE; D is 2 throughout. Numeric conversion has intentionally discarded the case distinction. If a citation, catalog key or publication style requires original capitalization, retain A and inspect it separately.

A second useful workflow is numeric ordering: enter IX, XL, IV, XC in F2:F5 and fill G2 =ARABIC(F2) through G5. The values are 9,40,4,90. Their ascending numeric order is IV, IX, XL, XC. Keep the original text aligned with its converted number when sorting; rearranging only G would corrupt the pairs.

The checked documentation does not define a complete Roman grammar or say which nonstandard subtractive forms it accepts. A conversion function should not be treated as a strict style validator. Whitespace, negative signs, over-range values, Unicode Roman numeral characters, blank references and exact error messages remain unverified here.

Zoho’s shared glossary names invalid-type/name/reference failures, but it is not a comprehensive ARABIC parser specification. If a value fails, compare it with the successful VI control and inspect the actual string. If empty means missing in your dataset, preserve that distinction before conversion: the documented empty-string output 0 is a real numeric result and can affect averages or counts.

EXACT compares text identity; LEN checks the number of characters. Neither proves a Roman numeral is stylistically valid. Cross-product acceptance of unusual spellings and error behavior has not been established by this guide’s independent conventional-numeral checks.