When we convert Brother Scan'n'Cut FCM files to SVG we have found that the SVG version is reduced in size compared to the original when we cut using the SVG. This can be shown when we "round trip" the SVG back in to Canvas. I attach a comparison of screen grabs from canvas showing the different sizes (please note that there is a different vertical offset on the mat, but they are different sizes).

The orignal file, called Divider_3.fcm may still be on your server, but if not I can send you a copy.

Were you aware of a problem, is there anything that can be done to fix it?

The problem is that the SVG reader in ScanNCut Canvas is not implemented correctly according to the SVG specifications. There are also a number of others applications that do not read in SVG files at the correct size.

The SVG reader in ScanNCut canvas is using 96 DPI (Dots per Inch) instead of 90 DPI. This means that the imported SVG file will be smaller than it actually is. 90/96 = 0.9375

When an SVG file is saved in Inkscape, it correctly imports the SVG file. They seem to believe that all files saved in Inkscape will be 90 DPI, which is not true, they can be saved in millimetres.

Hi IanI have been doing some research into this and have come to similar conclusion. The SVG standard seems to deliberately avoid specifying a DPI or conversion between physical units, like mm, and its "User Units" or pixels, so I am not sure that Scan'n'Cut is doing it wrong, more like it is open to interpretation/implementation. Apparently the CSS standard is 96 DPI, though I haven't verified that, and I have also read that Inkscape default DPI was changed from 90 to 96dpi in version 0.92 (I am still using 0.91). There is some info about that here on the Inkscape wiki http://wiki.inkscape.org/wiki/index.php/Units_In_Inkscape#Inkscape_.26_Units

What I have found is that I can hack the files to add in a scaling transform that will give the correct results. If I alter the "transform" element to the path attribute with a scale to compensate for 90 to 96 dpi it works, so change the two "1"s in the matrix to 1.06666669. This...

<path id="A01" transform="matrix(1.06666669, 0, 0, 1.06666669, 178.866141732283, 54.9035433070866)"From what you say I can understand why you have used 90dpi on your converter, but if the Scan'n'Cut, CSS, and now the latest version of Inkscape are all using 96dpi as some kind of defacto standard it might be time to consider changing, or putting in an option.

Thank you for you work on this converter and making it available to the community!

There is fix. By defining and using real world units for the height and width, and setting the viewBox to those values, it is the correct scale in 0.91, 0.92, ScanNCut Canvas, Make the Cut, Sure Cuts a Lot, Silhouette Studio, Cricut Design Space, and my own Cutter Controller.