Announcement

Collapse

Please use the Hentai ID thread for all hentai ID requests. Click me for link!

The Identification Thread is Here:

http://www.hongfire.com/forum/showthread.php/447081
See more
See less

Translation Aggregator

Collapse
This is a sticky topic.
X
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Translation Aggregator

    I'm no longer working on Translation Aggregator, but Setx has released an updated version, here. The files attached directly to this post are now outdated

    Translation Aggregator basically works like ATLAS, with support for using a number of website translators and ATLAS simultaneously. It was designed to replace ATLAS's interface as well as add support for getting translations from a few additional sources. Currently, it has support for getting translations from Atlas V13 or V14 (Don't need to have Atlas running), Google, Honyaku, Babel Fish, FreeTranslations.com, Excite, OCN, a word-by-word breakdown from WWWJDIC, MeCab, which converts Kanji to Katakana, and its own built-in Japanese parser (JParser). I picked websites based primarily on what I use and how easy it was to figure out their translation request format. I'm open to adding more, but some of the other sites (Like Word Lingo) seem to go to some effort to make this difficult.

    JParser requires edict2 (Or edict) in the dictionaries directory, and supports multiple dictionaries in there at once. It does not support jmdict. You can also stick enamdict in the directory and it'll detect some names as well, though the name list will be heavily filtered to avoid swamping out other hits. If you have MeCab installed, JParser can use it to significantly improve its results. TA can also look up definitions for MeCab output as well, if a dictionary is installed. In general, MeCab makes fewer mistakes, but JParser handles compound words better, and groups verb conjugations with the verb rather than treating them as separate words.

    TA also includes the ability to launch Japanese apps with Japanese locale settings, automatically inject AGTH into them, and inject its own dll into Japanese apps. Its dll can also translate their menus and dialogs using the ATLAS module (Requires you have ATLAS installed, of course). Versions 0.4.0 and later also include a text hooking engine modeled after AGTH. The menu translation option attempts to translate Windows-managed in-game menus, and is AGTH compatible. The AGTH exe and dlls must be in the Translation Aggregator directory for it to be able to inject AGTH into a process. AGTH is included with the most recent versions of TA.

    The interface is pretty simple, much like ATLAS: Just paste text into the upper left window, and either press the double arrow button to run it through all translators, or press the arrow buttons for individual translation apps. Each algorithm is only run once at a time, so if a window is busy when you tell it to translate something, it'll queue it up if it's a remote request, or stop and rerun it for local algorithms. If you have clipboard monitoring enabled (The untranslated text clipboard button disables it altogether), it'll run any clipboard text with Japanese characters copied from any other app through all translators with clipboard monitoring enabled. I won't automatically submit text with over 500 characters to any of the translation websites, so you can skip forward in agth without flooding servers, in theory. I still don't recommend automatic clipboard translation for the website translators, however.

    To assign a hotkey to the current window layout, press shift-alt-#. Press alt-# to restore the layout. Bound hotkeys will automatically include the current transparency, window frame, and toobar states. If you don't want a bound hotkey to affect one or more of those states, then you can remove the first 1 to 3 entries in the associated line in the ini file. Only modify the ini yourself when the program isn't running. All other values in those lines are mandatory.

    Pre-translation substitutions modify input text before it's sent to any translator. Currently applies to websites, ATLAS, Mecab, and JParser. There's a list of universal replacements ("*") and replacements for every launch profile you've created. I pick which set(s) of substitutions to use based on currently running apps. Note that you do not need to be running AGTH or even have launched a game through TA's launch interface for the game to be detected, but you do need to create a launch profile. May allow you to just drag and drop exes onto the dialog in the future.

    MeCab is a free program that separates words and gives their pronunciation and part of speech. I use it to get the information needed to parse words and display furigana. If you have MeCab installed but I report I'm having trouble initializing it, you can try copying libmecab.dll to the same directory as this program. Do not install MeCab using a UTF16 dictionary, as I have no idea how to talk to it (UTF16 strings don't seem to work). Instead, configure MeCab to use UTF8, Shift-JIS, or EUC-JP. If you have both MeCab and edict/edict2 installed, you can view a word's translation in MeCab by hovering the mouse over it. Also, JParser can use MeCab to help in parsing sentences.

    JParser tends to be a better choice for those who know almost no Japanese - it tells you how verbs are conjugated, handles some expressions, etc. MeCab may well be the better choice for those who know some Japanese, however.

    Source, attached below, is available under the GPL v2.

    Thanks to (In alphabetical order, sorry if I'm leaving anyone out):
    Hongfire Members:
    Freaka for his innumerable feature suggestions and reported issues over the course of development.
    Setsumi for TA Helper and for all his suggested improvements and reported issues, particularly with JParser.
    Setx for AGTH.
    Stomp for fixing the open file dialog not working properly on some systems and adding the tooltip font dialog, and fixing a bug that required admin privileges when certain other software was installed.
    Might sound like minor contributions, but feedback really drives the development of TA.

    Non-members:
    KingMike of KingMike's Translations, who is apparently the creator of the EUC-JP table I used to generate my own conversion table.
    Nasser R. Rowhani for his function hooking code.
    Z0mbie for writing the opcode length detector/disassembler I use for hooking. Apparently was intended for virus-related use, but works fine for other things, too.
    And the creators and maintainers of edict, MeCab, and zlib.

    You might also be interested in:
    *Setsumi's TA Helper and AGTHGrab.
    *errotzol's replacements script.
    *Devocalypse's devOSD.
    *kaosu's ITH (Like AGTH. No direct TA support, due to lack of a command line interface, but definitely worth checking out).

    MeCab
    edict2

    Changelog:
    0.4.9
    * Fixed MeCab/JParser getting stuck when starting a new translation before the last is fixed.
    * Fixed interface lockup while mousing over an item in MeCab while JParser is running.
    * Menu translation will now translate column headings in ListViews (Needed this for the AA launcher)
    * Fixed ATLAS config crash.
    * Global hotkey support. Toggle under "File" menu (Tools is kinda big already). Currently only really supports history navigation. May add more later.

    0.4.8
    * Added history. Logs both original text and translations (For online translators). It logs up to 20 MB of original text, and whatever translations are associated with it. Currently only way to force a retranslation is to toggle one of several options (Autoreplace half-width characters, src/dest language, modify substitutions).
    * Fixed deadlock bug on MaCab mouse over while JParser is running.
    * Fix corrupting built-in text hooker settings when launch failed. Suspect no one uses this, anyways.
    * Drag/dropping an exe onto TA to open up the injection dialog now actives TA.

    0.4.7
    * JParser and MeCab each use their own thread (Mostly).
    * Changed conjugation table format to JSON - plan to do this to a lot of other files (Being careful not to mess up game settings or substitution tables). Currently have way too much file loading code.

    0.4.6
    * Fix WWWJDIC
    * Fix closing injection dialog
    * Updating process list 10+x faster
    * Process list autoupdates
    * Fixed bug that would result in injecting into wrong process when one program is running multiple times.
    * Updated included AGTH version

    0.4.5
    * Added bing support.
    * Updated Honyaku code (They didn't try and block TA, they just modified their HTML)
    * Fixed AGTH command line code.
    * Replaced "/GL" with "/SM" compile option, resulting in faster builds when one has a lot of cores.

    0.4.4
    * Regular expressions are now compiled
    * Injection validation when using addresses relative to dlls (Or function addresses in dlls) should be fixed.
    * Added option to create shortcuts. They'll launch TA (If it's not running) and try to launch the game using the current injection settings (Injection settings that you'd get at the launch screen - the current settings are not saved - it always uses the most recently used ones).
    * Appropriated some of Setsumi's code to make tooltips larger.

    0.4.3
    * Multiple subcontexts now supported. Separate them with semi-colons. AGTH code converter will add two subcontexts, when appropriate.
    * Using aliases for hooks added. Prefix a hook with "[Alias Text]" and that's what will be displayed on the context manager screen as the hook's name. Makes it easier to see context strings.
    * Locale selection added to injection dialog.
    * "Hook delay" added to injection dialog. Actually doesn't delay hooking, delays how long before hooks that use filtering based on calling function's dll are enabled. Generally only the default hooks do this. Increasing this delay may circumvent issues with games that crash when launched with AGTH, but work fine when injected after launching.
    * Added "!" and "~" operators.

    * Stomp's admin privilege fix when using some 3rd party software added.
    * Excite fixed
    * Fixed sanity testing for injection addresses, so when specify a dll or exe name in a text hook, shouldn't erroneously think it's an error when the module isn't loaded in the current address space.
    * Fixed some JParser dicrionary common word parsing, when using versions of edict with entL entries. Also changed treatment of Kanji entries when only their corresponding Hiragana are marked as common.
    * Fixed substitution matching Hiragana with Katakana and vice versa.
    * Fixed a clipboard-related crash bug.
    * Fixed hooks causing crashes when relocating call/jumps (Hopefully...)
    * Fixed AGTH repeat filter length placement (oops).

    0.4.2b
    * Fixed substitution loading/deleting.
    * Fixed << and >>.

    0.4.2
    * AGTH code conversion tool.
    * Injection code checker added.
    * New child process injection handler (Really nifty injection code for that...). Should be a little more robust than before.
    * Option not to inject into child processes added.
    * Auto copy to clipboard added.
    * Both extension filters fixed.
    * Both eternal repeat filters fixed/upgraded.
    * Phrase repeat filter fixed/upgraded.
    * OpenMP/MSVC 2008 SP1 runtime requirement removed
    * char/charBE fixed
    * GetGlyphOutline fixed
    * Copy to clipboard crash when auto translate disabled fixed.
    * Slightly improved dll injection error handling.

    0.4.1
    * More context/filter options.
    * Repeated phrase filter now handles cases where phrase is being extended by a couple characters each time (xxyxyz, etc). Extension filters no longer really needed, unless the repeat starts out too short.
    * Option to handle eternally looping text.
    * Option to ignore text without any Japanese characters.
    * Text which substitution rules reduce to nothing no longer overwrites translated text.
    * Log length limit added.
    * Options to manage default internal text hooks added.
    * Clipboard treated as a context. Its default settings should mirror the old handling.

    0.4.0
    * Added it's own text hooking engine. Probably still buggy.
    * Fixed excessive redrawing when a hidden furigana window had clipboard translation enabled.
    * Works with new, even more poorly formatted edict files.
    * Handles EUC_JP characters that Windows does not (Doesn't use them properly with WWWJDIC at the moment, however). Only really fixes loading edict files with those characters.
    * Fixed right clicking when full screen.
    * Fixed not checking auto Hiragana mode.
    * Less picky when reading MeCab output.
    Attached Files
    Last edited by ScumSuckingPig; 07-11-2015, 11:20 AM. Reason: Change download link, re-upload attachments upon request from Setx

  • Since when does TA consist of just an exe and dll. I overwrite everything with each new version. All functions are working. All settings are preserved including profiles and custom dictionaries. Haven't updated edict since last year.
    devOSD nEXT - advanced eroge translation overlay

    Comment


    • Originally posted by Blago View Post
      When you update your previous TA to the latest version (overwrite the .exe and the .dll), JParser doesn't recognize it even if edict2 is still there in the dictionaries folder, after messing around with it a bit I made it work again, I guess it was after deleting everything in the dictionaries folder (except conjugations.txt) and then extracting edict2 there again.
      Since I updated the compiled dictionary format (Well...just updated the conjugation tables, actually), it will want to recompile the dictionaries. If you deleted the uncompiled copy of edict in your dictionaries directory, then that will happen. If it's still there, it should silently rebuild its dictionaries.

      Edit: You'll also need to overrwrite the conjugation tables file, as I changed its format. Note that no configuration files are included in the rar, so you should be able to safely overwrite everything without losing any settings (Except when I change file formats).
      Last edited by ScumSuckingPig; 06-05-2011, 07:26 AM.

      Comment


      • Is it always safe to overwrite everything?

        I have that many shortcuts/profiles/substitution files - would be really bad to lose any of it...

        I had the jparser problem with the conjugation.txt too, since i always only overwrite the .dll and .exe of TA out of fear it would overwrite anything important...


        Originally posted by ScumSuckingPig View Post
        Since I updated the compiled dictionary format (Well...just updated the conjugation tables, actually), it will want to recompile the dictionaries. If you deleted the uncompiled copy of edict in your dictionaries directory, then that will happen. If it's still there, it should silently rebuild its dictionaries.

        Edit: You'll also need to overrwrite the conjugation tables file, as I changed its format. Note that no configuration files are included in the rar, so you should be able to safely overwrite everything without losing any settings (Except when I change file formats).

        Comment


        • I'm very careful about what I add to the rar. I have a separate "pristine" install directory that I copy release binaries to just prior to release (Which is why I forgot to update them in my first 0.4.7 release). It has no configuration files. I now never run TA from there (I used to, when debugging, which would occasionally result in accidentally adding a TA.ini file, which just contains TA general settings, but I'm now sufficiently paranoid that I no longer do so).

          Moreover, game-specific profiles each have their own name, so there's no real chance of wreaking havoc on them. TA shortcuts just have the exe name to launch, and use whatever profile is associated with the exe. The only files where the name doesn't change are the substitution file, and the generic settings ini file.

          That having been said, I *have* released versions that corrupted the substitutions file. This wasn't because of an extra file, but rather because of a bug in my code. So it might make sense to back that up before updating, if you have a long one.

          Comment


          • Thanks for the info guys. Not I got to use the JParser. But I still don't get it about the function of Mecab & JParser, it's functionly to make the Japanese words become better than not use it and the Atlas result become more perfect for translation? (Is the Atlas changed the result between use the Mecab+JParser and not use it?)

            Comment


            • MeCab and JParser don't affect ATLAS. They provide a word-by-word breakdown, which can help in understanding particularly poorly translated words and sentences. They're most useful if you know at least a smattering of Japanese.

              I had thought about turning JParser into its own translation engine, but there were too many issues (Figuring out which subclause describes what, left off pronouns, topic vs. subjects vs. object, edict isn't really a good dictionary for translating).
              Last edited by ScumSuckingPig; 06-05-2011, 08:43 AM.

              Comment


              • Originally posted by ScumSuckingPig View Post
                MeCab and JParser don't affect ATLAS. They provide a word-by-word breakdown, which can help in understanding particularly poorly translated words and sentences. They're most useful if you know at least a smattering of Japanese.
                Speaking of jparser:

                i was wondering if there would be a way to improve jparsers results (word breakdown) somehow?

                It works very well using edict2, but using the japanese-german dictionary "wadoku", theres alot of junk in the jparser windows. i think this could be fixed if you would filter out special characters, since they're described (they have dictionary entrys) in this dictionary, and if you would give us an option to limit the max length of a word (since wadoku contains alot of examples and example sentences too, wich are of course breaking the word recognition...).

                do you know something you could do about that? there's no other good japanese-german edit-formart dictionary, so i'm stuck to edict2...

                (^・^)

                Comment


                • Originally posted by tamers182 View Post
                  Speaking of jparser:

                  i was wondering if there would be a way to improve jparsers results (word breakdown) somehow?

                  It works very well using edict2, but using the japanese-german dictionary "wadoku", theres alot of junk in the jparser windows. i think this could be fixed if you would filter out special characters, since they're described (they have dictionary entrys) in this dictionary, and if you would give us an option to limit the max length of a word (since wadoku contains alot of examples and example sentences too, wich are of course breaking the word recognition...).

                  do you know something you could do about that? there's no other good japanese-german edit-formart dictionary, so i'm stuck to edict2...

                  (^・^)
                  I'd need to see the dictionary you're using, in edict format. A quick search didn't turn up anything.

                  I believe I have a filter somewhere to prevent a similar entry appearing for certain similar entries in edict (Or at least Furigana for similar entries).

                  Comment


                  • Originally posted by ScumSuckingPig View Post
                    I'd need to see the dictionary you're using, in edict format. A quick search didn't turn up anything.

                    I believe I have a filter somewhere to prevent a similar entry appearing for certain similar entries in edict (Or at least Furigana for similar entries).

                    I uploaded the dictionary HERE.

                    I'll make some screens of jparser with it and upload them later.

                    edit:

                    heres a screenshot showing some of the problems:
                    Spoiler
                    Last edited by tamers182; 06-05-2011, 01:17 PM.

                    Comment


                    • And just nuking the lines with "[] [] [] [] [] [] [] [] [] []" isn't enough? Looks like the file lacks part of speech info, too, which breaks my verb conjugating (Which is rather important, since I try and match every word).

                      The ideal solution would be to merge it with edict, taking the parts of speed from edict, and dropping unmatched entries, but I don't have time for that, unfortunately.

                      Comment


                      • Originally posted by ScumSuckingPig View Post
                        And just nuking the lines with "[] [] [] [] [] [] [] [] [] []" isn't enough? Looks like the file lacks part of speech info, too, which breaks my verb conjugating (Which is rather important, since I try and match every word).

                        The ideal solution would be to merge it with edict, taking the parts of speed from edict, and dropping unmatched entries, but I don't have time for that, unfortunately.
                        And i don't have the knowledgle do to so, unfortunately.

                        I guess i have to stick with edict2 then - or is there any "better" japanese-englisch dictionary in edict format?

                        what did you mean with "lines with '[] [] [] [] [] [] [] [] [] []' isn't enough?" Would that change anything?

                        Comment


                        • Originally posted by tamers182 View Post
                          And i don't have the knowledgle do to so, unfortunately.

                          I guess i have to stick with edict2 then - or is there any "better" japanese-englisch dictionary in edict format?

                          what did you mean with "lines with '[] [] [] [] [] [] [] [] [] []' isn't enough?" Would that change anything?
                          Open up the dictionary with a text editor...there are about a dozen lines with "[] [] [] [] [] [] [] [] [] []" in them. All 3 of the words you have nasty-looking furigana above are among them.

                          Comment


                          • Originally posted by ScumSuckingPig View Post
                            Open up the dictionary with a text editor...there are about a dozen lines with "[] [] [] [] [] [] [] [] [] []" in them. All 3 of the words you have nasty-looking furigana above are among them.
                            You may hit me if the solution is that simple...

                            Comment


                            • That still won't fix the verb issue, however, which I suspect will pretty much completely break things whenever you come across one

                              Comment


                              • Originally posted by ScumSuckingPig View Post
                                That still won't fix the verb issue, however, which I suspect will pretty much completely break things whenever you come across one
                                well, since a single verb is all you need for a perfectly fine japanese sentence, i guess i'd encounter them about everytime i hit the enter button.


                                Something else about TA's 0.4.8 update i noticed:

                                could you make the text history hotkey global somehow, so that i don't have to select TA's window to use them?

                                They didn't work ingame...

                                Comment

                                Working...
                                X