Jump to content


  • Posts

  • Joined

  • Last visited

Everything posted by ballardstudio

  1. 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.
  2. 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.
  3. 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.
  4. 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.
  5. 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.
  6. Thanks for backing me up on this one! A lot of designers don't understand the back end portion of this.
  7. 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.
  8. Importing Word documents is bad practice when creating layouts. The carried over character attributes are known for causing various issues that can lead to a series of problems, including file corruption. You're better off creating a plain text document and reformatting it
  9. Thanks! I know font collection may be a tricky one because of the copyright laws that are involved with fonts. Hopefully an auto-collect tool will be available before the full version launch.
  10. Well said MEB! I also did extensive testing on other back end processes (mentioned above).
  11. 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.
  12. I was looking at something a little more for font usage as opposed to find and replace. This does work to an extent, but could work better for the designer who is looking to collect assets (still looking for an auto-collect panel) or wants to find and replace fonts quickly by family.
  13. So are you saying that when the panel opens you can find fonts? My panel received the error. When I relaunched, Find was totally unresponsive.
  14. Here's a layout I created with Affinity Publisher. Photo and copy credits included.
  15. Here's a layout I created with Affinity Publisher as a test. Copy and photo credits added at the end of the body copy.
  16. How do you find fonts being used in a document? I navigated to Text> Find... and received an error (posted to the bug forum). Is there another way to view the fonts?
  17. When using Publisher today, I totally saw this going in the direction of competing with Sketch and XD as well as InDesign. Is the combination of print and digital design in one application the objective of Publisher?
  18. I would like to make two suggestions for a solution: 1. Double-clicking the Text Table Tool to set up the table properties. Example: I've had to set up tables that are 12 columns wide by 3 columns deep. To drag out 12 columns in a width and then to resize the table requires extra steps. Adding specifications before the able is created would be easier for the workflow. 2.In the Table palette, include a space for rows and columns, so the Text Table Tool box will conform to the rows and column needed within the parameters drawn.
  19. The Table Text Tool needs some work. I found a couple of issues: 1. The columns and rows delete one-by-one only, even though multiple rows are selected and the UI states "Row(s)". 2. There isn't an option to set up the table rows and columns. The table is dynamic, which is great, but sometimes the table needs an initial setup.
  20. Press the tab key with nothing selected to Toggle UI. Also under View > Toggle UI
  21. If Affinity doesn't do it, there probably will be a third-party plug-in like Markzware did with Q2ID.
  • Create New...

Important Information

Please note there is currently a delay in replying to some post. See pinned thread in the Questions forum. These are the Terms of Use you will be asked to agree to if you join the forum. | 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.