1 / 15

MdC Our Subject

MdC Our Subject. Internal coding. Graphic interface. External viewable coding. Rendering engine. Text Editor. MdC Basic Requirements. in user terms : MdC coding is easily understood and learned MdC coding is concise MdC coding provides two sets of functionalities :

shanna
Download Presentation

MdC Our Subject

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

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

  2. MdC Basic Requirements • 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 »

  3. Basic and Extended Functionalities Extended Basic Render a fragment of text render a facsimile Simple cadrats complex cadrats Simple alignments computed alignments No text integrated texts … …

  4. MdC Evolutions • 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

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

  6. Other Alignments • Cartridges in three contiguousvertical texts are horizontallyaligned Louxor Obelisque (South face - Paris, place de la concorde)

  7. Browsable FacsimileNavigation into Nefertabiet Stela(Projet Rosette implementation)

  8. Browsable FacsimileNavigation into Nefertabiet Stela(Projet Rosette implementation) Click Click

  9. Browsable FacsimileAstronomic ceiling - Ramesseum(projet Rosette implementation)

  10. MdC Evolutions • 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

  11. Move to a State of the Art Syntax Stela king Kamose • MdC88 fundation syntax is almost convenientanx 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

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

  13. Move to a State of the Art Syntax(projet Rosette implementation) • 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 !

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

  15. 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.

More Related