So, I'm looking for an alternative way to preview the fonts after are compiled or converted with fontforge. exe file.īut will last an eternity to load the Windows\Fonts\ directory if you are working in a institute that is making paleography and fonts. Simple font viewer with interactive editor.Ĭan load fonts from a directory, i.e. If it does not need to remain text, you can merge the shapes too.There are a lot of programs on for listing fonts and there are less that can display a single font file as 'fontview' from Windows but only shows the font glyph if is installed in /Windows/Fonts/ and not for other fonts such as vectorial scalar. So until Affinity supports variable fonts, the easiest workaround is to use the OTF fonts. Otherwise you end up with a bunch of non-standard franken-fonts. They have made the decision to not modify valid fonts to work around various app limitations. There are a number of other issues where the rendering in apps does not work properly.Īnd that includes Adopey, Apple, and others. Overlaps is not the only rendering issue they have to contend with. That does not include "remove overlaps" (fonttools can do it but it is not 100%). Google Fonts takes the original source files and uses their own tools to build the fonts for GF. So the fonts they provide in their repo generally do not have overlaps in the TTF files. Typically when font developers export their fonts from their GlyphsApp, or FontLab source files, they select "Remove Overlaps" as one of the export parameters. So apps which support variable fonts have already dealt with this issue. To support variable fonts, text rendering engines must support properly rendering overlaps. OpenType-PS (.otf) fonts do not use components so they will not have overlaps (for now). In Affinity suite, especially Photo, and also in the stable 2.10.x version of Gimp for example the issue is clearly visible, and with different weights also manifests on other glyphs.Īnother workaround is to use the OTF fonts if available. The issue is about 50% less visible and only manifests on "h". From joe_l's message above I suspect Adobe suite might also handle it fine.Ĭhromium or SumatraPDF also render it incorrectly, but less so than Affinity suite. I found two applications that seem to handle it with zero issues: Firefox (or at least its pdf viewer) and the development (2.99.x) version of Gimp. Rendering issues with this font seem to be really common, so I tested various applications to find any differences. png it is slightly less visible than in application (and dependent on DPI), but still present. I don't use Adobe Reader, but I assume they would not have this issue. When exporting to pdf the rendering issue gets delegated to the pdf rendering application. I see some faults while changing the zoom, but there are no faults in the exported PDF. I wonder if that has something to do with the rendering issues in Affinity suite. Blender has trouble identifying which side of a component boundary is inside and which is outside (that is why parts of the glyphs are hollow). I'm adding it because it shows the components that the glyph is made from (I don't have a specialized application for that) - the rendering issue in Publisher clearly happens in a place where several components overlap. Here's a screenshot from a completely different application, Blender, in which this font is even more broken. With various font sizes and weights it happens with other glyphs as well, although usually not as obviously: Here's an image from Publisher showing a problem with "h". However it took me several hours of work spread over several days (due to communication with the font author and a Google github person) to diagnose the issue and find this workaround and I don't think it's reasonable to expect users to do this. I don't know if their decision is reasonable, but it means that this is not going away.Ĭurrent workaround: Individual font repositories in the Google fonts github seem to contain static versions of the fonts different than the Google fonts website, and at least with Comfortaa it does not have this issue. I first thought this was a bug in Google fonts, but they assured me that this is deliberate, it's how they will continue to generate their static fonts and any applications are supposed to render it correctly. The font I'm using as an example is Comfortaa, but unfortunately this seems to happen in (static versions of) various Google fonts. Affinity applications seem to not handle this correctly, which sometimes creates subpixel errors (see image below). Problem: Some fonts contain glyphs made of several components that overlap. I first noticed it in Publisher, so I'm putting it here. Application: All latest Affinity suite applications afaik.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |