This article sums up the most relevant technicalities of Corporate Terminology.
Prerequisites
|
Important
|
Where will Corporate Terminology take effect?
Corporate Terminology uses the Microsoft Office dictionary and Auto-correct. This means that it will take effect in all the Office applications that use the Microsoft Office dictionary, and Auto-correct today, being:
- Word, PowerPoint, Excel, Outlook and OneNote.
How are the dictionary and Auto-correct updated?
Clicking Publish in the Admin Center will trigger Templafy Desktop to add/edit/delete these words with the next Templafy Desktop update performed on the end-user’s PC through Corporate Terminology plugin.
NoteThe automatic update in Templafy Desktop only happens once every 24 hours, so it might take this long before end-users experience the changes. |
What will be added to user’s computer with Corporate Terminology?
Templafy folders
- Check requirements: A corporate-terminology.json file will be added under the \AppData\Local\Templafy\SlideProof folder.
- Microsoft Office Dictionary and Microsoft Auto-correct requirements: A corporate-terminology.json and a corporate-terminology-languages.json file will be added under the \AppData\Local\Templafy\AddIns\CorporateTerminology folder.
- Plugin requirements: under the \AppData\Local\Templafy\AddIns\CorporateTerminology folder a TemplafyDesktopPlugins folder will be created gathering all the necessary dll files.
Office Folders
- Office Dictionary: CUSTOM.DIC will be created (or modified if already existing) in \AppData\Roaming\Microsoft\UProof to inject the Prefer terms.
- Autocorrect: .alc files will be created (or modified if already existing) in \AppData\Roaming\Microsoft\Office to inject the required terms to autocorrect.
Note
|
Troubleshooting tips
TipIf terms are still underlined in Office or aren’t being autocorrected:
|
Validation warnings and Errors
In the Admin Center, some warnings will be displayed if the words being added might conflict with one another. Please find below the difference validation performed upon adding words in Corporate Terminology in the Admin Center.
Validation for main terms
| Type | Prefer | Avoid |
|---|---|---|
| Main term already exists as related term in prefer |
Error, since the rule you are creating, will conflict with the other rule (be each others opposite). Message in UI: This term already exists as a related term in 'main term'. |
Warning, since Check will show two. |
| Main term already exists as related term in avoid | No error |
Error, since the rule you are creating, will conflict with the other rule (be each others opposite). Message in UI: This term already exists as a related term in 'main term'. |
| Duplicated main term | Error, since we need only one source of truth. | Error, since we need only one source of truth. |
| No main terms | Error, since we need something to correct. | Error, since we need something to correct. |
Validation for related terms
| Type | Prefer | Avoid |
|---|---|---|
| Related term already exists as related term of an Avoid term |
Error, since one rule will trigger the other rule. The admin needs to be consistent in what he/she wants to be the correct term. Message in UI: The related term 'related term' already exists as a related term to the avoid term, 'main term'. |
No error, since the related terms are just suggestions, and the same suggestion can apply to several main terms. |
| Related term already exists as related term of a Preferred term |
Error, since the related terms are the ones being corrected, and we cannot have two correct answers. Message in UI: The related term 'related term' already exists as a related term to the preferred term, 'main term'. |
Error, since one rule will trigger the other rule. The admin needs to be consistent in what he/she wants to be the correct term. Message in UI: The related term 'related term' already exists as a related term to the preferred term, 'main term'. |
| Related term already exists as main term in prefer |
Error, since the rule you are creating, will conflict with the other rule (be each others opposite). Message in UI: The related term 'related term' already exists as a preferred term. |
No error, since the related terms are just suggestions for alternatives and can easily be a term you also prefer. |
| Related term already exists as main term in avoid |
Warning, since it will cause Check for PowerPoint to have two warnings. Message in UI: One or more related terms already exist as an avoid term, Check for PowerPoint will produce two warnings. |
Error, since the rule you are creating, will conflict with the other rule (be each others opposite). Message in UI: The related term 'related term' already exists an avoid term. |
| More related terms of the same spelling (only capitalization difference) | Warning, but only when Autocorrect is enabled, since there is no need to add more versions of the same term - Auto-Correct will fix it out of the box. | No error, since Avoid only works in Check for PowerPoint, and here we don't have a technical constraint and therefore can have as many suggested alternatives as the admin finds relevant. |
| No related term | No error, since it should be able to appear in the dictionary, without necessarily having a related term to correct. | No error, since Check for PowerPoint can still provide value by pointing out that the term should be avoided, without giving an alternative. |
Comments
Article is closed for comments.