Jump to content

Last Chance

  • Content Count

  • Joined

  • Last visited

  1. It is being experienced in Publisher. The OS is Windows 10 and yes, this is when opening native .afpub files. It's easy enough to correct (find/replace), but thought I'd just raise the issue 🙂 Here's a snapshot:
  2. I am finding that text from 1.7 files are being transformed when loaded saved in 1.8. The letters 'ti' (as in 'ambitious') is now shown as 'Â' (i.e. 'ambiÂous'). Sorry, but I can't tell you if it was there on loading the document into 1.8, or after it was saved.
  3. To clarify: the issue is that it crashed (closed down) Publisher and I restarted the computer each time.
  4. I too am having problems loading many existing 1.7.x.x files with the latest version ( on a Toshiba laptop running Windows 10. A smaller, single page document, however, was loaded earlier without a problem. Could it be the recent Windows update that was recently installed? Quite happy to upload the .afpub file to Dropbox link if you wish.
  5. Thanks all, most helpful. I'll see which is the best option. Fixx, I just reckon that some correct auto-correction is better than none at all and a space/en-dash/space is one that should be invoked virtually every time. Date ranges, however, are always wrong (e.g. 1910-1920 should be 1910–1920), but I agree it is difficult for any program to distinguish when the correct instance is required.
  6. Another simple feature to include would be the auto-creation of the en-dash as it is typed – as with MS Word. It saves having to use Alt-0150 each time – is an en-dash - is the hyphen Thanks!
  7. Apologies if this feature has already been suggested, or even implemented, but I cannot find either. The feature is one found in InDesign and which I found genuinely useful: a 'size to fit' for textboxes. This would cause any text boxes to resize, whether it was an overflow or to shrink to the available content. I seem to remember it was Alt-Ctrl-C, but perhaps someone can correct me.
  8. It's called forward planning. My point is that I publish books and certain projects are nearing completion. So should I throw money at the Adobe solution (expensive and their support sucks - unlike Serif, I would like to point out), which means committing to a minimum monthly fee of £20, or £50 per month for the full Creative Cloud "experience". I am plodding away quite happily with Affinity Publisher & Photo for the small magazines I'm committed to, but once the next book project kicks in then we are talking of at least six months development to get it print-ready (it's about 400pp and liberally illustrated). So I need to commit one way or the other quite soon, e.g. although Publisher will soon allow the importing of InDesign files, the same cannot be said for the reverse. My own book will follow this and will probably be two volumes, 800pp; again liberally illustrated, so this isn't a light undertaking. Don't get me wrong - I am impressed (stunned!) by what Publisher can offer for £50 and would quite happily pay double that for the features planned. It's the "not knowing" that make my buttocks clench 😉
  9. Is it obvious? Remaining quiet and being patient is fine in a non-commercial world where deadlines do not exist, but it would be nice to be kept abreast of the actual progress and a possible timeline - we do need to know one way or the other. Do I switch back to InDesign or should I remain with Affinity?
  10. No, it was not reproducible on a blank doc. I then tried to replicate the same document, even to including a baseline grid and I could not replicate the problem. I also loaded the original document and that seems fine now, so I'm guessing it was a glitch while I worked on the original.
  11. Just faffing about with the latest Beta test (, but I noted that with 'Preview' mode on, I'm unable to scroll past the first full spread (pp 2 & 3; about two-thirds down this spread) of a 104pp document. Switching Preview off allows scrolling of the document as normal, but switching it back on and any action makes it jumps back to the first spread.
  12. You can also export the document as a PDF and import this, complete with endnotes (footnotes are a problem though). However, this is a problematic process as no paragraph or character styles are imported and there is a line break for every line. While I think the line breaks could be stripped out, the loss of all the styles is a major headache.
  13. I think we'll have to "agree to disagree" here Pyanepsion My experience with importing Word DOCX files into InDesign has, on the whole, been very good with little, or no alterations necessary. Importing raw text files of even RTF just creates a lot of work, IMHO. As I said before, Affinity Publisher's handling of Word DOCX files is "OK" as at least all the paragraph and style definitions are included - it's just that the fonts, sizes etc. can (but not always) be altered, which is a simple matter of correcting the definitions. Generally, this is much better for me when dealing with entire books. My current book is about 300,000 words and this will probably end up nearer 400,000 when completed. I'm not sure how large, or small, your client's documents are, but for a book this size having some of the work done is better than none at all
  14. Guys, the only reason it's "not a good idea" to import a DOCX is because Affinity Publisher does not quite handle it properly - yet. It's not bad, but some of the Styles do get screwed for some reason and apparently the developers are working on it. I learnt this after I sent an email to Serif, to which they replied promptly. But it still imports all the definitions and so can be edited and applied, so a lot easier than using RTF, which would lose all the definitions completely. As a budget piece of software, though, I am amazed at what Affinity Publisher CAN do! Sure, it will never aspire to be as good as InDesign, which I currently use, but as a replacement it's very hard (impossible?) to beat on price and for this reason, I think I will drop that money pit (InDesign ~£240 per annum) and swap over. By the time my next book is ready to publish, I'm hoping the footnotes & endnotes will be sorted as that is the only major feature I miss so far.
  • Create New...

Important Information

Please note the Annual Company Closure section in the Terms of Use. 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.