Graphic interface Text Editor External viewable coding Rendering engine Internal coding MdC Our Subject

in user terms : MdC coding is easily understood and learned MdC coding is concise MdC coding provides two sets of functionalities : basic (i.e. implemented by all rendering engines) extended functionalities (i.e. optional but implemented using a standardised syntax) current MdC88 is supported for a certain period of time In rendering engines terms : MdC coding is based on a « regular » syntax to be easily implementable and to reduce the consumed resources software not supporting « extended functionalities » is silencious at rendering time Software should provide a tool signaling « deprecated » and not supported « extended functionalities » MdC Basic Requirements

Basic and Extended Functionalities Engine 1Engine 2Engine 3 Basic functionalities Extended functionality A Extended functionality B Extended functionality C Basic Extended Render a fragment of textrender a facsimile Simple cadratscomplex cadrats Simple alignmentscomputed alignments No textintegrated texts…

Last version of the Manuel de Codage released in 1988 has been fruitfully used for many years Two directions of evolutions direction 1 : introduction of new functionalities direction 2 : move to a « state of the art » syntax MdC Evolutions

Alignments / tabulations Other alignments Browsable facsimile Nefertabiet stela New Functionalities (two examples)

Other Alignments Cartridges in three contiguous vertical texts are horizontally aligned Louxor Obelisque (South face - Paris, place de la concorde)

Browsable Facsimile Navigation into Nefertabiet Stela (Projet Rosette implementation)

Click

Browsable Facsimile Astronomic ceiling - Ramesseum (projet Rosette implementation)

Last version of the Manuel de Codage released in 1988 has been used for many years Two directions of evolutions direction 1 : introduction of new functionalities direction 2 : move to a « state of the art » syntax MdC Evolutions

MdC88 fundation syntax is almost convenient anx wDA snb or G17 D54:I9 D21 MdC88 syntax for « modifications » is now inappropriate (chaotic, inconsistent) usage and learning made difficult by needless inconsistencies for instance # for hashing and superposition characters wasted mixing syntaxic and semantic roles which character for aligments marks ? how to draw grey hieros ? $g ? irregular syntax makes impossible to use standard tools Move to a State of the Art Syntax Stela king Kamose

keep the fundation syntax mark unapropriate syntax elements as « deprecated » implement new and consistent operators fully support MdC88 during a limited initial phase Move to a State of the Art Syntax (suggested guidelines) Deprecated : « marked as obsolete to warn against its use in the future so that it may be phased out »

MdC88 fundation syntax is kept as it is modifications of individual glyphs are always coded by postfixed operator beginning by a / these operators may be factorised to several hieroglyphs by parenthesis modification of « states » (orientation, direction,…) specified by # tags MdC88 is fully supported (hopefully for a limited period of time) A syntax checker is available Full Unicode 5.2 / EGPZ : under the hood ! Move to a State of the Art Syntax (projet Rosette implementation)

Modification of individual glyphs Tags for modification of « state » A1 A1/cr A1/r45 ( A1 A1/r45 )/cr /cr color red oH orientation Horizontal, dr direction right to left #poH;dr U28 G1 P34/ar25:pt #poV D58*(N35:W24) G31 D4 Q1*A40 Move to a State of the Art Syntax (projet Rosette implementation) Ramesseum /r45 rotate 45°( … ) factorize /cr oV orientation Vertical /ar25 hashing 25% from right

Suggested Road Map Define new syntax morphology guidelines. As a consequence, list the « deprecated » syntax elements List « Basic » functionalities (and associated syntax) List a first set of « extended » functionalities (and associated syntax) Determine appropriate milestones and associated timing A dedicated working-group should be missioned and structured to follow this road-map with a major milestone to the next I&E meeting. An on-line forum should support this effort.