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

  • Tracking back previous version.. I can run both 0.1.5 and 0.1.4 just fine. its the version past .16 that crashing on me.

    The error window spew out is
    the exception integer division by zero. (0xc0000094) occured in the app at location 0x0040977c

    Comment


    • Originally posted by ToxicKing View Post
      I'm on XP SP2 if its any help at all.
      This is it. Was crashing for me too. Installing SP3 fixed the issue for me.
      EDIT: Also, versions 0.1.5 and 0.1.4 was just fine too.
      読んでみた。 読んでみようとした。 読めたらいいな、と思った。

      Comment


      • Maybe keeping a list of games installed on current computer and the settings of them(like a /h code) will help to decrease amount of necessary clicks to start a game. But if the list is complemented this program is more likely to grow into a game helper(launch+get text+dict+translate...)
        sigpic
        Got stuck at AGTH H-codes? Have a try of ITH, supports more game engine.
        http://www.hongfire.com/forum/showthread.php?t=208860

        Comment


        • ToxicKing: A module name would be much more useful. One thing you could test is temporarily moving all the dll files out of the ATLAS directory. Wouldn't be surprised if the issue is with initializing them or something.

          Comment


          • 0.2.0 released. It fixes a couple of the aforementioned problems, and adds its own Japanese parser. You must download and extract edict2 (Or edict, but not jmdict) to its dictionaries directory. It'll make a compiled dictionary in that directory, and automatically overwrite it when you modify the dictionary.

            The display for the Japanese parser is currently very rudimentary, still trying to figure out how to display translations in a more user-friendly format. It's in its early stages, so expect bugs. It should handle most single verb conjugations. Doesn't handle things like the te-form of the progressive tense, but does handle the te-form and the progressive tense separately. Doesn't furiganify conjugated forms of "来る" correctly, but that's not exactly a big issue. Doesn't handle conjugated forms of the copula yet. Currently can only see translations by mousing over the text. Note that my tooltip stuff has a bug so that when I can't fit the entire tooltip below or to the right of the cursor, it flashes on and off repeatedly. Only really an issue with low resolutions or words that have a lot of matches.

            Also not sure about the verb forms with only an informal non-negative form (Continuative, Hypothetical, Attributive, etc). I believe they are stem forms, so it might be best not to include them, at least when there are other hits to the same word, as often one verb's attributive is another verb's non-past form, conveniently enough. Definitely need to at least filter/merge multiple hits for the same word.

            Edit: Just realized that the crash address is in my code, and not in a function call, like I assumed. I don't divide a whole lot, but the address doesn't seem to correspond to one of my divisions. I'll look around again and see if I can find it.

            I'll probably release another version in a week or so, with the JParser fixed up a bit. Curious if anyone has any suggestions in terms of interface for the new stuff. Do plan on adding custom dictionaries with a built-in editor, but that's not a priority.
            Last edited by ScumSuckingPig; 06-19-2009, 12:35 PM.

            Comment


            • TA 0.2.0, WinXP SP3
              #1 Any attempt to show JParser window crashes with division by zero (pic.1). I.e. run clean installation crashes right away. If put old .ini file (disabling initial display of JParser), runs fine, but clicking to display JParser -> crash.

              #2 If TA runs with empty clipboard, Mecab crashes with access violation (pic.2 - pic taken from my debug build just for clearer display, original exe crashes the same). In case of not crashing right away, toggling ON and OFF "two column display" helps it.

              Decided to make debug build to track down error#1
              Got warning:
              Code:
              stringutil.cpp(435) : warning C4566: character, represented by universal name  "\u00A1", unable to represent in current code pade (1251)
              stringutil.cpp(435) : if (fsize >= 2 && !memcmp("¡©", temp, 2)) {
              I think, because of that, dictionary compiler broke, so TA hangs in infinite loop when starting, and edict2.bin file never appear.

              Ignored that, by putting edict2.bin back. TA runs fine and JParser shows at last (i.e. error#1 mysteriously goes away. also running original exe under OllyDbg has the same effect).
              - If TA runs with single character 猫 (neko) in clipboard, JParser crashes with the same furigana error#2
              Last edited by Setsumi; 06-19-2009, 09:11 PM.
              読んでみた。 読んでみようとした。 読めたらいいな、と思った。

              Comment


              • Thanks so much for all that info, made fixing things easy. Finally decided it was worth looking into when I realized it was a problem with my code, had been thinking before I wasn't initializing ATLAS properly. Both bugs are with the Furigana code shared by both mecab and the JParser when there's no text to display. Found that idiv earlier today, actually. The other one is a completely new issue with my mouse over code. Think I've found and fixed both of them (And fixed the compilation thing you were running into, too. No idea why it resulted in an infinite loop, though). Could you (And anyone else with any crash issues) see if the version below doesn't crash? I was able to replicate crash #2 myself, but never got #1. Source and binaries are included.

                Edit: Hmm...Looks like there's an additional bug that causes JParser to ignore the last character of the original text. Otherwise, neko would result in neither bug. Only ran it on sentences with punctuation, so never noticed. I'll fix that and merge redundant verb conjugations in the output (And correctly label formal/negative conjugations), and if the crash issue is indeed fixed, I'll release a new version. Also a bug where I output chopped up Japanese verbs in the alternate spellings list will be fixed, as will the tooltip colors.

                <Edit: Outdated. Attachment removed>
                Last edited by ScumSuckingPig; 06-20-2009, 07:03 AM.

                Comment


                • Crash#1 remains for me. But now TA just terminates silently instead of crashing. Debug version and release version under debugger, works, like before.
                  Otherwise works nice. Thank you very much!

                  Edit: Notice. Looks like dictionary .bin file is system-locale dependent. File generated under japanese locale not work under non-japanese and the other way around. Need to regenerate if locale changed.
                  Last edited by Setsumi; 06-20-2009, 12:37 AM.
                  読んでみた。 読んでみようとした。 読めたらいいな、と思った。

                  Comment


                  • Actually, the .bin files are region independent. They contain only UTF8 and UTF16.

                    I can't manage to get Microsoft to let me to create one when running under a Japanese locale, but once one is built, works fine for me under any locale. Reason I'm blaming Microsoft is that MultiByteToWideChar(20932, *) doesn't seem to convert EUC_JP to unicode properly when running with a Japanese locale. Why not? I have no idea. Notice that WWWJDIC doesn't work when running TAA under a Japanese locale either, for the same reason.

                    Regardless, once you have a bin made under a normal locale, the bin file should always work under any locale, even Japanese, or at least it does so for me. As I'm not going to write my own EUC_JP to unicode conversion function, and Microsoft's doesn't work under Japanese locales (wtf? Specs say nothing about this behavior), a fix for this is unlikely unless enough people complain or I come across some simple workaround. One workaround you could do is convert the edict file yourself from EUC_JP to either UTF8 or UTF 16, I suppose.

                    Here's another experimental fix for the crash thing.

                    <Outdated, see 0.2.1>
                    Last edited by ScumSuckingPig; 06-20-2009, 09:01 AM.

                    Comment


                    • Originally posted by ScumSuckingPig View Post
                      Here's another experimental fix for the crash thing.
                      It works No crashes, no slowdowns!

                      About bin file. I wasn't complaining or anything. Just wrote for information. Delete .bin and restart TA is very easy and not count for "issue". Also, condition like these is very rare, i think.
                      Originally posted by ScumSuckingPig View Post
                      Notice that WWWJDIC doesn't work when running TAA under a Japanese locale either, for the same reason.
                      ???
                      I have separate windows installation with locale and all regional settings set to japanese, dedicated to play such games, and always use TA with WWWJDIC without any problems.
                      Last edited by Setsumi; 06-20-2009, 04:57 AM.
                      読んでみた。 読んでみようとした。 読めたらいいな、と思った。

                      Comment


                      • That's odd - I'm trying now, and when using Japanese locale with WWWJDIC, it simply does not work for me, and it seems to be for the aforementioned reason. I am using applocale to launch it directly, however, so might be something funky with using applocale vs a different regional setting. This issue just seems very strange to me. Spent an hour or so googling for info on it earlier with no luck. Could be we're running into two different problems (Or two different manifestations of the same problem).

                        Anyhow, thanks again for your help testing it and providing all that info. Have to wait and see if anyone else has any other crash issues.

                        Maybe I will create my own string conversion functions. Thinking about it, it's easier than I had been thinking - just create 3 or 4 conversion tables using Microsoft's stuff in an environment where they all work. Might make the exe a fair bit bigger unless I put at least a little work into cleaning them up, but not really a big deal.
                        Last edited by ScumSuckingPig; 06-20-2009, 09:02 AM.

                        Comment


                        • 0.2.1 released.

                          Turns out it was two completely different issues. My search function uses a pre-calculated binary search tree based on Window's comparison function, which varies by locale. This is the issue you were running into. There was actually a simple fix for that. The issue I was running into seems to only be a problem when using AppLocale, rather than a general locale issue, so is probably not worth the effort of fixing. AppLocale apparently has no affect on sorting order.

                          0.2.1 fixes the sorting issue, and (hopefully) fixes all crashing issues. Should automatically recreate any dictionaries the first time it's run. Updated the conjugation table a little, too, so make sure you extract that as well. Also fixes all issues I know about in terms of which translations are displayed. If anyone runs into any more crashes, please do tell me.
                          Last edited by ScumSuckingPig; 06-20-2009, 09:57 AM.

                          Comment


                          • #1 Sometimes JParser picks for furigana and(or) on top of pop-up, most obscured meanings buried behind others instead of obvious ones. (pic.1)
                            #2 Also JParser incorrectly handles words like hoshii, ureshii, kanashii (pic.2)

                            About #2. First thought was to make user dictionary with above mentioned words without last "i" (not pretty), but user dictionary looks like too much effort now. Every time: Add word to user dictionary in JWPCE -> Copy dictionary file to TA directory -> Restart TA to apply changes...
                            It will be so nice if TA has simple dialog for adding words to user dictionary (named "user" for example) and after pressing [Add/Ok] this dictionary be rebuilded and used at once.
                            読んでみた。 読んでみようとした。 読めたらいいな、と思った。

                            Comment


                            • I actually already use the (P) tags when sorting the word list, and when choosing how to parse text...Problem is the dictionary itself. Sometimes it puts (P) tags by Japanese words, like "命 [めい(P);みょう]" and sometimes at random spots in the english translation, like "命 [いのち] /(n) (mortal) life/(P)/". There are two issues there. First, I forgot to sort by (P) tag before getting the furigana. Second, although I already use them when creating the list of definitions, I only use the (P) tags after the Japanese words. First issue has already been fixed. I'll fix the second before my next release.

                              There's a bug with the i-adjective tables so they aren't being used at all...But if the shii adjectives are a special case, I need the rules for them so I can make another table for them as well. Once they're in a conjugation table, all necessary chopping up will be handled automatically, like it is with verbs. Don't suppose you have a reference? I've found it very difficult to get complete and accurate conjugation information. Also, different sources seem to use different names for the same tenses, which makes things even uglier.

                              Edit: Also, do plan to get in an interface for adding to a dictionary. Would work just like edict, in that there'd be a plain text version and a compiled version, so I could change formats without breaking it, but would allow changes directly in TAA. As a quick fix, could also check for modifications to any dictionary file before a translation, and reload it if there are any. All I'd need to check is the modification date, so wouldn't be a noticeable slowdown (Except when large dictionaries were changed, of course).
                              Last edited by ScumSuckingPig; 06-21-2009, 02:35 AM.

                              Comment


                              • Posting 0.2.2 now. Wasn't planning on that many releases over the weekend, but like to have people beating on the latest version.

                                0.2.2 fixes the adjective table and both those issues with not favoring words labeled with a (P). Also handles stacked verb tenses, so can now recognize things like causative passive negative past tense.

                                Also should check the dictionaries before each translation, and update if any of them have been changed. And I fixed a couple bugs related to using multiple dictionaries. More than one dictionary should work fine, now. Note that dictionaries must start with 4 full-width question marks and have no extension. First line will always be ignored. Dictionaries can be in EUC_JP, UTF8, or UTF16 format. Been forgetting to add SJIS detection.

                                Also lets you drag windows out of the main window (And can then put multiple child windows together in a new window...Kinda nifty). Required pretty significant infrastructure changes, so may have some bugs in terms of top-level interface behaviors, though everything seems to be working.

                                Setsumi: For some reason, I was thinking what you posted yesterday had the "shi" inflected in some funky way. First two were just a result of the adjective table bug. 3rd one won't be fixed by fixing the bug, as I don't display stems. And even if I did, there are two parseable words there that might score just as highly as the stem and "sou" would. Only possible solution I can think of would be to create a new conjugated verb "tense" consisting of an i-adjective and sou. Then that particular combination would work fine, but it doesn't scale well, so only makes sense for fairly common cases.

                                Tenses currently have to be hard-coded in addition to being put in the ConjugationTable.txt file, but I'm thinking about changing that.
                                Last edited by ScumSuckingPig; 06-21-2009, 08:45 PM.

                                Comment

                                Working...
                                X