Re: Autohinter project for GSoC

> Although I am curious to know— what fraction of the time would you > estimate various stages to take? From what I understand, it sounds > like roughly 50% would involve designing the database and 50% > implementing it, but it’s hard for me to know. My gut feeling says it's about 30% design and

Re: Autohinter project for GSoC

>> As far as I can see it is hard to split the project for adding a >> capability database to the auto-hinter … > > Just speculating here… might it be possible to reduce the workload > by only focussing on a few characters at first? From what I can see > the single worst Latin-script diacritics

Re: Autohinter project for GSoC

> However, I am somewhat worried about the scope of this project. I > am completing a Master’s degree this year, and will not have the > time to complete a full 350 h project; I’m sure I would make good > progress, but suspect the scope of the project might need to be > reduced for it to be

Re: Interested in Font Adjustment project idea for GsoC

Type's scope. Werner > On Sun, Mar 19, 2023 at 2:04 AM Werner LEMBERG wrote: > >> >> Hello Craig, >> >> >> welcome to FreeType! >> >> > The project idea about making a capability database for the >> > auto-hinter cau

Re: permissiveness in FreeType for CFF fonts

> Due to massive spam & cryptomining attacks, some features of > gitlab.freedesktop.org have gotten locked down in recent weeks, and > that includes permission to fork repositories for newly created > users [...] Ah, thanks, I missed the forking limitation. Werner.

Re: permissiveness in FreeType for CFF fonts

> Regarding the access to the repo, the fork button doesn’t seem to be > enabled here https://gitlab.freedesktop.org/freetype/freetype , I > did click on the request access button. Interesting. For me the 'Fork' button works – I'm not aware of restrictions regarding forking... You have to be

Re: permissiveness in FreeType for CFF fonts

> We encountered a few (potentially not fully compliant with the > specification) CFF fonts (i.e. CIDFontType0) that have enough > information to be rendered, but FreeType throws an exception due to > not having both the `head` and the `cmap` tables. Could you provide such a font for testing

Re: Interested in Font Adjustment project idea for GsoC

Hello Craig, welcome to FreeType! > The project idea about making a capability database for the > auto-hinter caught my eye. I have a few questions about it though: > > - What will be the impact of a capabilities database from the > perspective of end users? Particularly, consumers of the

Re: Getting Involved With Freetype

Sorry for the late response. > 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.

Re: (cross-)building ttdebug for windows

> I haven't tried the meson build yet, but I can't see it defining > UNIX anywhere. So likely windows build works, but linux build is > crippled / broken Indeed, `ttdebug` under GNU/Linux built with Meson compiles but doesn't really work because of unwanted input buffering. Patches are

Re: (cross-)building ttdebug for windows

> in Makefile, near line 304: > > Change > > EXTRAFLAGS = $DUNIX $DHAVE_POSIX_TERMIOS > > to > > EXTRAFLAGS = > > that's the line which blindly defines "-DUNIX -DHAVE_POSIX_TERMIOS". > With this simple change, ttdebug cross-builds. Good catch! > I guess nobody have tried cross-compiling the

Re: Getting Involved With Freetype

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

Re: cry for help, FreeType GSoC 2023 Aspirant

Hello Laghav, welcome to FreeType! > I am eager to submit an application for the FreeType GSoC in > 2023. Since I'm new to this, it would be wonderful if someone could > help me get started. > > Of course, I have these doubts, as every other aspirant does. > - What are the best practises to

Fw: How to have sharp fonts?

Can someone help this guy, please? Werner --- Begin Message --- Hello werner I have problem with all linux distros about fonts generally, fonts are very smooth or fuzzy and it hurts my eyes when i read more of the texts , but on windows is very pleasurable to read texts. Is there any

Re: grep -E vs. egrep

> Since neither grep -E nor egrep is portable any more, here is a > patch that does essentially the same test as AC_PROG_EGREP for the > top-level configure. Can be overridden with the EGREP envvar. Applied, thanks! Werner

Re: [GSoC][Introducing Myself]

