I tend to agree with giving the parameter as the integer or the float, because, though FT_Library_SetLcdFilterWeights() expects the bytes of the array, fontconfig needs to parse the human-readable string to it. that makes no sense because of using the xml format as the configuration. However I guess the code needs to be updated more since FC_LCD_FILTER accepts the integer only. fontconfig will picks up only the beginning of something looking like an array of the integer or the float (but fontconfig definitely won't deal with it like so). On Mon, Nov 21, 2011 at 10:15 PM, James Cloos <cloos@xxxxxxxxxxx> wrote: > I suspect a list of <double/> or <int/> elements would be better than a <string/>. > > Your example would then be either: > > <match target="font"> > <edit mode="assign" name="lcdfilter"> > <const>lcdcustom</const> > </edit> > </match> > <match target="font"> > <edit mode="assign" name="lcdfiltercustom"> > <double>.0625</double> > <double>.25</double> > <double>.4375</double> > <double>.25</double> > <double>.0625</double> > </edit> > </match> > > or someting like: > > <match target="font"> > <edit mode="assign" name="lcdfilter"> > <const>lcdcustom</const> > </edit> > </match> > <match target="font"> > <edit mode="assign" name="lcdfiltercustom"> > <int>16</int> > <int>64</int> > <int>112</int> > <int>64</int> > <int>16</int> > </edit> > </match> > > if the range is u8. > > The dtd needs to be updated to mention this. > > An lcdheavy conf.avail file also should be part of the changeset. > > Otherwise, I, at least, am very much in favour of this. > > -JimC > -- > James Cloos <cloos@xxxxxxxxxxx> OpenPGP: 1024D/ED7DAEA6 > _______________________________________________ > Fontconfig mailing list > Fontconfig@xxxxxxxxxxxxxxxxxxxxx > http://lists.freedesktop.org/mailman/listinfo/fontconfig > -- Akira TAGOH _______________________________________________ Fontconfig mailing list Fontconfig@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/fontconfig
