LostInTranslation

Update: I tried converting my font to TTF and to my surprise it actually worked. With this one installed, the umlauts are showing up again, I really hope this was it and I don't have to discover any downside later on. On a different note: File incompatibilities inside a major version are an absolute no-no and Affinity should be ashamed of themselves. Otherwise I just would have installed the last working version of Publisher and everything would have been fine.

All the best!

well, since this subforum is called "V2 Bugs found on Windows" I'll let you take a wild guess ...

Thank you, at least it's known already. Unfortunately I had already saved the new file in 2.6.3. so I can't re-install an older version. Seems I have to do it all over again, not happy!

This is a catastrophe, I made a couple of packaging designs for a client. I have to make changes, but for some reason Umlauts are no longer shown. There are just blank spaces instead. Yes, the font does have umlauts and when I try it in Affinity V1, everything works, as well as in any other application. If I open a new file in V2, just type some text with umlauts in the desired font, they don't show up. Maybe important: The specific font I need is in the format PFM/PFB, not TTF or OTF Unortunately I can't go back and use V1 because everything was made in V2 already. And it worked about 2 versions back in Publisher.

Thanks to everybody for their insights. Right now the AI-feature seems to be a better (or at least faster) selection brush, but still needs work most of the time. I have no problem with that, but on the other hand it is not a "must have" for me. I wanted to try it on my iPad, but apparently I "do not have Apple silicon" so it does not work. I will update on PC soon and then hopefully get to try it myself.

Hi, i have not upgraded to 2.6 yet, I always wait until my current projects are finished in case something is not working. But i have watched a couple of videos. It seems that the new Subject/Object Selection Tool is not getting great results most of the time. Affinity stretches, that all processing is done locally and none of my artwork is used for training. Does this also mean that we are stuck with what it is now? How could it get better? Would Affinity need to train another, better model?

Wow, that is smart, thank you!

Thank you, if everything else fails I will do it like that. But I would much prefer to only have ONE main part and just the locations being variable. If at any point the "main logo" should change or be needed in another color, I would not want to change every single layer.

Thank you, but how can I "automatically" export all states while keeping the state's name as filename just like with slices? I made a quick demo but don't find any option to do that. Tha main goal is to NOT have to export every single layer by hand and in multiple formats.

Please explain or can you provide a link to a tutorial? I'd like it to be "automated" and the exported files need to have the layer names.

I do, but can't use that. Each locationname needs to be individually kerned and due to very different lenghts I sometimes need to adjust the font-size too.

Hi, I am currently creating a logo for a company with a large number of locations, around 350 or so. I need to export a different version for each of them, where the "base" of the logo stays the same, but with the respective location added. I have illustrated it below, the red part stays the same, the green part should change with each iteration while exporting the whole logo. The layer of each location will be named "company_locationname" and this should be the filename on export. I have played around with the slice tool in the export persona, watched a couple of videos but can't figure it out for the life of me. Is this even possible? If so, how? Thanks for any help!

Perfect, thank you very much, it works.

Hi, in a catalog, I have a number of diagrams. Visually, they look like they should. Preflight keeps telling me, that they are ever so slightly non-proportionally scaled. I tried fixing it manually, but it is guesswork to find the specific numbers to fix the 0.1%. Is there an easy fix for this? These are placed images, NOT image frames. Example: