Re: [fontforge-users] Composite small caps

[Gé v. G. <gev...@gm...>]

Sorry, I didn’t make myself clear. I’ll try again:

1. This – I think – might be a solution for the difficulties you’re facing
right now:
If the script works well with the combining marks, you could copy all your
spacing marks into their slots, then let the script do the work (after you
have adjusted their horizontal positioning…).

2. This is a separate rambling about the use of fonts:
I’m wondering if it’s worth-while to put much attention on composite
glyphs, when applications are using them less and less.
Maybe Thales Martins can shed more light on this matter?


On Mon, Aug 24, 2026 at 1:04 PM Mauro Sacchetto via fontforge-users <
fon...@li...> wrote:

>
> "Precomposing" with anchors speeds up the work considerably, although -
> as always - manual adjustments are required.
>
> Sure, it's possible to copy the accents one by one over the base glyphs,
> but using references and anchors, if any changes are made, they're
> immediately reflected everywhere without having to edit the glyphs one
> by one again. It's a bit like working with styles in a word processor...
> I placed 40 acute accents, then I changed their design and now I must
> redo everything by hand. ):
>
> FF actually doesn't do a bad job; it recognizes .cap marks and - this is
> the mysterious problem - almost all .sc marks.As I've already written,
> grave.sc, acute.sc, and macron.sc, unlike all the others, don't.
>
> That's why this seems like a small bug to me.
>
>
>
> Il 24/08/26 12:39, Gé van Gasteren ha scritto:
> > On Sun, Aug 23, 2026 at 10:44 PM Mauro Sacchetto via fontforge-users
> > <fon...@li...> wrote:
> >
> >
> >     If I set PreferSpacingAccents to OFF, it always uses only modifier
> >     glyphs
> >
> >
> > Sorry for interrupting with a silly idea maybe, but I wonder why you
> > can’t copy the accents you made into the composing counterparts?
> > You’d have to adjust their horizontal positions individually, I guess
> > – is that the main disadvantage?
> >
> > Composing diacritical marks are the future; the precomposed characters
> > are kept for backward compatibility of course, but these days, apps
> > don’t use them as much.
> >