<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix">Hi Juan,</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">thanks for the explanation. I suspected
it had to do with the technique being used for VG.</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">Cheers,</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix"> Mariano</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">El 31/10/22 a las 12:37, Juan Vuletich
escribió:<br>
</div>
<blockquote type="cite" cite="mid:635FEBC0.4040200@cuis.st">
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
Hi Mariano,<br>
<br>
Thanks for the samples and the details on your screen. Now I can
tell what you see.<br>
<br>
Other Text Rasterization Engines, such as FreeType, CoreText and
ClearType do auto-hinting of glyphs. This aligns glyph features to
integer pixel coordinates at the expense of correct geometry.
VectorEnginePlugin doesn't. It rasterizes glyphs just like any
other vector graphics, respecting the true geometry of glyphs.<br>
<br>
This is only noticeable in horizontal lines, when they want to
cover half a pixel or so.<br>
<br>
If you disable glyph caching, or (even slightly) zoom windows,
then not even the position of glyphs is aligned to integer pixels,
giving a more correct layout of text, making each instance of the
same character be drawn differently. You can see this if you
capture a screen and zoom the pixels to make them larger.<br>
<br>
This is a rather fundamental decision on how VectorEngine works.
It doesn't "draw pixels", but applies a low pass filter and then
samples a continuous shape.<br>
<br>
The older StrikeFonts were rendered with FreeType, and then
captured as Bitmaps.<br>
<br>
Thanks,<br>
<br>
<br>
<br>
On 10/30/2022 10:28 AM, Mariano Montone via Cuis-dev wrote:
<blockquote
cite="mid:ccaec59e-9d55-258f-2a9e-f7eb26527844@gmail.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=UTF-8">
<div class="moz-cite-prefix">El 29/10/22 a las 21:01, Juan
Vuletich escribió:<br>
</div>
<blockquote type="cite" cite="mid:635DBEDF.1060201@cuis.st">Hi
Mariano, <br>
<br>
On 10/29/2022 7:53 AM, Mariano Montone via Cuis-dev wrote: <br>
<blockquote type="cite">A thing I would like to adjust if it
were possible, is that I feel like the font rendering loses
some sharpness with VG; some fonts more than others, and
some sizes more than others. <br>
</blockquote>
<br>
You can tweak
VectorEngineWithPluginSubPixel>>#defaultAntiAliasingWidth
and then evaluate `TrueTypeFont allInstancesDo: [ :f | f
releaseCachedState ].`, to try different parameters for the
antialiasing filter. <br>
</blockquote>
Ah, apologies to Gerald, I didn't see that part when he pointed
it to me.<br>
<blockquote type="cite" cite="mid:635DBEDF.1060201@cuis.st"> <br>
Still, I'm curious. Can you post a Display using
HybridCanvas/VectorCanvas and another using BitBltCanvas? Best
if you can include some fonts/sizes you feel are sharp enough,
and others that aren't. If file sizes are too big for the list
(I believe it is 500kb once encoded in MIME64), please send
them to me privately. <br>
</blockquote>
I'm inserting some images below. Look at the equality symbol for
example. I think the problem is that the greying of the font is
too much and makes the font blurry. But my comparison is
probably unfair, since I'm using the DejaVuBitmap font for the
Bitmap case, with doesn't use the greying, or too little; but
that's an example of what I mean "sharp".<br>
<blockquote type="cite" cite="mid:635DBEDF.1060201@cuis.st"> <br>
One question: What Display resolution do you use? Size of
screen? Does the `Display size` in Cuis match the OS and
physical screen resolution? (this is rarely the case on MacOS,
unfortunately). <br>
</blockquote>
<p>I'm on Linux with screen size of 1366x768. Cuis Display is
1360x713.<br>
</p>
<blockquote type="cite" cite="mid:635DBEDF.1060201@cuis.st"> <br>
Finally, a screen capture of an editor in your host OS with
some text that looks sharp to your eyes would be helpful. <br>
</blockquote>
<p>Bitmap Cuis (DejaVuBitmap) (sharp):<br>
</p>
<p><img moz-do-not-send="false"
src="cid:part1.xtEKEv0A.nbct5jUJ@gmail.com" alt="" class=""
width="252" height="100"></p>
<p>Vector (DejaVuSans) (not sharp):<br>
</p>
<p><img moz-do-not-send="false"
src="cid:part2.Sg5quF5K.h8tIyVbn@gmail.com" alt="" class=""
width="269" height="91"></p>
<p>Host OS app:</p>
<img moz-do-not-send="false"
src="cid:part3.ah9kOm8I.lkRSiLBv@gmail.com" alt="" class=""
width="820" height="108"><br>
<p>I feel like the Host OS is using less greying around the
fonts than Cuis and that makes it sharper.</p>
<p><br>
</p>
<p>Thanks, <br>
</p>
<p> Mariano<br>
</p>
<br>
<p><br>
</p>
</blockquote>
<br>
<br>
<pre class="moz-signature" cols="72">--
Juan Vuletich
cuis.st
github.com/jvuletich
researchgate.net/profile/Juan-Vuletich
independent.academia.edu/JuanVuletich
patents.justia.com/inventor/juan-manuel-vuletich
linkedin.com/in/juan-vuletich-75611b3
twitter.com/JuanVuletich</pre>
</blockquote>
<p><br>
</p>
</body>
</html>