![]() ![]() recompile from the latest GitHub source code (see Installing Fontforge),.If they can do this, then they will be able to work out where the code is going wrong, and create a fix.Īfter the Pull Request that addresses the issue is merged, you’ll need to get a version after that. With your description the FontForge software developers will try to reproduce the crash. If you have a particular font file (SFD, UFO, OTF, TTF, etc) that triggers the crash, you can either upload it to a new GitHub repository yourself (or Dropbox or another platform) and include a link, or post your email and ask a developer to email you to get a copy privately. If you find FontForge crashing whilst in use, create an issue as above. Sending a good crash report to the FontForge developers really does help them a lot to improve the stability of the program for everybody!ĭon’t feel shy about reporting such issues, because a crash that isn’t reported is a crash that is far less likely to be fixed. The process is just the same for reporting a crash or other kinds of bugs as it is for new features or questions. Please don’t close other people’s issues - ask them to close the issue if it is closed to their satisfaction. You can also place files on your own website or a file sharing service temporarily (such as MegaUpload, DropBox, Google Drive, etc.)įinally, if you do not wish to make your files publicly available, you can provide an email address for a FontForge developer to contact you at to get a private copy of the file. 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. When Things Go Wrong With FontForge Itself ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |