Martin_GER

This is a feature that should not be missing in a professional image editing program. It is not possible that many important metadata are lost when editing with Affinity Photo. The fact that this feature is not already on the developers' to-do list, but only might be included in future ones is poor. Unfortunately another reason to stick to Adobe Photoshop for a long time to come.

Thanks Walt for the hint, but I've been using SVG for a long time, which works fine and is valid on the web without this code snippet.

No, it's not. At least not for us, who produce dozens of SVG on some days. You stay with Affinity and I'll go back to the hated Adobe, because obviously I'm no better with Affinity Designer and Photoshop either. On the contrary: I even miss some professional features painfully in Affinity. By the way, I'm also tired of this discussion now and prefer to work.

If I expect nothing else from Adobe than that they put their company name everywhere, then I would at least expect better from Affinity. In any case, a comment can be removed easier and faster than snippets in the middle of the code.

It is a completely unnecessary information, which font I used in my design. Sometimes this should also remain a secret, so that the design cannot be copied so easily. Also which software I use is nobody's business. Above all I want code without superfluous content. Ever heard of the principle of data minimization / economy?

Spotted the "problem" with the font name: When converting to paths, I packed the individual curves into a folder and named it after the font. This was implemented in SVG as <g id="Folder Name" serif:id="Folder Name"...

Thanks for the hint: I can't reproduce my described problem with new files myself anymore. But before I had definitely converted all texts to curves and also switched off the option "Export text as curves". For new files, the SVG export now works without implementation of the font name (even a licensed font). To edit exported SVG files again is out of question for me because of time constraints. Also f… Adobe has to write its name in the SVG - but at least in the comment and not in the code.

That well may be. However, it is certainly not Affinity's business to enforce assumed copyrights of any creators. Especially not if they are not subject to any copyright, like the fonts I use in my designs (Frutiger was just an example). No one mentions the font used on websites or in print publications. Digital rights management works completely different. 🤨

Hello, Callum, thank you for the quick response. Unfortunately, this is a reason for me not to use Affinity Designer anymore. So with a heavy heart I have to go back to Illustrator to create SVGs. Are there plans to remove the font naming in SVG? If so, when approximately? Thanks in advance for the info. Martin

Hello, when exporting a file to SVG format, the source code of the SVG includes 1.) the font used (<g id="Frutiger semi-bold) serif:id="Frutiger semi-bold") 2) a reference to Serif (xmlns:serif="http://www.serif.com/") The font is even named, even though the font was completely converted into paths before! The font used is nobody's business. I also consider it technically unnecessary. I also don't want a reference to the software used. How can this be prevented without having to edit the file afterwards? Thanks in advance for your help. Martin