<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 2014-05-25 18:05, Matteo Campanelli
wrote:<br>
</div>
<blockquote
cite="mid:CAMuW_XxBiDVpGm9+d1+wteEyf5X=3Tka+p82So41+1RM5gUS3w@mail.gmail.com"
type="cite">
<div dir="ltr"><span
style="font-family:arial,sans-serif;font-size:12.800000190734863px"></span><span
style="font-family:arial,sans-serif;font-size:12.800000190734863px">during
last week I studied how to make arbitrary portions of text
have a (possibly transparent) background color. </span>
<div><span
style="font-family:arial,sans-serif;font-size:12.800000190734863px">So
far I have been able to render a monochromatic
non-transparent background behind text (see attachment).</span><br>
</div>
</div>
</blockquote>
<br>
Hi<br>
<br>
Nice work!<br>
<br>
I'm not sure how LO's current glyph bitmap caching works, but you
might run into some visual artifacts with anti-aliasing.<br>
<br>
Some programs cache the rendering of glyphs, especially when doing
anti-aliasing, because it is quite expensive to do the computation.<br>
<br>
However, this can lead to some odd pixel effects when you change the
background color, because doing anti-aliasing properly is dependent
on both the color of the glyph and the color of the background.<br>
<br>
Hopefully LO doesn't have this problem, but just in case, I thought
you should know.<br>
<br>
Regards, Noel Grandin<br>
<br><br><br><hr><font size="-2" color=808080>Disclaimer: <a href="http://www.peralex.com/disclaimer.html">http://www.peralex.com/disclaimer.html</a><br><br>
</body>
</html>