We are seeing incorrect font rendering in document previews/thumbnails. The current implementation already includes several font-related mitigations:
- Arial font files are already bundled in the repo
- fonts are copied into the Windows container
- fonts are registered in Windows
- GroupDocs is given explicit font directories
- font-info/PANOSE-based substitution is enabled
Despite all of that, the Arial rendering problem is still reproducible.
Note from the system’s architect:
The overarching topic is we are struggling to get a stable environment using the more common docker images we conventionally use. We moved away from Ubuntu Jammy; at the time it appeared GroupDocs is mainly meant to work with GDI+, and we had memory leakage issues on Linux, seemingly when Libgdiplus was invoked (speculation\correlation on our side but it seemed like it).
Memory usage massively improved when we simply moved to a Windows image. However, Microsoft removed so many features when hardening Windows Server Core that they removed most font support, which we cannot seem to walk back, as detailed in our dev’s notes.
We are actively looking for a solution to work around building our own .Net server on top of a full Windows image. Any guidance would be greatly appreciated.