[MEI-L] <div> in header

Sun Oct 25 23:00:38 CET 2015

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.

This is somewhat related to a recent discussion on GitHub: https://github.com/music-encoding/music-encoding/issues/272

-Andrew

> On Oct 25, 2015, at 1:23 PM, Axel Teich Geertinger <atge at kb.dk> wrote:
> 
> Hi
> 
> Is there any particular reason why <div> elements are not allowed anywhere in the header?
> 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. 
> 
> 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>?
> 
> Best,
> Axel
>  
> _______________________________________________
> mei-l mailing list
> mei-l at lists.uni-paderborn.de <mailto:mei-l at lists.uni-paderborn.de>
> https://lists.uni-paderborn.de/mailman/listinfo/mei-l <https://lists.uni-paderborn.de/mailman/listinfo/mei-l>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.uni-paderborn.de/pipermail/mei-l/attachments/20151025/19323589/attachment.html>