When Two Rules Want the Same Cell

The problem of overlapping scope

Braille contractions do not operate on isolated words in a vacuum. They apply to strings of letters in sequence, and a given string can sometimes satisfy more than one rule at once. The word mother, for instance, contains both the whole-word contraction for mother (dot 5 followed by m) and the part-word contraction the buried inside it. Which wins? The answer is: the longer match, which here means the dedicated whole-word sign. But the reasoning behind that answer is what matters, because the same logic applies across dozens of similar collisions.

Unified English Braille (UEB) inherits its precedence hierarchy from decades of prior codification. The hierarchy runs, roughly, from most specific to least: whole-word contractions claim priority over part-word contractions, longer part-word contractions claim priority over shorter ones, and no contraction may be applied if doing so would misrepresent word boundaries or produce an ambiguous reading. These are not arbitrary tie-breaking rules; they reflect a consistent underlying principle — the contraction that encodes the most information in the fewest cells wins, provided it does not break another constraint.

Three cases in detail

Case one: altogether. The word contains the letters all followed by together, and together has its own shortform, so it looks as if the word could be assembled from parts. UEB resolves this with a single shortform, alt, which stands for the whole word altogether, so the word is not built from smaller contractions at all. Because the shortform covers the whole word, it takes precedence over any smaller pieces; there is nothing left to assemble.

Case two: should. This word contains the part-word contraction sh at its opening and also qualifies for the shortform for should (shd). The whole-word sign is preferred. Applying sh followed by the letters ould would be technically legal but wasteful; UEB instructs that where a whole-word contraction exists and the word is used as a standalone word, that sign takes precedence. The same pattern governs would, could, every, their, and others: the dedicated sign is not optional when the word appears in its base form.

Case three: receive. Here the tension is subtler. Under UEB, receive is written with its own shortform, rcv, so the word is not built from smaller letter-group signs at all. Once a sign has been selected for a span of letters, the letters it covers are consumed; no smaller rule can reach inside it, because contractions are not applied inside a contraction already in use.

This last point is the most practically important one. Contracted braille is not a system of simultaneous substitutions — it is sequential and greedy in the specific sense that a matched span is taken out of play. Once a span has claimed its letters, only the letters outside it remain, and those are written by whatever rules can still reach them, or spelled out in full if none can.

How to think about it

The precedence system resolves to three working rules. Whole-word signs beat part-word signs for complete words. Longer spans beat shorter spans when both start at the same position. And no rule operates on letters already consumed by an earlier rule. Apply those three in order and most conflicts resolve without ambiguity.

Where genuine ambiguity persists — and it does, in a small number of edge cases involving proper-noun fragments, foreign loanwords, and certain compound constructions — UEB's guidance is to default to the less contracted form. The words contractions cannot shorten are partly defined by exactly this conservatism: when the precedence logic produces a form that could mislead, the code retreats to the literal.

The system is consistent. Learning the precedence hierarchy is, in a real sense, learning the grammar beneath the grammar.