With the sample file from bug #436962:
<https://bugs.launchpad.net/inkscape/+bug/436962/+attachment/745677/+files/inkscape.svg>
The symbol definitions themselves are no longer exported (compared to PDF exported with r10196 with 4 red circles there are only two red circles in r10197). The remaining issue of bug #436962 - both red circles are still rendered filled (instead of showing a white fill in the cut-out area) - seems unrelated to the <symbol> problem because the cairo-based export apparently ignores the fill rule which is set on a parent group instead of the red path itself (which isn't an instantiated symbol (<use> element) btw).
Fix in r10197 confirmed with from bug #705345 and bug #485846: /bugs.launchpad .net/inkscape/ +bug/705345/ +attachment/ 1800409/ +files/ test.svg> /bugs.launchpad .net/inkscape/ +bug/485846/ +attachment/ 1040436/ +files/ Addition. svg>
<https:/
<https:/
With the sample file from bug #436962: /bugs.launchpad .net/inkscape/ +bug/436962/ +attachment/ 745677/ +files/ inkscape. svg>
<https:/
The symbol definitions themselves are no longer exported (compared to PDF exported with r10196 with 4 red circles there are only two red circles in r10197). The remaining issue of bug #436962 - both red circles are still rendered filled (instead of showing a white fill in the cut-out area) - seems unrelated to the <symbol> problem because the cairo-based export apparently ignores the fill rule which is set on a parent group instead of the red path itself (which isn't an instantiated symbol (<use> element) btw).