Hangman

To be honest I've not successfully reproduced the masks I had created on those other layers, and I'm time pressed to spend more time on it given the Export persona gives me the end result I need.  I felt it was important to thank / acknowledge the trouble you went to though.  I do need to work out how I did that in the first place.  I've been using AD for about a year now and still find things like this to be counterintuitive.  I sort of expect to be able to select a rectangular region, and then create a mask for selected layers to that rectangle.  
Somehow my brain just isn't getting it right now.

It appears in the Help file linked above...
"As defined by the language-specific hyphenation dictionary, words have pre-defined hyphenation points at which hyphenation will occur. Each hyphenation point has a value weighting associated with it. For example, the hyphenation point in the middle of the word yellow (to produce the word "yel-low") has a score value of 1, i.e yel1low; for "acc-ommo-date" the values are acc2ommo5date. Setting a Minimum Score value to a larger number (e.g., 3) will hyphenate less often."

Hi @Alessandro Carnevali and welcome to the forums,
The good news is that your file opens without any issues. All the assets in the file are Linked which suggests it's likely one of the Linked files causing the issue, most likely the version of 'Store basket.ai' on Page 3 which I replaced in the attached file.
I would strongly recommend that you move all your Linked files to your Internal Hard Drive, keeping them stored on a Cloud Drive or External Drive can cause issues.
If you rename the folder where all your Linked Assets are stored to break the link to the Publisher file you should find the file will open. Then move your Linked files to your Internal Hard Drive, relink them and see if that fixes the issue for you...
Let us know how you get on with the attached file, whether moving and relinking the assets works for you, or whether you still encounter problems.
Note: The attached Publisher file is saved using v2.4.2
Guida Cammino prova 2 noai v2.afpub

Hi @Alessandro Carnevali,
That's no problem at all, I'm glad all is working for you again and you can continue working on your file...
Thanks for confirming that your assets are stored locally, the file path to the Linked files looked as though it might have been Cloud Storage. Hopefully, you won't run into any more issues please reach out if you do.

Loading your PNG file as the sub-brush texture both previews and paints on macOS so it looks as though this may be a Windows issue...
Edit: Ignore me, it's not working for the sub-brush

Hi Guys,
I have logged this with our developers to be fixed in a future update
Thanks
C

Hi @nvtypenut and welcome to the forums,
I'm having no issues printing your image multiple times after cropping but I'm on Monterey...
This may (or may not) be related to a known issue with Sonoma reported a few times in the forums... the basic solution to the known issue appears to be to remove the printer in the Mac Printers and Scanners System Settings then re-add your Printer...
I can't guarantee this is the same issue but perhaps worth a try...

Thank you for that response.  To be honest I am puzzled because I was sure it didn't behave like this when I set up this document a couple weeks back. As the app updated a couple of days back, I saw the behaviour as a result of that.
Having said that, indeed, moving it all to be a child of the Artboard solved this movement issue.  Many thanks.

Publisher 2.4.2 Dragging any layer with effects only over the image frame causes the FX effects to be lost on MacOS

2024-04-14 о 19.13.15.mov    

It’s actually called OCR-A (where OCR stands for Optical Character Recognition). OCR-B is much less ugly and much more readable by humans, which means it lacks the geeky feel of the original.
 
OCR-A:

 
OCR-B:

 

Hi @knippex and welcome to the forums,
Affinity apps don't export SVG files using user units which is a big problem for many users when importing SVG files into CAD, Plot, Laser Cut and a myriad of other software...
W3C Specs say SVG should use 96 dpi but both Affinity and Adobe apps incorrectly use 72 dpi, unlike Inkscape and Corel which correctly use 96 dpi...
There is also a bug, listed as AF-2692 in the SVG export window when exporting SVG files from Affinity apps where the 'Use dpi' entry fails to honour the dpi entered.
The size of your exported SVG suggests your Affinity Document uses 300 dpi, (300 / 96) x 100 = 312.50% | 20 mm + 312.50% = 82.5 mm which sounds like what you're seeing.
There are two workarounds:
Workaround One - Set your Document Setup to 96 dpi and export to SVG with 'Use document resolution' selected in the export window Workaround Two - Edit your exported SVG file in a text editor and change the width and height from 100% to the respective user units, i.e., change
<svg width="100%" height="100%" viewBox="0 0 237 296" version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" xml:space="preserve" xmlns:serif="http://www.serif.com/" style="fill-rule:evenodd;clip-rule:evenodd;stroke-linejoin:round;stroke-miterlimit:2;"> <rect x="0" y="0" width="236.22" height="295.276" style="fill:#fff120;"/> </svg> to
<svg width="20mm" height="25mm" viewBox="0 0 237 296" version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" xml:space="preserve" xmlns:serif="http://www.serif.com/" style="fill-rule:evenodd;clip-rule:evenodd;stroke-linejoin:round;stroke-miterlimit:2;"> <rect x="0" y="0" width="236.22" height="295.276" style="fill:#fff120;"/> </svg> Note: The SVG will still open at the incorrect size when reopened in Affinity apps because Affinity apps interpret the SVG at 72 dpi instead of 96 dpi but assuming the Arduino software uses 96 dpi as its base the SVG exported from Affinity apps 'should' appear at the correct size...
I hope that helps... let us know if the workarounds work for you and if not let us know the outcome you see.
I think the answer is 'yes' but could you elaborate a little with a simple example of what you're trying to achieve so we can better help you?

