I've learned some pretty cool stuff from the Eclipse FB group. I strongly recommend checking it out if you're on Eclipse. I also watched the full 8 hours of Eclipse basic training tutorials (bo-ring!). It was mostly about title pages and auto indexing and stuff I don't use, or stuff I already know how to do, but I did pick up a couple ideas.
I have a stroke that takes me to the bottom of my realtime feed/has me follow it, and it was always bad when I forgot to hit that after I scrolled up to look at something. But I found out about the "follow always" checkbox in the realtime tab, and now that's not a problem anymore.
I learned that you can make conflicts if you want a certain thing to happen after a number. I use P-KT for % and PER/KRENT for percent, but sometimes it's so much easier to hit P-KT, that I just don't get PER/KRENT in there. I think I've got it set up now that I can write "a large P-KT" or something and it will come up "a large percent," so that's cool. I've been trying to see new opportunities for conflicts overall. Sometimes I miss the F in I've (AO*IV) and get "aye," but why not make it a conflict with the first choice being "aye"? Just today I changed YO*U from ewe to \ewe\you're, because I miss that R so often.
The best idea I got from the FB group was about suffixes. I think someone just said something about their suffix rules table, and it reminded me about how I keep getting things like "organizationtion" when I accidentally drag an extra G into ORGS/S, making it ORGS/GS. So I made a rule that when the word ends in -tion, the suffix should delete the -tion and add an -s, and voila! ORGS/GS is organizations now, and I won't get orientationtion or objectiontion or anything like that, either.
I've come up with tons of applications for that now that I've realized I can do it. No more defectiveive if I already tucked the V and forgot about it (DE/F*EFKT/IV), no more passageage if I got confused and did PAJ/AJ, no more strategicically, or longerer if I didn't realize I tucked the R (LORNG/ER). I don't think -tor was in there as a real suffix; it was in my dictionary, but it wasn't in the suffix table, so it didn't have any suffix rules. I kept getting things like compacttor and reacttor because instead of RE/AK/TOR, I'd write RAEKT/TOR.
But I fixed that rule, so it works for -tor and -tors. And I was getting things like "humorral," so I told it if you're going to add -ral and the word already ends in "r," delete the first "r." I feel like someone who does realtime already has all these suffixes in their suffix table and suffix spelling rules, and I must've missed out on them in an update or something. I should ask on depoman or the FB group for someone's tables, but I'm afraid it might mess things up. I don't see how it could, though, really; it would only change the suffixes in English. It wouldn't have anything to do with my steno outlines. I guess I'd just have to make sure all the things I've changed were still in there.
I also changed my background color from white to gray. Someone on the FB group said it's easier on the eyes. I've heard stuff like that before, but I never really thought about actually changing it until I saw it there. I really do like it better.
I have a ton of different settings files I use for different companies, so it's a pain to change suffix tables or whatever in all of them. I asked about it on FB, and Dave Stanley said that I could just have a global.set that all settings would use for certain things. It seemed like a great idea, except that it overwrites your realtime settings if you let it change your translation settings. It also overwrites your job dictionaries no matter what you do, which is a drag.
I learned how to finally get TM to stop messing with my stroke for "a," which is awesome. I told it to stop pulling "an" and "everyone" into other words, too. I actually turned TM up a bit. The new sliders are kind of confusing, but I understand them now. My main problem was that TM wasn't being aggressive enough; there were tons of words it just left alone. So I unchecked "require an untran," and I bumped it up from whatever it was at (it might've been as low as 1%) to 30%, and I think it's doing better now.
I found out there's a dictionary entry you can use to reject the last AB suggestion and get a new one all at once, and I also found a macro for requesting a brief for the last word, which I think will come in handy.
No comments:
Post a Comment