![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
Imperfect perfection...
Aug. 10th, 2012 08:16 pmAfter this morning's ham-as-in-radio breakfast, the morning quickly shaped into a kind of "perfect storm" of errands that needed to be run, so I ran them and came home.
While Galina went to Durango to pick up some stuff for the house, I went through a few boxes of books, moved some stuff around the garage, and then took a nap. When I got up, I received a phone call asking that a package of translated and edited files I had sent to my editor be resent to a new editor, as it turns out my editor flew all the way to Hawaii and then collapsed. He's an awfully nice guy and we get along well together in our professional relationship. I hope he recovers from whatever it was quickly.
The news cast a pall on the rest of the day for me, and I've been trying to snap out of a rather depressed mood.
* * * Changing the subject, over a year ago, I caught sight of an article at the ThinkBuzan blog on using the company's flagship software product—iMindMap—for document management. A copy I had printed surfaced a few days ago and I've read it several times since.
Document management is an important part of the translator's "toolkit." And here, I'm not necessarily referring to being able to put one's hands on a previous version of a document, but—as documents become increasingly converted to electronic format—to various references.
The only problem is, I'm doing quite well with Emacs and org mode, so I really don't need to use iMindMap like this. What I could use is a non-memory-hogging demon that monitors file movement, the most common example of which takes place when a job is invoiced (when the associated job folder is moved from my "current-and-awaiting-invoicing" folder—deliberately so structured to encourage me to keep up with invoicing—to my invoiced folder).
When that happens, all of the respective folder links in my org-mode assignment list end up pointing to a folder that's no longer there, and while it's generally not that big a deal to go in and change the path, it's still an extra step.
I'm sure there's a solution somewhere. I just need to find it, or let it find me.
Cheers...
While Galina went to Durango to pick up some stuff for the house, I went through a few boxes of books, moved some stuff around the garage, and then took a nap. When I got up, I received a phone call asking that a package of translated and edited files I had sent to my editor be resent to a new editor, as it turns out my editor flew all the way to Hawaii and then collapsed. He's an awfully nice guy and we get along well together in our professional relationship. I hope he recovers from whatever it was quickly.
The news cast a pall on the rest of the day for me, and I've been trying to snap out of a rather depressed mood.
Document management is an important part of the translator's "toolkit." And here, I'm not necessarily referring to being able to put one's hands on a previous version of a document, but—as documents become increasingly converted to electronic format—to various references.
The only problem is, I'm doing quite well with Emacs and org mode, so I really don't need to use iMindMap like this. What I could use is a non-memory-hogging demon that monitors file movement, the most common example of which takes place when a job is invoiced (when the associated job folder is moved from my "current-and-awaiting-invoicing" folder—deliberately so structured to encourage me to keep up with invoicing—to my invoiced folder).
When that happens, all of the respective folder links in my org-mode assignment list end up pointing to a folder that's no longer there, and while it's generally not that big a deal to go in and change the path, it's still an extra step.
I'm sure there's a solution somewhere. I just need to find it, or let it find me.
Cheers...
