Re: [fontforge-users] Composite small caps

[Thales M. <tha...@gm...>]

So there's your solution. Delete the glyphs that you don't want(move them
to the background layer and delete the foreground), generate all the
composites and then move the marks back to the foreground.

On Sun, Aug 23, 2026, 06:31 Mauro Sacchetto <mau...@gm...>
wrote:

> Oh, now I see! I can unlink or modify manually the components to
> preserve the references.
>
> I've done other experiments, but I can't make sense of them.
>
> I create a font from scratch (actually, I copied and pasted it from
> somewhere else), but without adding the modifiers and combining marks;
> in PUA, I insert the various marks (grave, acute, circumflex, ...,
> macron, and breve) in the appropriate slots. The .sc glyphs are composed
> correctly with the .sc marks.
>
> Then I insert the modifiers and combining marks; at this point,
> grave.sc, breve.sc, and macron.sc are no longer recognized (all the
> others are), and the glyphs in these three cases are composed using the
> modifier (gravecomb, etc.) and not the .sc mark.
>
> I don't understand anything...
>
>
>
>
>
>
>
> Il 23/08/26 01:08, Thales Martins ha scritto:
> > The algorithms are very probably full of bugs, far from perfect. Fonts
> > still need a lot of manual work to be produced. You should look into
> > Python's FontForge class documentation to see if it's possible to do
> > that by code. Chat bots can help you with that. I, every now and then,
> > use scripts to do those kinds of things, like when I wrote a script
> > that adds composite characters to the same kerning class as their main
> > reference. The scripting in FontForge's class is limited though; there
> > are some things it won't do, like manipulating splines.
> >
> > The procedure that I suggested involves using Edit -> Unlink
> > Reference. You go and change the spline of the accent that is being
> > used by the automatic composite generation to what you want, generate
> > the composites, unlink the references to those generated glyphs, and
> > change the accent glyph back to what it was before. The downside is
> > that, like this, you will end up with accented glyphs containing only
> > splines instead of the references to the fundamental glyphs. Using
> > layers also helps, as you can store the original splines in a
> > different layer, and there are commands to transfer a whole layer to
> > another, for all glyphs at the same time.
> >
> > On Sat, Aug 22, 2026 at 8:10 PM Mauro Sacchetto
> > <mau...@gm...> wrote:
> >
> >     Another issue: I create omacron.sc <http://omacron.sc>, FF ignores
> >     macron.sc <http://macron.sc> and uses the
> >     modifier (U-02c9).
> >
> >     However, in GPOS lookup "Mark" the correct glyph appears with
> >     macron.sc <http://macron.sc>.
> >
> >     Since this behavior only occurs with macron, grave, and acute,
> >     couldn't
> >     it be a small bug in the automatic glyph construction mechanisms?
> >
> >     >
> >     >
> >     > _______________________________________________
> >     > fontforge-users mailing list
> >     > fon...@li...
> >     > https://lists.sourceforge.net/lists/listinfo/fontforge-users
> >     > http://fontforge.10959.n7.nabble.com/User-f8781.html
> >
>
>
> _______________________________________________
> fontforge-users mailing list
> fon...@li...
> https://lists.sourceforge.net/lists/listinfo/fontforge-users
> http://fontforge.10959.n7.nabble.com/User-f8781.html