William E Lee Posted December 27, 2019 Posted December 27, 2019 My spell check is unable to deal with people's names, the names of places, etc. Westchester, for example, Vanhooten, for example... Veronica, for example. All perfectly acceptible words, and capitalized in any event which identifies them as proper nouns, which means they should be learnable. When I use the define function it successfully returns, for example Westchester, but still will not allow me to move on past that point. In many program the spell check will allow you to check specific highlighted text. Publisher simply checks everything and freezes up when it encounters words such as these. This creates the horrible the need for the round about of exporting the text to some other program with functioning spellcheck. And yess I have the language setting both in the character pane and in my operating systems set to English. What gives?
walt.farrell Posted December 27, 2019 Posted December 27, 2019 There was, if I remember correctly, a bug fixed in the 1.8 beta, about not being able to learn words inherited from a Master Page. Would that explain your issue? -- Walt Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases PC: Desktop: Windows 11 Pro 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 Laptop: Windows 11 Pro 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU. Laptop 2: Windows 11 Pro 24H2, 16GB memory, Snapdragon(R) X Elite - X1E80100 - Qualcomm(R) Oryon(TM) 12 Core CPU 4.01 GHz, Qualcomm(R) Adreno(TM) X1-85 GPU iPad: iPad Pro M1, 12.9": iPadOS 18.3, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.0.1
William E Lee Posted December 28, 2019 Author Posted December 28, 2019 Somewhere about half through a two hundred page novel, spell check died. It hung on the first word it wouldn't solve and would go no farther. No learn, ignore or whatever worked, it hung on the word and wouldn't let go. Next didn't work.
Staff Patrick Connor Posted April 17, 2020 Staff Posted April 17, 2020 Sorry. Thank you for reporting a problem using 1.7.x . It appears that a member of the Affinity QA team didn't get round to fully investigating this specific report posted in the bugs forums. We are very sorry for this oversight. Yours is one of a number of reports that I am posting this apology to, using an automated script. Now we have released 1.8.3 on all platforms containing many hundreds of bug fixes, and we hope your problem has already been fully addressed. If you still have this problem in the 1.8.3 release build, then the QA team would really appreciate you reporting again it in the relevant Bugs forum. Report a Bug in Affinity Designer Report a Bug in Affinity Photo Report a Bug in Affinity Publisher Each of those links above contains instructions how best to report a bug to us. If that is what you already did in this thread just copy paste your original report into a new thread. We appreciate all the information that you have including sample files and screen shots to help us replicate your problem. This thread has now been locked as the QA team are not following the threads to which this automatic reply is made, which is why we would appreciate a new bug report if you are still have this problem in the current 1.8.3 release build. Patrick Connor Serif Europe Ltd Latest V2 releases on each platform Help make our apps better by joining our beta program! "There is nothing noble in being superior to your fellow man. True nobility lies in being superior to your previous self." W. L. Sheldon
Recommended Posts