Wosven

Trim begining and ending spaces (and return or line break at same positions seems logical or possible, no more*), but the more important is URL_encode (percent encoding) when memorising the text — and URL_decode when displaying the URL for modification, should be done by the app. Some red flags to indicate a wrong URL... why not, but it shouldn't prevent PDF export, unless it's an option (copy-editor or the worker seriousness are the ones that need to check valid URL). The same for mailto. And the app shouldn't auto-correct any text inserted in those field, or words beginning by common URL/FTP prefixes or containing an @. * Working with the Office suit means using apps that'll use their limited AI to select more than what you want... or use unintuitive shortcuts impossible to disable or modify... That's where some small tricks in apps like APub can compensate those overzealous "user friendly" additions.

And if at some point the page numbers disappear, just select all, apply [no style] and apply again the List paragraph style, they'll reappear.

Why not use text frames linked with a Numbered List Paragraph Style flowing/begining in each new frame? (The only bad news is that you need to link them manually... but after that, type a space and a return and the numbers appear) When you add pages, you just need to reflow few frames. numPage_left.afpub

You're right, that just draws on the same "layer object", it's the CMD (Mac), Ctrl (PC) that do th etrick.

You can proceed like this: First, select all the lines and ensure they'll scale with object (keep same ratio depending of the new page format) After this, you can modify the document: (I choose A4 since it's just a little bit biger than your format):

You can click on a node with the Pen tool

It's not like this feature was never asked for or the default option is causing problems, but it seems Affinity won't modify this setting, when stats show that we export to all pages 99% of the time (spread is only for specific small pages, when needing easy to read copy-editing/checking, and to avoid using a lot of paper when printing, since most PDF readers are able to display facing pages, or print different pages on a page: this setting is less and less usefull with time, and shoudln't be the default one): ...

It woud mean adding an email client in the apps... not sure it's usefull for a lot of us or a priority. Perhaps an estimate of time so you can check if it's finished when it's suppose to be?

Another "test" idea: if the problem come from fill layers, can you test rasterizing only this layer (or a copy of this one)?

Nice that you figure it out while I was sleeping

Like @Old Bruce, I would redraw... It'sdifficult to get something clean since part of the drawing should stay, part of it should disappear, but they are the same value...

HI, That's really strange, I never work with a printer asking for no crop marks when dealing with books or magazines (they complain if there's a lack of bleed and crop marks). They can delete it if needed, but at least they have the PDF to check how the result should be. No guesswork of different print test. If they can't provide a page with technical and clear explanations about how to set the page, I would probably found another printer... The fisrt thing we do once a project is decided, after some technical choices due to cost, is to write down the specifications needed for the document. Do they have a page with such informations, or is it a special format?

From something I read long ago I don't know where... Those subtle spaces rarely exist in the fonts, and layout apps will give the specific and needed proprieties. (The article, that I'll search, was about the different implementations and choices mades by dev, between QXD and ID).

Hi @Studio97Visuals, Don't forget to check the color you're using with the brush... You're painting white on white. Unless you're Malévitch, it'll get nowhere

Another option, since converting text to curves generate a group, would be for this group to get as name the first 10 (?) characters of the 1st line of text..

Hello and welcome @AndrettI, Without the original file, difficult to understand the problem, and since the "Adobe output" is just an image pasted in APhoto and exported as PDF from there... Did you imported a PDF in 2 different apps before exporting as PDF?

Yes, that's annoying that the apps only have one path variable for everything. Imagine the time we spend searching files exported or saved in the wrong folder when working on different projects at the same time...

@R C-R effectively... But as you said, it seems to be a OSX problem with fill layer. Perhaps this need to be in the bugs section.

Damn, I've got no problem also, exporting it. Can you try opening this one, and test? 011-Hiltenfingen2.afphoto

And they usually give a maximum size, this means that under this size, it's also acceptable.

And a tip: when you hide the record layer, the real transparent checkered background is of a different size. This means the layer isn't transparent.

The record isn't transparent (the checkered part doesn't disappear to display the black background) The other one is transparent (no background, black parts on black not visible): The record isn't transparent:

The purpose of my post with the 2 PNG was for @acehan80 to download them and check them, and compare result. (I just forget to write it in the end )

That's sure that there's a difference between a screen shot of a PNG's transparency (the previews I was talking about in my first post, with checkered background), and a real transparent PNG you save with from a site or create. Fake PNG (screenshot): Real PNG with transparency:

The app got a problem in this corner. Did you try adding a new layer doing modification on the whole image, and try to export it? If the image is whole, perhaps adding an adjustement layer with 1% action (contrast for exemple), can force the app to memorize again the whole image and this problematic part.