Translation Assistant.ahk is a word processing program that I have written specifically for line-by-line to-English translations. Simply load a raw file into the app and write an English equivalency for each line; a translator should not skip or summarize. The image on the left displays the setup I use to translate; with Translation Aggregator and my own Translation Assistant.ahk open.
Languages: Japanese, and Korean.
Add-on Programs: Translation Aggregator.
1. Optionally displays Google, Bing, Babylon, and Honyaku (Japanese) or Naver (Korean) machine translations of any given line.
2. Each raw line is automatically placed on the user’s clipboard to facilitate the use of Translation Aggregator or other unsupported translation methods.
3. Improved machine translations can be generated by adding Phrases, which allows the user to selectively substitute translations into lines before the program feeds them into the translators. Phrases are stored in and can be loaded from .csv (comma delimited) files.
4. Line movement can be controlled by arrow keys. Up/Down navigates between lines as a substitute for the arrow buttons next to the translation field. Ctrl+Left/Right allows the user to parse through and selectively translate parts of a line at a time based on the Parse Characters field in Settings. Use Ctrl+Up/Down to navigate to the top/bottom of the current translation.
5. Ctrl+F can be used to navigate to the next matching phrase in either the raw or translated lines. Ctrl+G can be used to go to a specific line within range.
6. A spell-check is forced for every line, to prevent typos. Any phrases added are placed in a custom.dic file (only associated with this program) to prevent them from activating the spell-check prompt.
7. Profiles can be kept and created for each series. Each profile contains a separate set of phrases, a separate custom.dic, and its own language setting (which in turn stores the Honyaku/Naver settings.)
8. Fields should intelligently and automatically populate from your current clipboard’s text. I.E. If you open Add Phrase (Ctrl+Enter, designed for quick usage) and your clipboard does not match last line the app fed it, the app will automatically assume you recently copied something relevant to this action and display your clipboard as the default new phrase.
9. Translation Aggregator will minimize/restore along with Translation Assistant.
1. Windows 7 or 8. No Macs, Linux, or Tablets. Only Windows systems can run AHK. Windows XP and earlier are untested and unsupported.
2. Internet Explorer must be installed, preferably with default settings.
3. AHK Unicode must be installed, which allows your computer to run the AHK programming language, download it here.
4. The ability to unzip a file.
Read System Requirements and install AHK.
Recommended: Download the prepackaged version of Translation Aggregator and Translation Assistant, unzip, and done. Run Translation Assistant from inside the Translation Aggregator folder, or create a shortcut if you’d like it elsewhere but do not move the file itself. The Translations folder must be in the same directory as Translation Assistant.ahk; if you already have Translation Aggregator installed then simply download and only unzip Translation Assistant.ahk and the Translations folder.
Or download TA.ahk by itself to update your version.
(Optional) Install a questionably legal version of Atlas v14.
Notes: Atlas (which powers Mecab and JParser) are by far the most useful Japanese to English translation tools I have found. If you’re inexperienced, you should consider these tools necessary; or if you’re squeamish, use this set to rollover and paste the lines in. Korean does not currently have equivalent support.
1. Create a new file via File > New or Ctrl+N, name it, and select a folder to save it in. (Optional) Enable One Sentence Per Line to prevent multi-sentence lines from crowding fields.
2. (Optional) Load/create a Profile via Settings, select the Language and machine translations to display, add Parse Characters to break up lines (recommended are Japanese comma and period, note that English versions will not work), and add or import phrases to be used for substitutions.
3. Begin translating by typing into the white edit field. Navigate between lines using your arrow keys. Use Ctrl+Up/Down to go to the top/bottom of the current translation respectively. Use Ctrl+Left/Right to feed parsed lines to the translators. Use Ctrl+? to navigate to the topmost untranslated line. Enclose comments in <ref></ref> tags and use — to create Part X for Wiki and WordPress formats. A </ref> tag is automatically added to the end of a line upon navigation if a <ref> tag exists, to close it.
4. Don’t forget to Save with Ctrl+S. If you do forget or your system crashes/shuts down, then Translation Aggregator/Translations/Settings/Recovery.txt will contain the last updated translation file.
5. Go to Menu > Clipboard to place different versions of the open file on your clipboard for easy pasting. WikiFormat and WordPress automatically and intelligently add code to format your post.
Q: Why did a bunch of Internet Explorer windows pop up when I closed Translation Assistant?
A: Bing, Babylon, and Honyaku/Naver are retrieved using COM which uses hidden IE windows. COM is unreliable. The windows become visible in case the script fails to close them so the user can manually do it, which would otherwise cause the user to be unable to close the app.
Q: Why are Bing/Babylon/Honyaku/Naver taking so long?
A: COM. Either that or you’re attempting to feed them the same line over again, which requires a 30 second time-out for the app to stop waiting until the COM object’s fields change. I’ve actually found that, because of speed issues, these aren’t really worth using for Japanese because Translation Aggregator provides more than enough feedback; so I only have Google activated. I might try to learn how to use a different retrieval method in the future to speed these up.
Q: I found a glitch!
A: Try to repeat it. Post the process on my Contact Me form under About. Screenshots = bonus points. I cannot fix a glitch if I cannot replicate it.
Q: Add support for X, Y, and Z and change Q!
A: Maybe. Give me a justification as to why you think I should and I’ll consider it if it’s within my capabilities. Most of the app, especially its admittedly ugly graphical interface, is extremely time consuming to change; the more time I expect a change to take, the greater a justification required.
Q: Why didn’t you just give us a .exe file?
A: So you can see the code for yourself and understand that nothing malicious has been (knowingly) included.
More information about Translation Aggregator here.
More information about AHK here. There’s AHK.org and AHK.com because a power-hungry idiot was left in charge of the .com domain, or so I’m told. They host the same coding language, just different versions.
Reminder: Report any serious glitches/request any changes on my Contact Me page.