1. 1, the way I do it. I don’t use anyone else’s translations, so all it involves is to start typing.
2. 1, because again, the way I do it, you may not even realize you’re using one at first. You just sort of... start translating things and suddenly you notice the fuzzy matcher is showing lines you have previously entered.
3. $0.00, in U.S. moneys.
4. 3. I’m never all that satisfied with Java applications, but I mean, I don’t exactly pay out the nose to use it. Also, I’m not that picky, either, because I don’t translate professionally (and probably never will) and I am perennially broke-ass anyway.
5. I couldn’t say; it only applies to large, cohesive projects rather than any spot translations I do.
6. Fuzzy matching. In several projects, I have had story branches where wordings change ever so slightly; having these at a glance no matter what line I go to is awesome.
7. The speed at which things run. Between Java, and going through so much text after a while, things can slow down to an annoying pace.
8. This question doesn’t really mean anything to me.
13. I haven’t made a single dollar from translat—*checks unnamed ad service* I have made less than a dollar from translating and I haven’t seen it yet.
14. 3~4-ish, though it really depends on the arena.
15. Stay out of the way when I don’t need it, be right there when I do. Until computers can read minds like they do on Star Trek, that means the TM bits should be easy-access yet not hogging all the screen space.
16. I don’t see why not, though I imagine a fair number of my contributions would be painful to read or highly unconventional.