Custom Dictionary Office For Mac



  1. Mac Dictionary Download
  2. Medical Dictionary For Mac
  3. Custom Dictionary Office For Mac Computer
  4. Custom Dictionary In Outlook
-->

Hi All, I created a custom dictionary and placed it in the same folder as 'standard.dic' is located. I checked this custom dictionary in the list of 'user-defined dictionaries' in Tools-Spelling-Options. But my spreadsheet still shows any words from that dictionary as misspelled. However, Mac OS does not have the Scripting Runtime library, so none of those things will be available to you - Dictionary, FileSystemObject, etc. You'll need to use a Collection or other data type in lieu of Dictionary type, or you can borrow from this other answer and implement a custom dictionary-like Class. I have a project to programmatically install custom dictionary into Microsoft Word 2011 for mac. I have made the version for MS Word 2008, but now microsoft has changed the format. Can anybody help me to find out the format of the custom dictionary entry in the com.microsoft.office.plist for MS WORD 2011 for mac. The problem for me was that since installing office 2016 on my mac, word has been pointing at a non-existant 'custom dictionary' file in location set by office 2011. By adding a new 'custom dictionary' (to which word added a '.dic' extension) put in the right place, and deleting the old one, everything works now. The App installs this extra wordlist as a custom dictionary for Word. More red squiggly lines under something that is spelt correctly. This is a modern spell check dictionary for Mac Word.

Data loss prevention (DLP) can identify, monitor, and protect your sensitive items. Identifying sensitive items sometimes requires looking for keywords, particularly when identifying generic content (such as healthcare-related communication), or inappropriate or explicit language. Although you can create keyword lists in sensitive information types, keyword lists are limited in size and require modifying XML to create or edit them. Keyword dictionaries provide simpler management of keywords and at a much larger scale, supporting up to 1MB of terms (post compression) in the dictionary and support any language. The tenant limit is also 1MB after compression. 1MB of post compression limit means that all dictionaries combined across a tenant can have close to 1 million character.

Note

Microsoft 365 Information Protection now supports in preview double byte character set languages for:

  • Chinese (simplified)
  • Chinese (traditional)
  • Korean
  • Japanese

This support is available for sensitive information types. See, Information protection support for double byte character sets release notes (preview) for more information.

Basic steps to creating a keyword dictionary