Hello Kostya, welcome to FreeType! > I just wanted to introduce myself. My name is Kostya Farber. I am a > data engineer, I work at Aviva and am based in London. I have a > strong passion and love for software development and technology in > general. Nice! > I have been learning c for a

Re: FreeType INSTCTRL behavior (Po Lu)

>> It's not a bug but a feature. [...] > > BTW, isn't this an incompatible change to TrueType unilaterally made > by MS? What does Apple's scaler do? I have no idea. Given that (a) Apple doesn't really support hinting anymore in macOS, and (b) there wasn't a problem report in the last ten

Deactivating the mailing list's digest feature

Folks, within the next days we are going to deactivate the list's digest feature. The reason is that it splits threads, which makes it both hard to reply and to follow the order of the replies. A recent example on the `freetype-devel` list is the subject line ``` FreeType INSTCTRL behavior

Deactivating the mailing list's digest feature

Folks, within the next days we are going to deactivate the list's digest feature. The reason is that it splits threads, which makes it both hard to reply and to follow the order of the replies. A recent example on the `freetype-devel` list is the subject line ``` FreeType INSTCTRL behavior

Re: FreeType INSTCTRL behavior (Po Lu)

> Here is what the TrueType reference manual says: [...] Found it! It's not a bug but a feature. From file `src/truetype/ttobjs.c`, lines 1048ff: ``` /* UNDOCUMENTED! The MS rasterizer doesn't allow the following */ /* graphics state variables to be modified by the CVT program. */

Re: FreeType INSTCTRL behavior

> AFAIU, as long as a font does not perform an INSTCTRL which sets > bit 2 in the instruction control, changes made to the graphics state > from the control value program will become the ``default'' state > from which glyphs are instructed. > > However, some CJK fonts perform no INSTCTRL

[ft-announce] Announcing FreeType 2.13.0

FreeType 2.13.0 has been released. It is available from https://savannah.nongnu.org/download/freetype/ or https://sourceforge.net/projects/freetype/files/ The latter site also holds older versions of the FreeType library. See below for the relevant snippet from the CHANGES file.

Announcing FreeType 2.13.0

FreeType 2.13.0 has been released. It is available from https://savannah.nongnu.org/download/freetype/ or https://sourceforge.net/projects/freetype/files/ The latter site also holds older versions of the FreeType library. See below for the relevant snippet from the CHANGES file.

Announcing FreeType 2.13.0

FreeType 2.13.0 has been released. It is available from https://savannah.nongnu.org/download/freetype/ or https://sourceforge.net/projects/freetype/files/ The latter site also holds older versions of the FreeType library. See below for the relevant snippet from the CHANGES file.

Re: GSoC 2023

s emitted by `ftbench` could be post-processed by a script to produce a nice-looking HTML page. Another possibility is to modify the `ftbench` program directly to emit HTML code. Difficulty: medium. Size: 175h/350h. Requirements: C, Unix build tools, meson, HTML. Potential mentors: Werner Lemberg, Alexei Podtelezhnikov, Toshiya Suzuki (FreeType).

Re: Regarding guidance for contribution to your organisation

Hello Shivansh, > I am very much excited for open source contributions and would love > to work with you but could you please tell me how to get started? https://freetype.org/gsoc.html Werner

Re: License question

> Hello, I was wondering if instead of a disclaimer, a way to download the > license to view it is alright? If you are developing an online application, this should be fine – I guess you provide a button that says 'disclaimer', and if the user presses this button, the license gets downloaded and

Re: More axes for `ftmulti`

> Now you can collapse all these cases using: > axis = event. key - ‘A’; > Or > axis = event.key - ‘a’; Good idea, now committed. > And make an alphabetical list on the screen. > A axis > B axis > C axis Already done :-) Werner

Re: More axes for `ftmulti`

>> ? display this help screen > And F1 as commonly used for help [...] Thanks. Here is what I've now committed, and I'm quite satisfied now. ``` F1, ? display this help screen q, ESC quit ftmulti F2 toggle axis grouping F3 toggle outline hinting F4

Re: More axes for `ftmulti`

> OK, will go for the first scheme. Here are the new key assignments that I currently have (but not yet committed), please comment. ``` ? display this help screen q, ESC quit ftmulti F1 toggle axis grouping F2 toggle anti-aliasing F3 toggle

