psfufo2ttf can create Unicode Variation Sequencen (UVS) cmaps from either org.sil.variationSequences (in the lib.plist) or the org.sil.uvs keys in .glif files, but will process only one of these sets of data -- with a preference for the data in lib.plist.
My guess is that the .glif data is incorrect and should be removed, which can easily be done by:
cd font-padauk/sources/masters
psfremovegliflibkeys Padauk-Regular.ufo/ org.sil.uvs
psfremovegliflibkeys Padauk-SemiBold.ufo/ org.sil.uvs
Then, by renaming org.sil.variationSequences to public.unicodeVariationSequences, the UFOs can be compiled to TTF by non-SIL tools as well as by psfufo2ttf
psfufo2ttf
can create Unicode Variation Sequencen (UVS) cmaps from eitherorg.sil.variationSequences
(in thelib.plist
) or theorg.sil.uvs
keys in.glif
files, but will process only one of these sets of data -- with a preference for the data inlib.plist
.As discussed in https://github.com/silnrsi/pysilfont/issues/84#issuecomment-1712228282, Padauk has both
org.sil.variationSequences
(in thelib.plist
) andorg.sil.uvs
(in a number of.glif
files), and the data is different.My guess is that the
.glif
data is incorrect and should be removed, which can easily be done by:Then, by renaming
org.sil.variationSequences
topublic.unicodeVariationSequences
, the UFOs can be compiled to TTF by non-SIL tools as well as bypsfufo2ttf