I love the number triggers in Eclipse. They make me look like a million bucks. Saves editing time too.

First there are the after-the-fact triggers. Write any number and then the trigger stroke afterwards to get the desired translation:

R*-M={#R} Makes Roman numerals
T*-M={#T} Makes time, including military
TK*T={#D} Puts hypens in for dates and apostrophes for abbreviated years.


Then there are the triggers that are right in with the steno and they translate automatically. Below are examples. I will attach an Eclipse dictionary file with the conflicts so the AI data can be utilized. #G = Generic, #R = Roman

\rule\Rule{#G} = RAOUL
\region\Region{#R} = RAOEPBLG
\war\{|-}War{#R} = WAR
\Olympic\{#R}Olympic = PHREUFRP
\Pentium\Pentium{#R} = PEPBT KWRUPL
\World War{#R}\world war = TKWAORLD
\section\Section{#G} = S*EBGS
\Super Bowl\Super Bowl{#R} = SPER PWOEL
Wrestlemania{#R} = WRES -L PHAEUPB KWRA
Henry{#R} = HEPB RAOE (don't write the word "the" after)
Elizabeth{#R} = HREUS PW*ET

Then there are the number template entries, which are found in the bottom right corner of the Numbers Tab in User settings. These are a huge time saver. Before you use these, make sure your templates match the following:

1=.### (will add a decimal point before the number written in steno .22, .45, .357, etc.)

{#1}holster = HOEL STER
{#1}pistol = P*EUS -L
{#1}Magnum = PHAG TPHUPL
{#1}rifle=RAOEUFL
{#1}caliber = KAL PWER

2=#'#" (will make the equivalent of 6'4", rather than 6 foot 4 inches - great for CART/captioning)

{#2} = TPAO*T (write SEUBGS/FAO*T/FOUR or 6/FAO*T/4 = 6'4" - you don't have to write "inches"!)

For those that are writing extra strokes for ordinal numbers, those can be done in one stroke for one-digit numbers, two for two digit numbers. The dictionary entry looks like this:
1{#O}, 2{#O}, and so on up through 10{#O}. The steno I use is 1E, 2E, E6, E7 and so on. Note: do not put 1{#O}=1st in your dictionary. That is a redundant entry and will mess up the number conversion. In my example my dictionary looks like so: 1E=1{#O}.

When I want an ordinal for a two-digit number, I stroke the number with the trigger stroke last: 1/1E = 11th, 10/1E = 101st, 5/3E = 53rd, 7/E9=79th.


The are some caveats, though. If you write number bar 2 and then the word pistol, for example, it will translate .2 pistol.

In addition, if you don't use the number bar, make sure that "ignore written numbers" is UNchecked. There may also be some tweaking of the number conversion settings on Number Tab depending on how you write your numbers. Check out the attached documents for further explanation.
1: Dictionary w/conflict AI data
2: Eclipse Numbers Setup
3: Further Number explanation

If you need more assistance, I have other cheat sheets I can provide or I would be happy to answer questions.

Rebecca

Views: 178

Attachments:

Replies to This Discussion

Hi, Laurie,
If you define your slash mark with the the number trigger {#G}, Eclipse will translate any number you write before and after into a digit.

HTH,
Rebecca
Rebecca, thanks for this piece on numbers. I guess a lot of us learned to write numbers with added "steno intelligence' -- getting the translations we wanted with creative stroking methods. Eclipse does plenty with less strokes. I'll be printing and keeping your comment.

Thank you, Rebecca!  What an excellent post!  I will print it also.  I've been wanting to know how to force the written-out numbers into the Arabic numbers. I use the number bar.

 

I'm deriving, from what you have above, that when I write 3 on the number bar and Eclipse writes "three," I could define a stroke, say G*, defined as {#G}, and it will force the previously written-out "three" to 3?

TIP I got from Jeremy last year, which is what led me to using NC:

If you have a number that you don't want NC to go near (and I have plenty), put them in curly brackets.  I have a way of writing "hundred" when I don't want it converted to 00.  Define it {hundred}.  { } is kryptonite to number conversion!

RSS

© 2019   Created by Kelli Combs (admin).   Powered by

Badges  |  Report an Issue  |  Terms of Service