[Fontconfig] strict check for object modification

[Behdad Esfahbod]

On 08/10/2012 05:42 AM, Akira TAGOH wrote:
> Hi,

Hi,

> As fontconfig warns to edit the user-defined object for target="scan"
> right now,

Let me put this into perspective: the reason it warns right now is because
those user-defined objects are NOT saved to the cache and lost, hence the
warning.  If you fix the cache, I'd say you should also remove the warning.
As such, I don't think you should take the warning so much as a design
precedent here.

For the rest of the proposal, I fully agree with everything that Raimund said.
 I'd rather not touch these things unless absolutely necessary.

Cheers,
behdad


> I think it should warns for other cases so that that would
> helps to write sane rules.
> So I want to sort out what objects are allowed to edit and where the
> target is it in. please let me know if something wrong and the
> use-case why it needs. particularly for target="pattern". I'm listing
> as is so far. it's what fontconfig is looking at the objects on
> matching. and for target="scan", I put the same name to
> target="pattern" because any objects not checking for target="pattern"
> isn't needed to cache.
> 
> target="scan":
> family
> style
> slant
> weight
> pixelsize
> spacing
> foundry
> antialias
> width
> file
> rasterizer
> outline
> charset
> lang
> fontversion
> familylang
> stylelang
> fullnamelang
> decorative
> 
> target="pattern":
> family
> style
> slant
> weight
> pixelsize
> spacing
> foundry
> antialias
> width
> file
> rasterizer
> outline
> charset
> lang
> fontversion
> familylang
> stylelang
> fullnamelang
> decorative
> user-defined objects
> 
> target="font":
> antialias
> hinting
> hintstyle
> verticallayout
> autohint
> globaladvance
> rasterizer
> outline
> scalable
> scale
> dpi
> rgba
> minspace
> embolden
> embeddedbitmap
> decorative
> lcdfilter
> charwidth
> charheight
> matrix
> user-defined objects
> 
> Cheers,