thomaso

Yes, we can't remove our posts but we can hide them. (or keep the post and delete its content, which may confuse more). Probably my reply was posted (or started) before you've hidden your post. Its nothing special and happens occasionally in the forum.

It seems like you solved it in the last few minutes with help from @NotMyFault and @GarryP. By the way / just in case: There was also a similar issue (AF-5966) regarding the displayed bounding box (which seems to be solved, too, according to the @Affinity Info Bot):

Also in Acrobat some objects (outer contour) seem to be positioned outside the page and in the bleed area. Nevertheless the PDF gets interpreted oddly if opened in Affinity (apparently the OP wants to open the PDF, not just place it). If I open the PDF in V1 it opens with bleed area but with a smaller page size + objects partially in the bleed area + without the (larger) mediabox. If opened in Affinity there is a Layer layer named "Trim" with an odd size and its content (text box) outside the page: If I re-export the opened PDF from Affinity it appears in Acrobat with the reduced page size and lacks the (larger) mediabox + text box, possibly because Affinity generally doesn't export a separate "slug" area:

"Ungroup" is not only in a group's right-click menu but also as a button in the Context Toolbar and in the main menu (with shortcuts):

Can the N-Up model be combined with the Booklet model? The OP wants "to print a booklet", probably with the required imposition of pages. A similar request was recently made and workarounds were discussed:

If you prefer separate exports of individual layers/groups, you could use nested artboards (with the "Edit All Layers" option disabled). While this is more complex to create, it offers more/easier export options separated by artboards, both via the "Export" menu and via "Export Persona > Slices." (In the examples, the nested artboards are offset for clarity; in a real-world workflow, they may be the same size and position.) Of course you can combine nested artboards with Layer layers … … and maintain the advantage of auto-created slices for the parent artboards:

You can try ungrouping + regrouping the Group to get a straight bounding box for a rotated Group layer: group rotation box.m4v

If you export as PDF all text should be sharp in any font size and exported file size. If text gets unsharp it seems to be rasterized either before or during export. If this is the case we would need more info about the layout, its objects and possibly rasterizing causes (e.g. adjustments, filters, blend modes etc). Regarding image quality + exported file size you have three export options that directly influence both aspects: • export resolution, • downsampling, • JPG compression. For a quick&dirty test you can reduce the JPG compression from its default of 98 to 50% to see the impact on file size and quality. Depending on the colour spaces/profiles of the placed images also the option •"Convert image colour spaces" can affect the file size massively, and accordingly also the PDF version can do (e.g. PDF/X vs. PDF 1.7). Aside from the three or four aspects mentioned above, there are no more general recommendations for "the best settings" than Affinity's various default settings. All settings also depend on your specific requirements and individual preferences, like your idea of "acceptable" image quality. However, if your resulting PDF is 150 MB or larger, even though a maximum of 10 MB is desired/requested, we need additional information about the layout, object types (e.g. vector vs. pixel), and the total page count to assess whether exporting this document to a size of 10 MB is even worthwhile. It is useful to be aware of involved colour spaces, of the document, the placed resources and for the export. CMYK with its 4 ink channels is about 1/4 larger than RGB with 3 colour channels. CMYK is meant to be used for print only and it has a smaller gammut (a smaller range of displayed colours). EDIT: Since the topic states "mainly the Text," you could – in addition to the aforementioned rasterization of the text – check whether the text in the resulting PDF has been converted to curves, which may influence the resulting file size and also the visual appearance of text ("sharpness"). Test: If no text is selectable in the exported PDF, it has either been rasterized or converted to curves. In an even worse case, the text could be duplicated, one version as curves, another as selectable text, which would complicate the assessment.

... or use the colour Picker tool of the HSL adjustment dialog (unless you want to specify numeric values).

Ah, Pšenda was faster. However, for more flexibility with the setup of the HSL Shift you could just mask red parts (e.g. lips, hands, tows) in the adjustment layer.

You can edit the properties of the desired double-page spread: Double the width of the spread(s) -> move all content to one of the two adjusted pages -> delete the other page. This might cause a ghost page, but the 'merged spread' will be exported as a single page between other single pages. Of course, you'll need to -> start a new section after each of these merged spreads to ensure correct page numbering. In my example (from the iPad), the last page should be page 6, not page 5. single pages & 'merged spread'.pdf

Aside from RE4LLY's note: The PNG file type does not support CMYK (but does support RGB and grayscale), so there may also be a problem with the colour profile.

Good catch. How did you detect that stroke settings are the culprit? Have you ever had a similar problem – or was it 'just' trial and error, layer by layer? BTW, it's logged/tagged meanwhile as AF-7738.

Apart from MEB's hint regarding layer hierarchy, a change of attributes works also with Affinity Groups: If a "Group" layer is selected then a change of stroke or fill colour (et al.) will be assigned to layers inside the "Group" – but it's limited for multiple nested layers, e.g. a child object clipped by a parent object inside the group is not affected of a such a change done to the parent group.

