In my WPF application often used small size text (12-13 px). As a result I see a bad display of it (imho, for me). ClearType used (but does not help).
Example (from above is a desired result):
How you thinks, what must be helpful for me?
8
-
2I'm voting to close this question as off-topic because this belongs to stack overflow– joojaaJun 14, 2017 at 10:57
-
1Funny, but there they told me to go here...– D .StarkJun 14, 2017 at 11:40
-
Then why you did not vote against?– D .StarkJun 14, 2017 at 11:42
-
I did that message is generated by the vote system. In anycase you question does not have any actionable points, what i think is not a question. Yes text antialiasing is sometimes an issue. Not much you can do about that.– joojaaJun 14, 2017 at 12:09
-
1Just to be clear: Above is the desired result and below is what you obtain, right? If so, note that the below case looks as if it has compression artifacts, which makes it quite difficult to make good statements about the actual font rendering. Also, what exactly do you consider bad?– Wrzlprmft ♦Jun 15, 2017 at 7:19
|
Show 3 more comments
2 Answers
Use a bitmap font just in the wanted size. Get one that is designed for small size. Prevent any scaling and smoothing.
-
-
Forgot to add that Kaspersky Antivirus font is perfect! It is represented in the picture (which is on top).– D .StarkJun 14, 2017 at 14:40
-
I was told that subpixel (ClearType) smoothing is applied. Is this true?– D .StarkJun 14, 2017 at 14:42
-
@D.Stark Unfortunately bitmap fonts cannot have very large stylistic variation spectrum. It's difficult enough to get all needed characters acceptably visible. Please, check, if something applicable exixts here dafont.com/bitmap.php?page=1&text=Bitmap+Text+for+Everyone. I'm not a programmer so I cannot give proper answers for that area. But surely any smoothing means harmful blurring too in small sizes.– user82991Jun 14, 2017 at 14:51
The bottom image looks like it is using greyscale subpixel rendering. This is normal behavior in WPF for certain circumstances. The following randomly selected link summarizes better than I can:
This is not a bug actually, rather it's a known limitation, there are some of situations in which font antialiasing algorithm will fallback to grayscale, they are:
- Text content rendered into software render target using RenderTargetBitmap.
- Text content hosted inside layered windows (aka ContextMenus, ToolTips etc).
- Text content rasterized into VisualBrush.
- Text content rendered into a CompostionTarget whose Background property is set to Colors.Transparent to support areo glass frame extension.
Note: this is definitely a stack overflow question.
