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, 12:20 PM. Reason: Change download link, re-upload attachments upon request from Setx

  • Yeah, I posted something like that many pages ago and stopped using google because of that. I regularly ran into google no longer answering the requests.

    Comment


    • i noticed that to about google stoping responding to requests.

      going therfe by oneself i ended up at a "im sorry but you'r request looks like automatic request. please check if you got any viruses" page witha human verification code.

      so using google to often would probylary mean that one end's up on some sort of ip blacklist to stop automatic request's
      Weirdly enough things seems to get easier with experience.
      ----------
      My カスタム隷奴2+ Grafics patch
      Agth /hcodes found by me!
      Found so far 6

      Comment


      • Tried out TAA with Atlas 14 on a fresh install and it seems that the activated trial somehow causes a crash with atlcheck.dll in the target application when trying to inject/launch with menu translation activated (no crash without).

        Comment


        • Is there a trial popup when running my main executable? Probably a threading issue.

          Comment


          • Originally posted by ScumSuckingPig View Post
            Is there a trial popup when running my main executable? Probably a threading issue.
            yeah, trial popup via taa shows up. not sure if that is caused by clipboard translation or the hooking though (or both)

            Comment


            • It's probably caused by linking the ATLAS dll. Loading the dll pops up the registration message, which causes a crash (Games probably don't like having a second thread running that they know nothing about popping up strange windows on them). Not sure how I'd fix the problem, other than by getting rid of the popup, which I'm not sure how to do, and not sure I'd want to do even if I could.

              Edit: Hmm...Could theoretically even be me trying to translate something while the window's up, which would be bad...
              Last edited by ScumSuckingPig; 02-25-2009, 06:15 PM.

              Comment


              • Hello, I really like that program of yours. It's been a godsend for me in order to play my first non-english sim that wasn't put out though an english company. But, like a few others here, I've come across the Google error page. BUT, I may have a solution for you and others to get around it. Since Google provides a CAPCHA on the page you may be able to use it in a pop-up window so a user can input it and go on normally.

                Here is the HTML code for that section, taken from the page:
                Spoiler


                <form action="Captcha" method="get">
                <input type="hidden" name="continue" value="http://translate.google.com/translate_t">
                <input type="hidden" name="id" value="3373129272379505202">
                <table cellpadding="4" cellspacing="0" border="0">
                <tr><td valign="top" align="left">
                <font face="Arial, sans-serif" color="#aa1002">
                <b>To continue searching, please type the characters you see below:</b>

                </font>
                <input type="text" name="captcha" value="" id="captcha" size="12">
                </td></tr>
                <tr><td>
                <div align="right">
                <img src="/sorry/image?id=3373129272379505202&amp;hl=en" border="1" alt="If you can read this, you do not have images enabled. Please enable images in order to proceed."></div>
                </td></tr>
                </table>
                <p>
                </form>



                Using their CAPCHA might help to un-blacklist users of this by google and resume normal translation flow.

                I would also like to suggest that in the next version that some extra options be user adjustable. Like for example opening up the queue, and maybe adding a queue delay of X number of seconds before sending the next request. Any new text added will be included on the same form for the next request instead of sending one line at a time up to the limit set in the program or by the user.

                Also, when a request times out, the delay can be used with the queue to not send a request until a minimum amount of text is in the queue before sending it to a server, so a server flood would be nearly impossible. Another thing would be if there IS a delay and there is a number of lines queued, the program could add delimiters to the translation text to indicate the lines separately to avoid confusion if 3 or more lines get queued before the server starts responding again.

                It would also be nice if there is queued text that can be displayed while the server is busy with a previous request. But this is optional.

                The outputed text might look like this:

                Sent Request:
                「おにいちゃん、起きて……」
                "Older brother, wake up……"

                ---- Queue 1 (0.26 seconds)----
                「う~~~~ん……」

                ---- Queue 2 (0.28 seconds)----
                「おにいちゃんってば……」

                ---- Queue 3 (0.42 seconds)----
                「もう朝だよ? 早く起きないと、ちこくしちゃうよ……?」

                ---- Queue 4 (0.24 seconds)----
                「ねぇ、起きて。ねてたらだめだよ……」

                The purpose of the time in seconds is to tell the program the amount of time has passed since the last line of text was passed to it. The time also tells the program that the text is to be parsed in "lines" rather than mashed together into one continuous block of text. So if one is skimming though the text very fast, it won't bog down the program nor the servers. Well, as long as the program can keep up with the speed of the text from the game. The fast forward function does tend to do this a lot, but no big deal.

                This example shows about less than 3 seconds of queued up text total, though realistically the times would be longer, if the user was taking their time to read it.

                The above is what the queue text might look like before being sent to be translated if one or more servers is taking it's time to respond. Though only the dashes or other delimiter characters could be used for the sent request rather than exactly what's above.

                Like this:

                - Q 1 -
                「う~~~~ん……」

                - Q 2 -
                「おにいちゃんってば……」

                - Q 3 -
                「もう朝だよ? 早く起きないと、ちこくしちゃうよ……?」

                - Q 4 -
                「ねぇ、起きて。ねてたらだめだよ……」

                The above would be what's sent to be translated. You may choose to use your own version or let the user customize it. Notice that in the first set of text that 1 line is already translated. That would be what the server is currently working on while the queue builds up before the next request goes out. This would apply to both server timeouts and to user set time or minimum # of lines delay rules.

                If it receives a large number of lines in a short period of time, say 25 lines in 5 (or other user settable) number of seconds, it will automatically use the delay time or number of character limit rules for it's next server access if enabled. It would also be nice to customize these rules for each translator as well as globally.

                If this is not too hard to implement, I'm sure that we all will be able to continue to enjoy the great games out there without looking too suspicious to those online translator administrators. I may have some more ideas as I continue use of the aggregator for all my translation needs.

                Thank you for your efforts and a wonderful program.

                EDIT: Here is Google's own coding info on thier translator: http://code.google.com/apis/ajaxlang...onje_translate
                Attached Files
                Last edited by Grrdraxin; 02-28-2009, 11:22 PM. Reason: Word corrections
                Lord GrrDraxin - The Lost God

                We are the Otaku. You will be animized (anime-ized). Your visual
                and audible distinctiveness will be added to our own. You will adapt
                to being collected and viewed by us. Resistance is unlikely (futile).

                Sig Revision version 3.8

                Comment


                • Using the manual verification doesn't unblacklist you. I ended up just changing my IP and turning off the Google window in TAA.

                  Comment


                  • Originally posted by DCB View Post
                    Using the manual verification doesn't unblacklist you. I ended up just changing my IP and turning off the Google window in TAA.
                    How many times did you try before you gave up? I tied a few times myself, but it may take a lot more than all of your digets worth.... maybe.
                    Lord GrrDraxin - The Lost God

                    We are the Otaku. You will be animized (anime-ized). Your visual
                    and audible distinctiveness will be added to our own. You will adapt
                    to being collected and viewed by us. Resistance is unlikely (futile).

                    Sig Revision version 3.8

                    Comment


                    • At the moment, I only queue a single line per app, and queuing a new line deletes the old one. AGTH already has timing options to separate lines, see no reason to duplicate that functionality.

                      That having been said, some intelligent way of appending multiple lines together instead and submitting them at once might be useful, but this would still be pretty useless when fast forwarding through a game. Most of the sites have pretty strict submission length limits (WWWJDICT may be the only one without one, not sure), so the sites would still be getting mad at you.

                      Timer of some sort might be nice. Currently not meant for you to be fastforwarding through a game while clipboard translation is on for one of the web-based translators. That's why auto-clipboard translation is disabled by default for those. We'll see.

                      Comment


                      • I have been using this translator to play Cleavage but it has been running smoothly, but today I started playing and I can no longer use Google translation tool. I get this error everytime trying to get translation from Google "Unrecognized response received:

                        <html>
                        <head>
                        <meta http-equiv="content-type" content="text/html; charset=utf-8"/>
                        <title>403 Forbidden</title>
                        <style>
                        body {
                        font-family: Arial, sans-serif;
                        }
                        </style>
                        </head>
                        <body bgcolor="#ffffff" text="#000000" link="#0000cc" vlink="#551a8b" alink="#ff0000">
                        <table cellpadding="0" cellspacing="0" border="0">
                        <tr>
                        <td><b><font face=times color=#0039b6 size=10>G</font><font face=times color=#c41200 size=10>o</font><font face=times color=#f3c518 size=10>o</font><font face=times color=#0039b6 size=10>g</font><font face=times color=#30a72f size=10>l</font><font face=times color=#c41200 size=10>e</font></b></td>
                        <td valign=middle width="100%" style="padding-left: 10px">
                        <table bgcolor="#e5ecf9" width="100%" cellpadding="0"
                        cellspacing="0" border="0" style="border-top: 1px solid #3366cc">
                        <tr>
                        <td><font size="+1">&nbsp;<b>Error</b></font></td>
                        <td align="right" nowrap><font size="-1">&nbsp;</font></td>
                        </tr>
                        </table>
                        </td>
                        </tr>
                        </table>
                        <blockquote>
                        <h1>We're sorry...</h1>
                        <p>... but your query looks similar
                        to automated requests from a computer virus or spyware
                        application. To protect our users, we can't process your request
                        right now.
                        </p>
                        <p>We'll restore your access as quickly as possible, so try again soon. In the meantime, if you suspect that your computer or network has been infected,
                        you might want to run a <a href="http://www.download.com/Antivirus/3150-2239-0.html"> virus checker</a> or <a href="http://www.download.com/sort/3150-8022-0-1-4.html">spyware remover</a> to make sure that your systems are free of viruses and other spurious software.
                        </p>
                        <p>
                        If you're continually receiving this error, you may be able to resolve the
                        problem by deleting your Google cookie and revisiting Google. For
                        browser-specific instructions, please consult your browser's online support
                        center.
                        </p>
                        <p>
                        If your entire network is affected, more information is available in the <a
                        href="http://www.google.com/support/bin/answer.py?answer=86640">Google
                        Web Search Help Center</a>.
                        </p>
                        <p>We apologize for the inconvenience, and hope we'll see you again on Google.





                        </blockquote>
                        <br><table width=100% cellpadding=0 cellspacing=0>
                        <tr><td bgcolor=#3366cc><img alt="" width=1 height=3></td></tr>
                        </table>
                        </body>
                        </html>"

                        Anyone has any idea what the problem is?

                        Comment


                        • That happens when you spam google, which is what we've been talking about. Fast forward the game with auto-clipboard translation enabled for google, and you spam google with requests, which makes google mad.

                          Comment


                          • Originally posted by ScumSuckingPig View Post
                            At the moment, I only queue a single line per app, and queuing a new line deletes the old one. AGTH already has timing options to separate lines, see no reason to duplicate that functionality.

                            That having been said, some intelligent way of appending multiple lines together instead and submitting them at once might be useful, but this would still be pretty useless when fast forwarding through a game. Most of the sites have pretty strict submission length limits (WWWJDICT may be the only one without one, not sure), so the sites would still be getting mad at you.

                            Timer of some sort might be nice. Currently not meant for you to be fastforwarding through a game while clipboard translation is on for one of the web-based translators. That's why auto-clipboard translation is disabled by default for those. We'll see.
                            Yes, I see indeed. I've been messing with the AGTH timing for the clipboard and that seems to do some of the trick. But then people have to scroll to read the text, but that's just a minor thing. Maybe figuring out a way unify the windows could help with that. However, the queue function would be a must in order to keep the translated text synchronized. And of course it's useless for fast forwarding, if it's intelligent enough to recognize text coming in from a "fast forwarded" source, not many would care if it simply ignored it and continued with the next bit of "small" lines of text.

                            The way to do that, would be to set it to not process huge blocks of text it receives in too short a time. naturally this option would need tweeking, But, why not let the users decide what to set it at? It's different for everybody.

                            I set my AGTH to 5000 ms, and that seems to get most everything correct, and doesn't overload the clipboard even during a fast forward. But I'd still like to customize how much text the aggragator will take before it goes into ignore text dump mode though. You have it set at 500, and I'd probably set it at 300 or 400 just to be safe. I even went and changed my router MAC and IP address just so I can use Google again. So far no problems.

                            It's really too bad I don't know squat about coding, or I'd be helping you with that. But I hope my suggestions are insightful and helpful. this program is certainly useful for much more than simply for translating games, that's for sure. I can even surf japanese image forums now, and actually understand what's going on.
                            Last edited by Grrdraxin; 03-03-2009, 02:40 AM. Reason: Adding comments
                            Lord GrrDraxin - The Lost God

                            We are the Otaku. You will be animized (anime-ized). Your visual
                            and audible distinctiveness will be added to our own. You will adapt
                            to being collected and viewed by us. Resistance is unlikely (futile).

                            Sig Revision version 3.8

                            Comment


                            • (bug) Toggling window frame raises clipboard capture event every time, spamming online services. Please, ignore it once after window recreation, or something. I read slow and auto clipboard translation really helps, instead of tedious clicking.

                              (suggestion) to replace Ctrl with Alt or something in all hotkeys. Habit of pressing Ctrl is dangerous and annoying because it activates fast forward in games; i.e. loading from last save and even spoilers.

                              (selfish request) to move Mecab's WORD_PADDING and HEIGHT_PADDING to ini-file from hardcode. It looks much nicer with both of them zero...
                              読んでみた。 読んでみようとした。 読めたらいいな、と思った。

                              Comment


                              • Cool little translation app, too bad Japanese machine translations didn't make sense half the time!!

                                A few notes....

                                Atlas and Excite basically run off the same translation software btw, the only difference is the Atlas settings and the user dictionary. So if your looking to close a frame for more room end users....

                                I'd also add frames for these websites, especially OCN its one of the most recognized translation engines in Japan and provides a very different translation then most others. Works very well for game dialog:

                                http://www.ocn.ne.jp/translation/

                                I'd also make frames for:

                                http://www.magicalgate.net/ja/index.html#

                                Good luck everybody! (reading machine translations gives me a head ache...)
                                Last edited by SatinCreamDelight; 03-03-2009, 02:34 PM.
                                "Its done when its done."
                                - Blizzard Entertainment

                                Comment

                                Working...
                                X