Interesting. It’s what I thought.
And this is a good bug report for GF.
Your SVG uses the
<use> tag, which is used to reuse a defined shape elsewhere in the SVG.
Pixelmator embeds your bitmap as a defined
<image>, and then uses
<use> to position it.
It seems GF incorrectly ignores attributes on the
<use> tag and instead just uses the attributes on the
The easiest fix, is to not use the symbol definitions and the
<use> tag. For your workflow, I’m not sure if you can get Pixelmator to export differently. If you screenshot your export settings or whatever, maybe I can give you some guidance.
But at least for this file, I fixed it manually for you, in two ways.
The first, I just removed the
<use> and put the
<image> directly where the
The second, I put the
y attributes from the
<use> on the
<image> in the definition. This actually renders incorrectly everywhere else, but worked correctly in the GFUI, which is maybe further evidence the GFUI has a bug.
@GF Staff folks… if there’s a better way to file a proper bug like this, let me know.
Anyway @designatednerd, here’s two fixed version for you, I’d recommend the first:
pollo_coaster 2-fixed.svg.zip (10.3 KB)
pollo_coaster 2-fixed but also broken.svg.zip (10.3 KB)