He has several how tos on this subject in the tutorials section. A logo svg can only have a single path (created by combining paths in Inkscape.) I have never actually been able to get this to work I don’t know enough about paths, is the expert here. That said, the svg has multiple paths in it. Select the data after ’ ’ and copy that text in to a new svg file. Search for the text ’ instance moduleIdRef=“BoardLogoImageModuleID” ’ fz file which is standard xml so edit the fz file with a text editor. Since I had to do this I figured I document how to do it for other people. Because the source svg is in the fzz file. I recently needed to recover the svg for a board outline with only the fzz file. fzz file Tutorials - Guides - How to's - & Experiences. If anyone has any better workarounds, or spots any similar regressions, please add a comment to this topic so there's a single place to point people to for solutions.Recovering the pcb outline svg from a. In 1.0 you have to break the shape apart (Path > Break Apart), reverse the path in question, then re-combine (Path > Combine). Path > Reverse on a sub-path In 0.92 you could select a single node in a sub-path and use Path > Reverse to reverse just that sub-path.The closest option would be to clone the text object and use a morphology filter on the clone (e.g. Linked Offset applied to a text object No longer works.In 1.0 you need to follow the steps above to convert to a path first, then apply the tool. Inset, Outset, Dynamic Offset applied to a text object In 0.92 you could apply these tools directly to a text object, and it would be implicitly converted to a single path and the tool's effect applied.For 1.0 the only workflow I've found is to use Path > Object to Path, then Object > Ungroup, then Path > Union (or Combine). In 0.92 you could use Path > Union to convert a text object into a single complex path. Convert text object to a single complex path.

I'll report all these as issues when I have the time but, for now, here are the long-winded ways to work around things that used to be very simple in 0.92: It appears that 1.0 has broken several handy tricks or shortcuts when working with paths.

Inkscape text to path externally