That's no problem at all, hopefully, you're closer to achieving what you set out to achieve...

If drawing a slice manually then, yes, it will snap to pixels rather than the edge of your graphic if your graphic is not perfectly pixel-aligned using integer pixel values for both its dimensions and x and y coordinates (as mentioned above)...
That's just the way the Export Persona works in the Affinity apps... I believe this is because SVG is based on XML, which is pixel-based, though I'm sure someone will correct me if this is not the case...
If you change the document units to pixels your exported graphics' dimensions will be rounded up to the nearest whole pixel for both width and height considering the x and y coordinates of your graphic which if not perfectly pixel-aligned will add pixels to the exported SVG...
Only when your graphic is perfectly aligned and sized using integer pixel values will the slice snap perfectly to the outer edge of your graphic...
So this...

will result in this...

Did you try not selecting any layers and just exporting the graphic as per the previous post?

PCB.mp4

@Hangman
The basic idea is to have a large "work surface" where I have many sample elements next to each other. 
Then I will create my new component in a free area. Here I now can copy the sub-elements from the other template files quickly and easily. 
Then I simply slice my component, export it and I'm done.
I can then copy this file from project to project and just replace the last element created with my new one.

@Hangman, @bbrother
My problem with slicing is that I cannot slice elements that are not grouped together. 
If I select individual elements and then click on the slice button, see below, it slices all elements individually. 
Then I wanted to use the slice tool to simply make my frame large and hoped that there might be a way to make this frame snap to the outer edges or something similar. But unfortunately I can't get any further. When I group the individual elements, it works as it should.
But as far as I have read, the elements should be ungrouped when exported so that the software can read them in cleanly.


Here I tried to select individual elements and pressed slice. But as you can see, the result is not a large slice but a single slice for each element.

 
@Hangman @bbrother
It's nice to see that you reply to me so quickly. Super community thanks for the help so far. ☺️
 

I think I have discovered what the problem is.  When I transferred files to this computer a large number in one folder transferred across with zero bites.  I have been trying to open some of these without realising they had been corrupted.  I have now successfully opened other V1 files, which is a big relief!

Hi @Dan C,
I'd be interested to know the expected behaviour, I assume it will be as it currently is...
I can certainly see arguments for both behaviours as well, maybe there could/should be an additional selectable option in the Alignment Panel for 'Relative to Regular Bounds' which when unchecked exhibits the current behaviour and when checked 'Make Same: Width' and 'Make Same: Height is based on the Regular Bounds of the first selected item...

Thanks for your report @Hangman & our apologies for the delay!
I can see from the internal bug report that it appears our development team have confirmed that the behaviour with 90, 180 & 270 degree rotated objects and Set Section Box is expected, with the following reason:
However, the bug you're reporting here seems to affect any rotational value that is not 90, 180 & 270 - after using the Set Section Box command.
For example;
Draw a rectangle Rotate by 45° Cycle Selection Box Set Selection Box Note the current Height & Width reported in Transform Draw a second rectangle using different size values Select the previously rotated object, then the newly drawn rectangle Make Same: Width
⚠Note the Width of the second rectangle does not match that of the rotated Regular Bounds rectangle, the Base Box value is used Make Same: Height
⚠Note the Height of the second rectangle does not match that of the rotated Regular Bounds rectangle, the Base Box value is used I can see arguments for both behaviours here - some users might expect the 'true' width / height of the object to be used, ignoring the rotational value affecting the Regular Bounds transform values however others may expect these Regular Bounds to be used after applying the Set Selection Box command.
Therefore I'm checking this with our development team now as to their expected behaviour and will log this as a bug as required - once I have further information from our team I'll be sure to share this here

Welcome to the Serif Affinity Forums, Duncan.
What you’ve described isn’t actually a bug. The ‘Character > Positioning and Transform’ route positions and transforms glyphs for the regular characters so that they’re smaller and (for subscripts) lower than the originals. The ‘Typography > Subscript’ option uses glyphs for the subscript characters where available, but there will usually only be numerals plus a few alphabetic characters, and the font designer may have chosen to make those glyphs look different from their full-size counterparts.

I did try the same using an image located in iCloud, thinking that may be the reason but I still only saw the Image Policy message once which was why I was slightly baffled...

That was the solution. It works again. Top support. Thank you very much. Now I can create beautiful cat pictures for my customers again.

@Hangman @Alfred This is indeed what I was looking for. Thank you very much.
To all who responded, thank you for taking the time to try and help me. Much appreciated. 

Now I went to my search bar and opened the app not from the recently opened file and held down ctrl, the app is now open and still there but no Clear User Data came up.  Whatever it seems to be working now..  Thank you

As @Alfred said...
Assuming all your images are the same size, JPEG, PNG or TIFF files... Mine happen to be square so I'm demonstrating using a 210 mm x 280 mm document...

Images.mp4

As @Alfred said...
Assuming all your images are the same size, JPEG, PNG or TIFF files... Mine happen to be square so I'm demonstrating using a 210 mm x 280 mm document...

Images.mp4

An A4 portrait page is 210 mm wide by 297 mm high, so for a row of three pictures you need each one to be no more than 70 mm wide (and each row must be no more than 74 mm high). If you’re using an A4 landscape page, the maximum width becomes 99 mm and the maximum height becomes 52.5 mm.
Create a new A4 document, place the 12 pictures on the page at the desired size, and use the Move Tool to arrange them in a pleasing layout.