[Fontconfig] On the order of test and edit elements in a match
Raimund Steger
rs at mytum.de
Mon Jan 28 18:08:47 PST 2013
Akira TAGOH wrote:
> On Tue, Jan 15, 2013 at 9:44 AM, Raimund Steger <rs at mytum.de
> <mailto:rs at mytum.de>> wrote:
>
> Why not...
> Since interleaved <test> and <edit> were previously not even allowed
> by the DTD, it shouldn't have any real impact on existing configs.
> OK it was tolerated by fontconfig but I can't imagine this was
> exploited by anyone...
>
>
> That should be a bug if one expected it. so that should be no problem.
>
> FWIW currently fonts.dtd says:
>
> <!ELEMENT match (test*, edit*)>
>
> just wonder how useful marking "edit" as zero-or-more state is? it
> doesn't take any effects. we can simply ignore it. so shouldn't it be:
>
> <!ELEMENT match (test*, edit+)>
>
> and for this proposal:
>
> <!ELEMENT match (test*, edit+)+>
>
> any comments?
looks good to me.
Raimund
--
Worringer Str 31 Duesseldorf 40211 DE home: <rs at mytum.de>
+49-179-2981632 icq 16845346 work: <rs at interface-ag.de>
More information about the Fontconfig
mailing list