walt.farrell

I think the suggestion may have been to install the Trial of V2, so you can see. But as it's only a 7-day Trial, and as I don't recall any V2 changes in this area, I don't think I would suggest that.
Your problem is that you have two objects overlapping each other, and so when you try to click on the text at the top of the circle you're selecting the top object, which is the text at the bottom of the circle. Instead of a simple Left-click, try Alt+Left-click.
That's covered in the Help; see the box describing the Modifier Keys: https://affinity.help/publisher/en-US.lproj/pages/ObjectControl/select.html

I would disagree.
That thread is specifically for discussing the Variable Font support coming in the 2.5.0 beta, not for general font-related discussions. It should be restricted to its stated purpose, to help the beta run smoothly.

Thanks for your reply, Walt.
The problem I described happens so irregularly (but too often) that it is even just as problematic to assign myself the task of selecting an image and begin to use the Selection Brish Tool to recreate it on demand. Neither a screen recording nor a screenshot would, in my opinion (as someone with software development experience) shed any more light on an issue that seems to be a bug, not user error. ( I reserve the right to be wrong.)
I will nevertheless post this to the proper section of this forum if I can find it; a bit of a labyrith. 🤨

It imports ok into V1.10.6, not that I will ever use it, it would be like going back to a dial-up modem

For PDF, presumably the same as every other application that supports Variable fonts and PDF: the application must generate a Static subset of the Variable Font and embed that in the PDF. Or it must Convert to Curves.
I have no idea about SVG, except perhaps using Converting to Curves.

That's a bit tricky. It's a system palette on macOS, and if you just select it and try to export it it will exportfrom a macOS Affinity application as an Apple .clr file, and you cannot import .clr files as swatches into the Affinity applications on Windows.
Workaround:
Import it as a document palette into an Affinity document. Then Export it from the Swatches panel as a document palette, which will get you a .afpalette file. Then Import that file as an application palette or document palette into your Windows Affinity application.  
Web Safe Colors.afpalette

Thanks Alfred and Walt. That indeed appears to have been the case, as the original file was from Publisher. I worked around the problem by exporting to a jpeg, which I could  then crop. Looks like I'll have to brush up on that vector crop tool.

Thanks, Walt. I looked at both of these, and there was no joy from what I could see. 
 

For PDF, presumably the same as every other application that supports Variable fonts and PDF: the application must generate a Static subset of the Variable Font and embed that in the PDF. Or it must Convert to Curves.
I have no idea about SVG, except perhaps using Converting to Curves.

Actually currently for SVG we will always convert a variable font to curves.
For PDF as Walt suggests we effectively create a new static font with the attributes applied which we embed within the PDF file. i.e. if you use 5 variations of the same variable font within your document, the PDF will have 5 'different' static fonts embedded.

For SVG you can use variable fonts if the rendering application supports it. ie: you can use variable fonts in most web-browsers available today. For other contexts such as importing into other applications; CAD, 3D tools, cutting tools, etc I suspect most SVG implementations in these contexts won't support variable fonts and converting text to curves will likely produce much better results.

For PDF, presumably the same as every other application that supports Variable fonts and PDF: the application must generate a Static subset of the Variable Font and embed that in the PDF. Or it must Convert to Curves.
I have no idea about SVG, except perhaps using Converting to Curves.

I confirm that EXE versions keep my CSV files in resources folder.
YES!!!

Thank you so far. I'm going to save backup copies regularly again. 

As I understand it, "Missing Characters" means that the characters are not present in the font you've chosen. If you see anything, it should be a substitution from some different font. That may, or may not, matter to you. It's more likely to matter if nothing shows up, but it could matter even if something shows up from a different font  

As I understand it, "Missing Characters" means that the characters are not present in the font you've chosen. If you see anything, it should be a substitution from some different font. That may, or may not, matter to you. It's more likely to matter if nothing shows up, but it could matter even if something shows up from a different font  

The top six characters in the column in the following document.
https://www.unicode.org/charts/PDF/Unicode-15.0/U150-2440.pdf
OCR A extended which I found on this computer recently.
It is not listed on the following page.
https://learn.microsoft.com/en-us/typography/fonts/windows_11_font_list
I have not used this computer much since I got it so I don't know at present how that font arrived on my computer.
William
 
 

No, app just freezes, and there is no response.

Good question. I'm using the default MSIX apps. 

Welcome to the Serif Affinity forums, @DJR.
What you expect is the way that Publisher works, as part of its StudioLink feature. This gives you access, in Publisher, to the Photo Persona of the Photo application, and the Designer Persona of the Designer application. It does not give access to the other Personas of either application.
Photo and Designer do not have the StudioLink feature, and they provide access only to their own set of Personas. 
What you are seeing is normal and correct.

When it starts you'll know because they'll post the details. 

When it starts you'll know because they'll post the details. 

When it starts you'll know because they'll post the details. 

I found the answer. As of Sonoma 14.4, Apple has separated where learned words are stored from where users install additional dictionaries. Perhaps users were breaking things when editing the learned word lists.
There's no change to where additional dictionaries are installed, but the learned word lists are now stored here:
~/Library/Group Containers/group.com.apple.AppleSpell/Library/Spelling/
Apple should have migrated users' learned word lists from ~/Library/Spelling/ instead of forcing us to start from scratch, but perhaps this was just a glitch that affected a small number of users such as myself and @Demonskunk.

To my understanding, yes. There is no guarantee that you would want them in the existing text flow. You could, for example, be inserting one or more pages to hold illustrations.