<html dir="ltr">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<style id="owaParaStyle" type="text/css">P {margin-top:0;margin-bottom:0;}</style>
</head>
<body ocsi="0" fpstyle="1" class="" style="word-wrap:break-word">
<div style="direction: ltr;font-family: Tahoma;color: #000000;font-size: 10pt;">Hi Andrew<br>
<br>
I can do a workaround by wrapping the contents in a <div> before passing it to the text editor and stripping it off again with XSLT on saving. Nevertheless, I am not sure I agree that header contents is never intended to be rendered. After all, the header may
contain such information as transcriptions of a source's title page. <br>
We are rendering loads of header information in our catalogues. I agree that exact placement of text blocks doesn't seem to be a likely thing to do in the header, not even within the title page transcriptions (I have no idea what kind of coordinates would make
any sense unless we implement a detailed page layout specification; but that's definitely not a road I want MEI to go down). MEI does, however, already allow quite some text formatting within <p> such as font style, size, and color, so header content may already
contain some rendering information. <br>
But more important, I do not see why <div> should be used for positioning and other rendering purposes only. On the contrary – the MEI guidelines say:
<br>
<blockquote><span class="label"><div> </span>(division) – Major structural division of text, such as a preface, chapter or section.<br>
</blockquote>
This is exactly the structuring mechanism I would like to see in the header as well: structure on a larger scale than <p>.
<br>
<br>
Best,<br>
Axel<br>
<br>
<div><br>
<p> </p>
</div>
<div style="font-family: Times New Roman; color: #000000; font-size: 16px">
<hr tabindex="-1">
<div style="direction: ltr;" id="divRpF308555"><font color="#000000" face="Tahoma" size="2"><b>Fra:</b> mei-l [mei-l-bounces@lists.uni-paderborn.de] på vegne af Andrew Hankinson [andrew.hankinson@mail.mcgill.ca]<br>
<b>Sendt:</b> 25. oktober 2015 23:00<br>
<b>Til:</b> Music Encoding Initiative<br>
<b>Emne:</b> Re: [MEI-L] <div> in header<br>
</font><br>
</div>
<div></div>
<div>Personally, I think of <div> being used to position rendered text like in HTML. So having it in the header would be problematic, since that information is never intended to be "rendered" directly.<br class="">
<div class=""><br class="">
</div>
<div class="">This is somewhat related to a recent discussion on GitHub: <a href="https://github.com/music-encoding/music-encoding/issues/272" class="" target="_blank">https://github.com/music-encoding/music-encoding/issues/272</a></div>
<div class=""><br class="">
</div>
<div class="">-Andrew</div>
<div class=""><br class="">
<div class="">
<div>
<blockquote type="cite" class="">
<div class="">On Oct 25, 2015, at 1:23 PM, Axel Teich Geertinger <<a href="mailto:atge@kb.dk" class="" target="_blank">atge@kb.dk</a>> wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<div class="" style="font-style:normal; font-variant:normal; font-weight:normal; letter-spacing:normal; orphans:auto; text-align:start; text-indent:0px; text-transform:none; white-space:normal; widows:auto; word-spacing:0px; direction:ltr; font-family:Tahoma; font-size:10pt">
Hi<br class="">
<br class="">
Is there any particular reason why <div> elements are not allowed anywhere in the header?<br class="">
I am asking this because I want to use a Rich Text Editor (tinyMCE) for blocks of text in the header, for instance in <annot> or <history> within <work>. This type of editor requires that the editable content is wrapped in a single element (like <p> or <div>).
It is not good at handling mixed content. Of course i could use <p> as the wrapper, but then I would have to have one editor instance for every paragraph, if I want more than one paragraph of text.<span class="Apple-converted-space"> </span><br class="">
<br class="">
I actually think that allowing <div> in <history> could also make the structure a little clearer. As it is, <history> may contain <head>, <creation>, <eventList> and any number of <p>s. Perhaps it would be nice to be able to wrap all non-structured text in
a single <div> to separate it from the more structured elements <creation> and <eventList>?<br class="">
<br class="">
<div class="">Best,<br class="">
Axel<br class="">
<p class="" style="margin-top:0px; margin-bottom:0px"> </p>
</div>
</div>
<span class="" style="font-family:SourceCodePro-Regular; font-size:14px; font-style:normal; font-variant:normal; font-weight:normal; letter-spacing:normal; orphans:auto; text-align:start; text-indent:0px; text-transform:none; white-space:normal; widows:auto; word-spacing:0px; float:none; display:inline!important">_______________________________________________</span><br class="" style="font-family:SourceCodePro-Regular; font-size:14px; font-style:normal; font-variant:normal; font-weight:normal; letter-spacing:normal; orphans:auto; text-align:start; text-indent:0px; text-transform:none; white-space:normal; widows:auto; word-spacing:0px">
<span class="" style="font-family:SourceCodePro-Regular; font-size:14px; font-style:normal; font-variant:normal; font-weight:normal; letter-spacing:normal; orphans:auto; text-align:start; text-indent:0px; text-transform:none; white-space:normal; widows:auto; word-spacing:0px; float:none; display:inline!important">mei-l
mailing list</span><br class="" style="font-family:SourceCodePro-Regular; font-size:14px; font-style:normal; font-variant:normal; font-weight:normal; letter-spacing:normal; orphans:auto; text-align:start; text-indent:0px; text-transform:none; white-space:normal; widows:auto; word-spacing:0px">
<a href="mailto:mei-l@lists.uni-paderborn.de" class="" style="font-family:SourceCodePro-Regular; font-size:14px; font-style:normal; font-variant:normal; font-weight:normal; letter-spacing:normal; orphans:auto; text-align:start; text-indent:0px; text-transform:none; white-space:normal; widows:auto; word-spacing:0px" target="_blank">mei-l@lists.uni-paderborn.de</a><br class="" style="font-family:SourceCodePro-Regular; font-size:14px; font-style:normal; font-variant:normal; font-weight:normal; letter-spacing:normal; orphans:auto; text-align:start; text-indent:0px; text-transform:none; white-space:normal; widows:auto; word-spacing:0px">
<a href="https://lists.uni-paderborn.de/mailman/listinfo/mei-l" class="" style="font-family:SourceCodePro-Regular; font-size:14px; font-style:normal; font-variant:normal; font-weight:normal; letter-spacing:normal; orphans:auto; text-align:start; text-indent:0px; text-transform:none; white-space:normal; widows:auto; word-spacing:0px" target="_blank">https://lists.uni-paderborn.de/mailman/listinfo/mei-l</a></div>
</blockquote>
</div>
<br class="">
</div>
</div>
</div>
</div>
</div>
</body>
</html>