Andreas Scherer

See https://support.blurb.com/hc/en-us/articles/360044955872-Affinity-Publisher-PDF-files

It might also be useful that apps check for external changes and either pop up an indication ad hoc or warn when trying to save the file and suggest to save over or separate.

Or multiple FX like Outline. (Be careful not to un-group, though.)

Use a dotted curve as usual (Affinity V2 is better with its distribution settings; my example comes from V1). Then expand the curve (Layer menu) and swap the fill and outline colors of the "bullets" to make "holes". If need be, the single "curves" layer can be separated into individual elements.

CMIIW, not necessarily with all versions/installations. Here on macOS 13.6.3, imagemagick: stable 7.1.1-25 (bottled) (installed from Homebrew) does not magick identify -list format neither (A)IFF nor ILBM. Also ImageMagick 6.9.11-60 Q16 x86_64 2021-01-25 on Kubuntu 22.04 does not show these for convert display -list format.

On macOS it's SF Pro.

I/we have started using Affinity in 2020, and since then I reported several issues in the “stable” versions of the suite and in some “betas”. I must say that I have experienced a quite satisfying rate of “successes” with my bug reports in the past three years. The output by Serif does feel a bit weird at times, but they are a small shop after all. Just my two cents.

From a quick glance after the upgrade to version 2.3, I can confirm that this issue is fixed. Thanks!

My eyesight has also degraded, so I use my WQHD-Monitor at FullHD only, but otherwise I activate the Screen Magnifier of MacOS, i.e., Ctrl+MouseWheel. This helps quite well.

In case that you want a changed shape, you can use the boolean operator "overlap".

Sure, just not with a brush. As a geometric object, it can be created usong the Pen Tool.

Create your own brush and use it as outline of a circle. Here's a video tutorial:

I used the non-commercial package of the Brill font directly from Brill.com and the Monterchi font for personal/non-commercial use from DaFont.com. (The latter installs as Monterchi Trial.)

I can confirm these by practical example. The Glyph Browser in APub is your friend.

Mac Mini M1 2020 with MacOS Ventura 13.6.1 Affinity 1.10.8 Maybe it is just me, so bear with me. While scrolling in the Document View with the up/down gesture on a Magic Mouse works just as with a third-party mouse with physical scroll wheel, the same is not the case with numeric fields, e.g., in the Transformation panel. With a physical scroll wheel I can hover over such fields and increase/decrease the value by rolling the wheel. With a Magic Mouse, the scrolling gesture does not change the values. Is this normal or a user error?

SVG is a form of XML, so the file content is in "plain text", accessible with your favorite text editor (i.e. Vim). CSS styling is defined in the <style>...</style> group at the start of the SVG file, just as @Palatino shows above. The problem in this particular SVG file is to detect the final styling of the various tags, due to the cascading (that's the 'C' in 'CSS'), i.e. overriding, definitions. The last value for stroke-width for a particular tag takes effect. (In the original SVG file, the stroke-width for, e.g., .st7 is overwritten several times.) Most of what I learned about HTML, CSS, ..., XML, SVG came from the SelfHTML site (in German). However, there are tons of other sources for self-study.

It is. Affinity acknowledges only limited CSS styling in SVG.

That seems to be not quite correct. At least in this situation, CSS styling works. AD just doesn't grok more tricky CSS that other apps (and W3C) accept.

I think the W3C server was temporarily too busy to service your request.

The W3C CSS Validator reports the original SVG/CSS file as valid.

Obviously, AD (1.10.8 on MacOS Ventura 13.6.1 here) doesn't grok this styling: .st3,.st4,.st5,.st6,.st7{fill:none;stroke:#000;stroke-width:.09449;stroke-linecap:round;stroke-linejoin:round;stroke-miterlimit:10} i.e., the comma-separated list of common style tags. If you fully expand the CSS instructions to .st3{fill:none;stroke:#000;stroke-width:.09449;stroke-linecap:round;stroke-linejoin:round;stroke-miterlimit:10} .st4{fill:none;stroke:#000;stroke-width:.23622;stroke-linecap:round;stroke-linejoin:round;stroke-miterlimit:10} .st5{fill:none;stroke:#000;stroke-width:.28346;stroke-linecap:round;stroke-linejoin:round;stroke-miterlimit:10} .st6{fill:none;stroke:#000;stroke-width:.33071;stroke-linecap:round;stroke-linejoin:round;stroke-miterlimit:10} .st7{fill:none;stroke:#000;stroke-width:.37795;stroke-linecap:round;stroke-linejoin:round;stroke-miterlimit:10} then the map looks great in full detail. Pittsburgh.svg

For more than just a few code snippets, I'd suggest some form of Literate Programming (obviously not in APub). Here's an extended collection of C and Pascal programs. 🙂

It's the same with APub 1.10.6. And variables are ignored in AD (also 1.10.6) as soon as one uses Artboards. PS: This is on MacOS 13.6.1 Ventura, btw.

I totally understand that this can easily require more than 8GB RAM/250GB storage. What I don't understand is why you are blaming APub to break the wall, when it – at least from the info above – requires only a fraction of your other main app? I stick with my observation that the OP with the task at hand will most likely not require more than a base configuration on any current Mx-Mac.

Nice comparison: https://www.jetbrains.com/help/idea/prerequisites.html vs https://affinity.help/designer/English.lproj/index.html?page=pages/Appendix/system_requirements.html?title=System requirements 🙃