Re: More axes for `ftmulti`

> Can I suggest a more intuitive scheme? > A,a to control axis 1 > B,b to control axis 2 > C,c to control axis 3 > and so on. > > This is also easier to process. Or this > 1,! to control axis 1 > 2,@ to control axis 2 > but this is only for US keyboard OK, will go for the first scheme.

More axes for `ftmulti`

I've just increased the number of handled axes in `ftmulti` from 6 to 15. Due to the new support of the 'avar' version 2 OpenType extension it is expected that the number of axes in many fonts will increase (after this extension gets accepted in the OpenType standard) because adding 'virtual

GSoC 2023

Folks, I've just applied to GSoC 2023. Let's see whether we will be accepted this year. I've also updated our GSoC pages at https://freetype.org/gsoc.html – if you have ideas for improvements or new projects, please write to this list! Werner

Re: [HarfBuzz] Getting character bitmap

> I suggest that you go through the FreeType tutorial at > > https://freetype.org/freetype2/docs/tutorial/index.html > > It comes with examples that you can adapt to your needs. I forgot to mention the FreeType demo programs. You can download a tarball from

Re: [HarfBuzz] Getting character bitmap

> Any help is appreciated in code below to convert the glyph to 0 > and 1 based bitmap as shown at the end. >> >> Since I'm new to C, I don't quite know how to connect function >> Char_Index output to FT_Bitmap. I'm new to reading such >> C documentation. I suggest that you go through the

Re: Variable Fonts

> Now that I researched more, I cannot cache glyphs of different > variations inside the cache manager unless I provide a different > face_id for each variation and only then my system works correctly. > To be honest this is a flaw in the cache subsystem of the freetype > library. Please open

Re: Variable fonts

> I am currently using the multiple master feature of freetype library > to support the variable fonts. There is an issue that I am facing > currently. For an example, consider that I am making letter "A" > bold using the weight axis but in my system I want to be able to > uniquely identify

Re: [TrueType] CVT table is not correctly clone for composite fonts

> I tried to report this issue by protal today, but probably > without success. The issue is not visible in the list of issues. I > don't know what is wrong. I guess you've tried the FreeType mirror at github. This doesn't work; I have disabled issues there (hopefully!) so that reports

Re: ftjam issue in ArchLinux

Hello David, > I had a lot of trouble getting FT-Jam to do a proper incremental > build on my ArchLinux system. [...] We no longer support Jam. It wasn't used by any active developer (and probably by nobody else), and the changes specific to `ftjam` are ancient, unmaintained, and very

Re: How to access to an AxisRecord in the Stat table?

> Hi,I there a way to get the AxisRecord in the Stat table? No, there isn't: FreeType has no extra support for this table. You would have to load the table with `FT_Load_Sfnt_Table` and parse it by yourself. Note, however, that I strongly recommend to *not* doing this. You should rather use

no PRs at FreeType's github mirror

FYI: I've just activated Setting Moderation Options Limit to repository collaborators which is, according to https://stackoverflow.com/questions/27957454/how-to-disable-pull-requests-in-github, the only possibility to disable PRs on github. Note that this setting is limited to six

Re: Free type2 software font engine

> Good afternoon, I was wondering were could I find the “free type 2 > software font engine “ it for a 2010 bmw 535 I thanks It's not clear to me how you actually want to use a font rendering engine for a BMW car, but here is a link to our website. https://freetype.org Werner

Re: Nice way to do Bold

> I have pushed a new method to do terminal bold that seems to work > well. See screenshot. > > Basically I use a brightness of 7/8th for non-bold, and for bold a 1 > pixel shadow of 13/16ths brightness. After hours of experimentation > that seems to provide the best results for all fonts. > >

Re: FreeType and Go/Golang

> I want/need to learn golang, so one thing that comes to mind is to try > rewriting some of freetype2-demo in go. [...] Please tell us if you find bugs :-) Werner

Re: non-antialiased font configuration

> Ed, I have added monochrome support to cooledit. > See the 'devel' branch: > https://github.com/paulsheer/cooledit/tree/devel Nice! Werner

