ballardstudio

My concern for users is creating a 350 page manual and having to output a file that is a several terabytes large because the APub file and the supporting files need to be included; especially when linked.

The one image used is 155MB. My point though is that the size of the layout, with or without embedded images, is approximately the same size. If the file is linked, the Affinity Publisher file (large) and the linked image (large) both need to be send for output (if printing). If so, the files will be double the size that they should be. The Publisher size should be about 5 MB.

Something similar happens on the Windows side but affects all Adobe applications. What's great about this find is that Affinity Publisher recognizes all layers in the file and the file is also editable in Affinity Publisher. That includes .AI (PDF option) files and .PSDs.

I just created a comparison layout to compare file sizes between InDesign and Affinity Publisher. The difference in sizes is enormous! A four page document with one large image (spread) and some text with an image calculates out to this: Affinity Publisher Layout (embedded images): 186 MB Affinity Publisher Layout (linked images): 165 MB Adobe InDesign Layout (linked images): 2.07 MB Affinity Publisher Layout (ZIP file): 94.6 MB What is making the file sizes so bloated?

Errors like this are usually due to attributes that aren't translating properly. Now imagine this being added into a Affinity Publisher file and not seeing the errors on the front-end because you used a Word file import. For you, everything looks perfect...you're golden! On the back-end, it's a complete disaster! There are comments here from prepress operators about these issues earlier in the thread.

This is why Character Styles and Paragraph Styles were created. If an import is to be created, let it except Word files, but import the text as plain text so it doesn't ruin anything like TOC linking and other formatting within the document. This is crucial for long format documents especially manuals with images.

Yes, it does Rocketdrive. You have to select the option though because by default Publisher embeds images as opposed to linking them. Otherwise, I didn't run into any functional issues so much. Just a known error when opening the Find menu. I'll post other issues on the boards if I run into anything.

Thanks!

I remember those days. A lot has carried over since then. I was the designer who had to take the art and creative director's work and fix it all before it went to press. There are so many odd issues I've encountered, I just try to keep note as to what causes the problem and how to fix it; Word import is a big offender.

Thanks! What is supposed to happen once you click on Find? The error hasn't repeated itself, so I'm not sure if a function is actually happening.

Yes, but keeping in mind that Affinity Publisher is a layout application not a photo editor or illustration tool makes me wonder what is the path of full capabilities for the application.

Affinity Publisher just made all of my Adobe Photoshop and Adobe Illustrator files the default application for file launching. This may not be a bug, it could be an intentional because I didn't realize you can edit Adobe PSD and AI files directly in Affinity Publisher. This includes layered files. I thought Personas weren't available just yet .

It's a nightmare on the back end. What would be nice is to have Word files import as plain text with the ability to stylize copy on import.

Thanks for backing me up on this one! A lot of designers don't understand the back end portion of this.

I am very serious. Carrying over attributes, especially from Microsoft, to any other application can cause issues with your files. I've seen it too many times and ask designers not to use imported or copy/paste text from MS Word. These issues also occur in digital design when copying text from Word and pasting it into an HTML document. In print, your provider may be charging you additional money for fixes in your files due to attributes and you wouldn't know because it's considered as a hidden production charge.