Lines Matching defs:weak
162 * However, there is no such call and as of Fc 2.11.0 even FcPatternEquals ignores the weak bit.
163 * Currently, the only reliable way of finding the weak bit is by its effect on matching.
164 * The weak bit only affects the matching of FC_FAMILY and FC_POSTSCRIPT_NAME object values.
165 * A element with the weak bit is scored after FC_LANG, without the weak bit is scored before.
166 * Note that the weak bit is stored on the element, not on the value it holds.
205 SkAutoFcPattern weak;
206 FcPatternAddString(weak, object, (const FcChar8*)"nomatchstring");
207 FcPatternAddLangSet(weak, FC_LANG, weakLangSet);
210 FcFontSetAdd(fontSet, weak.release());
216 // If the 'id' was weak, then we should match the pattern with 'matchlang'.
232 /** Removes weak elements from either FC_FAMILY or FC_POSTSCRIPT_NAME objects in the property.
234 * This removes all of the weak elements after the last strong element.
257 // If they were all weak, then leave the pattern alone.
884 // If a family name was specified, assume that any weak matches after the last strong
885 // match are weak (default) and ignore them.
887 // there are many weak but preferred names, followed by defaults.
889 // In aliases, bindings are weak by default, so this is easy and common.
890 // If no family name was specified, we'll probably only get weak matches, but that's ok.