![]() LiquidText homepage, and I would suggest hitting the links for Deeper Dive and for Videos if you're still intrigued after looking over the homepage. If you have an iPad I can see how it might be helpful if you're doing a lot of annotating and summarizing. And while I understand your feelings about iOS, you may want to look at LiquidText. For annotations, I've just defaulted to Preview just because I have it and I've never taken the time to determine if there's a better approach for me on the Mac. #Typinator vs textexpander pdfAcross all applications, I have F2 set for app-specific KM actions, so it's nearly instinctive for me to hit that key.Īs for PDF annotations and summaries, that's not something I do often. So I'm selecting a variable amount of text that needs to change, then using the palette options to replace the selection. There are text insertions I regularly have to do, but they're done to replace text that isn't consistent in presentation. I know that second one might seem absurd, but it's because of the OCR-related work. I invoke a palette and select the insertion I want (which is pasted).Typed String (then delete key simulations to remove the typed string) followed by text being pasted, or.For now, my TextEdit expansions are either That's an approach I'll look into someday. I never thought of storing text expansions in variables until it was mentioned upthread. If you have extensive needs, or thousands of snippets to import from somewhere, then use Typinator. So, my recommendation is that if you have light-to-moderate text expansion needs, use KM, or at least start with KM. Some others I can't remember right now.However, there are some use cases where KM might be preferred:.It is not designed to handle thousands of snippets (which means Macros in KM). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |