Jump to content
You must now use your email address to sign in [click for more info] ×

ballardstudio

Members
  • Posts

    48
  • Joined

  • Last visited

Posts posted by ballardstudio

  1. On 9/11/2018 at 10:17 AM, rjvela82 said:

    How big is the actual image file used? I have a 9 page spread with 6 master with a large image spread in each at under 5 MB.

    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.

  2. 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?

  3. 44 minutes ago, Fixx said:

    How would styles help if ÖÄÅØÜß are all wrong characters? 

    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.

  4. On 9/5/2018 at 3:52 AM, Fixx said:

    txt format usually get special characters all wrong when transferred to different computer. Word is much more reliable. It used to be normal to massage text in Word before importing it to layout application..

    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.

  5. On 9/4/2018 at 11:14 AM, Rocketdrive said:

    Pretty thorough testing, ballardstudio. Did You run into any problems or interesting things? Would be great if You shared Your findings. Oh BTW: does Publisher support document linking for images? I managed to do my clients' print design in Designer until now, but the files tend to bloat towards epic sizes, megabyte-wise.

    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.

  6. On 9/5/2018 at 5:08 PM, kirknurse said:

    I am a designer but I was fortunate to work with a few prepress houses back in the early days before direct-to-press. You had to do separations to film and then burn plates. Film was not cheap so you HAD to get it correct almost from the very beginning.

     

    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.

  7. 27 minutes ago, αℓƒяє∂ said:

    The Affinity apps can import and export PSD, but text will be rasterized on export (instead of being exported as editable text). AI files can only be imported if they contain a PDF stream: the native AI data is ignored.

    None of the above has anything to do with Personas.

    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.

  8. 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 :).

  9. 44 minutes ago, fritz franz vogel said:

    it's not just a bit word-files, that i like to include in APu (copy&paste by small texts may be ok). but how about long texts, 200, 400 pages  (literature, scientific work with hundreds of foot or endnotes, with complex hierarchy in titling)? it would be really nice to have an automatic import instead of clicking and binding the text boxes again and again.

    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.

  10. 16 hours ago, kirknurse said:

    I second that, It is a big pain in the behind. Set up your native style sheets (in this case apub) and then bring in plain text is the way I have always done it. It can even be a pre-press nightmare as when you're pre-flighting and it's looking for a nonexistent font.

     

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

  11. 2 hours ago, Seneca said:

    You must be kidding.

    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.

  12. 10 minutes ago, MEB said:

    Hi AffinityJules,
    Technically, yes you can create this in Affinity Photo but it would require more manual work. It's also a relatively simple example for a layout (no multiple pages/spreads etc). For example the text columns had to be set manually as well as the text itself since it doesn't flow from one text frame to another in Photo. Affinity Photo also doesn't support baseline grids to keep the text alignments consistent between text blocks.

    Well said MEB! I also did extensive testing on other back end processes (mentioned above).

  13. On 9/2/2018 at 2:43 PM, AffinityJules said:

    Looks fine to me but, I have to say I'm a bit confused.

     Could this design not have been achieved using AP? After all, it's just a picture with various fonts.

     Please tell a Mr Don't Know what would be the primary difference?

    Yes, this could be produced with any layout tool and possibly a word processor, but it's a CMYK layout, produced with Affinity Publisher using various advanced functions and tested for embedded images, PDF output, offset and digital printing capabilities, OpenType compatibility, cross-platform translation between Mac and PC, ZIP file compression, cloud compression and bloat, file bloating, color correction, color accuracy, color profile accuracy, color conversion, and other details that advanced design directors, UI and UX designers, and prepress operators would look into when beta testing new software.

×
×
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.