<html>
<head>
<base href="https://bugs.documentfoundation.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Font in character style should be initialized with what is defined on paragraph style"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=136433#c4">Comment # 4</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Font in character style should be initialized with what is defined on paragraph style"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=136433">bug 136433</a>
from <span class="vcard"><a class="email" href="mailto:telesto@surfxs.nl" title="Telesto <telesto@surfxs.nl>"> <span class="fn">Telesto</span></a>
</span></b>
<pre>(In reply to Heiko Tietze from <a href="show_bug.cgi?id=136433#c2">comment #2</a>)
<span class="quote">> Yes, this enhancement would make it more clear. However, the CS is first of
> all a style independently from the actual PS. You can, for example, also
> edit a CS that is not yet applied. That's also why CS has no WYSIWYG font
> when preview is on (unlike PS). So it's likely a WF: CS has no hierarchy,
> and no parent until it is used.</span >
Which would mean a new (place holder 'font') called inherited ;-). They CS
style obviously not show any 'font'; as which font it is depends on PS. Except
if the CS style defines a specific font (overriding the PS).
Currently CS style look show up as if they are overriding PS styles, which
isn't the case.</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>