AffinityAtWork Posted August 2, 2023 Share Posted August 2, 2023 I followed https://affinity.help/publisher/de.lproj/index.html?page=pages/Text/autoCorrect.html?title=Autokorrektur und Rechtschreibprüfung bei der Eingabe and https://forum.affinity.serif.com/index.php?/topic/98911-how-do-i-add-additional-dictionaries-to-affinity-publisher/ but my additional de-CH dictionary won't work. Roughly translates to: Not supported language. The document contains languages (de-CH), that don't have corresponding dictionaries. Btw, paths and download links are outdated and need an update. Quote Link to comment Share on other sites More sharing options...
Dan C Posted August 2, 2023 Share Posted August 2, 2023 Hi @AffinityAtWork, Sorry to hear you're having trouble! Can you please open Publisher then navigate to Edit > Settings > Tools and then select the 'Open' option for the Additional Dictionaries folder. Please now take screenshots of the Windows Explorer dialog that opens, including the folders and their contents so that I can check this has been added correctly. 2 hours ago, AffinityAtWork said: Btw, paths and download links are outdated and need an update. I can confirm the FAQ you have linked is for V1 and not V2 of the Affinity apps and therefore the file/folder paths may not match your V2 installation - however all of the download links continue to work as expected for me, have I misunderstood the links you are referring to please? Many thanks in advance Quote Link to comment Share on other sites More sharing options...
walt.farrell Posted August 2, 2023 Share Posted August 2, 2023 2 hours ago, AffinityAtWork said: Roughly translates to: Not supported language. The document contains languages (de-CH), that don't have corresponding dictionaries. Also, if you downloaded the files by going to GitHub yourself, there is a good possibility you may have downloaded them in the wrong format. It is better to download from the links in the second post of that FAQ topic, which will give the correct format. To check, you could open your downloaded files with a text editor. If they contain HTML code, that will explain them not working. They must be plain text. AffinityAtWork 1 Quote -- 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.1, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.0.1 Link to comment Share on other sites More sharing options...
AffinityAtWork Posted August 2, 2023 Author Share Posted August 2, 2023 38 minutes ago, Dan C said: Please now take screenshots of the Windows Explorer dialog that opens, including the folders and their contents so that I can check this has been added correctly. 3 hours ago, AffinityAtWork said: 38 minutes ago, Dan C said: download links continue to work as expected for me, have I misunderstood the links you are referring to please? https://affinity.help/publisher/de.lproj/index.html?page=pages/Text/autoCorrect.html?title=Autokorrektur und Rechtschreibprüfung bei der Eingabe "Webseite" points to OpenOffice Quote Link to comment Share on other sites More sharing options...
AffinityAtWork Posted August 2, 2023 Author Share Posted August 2, 2023 34 minutes ago, walt.farrell said: Also, if you downloaded the files by going to GitHub yourself, there is a good possibility you may have downloaded them in the wrong format. It is better to download from the links in the second post of that FAQ topic, which will give the correct format. Don't remember where I got the oxt file from, but you were right! After using your links, it works now! Thanks a lot for your help guys! Dan C 1 Quote Link to comment Share on other sites More sharing options...
walt.farrell Posted August 2, 2023 Share Posted August 2, 2023 You can't use those files. You must have .aff and .dic files. If I remember correctly, though, you could perhaps rename the .oxt file to .zip, unzip it, and you might have the files available then that you need. Better, though, to use the files from the FAQ Quote -- 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.1, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.0.1 Link to comment Share on other sites More sharing options...
Dan C Posted August 2, 2023 Share Posted August 2, 2023 2 hours ago, AffinityAtWork said: https://affinity.help/publisher/de.lproj/index.html?page=pages/Text/autoCorrect.html?title=Autokorrektur und Rechtschreibprüfung bei der Eingabe "Webseite" points to OpenOffice Thanks for letting me know, these are OpenOffice dictionaries and therefore this link is correct - though I can certainly understand the confusion. 1 hour ago, AffinityAtWork said: Don't remember where I got the oxt file from, but you were right! After using your links, it works now! I'm glad to hear this is now working as expected for you Quote Link to comment Share on other sites More sharing options...
AffinityAtWork Posted August 2, 2023 Author Share Posted August 2, 2023 Wait, I thought that you guy officially support LibreOffice now and ditched OpenOffice? All the github links point to LibreOffice, not OpenOffice 🙂 Quote Link to comment Share on other sites More sharing options...
Dan C Posted August 2, 2023 Share Posted August 2, 2023 2 minutes ago, AffinityAtWork said: Wait, I thought that you guy officially support LibreOffice now and ditched OpenOffice? Affinity (and OpenOffice/LibreOffice, amongst others) use Hunspell dictionary support for spellchecking - meaning you can use either OpenOffice or LibreOffice dictionary files in Affinity, provided they are in the correct format as Walt mentioned AffinityAtWork 1 Quote Link to comment Share on other sites More sharing options...
AffinityAtWork Posted August 2, 2023 Author Share Posted August 2, 2023 Ahh.... that makes sense. Anyway, I find the github page to be easier to download than OpenOffice Extensions. This is where I got the misleading oxt file in the first place 😄 Dan C 1 Quote Link to comment Share on other sites More sharing options...
walt.farrell Posted August 2, 2023 Share Posted August 2, 2023 53 minutes ago, Dan C said: Thanks for letting me know, these are OpenOffice dictionaries and therefore this link is correct - though I can certainly understand the confusion. Perhaps the Publisher Help (https://affinity.help/publisher/en-US.lproj/pages/Text/spelling.html) should not point to the OpenOffice site, without providing additional details on what the user would need to do to the .oxt files they will find there? Ideally, it might give the same instructions as the FAQ provides, or point to the FAQ for both the details and the pointer to the download location? From the Help page: Quote Installing alternative spelling dictionaries Spelling dictionaries are installed for the languages supported by Affinity apps, except for Chinese, Japanese and Russian. To install for these languages do the following: Visit the OpenOffice™ website and download the appropriate language dictionary or try an internet search for "spelling dictionaries". That's not anywhere near comprehensive enough, especially given that you end up with .oxt files that way. AffinityAtWork 1 Quote -- 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.1, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.0.1 Link to comment Share on other sites More sharing options...
Dan C Posted August 2, 2023 Share Posted August 2, 2023 29 minutes ago, walt.farrell said: That's not anywhere near comprehensive enough, especially given that you end up with .oxt files that way. I agree, and I have raised this internally previously. Personally I much prefer the V1 FAQ (I'll also note to update that to be V2 compatible ASAP) so I'll raise this once again with the docs team - thanks Walt walt.farrell and AffinityAtWork 2 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.