Re: non-antialiased font configuration

> Great info thanks again Werner, keeping this in the realm of > freetype/ftview, what option might I pass to ftview to get the > ftview rendering looking like the amber terminal in the attachment? > Again, I'm trying to avoid antialiasing, particularly in small > console/monospaced consoles.

Re: non-antialiased font configuration

> Thanks Werner,  the images were embedded/smime, Nope, see https://lists.gnu.org/archive/html/freetype/2022-10/msg5.html > but they're attached to this email. Now they are, thanks. > Fonts are antialiased in ftview, is there a way to have ftview > render fonts without antialiasing?

Re: non-antialiased font configuration

> I've spent about a day trying to make the lower window (Kubuntu > 22.04 KDE), look like the top window (Kubuntu 18.04 KDE) [...] First of all, there were no images attached to your mail. Secondly, you are barking up the wrong tree, sorry: FreeType is a very low-level library, and all the

improved (SVG) images for 'FreeType Glyph Conventions'

As the title says. Enjoy! Werner

improved (SVG) images for 'FreeType Glyph Conventions'

As the title says. Enjoy! Werner

Re: [GSoC] Status of font-rs port

Hello Anurag, what's the current state of your project? Please tell us what's going on :-) Werner

Re: glyph diagram

An answer to a mail from the distant past :-) >> Could you contribute SVG images of the two graphics to >> FreeType? > > OK, I have changed the output format of my script to SVG (Cairo > seems to do a good job of SVG output, at least in this case), and > split out the two diagrams into

GSoC project `ftinspect` now in master

Folks, I've just merged Charlie's GSoC project `ftinspect` into master – enjoy! `ftinspect` is a essentially a Qt-based application that merges and extends the functionality of most FreeType demo programs (`ftview`, `ftgrid`, etc.) Charlie did a great job, and it was a pleasure to work with

GSoC project `ftinspect` now in master

Folks, I've just merged Charlie's GSoC project `ftinspect` into master – enjoy! `ftinspect` is a essentially a Qt-based application that merges and extends the functionality of most FreeType demo programs (`ftview`, `ftgrid`, etc.) Charlie did a great job, and it was a pleasure to work with

Re: Some error after compiled and linked to the freetype file on M1 Macbook :(

> I successfully configured the file and include it normally. There > is no error after linking, but when I have FT_Init_FreeType, it > gives me Undefined symbols for architecture arm64: > > "_FT_Init_FreeType", referenced from: > main in main-a92552.o > ld: symbol(s) not found for

Re: [PATCH] fix null pointer offset UB

> The previous patch missed some cases which for some reason my test > program wasn't hitting - apologies for that. Here is the corrected > patch. [...] Thanks! Please file a merge request at https://gitlab.freedesktop.org/freetype/freetype/-/merge_requests together with an improved

Re: 回复：This is freetype sourcecode from TSIT(I made many improvements)

> 1, Check in the latest freetype code (release or dev version ? I >will use release first). Don't use the last release first. Please start immediately with the head of FreeType's current git repository. This simplifies both rebasing and merging. Werner

Re: Google's NotoColorEmoji-Regular.ttf not rending

> Thanks, ftview is a great help. However it does not display > NotoColorEmoji-Regular.ttf Well, this font contains a 'COLR' v1 table, which `ftview` doesn't support – you have to render the layers by yourself.[*] Note that 'COLR' v1 support in FreeType is not complete yet (but Dominik is

Re: Google's NotoColorEmoji-Regular.ttf not rending

> > I have had great success with Google's older NotoColorEmoji.ttf and > NotoEmoji-Regular.ttf released by Google in 2019. > > However they have since updated their fonts. They now have a font > NotoColorEmoji-Regular.ttf They have? Looking at

Re: [GSoC] Status of font-rs port

> 1 and 2 have been fixed, but monochrome output still crashes ftgrid > for the dense rasterizer A good start would be a backtrace... Werner

Re: Possible Wording Error on FreeType Tutorial 1 Page

> Please refer to your following page: FreeType Tutorial / > I > > Please confirm/explain if the part that I’ve highlighted in Red > below, is in error? Please don't use colours for markings. On 'freetype@nongnu.org' we encourage

Re: Subpixel offset for glyphs rendering

> I'm using FT_Outline_Translate(), though I'm still not sure if I'm > supposed to pass the translation vector as pixels or font units. Pixels (in 26.6 format), since `FT_Load_Glyph` converts the glyph from the font space to the user device space (except if you specify `FT_LOAD_NO_SCALE`). >

Re: Subpixel offset for glyphs rendering

Sorry for the late reply. > Is there a way to make freetype rasterize a glyph offsetted by a > certain amount of pixels? Should I use the FT_Set_Transform() API, > in particular the delta parameter, before calling FT_Render_Glyph()? Yes, this should work. Werner

Re: Compiling old version (2.6.5) of FreeType

> I checked out the VER-2-6-5 tag on the repo and ran autogen.sh, > which resulted in: [...] This is OK. > Simply running configure and make seemed to work but then there were > compilation errors in freetype-demos. > > I tried checking out a ~2016 commit but couldn't really get it to >

Re: Help with SDF Rendering

>I would like to get more information on how to set the spread for >SDF Rendering. [...] Please have a look at the `ftsdf` demo program, which should answer (most of) your questions. https://gitlab.freedesktop.org/freetype/freetype-demos/-/blob/master/src/ftsdf.c Werner

Re: Infinality removal (Freetype-devel Digest, Vol 299, Issue 99)

> I hope some of these knowledge in comments, probably also alsewhere, > are copied over before its removal. There are people who want to > know what Apple/MS does which FreeType does not (yet), even if those > corners are practically unimportant and/or nobody is doing anything > about it any

Re: Free type "invalid glyphs"

> I have found that FT_Get_Char_Index will explicitly return 0 for > 'missing' characters which is the fix for the issue. I am using > FT_Load_Char but should that really return a valid construct for an > "invalid" character? Why not? Go to a Wikipedia site for a foreign language without

Re: Free type "invalid glyphs"

> For various fonts it will present the rectangle for a glyph I assume > it couldn't determine, but there are no errors and even the data is > still filled in. If you use OpenType fonts it is common that characters that have no corresponding glyphs are mapped to glyph index 0, the '.notdef'

Re: Font rendering question - unifont-14.0.04.ttf

> Over at Python Pillow, we've had a user raise an issue about the way > that Pillow is rendering characters from unifont-14.0.04.ttf - > https://github.com/python-pillow/Pillow/issues/6421. I took a look, > and concluded that Pillow wasn't doing anything special, but just > showing what our

Re: FT_Get_Advance() too slow?

> I finally spent enough time on it to have a clue. I wrote up my > findings in a document: > > https://docs.google.com/document/d/1wskYbA-czBt57oH9gEuGf3sWbTx7bfOiEIcDs36-heo Thanks a lot, this is very good reading. Werner

Re: Qt5 versions in Ubuntu

>> I've updated my openSUSE box, and I'm now using Qt 5.15.2.  >> However, I still ask you to adjust the meson and cmake build files >> to request a proper minimum version for Qt (this is not urgent, >> though). > > This has been already done on the `gsoc-2022-chariri-3` branch, see > commit

Re: compilation of `ftinspect` fails

>> Please add code to the meson and cmake build files that checks whether >> the Qt version you need is installed. If not, make them exit with an >> error. After you are done you can revert the work-around for older >> Qt5 versions :-) > > OK, I've push the reverted version with check

Re: Use features of `ttfautohintGUI` in `ftinspect`

> As for adaptive layout... I'll set it as a future task with a lower > priority. I can think of a few locations in the current `ftinspect` > version where adaptive layout can be used, but honestly, it may cost > some tome to learn how to implement this in Qt. OK, no problem. > BTW, I

Use features of `ttfautohintGUI` in `ftinspect`

Charlie, I suggest that you have a look at my `ttfautohintGUI` program; it provides two features that might be interesting for `ftinspect` (what the program actually does is not of importance). http://freetype.org/ttfautohint/ * It uses tooltips for documentation. * It provides two

