On 27 March 2025 the Central Bank of the UAE unveiled a symbol for the Dirham, in an announcement tied to the UAE joining the FX Global Code. Two symbols were shown that day, not one. The first is for the physical currency: a letter taken from the English name "Dirham", crossed by two horizontal lines that the Central Bank describes as embodying stability and as inspired by the UAE flag. The second is a Digital Dirham symbol — the same shape enclosed in a circle in the flag colours. Only the physical-currency symbol is the one that has been encoded, and it is the only one this module renders.

The mental model: three things moving at three speeds. A currency sign is a design, a code point and a glyph in a font, and those three are settled by three different bodies at three different times. The design was settled by the Central Bank in March 2025. The code point was agreed by the Unicode Technical Committee a few months later. The glyph — the drawing your screen actually loads to paint the character — is the slow one, and its slowness is the entire reason this module exists.

Where the encoding stands. The Unicode Technical Committee accepted U+20C3 UAE DIRHAM SIGN for encoding at meeting #184, held 22–24 July 2025, placing it in the Currency Symbols block for Unicode 18.0. Unicode 18.0 is scheduled for release in September 2026, so as at 18 August 2026 the encoding is agreed but not yet published — and a character that is not yet in a released standard is a character that virtually no operating system or browser font has drawn. That is the whole explanation for the empty box, and it is temporary.

What the module does about it. Odoone UAE Dirham Symbol carries its own font containing that single glyph, under the SIL Open Font License 1.1, so the sign renders correctly with nothing installed on anyone's machine. Its @font-face declares a unicode-range limited to that one character, so it patches in only that glyph over your normal font stack; every other character on the page keeps rendering in your regular fonts. Your typography is not being changed — one character is being supplied.

The click path. Go to Apps, search for Odoone UAE Dirham Symbol, and press Install; the technical name is odoone_uae_dirham, and it depends on web and account. If the database already runs Odoone Localization — United Arab Emirates there is a second route to the same module: tick New Dirham Symbol on Settings › UAE. Installing does one thing to your data immediately, and Lesson 2 is about that one thing.

Worked example. Marina Ridge Trading LLC installs the module on a Sunday morning. A sales invoice that read AED 1,250.00 on Saturday now reads ⃃ 1,250.00 — the new Dirham sign, before the number. The finance manager pastes that line into an email to a supplier, and the supplier sees a rectangle where the sign should be. Neither system is broken: the browser inside Odoone loaded the module's bundled font, and the mail client had no such font to load.

The failure mode. "The Central Bank's announcement says nothing about Unicode. Which code point is official?" U+20C3 is the encoded character, and you will not find it confirmed on a Central Bank page: that announcement does not mention Unicode or any code point, and the encoding proposal was not submitted by the Central Bank but authored independently. Both facts are sound, and they come from two different bodies — worth knowing before you spend an afternoon hunting for one official page that carries both.