Combine two word match lists. This simply adds each entry from the second list that doesn't already have a corresponding entry in the first list, returning the combined list.

Combine the given word match entries. We'll merge the flags of the two entries to produce a single merged entry in 'a'.

Check a dictionary match's string comparator flags to see if the match is "exact." The exact meaning of "exact" is dependent on the language's lexical rules; this generic base version considers a match to be exact if it doesn't have any string comparator flags other than the base "matched" flag and the case-fold flag. This should be suitable for most languages, as (1) case folding usually doesn't improve match strength, and (2) any additional comparator flags usually indicate some kind of inexact match status.

A language that depends on upper/lower case as a marker of match strength will need to override this to consider the case-fold flag as significant in determining match exactness. In addition, a language that uses additional string comparator flags to indicate better (rather than worse) matches will have to override this to require the presence of those flags.

Compare two dictionary matches for the same object and determine if the first one is stronger than the second. Both are for the same object; the only difference is the string comparator flags.

Language modules might need to override this to supplement the filtering with their own rules. This generic base version considers truncation: an untruncated match is stronger than a truncated match. Non-English languages might want to consider other lexical factors in the match strength, such as whether we matched the exact accented characters or approximated with unaccented equivalents - this information will, of course, need to be coordinated with the dictionary's string comparator, and reflected in the comparator match flags. It's the comparator match flags that we're looking at here.

Filter a dictionary match list. This is called to clean up the raw match list returned from looking up a vocabulary word in the dictionary.

The main purpose of this routine is to eliminate unwanted redundancy from the dictionary matches; in particular, the dictionary might have multiple matches for a given word at a given object, due to truncation, upper/lower folding, accent removal, and so on. In general, we want to keep only the single strongest match from the dictionary for a given word matching a given object.

The meaning of "stronger" and "exact" matches is language-dependent, so we abstract these with the separate methods dictMatchIsExact() and dictMatchIsStronger().

Keep in mind that the raw dictionary match list has alternating entries: object, comparator flags, object, comparator flags, etc. The return list should be in the same format.

Each subclass must override getAdjustedTokens() to provide the appropriate set of tokens used to match the object. This is usually simply the original set of tokens, but in some cases it may differ; for example, spelled-out numbers normally adjust to the numeral form of the number.

For each adjusted token, the list must have two entries: the first is a string giving the token text, and the second is the property giving the part of speech for the token.

Get the vocabulary match list. This is simply the set of objects that match all of the words in the noun phrase. Each rule subclass must override this to return an appropriate list. Note that subclasses should use getWordMatches() and intersectWordMatches() to build the list.

Get a list of the matches in the main dictionary for the given token as the given part of speech (&noun, &adjective, &plural, or others as appropriate for the local language) that are in scope according to the resolver.

Given a list of dictionary matches to a given word, construct a list of ResolveInfo objects for the matches that are in scope. For regular resolution, "in scope" means the resolver thinks the object is in scope.

Get a list of the matches in the main dictionary for the given token, intersecting the resulting list with the given list.

Resolve the objects.

Run a set of resolved objects through matchName() or a similar routine. Returns the filtered results.