Richard S

Thanks. Today, it seems that nothing (and no-one) likes me. ;-) Better luck next year?

Thanks. Great idea: Setting the Windows Scaling to 120% is a reasonable compromise... until Affinity resolves the issue. The "Export" & "Cancel" buttons are visible.
(Forum won't let me upload a screenshot.)

Thanks for that tip about the LibreOffice extension. I hope Affininty Publisher is soon updated to at least provide a means of exporting text and stories, so that the same content can be used in other programs.

I've created a booklet using Publisher 1.7.1 by assembling text from several sources direct into Publisher, and then tweaking the result. So the text in Publisher is now the only "master."
I now want also to create a Kindle version, with flowing text. I have PagePlus X9, Sigil, Libre Office, and various Amazon tools. If possible, I do not want to install / buy yet more software.
Recently, I've published other books from PagePlus X9 in flowing ePub3, then used Amazon's tools to convert into Kindle formats. This has worked well: Amazon has reported no problems.
Questions:
What is the best way to convert a Publisher document into a flowing Kindle eBook? What is the best way to extract the story text from a Publisher document, for use elsewhere? Do I really have to recreate this document in PagePlus X9 (or another program) before exporting it as a flowing ePub? Are there other tools which would make any of this easier?

I've created a booklet using Publisher 1.7.1 by assembling text from several sources direct into Publisher, and then tweaking the result. So the text in Publisher is now the only "master."
I now want also to create a Kindle version, with flowing text. I have PagePlus X9, Sigil, Libre Office, and various Amazon tools. If possible, I do not want to install / buy yet more software.
Recently, I've published other books from PagePlus X9 in flowing ePub3, then used Amazon's tools to convert into Kindle formats. This has worked well: Amazon has reported no problems.
Questions:
What is the best way to convert a Publisher document into a flowing Kindle eBook? What is the best way to extract the story text from a Publisher document, for use elsewhere? Do I really have to recreate this document in PagePlus X9 (or another program) before exporting it as a flowing ePub? Are there other tools which would make any of this easier?

Thanks everyone. I have now published a Kindle version as well as a printed version.
My method was roundabout and probably not ideal, but used the tools I'm familiar with. It also seems to produce cleaner ePub encoding:
Prepared the printed version using Affinity Publisher, exported this as PDF-x1a, sent it to the online printing service: Printed version looks good. Tried copy/paste of text from Affinity Publisher and from Adobe Reader, but found that the resulting unformatted text needed too much work. Imported the PDF-x1a into Serif PagePlus X9, in "flow" mode. This resulted in a separate "story" for each page, and put each page number into a separate story. Used "Edit Story" in PagePlus X9 to export each text story as a separate RTF file. Then re-assembled these using LibreOffice to produce a clean .ODT master file. In PagePlus X9, created a new iPad mini document, inserted the .ODT text file. Inserted the images. Tweaked & cleaned the text and formatting. "Published" the document from PagePlus X9 as a Flowing ePub3, adding a hyperlinked ToC. Previewed this using MS Edge. Made changes, then repeated this... Uploaded the ePub3 to Amazon KDP, uploaded the cover image, previewed the converted result using Amazon's online previewer, also downloaded the converted .mobi file and checked this using Amazon's offline Kindle Previewer software. The Amazon KDP service happily accepted the flowing ePub3 file created using PagePlus X9. I clicked the final "submit" button at about 10pm... by the early hours next morning, my new book was live for sale on Amazon Kindle.
I have also exported the final text using "edit story" in PagePlus X9 as an RTF file, to update my master text file in LibreOffice.
Serif PagePlus X9 can also publish documents as ePub2 or as .MOBI files, reliably. But I now prefer to use the newer features provided by Amazon's newer tools.
Obviously I would like Affinity Publisher (very soon) to provide:
A. Text export feature. Even just a basic feature; ideally something like PagePlus's "edit story" / WritePlus feature.
B. ePub export mode. For creating eBooks directly, or more likely in a format which is compatible with eBook creation services & programs.
BTW. I have much to learn about how to publicise & market Kindle eBooks.

Could this please be made clearer in Affinity Publisher's "help" or even on the PDF dialogues?
My commercial printing service wanted the PDF to contain "separate pages" rather than "spreads." As someone who is new to commercial printing, it was not obvious how to translate the language of the printer's requirements into language used by Affinity.
To clarify:
Affinity's "All Spreads" PDF exports eg. facing pages of a booklet as double-page spreads; but as viewed... ie. not arranged for printing. Affinity's "All Pages" PDF exports eg. facing pages of a booklet as a series of single pages, in consecutive order.  

Thanks. Although I also publish webpages, I've never tried converting them to eBooks; probably because I started publishing eBooks only after getting Serif PagePlus. In fact I needed also to copy/paste text to update some of my webpages while creating these books.
I've also updated Sigil, but chose not to use it this time.
PagePlus (or Affinity Publisher) are way over the top for producing simple eBooks; especially the flowing ePubs I prefer. But, when you have a hammer...
I needed to publish this project as a printed booklet, as a Kindle eBook, and on webpages: I value flexible import & export options from programs, to avoid the need for recreating text. Also, some of my text and images were originally created decades ago using long lost tools: I value programs which can export material in "industry standard" formats so that the material can be imported into other or newer programs.
BTW. For similar reasons, I do not use Amazon Kindle's DRM: I prefer to trust people who buy my books and not to leave the material "locked" within one company's software. There is some "leakage," some of it via "sharing" websites, but probably to people who would never have paid for a copy.

Thanks everyone. I have now published a Kindle version as well as a printed version.
My method was roundabout and probably not ideal, but used the tools I'm familiar with. It also seems to produce cleaner ePub encoding:
Prepared the printed version using Affinity Publisher, exported this as PDF-x1a, sent it to the online printing service: Printed version looks good. Tried copy/paste of text from Affinity Publisher and from Adobe Reader, but found that the resulting unformatted text needed too much work. Imported the PDF-x1a into Serif PagePlus X9, in "flow" mode. This resulted in a separate "story" for each page, and put each page number into a separate story. Used "Edit Story" in PagePlus X9 to export each text story as a separate RTF file. Then re-assembled these using LibreOffice to produce a clean .ODT master file. In PagePlus X9, created a new iPad mini document, inserted the .ODT text file. Inserted the images. Tweaked & cleaned the text and formatting. "Published" the document from PagePlus X9 as a Flowing ePub3, adding a hyperlinked ToC. Previewed this using MS Edge. Made changes, then repeated this... Uploaded the ePub3 to Amazon KDP, uploaded the cover image, previewed the converted result using Amazon's online previewer, also downloaded the converted .mobi file and checked this using Amazon's offline Kindle Previewer software. The Amazon KDP service happily accepted the flowing ePub3 file created using PagePlus X9. I clicked the final "submit" button at about 10pm... by the early hours next morning, my new book was live for sale on Amazon Kindle.
I have also exported the final text using "edit story" in PagePlus X9 as an RTF file, to update my master text file in LibreOffice.
Serif PagePlus X9 can also publish documents as ePub2 or as .MOBI files, reliably. But I now prefer to use the newer features provided by Amazon's newer tools.
Obviously I would like Affinity Publisher (very soon) to provide:
A. Text export feature. Even just a basic feature; ideally something like PagePlus's "edit story" / WritePlus feature.
B. ePub export mode. For creating eBooks directly, or more likely in a format which is compatible with eBook creation services & programs.
BTW. I have much to learn about how to publicise & market Kindle eBooks.

You can untick the facing pages in the Document Setup set up and the pages will be single, this can be re ticked when you want to work across facing pages for text flow etc.

I figured out an easy way to feather edges in AP.......use the f(x) called Outer Glow. Change it to your images existing color. It really was that easy. 

Very much agree.

I need a story editor because I have to change words, terms or entire paragraphs for many, many reasons beyond my control long after I receive them and place them. "Fun" before deadline. Customers, politicians, managers, communication experts or the common pygmy.  I belive this is a common scenario. It is not word processing like what the author did for days. It is final adjustments to the text or layout.
That work is clumsy and slow in the WYSIWYG page layout mode. Slow doesn't buy you food or clothes. Why would I wish to work in the worst mode available when I have to work with 40 or 100+ pages of text in complex layout? That is why you can work in outline mode or just view the selected object in Designer. Focus and speed! Thats why story editors exist. Somebody needs to focus on the text alone in the final phase. 
Whatever. If it makes sense to integrate Designer and Photo into Publisher - a story editor makes sense too. 
So, pretty please, with sugar on top, add a story editor.

Thread moved.

There would be much less uncertainty if "All Pages" was default and you had to to select "All Spreads" intentionally to create non-printable output.

Thanks. But as you'll see from replies above, other PDF viewing software also have problems with PDFs created using Affinity Publisher.
At the very least, users of Affinity Publisher should be warned that their PDFs may not display properly on millions of Windows 10 PCs.
One possible temporary fix during the next update would be to change the preset settings, so that the Export... PDF (Web) embeds subsets of "All Fonts."

Thanks. But as you'll see from replies above, other PDF viewing software also have problems with PDFs created using Affinity Publisher.
At the very least, users of Affinity Publisher should be warned that their PDFs may not display properly on millions of Windows 10 PCs.
One possible temporary fix during the next update would be to change the preset settings, so that the Export... PDF (Web) embeds subsets of "All Fonts."

Thanks. But as you'll see from replies above, other PDF viewing software also have problems with PDFs created using Affinity Publisher.
At the very least, users of Affinity Publisher should be warned that their PDFs may not display properly on millions of Windows 10 PCs.
One possible temporary fix during the next update would be to change the preset settings, so that the Export... PDF (Web) embeds subsets of "All Fonts."