Re: [fontforge-users] Composite small caps

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

"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.
>
> _______________________________________________
> fontforge-users mailing list
> fon...@li...
> https://lists.sourceforge.net/lists/listinfo/fontforge-users
> http://fontforge.10959.n7.nabble.com/User-f8781.html

-- 
Mauro Sacchetto
Santa Croce 1332a
30135 Venezia (VE)
tel.: 041 722938
cell.: 348 9690575
e-mail: mau...@ic...