All Media Lab Posted January 4, 2022 Share Posted January 4, 2022 Hi, Test site: https://www.yourweblab.nl/preloader/ HTML validation errors: https://validator.w3.org/nu/?doc=https%3A%2F%2Fwww.yourweblab.nl%2Fpreloader%2F Created a Greensok animation with a SVG I created in Affinity Designer. Errors are caused by the multiple identical ID's Affinity Designer put's in <g id="L1" serif:id="L"> and a !DOCTYPE svg (that I already removed). This happens in all export settings and with the fonts as curves or real fonts. Anyone found a workaround? Cheers, David Quote Link to comment Share on other sites More sharing options...
Alfred Posted January 4, 2022 Share Posted January 4, 2022 1 hour ago, All Media Lab said: Anyone found a workaround? The “workaround” is for the apps to be updated! The !DOCTYPE declaration should be omitted (to avoid problems associated with DTD-based validation) and the coding needs to be revised so that no serif:id attribute errors are generated. All Media Lab 1 Quote Alfred Affinity Designer/Photo/Publisher 2 for Windows • Windows 10 Home/Pro Affinity Designer/Photo/Publisher 2 for iPad • iPadOS 17.4.1 (iPad 7th gen) Link to comment Share on other sites More sharing options...
v_kyr Posted January 4, 2022 Share Posted January 4, 2022 2 hours ago, All Media Lab said: Errors are caused by the multiple identical ID's Affinity Designer put's in Did you named any of the layer groups by yourself? Quote ☛ Affinity Designer 1.10.8 ◆ Affinity Photo 1.10.8 ◆ Affinity Publisher 1.10.8 ◆ OSX El Capitan ☛ Affinity V2.3 apps ◆ MacOS Sonoma 14.2 ◆ iPad OS 17.2 Link to comment Share on other sites More sharing options...
walt.farrell Posted January 4, 2022 Share Posted January 4, 2022 3 hours ago, All Media Lab said: Errors are caused by the multiple identical ID's Affinity Designer put's in That almost sounds like you created multiple SVG exports from Affinity, and then extracted the code from them using a text editor, and modified it a bit, and embedded the modified code into another document. If so, I don't think that's how one should use SVGs, but I'm not an expert. I would have simply referred to the external SVG files from my HTML page, though. Quote -- Walt Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases PC: Desktop: Windows 11 Pro, version 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 Laptop: Windows 11 Pro, version 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU. iPad: iPad Pro M1, 12.9": iPadOS 17.4.1, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sonoma 14.4.1 Link to comment Share on other sites More sharing options...
v_kyr Posted January 4, 2022 Share Posted January 4, 2022 4 hours ago, walt.farrell said: ... using a text editor, and modified it a bit, and embedded the modified code into another document. Honestly the SVG code on the OPs referenced site page looks like this, aka that it is more manually crafted together with some uncommon group name structurings. Quote ☛ Affinity Designer 1.10.8 ◆ Affinity Photo 1.10.8 ◆ Affinity Publisher 1.10.8 ◆ OSX El Capitan ☛ Affinity V2.3 apps ◆ MacOS Sonoma 14.2 ◆ iPad OS 17.2 Link to comment Share on other sites More sharing options...
Recommended Posts
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.