Bidirectional MdC↔Unicode converter

Sign list: Unicode (Egyptian Hieroglyphs + Extended-A). Quadrats are encoded with the Unicode Egyptian Hieroglyph Format Controls and displayed with the bundled Egyptian OpenType font (Microsoft, SIL OFL); outside this page, a font that supports these controls is needed to see the signs arranged.

MdC Meaning Unicode
- or space Quadrat separator –
A:B A above B U+13430
A*B A beside B U+13431
( ) Grouping U+13437 / U+13438
A&B B overlaid on A U+13436
A^tsB, ^bs, ^te, ^be Insert B at top-start / bottom-start / top-end / bottom-end of A U+13432–U+13435
A^tB, ^m, ^b Insert B at top / middle / bottom of A U+1343A / U+13439 / U+1343B
A\ Mirrored sign U+13440
A\r1, \r2, \r3, \R45 Rotation 90° / 180° / 270° / other angles VS1–VS7
A#1234 Damaged quarters (1 top-start, 2 top-end, 3 bottom-start, 4 bottom-end) U+13447–U+13455
.., . Full / half blank U+13441 / U+13442
//, /, v/, h/ Lost sign: full / half / tall / wide U+13443–U+13446
< ... >, <2, 1>, <0, 0> Cartouche, knotted start, knotless end, no visible end U+1343C / U+1343D
<S ... S>, <H ... H>, <h2, <h3 Serekh, hwt (low / high) U+1343C / U+1343D
<F ... F> Fortified wall U+1343E / U+1343F
[[ ]], [' '], [{ }], [& &] Editorial marks [ ] ⸢ ⸣ { } ⟦ ⟧
! End of line Line break

Example: G17^bsX1-<-N5-Y5:N35-L1->

About this converter

A current debate in digital Egyptology concerns the use of Unicode as a standard for encoding hieroglyphs in academic publications.

In this field, the Manuel de Codage (MdC), as used by applications such as JSesh, has long held that role, much as LaTeX is used to encode mathematical expressions in other academic disciplines. MdC works well for producing images, but a long-standing question has been whether correctly formatted hieroglyphic lines can be embedded as inline text without inserting images into the text.

Unicode seems like a reasonable solution. Until recently, however, its hieroglyph repertoire was relatively limited, especially compared with JSesh, whose sign inventory contains roughly 7,000 signs. This changed substantially with Unicode 16.0 (2024), which introduced the Egyptian Hieroglyphs Extended-A block with 3,995 additional characters. The current Unicode 18.0 sign database used by this converter covers 5,067 signs. Unicode 12.0 (2019) had already introduced the Egyptian Hieroglyph Format Controls, which arrange signs into quadrats and position or transform them in ways similar to JSesh. See also the Unicode specification for these controls. Unicode 18.0 continues this technical development, and updates the Unikemet database, which provides information to help identify, classify, and process signs in fonts and software. See the Unicode 18.0 release notes.

Despite these improvements, the repertoire remains smaller than JSesh's, particularly for subtle variants that are essential to some research, and Unicode does not support every transformation available in JSesh. Moreover, the format controls display correctly only with a font and text layout engine that support the specification. Otherwise, they may appear inline as visible boxes, as in this example:

π“…­π“΄π“‡³π“Ήπ“Όπ“‡‹π“ π“°π“ˆ–π“·π“…±π“³π“π“΄π“π“Έπ“‹Ύπ“‰Ίπ“‡—π“½π“Ί

instead of

π“…­π“΄π“‡³π“Ήπ“Όπ“‡‹π“ π“°π“ˆ–π“·π“…±π“³π“π“΄π“π“Έπ“‹Ύπ“‰Ίπ“‡—π“½π“Ί

This does not prevent Unicode from serving as a reasonable resource for research texts when used with a suitable font and software, much like transliteration. Meanwhile, hieroglyph processing applications such as JSesh remain necessary for generating figures and for contexts where exact reproduction of the original layout is essential.

With these new possibilities in mind, I have updated a small web tool and developer library that I first created in 2024 to convert between MdC and Unicode. The original version did not support sign positioning. It now includes the expanded sign repertoire and the composition and transformation mechanisms available in Unicode, giving researchers and developers familiar with MdC a way to work with this system.

ORAEC's recommendations, published in 2022 and accompanied by a checker in 2024, were valuable in developing and improving this project. However, sign variation can be important in many research contexts. I therefore preserve all variants represented in the current Unicode release rather than unifying them, for example by always mapping W17/W18 to W17. If a sign has no Unicode mapping, the converter reports β€œUnknown MdC code” instead of substituting another sign. Sign selection is left entirely to the user. Read the original ORAEC recommendations, browse the source repository and its character-by-character CSV, or try the 2024 Unicode Recommendations Checker.