If you can read your steno, even when it’s not perfect, why shouldn’t your CAT system? With Eclipse, you can count on dictionary conflicts resolving with a high degree of accuracy. You can create conflicts that you wouldn’t dare use on other CAT systems. With Eclipse, not only can conflicts resolve well, they can reduce your editing time and even cope with machine problems like steno stacking.
For this example, assume the following dictionary entries.
Standard entries (displayed in black)
EU = I
AOEFP = each
FPLT = .
RBGS = ,
PH-L = million
HUPB = hundred
T = the
SEBGD = second
Conflict entries (displayed in blue)
A comma conflict
SEUR = sir\sir,\, sir,\, sir
A “stacking” conflict
TPH-D = understand\-ed in
A “shadowing” conflict
P-PL = p.m.\approximately
A basic conflict
SAOE = see\sea
A few hyphenation and capitalization conflicts
KPEUBT = exhibit\Exhibit
SEBGD TO HRAFT = second to last\second-to-last
PHAEU = may\May
Misstroked steno (displayed in purple)
SKAOERT should be SKAORT = security
SKPAOD should be SKPAOED = exceed
*DZ should be DZ = dollars\-ed
AOPBLD should be APBD = and
SEPBLTS should be SEPBTS = cents
Undefined steno is indicated in red and must be handled by intelligent or basic phonetics.