<html>
<head>
<base href="https://bugs.documentfoundation.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Style indicator in document margin"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=38194#c22">Comment # 22</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Style indicator in document margin"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=38194">bug 38194</a>
from <span class="vcard"><a class="email" href="mailto:kainz.a@gmail.com" title="andreas_k <kainz.a@gmail.com>"> <span class="fn">andreas_k</span></a>
</span></b>
<pre>
<span class="quote">> (In reply to andreas_k from <a href="show_bug.cgi?id=38194#c18">comment #18</a>)
> > Would it be more helpful to use an mockup language layout.
>
> Isn't the markdown/reveal code approach the opposite of feedback to the
> WYSIWYG document? I mean you enter (a few) styles to the document - and we
> have formatted it. Point here is to get an overview and understanding of
> what is applied and how styles are defined.</span >
Maybe its the other way around, but this is a complete new ui scenario and
mockup languages + highlighting is an well known approach from coding, html
editting, ... for me mockup language support is the link between latex users,
coders and an office suite.
I am thinking more like webinspector tools from firefox and chrome. Split the
content into text and styles into an separate view.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>