Jump to content


  • Content count

  • Joined

  • Last visited

About CarlM

  • Rank

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I reported this bug in the Publisher Beta forum a week ago and didn't receive a response. It is also a bug in the retail version 171.404. If I use the Place function to import text into a publisher file, the auto spellcheck identifies words not in the dictionary but is unable to add those words using "Learn" It cannot "Unlearn" either. The History shows that even if the word is fully highlighted it isn't being detected and Publisher records it as an empty string. This only seems to occur when the Text Frame is created in a Master Page and not when a Text Frame is created on a document page. Publisher Spell Check Test Doc.afpub Publisher Spell Check Test.docx
  2. I;ve now discovered that Placing an MS Word .DOCX file into publisher Text frames results in the same problem. I noticed it when going back through the pages trying to correct some red underlined words. To test it I created a new document and placed the DOCX file into the frames. I even added in a couple of words that weren't in publisher dictionary and attempted to get publisher to "Learn" them. The result was exactly as in my previous post. The text frames were created in a Master page - if that helps. This is a bit of a deal breaker unless its something I'm doing wrong in which case someone please tell me what I've idiotically done wrong.
  3. Agreed. I meant to write "If not yet." I should proof read before hitting Submit
  4. If people simply want to be able to make use of old projects originally created in InDesign then I can see their point - to a degree. To call not having the ability to read and write to IDML a deal breaker is simply ridiculous though. It's a useful to have for those making the transition but honestly if you're migrating to Affinity from Indesign then for goodness sake have some common sense and run both applications until you've finished with the projects you built on the Adobe platform. Incidentally, I don't hear the same shouting about Quark Xpress, but I suppose that's because Quark doesn't use a subscription model so owners can continue using their copy of Xpress after they have migrated but once you stop paying your Adobe sub you're beggared. But it's not Serif's fault or problem that people have bought into the Adobe model. I have the photography Creative Cloud subscription and will continue to pay it because I don't have a problem with that but also need to have it because I teach the software to photographers, but if I need to add Affinity Photo to my arsenal along with publisher and Designer then I'll buy it and use it as necessary as part of the excellent Persona concept, but I won't necessarily abandon Adobe in the process - but that's my choice. When InDesign was first released it frankly wasn't very good and certainly wasn't compatible with Quark. It's taken 20 years to mature in to the industry standard product it has become yet some Affinity users seem to want everything now - not going to happen sorry. I think that to become a success then Affinity Publisher has to take it's own path just as InDesign did all that time ago. If in the process an IDML converter is part of the deal then fine. If not then live with it. Frankly there are far more important functions that should be added such as a proper package manager and addressing some of the apparent pdf/x conversion issues (though I suspect many of the complaints are down to a failure of users to properly understand the PDF/X protocols). I can understand that collaboration might be an issue if you're working with an InDesign user (though one has to ask why are you working with two incompatible software packages in that way?). I also understand that it might be a must have if you receive IDML files from a client to work on but it makes no business sense to work like that in the longer term. IF you regularly receive IDML or INDD files it would make sense to continue to retain InDesign until Publisher is mature enough to stand on it's own two feet and become another mainstream product like Quark and InDesgn (which may not be that far off).
  5. Are you a congenital idiot or just a Troll? Actually probably both given you don't identify which app you're referring to and given your reference to Gimp (I suspect you probably are one) I suspect that you're discussing (after a fashion) Affinity Photo. None of your three observations seem to have any relation to the real world. I don't use Affinity Photo because I'm a Lightroom/Photoshop user but I downloaded the trial just to test your assertions and can only think that you meant to post on another site in a galaxy far far away because I couldn't identify any of the so-called faults you describe. By the way - it's spelled "pixelation" not pixilation (which would be a reference to transmogrification into a mythological tiny creature with pointy ears and a bizarre fashion sense from Cornwall).
  6. If you write any text directly into Publisher or import a Word document then the auto spell check works as expected. Any underlined word can be added to the personal dictionary. Copy from a Word Document (or Notepad) and pasted into a Text Frame - no problem either. However, if I copy and paste text from PagePlus X9 the auto spell check identifies words not in the dictionary but the words cannot be added into the personal dictionary. If the words are typed into a fresh publisher document and spellchecked then they can be added but cannot be unlearned from the first document. From that point on the spell check won't allow the addition of any new words into the dictionary. I've attached a sample publisher file that demonstrates what I mean. And this screenshot from the History panel shows that the highlighted word isn't being read. there shouldn't be any reason why this happens when copying and pasting text or why it only seems to occur with PagePlus text. Test Document.afpub
  7. Keynote and the website make it clear that Studiolink doesn't actually run all the apps as one but allow access to the functionality of the sister apps from within the application you are working. "With Affinity Publisher, you can directly link to your other Affinity apps through StudioLink. The first technology of its kind, this revolutionary feature takes the pain out of publishing by allowing you to instantly switch to the advanced photo editing features of Affinity Photo and precise vector tools of Affinity Designer without ever leaving the app." As Rick G said, do the heavy lifting in the app and once you're in Publisher (for example) tweak if needed. I don't believe there was ever any suggestion that Studiolink was going to create one massive super app that can do everything. Personally I wouldn't want that anyway.
  8. CarlM

    Jagged line

    Except it doesn't work unfortunately. I reported it a long time back during an earlier beta but it's never been fixed. Neither Learn nor Ignore work.
  9. Hi Timo I just ran a test and encountered the same issue. The Outer Shadow Text layer in the exported pdf is a completely different shade of the colour you create in Publisher and appears much more opaque just as you identified. I have a fully colour managed system and just tested the pdf exports with a number of different settings with the same results. I don't know how I missed that one during Beta testing.
  10. I can repeat the bug in .420 as well. It work as intended in .404
  11. Go to Export and click the More... button. Halfway down you'll find the Colour Space and ICC profile options. You will need to drop the profile into a folder, usually Windows>system32>Spool>drivers>color if you're using Windows but it is possible that there is a dedicated Affinity folder to add them to.
  12. Do you mean page imposition so that the sheets are grouped as they will appear when you assemble the hard copy pages e.g. sheet 1 - 1,8,2,7, sheet 2 - 3,6,4,5? Affinity Publisher doesn't do imposition (neither does InDesign) and for that you'd need to use some imposition software like Montax Imposer or PDF Booklet Creator to assemble the pages in print order. You do need to remember to set the document up with facing pages though.
  13. Photoshop is a photo editing application and Publisher a DTP application - two different beasts. It's better to compare like against like rather than apples and Tow Trucks. Adobe InDesign not only doesn't have a snapshot option but doesn't have a History panel either and these two applications are normally compared against each other. I'd guess that a snapshot option for a DTP application is a lot more complicated to implement than in a photo editing app. It's also worth bearing in mind that Indesign currently costs £238 per year as an individual app compared to the likely £48.99 (or whatever the pricing for each Affinity app is at Publisher launch) for the release version of Publisher. I don't expect it to compare 100% with Indesign yet but already it has features that Indesign doesn't and runs so much faster.
  14. The dictionary files that come with APub look like standard Hunspell files: C:\Program Files\Affinity\Publisher Public Beta\Resources\Dictionaries\ The User dictionary is here but it's not user editable: C:\Users\Carl\AppData\Roaming\Affinity\Publisher\1.0 (Beta)\user\dictionary.propcol
  15. CarlM

    Replace a pdf-file

    It works for me. Did you make sure that the "include printers marks" box was ticked in the Export Settings and the boxes for the setting you want to appear in the PDF were also ticked? If they all were then I'm not sure why they shouldn't have appeared in the output PDF.