The Multi-Stroke DilemmaIf Plover only supported single-stroke words, then it would be obvious where each word ended and the next began. But with multi-stroke words, Plover has to decide whether a given stroke is a whole word or just a part of a larger word. It needs to make this decision partly because it wants to output the correct word, and partly because Plover inserts spaces automatically between words, and needs to get that right as well. Plover (and all steno systems) must make this choice for each stroke you type. This introduces a whole new class of homophones into the mix. If Plover only supported single stroke words, it would only need to disambiguate between individual words like 'beat' and 'beet'. By supporting multi-stroke words, Plover also has to deal with homophonic word sequences like 'light engage' and 'lighten gauge'. The Natural ResolutionPlover can't intuitively know which homophonic word sequence you intend with a series of strokes. But it does have a consistent and predictable set of internal rules that results in a clean selection for every sequence of strokes:
Taking ControlPlover supports various techniques for controlling which multi-stroke homophone it should output. The most preferred option by far is described in Lesson 5: Prefix And Suffix Strokes. But there are other techniques that, while perhaps more convenient for the beginner, are slow and should not be considered a real solution to the problem. |