However, we recommend that the total file size of a custom dictionary file does not exceed 2 gigabytes (GB).
There are no settings available to change this limit. The maximum limit to the number of entries in a custom dictionary is 10,000.
Table 1 – Examples of supported and unsupported entries for custom dictionary files Supported The following table shows examples of supported and unsupported entries. The maximum length of an entry is 128 (Unicode) characters. The number sign character (#) cannot be used at the beginning of an entry but it can be used within or at the end of an entry.Įxcept for the pipe, number sign, and white-space characters previously mentioned, any alphanumeric characters, punctuation, symbols, and breaking characters are valid. When you add entries to a custom dictionary, consider the following rules to avoid unexpected results: Each entry must be on a separate line, separated by a carriage return (CR) and line feed (LF). Rules for creating a custom dictionaryĪ custom dictionary is a Unicode-formatted file.
#HOW TO MAKE CUSTOM DICTIONARY IN WORD HOW TO#
For information about how to use thesaurus files, see Create and deploy a thesaurus in SharePoint Server. In this case, adding the CAS registry number to the custom dictionary of the appropriate language resolves the problem. For example, if the CAS registry number is part of an expansion set in the thesaurus and the word breaker breaks that number at the hyphens into three separate numbers, the expansion set of which that number is a part might not work as expected. This is especially important if you have words or numbers in a thesaurus file. Instead, all terms that are in custom dictionaries are treated as a match. Named-entity normalizations, such as date normalizations, that are ordinarily applied by word breakers are not applied to terms that are in custom dictionaries. Adding the CAS registry numbers that appear in a corpus to a custom dictionary directs the search system to index each number without breaking it into parts. After word-breaker processing, this CAS registry number is broken into three parts: the numbers 7782, 44, and 7. For example, the CAS registry number for oxygen is. For example, word breakers typically split numbers that appear before or after a hyphen or other special character from the rest of the number. Terms like Chemical Abstracts Service (CAS) registry numbers can be affected by word breakers. If “IT&T” is in the custom dictionary, and if a document does not contain "IT" or "T" but does contain "IT&T", a query that contains "IT" or "T" but not "IT&T" does not return that document in the results set. However, if the token “IT&T” is in the custom dictionary of the same language as the word breaker that is being used, the word breaker does not break that token (at crawl time or query time).
The following two examples describe typical word breaker behavior and how an entry in the custom dictionary can affect that behavior.Ī word breaker might break the token “IT&T” immediately before and after the ampersand (&), resulting in the three tokens “IT”, “&”, and “T”. If the token exists in the custom dictionary, the word breaker does not perform any actions on that token. If the word does not exist in the custom dictionary, the word breaker performs its usual actions, which might result in breaking a token into multiple tokens. In each case, if a custom dictionary exists that supports the language and dialect of the word breaker that is being used, the search system checks for the word in the custom dictionary before it determines whether to use a word breaker for that word. The indexing system uses word breakers to break tokens when it indexes crawled content, and the query processor uses word breakers in queries. To know whether you must have a custom dictionary and what entries it should contain, you must understand the behavior of word breakers. Stop and restart the SharePoint Server Search 14 service A custom dictionary for a given language applies to all Search service applications in the server farm.Ĭopy the custom dictionary to each application server
0 kommentar(er)
