Search the Community

Hi, I encountered with some problems with pictures after instalation of v. .305: when I am placing text into a new document, I get this (see import.png); when I try to move a picture a little bit and I release the mouse button, it comes back to its previous position (sticky picture?) and the text bellow it goes up row-by-row every time I reposition it; sometimes the picture disapper, but its frame stays. Supprisingly good, I didn't find any problems I mentioned, if the picture is pinned. Great. I also attach the DOCX file I have problems with. The pictures are at the end of the document. книгата.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.

Publisher is not checking if the content of a file is corresponding to the expected file format. Means: Rename any file to xxx.docx and Publisher hangs. Same happened with rtf-import. The attached text file contains one x, was meant to be HTML and was saved as .docx instead. crash.docx

Attached you will a small docx with a table of 2 rows and 3 columns. When the file gets placed the table gets huge in width (2830,4 mm each column). The docx is generated by LibreOffice. tabellentest.docx

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

Sir, I have imported a 44 pages PDF X/3 document in 1.7.133. This document has already been successfully generated by Foxit Phantom Pro. It was a combination of Scribus 1.5.4 PDFX/3 files and .docx imports. The whole document was printed in Germany and went without a remark through the pre-print analysis of the printing company. Prints are perfect. The page shown in attachment was a .docx file imported in Foxit. 1) Publisher Import: Issue 1: Compared to an Acrobat Reader view, I notice that the text is not properly "Left justifed" anymore. See the jpg in attachment, name ending with "...start.jpg", there is a blank on the left of "333" Acrobat and prints show all end lines perfectly justified. Issue 2: the text frame was centered in the original document. Affinity shows a wider blue frame correct on the left side, but on the right side there is like a blank character that was added at the end of each line 2) I have just changed the "line space" of 9pt to "Exactly" and 150%, i.e.13.5 pt Underlined texts are not managed properly. The text "www.tramania.com" of the next paragraph "loses" its underline. This underline line stays at its original position and pollutes the previous paragraph that was modified. I did not find a way to delete this line Note: Everything is default. No special styles, etc First file loaded with a fresh 1.7.133 install Regards, Philippe

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.