Error parsing SVG path with optimized ARC parameters

[rgchris]

The following SVG shape stops parsing at the double zero (permitted in this case as these values represent boolean values, not scalars):

<svg viewBox="0,0,100,75" width="100" height="75" xmlns="http://www.w3.org/2000/svg" fill-rule="evenodd" clip-rule="evenodd" stroke-linejoin="round" stroke-miterlimit="2">
  <path d="
      M30 65
      h-11
      v-55
      h21
      l10 38
      l10-38
      h21
      v55
      h-11
      v-36.5
      c0-.5-.5-1-.5-1
      c-.5-.5-1-.5-1.5-.5
      c-.5 0-1 0-1.5.5
      c0 .5-.5.5-.5 1
      l-9 36.5
      h-14
      l-9-36.5
      c-.5-1-1-1.5-2.5-1.5
      a2 2 0 00-1 .5
      c-.5.5-.5.5-.5 1
      v36.5
      z
" fill="black"/>
</svg>

Changing the line a2 2 0 00-1 .5 to a2 2 0 0 0-1 .5 allows the shape to load correctly hinting at this being a parsing error.

[Sean P]

Hi rgchris,

Thank you very much for your detailed report. I can reproduce the issue here (along with the change fixing it) and will get it passed on to development.

[numma_cway]

This is a duplicate of this one:

.

[Patrick Connor]

We have made fixes/improvements to this area (Error parsing SVG path with optimized ARC parameters) of the program in the latest release.

The fixes and how to update are described in these forum posts.

• Affinity Designer 1.8.4 for Windows            ( Microsoft Store and Affinity Store )
• Affinity Designer 1.8.4 for macOS               ( Mac App Store and Affinity Store )
• Affinity Designer 1.8.4 for iOS                      ( Apple iPad Store )
   
• Affinity Photo 1.8.4 for Windows                ( Microsoft Store and Affinity Store )
• Affinity Photo 1.8.4 for macOS                   ( Mac App Store and Affinity Store )
• Affinity Photo 1.8.4 for iOS                          ( Apple iPad Store )
    
• Affinity Publisher 1.8.4 for Windows         ( Microsoft Store and Affinity Store )
• Affinity Publisher 1.8.4 for macOS            ( Mac App Store and Affinity Store )

We would appreciate you checking that this issue has now been resolved for you,