Supported Fonts

Odia encodings, and where each one stands

A legacy font stores Odia letters in the slots of Latin characters, and every font family uses different slots. That is why text pasted from an old file looks like gibberish — and why each font needs its own rules.

Unicode OdiaUnicode

The international standard (U+0B00–U+0B7F). Works in Word, Google Docs, websites, email and phones with any Unicode Odia font such as Noto Sans Oriya or Kalinga.

Akruti SaralaLegacy

Akruti family legacy encoding (AkrutiOriSarala and related fonts), common in Odisha DTP and printing.

SreelipiLegacy

Sreelipi (spelled “Shreelipi” upstream) legacy Odia font encoding, common in publishing and newspapers.

AprantaLegacy

Apranta (spelled “Aprant” upstream) legacy Odia font encoding.

ORTT SaralaLegacy

ORTT Sarala legacy encoding. Despite the shared word “Sarala”, its layout differs from Akruti Sarala.

SambadLegacy

Not yet available. Upstream once had a Sambad EML converter but removed it in July 2016; no verified mapping is in use.

GISTLegacy

Not yet available. No verified mapping has been sourced.

LipikarLegacy

Not yet available. The exact encoding and version still need to be identified.

Conversion directions

Legacy-to-legacy (for example Akruti Sarala to Sreelipi) goes through Unicode and opens only when both halves are verified.

DirectionStatusNotes
Akruti SaralaUnicode OdiaAvailable · betaByte-identical to the OdiaWikimedia converter on our start-up self-test. Independent proof-read reference text is still being collected, so please proof-read important work.
Unicode OdiaAkruti SaralaIn developmentIn development. Upstream provides no Unicode-to-legacy rules, and reversing the table is not safe (it is neither one-to-one nor context-free). Needs reference text typed in this font.
SreelipiUnicode OdiaAvailable · betaByte-identical to the OdiaWikimedia converter on our start-up self-test. Independent proof-read reference text is still being collected, so please proof-read important work.
Unicode OdiaSreelipiIn developmentIn development. Upstream provides no Unicode-to-legacy rules, and reversing the table is not safe (it is neither one-to-one nor context-free). Needs reference text typed in this font.
AprantaUnicode OdiaAvailable · betaByte-identical to the OdiaWikimedia converter on our start-up self-test. Independent proof-read reference text is still being collected, so please proof-read important work.
Unicode OdiaAprantaIn developmentIn development. Upstream provides no Unicode-to-legacy rules, and reversing the table is not safe (it is neither one-to-one nor context-free). Needs reference text typed in this font.
ORTT SaralaUnicode OdiaAvailable · betaByte-identical to the OdiaWikimedia converter on our start-up self-test. Independent proof-read reference text is still being collected, so please proof-read important work.
Unicode OdiaORTT SaralaIn developmentIn development. Upstream provides no Unicode-to-legacy rules, and reversing the table is not safe (it is neither one-to-one nor context-free). Needs reference text typed in this font.
SambadUnicode OdiaPlannedNo verified mapping yet.
Unicode OdiaSambadPlannedNo verified mapping yet.
GISTUnicode OdiaPlannedNo verified mapping yet.
Unicode OdiaGISTPlannedNo verified mapping yet.
LipikarUnicode OdiaPlannedNo verified mapping yet.
Unicode OdiaLipikarPlannedNo verified mapping yet.

Engine version 1.0.0+upstream.76664f0. Font names are used only to describe compatibility; no font files are provided here.