[Fontconfig] On the order of test and edit elements in a match

Akira TAGOH akira at tagoh.org
Thu Jan 24 18:46:13 PST 2013


On Tue, Jan 15, 2013 at 9:44 AM, Raimund Steger <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?


>
> Raimund
>
>
> --
> Worringer Str 31 Duesseldorf 40211 DE  home: <rs at mytum.de>
> +49-179-2981632 icq 16845346           work: <rs at interface-ag.de>
>
> ______________________________**_________________
> Fontconfig mailing list
> Fontconfig at lists.freedesktop.**org <Fontconfig at lists.freedesktop.org>
> http://lists.freedesktop.org/**mailman/listinfo/fontconfig<http://lists.freedesktop.org/mailman/listinfo/fontconfig>
>



-- 
Akira TAGOH
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/fontconfig/attachments/20130125/c25a1200/attachment-0001.html>


More information about the Fontconfig mailing list