Wrong rect displaying

[Kozinaka]

There are sample of two similar files with single rect 32x32 px size. Both of them editable by Inkscape and don't change it's behaviour after resaving in it. Right.svg displaying right, Wrong.svg displaying with error (rendered rect is smaller than expected).

Files to test: Samples.zip

[paulushub]

@Kozinaka I have found the source of the issue, but there is no fix needed.

In both conversion (see the Xaml Output), a root clipping region is added due to the defined size of 32 by 32.

    <DrawingGroup.ClipGeometry>
      <RectangleGeometry Rect="0,0,32,32" />
    </DrawingGroup.ClipGeometry>

The clipping region in the output is affecting the "wrong" output file. There is no need for a fix because the conversion settings allow you to turn on or off the root clipping region through a property named IgnoreRootViewbox, which is false by default and is used as such in the WpfSvgTestBox application.
Setting this property to true in the SvgPage.xaml.cs constructor will give the same output for both files.
_wpfSettings.IgnoreRootViewbox = true;

I will update the WpfSvgTestBox application to make the conversion settings available to turn on or off the options and observe the effects on the outputs.

[Kozinaka]

But both files contains one single green rect [0,0,32,32] inside of it in Inkscape and both of it have clip region [0, 0, 32, 32]! Why "wrong" file have something outside [0,0,32,32] when output in SharpVectors?

[paulushub]

Nice observation, thank you. It is a bug in the current SvgNumber.ScientificToDec method.

[paulushub]

Thanks for submitting this issue, I think it have now fixed it in the committed code 5bc4324.
Please verify the fix.

[Kozinaka]

Build is broken :)
..\Source\SharpVectorModel\BasicTypes\SvgTransform.cs:
'SvgNumber.DoubleRegex' is inaccessible due to its protection level

[paulushub]

Sorry, but my local repository is not broken!!!
I will have to commit all changes (many are unfinished work!) to fix this issue, let me review my local sources first, sorry for the inconvenience.

[paulushub]

The review will take time, I think committing the SvgTransform class will fix the problem build.

[paulushub]

Finally committed all the local changes: ad7b893

[Kozinaka]

But now it explodes in runtime when loading some icons. :)
F.e. WpfSvgTestBox crashes when try to load this icon: Front32.zip

[paulushub]

@Kozinaka Sorry, I could not reproduce this latest issue. The attached icon is rendered normally as shown below:

[Kozinaka]

There are needed to add independent number format to decimal.Parse. In Russian format dot is decimal delimiter, not comma.

[paulushub]

@Kozinaka Not having access to Russian Windows (only English and Japanese) but was able to reproduce the parsing error with var culture = CultureInfo.GetCultureInfo("ru-RU");.
Hope the latest commit will now fix the issue.