try with fresh export from figma

Author: knzai

_posts/2024-09-01-svg-ccc.md

@@ -49,7 +49,7 @@ This is the result I ended up on for this header, originally (I ended up using a
 ![SVG: SVG cross-codec-compilation - SVG](/assets/img/posts/svg-ccc/composite.svg)
 
 ```xml
-<svg xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" fill="none" viewBox="0 0 918 560">
+<svg xmlns="http://www.w3.org/2000/svg" fill="none" viewBox="0 0 918 560">
   <g clip-path="url(#a)">
     <path fill="url(#b)" d="M-134 0H918v560H-134z"/>
     <g filter="url(#c)" style="mix-blend-mode:overlay">
@@ -67,9 +67,9 @@ This is the result I ended up on for this header, originally (I ended up using a
       <rect width="918" height="560" fill="#fff" rx="7"/>
     </clipPath>
     <pattern id="c" width="1" height="1" patternContentUnits="objectBoundingBox">
-      <use xlink:href="#d" transform="matrix(.00204 0 0 .00184 -.013 -.03)"/>
+      <use href="#d" transform="matrix(.00204 0 0 .00184 -.013 -.03)"/>
     </pattern>
-    <image id="d" xlink:href="data:image/png;base64,...
+    <image id="d" href="data:image/avif;base64,...
 ```
 
 Tools like Figma usually don't support AVIF yet, so you may have to do something like export the SVG with just the raw png in the svg, delete out it's href and replace it with the avif data. This can get a little cumbersome, and it may just be worth it using a reasonably well encoding AVIF.  Hopefully the tooling starts supporting AVIF more broadly and it will get a little simpler.