![]() Questions about SimConnect can be posted in the SimConnect forum.Īny other question that is not specific to an aspect of development or tool can be posted in the General chat forum.īy following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.Questions about terrain design can be posted in the FS2020 terrain design forum.Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course. Questions about airport design can be posted in the FS2020 airport design forum.Questions about aircraft design can be posted in the Aircraft design forum.Either post them in the subforum of the modelling tool you use or in the general forum if they are general. Questions about making 3D assets can be posted in the 3D asset design forum.Tag FS2020 specific questions with the MSFS2020 tag.So therefore we would like to ask you all to use the following guidelines when posting your questions: But having all questions about FS2020 in one forum becomes a bit messy. In short, the missing information is the scope of the problem, and once determined the scope of the problem may point away from changes to FontForge itself.Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. We know it's not a hard fix because all that needs to happen is that GSUB kerning entries be ignored. And if the answer points to a particular library or combination of libraries the same question arises: Why not file a bug against the relevant library instead? But in that case we still have a documentation issue - how do we indicate to a user what the flag is for. This problem could easily be wider than GIMP, of course. I cringe at the thought of later projects needing to add support for a GSUB/ kern combination because FontForge made it easy to build such fonts and they wound up in distributions that are unable or uninterested in rebuilding them. New and unusual font format combinations shouldn't be added into the ecosystem lightly - they tend to stick around. ![]() more Tutorial: Kerning - Auto-Kern FontforgeSocials: Join. Indeed, I would much rather spend time digging around a bit in their code than making an exception in FontForge. 107 4.4K views 2 years ago - FontForge - Tutorial: Kerning - Auto-Kern Fontforge Socials. I would not work on such a fix before pursuing the problem with the GIMP development team. However, suppose that GIMP were the only such application we knew of, and the proposal were to add a "GIMP compatibility" checkbox. ![]() GIMP is confirmed as one such application, and is significant enough an application that it might warrant a workaround. (Note: if the proposal is to output non- kern GPOS tables, before going forward we would need to confirm that it's just kern and not any GPOS tables that cause the problem.) For whatever reason will not use an embedded kern table if GPOS kerning is present.Does not use GPOS (for kerning, at least), and.Therefore what this flag would address is software that: Roughly speaking, the way to be FreeType 2 compatible is to be more or less a TrueType font. It can't really be a flag for FreeType 2 compatibility because FreeType 2 doesn't include either GSUB or GPOS processing. ![]() 's conception of its purpose hasn't yet accounted for all of the evidence. Still, I've been looking at this issue so I'll summarize what further information I would need in order to go ahead with a fix.Īny added flag should have an associated explanation for when it might be used. I'm just a random person doing stuff here for a bit, so it's not really my business what and how issues should be addressed. Any tool that can use GSUB but not GPOS is at least a little suspicious. One could be added of course, but that would raise the question of its intended purpose. So I take it that what you're looking for is a set of options that will output GSUB and kern but not GPOS. That deleting the GPOS data with an external application seems to work suggests that the kern contains the correct data.įrom a glance at tottf.c it appears that when OpenType is left unchecked the GSUB/GPOS/GDEF tables will not be output. Together this means that in outputting both kern and GPOS tables FontForge is behaving as documented for these options. This may confuse other applications though." It may not be set in conjunction with the Apple checkbox. If you want to include both 'GPOS' and old-style 'kern' tables set this check box. Many applications still don't support 'GPOS' kerning. Also, the tooltext for the "Old style 'kern'" says: The kern table is (one hopes) being output because it has been specified here.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |