Re: [fontforge-users] Composite small caps

[Mauro S. <mau...@ic...>]

Thanks for the Python tip; I'll take my time.


One last, crucial question.

When creating composite glyphs, FF uses Modifiers, not Combinings. But 
the former shouldn't contain anchors, unlike the latter. For example, 
agrave is automatically composed of a + gravemodifier (uni02cb) and not 
a + gravecomb (uni0300). This defeats a more precise positioning 
calculated with anchors.

Is there a way to set FF to automatically use Combinings and not Modifiers?





Il 26/08/26 16:42, Thales Martins ha scritto:
> Do you know any programming at all?
>
> Take a look at this documentation: 
> https://fontforge.org/docs/scripting/python/fontforge.html
>
> As you can see, there are methods like "glyph.anchorPoints" and 
> "glyph.addReference" that allow you to look at an anchor, create a 
> proper transformation matrix and position the reference to create your 
> composites.
>
> Learning Python with chatbots is really fun. Programming in general 
> can be really fun but it can also be really annoying and drive you 
> crazy. The fun part is when you're developing the ideas, testing, and 
> it's all working, and the project is moving forward. The really 
> annoying part is when the project gets really really complex, that 
> every now and then a bug arises, and you get stuck for 3 weeks turning 
> everything upside down and can't for the love of God make it work. And 
> just so you know, so you can make an informed decision, the fun part 
> is usually 10% of the time, while the annoying, crazy driving part, is 
> the other 90%.
>
> On Tue, Aug 25, 2026 at 3:10 PM Mauro Sacchetto via fontforge-users 
> <fon...@li...> wrote:
>
>
>     I've never used Python scripts; I'm curious where I could find some
>     exa
>