wilkinson.bj

Hi, Jon, I've worked with the original file through so many iterations that I've lost the precise copy from which I produced the screen shot. I apologize for that. I should have seen this request coming. I started over again and produced the attached file, with history saved this time. I hope it helps. The gist of it is that the original Autoflow from page one created all the pages necessary to contain the document but the text displayed only page two, with no evidence of text on page three or beyond. I manually flowed page two to three, three to four, etc., until I came to chapter two, at which point I inserted an odd page break. At that point, I was able to duplicate the original screen shot situation, where text was not visible after a manual flow to the next page, but with a CNTL+A command, the highlight where text should be displayed is visible. The history shows all of this. I hope this helps. It seems to me to be a complicated issue, but then I suppose many of your beta issues are complicated. Thank you all for the great work you've done so far and continue to do. I'll say one thing about this process. In my attempts to find out if I did something wrong or if I exposed a bug, I'm getting to know my way around AP quite well, so that when all of this produces the first release version, I'm going to be pretty smooth at doing what I need to do to produce the work I produce. Good luck! Recreate WEST Test.afpub

Affinity Publisher Public Beta - 1.7.0.249 on Windows 10 The setup: Create new file. Create a master page for Chapter Title (single page, recto) and a master spread (verso/recto, complete with text boxes. Create page and apply Chapter Title master. Create spread for pages 2 and 3 and apply verso/recto master to it. Place an RTF file that will result in approx 350 pages, beginning on page 1 (Chapter Title,) and manually flowed onto pages 2 and 3 (verso/recto,) (because if I autoflow from page 1, all newly-created pages, including 2 and 3, will have the Chapter Title master automatically applied.) So far, so good. However, at the end of each chapter, I need to insert an odd-page break, and then apply the Chapter Title master to the next odd page. When I do so, the text is apparently deleted on the page where I apply the new master. Applying a new master (either of my masters) to any page(s) has the same effect. The text on those pages is deleted. Alternatively, if I manually flow from page 1 to 2, then to 3 and beyond, the flow will not cause a conversion of master on consecutive pages as it does with autoflow, however at some point (in one test about 40 pages in, the text will become invisible on the next page. What I mean by invisible is that I cannot see the text, but it is apparently "there," because if I use CNTL+A to highlight all text, I can see the highlight on an otherwise blank page (see attached .pdf.) So in some way, the text exists; I just can't see it. If I apply a new master to any next page (say, to begin a new chapter,) then the text disappears again, by which I mean if I use a selection method like CNTL+A, there are no highlights on the newly-mastered page to indicate that text exists in some way that is invisible. Nice that autoflow works on re-opened files now, but I would not expect it to convert pages I've already created to new masters. Thanks for all the good work. Onward and upward. Bruce Wilkinson Spread.pdf

Thank you for your response, Walt. I understand, now, that the General language option can't be changed until a future update. My concern with the Auto-Correct setting that can be changed but reverts as soon as Preferences is closed, is that I would expect it to set some standard spelling conventions between, for instance, English UK and English US -- colour vs. color, to name one of many. My guess is that the language setting exists in Auto-Correct Preferences for this reason. That said, at this point of the beta process, I imagine there are much bigger issues to address; that this one will be addressed in due time, and I've found the progress through the beta releases to be satisfying. Thanks again for the considered reply.

When I add an Auto-Correct entry of my own, for instance, convert three asterisks to an em-dash, the auto-correct does not occur in document text. I have also tested some of the built-in auto-correct entries and the ones I've tested do not function, either. Windows, Beta 1.7.0.157

In Preferences/General, I cannot reset language. The field is grayed out. In Preferences/Auto-Correct, another language may be chosen, but it is not persistent. It reverts to English UK, perhaps because the default in the General Preferences cannot be reset

Patrick and all readers, I may have found the problem with my original .rtf file. It was generated from Scrivener. If I convert the original .docx file to .rtf, the new file imports into A.Pub. 1.7.0.133 fine. This appears to be an issue with Scrivener's configuration of an .rtf file, rather than with Affinity Publisher Beta's ability to import .rtf.

Thank you for your response, Patrick. Further information: Publisher Beta 1.7.0.128 (I did not have a problem with this file in 1.7.0.58). Windows 10. The issue does not occur when I import text from this file into a default "new document." It does occur when I have modified page size, margins and other specifications in new document setup. I can import a .txt file under all circumstances I've tested so far. Again, thank you. I'm enjoying the beta process and I will continue to tinker with this problem in hopes of being able to give you more, and more specific, information. IM 9-19-18.rtf