Jump to content

Recommended Posts

Posted

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

  • Staff
Posted

Hi Martin_GER,

Welcome to the forums :)

At the moment the only way to remove this is manually editing the code of the SVG.

Thanks

C

Please tag me using @ in your reply so I can be sure to respond ASAP.

Posted

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

Posted
1 hour ago, Martin_GER said:

The font used is nobody's business.

I suppose it might be the business of the creator of the font, depending on the conditions of the EULA. 😉

Acer XC-895 : Core i5-10400 Hexa-core 2.90 GHz :  32GB RAM : Intel UHD Graphics 630 : Windows 11 Home
Affinity Publisher 2 : Affinity Photo 2 : Affinity Designer 2 : (latest release versions) on desktop and iPad

"Beware of false knowledge, it is more dangerous than ignorance." (GBS)

Posted

Just out of interest, under which circumstances would the inclusion of the serif namespace and font names be a bad thing?
In other words, why would their inclusion be a reason not to use Designer?

Posted
16 minutes ago, Martin_GER said:

Are there plans to remove the font naming in SVG? If so, when approximately?

There should be no naming of the font name anymore after converting to curves. Made a few tests myself. Maybe you should additionally check Export text as curves in the export dialogue.

And if it is so important for you to remove the existence of Serif from the files, there are plenty of editors that allow search and replace inside files without asking. Even the ancient Weaverslave can do this. This action takes a few seconds. So stay a little longer with Affinity please. ;)

------
Windows 10 | i5-8500 CPU | Intel UHD 630 Graphics | 32 GB RAM | Latest Retail and Beta versions of complete Affinity range installed

Posted
1 hour ago, PaulEC said:

I suppose it might be the business of the creator of the font, depending on the conditions of the EULA. 😉

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. 🤨

Posted
1 hour ago, Joachim_L said:

There should be no naming of the font name anymore after converting to curves. Made a few tests myself. Maybe you should additionally check Export text as curves in the export dialogue.

And if it is so important for you to remove the existence of Serif from the files, there are plenty of editors that allow search and replace inside files without asking. Even the ancient Weaverslave can do this. This action takes a few seconds. So stay a little longer with Affinity please. ;)

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.

Posted

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"...

Posted
Just now, Martin_GER said:

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"...

My fault.

 

Posted
2 hours ago, GarryP said:

Just out of interest, under which circumstances would the inclusion of the serif namespace and font names be a bad thing?
In other words, why would their inclusion be a reason not to use Designer?

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?

Posted

So what is the difference to Adobe having their name in the comments? AFAIK there is no option in Illustrator to omit this comment on saving. Is there any technical or other impact this can have? In the end I know what you mean by data minimization, but when I definitely need minimal data I edit the code manually.

------
Windows 10 | i5-8500 CPU | Intel UHD 630 Graphics | 32 GB RAM | Latest Retail and Beta versions of complete Affinity range installed

Posted
14 minutes ago, Joachim_L said:

So what is the difference to Adobe having their name in the comments? AFAIK there is no option in Illustrator to omit this comment on saving. Is there any technical or other impact this can have? In the end I know what you mean by data minimization, but when I definitely need minimal data I edit the code manually.

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.

Posted

Serif places its name once/twice (not everywhere) in line 3 (not in the middle of the code). Removing this snippet is as easy as removing a comment.

------
Windows 10 | i5-8500 CPU | Intel UHD 630 Graphics | 32 GB RAM | Latest Retail and Beta versions of complete Affinity range installed

Posted
1 hour ago, Martin_GER said:

No one mentions the font used on websites or in print publications.

Actually on websites it's usually in the code, and it's often on the copyright page in books.

Acer XC-895 : Core i5-10400 Hexa-core 2.90 GHz :  32GB RAM : Intel UHD Graphics 630 : Windows 11 Home
Affinity Publisher 2 : Affinity Photo 2 : Affinity Designer 2 : (latest release versions) on desktop and iPad

"Beware of false knowledge, it is more dangerous than ignorance." (GBS)

Posted
1 hour ago, Martin_GER said:

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"...

The inclusion of "serif:id="Folder Name" means, I believe, that the xmlns:serif and and its associated URL must remain in the output. Otherwise your SVG file won't be a valid XML document.

-- Walt
Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases
PC:
    Desktop:  Windows 11 Pro 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 

    Laptop:  Windows 11 Pro 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU.
    Laptop 2: Windows 11 Pro 24H2,  16GB memory, Snapdragon(R) X Elite - X1E80100 - Qualcomm(R) Oryon(TM) 12 Core CPU 4.01 GHz, Qualcomm(R) Adreno(TM) X1-85 GPU
iPad:  iPad Pro M1, 12.9": iPadOS 18.3, Apple Pencil 2, Magic Keyboard 
Mac:  2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.0.1

Posted
20 minutes ago, Joachim_L said:

Serif places its name once/twice (not everywhere) in line 3 (not in the middle of the code). Removing this snippet is as easy as removing a comment.

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.

Posted
6 minutes ago, walt.farrell said:

The inclusion of "serif:id="Folder Name" means, I believe, that the xmlns:serif and and its associated URL must remain in the output. Otherwise your SVG file won't be a valid XML document.

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. 

Posted
24 minutes ago, Martin_GER said:

By the way, I'm also tired of this discussion now and prefer to work.

So do I instead of trying being helpful. Good luck. 

------
Windows 10 | i5-8500 CPU | Intel UHD 630 Graphics | 32 GB RAM | Latest Retail and Beta versions of complete Affinity range installed

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.