Search the Community

When I tried the beta, I was immediately sold. I was up and running from an RTF template in moment, all my styles importing. Now when I import, they styles don't come in. When I tried to do it in different ways, Publisher crashed on me. I'm going to give it one more try on the new 16 page project I'm doing, then going back to Adobe until I figure this out. Did something change in how things import or come in?

There are some bugs with the new Publisher .docx import feature: From a new blank document in macos Pages (version 7.1 (5683)) I used the default styles to make a simple document containing the Title, Subtitle and Body styles, then exported to .docx. On import into a Publisher textframe, the paragraphs are have 'Start: On Next Page' applied in the Flow Options, even though this wasn't part of the style in the original Pages document. (So on import, only the first paragraph appears, with the text overflow icon showing red. By option-shift clicking on the overflow icon, a number of new pages are created for each of the paragraphs in the document.) Also, the original font Helvetica Neue Bold has small caps and italics applied on import. Original Pages file and .docx export file attached. (Full specs of my system in sig.) docx-export-test.pages docx-export-test.docx

Can anyone tell me what this Great Blue Anchor signifies? It appears at the top of a placed Docx file. but not an RTF file or a TXT file. Tia. WIN 7, AFF Pub. v .312

I tried to import a .docx file and it locks up every time.

There are a number of requests here for InDesign/Word DOCX/IDML/Markdown import as well as EPUB export, but nothing really looking at the big picture of how this should fit within a workflow of producing content for web and in print. Most of these seem to imply replicating InDesign's functionality – but these features could be much better implemented. In my experience, InDesign's text import and EPUB export are both rather grim. The Word import function doesn't import styles in a particularly useful manner, often taking far too much from the source document that then needs to be cleaned out. I use Pandoc instead to convert DOCX to Markdown and clean up the file with a text editor. I can then export to HTML or EPUB for a Web version, and ICML for a nicely typeset print version with InDesign. Rather than have Affinity Publisher become bloated with Web features that become quickly outdated and don't work properly in the first place, as InDesign has, I would like to see it focus on professional typesetting for print while integrating with other applications to enable technology-independent content creation.