Hi, When someone is working on a text project, the spellchecker comes to play a dominant role, upon which writers rely. There is a problem, however (in terms of reliability). There are tons of words that get underlined, although they are correct. These get saved in custom / private dictionaries... But what if you move over to another machine? Your dictionary is lost... and there fore tons of underlyings appear again, which prevent you from spotting the real errors... It would be cool if we were able to save (export to a location in a human readable text form) and import and load these dictionaries... Almost every project needs a custom dictionary... or is was better off with a dedicated custom dictionary than with the sum of custom dictionaries of several projects.. It would be great... to have a project directory defined per document... other than the default document directory PATH ... If such a project directory could be defined, a folder could be defined within that -- say "project background files"... where styles and dictionaries could be saved, and kept accessible for Libreoffice in a transparent manner... Handling dictionaries wouldn't be difficult anymore... (if we could save and export and import them)
I feel like adding a UI for import export has already been requested somewhere but the closest i found is bug 76295. Are you aware you can find those files in your user profile? https://wiki.documentfoundation.org/UserProfile
hi, Stéphane, I am aware that the machine's administrator can actually go to the secret folder (hidden in Linux, like, ".hidden", or rather: .Libreoffice/... and copy dictionaries, and various settings too.. or rather, data that refers to these... But this is not to be called an export import method :) What I'm talking about is: Someone's working on a text, say, about Andy Warhol. She or he opens the project -- thanks to the cloud system -- on another machine. All of a sudden, lots of words would be underlined, marked for correction. This means: weeks of work is not available at that moment, on that machine. This means: chances that there's a typo somewhere and sh/he can spot it are really vague... Then imagine another text about Kandinsky... That one involves Russian-like words... You wouldn't like to fill your dictionary with those... they are for this project only... Basically every project needs a custom dictionary... and moving to another machine should be continuing work where you've left off... This is what I mean...
Thanks for clarifying, Peter. I found an even better match on Ask.LO: someone asking for a way to attach a dictionary to a file (like we allow embedding fonts): https://ask.libreoffice.org/t/how-do-i-attach-a-custom-dictionary-to-a-libreoffice-document/30535 (on top of the related https://ask.libreoffice.org/t/saving-personal-dictionary-the-words-i-added-to-libreoffice-dictionary-saving-or-copying-them-to-another-computer/30781) I can see the use case, where a file with specialist language that will probably only ever pertain to that specific document, needs sharing around to different contributors, or editing on different computers. The example of writing fiction with heavy world-building. UX/Design team, what do you think about supporting attaching a dictionary to a file? Has it been suggested before? Would involve extending the format and a fair bit of UI changes, I guess...
Adding it to a dictionary means you need being able to pick one in the spell-checking dialog (there is for sure a ticket), if it's the auto-correction we don't have such thing yet. In both cases it requires an enhancement to the document format.
possible relatively simple solution: allow a dictionary to be saved as <filepath>/<filename>.dic Does need work on the code, but not on ODF.
We discussed the topic in the design meeting. Just placing a dictionary (*.dic/aff) in some folder (which can be added via tools > options > path to the dictionary locations) does not make it available as writing aid; the procedure apparently needs some registration. And while export/import could be a nice task for a macro it's a generic use case for the majority of users and adding this to the core makes sense So the recommendation is to add export/import buttons to the dictionary dialog.