Initial Work on W3C Test Compliance

[erdomke]

Sorry for the huge pull request, but I have been working through a number of changes and refactorings to get better support for a number of the W3C tests. I thought that these changes would prove useful in the main branch. Part of the huge commit is including many of the W3C tests in the code so that other developers can work through them as well.

[Emasoft]

Wow! I'm looking forward to test it.

[tebjan]

never be sorry for a huge pull request 👍 i'll integrate it and give it a test run. implementing the official SVG test framework is a big step forward. thank you very much again!

[erdomke]

I thought that the project built when I submitted the pull request.
However, if it doesn't, a delete of the defunct "SvgReader" class out of
the c# project should due the trick...

On Mon, Aug 4, 2014 at 10:55 AM, Tebjan Halm notifications@github.com
wrote:

Merged #90 #90.

—
Reply to this email directly or view it on GitHub
#90 (comment).

[Emasoft]

I've just tried to compile it, and SvgReader class is not the only problem.
There are some added references to the PresentationCore assembly (a WPF component) that give me errors (in example: you are using System.Windows.Media.FontFamily instead of System.Drawing.FontFamily). This is because WPF is not portable and it is not supported by Mono. I think we should make a portable library and avoid using proprietary frameworks like WPF.

[erdomke]

I can see about removing that. It is only referenced by the SvgUnit class
right now. I am using it to try and accurately get the x-height of a font.
WPF provides this quite easily, but I am not quite certain how to handle
it in System.Drawing. Just the same, it should be straightforward to
change.

On Mon, Aug 4, 2014 at 12:17 PM, Emasoft notifications@github.com wrote:

I've just tried to compile it, and SvgReader class is not the only problem.
There are some added references to the PresentationCore assembly (a WPF
component) that give me errors (in example: you are using
System.Windows.Media.FontFamily instead of System.Drawing.FontFamily). This
is because WPF is not portable and it is not supported by Mono. I think we
should make a portable library and avoid using proprietary frameworks like
WPF.

—
Reply to this email directly or view it on GitHub
#90 (comment).

[Emasoft]

Mmhh.. it seems that the x-height property is not included in System.Drawing. We should calculate that ourselves. But I can't find a documented algorithm to do it.

[erdomke]

My initial thought is just to use 0.5 of the em calculation for the ex
value. While not ideal, I would think that this should be close enough for
most situations. At the very least, it beats not supporting the unit at
all.

On Mon, Aug 4, 2014 at 3:17 PM, Emasoft notifications@github.com wrote:

Mmhh.. it seems that the x-height property is not included in
System.Drawing. We should calculate that ourselves. But I can't find a
documented algorithm to do it.

—
Reply to this email directly or view it on GitHub
#90 (comment).