<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:"Yu Gothic";
panose-1:2 11 4 0 0 0 0 0 0 0;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:"Segoe UI Historic";
panose-1:2 11 5 2 4 2 4 2 2 3;}
@font-face
{font-family:"\@Yu Gothic";
panose-1:2 11 4 0 0 0 0 0 0 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:36.0pt;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:967978198;
mso-list-type:hybrid;
mso-list-template-ids:-1811390328 -1 134807577 134807579 134807567 134807577 134807579 134807567 134807577 134807579;}
@list l0:level1
{mso-level-number-format:alpha-lower;
mso-level-text:"%1\)";
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
ol
{margin-bottom:0cm;}
ul
{margin-bottom:0cm;}
--></style>
</head>
<body lang="EN-GB" link="blue" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal">All</p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">My error: I had meant to say 8 format controls in total, 6 are new – the original 2 (VJ and HJ) were proposed over two years ago though still waiting to be released in a future version of the Unicode standard.</p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">One thing to be clear about. There are many data formats that can use Unicode hieroglyphic so UMdC does not have to do everything. For instance Daniel mentions TEI-XML an established system and there are many more.</p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Daniel:</p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The Rosetta data makes for an excellent example lets discuss this off list and get a TEI with new Unicode version together – replacing items like <seg rendition="#vert"><span style="font-family:"Segoe UI Historic",sans-serif">𓀎𓏥</span></seg>
with <span style="font-family:"Segoe UI Historic",sans-serif">𓀎:𓏥 </span> aids readability considerably and its interesting to see TEI and putative UMdC side by side.</p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Incidentally I’m writing some guidelines for hieroglyphic in Markdown for publishing docs on Github etc.</p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Serge:</p>
<p class="MsoNormal"><o:p> </o:p></p>
<ol style="margin-top:0cm" start="1" type="a">
<li class="MsoListParagraph" style="margin-left:0cm;mso-list:l0 level1 lfo1">I envisage UMdC as a simple plain text markup system focussed on end user usability rather than an XML file format so more akin to Markdown than TEI-XML (but less complex fundamentally
than either). However I agree that (for instance) a tag convention for signs missing in Unicode can be useful. The possible approaches can be discussed in detail.</li><li class="MsoListParagraph" style="margin-left:0cm;mso-list:l0 level1 lfo1">I agree.</li></ol>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Regards,</p>
<p class="MsoNormal">Bob</p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-family:"Segoe UI Historic",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div style="mso-element:para-border-div;border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal" style="border:none;padding:0cm"><b>From: </b><a href="mailto:rosmord@gmail.com">Serge Rosmorduc</a><br>
<b>Sent: </b>26 July 2017 06:49<br>
<b>To: </b><a href="mailto:egyptian@evertype.com">Egyptian Hieroglyphs in the UCS</a><br>
<b>Subject: </b>Re: [Egyptian] UMdC - A Unicode Coding Manual for Egyptian?</p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">dear all, <o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">My two cents on the subject:<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">a) If XML is used (and XML is needed for some uses), I believe we should use it for all structural information. We don't want to need to parse XML and some light MDC in the same file. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">I also believe that regularity and ease of processing are more important than convenience when manually writing XML. In particular, I would use an XML element for each sign (it's needed in some cases to attach properties to the sign, so
let's use it in all cases).<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">b) For simple texts, the MDC has the advantage of being somehow readable - and will be even more with Unicode.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Both uses might be kept alongside each other. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">best regards<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Serge<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">Le 25 juil. 2017 13:57, "Daniel Werning" <<a href="mailto:daniel.werning@topoi.org">daniel.werning@topoi.org</a>> a écrit :<o:p></o:p></p>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm">
<p class="MsoNormal">Dear Bob,<br>
<br>
I am generally interested in joining the discussion.<br>
I have exercised some encoding in TEI XML based on the current state of Unicode encoding.<br>
See: <a href="http://rosettastone.hieroglyphic-texts.net/tei-xml/" target="_blank">
http://rosettastone.hieroglyphic-texts.net/tei-xml/</a>.<br>
The encoding of the arrangement will be easier with the six control characters in pipeline for Unicode. However, there are cases left of non-unicode signs and non-simple arrangements, which can -- nicely, I believe -- be encoded in TEI XML. Anyhow, I can imagine
that I can contribute based on my experience.<br>
<br>
All the best,<br>
Daniel (Werning)<br>
-- <br>
_____________________________________________________________<br>
Dr. Daniel A. Werning<br>
<br>
<a href="mailto:daniel.werning@topoi.org" target="_blank">daniel.werning@topoi.org</a><br>
<a href="http://www.topoi.org/person/werning-daniel-a/" target="_blank">http://www.topoi.org/person/werning-daniel-a/</a><br>
<br>
Exzellenzcluster Topoi<br>
Humboldt-Universität zu Berlin<br>
_____________________________________________________________ <o:p></o:p></p>
<div>
<p class="MsoNormal"><br>
<br>
<br>
Am 25.07.2017 um 12:11 schrieb Bob Richmond:<o:p></o:p></p>
</div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm">
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt">Hi All<br>
<br>
1071 Hieroglyphs have been available in Unicode since version 5.2 (2009). Six formatting characters are now in the pipeline (since May). Eventually there will be more hieroglyphs and likely control characters too.<br>
<br>
The idea of defining a data file format “UMdC” acknowledging Unicode was discussed at I&E 2006 and afterwards but the lack of Unicode availability in the standard and issues of application and system support made this seem a little premature. It seems to me
the time is now ripe to revisit the topic.<br>
<br>
The basics of UMdC (as I see it) are as follows:<o:p></o:p></p>
</div>
<p class="MsoNormal"> 1. A well defined file type “umdc” containing plain text and markup
<o:p></o:p></p>
<div>
<p class="MsoNormal"><br>
(capable of being edited in simple text editors such as Windows<br>
Notepad and HTML textarea blocks).<o:p></o:p></p>
</div>
<p class="MsoNormal"> 2. Guidance on subset usage in database records.<br>
3. Basic plain text including the 1071 + 6 for Egyptian characters<br>
(plus e.g. transliteration formats).<br>
4. Markup to deal with elements missing from Unicode such as <o:p></o:p></p>
<div>
<p class="MsoNormal"><br>
hieroglyphs not in the 1071 set.<o:p></o:p></p>
</div>
<p class="MsoNormal"> 5. Optional markup to help with preparing data for use with other
<o:p></o:p></p>
<div>
<p class="MsoNormal"><br>
formats such as HTML/CSS and Office applications.<o:p></o:p></p>
</div>
<p class="MsoNormal"> 6. Optional markup to help with interoperability with MdC88 based data
<o:p></o:p></p>
<div>
<p class="MsoNormal"><br>
formats (including extensions such as JSesh).<o:p></o:p></p>
</div>
<p class="MsoNormal"> 7. Specification of font requirements needed for representation of UMdC
<o:p></o:p></p>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
data.<br>
<br>
So long as the markup system is sufficiently flexible (e.g. use of XML-like tags) version 1 of UMdC need not be overly featured and then additions can be made as need is proven. It should be possible to create a version 1 specification supported with basic
tools in months not years.<br>
<br>
I expect I’m not the only person who has already done related work. Has anyone any points to make of what they would like to see in UMdC? Anyone like to get involved in defining the markup scheme?<br>
<br>
Thanks<br>
<br>
Bob Richmond<br>
<br>
<br>
<o:p></o:p></p>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt">_______________________________________________<br>
Egyptian mailing list<br>
<a href="mailto:Egyptian@evertype.com" target="_blank">Egyptian@evertype.com</a><br>
<a href="http://evertype.com/mailman/listinfo/egyptian_evertype.com" target="_blank">http://evertype.com/mailman/listinfo/egyptian_evertype.com</a><o:p></o:p></p>
</blockquote>
<p class="MsoNormal"><br>
_______________________________________________<br>
Egyptian mailing list<br>
<a href="mailto:Egyptian@evertype.com" target="_blank">Egyptian@evertype.com</a><br>
<a href="http://evertype.com/mailman/listinfo/egyptian_evertype.com" target="_blank">http://evertype.com/mailman/listinfo/egyptian_evertype.com</a><o:p></o:p></p>
</blockquote>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>