On Fri, Jan 11, 2013 at 12:28 PM, Behdad Esfahbod <behdad@xxxxxxxxxx> wrote:
I don't think we should validate. Just pass data around. Should we call itOT_FEATURES or more generically FONT_FEATURES? If and when we add AAT support
(or the existing Graphite support), those backends will use these same tags as
far as HarfBuzz API is concerned. CSS calls them font-features, that's why I
chose that.
Aha. that sounds good then. let's call it FONT_FEATURES.
Right. That's why I've been putting this off. I need to extend thePangoAttribute framework to allow "reducing" a set of attributes to a single
value, in this case, add the lists of features together or something.
Right. that too.
Ok, I'll push it up. Any name preference? FC_PRGNAME is fine? ShouldDefaultSubstitute try to populate that using system-specific heuristics?
(/proc/self/exe or something)
Yep sounds good to me.
behdad
Akira TAGOH
_______________________________________________ Fontconfig mailing list Fontconfig@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/fontconfig