<div dir="ltr">I have taken a look at TextMorph textStyle which seem superfluous. All textStyle is either handled by the paragraph or the the runs in Text. <div>It seems we can replace all references to TextMorph textStyle instance variable to paragraph textstyle without any side effects.</div><div>But I guess we must keep the instance variable for backwards compability.</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Apr 30, 2015 at 2:29 PM, karl ramberg <span dir="ltr"><<a href="mailto:karlramberg@gmail.com" target="_blank">karlramberg@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi,<div>the current font handling could need a refactoring/ cleanup.</div><div>Emphasis of a font are stored in different places and that makes it inconsistent and very hard to interface.</div><div><br></div><div>As far as I can tell should the emphasis info be stored as a text attribute.</div><div>But it seems that many tools set the emphasis directly in the font.</div><div><br></div><div>Here is a couple of examples from text in Workspaces:</div><div><br></div><div>{a TextEmphasis code: 1 . aTextFontReference(TTCFont(BitstreamVeraSansMono 24 Bold Oblique))}<br></div><div>This font has bold and italics set in the font (corresponds to value 3), but the emphasis attribute is 1 which corresponds to bold.<br></div><div><br></div><div>{a TextFontReference(a StrikeFont(Accumon10 12))}</div><div>Here is also emphasis set in the font and no emphasis attribute is present at all.</div><span class="HOEnZb"><font color="#888888"><div><br></div><div><br></div><div>Karl</div></font></span></div>
</blockquote></div><br></div>