![]() ![]() If you can make a file that is small and only contains what is needed to reproduce the issue, please fork the fontforge repo and add these files to /tests/fonts and submit a pull request. To reproduce the issue, it can helpful to share with the developer community the files you are working with. You can drag and drop screenshots or other images directly into the issue page to include them.Īn easy way to report issues is to record a screencast video in which you explain in a narrated voiceover the things you are interested in as they happen, and then upload it to YouTube and include a link to your video. what happens, step by step, to produce the issue.your FontForge version and where you got it from,.If it was not already reported, open up a new issue.Ĭlick the green “New Issue” button, and then describe your question, what you did to trigger a crash, or your idea for an improvement.If it was, and your issue is related but not quite the same, please comment on that issue with your own take on the issue. In the Issues search box, try searching for similar issues, to see if the problem you are facing was reported already.Visit the FontForge GitHub Issue Tracker and sign in to GitHub (after creating an account, if you don’t have one yet).Revisit the issue and add a comment with the link to the FreedomSponsors issue page, with a personal note that you’re offering a paid bounty for this issue to be closed.Visit FreedomSponsors and sponsor a new issue, using the URL you copied earlier.Copy the URL of the issue to the clipboard. Create a FontForge issue describing what you want to be changed (see below).When other font editors with similar comprehensive features cost hundreds of US dollars, if we each pay a similar amount to FontForge developers to get our most annoying bugs fixed, FontForge will become better and better.įreedomSponsors offers a transparent system for paying FontForge developers to fix issues you care about in a timely fashion. This might be a surprise, but it is both possible and encouraged to pay for FontForge support when things go wrong. To learn more about GitHub, check out Good Resources for Learning Git and GitHub. The FontForge team uses GitHub Issues to discuss problems, errors and ideas for improvements, and then someone develops a solution and proposes it as a Pull Request. On Mac, I have some alignement issue (centred is not really vertically centred)Īnd there is a huge difference in font size between OSX and Windows and probably rendering as well.When Things Go Wrong With FontForge Itself On Windows, there was some user reporting some bogus font display which was fixed using TextLayout instead of Graphics::drawText (don’t ask me why) In some recent project, we have tried to move to Juce own stuff (createSystemTypefaceFor) So far at UVI, we have been using Vinnie Falcon FreeType engine and it works great.Īt the time we used that because there was no Typeface::createSystemTypefaceFor so this was the only solution besides serialising font on the system which was clearly not very practical (even though we first started doing that in first Juce based products). I wonder how Juce users are displaying custom fonts in a cross platform way. Currently the font system is quite different between Windows and Mac.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |