You can configure the spelling checker to check words against an organizational vocabulary.
- Using Notepad, create a text file containing one word per line, without extraneous spaces. The order of the words in the file is not important. Only single-byte ANSI (Latin1) characters should be used, and the file should be saved with ANSI encoding. The first line of this file must be the following:
#LID 30840The words in the custom dictionary must follow this first line. Here is an example custom dictionary containing three words:
#LID 30840dogcathorseBe careful when entering words: misspelled words will compromise the effectiveness of the spelling checker for all users. Also note that changes made to custom dictionaries that are already in use will have no effect until PPM is restarted. There is no way to dynamically add words to organizational custom dictionaries at run time without stopping and starting Primavera Portfolio Management.
Save the text file in the Dictionaries folder off the PPM install directory. By default, this folder would be located at C:\Program Files\Oracle\Primavera Portfolio Management\Portfolios\Dictionaries.
- Using Registry Editor, locate the registry string value:
HKEY_LOCAL_MACHINE\SOFTWARE\Oracle\Primavera Portfolio Management\Portfolios\Server\SpellingServer\Languages\24941\DictionariesThis string value contains the file names of the dictionaries that the spelling checker checks words against. Add a semicolon and the name of the file you created in step 1 (including extension but without path) to the end of the string value of this registry entry.
As an example, if the name of the file you created in step 1 is "orgcust.txt", the value of the registry entry would need to be:
ssceam.tlx;ssceam2.clx;correct.tlx;tech.tlx;(the required addition has been emphasized here for extra clarity only).
- To apply the change, restart PPM.
By repeating the above steps with files saved under different names, you can use multiple custom dictionaries.