This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(134.4, 88%, 23%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EP%3C/text%3E%3C/svg%3E)
Generates 6 different glyph images per character
https://www.codeproject.com/Articles/368070/A-WPF-Font-Picker-with-Color
Generates many different glyph images per character
https://learn.microsoft.com/en-us/samples/microsoft/wpf-samples/font-dialog-box-demo/
Microsoft Technologies based on the .NET software framework. Miscellaneous topics that do not fit into specific categories.
Answer accepted by question author
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(211.20000000000002, 61%, 30%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EBS%3C/text%3E%3C/svg%3E)
They are running different versions of the .net runtime, and thus different font rendering libraries. The .net 7 version uses more font hints.
note: there were lots of complaints about WCF font rendering (blurry), so it has improved with different versions.
I tried the same thing with .NET 5.0 and have the same issue. Is there anyway to force .NET 4.0? (The project properties only goes down to 5.0)
No. The second sample code is a .net core application and the code will not run on the 4.* runtime.
the first example (really old code), you could update to 4.8, the current supported version and it may behave more like the second
My 20 year long project with thousands of hours invested and two patents becomes infeasible unless I can force rasterization to produce a finite number of glyph images per character. Six would be fine, an unlimited number makes my system infeasible. Any way to overcome this? ---
I started in commercial typesetting where fonts always had hints even for 1000dpi output. When rendering on a low res device, we tended to use vertical fonts with antialiasing.
in the consumer computer world bitmap fonts where used, but scaling was an issue. Once desktop publishing adobe and pdf became the standard. Adobe used outline fonts with hints (like commercial typesetting).
it’s complex and mostly due to licensing costs, TrueType was developed by apple as adobe fonts with antialiasing support. This was later licensed to Microsoft who added ClearText extensions for sub pixel support on lcd screens.
As lcd screen resolution has improved and the use of oled, and micro led, ClearType is basically obsolete and it’s back to improving antialiasing of fonts. Even with white text on a black screen or black text on white, grayscale can be used in the antialiasing.
if you control the application code, you can typically render without hints and antialiasing. but if you controlled the code, you could use bitmap fonts rather than outline or vector.
as we get higher resolution display, hints will normally only be needed with smaller font sizes, but antialiasing seems here to stay. Apple stopped support of disabling antialiasing. Due to some complaints of blurry fonts, I’d expect improvements in this area.
for you code this means a moving target of font glyphs. There are removal of antialiasing algorithms you might want to look at.
if you are familiar with edge detection algorithms, you might use them to find the common core bitmaps of the font glyphs. Actually a scaled pattern match of the core bitmap might work.
This sample has 70 different glyph bitmaps. The system must work with any aribitrary desktop system with no source code available. ---
This answer showed up in my email yet could not be accessed through the web interface.
Bruce (SqlWork.com) answered your question Why do these two projects generate a different number of glyph images per character? on Microsoft Q&A.
They are running different versions of the .net runtime, and thus different font rendering libraries. The .net 7 version uses more font hints. note: there were lots of complaints about WCF font rendering (blurry), so it has improved with different…
There is bug in the forum where posts may be delayed. The issue has improved, but still common.
I think that my post of your comment flushed its buffer.