SVG import issues

[tommyemo]

after importing an SVG, objects lose their position in an artboard and there is no way that I've found to fix it, even just importing an object's PathData doesn't work. I've attached a couple images here and the SVGs are here: https://drive.google.com/open?id=0B8ZeRR-6g4JbdzNidHJQcUphQVU

One quick note is that these SVGs are made in Figma. Not sure if that's a factor but I've heard of similar issues from AI users as well.

[romannurik]

Will look into it ASAP thanks!

On Wed, Feb 1, 2017, 5:54 PM TWellington [email protected] wrote:

after importing an SVG, objects lose their position in an artboard and there is no way that I've found to fix it, even just importing an object's PathData doesn't work. I've attached a couple images here and the SVGs are here: https://drive.google.com/open?id=0B8ZeRR-6g4JbdzNidHJQcUphQVU

One quick note is that these SVGs are made in Figma. Not sure if that's a factor but I've heard of similar issues from AI users as well. [image: screen shot 2017-02-01 at 1 50 06 pm] https://cloud.githubusercontent.com/assets/7970209/22529934/1b786dd4-e89f-11e6-9818-8b9bf5da00a7.png [image: screen shot 2017-02-01 at 4 32 50 pm] https://cloud.githubusercontent.com/assets/7970209/22529935/1b7a09b4-e89f-11e6-85dc-f08f2fbd4f1e.png

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/romannurik/AndroidIconAnimator/issues/100, or mute the thread https://github.com/notifications/unsubscribe-auth/AAGHO0qe6sXEe6gHvGyUMtLAN1byjhkCks5rYQ0ugaJpZM4L0f1S .

[alexjlockwood]

It's because the SVG contains <defs> declarations, which aren't currently supported (although #64 begins to add initial support for them).

Until <defs> are correctly parsed and imported, a work around is to manipulate the SVG file by hand by copying/pasting the paths out of the <defs> and hard coding them directly into the nodes which reference them.

[tommyemo]

@alexjlockwood I'm not seeing any in the path data, and I already tried copy + pasting the path data into the tool.

[alexjlockwood]

So as an example, your stroke.svg file could be simplified to this:

<svg xmlns="http://www.w3.org/2000/svg"
  viewBox="0 0 24 24"
  xmlns:xlink="http://www.w3.org/1999/xlink">
  <g transform="translate(45 71)">
    <path fill="#C4C4C4"
      transform="translate(-43 -69)"
      d="M17.16 10.98c.04-.32.07-.64.07-.98 0-.34-.03-.66-.07-.98l2.1-1.65c.2-.15.25-.42.13-.64l-2-3.46c-.15-.22-.4-.3-.64-.22l-2.5 1c-.5-.4-1.07-.73-1.68-.98L12.2.42c-.03-.24-.24-.42-.5-.42h-4c-.24 0-.45.18-.48.42l-.38 2.65c-.6.25-1.17.6-1.7.98l-2.48-1c-.23-.1-.5 0-.6.22l-2 3.46c-.14.22-.08.5.1.64L2.3 9.02c-.04.32-.07.65-.07.98 0 .33.03.66.07.98L.2 12.63c-.2.15-.25.42-.13.64l2 3.46c.12.22.4.3.6.22l2.5-1c.52.4 1.08.73 1.7.98l.37 2.65c.03.24.24.42.5.42h4c.24 0 .45-.18.48-.42l.38-2.65c.6-.25 1.17-.6 1.7-.98l2.48 1c.23.1.5 0 .6-.22l2-3.46c.13-.22.08-.5-.1-.64l-2.12-1.65zM9.73 13.5c-1.93 0-3.5-1.57-3.5-3.5s1.57-3.5 3.5-3.5 3.5 1.57 3.5 3.5-1.57 3.5-3.5 3.5z" />
  </g>
</svg>

It looks like Figma adds a bunch of stuff that AndroidIconAnimator's SVG parsing engine doesn't yet support. Not only is it using <defs>s and <use> but it's also rendering the icon in a weirdly indirect way by applying a clip mask on a grey background rectangle or something. Bleh.

@romannurik This would be a good SVG to save for later when later revisiting SVG import improvements. Although TBH I'm not sure how I would solve this right now. :/

[tommyemo]

that rectangle was placed by me in an attempt to fix the issue, I can remove it and reupload the SVGs tho