Le jeudi 26 novembre 2009 à 19:44 +0100, Nicolas Mailhot a écrit : > I think you could solve many user pains by > making it possible to use > > <font> > <family>some family name</family> > <style>some style name</style> > <format>some font format name</format> > <unicode> > <min>some-unicode-value</min> > <max>some-greater-unicode-value</max> > <unicode> > <lang>some fontconfig orth id</lang> > </font> … > And it would also be useful to define a <not/> operator, for example > <not> > <lang>ja_Ja</lang> > </not> And just to be 100% clear, in my mind 1. sub-elements of fonts are implicitely OR-ed if they are of the same kind: <font> <family>foo</family> <family>bar</family> <font> applies to all fonts with a family name of foo or bar 2. sub-elements of fonts are implicitely AND-ed if they are of different kinds <font> <family>foo</family> <style>bar</style> <font> applies to fonts only if they have the foo family and the bar style 3. lang and unicode are of the same kind: they are two different ways to specify an unicode range. Maybe it's better to make it explicit and define a <glyph type="unicode-range"/> and <glyph type="lang"/> selector? -- Nicolas Mailhot _______________________________________________ Fontconfig mailing list Fontconfig@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/fontconfig
