freetype-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Getting Involved With Freetype


From: James Hu
Subject: Re: Getting Involved With Freetype
Date: Sun, 5 Mar 2023 23:14:57 -0500

Hi,
Over the past few days I was successfully able to clone/make both the freetype and freetype-demo libraries. I've also read through the documentation on the site and feel I have a rudimentary understanding of fonts, glyphs, and other font rendering concepts. However, I don't feel ready to tackle any of the issues linked here. I do have experience with C, but it was relatively basic compared to what I've been looking at in the freetype repo. In other words, I haven't worked with codebases this large or complex. Would this present a major problem if I want to get involved with FreeType? In other words, is there room for learning more about C and font rendering as I go?

Currently, I am most interested in the VFLib. From my understanding, TFM stores font information, while the actual glyphs are stored in PK/GF as bitmaps/raster formats. So is the overall goal of the VFLib project then to add TFM and PK/GF rendering capability directly into FreeType? (Ideally without using VFLib as a dependency) In addition, is it possible to check if the original GSOC 2018 contributor, Parth Wazurkar, is still following the mailing list (it seems that email addresses are hidden on the mailing list)? If not, is there an alternate way to get into contact with them?

Thanks

On Fri, Mar 3, 2023 at 4:58 AM Werner LEMBERG <wl@gnu.org> wrote:

Hello James,


welcome to FreeType – please subscribe to the mailing list!

> I've noticed that a few other open source organizations tag
> "beginner-friendly" bugs on their repo pages as a way to help new
> contributors get used to the code base.  I haven't noticed any of
> these labels on FreeType's GitLab page.  Is there a list of bugs
> that might be suitable for a beginner to tackle?

Unfortunately, no.  FreeType is an old and mature library that
normally doesn't have small open tasks since we are going to fix them
rather quickly.  Looking into the issues, however, maybe you can try
one of the following.

* This report

    https://gitlab.freedesktop.org/freetype/freetype/-/issues/1129

  qualifies as something not too difficult to do, provided you have
  experience with Windows programming.

* A non-programming task is

    https://gitlab.freedesktop.org/freetype/freetype/-/issues/1163

* Some `git bisect` training together with step-wise debugging could be

    https://gitlab.freedesktop.org/freetype/freetype/-/issues/1005

  to identify the problem (and eventually fix it).

* Maybe

    https://gitlab.freedesktop.org/freetype/freetype/-/issues/1004

  is also not too difficult.


     Werner

reply via email to

[Prev in Thread] Current Thread [Next in Thread]