thomaso

As far I remember from earlier threads not only the macOS version but also a / some macOS system setting(s) may influence custom dictionary entries / their storage file path … which might cause more confusion unfortunately. For instance:

If you have master page spreads of different sizes then you would need to care for the settings of "Single/Facing" and "Page/Spread", otherwise all master spreads may get get changed to the size you currently have defined for the change and may let to confusion for the app and the user. To me this two settings worked, note that a certain master spread is currently selected and influences the required setting for "Single/Facing". In my various tests I also got unwanted results with page sizes that appeared unchanged or the 2-page-spread turned to 2 landscape pages or to a single portrait master page instead of a spread (leading to a blank right document page 5). Unfortunately in some of these resulting changes neither "Undo" nor the "History Panel" worked to fully undo the procedure but created more confusion. At least in this undoable results there seems to be a buggy app behaviour (which a V2 user might want to test for a possible Bug Report). Nevertheless it does not explain your experience that deleting a document page/spread causes the deletion of content on a master page (and thus in the entire document on pages that have this master applied). This would require a document page working as "master" for a master page, which can't be created in APub as far I know*. Even master pages applied to other master pages would not cause your result of changing a master page when deleting a document page but might cause interruption or confusion with text flow only. (*that is why I asked you before whether AD "Symbols" were used, since a "Symbol" object can create dependency between a 'master' symbol and its further instances anywhere in a document.) In your situation I would go back to the initial document (before scaling) and start the procedure again to make sure all scaling gets done as wanted without causing local issues. This might help to avoid possible confusion that may occur at any later time of the layout process when editing or moving items. This is not unusual: Scaling text objects doesn't change the attributes of saved text styles but causes 'local overrides' which are indicated by a + symbol next to the style name at various spots of the interface. To change the style attributes to the new size you can use the "Update" option (<- right click on a style's burger menu).

With the text frame selected switch to the Fill Tool to apply the gradient. It shows in the Context Toolbar a menu to choose Fill or Stroke. Means you need to apply both (2 steps).

Even if Serif/Affinity would use perfectly spellchecked "Latin" for filler text it is useful to have it set to None because this allows the user to modify the filler text individually within a text frame (e.g. to achieve a specific visual impression, ignoring its sense.). Also, btw, note we may have custom filler text content AND its language which will get set for filler text accordingly if used.

This makes me still ask how hyphenation works for you on mac in V2 (while I do have the .dic in V1). I don't wonder that the spelling dictionary is not included, it may simply not be required for filler text because that text is an internal app resource which might be "spell checked" before implementation. Also note that this app folder …/Resources/Dictionaries/… contains only hyphenation .dic files (but for various languages), no spelling .aff at all.

No. With a linked image layer selected the Context Toolbar offers the "Edit Image" button, this is not available for embedded images. @R C-R, the hint "Linked document" appears for container file formats and thus also shows for placed Affinity documents and EPS files. This also means that they cannot be easily edited in the same way that placed image layers can be.

What do you mean by "replaced"? – I used this decades ago in various macs successfully, it does not only remove system (macOS) language files but also according files from app packages. If you have Adobe apps installed it is recommended not to remove their language files because they might not launch any more (and require re-installation). (when I used "Monolingual" it offered a dialog for excluding Adobe in particular)

... but filler text appears to trigger & use a hyphenation dictionary "Latin". It might not be sufficient for 'true' Latin, that's why I started with "what it's worth…". I have it on mac in APub's V1 app package as "hyph_la.dic" (2 kB). – What hyphenation .dic is used for filler text for you in V2 / mac?

For what it's worth, the Affinity app package may already contain a hyphenation .dic for Latin (filler text). /Applications/Affinity Publisher.app/Contents/Resources/Dictionaries/la

It might be worth to mention that the (any) FX method will cause rasterisation on export.

How often do you want to ask? – I recommend to start reading again and focus on "open" (not on "place") and/or read the linked feature request. For instance from my first post in this thread: While opening as "pixel" is the existing behaviour it's clear that the option to open as linked is the wanted/requested/suggested/new/missing way of opening.

That's why I think an inspection of your document with filler text (instead of copyright text) may be worth a look. Currently you still describe symptoms only … without a chance to inspect/detect a culprit in the Layer Panel's layer structure of master + document pages (i.e. via uploaded screenshots, video or document).

… but not in in the OP's PDF/X-1. This PDF version does not support/accept RGB.

What image quality settings did you use: Was downsampling activated / what compression rate? In addition to @GarryP's sample calculation you need to consider that the images get saved in the PDF as CMYK (32 bit) while the initial PNG files on disk may be RGB (24 bit), which means 1/4 more data (1 colour channel) for every image in the exported PDF.

Do you mean the issue appears and disappears? If yes, could this be a redraw issue (not displaying existing text)? Or do the objects (text frames) in fact disappear in the Layers Panel of the affected master pages? Assuming not the text content is causing the issue of disappearing content on master pages but rather the layers/objects you possibly can replace the sensible content of the main story text flow with filler text and upload the modified document. Alternatively you might show a video demonstrating the issue resulting from a spread deletion + unfolded all possibly collapsed layers on the affected master page. (.IDML is the exchange file format to use InDesign documents in APub, "Symbol" is a feature to link instances of objects in AD)

Yes. (I'm talking about opening, you keep talking about placing instead). Compare this feature request from 2020, which has been implemented and enabled in V2 for RAW but not for other image file types:

Either assign the gradient to fill + and to stroke … … or use AD > Contour Tool and assign fill only:

I would try to scale the content on this page manually. I would not delete single pages but 2-page-spreads only to avoid confusion of left vs. right pages. I have no idea what is going on and how the content of a document page can affect the content of a master page. Possibly the temporary page shift (left/right) caused confusion for hidden, invisible parts of master spread content? (compare: the invisible master page content left of page 1). Was .IDML involved for the document creation, or possibly AD's "Symbols"? It may need to inspect the Layers Panel (with all layers unfolded) of the related spread and master to detect a possible confusion or culprit. Can you upload your .afpub to the forum?

As mentioned >>I always wonder why "open" is forced to create a "background" = "pixel" layer … but does not allow to open linked << it means the way how images are opened (opposite to placed). I would want the option to open (not place) an image but with the result of placed items: as linked layers and/or with an entry in the Resource Manager – but possibly still with the name + suffix of the opened file (for simple "Save" if wanted).

@stokerg, I always wonder why "open" is forced to create a "background" = "pixel" layer … but does not allow to open linked (as possible with "Place" or when opening a RAW in V2). I often open an image (to get a document in its size created, then delete the "background" layer + place the image to get an "image" layer to avoid a large default .afphoto file size). Wouldn't it be useful (and also auto-avoid unwanted snapshots) to have a choice when opening an image to open as "pixel" or as linked "image"?

I agree this dialog appears unclear or misleading and the app would not need this prompt in documents where all master + master pages have the same size (= because they do not differ). It appears to be coded (implemented) as a general dialog if the feature gets used for master pages. (and it points to / is related to the optional fact that a master spread size may differ from a document spread size but deliver the master's content only without its spread size). You don't have to scale the master pages "manually" but can use the same dialog you used to scale document pages ("spread setup") but apply this rather for Master Pages by having a master page selected when opening + setting this dialog. Also you don't have to change master pages/spreads individually/separately but can choose "All Spreads" to change the size + content of all pages in 1 step (shown above in my screenshot for V1). Then just confirm the prompt with "Yes". Note, if executed you can Undo this procedure with the Undo command or via History Panel, so you can try and see what it changes you got and possibly restart the procedure with adjusted settings.

In addition, the viewing option for "Pixel Selection" may be deactivated.

In both screenshot no object was selected. They just show any current stroke setting which doesn't have to be applied to any object.

In your screenshots it seems that the master pages did not change their size. Possibly you set them first, they might auto-adjust all their objects + related page sizes. You may get asked whether you want to adjust the document page sizes.

While the non-affecting flow options for any "Start in/on Next…" setting appear like a bug to me, a workaround might work in the meanwhile: a large "Space After" for the previous style instead of "Start on Next…" for its following paragraph style.