<div dir="auto">dear all, <div dir="auto"><br></div><div dir="auto">My two cents on the subject:</div><div dir="auto"><br></div><div dir="auto">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. </div><div dir="auto"><br></div><div dir="auto">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).</div><div dir="auto"><br></div><div dir="auto">b) For simple texts, the MDC has the advantage of being somehow readable - and will be even more with Unicode.</div><div dir="auto">Both uses might be kept alongside each other. <br></div><div dir="auto"><br></div><div dir="auto"><br></div><div dir="auto"><br></div><div dir="auto">best regards</div><div dir="auto"><br></div><div dir="auto">Serge</div><div dir="auto"><br></div><div dir="auto"><div dir="auto"><br></div></div></div><div class="gmail_extra"><br><div class="gmail_quote">Le 25 juil. 2017 13:57, "Daniel Werning" <<a href="mailto:daniel.werning@topoi.org">daniel.werning@topoi.org</a>> a écrit :<br type="attribution"><blockquote class="quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">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/" rel="noreferrer" target="_blank">http://rosettastone.hieroglyph<wbr>ic-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>
______________________________<wbr>______________________________<wbr>_<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/" rel="noreferrer" target="_blank">http://www.topoi.org/person/we<wbr>rning-daniel-a/</a><br>
<br>
Exzellenzcluster Topoi<br>
Humboldt-Universität zu Berlin<br>
______________________________<wbr>______________________________<wbr>_<div class="quoted-text"><br>
<br>
<br>
Am 25.07.2017 um 12:11 schrieb Bob Richmond:<br>
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="quoted-text">
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:<br>
<br></div>
1. A well defined file type “umdc” containing plain text and markup<div class="quoted-text"><br>
(capable of being edited in simple text editors such as Windows<br>
Notepad and HTML textarea blocks).<br></div>
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<div class="quoted-text"><br>
hieroglyphs not in the 1071 set.<br></div>
5. Optional markup to help with preparing data for use with other<div class="quoted-text"><br>
formats such as HTML/CSS and Office applications.<br></div>
6. Optional markup to help with interoperability with MdC88 based data<div class="quoted-text"><br>
formats (including extensions such as JSesh).<br></div>
7. Specification of font requirements needed for representation of UMdC<div class="quoted-text"><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>
<br></div>
______________________________<wbr>_________________<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" rel="noreferrer" target="_blank">http://evertype.com/mailman/li<wbr>stinfo/egyptian_evertype.com</a><br>
<br>
</blockquote>
<br>
______________________________<wbr>_________________<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" rel="noreferrer" target="_blank">http://evertype.com/mailman/li<wbr>stinfo/egyptian_evertype.com</a><br>
</blockquote></div><br></div>