Re: compilation of `ftinspect` fails

> I've pushed a commit supporting older Qt versions (5.12). Thanks, but see below. > But I still recommend upgrading Qt since honestly, I don't know if > I'll accidentally use more new features. On the other hand, Qt 5 > has ceased to release new "minor" versions, so 5.15 would be the > last,

compilation of `ftinspect` fails

[branch gsoc-2022-chariri-2, commit 6a264517f2] Compilation of 'freetype2-demos' using ``` meson setup meson-build meson compile -C meson-build ``` fails with ``` ../src/ftinspect/widgets/tripletselector.cpp: In member function ‘void TripletSelector::repopulateFonts()’:

Re: FT_Get_Advance() too slow?

Hello Behdad, > Any chance the one-line patch below can be applied? I've applied this as commit b98dd169a1823485e35b3007ce707a6712dcd5251 on May 25th; see https://lists.nongnu.org/archive/html/freetype-devel/2022-05/msg4.html Werner

Re: Commit 4f3a8eba3a doesn't compile

> Two ideas: And another one :-) * Assuming that you don't intend to implement a waterfall in vertical mode, the 'Vertical' checkbox should be greyed out if the 'Waterfall' checkbox is set. Werner

Re: Commit 4f3a8eba3a doesn't compile

[please write to freetype-devel by default] > The CharMap combobox issue is solved, please give it a test. The > Singular Tab's positioning is fixed as well. Works now, thanks! > As for the red square in the waterfall view, I think it is the > intended behavior because under extreme small

Re: Commit 4f3a8eba3a doesn't compile

>> However, reloading of font should not reset the charmap option >> either if the charmaps didn't change during the reloading >> (e.g. when the font isn't changed actually). Line 116, 120~124 and >> 144~145 are exactly intended to avoid unexpected resetting, but it >> don't seem to work. I will

Re: Commit 4f3a8eba3a doesn't compile

> However, what do you prefer for me to prioritize? > > * The Hinting Comperator Tab (= `ftdiff`), a new tab parallel to >singular grid view and continuous view > * The long, long list of TODO features, and the most wanted >features seem to be the zoom/scroll/drag operations and >

Re: Commit 4f3a8eba3a doesn't compile

[commit 94bfed42b7200a9f9ed7437158f5f0332370037c] >> No, it's not – at least not while using my dark KDE theme. The >> input field is disabled, yes, but the text colour of 'The quick >> ...' doesn't change to gray, contrary to other grayed-out items >> like the 'Next Named Instance' box. > > I

Re: Commit 4f3a8eba3a doesn't compile

>> * What do you think about greying out the text box (holding 'The >> quick...') if the 'Text Source' field is not 'Text String'? > > This is already been done and works at my side. Is it not greying > out under Linux? No, it's not – at least not while using my dark KDE theme. The input field

Re: Font-rs GSoC Phase 1 update

> 1. Code: > > I have pushed the ported font-rs code to the "gsoc-anurag-2022" branch > (here: > https://gitlab.freedesktop.org/freetype/freetype/-/tree/gsoc-anurag-2022) Great, thanks! > 2. Documentation: > > I have started work on improving the existing documentation > (explanations for

Re: can't use meson for 'freetype-demos'

>> Everything's look OK. Note that the GNU mailing list server has >> hiccups quite frequently, which means some delay until e-mails are >> eventually delivered. > > The current problem is that, I keep receiving in my Inbox E-Mails > that I sent. Is this expected behavior? By default,

Re: can't use meson for 'freetype-demos'

>> Interesting. Why is that? FreeType only produces 256 levels of >> opacity; I thought it would be straightforward to map them >> inversely. > > The point was, should I inverse all the colors on the canvas as well > (grid, outline, points, point numbers)? If not so (only bitmap & > grid),

Re: can't use meson for 'freetype-demos'

> You mean click onto a single glyph to get info about it? Yes. > If so, this would involve mapping from clicked position to glyph > index - exactly what I didn't consider when implementing "Continuous > View", which is quite embarrassing. :-) For me it feels natural to click on a glyph to

Re: can't use meson for 'freetype-demos'

> I'm currently working on non-outline glyphs support. I'll post the > roadmap later on the GitLab Issue (after taking consideration of > points mentioned in your feedback). Thanks. >> * I use a dark KDE theme; `ftinspect` looks as shown in the >> attached image. As you can see, the

Re: can't use meson for 'freetype-demos'

>> Thanks. Now I get the following error: > > Now fixed. MSVC is way too lenient... :-) However, it would be nice if you could ensure that both clang and gcc builds work fine. The next bunch of errors is below. Werner

Re: can't use meson for 'freetype-demos'

> Fixed in branch `gsoc-2022-chariri-2`. Using a new branch because I > rebased to the new `master` which may mess up with the commit hashes > in the report. Thanks. Now I get the following error: FAILED: src/ftinspect/ftinspect.p/meson-generated_moc_ttsettingscomboboxmodel.cpp.o ccache

can't use meson for 'freetype-demos'

[274212df5a7812430010e9cc67cbb2a4f5203288, gsoc-2022-chariri] Hello Charlie, I've just tried ``` meson setup meson-build ``` and I got src/ftinspect/meson.build:49:2: ERROR: File widgets/glyphcontinuous.hpp does not exist. Please fix. Werner

Re: [PATCH] Clarify documentation for FT_Stream_IoFunc

> [...] I fell into this trap myself, and while it seems dumb, > searching online found a few unresolved threads from other poor > souls who were having this exact issue in the past. [...] Thanks for the patch; I've added it to the repository (with very minor amendments). Werner

Re: [URGENT] Confirmation of Fixes for CVE's in 2.12.1

> I arrived at the conclusion because I was expecting a mention of > CVE-2022-27404 and the change that fixed it. [...] Thanks for the explanation. We usually don't mention CVEs in release messages except someone explicitly tells us. In most cases CVEs are made public much later than the

Re: [URGENT] Confirmation of Fixes for CVE's in 2.12.1

> Can you confirm which or if all the following fixes/patches/commits > that resolve issues and CVE's below are incorporate into latest > available version, 2.12.1? [...] They are, because... > I see that version 2.12.1 was release 1 month ago [...] and that > these fixes were committed 3

Re: [GSoC] Merge Request - to master or to a seperate branch?

> If I set up a parallel personal branch (gsoc-2022-chariri) > cherry-picking my contributions, while new commits are still being > merged, would it work? The parallel branch would serve the purpose > of proof-of-contribution and it will be a logically organized single > line. This should work.

Re: [GSoC] Merge Request - to master or to a seperate branch?

>> If you want to submit general changes to FreeType please submit >> MRs. However, for your ftinspect GSoC stuff you should push to a >> personal branch (or even branches, if necessary) of the upstream >> repositories *without* MRs. In your personal branch(es) you can go >> wild – no need for

Re: [GSoC] Merge Request - to master or to a seperate branch?

Hello Charlie, > I'm going to make my first commit for the GSoC. Great! > It's a minor change - CMakeLists.txt for ftinspect. I've pushed the > commit to my forked repo on the GitLab. However, where should I > create MR to? Should I create a MR from my master branch to the > master branch

Re: Add support for FT_Face cloning

Hello Tayyab, > I have been following for quite some time but David is not > responding. It feels to me like he is not interested in this > proposal. David, while still being the spiritus rector behind the scenes, is not a regular contributor to FreeType any more due to time constraints; if

Re: Update on community bonding phase: Plans on refactoring ftinspect

>> [Charlie, please subscribe to the 'freetype-devel' mailing list.] > > But I can still manage my subscription status on > https://lists.nongnu.org/ . Is my subscription accidentally dropped? Ah, your status was 'moderated' for some unknown reason. Now fixed. >> I don't know. What would be

Re: Update on community bonding phase: Plans on refactoring ftinspect

[Charlie, please subscribe to the 'freetype-devel' mailing list.] > Therefore, I'm planning to bring forward the next phase (Part 2 in > the timeline), which is refactoring the current base. OK. > * You're creating a lot of "extra" widgets by inheriting the >original widgets in Qt. This

<    1   2   3   4   5   6   7   8   9   10   >