The keywords for your dictionary could come from a variety of sources, most commonly from a file (such as a .csv or .txt list) imported in the service or by PowerShell cmdlet, from a list you enter directly in the PowerShell cmdlet, or from an existing dictionary. When you create a keyword dictionary, you follow the same core steps:

  1. Use the Security & Compliance Center (https://protection.office.com) or connect to Security & Compliance Center PowerShell.

  2. Define or load your keywords from your intended source. The wizard and the cmdlet both accept a comma-separated list of keywords to create a custom keyword dictionary, so this step will vary slightly depending on where your keywords come from. Once loaded, they're encoded and converted to a byte array before they're imported.

  3. Create your dictionary. Choose a name and description and create your dictionary.

Create a keyword dictionary using the Security & Compliance Center

Use the following steps to create and import keywords for a custom dictionary:

  1. Connect to the Security & Compliance Center (https://protection.office.com).

  2. Navigate to Classifications > Sensitive info types.

  3. Select Create and enter a Name and Description for your sensitive info type, then select Next

  4. Select Add an element, then select Dictionary (Large keywords) in the Detect content containing drop-down list.

  5. Select Add a dictionary

  6. Under the Search control, select You can create new keyword dictionaries here.

  7. Enter a Name for your custom dictionary.

  8. Select Import, and select either From text or From csv depending on your keyword file type.

  9. In the file dialog, select the keyword file from your local PC or network file share, then select Open.

  10. Select Save, then select your custom dictionary from the Keyword dictionaries list.

  11. Select Add, then select Next.

  12. Review and finalize your sensitive info type selections, then select Finish.

Office custom dictionary location

Create a keyword dictionary from a file using PowerShell

Often when you need to create a large dictionary, it's to use keywords from a file or a list exported from some other source. In this case, you'll create a keyword dictionary containing a list of inappropriate language to screen in external email. You must first connect to Security & Compliance Center PowerShell.

  1. Copy the keywords into a text file and make sure that each keyword is on a separate line.

  2. Save the text file with Unicode encoding. In Notepad > Save As > Encoding > Unicode.

  3. Read the file into a variable by running this cmdlet:

  4. Create the dictionary by running this cmdlet:

Modifying an existing keyword dictionary

You might need to modify keywords in one of your keyword dictionaries, or modify one of the built-in dictionaries. Currently, your can only update a custom keyword dictionary using PowerShell.

For example, we'll modify some terms in PowerShell, save the terms locally where you can modify them in an editor, and then update the previous terms in place.

First, retrieve the dictionary object:

Printing $dict will show the various variables. The keywords themselves are stored in an object on the backend, but $dict.KeywordDictionary contains a string representation of them, which you'll use to modify the dictionary.

Before you modify the dictionary, you need to turn the string of terms back into an array using the .split(',') method. Then you'll clean up the unwanted spaces between the keywords with the .trim() method, leaving just the keywords to work with.

Mac dictionary download

Now you'll remove some terms from the dictionary. Because the example dictionary has only a few keywords, you could just as easily skip to exporting the dictionary and editing it in Notepad, but dictionaries generally contain a large amount of text, so you'll first learn this way to edit them easily in PowerShell.

In the last step, you saved the keywords to an array. There are several ways to remove items from an array, but as a straightforward approach, you'll create an array of the terms you want to remove from the dictionary, and then copy only the dictionary terms to it that aren't in the list of terms to remove.

Run the command $terms to show the current list of terms. The output of the command looks like this:

aarskog's syndromeabandonmentabasiaabderhalden-kaufmann-lignacabdominalgiaabduction contractureabetalipoproteinemiaabiotrophyablatioablationablephariaabocclusionabolitionaborterabortionabortusaboulomaniaabrami's disease

Run this command to specify the terms that you want to remove:

Run this command to actually remove the terms from the list:

Run the command $updatedTerms to show the updated list of terms. The output of the command looks like this (the specified terms have been removed):

aarskog's syndromeabasiaabderhalden-kaufmann-lignacabdominalgiaabduction contractureabetalipo proteinemiaabiotrophyablationablephariaabocclusionabolitionaborterabortionabortusaboulomaniaabrami's disease

Now simply open the file, add your additional terms, and save with Unicode encoding (UTF-16). Now you'll upload the updated terms and update the dictionary in place.

Now the dictionary has been updated in place. Note that the Identity field takes the name of the dictionary. If you wanted to also change the name of your dictionary using the set- cmdlet, you would just need to add the -Name parameter to what's above with your new dictionary name.

Using keyword dictionaries in custom sensitive information types and DLP policies

Keyword dictionaries can be used as part of the match requirements for a custom sensitive information type, or as a sensitive information type themselves. Both require you to create a custom sensitive information type. Follow the instructions in the linked article to create a sensitive information type. Once you have the XML, you'll need the GUID identifier for the dictionary to use it.

To get the identity of your dictionary, run this command and copy the Identity property value:

The output of the command looks like this:

RunspaceId : 138e55e7-ea1e-4f7a-b824-79f2c4252255Identity : 8d2d44b0-91f4-41f2-94e0-21c1c5b5fc9fName : DiseasesDescription : Names of diseases and injuries from ICD-10-CM lexiconKeywordDictionary : aarskog's syndrome, abandonment, abasia, abderhalden-kaufmann-lignac, abdominalgia, abduction contracture, abetalipoproteinemia, abiotrophy, ablatio, ablation, ablepharia, abocclusion, abolition, aborter, abortion, abortus, aboulomania,abrami's disease, abramoIsValid : TrueObjectState : Unchanged

Paste the identity into your custom sensitive information type's XML and upload it. Now your dictionary will appear in your list of sensitive information types and you can use it right in your policy, specifying how many keywords are required to match.

I’ve added a couple of wrongly spelled words to the custom dictionary by mistake.

How can I remove them again?

The default dictionary where you store your own words in is in a file called CUSTOM.DIC. You can edit it from within Outlook or by directly opening it in Notepad.

When you are using Outlook 2013 or Outlook 2016 and are logged in with a Microsoft Account via File-> Office Account, then this file is called RoamingCustom.dic and is part of your cloud based Office profile. In this case, you can only edit it from within Outlook itself as it is not saved as an editable file on your computer.

Language specific dictionary files are called default.dic by default and can only be edited by opening the file in Notepad and not from within Outlook.

Mac Dictionary Download

Outlook 2010 and Outlook 2013

File-> Options-> section Mail-> button Editor Options…-> section: Proofing-> button Custom Dictionaries…-> button Edit Word List…

Outlook 2007

Dictionary

Tools-> Options…-> tab Mail Format-> button Editor Options…-> section: Proofing-> button Custom Dictionaries…-> button Edit Word List…

Outlook 2003 and previous

Tools-> Options-> tab Spelling-> section: Edit custom dictionary-> button Edit…

Medical Dictionary For Mac


Editing the RoamingCustom.dic word list within Outlook.

Custom Dictionary Office For Mac Computer

Note: You can’t actually edit a word via the above dialog. You’ll need to remove it and add the corrected word again. Editing is possible via the Notepad method (except for the RoamingCustom.dic file) when you open the file from the location below.

Folder location of CUSTOM.DIC and DEFAULT.DIC

Custom Dictionary In Outlook

By default the CUSTOM.DIC file is kept in a folder called UProof (for Outlook 2007 and later) or Proof (for Outlook 2003 and previous) and can be found in the following location;

  • Windows 8, Windows 7 and Windows Vista
    C:Users%username%AppDataRoamingMicrosoft
  • Windows XP
    C:Documents and Settings%username%Application DataMicrosoft

Language specific default.dic files are stored in the same basis location as above but the folder is called Spelling instead of UProof or Proof. Within this folder, you’ll find a subfolder representing each language that you have installed for Office.

For example, the default.dic file for United States English is stored in:
C:Users%username%AppDataRoamingMicrosoftSpellingen-US


The Custom Dictionaries dialog reveals the location of your dictionary files except for RoamingCustom.dic. (Click on image to enlarge)

Note 1: The name of the folder for CUSTOM.DIC is different because since Outlook/Office 2007 the CUSTOM.DIC file is saved in Unicode where the previous versions of Outlook/Office used the ANSI format. The U in UProof stands for Unicode.

Note 2: If you are in an organization, your network administrator can choose to deploy a CUSTOM.DIC file which for instance already includes some words which are not in any default dictionary such as the company name and internal abbreviations.