Sorry, I don't understand your use of "traditional" and your colour example described for layers (... or layout objects?). Possibly you have "Global Layers" in mind? This layer type gets created for an entire document, used as container for future layout objects. They just structure the layer hierarchy across an entire document (i.e. on all pages) and can be used, for example, to organize different object types (e.g., text vs. image vs. background) within the layers panel or different text versions (e.g., English vs. French). If the property of a global layer is changed on one page (e.g., its vertical position in the layer hierarchy or its interface colour), the change is displayed synchronously on all other pages, so every page shows the same set of "Global Layers" but gets filled individually on individual pages. Unfortunately, "Global Layers" are not available in Affinity, although a discussion was nudged and kind of announced for APub by Serif staff members several years ago.

I don't think so, unless you accept the CMYK output of your CMYK document in the exported PDF which you had set to RGB before export (and without selecting a profile). Apparently the same oddity as shown above (for iPad) occurs and Affinity can't set and export a PDF/X in combination with an RGB profile. What menu entries (profiles) do you get when you try to set the colour profile in your settings? Can you choose sRGB? If you open your exported PDF/X-3 in Affinity and let it estimate the colour space, in what space gets the document created?

The colour shift seems to be caused by known Affinity issues with mixing colour spaces: CMYK document -> CMYK adjustment -> RGB output. If you switch the document from its current CMYK to RGB the issue gets displayed in the layout window already. If you then define the adjustment curve in its RGB space the issue doesn't occur. Note, in the attached example PDFs the adjustment curves were just roughly set and thus aren't corresponding. RGB-doc_RGB-adjustm-v1.7.pdf - CMYK-doc_RGB-adjustm_RGB-export.pdf If I export (v2, iPad) the original CMYK document to RGB (e.g. 'digital' preset) then the profile menu still offers CMYK profiles only instead of RGB profiles. A vaguely remember this was reported and logged as BUG years ago for the V1 desktop version.

You attached a PDF (v 1.7) with the image in the light blue version. I assume you meant to upload an Affinity document (with the image embedded), right?

You could resize in two steps: Resize by 100 px with the anchor set to the right canvas edge + resize by 500 px with the anchor at the left edge.

Yes, I agree, of course workarounds can be annoying and not very welcome. I was rather confused be the OP's response… ...unless they specifically requested an answer without workarounds. In that case, the answer would have been "It's not possible in Affinity," and the thread would have ended. However, I can think of another workaround that accommodates the desire/requirement of printing two double-page spreads on one sheet and cutting them later. Its efficiency depends heavily on the layout and the variety of object types used. Increase the page height of the document by duplicating it and setting the anchor at the top. Duplicate all objects on all pages and, with the copies still selected,… …move them down by the original page height (half the new height). The result is a layout that includes a copy of each double-page spread, as shown in the screenshot of the OP's first post: This can be printed as a “normal” brochure without fiddling around with N-Up options, and with the sheets being halved as desired after printing.

I can't follow. To me printing single spreads on single sheets appears to be fully related to the topic. Though it suggests another than the requested workflow, it still achieves the desired result ... ... but with less complexity: The only difference seems to be the reversed order of printing & cutting and the resulting reduced requirement for certain printing options.

If you want to get the currently assigned text style replaced by the default text style attributes you can press "No Style" as @Hangman mentioned. Alternatively there is the menu option "Detach Paragraphs From <stylename>" (dt.: abtrennen) which will deactivate the first menu option but maintain the style attributes with none of your saved text styles assigned to the text with the consequence that also "No Style" is highlighted but not with the default attributes (see above: Arial normal vs. below: Cambria italic). Result:

Hmm? Doesn't a single misprint on a sheet for 4 layout instances (= 4 final cards) actually cause 4 times as much ink + paper waste as a misprint with only 1 single layout on 1 printing sheet/card? Your thought may be correct as example for an offset printing machine and large sheets of 100 x 70 cm and with high print speed while every machine hour costs. But for a fully manually procedure I can't see an advantage to print multiple pages on larger sheets and cut them after printing.

For file size reasons for instance. If an image is sRGB than a missing profile quite likely doesn't harm since it is the standard. Note, if you upload an image to this forum its software strips the profile, quite likely for disk space reasons. And if not sRGB standard: If users upload a screenshot this file usually had the user's monitor profile embedded which got stripped during the upload. If the metadata haven't been removed before upload, then other forum members still have the profile info available (e.g. in case of colour questions).

Does it not work in every document and with every image/curves adjustment, or just in this in particular document? Have you tried to activate for PDF v1.x the export option "Allow advanced features"? The preview seems to show a masked adjustment (~ blue only). If yes, does it make a difference if you export without the mask? Is the document's colour space/profile sRGB (... as used for the v1.x export)? Can you show the Layers panel? In addition to the colour issue: In your screenshots the estimated file size for PDF/X is about six times larger than the v1.x version (512 vs. 77 kB). Is this difference still existing after export? FWIW, I can't reproduce the issue with Affinity V2, iPad.