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)